recently got a nexus 4 and now i trying to root but i need ADB well i installed the correct drivers and for it and then i go to use either nexus 4 tool kits and both say device is found but adb is offline i tried updating drivers even changing path for adb in environmental properties updated my sdk.. idk what else to do
do it the right way, use fastboot instead of a root toolkit. you dont need adb to root, all you need is fastboot.
fastboot oem unlock, fastboot flash a custom recovery, flash the su binaries or a custom rom in your new recovery, then reboot and profit.
KeemGoodFella said:
recently got a nexus 4 and now i trying to root but i need ADB well i installed the correct drivers and for it and then i go to use either nexus 4 tool kits and both say device is found but adb is offline i tried updating drivers even changing path for adb in environmental properties updated my sdk.. idk what else to do
Click to expand...
Click to collapse
The toolkits are using an outdated version of adb, 4.2.2 requires the latest release, and will have to be updated by their developers before they will work again.
http://forum.xda-developers.com/showpost.php?p=37989017&postcount=956
Related
System:
Windows 7 (x64)
Nexus S (Stock)
Android SDK (installed
Java (jre-jdk installed)
I did a nandroid backup on my device so i could 'pull' some fresh systemui.apk's and now when i enter bootloader to root my nexus s, adb will never find it .
My nexus s WAS fully rooted with su permissions and clockworkmod installed, now i cant 'fastboot flash recovery recovery.img' because i get '<waiting for device>' in my 'cmd' window.
If any could bring around any solutions i would surely thank you
XDA_Badman said:
System:
Windows 7 (x64)
Nexus S (Stock)
Android SDK (installed
Java (jre-jdk installed)
I did a nandroid backup on my device so i could 'pull' some fresh systemui.apk's and now when i enter bootloader to root my nexus s, adb will never find it .
My nexus s WAS fully rooted with su permissions and clockworkmod installed, now i cant 'fastboot flash recovery recovery.img' because i get '<waiting for device>' in my 'cmd' window.
If any could bring around any solutions i would surely thank you
Click to expand...
Click to collapse
I would try completely removing and then reinstalling the device drivers on your PC.
i would say check to make sure that you are in the right directory when trying to use fastboot or adb. when i downloaded sdk, the adb stuff was in "platform-tools" folder and fastboot stuff was in "tools" folder.
You need a special driver.
It's included in the PDA net pc program.
Sent from my Nexus S using XDA App
XDA_Badman said:
My nexus s WAS fully rooted with su permissions and clockworkmod installed, now i cant 'fastboot flash recovery recovery.img' because i get '<waiting for device>' in my 'cmd' window.
If any could bring around any solutions i would surely thank you
Click to expand...
Click to collapse
Did you boot into bootloader first before trying fastboot commands?
I Did something really stupid, I have a Nexus 7, rooted, unlocked, went to twrp and did a back up of the stock rom, it said successful, then rebooted used the rom, everything perfect but I had tablet mod on it, decided to go back to full stock, booted to recovery, wiped everything, tried to restore and my backup is not there, and I deleted the rom as well, so now I have no rom to flash and I'm stock in recovery, anyway to push a rom into the nexus in recovery or bootloader? I tried flashing it with root toolkit 1.5.5 but it doesn't find the tablet,(all the drivers are installed), any and all help is appreciated...
Your PC won't see your N7 in Android because you haven't turned on USB debugging, and probably can't now.
You should be able to push an updated TWRP in fastboot that will see your 4.2 backup. The older version can't find its backups in 4.2,as you've discovered.
I'm not the lowest of the low, but I am the slowest of the slow.
I did have it on, I can see the tablet from control panel, but when I run the kit it says adb device not found..
Sent from my EVO using xda app-developers app
The drivers will let your PC see the N7, but you have to be in USB debugging for ADB to work. You lost it when you wiped your system, as the failure of the toolkit to see the ADB proves.
I'm not the lowest of the low, but I am the slowest of the slow.
exglynco said:
The drivers will let your PC see the N7, but you have to be in USB debugging for ADB to work. You lost it when you wiped your system, as the failure of the toolkit to see the ADB proves.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
USB Debugging doesn't need to be on for ADB through recovery to work.. Why would it? The system isn't even on it is in recovery.
Try the toolkit in fastboot.
Sent from my Full Android on Grouper using Tapatalk 2
joshnichols189 said:
USB Debugging doesn't need to be on for ADB through recovery to work.. Why would it? The system isn't even on it is in recovery.
Try the toolkit in fastboot.
Sent from my Full Android on Grouper using Tapatalk 2
Click to expand...
Click to collapse
when I'm in the bootloader it says it's in fastboot mode, but the toolkit wont find it!
I running recovery 2.3.2.1
tried adb sideload as well and it says "cannot read sideload" any ideas? getting a little crazy here..
Can anybody give me specific commands in ADB or fast boot I'm an idiot when it comes to that, on how to try to push a ROM into the device so I can flash it from recovery, or maybe a link to where I can read about it, I would really appreciate it..
Sent from my EVO using xda app-developers app
While in recovery, type in the following:
Code:
adb push <name of ROM zip> /sdcard
You need to open a command prompt window, change directories (cd) to your Android SDK - platform tools directory, and to make things easy, move the ROM zip file into that directory as well (platform-tools that is). Then type the adb push command above.
EDIT: This puts the ROM zip on the root of your sd card (/sdcard). I have a ROM folder on my sd card, so I would type:
Code:
adb push <name of ROM zip> /sdcard/ROM
This just shows that you can push a file into a folder on your sd card.
Hi all,
First let me start by saying that I've been trying to get past this for the last 2 days. I just bought a nexus 10 (YAY!), However when i try to root it via skipsoft toolkit, i get the above error code...
Ive done the ctrl+shift+del and stopped any running adb processes, I've switched usb ports, and cannot figure this out. Am i missing a completely obvious step here? I've rooted many items using rhe same computer, and same type of toolkits offered by Mark... Any help would be truly appreciated!
Cheers,
Well its a nexus, toolkits are from needed
fastboot oem unlock
All data is wiped here, now make a choice for stock rooted or custom rom, but youre on xda so next steps
fastboot flash recovery nameofrecovery.img
Now reboot to new recovery (twrp is a good choice)
And flash rom and or any gapps here
If none on device, which after unlock i doubt it, use an otg cable or adb sideload
Then reboot, all takes 5min tops
For your adb issue make sure you update your sdk, then open cmd/terminal and type
adb kill server
adb start server
If you just want stock rooted or cant find needed files let me know
Happy flashing
Sent from my SGH-T699 using XDA Premium 4 mobile app
I accidently formatted my internal storage and system partision through TWRP recovery. Now im stuck with an unbootable Nexus 4 since there is no rom installed. How can i push a zip into my device? I can only access TWRP and Fastboot. and never really used ADB. I used a Toolkit to Root my phone (WugFresh's Toolkit) cant really use that since i cant boot my device to turn on USB Debugging. Any help?
Update: Searched several hours on xda, i cant manage to set up adb. Redownloaded Android SDK. Installed/updated adb (v). Tried multiple drivers (from official google usb drivers to univeral usb driver from Koush). Every time i open cmd and type "adb device" and long list of adb commands and other stuff appear. every time i type adb and any word infront of it, that happens. adb doesnt want to run or something. This is getting fustrating. and when i run adb.exe (from toolkit folder) it closes really quickly. only odd thing i see is under device manager my Nexus 4 is being displayed as Google Galaxy Nexus ADB Interface???
What operating system you're using?
Look here: http://forum.xda-developers.com/showthread.php?t=2010312
only this drivers worked for me
http://forum.xda-developers.com/showthread.php?t=1992345
Threadz said:
I accidently formatted my internal storage and system partision through TWRP recovery. Now im stuck with an unbootable Nexus 4 since there is no rom installed. How can i push a zip into my device? I can only access TWRP and Fastboot. and never really used ADB. I used a Toolkit to Root my phone (WugFresh's Toolkit) cant really use that since i cant boot my device to turn on USB Debugging. Any help?
Update: Searched several hours on xda, i cant manage to set up adb. Redownloaded Android SDK. Installed/updated adb (v). Tried multiple drivers (from official google usb drivers to univeral usb driver from Koush). Every time i open cmd and type "adb device" and long list of adb commands and other stuff appear. every time i type adb and any word infront of it, that happens. adb doesnt want to run or something. This is getting fustrating. and when i run adb.exe (from toolkit folder) it closes really quickly. only odd thing i see is under device manager my Nexus 4 is being displayed as Google Galaxy Nexus ADB Interface???
Click to expand...
Click to collapse
Hi the command is 'adb devices' if it's showing you the commands adb is set up correct. You don't actually need adb for this though, get your phone in fastboot mode and type 'fastboot devices' with your phone connected. If it outputs anything you're ready to flash a factory rom and fix your phone.
Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!
go to settings/storage open 3dots menu /usb computer connection. if nothing is selected that is why your phone doesn't connect. select mtp an problem solved.
if it's not that i cannot help you except suggesting to reinstall android from scratch using wug toolkit.
wasabitobiko said:
Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!
Click to expand...
Click to collapse
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?
acejavelin said:
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?
Click to expand...
Click to collapse
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..
wasabitobiko said:
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..
Click to expand...
Click to collapse
OK, so your fastboot commands are not working, that would likely be a driver issue? If you do
Code:
fastboot devices
and get a result, then keep going, if you don't, use one of the driver options in Wugfresh's toolkit, follow the instructions TO THE LETTER...
If you are just trying to get root and are unlocked, download the latest SuperSU.zip (to your phone preferably) from http://download.chainfire.eu/supersu and openrecovery-twrp-2.7.0.0-mako.img then start phone in Fastboot mode and enter:
Code:
fastboot boot openrecovery-twrp-2.7.0.0-mako.img
this will start TWRP on your device WITHOUT flashing it.
If the SuperSU zip file is on your phone, just use TWRP's Install button and navigate the file and flash it, then reboot and enjoy.
If the SuperSU zip is on your PC, then in TWRP go to Advanced, and start ADB Sideload, give it a few seconds for it to be recognized by your PC, you should be able to enter
Code:
adb devices
and get a result of SIDELOAD back, then enter:
Code:
adb sideload UPDATE-SuperSU-v1.94.zip
Or whatever the current SuperSU zip file is named. Then reboot and enjoy, your rooted!
Remember that adb commands only work in android and custom recovery NOT in fastboot mode.
Sent from my Nexus 4 using XDA Free mobile app
Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
ADB sideload is a special mode that recovery can be placed into, it only allows the "sideload" command to be used. Fastboot is different, it uses the fastboot.exe program and fastboot mode on the android device to allow a limited list of features to be used.
I don't know what you are using for a rooting guide, but basically the end result is to flash SuperSU via recovery, that is all that is really needed.
Sent from my Nexus 4 using Tapatalk
Well, basically if your boot loader is unlocked and you have a custom recovery installed just download the latest superSU zip to your SD card. Reboot into recovery, install SuperSU, reboot. Alas, you're rooted.
Sent from my Nexus 4 using XDA Free mobile app
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
If you unlocked your bootloader your drivers should be working fine. If you rebooted your phone now you'd see it works fine. Next step in rooting is to flash custom recovery. Download a custom recovery, I recommend latest version of TWRP, then flash the recovery image. 'fastboot flash recovery recovery.img' (replace recovery.img with whatever .img file you are flashing.
Once custom recovery is installed you can boot into it to flash supersu. If using TWRP it will prompt you to root when you reboot it.
Thanks.. And please don't take offense to this but re-read the thread. Ever since I used wug's rootkit to unlock the bootloader, neither my pc nor linux machine will recognize the Nexus 4. When I plug it in I get a usb error "device failed to load".. When I look at the device mgr it's listed as unknown device. Btw.. I've restarted both my phone and machine multiple times to no avail.
Sent from my Nexus 4 using XDA Free mobile app
Unknown device? Youve probably installed no or wrong fastboot drivers.
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Google tool 15 second adb xda
Sent from my Nexus 5 using XDA Free mobile app
UPDATE: It looks like the micro usb port on the phone is fried... had been charging fine until today. I'll keep you posted. Thanks for all the help. Does anyone know if this is a relatively easy fix?
Update: Fixed..
Replacing the usb port on the Nexus 4 is super easy. Thanks for the help guys. Everything's working and root has been achieved.