Database Users

New to rooting - What is easiest?

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?

[Q] Unlocking vs rooting

Potential first time Nexus user coming over from Desire Z.
I intend to transfer my old data from my DZ to the nexus4 when I get it via Titanium Backup. My DZ is rooted with S-off, so it's all good.
I've stumbled over instructions on how to unlock the nexus4 via ABD, but if I'm not wrong, that's only to allow flashing of custom bootloaders and ROMs, right?
Which is to say, unlocking != rooting, and in order for Titanium Backup to work properly, the n4 will have to be rooted as well as SU, busybox etc installed.
Am I on the right track?
Cheers.

nexus come unlock.
unlock = to be use with any carrier
rooting = giving beyond standard permissions such as changing how android does things. EG overclocking, changing your sound "quailty" etc and you said. TB (titanium backup)

Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.

Unlawful said:
Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
Click to expand...
Click to collapse
Thanks Unlawful. Yes, I meant bootloader unlocking.
Unlawful said:
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.
Click to expand...
Click to collapse
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.

endlesstrail said:
Thanks Unlawful. Yes, I meant bootloader unlocking.
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
I doubt it. Be cool if it did
Once you have it unlocked you enter the recovery mode and root it there. I'm probably guessing shortly after its release someone is going to make a program so it does it in few steps.
There won't be anything really out that really requires root, other than TB.

endlesstrail said:
Thanks Unlawful. Yes, I meant bootloader unlocking.
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
Nexus 4 does not come rooted. You have to root it.

NeverAlwaysEver said:
Nexus 4 does not come rooted. You have to root it.
Click to expand...
Click to collapse
Thanks guys. I guessed as much.
Yeah, I'll probably have to do without the backup of my apps for a few days until some kind soul manages to root it and posts instructions. Maybe it'll just be a day or a few hours even! :fingers-crossed:

You will be able to unlock the bootloader right away.
Root maybe not. In order to root it you will need either need a custom recovery for the device or a software exploit.
It won't take long but a custom recovery needs to be built and tested first.

It's easy to root a nexus
First you unlock the bootloader=fastboot oem unlock.
Then you use fastboot to flash a recovery. Once recovery is flashed you have to use adb to make it stick(delete the script that overwrite custom recovery with stock) then you flash su. Zip in recovery. Very simple to do
Sent from my SCH-I535 using xda premium

Unlawful said:
Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.
Click to expand...
Click to collapse
Just want to clarify, I have not had a nexus device before, but my understanding is that, even on a Nexus, without unlocking the bootloader, one would still need to exploit and mount system as RW first to install SU.

USSENTERNCC1701E said:
Just want to clarify, I have not had a nexus device before, but my understanding is that, even on a Nexus, without unlocking the bootloader, one would still need to exploit and mount system as RW first to install SU.
Click to expand...
Click to collapse
Without unlocking the bootloader, it's much more difficult to root and as you said, one would need to use an exploit and then do as you have said. However, Nexus devices do come with the luxury of unlockable bootloaders for a multitude of reasons .
endlesstrail said:
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
I think Chainfire meant that in case you wanted to switch from Superuser to SuperSU or if you're just installing the APK (the application). If you do want to root, you should just flash the zip file found here in a custom recovery which does everything for you.

Unlawful said:
Without unlocking the bootloader, it's much more difficult to root and as you said, one would need to use an exploit and then do as you have said. However, Nexus devices do come with the luxury of unlockable bootloaders for a multitude of reasons .
Click to expand...
Click to collapse
Thanks. Bytheby, my only experience in the past with non-hack bootloader unlocking is with HTCunlock. Have past nexus devices had a permanent watermark even after relocking? I'm hoping that's not the case, cause extensive googling does not have anyone explicitly saying one way or the other, so maybe only HTC is that jacked.

I just want to clear up some terminology to stop people getting confused...
Bootloader a.k.a HBoot - This is the piece of software that runs before anything else on the phone. It basically packages it all up, tells what to run in what order e.t.c Every computer device has a bootloader in some form or another, be it an Android Phone, iPhone, Windows PC, iMac e.t.c. The HBoot is accessible by switching your phone off, then holding down volume down as you turn it back on. The first line of the HBoot will tell you if you are S-OFF or S-ON.
Recovery - The recovery is the piece of software that allows us to write files to partitions while they aren't being used. It is the portal to allow us to flash custom ROM's and kernels. There are custom recoveries with more options than the stock such as ClockworkMod.
Superuser a.k.a su or Root - This is a user that is present on all linux distros that allows higher permissions than standard users have access to. Certain apps need superuser permissions to function, such as Titanium Backup.
A bootloader is traditionally locked. This means it stops you from writing to any partition on the device other than data. What is always true of Nexus devices, and now true of most consumer devices, there is an offical method for unlocking the bootloader. With HTC, you have to download some software, with Nexus devices, it is as simple as booting into fastboot mode, and typing the command "fastboot oem unlock" (assuming you have fastboot installed on your connected PC / mac).
Although this unlocks the bootloader (which by the way resets your device to factory settings), you still aren't rooted. You now have the ability to flash images to the previously locked partitions. Once you have access to write to partitions, the easiest method of rooting is installing a custom recovery (fastboot flash recovery recovery.img, and then using that to flash a superuser zip.
There are exploits for rooting, which either eman the recovery partition gets written to without the bootloader unlocking OR the su files get pushed to the system partition while the bootloader is locked. These exploits are more tricky and are getting harder to find, but allow you to gain root access without voiding your warranty.
To answer someone else's question, when you unlocked the bootloader on the Nexus One you got a watermark on the bootsplash, I don't know about any Nexus after that.
EDIT - Unlocked Phone: To throw some further clarification, when people talk about "unlocked phones" what they actually means is carrier. This term pre-dates smartphones, and a locked phone just meant that if you bought your phone through a carrier, you could only use it on their network, so no other SIM would work unless you bought a code off them to unlock it. This only applied to GSM phones (not CDMA) and s still practised today. The Nexus 4 will not be carrier locked wherever you buy it.

l0st.prophet said:
I just want to clear up some terminology to stop people getting confused...
Click to expand...
Click to collapse
Thanks for the excellent clarification. It's much clearer now.

USSENTERNCC1701E said:
Thanks. Bytheby, my only experience in the past with non-hack bootloader unlocking is with HTCunlock. Have past nexus devices had a permanent watermark even after relocking? I'm hoping that's not the case, cause extensive googling does not have anyone explicitly saying one way or the other, so maybe only HTC is that jacked.
Click to expand...
Click to collapse
Both the Galaxy Nexus and the Nexus 7 don't have anything changed when you unlock the bootloader (apart from an unlocked lock image on the boot screen beneath the Google logo and then it disappears after going to the boot animation). I would assume this was the same with the Nexus S . Also another good thing about Nexus devices is that you can relock the bootloader after unlocking it and it will be back to a stock configuration (assuming you're on the Google-built ROM).

PlanBSTi said:
There won't be anything really out that really requires root, other than TB.
Click to expand...
Click to collapse
I beg to differ; DroidWall is the one utility I refuse to live without, and that requires root.
Other than that and TitaniumBackup though, you're quite right; the new stock features of JellyBean mean I likely won't even bother with any major third-party modifications. Indeed, I'm thinking this'll be the first 'phone in many a year which I won't be installing a custom ROM on for at least the first six months of use.

PlanBSTi said:
There won't be anything really out that really requires root, other than TB.
Click to expand...
Click to collapse
Lol, the irony is I really only use TB because I'm switching ROMs. I disagree though, I really like the extra customization that comes with a lot of custom ROM's. But I've run phones for a few months with OEM skins, while waiting on an exploit. I agree there won't be a pressing need for root.

I guess you guys like to actually see ads on your phones.

albundy2010 said:
I guess you guys like to actually see ads on your phones.
Click to expand...
Click to collapse
I actually don't find many apps to have very intrusive ads at all. I also feel better knowing I'm not ripping off the devs

albundy2010 said:
I guess you guys like to actually see ads on your phones.
Click to expand...
Click to collapse
I've never actually ended up with an air push app, and the rest of the ads really don't bother me, sometimes I'll go on a clicking spree to support devs. If it really bothers me I buy the full version or uninstall it.

[Q] Asus Google Nexus 7 Toolkit v4.0.0 - I just want to root and nothing else

Hi all,
After deeply snorkeling in the whole forum I ended up realizing that (perhaps) there's no answer for my question. So, I think now I'm able to post it here (since I'm so new in this forum that I'm not able to post in Development thread).
Ok, here is my issue:
I recently got my brand new N716G (JB 4.2.1), so far so good it has everything I need, except by game playing experience in some games: using a touch screen for playing some games is really anoying... The good news is that my gamming experience could be improved a little bit if I use my PS3 joystick, but again I got frustrated by the (again) anoying USB cable... I didn't give up and continued my journey to joy, by doing some extra research. I ended up finding a really nice tool on google play: "sixaxis controller" but it is required to root my device in order to run this software in my N7.
Since I just want to root my N7 in order to allow "sixaxis controller" to work, I need something really simple.
I've found that "Asus google Nexus 7 Toolkit" from mskip could help me on this but I've to be honest: I've never rooted an android device before.
Of course, I read almost the whole thread (link) in order to learn what I'm going to do and now I'm pretty sure that I really need to root my tablet but I'm not interested (at least now) on putting a custom ROM nor tweak any configuration. Also, I want to keep my tablet stil able to keep updating by itself whenever a new android version is coming (OTA) after rooting it (I know I'd need to re root after OTA but I might avoid that by installing another tool from google play that avoids that).
So, by using that tool I guess I would need to perform the following steps:
a) 1. Install Google Nexus drivers on your PC
b) 2. Back up your device
c) 3. Unlock your loader
d) 4. Root your device
e) 4.2. Root device + Install busybox
f) 2. Restore backup
Steps a) and b) are done. I didn't continue because I don't know if there's something else I've to do... Do I really need to flash a recovery? How should I continue? In my specific case, what sequence should I have to follow in order to succeed? Just a,b,c,d,e,f and that's all?
I know there's a "1-click for all" option but I don't know if that will fit my needs...
By the way, thanks for reading up to here and many thanks in advance... For sure, any help or tip will be highly appreciated.
Nico.

easiest way to gain root, and without a toolkit.. fastboot oem unlock(unlocks the bootloader), fastboot flash a custom recovery, flash the su binaries in that custom recovery, reboot.

simms22 said:
easiest way to gain root, and without a toolkit.. fastboot oem unlock(unlocks the bootloader), fastboot flash a custom recovery, flash the su binaries in that custom recovery, reboot.
Click to expand...
Click to collapse
Hi simms22,
thank you for your reply!
Sorry but I don't understand. Do you mean that I can root my N7 manually by fastboot it and then flash a custom recovery? How?
I'd rather let an application (or script) to perform such actions for me since I'm really new on this and I just want to avoid any brick
Thanks again!
Nico.

IlNiCoLiNo said:
Hi simms22,
thank you for your reply!
Sorry but I don't understand. Do you mean that I can root my N7 manually by fastboot it and then flash a custom recovery? How?
I'd rather let an application (or script) to perform such actions for me since I'm really new on this and I just want to avoid any brick
Thanks again!
Nico.
Click to expand...
Click to collapse
thats the problem, since youre new. by letting something else do it for you, you learn nothing. so when it comes time for simple maintenance, you get stuck, possibly ruining your device. rooting any nexus is easy, it was designed to be easily "rooted". all you need is to install fastboot onto your computer, and make sure the drivers are installed. there are a few threads here that explain how to do it. then, with one line(three words), you unlock the bootloader. with another four word line you flash the recovery. then all youndo is flash the su binaries zip imnthat custom recovery and reboot. anyways, it still comes down to it being your choice how you want to root your device

Agree with simms. I used a toolkit when I first got my Nexus because I thought there's no way I'll be able to figure it out and I'll probably brick the thing. Then when I had to figure out how to use adb for something else I had no idea and was starting from scratch.
Basically, go ahead, it's easy.

+1 for no toolkit. My first rooting experience was on my HTC IncS which involved downgrading HBOOT, doing everything manually, and the like. I'm glad that was the case as it certainly provided me a challenge at the time but it forced me to learn at least the basics of adb and fastboot. (although I certainly know more now) You should try to gain root manually as it is actually very easy on the Nexus 7 and the basic knowledge you will gain will stand you in good stead if you ever have any problems or want to delve into custom ROMs or kernels in the future.

simms22 said:
thats the problem, since youre new. by letting something else do it for you, you learn nothing. so when it comes time for simple maintenance, you get stuck, possibly ruining your device. rooting any nexus is easy, it was designed to be easily "rooted". all you need is to install fastboot onto your computer, and make sure the drivers are installed. there are a few threads here that explain how to do it. then, with one line(three words), you unlock the bootloader. with another four word line you flash the recovery. then all youndo is flash the su binaries zip imnthat custom recovery and reboot. anyways, it still comes down to it being your choice how you want to root your device
Click to expand...
Click to collapse
You're right. I guess I'll give that tool a try and see what happens.
Thank you for your patience!
Nico

I'm going to throw one thing out there. If you install super user and busy box THEN restore a backup, all you have done is unlocked your boot loader and flashed custom recovery. Install super user/busy box after you restore your backup. Also, you posted in the right section. If you had posted this in development you would have been flamed. Big time.
Sent from my Nexus 7 using xda app-developers app

I think there are some basics that I must learn before even rise an opinion here
Is there any tutorial or something you'd recommend to start with?
I don't know, may be "android rooting for noobs" or "teach yourself android basics in 21 days"
Thanks!
Nico.

As a fellow noob, I thought you'd appreciate a simpler answer. I'd like to learn more but it can be confusing having all these different methods to consider. I've just unlocked the bootloader and rooted the device using the toolkit. You can go ahead with steps c, d, e & f Nico. You don't need to install a custom recovery unless you plan on flashing a custom rom. I'm sticking with the official OTA updates for now so I've stuck with the stock recovery.
Sent from my Nexus 7 using xda app-developers app

For future reference read all these links
http://forum.xda-developers.com/showthread.php?t=2070419

Used wugfresh toolkit with not one single problem and its simple...in fact I even rooted my galaxy nexus with the same toolkit.
Sent from my Nexus 7 using xda premium

FlexiPack said:
As a fellow noob, I thought you'd appreciate a simpler answer. I'd like to learn more but it can be confusing having all these different methods to consider. I've just unlocked the bootloader and rooted the device using the toolkit. You can go ahead with steps c, d, e & f Nico. You don't need to install a custom recovery unless you plan on flashing a custom rom. I'm sticking with the official OTA updates for now so I've stuck with the stock recovery.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you, FlexiPack! You really made my day with your reply.
Regarding the back up, I was not able to back up the virtual SD from the back up menu (0 files were backed up) but I did a complete applications backup (including system files and SD card). I don't know what was the difference but at the end, the .bak file was noticeably bigger. Hence I assumed that in fact all SD contents were backed up.
How was your experience with the backup option and after restoring your data? Did you lost something?
Again, thank you!
Nico.

Hello there guys, I too am a utter android noob and this my my first android device. I'm basicly in the same boat as the poster, all I want to do is root. No custom ROM and flashing of any sort. All I want to accomplish is root to enable USB OTG.
I know there are apps that enable reading such as Nexus media importer but I want to be able to read and write data to external storage via USB (Flas drives, external hard drives and cameras and the sort)
What I've discovered the first big step (after installing drivers and the lot - which is all rather simple) is to unlock the bootloader if I'm correct? But in this process the device will format? I honestly dont want to format my device. I'm totally confused and put off by the whole process.
Another question, what is a good backup program to use - of course for unrooted devices.
Sent from my Nexus 7 using xda app-developers app

smartass145 said:
Hello there guys, I too am a utter android noob and this my my first android device. I'm basicly in the same boat as the poster, all I want to do is root. No custom ROM and flashing of any sort. All I want to accomplish is root to enable USB OTG.
I know there are apps that enable reading such as Nexus media importer but I want to be able to read and write data to external storage via USB (Flas drives, external hard drives and cameras and the sort)
What I've discovered the first big step (after installing drivers and the lot - which is all rather simple) is to unlock the bootloader if I'm correct? But in this process the device will format? I honestly dont want to format my device. I'm totally confused and put off by the whole process.
Another question, what is a good backup program to use - of course for unrooted devices.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Toolkit you can backup the whole thing to your comp
Sent from my Galaxy Nexus using xda app-developers app

VonEsch said:
Toolkit you can backup the whole thing to your comp
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Alright, and formatting to unlock the bootloader?
Sent from my Nexus 7 using xda app-developers app

This is kind of a rant but applies here: Don't be afraid to unlock, install custom recoveries, and root.
I hear so many people say, "I just want to be stock... but I want all these features". I can't understand why people hold on to this "stock" state so dearly. It's like device virginity (and it is since you "can't" [mentally] really ever go back). There are so many features and updates that are worth enjoying today. At least, a custom recovery is critical for backups.
I understand this stuff isn't for everybody... but if you are reading this, you aren't grouped with everybody.

player911 said:
This is kind of a rant but applies here: Don't be afraid to unlock, install custom recoveries, and root.
I hear so many people say, "I just want to be stock... but I want all these features". I can't understand why people hold on to this "stock" state so dearly. It's like device virginity (and it is since you "can't" [mentally] really ever go back). There are so many features and updates that are worth enjoying today. At least, a custom recovery is critical for backups.
I understand this stuff isn't for everybody... but if you are reading this, you aren't grouped with everybody.
Click to expand...
Click to collapse
For me vanilla android offers me everything I need at the moment. All I want more from it at the moment is USB OTG functionality - which it has its just been locked by Google for this device.
Sent from my Nexus 7 using xda app-developers app

For all people who call themselves noobs, you really aren't cuz you now know certain things better than the average user.
Trust me, I saw a Customer buying Note 2 today, and when the sales guy told him that it's jelly bean, the retort was "what's that!!!"
And yes, all nexus devices are the easiest lot to root, unroot, unlock and then relock.
Trust me, Google and xda are your best friends.
Just remember one thing, backup before anything, you can always revert then!!!
You guys (noobs as you yourself call) have already jumped, now swim...
One most important thing, search, read, and take the plunge...
All forums have at the least one tutorial stickied!!!
As regards adb, fastboot, google, read, and trust me, you'll not be stuck for more than an hour!!!
Just my 2 cents, actually more!!
Sent from my Galaxy Nexus using xda app-developers app

It really is like that. But once you start you can't stop. I started by rooting my original android phone ( there were no toolkits and no problems) and ended up with two nexus devices compiling unofficial nightlies for them. I didn't even boot stock on my 7 before I flashed twrp. There's a whole world of fun if you're willing to get your feet wet. If you can stop with just root you're a stronger person than I.

[Q] Which root method for Sprint version

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:

Easy 2 click root: How I got to 4.2.2 Camera Update/Rooted and WP permanently Off

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: