Related
I'm looking up update to a new phone, and I ran into this question that I've never thought about... I've never had to do an update to my bootloader (After it was unlocked, That I'm aware of) when going between Android 4.x, 5.x, and 6.x. I know there are new kernels/boot.imgs, but never noticed a bootloader update. Unless I'm missing something, from what I can tell other phones (even ones that are unlocked) seem to "require" an updated bootloader to allow the newer code in the OS to boot.
If this is all true, and I'm not missing something obvious, why is this? Did someone rig the kernel or OS on our phones to allow using an older bootloader or something? I'm seeing responses on other sections of the site for other phones like the G4 T-Mobile (Which doesn't have a locked bootloader) and some other places that a Marshmallow update to CM or another AOSP-like cannot be done until the carrier releases 6.x for the phone, even if the International variant of the phone has the 6.0 update.
Title says it all. I have a 7.1.2 (beta) Pixel on VZW with a locked bootloader. I'd like to go back to 7.1.1 public static le release. I unenroll from the beta program and I haven't got an OTA to go back. It's been over 24hrs.
I know Google will eventually fix their OTA beta system, but in the meantime can't I do this manually?
I tried to side load the 7.1.1 OTA from Google via ADB and it gave me an error about being older than the version currently on the device. Is there a file I can modify in the OTA.zip to get around that or am I stuck as long as my bootloader is locked?
farfromovin said:
Title says it all. I have a 7.1.2 (beta) Pixel on VZW with a locked bootloader. I'd like to go back to 7.1.1 public static le release. I unenroll from the beta program and I haven't got an OTA to go back. It's been over 24hrs.
I know Google will eventually fix their OTA beta system, but in the meantime can't I do this manually?
I tried to side load the 7.1.1 OTA from Google via ADB and it gave me an error about being older than the version currently on the device. Is there a file I can modify in the OTA.zip to get around that or am I stuck as long as my bootloader is locked?
Click to expand...
Click to collapse
You're stuck for now. Don't modify anything that might brick the device since you can't recover with a locked bl. Just wait for the public release to be sent to the device. Why do you want to go back to 7.1.1?
bobby janow said:
You're stuck for now. Don't modify anything that might brick the device since you can't recover with a locked bl. Just wait for the public release to be sent to the device. Why do you want to go back to 7.1.1?
Click to expand...
Click to collapse
Ok thanks. I didn't notice anything new with 7.1.2 other than a couple little bugs. I had some graphical tearing on the status bar initially and then wifi advanced settings continuously crashes if you try to open it. Personally, I like 7.1.1 better than the first beta 7.1.2.
Since the update to 7.1.1 any possibility to downgrade is blocked. Verizon pushed the update to block any method that allows bootloader unlock. If you were locked and took the OTA you are permanently locked. Although anything is possible do not hold out for a new exploit to be found. I have never seen a new method found to unlock a device that has had the exploit patched.
Hello just a few minutes ago I manually searched for updates from the system setting (have auto update off) and realized I had an update so I took it. I've taken updates OTA before with no issues however this time it basically completely factory data reset my phone and also what's more bizarre is it removed my bootloader unlock that I had gotten way back when the phone was first released. I have never installed custom firmware or even rooted the device but I did get my bootloader unlocked using a paid service that I found about here. I have a snapdragon model note 20 ultra 5g. I am so confused why this time around the OTA affected these things. I have included a screenshot of the OTA I took. Can anyone tell me what happened to my bootloader unlock I've had for like 6 months ?
Do you have a U or a UI device? If so I think Samsung changed the bootloader from version 1 to version 2 and that might be why you lost it. Checkout the last 2 pages of this thread here where you might be able to get more clarification.
Whenever you lock or unlock your bootloader, you device will factory reset.
When you took the update, it updated the bootloader to version 2.
Since your unlock was not an official one, it relocked your bootloader in the process.
This is what caused the wipe.
Yup. You're not supposed to take ota updates with unofficial unlocked bootloader.
Not even sim unlock.
coilbio said:
Yup. You're not supposed to take ota updates with unofficial unlocked bootloader.
Not even sim unlock.
Click to expand...
Click to collapse
Is there such a thing as an official bootloader unlock?
shpotik said:
Is there such a thing as an official bootloader unlock?
Click to expand...
Click to collapse
Nope. Not for US versions.
Why did you unlock the bootloader if you haven't ever rooted or flashed custom?
*Detection* said:
Why did you unlock the bootloader if you haven't ever rooted or flashed custom?
Click to expand...
Click to collapse
It sounded like a good idea at the time.
As my device was rooted a month ago but couple of days ago I lost the L1 cirtification, today I updated to latest firmware by downloading full size by oxygen updater and updated it with in-device local update method. But even after the update my device's L1 cirtification is still not back and it's showing L3.
I rooted my device by flashing patched image with adb. Now I'm afraid locking bootloader might cause issues... Any suggestions how should I lock my bootloader. Somewhere I saw that lock option for bootloader in developer option cause bootloop/brick.
Btw my own lock is greyed.
Relocking the bootloader will definitely cause issues, maybe this thread can help?
XDHx86 said:
Relocking the bootloader will definitely cause issues, maybe this thread can help?
Click to expand...
Click to collapse
Yes I tried that already.
Hi, I found my old Asus ZenFone 4 Max hard bricked from last time when I lock the bootloader after installing lineage OS. I leave the phone abandoned around 6 months since I already feel hopeless.
First I unlocked the bootloader, then flash lineage os recovery then lineage os.
After completing flashing lineage os, I locked the bootloader and it can't be unlocked anymore.
I tried to unlock the bootloader again but it receives an error. (Forgot the error long ago). Tried to flash stock ROM or recovery with bootloader locked also can't.
Send to service center probably cost more then the phone value, since it's not very good condition (screen crack) and old device.
Is there any way to solve it?
Thanks
Also, it can't be used any more. Stuck on fastboot screen but can't unlock bootloader.
Forgot to mention, X00HD