Accidentally hit the OTA lollipop update and phone would not get out of twrp. Have been able to download TOT and KDZ files and back and forth from KitKat to Lollipop. I can even download using the LG utility to update. The problem is that after the phone boots it restarts. I have no chance of pushing TWRP or any image for that matter. I can do hard reset I can put it in download mode but flashing does not fix the issue. I've spent all day looking on the web and all related forums to no avail. Any suggestions?
T-Mobile LG G3 Lollipop 5.0.1 stck firmware
vicvega said:
Accidentally hit the OTA lollipop update and phone would not get out of twrp. Have been able to download TOT and KDZ files and back and forth from KitKat to Lollipop. I can even download using the LG utility to update. The problem is that after the phone boots it restarts. I have no chance of pushing TWRP or any image for that matter. I can do hard reset I can put it in download mode but flashing does not fix the issue. I've spent all day looking on the web and all related forums to no avail. Any suggestions?
T-Mobile LG G3 Lollipop 5.0.1 stck firmware
Click to expand...
Click to collapse
ADB push? http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
That's a great suggestion but did I mention I no longer have twrp installed on the phone?
vicvega said:
That's a great suggestion but did I mention I no longer have twrp installed on the phone?
Click to expand...
Click to collapse
You said it wouldn't get out of twrp mode after update. You most likely need to clear fota and misc because they are corrupted since you took an OTA with a custom recovery. You do not need TWRP to do this. You can use adb.
Ok, so if I put the phone in download mode then adb "should" detect it? With root gone this should do the trick? I ask because I have put the phone in download mode but adb won't communicate with it and the phone doesn't give me enough time to put it in debugger mode. Thanks for your time and advice. I don't wish to buy a new phone when this isn't even a year old.
vicvega said:
Ok, so if I put the phone in download mode then adb "should" detect it? With root gone this should do the trick? I ask because I have put the phone in download mode but adb won't communicate with it and the phone doesn't give me enough time to put it in debugger mode. Thanks for your time and advice. I don't wish to buy a new phone when this isn't even a year old.
Click to expand...
Click to collapse
You need to use the adb commands listed in the link, not the zip. You do not need to be in download mode. You'll probably have to connect and reconnect multiple times because of boot issue to get adb to recognize and lock on it. Try first with pulling the battery also
"Code: adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=256 count=1 conv=notrunc
reboot"
It is also possible to push a zip and install. I recommend reading up on adb if you are unfamiliar http://forum.xda-developers.com/showthread.php?t=2266638.
I will say it sounds soft bricked and is recoverable. Perhaps, someone with more expertise than I can help
maybe you can take the external sd out transfer the zip-- maybe name it update zip-- put sd back in use download mode. But honestly, I haven't used a stock recovery since htc g2
Thanks for all your efforts but the two issues I'm having is the phone doesn't stay on long enough and the mtp drivers are not load applying. Tried on four computers with eight different cables. I give up. I can connect in download mode but then adb says dd is not a recognized command. I guess this is why other threads with this issue are still open.
Update. Sent the unit to LG and they were able to fix the issue and also replaced the usb port which sometimes wouldn't charge unless a new cable was used. Again, thanks for all the help. This should hold me off until I can get my hands on the G4.
Related
Sorry, I'm relatively new to rooting and I looked through the threads and found similar problems, but none that seem to exactly match mine.
I have a rooted VS985 that I was trying to flash with the AndroidNow HD 6.1 ROM using TWRP and I guess the flash tool crashed. It was stuck on a black screen for an hour or two so I hard reset it and after that, the phone will only flash the LG logo for a second before the screen turns off and the indicator light alternates flashing red and blue. As far as I can tell, the computer does not detect it when it is in this mode (seems similar to the secure boot issue that some people have been having). I cannot enter download mode (the LG logo flashes on and the indicator light flashes blue once and then both turn off) but I can still boot into TWRP Recovery. When I try to boot into download mode, even while the screen is off, my computer detects the phone as QHSUSB_BULK. Also, when in recovery mode, my computer can detect the phone as a G3 and I can access it with adb tools but I don't know where to go from here. I have tried using the LGFlashTool but I can't seem to access the phone because it will not enter download mode and I've tried reflashing AndroidNow HW 6.1. The flash completes and says it is successful, but the phone still will not boot properly.
Luckily, I got the phone a few days ago from Costco, so there is a good chance I can still return it, but I would like to fix it if I can.
Any help would be greatly appreciated.
pyroguy3590 said:
Sorry, I'm relatively new to rooting and I looked through the threads and found similar problems, but none that seem to exactly match mine.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You said you have adb working.
Did you make a backup of your stock download mode at anypoint of time? (Iaf.img)
I guess it can be pushed back using adb, but am not very sure. Even if not, maybe you can take the stock Iaf.img from someone else and try pushing it via adb using this command:
Code:
dd if=/storage/external_SD/stock-laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
Then you can boot into the download mode using the command:
Code:
fastboot boot stock-laf.img
It doesn't look like I have the stock laf.img backed up. I'll try to get it from someone. Thanks, I'll let you know what happens when I get it.
I need this tooi fi h
had a nandroid backup but accidentatlly delted it when i formatted my internal memory now im stuck on liquidsmooth custom rom cant get into download mode so kdz/tot will not work for me... I have twrp installed and that works though. I need to use adb to flash those files or have a stock vs985 that i can flash with twrp... I have vs985 i like the liquid smooth room but the camera and video camera doesnt work as good as it did with stock...
Any help or ideas would bee aprraciedated ive tried everything
just Switch off your mobile.. and put out bettery from it,
And In Pc Download Any Official Tot rom For Your lg g3 vs985 than Open LG Flash Tool 2014
download it from Xdadevelopers any version
Than Put back your bettery In Your Mobile And dont press any button Just put your usb in,your pc and Same time Put Pin in your mobile and press Volume up button And Your Mobile goes in Download Mod Automaticly..
Than Just Flash any Tot Software in It..
Its Working Like Charm,,
Try it It is Working for me Also
Hey all, Before I start, ive searched and search and have not been able to find the solution.
I have my LS980 which was rooted. I learned about the zvg upgrade and tot back to stock zve.
Then I accepted the OTA to zvg and all was good so for I was at total stock ZVG.
I searched how to root and I tried the one click root method but something in the script would pause at the waiting for device...
so, I uninstalled all my LG drivers and root programs, Rebooted my computer and then made sure my phone was enabled debugging.
I then ran the LG root script v1.2, the program ran through without any problems. I entered download when it prompted me to and the phone was immediately detected and the su script continued. I left everything connected until it said don! then the control c and n to reboot.
This is the problem now, when the phone reboots it stays at the LG splash screen and the led alternates colors slowly. I cant get it into download mode but I'm able to boot back into stock recovery. I've tried to reboot system repeatedly for 4 or 5 times in a row (hoping something will change and let it boot), but nothing the longest I've left it at the LG screen is 45 minutes. I'm getting frustrated with this, Im really want to get this update rooted. So far the only way I can get the phone to boot is to side load the zvg ota update from stock recovery. can anyone tell me what I need to do to get past my last step and get rooted boot stock zvg?
thanks in advance. I usually can find all the information I need on xda but im stuck on this one.
Is zvg actually taking? I know with the GUI version. It would progress to 90%get stuck and never proceed. Them I would wait 5 minutes. Disconnect and reboot phone. I would have root
I can't tell.. The script run all the way through but i have yet been able to boot. It keeps hanging at the lg screen. Like i said ive waited up to 45 minutes on this state then from the screen I'll just adb to recovery and side load stock zvg update. To get the phone to boot but no root.
When the phone boots back up do you verify you are on zvg. Have you tried re-installing 1 click root for windows. Just in case
Yes I'mback on zvg, because since i can't get the phone to boot i have to adb to stock recovery and sideload the zvgupdate.zip. and then reboot I'm still on stock unrooted zvg.
jcsheriff said:
Yes I'mback on zvg, because since i can't get the phone to boot i have to adb to stock recovery and sideload the zvgupdate.zip. and then reboot I'm still on stock unrooted zvg.
Click to expand...
Click to collapse
Are you able to use the 1.3 version.
The problem i had with 1.3 was that it would hang after waiting for device.. So fast is why i went with 1.2.
I'll be home in a little bit and try the 1.3 Again, because i still had the problem when i switched to 1.2.. Until i deleted and reinstalled all drivers and root programs. I'll Report back
jcsheriff said:
The problem i had with 1.3 was that it would hang after waiting for device.. So fast is why i went with 1.2.
I'll be home in a little bit and try the 1.3 Again, because i still had the problem when i switched to 1.2.. Until i deleted and reinstalled all drivers and root programs. I'll Report back
Click to expand...
Click to collapse
From phone on, with USB debugging on. It should show an authorization key. Select always and OK. It will copy files over and day rebooting to download mode. That will fail. Unplug phone. Shut off. Hold volume up connect phone. The rest will go to 90%. Wait 5 minutes. Reboot phone to system.
I appreciate your advise.. I just deleted and reinstalled the lg drivers again and then ran v1.3. I got the same result..out loads the files then fails at reboot. I discover the phone and reboot to download mode then reconnect. Then i wait and wait..i hear the computer recognize the device but i continue to wait 20 minutes and nothing. I tried it several times with the same result. I then reinstalled the lg drivers uninstalled v1.3 and executed 1.2 when prompted to put device in download mode the device was connected/recognized after about 10 minutes out shows all the files installed and expanded then instructs me how too exit then reboot. I disconnect reboot and waited another 30 minutes.. Still nothing..so once again i adb to stock recovery then sideload the zvg update. Then the phone boots but still no root.
jcsheriff said:
I appreciate your advise.. I just deleted and reinstalled the lg drivers again and then ran v1.3. I got the same result..out loads the files then fails at reboot. I discover the phone and reboot to download mode then reconnect. Then i wait and wait..i hear the computer recognize the device but i continue to wait 20 minutes and nothing. I tried it several times with the same result. I then reinstalled the lg drivers uninstalled v1.3 and executed 1.2 when prompted to put device in download mode the device was connected/recognized after about 10 minutes out shows all the files installed and expanded then instructs me how too exit then reboot. I disconnect reboot and waited another 30 minutes.. Still nothing..so once again i adb to stock recovery then sideload the zvg update. Then the phone boots but still no root.
Click to expand...
Click to collapse
Question, when you connect in download mode and it just sits there. Go to device manager and check com port. Maybe it is connecting to the wrong port.
I think mine originally connect to port 41, when it should be 3.
I've verify the port assignment and I've tried port 3 port 4 and port 41...but the scripts always find the device and identify the port as Whatvi have assigned it to. I've even tied several other computer some running win 7 and others running win 8.1
I just read someone else's post that they were having problems but fixed with newer lg drivers, that his were old.
I noticed I've found a few variations of the driver. Any idea of link to the most current one?
finally rooted
Tekone said:
Maybe you should try this method. Restore to ZVE and rootz it with Lg one click v1.2. Once you confirmed it's rooted, then adb sideload on stock recovery to upgrade to ZVG. When you upgraded to zvg, try the Lg one click root v1.2 again Usually, that Lg One click root v1.2 will stuck on and take awhile, but it did it's job. Also to change the port number after used the LgFlashtool. Alot time, the port 41 don't work with Lg one click root.
Click to expand...
Click to collapse
This worked flawlessly for me. However once i rerooted after sideload. When the script ask you to put the phone inn download mode.. I saw the su script push but the machine appeared to stop working. I left it connected and waited 25 minutes to make sure all was good. Then i pressed and power button and held it down until the phone reset. The script showed complete and the phone booted all the way through. It did take about 10 minutes to boot, then super user was installed and i was rooted.
Hello.
The other night I applied 3 software updates to Android and ended up with an unusable phone. The updates (I assume) were like this: http://forum.xda-developers.com/tmobile-htc-one-m8/help/3-software-updates-t3268014
After the phone rebooted a couple times, it got stuck at the white HTC logo screen (I ended up falling asleep and the phone was like the after waking up, so stuck for about 6 hours) and wouldn't respond to just holding the power button. I had to hold power + vol up to get it to restart. After restarting it now boots to a black screen. It is possible to get to HBOOT and TWRP but I can't get adb to recognize it anymore so I'm not sure how to go about getting fixes on the phone.
The phone was running a custom recovery (clockwork recovery) and rooted. I then tried to get it back to stock to apply the Android 5.0 RUU and then used TWRP without flashing the recovery to root the phone again. My guess is that something about that process might have messed with something that one of the software updates was updating.
So, I have two questions:
1. Is it possible to recover files (pictures, for exampl) off the internal sd? Like I said, I cannot get adb (or windows) to recognize the phone, though it does show in the windows device manager.
2. If it's not possible to get recover those files, how can I get the phone usable at all?
Can you get it into the boot loader?
Yes, luckily I can get to the bootloader.
hatbocs said:
Yes, luckily I can get to the bootloader.
Click to expand...
Click to collapse
If so once in the bootloader can you use something like:
fastboot boot twrp-2.8.7.0.img
to boot into twrp? (note twrp-2.8.7.0.img is the filename of the twrp image that I saved it as, yours might be different)
If you can boot into twrp then you can install a rom/backup. also you could use, I think, something like "fastboot flash recovery twrp-2.8.7.0.img" as well.
-brad
I'm at work so I can't test this again to make 100% sure but if fastboot works like ADB then my phone doesn't show.
I do currently have TWRP installed however windows does not see the phone.
So if twrp works, you should be able to use that to connect to your pc. If not go and buy an OTG usb drive. Copy a Rom onto it, and then connect it to your phone. One time I messed my phone up and I used this method.
Worth a try. I'm in the middle of moving and that box of stuff isn't in this house. So I'll have to wait to report back. Thanks for the help so far.
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
yakub234go said:
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
Click to expand...
Click to collapse
Thanks for the response. I've tried this a dozen times, but unfortunately (this is going to sound weird) since it's not completely bricked it is only detected as Moorefield for a few seconds when started. This allows the xfstk tool to detect it and begin the download, but not long enough to complete the process so it times out. The only development access I have to the phone now is via adb, but since I don't have root I'm very limited in what I can do via command line. Since I can't access fastboot I can't achieve root. It's just a comedy of errors now.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
sukhwant717 said:
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
Click to expand...
Click to collapse
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
kidnova said:
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
Click to expand...
Click to collapse
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
mrperalta said:
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
Click to expand...
Click to collapse
I've tried this many times, but it only shows Moorefield for a few seconds. I'm assuming this is because it has a fully operational OS so it doesn't stay in the generic USB device mode.
EDIT: I misread your original post. Holding power and volume DOWN does keep connect it in Moorefield. Thanks so much for that. The problem now is that once xFSTK gets to downloading the OS it reboots the phone which takes it out of USB mode and disconnects the tool. I'm still stuck where I was before, but that's a little progress. Any other thoughts?
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
kidnova said:
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
Click to expand...
Click to collapse
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
"those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds"
Click to expand...
Click to collapse
-sukhwant717
mrperalta said:
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
-sukhwant717
Click to expand...
Click to collapse
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
kidnova said:
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
Click to expand...
Click to collapse
Hi, got the same issues, I've read many posts. Tried all of the million options. What was your final way of doing it, do you remember?
I've been watching several threads for the last few days, and have not seen this exact issue. I would greatly appreciate some help.
Device:
- Nexus 5X LGH790 32GB
- Stock bootloader / fastboot
- Never unlocked / rooted / etc.
The only advanced thing I've done is join the beta program a few months ago to get 7.0 early. Got that without any issue.
Issue:
I received the 7.1.1 OTA on the day it came out. Installed with no problems. The next day, the phone just froze in the middle of regular use. After about 15 seconds, it started boot looping to the Google splash screen. I can hold volume-down to enter fastboot, but when I select recovery mode, it just starts looping again. Pretty much all I could do was power it off. I did find out by accident that if I left it looping for long enough, sometimes it actually loaded normally (I even saw beta program warning/notice). But when I tried using it for more than a minute, it would freeze, reboot, and loop again.
What I've already tried:
- I tried using the WugFresh NRT fix softbrick method. I was able to quickly turn on debugging one of the times that I left it to loop. But when NRT sent a reboot the phone, it threw it back into the loop and NRT stopped recognizing the device.
- I tried to follow the unbrick procedure using a TOT file in this thread: http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766 But even after using LGUP, I still cannot even get into recovery mode.
- I filed a bug in the AOSP here: https://code.google.com/p/android/issues/detail?id=225802.
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
DC_Knight said:
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
Click to expand...
Click to collapse
Try fastboot/bootloader mode and fastboot flash the OTA manually.
Update 2: Seems like all the other things I tried over the last few days have caused various unofficial USB drivers to be installed. I've tried uninstalling most of them. I downloaded the google USB driver from latest SDK. But my 5X is still recognized as a Kedacom device when it is sitting at FastBoot.
However, I must have made some progress because I was able to start the sideload process. Unfortunately, I am now stuck on yet another error. The phone hangs at "verifying update package" and then after about 2 minutes... it reboots itself and starts looping again!
I thought I had it. So close. Now I want to throw the phone. Going to sleep, but would be grateful for any other suggestions in the morning.
- DCK
use nrt to erase all partitions, then download 7.1 factory image, unzip and flash one by one the partitions.
DC_Knight said:
...
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Click to expand...
Click to collapse
Sounds like the boot loop issue many people have been having (the hardware/solder issue). It happened to me a few weeks ago after upgrading to Android 7.0. I got a replacement device from google.
If you're bootloader is locked, NRT or any other method to flash the factory image is not going to work. The only suggestion I have is to un-enroll in the beta program and hope your device will boot long enough to flash the ota Google will send the device to get back to 7.0. Note, this will wipe your device.
Sent from my Nexus 9 using XDA-Developers mobile app
Same problem here. It can't be recognized after I reboot to fastboot. So I can't flash anything.
If the device isn't recognized try this http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33. It's worked for a few of us with the same problem
Sent from my Nexus 9 using XDA-Developers mobile app
Enter stock recovery then flash the full ota via adb sideload