Develop Bugs

[Q] Secure booting Error! after official update - TWRP installed

This morning my LG V500 offered a software update. I started the update process without thinking. When the tablet restarted to install the update I saw the LG logo and then was greeted with the following message on the screen:
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
...after which I end up at the TWRP screen.
This happens every time I restart the tablet.
Before the update, I had Android 4.2.2 installed with kernel v3.4.0. I had installed TWRP v2.6.3.1 to root my phone. I have NO custom ROMs installed.
I'd prefer not to restart from scratch, but I guess that I can do a Factory Reset, Advanced Wipe or Format Data from TWRP to restore functionality to my tablet.
Any ideas on how I can avoid losing all my customizations?

Cal_ab said:
This morning my LG V500 offered a software update. I started the update process without thinking. When the tablet restarted to install the update I saw the LG logo and then was greeted with the following message on the screen:
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
...after which I end up at the TWRP screen.
This happens every time I restart the tablet.
Before the update, I had Android 4.2.2 installed with kernel v3.4.0. I had installed TWRP v2.6.3.1 to root my phone. I have NO custom ROMs installed.
I'd prefer not to restart from scratch, but I guess that I can do a Factory Reset, Advanced Wipe or Format Data from TWRP to restore functionality to my tablet.
Any ideas on how I can avoid losing all my customizations?
Click to expand...
Click to collapse
What all have you tried?
A simple shut down and re-start possibly could fix it. Just a guess, but worth a try. You should update to TWRP's latest also.

same problem here
Same problem as original poster, just I was on 2.7.0.0 TWRP. Upgraded to 2.7.0.1 - same problem.
Restored from previous TWRP backup - same problem. Installed custom ROM - SAME PROBLEM!
Out of options at this point. HELP!

g---man said:
Same problem as original poster, just I was on 2.7.0.0 TWRP. Upgraded to 2.7.0.1 - same problem.
Restored from previous TWRP backup - same problem. Installed custom ROM - SAME PROBLEM!
Out of options at this point. HELP!
Click to expand...
Click to collapse
Ever since I rooted I've had that. In fact if you watch Ytube's video about rooting an LG G Tab, you will see guy say "Don't know what that is - but all works.
Now on a transformer101 I didn't see that.
But frankly, so what? You don't go to recovery that much -- that is the only time it shows.

Cal-123 said:
Ever since I rooted I've had that. In fact if you watch Ytube's video about rooting an LG G Tab, you will see guy say "Don't know what that is - but all works.
Now on a transformer101 I didn't see that.
But frankly, so what? You don't go to recovery that much -- that is the only time it shows.
Click to expand...
Click to collapse
Cal-123 - issue here is not just information message, but boot loop. No matter what I tried - it goes to main TWRP screen.
Looks like solution is here: http://forum.xda-developers.com/showthread.php?t=2622034&page=2 , will post update when done

Cal_ab said:
This morning my LG V500 offered a software update. I started the update process without thinking. When the tablet restarted to install the update I saw the LG logo and then was greeted with the following message on the screen:
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
Click to expand...
Click to collapse
I did a recovery with the LG tools. All my data was backed up so it wasn't a huge deal for me. I can't even remember why I rooted my GPad in the first place.

g---man said:
Cal-123 - issue here is not just information message, but boot loop. No matter what I tried - it goes to main TWRP screen.
Looks like solution is here: http://forum.xda-developers.com/showthread.php?t=2622034&page=2 , will post update when done
Click to expand...
Click to collapse
I Hope you worked things out, but your problem possibly could be that some Roms have a built-in recovery option - by that, I mean instead of just rebooting, they will boot into recovery. You might ck. that to see if it is enabled. This "SlimKat" ROM has the feature.
Good luck!

Cal-123 said:
I Hope you worked things out, but your problem possibly could be that some Roms have a built-in recovery option - by that, I mean instead of just rebooting, they will boot into recovery. You might ck. that to see if it is enabled. This "SlimKat" ROM has the feature.
Good luck!
Click to expand...
Click to collapse
Cal-123, thanks, I was restoring backup done with TWRP - same problem (rebooting to TWRP screen, not to system). Still don't know root cause, but problem was resolved by flashing stock KK update by using B2CApp. Obviously root is gone, so back to reading forum
At least can play Deer Hunter again
Cheers!

After successful (?) upgrade to MM, can't boot past Verizon screen.

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.

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

bricked nexus 5x out of nowhere

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

various issues with google variant

I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?

I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.

stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:

I agree. I got it used tho which is an issue.

Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.

stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.

Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.

Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?

stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.

Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.

I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.

MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:

stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.

smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.