hi all,
I have an unlocked bootloader but not root, and the stock ROM (never changed)
I've read this guide to go back to stock but as I'm not rooted or have a custom rom, would it be possible to simply re-lock the bootloader for the nasty boot up screen message to disappear?
cable_guy said:
hi all,
I have an unlocked bootloader but not root, and the stock ROM (never changed)
I've read this guide to go back to stock but as I'm not rooted or have a custom rom, would it be possible to simply re-lock the bootloader for the nasty boot up screen message to disappear?
Click to expand...
Click to collapse
If you just unlock the bootloader without changing any partitions (like boot, system, recovery etc), you can simply relock the bootloader with the unlock code. But by doing that, the phone will fully factory reset, you may lose all data without backup.
Related
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
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
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.
Can we re-lock the boot loader on Pixel devices if the device is rooted and modded with custom boot and recovery partitions? I heard that it will brick the device when you try to re-lock the boot loader.
Also what if recovery partition ever gets corrupted and a user never had enabled OEM unlocking for the boot loader in the developer option as set as default, and the boot loader is locked as is, user can'f flash the factory images and /or full OTA from ADB.
I'm no expert but from what I've read 'Never relock the bootloader unless you are 10000% sure it's full stuck' and if I remember correctly there is no recovery partition on A/B slot builds which is why a brick is a non recoverable scenario (check that out just in case I'm wrong)
I've unlocked my bootloader and it ain't getting relocked after reading through heaps of bricked pixel threads, best to be safe than bricked.
Yep @junglism93 is right, only re-lock bootloader if you are 100% stock and unrooted to avoid bricks. Also Pixel doesn't have a recovery partition, everything happens in the boot partition, that means that in case of problems if you don't want to reflash the whole factory image (which needs unlocked bootloader), you can just reflash boot.img on slot-a and slot-b (which needs unlocked bootloader anyway).
I unlocked my bootloader straight after the unboxing and I can tell it's like a life saviour, if any problem occurs you can always solve it with an unlocked bootloader.
TENN3R said:
Yep @junglism93 is right, only re-lock bootloader if you are 100% stock and unrooted to avoid bricks. Also Pixel doesn't have a recovery partition, everything happens in the boot partition, that means that in case of problems if you don't want to reflash the whole factory image (which needs unlocked bootloader), you can just reflash boot.img on slot-a and slot-b (which needs unlocked bootloader anyway).
I unlocked my bootloader straight after the unboxing and I can tell it's like a life saviour, if any problem occurs you can always solve it with an unlocked bootloader.
Click to expand...
Click to collapse
That seems like a crazy partition scheme on the device. I can't stand that dreaded unlock screen at the startup. plus you never know for sure if that OEM unlock switch in the developer menu will stay enabled all the time and not accidentally get disabled after modding your device so you're just having a very vulnerable device if it is modded...eh?
I wonder if there is a pure Android device which does not have such restrictions and/or actually comes pre-rooted?
I was experiencing some minor glitches the past couple of weeks after taking the Android 10 OTA, so I decided to a factory reset and flash the Android 10 image. I had to unlock the bootloader to do that of course.
Now I'm realizing I need to re-lock the bootloader so that it's not in this insecure state. However I'm reading that re-locking the bootloader wipes the device (which returns it to Pie?) I'm also reading it can brick the phone if custom data is written.
When exactly do I re-lock the bootloader to preserve my clean install of Android 10?
terrapin01 said:
I was experiencing some minor glitches the past couple of weeks after taking the Android 10 OTA, so I decided to a factory reset and flash the Android 10 image. I had to unlock the bootloader to do that of course.
Now I'm realizing I need to re-lock the bootloader so that it's not in this insecure state. However I'm reading that re-locking the bootloader wipes the device (which returns it to Pie?) I'm also reading it can brick the phone if custom data is written.
When exactly do I re-lock the bootloader to preserve my clean install of Android 10?
Click to expand...
Click to collapse
If you're completely stock you can lock the bootloader. Before you do i would make sure you can boot into the stock recovery as sometimes flashing an ota in the stock recovery is the only way to recover your device if the bootloader is locked. Locking will wipe your device, but it won't change the operating system you're currently on. So if you're on andriod 10 it'll still be 10 after a wipe.