C:\Users\Sveinus>fastboot flash recovery C:\recovery.img
sending 'recovery' (1250 KB)... OKAY [ 0.189s]
writing 'recovery'... FAILED (remote: image error! (BootMagic check
fail))
finished. total time: 0.190s
Everytime I try, I just get this error.
Use rommanger app from the market and it will flash it in a jiffy!
I tried to flash it with enrEVOked again, and I thought it was finished when it said "running root." so I disconnected the phone. After that I've been unable to start recovery mode, and than I tried method II here; http://forum.xda-developers.com/showthread.php?t=929628
and I'm stil unable to enter recovery :S
purevower said:
Use rommanger app from the market and it will flash it in a jiffy!
Click to expand...
Click to collapse
^ This.
Be careful you choose the right device when you flash from ROM manager though - it's easy to get wrong
When I try "Flash ClockworkMod Recovery", I'll have to confirm what phone I use, and then it just says "Successfully downloaded ClockworkMod recovery!", and nothing more.
Related
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.
Ok good people of XDA, need some help on this one. Did a lot of reading and trying but can not figure this out. I was wiping my phone through TWRP, and without looking wiped /system. Naturally my phone is now getting stuck in HTC spplash screen, I can still get into recovery, but then the when trying to mount USB strage under TWRP was getting unknown format, so like an idiot I formatted FAT32 and anything I put on there recovery does not see. What is the file format for the storage? I also can not RUU the via fastboot as I gives me the following
C:\\Android>fastboot flash boot boot_signed.img
sending 'boot' (6236 KB)... OKAY [ 1.885s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.092s
C:\Android>fastboot flash system system.img
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
Probably because it cant read something. I did lock the boot-loader before doing it. Also, noticed the ADB commands are not working in the power off state either.
What do you guys think?
romka7 said:
Ok good people of XDA, need some help on this one. Did a lot of reading and trying but can not figure this out. I was wiping my phone through TWRP, and without looking wiped /system. Naturally my phone is now getting stuck in HTC spplash screen, I can still get into recovery, but then the when trying to mount USB strage under TWRP was getting unknown format, so like an idiot I formatted FAT32 and anything I put on there recovery does not see. What is the file format for the storage? I also can not RUU the via fastboot as I gives me the following
C:\\Android>fastboot flash boot boot_signed.img
sending 'boot' (6236 KB)... OKAY [ 1.885s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.092s
C:\Android>fastboot flash system system.img
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
Probably because it cant read something. I did lock the boot-loader before doing it. Also, noticed the ADB commands are not working in the power off state either.
What do you guys think?
Click to expand...
Click to collapse
If I remember right, it's actually EXT4 and android uses FUSE to make it look like a FAT32 partition to a connected machine.
I would have suggested RUU, but it seems like that's not an option for you. Good luck with your phone, man.
If worst comes to worst just go to att and say it broke randomly, I don't think they can tell it's rooted if you messed it up that badly
Sent from my One X using xda premium
Did you try just running the RUU ?
Ok, I beat it to death.... got it working. Somewhere in my trial and error process I ended up flashing to CWM recovery, which did nothing new for me, then I pushed TWRP again but the 2.1.8, was on 2.2 when the problem started.... all of the sudden ADB started working, not sure what happened on the newer version. I still did not see my SDcard, but I was able to push a version of cleanrom to the system partition. The install did not go, but the the process it formated the sdcard to the proper format.... or it restored some setting. I was then able to mount SD in TWRP and installed newest version of CleanRom.. All good now.... its all a learning process I guess
Hey guys,
my bootloader is unlocked - so far, so good. however though, when I want to flash cwm, I'm getting this result:
C:\xyz>fastboot flash recovery cwmrecovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6632 KB)...
OKAY [ 0.558s]
writing 'recovery'...
OKAY [ 1.838s]
finished. total time: 2.397s
so it looks successful. But I still have the stock recovery. When I'm trying the rom manager from the playstore alternatively, I'm getting an error right aways after the cwm download (looks as if nothing happened in between). Error message is simply "An error occurred while flashing your recovery"
Any suggestions?
Thanks!
After you fastboot flash recovery, IMMEDIATELY reboot to recovery. Do not reboot to Android.
Take a backup. Then boot to Android... should stick.
Yeah, I learned that the hard way....
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Yeah, I learned that the hard way....
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Weird! I had the similar issue as described above. I'm able to successfully flash the CWM flash to the SPH-710 for me. However, can't boot INITIALLY to the CWM boot; It's able to successfully go into normal boot; But Volume-UP, Center button Power button, just blinks the custom boot screen once then the screen becomes blank for some time.
Can't get out of the Stock ROM boot up to CWM;
When I try flash a recovery image using the command prompt I receive the following error:
fastboot flash recovery recovery.img
sending 'recovery' (8956 KB)...
OKAY [ 1.105s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.355s
How to resolve error?
Akio8 said:
When I try flash a recovery image using the command prompt I receive the following error:
fastboot flash recovery recovery.img
sending 'recovery' (8956 KB)...
OKAY [ 1.105s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.355s
How to resolve error?
Click to expand...
Click to collapse
Have you successfully unlocked the bootloader ?
Which recovery image are you trying to flash ?
htc_one_mini_m4 said:
Have you successfully unlocked the bootloader ?
Which recovery image are you trying to flash ?
Click to expand...
Click to collapse
Yes the bootloader is unlocked. I'm trying to flash philz-touch-6.26.1-m4.img
Akio8 said:
Yes the bootloader is unlocked. I'm trying to flash philz-touch-6.26.1-m4.img
Click to expand...
Click to collapse
Can you try flashing TWRP 2.7.1.1 instead ? ( Just to see if it's a general issue or something related to your image file )
htc_one_mini_m4 said:
Can you try flashing TWRP 2.7.1.1 instead ? ( Just to see if it's a general issue or something related to your image file )
Click to expand...
Click to collapse
It's a general issue it doesn't matter what image I try to flash
Akio8 said:
It's a general issue it doesn't matter what image I try to flash
Click to expand...
Click to collapse
So, you're stuck with the stock recovery or with a custom one ?
I'd try to install an unsecured kernel + ROM like Jmz's and try flashing a new recovery after that.
Not sure if it would work, just my thoughts and gut says that it might
Hi,
I'm trying to root my Moto G. Was able to unlock it but can't flash recovery or boot superboot with fastboot.
On trying to push twrp with: fastboot flash recovery twrp.img
I get the error:
target reported max download size of 536870912 bytes
sending 'recovery' (8090 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.021s
On trying to boot superboot with: fastboot boot boot.superboot.img
Iget the error:
downloading 'boot.img' ...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s
I can't seem to find a solution online, does someone know how to fix these errors?
Uncannytable said:
Hi,
I'm trying to root my Moto G. Was able to unlock it but can't flash recovery or boot superboot with fastboot.
On trying to push twrp with: fastboot flash recovery twrp.img
I get the error:
target reported max download size of 536870912 bytes
sending 'recovery' (8090 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.021s
On trying to boot superboot with: fastboot boot boot.superboot.img
Iget the error:
downloading 'boot.img' ...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s
I can't seem to find a solution online, does someone know how to fix these errors?
Click to expand...
Click to collapse
just install flashify from the playstore and flash a recovery from there its very easy and i think a large number of people had the same problem anyhow thats how i fixed it after further reading in xda cheers,martin
I am actually a fan of rooting without changing the recovery
just use
fastboot boot YourRecovery.img
Click to expand...
Click to collapse
and then flash e.g. latest supersu zip http://download.chainfire.eu/supersu you can even do this by adb sideload in CWM (for the recovery i used CWMrecovery)
i like this method because it will leave your recovery untouched and just root :highfive:
Why dont you flash just Philz Touch recovery? Then go to recovery option on Fastboot mode, once Philz has booted, touch REBOOT SYSTEM, then the recovery will tell you "Your device is not rooted or SU is missing, do you want to apply SU?" Then scroll to YES option and phone will reboot.. DONE, rooted! Now go to Play Store and grab SuperSU app.. Then you can flash to stock recovery....
All I had to do was change the usb port. Now everything is working fine.
martindar said:
just install flashify from the playstore and flash a recovery from there its very easy and i think a large number of people had the same problem anyhow thats how i fixed it after further reading in xda cheers,martin
Click to expand...
Click to collapse
The OP is trying to root his device. AFAIK Flashify requires the device to be rooted to work. What am I missing?