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
Related
Hello,
I'm completely new to Android. I've been working on computer chips for 15+ years though (IC layout). I'm currently working on the follow up to Tegra 3.
I wanted to use SwitchMe on my N7 so I rooted it with msabra's one click root tool(CWM). Now I am getting constant reminders about the 4.1.1 system OTA update.
I really have no desire or time to play with mods right now.
I've searched on how to do it, but would one of you mind explaining the steps in detail? Also, if I unroot to install the update will I lose all of my user data, apps, etc?
Thanks!
Chris
ChrisAttebery said:
Hello,
I'm completely new to Android. I've been working on computer chips for 15+ years though (IC layout). I'm currently working on the follow up to Tegra 3.
I wanted to use SwitchMe on my N7 so I rooted it with msabra's one click root tool(CWM). Now I am getting constant reminders about the 4.1.1 system OTA update.
I really have no desire or time to play with mods right now.
I've searched on how to do it, but would one of you mind explaining the steps in detail? Also, if I unroot to install the update will I lose all of my user data, apps, etc?
Thanks!
Chris
Click to expand...
Click to collapse
You can just unroot, install the update, and reroot. I would use Wug's toolkit. You could also install voodoo OTA rootkeeper I believe, and backup your root, temp unroot and install the OTA update, and then restore the root that you backed up.
Unless you lock the bootloader and unlock the bootloader, the device shouldn't wipe the data partition on it's own.
Thanks for the help. Unfortunately the toolkit keeps crashing at the unroot step.
http://forum.xda-developers.com/showthread.php?t=1465661
ChrisAttebery said:
Thanks for the help. Unfortunately the toolkit keeps crashing at the unroot step.
Click to expand...
Click to collapse
Try toolkit release by mskip..hope it help and for the wug toolkit make sure reboot your pc and please connect and disconnect the usb cable. Be sure that there is one android adb driver is install. Check at your device manager. If you use winXP, kindly upgrade to win7 pro or later for better stability. Hope it help .
I was able to run backups with Wug's kit, but it gave me an error every time I tried to unroot. I don't think I rebooted my PC after I installed it, so I'll try that out tonight.
I also downloaded mskip's kit, but haven't tried it out yet.
I'm on W7 64.
Thanks!
yosh76 said:
Try toolkit release by mskip..hope it help and for the wug toolkit make sure reboot your pc and please connect and disconnect the usb cable. Be sure that there is one android adb driver is install. Check at your device manager. If you use winXP, kindly upgrade to win7 pro or later for better stability. Hope it help .
Click to expand...
Click to collapse
I'm want to use Android Commander to transfer some files back and forth to the PC for development. AC needs root access... I've used WugFresh's excellent toolkit to unlock and root the device. All worked fine; SuperSU is present, BusyBox installed. But AC still reports no root access, and the FAQ briefly mentions the difference that not all rooting gives root access to adb.
Can anyone explain in simple terms (I'm pretty new to android) how to get full root access to the device so that I can use Android Commander? Googling for instructions to root the device seems to pretty much always lead back to WugFresh's toolkit, which I've already done.
Stuart
Try the link below .I remember having a similar problem on a Galaxy Note. I ain't certain but I think its to do with ADB insecure/secure. I could be completely wrong of course!!
http://www.xda-developers.com/android/run-adbd-in-root-mode-with-adbd-insecure/
ScottArten said:
Try the link below .I remember having a similar problem on a Galaxy Note. I ain't certain but I think its to do with ADB insecure/secure. I could be completely wrong of course!!
http://www.xda-developers.com/android/run-adbd-in-root-mode-with-adbd-insecure/
Click to expand...
Click to collapse
Many thanks, yes, that seems to have worked. Strange that there isn't more info about this out there.
This says that it only persists until a reboot - I would still be interested in anyone knows a way of doing this permanently without installing a custom ROM
Stuart
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.
Hello Everyone,
Just got my Nexus 4 the other day and have loved every minute spent with it. I'm trying to root it using the apparently fool-proof cf-auto root, but --despite apparent success-- have been having issues installing the fastboot drivers. Despite downloading and installing the appropriate drivers with the Nexus 4 toolkit, following all the instructions, troubleshooting a bit (switching from MTP to TPT USB mode to get those drivers as advised at the end of the toolkit instructions), I have had no luck at all with cf-auto root. The first step, where I think it says it will unlock the bootloader before the root, I get "The system cannot find the path specified." The phone is recognized and drivers have been automatically obtained from the internet exactly when they were supposed to be, according to the step by step instructions in the toolkit and the cf-auto root guide.
I really can't wait to get this thing rooted. Anyone have any idea as to what I can do? Also, what exactly do I need to uninstall/reset so that I can start the process from scratch in case that's necessary? Thanks so much everyone. Can't wait to have some actually fun questions to ask...
hexagondun said:
Hello Everyone,
Just got my Nexus 4 the other day and have loved every minute spent with it. I'm trying to root it using the apparently fool-proof cf-auto root, but --despite apparent success-- have been having issues installing the fastboot drivers. Despite downloading and installing the appropriate drivers with the Nexus 4 toolkit, following all the instructions, troubleshooting a bit (switching from MTP to TPT USB mode to get those drivers as advised at the end of the toolkit instructions), I have had no luck at all with cf-auto root. The first step, where I think it says it will unlock the bootloader before the root, I get "The system cannot find the path specified." The phone is recognized and drivers have been automatically obtained from the internet exactly when they were supposed to be, according to the step by step instructions in the toolkit and the cf-auto root guide.
I really can't wait to get this thing rooted. Anyone have any idea as to what I can do? Also, what exactly do I need to uninstall/reset so that I can start the process from scratch in case that's necessary? Thanks so much everyone. Can't wait to have some actually fun questions to ask...
Click to expand...
Click to collapse
forgot to mention that i downloaded android sdk for drivers too.
Hey,
I decided after a couple of months to finally root my Nexus 4. I followed a manual guide, I didn't want to use a toolkit because I'd figure I'd learn it the proper way. Anyhow, If I go to the bootloader it clearly says it's unlocked. As the guide told me I then went into the clockwerk recovery and installed SuperSu 1.89.
I then proceed to restart my Nexus 4 to then be told that by SuperSu that there are no binaries installed and thus has no root access. It has been driving me nuts and I have spend 3 hours troubleshooting with google searches and experimentation because I hate to just make a thread without researching myself first. what am I missing?
Thanks, a lot.
Alibambam said:
Hey,
I decided after a couple of months to finally root my Nexus 4. I followed a manual guide, I didn't want to use a toolkit because I'd figure I'd learn it the proper way. Anyhow, If I go to the bootloader it clearly says it's unlocked. As the guide told me I then went into the clockwerk recovery and installed SuperSu 1.89.
I then proceed to restart my Nexus 4 to then be told that by SuperSu that there are no binaries installed and thus has no root access. It has been driving me nuts and I have spend 3 hours troubleshooting with google searches and experimentation because I hate to just make a thread without researching myself first. what am I missing?
Thanks, a lot.
Click to expand...
Click to collapse
If you flashed the correct Supersu zip, then it should have also installed binaries. Did you install the zip from Chainfire's site?
Try flashing it again. Sometimes it doesn't seem to stick.
Sent from my Nexus 7 using Tapatalk