If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.
If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.
If you're on a device that cannot be unlocked, you should wait the Android 13 official release.
Related
Just curious if the new 2.3.4 gingerbread OTA can be unlocked using pudding. I'm having to get my atrix replaced via warranty and if the replacement happens to come with gingerbread already on it i want to know if i'll be able to unlock it or if i'll be stuck using p-roms.
You should be able to unlock it with pudding since its the same version of gingerbread that we have. Also, don't flash any sbf files (except pudding) because it has the new bootloader and you'll hard brick it if you do.
You can unlock with pudding and fastboot BUT there's a high chance you'll soft brick first with 0x1000 ... all you need to do is get into fastboot mode and redo the oem unlock command.
mysticdrew said:
You can unlock with pudding and fastboot BUT there's a high chance you'll soft brick first with 0x1000 ... all you need to do is get into fastboot mode and redo the oem unlock command.
Click to expand...
Click to collapse
Alright, just to be absolutely, completely, all the way, 101% sure: does this OTA have ANY bootloader restrictions, be they a brick or non-unlockable bootloader. Has anybody tried to unlock the bootloader and run a custom ROM on the AT&T OTA? I just want to be able to run custom ROM's down the road (as in full ROM's, as in Cyanogenmod).
Do the OTA and never, never go back to any older stock version via RSD. Or you'll brick your phone.
@Chairsofter1138: the ota bootloader is locked. flash the pudding to unlock.
Alright, has anyone actually attempted to unlock the OTA via the pudding method? I'm being extra cautious here because I don't want to be stuck with a permanently locked down phone. Does it matter, then, if I use Kenthepenns (sp?) installation method or OTA straight from AT&T/ Motorola?
Chairsofter1138 said:
Alright, has anyone actually attempted to unlock the OTA via the pudding method? I'm being extra cautious here because I don't want to be stuck with a permanently locked down phone. Does it matter, then, if I use Kenthepenns (sp?) installation method or OTA straight from AT&T/ Motorola?
Click to expand...
Click to collapse
Yes everyone has been unlocking via pudidng because it's the same leaked version that has been out for the past couple weeks.
Yes Going to this OTA will make a brickable phone. You WILL NOT BE ABLE TO DOWNGRADE via traditional SBF.
This is the question everyone has been asking on every thread and the devs aren't answering.
I am locked and stock on 1.83. My fuse HAS not been burnt. I want to be
1. On Gingerbread
2. Unlocked
The problem is that all the current gingerbread sbfs said you had to be ALREADY unlocked to flash them, so I don't know how anyone has been testing this OTA with a locked bootloader. If you had the new Gingerbread, you were already unlocked, is how I understood it.
Questions in follow up to the above:
1. If I OTA before unlocking, what do I flash afterwards to unlock? Saying 'pudding' because there's 10,000 files in that thread, including links to an 'unlocker.sbf', as well as a full sbf operating system. What specific file?
2. Lots of new builds say they have an 'unlocked bootloader' built in, but nobody can figure out what that means. Does that mean you can flash them without being unlocked to unlock? What do you need to do to unlock after you flash them?
3. If I unlock now at stock 1.83, and take the OTA, what happens, is the bootloader locked again? I know OTA installs a new bootloader.
Please someone help me understand. There's too much hard bricking and misinformation out there on all the dev threads. What's true (and please tell us how you know).
I noticed everyone talking about the OTA. I saw on the Moto site that the new update is only available OTA but there's a link for download for the file "Blur_Version.4.5.91.MB860.ATT.en.US". Can anyone confirm that this can be installed without brick on an unlocked bootloader? I've seen other threads stating so but they're not really clear on what's being said.
m0use1 said:
This is the question everyone has been asking on every thread and the devs aren't answering.
I am locked and stock on 1.83. My fuse HAS not been burnt. I want to be
1. On Gingerbread
2. Unlocked
The problem is that all the current gingerbread sbfs said you had to be ALREADY unlocked to flash them, so I don't know how anyone has been testing this OTA with a locked bootloader. If you had the new Gingerbread, you were already unlocked, is how I understood it.
Questions in follow up to the above:
1. If I OTA before unlocking, what do I flash afterwards to unlock? Saying 'pudding' because there's 10,000 files in that thread, including links to an 'unlocker.sbf', as well as a full sbf operating system. What specific file?
2. Lots of new builds say they have an 'unlocked bootloader' built in, but nobody can figure out what that means. Does that mean you can flash them without being unlocked to unlock? What do you need to do to unlock after you flash them?
3. If I unlock now at stock 1.83, and take the OTA, what happens, is the bootloader locked again? I know OTA installs a new bootloader.
Please someone help me understand. There's too much hard bricking and misinformation out there on all the dev threads. What's true (and please tell us how you know).
Click to expand...
Click to collapse
+1 to everything this guy said..There is a ton of guests in this forum wondering the same **** too. Devs are doing a fantastic job, but us end users (including myself) don't really have a sense of direction right now.
hi to everyone,
'till last week I was able to install every custom rom I wanted to on my mediapad, but now, after reinstalling an original one, my bootload is locked!?!
How can it be?
Fastboot says my lovely brick is LOCKED.
Is there a way to unlock it?
How?
Thanx in advance.
Dan
Just flash older fw version from huawei website. Last 2 or 3 versions are with locked bootloader.
This might work:
fastboot oem unlock
Why would they start locking the bootloader?? Locked bootloaders cause bricked phones
Sent from my SCH-I200 using xda app-developers app
try to flash official c232b005. that is the last stable official rom that not lock the bootloader.
huawei starting to lock the bootloader from the released rom after that, for device s7-302u. maybe they think with locked bootloader user cant or difficult to root or anything else with the device. that can minimize the device brick.
I have this PadFone S for over a week, and it's my 5th android device, but certainly the 1st one having a locked bootloader. So far I have read how to flash stock firmware, how to root and unroot, which requires unlocking bootloader first using CrowLock, how to install CWM and CM12 etc. I haven't try anything yet (still uprooted, and my bootloader is still unlocked).
One question still unanswered, is there any way to lock the bootloader after it's unlocked ? Perhaps by using the CrowLock app, or simply flashing stock firmware ? I need to be assured that any changes I do is reversible.
Thanks in advance
I too purchased the Padfone S and have the same question. Also, does anyone know if flashing crowlock will void the warranty of the phone? Can someone who has unlocked their bootloader using crowlock paste the output of "fastboot oem device-info"?
Does Asus' bootloader not check the signature for the recovery partition before booting from recovery? Given that everyone is flashing the recovery after rooting and running crowlock from the recovery, it seems so, but I'm not sure.
Anyone know if the bootloader's source code is available? I know it's based on the littlekernel, but I'm not sure which version it was built from.
Bump! I need the answer too.
I have bricked my phone. It's stucked in a boot loop.
I had an up-to-date, non-rooted, locked XT1524. Since 3G and 4G didn't work on my country, first I tried flashing the modem and baseband from a retail XT1527 stock ROM. The flashing went OK, but 3G and 4G still didn't work (as happened to pablo_cba in this thread).
Then I turned my common sense off and tried flashing the whole XT1527 ROM. I though that since they were stock ROMs I didn't have any need to root the phone (or install TWRP). And since I was flashing the same version I had, I didn't need to unlock the bootloader either. Wrong! The ROM I flashed was version 5.1 (23.29-15), and my current ROM at the moment was 5.0 (22.50-X). Since I haven't unlocked the bootloader, I can't go back to the retail XT1524 stock ROM published here.
I was able to flash gpt.bin and bootloader.img, but things went south on boot.img. Now the bootloader is stuck with the following error:
Code:
version downgraded for boot
failed to validate boot image
Trying to flash boot.img (or system) fails with error:
Code:
hab check failed for boot
Failed to verify hab image boot
Trying to go back to XT1524 ROM fails with:
Code:
version downgraded for aboot
Trying to unlock the bootloader fails with:
Code:
Enable OEM Unlock
Which is obvious because I haven't enabled it on the phone, but it sucks because I can't boot and enable it.
So, here goes my questions:
- What does the "hab check failed" means? Is there any way to bypass it and finish flashing the XT1527 ROM?
- Is there any way to unlock the bootloader without enabling it first on developer settings?
- Is there anything I can do other than waiting that 5.1 gets rolled to XT1524 phones, and that a stock ROM for it gets leaked?
Thanks a lot for your kindly help!
Ah, I know exactly what happened. The good news is that your device is not bricked. The bad news is that you will need to wait a few weeks for the XT1524 5.1 stock images to be released.
The CID is a one byte Motorola specific value that indicates which region your device is for. Boot and system images are signed by Motorola tools that sign for a specific CID. The bootloaders for Motorola phones are signed with qualcomm tools that do not care about CIDs. As a result, you can flash a bootloader meant for a device with a different CID, but you can't flash a boot or system image for a different CID (while bootloader locked).
Since the bootloader is not CID specific, you were able to flash the new bootloader. The new bootloader blows fuses to increment the security version and prevent rollback. It will not allow you to flash an older boot and system image, since they may contain vulnerabilities. Now, the bootloader won't allow you to flash anything except a new 5.1 ROM signed for your CID.
I'd recommend just waiting a few weeks for the signed official 5.1 images for XT1524 to be released.
If you can't wait and are willing to take your phone apart and void the warranty and solder onto stuff, you can circumvent the Factory Reset Protection feature to unlock your bootloader. I don't recommend doing this, but it can be done. You will need to solder onto test points for the flash (that will be located underneath shielding cans). Writing 0x01 to the last byte of the frp partition will enable bootloader unlocking. Once again, I don't recommend doing this, I'm just stating what is possible.
EDIT: It might be worth a try seeing if Motorola will do something under warranty. The challenge will be to explain your problem in a manner that will not make them consider it to have been damaged by you. I don't know what they will think of your issue.
The exact thing happened to me. I think that the 5.1 firmware will arrive soon to your device. I took to my carrier, and they gave a new one in 2 weeks. I think that Motorola won't help you, as you requested the bootloader code.
I have tried for multiple hours to get fastboot and ADB to work with my S6 Edge but it is not working. I suspect I might need to try older Samsung drivers (I only tried the latest ones as far as I remember). I wanted these tools in order to check if my bootloader was unlocked so that I wouldn't brick my device if I tried to install a custom ROM and TWRP. Anyway I followed a video and installed TWRP on my phone and installed Lineage OS Android 10 without checking the bootloader since the guy in the video did not mention doing so and still installed the custom ROM and TWRP. It is working fine. I know it is most likely that since this was possible, the bootloader should probably be unlocked but I just wanted to confirm with more experienced smartphone modders if this is indeed the case. Is it then safe to root my phone without checking bootloader?
Sub-question: If a person were to theoretically attmept to install custom ROM or TWRP or root the phone while the bootloader is locked, would that result in the root failing but the device still being usable or would the attempt result in the device being bricked? IE if the bootloader is locked is it dangerous to attempt to flash software to the phone or will it result in a harmless "failed" message, etc.?
Thank you.