[Recovery] ClockworkMod 2.5.1.7 offmode charging

drumist

Senior Member
Aug 6, 2010
1,725
543
0
I have have used the Fastboot method and at point where fastboot is writing recovery, I get the message "Failed: (Remote not allowed)"
This is the method you should use to update. (Not Unrevoked.)

Your phone must be at the FASTBOOT screen when you do this. Turn your phone completely off, then hold down volume down button and press power button. Then press power button again while "fastboot" is selected (wait about 15 seconds first). It should say FASTBOOT in red -- that's the screen when you can flash a new recovery.
 
Last edited:

Bob in Northern NJ

Senior Member
Oct 22, 2010
711
309
0
Hopatcong
Yes drumist, not a noob here. I was on the fastboot screen when I did the update routine. Still got the error message. Was on the fastboot screen while running fastboot commands from command prompt in windows 7, got the failure message that way too. I followed all of the steps as outlined for each of the methods to update CWM exactly, and they all failed.
 

drumist

Senior Member
Aug 6, 2010
1,725
543
0
Yes drumist, not a noob here. I was on the fastboot screen when I did the update routine. Still got the error message. Was on the fastboot screen while running fastboot commands from command prompt in windows 7, got the failure message that way too. I followed all of the steps as outlined for each of the methods to update CWM exactly, and they all failed.
Perhaps it's a driver issue. I'd try connecting your phone in fastboot mode again, then going into device manager and updating the driver with the one in this zip file: http://dl4.htc.com/RomCode/Source_and_Binaries/USB_driver_20101122_release.zip

If you already have HTC Sync drivers installed though this shouldn't be necessary.
 

R2D2_SW

Senior Member
Feb 9, 2009
407
63
58
Yes drumist, not a noob here. I was on the fastboot screen when I did the update routine. Still got the error message. Was on the fastboot screen while running fastboot commands from command prompt in windows 7, got the failure message that way too. I followed all of the steps as outlined for each of the methods to update CWM exactly, and they all failed.
Are u trying to flash the entire zip? I also had trouble doing that and kept getting errors. Instead I extracted the recovery.img file from it, placed it in the root of my SD card and flashed it using fastboot. That worked fine and solved the off-mode charging.

Sent from my HTC Aria using XDA App
 

Bob in Northern NJ

Senior Member
Oct 22, 2010
711
309
0
Hopatcong
Thanks for all the suggestions. Again, no, I am not trying to flash a zip file, but the image file copied to my SD root that is contained within the zip, as specified in the direction sets for one of the methods contained in this thread.

I have tried all of the methods contained in this thread, including renaming Recovery.img to LIBEIMG.img, posting on my SD Root, and them booting into HBOOT and then recovery. I thought that would work, as it started to process the img file, and then went straight to the old recovery, no green LED, not charging battery image.

Although in the grand scheme of things this is really not a big deal, it is however frustrating as I am usually able to solve these problems! Keep the suggestions coming!

Again my phone specs are: Android Version 2.2.2
Kernal Version 2.6.32.21 Hoxnet_Liberated_006b [email protected] #25 June 6, 2011 (release 1 from Gene Poole)
Build # 2.20.502.1 CL331188
HBOOT version 1.02.0000
Clockwork Mod Recovery Version 2.5.0.1

Again, using unrevoked says my phone's firmware is too new
Using the Fastboot command method gives me a fail message when writing the image file
Same thing happens when using Android Flasher 1.8
Same thing happens when using Revolutionary method.

I shouldn't have to unroot my phone to a factory ROM, and start from scratch.

Anyone else have success installing this version of Recovery on a previously rooted phone with S-OFF and firmware version 1.02.0000?
 

tpbklake

Senior Member
Aug 1, 2007
3,887
1,700
0
Thanks for all the suggestions. Again, no, I am not trying to flash a zip file, but the image file copied to my SD root that is contained within the zip, as specified in the direction sets for one of the methods contained in this thread.

I have tried all of the methods contained in this thread, including renaming Recovery.img to LIBEIMG.img, posting on my SD Root, and them booting into HBOOT and then recovery. I thought that would work, as it started to process the img file, and then went straight to the old recovery, no green LED, not charging battery image.

Although in the grand scheme of things this is really not a big deal, it is however frustrating as I am usually able to solve these problems! Keep the suggestions coming!

Again my phone specs are: Android Version 2.2.2
Kernal Version 2.6.32.21 Hoxnet_Liberated_006b [email protected] #25 June 6, 2011 (release 1 from Gene Poole)
Build # 2.20.502.1 CL331188
HBOOT version 1.02.0000
Clockwork Mod Recovery Version 2.5.0.1

Again, using unrevoked says my phone's firmware is too new
Using the Fastboot command method gives me a fail message when writing the image file
Same thing happens when using Android Flasher 1.8
Same thing happens when using Revolutionary method.

I shouldn't have to unroot my phone to a factory ROM, and start from scratch.

Anyone else have success installing this version of Recovery on a previously rooted phone with S-OFF and firmware version 1.02.0000?
If you have S-OFF with AlphaRevX/Revolutionary, you HBOOT version should be 6.xx, shouldn't it? If it is still showing HBOOT 1.02, then you don't have the AlphaRevX HBOOT in place which is why the FASTBOOT commands are not working.
 

drumist

Senior Member
Aug 6, 2010
1,725
543
0
Unrevoked will not work with a phone that has updated the HBOOT to 1.02 (or 6.x). The LIBEIMG method won't work because the Clockworkmod recovery img files are not properly signed (only HTC can sign it).

I'd probably suggest trying the fastboot method with a different computer or after booting into a Linux Live CD.
 
Last edited:

Bob in Northern NJ

Senior Member
Oct 22, 2010
711
309
0
Hopatcong
Well....I restored the phone to factory settings, erased the cache and delvik cache, unrooted the phone to a stock ATT 2.1 ROM, had an hboot version of .057 or something like that. Installed the 2.5.1.7 recovery and guess what? It works, but there is no battery icon when charging while the phone is off. However, it does charge, and the LED does turn green when it is done charging.

To that end, I restored to factory stock, wiped cache and delvik cache again, and installed the stock AT&T 2.2.2 ROM that updated my hboot to the 1.02.000 fortunately, S-OFF stayed off. Again, installed 2.5.1.7 recovery successfully, and again, no battery icon while charging, but the LED still turned green when it was done.

So what the heck! At this point I ran the Revolutionary S-OFF update with the hboot upgrade to 6.02.1002 which then allowed me to install CWM Recovery version 4.0.1.4. LOVE the multiple options above and beyond stock CWM Recovery 2.5.0.1!!! And the electric blue text is really cool too! Did an ADVANCED nandroid restore that allowed me to restore everything except the boot, via individual selections. Phone is 100% functional again.

Guess what! No battery icon when charging in off mode, however it DOES charge when in off mode! No green LED indicator when it is 100% charged either. Small concessions to make given the improved options that are available in this version of CWM Recovery.

Having the ability to charge in off mode is important, having the battery icon and a green LED while it is doing so is not, but would have been nice to have. Kudos to those of you that were able to get that, but for now, I am happy!
 

drumist

Senior Member
Aug 6, 2010
1,725
543
0
It's not possible to downgrade your HBOOT version, even with the RUU, so I have to assume you are mistaken about having done so. It IS possible that you actually had 0.57 with S-OFF all along. Can I ask what method you used to originally S-OFF your device? Was it done with the hardware method?

In any case, I'm glad you were able to solve the problem. By the way, s0be compiled CWM 4.0.1.5 for the Aria. Download it here: http://forum.xda-developers.com/showpost.php?p=17120517&postcount=82 . Supposedly this version supports off-mode charging. Let me know how it works out for you if you try it.
 

kaboose01

Senior Member
Dec 12, 2010
169
23
0
29
louisville
It's not possible to downgrade your HBOOT version, even with the RUU, so I have to assume you are mistaken about having done so. It IS possible that you actually had 0.57 with S-OFF all along. Can I ask what method you used to originally S-OFF your device? Was it done with the hardware method?

In any case, I'm glad you were able to solve the problem. By the way, s0be compiled CWM 4.0.1.5 for the Aria. Download it here: http://forum.xda-developers.com/showpost.php?p=17120517&postcount=82 . Supposedly this version supports off-mode charging. Let me know how it works out for you if you try it.
off mode charging works great with that version of cwm.
 

Bob in Northern NJ

Senior Member
Oct 22, 2010
711
309
0
Hopatcong
Downgrading the HBOOT from 1.02.0000 to .057

It's not possible to downgrade your HBOOT version, even with the RUU, so I have to assume you are mistaken about having done so. It IS possible that you actually had 0.57 with S-OFF all along. Can I ask what method you used to originally S-OFF your device? Was it done with the hardware method?



Well I guess it is possible to downgrade the Hboot from 1.02.0000 because that is exactly what happened!


To answer your last question first, I broke my phone's display several months ago, and used the below mentioned ROM flash and RUU steps to restore it to an AT&T original Android 2.1 state to return it for replacement. When I got my replacement phone from AT&T, it was Android 2.2, with Hboot 1.02.0000 and S-ON. I sent it out to ATTN1 and he used a gold card method I believe to turn it to S-OFF, rooted with Recovery 2.5.0.1 As soon as i got the phone back from ATTN1, I installed the Hoxnet 2.2.2 ROM from Gene Poole, and didn't try to do anything else with the phone until a couple days ago when I tried to flash the Recovery to this off mode charge with battery icon. Which led me to to the steps below...

The first downgrade RUU that I performed was from a June 2010 RUU that I still had saved on my laptop. First, I did a factory reset, then I wiped cache and delvik cache. Then I flashed aria_shipped_signed.zip, and then finally HTCAriaOriginalShipROM which was the Android 2.1 RUU from 6/2010. (Maybe this particular HTC ROM also had the capability to flash the Hboot. Or maybe the Aria_Shipped_signed.zip that I initially flashed did. I will be happy to send them both to you so you can take it apart and play with it.) Then I booted to Hboot and saw that my Hboot had been downgraded to .057. I figured that the phone would now allow an install of 2.5.1.7 Recovery with charging, which it did, but still no battery Icon. So next I flashed the Android 2.1 RUU from September, provided in this thread, which upgraded Hboot again to a .6x or maybe it was a .8x. Again, I attempted to install Recovery 2.5.1.7 and again, got the results exactly as I documented them. Finally, I ran the HTC_Aria_for _ATT_Android_2.2_ROM_update RUU, which upgraded my phone to Android 2.2 with Hboot 1.02.0000. Fhttp://forum.xda-developers.com/newreply.php?do=newreply&p=17448103ortunately, the S-OFF remained off. As previously stated, I next flased the Revolutionary S-OFF which upgraded my Hboot to the current 6.x version, and installed recovery 4.x

So in summary, it IS possible to downgrade the Hboot from 1.02.0000 to .057 by flashing the aria_shipped_signed.zip ROM, or running the HTCAriaOriginalShipROM.exe which was the Android 2.1 RUU from 6/2010

I tried to post the files here, but the first one is 115 meg, and the one that contains the RUU is 135 meg.

Lastly the Revolutionary Recover 4.0.1.4 that installed supports off mode charging. It just doesn't turn the LED green or have a battery screen while doing so. I will take a look at the 4.0.1.5 though to see what the difference is.
 

drumist

Senior Member
Aug 6, 2010
1,725
543
0
Thanks for the explanation. I assume because you S-OFF'd via the hardware method (XTC Clip) that it gave you the additional ability to downgrade your HBOOT or something. For people who S-OFF using AlphaRevX or Revolutionary, it wouldn't be possible. I'm not sure why it works differently in those cases, but I'll try to look into it another time.

As for the original ROMs, I actually already have copies of them. But like I said, they wouldn't work for someone who used AlphaRevX/Revolutionary.
 

TDQuiksilver

Senior Member
Jul 25, 2010
197
5
0
It's not possible to downgrade your HBOOT version, even with the RUU, so I have to assume you are mistaken about having done so. It IS possible that you actually had 0.57 with S-OFF all along. Can I ask what method you used to originally S-OFF your device? Was it done with the hardware method?

In any case, I'm glad you were able to solve the problem. By the way, s0be compiled CWM 4.0.1.5 for the Aria. Download it here: http://forum.xda-developers.com/showpost.php?p=17120517&postcount=82 . Supposedly this version supports off-mode charging. Let me know how it works out for you if you try it.
But is there any way to upgrade HBOOT from 0.57 to 1.20? Without using the RUU of course.
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone