Hi there.
Boot into recovery.
Hold down volume up and power to open the menu.
Factory reset and clear cache.
Reboot
El Daddy said:
Boot into recovery.
Hold down volume up and power to open the menu.
Click to expand...
Click to collapse
This was not working for me for some reason (probably user error). I plugged my phone into my computer, opened a command prompt to the Android SDK and typed:
Code:
adb reboot recovery
miguelmondo said:
This was not working for me for some reason (probably user error). I plugged my phone into my computer, opened a command prompt to the Android SDK and typed:
Code:
adb reboot recovery
Click to expand...
Click to collapse
you need ADB environment set up as well as drivers (windows)
"cd <path to file>"
Related
Hi
I just wiped my phone using the HD revolution script to install, I had a 'bad file' error so rebooted... my phone's volume down button doesnt work so now I cannot get into Hboot or Recovery, is there any other way?
Using adb - if it works.
Plug your phone in to your PC, switch on then run this command.
Code:
adb reboot recovery
Ah of course! Thanks, forgot about adb
Hello yesterday i wiped everything on my phone by a mistake.Then i plugged it to my pc but it didnt recognized it,even when my phone is at recovery screen or bootloader screen.What to do? İ decided to flash roms by usng the pc.
NOte:İt gives a sound when i connect it but then nothing happens.
Is it recognized by adb while in recovery?
chromium96 said:
Is it recognized by adb while in recovery?
Click to expand...
Click to collapse
How to undertstand if it does?
korkuadam said:
How to undertstand if it does?
Click to expand...
Click to collapse
-setup adb
-boot phone into recovery and plug it into your computer
-open command prompt and type:
Code:
adb devices
-if your phones serial number shows up, its recognized. Then you can push a rom back onto your phone and flash it using:
Code:
adb push \path\to\rom.zip /sdcard
chromium96 said:
-setup adb
-boot phone into recovery and plug it into your computer
-open command prompt and type:
Code:
adb devices
-if your phones serial number shows up, its recognized. Then you can push a rom back onto your phone and flash it using:
Code:
adb push \path\to\rom.zip /sdcard
Click to expand...
Click to collapse
This is not working.Can i do something with toolkit?
korkuadam said:
This is not working.Can i do something with toolkit?
Click to expand...
Click to collapse
İ just fixed it somehow,thanks
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Anything?
oliverm91 said:
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Click to expand...
Click to collapse
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
taodan said:
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
Click to expand...
Click to collapse
You mean turn off the phone and turn on to recovery? Because I've already done that as I mentioned in the first post.
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
audit13 said:
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
Click to expand...
Click to collapse
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
oliverm91 said:
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
Click to expand...
Click to collapse
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
audit13 said:
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
Click to expand...
Click to collapse
I am, Windows 8. But this problems happens even after rebooting my PC.
oliverm91 said:
I am, Windows 8. But this problems happens even after rebooting my PC.
Click to expand...
Click to collapse
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
audit13 said:
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
Click to expand...
Click to collapse
I use PowerShell as admin
No clue?
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
karthi89 said:
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Did this, but ADB still doesn't recognize my phone while in recovery.
jd1639 said:
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, but ADB won't recognize my device when it's on CWM (CWM v6.0.4.7)
I realised that in "device manager" of Windows a yellow triangle appears on "Other devices" -> Nexus 4 (when im in Recovery)
and when I normally boot my phone it appears normally under "Android device" -> android composite adb interface
No clue?
Hi folks!
I wanted to install Cyanogenmod as described in Cyanogenmod Wiki.
So I downloaded ioroot, rootet my phone via adb and used AutoRec to install TWRP (version 2.7.0.0).
Then I rebooted into recovery mode, wiped EVERYTHING and wanted to sideload the CM image via adb.
So in TWRP I selected Advanced/ADB Sideload and swipe to start sideload but all that happens is the notification "Starting ADB sideload feature...".
Consequently the phone is not recognized by adb on my PC.
What can I do to make the sideload feature work?
BTW: TWRP tells me that my devices doesnt appear to be rooted when I want to leave TWRP (reboot). Moreover when i want to enter TWRP again (by pressing POWER + VOLUE DOWN) I first get a screen that asks me if want to do a factory hard reset! Only if I agree (by pressing the power key) I get into TWRP.
Contrary when I enter the Download Mode (VOLUME UP when when connecting the powered off phone to the USB port) I am told that the phone is rooted. Moreover the LG Mobile Support Tool is able to detect the device and tells me that the installed software is up to date.
Thx!!
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Make sure you're in the proper folder in prompt and the device name will be sideload if you do, adb devices.
Sent from my LG-D800 using Tapatalk
meangreenie said:
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Click to expand...
Click to collapse
Thanks but this doesnt help either. Same error message "error: device not found"
boot into twrp, don't start sideload
try adb devices, if you get not find you need to change the usb drivers
when you have it working, type, adb push /sdcard/ rom.zip .. check the syntax on that command, but i think that's right from memory
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
It sounds like you may not have the latest drivers for the Android SDK or ADB toolkit.
RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
When you are in bootloader, you can use fastboot commands.
RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
JustPlayingHard said:
When you are in bootloader, you can use fastboot commands.
Click to expand...
Click to collapse
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
RonaldusMagnus said:
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
Click to expand...
Click to collapse
It's not adb fastboot.. It's just fastboot.
teh roxxorz said:
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
Click to expand...
Click to collapse
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
RonaldusMagnus said:
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
JustPlayingHard said:
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
Click to expand...
Click to collapse
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
No worries, it's probably me that's being dense.
That should work fine
RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
or plug your phone in (while its booted normally, into its OS)
type: adb reboot bootloader
once phone reboots to bootloader, type: fastboot devices
He must have came from a HTC bc he's looking for the option Fastboot in Bootloader.
Sent from my Nexus 6P using Tapatalk
Thanks for your help everyone. I'm back up and running now. My problems stemmed from a misunderstanding that once in the bootloader I'm already able to execute fastboot commands and didn't need to select a fastboot option from the bootloader. And I had a misunderstood how to execute the fastboot commands from the command prompt.
Many thanks to everyone setting me straight!