Database Users

Stuck on Encryption Unsuccessful

I apologize if this is in the wrong section this is my first time posting to xda
I tried rooting my tmobile LG V20 and cant seem to get into TWRP. Every time i boot up it goes to screen that says
"your device software cannot be checked for corruption. Lock the bootloader"
then it boots to a white screen that says Encryption Unsuccessful with a reset button at the bottom. I am unable to get into twrp with the power and volume down button.

epr2175 said:
I apologize if this is in the wrong section this is my first time posting to xda
I tried rooting my tmobile LG V20 and cant seem to get into TWRP. Every time i boot up it goes to screen that says
"your device software cannot be checked for corruption. Lock the bootloader"
then it boots to a white screen that says Encryption Unsuccessful with a reset button at the bottom. I am unable to get into twrp with the power and volume down button.
Click to expand...
Click to collapse
There is another thread around here that answers your problem. I had the same issue. Something along the lines of plug in phone and open command prompt with command : and reboot bootloader and reboot phone. When you see twrp booting and installing files hit enter and you should boot into twrp again.
I tried it about 35-40 times and failed. It finally worked after many tries. Look for the thread around here somewhere though.
---------- Post added at 04:42 AM ---------- Previous post was at 04:38 AM ----------
Found it, its under questions and answers. The title is "hi guys my tmobile is stuck in bootloop"

Happed to me too. Turn off tne phone hold vol down plug in phone that will get you into bootloader lock it then unlock it again. Mine booted right up after that.
Sent from my LG-H918 using XDA-Developers mobile app

Also stuck at the same page with the reset button please help

Locking/Unlocking Bootloader Works!!
Thank You!!! You finally got my phone to work after trying for a few days! :laugh:

jjr3211 said:
Happed to me too. Turn off tne phone hold vol down plug in phone that will get you into bootloader lock it then unlock it again. Mine booted right up after that.
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you for this tips, i Lock the bootloader and then Unlock it again as your command, and viola my phone back to life haha

The reason locking / unlocking your bootloader worked is because that formats data. If you would have formatted data in TWRP (NOT wipe -- FORMAT), then your problem would have been solved.
You got lucky, and OEM Unlock was still enabled in developer options. If it hadn't been, then you would have locked your bootloader and wouldn't have been able to unlock it.
-- Brian

runningnak3d said:
The reason locking / unlocking your bootloader worked is because that formats data. If you would have formatted data in TWRP (NOT wipe -- FORMAT), then your problem would have been solved.
You got lucky, and OEM Unlock was still enabled in developer options. If it hadn't been, then you would have locked your bootloader and wouldn't have been able to unlock it.
-- Brian
Click to expand...
Click to collapse
still have issue, i can't install ane apps now.. how to solve it please ?

jjr3211 said:
Happed to me too. Turn off tne phone hold vol down plug in phone that will get you into bootloader lock it then unlock it again. Mine booted right up after that.
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
You saved the day my friend! Locking and unlocking via fastboot did the trick. Phone booted right up.

runningnak3d said:
The reason locking / unlocking your bootloader worked is because that formats data. If you would have formatted data in TWRP (NOT wipe -- FORMAT), then your problem would have been solved.
You got lucky, and OEM Unlock was still enabled in developer options. If it hadn't been, then you would have locked your bootloader and wouldn't have been able to unlock it.
-- Brian
Click to expand...
Click to collapse
Okay - I have this too now. I have a h910 that I just followed runningnak3d's dirty santa guide on. Been flashing all around the last 2 weeks - learning a lot along the way. But today I flashed back to stock 10r. I fomatted data in TWRP - typed yes etc and it just reboots to that. I went to TWRP and installed Alpha Omega Oreo - same error. Restored one of my backups of Lineage I get the same error. So what is the right way out of this problem?
KDZ back and follow your dirty santa guide to re/unlock the bootloader? (I sure hope Brian is still around reading these) Not to screw up the terminology - but if TWRP still boots as my recovery - doesn't that mean my bootloader is unlocked.?

Well - not sure what I was doing yesterday... But wiped all, format data and factory reset in TWRP this morning and flashed h910 10r and then Magisk v20.4 and it worked. Could it be as simple as forgetting to flash Magisk? Maybe that is all that was wrong?
Thanks for reading.

Well if you find yourself in this same sticky spot - check out this here
I flashed 2018-04-15 level and my restore worked without issue.
YMMV
Good Luck

I formatted data in twrp. No change

The correct answer is to downgrade twrp, at least only that fixed it for me.

LG H918 V20 Hard Brick - Dirty Santa

Got a new V20, but it's been hard bricked after running step 3 of the Dirtysanta patch.
Before running Dirtysanta, I did unlock the bootloader by rebooting into fastboot and running
Code:
fastboot oem unlock
I verified it was unlocked through fastboot.
In order to install TWRP, I started Dirtysanta from the top. It seemed to be going successfully until I ran step3.bat to reboot the phone.
The screen only comes to life when taking out the battery completely and plugging it in. It brings up a no battery warning screen.
If the power button is pressed, the phone vibrates but the screen remains off. Same with pressing vol. down + power while trying to get into recovery mode.
Holding vol. up and plugging in the USB to get to download mode hasn't worked. I don't know what else to do.
edit: one other person in the dirtysanta thread has indicated he had the same problem. seems that dirtysanta completely bricks T-Mobile V20s. welp.

mocklee said:
Got a new V20, but it's been hard bricked after running step 3 of the Dirtysanta patch.
Before running Dirtysanta, I did unlock the bootloader by rebooting into fastboot and running
Code:
fastboot oem unlock
I verified it was unlocked through fastboot.
In order to install TWRP, I started Dirtysanta from the top. It seemed to be going successfully until I ran step3.bat to reboot the phone.
The screen only comes to life when taking out the battery completely and plugging it in. It brings up a no battery warning screen.
If the power button is pressed, the phone vibrates but the screen remains off. Same with pressing vol. down + power while trying to get into recovery mode.
Holding vol. up and plugging in the USB to get to download mode hasn't worked. I don't know what else to do.
edit: one other person in the dirtysanta thread has indicated he had the same problem. seems that dirtysanta completely bricks T-Mobile V20s. welp.
Click to expand...
Click to collapse
Yes dirtysanta completely bricks tmo devices. THATS WHY ITS NOT SUPPORTED There is no way to fix. take the insurance loss and get it replaced.

Then which is the best way to root for TMO?

suaverc118 said:
Then which is the best way to root for TMO?
Click to expand...
Click to collapse
https://forum.xda-developers.com/v20/development/lg-h918-t-mobile-one-click-recowvery-t3491969

suaverc118 said:
Then which is the best way to root for TMO?
Click to expand...
Click to collapse
As jerry has linked you. The one that specifically states its for tmo

Appreciate y'all fellas

me2151 said:
As jerry has linked you. The one that specifically states its for tmo
Click to expand...
Click to collapse
Is there anyway to revive a v20 tmo that is hard bricked ? I mean literally no power on. Even computer just makes a buzzer sound like I lost at a spelling bee sound when I connect the phone to it. I was attempting to flash older fw with cracked v20 lgup tool. Any advice? I think it's just a Frisbee now :crying:

LG-h918 bricked with old 9008 loader
I am trying to unbrick an LG-h918 using QFIL and I keep getting sahara fail. I am open to ANY options to unbrick this device!not just QFIL. Any help would be greatly appreciated

jevans85 said:
I am trying to unbrick an LG-h918 using QFIL and I keep getting sahara fail. I am open to ANY options to unbrick this device!not just QFIL. Any help would be greatly appreciated
Click to expand...
Click to collapse
There are 0, an h918 in 9008/EDL mode is DONE. The firehose that leaked for the other models of v20 won't work for it (can't remember if its an arb check, the differing firmware signature, or both,, its talked about somewhere in the firehose/9008 test point thread). If you don't at least have download mode or twrp there's nothing to be done for it without sending it LG and paying them (if they bother to dig out their copy of the firehose or just replace the board or just tell you sorry, idk, but they're the only ones who might be able to do anything)

Nexus 6P - the locked bootloader and bootloop paradox

Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards

robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
Super easy to fix.
Download the newest Full OTA image for angler: https://developers.google.com/android/ota
Then reboot to recovery by holding VOL-DOWN and powering on, then selecting recovery from the boot menu. Then choose "Apply Update from ADB", and use adb sideload /path/to/filenameofotaimage.zip to revive it.

Hey!
Thanks for your fast reply and your helpful tone.
However, when I choose Recovery mode it once again stucks in bootloop resulting in me never accessing recovery mode

npjohnson said:
Super easy to fix.
Download the newest Full OTA image for angler: https://developers.google.com/android/ota
Then reboot to recovery by holding VOL-DOWN and powering on, then selecting recovery from the boot menu. Then choose "Apply Update from ADB", and use adb sideload /path/to/filenameofotaimage.zip to revive it.
Click to expand...
Click to collapse
I am not sure my first reply was sent (having an unstable connection) so trying again:
When in bootloader and pressing recovery mode it goes straight back to bootloop. Hence, I cannot access recovery mode. Feels like a catch-22.

robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
maybe if you posted it in the correct forum, you would get an answer...

Moved to the correct board...

If you can't boot the phone and you can't boot to recovery and Android debugging and oem unlocking are not enabled, there isn't much (read anything) you can do. Maybe take it to a local repair shop and see if they can replace the motherboard for you.

robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6p/general/confirmed-hardware-defects-nexus-6p-t3610405
Heating the phone temporarily boots the phone. (You can also check videos for saving data in bootlooped LG phones)

Factory Reset my Magisk root device now its bricked

i factory reset my device and now it says "official released binaries only " in red and it wont boot at all. idk what to do.. i dont know how to force it to go into download mode i tried plugging it into the computer but it doesn't help. it just keeps restarting over and over again i only see the Samsung S10+ with the Yellow Triangle logo with that message at the top then it reboots. " anyone got any ideas how i can fix this there isn't a samsung store near me. if i plug-in the device into the computer it just keeps rebooting to the samsung s10 screen with the yellow triangle saying at the top in red "Only Official released binaries are allowed to be flashed" my issue is that i can't get the phone into download mode i tried holding down Bixby volume down power then plugin the usb cable. and even bixby volume up and power . it just keeps rebooting itself (sm-G975F)

have a quick look at this thread..... you should be able to boot into download mode, make sure u have the drivers for your phone installed on your pc. you will need to flash another firmware via odin (id recommend stock firmware to get you back on track )
https://forum.xda-developers.com/galaxy-note-9/help/official-released-binaries-allowed-to-t3893592

100000x likes.. you saved me bro.
volume down + bixby that was the magic key's to get back into download mode. i am flashing the firmware now. thank you again. i couldn't figure it out and i was going nuts .

? glad to help

meddylad said:
? glad to help
Click to expand...
Click to collapse
i lost oem unlock so i changed the date to may 1st and it showed up. but now how do i get it back to grayed out.. because when it needs internet it changes the date back to. todays date. got any ideas.
edit: when i reset up the phone after i checked oem unlock i put the the date for 10 days ago. so that the unlock stayed. anyways thanks again @meddylad

I think you have no choice but to wait the 7 days (think its a knox issue)... you could turn off auto time sync but that messes up other apps.
maybe someone else might have a workaround so hold tight

meddylad said:
I think you have no choice but to wait the 7 days (think its a knox issue)... you could turn off auto time sync but that messes up other apps.
maybe someone else might have a workaround so hold tight
Click to expand...
Click to collapse
I turned off auto time . And got OEM unlock then unlocked it and re installed magisk then for the final setup I put the auto time.
Question are you on asd6 or asd4 firmware?

rp4k said:
I turned off auto time . And got OEM unlock then unlocked it and re installed magisk then for the final setup I put the auto time.
Question are you on asd6 or asd4 firmware?
Click to expand...
Click to collapse
Personally I don't known an S10. However, from what I know, Samsung incorporated a fastboot-like feature. In Download Mode, when you press Up, it asks you to factory reset to unlock your bootloader. You might need to relock it (if you come from pure stock), wait the 7 days, and unlock it again.
"Only official binaries can be flashed" is due to RMM state changing to Prenormal. It happens on a factory reset. To prevent it, you need to patch it through TWRP. If you can on the S10 I don't know, but patching RMM will prevent this warning. It's basically meaning OEM Unlock is back on.

Visera said:
Personally I don't known an S10. However, from what I know, Samsung incorporated a fastboot-like feature. In Download Mode, when you press Up, it asks you to factory reset to unlock your bootloader. You might need to relock it (if you come from pure stock), wait the 7 days, and unlock it again.
"Only official binaries can be flashed" is due to RMM state changing to Prenormal. It happens on a factory reset. To prevent it, you need to patch it through TWRP. If you can on the S10 I don't know, but patching RMM will prevent this warning. It's basically meaning OEM Unlock is back on.
Click to expand...
Click to collapse
There isn't a patch for it yet on s10 because it's not possible because of how the partitions are setup. I already fixed my device already and like I stated in the lost before
You can bypass the 7 day wait.
First boot of new firmware have no internet or sim and set the date to 7 or 10 days before. Then once in the os do the developer mode unlock and click OEM unlock. Then go into download to unlock it fully then When the phone reboots to erase all data set it again to the same date . But this time once your In the OS you enable wifi but disable automatically time and date and set it to the same date as before. And OEM unlock will be grayed out. Then reboot to Download mode and flash the patched .tar from magisk. Once that finishes reboot to stock recovery do a factory wipe. Then reboot with volume+ Bixby, power to get into magisk image of os. And you will have the unlocked bootloader . But the OEM won't be grayed but it will be active.

rp4k said:
There isn't a patch for it yet on s10 because it's not possible because of how the partitions are setup. I already fixed my device already and like I stated in the lost before
You can bypass the 7 day wait.
First boot of new firmware have no internet or sim and set the date to 7 or 10 days before. Then once in the os do the developer mode unlock and click OEM unlock. Then go into download to unlock it fully then When the phone reboots to erase all data set it again to the same date . But this time once your In the OS you enable wifi but disable automatically time and date and set it to the same date as before. And OEM unlock will be grayed out. Then reboot to Download mode and flash the patched .tar from magisk. Once that finishes reboot to stock recovery do a factory wipe. Then reboot with volume+ Bixby, power to get into magisk image of os. And you will have the unlocked bootloader . But the OEM won't be grayed but it will be active.
Click to expand...
Click to collapse
Yeah, the same trick used to work on the older phones with the OEM unlock bug. No longer works, however RMM patching fixes it. I'm sure it'll be the same as S9. S10 has the same partitions, same OneUI, simular pie vendor, all that magic. Won't take long hopefully, S9/S10 are both Treble enabled and A - only.
edit: Read S10 isn't as simular. I'm tired.

Visera said:
Yeah, the same trick used to work on the older phones with the OEM unlock bug. No longer works, however RMM patching fixes it. I'm sure it'll be the same as S9. S10 has the same partitions, same OneUI, simular pie vendor, all that magic. Won't take long hopefully, S9/S10 are both Treble enabled and A - only.
edit: Read S10 isn't as simular. I'm tired.
Click to expand...
Click to collapse
Well this trick works fine on the s10.

Bootlooped Pixel 4 (locked Bootloader, can launch bootloader menu)

I have a Pixel 4 that failed to update.
I have not made any modifications to this device and was using it in its stock environment, I guess that the battery ran out during the update.
The device is in a bootloop state and I can invoke the bootloader menu, but the bootloader is locked and the fastboot command is not available.
Recovery appears to be corrupted and when I try to open recovery get a bootloop.
For these reasons, neither the method of using the fastboot command nor the method of using adb sideload
to perform an OTA update can be used.
Below is the device information.
Product revision: flame MP1.0(JPN)
Bootloader version: c2f2-0.3-7376653
Baseband version: g8150-00088-210507-B-7345963
I realize that this device is usually a non-recoverable scenario, but I would like to know if there is a way to recover it.
Appreciate all support and suggestions. Thanks.

The only thing you might try is select Rescue Mode from the bootloader menu, then try the Pixel Repair Tool. However, I believe this depends on working recovery, so it's very possible you are out of options - the device is not recoverable.

Thanks for the reply.
My Pixel does not allow me to start Rescue Mode and when I try to start Rescue Mode/Recovery Mode from the menu, it goes back to bootloop.
I contacted Google Support yesterday and they told me to force reboot the device 7 times, which I did and the no Commands screen appeared. However, I release the button at the wrong time, it goes back to the boot loop.
Also,it is difficult to distinguish between the boot loop and the forced restart by the button, and I have not been able to reproduce it since then.
However, does the fact that the no Commands screen appears mean that recovery is partially working?
I would appreciate your findings.
Thanks again for your reply.

did u solve this?
if u want, u can send me a DM

Khanov said:
did u solve this?
if u want, u can send me a DM
Click to expand...
Click to collapse
Sorry for the delay in replying.
The problem has not been resolved, I will send you a DM.