How to fix "Your device is corrupt. It can't be trusted and may not work properly"?
I keep getting this "Your device is corrupt. It can't be trusted and may not work properly" red error when booting up.
Formating data, reflashing OOS, factory reset, etc doesn't get rid of the error either. What can I do? Thanks!
Is it actually working? Is your bootloader unlocked?
If yes to both, that's just the default message you get when your bootloader is unlocked.
hartleyshc said:
Is it actually working? Is your bootloader unlocked?
If yes to both, that's just the default message you get when your bootloader is unlocked.
Click to expand...
Click to collapse
It does boot into the system (with or without Magisk), though I'd have to press power button twice to get past the red "Your device is corrupt" error in order to boot into the system.
Sometimes it boots into the system after double pressing the power button. Sometimes I'd have to force restart the phone.
And even if I `fastboot oem lock`, the red error screen still shows
wongmjane said:
It does boot into the system (with or without Magisk), though I'd have to press power button twice to get past the red "Your device is corrupt" error in order to boot into the system.
Sometimes it boots into the system after double pressing the power button. Sometimes I'd have to force restart the phone.
And even if I `fastboot oem lock`, the red error screen still shows
Click to expand...
Click to collapse
You'll have to go fully back to stock. No root, no TWRP. Flash the full stock rom and then do the fastboot oem lock and the message will go away.
Also you don't have to press the power button twice to by pass it. Just don't press anything and it will go past the screen on its own.
It's press power button once to pause, press again to unpause. If you don't press anything, it will go on its own in a second or two.
hartleyshc said:
If you don't press anything, it will go on its own in a second or two.
Click to expand...
Click to collapse
This red error message occurs after the install of the 9.0.15 Official OOS, and it will not continue boot automatically past the error. It waits about 20 seconds, then reboots to the same error.
If I reboot to recovery, I get the usual orange message that does not use the word "corrupt", and it will boot into TWRP properly after a few seconds, the same way it would boot properly after a few seconds into my previous ROM, 9.0.12. Not the case with this new red error message though--a button must be pressed, then it continues boot into system.
---------- Post added at 07:57 PM ---------- Previous post was at 07:45 PM ----------
wongmjane said:
I keep getting this "Your device is corrupt.
Click to expand...
Click to collapse
hartleyshc said:
Is it actually working? Is your bootloader unlocked?
Click to expand...
Click to collapse
Here's the solution, thanks to @mauronofrio.
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-fix-red-boot-screen-device-t3891479
Related
Ok, I flashed Trinity kernel with no issues, phone booted up ran great. Then I pushed PA to my phone to flash using the Nexus Root Toolkit and when it rebooted me into TWRP, I proceeded to wipe sys and dalvik and try to flash the zip. It failed. No big deal, some of my flashes have failed before on this N7. Not sure why, but I usually just reboot and press on. This time however, as it starts to boot I get a msg saying "unfortunately Setup Wizard has stopped" with an "ok" button, but when I press the "ok" button it just cycles back to the same button. I have tried powering down, but the Ok button sits on top of the power off confirmation button and so I can't even turn it off to reboot into recovery mode. Anyone got any suggestions? The toolkit won't seem to reboot it into recovery either, not sure why unless the ok button is overriding everything. Help?
UPDATE: I managed to get the trick of hitting the ok button fast enough to get to the power confirm button behind it, but when I boot it into recovery mode, I get the droid with the red ! mark and can't seem to get it to do anything else. I have tried booting into recovery from Toolkit, but it says I need to put it into USB debugging mode, which of course I can't do because I can't get past the failed setup...
UPDATE: Ok, I have managed to finagle it into resetting to factory stock ROM. So I have it up and running again and just have to start from scratch. But at least I am able to.
How'd ya do that
Lazarus416 said:
Ok, I flashed Trinity kernel with no issues, phone booted up ran great. Then I pushed PA to my phone to flash using the Nexus Root Toolkit and when it rebooted me into TWRP, I proceeded to wipe sys and dalvik and try to flash the zip. It failed. No big deal, some of my flashes have failed before on this N7. Not sure why, but I usually just reboot and press on. This time however, as it starts to boot I get a msg saying "unfortunately Setup Wizard has stopped" with an "ok" button, but when I press the "ok" button it just cycles back to the same button. I have tried powering down, but the Ok button sits on top of the power off confirmation button and so I can't even turn it off to reboot into recovery mode. Anyone got any suggestions? The toolkit won't seem to reboot it into recovery either, not sure why unless the ok button is overriding everything. Help?
UPDATE: I managed to get the trick of hitting the ok button fast enough to get to the power confirm button behind it, but when I boot it into recovery mode, I get the droid with the red ! mark and can't seem to get it to do anything else. I have tried booting into recovery from Toolkit, but it says I need to put it into USB debugging mode, which of course I can't do because I can't get past the failed setup...
UPDATE: Ok, I have managed to finagle it into resetting to factory stock ROM. So I have it up and running again and just have to start from scratch. But at least I am able to.
Click to expand...
Click to collapse
May I ask how you finagled it into resetting to factory stock ROM? I am having the same issue but not able to get out of the loop
jasonmrouse said:
May I ask how you finagled it into resetting to factory stock ROM? I am having the same issue but not able to get out of the loop
Click to expand...
Click to collapse
Hold all three hardware buttons for 30 seconds and the device reboots to the bootloader. Then, fastboot flash the stock image.
jasonmrouse said:
May I ask how you finagled it into resetting to factory stock ROM? I am having the same issue but not able to get out of the loop
Click to expand...
Click to collapse
You can get to the bootloader (fastboot mode) FROM ANY STATE.
Read that again - from any state.
See "bootloader interrupt" in this thread:
[REF] Nexus 7 Button Combinations
cheers
I recently got the update for 4.4 notification, clicked it but then the installation froze on a picture of android with an exclamation in his belly.
After that I could no longer boot to bootloader or recovery.
I tried fastboot but I cant not install the drivers as I cant boot to bootloader.
So I tried NRT and managed to get my recovery back (TWRP), but still no bootloader.
I have the option to return to stock on NRT but I am afraid it will fail and brick my N7.
I have SuperSU, flashify and TWRP apps running now with TWRP recovery also bootable.
How can I get my bootloader back?
Siddy1200 said:
I recently got the update for 4.4 notification, clicked it but then the installation froze on a picture of android with an exclamation in his belly.
After that I could no longer boot to bootloader or recovery.
I tried fastboot but I cant not install the drivers as I cant boot to bootloader.
So I tried NRT and managed to get my recovery back (TWRP), but still no bootloader.
I have the option to return to stock on NRT but I am afraid it will fail and brick my N7.
I have SuperSU, flashify and TWRP apps running now with TWRP recovery also bootable.
How can I get my bootloader back?
Click to expand...
Click to collapse
Hi, Siddy1200...
If you had no bootloader... nothing would work... at all.
The bootloader underpins everything you do with your Nexus 7. Nothing happens without one... in which case , you'd be effectively HARDBRICKED.
The fact that stuff is working indicates that your bootloader is fine.
To access the bootloader manually... shut down the Nexus 7 completely.
Press and hold the VOL DOWN button...
Whilst holding, press the POWER ON button, for around 5-10 seconds...
You should now boot into the bootloader.
This key press sequence should also work if you CAN'T shut down the Nexus 7 normally... for example, if you're bootlooping. I've had a few scary moments myself in the past, and the VOL DOWN+hold, POWER ON sequence has always thrown me back into the bootloader...
Rgrds,
Ged.
GedBlake said:
Hi, Siddy1200...
If you had no bootloader... nothing would work... at all.
The bootloader underpins everything you do with your Nexus 7. Nothing happens without one... in which case , you'd be effectively HARDBRICKED.
The fact that stuff is working indicates that your bootloader is fine.
To access the bootloader manually... shut down the Nexus 7 completely.
Press and hold the VOL DOWN button...
Whilst holding, press the POWER ON button, for around 5-10 seconds...
You should now boot into the bootloader.
This key press sequence should also work if you CAN'T shut down the Nexus 7 normally... for example, if you're bootlooping. I've had a few scary moments myself in the past, and the VOL DOWN+hold, POWER ON sequence has always thrown me back into the bootloader...
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks for the reply Greg.
I can't boot to boot loader, that means when I power on with vol- pressed, then select boot loader and press power , it doesn't work. The screen flashes for a second and it is back to the previous screen to where I can choose restart, recovery, boot loader,etc.
This also happened with recovery but I fixed it, now I'm trying to fix the bootloader
Siddy1200 said:
Thanks for the reply Greg.
I can't boot to boot loader, that means when I power on with vol- pressed, then select boot loader and press power , it doesn't work. The screen flashes for a second and it is back to the previous screen to where I can choose restart, recovery, boot loader,etc.
This also happened with recovery but I fixed it, now I'm trying to fix the bootloader
Click to expand...
Click to collapse
Apologies, Siddy1200... but I'm a little confused... based upon my reading of your post... I think you're already in the bootloader!!.
"...it is back to the previous screen to where I can choose restart, recovery, boot loader,etc..."
The bootloader features a green android, lying on its back, with it's belly open - some really tiny text at the lower left hand side of the screen giving details about the current bootloader version and it's lock state. At the upper right hand side of the screen, adjacent to the power button, are selectable options via the POWER BUTTON, which can be cycled through with the VOL BUTTONS... and these options are START, RESTART BOOTLOADER, RECOVERY MODE, POWER OFF... and then START again.
Somewhat similar to your above quoted description.
Selecting RESTART BOOTLOADER will just bring you back to where you already are... ie., the BOOTLOADER.
Also, if you can't access the bootloader, how are you managing to boot into TWRP?... as this is normally done via the bootloader... ie, by selecting the RECOVERY MODE option.
Rgrds,
Ged.
GedBlake said:
Apologies, Siddy1200... but I'm a little confused... based upon my reading of your post... I think you're already in the bootloader!!.
"...it is back to the previous screen to where I can choose restart, recovery, boot loader,etc..."
The bootloader features a green android, lying on its back, with it's belly open - some really tiny text at the lower left hand side of the screen giving details about the current bootloader version and it's lock state. At the upper right hand side of the screen, adjacent to the power button, are selectable options via the POWER BUTTON, which can be cycled through with the VOL BUTTONS... and these options are START, RESTART BOOTLOADER, RECOVERY MODE, POWER OFF... and then START again.
Somewhat similar to your above quoted description.
Selecting RESTART BOOTLOADER will just bring you back to where you already are... ie., the BOOTLOADER.
Also, if you can't access the bootloader, how are you managing to boot into TWRP?... as this is normally done via the bootloader... ie, by selecting the RECOVERY MODE option.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks for your persistence Greg, I think I was confused as what the bootloader actually is, now I can see I am already in bootloader :silly:
I will return to stock with NRT and try the 4.4 update now.
So .... I flashed the mantaray-lrx21p image from Nexus Factory Images on my Nexus 10 (16GB Wifi) and now it's stuck in a bootloop.
No problem, I thought, I can get into recovery and fix it, right? Maybe do a wipe and try again? Yeah, not so fast. I get the bootloader screen, but the only option is 'Start' which just boots into the system that bootloops.
That's OK, I'll just use fastboot to wipe it. Nope. Fastboot doesn't detect a device.
I've tried both ADB and fastboot on Mac & Linux. Same issue (neither fastboot nor adb detect a device).
Ideas?
Observations
In case you think I'm just being impatient, it has been doing the boot animation for about 25 minutes now.
It doesn't like to stay off. If I hold the power button for 10 seconds it turns off, but it turns itself back on in about 5 seconds.
If I power it on while holding the volume button closer to the power button, I can get into a half-assed bootloader ... meaning that I can only push the power button again to 'Start'. I cannot cycle through the options with the volume buttons.
During the mentioned (half-assed) bootloader screen, fastboot does not detect a device.
During the boot animation, adb does not detect a device.
copolii said:
So .... I flashed the mantaray-lrx21p image from Nexus Factory Images on my Nexus 10 (16GB Wifi) and now it's stuck in a bootloop.
No problem, I thought, I can get into recovery and fix it, right? Maybe do a wipe and try again? Yeah, not so fast. I get the bootloader screen, but the only option is 'Start' which just boots into the system that bootloops.
That's OK, I'll just use fastboot to wipe it. Nope. Fastboot doesn't detect a device.
I've tried both ADB and fastboot on Mac & Linux. Same issue (neither fastboot nor adb detect a device).
Ideas?
Observations
In case you think I'm just being impatient, it has been doing the boot animation for about 25 minutes now.
It doesn't like to stay off. If I hold the power button for 10 seconds it turns off, but it turns itself back on in about 5 seconds.
If I power it on while holding the volume button closer to the power button, I can get into a half-assed bootloader ... meaning that I can only push the power button again to 'Start'. I cannot cycle through the options with the volume buttons.
During the mentioned (half-assed) bootloader screen, fastboot does not detect a device.
During the boot animation, adb does not detect a device.
Click to expand...
Click to collapse
The reason starts the only option is because your only holding volume up when going into fastboot. Hold power and volume up AND DOWN. All at the same time. Trust me I had the same issue but googling helped me find out you gotta hold both buttons
Sent from my VS980 4G
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
supermamie said:
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
Click to expand...
Click to collapse
I launched a 3rd flash while I downloaded the sdk and this one worked...
Absolutely no idea why.
I finally got it to boot.
boot into bootloader (hold vol-up+vol-down+power)
choose reboot bootloader
choose shutdown
turn it back on
Seems like it needed to be shut completely off not just rebooted after the flash. Perhaps a reboot maintains weird memory fragments or something? Crazy talk, I know.
Edit: you shouldn't have to wait long to see if it works. Mine jumped to the "Upgrading apps ..." screen straight away.
The very first boot on my n7 and n10 took about 20 min, after that they have normal boot time, I believe this may have something to do with encryption but never bothered to check as I just did something else while it booted
Side note, the n9 has an initial boot time of at least 5-10 min (can't recall but it took forever it felt like) and this is optimized hardware for the software so no surprise that there is a huge long boot time on the first go
Also I flashed both manually erasing all partitions first through fastboot then flashing each one individually... Just another side note
supermamie said:
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
I launched a 3rd flash while I downloaded the sdk and this one worked...
Absolutely no idea why.
Click to expand...
Click to collapse
Ive tried to connect to the device in adb, fastboot, I can only get it to adb sideload mode.
Sideloading gives the message Wrong footer instalation aborted.
How did you manage to flash the image? All drivers did install properly it seems.
Boot loop
thedarksavant said:
I finally got it to boot.
The same was happening to me, after unlocking it it began to loop, even after I wipe it was still looping.
I followed your steps of going into reboot recovery then power off. -- issue resolved!!
Thanks!
******
Click to expand...
Click to collapse
"It can't be trusted and my not work properly"
Hi,
I unlocked the bootloader and flashed twrp but can't boot the phone anymore.
It only starts when pressing power button + volume up. Then I get following message two times before I get the third, final message mentioned in the headline:
Code:
Your device has been unlocked and can't be trusted
After that it tells my to press the power button to continue -> phone goes off.
Can't connect to adb shell, so what can I do?
BR
Michael
happyass**** said:
"It can't be trusted and my not work properly"
Hi,
I unlocked the bootloader and flashed twrp but can't boot the phone anymore.
It only starts when pressing power button + volume up. Then I get following message two times before I get the third, final message mentioned in the headline:
Code:
Your device has been unlocked and can't be trusted
After that it tells my to press the power button to continue -> phone goes off.
Can't connect to adb shell, so what can I do?
BR
Michael
Click to expand...
Click to collapse
Can you get into recovery? If so, I would say connect phone in recovery, (will show up on PC as mtp device), then copy anything you don't want to lose. Then do a full wipe, and flash stock rom, or custom rom and see if the message is still there.
Managed to enter recovery for once. Flashed Omnirom but know it stucks at the 'Sony screen'.
Can't get into recovery anymore.
I did it!
It works!
Don't ask me how. Wild keypress combinations and luck.
I think its related to sony drm, you have to flash genesis kernel for it to work well, anyway good luck
i cant do hard reset because i get no command and no recovry mode
any solutions ?
Mayersdz said:
i cant do hard reset because i get no command and no recovry mode
any solutions ?
Click to expand...
Click to collapse
Just press once volume up and power button together when you see the no command
You will get the recovery
I have a nokia 6 1025 (ex-AmazonPrime) flashed via OST with june firmware, and update via sd card recovery with ota updates until december. Then I flashed Oreo Beta in january.
All worked fine.
Now i want to update to Oreo final. The zip is in the SD card, but when i try to put in recovery mode there is only the "no command" message.
I tried to get into recovery with both methods, with volumeup+power keys, and with "adb reboot recovery". Always the same "no command" message
The suggested solution, pressing volumeup and power together does not work.
artigasperez said:
I have a nokia 6 1025 (ex-AmazonPrime) flashed via OST with june firmware, and update via sd card recovery with ota updates until december. Then I flashed Oreo Beta in january.
All worked fine.
Now i want to update to Oreo final. The zip is in the SD card, but when i try to put in recovery mode there is only the "no command" message.
I tried to get into recovery with both methods, with volumeup+power keys, and with "adb reboot recovery". Always the same "no command" message
The suggested solution, pressing volumeup and power together does not work.
Click to expand...
Click to collapse
Try pressing them together few times, its lil tricky
If it still doesn't work, then flash back mena firmware and then update till January patch, then install the final oreo, do not install beta oreo
You forget to press home button.
It should be volumeup+power+home button together.
Alvin Fung said:
You forget to press home button.
It should be volumeup+power+home button together.
Click to expand...
Click to collapse
Yes, i saw situshar answered volumeup+power+home in another thread, and it worked.
Returned here to say thanks and also found your answer.
artigasperez said:
Yes, i saw situshar answered volumeup+power+home in another thread, and it worked.
Returned here to say thanks and also found your answer.
Click to expand...
Click to collapse
Buddy @artigasperez its sltushar, not situshar
No Command screen, what from there?
My Nokia 6 suddenly stopped recognizing my security pattern the other day. I have tried to do the Hard Reset (+ and Power and "home" buttons), and finally managed to get to a screen that read "No Command" and had a little green guy lying on his back. What am I supposed to do from there? I apologize for asking such a basic question, but I am completely lost. Any help is much appreciated. Thanks!
When you at "no command" screen press Volume UP & Power simultaneously, then release Power button to get into recovery menu.
Thank you - how long after you release the Power button do you continue to hold the + button? Nothing happened for the longest time, and then the phone just rebooted (back to the Pattern screen, where it says I'm doing it wrong). I will get it back to "No Command" and try again. I really appreciate your help. (I've tried three times now, same thing happens each time.)
qwertysmerty said:
When you at "no command" screen press Volume UP & Power simultaneously, then release Power button to get into recovery menu.
Click to expand...
Click to collapse
Sorry, stupid me. Press Volume UP & Power simultaneously, then release Volume UP button to get into recovery menu
OK, got it - Wiped data/factory reset & cache partition ... now what? Thanks for the help!
qwertysmerty said:
Sorry, stupid me. Press Volume UP & Power simultaneously, then release Volume UP button to get into recovery menu
Click to expand...
Click to collapse
---------- Post added at 02:06 AM ---------- Previous post was at 01:56 AM ----------
I got it, I believe - at least, I am back to a "Welcome" screen on my phone. Thank you SO MUCH for the help!
heatheranne said:
OK, got it - Wiped data/factory reset & cache partition ... now what? Thanks for the help!
Click to expand...
Click to collapse
I have Wiped data/factory reset & cache partition but still no Command. kindly help
akinpeluvictor said:
I have Wiped data/factory reset & cache partition but still no Command. kindly help
Click to expand...
Click to collapse
What are u trying to do before getting the message?
akinpeluvictor said:
I have Wiped data/factory reset & cache partition but still no Command. kindly help
Click to expand...
Click to collapse
I try to update mu phone to Android 8.0 after that my phone download automatically next security patch.i tap to reboot to install.
But my phone stuck on "no command"
I try to wipe cache and data.but still no command and phone not booting
Only showa Android logo
Please help me
sajjadaf said:
I try to update mu phone to Android 8.0 after that my phone download automatically next security patch.i tap to reboot to install.
But my phone stuck on "no command"
I try to wipe cache and data.but still no command and phone not booting
Only showa Android logo
Please help me
Click to expand...
Click to collapse
Step 1. Plug in a usb charger to the phone, then quickly press vol+ and power button to get into the "No command screen"
Step 2. Again, press the vol+ and power button AND press the HOME button, then you will see the Recovery menu .
See the solution here :good:
Mayersdz said:
i cant do hard reset because i get no command and no recovry mode
any solutions ?
Click to expand...
Click to collapse
Hi based on this how did you sort out the issue. I have a Nokia 6 model TA-1024 it is stuck on the No command screen
---------- Post added at 12:34 PM ---------- Previous post was at 12:21 PM ----------
artigasperez said:
I have a nokia 6 1025 (ex-AmazonPrime) flashed via OST with june firmware, and update via sd card recovery with ota updates until december. Then I flashed Oreo Beta in january.
All worked fine.
Now i want to update to Oreo final. The zip is in the SD card, but when i try to put in recovery mode there is only the "no command" message.
I tried to get into recovery with both methods, with volumeup+power keys, and with "adb reboot recovery". Always the same "no command" message
The suggested solution, pressing volumeup and power together does not work.
Click to expand...
Click to collapse
Hi similar situation here, how did you go about it
sltushar said:
Just press once volume up and power button together when you see the no command
You will get the recovery
Click to expand...
Click to collapse
I have a Samsung galaxy s5, phone keeps rebooting into recovery mode tried wiping cache partition, factory reset all failing to work. now want to install custom firmware but the reboot to bootloader function wont work it quickly flashes a no command screen then goes back to Android recovery screen. How can I get past this?
Flash it thru Odin, whichever is supported right now, then unlock the bootloader for custom roms. If you dont know the process of unlocking bootloader then ask me when you finish installing official firmware via odin
sltushar said:
Flash it thru Odin, whichever is supported right now, then unlock the bootloader for custom roms. If you dont know the process of unlocking bootloader then ask me when you finish installing official firmware via odin
Click to expand...
Click to collapse
Thanks but it wont go into download mode it keeps going back to recovery mode any time I try to go to download mode unless there is another way it am not aware of to flash without going into download mode