------[ UPDATE ]-------
DooMRecovery v05 released! changelog here
------[ UPDATE ]-------
DooMRecovery for Sony Xperia S is based on ClockworkMod recovery source (GB 5.0.2.x).
Credits and special thanks to Koush and everyone else involved in Cyanogenmod project!
{
"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"
}
(the video is a bit older one from my Xperia Play but gives u an idea how it will work on device)
[ info ]
firstly i want to thank all the users of this community who donated the device to me! thanks everyone!
so friends i present to u DooMRecovery! its based on CWM 5.0.2.x sources... i have done some additions which i feel makes the recovery a lot smarter... i am still working on the recovery and will be actively maintaining it, so there will be updates as and when i get things working/add new features...
Touch capabilities are added by my teammate (Team UtterChaos) Napstar....
For posting BUGS/issues related to my kernel post them in kernel thread:
http://forum.xda-developers.com/showthread.php?t=1557452
For posting BUGS/issues related to my recovery post them in recovery thread:
http://forum.xda-developers.com/showthread.php?t=1594828
For general discussion regarding my kernel/recovery OR if u want to request for new features, post them in discussion thread:
http://forum.xda-developers.com/showthread.php?t=1596041
RECOVERY IS CURRENTLY AVAILABLE AS PART OF DooMKernel & Advanced Stock Kernel
THE RECOVERY IS STILL WORK IN PROGRESS AND I AM WORKING TO IMPROVE IT!!!
THE RECOVERY IS COMPATIBLE WITH ROM MANAGER!
Start the ROM Manager APP
Click on Menu
Select Manual Flash Override
Click OK at the next prompt
Confirm phone model as "LT26i"
Confirm version as "ClockworkMod 3.x+"
Click OK at the next prompt
thats it ROM Manager is now configured to use this recovery
[ disabled for this device ]
Advanced Menu -> Partition SDcard
[ credits / special thanks ]
Koush - for the brilliant work & coding on CWM recovery
Napstar - for doing most of the work on Touch capabilities for CWM recovery (not fully implemented it)
Frosty666 for the Vibration triggers
FreeXperia Team (Bin4ry & jerpelea) - for tooo many things!!
[ features ]
added a new menu "More Options"
AROMA File Manager is NOW directly accessible via this new menu
current ROM details can be retrieved via this new menu
fixed some internal sdcard (/emmc) related bugs
fixed advanced backup option
fixed this bug
fixed display of "build timestamp" and battery level
some more changes in font color to make it more readable
replaced background with my old favorite (thanks to Soheil)
implemented detection of internal sdcard as /emmc (if required)
slight changes in font color to make it more readable
now features larger XHDPI fonts (thanks to koush)
replaced the bottom "on-screen navigation buttons" with bigger buttons
fixed SDCARD mounting to PC as mass-storage
now recovery can backup/restore kernels and users can flash kernels (kernel.elf)
FULL TOUCH interface
swipe gesture support!!! - the hotspot for this is across full screen
swipe left to GO BACK/ Scroll UP
swipe right to Scroll Down
Honeycomb themed
haptic feedback
incase the recovery "hangs" or incase some unwanted event starts u can press the POWER button to restart the recovery (the device wont reboot, only recovery will restart)
shows current time (time when the recovery was entered/started)
shows the current battery percentage (CURRENTLY BUGGY)
uses new Roboto FONT (from latest CWM repo)
new "select update.zip menu": it will give u a new option - "show file details" - which will display the size (in bytes) and the MD5SUM of the selected file
when any update.zip is selected its complete file name will now be displayed (right at the top) and full path to that file will be printed before flashing begins
added prompt to display the "backup folder name" when user starts restoring a backup
added a warning and option to abort backup if space on sdcard is < 150 MB
removed Wipe cache partition from main menu (u can format /cache from "Mounts & Storage" menu)
removed those tons of "No"s
add confirmation to "backup" option in Nandroid menu... it used to keep getting pressed by mistake and start making backups immediately... now it will ask u before starting backup
replaced "reboot system now" with new menu "reboot options"... now with this new menu u can:
reboot sytem
reboot into recovery
reboot into fastboot mode
Power Off
added "advanced backup" menu (based on amit.bagaria implementations for his CF-Root kernel for SGS-SL)
now u can selectively choose which partitions to backup
its like a toggle
once u have finished choosing which partitions u want just click on "perform backup" and only those partitions will be backed up!!!
revamped layout for recovery menu (to improve navigation) [renamed few options and changed their order]
changed "wipe data/factory reset" option to just "factory reset", and detailed the partitions which will be wiped
changed text of most menus to fit the new honeycomb inspired design
the Nandroid backups & restore now show/displays which files were used to restore/what the backup is called (folder name)
[ known bugs ]
all backups are done get time stamp of year 1970 dont know why this happens but i am trying to sort it out some how
the recovery sometimes hangs - just press power button it will restart recovery without rebooting device
there are some graphics glitches
backups created with v01 recovery might give errors while restoring using v02 recovery... work around is posted here
if you encounter any other bugs/issues DO LET ME KNOW ASAP by posting them in THIS THREAD
[ requirements ]
UNLOCKED BOOTLOADER
fastboot binaries
[ how to install? ]
The recovery in integrated into the kernel! so when u flash the kernel it will contain the recovery!
[ how to enter recovery? ]
the recovery entry key is VOLUME UP button... so when you see the bootlogo watch out for the following notification which will tell u when u press the entry key (VOL UP):
the LED will turn BLUE
the device will vibrate for short duration
the bottom strip will be illuminated
if u press the entry key within this timeframe of the notifications (3 seconds) the device will enter into recovery
[ how to use recovery? ]
hardware keys
VOL UP/VOL DOWN key to move Up/Down in menu
HOME key to SELECT item
BACK key to GO BACK
OR
On-screen Navigation buttons
OR
Full Touch capibility!
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
ENJOY!!
DooMRecovery v01 released!
details, changelog at first post!!!
DooMRecovery is currently available ONLY as a part of DooMKernel!
please test out and let me know if u have any bugs/issues in THIS THREAD...
for general discussions use the following thread:
http://forum.xda-developers.com/showthread.php?t=1596041
I have just made an very old recovery backup as it says
Current Time:
12:03:27 GMT Mon 23 Feb 1970
but it feels good to have recory backup back again, thanks.
Hi Doom,
One quick question - is it possible to disable vibration in the recovery?
harfot said:
I have just made an very old recovery backup as it says
Current Time:
12:03:27 GMT Mon 23 Feb 1970
but it feels good to have recory backup back again, thanks.
Click to expand...
Click to collapse
ya i know
its like back to the future
kazuni said:
Hi Doom,
One quick question - is it possible to disable vibration in the recovery?
Click to expand...
Click to collapse
nope i have implemented it as a feature so its easier to check if the "touch response" was registered...
@DooMLoRD
Have you considered to get your CWM based recovery actually on CWM ROM Manager?
Auto Installation would be sweet for something like this for allready rooted users. and much easier to update aswell.
Might be a consideration. I would certainly donate for that to happen. ;D
Just flashed this. Runs good, su works as expected, overclocking is good to have, but I'll probably stick to default or even underclock a bit.
Sent from my LT26i using XDA
Edit: wrong thread, derp.
How about make console runs in recovery mode? With console, we can browse and delete apps in recovery!
The OpenRecovery for Motorola Milestone has this feature!
Thank!
juzz|NOR said:
@DooMLoRD
Have you considered to get your CWM based recovery actually on CWM ROM Manager?
Auto Installation would be sweet for something like this for allready rooted users. and much easier to update aswell.
Might be a consideration. I would certainly donate for that to happen. ;D
Click to expand...
Click to collapse
we dont have dedicated recovery partition... so we cant use any app to flash it...
also only officially supported devices get official CWM from ROM Manager (its limited only to releases by Koush)...
K900 said:
Just flashed this. Runs good, su works as expected, overclocking is good to have, but I'll probably stick to default or even underclock a bit.
Sent from my LT26i using XDA
Edit: wrong thread, derp.
Click to expand...
Click to collapse
yes even i underclock to max 1Ghz
keunhuvac said:
How about make console runs in recovery mode? With console, we can browse and delete apps in recovery!
The OpenRecovery for Motorola Milestone has this feature!
Thank!
Click to expand...
Click to collapse
interesting can u share some details?
PLEASE KEEP THIS THREAD FOR REPORTING ISSUES/BUGS
FOR GENERAL DISCUSSION/FEATURE REQUEST USE THIS THREAD
DooMLoRD said:
we dont have dedicated recovery partition... so we cant use any app to flash it...
also only officially supported devices get official CWM from ROM Manager (its limited only to releases by Koush)...
Click to expand...
Click to collapse
Something I came up with the other day: maybe put the recovery fs in a separate file? Then we can change the ramdisk to either load android normally or mount the recovery image like a ramdisk and boot it. This way any kernel (as long as it supports this method) can coexist with any recovery. Also means we could probably use recovery to flash kernels because it runs from RAM so there's no risk of breaking the recovery.
Sent from my Transformer TF101 using XDA
__ delete
K900 said:
Something I came up with the other day: maybe put the recovery fs in a separate file? Then we can change the ramdisk to either load android normally or mount the recovery image like a ramdisk and boot it. This way any kernel (as long as it supports this method) can coexist with any recovery. Also means we could probably use recovery to flash kernels because it runs from RAM so there's no risk of breaking the recovery.
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
we already did those things for X10, ARC... point is where will u keep the recovery file? if u keep it on /system then its not a true recovery as formatting /system will remove it... and in case of "bad flash" u will be left with no access to recovery...
so we have done the next best thing... integrated recovery into kernel... we use this for all xperia devices...
If I install the recovery with ROM Manager, also install automatically the Kernel?
Are there any requirements to install it?
Thank you!!
treoking said:
If I install the recovery with ROM Manager, also install automatically the Kernel?
Are there any requirements to install it?
Thank you!!
Click to expand...
Click to collapse
installing recovery from ROM Manager is ONLY supported for devices which have dedicated recovery partition and the ones which officially supported by Koush...
only way to get recovery is to flash kernel containing recovery via fastboot
DooMLoRD said:
we already did those things for X10, ARC... point is where will u keep the recovery file? if u keep it on /system then its not a true recovery as formatting /system will remove it... and in case of "bad flash" u will be left with no access to recovery...
so we have done the next best thing... integrated recovery into kernel... we use this for all xperia devices...
Click to expand...
Click to collapse
The idea is to keep the recovery on /boot, but make it possible to run a custom image from /system.
Sent from my Transformer TF101 using XDA
K900 said:
The idea is to keep the recovery on /boot, but make it possible to run a custom image from /system.
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
/boot is the kernel partition, which is not accessible... so essentially its going to be in kernel ramdisk
DooMLoRD said:
/boot is the kernel partition, which is not accessible... so essentially its going to be in kernel ramdisk
Click to expand...
Click to collapse
That's what I meant. I still getting used to the Xperias' internals after three years of HTC/Samsung
Sent from my Transformer TF101 using XDA
K900 said:
That's what I meant. I still getting used to the Xperias' internals after three years of HTC/Samsung
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
hehe...
Xperia are a bit of a pain in the a**...
anyways u all will be happy to know that we can finally flash kernels from recovery/OS to boot partition of this device (Xperia S)...
i have tested and it works well!!
Creating a new file called .hidenandroidprogress in the clockworkmod folder should speed up the nandroid backups eg:
/sdcard/clockworkmod/.hidenandroidprogress
-smc
DooMLoRD said:
hehe...
Xperia are a bit of a pain in the a**...
anyways u all will be happy to know that we can finally flash kernels from recovery/OS to boot partition of this device (Xperia S)...
i have tested and it works well!!
Click to expand...
Click to collapse
Great news Also HTCs can sometimes be even more pain, especially locked ones
Sent from my Transformer TF101 using XDA
Related
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
Kernel: official HTC kernel sources.
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.
I have the full version 4EXT. You make great job.
Thanks.
Am looking forward to checking out the hard work Just reading over the change log,have you managed to include an option for Wipe_Efs script?
Amazing!
Wow, simply amazing!! A touch based recovery. Cant believe it.
Dont really love the new Colors, but i trust you, that theming will be back soon.
Then we will have nice to control and beautiful looking recovery!
Have the paid version btw.
Awesome! Getting it right now!
---------- Post added at 03:51 PM ---------- Previous post was at 03:33 PM ----------
weird Recovery control didn't want to update I had to go through the my apps on the market vs the actual page for 4ext recovery control. weird, but i got it working all right!
Thank you all very much
IharpI said:
Wow, simply amazing!! A touch based recovery. Cant believe it.
Dont really love the new Colors, but i trust you, that theming will be back soon.
Then we will have nice to control and beautiful looking recovery!
Have the paid version btw.
Click to expand...
Click to collapse
Thanks
It's already completely customizable, just not via the app yet. This will be added of course as soon as possible!
In the meantime you can change all the colours by editing the file theme.prop on your sdcard inside the folder 4ext.
There will also be complete themes shortly. I think the first ones for the display resolution of your device are already available..
Need to gather the links..
Wow max, wow. This is truly epic. Awesome work buddy
Sent from my HTC Desire S using Tapatalk
I have the paid version too
Just bought the Market version Any word about the EFS wipe integration?
Edit: just gave this a try. The UI is very intuitive and works well! If I may give one suggestion, perhaps the confirmation messages that slide down from the top could show up a bit faster.
c00ller said:
Just bought the Market version Any word about the EFS wipe integration?
Click to expand...
Click to collapse
It's already there; check the wipe menu in the recovery section
Sent from my HTC Vision using XDA App
Congrats on your new release Madmaxx82. This new UI is top shelf. Love it!
thx for all your hard work on this.....
OriginalGabriel said:
It's already there; check the wipe menu in the recovery section
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I would actually prefer it in the wipe menu in recovery and not from within the rom app.
Thanks for the new 4EXT recovery version, absolutely love the new UI. 4EXT has been my go to recovery since it has been released. Think its time for me to make the jump to the paid version.
Thank you all soo much for that amazing feedback
Need to get some sleep now, but will answer any questions/posts tomorrow!
All I can say is "wow" this is mind blastingly awesome!
Sent from my HTC Vision using xda premium
Mind = Blown
I've been using 4EXT for quite a while, but this update is amazing! Thank you for all the hard work that you put into this recovery.
Sent from R2's G2
Just flashed the new touch version and I have to say that you did a great job. Can't wait to see what future releases bring us.
I'll be jumping on this recovery bandwagon soon, looks too good to pass up. She's ICS ready correct?
Sent from my T-mobile G2 using Tapatalk
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.
I can confirm 4ex touch recovery works fine on my mytouch4g.
Sent from my SGH-T959V using xda premium
cnote74 said:
I can confirm 4ex touch recovery works fine on my mytouch4g.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Thanks!
If someone who doesn't have the t-mobile one could confirm it would be great.
madmaxx82 said:
Thanks!
If someone who doesn't have the t-mobile one could confirm it would be great.
Click to expand...
Click to collapse
flashed tdj miui from on my mytouch 4g no problem, except I freaked out when the screen went black when I was formatting all partitions, then my phone rebooted into recovery so I could flash my rom.
Sent from my SGH-T959V using xda premium
Yes, I too, confirm that it works on myTouch 4G. Thanks for the beta
Yup mytouch 4g running RCMix 4.0 Energized BLUE Edition...works
Thank You for this!
It's Awesome!
No problems so far.
This is working great. Thank you for all your hard work.
Sent from my HTC Glacier using xda premium
Working here! Simply efing Amazing!!!!!!!!!!!!
This is amazing. Thank you so much.
Sent from my HTC Glacier using XDA App
YES ! Recovery just got 10 times better!
tried to get it from recovery control, no touch update available for mt4g...
its in beta download and flash through bootloader
http://www.4ext.net/PD15IMG.zip
Thank you all very much for the awesome feedback!
I have added it to the repo now with changelogs et.c.
Please flash it via 4EXT Recovery Updater / Control as it will setup or change 1;2 properties in your 4ext config.
flashed like a boss!
Very awesome work. I am very impressed. I didn't think that setup in recovery was possible.
Sent from my HTC Glacier using xda premium
Flashing from the repository now. Successful! Thanks Maxx
Yahoo! Glad I got to help with this! I learned some stuff in the process!
This is a Custom CWM-Based Touch Recovery 5.0.2.7 for Kindle Fire
Credits and special thanks to Koush and everyone else involved in Cyanogenmod project!
{
"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"
}
[ info ]
This is standard CWM recovery with some smart features/modifications and ability to navigate using touch screen (on-screen buttons)
i dont have this device with me so cant do testing myself... smirkis & others from this thread helped out with testing it...
[ credits / special thanks ]
Koush - for his brilliant work & coding for CWM recovery
TeamWin - for the TWRP recovery... i have used the recovery.fstab from their recovery-ramdisk...
pokey9000 - for providing the custom binaries to set bootmode
Napstar - my teammate (Team UtterChaos) for his work on implementing touch based navigation interface
sztupy - for his work on SteamMOD recovery (the core touch interface is based on his work)
jcase - for pointing out correct default.prop entires
all testers who helped with the initial test versions
[ WARNING ]
and incase this doest work correctly make sure that u can restore to factory condition...
DO NOT rapidly tap the on-screen buttons...
[ Requirements ]
fastboot capable Kindle Fire (factory cable way or rooted and bootmode enabled)
[ features ]
touch based on-screen buttons for navigation thru menus (from top to bottom):
SELECT
UP
DOWN
BACK
based on standard CWM5.0.2.7 recovery sources
revamped layout for recovery menu (to improve navigation) [renamed few options and changed their order]
changed "wipe data/factory reset" option to just "factory reset", and detailed the partitions which will be wiped
added reboot options (Kindle Fire specific)
reboot into system
reboot into recovery
reboot into fastboot mode
"Partition SDCard" is disabled for this device
add confirmation to "backup" option in Nandroid menu... it used to keep getting pressed by mistake and start making backups immediately... now it will ask u before starting backup
removed tons of "NO"s from some menus...
fixed "reboot into recovery" in "advanced menu"
shows battery percentage [based on generic sysfs interface] (not sure if this works as i dont have device to test)
shows current time (time when the recovery was entered/started)
uses new Roboto FONT (from latest CWM repo)
recovery build date/time is now shown
new "select update.zip menu": it will give u a new option - "show file details" - which will display the size (in bytes) and the MD5SUM of the selected file
new "advanced backup menu": it will allow the user to manually select which partitions to be backed up... supported partitions (/boot (kernel), /system, /data, /cache & /sd-ext)... THESE BACKUPs WILL BE DONE TO /sdcard
added prompt to display the "backup folder name" when user starts restoring a backup
added a warning and option to abort backup if space on sdcard is < 150 MB
increased on screen log/output display to 36 rows
[ how to flash/install ]
reboot into fastboot mode and enter the command:
Code:
fastboot flash recovery filename.img
[ how to use recovery ]
use onscreen buttons to navigate in recovery menus
[ what all to test ]
flashing UPDATE.zip (test update.zip : test_emmc_update-v3.zip will copy a file "blankplaceholder" to /system, /data & /cache partitions)
backup/restore of current ROM
mounting USB storage in recovery menu
access to device via adb
fix permissions (Advanced Menu)
reboot options (check if device can reboot into system, recovery & fastboot mode)
[ how to report issues ]
while reporting issues (if any) kindly provided detailed info as to what all steps lead to that error/issue... also while in this recovery mode (before rebooting) pull the recovery log files using ADB and upload them with ur post
Code:
adb pull /cache/recovery .
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
[ sources ]
https://github.com/DooMLoRD/CWM-Recovery-Modded-Kindle-Fire
[ download links ]
< NEW >
[Kindle Fire] CWM-Based Touch Edition Recovery 5.0.2.7 by TeamUtterChaos (v01-FINAL)
MD5HASH: 980f152121afd5dcd12b732669e21b09
< OLD >
[Kindle Fire] CWM-Based Touch Edition Recovery 5.0.2.7 by TeamUtterChaos (v01-BETA2)
MD5HASH: 62022defd4a459ff552490e7c07de5af
[Kindle Fire] CWM-Based Touch Edition Recovery 5.0.2.7 by TeamUtterChaos (v01-BETA1)
MD5HASH: 7524585473aa20158fc8491f85023dcc
enjoy!!!
reserved for later
Last night I got the forced 6.2.2 update that broke root. I was able to get root back using burritoroot2. But no matter what I tried I couldnt get twrp back. So I tried this CWM based recovery and it worked. I have it running now on my 6.2.2 rooted Fire. Just did a full back up. So far so good. Im just glad to have recovery again. Thanks for this.
Heres what Ive been able to do. Full backup, reboot to system, reboot to recovery, and mount usb storage.
kinda offtopic but somewhat relevant
Ok, so I was over at friends for dinner and then I wanted to perform a backup in anticipation of tonights beta1 test and left the KF on the couch in recovery mode... and my friends kids got ahold of the KF........ :/
After dinner I found it in perpetual fastboot mode with the SDcard erased and no image in /system... which means they wiped both my SDCard and then my whole image!!! Luckily I had my laptop in my car so I simply restored my SDCard and fastbooted a backup back in.
I am not sure how they did it as theyre not even past the "See **** Jump Jane" reading level but they did it.
which means we need to be extra careful when the device is in recovery mode... I dont think they would have succeeded if it was my Vision left on the couch vs the Fire with touchscreen....
anyway - this prompts two ideas..
1. additional prompts at the Factory Reset option (do you reeally really really want to do this) and at the Format SDCard option.
EDIT - and this is how I flash recovery
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Fire\tools>fastboot devices
0123456789ABCDEF fastboot
C:\Fire\tools>fastboot erase recovery
erasing 'recovery'... OKAY [ 2.030s]
finished. total time: 2.030s
C:\Fire\tools>fastboot flash recovery chaosbeta1.img
sending 'recovery' (5194 KB)... OKAY [ 1.473s]
writing 'recovery'... OKAY [ 1.020s]
finished. total time: 2.494s
C:\Fire\tools>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Fire\tools>
Gam3r 4 Life said:
Last night I got the forced 6.2.2 update that broke root. I was able to get root back using burritoroot2. But no matter what I tried I couldnt get twrp back. So I tried this CWM based recovery and it worked. I have it running now on my 6.2.2 rooted Fire. Just did a full back up. So far so good. Im just glad to have recovery again. Thanks for this.
Heres what Ive been able to do. Full backup, reboot to system, reboot to recovery, and mount usb storage.
Click to expand...
Click to collapse
glad to hear that...
androidcues said:
Ok, so I was over at friends for dinner and then I wanted to perform a backup in anticipation of tonights beta1 test and left the KF on the couch in recovery mode... and my friends kids got ahold of the KF........ :/
After dinner I found it in perpetual fastboot mode with the SDcard erased and no image in /system... which means they wiped both my SDCard and then my whole image!!! Luckily I had my laptop in my car so I simply restored my SDCard and fastbooted a backup back in.
I am not sure how they did it as theyre not even past the "See **** Jump Jane" reading level but they did it.
which means we need to be extra careful when the device is in recovery mode... I dont think they would have succeeded if it was my Vision left on the couch vs the Fire with touchscreen....
anyway - this prompts two ideas..
1. additional prompts at the Factory Reset option (do you reeally really really want to do this) and at the Format SDCard option.
Click to expand...
Click to collapse
hehe kids can figure out stuff
Factory reset already has a "are u sure prompt"
lets see if i have time i might add prompts to those format options...
Is source up anywhere, I would like to contribute.
DooMLoRD said:
glad to hear that...
hehe kids can figure out stuff
Factory reset already has a "are u sure prompt"
lets see if i have time i might add prompts to those format options...
Click to expand...
Click to collapse
jcase said:
Is source up anywhere, I would like to contribute.
Click to expand...
Click to collapse
touch edition sources arent pushed yet...
we are still finalizing things...
but it will be released soon...
DooMLoRD said:
touch edition sources arent pushed yet...
we are still finalizing things...
but it will be released soon...
Click to expand...
Click to collapse
Ok, it's just silly for two seperate groups to be working on the same thing at the same time.
Is this based off gweedo's/koush's?
jcase said:
Ok, it's just silly for two seperate groups to be working on the same thing at the same time.
Is this based off gweedo's/koush's?
Click to expand...
Click to collapse
base is CWM5.0.2.7 from koush/CM repo
Flashed beta1 and its much better than last... did everything on the menu and not one problem at all... except for getting sent to no mans land in key test... still cant find that trapdoor to get back. did backup restore flashed update.zip and emmcV3 and then flashed ICS played with full reboot menu liked how i can reboot into fastboot so i can flash a new recovery... but whatever.. good release... ready for next test.
now one suggestion and ill stop with suggestions after this... i liked it how CWM on the Vision would turn on when the device was off and charging... folks saw this as a bug but i saw it as feature and then that was patched up. Since Fire only has one button and i dont really like pushing that button to get to recovery (itll wear out faster) it would be killer if CWM could turn on when charging so when someones done charging and ready to turn oon device they can start right off in CWM. People can either just reboot system or start off with CWM utilities.
Sent from my T-Mobile G2 using xda premium
jimmydafish said:
mod edit *snip* insert really unwanted post here
Click to expand...
Click to collapse
we have been working on this for past two months and have released this recovery for various devices (SE Xperia X10, ARC, PLAY; HTC Flyer; Huawei Ideos X6; Samsung Galaxy SL i9003)...
FYI the base for this recovery is CWM (by koush/CM team) and i have personally added some modifications which can be found here: https://github.com/DooMLoRD/CWM-Recovery-Modded
most of the work, related to adding touch based navigation, has been done by my team-mate Napstar... the "touch" capability is from a small block of code from SteamMOD recovery by sztupy...
u can decide urself when u see the sources (sources will be released soon)...
further more if u dont understand/appreciate our work then u can leave this thread and stop talking crap like this...
another thing ur post is being reported to the MODS...
if ppl are not interested in our work i think we will stop this... there is no point wasting our time for a community who doesnt understand/appreciate what we are doing and anyways we dont have the device... we were purely doing this so that users from ur community can benefit... if there is so much hatred we will close this project...
Hey guys, just wanted to chime in here. I looked over his source code and he didn't use any of my work from what I can see. Keep up the good work man, the Fire needs something other than TWRP
gweedo767 said:
Hey guys, just wanted to chime in here. I looked over his source code and he didn't use any of my work from what I can see. Keep up the good work man, the Fire needs something other than TWRP
Click to expand...
Click to collapse
ha,, thanks,, that's easy for me... i was just checking in on it....spares me some time investigating.
cheers
DoomLord,
There are a lot of haters here, but a lot more that really appreciate all you are doing for us. Ignore those that ***** about **** they know nothing about, and keep on Keepin' on Thanks again!
MayfairDROID said:
DoomLord,
There are a lot of haters here, but a lot more that really appreciate all you are doing for us. Ignore those that ***** about **** they know nothing about, and keep on Keepin' on Thanks again!
Click to expand...
Click to collapse
I approve this message.
@DoomLord
I want to say thanks again. Please dont take one stupid comment from one person as reflecting the community. I myself have gotten pretty frustrated at people on this site. For every snobby, rude, know it all person on here there are many more that help and contribute to the overall community. So keep up the good work and ignore the haters.
DooMLoRD said:
we have been working on this for past two months and have released this recovery for various devices (SE Xperia X10, ARC, PLAY; HTC Flyer; Huawei Ideos X6; Samsung Galaxy SL i9003)...
FYI the base for this recovery is CWM (by koush/CM team) and i have personally added some modifications which can be found here: https://github.com/DooMLoRD/CWM-Recovery-Modded
most of the work, related to adding touch based navigation, has been done by my team-mate Napstar... the "touch" capability is from a small block of code from SteamMOD recovery by sztupy...
u can decide urself when u see the sources (sources will be released soon)...
further more if u dont understand/appreciate our work then u can leave this thread and stop talking crap like this...
another thing ur post is being reported to the MODS...
if ppl are not interested in our work i think we will stop this... there is no point wasting our time for a community who doesnt understand/appreciate what we are doing and anyways we dont have the device... we were purely doing this so that users from ur community can benefit... if there is so much hatred we will close this project...
Click to expand...
Click to collapse
So because of one person you are now accusing the WHOLE community of being unappreciative? Dude....wake up. Look at all the appreciative people on this thread and in many others. The thanks button love is flowing.
Sent from my Kindle Fire using xda premium
CTTKDKing said:
I approve this message.
Click to expand...
Click to collapse
Gam3r 4 Life said:
@DoomLord
I want to say thanks again. Please dont take one stupid comment from one person as reflecting the community. I myself have gotten pretty frustrated at people on this site. For every snobby, rude, know it all person on here there are many more that help and contribute to the overall community. So keep up the good work and ignore the haters.
Click to expand...
Click to collapse
thank you guys for ur support!
G1ForFun said:
So because of one person you are now accusing the WHOLE community of being unappreciative? Dude....wake up. Look at all the appreciative people on this thread and in many others. The thanks button love is flowing.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
well... this is not the first time something like this is happening...
and i am a bit edgy today
anyways lets get back to testing...
DoomLord
Do not stop the work at any cost..Let haters talk crap.
This great device needs CWM badly and a great developer like you..
ATB
Sent from my GT-I9100 using XDA App
Ok so to revert back to cm's stock boot.img after fastboot flashing a boot.img (a kernel) I would just reinstall cm 7. However, the zip fails to install now with this error...
-- Installing: /sdcard/Download/update-cm7.zip
Finding update package...
I:Update location: /sdcard/Download/update-cm7.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "blaze" || getprop("ro.build.product") == "blaze" || getprop("ro.product.board") == "blaze"
assert failed: getprop("ro.product.device") == "blaze" || getprop("ro.build.product") == "blaze" || getprop("ro.product.board") == "blaze"
E:Error in /sdcard/Download/update-cm7.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/Download/update-cm7.zip")
I think this is a updated version of the zip so i don't think i have installed it before. I was able to reinstall over cm previously (but with a different zip)
Aside from that, I've made a total of 2 backups, flash a different ROM several times, wiped multiple times, restored several times... Heck, i even used ROM manager to backup, wipe, install ROM, install gapps, install titanium zip and install several of my own zip's all in one run
This recovery is awesome! Thanks DooMLoRD!!!
I wonder what kinda stuff you would make if you actually had the device
Edit, could ROM manager be telling the recovery that i have a different device (because I choose manual override and picked despite HD to bypass installing the recovery with ROM manager) causing the install error (because Maby the zip is checking that to prevent installing the wrong zip)
Hello Guys .. this is clockworkmod v 6.0.1.0 By Koush
Now It's The Final build
Here is what Koush said on his G+ Account
ClockworkMod Recovery 6 for Galaxy Nexus
... has been released on ROM Manager.
Changes:
New backup format that deduplicates data between backups.
Faster backups.
Fixed restores > 2GB.
Minor UI tweaks (new background, animated Android)
Future:
In the past, I have merged/rebased every CWM with AOSP. With Jellybean, I have decided this is no longer in the best interest of the project. There are only a few areas of AOSP recovery that are of interest (roots.c - file system, minui, and updater). Those will continue to be merged into CWM. Other than that, doing a full rebase with every code drop has been a giant headache, with the code churn from upstream that providing little to no value to CWM.
In any case, this unties my hands to deviate completely from AOSP, with the primary goal to make a much more polished touch UI.
ROM Manager
ROM Manager is a little over 2 years old, and though it has grown in features quite a bit since its first incarnation, parts are starting to show its age. I've been contemplating a significant UI rewrite for some time now, and will pull the trigger on that shortly. I also want to add in some features that I am hoping will be of some interest:
* A paid ROM section for devs to publish their work and support their hobby.
* Upload your current ROM to ROM Manager for anyone to use, from the device.
* Connect ROM Manager to the Recovery Builder for automatic updates of recovery. No device left behind
Speaking of the Recovery Builder; it has been pleasantly successful. To date, around 1700 recoveries have been built. Many for devices ROM Manager currently does not even support.
Anyways, if you have any suggestions for the future of ClockworkMod products, please drop me a line!.
Click to expand...
Click to collapse
Here Koush explains how the new CWM method works that makes the backup files so small in size
New ClockworkMod Backup Format
TL;DR:
Don't delete /sdcard/clockworkmod/blobs
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.
Click to expand...
Click to collapse
{
"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"
}
Download links
CWM v6.0.1.0
http://goo.gl/Ohcrl
Touch CWM v6.0.1.0
http://goo.gl/DKxEX
Use Fastboot Commands to Flash it
Type " Fastboot Flash Recovery recovery-clockwork-touch-6.0.1.0-toro.img
or Fastboot Flash recovery-clockwork-6.0.1.0-toro.img
I take no credits for the Recovery i'm just trying to share it with you guys it's Done by Koushik as i mentioned
The original Post on G+ : http://goo.gl/jGgl5
This is a flashable zip for the 6.0 series Touch recoveries, in case anyone wants it. Boot into recovery, install zip, choose zip, go back, go to advanced, reboot recovery, profit. I hold no responsibility if it blows up your phone, but I've tested each one before uploading. So enjoy and thanks to D3vious for the OP.
This is the Flashable zip for the 6.0.0.1 -------> http://dl.dropbox.com/u/17342655/CWM-Touch-6.0.0.1-Toro.zip
MD5 - 4acbc676039817382cab3e6338c1872f
This is the Flashable zip for the 6.0.0.4 -------> http://dl.dropbox.com/u/17342655/CWM-Touch-6.0.0.4-Toro.zip
MD5 - 4cfe0f710120c820915e37948ecc2cd2
This is the Flashable zip for the 6.0.0.5 -------> http://dl.dropbox.com/u/17342655/CWM-Touch-6.0.0.5-Toro.zip
MD5 - 026a7d86db10da65c358f1a67952bc1e
Thank you for posting this. The previous version didn't work well on my end. One press on the volume keys made the selection jump around and sometimes not even register the selection when selected and produce a black screen.
6.0.0.1 works great. I'll flash the touch when i get home.
I wish there was an app like Flash Image GUI that i used for my Evo 3d for the G-NEX. Unfortunately that's way beyond my abilities to cook up. If someone did it would be a money maker. Unless there's a way to trick Rom Manager into flashing the touch recovery
Sent from my Galaxy Nexus using Tapatalk 2
totally forgot I saw this on droid-life. Thanks for reminding me!
xavier86 said:
Thank you for posting this. The previous version didn't work well on my end. One press on the volume keys made the selection jump around and sometimes not even register the selection when selected and produce a black screen.
6.0.0.1 works great. I'll flash the touch when i get home.
I wish there was an app like Flash Image GUI that i used for my Evo 3d for the G-NEX. Unfortunately that's way beyond my abilities to cook up. If someone did it would be a money maker. Unless there's a way to trick Rom Manager into flashing the touch recovery
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Renaming it should work
Sent from my Galaxy Nexus using xda app-developers app
When in the Touch recovery when I go to reboot my device I get this screen that says:
"ROM may flash stock recovery on boot. Fix? THIS CAN NOT NE UNDONE."
The usual multiple NOs and a "YES - Disable recovery flash"
What does this mean? Do I choose yes? or keep hitting no or Go Back when I reboot?
I flashed using the CWMR Touch app which can flash IMG files
Also my background is grey not black?
Maybe I should give it a try.
destinydmm said:
When in the Touch recovery when I go to reboot my device I get this screen that says:
"ROM may flash stock recovery on boot. Fix? THIS CAN NOT NE UNDONE."
The usual multiple NOs and a "YES - Disable recovery flash"
What does this mean? Do I choose yes? or keep hitting no or Go Back when I reboot?
I flashed using the CWMR Touch app which can flash IMG files
Also my background is grey not black?
Click to expand...
Click to collapse
Background being gray is part of the change log, Koush just decided to change it is all. Its normal.
As for your other issue, I'm not sure. Mine definitely hasn't done that
Sent from my Galaxy Nexus using xda app-developers app
bill12690 said:
Background being gray is part of the change log, Koush just decided to change it is all. Its normal.
As for your other issue, I'm not sure. Mine definitely hasn't done that
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
EDIT: Refresh my memory on how to flash with flashboot commands again?? PLEASE
NEVERMIND READ THE WIKI
Saw it on Koush's G+ page don't delete the new "blobs" folder
Edit nevermind.
Works great but now when I reboot from recovery it throws up another menu and talks about stock recovery. Is this something I can delete from the recovery. I just want it to reboot with no warnings. If this is a new feature then that's fine. I am OK with it I just have never had this option and it reboots whether I click go back or yes
6.0.0.4 is out now
Khayos said:
6.0.0.4 is out now
Click to expand...
Click to collapse
Yep. Saw the announcement for the CWM update and got myself 6.0.0.4.
Where can you grab the 6.0.0.4 img file?
Any chance of a flashable 6.0.0.4? In the process of moving, don't have computer available to issue fast boot commands.
Sent from my Galaxy Nexus using xda premium
thenewguy821 said:
Any chance of a flashable 6.0.0.4? In the process of moving, don't have computer available to issue fast boot commands.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Use ROM manager
I did read somewhere you can put it on your SD card and use terminal emulator but have never done it myself. Sorry.
Is anyone else having problems backing up the blobs folder to your PC? Whether I use the Backup SD Card option in the toolkit or just try to drag and drop in Windows it fails to copy.
otaku91 said:
Is anyone else having problems backing up the blobs folder to your PC? Whether I use the Backup SD Card option in the toolkit or just try to drag and drop in Windows it fails to copy.
Click to expand...
Click to collapse
A moderator on AndroidForums said he was having issues with CWM 6.0.0.1 and restoring a NANDRIOD made with it. Has this issue been resolved with this build?
{
"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"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
WARNING
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to TheMultiROM Menu (3 bars in the top right corner) to flash ROMs/kernels or other mods.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
Your device must not be encrypted.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
Make sure you are on a Rom compatible with one of these kernels and flash it or use the non-kexec workaround. (See important Notices)
Reboot into MultiROM TWRP and flash the MultiROM installer
That's it. You can now go to TheMultiROM Menu (3 bars in the top right corner) to start flashing other ROMs.
Adding ROMs
Go to recovery, select TheMultiROM Menu (3 bars in the top right corner) -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to TheMultiROM Menu (3 bars in the top right corner) in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to TheMultiROM Menu (3 bars in the top right corner) -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch master)
Modified TWRP - https://github.com/multirom-htc/Team-Win-Recovery-Project (branch android-6.0)
Kernel w/ kexec-hardboot patch - https://github.com/Myself5/kernel/ (branch aosp/LA.BF64.1.2.2_rb4.7)
FAQs can be found here.
CREDITs
Tasssadar
Olivier
nkk71
Garcia98
Thunder07
skin1980
Envious_Data
[NUT]
Panic Brothers
You might want to consider a Donation to Tasssadar, who is the Mastermind behind MultiROM
As well as a Donation to nkk71, who wrote the kexec-workaround and helped me a lot
Thanks a lot to those who have donated! The 2 really deserve it!
XDA:DevDB Information
MultiROM for Sony Xperia Z5, Tool/Utility for the Sony Xperia Z5
Contributors
Myself5
Source Code: https://github.com/XperiaMultiROM/multirom/tree/master
Version Information
Status: Testing
Created 2016-05-08
Last Updated 2016-06-25
Important Notice
This Posts includes Important Notices you need to read if you want to use MultiROM on your Z5.
You need to a kexec-hardboot supporting kernel or the non-kexec workaround as described perfectly by @nkk71 here: http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4 (Be sure to leave him a like!)
Recovery Notice: The Recovery is working with init_sony. If your Kernel is using a older way to load recoverys, then it wont work. Talk to your Kernel dev about using init_sony.
MOST IMPORTANT: When installing MultiROM on Stock, USB Connections will be broken (Charging is fine). It's caused by MultiROM screwing up the permissions of a init file which is responsible for USB. There are Kernels where USB is fixed already. A list of them is in post 3. For intrested Devs, this is how to fix it:
Just add
Code:
chmod 750 /init.usbmode.sh
to the on init step inside of init.sony.usb.rc. It will fixup the permissions MultiROM screwes up.
CHANGELOGs
General MultiROM Changelog can be found here:
Changelog
XperiaMultiROM Specific Changelog is here:
Recovery Changelog
MultiROM Changelog
DOWNLOAD
https://dl.myself5.de
The recovery.img is Tassadars modified TWRP to flash secondary Roms. It is needed to flash the secondary Roms.
SUPPORTED KERNELs
Basically you can use any Kernel you want, if you can live without Touch Support in MultiROM and use the no-kexec workaround.
However, if you want Touch Support as well as fixed USB and kexec-hardboot, use one of these kernels:
OM5Z Kernel
AndroPlus Kernel (not sure if AP Kernel has fixed USB)
If you want your favorite kernel to support kexec or at least working touch and USB, tell the dev to merge my commits.
Nice work mate :good::good:
Though every effort has been made to ensure some form of safeguards and redundancy, MultiROM has always been a "hack", and the no-kexec-workaround is as well.
The no-kexec-workaround is working nicely on HTCs (well at least M7, M8, and M9) and I've seen some other devices using it successfully as well.
As always, have your backups safely tucked away somewhere fully safe.
Happy testing, and feel free to mention me (easiest way for me to get notified), if you think there's an issue to be addressed with the workaround.... I've personally only used it on HTC M7, M8 and M9, so there may be device specific issues, which I cannot account for.
Special thanks to @Captain_Throwback , @ljjehl and @MassStash for all the help and encouragement
And a very special thanks to @z31s1g not only for the official TWRP theme, but all the help he provided bringing it to MultiROM in a very quick way, thanks :good:
Wow this is so nice I was waiting for this! I still have a few questions tho:
-Will this work with stock 6.0 with the modified stock kernel (DM-Verity disabled/ Sony RIC disabled / DRM-FIX) ? I'm worried if it will brick my device since you wrote you have a hard time with stock.
-What is no-kexec? Why do I need it?
-About the USB connection bug on stock so if I install your dirty fix everything will work as before? If I uninstall multiROM I assume the USB bug will go away right?
Thank you for your time sorry I'm a noob
zate27 said:
Wow this is so nice I was waiting for this! I still have a few questions tho:
-Will this work with stock 6.0 with the modified stock kernel (DM-Verity disabled/ Sony RIC disabled / DRM-FIX) ? I'm worried if it will brick my device since you wrote you have a hard time with stock.
-What is no-kexec? Why do I need it?
-About the USB connection bug on stock so if I install your dirty fix everything will work as before? If I uninstall multiROM I assume the USB bug will go away right?
Thank you for your time sorry I'm a noob
Click to expand...
Click to collapse
1. Yes, it will work (You just won't have touch in the MultiROM menu (don't worry, you can setup the kexec workaround to work automatically in TWRP, as well as navigate with the volume buttons inside the MRom Menu). The hard time I get is with porting kexec to the stock kernel.
2. The No-kexec workaround is a (ha, who tought that ) workaround to not use kexec-hardboot. Kexec hardboot is a technology to load a kernel into the RAM using an other kernel. This is how MultiROM usually works. Read more about that here if you're intrested: http://forum.xda-developers.com/showthread.php?t=2104706 . Now, the no-kexec workaround is doing it on a rather dirty (but nicely working) way. It flashes the secondary ROMs boot.img to your boot partition, and then modifies the mount points to link to the ROM files in your internal/external storage (whereever you installed your secondary ROMs). It is needed, because of (1.), and because stock will probably not able to load a AOSP Kernel once kexec is working (so stock can only load stock, and AOSP can only load AOSP. For everything else, you need the no-kexec workaround).
3. Yes. USB is not working, because a script (which is responsible to start the USB Service) has the wrong permissions after booting from the MultiROM Menu (I was not able to include a proper fix for it inside the MultiROM code itself, maybe I will be some day). My App just fixes the permissions and executes the script (which else would be done by the system automatically) (It's basically just executing these 2 commands when pressing the button (or at boot when you turn the autofix on) https://github.com/Myself5/andoid_p...ava/de/myself5/stockusbfix/FixIt.java#L31-L34). Once you remove MultiROM, the script will get its proper permissions back as its a ramdisk file, inside the ramdisk it actually has its proper permissions, it just doesnt when getting extracted from the ramdisk at boot and MultiROM follows (MultiROM messes up the permissions).
I hope that answers your questions, if not, feel free to ask again
P.S. Be sure to read nkk71s Info about how to enable the kexec-workaround in the post I linked in the important notices post, it might shed some more light on what is the non-kexec workaround.
Myself5 said:
SNIP
Click to expand...
Click to collapse
Thank you very much for your quick answer!
So if I understood this right the detailed instructions would be:
Flash TWRP-Multirom-20160507-00-sumire.img or the recovery.img or both(?) with fastboot(?) to get the modified TWRP w/ MultiROM support
Now with this Modded TWRP I need to enable that no-kexec workaround in the settings?
Flash the actual multiROM: multirom-20160507-v33x-UNOFFICIAL-sumire.zip in TWRP
Flash e.g. CM13 (Finally ) from here: http://forum.xda-developers.com/xperia-z5/development/rom-cyanogenmod-13-sony-xperia-z5-t3356163" via the MultiROM menu.
Install the usbfix.
Does the CM13 Rom need to be modified to work with MultiROM or will it work as it is?
Thank you in advance
zate27 said:
Thank you very much for your quick answer!
So if I understood this right the detailed instructions would be:
Flash TWRP-Multirom-20160507-00-sumire.img or the recovery.img or both(?) with fastboot(?) to get the modified TWRP w/ MultiROM support
Now with this Modded TWRP I need to enable that no-kexec workaround in the settings?
Flash the actual multiROM: multirom-20160507-v33x-UNOFFICIAL-sumire.zip in TWRP
Flash e.g. CM13 (Finally ) from here: http://forum.xda-developers.com/xperia-z5/development/rom-cyanogenmod-13-sony-xperia-z5-t3356163" via the MultiROM menu.
Install the usbfix.
Does the CM13 Rom need to be modified to work with MultiROM or will it work as it is?
Thank you in advance
Click to expand...
Click to collapse
1. TWRP-Multirom-Stock-20160507-00-sumire.img is the recovery you need. Flash it via
Code:
fastboot flash recovery TWRP-Multirom-Stock-20160507-00-sumire.img
(If the Stock is not working, use the other one, I don't know which of the 2 existing recovery loading tools your kernel is using).
2. First flash multirom, then enable it in the MultiROM Settings Tab inside TWRP (see important notices on how to do that, nkk71 describes it in the thread)
3. yes.
4. Exactly.
5. Yes, only needed for stock roms, don't forget that. Oh, and it requires root, so depending if you have root already, you also need to install SuperSU (use 2.71 beta, it worked fine for me)
6. No, the secondary Roms don't need any changes at all.
BTW, your questions seem to be common, do you mind if I copy them together with my answers to a little FAQ in post 2?
Myself5 said:
1. TWRP-Multirom-Stock-20160507-00-sumire.img is the recovery you need. Flash it via
Code:
fastboot flash recovery TWRP-Multirom-Stock-20160507-00-sumire.img
(If the Stock is not working, use the other one, I don't know which of the 2 existing recovery loading tools your kernel is using).
2. First flash multirom, then enable it in the MultiROM Settings Tab inside TWRP (see important notices on how to do that, nkk71 describes it in the thread)
3. yes.
4. Exactly.
5. Yes, only needed for stock roms, don't forget that. Oh, and it requires root, so depending if you have root already, you also need to install SuperSU (use 2.71 beta, it worked fine for me)
6. No, the secondary Roms don't need any changes at all.
BTW, your questions seem to be common, do you mind if I copy them together with my answers to a little FAQ in post 2?
Click to expand...
Click to collapse
Thanks for answering all my questions. That should have cleared it up for noobs like me
The instructions seem a bit summarily written so your answers help a lot.
Yes sure go ahead FAQ is always nice
noob flasher here not quite got this fully working with a secondary rom yet still trying, but one scenario I can't get my head around.
If your primary rom is stock no root. How can you install the usbfix? Is this scenario possible?
bongo1 said:
noob flasher here not quite got this fully working with a secondary rom yet still trying, but one scenario I can't get my head around.
If your primary rom is stock no root. How can you install the usbfix? Is this scenario possible?
Click to expand...
Click to collapse
Nope. USB Fix needs root to work. I am still working on a different workaround for it (maybe inside MultiROM), but thats lower priority.
Sent from my Xperia Z3 using Tapatalk
@Myself5 , hey.
Could you extend support to the z5 premium too maybe ?
Thanks
Regards
AVK
Ashray_Vk said:
@Myself5 , hey.
Could you extend support to the z5 premium too maybe ?
Thanks
Regards
AVK
Click to expand...
Click to collapse
I don't develop for devices I don't own, as I then can't guarantee that everything does work nor that it won't break someones device. If there is a developer working on satsuki who wants to port it and comes across problems, I'll gladly help, but I'm not going to blind-port it on my own, I hope you understand that
Hey I have the E6653 and I'm getting error 7 while flashing multirom. Recovery flashing was successful tho. Why am I getting the error the codename of my phone should be "sumire" or is there something I've missed?
zate27 said:
Hey I have the E6653 and I'm getting error 7 while flashing multirom. Recovery flashing was successful tho. Why am I getting the error the codename of my phone should be "sumire" or is there something I've missed?
Click to expand...
Click to collapse
hum, 6653 is what I have too. What did you flash it on? Which recovery did you use? The Stock or the other one?
Sent from my Xperia Z3 using Tapatalk
Damn man you answer fast
I flashed it via TWRP, TWRP 3.0.2-0 (wrong I guess), I tried to flash the stock recovery one
Here is my fastboot output:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users
\Pein\Downloads\TWRP-Multirom-Stock-20160507-00-sumire.img
target reported max download size of 536870912 bytes
sending 'recovery' (33988 KB)...
OKAY [ 1.118s]
writing 'recovery'...
OKAY [ 0.464s]
finished. total time: 1.584s
Seems like it wasn't successfull because TWRP seems like the same as before :/ Should I try the other recovery? (Without stock)
zate27 said:
Damn man you answer fast [emoji14]
I flashed it via TWRP, TWRP 3.0.2-0 (wrong I guess), I tried to flash the stock recovery one
Here is my fastboot output:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users
\Pein\Downloads\TWRP-Multirom-Stock-20160507-00-sumire.img
target reported max download size of 536870912 bytes
sending 'recovery' (33988 KB)...
OKAY [ 1.118s]
writing 'recovery'...
OKAY [ 0.464s]
finished. total time: 1.584s
Seems like it wasn't successfull because TWRP seems like the same as before :/ Should I try the other recovery? (Without stock)
Click to expand...
Click to collapse
which kernel are you using?
BTW: MROM TWRP looks pretty similiar to the default TWRP, it just has 3 bars in the upper right corner which opens the Mrom Menu.
Sent from my Xperia Z3 using Tapatalk
kexec and Stock!
All right. I finally managed to get kexec-hardboot working on stock. I ported it to @AndroPlus Kernel at a first, because it seems to be the kernel you people use. I also uploaded a flashable zip (I used AndroPlus' flashable zip as a base), you can find it here:
Boot.img: http://dl.myself5.de/sumire/MultiROM/boot_E6653_M5_AP.img
Flashable ZIP: http://dl.myself5.de/sumire/MultiROM/Z5_AndroPlusKernel_M5_ModZ_Edit_Permissive_v27.zip
Source for it would be here: https://github.com/Myself5/android_kernel_sony_msm8994_kitakami_r2
I also send a PR for it to @AndroPlus (https://github.com/AndroPlus-org/android_kernel_sony_msm8994_kitakami_r2/pull/3)
(Ramdisk is from AndroPlus Kernel v27, with the fix below)
Oh, and because I am badass, I also fixed up USB on Stock with that Kernel.
For every Stock Kernel Developer who's intrested how I did that (looking at you @AndroPlus and @zacharias.maladroit), I simply adjusted the USB files permissions in the ramdisk.
Just add
Code:
chmod 750 /init.usbmode.sh
to the on init step inside of init.sony.usb.rc. I know it's dirty.. but hey. It surely is less dirty than my hacky App (which therefore is no longer needed BTW).
Will suzuran devices work
killedbyghost58 said:
Will suzuran devices work
Click to expand...
Click to collapse
No.
Regarding porting requests its the same as for Z5 Premium. If I don't own the device, I'm not going to port Mrom to it.
HOWEVER: For suzuran specifically, @oshmoun is working on porting MultiROM to it, based on my device trees which means MultiROM for Z5C is coming in the nearish future.