Hello,
Here is what led to my issue:
I rooted my phone using this method: http://forum.xda-developers.com/showthread.php?p=38886073#post38886073
Downloaded clockwork rom manager.
Here comes the thing I don't remember. At least i know that the last thing i did was to click on 'backup current rom'
After this the phone reset itself and this message came up:
Secure booting error!
Cause: boot certification verify
Then i tried to reset using the power button, which led me to the 'battery full' screen - afterwards i was able to reboot. As stupid as I am I just tried the same thing again. And ever since i am stuck at the 'Secure booting error!' screen.
I am unable to enter download mode. I get to the 'Hard factory reset' screen, but if i accept doing so, it says 'Secure booting error!' again.
I also remember clicking on 'restart into recovery mode' at some point, but this is not the last thing i did.
I am really desperate. Please, help me!
Well i had the same issue today... It happened after i did two changes. One of them was to to try to relock from freegee and flash twrp again from freegee. In my case i was able to go in download mode and flash original kk rom with lg flash tool.
Unfortunatly, trying to boot in downloadmode, i still get the same error :/
Jubi-Wan said:
Unfortunatly, trying to boot in downloadmode, i still get the same error :/
Click to expand...
Click to collapse
How are you trying to boot into download mode? And what factory reset screen? It seems as though you did not unlock the bootloader using freegee, if you make any changes and relock the boot loader you will get that error. But it seems that it has not been unlocked. If you hold power and volume up what happens? Same thing when power and volume down, one of them is recovery (possibly factory reset you are seeing) and the other is download mode. I don't remember right now but you should read the whole softbrick thread and see if you are missing something. You may need to use LGPNST to go back to stock, you can also use that program to flash a new recovery so read carefully and follow all steps.
When this happened to me I was able to flash an unlocked bootloader and it allowed me to use my phone again as it was before doing something stupid (for me it was an attempt to re lock the bootloader).
well, i managed to get into download mode. Obviously i used the wrong method to get into download mode...
I used this method and everything worked fine, so far. : http://forum.xda-developers.com/showthread.php?t=2249500
My phone doesn't boot now. Fast Boot doesnt work aswell.
All that happens is a white battery showing on the screen and when i try to fastboot all that happens is that the LED is blinking or glowing red after some while.
Jubi-Wan said:
well, i managed to get into download mode. Obviously i used the wrong method to get into download mode...
I used this method and everything worked fine, so far. : http://forum.xda-developers.com/showthread.php?t=2249500
My phone doesn't boot now. Fast Boot doesnt work aswell.
All that happens is a white battery showing on the screen and when i try to fastboot all that happens is that the LED is blinking or glowing red after some while.
Click to expand...
Click to collapse
What do you mean when you try to fastboot? Fastboot is basically the bootloader and allows you to select recovery or download mode. What you should have done after following that thread is go to recovery and wipe everything and flash a new ROM.
If you are saying that the bootloader is not coming up and allowing you into recovery then I believe something was missed.
After trying out some varioants of this it worked: http://forum.xda-developers.com/showthread.php?p=40274560&highlight=red+led#post40274560
I wiped the phone, but since I had to leave over the weekend i just turned it off and went away.
Now that I am back, nothing works now :/ The Phone doesnt react to anything, not even donwload-mode.
Is the battery too low maybe? It's on the wall now for a few hours, but it still doesn't react. It's not warm either.
edit:
when i charge the phone, i will get a 'watchdog bark' after some time allowing me to get into recovery. accesing downloadmode from there doesn't do anything. strangely, the recovery isnt trwp although it should be because teenybin comes with it. it's 'bbs.gaodi.net' which doesn't have a sideload feature. what do i do now?
edit2:
after 10000 tries i got into download mode. i don't want to **** up now so i won't do anything until i know exactly what to do.
any advice?
edit3:
got it working by flashing another teenybin which included trwp - then i installed miui via sideload. i don't have signal though, but i will open another thread for this since this is another issue.
My N5X has been stuck in the boot loop animation for the last 30 minutes or so after unlocking the bootloader and flashing TWRP 3.0.0. I followed the manual method guide for rooting/unlocking and was trying to make a nandroid backup, but was given a system error instead (forgot the message). I rebooted instead and have been stuck in the boot loop animation since.
When I restart the phone by holding down the power button, the bootloader still showed up as unlocked and a message popped up saying "Your device is corrupt. It's can't be trusted and may not work properly" with a red exclamation point.
Unfortunately, my computer can't detect my phone anymore through USB even after reinstalling the drivers so I can't reflash. Any thoughts?
vomitcomet said:
My N5X has been stuck in the boot loop animation for the last 30 minutes or so after unlocking the bootloader and flashing TWRP 3.0.0. I followed the manual method guide for rooting/unlocking and was trying to make a nandroid backup, but was given a system error instead (forgot the message). I rebooted instead and have been stuck in the boot loop animation since.
When I restart the phone by holding down the power button, the bootloader still showed up as unlocked and a message popped up saying "Your device is corrupt. It's can't be trusted and may not work properly" with a red exclamation point.
Unfortunately, my computer can't detect my phone anymore through USB even after reinstalling the drivers so I can't reflash. Any thoughts?
Click to expand...
Click to collapse
Are you able to get into bootloader and do a "fastboot devices" query?
peltus said:
Are you able to get into bootloader and do a "fastboot devices" query?
Click to expand...
Click to collapse
Nope
But there's good news!
I let the battery drain to 0% by letting it boot loop over and over again overnight. Plugged it back in and was able to get into TWRP. Internal storage showed up as 0MB so I factory reset it (thank you some other XDA thread). Rebooted again and now everything's good!
I guess this whole thing would have gone by a lot faster if I had done a "battery pull". Holding the power button down only restarts the phone.
vomitcomet said:
Nope
But there's good news!
I let the battery drain to 0% by letting it boot loop over and over again overnight. Plugged it back in and was able to get into TWRP. Internal storage showed up as 0MB so I factory reset it (thank you some other XDA thread). Rebooted again and now everything's good!
I guess this whole thing would have gone by a lot faster if I had done a "battery pull". Holding the power button down only restarts the phone.
Click to expand...
Click to collapse
For future reference, hold power and volume down to get into the bootloader. By holding the power button (per your OP and second post), this just reboots the phone. You only saw the bootloader message that the device is unlocked, not the actual bootloader mode.
Sent from my Nexus 5X using Tapatalk
Hi all,
I'm hoping to get some advice/help from all you experts for my HTC One M8.
It's stock, hasn't been changed or modified in anyway. After the battery went flat and it was recharged it came up with "Your phone is encrypted - enter your screen lock password". I used to have a password months ago but took it off. Anyway I put the password in and it comes up with this..."Decryption unsuccessful. The password you entered is correct, but unfortunately your data is corrupt. 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." At this point I'm swearing as it doesn't look good. I hit the "reset phone" button hoping it will magically work but after a couple of minutes and a sickening red triangle with an exclamation mark in the middle, it returns to the "your phone is encyrpted" page.
So here I am, pleading for help as its magically only two months outside of warranty and my carrier doesn't want to know me.
Please help!
Thank you in advance
UPDATE
UPDATE:
I have tried going through the htcdev unlock bootloader in the effort to get TWRP and hopefully some success from there but it doesn't seem to finish the unlock process. I get to the last step where I accept the unlock on the phone and it resets back to the same encyrpted/corrupted screen. Using the power and volume down I can see in the boot menu that it is still ***locked***.
Is there ANY other way to unlock bootloader and install TWRP?
same with me
unable to mount anything, cant flash recovery(it flashes, but nothing changes)
cant format, when phone boots it says that "phone is encrypted bla bla bla, reset device just reboots back to twrp)
cant boot into oem rebootRUU, it just reboots phone=(
olvrick said:
device just reboots back to twrp)
Click to expand...
Click to collapse
If you can get into TWRP, that's a good thing. Go to Wipe section, and tap the button "Format Data". This usually fixes the storage corruption issue.
The OP has a different version of this. He doesn't have custom recovery, and in this condition, I don't think you can flash TWRP, anyway. So unlocking the bootloader is probably not going to help matters. Try to RUU, if your version has one.
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
I would fastboot latest factory image.
Just hold vol- when a reboot comes it will go into bootloader.
piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709
piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Just started with me today too.
I cannot get into recovery or boot loader
rebooting using the hard button just brings up this Dump to EXT4 and then into the ROM that is havnig a ish ton of force closes.
My plan is to back up some stuff I need to copy off the phone and then start factory reset from within settings.
EDIT:
I was rooted running stock
All i did was run a backup in TWRP
issues started after reooting.
Once i factory reset and re Root i will see if I can restore backup, maybe
sb1893 said:
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709
Click to expand...
Click to collapse
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!
piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April. How do I revert the bootloader?
Also, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful so far. Thanks!
Click to expand...
Click to collapse
They flashing all the parts of the image manually. Something like this happened to a buddy of mine and using the flash all wouldn't fix. He couldn't get the device to boot until he did all the images manually.
piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!
Click to expand...
Click to collapse
Glad you got it working. I checked and I did link the thread I intended to. Starting at post #57 onward from that thread has the information on how to update to the May update and leverage Chainfire's VerifiedBootSigner.zip.
Thx,
S
Pixel bootloop
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!
rosendomurilo said:
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!
Click to expand...
Click to collapse
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.
Phalanx7621 said:
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.
Click to expand...
Click to collapse
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...
rosendomurilo said:
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...
Click to expand...
Click to collapse
Can you get to recovery ?
Phalanx7621 said:
Can you get to recovery ?
Click to expand...
Click to collapse
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...
rosendomurilo said:
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...
Click to expand...
Click to collapse
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.
Phalanx7621 said:
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.
Click to expand...
Click to collapse
Perfect! Just as I expected... Probably i will do an youtube guide if it works... Thanks bro!
My S7 Active SM-G891a had issues out of nowhere one day and got stuck in the recovery booting boot loop. I couldn't get the stock recovery mode to ever load up, it would always restart or tell me no command even after entering in commands to load the stock recovery mode up. I have tried flashing with a handful of firmwares, the 6.0 firmware just go into a recovery booting boot loop and the 7.0 ones I have tried act like they are going to boot but then get a warning "Security Error: This phone has been flashed with unauthorized software & is locked. With the 7.0 software I can get back into stock recovery mode but still cant actually boot the phone up afterwards. Is there an ATT US firmware that I should be able to use that wont get this message? Also as a note, during the flash, the BL would never flash with any of the firmwares I have downloaded. It was hit or miss if the AP, CP, or CSC would flash without failure. Some would have success on all 3 and others wouldn't. Just trying to get the phone functional again, and not necessarily rooting it or unlocking it. Thanks
I have never heard of that happening. Sounds frustrating sorry.
Try flashing:
https://cloud.mail.ru/public/BGy7/g..._QB17619845_REV02_user_low_ship_MULTI_CERT.7z
With Odin Modified:
https://androidfilehost.com/?fid=24591023225177749
For future reference, when you see the "No Command" screen with a little dead android character, if you hold power while clicking vol up then release recovery should start up. If you are in recovery and don't select "reboot system" then the phone will continually reboot to recovery first stopping at the "No Command" screen. This will happen even if you hard power down the phone until you specify boot to system. This is actually a feature to default you to a recovery position rather than getting stuck in messed up software.
I agree with @ThunderingLight that attempting to flash the Nougat stock ROM is the only way out. This model phone is very locked down, so you are running up against the security features that keep it locked and prevent unauthorized software from being loaded. Overall, that's a good thing for most people, but bad for folks that like to play with their devices.
Good luck