Develop Bugs

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

[Q] How to get CWM recovery working after unlocking bootloader through HTC

I have an HTC Explorer and have installed CM 9 easily. Unlock bootloader through HTC , install custom CWM recovery using fastboot, then install CM 9 zip from sd card using CWM recovery. I have tried to do the same with my daughter's Wildfire. I get as far as installing a CWM recovery but it hangs at a "hat" icon when I try to use it. I have tried several CWM img files, including the one in the "cm49?" zip. None work. Is there a way for me to get a CWM recovery working? I don't want to go through all the s-off process, I don't think it is needed. My Explorer works great with s-on. I hope someone can help. I promised my daughter I would get ICS on her phone as her Christmas present.

bobharding said:
I have an HTC Explorer and have installed CM 9 easily. Unlock bootloader through HTC , install custom CWM recovery using fastboot, then install CM 9 zip from sd card using CWM recovery. I have tried to do the same with my daughter's Wildfire. I get as far as installing a CWM recovery but it hangs at a "hat" icon when I try to use it. I have tried several CWM img files, including the one in the "cm49?" zip. None work. Is there a way for me to get a CWM recovery working? I don't want to go through all the s-off process, I don't think it is needed. My Explorer works great with s-on. I hope someone can help. I promised my daughter I would get ICS on her phone as her Christmas present.
Click to expand...
Click to collapse
If I'm not mistaken you have to flash the boot.img manually with S-ON so I think a S-Off'd device is much better and it isn't that hard to S-Off it. I don't know if the S-Off methods still work if you unlocked it before but they should.
Besides you haven't taken the CWM from Pico/Explorer and tried to install it on the Wildfire, have you?

miniAndroidian said:
If I'm not mistaken you have to flash the boot.img manually with S-ON so I think a S-Off'd device is much better and it isn't that hard to S-Off it. I don't know if the S-Off methods still work if you unlocked it before but they should.
Besides you haven't taken the CWM from Pico/Explorer and tried to install it on the Wildfire, have you?
Click to expand...
Click to collapse
Thanks for your reply. All the cwm img files I have used have come from this forum. I had high hopes for the one I extracted from "pc49img.zip" as it seemed to say it might work on another post. It installed like the other but doesn't work.

bobharding said:
Thanks for your reply. All the cwm img files I have used have come from this forum. I had high hopes for the one I extracted from "pc49img.zip" as it seemed to say it might work on another post. It installed like the other but doesn't work.
Click to expand...
Click to collapse
I got a question are you just unlocked or already rooted on the WF? I think you can't install CWM if you're not rooted. That would be nice to know. Otherwise you can may follow this guide

miniAndroidian said:
I got a question are you just unlocked or already rooted on the WF? I think you can't install CWM if you're not rooted. That would be nice to know. Otherwise you can may follow this guide
Click to expand...
Click to collapse
Just unlocked after following the procedure on "htcdev.com". With my Explorer you can root the phone with the aid of the CWM recovery you install after unlocking it. Maybe the CWM recoveries for Wildfire assume your phone is already rooted, but I don't know how to root it without having a working CWM recovery first.

bobharding said:
Just unlocked after following the procedure on "htcdev.com". With my Explorer you can root the phone with the aid of the CWM recovery you install after unlocking it. Maybe the CWM recoveries for Wildfire assume your phone is already rooted, but I don't know how to root it without having a working CWM recovery first.
Click to expand...
Click to collapse
Yeah you're right. I think the progress on S-ON should be like this:
-flash CWM
-flash superuser rights (thats how it worked on the HTC One X)
I found this:
http://forum.xda-developers.com/showthread.php?t=1484124&highlight=recovery
Let me know if it worked.

miniAndroidian said:
Yeah you're right. I think the progress on S-ON should be like this:
-flash CWM
-flash superuser rights (thats how it worked on the HTC One X)
I found this:
http://forum.xda-developers.com/showthread.php?t=1484124&highlight=recovery
Let me know if it worked.
Click to expand...
Click to collapse
Thanks for all your help miniAndroidian (the Nexus 4 should be awesome, (I am saving up, but they are not available in Australia at the moment. I told my daughter she should get one too, but she hasn't got the money either, so that's why I am working on the Wildfire)
Unfortunately the post you directed me to says you have to flash the CWM recovery from the stock recovery but I don't have that anymore as I have replaced it with the CWM recovery which just hangs. There must be a way round it, but I am no expert at all.

bobharding said:
Thanks for all your help miniAndroidian (the Nexus 4 should be awesome, (I am saving up, but they are not available in Australia at the moment. I told my daughter she should get one too, but she hasn't got the money either, so that's why I am working on the Wildfire)
Unfortunately the post you directed me to says you have to flash the CWM recovery from the stock recovery but I don't have that anymore as I have replaced it with the CWM recovery which just hangs. There must be a way round it, but I am no expert at all.
Click to expand...
Click to collapse
Same in Germany with the Nexus 4 but it should be avalible in the middle of january
Back to the topic:
You have to put the "update.zip" to the root of your SD-Card and boot into the bootloader menu (the white screen with 3 android's on the bottom) and then it should recognize the new CWM.

Terrific. I didn't understand it. My daughter lives 100km from me so I will have to visit her this weekend. She left after Christmas saying "Dad, admit it you are a failure" after I had spent hours on it, so this might show her I am not as useless as she thinks. I am intending to flash the "mini" CM 9 rom. I hope this is the best one.

bobharding said:
Terrific. I didn't understand it. My daughter lives 100km from me so I will have to visit her this weekend. She left after Christmas saying "Dad, admit it you are a failure" after I had spent hours on it, so this might show her I am not as useless as she thinks. I am intending to flash the "mini" CM 9 rom. I hope this is the best one.
Click to expand...
Click to collapse
I really hope it works (i'm out of solutions ) otherwise you should really think about S-Off'ing it.
miniCM 9 is the fastest one but the sensor buttons don't give a vibration feedback it's a kinda annoying.
Good luck

I have had a very very frustrating day. I tried "update.zip", didn't do anything. I even renamed it "pc49img.zip" nothing. I finally found a windows program called "unlock root". I used the free version. You just connect up the phone via usb and press root. It gets you to confirm it is a wildfire and then after a bit says successfully rooted. I then installed Superuser, Rom Manager and ES File Explorer to check it.
I backed up the present rom successfully with Rom Manager. It even has an option for flashing Clockworkmod recovery and one for rebooting into recovery for manual management. It downloads CWM recovery 5.0.2.0 but it doesn't work either (looking at the files on the SD card I think it is just the same as the "update.zip"). There is also an option for installing a rom from sd card but when I went to this it asked if there was any addon, and of course I need tiny gapps. It then said I need the paid version for this. Seeing the recovery didn't work I didn't want to risk it.
My conclusion is all the present CWM recoveries require S-Off. I have read some people like the Aroma installer. I know nothing about it, but I wonder if it might be possible to install the CM 9 rom with it.

I have worked out what my problem has been. I have fallen for the old Trackball trick. I must be the only person not to know you use the Trackball in CWM recovery not the power button. I sent my daughter an email and she has confirmed the recovery in Rom Manager actually works when you use the Trackball. I will have to visit her again now to install CM 9.

MiniCM9 installed. Working great. I will put a how to in "General"

HTC One X Semi Bricked NEED HELP.

Hello,
Well, I was trying to install some new kernels but somehow my phone went into Boot Loop.
After that, I accidentally formatted my system and system memory. End Result: Their is nothing in my SD Card Right now.
I have searched in this forum and others for 2 days and still can not find a proper solution. Now, my laptop and computer does not recognize my device through adb device. I tried to insall stock rom through RUU but it gave an Boot Loader Version Error. However, I managed to install philz recovery and tried to mount memory but still no luck, I can not push files through adb as it can not recognize my device.
My CID is 02_001. I downloaded the matched CID RUU (RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed) but it didnt work. My image number of the phone (I dont know what is this actually) is like 4.xxxx and the image number of the RUU is 1.xxxx.
The HBOOT version is 1.72 S ON.
Can someone by someway, please give me the link of UPDATED RUU so that I can flash to stock rom or just help me to find a way to transfer custom rom to my phone memory so that I can flash a custom rom.
I was using VIPERX ROM 4.1.1,as the phone was draining alot of battery so over efficiently I tried to FLASH BRICKED KERNEL.
NOW I AM STUCK, HELPLESS and after losing the battle I am posting this thread.
PLEASE HELP ME WITH A SUITABLE ANSWER.
I would prefer to install stock rom but it wont work I guess because of the updated HBOOT version.

WaleedUQ said:
Hello,
Well, I was trying to install some new kernels but somehow my phone went into Boot Loop.
After that, I accidentally formatted my system and system memory. End Result: Their is nothing in my SD Card Right now.
I have searched in this forum and others for 2 days and still can not find a proper solution. Now, my laptop and computer does not recognize my device through adb device. I tried to insall stock rom through RUU but it gave an Boot Loader Version Error. However, I managed to install philz recovery and tried to mount memory but still no luck, I can not push files through adb as it can not recognize my device.
My CID is 02_001. I downloaded the matched CID RUU (RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed) but it didnt work. My image number of the phone (I dont know what is this actually) is like 4.xxxx and the image number of the RUU is 1.xxxx.
The HBOOT version is 1.72 S ON.
Can someone by someway, please give me the link of UPDATED RUU so that I can flash to stock rom or just help me to find a way to transfer custom rom to my phone memory so that I can flash a custom rom.
I was using VIPERX ROM 4.1.1,as the phone was draining alot of battery so over efficiently I tried to FLASH BRICKED KERNEL.
NOW I AM STUCK, HELPLESS and after losing the battle I am posting this thread.
PLEASE HELP ME WITH A SUITABLE ANSWER.
I would prefer to install stock rom but it wont work I guess because of the updated HBOOT version.
Click to expand...
Click to collapse
Flash Philz 5.15.9 recovery munt sd card and copy your rom to sd card after this install it and flash the boot.img from your rom archive

Thant said:
Flash Philz 5.15.9 recovery munt sd card and copy your rom to sd card after this install it and flash the boot.img from your rom archive
Click to expand...
Click to collapse
Ohkay, I tried the way you told me .
I have Philz Version 6.19.3 however now,
I am getting this error
asset failed: getprop('ro.product.device')=='endeavoru'
II getprop('ro.build.product')=='endeavoru' II
getprop('ro.product.board')=='endeavoru'

WaleedUQ said:
Ohkay, I tried the way you told me .
I have Philz Version 6.19.3 however now,
I am getting this error
asset failed: getprop('ro.product.device')=='endeavoru'
II getprop('ro.build.product')=='endeavoru' II
getprop('ro.product.board')=='endeavoru'
Click to expand...
Click to collapse
Man, @Thant trying to help and you skip his instructions?
Do what he said,flash philz 5.15.9.

WaleedUQ said:
Ohkay, I tried the way you told me .
I have Philz Version 6.19.3 however now,
I am getting this error
asset failed: getprop('ro.product.device')=='endeavoru'
II getprop('ro.build.product')=='endeavoru' II
getprop('ro.product.board')=='endeavoru'
Click to expand...
Click to collapse
witch Rom are you try to install?

HTC One X Trying to install ROM but stuck with problems.

Hi, so recently my HTC One X has been acting up so I decided to install a ROM to make it much faster, so I had to unlock the bootloader. When i've done that I flashed CWM on my device. Then I tried to install a rom that was on the device and it didn't install which leads me to my first problem, the page said I needed to reset everything and use the fastboot command to flash the zip file that worked but when I went to CWM (to install gapps) the device never booted in the ROM just kept going back to CWM. So I googled this and there was multiple things I tired out like adb command etc also it would be easier if this problem was fixed if this button worked (mount USB storage) I press that and it does not work. So then I don't know what to do. I'm stuck here please help me the rom was cm-11-20160815-NIGHTLY-endeavoru.zip.

swarby2 said:
Hi, so recently my HTC One X has been acting up so I decided to install a ROM to make it much faster, so I had to unlock the bootloader. When i've done that I flashed CWM on my device. Then I tried to install a rom that was on the device and it didn't install which leads me to my first problem, the page said I needed to reset everything and use the fastboot command to flash the zip file that worked but when I went to CWM (to install gapps) the device never booted in the ROM just kept going back to CWM. So I googled this and there was multiple things I tired out like adb command etc also it would be easier if this problem was fixed if this button worked (mount USB storage) I press that and it does not work. So then I don't know what to do. I'm stuck here please help me the rom was cm-11-20160815-NIGHTLY-endeavoru.zip.
Click to expand...
Click to collapse
CWM was abandoned a long time ago in the community so it won't cope with the instructions modern roms use. Its a bit sad that CWM came to a such sudden end I kind of miss the different recoveries based on it. Not to mention philz touch recovery..
Anyway go here: (its a twrp recovery) http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Read the instructions and flash the provided .img file and your phone should be up and running within the hour.
Edit: I'm not sure if that rom uses the new or old layout. The documenation is more than a bit poor because the device info is outdated on the cyanogenmod wiki. Last edited in year 2012..
https://wiki.cyanogenmod.org/w/Endeavoru_Info
If the rom will not flash with the new layout recovery provided above.
Read instrutions how to revert to old layout first. And flash this older recovery from here:
https://dl.twrp.me/endeavoru/

SÜPERUSER said:
CWM was abandoned a long time ago in the community so it won't cope with the instructions modern roms use. Its a bit sad that CWM came to a such sudden end I kind of miss the different recoveries based on it. Not to mention philz touch recovery..
Anyway go here: (its a twrp recovery) http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Read the instructions and flash the provided .img file and your phone should be up and running within the hour.
Edit: I'm not sure if that rom uses the new or old layout. The documenation is more than a bit poor because the device info is outdated on the cyanogenmod wiki. Last edited in year 2012..
https://wiki.cyanogenmod.org/w/Endeavoru_Info
If the rom will not flash with the new layout recovery provided above.
Read instrutions how to revert to old layout first. And flash this older recovery from here:
https://dl.twrp.me/endeavoru/
Click to expand...
Click to collapse
Really? Didn't realise that... Im trying to charge my phone because I can't flash it because the battery is too low. So thanks for telling me. I will post when Ive flashed it to my phone. When you flash it dosen't get rid of all the roms that's already on the phone? Because I cant access the phone within usb but does this recovery solve that? Like mount usb storage like in CWM?

swarby2 said:
Really? Didn't realise that... Im trying to charge my phone because I can't flash it because the battery is too low. So thanks for telling me. I will post when Ive flashed it to my phone. When you flash it dosen't get rid of all the roms that's already on the phone? Because I cant access the phone within usb but does this recovery solve that? Like mount usb storage like in CWM?
Click to expand...
Click to collapse
Flashing the recovery will not wipe anything except the recovery partition obviously. When you boot to twrp you will be able to access the internal storage by going to Mount and press the Mount usb storage twice. And the one x should be detected on your pc.
But when you're done with the backup you will wipe all partitions with the Format data option as described in the thread I linked yesterday. So backup all important data to your computer.

Thank you so much! I'm up and running!

HTC ONE m9 boot loop after rooting

I have tried to root my HTC ONE M9. Like said, i followed the instructions and installed Twrp latest version. it went fine.And then it was asked to copy SUPER SU to the internal memory and then install in from recovery which i did. After that when i tried to turn my phone ON, its stuck in the boot page with HTC icon. I tried to clear cache,factory reset but didnt work.What i feel is the sense OS got corrupted.What should i do.I dont want to use a different UI as i want my default sense. What must be the problem.if i have to get a custom ROM, which one u guys suggest.Pls help me here
Than You

Restore from backup then use supersu v2.64 or v2.65

Where is the best place to get SuperSU 2.64 or 2.65?

When I was still using my M9 regularly this would happen sometimes. I think it has to do with the bootloader and/or kernel checking partition signatures and putting the phone in a bootloop if the boot/system partition was modified. Flash a custom kernel.

I have the same problem. Any solution that work ?