Hi, I wanted to root my Nexus 5x. However after I unlock the boot loader (it works fine) but then install twrp recovery and reboot out of it, I get a message that my system is corrupted (not the we can't check for corruption orange one, the red one that tells you it's corrupted and might not boot properly). Is this something normal that happens? Is there something I can do about it? Any help is GREATLY appreciated
Yes the orange text is normal behavior, i believe it happens when you unlock the bootloader, and the red is when you install a custom recovery. When you install the modified boot image, for rooting, i believe it removes the red message.
I only get the orange message here.
Related
I'm asking this for a friend as he has little experience with hacking phones, but did successfully root his Desire.
There is currently no ROM installed because I did a factory reset but didn't install a ROM.
When trying to boot into recovery, it shows the standard HTC screen, after a while I get a black screen with an image of a phone and a red triangle with an exclamation mark in it. So I can't flash a new ROM either.
I can get into the bootloader (where you are given the option to boot into recovery).
What would be the best course of action to fix this problem?
I was thinking flashing a RUU will probably fix it, but does this not require the phone to have a ROM and be booted into it?
My friend's phone somehow got into a reboot cycle. It loads up, launcher starts, notifications start working. Then there is a nullpointer and a core service that is failing to start then it reboots.
So as a solution I thought try wiping data/cache. When booting the bootloader it was already unlocked - not sure if we did that a while ago or what. So going into recovery, trying the data wipe, it says success and then when I start the phone it is the same, no data is gone, apps are there, reboot problem continues.
So next step, try flashing the os. I downloaded the most recent yakju build, jwr66y. My bootloader version is PRIMELA03 and the build comes with MD04, so I try:
fastboot flash bootloader <bootloader_img>
And it reports success, everything looks fine. So I reboot the bootloader and it says BOOTLOADER VERSION - PRIMELA03.
Try fastboot oem lock, says locked. Reboot, UNLOCKED. Tried flashing the bootloader and the main img with and without restarting but always get the error:
Device version-bootloader is 'PRIMELA03'.
Update requires 'PRIMEMD04'.
when trying to flash the stock rom.
I also can't boot the stock image via 'fastboot boot'. It looks successful up until it says booting and goes to the Google screen with the padlock at the bottom and just hangs.
If I try using adb sideload to push the stock update, it says verifying, then aborts.
I also tried flashing the recovery with a cwm recovery but the same problem - it says writing, OKAY, no error message, everything looks fine, then boot recovery and it's the stock recovery.
What it looks like to me is that the bootloader and possibly the entire system is failing to write to the system flash but for some reason thinks it's succeeding. How is this possible? Is the flash dead? Am I missing something basic? I haven't rooted a phone in a couple years so it's quite possible I'm just missing a step.
Thanks in advance for any advice.
I just tried flashing an older stock (imm76i), starting by flashing the radio, but again the radio flash looks successful but the kernel won't flash because it complains about an out of date baseband and sure enough, the old one is still the one it's reporting, not the one just flashed.
tried fastboot erase system and fastboot erase recovery. Both report success but recovery boots as normal and system boots as normal (still in a reboot cycle).
I should also mention, that after the system boots, there is enough time to uninstall an app. It says successfully uninstalled, but after a reboot, the app is still there (this was the first attempt to stop the reboot cycle as a custom keyboard app was suspected). But again, the changes to flash seem to not be sticking.
Hi,
Have you resolved the problem? I'm in the same situation and I don't know what to do to stop the continuous reboot. I've already tried to flash a stock 4.3 factory image, erase the user data or only unlock the bootloader but nothing works. I'm running Android 4.3 stock without root and my bootloader is locked.
thank you in advance.
Last night I had a secure boot error after I tried flashing a custom kernel over a new ROM* I also just flashed.
The ROM came pre-rooted so I downloaded freegee and tried to unlock it, but no "unlock" option; all it showed was "re-lock (restore efs)". So i assumed it was safe to flash and viola! Secure Boot Error!
I wrestled with it for about an hour, looking for a way to revive my OG without losing all my data, and I had the problem of a faulty power button. I tried VUp+VDown+Power which only turned off my device, I tried VDown+Power which put me in hard reset mode, then something interesting happened. I tried VUp+Power which after a few seconds my OG's screen flashed twich and the error message now read:
Secure Boot Error
Cause: Device unLock!! so Boot successful!
from:
Secure Boot Error
Cause: boot certification verify
The new message only shows when I reboot into recovery though, when I turn off my phone then turn on or reboot, it boots like normal.
Anyone have any idea what this is, what it means or if it means my bootloader is unlocked or not?
Decided to post it here in General since I thought this is a matter of general interest and I'm not asking for help/troubleshooting, just asking a simple question.
hi
i have canadian htc m8. i have the phone is encrypted error. when i boot into recovery its a black screen and reboots phones
when i try to unlock bootloader to put custom recovery , i get to message where it says Yes/no i hit yes goes to black screen and reboots and goes back to your phone is encrypted error. when i go to hboot again it says locked.
basically i need a way to install recovery. when i put command to boot into recovery or flash fastboot gives remote error because bootloader isnt unlocked
please help
techknewz1 said:
hi i
have canadian htc m8. i have the phone is encrypted error. when i boot into recovery its a black screen and reboots phones
when I try to unlock the bootloader to put custom recovery, I get to message where it says Yes/no I hit yes goes to black screen and reboots and goes back to your phone is encrypted error. when I go to hboot again it says locked.
basically, i need a way to install recovery. when I put command to boot into recovery or flash fastboot gives a remote error because bootloader isn't unlocked
please help
Click to expand...
Click to collapse
hi there I was wondering if you resolved this by any chance as I have the exact same problem
So far, I decided since my tablet was running slower than it did when I first got it, to reset it. And since I was doing that, might as well unlock the bootloader.
Well, I unlocked the device, attempted to install TWRP, then got the remote failed error, unknown command. Apparently you have to install it via flashify or whatever. Anyhow...
I rebooted the device, but now, all it does is go into recovery, shows the android robot on its side for a split second, then starts flashing white then black on the screen. The only way to stop it is to pull off the battery connector.
The LG mobile tool can see it in download mode, send it the latest kdz image or whatever, works, but still goes back to the same error - boots to recovery then hangs.
Is there a way to fix this? Trying to get it to boot a recovery img didn't work. Erasing all data seemed to have done nothing.
Did you ever unbrick it...?