Related
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.
I just got the official update to Marshmallow and I decided to just do it since it is official. It downloaded and then installed. Then it rebooted and showed that "apps are being optimized" screen and after that a bootloop of the lg logo. Rebooting doesnt work only if I take the battery out but afterwards there's still a bootloop. I also didn't do root or anything else to my device. I can not enter download mode or recovery either, but honestly idk if it has worked before.
Can anyone with probably similar experiences help me? Thanks in Advance from Germany
LG G3 D855 16Gb Europe unlocked Marshmallow update boot loop.
PCSE said:
I just got the official update to Marshmallow and I decided to just do it since it is official. It downloaded and then installed. Then it rebooted and showed that "apps are being optimized" screen and after that a bootloop of the lg logo. Rebooting doesnt work only if I take the battery out but afterwards there's still a bootloop. I also didn't do root or anything else to my device. I can not enter download mode or recovery either, but honestly idk if it has worked before.
Can anyone with probably similar experiences help me? Thanks in Advance from Germany
Click to expand...
Click to collapse
I have exactly the same issue. I have a German-bought LG G3 d855 updating this morning to Marshmallow. It is now caught in exactly the same boot loop. I get the LG logo, for a few minutes (the brightness changes during this time) followed by the "Android is updating..." app optimization screen which optimizes my 44 apps before going back to the logo in a constant cycle. Then my 44 apps get optimized yet again, and on it goes. I can't enter recovery, none of the button combinations has any effect. Phone has no mods, and was working fine before this.
Does anyone have any ideas?
Hi,
Similar issue here, my phone updated today (also no root, no mods) and for a couple of hours everything worked fine (just some missing apps after the process, but ok), then I went to flight mode and back and then it started with the reboot loops.
The reboots on my phone happen after some seconds in the home screen, so I have time to try to set it in flight mode again, and in some cases, after this it stops rebooting, but in flight mode, with no connections at all.
I'm trying to remove things to avoid doing a factory reset by now, removing cache didn't help...
Is your phone rebooting also after loading the home screen? or it just loops in the LG screen or in the apps update screen?
Hello,
I had the same problem. Just hardware reset the device and the device will continue from optimizing the apps
Instructions on how to hard reset see the video find on youtube "How to Enter into Recovery Mode on LG G3!"
pbasiros said:
Hello,
I had the same problem. Just hardware reset the device and the device will continue from optimizing the apps
Instructions on how to hard reset see the video find on youtube "How to Enter into Recovery Mode on LG G3!"
Click to expand...
Click to collapse
Hello,
I got exactly the same problem (LG logo, brithness + and -, and then optimizing apps, then reboot)
I have a G3 european stock version, recently update to marshmallow (3 weeks ago). The pb occur when trying to connect to a open wifi network : suddenly reboot, then stucked in bootloop.
Is there any possbility of doing something using the "download mode" ? I really would like to recover photos in internal memory...
thanks
PCSE said:
I just got the official update to Marshmallow and I decided to just do it since it is official. It downloaded and then installed. Then it rebooted and showed that "apps are being optimized" screen and after that a bootloop of the lg logo. Rebooting doesnt work only if I take the battery out but afterwards there's still a bootloop. I also didn't do root or anything else to my device. I can not enter download mode or recovery either, but honestly idk if it has worked before.
Can anyone with probably similar experiences help me? Thanks in Advance from Germany
Click to expand...
Click to collapse
Hi
I managed to recover my phone, BUT I didn't manage to recover my personnal data... I had to reset everything...
My method : with this tool https://www.google.fr/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwi9oJnC66bMAhWHDsAKHY_cBVQQFggdMAA&url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D2683691&usg=AFQjCNGG5q9UKA6oKXlahEEOksUo8faGrw&sig2=cTz4bAtdqp4BEut2S4B2GA enter your imei, and download KDZ file, latest directly from LG server.
Then follow this method (in french sorry)
http://www.phonandroid.com/forum/installation-propre-flasher-facilement-un-firmware-officiel-fichier-kdz-lg-g3-t97193.html#p1452621
You can try "normal flash" at the first time, but if it doesn't work (for me it doesn't work) you will have to choose "CSE Flash" and it should work. But you will loose your personnal data. So be strong.
nikoscotch said:
Hi
I managed to recover my phone, BUT I didn't manage to recover my personnal data... I had to reset everything...
My method : with this tool https://www.google.fr/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwi9oJnC66bMAhWHDsAKHY_cBVQQFggdMAA&url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D2683691&usg=AFQjCNGG5q9UKA6oKXlahEEOksUo8faGrw&sig2=cTz4bAtdqp4BEut2S4B2GA enter your imei, and download KDZ file, latest directly from LG server.
Then follow this method (in french sorry)
http://www.phonandroid.com/forum/installation-propre-flasher-facilement-un-firmware-officiel-fichier-kdz-lg-g3-t97193.html#p1452621
You can try "normal flash" at the first time, but if it doesn't work (for me it doesn't work) you will have to choose "CSE Flash" and it should work. But you will loose your personnal data. So be strong.
Click to expand...
Click to collapse
Bro Thank You so much ive been searching for solution the last 2 days and you finally saved my life Thank you Man !
i have the same problem....after the stock firmware has been restored,what method is used to get the proper working marshmallow upgrade?
I went from 5.0 to 6.0 using the LG PC Suite.
0 problems, 0 reboots, quick and fast. Did you update through OTA?
yes i did but still boot lop............is it the battery?
so ?
Same problem here, did you find a solution ?
New G3 from LG but back in bootloop after 24h of use.
Thank you.
I got the exact same issue, neither hard reset or flashing firmware works. Is there any other solution or should i start looking for a new phone?
Edit: Somehow it works just fine now lol. Tried flashing it like 3 times and hard reset twice and now after an hour of constant optimizing apps bootlopping i pulled out the battery for like the 100th time and now it works, what the hell. Looks like my G3 will die soon tho haha
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
Long story short, my phone came from China and did not have Google Apps installed. I tried to root it with some youtube method and the boot.img file got changed, not knowing what to do next I gave it to repair shop.
They somehow managed to restore the stock rom and gave me the stock rom.zip file as well but the IMEI was removed, so after trying a few methods I realized my phone doesn't get detected in META Mode but somehow gets detected if it's turned off and connected directly. I thought should install the stock firmware again by myself.
I first tried it with Download mode only, it loaded a few files but gave some error like IMGHDR_TYPE_MISMATCHED. After that it got stuck on boot screen.
So instead of the download option in SP tool I chose Format All + Download.
The thing is my phone does not get detected in META Mode so I thought it wouldn't change anything but now the phone doesn't turn on. The screen is blank, nothing happens with phone is connected to charger.
If I connect the phone to PC, it detects a Preloader Port Android (COM 7) on device manager for a few seconds then goes off, then keeps going on and off like it's trying to boot but doesn't boot.
Please help. This phone can't be sent back to china because the warranty is possibly void as this phone has been used about 6 months and also been tried for rooting.
It still gets connected via SP Tool but gives the same error after loading a few files. Image Attached.
https://preview.ibb.co/kyJvZn/xt1662bricked.png
Any help in this regard would be much appreciated.
Thank you.
I had the same initial issue, so I did the "Format All + Download" on the SP Tool with a ROM I downloaded and it flashed successfully and everything works fine now, it even auto updated to the Android 7.0 and the latest security patches (05/08/18).
I cannot remember from where I got the ROM I used but I can upload it for you, if you want/need it.
The only issue is that I lost my IMEI. When I find a way to fix it I will let you know.
https://www.youtube.com/watch?v=jgTSbGBk1bI
I followed that and I successfully restored my lost IMEI, everything works fine now.
Hope it helps.
Tiki Thorsen said:
I had the same initial issue, so I did the "Format All + Download" on the SP Tool with a ROM I downloaded and it flashed successfully and everything works fine now, it even auto updated to the Android 7.0 and the latest security patches (05/08/18).
I cannot remember from where I got the ROM I used but I can upload it for you, if you want/need it.
The only issue is that I lost my IMEI. When I find a way to fix it I will let you know.
Click to expand...
Click to collapse
when i m trying this i m getting error of
verified boot is enabled please download signed image (md1img-verified.img) or disable verified boot
earthworm82 said:
when i m trying this i m getting error of
verified boot is enabled please download signed image (md1img-verified.img) or disable verified boot
Click to expand...
Click to collapse
Sadly I cannot help you since I no longer have that phone available, sorry.