CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1 - Galaxy Ace S5830 Android Development

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://docs.google.com/uc?id=0B5c3gpyMBJusXzRfRWg4TXhZdVE&export=download
aromafm_cooper.zip (v1.91)
http://www.upload.ee/files/3959191/aromafm_cooper.zip
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ Touch Recovery for Galaxy Ace, Tool/Utility for the Samsung Galaxy Ace S5830
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-07

:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.

NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary
commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root

Very nice... will try it soon... :good:

Wow this should be great

I tried the recovery and it works. Installation is quick and simple and works just as described. Installing, wiping, backups, touch (up and down) and everything else works just as said. Kudos to you OP!

The last thing I wanna know:
After installing/restoring anything, can you successfully reboot to system?
You should also try Aroma File manager, it's the best part of this recovery.

Gonna Try...

@Bhargav97 i tested it , everything is working but there is one big problem , the recovery cannot reboot to system , it only reboot to recovery ,even if i shut down the device and then boot it , still stuck on recovery
hope you fix it
thanks for your hard work
Sent from my GT-S5830 using Tapatalk

nizar.nasani said:
@Bhargav97 i tested it , everything is working but there is one big problem , the recovery cannot reboot to system , it only reboot to recovery ,even if i shut down the device and the boot it , still stuck on recovery
hope you fix it
thanks for your hard work
Sent from my GT-S5830 using Tapatalk
Click to expand...
Click to collapse
Expect a fix soon!
I was understanding the problem for last few days (because same happens to other two devices also) and finally got the solution and I'll be re-compiling recovery as soon as I get some time.

UPDATE:
-Updated philz recovery sources to 6.23.9 (26.03.2014)
-cm-ota compatibility fixes.
-reboot to system bug is now fixed.
Download link updated in first post.

Am I dreaming? Thanks for revive my old Ace
Sent from my Nexus 5 using XDA Premium 4 mobile app

Bhargav97 said:
UPDATE:
-Updated philz recovery sources to 6.23.9 (26.03.2014)
-cm-ota compatibility fixes.
-reboot to system bug is now fixed.
Download link updated in first post.
Click to expand...
Click to collapse
swipe left and right dont work for me ????

Rhievaldo said:
swipe left and right dont work for me ????
Click to expand...
Click to collapse
Always Read OPs of a thread.
See my post #3, I've already stated that Right/Left swipe won't work yet. We're lucky to at least have a basic touch code implemented in our androidarmv6 sources. It is improving...someday if androidarmv6 developers plan to furnish the recovery touch code, right/left swipe will also be fixed. I can't fix that.

Bhargav97 said:
Always Read OPs of a thread.
See my post #3, I've already stated that Right/Left swipe won't work yet. We're lucky to at least have a basic touch code implemented in our androidarmv6 sources. It is improving...someday if androidarmv6 developers plan to furnish the recovery touch code, right/left swipe will also be fixed. I can't fix that.
Click to expand...
Click to collapse
always read it,, but forgot about that. Sorry... cause read it at 23 march, and try at 30 march..

MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusUkVLRWJ2OVBXak0/edit?usp=sharing

everything seems to be working for me
---------- Post added at 06:43 PM ---------- Previous post was at 06:34 PM ----------
actually, all features work butkeeps rebooting into recovery,, not sure if its a problem restoring a back up ill try installing a new rom
edit,, yes it reboots into recovery no matter what,, damn,, nearly close to perfect

Bhargav97 said:
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusUkVLRWJ2OVBXak0/edit?usp=sharing
Click to expand...
Click to collapse
yes right when i reboot to system it reboot to recovery, the same as the previous time.

There was a little bug which caused issue for rebooting to system. I just fixed it and asked @chraso to compile. So, now finally it's done! Updated first, second and third posts.
Report back for the download link put up on first post.

i've test almost everything and i can say this is the best recovery ever made for ace ✌
thanks for bring it to our ace
sent from my kitkat ACE

Related

Oldkitchen. Closed thread.

THIS IS AN OLD OBSOLETE TOOL. CLICK HERE TO GET THE NEW IMPROVED ONE!
{
"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"
}
FEATURES
Rickys Rom Kitchen Features(BETA2):
Build updater-script
Set up working from backup imgs (doesnt always work)
Add my theming system
Check for boot.img
Check for theming system
Ability to add license for aroma
Push to device and flash with ORS
Split boot.img
Rebuild boot.img from kernel and ramdisk
Setup project from phone
Setup project from .zip
Ability to modify .zips
Saves project and project settings
Open working folder
Add busybox
Install curl and openssl
Deodex
Zipalign
Build.prop options
Install aroma
Configure aroma
Open most recent build
Remove current project and files
Add lines to build.prop
Automatically adds project name to build.prop
Automatically adds project name to aroma-config
Build PROJECTNAME
Configure preinstalled aroma
Sign PROJECTNAME
TOOL FEATURES FOR All Other Phones:
Deodex rom
Odex rom
Port rom(very early beta)
Get device information
Install Curl
Install OpenSSL
Install Busybox
Hot Reboot
Compress Backup
Integrated Lcd Density Changer
Fixes Permissions
Show oem token code
Flash oem token
Flash recoveries
Flash recovery themes
My GraffStyleZ TWRP Theme Included
Enable root permissions
Flash any .zip file
Flash a rom
Create a coloured logcat
Show CID
Write superCID
Backup device
Restore device
Relock bootloader
Reboot options
Advanced wipe Options
Pulls Files From Server
Manual Adb And Fastboot
Wipe Data
Wipe Cache
Wipe System
Wipe Dalvik Cache
Wipe Android Secure
Wipe Recovery
Wipe Boot img
Wipe Data,Cache
Wipe Data,Cache,System,Dalvik
Fix Low battery error
Automatically Kills adb Upon Completion Of Task
Unlock bootloader guide
Install custom recovery guide
Install recovery theme guide
Enable root permissions guide
Install roms or .zip files guide
Restore device to defaults guide
TOOL FEATURES FOR HTC Sensation XL:
Deodex rom
Odex rom
Port rom(very early beta)
Get device information
Install Curl
Install OpenSSL
Install Busybox
Hot Reboot
Compress Backup
Integrated Lcd Density Changer
Fixes Permissions
Show oem token code
Flash oem token
Flash recoveries
Flash recovery themes
My GraffStyleZ TWRP Theme Included
S-Off
Enable root permissions
Force Update
Flash any .zip file
Flash a rom
Create a logcat
Show CID
Write superCID
Backup device
Restore device
Relock bootloader
Flash custom radio
Fix sdcard errors
Reboot options
Fix low battery error
Advanced wipe Options
Pulls Files From Server
Manual Adb And Fastboot
Wipe Data
Wipe Cache
Wipe System
Wipe Dalvik Cache
Wipe Android Secure
Wipe Recovery
Wipe Boot img
Wipe Data,Cache
Wipe Data,Cache,System,Dalvik
Automatically Kills adb Upon Completion Of Task
Unlock bootloader guide
Install custom recovery guide
Install recovery theme guide
Enable root permissions guide
Install roms or .zip files guide
Restore device to defaults guide
DOWNLOAD
Download The .EXE (Installation Package) From D-h.st(Dev host)
Download The .ISO (Disk Image)From d-h.st(Dev host)​
Click to expand...
Click to collapse
Installation For .EXE
1. download and install java and notepad++(optional but reccomended)
2. Open AETv7.5.exe
3. Follow Prompts
4. Enjoy
Installation For .ISO
1. download and install java and notepad++(optional but reccomended)
2. Right click on AETv7.5.iso
3. Click "burn disk image"
4. Burn it to a disk
5. Insert disk and it will run installation
-NOTE-
This tool is to be used at your own risk, i will not be held responsible for any damages even though none are expected!
This tool voids your warranty!
VERSION 10.0(BETA2)-
Added build updater-script
Set up working from backup imgs (doesnt always work)
Add my theming system
Checks for boot.img
Checks for theming system
Ability to add license for aroma
Push to device and flash with ORS
Split boot.img
Rebuild boot.img from kernel and ramdisk
Partially fixed deodex issue
VERSION 9.0(BETA)-
Made and added Rickys Rom Kitchen(like kitchen for windows)
--kitchen options
Setup project from phone
Setup project from .zip
Ability to modify .zips
Saves project and project settings
Open working folder
Add busybox
Install curl and openssl
Deodex
Zipalign
Build.prop options
Install aroma
Configure aroma
Open most recent build
Remove current project and files
Add lines to build.prop
Automatically adds project name to build.prop
Automatically adds project name to aroma-config
Build PROJECTNAME
Configure preinstalled aroma
Sign PROJECTNAME
--kitchen options
Added developer options
Added deodexing
Added odexing
Added decompile
Added better backup compression
Added port rom option
Fixed menu issue
Minor code fixes
New icon
Added skip backup in installation
CHANGELOGS FOR OLDER RELEASES
VERSION 7.5-
Program wont install unless device is connected
.iso Image (able to burn to disk)
More Lcd density Options
Fixed menu error
Added compress backup to save space
Hot Reboot option added
Ability to install 'BusyBox'
Ability to install 'cuRL' and 'openSSL'
Get Device Info
AET icon
Uninstall-able
VERSION 6.0-
Fixed All Knows Bugs
Integrated Lcd Density Changer
Fix Permissions
VERSION 5.0-
Manual Adb And Fastboot
Pulls files from server
better compression
Smaller file size
Fixed bugs
Updated sources
Semi-Final build
VERSION 4.5-
Added low battery fix
Fixed Big
Fixed 'Choose device' Menu
VERSION 4.0-
Title Change
Fixed sources
Updated adb
Updated AdbWinApi.dll
Updated AdbWinUsbApi.dll
Updated fastboot
Added backup
Added restore
Added super CID
Added colour logcat
Fixed bug
VERSION 3.0-
Fixed all bugs, added advanced wipe options,
automatically kills adb server upon completion of a task
VERSION 2.5-
Fixed allmost all bugs, Added 'GraffStyleZ' TWRP Theme By Me!
VERSION 2-
Support for all HTC Devices and minor bug fixes
VERSION 1-
Initial release[As Alpha], only support for HTC Sensation XL
If You Like This Tool And Want Me To Continue My Learning And Development, Hit The Thanks Or Donate To Me Providing Better Hardware For Better Tools, Roms and Mods!
Credits:
Special-TRoP0niCZ - Teaching me how to create roms, tools, and mods
RunnyCM Team (anders3408, Lexmazter and Zasuk)
Prof Peach
Cybervibin
ChainsDD
And Many Other For Allowing Me To Use There Creations But Unfortunately Were Not Used In My Tool!
XDAevDB Information
Rickys rom kitchen and android everything tool, a universal way to do everything in one package
Contributors
Ricky310711
Version Information
Status: Stable
Current Stable Version: RRK 2.0 AET 10.0
Stable Release Date: 16/10/2013
Created 12/02/2013
Last Updated 16/10/2013
Follow me on Twitter or Facebook to receive news about my developments first!
Any chance for S-Off for the HTC One S in here? Or just the Sensation?
Closed Source Project said:
Any chance for S-Off for the HTC One S in here? Or just the Sensation?
Click to expand...
Click to collapse
If You Can Link Me To The S-OFF Hboot I Will Modify This Tool For HTC One S! i heard there is facepalm s-off for your device, link me to the thread and ill see what i can do!
Closed Source Project said:
Any chance for S-Off for the HTC One S in here? Or just the Sensation?
Click to expand...
Click to collapse
This won't have S-Off or the better looking AIO Toolkit(sorry) would have it. The dev asked not to do such a thing.
ricky310711 said:
If You Can Link Me To The S-OFF Hboot I Will Modify This Tool For HTC One S! i heard there is facepalm s-off for your device, link me to the thread and ill see what i can do!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2155135 but then
Lastly, the work herein should not be stolen, repackaged, one clicked, bat’d, etc. soffbin3 is not GPL and may not be reused, integrated into other work, reposted, or redistributed without our permission.
Click to expand...
Click to collapse
Darknites said:
This won't have S-Off or the better looking AIO Toolkit(sorry) would have it. The dev asked not to do such a thing.
Click to expand...
Click to collapse
That Explains, i just already pm the facepalm dev to see if i could, i guess ill know the answer then
But if theres any suggestions someone would like me to add to v3 please pm me
cat2115 said:
http://forum.xda-developers.com/showthread.php?t=2155135
Click to expand...
Click to collapse
sorry cat2115: im afraid i cant publish a v3 without permisions to publish with facepalm unless i get permissions!
ricky310711 said:
That Explains, i just already pm the facepalm dev to see if i could, i guess ill know the answer then
But if theres any suggestions someone would like me to add to v3 please pm me
Click to expand...
Click to collapse
Ya I think its a bit lame but guess they just don't want to deal with it or what ever.
Be wary of this... I followed the instructions TO THE T yet I believe this flashed a recovery to my phone that was not from the HoS. I had to Ruu to stock to fix it. Suppose I could have done something wrong... but nonetheless. Also, when I tried doing the recovery it opened my docs... I put the .img in there and then it said I needed to put it in ETv2/prog/zo so I did so and that's when bootloader froze up on me.
Re: [TOOL] HTC Everything Tool!
Fastboot is programmed to execute 'fastboot flash recovery recovery.img' it flashes it the only way you can via pc, although I will look into the problem and see if its on the software side!
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Daiskei said:
Be wary of this... I followed the instructions TO THE T yet I believe this flashed a recovery to my phone that was not from the HoS. I had to Ruu to stock to fix it. Suppose I could have done something wrong... but nonetheless. Also, when I tried doing the recovery it opened my docs... I put the .img in there and then it said I needed to put it in ETv2/prog/zo so I did so and that's when bootloader froze up on me.
Click to expand...
Click to collapse
Uh i think u just got a bad flash. it happens once in a while. Happened to me a few months ago. Had to RUU back to stock before flashing anything cuz fastboot commands wouldn't work. and i do everything by hand. not a fan of tools.
blackhartct said:
Uh i think u just got a bad flash. it happens once in a while. Happened to me a few months ago. Had to RUU back to stock before flashing anything cuz fastboot commands wouldn't work. and i do everything by hand. not a fan of tools.
Click to expand...
Click to collapse
Ive checked over the batch file, there seems to be no problem, i also just flashed twrp on a friends phone and was successfull, maybe it was a bad flash!
ricky310711 said:
Ive checked over the batch file, there seems to be no problem, i also just flashed twrp on a friends phone and was successfull, maybe it was a bad flash!
Click to expand...
Click to collapse
Yeah, that must be it. No worries guys, like I said... I got it back. ^_~ I was just really scared thinking I screwed up the recovery partition or something because flashing the recoveries manually did nothing and when I tried to boot to recovery it would just go to a black screen. At that point I was unsure how to re-lock the phone without the recovery to flash my bootloader lock zip so I tried fastboot oem lock and though it gave me an error I saw that it was now "Relocked" and I was like.. "Oh crap, please RUU back to stock with stock recovery... PLEASE!" XD
Re: [TOOL] HTC Everything Tool!
Well glad it worked, I just flashed twrp recovery and everything went well, although I found minor hugs and fixed them, updating my tool to v2.5
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Tool Updated to 3.0
Could you add S-Off support for the HTC ONE S?
lejohn said:
Could you add S-Off support for the HTC ONE S?
Click to expand...
Click to collapse
i am sorry, i wanted to but i do not have permission to publish tool with facepalm sorry
ricky310711 said:
i am sorry, i wanted to but i do not have permission to publish tool with facepalm sorry
Click to expand...
Click to collapse
Sorry to hear that. SuperCID looks a bit complicated. Pushing the files and rooting must be do-able.
Look like I'll have to wait a bit more then.
Thanks for the reply.
lejohn said:
Sorry to hear that. SuperCID looks a bit complicated. Pushing the files and rooting must be do-able.
Look like I'll have to wait a bit more then.
Thanks for the reply.
Click to expand...
Click to collapse
cant you 'fastboot oem writecid 11111111' in cmd or terminal?
ricky310711 said:
cant you 'fastboot oem writecid 11111111' in cmd or terminal?
Click to expand...
Click to collapse
also a write cid option in v3.5 or v4.0

[ROM][STOCK][FLASHABLE ZIP][JB.1.2][BELL SGH-I757M ONLY] Samsung Stock Rom

STOCK ROM JB 4.1.2 FOR BELL CANADA SGH-I757M (FLASHABLE ZIP)
*** NEW AROMA INSTALLER FOR STOCK JB 4.1.2 ***
***************************************************************************
WARNING
***************************************************************************
I assume no responsibility in the event you brick your device. Make sure you have read the instructions before flashing as they may slightly differ from what your used to.​
Click to expand...
Click to collapse
About This ROM:
Hey guys, so Samsung has finally released JB 4.1.2 for the Bell Canada SGH-I757M, which is currently only available through the sammobile.com website and through Samsung KIES. The download zip contains a tar.md5 file and includes a 3e Recovery partition. That's bad news for those of you with a custom recovery. It will be overwritten and you'll have to go through flashing your custom recovery partition again.
So I bring you a Stock Flashable zip that won't replace your custom recovery. That way you can try the new stock rom without loosing root or your custom recovery.
The only credit I assume here is putting the zip package together which involved using @dsixda Kitchen (thanks dsixda). I also added root to this package so that you can have a fully rooted Stock Rom.
Click to expand...
Click to collapse
Images:
{
"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
Instructions:
*** MAKE SURE YOUR BATTERY IS AT LEAST 75% OR MORE BEFORE FLASHING ***
Before you flash this ROM, you will need a custom recovery installed. I recommend Philz touch recovery found here:
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
*** UPDATED: July 31, 2013 v3 - See second post for changes ***
Those of you looking for a flashable zip for rooting that works with the tar.md5 JB rom from sammobile.com, use this one:
CWM-SuperSU-v0.99.zip - I did not put this package together, it was given to my be another member, but it worked when others did not.New Instructions (Aroma Installer):
Instructions for the Aroma Installer version is extremely simple, there is no need to wipe data/format cache/format dalvik-cache as the Installer will take care of that for you if you want it to.
*** ALWAYS REMEMBER TO TAKE A NANDROID AND ALL YOUR NECESSARY BACKUPS BEFORE FLASHING ***
The one zip file contains all of the modems (ICS & JB), the new playstore app (install optional) and all mods. Just download the zip file and flash it like you would any other ROM, then you will be taken through a series of installer screens that will allow you to choose which apps, mods and modems you want to install.
Download:
Aroma Installer for Stock JB 4.1.2 from Samsung v3 - 794.9MB
New Instructions (Aroma Installer):
Instructions for the Aroma Installer version is extremely simple, there is no need to wipe data/format cache/format dalvik-cache as the Installer will take care of that for you if you want it to.
*** ALWAYS REMEMBER TO TAKE A NANDROID AND ALL YOUR NECESSARY BACKUPS BEFORE FLASHING ***
The one zip file contains all of the modems (ICS & JB), the new playstore app (install optional) and all mods. Just download the zip file and flash it like you would any other ROM, then you will be taken through a series of installer screens that will allow you to choose which apps, mods and modems you want to install.
Download:
Aroma Installer for Stock JB 4.1.2 from Samsung v3 - 794.9MB
Click to expand...
Click to collapse
*** For change log, tips and tricks and FAQ, please go to the second post ***
ENJOY!!!
Change Log
*** UPDATED: July 31, 2013 v3 ***
-Aroma Installer now used for flashing
- Option to do a clean install. Will format your /system, /data, /cache and /preload partitions, no need to factory reset before flashing.
- All modem firmwares included with installer
- Option for rooted/non-rooted install
- Option to install the new Google Play Store app
- All mods are included with installer (install optional)
- All stock apps included with installer (install optional)
- Some stock apps placed in /preload/system/app to save space on the /system partition
- Some Google apps placed in /data/app to save space and for easy deletion
Duplicate build.prop entries removed
- All apps are current as of this release
- Additional utility apps included with installer (install optional)
- Install only the mods and apps you want
*** UPDATED: May 12, 2013 v2 ***
- Full Stock/Debloated Stock
- De-Odexed
- All system apps now located in /system/app
- Unsecured Kernel (allows adb to run in root mode)
- su binary and supersu.apk installed for root permission
- Busy Box shell for installed for better control via a terminal emulator (terminal emulator not included yet)
- Busy Box run-parts (init.d) support enabled to allow for running custom shell scripts at boot
Tips and Tricks (This should no longer be needed if your using the Aroma Installer)
The tips and tricks for this phone have been graciously contributed by xda member @rukusx7. Please press the thanks button on his post if it helped you out:
rukusx7's tweaks to improve device performance.
MODS
Extended Power Menu MOD
To apply the Extended Power Menu MOD, download the following zip to your sdcard as it needs to be flashed from CWM:
MOD_SGH-I757M_STOCK_JB_EXTENDED_POWER_MENU.zip (19.6MB)
1. First take a nandroid backup since we are modifying system files and can easily soft brick our phone by doing this.
2. Flash the MOD from CWM, and restart your phone.
Please be aware that the phone doesn't like to start up for the first time after you flash this mod, you will get stuck at the bootloader screen (not sure why). This is easily overcome by pressing and holding your power button for a hard reset (Hold it for about 10 to 15 seconds. You will feel it vibrate). It should then get past the boot screen. If that did not get you past the boot screen, restore your nandroid backup and try again. If the problem still persists. Post a message and I'll see if I can help you out
S-Voice (like apple's SIRI)
Here is a CWM flashable zip that will install the Galaxy S4's S-Voice onto your SGH-I757M. S-Voice is Samsung's SIRI clone. It seems to work fairly well so far. Just a little slow at times. Just download this zip to your sdcard, make a nandroid backup, and flash this zip. This will install S-Voice on your device. (It may force close on you a couple of times when you first open it up. Just keep opening it up until the force closes stop).
SGH-I757M-SVoice-MOD (62.4MB)
Thanks to @cabetoguerra for finding this leaked apk. Other files and libs were gathered by me and mostly found from a zip file created by xda member zoot1.
FAQ
Q. After I flash the Rom, I get FC's (force closes) like crazy, and I'm gonna pull my hair out!
A. If you did not expressly follow the instructions above, go back and read them. You must format the system, cache and data partitions manually in addition to the regular method.
If you did read and follow the instructions and are still getting FC's. Try the whole process over again and flash the Rom twice just to make sure it fully flashed and all the scripts ran successfully.
Thanks to @4runner10 for actually having to try this
Q. I'm on a Telus network and I get no data connection.
A. Check out this post: http://forum.xda-developers.com/showthread.php?t=1987678 for Telus APN settings as they differ from Bell APN settings.
Thanks to @rukusx7 for the tip
*** reserved ***
Download doesn't work.... Requests permission even when logged in
Sent from my SGH-I757M using Tapatalk 2
dmeinder said:
Download doesn't work.... Requests permission even when logged in
Sent from my SGH-I757M using Tapatalk 2
Click to expand...
Click to collapse
I do apologize, I forgot to allow access to it.... it should be fixed now.
Sent from my SGH-I757M using xda premium
is possible root it room?
shadow404040 said:
is possible root it room?
Click to expand...
Click to collapse
It's already rooted
Sent from my SGH-I757M using xda premium
i update for kies is diponible.
please send me the tutorial for rooted and files
thanks
shadow404040 said:
i update for kies is diponible.
pleasThanks to jonnyb for providing me the e send me the tutorial for rooted and files
thanks
Click to expand...
Click to collapse
Use dsixda's tutorial for Clockworkmod here:
http://forum.xda-developers.com/showthread.php?p=27326599
Then download and flash this zip file (not mine):
http://bit.my/13IiJRT
which pushes su and superuser.apk to your phone. Then your root
Sent from my SGH-I757M using xda premium
first time I flashed the rom (followed instructions), was getting FC's during initial setup. i'm going to try a clean install again.
4runner10 said:
first time I flashed the rom (followed instructions), was getting FC's during initial setup. i'm going to try a clean install again.
Click to expand...
Click to collapse
Did you format the partitions as described in the instructions? I was having that same issue until I formatted the partitions.
Sent from my SGH-I757M using xda premium
Maybe try flashing twice just to be sure
Sent from my SGH-I757M using xda premium
BTW thanks a ton for doing this man. looking forward to seeing the stock jb
---------- Post added at 01:53 AM ---------- Previous post was at 01:52 AM ----------
titanic_fanatic said:
Maybe try flashing twice just to be sure
Sent from my SGH-I757M using xda premium
Click to expand...
Click to collapse
yeah, i always used to flash the rom twice but didn't bother this time. might want to mod the instructions! that did the trick, i also wiped the dalvik after the rom and modem were flashed. no idea if that would make a diff tho!
seems pretty smooth during setup!
4runner10 said:
BTW thanks a ton for doing this man. looking forward to seeing the stock jb
---------- Post added at 01:53 AM ---------- Previous post was at 01:52 AM ----------
yeah, i always used to flash the rom twice but didn't bother this time. might want to mod the instructions! that did the trick, i also wiped the dalvik after the rom and modem were flashed. no idea if that would make a diff tho!
seems pretty smooth during setup!
Click to expand...
Click to collapse
Wicked I'll add that right now. Thanks for the feedback
Sent from my SGH-I757M using xda premium
Hmm. Kept getting fc when trying to open settings. I'm back to dadoes for the time being. Thanks again for your work on this man!
4runner10 said:
Hmm. Kept getting fc when trying to open settings. I'm back to dadoes for the time being. Thanks again for your work on this man!
Click to expand...
Click to collapse
I think it might have to do with the new partition and it's weird symlinks. I'll look into moving these files back into the /system/app folder. Hopefully that will help fix the fc's
Sent from my SGH-I757M using xda premium
Cool man. Glad u know more about this than me! I'll await the next version whenever you get around to it.
thanks titanic_fanatic update and root 4.1.2 thanks thanks
Yay! This is going to be fun. Thanks titanic!
Sent from my SGH-I757M using xda premium
Wow amazing! Thanks very much. Had given up on Samsung creating a stock jb ROM for this phone.
Curious if there will be a de-bloated version soon?
Sent from my SGH-I757M using xda app-developers app

[APP] ROM Installer

{
"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"
}
OVERVIEW
ROM Installer, by JRummy Apps, is the best way to find and install custom ROMs and ZIPs. It is a must have app for any root user.
You will find more ROMs available than any other app on the Google Play Store. It has many of the same features you will find in Goo Manager, ROM Manager, ZipInstaller and other similar products.
Installing ROMs like Android Open Kang Project (AOKP), CyanogenMod, Paranoid Android, Miui and others is easy. Some devices will not show as many ROMs because of the lack of support for that specific device. Please contact your ROM developer to add their ROM to ROM Installer or goo.im
ROM Installer also offers the fastest way to install the most recent recovery. All TWRP recoveries are hosted on our fast server and updated on a constant basis. No other app offers an easier way.
DOWNLOAD ROM
What is a ROM?
A ROM is a modified version of the Android OS. ROMs are often built from the Android Open Source Project (AOSP) with added features. ROM Installer offers many popular ROMs to download for supported devices, including CyanogenMod, Paranoid Android, MIUI and AOKP (Android Open Kang Project). There are countless other ROMs and ZIPs you can install too.
ROM Downloads & Details
When you first open ROM Installer a list of supported device will be loaded. You must have an internet connection to list the most recent ROMs. Wifi is highly recommended when downloading ROMs because they are usually large ZIP files.
When clicking on a ROM in the list you will be presented with the ROM details page. This page offers screenshots, comments, likes, view counts, descriptions, a list of files to download and install and links to the ROM developer’s social media sites.
How To: Download & Install a ROM
1. Download and install ROM Installer from Google Play.
2. Click on the ROM Developer of your choice.
3. Under the ‘Download’ section click the ‘Download’ button from the quickaction menu.
4. The file will be downloaded in a background service and notify you when completed.
5. Once the download is complete, click the notification and it will open a new ROM Install activity.
6. In the ROM Installer select the option to wipe and backup your current ROM (optional but suggested).
7. Click install and confirm to reboot your device into recovery mode.
Tips and Tricks:
Before installing a ROM you should always know how to ‘unbrick’ your device incase anything should go wrong. Installing custom operating systems can be dangerous and rooting most likely voids your warranty. JRummy Apps Inc. claims no responsibility for any damaged or ‘bricked’ devices, loss of data or any other damage that could come from installing third party operating systems.
Always remember to have a current backup and keep your apps and data backed up. Forum members at websites like XDA-Developers or RootzWiki are helpful tools when you have questions about flashing a new ROM or ZIP.
BACKUP & RESTORE
What is a nandroid backup?
A Nandroid backup is a backup of your entire Android system saved to your SDcard. Due to the possibility of anything going wrong when changing aspects of the Android system, we highly recommend that you have a current Nandroid Backup. By having a current Nandroid backup you can manually restore your device through recovery.
How To: Create a Nandroid Backup
1. Download and install ROM Installer from Google Play.
2. Click menu -> Create Backup
3. Enter the desired name of the backup (no spaces allowed)
4. Click ‘OK’ and then confirm to reboot into recovery mode.
How To: Restore a Nandroid Backup
1. Download and install ROM Installer from Google Play.
2. Slide from left to right to open the sliding drawer.
3. Click ‘BACKUP & RESTORE’
4. Select the backup you want to manage or restore
5. Click ‘Restore’ and then confirm to reboot into recovery mode.
How To: Extract Files from a Nandroid
1. Download and install ROM Installer from Google Play.
2. Slide from left to right to open the sliding drawer.
3. Click ‘BACKUP & RESTORE’
4. Select the backup you want to manage or restore
5. Click ‘Extract’ and then select which tar file you would like work with.
6. You will see two tabs (Files, Apps). You can extract and restore app data and files from previous backups.
Tips and Tricks:
ROM Installer supports both TWRP and CWMR backups. You need to have the correct recovery installed to restore a backup (TWRP backups cannot be restored in CWMR). If you update your recovery manually don’t forget to update the recovery settings in ROM Installer.
Upgrading ROM Installer enabled the ‘Extract’ feature. This can be used to restore apps and old system files quickly. More features and planned in this section for the future.
Things You Should Know:
Creating a backup requires you to install a custom recovery. ROM Installer supports TWRP and CWM recovery. Please read more about recoveries in the ‘FLASH RECOVERY’ section.
FLASH RECOVERY
Things You Should Know:
After rooting your Android device, installing a recovery is the most important next step. What is recovery? In Android, recovery refers to the dedicated, bootable partition that has the recovery console installed. A custom recovery offers much more than the default recovery that comes pre-installed on your device. It allows you to install custom ROMs, wipe partitions and restore your phone when ‘soft bricked’. Before rooting and changing anything you should become familiar with a custom recovery.
ROM Installer goes to great lengths to get you the most recent recovery for your device. It has thousands of recoveries hosted on our fast servers to meet your rooting needs. ROM Installer is the easiest way to install your favorite custom recovery.
How To: Install a Custom Recovery
1. Download and install ROM Installer from Google Play.
2. Slide from left to right to open the sliding drawer.
3. Click ‘FLASH RECOVERY’. A list of supported recoveries for your device will be listed.
4. Select the recovery of your choice and click ‘Yes’ to confirm your install.
5. The recovery will download to your SDcard and be installed.
6. To reboot into recovery mode you can click the menu -> Reboot Recovery.
Supported Recoveries:
Team Win Recovery Project (TWRP)
We recommend that you use Team Win Recovery (TWRP). TWRP will allow you to easily install any ROM using ROM Installer. TWRP is a custom recovery built with ease of use and customization in mind. TWRP is built off AOSP recovery and has the standard recovery options and much more. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Clockworkmod Recovery (CWMR)
ClockworkMod Recovery is popular and has been around for years. Unfortunately this developer blocked all other apps from using the official version of ClockworkMod recovery unless ROM Manager Premium is installed on the device. If you choose to use CWMR then ROM Installer needs ROM Manager to install custom ROMs.
After you have selected the recovery you would like to use just tap on it. The recovery will download and install.
ROM INSTALLER
Things You Should Know:
Installing multiple ZIP packages at once has never been easier with ROM Installer. You can drag and drop files to order when each flashable ZIP will be installed. Before your recovery installs any packages, you can choose to backup your current ROM and wipe data and cache partitions.
How To: Install a Custom ROM
1. Download and install ROM Installer from Google Play.
2. Download the ROM and any extra packages (Like GAPPS). Use the ROM list to navigate and install your favorite ROM.
3. Once the ROM download is finished click on the notification to open the ROM Installer
4. Select to backup your current ROM and wipe data and cache if desired/required.
5. Click ‘INSTALL’ and confirm to reboot into recovery mode and install your ROM
ROM PRE-INSTALLATION:
Backup Existing ROM: This will create a backup in your recoveries default backup directory that you can restore later. You can locate your backup in the ‘BACKUP & RESTORE’ section after you install your ROM/ZIPs.
Wipe Data and Cache: This will wipe any apps and data. It is important to backup your apps and data before installing a ROM. You can use ROM Toolbox’s App Manager or another of your favorite backup apps to easily restore app data afterward.
Install Queue: To add ZIP packages to the install queue click on the ‘ADD ZIP’ button. You can either add a flashable ZIP package via a built in file browser or from the files saved in the download database that ROM Installer manages. Once you have added your ZIP packages you can re-order them using the drag and drop feature, slide them to the right or left to remove them from the list and click them to see more information about the file.
Installing ROMs & ZIPs:
The ROM Installation depends on your custom recovery. When you click on the ‘INSTALL’ button (located at the bottom of the screen) it will ask you to confirm to reboot into recovery and install the ZIP package.
If you are using an officially built version of ClockworkMod recovery then ROM Manager is needed to install a single ZIP package. If you want to install multiple ZIP packages and also use the official version of CWMR then ROM Manager Premium also needs to be installed in order for ROM Installer to work correctly in recovery mode.
ROM UPDATES
Receiving notifications for ROM updates:
Installing the latest build of your ROM can become exciting and addicting to see the new features. The ROM Update service provided in ROM Installer checks for new ROMs on goo.im and the individual developer’s server (if enabled).
How To: Enable ROM Notifications
1. Download and install ROM Installer from Google Play.
2. Open the sliding drawer and select ‘ROM UPDATES’
3. Select the time interval (from the dropdown menu) and the time of day to run the service.
4. Make sure the Switch is set to ‘ON’
5. If an update is available you will see a notification in your app drawer. Clicking on the notification will start a new activity to download the ZIP from ROM Installer or goo.im.
GOO MANAGER
GOO Manager Features:
- Browse compatible ROMs and ZIPs for your device
- Browse and search any file hosted by hundreds of developers
- Sponsor login for faster downloads
- ROM Installer for downloaded flashable ZIPs
- Download thelatest Google Apps (GAPPS) hosted on goo.im
- Installe the latest recovery by Open Recovery hosted on goo.im
- Receive update notifications when goo.im developers add new ROMs
Things You Should Know:
The website, goo.im, is a popular hosting site for ROM developers. The Goo Manager built into ROM Installer offers all the features found in the official app from goo.im. Many of the ROMs available in ROM Installer are hosted on goo.im. For faster downloads you can donate to goo.im to get instant downloads instead of waiting 10 seconds. Donations to goo.im do not support JRummy Apps Inc.
If you would like to have direct access to the Goo Manager from your launcher you can enable this feature in ROM Installer Settings.
THANK YOU
Thank you Android family for supporting my work! If you have questions or concerns please email me at [email protected]
JOIN THE BETA TESTING GROUP ON GOOGLE+
RESERVED
Reserved thanks
Sent from my GT-I9100 using Tapatalk 4
Looks like another great app from JRummy Apps Inc. Rom Installer, Busy Box Pro, Rom Tool Box Pro, and Root browser...what else would anyone need?? Great Job @jrummy16 and team!
jayjay3333 said:
Looks like another great app from JRummy Apps Inc. Rom Installer, Busy Box Pro, Rom Tool Box Pro, and Root browser...what else would anyone need?? Great Job @jrummy16 and team!
Click to expand...
Click to collapse
You forgot zipme!!
does this mean ROM manager in the Toolbox will be no longer updated? thanks
hi,
could you add PA-Google Apps? Because they offer a minimal gapps package as well. For me, i only need a few of the google apps.
Can i only resotre apps+data from nandroid backup? Or is it "advanced restore" -> "data" ?
Does Rom Installer notify me when a new recovery update is released?
1. Just added PA gapps
2. You can extract apps from a nandroid backup. Click on the backup and click extract.
3. Yes, it will notify you of recovery updates.
Sent from my XT1060 using XDA Premium 4 mobile app
jrummy16 said:
1. Just added PA gapps
2. You can extract apps from a nandroid backup. Click on the backup and click extract.
3. Yes, it will notify you of recovery updates.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you! If you could extend the restore functionality by restore multiple apps + data and contacts + SMS/mms.
its the true all in one app for flashing a new rom.
At least for me... but its already a lot of a time saver!
Sent from my Desire S using xda app-developers app
...
Love this app but I get error when trying to back up kernel or recovery. I have a sprint s3 running rooted stock kitkat. anything i can do?
When i click on Flash recovery, it says No available recoveries LGE LG D410 (w7dsn), what can i do ?
i want a custom recovery for my D410HN lollipop 5.0.2, base band M8626A-AAAANAZM-1.0.6063 kernel 3.4.0+ ,next info LRX22G.A1440649755 and V20c-OP1-HQ, thanks in advance any info regarding.
can i install androd 5.1 in my samsung star gts5282 mobile through this roms
Hi
First thanks allot for your efforts
I have question
Could this lovely application used ti fix bricked ace plus gt-s7500?
and how?
Sent from my PC36100 using XDA Free mobile app

[EOL] MultiROM v33(e) for OP3/3T [UNIFIED]

{
"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 one-of-a-kind multi-boot mod for Oneplus 3. 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.​
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is encrypted).
MultiROM has 2 parts you need to install:
Modified recovery - You cand download the unified IMG file here, or specific for OP3 from second post and use fastboot or TWRP or Flashify app to flash it.
MultiROM - download the unified ZIP file here, or specific for OP3 from second post and flash it in recovery.
Go into TWRP MultiRom settings and check "Enable No-KEXEC Workaround"
Your current rom will not be erased by the installation.
Download links for specific OP3 version are in the second post.​
WORKAROUND for FCs
If you get FC's in your secondary, edit build.prop in that secondary's /system dir and set:
Code:
#ro.sys.sdcardfs=true
...to comment the line (don't delete, don't set to false).
Don't boot before editing this line (flash secondary, edit and then boot).
You can edit in your primary if you are rooted, looking into:
Code:
/sdcard/multirom/roms/<your_sec_rom>/system/build.prop
*You can also try using multiromfix.zip, available in this post, thx to @Startrek852 (to disable sdcardfs support in that secondary).
​
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.​
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 MultiROM 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 MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/MR-op3/multirom
Modified TWRP - https://github.com/MR-op3/android_bootable_recovery
MultiROM device tree - https://github.com/MR-op3/device_oneplus_oneplus3​
Thanks a lot to Tasssadar for creating this awesome utility.
And to @nkk71 for the No-KEXEC workaround
MultiROM, Tool/Utility for the OnePlus 3
XDA:DevDB Information
MultiROM OP3/3T, Tool/Utility for the OnePlus 3
Contributors
martinusbe, BitOBSessiOn
Version Information
Status: Alpha
Current Beta Version: 3.0.3-2
Beta Release Date: 2017-02-12
Created 2016-07-10
Last Updated 2019-09-10
Reserved
Downloads
IT WILL NOT WORK WHEN ENCRYPTED
How-To by @bihariel
MultiRom for oneplus3
Recovery 08/03 Fixed usb-otg
multirom-20160814-v33b-UNOFFICIAL-oneplus3.zip
uninstaller
Update 11/26
Recovery 11/26
multirom-20161126-v33e-UNOFFICIAL-oneplus3.zip
Update 02/05/2017 op3
for new firmware 4.0.+, so older roms/kernels will not work on this!
AFH folder here
Update 02/20 by @BitOBSessiOn Unified
In post #1183
Update 03/10 Unified By BitOBSessiOn
recovery https://www.androidfilehost.com/?fid=745425885120713897
mr zip https://www.androidfilehost.com/?fid=817550096634752067
Update 08/07 by BitOBSessiOn
Post #1950
Flashable zip to fix your locksettings can be found here
MR Manager TBO 2016/08/17
Multirom Manager apk with oneplus support
Changelog:
- Darkened UI by @daveyannihilation #WhiteUImustDie
- Added icons for OOS, Tipsy, Tesla, Validus, Slim (needs the new zip flashed)
- Supports all Oneplus devices, Redmi2, Lux unoffically (to use the icons, the MR maintainer will need to update his MR zip)
MR Manager TBO 2017/04/21
Multirom Manager apk with added oneplus3T support
Flash recovery
Flash multirom zip
Enable kexec workaround in TWRP mr settings
Enjoy!
Reserved
Please read all about the no-kexec workaround from the author directly, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
*Updated MultiROM Manager APK available here.
*FCs in secondaries should have been fixed in latest TWRP-MROM versions.
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Hello, MultiRom does not recognize the recovery amends
bihariel said:
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Click to expand...
Click to collapse
Its a first build, give me a minute, i have a family
jejemc said:
Hello, MultiRom does not recognize the recovery amends
Click to expand...
Click to collapse
i know
Great work bro :beer: :good:
Unreal work bro much alohas
And here we are!! Thanks a lot @martinusbe, working like a charm!
Superfast! Many thx! Can´t wait to get my oneplus3
Dope. Nice way to use cm13 if I need dash boot into oxygen OS awesome!!
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
cunc-cam said:
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
Click to expand...
Click to collapse
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
bihariel said:
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Click to expand...
Click to collapse
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
cunc-cam said:
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
Click to expand...
Click to collapse
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
bihariel said:
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
Click to expand...
Click to collapse
Huh. Be sure you checked the custom recovery setting related to kexec, I don't think that is supported on our device. Other than that, I'm as clueless as you
Its checked kexec warkaround. Injected sector boot. When i select secondary to boot, the phone reboots but it always goes back to boot menu... Will investigate a bit more...
touchscreen does not work on boot menu
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
bud77 said:
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
Click to expand...
Click to collapse
does touchscreen working for you?

Dual/Multi Boot On the OnePlus 3T

{
"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"
}
I have looked around and haven't seen anyone mention this so I thought I would post about it. I hope others find this useful. I've used this tool on my Galaxy Note 4 to have two different OS's running (mostly due to bluetooth problems on CM, but I digress). This allows the user to dual boot and maintain safetynet with Magisk. I've used this a lot and was really excited to see that it is compatible with this amazing phone!
The thread that caught my interest on the subject (for Note 4): http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
The original thread quoted by @aukhan (for S4, but most of the discussion is here too): http://forum.xda-developers.com/showthread.php?t=2447534
All credit goes to the original developers for this tool, I had nothing to do with its development. This thread is made to troubleshoot our specific device without clogging up their threads for other devices.
Thanks to @aukhan, @rlorange, @chenxiaolong , and other contributors.
Download the Dual Boot Patcher snapshot apk from here. That is the only app that you should need to complete the process. Click on the latest build link and then click on the android file that ends in "snapshot.apk". The snapshots are the recommended version at the moment.
I made a video walkthrough of this process for the Note 4. A lot of it is similar, but I will try to get a new video up for the OP3T when I have time.
Basically you patch all of the .zip files that you would have flashed normally and then you flash them to a new ROM slot. If there are more questions that the video and my more specific instructions below don't answer I'll be happy to answer them or post a better walkthrough if needed.
It should be noted that to switch back and forth you'll need to install the Dual Boot Patcher apk on both ROMs. This does not affect TWRP Recovery.
So far I've only done this once on the 3T and I haven't had any issues. Obviously the 5 second delay is a little annoying when booting between ROMs, but I can get over that. I currently have RR Official installed as my primary with Open Beta 6 as my secondary. Normally the stock ROM is recommended for the primary boot slot, but this seems to work fine.
More Specific Instructions for recommended Data Slot:
1) Download all .zip files that you would flash if you were going to flash the ROM normally (ex. LOS, Gapps, SuperSu, XPosed, kernels, etc)
2) Download the Dual Boot Patcher apk: https://snapshots.noobdev.io/, install it on your phone, set the kernel, and update the ramdisk (ROMs page, three dots on Primary, scroll to bottom)
3) Open Dual Boot Patcher app and tap the three lines in the upper left then select "Patch Zip File"
4) Tap the plus button and find each of the .zip files that you will be flashing. After selecting one make sure to change "Partition Configuration" to "Data slot" and enter a number (be consistent with each file). Push continue.
5) A file browser will now open. Navigate to the place you'd like to save the file and select the location.
6) You may now repeat steps 4 and 5 to add the rest of the zip files
7) Tap the check mark in the upper right to "Patch" all of the .zip files
8) Tap the three lines in the upper left again and select ROMs
-Installation
--Option 1
9) Tap the phone icon in the lower right and push okay
10) Tap the plus button in the lower right and navigate to where you saved your patched files. Select the main ROM (the ROM you want to dual boot to) and tap "keep location" (this will put all data in the location it specified ie /data/multiboot/data-slot-1 for this case)
11) Repeat step 10 until all zips are added in the order you want them flashed (the order is important so get your ROM before your Gapps etc). If you mess up swipe the one that's in the wrong order to the right to remove it from the list
12) Tap the check mark in the upper right. A console should appear and it should virtually flash the ROM as you would expect in TWRP
13) Once it says "x/x completed" in cyan text and it has stopped you can just tap the back arrow in the upper left
14) If you go back to the ROMs page there should now be a "Secondary" ROM. To test it out you'll need to select it and then reboot the phone.
15) Once it has booted and you are past the setup you'll need to enable "unknown sources" in the menu and install Dual Boot Patcher. Once it's installed, open it. It should find the two ROMs and you'll be able to select Primary from the ROMs menu and reboot back
--Option 2 (best if your ROM doesn't report your device name like RR)
9) After patching the files reboot into TWRP
10) Flash the patched files like you would normally flash a ROM (order is important so flash the ROM before Gapps, su, etc)
11) Once the process has completed reboot into system
12) Since you haven't selected the secondary ROM at this point it should boot to your primary ROM (although I can't remember at the moment). Open Dual Boot Patcher, select the ROMs page, select the secondary ROM, and reboot your phone
13) It should reboot to your newly installed ROM where you can set it up and install DBP to boot back between ROMs.
This process can be done using any of the partition configurations listed when patching a Zip file. Secondary and Multi Slots go to the System partition and data slot goes to internal storage. I recommend not using the Multi Slots since more than two ROMs is a lot on the system partition. I would recommend the data slots.
If you have problems make sure to set the kernel and update the ramdisk before flashing
In the event of a bootloop you can recover your primary ROM by entering TWRP, tapping install, selecting image in the bottom right corner, navigating to the /sdcard/MultiBoot/primary folder, and selecting the "boot.img" file. This will return your phone back to the primary ROM.
There is a multiboot.log file that is very useful for debugging. Please post it if you have issues (found in the /sdcard folder)
If you later want to flash anything to the ROM that you're "dual booting" into then all you have to do is patch the zip files and flash them like before except you're flashing to a slot that already has a ROM now.
Tasker Integration
I've been using RR as my daily driver, but the BT doesn't work in my car. I did a lot of research to enable ROM switching in Tasker so that I could easily switch over ROMs when I get into my car. I use my android watch to trigger the task into my OOS ROM and then when BT disconnects I have it trigger a task to switch back to RR. Here it is:
Add action>system>send intent
Under "Action" enter
Code:
com.github.chenxiaolong.dualbootpatcher.SWITCH_ROM
Under "Cat": Default
Under the first "Extra" enter
Code:
rom_id:primary
(change primary to dual or whatever your other slot name is)
Under the second "Extra" enter
Code:
reboot:true
(this tells the app to reboot right after switching the ROM to the desired one)
Under "Target": Activity
I have found that the intent will trigger if the phone is locked, but won't do anything until the phone is unlocked. With swipe or smart lock enabled you can use secure settings to wake the screen and then run a shell with root to swipe up on the lock screen (Command: "input swipe X1 Y1 X2 Y2" replace the X's and Y's with numbers for your screen. Use developer settings to figure out where the start and stop should be.)
All of this allows me to trigger a ROM switch and reboot from my watch without taking my phone out of my pocket (i.e. while driving).
Backup/Restore/Move ROMs from/to specified slots
chenxiaolong said:
Wow, a lot has happened since my midterms started Once midterms are over, I'll start replying to posts here again (starting from around page 731 when I last posted).
I haven't been doing absolutely nothing over the past couple weeks though! We now have a very basic backup and restore implementation. This is still very much a work-in-progress and currently has no UI (nor does it work outside of recovery mode). But anyway, I figured some people who love bleeding edge stuff will want to give this a try. (And yes, backing up one slot and restoring to another already works!)
Like the installer, DualBootUtilities, and pretty much everything multiboot-related, backup and restore is handled by mbtool. I've compiled debug versions here with the new backup & restore features: https://snapshots.noobdev.io/misc/mbtool/mbtool_recovery_8.0.0.r1855.gfeb767e_DEBUG.tar.xz EDIT: Extract "mbtool_recovery" from the PC zip (easier) or from assets/data-8.0.0-rVERSION.tar.xz in the apk.
To give this a try, you'll want make sure your adb command is set up properly and reboot into recovery. Then you'll need to copy the appropriate mbtool_recovery binary to /tmp/:
Code:
# For 32-bit ARM devices
adb push armeabi-v7a/mbtool_recovery /tmp/
# For 64-bit ARM devices
adb push arm64-v8a/mbtool_recovery /tmp/
# For x86/x86_64 Intel devices, you guys probably already know what you're doing
Then, make sure /system is mounted because TWRP does not mount it by default.
Code:
adb shell mount /system
Now, to backup a ROM, run, for example (to backup extsd-slot-cm to a backup named "my_backup_name"):
EDIT: One thing to note because the tool doesn't detect this yet. If you want to backup the primary ROM, make sure to do a ramdisk update from the app first. Otherwise, the kernel will not have any multiboot code and won't boot if you decide to restore it to another slot.
Code:
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery backup -r extsd-slot-cm -n my_backup_name
To restore a ROM, run, for example (to restore "my_backup_name" to multi-slot-1):
Code:
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery restore -r multi-slot-1 -n my_backup_name
If you want to do partial backups (say, backing up the data and kernel only), you can add "-t data,boot" to the command. For more command arguments, see:
Code:
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery backup --help
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery restore --help
I expect there to be a lot of bugs, so feel free to blame me or yell at me for whatever issues you run into
Click to expand...
Click to collapse
Edit: Turns out I didn't look hard enough. There is a thread that has already been created to discuss this tool on this wonderful phone and it fixes an issue where some ROMs with 3/3T support won't flash in dual-boot.
I erroneously did the upgrade ramdisk on my 3t with OxygenOS and now phone is not booting anymore (5 vibration and then recovery)... Someone can help me in understanding what I can do to solve it?
mar.ste said:
I erroneously did the upgrade ramdisk on my 3t with OxygenOS and now phone is not booting anymore (5 vibration and then recovery)... Someone can help me in understanding what I can do to solve it?
Click to expand...
Click to collapse
It has been awhile since I've played with DBP, but I seem to recall that it stores a copy of the boot image before the ramdisk update that you can flash

Categories

Resources