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 have a moto G Xt1032 bootloader unlocked,rooted if I flash again the bootloader in the device info can I see the "warranty was void" message?
If you flash again the bootloader nothing will change.
If you just want to remove that warning screen, read this thread: http://forum.xda-developers.com/showthread.php?t=2548530
That will put your bootup logo to how it was before you unlocked, yet your devices will still be unlocked. This is probably your best option.
If you re-lock your Moto-G, it is still possible to tell that the phone was once unlocked. This will not restore the warranty. I generally don't bother doing this.
Hello guys,
I have a Moto G, Dual Sim variant.
I decided to lock my bootloader, but even after i locked the bootloader back, the warning on the boot screen won't go
Can anyone help?
Thanks in advance!
Fix
Im assuming you're talking about the screen saying "Warning Bootloader Unlocked"??
If so, unlock your bootloader, get a custom recovery like CWM or TWRP.
Follow the instructions over here:
http://forum.xda-developers.com/showthread.php?t=2548530
Download the second zip in the OP, "logo.zip"
Go to your recovery and flash it.
Your Warning Screen should be gone
reeved said:
Im assuming you're talking about the screen saying "Warning Bootloader Unlocked"??
If so, unlock your bootloader, get a custom recovery like CWM or TWRP.
Follow the instructions over here:
http://forum.xda-developers.com/showthread.php?t=2548530
Download the second zip in the OP, "logo.zip"
Go to your recovery and flash it.
Your Warning Screen should be gone
Click to expand...
Click to collapse
This will remove the unlock message but if you check on the fastboot screen your phone will still say locked. code 2 Once unlocked you can relock the bootloader but you can never get back to a locked code 0
Forgot to mention that. What he said. Once you unlock your bootloader, it will never be 0. If you try to go for warranty or something like that, I'm assuming that's how Motorola or whatever will know you unlocked your bootloader and hence, voided your warranty.
Thank you everyone, I just wanted to unlock the bootloader because i am giving my Moto to my brother
I just flashed Lollipop images in my Nexus 5 devices I bought 5 days ago. I didn't used it before so it was a clean install. I'm not familiar with Android so I followed a procedure to flash. In this procedure it says I should unlock the bootloader for flashing. I did it. But now my bootloader remains unlocked.
1) Is that affect battery life?
2) May I fix it?
Thanks.
An unlocked bootloader won't affect battery. It's not necessarily something that needs to be "fixed" but it could be a potential security hole if someone gets his hands on your phone.
If your phone is rooted, download an app called bootunlocker from the play store to relock. If you're not, I believe the fastboot command to lock your bootloader is "fastboot oem lock".
When i did the OTA update, the device is bootlooping. Unfortunately i dont have an unlocked bootloader and have no way of unlocking it as the phone needs to restart to unlock the bootloader. It still stays locked after go to fastboot mode again. I have the stock image from google but have no way of flashing it. Is there anyway to unlock the bootloader without having to restart?
The bootloader relocks itself after reboot? If it does, the emmc is defective and cannot be repaired by reflashing a stock rom or custom rom.