Database Users

Pre-Rooted HTC, flashed new custom recovery. Cannot boot into.

Hi Guys,
A while ago I used the flashrec app to flash a custom recovery on my unlocked hero which worked well. I'd been using this for ages to flash custom rooted roms etc onto my device.
Today I decided to update the recovery rom to recovery-ra-hero-v1.6.2.img by terminal emulator. (su, flash_image recovery /sdcard/recovery-ra-hero-v1.6.2.img). This didn't work! When I try and enter recovery mode (hold down HOME whilst booting), it freezes.
I can still get into my rooted rom, and it still appears via adb, but I cannot flash any custom recoveries! When I try to flash via adb I get the wonderful 'downloading 'boot.img'... FAILED (remote: not allow)' error.
Any idea how I can flash the recovery?
Cheers,
Matt

Have you tried using Flashrec again?
btdag said:
5. Download this APK and recovery image and save it to your computer:
http://zenthought.org/content/project/flashrec - FlashRec.apk
http://forum.xda-developers.com/showthread.php?t=561124 - Amon_Ra’s Hero Recovery Image
6. Copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
7. Unplug the phone from the computer once they are downloaded to the SD card.
8. Go to the Market and download ASTRO File Manager or any file manager program if you do not already have one.
9. Open the file manager and find the FlashRec apk file and click it and choose open app manager and then install it.
10. When it is installed click Open. Click on Backup Recovery Image and wait for it to finish. If you get "backup failed" response see the text on the right for more details, if the backup is a success carry on to step 11.
a. Installing the correct HTC ROM
Orange UK Users - Please downgrade your ROM version to 2.73.61.5
Generic Hero Users - Please downgrade to 2.73.405.5, or follow the goldcard method if this doesn't work
T-Mobile UK Users – Please follow the "Goldcard" method below
All Other Users - Please follow the "Goldcard" method below​
11. Once done, click on the empty text box in the FlashRec program and type:
/sdcard/recovery-RA-hero-v1.6.2.img
(replace exact name as new versions come out)
Then click on the Flash Recovery Image button and wait for it to finish.
Click to expand...
Click to collapse

I have yes, forgot to say in OP - sorry! It gives the generic 'flashing failed' message.
I think I've narrowed it down to my running hboot 1.76.0007. Am I right in thinking this version doesn't allow non-htc images to be booted?

I wouldn't know about the hboot stuff sorry...
... But I did once read that an older version of Flashrec worked where the latest did not,... worth a try?
http://code.google.com/p/flashrec/downloads/detail?name=flashrec-1.1.2-20090909.apk

Same error - backup failed: could not run command.
I have a android backup which should include the previous recovery image. Is there any way of restoring that from a terminal in the rom or via adb?

I don't think a Nandroid backup covers the recovery... and I wouldn't know about restoring it through adb.
Only other things I can think of are,...
1... Find out how to update recovery through fastboot? ( I once looked into this but dint get v-far)
2... Run a HTC RUU .exe and start from scratch.
I'd go option 2 for ease, 1 if you want to educate yourself.

I think I've already tried number 1 - "fastboot flash recovery recovery-ra-hero-v1.6.2.img" and got an error: "remote does not allow".
Looks like I'm going to have to go down the RUU route. Hopefully I'll be able to restore a recent nandroid backup once it's complete!
Thanks for your help!

Can't get recovery image on my Hero (rooted)

Hi,
last year, I rooted my Hero, then I bought a Desire. But now my girlfriend would like to use my Hero. So I took my rooted Hero and tried to reflash a new rom, but on one way or another, it keeps failing.
I tried to re-install a new recovery, but accidentaly chose CDMA-hero instead of GSM-hero. Now I can't get into a recovery. When I try to boot the phone, while holding Home button, I only get the HERO-logo... I can get into fastboot though.
I remember I just installed a rooted stock rom: HTC Generic 2.73.405.66. Now I'm reading that this rom results in troubles installing a recovery. I tried EVERYTHING:
- flashrec: can't backup my image, can't flash a recovery (button greyed out)
- tried to downgrade to 2.73.405.5 as suggested on the homepage of flashrec
- tried the guide on modaco: http://android.modaco.com/content/h...ng-the-patched-recovery-image-on-your-device/
My situation is now: Hero is rooted, but my Hero doesn't have a recovery image...and I really need one to flash a custom rom on it...
Can anyone help me please?

Greetings,
Why not try this :
http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
Code:
Copy recovery-RA-hero-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
Change to this on my gsm hero today and easy enough to do via adb.

If above doesn't work. Just downgrade to 2.73.405.5 - use the goldcard method in my guide in my sig. Simple.

Steven_belfast said:
Greetings,
Why not try this :
http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
Code:
Copy recovery-RA-hero-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
Change to this on my gsm hero today and easy enough to do via adb.
Click to expand...
Click to collapse
euhm, the problem is, that I even can't get into recovery since it crashes and keeps showing the HERO-logo... and I already said that I can't downgrade, the process returns an error 'wrong client id' or something... I don't need the goldcard since my Hero is unbranded.

[Q] Cannot get into recovery mode after rooting by using super one click method

Hello all,
I have been using the super one click method to root my HTC Magic Saphhire 32A.
It works well so far albeit need to alter some SU files in the program. Running of terminal emulator with the command prompt SU confirmed that I have the superuser rights.
Now the problem is whenever I use ROM manager to reboot in recovery, the phone restart, HTC logo shows, then the next screen I see is a big asterisk and a phone image, after this I pressed Home + power, the screen manage to switch to Android system recovery utility, BUT with only 3 options:
1) Reboot system now
2) Apply sdcard:update.zip
3) Wipe data/factory reset
And in the end of the screen, there is one line highlighted in red: E: can’t open /cache/recovery/command
After the phone been rebooted, I switched off the phone. And Pressed vol - with power button, same issue happen too with the asterisk sign shows on the screen. After unrooting it, the phone recovery mode are back to normal with the 3 androids in skates appear on the screen.
Have anyone face the same problem? Any ways to sort this out? I am planning to back up my stock ROM, and wanted to try out some cyanogenmod ROM. I tried Googled and read lots of forum post but left without a solution. Any helps are appreciated! Cheers!
p/s: I am a noob in Android OS. XD

I have the legend and these is a process of booting the recovery from there as update.zip. have you tried renaming the ROM update.zip and flashing it from there?
Sent from my HTC Legend using XDA App

I fiddled with the ROm manger setting by choosing "delete recovery prior to flashing", and now it makes it worse.
I selected "reboot in recovery" in ROM manager and the phone reboot, but just stuck at the HTC start up screen.
I plugged in the phone while trying another recovery reboot, and it still stuck at the HTC screen, but with a red line on the top saying "fastboot USB". Gosh I think i am going no way with this...

E:Can’t open /cache/recovery/command
Same fault here mytouch 3g unlocked at&t 32b downgraded too cupcake and tried
getting E:Can’t open /cache/recovery/command

home and power button down still cant get you in recovery? you cant flash any other working rom?
32b myTouch 3g 2.2.1
Cyanogen Nightly 271
Hboot - 1.33.0006
Radio - 2.22.19.26i
Kernel - 2.6.35.9
ADW 1.3.3
ClockworkMod Recovery
Slideit keyboard

Did you flash custom recovery with ROM manager? Or you just rooted the phone with 1 click method?

Sorry for the late reply. I am just back from overseas business trips. I used Clockmod ROM Manager and did a backup, tried reboot in recovery, and the phone rebooted itself but stuck at the HTC logo now.
I can confirm that the phone is rooted with super user permission.
The reason being the phone didn't manage to get into recovery mode might be due to the missing recovery.img in the phone. Pushing the img file to phone through Clockmod didn't work apparently, so I tried command prompt from PC fastboot flash recovery c:\recoveryxyz.img. It failed too with an error remote failed.
I tried using the terminal emulator in the phone and tried pushing the recovery image again and it didn't happen too. Can some one please help? Cheers!

Download ROM manager and you have option that says install custom recovery it will install Clockwork, and you have flash alternative recovery it installs amon ra's recovery i prefer most

Will try it tonight and revert for the result. Cheers!

I have tried flashing alternate ROM through ROM manager and for once it managed to boot into recovery mode. BUT the device hang right after that, I can't select any of the options and have to pull the battery out to force shutdown.
I tried using fastboot flash recovery *.img remotely through my PC while the phone is in fastboot USB mode, and my command prompt stated FAILED (remote: not allow)
Urgh, I think I might have missed something here... Could some one please help? Cheers!
p/s: my objective is to upgrade my stock ROM android 1.5 to cyanogen ROM. Cheers!

I don't know whether this info helps but here goes:
phone info:
sapphire pvt 32A ship s-on H
Hboot- 1.76.0007 (SAPP10000)
CPLD - 12
RADIO - 6.35.07.29
AUG 4 2009

callmeneotheone said:
I have tried flashing alternate ROM through ROM manager and for once it managed to boot into recovery mode. BUT the device hang right after that, I can't select any of the options and have to pull the battery out to force shutdown.
I tried using fastboot flash recovery *.img remotely through my PC while the phone is in fastboot USB mode, and my command prompt stated FAILED (remote: not allow)
Urgh, I think I might have missed something here... Could some one please help? Cheers!
p/s: my objective is to upgrade my stock ROM android 1.5 to cyanogen ROM. Cheers!
Click to expand...
Click to collapse
OK here is the thing did you chose right model of your phone? HTC magic is 32A and mytouch and something else is for 32B you maybe flashed the wrong one?

Thanks WoblyGoblin for taking your time to help. Yes, I have selected the correct phone model. I chose HTC Magic.

Did you install the recovery?
Sent from my HTC Magic using XDA App

I am stuck in trying to install recovery img into the phone. can't boot in recovery mode, tried ROM manager and remote push of recovery img into the phone.
Please refer to the previous post for more info. Cheers!

Ok here is the solution for you use this guide but download this apk and this recovery.
If you dont have 1.5 android but 1.6 download Terminal emulator from market and when you start it type first:
su
flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img

Hello mate,
i just tried the method and I am stuck at FlashRec backup recovery image step.
I clicked on backup recovery image, but there is a command prompt that says:" backup FAILED: Could not run command.
FYI, I am running on Android 1.5. On the edge of giving up rooting and loading a custom ROM now and without a MARKET apps on the phone.

callmeneotheone said:
Hello mate,
i just tried the method and I am stuck at FlashRec backup recovery image step.
I clicked on backup recovery image, but there is a command prompt that says:" backup FAILED: Could not run command.
FYI, I am running on Android 1.5. On the edge of giving up rooting and loading a custom ROM now and without a MARKET apps on the phone.
Click to expand...
Click to collapse
Did you try terminal emulator app?
And commands that i gave you?

yes mate, have tried flash_image recovery command from the terminal app and tries to restart in recovery without any result.
I have did a few research and read up and found out that I am stuck with the south east asia Magic model without the google based support, with no market apps and it is perfected SPL.
Quite upset by it. LOL!

callmeneotheone said:
yes mate, have tried flash_image recovery command from the terminal app and tries to restart in recovery without any result.
I have did a few research and read up and found out that I am stuck with the south east asia Magic model without the google based support, with no market apps and it is perfected SPL.
Quite upset by it. LOL!
Click to expand...
Click to collapse
Try this

Clockwork Recovery is Installed, Won't Load, missing recovery partition.

I'm putting this in General because this is my first time I've actually posted on XDA and I hope someone will move it to wherever it needs to be.
I've rooted my Nexus S a long time back when it was new, originally had some trouble with fastboot hanging on "waiting for device" I want to say trying PDANet fixed my problem then. I'm not foreign to the flashing/rooting process. And I know this is a long post but If you can please read it all it would be appreciated.
My Story:
>ICS was released and while Google said Nexus S would get an official update I saw some on XDA that were promising ports.
>I downloaded We Scream for Ice Cream Beta 9 and installed through Rom Manager
>About a month later I'm fed up with all the force closes and missing features the thread didn't inform me on and went to find another ICS Port.
>Downloaded and about to install through Rom Manager I'm informed that I need Clockwork (strange because I already have it) so within Rom Manager I flashed a new one.
>Install via SD Card and my phone reboots and then instead of loading recovery and doing its stuff I wait at the Bootloader screen. I try entering recovery myself and my phone restarts and again I'm at the bootloader screen.
>At the very bottom of the screen in gray lettering it says Fastboot FAILEDcommand
(As of now it displays the Google Logo with the unlock icon and hangs)
>At this point I decide I' going to flash over clockworkmod myself via adb. This should be the magic formula: via addictive tips (new user, can't include hyperlinks)
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
>Adb gives me an error similar to won't link after the mount/remount command. Also trying to cp the flash image to bin fails to work.
>I boot my phone, open Total Commander and try to copy the flash image myself to the bin folder in my root and it fails
(As of now I get error: device not found)
Then i think alright, maybe it's my drivers. I tried several different drivers from different tutorials because perhaps they are different in some slight way. >Whenever I try a new driver I can pick "adb Composite" "bootloader" or vanilla "adb interface".
>My device appears as "Android Phone" as the first entry in the Device Manager and the icon is a monitor with a small PCB chip in the corner.
>When the divers are completely uninstalled it appears in Other Devices with a yellow exclamation point.
>My understanding is that while it will automatiaclly grab the driver for USB mode, I have to force it to install the bootloader driver for when my phone is in the bootloader screen.
>And USB Debugging has been checked for everything I've done.
>Now i try to use PDANet, first I uninstall the drivers and install PDANet. Message appears saying there is already an Android Driver installed, I choose reinstall, select Samsung, pop says are you sure you want this driver, publisher cannot be confirmed? I click yes, I beleive that happens twice, it installs and then runs. It installed the vanilla "adb interface" driver.
(This is where I'm at now, the Fastboot FAILEDcommand is also gone.)
So now I'm like well there's fastboot, let me see if it recognizes it.
>Fastboot devices: nothing appears
>fastboot flash recovery recovery.img : it hangs on waiting for device.
>Same goes for other commands like OEM unlock.
All the while ROm Manager insists I have clockwork recovery verison 5.x - only it wont load and none of my PC options are recognizing the phone. So I can't flash over a different recovery image, and there;s nothing under alternate recovery in Rom Manager.
And the strangest of them all which may be Rom Manager's problem is that Super User FCs as soon as I try running it. Rom Manager states Super User gives it power at the end of the clockwork recovery flash, however, still says it's successful.
Before this entire thing my phone tried to OTA update to 2.6.7 for Google Wallet and where it would normally respond I got the Android Guy with a box and a yellow exclamation. This is also what I got when I first had some problems rooting months back before I flashed over images and roms. I figured it wouldn't update because it needed the stock recovery image and wasn't compatible updating with clockwork mod (however i think my phone has updated before with this method.)
I wouldn't mind rolling back to my stock deodexed version of Gingerbread at this point because the ROM I have now for ICS NFC and Bluetooth wont work among a slew of problems. And NFC was the major update in 2.6.7 in regards of tap to share and Wallet.
So I either need ADB and Fastboot to recognize my device to try reflashing clockwork and an Entirely new ROM remotely (if that's possible) or get clockwork mod on my phone to open.

More Details
Also when I load the recovery image and it loops back into the bootloader I get the message up top saying I don't have a boot image or recovery image. yet my phone still boots fine.
I really want my phone to work %100 again, can anyone help me?

I didn't read all you wrote, but if you're having trouble getting adb or fastbook to work correctly just use ROM Manager. Even if it says you have it installed, do it a few times. You can also go into settings and check off the format or erase recovery option before flashing.
It will eventually work. Just keep trying it.

Thanks
I know I've read things where flashing several times gets it to work. But I'm wondering if because SuperUser force closes without opening it's unable to give RomManager the permissions needed to complete the flash.
I've tried a few times ever once in a while. Still waiting, but adb will recognize my phone on my guest login but still no fastboot.

What rom you on? Have you tried going into app manager and then clearing data for superuser? Try that and then reflash the recovery a few times from rom manager.
If you're using CM9 alpha 11 or any of the builds by Koush, and superuser FC's from fresh flash. Clear the data, use root explorer or another app that has root access (it will prompt you for root access even if superuser UI won't open) then you can go into /system/app/ and delete or rename superuser.apk.
Once that is done, get the latest one from the market. Soon as it installs, clear the old data from the previous one by using app manager again. Then your superuser app should be working normally.

What's your phone model? (I guess it's I9020T)
When you boot into bootloader, does the fastboot devices command see the device properly?

You should use fastboot to flash your recovery. You probably have driver issues. Check the rooting guide at nexusshacks.com.
Sent from my Nexus S using XDA App

Fixed
Thanks to everyone and heir suggestions.
Eventually I downloaded another set of Fastboot and ADB registered with my phone and I was able to flash a new ClockworkRecoveryMod.
My only explanation is that the two tools where in the same folder this time - that was the only part that was different.
However ROM manager will still tell me I do not have Clockwork on my phone and when it 'flashed' it over it actually breaks my recovery partition all over again.
Thank god for ADB and Fastboot.

Problems installing a custom ROM on Grand Prime Duos (SM-G530H)

I have a Grand Prime Duos (SM-G530H), currently running an Android version 4.4.4 and I wanted to install a custom ROM to have a higher version of Android. (Tried installing LineageOS 17.1 from itexpert.120, but any custom ROM with a higher version of Android would do)
Problem 1: No custom recovery seems to work.
I installed the TWRP app and tried to flash 4 different versions of their recovery images (from twrp-3.7.0_9-0-fortuna3g.img to twrp-3.4.0-0-fortuna3g.img) and all of them resulted in a unless glitched gray recovery screen.
I also tried the CWM app but it fails to download a recovery image for the device, tried looking online for a image file but didn't find one either.
In the end I reverted the recovery to the default one that I had backed up.
Problem 2: ADB works but fastboot doesn't.
I downloaded the ADB tools to try and flash the ROM from my computer instead. The ADB commands work, but when the device enters recovery mode the fastboot commands don't work. ("fastboot devices" doesn't even list the device)
Went to check the drivers. Most tutorials say to open the device manager and look for the phone device with an exclamation mark and update the driver with ones downloaded from the official site. To my surprise the device doesn't show up at all in the device manager (not even with an exclamation mark). Trying to install the drivers anyway says it's already installed.
The Odin software showed the same problems, detects the device when it's on, but doesn't detect it when in recovery mode.
Problem 3: Error when installing directly through the recovery mode options.
This probably wouldn't work for technical reason I'm not aware of, but I went and tried anyway. On the default recovery mode there are 2 options, apply update from ADB and apply update from external storage. Tried both, the first using the command "adb sideload <lineage rom file>" and the second using the ROM file in a SD card. Both begin to unpack and install the file but after a while throw an error "E: failed to verify whole-file signature", then the device boots to the usual OS.
So, is there anything else I can try? any other recovery images or hacks that won't give me the glitched recovery that TWRP had? Or another method to install a ROM without fastboot? Maybe using another file format in problem 3?
OBS: the device is rooted and has no "OEM unlock" options in its settings

delete the samsung usb drivers and install an older version. only way you can flash custom recovery is with odin. only way to flash custom rom is with custom recovery. fastboot and sideload wont work, this isnt a nexus

You think the reason why the custom recovery was glitched is because it was flashed through the TWRP app and not Odin? Seems unlikely. Is there any non-TWRP recovery image for my model you can point me to?