My Nexus 5 (bone stock) shows up properly as a device in ADB when in regular ON mode. As soon as I reboot in recovery mode (abd reboot recovery) it shows "error device not found" even after I choose the option to update via sideload in recovery mode.
ADB can see it when ON, but can't see it in recovery.
I'm obviously trying to sideload 4.4.1
Thanks!
When in recovery, you’ll see an android laying down. Press power then immediately press volume up and release. The menu will appear. Select “apply update from adb”
Then you can sideload your zip file.
Or
Reinstall naked USB adb driver...
Sent from my Nexus 5 using Tapatalk
Bombn said:
My Nexus 5 (bone stock) shows up properly as a device in ADB when in regular ON mode. As soon as I reboot in recovery mode (abd reboot recovery) it shows "error device not found" even after I choose the option to update via sideload in recovery mode.
ADB can see it when ON, but can't see it in recovery.
I'm obviously trying to sideload 4.4.1
Thanks!
Click to expand...
Click to collapse
I had this issue. Resolution was to manually install the ADB driver.
lpganesh said:
When in recovery, you’ll see an android laying down. Press power then immediately press volume up and release. The menu will appear. Select “apply update from adb”
Then you can sideload your zip file.
Or
Reinstall naked USB adb driver...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The menu will appear. Select “apply update from adb”
Click to expand...
Click to collapse
That's exactly when ADB no longer see my Nexus.
Resolved.
Reinstalled the Google USB Driver via Device Manager and all everything works.
Thanks for the help!
Related
Anyway to get into stock recovery without working volume buttons?
tonyb81 said:
Anyway to get into stock recovery without working volume buttons?
Click to expand...
Click to collapse
Can you boot the phone? If so, use Rom Manager to boot into recovery from the main options menu.
trev869 said:
Can you boot the phone? If so, use Rom Manager to boot into recovery from the main options menu.
Click to expand...
Click to collapse
not sure if this will work as he says he's on stock. unless it's stock rooted by attn1 that is.
otherwise, if you have the android sdk and/or adb installed, you can just pass open a command prompt in the folder with adb and connect your phone over usb (make sure debugging mode is enabled via settings --> apps --> development). then in the command prompt, simply type adb reboot recovery.
hope tihs helps
Even when you use ROM manager to boot into recovery how are you going to use recovery without your volume buttons working?
Sent from my Desire HD using XDA App
As long as the power (enter) button works, you ate okay. The menu softkey will scroll down and the return will take you back one menu.
Edit: are okay
Sent from my ClearDroid Inspire 4G using XDA App
Tried that and all you get is the rom manager picture in the middle of the screen.
What version has those options in it ?
Have found a program in Desire HD development.
You can change your recovery.
http://forum.xda-developers.com/showthread.php?t=1161710
Volume buttons not needed....
tonyb81 said:
Anyway to get into stock recovery without working volume buttons?
Click to expand...
Click to collapse
Yes with adb command line, in the PC typing "adb reboot recovery", this method working very fine too if your phone stuck in boot loop and the volume keys not working, for this problem the steps are:
1. remove battery
2. insert battery and put the cover
3. conect the usb cable to pc and phone
4. waiting 10 seconds and with adb command line in the PC typing "adb reboot recovery" and the phone restart in recovery mode and here you navigate with the touch buttons home= up menu=down search=enter
Regards
ok i have a tf300t flashed a stock asus (latest rom) it rebooted into asus now when i try and go into rck it just gets to little man falls down. I have no usb icon to choose to let me fastboot the twrp/cwm recovery and i wanted to flash the rom android blue. What can i do?
yoshaben said:
ok i have a tf300t flashed a stock asus (latest rom) it rebooted into asus now when i try and go into rck it just gets to little man falls down. I have no usb icon to choose to let me fastboot the twrp/cwm recovery and i wanted to flash the rom android blue. What can i do?
Click to expand...
Click to collapse
The tablet is already in fastboot when you see RCK and the other options. If youlook above the options, you'll see 'starting fastboot usb download protocol' So you dont need to select the usb icon to enter fastboot.
Ok, thanks.... However one other thing I noticed there is also a message that says key driver not found booting Os. Is that important?
Sent from my SCH-I605 using xda premium
yoshaben said:
Ok, thanks.... However one other thing I noticed there is also a message that says key driver not found booting Os. Is that important?
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
I read about it that it's not important. i also see that on my tablet too. i've flash my tablet more that 20 times without any problems. SO dont worry about it.
crazynitro said:
The tablet is already in fastboot when you see RCK and the other options. If youlook above the options, you'll see 'starting fastboot usb download protocol' So you dont need to select the usb icon to enter fastboot.
Click to expand...
Click to collapse
I have the same problem on my tablet; the point is:
if it is already in fastboot mode, how can i install clockworck mode recovery or install a new rom?
Beside, I've noticed that when i plug it into the pc, open a terminal (in ubuntu) and type "fastboot device", the pc does not recognize it and just displays on the terminal this message "<waiting for device>;
what does it mean??
se242196sa said:
I have the same problem on my tablet; the point is:
if it is already in fastboot mode, how can i install clockworck mode recovery or install a new rom?
Beside, I've noticed that when i plug it into the pc, open a terminal (in ubuntu) and type "fastboot device", the pc does not recognize it and just displays on the terminal this message "<waiting for device>;
what does it mean??
Click to expand...
Click to collapse
You need to install the Naked Universal Drivers to use ADB and Fastboot. Look for the device in device manager as well.
All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?
spooky71 said:
All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?
Click to expand...
Click to collapse
What happened?
This is a common result if you flash a non-4.2 twrp on a 4.2 bootloader, which will cause a fastboot flash brick.
You will need adb drivers installed on pc, then while in recovery connect your tab to pc, open a command prompt and cd to you android-sdk/platform-tools folder and type
Code:
adb devices
if adb is setup correctly you will get a response with your devices s/n. If this is ok then type
Code:
adb reboot-bootloader
which will reboot your tab to the bootloader screen.
The problem is that whenever I boot up, all i get is the TWRP menu, not letting the pc see the pad. On device manager I get Transformer under other devices. Ive downloaded the drivers, but its not installing them. When I run adb reboot-bootloader, I get device not found.
Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later
pjc21 said:
Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later
Click to expand...
Click to collapse
Still nothing. Whats killing me is that it cant detect different sd cards.
So I am having trouble with adb it seems like. When in fastboot and using adb I type in "fastboot devices" and my phone shows up and when typing "adb version" the version number shows up too. But when I go into recovery and try to sideload the 4.4.1 update to my phone I get a message that my device couldn't be found.
Any suggestions on what this could be? I tried using a toolkit too and I get the same message showing up too.
Did you press vol up + power button in stock recovery and select sideload from adb? That right there should enable adb mode in recovery.
peachpuff said:
Did you press vol up + power button in stock recovery and select sideload from adb? That right there should enable adb mode in recovery.
Click to expand...
Click to collapse
Yes I did. After I do that I type "adb sideload <file name>" and then that is when i get the message that the device cant be found.
peachpuff said:
Did you press vol up + power button in stock recovery and select sideload from adb? That right there should enable adb mode in recovery.
Click to expand...
Click to collapse
Install Koush's Universal ADB Drivers.
Had the same problem. Google drivers not working in recovery sideload mode.
Aerowinder said:
Install Koush's Universal ADB Drivers.
Had the same problem. Google drivers not working in recovery sideload mode.
Click to expand...
Click to collapse
Will do. I shall report back if it works or not.
Aerowinder said:
Install Koush's Universal ADB Drivers.
Had the same problem. Google drivers not working in recovery sideload mode.
Click to expand...
Click to collapse
Worked like a charm thanks!
Hello everyone,
I have a Nexus 5 Stock without root with Android 5.0.1.
When I get the OTA Android 5.1, when it is unloaded, i restart the phone for installation but this crashes and shows the android with the belly open and the red triangle (and the word error in the robot).
This problem happened to me on other occasions, is the only solution that I was able to find was to manually flash the ROM. But I'd like you would install the ROM normally using 'OTA.
I hope you can solve my problem, thank you in advance
thejackal94 said:
Hello everyone,
I have a Nexus 5 Stock without root with Android 5.0.1.
When I get the OTA Android 5.1, when it is unloaded, i restart the phone for installation but this crashes and shows the android with the belly open and the red triangle (and the word error in the robot).
This problem happened to me on other occasions, is the only solution that I was able to find was to manually flash the ROM. But I'd like you would install the ROM normally using 'OTA.
I hope you can solve my problem, thank you in advance
Click to expand...
Click to collapse
Try to install ota again, and when you get that error screen press and hold power key then press and release volume_up key then you should some sort of text which will tell what caused the error and then you can release the power key.
What error you see?
thejackal94 said:
Hello everyone,
I have a Nexus 5 Stock without root with Android 5.0.1.
When I get the OTA Android 5.1, when it is unloaded, i restart the phone for installation but this crashes and shows the android with the belly open and the red triangle (and the word error in the robot).
This problem happened to me on other occasions, is the only solution that I was able to find was to manually flash the ROM. But I'd like you would install the ROM normally using 'OTA.
I hope you can solve my problem, thank you in advance
Click to expand...
Click to collapse
It doesn't sound like you do, but in the off chance that you have TWRP or ClockworkMod installed, these will cause an OTA to fail installing.
bitdomo said:
Try to install ota again, and when you get that error screen press and hold power key then press and release volume_up key then you should some sort of text which will tell what caused the error and then you can release the power key.
What error you see?
Click to expand...
Click to collapse
Ok i have tried, this is the message that appears:
E:Error in /cache/update.zip
(status 7)
Installation aborted.
Mounted /system
Visa Declined said:
It doesn't sound like you do, but in the off chance that you have TWRP or ClockworkMod installed, these will cause an OTA to fail installing.
Click to expand...
Click to collapse
My nexus is completely stock, I never installed TWRP, ClockworkMod.
thejackal94 said:
Ok i have tried, this is the message that appears:
E:Error in /cache/update.zip
(status 7)
Installation aborted.
Mounted /system
Click to expand...
Click to collapse
Maybe you have a bad download.
Wipe cache in the stock recovery. This will delete the downloaded OTA and will force the phone to download it again.
bitdomo said:
Maybe you have a bad download.
Wipe cache in the stock recovery. This will delete the downloaded OTA and will force the phone to download it again.
Click to expand...
Click to collapse
I tried to do the Wipe cache, but always same error (status 7)
thejackal94 said:
I tried to do the Wipe cache, but always same error (status 7)
Click to expand...
Click to collapse
Download google usb drivers
Extract it
Download ota
Rename ota to update.zip
Download 15 secs adb installer
Install it
Connect phone in bootloader mode.
Install drivers for bootloader mode in device manager using the the extracted google usb drivers.
Go to recovery mode.
Enable the recovery menu
Select apply update from ADB
In device manager install the drivers for the new Unknown (or nexus 5) device. You have to select the Let me pick from list of device drivers on my computer then select ADB Interface and then select anything which has ADB in its name.
Open CMD
cd to the directory which contains the update.zip
Use this command: adb sideload update.zip
If ADB sideload timed out on the phone then select apply update from ADB again
bitdomo said:
Download google usb drivers
Extract it
Download ota
Rename ota to update.zip
Download 15 secs adb installer
Install it
Connect phone in bootloader mode.
Install drivers for bootloader mode in device manager using the the extracted google usb drivers.
Go to recovery mode.
Enable the recovery menu
Select apply update from ADB
In device manager install the drivers for the new Unknown (or nexus 5) device. You have to select the Let me pick from list of device drivers on my computer then select ADB Interface and then select anything which has ADB in its name.
Open CMD
cd to the directory which contains the update.zip
Use this command: adb sideload update.zip
If ADB sideload timed out on the phone then select apply update from ADB again
Click to expand...
Click to collapse
I followed step by step the guide but again appears Status 7! I don't know what to do
thejackal94 said:
I followed step by step the guide but again appears Status 7! I don't know what to do
Click to expand...
Click to collapse
The next step would be doing a factory reset. If that not works then unlocking bootloader and flashing the latest stock rom in fastboot.