yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] madmaxx82:
Sorry for the late reply!

Regarding tar backups: no issues were reported again after this was improved in rc3.

Regarding fat32 check: this is far too sensitive.. that is why I changed the text to "MIGHT". It is enough to trigger it if you mount your sdcard.

I'm considering changing it to a complete repair only item.

You can repair your fat32 fs with it, but it can't be used to tell you if your fat32 file system is really corrupted.

@Leith51: Please send me a bugreport or an email regarding missing apps2d apps. We should take a closer look at that backup you restored and find the reason.

It doesn't mean that there is a bug, but it could be possible of course.

If there was a bug in the current version then I must fix it :)

I believe though that if there was really a bug, then it must have been in an earlier version where this backup was created.

I must leave the city for 2 days and it's much easier to communicate via email.

Thank you :)
[Desire HD Android Development] leith51:
I've not got apps2sd it was when I moved them 1 by 1 like on froyo not even got an ext on SD card full fat32

Also the backup was made with the latest version and latest app
[Desire HD Android Development] madmaxx82:
Leith51, please send me a bugreport. If possible (not too much work) reproduce the problem and send it immediately after booting your rom.

Will look at it and answer as soon as I get up tomorrow.

I have no possibility to help if I don't get more info like the last log which can be attached automatically by just ticking an option (you don't need to have saved it to your sdcard or anything. This always works..) . Might also need to meet you on irc.

Please, anyone stumbling about any problem any time needing help or suspecting an issue, send me a bugreport immediately after running into it.

Thanks!
[Desire HD Android Development] leith51:
Will do it as soon as I can working night shifts so will be sleeping the day time will reproduce and send as soon as I can
[Desire HD Android Development] BioTecK:
just a quick question;

What's the main difference between 4EXT recovery and ClockworkMod Recovery?

I flashed my Sensation with Android Revolution HD 3.6.3 and when I wanted to make a backup (which I previously did with Clockmodworks) I noticed that the screen mentioned 4EXT Recovery instead of ClockworkMod Recovery screen.

Thanks for explanation. =)
[Desire HD Android Development] madmaxx82:
Hi!

That's difficult to explain because it's a lot :)

Please check the first post for all the features.

As much as I know none of them is in CWMR ;)
[Desire HD Android Development] andreasy:
I'm curious to ask this in regards to restore within the recovery control:

The way I used to manually restore my backups until now was:

- Boot into recovery

- wipe all (factory reset)

- wipe system (because full wipe didn't seem to wipe this)

- restore

Does restore option from within recovery control format all those partitions before restore?

And BTW, why doesn't the first option in recovery (I think it's called factory reset?) format system partition as well? it only formats cache data and dalvik?
[Desire HD Android Development] madmaxx82:
For recovery control please take a look at the application settings. There you need to enable advanced restore and superwipe. Once you enabled that you will be presented many more options in the restore dialogues where you can tick a box to format all partitions before a restore for example.

Inside recovery, the first item is wipe data / factory reset. This one does not format system because it is not supposed to put your device into a state where it cannot boot anymore. It is solely there to clear all your custom data and settings. If you boot afterwards it would look like a first boot.

To format all partitions inside recovery you need to use the last item.

Btw: it is usually not needed to do this at all, since any recovery -also 4ext- formats a partition in the background before it starts to restore the data.
[Desire HD Android Development] Chezbel:
Option to "swap ROMs"

I wonder if it would be useful to have an option that helps people switch between different ROMs?

When you switch between ROMs you typically need to do a complete wipe and then setup everything again once that ROM is installed. However, if you are smart and make nandroids of both ROMs then it is pretty easy to switch between them, but it still requires a few steps, especially if you want to switch to a previous ROM and then update it:

1) Backup current ROM

2) Optionally wipe (probably not needed because of the next step)

3) Restore a different backup for a different ROM

4) Install a new .zip from sdcard to update the ROM just restored.

The main benefit would be that you can setup everything in the beginning and you don't have to wait for each step to finish before doing the next one.
[Desire HD Android Development] fogbav:
is there a chance to implement compression on the *.tar archives ?

Compression is about 40 % with rar ... so this would give us the opertunity to have more versions of backups on SD ...
[Desire HD Android Development] madmaxx82:
I see your point. Now what do you suggest should a feature that makes those steps transparent to the user do? How would it look like from a users point of view?

It would be easy to add, currently thinking of a way to implement another type of backup though.

Probably I will do both, but 4ext-ng must be published first ;)
[Desire HD Android Development] Chezbel:
Let me think about that. I see that your advanced restore already has all the pieces necessary to do this. For example "backup before restore" and "Files to flash afterwards". So perhaps it's not worth a separate option...

Sent from my abucus
[Desire HD Android Development] Euphorie:
AFAIK rar uses proprietary format. Developers have access to unpacking code, but don't have access to compression/packing algorithm.

7z could be an option in this case.
[Desire HD Android Development] madmaxx82:
You are right :)

But gzip would be used anyway ;)
[Desire HD Android Development] madmaxx82:
I got some questions regarding Titanium Backup's new feature: extract from "CWMR5" backups:

This actually means "tar backups", which CWMR5 uses always, and it works exactly the same with 4EXT.

But since in 4EXT recovery you have the choice to switch tar backups on or off, it means you can only use this new Titanium Backup feature for your tar backups!

Tar backups in 4EXT Recovery were disabled by default in earlier versions and are now default. However you might want to check if you have tar backups enabled or not.

You can do this via the App or by taking a look at your 4ext.prop file.

Using the app: select "recovery" and then "recovery settings". There you will find a switch "Use tar backups".

You can also verify whether tar backups are enabled or not if you enter "Manage your backups".

The currently used setting is in the title.. it should read "Backup setting: tar"

Using 4ext.prop:

You can also manually switch tar backups on or off by editing 4ext.prop:

Just open that file inside /sdcard/4ext/ and set "backups.use.tar=yes"

All backups done by 4ext recovery when tar backups were enabled will work for titanium backup's "extract from CWMR" feature.
[Desire HD Android Development] Chezbel:
I finally got around to testing this with 4EXT by using steps 1, 3 and 4 above. It was simple using the options that already exist in 4EXT. So ignore my previous request, it was based on ignorance... :)
[Desire HD Android Development] :No-Frost::
Continuing the other thread talk...

My issue is directly market related as I just cant buy the app, I've already tried everything and no matter what I do, I just can't buy this app...

For some reason, Android Market thinks Free 4Ext app is the paid one so it was linked to the one in the market, after this everytime I try to buy the paid version it says that I bought the app but I didn't pay for it so the installation or update is rejected :(...

This is happening with a lot of apps :(

It's not 4Ext issue though...

PS: I've already cleared market data, wiped, started from 0 and nothing :(
[Desire HD Android Development] Chezbel:
What version of the Market App are you using? I had alot of trouble with the 3.x version. The older 2.3.6 version works a lot better for me, maybe it will also work better for you.
[Desire HD Android Development] :No-Frost::
I have the latest one... I will search for the old market to see if that fix my issue :D thanks
[Desire HD Android Development] leith51:
How do you stop it updating every time I use the old market it updates itself
[Desire HD Android Development] Chezbel:
I think this is controlled by the MarketUpdater app. If you use Titanium Backup you can freeze this app and that should stop the updates.
[Desire HD Android Development] Drashna:
Or detach it from the market

Sent from my Inspire4G
[Desire HD Android Development] madmaxx82:
Hi!

Did you succeed?

Sorry for not answering earlier.

BTW: Was the Free App included in your rom? I have seen some roms where it was included as a system app, which is bad :(
[Desire HD Android Development] madmaxx82:
New app preview version is online:

Download: 2.1.1 Preview

"Preview" because there were a few internal changes and also translations into French and German that might need testing. (you can switch to English again in the settings if you dislike the localized version)

A few little bugfixes and little improvements:

Backups should now be sorted by date, MIUI roms that are quite different in where they put their rom names weren't always detected correctly in the past. This should work the same now as it does for all the other roms.

There are also two new features:

Exported color settings can now be imported again.

And finally there is a new wipe feature for the Desire Z / G2, myTouch 4G and Desire HD:

Wipe EFS partitions. The app will create backups of those partitions just in case. It also won't wipe them if it discovers that the backups weren't created.

But still: BE CAREFUL! This was tested only once so far.

Credits to ghul for telling us about that.

This is not the update I wanted though. There are tons of features that I'd like to implement, however I need to focus somewhere and at the moment this is the upcoming next final version of 4ext recovery.

Please bear with me, I will continue to work on the app again asap :)

Everyone can download and use/test the new app version. It is fully featured until 14th.

I'm planning to release it officially tomorrow on the market/slideme and the official free version too.
[Desire HD Android Development] :
Hey if you dont mind me asking, well I havent kept up with your latest build on 4ext and cant see the changelog for 4ext

dont know if you remember but im the guy that was throwing ideas at you for what you can implement, I asked if you would implement compression/decompression within the build

has that been accomplished? if not are you willing to put it in? if not I understand :) thanks
[Desire HD Android Development] madmaxx82:
Hi,

You can view all changelogs and known issues via the (free) app.

No I haven't implemented this yet, but I will do it soon!

But first the next final must be finished ;)

It's been 4 months or so since the last "final" version.

2.2.7 rc5 is actually already more stable than any "final", but there are a few things that need to be changed/improved.
[Desire HD Android Development] :
I understand and Thank you I appreciate it, but my dhd is currently not usable just now since im doing a few things, so I cant view the changelog

I think a good idea would be to give an option of the rate of compression

and option to compress backup while backing up the rom, maybe have a seperate menu for compression aswell, these are just ideas for you
[Desire HD Android Development] Chezbel:
Ok, this is very minor, but I'll mention it in case you think it is worth doing. The recovery menu has an option for "Mount /system writable", but if you make your system writable that setting does not persist when you go into recovery.

I discovered this is because flashing a RIL requires /system to be writable. So I made /system writable and then used "Install zip from sdcard" to choose the RIL to flash. After my system booted it still had the old RIL.

To get around this is very easy, just boot into recovery first and then mount /system and then choose the .zip to flash. That worked fine for me.

If it is easy to do it would be nice if "Mount /system writable" would persist after going into recovery. Or even better would be a check box on the Install Options menu that says "Mount /system before flashing"
[Desire HD Android Development] Wacco001:
4EXT Recovery Control 2.1.2 looks great ! Thanks for this update !! :)

Cheers,
[Desire HD Android Development] sigurd_LU:
+1 on this :)
[Desire HD Android Development] skoblar:
good evening:)

if you like me how to install 4EXT_Recovery_Control_v2.1.0.zip.

I have also 4EXTRecoveryUpdater.apk

thank you:D
[Desire HD Android Development] madmaxx82:
I'll maybe make it configurable. However compression depending on the level will certainly increase the time to make a backup drastically. So I will first test various options and if there is a "sweet spot" where compression ratio is very good and doesn't get a lot better anymore and speed is acceptable or even on par, then I will use that.

Hi,

This option to mount /system writeable was a feature request and not meant to be carried over to recovery on reboot.

I could do that, but this would make things much more complex and prone to errors!

Let's assume I would do that and someone was going to flash something that claims to need system mounted, but he also wants to flash something else after that that doesn't.

What happened would be that the recovery mounts /system and then starts to flash the zip files. The one that likes system mounted would work, the other one would fail.

While it is generally a bad idea for someone writing updater-scripts to assume anything (like system being unmounted or mounted before the script starts), it is default that system is not mounted when you flash something, unless the user did it manually. So there are unfortunately some updater-scripts that rely on system being unmounted when they start.

We would need to take this into account and this would not be possible without the users help. Most users though either don't have the knowledge or don't want to care about such things.

And I don't think this is something I should support, because it would only be a workaround for very rare, bad updater-scripts. Anyone who needs to write files to /system in a flashable zip file is responsible for mounting /system before he does that obviously.

The ril files flashable zips here don't need that anymore btw.

Thanks both of you :)

However it was only a small update.. more to come, but now need to focus on recovery ;)

Hi! What do you mean?

Can you link me that 4EXT_Recovery_Control_v2.1.0.zip?
[Desire HD Android Development] madmaxx82:
Chezbel: Reconsidered.. If you really really want it, I will do it in a future release, where the menu for flashing stuff will change.

But please anyone that stumbles across something that tells you to mount

/system before you can flash it, tell that guy that this is crazy and that he should rewrite his updater-scripts ;)

In case of the script for the ril files, it didn't work because the script was mounting /system using "MTD" as mount parameter. But the DesireHD is no MTD device, it has no MTD partitions like the Desire or Nexus One, so this line was completely useless and didn't have any effect at all.
[Desire HD Android Development] Selec1:
What is 4EXT-NG the app tells about?
[Desire HD Android Development] Chezbel:
Why don't you wait and see if other people ask for this. It's easy to work around. I didn't think about the fact that people might misuse this and cause you more headaches to support them.

I didn't send this... not sure how it got here.
[Desire HD Android Development] sugardaddy1979:
Any chance you can make the market allow us to download still even if we are on a dpi other than 240?
[Desire HD Android Development] ghostofcain:
Use older market, and simples. Not sure what this has to do with recovery though
[Desire HD Android Development] Selec1:
I have a request for the app.

I would like a 'pause' option after flashing. Now, it directly boots after flashing. I would be nice if we could set an 5/10/15 seconds pause option so we can read If everything went well.

(i know you can stay in recovery, but it just isn't enough :p)
[Desire HD Android Development] madmaxx82:
Will do :)

BTW: If something went wrong the recovery won't reboot!
[Desire HD Android Development] lhinsz:
@madmaxx82 - You and the rest of the AR Team ROCK!!

Awesome app!! I just wanted to say thank you so much; I just love this recovery app!! I've been using it since I switched to AR 6x in September, and I just purchased your new Market version a few minutes ago! You definitely deserve the support of your development work!!!

I have a couple of questions, though:

I currently have the version that installed with AR 6.12 (2.2.6 RC5) and I am getting ready to flash the latest (6.15) version of AR. I always use ROM Cleaner and/or the No-Sense script after a flash... So -- I just finished my Nandroid before I flash the update, but I wonder the best way to "update" to the paid version of EXT4?

Should I reboot my phone and let the market install happen first, or should I go ahead and flash the updated ROM, do my "no-sense" stuff, and then boot and let the Market install the paid version??

Or... any other order you recommend??

THANKS again for your work; I'm donating to the AR team one member at a time, as I can! You guys are awesome!! I've used dozens of ROMs now and this is definitely my favorite!! :D:D:D
[Desire HD Android Development] Towboat_man:
Just want to say Fine Job been useing this for a while and haven't looked back...I do have one (Q) though...When I do a backup it saves it in clockworks backup folder is there a option to have it save it somewhere else that I'm not seeing...Would love to get rid of Rom manager..

Sent from my "Pocket Rocket"
[Desire HD Android Development] madmaxx82:
Thank you very much for that awesome feedback and your support! :)

Sorry for the very late reply! At the moment I'm much more busy than usual and so I don't check all the threads everyday.

(I'm really sorry about that. Best is to send me an email or use the contact button in the app to get a reply as fast as possible..)

It shouldn't matter at all. Just uninstall the free app and then install it through the market :)

Thanks again, your support and your great feedback are very much appreciated :)

Also thank you very much!

Unfortunately if I moved the backup location then this would break compatibility with other apps that expect your backups to be there (like titanium which can extract apps and data from your CWM (and 4ext tar-) backups).

This doesn't mean you need to have Rom Manager installed though. You can uninstall it if you like!

The folder structure will just be recreated. It is all that is needed :)
[Desire HD Android Development] metaldood:
Is it possible to add 'multi select' option while select a zip file from the SD card? Instead of clicking 'add another' and going back and forth, why not have a checkbox against the list of files. So I can select 5-6 files all in one go?

Thanks

Excellent app btw. Great functionality and options.
[Desire HD Android Development] preacher65:
I can understand what you mean and why it would be helpful, but personally I like the "install another" option, as sometimes it's important to flash things in a particular order. So if this does get added, please can we keep the existing method as well? :)
[Desire HD Android Development] Drashna:
I know that root explorer has a 'multiselect' option, that would be a viable way to do this. I'm not really a fan of the idea, as i'd rather just make my own zip. :)

Sent from my Inspire 4G
[Desire HD Android Development] metaldood:
Oops.. yes the order does matter. Good point and I totally forgot :(
[Desire HD Android Development] madmaxx82:
Once the next update is released, I will again work on the app (app -> recovery -> app...). Soon I'll change the "recovery" menu as a whole and then this might make sense :)
[Desire HD Android Development] koyannaing:
Hi, Anyone got error on ROM Manager & 4EXT Recovery Control Force Closing on AD2SDX http://xdaforums.com/showthread.php?p=18911182#post18911182 ? Any solution to fix it? Thanks in advanced
[Desire HD Android Development] madmaxx82:
Did you already post your question in the thread of that...script?
[Desire HD Android Development] Doo Doo:
madmaxx im having a little issue with 4EXT Recovery

everytime i create a backup within 4EXT after it is done creating the backup & the phone reboots it always gets stuck on the first boot screen & i have to pull battery just to get it to boot back up normally

could you maybe tell me why this could be happening?
[Desire HD Android Development] leith51:
What Rom you using ?

sent from my dhd
[Desire HD Android Development] Doo Doo:
im using Bindroid 2.2 right now
[Desire HD Android Development] leith51:
Was it doing it before bindroid 2.2? Try to recreate using a different Rom it could be something in the Rom conflicting with the ext4 recovery so if you redo with a different Rom and it doesn't cause the same result its a possible Rom problem

sent from my dhd
[Desire HD Android Development] M@jkel:
Max, I have a question. I accidentally used market doctor in titanium backup on 4ext Updater (I used the free version). Now when I try to buy your app market tells me I already did and won't let me do anything :/ Tried erasing its data, unlinking the app from market with titanium, even tried earlier backup, just to check if it helps anything. No result. Any ideas what I might do to buy your app from market? Thanks in advance :)

@Desire HD & CyanogenMod
[Desire HD Android Development] JagDave:
Try clearing the dalvik.

Sent from The App that Time Forgot.
[Desire HD Android Development] M@jkel:
Wiping cache and dalvik cache didn't help :( Market still see's 4ext as an already bought app...

@Desire HD & CyanogenMod
[Desire HD Android Development] Doo Doo:
i think i might have figured it out when the name of the backup was to long it would get stuck at the boot screen

so when i shortened the name of the backup BAM it booted just fine so i think having the backup name to long was causing it to get stuck at the boot screen
[Desire HD Android Development] madmaxx82:
First: big sorry for taking so long to reply!

I misses your posts completely and didn't check the threads manually because of lack of time due to 4ext-ng which should be released shortly.

This is VERY weird! I can't think of any possibility why the length of the backup folder's name could be related in any way. If you manage to reproduce that it would be awesome.

When it gets stuck on reboot into your rom and you then boot manually, please send me a report via the app and tick the options to include the logs!

I'd really like to find out why this is happening for you!

If there's an issue it must be quite rare and so I really need your help to be able to fix that!

also sorry for the very late reply.

Did you already unlink the app from market via titanium and cleared the market data (settings/apps/manage/market)?

If this problem persists, could you please send me an email?

Either via the app or directly using the mail address in my signature.

Thank you and sorry for the inconvenience!
[Desire HD Android Development] Doo Doo:
how exactly can i send you a report via the app & where is the option to include logs?

sorry for my noobness :o
[Desire HD Android Development] madmaxx82:
No problem ;)

Just enter the app and click on Bugreport | Contact .. inside you will find 2 checkboxes you can check to include logs :)
[Desire HD Android Development] Doo Doo:
thanks :D

i'll try to reproduce the issue if i can & send you the report if i reproduce the issue
[Desire HD Android Development] M@jkel:
Problem was solved by occasion when I flashed new ROM for testing (which had older market), so I'm now having your app bound to my account :) Thanks for your reply! :)