I've decided to post a little blurb about the difference between rooting and unlocking your bootloader because I've seen too many posts using the terms incorrectly. I will update this based of off information posted here and as more information comes to mind.
Unlocking your bootloader:
First, let me describe what the bootloader is.The bootloader is a piece of software that is (essentially) the first thing that runs when you start up a device (bootloaders are on almost every device with an operating system.) The bootloader is what loads the operating system into memory. Now, unlocking the bootloader modifies the bootloader through a hack or a flag that is toggled in the bootloader (this is how the HTC Dev unlock works) that allows the recovery partition to be flashed (or a non-oem recovery to be flashed.) JCase's exploit (http://forum.xda-developers.com/showthread.php?t=2011611) is not a bootloader unlock; it is a method to allow the bootloader to be unlocked by modifying part of your device to emulate another device. This method allows you to use the HTC Dev website to semi-unlock the bootloader.
Rooting your device:
Rooting your device is gaining what is called root access to your device. On some devices, like the DNA, you must unlock your bootloader before you can gain root access. This is because after you unlock your bootloader you can put a file call 'su' in the /system/bin folder. Root privileges in Linux are equatable to administrator privileges in Windows. This is done by flashing the 'su' file to your device. The 'su' file is called by any program that would like to do things that need root privileges to do. The Superuser or SuperSU app on your phone is a manager for the su binary allowing you to allow and deny access to su. The su manager applications are equatable to firewalls for network access.
If anyone has any suggestions or comments for changes/mis-information let me know, please.
Edit:
Made some changes based off of Jarocks' information.
I'm not positive on this, but don't you need to unlock the bootloader to achieve permanent root on the Droid DNA? (Or even temporary root for that matter?)
Jarocks said:
I'm not positive on this, but don't you need to unlock the bootloader to achieve permanent root on the Droid DNA? (Or even temporary root for that matter?)
Click to expand...
Click to collapse
Yessir, you do.
Edit: I misunderstood your reply, and have modified my answer thusly.
Related
I tried to use the HTC dev method to root my phone. (Stupid, I know, I should have read more into it). However, I only got as far as unlocking it. http://forum.xda-developers.com/showthread.php?t=1225974 <- I got up to step 17.
So my question is, when the Revolutionary method is changed to work for 1.50 Hboot (which I have) will this affect my ability to fully root my device? My phone is now unlocked, so will I have to do something different to root it later?
Yntamin said:
I tried to use the HTC dev method to root my phone. (Stupid, I know, I should have read more into it). However, I only got as far as unlocking it. http://forum.xda-developers.com/showthread.php?t=1225974 <- I got up to step 17.
So my question is, when the Revolutionary method is changed to work for 1.50 Hboot (which I have) will this affect my ability to fully root my device? My phone is now unlocked, so will I have to do something different to root it later?
Click to expand...
Click to collapse
Short answer: If your phone is unlocked, you can provide root access now.
Long answer: To provide some clarification of terms:
1) rooting or root provides superuser access to the device
2) HTC unlock/revolutionary provide write access to the internal memory.
Details: Revolutionary's approach, specifically their methods and code are all closed. HTC's approach is also very closed.
Due to the closed nature of Revolutionary's and HTC's work, it is near impossible to predict how these approaches would work on top of each other. If I were to speculate, I would think these approaches *could* be mutually exclusive or if done on top of each other, revolutionary's approach would unlock more internal memory write access than HTC's.
After providing this information, to circle back to your original questions, if you have unlocked the internal memory write protection, you can provide a permanent root solution now. You don't need to wait for anything in the future.
I've taken a fairly narrow, specific, and high level approach to answering your question w/o making any assumptions as to the depth of your knowledge.
If you have any other questions, please post and we'll do our best to answer!
Hope that helps!
So what should I do? I'm not able to finish with HTC's method. Will the Revolutionary way work now?
If you have a HBOOT 1.5 then no you cant use the Revolutionary Unlock method as it onlys supports HBOOTS 1.3 & 1.4. If you want root access with a 1.5 HBOOT you will have to use the HTC unlock method for now. If you have a 1.3 or 1.4 HBOOT then yes you should be able to root using the Revolutionary hack.
1. I'm new here. Xperia Mini is first Android. I really have no idea on what should I do.
2. I've just read trough all replies in
Revolutionary - zergRush local root 2.2/2.3 [22-10: Samsung/SE update]
And I'm wondering, does this way of rooting affect the DRM and TrackID, and all that stuff, as SE site says? I really don't want to lose any functions permanently on my phone, but I want root access, so I can mod small things, and especially install apps like WifiKill.
So, does this root break stuff , as said on SE unlock site?
AFAIK, unlocking the bootloader can erase the DRM keys. Rooting is a different thing. Originally, you could only root after unlocking the bootloader. Apparently this new method can bypass that? But I'm not 100% sure.
barrist said:
AFAIK, unlocking the bootloader can erase the DRM keys. Rooting is a different thing. Originally, you could only root after unlocking the bootloader. Apparently this new method can bypass that? But I'm not 100% sure.
Click to expand...
Click to collapse
Okay, I'm downloading ADB at the moment. Since either it works or can't do any harm, I'm glad to try it.
TrackID works, i don`t use FB so i can not confirm that it works too.
My BL is (re)locked with S1 Tool and the phone was fresh flashed with .335 by wotanclient.
And, yes, by the way, my firmware is 4.0.2.A.0.42 (Android 2.3.4)
And I'm unclear with this:
The binary is available from here: zergRush binary.
The exploit source is available here: Revolutionary GitHub.
Usage:
You will need adb shell to execute this exploit. We need shell permissions.
Push the binary onto /data/local/ and execute these commands in a shell:
Click to expand...
Click to collapse
1. is binary any different from exploit source? I guess we don't need exploit source at all?
is ADB shell same as ADB? How can I get shell permissions?
why do you not use this script:
http://forum.xda-developers.com/showthread.php?t=1320350
? everythis is automatic.
Telemuddi said:
why do you not use this script:
http://forum.xda-developers.com/showthread.php?t=1320350
? everythis is automatic.
Click to expand...
Click to collapse
Wow, this seems alot easier!
I guess I still need ADB (it needs adb drivers) ?
Wow,running that batch file, I have SU, does this mean it's rooted?
I haven't exactly rooted 100 devices before. Most of the root utilities I've used were things like Z4Root where it's one click and done. I've recently become interested in flashing my Incredible 4G LTE. On top of that, I've already rooted my Nexus 7 using instructions like this here.
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
I'm curious if this guide, being that it's more of a manual way to do it since it involves running several commands (I ran this from my Linux desktop to root my N7) is anything like what it would be to root the Incredible manually, or any device. I guess the only device that would be different would likely be the bootloader step (grouper?) since HTC likely did their's differently than Google with the Nexus 7, no?
Just trying to get more insight on it, as I certainly don't want to brick anything but I'd like to get them done. :good:
It seems to me that we would first need a modified bootloader or /system to attempt to flash, but I doubt "fastboot erase ..." is allowed without dev unlock on the bootloader, and "fastboot flash ..." most likely needs a signed image.
Does anyone with more expertise on this topic have any input?
JaSauders said:
I haven't exactly rooted 100 devices before. Most of the root utilities I've used were things like Z4Root where it's one click and done. I've recently become interested in flashing my Incredible 4G LTE. On top of that, I've already rooted my Nexus 7 using instructions like this here.
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
I'm curious if this guide, being that it's more of a manual way to do it since it involves running several commands (I ran this from my Linux desktop to root my N7) is anything like what it would be to root the Incredible manually, or any device. I guess the only device that would be different would likely be the bootloader step (grouper?) since HTC likely did their's differently than Google with the Nexus 7, no?
Just trying to get more insight on it, as I certainly don't want to brick anything but I'd like to get them done. :good:
Click to expand...
Click to collapse
What those tools do is use an exploit to write the su and superuser.apk to /system and/or a modified recovery for flashing ROMS and kernels on unlocked bootloader devices.
google has properly patched those exploits as they should as we don't want a malicious app installing Root and hacking data on just anyone's phone.
Some phones with locked bootloaders have had exploits to install custom recovery and/or hacked/leaked bootloaders in order to allow us to use the phone like it was unlocked. HTC fixed this issue with their latest phones.
Their bootloaders now do not run all of the adb commands until unlocked by HTC dev, which limits us a lot. They also made it so that even if we DID manage to find a software exploit and start flashing stuff, the locked bootloader would know, via a signature check, that something was modified... and refuse to boot (Bricked Phone).
HTC Dev unlock is not true unlock either. We still can't modify the HBOOT w/o triggering it to brick the phone. An unlocked HTC bootloader limits changing the kernel to HBOOT mode only, which means u need a PC and extra steps to finish flashing any ROM.
Some brilliant Dev's managed to use RUU files to update the kernel only, but that also causes issues. If one Dev uses a newer RUU, you can't use the another Dev's older RUU to flash a kernel because the unlocked HTC Bootloader doesn't allow you to "Downgrade" firmware. This leads to headaches with people ignoring the kernel step and screaming because their phone won't boot.
The ultimate Holy grail for is is what is known as "S-OFF"
This allows full access to the HBOOT Recovery and system for all of our awesome devs to work their magic. This was obtained (long after HTCDev unlock) with the Rezound only through a HARDWARE exploit. We needed root exploit (which we had on the GB stock ROM), and to physically short out a pin on the mainboard to ground at precise times while the SOFF program ran on your PC.
We have to wait for the less popular HTCDev unlock (which HTC Did give us on the rezound with a middle finger to verizon), or for some1 to find another Exploit that would bypass the signature check of the HBOOT and give us "S-OFF".
Either will give us Root, custom recoveries, and ROMs.
I am no dev, but this is my understanding of what's happening with these devices. This is my 9th android device, 5th HTC, but I am always learning more. Dev's feel free to correct me, or expand on anything I have written here ^^
Hey guys,
I have a question regarding locking the bootloader, but I'm not sure if it's entirebly possible.
TL;DR: Can I keep root access on the phone if I re-lock my bootloader?
Context:
When I unlock the bootloader, I am able flash custom roms and grant root access to APKs.
To do this, I must first go to "developer settings" and "allow OEM unlocking". Then I will be able to unlock the bootloader.
This allows me to install Cerberus, an anti-theft apk, as a system app.
However, in case the phone gets stolen, If I leave the bootloader unlocked, I am allowing anyone to flash over my phone, thus wiping Cerberus with it.
To prevent someone from tampering with it, I must "allow OEM unlocking" in the developer settings, which can only be toggled when the bootloader is locked.
Basically, I want to be able to unlock my bootloader, root my phone, install Cerberus, and re-lock my bootloader to prevent further tampering, while retaining root access to the phone. Is this possible?
Is this possible?
Don't know if I was confusing in my explanation, but I hope not.
SmoothMarx said:
Hey guys,
I have a question regarding locking the bootloader, but I'm not sure if it's entirebly possible.
TL;DR: Can I keep root access on the phone if I re-lock my bootloader?
Context:
When I unlock the bootloader, I am able flash custom roms and grant root access to APKs.
To do this, I must first go to "developer settings" and "allow OEM unlocking". Then I will be able to unlock the bootloader.
This allows me to install Cerberus, an anti-theft apk, as a system app.
However, in case the phone gets stolen, If I leave the bootloader unlocked, I am allowing anyone to flash over my phone, thus wiping Cerberus with it.
To prevent someone from tampering with it, I must "allow OEM unlocking" in the developer settings, which can only be toggled when the bootloader is locked.
Basically, I want to be able to unlock my bootloader, root my phone, install Cerberus, and re-lock my bootloader to prevent further tampering, while retaining root access to the phone. Is this possible?
Is this possible?
Don't know if I was confusing in my explanation, but I hope not.
Click to expand...
Click to collapse
I'm guessing the same question, will be impossible to steal a phone with Cerberus and locked bootloader.
If Cerberus is a system app it doesn't even need the root to work, isn't it?
Sent from my MI 5s using Tapatalk
SmoothMarx said:
Hey guys,
I have a question regarding locking the bootloader, but I'm not sure if it's entirebly possible.
TL;DR: Can I keep root access on the phone if I re-lock my bootloader?
Context:
When I unlock the bootloader, I am able flash custom roms and grant root access to APKs.
To do this, I must first go to "developer settings" and "allow OEM unlocking". Then I will be able to unlock the bootloader.
This allows me to install Cerberus, an anti-theft apk, as a system app.
However, in case the phone gets stolen, If I leave the bootloader unlocked, I am allowing anyone to flash over my phone, thus wiping Cerberus with it.
To prevent someone from tampering with it, I must "allow OEM unlocking" in the developer settings, which can only be toggled when the bootloader is locked.
Basically, I want to be able to unlock my bootloader, root my phone, install Cerberus, and re-lock my bootloader to prevent further tampering, while retaining root access to the phone. Is this possible?
Is this possible?
Don't know if I was confusing in my explanation, but I hope not.
Click to expand...
Click to collapse
Which phone are you using?
In many phones, bootloader can be locked after rooting, without losing root.
Are you sure locking bootloader will prevent someone who steal phone from unlocking bootloader again? I don't think so.
Wanting to root Alcatel Fierce (model #5049z) and trying to discover whether boot loader is "locked". Read all the posts here concerning this phone and still don't know whether it can be rooted (yet). This is a fairly new phone and information for/about it is sparse. Anyone familiar with this phone and can offer up some vital stats/information or where I might obtain the information? This phone has "unlock boot loader" option, but not sure it works? HELP!!!!!! [Android 7.0]
THANX:
Rick
This does have a oem unlock option yet king root or kingo root doesnt work lol anyways I just picked one of these phones up today and looks like I will have to create my own root and hell mise well get a working twrp in order too. Back to the kitchen!
Just check whether bootloader is unlocked using fastboot.
Use rooting tools after unlocking.
Thats the plan, I planned on creating a way to root then once rooted I can make a full dump if all the partitions of the phone with fire flash then off to deodexing and debloating the system and placing SuperSU in the system so no more issues with root
I will like to know the working method as well i have turned on that option to unlock the bootloader but i have failed to google anything that actually works I have tried iroot, rootme, SRSRoot for Android and none of them was able to root the device
Anything yet?
Has anyone going out anything on this phone. Would like to be able to change a few settings on this phone. Thanks.