[RECOVERY] 4EXT Touch 1.0.0.5 RC5 by MadMaxx82 [06/12/12]

Search This thread
G

glacierguy

Guest
OK here it is guys... All credit goes to MadMaxx82!

4EXT Recovery Controller App v2.4.1

www.4EXT.net

UPDATED 06/12/12


Thank you all very much ;)


Proudly presenting:
4EXT Recovery Touch

attachment.php
attachment.php
attachment.php



  • brand new user interface: "4EXT UI"
  • touchscreen only
  • extremely fast
  • much more useful features than the already feature-packed 4EXT Recovery Classic v2.2.7 RC5 (see 2nd post)
  • 4EXT SmartFlash for s-on devices
  • optionally save space by configuring recovery to exclude /cache from backups
  • you can configure recovery to save even more space by excluding dalvik-cache from backups
  • calculates real space needed to complete a backup to save you from troubles
  • detects your local time zone
  • -> correct time is used for backups you start from within recovery
  • allows you to change md5sum check behaviour
  • displays and updates your current battery level in real time
  • scrollable texthistory (drag down the statusbar)
  • built-in interactivity (yes/no questions) for updater-scripts
  • built-in screenshot functionality
  • extensive theming capabilities!
  • nearly ALL YOU SEE is changeable.
  • "worker bar": create your own custom animations, there are (nearly) no limits! Use any shapes/sizes/animations et.c.
  • extra low cpu needed for that: absolutely no negative impact on backup/restore speed.
  • async UI rendering for optimal performance for the "heavy tasks" like backup/restore
  • backups even faster than with usual recoveries.
  • .. explore the new interface to see more ;)
  • includes all features of 4EXT Recovery Classic







About 4EXT SmartFlash



This is a new feature that allows recovery to flash your boot partition just like as if you were s-off.

Credits and thanks to Team Win and Dees_Troy for their commitment to the community, for their amazing idea with the Dumlock and for extra contacting me only to offer that I may use it.
You guys really rock!

SmartFlash is a different approach to Team Win's HTC Dumlock


  • Just use your recovery like you would if your device were s-off
  • No preparations needed, other than telling the recovery that your device is actually s-on
  • This is done when you install recovery and answer the question that you are s-on with "yes"
  • You can also change that setting later on via RecoveryControl -> Recovery settings, or by editing 4ext.prop manually
  • Recovery will autodetect any changes done to "boot" and only attempt to flash your boot partition if it was really changed
  • This even reduces unnecessary writes to "boot" when for example a new rom uses the same kernel as your previous one
  • Before updating your boot partition, recovery will always backup your boot partition to your sdcard just for the case something goes wrong
  • Only the 4 latest boot images are stored, older ones will be removed automatically to prevent taking up too much space.
  • In case you want to enable or disable that feature temporarily, you can use a switch inside the tools menu in recovery



How it works:


  • Recovery will detect any requested changes for your boot partition
  • When you reboot out of recovery, it will prepare updating your boot partition on next rom start
  • This means that your boot partition will be updated when you see the HTC Splash screen, followed by 1 reboot
  • So basically the only visible difference to when you are s-off is one additional reboot, which takes only a few seconds.
  • Recovery is NOT flashed to boot and boot is also only flashed once/update
  • Recovery will only attempt to flash your boot partition if it was really changed




Limitations:

  1. Radio and firmware:
    Usually those are flashed via bootloader flashable zips or fastboot even on devices that are s-off.
    But in case you wondered: this does not enable you to flash new firmwares or radio images via recovery.
  2. SmartFlash needs a working kernel to be able to upgrade your boot partition.
    It cannot work in case your current kernel is incompatible with your device/hboot or has been wiped outside of recovery.
    For example you cannot erase boot via fastboot and then start up recovery to update your kernel.
    However you don't need a working rom to use it.
    The only requirement is that your current kernel is able to start (this happens before you see the boot animation) and that your system partition is mountable.





INFO:


For App and Rom devs:


Make use of the Recovery Interface Api provided by the (free and paid) 4EXT Recovery Apps to push updates/mods/addons for auto installation.
Very easy to use and to integrate into Apps or even shell scripts.

Please check 3rd post.​

Info regarding 4EXT Recovery Touch and its yesno feature, or any interactive installer scripts you might already use, please see 3rd post.​







Themes for 4EXT Recovery Touch:

Official 4EXT Recovery Themes Index & Discussion Thread





Download






  • This ensures that your downloads are ok by automatically verifying md5sums and that known issues and changelogs are easily accessible
  • When you install or download a recovery via the app it makes sure that your recovery config is correctly set up.
  • Configure 4EXT Recovery comfortably without the need to modify config files.
  • It allows to automatically setup your time zone for recovery.
  • You can use it to get notified about updates regarding your recovery version
  • You can configure it to get notified in case any critical bugs have been discovered of the recovery version you currently have installed.
  • It allows me to update known issues/changelogs immediately and to quickly pull a newly released version if there were reports about critical bugs
  • You can also use it to just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!



By default the app also saves the recovery.img you flash on your sdcard,
so you can use it to flash the recovery via fastboot in case you need to do that one day.
If you somehow lost those files, there's a direct download for a version you can flash via fastboot.





4EXT Recovery Control



For a list of its many features, visit www.4ext.net

Some examples :
  • Very easy to use, but also includes an extensive set of features available via "advanced mode"
  • Comfortable configure all settings of recovery
  • Calculate the space needed to create a new full or advanced backup

    So you can make sure the backup will succeed before even rebooting into recovery.
    Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.​
  • Identifies and adds your romname so you don't need to type so much when chosing a meaningful name for your backup
  • When you restore a backup, the app does the md5sum check instead of the recovery
    This ensures that you know whether the restore process will succeed before even rebooting into recovery​
  • Flash as many zip files you want in one go
  • Automatically calculate and display the md5sums of all zip files you are going to flash
  • Check your backups' health to ensure they will restore later when you need them, by verifying their md5sums!
  • Optionally, but highly not recommended:
    If md5sums don't match but you really need that backup badly, you might want to restore it anyway.
    You can you this app to fix the md5sums of a given backup​
  • As an example, the following is possible to do in just one session:
    Restore a backup, set to create a backup / advanced backup before the restore,
    format all partitions with a file system of your choice before the restore process starts,
    flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.​
  • Much, much more! See www.4ext.net :)



 
Last edited:

rbaruch

Senior Member
Dec 17, 2011
490
117
Holy crap, all you do is install app, click install recovery and follow instructions.

So easy even a retard like me can do it..

10/10 app.

Makes CWM looks like something children play with..
 
Last edited:

dubt17

Senior Member
Feb 26, 2010
630
180
Google Pixel 6 Pro
Google Pixel 6
Oh wow! Just backed up, wiped, installed evervolv ics preview 3, booted into it, then wiped and restored and am now in the xda app!!! This is awesome! No more tether!!! :D

Sent from my HTC_Amaze_4G using XDA
 

gaww

Senior Member
Oct 4, 2010
7,277
1,254
Asheville, NC
I installed and am trying out Recovery Updater. It looks real interesting - just wish there was something new (kernel, etc.) to try flashing - lol. In the meantime, had it check some backup mDsums and making a new backup.

I definitely intend to upgrade and support the developer.

I am wondering if this will eliminate most of the need for s=off, except s=off would possibly attract some more development to the Amaze.

I guess it is goodby to CMW Recovery on the Amaze
 

MildewMan

Senior Member
Dec 25, 2010
288
61
Saint Louis, MO
Awesome. I've always used CWM, so I'm kind of nervous about trying something new, but I am going to give it a try since you rave about it IceMan. :)
 

aj_2423

Senior Member
Sep 21, 2010
1,614
979
34
Sacramento, Ca
Wow this recovery seems much more advanced. 20x better ui than cwm, and it even supports charging while in recovery

Sent from my NRGized Amaze...
via xda premium
 
  • Like
Reactions: dubt17

rbaruch

Senior Member
Dec 17, 2011
490
117
Holy crap
Where can I find a lot of themes? =)

Sent from my HTC Amaze 4G using xda premium
 
Last edited:
  • Like
Reactions: dubt17

2kwic25

Senior Member
Dec 13, 2010
191
34
Hey gguy since you been testing this I just have one ? So all I have to do now for instance download energy Rom and flash it without hooking it up to the computer and flashing the kernal ?
 
Last edited:
  • Like
Reactions: dubt17
G

glacierguy

Guest
Hey gguy since you been testing this I just have one ? So all I have to do now for instance download energy Rom and flash it with hooking it up to the computer and flashing the kernal ?

No need for PC... :D flash kernel from recovery... Those kernel flashers are SOOOO old skool :D

Check out OP... MadMaxx has quote of how smart flash works. It recognizes changes in the boot.img from ROMto ROM... It flashes it while flashes the ROM. If your boot.img is different, you will get an extra prompt notifying you of the change. When you reboot from recovery, if u flashed a new kernel, you will get an extra reboot before the boot animation. Don't be alarmed... It's all cool baby! :cool:

Sent from my HTC_Amaze_4G using Tapatalk
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    sooo stoked this finally got an official release, I was feeling bad that you guys had to wait for it... glad I was able to contribute a little to the testing process, also threw a donation in Madmaxx's direction, he totally deserves it... I will probably start donating pretty regularly to him, his work is some of the finest available for android phones... the devices he supports will definitely influence the devices I purchase!:D

    edit: I would also strongly urge anyone that can to do the same (donate)...
    4
    Here's my link to the recovery.img. The newest stable

    https://www.box.com/s/mp4v31quljfvdlmy945z

    Sent from my HTC_Amaze_4G...Go Canes []_[]
    4
    Hi Amaze users,

    Just to bump the thread, as a new version of 4EXT Recovery Touch v1.0.0.6 RC1 is now available as of 31/12/2013 and all finally packaged up early morning 01/01/2014 so thanks for this at New Years!

    To get your hands on the recovery.img, download 4EXT_Recovery_Touch_v1.0.0.6_RC1.zip using the 4EXT Apps.

    The Free 4EXT Recovery Updater v2.4.6b App.
    Or the Paid 4EXT Recovery Control App.

    Version v1.0.0.6 RC1 is required for the Android 4.4 KitKat ROMs and GAPPs.

    Here is the changelog for 4EXT Recovery Touch v1.0.0.6 RC1.
    - Based on the rock solid v1.0.0.5 RC9
    - Added support for SELinux needed by some Android 4.4 roms.

    Big thanks to the following testers:
    Papete, Dtr204, CChako, and Kingmook!

    Hope the above helps!

    Happy Testing,

    Rob.
    4
    Also, if you are new and using this, and you are "S-ON"... MAKE SURE YOU HAVE "SMART-FLASH" ENABLED IN THE SETTINGS!! if not then we will end up with about the 500th thread titled "amaze 4g stuck at boot logo, please help!!!" Or "flashed x.x.x Rom and now phone just stays at HTC screen" because of course you won't search first :D

    sent from my
    NRGized amaze
    powered by Faux
    4
    If I leave the notification on will it keep the app running in the background? I always opt to leave it turned off but I noticed that I was behind on some builds.

    Wait....I sent this with Tapatalk?

    No ;)

    I made sure to not have any background processes.
    The problem is that when YOU force close it, Android will remove all scheduled checks by design.


    For Android it's okay if an app kills itself.. any set schedules will remain registered.
    However when the user kills an app, all set schedules are removed.
    This is by design so you can get rid of any misbehaving apps completely.

    This is why I added a "wanted" force close where the app itself removes itself from memory when you exit it by pressing back on the mainscreen (2 times.. I'm sure you know the message that pops up when you press back once).
    That's basically against the Android design that just puts apps into the background until it gets short of memory where they are removed then.

    When you leave my app it's removed immediately. I did that to make adding it to task killers obsolete.

    Because if you added it to taks killers, it would make Android forget about the schedules you set up.

    You can verify that by using any process managers.
    When you leave the app like usual (not by pressing the home button), it won't show up in any process managers.

    When you enable notifications, the app tells android to start a service for a short time at your chosen interval.
    The service then checks for updates or news and then force closes itself!
    This takes only a few seconds.

    To make Android not forget about the schedules you set, they need to be re set at boot time.

    That's why a component of the app will start at boot time (if you enabled notifications).
    This component sets up your chosen schedules in Android's AlarmManager and then kills itself!

    You will never find any background processes or processes listed in any task/process managers!

    However you will see a force close button when you select the app in manage applications.
    This means that you can even kill the schedules it has set up.
    It's not related to it consuming memory or cpu time as there is no process running.. again: check it by using a process manager app or something like that.