Database Info

[App] Root Toolkit for Android™

.
Market link: Android Root Toolkit (free)
Root Toolkit for Android™
I wrote this little root utility for myself to help consolidate and automate some root functions that are available in various other apps, but nowhere all together.
Note: this utility does not root your Android device--it assumes that your device is already rooted.
If you are having problems or issues with it, please send me an email at [email protected] with as much detail as you can provide.
FEATURES:
display current root, /system and root (/) mount status, and root save status; will also display bootloader lock status for the Samsung Galaxy Nexus
reboot options (normal, recovery, bootloader)
power off device
remount rootfs (/) and/or /system in read-write or read-only mode; note: remount behavior changed in Android 4.2 and higher that causes remount effect to not be usable by apps other than the one that initiated the remount
save (protect) / restore root function; for 4.2 devices with ext2/3/4 /system partitons, a copy of su binary can be saved and later restored; for 4.3 devices, I've implemented Pau Oliva's 4.3+ "OTA rootkeeper" functionality (i.e., via keeproot.sh)
freeze (disable) or thaw (enable) an application (use caution when freezing a system app!); you can select showing user and/or system apps in the Freeze/Thaw Display Options in the Preferences/Settings menu
display system (getprop) property values
Galaxy Nexus and Nexus 7 (1st gen) only options:
flash a stock recovery
flash various custom recoveries
make recovery "stick" (keep stock recovery from overwriting your custom recovery)
identify currently installed recovery
bootloader lock, unlock, status (Galaxy Nexus only)
option to turn confirmation mode on / off (defaults to on)
option to turn "safe mode" on for the app to prevent any su or flashing operation from occurring
Warning / disclaimer: the author of this app is not responsible for any loss or damage caused by or related to its use.
If you are not comfortable with or knowledgeable about the proper use and functionality of this app, please discontinue its use and uninstall.
Click to expand...
Click to collapse
PERMISSIONS:
INTERNET - for downloading recoveries from the internet
WRITE_EXTERNAL_STORAGE - this is for the downloaded recoveries and work files used to identify which recovery is currently installed
ACCESS_SUPERUSER permission to support interaction with SuperSU
Keywords: root status, root checker, mount status, flash stock recovery, flash custom recovery, reboot recovery, reboot bootloader, power off device, remount system, make recovery stick, identify recovery, save root, restore root, freeze app, disable app, thaw app, enable app,
bootloader lock, bootloader unlock, bootloader status, getprop, system properties
Screen shots:
{
"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"
}
--------------------------------------
Android is a trademark of Google, Inc.

Version 1.3 just uploaded to the Market:
[version 1.3 - 22-April-2012]:
- support freezing (disabling) or thawing (enabling) applications
..(take care before deciding to freeze a system app)
These updates weren't as easy or straight-forward as I had imagined it would be--no wonder there's so few apps out there that have the freeze/thaw feature .

interesting and important tool
I am very interested in this tool and will have a try for sure. Number of questions:
1. Can your tool save current recovery as a blob, which is either cwm flashable or dd flasable(flash through "dd if=/sdcard/recovery_blob_backup of=/dev/block/mmcblk0p4"). My ASUS TF101 is rooted with stock recovery, I would like to try cwm recovery, but I want to save my stock recovery so that I can switch back to stock recovery when OTA is coming.
2. The most important features are those marked as "Galaxy Nexus only options". Is it harmful to try these on other devices such as ASUS transformer.
3. Does it work to use cwm recovery to flash official firmware package without any repacking. How about your tool?
Thanks in advance
---------- Post added at 03:51 PM ---------- Previous post was at 03:30 PM ----------
Two more questions:
4. The su backup made by Voodo rootkeeper is not "immutable", it can be revoced by "chattr -i" and then "rm". how about your backup?
5. If superuser.apk is removed or disabled, does your root protection tool
still work?
Thanks

e154037 said:
I am very interested in this tool and will have a try for sure. Number of questions:
1. Can your tool save current recovery as a blob, which is either cwm flashable or dd flasable(flash through "dd if=/sdcard/recovery_blob_backup of=/dev/block/mmcblk0p4"). My ASUS TF101 is rooted with stock recovery, I would like to try cwm recovery, but I want to save my stock recovery so that I can switch back to stock recovery when OTA is coming.
Click to expand...
Click to collapse
The app will not save a current recovery (not a currently implemented function).
I can tell you I tried copying the currently installed recovery on my GNex using exactly the process you described above. Unfortunately, the flash_image of that copy/backup does not appear to flash properly (and/or I got an error--I think I did get an error when doing the flash and ended-up trying several different versions of the flash_image utility to no avail). The resultant backup/copy of the recovery partition was usually about 12MB vs. approx. 5MB for a "normal" other recovery file that you would flash, so I don't know if its a size issue or limitation with the flash_image utility or not, but flashing a copy of the whole recovery partition did not work for me on the GNex.
I suppose "flashing" via the dd command might / would work, but I haven't yet tried that (dd is scary ).
2. The most important features are those marked as "Galaxy Nexus only options". Is it harmful to try these on other devices such as ASUS transformer.
Click to expand...
Click to collapse
I have product/device checks in the app that should keep those options from even being available to you on the main menu if its not a GNex device. The Setting / Preferences settings will still appear, but if you don't have a GNex, they should not appear on the actual main menu (I'd be very interested to know if they do ).
3. Does it work to use cwm recovery to flash official firmware package without any repacking. How about your tool?
Click to expand...
Click to collapse
My app uses the flash_image utility to flash its recoveries for the GNex. It does not use ROM Manager or ClockworkMod for any flashing operations that it undertakes.
4. The su backup made by Voodo rootkeeper is not "immutable", it can be revoced by "chattr -i" and then "rm". how about your backup?
Click to expand...
Click to collapse
Yep, works exactly the same .
The immutable property is apparently only supported on the ext2/3/4 type of filesystems (I think that's the right list)
5. If superuser.apk is removed or disabled, does your root protection tool
still work?
Click to expand...
Click to collapse
I never specifically tested removing Superuser.apk, but you should/would still be able to re-download that app from the Market and install it to complete the second half of root (the first being restoration of the su binary).
~ ~ ~
You should know that the GNex-only options that I support in the app were basically because I own a GNex and wanted to support some functions that I got tired of doing via other apps. Supporting devices other than the GNex is not currently in my plans since it these things are very device- and recovery-specific and I wasn't comfortable releasing features and functionality that I could not directly test and validate myself.
Cheers!

Thanks for the explanation. Where can I find the flash_image utility, is it device spacifilc? If it is not your self-made component, can you give me a copy of the utility.

e154037 said:
Thanks for the explanation. Where can I find the flash_image utility, is it device spacifilc? If it is not your self-made component, can you give me a copy of the utility.
Click to expand...
Click to collapse
Ah, there's a billion copies of it "out there", but you should be able to extract if from the .apk file of my app if you want.
Just make a copy of .apk file (its really just a .zip file, after all). Then use a file explorer or unzip utility and explore res/raw folder (I think that's where it is).
It should work on all Android devices (I've got/found multiple copies and versions of various ages and sizes that I'm sure are due to the different builds of Android).
The key thing you need to be careful of is making sure you've got the proper partition / area that you are going to be flashing to (i.e., the recovery partition is not located in the same place / name on every device and there's no way (that I'm aware of) to universally describe how to identify it (short of looking in the build code for your specific device)). Flashing a recovery to the boot partition is a quick and easy way to brick your device .
Also, making sure that you've verified that integrity of the file you are flashing (i.e., via and MD5 or SHA1 checksum) is always a good idea. There's no inherent checksum / integrity check done by the flash_image utility--it'll flash anything to anywhere you tell it (or at least try to).
All due caution and a current Nandroid backup is always your best friend .
Cheers!

Thanks.
Stupid me! I should have realized that the tool could be extracted from your apk or for ROM manager.
Question on image file used in flash_image:
Asus official firmware package's zip file contains a file "blob", unpack the blob one can find a number of images, including blob.SOS. This blob.SOS is the stock recovery image. To my knowledge, blob.SOS should be repacked when being flashed with dd.
Is this blob.SOS (witout any repack) the right one goes with flash_image (flash_image recovery /sdcard/blob.SOS)?

e154037 said:
Thanks.
Stupid me! I should have realized that the tool could be extracted from your apk or for ROM manager.
Question on image file used in flash_image:
Asus official firmware package's zip file contains a file "blob", unpack the blob one can find a number of images, including blob.SOS. This blob.SOS is the stock recovery image. To my knowledge, blob.SOS should be repacked when being flashed with dd.
Is this blob.SOS (witout any repack) the right one goes with flash_image (flash_image recovery /sdcard/blob.SOS)?
Click to expand...
Click to collapse
LOL, no worries! (I've had more than my share of those moments )
I'm not familiar with the Asus .zip package formats or the blobs.
But, I would think you could verify that you are talking apples-to-apples (so-to-speak) if you were to calculate the MD5 of a current blob recovery file with an extracted dd dump of the currently installed recovery's MD5 file (i.e., find the published blob that should match what you have installed; if they match, then you are on the right track, otherwise, you'll have to re-evaluate and dig a little deeper).
Cheers!

Says i dont have superuser.apk but i do ..
Sent from my VS910 4G using xda premium

motodroidfreak said:
Says i dont have superuser.apk but i do ..
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Hmm, do you know where it's actually installed (i.e., the full file path)?
My app checks for "Superuser.apk" or "SuperUser.apk" in the /system/app directory.
Lemme know where yours is installed and I'll make a quick tweak .
Cheers and thanks!

Android Root Toolkit: updated to version 2.6
New version just published to the Play Market...thanks!
Here's the most recent change log items:
[version 2.6 - 08-December-2013]:
- support save root for 4.3+ devices (credit/thanks to Pau Oliva (poliva) and Chainfire)
- fix FC caused in some devices that return weird (non-standard) Android version information
- 2012 N7 only: support 4.3 (jwr66y) and 4.4 (krt16s) stock recoveries
- Samsung Galaxy Nexus only: support recent stock recoveries for international and Sprint versions
- address transitory mount behaviour that apparently started in Android 4.2 and up
- display warnings for keeping a pre-4.3 saved root present before installing a 4.4+ OTA
- lots of other minor tweaks, cleanups, and enhancements
Click to expand...
Click to collapse

[ROOT][ROM][RECOVERY]SliPer ModRecovery + G1345 RootROM

SliPer ModRecovery and G1345 RootROM. What are they?
By now combination of these two is the only way to obtain root privileges on Gigabyte GSmart G1345 with the following ROM software builds installed:
0.56.4 build 1962.124.2931#EEU,
0.56.5 build 1677.124.2667#RUS,
0.56.5 build 1621.124.2855#Stellar,
0.56.6 build 1898.124.2952#CHT,
1.4.2 build 1970.124.2847#EEU,
1.4.3 build 1736.124.2969#WEU.
That's because no known exploit works on these builds.
SliPer ModRecovery is a custom Andriod system recovery. G1345 RootROM is a custom ROM for Gigabyte GSmart G1345/Mc Onsen MCG1345/Cherry Mobile Stellar smartphone with Dual-SIM support. Several versions of G1345 RootROM correspond to different builds, each designed for a specific region or reseller.
What are the differences between SliPer ModRecovery and stock recovery?
The only difference between SliPer ModRecovery and stock recovery is that during ROM installation process Gigabyte signature verification is disabled in SliPer ModRecovery. So you're able to install any stock/custom ROM (suitable for your device). The only restriction, while installing stock ROM (not custom!), is that BUILD_SW_PROJ field in update_ver.txt file of already installed ROM and BUILD_SW_PROJ field in update_ver.txt file inside update1.zip/update.zip package on SDCard should be equal.
What are the differences between G1345 RootROM and stock ROM?
In general, a custom ROM may differ from a stock ROM in everything ranging from the custom user interface to the modified kernel.
These are the differences of G1345 RootROM comparing to the stock ROM:
disabled BUILD_SW_PROJ check in the update script;
ROM is already rooted;
added BusyBox 1.19.4;
adbd runs with root permissions and "USB Debugging" is turned on for logging of the boot process by default;
G1345 RootROM preserves SliPer ModRecovery on ordinary boot for further use (if stock ROM is installed, on each ordinary boot recovery partition is being rewritten with the original recovery image formed by patching original boot image with binary diff file recovery-from-boot.p).
Interface and kernel are derived from the original ROM.
Will I lose the warranty after installing G1345 RootROM by using SliPer ModRecovery?
Before calling for service install G1345 RootROM for your region, then install original ROM for your region. This is required to restore original ROM and recovery. After that clear cache and erase userdata by using stock recovery, remove SDCard from the device.
How to install G1345 RootROM?
WARNING! ALL userdata will be erased during G1345 RootROM installation process, so it's highly recommended to backup your valuable data!
You should install smartphone drivers if they haven't been installed yet.
It's important that you DON'T need root privileges to install G1345 RootROM by using SliPer ModRecovery.
There're 2 types of G1345 model. They differ in WLAN hardware being used in their design. The first type of G1345 uses AR6002 WLAN platform and these devices can be flashed with the following ROM software builds (each of these builds is located in the root directory of the corresponding ROM archive update1.zip/update.zip): 0.56.4 build 1962.124.2931#EEU, 0.56.5 build 1677.124.2667#RUS, 0.56.5 build 1621.124.2855#Stellar, 0.56.6 build 1898.124.2952#CHT, 1.4.2 build 1970.124.2847#EEU, 1.4.3 build 1736.124.2969#WEU. The second type of G1345 uses AR6003 WLAN platform and these devices can be flashed with the following ROM software builds (each of these builds is located in "la" directory of the corresponding ROM archive update1.zip/update.zip): 0.56.4_1 build 1963.124.2931#EEU, 0.56.5_1 build 1678.124.2667#RUS, 0.56.6_1 build 1899.124.2952#CHT, 1.4.2_1 build 1971.124.2847#EEU, 1.4.3_1 build 1739.124.2969#WEU.
WARNING! IN ORDER TO INSTALL SliPer ModRecovery and G1345 RootROM CORRECTLY YOU SHOULD KNOW THE TYPE OF YOUR G1345 MODEL (THESE TYPES ARE THE FIRST OR THE SECOND TYPE MENTIONED ABOVE)! You're able to check this by installing original ROM for your region/reseller and selecting "Menu"->"Settings"->"About phone"->"Build number":
Original 0.56.4_EEU ROM
Original 0.56.5_RUS ROM
Original 0.56.5_Stellar ROM
Original 0.56.6_CHT ROM (registration required)
Original 1.4.2_EEU ROM (registration required)
Original 1.4.3_WEU ROM (archive password required )
Download one of G1345 RootROMs:
G1345-0.56.4_EEU.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Cz/
G1345-0.56.5_RUS.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Russia/
G1345-0.56.5_Stellar.zip - based on the original ROM from Cherry Mobile official website http://www.cherrymobile.com.ph/products/smart-social/stellar (FOR THE FIRST TYPE OF G1345 ONLY!)
G1345-0.56.6_CHT.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Taiwan/
G1345-1.4.2_EEU.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Eng/
G1345-1.4.3_WEU.zip - based on the original ROM from Mc Onsen official website http://www.mconsen.com/mcg1345.php
Then extract configure (THIS FILE IS REQUIRED ON G1345 FOR THE AUTOMATION OF ROM INSTALLATON PROCESS, BECAUSE DURING THE FIRST PHASE OF THIS PROCESS TOUCHSCREEN IS TURNED OFF) and update1.zip/update.zip from archive to the root of SDCard which will be used to update ROM.
Download ModRecovery_BootScript.zip and unpack it somewhere to your PC. This is a "script" for booting up smartphone with recovery.img in fastboot mode. "Script" file flasher.bat itself is located in ModRecovery_BootScript folder. Extract recovery.img suitable FOR YOUR TYPE OF G1345 from previously copied to SDCard update1.zip/update.zip archive to ModRecovery_BootScript folder. If you've got the first type of G1345, you should extract recovery.img from the root directory of update1.zip/update.zip archive, otherwise if you've got the second type of G1345, you should extract recovery.img, which is located in "la" directory inside update1.zip/update.zip archive.
Then turn off your device, insert SDCard (with configure and update1.zip/update.zip files located in SDCard root directory) into it, turn the device into fastboot mode by holding volume down button + power button until blue LED blinks once. Then connect the device to PC, wait until fastboot mode drivers will be completely installed and run flasher.bat. The first phase of installation process is automated (if configure is located in SDCard root directory) and performed with touchscreen turned off. After reboot touchscreen will be turned on and the installation process will be continued. At the end of the update process you'll get installed software version on the screen along with reboot request. Confirm reboot. Device will reboot in ordinary mode with SU and BusyBox properly installed. Enjoy!
In order to check whether you've got SliPer ModRecovery properly installed, delete/move configure and update1.zip/update.zip from the root of SDCard, reboot in recovery mode by holding volume up button + power button until blue LED blinks 3 times. If you get the following screen, then SliPer ModRecovery has been installed properly:
{
"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"
}
Donations
All donations are strictly voluntary. But I really appreciate any help, because I've got some financial troubles now.
PayPal
Donate
WebMoney Transfer
Z135745021429
E301654453478
R160707042034
U897012425686
QIWI Wallet
9167226205
Yandex Money
410011384134846
--------------------
ROMs and ModRecoveries for other Gigabyte Dual-SIM Android phones:
[ROM][RECOVERY]SliPer ModRecovery + G1310 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1315 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1317D RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1355 RootROM

root
Welcome sliper123!
I have a problem! I would be really grateful if you could help ...
1.4.2 EEU # 1970 ... is the rom on my device.
SD card root directory of the "configure" and "update1.zip" file, but in vain, after I run flasher.bat fastboot file, reboot, and delete only offers.
It is possible that something is not doing well ....
Thanks in advance for the help!
netjoe3

G1342
Hi,
I have G1342 from gsmart and i need root.
Android Version: 2.3.5
BaseBand Version: 1.8.0 build 1780#std
Build Number: 18.0 buid 1780.0124.3014# GSmart.
How to obtain root access.
Regards
Bluffmaster

Thanx man. Just what I needed. Works perfectly!

Great job
Hi SliPer,
I've just installed G1345-1.4.2_EEU.zip RootROM, it works perfectly. Thanks, excellent job.
My only problem is the lack of Kernel support for 2 way call recording.
Could you share your opinions how to patch or do something for 2wcr feature?
Thanks.
Best regards,
rocky

can i install the 0.56.5 update on my Stellar even though im using a 0.52 RUS Rom? please reply.
i think my phone is bricked
after i use the flasher bat the transfer went fine but after that the phone doesnt respond anymore.. also stuck at the Gsmart logo
Messaged Sent to sir Sliper
hello sir.. please help me.. i have a Cherry Mobile Stellar 1st Type of G1345
my phone got bricked when i tried your RootROMs... before i tried your RootROMs im in 0.52.2 RUS Rom so what i did is download the 0.56.5 RUS RootROMs then i prepared all the files that is needed like the ModRecovery Script and copied recovery.img of 0.56.5 RUS RootROM in the ModRecovery Folder.. i have installed all the drivers including the fastboot drivers... so here what happens.. i turned off my phone then go to fastboot mode.. then i opened flasher.bat and pressed Enter.. but after that nothing happens in my phone the LED just turned RED it doesnt boot and its not responding.. after waiting for 30 mins of black screen still nothing.. so i assumed that my phone is Soft Bricked.. and can you please help me recover from this brick sir? i have tried all update1 files all your RootROMs and even Stock ROMs but they cant be detected by the Recovery Mode so my phone is like a stuck right now gathering dust.. please reply to my message ASAP sir.. thanks !

[ROOT][ROM][RECOVERY]SliPer ModRecovery + G1315 RootROM

SliPer ModRecovery and G1315 RootROM. What are they?
SliPer ModRecovery is a custom Andriod system recovery. G1315 RootROM is a custom ROM for Gigabyte GSmart G1315 smartphone with Dual-SIM support. Several versions of G1315 RootROM correspond to different builds, each designed for a specific region or reseller.
What are the differences between SliPer ModRecovery and stock recovery?
The only difference between SliPer ModRecovery and stock recovery is that during ROM installation process Gigabyte signature verification is disabled in SliPer ModRecovery. So you're able to install any stock/custom ROM (suitable for your device). The only restriction, while installing stock ROM (not custom!), is that BUILD_SW_PROJ field in update_ver.txt file of already installed ROM and BUILD_SW_PROJ field in update_ver.txt file inside update1.zip/update.zip package on SDCard should be equal.
What are the differences between G1315 RootROM and stock ROM?
In general, a custom ROM may differ from a stock ROM in everything ranging from the custom user interface to the modified kernel.
These are the differences of G1315 RootROM comparing to the stock ROM:
disabled BUILD_SW_PROJ check in the update script;
ROM is already rooted;
added BusyBox 1.19.4;
adbd runs with root permissions and "USB Debugging" is turned on for logging of the boot process by default;
G1315 RootROM preserves SliPer ModRecovery on ordinary boot for further use (if stock ROM is installed, on each ordinary boot recovery partition is being rewritten with the original recovery image formed by patching original boot image with binary diff file recovery-from-boot.p).
Interface and kernel are derived from the original ROM.
Will I lose the warranty after installing G1315 RootROM by using SliPer ModRecovery?
Before calling for service install G1315 RootROM for your region, then install original ROM for your region. This is required to restore original ROM and recovery. After that clear cache and erase userdata by using stock recovery, remove SDCard from the device.
How to install G1315 RootROM?
NO userdata will be erased during G1315 RootROM installation process, but it would be better to backup your valuable data anyway!
You should install smartphone drivers if they haven't been installed yet.
It's important that you DON'T need root privileges to install G1315 RootROM by using SliPer ModRecovery.
Download one of G1315 RootROMs:
G1315-0.50.3_pl_cz.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Eng/
G1315-0.50.3_RUS.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Ukraine/
G1315-0.50.4_Vobis.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Russia/
G1315-0.50.6_CHT.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Taiwan/
Then copy update1.zip/update.zip from archive to the root of SDCard which will be used to update ROM.
Download ModRecovery_BootScript.zip and unpack it somewhere to your PC. This is a "script" for booting up smartphone with recovery.img in fastboot mode. "Script" file flasher.bat itself is located in ModRecovery_BootScript folder. Extract recovery.img suitable for your G1315 from previously copied to SDCard update1.zip/update.zip archive to ModRecovery_BootScript folder.
Then turn off your device, insert SDCard (with update1.zip/update.zip located in SDCard root directory) into it, turn the device into fastboot mode by holding volume down button + power button until blue LED blinks once. Then connect the device to PC, wait until fastboot mode drivers will be completely installed and run flasher.bat. Confirm the update. Smartphone will reboot once during the installation process and boot up in normal mode with SU and BusyBox installed after everything will be completed. Enjoy!
In order to check whether you've got SliPer ModRecovery properly installed, delete/move update1.zip/update.zip from the root of SDCard, reboot in recovery mode by holding volume up button + power button until blue LED blinks 3 times. If you get the following screen, then SliPer ModRecovery has been installed properly:
{
"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"
}
Donations
All donations are strictly voluntary. But I really appreciate any help, because I've got some financial troubles now.
PayPal
Donate
WebMoney Transfer
Z135745021429
E301654453478
R160707042034
U897012425686
QIWI Wallet
9167226205
Yandex Money
410011384134846
--------------------
ROMs and ModRecoveries for other Gigabyte Dual-SIM Android phones:
[ROM][RECOVERY]SliPer ModRecovery + G1310 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1317D RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1345 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1355 RootROM

Thank you very very very very muuuuuch
sliper123 said:
SliPer ModRecovery and G1315 RootROM. What are they?
SliPer ModRecovery is a custom Andriod system recovery. G1315 RootROM is a custom ROM for Gigabyte GSmart G1315 smartphone with Dual-SIM support. Several versions of G1315 RootROM correspond to different builds, each designed for a specific region or reseller.
What are the differences between SliPer ModRecovery and stock recovery?
The only difference between SliPer ModRecovery and stock recovery is that during ROM installation process Gigabyte signature verification is disabled in SliPer ModRecovery. So you're able to install any stock/custom ROM (suitable for your device). The only restriction, while installing stock ROM (not custom!), is that BUILD_SW_PROJ field in update_ver.txt file of already installed ROM and BUILD_SW_PROJ field in update_ver.txt file inside update1.zip/update.zip package on SDCard should be equal.
What are the differences between G1315 RootROM and stock ROM?
In general, a custom ROM may differ from a stock ROM in everything ranging from the custom user interface to the modified kernel.
These are the differences of G1315 RootROM comparing to the stock ROM:
disabled BUILD_SW_PROJ check in the update script;
ROM is already rooted;
added BusyBox 1.19.4;
adbd runs with root permissions and "USB Debugging" is turned on for logging of the boot process by default;
G1315 RootROM preserves SliPer ModRecovery on ordinary boot for further use (if stock ROM is installed, on each ordinary boot recovery partition is being rewritten with the original recovery image formed by patching original boot image with binary diff file recovery-from-boot.p).
Interface and kernel are derived from the original ROM.
Will I lose the warranty after installing G1315 RootROM by using SliPer ModRecovery?
Before calling for service install G1315 RootROM for your region, then install original ROM for your region. This is required to restore original ROM and recovery. After that clear cache and erase userdata by using stock recovery, remove SDCard from the device.
How to install G1315 RootROM?
NO userdata will be erased during G1315 RootROM installation process, but it would be better to backup your valuable data anyway!
You should install smartphone drivers if they haven't been installed yet.
It's important that you DON'T need root privileges to install G1315 RootROM by using SliPer ModRecovery.
Download one of G1315 RootROMs:
G1315-0.50.3_pl_cz.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Eng/
G1315-0.50.3_RUS.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Ukraine/
G1315-0.50.4_Vobis.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Russia/
G1315-0.50.6_CHT.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Taiwan/
Then copy update1.zip/update.zip from archive to the root of SDCard which will be used to update ROM.
Download ModRecovery_BootScript.zip and unpack it somewhere to your PC. This is a "script" for booting up smartphone with recovery.img in fastboot mode. "Script" file flasher.bat itself is located in ModRecovery_BootScript folder. Extract recovery.img suitable for your G1315 from previously copied to SDCard update1.zip/update.zip archive to ModRecovery_BootScript folder.
Then turn off your device, insert SDCard (with update1.zip/update.zip located in SDCard root directory) into it, turn the device into fastboot mode by holding volume down button + power button until blue LED blinks once. Then connect the device to PC, wait until fastboot mode drivers will be completely installed and run flasher.bat. Confirm the update. Smartphone will reboot once during the installation process and boot up in normal mode with SU and BusyBox installed after everything will be completed. Enjoy!
In order to check whether you've got SliPer ModRecovery properly installed, delete/move update1.zip/update.zip from the root of SDCard, reboot in recovery mode by holding volume up button + power button until blue LED blinks 3 times. If you get the following screen, then SliPer ModRecovery has been installed properly:
Donations
All donations are strictly voluntary. But I really appreciate any help, because I've got some financial troubles now.
PayPal
Donate
WebMoney Transfer
Z135745021429
E301654453478
R160707042034
U897012425686
QIWI Wallet
9167226205
Yandex Money
410011384134846
--------------------
ROMs and ModRecoveries for other Gigabyte Dual-SIM Android phones:
[ROM][RECOVERY]SliPer ModRecovery + G1310 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1317D RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1345 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1355 RootROM
Click to expand...
Click to collapse
THANK YOU, YOU SAVE MAY DAYS... It almost 2 weeks i''ve been stressed to find a way on how to make my Nexian Cosmic Journey aka Gsmart G1315 back to fully fuction again. I was just about want to throw away and break it. And finally i see this tutorial...
I will remember you always "sliper123"... I want to open paypal account and donate you... ONCE AGAIN, THANK YOU, YOU SAVE MAY DAYS...

Hi sliper, where do i could find fastboot driver for gsmart g1315 ???
thank you before...

BLU DASH 5.0 D410a Stock ROM Images + Root + TWRP

STOCK ROM IMAGES BLU DASH 5.0 D410a V27-GENERIC Android Kitkat 4.4.2 MT6572 Chipset (no UBIFS)
PLEASE READ THE INSTRUCTIONS BEFORE FLASHING YOUR PHONE SO THAT YOU WON'T BRICK IT.
EDIT: 14 January 2015. Updated the TWRP 2.8.2.0 download link. Fixed the problem where ADB and MTP was not functioning in TWRP. Added backup support for a few other partitions including the Baseband.
EDIT: 19 January 2015. Changed method of rooting and added flashable zip with modified kernel to add init.d support (that was tested and is functioning properly.)
STEP 1
BACKUP YOUR MEDIATEK DEVICE
Prerequisites
All of the software is for Windows.
Download and Extract the MTK USB Drivers and the SP Flash Tool found closest to the top of the list at:
http://mtk2000.ucoz.ru/
Press the play button to the right of the file to start the download.
Download MTK Droid Root & Tools
Latest version can be found by following the link of the following post.
http://forum.xda-developers.com/showpost.php?p=38320254&postcount=1
Hint: Click the show content button to see the link to another forum with the download link
Direct Download Link of MTK Droid Root & Tools if you are having problems getting the link.
http://depositfiles.com/files/ne1gnposp
You will need Winrar to extract the files.
That can be downloaded from: http://www.rarlab.com/download.htm
READ HERE ON HOW TO BACKUP: http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Thanks to @rua1 for the instructions and software.
NOTE: I WOULD RECOMMEND BACKUPING UP THE USRDATA PARTITION AS WELL TO DO THAT USE HEX "0X96B40000" AS THE LENGTH DURING READ BACK IN SP FLASH TOOL
To flash the DASH 5.0 you need to use the Preloader to do it.
STEP 2
Installing the Preloader Driver (READ this section entirely before trying)
Open Device Manager
Start -> Run
Type:
Code:
devmgmt.msc
Press Enter
Turn off the phone until it is completely shut down with nothing plugged in the USB port. You will see the screen go black and shortly afterwards it will vibrate.
With Device Manager open, connect the USB cable to the phone without turning it on.
You will see the MT65XX Preloader appear (see image)
{
"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"
}
Quickly double click MT65XX Preloader before it disappears, if it disappered, just unplug and plug back in the cable and try again.
Under the Driver tab, click Update Driver, click Browse my computer for driver software.
Using the Browse button find the MTKUSBAll folder you extracted and click on "New inst. win 7&8x64" and click OK
Click Next
If you get the message "Windows can't verify the publisher of this driver software", just click "Install this driver software anyway"
Click Close
Click Close
After the driver is installed you can unplug the phone.
STEP 3
Uploading the image files to the phone{/B}
WARNING: The BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip file has all of the necessary images but do not flash them unless you trying to recover from a brick.
DO NOT FLASH THE PRELOADER.BIN AS IT MAY BRICK YOUR PHONE.
THE ONLY FILES I HAVE PERSONALLY TESTED ARE boot.img, factory_NONmodified_recovery.img and system.img
Download BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip from here:
http://d-h.st/3L9G
See Step 5
Extract the SP Flash Tool.
Extract the system.img and MT6572_Android_scatter.txt (and/or boot.img and factory_NONmodified_recovery.img, if you wish)
Open the SP Flash Tool
Click the Download tab
Click the Scatter-loading button and select the MT6572_Android_scatter.txt file.
Click the location of ONLY the parition(s) you are going to flash: ANDROID = SYTEM partition (system.img), BOOTIMG = KERNEL (boot.img) and RECOVERY=RECOVERY (factory_NONmodified_recovery.img or custom recovery file)
Select the image file (e.g. system.img or system_rooted.img)
MAKE SURE ALL OTHERS ARE NOT TICKED
Click the Download button.
Plug in the phone or unplug and plug it back in to start flashing the images to the phone.
Note: This can also be done with the battery removed.
Your phone will have root.
STEP 4 - Adding TWRP
First we need to rename the file recovery-from-boot.p found in the /system folder.
Using a File Manager with root permissions rename
Code:
recovery-from-boot.p
to
Code:
recovery-from-boot.bak
OR
From an adb shell, rename the file
Code:
su
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
Now turn off the phone and with SP Flash Tool flash TWRP 2.8.2.0. Download link below.
NOTE: Select only the RECOVERY partition to flash. TWRP themes are supported as well as the Aroma File Manager.
http://d-h.st/aQmt
STEP 5 - Rooting and adding init.d support
Go to http://download.chainfire.eu/supersu
Download the latest SuperSU.
Go to http://d-h.st/AJQ
Download the init.d support zip file.
Boot to TWRP while connected to a PC with adb tools run the command
Code:
adb reboot recovery[/url]
OR
Hold down the power select Reboot and hold down the volume up button until you see the TWRP logo.
Via the install menu, flash the SuperSU zip and inti.d support zip.
ALL DONE!
THANKS:
[user=631273]@Chainfire[/user] for SuperSU
[user=5119815]@rua1[/user] for MTK Droid Root & Tools and instructions on how to use SP Tools
[user=4478781]@yuweng[/user] for creating the tool to make TWRP for MediaTek devices
[user=912474]@Dees_Troy[/user] for TWRP

I will give a brief explanatoin and will elaborate more when I have the time.
For Root:
Thanks to @Chainfire
I basically mounted the system.img in a Linux OS and copied the files from the SuperSU v2.36 zip file and placed them in their relevant directories added the relevant permissions, etc.
For init.d scripts
Thanks to @alireza7991
See his thread: http://forum.xda-developers.com/showthread.php?t=2287540
I modified the kernel to boot and created a flashable zip that adds busybox to /system/xbin and creates the necessary folders then flashes the modified kernel.
For TWRP:
Thanks to @yuweng
I used Easy Magic TWRP Installer for MTK. See http://forum.xda-developers.com/showthread.php?p=53752834#post53752834
It worked but changed my partition information for some reason even though the size fit my paritition size. I wiped my phone and lost my baseband and recovered it. Posted a new thread on how to do that. See http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
That is why I posted the image file so no one has to face that problem too. I tested it and it is functioning without any problems.
You can follow yuweng's thread to make it smaller if your partition size is smaller than 6MB for some phones, at a cost of course.

Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh

After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.

jorgefar said:
After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.
Click to expand...
Click to collapse
What procedure did you use to flash it?

SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok

jorgefar said:
SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok
Click to expand...
Click to collapse
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img

Thanks for you le answer! Thats right, is a Blu Dash 5.0 D410a, I try on Monday the suggested and post results!!!

Hi again, flashed system and recovery only, stuck on Blu screen again, try wipe and reset cache, stuck on screen Blu,any recomendation??

Added a flashable zip to add init.d and install LInk2SD with a modified mount script to run properly on this phone, BLU DASH 5.0 D420a running V27 Android 4.4.2.
See post #3

dechronic said:
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img
Click to expand...
Click to collapse
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.

Sexyr said:
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.
Click to expand...
Click to collapse
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.

dechronic said:
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.
Click to expand...
Click to collapse
Cool got it and am on v27 now. thanks..... now if ony there were other roms for it ah well, at least i'm rooted again with recovery.

can i flash this on BLU Dash 5.0 D400a

dechronic said:
Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh
Click to expand...
Click to collapse
This say file no longer available..could it be downloaded elsewhere?

Does this work on 5.0+?

Stiffymeister said:
Does this work on 5.0+?
Click to expand...
Click to collapse
Don't think so but I think I have a 5.0+ image. Anything in particular you looking for? I should be able to provide it tomorrow

i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27

dlongnasty said:
i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27
Click to expand...
Click to collapse
I probably need to redo the steps for a couple of the posts.
Download the TWRP at http://d-h.st/aQmt
Upload it to the phone. Make sure that only recovery is ticked in the Smart Phone Flash Tool (SP Flash Tool) and select the file you downloaded. You should be able to figure out the rest based on my instructions.
Flash SuperSU which can be downloaded from http://download.chainfire.eu/supersu
It will rename the file that would put back the original recovery.
That should be it.

got it working thanks. are their any custom roms for the d410a?

[MOD][WIP] MultiROM v33

Introduction
{
"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 Xiaomi Mi4i. 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
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
You can install it either from MultiROM Manager app or from this guide:
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM - download the ZIP file from second post and flash it in recovery.
Modified recovery - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb 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
Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.​
Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.​
Thanks a lot to Tasssadar for creating this awesome utility.
XDA:DevDB Information
MultiROM for Mi4i, Tool/Utility for the Xiaomi Mi 4i
Contributors
haikalizz
Source Code: https://github.com/webhaikal/android_device_xiaomi_ferrari-twrp
Version Information
Status: Alpha
Created 2015-12-11
Last Updated 2017-06-07

Reserved
Downloads
MultiROM : https://transfer.sh/Lz0kx/multirom-ferrari.zip
Modified Recovery : https://transfer.sh/fILcp/recovery-mr-ferrari.img
MultiROM Uninstaller : Coming Soon
Supported Kernels
This kexec-less multirom

Reserved
FAQ and other notes
About security​In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.​
What do the ROMs share?​All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​
How many ROMs can I have?/Where are the ROMs stored?​You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.​
Where can I find files from other ROMs?​http://forum.xda-developers.com/mi-4i/general/index-xiaomi-mi4i-roms-kernels-toolkits-t3187438​
Can I have different versions of Android working alongside? How to use Lollipop and Marshmallow at the same time?​Yes. The systems are separated.​
The menu with all the ROMs won't show up during boot, how to fix it?​Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.​
The boot animation shows after a few seconds on primary ROMs, why?​Because the framebuffer gets blanked for a few seconds after it gets closed by MultiROM.​
Can I use MultiROM without root?​Yes, if you don't use MultiROM Manager app but flash everything manually​
Will I get OTAs when I have MultiROM installed? Do I lose secondary ROMs after an OTA?​Probably not, you will have to install them manually and you'll have to reinstall MultiROM
No, you won't lose secondary ROMs​
My secondary ROM doesn't boot, what should I do?​Probably you forgot to inject current boot sector once, MultiROM didn't run, so /data SELinux context is set to secondary ROMs that are in /data/media so secondary /system has /data contexts.
Go into recovery Advanced > MultiROM > List ROMs > Choose the non booting ROM > Run restorecon
This will fix SELinux contexts and the ROM will boot again​

Will this work for cm13 and MIUI 7 as they have different partition tables.

sykomaniac said:
Will this work for cm13 and MIUI 7 as they have different partition tables.
Click to expand...
Click to collapse
Haven't tested with Miui but CM and CM works...

hello friends which is the best rom with reduce heating issue and best battery back up?

jai25993 said:
hello friends which is the best rom with reduce heating issue and best battery back up?
Click to expand...
Click to collapse
Wrong thread Ask this question in Q&A thread please.

jai25993 said:
hello friends which is the best rom with reduce heating issue and best battery back up?
Click to expand...
Click to collapse
@jai25993: Please, don't spam the thread, your question have no any relation with this thread, you should ask this in Xiaomi MI 4i Q&A section.
I am a person who always prefered multi boot on computer, and who like to play with OS's. At this moment, I have four GNU/Linux distros, one Windows and one Android x86 installed on my laptop hdd, and can't belive that finaly can try similar things on my phone.
Thanks to dev(s), and God bless you
EDIT:
haikalizz said:
You can install it either from MultiROM Manager app or from this guide:
Click to expand...
Click to collapse
I installed MultiROM Manager app, and app said "ferrari is not suported":
Is it safe to try manually, is somebody try allready?

Awesome ! Great job !! waiting for report of Miui / Polska / Pro + CM rom combination..

stiw47 said:
EDIT
I installed MultiROM Manager app, and app said "ferrari is not suported":
Is it safe to try manually, is somebody try allready?
Click to expand...
Click to collapse
It's safe though, the app still hasn't recognised our phone yet..

I uploaded a new recovery image. Old one wasn't built with multirom... My mistake, sorry.

stiw47 said:
@jai25993: Please, don't spam the thread, your question have no any relation with this thread, you should ask this in Xiaomi MI 4i Q&A section.
I am a person who always prefered multi boot on computer, and who like to play with OS's. At this moment, I have four GNU/Linux distros, one Windows and one Android x86 installed on my laptop hdd, and can't belive that finaly can try similar things on my phone.
Thanks to dev(s), and God bless you
EDIT:
I installed MultiROM Manager app, and app said "ferrari is not suported":
Is it safe to try manually, is somebody try allready?
Click to expand...
Click to collapse
sorry dear i will be careful in next time

Push to github and link them ! Good job

haikalizz said:
I uploaded a new recovery image. Old one wasn't built with multirom... My mistake, sorry.
Click to expand...
Click to collapse
I didn't try first uploaded (wrong) recovery image, but I think that new one, aka second uploaded, is not good. I was try to flash several times, either via Flashify, Rashr or fastboot, I downloaded again, and flash again via all above tools, everytime flash is succesful, and every time i got only black MI splash screen, when I try to boot to recovery (no recovery screen). If I execute "adb devices" in that moment, I got recognized device with number (List of devices attached *some number* recovery), and yes, it says is in recovery, but no recovery screen on phone.
Did you try your method? Is it working with you?
I am on Ressurection Remix if that is meather (I think no), and using TWRP Mi4i by magdag.
P.S. Can you be more specific in which order we should install a files? I think:
1. MultiROM .zip
2. Modified recovery
3. Sensei kernel
4. Second ROM
Am I wrong?

stiw47 said:
I didn't try first uploaded (wrong) recovery image, but I think that new one, aka second uploaded, is not good. I was try to flash several times, either via Flashify, Rashr or fastboot, I downloaded again, and flash again via all above tools, everytime flash is succesful, and every time i got only black MI splash screen, when I try to boot to recovery (no recovery screen). If I execute "adb devices" in that moment, I got recognized device with number (List of devices attached *some number* recovery), and yes, it says is in recovery, but no recovery screen on phone.
Did you try your method? Is it working with you?
I am on Ressurection Remix if that is meather (I think no), and using TWRP Mi4i by magdag.
P.S. Can you be more specific in which order we should install a files? I think:
1. MultiROM .zip
2. Modified recovery
3. Sensei kernel
4. Second ROM
Am I wrong?
Click to expand...
Click to collapse
You're right on the order. About the recovery, both versions didn't have UI... I'm guessing some ui scripts didn't compiled... Need to check.

haikalizz said:
You're right on the order. About the recovery, both versions didn't have UI... I'm guessing some ui scripts didn't compiled... Need to check.
Click to expand...
Click to collapse
So what now? Can we use this recovery without ui on some way via adb/terminal (or some other way, I don't know), or we should waiting for ui fix?

Don't know how to use it without the ui though, no harm trying. I've pm'ed the multirom dev for any info on this...

Account removal
Deleted

Is it whole this method usable at this moment. How? (without gui in recovery)?

I may have found an error in the TWRP compiled for multirom... Can't get a logcat to actually ensure it but compiling TWRP from omnirom works just it doesn't have the multirom features