Related
Using a linux PC I was attempting to unlock my bootloader following the directions at http://www.geek.com/articles/mobile/how-to-unlock-and-root-the-nexus-7-2012081/.
I can execute adb reboot bootloader just fine.... however when I issue the fastboot oem unlock command nothing happens on the tablet, and I see "< waiting for device >" in the terminal window. If I CTRL-C to break out and then do a 'adb devices' I see that there are no devices listed.
The Nexus 7 is a stock 16gb, C70 running 4.1.2/JZO54K.
Probably unrelated - I noticed in the last couple of weeks that the tablet has become slugging/laggy. Available space was at about 2gb. I removed some storage hungry games and got available space back up to about 5.5 gb.... but it's still laggy and touch detection barfs on occasion.
Any help/advice would be greatly appreciated.
Being on Linux make sure hat your fastboot command either has suid-bit set and owner is set to root or you need to run the command by sudo:
sudo fastboot devices
For adb there should be no problems, but adb is not working if your device is in fastboot mode.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Being on Linux make sure hat your fastboot command either has suid-bit set and owner is set to root or you need to run the command by sudo:
sudo fastboot devices
For adb there should be no problems, but adb is not working if your device is in fastboot mode.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Uggg.... Years of using Odin has made me stupid and lazy.... sudo did the trick. Thanks!!
I tried updating my nexus 7 to 4.2.1 and i thought everything went okay but now adb doesn't recognize my device in fastboot and i can't boot up my nexus 7 because everything got wiped on my sd card. I can boot into recovery but i can't mount my sd card either. It tells me there is an error. Apparently there is no OS installed. Any help is welcomed.
YoungCorruptionV2.0 said:
I tried updating my nexus 7 to 4.2.1 and i thought everything went okay but now adb doesn't recognize my device in fastboot and i can't boot up my nexus 7 because everything got wiped on my sd card. I can boot into recovery but i can't mount my sd card either. It tells me there is an error. Apparently there is no OS installed. Any help is welcomed.
Click to expand...
Click to collapse
You can boot into the bootloader, and use fastboot commands to reflash the stock Android 4.2.1 OS.
RMarkwald said:
You can boot into the bootloader, and use fastboot commands to reflash the stock Android 4.2.1 OS.
Click to expand...
Click to collapse
Fast boot commands don't work because adb can't recognized my device while in fastboot. I tried "adb devices" and no devices were listed
Sent from my EVO using Tapatalk 2
YoungCorruptionV2.0 said:
Fast boot commands don't work because adb can't recognized my device while in fastboot. I tried "adb devices" and no devices were listed
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
You can't use adb in fast boot . Reboot to the boot loader. If you type 'fastboot devices' in fast boot your phone will show
Sent from my One X using xda app-developers app
I had the same problem.
What version of adb.exe Ade you using?
The latest is dated sometime in November this year. If it's earlier than that, download the SDK from android development site and use newer version of adb.exe
That should fix the issue...
Sent from my Nexus 7 using xda premium
From bootloader use fastboot commands, from recovery use adb commands.
You can't do adb commands in fastboot mode. To do adb commands you either need to be in Android or in a recovery.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
If you have twrp recovery installed you can boot to recovery and use adb sideload.
So just download a rom on your computer boot to recovery and sideload the rom to your device and then install it.
Not sure if this can be done with cwm though
Sent from my Nexus 7 using Tapatalk 2
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.
Hi everybody, 2 months ago I tried to encrypt my nexus using the security settings. When my n4 rebooted the touch stopped working. I couldn't use the recovery becouse the data partition was encrypted, so I used this tutorial (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060) to reset my phone. Now windows (neither ubuntu) do not recognize the n4. I tried to follow any kind of guide or tutorial i found but uselessly. I'm desperate, the recovery doesn't work, if i try ,it stop on android logo saying "no command". Entering in windows device manager (after i formatted my pc) the nexus is seen as "full jellybean on mako", i tested this driver (http://forum.xda-developers.com/nexus-4/help/phone-detected-jellybean-mako-install-t2411201) but the situation has not changed. I hope someone can help me.
Does your phone boot?
BTW, if you need only driver download from this thread: http://forum.xda-developers.com/nexus-4/general/drivers-nexus-4-driver-windows-t1992345
PsyGik said:
Does your phone boot?
BTW, if you need only driver download from this thread: http://forum.xda-developers.com/nexus-4/general/drivers-nexus-4-driver-windows-t1992345
Click to expand...
Click to collapse
It works perfectly, but I can't copy files on or change rom (now is running stock android 4.2)
werba59 said:
It works perfectly, but I can't copy files on or change rom (now is running stock android 4.2)
Click to expand...
Click to collapse
Boot into bootloader and flash stock rom from here :https://developers.google.com/android/nexus/images
BTW, did you enable developer options?
Sorry, I misread your answer. "It works perfectly" means that i can use it to call or whatever. Using the key combo (vol up+vol dw+power) it doesn't boot in download mode. I think it isn't a driver problem, something in my n4 went wrong. It boot only in fastboot mode and the recovery doesn't work.
werba59 said:
Sorry, I misread your answer. "It works perfectly" means that i can use it to call or whatever. Using the key combo (vol up+vol dw+power) it doesn't boot in download mode. I think it isn't a driver problem, something in my n4 went wrong. It boot only in fastboot mode and the recovery doesn't work.
Click to expand...
Click to collapse
If it boots into Fast-boot/boot-loader then problem is solved right. Does your PC recognise your phone when it boots into fastboot mode? If yes then open up terminal and type:
Code:
fastboot oem unlock
Then open the downloaded image from here https://developers.google.com/android/nexus/images and Execute the flash-all script. This script installs the necessary bootloader, firmware,and system. Wait for a couple of minutes and then phone will reboot itself. After phone boots enable developer options in the phone and enable USB debugging.
If you are still not able to mount the storage in Ubuntu, you can install the mtpfs tool for Ubuntu.
Code:
sudo apt-get install mtp-tools mtpfs
sudo gedit /etc/udev/rules.d/51-android.rules
and in the 51-android.rules write the following:
Code:
#LG – Nexus 4
SUBSYSTEM==”usb”, ATTR{idVendor}==”1004?, MODE=”0666?
Then do:
Code:
sudo chmod +x /etc/udev/rules.d/51-android.rules
sudo service udev restart
sudo mkdir /media/nexus4
chmod 755 /media/nexus4
sudo mtpfs -o allow_other /media/nexus4
This should get it working. This thread tells everything in much more detail if you still didn't get it to work.
http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
PsyGik said:
If it boots into Fast-boot/boot-loader then problem is solved right. Does your PC recognise your phone when it boots into fastboot mode? If yes then open up terminal and type:
Code:
fastboot oem unlock
My PC do not recognise my phone when it boots into fastboot mode, that's the problem, any pc and any kind of so i tested do not recognise my n4.
Click to expand...
Click to collapse
werba59 said:
PsyGik said:
If it boots into Fast-boot/boot-loader then problem is solved right. Does your PC recognise your phone when it boots into fastboot mode? If yes then open up terminal and type:
Code:
fastboot oem unlock
My PC do not recognise my phone when it boots into fastboot mode, that's the problem, any pc and any kind of so i tested do not recognise my n4.
Click to expand...
Click to collapse
If no pc will recognize it it's probably your pc port on the device. Have you tried different cables too? It's pretty easy to replace or have replaced.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Seems like something going wrong with drivers, open the device manager on windows, plug in your phone (in fastboot) and uninstall the driver. Then use this http://www.koushikdutta.com/post/universal-adb-driver
Dunno what that full JB driver is about but it doesn't seem right.
You might have to repeat this process when phone is booted normally too if it won't connect via MTP
Hi, just get here after look in several forums.
my laptop can't recognize my n4, also tried in other two computers. i already updated the drivers, used a toolkit. what should i do next? the phone works good, just can't connect it to any pc. "USB device is not recognized"
as i said, already updated the drivers.
Anything else i can do?
Hi,
I follow this Tutorial to root my Moto g6 Plus.
I could unlock my bootloader, but i cant boot twrp-3.2.3-42-evert.img.
When I try "fastboot boot twrp-3.2.3-42-evert.img" , I get
Code:
Sending 'boot.img' (31100 KB) OKAY [ 0.878s]
Booting FAILED (remote: '')
fastboot: error: Command failed
I am using Windows 10, 64 BIt.
I use cmd in WIndows Terminal.
I used the ADB and Fastboot Installer for Windows to install adb and fastboot.
Can someone help me please?
autowert66
I ran into this when I was looking to replace HavocOS 2.7 on Moto G6 plus and fix a few issues after a failed update using the tutorial here.
Did you disable lockscreen?
Even though this did not fix this issue for me it is well documented that it can have an effect on adb/fastboot use.
Did you see the notice on your phone to trust the connecting device?
I missed it the 1st time I tried using adb and it didn't prompt me again after that.
Have you tried adb/fastboot on another (older) machine .
I could NOT use fastboot on my Ryzen 7 linux machine w/ native USB 3.0 (or the 2.0 ports) and was getting the same type of results as you, although "adb reboot bootloader" worked fine.
I ended up usng an old HP Celeron laptop booting FWUL (bootable linux dev enviroment, Search for it here on XDA) on a USB stick which recognized the phone no problem and allowed me to "fastboot boot twrp-3.2.3-42-evert.img" (although I did copy/rename it to boot.img to save typing time), use it to backup to sdcard, format data, and install "new" ROM.
WARNING:
The tutorial I used above also has directions for installing (Open)Gapps and Magisk which, even after 2X attempts had lawnchair crashing continuously.
The 3rd time I just installed the ROM and Magisk and it's working fine.
This will be a test to use the phone w/o any g00gle at all (g00gle is EVIL).
HTH!
i know this is not a solution, but this kind of issue is solve by using a different pc.
i got the same "bug" with my current pc (ryzen 5 + motherboard asus b450m-a)
but my wife's pc (intel+asus mb) have working fastboot commands like usual
also try (if you can) using a usb hub... in my case it did not work but i read some users do.
àutowert66 said:
Hi,
I follow this Tutorial to root my Moto g6 Plus.
I could unlock my bootloader, but i cant boot twrp-3.2.3-42-evert.img.
When I try "fastboot boot twrp-3.2.3-42-evert.img" , I get
Code:
Sending 'boot.img' (31100 KB) OKAY [ 0.878s]
Booting FAILED (remote: '')
fastboot: error: Command failed
I am using Windows 10, 64 BIt.
I use cmd in WIndows Terminal.
I used the ADB and Fastboot Installer for Windows to install adb and fastboot.
Can someone help me please?
autowert66
Click to expand...
Click to collapse
What is your pc specs? Are you using a Ryzen CPU? Idk why but this phone won´t pick fastboot commands with a Ryzen CPU. Get any Intel and you will be able perform the booting.
d_g_m_2000 said:
i know this is not a solution, but this kind of issue is solve by using a different pc.
i got the same "bug" with my current pc (ryzen 5 + motherboard asus b450m-a)
but my wife's pc (intel+asus mb) have working fastboot commands like usual
also try (if you can) using a usb hub... in my case it did not work but i read some users do.
Click to expand...
Click to collapse
You are tottaly right. It is a bug or a known issue but this pc won´t pick fastboot commands from Ryzen pc.
àutowert66 said:
Hi,
I follow this Tutorial to root my Moto g6 Plus.
I could unlock my bootloader, but i cant boot twrp-3.2.3-42-evert.img.
When I try "fastboot boot twrp-3.2.3-42-evert.img" , I get
Code:
Sending 'boot.img' (31100 KB) OKAY [ 0.878s]
Booting FAILED (remote: '')
fastboot: error: Command failed
I am using Windows 10, 64 BIt.
I use cmd in WIndows Terminal.
I used the ADB and Fastboot Installer for Windows to install adb and fastboot.
Can someone help me please?
autowert66
Click to expand...
Click to collapse
In my case fastboot got stuck at sending boot.img forever until I removed the cable and then I got a similar or the same error. I solved this problem by disconnecting the cable, then typing in the command and pressing enter and after that putting in the cable again. Then it sent successfully and booted. I hope this helped someone.
If you have ryzen get a usb hub. If you have intel, run the command and wat for the "<wating for device>" and plug in the phone there. Also use usb 2.0
Diego_992 said:
What is your pc specs? Are you using a Ryzen CPU? Idk why but this phone won´t pick fastboot commands with a Ryzen CPU. Get any Intel and you will be able perform the booting.
You are tottaly right. It is a bug or a known issue but this pc won´t pick fastboot commands from Ryzen pc.
Click to expand...
Click to collapse
this is exactly why i didnt chose ryzen for my latest build. i know ryzen is dominating rn, and i really wanted an amd cpu, but need fastboot commands to work since im a regular modder on my oneplus 6T and moto phones