Hey folks,
I'm trying to install a recovery image using fastboot, as per the directions presented here:
http://wiki.cyanogenmod.org/w/Install_CM_for_fireball
When I try flashing the recovery, I get the following error message:
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.117s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.149s
I was able to obtain S-OFF following the directions presented in this thread:
http://forum.xda-developers.com/showthread.php?t=2664460
but I am now currently in "relocked" state because I followed step 5 and tried running DirtyRacun.
Phone: HTC incredible 4g lte.
hboot: 1.15.0000
radio: 1.53.06.0919
OpenDSP-v29.1.0.45.0622
Thanks in advance!
in other news ...
My phone is in an unusable state. I still have access to the bootloader, and when it's plugged into my computer, I have access to it through adb, but otherwise, I can't send or receive phone calls from it.
stringedonbass said:
My phone is in an unusable state. I still have access to the bootloader, and when it's plugged into my computer, I have access to it through adb, but otherwise, I can't send or receive phone calls from it.
Click to expand...
Click to collapse
Apparently shutting down and pulling the battery "fixes" that problem.
Step 5 was not to run dirty racoon it was to flash the engineering hboot from the DirtyRacun webpage, but with S-off you should still be able to flash the hboot and recovery.
I find this page useful when I am working in ADB to keep the ideas fresh. http://forum.xda-developers.com/showthread.php?t=2141817
stringedonbass said:
Hey folks,
I'm trying to install a recovery image using fastboot, as per the directions presented here:
http://wiki.cyanogenmod.org/w/Install_CM_for_fireball
When I try flashing the recovery, I get the following error message:
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.117s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.149s
I was able to obtain S-OFF following the directions presented in this thread:
http://forum.xda-developers.com/showthread.php?t=2664460
but I am now currently in "relocked" state because I followed step 5 and tried running DirtyRacun.
Phone: HTC incredible 4g lte.
hboot: 1.15.0000
radio: 1.53.06.0919
OpenDSP-v29.1.0.45.0622
Thanks in advance!
Click to expand...
Click to collapse
Re: adb guide
wmuflyer said:
Step 5 was not to run dirty racoon it was to flash the engineering hboot from the DirtyRacun webpage, but with S-off you should still be able to flash the hboot and recovery.
I find this page useful when I am working in ADB to keep the ideas fresh. http://forum.xda-developers.com/showthread.php?t=2141817
Click to expand...
Click to collapse
That's a nice guide on the Android Debug Bridge (abd). As a side note, I was pleased to find that fastboot and adb can be found in Ubuntu's repositories.
Update: flashed DirtyRacun's HBOOT
My phone now says
-- DirtyRacun --
at the top of the bootloader. No need to "unlocking" the phone because it was already in S-OFF state. After downloading the HBOOT file from unlimited's fireball website, I typed these commands, also available from their website:
Code:
sudo ./fastboot erase cache
sudo ./fastboot oem rebootRUU
sudo ./fastboot flash zip [file name]
sudo ./fastboot reboot
Happily rooted with CyanogenMOD installed
I'm happily rooted and have CyanogenMOD up and running.
After flashing the engineering hboot onto my phone using unlimited's directions, I was able to install ClockworkMod Recovery for fireball following the directions posted on their website.
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.141s]
writing 'recovery'...
OKAY [ 2.129s]
finished. total time: 3.271s
I then was able to install CyanogenMod from recovery like "clockwork". Of course, "abd reboot-bootloader" is much faster than the crazy key combinations they ask you do to. When asked to install from sdcard, there were two locations to look at.
Cheers everyone! :victory:
Related
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
I was running the latest TRON ROM from Neo with no issues for several days. Tonight, I went to use the camera and it FC'd. It kept doing it so I tried rebooting. It flashed the white screen with the green HTC logo and thats it, it won't go any farther.
I can get to recovery by pulling the battery and using the hard buttons, but recovery is not able to mount the internal or external memory. I cant backup, restore, flash a zip, or do anything really. How could this have happened? Am I bricked?
HELP!
If the phone does anything at all, it is not bricked. (The state it's in is sometimes called a soft brick, though). I believe there are two things you can do: either get an RUU (PH98IMG.zip) onto your SD with a computer (and an SD card reader EDIT: Or the Incredible you mentioned in the ROM thread), then boot up to hboot and let it flash, or try flashing a kernel (boot.img), ROM, or RUU using adb/fastboot.
If you have questions about the first of these processes, I may be able to answer them, but I probably won't be too helpful about the latter since I haven't flashed anything with adb/fastboot in quite a while.
HERE is the latest RUU, by the way.
Thanks, I'll try this out tomorrow.
s-on? Can you boot into the bootloader? Try reflashing the kernel via fastboot.
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
trud9340 said:
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
Click to expand...
Click to collapse
Did you re-unlock after running the RUU?
trud9340 said:
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
Click to expand...
Click to collapse
download this zip and place it on the root of your sd card. it will flash Amon RA through hboot. no need for fastboot commands.
http://androidfilehost.com/?fid=9390248398092764223
mjones73 said:
Did you re-unlock after running the RUU?
Click to expand...
Click to collapse
Just realized that, after doing some research...DOH!
Unlocked and good to go. Thanks!
Try this at your own risk. I do not take any responsibility, read on if you accept the risks.
I have discovered a working solution for people that have S-OFF RELOCKED and took the latest/last OTA update but cant flash a recovery via fastboot and cant re-unlock.
When i tried the following in fastboot
fastboot flash recovery recovery.img (place your favorite recovery into platform-tools folder)
< waiting for device >
sending 'recovery' (8758 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.049s
It errors out by using TWRP and CWM FAILED (remote: not allowed)
INSTRUCTIONS:
download the attached recovery.zip and place it into platform-tools (TWRP recovery)
fastboot oem rebootRUU
---wait for black HTC logo--
fastboot flash zip recovery.zip
--it will show a progress bar on your phone, and finished in the CMD window--
fastboot reboot bootloader
select recovery
profit
Can someone confirm that flashing recovery works with the method above. Also post what version software you are running. Someone with S-ON LOCKED please try this, possible new way to flash ROMS without S-OFF/unlock?
Awesome
I know it's been a while since you posted this, but THANK YOU. Worked a charm on my S-OFF Relocked 3.06. I even modified the zip file, removed the older version of TWRP, inserted a new version (renamed as recovery.img) and now have the most recent TWRP.
Droidel said:
Try this at your own risk. I do not take any responsibility, read on if you accept the risks.
I have discovered a working solution for people that have S-OFF RELOCKED and took the latest/last OTA update but cant flash a recovery via fastboot and cant re-unlock.
When i tried the following in fastboot
fastboot flash recovery recovery.img (place your favorite recovery into platform-tools folder)
< waiting for device >
sending 'recovery' (8758 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.049s
It errors out by using TWRP and CWM FAILED (remote: not allowed)
INSTRUCTIONS:
download the attached recovery.zip and place it into platform-tools (TWRP recovery)
fastboot oem rebootRUU
---wait for black HTC logo--
fastboot flash zip recovery.zip
--it will show a progress bar on your phone, and finished in the CMD window--
fastboot reboot bootloader
select recovery
profit
Can someone confirm that flashing recovery works with the method above. Also post what version software you are running. Someone with S-ON LOCKED please try this, possible new way to flash ROMS without S-OFF/unlock?
Click to expand...
Click to collapse
not working on my htc droid dna firmware version 4.09.605.5
Droidel said:
Try this at your own risk. I do not take any responsibility, read on if you accept the risks.
I have discovered a working solution for people that have S-OFF RELOCKED and took the latest/last OTA update but cant flash a recovery via fastboot and cant re-unlock.
When i tried the following in fastboot
fastboot flash recovery recovery.img (place your favorite recovery into platform-tools folder)
< waiting for device >
sending 'recovery' (8758 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.049s
It errors out by using TWRP and CWM FAILED (remote: not allowed)
INSTRUCTIONS:
download the attached recovery.zip and place it into platform-tools (TWRP recovery)
fastboot oem rebootRUU
---wait for black HTC logo--
fastboot flash zip recovery.zip
--it will show a progress bar on your phone, and finished in the CMD window--
fastboot reboot bootloader
select recovery
profit
Can someone confirm that flashing recovery works with the method above. Also post what version software you are running. Someone with S-ON LOCKED please try this, possible new way to flash ROMS without S-OFF/unlock?
Click to expand...
Click to collapse
Thank you thank you thank you so much.
luis181193 said:
Thank you thank you thank you so much.
Click to expand...
Click to collapse
aminebigboss said:
not working on my htc droid dna firmware version 4.09.605.5
Click to expand...
Click to collapse
Mine work!!
htc droid dna firmware version 4.09.605.5
Hello xda people,
I tried to flash my TF201 with stock 4.1.1 ROM and 10.4.2.18 bootloader and I think I messed up the bootloader because now it can only go into USB mode - RCK, Wipe Data and Android all return "unrecoverable bootloader error" (0x0000000). And in USB mode, only fastboot commands work - ADB commands cannot be executed since it doesn't see the device.
I tried to follow a few troubleshooting guides posted here but hit a snag.
After running the following command:
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
I had this error message:
Code:
FAILED (command write failed (Unknown error))
finished. total time: 0.641s
so I went ahead and probably deleted more things that I should have.
Now I somehow managed to execute :
Code:
fastboot -i 0x0b05 flash recovery openrecovery-twrp-2.6.3.0-tf201-JB.blob
but after that the following command returns an error message:
sending 'recovery' (7934 KB)...
OKAY [ 1.373s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 2.901s
Click to expand...
Click to collapse
Code:
fastboot -i 0x0b05 reboot-bootloader
so I had to reset the device with a paperclip in the reset hole on the side to be able to pick USB mode ( and fastboot)
I think I messed up big time and hope you can help me restore my Prime back to life.
Thank you!
Update:
After performing the following steps , I managed to revert it back to factory ROM:
1. Installed ADB Installer from : http://forum.xda-developers.com/showthread.php?t=2588979
2. Downloaded original ASUS blob from their website - make sure you pick the one for your SKU
3. Followed the steps posted in the Answer from this post: http://android.stackexchange.com/questions/28077/bricked-my-asus-tf300t-manual-jb-update
Hope this helps someone.
When I try to pick RCK from the bootloader options , I get the red exclamation mark with the laying android logo - that has been the case from the very beginning - even before having made any changes to the original stock 4.1.1. ROM.
I have a question: Since I have not unlocked the bootloader prior to upgrading to JB via OTA update, what are the next steps to put KitKat custom ROM to my tablet?
I just brought it back from the dead - I don't want to risk bricking my TF201.
Thanks!