yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] madmaxx82:
You are right!

I'm sorry because of my ignorance.

I didn't think further, of read-modify-write, where this makes sense.

But also without extents, it does.

So we should add that for ext3 too. Although it might be much better to migrate to ext4 anyway as the difference would be bigger, than tweaking ext3.

About my stupid "make you happy" comment. I didn't mean you, but -like you said- the community who is using those scripts which use that parameter..

So they can safely use 4ext without fear of less optimization.

That's why I'm using that parameter in 4ext anyway, although I didn't think it to have any possible positive effect.

And I'm now glad I did.

It's very important that the recovery uses the same optimizations any script does, because otherwise any user would need to rerun any alignment script every time after restoring a backup as this involves formatting the partition.

Thnx for the discussion, otherwise I'd still be blind and would never have researched on that topic any further.
[Desire Android Development] madmaxx82:
With 2.1.2 it was possible that any text output ended up above the progress bar, because the lowest possible position of any text was set too low.

Where does it hang? What do you see exactly?
[Desire Android Development] Sebby:
madmax

can i still use custom mtd with the recovery v2.1.3
[Desire Android Development] madmaxx82:
Nothing has changed in this regard from previous versions, so yes ;)
[Desire Android Development] Sebby:
madmax

can you tell me how i can see all my partition size's with adb

cant remember how to do that
[Desire Android Development] madmaxx82:
For partitions on your sdcard:

adb shell /sbin/parted -s /dev/block/mmcblk0 unit MiB print all
[Desire Android Development] Sebby:
no i can see the size of my ext in your recovery

but for the system,data,cache

or can you make me a recovery 2.1.3 that it displays also the system data cache

i no you dont like it but if i want to use custom mtd

so i can see if my custom mtd is correct size
[Desire Android Development] madmaxx82:
I will include that in the next version.

For now the simplest way doing that is :

adb shell mount /system

adb shell mount /data

adb shell mount /cache

adb shell df -h

You can also do that when your device is not in recovery.. then you don't need to mount those partitions first..

When your Desire is fully booted, just use adb shell df -h and you will get all the info.
[Desire Android Development] Sebby:
oke madmax thanks for the info:D

your recovery keeps getting better and better:D

more and more people are using it:D

keep up the good work my friend.....:D
[Desire Android Development] madmaxx82:
Thank you very much :)

And good luck to you with your job!!
[Desire Android Development] beanbean50:
Hi max,

I've been changing my Hboot every now and again and currently using stock Hboot, I just tried your df -h trick and wondered if my partitions look perfectly normal to you?

Filesystem Size Used Available Use% Mounted on

tmpfs 202.3M 64.0K 202.2M 0% /dev

tmpfs 202.3M 0 202.3M 0% /mnt/asec

tmpfs 202.3M 0 202.3M 0% /mnt/asec/download

tmpfs 202.3M 0 202.3M 0% /mnt/obb

tmpfs 8.0M 0 8.0M 0% /app-cache

/dev/block/mtdblock3 250.0M 164.8M 85.2M 66% /system

/dev/block/mtdblock5 147.6M 31.9M 115.8M 22% /data

/dev/block/mtdblock4 40.0M 1.5M 38.5M 4% /cache

/dev/block/mmcblk0p2 1007.9M 301.4M 706.5M 30% /sd-ext

/dev/block/vold/179:1

13.7G 3.3G 10.4G 24% /mnt/sdcard

/dev/block/vold/179:1

13.7G 3.3G 10.4G 24% /mnt/secure/asec
[Desire Android Development] suiller:
yep I totally agree... this rec is a true (welcome) surprise :cool:
[Desire Android Development] John_Blaze:
What was it ole boy called 4ext awhile back? Rockcovery! Yea.. :D ;)
[Desire Android Development] mattman83:
That's the parts you need to look at (system, data, cache) and that looks absolutely fine for stock hboot.

M.
[Desire Android Development] Borat38:
To which directory does 4Ext save its nandroid backups? I can't seem to find them in the original nandroid folder (I came from Amon_Ra_2.0.1)

EDIT: Found it using Root Explorer. Sorry for taking up space.
[Desire Android Development] John_Blaze:
It saves mine in clockwork> backup

sent from my awesome fone
[Desire Android Development] sibere:
No worries mate, I had to learn this also at some stage in the past before adding this option to my script :)

Yep, that's why there are two important things: partition alignment and data alignment (done with the stripe option) inside the partition by the filesystem itself.

Ho well why not? This will not cause any arm anyway :)

At least it cannot have bad effects ;)

Once the data has been written unaligned, it remains unaligned. The only problem is for writing, reading unaligned data doesn't cost anything performancewise.

If you wanna realign the data, it has to be re-written with the stripe/stride options enabled.

You're welcome! That's the right way to learn new stuff :)
[Desire Android Development] madmaxx82:
Of course, the same applies to blocksize.

Edit: Alignment should affect read speeds too. Not because of read on modify write which is the problem with newly data written and garbage collection, where the complete erase block sized block needs to be erased, and any valid data moved, but with other alignment factors like partition alignment and blocksize for example.

BTW this renders any script you might run completely useless as long as the user uses backup/restore functionality.

Because on every restore of a backup, recovery first formats the partition (was always like that in cwmr).

And that's why I use these parameters in 4extrecovery when ever recovery formats an ext4 partition since I support the Desire..
[Desire Android Development] madmaxx82:
Sorry for the late reply!

I see you already got an answer ;)

I too think it looks good :)

thank you :)

Hahahaha thank you!!
[Desire Android Development] beanbean50:
Hi max,

would it be possible in your next release to be able to name the backup you want to backup or is that mission impossible hehe
[Desire Android Development] madmaxx82:
Will be possible in a future release ;)
[Desire Android Development] morgan39:
Hi madmaxx82,

When we change Rom, normally we need to make a Wipe data/factory reset, Wipe cache and Wipe Dalvick cache.

Would it be possible in your next release to be able to have a menu option with "Wipe complet for new Rom" (for example) and this option makes the three wipes herself without further elections?

It´s not hard work wipe on three steps but if you can simplify can be better ................

Thanks a lot for hard work and a great Recovery. :D:D
[Desire Android Development] madmaxx82:
Wipe data/factory reset should include cache and dalvik cache already. Just look at the text output ;)

Also there is an option "wipe all" already, which wipes everything ;)
[Desire Android Development] morgan39:
Ok, I did not know wipe factory reset for that ; so, wipe all is the same as wipe factory reset?

Thanks
[Desire Android Development] madmaxx82:
No, wipe all formats boot (although not necessary, but someone wanted it), system, cache, data, sd-ext(2) which includes dalvik of course.

But wipe data/factory reset should format data, cache and dalvik.

Verify it by watching the text output when you use it!
[Desire Android Development] suiller:
I confirm 2.1.3 working as expected: wipe/backup/restore/etc... tested under oxygen 2.2.1 (GRJ90 - 2.3.5)

as always thank you ;)
[Desire Android Development] John_Blaze:
Good moooorning MadMaxxx!! Recovery is working just fine.. start up time 3-5 secs. nothings wrong jus saying goodmorning.. hahaha :D
[Desire Android Development] bmonster:
I'm still here :D and still having no problems.

Boot times are a little slow, but its not a problem.
[Desire Android Development] Droidxda:
The flash is perfect, now i ll try Rom Manager :p

best recovery i meet
[Desire Android Development] angusc:
John how do you get that fast boot in to recovery. Mine takes at least 40 seconds to get there.

Sent with Desire
[Desire Android Development] John_Blaze:
I was having that same problem a couple days ago.. idk i guess it jus worked itself out. Beats me.. lol
[Desire Android Development] Moe5508:
OK guys, don't flame me now if this request has been made yet but @madmaxx, can you please include the functionality to flash "img" image files in this tool? Think it would be awesome then we can flash HBOOT img files and other such directly from recovery...
[Desire Android Development] madmaxx82:
thnx ;)

Good morning!! Great to hear :)
[Desire Android Development] madmaxx82:
Thank you :)

Angusc, please try deleting your 4ext folder on sdcard.

First boot after that could be slower, but the second after that is normal.

Also please install 2.1.3 if you haven't done already.

And last question: do you use any themes?

Edit: Themes in version 2.1.3 shouldn't have such a big impact on startup time anymore as in earlier versions.

Also it's really interesting.. never got any report about a delay from a user of any other supported device. Just from Desire..

But this will be improved ;)
[Desire Android Development] madmaxx82:
Flashing hboot and splash are things that can permanently brick your phone.

Those things should be flashed via fastboot and not by recovery.

For me this is too dangerous.
[Desire Android Development] RevoWution:
Been using v2.1.0 as my permanent recovery, and I'm loving it.

However I do have one question. Is the speed of 4extrecovery drastically affected by whichever custom HBOOT I currently have flashed?

Reason I ask is because 4ext used to run/load within 10-20 seconds after I enter RECOVERY (while I was on AlphaRev and Revoked's Revolutionary HBOOT), but since I flashed AlphaRev's Data++ HBOOT (wanted to try out LeeDroiD's GB HD port), it takes ages (I timed ~5 minutes once) for 4ext to load up and become usable. In fact, quite a few times, 4ext failed to load altogether.
[Desire Android Development] johno168:
is it possible to restore clockworkmod recovery backups with this recovery?
[Desire Android Development] madmaxx82:
Thank you!

Are all your partitions ext4?

Could you try a restore if you have time? ;)
[Desire Android Development] ghiki:
WOW! Very "vitaminized" recovery, i go to try it ;)
[Desire Android Development] madmaxx82:
:)

Thank you!

Please wait an hour or so.. I will upload a new version that fixed romname detection with some roms + fixes the error when creating a backup one user reported ..
[Desire Android Development] Muxeu:
I have one ext4.

Restored sd-ext from Advanced restore successfully

sdcard -> fat32 -> 7141 MB
sd-ext -> ext4 -> 1023 MB
....
Restoring sd-ext...
Found 4EXT info for /sd-ext -> ext4
mke2fs 1.41.12 (17-May-2010)
Filesystem label=sd-ext
OS type: Linux
....
Writing superblocks and filesystem accounting information: done
....
Restore complete!
[Desire Android Development] madmaxx82:
Thnx, then it is ok :)
[Desire Android Development] ziggy1001:
Just a quick question couldn't find and info in the thread on this

I aligned my Fat 32 partition via this method post #2

HOWTO: Increase write speed by 'aligning' FAT32

And the recovery says Fat 32 not perfectly aligned, so would using your recovery to partition my sd-card from scratch make an improvement?
[Desire Android Development] madmaxx82:
Yes, it will create the fat32 partition on a start sector which is aligned to 4k sectors.

Then if you want to get the rest out of it, you have to repeat the step from the link you posted :)
[Desire Android Development] madmaxx82:
New version.. it should now identify all or at least most of all roms properly + some bugs fixed.. hope I didn't introduce new ones :D

Could someone please test that?

edit: This test version prints the rom name 2 times on boot, I know :D
[Desire Android Development] tinker2000:
I tried the check MD5 function and it failed, advising me to report this bug.

Excellent work by the way, than you
[Desire Android Development] madmaxx82:
Thank you very much :)

Yes, I'm working currently on exactly this issue :D

It fails if the path is very long..
[Desire Android Development] tinker2000:
/sdcard/My Documents/ROM Updates/SGBS was the path. Thanks
[Desire Android Development] madmaxx82:
Already fixed..

Will upload the new version now.

Could you maybe test it? Md5sum checking of your example path which previously failed, rom name detection + backup/restore?

Only if you have time for that :)

If this is successful (it is for me) then I'll update the first post :)
[Desire Android Development] madmaxx82:
Here is "potentially" rc1 :)

Md5sum bug fixed, should detect all romnames (at least the 14 I tried :D )

Please someone test a few things.. it doesn't have to be much..

Then it's easier for me to decide to release it or not..

Thank you!
[Desire Android Development] madmaxx82:
Ah really funny.. I forgot to attach it to the post.. :D
[Desire Android Development] Sashtheflash:
i just flashed your recovery and then tried to flash radio.. soooo why is radioflash no longer supported dont really understand the script talk when i try to... so I decided to flash Leedroid 3.0.8.2 I did a full wipe and flashed it... goes till second boot screen... doesn't go any further..worked on amonra sry for asking but dont know what this issue can be
[Desire Android Development] madmaxx82:
Yes that is strange..

Can you please try the version I just posted 10 seconds before? :D
[Desire Android Development] madmaxx82:
BTW: Why don't you flash radio with fastboot / in HBOOT? Just want to understand (coming from an incredible s, don't have a desire..)
[Desire Android Development] Sashtheflash:
now it worked.. strange.. can you fix the radio flashing or isnt this possible?
[Desire Android Development] madmaxx82:
I think it worked NOW, because I accidentally changed the kernel in the version before (not ext4 compatible)

What do you mean by radio flash?

What exactly is it you expect to have in recovery which is not there?

Is this something you have in standard clockworkmod recovery and I ripped it out?

Is there a menu item missing, or how do you do that?

Apply update.zip maybe?
[Desire Android Development] rophaq:
md5 checksum please for this new one, just to be safe, nothing corrupted.:)
[Desire Android Development] John_Blaze:
Sure enough.. :D I did when i first switched to 4ext
[Desire Android Development] johno168:
Thank you! This is the best recovery to date!
[Desire Android Development] DroidRevenge:
I wanna try but...

Hi,

i wanna try this recovery but i can't understand how to install, i have tried:

1 - ONE CLICK method but it doesn't work

2 - reboot in fastboot mode and typed command "fastboot flash hboot recovery v2.1.3.img" but it tells "FAILED (remote: signature verify fail)"

Now i wanna avoid to brick my device and so i am asking what i have to do.

10x

P.S.: i am running CWM recovery at the moment...
[Desire Android Development] Droidxda:
Hi, you need to be S-OFF to use fastboot command, even you can try the simple methodes : PB99IMG.zip
[Desire Android Development] Droidxda:
Hi Max,

Some problems with the 2.1.3 to mount the sdext in recovery.

message 'unable to mount /sdext, bad command or missing option'

thing about busybox problem.

I try to manually mount the /sdext (by th recovery menu) it's ok, ad i could flash my rom after this.

Any idea ?
[Desire Android Development] madmaxx82:
Hi, when did you get that message? When installing a rom maybe?

Could be the installer script trying to mount /sdext expecting it to have a certain file system or something else.. as in cwmr it would be predictable after wiping data that you are on ext3, while this doesn't apply to 4extrecovery.

That's one reason I can think of. A command like mount("ext3",......); would fail in that case.

Just one possible reason.

I'd need the recovery.log..
[Desire Android Development] DroidRevenge:
I am not a noob but i don't understand.

I have:

- copyed img file to sdcard with name "PB99IMG.ZIP"

- from console "adb reboot bootloader"

and now?
[Desire Android Development] Droidxda:
Excuse me trying help you

nothing to do more, the bootloader will detect the pb99img.zip and flash the recovery itself
[Desire Android Development] DroidRevenge:
mmh... then there is somthing wrong!

In my procedure i mean!

Once in bootloader it says nothing, 0, nada...

:(
[Desire Android Development] madmaxx82:
Wow! I wouldn't use my recovery if it would take so long to boot myself :D

I can't say that, because I don't have a (working) desire to test.

It would be interesting to see if others with the same hboot you mentioned have the same delay. So we could nail it down to that.

Will take a look at it.
[Desire Android Development] madmaxx82:
Sorry for the following dumb questions:

- Windows users often add a second .zip to the extension as they often have turned off displaying of file extensions.

- You mentioned you downloaded the image and named it PB99IMG.zip.

You did download "4EXTRecovery v2.1.3 PB99IMG to flash via bootloader" didn't you? And just renamed it PB99IMG.zip, not extracted it? And you put it onto the root of your /sdcard?

- Which hboot do you have? Patched with "eng hboot" functionality or without (for example s-offed by XTC Clip)?

Because it's strange that fastboot doesn't work although you say you are S-OFF and most of you are using alpharevx where they patched in eng hboot functionality.
[Desire Android Development] DroidRevenge:
I am not sooooo nooooob to apply 2nd .zip extension... sorry...

I am S-ON, never wrote i am S-OFF, must be S-OFF?

Info about my device:

S-ON

HBOOT 0.80

RADIO 5.17.05.80

10x
[Desire Android Development] bugfix2k:
I think that hboot is a bit old.. maybe not compatible with 4ext?
[Desire Android Development] madmaxx82:
I hate that term noob!

How am I supposed to know what knowledge you have?

If someone fails in installing it I must ask a few things, because they happen quite frequently.

Droidxda already told you that you need to be S-OFF for flashing via hboot and you didn't answer him you were S-ON.

If you are S-ON you need to either use unrevoked to "flash it" and/or use the fake flash version ;)

But you might consider to S-OFF anyway ;)
[Desire Android Development] madmaxx82:
No, 4ext works on any hboot version ;)

If he is S-ON he cannot flash things that way ;)
[Desire Android Development] DroidRevenge:
Ok thanks, i have lost "NEED TO BE" in the droidxda's post.

10x again
[Desire Android Development] Droidxda:
The best , you are old jedi :p

mount("ext3", "MMC", "/dev/block/mmcblk0p2", "/sd-ext");

I thought that, and i totally forget to check that stupid ligne :p

thank you
[Desire Android Development] madmaxx82:
Np!

If you have any questions on how to use the fake flash version or anything else, just post!
[Desire Android Development] madmaxx82:
Hahaha :D

BTW: I don't understand why most updater-scripts don't just mount using the "native" mount command. Since we have different file systems, it would make things so much easier..

Otherwise you need things like assert(mount("ext3", "EMMC", "dev...") || mount("ext4",...) );

run_program("/sbin/mount", "/mount point"); will work all the time, on any device, regardless of file system.

You know that, I know that, but still hardly anyone does it like that. Wonder why.
[Desire Android Development] Droidxda:
By the way, i didn't know the syntax or the command to pass through updater-script, so thank you for this run_program(" "); i like it

i should look for this updater-script command,do you have a link :p
[Desire Android Development] madmaxx82:
Sorry no link, but run_program works like that:

run_program("<path_to_executable>", "param1", "param2", ....);

;)
[Desire Android Development] Droidxda:
It's ok, thank you for that
[Desire Android Development] RevoWution:
Cheers for the response, madmaxx82 :)

Upon further testing, it appears it was extra long that particular time because I had flashed a ROM but had wiped the data, so maybe it was conflicting somehow.

Since flashing and running LeeDroiD's HD port, 4extrecovery loading times have been much faster (~1min now).
[Desire Android Development] p1yke:
I love the recovery but the start up time I have witnessed is about a minute. I am s off but current have the h boot table and tried all forms of the recovery, I have found that it is takes about a minute with all roms I have tried. I have tried everything that has been suggested to improve the start up time but with no success. The start up time is a ball ache to be blunt but it is worth every second.

Great work
[Desire Android Development] John_Blaze:
Wow! 1 min is still pretty slow. Mine used to take up to 40 45 secs and i think one time over 1 min.. but seems its worked itself out somehow and now it only takes about 3-6 secs.. Maybe repartioning my sdcard helped.. Idk
[Desire Android Development] live_0978:
Very slow on my desire bravo cm7 r2 hboot running any ROM. Takes couple mins most times.
[Desire Android Development] RevoWution:
Yeah I've also been thinking maybe the type of partition you have affects the boot up time for 4ext.

I was using an SD card with Fat32 and ext4 partitions, and I found boot up times while with that setup was noticeably faster. Whereas I'm currently running Fat32 and an ext3 (for LeeDroiD's Desire HD ROM), which is slower than when I had an ext4 partition.
[Desire Android Development] John_Blaze:
Ok i jus entered Recovery and and it took roughly 12 secs wich isnt to bad.. but heres how i have my partition set.. seems to work well with the rom im running ( Oxygen 2.1.6 ) and havent had no other problems

View attachment 683305
[Desire Android Development] madmaxx82:
That's disguting :D

Need to really improve that badly!

BTW: I hope I'll get a working (this time :D ) Desire soon, so that I can also enjoy seeing boot times of 5 Minutes :D
[Desire Android Development] MrPontus:
(solved somehow;edit2)

I don't know if it's a bug or why, but 4EXT 2.1.3 says on my old Desire that "sd-ext is not formated!"

why this message? the se-ext is formated and in use (btw. I now see that the "sd-ext" is called "data" here :S )

4EXT 2.1.3

Bravo PVT1 (GSM)

S-OFF, Oxygen r3 HBOOT (120/5/312MB)

ROM Oxygen 2.2.1

32GB Lexar class 10 SD card

edit: I understand if it's saying sd-ext not formated if it thinks that I don't have one,

but then if it doesn't exist a "format" wont help, the "partition" needs to be created first :D

edit2: rebooting phone and entering the recovery again, now the previously called "data" is called "sd-ext" as it should be, and I no longer have the "Warning: sd-ext is not formated!" message
[Desire Android Development] madmaxx82:
Yes maybe a strange effect from sdcard model / parted / partitioning.

But I'd try re downloading(!) and reflashing 4extrecovery.

If it still doesn't work for you after reflashing, please try the stable version!

BTW: I've had only one such case since it was stable on the Desire up until now. But detection of sd-ext partitions will change in an upcoming release anyway.

Edit: if it says it is unformatted, it detected the partition but no file system. The message also tells you that you can format it inside the 4EXT menu!
[Desire Android Development] MrPontus:
ahh, I did not see there was a next page (edited last post)

"rebooting phone and entering the recovery again, now the previously called "data" is called "sd-ext" as it should be, and I no longer have the "Warning: sd-ext is not formated!" message"

a little long load times (first time I thought there was something wrong)

but the Incredible S version is very nice :D (why the difference in load time? I know you are working on it)

after next release I think I will make a small donation, grate work :)
[Desire Android Development] madmaxx82:
Thank you very much :)

Great you got it working!

I'm not sure yet.

But the IS doesn't use any sd-ext partitions and parted is really damn slow which is still partly used for detection. This should be very much improved in the future.. apart from the IS being a little bit faster, there might also be other reasons for this.. will take a look at that when / if I get my Desire.

Good night! Already 4am here, but I guess it's quite late/early where you are too ;)