I'm stuck in a boot loop. will sometimes come up with a "This device is corrupted and cannot be trusted" error and will ask for a password to start android? Please help can this be fixed? By the way the error message is in orange not sure why
You can try to install the latest factory (which will erase all your data). Otherwise it could be a case for repairing.
cell2011 said:
I'm stuck in a boot loop. will sometimes come up with a "This device is corrupted and cannot be trusted" error and will ask for a password to start android? Please help can this be fixed? By the way the error message is in orange not sure why
Click to expand...
Click to collapse
It will not ask if you not encrypted. Possibly something in your phone was corrupted. Or it will boot or will stuck at Google logo and need to reflash the Factory Image.
Related
Hi
I had stock room+root and got massage about firmware update, I dl it and try to update. My device rebooted and show for few second: secure booting error cause: device unlock!, so boot success! And than entering to the twrp (v2.6.3.0). Now everytime when I tring to power on my g pad happen the same.
Any idea how to repair it? Im stuck. I tryied reinstal rom and done full wipe, but nothink changed.
Sorry for my bad english :/
ekterion said:
Hi
I had stock room+root and got massage about firmware update, I dl it and try to update. My device rebooted and show for few second: secure booting error cause: device unlock!, so boot success! And than entering to the twrp (v2.6.3.0). Now everytime when I tring to power on my g pad happen the same.
Any idea how to repair it? Im stuck. I tryied reinstal rom and done full wipe, but nothink changed.
Sorry for my bad english :/
Click to expand...
Click to collapse
I think that you were not supposed to use TWRP 2.6.3.0. The correct version is 2.6.3.2. Not sure how to fix your current problem, though.
this message is normal to see if you have twrp installed and try to enter recovery or if you have cyanogen mod 11. Also update your twrp with version 2.6.3.2
katsika said:
this message is normal to see if you have twrp installed and try to enter recovery or if you have cyanogen mod 11. Also update your twrp with version 2.6.3.2
Click to expand...
Click to collapse
Except he says he sees the message every time he power's on the phone. Does CM do that?
woody1 said:
Except he says he sees the message every time he power's on the phone. Does CM do that?
Click to expand...
Click to collapse
yes its normal if you have cm11 to see this message everytime you boot the gpad, it just means that loki is working. Now if he has stock rom it isnt normal to see this message except for when he does the button combo to enter recovery.
i want to sell my lg g pro but the problem is that when i power it i get on lg screen "booting error,deveice unlock so booting" and people start to think that the phone have problems so it wont sell!!
i want the message to disappear ,is there any way to do that? if not how can i relock my bootloader to remove the error ?
i used freegee to get to cmwr and twrp
apart from the message the phones works and boots fine 100%
thanks
Restore to stock and this error will disappear! Is not anything to worry about.
hypnz said:
Restore to stock and this error will disappear! Is not anything to worry about.
Click to expand...
Click to collapse
what do you mean restore to stock the rom or the boot loader ?
If you restore to stock will restored and the boot loader.
So I had relocked my phone after using twrp and rooting my phone, than removing root since phone was being slow.
now, I get the message that it cant be trusted, and wont boot...
I go to recover my phone, and the recovery boots straight to error message. so my recovery is gone. Next thing I do, is try to flash the stock image or recovery, cant because its locked, tried to reunlock, says to go into developer mode but cant get into system.
tried RDS lite, get the message it cant boot into fastboot when IT IS in fastboot.
Tried to boot directly into twrp, nothing.
I know im just gonna be told to send it in but im trying to avoid that... please help.
SinXDaemos said:
So I had relocked my phone after using twrp and rooting my phone, than removing root since phone was being slow.
now, I get the message that it cant be trusted, and wont boot...
I go to recover my phone, and the recovery boots straight to error message. so my recovery is gone. Next thing I do, is try to flash the stock image or recovery, cant because its locked, tried to reunlock, says to go into developer mode but cant get into system.
tried RDS lite, get the message it cant boot into fastboot when IT IS in fastboot.
Tried to boot directly into twrp, nothing.
I know im just gonna be told to send it in but im trying to avoid that... please help.
Click to expand...
Click to collapse
fastboot --set-active=other
While in bootloader
The message I get is...
(Bootloader) slot-suffi: not found
Error: device does not support slots
SinXDaemos said:
The message I get is...
(Bootloader) slot-suffi: not found
Error: device does not support slots
Click to expand...
Click to collapse
Try the flash all for your variant in the return to stock thread
Tried that, says my Flash Permission is no, so when i attemp to flash all, it says i dont have permission and to go through settings to unlock bootloader, but i cant access it unless i can log in, lol , its weird
Hey, all.
I have a D855 variant called D855AR distributed only in Argentina. When I try to dd any recovery image for D855 other than the stock one, I invariably get a boot certification verify error when I try to boot into it. I've already tried just about everything I can find by just google. Most troubleshooting for this error revolves around getting the device to boot normally, but I have no problem doing that. My problem is that I can't boot the recovery image I want, in order to install LineageOS.
Does anyone know what I might be missing?
Thanks.
Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.
This is for Google Pixel 2 XL.
SonyXperiaSP said:
Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.
Click to expand...
Click to collapse
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.
Strephon Alkhalikoi said:
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.
Click to expand...
Click to collapse
First of all thank you for the reply. I don't know but I left the phone alone for couple of hours and right before seeing your post got into bootloader by pressing volume down and power key. Tried to flash TWRP and as soon as it flashed I got the exact same error like last time. I will now be following your method and install factory image. "NOT install - TWRP and Install a custom ROM", so I will not be installing TWRP this time.
I will post updates on what goes and hopefully will be able to flash the factory image without errors.
Thank you very much for the help Strephon. Really, really appreciate it. I am now able to boot into the OS and hopefully installing custom rom or rooting afterwards won't be an issue, Again, thank you very much.