Related
Hello there
Got myself a nexus 10 and to say I'm jealous of some of the homescreen posts is an understatement it really has me salivating when I see those custom icon packs coupled with a 2560x1600 resolution. I'm reasonably tech savvy myself but find the task of rooting my device a daunting one. I Find it difficult to follow all the steps and I'm afraid to mess it up and to be left with a device the won't even power on and as I live in Ireland it will prove difficult to send back for repair. Device still not available here officially. Anybody know an extremely easy reliable root?.just wanna run flash and customise the appearance a bit and maybe a little over clocking Any suggestions are welcome.
Thanks in advance
Thanks
Sent from my GT-I9300 using xda premium
rdsreference said:
Hello there
Got myself a nexus 10 and to say I'm jealous of some of the homescreen posts is an understatement it really has me salivating when I see those custom icon packs coupled with a 2560x1600 resolution. I'm reasonably tech savvy myself but find the task of rooting my device a daunting one. I Find it difficult to follow all the steps and I'm afraid to mess it up and to be left with a device the won't even power on and as I live in Ireland it will prove difficult to send back for repair. Device still not available here officially. Anybody know an extremely easy reliable root?.just wanna run flash and customise the appearance a bit and maybe a little over clocking Any suggestions are welcome.
Thanks in advance
Thanks
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Check the original android development section there's a nexus 10 toolkit that will unlock the bootloader and root along with a bunch of other features. Of course, learning how to use adb commands are best, but if you want a quick fix, use the toolkit.
If you mess up, as long as you managed to get as far as flashing a custom recovery you can fix just about any mistake. And even if you broke it all (which is HIGHLY unlikely) before you even flashed a custom recovery, you can still fix just about any problems you made. I actually just helped another guy who screwed up his tablet pretty bad if you want to read my post on how to get out of a jam:
http://forum.xda-developers.com/showpost.php?p=37019359&postcount=10
As for unlocking, if you follow the first few steps of my other post you will have the Android SDK downloaded and the files you need in an easy to access folder. From there you will just want to download a custom Recovery .img file, like this one here:
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.3.3.0-manta.img
and do the commands:
fastboot oem unlock
Then follow the couple steps on your tablet to confirm the unlock. Copy that recovery .img file you downloaded into your Android-SDK folder, and then use the command:
fastboot flash recovery blahblahblah.img (where blahblahblah is the actual file name of the recovery image you downloaded)
Once done then use the volume buttons to go down the fastboot menu on your tablet until it says "Recovery", press the power button to confirm booting into recovery.
Then download this file and place it in the Android-SDK-Windows directory:
http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip?retrieve_file=1
and use the command:
adb push CWM-SuperSU-v0.98.zip /data/media/0
Which will push the file to your tablet (or alternatively instead of pushing through ADB just start your tablet like normal and copy the file the normal way from your computer to your internal storage)
Once the file is copied/pushed then in your recovery go to the install menu and flash it. This will flash root to your current ROM. Then you should be dine, you are now unlocked on the stock ROM with root. Alternatively, instead of flashing root, you can just go straight away to flashing a custom ROM since those already have root access anyway.
It really is quite easy and simple. Should take 5-10 minutes tops. If you want to lock the tablet again then find a completely stock ROM (or google how to reset and flash the original RUU) and flash it to your tablet and then do the same thing as unlocking but use the command: "fastboot oem lock"
http://forum.xda-developers.com/showthread.php?t=2015467
Wugfresh has a toolkit that's foolproof. As long as you follow the directions and slowly go through each step, ensuring you're reading everything carefully, you'll be fine. In the OP of the link I provided is another link that takes to to a YouTube video of the Nexus 10 being unlocked and rooted using the toolkit. It goes step-by-step, so follow along with the video, do EXACTLY as he does, and you'll have no problems.
Just use cf-root, takes less than 10 sec and very straight forward
Sent from my Nexus 10 using Tapatalk HD
Does the name qbking77 mean anything to you??
Sent from my Galaxy Nexus using Tapatalk 2
Just use superboot, you won't loose data and won't need to unlock bootloader or install a custom recovey...
gmfeny said:
Does the name qbking77 mean anything to you??
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The link I provided has a link to qbking77's YouTube video showing the Nexus 10 being unlocked and rooted using Wugfresh's toolkit.
Rodeojones said:
The link I provided has a link to qbking77's YouTube video showing the Nexus 10 being unlocked and rooted using Wugfresh's toolkit.
Click to expand...
Click to collapse
Yea I know that's what I used when I rooted mines!
Sent from my Galaxy Nexus using Tapatalk 2
Well unlocking the boot loader is possible but when rooting the nexus 7 gets stuck in fastboot when its suppose to be rebooting its self oh well I been at it all night so now I realized its impossible
Sent from my Nexus 7 using xda app-developers app
Use the toolkit, worked great for me. I couldnt get the adb right so I tried that. My nexus 4 was easy without the toolkit though..
Sent from my Nexus 4
I get a error saying failed <remote: <>
Sent from my Nexus 7 using xda app-developers app
If you can unlock the boot loader, you can do *anything* to your tablet starting with fastboot.
Learning to install drivers is a Windows issue - the skills needed to analyze & resolve driver problems have almost nothing to do with what device is attached to the other end of the USB cable.
Toolkits are a crutch for avoiding learning a very small number of skills; if you don't want to learn those skills, probably you shouldn't be rooting.
Throw away your toolkit and read the fastboot thread. The whole process is far easier than you think.
How come y'all help everyone else but I can't even get a hint on what I'm suppose to do I'll just return my tablet and get a new one Cruz obviously its gotta be my tablet
Sent from my Nexus 7 using xda app-developers app
I'll just go to yahoo answers I'll have more help there
Sent from my Nexus 7 using xda app-developers app
Class_of_punk26 said:
How come y'all help everyone else but I can't even get a hint on what I'm suppose to do I'll just return my tablet and get a new one Cruz obviously its gotta be my tablet
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
If you unlocked the bootloader and you're having trouble rooting your device then I don't see you being able to relock the device either, which is critical to do before returning it as technically an unlocked device is out of warranty.
And you say no one is helping you, but you haven't provided any information at all. We have no idea what you did to even cause that error, and you were recommended just to use a toolkit if you want, as that is an easy approach, and you haven't responded on whether you have done that either.
Exactly, how is anyone supposed to help if you don't tell us what you did.
How did you unlock fast boot? What did you try to get rooted?........etc
User is informed of multiple posts. So hopefully, with your help, the root issue can get resolved.
User MUST tell people exactly the steps taken to replicate the error. Including PC type and Operating System.
I hope we do not see duplicated posts anymore.
So if some of you more experienced users, can do some "hand holding" and walk him through the steps, then it will be appreciated. As clearly, he has issues on his own.
Do it for XDA...
MD
bftb0 said:
If you can unlock the boot loader, you can do *anything* to your tablet starting with fastboot.
Learning to install drivers is a Windows issue - the skills needed to analyze & resolve driver problems have almost nothing to do with what device is attached to the other end of the USB cable.
Toolkits are a crutch for avoiding learning a very small number of skills; if you don't want to learn those skills, probably you shouldn't be rooting.
Throw away your toolkit and read the fastboot thread. The whole process is far easier than you think.
Click to expand...
Click to collapse
I agree 100% on Toolkits
That sounds like a windows driver issue. I had a similar issue when rooting my N7.
Open device manager
Look for Nexus 7
Does it have the yellow triangle on it? If yes, then your ADB driver is not installed, or not installed correctly
In ADB mode it should show up in the device manager as Android ADB Device (or something similar)
arclight25 said:
That sounds like a windows driver issue. I had a similar issue when rooting my N7.
Open device manager
Look for Nexus 7
Does it have the yellow triangle on it? If yes, then your ADB driver is not installed, or not installed correctly
In ADB mode it should show up in the device manager as Android ADB Device (or something similar)
Click to expand...
Click to collapse
Yeah, this was my problem.. That's the only reason I used the toolkit. It wouldnt install right after downloading USB driver through SDK . got me pissed off and uninstalled every driver, and installed my nexus 4 all over also. Some how that one went easy..
Sent from my Nexus 4
LOL op went to yahoo answer, hilarious!
If he is still reading this, USE THE GOD DAMN TOOLKIT FFS, its pretty much idiot proof.
Yea, toolkit is the only way to go.
I think he is stuck in the same place I am stuck in. Whenever I get to the "Reboot Bootloader" in the Toolkit, it fails to go any further. I've made a thread about it here: http://forum.xda-developers.com/showthread.php?p=37524971
The toolkit isn't for everyone, unless of course I'm doing something wrong.
as long as toolkit detects your device, you can simply flash the google image and have everything reset, i dont see how that isnt for everyone honestly......
I used Wugfresh's toolkit and everything worked easily. I dont know any other way to do it, and the toolkit makes it easy for Gnex or Nexus 7.
I been at it all day guess I should just wait till something comes out for 4.2.2?
Sent from my Nexus 7 using xda app-developers app
If you don't know how to search on forums, there is something called "Google".
You ask, Google gives the answer. Easy stuff
I am backing up my n7 and setting to factory everything, including locked bootloader just to prove its possible
Code:
C:\temp\nex7>fastboot flash recovery openrecovery-twrp-2.4.1.0-grouper.img
sending 'recovery' (7182 KB)...
OKAY [ 0.951s]
writing 'recovery'...
OKAY [ 1.760s]
finished. total time: 2.718s
flashing recovery works fine
Code:
C:\temp\nex7>adb shell
[email protected]:/ $ su
su
[email protected]:/ #
yep. rooting works just like every other nexus device on any version.
Rooting via Nexus Root Toolkit v1.6.2 for 4.2.2
Hey all,
It seems like the OP may not have too much experience like me based on his post count. The responders on the other hand seem like guru's.
Well I did some troubleshooting after 4.2.2 to try to get the rooting to work (yes, i used google search). Just for the record I'm new to all this, but I've been doing a lot of goog'ling and figured the time I spent troubleshooting may be of help to other novices.
Apparently the rooting issue is well known if you're using the Nexus Root Toolkit v1.6.2 to try and do your rooting. There's a fix available which is described on the main webpage (between the red lines)
google wugfresh for homepage (I can't post links yet)
Just download the zip file and unzip in the folder described, overwriting what's already there there. Make sure your drivers are working . They were acting really finicky for me when using the toolkit but I finally troubleshooted it. If you're having issues you may want to try the newest PdaNet driver, although I didn't have to. Once your drivers are fine, select the Android "any" option and hit root with Custom Recovery checked. I dunno about everyone else but my Custom Recovery was gone/messed-up after upgrading to 4.2.2
If you don't use Nexus Root Toolkit, I recommend it for the less computer savvy ppl out there, like me. Hopefully they'll come out with an update.
Hope this helps.
One newB question I have is can I install my 4.2.1 custom ROMs after upgrading to 4.2.2? I'm not sure if there's some kind of firmware component of 4.2.2 that'll render my Nexus 7 incompatible with the 4.2.1 custom ROMs out there. If it's not okay is it possible to downgrade back down to 4.2.1 from a factory image and then install these custom ROM's?
Thanks ahead of time.
Here's a tip, it seems like your a noob with the nexus 7. In order to mod this thing you should familiarize yourself with command prompt.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jesus people hate noobs here, why doesnt some just show them how to get adb and fastboot going, instruct on how to properly instal the adt and jdk bundles inc path etc. there are no easy tutorials for noobs, if people are expect to learn then teach them, dont forget we were all noobs once.
Sent from my Nexus 7 using XDA Premium HD app
This might help. Go to this link and download the 4.1.2 (JZO54K) image for nexus7 wifi only if that's the one you got and downgrade everything to that and then root and download and install Chainfires SuperSU and SuperSU-Pro from the market and after you install that open SuperSU and check mark Survival Mode and then do the OTA update and you will still have root. Yes you can downgrade. I had to downgrade back to 4.2.1 and do what i said above. You have to have SuperSU Pro installed to use survival mode. its worth the price it cost.
https://developers.google.com/android/nexus/images#nakasi
After downloading the correct images from the link above
Follow these instructions
Nexus 7 Back to Stock
Step 1. fastboot erase boot
Step 2. fastboot format cache
Step 3. fastboot erase recovery
Step 4. fastboot format system
Step 5. fastboot format userdata
Step 6. fastboot flash bootloader bootloader-grouper-x.xx.img
Step 7. fastboot reboot-bootloader
Step 8. fastboot -w update image-nameofzip.zip
Step 9. fastboot reboot-bootloader
After you downgrade your device doing all the steps above then go and root the nexus 7 and install SuperSU and SuperSU-Pro check mark survival mode in superSU and Install busybox also from the google playstore and then do the ota update.
Unlock Boot Loader
fastboot oem unlock
fastboot reboot-bootloader
Lock Boot Loader
fastboot oem lock
fastboot reboot-bootloader
I was 4.2.1 would this still work?
Sent from my Nexus 7 using xda app-developers app
gastonwalpole said:
jesus people hate noobs here, why doesnt some just show them how to get adb and fastboot going, instruct on how to properly instal the adt and jdk bundles inc path etc. there are no easy tutorials for noobs, if people are expect to learn then teach them, dont forget we were all noobs once.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
We don't like noobs because we don't like seeing the same posts over and over and over. I remember when I was a noob, I had no help. I wasn't a member of xda so I learned everything on my own, lots of soft bricks, lots of Googling, and lots of sleepless nights. That's how everyone should learn. You learn more by figuring it out yourself, not being told how. This guy has been told how to root in about every thread he's posted but wont listen. Look at the 5 other posts he's posted, you'll understand why we're annoyed.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
lol
fastboot oem unlock it
fastboot flash a custom recovery
then in that recovery flash the supersu zip from chainfire's thread. I just did this from fully stock and now its rooted
Class_of_punk26 said:
I been at it all day guess I should just wait till something comes out for 4.2.2?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I dunno whats all this fuss about, root 4.2.2 via Nexus 7 toolkit.
I checked today, installed stock 4.2.1, and ota to 4.2.2 than rooted via Nexus 7 toolkit. Select 2nd option, and 2nd option again "install root and busy box". :good:
markj338 said:
lol
fastboot oem unlock it
fastboot flash a custom recovery
then in that recovery flash the supersu zip from chainfire's thread. I just did this from fully stock and now its rooted
Click to expand...
Click to collapse
Sorry i was just trying to help.
AndroidSmitty said:
Sorry i was just trying to help.
Click to expand...
Click to collapse
Hey I wasn't hating on you
I was just saying that if the OP already has 4.2.2 its easy to do it by flashing the supersu zip.
spitfire2425 said:
We don't like noobs because we don't like seeing the same posts over and over and over. I remember when I was a noob, I had no help. I wasn't a member of xda so I learned everything on my own, lots of soft bricks, lots of Googling, and lots of sleepless nights. That's how everyone should learn. You learn more by figuring it out yourself, not being told how. This guy has been told how to root in about every thread he's posted but wont listen. Look at the 5 other posts he's posted, you'll understand why we're annoyed.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Spitfire, it may have occurred to you that not everybody wants to go through that process, reinventing the wheel. Granted, the best way to learn something is doing it and making mistakes, but not always so for someone who just wants to get the job done rather than understand. This is why people here create guides.
If noobs annoy you so much, just let it go and do something else. Leave those with a better temperament to help them.
What's really annoying about this cat is that he has a minimum of 5 threads that he opened for the same issue.
you think thats acceptable behavior?
gastonwalpole said:
jesus people hate noobs here, why doesnt some just show them how to get adb and fastboot going, instruct on how to properly instal the adt and jdk bundles inc path etc. there are no easy tutorials for noobs, if people are expect to learn then teach them, dont forget we were all noobs once.
Click to expand...
Click to collapse
You've probably noticed by now that ROM devs and kernel devs rarely step in over here. There's a reason for that - what they do takes serious amounts of time (usually apart from their day jobs or studies) - and for every one of them there are literally hundreds of less skilled folks asking questions. If they tried to help, they simply wouldn't accomplish their positive contributions.
The other difficulties are:
(1) Forums organize info into a horrible format for learning
(2) The pace of technological change tends to invalidate even valuable posts rather quickly.
That first assertion (1) is made even worse by a flood of posts that scroll valuable (non-stickied) threads off to infinity.
Paradoxically, newbs that insist on creating their own threads for issues that closely resemble the issues covered in other threads are actually, yes, making the site worse for others - especially other newbs that seem to avoid using search.
In the case of this particular OP, he had threads closed and was issued a warning by a mod for exactly the behavior being repeated again here.
Well, if YOU want to create a tutorial, I would encourage you to do so ... & also try to get a mod to sticky the thing.
But don't come in here and say "somebody besides me should do this for the newbs". That's just lame.
The easiest way for beginners is to use Wug's toolkit. All you have to do it update the adb files in the install directory and it will all work. http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 <-- Look there
im not an expert yet mate, just started using xda, what i know ive researched, its hard for noobs to find the info required, i dont understand why it has to be so hard for people, if info already exist here why doesnt anyone point them in the right direction, i just dont want others to go through what i went through, people dont talk to each other with respect here, id like to see if they are that up front face to face. once im more confident i will help others dont worry about that, i am trying to already.
cheers
Sent from my Nexus 7 using XDA Premium HD app
Hi, now most people here are smart with this type of thing soooo i wanted to ask you how i can root the nexus 7 running 4.2.2. I tried to use the wugfresh NRT but when I was installing drivers a problem occurred. Instead of having ADB drivers or something like that I had ADB Composite drivers installed even though i followed the guide completely and I have tried several times to correct this but i havent found a solution. Also i attempted to carry on the rooting process but it said i did not have the correct drivers installed and etc. So can someone give me a fool proof way of getting the right drivers for this thing so i can root so i can finally install some kernels and use the sixaxis controller app! sorry for the essay and all help is appreciated
hrsedJe Something
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
Dude, most commands for doing stuff on the N7 manually are four words. It really isn't a lot to remember. Also I don't think you understand the purpose of this site/forum.
..That being said.
Use Wug's toolkit and update the adb files in its install directory. Then just use the 4.2.1 settings if 4.2.2 doesn't show.
Here is a post with the files: http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650
sucks that the toolkit is only for windows, sucky windows
Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2019519
had the same problems
Just google fastboot files for n7, get sdk and pack files AND the recovery into the sdk tool folder.
Shift+right click -> start command here
Fastboot flash recovery recovery.img
Start tab abd sideload the SU.zip (google superuser)
Flash
Done ))
Did it yesterday no issues!
phonic said:
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk
Click to expand...
Click to collapse
Well said phonic. I prefer the manual way as well. It is always good to know what you are doing, but knowing how it works and learning something is always better.
I would much rather learn something than to have someone do it for me. If ever I need help and ask someone, they say I'll do it for you I say no, please show me how to do it!
Sent from my Nexus 7 using Tapatalk 2
kidujp said:
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.
Click to expand...
Click to collapse
You may receive an error message "ABD" is offline, in this case download the latest Android SDK manager and upgrade all USB drivers before using the toolkit again.
Sent from my Nexus 7 using xda app-developers app
phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Never ceases to amaze me how many pretentious pricks use XDA.... Reminds me of Apple snobs.
command line is the way to go
command line is the way to go m8!!
cheers,
geek endangered
So for the past weeks I've been looking in to flashing PA ROM on my nexus 4 , Honestly I'm kind of nervous that I will end up Bricking it... its completely Stock ATM . I noticed a few people saying not to use a toolkit, but to me it seems a lot easier, even to get it back to stock if I needed to . So how many have used a toolkit ? Any Problems Major issues ?
Sent from my Nexus 4 using xda app-developers app
yes
Sent from my Nexus 4 using xda app-developers app
Did you use this one?
http://forum.xda-developers.com/showthread.php?t=1995688
Toolkits aren't bad it's when people use them but have no idea what it is doing that is bad.
Your phone goes into a bootloop then you don't know how to fix it. If you don't know the 6 partitions in the Google.imgs how to use adb or fastboot don't use a toolkit
Edit: http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4
g2uzer said:
Did you use this one?
http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
I used Mr Skip's and it worked really well, most important thing to get right is installing the drivers on your PC, I donated to him cause it has so many options and worked so well
Never have and never will. Once you learn fastboot it's too much fun playing in the command prompt lol.
spaceman860 said:
Toolkits aren't bad it's when people use them but have no idea what it is doing that is bad.
Your phone goes into a bootloop then you don't know how to fix it. If you don't know the 6 partitions in the Google.imgs how to use adb or fastboot don't use a toolkit
Edit: http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4
Click to expand...
Click to collapse
Yeah I have read about phone going in to bootloop and it seems like a easy fix from what I read, the only phone I have rooted was a g2x thru a kit, so yeah I'm mostly a noobie, I've done a lot of reading but I usually ask my friend to do it for me since he knows A LOT more than me , I seen him unlock,rooot a few phones with out kits,,but to me it seems a lot more steps and there for more chances of me messing something up, so the only possibility you have thru rootkit is your phone going to boot loop ?
I have read mrskip but seems that this one looks easier (I think so )
http://forum.xda-developers.com/showthread.php?t=1766475
g2uzer said:
Yeah I have read about phone going in to bootloop and it seems like a easy fix from what I read, the only phone I have rooted was a g2x thru a kit, so yeah I'm mostly a noobie, I've done a lot of reading but I usually ask my friend to do it for me since he knows A LOT more than me , I seen him unlock,rooot a few phones with out kits,,but to me it seems a lot more steps and there for more chances of me messing something up, so the only possibility you have thru rootkit is your phone going to boot loop ?
I have read mrskip but seems that this one looks easier (I think so )
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
spaceman860 said:
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
Click to expand...
Click to collapse
i disagree with you..
instead of using "done", id use "profit" :silly:
spaceman860 said:
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
Click to expand...
Click to collapse
Good i found this thread, ill get an n4 soon and just wanted to check things out. I am comfortable with fastboot, and ADB(done everything with one v).
So its like this right?
fastboot oem unlock (cant believe its this simple, you have to use an unlock token to unlock an HTC boot loader)
fastboot flash recovery recovery.img same with the one v
Root by flashing zip.
After that simply enjoy flashing. Am i right? Also, do you need to flash kernels while changing ROMs like on hTC phones?
Just read, someone mentioned that if you don't know the 6 partitions you better not flash. Which 6 partitions?
Sent from my One V using xda app-developers app
soham_sss said:
Good i found this thread, ill get an n4 soon and just wanted to check things out. I am comfortable with fastboot, and ADB(done everything with one v).
So its like this right?
fastboot oem unlock (cant believe its this simple, you have to use an unlock token to unlock an HTC boot loader)
fastboot flash recovery recovery.img same with the one v
Root by flashing zip.
After that simply enjoy flashing. Am i right? Also, do you need to flash kernels while changing ROMs like on hTC phones?
Just read, someone mentioned that if you don't know the 6 partitions you better not flash. Which 6 partitions?
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
yup, thats it. fastboot oem unlock, fastboot flash a custom recovery, flash a custom rom or the su binaries via your new custom recovery, then reboot and profit. you dont have to flash kernels since all custom roms include them. but, you can and should flash custom kernels to better your device
simms22 said:
yup, thats it. fastboot oem unlock, fastboot flash a custom recovery, flash a custom rom or the su binaries via your new custom recovery, then reboot and profit. you dont have to flash kernels since all custom roms include them. but, you can and should flash custom kernels to better your device
Click to expand...
Click to collapse
Is there a updated video doing it this method? ( not using any rootkit) I'm more of a visual learner
Can't seem to find one.
After unlocking every thing I know how to flash ROMs, just the unlocking is what got me nervous .
Thanks
Sent from my Nexus 4 using xda app-developers app
g2uzer said:
Is there a updated video doing it this method? ( not using any rootkit) I'm more of a visual learner
Can't seem to find one.
After unlocking every thing I know how to flash ROMs, just the unlocking is what got me nervous .
Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd like a video of this too.
Can you brick your phone while unlocking? Or just while flashing?
g2uzer said:
So for the past weeks I've been looking in to flashing PA ROM on my nexus 4 , Honestly I'm kind of nervous that I will end up Bricking it... its completely Stock ATM . I noticed a few people saying not to use a toolkit, but to me it seems a lot easier, even to get it back to stock if I needed to . So how many have used a toolkit ? Any Problems Major issues ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
use the nexus 4 toolkit by msskip..
its the best one so far and very easy to use...and dont worry abt bricking..
post if any issues,,.
No toolkit. It's important to know how to use fastboot.
Sent from my Nexus 4 using Tapatalk 4 Beta
Unlocking the bootloader and rooting for new users
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
sparkplugDev said:
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
Click to expand...
Click to collapse
Thanks a lot ! When I get home I'm going to read this for the 3rd time .
So if I want to go back completely stock I can use a toolkit ?
Sent from my Nexus 4 using xda app-developers app
g2uzer said:
Thanks a lot ! When I get home I'm going to read this for the 3rd time .
So if I want to go back completely stock I can use a toolkit ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah, like I said, the toolkit makes it a lot easier to flash a factory image and frankly, I think it's safer. Less room for mistakes. The less you toy around with flashing the bootloader and the radio, the better chance you have of not bricking your device. Fortunately, when your bootloader is unlocked, as long as you aren't doing anything crazy, you will have a hard time bricking your device. If you have any further questions while you're working on it shoot me a PM and I will try to help. Good Luck!
sparkplugDev said:
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
Click to expand...
Click to collapse
Superb, all this I know already as I did this with one v
But, I read in some tutorial that if you don't reboot to stock recovery and data reset your phone AFTER you've unlocked the boot loader, you will end up with a soft brick? Is it true?
Sent from my Nexus 4 using xda app-developers app
I've been playing g with androids for a long time and dozens of devices. Personally have never used a toolkit and its hard for me to recommend or knock them.
My view is a toolkit teaches you nothing
If a toolkit was made so was another method
Everyone will have an issue with something at some point, so the more you learn now the less freaking out latter
Learning to do thongs yourself will always be safer, I mean yes manually typing a dd command can be dangerous but if you know what you are doing you know when to be cautious, there will always be an example for either argument on this, but I truly can't see a reason to believe a tool kit is safer
But I'm a to each their own sorta guy, but also one who feels the need to learn as much as possible so will promote as much manually methods for anything in life and will do my best to stay away from auto-just-about-anything.... Just a my $.02
Sent from my Nexus 7 using xda premium