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

Search This thread

pappasmurfsharem

Senior Member
Feb 13, 2008
132
29
I'm getting a recovery loop now, I just flashed a rom. and it worked great then when to flash a new rom and it just recovery loops
 

hzm82

Member
Oct 14, 2006
44
6
I was on build 59 rc2, i installed speed rom straight from the recovery, went back into recovery afterward to install another rom and the recovery is looping. i reflashed rc 3 build 5 from apk. Still looping.
 
G

glacierguy

Guest
Well wtf...

I'm starting to dl the ROM now... Maxx is gonna want me to have that I'm sure tomorrow :-/

All these girls excited Oooo ya know they like it I'm so icy, so icy
 

hzm82

Member
Oct 14, 2006
44
6
Flashed CWM Recovery ==> Boot into recovery ==> Installed Revolution ==> Flash 4EXT RC03 ==> Good to go, no more recovery loop

Hope it gets worked out either on the Recovery end or Rom end
 

madmaxx82

Retired Recognized Developer
Jan 17, 2010
4,287
4,563
www.4ext.net
Thank you all very much ;)


New build available ;)

Please update!


Parts of the changelog:

  • The most important parts of your recovery configuration are now displayed at boot time
    It's too fast to read though. Just pull down the statusbar after boot if you want to check your active configuration.​
  • Fixed current time in backup names.
  • Fixed a potential crash when identifying rom names
    Although fixed, recovery will no longer try to identify the current rom at boot time, but only when needed.​
  • Fixed copying screenshots to sdcard.
  • Dual SD-Cards: Fixed a potential problem when choosing sdcards
  • Disabled button events while Aroma is run.
 

EclipzeRemix

Senior Member
Oct 8, 2011
3,225
5,615
Thank you all very much ;)


New build available ;)

Please update!


Parts of the changelog:

  • The most important parts of your recovery configuration are now displayed at boot time
    It's too fast to read though. Just pull down the statusbar after boot if you want to check your active configuration.​
  • Fixed current time in backup names.
  • Fixed a potential crash when identifying rom names
    Although fixed, recovery will no longer try to identify the current rom at boot time, but only when needed.​
  • Fixed copying screenshots to sdcard.
  • Dual SD-Cards: Fixed a potential problem when choosing sdcards
  • Disabled button events while Aroma is run.

so will this murder the potential bootloops?
 

madmaxx82

Retired Recognized Developer
Jan 17, 2010
4,287
4,563
www.4ext.net

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.