I admit it, I'm confused by the various different rooting threads at this point.
Which root method is the right one for the Sprint model?
Sent from my SPH-L720 using Tapatalk 2
I used this & it worked for me. Easy & quick: http://forum.xda-developers.com/showthread.php?t=2219803
I used the method mentioned above. Seemed to work perfectly. Very easy too.
Sent from my SPH-L720 using Tapatalk 2
Is the bootloader locked or unlocked on the Sprint version ?
Doesn't it have to be unlocked since they are reporting success rooting it?
mysongranhills said:
Doesn't it have to be unlocked since they are reporting success rooting it?
Click to expand...
Click to collapse
These threads are a bit confusing and i want to make sure before i decide to get one
No one really knows if the bootloader is locked or not. Some are able to obtain root, but when flashing certain things, bricked their s4. One dude tried flashing stock and bricked. So I wouldn't get too crazy yet until a dev or someone who knows what they're doing figures out exactly what's going on.
Wow thats crazy flashing something to your phone that isn't made for it.
opz187 said:
No one really knows if the bootloader is locked or not. Some are able to obtain root, but when flashing certain things, bricked their s4. One dude tried flashing stock and bricked. So I wouldn't get too crazy yet until a dev or someone who knows what they're doing figures out exactly what's going on.
Click to expand...
Click to collapse
We have a Stock (dump) build, which will be made available later today that flashes just fine.
If you're following the Engadget bootloader thread, i posted this earlier today..
http://forum.xda-developers.com/showpost.php?p=40844084&postcount=141
This method worked and was painless.
http://forum.xda-developers.com/showthread.php?t=2252248
With regards to the boot methods - we have found something interesting.
@crawrj Had used the Moto root method and couldn't use Solid Explorer properly (i.e. couldn't open init.rc to view, copy system files, etc)
He then used the CF autoroot method and functionality came back.
While not specific enough to point at anything (we don't have logs to look at) I would advise you to check your apps that need root to make sure they function properly.
Just FYI.
I used the AT&T root method and worked fine for me only took 20 seconds.
http://forum.xda-developers.com/showthread.php?t=2252248
Just follow the steps and you will be rooted.
Sent from my SPH-L720 using xda premium
---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------
Pheonix28 said:
This method worked and was painless.
http://forum.xda-developers.com/showthread.php?t=2252248
Click to expand...
Click to collapse
Sorry didn't see this post.
Sent from my SPH-L720 using xda premium
benny3 said:
Is the bootloader locked or unlocked on the Sprint version ?
Click to expand...
Click to collapse
The write protection is enabled in odin mode....don't know what that means as I haven't dived in yet :thumbup:
Sent from my SPH-L720 using Tapatalk 2
Shadow_God said:
The write protection is enabled in odin mode....don't know what that means as I haven't dived in yet :thumbup:
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
I have the HTC ONE and it has the Write Protection enabled also. We have a work around that can be flash through recovery, Not sure how you would implement it with Odin but here is the Link, Maybe you can look at it and may help
http://forum.xda-developers.com/showthread.php?t=2236849
JasonJoel said:
I admit it, I'm confused by the various different rooting threads at this point.
Which root method is the right one for the Sprint model?
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Motochopper, featured in you tube (http://www.youtube.com/watch?v=6fi1tYaoP0U) or (http://www.youtube.com/watch?v=GrvrXXFb2Uo) and be sure to Download the Drivers from the samsung website. For some reason, the drivers within XDA didn't work for me. Once I D/Ld the one specifically for Sprint, motochopper was able to communicate w/my s4 and rooted it:good:
I've not tried the motochopper stuff so I can't speak for that.
I can confirm that I had success the first time with no driver download needed when I used the CF auto-root method. I simply plugged the phone in, let Win7 download the drivers. I then put it in recovery mode (vol down, home and power button, release power button) and once win7 downloaded those (MHT etc) drivers I loaded the file through pda in odin and it went right through with no problems whatsoever.
The CF auto-root thread is here:
http://forum.xda-developers.com/showthread.php?p=39901375
I would suggest waiting until we figure out just what WRITE PROECTION: ENABLED means on the download screen.
Keep in mind that obtaining Root and bootloader lock status are two completely separate things. Typically, the bootloader being locked doesn't affect the ability to OBTAIN Root. But it will block certain partitions of the device being flashed, if it's indeed locked. And it can also affect the root from being permanent or not. (sticking after a reboot)
Root is an android system thing. An operating system thing. Bootloader is a low level boot thing, before android itself is even initialized. Think of it like the BIOS on a PC, it's the screen you see before you get to windows or linux or whatever operating system you're running.
It's sounding like they are having success with writing to many of the partitions that are ordinarily blocked by a locked bootloader. So it's sounding like the WRITE PROTECTION: ENABLED doesn't actually indicate whether or not the bootloader is locked. But we don't know that for sure yet. It's too early to tell.
Unknownforce said:
I would suggest waiting until we figure out just what WRITE PROECTION: ENABLED means on the download screen.
Keep in mind that obtaining Root and bootloader lock status are two completely separate things. Typically, the bootloader being locked doesn't affect the ability to OBTAIN Root. But it will block certain partitions of the device being flashed, if it's indeed locked. And it can also affect the root from being permanent or not. (sticking after a reboot)
Root is an android system thing. An operating system thing. Bootloader is a low level boot thing, before android itself is even initialized. Think of it like the BIOS on a PC, it's the screen you see before you get to windows or linux or whatever operating system you're running.
It's sounding like they are having success with writing to many of the partitions that are ordinarily blocked by a locked bootloader. So it's sounding like the WRITE PROTECTION: ENABLED doesn't actually indicate whether or not the bootloader is locked. But we don't know that for sure yet. It's too early to tell.
Click to expand...
Click to collapse
Our phone is not locked, at least not in the way we know it. We have flashed kernels, recovery and the system partition from Odin. CF Auto root is the best method of Root IMO. Although both rooting options install and stick. But as MoHoGalore stated I had trouble with an app that required root access using the Moto method. I switched to the CF method and everything was working perfectly. We have no idea what the Write Protection means yet but so far it has not inhibited us in any way.
If unknownforce tells me to wait, I wait. I trust his advice quite a bit, after seeing what he is capable of in the evo3d section.
Sent from my SPH-L900 using Tapatalk 2
k2buckley said:
If unknownforce tells me to wait, I wait. I trust his advice quite a bit, after seeing what he is capable of in the evo3d section.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
There is nothing wrong with staying with what you know.
Once we get a complete package, which may not be too far in the near future, we'll know more.
---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------
crawrj said:
Our phone is not locked, at least not in the way we know it. We have flashed kernels, recovery and the system partition from Odin. CF Auto root is the best method of Root IMO. Although both rooting options install and stick. But as MoHoGalore stated I had trouble with an app that required root access using the Moto method. I switched to the CF method and everything was working perfectly. We have no idea what the Write Protection means yet but so far it has not inhibited us in any way.
Click to expand...
Click to collapse
I can attest to this and I'm still functional.
But, for the masses, there are a few of us willing to try if you want to wait.
Here's hoping we know more very soon. :beer:
Related
Hi everyone,
I'm new to "rooting" android devices, although I have jailbroken all my iPhones and "rooted" my palm pre.
As a newbie, it seems the "root toolkit" is the best way to do this? Is this Windows only, or is there a Mac version?
anything else I should read up on / know before rooting? I basically want to root, initially at least, to get sixaxis support and stickmount working.
Thank you all for your help in advance.
First of all, this is the wrong section. You should post inquiries in the q/a section.
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Sent from my Nexus 7
Take a peek at the nexus root toolkit thread in this forum...quick and easy.
Sent from my Nexus 7 using xda app-developers app
The tool kit is windows only, correct?
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
I would agree with:
evonc said:
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Click to expand...
Click to collapse
Then you know what is happening, and how it works... so if you run into troubles later, you know what to do.
Hard to brick this device.
Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
Click to expand...
Click to collapse
For practice, and maybe the one-click solution is not flexible enough for your means. It's usually dependent on the developer to update it, so do check if it has any limitations.
Also, the ones I've seen are Windows only.
Foxman2k said:
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
As long as you don't mess up the bootloader, it should be possible to reflash stuff via recovery or fastboot. Bear in mind there have been exceptions (though that came about because of a serious kernel bug, rather than due to user error) so this can't be a guarantee.
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
spdecoste said:
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
Click to expand...
Click to collapse
Another recommendation for WUGS rootkit - literally very easy foolproof step by step menus/instructions - only prob I had were the drivers - just manually pointing to driver directory sorted this out.
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
This seems to rely on Windows. Any Mac tools available?
Foxman2k said:
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
Click to expand...
Click to collapse
Unlocking the bootloader allows you to mess with the bootloaders progression at startup, which gives you the ability to install a custom recovery and gives us the method to gain root access. The bootloader can be unlocked by many different methods - some manual and some "one-click". I'd suggest doing it the manual way first, so you understand the process, and are able to fix it manually if anything goes wrong.
To my understanding, it's locked so that people who don't know what they're doing can't mess the device up. It's a safety procedure basically.
To relock the bootloader, you just type (I only know how to do this in windows - Linux and Mac work as well al beit differently)
Code:
fastboot oem lock
and you're all set.
Foxman2k said:
This seems to rely on Windows. Any Mac tools available?
Click to expand...
Click to collapse
The Android SDK and ADB tools are equally available on Linux and Mac. You won't have to do the "Adding to Path" thing. All of the ADB commands will be the same, though.
I didn't know anything about rooting at all too, despite having an android phone for more than 2 years.
I went with the one-click root process.
Download this file, plug your Nexus 7, follow the instructions- which means typing Y, N, Y etc
Done in 5 minutes. There's a youtube video on it too. Go check it out.
I still dont know much about the process.. except I'm unlocked and rooted =)
I have a few naive questions
Do I have to do the OEM unlock to root the device? I would prefer not to wipe it.
Assuming I don't hard brick the device, can I go back to stock for warranty work?
Does rooting the device mean I can't get OTA updates from Google? For now I just want to run the stock kernel/rom and get updates. I just want root to run titanium and certain other apps that require root.
I've seen a thread that suggest that the play store (market) doesn't work on rooted devices. Is that true?
Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!
timour79 said:
Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!
Click to expand...
Click to collapse
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.
Billchen0014 said:
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.
Click to expand...
Click to collapse
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
Alright, thanks
Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock
timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
What's your reason for wanting it relocked?
Sent from my HTC Vision using xda app-developers app
noneabove said:
What's your reason for wanting it relocked?
Click to expand...
Click to collapse
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?
Nate2 said:
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?
Click to expand...
Click to collapse
Well I dont want to completely void the warranty, unless rooting already does that. If it was mine then i would've unlocked and rooted. I'd probably already have a rom and kernel on it. But it's actually my dad's, and he said I can root it if I don't do anything too serious(like I said, I just want Superuser so I can use things like the sixaxis controller app.)
comminus said:
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock
Click to expand...
Click to collapse
Would that be manual rooting?
NRT questions
hey there
have some newb questions about rooting along the same lines of the OP. hope you can help me
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
sorry for the newb questions but there are so many different guides out there and some of them refer to older versions of the NRT so just want to clarify these points.
timour79 said:
Would that be manual rooting?
Click to expand...
Click to collapse
No. All you are doing there is unlocking the bootloader. Unlocking the bootloader is the equivalent of pre-heating your oven. You haven't messed with any ingredients or cooked anything yet.
---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------
Lemegeton300 said:
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
Click to expand...
Click to collapse
1. The chances are pretty slim for permanently bricking. That is the beauty of Nexus devices - the entire factory image is available to be flashed back on if you screw things up. That is the equivalent of reformatting your harddrive & reinstalling your OS on your desktop.
2. mkskip's toolkit will install it for you. I am sure wug's will too.
3. You don't have to install CWM, especially if you are thinking that you will pretty much always stay stock. But, the bug might hit you in a month or two to start playing around, and then CWM or TWRP is your friend. I installed CWM & made a backup pretty quickly in case I do something I shouldn't, such as accidentally deleting a vital system app. That way you do not have to do the factory reinstall route. Every few weeks you can make yourself a fresh backup just for fun.
4. You should be fine - the drivers must be working if the toolkit is doing backups for you. I am assuming you are using mkskips toolkit based on this question - his instructions say that sometimes in 1 step it says drivers didn't install correctly when they actually do - Windows is...Windows. If you want to be sure, ask away on mkskip's thread. He is quite helpful.
5. If you reflash the factory image & the bootloader is relocked, there is nothing for them to see...not that they'd really care since the point of a Nexus is to develop on it. You would only be returning it for a hardware issue, and the software unlocking has no impact on the hardware problem, since your hardware issue would've happened no matter what software you had on it. The only way a software thing could cause a hardware issue would be if you over-overclocked it & cooked some parts. You'd really have to work at doing that since these things usually shut down when the temperature gets too high.
In short: root it & enjoy it!
Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Lemegeton300 said:
Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes. When you restore a backup it will be just as it was when you made it. Have fun!
When will the root for NB1 be out? i know that the developers are still working on it, but i just want to know how long will it take. cause i cant wait to do awesome things with the new firmware!!! Did any other kitkat devices succeed to root? like Nexus 5? I should switch to T mobile. tired of this bootloader.
ryujeff said:
When will the root for NB1 be out? i know that the developers are still working on it, but i just want to know how long will it take. cause i cant wait to do awesome things with the new firmware!!! Did any other kitkat devices succeed to root? like Nexus 5? I should switch to T mobile. tired of this bootloader.
Click to expand...
Click to collapse
We do not have root for NB1 as of right now.
We have no idea how long it will take, and asking for an ETA is rude.
Other Kitkat devices have been rooted.
Simple search could tell ya bro.
Live long and prosper...
ryujeff said:
When will the root for NB1 be out? i know that the developers are still working on it, but i just want to know how long will it take. cause i cant wait to do awesome things with the new firmware!!! Did any other kitkat devices succeed to root? like Nexus 5? I should switch to T mobile. tired of this bootloader.
Click to expand...
Click to collapse
Root itself has nothing to do with the bootloader. In the future it will be harder for even unlocked devices to be rooted. Google is cracking down on root too. Unfortunately.
If you are not able to develop should not stop you from trying to find a root method yourself. It could very well be another root method works. After all the first root method for the i337 was made for Motorola phones.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Ok Im sorry for asking about root. Some people says that root won't be able. Just wanted to know. I was not trying to be rude, but well... it went wrong.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
ryujeff said:
Ok Im sorry for asking about root. Some people says that root won't be able. Just wanted to know. I was not trying to be rude, but well... it went wrong.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
You are not really asking for an ETA and not really rude--:good:
It is just a question like who will win the lottery tomorrow--no one knows
There is a thread on the subject you can follow
I wouldn't hold my breath and if you "really" want root/custom roms may want to look at other phones, sorry to say--
ryujeff said:
Ok Im sorry for asking about root. Some people says that root won't be able. Just wanted to know. I was not trying to be rude, but well... it went wrong.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
If my comment came across as rude. I apologize. I only meant for it to be helpful.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
CAG-man said:
Root itself has nothing to do with the bootloader. In the future it will be harder for even unlocked devices to be rooted. Google is cracking down on root too. Unfortunately.
If you are not able to develop should not stop you from trying to find a root method yourself. It could very well be another root method works. After all the first root method for the i337 was made for Motorola phones.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wait, when Chainfire recently got international gs4's root method, Chainfire said that AT&T model cant be rooted due to it's locked bootloader.
Chainfire's CF auto root has not been able to work on the Galaxy S4's in the US because of the locked bootloader true. In my understanding of the method it requires access to the bootloader to inject the su binary. The S4 can be rooted, just not with the chain fire method. All the root methods so far have more or less been obtained through some sideloading. Pushing it off the sd card or off a computer through the adb interface. Therefore not needing to access the bootloader for fastboot to inject the su binary to gain access to the root user.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
CAG-man said:
Chainfire's CF auto root has not been able to work on the Galaxy S4's in the US because of the locked bootloader true. In my understanding of the method it requires access to the bootloader to inject the su binary. The S4 can be rooted, just not with the chain fire method. All the root methods so far have more or less been obtained through some sideloading. Pushing it off the sd card or off a computer through the adb interface. Therefore not needing to access the bootloader for fastboot to inject the su binary to gain access to the root user.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Rooting needs write access to the system partition and since bootloader locks the write access, we can only get temporary root.
So does that mean that sideloading enables us to access to the system partition without bootloader's restriction?
ryujeff said:
Rooting needs write access to the system partition and since bootloader locks the write access, we can only get temporary root.
So does that mean that sideloading enables us to access to the system partition without bootloader's restriction?
Click to expand...
Click to collapse
I don't know your experience level with Unix type systems. Excuse me if you have expereince. In a nutshell Android is built on top of Linux, a Unix type system like OSX and of course Unix. Unix type systems have a "master user" a "super user" named root. Root is the almighty powrful, and thus why it is common for access to it be restricted on Android. The root user can make any system level change. A user can access the root user by typing SU in the command line. This is because the SU binary exists.
The boot loader is pre-system. Its sole purpose and function is to load the operating system. In our case it is also making sure it only loads the approved operating system made by Samsung and ATT. A common bootloader in Linux is called GRUB. Some changes to the system can be made through GRUB. This is in effect what Chairfire does, uses the bootloader to make the changes. Our bootloader is locked so this method will not work. That however does not mean a change cannot be made in the Operating system itself. Why? Because once the bootloader is done, it's sole purpose in life is over until the next boot. An example is found in the check for custom software. When you restart your phone go to settings -about device - status as fast as you can. You will notice as the very bottom Device Status will read "Checking" which will be replaced by either official or custom after it is done. This is the post boot check samsung built in. This is done from the operating system and not the boot loader.
In the operating system there is the super user also known as root, administrators, and standard users. When we use Android we use it as a standard user. You can find the list of Administrators in settings - security - device adminstrators. On our device when root has been achieved in the past it was because a security hole had been found in the system more or less. A developer finds the hole and makes the way to place the SU binary in the system folder. Once there, we can access the root user, the system has been "rooted."
Because it is a give and take battle with the manufacturers, the hole that allowed the most recent root method will inevitably be patched. However in doing so another will inevitably be made. It could be possible that it was an old one. Thus it is good to check other methods that have been created for our device or other devices. It could be it is a new hole entirely and that a new method will be created. All of this does not need approval from the bootloader, because its purpose in life is just to check the OS and initiate it.
I hope that made sense. I tried to make it brief. If anyone see any errors feel free to correct it. I have a good concept, just may not have worded it right.
Sent from my GT-P5210 using XDA Premium HD app
CAG-man said:
I don't know your experience level with Unix type systems. Excuse me if you have expereince. In a nutshell Android is built on top of Linux, a Unix type system like OSX and of course Unix. Unix type systems have a "master user" a "super user" named root. Root is the almighty powrful, and thus why it is common for access to it be restricted on Android. The root user can make any system level change. A user can access the root user by typing SU in the command line. This is because the SU binary exists.
The boot loader is pre-system. Its sole purpose and function is to load the operating system. In our case it is also making sure it only loads the approved operating system made by Samsung and ATT. A common bootloader in Linux is called GRUB. SOme changes to the system can be made through GRUB. This is in effect what Chairfire does, uses the bootloader to make the changes. Ours is locked to his method will not work. That however does not mean a change cannot be made in the Operating system itself. Why? Because once the bootloader is done, it's sole purpose in life is over until the next boot. An example is found in the check for custom software. When you restart your phone go to settings -about device - status as fast as you can. You will notice as teh very bottom Device Status will read "Checking" which will be replaced by either official or custom after it is done. This is the post boot check samsung built in. This is done from teh operating system and not the boot loader.
In the operating system there is the super user also known as root, administrators, and standard users. When we use Android we use it as a standard user. You can find the list of Administrators in settings - security - device adminstrators. On our device when root has been achieved in teh past it was because a security hole had been found in the system more or less. A developer finds the hole and makes the way to place the SU binary in the system folder. Once there, we can access the root user, the system has been "rooted."
Because it is a give and take battle with the manufacturers the hole that allowed the most recent root method will inevitably be patched. However in doing so another wil inevitably be made. It could be possible that it was an old one. Thus it is good to check other methods that have been created for our device or other devices. It could be it is a new hole entirely that a new method will be created. All of this does not need approval from teh bootloader, because its purpose in life is just to check the OS and initiate it.
I hope that made sense. I tried to make it brief. If anyone see any errors feel free to correct it. I have a good concept, just may not have worded it right.
Sent from my GT-P5210 using XDA Premium HD app
Click to expand...
Click to collapse
so if the bootloader checks for an approved operating system made by Samsung and ATT would that be a hole needed to place the superuser binary in the system folder? I'm sorry if that sound noobish but your posting have got me curious but I do not posses the knowledge or software to do anything.
Yeah thanks for lengthy explanation. I know what GRUB and root is. Anyone using linux should know that. Now I understand a bit more.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
If Apple developers can keep coming up with ways to jailbreak the latest OS, I'm sure our talented Android developers will find a way. I have faith in them. :good:
Let's hope so. I like ATT for better coverage than TMO and less money than Verizon. And, want a Note4 on ATT.
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Piaband said:
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
if i could unlock it when i had gotten it in august, sure. but it's too much effort to start over at this point. i have everything set up perfectly. never had to start over. also didn't want to pay for it and send my info to some stranger on the internet. anyway, moot point. good for you, but that option's not available for most people.
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
No nothing roots 4.4 at this point.
vegasdgk said:
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No he basically just rewrote the instructions of how to root the original firmware.
akellar said:
No he basically just rewrote the instructions of how to root the original firmware.
Click to expand...
Click to collapse
I didn't rewrite it. No where are there instructions for getting root AND write protection off on the 4.2.2 camera update without 1 using command line commands AND 2 that network based program (called Cydia compactor I think). There's none of those complications here. Most people don't even realize 1 click root survives the camera update.
But you are right as to kit kat. I thought my title was clear that this is for jellybean though.
mistermojorizin said:
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
Click to expand...
Click to collapse
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
-Zeta- said:
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
Click to expand...
Click to collapse
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
mistermojorizin said:
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
Click to expand...
Click to collapse
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
-Zeta- said:
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
Click to expand...
Click to collapse
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
mistermojorizin said:
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
Click to expand...
Click to collapse
Not sure about the battery life on kitkat of the MAXX right now, so i will stick with 4.2.2 first and do a little research.
Anyway, thanks for the reply and I've gained root on 4.2.2 (12.15.15) using RockMyMoto:laugh:
So, I periodically try different Root methods on this sm-n900v and tonight I tried Kingo Root (PC), and one time when it rebooted it showed the custom unlocked icon. Is this normal? I figure I'm going to try and repeat what I did until it shows that to me again...
Feedback is always appreciated!
When you say custom unlocked icon do you mean when the Galaxy screen comes on? I see that, but I used Towelroot instead of Kingo
I'm on 5.0 OB6.
Interesting. I don't think it's supposed to work like that
AlexanderJohn said:
I'm on 5.0 OB6.
Click to expand...
Click to collapse
You can try forever...but so far...there is NO way to root OB6
Sent from my Note 3 via Tapatalk
I know, but the custom unlock screen came up and I'm curious as to why. Sorry I didn't clarify that.
Sent from my SM-N900V using Tapatalk
AlexanderJohn said:
I know, but the custom unlock screen came up and I'm curious as to why. Sorry I didn't clarify that.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
All that means is you attempted to load a non standard system.....it obviously didn't mean it worked. It's your time, your effort, your phone...have at it.
But people who know a whole lot more about rooting and the issues involved than you or I have been trying for quite a while and have come up empty handed.
Sent from my Note 3 via Tapatalk
Useful and helpful
donc113 said:
All that means is you attempted to load a non standard system.....
Click to expand...
Click to collapse
neither useful or helpful
donc113 said:
it obviously didn't mean it worked. It's your time, your effort, your phone...have at it.
But people who know a whole lot more about rooting and the issues involved than you or I have been trying for quite a while and have come up empty handed.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Sent from my HTC6435LVW using Tapatalk
hey guys, i dont know much about root script but i got an idea. Cant we somehow brick out bootloiader partition so we can flash the old firmware and than root? tell me what you think.
kstoianov said:
hey guys, i dont know much about root script but i got an idea. Cant we somehow brick out bootloiader partition so we can flash the old firmware and than root? tell me what you think.
Click to expand...
Click to collapse
I've actually thought this same thing, maybe wipe the phone out 100% so it would be as if nothing was there then find a write program to put the older bootloader on their or maybe in that case could get into the bootloader and unlock it and flash the phone as new...hmm, I've had that thought many time but I think it would just completely mess the phone up beyond Bootable or working
Sent from my SM-N900V using Tapatalk
thunderblaster88 said:
I've actually thought this same thing, maybe wipe the phone out 100% so it would be as if nothing was there then find a write program to put the older bootloader on their or maybe in that case could get into the bootloader and unlock it and flash the phone as new...hmm, I've had that thought many time but I think it would just completely mess the phone up beyond Bootable or working
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I am ready to try but i need tool to wipe my aboot.img and a software to flash via qualcomm mode and old aboot.img
I'd be willing to do this stuff to if we can find the right tools
The thing about doing a full 100% wipe to reload say the inital factory firmware is what is called a jtag is needed it is a serial connection to the flash chips that is used in the factory to do the inital programming. The problem is this connection is cut off or more often not made accessible to assembled units.
there was with previous samsung phones a usb jtag kicking dongle that could kick a hard bricked phone into a sorta download mode.
this is not present on the note 3 and the note 3 has e fuses that permanently blow preventing some of these things. Additionally there is a built in check to prevent the loading of bootloaders that are unsigned or older than the current bootloader.
so in the end the only thing messing with wiping the boot loader is going to acomplish is hard or soft bricks...
it could be off topic but how they sign their updates? cant we fool the factory recovery?
mirrin said:
The thing about doing a full 100% wipe to reload say the inital factory firmware is what is called a jtag is needed it is a serial connection to the flash chips that is used in the factory to do the inital programming. The problem is this connection is cut off or more often not made accessible to assembled units.
there was with previous samsung phones a usb jtag kicking dongle that could kick a hard bricked phone into a sorta download mode.
this is not present on the note 3 and the note 3 has e fuses that permanently blow preventing some of these things. Additionally there is a built in check to prevent the loading of bootloaders that are unsigned or older than the current bootloader.
so in the end the only thing messing with wiping the boot loader is going to acomplish is hard or soft bricks...
Click to expand...
Click to collapse
That's kinda what I figured
kstoianov said:
it could be off topic but how they sign their updates? cant we fool the factory recovery?
Click to expand...
Click to collapse
Encrypted I know you guys are grasping as straws in desperate hope of the phone not being as locked down as previously thought. But if it were such a simple task of getting the dev device boot loader and fooling the system into thinking it is a legit update we would have an open phone.
the things with the nc2 and nc4 bootloaders was they for some reason did not use the check correctly and left it open for us.