[Unlocked Only][RECOVERY][2011-11-14] Custom CWM-based Recovery 5.0.2.7-photon3 - Motorola Photon 4G

This is a modified CWM-based recovery for the Motorola Photon 4G. It is based on my own custom code forked from the CyanogenMod team's recovery. The major changes I have made include full support for dual SD cards, support for webtop partitions (SD card and internal) and changes to Nandroid backup/restore for this phone's additional partitions.
Some highlights include:
Dual SD card support
ADB support
USB Mass Storage support
Nandroid additions/changes
ext3 formatting
Probably others
This recovery is only for UNLOCKED devices. It is intended to be flashed directly to the recovery partition.
UNLOCKED users can flash this recovery using:
Code:
moto-fastboot devices
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-photon3.img
Example:
Code:
$ moto-fastboot devices
TA20700KXH fastboot
$ moto-fastboot erase recovery
erasing 'recovery'... OKAY [ 0.741s]
$ moto-fastboot flash recovery recovery.img
sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]
This is posted in a DEVELOPER forum and is being released to help further the development of Android for the Motorola Photon 4G. I have NOT personally tested this on my phone and YOU assume full responsibility for any damage incurred to YOUR phone!
Click to expand...
Click to collapse
I do NOT have a Motorola Photon 4G. I have based this recovery off the Photon kernel and Atrix resources as suggested by Calkulin. I do not SUSPECT there will be problems but again, I have NOT personally tested this on my phone and YOU assume full responsibility for any damage incurred to YOUR phone!
Click to expand...
Click to collapse
SPRINT USERS
Orange 5.0.2.7-photon3 / ZIP version.
MD5 0dc70209659fecbf7a2a01fe64b431af / a7fa2daf946557006931d33f3954e350
Cyan 5.0.2.7-photon3 / ZIP version.
MD5 440baa230638bd12dfd38b67977d3ac3 / 4da9f845f5d8ae0c37d0e1deaecd931c
Light green 5.0.2.7-photon3 / ZIP version.
MD5 b0791b6a4e0ea1a593d450518f309315 / f4afa4ca6f9616713ba436149df48c46
Dark green 5.0.2.7-photon3 / ZIP version.
MD5 5ef4862918169c1b4f9b0cbd60c70267 / 12acbe4adac62dc79e9a2b9ed1d0ea3b
Blue 5.0.2.7-photon3 / ZIP version.
MD5 cb1a4b2b48d18f535f5a3ce312e3ee81 / 53eee173392a8a821e45e8ddb1bbefd6
Red 5.0.2.7-photon3 / ZIP version.
MD5 f95a0adfb47ae2b995412b89d95f40fe / ca222e4891f756b5b4ad59fe06b6f0bf
Original ROM Manager/CWM installable zip thanks to SolidHelix. You must still be UNLOCKED and have already applied at least one version of this recovery via fastboot to use them.
Source is here.
A few notes:
The "osh" partition is webtop. It is the largest by far and will take some time to backup. Nandroid is not frozen!
The "sd-ext" partition is an ext2/3 partition on your external SD card. Veterans will know this as apps2sd and data2sd from other phones. I am not aware of any use of this partition on this phone yet.
Thanks to:
Koush and the CM team for CWM
Calkulin for pointing out the kernel
Everyone who has made unlocking the Photon possible

** Changelog **
2011-11-14 (5.0.2.7-photon3):
Minor bugfix update mostly
ext4 experimental support
Added the ability to convert an ext3 partition to ext4 under advanced. Shouldn't break anything, but it is experimental
2011-09-23 (5.0.2.3-photon2):
Updated to CWR5 base source.
The blue version is now the new CWR5 color. Old blue is gone. New photos welcome!
2011-09-17 (4.0.1.5-photon1.3):
Added a verify option to the backup and restore menu.
Renamed internal SD card mount point to /emmc and external is now /sdcard (this is largely cosmetic).
Merged in miscellaneous fixes from the official CWM. Version 5 will be merged in once its ready.
2011-08-17 (4.0.1.5-photon1.2):
Changed fstab to ext3 since no kernel support yet
2011-08-17 (4.0.1.4-photon1.1):
Added 0MB option to ext3 partition size under External SD card partitioning which removes any ext3 partitions from the card (choose 0MB ext3/0MB swap to have only a FAT32 partition).
Added a red build to the mix.
Updated the update-binary in the CWM zips to be tailored for this phone.
Minor fixes to sdparted (log file related mostly).
2011-08-14 (4.0.1.4-photon1):
Initial release
Screenshots
Thanks to DarkSim2o9 for the following screenshots (these show an Atrix, but the color is identical):
Orange
Cyan
Blue
Light green
Dark green
Red
Known Issues
I doubt ext4 support works due to no kernel support. Disabled currently. Added in -photon3.
Soft keys to use as navigation may not work due to the kernel.
Miscellaneous
If you'd like ROM Manager to see this recovery as "official" you can try XCellPhoneSalesRep's suggestion posted here.
Alternately, you can try dcarpenter85's suggestion here.
For issues with recovery not sticking, see here:
Thanks to mrinehart93 for pointing this out.
The system runs /system/etc/install-recovery.sh on boot with the stock rom. On boot it checks the recovery partition for some update and with CWM installed decides to reflash the stock recovery over it. Rename or delete the file and the CWM should stick.
Click to expand...
Click to collapse
Old versions
You can browse and download old versions here.

Awsome!!!
Sent from my MB855 using XDA App

Sounds good. Will try.
Sent from my unlocked rooted Moho!

This is what Calk posted earlier......right? I know it's yours, but not to be confused......just different colors...correct?

I like that there is a choice of colors. Well done!

Awesome job. One question, how might one boot direct into the recovery from a full Power Off?

the3rd said:
Awesome job. One question, how might one boot direct into the recovery from a full Power Off?
Click to expand...
Click to collapse
Hold down volume down and power till boot. Volume down till you see android recovery, then volume up.
Also, as aaron130 said you can use quick reboot from the market.
Sent from my unlocked rooted Mopho!

Fricken Awesomeness
Sent from my Photon Blaster.

ahhh this is what im getting..it seems fastboot isnt working for some reason even tho i just rooted..some help please
C:\AndroidSDK\tools\moto-fastboot>moto-fastboot devices
C:\AndroidSDK\tools\moto-fastboot>moto-fastboot erase recovery
< waiting for device >"
edit: nevermind got it working ..thanks!

Two questions:
1. Has anybody verified the "ROM Manager support" method on the Photon yet?
2. Other than color choice, what is the difference between this recovery and the one Calkulin posted earlier?

i think theres an issue with the recovery.
it installed perfectly and booted properly.
i chose to format the internal sd partition and it didnt remove any of the data.
i havent tried to flash anything yet or make a nandroid but ill keep you posted and i do have it loaded.
thanks for all of your hard work. greatly appreciated

the3rd said:
Awesome job. One question, how might one boot direct into the recovery from a full Power Off?
Click to expand...
Click to collapse
the same way you boot into fastboot
when phone is off.......
1. press and hold power and volume down
2. when the phone displays fastboot release the buttons
3. use volume down to switch to android recovery
4. press volume up and boot into cwm

Im creating a backup as I type (speak)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jglee311 said:
This is what Calk posted earlier......right? I know it's yours, but not to be confused......just different colors...correct?
Click to expand...
Click to collapse
Lokifish Marz said:
Two questions:
1. Has anybody verified the "ROM Manager support" method on the Photon yet?
2. Other than color choice, what is the difference between this recovery and the one Calkulin posted earlier?
Click to expand...
Click to collapse
Calkulin's is based off my -atrix3 revision. This is slightly newer code (-atrix3.1 bug fixes mostly). It uses the same kernel as his. He PM'ed me to let me know how he got it to work on this phone and I simply used his advice to create the thread.
I haven't verified ROM Manager on this phone. It may need until Koush updates ROM Manager to say it supports this phone. I thought several times about editing that out of the second post but chose to leave it for now..

tim-tim said:
i think theres an issue with the recovery.
it installed perfectly and booted properly.
i chose to format the internal sd partition and it didnt remove any of the data.
i havent tried to flash anything yet or make a nandroid but ill keep you posted and i do have it loaded.
thanks for all of your hard work. greatly appreciated
Click to expand...
Click to collapse
Under Mounts and Storage menu? If someone can provide me with /proc/mounts while booted into regular Android, I can check it out.

romracer said:
Under Mounts and Storage menu? If someone can provide me with /proc/mounts while booted into regular Android, I can check it out.
Click to expand...
Click to collapse
http://pastebin.com/uGakTEYu

Yay 4 Juggs said:
http://pastebin.com/uGakTEYu
Click to expand...
Click to collapse
Thanks, the table looks exactly like the Atrix (not surprising). If choosing "Format /sdcard" from the mounts and storage menu didn't work, I'll probably need /tmp/recovery.log after trying (but before exiting recovery - the file is lost then).

Minor update released. Biggest changes include 0MB ext partition option under external SD card partitioning which combined with 0MB swap gives you just a FAT32 partition without having to use Windows, etc. There's also a red version now.
The code is technically based on 4.0.1.5 but Koush pushed his commit late and so the build still says 4.0.1.4. I didn't see the need to recompile just for that

romracer said:
Minor update released. Biggest changes include 0MB ext partition option under external SD card partitioning which combined with 0MB swap gives you just a FAT32 partition without having to use Windows, etc. There's also a red version now.
The code is technically based on 4.0.1.5 but Koush pushed his commit late and so the build still says 4.0.1.4. I didn't see the need to recompile just for that
Click to expand...
Click to collapse
are the tools fixed such as being able to clear cache...nandroid...etc?

Related

[RECOVERY][5/6/11] ClockworkMod Recovery for X10mini / X8 - 3.2.0.0-r3

This is ClockworkMod Recovery (v.3.2.0.0) ported to work on X10mini / X10mini pro / X8
Introduction
ClockworkMod Recovery is the default recovery option by the CyanogenMod, it has several additional features over plain old xRecovery and uses Edify exclusively:
CyanogenMod said:
Amend scripting (update-script) is no longer supported
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Click to expand...
Click to collapse
Despite the non-support for Amend scripts, it's the future of Recoveries and cooks should get used to this kind of scripting when making their zips.
Update:
CWM 3.2.0.0-r3 introduces two new features that validate and restore the currently installed recovery and it's deps before reboot / shutdown. If the current recovery doesn't appear to be correct, it will prompt for a recovery restore option that at least guarantees that the phone can boot into recovery. This is NOT:
- a way to make any ROM that you installed boot
- an idiot proof mechanism (e.g. if you are prompted and omit restoring, you are on your own)
Features
ADB root shell
reboot system now
apply update from sdcard
wipe data / factory reset
wipe cache partition
install zip from sdcard
backup and restore
backup (also backs up ext partition and installed apps to sdcard)
restore (also restores ext partition and installed apps to sdcard)
restore from xRecovery (Use this in case you want to restore backups done with xRecovery)
advanced restore
mounts and storage
mount / unmount /cache
mount / unmount /data
mount / unmount /sdcard
mount / unmount /system
mount / unmount /sd-ext
mount / unmount /cache
format /cache
format /data
format /sdcard
format /system
format /sd-ext
mount USB storage
advanced
reboot recovery
wipe Dalvik Cache
wipe Battery Stats
report Error
key Test
partition SD Card
Ext Size (formatting as ext4)
Swap Size (Set this to 0)
Rest Size is for vfat
fix permissions
validate recovery
restore recovery
power off
Usage
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CW recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
Requirements
Stock 2.1 ROM
Busybox from the market
Root
Installation
EITHER:
If you have xRecovery: Flash the CWM recovery Amend zip
OR:
If you have a previous version of CWM Recovery: Flash the CWM recovery Edify zip
OR:
If you don't have a recovery installed, using Root explorer: manually extract any of the above CWM recovery zips and copy the contents of the system folder (system/bin and system/xbin) to /system, then give 755 permissions to those files, especially to /system/bin/chargemon, or you'll get bootloop.
Notes to everyone
Do NOT use this recovery if you are not in Stock 2.1 firmware. If you have a custom ROM, your cook should incorporate this to his ROM first
Notes to Devs/Cooks
To incorporate this to your ROM, extend the chargemon file to contain the needed part required in order to boot your ROM, the rest of the files need no changes.
Switch to Edify when giving updates for your ROMs. Search xda and google for that, there are plenty of resources out there. E.g: http://forum.xda-developers.com/showthread.php?t=936175
Also use the attached update-binary which is modified and tested to work correctly with this recovery.
Credits:
DaRk_dOg for his testing / support
koushd for writing the piece of software the first place
zdzihu for his rm -rf tip
Cyanogen for the obvious reasons...
Disclaimer:
I can't be held responsible if this Mod bricks your device or makes it explode in your hands! Use it at your own risk!
​
Changelog:
ClockworkMod Recovery v.3.2.0.0-r2:
- Added restore from xRecovery option
- Fixed letters cutoff at the bottom of the screen
ClockworkMod Recovery v.3.2.0.0-r1 for x10mini
- Ported default CM7 Recovery option
Thank you mate! Another great addition!
very cool but does this mean i cant install it when i am using your miniCM7 ??
freebordjunky said:
very cool but does this mean i cant install it when i am using your miniCM7 ??
Click to expand...
Click to collapse
That means you should bother the dev of your ROM.
....
And also check the MiniCM7 thread
Thanks a million! Will try on MiniCM6-1.0.1!
Sent from my X10mini using XDA Premium App
Great work. Thanks
o2gulo said:
Thanks a million! Will try on MiniCM6-1.0.1!
Sent from my X10mini using XDA Premium App
Click to expand...
Click to collapse
Uhm, you shouldn't.....
nobodyAtall said:
Notes to everyone
Do NOT use this recovery if you are not in Stock 2.1 firmware. If you have a custom ROM, your cook should incorporate this to his ROM first
Click to expand...
Click to collapse
Nobody.... I have one question. Though my phone gets stuck up in SE screen the CWM recovery works fine and shows up on repeated pressing of back button. Now once you upload the rectified ".zip" file can I not reflash it with CWM recovery and boot my device normally instead of going through the entire process of updating through SEUS?
This seems great as with all your work. May I bother you enough to make it work with MiniCM6, as the one you posted effed up my cellphone?
Keep up the great work, nAa
parthabhatta said:
Nobody.... I have one question. Though my phone gets stuck up in SE screen the CWM recovery works fine and shows up on repeated pressing of back button. Now once you upload the rectified ".zip" file can I not reflash it with CWM recovery and boot my device normally instead of going through the entire process of updating through SEUS?
Click to expand...
Click to collapse
Hi,
This thread is for Stock 2.1 ROMs only.
At the state you are, you need to reflash with SEUS and restore with xrecovery.
Good Thing I reverted Back to 2.1 ..
One question, If we use xRec and Flash it, will xRec be removed?
Is backward compatible with xRecovery? I mean themes updates and Backups made for xRecovery will work?
Sent from my X10mini using XDA App
It replaced xRecovery.. No problems at all... Works great... Thanks dude..
When want to replace my recovery i get:
E:Can't chown/mod /system/bin/charger
(No such file or directory)
E:Failure at line 4:
set_perm 0 0 0755 SYSTEM:bin/charger
Edit: well it seemed like it worked, well recovery is orange now
Now it is stuck on SE screen, i dit revert back to stock 2.1
nobodyAtall please help
a couple of questions,
1. i did a backup with the new cwm so the old backups from xrecovery wont work so can i delete them?
and
what is key test?
X10mini miniCM7 2.0.1 using XDA Premium App
This is really awesome, porting to mini pro right now! Thanks nAa, you're the man
cheers, d4.
EDIT:
@nAa Still some wrong on sizes, hope you can fix it, or upload sources, but awesome work, ported to mini pro, ofc all crdtis for you
EDIT2:
Can you please upload a modded version that says Mini pro? Thanks
I flashed the file zip, but the phone forces close..it doesn't work..i repaired the software with SE
Sent from my X10mini using XDA Premium App
the last line when making backup or something others is half cutted by backup is this : Backing up System
the words shows me like this (example from PC) :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
seams it isnt fixed on right resolution
*edit*
Great Port thx to all for make this happen
bitmovel said:
also, "fix permissions" does not work. the phone stops working. only battery off can make it run again
Click to expand...
Click to collapse
DJxSpeedy said:
the last line when making backup or something others is half cutted by backup is this : Backing up System
the words shows me like this (example from PC) :
seams it isnt fixed on right resolution
*edit*
Great Port thx to all for make this happen
Click to expand...
Click to collapse
Yeah, same here, btw, tried to make a edify script for flashing old xRecovery, and it gives me error ?, I used chumby's amend2edify tool

[RECOVERY] ClockworkMod Recovery for X10 Mini Pro - 3.2.0.0-r3

First, I need to say that this was not made by me!, all credits go to nobodyAtall, I just changed chargemon to make it work on mini pro, all roms, Please read original post here for more info
This is the latest ClockworkMod Recovery (v.3.2.0.0) ported to work on X10 mini pro
Introduction
ClockworkMod Recovery is the default recovery option by the CyanogenMod, it has several additional features over plain old xRecovery and uses Edify exclusively:
CyanogenMod said:
Amend scripting (update-script) is no longer supported
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Click to expand...
Click to collapse
Despite the non-support for Amend scripts, it's the future of Recoveries and cooks should get used to this kind of scripting when making their zips.
Update:
CWM 3.2.0.0-r3 introduces two new features that validate and restore the currently installed recovery and it's deps before reboot / shutdown. If the current recovery doesn't appear to be correct, it will prompt for a recovery restore option that at least guarantees that the phone can boot into recovery. This is NOT:
- a way to make any ROM that you installed boot
- an idiot proof mechanism (e.g. if you are prompted and omit restoring, you are on your own)
Features
ADB root shell
reboot system now
apply update from sdcard
wipe data / factory reset
wipe cache partition
install zip from sdcard
backup and restore
backup (also backs up ext partition and installed apps to sdcard)
restore (also restores ext partition and installed apps to sdcard)
restore from xRecovery (Use this in case you want to restore backups done with xRecovery)
advanced restore
mounts and storage
mount / unmount /cache
mount / unmount /data
mount / unmount /sdcard
mount / unmount /system
mount / unmount /sd-ext
mount / unmount /cache
format /cache
format /data
format /sdcard
format /system
format /sd-ext
mount USB storage
advanced
reboot recovery
wipe Dalvik Cache
wipe Battery Stats
report Error
key Test
partition SD Card
Ext Size (formatting as ext4)
Swap Size (Set this to 0)
Rest Size is for vfat
fix permissions
validate recovery
restore recovery
power off
Usage
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CW recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
Requirements
Working on any ROM .. Unified chargemon (For stock last version supported it's 2.1.1.A.0.6!, if you have newer, downgrade, don't working for stock 1.6)
Busybox from the market
Root
Installation
Install through CWM recovery (sorry no more support for xRecovery)
Credits:
nobodyAtall for porting this amazing software to mini, thumbs up to him PLEASE
All credits on original post
Fast Disclaimer: I'm not responsible if this brick your lovely device
Installing right now
Sent from my U20i using XDA Premium App
Just installed it on my mini pro, works fine. Much appriciated.
Thx to nobodyAtall too
Hey, awesome, I've been waiting for this on our Mini Pro's Thanks to you and nobodyatall! just a question - does this mean, we can use ROM Manager?
Ravencz said:
Hey, awesome, I've been waiting for this on our Mini Pro's Thanks to you and nobodyatall! just a question - does this mean, we can use ROM Manager?
Click to expand...
Click to collapse
I think it still need some changes, but we're close to get CWM recovery 100% functional
Ravencz said:
Hey, awesome, I've been waiting for this on our Mini Pro's Thanks to you and nobodyatall! just a question - does this mean, we can use ROM Manager?
Click to expand...
Click to collapse
This is the goal actually (or some other easy way to install updates), at least for MiniCM
Glad it works for you guys too
the last line when making backup or something others is half cutted by backup is this : Backing up System
the words shows me like this (example from PC) :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
seams it isnt fixed on right resolution
*edit*
Great Port thx to all for make this happen
With the ClockworkMod it's possible recorevy backup of the xrecovery??
Download now, hehe
DJxSpeedy said:
the last line when making backup or something others is half cutted by backup is this : Backing up System
the words shows me like this (example from PC) :
seams it isnt fixed on right resolution
*edit*
Great Port thx to all for make this happen
Click to expand...
Click to collapse
same error here.
also, "fix permissions" does not work. the phone stops working. only battery off can make it run again
Andreson01 said:
With the ClockworkMod it's possible recorevy backup of the xrecovery??
Download now, hehe
Click to expand...
Click to collapse
Testing as we speak. Please remember you cannot use xrecovery folder anymore. you must move it to new clockworkmod foler
bitmovel said:
same error here.
also, "fix permissions" does not work. the phone stops working. only battery off can make it run again
Testing as we speak. Please remember you cannot use xrecovery folder anymore. you must move it to new clockworkmod foler
Click to expand...
Click to collapse
Please make this reports on X10 mini thread, nAa sure will give us a answer
Just tested:
Yes! It can restore xrecovery backups. Just move them to the new directory
Thank you!!
D4rKn3sSyS said:
Please make this reports on X10 mini thread, nAa sure will give us a answer
Click to expand...
Click to collapse
ive quoted my post here with bitmovel's post to mini thread
thanks
bitmovel said:
thanks
Click to expand...
Click to collapse
no problem
31 download and 4 thanks ... Some of you guys dont really appreciate the dev's work, same with nAa post, i dont care thanks on me, but at least thank to nAa, he's a awesome dev
D4rKn3sSyS said:
31 views and 4 thanks ... You guys dont really appreciate the dev's work, same with nAa post
Click to expand...
Click to collapse
Hey mate i love your work! I'm on mobile i give you a thanks tomorrow! Use the force dev and never say die! You are great! ;-)
Inviato dal mio U20i usando Tapatalk
Just tested it on my mini pro and seems to work just fine. Only the last line in the "loogging" part is sligtly under the screen and therefore cut-off but that's not a big issue as the text is still very readable
Testing report: fix permissions IS working, as normal it take a while, exactly equal that on xRecovery, so test it again people who are having problems, will take about 2 mins, seems to be that clean battery status it's not working.. im doing tests
EDIT: Confirmed working on r2, nicely working, only 1 bug left, sd-ext mount, already reported to nAa
D4rKn3sSyS said:
Testing report: fix permissions IS working, as normal it take a while, exactly equal that on xRecovery, so test it again people who are having problems, will take about 2 mins, seems to be that clean battery status it's not working.. im doing tests
Click to expand...
Click to collapse
thanks.
looks like I didnt wait enough time.
I miss your xrecovery backgrounds... hehe

[TOUCHCOVERY] ORIGINAL | 4EXT Recovery Touch v1.0.0.5 RC6 with SmartFlash for s-on

Proudly presenting:
4EXT Recovery Touch
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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:
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.
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​
All downloads are available through 4EXT Recovery Updater.
It's free, no ads, no tracking, no nothing, don't worry
..and of course via 4EXT Recovery Control
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.
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.
4EXT Recovery Control
Free version: Recovery Updater
Fully featured: 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
Big thanks to craacK for a lot of great icons!
​
Thanks:​
Big thanks to DolphiCom for all the graphics, the worker bar and a whole lot of great ideas and to the many great testers who spent all day/night testing, reporting bugs, making suggestions, helping with decisions:
Jotha, craacK, Patrics83, Euphorie, Mike1986, Whiskey103, ptr_hamilton, Lizard, TheUntouchable
Big thanks to Jotha and Whiskey103 for testing the themes features creating and their first themes for 4EXT Recovery Touch.
Special thanks to Dees_Troy who joined #4ext several times, just to tell me about important things he assumed I didn't know (and he was right! )
Also Big thanks to all the donators to 4EXT Recovery and everyone who has bought 4EXT Recovery Control! Without you I wouldn't be able to spend as much time with the project:
SO A HUGE THANK YOU!​
FRANKIE-BOY, BENJAMINNZIS, DESPERANTO86, SYRAKUS, VRC8883, FISHA21, ZJXPOT, ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, HAWST, ANIT77, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
Of course BIG THANKS to KOUSH for ClockworkModRecovery!
Without him, 4EXT Recovery wouldn't exist!​
Thanks a lot to the following users for initial testing for specific devices :
SPEEDYCARV, PTR_HAMILTON, JAMESCLINTON, SNOWBOARDKID503, MJESSE81, SEBASTIAAN15, THEUNTOUCHABLE, BMONSTER, ANDREIGHERGHE, PRESTON74, MADKAI, YASIR, PLAYPETEPP
IPERZAMPEM0, THESHAWTY, JBBANDOS, TAZMAN1963, GREGFERNS and INCREDULOUS
Special thanks to Invasion2 and Stlouie65 for spending at least 10 hours of their time helping me debug a really nasty issue on the myTouch 4G!
Also thanks for obtaining calibration values for the touchscreen:
Mjesse81,
Speedycarv,
Wolfepakt
Jaibar
Jayallen1980
Stlouie65
Invasion2
PacerguyDon
Ben_Pyett
Dargocitfer
Darknessrise1234
Lizard
Azazel71
​
Features of 4EXT Recovery Classic:
(Use 4EXT Recovery Control or Recovery Updater for complete Changelogs and Known issues!)
not all features may be relevant for all devices
Displays additional information:
Identifies your current rom and displays its name
Current filesystems on your partitions
Free space remaining of all of your volumes
Current battery charge level
Backup | Restore:
Correctly calculates free space needed to complete a backup ( version > 2.2.6 RC4 )
Tar backups (can be switched on or off)
Complete CWMR5 compatibility
All Backups you create will be named after your currently installed Rom for easier identification.
Never unwillingly get "downgraded" to EXT3 again
Always restores backups using the file systems you HAD on your partitions at the time of creation!
-> all partitions formatted with ext4 at that time, will be restored to ext4. The same is true for ext3.​
You can manually change any existing Backup to ext4 or ext3
-> so that after a restore, all partitions and up with the file system you wanted!​
Advanced Backup: backup only a single partition
Convert any of your partitions to EXT4 or EXT3 without data loss.
Formatting:
When you wipe or format it will always use the same file system you currently have.
-> but you can change that​
When you format ext4 it will always create an aligned file system
Correctly identifies unformatted sd-ext partitions
-> if it finds one it displays a warning and suggests you may format them by visiting the 4EXT menu​
Filesystem check and repair option in advanced menu
Partitioning:
Alignment check of your partitions
Full support for up to 2 sd-ext partitions + swap (Backup/restore/format/convert, fsck, et.c.)
(RE-) Partition your sdcard for sd-ext without removing your fat32 partition.
All partitions created with 4EXTRecovery will be perfectly aligned to 4k
Installing:
Integrated md5sum checking option
Menus:
Most popular menu items rearranged
Format menu
Power Menu + option to reboot into bootloader
Changed Advanced Restore: first select what you want to restore, then select the backup
-> Useful for restoring from "Advanced Backups"​
4ext.prop:
Configuration file on your sdcard where you can set options to be used by 4EXTRecovery
Change all settings conveniently with 4EXT Recovery Control
Many more options to come
Share your settings / themes by packing your config into a flashable theme
Other stuff:
USB Storage Autostart (must be switched on)
Mount usb storage exposes all partitions on your sdcard to the os (not just fat32)
-> you could even partition your sdcard from your PC while connected via USB​
Switch haptic feedback on/off
Button backlights
​
Recovery Interface Api for Apps and Scripts​
Both: free and paid 4EXT apps now provide a very easy to use interface you can use to access 4EXT Recovery from within your shell scripts or apps.
Features:
wipe cache
wipe dalvik
wipe data / factory reset
install multiple zips at once
backup
If you are interested, please download this zip file with examples​
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:
Code:
if getprop("ext.edition") == "ng" then
<your code>
endif;
To use the native confirm dialogues:
Code:
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 )
Code:
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.
Oh yeah I have been waiting for this!!
Thanks alot!!
1st post ;D
best app
Yeah after a long time
Hi,
Any links to the themes?
thanks
4D3 said:
Hi,
Any links to the themes?
thanks
Click to expand...
Click to collapse
In my signature and inside the app in the themes menu
And also somewhere inside the post
it looks very nice, good job
Does the new touch 4ext recovery have the phone-off charging bug?
rahditzz said:
Does the new touch 4ext recovery have the phone-off charging bug?
Click to expand...
Click to collapse
it will charge your device to death
jk, no, charging works inside and outside recovery.
GREAT! I honestly wasn't expecting this!
I just flashed it (latest beta, RC4). It boots, the battery level and time is right, the display works fine... I'll test the backup/restore/flash functions later this week.
--
It appears that the phone DOES charge while it's turned off! Same behavior as when using the Revolutionary 4.0.1.4 recovery (LED goes red for a few seconds, then turns off, then goes back on (red) and stays that way, == charging ).
GREAT WORK !
Awsome.. Loving it already.. hehe..
madmaxx82 said:
In my signature and inside the app in the themes menu
And also somewhere inside the post
Click to expand...
Click to collapse
I guess i can use any for the sensation?
thanks
Formhault said:
GREAT! I honestly wasn't expecting this!
I just flashed it (latest beta, RC4). It boots, the battery level and time is right, the display works fine... I'll test the backup/restore/flash functions later this week.
--
It appears that the phone DOES charge while it's turned off! Same behavior as when using the Revolutionary 4.0.1.4 recovery (LED goes red for a few seconds, then turns off, then goes back on (red) and stays that way, == charging ).
GREAT WORK !
Click to expand...
Click to collapse
Thanks!
Why weren't you expecting this ?
It's very unlikely that there are any real bugs, because it's just an improvement over RC2.
But with any new build, even if there weren't alot of changes, there is still a certain "risk".
That's why any new release gets flagged as "testing".
1.0.0.4 RC2 is the fastest 4EXT Recovery yet and as stable as the most stable version released since June last year.
Let's see how Build Nr. 2 of RC3 will behave.
madmaxx82 said:
Thanks!
Why weren't you expecting this ?
It's very unlikely that there are any real bugs, because it's just an improvement over RC2.
But with any new build, even if there weren't alot of changes, there is still a certain "risk".
That's why any new release gets flagged as "testing".
1.0.0.4 RC2 is the fastest 4EXT Recovery yet and as stable as the most stable version released since June last year.
Click to expand...
Click to collapse
I had the Desire HD and I was using this recovery! RC2, I believe, 3 months ago. I still use it on my girlfriend's Desire S !
I wasn't expecting it to be 1.0.0.4, the same as for the other phones, and in perfect condition! I thought this would be the first build...
Formhault said:
I had the Desire HD and I was using this recovery! RC2, I believe, 3 months ago. I still use it on my girlfriend's Desire S !
I wasn't expecting it to be 1.0.0.4, the same as for the other phones, and in perfect condition! I thought this would be the first build...
Click to expand...
Click to collapse
The code for all devices is the same.
Only some adjustments regarding the Touchscreen were needed for the Evo GSM
Edit: ohh and the charging problems
BTW: Please upgrade the rc2 you mention is too old so it can't be 1.0.0.4
Formhault said:
I just flashed it (latest beta, RC4).
Click to expand...
Click to collapse
Where did u get RC4? I can only get RC3..:S
rahditzz said:
Where did u get RC4? I can only get RC3..:S
Click to expand...
Click to collapse
4EXT Recovery app... That's how I got it. There's no other way you can possibly get it, anyway .
Hmm.. RC4 isnt showing up for me..:S
madmaxx82 said:
The code for all devices is the same.
Only some adjustments regarding the Touchscreen were needed for the Evo GSM
Edit: ohh and the charging problems
BTW: Please upgrade the rc2 you mention is too old so it can't be 1.0.0.4
Click to expand...
Click to collapse
Then perhaps my memory was failing on me . I'll see tomorrow what version it is on my gf's DS and update it (I only use it once every few months, anyway). I no longer own the DHD, btw.
Thanks again for bringing the 3VO into your supported-phones line
@those not being able to see RC4... Perhaps you should update the 4EXT Recovery Control app... Latest is v2.3.1
Sent from my LeeDrOiD-loaded 3VO

[recovery] twrp 2.8 OFFICIAL INTERNATIONAL

Team Win Recovery Project 2.8, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
***WHAT WORKS***
EVERYTHING and it's been made OFFICIAL
MAKE SURE YOU GET THE CORRECT VERSION'S I WILL NOT BE TO BLAME IF YOU FLASH THE WRONG ONE
READ THIS IF YOU FLASH THE RECOVERY AND THEN ASK ME QUESTIONS I WILL POINT YOU TO THIS THREAD OR EVEN IGNORE YOU
READ REGARDING ADB IN RECOVERY
TWRP IRC CHANNEL
DOWNLOAD
DOWNLOAD ---- MY BUILD
Thanks to
The TWRP GUYS
and football for his ruu's so i can get the img's i need
and milestoner for confirming it works
Mr anon
and all the following people
orb3000
morphly
hasoon2000
hasan_abeer
vogi
chrigel2000
AndroHero
ectodroid
[email protected]
Anon #1
Ixz
bboerny
Anon #2
Anon #3
sellers86
Wik
Anon #4
simonsimons34
caedanne
flipside101
morphly
bboerny
TWRP WEBSITE
**INSTRUCTIONS**
Download the file
then either use HASOON'S toolkit
or
Manual method
reboot into bootloader
fastboot flash recovery TWRPrecovery.img
SIDELOAD INSTRUCTIONS
MarylandCookie said:
I had the same issue and fixed it via adb sideload.
I have uploaded the latest binaries to my dev host account.
1. Download and extract these to a directory and copy the rom over into the same directory.
2. Boot up your phone into twrp recovery.
3. Select advanced and adbsideload (Your phone will be waiting for the file transfer.)
4. Open command prompt in the above directory you created with the binaries and rom.
5. Issue command "adb devices" (You should get the serial number with sideload next to it)
6. Finally issue command "adb sideload rom.zip" (rom.zip will be the name of your rom)
This will start sending your rom to the handset and will automatically install.
Hope the above helps
Link to Binaries:
ADB Binaries
Click to expand...
Click to collapse
Code:
CHANGELOG
19/11/12
Last unofficial build (all builds forward are official direct from TWRP)
AT&T added
data/media sorted
-----------------------------------
Build 1 16/11/12
1st build
LET ME KNOW OF ANY PROBLEMS
any feedback on this guys?
Wow. I didnt even see this. I couldve added it to my toolkit lol. ill wait til people say if it works and then ill add. Thanks Lloir!
if it work's i'll talk to dees_troy about making it official
So it's still untested? I would like to install it but I'm afraid it will brick my phone somehow..
Edit: Flashed it but I can't seem to browse through the sdcard, just the internal system (/sdcard vs /sdcard1) where the app/system etc. is located.
thecompany said:
So it's still untested? I would like to install it but I'm afraid it will brick my phone somehow..
Edit: Flashed it but I can't seem to browse through the sdcard, just the internal system (/sdcard vs /sdcard1) where the app/system etc. is located.
Click to expand...
Click to collapse
meh thanks dude, i'll look into this more when i get the HOX+
locking thread for now
Got a report that this is working fine, the sdcard is under /sdcard/media so it works perfect!
thanks milestoner for pointing this out!
Does this work with At&t HTC one X+?
Sent from my HTC One X+ using xda premium
samomamo said:
Does this work with At&t HTC one X+?
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Now it does
Sent from my One V using Tapatalk 2
Just a few comments:
- can't mount SD Card in Recovery (or at least can't access to it)
- backup/nandroid is saved in (SDCard - DATA) / TWP
and not in (SDCard - DATA)/media, so can't access to the back-up
Steve0007 said:
Just a few comments:
- can't mount SD Card in Recovery (or at least can't access to it)
- backup/nandroid is saved in (SDCard - DATA) / TWP
and not in (SDCard - DATA)/media, so can't access to the back-up
Click to expand...
Click to collapse
cant access it from TWRP? or? i cant test sdcard mount as linux is being a *****, but it looks like it mounts fine, i have a nandroid and i can see it to restore......
*edit*
nevermind see what you mean, i'll sort it for the next build
I can confirm that mount points are borked at the moment. While in recovery the sdcard can be found in /sdcard/media. Backing up seem to work ok but backups are insanely huge (6.6GB for a compressed backup!). This is probably because everything including the whole sdcard is backed up. While TWRP itself finds the backups just fine, when android is running they are located in /data/TWRP. I haven't tried to restore a backup yet.
I'm a little bit worried about what will happen later if I try to restore one of my backups that are made with the current TWRP version. Will the fixed version recognize and correct the mixed up mount points of the current version? If not, I can forget about all of my current backups .
---------- Post added at 01:18 PM ---------- Previous post was at 01:10 PM ----------
Just two more minor details: Time and battery values displayed at the top of TWRP are wrong. The battery stays put at 66% and time is shifted by a couple of hours.
Thanks again for your work!
milestoner said:
I can confirm that mount points are borked at the moment. While in recovery the sdcard can be found in /sdcard/media. Backing up seem to work ok but backups are insanely huge (6.6GB for a compressed backup!). This is probably because everything including the whole sdcard is backed up. While TWRP itself finds the backups just fine, when android is running they are located in /data/TWRP. I haven't tried to restore a backup yet.
I'm a little bit worried about what will happen later if I try to restore one of my backups that are made with the current TWRP version. Will the fixed version recognize and correct the mixed up mount points of the current version? If not, I can forget about all of my current backups .
---------- Post added at 01:18 PM ---------- Previous post was at 01:10 PM ----------
Just two more minor details: Time and battery values displayed at the top of TWRP are wrong. The battery stays put at 66% and time is shifted by a couple of hours.
Thanks again for your work!
Click to expand...
Click to collapse
yea the battery thing is a pain, time you can set yourself...the fstab is fine, it's other settings i need to sort out, just working on the AT&T one and then i'll sort this one out
@LIoir
you wont belive it but HTC ONE X+ source code for Kernel is out (sorry for writing it here), so i can start to look into it !
I will try to push the source to github tonight, so you can also have a look into it and if you still wont to, we can work together on it
Op updated!
Lloir said:
Op updated!
Click to expand...
Click to collapse
ATT FTW!!!! Unfortunately the link is dead. Thank you for your wonderful efforts none the less
sparkplug619 said:
ATT FTW!!!! Unfortunately the link is dead. Thank you for your wonderful efforts none the less
Click to expand...
Click to collapse
woops was a typo
http://cyano-rob.tuennerhoff-edv.de/RECOVERY/TWRP/evitareu/recovery.img
there's the link also link is fixed in the OP
Lloir said:
woops was a typo
http://cyano-rob.tuennerhoff-edv.de/RECOVERY/TWRP/evitareu/recovery.img
there's the link also link is fixed in the OP
Click to expand...
Click to collapse
If this works, can an AT&T user make a nandroid and upload the boot.img and system?

[RECOVERY/M8_UL_CA] TWRP 2.7.0.4 Touch Recovery [2014-04-09]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
What's new in 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
What's new in 2.6.3.0:
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
What's new in 2.6.1.0:
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
Downloadhttp://androidfil.es/1mMD
Huge shoutouts go specifically to
@Flemmard @bigbiff @Dees_Troy
I learned how to properly deal with DTB from these guys....
Known Issues:
No known issues anymore
No exFAT support. Need kernel source to investigate
Random segfaults when starting actions. i.e. flashing restoring, backing up. Just makes you redo what you were trying to do. Dees_troy deems this nearly impossible to trace.
Glad to see you here JMZ!!
Hi I'm trying to get a recovery flashed on my phone and I've been working with mike1986 for a couple hours and for whatever reason my phone refuses to flash it. Every time I run the fastboot flash recovery command it gets to: sending 'recovery'... and then just hangs there indefinitely until I reboot. Any ideas? Thanks!
im getting cache errors in the recovery.
fix-this! said:
im getting cache errors in the recovery.
Click to expand...
Click to collapse
Can you pull /tmp/recovery.log and post here. I'm not seeing this on my device
Sent from my HTC One_M8 using Tapatalk
jmz said:
Can you pull /tmp/recovery.log and post here. I'm not seeing this on my device
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Just tried to flash it. It worked when I backed up to internal memory but when I tried to back up to the external sd card I got this error:
E: Unable to create folder: /external_sd/TWRP/BACKUPS/SerialNum/Date
errno=13
failed to make backup folder
graffixnyc said:
Just tried to flash it. It worked when I backed up to internal memory but when I tried to back up to the external sd card I got this error:
E: Unable to create folder: /external_sd/TWRP/BACKUPS/SerialNum/Date
errno=13
failed to make backup folder
Click to expand...
Click to collapse
you on freenode anywhere?
jmz said:
you on freenode anywhere?
Click to expand...
Click to collapse
Not at the moment. I'm in class. I should be home on a couple of hours
Sent from my HTC One_M8 using Tapatalk
Uploaded a new version. Tested backing up to external sdcard and OTG. Not quite sure what the issue was before
How is this different from the one posted in the international m8 section? I see this is 2.7.0.0 though. Is it wise to run theirs or no?
jmz said:
Uploaded a new version. Tested backing up to external sdcard and OTG. Not quite sure what the issue was before
Click to expand...
Click to collapse
Still getting the same error. I'll be home in a few and can jump on irc
and to add to it.. When it failed to back up I pressed the reboot system button right there. All the other times I would back out to the main menu to the reboot menu.. Now after I pressed reboot right after the error I'm stuck at the bootlogo, no adb access and holding power isn't rebooting the phone either
I got it to reboot by holding volume up and power. Booted back in now.. That was odd.
graffixnyc said:
Still getting the same error. I'll be home in a few and can jump on irc
and to add to it.. When it failed to back up I pressed the reboot system button right there. All the other times I would back out to the main menu to the reboot menu.. Now after I pressed reboot right after the error I'm stuck at the bootlogo, no adb access and holding power isn't rebooting the phone either
I got it to reboot by holding volume up and power. Booted back in now.. That was odd.
Click to expand...
Click to collapse
What format is your sdcard in
Sent from my HTC One_M8 using Tapatalk
Adb fasboot flash recovery recovery.img right? Been awhile lol
Sent from my HTC One_M8 using Tapatalk
Fidelio_o said:
Adb fasboot flash recovery recovery.img right? Been awhile lol
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
It should just be
Code:
fastboot flash recovery recovery.img
The "adb" at the beginning isn't necessary.
fix-this! said:
How is this different from the one posted in the international m8 section?
Click to expand...
Click to collapse
I'm curious to know too.
fix-this! said:
How is this different from the one posted in the international m8 section? I see this is 2.7.0.0 though. Is it wise to run theirs or no?
Click to expand...
Click to collapse
Tikerz said:
I'm curious to know too.
Click to expand...
Click to collapse
this is built from source. Not ported from M7. plus this supports external sdcard
im getting error: cannot open recovery.img
NEVERMIND IM AN IDIOT
Uploaded a new version. 2.7.0.2 This has working offmode charging
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Having the same issue with my SD card as above. 64gb SD formatted in exfat. System uses it fine for photos etc...
Sent from my HTC One_M8 using Tapatalk

Categories

Resources