Trying to root again after 4.2.1 update - Nexus 10 Q&A, Help & Troubleshooting

I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.

Dynesh said:
I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.
Click to expand...
Click to collapse
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.

xIC-MACIx said:
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.
Click to expand...
Click to collapse
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!

Well, I tried to run that program from the link, and it said some files were missing, so I stopped it. I tried to flash clockwork mod recovery and when it booted back into Android to rename the files, it got stuck on waiting on ADB. Frustrating.

Dynesh said:
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!
Click to expand...
Click to collapse
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)

xIC-MACIx said:
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)
Click to expand...
Click to collapse
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.

Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Glad it's working, Android can be temperamental at times & the issue is typically caused by the small things!

Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.

kane1513 said:
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.
Click to expand...
Click to collapse
I rooted using this method.
http://forum.xda-developers.com/showthread.php?t=2001868
I did have to unlock the bootloader so I did lose everything, but it wasn't that hard and I did it early enough that I didn't lose too much of what I had on there.

Related

Root my phone

What's the best way to root my so I can use setcpu? I only want to do that and keep everything I currently have the same. Is this possible and if so how?
Believers b3ar fruit with their Nexus S.....
B3arfruit said:
What's the best way to root my so I can use setcpu? I only want to do that and keep everything I currently have the same. Is this possible and if so how?
Believers b3ar fruit with their Nexus S.....
Click to expand...
Click to collapse
CAUTION: experimental/theoretical until someone tries it on a virgin phone, but...
Shrivelfig's found a method that might let you root without unlocking your bootloader and erasing the phone.
Download these two files:
clockwork recovery
su-2.3.6.1-ef-signed.zip
Place the su zip one in your sdcard.
Place the other on your computer.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the instructions that Allgamer gives in this thread, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps from this thread:
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
Reboot.
If it works, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
Please let me know if that works; I've not seen anyone who wasn't already rooted report back on the success or failure of this method.
distortedloop said:
CAUTION: experimental/theoretical until someone tries it on a virgin phone, but...
Shrivelfig's found a method that might let you root without unlocking your bootloader and erasing the phone.
Download these two files:
clockwork recovery
su-2.3.6.1-ef-signed.zip
Place the su zip one in your sdcard.
Place the other on your computer.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the instructions that Allgamer gives in this thread, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps from this thread:
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
Reboot.
If it works, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
Please let me know if that works; I've not seen anyone who wasn't already rooted report back on the success or failure of this method.
Click to expand...
Click to collapse
If I do a full root does it delete everything that I have? I have never tried it an I now looking Ratbags site that has a full outline on how to do it. All I want to do is use setcpu without deleting my stuff
Believers b3ar fruit with their Nexus S.....
B3arfruit said:
If I do a full root does it delete everything that I have? I have never tried it an I now looking Ratbags site that has a full outline on how to do it. All I want to do is use setcpu without deleting my stuff
Believers b3ar fruit with their Nexus S.....
Click to expand...
Click to collapse
Most of the root methods involve unlocking the bootloader with the "fastboot oem unlock" command as the first step.
That's the command that erases your phone.
Any method that has you do that command will erase your phone.
If the method above works as expected, it will root you without erasing your phone. Shrivelfig did it without harm to his phone, but he had already been rooted the old-fashioned way.
I would certainly backup my data that I could before doing any root method, but this one seems like it's 99% safe.
Use at own risk, of course, but that's true of all the methods.
OK last question what is the easiest way to backup your phone? How?
Believers b3ar fruit with their Nexus S.....
B3arfruit said:
OK last question what is the easiest way to backup your phone? How?
Believers b3ar fruit with their Nexus S.....
Click to expand...
Click to collapse
Without root, your options are limited and incomplete.
The only stuff you'll be able to backup are items that are stored on the sdcard. Some apps put their data there, some don't, some mix it up.
To backup the sdcard is as easy as usb mounting the phone and dragging/dropping the stuff you want to save.
distortedloop said:
Without root, your options are limited and incomplete.
The only stuff you'll be able to backup are items that are stored on the sdcard. Some apps put their data there, some don't, some mix it up.
To backup the sdcard is as easy as usb mounting the phone and dragging/dropping the stuff you want to save.
Click to expand...
Click to collapse
Your the man thanks bro I'll let you know if it works. Hope my phone doesn't crash on me
Man I suck I followed a lot of different direction and still can get my computer to recognize my phone when trying to root....
B3arfruit said:
Man I suck I followed a lot of different direction and still can get my computer to recognize my phone when trying to root....
Click to expand...
Click to collapse
You're putting the phone in fastboot mode? It's got the white screen?
You're using the proper commands fastboot? What message does your computer show? Are you Win, Mac, or Linux?
distortedloop said:
CAUTION: experimental/theoretical until someone tries it on a virgin phone, but...
Shrivelfig's found a method that might let you root without unlocking your bootloader and erasing the phone.
Download these two files:
clockwork recovery
su-2.3.6.1-ef-signed.zip
Place the su zip one in your sdcard.
Place the other on your computer.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the instructions that Allgamer gives in this thread, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps from this thread:
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
Reboot.
If it works, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
Please let me know if that works; I've not seen anyone who wasn't already rooted report back on the success or failure of this method.
Click to expand...
Click to collapse
Just tried it on a new Nexus S, worked perfectly
I rooted using this method last night. From start to finish, 10 minutes. I have full root capabilities.
Sent from my Nexus S using XDA App
I've been somewhat discouraged from rooting my Nexus S because of the apparent hurdles to rooting. When I rooted my Vibrant it never erased any data or stopped me from getting a firmware upgrade. Sure I lost root after upgrading, but all I had to do was run it again.
With the NS, when I hear people talk about root methods erasing their phones and preventing them from upgrading, it worries me. Sure I can back up all the data I really care about, but why should the NS have these difficulties when the Vibrant didn't?
zorak950 said:
I've been somewhat discouraged from rooting my Nexus S because of the apparent hurdles to rooting. When I rooted my Vibrant it never erased any data or stopped me from getting a firmware upgrade. Sure I lost root after upgrading, but all I had to do was run it again.
With the NS, when I hear people talk about root methods erasing their phones and preventing them from upgrading, it worries me. Sure I can back up all the data I really care about, but why should the NS have these difficulties when the Vibrant didn't?
Click to expand...
Click to collapse
Actually, you haven't been keeping up with the rooting methods. A few weeks back someone figured out how to push a recovery and install Superuser without unlocking the bootloader which is the part that wipes your phone.
The reason it is so easy to root most phones is that they use an exploit in the Android system to grant Superuser priveleges while on the Nexus S we do it the legitimate way. I've not heard of root preventing people from updating nor does it really bother me. I run custom roms and therefore wait for the updates to be integrated in my custom ROM. I'm sort of confused why someone would buy a Nexus S, a phone Google has said was designed to be hacked to pieces, and leave it stock.
kenvan19 said:
Actually, you haven't been keeping up with the rooting methods. A few weeks back someone figured out how to push a recovery and install Superuser without unlocking the bootloader which is the part that wipes your phone.
The reason it is so easy to root most phones is that they use an exploit in the Android system to grant Superuser priveleges while on the Nexus S we do it the legitimate way. I've not heard of root preventing people from updating nor does it really bother me. I run custom roms and therefore wait for the updates to be integrated in my custom ROM. I'm sort of confused why someone would buy a Nexus S, a phone Google has said was designed to be hacked to pieces, and leave it stock.
Click to expand...
Click to collapse
Because it's the fastest, cleanest, most up-to-date Android device of its class on the market. Custom ROMS are all well and good, but they're hardly the only reason to get the phone. Indeed, there are a ton of phones out there with arguably equal or better third-party ROM options at present. Anyway, to say Google designed the NS to be hacked to pieces is perhaps a bit of an overstatement; to my knowledge all they said is that they deliberately left open a way to root the phone, and even at that, it wasn't exactly a consumer marketing point.
Not that I'm badmouthing rooting, installing custom ROMS, or whatever else people do to their phones. On the contrary, I think it's fantastic. But ultimately, I object to the idea that there's a "wrong" choice when it comes to making those modifications. Different people have different priorities, concerns, and levels of comfort with various procedures, and the NS is a great phone no matter what you choose to run on it. I'm probably on the low end of the spectrum with respect to my interest and comfort in modding as far as people who post with any regularity on these forums go, but bear in mind I'm also probably a great deal more engaged with it than the majority of users, many of which may not even make full use of their phone's basic features, let alone think to try making their phone do anything that the top-layer UI doesn't facilitate.
Clockwork link not working
suhas_sm said:
Clockwork link not working
Click to expand...
Click to collapse
Try this one: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.5-crespo.img
or go straight to koush's blog: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
worked for me as well, on 2.3.2 without erasing anything.
thanks!
I concurr, the nowipe method works here (UK SNS fro Carphone Warehouse on 2.3.2).
All we need now is google to fix the issues (rebooting in particular).
Hey, thanks ... if this works without unlocking the bootloader, I'm trying it
Two things before that though:
a) Please let us know if you can update to 2.3.3 after this or if you have to wait for a new image.
b) Can I rewind and get my phone back to the unrooted version as it was when I bought it? If yes, can someone write the steps for that too?
Thanks
Paparasee said:
Hey, thanks ... if this works without unlocking the bootloader, I'm trying it
Click to expand...
Click to collapse
It works. Try it. Full thread on it that I'll update as things change here.
Paparasee said:
Two things before that though:
a) Please let us know if you can update to 2.3.3 after this or if you have to wait for a new image.
Click to expand...
Click to collapse
We won't know for sure until the 2.3.3 update comes out and we can examine its contents and what it does. There's no reason to expect that Google will do much differently in terms of the bootloader or recovery than they have in the last two updates, especially since they've said in the Google blog that the NS was designed to be easily unlocked and rooted.
In the prior two OTA updates, you could update with no issues other than your root being broken, but it was as easy as just rebooting into clockwork and reinstalling the su update zip.
The only people who had issues updating prior OTAs after this kind of root were folks who had messed around with applications in the /system folder (such as replacing the Market or Gmail apps with some modded one). That can be worked around easily and is discussed numerous times in a couple of threads.
Paparasee said:
b) Can I rewind and get my phone back to the unrooted version as it was when I bought it? If yes, can someone write the steps for that too?
Thanks
Click to expand...
Click to collapse
All rooting with this method does is add the su binary to /system/bin, the superuser.apk file to /data/app and change permissions on /system/bin. If you install busybox (which you really need to do for root to be most effective) it will add it's own files and some symlinks.
Several easy ways to reverse the process:
Restore/flash a nandroid or stock rom image that's not rooted. (Try making one after getting into Clockwork and before flashing su-update.zip.)
Use terminal/adb, the Settings/Applications app or the Market to rm and/or uninstall the su binary, the busybox install, and the superuser.apk as well as any root-enabled apps you installed.
There's more details if you need them in another thread here or Q&A section. You should be able to find them with a search on the terms "rm /system/bin/ root".

[Q] Best first steps with a new tablet

Ultra Noob here
So I had my first android-TF700 for about 10 days. Played around with it, read around this site and realized it was a tablet for someone with experience.
So I now have an N10. Charged, not even turned on yet. What should be my next steps? I see a couple toolkits,an auto root, and ASOP-
What would you suggest a noob start with?
I know, I know, turn it on
Thanks!
Depends on what you want to accomplish with the device. If you want to try or at least gain some understanding as to the different features you might be interested in, read the first post of the different ROMs available and see if anything sounds enticing.
I personally use me for taking media with me on the go, be it news or videos, so I don't have to carry a laptop around. I'm on CM10.1 right now but cycle through every rom to see how everything works. Good luck!
Sent from my Nexus 10 using XDA Premium HD app
First step is unlocking the bootloader and installing root and a custom recovery. Even if you don't need it at the moment there will come the time you want to try it. When you unlock the bootloader you will lose all your data so it's the best if you do it at first when you get your tablet.
rauschkugl said:
First step is unlocking the bootloader and installing root and a custom recovery. Even if you don't need it at the moment there will come the time you want to try it. When you unlock the bootloader you will lose all your data so it's the best if you do it at first when you get your tablet.
Click to expand...
Click to collapse
And how do you unlock the bootloader and install root?
What do you mean a custom recovery?
Are there other ways to root the device with out wiping it? Seems like most android smartphone you can load up an exe or something to shift the su app around or something.
Thanks.. (still waiting for my N10 to arrive.. meanwhile.. still playing with my ICS Bionic)
There are tons of threads here about unlocking the bootloader, rooting and installing a recovery like teamwin or clockworkmod.
rauschkugl said:
There are tons of threads here about unlocking the bootloader, rooting and installing a recovery like teamwin or clockworkmod.
Click to expand...
Click to collapse
Found the threads. Look easy enough to follow. Something I'm not understanding . What does it mean to install a recovery? whats the purpose of that. I've search and (at least not yet) found a good description of what/why that it. I'm sensing that devices are different (duh!) and I didnt need to install a "recovery" on my Droid Bionic when I rooted it, but this N10 must be different.
With the custom recovery you're able to install zip files, make a backup of your Rom,... You can't do that with the recovery that comes with the nexus 10.
Recovery is like a separate system that you can boot to, if you want to mess with the main Android OS. Like rauschkugl said, you can boot to a custom recovery to flash different ROMs that are distributed in flashable ZIP files. You can also make (or if anything goes wrong, revert to) a complete backup of the device's internal memory.
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
EraVulgaris said:
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
Click to expand...
Click to collapse
Great questions. You are one step ahead of me on my new N10. I've not turned it on yet, really wanting to, but I dont want to do much to it, until after I unlock/root/ and learn how to make backups. Though since i've got a TBpro license, I'll probably use that. I dont want to tweak the OS. so I think I need root just to be able to run TBpro. I just want to be sure I'll still get OFA updates, and I want to learn more about if and how backup work for a multi-user N10.
EraVulgaris said:
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
Click to expand...
Click to collapse
I would suggest straight away that you perform a backup with TWRP, so that if you decide to delve deeper into ROMs and playing with your system files, you'll have a completely stock backup to rely on. Simply boot into recovery and select 'Backup', then you can rename the backup file if you want, then swipe the slider across and wait, then you're done!
When it comes to system updates, you'll most likely have to use your root toolkit to unroot the device, else the update will fail. You can however continue to update all your apps as you normally would. Hope this helped
OK
So I kinda started from the beginning of Droid ModderX's video, picked yes to update the toolkit i had donated- (got an update) accessed TWRP (pain to get to- could I download goomanager now after I have TWRP?) and backed up my stock set up just as you said Huggogguh :good:.
Then I went ahead and touched "install system update" that was hanging around in the upper left corner of my tablet (I'm being really specific for other noobs) and it updated my system to 4.2.1 and my apps. Build number changed to JOP4OD
Looked at root checker app. I am now not rooted, so I will go back through toolkit and choose 4 once I am in fastboot mode to reroot I hope:fingers-crossed:.
Thanks!
EraVulgaris said:
OK
So I kinda started from the beginning of Droid ModderX's video, picked yes to update the toolkit i had donated- (got an update) accessed TWRP (pain to get to- could I download goomanager now after I have TWRP?) and backed up my stock set up just as you said Huggogguh :good:.
Then I went ahead and touched "install system update" that was hanging around in the upper left corner of my tablet (I'm being really specific for other noobs) and it updated my system to 4.2.1 and my apps. Build number changed to JOP4OD
Looked at root checker app. I am now not rooted, so I will go back through toolkit and choose 4 once I am in fastboot mode to reroot I hope:fingers-crossed:.
Thanks!
Click to expand...
Click to collapse
Sounds like a great success then so are you saying that you performed the system update while you were rooted and you retained the root access?
Nope. Got the OTA system update and it knocked me off root. But I got it back easily with the toolkit.

[Q] Problems with the root after 4.2.2 update

Hello everyone, I am fairly new to rooting, roms and what not. The only other experience I had rooting something was with my old g2x. Anyways, I was reading everywhere that the new 4.2.2 OTA update was available and people had provided urls. I decided I would go ahead and root my nexus 10 while it was on 4.2.1. I followed the instructions with rooting a nexus 10 by using the nexus root toolkit by WugFresh. I followed every instruction (backing up, unlocking, then rooting) without making any mistakes. Everything went fine with the rooting process until i tried to install a paid app. I then went ahead and looked up what the -24 error was. They said to fix it i needed to go into data/data and delete the folders. This is when I realized the my root hadn't worked. The unlock worked but the root didnt. I downloded rootchecker and it said I wasnt rooted. Now I'm attempting to root my nexus 10 again but it keeps saying my adb device is listed as offline. No matter what I do, uninstalling all the usb drivers related to google and such, wiping my nexus 10 etc. I can't get it to root. Some assistance is needed! Anything I can do to root my tablet?
itstommy said:
Hello everyone, I am fairly new to rooting, roms and what not. The only other experience I had rooting something was with my old g2x. Anyways, I was reading everywhere that the new 4.2.2 OTA update was available and people had provided urls. I decided I would go ahead and root my nexus 10 while it was on 4.2.1. I followed the instructions with rooting a nexus 10 by using the nexus root toolkit by WugFresh. I followed every instruction (backing up, unlocking, then rooting) without making any mistakes. Everything went fine with the rooting process until i tried to install a paid app. I then went ahead and looked up what the -24 error was. They said to fix it i needed to go into data/data and delete the folders. This is when I realized the my root hadn't worked. The unlock worked but the root didnt. I downloded rootchecker and it said I wasnt rooted. Now I'm attempting to root my nexus 10 again but it keeps saying my adb device is listed as offline. No matter what I do, uninstalling all the usb drivers related to google and such, wiping my nexus 10 etc. I can't get it to root. Some assistance is needed! Anything I can do to root my tablet?
Click to expand...
Click to collapse
I recommend trying the Nexus 10 Toolkit 1.3.0. I successfully rooted my 4.2.1 N10 with this tool a few days ago (and promptly lost it in the OTA). http://forum.xda-developers.com/showthread.php?t=2001868
nalf38 said:
I recommend trying the Nexus 10 Toolkit 1.3.0. I successfully rooted my 4.2.1 N10 with this tool a few days ago (and promptly lost it in the OTA). http://forum.xda-developers.com/showthread.php?t=2001868
Click to expand...
Click to collapse
Yeah, but the thing is it doesn't recognize the device being plugged in. I don't know what else to do. I've tried using that toolkit (the one click all) and it wont even start.
itstommy said:
Yeah, but the thing is it doesn't recognize the device being plugged in. I don't know what else to do. I've tried using that toolkit (the one click all) and it wont even start.
Click to expand...
Click to collapse
Have you tried the Naked ADB drivers? What Windows OS are you using?
nalf38 said:
Have you tried the Naked ADB drivers? What Windows OS are you using?
Click to expand...
Click to collapse
where did you find the naked drivers? I'm running W7 64 bit. I only installed the drivers that came with pdanet as required by the guide I followed. Now im stuck in an unrooted 4.2.2.
ADB mode offline Both toolkits
nalf38 said:
I recommend trying the Nexus 10 Toolkit 1.3.0. I successfully rooted my 4.2.1 N10 with this tool a few days ago (and promptly lost it in the OTA). http://forum.xda-developers.com/showthread.php?t=2001868
Click to expand...
Click to collapse
I too have the same problem. Been searching for hours trying to find a solution.
I have tried both Wug's and mskips (paid version) toolkits and still the device shows offline.
I have ADB debuging enabled and tried in PTP and MTP modes. Have uninstalled the drivers and tried the PDAnet versions as well as the ones from mskips toolkit.
Both toolkits show that the device is connected, and I have booted to recovery and done the driver install (sees it as a Nexus 4 btw), but it's in offline mode.
My G-Nex works just fine, and I'm no stranger to rooting/custom roms. Not sure if having both devices loaded on this laptop is the issue.
Any help would be appreciated
Thanks
Jim
mrlow999 said:
I too have the same problem. Been searching for hours trying to find a solution.
I have tried both Wug's and mskips (paid version) toolkits and still the device shows offline.
I have ADB debuging enabled and tried in PTP and MTP modes. Have uninstalled the drivers and tried the PDAnet versions as well as the ones from mskips toolkit.
Both toolkits show that the device is connected, and I have booted to recovery and done the driver install (sees it as a Nexus 4 btw), but it's in offline mode.
My G-Nex works just fine, and I'm no stranger to rooting/custom roms. Not sure if having both devices loaded on this laptop is the issue.
Any help would be appreciated
Thanks
Jim
Click to expand...
Click to collapse
You're not researching in the right places. Wug's toolkit 1.6.2 have been confirm by the developer to not be working properly and he states that an update is in the horizon so be patient. Also, if you click on his website he wrote a paragraph about a temporary fix and he gives you a zip file so you can replace the files on the computer. I can assure you it works. If the files are replaced properly your device will show online instead of offline.
Here is his website where he gives you the tools to make it work: http://www.wugfresh.com/nrt/
THANK YOU SO MUCH FOR POSTING THIS. I've been scouring the forums everywhere just trying to fix this when the answer was right under my nose.
Thanks!
RawBott Bigg said:
You're not researching in the right places. Wug's toolkit 1.6.2 have been confirm by the developer to not be working properly and he states that an update is in the horizon so be patient. Also, if you click on his website he wrote a paragraph about a temporary fix and he gives you a zip file so you can replace the files on the computer. I can assure you it works. If the files are replaced properly your device will show online instead of offline.
Click to expand...
Click to collapse
Thanks a bunch! :good:
I did finally get it working late last night using mskips toolkit (donate version). Went without a hitch.
I can't believe I didn't see that. It's easy to miss something when you're frustrated, and not thinking about the right search terms.
The solution I found was it was a permission problem. As soon as I tried to do something with the toolkit, I got a popup on the tablet asking if I wanted to let my laptop control it. As soon as I said yes and always it worked beautifully. Had to do it again when it did the factory reset, but I was ready that time.
It threw me for a loop, never had to do that with my GNex or my OG Droid.
For now, I'll stick with mskips toolkit.
Thanks again.
Jim

[Q] Stuck at "X" Nexus 7 2013

First I have been to and searched every post and site I can find to turn this thing around, with no success. Sent several emails.
Took a rooted New Nexus 7 that had been restored back because it froze/did not respond. Got a new N7, unlocked bootloader and installed TWRP using Terminal (Mac) booted into recovery (TWRP) it said you are not rooted, install SU by swiping below. I swiped and tried to reboot and it stops at X. I have wiped, reinstalled TWRP and used a One Click Toolkit to Root. no success. Not really sure what I did wrong.....given I have always trusted TWRP.
Anyway... have unlocked bootloader, TWRP installed and cannot get Android File Transfer to recognize device. Welcome help or suggestions.
Thank you in advance.
David
Same thing happened to me. Don't listen to TWRP about SU. You'll need to do it manually for it to be successful. Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2381582. This won't relock your bootloader. You just need to root it by flashing the SU zip found on one if the "How to root" threads.
natezire71 said:
Same thing happened to me. Don't listen to TWRP about SU. You'll need to do it manually for it to be successful. Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2381582. This won't relock your bootloader. You just need to root it by flashing the SU zip found on one if the "How to root" threads.
Click to expand...
Click to collapse
Yeah, youre correct, you have to manually flash twrp. I would suggest running the utility to make youre device boot again, then make sure you have the LATEST twrp, then reboot and flash COMPATIBLE SU and you should be golden. Im not sure about macs though but you should deff be goin the right way.
Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David
dschaap said:
Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David
Click to expand...
Click to collapse
Give this a try: http://forum.xda-developers.com/showthread.php?t=2395003
I don't have a Mac, so I don't know if this will help. Only thing I could find.
dschaap said:
Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David
Click to expand...
Click to collapse
If you were able to install using a Mac, then you should have no troubles setting things up again. Avoid toolkits if you can, especially during the early days where things are buggy.
If you put your tablet into fastboot though, you can get started by going ahead and running fastboot -w and then flashing the stock recovery images back on. Sure, you won't have root, but I've found that 1) root doesn't take super nicely unless you're already signed into the tablet anyway, and 2) regardless of 1), once your bootloader is unlocked you might as well get set up and then root afterwards.
Mine did the same thing. What I did to fix was:
1. Go into recovery and format data in the wipe menu.
2. Then factory reset.
3. Restart os.
This was posted by decksy post #11 in tutorial for unlock, recovery, and root thread so if it works thank him.
Sent from my Nexus 7 using xda app-developers app

[Q] Can't unlock Nexus 7 2013

Went thru other problems in here but none of them worked.
I'm using Nexus Root Toolkit 1.8.2.
Everything seems to work except when Unlock finishes, it does not go back to "new" state. Everything is still there: all my apps, settings, everything.
I tried another USB port, another USB cable, and then used a different computer and went thru it all again. Same problem.
I made sure I set it to v2 and 4.4.2 KOT49H. Went thru the drivers setup. Everything passed after I followed all the instruction.
I even tried to Root it and still nothing. It reboots, it does everything it's supposed to do. I even watched the video on their webpage about my Nexus. It does exactly as it should, except when it comes out of unlock, apparently it's not unlocked.
Maybe try a different root program?
goofy173 said:
Went thru other problems in here but none of them worked.
I'm using Nexus Root Toolkit 1.8.2.
Everything seems to work except when Unlock finishes, it does not go back to "new" state. Everything is still there: all my apps, settings, everything.
I tried another USB port, another USB cable, and then used a different computer and went thru it all again. Same problem.
I made sure I set it to v2 and 4.4.2 KOT49H. Went thru the drivers setup. Everything passed after I followed all the instruction.
I even tried to Root it and still nothing. It reboots, it does everything it's supposed to do. I even watched the video on their webpage about my Nexus. It does exactly as it should, except when it comes out of unlock, apparently it's not unlocked.
Maybe try a different root program?
Click to expand...
Click to collapse
Did you try unlocking manually by using the fastboot drivers? See if that works.
How do I do that? Its that something within Nexus Root Toolkit?
I tried manually putting it into bootloader and then running the toolkit with no luck
I have these options on the bootloader:
Restart Bootloader
Recovery Mode
Power Off
Start
At the bottom I have:
FASTBOOT MODE
PRODUCT NAME - flo
VARIANT - flo 32G
HW VERSION - rev_e
BOOTLOADER VERSION - FLO-04.02
CARRIER INFO - None
SERIAL NUMBER - 05858bae
SIGNING - yes
SECURE BOOT - enabled
LOCK STATE - unlocked
Does that last one mean it's already unlocked?
Here's what I did:
I tried another method. I got the clockwork recovery image, SuperSU and Fastboot.
I opened a command prompt to get it into bootloader but it never worked so I did it manually.
I typed fastboot oem unlock and that worked. It looks like its already unlocked.
Rebooted but all my data was still there.
Then I typed fastboot flash recovery recovery-clockwork-6.0.4.3-flo.img (Now I see WiFi only I was supposed to use 6.0.4.4, oh well)
and it said it was successful. When I rebooted it was back the way it always is, with my data.
I sent ahead with the root by copying SuperSU.zip over to the root directory.
Rebooted to recovery mode
and install teh zip file
It all said it worked but I rebooted and it's still all the same.
Now this would have normally told me it was already rooted, but I tried to install an adblocker the other day that required a rooted tablet, and it said it could perform the install because it wasn't rooted.
So???
Unlocking the bootloader destroys your data. If they're still there, I doubt you successfully unlocked the bootloader. Check by powering down. Boot back up. You should see the word Google followed by an icon of an open lock if you successfully unlocked the bootloader.
Sent from my Nexus 7 using Tapatalk
exglynco said:
Unlocking the bootloader destroys your data. If they're still there, I doubt you successfully unlocked the bootloader. Check by powering down. Boot back up. You should see the word Google followed by an icon of an open lock if you successfully unlocked the bootloader.
Click to expand...
Click to collapse
I've had that open lock icon from when I first got the tablet.
I don't think i can post images.
https://www.dropbox.com/s/is51bsgh11zxkcu/100_1690[1].JPG
I tried 2 other root required apps, one which is for checking if it rooted, and it said it wasn't, and a root-required app also said it wasn't.
Dude you are already unlocked. If it says in bootloader mode that you are unlocked and you have the unlock symbol when you boot you are unlocked. You just need to root. Rooting is is not the same as unlocking your bootloader. To root you can either use a toolkit. Or get the LATEST Supersu flashable zip file. Then download the Supersu app from the play store and update your binaries
Sent from my SCH-I535 using Tapatalk
And I've done both of those and neither has rooted it. Says it did it, but when I check it with 2 apps that require a rooted tablet, it says it's not rooted. I dl'ed a root check app and it also says its not rooted. Gonna go thru it again right now.
And it worked with Nexus Root Toolkit and just clicking root and following everything from then on out.
not sure where I messed up. Not even sure that mine came already unlocked now. Maybe I unlocked it the first time I tried?
Anyway, the root checker app said its rooted! Thanks for your help as this is my first root of anything.
I guess since I never lost my data and apps since I first started trying to root this Nexus yesterday, it must have already been unlocked, since from my understanding, unlocking it would have lost the apps and data and took it back to as-new setup.
goofy173 said:
I guess since I never lost my data and apps since I first started trying to root this Nexus yesterday, it must have already been unlocked, since from my understanding, unlocking it would have lost the apps and data and took it back to as-new setup.
Click to expand...
Click to collapse
Unlocking doesn't delete your apps. But it does delete everything on the internal SD card
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
Unlocking doesn't delete your apps. But it does delete everything on the internal SD card
Click to expand...
Click to collapse
oh. I figured that was everything. I do remember at one point I had to put my password in manually to connect to my router. Must have been when it unlocked.
Now when I just did my daughter's Nexus 7 (2012) it did erase everything and took it back to original, but she's only had a for a week so she can reinstall everything.

Categories

Resources