[Q] stuck at LG Logo after sucessful LG root Script v1.2 - Sprint LG G2

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.

Related

is this **** bricked??

its just sitting on the freaking LG screen... every time i vol dwn + pwr and double press power it goes normal but then cwm doesn't come up and it just restarts and hangs at LG again. i ****ing hate this phone can someone please help me out? why won't cwm load
can you describe exactly the process you took to port CWM into your phone? Let's see if something happened along the way to cause it to not work properly.
Also, is CWM the one not working, or did you flash a ROM on your phone and something went wrong, and you are trying to get to CWM to restore your phone but not getting anywhere with it?
aquariuz23 said:
can you describe exactly the process you took to port CWM into your phone? Let's see if something happened along the way to cause it to not work properly.
Also, is CWM the one not working, or did you flash a ROM on your phone and something went wrong, and you are trying to get to CWM to restore your phone but not getting anywhere with it?
Click to expand...
Click to collapse
followed the steps on the cwm thread. used terminal emulator. worked great. was working fine until now. i flashed kernels beta 2 and only wiped cache and dalvik and now nothing is working. no cwm to restore, can't even get to the at&t boot animation. this is a mystery.
mic.mayorga said:
followed the steps on the cwm thread. used terminal emulator. worked great. was working fine until now. i flashed kernels beta 2 and only wiped cache and dalvik and now nothing is working. no cwm to restore, can't even get to the at&t boot animation. this is a mystery.
Click to expand...
Click to collapse
Sorry to hear that. Unfortunately I can't help much at all since I haven't done either yet (CWM or Kernels/rom installations) so rather than making things worse for you, I'll leave it to the Pros here to help you. Im sure one of them will respond back soon enough.
Try this:
Disconnect the phone and pull out the battery.
Put battery back in and plug phone to a wall charger. Let it boot to the battery charging screen. Once there press and hold POWER + VOLDOWN
Depends on type of the problem, it helped me 9 out 10 times...
tried it at least 20 times now. just realized that i didn't format /system nor did i update cwm yesterday. probably the root of all these problems. I'm just gonna start fresh with the kdz. I'm on a mac though so its going to be a long night starting with boot camp.
I'm having the same problems...well kind of...
I followed all the instructions for CWM and everything went great. No real issues but had to reinstall the .img twice and then was perfect thereafter. Saw the beta 2 ROM and figured what the hey...downloaded and installed to SD Card. Used CWM/Nandroid to do a backup then installed the zip for the ROM from the sd card.
It took a matter of 10 seconds and said it was successful/done and restarted phone-got a boot loop on LG screen for about 15 minutes and finally did a battery pull-tried several times to get it into CWM with no luck and finally was able to get in-but had to plug it into the wall and wait for charging screen to show. Was able to restore and all was well until turning the phone off.
Turning off the phone now causes the phone to loop on the ATT screen-I can get into download mode and can get into CWM and restore and all is well until turning phone off.
I figured it just needs a fresh install so I've been trying to flash the kdz but the firmware updater keeps faulting and never makes it through the process...so I'm stuck...have all the files I need (I believe) and have everything in place...just can't get it back to normal.
Any ideas from here?
Thanks in advance!
Yeah, sometimes it could be quicker just start over and restore backups...
While you there, would you mind do this: Needed SystemUI.apk from SU640
[EDIT]
@fishscale28:
did you do kdz unbrick before? If not, then perhaps you are not doing it right...btw, kdz file for LU6200 didn't work for me.
Nope-never done a kdz unbrick before-I have the kdz v10i_00 for the 640. I have all the drivers installed, the parser deal installed, windows enabler program running and use the kdz updater to update the firmware. Is there something Im missing here? Seems like several people have gotten the updater to crash when trying to update the firmware...any ideas why?
---------- Post added at 05:51 AM ---------- Previous post was at 05:38 AM ----------
I went through a few of the threads and saw there was a .dll file to be deleted in the updater folders so I did that and now I can do absolutely nothing with the program. Only start and exit...am unable to select anything, view anything, get anything to function...
fishscale28 said:
Nope-never done a kdz unbrick before-I have the kdz v10i_00 for the 640. I have all the drivers installed, the parser deal installed, windows enabler program running and use the kdz updater to update the firmware. Is there something Im missing here? Seems like several people have gotten the updater to crash when trying to update the firmware...any ideas why?
---------- Post added at 05:51 AM ---------- Previous post was at 05:38 AM ----------
I went through a few of the threads and saw there was a .dll file to be deleted in the updater folders so I did that and now I can do absolutely nothing with the program. Only start and exit...am unable to select anything, view anything, get anything to function...
Click to expand...
Click to collapse
I installed from the kdz yesterday and didn't have to delete any files. I'm on Win 7 x64. The first time it ran it told me to restart my phone cause it didn't see it, but the second time it ran until my phone reboot and I killed the program. Be sure you have the KDZ_FW_UPD_EN with UpTestEX_mod2_marwin.exe in it. Hope this helps.
Thanks for your help. I did all that...again...I even deleted, reinstalled all the updater stuff, tried running as admin, tried running in compatibility mode, ran it after deleting the recommended .dll file and the option to do anything was gone, put it back in and was able to run everything fine and a little after extracting the kdz it would crash. I unplugged the phone and re-ran the proggy and it went through the check, noticed the phone wasn't hooked up and finished the check. Plug phone in, start process over and proggy crashes.
I don't get it-I would say its the wrong kdz but its not. I installed all the drivers and it still doesn't work. I've tried every combo of everything and the proggies keep crashing.
Now I was finally able to get into CWM to flash another ROM and was able to get one going-was able to boot into the os but same as before-once the phone is turned off it starts the boot loop. Now its even harder to get back to CWM but a restore works from there. Any ideas on why the boot image keeps reverting back to whatever was screwed up? Has to be something that happens once the system starts up again as it's after a restore and when the phone is turned off. Stumped and would love to be able to use my phone...It seems like flashing the kdz would be the sure fire way to get it done-are there options aside from the updaters that keep crashing?
Thanks in advance!
Maybe http://www.microsoft.com/windows/virtual-pc/ can help?
alright so i got to the 4% thing and my phone rebooted but it kept looping to the screen LG Optimus LTE bootscreen with the pink candy cane. thats it. i did vol dwn + pwr and got the android arrow and box with loading bar no text, then it rebooted back to the optimus lte screen. never got to the setup screen. tried the kdz again and my phone died. now when i plug it in i only get download mode... does it charge in download mode and why did it not get to the setup screen?!
fishscale28 said:
Thanks for your help. I did all that...again...I even deleted, reinstalled all the updater stuff, tried running as admin, tried running in compatibility mode, ran it after deleting the recommended .dll file and the option to do anything was gone, put it back in and was able to run everything fine and a little after extracting the kdz it would crash. I unplugged the phone and re-ran the proggy and it went through the check, noticed the phone wasn't hooked up and finished the check. Plug phone in, start process over and proggy crashes.
I don't get it-I would say its the wrong kdz but its not. I installed all the drivers and it still doesn't work. I've tried every combo of everything and the proggies keep crashing.
Now I was finally able to get into CWM to flash another ROM and was able to get one going-was able to boot into the os but same as before-once the phone is turned off it starts the boot loop. Now its even harder to get back to CWM but a restore works from there. Any ideas on why the boot image keeps reverting back to whatever was screwed up? Has to be something that happens once the system starts up again as it's after a restore and when the phone is turned off. Stumped and would love to be able to use my phone...It seems like flashing the kdz would be the sure fire way to get it done-are there options aside from the updaters that keep crashing?
Thanks in advance!
Click to expand...
Click to collapse
Even after running the kdz, my phone still does that after installing CWM. I don't know if it's something with my ROM or something with CWM, but if you can't get into CWM you probably don't need to run the kdz. I couldn't get into CWM anymore when I ran it.
So you're saying you go into the boot loop after turning off your phone even after unbricking?
I don't get it-now I can't get into recovery and it keeps up with the boot loop. I've tried running on the virtual PC/XP deal and it doesn't crash but now it doesn't even see the phone...reinstalled all the drivers, etc. and still no luck. Is there anyway to get the kdz installed without this updater?
fishscale28 said:
So you're saying you go into the boot loop after turning off your phone even after unbricking?
Click to expand...
Click to collapse
Yes. I don't think that was happening until I put CWM on. But I can live with it until the issue is solved. I don't think I'm the only one having it.

[Q] Unable to root Sprint G2

I restored a TOT file using lgflashtool to go back to stock ZVE (previously rooted with TWRP), then ADB sideloaded to ZVG. Everything is working fine, but I can't root. I have tried the LG One Click Root (both 1.2 and 1.3) and one from highonandroid but it didn't work either. I have followed the directions exactly, enabling USB debugging and I run as admin. I am succesfully able to get the phone into download mode as well, so that is not a problem. Any ideas? I have searched this forum and didn't see anybody having problems with it so sorry if this is repeated information.
try the script method?
Hey I too have been struggling with the root via one click .. I would be good until the script would be waiting for device and download mode. I eventually uninstalled all the lg drivers and root programs I had installed. Then rebooted computer, reinstalled lg driver and ran the lg root script version 1.2, run the program and be patient. it may take up to five minutes then it will tell you to put the phone in down load mode and reconnect. It recognized the phone immediately and then I waited and waited and waited, then finally the su script completed and then the prompt was to press control+C and then N and reboot. maybe it will work for you but this is where im getting stuck.. good luck if any of this helps.
The graphic interface version worked for me. In download mode make sure it finds it on the correct Port.
If not change it in device settings.
Mine would progress to 90%and stick. After 5 minutes I disconnect, reboot phone and root was there.
Do you know what port the gui looks for the device on by default? Maybe i can assign the port befor executing the gui script.
Did you try stump root? That one worked for me on ZVE.
i
I was able to gain root by one click it would detect my phone try to reboot it in download mode but It wouldn't go into download mode if it makes it that far let it sit there rebooted and ui on computer will ask u to put it in dl mode manually. As for the port I used 41 as if I was doing a tot. Restore I can go into more detail if this is the same issue u r having
Yup. Stump dosent work on zvg. I've installed it despite what I've read and tried it. It tells me. Out says I'm already rooted, but super user tells me I'm not rooted.
Dopamin3 said:
I restored a TOT file using lgflashtool to go back to stock ZVE (previously rooted with TWRP), then ADB sideloaded to ZVG. Everything is working fine, but I can't root. I have tried the LG One Click Root (both 1.2 and 1.3) and one from highonandroid but it didn't work either. I have followed the directions exactly, enabling USB debugging and I run as admin. I am succesfully able to get the phone into download mode as well, so that is not a problem. Any ideas? I have searched this forum and didn't see anybody having problems with it so sorry if this is repeated information.
Click to expand...
Click to collapse
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.
Port 41works for mine

Phone boots into firmware update

I recently updated my lg G3 ( Google patch update named Aug-18-2015 etc) and it started to malfunction with resets, crashing and eventually got it stuck in boot loop. Then it booted into a green screen that said "demigod crash handler/tz crash" thrice. Instead of a hard reset I decided to using the lg mobile support tool to fix it. During the upgrade recovery my phone went into download mode/firmware update. I could see the progress bar moving and then get stuck and my mobile would switch off. Took out the battery, disconnected and reconnected the phone and tried the process all over again but in vain. I repeated this at least 8 times and eventually gave up. Now my phone is basically useless and only boots into firmware update. Hard reset doesn't work either. Can somebody please help me fix this?
Android version : 5.0
Kernel: 3.4.0
Firmware : v20t-ame-xx
Did you try to unbrick/unroot (there so much video about it) it should fix it
jonnyszt said:
Did you try to unbrick/unroot (there so much video about it) it should fix it
Click to expand...
Click to collapse
I have tried everything available online but nothing works. Im so frustrated atm. :/
Could you enter recovery. Connect your phone into your computer in firewall update and after go on adb and fastboot commends and type adb reboot-recovery

Phone no longer bricked (yay!), but not fastboot

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?

[REQ] Help: bootloop after 7.1.1 beta OTA and cannot enter recovery mode

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

Categories

Resources