I was on 13B rooted, then flashed the stock system to return to unroot status. Everything worked fine. Plugged into computer and Verizon Upgrade Assistant suggested upgrade to 13C, so I bit. After a 4 hour (!) download of a 2 Gb file, the upgrade install proceeded without incident, and resulted in a successful completion according to the Assistant. Phone started booting and the Upgrade Assistant re-read the phone as being on 13C, but, the phone stalls and refuses to boot past the Verizon red splash screen. I have pulled battery and tried numerous times to boot, with no luck. It just sticks at the same spot.
Any suggestions? I'm nervous about re-flashing 13 B for fear of bricking it, so perhaps flash 13C kdz?
Thanks in advance for any help.
I have now tried flashing the 13C kdz unsuccessfully a number of times. I verified the checksum on the downloaded kdz file, and attempted to flash it on three separate computers where I had successfully flashed the G4 in the past. Each time that I tried flashing the 13C it reads: "Required Information cannot be found. Contact the system administrator."
I am still stuck here. Even in the flash tool, the phone is read as having 13C on it, but it still will not boot past the Verizon splash screen. Any thoughts on whether I should dare try flashing 13B, or would I end up with even more of a brick then I have now?
Thanks again.
DO NOT FLASH 13B!
Isn't Android 6 24c?
I got stuck on the Verizon screen, but a wipe fixed it at that point.
fr4nk1yn said:
DO NOT FLASH 13B!
Isn't Android 6*?
I got stuck on the Verizon screen, but a wipe fixed it at that point.
Click to expand...
Click to collapse
Thanks, and you are correct on the number, MM is 24C.
May I ask, how were you able to wipe when stuck on the Verizon splash screen? I would love to do that if possible.
Thanks again.
Katmeat said:
Thanks, and you are correct on the number, MM is 24C.
May I ask, how were you able to wipe when stuck on the Verizon splash screen? I would love to do that if possible.
Thanks again.
Click to expand...
Click to collapse
Hold volume down and power on if I remember correctly to put the phone in recovery mode. From there you can choose to do a wipe/factory reset.
I had issues with way long boot times, the wipe fixed that, but then apps kept FC. I ended up downloading the KDZ file and used the flash tool to reflash 24C. Everything is stellar now.
Thank you so much, mikeewhite! I followed your instructions and they worked perfectly, so I am back up and running. You are the reason that I love this list so much, as there are so many people like you generous with their time and advice.
Related
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
hi everyone
after an afternoon of googling I decided I need more help
so this is what happened (at that moment I was running on PureNexus and TWRP:
at some point I noticed that my phone was off, I tried to reboot it, it showed the google logo for a moment, but then the screen went black.
after a while I tried to reboot again, with the same effect...and again
so I decided, hm maybe a factory reset helps and tried to boot into TWRP. tried to boot into recovery, but with the same result as before: google logo appears then screen turns black
next I booted into bootloader and flashed TWRP through adb. but this didnt help either. still everything just as before.
at that point I got a little nervous. then I deleted cache and userdata through fastboot, still nothing.
after some googling I stumbled over a thread which suggested to use the Nexus Root Toolkit for reflashing Stock.
I followed all the instructions in NRT and according to the log (and fastboot), all the images were successfully flashed, but when I booted the screen turned black after the google logo again.
since I was able to boot into bootloader, I decided to lock and unlock the bootloader (at that point I was just trying to see some effect), but nothing worked
any suggestions on what else I could try?
thanks! cheers
trier09 said:
hi everyone
after an afternoon of googling I decided I need more help
so this is what happened (at that moment I was running on PureNexus and TWRP:
at some point I noticed that my phone was off, I tried to reboot it, it showed the google logo for a moment, but then the screen went black.
after a while I tried to reboot again, with the same effect...and again
so I decided, hm maybe a factory reset helps and tried to boot into TWRP. tried to boot into recovery, but with the same result as before: google logo appears then screen turns black
next I booted into bootloader and flashed TWRP through adb. but this didnt help either. still everything just as before.
at that point I got a little nervous. then I deleted cache and userdata through fastboot, still nothing.
after some googling I stumbled over a thread which suggested to use the Nexus Root Toolkit for reflashing Stock.
I followed all the instructions in NRT and according to the log (and fastboot), all the images were successfully flashed, but when I booted the screen turned black after the google logo again.
since I was able to boot into bootloader, I decided to lock and unlock the bootloader (at that point I was just trying to see some effect), but nothing worked
any suggestions on what else I could try?
thanks! cheers
Click to expand...
Click to collapse
If this is not the dreaded bootloop, unlock the bootloader and flash factory image manually.
That should help.
indian84 said:
If this is not the dreaded bootloop, unlock the bootloader and flash factory image manually.
That should help.
Click to expand...
Click to collapse
thanks, I was afraid it might be....
I flashed the factory image first with the sh_all option and then manually. both methods didnt work and I couldnt get past the google logo.
Right now Im not even able to boot into the bootloader.
Im assuming theres nothing else the try besides contacting LG support?
Maybe its time to say goodbye to a good friend
trier09 said:
thanks, I was afraid it might be....
I flashed the factory image first with the sh_all option and then manually. both methods didnt work and I couldnt get past the google logo.
Right now Im not even able to boot into the bootloader.
Im assuming theres nothing else the try besides contacting LG support?
Maybe its time to say goodbye to a good friend
Click to expand...
Click to collapse
LG Support it is for you. They have know to replace units that have passed the warranty period by one or two months. Give it a shot
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 was running the latest version of TWRP and a rooted version of the LG G6 port. Everything was stable and worked fine. So I was ready to give it back to its owner who I had modded it for. I went into the settings menu of the phone and did a standard factory reset to remove my account that was logged in so I could test the phone out before giving it to the owner. well when it finished resetting and rebooted, its been stuck in a boot loop ever since.
Tried just clearing both Dalvik Cache and Cache, to no avail. Tried Reflashing the rom and starting over. Still nothing. Tried flashing a different rom. Still nothing.
So what else can I try? and also if its the only thing I can do, rest it all the way back to stock factory everything. How do I do that on this phone. What program do I need and what files. and whats the steps to complete the process.
Thank you in advance for all help that is given
i factory reset in twrp and turned on developers options after first boot then reflashed twrp i always forget backup lol or delete it or use kdz you flashed before anyway i can help i will if you still need
if you have tried to flash the same custom rom or another is still not working, flashes with the program "lg up", you will need a kdz file,and the corresponding drivers. if with that you can not watch this tutorial before doing anything.
if you have a backup made with twrp, it flashes again.
https://forum.xda-developers.com/g4/help/unbrick-lg-g4-brick-hs-usb-qdloader-t3542785
during this process you will have to disassemble the back of the phone, (plastic) you do not need to remove the motherboard completely from the phone, anyway if you can enter download mode try with lg up tool.
if you need help around here we are.
Well now in the process of trying to fix it. The phone bricked and will no longer turn on at all. Is there anyway to fix this ?
Silicon Knight said:
Well now in the process of trying to fix it. The phone bricked and will no longer turn on at all. Is there anyway to fix this ?
Click to expand...
Click to collapse
Can you get into download mode?
Also, it's possible you have been hit by the bootloop
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.