Having moved from MIUI to CM7 Nightlies earlier today, I decided to change my HBOOT to the specific CM7 one. It didn't stick, as it wouldn't let me boot into any ROM past recovery, so I decided to replace the the HBOOT back to Bravo Stock 1.8, and to try again.
Performed the following, after checking the MD5 hash:
Code:
>fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)... OKAY [ 0.082s]
writing 'hboot'... FAILED (remote: image update error)
finished. total time: 0.304s
After that any fastboot command just gave <waiting for device>.
Taking out and then reseating the battery has now left me with my device no longer being able to turn on, pressing power does nothing, and plugging into a computer, or even the wall socket yields no charge LED.
Obviously I've gone and done something stupid, all I really need to know is am I done for?
Related
Hi.
At first I tried the fastboot method, with this result;
Code:
C:\Users\Sveinus>fastboot flash recovery C:\recovery.img
sending 'recovery' (1250 KB)... OKAY [ 0.189s]
writing 'recovery'... FAILED (remote: image error! (BootMagic check
fail))
finished. total time: 0.190s
Then I tried to flash it with enrEVOked again, and I thought it was finished when it said "running root." so I disconnected the phone. After that I've been unable to start recovery mode, and than I tried method II here; http://forum.xda-developers.com/showthread.php?t=929628
and I'm stil unable to enter recovery :S
I recommend you reflash the device with a RUU, then do the Unrevoked again. I usually untick 'Disable security on phone" before enabling USB debugging on the phone in Unrevoked since it doesn't work for me (why install something that doesn't work?) and apply the AlphaRev HBOOT instead.
Also, if an error comes up regarding getting root, reset to factory settings from the OS (Settings) and try again.
unrEVOked doesn't S-OFF GSM phones, only CDMA ones
Ah, didn't know that. Thanks
god tho know !
Edit - Problem was after flashing hboot I could not boot into recovery .... I tried multiple recovery images AmonRa and Cwm but it would never boot.
Solved - I have no idea how, I downloaded the recovery image again with the same link as the previous images, all md5sums were ok, but the 4th download worked and I was able to flash + boot into recovery again? Do I have some other problem though because I don't see why it took so many flashes for me to be able to access recovery again?
Alphrev Cm7 r2
Bravo PVT1 Ship S- OFF
Hboot-6.83.1002
Radio-5.17:52.18
C:\android\tools>fastboot devices
HT~~####93 fastboot
C:\android\tools>fastboot flash hboot bravo_alphaspl-cm7r2.img
sending 'hboot' (512 KB)...
OKAY [ 0.096s]
writing 'hboot'...
OKAY [ 0.164s]
finished. total time: 0.261s
C:\android\tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\android\tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.039s]
finished. total time: 0.040s
Reboot to recovery - stuck on splash??? Using Reflex S...
Edit - After trying to boot to recovery, sat on splash screen for 40 mins and then my bootanimation randomly started... everything is just back to normal?
I can't seem to be able to flash recovery though, it just doesn't boot into it?! I've tried a couple of images and checked md5sum's but it always sticks on splash??
hmm that's strange, suppose you could try to flash a different HBOOT, then try a different recovery - that's what I'd do anyway
bortak said:
hmm that's strange, suppose you could try to flash a different HBOOT, then try a different recovery - that's what I'd do anyway
Click to expand...
Click to collapse
I shouldn't of posted really but something that usually take 10 minutes took an hour or two.... I used the exact command everytime and the same files... It just didn't work!? I'm still really confused but happy it's working
I've got Desire which is stuck in hboot with only ruu option. The original owner tried to apply the official Gingerbread update and failed. It's S-ON with new hboot. I've tried to apply the RUU again and it hang on updating radio.... and in one point I've got the screen where it says that everything is ok except the radio. I've tried to Alpharev it, SuperOneClick, Revolutionary and so on. but without success, they are all waiting for the device
I assume that this hboot with only ruu option doesn't give much of the fastboot commands. The only one I have successfully started is fastboot devices. The fastboot flash of any img is no go.
Is there something I can do to get custom recovery or s-off to get it back to life?
btw. I've read all the possible threads that I could find, with connection to this status, but all of the people that have solved the issue are with S-OFF phone.
Thanks
So you are currently on hboot version 1.02.0001? If yes, revolutionary should work. This "waiting for device" sounds to me as if you did not uninstall htc sync (reboot computer after this) and installed these htc fastboot drivers from revolutionary site. Or did you?
From what you've told us, it's a radio brick - which is unfixable. Only hope is to send it back to HTC and make up a good story.
If the radio update really failed, the phone would not react at all.
TouchPaled from dGB with Transparent XDA App
@MatDrOiD: I've tried that, but nothing happens. But I've successfully managed to "finish" the RUU with revolutionary fastboot drivers. But at the end it showed the screen with some sort of info in hboot which says radio_v2: fail-pu in red letters, end everything else is ok. But it's still stuck with htc logo with exlamation marks or hboot with ruu option.
@bortak: The phone was not rooted or S-Offed so I think there's nothing to be concerned about warranty with HTC. But I don't have warranty for it, maybe the previous owner have it.
Maybe it's a radio brick, but I'm thinking if the xtc clip can sort thing out. If the xtc clip can flash the new hboot and even recovery, maybe it could unbrick the phone? :|
Thanks for you answers, I hope that the phone is not that dead
Same thing has happened to me. It's stuck at the hboot screen with the following:
AlphaRev CM7 r2
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
RUU
It does not show a "Fastboot" option, and pressing Vol Down or Back buttons while turning it on does nothing. I've tried almost every alternative out there, to no avail. It's that screen or the black one with the /!\ on the corners, nothing else.
EDIT:
I've gathered some additional information that could lead to a solution:
I've run Fastboot from the command line, and it recongizes the device s/n, and even lets me run most of the commands. The phone, however, remains unaltered, displaying the same screen with the Alpharev hboot.
Using Android Flasher i've managed to flash a recovery, but couldn't flash the boot.img:
sending 'recovery' (3054 KB)...
OKAY [ 0.589s]
writing 'recovery'...
OKAY [ 0.907s]
finished. total time: 1.496s
downloading 'boot.img'...
OKAY [ 0.587s]
booting...
OKAY [ 0.000s]
finished. total time: 0.587s
rebooting...
finished. total time: 18.499s
sending 'hboot' (1934 KB)...
OKAY [ 0.377s]
writing 'hboot'...
FAILED (remote: image error! (Platform check fail))
finished. total time: 0.378s
rebooting into bootloader...
OKAY [ 0.091s]
finished. total time: 0.091s
rebooting...
So I'm thinking the problem has something to do with the bootloader. Thing is, there's no way to overwrite the hboot already present. Neither stock nor clockwork hboots are working.
¿Is there any way to erase/replace the HBOOT?
sansintierra said:
Same thing has happened to me. It's stuck at the hboot screen with the following:
AlphaRev CM7 r2
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
RUU
It does not show a "Fastboot" option, and pressing Vol Down or Back buttons while turning it on does nothing. I've tried almost every alternative out there, to no avail. It's that screen or the black one with the /!\ on the corners, nothing else.
EDIT:
I've gathered some additional information that could lead to a solution:
I've run Fastboot from the command line, and it recongizes the device s/n, and even lets me run most of the commands. The phone, however, remains unaltered, displaying the same screen with the Alpharev hboot.
Using Android Flasher i've managed to flash a recovery, but couldn't flash the boot.img:
sending 'recovery' (3054 KB)...
OKAY [ 0.589s]
writing 'recovery'...
OKAY [ 0.907s]
finished. total time: 1.496s
downloading 'boot.img'...
OKAY [ 0.587s]
booting...
OKAY [ 0.000s]
finished. total time: 0.587s
rebooting...
finished. total time: 18.499s
sending 'hboot' (1934 KB)...
OKAY [ 0.377s]
writing 'hboot'...
FAILED (remote: image error! (Platform check fail))
finished. total time: 0.378s
rebooting into bootloader...
OKAY [ 0.091s]
finished. total time: 0.091s
rebooting...
So I'm thinking the problem has something to do with the bootloader. Thing is, there's no way to overwrite the hboot already present. Neither stock nor clockwork hboots are working.
¿Is there any way to erase/replace the HBOOT?
Click to expand...
Click to collapse
All you need is alpharev downgrade (flash it via fastboot commands not commander) then run 2.3 RUU (or official 2.3 upgrade that can be found on htc dev site, you can call it however you want).
Sent from my HTC Desire using flashes and thunders
I was trying to update my hboot from 0.94.0000 to install a 4.1 rom. I was following the guide and relocked my bootloader, but the hboot zip wouldn't update.
Now, the phone won't boot, saying "RELOCKED" and "Security Warning" at the top of the screen.
I'm trying to flash a stock RUU to the phone, but can't as I apparently have less than 30% battery.
I'm not sure if the phone is charging in hboot, but I can't turn off the screen, and when I tell the phone to Power Down it just reboots, so if it is charging it's doing it very slowly.
How can I get the phone to turn off so it will charge?!
Nemeth782 said:
I was trying to update my hboot from 0.94.0000 to install a 4.1 rom. I was following the guide and relocked my bootloader, but the hboot zip wouldn't update.
Now, the phone won't boot, saying "RELOCKED" and "Security Warning" at the top of the screen.
I'm trying to flash a stock RUU to the phone, but can't as I apparently have less than 30% battery.
I'm not sure if the phone is charging in hboot, but I can't turn off the screen, and when I tell the phone to Power Down it just reboots, so if it is charging it's doing it very slowly.
How can I get the phone to turn off so it will charge?!
Click to expand...
Click to collapse
Sorry, trying to delete this post to move it but the forum won't let me!
Power down the phone without any charge cable,
Wait 5 minits and plug the power cable in the phone,
Grtz Rongogo
Rongogo said:
Power down the phone without any charge cable,
Wait 5 minits and plug the power cable in the phone,
Grtz Rongogo
Click to expand...
Click to collapse
As soon as I plug it in it boots!
The phone can't charge and stay switched off, as with a custom recovery it will always boot up when connected to a power source. Just unlock the bootloader again and then you should be able to boot normally and can then charge the phone before trying again.
ClydeB1 said:
The phone can't charge and stay switched off, as with a custom recovery it will always boot up when connected to a power source. Just unlock the bootloader again and then you should be able to boot normally and can then charge the phone before trying again.
Click to expand...
Click to collapse
Seemed perfect but can't unlock due to the battery :/
C:\adt-bundle-windows\sdk\platform-tools>fastboot flash unlocktoken c:\Unlock_co
de.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s
Nemeth782 said:
Seemed perfect but can't unlock due to the battery :/
C:\adt-bundle-windows\sdk\platform-tools>fastboot flash unlocktoken c:\Unlock_co
de.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s
Click to expand...
Click to collapse
Using the batch file mentioned elsewhere:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Voltage seems to be (slowly) going up...
Hi,
Unfortenately, I've got the same problem as you mentioned here. Can you please tell me how you did solve this problem?
Regards,
André
Nemeth782 said:
Seemed perfect but can't unlock due to the battery :/
C:\adt-bundle-windows\sdk\platform-tools>fastboot flash unlocktoken c:\Unlock_co
de.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s
Click to expand...
Click to collapse
I finally managed to charge the battery to the desired level with the batch file.
At first, the battery level still lowered using the batch file. It depends on the starting level of the battery, first try AC and the used cable. Hopes this helps other people. I was desperate!
KoosContactdoos said:
Hi,
Unfortenately, I've got the same problem as you mentioned here. Can you please tell me how you did solve this problem?
Regards,
André
Click to expand...
Click to collapse
Q&A for Kindle Fire 2 7" Stock Restore
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Kindle Fire 2 7" Stock Restore. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Gen2 Kindle stock restore - stuck in a boot loop - following overlode's doc
Overlode - Huge thank you for the simple list for us NOOBS of how to get a stock Kindle stuck in a boot loop back up and running. I am having some problems though and was hoping for some help.
I am running Win7 on my PC. I've installed Android SDK, I have a factory cable and my gen 2 Kindle has the pretty "Fastboot" logo with the flashing green light and a non-flashing red light. When I go into my devices manager and see the "Otter2-***.***" it does have the yellow triangle. This is where I deviate from your instructions (in your .doc file). When I right click I do not see the simple "update driver software". I have to go through several windows to finally reach that option. No big deal. But... I clicked the option to "browse my computer for driver software" then "Let me pick from a list of device drivers on my computer". I do not have the option to select "Kindle". I went to have it list ALL DRIVERS and it is not in that list either.
I'm stuck. I don't know how to get the drivers up and working so I can continue with your instruction sheet. I REALLY appreciate all your efforts (with the drop box and everything). I've been fighting this boot loop for a month now and I'm scared to make a bigger mistake. I can build a pc from scratch- no problem... programming and mobile devices just make my brain hurt. Be kind. Everyone seems to throw around abbreviations like Halloween candy and this just makes me want to run for the hills. I'm learning but please don't just assume I know what you're talking about. Thanks in Advance!!
Myth421 said:
Overlode - Huge thank you for the simple list for us NOOBS of how to get a stock Kindle stuck in a boot loop back up and running. I am having some problems though and was hoping for some help.
I am running Win7 on my PC. I've installed Android SDK, I have a factory cable and my gen 2 Kindle has the pretty "Fastboot" logo with the flashing green light and a non-flashing red light. When I go into my devices manager and see the "Otter2-***.***" it does have the yellow triangle. This is where I deviate from your instructions (in your .doc file). When I right click I do not see the simple "update driver software". I have to go through several windows to finally reach that option. No big deal. But... I clicked the option to "browse my computer for driver software" then "Let me pick from a list of device drivers on my computer". I do not have the option to select "Kindle". I went to have it list ALL DRIVERS and it is not in that list either.
I'm stuck. I don't know how to get the drivers up and working so I can continue with your instruction sheet. I REALLY appreciate all your efforts (with the drop box and everything). I've been fighting this boot loop for a month now and I'm scared to make a bigger mistake. I can build a pc from scratch- no problem... programming and mobile devices just make my brain hurt. Be kind. Everyone seems to throw around abbreviations like Halloween candy and this just makes me want to run for the hills. I'm learning but please don't just assume I know what you're talking about. Thanks in Advance!!
Click to expand...
Click to collapse
EDIT: (a day or so later) Hey.. Nevermind. I was able to finally figure things out and downloaded KindleFireFirstAid and was able to wipe it out back to stock using my factory cable. The boot loop was limiting my options. Thanks Anyway.
Fastboot
What would be stopping Fastboot from recognizing my device? I have a fastboot cable for my kindle fire 2, I plug it into my computer then into the kf2, the kf2 boots up into fastboot mode my computer see the kindle and it has the proper drivers installed, but fastboot can't see it for some reason.
I had this problem before when I installed CM10 onto my kf2 but that was a year ago and for the life of me I don't remember how I got fastboot to see my kf2.
All i want to do is downgrade my kf2 back to stock and sell it on ebay. PLEASE HELP! I'm dying here
Any other options?
Overlode-My wife;s KF2 was stuck in boot loop so I tried your stock restore method with a factory cable. Everything seemed to work fine. The drivers were installed, fastboot commands worked on the device, etc. When I did the last reboot step, the device never turned back on. Now the device will not power up with the factory cable or USB cable. Is there anything I can do to fix this KF2 or is it permanently screwed? Thanks.
Kindle Fire 2 - Bricked
Today I tried the procedure in post http://forum.xda-developers.com/kindle-fire-hd/fire-2-development/kindle-fire-2-7-stock-restore-t2840987 but as I use Linux and have the SDK installed I entered the commands from console.
A couple of days ago I flashed Cyanogenmod using very similar steps.
Here is my log for the attempt to restore the stock ROM:
Code:
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.060s]
writing 'bootloader'...
OKAY [ 0.060s]
finished. total time: 0.120s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash boot boot.img
sending 'boot' (4310 KB)...
OKAY [ 1.082s]
writing 'boot'...
OKAY [ 1.053s]
finished. total time: 2.134s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash recovery recovery.img
sending 'recovery' (4828 KB)...
OKAY [ 1.211s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 2.165s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [114.081s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 28.939s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 143.021s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash system system.img
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.004s
(1)
What is worse, after the failure I rebooted in order to restart with the procedure that worked a couple of days ago and leave Cyanogenmod in the Kindle...
but...
No reboot, no lights, no USB detected....
It seems that the tablet is hard bricked.
Is there anything that can be done except using it as a paperweight?
Thanks in advance
KF2 - hardbricked and restored.......almost!!!
Hi,
I have a KF2, which I had previously rooted and installed CM10 custom ROM. Had no problems with it, but decided to try a few more custom ROMS. Forgot about NOT using the KFU program as it was for KF1 devices, and for some stupid reason went ahead and flashed the wrong bootloader.
Result is fairly predictable - HARD BRICKED KF2!!
Thought that was it - searched the forums and everyone was saying the same - no way back from that! Then I came across Kurohyou's post and brilliant guide about hacking a card reader and attaching direct to motherboard. Followed his guide and voila - managed to boot up into recovery (TWRP). However after pushing the ROM files etc to try and install CM ROM again just kept getting "error flashing ROM" . I left the thing after trying various methods and different PC's etc to push the files across and gave up. When I went back to it this morning I couldn't get it to boot into recovery - which I thought was a bit strange. However FASTBOOT mode is ok - I have made a fastboot cable myself which works fine. Kindle was booting up with orange logo, quick flash, orange kindle logo again and repeat. It would not boot into recovery even though I had flashed the correct files via fastboot.
Again almost giving up when I came across Overlode's instructions. Followed them to the letter, and what I am left with now is the standard Kindle Fire logo (orange) which blinks after about 5 seconds and just stays there - left it for about an hour just in case....
I can post screenshots of me flashing the files as per Overlode's instructions if it helps. I get a few errors when using the wipe command, response is "erase successful, but not automatically formatting. File system type not supported" everything else is ok.
I still have the hacked card reader attached which through Ubuntu can see the EMMC directly so don't know if might be worth copying the files directly instead of flashing via fastboot?
Any suggestions gratefully received...... I'm at my wits end with this thing - I know I should have left well alone!!! but I feel like I have run a marathon with this thing only to have fallen flat on my face 5 metres from the finish line!!
Thanks in advance for any help.
lmayala said:
Today I tried the procedure in post http://forum.xda-developers.com/kin...opment/kindle-fire-2-7-stock-restore-t2840987 but as I use Linux and have the SDK installed I entered the commands from console.
A couple of days ago I flashed Cyanogenmod using very similar steps.
Here is my log for the attempt to restore the stock ROM:
Code:
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.060s]
writing 'bootloader'...
OKAY [ 0.060s]
finished. total time: 0.120s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash boot boot.img
sending 'boot' (4310 KB)...
OKAY [ 1.082s]
writing 'boot'...
OKAY [ 1.053s]
finished. total time: 2.134s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash recovery recovery.img
sending 'recovery' (4828 KB)...
OKAY [ 1.211s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 2.165s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [114.081s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 28.939s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 143.021s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash system system.img
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.004s
(1)
What is worse, after the failure I rebooted in order to restart with the procedure that worked a couple of days ago and leave Cyanogenmod in the Kindle...
but...
No reboot, no lights, no USB detected....
It seems that the tablet is hard bricked.
Is there anything that can be done except using it as a paperweight?
Thanks in advance
Click to expand...
Click to collapse
Hi - see my last post - I too have a hard bricked kindle. if you're handy with a soldering iron you can try it - I can confirm it does work.
details here -
http://forum.xda-developers.com/showthread.php?t=2415870
I managed to get my kindle from nothing (not even charging light) to back up and running with TWRP installed. I couldn't get a custom ROM installed, kept getting errors - but I think my board has other issues. While I was putting it back together I managed to stick my screwdriver through the battery (don't ask!!!) Since then I think I have caused other damage and it was never the same again I think I may have damaged the memory or the EMMC..... on the hunt for new motherboard at present!
Good luck!
registered an account just to thank you. You saved my KF2.