Database Info

[ROM][PORT]Kalawakan Rom v2.9[UPDATE][4.1.2]

CLOUDFONE EXCITE 501D CUSTOM ROM
Android Jellybean [4.1.2]
- Pre-rooted
- 60 Framerate per second
- Good for gamers
- Smooth UI
- Full S4 UI
- S4 Launcher
- S4 Weather Widget
- S4 Status Bar
- S4 Font ( Rosemary )
- JMP TWEAKS
- SECRET RECIPE FOR GAMERS
- Very Smooth on lite games like (temple run, angry birds, fruit ninja, plants vs zombies 2, etc)
NEW TO VERSION 2.9:
- INIT.D SUPPORT
- REMOVE THOSE USELESS WEATHER APP AND WIDGETS
- REMOVE USELESS LIVE WALLPAPER
- DEBLOATED
- ZIPALIGNED
- BUILT-IN VIPER4ANDROID
-ADDED X-REALITY ENGINE
-ADDED NEW PATCH
-ADDED ALBUM AND PHOTO EDITOR IN ORDER TO CHANGE LOCKSCREEN WALLPAPER
-IMPROVE GPS LOCKTIME
-LESSER FC'S ON SOME HEAVY APPS AND GAMES
-MORE STABLE
-ADDED XPOSED INSTALLER
-ADDED BUILD.PROP TWEAKS​
XDA:DevDB Information
Kalawakan v2.9, ROM for all devices (see above for details)
Contributors
flarestar123, Leingod0923
ROM OS Version: 4.1.x Jelly Bean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 4.1.1-4.1.2
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 2.9
Stable Release Date: 2014-11-01
Created 2014-10-31
Last Updated 2014-11-04

CREDITS:
http://forum.xda-developers.com/showthread.php?t=2025391 @jigarmpattani
Thank him for I use his ROM from the very base
http://forum.xda-developers.com/showthread.php?t=2191223 @zhuhang
Thank him for his amazing viper4android
Rymoj Serolf
Ronald Hipz Pajal
Jaymar Dela Cruz
Yconne Libot
Shine Lee
Charliemae de Castro
Andre Aggasid
MyPhone A848i Family
Chinese Developers
Myphone PH Developers *OFFICIAL AND UNOFFICIAL DEVS*
Micromax XDA Developers
PROCEDURE TO FLASH THE ROM
1. WIPE DATA
2. WIPE CACHE PARTITION
3. WIPE DALVIK CACHE IN ADVANCE
4. GO TO MOUNT AND STORAGE AND FORMAT SYSTEM
5. INSTALL ZIP FROM SD CARD
6. REBOOT SYSTEM NOW
7. FINISH THE SET UP
8. OPEN VIPER4ANDROID AND INSTALL ITS DRIVER
9. OPEN XPOSED AND INSTALL ITS FRAMEWORK
10. REBOOT
FOR FLASHING THE PATCH
1. PLACE THE PATCH TO SD CARD
2. INSTALL THE ZIP FROM SD CARD
3. REBOOT SYSTEM NOW

SCREENSHOTS: https://www.facebook.com/media/set/?set=oa.517481885003841&type=1
{
"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"
}
DON'T BE A SILENT DOWNLOADER HIT THANKS IF YOU LIKED MY WORK :good:​DOWNLOAD LINK:​ROM LINK: http://www.mediafire.com/download/d45gacsl1w3eb1c/Kalawakan_Rom_v2.9.zip
NEW! PATCH LINK: http://d-h.st/FIR
NOTE: IF YOU WANT TO PORT TO ANOTHER DEVICE PLEASE ASK PERMISSION ​

Re-partitioning and add on section
CLOUDFONE 501D REPARTION
Procedure:
BACKUP! BACKUP! BACKUP!
1. Go to CWM/TWRP Recovery
2. Install zip from sdcard >> then choose zip from sdcard
3. Flash "desired repartition" when it's complete
4. Choose "go back" then "wipe data/factory reset, wipe cache and in advanced wipe dalvik cache"
5. Flash again "desired repartition"
6. Go back >> go to advanced >> reboot to recovery
7. Wipe data/ factory reset and wipe cache
8. Flash your "DESIRED ROM" and then reboot
***I do not own this work, this is just a repost***
Credits to: Archie Shinshan
Steven Sombremesana
DOWNLOAD LINK:
2.5gb internal and 55mb
DIRECT LINK: http://www.4shared.com/zip/OC0trpH5/A919_Data_Repartition_25GB_int.html
MIRROR LINK: https://docs.google.com/file/d/0BwE0fpvujMnSRUdxY1huellQM28/edit?pli=1
1.5gb internal and 1gb sd card
DIRECT LINK: http://www.4shared.com/zip/a0IE1Fxc/A919_Data_Repartition_15gb_int.html

Finished uploading
download links are now available enjoy!

The CWM mod for my 501D does not seem to work as rebooting into recovery mode freezes the phone into the "cloudfone" booting image. And it also does the same thing when I try to boot into recovery mode. Is there a way to flash your custom rom to the phone with the use of a software? Thanks.

lhites said:
The CWM mod for my 501D does not seem to work as rebooting into recovery mode freezes the phone into the "cloudfone" booting image. And it also does the same thing when I try to boot into recovery mode. Is there a way to flash your custom rom to the phone with the use of a software? Thanks.
Click to expand...
Click to collapse
Please repeat the steps here in installing CWM in our phones: http://www.symbianize.com/showthread.php?t=1136946
Because it is better to have a CWM working so that you can also flash my repartition tutorials.

flarestar123 said:
Please repeat the steps here in installing CWM in our phones: http://www.symbianize.com/showthread.php?t=1136946
Because it is better to have a CWM working so that you can also flash my repartition tutorials.
Click to expand...
Click to collapse
I am sorry. But I already did follow the thread you were referring to before I requested/posted for some help. I have read about Flashify, can I use it instead to flash your custom rom? (http://forum.xda-developers.com/showthread.php?t=2798257) Or can I go ahead with Magic TWRP rather than CWM (since it does not work on mine). And then just use Magic TWRP to flash your custom rom? Agyamanak

lhites said:
I am sorry. But I already did follow the thread you were referring to before I requested/posted for some help.
I have read about Flashify, can I use it instead to flash your custom rom? (http://forum.xda-developers.com/showthread.php?t=2798257)
Agyaman
Click to expand...
Click to collapse
I really recommend you use carliv or cwm recovery because if something goes wrong you can still recover your bricked phone. But if you use flashify then you got an error while flashing the rom. Then dont blame me if you brick your phone thus you cant anymore flash a stock rom to repair it cause you dont have a working CWM. If I have the ability to install a cwm in my phone so you can cause we have the same phone.

flarestar123 said:
I really recommend you use carliv or cwm recovery because if something goes wrong you can still recover your bricked phone. But if you use flashify then you got an error while flashing the rom. Then dont blame me if you brick your phone thus you cant anymore flash a stock rom to repair it cause you dont have a working CWM. If I have the ability to install a cwm in my phone so you can cause we have the same phone.
Click to expand...
Click to collapse
Thank you. I know I can't just blame anyone except myself if I brick my 501D phone. That much I already know. But your suggestion did not work on my android phone (since I already went through it many times without success). Have you tried Magic TWRP? Or some other way of having a custom recovery? If not, then all I can do is be patient with my buggy phone

lhites said:
Thank you. I know I can't just blame anyone except myself if I brick my 501D phone. That much I already know. But your suggestion did not work on my android phone (since I already went through it many times without success). Have you tried Magic TWRP? Or some other way of having a custom recovery? If not, then all I can do is be patient with my buggy phone
Click to expand...
Click to collapse
You can follow an alternative step in installing CWM recovery on our phone: http://forum.xda-developers.com/showthread.php?t=2519432

Okay thanks. Will try this and let you know how it goes. Wish me luck

Good news! Flashify was able to successfully flash CWM Having gone into CWM recovery mode, CWM reported a "bad" rom while attempting to flash your custom rom. Will download another copy of your rom when I am on a faster connection. Thank you for all your help.

lhites said:
Good news! Flashify was able to successfully flash CWM Having gone into CWM recovery mode, CWM reported a "bad" rom while attempting to flash your custom rom. Will download another copy of your rom when I am on a faster connection. Thank you for all your help.
Click to expand...
Click to collapse
Okay thats great because I am planning to upload a new custom rom for our phone.

Then I'll wait for your new custom rom just flashed the deodexed stock rom two days ago, will use it for the meantime.

I was able to flash the kalawakan rom unfortunately I did not like it. So I went back to the stock deodexed rom. flashing the backup via cwm did not work either. I had to flash the rom from start. FYI.

My cloudfone 501D shuts off intermittently without any warning. I thought that reflashing will solve the problem. Do you have any ideas on how to solve this problem? Thanks in advance.

nice
nice

Ask lng po .
Pwede po bang iflash na yan kahit naka kalawakan rom v2 lng po ako? o kailngan pang ibalik sastockrom ng cloudfone 501d ?

erisjean said:
Pwede po bang iflash na yan kahit naka kalawakan rom v2 lng po ako? o kailngan pang ibalik sastockrom ng cloudfone 501d ?
Click to expand...
Click to collapse
Just do the proper wiping to avoid any conflicts and YES you can flash it eventhough you are already at Kalawakan Rom v2
Siong05 said:
nice
Click to expand...
Click to collapse
It would be nicer if you can wait for the lollipop theme rom
lhites said:
My cloudfone 501D shuts off intermittently without any warning. I thought that reflashing will solve the problem. Do you have any ideas on how to solve this problem? Thanks in advance.
Click to expand...
Click to collapse
Please wait for the new rom maybe this will help you solve the problem

Twrp recovery

TWRP for XOLO Q3000​
Here is TWRP for xolo Q3000 .
{
"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 request
chinasa
@allan.vaz
@amrutb
@Jagadish-ravi
@qwerty.3551
@ravikumarbeniwal
@rohithdivakaran
@rufus.reynolds
@sushbabblu
@Vineet3
@smahalgavaiya
@vijay jay
m0han
@aabidhashmi
@barath anandan
 @drlalitbida
 @fort21
@nihar13
@qwerty.3551
@sanyamjain
@Sandy d Candy
@SPG30759
@ranjanshandilya
@Rishi45
 @indigo110
@rahulhacker007
@sunny76900
@patilsb
@akxolo
@xoloq3000
@ravi_21
@mhp1995
@Karan_Kapuria
@nicksaisw
@Aftab Memon
@ashuchem
@Haldar_dhruv
@rohitsinghpu
@beinglazy
@viru_192 
 @chaobuddy
@irfanjunaid
@arnabbiswasalsodeep
@Anand Ramesh
@ashishji12
ApriliaM3
Please try this recovery and report back about JB and KK rom switching.
In TWRP 2.8 u cant root with it as supersu is deleted from recovery to reduce size.
As we have other flashable zips to root it wont be an big issue.
Waiting for response from u guys.​
Credits-
@yuweng Sir this wont be possible without his tool
TWRP team 
 @hanuma for help:good:

avi3230 said:
In TWRP 2.8 u cant root with it as supersu is deleted from recovery to reduce size.
As we have other flashable zips to root it wont be an big issue.....
Click to expand...
Click to collapse
i'm on clone stock kk rom with cwm v6.0.2.8 now. i wanna have twrp v2.8 and also root. how best to go about it?
does your op imply "if twrp v2.7 is used, root is not lost"? - on rooted device having any other custom recovery.
and, what if i flash your twrp v2.8 and then flash supersu zip file from here? will i have proper root?
btw, can this be installed using flashify or mobileuncletools? or, is spftools procedure itself required?
suggest that you make the op clearer and noob-friendly. thanks.

m0han said:
i'm on clone stock kk rom with cwm v6.0.2.8 now. i wanna have twrp v2.8 and also root. how best to go about it?
does your op imply "if twrp v2.7 is used, root is not lost"? - on rooted device having any other custom recovery.
and, what if i flash your twrp v2.8 and then flash supersu zip file from here? will i have proper root?
btw, can this be installed using flashify or mobileuncletools? or, is spftools procedure itself required?
suggest that you make the op clearer and noob-friendly. thanks.
Click to expand...
Click to collapse
Make sure you flash stock rom first before flashing this recovery! When i was using Q900, it used to give variety of errors! So always begin with clean flashed device! The error that i got frequently was E: cannot mount /Data bla bla.... Always ended up with mounting errors! Then came Shikar bro who ported the recovery and after which i developed the custom first custom ROM!

irfanjunaid said:
Make sure you flash stock rom first before flashing this recovery! When i was using Q900, it used to give variety of errors! So always begin with clean flashed device! The error that i got frequently was E: cannot mount /Data bla bla.... Always ended up with mounting errors! Then came Shikar bro who ported the recovery and after which i developed the custom first custom ROM!
Click to expand...
Click to collapse
Anyone having this issue???
I didnt got it.
working correctly till now
but thanks for the info:good:

m0han said:
i'm on clone stock kk rom with cwm v6.0.2.8 now. i wanna have twrp v2.8 and also root. how best to go about it?
does your op imply "if twrp v2.7 is used, root is not lost"? - on rooted device having any other custom recovery.
and, what if i flash your twrp v2.8 and then flash supersu zip file from here? will i have proper root?
btw, can this be installed using flashify or mobileuncletools? or, is spftools procedure itself required?
suggest that you make the op clearer and noob-friendly. thanks.
Click to expand...
Click to collapse
U cant root using 2.8 recovery.
sometimes if rom is not rooted then at end of flash it ask u to root, 2.8 cant do that but 2.7 can:good:.
u cant have 2.8 with root facility as size will exceed 6mb.
u can root device using any flashble root zip.
================================================================================================
For kitkat 4.4.2 the zip in link is not at all useful.
Also it cant be rooted with supersu provided in recovery
so if u wanna use 2.8 u cant use rooting within recovery.
if u wanna root ur 4.4.2 see this post method 8 definatly works.
also if u want supersu as root app head over to this post.
For recovery flashing I always prefer sp tool method which will work 100% and u dont have to bother about properly rooted device.
if u have rooted device flashify or mobileuncle tool should work.

Hi Avi, when i tried to flash the recovery via flashify my stock recovery is gone as well as the one which i flashed twrp also gone and currently my phone is running without recovery

sushbabblu said:
Hi Avi, when i tried to flash the recovery via flashify my stock recovery is gone as well as the one which i flashed twrp also gone and currently my phone is running without recovery
Click to expand...
Click to collapse
Please try with sp tools.
if u running 4.4.2 flashify may give this type of error.

TWRP - 2.8 - 94 downloads:good::good::good:

avi3230 said:
TWRP - 2.8 - 94 downloads
Click to expand...
Click to collapse
weird graphics and touch issues were reported in 2.8.0.0. how about 2.8.2.0?
bovirus said:
TWRP released a bugfix for TWRP 2.8.1.0 . Now it's available TWRP 2.8.2.0.
Click to expand...
Click to collapse

m0han said:
weird graphics and touch issues were reported in 2.8.0.0. how about 2.8.2.0?
Click to expand...
Click to collapse
Yes Sir,
I ported 2.8.2.0 but the size is 6.54mb way too much than recovery partition.
I am trying much hard for more than 6 mb partition which can boot in recovery.
Already bricked my device several times for the same.
But still only 6 mb recovery can boot.
NOw we have two options.
Compile new kernel with less size - source codes are needed
we have bq codes - but it may not work for our device - so i am much reluctant to take chance.
we need to compile new uboot.bin which can make booting in recovery of even 11mb size
again source code and compiling.
If anyone from ur side can help in compiling that would be great- as i am just beginner for it
u can get source code for BQ here.
Thank you.

avi3230 said:
....If anyone from ur side can help in compiling that would be great.....
Click to expand...
Click to collapse
sorry. no knowledge in these matters. hope someone else would come forward.

avi3230 said:
...I ported 2.8.2.0 but the size is 6.54mb way too much than recovery partition.
I am trying much hard for more than 6 mb partition which can boot in recovery.....
Click to expand...
Click to collapse
any hope for latest version of twrp?
please see screenshots of twrp v2.8.0.0. the interface is not clear (highly pixelated). the actual display is worse than seen here. can anything be done about it?
does anyone know of any themes than work on twrp v2.8.0.0 for xolo q3000? the ones i tried didn't work although i chose the correct resolution.
also, what exactly does "repair or change file system" do?
my device gets connected as an mtp device and shows up as a separate device in "my computer". i mean, the sd cards do not get connected as separate usb drives.
i can open the device and see both my sd cards listed and also browse & carry out operations. but, any changes made are not reflected even after 'refreshing'.
if i click "disable mtp" as seen in the 3rd screenshot, will the disabling be temporary or permanent? will my sd cards get connected as separate usb drives?
i'd appreciate it if someone who has authentic knowledge about these matters responds with suggestions. thanks for any help.
btw, i hope @avi3230 is following this thread. maybe we can hope for ctr v3.0 kitkat for xolo q3000 soon.
edit: saw this thread only now . will try that and report :good:. please answer the queries in blue. thanks.

@m0han
TWRP 2.8.2.0 coming soon.
themes for 2.8.0.0
what exactly does "repair or change file system" do?
answer is here.
What's new in 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Click to expand...
Click to collapse
MTP is also mentioned under 2.8.0.0
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Click to expand...
Click to collapse
I am following CTR :good::good:

avi3230 said:
....MTP is also mentioned under 2.8.0.0....
Click to expand...
Click to collapse
i'd like to know about this:
m0han said:
....if i click "disable mtp" as seen in the 3rd screenshot,
will the disabling be temporary or permanent?
will my sd cards get connected as separate usb drives?....
Click to expand...
Click to collapse
any idea about this?

[Multi boot-BETA][Apk][Condor][Patcher]

Hey guys the much awaited DualBootPatcher is here for our Condor don't believe me test out yourself
It can patch:
Custom kernels for multi support
ROMs so that they can be installed as secondary
Google Apps packages
SuperSU so that it can be used in other ROMs
xposed
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and install.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Secondary: Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of Extsd slots. These install to the external sd partition and eat up space on the external storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny and your data partition is getting full. These slots are named "extsd-slot-[id]", where "id" is something you provide in the app.
NOTE- It is highly recommended to install secondary roms in external sd slot
How To
1. Install the Multi Boot Patcher app
2. Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
3. Now go to rom settings and click on "Update ramdisk" it will update ramdisk and after that reboot
4. Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
*FLASHING FROM RECOVERY NOT RECOMMENDED*
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from the custom recovery will literally backup every ROM you have installed so think about this before making a backup.
App and data sharing
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
1.Install the app you want to share
2.Open DualBootPatcher and go to "App Sharing" in the navigation drawer
3. Enable individual app sharing
4. Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply becomes unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
FAQ's
Switch the ROM if something doesn't work properly?
If you have TWRP, you can switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
I installed a new rom and want to switch to it?
Open app, select ROMs, then select the rom you want to switch to. When the switch is successful, reboot.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Link :- https://snapshots.noobdev.io/
CREDITS
@chenxiaolong For the app
Me for porting it for you guys @princetrishi for the video
ORIGINAL THREAD
XDA:DevDB Information
Multiboot for condor , Device Specific App for the Moto E
Contributors
zeeshanhussain12
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Beta
Current Beta Version: 8.99.12
Beta Release Date: 2015-11-14
Created 2015-11-14
Last Updated 2015-11-14

Reserved
How To Report Issues ?
Getlogs.zip: getlogs.zip
If a multi-booted ROM is unable to boot, logs will be needed for debugging the issue. Please reboot into recovery without shutting down the device (ie. no removing the battery u cant remove battery in moto e [emoji14] ) and flash the GetLogs zip. This must be done immediately following the boot failure because some logs will be lost after a reboot The zip will save many logs from /sdcard/MultiBoot and device information from /dev, /proc, and /sys to /sdcard/logs/[Date&Time].tar. Please attach this tar archive when reporting an issue.
Also, state whether the ROM reboots or hangs at the moto logo or the ROM's boot animation. If the ROM reboots, please state whether it reboots into recovery or not.
NOTE- CM13 is supported

Installation Video
Thanks to YouTuber Starkdroid (@princetrishi) for making this awesome installation video!
Screenies [emoji10]
{
"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"
}

Awesome work, thanks for your hard work

And the VIDEO TUTORIAL IS HERE!!!
https://www.youtube.com/watch?v=NCk1tr6T76M&feature=youtu.be

worked
Thanks bro.... Worked for me...

Doubt
Like we flash both ROM and gapps from recovery, i cant flash it from here. I patched the ROM, flashed it, good job. But how do i flash the gapps? it shows errors. I flashed it along with the ROM. I tried the second method and flashed it after flashing the ROM...Still ain't working. Please help.
Edit : I flashed gapps seperately...and it worked!!!
Steps for those who face similar problems while patching Gapps -
1. Switch the ROM from Dual Boot Patcher.
2. Reboot your phone. If you flashed correctly, you should be on the secondary ROM....
3. Reboot to recovery and flash gapps. No need to wipe cache/dalvik cache.
4. Woila! Gapps flashed successfully!
Hit Thanks Button if I Helped!!!

The Keeper said:
Like we flash both ROM and gapps from recovery, i cant flash it from here. I patched the ROM, flashed it, good job. But how do i flash the gapps? it shows errors. I flashed it along with the ROM. I tried the second method and flashed it after flashing the ROM...Still ain't working. Please help.
Click to expand...
Click to collapse
You need to patch gapps too [emoji6] and flash it from the app itself
Sent from my Moto E using Tapatalk

The Keeper said:
No....I tried. It doesn't work. It fails.
Click to expand...
Click to collapse
Its working for me, make sure you patch for correct slot
Sent from my Moto E using Tapatalk

Hey...will this work with cm13 as primary rom?

can this work with cm13 as secondary rom?

ishu.aryan said:
can this work with cm13 as secondary rom?
Click to expand...
Click to collapse
Nop cm13 is not supported in both primary and secondary ROM , I m still working on that part mate
Adrao123 said:
Hey...will this work with cm13 as primary rom?
Click to expand...
Click to collapse
Sent from my Moto E using Tapatalk

Thanks for the port
I was waiting for lp support of multirom, and then you ported multiboot, this is far better than multirom..

The Keeper said:
Like we flash both ROM and gapps from recovery, i cant flash it from here. I patched the ROM, flashed it, good job. But how do i flash the gapps? it shows errors. I flashed it along with the ROM. I tried the second method and flashed it after flashing the ROM...Still ain't working. Please help.
Click to expand...
Click to collapse
Bro try different gaaps..
Few gapps didn't worked even for me..
But at last I was able to flash

viku1996 said:
Bro try different gaaps..
Few gapps didn't worked even for me..
But at last I was able to flash
Click to expand...
Click to collapse
umm..okay...Thanks

It shows failed to update ramdisk for me... Help plz..
Sent from my Moto E using Tapatalk

Please be more precise and which ROM you are using?
Note - cm13 is not supported
Gowtham_j said:
It shows failed to update ramdisk for me... Help plz..
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
Sent from my Moto E using Tapatalk

I'm on exodus 5.1. I've followed the steps as quoted in the op. After setting the kernel I tried to update the ramdisk, but I faced an error. It shows "failed to update ramdisk".

Gowtham_j said:
I'm on exodus 5.1. I've followed the steps as quoted in the op. After setting the kernel I tried to update the ramdisk, but I faced an error. It shows "failed to update ramdisk".
Click to expand...
Click to collapse
It was working for my friend. Please upload ramdisk update log . it will be there in multiboot folder
Sent from my Moto E using Tapatalk

if i wanna flash xposed
then should i patch xposed zip too?

[RECOVERY][MOD] MultiROM v33 + TWRP v3.1.1 for Xiaomi Mi MIX (lithium)

{
"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. 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).
To decrypt your device:
Backup ALL your data if you need to recover later (TWRP backup to USB or copy to your PC)
In fastboot mode:
Code:
fastboot format userdata
In TWRP: Flash Magisk (recommended) or SuperSU to avoid auto-encryption in next boot.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP). Flash it as usual TWRP (fastboot flash recovery, or any flasher app if you're rooted).
MultiROM. Install it as usual zip from modded TWRP once flashed.
Go into TWRP MultiRom settings and be sure that "Enable No-KEXEC Workaround" is enabled (enabled by default)
Your current rom will not be erased by the installation.​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.​
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.
MIUI ROM as Secondary <--- Latest versions fix this, so you shouldn't need it anymore
Install MIUI as secondary via MultiROM settings in TWRP
Boot into your (rooted) primary
Edit fstab.qcom file in /storage/emulated/multirom/roms//boot/ and add /cache partition entries:
Code:
/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait,check,formattable
/dev/block/bootdevice/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check,formattable
Alternatively you can use attached file "fstab.qcom.txt" (rename to: fstab.qcom without .txt ). Be sure to set proper permissions (copy from original fstab.qcom, after renaming to fstab.qcom.bak, don't delete it...)
DON'T FORGET to flash Magisk / SuperSU after flashing to avoid re-encryption if you're flashing stock (not modded).
Known issues
You must wait a few seconds (3-5) before you get touch screen responsiveness in TWRP and MultiROM. (fixed by 2017.08.01 build) -- USUAL WHEN SWITCHING FROM MIUI
Some FCs on some secondary ROMs: Try using multiromfix.zip, thx to @Startrek852 (to disable sdcardfs support in that secondary) -- USE MAGISK 13.5+
Issues with TWRP to boot on 4GB/128GB model... (Working on troubleshooting...) -- PRELIMINARY FIX HERE
Reporting issues
As you surely understand, a simply "it does NOT work" is not enough... so please, report your issue describing scenario as much as you can, try following this (as much as possible information is welcome, it's very tiring for me asking what this, what that, etc...):
Issue description (what, how, when, etc...)
Device model : 4GB or 6GB RAM
Decrypted? /cache and /data FSs ? (We assume IS decrypted becaues you're using MultiROM, and EXT4 FS for /cache and /data if you don't know or manually formatted to F2FS)
TWRP version + MultiROM version
Primary ROM (name, better with version)
Firmware version
Secondary ROM (the one with the issue, name and better version)
Custom kernel ? (name and version if so) <--- In theory, we shouldn't support scenarios with custom kernels.... (they can touch system stuff that make things more complex)
Xposed ? <--- Sorry we DON'T support MultiROM if you use Xposed
Google Apps (name, better with version)
Magisk / SuperSU (version and if you use it in Primary and/or Secondary and version)
Logs <--- This would be amazing great and helpful !!!! (you can get them via adb shell, terminal or using any tool)
*Original post and example in this post, please: ​
Download
You can download all stuff from here, where you can find latest TWRP and MultiROM. If you need to uninstall MultiROM, you can use this uninstaller.
MultiROM Manager (apk) available here.​
Source code
MultiROM - https://github.com/MultiROM-dev/multirom
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/BitOBSessiOn/android_device_xiaomi_lithium​
Special thanks to:
@Tasssadar for creating this awesome utility
@nkk71 for the No-KEXEC workaround
@AdrianDC and all MultiROM guys involved in its development
@jcadduono for TWRP port

We will have to try soon... It's the perfect set up for flashaholics

Great news [emoji847][emoji847]
Envoyé de mon MIX en utilisant Tapatalk

I can't make it work

fil0s0f0 said:
I can't make it work
Click to expand...
Click to collapse
The MultiROM app from market is only for official devices (I haven't updated the Android app, imo it's not very useful), So you must follow OP steps.
If you have some issue, please, describe your problem and we will try to help.
Keep in mind that you must have unlocked bootloader, decrypted device, etc...

Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback

fil0s0f0 said:
Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback
Click to expand...
Click to collapse
Yes, there are, please, revise OP, and describe which steps have you followed to find out what's your issue. Thx

provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output

Superb, I missed it in this great smarphone

acasmc said:
provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output
Click to expand...
Click to collapse
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.

BitOBSessiOn said:
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.
Click to expand...
Click to collapse
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.

acasmc said:
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.
Click to expand...
Click to collapse
Too weird... I've just downloaded and flashed again with rashr and ok.
Which model do you own (128/256)? Primary rom...?
TWRP must work ok with encrypted /data (but you need decrypted for MultiROM).

I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.

acasmc said:
I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.
Click to expand...
Click to collapse
Can you try some of older versions in testing or backup folder in n AFH, please...?
Can you take a photo of error if it still occurs...?

there is only one TWRP in your folder. can you point me to another. I'll try no worries

acasmc said:
there is only one TWRP in your folder. can you point me to another. I'll try no worries
Click to expand...
Click to collapse
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564

Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]

Konsstantine34 said:
Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]
Click to expand...
Click to collapse
Usually I don't start to develop for a device before I can use MultiROM....

BitOBSessiOn said:
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564
Click to expand...
Click to collapse
tried other two that are on that link. still the same. sadly don't have another phone with me, to take a picture.
guess gonna have to wait for an update. :/

BitOBSessiOn said:
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
Click to expand...
Click to collapse
About encrypting, Is it enough to flash the "no-verity-opt-encrypt-5.1".zip?, And if its not, Is there a guide of how to encrypt my device?

[ROM][BETA] OFFICIAL PIE from ASUS

I am not responsible if you brick your device.
UPDATE BETA PIE ROM
Direct link Download- https://drive.google.com/uc?id=1_r6zxR34q5aN72SPhAjMLkV4GxQcD4ff&export=download
Flash procedure for pie- https://www.asuswebstorage.com/navigate/a/#/s/A9A029F390A34806BED2A412E194C44D4
For BL unlocked phones
Recommended PBRP
PBRP has function to fix the encryption after flashing the ROM. You may choose to flash decrypt.zip for your own satisfaction.
PBRP worked like a charm for me.
* Use 7zip/WinRAR- Extract / Open Archive by right clicking the firmware zip and go to > META-INF > com > google > android
*open updater-script with a note editor
* Remove all the lines above the code
ui_print("Target: Android/sdm660_64/sdm660_64:X.X.X/XXXX/XX.20XX.XXXX.XXX-20XXXXXX:user/release-keys");
*Save it/rezip the firmware and copy it to sdcard
*Wipe System, data, cache / format DATA.
*Flash the ROM
Stock FULL ROM OREO 8.1
Stock Recovery & TWRP Flash-able
You have to flash full ROM if magisk is installed. Take backup & be very careful if device get encrypted after installing the ROM. (Flash decryption file- https://forum.xda-developers.com/asus-zenfone-max-pro-m1/how-to/mod-decrypt-data-t3787311 )
* Use 7zip/WinRAR- Extract / Open Archive by right clicking the firmware zip and go to > META-INF > com > google > android
*open updater-script with a note editor
* Remove all the lines above the code
ui_print("Target: Android/sdm660_64/sdm660_64:X.X.X/XXXX/XX.20XX.XXXX.XXX-20XXXXXX:user/release-keys");
*Save it/rezip the firmware and copy it to sdcard
*Wipe System, data, cache / format DATA.
*Flash the ROM
Official ROM link- https://www.asus.com/Phone/ZenFone-Max-Pro-M2/HelpDesk_BIOS/
One click Download - https://dlcdnets.asus.com/pub/ASUS/...995.844210030.1548823414-323285766.1546595187

so after installing latest 186 ROM continue installing decrypt.zip right?

rycroot96 said:
so after installing latest 186 ROM continue installing decrypt.zip right?
Click to expand...
Click to collapse
when i had installed December update (unlocked bootloader & magisk installed) i flashed the new rom, installed decrypt.zip yet the phone got encrypted on boot. Later i formatted data and flashed decrypt.zip and the phone booted normally.
Its kind of two way procedure. Try it. There is nothing wrong in experiment unless you haven't taken backup.
I'll flash as soon as i go home & let you know the status.

Ajeyvm said:
when i had installed December update (unlocked bootloader & magisk installed) i flashed the new rom, installed decrypt.zip yet the phone got encrypted on boot. Later i formatted data and flashed decrypt.zip and the phone booted normally.
Its kind of two way procedure. Try it. There is nothing wrong in experiment unless you haven't taken backup.
I'll flash as soon as i go home & let you know the status.
Click to expand...
Click to collapse
but when encrypted twrp doesn't disappear right? ok I am waiting I haven't updated since ubl + magisk. what is meant by twrp backup right? I have a system backup and booted. thanks a lot for the info bro

rycroot96 said:
but when encrypted twrp doesn't disappear right? ok I am waiting I haven't updated since ubl + magisk. what is meant by twrp backup right? I have a system backup and booted. thanks a lot for the info bro
Click to expand...
Click to collapse
backup means your personal data, apps, contacts, internal storage.
TWRP wont be gone after flashing. The phone works fine even after its encrypted. You need to flash decrypt.zip to get internal storage access in TWRP . And for overall smoothness of the device.

Ajeyvm said:
backup means your personal data, apps, contacts, internal storage.
TWRP wont be gone after flashing. The phone works fine even after its encrypted. You need to flash decrypt.zip to get internal storage access in TWRP . And for overall smoothness of the device.
Click to expand...
Click to collapse
thank you very much for the info

Guys ... Use PBRP Recovery.. It is based on TWRP...
It automatically patches forced encryption, after flashing the firmware file...
But just to make sure flash decrypt.zip too ...

So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
and my nandroid backup that I just make is on internal storage... so now it's already encrypted(or it isn't?) and no longer be able to use...
Is there any way I can decrypt back my phone?
my custom recovery/twrp encrypted as well
I got my nandroid backup few days ago on my computer
{
"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"
}

watatara.102 said:
So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
and my nandroid backup that I just make is on internal storage... so now it's already encrypted(or it isn't?) and no longer be able to use...
Is there any way I can decrypt back my phone?
my custom recovery/twrp encrypted as well
I got my nandroid backup few days ago on my computer
Click to expand...
Click to collapse
I don't think there is a way to decrypt your phone without losing data...
Best way is restore from your nandroid backup...
watatara.102 said:
So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
Click to expand...
Click to collapse
I did exactly the same... But using PBRP recovery... Faced no issue at all...

Tyakrish said:
I don't think there is a way to decrypt your phone without losing data...
Best way is restore from your nandroid backup...
I did exactly the same... But using PBRP recovery... Faced no issue at all...
Click to expand...
Click to collapse
uh, the one that is encrypted is on /data I'm right?
my internal storage/internal SD which is on /data/media is not encrypted right? then I still can copy my NANDroid backup?

error displayed 7 in twrp.
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution

shivrajmalani said:
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution
Click to expand...
Click to collapse
Do not unzip the file.
Right click on the file, open archive. Edit the updater script. Save it. Better to use 7Zip.

watatara.102 said:
uh, the one that is encrypted is on /data I'm right?
my internal storage/internal SD which is on /data/media is not encrypted right? then I still can copy my NANDroid backup?
Click to expand...
Click to collapse
I am not sure exactly, which partitions are encrypted. But yes I think internal storage on /data/media is not encrypted...
But if you open TWRP then you will get a message to decrypt your device... DONT do this ! It will wipe your internal storage too, even if it is not encrypted...
If you want to copy your nandroid backup, then boot up your ROM and then transfer files using MTP to your computer..
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
shivrajmalani said:
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution
Click to expand...
Click to collapse
Did you use WinRAR ? Do one thing...
After extracting zip, and editing the script, go to the root of your firmware folder, select all files then add to archive. Select archive format as zip and keep the lowest compression possible...
While flashing, disable zip verification. This should work... Otherwise try the method by @Ajeyvm

I got this weird bug and it's will keep creating new log everytime reboot
here log file https://pastebin.com/wXHvcbDT

watatara.102 said:
I got this weird bug and it's will keep creating new log everytime reboot
here log file https://pastebin.com/wXHvcbDT
Click to expand...
Click to collapse
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version

Zahirpro2 said:
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version
Click to expand...
Click to collapse
Whenever i restart my phone i get that bug report. I clear it & use the device as usual. Evrything else is working fine. No need to revert back unless u r facing some major issue.

Zahirpro2 said:
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version
Click to expand...
Click to collapse
Oh so its not just me then, good to know

It looks good.
Edit, someone posted a review - https://youtu.be/_wli8M-71yI

Someone should really post a mirror of the official link

Official link is down does anyone has any other mirror link?