Well, I was installing the M Preview when it froze and my Nexus 9 rebooted and had a screen saying the data was corrupted and I need to reset. I reset it but it never turned back on. I let it stay in the boot loop for about 15 minutes and nothing changed. loader the bootloader and now it says OS-n/a at the top. I cant connect via ADB anymore and cant flash the stock ROM. Google and HTC both said they cant help. I hope one of you can help me! ordo i just have a expensive paper weight now? (hope not!)
also, my bootloader is still unlocked but I just cant connect with ADB to flash the stock ROM.
How I solved this issue
ConceptCars_ said:
also, my bootloader is still unlocked but I just cant connect with ADB to flash the stock ROM.
Click to expand...
Click to collapse
Hi there,
I was running into the same issue today. I'm new to android so I thought I could just simply load the image-volantis-MPZ44Q.zip into a command prompt and that all would be well. Unfortunately, my N9 bricked and ended up in an endless reboot loop. I saw "google" then a few bouncing balls for a second or two and then the entire process would restart again. (note: I was trying to upgrade from 5.1.1 to M)
Here's how I fixed it
NOTE: I am typing this out from memory. Some steps may be missing. If so, I trust that the rest of the community who is more knowledgeable on this and other related topics will be able to assist.
After hours of research and numerous failed attempts, I was able to bring it back to 5.1.1 using the following method:
1. Google WUBFRESH Nexus Root Toolkit and download and Install it. (I can't post any links because I just signed up to post this message).
2. Choose your model type etc and the android build and hit apply. For me, I choose Nexus 9 (HTC Wi-Fi Tablet) and VOLANTIS-FLOUNDER: Android 5.1.1 - Build: LMY47X.
3. The toolkit should load up now. On the right side under Restore/Upgrade/Downgrade choose "soft-bricked/bootloop" and click "Flash Stock + Unroot". Note, you need to be unlocked for this step. I was already unlocked prior to my attempt at upgrading to M.
4. Plug in your N9 via USB to your computer. If it's still boot looping, wait until you see the google text, then hold the power button and the volume down button until you get either the HBOOT menu or you get an icon that shows the little android guy lying down with his door open (aka recovery mode). If you see a white screen with HBOOT, make sure at the top it says "UNLOCKED". If it says LOCKED, these steps may not work for you!
5. Use the volume buttons to select Fastboot and then press the power button to enter in it.
6. Back to your computer.
7. Press OK to get through all warning screen (read them first obviously).
8. The program will ask you for an image. At the top, choose VOLANTIS-FLOUNDER: Android 5.1.1 - Build: LMY47X from the drop down menu. Under Choice, choose Automatic download + extract. Under Settings, choose "Force Flash Mode". Press OK.
9. It will begin downloading the factory image from the google developer servers.
OPTIONAL:If the program isn't able to communicate with your device, it may be a driver issue. I used the instructions on the following site: (remove spaces when pasting into your webbrowser) theandroidsoul.com/ nexus-9-driver-adb-fastboot-mtp-installation-guide-68375/ . I had to supplement the instructions by first unplugging my device, then loading it into HBOOT, then choosing Recovery, then choosing apply update from ABD, then plugging in my device. The computer recognized it and it showed up in my device manager with a yellow exclamation mark. I right clicked, went to it's properties and then updated the driver. Then I choose Browse My Files, and choose "let me pick from a list", then I pressed have disk, navigated to where I had downloaded and extracted the usb drivers and selected android_winusb.inf. I selected the first one and continued through all the warnings by pressing next/ok. It was finally complete and the yellow exclamation mark was gone.
10. Once complete, the program may ask you again if you have backed up your files as this is a point of no return. Read the notice and press OK when you are ready to continue.
11. At this point, a command prompt will open up and it will transfer the 5.1.1 files. This took approximately 5 minutes on my end. At the end, there were some instructions that the N9 may be rebooting and that it would take 5-10 minutes. This never occurred for me. Instead, the device went back to the fastboot screen. I then selected REBOOT (the second option in yellow).
12. Finally! The device turned on. The colored balls were flying and after 5 minutes or so, the ANDROID logo came up and I was able to setup lollipop.
Hope this helps...
logikol said:
Hi there,
I was running into the same issue today. I'm new to android so I thought I could just simply load the image-volantis-MPZ44Q.zip into a command prompt and that all would be well. Unfortunately, my N9 bricked and ended up in an endless reboot loop. I saw "google" then a few bouncing balls for a second or two and then the entire process would restart again. (note: I was trying to upgrade from 5.1.1 to M)
Here's how I fixed it
NOTE: I am typing this out from memory. Some steps may be missing. If so, I trust that the rest of the community who is more knowledgeable on this and other related topics will be able to assist.
After hours of research and numerous failed attempts, I was able to bring it back to 5.1.1 using the following method:
1. Google WUBFRESH Nexus Root Toolkit and download and Install it. (I can't post any links because I just signed up to post this message).
2. Choose your model type etc and the android build and hit apply. For me, I choose Nexus 9 (HTC Wi-Fi Tablet) and VOLANTIS-FLOUNDER: Android 5.1.1 - Build: LMY47X.
3. The toolkit should load up now. On the right side under Restore/Upgrade/Downgrade choose "soft-bricked/bootloop" and click "Flash Stock + Unroot". Note, you need to be unlocked for this step. I was already unlocked prior to my attempt at upgrading to M.
4. Plug in your N9 via USB to your computer. If it's still boot looping, wait until you see the google text, then hold the power button and the volume down button until you get either the HBOOT menu or you get an icon that shows the little android guy lying down with his door open (aka recovery mode). If you see a white screen with HBOOT, make sure at the top it says "UNLOCKED". If it says LOCKED, these steps may not work for you!
5. Use the volume buttons to select Fastboot and then press the power button to enter in it.
6. Back to your computer.
7. Press OK to get through all warning screen (read them first obviously).
8. The program will ask you for an image. At the top, choose VOLANTIS-FLOUNDER: Android 5.1.1 - Build: LMY47X from the drop down menu. Under Choice, choose Automatic download + extract. Under Settings, choose "Force Flash Mode". Press OK.
9. It will begin downloading the factory image from the google developer servers.
OPTIONAL:If the program isn't able to communicate with your device, it may be a driver issue. I used the instructions on the following site: (remove spaces when pasting into your webbrowser) theandroidsoul.com/ nexus-9-driver-adb-fastboot-mtp-installation-guide-68375/ . I had to supplement the instructions by first unplugging my device, then loading it into HBOOT, then choosing Recovery, then choosing apply update from ABD, then plugging in my device. The computer recognized it and it showed up in my device manager with a yellow exclamation mark. I right clicked, went to it's properties and then updated the driver. Then I choose Browse My Files, and choose "let me pick from a list", then I pressed have disk, navigated to where I had downloaded and extracted the usb drivers and selected android_winusb.inf. I selected the first one and continued through all the warnings by pressing next/ok. It was finally complete and the yellow exclamation mark was gone.
10. Once complete, the program may ask you again if you have backed up your files as this is a point of no return. Read the notice and press OK when you are ready to continue.
11. At this point, a command prompt will open up and it will transfer the 5.1.1 files. This took approximately 5 minutes on my end. At the end, there were some instructions that the N9 may be rebooting and that it would take 5-10 minutes. This never occurred for me. Instead, the device went back to the fastboot screen. I then selected REBOOT (the second option in yellow).
12. Finally! The device turned on. The colored balls were flying and after 5 minutes or so, the ANDROID logo came up and I was able to setup lollipop.
Hope this helps...
Click to expand...
Click to collapse
Hi, ive tried this a few times now but it keeps saying:
sending 'cache' (6248 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.003s
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s
sending 'recovery' (8434 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.007s
sending 'vendor' (161111 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 5.451s
rebooting into bootloader...
OKAY [ 0.024s]
finished. total time: 0.025s
and then nothing happens. I really dont knot what to do now!
Ok so.... HOLY ****!
after trying about 25 times to do a factory reset, and it just going back into the bootloop. I tried again just after posting my last reply and it F***king worked! thanks for the help, hopefully other will find it useful!
Glad it worked out
Same Issue
so I'm running into the same issue and running the Root Toolkit. I've ran it about 6 times and I'm still hanging on Google. Did you continue running the same thing until it worked again randomly? Did you try change the Android version at any point from 5.1.1 to something earlier?
---------- Post added at 10:18 PM ---------- Previous post was at 09:26 PM ----------
Well scratch that, right after posting this, the next time it worked. Seems like the trick is to post here that it doesn't work and then it will work.
Lol
Sent from my HTC6500LVW using XDA Free mobile app
[email protected] said:
so I'm running into the same issue and running the Root Toolkit. I've ran it about 6 times and I'm still hanging on Google. Did you continue running the same thing until it worked again randomly? Did you try change the Android version at any point from 5.1.1 to something earlier?
---------- Post added at 10:18 PM ---------- Previous post was at 09:26 PM ----------
Well scratch that, right after posting this, the next time it worked. Seems like the trick is to post here that it doesn't work and then it will work.
Click to expand...
Click to collapse
Haha - glad it also worked for you.
Conceptcars, can you please rename the thread to "SOLVED" - might be easier to find for anyone else in the future who is also experiencing similar hangs
Related
Words of wisdom ... or warning!
By following this guide, you are agreeing that neither I nor anyone else apart from yourself is responsible for any damage, loss of earnings, fire, theft, the milk not being delivered or bricking your device - you are doing the modding so you are to blame if anything goes wrong!
I will credit the original authors of all the files I have included in my guide as best as I can, if I have missed you out then I do apologise.
With thanks to: kennethpenn, SamCripp, Stevendeb25, eval-, Edgan, Mossys, papy-polo, the2dcour, plus anyone that I have missed.
Note: I have linked file downloads from the guides I used when I rooted, unlocked and flashed my device. I will included a link to the thread so if the links are broken then you should look in the threads for updated links - also just let me know and I'll try to fix them.
Right on with the guide...
Rooting:
Downloads:
- Atrix drivers - Download: 32-bit | 64-bit
- Gingerbreak - Download
Instructions:
1. Install drivers
2. Run gingerbreak.exe
3. Give the phone a minute or two and then open the app drawer to find "Gingerbreak"
4. Run gingerbreak from your phone
5. Click 'root now'
6. Wait for your phone to reboot
Whayy! Your now rooted - If all went well.
Tegrapart?.. You need this to flash the correct boot.img later on.
Downloads:
Terminal emulator - Download from market
Instructions:
1. Download and run 'Terminal emulator'
2. Enter:
Code:
su
- you may be prompted to by SuperUser, press remember and then press 'Allow'
3. Now enter:
Code:
cat /proc/cmdline
4.a. That command will return quite a large string of text, scan through it untill you find something that starts something like this: 'tegrapart=mbr:'
4.b. If you see tegrapart=mbr:d00:100:800,kpanic:2100:400:800: then just remember that your device is d00
4.c. If you see tegrapart=mbr:1100:100:800,kpanic:2500:400:800: then you need to remember that your device is 1100
Unlocking the bootloader:
Downloads:
- RSD Lite 5.3.1 - Download - Thread
- Drivers - Download - Thread
- Fastboot - Download - Thread
- IHOP_Bell pudding - Download - Thread
Instructions:
a. Extract the file from IHOP_Bell into a location your will remember
b. Extract the files from Fastboot package to a location you will remember - I will use C:\fastboot\ in my example
1. Turn off you phone
2. For safety measures, take out your SIM card and microSD card
3. Boot into RSD Mode by holding volume up and the power button at the same time until "Starting RSD protocol support" is displayed on the screen
4. Run RSD Lite on your pc
5. Press the [...] box next to the box named 'Filename'
6. Locate the file from IHOP_Bell that you extracted earlier
7. Load the file
8. Plug your phone into your pc
9. RSD Lite should recognise your device and should say something like "Model: NS Flash Olympus" mine said "SE Flash Olympus" and it should also say "Connected..."
10. Press the 'Start' Button
11. Be paitient while the phone reboots as it may take a loooong time
12. Once the phone has rebooted, open a command prompt window
13. Type in CD followed by a space and then the directory where you extracted the fastboot package - I will use C:\Fastboot\ in my example so I would type
Code:
CD C:\Fastboot\
14. Turn off your phone
15. Unplug your phone from the usb port
16. Hold the volume down button and the power button until you see 'Fastboot' on the screen
17. Press volume up to select fastboot, you will see "Starting Fastboot protocol support" on screen
18. Plug your phone into the usb port
19. Then in the command prompt window, type in the following command:
Code:
fastboot oem unlock
20. You will see a warning along with a unique device ID
21. Type in the following commands but use your unique device ID in place of the '#####'
Code:
fastboot oem unlock #####
fastboot -w
fastboot reboot
22. Now wait for your device to boot, whilst booting you should see 'Unlocked' on the boot screenFlashing 2.3.4 (Orange FR):
Downloads:
Moto-fastboot - Download - Thread
OrangeFR system - Download - Thread
OrangeFR webtop - Download - Thread
(Remember your Tegrapart you found out earlier.. download the right one for your device)
d00 - Download - Thread
1100 - Download - Thread
Instructions:
a. Unzip the moto-fastboot package into a directory you will remember, again I will place mine in a directory named motofastboot in my C: drive.
b. Extract the system, webtop and the correct tegrapart boot.img and place them inside your motofastboot directory
1. Turn off your phone and unplug it from the usb port if it is connected
2. Boot into fastboot mode by holding volume down and the power button untill you see 'Fastboot' on screen.
3. When you see fastboot, press volume up.
4. Open a command prompt and CD to the directory you placed your moto-fastboot package, I would enter:
Code:
CD C:\motofastboot
5. Now enter:
Code:
moto-fastboot flash system ORFR234-system.img
6. Once complete, enter:
Code:
moto-fastboot flash webtop webtop.img
7. And finally enter either:
Code:
moto-fastboot flash boot ORFR234-tegrapart-d00100.boot.img
OR
Code:
moto-fastboot flash boot ORFR234-tegrapart-1100100.boot.img
Depending on your Tegrapart number.
8. Turn off your phone, boot it back up and you should now be rocking Orange 2.3.4 GingerBread.
briliant guide mate! could you add some kernels and roms thats working with UK's atrix
Cheers
Thanks, this is exactly what I needed in terms of clear, complete information all in one thread.
Sorry if this is a stupid question but I'm new to the Atrix and there's so much info all over the place my head is already spinning! I'm on UK T-mobile, I assume the unlocking and rooting part is still the same, but should I still flash the Orange file or would this mess up my phone? All I really want to do is root/unlock so I can flash a custom rom.
Many thanks.
eggshaped said:
Thanks, this is exactly what I needed in terms of clear, complete information all in one thread.
Sorry if this is a stupid question but I'm new to the Atrix and there's so much info all over the place my head is already spinning! I'm on UK T-mobile, I assume the unlocking and rooting part is still the same, but should I still flash the Orange file or would this mess up my phone? All I really want to do is root/unlock so I can flash a custom rom.
Many thanks.
Click to expand...
Click to collapse
No, it won't. In fact, even Orange FR and Orange UK are as different as AT&T and T-Mobile UK. Also, ALL AT&T ROMS WORK! All you need to do is to flash faux123's kernel over the top of the ROM, just to get back your RAM. Even if you don't flash the kernel, you will not brick, just have the limited RAM issue.
Finally, most of us should be on the N_01.95.00R radio. What speeds and battery life do you get out of this on Orange UK?
It seems I have been capped to 1.9mbps
kartik50 said:
No, it won't. In fact, even Orange FR and Orange UK are as different as AT&T and T-Mobile UK. Also, ALL AT&T ROMS WORK! All you need to do is to flash faux123's kernel over the top of the ROM, just to get back your RAM. Even if you don't flash the kernel, you will not brick, just have the limited RAM issue.
Finally, most of us should be on the N_01.95.00R radio. What speeds and battery life do you get out of this on Orange UK?
It seems I have been capped to 1.9mbps
Click to expand...
Click to collapse
Thanks for replying...I think I understand what you're saying.
However, I'm on T-mobile UK not Orange. I only ever use wifi for data so not sure about speed, but battery life seems to be just over a day although I've only had the phone a few days so far. Just trying to make sense of it all .
I wish there was one definitive thread on what you need to do to get the phone to a point where you can flash a custom rom. Don't get me wrong, I'm not lazy and don't mind reading up and researching, I'm just really confused at the moment about whether I need to follow the pudding thread and flash sbf files (it says to put Pudding on the phone, whatever that is) or use Gingerbreak or SuperOneClick, and how to get cwm recovery on the phone.
....more reading up is in order I guess, until it all sinks in
Anyone know why it's stuck on the boot screen with this? I even SBF'd back to stock Orange 2.2.2 before hand. I also fastboot -w it. Is there nothing you can just flash for this?
this is what i get when trying to flash???
C:\Users\kris\Desktop\motorola>fastboot flash system ORFR234-system.img
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.003s
C:\Users\kris\Desktop\motorola>moto-fastboot flash system ORFR234-system.img
'moto-fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\kris\Desktop\motorola>moto -fastboot flash system ORFR234-system.img
'moto' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\kris\Desktop\motorola>fastboot flash system ORFR234-system.img
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.002s
C:\Users\kris\Desktop\motorola>moto-fastboot
'moto-fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\kris\Desktop\motorola>fastboot flash system ORFR234-system.img
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.002s
C:\Users\kris\Desktop\motorola>moto-fastboot
'moto-fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\kris\Desktop\motorola>fastboot flash system ORFR234-system.img
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.002s
C:\Users\kris\Desktop\motorola>
cheers
ok then, the link supplied for moto-fastboot is incorrect - found in the instruction link http://forum.xda-developers.com/showthread.php?t=1138092 - the guide also needs to add to press the up arrow to transfer the images. moto-fastboot.exe is not included in the original link.
I assume the initial link is for linux.
Nope that's what I used on windows 7 x64 mate, and I didnt have to press up to transfer the images either :S
I had no problem with the moto-fastboot, but it does just get stuck on the loading screen with unlocked.
When I run Gingerbreak, nothing happens?
EDIT: Fixed.
usb debugging on and usb storage
I heard that people are reporting bluetooth problems after rooting their atrix. Can anyone confirm that their bluetooth are working after rooting here??
airheli1201 said:
I heard that people are reporting bluetooth problems after rooting their atrix. Can anyone confirm that their bluetooth are working after rooting here??
Click to expand...
Click to collapse
I didn't have any issues
another quick question. Will the data on my internal storage be somewhat erased by following these steps???
edit: found out... yes it does, yes it does. haha. lost all my application data! oh well.
Hi,
followed all the steps on unlocking the bootloader and all went well, expect now it appears stuck on rsd saying executed 100%, but 'please manually reboot power up this phone'. Oddly though the phone is already on, what should I do?
Hi ive rooted and unlocked the bootloader and was following the guide to a T...
on the part of flashing 2.3.4 ORANGE i downloaded all the relevant files and placed them the motofastboot folder. it says to then turn the phone off and boot into fast mode which i have done. and then pressed volume up and now states tarting Fastboot protocol support
I then connect the phone to the computer and started step 5. and it says its not recognised as an internal or external command....etc etc! what am i doing wrong? i tried to put cd before the command prompt and it just says system can not find the path??? but i have everything in the correct place? help plssss
Have you put renamed the motofastbootx86 or x64 to just motobootfastboot and then your commands will work. Hope that helps
Am desperate to get Gingerbread installed on my Atrix I have followed all the above steps carefully (atleast I think I have) but when I get to the stage of flashing at the cmd prompt I get:
The program can't start because adbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem.
What am I doing wrong ??? Thanks in advance
---------- Post added at 10:18 PM ---------- Previous post was at 09:53 PM ----------
Roberts56 I had that problem at 1st and founf that the motofastboot file is corrupt, I did a search and downloaded it from elsewhere and it all worked fine.
Well it did untill I got my error message above ;-(
Here is the working version with the dll files that I was missing, hope this helps.
Sorted me out in the end and I have to say it has given my Atrix a new lease of life.
Am well impressed
sorry for my english guys,
i have asus ME301T tablet, but now i can't start, only asus logo shown, then everything stop
i can't get recovery with START+VOL DOWN too
any solutions for dumb newcomer?
petr.mostyn said:
sorry for my english guys,
i have asus ME301T tablet, but now i can't start, only asus logo shown, then everything stop
i can't get recovery with START+VOL DOWN too
any solutions for dumb newcomer?
Click to expand...
Click to collapse
You're not dumb. I don't know anything about this tablet but check to see if you find solutions here.
vanessaem said:
You're not dumb. I don't know anything about this tablet but check to see if you find solutions here.
Click to expand...
Click to collapse
I agree with vanessaem.... You are not dumb at all, just a newbie. We all started out as a newbie ourselves
I just read on the forums for your device that there is a physical "Reset" button near the SD Card slot. Can you please try to stick a paperclip or pin into that hole and hold it down until the tablet reboots? I also read that these instructions may be in the manual as well.
If all else fails you can restore the tablet to defaults. I also did a quick search and came upwith the easy steps to restore it. These steps are from another forum so I will quote them since this is not my work.
I've only had this tablet a few hours, but managed to get to a point where it wouldn't boot pretty soon after rooting it. So after trying everything to get it up and running I finally managed it with ADB and fastboot, also it took from Android 4.1.1 to 4.2.1 - so here is what I did after reading various forums of problems with other Asus devices and soft-bricking other Android devices in the past - hopefully it might help someone one day.
You will need to install the Asus ADB drivers before following the steps below, if you haven't installed them you can get them here
1. Download and install Lightweight ADB and fastboot installer here from XDA
2. Create a folder called 'Fastboot' on your C: drive (it can actually be called anything but the prompts below refer to a folder with this name)
3. Download the CarePackage.zip file here and unzip the contents to C:\Fastboot, there are 4 files
4. Download your chosen firmware from the Asus web site - extract the zip file to reveal another zip, extract the second zip file, copy the 'blob' file to the Fastboot folder, there will now be 5 files in your fastboot folder
5. Reboot tablet, holding volume down, select the USB option (3rd icon) using volume down to cycle through icons and volume up to select and connect it to your PC using the USB cable
5. Run the Lightweight ADB and fastboot installer which will open the command line, enter the following commands;
c:\Fastboot
fastboot devices
fastboot -i 0x0B05 flash system blob
6. The following will now be displayed in the command line screen;
sending 'system' <1062567 KB> (the actual size will vary depending on the firmware selected) Also a blue bar will appear on your tablet screen showing the progress. It takes around 3-4 minutes to send the system files.
writing 'system' will then be displayed, this will take a further 3-4 minutes.
Once the files have have been sent and written the command screen will display something similar to;
finished. total time: 444.226s
7. Unplug the tablet and reboot it using the power button, you'll have a fresh install, all data, root etc will be lost.
For anyone who is struggling to recover their tablet or just actually update it I hope this helps
Click to expand...
Click to collapse
timmytim said:
I agree with vanessaem.... You are not dumb at all, just a newbie. We all started out as a newbie ourselves
I just read on the forums for your device that there is a physical "Reset" button near the SD Card slot. Can you please try to stick a paperclip or pin into that hole and hold it down until the tablet reboots? I also read that these instructions may be in the manual as well.
If all else fails you can restore the tablet to defaults. I also did a quick search and came upwith the easy steps to restore it. These steps are from another forum so I will quote them since this is not my work.
Click to expand...
Click to collapse
thanks for all advices, but i think this is a SERIOUS problem ..
i can't do fastboot, can't connect PC-ANDROID or vice versa
my android device has now only two modes / off or stoned when asus logo appears
RECOVERY twrp non reachable!
Okay guys, I think my phone has a soft brick (no boot logos), so I'm trying to do some restoration... but I'm not having much success.
So, I found a solution in XDA (/showthread.php?t=825173&page=3) saying that I should plug my phone in without battery, SD nor chip and disable the "LG Modem" on my Device Manager. Afterwards, start KDZ Updater and configure it to CS_EMERGENCY. Then I should install a 2.1 French firmware and as soon as KDZ finishes I'd plug off my phone, plug it back in and start it in DL mode again, this time flashing a file named "OUT.kdz", which gives back the boot logos.
Problem: KDZ Updater hangs as soon as I press "Start". It simply freezes when it's in CS_EMERGENCY. I have no solution to this whatsoever, and I also have another thread with previous problems I ran into (Soft-Bricked LG GT540 Optimus).
These are the best forums I've found for any kind of phone, so I'm positive I'll get the help I need, even if I might need to wait some time. Kudos to the admins and every member for taking part of such a great community!
Ebony Dubois said:
Okay guys, I think my phone has a soft brick (no boot logos), so I'm trying to do some restoration... but I'm not having much success.
So, I found a solution in XDA (/showthread.php?t=825173&page=3) saying that I should plug my phone in without battery, SD nor chip and disable the "LG Modem" on my Device Manager. Afterwards, start KDZ Updater and configure it to CS_EMERGENCY. Then I should install a 2.1 French firmware and as soon as KDZ finishes I'd plug off my phone, plug it back in and start it in DL mode again, this time flashing a file named "OUT.kdz", which gives back the boot logos.
Problem: KDZ Updater hangs as soon as I press "Start". It simply freezes when it's in CS_EMERGENCY. I have no solution to this whatsoever, and I also have another thread with previous problems I ran into (Soft-Bricked LG GT540 Optimus).
These are the best forums I've found for any kind of phone, so I'm positive I'll get the help I need, even if I might need to wait some time. Kudos to the admins and every member for taking part of such a great community!
Click to expand...
Click to collapse
I've fixed all my issues! I'll paste what I said in another thread. Yay for one-full-year struggles!
Just wanted to leave my 2 cents here, I've been trying to do my best since around august 2014, no success. 2 days ago I retried this, and I DID IT! I will tell everyone what I did very shortly:
My problem that I solved: I can boot, device works like a charm. But: no boot logos, no recovery.
My solution for TL;DR: UNINSTALL ALL DRIVERS FROM DEVICE MANAGER 1ST, then reinstall. After that, flash a fastboot ROM and use it to WIPE ALL THE DATA IN YOUR PHONE! THIS was what I needed and was never explained: you had to WIPE the old data in order to get the boot screens back.
IN THIS ORDER (THANK YOU to those people from previous replies, gathering all your info was of great value):
Uninstall all of your phone drivers from your PC!!! This is what made most of my headaches go away, just use Device Manager and uninstall anything from LGE. After that, plug in your device in your USB ports (always BACK ports, not front ports, important). It should detect all drivers and download them.
IF it fails (it generally does with LGE USB Modem), you can go to Device Manager > Unknown Device (the one that wasn't recognized) > Right Click and Update > Choose 2nd option, then choose "choose from a list of local controllers" (or whatever the button says). After that, scroll down to LG Electronics, Inc. and install what didn't install.
I also found these drivers, but I did not test them: http://www.mediafire.com/download/p693hcz6kkouh19/USB_Driver_LG_GT540.zip
Huzzah!
Now you're set to begin:
FIRST thing you wanna do is a factory reset, this is something I'd forgotten with time, don't make the same mistake as I did. You can do it by turning your phone on and pressing Volume +/- & Home & Quick Search buttons all together for 5 seconds (it works, be patient and wait for it, even if you open the camera or any other stuff).
Download this Google SDK Tools (unzip and put the folder in C:\ drive) and this Fastboot drivers for GT540 (unzip and put the files inside the folder in C:\android-sdk).
Skip this next line if you know your ROM has fastboot.
Now, if you don't have a ROM with fastboot, I recommend you use either European Open+Fastboot or V20C Orange France Fastboot ROM.
Click to expand...
Click to collapse
Since you have Fastboot enabled, now all you need to do is turn off your device (all this with its battery on it, no weird things) and hold the Camera button before turning it back on. This should take you either to a black screen, or simply to no display, like me. Either one will work anyways.
Now press the Windows key > Type cmd and open it with Right Click > Run as Administrator.
In it, type all this, command by command (you can paste by right clicking):
cd C:\android-sdk
fastboot -w
fastboot erase boot
fastboot erase system
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
And now it's go time! Do what everyone else says in here: Take out your phone's battery, SD and SIM cards, fire KDZ Updater up as Administrator (If your KDZ freezes, then it's either faulty or you did not install msxml, look for a good KDZ that comes with that file and delete your current one), choose CS_Emergency PhoneMode and:
1-Plug your phone while holding the volume DOWN button (don't worry! My phone didn't show "Download Mode" either, if you hear the Windows "Somethingpluggedin" Bump noise, it's ok).
2-Flash French V20A
3-Unplug your phone once KDZ says "==FINISHED==".
4-Plug it once again, holding the volume DOWN button.
5-Flash out.kdz (remember! it's CS_Emergency).
Click to expand...
Click to collapse
THANK YOU XDA!
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Download mfastboot and redownload the recovery img
hetor99 said:
Download mfastboot and redownload the recovery img
Click to expand...
Click to collapse
Thanks.
Decided to install it on my desktop. While trying various files, my laptop accidentally got hit with Chromium virus. It looked like all required files were there, but kept having problems with a couple of those sdk files (tools/platform tools).
I'm still getting the following error:
( bootloader) has-slot :recovery: not found
And once again the Android SDK Tools and Android SKD Platform-tools that are under Tools (preview channel) are unchecked. Not sure if they are needed.
Follow the instructions of how to install on the general section
hetor99 said:
Follow the instructions of how to install on the general section
Click to expand...
Click to collapse
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
L8Show said:
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
Click to expand...
Click to collapse
How to Install TWRP Recovery and Root MOTO E
https://www.youtube.com/watch?v=9Jh-O2LGL3Y
OK, it is done.
Took a couple days with several hours of clicking, and checking settings, and reading and researching, and watching videos, and downloading, and installing/uninstalling, and restarting, but it's now rooted! Way too much time wasted even though it was raining and the gf and I were just watching movies for a lot of it. She kept asking me why I'd waste so much time and remind me I had a perfectly fine iphone nearby. Today I finally got to the point where I had given up. I figured something was screwed up with the phone after that reset on my computer.
Some highlights that may or may not be helpful for the next moto e rooter:
USB debugging was somehow switched to off a few times after I turned it on. Might have been after resetting phone, but who knows exactly.
I set screen to stay while connected via USB.
I removed all the apps I could and took out the sd card.
Kingoroot stuck at 66% many, many times, and then phone would restart. Research showed it may be accessing the wrong ADB instance or something. So I uninstalled SDK, fastboot, Minimal, etc. Anywhere it could have been hiding. Even did a system restore to last week the day I reinstalled windows. Didn't help one bit. Which is to also say... there are a half dozen or more legit options. Try different ones if you are relatively confident you followed directions the 1st 10 times.
Ministro didn't have moto e in their data base.
Finally back to XDA after checking a dozen videos (I have to admit I was completely dumbfounded and was mad at the whole process). I found XDA Kingroot and right away it worked, but it needed permission to allow apps that were not certified or some thing. I can see how people would think this is so easy. If I had started with this, I'd never have had to ask for help here. Btw, was this my problem all along? Did I miss that in the instructions or was it something else possibly? I don't remember if I did that before since it was 3 days ago.
So far I am thoroughly impressed with the this moto e. I paid $40 for it on a whim and now that I can remove a bunch of bloatware and customize it a bit, I think it may be a good gateway into android devices.
Thanks for looking and all your suggestions.
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
faheyd said:
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
Click to expand...
Click to collapse
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
L8Show said:
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
Click to expand...
Click to collapse
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
-z3r0- said:
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
Click to expand...
Click to collapse
Thanks for that information. I thought I saw adb devices command working in fastboot mode in one of the videos so I thought that was the problem. I thought adb needed to root the phone.
In order of what I've done with the phone so far:
Sent/got codes and unlocked moto e.
Turned on developer options and USB debugging.
Was then unable to get TWRP or the other cw something to work using the command fastboot flash recovery (file name) or fastboot boot... commands.
Gave up and installed Kingroot and everything worked fine.
Decided to try to install TWRP and superSU since kingroot had worked. I read that the phone needed to be flashed back to stock to do this and watched/read a couple of guides. http://forum.xda-developers.com/showthread.php?t=2759495
I used the following named file:
SURNIA_ACG_LTE_5.1_LPI23.29-30_cid9_subsidy-DEFAULT_CFC
The phone was changed back, but data doesn't work. I can't access wifi because as soon as I switch it on, it switches back off. 4G, etc is not working either. So after trying to figure that out I decided to just proceed and put TWRP/superSU on the phone.
I powered off the phone. Powered into fastboot mode connected the phone to my computer.
I opened Minimal fastboot folder and shift/right click to bring up the command prompt.
In the command promt i typed fastboot devices and it shows my phone.
I then type fastboot flash recovery (file name or renamed to recovery or renamed to TWRP or I click the actual file and drag it to the command prompt) and then hit enter.
It says it's doing stuff in so many seconds, but after nothing happens. The phone doesn't reset like some of the videos. If I reset it, it powers on, but not into the TWRP screen.
After that I did more reading and found out that adb doesn't always play nice with windows 8.1 and that you might need to force other drivers to make it work right. I did this next and was going to try all the available options from universal naked driver later, but there were no motorola drivers.
Then I came here and learned something new. ADB devices command doesn't work when the phone is in fastboot mode so that has no effect on installing twrp...
Right now I am considering trying to install the other stock files I have access to:
SURNIA_ACG_LTE_5.1_LPI23.29-20_cid9_subsidy-DEFAULT_CFC (20 instead of 30).
After that I am out of ideas if it's not the adb problem. Might kingroot again and go from there.
Ok after researching, it seems that LTE file may not work on sprint and there was success using the boost file from
http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
(2 hour dl make that 5+ lol)
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'll try that next to get the wifi working and then figure out why it won't root.
Thx!
L8Show said:
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Click to expand...
Click to collapse
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
rakeshwipr said:
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
Click to expand...
Click to collapse
and open the command prompt with admin rights
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
d
Thanks! The devices shows up when on as ADB and in fastboot too. I had to take a break when the kernel download took 8 hours, but I think I got the file that will work to fix the wifi issue. I can't mess with it til I get home tomorrow, but I will read and follow all advice.
For the previous poster, I did do the admin rights and did rename TWRP file to recovery... I aslo tried many other combinations, but will keep it in mind for all further attempts.
Appreciate the help so far. I almost left it with the kingroot, but it was bugging me that I couldn't get it to go. Hopefully I'll have good new tomorrow.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
Device shows up in both instances.
It's stock now and the wifi works. Flashed it back to stock by following Mdkcheatz guide here:
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'm stuck where I was when I first started this thread. I've set my account up as administrator. Developer is enabled and so is USB debugging. I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
I confirmed the connection:
fastboot devices
I try to flash it with the:
fastboot flash recovery recovery.img
It says:
target reported max download size of 268435456 bytes
sending 'recovery' (6928 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.359s]
finished total time: 0.578s
C: |Program Files (x86)\Minial ADB and Fastboot>
I'm running windows 8.1 (64 bit). I read that some people had had problems with windows 8. Kingroot worked through the app store. It has been flashed with various stock kernels and that usually takes a few minutes so I don't think it's doing much in half a second. I'll research a bit more, but I think it just a bad combination of this version phone and windows 8.1.
I started the phone after this last attempt. Are there any files in internal storage that I should look for?
L8Show said:
I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
Click to expand...
Click to collapse
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
-z3r0- said:
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
Click to expand...
Click to collapse
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
L8Show said:
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
Click to expand...
Click to collapse
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
-z3r0- said:
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
I am on v2.65. Should I use this version? I checked root and it's rooted, but I needed to use no bloat app (instead of free titanium) to remove some apps. Is that normal? I thought once rooted and set up, I would have complete control. Some apps seem very invasive so I haven't grabbed many yet. I have some questions about apps, etc., but will probably research and ask in another forum if needed.
Thx again for all the help and pointing out my mistake.
Hello everyone,
I ran into this problem while trying to solve another.
The current state of my phone (h850):
On booting, I receive this message: "Your device is corrupt. It cannot be trusted and will not boot."
Fastboot is still accessible.
Download mode is not: holding the volume up button and connecting a USB cable presents me with the above message.
I can still access the "Factory data reset" dialog, but after selecting "Yes" twice it takes me to the above message.
[edit]:
fastboot getvar unlocked
unlocked: no
I tried unlocking the phone again using fastboot flash unlock:
Code:
fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.040s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
... so that sucks.
Any way to recover from this?
How the hell did I get here?
I had TWRP and LineageOS 14.1 installed. Lineage released a new update which I tried to install from the OTA-Update list. After rebooting, I ended up in TWRP, which did... nothing. So I tried rebooting, only to end up in TWRP again; there appeared to be no escape. Finally, I came across an answer on reddit (I'm not allowed to post outside links... it's on the LineageOS subreddit, post ID is 61nxs6):
for g5 the command are these:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
Click to expand...
Click to collapse
I tried those, and that's how I got here.
Try reflashing twrp.img in fast boot (see Autoprime's AIO post for instructions) then try booting into twrp - then at least you can wipe and flash a new stock/custom rom!
Best of luck!
megatron_lives said:
Try reflashing twrp.img in fast boot (see Autoprime's AIO post for instructions) then try booting into twrp - then at least you can wipe and flash a new stock/custom rom!
Best of luck!
Click to expand...
Click to collapse
Thanks for the reply!
Reflashing TWRP doesn't work as the device is somehow locked again:
Code:
fastboot flash recovery twrp-3.1.1-0-h850.img
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.471s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.490s
Unlocking fails as mentioned in my fist post.
did you try flashing stock kdz file with lgup? if it boots you can later try unlocking.
ozkaya said:
did you try flashing stock kdz file with lgup? if it boots you can later try unlocking.
Click to expand...
Click to collapse
It's my understanding that LGUP requires "download mode" to be active (which I cannot access, see first post). In any event, any mode that I can still reach (error message, factory reset, fastboot) does not cause the device to be visible to LGUP, even using Uppercut.
gqo said:
It's my understanding that LGUP requires "download mode" to be active (which I cannot access, see first post). In any event, any mode that I can still reach (error message, factory reset, fastboot) does not cause the device to be visible to LGUP, even using Uppercut.
Click to expand...
Click to collapse
good point. how about if you try fastboot flash recovery twrp.img or if it fails flash stockrecovery.img?
---------- Post added at 06:11 PM ---------- Previous post was at 06:08 PM ----------
gqo said:
It's my understanding that LGUP requires "download mode" to be active (which I cannot access, see first post). In any event, any mode that I can still reach (error message, factory reset, fastboot) does not cause the device to be visible to LGUP, even using Uppercut.
Click to expand...
Click to collapse
if flashing recoveries fail, try fastboot flash bootloader stockbootloader.img (you can find these images from stock zip format in the forum)
Thanks everyone for the help! Just to be thorough, I tried entering download mode for what felt like the 42nd time, and whaddaya know, it worked! So I'm currently in the process of returning to the point I was on before I tried that ill-fated update of LineageOS. Thanks again everyone!
gqo said:
Thanks everyone for the help! Just to be thorough, I tried entering download mode for what felt like the 42nd time, and whaddaya know, it worked! So I'm currently in the process of returning to the point I was on before I tried that ill-fated update of LineageOS. Thanks again everyone!
Click to expand...
Click to collapse
what exactly have you done? i have the same problem
trinity_user said:
what exactly have you done? i have the same problem
Click to expand...
Click to collapse
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
did u lost ur imei?
Zer0_rulz said:
did u lost ur imei?
Click to expand...
Click to collapse
Not sure what you mean. If you're wondering whether I lost that piece of information: no, it's printed on a sticker on the back of my phone. In general there's usually a sticker with your phone's IMEI somewhere on the packaging or, like in my case, on the device itself.
gqo said:
Hello everyone,
I ran into this problem while trying to solve another.
The current state of my phone (h850):
On booting, I receive this message: "Your device is corrupt. It cannot be trusted and will not boot."
Fastboot is still accessible.
Download mode is not: holding the volume up button and connecting a USB cable presents me with the above message.
I can still access the "Factory data reset" dialog, but after selecting "Yes" twice it takes me to the above message.
[edit]:
fastboot getvar unlocked
unlocked: no
I tried unlocking the phone again using fastboot flash unlock:
Code:
fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.040s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
... so that sucks.
Any way to recover from this?
How the hell did I get here?
I had TWRP and LineageOS 14.1 installed. Lineage released a new update which I tried to install from the OTA-Update list. After rebooting, I ended up in TWRP, which did... nothing. So I tried rebooting, only to end up in TWRP again; there appeared to be no escape. Finally, I came across an answer on reddit (I'm not allowed to post outside links... it's on the LineageOS subreddit, post ID is 61nxs6):
I tried those, and that's how I got here.
Click to expand...
Click to collapse
Wow... It's uncanny how close this is to the my own situation, except that in my case it's a G6 (US997).
gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
Again I did the same, bar the tea, but unfortunately my tale does not end quite so happily... Not yet at least. I can "upgrade" with literally no problems using LGUP and one of the few G6 KDZs available, but when it's time reboot my phone always boots into the fastboot for bootloader unlock mode. I can use fastboot commands but my bootloader relocked at some point and I'm still not able to unlock it again. No matter what I do my phone always boots to fastboot... Except when I do the recovery key combination and press "Yes" twice, in this case there's a brief "erasing" animation and then I'm back to fastboot.
I realize I'm using a different device, but would anyone happen to have any thoughts on this? This is my first time using a non-Nexus LG and I must admit I'm struggling a bit to get out of this mess. The recovery and fastboot modes also look quite bare to me, but I might just be using the wrong.
Cheers!
gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
Thank you for your detailed guide, but it didnt work for me yet. I tried maybe 100 times. Everytime the same Message "Your device is corrupted".
You are a life saver
Thank you for detailed tutorial.
My H850, which I managed to almost dead brick, like yours (of course from the same source - reddit ) after few minutes with uppercut + lgup ressurected with all the files and apps inside
So, after that I'm running through factory reset now and trying to unlock once again.
Thank you
Have the same problem but......
gqo said:
Hello everyone,
I ran into this problem while trying to solve another.
The current state of my phone (h850):
On booting, I receive this message: "Your device is corrupt. It cannot be trusted and will not boot."
Fastboot is still accessible.
Download mode is not: holding the volume up button and connecting a USB cable presents me with the above message.
I can still access the "Factory data reset" dialog, but after selecting "Yes" twice it takes me to the above message.
[edit]:
fastboot getvar unlocked
unlocked: no
I tried unlocking the phone again using fastboot flash unlock:
Code:
fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.040s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
... so that sucks.
Any way to recover from this?
How the hell did I get here?
I had TWRP and LineageOS 14.1 installed. Lineage released a new update which I tried to install from the OTA-Update list. After rebooting, I ended up in TWRP, which did... nothing. So I tried rebooting, only to end up in TWRP again; there appeared to be no escape. Finally, I came across an answer on reddit (I'm not allowed to post outside links... it's on the LineageOS subreddit, post ID is 61nxs6):
I tried those, and that's how I got here.
Click to expand...
Click to collapse
i have the same problem but i can still use the phone, how can i delete this error?
the boot loader it s not working.......PLEASE HEEEELP
gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
I tried this, but my pc (and so LGUP) doesn't recognize my lg g5 (drivers are installed)... I don't know what to do.. please help me!!!
Use uppercut
Hello. I have the same problem. I was on LOS 15.1, then i deviced to go back on stock. I relocked the bootloader and i have this messege. When i go to download mode, lgup recognize the phone, but after 10 seconds the phone reboot and go to that screen again. Any suggestions?
volen said:
You are a life saver
Thank you for detailed tutorial.
My H850, which I managed to almost dead brick, like yours (of course from the same source - reddit ) after few minutes with uppercut + lgup ressurected with all the files and apps inside
So, after that I'm running through factory reset now and trying to unlock once again.
Thank you
Click to expand...
Click to collapse
I've got this problem also, thanks to those lines put into 'terminal'.
I can get into download mode easily, however by the time I then open Uppercut and try doing anything the phone reboots itself back into the 'corrupt' screen and keeps looping on that.
mgolder said:
I've got this problem also, thanks to those lines put into 'terminal'.
I can get into download mode easily, however by the time I then open Uppercut and try doing anything the phone reboots itself back into the 'corrupt' screen and keeps looping on that.
Click to expand...
Click to collapse
Maybe unlock.bin is corrupted, try ask LG to resend the file.