Here CLK 1.5 with 4EXT RC5 themed working 100%
kasserx said:
Here CLK 1.5 with 4EXT RC5 themed working 100%
Click to expand...
Click to collapse
Nice, where is the zip..???
Whats the difference between this and CWM's Ext3? Is it faster or something?
mountainmon said:
Whats the difference between this and CWM's Ext3? Is it faster or something?
Click to expand...
Click to collapse
.... 4EXT... not EXT4... wakie wakie...
on that note, its nice to see, but putting the crapple logo on our wonderful hd2 makes me want to "slaps OP with a rather large trout"... to quote old IRC emotes..
That will not say anything, but try not to lose anything
ex4 faster than ext3
lol apple!!!!! hope this is some kind of a joke
kasserx said:
That will not say anything, but try not to lose anything
ex4 faster than ext3
Click to expand...
Click to collapse
Hi, there's a mistake with the name, 4ext is NOT the same as EXT4. Yes, it seems equal but there two different things. The object of that thread is a kind of recovery.
A question for the author: the first edition of 4ext that I tried doesn't power on the phone while is plugged to charger. Is this item corrected right now?
look at Attached Thumbnails you'll see ext4 format (sd-ext) that not fake
Rando81 said:
lol apple!!!!! hope this is some kind of a joke
Click to expand...
Click to collapse
I think you did not see the word Themed in the title
kasserx said:
I think you did not see the word Themed in the title
Click to expand...
Click to collapse
no, we just wished you had put iCrapple themed instead of just themed...
And the misunderstanding continue to fly...
EXT# <- this is the formatting for the file system, with EXT4 being better (in most cases) in terms of performance then EXT3 (sadly, no headway on EXT4 NAND.. QQ)
4EXT <- this is an alternative recovery platform much like CWM and AmonRa and TWRP, it has the ability to format (external media only at the moment) your media to EXT4 and set specifics like size, offset, and even alignment, its REALLY good when setting things up for a first run*
Please READ and stop confusing the two... ones a file system, and ones a TOOL that CAN use said file system;...
*I have used 4EXT to format all 6 of my MicroSD cards and align them properly, FAT32 -> EXT4 -> SWAP in partition layout, or Storage -> App2SD -> PseudoRAM
Hammerfest said:
no, we just wished you had put iCrapple themed instead of just themed...
And the misunderstanding continue to fly...
EXT# <- this is the formatting for the file system, with EXT4 being better (in most cases) in terms of performance then EXT3 (sadly, no headway on EXT4 NAND.. QQ)
4EXT <- this is an alternative recovery platform much like CWM and AmonRa and TWRP, it has the ability to format (external media only at the moment) your media to EXT4 and set specifics like size, offset, and even alignment, its REALLY good when setting things up for a first run*
Please READ and stop confusing the two... ones a file system, and ones a TOOL that CAN use said file system;...
*I have used 4EXT to format all 6 of my MicroSD cards and align them properly, FAT32 -> EXT4 -> SWAP in partition layout, or Storage -> App2SD -> PseudoRAM
Click to expand...
Click to collapse
Thanks to cjward23 and friends for testing, 4EXT Recovery is now also available for the Desire Z / G2.
Quick note about themes:
Available themes as of Aug/28:
Themes by pravus_nephilim
Themes by Apaquette420
Themes by Whiskey103
Themes by Amresh
Themes by Apaquette420
Themes by CWhitney24
Themes by DaMyth
Themes by Blindndumb
To uninstall any "flashed theme" and to revert to your own custom settings you had before flashing, just use this Theme Uninstaller in recovery.
It will clear any theme you might have flashed and revert to your own custom settings you had before flashing that theme!
THANKS:
All credits and my deepest respect go to Koush for his extremely great code!
Without him 4EXT Recovery wouldn't have been possible!
Biggest thanks possible go to Sebastiaan15 for his brilliant ideas and who spent whole weeks testing my buggy code with his Desire
Without you I could never have made it!!!
So BIG THANKS to SEBASTIAAN15 and KOUSH for his hard work with CWMR !!!
Many credits to the Desire S community ( especially to loveboatcaptain - LBC Mod Android Development and Marylandcookie ) for testing, very nice ideas, feature suggestions and helping to get the code running on the Desire S!
Special big thanks to RAVENNA from android-hilfe.de board for hours of testing for the Desire!
BIG Thanks to Hussainmushahid who helped me a lot spending much of time with solving a bug I could not reproduce on my device.
And many thanks to all users who reported and helped to identify problems ( can't any longer list all of you here since the list has grown too large )!
Even more thanks to people who 've bought me some beer YOU ROCK!! ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
v2.2.6 RC4 Released: Oct/01
• Rare Superuser problem when tar backups were enabled (disabled by default) was fixed.
• Converting partitions between ext3 and ext4 without data loss now correctly calculates the space needed to successfully complete the operation
• New option: check and optionally repair the file system on your sdcard (fat32)
• Removed duplicate format cache option inside the format menu (wipe cache does the same)
• When formatting fat32 it will now save your 4ext.prop settings and restore them afterwards
• Changed partitioning of the sdcard to not use LBA mode for new fat32 partitions as requested by Ghiki
• Added new size option (128mb) to the partitioning menu per request
• Parted is no longer used to format fat32 in the partition menu
-> This solves a bug where sometimes the creation of the fat32 file system failed and produces better quality results
• 4EXT Recovery themes should now stay when formatting /system or flashing new roms
• New option: format /sdcard fat32
• New 4EXT Recovery Control API because I'm forced to drop "extendedcommand" (see App for the reason why)
enables file names and directories to include spaces for installations
calculates needed space to complete a full or advanced backup at the beginning of the backup.
This ensures that you are not left with a non working backup.
• Size for recovery greatly reduced
New 4EXT Recovery Control Features
• Please see www.4ext.net for more.
• Fix permissions
• Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
• As an example, the following would be 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.
Features: 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
Themes:• Customize all colours used throughout recovery
• Use your own icons, background images, progress bars.. more to come.
• Assign different backgrounds to different menu categories (version >= 2.1.2)
• Create a flashable zip for others to flash your theme.
Menus:• Most popular menu items rearranged
• Format menu
• Power Menu + option to reboot into bootloader
• Less "No's" in confirmation dialogues
• 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
• You don't need to reboot recovery if you transferred a file to show up in the install menu.
-> This bug affected only some users with either CWMR or previous versions of 4EXT.
• Button backlights (Desire S, Desire HD and Incredible S only)
Download:
•All downloads are now 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
• It also notifies you when there are any new critical bugs found
• Recovery images will be uploaded for download soon too, but they can also be acquired easily by using Updater or Control.
• You can for example just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
4EXT Recovery Control •Free version: Recovery Updater
•Fully featured version: 4EXT Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :•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 to "forcefully" restore it!
• Calculate real values for the space needed to create a new full or advanced backup
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
• 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
Recovery theming • Uninstall and Install themes with live preview and the option to change their colours without the need to reboot into recovery.
• Change all colours with live preview and a nice colour picker.
__________________
Please send bugreports | feature requests via:
4EXT Recovery Control or Updater App
4EXT Recovery Touch 1.0.0.3 RC 3
Free 4EXT Recovery Updater v2.2.5
Want to support development of 4EXTRecovery?
Check out 4EXT Recovery Control
please read this full it is from www.4ext.net ((for desire hd sensation ...etc)) now for hd2
http://forum.xda-developers.com/showthread.php?p=17748849
hd2
kasserx said:
Thanks to cjward23 and friends for testing, 4EXT Recovery is now also available for the Desire Z / G2.
Quick note about themes:
Available themes as of Aug/28:
Themes by pravus_nephilim
Themes by Apaquette420
Themes by Whiskey103
Themes by Amresh
Themes by Apaquette420
Themes by CWhitney24
Themes by DaMyth
Themes by Blindndumb
To uninstall any "flashed theme" and to revert to your own custom settings you had before flashing, just use this Theme Uninstaller in recovery.
It will clear any theme you might have flashed and revert to your own custom settings you had before flashing that theme!
THANKS:
All credits and my deepest respect go to Koush for his extremely great code!
Without him 4EXT Recovery wouldn't have been possible!
Biggest thanks possible go to Sebastiaan15 for his brilliant ideas and who spent whole weeks testing my buggy code with his Desire
Without you I could never have made it!!!
So BIG THANKS to SEBASTIAAN15 and KOUSH for his hard work with CWMR !!!
Many credits to the Desire S community ( especially to loveboatcaptain - LBC Mod Android Development and Marylandcookie ) for testing, very nice ideas, feature suggestions and helping to get the code running on the Desire S!
Special big thanks to RAVENNA from android-hilfe.de board for hours of testing for the Desire!
BIG Thanks to Hussainmushahid who helped me a lot spending much of time with solving a bug I could not reproduce on my device.
And many thanks to all users who reported and helped to identify problems ( can't any longer list all of you here since the list has grown too large )!
Even more thanks to people who 've bought me some beer YOU ROCK!! ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
v2.2.6 RC4 Released: Oct/01
• Rare Superuser problem when tar backups were enabled (disabled by default) was fixed.
• Converting partitions between ext3 and ext4 without data loss now correctly calculates the space needed to successfully complete the operation
• New option: check and optionally repair the file system on your sdcard (fat32)
• Removed duplicate format cache option inside the format menu (wipe cache does the same)
• When formatting fat32 it will now save your 4ext.prop settings and restore them afterwards
• Changed partitioning of the sdcard to not use LBA mode for new fat32 partitions as requested by Ghiki
• Added new size option (128mb) to the partitioning menu per request
• Parted is no longer used to format fat32 in the partition menu
-> This solves a bug where sometimes the creation of the fat32 file system failed and produces better quality results
• 4EXT Recovery themes should now stay when formatting /system or flashing new roms
• New option: format /sdcard fat32
• New 4EXT Recovery Control API because I'm forced to drop "extendedcommand" (see App for the reason why)
enables file names and directories to include spaces for installations
calculates needed space to complete a full or advanced backup at the beginning of the backup.
This ensures that you are not left with a non working backup.
• Size for recovery greatly reduced
New 4EXT Recovery Control Features
• Please see www.4ext.net for more.
• Fix permissions
• Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
• As an example, the following would be 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.
Features: 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
Themes:• Customize all colours used throughout recovery
• Use your own icons, background images, progress bars.. more to come.
• Assign different backgrounds to different menu categories (version >= 2.1.2)
• Create a flashable zip for others to flash your theme.
Menus:• Most popular menu items rearranged
• Format menu
• Power Menu + option to reboot into bootloader
• Less "No's" in confirmation dialogues
• 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
• You don't need to reboot recovery if you transferred a file to show up in the install menu.
-> This bug affected only some users with either CWMR or previous versions of 4EXT.
• Button backlights (Desire S, Desire HD and Incredible S only)
Download:
•All downloads are now 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
• It also notifies you when there are any new critical bugs found
• Recovery images will be uploaded for download soon too, but they can also be acquired easily by using Updater or Control.
• You can for example just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
4EXT Recovery Control •Free version: Recovery Updater
•Fully featured version: 4EXT Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :•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 to "forcefully" restore it!
• Calculate real values for the space needed to create a new full or advanced backup
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
• 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
Recovery theming • Uninstall and Install themes with live preview and the option to change their colours without the need to reboot into recovery.
• Change all colours with live preview and a nice colour picker.
__________________
Please send bugreports | feature requests via:
4EXT Recovery Control or Updater App
4EXT Recovery Touch 1.0.0.3 RC 3
Free 4EXT Recovery Updater v2.2.5
Want to support development of 4EXTRecovery?
Check out 4EXT Recovery Control
please read this full it is from www.4ext.net ((for desire hd sensation ...etc)) now for hd2
http://forum.xda-developers.com/showthread.php?p=17748849
Click to expand...
Click to collapse
are u sure this works on hd2 as read post on link above and it doesnt mention our hd2 i dont want 2 brick my phone if its not compatible???!?
Hi, zip in first post contains cLk 1.4, not 1.5 am I right ?
BTW thanks for sharing
no reply
maddoc1007 said:
are u sure this works on hd2 as read post on link above and it doesnt mention our hd2 i dont want 2 brick my phone if its not compatible???!?
Click to expand...
Click to collapse
since no 1 answered this i take it its not for.hd2s?
maddoc1007 said:
since no 1 answered this i take it its not for.hd2s?
Click to expand...
Click to collapse
On my HD2 EU it worked, but i can't change current theme to any another 4EXT theme.
CyCaHuH-uBAH said:
On my HD2 EU it worked, but i can't change current theme to any another 4EXT theme.
Click to expand...
Click to collapse
you can re-flash from beginning
see this video from my hd2
http://www.youtube.com/watch?v=T_BIaVduUDs&feature=player_embedded
http://www.youtube.com/watch?v=T_BIaVduUDs&feature=player_embedded
see this pictures also from my hd2
go to medifire ( image view )
http://www.mediafire.com/?vbe9sfz2b...mv84ibfd3a2r3,jpnioltu8lqa1nd,xr67icguou77p1f
this is not clk 1.5 its 1.4
Sent from my HTC HD2 using XDA App
men this is no clk 1.5 this is clk is 1.4.1 ....
Is it possible to install & launch "touch" versions of 4Ext recovery? Classic version is too old for now and cant do as much as Touch.
Related
Thanks to cjward23 and friends for testing, 4EXT Recovery is now also available for the Desire Z / G2.
{
"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"
}
Quick note about themes:
Available themes as of Aug/28:
Themes by pravus_nephilim
Themes by Apaquette420
Themes by Whiskey103
Themes by Amresh
Themes by Apaquette420
Themes by CWhitney24
Themes by DaMyth
Themes by Blindndumb
To uninstall any "flashed theme" and to revert to your own custom settings you had before flashing, just use this Theme Uninstaller in recovery.
It will clear any theme you might have flashed and revert to your own custom settings you had before flashing that theme!
THANKS:
All credits and my deepest respect go to Koush for his extremely great code!
Without him 4EXT Recovery wouldn't have been possible!
Biggest thanks possible go to Sebastiaan15 for his brilliant ideas and who spent whole weeks testing my buggy code with his Desire
Without you I could never have made it!!!
So BIG THANKS to SEBASTIAAN15 and KOUSH for his hard work with CWMR !!!
Many credits to the Desire S community ( especially to loveboatcaptain - LBC Mod Android Development and Marylandcookie ) for testing, very nice ideas, feature suggestions and helping to get the code running on the Desire S!
Special big thanks to RAVENNA from android-hilfe.de board for hours of testing for the Desire!
BIG Thanks to Hussainmushahid who helped me a lot spending much of time with solving a bug I could not reproduce on my device.
And many thanks to all users who reported and helped to identify problems ( can't any longer list all of you here since the list has grown too large )!
Even more thanks to people who 've bought me some beer YOU ROCK!! ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
v2.2.6 RC4 Released: Oct/01
Rare Superuser problem when tar backups were enabled (disabled by default) was fixed.
Converting partitions between ext3 and ext4 without data loss now correctly calculates the space needed to successfully complete the operation
New option: check and optionally repair the file system on your sdcard (fat32)
Removed duplicate format cache option inside the format menu (wipe cache does the same)
When formatting fat32 it will now save your 4ext.prop settings and restore them afterwards
Changed partitioning of the sdcard to not use LBA mode for new fat32 partitions as requested by Ghiki
Added new size option (128mb) to the partitioning menu per request
Parted is no longer used to format fat32 in the partition menu
-> This solves a bug where sometimes the creation of the fat32 file system failed and produces better quality results
4EXT Recovery themes should now stay when formatting /system or flashing new roms
New option: format /sdcard fat32
New 4EXT Recovery Control API because I'm forced to drop "extendedcommand" (see App for the reason why)
enables file names and directories to include spaces for installations
calculates needed space to complete a full or advanced backup at the beginning of the backup.
This ensures that you are not left with a non working backup.
Size for recovery greatly reduced
New 4EXT Recovery Control Features
Please see www.4ext.net for more.
Fix permissions
Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
As an example, the following would be 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.
Features: 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
Themes:
Customize all colours used throughout recovery
Use your own icons, background images, progress bars.. more to come.
Assign different backgrounds to different menu categories (version >= 2.1.2)
Create a flashable zip for others to flash your theme.
Menus:
Most popular menu items rearranged
Format menu
Power Menu + option to reboot into bootloader
Less "No's" in confirmation dialogues
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
You don't need to reboot recovery if you transferred a file to show up in the install menu.
-> This bug affected only some users with either CWMR or previous versions of 4EXT.
Button backlights (Desire S, Desire HD and Incredible S only)
Download:
All downloads are now 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
It also notifies you when there are any new critical bugs found
Recovery images will be uploaded for download soon too, but they can also be acquired easily by using Updater or Control.
You can for example just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
4EXT Recovery Control
Free version: Recovery Updater
Fully featured version: 4EXT Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :
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 to "forcefully" restore it!
Calculate real values for the space needed to create a new full or advanced backup
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
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
Recovery theming
Uninstall and Install themes with live preview and the option to change their colours without the need to reboot into recovery.
Change all colours with live preview and a nice colour picker.
great have been waiting for this release
L-ViZ said:
great have been waiting for this release
Click to expand...
Click to collapse
Hehe thanks.
BTW: version 2.1.6 RC2 should be rock solid, just like a "final".
Except *maybe* for the optional tar backups feature (which can be switched on optionally).
It was tested very much, but as it is so new, noone knows if there are any "hidden" bugs with it that could possibly appear in the future
awesome, will give it a whirl!
So is this better than CWM 5?
Sent from my Desire Z running @ 2GHZ
being that cwm5 randomly freezes your phone, i don't see how it could be any worse. so far seems to have more features than 3.0.2.4 and i like the tar backup option, much quicker.
xT4Z1N4TRx said:
So is this better than CWM 5?
Sent from my Desire Z running @ 2GHZ
Click to expand...
Click to collapse
I wouldn't say better, it's different.
It has a lot more features and really detects your file systems correctly and preserves them on backup/restore.
CWMR5 is the first version that does that too, but at least in my case it failed.. when I restore a backup with it, all my partitions are formatted ext3 again (when they were ext4 as I created the backup)
But hey, I'm biased
Try it yourself and see what you like better
If you want, take a look what ppl say in the other 4ext threads:
http://forum.xda-developers.com/showthread.php?p=15504830
http://forum.xda-developers.com/showthread.php?p=15349806
http://forum.xda-developers.com/showthread.php?t=1104765
http://forum.xda-developers.com/showthread.php?t=1130004
well im sold, i defenetly have to this recovery, it has the feature iv been wating for, to disable md5 checksum
edit: dude i can i just say thank you, omfg this recovery is to much, battery info, parttion size info and rom name all in recovery? this is just amazing. i literately have no words man
siulmagic said:
well im sold, i defenetly have to this recovery, it has the feature iv been wating for, to disable md5 checksum
Click to expand...
Click to collapse
Hi thanks
But it doesn't have that feature to disable md5checksums.
However you can use Recovery Control to verify any of your backups for correct md5sums. If they don't match, you can als use it to "correct" them.
This is not recommended of course, since it indicates that there's a problem with that backup's data integrity. However sometimes ppl need exactly that backup badly.. so they can *try* to restore it anyway.
Disabling md5sum checks completely is a really bad idea.
I got one request about that from a guy with a phone that had a defect in handling sdcard memory. He tried numerous sdcards but still had that problem for a month.. any md5sumchecks fail for him.
He asked me to include a switch to disable them for him.
In the meanwhile he has sent his phone in for repair.
I might do that and add that switch, but it's not a very high priority since there is really much todo.
madmaxx82 said:
Hi thanks
But it doesn't have that feature to disable md5checksums.
However you can use Recovery Control to verify any of your backups for correct md5sums. If they don't match, you can als use it to "correct" them.
This is not recommended of course, since it indicates that there's a problem with that backup's data integrity. However sometimes ppl need exactly that backup badly.. so they can *try* to restore it anyway.
Disabling md5sum checks completely is a really bad idea.
I got one request about that from a guy with a phone that had a defect in handling sdcard memory. He tried numerous sdcards but still had that problem for a month.. any md5sumchecks fail for him.
He asked me to include a switch to disable them for him.
In the meanwhile he has sent his phone in for repair.
I might do that and add that switch, but it's not a very high priority since there is really much todo.
Click to expand...
Click to collapse
aw really, i was sure i read it on the description, regardless its still awesome
siulmagic said:
aw really, i was sure i read it on the description, regardless its still awesome
Click to expand...
Click to collapse
Thanks
May I ask why you want that feature?
If there is demand for that I will add it (although I'm really against that.).
THIS IS BRILLIANT
Sent from my Desire Z running @ 2GHZ
xT4Z1N4TRx said:
THIS IS BRILLIANT
Sent from my Desire Z running @ 2GHZ
Click to expand...
Click to collapse
Wow
Thank you very much
madmaxx82 said:
Thanks
May I ask why you want that feature?
If there is demand for that I will add it (although I'm really against that.).
Click to expand...
Click to collapse
well back in the day, when i had a motoroal cliq, we had amonra recovery, and so nanddroid on that recovery dint have md5checksums, and so we could rename our nanddroid backs and they would still flash, but i could be wrong, maybe it did have md5checksum im not sure, regardless i could flash any nadndroid, even if it dint have the same name it was made with. again this is the best recovery, we been waiting long enough, thank you
Haha, thought you guys would like this.
Sent from my HTC Desire S using Tapatalk
siulmagic said:
well back in the day, when i had a motoroal cliq, we had amonra recovery, and so nanddroid on that recovery dint have md5checksums, and so we could rename our nanddroid backs and they would still flash, but i could be wrong, maybe it did have md5checksum im not sure, regardless i could flash any nadndroid, even if it dint have the same name it was made with. again this is the best recovery, we been waiting long enough, thank you
Click to expand...
Click to collapse
Thanks again!
BTW: You can rename any of your backups and it will work
madmaxx82 said:
Thanks again!
BTW: You can rename any of your backups and it will work
Click to expand...
Click to collapse
ah awesome man, even better, i like this recovery more and more every minute.
cjward23 said:
Haha, thought you guys would like this.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
haha thanks for pushing me and for the testing
Firstly i want to thank you for this recovery, i have converted all my filesystem to ext4 but i have no idea what it does or can it improve speed of my device...
This is a pretty nice recovery! Thanks!
[Recovery] 4EXT 2.2.7 RC5 | STAY @EXT4 | Convert FS | MD5sum check | Rom > Backupname
Thanks to Jarheadflip for testing, 4EXT Recovery is now also available for the myTouch 4G
{
"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"
}
Quick note about themes:
Available themes as of Oct/17:
Themes by GuestK00388
Themes by Apaquette420
Themes by Whiskey103
Themes by Amresh
Themes by Apaquette420
Themes by CWhitney24
Themes by DaMyth
Themes by Blindndumb
To uninstall any "flashed theme" and to revert to your own custom settings you had before flashing, just use this Theme Uninstaller in recovery.
It will clear any theme you might have flashed and revert to your own custom settings you had before flashing that theme!
THANKS:
All credits and my deepest respect go to Koush for his extremely great code!
Without him 4EXT Recovery wouldn't have been possible!
Biggest thanks possible go to Sebastiaan15 for his brilliant ideas and who spent whole weeks testing my buggy code with his Desire
Without you I could never have made it!!!
So BIG THANKS to SEBASTIAAN15 and KOUSH for his hard work with CWMR !!!
Many credits to the Desire S community ( especially to loveboatcaptain - LBC Mod Android Development and Marylandcookie ) for testing, very nice ideas, feature suggestions and helping to get the code running on the Desire S!
Special big thanks to RAVENNA from android-hilfe.de board for hours of testing for the Desire!
BIG Thanks to Hussainmushahid who helped me a lot spending much of time with solving a bug I could not reproduce on my device.
And many thanks to all users who reported and helped to identify problems ( can't any longer list all of you here since the list has grown too large )!
Even more thanks to people who 've bought me some beer YOU ROCK!! ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
v2.2.6 RC4 Released: Oct/01
Rare Superuser problem when tar backups were enabled (disabled by default) was fixed.
Converting partitions between ext3 and ext4 without data loss now correctly calculates the space needed to successfully complete the operation
New option: check and optionally repair the file system on your sdcard (fat32)
Removed duplicate format cache option inside the format menu (wipe cache does the same)
When formatting fat32 it will now save your 4ext.prop settings and restore them afterwards
Changed partitioning of the sdcard to not use LBA mode for new fat32 partitions as requested by Ghiki
Added new size option (128mb) to the partitioning menu per request
Parted is no longer used to format fat32 in the partition menu
-> This solves a bug where sometimes the creation of the fat32 file system failed and produces better quality results
4EXT Recovery themes should now stay when formatting /system or flashing new roms
New option: format /sdcard fat32
New 4EXT Recovery Control API because I'm forced to drop "extendedcommand" (see App for the reason why)
enables file names and directories to include spaces for installations
calculates needed space to complete a full or advanced backup at the beginning of the backup.
This ensures that you are not left with a non working backup.
Size for recovery greatly reduced
New 4EXT Recovery Control Features
Please see www.4ext.net for more.
Fix permissions
Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
As an example, the following would be 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.
Features: 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
Themes:
Customize all colours used throughout recovery
Use your own icons, background images, progress bars.. more to come.
Assign different backgrounds to different menu categories (version >= 2.1.2)
Create a flashable zip for others to flash your theme.
Menus:
Most popular menu items rearranged
Format menu
Power Menu + option to reboot into bootloader
Less "No's" in confirmation dialogues
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
You don't need to reboot recovery if you transferred a file to show up in the install menu.
-> This bug affected only some users with either CWMR or previous versions of 4EXT.
Button backlights (Desire S, Desire HD and Incredible S only)
Download:
All downloads are now 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
It also notifies you when there are any new critical bugs found
Recovery images will be uploaded for download soon too, but they can also be acquired easily by using Updater or Control.
You can for example just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
4EXT Recovery Control
Free version: Recovery Updater
Fully featured version: 4EXT Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :
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 to "forcefully" restore it!
Calculate real values for the space needed to create a new full or advanced backup
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
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
Recovery theming
Uninstall and Install themes with live preview and the option to change their colours without the need to reboot into recovery.
Change all colours with live preview and a nice colour picker.
Works well, thanks for getting this going on the MT4G.
mikeyinid said:
Works well, thanks for getting this going on the MT4G.
Click to expand...
Click to collapse
Thanks for the feedback
Oh wow nice. Thanks! Finally happy to see an alternative to CWM.
Sent from my HTC Glacier using xda premium
Great to see this recovery make it to the glacier, huge props to madmaxx for porting it to everyone's devices and giving them an awesome recovery!
Sent from my LG-P999 using xda premium
Thank you all for the great feedback
d12unk13astard said:
Great to see this recovery make it to the glacier, huge props to madmaxx for porting it to everyone's devices and giving them an awesome recovery!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Hehe thanks, but 4EXT is very small.. only a handful of devices, and it won't grow big.
I will however try to support your device in the future
maddmaxx, im pretty sure i understand, but just to be sure. so i converted data to ext4, as it was only partition at ext3. if i flash a different rom it will stay ext4 correct? and can someone a little more familiar tell me if most if not all current release roms for mt4g will support ext4? tia
mikeyinid said:
maddmaxx, im pretty sure i understand, but just to be sure. so i converted data to ext4, as it was only partition at ext3. if i flash a different rom it will stay ext4 correct? and can someone a little more familiar tell me if most if not all current release roms for mt4g will support ext4? tia
Click to expand...
Click to collapse
4ext will always preserve your file systems unless you tell it to convert or format in a different one.
But it has no control over updater-scripts of roms you flash.
So when you flash a rom that formats system ext3, it will be done. And 4ext will preserve ext3 on /system from now on.. unless you convert or format ext4 et.c.
For data it should stay, because there shouldn't be a lot of roms that format your data partition that would be crazy
madmaxx82 said:
Thank you all for the great feedback
Hehe thanks, but 4EXT is very small.. only a handful of devices, and it won't grow big.
I will however try to support your device in the future
Click to expand...
Click to collapse
I'm just really glad to see it ported for the mt4g cuz even tho I don't own 1 anymore you still came thru and ported it as promised. If I find a bargain mt4g on craigslist I'm gonna go for it and definetly install this recovery. Does it have a terminal emulator included in options somewhere? I always liked partitioning my sdcard thru gparted in amon_RA recovery.
Sent from my LG-P999 using xda premium
d12unk13astard said:
I'm just really glad to see it ported for the mt4g cuz even tho I don't own 1 anymore you still came thru and ported it as promised. If I find a bargain mt4g on craigslist I'm gonna go for it and definetly install this recovery. Does it have a terminal emulator included in options somewhere? I always liked partitioning my sdcard thru gparted in amon_RA recovery.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
No, it doesn't have a terminal emulator, but it will correctly align all partitions you set up with it! Guaranteed! That's one of its features. There's also an alignment check.
works perfect even flashed one of the themes and it worked flawlessly 2thumbs up!!!!!!!!!!!!
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
lil question when i open the app on the top it says v 2.0.2 but i flashed the 2.2.1....or is that normal cuz when i go into recovery it shows me at 2.2.1
Ascarface23 said:
works perfect even flashed one of the themes and it worked flawlessly 2thumbs up!!!!!!!!!!!!
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
lil question when i open the app on the top it says v 2.0.2 but i flashed the 2.2.1....or is that normal cuz when i go into recovery it shows me at 2.2.1
Click to expand...
Click to collapse
Thnx
That's the App's version.
When you go inside the Update / Install menu where you can select different recovery versions to flash you will see your current version highlighted in yellowish orange and your version number of recovery in the title.
Everywhere else it's the current apk version
BTW: I would really recommend you to use the latest. 2.2.6 rc4.
There are too many advantages like checking for needed space to complete a conversion et.c.
madmaxx82 said:
Thnx
That's the App's version.
When you go inside the Update / Install menu where you can select different recovery versions to flash you will see your current version highlighted in yellowish orange and your version number of recovery in the title.
Everywhere else it's the current apk version
BTW: I would really recommend you to use the latest. 2.2.6 rc4.
There are too many advantages like checking for needed space to complete a conversion et.c.
Click to expand...
Click to collapse
yes i just noticed that thx for the fast reply and im updating to the 2.2.6 rc4 as we speak ...
ps- this **** is awesome!!!!!!!!!! flashing with out rebooting FTW.....
Is the recovery updater supposed to be in the market? I can only find the paid version.
I am able to direct download from the 4ext.net page and transfer to the sd card.
Nice to see this made it over here! good recovery! nice work!
Ascarface23 said:
yes i just noticed that thx for the fast reply and im updating to the 2.2.6 rc4 as we speak ...
ps- this **** is awesome!!!!!!!!!! flashing with out rebooting FTW.....
Click to expand...
Click to collapse
thanks
wolfepakt said:
Is the recovery updater supposed to be in the market? I can only find the paid version.
I am able to direct download from the 4ext.net page and transfer to the sd card.
Click to expand...
Click to collapse
No it's only available on the website.. but when there is an update it will notify you and download and trigger the install automatically if you allow it to.
Edit: I mean an update for the Updater app.. so you stay up to date even though it's not on the market.
thederekjay said:
Nice to see this made it over here! good recovery! nice work!
Click to expand...
Click to collapse
Thank ya
Sent from my HTC Glacier using XDA Premium App
Ascarface23 said:
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
hehe nice
I love her
My favourite theme.
Did you change the colours by editing 4ext.prop or by using the app?
Edit: stupid me.. that picture is from inside the app, right?
That's why you can't read the text that good.. inside recovery the background image is a tiny bit less "obtrusive"
madmaxx82 said:
hehe nice
I love her
My favourite theme.
Did you change the colours by editing 4ext.prop or by using the app?
Click to expand...
Click to collapse
i used the app to do everything
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)
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
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.
If you somehow lost those files, there's a direct download for a version you can flash via fastboot.
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.
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, SYRAKUS, 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 :
PTR_HAMILTON, SEBASTIAAN15, THEUNTOUCHABLE, BMONSTER, ANDREIGHERGHE, PRESTON74, MADKAI, YASIR, PLAYPETEPP
IPERZAMPEM0, THESHAWTY, JBBANDOS, 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:
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.
This a great Recovery!! I've been wanting a touch recovery for a long time. So glad to see this come to life, and get a chance to test it out. It's really nice, and so much easier to use.
Thanks to Madmaxx for bringing this to us!!! Try it, you'll like it
Great work!! So nice to have a touch recovery! Many thanks Madmaxx!!!
Thank you very much
Need to get some sleep now, but will answer any questions/posts tomorrow!
I absolutely love this recovery I bought the paid version tonight and it has been well worth it!! Thx for this
Sent from my ADR6350 using Tapatalk
Def going to try this out tomorrow, need sleep otherwise I'd play with it now
Sent from my ADR6350 using Tapatalk
I can't wait to try this. This would be amazing on my kindle fire
Sent from my Incredible 2 using XDA App
Having spent the past day now using this recovery, I wanted to give a follow up.
I've used this now to do a couple of backups, one restore, downloaded a rom through rom manager (which works with this recovery just fine) flashed a couple of zips from the sd card, system format.... First impression. The UI is amazing. It's so nice to not have to use the volume and power button for making selections. It's fast. Backing up a Sense 3.5 rom (huge file) took roughly 3-4 minutes less then previous recoveries. It's very user friendly and very easy to use. it looks great.
Very well done. Try it you may like it!
Installed. I wiped cache and dalvik, fixed permissions, mounted. Feels fine going through all the menus.
However, the time for that dropdown menu to go down is way too slow. I pressed "Wipe dalvik" and then it takes like a second or so for the menu to roll down from the top just to ask me to confirm, kind of annoying. The same happens when I cancel it. I can't even use the back button, I still have to wait for the menu to roll back up before I can do anything.
PacerguyDon said:
Try it you may like it!
Click to expand...
Click to collapse
LOL sounds like a quote from my son's favorite cartoon
Sent from my ADR6350 using Tapatalk
PharmCAT said:
Installed. I wiped cache and dalvik, fixed permissions, mounted. Feels fine going through all the menus.
However, the time for that dropdown menu to go down is way too slow. I pressed "Wipe dalvik" and then it takes like a second or so for the menu to roll down from the top just to ask me to confirm, kind of annoying. The same happens when I cancel it. I can't even use the back button, I still have to wait for the menu to roll back up before I can do anything.
Click to expand...
Click to collapse
+1, this is absolutely amazing!
More only gripe is how long that menu does take!
but can certainly live with it for this baby..
andybones said:
+1, this is absolutely amazing!
More only gripe is how long that menu does take!
but can certainly live with it for this baby..
Click to expand...
Click to collapse
I feel like between that and possibly calibrating touch better for more responsiveness. I felt like it wasn't super accurate and took a few times to select install from zip. Not complaining, and I know this is only a first release, and still needs work, but that's the only thing I've noticed.
Sent from my Incredible 2 HD using "Iced Frosting" Tapatalk
Easy and fun to use!!
Sent from my Incredible 2 using xda premium
This is incredibly slick. Downloaded from the app and let it install it. Incredibly cool to have touch screen in recovery.
awsome work! thank you!
Sent from my Incredible 2 using XDA Premium App
I haven't noticed any lag in the menus I've used but I haven't done anything but backup, restore and install from sd card. All were very responsive. Touchscreen support for recovery is long overdue. I can't thank you enough, MadMaxx. You're the bomb. I pity the fools who have unsupported devices *in my best Mr. T voice*
slacka-vt said:
I haven't noticed any lag in the menus I've used but I haven't done anything but backup, restore and install from sd card. All were very responsive. Touchscreen support for recovery is long overdue. I can't thank you enough, MadMaxx. You're the bomb. I pity the fools who have unsupported devices *in my best Mr. T voice*
Click to expand...
Click to collapse
I noticed he put out an update already, so I'm assuming he fixed it.
Latest update really helped out on the lag. It's pretty smooth now and very responsive
IRC on freenode: #sk8erwitskil
NEW: I have created a script to easily update to the latest version of my recovery.
- Download this file ----> updater.sh (updated to fix typo)
- Put it on your sdcard
- open adb and type:
Code:
su
sh /mnt/sdcard/updater.sh skyrocket
- it will reboot you into recovery
- starting in v14.2.1 it will automatically start installing and reboot when its done
Note: If your sdcard is not mounted on /mnt/sdcard then open the script and change the line that says path=/mnt/sdcard/sk8sUpdater to match your mount point. i.e. ICS users may have to change it to say path=/mnt/emmc/sk8sUpdater
Click to expand...
Click to collapse
I have ported touch recovery to Clockworkmod 6. I will be making updates to this just like my other touch recovery. I have added a few menu items and tweaks to make it like my CWM5 recovery.
Looking through the cwm code more in depth i have noticed MANY flaws with the code for new(er) phones that use /emmc instead of /sdcard as the main storage. i have now fixed those flaws in v9+.
Here is a video of how it works: --------> YOUTUBE LINK
Flashable zip:
cwm6027touch_v14.4.6_hercules.zip: ---------> DOWNLOAD
Click to expand...
Click to collapse
Thanks to :
gweedo767 (for creating the original touch recovery)
koush (for creating CWM)
PhilZ (for his amazing improvements and help with applying universal touch code) BIG THANKS!
PREVIOUS VERSIONS:
Code:
v1:
[CODE]initial release
v2:
Code:
- updated to latest version of clockworkmod
- add reboot download option
- add reboot recovery option
- add power off option
- change font size
- add various internal/external sdcard options from cwm 5.5.0.4 touch recovery
- change order of internal/external sdcard so internal comes first on backup/restore/install
v3:
Code:
- add support for phones that sdcard mounts as external_sd
- fix the line below the menu to actually be below the menu
- clean up the "andy the android" picture. (if you make a backup you will see that the picture in the background has been poorly edited. there are bits of black spots around him)
- JellyBean Background
v4:
Code:
- fixed missing slash that was not allowing installs from external sdcard
v5:
Code:
- update to latest version of CWM 6.0.0.8
v6:
Code:
- updated to latest version of CWM 6.0.0.9
- added ability to delete nandroids from recovery (in backup and restore menu)
- changed order of internal/external so external comes first
- fix timestamp creation on backups
v7:
Code:
- updated to latest version of CWM 6.0.1.0
- fixed bug that would not allow backup of /system
v8:
Code:
- update to latest version of CWM 6.0.1.1
- allow customization of backup format (dedupe/tar)
- use minizip tool instead of e2fsck, etc.
- more....
v9:
Code:
- update to latest version CWM 6.0.1.2
- fixed bug where backing up to external wouldnt backup /emmc/.android_secure
- ADDED DUAL LUNFILE SUPPORT! (thanks to topprospect for this!)
-- what this does is when you mount USB storage you
will see both of your sdcards mount at the same time
- various /emmc fixes (recovery now looks for all clockworkmod "." files in /emmc instead of /sdcard)
- this is useful for people who dont use an external sdcard at all
v10:
Code:
- grabbed latest commits to official CWM 6
- added new extras menu (look in 2nd post for info)
- some other stuff i dont remember
v11:
Code:
- fixed hide nandroid progress bug (it now works)
- added sk8's fix permissions option (logging is disabled so it runs faster and it also clears stale data directories)
- fixed bug where normal fix permissions wouldnt create a log to correct location
- cleaned up some syntax
v12:
Code:
- added darkside wipe/super wipe built in
- added aroma file manager built in
- added ability to backup/restore the /efs partition
- cleaned up oneconfirm/hidenandroidprogess features to be one menu item
- more......
v12.5:
Code:
- fixed bug where darkside cache scripts wouldnt work
- added option to create a custom zip (read 2nd post)
v13:
Code:
- report log gets copied to /emmc instead of /sdcard
- add support for roms without busybox (stock roms) to create a custom rom zip
- add support for openrecoveryscript (read [URL="http://forum.xda-developers.com/showpost.php?p=31093552&postcount=344"]THIS[/URL])
- add support to choose a custom created openrecoveryscript
- use goo-manager to flash roms and create openrecoveryscripts
- now detects where android_secure is automatically
- fix ors-mount.sh to work even if 'sdcard' is in the path
- misc code cleanups.....
v13.1
Code:
- bug fixes
- android_secure fixes
v13.2
Code:
- that pesky android_secure - bugfixes for restoring android_secure
v13.3
Code:
- updated to latest 6.0.1.4
- some bugfixes
- added option to select where android_secure lives (hopefully this is the last time. i promise)
v13.4:
Code:
- updated aroma file manager to latest version
v13.5:
Code:
- add initial support for whole-device encryption (thanks topprospect)
v14:
Code:
- updated to latest CWM 6.0.1.5
- fixed some mtdutils issues
- added a bootanimation changer
v14.1:
Code:
- not released
v14.2:
Code:
- added bootanimation change selection from external sdcard
- added newest aroma filemanager w/ console support (you can use terminal in recovery)
- updated to latest changes of official CWM
- added support for Android 4.2
- zip file now installs updater.sh to your internal sdcard
- updated updater.sh to fix typo
v14.2.1:
Code:
- openrecoveryscript automatically runs if script is found in /cache/recovery/
- this is good for using my updater.sh or goomanager
v14.3
Code:
- skipping this number to keep in line with my other devices
v14.3.1
Code:
- lots and lots of under the hood improvements
- re-wrote OpenRecoveryScript and efs backup/restore code
- these work alot better now (thanks so much to PhilZ for his amazing help)
- add option to backup/restore boot.img from sdcard
- now using latest stable kernel
- completely re-wrote the touch code for some improvements
- now to select you tap anywhere on the screen
- fixed some typos
- made my source code universally compatible with all phones using ICS or greater
- compiling in jellybean base recovery code now
Code:
v14.4
- fixed soft keys (virtual keys on bottom) (credit to PhilZ for this)
- reverted back to swipe to select
- tweaked some features in the extras menu
Code:
v14.4.1
- messed up on the mount points so i fixed them now
- added some buffer to fix ability to accidentally select wrong item
Code:
v14.4.5
- skipped some versions because they were made for other phones
- re-wrote the create custom backup feature to be universal now with all phones/roms (thanks to PhilZ for the help)
- added new settings menu
- add ability to change timezone
- added /preload support [B](must go and enable it in misc nandroid settings)[/B]
- add rom name to nandroid names
- more i just cant remember now....
[/CODE]
Current Version:
v14.4.6
- added exFAT support
- some under the hood optimizations
Click to expand...
Click to collapse
Major update to how touch works now:
UP - swipe finger up on screen
DOWN - swipe finger down on screen
SELECT - swipe finger from left to right
BACK - swipe from right to left
SOURCE: https://github.com/sk8erwitskil/touch_recovery_cm10
This is what the new dedupe format does. This is a direct quote from the original creator of clockworkmod:
Code:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard(or emmc)/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Whats in the extras menu?
- change bootanimation (this lets you select a bootanimation form your internal sdcard. it backs up your current bootanimation to /{internal sdcard}/clockworkmod/ba_backup/. it only backs up the original bootanimation so if you keep changing your bootanimation you will still only have your original one in ba_backup.)
- enable/disable one confirm (this makes it so you only have to scroll through one confirm selection when installing something instead of having to go through 10 of them to click yes)
- hide/show backup & restore progress (this makes it so the progress bar when you backup/restore doesnt show up and makes backups/restores a bit faster since it doesnt have to show you the progress and files its backing up)
- select android_secure on internal/external (use this to select where you have .android_secure. default is internal, so if you have it on external make sure to choose this once to set it up)
- aroma file manager (file explorer)
- create custom zip (this will create a custom rom from the currently installed files you have on your phone. it takes your /system partition and /boot partition and makes them into a zip file ready to be flashed. the end product will be in clockworkmod/custom_rom/. this has recently been fixed to work on all phones/roms
- choose custom openrecoveryscript (read THIS)
- recovery info (shows the version of recovery and the build date)
- Special Backup & Restore (backup and restore your kernel/boot and /misc partitions)
- Misc Nandroid Settings (change time zone, turn preload support on/off (default is off), enable md5 checking)
hellz yes!!!
Sent from my SGH-T989 using xda premium
Thank you and welcome back brother!
Thanks buddy! will report if I come across any bugs
Working great and looks beautiful do u recommend to do the hide the progress option or to not?
casonswag said:
Working great and looks beautiful do u recommend to do the hide the progress option or to not?
Click to expand...
Click to collapse
its up to you. if you want to know how far along the progress is then show it. but itll take a little bit longer to backup. or if you dont care about how far along you are and just want it to be done in the fastest time possible then hide it.
when i go into cwm it says read only file system...?...how do i fix that...cause my system is monted and my sd card is mounted...pleasse help...thanks in advance...
ooo this is sweet , thanx, now i can delet the other thread and leave
only the non-touch version!
if your .android_secure folder lives on your external sdcard then download this file -----------> [url said:
http://d-h.st/PdV[/url]
Click to expand...
Click to collapse
I do see that folder in my external, micro sd right?? So, i just need this file only?? Its the recorvery itself..??
Sent from my SGH-T989
phordych05 said:
when i go into cwm it says read only file system...?...how do i fix that...cause my system is monted and my sd card is mounted...pleasse help...thanks in advance...
Click to expand...
Click to collapse
can you please explain more? what are you trying to do when it says read only file system? are you trying to adb something to your system partition? you need to remount it as rw before you can put something there. thats always the case.
noodles2224 said:
I do see that folder in my external, micro sd right?? So, i just need this file only?? Its the recorvery itself..??
Sent from my SGH-T989
Click to expand...
Click to collapse
yes if you have .android_secure in /sdcard then download the secondary one
I hate to be "that guy" who asks this question, but...
Will this play nice with installing the various ROM's for this phone? Although I have never personally had a problem with installing any ROM's on the various recoveries, people always report problems with certain combinations.
I downloaded this last night and used it right away... This takes waaaay too long to do a backup. Close to 15 mins... too long for me
TWRP all day, everyday. Why bother with prehistoric recoveries.
tikay00 said:
TWRP all day, everyday. Why bother with prehistoric recoveries.
Click to expand...
Click to collapse
Dude why are you going to every thread Trolling making nonsense comments thats not needed ?
sk8erwitskil said:
can you please explain more? what are you trying to do when it says read only file system? are you trying to adb something to your system partition? you need to remount it as rw before you can put something there. thats always the case.
yes if you have .android_secure in /sdcard then download the secondary one
Click to expand...
Click to collapse
Well i have it in /sdcard/external_sd not just /sdcard. Still download the second one right? Sorry but with this samsung internal and external, sometimes just saying sdcard is a little confusing..
Sent from my SGH-T989
scribbles92 said:
I downloaded this last night and used it right away... This takes waaaay too long to do a backup. Close to 15 mins... too long for me
Click to expand...
Click to collapse
thats already been talked about. the first backup takes longer because of the dedupe format. incremental backups are much quicker. do a google search for koush dedupe clockworkmod 6 and youll see. i dont have the energy to explain it again.
noodles2224 said:
Well i have it in /sdcard/external_sd not just /sdcard. Still download the second one right? Sorry but with this samsung internal and external, sometimes just saying sdcard is a little confusing..
Sent from my SGH-T989
Click to expand...
Click to collapse
correct. because /sdcard/external_sd is how your OS mounts it. but in recovery it will be mounted as /sdcard. for samsung devices the stock way to mount storage is: internal = /emmc, external = /sdcard. depending on what rom you use though the developer of that rom may change the way that the OS mounts it because he prefers a different way. but in recovery i set it to be internal = /emmc, external = /sdcard
tikay00 said:
TWRP all day, everyday. Why bother with prehistoric recoveries.
Click to expand...
Click to collapse
cool story, bro
sk8erwitskil said:
thats already been talked about. the first backup takes longer because of the dedupe format. incremental backups are much quicker. do a google search for koush dedupe clockworkmod 6 and youll see. i dont have the energy to explain it again.
Click to expand...
Click to collapse
Oh ok, thanks sk8er... I was looking for another recovery and hadn't read up on it so... maybe I will give this another shot. (I'm actually coming from your other recovery -CWMR 5.5.0.4)
sk8erwitskil said:
thats already been talked about. the first backup takes longer because of the dedupe format. incremental backups are much quicker. do a google search for koush dedupe clockworkmod 6 and youll see. i dont have the energy to explain it again.
correct. because /sdcard/external_sd is how your OS mounts it. but in recovery it will be mounted as /sdcard. for samsung devices the stock way to mount storage is: internal = /emmc, external = /sdcard. depending on what rom you use though the developer of that rom may change the way that the OS mounts it because he prefers a different way. but in recovery i set it to be internal = /emmc, external = /sdcard
Click to expand...
Click to collapse
I hate to ask this but how do I know if it's located there or not?
Sent from my SAMSUNG-SGH-T989 using xda premium
This thread should clarify the methods you can use to enable dual-boot functionality along with common problems and solutions. Hopefully, the list of questions should help. The initial author of this important thread was RichMD. He has kindly asked me to maintain it further instead of him, as he is too busy for that in the moment. I have accepted it and I do it as of February, 2014. Although I'm an active user of dual boot since I own my N7100, I don't consider myself to be a guru for this and I will highly appreciate any cooperative posts and I will try to add the important information and frequently update this OP.
IMPORTANT: particulary new users, please read especially careful here and mind, as the features of Devil Dual Boot Recovery have been strongly changed between the updates! I have kept first two parts of this OP the way RichMD has written them. So all the information are regarding pre-F2FS recovery versions (until v6.0.4.4). My screenshots also show only UI of the 6.0.4.4 version. From part 3 onwards, th einformation are regarding entirely newer recovery and kernel versions with F2FS support.
LIST OF CONTENTS:
About Devil dual boot recovery
Part 1: FAQs: dual-boot general
Part 2: GUIDE: setup dual-boot
Part 3: FAQs: benefits of F2FS
Part 4: GUIDE: migrate from ext4 to F2FS
Part 5: bootloader info & download links
Click to expand...
Click to collapse
About Devil Dual Boot Recovery
A luxory version of CWM based recovery with touch UI
Each choice must be clicked twice by touch navigation (to avoid accidental touch)
Navigation can be done by swiping with finger up or down beyond the menu contents
The navigation bar on the bottom works identic like with PhilZ recovery
SCREENSHOTS: (v6.0.4.4, the last pre-F2FS version)
{
"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"
}
Click to expand...
Click to collapse
1: FAQs / dual-boot general
Q.) Can I run all 4.3 and 4.4 AOSP and Touchwiz based ROMs with devil2 dual-boot kernel?
A.) All AOSP ROMs between 4.3 and 4.4.2 will work, but ATM only 4.3 TW based ROMs will boot, 4.4 isn't yet supported.
Q.) Why do I keep getting "Something went wrong..." when trying to install a ROM.
A.) Some people have had this problem when trying to install from the external SD card and the error does not happen after the zip is moved to the SD card. There are additional reasons for that error that I listed below.
Q.) I am having ... problem with the secondary ROM (Play Store FC, no SD card access, no MTP, it fails to install and affects the primary ROM, etc)
A.) 4.2 ROMs do not typically install properly to the secondary partition currently. Additionally, 4.1 roms have a problem with MTP frequently or AROMA roms will fail the ROM to secondary install-script-modification step . Instead, install your desired ROM to primary, boot with the kernel included in the ROM and ensure everything works including MTP. Then flash the dual-boot kernel. Then back it up and wipe the secondary partition. Then restore your backup to the secondary.
Note: DerTeufel has fixed the problem of internal SD card access for 4.2 ROMs for N-7105 (LTE) based phones but N-7100 phones still have the problem. It is being worked on.
Workaround if you can't access the phone via USB
You can load and use easy UMS one time. You will have access to the external SD. Simply reboot and then set the app back to the default MTP mode and both should be accessible. You don't need the app after that. - (https://play.google.com/store/apps/details?id=com.mohammadag.samsungusbmassstorageenabler) and you shouldn't need it anymore.
Q.) Can I revert back to a configuration without dual-boot and how do you do it?
A.) Yes. Use a file manager with root access on the primary ROM to delete the /data/media/.secondrom folder which contains the 1.5GB file and the data folder. Flash another recovery (CWM or TWRP) and flash as you normally would.
Q.) I can't seem to get my nandroid to restore to the secondary partition. What am I doing wrong?
A.) One possible problem is that the secondary /system partition is sized at 1.5GB (recent F2FS kernel version enlarged secondaryFS to 1.9GB). If your nandroid backup has over this amount in /system then it won't work. One possible solution is if you use Titanium Backup (or similar backup program) to do a full backup of apps AND system info. Although it is often written not to restore system info, it is OK if it to the same exact ROM and version. You could then factory reset to wipe it clean, do a nandroid backup and then restore that to secondary. Then install TB and restore selectively only the apps you want. I would probably suggest restoring "missing apps + all system data" but then deselect most of the apps that aren't really necessary. Once that is complete and the configuration is working, you could selectively restore other missing apps and data on a priority basis until you start running low on /system space. TB will show that at the bottom of the initial screen.
Q.) I tried a fresh install to the secondary partition and it completed successfully but now when I boot the primary ROM, I have what I meant to install to the secondary partition. What's wrong?
A.) This will happen if you choose "ZIP to secondary rather than ROM to secondary because of what I listed below in initial setup. Choosing ROM to secondary will cause the installation script to be modified to install to the secondary partition or it will error out with "Something went wrong". Zips installation scripts do not need to be modified because they will reference recovery.fstab which has been modified to support the secondary partition (when you select enable secondary FS.
Q.) Why doesn't vibration work after flashing this kernel?
A.) The default setting for vibration in the kernel is 2%. Use the DevilTools app referenced in DerTeufel's OP and change "Set Vibration Intensity" under the Tweak group.
Q.) Does exFat work?
A.) The kernel supports it but the recovery has not yet been modified to support it.
Click to expand...
Click to collapse
2: GUIDE / how to setup dual-boot
Initial Setup
1) Have you flashed the dual-boot (aka DB ) kernel yet? If yes, go to step 3
2) Flash the DB kernel: Go to the DB OP here and flash the version for your model type - http://forum.xda-developers.com/showpost.php?p=40410021&postcount=1 N7100 is for non-LTE models and t0lte is LTE enabled (AT&T, Verizon, etc). The zip will NOT list recovery in the name...
3) Have you flashed the DB recovery? If yes, go to step 5
4) Flash the DB Recovery: Navigate to DB OP listed above and flash the version for your model type (as in step 2 above)
5) Have you created the secondary system partition? If yes, go to step 7
6) Create the secondary partition image: Boot into the DB recovery and select Dual Boot Menu > enable mounting secondary and then select create secondary system image (also under Dual Boot Menu". This will take a couple of minutes. This only has to be done once.
7) Ready to flash primary or secondary ROMs: Note: It is probably a good idea to get in the habit of always selecting the FS (primary or secondary) that you want to affect just to ensure you don't wipe the wrong one, etc. Select Dual boot menu > enable mounting of (pri or sec.)... It stays selected until you boot into recovery and change it. You will see recovery flash (reload) with the appropriate FS selected. Obviously, don't select it again - logic loop...
8 ) You at least need to follow standard ROM installation instructions at this point such as wipe data, etc (as appropriate). Wipe Data/Factory Reset will leave the ROM (typical) and the 2nd option (wipe data-cache-system-preload) will wipe out the ROM completely so you can start "clean". Only the selected FS is modified so the other ROM is not affected. All apps and data are separate for each ROM. SD card storage is common so keep that in mind for an app that exists in both ROMs.
9) Installing to the primary partition does not need any special instructions. You should have already selected "enable primary". Select "Install zip" > Choose zip from sdcard or external > ROM to Primary FS. The difference between the "ROM" and "Zip" selections is that zips do not typically explicitly access the file systems - they use references in recovery.fstab which DerTeufel modified to point to the appropriate locations depending on your selection (primary or secondary). Yes, choosing install zip might work for installing a ROM to primary but NOT to secondary. Also, the intention is to avoid confusion.
10) Installing to the secondary partition MIGHT be more problematic since the zip has to be modified first to replace FS references with the secondary locations. When you select this option, it can take a couple of minutes since it is changing the references and then re-zipping to a modified file on the SD card. Note: The original will be gone (at least if it was originally on the SD rather than the external SD) so make a copy, etc before proceeding if you want it to be available for standard/primary flashing in the future. The modified file will always install to the secondary partition after being modified. Note: Complicated install scripts (such as AROMA) will likely fail. If you want an AROMA based installation then the safest way is to install it to the primary partition, ensure it is working, make a backup and then restore the backup to the secondary partition (using the DB recovery of course). Backup/restore will be detailed below.
11) Recovery does not automatically mount /system, and /data so ensure /cache and these are already mounted before running a zip that will need to modify them
12) Avoiding MTP issues: After flashing a ROM, recovery prompts you to install the DB kernel again. Otherwise, the kernel installed with your ROM will not be able to boot the secondary ROM. However, if you do flash the DB kernel right away (for now at least) you may have a problem with MTP (access from a PC over USB ). If you boot the new ROM (with the ROM's kernel which will work for PRIMARY) then MTP should be working. You can then flash the DB kernel after rebooting to recovery and MTP will still work (afaik). Similar to the AROMA note above, you might want to install a ROM to primary first even if you want it in the secondary partition. The install script will not need to be modified and a normal kernel will boot the ROM so MTP will work. Then you can flash the DB kernel, make a backup and restore to the secondary. Hopefully, this is only temporary but at least this workaround exists.
13) Ready to flash zips to primary or secondary ROMs Flashing gapps, etc. simply requires that the correct FS is enabled, /system and /data (as necessary) are mounted and select your target under "Install zip" > "Choose zip from..." > Zip to (primary or secondary).
Kashortiexda has created another installation process documented in post #13 > http://forum.xda-developers.com/showpost.php?p=41992232&postcount=13
Click to expand...
Click to collapse
3: FAQs about F2FS / benefits of F2FS and dual-boot in f2fs
Q.) What is F2FS?
A.) "The Flash Friendly File System" created by Kim Jaegeuk (Samsung) and released in February 2013. Read more about F2FS here
Q.) Recently, DerTeufel1980 has updated his devil2 dual-boot kernel and recovery and merged F2FS support. What is the benefit of F2FS?
A.) if the internal sdcard is formatted to F2FS, the system is supposed to be up to 2 times faster than on ext4 (default formatting).
Q.) After update to the newest Devil DB Recovery with F2FS support I had problems by installing ROM to the Secondary FS / my nandroid backup was restored with errors
A.) The newest recovery has enlarged Secondary FS image to 1.9GB (earlier was 1.5GB). This can be cause for many errors. So be sure to create a nandroid backup of your Secondary ROM before you erase /secondrom partition from data/media and to create it again with the new recovery. This is very important to do after the recovery update.
Q.) What should I do to be able to use the benefits of F2FS on my device?
A.) Five steps! First: flash new DB recovery & new DB kernel with F2FS support. Second: create nandroid backup(s) of your ROM(s). Third: move all your data from internal sdcard and save them elswhere, as the formatting to F2FS will erase your entire internal sdcard. Fourth: format in recovery mode all the (internal) sdcard partitions to F2FS one by one. Fifth: restore your ROM(s) and data.
Q.) Can I revert from F2FS back to ext4?
A.) Yes. You can use either of Devil DB Recovery versions to revert back to ext4 (in the new version you will can choose between F2FS or ext4) or you can simply flash any other recivery that doesn't support F2FS and format with it all the partitions. It will format all back to ext4 (you will have to repeat the procedure like described in the question right before).
Q.) After return to ext4 I couldn't format /cache back to ext4
A.) Formatting back to ext4 seems to not work reliably with the newest Devil Touch recovery for N7100. If it is only /cache, it doesn't matter as everything seems to work normally. You can use any other non-F2FS recovery (like TWRP 2.6.3.x or PhilZ touch 6.12.8 to format cache back to ext4)
Q.) Can I with F2FS update my ROM(s) normally with any nightly build?
A.) No, it is not recommended, as the nightlies will ATM reformat some of the partitions back to ext4. Well, yes, in fact you can update, but it is quite complicated way around, therefore, F2FS is more practical for those who want to stick longer time with their ROMs and use benefits of very fast performance of their device on F2FS.
Q.) I've got error message after migration to F2FS when I tried to restore my nandroid backup
A.) This happens occasionally mostly there is a "can't mount /data" error message. Don't worry about that, simply reboot recovery, format again all to F2FS and restore your nandroid backup then.
Q.) After migration to F2FS, I can't reach my Secondary FS partition under "dual boot menu", why?
A.) If the recovery displays "Only with Devil Kernel available" (altough it is flashed already), simply reboot into the Primary FS and reboot into the recovery right after that. Then you will be able to create again the Secondary FS partition and restore your nandroid backup.
It has been reported at least by one user that System, Data, EFS, & Storage had to be remounted manually every time for successful boot up by switching from Primary to Secondary FS and vice versa.
DerTeufel1980's features description just after updating kernel and recovery for t0lte to F2FS (N7100 update was released about one week later):
What's new:
kernel:
added new f2fs filesystem support (supposed to be up to 2 times faster than ext4)
introduce the BFQ-v6r2 I/O sched for 3.3
block, bfq: add Early Queue Merge (EQM) to BFQ-v6r2 for 3.3.0
enable CGROUP_BFQIO by default
backport SLUB from Linux 3.3 (thanks to faux123)
afsync: replace fput() with fput_light() accordingly
cfg80211: Fix memory leak
mm: implement WasActive page flag (for improving cleancache)
fix triangle away
usb: fix 'adb root'
recovery:
completed the rework of recovery ui (primary and secondary rom need to be selected once in dualboot menu) if you can't access dualboot menu, please boot primary or secondary rom with the new kernel once
resized secondary system image to 1.9 gb
possibility to flash roms to secondary without modifying the zip (you HAVE TO CHOOSE ROM). if this fails, select use workaround (this is the old method) next time
added support to format and mount f2fs formated partitions (/system, /data and /cache)
if you format data to f2fs (this gives the maximum performance, you have to select primary rom in dualboot menu, then the option will be in mounts and storage: format /data, /data/media and secondary (please backup before, this wipes your internal sdcard as well)
You only can format data to f2fs, when you select to manage primary Filesystem, because it formats the entire partition, including your internal sd card (which also includes your second rom partitions). Formatting data gives you a complete clean data partition, and you need to backup/restore data, and sdcard (if you backup the sdcard with custom nandroid to external sdcard, you can restore it afterwards, which also restores the secondary rom).
The kernel 2.4.5b for t0lte fixes boot on Omnirom, as well as fixes Selinux on Samsung rom. By default Selinux is set to "enforcing" now, for Samsung as well as for AOSP roms.
If one wants to completely disable selinux, you need to create the file: "/.secondrom/.selinux_disable" (if you are currently booted into secondrom, otherwirse the path would be "/data/.selinux_disable" (both is the same file, and creating it, disables selinux for both roms, once rebooted). selinux stays disabled until the file gets deleted again, and the device rebooted.
On some Sammy roms FC may occur with enforced selinux with the warning: "smartcard service has stopped". Except the fact that only few may know what this service does, usually nothing bad will happen (this message appears once once after boot up)
WARNING: After "fixing" booting on Omnirom, DerTeufel1980 has warned that f2fs only seems to be working properly on CM11 based roms. Samsung ROMs are at least working with selinux disabled, but Omni ROM breaks baseband if selinux disabled!!
Click to expand...
Click to collapse
4: GUIDE / ext4 to F2FS migration
New Devil Touch-DB-recovery v6.0.4.5 has some new features:
Instead of double amount of options (for primary FS or secondary FS, respectively) now there is "dual boot menu" where we can choos which FS to manage
Menu text of the secondary FS is displayed now in red color
The size of secondary FS partition is now 1.9GB so even big ROMs can be installed as secondary FS
SCREENSHOT: (new Devil Touch v6.0.4.5 with f2fs support)
As described above under F2FS FAQ, we will migrate to F2FS in five steps:
Step 1/5: flash Devil Touch v6.0.4.5 recovery & kernel with F2FS support for your device (check the download links on the bottom of this post)
flash Devil Recovery with F2FS support for your device (download links are on the bottom of this post)
reboot recovery (under "power options" on the bottom of the main menu)
for single-boot: flash Devil2-F2FS-kernel.zip to your ROM (2.4.5b for t0lte and Verizon / 2.4.6 for N7100)
for dual-boot: if you are already dual-boot user, now flash Devil2-F2FS-kernel.zip to both your ROMs: primary FS and secondary FS
Step 2/5: create now nandroid backup(s) of both your ROM(s):
under "Backup and Restore" choose "Custom Backup and Restore"
in this sub-menu, choose "Custom Backup to /sdcard1" or optionally: "Custom Backup Job"
check for backup only: /system and /data and then >>Start Custom Backup Job<<
as the final step choose "Backup to /storage/sdcard1" option (your external micro SD card)
repeat the same procedure for your second ROM
OPTIONALLY: under this step you can also create a full nandroid backups, but just make sure that you then after migration to F2FS restore only /system and /data in "Custom Restore Job"!
Step 3/5: move all your data from internal sdcard and save them elsewhere, as the formatting to F2FS will erase your entire internal SDcard!
use either external SD card, or your PC as storage, as the entire internal phone memory will be erased in the following step.
mind that this step can take some time, regarding size of the data that has to be copied (20-30 min)
Step 4/5: reboot into the recovery to fs=1 (primary) and format under "Mounts and Storage" following partitions to F2FS:
format /system
format /data, /sdcard and secondrom (this step will destroy the /.secondrom partition)
Step 5/5: restore your ROM(s) and data.
reboot recovery
restore your primary FS
flash Devil-DB kernel
reboot to system and back to recovery
create secondary FS partition
restore your nandroid backup to secondary FS (if you have used "Custom Backup Job")
flash Devil-DB kernel again
OPTIONALLY: if you have made full nandroid backups under step 2/5 now at this point don't miss that you should restore only /system and /data with "Custom Restore Job" option!
Finished! Enjoy F2FS
reverting from F2FS back to ext4
Repeat whole the procedure, just choose under formatting always "ext4" instead of "F2FS"
Click to expand...
Click to collapse
5: download links / troubleshooting
DOWNLOAD LINKS:
Latest versions of the kernel and recovery without F2FS support for Note 2:
Devil2 dual-boot kernel MAIN THREAD
Note 2 kernel and recoveries with F2FS support:
n7100 Devil2 kernel: download here
n7100 recovery: download here
t0lte Devil2 kernel: download here
t0lte recovery: download here (this one works also for Verizon)
The newest Devil3 hybrid kernel for N7100 and t0lte: download here
BOOTLOADER check
Regarding the fact that Devil2-recovery boots 4.3 and 4.4 ROMs, owners of the Note 2 should mind, that many recent custom ROMs are designed to work flawless only with the recent JB bootloaders. Custom ROMs don't update your bootloader, so your bootloader was flashed together with your latest stock ROM that you were using. While ICS bootloaders are nearly completely outdated, now also earliest JB bootloaders might cause problems and malfunctions. If so, some users will have to consider to update the bootloader.
Experienced users know: this is a damn risky task, as if Odin fails so that the old bootloader gets erased and new doesn't get properly flashed, only JTAG will be able to revive your device.
I have made a little guide and provided download link how to flash a knox-free 4.3 MJ5 bootloader for N7100: CLICK HERE
This 4.3 bootloader will boot any 4.3 or 4.4 OS, but it still has the charging issue (Sammy's fault) if the device is turned off. All the newer 4.4 bootloaders where the issue is solved are KNOX'ed, so bootloader downgrade won't be possible anymore if you use any of the later bootloader versions.
CAMERA APP TROUBLESHOOTING:
All who use AOSP custom ROMs (especially CM based ones) on their Note 2 devices might face the "ERROR: can't connect camera" issue. This problem is not devil2 kernel related. The Camera app is crashy on numerous devices. We can have our Camera working reliably, just mind that it is utterly important to keep the phone in clearly defined position when starting the camera (horizontal/vertical) and to be careful by each change of the axis rotation. Also don't view freshly shot photo in your camera app, but close the Camera and use Gallery for that.
Should you still face the nasty "can't connect..." error, instead of rebooting the OS use either of those apps, that can successfully restart the camera with one click (my N7100 needed to have both apps installed to make reset working, now either works fine):
Camera (CMFix) app from Play Store
Restart Camera.apk from HERE
Click to expand...
Click to collapse
Devil-DB-Recovery screenshots (v6.0.4.4):
Nice work m8!! Appreciate the time in you explaining the processes involved:thumbup:
Sent from my SGH-I317M using Tapatalk 2
Very detail write up Rich. Double:thumbup::thumbup:
Thanx
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2
Thanks RichMD, appreciated "how-to" guide.
However a few remarks:
Similar to the AROMA note above, you might want to install a ROM to primary first even if you want it in the secondary partition. The install script will not need to be modified and a normal kernel will boot the ROM so MTP will work. Then you can flash the DB kernel, make a backup and restore to the secondary. Hopefully, this is only temporary but at least this workaround exists. Hopefully, this is only temporary but at least this workaround exists.
Click to expand...
Click to collapse
It means that in the future we won't need to backup then restore Roms which have to be installed with a Aroma Installer?
In your guide I suggest to add the following b4 Step 5:
Make a Nandroid backup to save our current configuration! If you don't manage to install DB or if we aren't convinced by DB benefitis we can come back to an "one ROM boot".
totelysw classical
Sounds good so far hope to be able to install to external sd storage instead of the internal
Sometimes this process will need extras. At least it did for me, and more than once. Most probably because recovery is trying to replace or prevent original kernel of the second rom to be installed and causing mishaps..
So my additions are:
After flashing second rom howsoever, reflash dualboot kernel.
Reboot rom if stuck get into recovery and wipe cache and dalvik.
I had the issue of cm roms to use partitions, i had to fix permissions (for sec fs) and also once i had to log into recovery, then advanced menu and select /data location..
Sent from my GT-N7100 using xda premium
Memphis_ said:
Thanks RichMD, appreciated "how-to" guide.
However a few remarks:
It means that in the future we won't need to backup then restore Roms which have to be installed with a Aroma Installer?
In your guide I suggest to add the following b4 Step 5:
Make a Nandroid backup to save our current configuration! If you don't manage to install DB or if we aren't convinced by DB benefitis we can come back to an "one ROM boot".
Click to expand...
Click to collapse
Thanks. I plan to add a "How do you completely remove dual-boot" even if you didn't make a nandroid first but I will add a comment similar to what you mentioned.
Awesome!
great work cheers!:fingers-crossed:
myaslioglu said:
Sometimes this process will need extras. At least it did for me, and more than once. Most probably because recovery is trying to replace or prevent original kernel of the second rom to be installed and causing mishaps..
So my additions are:
After flashing second rom howsoever, reflash dualboot kernel.
Reboot rom if stuck get into recovery and wipe cache and dalvik.
I had the issue of cm roms to use partitions, i had to fix permissions (for sec fs) and also once i had to log into recovery, then advanced menu and select /data location..
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Flashing the DB kernel again is required after flashing primary or secondary. My comments are simply that you may not want to do it immediately and let the (primary partition ROM only) boot initially with the ROM included kernel to ensure MTP works. You then need to flash the DB kernel after if you ever want to boot the secondary ROM. If you just finished flashing a ROM to secondary then I "believe" you would need to flash the DB kernel before you could ever boot that ROM. However, MTP (at this point) might not work. If it doesn't then the workaround I listed would help. Does that answer your question/comment?
I will add more to the post on fixing permissions, etc. I need a bit more detail on what your process for CM was. You installed CM to secondary and it wouldn't boot so you went into recovery and advanced > fixed permissions (secondary FS was already enabled)?. I'm not sure what your comment about /data means other than you went to mounts and storage and mounted /data. Is that what you meant?
RichMD said:
Flashing the DB kernel again is required after flashing primary or secondary. My comments are simply that you may not want to do it immediately and let the (primary partition ROM only) boot initially with the ROM included kernel to ensure MTP works. You then need to flash the DB kernel after if you ever want to boot the secondary ROM. If you just finished flashing a ROM to secondary then I "believe" you would need to flash the DB kernel before you could ever boot that ROM. However, MTP (at this point) might not work. If it doesn't then the workaround I listed would help. Does that answer your question/comment?
I will add more to the post on fixing permissions, etc. I need a bit more detail on what your process for CM was. You installed CM to secondary and it wouldn't boot so you went into recovery and advanced > fixed permissions (secondary FS was already enabled)?. I'm not sure what your comment about /data means other than you went to mounts and storage and mounted /data. Is that what you meant?
Click to expand...
Click to collapse
No it is the other way around. Everything worked fine, CM booted perfectly, settings were to be applied easily. Gapps flashed well and worked without glitch. However, file managers, play store or anything trying to access fs couldnt manage to do so.. I first changed my ROM tried old sentinel (4.5) then paranoidandroid and then new sentinel.. But same thing happened. Then I booted reflashed DB and fixed permissions. Rebooted CM, still no access. Afterwards, I rebooted into recovery re-fixed permissions but this time under the advanced menu (surely after activating second partition from dualboot menu) I set the storage to /data/media/0 .. rebooted 2nd rom. this time everthing worked fine.
Aforementioned are all for 2nd rom. 1st rom worked like a charm except for the MTP
I would love to see this on the tmobile s4
Sent from my SGH-M919 using xda premium
Strange behaviour on my N7100
After I flash the Devil dual-boot kernel (either the current - Devil-n7100-DUAL-0.21.3_20130529.zip or the previous version) this is happening to my device:
0. flashing is succesful and I reboot
1. the logo "Samsung Galaxy Note II N7100" stays on screen for approx. 4 or 5 minutes. Initially I believed it's completely frozen
2. the ROM specific logo (CyanogenMod or Samsung) appears on screen and ROM is loading shortly
3. everything works perfect, except touchscreen with fingers. Only S-Pen is working. I can check the kernel and it's the version I've flashed. Also when I press Home button 4 times, screen colors becomes negative, as it should.
4. if device enters in Sleep (screen off), the notifications are working (eg. new mail)
5. if phone gets an incoming call or if I wake the phone from sleep, the screen stays on for less than a second, then forcibly reboots
6. back to step 1.
Have anyone encountered this problem? This is happening with either Samsung stock 4.1.1 firmware rooted or with Cyanogenmod 10.1 nightly from last days.
I would love to have this kernel working...
RichMD
sorry to hijack your thread, delete if you need.. here's what works for me, several times ( I used your and Der Teufel guide as reference) just put it in a step by step guide
After a lot of reading and some tinkering, I've got PACMAN 4.2.2 PA /AOKP /CM10 1on ROM1 and 4.1.2 Mike1986 ARHD17 Sammy on ROM2.
Adb, MTP, Trickster works fine on both.
Working great. Even managed to get Simplistic Framework and Xposed working on rom 2 (Sammy)
simply
(a) first put the rom you want as PRIMARY on your ext sd card, either a flashable zip or a CWM nandroid backup (NOT TWRP).. you will need this later in step 32
1 on your existing rom and kernel combination , flash DT recovery,
2 reboot to recovery
3 go to dual boot options in recovery
4 create second partition
5 reboot to first rom
6 check MTP
7 reboot recovery
8 dual boot menu
9 enable mount primary ( second on list of 3 options )
10 go back, Mounts and storage
11 mount efs, system, data, ext sdcard
12 go Back, wipe data (2nd option for FULL wipe)
13 check mounts again and remount as above
14 flash the rom you want to be as SECOND rom
15 do all your fancy mods now (Xposed etc)
16 check mounts, remount if necessary
17 flash DT dual boot kernel with "flash kernel" option
18 reboot
19 check MTP
20 go to step 7 and repeat 7-11 inclusive
21 do a backup to ext sd
to move the rom to second rom position..
22 dual boot menu
23 enable mount secondary ( third/last on list of 3 options )
24 go back, Mounts and storage
25 mount efs, system, data, ext sdcard
26 go Back, wipe data (2nd option for FULL wipe)
27 go to Backup and Restore
28 restore the rom you made in step 21 from the ext sd
29 reboot to second rom (allow full boot)
30 check MTP, should work
31 do steps 7-13
32 flash, or restore the rom you placed on your ext sd card in the very beginning step (a) ie the one that you want to be as FIRST/PRIMARY rom
33 Reboot
Done
DO NOT FLASH ANY KERNEL AFTER STEP 33 ( the kernel will show in primary rom settings as unavailable but check with Trickster Mod or CPU spy, it will show you that it is DT dual boot kernel)
The above has worked for me several times now, and some steps are overkill..
The 0 folder from 4.2.2 is visible from the Sammy rom but the Sammy files are not visible from 4.2.2 that's why I recommend using the ext sd for the above procedures as a failsafe
Sent from my dual boot GT-N7100 using Tapatalk 2
kashortiexda said:
RichMD
sorry to hijack your thread, delete if you need.. here's what works for me, several times ( I used your and Der Teufel guide as reference) just put it in a step by step guide
After a lot of reading and some tinkering, I've got PACMAN 4.2.2 PA /AOKP /CM10 1on ROM1 and 4.1.2 Mike1986 ARHD17 Sammy on ROM2.
Adb, MTP, Trickster works fine on both.
Working great. Even managed to get Simplistic Framework and Xposed working on rom 2 (Sammy)
simply
(a) first put the rom you want as PRIMARY on your ext sd card, either a flashable zip or a CWM nandroid backup (NOT TWRP).. you will need this later in step 32
1 on your existing rom and kernel combination , flash DT recovery,
2 reboot to recovery
3 go to dual boot options in recovery
4 create second partition
5 reboot to first rom
6 check MTP
7 reboot recovery
8 dual boot menu
9 enable mount primary ( second on list of 3 options )
10 go back, Mounts and storage
11 mount efs, system, data, ext sdcard
12 go Back, wipe data (2nd option for FULL wipe)
13 check mounts again and remount as above
14 flash the rom you want to be as SECOND rom
15 do all your fancy mods now (Xposed etc)
16 check mounts, remount if necessary
17 flash DT dual boot kernel with "flash kernel" option
18 reboot
19 check MTP
20 go to step 7 and repeat 7-11 inclusive
21 do a backup to ext sd
to move the rom to second rom position..
22 dual boot menu
23 enable mount secondary ( third/last on list of 3 options )
24 go back, Mounts and storage
25 mount efs, system, data, ext sdcard
26 go Back, wipe data (2nd option for FULL wipe)
27 go to Backup and Restore
28 restore the rom you made in step 21 from the ext sd
29 reboot to second rom (allow full boot)
30 check MTP, should work
31 do steps 7-13
32 flash, or restore the rom you placed on your ext sd card in the very beginning step (a) ie the one that you want to be as FIRST/PRIMARY rom
33 Reboot
Done
DO NOT FLASH ANY KERNEL AFTER STEP 33 ( the kernel will show in primary rom settings as unavailable but check with Trickster Mod or CPU spy, it will show you that it is DT dual boot kernel)
The above has worked for me several times now, and some steps are overkill..
The 0 folder from 4.2.2 is visible from the Sammy rom but the Sammy files are not visible from 4.2.2 that's why I recommend using the ext sd for the above procedures as a failsafe
Sent from my dual boot GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I certainly don't see that as a "hijack". The intent of the thread is to help anyone that is having a problem with the installations. Having multiple methods to try just helps ensure success if they keep trying.
n4553 said:
After I flash the Devil dual-boot kernel (either the current - Devil-n7100-DUAL-0.21.3_20130529.zip or the previous version) this is happening to my device:
0. flashing is succesful and I reboot
1. the logo "Samsung Galaxy Note II N7100" stays on screen for approx. 4 or 5 minutes. Initially I believed it's completely frozen
2. the ROM specific logo (CyanogenMod or Samsung) appears on screen and ROM is loading shortly
3. everything works perfect, except touchscreen with fingers. Only S-Pen is working. I can check the kernel and it's the version I've flashed. Also when I press Home button 4 times, screen colors becomes negative, as it should.
4. if device enters in Sleep (screen off), the notifications are working (eg. new mail)
5. if phone gets an incoming call or if I wake the phone from sleep, the screen stays on for less than a second, then forcibly reboots
6. back to step 1.
Have anyone encountered this problem? This is happening with either Samsung stock 4.1.1 firmware rooted or with Cyanogenmod 10.1 nightly from last days.
I would love to have this kernel working...
Click to expand...
Click to collapse
Just to confirm, this looks like you aren't trying to do anything with dual-boot - just using his dual-boot kernel on a solitary ROM - correct? If you can flash other custom kernels successfully (perseus, sabre, soap, etc.) then I don't know what to tell you. What recovery are you using to flash it?
HI RichMD,
I am getting error at step 6.
it fails to mount Primary Files.
I tried following
Reloaded Recovery -in duel boot menu -enable mounting of Pri File.
thn i tried to create secondary System image. Still m getting same error.
am i missing something .
Also i noticed that i am not able to mount SDCARD in menu Maount and Storage
regards
JoyMoro
---------- Post added at 11:31 AM ---------- Previous post was at 10:50 AM ----------
JoyMoro said:
HI RichMD,
I am getting error at step 6.
it fails to mount Primary Files.
I tried following
Reloaded Recovery -in duel boot menu -enable mounting of Pri File.
thn i tried to create secondary System image. Still m getting same error.
am i missing something .
Also i noticed that i am not able to mount SDCARD in menu Maount and Storage
regards
JoyMoro
Click to expand...
Click to collapse
Pls ignore it,. I got it working.
regards
JoyMoro
RichMD said:
Just to confirm, this looks like you aren't trying to do anything with dual-boot - just using his dual-boot kernel on a solitary ROM - correct? If you can flash other custom kernels successfully (perseus, sabre, soap, etc.) then I don't know what to tell you. What recovery are you using to flash it?
Click to expand...
Click to collapse
Yes, for now I haven't installed the second rom, however this is what I want to achieve, dual-boot. But firstly I wanted to make sure the kernel is working. I am using Devil recovery, when I flash other things with it, there are no problems...
I am getting error at step 6.
it fails to mount Primary Files.
I tried following
Reloaded Recovery -in duel boot menu -enable mounting of Pri File.
thn i tried to create secondary System image. Still m getting same error.
am i missing something .
Also i noticed that i am not able to mount SDCARD in menu Maount and Storage
Pls ignore it,. I got it working.
How did u get it working since i got the same issue here?
Is it only me who cannot get play store to work on sec.rom or anyone else have the same issue
Sent from my GT-N7100 using xda premium
no prob
myaslioglu said:
Is it only me who cannot get play store to work on sec.rom or anyone else have the same issue
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Play store works fine for me on second rom