Hi
I was trying to root Nexus 5 with Windows 7 laptop. Got the error message shown in the picture.
" Rooting Failed! Command write failed (Too many links) "
Anyone know what is going on?
Any and all help is appreciated!
EDIT: I was able to unlock the bootloader but I still do not have root access!
saadster25 said:
Hi
I was trying to root Nexus 5 with Windows 7 laptop. Got the error message shown in the picture.
" Rooting Failed! Command write failed (Too many links) "
Anyone know what is going on?
Any and all help is appreciated!
Click to expand...
Click to collapse
Dont root with toolkits. Use this method http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
GUGUITOMTG4 said:
Dont root with toolkits. Use this method http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
I second this
Sent from my Nexus 5 using XDA Premium 4 mobile app
That and don't use s USB 3 port.
As @aooga said, make sure you use a USB 2.0 port. If that doesn't fix it, try another USB cable.
El Daddy said:
As @aooga said, make sure you use a USB 2.0 port. If that doesn't fix it, try another USB cable.
Click to expand...
Click to collapse
GUGUITOMTG4 said:
Dont root with toolkits. Use this method http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Wasn't using toolkits, was following CF auto root method as described on various sources including youtube videos.
Could it be just as simple as using a USB 2.0 port? Seems trivial.
saadster25 said:
Wasn't using toolkits, was following CF auto root method as described on various sources including youtube videos.
Could it be just as simple as using a USB 2.0 port? Seems trivial.
Click to expand...
Click to collapse
USB 3 is the killer of all this adb stuff especially on Windows 8+. Just use a USB 2.
aooga said:
USB 3 is the killer of all this adb stuff especially on Windows 8+. Just use a USB 2.
Click to expand...
Click to collapse
Alright will try that. However just to let you know under the ADB devices command my device does show up listed and I am able to ADB pull apks off the device. Just this error message seems to come out of no where.
saadster25 said:
Alright will try that. However just to let you know under the ADB devices command my device does show up listed and I am able to ADB pull apks off the device. Just this error message seems to come out of no where.
Click to expand...
Click to collapse
Yeah I know. This happened to a bunch of other people too. I see you already unlocked the bootloader, so I'm assuming you know what to do from here. (flash recovery and flash the root.zip)
saadster25 said:
Wasn't using toolkits, was following CF auto root method as described on various sources including youtube videos.
Could it be just as simple as using a USB 2.0 port? Seems trivial.
Click to expand...
Click to collapse
We consider it a toolkit because it does things (a couple of them) for you. Now you run into issues and don't know what failed because it was doing hidden tasks.
The manual method besides doing the job, will teach you a thing or 2 or 3, plus will help you to troubleshoot simple things.
aooga said:
Yeah I know. This happened to a bunch of other people too. I see you already unlocked the bootloader, so I'm assuming you know what to do from here. (flash recovery and flash the root.zip)
Click to expand...
Click to collapse
Side question, does rooting phone and unlocking the bootloader stop over the air (or any kind of) updates from google?
saadster25 said:
Side question, does rooting phone and unlocking the bootloader stop over the air (or any kind of) updates from google?
Click to expand...
Click to collapse
Technically, yes, but here is a thread with all the workarounds http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
saadster25 said:
Side question, does rooting phone and unlocking the bootloader stop over the air (or any kind of) updates from google?
Click to expand...
Click to collapse
If you only unlock the BL/root the phone and don`t uninstall/replace system components you will still be able to receive and install OTA`s with the stock recovery. You`ll have to reroot afterwards though, but that only takes a minute.
Related
hi, ive been having issues rooting this phone.
Ive tried 4 different cables & 2 different laptops.
Have the latest usb drivers + the samsung drivers. I did notice that it cant be found in device manager.
when i click on the bat file in qbkings one click root folder, i get "device not found". <duh
Usb debugging is enabled. Could the phone itself be damaged?
You're better off unlocking the bootloader and flashing custom recovery through adb. The directions aren't difficult to find (I'd link you but I'm on my phone). That way if something goes wrong you know where it failed instead of being dependent on a piece of software.
I wish everybody did it this way. Plus, I 100% agree with your statement. Not only that, you learn a few things along the way
mrmondaynight said:
hi, ive been having issues rooting this phone.
Ive tried 4 different cables & 2 different laptops.
Have the latest usb drivers + the samsung drivers. I did notice that it cant be found in device manager.
when i click on the bat file in qbkings one click root folder, i get "device not found". <duh
Usb debugging is enabled. Could the phone itself be damaged?
Click to expand...
Click to collapse
Before trying to root the phone, did you ever connect to any computer at all?
And what ru on...GB 2.37?
Vs Nexus S 4G
063_XOBX said:
You're better off unlocking the bootloader and flashing custom recovery through adb. The directions aren't difficult to find (I'd link you but I'm on my phone). That way if something goes wrong you know where it failed instead of being dependent on a piece of software.
Click to expand...
Click to collapse
man, im slow. Im having a hard time locating the directions :crying:
vidaljs said:
Before trying to root the phone, did you ever connect to any computer at all?
And what ru on...GB 2.37?
Vs Nexus S 4G
Click to expand...
Click to collapse
Yes.
Same issue. Even with usb storage.
phone is on ICS 4.0.4 via ota update.
http://forum.xda-developers.com/showthread.php?t=1623481
Step by Step Root is here in the sticky. If the phone isn't seen just to see the SD card then the phones USB may be shot and that is a hardware issue.
o I rooted my nexus 5. No issues. Installed TWRP. Same. Downloaded CM and GA to the phone. Then, very foolishly, wiped everything to prep for the install - SD card included. Now, all I can load is TWRP. No ROM to be found - obviously. Computer won't recognize the phone to load a ROM that way. Would be VERY appreciative of any help. TY!S
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
meangreenie said:
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
Click to expand...
Click to collapse
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
bradley.robt said:
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
Click to expand...
Click to collapse
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
aldyu said:
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
Click to expand...
Click to collapse
Sorry, assume 'adb devices' is in the command prompt, but noob town - which folder in the ADT parent folder?
RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
That's what I figured, but...challenge accepted. Thanks for the links.
RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
RoyJ,
Appreciate the help. TY, all's good.
Happened to me a few times tinkering with the gnex, n4...boneheadedly wiped the internal storage. Easiest fix in my opinion is to just flash factory stock and start back from stretch. If not like they said you're in for a long night trying to get your phone to sync up to push the files via adb if you aren't familiar with the stuff.
Do wish you the best. Been there.
I have not been in that situation but couldn't you use a OTG cable (a Y type one which accepts power as well) and a SD card or stick and then mount it within TWRP to access a ROM to flash...?
EDIT: Also consider the Nexus Toolkit - very useful.
I really think that the faster way is to flash stock firmware back (if you have no experience with ADB commands).
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
TheLastSidekick said:
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
It's really not that hard.. You plug it in, open a folder, open the prompt and type a few words.. My advice is to try and learn.
sent from my Nexus 5
Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Glad you got it sorted.
Letharqy said:
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Click to expand...
Click to collapse
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
TheLastSidekick said:
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
No, you didn;t get my point. I told him to straight away restore by images just because his phone wasn't working at all. He can learn all that stuff later, but atleast he should be with no phone at all.
Seadra said:
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
Click to expand...
Click to collapse
How would you flash the .imgs without using adb/fastboot?
Letharqy said:
How would you flash the .imgs without using adb/fastboot?
Click to expand...
Click to collapse
by adb drivers, I mean adb/fastboot or SDK and drivers of the phone that's always included.
Hey guys,
I am pretty new to the rooting stuff on the Nexus.
I read the sticky threat from rootSU (http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527) and followed his description. So I installed ADB and fastboot through the "15 sec. installer" (http://forum.xda-developers.com/showthread.php?t=2588979).
So fast so good, everything went fine. But as I tried to "check" if ADB and fastboot are recognizing my device with the command "adb devices" and "fastboot devices" in cmd, I got some strange output (look at the picture).
How can it be that ADB "sees" my device and fastboot not? What I did wrong there?
(I didn't installed the drivers with the 15 sec tool; when I plugged in my device to the computer, it downloaded the drivers itself)
Any help would be very appreciated!
Follow the next step on my thread and install the naked drivers
Okay thank you!
I'll try it tonight and report back.
I also thought of a problem with the drivers, but I thought that I messed up with installing ADB and fastboot somehow, because ADB could recognize my device.
One question again: When I uninstall the Nexus 5 drivers and I reconnect my phone to the pc, it download the driver itself.. How can I stop that to install the naked drivers?
Blackbox421 said:
Okay thank you!
I'll try it tonight and report back.
I also thought of a problem with the drivers, but I thought that I messed up with installing ADB and fastboot somehow, because ADB could recognize my device.
One question again: When I uninstall the Nexus 5 drivers and I reconnect my phone to the pc, it download the driver itself.. How can I stop that to install the naked drivers?
Click to expand...
Click to collapse
Remember - adb ONLY works when Android is booted up or you're in recovery, fastboot ONLY works when you're in the bootloader
EddyOS said:
Remember - adb ONLY works when Android is booted up or you're in recovery, fastboot ONLY works when you're in the bootloader
Click to expand...
Click to collapse
Damn, thats it! I am so dumb! I don't know how I could forget that.. I read it some hours ago.
After I went into bootloader mode, fastboot recognized my device!
Thanks a lot guys, now I can go to the next step to root my device! =)
Btw.. another question, which is offtopic - does it makes a difference to root KitKat or Lollipop? I guess the guides around here are all made for KitKat and I don't want to mess up. :/ Thx!
Blackbox421 said:
Damn, thats it! I am so dumb! I don't know how I could forget that.. I read it some hours ago.
After I went into bootloader mode, fastboot recognized my device!
Thanks a lot guys, now I can go to the next step to root my device! =)
Btw.. another question, which is offtopic - does it makes a difference to root KitKat or Lollipop? I guess the guides around here are all made for KitKat and I don't want to mess up. :/ Thx!
Click to expand...
Click to collapse
@rootSU has posted some new guides on rooting Lollipop, so best read his threads in the General section
To root Lollipop you have to use Chainfire Auto Root. There is extra security in Lollipop that keeps the old root method from KitKat from working.
Oh I see..thats annoying. But thank you for your answers! I guess I'll read those threads. =)
Btw.. Can you guys tell me if I understood everything..:
To go back to the official 4.4.4., I don't have to root my device, right? I "only" have to unlock my bootloader and flash the official factory image through fastboot. And afterwards I could root my device using the guides around here on xda.
Blackbox421 said:
Oh I see..thats annoying. But thank you for your answers! I guess I'll read those threads. =)
Btw.. Can you guys tell me if I understood everything..:
To go back to the official 4.4.4., I don't have to root my device, right? I "only" have to unlock my bootloader and flash the official factory image through fastboot. And afterwards I could root my device using the guides around here on xda.
Click to expand...
Click to collapse
That's correct!
EddyOS said:
That's correct!
Click to expand...
Click to collapse
Oh, actually thats all I wanted! =)
On my old Samsung Galaxy Ace you had to root your device first, before you even could install another stock rom, thats why I thought it would be the same for the Nexus 5.
Thanks alot, I'll save my data on my PC now and start with the "downgrading"!
Blackbox421 said:
Oh, actually thats all I wanted! =)
On my old Samsung Galaxy Ace you had to root your device first, before you even could install another stock rom, thats why I thought it would be the same for the Nexus 5.
Thanks alot, I'll save my data on my PC now and start with the "downgrading"!
Click to expand...
Click to collapse
It's all very easy with a Nexus device
EddyOS said:
It's all very easy with a Nexus device
Click to expand...
Click to collapse
Yeah I think I got it now. I unlocked my bootloader and flashed the official 4.4.4. factory image from the google developers website. Afterwards I booted into the stock recovery and wiped data/factory reset and reboot. Everything is fine now!
Thank you for your help! Learned a lot of basic understandings.
Jnewell05 said:
To root Lollipop you have to use Chainfire Auto Root. There is extra security in Lollipop that keeps the old root method from KitKat from working.
Click to expand...
Click to collapse
There are multiple methods. Cf auto root is just one of them.
I documented all methods in general. There's a link to my thread from "sticky roll-up in general
rootSU said:
There are multiple methods. Cf auto root is just one of them.
I documented all methods in general. There's a link to my thread from "sticky roll-up in general
Click to expand...
Click to collapse
Huh, I thought the methods from your thread would be only for KitKat
Blackbox421 said:
Huh, I thought the methods from your thread would be only for KitKat
Click to expand...
Click to collapse
I usualy root my Nexus by booting into a custom recovery (TWRP), flash the latest superSU.zip and any mod i want and reboot/done That way i keep my stock recovery.
guys i want to root my phone on the fast and very simple way possible.
found this root method on https://autoroot.chainfire.eu
this is the link for the root method https://download.chainfire.eu/982/C...Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip
i did not tryed it my self yet. but if theres a user that rooted their phone that way, let me know.
bump
I don't think this will work unless we get our Bootloader unlocked (which hasn't been done yet as far as i know)
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
this is kind of lame.... why chainfire release a auto root if the thevice have bootloader locked down? and onlockable?
Confused myself
I want to say root is possible, there are tons of sites with instructions: https://www.google.com/search?q=SM-...i57j0j69i60.9343j0j4&sourceid=chrome&ie=UTF-8
Of course, XDA doesn't seem to have a specific G930T thread for rooting with instructions, then see threads like this today. I was all set to give it a try, but unsure if should proceed...
Did find this: http://forum.xda-developers.com/tmobile-galaxy-s7/help/sm-g930t-root-doesnt-void-warranty-t3415936
EDIT: so the one linked in original comment was the bleeding edge root process and seems like had a really high failure rate. Most current I've seen is: http://lifeatsamsung.com/root-t-mobile-galaxy-s7-sm-g930t-2/
Seems a little more clean cut and easy. I'll edit again if I find a newer solution or at least commentary on success/fail
In comments OP posts:
Yes I am planning to make a video tutorial.
Also I used the method provided here (this is Max Lee's website)
Click to expand...
Click to collapse
blackwing182 said:
guys i want to root my phone on the fast and very simple way possible.
found this root method on https://autoroot.chainfire.eu
this is the link for the root method https://download.chainfire.eu/982/C...Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip
i did not tryed it my self yet. but if theres a user that rooted their phone that way, let me know.
Click to expand...
Click to collapse
So the solution and all the fixes, etc is right here: http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Worked for me, no problem. Even installed the debloated, deox'd ROM. Unfortunately after root you will need to follow rest of guide, otherwise you will see some lag issues.
On the other side of it, phone is great, fast, if not faster than before, and got root. Let me know if you would like some screenshots proving a TMO phone is rootable or if can answer any questions
blackwing182 said:
guys i want to root my phone on the fast and very simple way possible.
found this root method on https://autoroot.chainfire.eu
this is the link for the root method https://download.chainfire.eu/982/C...Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip
i did not tryed it my self yet. but if theres a user that rooted their phone that way, let me know.
Click to expand...
Click to collapse
I would like to see some screens that show it is rooted, yes. I am about to purchase tomorrow and would like everything in place before I do.
Thanks
Mordred said:
I would like to see some screens that show it is rooted, yes. I am about to purchase tomorrow and would like everything in place before I do.
Thanks
Click to expand...
Click to collapse
There is root but the bootloaders on USA snapdragon is still locked so it's not as smooth and simple as flashing cf root
TH3B0SS said:
There is root but the bootloaders on USA snapdragon is still locked so it's not as smooth and simple as flashing cf root
Click to expand...
Click to collapse
So what does this mean in layman's terms. Can I root the device safely with full functionality or not? Are there plans to get a rooted bootloader? And what does this mean because I thought the TMO version had a qualcom processor...
Mordred said:
So what does this mean in layman's terms. Can I root the device safely with full functionality or not? Are there plans to get a rooted bootloader? And what does this mean because I thought the TMO version had a qualcom processor...
Click to expand...
Click to collapse
This means that the only rooting method right now isn't as stable as it would be if it had a unlocked bootloader the root right now will cause some issues but they can easily be fix from some of the steps after rooting guides that are in the xda forums and yes it using a Qualcomm processor Witch is pretty much the snapdragon and there hasn't been any luck this past year of getting the bootloader unlocked for full and smooth rooting I'm really ****ty at explaining sorry if your still lost
The Chainfire method he released does NOT work. I'm not sure why he released it...maybe he knows of a future bootloader unlock that we don't know about.
@troby86 I see you have yours rooted. How did you accomplish this?
Mordred said:
@troby86 I see you have yours rooted. How did you accomplish this?
Click to expand...
Click to collapse
I used the engineering boot image to do it. There is a post in this forum that has a link to a guide to do it.
Thank you. Lots to look through.
troby86 said:
I used the engineering boot image to do it. There is a post in this forum that has a link to a guide to do it.
Click to expand...
Click to collapse
@troby86 OK, bought my S7 today. Trying Max Lee's root method. I can't get SU to inject using adb command. I have retried numerous times to include reflashing and system reset. Any thoughts?
Mordred said:
@troby86 OK, bought my S7 today. Trying Max Lee's root method. I can't get SU to inject using adb command. I have retried numerous times to include reflashing and system reset. Any thoughts?
Click to expand...
Click to collapse
Run CMD in admin mode or if the CMD prompt freezes unplug and replug in your phone and then it should start...
KillerClaw321 said:
Run CMD in admin mode or if the CMD prompt freezes unplug and replug in your phone and then it should start...
Click to expand...
Click to collapse
@KillerClaw321 I am at the machine now and have tried running CMD in admin mode. Still no joy. What are the beat adb drivers to use for AMD machine? Maybe the drivers are the problem? What else can I try? I am on PK1 as the phone is new from the store yesterday and a fresh shipment to them the day before.
I also see a DM verification verify failed dialogue at the bottom when i try the factory reset. No DRK
Mordred said:
@KillerClaw321 I am at the machine now and have tried running CMD in admin mode. Still no joy. What are the beat adb drivers to use for AMD machine? Maybe the drivers are the problem? What else can I try? I am on PK1 as the phone is new from the store yesterday and a fresh shipment to them the day before.
I also see a DM verification verify failed dialogue at the bottom when i try the factory reset. No DRK
Click to expand...
Click to collapse
Remove any existing drivers for your S7 and install this one
http://www.samsung.com/us/mobile/ph...7-32gb-t-mobile-gold-platinum-sm-g930tzdatmb/
Make sure you click allow on the pop-up on your phone after you plug it into the computer... Good Luck!
KillerClaw321 said:
Remove any existing drivers for your S7 and install this one
http://www.samsung.com/us/mobile/ph...7-32gb-t-mobile-gold-platinum-sm-g930tzdatmb/
Make sure you click allow on the pop-up on your phone after you plug it into the computer... Good Luck!
Click to expand...
Click to collapse
Sorry for being daft... I don't see a driver link and how do I remove the previous version?
Laptop is in for repairs so all I have is my old rooted 8T. Is it possible to unlock the bootloader and root my new phone with the 8t? If so how?
Yes using Termux + ADB/Fastboot for Android on the device you are using in place of a pc/laptop. Not worth the trouble if you have other options..
Andrologic said:
Yes using Termux + ADB/Fastboot for Android on the device you are using in place of a pc/laptop. Not worth the trouble if you have other options..
Click to expand...
Click to collapse
No other options. Too impatient to wait the couple weeks for my laptop to be fixed. Thanks though! I'll look into it.
If anyone cares, I did it. Unlocked the bootloader and got root no problem. No PC in sight. 5 minute job including downloads.
shadowofdeth said:
If anyone cares, I did it. Unlocked the bootloader and got root no problem. No PC in sight. 5 minute job including downloads.
Click to expand...
Click to collapse
Great!
And it would help others who are interested in this if you described how you did it.
Downloaded Msgisk ADB and fastboot
BillGoss said:
Great!
And it would help others who are interested in this if you described how you did it.
Click to expand...
Click to collapse
Exactly the same steps as if it was done on a computer only needing to download the adb fastboot Msgisk module like suggested earlier. That's it. That's all I did.
Was also able to fully wipe my old phone and relock the bootloader without issue too.