I was on a stock rom with root and use OTA root keeper and took the jellybean ota update. I'm now on 4.1.1 with root, but can't get the bootloader unlocked. Only reason I say the BL isn't unlocked is because every time I flash a OC kernel, I cant change the cpu or when it does allow me to change the cpu, it just goes right back to 1512.
I can flash roms, but it seems as if the whole rom doesn't flash. I tried ez-recovery with ez-unlock and it just says device status unknown and when I click unlock it says it unlocks it but status still says unknown. Anyone done the ota rootkeeper and got the unlocked bootloader back?
I did the OTA rootkeeper then used EZ Unlocker with no issues.
Sent from my SCH-I535 using xda premium
DarkMenace said:
I did the OTA rootkeeper then used EZ Unlocker with no issues.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Not sure how I screwed it up. I odin'd back to stock (route66). Then did root and installed root keeper and backed it up. Then took all.of the ota's until I got to 4.1.1, then restored root, installed ez-recovery and flashed cwm, then installed ez-unlock. Device status says unknown. Did yours say locked/unlocked on yours?
It did untill I used EZ Unlock. Once I used that the unlock icon vanished.
Sent from my SCH-I535 using xda premium
justdhutch said:
I was on a stock rom with root and use OTA root keeper and took the jellybean ota update. I'm now on 4.1.1 with root, but can't get the bootloader unlocked. Only reason I say the BL isn't unlocked is because every time I flash a OC kernel, I cant change the cpu or when it does allow me to change the cpu, it just goes right back to 1512.
I can flash roms, but it seems as if the whole rom doesn't flash. I tried ez-recovery with ez-unlock and it just says device status unknown and when I click unlock it says it unlocks it but status still says unknown. Anyone done the ota rootkeeper and got the unlocked bootloader back?
Click to expand...
Click to collapse
Download version 1.2 of EZ-Unlock from here. The latest version on the market has a bug that leaves the status always saying "unknown".
It sounds to me like your bootloader is unlocked, and the OC issue is with your kernel. If your bootloader was locked, your phone would not boot with a custom kernel, instead you would be greeted with "Unauthorized software detected, bring your phone into Verizon Wireless".
Related
Just got my replacement unit and it came with 4.1.1. Am I safe to start rooting or do i need to check bootloader?
Sent from my EVO using xda app-developers app
Rooting is independent of the bootloader.
Ok. In terms of unlocking and changing the Rom I'd have to verify bootloader or is 4.1.1 only shipped with 1 bootloader?
Sent from my EVO using xda app-developers app
mumbles202 said:
Ok. In terms of unlocking and changing the Rom I'd have to verify bootloader or is 4.1.1 only shipped with 1 bootloader?
Click to expand...
Click to collapse
With the original firmware (before unlocking and installing custom stuff), the bootloader version is always the same as your firmware build (10.4.x for Android 4.1).
Before you install a 4.2-based custom ROM you must update your bootloader to 10.6.x and install a compatible recovery (e.g. TWRP 2.5 or 2.6).
_that said:
With the original firmware (before unlocking and installing custom stuff), the bootloader version is always the same as your firmware build (10.4.x for Android 4.1).
Before you install a 4.2-based custom ROM you must update your bootloader to 10.6.x and install a compatible recovery (e.g. TWRP 2.5 or 2.6).
Click to expand...
Click to collapse
Ok thanks. I used Motochopper to get root just now. To unlock bootloader does it matter whether I go to 4.2 first? If either way it reaches out to Asus what's the difference?
mumbles202 said:
Ok thanks. I used Motochopper to get root just now. To unlock bootloader does it matter whether I go to 4.2 first? If either way it reaches out to Asus what's the difference?
Click to expand...
Click to collapse
On Asus' website it says the Unlock Tool is only for ICS firmware, which is incorrect. You can use it just fine on any JB firmware.
So no, it does not matter if you upgrade to JB 4.2.1 first. But you will loose root though and have to use Motochopper again to regain it.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
OTA just updated Nexus 5 to 4.4.2. I've lost TWRP and ROOT. Can I use stock recovery to install superuser, if so, how? The reason I'm asking is I don't to start over from scratch if the bootloader has to be unlocked.
Note: I didn't loose Hotspot tethering after OTA 4.4.2 update. It kept all my settings.
Update: I think I've figured out my own question. The bootloader has to be unlocked, so you'll lose your settings and data. Lesson learned; just update using zip in recovery mode next time.
Either use cf-root or twrp to get root, only time the phone gets wiped is if you unlock the bootloader, and ota updates never relock the bootloader.
hi, i have a noob question. I'm not a true noob but i never had a "nexus".
Today i unlocked bootloader, installed twrp recovery and rooted my device. Then i flashed only franco kernel to try new screen firmware update.
So i'm stock with cm11s without kernel.
When an update will be released,unchecked CM recovery update, can i update or i have to unlock bootloader again before?
after updated iìll be with bootloader lock or unlock?
Thanks to everyone
The OnePlus One is not a nexus device but it is very close to being one.
No you do not have to relock your bootloader, leave your bootloader unlocked. There is no point in relocking it unless you're doing warranty.
Just untick "Update CM Recovery" in Developer Options if you haven't already. You can flash the new OTA with TWRP.
Hi guys.
I'm also having some questions about the OTA updates and the root/bootloader.
Currently i'm still having the 25R, i unlocked it, rooted it with TWRP, all fine.
I've been using Nexus 4 before, and after lots of Roms i kept using CM for a very long time, so normally i just updated it, and i was still rooted and everything.
But now i keep reading that you will lose root and bootloader if you update the CMs (with OTA?).
So then i have to unlock and root again, so i will need to wipe all data again?
Or is there a simple method to just update and still keep all root etc?
greetings
GirlKillu said:
Hi guys.
I'm also having some questions about the OTA updates and the root/bootloader.
Currently i'm still having the 25R, i unlocked it, rooted it with TWRP, all fine.
I've been using Nexus 4 before, and after lots of Roms i kept using CM for a very long time, so normally i just updated it, and i was still rooted and everything.
But now i keep reading that you will lose root and bootloader if you update the CMs (with OTA?).
So then i have to unlock and root again, so i will need to wipe all data again?
Or is there a simple method to just update and still keep all root etc?
greetings
Click to expand...
Click to collapse
Nothing will happen to the bootloader. If root is lost after applying OTA, just reflash SuperSU. You can apply OTAs using TWRP.
No wipe needed.
Hello,
I'm guessing most of you already know that the android 5.0 or android lollipop updates started rolling out OTA. My nexus 5 is rooted and its running stock android 4.4.4 with the stock recovery. Also my boot loader is locked. Should I "un-root" my nexus 5 for the OTA update or should I try updating it with root on my phone?
Regards,
cyberusman
It should update with root but you'll lose it. You'll need to unlock your bootloader to root again though. I'd just unlock with boot unlocker and flash factory image personally.
rootSU said:
It should update with root but you'll lose it. You'll need to unlock your bootloader to root again though. I'd just unlock with boot unlocker and flash factory image personally.
Click to expand...
Click to collapse
I went onto my root app(superuser) and went to info and checked the box called OTA survival. After that ontroead the OTA update, it installed 1/4 of the way then just said error. What do i do?
Try other update methods. Root options available in my signature
rootSU said:
It should update with root but you'll lose it. You'll need to unlock your bootloader to root again though. I'd just unlock with boot unlocker and flash factory image personally.
Click to expand...
Click to collapse
I took the OTA with root and stock recovery. Updated, lost root, but the bootloader is still unlocked. My N5 is the Google play store edition if that makes a difference. Im I'm guessing carrier specific phones are relocking the bootloader.
Sent from my LGLS990 using XDA Free mobile app
MikeDroid said:
I took the OTA with root and stock recovery. Updated, lost root, but the bootloader is still unlocked. My N5 is the Google play store edition if that makes a difference. Im I'm guessing carrier specific phones are relocking the bootloader.
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
OTA doesn't lock the bootloader. All nexus 5's are created equal
Hi,
I have an LG Nexus 5 (KTU84P, or "hammerhead") running Android KitKat 4.4.4. It is rooted using Chainfire's AutoRoot for the Nexus 5 for Android 4.4.4, and I have no custom ROM, simply Vanilla Android but with SuperSU. I am looking to update to Android L, version 5, and I have received a notification for the OTA update.
I understand that with OTA updates, your data will not be wiped, but you will lose root access. I have researched ways to keep the root, but they only appear to be for older versions of Android. I understand that I will lose root.
My question is, will I have to run the "oem unlock" (which I understand is the part of the whole rooting process which actually wipes your device), or will I just have to load Chainfire's AutoRoot? If I go through with it, I will use his AutoRoot for hammerhead for Android L, but basically my end goal is to root and update and not lose any data.
Thanks, if you need more info, let me know?
Autoroot will not wipe your data if your bootloader is already unlocked. Only if your bootloader was locked to begin with.
Nope. Once unlocked it stays unlocked unless you lock it yourself
frenziedfemale said:
Autoroot will not wipe your data if your bootloader is already unlocked. Only if your bootloader was locked to begin with.
Click to expand...
Click to collapse
musclehead84 said:
Nope. Once unlocked it stays unlocked unless you lock it yourself
Click to expand...
Click to collapse
Thank you both very much!
Of course with L you can no longer get the OTA if you have custom recovery. Just incase you weren't aware
rootSU said:
Of course with L you can no longer get the OTA if you have custom recovery. Just incase you weren't aware
Click to expand...
Click to collapse
I have updated OTA, and I kept EVERYTHING, even my root apps, but when I open up SuperSU I get a notification explaining that the Su binary is not installed, which is obviously removed when updating. Now, I'm just backing up my data. Another thing I would like to confirm is, if I use Chainfire's Auto Root for the Nexus 5 running Android 5.0, will it run OEM unlock again, and if it does, will I be affected considering my bootloader is already unlocked?
AudaxNovus said:
I have updated OTA, and I kept EVERYTHING, even my root apps, but when I open up SuperSU I get a notification explaining that the Su binary is not installed, which is obviously removed when updating. Now, I'm just backing up my data. Another thing I would like to confirm is, if I use Chainfire's Auto Root for the Nexus 5 running Android 5.0, will it run OEM unlock again, and if it does, will I be affected considering my bootloader is already unlocked?
Click to expand...
Click to collapse
If its unlocked, it can't be unlocked again.
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
D3abL3 said:
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
Click to expand...
Click to collapse
Odd. Hasn't locked for anyone else afaik
D3abL3 said:
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
Click to expand...
Click to collapse
There's a REALLY easy way to test that theory.
Open the factory image archives and check the script. Unless it runs 'fastboot oem lock' it isn't relocking it.
#stayparanoid
Don't you think this makes the trick?
"fastboot flash bootloader bootloader-hammerhead-hhz12d.img"