Develop Bugs

[Q] Clockwork mod won't flash Rom, won't update

According to ROM Mgr, I have successfully flashed CWM 3.0.0.8 but when I boot into Recovery, it shows 2.5.0.1. Also when I try to flash a new ROM with ROM Mgr, I get error msg saying to check log. The only way I can flash a new ROM is to do the Update.zip thing. Nandroid seems to work ok. What am I doing wrong?

Sometimes you have to flash it twice to get it to take. Dunno why.
hope that helps.

I've tried that several times. ROM Mgr says that 3.0.0.8 has successfully flashed but Recovery says otherwise. Has to be related to the fact that ROM Mgr will not flash any different ROMs. Flashing with Update.zip doesn't give the option to wipe before reflash which worries me a little. How drastic will I have to get to fix this?

budman 53 said:
I've tried that several times. ROM Mgr says that 3.0.0.8 has successfully flashed but Recovery says otherwise. Has to be related to the fact that ROM Mgr will not flash any different ROMs. Flashing with Update.zip doesn't give the option to wipe before reflash which worries me a little. How drastic will I have to get to fix this?
Click to expand...
Click to collapse
depending on what your flashing needs are, you could try to go to rom manager and flash alternate recovery ra_gnm v1.8.1 I have used it and it worked fine for me. not sure if it supports the new scripting for clockwork after 3.0.0.XX. you could also try flashing the alternate recovery and then flash clockwork back right away see if it sticks that way.

I was having the same problem i would flash in RM and when I booted the phone it will still have the 2.5 version of CW.. but Some one here in the forum gave me this file and it work just fine.... dont flash it in recovery just put it your root sdcard and power off and them power on + Vol - and you should have 3.0.8 hope it works....

I have the exact same problem as described above.... I tried the PB31IMG.zip and had no luck any other suggestions ?

bwickes1 said:
I have the exact same problem as described above.... I tried the PB31IMG.zip and had no luck any other suggestions ?
Click to expand...
Click to collapse
I tried this. No luck. I also tried flashing several alternate CWMs. They all show as being successfully flashed in RM, but when I boot to recovery, 2.5.0.1 still prevails. ???????

budman 53 said:
I tried this. No luck. I also tried flashing several alternate CWMs. They all show as being successfully flashed in RM, but when I boot to recovery, 2.5.0.1 still prevails. ???????
Click to expand...
Click to collapse
See this thread:
http://forum.xda-developers.com/showthread.php?t=970032
The OP contains lots of advice for getting 3.0.0.8 installed and working properly.
Perhaps most importantly, make sure "Erase recovery" is checked in Rom Manager settings.

bwickes1 said:
I have the exact same problem as described above.... I tried the PB31IMG.zip and had no luck any other suggestions ?
Click to expand...
Click to collapse
When flashing in hoot your SD card has to be formatted fat32 or it won't work..... check and see if your formatted correctly..... if not back up your files on your pc then reformat and it should work
Sent from my Incredible using XDA App

Don't know whether you solved your problem in the last 30 days, but my suggestion is DON'T USE ROM MANAGER TO UPDATE CLOCKWORK.
I downloaded the most recent CWM from Doug Piston's site, renamed it to PB31IMG.zip and put it in the root directory of my SD card, booted into Bootloader, when it recognized the update file, I ran the update and got to 3.0.0.8.
Meanwhile, ROM Manager still reports that I have an earlier version of CWM, and I've even gone so far as to update the .settings file to correct it, but ROM Manager blithely goes about its business ignorant of the real recovery.
Since my ROM isn't supported by ROM Manager, I figure I can just leave ROM Manager alone ---- I've never trusted backups run through it anyway; I always run Nandroids from Recovery.

tdiman said:
See this thread:
http://forum.xda-developers.com/showthread.php?t=970032
The OP contains lots of advice for getting 3.0.0.8 installed and working properly.
Perhaps most importantly, make sure "Erase recovery" is checked in Rom Manager settings.
Click to expand...
Click to collapse
I love you!!!

Wildfire ROM update - backup questions

Hi everyone,
I'm using a HTC Wildfire and am considering changing from stock (HTC non-branded) to CyanogenMod for a number of minor reasons. Could anyone just confirm that I got a few points right before I get started:
- Recovery is totally independent from the ROM itself, right? So I can flash ClockWorkMod Recovery only, continue to use the stock ROM, but have the additional features of ClockWorkMod available, such as backup, with which I can create a complete backup of the stock ROM. In case I don't like CyanogenMod, I can restore the stock image and be exactly where I left it, Apps, Settings and everything (of course the new Recovery will still be installed.) Is this correct?
- I'm planning to do the following steps (I read about the details, just want to confirm the basics):
x use the Revolutionary way to S-OFF and install new Recovery
x create full image backup of the stock ROM using the new Recovery
x install new ROM (ClockWorkMod)
x if I don't like CM: restore image created before to return to stock
-> This should work, shouldn't it?
- One more: What will happen if the the phone is S-OFF, an alternative Recovery is installed, and a HTC Firmware-Update is attempted? Will this work at all, will it update just the ROM, or will it update the Recovery, too? S-OFF will not be changed back to S-ON, right?
Thanks for your help.
Regards

1. Yes, the recovery is in it's own partition and is independent from the ROM
2. The recovery creates a "snapshot" of your current ROM. So when you restore, it'll be just the way you left it.
3. There's no need to do any HTC Firmware updates after installing a custom ROM (infact, I'm almost 100% sure that it won't work)

As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
As for HTC firmware update question,if your talking about the over the air updates I'm not sure but I think it would update your hboot thus reverting back to s-on status again so best not accept it if you do get one (turn off in settings)
Edit : ninja'd lol
Sent from my HTC Wildfire using XDA App

slymobi said:
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
Click to expand...
Click to collapse
Yes, of course.
As for HTC firmware update question,if your talking about the over the air updates [...]
Click to expand...
Click to collapse
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.

150d said:
Yes, of course.
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
Click to expand...
Click to collapse
Ah sorry never dealt with any firmware updates. There are ruu.exe to help get back to stock if something goes wrong I think.
Sent from my HTC Wildfire using XDA App

You can go completely back to stock, s-on and all but believe me once you have cwm installed there really is no point unless its for warranty reasons, backup fails are rare with the latest recoveries + if it does fail with your first backup you can always post here and we will explain how to extract a stock Rom from an ruu to put things back to how they where before or you can flash a custom sense Rom and modify it to your liking.
Sent from my HTC Wildfire using xda premium

Scratch0805 said:
You can go completely back to stock, s-on and all
Click to expand...
Click to collapse
That's great.
[...] but believe me once you have cwm installed there really is no point unless its for warranty reasons[...]
Click to expand...
Click to collapse
Yea, exactly. I'm a little on the paranoid side, I know... ;-)
Ok, I'm on my way now. I've performed the "Revolutionary" S-OFF and am now running "Revolutionary CWM v4.0.1.4". Is this an out-of-date version?
I've read about ROM-Manager being able to auto-check for and flash a new Clockworks Recovery, but I've also read that ROM-Manager needs root. I have not yet flashed a new ROM, so I assume that I'm not yet rooted, am I? Can I find a ZIP of CWM that I can directly flash from the SD-card?
Does the CWM-version I'm running have any effect on the "quality" of the image backup? In other words, if I create a backup now, will I be able to restore it later running a different version of CWM?

The "different version backup restore" is a bit wonky and won't always work.
To flash a different recovery from the SD card do this:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
2. Boot into the bootloader
3. Wait a bit and then it should prompt you to update
4. Click the volume+ key to update
5. Remove SD card
6. Boot into the new recovery and insert the SD card
7. Go under mounts and select Mount USB storage
8. Delete the PCIMG file from your computer

nejc121 said:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
Click to expand...
Click to collapse
I tried to, but I couldn't use the link. The whole domain seems to be down - maybe another holy crusade of Big Content, who knows. They sure leave fans in their wake, don't they.
Since you indicated that updating would be ok for the wildfire I went to http://www.clockworkmod.com/rommanager and downloaded the file recovery-clockwork-5.0.2.0-buzz.zip.
However, I'm not sure how to handle it: If I put it on the card under this name, nothing happens on bootloader-start. In recovery, I can select the file and install it, and then I immidiatly get a newly colored menu with the new CWM version 5.something. However, once I restart, the old CWM (v4.x) is there again.
I assume I need to use a magic filename so that the bootloader performs the update, not the (already running) recovery. Right?
**EDIT: Ah, disregard. I believe I found the answer myself.

Do you have fastboot?
If you do I can give you the recovery.img I'm using, which you can flash via fastboot.

Yes, fastboot is available.
Thank you.

Okay, here's how you flash a recovery via fastboot.
1. Extract the .zip I attached to the location where you fastboot is
2. Reboot phone in the bootloader
3. Select fastboot and attach USB cable
4. Open up the command prompt and type in "cd [location of fastboot]
5. Type in "fastboot flash recovery recovery.img"
6. You're done
Oh and by [location of fastboot] I mean that you type in the location of fastboot.

Wow - this was fun. There was something really curious going on with my device: Whatever I tried, no "official" way worked to modify CWM v4 to v5. In every case, the menu of the new version showed up and was usable, but was gone again after restart. After the file-on-card method got me nowhere (file was not recognized), I tried the high road and installed ROM-Manager. This complained about missing su. So I installed su. After that ROM-Manager downloaded CWM v5 and put it onto the card (into a file named update.zip - ahh... ) On restart, the CWM-install-screen came up, then the v5 menu.
And after restart, it was gone again. Even ROM-Manager was confused: He showed v5 as "installed", when in fact it was still v4. ;-)
So finally I downloaded the Android SDK (to get fastboot.exe) and performed the flash as you suggested in the first place. And it worked. First try, without hitch, permanently.
Thank you very much for your help!
Regards

The problem with ROM Manager's version is that it's only temporary and can only be accessed from the ROM Manager itself

Flashing Radio

Hi all! I have a rooted Wildfire with the latest stable Cyanogen release, and it works fine (GPS and Wi-Fi too).
My only gripe is this: my radio version is 13.45.55.24H_3.35.15.31, and I have files for upgrading it to 3.35.19.25 or 3.35.20.10, but flashing doesn't seem to work.
I have done the procedure from recovery, using an old (2.5.0.x) version of Clockwork as recommended (later version won't even start the flashing): flashing says "successfully completed", but when I restart the phone I still have the 3.35.15.31 version installed...
What am I doing wrong?

Use adb for flashing radio!

To be precise, from recovery I simply do "Install from SD" and select the zip file with the radio image, and then reboot.. Nothing else...
Maybe I am missing some steps?

plakiko said:
Use adb for flashing radio!
Click to expand...
Click to collapse
You mean go into HBOOT?
What steps should I follow exactly?

Ok, never mind!
Downloaded the Android SDK and did it!
Thank you!

[Q] please help me error after upgrading hbot

my one x is HTC_622 hboot 1.36
now, my one x cant get into the android
before the error, my one x is android 4.0 custom rom
and i want to upgrade to 4.1
and i tried this one http://forum.xda-developers.com/showthread.php?t=1660807
and i tried http://forum.xda-developers.com/showthread.php?t=2009525
unfortunately, i forgot the ruu will clear my sdcard. and i dont have the zip file in the sd card
i cant trun on my phone into android, so i cant put the zip to sd card
so i run the ruu of radio 2.12 again in order to get back the stock rom
but it failed.
how to slove this problem.

kelvin1hui said:
my one x is HTC_622 hboot 1.36
now, my one x cant get into the android
before the error, my one x is android 4.0 custom rom
and i want to upgrade to 4.1
and i tried this one http://forum.xda-developers.com/showthread.php?t=1660807
and i tried http://forum.xda-developers.com/showthread.php?t=2009525
unfortunately, i forgot the ruu will clear my sdcard. and i dont have the zip file in the sd card
i cant trun on my phone into android, so i cant put the zip to sd card
so i run the ruu of radio 2.12 again in order to get back the stock rom
but it failed.
how to slove this problem.
Click to expand...
Click to collapse
1.Flash custom recovery http://download.clockworkmod.com/rec...-endeavoru.img ( Fastboot flash recovery nameofrecoveryfile.img) make sure youre in fastboot folder.
2.Go to Fastboot mode holding power and volume button simultaneously.
3. Select recovery mode.
4. Go to mount and storage < Mount usb storage.
Copy the ROM of your choice.
5. Flash the boot.img - fastboot flash boot boot.img
Note: Use any custom JB rom of your choice
Hope it helps.

thx
but another problem happened
after i installed viper 3.2, i cant get any phone signal, that means i cant connect to internet wif hspa or cant phone
do you know how to slove this? i cant use viper3.2 in hong kong?

kelvin1hui said:
thx
but another problem happened
after i installed viper 3.2, i cant get any phone signal, that means i cant connect to internet wif hspa or cant phone
do you know how to slove this? i cant use viper3.2 in hong kong?
Click to expand...
Click to collapse
have you flashed the rom's boot.img?

matt95 said:
have you flashed the rom's boot.img?
Click to expand...
Click to collapse
yes, i confirmed twice

kelvin1hui said:
yes, i confirmed twice
Click to expand...
Click to collapse
Try flashing the boot.img only, make sure to clean cache and dalvik cache.
Under mobile network try to do a manual search.

ashishchandra said:
Try flashing the boot.img only, make sure to clean cache and dalvik cache.
Under mobile network try to do a manual search.
Click to expand...
Click to collapse
fastboot erase cache?

kelvin1hui said:
fastboot erase cache?
Click to expand...
Click to collapse
That's always good to do, but Matt means the cache and dalvik cache that you can wipe in the recovery

kelvin1hui said:
fastboot erase cache?
Click to expand...
Click to collapse
yes from fastboot as well as from recovery !!

Hmmm i am starting to lose the confidence in the hboot firmware update. I am seeing more and more reports of this problem. My opinion :
its always the best thing to update officially with a nandroid backup !
This way you avoid radio/ril problems ..... but its to late for that now, the solution ..... I don't have it
Try to flash from scratch again, wipe ALL from recovery even format the sdcard and copy only the rom.zip back on it.
Flash the boot.img and install this script right before you install the rom !
http://db.tt/eLoVUcRc
(Install it the same way as a rom - install zip from sdcard and continue to install it)
Then the rom, and also choose in the aroma full wipe and also very important (this might be the problem!!!) The question about the custom kernel ....choose NO !

You could try getRIL from play store.
Sent from my One X

:laugh::laugh::laugh:
every problem solved now ,after i follow all steps that you guys recommend
now im using viper 3.2 now
i hope i dont need to upgrade hboot again when 4.2 or 5.0 released

Nice !

kelvin1hui said:
:laugh::laugh::laugh:
every problem solved now ,after i follow all steps that you guys recommend
now im using viper 3.2 now
i hope i dont need to upgrade hboot again when 4.2 or 5.0 released
Click to expand...
Click to collapse
Good Luck mate, you will learn a lot from all . :good:

[Q] stuck after installing firmware

i flashed new firmware to my htc one m8
I got into recovery and changed the name firmware file.
but now in the recovery it doesn't recognize my internal storage, kind of. it says 0 mb.
And when I try via adb to push a file to it it fails. (adb push filename.zip /sdcard/)
so it seems like i only have the external card now working.
what can I do?
I'm currently in the stage where i have the firmware file in the right name and it keeps asking me to update, if i remove the external card, i can get into recovery change the name, and then i see it won't read the internal storage like i wrote up here.
but after I change the name i can get into fastboot mode.
I currently have recovery mode - twrp 2.8.0.3
p.s I think my internal storage does work, cause i can go into recovery mode(twrp), my external_sd was formmated
before i used to update the firmware, so it has nothing except for that file

You're not flashing the firmware through recovery, are you?

No, i flashed, with the guide here, via an external card, changing the name of the firnware so the hboot would recognize it.. and update it

josh.walker.9242 said:
You're not flashing the firmware through recovery, are you?
Click to expand...
Click to collapse
I was thinking that maybe my twrp version 2.8.0.3 is too old for this bootloader veraion maybe, and i need to update to twrp to 2.8.6 and then try to transfer the rom file and install it.
What do u think?
Do u have any suggestions?

dav_sap said:
I was thinking that maybe my twrp version 2.8.0.3 is too old for this bootloader veraion maybe, and i need to update to twrp to 2.8.6 and then try to transfer the rom file and install it.
What do u think?
Do u have any suggestions?
Click to expand...
Click to collapse
I have TWRP 2.8.0.6. You can download TWRP manager from Play Store, it has a list of TWRP versions you can install. The app installs them too. Everytime I used the app to install it, it says it failed but it actually works, just install, then say ok to the failed install pop up and reboot into recovery and it'll be there.
Edit: As soon as the firmware has flashed successfully, boot up and delete the firmware file off of your external SD card so it doesn't keep asking you to update.

josh.walker.9242 said:
I have TWRP 2.8.0.6. You can download TWRP manager from Play Store, it has a list of TWRP versions you can install. The app installs them too. Everytime I used the app to install it, it says it failed but it actually works, just install, then say ok to the failed install pop up and reboot into recovery and it'll be there.
Click to expand...
Click to collapse
I have no OS now.
I need to download it, and flash it via fastboot. I'm wondering if that's the problem that the internal storage is giving me these problems or it has nothing to do with it.
Does a different firmware require different twrp versions?
Sent from my HTC Desire HD using XDA Free mobile app

dav_sap said:
I have no OS now.
I need to download it, and flash it via fastboot. I'm wondering if that's the problem that the internal storage is giving me these problems or it has nothing to do with it.
Does a different firmware require different twrp versions?
Sent from my HTC Desire HD using XDA Free mobile app
Click to expand...
Click to collapse
Not as far as I know. Your best bet man is probably to download an RUU and just flash that through fastboot or the external sd card method. Then after that, flash the TWRP then put a ROM zip on your phone and flash that way.

josh.walker.9242 said:
Not as far as I know. Your best bet man is probably to download an RUU and just flash that through fastboot or the external sd card method. Then after that, flash the TWRP then put a ROM zip on your phone and flash that way.
Click to expand...
Click to collapse
What RUU should i use? Isn't that just firmware like the one i flashed now?

dav_sap said:
What RUU should i use? Isn't that just firmware like the one i flashed now?
Click to expand...
Click to collapse
No, an RUU is a complete system install. Completely stock with the exception of some RUUs contain root. But it will wipe everything on your phone, all your personal data and what not.