Pretty much I wiped everything from my system and did a reboot. I am unable to boot up recovery mode. Using the "adb devices" command doesn't detect the phone.
If you can fastboot, just flash Fastboot rom. Check out the guide section or search fastboot rom
Gr8man001 said:
If you can fastboot, just flash Fastboot rom. Check out the guide section or search fastboot rom
Click to expand...
Click to collapse
Thanks i was able to fix the problem
Related
Basically, my xoom has been rooted and currently I have CynogenMod9 RC0 Wingray currently installed.
I wanted to install a new rom but I couldn't do this using CWM Recovery as the SD Card doesn't Mount. Upon doing some reading I found I need to install the Rogue (or EOS) Recovery image. This is where my problems begin as I can connect to the device when the xoom is fully booted in the CM9 and connected via debugging mode(running adb devices returns a sequence of numbers ).
But then when I reboot into the bootloader it gets stuck on "Starting Fastboot protocol support." and i can't connect via adb!!!
I believe this started happening after I unlocked the bootloader but i can't be 100% sure (fastboot oemunlock)
Please help!!!
When it is on fastboot mode you can only use fastboot commands (fastboot flash recovery recovery.img) that is how you would install the recovery image from rogue or EOS or TWRP, whichever you choose.
Or to make it easier, you can boot your tablet, install GOO Manager. When you open the GOO manager, tap the setting in the top right corner and choose Install Open Recovery script and let it install TWRP. Then boot to recovery.
Sent from my SGH-I747 using xda premium
d3athsd00r said:
When it is on fastboot mode you can only use fastboot commands (fastboot flash recovery recovery.img) that is how you would install the recovery image from rogue or EOS or TWRP, whichever you choose.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
But it never gets into fastboot mode now.
miahmad said:
But it never gets into fastboot mode now.
Click to expand...
Click to collapse
You specifically said it says starting fastboot protocol. That's as far as it goes. You then issue fastboot commands, not adb commands
Sent from my SGH-I747 using xda premium
Moved to Q & A.
Sent from my Galaxy Nexus using Tapatalk 2
d3athsd00r said:
You specifically said it says starting fastboot protocol. That's as far as it goes. You then issue fastboot commands, not adb commands
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Ohh ok, makes sense. I will give it a try later when i'm home. Is there a Fastboot command i can use to check the device is connected??
miahmad said:
Ohh ok, makes sense. I will give it a try later when i'm home. Is there a Fastboot command i can use to check the device is connected??
Click to expand...
Click to collapse
fastboot devices
miahmad said:
Basically, my xoom has been rooted and currently I have CynogenMod9 RC0 Wingray currently installed.
I wanted to install a new rom but I couldn't do this using CWM Recovery as the SD Card doesn't Mount. Upon doing some reading I found I need to install the Rogue (or EOS) Recovery image. This is where my problems begin as I can connect to the device when the xoom is fully booted in the CM9 and connected via debugging mode(running adb devices returns a sequence of numbers ).
But then when I reboot into the bootloader it gets stuck on "Starting Fastboot protocol support." and i can't connect via adb!!!
I believe this started happening after I unlocked the bootloader but i can't be 100% sure (fastboot oemunlock)
Please help!!!
Click to expand...
Click to collapse
These are what i use from day 1
INSTRUCTIONS TO FLASH & RE-LOCK YOUR MOTOROLA XOOM:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
---------------------------------------------------------------------------------------------------------------------
Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6-softkeys.img
fastboot flash recoverytwrp-2.2.1-stingray_cdma.img
fastboot reboot
adb reboot recovery
-------------------------------------------------------------------------------------------------------------------------
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot
3. Flash recovery
Code:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Hello,
I have followed a tutorial for solving the problem of "Fastboot mode started
udc_start()" from this thread http://forum.xda-developers.com/showthread.php?t=2131247 and something was go wrong.
I have done this steps in the sdk platform tools folder:
1- fastboot erase recovery
2- fastboot flash recovery recovery.img ( here i've got an error)
3- fastboot reboot
Everyting was ok until I have tried to write the .img file on the phone. I've got an error that I don't have enough space. I think I have deleted the recovery file and now it's stuck, because it's not booting. The 4 leds from the bottom it's flashing continuously and the screen remains to the LG logo. I have tried to connect the phone to the PC but the device it's not recognized anymore. I get this message in the adb tool "Waiting for device"
I really appreciate if it's someone that can help me
I have a p500 and I had the exact same problem as you. But I was able to fix it after a lot of Googling.
Can you get to fastboot right now? If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located. After that, type:
Code:
fastboot devices
into ADB. If your device is listed then proceed and type:
Code:
fastboot flash recovery recovery.img
If nothing comes up when you ask it to list fastboot devices you need to delete all of the drivers associated with your p350, and then reinstall them using a toolkit or PDAnet. Then go back and try fastboot devices again.
.
Logan_M said:
I have a p500 and I had the exact same problem as you. But I was able to fix it after a lot of Googling.
Can you get to fastboot right now? If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located. After that, type:
Code:
fastboot devices
into ADB. If your device is listed then proceed and type:
Code:
fastboot flash recovery recovery.img
If nothing comes up when you ask it to list fastboot devices you need to delete all of the drivers associated with your p350, and then reinstall them using a toolkit or PDAnet. Then go back and try fastboot devices again.
.
Click to expand...
Click to collapse
No, I can't get to fastboot. I can't do anything with the command line. It remains to the logo screen
catalin11 said:
No, I can't get to fastboot. I can't do anything with the command line. It remains to the logo screen
Click to expand...
Click to collapse
Can you pull the battery and then use the combination to get into Fastboot? If you can't get to fastboot, then the problem is beyond what I'm capable of doing.
Though, the problem may be that you completely deleted your recovery.
Logan_M said:
Can you pull the battery and then use the combination to get into Fastboot? If you can't get to fastboot, then the problem is beyond what I'm capable of doing.
Though, the problem may be that you completely deleted your recovery.
Click to expand...
Click to collapse
Now, I'm back to the first problem
"Fastboot mode started udc_start()
-- suspend --
-- suspend --
"
catalin11 said:
Now, I'm back to the first problem
"Fastboot mode started udc_start()
-- suspend --
-- suspend --
"
Click to expand...
Click to collapse
if i write this in cmd "fastboot flash recovery recovery.img" it apear < waiting for device > and nothing happens
catalin11 said:
if i write this in cmd "fastboot flash recovery recovery.img" it apear < waiting for device > and nothing happens
Click to expand...
Click to collapse
now i'm in the emergency mode
Problem solved:
1- download the official drivers from LG Site
2- cmd and:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot -w
fastboot flash recovery recovery.img (Clowork custom recovery)
Fastboot Reboot
Installing Cyanogen after i erase everything (fastboot erase sdcard). I like fresh starts
some1 pls help me
catalin11 said:
Problem solved:
1- download the official drivers from LG Site
2- cmd and:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot -w
fastboot flash recovery recovery.img (Clowork custom recovery)
Fastboot Reboot
Installing Cyanogen after i erase everything (fastboot erase sdcard). I like fresh starts
Click to expand...
Click to collapse
can u plz elaborate...i too have the same problem....plz..
Logan_M said:
If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located.
Click to expand...
Click to collapse
That is incorrect. The recovery does NOT have to be named recovery to use fastboot to flash it, although it does make life simpler
whenever i try to go into recovery mode, it takes me to the default one even after i flashed twrp. my bootloader is unlocked and i flashed twrp several times. even when i use the command prompt from fastboot mode it still takes me to the default recovery. any ideas to what's wrong?
Asafbzm said:
whenever i try to go into recovery mode, it takes me to the default one even after i flashed twrp. my bootloader is unlocked and i flashed twrp several times. even when i use the command prompt from fastboot mode it still takes me to the default recovery. any ideas to what's wrong?
Click to expand...
Click to collapse
This could be a solution or a workaround:
"Hello i just had a personal experience with my Asus zenfone selfie Z00T Stock recovery kept replacing TWRP. (Boot loader already unlocked)
This is how i got around it i downloaded the latest TWRP for my device and placed directly in minimal adb and fastboot app folder then i renamed it to recovery .
then i put my device in fastboot mode using the buttons on the phone and After i ran minimal adb and fastboot app as admin then i typed fastboot flash recovery recovery.img
once done i then i typed fastboot boot recovery.img. and my phone booted to twrp recovery then i selected reboot recovery directly on my phone and to finish reboot system (still in twrp) that's it.
(OEM commands to boot from fastboot to recovery do not work on some devices )
it only worked for me eventually because i downloaded the latest TWRP from the official TWRP website.
The idea is to flash the custom recovery and then booting from the custom recovery.img that you just used to flash (the one still on the pc) using minimal adb and fastboot app.
IT may not work on all devices as the commands may change from one device to another but the idea stays the same. (example for nexus fastboot -c "lge.kcal=0|0|0|x" boot recovery.img)
I hope this will help some people out."
sill not booting into twrp
Tiqqy said:
This could be a solution or a workaround:
"Hello i just had a personal experience with my Asus zenfone selfie Z00T Stock recovery kept replacing TWRP. (Boot loader already unlocked)
This is how i got around it i downloaded the latest TWRP for my device and placed directly in minimal adb and fastboot app folder then i renamed it to recovery .
then i put my device in fastboot mode using the buttons on the phone and After i ran minimal adb and fastboot app as admin then i typed fastboot flash recovery recovery.img
once done i then i typed fastboot boot recovery.img. and my phone booted to twrp recovery then i selected reboot recovery directly on my phone and to finish reboot system (still in twrp) that's it.
(OEM commands to boot from fastboot to recovery do not work on some devices )
it only worked for me eventually because i downloaded the latest TWRP from the official TWRP website.
The idea is to flash the custom recovery and then booting from the custom recovery.img that you just used to flash (the one still on the pc) using minimal adb and fastboot app.
IT may not work on all devices as the commands may change from one device to another but the idea stays the same. (example for nexus fastboot -c "lge.kcal=0|0|0|x" boot recovery.img)
I hope this will help some people out."
Click to expand...
Click to collapse
i've just tried this but the 'fastboot boot recovery' command just turn the phone back on from fastboot. thanks anyways!
Tiqqy said:
This could be a solution or a workaround:
"Hello i just had a personal experience with my Asus zenfone selfie Z00T Stock recovery kept replacing TWRP. (Boot loader already unlocked)
This is how i got around it i downloaded the latest TWRP for my device and placed directly in minimal adb and fastboot app folder then i renamed it to recovery .
then i put my device in fastboot mode using the buttons on the phone and After i ran minimal adb and fastboot app as admin then i typed fastboot flash recovery recovery.img
once done i then i typed fastboot boot recovery.img. and my phone booted to twrp recovery then i selected reboot recovery directly on my phone and to finish reboot system (still in twrp) that's it.
(OEM commands to boot from fastboot to recovery do not work on some devices )
it only worked for me eventually because i downloaded the latest TWRP from the official TWRP website.
The idea is to flash the custom recovery and then booting from the custom recovery.img that you just used to flash (the one still on the pc) using minimal adb and fastboot app.
IT may not work on all devices as the commands may change from one device to another but the idea stays the same. (example for nexus fastboot -c "lge.kcal=0|0|0|x" boot recovery.img)
I hope this will help some people out."
Click to expand...
Click to collapse
Work for me. Thanks buddy
This works, thumb up
Asafbzm said:
i've just tried this but the 'fastboot boot recovery' command just turn the phone back on from fastboot. thanks anyways!
Click to expand...
Click to collapse
i have suffered with the same problem for hours until i decided to come here and look for related article , it actually worked and made me wonder that it wasn't that hard to fix it , i just rebooted fastboot and flashed twrp and in the end typed 'fastboot reboot recovery.img
that solved my suffering within 5 seconds. thank you for sharing the knowledge
Tiqqy said:
This could be a solution or a workaround:
"Hello i just had a personal experience with my Asus zenfone selfie Z00T Stock recovery kept replacing TWRP. (Boot loader already unlocked)
This is how i got around it i downloaded the latest TWRP for my device and placed directly in minimal adb and fastboot app folder then i renamed it to recovery .
then i put my device in fastboot mode using the buttons on the phone and After i ran minimal adb and fastboot app as admin then i typed fastboot flash recovery recovery.img
once done i then i typed fastboot boot recovery.img. and my phone booted to twrp recovery then i selected reboot recovery directly on my phone and to finish reboot system (still in twrp) that's it.
(OEM commands to boot from fastboot to recovery do not work on some devices )
it only worked for me eventually because i downloaded the latest TWRP from the official TWRP website.
The idea is to flash the custom recovery and then booting from the custom recovery.img that you just used to flash (the one still on the pc) using minimal adb and fastboot app.
IT may not work on all devices as the commands may change from one device to another but the idea stays the same. (example for nexus fastboot -c "lge.kcal=0|0|0|x" boot recovery.img)
I hope this will help some people out."
Click to expand...
Click to collapse
I had the same issue on Poco F1 and this worked for me as well! Pleasant surprise. First result on google was this article and it worked, 2 minutes work.
Lamantin001 said:
I had the same issue on Poco F1 and this worked for me as well! Pleasant surprise. First result on google was this article and it worked, 2 minutes work.
Click to expand...
Click to collapse
Okay, I was a bit too early with that. The next time I turned off the phone and tried booting to recovery (Vol up+pwr), I got booted into factory recovery (mi-recovery 3.0) :/
Lamantin001 said:
Okay, I was a bit too early with that. The next time I turned off the phone and tried booting to recovery (Vol up+pwr), I got booted into factory recovery (mi-recovery 3.0) :/
Click to expand...
Click to collapse
Update:
I found the solution. I followed the steps in this article:
How can I keep MIUI from overwrite TWRP with stock recovery after a ROM flash?
I'm on fw Global 9.6.6.0. (Bought the phone 'bogus' unlocked with "fake" 9.6.4.0, bricked it while trying to restore chinese fw and re-lock bootloader using miflash - I'm not doing that again brought it back to life using the steps from...
forum.xda-developers.com
Asafbzm said:
whenever i try to go into recovery mode, it takes me to the default one even after i flashed twrp. my bootloader is unlocked and i flashed twrp several times. even when i use the command prompt from fastboot mode it still takes me to the default recovery. any ideas to what's wrong?
Click to expand...
Click to collapse
Try this:
when you are in fastboot mode type:
Code:
fastboot boot recovery.img
This command will boot your phone to twrp. Install twrp .zip file (there are 2 options when installing .img or .zip)
after this go to ADB/Sideload - This is in Advanced section
Then swipe to start a sideload. Now on your pc type:
Code:
adb sideload recovery.zip
This worked for me. I hope this works for you too
Hello,
I have unlocked my bootloader successfully.
When i try to flash recoveries:
TWRP-3.5.1-vayu-Nebrassy-1.img
PBRP-vayu-20210407-test-UNOFFICIAL.img
twrp-3.5.1_10-0-vayu-Nebrassy.img
OrangeFox-R11.0_5-Unofficial-vayu.img
The fastboot command is successfull, no errors whatsoever.
But when try to boot to recovery by vol up + power, i get to the fastboot screen only.
and fastboot boot recovery.img also does not boot to the recovery, rather just boots me to MIUI.
When i do a adb reboot recovery from within miui, i go to miui recovery.
So surely the recovery isint flashing.
Has anyone faced such issue?
Thanks.
Oh my goodness..
I was doing this on a windows m/c since the miflash is windows application.
I switched to linux, and flashing works.. i am on TWRP!
It will flash if you flash custom recovery. However, it will change the custom recovery back to Mi-recovery every time after booting, if your system is stock MIUI.
TWRP works better if you use
fastboot boot twrp.img
Click to expand...
Click to collapse
If you are flashing roms on bhima, don't use TWRP.
Use OrangeFox.
fastboot boot OrangeFox-R11.0_5-Unofficial-vayu.img
Click to expand...
Click to collapse
Hello. I am new to rooting and I wanted to root my old Moto E3 power. But the problem is when I flash TWRP into the recovery it says OKAY and finished then when I try to enter recovery mode my phone just boots up the OS and TWRP is not installed. Please help. Thank you in advance.
Fastboot commands operate on phone's bootloader, not on Android OS as this ADB does.
jwoegerbauer said:
Fastboot commands operate on phone's bootloader, not on Android OS as this ADB does.
Click to expand...
Click to collapse
I know. What i wanted to say was when I do "fastboot flash recovery recovery.img" it just says OKAY and finished. As my phone's power button is broken I can't go directly into recovery from there what do I do?? and also thank you for replying.
Code:
adb devices
adb reboot recovery
jwoegerbauer said:
Code:
adb devices
adb reboot recovery
Click to expand...
Click to collapse
ok I did that now it says no command on the recovery and no TWRP. Now what?
Reflash phone's Stock ROM to get rid off of all modifications you applied so far.