Database Info

[DEV][2012/08/29] Multiboot v0.8

So I created a new thread for this so I can edit the first post for release-info.
This is the old thread:
http://forum.xda-developers.com/showthread.php?t=1133866
Please note that the multiboot-feature will be removed if you update your real system.
The virtual systems will stay on the sdcard so just reinstall the mod and you can boot your virtual systems again
Changelog:
Code:
[B]v0.8:[/B]
- addon.d (Multiboot will be kept on ROM-Update)
- working reboot recovery inside multiboot-rom(will boot directly into the recovery for that rom)
- working reboot into bootmenu inside multiboot-rom
- security-fixes
- TLS-support
- fixed sdcard-problems for NAND-system
[B]v0.7:[/B]
- added integration in touchbootmenu. This is no compatibility-patch - since now multiboot can only be used in combination with touchbootmenu
[B]v0.6.1:[/B]
- fixed some memory-leaks in kernel-module
- fixed stupid bug which prevented creating backups on first start
[B]v0.6:[/B]
- new hook-method with kernel-side code which should be the solution to most rom-problems
- fixed a bug which prevented mounting cache-partition inside recovery
- fixed installer-bug when TouchBootmenu is used on NAND
- reboot to recovery/bootmenu does not work for now. will be fixed in future
[B]v0.5.5:[/B]
- support for Stock-roms with Greenbreadmod
- added version-file(for updater which comes soon)
[B]v0.5.4:[/B]
- fixed problem with install-script
[B]v0.5.3:[/B]
- support for TWRP recovery
- fixed problem with virtual systems with names longer than 9 chars
- don't change 2ndBoot-script for bootmenus with 2ndSystem-support
- show graphical error-message when error was detected and copy log to "/cache/multiboot/error.log"
- experimental support for booting stock-roms
[B]v0.5.2:[/B]
- more configurable(via config-file)
- fixed error-detection. On early errors you will get back to bootmenu
- fix boot-problems for some roms
[B]v0.5.1:[/B]
- fixed crash of GUI when choosing recovery
- fixed bug which prevented creating important images on first boot
- virtual systems now are using nand-backups with real data so you could install backups of virtual systems on NAND
- installer sets default bootmode to 2nd-boot
- added recovery-option for NAND
- patch background-image of virtual recovery so you see if you are flashing real or virtual system
- reboot system if you click "Go Back" in virtual recovery(until I found a solution for going back to multiboot-GUI)
[B]v0.5:[/B]
- better protection against unwanted changes on real partitions(thanks wizwin)
- fix Phone for for GB-kernel(thanks quarx)
- set props so apps can detect if phone started with multiboot or not(for future versions of multiboot-manager)
- reboot into bootmenu/recovery now works
ATTENTION: reboot into recovery will open recovery for REAL system!!!
- added GUI for choosing which (virtual) system you want to boot
[B]v0.4:[/B]
- replacing all references to real system with stub-image(will be automatically created at /sdcard/fsimage/stub.img).
Now the recovery for the virtual system should be completely abstracted and it shouldn't make any changes to the real system
- a PDS-backup will be created and injected because it's needed by android-system and above change removes the reference
[B]v0.3/v0.3.1:[/B]
- moving original system-partition to another location instead of lazy unmount so she will be accessible in 2ndBoot-system and will not be busy
- fixed recovery to improve installer-zip compatibility. MIUI works now
- internal script-changes
[B]v0.2:[/B]
- "Install zip from SDcard" works now
- changed hook-method so it works with more ROM's(including ICS)
[B]v0.1:[/B]
First release
Source:
https://github.com/M1cha/DefyMultiboot
Download:
http://forum.xda-developers.com/attachment.php?attachmentid=1289953&d=1346244428
Installation:
1. Download zip-file and copy to sdcard
2. create 3 filesystem-images in ext3-format and copy them to /sdcard/multiboot/NAME with the names system.img, data.img and cache.img.
Please replace NAME with the folder-name of your virtual system(you have to create this)
You can download ready-to-use images from here:
http://www.multiupload.com/VY3U4IXRO1
2. install zip-file in CWM
Some info:
- The menu-entry "Lastest Recovery" is no longer supported and will affect your real system!
- boot the System-Chooser with the 2ndBoot-option in bootmenu
Bugs:
- Data-Wipe deletes android_secure
Donate:
Developing Multiboot makes much fun and I really like the results but takes much time, so feel free to donate a beer.

Hey,
i have no "Lastest Recovery" but a "Custom Recovery"
Can i install your script or does it not work with this version of the Bootmenu?

Which rom do you have installed?
I will check if it's compatible.

Thanks for the fast answer
i installed the CM7.2 Nightly "cm72-111125.0850-NIGHTLY-Defy"

The nightlys should always have the newest version of bootmenu.
Where you downloaded the nightly? I only could find "cm72-111123.1710-NIGHTLY-Defy.zip".
But generally it would work if you install but the problem is that you will never be able to change your real system because recovery will only make changes to the virtual one.
That bootmenu has 2 recovery-entrys is a lucky thing which I use as trick so I don't need to modify bootmenu
But when bootmenu-integration is done and you have an old version you will have to update bootmenu.

updated to v0.4
See first post for more info

Gonna try this now. I downloaded your empty .img files but how do I create my own img's on Win7? And what do you think is the smallest size I can make them safely to use with MIUI or ICS?

I don't know how you can create the images on windows, sry.
Maybe I can write a little App which does this directly on Android.
I have to admit that the images I uploaded are a little bit oversized.
system needs max 200MB
cache and data depends on your usage.
I would choose a minimum of 100MB for data and cache. If you plan to install many Apps you should make the data-partition over 300-500MB

Doesn't matter, instructions for Linux would do too
Hmm..oversized but no prob downloading because they were empty, only transferring via USB takes time. 200 MB for system and data and 100 for cache sounds good I'll make them myself if you can give me the instructions, I have Ubuntu.
App to do this on the phone itself sounds good, makes it even faster, no transferring from PC Thanks for your work

The Problem is that I can't find a mkfs.ext3-binary for Android
Maybe I'll extract it from another phone which contains this.
But as of now, here are the instructions:
Code:
dd if=/dev/zero of=./system.img bs=1000000 count=200
mkfs.ext3 ./system.img
The number 200 specifies the size in MegaBytes. I hope this will help you so far

Sure does
But like the poster above said, CM7 latest nightiles contain Custom Recovery, Stable Recovery, and Stock Recovery in the Bootmenu option for recovery. So Custom Recovery = Latest Recovery for your tool? I remember it used to say Latest recovery a few months back, dunno when that changed.

Oh, now I unsterstand what he wants to say.
I thought there is ONLY "custom recovery".
But if there are two recovery's it's ok to install. So you can use "Custom Recovery" for your virtual filesystem.
I'm downloading the CM7-source so I can extend and compile bootmenu and everything will be easier.
But with a download-speed of 170KiB/s this will take a long time

How fast is the virtual system? Could it be laggy because it is loaded from the sd-card?

the time from bootmenu to the boot-process itself takes a little bit time sometimes if I'm debugging.
But normally the booted system is in normal speed for me.
I think this depends on the speed of your sd-card and the usage of your apps.

m11kkaa said:
But normally the booted system is in normal speed for me.
I think this depends on the speed of your sd-card and the usage of your apps.
Click to expand...
Click to collapse
What class brand capacity card do you use?
I'll be trying with miui and ics tonight
Sent from my MB525 using XDA App

I don't know which class my card is because there is no label. It's completely black
But I don't think I have the best one(maybe class 2 or something else?)

An APP for windows to create ext-3 partitions http://forum.xda-developers.com/showthread.php?t=824154
download link: http://www.multiupload.com/SV7SOY33MQ

I have a 8GB class 4 card. Will test it in a few minutes with CM7 as real system and ICS as virtual system. Do you know what happen if I restore a backup in the real system? As far as I know a backup will override the bootmenu, too. Or am I wrong?

Yes, that will override the bootmenu.
But your virtual system stays on the sdcard.
You just need to patch again bootmenu with the downloaded "defy_multiboot_vX".

I'm on CM7 latest nightly and got boot loop when i tried to install Galnet MIUI ICS on virtual system. Could you fix it?

[ROM2]R11Max_MT6572_S00_nand_4.4.2

------------------------DISCLAIMER------------------------
Flash this Firmware with SP flash tool at your own risk i am in no way responsible for any damage that can occurr flashing your MTK device with flash tools, such as
•Hardbricked devices
•Soft Bricked devices
•Lost imei or baseband issues
or anything else for that matter, you are solely responsible for the actions you make when flashing this firmware, however following instructions below you shouldnt have a problem with the device and you can enjoy your new updated R11 max Firmware.
______________________________________
This Rom has been built by myslef with the base system of an R11 max chinaphone ive replaced almost everything.
DEVICE INFO
Android OS : 4.4.2 Kit Kat SDK:19
Kernel Version: 3.4.67
File System: UBIFS
BaseBand CPU: MT6572_S00
BaseBand CPU Secure Version: FF
BaseBand CPU Bootloader Version: 01
_____________________________________
REMOVED
_____________________________________
• Cooee launcher ( spyware )
• Marshmallow game ( adware )
• Browser
• calander
• gallery
• camera
• music fx
• exchange2
• email
• Volume control
• framework.jar
• calculator
• music player
• File manager
• system/vendor apps/FBlite/Whatsapp
• Stock boot animation
• Stock shutdown animation
• Stock start tone
• Stock Shutdown tone
• Stock UI sounds
• Stock Notifications sounds
• Stock Ringtone Sounds
• Stock Boot Logo
• Libs from removed apps
• framework from removed apps
• -res from removed apps
• Build.prop (Edited)
• Test Keys (they should be release)
• Wallpapers
• Live wallpapers
• Network Restriction lock (network Lock )
• Modem (connectivity & imei issues )
Plus alot more crap removed that i cant remember right now....
___________________________________________
ADDED OR REPLACED
___________________________________________
• updated Launcher with inbuilt,
Gestures
Wallpaper changer
Power managent
Ram management
Charging lockscreen with charge managent for healthy battery life.
T9 app quick search
App draw mode or home screen mode option for apps
Plus more
• Lightning Browser (looks like chrome)
• Google Calander
• FOTO gallery
• Kernel Auditor
• Open Camera
• MTK Video Wallpapers
• Bubbles Live Wallpaper
• AIMP music player
• JRD File Manager
• JRD Calculator
• updated exchange2
• JRD Secure container
• JRD plugger
• Updated music FX
• AVG mobile antivirus PRO with 365 day sub
• No root data firewall
• JRD video player
• JRD media container
• Mobile Log
• Modem log
• Alcatel one touch manager agaent (wifi data sync)
• Lollipop 5.1 boot animation
• Lollipop 5.1 Shutdown Animation
• Huawei Boot Tone
• Huawei Shutdown Tone
• LollipopOS boot logo (created by me)
• Samsung G930F oreo Ringtone Sounds
• Samsung G930F oreo Notification Sounds
• Samsung G930F oreo UI sounds (where available)
• Build edited to display device as Lollipop 5.1
• Fingerprint updated to Lollipop 5.1
• Updated to Release Keys (was test keys)
• updated libs for Jrd app support
• updates -res
• root set to function without the need for Su manager app binaries can run themselves.
• UPDATED 3G modem to fix connectivity issues (pulled from HTC desire 310)
•Replaced some system apps and some other apps from and alcatel OT 5050 MT6575 for faster UI and system stability.
• SU Binary pre installed to system, will remain even after factory reset.
• BUSY BOX 1.28 binary pre installed to system, will remain even after factory reset.
________________________________________
STORAGE CAPACITY
________________________________________
Flashing this firmware on a 500mb nand chip
Has the following storage results upon first boot
Data/ 62.9mb (was originally 20MB)
System/ 42.3mb (was originally 9KB)
If you wish to flash this to a bigger nand chip simply change the start address and length addresses in the scatter to match your devices partition info
---------☆☆☆MODIFIED BOOT IMG☆☆☆---------
as these R11 max only come with a 512mb NAND chip with OS installed there is only 42.3mb Data storage after flash of my firmware,using the modified boot.img allows you to use the devices SD card as the devices ROM & internal storage,
This has not been implemented into the build due to firmware size when pulling,
If you wish to use the modifed Boot.img and SD card you MUST partition the SD card BEFORE flashing the firmware if you wish to use the boot.img which is OPTIONAL rom will work fine without it,
Partition your SD card as follows with 2 partitions in this exact order EXT 4 Cannot be first or you will face data decryption error until rectified.
•PRIMARY partition - FAT32
•PRIMARY partition - EXT4 (label it mmcblk0p2)
To flash with modified boot.img follow steps above for SD card, and steps below for flashing.
__________________________________________
FLASHING THE FIRMWARE
__________________________________________
********This is a "UBIFS" filesystem*********
EMMC storage devices are NOT compatible
Unless you change the scatter to support your file system and even then it may require porting still.
Open SP flash tool, and open the scatter.file and change flash method to download only and click download, plug the device in while switched off and the device will flash,
DO NOT USE "format all + download" unless you have a backup of your firmware and security partition or you WILL lose your imei.
_________________________________________
LINKS
SP FLASH TOOL : https://spflashtool.com/download/SP_Flash_Tool_v5.1824_Win.zip
FIRMWARE : https://drive.google.com/file/d/1UU26fAdcCdU-tdV2enu7Ed4qGM2ceGbX/view?usp=drivesdk
MODIFIED BOOT IMG : https://drive.google.com/file/d/1IRwW4SY-mcRfRrFLYw45CpKacmoRRRW3/view?usp=drivesdk
All credit to Luca Roggero for making the extended storage space possible with his modified boot.img

Firmwares up dont forget to read the README.txt inside of firmware also.

Attention all users of R11 max,
A New build will be up in a week maximum, Google play is functional, i have also built a custom recovery for this model R11_Max however wont be released until the new rom is released.
Thread will be updated here with new links when its ready.

New rom is not far away now for the R11 MAX im just finishing up some minor touchups in the meantime i have built a number of custom recoveries for the phones due to 1 there not being any available at all for it & 2 all recovery porting tools do not work with this phone so manually built a number of different styles,versions etc theres TWRP, CTR, CWM, etc even an OPPO touch recovery even that i also managed to build enjoy,
https://forum.xda-developers.com/android/development/recovery-t3892041

Note all R11 max users,
A new rom will be released for this device by me in the near future when released it is advised to update to the latest build, modded with CM but stock 4.4.4 unfortunately that is all i am able to upgrade it to, 6.0 build i am scrapping for now i can get 6.0 apps to install but they just will not run most not at all,
Another note though ive managed to modify the boot.img some more to swap not only the data from
"ubifs" "UBI" "userdata" "/data" to
"Ext4 "EMMC" "/dev/block/platform/mtk-msdc.1/by-num/p2 (EXTERNAL SD)
but also system from
"ubifs" "UBI" "system" "/system" to
"ext4" EMMC" "/dev/block/mmcblk0p3" "/system" (SDCARD)
Not sure if i can get a rom functional to boot from it but TWRP recognises it aswell as mounts & formats it correctly, some useful info incase anyone else wants to give it a go also

All R11 users please be aware that a new build will be uploaded today or tomorrow latest which is a full AOSP CyanogenMod 11 flashable zip,
I will link the thread here was built for hs_q6_mb
But should work on all other variants as long as you use your stock boot.img
New thread will be linked here when completed and rom is uploaded

New roms up link is here
https://forum.xda-developers.com/android/development/rom-cyanogenmod11r11maxmt6572ubifs-t3920315

Matty1993 said:
New roms up link is here
https://forum.xda-developers.com/android/development/rom-cyanogenmod11r11maxmt6572ubifs-t3920315
Click to expand...
Click to collapse
Dear Matty1993! Can you give me the stock firmware and modem files to restore the imei device R11 max motherboard HS_Q6_MB_V1.0 Thank you.

Pavel70 said:
Dear Matty1993! Can you give me the stock firmware and modem files to restore the imei device R11 max motherboard HS_Q6_MB_V1.0 Thank you.
Click to expand...
Click to collapse
In hospital atm, once im out i may be able to help you out but your R11 max MUST have the exact same imei number or unfortunately i cannot provide it due to it being a federal crime in most states and countries to change it to something other than what it should be, however if your imei matches as i beleive it will due to having the same board model than my test device then i will happily provide you every needed file to restore your imei
To confirm our imeis match can you provide me only the first 4 numbers and the last 4 numbers so i can cross reference when i have access to my pc and if match ill upload to google drive and pm you the link to files please DO NOT write your entire imei out here just the first and last 4 digits will suffice.
On another note please do not use the stock firmware these came with they are riddled with adware and spyware, aswell as patched apps to steal your info even the launcher downloads spyware if you would like to use a custom rom i suggest checking out my CyanogenmodOS 11.0 i created for R11 max id suggest to use build #002 as build #003 has a google play issue you could try to flash that to restore your imei in the meantime see the OP for download links

[ROM3]_4.4.2_R11max_MT6572_S00_nand

------------------------DISCLAIMER------------------------
Flash this Firmware with SP flash tool at your own risk i am in no way responsible for any damage that can occurr flashing your MTK device with flash tools, such as
•Hardbricked devices
•Soft Bricked devices
•Lost imei or baseband issues
or anything else for that matter, you are solely responsible for the actions you make when flashing this firmware, however following instructions below you shouldnt have a problem with the device and you can enjoy your new updated R11 max Firmware.
______________________________________
This Rom has been built by myslef with the base system of an R11 max chinaphone ive replaced almost everything.
DEVICE INFO
Android OS : 4.4.2 Kit Kat SDK:19
Kernel Version: 3.4.67
File System: UBIFS
BaseBand CPU: MT6572_S00
BaseBand CPU Secure Version: FF
BaseBand CPU Bootloader Version: 01
_____________________________________
REMOVED
_____________________________________
• Cooee launcher ( spyware )
• Marshmallow game ( adware )
• Browser
• calander
• gallery
• camera
• music fx
• exchange2
• email
• Volume control
• framework.jar
• calculator
• music player
• File manager
• system/vendor apps/FBlite/Whatsapp
• Stock boot animation
• Stock shutdown animation
• Stock start tone
• Stock Shutdown tone
• Stock UI sounds
• Stock Notifications sounds
• Stock Ringtone Sounds
• Stock Boot Logo
• Libs from removed apps
• framework from removed apps
• -res from removed apps
• Build.prop (Edited)
• Test Keys (they should be release)
• Wallpapers
• Live wallpapers
• Network Restriction lock (network Lock )
• Modem (connectivity & imei issues )
Plus alot more crap removed that i cant remember right now....
___________________________________________
ADDED OR REPLACED
___________________________________________
• updated Launcher with inbuilt,
• Lightning Browser (looks like chrome)
• gallery V1.1 with photolocker
• Camera FV-5
• JRD File Manager
• JRD Secure container
• JRD plugger
• Updated music FX
• JRD media container
• Lollipop Boot animation created by me
• Lollipop Shut Animation created by my
• LollipopOS boot logo created by me
• Samsung G930F oreo Ringtone Sounds
• Samsung G930F oreo Notification Sounds
• Samsung G930F oreo UI sounds (where available)
• Build edited to display device as Lollipop 5.1
• Fingerprint updated to Lollipop 5.1
• Updated to Release Keys (was test keys)
• updated libs for Jrd app support
• updates -res
• root set to function without the need for Su manager app binaries can run themselves.
• UPDATED 3G modem to fix connectivity issues (pulled from HTC desire 310)
•Replaced some system apps and some other apps from and alcatel OT 5050 MT6575 for faster UI and system stability.
• SU Binary pre installed to system, will remain even after factory reset.
• BUSY BOX 1.28 binary pre installed to system, will remain even after factory reset.
________________________________________
STORAGE CAPACITY
________________________________________
Flashing this firmware on a 500mb nand chip
Has the following storage results upon first boot
Data/ 80.9mb (was originally 20MB)
System/ 100.5mb (was originally 9KB)
If you wish to flash this to a bigger nand chip simply change the start address and length addresses in the scatter to match your devices partition info
---------☆☆☆MODIFIED BOOT IMG☆☆☆---------
as these R11 max only come with a 512mb NAND chip with OS installed there is only 80.9mb Data and update storage after flash of my firmware,using the modified boot.img allows you to use the devices SD card as the devices ROM & internal storage,
This has not been implemented into the build due to firmware size when pulling,
If you wish to use the modifed Boot.img and SD card you MUST partition the SD card BEFORE flashing the firmware if you wish to use the boot.img which is OPTIONAL rom will work fine without it,
Partition your SD card as follows with 2 partitions in this exact order EXT 4 Cannot be first or you will face data decryption error until rectified.
•PRIMARY partition - FAT32
•PRIMARY partition - EXT4 (label it mmcblk0p2)
To flash with modified boot.img follow steps above for SD card, and steps below for flashing.
__________________________________________
FLASHING THE FIRMWARE
__________________________________________
********This is a "UBIFS" filesystem*********
EMMC storage devices are NOT compatible
Unless you change the scatter to support your file system and even then it may require porting still.
Open SP flash tool, and open the scatter.file and change flash method to download only and click download, plug the device in while switched off and the device will flash,
DO NOT USE "format all + download" unless you have a backup of your firmware and security partition or you WILL lose your imei.
_________________________________________
LINKS
SP FLASH TOOL : https://spflashtool.com/download/SP_Flash_Tool_v5.1824_Win.zip
FIRMWARE : https://drive.google.com/file/d/1yIVCL49KQ77BOkoFbW-Dt_n7IkzqQkwV/view?usp=drivesdk
All credit to Luca Roggero for making the extended storage space possible with his modified boot.img within the firmware file

Thanks for taking the time to give this phone proper treatment.
My aunt fell victim to the R11Max scam a few months ago. She gave it to me today so naturally, I came here for a solution.
It only took a few mins of playing with it and my red flag alarm was full tilt. Suspicious apps and running processes were my first clue.
Looks like this phone is getting an upgrade this weekend. Thanks again!!

All good mate,
Ill have another one out in a few days ill post the link to it on this thread for you it will be Samsung S7 themed almost done just a few more minor things,
Juat glad im able to help as the stock OS It comes with is horrible, at least with these build there is space to install apps & if you use the modifed boot.img with SD card you can make it a 4gb or 6GB or whatever size SD card you have just use a decent quality one or your phone will be slow with it.

Matty1993 said:
All good mate,
Ill have another one out in a few days ill post the link to it on this thread for you it will be Samsung S7 themed almost done just a few more minor things,
Juat glad im able to help as the stock OS It comes with is horrible, at least with these build there is space to install apps & if you use the modifed boot.img with SD card you can make it a 4gb or 6GB or whatever size SD card you have just use a decent quality one or your phone will be slow with it.
Click to expand...
Click to collapse
Awesome! I've got an old 2GB card I'm about to partition for her. It's just going to be used for games she likes to play.
Sent from my Galaxy S5 using XDA Labs

Id probably get something a bit better than a 2GB will be low quality made and will make the system go very slow,
I tried this myself with a low end 2GB was very laggy with the modified boot.img
I then tried with a sandisk 16GB SD HC 1 sd card i paid $12 for it and its like an emmc chip built in to the phone only in an SD card form theres no lag what so ever
New build is close to being done ive fixed a few more things today and have a few more to do and will be out there will be one with google play store installed & another build with only Aptiode store inatalled instead of google play so everyone will be able to choose what they would rather have as an app store

KernelCorn said:
Awesome! I've got an old 2GB card I'm about to partition for her. It's just going to be used for games she likes to play.
Click to expand...
Click to collapse
Hey mate,
New firmware is up,
Small bug with storage mounting for app stores without the modified boot.img so modded boot.img is a must until fixed or you wont be able to install apps from the app store,
Everything else is working as far as ive tested link is below, screenshots are also on the post,
https://forum.xda-developers.com/android/development/rom4-r11maxmt6572s00nand-t3878300

Attention all users of R11 max,
A New build will be up in a week maximum, Google play is functional, i have also built a custom recovery for this model R11_Max however wont be released until the new rom is released.
Thread will be updated here with new links when its ready.

New rom is not far away now for the R11 MAX im just finishing up some minor touchups in the meantime i have built a number of custom recoveries for the phones due to 1 there not being any available at all for it & 2 all recovery porting tools do not work with this phone so manually built a number of different styles,versions etc theres TWRP, CTR, CWM, etc even an OPPO touch recovery even that i also managed to build enjoy,
https://forum.xda-developers.com/android/development/recovery-t3892041

Note all R11 max users,
A new rom will be released for this device by me in the near future when released it is advised to update to the latest build, modded with CM but stock 4.4.4 unfortunately that is all i am able to upgrade it to, 6.0 build i am scrapping for now i can get 6.0 apps to install but they just will not run most not at all,
Another note though ive managed to modify the boot.img some more to swap not only the data from
"ubifs" "UBI" "userdata" "/data" to
"Ext4 "EMMC" "/dev/block/platform/mtk-msdc.1/by-num/p2 (EXTERNAL SD)
but also system from
"ubifs" "UBI" "system" "/system" to
"ext4" EMMC" "/dev/block/mmcblk0p3" "/system" (SDCARD)
Not sure if i can get a rom functional to boot from it but TWRP recognises it aswell as mounts & formats it correctly, some useful info incase anyone else wants to give it a go also

All R11 users please be aware that a new build will be uploaded today or tomorrow latest which is a full AOSP CyanogenMod 11 flashable zip,
I will link the thread here was built for hs_q6_mb
But should work on all other variants as long as you use your stock boot.img
New thread will be linked here one completed and rom is uploaded

New rom is up link is here
https://forum.xda-developers.com/android/development/rom-cyanogenmod11r11maxmt6572ubifs-t3920315

[ROM][UBIFS]CyanogenMod11_R11_Max_MT6572

#-------------------------Disclaimer----------------------------#
I am in no way responsible for dead NAND/EMMC chips, SD cards Lost basebands, nuclear war or anything else for that matter YOU the users are soley responsible for any and all actions you make the build is 100% tested & confirmed working on UBIFS R11 max chinaphone with board variant Q6_M144_GT-018_MB_1.0
#-----------------------Device info----------------------------#
Android OS : 4.4.2 Kit Kat SDK:19
Kernel Version: 3.4.67
File System: UBIFS
BaseBand CPU: MT6572_S00
BaseBand CPU Secure Version: FF
BaseBand CPU Bootloader Version: 01
Board Variant: HS_Q6_MB_V1.0
Storage Capacity=512Mb (4Gb ext through recovery)
Ram Capacity= 497Mb
Resolution= 480×854
#-----------------CyanogenmodOS--------------------------#
Version = 11
SDK-ver = 4.4.4
SDK-API = 20
B-TYPE = userdebug
Build id = XNG3C
Linux Kernel = 3.4.67
LCD- density = 240
LCD-Dpi = 320
• Deodexed
• IO_scheduler set to CFQ
• Performance adjustments
• Preloaded with Gapps
• Cyanogen account support
• CyanogenMod Logo
• Ram flag optimisations
• Default runtime set to art
• Voice unlock support
• Pre rooted with Cyanogenmod SU 1.34
• addon.d support
• init.d support
• BT NFC support
• addon.d & init.d slinked in cpio in bootimg
• Custom CM bootimg with storage fix.
• Ad and popup blockers
• CM ambient updater
• CM InCallUi
• google voice search
• CM Device management
• CM SetupWiz
• factory test mode [ *#*#0#*#* ]
• CM Live lockscreen
• CM MusicFX
• CM Trebuchet Launcher
• Chrome based browser
• CM Voice +
• Voice command support
• Camera interpolated and tweaked
• camera path changed to added cameraserver in vendor/bin/cameraserver instead of system/bin/mediaserver
• Added Clearmotion props to default & build.prop
• Added Clearmotion config to /etc
• Added Clearmotion support libs
• Added Clearmotion FW to /lib
#---------------------------NOTICE------------------------------#
I do this in my free time DO NOT ask for Eta's,
Includes storage modified CM boot.img which will be flashed with the rom please use the partiton sd card option in advanced options in recovery to make up to a 4096mb /data partition before transferring zip to sd and flashing.
#----------------------------BUGS------------------------------#
• update #003 is having a whinge with storage for downloaded apps from store so they wont install after download will be fixed in build #004,
• NFC is working properly but you must purchase NFC bluetooth module tags to support nfc transfer, i have compiled & added an nfc.ko module to use bluetooth instead of newer modules which use the wifi reciever as the antenna and due to there being no NFC compatibile HW on these extremely poor low end devices i do not wish to see comments about this as a bug.
#-------------------------LINKS------------------------------#
CM CTR recovery.
https://drive.google.com/file/d/1UErBsSe2DLFEtcgwXz-hZR_fQINxpn9H/view?usp=drivesdk
Stock touch recovery to replace original
https://drive.google.com/file/d/14Y-WQHDLfqlEdjmu-PTujNqGkkUpcpLn/view?usp=drivesdk
CyanogenmodOS #001-BETA 20190412
https://drive.google.com/file/d/1Xuf-gSHPHr5CGsZjFu3pgT44FdR5GFx5/view?usp=drivesdk
CyanogenmodOS update #002 20190414
https://drive.google.com/file/d/19Nt1pVo8ruvTCugsgejtMQvJDe2xZIb7/view?usp=drivesdk
CyanogenmodOS update #003 20190504
[ Has play store issue ]
https://drive.google.com/file/d/1D4sCf1oflvSTFJxFzH1WwMJL_1j8H5-G/view?usp=drivesdk

Welcome to CyanogenMod 11

BUILD #002 is up get it from the OP
CHANGELOG
Camera works now with slow motion & fast motion video recording, picture quality is still **** but is tons better than it was on stock rom.
Rebuilt the system layout and merged most /vendor files and folders to /system
Fixed gallery keeps stopping error even though it wasnt
Cleaned up the GUI scaling to produce cleaner icons etc etc changelog is in /etc for anyone that wants to look
Changed the Live lockscreen wallpaper to something much simpler & better looking.
Converted entire system to single sim & removed Gemini where i could & set props to disable what i couldnt find of it, repathed ril to run through mtk-ril.so also added init.volte.rc, volte_imsm.so/volte_stack.files to help ril call clarity as certain parts of the stack are interacting with ril even though its a GSM Radio
Added getenforce & setenforce to /bin and file_contexts to try and get my init.rc props for setenforce to run the kernel permissively for some extra init processes, BUT setenforce for some reason is receiving permission denied cannot symlink so i hope to have this completed & working in build #003
Added /product/build.prop dir to deal with zram for swap & ext4 /data partitiion under logical boot partitions.
Added new android apple crime screen power off logo
Added some misc ringtones, notification tones and ringtones other than the cyanogen tones.

Nice Work Matty1993!!
You have been a busy bee :highfive:

Hello,
I am new to ROMs, Could you give me detailed instructions on how I would install this?
Thanks,
Robby

bigrammy said:
You have been a busy bee :highfive:
Click to expand...
Click to collapse
Haha yeah one of my old projects ive been meaning to get finished for ages, finding out how to attach android to UBIFS on top of UBI was a pain in the ass lol got to experiment with ril on this one as it was dual sim and tried running gemini through it but as it was a source build dual sim compatibility dosent work so had to depract gemini and set single sim still been working on the tuba build tho taking my time with it as sony really like to mix things up, also finishing a lineage OS 14.1 build for Alcatel Pixi 3.5 that was from source also but dualsim works on this one even though this phones a single sim phone haha go figure lol

DJ Robby said:
Hello,
I am new to ROMs, Could you give me detailed instructions on how I would install this?
Thanks,
Robby
Click to expand...
Click to collapse
What model is your R11 max clone phone it must be HS_Q6_MB_V1.0 board revision or it wont boot on your device and i will need to build one for your revision if so as the kernel will be different,
You can find the board variant by taking the backing off the phone and looking at the sim slot see pic attached,
Check this out first or youll brick it 100% i gaurantee it, google how to take a firmware backup using SP flash tool before doing anything SP flash tool can be downloaded from here aswell as the MTK Vcom drivers for flash tool,
https://spflashtool.com
If your board is different i need the BOOTIMG.file from your SP Tool backup so please do this first before anything or i wont be able to build you anything as i need your stock kernel from boot.img to decompile and make changes for my rom aswell as the boot.img is highly modifed with CM source

Hello,
I can't find a number like that, I looked everywhere.
Here is a full backup of the phone: https://drive.google.com/file/d/15P9KutXb0FrxHRTj4qrQ-KW94XA6J2SI/view?usp=sharing
The kernel is the same though because if I go to settings it shows the same kernel number as the one in this post.
Thanks,
Robby

DJ Robby said:
Hello,
I can't find a number like that, I looked everywhere.
I have the boot.img, I will edit this message with the boot.img when I have a chance. The kernel is the same though because if I go to settings it shows the same kernel number as the one in this post.
Thanks,
Robby
Click to expand...
Click to collapse
Hey mate the kernel number may be the same but the config of the kernel will be diff, if it dosent have a number in the sim slot it will deffo not be a HS_Q6_MB you may have the ZMA_12_MB or ZMA_9_MB board
So deffo dont flash any of this stuff if you get me the stock boot.img & recovery img from your R11 max i can build the recoveries and rom for your board revison just upload them here in a .zip file when you get the chance
Thanks

Matty1993 said:
Hey mate the kernel number may be the same but the config of the kernel will be diff, if it dosent have a number in the sim slot it will deffo not be a HS_Q6_MB you may have the ZMA_12_MB or ZMA_9_MB board
So deffo dont flash any of this stuff if you get me the stock boot.img & recovery img from your R11 max i can build the recoveries and rom for your board revison just upload them here in a .zip file when you get the chance
Thanks
Click to expand...
Click to collapse
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!

DJ Robby said:
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
Click to expand...
Click to collapse
Hey mate,
Sweet ill get onto it and post link here to a new thread ill make for your variant r11 max.
Ive got a new build just about ready also which is build #003 so ill start your variant from #003 which has vast improvements from build #002
# edit
Glad you didnt flash your R10 is eMMC ext4 fs and not ubifs just finished the boot.img off anyhow

DJ Robby said:
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
Click to expand...
Click to collapse
Try these recoveries tell me if they boot uo and everything is ok with them
Oppo touch recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1ZUZ3jmNhVkWSTB-57ifPh9_Lmm_jjkCB/view?usp=drivesdk
CWM recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1WO44rtoWttfeeAvCdff_97JqbuXboeXB/view?usp=drivesdk
Open sp flash tool & load your scatter file,
Then click on the recovery path and load a recovery into the slot,
MAKE SURE that download only is selected and NOT format all + download this is very very important
Click download with phone switched off plug into pc & recovery will now flash,
Once flash is complete remove then re insert the cord wait for the charging screen to appear,
You can now boot to either recovery by holding the volume up button and power button until the first boot logo appears then release only the power button and keep holding power up to see if they will boot or not,
If they boot all sweet ill upload the rom as its just about finished being built

Matty1993 said:
Try these recoveries tell me if they boot uo and everything is ok with them
Oppo touch recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1ZUZ3jmNhVkWSTB-57ifPh9_Lmm_jjkCB/view?usp=drivesdk
CWM recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1WO44rtoWttfeeAvCdff_97JqbuXboeXB/view?usp=drivesdk
Open sp flash tool & load your scatter file,
Then click on the recovery path and load a recovery into the slot,
MAKE SURE that download only is selected and NOT format all + download this is very very important
Click download with phone switched off plug into pc & recovery will now flash,
Once flash is complete remove then re insert the cord wait for the charging screen to appear,
You can now boot to either recovery by holding the volume up button and power button until the first boot logo appears then release only the power button and keep holding power up to see if they will boot or not,
If they boot all sweet ill upload the rom as its just about finished being built
Click to expand...
Click to collapse
I can try when I get home but I already got TWRP with the Easy Magic Installer except it is an older version: https://forum.xda-developers.com/showthread.php?t=2798257

DJ Robby said:
I can try when I get home but I already got TWRP with the Easy Magic Installer except it is an older version: https://forum.xda-developers.com/showthread.php?t=2798257
Click to expand...
Click to collapse
More or less just to test for device compat is all glad you told me youve got TWRP tho as my rom dosent have mount asserts in the script as they were causing error 7 so ill have to rebuild the meta-inf again as ive got set for perm aswell whereas TWRP uses meta-data to set file permissions

Matty1993 said:
More or less just to test for device compat is all glad you told me youve got TWRP tho as my rom dosent have mount asserts in the script as they were causing error 7 so ill have to rebuild the meta-inf again as ive got set for perm aswell whereas TWRP uses meta-data to set file permissions
Click to expand...
Click to collapse
So when do you think the ROM will be ready?
Edit: Oppo Touch Recovery works, I'd rather not bother with CWM if that's ok? And if you could port a TWRP instead of Oppo Touch Recovery I would appreciate that since it is more advanced.

DJ Robby said:
So when do you think the ROM will be ready?
Edit: Oppo Touch Recovery works, I'd rather not bother with CWM if that's ok? And if you could port a TWRP instead of Oppo Touch Recovery I would appreciate that since it is more advanced.
Click to expand...
Click to collapse
Rom will be ready soon it takes time to convert things to ext4 from ubifs patience is a must for these things unless you want a brick ? Lol plus ive got another 5 projects on the go so lots to do and not enough time to do it all, just finished lineage 14.1 android 7.1.2 for alactel pixi 4027A using a stock kernel on android 4.4.4
as for TWRP probably not due to the size of your recovery and the size of most twrp is about 3mb to short for your partition youll need to use cwm ive added mount points to the script for your data & system partitions so if it dont flash mount in CWM and then flash if it still dosent use the take a log option in my installer and forward it to me so i can see if it was the mounts or what,
Also i havent set meta-data for permissions ive set perm & perm_recursive which is specifically for CWM so please flash with that,
I make no gaurantee it will boot as i dont have one in front of me to work on & debug but everything should work ok though link will be up in roughly half hour max

Links up tell me if it installs and boots ok is based off my cyanogenmod 11 new unreleased build #003 for ubifs
CyanogenMod 11 R10
emmc + ext4
BETA TEST BUILD
https://drive.google.com/file/d/1CvP3TPjo5fxXi6tHKI388WFN5KnWTyZ4/view?usp=drivesdk
If it dosent flash remember to get the log from my modified installer
if it dosent boot past first logo tell me it will be fstab issue which ill need to adjust
If it gets stuck on infinite bootanimation tell me ill need to adjust the vold
If any errors just flash back your backup with SP flash tool using download only mode and youll be back up and running with it until i get it fixed if it does need fixing.

Matty1993 said:
Links up tell me if it installs and boots ok is based off my cyanogenmod 11 new unreleased build #003 for ubifs
CyanogenMod 11 R10
emmc + ext4
BETA TEST BUILD
https://drive.google.com/file/d/1CvP3TPjo5fxXi6tHKI388WFN5KnWTyZ4/view?usp=drivesdk
If it dosent flash remember to get the log from my modified installer
if it dosent boot past first logo tell me it will be fstab issue which ill need to adjust
If it gets stuck on infinite bootanimation tell me ill need to adjust the vold
If any errors just flash back your backup with SP flash tool using download only mode and youll be back up and running with it until i get it fixed if it does need fixing.
Click to expand...
Click to collapse
So does that mean Oppo Touch Recovery is useless? So I should just put CWM in the recovery and then flash the CyanogenMod11 with CWM If I could get more detailed instructions that would be helpful as you know I am a noob...
Edit: So I flashed it with CWM and it failed, Here is the log: https://pastebin.com/i2F55g08
What I think happens is the first image that says welcome comes up, Then the boot animation comes up but it doesn't finish before returning to the welcome image that was at the start and it stays on that forever.
Edit 2: I also don't know how to restore the backup with SP Flash Tool but that is ok since this isn't my everyday phone so i'll just wait until you fix the ROM.

DJ Robby said:
So does that mean Oppo Touch Recovery is useless? So I should just put CWM in the recovery and then flash the CyanogenMod11 with CWM If I could get more detailed instructions that would be helpful as you know I am a noob...
Edit: So I flashed it with CWM and it failed, Here is the log: https://pastebin.com/i2F55g08
What I think happens is the first image that says welcome comes up, Then the boot animation comes up but it doesn't finish before returning to the welcome image that was at the start and it stays on that forever.
Edit 2: I also don't know how to restore the backup with SP Flash Tool but that is ok since this isn't my everyday phone so i'll just wait until you fix the ROM.
Click to expand...
Click to collapse
Hey mate i took a look at the log,
For some reason it didnt symlink any of the system files or set the perms for them
Modified boot.img didnt flash either for some reason so surprised it started playing animation so all my adjustments from ubifs to ext4 must be correct
In the script
Format was ok
Mounting was ok
Extract system files was ok
I think it may have something to do with CWM possibly as thats the only reason its not booting none of the files have correct perms everything else went ok though, so ill see what i can do today about another recovery for you,
The oppo touch recovery is just a stock recovery i added to get rid of the 3e recoveries these phones originally come with, much nicer is all,
To restore your backup using SP flash tool open flash tool, select the scatter box,
Navigate to your backuo folder & double click on the scatter_file.txt,
All of your partitions and files will automatically load up for flash,
Change the download mode to download only
Power off phone click start download
Connect phone & wait for flash

I will just wait for the new Recovery and ROM to work because like I said before this is a device that I didn't use at all but I will probably use it once I get the ROM. Again I just want to thank you for all your help since because of you I don't need to throw out this horrible phone.

[ROM][UBIFS][6.0.1]LineageOS-13.0_R11_Max_MT6572

For device R11Max Q6_MB_V1.0 UBIFS chinaphone
DISCLAIMER
Freshly compiled today see the disclaimer on 2nd screen of rom installer before proceeding with the installation process
FEATURES
• Custom CTR 2.7 lineageos themed by me which is an update from the old 2.2 i was using before
• Boot.img rebuilt from ground up to support Android 6.0 on ubifs UBI system layouts.
• Includes storage fix to make 4GB /data partition
• Custom boot logo created by me
• Custom lineageos aroma installer by me also
• Patched with Magisk V14
• Patched with LOS Root (dev options)
• Patched with nano Gapps
• Camera interploated and tweaked
• System tweaked for ubifs perf
• Tweaked read ahead and writeout for mmcblk's
• Tweaked and rewrote dalvikvm for ubifs perf
• Added init.d tweaks for system, cache & data
• Tweaked R/W options for low end sdcards
Update 2019-10- = Still in debug progression
• Fixed earpeice sensor not working sometimes
• Tweaked out the advan bluetooth and wifi modules and setprop for R11max wifi HW
• Updated modem paths and sockets for new rild
• Added debug props to fix camera flashes back and front as werent working before and also tweaked front camera flash to be brighter, couldnt do much about back as its a low lumen led but have brightened it up as best i can.
• Added NFC services to initrd and some system so far for TCT NFC immersion this will require purchasing an nfc tag if you want nfc
Some other stuff to i will comment below with new link when build is finished being debugged and uploaded in the next few days
NOT WORKING
• Offline charging not currently working should be soon enough
• Charging light not working offline or online ill see what i can do nearly forgot to list this one
BUGS
• You may get a random reboot or two or device may freeze and reboot once or twice this is due to magisk and not lineageos, have rigorously tested and goes away after system settles in
NOTES
• Build compiled using AdvanS4 eMMC sources as a base some modules have been left such as wifi and bluetooth if you have problems with either please let me know
• Once you complete the setupwizard if using a lower read/write speed class 10 sdcard give the device at least 5 minutes to settle in before using it or it will go a little slow until my tweaks kick in, high speed cards disregard this comment
• Tested and perf tweaked using class 10 HC 8GB card thats 6 years old with ancient slow read write speeds compared to todays HC cards, so those using new high speed cards should experience 0 lag at all
• See last picture if you would like to see how i have set sdcard partitions out for this lineageos build.
• If you dont have a scatter file to flash the recoveries let me know and will provide it in a link from google deive via PM i do this to stop people flashing with incompatible partition layouts.
• You will see a corrupt sdcard in settings/storage.....LEAVE IT ALONE... this is your /data partition the system us stating it is corrupt as it is expecting it to be in vfat format whereas it is in ext4 format, if tou format it youll stuff it up.
• Dates are diff in pictures as to what build dates actually are, pictures are old build append date is 20190930 5:35PM as you will find in settings about.
• You will see ViLTE,VoLTE,LTE options in networking settings note that this has not been fully intergrated and will not work on this device i added to system source for LTE devices i will recompile for in future and will save me adding it later for other devices using UBIFS please do not get confused this is GSM-2G radio device only and is not UMTS-3G or LTE-4G.
PREREQUISITES
• A computer with windows.
• SP Flash tool installed.
• SP Flash tool VCOM drivers installed.
• Scatter file for your device.
• Class 10 sdcard with high Read/Write speeds.
• USB cord for flashing.
• Can of coke or bourbon preferably.
• A brain or well at least half of one should suffice.
FLASHING
• Make a factory reset before doing anything and be sure to back your firmware up before proceeding.
• Insert your sdcard & flash this recovery
https://drive.google.com/file/d/1vggA-qFjsej2BdacsHUqnFOBx-izrCzK/view?usp=drivesdk
• Remove and reinsert battery after flash
• Hold power + volume up until recovery boots.
• Select advanced, partition sdcard, create 4096MB with 128MB swap on page after.
• Power off and flash this recovery boot to it the same way as you did the first recovery.
https://drive.google.com/file/d/1Xv49Qr9cZtH18EtkYwLO5NNcFrTvUtLh/view?usp=drivesdk
• Select UMS transfer and copy lineageos https://drive.google.com/file/d/1-vGYM_bDQKlYNgT_tYasVHLM0x3mXE7E/view?usp=drivesdk to the sdcard partition with pc.
• Power off and flash back to the first recovery and again boot to it.
• Select wipe menu, wipe data factory reset wait for it to complete, then select wipe all data preflash & wait for it to complete.
• Back to main menu select mounts & mount the system after return to the main menu.
• Select install, then install from sdcard and select the rom.zip and flash.
• Follow the on screen prompts and be sure to read page 2 of the installer before proceeding with installation.
• Reboot and done.
Dont forget the thanks button. :good:

Hey Matty,
Thanks a lot, the only problem I ran into was that I extracted the rom.zip before transferring I wasn't supposed to do that DOH!!
Cheers for your time and effort in creating this much appreciated! :good:

Hey Matty,
I cant install any app's from the play store though, it just keep's saying "downloading....."
Shall I go ahead and install the latest GApp's?
Thanks
Edit: total guess.... but the phone goes to Australia time zone every time I reboot (I have not activated the sim card yet to set time/ time zone automatically), I set it to UK time/ time zone and it does not download anything from the play store, maybe this is the problem? if I activate the sim will it fix the problem?

CraiglI said:
Hey Matty,
I cant install any app's from the play store though, it just keep's saying "downloading....."
Shall I go ahead and install the latest GApp's?
Thanks
Edit: total guess.... but the phone goes to Australia time zone every time I reboot (I have not activated the sim card yet to set time/ time zone automatically), I set it to UK time/ time zone and it does not download anything from the play store, maybe this is the problem? if I activate the sim will it fix the problem?
Click to expand...
Click to collapse
Hey mate just seen ya replys,
Okie dokie ill see what i can do bout getting it fixed ill update Google apps on next release with the most updated from openGapps as ive set All google services to /system on the first build,
I beleive the problem with them not downloading also is due to a storage issue on my behalf which i apologise for however ive gotten that issue hopefully already fixed for next build,
Ill see what i can do tonight about it and see if i can push a quick update out as i have been meening to get the second update finished for a while now.
Oh also it being set on aus timezone or country by default shouldnt affect it as default google client database is set to only android-google and not android-google-au so selecting your country and timezone should set default to your needs as such
Cheers

Found the problem with apps not downloading from playstore for the first build permissions and frameworks were somehow left out, got that fixed anyway now just need to finish rebuilding ramdisk and next update will be up in a day or two max
Added tons of performance tweaks to it so runs pretty nicely and smoothly considering its a dual core mt6572 with only 497mb of RAM got swap working more aggressively aswell for users with lower end sdcards inserted,
Just need to fix the ril again as its broken somewhere and need to change the build fingerprint to something of a stock 6.0 rom as ive updated gapps its now stating device is not play certified because its a custom rom

UPDATE
sadly i wont be pushing any more updates for the R11Max China phone as ive dropped it the other day and lcd is completely stuffed,
i can get an emulated screen in gui within os via scr_cpy on pc from github but unless anyone can tell me how to emulate the recovery display for build flashing and testing then im out of ideas unfortunately,
If anyone would like to take my builds and port them or make edits please feel free to go ahead,
I will keep trying to get recovery emulated but its not looking good so at this point development is over for this model unfortunately unless anyone wants to donate there device for a short period of time to finish updates