So, I finally managed to flash a recovery via fastboot, but now I can't enter the recovery, every time I enter fastboot and hit "recovery the phone keeps rebooting itself.
I also tried "fastboot boot recovery.img" with the same results. Is there a way to flash a ROM using fastboot? Also, ADB is not recognizing the device under "adb device".
Thanks in advance,
Related
Hi Guys,
I tried putting in a new ROM for my HTC ONE X International (HBOOT 1.33) and this problem came up.
1. Phone is stuck in bootloop. Whenever I try to turn it off, it automatically reboots
2. Battery drain because of bootloop, doesn't charge.
3. I can enter HBOOT but encounters the following issue
- Trying to enter recovery leads to rebooting and continuing the bootloop
- Trying to factory reset leads to rebooting and continuing the bootloop
4. Computer cannot detect the device since it never goes past the HTC load screen
I really appreciate any help you guys can provide.
Thank you
Did you flash the boot.img? You need to do it through fastboot: fastboot flash boot boot.img
Do a "fastboot erase cache" afterwards.
Also, which ROM were you flashing?
Sent from my One X
What recovery are you using? Try to flash the latest CWM from here http://www.clockworkmod.com/rommanager
it lets you charge when in recovery.
In order to flash it I had to have fastboot open and ready in the command window with the command to flash already typed in, then it was just a matter of timing->as soon as you go from Hboot to fastboot press enter.
Once you have access to the recovery you should be able to confirm your Hboot version and workout what needs to be done from there (ie flash the appropriate boot.img, or recovery from nandroid backup, run an RUU, or who knows what).
TToivanen said:
Did you flash the boot.img? You need to do it through fastboot: fastboot flash boot boot.img
Do a "fastboot erase cache" afterwards.
Also, which ROM were you flashing?
Sent from my One X
Click to expand...
Click to collapse
I was flashing OrDroidX 1.3.2. How can I flashboot if my device isn't recognized by my computer when I plug it in? (Sorry it's my first time) Also, my battery doesn't seem to be charging when it's off.
You need to be in fastboot mode. It should say fastboot in your bootloader menu, select it using hardware buttons. On the scree you should see
FASTBOOT USB
Then fastboot should work OK.
Check connection by doing
Code:
fastboot devices
If your battery voltage is really low, check out this script. It will start rebooting the phone and eventually battery will charge.
requiem11 said:
What recovery are you using? Try to flash the latest CWM from here
it lets you charge when in recovery.
In order to flash it I had to have fastboot open and ready in the command window with the command to flash already typed in, then it was just a matter of timing->as soon as you go from Hboot to fastboot press enter.
Once you have access to the recovery you should be able to confirm your Hboot version and workout what needs to be done from there (ie flash the appropriate boot.img, or recovery from nandroid backup, run an RUU, or who knows what).
Click to expand...
Click to collapse
How do I do this if my computer won't recognize the phone when I plug it into my computer? Thanks
Hey. I was using a 5.0.1 GPE Rom on my M8 and decided to update both the firmware and the rom to 5.1
I Backed everything up and decided to, as usual, use adb to sideload the firmware to the phone. I did and everything went as expected. After I finished I rebooted to android. I get NFC service stopped working, System UI stopped working and I can't interact with the phone. My thought, well let's go to the recovery and flash a rom I have in my external SD card. No recovery to be found just a android guy belly up with a red ! sign on his belly.
So I thought, I lost my recovery due to the firmware flash, I had happened before, So i went online found a TWRP recovery and went to flash it. Reboot to fastboot USB mode, but then in adb I cannot see the device at all. "adb devices" shows and empty list. I tried my windows 7 laptop to the same result.
Can anyone PLEASE PLEASE help me, I'm kinda freaking out at this point and am running out of options
xsidex said:
..... Reboot to fastboot USB mode, but then in adb I cannot see the device at all. "adb devices" shows and empty list.
Click to expand...
Click to collapse
When in fastboot mode - run command fastboot devices
No adb when in fastboot mode
To flash a recovery (unlocked bootloader)
fastboot flash recovery nameofrecovery.img
ckpv5 said:
When in fastboot mode - run command fastboot devices
No adb when in fastboot mode
To flash a recovery (unlocked bootloader)
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Sometimes some outside thought can be just ridiculasly helpfull when you are stuck in a tiny issue.
Thank you so much Kind sir, my heart rate thanks you aswell.
What a silly mistake
Hi everyone,
I´ve been trying to install twrp recovery in my Huawei Ascend P6 via fastboot. I followed this "techglen adb and fastboot guide"
I already installed everything needed for adb conection.
So I connect my phone in MTP mode and use "adb devices" and my device appears normally, but the problem happens when I reboot into Bootloader/Fastboot mode and use "Fastboot devices" it appears a device conected but with a bunch of "?????" and a smiley face at the end like this:
C:\Fastboot>adb devices
List of devices attached
123456789 device --------> bunch of numbers appear normally
C:\Fastboot>adb reboot bootloader --------> Phone restarts into bootloader mode (shows huawei ascend logo)
C:\Fastboot>fastboot devices
????????_?_???_?<??????? fastboot ----------> WTF (this is exactly what appears)
I would like to know if there's something wrong with my phone
Should I proceed and flash the custom recovery?
I have stock android 4.4.2 (rooted with kingroot) and stock recovery.
I am a total noob at this so I need your help :crying: I dont want to do anything stupid. (If already did let me know lol)
I have the same issue. Problem is that phone is bricked, so I can only enter in recovery (official, unrooted, unlocked) and fastboot mode.
Have you managed to solve or have some hint?
I have experienced a inconsistency while using minimal adb and fastboot. While device not showing i could send command and the phone would respond. After going into bootloader and while my device wasn't shown in the list i could flash twrp without much trouble, helped me go back from being stuck on bootanimation. used the command fastboot flash recovery xxxx.img (where xxx is the name recovery name). If you can get into boot loader try fastboot reboot bootloader and if the phone responds you might be in the same situation i was.
Always remember: Messing with recoveries bootloaders and boot images might make your phone unusable so do it at your own risk
Have you actually tried to flash twrp? Did you put the img file of twrp to the minimal adb and fastboot folder? If so, try the commands 'fastboot flash recovery recovery_twrp.img(<-- use the name of twrp file here, so not the exact name wrote here) and reboot. My phone is a bunch of question marks as well and it flashed twrp just perfectly (I got it frome here: http://forum.xda-developers.com/showthread.php?t=2632542)
I've been trying to flash TWRP recovery to my rooted LG G3 D855 (running 4.4.2 KitKat). I used the "Bump" method (thread) since I don't have an unlocked bootloader.
I tried the ADB method in that thread, I tried the Flashify method, and I tried the Official TWRP App. Each time, the recovery flashed correctly. But when I attempted to reboot into recovery (using the method in the linked thread, or in the case of the apps, they prompted me to reboot into recovery), my phone didn't bring up TWRP recovery or even the stock recovery. It just brings up "fastboot mode started". It's not stuck though, it boots normally when I pull the battery and power on.
I also separately tried rebooting it into fastboot mode with it plugged into my computer. When I entered "adb devices" into the command prompt, the device came up. Then I rebooted it into fastboot mode and entered "fastboot devices" - then nothing came up. I entered some other fastboot commands and it said "< waiting for device >". So it appears I can't issue normal fastboot commands either.
Any thoughts on how I can succesfully flash TWRP? Thanks.
i have installed my TWRP via this app -- https://ulozto.sk/!lisJevpDG1oS/recovery-d722l-apk
try hope itll help you
Well, somehow you failed to install it. Upgrade to LP (preferably v21C) and try this
Hi,
After several ROM flashings, my A2 Lite is in bootloop mode.
To try to recover my phone, I did followings.
Installed adb, fastboot, miflash.
Executed 'fastboot oem edl' - successful
Miflash of 'daisy_global_images_V9.6.10.0.ODLMIFF_8.1' gives 'SUCCESS' message, however still in bootloop mode.
I opened the back cover and successfully put the phone in edl mode.
Miflash again with the same ROM folder with 'SUCCESS' message , however still in bootloop mode
When I tried 'fastboot flashing unlock' or 'fastboot flashing unlock_critical' command, it produced - 'Failed, remote unknown command' message.
When I try ' fastboot boot twrp_for_daisy.img' , successfully executed . however the phone can not boot in recovery mode.
I would appreciate very much if somebody provides me any help.
Best regards,
Moricelo said:
Hi,
After several ROM flashings, my A2 Lite is in bootloop mode.
To try to recover my phone, I did followings.
Installed adb, fastboot, miflash.
Executed 'fastboot oem edl' - successful
Miflash of 'daisy_global_images_V9.6.10.0.ODLMIFF_8.1' gives 'SUCCESS' message, however still in bootloop mode.
I opened the back cover and successfully put the phone in edl mode.
Miflash again with the same ROM folder with 'SUCCESS' message , however still in bootloop mode
When I tried 'fastboot flashing unlock' or 'fastboot flashing unlock_critical' command, it produced - 'Failed, remote unknown command' message.
When I try ' fastboot boot twrp_for_daisy.img' , successfully executed . however the phone can not boot in recovery mode.
I would appreciate very much if somebody provides me any help.
Best regards,
Click to expand...
Click to collapse
Try changing boot slots via fastboot command