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
Related
Pardon my boldness but I have been on this forum now for awhile and been reading and getting alot of very good information on ROOTING.
I have yet to ROOT my Hero and I am really in a struggle to do so because it seems to me that those of you, for the most part, who have ROOTED your phones are the same people who are having all the problems with this and that appearently because of the ROOT. I mean that folks with stock Hero's very rarely say that something isn't working as it should. App's withstanding. I refer to stock features only.
Reading the problems is the Who's Who of why I think it not a wise choice for me to ROOT at this time.
Anyway, I had my say and my stock Hero works just fine with its 1800 from Mugen. Remember, its a phone, not a pc even tho it share's some pc features.
Thanks for listening...and for a great place to learn.
The key piece of information to remember is that rooting does't cause the issues we experience. It's the custom ROMs and hacks we install that cause problems
I think most everyone here remembers that we're doing these things at our own risk.
As for the OP, if you don't feel a desire for the features available after rooting or flashing a custom ROM, that's cool. It's not for everyone.
Rooting, flashing, hacking... it's for tinkerers. People who like to find out why something does or doesn't work and then find a fix for it.
I would place a bet on this:
The people who don't have root or don't want to root, and they rarely post their issues in comparision with those who have rooted.
Yes, Most of the issues you see here are self inflicted, but it's what we do. We like a challenge/problem, it gives us something to do. Another reason to stay up till 3 in the morning to find out WHY it's jacked up.
If your issues are so bad, RUU and stick with stock (A whole new set of issues).
We mention our problems so that developers can try and fix them for the next release. In all honesty, Ive had one 1 problem, that was when I installed AOSP 1.6, which btw is/will not supported by our phone officially, I got the dreaded SMS issue that SOME people are experiencing.
Well yea many people post about issues who are rooted, but it is caused by other things they are doing that require it. Simply rooting your device shouldn't cause anything to go wrong.
Roms and other things that require root access tend to be beta, and even if they are not beta they are created by people, and not everything will be perfect.
It is pretty hard to permakill your hero compared to other devices. The only way I know of using the software is through flashing the radio, or messing with ESID and stuff like that.
Which you aren't supposed to do .
Yo Is_907
Not quite the 1st reply I was expecting but a very nice understanding instead. You SIR are a gentlemen and I thank you.
Yes, at the ripe old age of 62 I do believe ROOTing and all that goes with it are for you younger folks who have grown up with computers and like devices. I do tinker somewhat and in fact, my wife and I host a private FREE World of Warcraft ( WOW )server. Been hosting online game servers for about 9 years now and we love it.
Once again, thanks and as you said, I probably need alot more schooling before I would attempt a ROOT. My only problem is AWAKE time, its really high even tho I have removed those apps I can remove to help that situation. Hopefully, 2.1 will help us Non Roots somewhat but if not, then I will strongly consider ROOTing. As long as I know there are people like yourself to help us old dudes.
Thanks again Is_907, and to the rest of you who voiced your opinions, Thanks. All good points and even more reason to consider ROOTing.
rdisanza said:
Pardon my boldness but I have been on this forum now for awhile and been reading and getting alot of very good information on ROOTING.
I have yet to ROOT my Hero and I am really in a struggle to do so because it seems to me that those of you, for the most part, who have ROOTED your phones are the same people who are having all the problems with this and that appearently because of the ROOT. I mean that folks with stock Hero's very rarely say that something isn't working as it should. App's withstanding. I refer to stock features only.
Reading the problems is the Who's Who of why I think it not a wise choice for me to ROOT at this time.
Anyway, I had my say and my stock Hero works just fine with its 1800 from Mugen. Remember, its a phone, not a pc even tho it share's some pc features.
Thanks for listening...and for a great place to learn.
Click to expand...
Click to collapse
There's not an issue with rooting in and of itself. Take me for instance. I've had some problems with my phone:
1. Apps2SD didn't work...but that was part of a ROM that was being beta tested.
2. Kernel locked up...that was due to an invalid setting I put into the kernel I was building.
3. Lost CPU kernel control...this is something I'm doing wrong in the kernel I am building. I simply restore a control file from a previous build and recompile.
These are things that were expected in testing and needed to be fixed or that I inflicted on my own.
I have a friend who has rooted his Hero, but hasn't applied any of the custom ROMs to his phone (although he has installed applications that require root). He's never had an issue with the phone.
It really depends on what you use it for.
rdisanza said:
Yo Is_907
Not quite the 1st reply I was expecting but a very nice understanding instead. You SIR are a gentlemen and I thank you.
Yes, at the ripe old age of 62 I do believe ROOTing and all that goes with it are for you younger folks who have grown up with computers and like devices. I do tinker somewhat and in fact, my wife and I host a private FREE World of Warcraft ( WOW )server. Been hosting online game servers for about 9 years now and we love it.
Once again, thanks and as you said, I probably need alot more schooling before I would attempt a ROOT. My only problem is AWAKE time, its really high even tho I have removed those apps I can remove to help that situation. Hopefully, 2.1 will help us Non Roots somewhat but if not, then I will strongly consider ROOTing. As long as I know there are people like yourself to help us old dudes.
Thanks again Is_907, and to the rest of you who voiced your opinions, Thanks. All good points and even more reason to consider ROOTing.
Click to expand...
Click to collapse
Rooting really isn't too difficult. Just look at the intelligence level of some of the people who have managed to root (before anyone flames me, I'm mainly talking about myself)!
I believe it's entirely possible to root your phone, install a custom ROM that is close to stock, and then live a happy life without ever messing with it again.... Sorry, I couldn't keep a straight face!
Kidding aside, did you update your phone with the Sprint Maintenance Release? You mentioned "awake time" which this patch will fix without the need to root.
Honestly, I mess around with my Hero so much that I am often startled when it rings and I'm reminded that it's a phone.
watzone69 said:
Rooting really isn't too difficult. Just look at the intelligence level of some of the people who have managed to root (before anyone flames me, I'm mainly talking about myself)!
I believe it's entirely possible to root your phone, install a custom ROM that is close to stock, and then live a happy life without ever messing with it again.... Sorry, I couldn't keep a straight face!
Kidding aside, did you update your phone with the Sprint Maintenance Release? You mentioned "awake time" which this patch will fix without the need to root.
Honestly, I mess around with my Hero so much that I am often startled when it rings and I'm reminded that it's a phone.
Click to expand...
Click to collapse
lol I second this my wife hates the fact the I have tis really nice phone and when ever I am at home she can never get ahold of because I am always doing something to it.
to the OP rooting really is not hard I mean if you are hosting a MMORPG server you could surely do it, but if your happy with your phone as is then that is really awesome. I myself when I first got my phone knew ABSOLUTLY NOTHING about android or linux or what in the work a kernel or apk was but with the help of the great community here I have learned so much. Dont get me wrong I am no where near where a lot of the guys on here are but I am learning and helping as much as I can just as those that helped me (i mean I am just happy that I think I could go through and make a theme now lol). if you are happy with the phone as is the only benifit of rooting I would bring up is being able to make backups of everything that way if anything does happen to the phone then you dont have to go trough and redownload apps and set everyhting back up again.
if you do decide to make the leap there are many people here more than willing to help.
Its not the Intelligence thing, I know I can ROOT if I wish either with PreKitchen or the cmd prompt. And YES, I do host a game server and can write script so its not that I don't have the know-how. Its just me, I really don't need to be ROOT'd but the thought of having full control is the thing. Guess you could say I am a Control Freak. If you have ever played online and been part of the game Administration, you know what I mean.
Thanks, I haven't said NO, still just wondering is all.
Regards,
rdisanza said:
Its not the Intelligence thing, I know I can ROOT if I wish either with PreKitchen or the cmd prompt. And YES, I do host a game server and can write script so its not that I don't have the know-how. Its just me, I really don't need to be ROOT'd but the thought of having full control is the thing. Guess you could say I am a Control Freak. If you have ever played online and been part of the game Administration, you know what I mean.
Thanks, I haven't said NO, still just wondering is all.
Regards,
Click to expand...
Click to collapse
oh please understand I wasnt trying to insult you at all, and yes I understand the control thing. thats why I rooted originally but then I flashed my first rom and got addicted. Now if im not changing my phone in some way on a pretty much daily basis I start to get the DT's lol.
No insult taken my friend. The DT's, lol WORD!
Rooting is actually deceptively easy. All you have to do is download fresh pre-kitchen and hit root. Even from the command prompt (which i used because i don't have access to a windows machine) is still easy. This is literally ALL you have to do: (These are instructions for macs, basically same on windows)
Step 1. Download Android SDK from android.com
Step 2. Download Amon Ra's Sprint Hero Recovery Image
Step 3. Copy the recovery image to root of phone's SD card (name it recovery.img)
Step 4. Open command prompt and navigate to tools folder of the SDK \AndroidSDK\Tools
Step 5. Type the following code with phone plugged in via USB:
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Your phone should then boot into a screen with green text on a black background. Success! You have rooted. (Note: you will need to get the version of Stock ROM with SU for root access.)
Before you reboot the phone go into Backup/Restore>Nandroid Backup Then hit Home to confirm. This will say Performing backup...... and then say Backup complete! You may now hit Reboot System Now and it will start up like normal. Then, mount the SD card, and copy the Nandroid folder to your computer. This is your stock ROM, if anything goes wrong copy this back to the phone and restore it. You may boot into recovery by starting up the phone while holding the home button. Hope this helped.
HeroMeng said:
Rooting is actually deceptively easy. All you have to do is download fresh pre-kitchen and hit root. Even from the command prompt (which i used because i don't have access to a windows machine) is still easy. This is literally ALL you have to do: (These are instructions for macs, basically same on windows)
Step 1. Download Android SDK from android.com
Step 2. Download Amon Ra's Sprint Hero Recovery Image
Step 3. Copy the recovery image to root of phone's SD card (name it recovery.img)
Step 4. Open command prompt and navigate to tools folder of the SDK \AndroidSDK\Tools
Step 5. Type the following code with phone plugged in via USB:
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Your phone should then boot into a screen with green text on a black background. Success! You have rooted. (Note: you will need to get the version of Stock ROM with SU for root access.)
Before you reboot the phone go into Backup/Restore>Nandroid Backup Then hit Home to confirm. This will say Performing backup...... and then say Backup complete! You may now hit Reboot System Now and it will start up like normal. Then, mount the SD card, and copy the Nandroid folder to your computer. This is your stock ROM, if anything goes wrong copy this back to the phone and restore it. You may boot into recovery by starting up the phone while holding the home button. Hope this helped.
Click to expand...
Click to collapse
You don't have to push the asroot2 exploit!?!?!!?
Kcarpenter said:
You don't have to push the asroot2 exploit!?!?!!?
Click to expand...
Click to collapse
Not if you're flashing a custom rom that already has it.
You have to have root access to initially install the custom recovery image. So you DO need to push the asroot2 exploit & run it on the phone.
gu1dry said:
You have to have root access to initially install the custom recovery image. So you DO need to push the asroot2 exploit & run it on the phone.
Click to expand...
Click to collapse
I never had to do that when I rooted. Flashed MCR right after I rooted using above method and it worked fine.
Yes the asroot2 exploit is was allows to root the phone, so therefore you had run the exploit initially.
I have a Mac, none of these .exe files will run. Is there a way I can just mount my Hero, download a zipfile, drop it in there and get a 2.1 ROM? I thought I could with Damageless?
um I have a MAC and you don't need any .exe files to root your phone. use the guide in the sticky at the top of the forum and your good to go.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
No, you must gain root one way or another to get a recovery image on there to flash ROMs...
Here:
http://forum.xda-developers.com/showthread.php?t=581686
Thanks, but I cant be assed doing all that work. Isnt there something that auto roots for you with a download and a few clicks?
yeah, but its an .exe. honestly, if you cant be assed to take 5 minutes to root manually, youre in wrong forum.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
abcdfv said:
yeah, but its an .exe. honestly, if you cant be assed to take 5 minutes to root manually, youre in wrong forum.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
I see. Once I root, I then have to flash a ROM too. This all takes 5 minutes? The instructions to flash dont look too detailed. Is there alot involved?
Rooting- quick. Flashing- pretty quick. First boot-dreadfully long.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
but u could flash it quicker with the Godspeed recovery.
Not to be a ****, but.....wow, are you going to piss and moan in every forum online about this? Didn't you say you were done with the Hero and going back to the iphone or something not to long ago in phandroid........Just root and get it over with already.
mbell75 said:
Thanks, but I cant be assed doing all that work. Isnt there something that auto roots for you with a download and a few clicks?
Click to expand...
Click to collapse
mbell75 said:
Thanks, but I cant be assed doing all that work. Isnt there something that auto roots for you with a download and a few clicks?
Click to expand...
Click to collapse
Well if you don't want do all that work then I suggest you just wait for the official release.
The only auto rooter is for windows. Rooting and flashing ROMs can lead to problems. If you are unwilling to put some effort into it then you are going to end up bricking your phone or running into what we on the forum would consider a small problem. However, it will turn into a huge issue because you don't understand some basic functionality of the recovery shell and wouldn't know how to access ADB to enter a couple commands to help diagnose.
This is an issue about you coming back and asking 101 questions and have people hold your hand because you can't be bothered to learn a couple things about a new world you are trying to enter.
If you are unwilling to learn then please leave these forums because I can tell you are going to be nothing but trouble.
spend the time reading everything fully first, this will save you time and make you more comfortable.
BTW, you can root with the flashrec method if you'd like with any computer platform, but to do anything useful like remove bloatware, you're going to need the adb from the SDK at least. I would root through terminal if I were you, its not hard and many helpful people on here, including myself. I've rooted 2 phones on mac, and 3 on PC already. Just give me a pm, if you run into trouble somewhere.
Things not to forget
USB debugging needs to be on (settings--applications--development)
commands in terminal require ./ before the adb commands
Rooting is easier on a mac than pc... no drivers to install.
rufflez2010 said:
spend the time reading everything fully first, this will save you time and make you more comfortable.
BTW, you can root with the flashrec method if you'd like with any computer platform, but to do anything useful like remove bloatware, you're going to need the adb from the SDK at least. I would root through terminal if I were you, its not hard and many helpful people on here, including myself. I've rooted 2 phones on mac, and 3 on PC already. Just give me a pm, if you run into trouble somewhere.
Things not to forget
USB debugging needs to be on (settings--applications--development)
commands in terminal require ./ before the adb commands
Rooting is easier on a mac than pc... no drivers to install.
Click to expand...
Click to collapse
Thanks. PM'd you.
mbell75 said:
Thanks, but I cant be assed doing all that work.
Click to expand...
Click to collapse
wow.. really?????
you cant be assed.. but your can be an a..
yes.. you can get 2.1 without Rooting.....
buy a phone with it on it!!!
i am normally really easy going and try to help.. I dont know much, but try to pass on what i have learned.. because others have helped me...
you and your statement above... has rubbed me.. in the wrong way.
Dan330 said:
wow.. really?????
you cant be assed.. but your can be an a..
yes.. you can get 2.1 without Rooting.....
buy a phone with it on it!!!
i am normally really easy going and try to help.. I dont know much, but try to pass on what i have learned.. because others have helped me...
you and your statement above... has rubbed me.. in the wrong way.
Click to expand...
Click to collapse
I so agree, just reading this guys post gave me a headache!
Tried doing this method http://forum.xda-developers.com/showthread.php?t=584029 and get stuck with the exclamation point triangle. Seems I need to do a wipe before flashing? Where do you get the zip that wipes the phone?
mbell75 said:
Tried doing this method http://forum.xda-developers.com/showthread.php?t=584029 and get stuck with the exclamation point triangle. Seems I need to do a wipe before flashing? Where do you get the zip that wipes the phone?
Click to expand...
Click to collapse
dont use flashrec jus do it through adb go to the stiki wiki and read how to root hero cdma for mac all you have to do is download the sdk it basically sets itsself up download asroot2 put it in the tools folder in your sdk and the recovery image of choice then simply copy and paste the commands from the guide its really that simple..
root with godspeed..........................woot woot
I would suggest rooting manually. You will learn some basic ADB commands.
maybe its just me but cant u use bootcamp and install xp or win7 and do it from there or is your Apple IIc just not up to the task..
mbell, didnt you get banned from android forums for spamming/flaming/trolling?
nothing personal but dont do that here or you''ll get banned even quicker.
But on the side note welcome to the forums! xD
I rooted my Nexus 7 with Nexus Root Toolkit without any problems but I've just bought a Nexus 4 and can't seem to root it.
I let it update to Android 4.2.2 then ran NRT (v1.6.3) on my PC. After a few goes the drivers installed and it passed the final driver test so I assume all is well there. I then unlocked it without any trouble but I ran into problems when I came to root it.
It seemed to be going smoothly until it reached "Booting TWRP temporarily" but nothing happened, it just sat in the bootloader screen and didn't move on, although the message changed to "Rooting" and then "Waiting for your device to finish booting back up". In the end I pressed the power button which rebooted the 'phone and appeared to finish the procedure but it hadn't rooted or installed SuperSU or BusyBox.
I tried flashing it back to stock and re-rooting it but it was the same, I even re-locked it and went through the procedure again but it was the same.
Can anyone help please?
:sly:
Sent from my Nexus 4 using Tapatalk 2
SimonP2 said:
I rooted my Nexus 7 with Nexus Root Toolkit without any problems but I've just bought a Nexus 4 and can't seem to root it.
I let it update to Android 4.2.2 then ran NRT (v1.6.3) on my PC. After a few goes the drivers installed and it passed the final driver test so I assume all is well there. I then unlocked it without any trouble but I ran into problems when I came to root it.
It seemed to be going smoothly until it reached "Booting TWRP temporarily" but nothing happened, it just sat in the bootloader screen and didn't move on, although the message changed to "Rooting" and then "Waiting for your device to finish booting back up". In the end I pressed the power button which rebooted the 'phone and appeared to finish the procedure but it hadn't rooted or installed SuperSU or BusyBox.
I tried flashing it back to stock and re-rooting it but it was the same, I even re-locked it and went through the procedure again but it was the same.
Can anyone help please?
Click to expand...
Click to collapse
Yes, uninstall and forget about root kits and look and (most importantly) learn from here http://forum.xda-developers.com/showthread.php?t=2010312.
This is also a good source to read: http://forum.xda-developers.com/showthread.php?t=1469909
Thanks for the suggestions, guys. I still don't know why Nexus Root Toolkit didn't do the job when it worked so well and easily on my Nexus 7 but in the end I used the hippowise.com rooting instructions (using Google Nexus 4 Toolkit) and it worked a treat so I'm a happy bunny again
http://hippowise.com/how-to-unlock-root-and-install-a-custom-recovery-on-a-nexus-4/
I know it's more sensible to do it manually so that I know what has happened but in this case I just wanted the job done as quickly and easily as possible. I'll look into exactly what happened when time permits.
Cheers,
Simon.
^^ Learning opportunity lost.
Ditto, I've heard nothing good about toolkits and never used them, and consequently have never had the weird problrms I hear associated with them. Set up fast boot, setting it up can be a pain sometimes but its a one time thing. Using it is too easy and it never fails.
I do get what you guys mean and I will be interested to look into the procedures to see what's going on and how it unlocks and roots when time permits but, aside from being short of time at the moment, these toolkits are just automating the list of commands that you would issue manually so as long as someone has seen it working on the device and OS that you want, they should be fine so I'm happy to use them and learn more if/when I need to resolve problems. I am techie by nature but I'm not familiar with *nix and the inner workings of Android so it's a lot to study for something that only needs doing occasionally.
Anyway, thanks again for pointing me in the right direction and encouraging me to not be so lazy
SimonP2 said:
I do get what you guys mean and I will be interested to look into the procedures to see what's going on and how it unlocks and roots when time permits but, aside from being short of time at the moment, these toolkits are just automating the list of commands that you would issue manually so as long as someone has seen it working on the device and OS that you want, they should be fine so I'm happy to use them and learn more if/when I need to resolve problems. I am techie by nature but I'm not familiar with *nix and the inner workings of Android so it's a lot to study for something that only needs doing occasionally.
Anyway, thanks again for pointing me in the right direction and encouraging me to not be so lazy
Click to expand...
Click to collapse
To be honest, the learning curve with manual rooting is very straightforward. Heck, I found it quicker to unlock and root manually than through toolkits. You are literally just inputting a few lines into command prompt.
Sent from my Nexus 4 using Tapatalk 2
I can confirm that I have the same problem. Stuck at "Booting TWRP Temporarily" logo, doesn't move... Nexus 7 2012 Grouper 16GB.
I want to root my nexus 7. I don't know how to all the tutorials are for windows or useing the tool kit I want to do it manually I don't have my boot loader unlocked
Whaleshark345 said:
I want to root my nexus 7. I don't know how to all the tutorials are for windows or useing the tool kit I want to do it manually I don't have my boot loader unlocked
Click to expand...
Click to collapse
All the tutorials presume unlocking of the bootloader. afaik, nobody has bothered to find a separate privilege escalation method of rooting for the N7.
fastboot is available from Google (SDK) for Linux. That means that fastboot methods are identical, irrespective of platform.
There is nothing that prevents you from re-locking the bootloader after you have rooted - with the penalty that unlocking it later will cause a full wipe of /data.
Technically though, it is the *act* of unlocking the bootloader that causes a voiding of the warranty. If they really wanted to do it, I have no doubt Asus could detect a re-locked bootloader (by examining low-level flash write counters).
cheers
Thanks but i was wondering if someone could explain it to me a little more clearly and pro give a link to a tutorial
Unlock the bootloader. There is zero reason not to, except for the factory reset it does.
Whaleshark345 said:
Thanks but i was wondering if someone could explain it to me a little more clearly and pro give a link to a tutorial
Click to expand...
Click to collapse
How long exactly did you look around? Two seconds?
http://forum.xda-developers.com/showthread.php?t=2150661
bftb0 said:
How long exactly did you look around? Two seconds?
http://forum.xda-developers.com/showthread.php?t=2150661
Click to expand...
Click to collapse
3 seconds
bftb0 said:
How long exactly did you look around? Two seconds?
http://forum.xda-developers.com/showthread.php?t=2150661
Click to expand...
Click to collapse
I can understand where the guy's coming from. I've now Googled about six different 'tutorials' on how to root the Nexus 7.
They are all total ****. Horribly written with unclear, incomplete, and contradictory instructions.
Seriously--that one you linked is only good if you already know how to do it. For someone that doesn't...it's useless.
I rooted my 7 months ago (unlocked bootloader, etc.), but lost root with the 4.2.2 update. I can't find the instruction set I used last time, and the tutorials I've found so far actually have me wishing whoever wrote them was here now so that I could beat the **** out of them.
Seriously, whoever wrote them--especially the one you linked--sucks. Bad. A lot. Terrible writing.
A shortcut is to install Windows in Virtualbox and use Wug's utility to get the job done, an extra step but this will surely save you a lot of time to do it manually.
http://www.webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html
I dont understand what is so complicated about rooting a nexus device. it is literally the EASIEST device to root and flash. Not sure why people need walkthroughs or tutorials.
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
reboot into recovery
install supersu.zip
what part of that is complicated that requires someone to hold your hand and help you type out the commands??
@fre1102
Well, I suppose that poorly written tutorials and a flood of newbs looking to be spoon fed is good for generating ad revenue for XDA. Not really great for what made it a compelling site in it's early history, though.
On the other hand, the OP asked a help question - and failed to do so in the help and questions forum. That certainly appears like a lack of paying attention, does it not?
I suppose you might have a complaint if you had actually been paying someone to give you advice, but to complain about the quality of something that costs you nothing seems a bit like an entitlement problem - whether you are correct in your appraisal or not.
It's an internet bulletin board - there is no barrier to entry and the quality is going to vary widely. That makes it YOUR RESPONSIBILITY to decide what to believe. It's not as if people are coming in to your home and forcing you to do any of this stuff.
Nobody here owes you anything; this site has always encouraged folks to take responsibility for their own actions. If you have a rooted device that is borked - simply put, that is YOUR FAULT. Period.
Pirateghost said:
http://www.webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html
I dont understand what is so complicated about rooting a nexus device. it is literally the EASIEST device to root and flash. Not sure why people need walkthroughs or tutorials.
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
reboot into recovery
install supersu.zip
what part of that is complicated that requires someone to hold your hand and help you type out the commands??
Click to expand...
Click to collapse
You can even cut that down by a step by installing the latest version of TWRP 2.4 which will autmatically detect an unrooted rom and root it for you.
I gotta admit though that getting some custom roms was a little confusing to me in the beginning after rooting and flashing a samsung phone using heimdall in Linux. It's the lack of a good guide that really didn't help. I was hoping that there would be a sticky in the Q&A or a wiki topic about it but those sections for the nexus 7 aren't that organized.
Maybe we should start using the wiki... It would be easier to keep up to date even if someone decides to abandon a thread since anyone else can go in and edit it, and if we get repeated questions we can just copy and paste a link for those who want to be spoon fed since they will always be a constant presence on this forum.
EDIT:
I had to use the cyanogenmod rom building wiki to get a good, well-written guide on unlocking the n7 and flashing a custom recovery. Good thing I had started building the rom before I got the device shipped to me since it helped to have a "good" version of cwm6 laying around.
thanks guys I rooted it was easy just needed to adjust the commands for Ubuntu witch is just adding a "sudo ./" to the beginning of every command
Whaleshark345 said:
thanks guys I rooted it was easy just needed to adjust the commands for Ubuntu witch is just adding a "sudo ./" to the beginning of every command
Click to expand...
Click to collapse
Good deal. Some folks go to the trouble of customizing some udev configuration files (I think it's udev, but can't remember right now) so that unprivileged Linux users have permissions on individual USB devices.
To me that seems like quite a bit of trouble for stuff that I do infrequently (using fastboot); I just drop to a root shell
$ sudo /bin/bash
#
and save a couple keystrokes with the fastboot commands.
BTW, when using adb from Linux, it is only necessary to start up the adb server with root privileges - the server process is the only thing needing privileges on the USB bus, so
Code:
$ sudo `which adb` devices
gets the party started but
$ adb pull /sdcard/myzipfile.zip
won't result in files owned by root.
Not surprisingly, all this stuff is less cumbersome using a Mac OS/X flavor of Unix - by default the USB devices are reachable by unprivileged users without any udev/hotplug diddling or sudo invocations.
cheers
Received device 2 hrs ago. Now stuck with "Error 7" trying to flash CM13 via TWRP
Received device 2 hrs ago. Now stuck with "Error 7" trying to flash CM13 via TWRP
Yeah well, the topic says all. Took the latest image from CM13 but it just won´t flash. Any ideas? So keen on starting with my new device...
688attacksub said:
Received device 2 hrs ago. Now stuck with "Error 7" trying to flash CM13 via TWRP
Yeah well, the topic says all. Took the latest image from CM13 but it just won´t flash. Any ideas? So keen on starting with my new device...
Click to expand...
Click to collapse
Flash the latest bootloader, radio, and vendor. And then go on flashing the ROM.
Any chance to get a quick hint HOW?! I´m rather unexperienced, sorry.
We can see that. lol
688attacksub said:
Any chance to get a quick hint HOW?! I´m rather unexperienced, sorry.
Click to expand...
Click to collapse
http://bfy.tw/4vLn
Just unrooted and unlocked it using the tool kit. Maybe I´ll have another try some other time. For time being I had enough thrill. Thx and n8 boys.
No offense to you but you should have done some reading on how to modify your phone instead of jumping to a toolkit to do all the work for you. Check out Heisenberg's guide in the general section.
688attacksub said:
Received device 2 hrs ago. Now stuck with "Error 7" trying to flash CM13 via TWRP
Yeah well, the topic says all. Took the latest image from CM13 but it just won´t flash. Any ideas? So keen on starting with my new device...
Click to expand...
Click to collapse
Read my guide. Read it again. Then read it again. Then read it some more. Ditch the toolkit. You'll be much better off knowing how to do things for yourself. You really shouldn't be modifying your phone if you don't know what you're doing, you're gonna end up bricking it.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Read my guide. Read it again. Then read it again. Then read it some more. Ditch the toolkit. You'll be much better off knowing how to do things for yourself. You really shouldn't be modifying your phone if you don't know what you're doing, you're gonna end up bricking it.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I do like the post you put together. But to say ditch the toolkit means some developer that put together the toolkit isn't getting support. I would agree that you should know what you're doing and how to recover a phone before using a toolkit, and probably should try to do the entire process without the toolkit, but once you got it down, no reason not to use the toolkit.
dbroer91884 said:
I do like the post you put together. But to say ditch the toolkit means some developer that put together the toolkit isn't getting support. I would agree that you should know what you're doing and how to recover a phone before using a toolkit, and probably should try to do the entire process without the toolkit, but once you got it down, no reason not to use the toolkit.
Click to expand...
Click to collapse
I can think of one reason not to use a toolkit: they're known to cause problems. There are threads in virtually every Q&A section that can attest to this.
Heisenberg said:
I can think of one reason not to use a toolkit: they're known to cause problems. There are threads in virtually every Q&A section that can attest to this.
Click to expand...
Click to collapse
I took time to learn how to to everything manually but I still have loads of experiences with tool kits nexus 5 and 7 even previous 6ps that are faulty and have never had a problem with them they simply provide more convenience
Sent from my Nexus 6P using Tapatalk
mystertom101 said:
I took time to learn how to to everything manually but I still have loads of experiences with tool kits nexus 5 and 7 even previous 6ps that are faulty and have never had a problem with them they simply provide more convenience
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I didn't say they cause problems for everyone, if they did they wouldn't be on the site. Anyway, the entire point I was making here, which seemed to be completely lost on some people, is that a beginner shouldn't be using a toolkit, they should be gaining the knowledge that's required (by reading and doing things manually) when you're modifying your phone.
Heisenberg said:
I didn't say they cause problems for everyone, if they did they wouldn't be on the site. Anyway, the entire point I was making here, which seemed to be completely lost on some people, is that a beginner shouldn't be using a toolkit, they should be gaining the knowledge that's required (by reading and doing things manually) when you're modifying your phone.
Click to expand...
Click to collapse
This. Heisenberg is not saying toolkits are useless. The main theme he's trying to employ here is that new users should not be relying on toolkits instead of taking the time to learn the basics of Fastboot before diving into the world of root and mods. When the toolkit fails, Fastboot will rescue you. If you don't know how to use Fastboot, avoidable threads such as this are constantly generated.