deleted..... nvm....
If you can't boot into recovery or fastboot you're screwed.
I'm in the same boat. Rogers screen is stuck (left it overnight, it's definitely stuck)
I can access Fastboot but not Recovery.
Any ideas?
@Creedian - Use fastboot to fix the brick...
Related
I picked up my nexus after hiking, found it froze on a screen and VERY hot. I pulled the battery, let it cool, and now its stuck at the boot loader.
I can access fastboot, but i can not get into recovery.
i tried:
1) reflash revocery via fastboot - no go
2) Tried to restore nexus to stock by
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash system system.img - All flashed, but still end up in a stuck bootloader
Phone is STILL stuck at bootloader screen. Any help? I had the phone for only 3 months. I dunno if HTC will cover it. Honestly i don't even know what went wrong besides it overheated
Hi Guys ;
I have unlocked the bootloader of my HTC one and now inside fastboot it shows UNLOCKED. I have also tried to flash both TWRP and CWM recoveries using fastboot method and both finishes with success with no error messages.
but the problem is that I can not boot into recovery. I dont know what happens exactly but seems rebooting into recovery fails and phone reboots again into normal mode so I see the htc boot screen twice and then I am in normal mode.
Do you have any ideas ?
Regards
I finally managed to install TWRP. the trick was to disable fast boot in power settings , then turn off the phone completely and enter hboot and then fastboot.
I was entering fastboot directly through adb and it was not working ! it should be a bug inside bootloader. it should not matter how you enter fastboot , but in this case it does matter ! I hope it helps someone.
I was using fastboot to flash recovery and boot images. Now I can't boot into recovery and the phone blacks out after the bootloader unlocked warning. Adb says the device is offline while fastboot shows nothing. When trying to reboot-bootloader using fastboot, it responds with <waiting on device>. Any suggestions?
Is it possible the battery is not sufficiently charged?
audit13 said:
Is it possible the battery is not sufficiently charged?
Click to expand...
Click to collapse
Maybe now, but the battery had plenty of juice at first. After the system was bricked, though, I could not turn it off. The screen kept a faint ethereal glow, so I definitely have to charge before any future attempts. Otherwise, it won't even show me the screen warning me that the bootloader is unlocked.
cavalier23 said:
I was using fastboot to flash recovery and boot images. Now I can't boot into recovery and the phone blacks out after the bootloader unlocked warning. Adb says the device is offline while fastboot shows nothing. When trying to reboot-bootloader using fastboot, it responds with <waiting on device>. Any suggestions?
Click to expand...
Click to collapse
I was working on a Mac while getting the above results. I have since tried Windows. The only difference is the error message from adb. Adb now says that the device is "unauthorized."
I was about to flash a recovery image to my son's generic tablet, but I issued a fastboot reboot command from adb and it now won't boot past an android splash screen. I've pulled the battery. I've tried holding the volume up key for booting to recovery. Nothing. No joy. I don't think it's possible to brick a device just by sending a reboot command. I'm assuming it's just stuck looking for a reboot recovery file of a different name. Then again, a boot loop is as good as bricked. Any suggestions?
lil_bono said:
I was about to flash a recovery image to my son's generic tablet, but I issued a fastboot reboot command from adb and it now won't boot past an android splash screen. I've pulled the battery. I've tried holding the volume up key for booting to recovery. Nothing. No joy. I don't think it's possible to brick a device just by sending a reboot command. I'm assuming it's just stuck looking for a reboot recovery file of a different name. Then again, a boot loop is as good as bricked. Any suggestions?
Click to expand...
Click to collapse
Nevermind... after a few groundings of the battery cables, it has come back from the dead. Thanks for playing
lil_bono said:
I was about to flash a recovery image to my son's generic tablet, but I issued a fastboot reboot command from adb and it now won't boot past an android splash screen. I've pulled the battery. I've tried holding the volume up key for booting to recovery. Nothing. No joy. I don't think it's possible to brick a device just by sending a reboot command. I'm assuming it's just stuck looking for a reboot recovery file of a different name. Then again, a boot loop is as good as bricked. Any suggestions?
Click to expand...
Click to collapse
I feel that I should update folks on the latest details. As it turns out, this tablet is a Chinese 'allwinner' made by Eken. It's not just hanging because of my actions. Apparently these devices do not follow proper GPL. It doesn't respond to many fastboot commands at all. Once I issued the command to boot into fastboot, and it gets into fastboot mode, it stops responding. You can not issue any commands to bring it out of fastboot either! Not something I would recommend people invest in, no matter how cheap. It also has software that I would consider malware attached to the Android browser. It literally tells you that it will track you and throw advertisements whenever it wants. Garbage.
So this watch was of my dad. One day it went into bootloop ....rebooting and stuck on lg logo. So first i unlocked its bootloader using fastboot commands. Then i tried to flash various roms,recoveries..but no luck. Basically only fastboot mode can be accessed..
When i try to go in recovery it just shows a black screen and reboots...so no adb
Any way i can revive it...?
Same problem here...
Use Fastboot to reflash all three image files. You may need a new battery first that is what caused my watch to start boot looping.