yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] 3f1f37:
@ MadMaxx

I have been using your recovery for a while now and I love your work dude, I don’t if this is possible or if it is already a function in the latest build but could you amend the recovery so that it can flash older zip files, specifically files that can only be flashed with CWM 2.5.0.7 as the weekend I flashed a zip file that 4EXT couldn’t flash an I was flabbergasted, I was like NOOOO WAAAAAAAY. So I had to reflash 2.5.0.7 flash the zip and then reflash 4EXT, by the way I am still using 2.1.0 final.

Aregato Goxaimas
[Desire Android Development] dirkw01:
Please see above my post #982 here and the following ones. :cool:

ROM Manager with its 'fake flash' of CWM 2.5.0.7 will do the trick. ;)

Cheers

Dirk
[Desire Android Development] LiooO:
Is the aligning done like this:

http://www.patriotmemory.com/forums/showthread.php?3696-HOWTO-Increase-write-speed-by-aligning-FAT32
[Desire Android Development] 3f1f37:
I am aware of booting into recovery via ROM Manager thus giving you 2.5.0.7 CWM I just thought there would be a 1 step solution, I mean 4EXT even flashing those old scripts. I suppose that is the only work around for now, Thanks anyway
[Desire Android Development] madmaxx82:
I will look into it, how much work it would be.. but I think there must be a reason why Koush dropped support for amend when CWM3 was released.

I remember a statement telling "was needed to drop support ..."

I'll see if I can do something, however there's already very much todo for the next version and the desire is the only device that still uses those old ril zip files..

BTW: If it is only the rils, it's far easier and faster to just fix those ril zips to use edify scripting.. the scripts are so tiny and basic, should be a matter of 10-30mins updating them.. or is there much of other stuff that uses amend the Desire community needs?
[Desire Android Development] dirkw01:
If your 'old' scripts have to stay, maybe you should consider to convert them with this converter to edify.

I have just discovered it, but haven't used it yet.

Cheers

Dirk
[Desire Android Development] artesano:
4EXTRecovery install v2.1.0 Final

I made a backup but can not find where you saved.

edit: I found it, the backup is in the folder ClockworkMod
[Desire Android Development] John_Blaze:
Just do what you must do Max.. you already do so much. We should move and leave the old behind and bring in the new.
[Desire Android Development] chichoko:
One small question!!! Can I flash the recovery via the Hboot without being s-off'ed??
[Desire Android Development] swemoza:
You cant flash recovery via fastboot if you are s on.
[Desire Android Development] chichoko:
Thanks for the insanely fast reply! Please check your inbox :)
[Desire Android Development] John_Blaze:
Question.. How are you S-ON and running Oxygen? :confused:
[Desire Android Development] John_Blaze:
Can anybody help me? I just tried to move something to my sdcard but it says not enough storage left.. but i tried a bigger mb app and it moved no problem. I have a 8 mb sdcard but it says in storage i only have 5.90 Gb total space. Is this due to how i have my sdcard partitioned?
[Desire Android Development] madmaxx82:
Hi Freak ;)

Yes this is possible.. do you have any sd-ext or swap partitions?
[Desire Android Development] John_Blaze:
Hey Max.. how are you bud? Heres a screen of recovery

View attachment 675156
[Desire Android Development] madmaxx82:
Everything OK ;) and you?

Hmmm.. would like to see you "raw" partition table.

Can you send me parted.log by mail?

You can get it via: "adb shell /sbin/parted -s /dev/block/mmcblk0 unit MiB print all > %USERPROFILE%\parted.log"
[Desire Android Development] John_Blaze:
Im good.. good as it gets anyways.

I can just copy and paste that in adb eh?
[Desire Android Development] madmaxx82:
good to hear :)

Yes, if you paste that line you don't need to first "adb shell".. just put it into a console window..
[Desire Android Development] John_Blaze:
Ok youre gonna have to jus give me what im supposed to put in command prompt window.. haha
[Desire Android Development] madmaxx82:
Hahaha

This "adb shell /sbin/parted -s /dev/block/mmcblk0 unit MiB print all > %USERPROFILE%\parted.log"

But need to go now. But will look at it in 6-10 hours when I wake up ;)

Good night!!
[Desire Android Development] John_Blaze:
This is what i got when i tried it

View attachment 675223
[Desire Android Development] madmaxx82:
Quite strange... instead of > %USERPROFILE%\parted.log rename parted.log to something else.. like parted1.log

And do that while your phone is in recovery ;)

Edit: I'm crazy... just use advanced/copy log to sdcard.. it will create some logs in 4ext folder.. just zip them and send them to mail mail address.

Then we might find out why your fat32 partition is not so big ;)
[Desire Android Development] John_Blaze:
hahaha i thought you were going to sleep. Yea i thought i could do something like that.. ok will have that in jus a few
[Desire Android Development] John_Blaze:
Here ya bud.. get ya some sleep though 1st. ;)

View attachment 675254
[Desire Android Development] jjdoctor:
The tutorial on Desire S forum is too difficult for installing via Terminal emulator...

Here it is simple:

1)download any of zip files and extract the "recovery.img" to Root of SDcard using a file explorer (i use X-plore)

2) in Terminal Emulator type:

thats it.... :)

Btw... thanks for the awesome recovery....
[Desire Android Development] madmaxx82:
Hey Freak ;)

Okay you have a 1GB partition after your fat32 partition..

If you don't use a rom that uses sd-ext, the simplest solution would be:

Make a backup of your sdcard, use the partition menu to "start from scratch" and create your partitions a new. If you only need fat32 and swap just select skip when it asks for sd-ext.. select a value for swap and the rest of the remaining space will be used for the fat32 partition..

IF you don't use swap, of course you can skip it too and all space will be used for fat32.

But if you are planning to change roms sometimes, then it's good to only have a fat32 partition of 6GB when your sdcard is 8GB, because then you can always create and resize additional sd-ext/swap partitions while keeping your fat32 partition intact (i.e. only add/remove/change any additional partitions that may come after your fat32 partition).

If you now distribute all the space to fat32 and sometimes later you need an sd-ext partition of 1GB, you would need to recreate your fat32 partition too, because there is no remaining free space after it.

Of course you could use any advanced partitioning program to shrink/grow the fat32 partition as needed too..
[Desire Android Development] madmaxx82:
Thnx, but why not just flash the whole zip file instead of extracting? ;)
[Desire Android Development] beanbean50:
Hi max,

I'm still using v2.1.0 RC1 has there been any major changes since then...?

:)
[Desire Android Development] madmaxx82:
Hi ;)

Looking at known issues:

v2.1.0 RC3: Roms with lazy updater-scripts that don't unmount /system before formatting failed to install

v2.1.0 RC2: Forgot the option to modify the toggle usb icon

v2.1.0 RC1: IS/DHD/DS: Very rare issue: got 4 reports about a backup which didn't restore properly. Still investigating

I would upgrade to final or 2.1.1b ;) 2.1.1b is like final but has additional sizes for partitioning.

Next version won't be ready during the next 7 days I fear.
[Desire Android Development] John_Blaze:
Ok so just what is Swap and Sd ext?
[Desire Android Development] beanbean50:
Thanks, will upgrade to the latest and take your sweet time for the next release, as they say 'the best things in life are worth waiting for' :)
[Desire Android Development] madmaxx82:
Swap is 512MB and sd-ext is 1GB.

Do you use a rom that needs sd-ext?

:D thnx!
[Desire Android Development] jjdoctor:
Well its just a different method to install your recovery... trust me I would prefer this way...

There won't be any extracting if you upload "recovery.img" in your attachments ...;)
[Desire Android Development] John_Blaze:
This what you were talking about?

View attachment 675772
[Desire Android Development] madmaxx82:
The problem is that not everyone has flash_image on the device.

It comes for example with rom manager. But if you have rom manager you can flash the flashable zip.

I have the OneClick version for download which does the same thing, but of course you need your phone connected to a pc for using that.

Yes ;)

Now it's correct.
[Desire Android Development] John_Blaze:
Ok thanks Max.. you the man! ;)
[Desire Android Development] stankyou:
Hi, I'm just dropping by to tell you that I flashed this recovery a couple of days ago since I was having problems repartitioning my SD card with EXT via my old recovery. Also, I was too stupid and lazy to use and learn gparted. :p

I got everything working again because of this recovery. The features are great. Great work!
[Desire Android Development] wingnutta:
Ok, very noobish question here but i just want to make sure. Heard a lot about this recovery so i want to try it. I am S-ON and currently using CWM 2.5.0.7. If i use the PB99IMG file - will that replace my CWM 2.5.0.7 permenantly? And is that the correct flashing method for S-ON?

I have looked for definitive answer, but thought i would double check first.

Appreciate any help peeps...
[Desire Android Development] John_Blaze:
You must be S-Off to flash
[Desire Android Development] angusc:
You can push it with fastboot?

Sent with Desire
[Desire Android Development] swemoza:
Yes you can push img file with fastboot if you are s off.
[Desire Android Development] madmaxx82:
Thank you very much ;)

You should use fake flash (update.zip)
[Desire Android Development] mattman83:
Hi just had some issues with 4EXT.

Latest Oxgyen would install fine over the top of previous install, however just got stuck at boot when doing a clean install (after full wipe). Leads me to think there's something not quite right in the wipe process.

Currently back on CWM and all going fine now, but I'll keep an eye on this as i do like the 4EXT recovery ;)
[Desire Android Development] madmaxx82:
Hi,

I'm not convinced that there's a problem yet. This version has been out for *quite* some time now, has been downloaded > 20.000x and there are still no known issues.

One reason why CWM worked, might also be related to the filesystem (for example).

If you wipe with CWM you will end up with ext3 on your partitions.. if you use 4ext it will wipe using the same fs currently on your partitions.

However you might also encounter a problem with CWM one day..

Just want to say that there are many variables why something might fail at the moment,

and that it's not always a bug in the version of recovery you are using at the moment. But of course it could be!

Edit: just imagine if 4ext was unable to install Oxygen! There would be a lot of posts (or they have yet to come and tomorrow we have 10 new ones with the same problem as you.. everything's possible :D )

Edit2: BTW I have ordered a Desire for development and for testing such cases.. should arrive tomorrow, maybe it will help me coding for the Desire in the future.

Edit3: The first thing I will do with it is install Oxygen :D
[Desire Android Development] John_Blaze:
I have never once had a problem doing a clean install of Oxygen. How long are you waiting?
[Desire Android Development] k3lcior:
Oxygen v2.2 doesn't fit oxygen hboot anymore, that's the problem probably.

Try to full wipe and flash v2.2.1 version.
[Desire Android Development] mattman83:
I was using CM7r2 HBOOT at the time, already had that covered ;)

My desire is PVT4 20K erase if that makes any difference... with a 512Mb EXT4 (which had previously been converted from EXT3 using this recovery - all been fine).

No issue at all installing 2.2.1 oxygen over the top of previous install, however it didn't like a clean install, had waiting up to 10 mins with no sign of life, just sat at splash the whole time. Tried this 4-5 times, recovering back to last known working install inbetween and kept having the same problem. This made me think it was more of an issue with the full wipe option than the install part of things... it did seem to pass over the wiping sd-ext part alot faster than CWM did - though that's just from memory, i wasn't specifically looking for issues at that point.

I'm not knocking the recovery at all either BTW - I'm more than happy to come back and probably will test again next time I'm doing a clean install (which is most oxygen releases) but just thought you may like to know.

And yeah i know there'd be alot of people screaming if it didn't work at all ;) but with all the hardware revisions of the desire sometimes it will work for alot of people - just not all. But anyway, you know what i mean.

M.
[Desire Android Development] madmaxx82:
That's one of those things I was referring to that make it hard to compare.

CWM has formatted your sd-ext partition ext3 again.

And.. formatting ext3 takes longer than ext4.

If you're ever again in doubt it's really formatting, just take a look at the log. You will see the output of mkfs.ext4 ;)

*sill waiting for my desire to arrive from england* Hope it will arrive today :D

Then maybe I'll have a little preview of 4ext-ng ;)
[Desire Android Development] John_Blaze:
Ok i see you said you tried v2.2.1 Ive only flashed v2.1.6 maybe there some difference in the rom.. idk.. can you point me to where to download v2.2.1 for BravoC and i will give it a try on my fone
[Desire Android Development] John_Blaze:
Morning Max! Or is it afternoon? haha Hey buddy youre gonna love that Desire.. as long as it isnt BravoC.. hahahahaha
[Desire Android Development] TheUntouchable:
Dont know if its allready metioned but the recovery shows only sd-ext and sdcard in the partion overview, but not the other partitions on my desire..

Using Cool-AceS-v8 with CM7 HBOOT S-OFF
[Desire Android Development] Smiffyboots:
I had this problem.

Either down grade your rom to standard froyo and flash the custom image with Unrevoked.

Or

Use the new Revolutionary tools to s-off your phone.

Both methods are easy for noobs like me that struggle with other methods :)
[Desire Android Development] madmaxx82:
Hehe hope so, though it was a bit crazy to buy it only for developing as I already have an incredible s.

Yes that was on purpose.. when I disabled that for the Desire, 4EXT was only showing file system types.. since on the Desire fs type for /system /data /cache is always the same, I disabled it.

Now that it also shows remaining free space it makes sense to activate it again.
[Desire Android Development] TheUntouchable:
Whould be very nice! :)
[Desire Android Development] Droidzone:
Hi madmaxx82,

Since 4extrecovery seems to check the kind of recovery everytime recovery starts up, could you add a piece of code to export this to a text file in /cache/4ext/rec.info or similiar file? That would be extremely useful for us who need to find the kind of ext installed. My script needs it to assess whether the user's partition needs to be converted. :)
[Desire Android Development] madmaxx82:
Hi,

what do you mean by it checks the kind of recovery everytime it starts up?

It doesn't check anything, because it knows what it is :D

I think I misunderstand you there.

However, what you want to do is already done ;)

I have also written a binary that checks its version. So roms that include it can check if the version they want to flash is newer than the one installed. Otherwise they don't flash.

The binary returns 1 or 0 so you can check that in updater-script.

If 4extrecovery is booted there is a file called /tmp/4ext_version.

You can just check if that exists.

If you want to have the binary to check its version, just send me a pm!
[Desire Android Development] Droidzone:
Oh darn.. lol..Guess I'm still fuzzy in the head after sitting till 4 am with the scripts of data2sd!

I meant it checks what kind of partition is present!! :D

It would be useful to interact with this..

But I see that you've already included it as sd_fstypes

However there is a bug in this.

cat /tmp/sd_fstypes
/dev/block/mmcblk0p1 2813 MiB fat32
/dev/block/mmcblk0p2 1025 MiB [COLOR=Red]ext2[/COLOR]

while the interface lists it correctly as:

cat /tmp/sd_fstypes
/dev/block/mmcblk0p2 1025 MiB [COLOR=Red][B]ext4[/B][/COLOR]
/dev/block/mmcblk0p1 2813 MiB fat32
[Desire Android Development] Droidzone:
And it if it helps you, the ext3 which was made by 4ext was formatted to ext4 by my script:

/system/bin/mke2fs -T ext4 -b 4096 -E stride=64,stripe-width=64 -O extent,^huge_file -m 0 -L userdata /dev/block/mmcblk0p2
[Desire Android Development] madmaxx82:
Hahaha

Everything's clear now.

Yes sd_types sometimes showing ext2 is a problem with parted (it's most of the time ext4 really).

When 4ext parses that file and finds "ext2" it will run a tune2fs -l to check for the correct file system ;)

Okay.. I could export that.

But I don't quite understand its usefulness since that would be a new version not used by many people..

But I don't have to understand it :D

I'm about to upload a new version with just a very little update: printing partition info also for yaffs2 partitions + more theming options + improved startup time if there is a theme installed that uses many different images.

This will be an unsupported release to shorten the time for the next major update which won't be ready so soon..

I could include that in that version.

Just tell me quickly. Finishing at the moment.

Edit: and tell me how the file should look like!

Do you need "device filesystem", or "mount_point filesystem"?
[Desire Android Development] Droidzone:
Rest assured, the 1500+ (No of downloads on 1st three days of release) users of Data2SD based Roms on ext4 do use it :D :D

Correct it only when you have time. I too use tune2fs to find out the version as of now. However a recovery with built in support is so much easier to work with.. :D
[Desire Android Development] madmaxx82:
BTW: if it is of interest, when the recovery restores a backup or if the user wipes or formats.. 4ext uses this to format in case of ext4:

-b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -E stride=64,stripe-width=64 -m 0

Although stride et.c. shouldn't be necessary as only setting blocksize would have the same effect if you are not using a raid :D
[Desire Android Development] Droidzone:
Thanks.. I'll keep that in mind. Excellent work, I've had most of my users change to yours, as preserving ext type is critical for my roms. It has done away with all the previous isses of CWM
[Desire Android Development] madmaxx82:
Thank you very much!

So, how should the file look like?

It's easy to add it now before I upload the new version..

<mount point> <fs type> ? or <device> <fs type>?
[Desire Android Development] Droidzone:
Can you add both? :)

<mount point> <device> <fs type>

We can parse it with grep and get what we need
[Desire Android Development] madmaxx82:
Okay done ;)

Will upload the new version soon.
[Desire Android Development] Droidzone:
Excellent, maybe I'll include your recovery in my next Rom :)
[Desire Android Development] madmaxx82:
Very cool ;)

Tomorrow I'll get my desire so I can try out your rom ;)

However still possible that this little update introduces new bugs, even though not much has changed.

The current version I'm working on is quite different so that I won't/can't put much time into that "2.1.2" release.

I hope it's as stable as 2.1.1b but this must be evaluated by the users :)
[Desire Android Development] Droidzone:
Cool.. I'll be happy to test out any alphas of your recovery if you like. I dont mind it being a bit unstable ;)
[Desire Android Development] madmaxx82:
Thank you! It's really good to have advanced users to test new versions before they are released! I will come back to your offer then! :)

But I just saw you disabled PMs..
[Desire Android Development] madmaxx82:
New version, more theming options

Because the next major version will take *at least* an additional week to be ready and will be a Beta when it arrives,

as it will be *quite* different to any previous version, here is a little unsupported update of the soon to be outdated code used in v2.x to keep you busy flashing :D

It's not the update with promised changes/additions, but introduces more theming options and some little improvements.
​

Changelog:

Improvements

:

Startuptime when there were themes with lots of different icons improved:

Except of the main background image, all images are loaded in the background after the recovery is ready.

-> so you can use it already even if the theme contained big background images which slowed down startup time even more on the Desire in previous versions.

Startup delay will be improved further, but this won't happen anymore for v2.x.

Filesystem info is now written to /cache/4ext/vol_info for any scripts that might want to check it.

New theming options

:

It's now possible to define a background image for any menu_item and its corresponding category.

While the user moves up/down any menu_items in main menu the background image changes "on the fly" to represent the item.

Menu item in 4EXT menu to reload the current theme.. so no restart is necessary any more when you change themes.

Of course the flashable zip of the theme must not reboot recovery, because it would render that option useless ;)

​

Desire GSM

:

md5sum: 47c11c15c3b90d3b85e6d8646cf2da06

flash via fastboot/AndroidFlasher: 4EXTRecovery_v2.1.2b_bravo.zip

md5sum: 6a38d77d347804ebbc00c1cdc805f565

flash via bootloader: PB99IMG_v2.1.2b_bravo.zip

Desire CDMA

:

md5sum: ca5505084bced365874f2305227c5eda

flash via fastboot/AndroidFlasher: 4EXTRecovery_v2.1.2b_bravoc.zip

Desire GSM & CDMA

:

md5sum: 65b2b916cdcee2d6bbebf88d60b65c91

fake flash: update.zip

This version is neither stable nor unstable.

Not much has changed so I hope it's as stable as 2.1.0 final / 2.1.1b, but this must be evaluated by you
[Desire Android Development] Droidzone:
Hey..just wanted to say that I've experimented with your recovery for conversion b/w ext3->4, and done a lot of backups/restores over the past hour, testing upgrades of roms and it works perfectly.

Your recovery is now an essential prereqisite for upgrading my rom :)

I've activated PM from you. I tend to get a truckload of PMs daily from newbies (most of which have already painstakingly been explained on my site), so I disabled PMs from users other than contacts. :)
[Desire Android Development] madmaxx82:
Ah I see, can imagine ;)

Thank you very much for testing and this very, very positive feedback!

My "baby" to be an essential prerequisite is really an honour for me :)

If you need anything else, just tell me!
[Desire Android Development] John_Blaze:
Well Max i jus flashed latest recovery and startup time for me atleast is still crap.. i do however have to icons in 4ext folder.. one is 108 kb and the other is 388 kb so is that to big?
[Desire Android Development] madmaxx82:
No that's not too big.

There are 2 reasons for startup delays: detection of sd-.ext partitions (will change completely in the future)

And themes with many or big images: that shouldn't be a problem now anymore!
[Desire Android Development] madmaxx82:
Reuploaded because of a potential autoreboot I had forgotten to remove, sorry :D
[Desire Android Development] John_Blaze:
Reuploaded what? Recovery?
[Desire Android Development] madmaxx82:
yes! v2.1.2
[Desire Android Development] John_Blaze:
Ok i just repartitioned my sdcard again to 512 for 1 ext and 0 for the rest.. lets see if that helps.. transfering everything back to sdcard right now.. will report back when done
[Desire Android Development] madmaxx82:
But you didn't do that because of speed now did you?

There's a misunderstanding then :D
[Desire Android Development] John_Blaze:
No.. there was an error in 2nd ext it was saying so i just made it 0.. having 0 for all of them the other day i wasnt able to restore my rom so i changed it. This is how i have it partitioned now.

View attachment 677606
[Desire Android Development] madmaxx82:
Ok, maybe it said something about not enough space available with the sizes you wanted to use?

Whiskey already has done some changing on the fly themes:

http://xdaforums.com/showthread.php?t=1174898&page=6