yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] madmaxx82:
That's because those screens are from Incredible S and Desire HD.

Yaffs2 partitions are currently not displayed inside recovery.

I still have to add that info. They were left out long ago wehn 4ext only displayed the specific file system types of partitions without any data about capacity or free space.

Back then it didn't make sense to print info about system data and cache on the devices with yaffs2 partitions, since the file system cannot change.

I didn't have time yet to include that. Will be done in the next or one of the next updates

They are however displayed inside the app.
[Desire Android Development] VekiCRO:
Yes,they are displayed inside the app.

Thanks for quick answer :)
[Desire Android Development] thanito:
I try to flash it via android flasher like I do every time (same with 2.1.3), but I get the following error:

The file "recovery.img" already exists/ followed by the above:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.IO.IOException: The file 'recovery.img' already exists.

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)

at AndroidFlasher.Log.run()

at AndroidFlasher.Log.timer1_Tick(Object sender, EventArgs e)

at System.EventHandler.Invoke(Object sender, EventArgs e)

at System.Windows.Forms.Timer.OnTick(EventArgs e)

at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

----------------------------------------

AndroidFlasher

Assembly Version: 2.0.5.0

Win32 Version: 2.0.5.0

CodeBase: file:///C:/Users/Tanito/Desktop/AndroidFlasher.exe

----------------------------------------

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5447 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.
[Desire Android Development] madmaxx82:
Please ask in the android flasher thread, obviously "the recovery.img is already there" :D

I can't support any errors of applications I didn't write or even use, as I don't know anything about them.

Why not just flash using the app or fastboot if you have trouble with your installation of android flasher?
[Desire Android Development] thanito:
Well i might go with the recovery updater:p
[Desire Android Development] madmaxx82:
App updated, new features per request:

- remount system rw/ro

- add to the context menu when a zip file is selected in file managers

- no need to download auxiliaries anymore

- bugfixes :)
[Desire Android Development] ogre_x:
Regression: doesn't show partition info on HTC Desire.
[Desire Android Development] madmaxx82:
You already sent me a report.

I already replied to you. Please try to do that and then tell me about your success/failure :)

Will solve this immediately.
[Desire Android Development] madmaxx82:
Problem solved :)
[Desire Android Development] sprooty:
no journal

Hi

Very happy with your recovery (and your shiny new app!), quick question though:

Does android (and 4ext) support ext4 modes other than journalled, ie ordered or writeback?
[Desire Android Development] madmaxx82:
Thank you :)

Yes it does, however 4ext always formats with journaling.

There are already settings inside the app and in 4ext.prop to enable fully customized format parameters also for tune2fs.

They are however not supported yet by recovery.

This will most probably be in the next update :)

Until then you need to use a script or do it manually after each restore or format (all recoveries format the partitions that are to be restored when you restore a backup)
[Desire Android Development] Bingley:
Hi,

Odd thing happening here on 2.2.6 rc4:

Partitioning sd card removing all previous partitions, for 1st sd-ext any size except 512 works: after selecting 512, skip, skip, yes: it says formatting sd card completed sucessfully; after selecting either ext3 or ext4 appears to have worked, only print partition info lists just:

sdcard fat32 (null) 7gb free - no ext4 partition is created. sd-ext does not appear in advanced backup, either.

This only seems to be happening on 512 size though - odd!
[Desire Android Development] madmaxx82:
Does this also happen when you reboot into recovery?

Maybe it shows your sd-ext then?

If there is a bug I must find and fix it, please can you repeat the steps you have made and then boot straight into your rom and immediately send me a bugreport checking the option to include the last recovery log?
[Desire Android Development] Bingley:
I just reflashed 2.1.3 rc2 and it worked fine
[Desire Android Development] madmaxx82:
Ok, but this doesn't help.

Could you please repeat the steps and then send me the bugreport including the log so I can see why it didn't work?
[Desire Android Development] TheUntouchable:
I think that doestn help to fix the bug.. ;)

EDIT: To slow.. :P
[Desire Android Development] Bingley:
yeah hang on. I don't have the new .img spare and as it's only available via the apk I've gotta work out how to reinstall and boot this thing now as I was hoping to do it all via the cli/recovery
[Desire Android Development] madmaxx82:
Found it! Bug confirmed!

Thanks for reporting!

Will work on fixing it now!
[Desire Android Development] Bingley:
That was quick! I'll reflash my working version, get phone online and update to hopefully-working update - thanks for the help!
[Desire Android Development] madmaxx82:
The strange thing is it really only happens with 512mb sd-ext ...

Sizes below or above work fine.

Hopefully have a 2.2.6 rc5 ready in the next hours.
[Desire Android Development] Bingley:
Exactly my thoughts. I'm still a newb but pretty knowledgeable about bits and bytes, and fairly confident with android flashing, modding etc. Little knowledge about this problem but simply selecting a diff size shouldn't invoke any diff procedure to cause problem, but there you go!

Thanks again, hope not too much work; intriguing oddity, though!
[Desire Android Development] madmaxx82:
Yes :D

News sent and known issues updated.
[Desire Android Development] madmaxx82:
Partitioning works, the partitions are created, sd-ext is also formatted, but it fails to detect the partitions later on.
[Desire Android Development] Bingley:
So it's a gnu parted bug of not reading the partition correctly? I see it's as page 170 here http://xdaforums.com/showthread.php?t=1154221&page=170 - I'm using an 8gb card, Lexar.

Not sure if I can be of any further help but will follow this thread as I'm kinda geeky and laerning = interesting :)
[Desire Android Development] madmaxx82:
Yes.. thanks.

Parted is not used for partitioning though. And not for formatting. which is good ;)

Will keep you updated :)
[Desire Android Development] l3zawi:
Max ... is the fixing errors for SDCARD working properly because when I fix sdcard errors and print partition info and check again for sdcard errors it tells me that errors was found even though I fixed the errors before ... strange thing
[Desire Android Development] madmaxx82:
It's EXTREMELY sensitive. Too sensitive! But it's useful nonetheless. As it fixes also serious errors.

Yes it's working properly!
[Desire Android Development] l3zawi:
Yes ... I noticed a speed increase in the ROM

tnx bro ;)
[Desire Android Development] madmaxx82:
Bug with partitioning fixed :)

np :)
[Desire Android Development] sprooty:
That's great, thanks!
[Desire Android Development] bugfix2k:
Bought Recovery Control from Market. Working flawlessly. Thank you very much madmaxx82!
[Desire Android Development] DirkStorck:
A short question. If I allign my ext partition using your recovery and restore it back from my nandroid will it be still alligned or does the restore of the backup override it again ?

Thanks!
[Desire Android Development] madmaxx82:
Thank you very much ! :)

You won't lose the alignment as long as you don't delete the partition and recreate it (not aligned)

The same applies to the ext4 filesystem. It's recreated on restore, but 4ext always formats using options that properly align it.

One of the next updates will include options for setting mkfs and tune2fs parameters manually which will then be used by 4ext.. so you can fine tune that.
[Desire Android Development] Sebby:
hello madmaxx

i have a backup off a rom with sd-ext as tar

now i won't to remove some files in the tar file

but when i restore the rom again the md5 checksum fails

please can you add md5 checksum on/off in recovery

or that you can make a new md5 checksum for that backup

and sorry i dont pm you about the apps backup option (forgot) busy

sorry i post this also in the desire s treat
[Desire Android Development] madmaxx82:
Ok then I will post my reply here too :D

Just open the app, go into manage your backups and let is check the backup you modified..

It will complain that the md5sums don't match and ask you if you want to correct that at your own "risk" :)
[Desire Android Development] Sebby:
but how can i do that when i already have done a full wipe

so i must restore a other backup then go to your apps and do the thing you say

that is not a good thing if you already have done a full wipe

in the begining of the recovery you had inplented does things but removed it afterwards

i only want to turn it off and then tru your apps change the md5 checksum
[Desire Android Development] madmaxx82:
I understand!

Ok, I will add that setting :)
[Desire Android Development] bmonster:
Hi Max,

Maybe you could get recovery to do the MD5 check before performing a superwipe.

I've also had this problem, where I've gone to restore a backup, with superwipe selected, its wiped my partitions, and then fail MD5.

Cheers

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

Ok, so I need to do the md5check inside the app before it reboots and tell recovery not to do another md5check.

Is that what you want? :)

When you do all that in recovery it wouldn't be possible of yourse since recovery doesn't know about which backup you would restore after wiping something.
[Desire Android Development] Droidzone:
@madmaxx..

You added dosfsck... Cool and thanks for implementing the suggestion so fast! :)

Can you tell me whether the recovery control app unmounts /data before rebooting? If not could you please add a lazy unmount to each of the reboot options? Since my roms switch nand with an ext4 file system, rebooting without unmounting can cause errors.. Cool work as always.. Koush's copyright seems directly intended against this app ;) Glad you found a solution so fast.. And thanks for keeping a free version for everyone..

TouchPal-d from my Desire running Supernova Extreme Rom - 450 apps and counting. .
[Desire Android Development] bmonster:
Or just get recovery to perform the check before doing the superwipe, then if it fails md5, its doesn't continue..

But having the app do the check is also an option.

Thanks.
[Desire Android Development] devil-kin:
Interesting.

I downloaded the latest tiamat kernel to install, went to 4ext recovery updater (2.0.7), picked the zip to install (without backup/wipe), and set it to go ahead.

Phone rebooted, ended in fastboot. Checked, the recovery is *gone*. Weird.

(it was the latest for desire, 2.2.6 RC5)
[Desire Android Development] madmaxx82:
Thank you very much ;)

I sync but don't umount. Behaviour similar to RM. Hope it's not too fast so a lazy would make sense.

Will add it of course :)

Ok, I will add it to the app then, because otherwise it would be much more work, since I'd need to parse the file more than once then.

Also if it does it inside the app before even rebooting it's easier to pick another backup or even fix the md5sums if needed.

Yes that's strange, but it has nothing to do with recovery or the app.
[Desire Android Development] madmaxx82:
Anyone there who would have some minutes to test an update?
[Desire Android Development] TheUntouchable:
Im already testin it am i right? ;)
[Desire Android Development] madmaxx82:
Haha yes, but not for the Desire I hope :D
[Desire Android Development] madmaxx82:
Got a tester :)

Thanks ;)
[Desire Android Development] Sebby:
madmaxx

i formated my sdcard and i see that it's format's the fat32 now

so now i don't have to format it again with gparted the fat32
[Desire Android Development] EViollet:
Issue with V2.2.6 RC5.

Hi.

I'm having a rather serious issue with V2.2.6 RC5...

I wanted to revert to a previous version of my ROM. So I installed the previous version using 4EXT. No problem.

But my ROM didn't want to boot.

So I tried wiping dalvik and cache. Quite strangely, dalvik wiped OK, but 4EXT keeps restarting each time I try to wipe cache:

I:Bitmap indeterminate6 missing header
I:Bitmap progress_empty missing header
I:Bitmap progress_fill missing header
done.
4EXT-NG postponed..
mtd: successfully wrote block at 0
I:Set boot command ""

-- Wiping cache...
Starting recovery on Mon Oct 10 14:43:32 2011

OK. Fair enough. I'll try reinstalling the correct ROM image. The problem is that I get the same result:

I:Bitmap progress_empty missing header
I:Bitmap progress_fill missing header
done.
4EXT-NG postponed..
mtd: successfully wrote block at 0
I:Set boot command ""

-- Installing: /sdcard/defrostsetup/GingerVillain3.1.zip
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
Starting recovery on Mon Oct 10 14:45:59 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)

What's also very amusing is that I can't restore my backup either:

I:Bitmap progress_empty missing header
I:Bitmap progress_fill missing header
done.
4EXT-NG postponed..
mtd: successfully wrote block at 0
I:Set boot command ""
mtd: successfully wrote block at 0
I:Set boot command ""
Starting recovery on Mon Oct 10 14:51:40 2011
can't open /dev/tty0: No such file or directory

Any ideas? My phone is currently basically bricked.

Please help.

Regards.
[Desire Android Development] madmaxx82:
Uninstall or reinstall your theme!

This bug that CAN occur sometimes, will be fixed for the next update!
[Desire Android Development] EViollet:
Thanks for your quick reply.

How can I uninstall the theme knowing that I don't have access to a bootable ROM, so I can't do it via the APK?

In advance, thanks.

edit: OK. Got it by mounting /system and removing the 4ext directory.

The ZIP files now flash again.

Thanks.
[Desire Android Development] madmaxx82:
I'll get you an updated recovery.

Please wait 5minutes.. will send you a pm.
[Desire Android Development] madmaxx82:
I have sent you a pm;)

The issue is fixed in the next update.

It was caused by the new code to save and restore the theme upon formatting or flashing.

So for the next update (today) this code will be deactivated completely which will prevent this from happening again..

Although I might have fixed it, it's not completely sure, so removing it is the only real solution for now.

It will be changed and reactivated for a later update, maybe a beta release.

known issues updated and news sent.
[Desire Android Development] madmaxx82:
Hey ;)

Yes!
[Desire Android Development] Droidxda:
if you need one, tell me :p
[Desire Android Development] steveathome:
Hi Max, just some feedback. The first update today would only boot into the Htc recovery. Your next update fixed it. running Sense-o-Maniac 1.4. :)
[Desire Android Development] John_Blaze:
Does anyone see anything wierd about this? This is my contents of my sdcard. Shouldnt it start from the top with A and go down like A B C D and so forth instead of up? hahaha

View attachment 746410
[Desire Android Development] erklat:
Is entering into recovery any faster compared to three-four versions ago?
[Desire Android Development] steveathome:
Mine has gone from about one minute after the Joker to about fifteen seconds. :)
[Desire Android Development] booce:
Help! I've made a terrible mistake and have got my phone (Desire) right old state and need some help please. I was S-off, Stock hboot and I was toying with flashing the CMR2 boot image. I decided not to and just put a different splash screen on. Unfortunately, it flashed the bootloader anyway and now I can't boot up or get in to recovery! I'm running ext4recovery latest version (2.27rc2) and the phone can boot in to the recovery menu (fast boot recovery etc). However, when I try to run recovery, it loads up and then exits the recovery only to reload it again. It never lets me in. Can anyone advise me on how to proceed?

*fixed it* sorry about the panic there ;-)

Booce
[Desire Android Development] skorpioneMM:
Flash another recovery or another older version off ext4 recovery and try again.
[Desire Android Development] madmaxx82:
You flashed the bootloader?

Hopefully flashing a new recovery will help.

I'd try it with 2.2.6 rc5: www.4ext.net/bravo.zip
[Desire Android Development] madmaxx82:
Thank you I will :)

Thanks ;) yes I noticed that, sent a news and fixed it. Changed build environment and my builds were completely broken for that time :D

Yes it should be very much faster.
[Desire Android Development] madmaxx82:
Just press the "sort by name" column once again and it will revert it :)

It only depends on your computer on how it displays that. You can use any ordering you wish :)
[Desire Android Development] booce:
Further adventures in flashing :-) Decided to go with CM7R2 after recovering from my earlier mishap with android flasher and got the boot image loaded fine. I then flashed ext4recovery that was posted earlier (2.2.6rc5) and it flashed ok. However, I still can't reboot in to recovery, it loads up and gets to the menu then it restart loading the recovery. Got round it by installing CWM 5.0.2.0 and that booted ok. I was coming from a stock hboot with insertcoin a2sd 1.1.4 on it and hadn't yet wiped caches or factory data. It's not a problem for me but I thought you might like to know.

Great recovery by the way, I much prefer it to CWM.

Booce.
[Desire Android Development] madmaxx82:
Thank you :)

Yes that is a strange problem.

Could you try it once more and afterwards if it fails, please boot up your rom and send me a bugreport using the app ticking the option to include the last recovery.log.

Then I might know more why it doesn't work on your device.

Did it work for you earlier? before you started with that?
[Desire Android Development] booce:
I'll be happy to have a look for the bug report but I suspect it may have been blown away when I got CWM on it, wiped caches and factory then installed my new CM7 ROM. Before this when I stuck to the stock hboot, ext4 always worked for me right up to the latest RC5. I'll try reinstalling it when I've got the phone built and settled and let you know how I get on. Thanks for the quick responses by the way!
[Desire Android Development] madmaxx82:
Thanks! That would be great :)

I just need the log and hopefully it will tell anything :)

It's really strange though since many people use that hboots you mentioned if I'm not mistaken and there are no problems with that.

I hope the problem can be found quickly.
[Desire Android Development] booce:
Ok, I'm guessing I did something strange as now that I have my rom up and running, I was able to install 2.2.7RC5 from the 4extrecovery app with no problems at all. I'm still on the CM7R2 hboot, so I really have no idea what went wrong there. Still, all happy now, got my CM7 and 4ext working nicely together.

Thanks for your help.

Booce
[Desire Android Development] devil-kin:
Unfortunately, this just happened again. The only thing I did today was upgrade to the latest recovery.

Did the upgrade of the recovery fail horribly or something?
[Desire Android Development] madmaxx82:
Great that it worked :)

I have a suspect.. where this could possibly happen when there are bad blocks.

Are you able to reproduce that everytime you flash a new version?

Please tell me, then we can see if a certain change helps.
[Desire Android Development] devil-kin:
It seems to be happening now all the time. I'll see if I can wipe the recovery flash through fastboot and then try to reinstall the recovery.
[Desire Android Development] madmaxx82:
No, please don't, your rom is working right?

Let's try an update!
[Desire Android Development] devil-kin:
Yeah, the rom works fine at this point. 4ext recovery updater works fine too.
[Desire Android Development] madmaxx82:
Thnx, I have sent you a pm.. did you try it already?
[Desire Android Development] madmaxx82:
Thank to devil-kin for testing!

If someone else runs into that problem one day, then flashing the update 2-3 times solves it. It's certainly caused by bad blocks on the recovery partition.
[Desire Android Development] bmonster:
I got the 1000th Thanks :)
[Desire Android Development] madmaxx82:
:D

That was a catch :D

Thank you :)
[Desire Android Development] teorouge:
Hello maxx, thanks once again for the wonderful recovery. I just updated the app and recovery but now I have both "4ext" and "4EXTControl" folder in memory card: can you make only one for future updates? May we delete one? Don't like messing up my sd! ;)
[Desire Android Development] madmaxx82:
Hi!

Thank you ;)

I did that already in version 2.0.6 or earlier..

It is strange that if you are running a new version of the apk the folder did not disappear..

It should have been removed automatically.

Are you really running 2.0.8?

If so and for some strange reason that folder still exists (4extcontrol) then just delete it :)
[Desire Android Development] teorouge:
I'll delete that and look for re-spawns, thanks for the tip! ;)
[Desire Android Development] madmaxx82:
So are you really running 2.0.8?

Did you start it one time?

It really should move it..
[Desire Android Development] teorouge:
I actually never run 2.0.8: I had a previous version, updated recovery and updated app. But didn't open that after upgrade.
[Desire Android Development] madmaxx82:
Oh.. I see.. after you started it, the folder should be gone ;)
[Desire Android Development] John_Blaze:
Well see.. you do learn something new everyday! Thanks bud :D