Hi there,
I'm trying to install CWM Touch Recovery, but i'm running into problems.
here's my scenario:
HTC Sensation 4G S-OFF, Rooted. Currently using Virtuous Sensation XE ROM
I downloaded the .img recovery image AND the Windows ADB Files
Installed the Naked ADB Drivers successfully
ADB detects my device. Successfully rebooted into bootloader mode via ADB.
Typed 'fastboot flash recovery recovery.img' and got this:
Code:
sending 'recovery' (4876 KB)... OKAY [ 1.348s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.665s
I thought this was related to rooting and such, so i booted back into Android. I'm Using SuperUser 3.0-beta4 and updated to my binaries to 3.0.3.2, but i still get the same error.
What am i doing wrong? Can you guys help me?
You also can't read the forums rules.
This goes in Q&A
pedrohp said:
Hi there,
I'm trying to install CWM Touch Recovery, but i'm running into problems.
here's my scenario:
HTC Sensation 4G S-OFF, Rooted. Currently using Virtuous Sensation XE ROM
I downloaded the .img recovery image AND the Windows ADB Files
Installed the Naked ADB Drivers successfully
ADB detects my device. Successfully rebooted into bootloader mode via ADB.
Typed 'fastboot flash recovery recovery.img' and got this:
Code:
sending 'recovery' (4876 KB)... OKAY [ 1.348s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.665s
I thought this was related to rooting and such, so i booted back into Android. I'm Using SuperUser 3.0-beta4 and updated to my binaries to 3.0.3.2, but i still get the same error.
What am i doing wrong? Can you guys help me?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1294779
Related
Hello
I installed Clockwork Recovery 3.0.0.5 on my HTC Dream/G1, and I can not revert nor to radream 1.7 nor to clockwork-2.5.0.9-modaco-r2-blade.img...
Could someone help me to restore my system please?
Best regards,
Emmanuel
C:\DREAM\SDK2.1\android-sdk-windows\tools>fastboot flash recovery recovery-clock
work-2.5.0.9-modaco-r2-blade.img
sending 'recovery' (3018 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Firstly this is the wrong section, the fact you put [Q] in the title should have lead you to think maybe this belongs in the Q&A Section?
That said looks to me like you haven't got an S-Off hboot. I'm gonna presume you are running the new 2708 hboot and spl as most are now and that hboot doesn't allow fastboot flashing of recovery. Go to THIS thread and read the first post. Your answer awaits you there, even if you're on another hboot then you'll still find what you need there. Or you could of course use adb to install the new recovery or even terminal emulator, you can find all details in each respective recovery's threads.
manu63970 said:
Hello
I installed Clockwork Recovery 3.0.0.5 on my HTC Dream/G1, and I can not revert nor to radream 1.7 nor to clockwork-2.5.0.9-modaco-r2-blade.img...
Could someone help me to restore my system please?
Best regards,
Emmanuel
C:\DREAM\SDK2.1\android-sdk-windows\tools>fastboot flash recovery recovery-clock
work-2.5.0.9-modaco-r2-blade.img
sending 'recovery' (3018 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
if you can still use it, then reboot in recovery
adb shell mount /sdcard
adb push newrec.img /sdcard/newrec.img
adb shell
flash_image recovery /sdcard/newrec.img
reboot to the new recovery
Hello guys !!!
many thanks for your help !!!
I get back to a stable status, that's wonderfull (it is my professional mobile phone )
Have a good evening
+++
Manu
manu63970 said:
Hello
I installed Clockwork Recovery 3.0.0.5 on my HTC Dream/G1, and I can not revert nor to radream 1.7 nor to clockwork-2.5.0.9-modaco-r2-blade.img...
Could someone help me to restore my system please?
Best regards,
Emmanuel
C:\DREAM\SDK2.1\android-sdk-windows\tools>fastboot flash recovery recovery-clock
work-2.5.0.9-modaco-r2-blade.img
sending 'recovery' (3018 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
boot to recovery
Code:
adb shell mount /sdcard
adb push recovery-clockwork-2.5.0.9-modaco-r2-blade.img /sdcard/
adb shell flash_image recovery /sdcard/recovery-clockwork-2.5.0.9-modaco-r2-blade.img
now reboot to recovery
I unable to reinstall stock recovery (now i have CWM v5.8.3.1 and work only this ver) ?
I try lock and unlock but see error:
sending 'recovery' (9480 KB)... OKAY [ 4.806s]
writing 'recovery'... FAILED (remote: image update error)
I unable to install ruu quit with error "IMG err 156" ?
Sorry I can't help you but this is posted in the wrong section.
Sent from F.E.M.A. Region 9
Moved To Q&A
Please post in the correct section
any solution?
schMATKA said:
I unable to reinstall stock recovery (now i have CWM v5.8.3.1 and work only this ver) ?
I try lock and unlock but see error:
sending 'recovery' (9480 KB)... OKAY [ 4.806s]
writing 'recovery'... FAILED (remote: image update error)
I unable to install ruu quit with error "IMG err 156" ?
Click to expand...
Click to collapse
What stock recovery image are you trying to flash?
Link to it?
baseballfanz said:
What stock recovery image are you trying to flash?
Link to it?
Click to expand...
Click to collapse
I try 3 version extract from ruu and One_S_All-In-One_Kit "Stock flash recovery" and r2-modaco-recovery-clockwork-touch-ville and ville_recovery_signed
Not sure, your bootloader is unlock when you're trying?
and the command
Code:
fastboot flash recovery [COLOR="Red"]recovery.img[/COLOR]
recovery.img has to be spell exactly as the recovery image file you have.
baseballfanz said:
Not sure, your bootloader is unlock when you're trying?
and the command
Code:
fastboot flash recovery [COLOR="Red"]recovery.img[/COLOR]
recovery.img has to be spell exactly as the recovery image file you have.
Click to expand...
Click to collapse
sending 'recovery' (9480 KB)... OKAY [ 4.806s]
writing 'recovery'... FAILED (remote: image update error)
pb
Siret to intercept,
I have an HTC VILLEC2 ( now i know this) few days ago I have tryed to install an custom rom. Because I didn't know that my device is an S3 processor i proceed with unlocking my boot loader. That went well. I have tryed to install CWM. That went also well, but I can't start it.
For te moment the phone runns în stock firmware pretty good but do not allowed me to make any Up Date frm HTC Updat server.
The question is, it is possibe to reinstall the original CWM. Also where can I download it?
THX FOR ALL SUPPORT IN ADVANCE.
I have an unlocked, rooted 300T with JB which I flashed to 10.4.2.13 using the existing installation of TWRP which has now disappeared when booting+Vol Down. I do not seem to be able to re-install TWRP using fast boot as I get this message.
Code:
C:\Users\Mike\Desktop\Fastboot>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)... OKAY [ 2.058s]
writing 'recovery'... FAILED (status read failed (Too many links))
finished. total time: 2.061s
I have searched extensively and cannot find a similar issue, but without TWRP I cannot then flash a custom ROM...:crying:
Seahorse said:
I have an unlocked, rooted 300T with JB which I flashed to 10.4.2.13 using the existing installation of TWRP which has now disappeared when booting+Vol Down. I do not seem to be able to re-install TWRP using fast boot as I get this message.
Code:
C:\Users\Mike\Desktop\Fastboot>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)... OKAY [ 2.058s]
writing 'recovery'... FAILED (status read failed (Too many links))
finished. total time: 2.061s
I have searched extensively and cannot find a similar issue, but without TWRP I cannot then flash a custom ROM...:crying:
Click to expand...
Click to collapse
Are you installing the jb compatible twrp? what happens when you try and boot recovery?
Sent from my SGH-I727 using xda app-developers app
I have downloaded the 2.2.2 jb blob from here. When I boot into recovery & select RCK I get an android on his back with an exclamation mark in his stomach.
Seahorse said:
I have downloaded the 2.2.2 jb blob from here. When I boot into recovery & select RCK I get an android on his back with an exclamation mark in his stomach.
Click to expand...
Click to collapse
When you used twrp to flash stock it includes recovery which overwrites twrp. Go back to the instructions to fastboot twrp, do so and you should be good.
Good Luck!
Try a new download of twrp!
Reboot your pc, only plugin your asus and no other device, retry fastboot.
Forgot, if on dock remove from dock reboot pc and asus and try again.
Clearing cache maybe? Just a shot in the dark, never seen this one. I can tell you I flashed ota v13 and it blew away my recovery but I was able to get it back easily.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
After following numerous google links - too many links fastboot, I found one resolution. Another device used on pc and usb drivers installed since last use of unit giving links error. Resolution was remove offending drivers, reboot pc and profit.
Good Luck!
I'm having a bit of a different problem. I have flashed twrp 2.2.2 several times and each time it says okay but it isn't updating it. I still have 2.2.1.5 installed.
Code I'm using...
adb reboot bootloader
fastboot -i 0x0B05 flash recovery tf300t-jb.blob
Click to expand...
Click to collapse
It goes through the install and says OKAY at the end yet it doesn't actually update the recovery blob.
Blew away cache, used fastboot again on twrp.blob and got same install fail error message. However, on power on + vol down RCK now works with TWRP, which is kind of odd, but there you go. Thanks for all the suggestions...
glad you got it fixed
SITH16 said:
I'm having a bit of a different problem. I have flashed twrp 2.2.2 several times and each time it says okay but it isn't updating it. I still have 2.2.1.5 installed.
Code I'm using...
Quote:
adb reboot bootloader
fastboot -i 0x0B05 flash recovery tf300t-jb.blob
It goes through the install and says OKAY at the end yet it doesn't actually update the recovery blob.
Click to expand...
Click to collapse
Three things come to mind.
1. Try to flash as twrp directions show; without adb reboot bootloader.
2. Verify you are trying to flash the proper version for your bootloader; ics or jb.
3. If the above two items fail redownload proper version for your boot loader and try again.
Note: The twrp page also shows how to flash with adb!
Good Luck!
Terminal Emulator is an easier way to flash TWRP imo. But hey.
babymatteo said:
Terminal Emulator is an easier way to flash TWRP imo. But hey.
Click to expand...
Click to collapse
Terminal method worked. Thanks everyone for helping me out.
TWRP Install Fail
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?
BadWolf428 said:
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?
Click to expand...
Click to collapse
this is the tf300t forum. Make sure you are installing a tf700t TWRP
cmendonc2 said:
this is the tf300t forum. Make sure you are installing a tf700t TWRP
Click to expand...
Click to collapse
I noticed that after I hit reply. I was using all of the correct TF700t TWRP and whatnot. I found this in a google search because it was similar to my issue. It turned out that even though I thought I had unlocked my device, it did not unlock. I fixed that and now I am all set.
BadWolf428 said:
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?
Click to expand...
Click to collapse
The warning invalid state normally applies to the bootloader being locked make sure your bootloader is unlocked.
Sent from my Nexus 5 using Tapatalk
Got a phone from a friend. Said it was bricked.
In bootloader:
*** unlocked ***
doubleshot pvt ship s-on rl
hboot-1.45.0013
microp-0353
emmc-boot
When click recovery, get 3 skateboarders and back to menu.
Tried to load a recovery:
C:\Android>fastboot flash recovery recovery-clockwork-5.0.2.7-doubleshot.img
sending 'recovery' (4754 KB)...
OKAY [ 0.888s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.348s
Received above error, should I perform another step first?
Somehow finally got cwm 5.0.2.7 into recovery.
Found this thread and did basically the same thing.
http://forum.xda-developers.com/showthread.php?t=2665472
Downloaded cm-9-1-(3-0-97)-r13.zip
Checked md5sum
Extract contents of ROM to PC(boot.img)
Put the full zip and gapps on SD card
Boot to recovery
Wipe data/factory reset, wipe cache partition
Flash ROM cm-9-1-(3-0-97)-r13.zip. Install successful.
Pulled battery, boot direct to bootloader
Flash kernel with fastboot <<<<< here I get the below error
fastboot flash boot boot.img
sending 'boot' (16384 KB)...
OKAY [ 2.624s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 4.085s
Any suggestions?
Try miktouch or another stock based ROM so you don't need to flash kernel
Sent from my Nexus 4 using XDA Premium 4 mobile app
Is there a particular miktouch I should try? Would the below link be good to try?(for some reason having hard time finding)
"cx.com/mycx/share/jzvMU-erEeGfjBICOBql1A/MikTouch-0.7-signed.zip"
And just follow the steps and flash it vs cm9, correct?
Any stock based ROM is easier to flash as you don't need to flash the kernel afterwards through fastboot. Also cm9 is one of the few Roms I have seen issues for people when trying to flash, granted it is one of the better Roms out there, but right now you are just trying to get this working again, so stick with easy.
And I would think that's a good link, but didn't check
Sent from my Nexus 7 using XDA Premium 4 mobile app
installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.
any suggestions on trying something else?
waynebattle said:
installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.
Click to expand...
Click to collapse
What ROM were you on before? If its non stock, I would try to fastboot flash the boot.img
Sent from my Nexus 4 using Tapatalk
unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?
waynebattle said:
unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?
Click to expand...
Click to collapse
On some of my Linux distros I would have to use fastboot flash with a ./ before it would work.
./fasboot flash boot boot.Img
I have no idea why it was like this but it helped me a fee times on the DS. If its anything else I'd have no idea, I haven't messed with this since I sent mine off to a XDA user here.
Sent from my Nexus 4 using Tapatalk
Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?
waynebattle said:
Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?
Click to expand...
Click to collapse
You said you are able to get into recovery? Try factory resetting there
Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.
abe5 said:
Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.
Click to expand...
Click to collapse
dont you need to be locked to do this? i've tried "fastboot oem lock" but it has an error about too many links and the phone shuts off and it shows that it is still unlocked. I tried the PG59IMG.zip anyway and it said parsing and went right back to hboot within a second.. Flashed miktouch rom. Restarted phone, still just stuck on logo screen.
What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.
abe5 said:
What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.
Click to expand...
Click to collapse
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?
waynebattle said:
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?
Click to expand...
Click to collapse
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6
abe5 said:
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6
Click to expand...
Click to collapse
No luck, (md5 check sum verified) get error when try to flash it:
C:\Android>fastboot flash recovery cwm.img
sending 'recovery' (6338 KB)...
OKAY [ 1.285s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.745s
Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When you say adb working from within recovery, I am able to mount usb storage within recovery and then on pc I can do 'adb devices' and I see the device, is that what you are referring to? Thanks.
Got desire HD which has a faulty firmware and most of the process gets killed and im unable to do anything like installing new app, Bluetooth connection or accessing memory through PC.
However, it does lets me connect to the PC
Details of DHD:
2.3.3
S-OFF
Stock recovery
Background:
Since I’m unable to install any app in it, I got hold of iRoot software and it says rooted successfully
now I got few recoveries
Problem:
adb reboot bootloader .. Goes to fastmode usb
fastboot flash recovery recovery.img … CMD says everything went successful
sending 'recovery' (4002 KB)... OKAY [ 0.777s]
writing 'recovery'... OKAY [ 1.372s]
finished. total time: 2.150s
fastboot reboot
Now it reboots and starts again in android. When I go back to bootloader screen it is still the same no custom recovery installed?
I also have tried going to 'recovery' option in bootloader after flashing recovery the phones gets stuck on HTC green logo and white background
hashims said:
Got desire HD which has a faulty firmware and most of the process gets killed and im unable to do anything like installing new app, Bluetooth connection or accessing memory through PC.
However, it does lets me connect to the PC
Details of DHD:
2.3.3
S-OFF
Stock recovery
Background:
Since I’m unable to install any app in it, I got hold of iRoot software and it says rooted successfully
now I got few recoveries
Problem:
adb reboot bootloader .. Goes to fastmode usb
fastboot flash recovery recovery.img … CMD says everything went successful
sending 'recovery' (4002 KB)... OKAY [ 0.777s]
writing 'recovery'... OKAY [ 1.372s]
finished. total time: 2.150s
fastboot reboot
Now it reboots and starts again in android. When I go back to bootloader screen it is still the same no custom recovery installed?
I also have tried going to 'recovery' option in bootloader after flashing recovery the phones gets stuck on HTC green logo and white background
Click to expand...
Click to collapse
I think when you flash a recovery and you boot into android, android overwrites the custom recovery with the stock one. Try to boot to recovery without booting in android.