I have successfully unlocked my bootloader using the htcdev.com way. Then I tried to flash FlyHigh ROMv1.2, unfortunately my Wi-Fi is unable to turn on. I get Error everytime I try to turn on my wi-fi. Then I tried to flash radio.img using the fastboot command: "fastboot flash radio radio.img" but it gives me an error message.
Code:
sending 'radio' (256000 KB)...
OKAY [ 4.161s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.082s
I was able to flash boot, recovery, the only thing that failed was radio.
Help me please.
EDIT: I got HC working, so nevermind.
Questions like this should go into General section or in the respective ROM thread. You mention FlyHigh, which already has a radio (20.3504.3 0.089BU_3809.07.04.12_M).
I would recommend to fullwipe your device with recovery twice and then re-flash FlyHigh via Recovery.
Sorry about the wrong section.
I fullwiped twice and flashed the FlyHigh ROM again but it doesn't work. I still cannot turn on my Wi-Fi, is it something wrong with the radio or something else?
Related
I have successfully unlocked my bootloader using the htcdev.com way. Then I tried to flash FlyHigh ROMv1.2, unfortunately my Wi-Fi is unable to turn on. I get Error everytime I try to turn on my wi-fi. Then I tried to flash radio.img using the fastboot command: "fastboot flash radio radio.img" but it gives me an error message.
Code:
sending 'radio' (256000 KB)...
OKAY [ 4.161s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.082s
I was able to flash boot, recovery, the only thing that failed was radio.
Help me please.
EDIT: I got HC working, so nevermind.
i too have the same problem and am going round in circles please help
You need to flash the boot.img
mcord11758 said:
You need to flash the boot.img
Click to expand...
Click to collapse
thanks for the reply so i flash he boot.img rather than radio.img ie fastboot flash boot boot.img rather than fastboot flash radio radio.img
Correct
hi all,
I'm HBOOT 1.5 and htcdev method to unlocked(but s-on), but can not flash radio.img, fastboot flash radio radio.img said:
sending 'radio' (17505 KB)...
OKAY [ 3.859s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.469s
the radio.img is extracted from PG86IMG.zip of 2.08.561.2.
Also, I can not flash wimax.img.
But, I can flash boot.img,recovery.img successfully, and totally updated with RUU 2.08.561.2 successfully. But when I try to flash radio.img,wimax.img with fastboot, it show above message; I tried toput radio.img,wimax.img onto the sd card(pachaged by PG86IMG.zip), hboot can find PG86IMG.zip, but after parsing the package, bootloader just ignore it and give nothing hint.
Any other method to flash radio.img? Thanks in advance!
Current state:
Hboot 1.50 Unlocked S-ON
Boots into stock ROM
I was stuck in a boot loop and couldn't get into recovery so I relocked my phone and ran RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.
Phone booted correctly after the RRU and was able to unlock the device. I went back and followed the instructions HERE to flash TWRP recovery. The exact same way that I had originally flashed.
When I was trying to Flash my recovery I received this:
Code:
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5068 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s
1. Am I screwed?
2. What can I do to prevent this in the future?
3. How do I fix it?
franciumgoesboom said:
Current state:
Hboot 1.50 Unlocked S-ON
Boots into stock ROM
I was stuck in a boot loop and couldn't get into recovery so I relocked my phone and ran RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.
Phone booted correctly after the RRU and was able to unlock the device. I went back and followed the instructions HERE to flash TWRP recovery. The exact same way that I had originally flashed.
When I was trying to Flash my recovery I received this:
Code:
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5068 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s
1. Am I screwed?
2. What can I do to prevent this in the future?
3. How do I fix it?
Click to expand...
Click to collapse
1. No.
2. Nothing, it happens sometimes.
3. Maybe a corrupt download? Try again with a new copy of recovery.
If that doesn't work, try a different recovery.
I receive that error no matter which recovery I try.
The first file I tried in the OP was the same file that I had used when I originally started flashing. I just tried with twrp 2.0 and the same thing happens.
Code:
C:\Android>fastboot flash recovery twrp-shooter-2.0.0RC0.img
sending 'recovery' (5122 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.012s
Maybe it is time to start looking at the downgrade process.
Hello!
I installed Munjeni's special hboot partition (to increase usable space) and wanted to update the phone back to stock (to take back to att).
The RUU utility failed with code of 152.
The partition failed.
Now the phone is "stuck" at the black HTC screen with four warning triangles in each corner.
Any ideas?
I can fastboot and issue some commands...
I am s-on, hboot 1.02.
Thanks in advance!
DanGeorges said:
Hello!
I installed Munjeni's special hboot partition (to increase usable space) and wanted to update the phone back to stock (to take back to att).
The RUU utility failed with code of 152.
The partition failed.
Now the phone is "stuck" at the black HTC screen with four warning triangles in each corner.
Any ideas?
I can fastboot and issue some commands...
I am s-on, hboot 1.02.
Thanks in advance!
Click to expand...
Click to collapse
If the bootloader is accessible, you can try grabbing the rom.zip out of the RUU (run it & let it load, then search in Windows' temporary folder for "rom.zip". If not there's probably a download somewhere), and rename it to "LIBEIMG.zip" on the root of the SD card.
Then boot into the bootloader (vol down) and it should pick it up and start flashing (might be a confirmation before it does)
Edit: Well I looked at the title again... does this mean its not accessible?
It should be if fastboot is, but I've never had the bad triangles so not completely sure..
If not, alternate option that may work: extract the hboot image from rom.zip and flash it with fastboot (if its allowed)
This is the RUU zip: http://www.mediafire.com/?tay1j415ymvukh5
drumist said:
This is the RUU zip: http://www.mediafire.com/?tay1j415ymvukh5
Click to expand...
Click to collapse
Thank you for the link. I'm downloading it now.
I can fastboot, but I'm S-on (from one of my flashes).
What's the fastboot command for flashing the hboot? Will this even let me?
I'll give this a try. Thanks again!
When I try to fastboot flash a recovery, here's what I get:
C:\Mobile\Android\Fastboot and ADB Tool>fastboot flash recovery recovery.img
sending 'recovery' (3716 KB)... OKAY [ 0.875s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.578s
C:\Mobile\Android\Fastboot and ADB Tool>
For hboot - does anyone have an idea which hboot I can try flashing?
WinSuk said:
If the bootloader is accessible, you can try grabbing the rom.zip out of the RUU (run it & let it load, then search in Windows' temporary folder for "rom.zip". If not there's probably a download somewhere), and rename it to "LIBEIMG.zip" on the root of the SD card.
Then boot into the bootloader (vol down) and it should pick it up and start flashing (might be a confirmation before it does)
Edit: Well I looked at the title again... does this mean its not accessible?
It should be if fastboot is, but I've never had the bad triangles so not completely sure..
If not, alternate option that may work: extract the hboot image from rom.zip and flash it with fastboot (if its allowed)
Click to expand...
Click to collapse
I'll try the hboot image and see what happens.
What's the fastboot command?
I tried:
fastboot flash hboot
and
fastboot flash boot
Both gave me an invalid signature:
C:\>fastboot flash hboot hboot_liberty_7227_1.02.0000_101104.nb0
sending 'hboot' (512 KB)... OKAY [ 0.234s]
writing 'hboot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.328s
C:\>fastboot flash boot hboot_liberty_7227_1.02.0000_101104.nb0
sending 'boot' (512 KB)... OKAY [ 0.234s]
writing 'boot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.328s
Hey Guys,
Last night I was attempting a Revolutionary S-off hack and during the first step where youre supposed to downgrade the software to 1.13 my restarted for updates -___- Since I relocked the bootloader to start the process (my phone was rooted and flashed with Harmonia) , I retried the process. I kept getting errors that said I was using the wrong updater for the process to work. (I wasnt). So i attepmted to work around the updater and found a copy of the RUU i needed (1.13) for the EVO V for Virgin Mobile earlier today and tried to flash the zip using the fastboot commands but it keeps telling me this:
C:\Users\Shaun\Desktop\Android>fastboot flash zip PG86IMG.zip
sending 'zip' (6882 KB)...
OKAY [ 2.465s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 4.449s
I cant access the recovery to try it there either. It just takes me back to the same white bootloader screen. It says its locked there. In fact, it wont let me flash anything, TWRP or the RUU or any other ROM for that matter. It just tells me "signature verify fail" So im completely stuck. Im out of ideas completely. Someone please help.