Trying to change to latest recovery.img on rooted phone.

[Guest G2 USER]

Hi,

I'm trying to load up the latest Amon Ra 1.6.2 blue recovery image using the following adb commands...

adb shell reboot bootloader

fastboot boot recovery-RA-hero-v1.6.2-blue.img

adb shell mount /sdcard

adb push recovery-RA-hero-v1.6.2-blue.img /sdcard/recovery-RA-hero-v1.6.2-blue.img

adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2-blue.img

I get into fast boot when i run the first line as expected but when i try....

fastboot boot recovery-RA-hero-v1.6.2-blue.img -- result is -- downloading 'boot.img'... FAILED (Remote: not allow)

If i try adb shell mount /sdcard -- result is -- error: device not found

Can anyone tell me what the problem is and how to fix this?

I can get into adb shell automatically goes into SU command - # fine but trying to re-flash recovery isn't working and would like to know why.

Phone is rooted and using modaco 3.2 (superuser and su as installed with modaco rom)

Thanks.

Edited April 16, 2010 by G2 USER

[Guest sinnadyr]

why fastboot?

I only used adb to flash the recovery image and it worked just fine. Dont remember the commands atm but it should be here in the forums ;)

[Guest Incomer]

use this:

via adb -> Requires a custom recovery (with test-keys) like Cyanogen's v1.4 or my previous recovery

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

[Guest G2 USER]

Thanks for the replys!!

Managed to upgrade using the boot to custom recovery then #flash_image recovery..... but still puzzled as to why i get the "remote not allow" when in fastboot?

Any idea's?

[Guest crawler9]

Thanks for the replys!!

Managed to upgrade using the boot to custom recovery then #flash_image recovery..... but still puzzled as to why i get the "remote not allow" when in fastboot?

Any idea's?

I'm not 100% sure about how it works on that phone, but I would guess it's the same with all Android phones. If someone else knows better, please correct me but here's my idea:

OP tried: fastboot boot recovery-RA-hero-v1.6.2-blue.img

to flash a recovery image shouldn't it be

fastboot flash recovery *.img or in this exact case fastboot flash recovery recovery-RA-hero-v1.6.2-blue.img

also it should be noted that adb cannot access the phone while it is in the bootloader mode. It can only be used if the phone is booted up and USB Debugging is on (at least on the Nexus) or in some recovery images.

Edited April 16, 2010 by crawler9

[Guest shenshang]

I'm not 100% sure about how it works on that phone, but I would guess it's the same with all Android phones. If someone else knows better, please correct me but here's my idea:

OP tried: fastboot boot recovery-RA-hero-v1.6.2-blue.img

to flash a recovery image shouldn't it be

fastboot flash recovery *.img or in this exact case fastboot flash recovery recovery-RA-hero-v1.6.2-blue.img

also it should be noted that adb cannot access the phone while it is in the bootloader mode. It can only be used if the phone is booted up and USB Debugging is on (at least on the Nexus) or in some recovery images.

Yeah, it should.

fastboot boot recovery *.img <== only boots the recovery image, it doesnt flash it

replace "boot" with "flash" and it does get flashed. if you wanna erase it, put "erase" instead of "boot"

[Guest xTc is loVe]

1.download ANY terminal emulator from the market.

2.Type in the emulator : su and give it root access.

3.Reload the Terminal

4.type in: su

next : flash_image recovery /sdcard/recovery-RA-hero-v1.6.2-blue.img or sh flash_image recovery /sdcard/recovery-RA-hero-v1.6.2-blue.img

one of thes should work perfectly =) have fun

Edited April 17, 2010 by xTc is loVe

[Guest G2 USER]

Thanks all for the replys, appreciated!!! ;)

Ok the first post command lines where taken form Amon RA's post on xda for using fastboot.

I tried the suggested fastboot flash instead of booting the rom (fastboot flash recovery *.img)...

Result -- sending 'recovery' (3862KB)... FAILED (remote: not allow) ;)

Using terminal app works fine.

So again Fastbboot wont allow remote access, any idea's?

Could this be the hboot version?

details......

HERO CVT SHIP S-ON

HBOOT-176.0007 (HERO10000)

MICROP-010f

TOUCHPANEL-SYN0104

RADIO-6.35.09.26

(Side note. I also looked at Flashrec, which i used as part of rooting the phone but no version will work with Madaco 3.2, which someone else mentioned on the forums)

THX.

Edited April 17, 2010 by G2 USER

[Guest]

Thanks all for the replys, appreciated!!! ;)

Ok the first post command lines where taken form Amon RA's post on xda for using fastboot.

I tried the suggested fastboot flash instead of booting the rom (fastboot flash recovery *.img)...

Result -- sending 'recovery' (3862KB)... FAILED (remote: not allow) ;)

Using terminal app works fine.

So again Fastbboot wont allow remote access, any idea's?

Could this be the hboot version?

details......

HERO CVT SHIP S-ON

HBOOT-176.0007 (HERO10000)

MICROP-010f

TOUCHPANEL-SYN0104

RADIO-6.35.09.26

(Side note. I also looked at Flashrec, which i used as part of rooting the phone but no version will work with Madaco 3.2, which someone else mentioned on the forums)

THX.

T-mobile made a change to the SPL to prevent fastboot from remotely flashing the phone.

Either work the recovery update via the USB cable and the SD card, or update to the unlocked SPL:

http://android.modaco.com/content/htc-hero...l-for-gsm-hero/

Flashrec is quite pointless on the more recent stock ROMs on T-mobile, since I suspect its some protection measure they installed. Its probably useless on the Modaco ROM since you can do a better job via ADB.

[Guest G2 USER]

T-mobile made a change to the SPL to prevent fastboot from remotely flashing the phone.

Either work the recovery update via the USB cable and the SD card, or update to the unlocked SPL:

http://android.modaco.com/content/htc-hero...l-for-gsm-hero/

Flashrec is quite pointless on the more recent stock ROMs on T-mobile, since I suspect its some protection measure they installed. Its probably useless on the Modaco ROM since you can do a better job via ADB.

Hi,

Thanks for the reply!!

Yes you are right, i found out that i was on a locked spl so flashed to Paul engineering spl and all works!

Just flashed a new full 2.1 rom called sensehero 2.1 ( ported from the recent hero CDMA android 2.1 release ), which stickman89 has just released a few days ago and its superb!!