yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Android Development] madmaxx82:
Thanks for the bugreport, I will fix that!

This does never happen if you are using the app to select the zip file.

Please do it that way in the meantime.

Thanks again!
[G2 and Desire Z Android Development] ptesmoke:
Beta works awesome, back arrow now does what it should and scrolling speed is way better :) thanks again for your hard work max :)
[G2 and Desire Z Android Development] mrbmg:
Great job madmaxx! Beta works awesome over here. Back arrow is now working as it should, and the touch is very responsive! Thanks for all your hard work bud :)

EDIT: from the control recovery I made a backup and had "stay inside recovery when finished" checked. It still restarted. Don't know if this is normal procedure, or if it should have actually stayed in recovery?
[G2 and Desire Z Android Development] cswroe:
It went a bit further, but when the counter reached 59 it stops and that is it. I am able to boot up the device and access the unformatted data, but now now matter what I do, when I boot into recovery it tries to perform a wipe. I will but a blank card in and see if I can get my device up and running.

Don't waste too much time on this, I am probably the only user with this issue so it is no biggie. The classic version is working fine for me.

Thanks for your help and if you need some more testing let me know.

EDIT: Put a blank card in and it ran through it's wipe of everything. I have since been able to boot into recovery normally now.
[G2 and Desire Z Android Development] madmaxx82:
Could someone please try out Beta 3 and tell me if the back onscreen button issue has -hopefully not- reappeared? ;)

Thank you!

No this is not supposed to be like that!

I just tried that out myself with Beta 3 and it stayed inside.

Could you please try again with beta 3? Maybe there was a problem in Beta 1 regarding stay or not to stay after completion.

Thanks very much :)
[G2 and Desire Z Android Development] mrbmg:
Flashed beta 3 and all is well. Just made a backup, and it stayed in recovery like I chose. Awesome work man! Really appreciate it.
[G2 and Desire Z Android Development] dargocitfer:
I concur! Everything seems to be running as it is supposed to with Beta 3!
[G2 and Desire Z Android Development] jethro650:
Yup...all good with beta 3 here also
[G2 and Desire Z Android Development] mrbmg:
Ok, after some more playing around with stuff. I've noticed this before, but never brought it up. Let's say I go to the wipe menu in recovery control. I have checked: wipe cache, davlik, and efs. It will automatically wipe efs when I tap proceed. Then it just restarts the phone. Should it be actually going into recovery to wipe cache and davlik?
[G2 and Desire Z Android Development] madmaxx82:
Thank you very much for the feedback!

EFS is different. It is not wiped in recovery but via the app directly.

As soon as you let it wipe EFS, the other options won't have any effect.

It doesn't force you to reboot though. You can then select the other options and let it do its job.

I realize this isn't very good. I will correct that!
[G2 and Desire Z Android Development] O W Y N:
Compatibility?

Until now I've just stuck with something I was familiar with (ClockworkMod Recovery), But I have decided that I think now would be a good time to change recoveries.. But one thing that concerned me was the compatibility with old backups made via CWM Recovery. Will the backups I've made in the past still work with 4EXT? or will i have to start from scratch in terms of backups?
[G2 and Desire Z Android Development] Ditamae:
Depends on what version of Clockworkmod you're using... in my experience backups created with 4EXT and CWM versions 5.X are compatible, but anything you made with CWM v3.0.2.4 won't work... it's well worth the transition though. 4EXT is based on CWM so there are many similarities, but madmaxx82 takes it to another level. Highly recommend it.
[G2 and Desire Z Android Development] misfit61871:
Merry xmas 4exters!

Ad Mortem Fidelis
[G2 and Desire Z Android Development] madmaxx82:
Thank you very much ;)

Need to correct something though.

4EXT Recovery will restore ANY backup made by ANY version of CWMR.

It behaves like CWMR5 there..

Restore: all backups made with 4EXT Recovery can be restored using CWMR5.

If you disable tar backups in 4ext recovery, then those backups can even be restored with old versions of CWMR.

sent from a phone using xda premium
[G2 and Desire Z Android Development] madmaxx82:
Merry Christmas! :)

sent from a phone using xda premium
[G2 and Desire Z Android Development] Ditamae:
You know, I thought this was true, but the other day when I changed hboot versions, I had CWM v3.0.2.4 installed momentarily and I tried to restore a backup I had just made with 4EXT (tar disabled), and CWM wouldn't recognize the backup file... so I just assumed that this particular version on CWM wasn't capable of restoring backups created with the latest 4EXT. I guess this doesn't even apply to the previous users post anyway. Anyone thinking of making the switch only needs your Recovery to restore older CWM backups... and that it does. In my opinion there is no reason in the world not to upgrade to 4EXT. :)
[G2 and Desire Z Android Development] O W Y N:
Thanks loads for clearing that up for me! The only thing that stopped me from flashing this a few days ago was the fear that some of my old backups (including the original ROM for my phone [which I'll probably never flash again anyways lol]) might not work if i needed them. Definitely flashing this tonight :)
[G2 and Desire Z Android Development] heybobitsme:
[FIXED]

Ok, I have a big problem. I flashed back to the G2 hboot from the DZ hboot and it wiped all my partitions. I expected this and made a backup using the 1.0.0.3 RC3 (I think, whichever was the latest one being shown in Recovery Updater). Now I booted to recovery from hboot and 4ext recovery partially loads, I get the error:

E:Can't mount /cache/recovery/command

I think I need to flash the classic recovery, but I'm stuck.

Edit: Ok, I fixed it. I went to the CWM recovery thread and fastboot flashed CWM5. It's restoring now.

Edit 2: Did I run into the issue with not enough space for the Touch recovery? As stated above, I had the DZ hboot, which allowed more space to /system. Flashing back the G2 recovery and I was stuck, but in recovery there was no menu options.
[G2 and Desire Z Android Development] madmaxx82:
Hi!

You need to wipe your partitions before changing hboot.

The classic recovery is even more susceptible for that.

How far does it boot? Are you able to wipe your partitions?

Since 1.0.0.3 Beta 1 it should enable its internal "safe mode" and boot nonetheless.
[G2 and Desire Z Android Development] heybobitsme:
I updated my post. Changing the hboot already wipes partitions. I did everything through adb and rebooted and it was stuck on the HTC screen, which I expected. I pulled the battery and held vol-down and power to get into hboot, selected recovery and it rebooted to recovery. The background was there, it gave me the error. That was it. The title bar at the top would turn off and on when I touched the screen but that was it. I had no menu options.

Edit: I flashed 1.0.0.3 beta 3 from the app and rebooted into recovery and it works fine. I had the menu options and they worked. I'm baffled.
[G2 and Desire Z Android Development] madmaxx82:
Changing the hboot already wipes the partitions? This is new to me. But then I only know how it is on the Desire, where users change them all the time.

Please boot into hboot -> fastboot mode and do:

fastboot erase cache

fastboot erase userdata

fastboot erase system

and then boot again into recovery.
[G2 and Desire Z Android Development] heybobitsme:
Ya, I'm mistaken, it just wipes /system. You're right about the commands above. I really need to remember my fastboot commands! Lol! Tbh, I've never run into that before, but the last time I changed hboot, I think I was on CWM3.
[G2 and Desire Z Android Development] WTF?:
actually....YES! It does!

to quote rmk of Virtuous ROM's fame: "Flashing a new HBOOT will wipe the radio, recovery, system, cache, data partitions, etc."
[G2 and Desire Z Android Development] madmaxx82:
Yeah but it's the question if he just wanted to point out that you will lose all your data on those partitions hence to create a backup before (which is following that statement), or if this really does a clean erase!

On the HTC Desire at least this is definitely NOT the case.
[G2 and Desire Z Android Development] bombadier:
On the Desire Z as I understand,it will do a full wipe as it will reorganise the size of the partitions making one bigger,although the method described by Rmk includes a new radio and recovery as well.

"The G2 HBOOT has only 400MB allocated to /system and 1.3GB allocated to /data, whereas the DesireZ HBOOT allows for 535MB of /system and 1GB of data" from same page.
[G2 and Desire Z Android Development] madmaxx82:
Well flashing a different hboot (at least the reason to do that is) usually to change the partition layout.

That's why everyone's crazy about that in the Desire community :D

When you do that, data are lost of course.

But in case of the Desire at least they are just "unusable" which is to be expected of course if you move/resize partitions.

So they are logically "gone", you can't access them anymore.

This doesn't mean though that the flash memory is actually "erased".

Just changing partition layout anywhere else, on your computer or anything doesn't erase anything either.. extra work would be necessary to do that.

Maybe that's all different on the Desire Z. :) .

New update shortly that isn't too picky about that :)
[G2 and Desire Z Android Development] WTF?:
well I guess you could say it is not a "wipe" in the CIA spy sense of the word, but just as on a computer, if you repartition the hard drive, it is effectively a wipe for most people! - lol (their data is effectively wiped, they are going to need a linux hacker or a forensic disk recovery app to retrieve it ;)
[G2 and Desire Z Android Development] bombadier:
Now you are getting technical ;) I have the desire z but changed the hboot to get fastboot commands working not to change the layout,so the partitions are not wiped until done from recovery then ? thanks for clearing that up sir :)
[G2 and Desire Z Android Development] madmaxx82:
The point of the whole discussion was that recovery had problems in previous versions when you didn't "clean up" before doing that. It simply hung.
[G2 and Desire Z Android Development] madmaxx82:
Updated :)

1.0.0.3 Beta 6 is now available.

It should be a major improvement over the last betas of 1.0.0.3 and I hope it is already as stable as a RC, or even better. I *hope* ;) You need to tell me ;)
[G2 and Desire Z Android Development] jethro650:
Installed a while ago and set up an install through recovery control. Installed rom, gapps and did all the wipes, hit the button to do it and all went well. New rom up and rrunning smoothly. Played around in recovery a bit and its very smooth and responsive. Again, very well done thank you so much.
[G2 and Desire Z Android Development] madmaxx82:
I'm very sorry.

A bug slipped through in Beta 6.

It was a last minute change.

Some menu items were out of order inside the wipe menu!

Please flash beta 7.

Sorry again!

Thank you very much :)
[G2 and Desire Z Android Development] Ditamae:
Beta 7 running great. And the 'wipe cache & dalvik' option is a nice addition. Thanks again. :)
[G2 and Desire Z Android Development] mrbmg:
First thing I noticed, had to use it..excited lol
[G2 and Desire Z Android Development] madmaxx82:
Thank you ;)

A very nice new theme is available from DaRk_dOg.

1st post updated a few days back. Just posting in case you missed it:

http://xdaforums.com/showthread.php?t=1399414

Also updated 3rd post with some info for Rom chefs:

How to make use of 4EXT Recovery Touch from within updater-scripts:​

Since Beta 1.0.0.3 Beta 4 you can do the following:

identify whether the user is running 4EXT Recovery Touch or not (to use or not to use the following commands)

make use of the native yes/no dialogue (confirm / cancel buttons)

prevent recovery from redrawing the screen ( in case you need to use your own 3rd party interactive binary )

​

To identify 4EXT Recovery Touch:

if getprop("ext.edition") == "ng" then

<your code>

endif;

To use the native confirm dialogues:

ui_print("4ext: show_yesno"); # <-- recovery will pause your script and display "yes / no" buttons.
run_program("/sbin/sleep", "2"); # <-- for safety since the above is executed asynchronous

#check the return value by calling:

if getprop("ext.confirm") == "yes" then

<yourcode>

endif;

To prevent recovery from redrawing the screen ( if you want to use an external binary that needs to occupy the screen and get the focus )

ui_print("4ext: disable_scrn_update");

# don't forget to enable it again after your yesno binary or graphical installer is finished, by calling:

ui_print("4ext: enable_scrn_update"); #otherwise the recovery will appear to be frozen as it won't update the screen anymore.
[G2 and Desire Z Android Development] Fedburin:
This is awesome!

Works great on my wife's G2. Any chance this could be ported to the HTC Flyer?
[G2 and Desire Z Android Development] madmaxx82:
Yes ;)

But no ETA possible at that time.
[G2 and Desire Z Android Development] WTF?:
maybe this is a really dumb question, but I am at my friends house and he purchased the 4EXT recovery classic via the market last week on his T-mobile G2, and today he downloaded and installed touch beta 7, but even after rebooting phone and restarting the app, his interface still looks like the old classic version on all of the menus, and it says at the top that he is using version 2.14

how does he get the pretty touch version to start up rather than classic?
[G2 and Desire Z Android Development] madmaxx82:
You cannot purchase 4EXT Recovery.

You can only purchase 4EXT Recovery Control

This is the App interface to the recovery.

With it you can download/flash the recovery (classic or touch), customize settings for recovery and do a lot of other things.

When you installed 4ext recovery touch via recovery control or the free app, you will have the touch recovery flashed, so when you reboot into recovery you will boot it ;)
[G2 and Desire Z Android Development] WTF?:
oh OK, I thought that the pretty part extended all the way into the menus on the phone portion of the app as well

you have got to fix all of this confusing nomenclature, I am a computer guru and yet I cannot find any logic in all of these confusing names and versions - is it 4EXT Recovery or 4EXT Recovery Updater or 4EXT Recovery Control or 4EXT Touch Recovery or 4EXT Touch Recovery Control and is it version 2.14 or 2.2.7RC5 or 1.0.0.3 beta7 or..... geez! :eek:
[G2 and Desire Z Android Development] madmaxx82:
Rom Manager Premium (paid)

Rom Manager (free)

Both flash CWMR

4EXT Recovery Control (paid)

4EXT recovery Updater (free)

Both flash 4EXT Recovery

4EXT Recovery got to a new level: touch, this supersedes 4ext classic.
[G2 and Desire Z Android Development] cswroe:
Pretty simple.
[G2 and Desire Z Android Development] WTF?:
pretty simple NOT

if it is confusing for me, imagine how it might be for someone less experienced, for example it seems that 2.1.4 is supposed to be the latest version of the free one (recovery updater?) and 2.2.7RC5 is supposed to be the latest version of the paid version (recovery control), yet when you go to the market it says recovery control (paid) and yet the version is 2.14 - even inside the app it uses the term 4EXT recovery (no updater or control, just recovery) version 2.2.7RC5 :eek:

all I am saying is that while it might make sense to you and to some long time users of 4EXT, but in order to spread this wonderful app to widespread distribution like Rom Manager (millions of users) it needs a cleanup of all of these confusing terms and versions - and we didn't even address classic or touch!

Steve Jobs sold millions of devices and a ton of software by thinking that perhaps everyone is not quite as intellectual and geeky as he is, and might need it Simplified - just sayin! :D

PS: - for the record, calling an app Rom Manager and also CWMR is confusing as well, just because koush started a confusing naming convention, doesn't mean it has to be a trend! - lol
[G2 and Desire Z Android Development] cswroe:
You are looking at this wrong and blending the version numbers, that is probably the confusion

4Ext Recovery Updater and 4Ext Recovery Control are Programs that run within the Android OS. One is free (Updater) and one is paid (Control). Both are version 2.1.4. Both of these programs facilitate the installation of the recovery image while in the Android OS, the paid version also allows to Backup, Restore, and more while in the OS.

The recovery itself is a recovery image, independent of the APK's, in fact, you do not need the APK's to use the 4ext Recovery which is basically an alternative boot partition; the classic version 2.2.7 RC5 and the touch version 1.0.0.3 Beta7.

Before the programs (Rom Manager or 4ext) were around, you used to have to flash the recovery image using terminal or ADB. The Programs just make it easier but have caused a couple problems, people really do not understand the technical aspect of what they are doing when the process is automated, and some people are messing around with their device that really should not be doing so.
[G2 and Desire Z Android Development] madmaxx82:
This is not true: It says 4EXT Recovery Control 2.1.4 everywhere inside the app.

When you are on the screen where you can select different versions of recovery to download or flash, it displays the recovery version you currently have on your device for reference.
[G2 and Desire Z Android Development] OriginalGabriel:
Seeing as how this is the first time anyone has mentioned being confused by the naming system, it might just be you.
[G2 and Desire Z Android Development] jethro650:
Only been using this for a couple weeks but it seems pretty straight forward to me. I really like the in app controls so you can set up a backup then the proper wipes, multiple flashes(usually rom and gapps)then press one button, come back a few minutes later and its done and the phone is rebooted already to go :cool:
[G2 and Desire Z Android Development] OriginalGabriel:
This is like saying MS Windows and MS DOS are the same thing; an application (ROM Manager) is not the same as a recovery image (CWMR).
[G2 and Desire Z Android Development] :
WTF?: you appreciation and criticism are welcome, these are just my musings on the matter. For the record, I think you've made it clear that you think the app is great and you are saying these things because you want to help the dev be successful.

Here's the thing, apps that are have less functionality are in general easier to navigate. Anybody who opens up Logic Pro for the first time will not really know where to start, but, say, iTunes is pretty obvious. (Both Apple apps)

That's a bit more extreme than this situation, but the 4ext recovery does have a lot more functionally than the average app (including rom manager). Some apps just have a steeper learning curve than others. And honestly, anybody who is inexperienced with operating recoveries should not be messing around with more advanced systems.

If you want to compare it to rom manager, that is like apples and oranges. Sure rom manager offers rom installation scripts as well, but in essence they have different goals. Rom manager is just like it's name suggests, likewise 4ext Recovery Control. There is overlap, for sure, but the end goal of the apps are different. It makes sense that they don't resemble each other too much. I usually use rom manager to download a rom but 4ext recovery control to flash it.

The thought of reorganizing the app menu structure has occurred to me, but in the end, I can always get what I want out of the app with minimal effort.

What is more productive with this kind of issue is to come to the dev offering solutions rather than problems. I mean, it doesn't take too much work to make a list of the functions and try to rearrange them in a more user friendly way. Then you can approach the dev with something positive and helpful, rather than something frustrating and negative.

After all, (it is a paid app), but this is an open source community and the name of the game is contribution.

Perhaps once the touch is out of beta, recovery, recovery control, and recovery updater can be released and forthwith be updated with common version numbers, just for diambiguity (even if some components have no changes). Just a thought.

My apologies for the novel. I'm a bit "new years eve" right now, so I just hope my thoughts are coherent. LOL

Sent from my Nexus 6 like tears in rain.
[G2 and Desire Z Android Development] WTF?:
OK, I think cswroe has clarified it for me - no one ever really explained it this well before - I think it was just a nomenclature problem I was having, I am a Windows guru, not a smartphone guru! - perhaps a 4EXT wiki would be a great idea?

so here is my next question, lets say my friend Paul has just purchased a brand new G2 off ebay, and he has successfully rooted it, and then he has purchased the 4EXT recovery control 2.1.4 app from the market and now he would like to use my image-type full backup (recovery?) that I created of my phone using 4EXT 2.1.4 (I guess I did a full recovery image, but in any event, it seems to restore the phone precisely as it was before I mess it up each time, apps and tweaks and everything! - lol) It's like Norton Ghost on the PC, it would seem!

this way he could instantly have his phone all tweaked (he loves the way I have mine set up) without having to spend hours or days getting everything just right! - then all he would need to do is replace my contact list with his, and my gmail google account info with his and set up his wifi and he is up and running in minutes with a great configuration!

what files does he need from me and in what directories to do this and will it work like I describe?

(I am guessing I need to send him the contents of the /sdcard/clockworkmod/backup/2011-12-30_VirtuousGLitev2.0.1 directory, which is around 580MB) or is this image somehow serialized and tied to the IMEI of my phone?
[G2 and Desire Z Android Development] :
I am 95% sure that will work. I've only restored system and boot from someone else's backup, and I had to create a new md5 sum for them since the md5 is for all partitions together. You will have to send him everything from that folder if you don't want to have to create new a md5 hash.

If you don't want him to have all your non system data/apps, I think the easiest thing to do is to restore the full backup, then use TB to filter everything but user apps then batch uninstall. That way your system settings will remain.

Sent from my Nexus 6 like tears in rain.
[G2 and Desire Z Android Development] OriginalGabriel:
Since you're a "Windows guru", let's put it this way: you install Windows on your system, install a bunch of programs (paid and otherwise), make a bunch of tweaks, sync a bunch of locals, etc. Can you now ghost that image to everyone?

No; while the tweaks may stay, any apps (specifically paid apps) won't work unless they already have them associated with their account.

If your friends are wanting certain tweaks, and you're as adept as you say, make a script to tweak the ROM install for them.
[G2 and Desire Z Android Development] WTF?:
I thought about that, but actually 4EXT and Root Explorer are the only paid apps I have, and my friend has already purchased those two, so I think we're good to go!

and on the install scripting, what is your recommended method for this?

PS - the reason this would not work on Windows, has nothing to do with apps being paid per se, but rather the Window's Security Identifier (SID) which is uniquely created on installation, and has to jive with the particular motherboard you are installing the system on, although software such as Ghost can get around this, this is the reason I asked whether the recovery image was serialized to the IMEI, for example, in my original query.