Ok, so I attempted to root my Xoom and accidentally flashed a 3G boot image instead of a Wifi boot image. As such, I flashed a wifi boot image back on, and it works fine now. My question is...is my bootloader locked again? I don't know where the bootloader resides, so I cannot answer this question myself.
Thanks!
(Yes, I unlocked the bootloader the first time around. I just don't know if it is still unlocked or not.)
As you flashed a wifi boot image, you are unlocked.
You only go back to locked when you do "fastboot oem lock" - and this will brick your xoom in some shape or form at the moment.
You're still unlocked. Here are the files to fix your Xoom...
http://developer.motorola.com/products/software/
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
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.
Hey guys, i have a problem, my Bootloader is locked and i can't access my recovery, and there is no rom installed, what should i do now? i can't access Developer options to Allow OEM unlock because there is no OS.
am i screwed? or there is something i can do?
Iago Duarte said:
Hey guys, i have a problem, my Bootloader is locked and i can't access my recovery, and there is no rom installed, what should i do now? i can't access Developer options to Allow OEM unlock because there is no OS.
am i screwed? or there is something i can do?
Click to expand...
Click to collapse
Did you ever enable developer options and allow USB debugging? If so, and you can connect to ADB on a PC, you can flash stock firmware back onto the phone.
or try this:
As I didn't have USB debugging enabled I couldn't connect to the phone via ADB, but if you put it into recovery mode you can use Fastboot. Hold down the power key to turn the device off and turn it on while holding down Vol Down to load up recovery mode.
Click to expand...
Click to collapse
However, with locked bootloader there is no room for error in flashing firmware via ADB or you will brick the phone. You have to flash the correct firmware exactly for your phone, with the same level of bootloader you already have or newer. You can't flash Mexico over Brazil or Lollipop over Marshmallow. Has to be exactly what was made for your phone, either what you already had or newer (if it exists).
What OS was installed before?
But WHY is there no ROM installed? What did you do?
The OS installed before was the most recent Stock MM Brazil, i installed the stock rom, it worked, then i wanted to go back to stock recovery, it it worked too, then i wanted to locked my bootloader, i locked, after that i couldn't enter recovery, neither boot to OS.
Iago Duarte said:
The OS installed before was the most recent Stock MM Brazil, i installed the stock rom, it worked, then i wanted to go back to stock recovery, it it worked too, then i wanted to locked my bootloader, i locked, after that i couldn't enter recovery, neither boot to OS.
Click to expand...
Click to collapse
You wanted to re-lock your bootloader? Unlocked bootloader = God mode.
Did you ever have TWRP? You said you wanted to go back to "stock recovery" (not sure why, it's mostly useless compared to TWRP custom recovery.)
I'm not sure why re-locking the bootloader would wipe the OS...
But you can boot to the bootloader screen using the volume and power button and re-flash the stock firmware, using ADB. Here's the link to the newest Brazil Marshmallow for XT1225:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
This guy below got out of a jam because he had an unlocked bootloader, which is very forgiving. Locked bootloader is harder.
https://forum.xda-developers.com/moto-maxx/help/maxx-xt1225-br-hard-brick-help-please-t3661803
Yeah, i don't know what happened either, why the **** did my OS got Wiped?
Can i flash the stock rom with the bootloader locked via ADB? how?
Iago Duarte said:
Yeah, i don't know what happened either, why the **** did my OS got Wiped?
Can i flash the stock rom with the bootloader locked via ADB? how?
Click to expand...
Click to collapse
You have to boot to the bootloader screen manually, using the volume + power button trick.
Once on the bootloader screen, when you plug you phone into a PC with ADB installed, it should recognize it.
Then, flash the full stock firmware, from the link above. It's Brazil Marshmallow firmware with December 2016 Security Update. I don't know of any newer right now. You have Brazil XT1225, so that Brazil firmware is compatible with your phone.
But with locked bootloader you have to flash exact same version or newer made for your phone, and you have to enter the commands correctly or you may brick your phone. (When I flashed from Puerto Rico Kitkat to India Lollipop, I messed up. But since my bootloader was unlocked, I just reflashed again, when I realized my mistake.)
If you are not sure of the steps, google Motorola firmware ADB. Here's a couple of excellent tutorials:
How to Manually Official Firmware on any Motorola Device
https://forum.xda-developers.com/dr...force-how-to-manually-flash-official-t3282077
I use this one above. IGNORE where it says you need an unlocked bootloader, because he's talking about cross-region flashing which you are NOT doing. You are flashing your own region firmware.
This one below is by rootjunky and he while he also discusses RSDLite, later in the article he says ADB/fastboot are best as RSDLite can stall.
Motorola Firmware Restore Plus Unbrick
http://www.rootjunky.com/motorola-firmware-restore/
If you get your phone running again, I suggest you unlock the bootloader. There are ways to hide an unlocked bootloader (like Magisk), if that's why you locked it back... But an unlocked bootloader + root makes it YOUR phone and much easier to recover from disasters.
Thanks a lot Chazz, it worked, thanks for the help, really appreciate it, thanks for all the useful tips too.
So here's the history, one beautiful day my XT1033 (Brazil), starts rebooting by itself. Went online, found somethings to do, UNLOCKED THE BOOTLOADER TROUGH THE MOTOROLA SITE, and downgraded to 4.4.4, but I made the mistake of updating it, trough the normal motorola updater. It went black, wouldn't turn on, not even fastboot. Researched a bit more, did a blank flash and then I could access fastboot again. Problem is, somehow my device's bootloader got locked again, and when I tried to "fastboot oem get_unlock_data" , I would get a " couldn't get unlock data!".
So, now I can't flash a ROM , and can't unlock bootloader, is there a way to flash a ROM with it locked? Or to re-unlock the bootloader?
Pls help, I can't stand using a Galaxy pocket neo anymore, HELP ME.
GOD BLESS!
if you can access Bootloader i can recommend just reflash the original stock firmware and u can do that with locked bootloader.
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?