Related
DISCLAIMER I (or any contributor) cannot be held responible in any way for any sort of damage caused for using this ROM or its derivatives.
This is the AOSP-based Android 4.1.1 Jellybean ROM using custom kernel 3.0 for Herotab C8/Dropad A8/Haipad M7/iBall Slide and compatible tablets.
The Herotab C8 and its siblings are one hackable device; It supports Android 2.2, 2.3, 3.0, 3.2, 4.0, and 4.1. It runs on a single-core Samsung S5PV210 1Ghz Processor and 512mb RAM. Pretty low spec, however with the right tinkering it can be one powerful device.
What works:
Display
Hardware acceleration
Touchscreen (thanks violet's ft506 driver and przemo27 for figuring the alternate data format)
Audio\Microphone (thanks to Asure's CM7 build for audio HAL; and mg3100's details on kernel)
Wi-Fi (thanks to violet's ar6000 driver and jolocotroco for locating source for a wpa_supplicant8 dependency)
Bluetooth
Accelerometer (thanks to Asure's port of mango210 kernel)
Battery Indicator
USB Host
USB OTG
Camera
Market, GoogleApps
Root
What does not work:
HDMI
3G dongle
(NOTE This list is not exhaustive; this build is still a Beta and not intended to be a daily driver)
Steps for flashing (using script; this will make 512MB system, 256MB cache and 1GB data partition and erase your existing settings and apps):
Extract the archive. You will get two files, one will be a GZipped tar (.tgz) and other the kernel (zImage). Copy these to the root of an external SD.
Download the attachment posted here and extract them to the root of the external SD. You should now see 6 files in the root of the external SD. (utscript, utscript_sd, utscript.sh, zImage.debug, zImage, rootfs.tgz).
Insert the SD card and boot your tablet using Menu+Power. This will flash your tablet.
Steps for flashing (using custom recovery):
Extract the archive. You will get two files, one will be a GZipped tar (.tgz) and other the kernel (zImage). Copy these into a folder (path muwst have no spaces) in your external SD card.
Boot into custom recovery.
Go to "Advanced", then "Partition SD card". Select partition sizes (make sure system partition > 320MB) and wait for it to format the partitions. Existing settings and apps will be lost.
[You can skip this step if your tab's system partition is > 320 MB]
Now return to the main menu, and select "Flash ROM". Give it the path where you stored the ROM in step 1. Wait for it to flash the ROM.
Return to main menu and select "Shutdown".
Turn on your tablet normally, and enjoy!
Links:
http://www.embedupload.com/?d=85OERSGVNV (Embedupload)
NOTE: I didn't make this ROM. The guys over at slatedroid did it, so credits all go to them. But you can thank me for sharing
Custom recovery for herotab c8
DISCLAIMER. Use this at your own risk. I will not be responsible for any damage\brick caused by using this recovery.
Currently this is a Beta and all functionality has not been thoroughly tested.
This is a custom recovery modeled on CWM recovery (built on the custom kernel based on Urbetter's source) for Herotab C8/Dropad A8/Haipad M7/iBall Slide i7011/Coby 7024 and equivalent tablets. It should also work on Coby 8024/1024 tablets.
The recovery is built to be compatible (as much as possible) with existing firmwares (stock as well as custom) and patches (again stock as well as those found in custom ROMs). The reason you might want to use this recovery to flash is that:
Its safer (bootloader, etc. are not touched so greatly reduced probability of bricking)
It does not erase your data partition (so Apps and Settings are carried over)
It maintains your existing partition layout (you can change if wanted)
In order to try this recovery,
Download BootExtRecovery.zip attached to this post.
Download the recovery zip from the GitHub link below
Extract both zip files to the root of an external SD card.
Boot your tablet using Menu+Power
This will boot the recovery externally (i.e. unless you actually do something using the recovery, your tablet will be completely unmodified). After the recovery boots and menus work, you may flash the recovery into your tablet (using "Partitions and Storage" menu). Flashed this way, the recovery can be booted into whenever both your SD cards don't have a "utscript" file (otherwise the script is executed instead of starting recovery).
Download: https://github.com/namko/midRecovery/downloads
Source: https://github.com/namko/midRecovery
Key assignments:
Herotab C8/Dropad A8/Haipad M7/iBall Slide -- HOME to select, MENU/BACK to scroll
Coby 7024 -- HOME to select, POWER to scroll
Function list:
Flash ROM - Flashes the ROM on SD card (external or internal) located in a specific folder.
This does not erase 'data' partition. If you downgrade Android, make sure to erase the 'data' partition (or at least erase dalvik-cache from advanced menu) for maximum compatibility.
This does not repartition the internal SD, so if you want a different layout, make sure to change before flashing.
This flashes only the kernel (no other partition e.g. logo, recovery, boot arguments, boot loader)
Apply patch/update - Prompts you to select a patch/update to apply.
Wipe data/factory reset - Erases the 'data' partition. This is equivalent to doing a factory reset.
Wipe cache - Erases the 'cache' partition.
Backup/Restore - Create a new backup (system = firmware, data = your settings/apps) or restore a previously created backup. Essentially this is a NANDROID backup.
Partitions/Storage - To backup or flash individual partitions (e.g. logo, kernel, recovery, boot arguments, bootloader, etc.)
Advanced - To repartition the internal SD card, erase Dalvik-cache, view log, etc.
You can flash ROM (or apply updates) from .ZIP files as well; but it doesn't support the "standard" format because they sometimes contain executables that must be executed to properly apply the patch.
Fixes and patches
Kernel fix (just update it via recovery -> apply patch/update -> update kernel):
http://www.4shared.com/zip/M_ZcGiSF/zImage.html
Wifi Patch:
http://www.4shared.com/zip/3T9hUxnt/wifipatch.html
Here's a patch implementing changes suggested by jolocotroco. To apply this patch:
Extract the zip into your external SD card (anywhere)
Boot into recovery
Select "Apply patch/update"
Select the extracted file ("wifi.patch.tgz")
Reboot after applying patch
It is also possible to apply the patch using adb. Remember to stop WiFi first. This will apply the patch and reboot your device.
adb push wifi.patch.tgz /mnt/sdcard
adb shell
su
mount -o rw,remount /
mount -o rw,remount /system
stop wpa_supplicant
stop hostapd
tar xvf /mnt/sdcard/wifi.patch.tgz -C /
reboot
Click to expand...
Click to collapse
bump
don't work
no one of this patch is recognized by the recovery...
also the kernel update is not a tgz file...
maybe i did a mistake?
j.valeron said:
no one of this patch is recognized by the recovery...
also the kernel update is not a tgz file...
maybe i did a mistake?
Click to expand...
Click to collapse
It should work, what steps did you took to install the kernel?
Custom Recovery for C8/A8/M7
I nearly forgot this. Sorry.
DISCLAIMER. Use this at your own risk. I will not be responsible for any damage\brick caused by using this recovery.
Currently this is a Beta and all functionality has not been thoroughly tested.
This is a custom recovery modeled on CWM recovery (built on the custom kernel based on Urbetter's source) for Herotab C8/Dropad A8/Haipad M7/iBall Slide i7011/Coby 7024 and equivalent tablets. It should also work on Coby 8024/1024 tablets.
The recovery is built to be compatible (as much as possible) with existing firmwares (stock as well as custom) and patches (again stock as well as those found in custom ROMs). The reason you might want to use this recovery to flash is that:
Its safer (bootloader, etc. are not touched so greatly reduced probability of bricking)
It does not erase your data partition (so Apps and Settings are carried over)
It maintains your existing partition layout (you can change if wanted)
In order to try this recovery,
Download BootExtRecovery.zip attached to this post.
Download the recovery zip from the GitHub link below
Extract both zip files to the root of an external SD card.
Boot your tablet using Menu+Power
This will boot the recovery externally (i.e. unless you actually do something using the recovery, your tablet will be completely unmodified). After the recovery boots and menus work, you may flash the recovery into your tablet (using "Partitions and Storage" menu). Flashed this way, the recovery can be booted into whenever both your SD cards don't have a "utscript" file (otherwise the script is executed instead of starting recovery).
Click to expand...
Click to collapse
Github:
https://github.com/namko/midRecovery/downloads
BootExtRecovery:
http://www.4shared.com/zip/HxPitG3B/BootExtRecovery.html
mid recovery is not working on 8024
the recovery is not working on 8024, i have just a black screen...
please help
Sorry it is working...
Now we have Jelly Bean 4.2 form SlateDroid
Please refer for the following hyperlink
http://www.slatedroid.com/topic/42771-romcm101android-421-build-1/
[WORKING]
- Audio
- Video
- Wifi
- Touchscreen
- Most regular things
[NOT WORKING]
- Bluetooth
- 3G
awesome will try it on my dropad A8 its a shame hdmi is not working
I am proud to present the first dual boot project for the Xiaomi Redmi3s/3sp/3x .This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here: https://gist.github.com/chenxiaolong...281941433ec54d
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
How to use the patcher:-
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting:-
Before doing anything, download the Dual Boot Patcher app from the download section below.
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.
Dual: Dual/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 Redmi 3S, 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 card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
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.
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.
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 recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/show....php?t=2491299
DOWNLOADS:-
https://dbp.noobdev.io/downloads/
NOTE:-
I AM NOT RESPONSIBLE IF ANYTHING HAPPENS TO YOUR DEVICE.USE AT YOUR OWN RISK.THIS IS PERSONALLY TESTED BY ME SO IT SHOULD NOT CREATE ANY PROBLEM IF YOU FOLLOW THE STEPS ABOVE PROPERLY
ENJOY
PROPER STEPS (Thnx @Vilo76)
<b>Basic Requirements:<br />
</b>Unlocked Bootloader, TWRP installed, Flash SU (Root),DualBOot patcher app and ur secondary roms<br />
<br />
<b>Must Follow Instructions:</b><br />
in TWRP-->Wipe-->FORMAT DATA-->type "yes" <br />
<b>NOTE 1:</b> this will decrypt ur DATA partition and u will lose all ur installed apps and Internal Memory as well<br />
if u want ur current rom data then BEFORE FORMATTING DATA plz take a twrp backup of ur rom into sd card and restore the data via twrp after decrypting data<br />
<br />
After decrypting the data, boot the Rom and follow the OP instructions: <br />
<br />
1. Install DualBootPatcherAndroid-9.1.0.r191.g3ee92131-snapshot.apk under the primary ROM and launch it<br />
2. If it ask for patching the Kernel, answer YES<br />
3. In the left menu, launch "Patch ZIP"<br />
4. Clic + in the bottom right and select "Add flashable zip"<br />
5. Select the ZIP file of the ROM you want to install<br />
6. As partition, select "DATA", give it a name, continue and select the destination folder<br />
7. After successful patch, go into ROM menu and add the previous patched ZIP (keeping the destination)<br />
8. Clic the TIC at the top right, and wait until green lines of text are displayed saying all is done with success, then go back with phone button<br />
9. Once installed, the new ROM becomes automatically the ROM to boot on<br />
10. In the left menu, choose "reboot", if all works, you should boot inside the new ROM
Click to expand...
Click to collapse
<br />
<b>NOTE 2:</b> Remove ur lock screen protection(PIN,Pattern,Password,FP.....) before flashing/booting into secondary rom
XDA:DevDB Information
[PATCHER][APP] DUAL BOOT PATCHER FOR REDMI 3S/3X/3SP, Tool/Utility for the Xiaomi Redmi 3S
Credits :- @chenxiaolong for adding it
Contributors
akshat2012, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Snapshot
Created 2017-02-18
Last Updated 2017-02-18
@akshat2012 Will switching ROMs take a lot of time? Or is it just like a reboot? What would you recommend I install the secondary Rom to if I wanted to dual boot Miui and Lineage os?
MPJINFiNiTE said:
@akshat2012 Will switching ROMs take a lot of time? Or is it just like a reboot? What would you recommend I install the secondary Rom to if I wanted to dual boot Miui and Lineage os?
Click to expand...
Click to collapse
it doesn't take long to boot.yeah its just a reboot . use lineage os as secondary .first boot wlil take time
akshat2012 said:
it doesn't take long to boot.yeah its just a reboot . use lineage os as secondary .first boot wlil take time
Click to expand...
Click to collapse
Okay where must I install it "to", as in which partition? Miui takes a lot it space in system I guess.
MPJINFiNiTE said:
Okay where must I install it "to", as in which partition? Miui takes a lot it space in system I guess.
Click to expand...
Click to collapse
data partition is recommended
WARNING
blablabla edited, see dev explaination below
Aronuser said:
WARNING
From what I heard, people testing this early version faced some errors.
Actually from what I know, some (one or more) bricked their devices because of it.
This should be just a temporary warning from my side, throught people who tried it.
I recommend to wait a little longer until the dev cleared up the situation and/or fixed the patcher.
Thanks a lot anyway for the hard work to the dev.
Click to expand...
Click to collapse
The phone won't get bricked by this -.-.You are only playing with system partition which can't brick the phone .Anyway I will upload a video of properly dual boot the phone
Sent from my Redmi 3S using Tapatalk
Thanks for the bootloop....
-__-
akshat2012 said:
The phone won't get bricked by this -.-.You are only playing with system partition which can't brick the phone .Anyway I will upload a video of properly dual boot the phone
Sent from my Redmi 3S using Tapatalk
Click to expand...
Click to collapse
I see, excuse me. I just wanted to protect people, because uknowwho had bricked his phone, and others said it was because of this.
Works well however flashing the secondary on system causes bootloop flashed on data partition
In app flashing is recommended
Aronuser said:
I see, excuse me. I just wanted to protect people, because uknowwho had bricked his phone, and others said it was because of this.
Click to expand...
Click to collapse
Nobody can't brick there phone by this . Max to max it will get bootlooped or ROM will get corrupted :v . Ik oh whom you are talking about . His phone was not hard bricked. It was something else.
Sent from my Redmi 3S using Tapatalk
awesumahti said:
Thanks for the bootloop....
-__-
Click to expand...
Click to collapse
-__- Pls flash on data partition and update ramdisk and set kernel before flashing other rom.In app flashing is recommended
Sent from my Redmi 3S using Tapatalk
My Redmi 3s Land boots in TWRP after flashing LineageOS 13. Any help?
neerajsain said:
My Redmi 3s Land boots in TWRP after flashing LineageOS 13. Any help?
Click to expand...
Click to collapse
You mean, after installing it as a secondary ROM?
Yes, after installing secondary ROM on data partition. My phone is now boots in TWRP only.
neerajsain said:
Yes, after installing secondary ROM on data partition. My phone is now boots in TWRP only.
Click to expand...
Click to collapse
Did you set kernel and updated ramdisk before booting
Sent from my Redmi 3S using Tapatalk
Yes, I did set kernel on initial launch of dual boot application. But After secondary ROM installation didn't. Is it required to do set kernel and ramdisk update after secondary rom installation?
Same here :
0. At first APP start, asked to patch kernel, answered yes.
1. Inside DualBootPatcher APP, patched ROM zip file (it was latest Mokee for testing purpose) for DATA slot (named it "mokee")
2. Inside APP, flashed patched zip (keeping destination)
3. Select newly installed ROM, update ramdisk (success)
4. Reboot
5. Bootloop (with 3-4 vibrations), only TWRP accessible (then flashed boot.img to restore primary)
All was done from latest ResurrectionRemix ROM, installed normally via TWRP.
"DualBootPatcher Utilities AROMA" didn't worked at all inside my TWRP (TWRP stalled).
Solved, DATA partition was encrypted. I was sure it wasn't, but it was.
After formating DATA, works like a charm.
@akshat2012 Give proper credits to Chenxiaolong in the OP.
@akshat2012
It asked for encryption password on bootup
Is it normal?
I didn't set password and twrp doesn't ask too (it says decrypted with default password
tnx in advance!
Read the update post if you are updating(click here to go there)
{
"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"
}
What is MultiRom?
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android Rom as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our 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. Roms are installed and managed via the modified TWRP recovery. You can use standard ZIP files to install secondary Android Roms, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Warning!
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is possible that something goes wrong and you will have to re-flash yours current Rom zips again. Make backups. Always!
Features:
MultiBoot any number of Android Roms
Restore Nandroid Backup as secondary ROM
Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
Boot from USB drive Attached via OTG cable (untested)
Compatibility
Theoretically any ROM can be used as primary or secondary, but I only test the bellow scenario:
Nougat Custom ROM Primary and secondary OK
Marshmallow Stock secondary OK
All the other possibilities of ROM are untested, also important encryption wasn't tested yet.
Installation instruction:
Via The MultiRom Manager App:
This is the easiest way to install everything MultiROM needs... Just follow the Below Instructions:
Install the app (MultiROMMgr_Quark_xx.apk) From Download folder
Select MultiROM and Recovery on the Install/Update card.
Press "Install" on the Install/Update card to start the installation.
Done.
You current rom WILL NOT be erased by the installation.
Manually via TWRP
Download the files
Install the Multi_ROM TWRP just like normal TWRP, check norma TWRP installation instructions in case of doubt
Flash MultiROM.zip in the primary ROM
Reboot to recovery and start using it
On secondary if Custom ROM and you have bootloop problem flash the Quark_Multi_ROM_FIX_CustomROM_V_1_0.zip to the secondary ROM
Download Folder Click here
Files description:
MultiROMMgr_APP_Quark_xx.apk MultiROM manager app adapt for Quark
multirom_twrp-X.X.X-mod_X-quark.img Normal TWRP image, but with a TWRP adapted for multiROM
multirom-XXXXXXX-vXX-quark.zip flashable zip of multiROM boot manager interface
multirom_uninstaller.zip flashable zip to remove multiROM boot manager interface and cleanup any secondary ROM
Quark_Multi_ROM_FIX_CustomROM_V_1_0.zip flashable zip, if using latest version of my kernel or Nougat ROM released by bhb27 no need to flash this but if you not, this is temp fix for any custom ROM running old version of my kernel or not as a secondary ROM, eventually this won't be need but to day it is, need to re-flash this in case of a kernel change.
XXXX are related to version and dates
Credits:
Tasssadar -Developer of MultiRom
nkk71 - For his No-KEXEC workaround that allow multi_boot to work without complicated kernel modifications
TWRP and MultiROM source click here and read the README.md
App source click here
Developer donation link:
To donate via paypal click here
No other donation option is available.
Help and etc:
Adding ROMs:
Android
Boot into MultiRom Recovery -> select MultiRom (top right corner menu) -> Add Rom -> Select the Rom's zip file or backup and click Confirm.
Switching ROMs (primary to secondary and vice versa):
To make the boot process faster I recomende to disable boot manager interface from showing on every time the device boot's and enable the "keypress-based boot", to enable it go to TWRP top right corner (Multirom menu on TWRP) > Settings > Auto boot > mark "keypress-based boot" and if you wanna to go to "boot manager interface" durring boot after the device vibrate press and hold volume up
Now to switch ROM the "boot manager interface" can be used just go there and click over the ROM you wanna to boot.
Or use the MultiROM manager app
On the app just open it slid left to right or click on left corner to open the tab menu > Manage ROMs > Click on the ROM > click BOOT
Warning!
Very importante always go back to primary ROM from a secondary before going to another secondary this is to prevent the boot.img of primary be override with the secondary and cause boot problems, in case that happens is always possible to restore a boot.img of primary using TWRP backup or flashing a boot.img that can be found on the ROM.zip of your current ROM
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 unless you wipe internal memory or format Data)
* 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 the Rom, follow these steps:
* Go to MultiRom -> List Roms and select the Rom you want to update.
* Select "Flash zip" and Flash the Rom's zip File.
Explanation of recovery menus:
Main menu
- Add Rom - Add Rom to Boot
- List Roms - List Installed Roms and Manage Them
- Inject boot.img File - When you Update something, for example a Kernel or a ROM, which is Distributed as a Whole boot.img (eg. ROM update zip), you have to use this option on it, otherwise you would lose MultiRom.
- Inject curr. boot sector - Use this option if MultiRom does not show up on boot, for example after Kernel Installation.
- Settings - Well, SETTINGS!
Manage Rom
- Rename, Delete - No Need to Explain this I Think!
- Flash Zip (Only Android Roms) - Flash zip to the Rom, for example GAPPS
- Add/Replace boot.img - Replaces boot.img used by this Rom, this is more like a Developer Option.
In case of a problem related to this project use @bhb27 on a post on this thread.
If anyone test different combinations of primary+secondary and or encryption let me know on the thread.
When we think our phone is going to die... BAM!
THANK YOU!
@bhb27
Your skills will never cease to amaze me my friend, great work!! Now I want to buy another Quark :good:
Wow! Sounds really good. Great job @bhb27
@bhb27 I installed the installation instruction but i think i may have now 2 Nougats. I made a backup of my current system. Installed the multiROM.zip file and then went to add ROM and installed my backup on internal memory. When i rebooted it did the 5 second countdown and i saw boot options internal and my backup. i though nothing of it until it finished booting and it was a barebone Nougat install.
On initial install is the multirom.zip going to be our base zip so i need to do a clean install and TiBU all my apps on to that, and then if i wish, install a second ROM. or can i install my backup on that base internal ROM which is currently a blank Nougat RR? Or did i choose wrong option when installing my backup?
johnbravado said:
@bhb27 I installed the installation instruction but i think i may have now 2 Nougats. I made a backup of my current system. Installed the multiROM.zip file and then went to add ROM and installed my backup on internal memory. When i rebooted it did the 5 second countdown and i saw boot options internal and my backup. i though nothing of it until it finished booting and it was a barebone Nougat install.
On initial install is the multirom.zip going to be our base zip so i need to do a clean install and TiBU all my apps on to that, and then if i wish, install a second ROM. or can i install my backup on that base internal ROM which is currently a blank Nougat RR? Or did i choose wrong option when installing my backup?
Click to expand...
Click to collapse
the multirom.zp doesn't change yours current ROM you did something that cause that, it is just the boot manager support.
on main twrp menu you manage yours primary ROM, on MultiROM menu the extra secondary, you can restore yours backup via normal twrp menu and all must be fine, inject the multiRom boot after restore before reboot.
I push the manager app to download folder, it allow in android changes, direct boot, etc...
when open the app it will point out that the TWRP is out of date, I push a new twrp that is the same as the previously but this "new" one has a version tag that can be see in twrp and by the app that version tag will help with future updates via app.
:good:
This is nice. Kinda like having safestrap again from the Moto Droid Maxx I had before the turbo.
bhb27 said:
I push the manager app to download folder, it allow in android changes, direct boot, etc...
when open the app it will point out that the TWRP is out of date, I push a new twrp that is the same as the previously but this "new" one has a version tag that can be see in twrp and by the app that version tag will help with future updates via app.
:good:
Click to expand...
Click to collapse
:good:
Seven android nougat!!
Links to all those?
Bumpn gums from my vzw DROID Turbo xt1254
---------- Post added at 04:14 AM ---------- Previous post was at 04:13 AM ----------
Which is best? RR I'm sure haha
Bumpn gums from my vzw DROID Turbo xt1254
@bhb27 this is fantastic !! Thanks !!
Never tried custom ROM as using quark as daily driver. This will allow me to try and test Roms.
Which partitions to backup before trying this ?
RSDamasceno said:
:good:
Seven android nougat!!
Click to expand...
Click to collapse
gangrenius said:
Links to all those?
Click to expand...
Click to collapse
I'm sure you are joking? You know they are all the Development section of this forum. Well, except for AOKP, which is over in the Development section of the split "Droid Turbo" forum.
But if you really are serious, then it's always a good idea to keep an eye on this thread:
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
That link is to the most recent post.
Rarely I speak before thinking and this was an occasion
Bumpn gums from my vzw DROID Turbo xt1254
z4ck1n said:
@bhb27 this is fantastic !! Thanks !!
Never tried custom ROM as using quark as daily driver. This will allow me to try and test Roms.
Which partitions to backup before trying this ?
Click to expand...
Click to collapse
system and boot, for ROM only.
system, boot and data if you wanna keep apps and they data...
if you test stock ROM as primary let me know the result.
Fantastic work
It's really great to see that devs are still working on quark. I'm also very excited to see Multi ROM for our device. It would be even more great if someone ports any Linux based OS to our device...
there is no need to flash Quark_Multi_ROM_FIX_CustomROM_V_1_0.zip to a secondary ROM if you have update your secondary to the latest version of the ROM or the kernel that I released...
It worked very well on my Maxx :good:
Thank you!
Is it possible to include the queue function for the secondary ROMs?
bhb27 said:
system and boot, for ROM only.
system, boot and data if you wanna keep apps and they data...
if you test stock ROM as primary let me know the result.
Click to expand...
Click to collapse
I don't want to mess with primary rom (current stock mm). Want to install this over it, without losing data.
My Data is to big to be backup ...
Few Questions
How does multirom work? Does it change boot sector record like normal desktop oses?
In multirom installation which partitions are impacted?
Where is secondary rom installed?
{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for K6 power. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our 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, daily prebuilt image files to install Ubuntu Touch 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
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting, once they are ported to the Moto X Play
* 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 messing with boot sector and data partition. 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
1. Via MultiROM Manager app (We do not have Official Support, so this is not an option for us yet)
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel (If you want to use Kexec) - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual 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.
MultiROM has 3 parts you need to install:
Modified recovery (TWRP.img) - download the IMG file from second post and use fastboot, TWRP or Flashify app to flash it.
MultiROM (multirom.zip) - download the ZIP file from second post and flash it in recovery.
You current rom will not be erased by the installation.
Adding Roms
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive (not tested yet)
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> 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 Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code:
Device tree-https://github.com/karthick111/twrp/tree/karate
MultiROM - https://github.com/multirom-dev
Downloads
Karate: https://www.androidfilehost.com/?w=files&flid=230440
Karatep: https://www.androidfilehost.com/?w=files&flid=230445
FAQ and other notes
Device encryption:
Encryption isn't supported right now. So decrypt your device before using this.
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.
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.
Can I flash secondary roms on Micro SD?
Yes but it's is very slow, internal storage is much better to flash secondary roms.
How do I flash Gapps in Secondary ROMs?
After AddRom and is done, go back and Click on the installed Secondary ROM, you will see one of the option to 'Flash Zip', click and install Gapps. Then you can reboot into secondary ROMs, do gapps installation before rebooting otherwise as usual need to deal with SetupWizard FC, at least thats what I observe in my device.
The thug arrived...
I installed secondary ROM to microSD card but when I boot, it only shows in internal section internal ROM and external section is always refreshing. In MultiROM recovery it says I have secondary ROM installed to microSD card. But how can I boot it if it is not shown?
Thomas_xxxxx said:
I installed secondary ROM to microSD card but when I boot, it only shows in internal section internal ROM and external section is always refreshing. In MultiROM recovery it says I have secondary ROM installed to microSD card. But how can I boot it if it is not shown?
Click to expand...
Click to collapse
It won't work in external sd card. That external spot is for USB & it'll be slow. Better use only internal slot.
dr.bathman said:
It won't work in external sd card. That external spot is for USB & it'll be slow. Better use only internal slot.
Click to expand...
Click to collapse
From FAQ: Can I flash secondary roms on Micro SD?
Yes but it's is very slow, internal storage is much better to flash secondary roms.
So it should work from external SD card.
Thomas_xxxxx said:
From FAQ: Can I flash secondary roms on Micro SD?
Yes but it's is very slow, internal storage is much better to flash secondary roms.
So it should work from external SD card.
Click to expand...
Click to collapse
But sadly not working.
dr.bathman said:
But sadly not working.
Click to expand...
Click to collapse
Hope some update will fix it.
after installing zip mobile goes to download mode so i restore stock boot.img after that mobile boot up bt multi rom not working.any idea ?
raj2k8 said:
after installing zip mobile goes to download mode so i restore stock boot.img after that mobile boot up bt multi rom not working.any idea ?
Click to expand...
Click to collapse
Flash the two files the multirom.zip then the modified twrp edition. Make sure you flash the right file name to your device
firemax13 said:
Flash the two files the multirom.zip then the modified twrp edition. Make sure you flash the right file name to your device
Click to expand...
Click to collapse
i flashed both zip n img but its not working even i tried both karate n karatep bt same problem.
I have LineageOS 15.0 installed as primary ROM. Then in recovery I added OmniROM as secondary, I tried to boot it via multirom boot menu but then screen went black, LED diode was turned on even disconnecting mobile from PC and it keeped connecting/disconnecting to PC around. I cannot even see MultiROM boot menu and I was only able to boot to recovery and reflash LOS 15.0 to have my mobile working. Could it be caused by selecting OmniROM as secondary ROM? In past I tried Paranoid android and it worked without any problem. I thought my phone was bricked but fortunately I managed to fix that.
Has anybody experienced problem with Xposed framework on secondary ROM? (7.1.2). It flashed xposed in recovery successfully but after opening Xposed installer, it crashed and display started to blick. Only hard restart helped.
Thomas_xxxxx said:
Has anybody experienced problem with Xposed framework on secondary ROM? (7.1.2). It flashed xposed in recovery successfully but after opening Xposed installer, it crashed and display started to blick. Only hard restart helped.
Click to expand...
Click to collapse
Even the magisk wont work on secondary. So please use only SU.
firemax13 said:
Even the magisk wont work on secondary. So please use only SU.
Click to expand...
Click to collapse
Why magisk and xposed dont work on secondary?
MultiROM does not work with LineageOS 15.1. Is it going to be updated?
How to uninstall multirom? @karthick mostwanted bro please also provide the uninstaller zip.
nitesh9 said:
How to uninstall multirom? @karthick mostwanted bro please also provide the uninstaller zip.
Click to expand...
Click to collapse
Then search it on google how to. Bro you can search but please search on google please.
firemax13 said:
Then search it on google how to. Bro you can search but please search on google please.
Click to expand...
Click to collapse
I am not a total noob (I know how to google). I searched on google and didn't found any relevant result.
Then I studied the the multirom uninstaller provided by devs of other devices and figured it out myself how to remove and restore the modified files manually.
However, it would have been easier if karthick had provided the uninstaller zip like other devs. (Would have been much helpful for newbies/noobs).
Hi Folks,
I am not sure if you are aware, but there is a large list of GSI ROMs that will work on the One Max, including LineageOS 16 (Android 9)! Everything appears to work (not 100% about NFC) including the camera. Here is the complete list:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
For some of these ROMs, you will need to install Gapps:
I recommend "pico"
https://opengapps.org/
Before you begin. DO A BACKUP FIRST!
The best method, after installing TWRP, and removing encryption is this:
1. Download/extract this LineageOS version:
https://sourceforge.net/projects/an...0-20190609-UNOFFICIAL-treble_arm64_avN.img.xz
2. Download ARM64/9.0 Gapps / https://opengapps.org/
3. Do a full Wipe.
4. Install the LineageOS image first. Pick Install Image > Pick LOS image > Select system partition
5. After image is done, go back to main menu in TWRP. Pick Install > Zip > Install Gapps.
6. Reboot, Setup Google Account, and restore your cloud backup.
7. Download latest Magisk app & Zip and install.
8. Refer to _cab13_ post. Towards the bottom on getting Magisk working with GSI Roms:
https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521
In TWRP, mount the /vendor and /system partitions to be able to copy files from one directory to another.
9. At this point, d'load a root checker app to verify prompts are working. You should now have rooted LOS16!
Encryption
After starting LOS and initial boot screen pops up w encryption, and says system UI keeps stopping.
Tries to encrypt the phone.
I formatted data and installed disable encryption zip after LOS image install
Any help appreciated
I am have twrp installed but twrp does not see xxxand...m64_avN.img.xz-file.
twrp accepts only zipfiles
So what can i am do, please?
Madricks18 said:
I am have twrp installed but twrp does not see xxxand...m64_avN.img.xz-file.
twrp accepts only zipfiles
So what can i am do, please?
Click to expand...
Click to collapse
You need the `unxz` tool, and all you have to do is `unxz <file.xz>` and it will unpack it.