Related
Hey there =)
I´ve often read threads and posts by people how did not realy know what they did and after an interrupted flash or a bad rom the phone does not work (propperly or at all) and now they think they really messed up theyr phone...
I know that there are many different phones and roms and ways to so called " soft brick" your phone but if you follow the statet steps you will bring your phone back to life =)
1. DONT WORRY and stay calm
2. Find out how to get into the recovery mode
2.1 If you found out try to whipe data/cash and restart the phone
(many people have bootloops after flashing a rom and dont whipe the data/cash)
3. If there is no way to safe your Firmware (for instance due a interupted flash) search (google) for a stock rom wich fits to your region and phone
(For instance "flashing I9001 stock rom" if you have a sgs+
4. In most of the cases youll find what you are searching for (samsung roms can be found on http://www.sammobile.com/firmware/)
5. If you are really a noob you have to know that the software wich is needed to flash a firmware is odin (in xda forum you will find what youre searching for)
All in all you have to know that there are many people who have or had the same problems like you and you dont have to worry you will make it
Im posting this thread because a few years ago i was total android noob and learned how to flash in the way i stated above
Stay well =)
Only a question. The jig usually help if your bootloader got corrupted ( or something like that) , or no way to save it?
Enviado de meu GT-S7500L usando o Tapatalk 2
gabriel2anjos said:
Only a question. The jig usually help if your bootloader got corrupted ( or something like that) , or no way to save it?
Enviado de meu GT-S7500L usando o Tapatalk 2
Click to expand...
Click to collapse
if never had to use the jig and because of this im not very introduced in this topic but a few days ago i read a thread dealing with such issues....a guy who flashed a bad rom couldn get into download mode neither the recovery mode so a dev suggested to use the jig to get fixed....
keep on searching
but as far as i know first of all try to reflash a stock rom one package via odin this ficked all my probles over the last years
fare well my friend
I have a ZTE V9 and i cannot enter not even into the recovery mode.
Keeps flashing all the time the "Robot" screen.
Any ideas?
AW: You did not brick your phone!!! 5 Steps to unbrick
Hey there i have a tool from ZTE it is for the Recover . I had the problem that i installed Cyanogenmod 7.2 and wanted back to 7.1 so i started the CWM and then wipe cache and data/factory reset and then installed via sd card. And then it stucked at the Android Logo . When i was trying to use the CWM i boots up to the menu and then only the Power Button worked . So i cant choose anything only Reboot System . Then i searched and found the ZTE tool .
I'll upload it later if you need ?
Sent from my GT-I8160 using xda app-developers app
Please do
Sent from my SPH-D710 using Xparent Blue Tapatalk 2
I have a suggestion to add in the OP,
For sony phones you can use the sony update tool to unbrick your phone,
Or what worked for me when i bricked my device and nothing worked: flashing all the mods you have at once and wipe everything
sony xperia ray
ics 4.0.4 rooted
stock rom
I flashed TWRP on my new tablet and now when I power it up, it is stuck on the boot screen. I can power it on and off but that is it. I can't get in to recovery and I can't even charge it. My computer does not recognize it now either. What can I do? How do I fix this? Please help!!!
My tablet is from Tablet Express. It is called a Dragon Touch X10. The ID is LMY48B. According to Google, the LMY48B is a Nexus 5 Hammerhead. The TWRP that I flashed was for the Nexus 5 Hammerhead.
Nice one...
Keep it up... its worked for me:good:
AndroidLover819 said:
I flashed TWRP on my new tablet and now when I power it up, it is stuck on the boot screen. I can power it on and off but that is it. I can't get in to recovery and I can't even charge it. My computer does not recognize it now either. What can I do? How do I fix this? Please help!!!
My tablet is from Tablet Express. It is called a Dragon Touch X10. The ID is LMY48B. According to Google, the LMY48B is a Nexus 5 Hammerhead. The TWRP that I flashed was for the Nexus 5 Hammerhead.
Click to expand...
Click to collapse
Build ID's are for a particular branch of Android, LMY48B = android-5.1.1_r3
For a custom recovery, like TWRP, it needs to be built for your device (or ported from a similar device, with an Allwinner chip)
You can go to the Tablet Express website and more than likely get the tools and firmware you need to fix your tab, link
So I had a rooted Galaxy Tab 4 10.1 that I didn't have any backups for and I stupidly changed the DPI of the screen and rebooted the device and it started up in bootloop and I tried recovering it and nothing would work. So I finally settled on the wipe and factory reset, and now it starts up VERY SLOWLY, and the start of the set up for the device shows up but constantly I'm being bombarbed by TOUCHWIZUI has stopped working and 3 other things keep popping up saying they have stopped working. The touch screen barely works.
I have no idea what to do. I have no backups. I am not that familiar with android. I am downloading the stock firmware and am going to try to put it on with odin but I doubt it's going to work.
Can someone give me some advice on what to do? I would REALLY appreciate it.
Sincerely,
SalvelinuxFontinalix
BTW. The tab is the SM-T530NU Canadian (Wifi) version. The firmware I am downloading is the T530NUUEU1ANI1_T530NUXAC1ANI1...
Can I use ODIN to flash this firmware from my PC onto the device or will it be a huge problem if the tablet has been wiped and factory reset and is missing all sorts of information?
Your gonna need to flash the stock rom for the device.
Thank you for your guidance!
zelendel said:
Your gonna need to flash the stock rom for the device.
Click to expand...
Click to collapse
Thank you so much I did what you said. I found the stock rom and "flashed it" I got it back to exactly how it was when I got the tablet! I was unsure how to do it but I learned a bit on my own form the search feature of XDA. I found the stock rom out of a list of many different ones and I found the correct ROM for my country and area and flashed it on with ODIN using my PC and it rebooted and was brand new. I re-rooted it and decided not to alter the DPI of the screen. It's nice enough as is.
Thanks Again! Zelendel! You are a life safer! Oh and BTW...is using ODIN to transfer the stock ROM onto the device considered "flashing"? Or is there some other way people flash devices?
Thanks again I'm so thrilled I don't have a broken device haha. THANKS!!!
Sincerely,
SalvelinuxFontinalix
SalvelinuxFontinalis said:
Thank you so much I did what you said. I found the stock rom and "flashed it" I got it back to exactly how it was when I got the tablet! I was unsure how to do it but I learned a bit on my own form the search feature of XDA. I found the stock rom out of a list of many different ones and I found the correct ROM for my country and area and flashed it on with ODIN using my PC and it rebooted and was brand new. I re-rooted it and decided not to alter the DPI of the screen. It's nice enough as is.
Thanks Again! Zelendel! You are a life safer! Oh and BTW...is using ODIN to transfer the stock ROM onto the device considered "flashing"? Or is there some other way people flash devices?
Thanks again I'm so thrilled I don't have a broken device haha. THANKS!!!
Sincerely,
SalvelinuxFontinalix
Click to expand...
Click to collapse
Yes it is. There are other ways with custom recoveries but that is only for custom rom flashs
It's for A7600-F version! I didn't test it on other variants.
Also the boot.img is for ...150401_ROW firmware. (the latest one)
TWRP + unsecured boot.img
* You need to be rooted at least for the while to do it. The easiest way is to use KingRoot. You can uninstall it later and/or replace it with SuperSU.
1. Download the images and copy them to internal storage -> Google Drive
2. Turn on USB Debugging, then use Android Emulator or ADB shell to type those commands:
Code:
dd if=/sdcard/TWRP_2.8.7.x_a7600f.img of=/dev/recovery bs=16777216 count=1
dd if=/sdcard/unsecuredboot_a7600f.img of=/dev/bootimg bs=16777216 count=1
Root
1. Just flash SuperSU in TWRP.
Bugs
*Screen sometimes doesn't turn on after it goes to sleep (Workaround: Settings-->Screen->Uncheck screen timeout)
*Reboot doesn't work (Workaround: adb reboot or reboot in Terminal Command)
Also external storage isn't tested.
Source: github
Replaced TWRP image with new version with better interface and it should be more stable in overall.
Anyone tried this? Success?
Gesendet von meinem Lenovo A7600-F mit Tapatalk
smogan said:
Anyone tried this? Success?
Gesendet von meinem Lenovo A7600-F mit Tapatalk
Click to expand...
Click to collapse
I had this device and it works lol
Hello!
Is there a way back to stock revocery? because i need to reflash the whole tablet and smart phone tools dont recognize the tablet anymore.
Could we use flashify?
Sent from my LG-D850 using Tapatalk
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
Also, this is for the regular a10-70f or a7600-f not the tab 2 version of the a10-70 correct?
Sent from my LG-D850 using Tapatalk
Bump
I too want to know if this works. Flashify or terminal dd command? Anyone?
I tried it with the dd command line. It works. But I don't know to get back to stock, because the flash tool for stock firmware now does not recognize my tablet anymore.
Maybe someone can make a backup of the system partition for me?
Gesendet von meinem Lenovo TAB S8-50F mit Tapatalk
smogan said:
I tried it with the dd command line. It works. But I don't know to get back to stock, because the flash tool for stock firmware now does not recognize my tablet anymore.
Maybe someone can make a backup of the system partition for me?
Gesendet von meinem Lenovo TAB S8-50F mit Tapatalk
Click to expand...
Click to collapse
Ouch Yeah I am rooted and have it the way I like and even have xposed running, but feel unsafe without a custom recovery installed yet.
Still no recovery solution
Have tried the guides that are around the net, but when I try them my tablet always wakes and boots when plugging it in to use flash tool. I have noticed that there is a flash boot option on tablet but flashtool did nothing in that mode. So I have been trying the apps like flashify to flash recovery directly and haven't been successful yet. Any suggestions are more than welcome at this point.
Lenovo A10-70F 4.4.4 KitKat Rooted
Installed recovery without a pc
Was finally able to install carliv (google it) up and running after trying every recovery image I could find.
First I backup up the stock recovery with rashr flashing tool then flashed the carliv img and boom a recovery solution. Tried many images from the internet and the non-touch version of carliv is the only one that would run.
spacenut said:
Was finally able to install carliv (google it) up and running after trying every recovery image I could find.
First I backup up the stock recovery with rashr flashing tool then flashed the carliv img and boom a recovery solution. Tried many images from the internet and the non-touch version of carliv is the only one that would run.
Click to expand...
Click to collapse
Would you care to tell us which version worked on your device? Nowhere do I see it compatible with the MTK 8165 that's running in this device. Also, the links I followed on xda only mention a touch version of the recovery. Am I missing something?
I'm hoping not to have to spend weeks experimenting to be able to get functionality that should never have been locked out in the first place. I can see the time in the near future where these software giants will finally be sued for willfully selling products that are essentially, deliberately crippled (like they are now). Unlocking my Galaxy Note 2 to gain full ownership was a piece of cake compared to this.
And if I may, as an old timer, rant a little - I've grown pretty sick and tired of the homeland security-esque computing environment of the last few years. When I get too depressed, I fire up my old Windows 98SE machine, tweaked to run like Windows 95, sit back and smile at how easy efficiently I could do everything with it...
Well, enough ranting for now. I'm sure a lot more people are going to start looking at ways to get this device to actually work for them after Christmas, as more people get it considering its great hardware features for the price and we'll get more input on these threads.
Keep up the good work folks, I'll keep looking on my end.
Well, after reading a lot and trying a few things here's what I discovered, for those who have this tablet:
Fist of all, thank you Lenovo for making a tablet that is designed for productive work! I got an external SD Card and was able to easily enable USB Mass storage mode directly without rooting, scripting or any other shenanigans
Furthermore, although this thing is running Kitkat 4.4.4 and although I wasn't sable to directly write to the SD Card, I was able to copy created content from the internal to the external SD Card without any issues. It's just that one cannot write from an installed app to the external card (at least that's what it seems to be from early testing with the tablet in unrooted, original OEM configuration).
I've been collecting files and information and as soon as I get this tablet fully under my control with root and a custom recovery I'll make a write up on it here if there is any interest.
Now if I could only find a way to turn down those impossibly garish colors in my pictures... For now it will have to wait, got stuff to take care at the house now, mess has been accumulating since I got the tablet a few days ago
Sorry I don't recall where I got the recover from it was some German sight. The non-touch version was all I was able to get to work.Play store has apps to fix the read only external sdcard.
Sent from my Lenovo TAB 2 A10-70F using XDA Free mobile app
spacenut said:
Sorry I don't recall where I got the recover from it was some German sight. The non-touch version was all I was able to get to work.Play store has apps to fix the read only external sdcard.
Sent from my Lenovo TAB 2 A10-70F using XDA Free mobile app
Click to expand...
Click to collapse
No problemo, I found it on the Russian Lenovo Forum, after reading this thread on xda-developers in its entirety (a MUST READ IMO) and a couple of other online postings elsewhere.
Basically, the recovery for kitkat (4.4.4) is here, for Lollipop 5.0.2 you need to use the one in that thread. Use Google Translate if you must, it's in the Russian.
I'm not sure why you couldn't get touch to work, and if you're worried because it's for the L version of the tablet originally (the tablet version with cellular data), although posted for the A10-70L (WiFi and Cellular version), it's been tested to work on the A10-70F by this new guy in this post, who succeded in rooting his Lollipop updated tablet, he's written a very nice summary of the whole procedure, so that's good enough for me.
I'll see how it goes as soon as I get my SD Card, which should be in a few days.
For those who wonder about this recovery, I've checked a few youtube videos, it's based it's based on ClockWorkMod, so if you're familiar with it you'll feel right at home. Just make sure you get the right recovery version for your tablet's android version
Old faithful said:
No problemo, I found it on the Russian Lenovo Forum, after reading this thread on xda-developers in its entirety (a MUST READ IMO) and a couple of other online postings elsewhere.
Basically, the recovery for kitkat (4.4.4) is here, for Lollipop 5.0.2 you need to use the one in that thread. Use Google Translate if you must, it's in the Russian.
I'm not sure why you couldn't get touch to work, and if you're worried because it's for the L version of the tablet originally (the tablet version with cellular data), although posted for the A10-70L (WiFi and Cellular version), it's been tested to work on the A10-70F by this new guy in this post, who succeded in rooting his Lollipop updated tablet, he's written a very nice summary of the whole procedure, so that's good enough for me.
I'll see how it goes as soon as I get my SD Card, which should be in a few days.
For those who wonder about this recovery, I've checked a few youtube videos, it's based it's based on ClockWorkMod, so if you're familiar with it you'll feel right at home. Just make sure you get the right recovery version for your tablet's android version
Click to expand...
Click to collapse
Not sure why the touch won't go. I was aware that the "f" and the "l" are the same with the latter just having data. Thanks for "cleaning up" the thread for us. Merry Christmas.
spacenut said:
Not sure why the touch won't go. I was aware that the "f" and the "l" are the same with the latter just having data. Thanks for "cleaning up" the thread for us. Merry Christmas.
Click to expand...
Click to collapse
Thank you for the good wishes
I found a great video online for backing up your own ROM http://bit.ly/1J6x6ruhere and am doing that next while the turkey is cooking and report back afterwards
Since my ROM is a slightly different version from the one posted before I thought it would ne best to make my own to make sure I don't run into problems should I need to get warranty service.
The instructions make it a very simple process, the only thing that isn't clear is what to do to make the tablet read and writable, since in that video you're supposed to remove the battery, which can't be done on our machines. I presume a simple power off should do. I'll be back when it's done.
Sent from my Note 2 using Tapatalk
Backing up
I just back up in Carlviv. The only issue is it does not see my external sdcard. So it takes up lots of room on the device.
spacenut said:
I just back up in Carlviv. The only issue is it does not see my external sdcard. So it takes up lots of room on the device.
Click to expand...
Click to collapse
Indeed - and it's difficult to understand why considering the SDCard can easily made writable - But you can move the backup later if you so wish. I just don't like the idea having to shuffle everything all the time. It's a huge annoyance.
I guess the only solution for now is to move on to lollipop...
Sent from my Note 2 using Tapatalk
I have this problem too but in a more complex version, I need to install TWRP whilst in a bootloop to gain ADB access because then I can push the stock ROM and fix the problem so I was wondering if you could do this without ADB?
I've been using Gnabo v_7 version for quite a long time, and a very simple and beautiful day when I woke up my Samsung GT-N8000 was stuck on bootscreen. I wasn't able to do much so I got this "Brazil stock rom" that I found in a website, and it flashed all right, except for the detail that there is something at the screen that I haven't got a bloody clue how to remove. hahaha
And still, whenever I try to install another room, I got stuck at bootlogo and so on. I'm kinda lost here, mind a little help?
I traveled around the forum but well, I'm a little dumb so I couldn't find any proper information about, how to solve this. I would like to know if there is a way to remove this thing from the main screen, and post here the image for you guys to see it please.
I tried to post the image here to make it easier understanding, but since I got this login recently I can't =\
Thanks
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
DroidTwe4kz said:
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
Click to expand...
Click to collapse
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
vitortakeda said:
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
Click to expand...
Click to collapse
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
DroidTwe4kz said:
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
Click to expand...
Click to collapse
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
vitortakeda said:
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
Click to expand...
Click to collapse
Here is tutorial about how to install ADB and Fastboot drivers and use them. Unfortunately, I don't know how to use it to restore efs. Sorry.
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
I know more about Motorola Droid phones. This is phone is new to me. I did do a lot of research out there and mainly on XDA. I have the option to return the phone for a full refund. I would like to see if I can fix the phone before hand. I have till this weekend to send it back.
Claps1775 said:
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
Click to expand...
Click to collapse
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Droidriven said:
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yes and yes. Okay. I know with droids when I was bootloader locked and rooted. I was fine updating. There was a change on loosing root. It's all about learning. I will try to find out how to unblock my phone. Thank you for the response.
Have you came across the ota .IMG file?
I was able to power my phone off. I connected the phone to my computer, installed the software, and tried the repair part. Failed on downloading. Version on my phone is 1.102VZ.
I found more info on xda refuring to the http://4pda.ru/forum/index.php?showtopic=597313&st=3680 site. I am not able to do anything with my phone now. Cannot get it to boot in recovery or even have my pc see it. The verizon apk sees it where I can still try to repair or update. That is it. I am going to send it back for a full refund and be done with this phone. Cannot spend weeks trying to fix this right now. Thanks all for the help.
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
I was able to flash the Rom_5.1.1_3153LR_Modem_3153LR_E6782 and my phone booted up and went into the optimizing but it is in Russian. I am further than I was. Need to find out if this is changeable to English and it all works. Yes, I do know that I will not flash anything than 5.0 now since the bootloader is locked or it can be unlocked with a code. Phone is up and running. I need a 5.1.1 US now.
It is not in Russian. It is in vietnamese. But I still need a clean 5.0 full rom.
Claps1775 said:
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
Click to expand...
Click to collapse
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I will try that. I have to get it into fastboot and that can take a few tries. The firmware I have on it has no verizon apps. It is a mod by someone. I am going to try original firmware 5.1.1 firmware. Downloading right now. it is a .rar file. Making head way witch is good. I am learning for sure.
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Claps1775 said:
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Click to expand...
Click to collapse
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Claps1775 said:
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Click to expand...
Click to collapse
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Claps1775 said:
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Click to expand...
Click to collapse
When some, lose some.
For future reference, when you want to update or modify a device, try doing some research into what NOT to do or what can go wrong with that particular device and how to fix it if it does BEFORE you focus on what CAN be done on that device and before you actually do anything to the device. Cover the bases, ask questions, search for issues others might have had when they modified their device.
Remember, just because something is available for that device, doesn't mean you can use it. Things change from android version to android version and this stock firmware to that stock firmware for a device, such as whether the bootloader is locked or unlocked, among other possible differences that can turn things into a train wreck.
Android devices are all different and are not all done the same. What and how it is done on "this" device is not the same on "that" device.
Sent from my SM-S903VL using Tapatalk