Hi there:
So, I've decided to unroot and relock my Xoom 4G, in anticipation of the official JB release. When I lock the bootloader (fastboot oem lock), the device locks, reboots, then comes up with the "Failed image SOS 0x0002" error. If I then unlock the bootloader, it boots into Honeycomb just fine.
Now, I'm assuming that I need my bootloader locked to do the upgrade, because there is a small update I'm notified on (HLK75F), and when I try to install it, the devices reboots, and I get the yellow bang and can go no further until a hard reset.
So, I can't boot with locked bootloader; can't do updates with an unlocked bootloader.
Can anyone advise?
Thanks!
shmengie said:
Hi there:
So, I've decided to unroot and relock my Xoom 4G, in anticipation of the official JB release. When I lock the bootloader (fastboot oem lock), the device locks, reboots, then comes up with the "Failed image SOS 0x0002" error. If I then unlock the bootloader, it boots into Honeycomb just fine.
Now, I'm assuming that I need my bootloader locked to do the upgrade, because there is a small update I'm notified on (HLK75F), and when I try to install it, the devices reboots, and I get the yellow bang and can go no further until a hard reset.
So, I can't boot with locked bootloader; can't do updates with an unlocked bootloader.
Can anyone advise?
Thanks!
Click to expand...
Click to collapse
You can do updates with an unlocked bootloader as long as it is stock. The lock doesn't have anything to do with that.
However: The fact that it can't boot when locked suggests that your not back to 100% stock. Re-download images for your Xoom from http://developer.motorola.com/products/software/ and re-flash them.
airesch said:
The fact that it can't boot when locked suggests that your not back to 100% stock.
Click to expand...
Click to collapse
Incorrect. If you've been running with your bootloader unlocked, then decide to lock it, 99% of the time it won't boot, even if you're running 100% stock. For example, if you're on stock 4.0.4 with an unlocked bootloader, then decide to re-lock it, it won't boot. If your bootloader is unlocked, the only way your Xoom will boot after locking it is to install one of the firmware packages listed for your device at http://developer.motorola.com/xoomsoftware, as you correctly pointed out. Once you flash those images with fastboot, you can then lock your bootloader and it will boot. Once it boots, just keep applying the system updates as it prompts you and eventually you'll end up on the latest version available for your device.
oldblue910 said:
Incorrect. If you've been running with your bootloader unlocked, then decide to lock it, 99% of the time it won't boot, even if you're running 100% stock. For example, if you're on stock 4.0.4 with an unlocked bootloader, then decide to re-lock it, it won't boot. If your bootloader is unlocked, the only way your Xoom will boot after locking it is to install one of the firmware packages listed for your device at http://developer.motorola.com/xoomsoftware, as you correctly pointed out. Once you flash those images with fastboot, you can then lock your bootloader and it will boot. Once it boots, just keep applying the system updates as it prompts you and eventually you'll end up on the latest version available for your device.
Click to expand...
Click to collapse
The cause of that 99% is because rooting the Xoom also changes the boot image (to set certain parameters,) and unless you have the clean boot image (of the right version that your updates are at,) it's not 100% stock. Even then, sometimes the rooting process (or if you have also installed busybox and not uninstalled it,) can update timestamps on folders in the system image which will foul up the checksums. I have restored a nandroid of my stock installs, re-flashed the boot and recovery to the right versions, and had it relock successfully several times. The trick is to have those images so all the checksums line up.
Lesson here: If it won't boot when locked, then it wasn't exatcly 100%.
Thanks, guys. I will try redownloading the img files and go through the fastboot commands again.
airesch said:
Lesson here: If it won't boot when locked, then it wasn't exatcly 100%.
Click to expand...
Click to collapse
False. Run unrooted pure stock 4.0.4 on an unlocked bootloader. After that, lock your bootloader and watch what happens.
Also, rooting only modifies your boot image if you use one of those pointless universal root methods. If you simply unlock, flash a mod recovery, and flash the Superuser ZIP from androidsu.com, it leaves the boot image untouched. An insecure boot image is only needed if you want root access in ADB, which 99% of rooted users couldn't care less about.
Sent from my Nexus S using Tapatalk 2
I ran fastboot oem unlock and it rebooted like normal after wiping. Now I am trying to return to stock and anytime I attempt to flash anything it just tells me flash failed due to device not being unlocked. What's going on?
I attempted to relock it and re unlock it but that hasn't seemed to work.
I was installed with Twrp and had rooted my oneplus 3.
I unticked root access in supersu.
Booted to bootloader and typed on my pc in command prompt ,"Fastboot oem lock"
This gave a confirmation on my device,I confirmed locking.
And after that my device did not booted up.I managed to get in bootloader again as I was not even able to open the recovery and unlocked the bootloader once again by this my device booted up.
I flashed stock recovery and repeated the relocking process,this time I was able to open recovery also but no able to boot up.
I again unlocked the bootloader and installed twrp back turned my device up.
Then I unchecked oem unlocking under developer options.
Relocked the bootloader once again.
And now I am stuck at bootloader,not able to unlock it even this time as I turned off oem unlocking.
Now I can only open bootloader.
Please help!
hchawla98 said:
I was installed with Twrp and had rooted my oneplus 3.
I unticked root access in supersu.
Booted to bootloader and typed on my pc in command prompt ,"Fastboot oem lock"
This gave a confirmation on my device,I confirmed locking.
And after that my device did not booted up.I managed to get in bootloader again as I was not even able to open the recovery and unlocked the bootloader once again by this my device booted up.
I flashed stock recovery and repeated the relocking process,this time I was able to open recovery also but no able to boot up.
I again unlocked the bootloader and installed twrp back turned my device up.
Then I unchecked oem unlocking under developer options.
Relocked the bootloader once again.
And now I am stuck at bootloader,not able to unlock it even this time as I turned off oem unlocking.
Now I can only open bootloader.
Please help!
Click to expand...
Click to collapse
OEM locking a bootloader on a phone that was rooted is a big mistake.
You'll need to flash stock recovery, then flash the stock ROM via adb sideload.
Can be done with this tool http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Thanks for reply
Newyork! said:
OEM locking a bootloader on a phone that was rooted is a big mistake.
You'll need to flash stock recovery, then flash the stock ROM via adb sideload.
Can be done with this tool http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Click to expand...
Click to collapse
with that tool I was only able to wipe cache.
Nothing else is working
It says failed
hchawla98 said:
with that tool I was only able to wipe cache.
Nothing else is working
It says failed
Click to expand...
Click to collapse
Can you access stock recovery?
NO
Newyork! said:
Can you access stock recovery?
Click to expand...
Click to collapse
I can't access it as I am installed with TWRP Recovery as it is also not starting.
This is the case, I have a problem with the Flash ROM, now the phone can go into fastboot, but there is no Recovery, and the phone's bootloader is locked.
You're going to have to give a bit more detail if you want help from this community.
For example:
What phone variant do you have?
What did you have on your phone when it was running properly? i.e stock android, locked bootloader, rooted etc.
What 'Flash ROM" do you mean a factory image or custom ROM?
What had been trying to do to your phone i.e upgrade from Android 9 to 10 by sideloading an image?
Had you previously unlocked the bootloader?
I'm not saying that I will ultimately be able to resolve your issues but the more info you give the more likely someone here will.
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
I used to unlock the bootloader, it is because I locked the bootloader that this situation has occurred.
Can you unlock the bootloader again in fastboot?
wangdaning said:
Can you unlock the bootloader again in fastboot?
Click to expand...
Click to collapse
When I lock my devices bootload,then this devices auto wipe data, so I think oem unlock is not open.And I can not unlock bootload.
I have a phone (Moto G8), I wanted to get rid of TWRP and I thought that just locking the bootloader will do it.
I only after saw that if you lock the bootloader with TWRP flashed you get into a boot-loop.
I found out that I can only use "fastboot boot" to boot into stuff because of the error stating: "Your device is corrupt. It can't be trusted and will not boot.".
Even if I go into the recovery mode the same error message would appear.
I know that by unlocking the bootloader I could get rid of that error but I don't have an unlocked bootloader and,
as most of you already know, after relocking the bootloader you need to enable OEM unlocking from developer options.
That was a huge problem since I couldn't access the phone at all besides the
bootloader, TWRP (although limited by the locked bootloader), and the default recovery.
That way I got into TWRP but I couldn't do much because of the locked bootloader.
Even if I had a full backup (which I didn't have) I couldn't do much.
I also tried downloading the full OTA image of an updated version of Android (I had Android 10 and I tried to go to Android 11)
to sideload but I couldn't find it. I found one but it was not a full OTA image (with bootloader, recovery, etc.) and I got an error message saying:
"Invalid zip verification signature" or something like that. Also, the error was happening at the start of the ADB sideload, I didn't know what else I could try.
So I have a question: Since I can use "fastboot boot" to bypass the error message,
is there maybe a bootable .img file that I can use to boot directly into the system and enable OEM unlocking?
Any help would be highly appreciated as well any other way to enable OEM unlocking through the bootloader or somehow ADB.