yashsingh1/xdaforums huggingface dataset:
[Wildfire Android Development] kylon:
http://www.ilsoftware.it/articoli.asp?id=6894

use google translate

i know ext4 is very important on dual core phones,but can also help a single core
[Wildfire Android Development] zyonee:
Sorry, but there's nothing in that article that suggests it's been done on Desire. Maybe Desire HD has it already, but not Nexus One, Desire or Wildfire, as far as I know of. Sorry. And even if there is, I don't think I could implement it myself.
[Wildfire Android Development] kylon:
I know wildfire doesn t have it

Desire s have it,sense rom use it
[Wildfire Android Development] zyonee:
Ah, ok, but that device has it natively.
[Wildfire Android Development] phantom200580:
Does one try to backup sd-ext4?
[Wildfire Android Development] zyonee:
Sorry, I don't understand your question.
[Wildfire Android Development] phantom200580:
Any1 try to make a nandriod backup with ext4? :( sorry for my bad english
[Wildfire Android Development] zyonee:
Oh. It should work, but I have no Wildfire to try it on. Maybe someone else already tried it?
[Wildfire Android Development] phantom200580:
aha, Ok thanQ sir :)
[Wildfire Android Development] fifarunnerr:
It backed up my sd-ext partition(EXT4), so I guess it works ifne ;)
[Wildfire Android Development] zyonee:
Have you also tried restoring it?
[Wildfire Android Development] phantom200580:
i partitioning SD card to ext4 but when i wipe sd-ext4 it's back to ext3 :(
[Wildfire Android Development] zyonee:
Hmm, the wipe defaults to ext3, I guess. Maybe I can look at it someday. No promises.
[Wildfire Android Development] phantom200580:
yes, plz sir :)
[Wildfire Android Development] zyonee:
I looked at it, and there's not much I can do. I might just break stuff rather than fix it. On the other hand, isn't there some command that can be typed in adb shell that will convert a volume from ext3 to ext4?
[Wildfire Android Development] zyonee:
New version

Version 5.0.2.7 in the OP.
[Wildfire Android Development] phantom200580:
You r the best Mr zyonee :)

but what about sd-ext4 is this version support this volume?
[Wildfire Android Development] zyonee:
When partitioning the sd card, yes. Maybe not when formatting the sd-ext partition.
[Wildfire Android Development] phantom200580:
When i partitioning the sd card to Ext4 it will be Ext3, i used MiniTool Partition Wizard to know it

so its fake

anyaway its Good work sir
[Wildfire Android Development] zyonee:
Hmm, failed attempt then. Or maybe it's identified wrong, since ext3 and ext4 seem to be similar file systems. I really don't know. It seemed to make a difference when I tried it on a Nexus One, though.
[Wildfire Android Development] chintu_a_b:
I'm not able to install it using unrevoked3. It is giving me error that firmware is too new. FYI phone was first downgraded to hboot 1.01.0001 from 1.01.0002 and then rooted with revolutionary.
[Wildfire Android Development] zyonee:
If it's rooted with Revolutionary, isn't it S-OFF then? If so, you can flash the recovery.img through fastboot:

adb reboot bootloader
fastboot flash recovery name-of-recovery.img

And if not, as far as I can remember, that error is shown when you're using a newer version of unrevoked3. Try version 3.14 (you'll have to google for it). It should let you flash the recovery properly
[Wildfire Android Development] chintu_a_b:
Thanks for quick reply. I just discovered that method and did "flash_image recovery /sdcard/recovery.img" from terminal and I was able to flash.

Thanks again for great work!
[Wildfire Android Development] chintu_a_b:
Backup from recovery didn't work. It just hangs while trying to backup /system. Trying to go back to previous recovery by using revolutionary. Not sure if it has anything to do with below custom mtd partition guide I followed.

http://xdaforums.com/showthread.php?t=1233340
[Wildfire Android Development] zyonee:
While I do understand the benefits of using a custom MTD table, I cannot guarantee that this recovery will work properly with it.
[Wildfire Android Development] th3ant:
I'm sorry for being repetitive, but I didn't quite get what people are saying before hand.

Do I just flash this (and any other recoveries on this matter) like I would any other ROM, or do I need to use another tool?

Sorry again, and thanks in advanced, th3ant
[Wildfire Android Development] chintu_a_b:
Check this link and use method suitable to you.

http://www.addictivetips.com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/
[Wildfire Android Development] zyonee:
New version

OP updated!
[Wildfire Android Development] masanijey:
Does this update enable green led in charging off mode?
[Wildfire Android Development] zyonee:
Green led when fully charged? I should think so, but please do try it.
[Wildfire Android Development] Alexcxvtr:
When flashing the .zip with the 5.0.2.0 recovery via clockworkmod everything goes well. But when I reboot my phone and enter recovery mode the version is still the previous one(3.0.0.6). I've downloaded the .zip file via ROM Manager.

Just to clarify... this happens when I reboot the device and NOT the recovery mode. So, I have to enter recovery again and flash the downloaded .zip to get 5.0.2.0 version in my phone. What to do?
[Wildfire Android Development] 3xeno:
Zips via ROM Manager are temporary. When you flash them, you get that version, and it is lost after a reboot and you must flash the zip again. To permanently update your CWM, you will need to flash the IMG file of the same to your device. Methods are posted here: (Check under heading 'Custom Recoveries'. This is not as straightforward as flashing a Zip file in your existing Clockworkmod Recovery)

http://xdaforums.com/showpost.php?p=12782368&postcount=2
[Wildfire Android Development] Alexcxvtr:
Thanks once more 3xeno! May I ask why flashing via ROM Manager is a temp thing?
[Wildfire Android Development] 3xeno:
They are installed to a virtual partition on the SDCard (It's designed to be like that). But, when you flash an IMG file, it is installed straight to the device's internal NAND memory, hence it's permanent.
[Wildfire Android Development] mac4rfree:
My ClockWorkMod Version is 2.5.0.1... so i like it to update this. so, i just need to flash the zip file like other ROMS????
[Wildfire Android Development] revan1993:
yes just flash the zip file in cwm and you have updated cwm, but its just temp update because not permantly read above the post from 3xeno =)
[Wildfire Android Development] Alexcxvtr:
Again, thank you! Take care...
[Wildfire Android Development] [sito_web]:
I've update the ClockWorkMod Recovery from 5.0.2.0 to 5.0.2.7 by PC49IMG.zip and when i've restarted my wildfire it remain the htc splash screen. i've waiting an hour but it doesn't boot.. So i return to CWM 5.0.2.0 but i've the same problem..

Now still remain only the splash screen.. Aniway i can swich-on the phone in recovery mode..

How can I solve?. I've tryed to wipe all but it doesn't work
[Wildfire Android Development] zyonee:
Apparently there's nothing wrong with the recovery flash. It's probably ROM/Kernel related. Try wiping system/cache/data and then flash a ROM/Kernel combo that should work. You may want to make a nandroid backup of your current setup first, so you can extract settings, apk's and such on a later occasion.
[Wildfire Android Development] calyxim:
Is there a PC49 image for the lazy? :D
[Wildfire Android Development] 3RMD:
For the lazy guys I made one:

https://dl.dropbox.com/s/h6hw7ieldh8l83d/PC49IMG.zip?dl=1

For me, it works ;)

I hope I'm allowed to do this.. if not tell me and I delete it :D
[Wildfire Android Development] zyonee:
Feel free, saves me some work. :)
[Wildfire Android Development] dud3me:
Is the PC49IMG.zip the latest recovery (5.0.27)?
[Wildfire Android Development] LSD DREAMER:
seeing this was compiled from cm 7 will it work with cm 9
[Wildfire Android Development] 3RMD:
Yes.

Yes.
[Wildfire Android Development] LSD DREAMER:
I think the update broke my rom manager but the recovery works brilliantly.
[Wildfire Android Development] gromez:
For anyone interested, here is a 5.0.2.8 stock version (compiled from CM sources)

www.mediafire.com/?s5cei1rwx1bto2n

Put it on root of the sdcard then run flash_image

adb push buzz-recovery-5.0.2.8.img /sdcard/
adb shell flash_image recovery /sdcard/buzz-recovery-5.0.2.8.img
adb shell rm /sdcard/buzz-recovery-5.0.2.8.img
[Wildfire Android Development] Amir.Adel:
Whats new in your version?
[Wildfire Android Development] hacktrix2006:
Thank you flashed and working smooth!
[Wildfire Android Development] Amir.Adel:
Whats new in this version?

ThanQ
[Wildfire Android Development] gromez:
Check the commit history here: https://github.com/CyanogenMod/android_bootable_recovery/commits/gingerbread/

It's all commits between the one named "support backup and restore on internal sdcard" and now.
[Wildfire Android Development] LSD DREAMER:
5.0.2.7 is a grate recovery but it does not want to work thru rom manager.
[Wildfire Android Development] LSD DREAMER:
How do u make this into a pc49img.zip
[Wildfire Android Development] 3RMD:
Simply replace the .img in an existing pc49img.zip without unzipping it.
[Wildfire Android Development] :
I tried flashing the img file using flash_image command from terminal on phone. Now it gets stuck on HTC splash screen if I boot into recovery. Haven't tried fastboot yet.
[Wildfire Android Development] zyonee:
fastboot should work better,provied that you have S-OFF and that the img file isn't broken.
[Wildfire Android Development] :
Ok i'll try fastboot. Of course I have unlocked bootloader! :D
[Wildfire Android Development] gino.d:
thanks a lot for this, saved my lot of hassle!
[Wildfire Android Development] darknight83:
works great though fastboot the is also a download link for the pc49img.zip

some where in this thread

---------- Post added at 05:42 AM ---------- Previous post was at 05:16 AM ----------

here is download link for pc49img.zip https://dl.dropbox.com/s/h6hw7ieldh8...49IMG.zip?dl=1 and then just use fastboot and hay presto done

please hit thanks if i helped :)
[Wildfire Android Development] KhurramF:
The link is dead. Can someone reup this please?

Thanks.
[Wildfire Android Development] miniAndroidian:
Please, this is the 5.0.2.8 version ;)
[Wildfire Android Development] KhurramF:
Thanks for posting the link. So I just copy it to the root of the sdcard and flash it from recovery? Btw, I am not able to use fastboot the push the recovery.img to my phone. It gives an error "FAILED: remote not allowed".
[Wildfire Android Development] Scratch0805:
No...... Place it on your sdcard and then reboot into bootloader (hboot) by pressing volume down + power.

hboot should pick up the file and ask you if you want to update. After that move the PC49IMG.zip into a folder on your sdcard or remove it altogether otherwise it'll get annoying asking overtime you boot into the bootloader.
[Wildfire Android Development] eventcom:
Btw you could find most of the wildfire stuff in 3xeno's "the complete wildfire index" thread on the general section ;)

Swyped from my HTC Wildfire (Buzz)
[Wildfire Android Development] KhurramF:
Thanks for the help. I placed the PC49IMG.zip file in the root of my sdcard and booted into hboot. But it does not prompt me to use the file. I just get the menu from where I can go into recovery (plus other options). I searched around in this thread and there is a reference to another tool, AndroidFlasher. I tried to use this tool, but it failed with an error message that I need an "ENG bootloader" to flash recovery.img.
[Wildfire Android Development] eventcom:
Your phone needs to be s-off to flash a custom recovery - if you don't know what I mean you most probably aren't...

Swyped from my HTC Wildfire (Buzz)
[Wildfire Android Development] KhurramF:
My phone is already s-off, rooted and has CWM 3.0.0.6 installed (hboot is 1.01.001). I am currently running a custom ICS based rom.
[Wildfire Android Development] Scratch0805:
Mind me asking how you s-off"d the phone?

Revolutionary should give you hboot 6.01.001 or something like, did you use xtc clip?

Make sure the zip isn't in any folders before booting into hboot i.e move it to the root of your card, make sure it in"t named PC49IMG.zip.zip as that's a common easy mistake to make.
[Wildfire Android Development] KhurramF:
The guy I bought it from had s-off'd it for me. I don't really know how he did it. I have attached an image of the phone when I boot it with volume down pressed.

The file is named PC49IMG.zip.

What if I run Revolutionary again? Can I s-off it again? I hope it does not mess up the phone.
[Wildfire Android Development] Scratch0805:
Hmmm....... Maybe my mistake, its been a while.

Take a look here for the different methods of flashing recovery. http://xdaforums.com/showthread.php?p=12782368

They should all work for you....... :)
[Wildfire Android Development] KhurramF:
Well, I decided to take the plunge and ran revolutionary. It did its thing and now the phone showed revolutionary on the initial screen and hboot 6.01.001. So far so good.

I still had PC49IMG.zip in the sdcard. So I turned off the phone and then turned it on with the volume down button pressed. hboot could still not find PC49IMG.zip. So booted the phone normally, connected it to the laptop and started AndroidFlash, chose the recovery.img for 5.0.2.8. AndroidFlash did its thing and said the flash was successful. I rebooted the phone again into recovery, but was surprised to see the old version of CWM (3.0.0.6). I rebooted the phone again into hboot, then used fastboot command to flash recovery.img to the phone. Rebooting the phone into recovery (finally) show CWM 5.0.2.8 :) Thanks to all who helped.
[Wildfire Android Development] eventcom:
Not sure about the HBOOT versions but the fastboot method definitely should work on all CWM versions...

glad you were able to sort it out :laugh:
[Wildfire Android Development] drewniany92:
so new recovery is better than 3x ? what differences can you see?(:

Taptapped from my little killer iPod 4G (;
[Wildfire Android Development] Scratch0805:
I know........... :cool:
[Wildfire Android Development] KhurramF:
fastboot did not work for me till I had run revolutionary (even though I aleady had s-off and CWM 3.0.0.6).

I have not used CWM 5.x extensively; I just used it to flash a custom rom. From what little I saw, it looks the same as CWM 3.x. The only reason I flash CWM 5.x was because the custom rom (RemPuzzleRom) suggested that I use it.
[Wildfire Android Development] eventcom:
not much of a difference but I've flashed 4.x by accident recently (because the PC49IMG file of the Wildfire Index thread was pretending to contain 5.2.0.x but is 4.x instead). That one has even an advantage over 5.2.0.x: you have all the wipes at one place in the menu ;)
[Wildfire Android Development] Wasimk32:
5.2.0.7 also has all wipes at one place. :D
[Wildfire Android Development] eventcom:
ha, didn't know :o
[Wildfire Android Development] Slymobi:
wow ive been in a coma or something!!! cwm version is up to 5.2xx? lol where's the link ;)

having an all wipe function can have its advantage but ive faced issues with 5.0.2.7/5.0.2.8 and some earlier versions of 3/4 but the most reliable version ive found to be 5.0.2.0.

at the end of the day they all do the same really.

R.V.3
[Wildfire Android Development] Wasimk32:
LOL :D

i didn't even notice what I'm reading and writing :D

i guess i need to get my eyes checked(brain as well :p)!

anyway,can you please provide a proper link for 5.0.2.0 ?

the one in wildfire index thread is actually 4.x.
[Wildfire Android Development] Slymobi:
lol. yes i know its a sneaky v4x version hidden in a PC49 hang 5 i will make a PC49IMG.zip to flash,back in a minute........

........ ok here you go

http://db.tt/uKeoMPs9

R.V.3
[Wildfire Android Development] Wasimk32:
Thanks mate. :)
[Wildfire Android Development] eventcom:
LOL

I haven't tested but I'd guess the zip's in the WF index thread are correct, though
[Wildfire Android Development] Slymobi:
well not quite,the PC49IMG for cwm 5.0.2.0 contains cwm 4x thats why i made a new one myself. its really easy...... using a PC49IMG.zip you extract and delete the recovery.img and replace the cwm (renamed recovery.img) archive it as zip and your done.

R.V.3
[Wildfire Android Development] eventcom:
yep, clear, sry I've been referring to the not-PCIMG49-zips (I know about the false one because I flashed it myself lol)
[Wildfire Android Development] TheCJMan:
Dead Link?

Hi

It seems the link on the first post is dead, or is it just me??
[Wildfire Android Development] Qmaster11:
Nope, they're not working
[Wildfire Android Development] joshkun:
If you notice the date it's from September last year. Maybe that's the reason. :confused:
[Wildfire Android Development] TheCJMan:
Dead Link?

Hi all

I am looking for CWM 5 and any tools I need to run/flash after upgrading from CWM4.0.4

The links in this forum seems to be dead...

thanx
[Wildfire Android Development] joshkun:
You can find it here

http://xdaforums.com/showthread.php?t=1483487 :)
[Wildfire Android Development] mazterjay:
Dead links

Like I said. Dead links.. :rolleyes:
[Wildfire Android Development] joshkun:
You did not try my link cause it's not dead yet http://xdaforums.com/showthread.php?t=1483487

And please try to search a bit. befor asking. :D
[Wildfire Android Development] joshkun:
Update

CWM 5.0.2.8 her => http://xdaforums.com/showthread.php?t=1566677&page=3 :cool:
[Wildfire Android Development] t.padelis:
It also has support for offmode charging :D
[Wildfire Android Development] jokergermany:
link down :(
[Wildfire Android Development] 3xeno:
Wipe /system using Recovery, and reflash the ROM you are using. This happens because Unrevoked installs its own version of Superuser, which clashes with the one in the ROM.
[Wildfire Android Development] rseke:
Thanx, i solved problem with reinstall. Remove old su binary and install new one.

Work perfect now. Thanx for help.

But i have another problem now,why my old clockworkmod come back,when i reboot from rom manager which i use he reboot me to old clockworkmod,and in info he says i have old clockworkmod,but if i shut down the phone and then i go to recovery mod i have new one which i install,how can i fix that problem with rom manager?

.Any suggestions
[Wildfire Android Development] zyonee:
Updated OP to version 4.0.0.0.
[Wildfire Android Development] kitaro2003:
error ... firmware files sees but does not set :(
[Wildfire Android Development] qtotter:
the installation went well, but i cannot mount my sd card with this version...

went back to v3.2.0.0.
[Wildfire Android Development] kitaro2003:
same problem...
[Wildfire Android Development] zyonee:
This was mentioned in the first post, it's a bug in the CWM sources and I haven't found a complete solution yet, but merely a half-way workaround.
[Wildfire Android Development] zyonee:
Added back the 3.2.0.0 version in the OP so you won't have the /sdcard mounting issue. Hopefully it can be resolved soon, so we can start using the 4.0.0.0 version. Sorry for the inconvenience. :)
[Wildfire Android Development] aq79:
No It would not create any problem, It will update your recovery.

you can also use ROM Manager to boot into this recovery version with 2.x.x.x still available (Power+volume-down) if you just flash the zip from recovery you can use ROM manager to boot into this recovery version. I prefer to use new recoveries from ROM manager

correct me if I am wrong
[Wildfire Android Development] s0ulbl5d3:
I got screwed up...i made a wipe and now i can't flash rom from recovery or any zip file it says it can't mount e:/sdcard...any suggestion on how to fix this...

How can i return to 2.5 when i cant boot the phone or i cant flash any rom?

FYI: NO ROM I INSTALLED ON MY PHONE RIGHT NOW SO DEFINETELY I CAN'T USE UNREVOKED TO RETURN TO 2.5. I GUESS I CAN ONLY DO THIS IF SOMEONE HAS A CM7 ROM THAT CAN BE FLASHED ON THIS RECOVERY.
[Wildfire Android Development] zyonee:
Use your computer:

adb shell umount /sdcard

This needs to be done before every file operation in the buggy recovery. At least you should be able to flash a ROM.

CM7 should flash also with 3.0+ recoveries.
[Wildfire Android Development] kitaro2003:
Will let down the file PC49IMG.zip([Recovery] ClockworkMod v3.2.0.0) in the root of flash card, go to the bootloader, would scan for updates, the volume up to confirm the installation, reboot, done!
[Wildfire Android Development] metapolis:
Wildfire off, PC49IMG.zip in the root of flash card. start wirdfire, it find the file but nothing happens. no possibility to scan for updates.. Any help
[Wildfire Android Development] zyonee:
People with no installed ROM and non-working recovery (can't mount /sdcard), did you try to do "adb shell umount /sdcard" before trying to flash a file?

Also, try mounting and unmounting USB storage, I don't know if it will work, but just maybe it will. You should be able to use the adb shell example above. Let me know if it works.
[Wildfire Android Development] metapolis:
I have a mac and don´t really know how to do this. Any help?
[Wildfire Android Development] kitaro2003:
Before you do anything, wait for positive feedback in the forum, and first make sure that you will be able and know how all of it back....
[Wildfire Android Development] zyonee:
Try to google for instructions on how to install adb. Once you have it all set up, you can use this command in a terminal before entering a file list in order to flash a CM7 zip file:

adb shell umount /sdcard

Enter it when you are already in the buggy recovery just before you select "Install zip from sd card". You may have to add the word "sudo" and a space before the adb command if it won't allow you to communicate with your phone.
[Wildfire Android Development] zyonee:
I edited 4.0.0.2, adding j_r0dd's mods and compiled it. Works well on Nexus One and Nexus S. No more sdcard mounting bug, it's been fixed. Can't test it on any other models myself. Updated first post of this thread.
[Wildfire Android Development] s0ulbl5d3:
@ zyonee...i'm having a problem setting up adb... is there any other way.
[Wildfire Android Development] zyonee:
Not that I know of, but there are really many step by step guides for adb on the web. Just keep trying. When "adb devices" returns your phone's info, you're ready.
[Wildfire Android Development] s0ulbl5d3:
does the cwm 4.0.2 version which is just posted on the 1st page already fixed this issue?
[Wildfire Android Development] zyonee:
If it's the sdcard issue that you're referring to, then yes, it should be fixed. Works well on nexus one, nexus s and desire hd.

Or did you mean about adb connectivity? That needs to be settled in your computer's os, not in the recovery.
[Wildfire Android Development] qtotter:
zyonee,

thanks for your quick move! i have confirmed i can mount my sdcard with 4.0.0.2 now.
[Wildfire Android Development] s0ulbl5d3:
i'm refering to sd card issue. i'm stuck up now can'y make this adb work...by the way how i can use adb in recovery...will it work?
[Wildfire Android Development] zyonee:
Great!

Yes, adb will work in recovery just as if you've booted your phone normally. What you'll need to do (once your adb connects properly to your phone) is to actually unmount the /sdcard partition in order to let the recovery itself mount it when displaying the file list so that you can flash a CM7 ROM. That's the important step. Once you've flashed, just boot up and then you should be able to use unrevoked 3.14 to change the recovery.
[Wildfire Android Development] metapolis:
Hi, I can use sdb on my mac. Now, with ./adb devices I recieve:

ups:platform-tools Metapolis$ ./adb devices

List of devices attached

HT07FPY04572	recovery

Ok, now I use the command ./adb shell unmount /sdcard and the result ist:

ups:platform-tools Metapolis$ ./adb shell unmount /sdcard

/sbin/sh: unmount: not found

ups:platform-tools Metapolis$

I also used the command ./adb shell umount /sdcard but it does not worked. Without ./ it does not work.

Any help?
[Wildfire Android Development] zyonee:
Try this:

./adb shell

(now you get a shell prompt starting with #)

umount /sdcard
[Wildfire Android Development] keyra74:
flashed to 4.0.0.2, no usb mount error

couldn't flash from fastboot or recovery so i used :

flash_image recovery /sdcard/recovery.img