My Nexus 7 (2012), with broken usb port, lost root while updating but the bootloader is still unlocked. Also, I have no recovery on it and have been unable to flash a new one so far.
Is there any way to salvage root via terminal or am I SOL? I've searched the forum but haven't been able to find anything that specifically applies to my situation. Help?
P.S. I'm charging it via the dock, thanks for asking
ndhusn said:
My Nexus 7 (2012), with broken usb port, lost root while updating but the bootloader is still unlocked. Also, I have no recovery on it and have been unable to flash a new one so far.
Is there any way to salvage root via terminal or am I SOL? I've searched the forum but haven't been able to find anything that specifically applies to my situation. Help?
P.S. I'm charging it via the dock, thanks for asking
Click to expand...
Click to collapse
I think you're SOL - Every which way I think about this... It always comes down to having a working USB connection.
Hi, ndhusn....
I've been thinking about your situation all day... and I can't think of anything that would work.
The "traditional" way of rooting the Nexus 7 is...
** fastboot flash a custom Recovery (CWM or TWRP)...
** Using that Custom Recovery, flash Chainfire's SuperSU root package.
But with a knackered USB port, you obviously can't fastboot flash anything.
Looking into alternative options... there is something called CF-autoroot...
http://autoroot.chainfire.eu
http://forum.xda-developers.com/showthread.php?t=2025272
I've never used this means of rooting myself... but it has been mentioned several times on this forum. It's chief advantage, it seems, is it doesn't require the fastboot flashing of a Custom Recovery first.... so I thought this might work for you. But upon closer examination, it appears you still have to hook up your Nexus 7 to a PC via USB in order to run it.
--------------------------------------
Without CWM or TWRP installed, I can't think of any way of rooting your Nexus 7.
The irony here is... that there IS A WAY of flashing a Custom Recovery without recourse to fastboot (and the need for a USB connection) using the Flashify app. But you need root to do it. You can even flash a Custom Recovery via a terminal shell, with...
Code:
$ su
# dd if=/sdcard/recovery-image-file.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
...but as you can see from the initial su command, root already needs to be available.
You're stuck in a 'chicken and egg' situation! You can't root without a Custom Recovery... and you can't install a Custom Recovery without root.
--------------------------------------
Even a 'root exploit' requires a USB connection... like the old 'motochopper exploit' which would root the Nexus 7 even with a LOCKED bootloader. Anyway, that 'exploit' now no longer works, since Google 'blocked' such exploits as of Jellybean 4.3 onwards.
--------------------------------------
ndhusn said:
...I'm charging it via the dock, thanks for asking...
Click to expand...
Click to collapse
If the USB port is that damaged, such that you have to use the dock to charge, then presumably this precludes the possibility of trying another, different USB cable... with the intent of fastboot flashing TWRP or CWM.
Sometimes, it's just the USB cable at fault... and not the USB port itself. Anyway, just a thought.
--------------------------------------
I'm sorry to say, that without a working USB port on your Nexus 7, I don't think you'll be able to root it... or at least, I can't think of anyway of doing so.
Rgrds,
Ged.
*** Edit & addendum - WARNING ***
Whilst tinkering around with various methods in order to acquire root, will likely not hardbrick your Nexus 7... but they may cause softbrick/bootloop situations.
Normally, these are relatively trivial to resolve... but in your situation, they could be permanent.
Without a Nandroid backup created with a Custom Recovery, you won't be able to restore back to a previously known 'good' version of Android.
And without a working USB port, you won't be able to fastboot flash a Google factory image.
So... tread carefully.
Better a working Nexus 7 without root, then a Nexus 7 perpetually locked in a bootloop. It's unlikely, but be aware that you're recovery options are limited.
Needs be as needs must...
I have a broken port also! Low quality parts.
Cheapest replacement I have found is here....
http://www.asusparts.eu/Asus-08301-00522000
I know this doesn't answer your question but always good to have options.
Related
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.
Noob for tablets. Got the nexus 10 for the family for christmas. Want to get it all setup before I turn it over to the wolves.
I love using TBpro on my Droid Bionic. I thought it would be good to have a solid backup program on the tablet, and since I have it on my smartphone I thought I would hang with what I've sorta know already.
Dont really understand what unlocked/locked means for a bootloader, and why the N10 needs that why many smartphone can be rooted without being unlocked.
I would love to hear some views on the purposes of apps like ClockWorkMod and TWRP and what they do and provide. Seems like they do perform backups and more. Why TBpro is likely just a backup app. What functions do these recovery apps have the make them "must have".
thanks for the time answering the tablet noob
TBPro requires Root access and to acquire root access you have to be able to modify the operating system. You can't do that until the bootloader is unlocked. Once unlocked, you then need to flash Custom Recovery (either CMW or TWRP) in order to to flash/install the the files required to install the root binaries. Other uses of recovery include making NAND/System Backups and installing custom roms. They are essential if you are into modding your device. I have an LG G2x that is rooted and has a custom rom (CM7.2) and a Custom Kernel (Faux123 v54), as well as Beats Audio for Gingerbread. I installed all of those via ClockworkMod. I followed ZedoMax's instructions to root my Nexus 10 and had only the initial bootloop issue after unlocking the bootloader. That was easy to fix but I couldn't get ClockWorkMod to stay installed so I flashed TWRP instead. Works great. Just follow this thread and watch the vids. Hope I helped some.
http://forum.xda-developers.com/showthread.php?t=1997227
bg1906 said:
TBPro requires Root access and to acquire root access you have to be able to modify the operating system. You can't do that until the bootloader is unlocked. Once unlocked, you then need to flash Custom Recovery (either CMW or TWRP) in order to to flash/install the the files required to install the root binaries. Other uses of recovery include making NAND/System Backups and installing custom roms. They are essential if you are into modding your device. I have an LG G2x that is rooted and has a custom rom (CM7.2) and a Custom Kernel (Faux123 v54), as well as Beats Audio for Gingerbread. I installed all of those via ClockworkMod. I followed ZedoMax's instructions to root my Nexus 10 and had only the initial bootloop issue after unlocking the bootloader. That was easy to fix but I couldn't get ClockWorkMod to stay installed so I flashed TWRP instead. Works great. Just follow this thread and watch the vids. Hope I helped some.
http://forum.xda-developers.com/showthread.php?t=1997227
Click to expand...
Click to collapse
Thanks!
After unlocking, and using CMW or TWRP. I can then "root" my device. ok. After rooting, I can use TBpro.
At this point, do I need to remain "unlocked" Does it matter? For the N10 will I receive OTA after being unlocked/rooted,
or do I need to be in another state?
jetguat said:
Thanks!
After unlocking, and using CMW or TWRP. I can then "root" my device. ok. After rooting, I can use TBpro.
At this point, do I need to remain "unlocked" Does it matter? For the N10 will I receive OTA after being unlocked/rooted,
or do I need to be in another state?
Click to expand...
Click to collapse
Yes to all. Another option for you if you are not comfortable typing in the various commands is to use the Wufresh method. Watch the video by qbking777 here: http://forum.xda-developers.com/showthread.php?t=2015467
bg1906 said:
Yes to all. Another option for you if you are not comfortable typing in the various commands is to use the Wufresh method. Watch the video by qbking777 here: http://forum.xda-developers.com/showthread.php?t=2015467
Click to expand...
Click to collapse
Thanks again. I did stumble across that site and was trying to compare that to the mskip Nexus root tool kit. That was had so many options and I didnt (yet) find the cliff note's version on what they all do and why you'd need to.
The GUI for Wufresh is simple. Do you use it? I read a little about the root and the root+custom recovery choices. Not entirely clear which is preferred, at least for me needs. And I've not got a warm fuzzy feeling about what state the N10 should be in, such that OTA updates still happen. Can they happen when unlocked+rooted+custom recovery but still stock ROM (without system mods)
The wugfresh version automates what the zedomax version does by hand. I did mine via the zedomax way.
Sent from my Nexus 10 using xda app-developers app
jetguat said:
Thanks again. I did stumble across that site and was trying to compare that to the mskip Nexus root tool kit. That was had so many options and I didnt (yet) find the cliff note's version on what they all do and why you'd need to.
The GUI for Wufresh is simple. Do you use it? I read a little about the root and the root+custom recovery choices. Not entirely clear which is preferred, at least for me needs. And I've not got a warm fuzzy feeling about what state the N10 should be in, such that OTA updates still happen. Can they happen when unlocked+rooted+custom recovery but still stock ROM (without system mods)
Click to expand...
Click to collapse
I would suggest using the Wugfresh method, definitely the simplest to use. And a great recovery is TWRP, it is very clear and easy to understand what it is that each menu contains.
Also with the OTA updates, it really depends on the size and type of update. If it is a fairly major one, like JB 4.1 to JB 4.2 then you will have to use the option in Wugfresh toolkit to 'unroot', then update. After the update you can simply reuse the toolkit to root again. Sometimes if the OTA is small it will simply install over the rooted device, but I wouldn't count on it. It definitely shouldn't discourage you from rooting though, its relatively simple to fix
I am a newbie. I want to root my Nexus 7 GSM on stock JB4.3 to read USB drives on OTG cable. Will the CF-Auto-Root-tilapia-nakasig-nexus7.zip downloaded from' http://download.chainfire.eu/294/CF-Root/CF-Auto-Root/CF-Auto-Root-tilapia-nakasig-nexus7.zip' work on stock JB4.3 N7 GSM? After rooted my N7, will there be any problems updating future system upgrades? Thanks.
Bump
SamOntario said:
I am a newbie. I want to root my Nexus 7 GSM on stock JB4.3 to read USB drives on OTG cable. Will the CF-Auto-Root-tilapia-nakasig-nexus7.zip downloaded from' http://download.chainfire.eu/294/CF-Root/CF-Auto-Root/CF-Auto-Root-tilapia-nakasig-nexus7.zip' work on stock JB4.3 N7 GSM? After rooted my N7, will there be any problems updating future system upgrades? Thanks.
Click to expand...
Click to collapse
Anyone?
Why wouldn't you just do it the right way? Unlock bootloader, fastboot flash a recovery, then flash supersu.zip in recovery?
Sent from my Galaxy Nexus
Pirateghost said:
Why wouldn't you just do it the right way? Unlock bootloader, fastboot flash a recovery, then flash supersu.zip in recovery?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks for the reply but these sound too complicated to me. I don't want to brick my N7 during these process or future updates. All I want is root the N7 and then mount something like stickmount and then to be able to read my USB flash drives. I am willing to try if detailed step by step procedures are available.
it is rather difficult to brick a nexus device. I am not sure what you expect CF-Auto-Root to do for you, but it does pretty much these steps.
if you cannot read the stickies that literally walk you through step by step how to root an easily rootable device, then you should not be modifying your device at all.
Pirateghost said:
it is rather difficult to brick a nexus device. I am not sure what you expect CF-Auto-Root to do for you, but it does pretty much these steps.
if you cannot read the stickies that literally walk you through step by step how to root an easily rootable device, then you should not be modifying your device at all.
Click to expand...
Click to collapse
Thanks for the reply again. On the safe side, I will take your advice not to root my N7.
SamOntario said:
Thanks for the reply again. On the safe side, I will take your advice not to root my N7.
Click to expand...
Click to collapse
I guess reading the stickies was too much work?
Sent from my Nexus 7
Pirateghost said:
I guess reading the stickies was too much work?
Sent from my Nexus 7
Click to expand...
Click to collapse
I am a newbie and have no special knowledge about androids like you guys who already spent a few years or a few months on it. Will be easy for you modding and too difficult for me especially my N7 is JB 4.3 which stickies seemed lacking. I couldn't tell those stickies which line is applicable and which line is outdated. I am concerning just rooting with the capability of reading USB flash drives without affecting the stock ROM for future upgrades. I guess my N7 should have at least 3 more years' usage and upgrades. I don't want the upgrades affected by modding with my limited/ignorant knowledge.
I am a user only and I am an old guy. Even I learn all stickies, I will only have limited use of these knowledge in future. Not very cost effective use of my time.
It doesn't matter what version of android you are on. rooting a nexus is the same no matter what OS version you are on.
Here are the key points to rooting a nexus device (these are what you should watch for when reading the stickies)
Unlock bootloader with 'fastboot oem unlock' <--the guides explain fastboot and how to use it (fastboot oem unlock WIPES the device)
flash a custom recovery (twrp or CWM) using 'fastboot flash recovery nameofrecovery.img' or if you dont want to have permanent custom recovery, use 'fastboot boot nameofrecovery.img'
using the custom recovery you can either 'adb push SuperSU-ver-x.x.zip /data/media/' or you can mount your USB OTG and flash the zip file directly from there
reboot and you are rooted
Thanks for all the efforts.
I'm in a bit of a hard place - I'd previously unlocked, loaded TWRP and rooted my Gen1 Nexus 7. I can no longer boot into recovery and get the " no command" message. This also gets in the way of the KitKat upgrade process. With all that said, the tablet works fine under 4.3 stock.
Here's the rub - one morning stumbling out of bed I stepped into a loop of USB cable that was charging the Nexus, yanked the cable and tablet violently enough to damage the USB port. Data communications or charging no longer work via USB. Fortunately I can still charge via dock and pogo pins.
Besides buying a new tablet or replacing the ports (about $60 on eBay) can anyone suggest another method to recover or load a bootloader?
Sent from my Nexus 7 using Tapatalk 4
Pretty sure you mean recovery, not bootloader.
The OS still works right? Just flash a recovery using an app like flashify and you're good to go.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Not sure what flashing a bootloader has to do with this.
If your bootloader is locked, you can't "flash an unlocked one"*, but even if you could, that wouldn't help as you still would not have use of fastboot via the USB to do a "fastboot flash of a recovery". And fastboot only speaks to the tablet when the bootloader is running, not when a kernel is loaded (recovery or regular boot).
To get a custom recovery re-installed, you can do that by using "dd" to overwrite the recovery partition from ANY root-privileged shell (either a custom recovery or a rooted ROM). So there's the rub: you need something running with root privilege.
If that is not the case (rooted ROM) you need to either find a "root exploit" for your current ROM, or get your USB plug repaired. You could run ADB over your WiFi network (instead of via the USB cable) or just use a terminal emulator app to run exploit codes.
I haven't been keeping up with things, but the "motochopper" exploit was exactly that - a method of rooting a stock ROM that avoids fooling with fastboot or the lock state of the bootloader. But that was a while ago, and I don't know whether it still works against newer stock ROMs. (Besides, you neglected to even mention what is currently on your tablet)
Good luck.
*actually you can, but only if you have a rooted ROM or custom recovery running AND you previously captured a raw dump of a certain partition while the bootloader was in an unlocked state (bootloader is encrypted on a per-tablet basis). I think osm0sis disclosed this method a long long time ago.
I apologize for my probable misuse of terms - in short (unless I can find a root exploit) a new Nexus 7 may be on my XMas list. I greatly appreciate your input.
Sent from my Nexus 7 using Tapatalk 4
Hello all,
Here is my situation:
- I have my brother's Nexus 4.
- The screen no longer responds to touch, though it still displays correctly when it is turned on.
- It has PIN security
- It is running stock KitKat 4.4.4.
- It is not rooted.
- USB Debugging (ADB) is not enabled.
- Stock recovery is installed.
- The bootloader is locked.
I would like to be able to back up the contents of the phone, but the state it is in renders that difficult. Here are the different options I've considered and discarded:
- Connect the phone via USB to copy the contents of the SD Card
# Impossible since the phone will not mount USB storage (might be a security feature since it has PIN enabled?)
- USB OTG mouse to bypass using the touchscreen
# OTG support is not available on stock kernels for the N4
- Bluetooth mouse
# No way to enable Bluetooth
- Use Android Control to control the phone via my PC
# No ADB; no way to enable ADB; unlocking bootloader to install a recovery with ADB enabled would wipe the phone.
The only option that might work that I have yet to attempt is to replace the screen. However, based on research I did while trying to troubleshoot my own Nexus 4, this could be a costly waste of time. The Nexus 4 has a history of having faulty touchscreens. Case in point, both my phone and my brother's phone suffered from this same flaw. This might be because the touchscreen controller is bad on the N4's motherboard. I junked my N4 specifically for this reason.
I'm beginning to think that there is no way for me to recover the data on this phone. Does anyone know of a way I could get the data off of it? Any way to enable ADB via Fastboot or Recovery? Any way to flash an ADB-enabled kernel via ADB sideload? Any way to unlock the bootloader without wiping all the data? Any way to run a backup of the whole phone?
Please help! Thank you in advance!
You might try towelroot to root. Then bootunlocker from the play store to unlock but you'd have to be able to use the touch screen. Long and short, you're kind of screwed
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You might try towelroot to root. Then bootunlocker from the play store to unlock but you'd have to be able to use the touch screen. Long and short, you're kind of screwed
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yup, that's pretty much what I thought. I was hoping someone here could think of something I hadn't thought of yet. Basically, I think the only two avenues I have to send anything to the phone are via the Bootloader (Fastboot) or via ADB sideload in Recovery. I was hoping I could find something to save me there, but it is looking unlikely.