Just got my Nexus 7 Flo. I unlocked the bootloader, but I can't successfully install TWRP Recovery. When I try to flash it in CMD, it says "waiting for device" and I get stuck there, nothing else happens.
The tablet is in Bootloader mode when I try to flash TWRP. I tried using GooManager as well after, and even though I get the impression that it flashed successfully at first, I can't boot into it. It didn't work.
Anyone know why I'm stuck in "waiting for device" in CMD? I've been at this all night.
Did you switch the connection from Mtp to camera?
Sent from my Nexus 7 using xda app-developers app
Weird. If you unlocked the boot loader it should work.
Boot up first after you unlock, skip setup and enable developer options and then USB debugging. It should pop up and ask to allow ADB connection.
Then do "adb devices". If it returns a device, type "adb reboot bootloader". Then at the boot loader, type "fastboot devices" then "fastboot flash recovery recovery.img".
Sent from Nexus 7 FHD from XDA Premium HD
Related
Hi Guys,
I'm stuck in the endless boot logo problem, I installed google drivers, I'm able to get into recovery mode.
the device manager in win7 reports a "android ADB Device" connected.
but when I issues some of the commands in this guide http://forum.xda-developers.com/showthread.php?t=1907796 (like adb devices) it doesn't show anything...
What I've to do?? Am I doing something wrong?
thanks
Can you restore your nandroid/twrp backup? If not, fastboot back to stock and start over.
Sent from my Nexus 7 using XDA Premium HD app
peneoark said:
Can you restore your nandroid/twrp backup? If not, fastboot back to stock and start over.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Already did that with no success... .
If your device is rooted, installed a custom recovery and you're able to get into recovery mode Windows should be able identify your device without asking for RSA fingerprint or something.
Get into recovery mode and try "adb devices" from cmd after connecting your device to pc. What do you see?
Djabolic said:
If are rooted, installed a custom recovery and you're able to get into recovery mode Windows should be able identify your device without asking for RSA fingerprint or something.
Get into recovery mode and try "adb devices" from cmd after connecting your device to pc. What do you see?
Click to expand...
Click to collapse
I'm not rooted,
when rebooting with power and vol- windows recognize the device but "adb devices" gives nothing"
If I select recovery mode the nexus disappears from windows device manager
Check windows device manager to see if you can find any devices without drivers especially something about ADB or Android.
Djabolic said:
Check windows device manager to see if you can find any devices without drivers especially something about ADB or Android.
Click to expand...
Click to collapse
Nothing, when in bootloader (the one with the green robot win belly open) it gets recognized as "bootloader adb interface"; when in recovery (green robot with red exclamation mark) there is nothing in device manager
lmalossi said:
Nothing, when in bootloader (the one with the green robot win belly open) it gets recognized as "bootloader adb interface"; when in recovery (green robot with red exclamation mark) there is nothing in device manager
Click to expand...
Click to collapse
So you can issue commands over fastboot then? You can flash stock firmware images over fastboot to get everything working again.
Djabolic said:
So you can issue commands over fastboot then? You can flash stock firmware images over fastboot to get everything working again.
Click to expand...
Click to collapse
but when if fastboot the command "adb devices" return nothing...
When you're in fastboot mode you don't see your device online over adb, you can freely issue any commands from fastboot if your computer recognizes the bootloader interface.
Follow this guide to flash nexus 7 stock firmware;
http://forum.xda-developers.com/showthread.php?t=1907796
Djabolic said:
When you're in fastboot mode you don't see your device online over adb, you can freely issue any commands from fastboot if your computer recognizes the bootloader interface.
Follow this guide to flash nexus 7 stock firmware;
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
I was already following your guide....
Didn't know that if I was already in fastboot mode I could issue fastboot commands even if adb devices didn't show anything...
N00b Error!! Now the thing is clearer to me
Flashed image, and the tablet appears to be working :fingers-crossed:
Thank you very much!!
Luca
If tried reinstalling the drivers and also using the toolkit. I choose not to flash a recovery, just temporary boot so I can install stuff. I tried using fastboot to boot twrp but all I get is a black screen. Seems like sometimes the driver changes. Never had this problem on 4.2
Sent from my Nexus 7 using Tapatalk 4
biggyk said:
If tried reinstalling the drivers and also using the toolkit. I choose not to flash a recovery, just temporary boot so I can install stuff. I tried using fastboot to boot twrp but all I get is a black screen. Seems like sometimes the driver changes. Never had this problem on 4.2
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Boot your Nexus to the bootloader by first powering down the phone then simultaneously press and hold the volume down and power buttons for 2 seconds. Once in the bootloader connect the USB cable from the Nexus to your computer. Open a command prompt in the folder where you have installed fastboot, type "fastboot devices", and press enter. If you see a deviceID listed, you will be able to flash TWRP with the command "fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img" (assuming you are installing TWRP v2.6.0.0); otherwise, you will need to reinstall the Nexus drivers.
^The op wants to boot the recovery, not flash it.
Google removed the "fastboot boot" command in the new 4.3 bootloader. The new way to do this is by using the following command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
Sent using xda-developers app
Chromium_ said:
^The op wants to boot the recovery, not flash it.
Google removed the "fastboot boot" command in the new 4.3 bootloader. The new way to do this is by using the following command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
Sent using xda-developers app
Click to expand...
Click to collapse
Thank you. Worked fine!!:victory:
I downloaded minimal adb and fastboot from another thread
I had to disable "enforce driver signature" to install drivers for the device. Now I have an item in my device manager called "Samsung Android Phone" with "Android ADB interface"
I have tried command "adb devices" and it recognises my device
When I try "fastboot devices" nothing happens.
Maybe I don't know how to put the device into fastboot, but i thought all i needed to do was press and hold : power vol+ vol- and the device would reboot into fastboot.
Ultimately I am trying to unlock the bootloader and root, but the toolkit I am using get stuck as "waiting for device"
Any help would be appreciated
Tjisana said:
I downloaded minimal adb and fastboot from another thread
I had to disable "enforce driver signature" to install drivers for the device. Now I have an item in my device manager called "Samsung Android Phone" with "Android ADB interface"
I have tried command "adb devices" and it recognises my device
When I try "fastboot devices" nothing happens.
Maybe I don't know how to put the device into fastboot, but i thought all i needed to do was press and hold : power vol+ vol- and the device would reboot into fastboot.
Ultimately I am trying to unlock the bootloader and root, but the toolkit I am using get stuck as "waiting for device"
Any help would be appreciated
Click to expand...
Click to collapse
You probably did this but just to check:
1. Start cmd.
2. Navigate to your adb/fastboot folder.
3. Check if USB debugging is enabled.
4. Type "adb reboot bootloader" in the cmd window.
5. Type "fastboot devices".
6. Type "fastboot oem unlock" (THIS WILL WIPE ALL YOUR DATA, data+internal storage).
7. Type "fastboot flash recovery /path/to/recovery.img".
8. Navigate to recovery option in the bootloader. And boot into recovery by pressing the power button.
9. Flash the latest supersu and wipe cache and dalvik cache.
10. Reboot.
11. Profit.
If it doesnt work at the step "adb reboot booloader" or "fastboot devices" you prabably are having a driver issue.
Sent from my Galaxy Nexus using XDA Premium HD app
please help with fastboot/bootloader mode
mrgnex said:
You probably did this but just to check:
1. Start cmd.
2. Navigate to your adb/fastboot folder.
3. Check if USB debugging is enabled.
4. Type "adb reboot bootloader" in the cmd window.
5. Type "fastboot devices".
6. Type "fastboot oem unlock" (THIS WILL WIPE ALL YOUR DATA, data+internal storage).
7. Type "fastboot flash recovery /path/to/recovery.img".
8. Navigate to recovery option in the bootloader. And boot into recovery by pressing the power button.
9. Flash the latest supersu and wipe cache and dalvik cache.
10. Reboot.
Click to expand...
Click to collapse
I tried this, but all my device does at step 4 is a normal reboot. I am able to fully use adb without any issues...
My device is a Titan Allwinner A20 Softwiner sun7i Tablet...
Does this mean that it does not have a fastboot/bootloader mode?
Thanks for your help...
I only know this for the Nexus 10. Maybe look up the thread for your device and see whats there. Or use google
Sent from my Galaxy Nexus using xda app-developers app
silentarts said:
I tried this, but all my device does at step 4 is a normal reboot. I am able to fully use adb without any issues...
My device is a Titan Allwinner A20 Softwiner sun7i Tablet...
Does this mean that it does not have a fastboot/bootloader mode?
Thanks for your help...
Click to expand...
Click to collapse
Hi,
This forum is dedicated to Nexus 10 only, I don't believe that we can be of wide help for you .
The fastboot commands only work for Nexus devices, so as you don't own one and can't even get boot loader mode, then I'm sorry but here is not the place that you may seek advice.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1
True this isn't the place for the question, and the answer is you probably do not have a bootloader that is capable of interacting with the fastboot binary.
However fastboot is not only for nexus devices, virtually all HTC android devices are able to use fastboot, same with many Motorola, Sony and lg devices.
But again, more than likely your device will not work with fastboot
Best of luck!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hi,
I've been trying to root my Nexus 4 for almost 8 hours now :crying:
I'm stuck on the flash recovery. When I open command prompt and type 'fastboot flash recovery recovery-clockwork-6.0.4.7-mako' it says 'waiting for device' forever. I've used different adb usb drivers such as Koush's universal driver and also Naked usb driver but it makes no difference whatsoever. How do I get cwm to work on my phone.
Thank you.
You have unlocked your boot loader, right?
Sent from my Nexus 4 using XDA Free mobile app
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.