Develop Bugs

[Q] I'm stuck with Clockworkmod 2.5.0.7 recovery !!

I cannot upgrade to a newer version of Clockworkmod recovery !
I have tried everything, fastboot flash returns failed signature verification, rom manger also cannot update to a newer version.
Also tried Unrevoked but it fails.
the phone is rooted and I have flashed several ROMs in the past without any problem.
Any idea?

Fastboot flash doesn't return verification failed error.
You need to be s-off to change recover using fastboot. Before you do anything, read some tutorials, you need to differentiate among most basic terms.
Sent from my HTC Desire using Tapatalk

erklat said:
Fastboot flash doesn't return verification failed error.
Click to expand...
Click to collapse
It can do if you try to fastboot flash connected in hboot or are s-on

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

I get this error from fastboot
< waiting for device >
sending 'recovery' (3256 KB)... OKAY [ 0.468s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.952s
I have tried to flash clockworkmod 5 and also tried the touch version, but with no luck.
Maybe the S-OFF is messed up, but only if rom manager did something wrong, because last time when I have upgraded the recovery it was from ROM Manager.

Fail on my part...
That seems like there is no device tho. My money is on broken drivers. There is a guide how to do in development so search for it as it works 100%.

unrevoked connects to phone, sends the file to phone then at the end it fails.
I have tried revolutionary for S-OFF the program connects to phone then displays the phone serial number, asks for the key then after I enter the key, the connection is lost.
So I really don't know what to do anymore, and I need a newer recovery since the one which I have does not have options to partition the SD Card and ICS is eating a lot of memory without SDExt.
The phone is ok, it's not broken, I flash every 2-3 days a newer ICS ROM and it works.

why dont you try a different recovery.i have been using ext4 recovery for a while and imo it is way better than cwm....

I use clockworkmod because I have purchased the ROM manager tool and it works with their recovery.
I finally managed to flash a newer clockworkmod recovery and very strange after reboot it has reverted back to the old 2.5.0.7 version !!! At least I was able to partition my sd-ext...
I have tried the boot CD with alpha-rev it freezes in the final stage, but after that I was able to flash the new recovery using the recovery itself, but as I said after reboot the new recovery has gone !
Now I have tried to flash again a newer recovery from ROM manager it says it finished successful, but the recovery still remains 2.5.0.7

evolution_x said:
I use clockworkmod because I have purchased the ROM manager tool and it works with their recovery.
I finally managed to flash a newer clockworkmod recovery and very strange after reboot it has reverted back to the old 2.5.0.7 version !!! At least I was able to partition my sd-ext...
I have tried the boot CD with alpha-rev it freezes in the final stage, but after that I was able to flash the new recovery using the recovery itself, but as I said after reboot the new recovery has gone !
Now I have tried to flash again a newer recovery from ROM manager it says it finished successful, but the recovery still remains 2.5.0.7
Click to expand...
Click to collapse
Because all you are doing is a fake flash. You need to flash it from fastboot in order to stick.
Ditch the Rom manager. That pos app is guilty of more usb bricks than most of us can count.

And how can I flash it from HBOOT ?

evolution_x said:
And how can I flash it from HBOOT ?
Click to expand...
Click to collapse
You need to read ADB for dummies guide to gain knowledge how to set ADB up.
Then you go into hboot by pressing vol- and power button.
Select fastboot.
Download your recovery.img and place it in the same folder your fastboot.exe is, then type in cmd:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot erase cache.
Return to hboot and boot in the recovery.

erklat said:
You need to read ADB for dummies guide to gain knowledge how to set ADB up.
Then you go into hboot by pressing vol- and power button.
Select fastboot.
Download your recovery.img and place it in the same folder your fastboot.exe is, then type in cmd:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot erase cache.
Return to hboot and boot in the recovery.
Click to expand...
Click to collapse
Erklat, thanks for this - I have the same problem.
i have finally got round to get adb, etc, working..and it kinda works, except that when flash a newer version of CWM (v5.0.2) on fastboot it still doesn't work. I tried using the Rom manager, which failed straight away, and I followed your steps above. But still didn't work.
So my story's background:
I rooted my Desire with Unrevoked so I could install ICS (sandvold) - and it has been working beautifully. But now I want to create an ext3 partition and the GParted method is far too complex for me to follow through.
CWM i have installed doens't partition, and so I though I'd update the recovery tool so I could use it to partition.
Any suggestions on what I could do?

KitkatKlub said:
Erklat, thanks for this - I have the same problem.
i have finally got round to get adb, etc, working..and it kinda works, except that when flash a newer version of CWM (v5.0.2) on fastboot it still doesn't work. I tried using the Rom manager, which failed straight away, and I followed your steps above. But still didn't work.
So my story's background:
I rooted my Desire with Unrevoked so I could install ICS (sandvold) - and it has been working beautifully. But now I want to create an ext3 partition and the GParted method is far too complex for me to follow through.
CWM i have installed doens't partition, and so I though I'd update the recovery tool so I could use it to partition.
Any suggestions on what I could do?
Click to expand...
Click to collapse
Do you get an error when you flash a new recovery via fastboot or does it say it successfully flashed the recovery.img file? If you didn't get an error, do you always go to Rom Manager to access recovery? If yes, I say ditch rom manager. Try vol down + power like on erklat's instruction, this time select Recovery. See if the recovery you flashed is booted.
If you are s-off it's better you flash 4ext recovery. It's by far the best recovery you can use for Desire.

stankyou said:
Do you get an error when you flash a new recovery via fastboot or does it say it successfully flashed the recovery.img file? If you didn't get an error, do you always go to Rom Manager to access recovery? If yes, I say ditch rom manager. Try vol down + power like on erklat's instruction, this time select Recovery. See if the recovery you flashed is booted.
If you are s-off it's better you flash 4ext recovery. It's by far the best recovery you can use for Desire.
Click to expand...
Click to collapse
Hey thanks sthankyou.
This is what i get on fastboot:
sending recovery...
OKAY
writing recovery
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.054s
I also tried flashing RA, just to see if it would work (and also heard its better). But nothing. It's quite bizarre.
My phone is not S-OFF - I used the HTC official software and I dont' think it does it - I have no problems in doing it if it will resolve this problem.
I have also tried this flashing using the terminal, Which I found in the Q&A's but i get several error messages, and then finally:
"error writing recovery: No space left on device"
So I uninstalled a couple of apps (freeing some 10mb+) but still the same issue.

As you are not s-off you can't flash recovery, get s-off and flash any you like
Sent from my HTC Sensation XE with Beats Audio using XDA Premium App

KitkatKlub said:
I also tried flashing RA, just to see if it would work (and also heard its better). But nothing. It's quite bizarre.
Click to expand...
Click to collapse
RA has not been maintained for quite some time. 4EXT is probably the best and it's developer is very devoted to his project.
KitkatKlub said:
My phone is not S-OFF - I used the HTC official software and I dont' think it does it - I have no problems in doing it if it will resolve this problem.
Click to expand...
Click to collapse
You made your life a whole lot complicated by using that official tool.
Sent from my HTC Desire using Tapatalk

erklat said:
RA has not been maintained for quite some time. 4EXT is probably the best and it's developer is very devoted to his project.
You made your life a whole lot complicated by using that official tool.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Ah that really sucks. Will I be able to gain S-Off by using AlphaRev? Revolution doesn't work because my HBoot is 1.0.3... and thus not supported.
Once I get it to be S-Off I'll switch to 4EXT.
Thanks, for the help so far!

KitkatKlub said:
Ah that really sucks. Will I be able to gain S-Off by using AlphaRev? Revolution doesn't work because my HBoot is 1.0.3... and thus not supported.
Once I get it to be S-Off I'll switch to 4EXT.
Thanks, for the help so far!
Click to expand...
Click to collapse
theresa way to downgrade. check resources on my guide.

i had the same problem. s-off solved everything.
i had problems with s-off. i had ISC 4.0.3. and i couldn't get it to s-off and i installed some stable rom. cant remember which one, but i'm sure it was on of stable ones. and then tried to s-off again and it was over in few minutes.
and then i flashed recovery with adb

fastboot mode-no boot or recovery img, and can't unlock the bootloader

Hello guys. I've been looking arround for a solution before posting my situation, but I didin't find any help, so I hope you can help me over.
The fact is that my phone is stuck in the bootloader mode. No matter what I do, anytime I turn it on, it goes directly to the bootloader mode and gives me a message that says "fastboot mode-no boot or recovery img" in red. Beside that, my bootloader is locked, and if I try to unlock it, it goes to the unlock screen, it ask me if I want to unlock it, but even if I say "YES", it doesn't unlock. I can't get into recovery mode, so it is impossible to restore any previous backup i've made.
I can get into download mode, but as soon as the odin starts to flash the ROM, the program crashes.
I tried to erase the boot image and the recovery image, but it just says "unknown partition".
Now, why all this did happen?, well I was trying to install the stock firmware that I downloaded from sammobile, and it never installed, the program crashed and my phone got... bricked????
If I could only unlock the bootloader it would be easier, i think.
Any help, please????

not sure if it will work on locked boot loader.... also don't use any tool, plain adb/fast boot
Errors you are getting doesn't say boot loader, but boot and recovery so try it.
Start phone in boot loader mode
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
You can get both files from Google images.

Thanks for responding. I tried to erase the boot and recovery partition but...
This is what i get if i try to erase the boot partition
C:\Users\Casa\Desktop\Android\ADB for NEXUS S>fastboot erase boot
erasing 'boot'...
FAILED (remote: Unknown Partition)
finished. total time: 0.000s
Same thing if I try to erase the recovery image.
And if i try to flash the boot without deleting it, this is what i get:
C:\Users\Casa\Desktop\Android\ADB for NEXUS S>fastboot flash boot boot.img
sending 'boot' (4148 KB)...
OKAY [ 0.406s]
writing 'boot'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.406s
This is really weird, i can't unlock the bootloader using "fastboot oem unlock". As I said before, it takes me to the unlocking screen, asks me if i'm sure, but even if I agree, the boot loeader is still locked. I really don't understand too much thisfar, but I think there's a problem with the partitions.
Any sugestion? I really need some help please...

Well if you're sure fastboot isn't working...
Have you tried ODIN? I think officially signed Odin.tar files can be flashed with a locked bootloader.
As much as Odin freaks me out (too damn finicky)...it can have it's uses.

Well i have already tried Odin, but the flashing process fails, as a fact it doesn't even flash the kernel.
Man, this is really weird. I can't unlock the bootloader, can't erase the boot nor the recovery image because partitions seems to be broken, damaged, lost, or I dunno; I can't flash a rom using Odin...
What can I do? I flashed an md5 file that I downloaded from sammobile (I9250XXKK1 ROM), and tried to flash it, and then my nightmare begun.
I really need some help, guys... I have posted the same problem in three different pages, and I have only gotten two answers, yours.

whats the error that odin gives you?

Have you tried using the Nexus Tool Kit?
Sent from my Galaxy Nexus using xda app-developers app

vikdal said:
Have you tried using the Nexus Tool Kit?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
that will not help him. all the toolkit does is use fastboot.

Zep, thanks for responding. I think that fastboot will not work for me , as you said some lines above, unless I manage to unlock the bootloader. Right now I'm at work (I really hate to work while my phone is bricked at home), so I can't tell you exactly the error I get while using Odin, but if you don't mind, i'll back home after work and i'll teel you the error I'm getting...

ok long shot try this
Get the cwm 6 img in fast boot folder
Fastboot boot cwm.img
Format data cache system
Flash some stable stock like rom or cm9 rc2. See what happens

atifsh said:
ok long shot try this
Get the cwm 6 img in fast boot folder
Fastboot boot cwm.img
Format data cache system
Flash some stable stock like rom or cm9 rc2. See what happens
Click to expand...
Click to collapse
he cant use fastboot.... can people really not read?

Zepius said:
he cant use fastboot.... can people really not read?
Click to expand...
Click to collapse
Huh, you should start reading buddy, he can use it just fine, he can't flash any thing is the issue.

atifsh said:
Huh, you should start reading buddy, he can use it just fine, he can't flash any thing is the issue.
Click to expand...
Click to collapse
really?
apolousm said:
Hello guys. I've been looking arround for a solution before posting my situation, but I didin't find any help, so I hope you can help me over.
The fact is that my phone is stuck in the bootloader mode. No matter what I do, anytime I turn it on, it goes directly to the bootloader mode and gives me a message that says "fastboot mode-no boot or recovery img" in red. Beside that, my bootloader is locked, and if I try to unlock it, it goes to the unlock screen, it ask me if I want to unlock it, but even if I say "YES", it doesn't unlock. I can't get into recovery mode, so it is impossible to restore any previous backup i've made.
Click to expand...
Click to collapse
sure looks like he cant use fastboot to me to flash anything.

stop it man, go see what he writes in response to my first reply.

Zepius said:
really?
sure looks like he cant use fastboot to me to flash anything.
Click to expand...
Click to collapse
Exactly! He can't write, Fastboot works just fine, it even send file ok, but failed to write.

atifsh said:
stop it man, go see what he writes in response to my first reply.
Click to expand...
Click to collapse
its clear you do not understand fastboot.
he cannot flash images with a locked bootloader using fasboot. period.
even in the referenced post you just gave me, it says:
C:\Users\Casa\Desktop\Android\ADB for NEXUS S>fastboot flash boot boot.img
sending 'boot' (4148 KB)...
OKAY [ 0.406s]
writing 'boot'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.406s
Click to expand...
Click to collapse
he mentioned in the first post that he cannot unlock the bootloader for whatever reason.

Zepius said:
its clear you do not understand fastboot.
he cannot flash images with a locked bootloader using fasboot. period.
even in the referenced post you just gave me, it says:
he mentioned in the first post that he cannot unlock the bootloader for whatever reason.
Click to expand...
Click to collapse
stop replying to my posts and if you can help him, you are just making this thread useless.

Hi guys... I think I should explain this ... first of all thanks for trying to help
The fact is that I can't use fastboot (I think). Let me explain: If I try to unlock the bootloader it takes me to the unlock screen, and if I choose yes, the bootloader doesn't unlock.
So, if we consider the fact that I need to unlock the bootloader to use the fastboot, I think there's no chance to use the fastboot command.
I really, really, reaaaaaaally apretiate your help guys, your knowledge will be allways wellcome.
I understand that booth have your point of view, and try to help.
This is the first tmioe I see a prolem like this, I have reading arround and there are no similiar posts, I mean, that the bootloeader can't be unlocked... I found this ------> http://forum.xda-developers.com/showthread.php?t=1067815&page=2 and as saycnahd said "...I feel like I need A to do B, and B to do A....".
Thanls in advice you guys...

the error message that you get from ODIN will be very helpful. we dont need it to fully write a rom, just a couple things so that you can use fastboot to flash anything you need.

Ok, Zep... I get it :good: as soon as I can, I'll post the error... right now i'm seated at work, front of my computer, using my mama's phone right now I just remember that the Odin showed me a Fail message on a big red square on the upper left corner, where it is supposed to appear the progres dialog. I know it sounds pretty basic and useless for now.

Brick - Nothing Works

Hi,
i think My A100 is completly bricked ..The Story:
my Tab was rooted and Unlocked TWRP was installed and running FlexReaper Rom.
1.i decided to reset my A100 completly to stock -> downloaded 014 ICS Rom and Named it update.zip
2. i want to flash this trough recovery when it searches for update.zip files but its not working (dont finding this file)
3. i flashed it in TWRP Recovery after it was done it says no OS installed but i ignored it (*facepalm*) <---I KNOW THIS WAS STUPID !
now the Tablet dont boot Android (stuck at white Acer Logo )and when trying to start revovery its says in Red Letters: Recovery verified failed ...
Bootloader is LOCKED and NOT Rooted
im able to get in Fastboot Mode but the Tablet accept only a very small amount of commads from adb.
my Question : is this Tablet ready to get back to Acer ?
i've tryed unlocking the BootLoader using the Fastboot oem unlock cmd to install the Recovery.img ,but nothing happend only the Screen blanks out for half a second.
and i tryed flash an update.zip from External SDCard but this doens't work as before the Brick.
Anyone have an Idea ? i hope you understand my English and my Problem, i'm from Germany.

Benny164 said:
Hi,
i think My A100 is completly bricked ..The Story:
my Tab was rooted and Unlocked TWRP was installed and running FlexReaper Rom.
1.i decided to reset my A100 completly to stock -> downloaded 014 ICS Rom and Named it update.zip
2. i want to flash this trough recovery when it searches for update.zip files but its not working (dont finding this file)
3. i flashed it in TWRP Recovery after it was done it says no OS installed but i ignored it (*facepalm*) <---I KNOW THIS WAS STUPID !
now the Tablet dont boot Android (stuck at white Acer Logo )and when trying to start revovery its says in Red Letters: Recovery verified failed ...
Bootloader is LOCKED and NOT Rooted
im able to get in Fastboot Mode but the Tablet accept only a very small amount of commads from adb.
my Question : is this Tablet ready to get back to Acer ?
i've tryed unlocking the BootLoader using the Fastboot oem unlock cmd to install the Recovery.img ,but nothing happend only the Screen blanks out for half a second.
and i tryed flash an update.zip from External SDCard but this doens't work as before the Brick.
Anyone have an Idea ? i hope you understand my English and my Problem, i'm from Germany.
Click to expand...
Click to collapse
Its not bricked, its working as intended. You did however lock yourself out. Keep doing the update.zip method, its the only way.
Tapatalked from my Galaxy S II.

I have tried the update.ZIP method with my Sandisk 8GB MicroSD but its not Working ... do you have a update.ZIP for me ?
Galaxy Nexus - Tapatalk

Benny164 said:
I have tried the update.ZIP method with my Sandisk 8GB MicroSD but its not Working ... do you have a update.ZIP for me ?
Galaxy Nexus - Tapatalk
Click to expand...
Click to collapse
It may not even work without at least the stock recovery there, but I would try the 014 in vaches thread with the stock ROMs. One was decrypted and is on a drop box I think, use that one. Triple check you name it update.zip all lower case and turn off hide file extensions to check it only has 1 .zip there.
Sending it to Acer may be your only choice now.
Tapatalked from my Galaxy S II.

Ok ...do you think i musst pay acer or only shipping ?
Galaxy Nexus - Tapatalk

Benny164 said:
Ok ...do you think i musst pay acer or only shipping ?
Galaxy Nexus - Tapatalk
Click to expand...
Click to collapse
You'll have to pay, its user error not a hardware failure. Unless you get really lucky, half the bricks are charged for repairs because it happens on a custom rom and that IS hardware failure.
Custom ROM + Custom recovery = warranty gone
Tapatalked from my Galaxy S II.

at the Moment i have completly Stock Firmware ...i think update.zip wont work tried a couple of Times no Luck.
I have attached a Picture.

I'd have to say with a borked recovery and a locked bootloader, you really can't do anything. You need at least one of them to even attempt anything besides the stock update.zip.
Thanks for your post. I'm running the exact same way. And was wondering how to go completely stock again, if need be. I think maybe flashing back to the stock recovery with zn's script, then applying the .014 stock package. I'm not brave enough to try though. I'm pretty sure a stock update will flash over an unlocked boot loader and root, no problem, but the recovery is the issue. Which your problem seems to reflect.

Yes i think im going to send it to Acer Repair Center
Galaxy Nexus - Tapatalk

You could flash the stock bootloader/recovery through adb,
Like
Fastboot flash recovery.img
Or something,
If your in tested I could look into it.
sent from my A1/500 Iconia slab of awsomeness

Do you have a link for the 014 ics recovery.IMG ?
Galaxy Nexus - Tapatalk

http://forum.xda-developers.com/showthread.php?t=1730093
Since your bootloader is locked I highly doubt it will push any files. But it never hurts to try.

das_webos_transformer said:
You could flash the stock bootloader/recovery through adb,
Like
Fastboot flash recovery.img
Or something,
If your in tested I could look into it.
sent from my A1/500 Iconia slab of awsomeness
Click to expand...
Click to collapse
That would work except two things.
1 stock a100 boot loader has no fastboot access or adb.
2 custom recovery has abd but is locked out by a100 boot loader.
Its stuck, no matter what.
The proper method to restore is simple, but tends to fail, and that's letting it run update.zip on its own.
Stock update will:
Erase cache, format system and data
Install system
Install boot loader
once booted it will flash stock recovery.
Safest method to return to stock:
Edit the stock ROM, remove bootloadr.blob from zip and updater script.
Save and re zip
Flash the stock system
Boot stock system
Root stock system
At this point you will have stock system, but a200 boot loader.
Reboot and check recovery for stock with adb reboot recovery
If its stock recovery you can then use the revert a100 bootloader script to flash back to locked a100.
Its long and annoying, but its the only way to verify each step without getting locked out.
Since he forced it in custom recovery it failed to install system but did install the bootloader, so they got stuck with a locked bootloader that cant be unlocked and a custom ROM and recovery, so locked out.
You could try a hard reset, it might kick start the stock ROM into working with the bootloader...
Tapatalked from my Kindle Fire - Hellfire Jelly CM10

pio_masaki said:
That would work except two things.
1 stock a100 boot loader has no fastboot access or adb.
2 custom recovery has abd but is locked out by a100 boot loader.
Its stuck, no matter what.
The proper method to restore is simple, but tends to fail, and that's letting it run update.zip on its own.
Stock update will:
Erase cache, format system and data
Install system
Install boot loader
once booted it will flash stock recovery.
Safest method to return to stock:
Edit the stock ROM, remove bootloadr.blob from zip and updater script.
Save and re zip
Flash the stock system
Boot stock system
Root stock system
At this point you will have stock system, but a200 boot loader.
Reboot and check recovery for stock with adb reboot recovery
If its stock recovery you can then use the revert a100 bootloader script to flash back to locked a100.
Its long and annoying, but its the only way to verify each step without getting locked out.
Since he forced it in custom recovery it failed to install system but did install the bootloader, so they got stuck with a locked bootloader that cant be unlocked and a custom ROM and recovery, so locked out.
You could try a hard reset, it might kick start the stock ROM into working with the bootloader...
Tapatalked from my Kindle Fire - Hellfire Jelly CM10
Click to expand...
Click to collapse
how i do a Hard Reset ?
when i try flashing the recovery.img its says : unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'

Benny164 said:
how i do a Hard Reset ?
when i try flashing the recovery.img its says : unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
Click to expand...
Click to collapse
Its the one where you power on holding volume + then toggle the lock switch a few times.
fastboot flash recovery recovery.img
Must have recovery where fast boot is run from.
Tapatalked from my Kindle Fire - Hellfire Jelly CM10

pio_masaki said:
Its the one where you power on holding volume + then toggle the lock switch a few times.
fastboot flash recovery recovery.img
Must have recovery where fast boot is run from.
Tapatalked from my Kindle Fire - Hellfire Jelly CM10
Click to expand...
Click to collapse
hard reset works but adb fails : C:\Users\Benny>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'

Benny164 said:
hard reset works but adb fails : C:\Users\Benny>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
Click to expand...
Click to collapse
Well for one, recovery.img must be in the same folder, and that files name used in the command.
Second, fast boot doesn't work on a100 bootloader as I already mentioned.
Tapatalked from my Kindle Fire - Hellfire Jelly CM10

pio_masaki said:
Well for one, recovery.img must be in the same folder, and that files name used in the command.
Second, fast boot doesn't work on a100 bootloader as I already mentioned.
Tapatalked from my Kindle Fire - Hellfire Jelly CM10
Click to expand...
Click to collapse
oh ok ... so do you guys have another Idea ?

Benny164 said:
oh ok ... so do you guys have another Idea ?
Click to expand...
Click to collapse
Does adb work? Not fast boot but adb. Try adb devices
Tapatalked from my Kindle Fire - Hellfire Jelly CM10

No in Fastboot Mode no devices have been Detected in Adb. I think my Android SDK Installation is OK ..my Windows 7 PC Sees my Galaxy Nexus in Toolkit.
Galaxy Nexus - Tapatalk

[Q] error: cannot load 'recovery-clockwork-touch-5.8.4.0-endeavoru'

Hi, I am having a problem with the recovery on my One X (UK - HTC_001). I am still running the stock ICS ROM, was planning on flashing JB ROM, but noticed that the OTA update became available for my device yesterday. I flashed stock recovery (endeavoru_recovery_signed) & proceeded with the OTA update, it got about 1/3 of the way through & switched to the red ! triangle. It rebooted & still works perfectly, so I figured back to plan A & flash a JB ROM. This is where my problems have began...
1. When booted into recovery, it loads a small image (a handset with green circular arrows above it) in the centre of the screen for a few seconds then goes back to the red ! triangle & eventually (after couple of minutes) reboots the handset.
2.When I try to flash CWM Recovery or any other Recovery I get this error....
C:\Users\Danny\Downloads\OneXRoot>fastboot flash recovery recovery-clockwork-tou
ch-5.8.4.0-endeavoru
error: cannot load 'recovery-clockwork-touch-5.8.4.0-endeavoru'
'fastboot erase recovery' comes up with a similar error.
I have also tried flashing CWM Recovery from ROM Manager several times, it appears to download & says flash complete, but when I reboot into recovery it still loads the useless stock recovery.
3. When i flashed the unlock code again i got this error (although the handset is now showing as unlocked)....
C:\Users\Danny\Downloads\OneXRoot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.021s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 16.391s
Other than this the handset works as normal. I am unsure about attempting to flash a JB ROM without having CWM Recovery. Any help / advice would be much appreciated.

try using JBFWTOOL. just do a quick search and you should find it

jinogungon said:
try using JBFWTOOL. just do a quick search and you should find it
Click to expand...
Click to collapse
Awesome, worked first time. Any tips on best custom JB ROM to flash?
Thanks

The error with flashing the unlocktoken is normal, I usually get it. Tried redownloading the clockworkmod img file?

DH0586 said:
Awesome, worked first time. Any tips on best custom JB ROM to flash?
Thanks
Click to expand...
Click to collapse
depends on what you want. for stock android i'd still go for cm10 official and i used it for three months and didn't have any problems. now i'm trying jb sense roms. i tried arhd for a few hours but got irritated of the stock sense look so i flashed renovate (renovate is a jb sense rom that looks a bit like vanilla jb, of course with the help of launchers)

[Q] S-Off but not unlocked, revolutionary instead of locked/unlocked

Hello,
I'm new here, I checked for simular threads and where to put this thread. I hope I did fine..
A few months back I flashed my Desire S without any problems to cyanogenmod 10.
Now I'm trying to do the same for my girlfriends Desire.
I used revolutionary to get s-off and root the phone..
Everything seemed to work out fine, but then it asked me (still in revolutionary) if i wanted to install recovery.
I did that, no errors occured, so I thought, so far, so good...
Than I rebooted in to fastboot to flash cyanogenmod.
I have S-off, but on top of the bootloader screen it says 'revolutionary' instead of unlocked.
I can go to recovery but the recovery doesn't work. Anything I select gives me a black screen with revolutionary logo and it just freezes.
I tried to flash a different recovery, but I get an error everytime I try:
c:\android>fastboot flash recovery recovery.img
sending 'recovery' (5624 KB)...
OKAY [ 0.827s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 0.842s
I tried flashing zip files for SU and I tried flashing a CM zip file, but I get more errors...
I hope someone can help me figure this out...
Thanks!
J.

JanCl said:
Hello,
I'm new here, I checked for simular threads and where to put this thread. I hope I did fine..
A few months back I flashed my Desire S without any problems to cyanogenmod 10.
Now I'm trying to do the same for my girlfriends Desire.
I used revolutionary to get s-off and root the phone..
Everything seemed to work out fine, but then it asked me (still in revolutionary) if i wanted to install recovery.
I did that, no errors occured, so I thought, so far, so good...
Than I rebooted in to fastboot to flash cyanogenmod.
I have S-off, but on top of the bootloader screen it says 'revolutionary' instead of unlocked.
I can go to recovery but the recovery doesn't work. Anything I select gives me a black screen with revolutionary logo and it just freezes.
I tried to flash a different recovery, but I get an error everytime I try:
c:\android>fastboot flash recovery recovery.img
sending 'recovery' (5624 KB)...
OKAY [ 0.827s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 0.842s
I tried flashing zip files for SU and I tried flashing a CM zip file, but I get more errors...
I hope someone can help me figure this out...
Thanks!
J.
Click to expand...
Click to collapse
Try flashing this recovery:
http://forum.xda-developers.com/showthread.php?t=1751258
Follow the instructions in the thread.

That worked like a charm! Thanks a lot, so easy, never thought this could work!
I'm in the new recovery now, so I'll try flashing the new rom.. I'll let you know if it worked..

Installed CM10 and gapps without any problems!
Only thing is.. there seems to be no camera app?
And another thing is the memory left on the internal device is only 17MB.. can't even install facebook app...
Is there any way to improve this?
Thanks!

JanCl said:
Installed CM10 and gapps without any problems!
Only thing is.. there seems to be no camera app?
And another thing is the memory left on the internal device is only 17MB.. can't even install facebook app...
Is there any way to improve this?
Thanks!
Click to expand...
Click to collapse
Check out the partitioning guide in my sig.
Try getting a camera app from the play store.