Hello,
I'm just starting with rooting and installing custom roms.
So I don't have any experience with that.
Today I unlocked my bootloader with the WugFresh Toolkit.
But when I want to root my device I get this message: ''ADB Device not found''
I already tried it with my Galaxy Nexus but I get the same message.
How can I fix this?
TheRicolaa10 said:
Hello,
I'm just starting with rooting and installing custom roms.
So I don't have any experience with that.
Today I unlocked my bootloader with the WugFresh Toolkit.
But when I want to root my device I get this message: ''ADB Device not found''
I already tried it with my Galaxy Nexus but I get the same message.
How can I fix this?
Click to expand...
Click to collapse
Did you go through all the driver steps? Even after the correct drivers were installed, I had to put mine into bootloader mode manually, then root.
I already tried that, with no succes.
I also had to uncheck MTP and install the drivers while in the webcam mode. Then my device would show up in the toolkit as ADB connected but status would be red. At that point is when I put it into bootloader manually. Running Windows XP, btw.
Krulm said:
and install the drivers while in the webcam mode. .
Click to expand...
Click to collapse
I will try to uncheck MTP. But what do you mean by ''In webcam mode''?
Mine gives two options (4.2.1). Media Device(MTP) or Camera(PTP), whereas I am forced to select one or the other. In PTP mode it shows up as a Webcam when connected to Win XP.
I did the rooting process. Bit it looks like it's failed. When I start up SuperSU it said: "No SU binary found".
Can I do this rooting process again?
It should have loaded the su binary. Are you ruining each section of the tool and following the instructions exactly? It's pretty fool proof.
Sent from my DROID RAZR using Tapatalk 4
iresq said:
It should have loaded the su binary. Are you ruining each section of the tool and following the instructions exactly? It's pretty fool proof.
Sent from my DROID RAZR using Tapatalk 4
Click to expand...
Click to collapse
I did it 2 times, I had no errors when I did the rooting process. I don't know where it goes wrong actually.
Is it possible to delete SuperSU?
iresq said:
It should have loaded the su binary. Are you ruining each section of the tool and following the instructions exactly? It's pretty fool proof.
Sent from my DROID RAZR using Tapatalk 4
Click to expand...
Click to collapse
Download http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Use Wugs toolkit to flash to device. Worked for me.
TheRicolaa10 said:
Hello,
I'm just starting with rooting and installing custom roms.
So I don't have any experience with that.
Today I unlocked my bootloader with the WugFresh Toolkit.
But when I want to root my device I get this message: ''ADB Device not found''
I already tried it with my Galaxy Nexus but I get the same message.
How can I fix this?
Click to expand...
Click to collapse
Hey, just turn off mpt connection, turn on USB debugging and ptp connection and viola. Might have to delete any former files from nexus 7 on computer first though. Then just use cmd or command line to confirm adb, type adb devices on the command line and hopefully it should identify your device (it doesn't have to be your actual device name, it can be with random numbers.) Those steps worked for me so it should work for you to, rooting it then takes 10 minutes if I can remember.
Sent from my Nexus 7 using XDA Premium HD app
I did this last night and I had to put mine into ptp. Then adb would recognize it. After I got unlocked before I could root I had to re delete everything and then it recognized it.
Hope that helps.
Sent from my Nexus 7 using xda app-developers app
Related
Hey guys,
So my brother recently purchased a Bell Motorola Atrix. I have been trying to root it for him in order to install the hack where you can access the WebTop environment via a normal HDMI cable.
I tried SuperOneClick, and it says rooting successful (even after it does the test to determine if the device is rooted) and SuperUser does appear in the applications list. I also tried UniversalAndroot, also to no avail.
However, any applications that require root claim that the device is not rooted.
Are there any other ways of rooting this device? Or am I just doing something wrong? (keep in mind I have rooted several other devices with SuperOneClick, and those have all been successful)
Please help,
Thanks,
DS1495
look for "adeo" in the dev forum. try that
Try rebooting? That's what happened with mine.
franciscojavierleon said:
look for "adeo" in the dev forum. try that
Click to expand...
Click to collapse
DONT DO THIS.
He has a Bell Atrix.
I had to toggle debug on and off a few times before it would move past waiting for device.
Make sure you have the mkro drivers installed. Also the phone should be in phone portal mode, I believe.
Good luck
Sent from my MB860 using XDA App
joelszs said:
I had to toggle debug on and off a few times before it would move past waiting for device.
Make sure you have the mkro drivers installed. Also the phone should be in phone portal mode, I believe.
Good luck
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I don't think it matters what it's set as, but I believe most devs recommend none.
DS1495 said:
Hey guys,
So my brother recently purchased a Bell Motorola Atrix. I have been trying to root it for him in order to install the hack where you can access the WebTop environment via a normal HDMI cable.
I tried SuperOneClick, and it says rooting successful (even after it does the test to determine if the device is rooted) and SuperUser does appear in the applications list. I also tried UniversalAndroot, also to no avail.
However, any applications that require root claim that the device is not rooted.
Are there any other ways of rooting this device? Or am I just doing something wrong? (keep in mind I have rooted several other devices with SuperOneClick, and those have all been successful)
Please help,
Thanks,
DS1495
Click to expand...
Click to collapse
Use aroot (dev section) worked great on 1st try on my Bell Atrix
Whatever works I guess
PixoNova said:
I don't think it matters what it's set as, but I believe most devs recommend none.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
Thanks guys, aRoot worked wonderfully! First try!
I have tried the aRoot on the Atrix I just bought yesterday from Bell (I am now a bell customer :-( ) but it doesn't work. I must be missing something. I double click the script, it runs through all the steps, even says, rebooting at the bottom, but it does nothing. I press any key to continue, and nothing.
any thoughts would be appreciated.
Thanks,
AZ
Figured it out, turns out it wasn't recognizing the adb driver.
nick78ru said:
Had this problem. While connected (as USB storage) uncheck USB debugging and and enable it again. Check in Control Panel=>Device manager for ADB Services (should be at the top with sublisting for Motorola usb device or smthing like that).
Then open command promt:
cd\
cd\AndroidSDK(or whatever you called the SDK folder)\tools\
adb devices
Let me know if it helps
Click to expand...
Click to collapse
Im getting a bit confused here, my devices is rooted, busybox is installed. I have updated my SDK but still my terminal (ADB) cant find my device, could it be because my bootloader is still locked? I have choosen to not unlock my bootloader til a recovery is confirmed working on the arc.
Thanks in advance.
Juevani said:
Im getting a bit confused here, my devices is rooted, busybox is installed. I have updated my SDK but still my terminal (ADB) cant find my device, could it be because my bootloader is still locked? I have choosen to not unlock my bootloader til a recovery is confirmed working on the arc.
Thanks in advance.
Click to expand...
Click to collapse
Did you turn on usb debugging in settings?
Sent from my Nexus S using XDA Premium App
Yes the usb debugging is on :/
Sent from my LT15i using XDA App
are you running windows 7? (x86)?? The drivers for fastbooting don't work - have a look on the bootloader thread for the 64bit drivers.. http://forum.xda-developers.com/showthread.php?t=1034087
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, 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
Hey everyone, made a tutorial showing how to unlock the bootloader on your Nexus 9! I'll make rooting videos and more soon enough.
Hope they help.
How to unlock the bootloader:
https://www.youtube.com/watch?v=AJEORWbf658
How to root the Nexus 9:
http://youtu.be/5jwoPx5mB7Y
Unboxing and hands on:
https://www.youtube.com/watch?v=8K5WAmwRH7o
Doing it as soon as i get home .
That's the first nexus device I've seen that doesn't use Google's bootloader, very interesting!
Sent from my Nexus 10 using Tapatalk
Good news: You can unlock the bootloader under the development tab in settings. http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/
lary50 said:
Good news: You can unlock the bootloader under the development tab in settings. http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/
Click to expand...
Click to collapse
Thanks for that, I kept getting permission denied. All is well now ?
I wonder what HTC means when they say ,"this *may* void your warranty" when unlocking the bootloader. Did the all the other nexus devices say that in the bootloader before they were unlocked?
Deltadroid said:
Did the all the other nexus devices say that in the bootloader before they were unlocked?
Click to expand...
Click to collapse
My nexus 4 did.
I guess it's fine as long as it's not being permanently marked with some bit set somewhere so their service department can see. The device can be locked again.
pantmunu said:
Doing it as soon as i get home .
Click to expand...
Click to collapse
same there but them i get it i will
Edit: no need to set up adb or fastboot
i have ubuntu haha
Deltadroid said:
I wonder what HTC means when they say ,"this *may* void your warranty" when unlocking the bootloader. Did the all the other nexus devices say that in the bootloader before they were unlocked?
Click to expand...
Click to collapse
They did. Although you can just type fastboot oem lock and it should relock the bootloader without wiping any data.
Will wait till root is available to unlock it
mk92595 said:
Will wait till root is available to unlock it
Click to expand...
Click to collapse
No way. Unlocking wipes the device, but rooting doesnt. I plan to unlock mine the second I get it. That way I can start loading data and stuff onto it and start using it. Then, when root is available, I don't have to wipe my data at that point to do it becuase I was already proactive about unlocking the bootloader.
qbking77 said:
Hey everyone, made a tutorial showing how to unlock the bootloader on your Nexus 9! I'll make rooting videos and more soon enough.
Hope they help.
How to unlock the bootloader:
https://www.youtube.com/watch?v=AJEORWbf658
Unboxing and hands on:
https://www.youtube.com/watch?v=8K5WAmwRH7o
Click to expand...
Click to collapse
Hey great tutorial!
I got 1 problem.
I installed the latest android the latest sdk of android on my pc.
Followed the tutorial from you to setup adb. although its from 2011
and when i tried to do: 'adb devices' nothing happened.
The list stayed empty and my nexus 9 didn't have a pop up.
I had the nexus 9 unlocked with the screen on.
berendspruijt said:
Hey great tutorial!
I got 1 problem.
I installed the latest android the latest sdk of android on my pc.
Followed the tutorial from you to setup adb. although its from 2011
and when i tried to do: 'adb devices' nothing happened.
The list stayed empty and my nexus 9 didn't have a pop up.
I had the nexus 9 unlocked with the screen on.
Click to expand...
Click to collapse
Same there win 8
But I unlocked it
On Ubuntu
berendspruijt said:
Hey great tutorial!
I got 1 problem.
I installed the latest android the latest sdk of android on my pc.
Followed the tutorial from you to setup adb. although its from 2011
and when i tried to do: 'adb devices' nothing happened.
The list stayed empty and my nexus 9 didn't have a pop up.
I had the nexus 9 unlocked with the screen on.
Click to expand...
Click to collapse
If you're on Windows, it could be a driver problem. You can check on it in Windows device manager. If you need to install the driver, Open the Android SDK manager and make sure the USB driver is installed, and install any available updates. If that doesn't work, you can find the Google nexus USB driver by itself and install it using the windows device manager. You can search for the relevant step by step guides here on the forum or elsewhere online.
mrkvchm said:
No way. Unlocking wipes the device, but rooting doesnt. I plan to unlock mine the second I get it. That way I can start loading data and stuff onto it and start using it. Then, when root is available, I don't have to wipe my data at that point to do it becuase I was already proactive about unlocking the bootloader.
Click to expand...
Click to collapse
I already installed everything I need. also with ADB you can backup apps easily.
mk92595 said:
I already installed everything I need. also with ADB you can backup apps easily.
Click to expand...
Click to collapse
But you'll have to reinstall everything when you unlock the bootloader. I know its not hard to do with ADB, but I don't understand why you'd bother backing up and restoring everything when you can just unlock the bootloader right away and save yourself from wiping to root once you're already established on the device. Well, to each his own I guess.
If i unlock my nexus9 do i still get android OTA's?
hill67 said:
If i unlock my nexus9 do i still get android OTA's?
Click to expand...
Click to collapse
Yes
mrkvchm said:
But you'll have to reinstall everything when you unlock the bootloader. I know its not hard to do with ADB, but I don't understand why you'd bother backing up and restoring everything when you can just unlock the bootloader right away and save yourself from wiping to root once you're already established on the device. Well, to each his own I guess.
Click to expand...
Click to collapse
I already have my Nexus 9. Everything is already installed.