[Q] Help! Won't boot after software update. - G3 Q&A, Help & Troubleshooting

Ok, so I did something really stupid this morning. I had a notification that a software update was available. I decided to ignore my better judgement and install it. After it downloaded, the phone rebooted and went into recovery. When I say recovery, I mean TWRP, since that's what I have installed. Now every time I reboot the phone, it just goes straight to TWRP! I tried wiping the phone (factory reset). I even tried installing a different ROM! It just keeps on booting straight to recovery.
Any suggestions? Please help. I'm dead in the water.

Download mode and Lg flashtool flash KDZ.

Whose a silly boy then.
Cant believe that people are still installing OTA updates even though they have TWRP.

Vivasanti said:
Whose a silly boy then.
Cant believe that people are still installing OTA updates even though they have TWRP.
Click to expand...
Click to collapse
You'll get no argument from me...

Related

[Q] ViperOne: "set_perm some changes failed"

So I tried flashing this ROM and i got this "set_perm some changes failed" at the end. It started to bootloop my phone and recovery wouldn't work anymore. I was able to get to fastbootUSB and tried reflashing recovery, but same issue. After wiping the cache via fastbootUSB and refalshing the recovery once again, i was able to get to recovery.
With that outta the way, whats this install error? I've really been waiting for ViperOne on VZW and i can't install it...
MagicsMan said:
So I tried flashing this ROM and i got this "set_perm some changes failed" at the end. It started to bootloop my phone and recovery wouldn't work anymore. I was able to get to fastbootUSB and tried reflashing recovery, but same issue. After wiping the cache via fastbootUSB and refalshing the recovery once again, i was able to get to recovery.
With that outta the way, whats this install error? I've really been waiting for ViperOne on VZW and i can't install it...
Click to expand...
Click to collapse
the guy who ported the rom over is fixing it. his thread said to check in the morning.
on another note, how did your recovery not work anymore?
wiredout46 said:
the guy who ported the rom over is fixing it. his thread said to check in the morning.
on another note, how did your recovery not work anymore?
Click to expand...
Click to collapse
went it bootlooped, i held the volume down key and while on HTC screen, top said "Entering Recovery" instead of booting to bootloader. once it tried to start recovery i see it for a sec then it reboots again.
BTW, is there any way i can post in his rom thread, he said he'll fix it in like an hour, and i'm up to the late hours of the night. i'd like to coment in that thread for any probs or help of any sort, cuase i get a forum error saying i new here, i may not post much but i've been on xda for a couple years now.

Trying to update while rooted...

Hello,
today I accidentally tapped on "Update" (to 7.1.1) on my rooted Nexus 5X... Something you usually shouldn't do, but it was 2am and I was tired and.... Doesn't matter. After this my phone rebooted and almost instantly showed the dead android with the message "No command". And now I'm stuck there. After rebooting I still land there.
Since the error message almost instantly appeared and since I still can boot into TWRP (3.0.2-2), I think the update wasn't installed and I hope to find a way to avoid the factory reset of my phone. Do you have some tips or possible solutions what I should do in this case?
Thank you for your help.
Its odd this happened, when rooted and twrp installed. in my experience, the update will just simply fail and it will boot back up.... in your case, it sounds like something flashed but the phone didnt like it.... All I can think of is if you cant get into twrp, boot into fastboot and flash the factory image from google, you will loose all data though.....
EDIT, RE-READ you post, if you CAN get into TWRP, try flashing a backup... you should have a backup I hope, lol... First rule of root and flashing is make a backup asap....LOL
When I rooted my phone I did a backup. But the problem is, it was several months ago. So I tried the only method I could save all my data. It wasn't safe, I knew this, but no risk no fun.
My solution was: Download the ota update from Google and flash it with TWRP... Voila! My phone boots properly with the new update... But this method is like I mentioned before not safe and can probably cause a boot-loop with an overwritten recovery. I had to flash my recovery again, but everything works fine now.

Boot Looping Help Please

I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
So I tried sideloading. I was able to get into the stock recovery. I tried wiping cache and data, then tried installing the newest stock rom.
Everything seemed to work. Then I had to restart. A message popped up after the same "Your device software can't be checked for corruptions. Please lock the bootloader". It had the title in blue stating "Encryption unsuccessful".
Then said, "Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
Then there is a single button that says, "Reset Phone".
Problem still persists.
Help please...
Why did you bought a bootlooped phone?
Sin Stalker said:
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
Click to expand...
Click to collapse
When my Nexus 5x got into bootloop, I sent it to LG and they had to change the whole circuit. So yeah.
When you flash Google Factory Image, it flash the stock kernel.
If you have warranty, then send it to Google/LG. If you haven't got, then you're in problem. New motherboard needed, but it's expensive.
See the following thread for more info.
https://forum.xda-developers.com/nexus-5x/help/5x-bootloop-cause-fix-t3476794/
khalifakk said:
Why did you bought a bootlooped phone?
Click to expand...
Click to collapse
Cause its cheaper.
Sin Stalker said:
Cause its cheaper.
Click to expand...
Click to collapse
Then face the consequences...
khalifakk said:
Then face the consequences...
Click to expand...
Click to collapse
What consequences?
Hardware bootloop can't be fix by software.
Duckscreen said:
Hardware bootloop can't be fix by software.
Click to expand...
Click to collapse
Exactly. Everyone has either been able to get a replacement under warranty or was pretty much screwed if it was out of warranty.
Sent from my Nexus 5X using Tapatalk
Sin Stalker said:
What consequences?
Click to expand...
Click to collapse
A bootlooped phone for ever....
I recommend you will install kernel adiutor app after try rooting
I recommend you will install kernel adiutor app after try rooting
Almost I got no bootloop even no random reboot nexus 5x's state

att g3 stuck in factory restore stage 2 (not sure if this goes here sorry)

I tried restoring back to factory after being stuck in a boot loop, thinking my root was the issue or something idk. I used flash tool to try and flash back to stock and fac reset and it gets to the end where MiniOS tries to do its thing but i get no promts and it just says factory reset status 2. its driving me insane trying to get this thing flashed back to stock. i dunno if im missing anything or something but im foloowing the steps like to the letter and it keeps bricking. any help or advice here that could help me out? and sorry if this doesnt go here and stuff. im new to the forums and all that.
Hi,
I had the same problem yesterday. Even worse after that factory reset status 2 my phone couldn't be detected anymore by flashtool 1.8. So I tried the kdz method. This worked for me and from stock I was able to use one click root and flash twrp with flashify. Then I went straight to android 8.1 with magisk root. Don't forget to flash mr bump after root without any reboot in between.
f4lkon said:
Hi,
I had the same problem yesterday. Even worse after that factory reset status 2 my phone couldn't be detected anymore by flashtool 1.8. So I tried the kdz method. This worked for me and from stock I was able to use one click root and flash twrp with flashify. Then I went straight to android 8.1 with magisk root. Don't forget to flash mr bump after root without any reboot in between.
Click to expand...
Click to collapse
yeah i ended up getting it out of status 2 and tried to run stock for a bit but ended up having issues where it would just randomly shut itself off. and then boot loops. switched out like 3 different batteries, (1 that came with the phone, a not so great quality 6000mAh, and a new stock lg battery) and still having boot loop issues. so im thinking that the phone is just dead. so with tax season coming up soon i may just wait and get that new sexy razer phone. i need something new anyway and better than this walmart zte placeholder im using. lol

I have hit a wall

Hello everyone, Merry Christmas!
Although I say that, I bring not so merry news. My OnePlus 7T is bricked and after trying everything I don't know where to go from here. Currently I am stuck at the:
The current image (boot/recovery) has been destroyed​phase of things and all I can do is boot into fastboot, that is it.
How did this all start? All I did was just update the phone to Android 12 with the official OTA update from OnePlus, big mistake. Worst update ever; my adaptive brightness went haywire, the brightness gets stuck at max, I couldn't receive calls, data was completely unresponsive, and the list goes on. So before the obvious downgrade method, I try a few things first:
Cycle airplane mode on/off
Reset network settings
Reset ANR
These worked for a minute on my data then right back to the same issue.
Wipe cache partition... Oh wait I had to find out the hard way Android 12 removed this option....
Wipe the phone
That fixed nothing.
Ok time to downgrade, but this is where things got tricky and I realized that maybe all my issues stemmed from me getting the wrong update from OnePlus? Although I found this out too late.
See my phone model is HD1907 which I already knew at the back of my head, but when it mattered to remember the most, I didn't catch what happened. After my update to A12, my model number changed to HD1901 which is the Indian version, and when I saw it didn't think anything of it at the time but then after all my problems it came back to me, my phone has always HD1907 so maybe this is a compatibility issue.
Anyway since I was going to downgrade anyway I thought to myself, 'since I already wiped everything, maybe I can use this opportunity to try out a ROM for A12 and see if it is just this ****ty OOS causing all these issues,' and so I did. First thing I did was unlock the bootloader, and try get TWRP on my phone. That all went fine, I booted into TWRP, flashed my zip for TWRP, then proceeded to try to boot into the OS... and the rest is history because that is as far as I got. Apparently my boot.img is destroyed and I can't boot back into TWRP anymore either, all I can do is get to fastboot.
So then I tried MSM, it won't detect my phone.... So then I tried flashing my Stock ROM through fastboot, apparently I'm missing a partition and it won't write to a critical partition either....
So where do I go from here...?
Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!
Canbeit said:
Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!
Click to expand...
Click to collapse
I too had all the symptoms after an update to OOS12, including progressively losing any semblance of booting. not even recovery and the drivers found elsewhere didn't work, and had a different name when installed and would never get detected in the MsmDownloadTool. After installing this one and rebooting, it finally detects it and installs the image of EDL mode.

Categories

Resources