I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
NegativeOne said:
I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
Click to expand...
Click to collapse
If you modify the system and relock the bootloader, you risk bricking the device entirely, if it won't accept fastboot commands
NegativeOne said:
I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
Click to expand...
Click to collapse
First question, I think on some firmware, custom Kernel with root is allowing Android Pay for some users on some carriers. I wouldn't universalize, you have to try.
However, only unlocking bootloadet doesn't work, but in addition a custom kernel can fix what breaks is needed.
ndarkside93 said:
If you modify the system and relock the bootloader, you risk bricking the device entirely, if it won't accept fastboot commands
Click to expand...
Click to collapse
Second question:
EXACTLY: the bootloader detects changes in the system partition away from pure stock, so if you change things, that signals "corruption" to the bootlader so it will PREVENT boot and as ndarkside says, RISK OF BRICK
Sent from my sailfish using XDA Labs
nednednerb said:
First question, I think on some firmware, custom Kernel with root is allowing Android Pay for some users on some carriers. I wouldn't universalize, you have to try.
However, only unlocking bootloadet doesn't work, but in addition a custom kernel can fix what breaks is needed.
Second question:
EXACTLY: the bootloader detects changes in the system partition away from pure stock, so if you change things, that signals "corruption" to the bootlader so it will PREVENT boot and as ndarkside says, RISK OF BRICK
Click to expand...
Click to collapse
Very true, but on the pixel with the November update, safety net checks for bootloader unlock, but I think Franco kernel can hide it to pass the check, if there is no root.
Related
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"
What is a bootloader(tell me in simplest way)....Is unlocking the bootloader really required...? If not then please post another method for root......
ak_wolf007 said:
What is a bootloader(tell me in simplest way)....Is unlocking the bootloader really required...? If not then please post another method for root......
Click to expand...
Click to collapse
watch this video to unlock it https://www.youtube.com/watch?v=iIdJg7KNH3A
and a bootloader allows you to flash kernels/recovers/ and other custom things but only if it is unlocked.
with custom recovery you can install roms,make full system backup,and other things.
a custom kernel wil allow you to overclock cpu/gpu and more.
a custom recovery can be used to flash root.update zip.
but after unlocking bootloader you void your warranty . and your device got hard reset(factory reset)
it can be only unlocked if it is allowed to be unlocked.
android-vinay said:
and a bootloader allows you to flash kernels/recovers/ and other custom things but only if it is unlocked.
Click to expand...
Click to collapse
Not entirely true, at least to all devices. I have a Moto Defy which also has a locked bootloader, no way to unlock, running KK CM11. Developer @pedrodh has managed to create an app called "2ndinit" (1) which allows a second kernel to boot on top of the locked one, allowing to flash new builds despite the locked bootloader. Because of this, Defy is known as unbricable. Similar approach could be used on E3 if some devel take a look into this.
(1) http://forum.xda-developers.com/showthread.php?t=1032212
Regards,
mmerlone said:
Not entirely true, at least to all devices. I have a Moto Defy which also has a locked bootloader, no way to unlock, running KK CM11. Developer @pedrodh has managed to create an app called "2ndinit" (1) which allows a second kernel to boot on top of the locked one, allowing to flash new builds despite the locked bootloader. Because of this, Defy is known as unbricable. Similar approach could be used on E3 if some devel take a look into this.
(1) http://forum.xda-developers.com/showthread.php?t=1032212
Regards,
Click to expand...
Click to collapse
this required root.
for now you need to unlockbootloader to root xperia.
root ur device without unlocking
vinay said:
this required root.
for now you need to unlockbootloader to root xperia.
Click to expand...
Click to collapse
just use kingoroot or kingroot to root ur device no need to unlock boot loader for running those you will have root access but can't do the flashing part
Hi guys,
Just wondering if anyone has an update on the availability or possibility of root for LB Xperia Z5s on Marshmallow?
Also, can I assume that because root is not available on Marshmallow, then it will be equally unavailable on Nougat?
Just a quick thought for the more technically minded - Would it not be possible to deconstruct a valid stock .ftf file and insert a modified kernel, allowing root, before recompiling it and flashing it? I know the locked bootloader stops us from flashing a custom kernel, but is there no way to spoof an .ftf file into using a modified kernel?
Sorry for the n00bish questions, just wondering aloud.
Cheers!
As far as I know you need to disable some security settings in the kernel to have permanent root access. But a locked bootloader won't let the system boot with this modified kernel.
I don't think there will come a method to have root without unlocking the bootloader in the near future.
Nope. No root without unlocked the BL as far as I am informed.
ianrobbie said:
Hi guys,
Just wondering if anyone has an update on the availability or possibility of root for LB Xperia Z5s on Marshmallow?
Also, can I assume that because root is not available on Marshmallow, then it will be equally unavailable on Nougat?
Just a quick thought for the more technically minded - Would it not be possible to deconstruct a valid stock .ftf file and insert a modified kernel, allowing root, before recompiling it and flashing it? I know the locked bootloader stops us from flashing a custom kernel, but is there no way to spoof an .ftf file into using a modified kernel?
Sorry for the n00bish questions, just wondering aloud.
Cheers!
Click to expand...
Click to collapse
Short answer: not possible without unlocking the bootloader.
Long answer:
There are two possible methods for acquiring permanent root on Marshmallow on the Z5:
Conventional root - you provide root by modifying certain /system files on the phone. The problem with this is that you are modifying the system partition on the phone. The stock kernels on the Z5 (and most other phones) have something called dm-verity which basically checks everything on the system partition against what it expects to be there. If the kernel notices that something in the system partition has changed, the phone will fail to boot. You can install a modified kernel that has dm-verity disabled, but then you run into the issue described with systemless root.
Systemless root - you modify the kernel to allow for root either with Systemless SuperSU or through Magisk. This allows for you to have an unmodified system partition and pass any potential system checks, however you have to modify and flash a new kernel. Herein lies the problem with a locked bootloader. A locked bootloader checks the file signature for the file you're trying to flash. These files are typically signed by the phone manufacturer or carrier, so when the bootloader checks the file signature and it matches what it expects, then it allows the flash, if the signature doesn't match, then it aborts the flash. If you modify a stock kernel to disable dm-verity or try to flash a custom kernel, you will be prevented doing so because your signature won't match what the bootloader expects. By unlocking the bootloader you are essentially disabling that signature check process.
So basically permanent root on Marshmallow isn't possible unless somebody can exploit a vulnerability in the boot chain.
As for modifying a stock ftf package. You again run into issues with the bootloader signature checks. The ftf files is basically a special zip container that contains a bunch of files. Most of these files if not all of them are signed by either the manufacturer or carrier so you are able to flash it because all of these files pass the bootloader signature checks. Once you modify one of those files within the ftf, you destroy the signature and flashing of the ftf file will abort.
In summary, you need to unlock the bootloader so that you can flash a modified kernel that has dm-verity disabled.
Thanks very much for all the replies. Looks like I'm stuck with stock for the time being.
Ever since TA backup and bypassing the TA checks was possible since MM or whatever, unlocking the bootloader is not a big deal. Very easy to backup, unlock, root, re-lock, restore.
xasbo said:
Ever since TA backup and bypassing the TA checks was possible since MM or whatever, unlocking the bootloader is not a big deal. Very easy to backup, unlock, root, re-lock, restore.
Click to expand...
Click to collapse
Yeah, but unfortunately I'm not allowed to unlock my bootloader.
ianrobbie said:
Yeah, but unfortunately I'm not allowed to unlock my bootloader.
Click to expand...
Click to collapse
Ahhh, sure, forgot that some carriers lock these phones. I had that same problem on my Z1, but fortunately they found a LB root exploit.
How long have you had your phone? If the upcoming Nokia offering looks good, I'll sell you my mint condition UB Z5
Hey guys I wanted to know the benefits of unlocking the bootloader on my Nexus 5x device.
Any help will be appreciated. Thank You.
Bootloader is like security software for your device, it'll prevent your device from loading a Software or code which aren't properly signed. So, by unlocking it, you can do vice-versa.. You can load all stuff that aren't allowed by your bootloader.
In this term and simple words, by unlock bootloader, you can enable root access and flashing various custom Software/firmware to your device.
R324D said:
Bootloader is like security software for your device, it'll prevent your device from loading a Software or code which aren't properly signed. So, by unlocking it, you can do vice-versa.. You can load all stuff that aren't allowed by your bootloader.
In this term and simple words, by unlock bootloader, you can enable root access and flashing various custom Software/firmware to your device.
Click to expand...
Click to collapse
Can I do this by only unlocking bootloader or is root access necessary. Also is there any way that my phone will be harmed by unlocking the bootloader
mufaddal25 said:
Can I do this by only unlocking bootloader or is root access necessary. Also is there any way that my phone will be harmed by unlocking the bootloader
Click to expand...
Click to collapse
Yes it does, lije I said before, bootloader is factory security software to prevent your device from running malicious codes and software.
Unlocking bootloader is necessary to overwrite your stock recovery by custom recovery like TWRP, because stock recovery doesn't allow you to altering system partition.
I suggesting you to do more research before applying this process as it's can harm and possibly bricked your device.
R324D said:
Yes it does, lije I said before, bootloader is factory security software to prevent your device from running malicious codes and software.
Unlocking bootloader is necessary to overwrite your stock recovery by custom recovery like TWRP, because stock recovery doesn't allow you to altering system partition.
I suggesting you to do more research before applying this process as it's can harm and possibly bricked your device.
Click to expand...
Click to collapse
Oh okay thanks
I have a rooted pixel 2 and an unlocked bootloader, but my company requires me to install MobileIron on my device. I can't seem to find a workaround for MobileIron, so it looks like I need to unroot and relock my bootloader.
1. Does anyone know how to get MobileIron up and running on a rooted device?
2. If no, can I unroot without losing any apps/data? I presume this should be possible, even though re-locking the bootloader might not be possible without losing the apps/data.
3. What about relocking the bootloader? I imagine it will be trickier than just going into developer options and unchecking the allow OEM unlocking box, but maybe that's all it takes?
Have you tired magisk hide? That's sytemless root and many security required apps are fooled by hiding root.
Unfortunately that doesn't work. Would uninstalling Magisk from inside the manager cause me to lose data?
No1ustad said:
I have a rooted pixel 2 and an unlocked bootloader, but my company requires me to install MobileIron on my device. I can't seem to find a workaround for MobileIron, so it looks like I need to unroot and relock my bootloader.
1. Does anyone know how to get MobileIron up and running on a rooted device?
2. If no, can I unroot without losing any apps/data? I presume this should be possible, even though re-locking the bootloader might not be possible without losing the apps/data.
3. What about relocking the bootloader? I imagine it will be trickier than just going into developer options and unchecking the allow OEM unlocking box, but maybe that's all it takes?
Click to expand...
Click to collapse
As far as your third question goes, to relock the bootloader, you don't uncheck allow OEM unlocking. You do the same as when you unlocked it. Plug it into your computer, boot to fastboot mode and, instead of typing fastboot flashing unlock, you type fastboot flashing lock. That's all there is to it. You want to be completely stock when you do it. Can't remember if it wipes the device though.
To unroot without losing your data, download the latest factory image, remove the -w in the flashall.bat file (don't forget to save it after you edit it) . Plug the phone into a computer and then run the flashall.bat file that you edited.