Related
!!This is ONLY for Toshiba Folio 100!!!
This Mod is based on Toshiba Stock with additions from Nvidia SDK, to make a better functioning stock rom with google apps and better OpenGL ES support.
Currently giving you an amazing
- 3000+ in Quadrant score!! (screenshot here )
- 50.5 frames in neocore (not amazing compared to HTC desireHD, i think, but still good)
You can also follow updates on Twitter now: Dexter Picard (DexterPicard) on Twitter or
me a Red bull, and you're sure i stay up working on this mod or you can visit my new homepage at Dexter's mods
for new users with latest 2.2.5.0131 firmware, here is a howto on reverting tablet to be able to install custom roms.
Wiki pages available here and here Other non-FolioMod , but folio100 threads Kernel&Tweaks & General questions thread
Please use these for non-FolioMod questions, like screen,battery etc...
Video illustration of FolioMod (Thanks to kevin.hansen)
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE.
A FACTORY RESET IN RECOVERY MENU IS ALWAYS RECOMMENDED TOO.
You can also try these instructions for v1.1 and lower versions here or here if those help you in another way than the one provided below.
download latest FolioMod full zipfile- Extract contents to a folder and follow instructions below.
copy the update.zip from inside downloaded zipfile to the root of your sdcard, and insert sdcard into folio.
Enter "Recovery menu" when folio is just turned on and press (POWER) once and (VOL up) next.
press (VOL up) Factory reset or system update.
press(VOL down) to continue to system update.
press (VOL up) to confirm system update.
during installation progress bar will show har far it is.
folio will reboot after installation.
if you need to wipe, repeat the steps above without sdcard inserted, and you get into recovery menu. Press "HOME" button to see menu and choose "factory reset".
After reboot a BLACK screen appear for 1 or 2 minutes!! don't worry, its normal!
Rollback to original stock rom:Download Folio stock image for full restore to stock rom
extract zip to a folder, and from here follow steps 1 - 7 above, to install the update.zip .
This image is for rollback purpose, if you do not want the mod edition, here is the way back to stock rom.
Remember to run a factory reset before or after this stock rom install..
Latest Full update
Download Mirror 1 - FolioMod v1.4 or Mirror 2
Patches
FolioWidget fix here , solves the compressed issue on regular launcher or LauncherPRo. now shows all icons.
V1.4 - Rollback of graphics tweak driver - if you got problems with touch screen here
V1.3+ old wifi driver(1.0 release) works better for some ppl. (Requested by many) here
V0.0+ Generic format internal storage for all mods (so far) here, only needed if you got internal storage problems.
Rename downloaded patch to update.zip and install using recovery.
Old releases
Download Mirror 1 - FolioMod v1.3d
Download Mirror 1 - FolioMod v1.3b
Download Mirror 1 - FolioMod v1.3 - Mirror 2 - easyshare - Mirror 3 - (NOT THERE)
Known issues (also reported by users)
NONE
THANKS to
ownhere - coming up with the initial idea on how to implement the loopback solution for optimized database access.
Weeds2000 , for the great help and fixes done so far for us (Orientation + paid apps, vold with NTFS corrections to FolioMod) + Kernel compiles
DerArtem - Compiling kernel + and being very active on getting 3G modem support for us on our folio!!
Sol Ido - Foliowidget
Teknoraver - Foliobuttons
badstorm2010 - First custom kernel on folio available.
CHANGELOG
v1.4 (changes compared to v2.2.5.0131)
libraries from v 2.2.5.0131 release of 18-feb-2011
eUpdate patch from stock release of 18-feb-2011 (touchscreen+i2c update)
Paid apps working. (thanks to weeds2000 for the fix)
rotation & mouse (fixed by Weeds2000)
Fixed toshiba pegadroid support (ext.jar missing pegadroid service), important for toshiba services.
added newest Market app (2.2.11)
3D frame hack (increased framerate from 51 to 70), if you got touchscreen issues, here is the rollback patch
BROKEN: 3G support (new toshiba kernel required for display driver, and we got no source available yet)
BROKEN: CIFS support
Filesystem optimization still active
newest flashplayer v10.1.120.10 included.
newest mediaplayer & filemanager update from toshiba.
Maps 5.0 added with multitouch rotation support
build.prop changed to emulate GalaxyTab (tablet Market support with more apps)
NOTE: Name is written as SGH-T849 (please just ignore, forum reports will be ignored too)
HDMI option added in Settings, for option to switch between 480p,576p,720p,1080p
note: tablet is still just 1024x600, so desktop is scaled, movieplayback should be correct.
360 degree rotation
settings - gapps sync enabled
deodex'd
wpa supplicant (adhoc) support (use FolioWidget to enable)
Added WMA/WMV support (upto 1080p)
Fixed Wifi script issues
Fixed /mnt/sdcard mount location (apps issue, better support now)
Root'd (Superuser + su included)
Rooted recovery + busybox tools
increased main filesystem (252MB)
SpareParts (disable "compatibility mode" to have old apps fullscreen.
Taskkiller included (Fixed for Toshiba framework)
More Locale 2 included (so all languages can be selected)
BROKEN: NTFS / CIFS / 3G support will be enabled as soon as a kernel source update is available, so DerArtem can compile
a working kernel for us.
Thanks to all those which have donated because of this FolioMod. Its truly appreciated to see people actually
like this and would pay a little to get the improvements in place!!
Thanks!
WARNING: Use this image at your own risk and i take no responsibility if
you brick your tablet.. Image has been tested on a Toshiba Folio 100 and works fine if guidelines are followed.
11.01.2011
Weeds2000 gave it a go, and fixed the download of paid apps! im sure alot will be happy to read this.
Then i found another tweak in the screen driver, to increase framerate which currently was only 51. now its increased to 80.
on top of this, DerArtem is currently working on making it possible to use USB 3G dongles on our folio, so we can go online using the phone functionality in Android. I have for now, enabled some phone functions and activated the signal level indicator (might be annoying, but enhancement has a cost for now).
It also seems, that i by mistake had enabled locationservices in the build.prop, so at every boot the GPS, which we don't have, was enabled and caused an additional CPU load during a bootup. this is now fixed as well.
31.12.2010
the update pack includes some fixes for wpa_supplicant issue, where it did not switch to the correct adhoc wpa_supplicant.
and weeds2000 has brought a new update to the orientation so compass works, but mouse is still wrong.
lastly it fixes the sensor readings which made your tablet unable to rotate.
30.12.2010
A little more details on v1.3 update release..
V1.3 went through a public beta1 stage and issues were found and fixed where possible.
While fixing bugs in 1.3beta a 3D performance pack was found with the Viewsonic forum, and i tested it with our Folio, with changes as required to match our system. and it increased framerates. So that is now part of the new 1.3.
Furthermore the filesystem I/O performance bugs were found and fixed, and we now have a 330MB partition running on a loopback device, making database calls and small file changes much faster.
With the ElocityA7 i found the newest Flashplayer minor update revision, and of course replaced our Toshiba beta with the new one found.
Other users has suggested kernel tweaks which also has been added to the v1.3, one of them is the "swappiness" parameter, it is suggested to increase application handling on our folio and its now "live" in this release.
Sol Ido, provided us with the 0.3.4 edition of the FolioWidget, which includes a tricker enabler for switching between the regular wpa_supplicant and the wpa_supplicant for adhoc use also included in 1.3.
The orientation fix from weeds2000 is now default included into v1.3, but can be removed with a rollback patch found in the patches section in Post #1. it does have flaws like mouse pointer moves in "portrait" mode right now. compass should not be working correctly. but in general more apps utilizing the orientation/sensor is now working much better.
With FolioMod 1.3 a small milestone is reached, getting 3000+ in Quadrant score without actually cheating here
But of course Quadrant benchmarking is just one way of meassuring our device, CPU performance has not changed at all, so dont get too excited, but it does help in the overall experience of your tablet.
19.12.2010
A little picture to document the problem with rotation on our tablet and other tegra2 tablets. click picture for better details.
{
"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"
}
as you see on the picture above, our tablet has native 0 degree in landscape mode where mobilephones got portrait native.. you can call this failure of nvidia, or someone else, but it seems that someone thinks this should be the standard.
if we can get the X and Y curve switched, we might just get it working normally.
12.12.2010
- Version 1.2 introduce use of the official patch installer from Toshiba which shows progress bar indicator movements on the screen, if recovery menu is not shown.
- Version 1.2 offers the newest toshiba update 2.5.0053 features, but which?
- BadStorm2010 managed to get a custom kernel compiled, which for adds support for ext4(future support),OpenVPN and cifs support, so you can mount filesystems over network.
- The FolioWidget offers control of your hardware buttons to have lights enabled and turns off only when pressed (good during evening/night)
- By failure of mine, the Vending.apk (Market app) included in 1.2, slows down the folio, so to enhance and fix it, i added a patch which adds the newest Market app to our folio with new design and way of selecting apps (actually is much better).
- as the framework is new, i tried to include all old features as 360 rotation , wma/wmv , Google apps + /mnt/sdcard location fix and other small issues.
- Paid apps still remain an issue with toshiba framework, only solution for you that want/need it, is to use the old 0.2 edition with nvidia framework.
29.11.2010
Currently the Toshiba edition 1.0b is having more issues than compared to 0.2a software wise. there is a freeze issues, and awake issues(solved,but fix is not released) and google paid apps cannot be downloaded.
So if you're ok without proper BT functions and usbstick unmounting, the 0.2a is probably you're best choice right now..
But if you need mouse/keyboard, usbstick proper unmount, 360rotation, the toshiba mod is the way forward.
I will try and get the freezing fixed, but more testing is needed..
28.11.2010
the Toshiba mod was created due to all the small differences in the framrwork with Bluetooth, USB functionality and sdcard card functions. Like on phones, vendors always do a little customization, which not always serves all users nicely when the image is modded based on other models. But now the stock rom is available with modded functions, so all should be happy now.
25.11.2010- on top of the above mentioned changes, here are some more regular info
- The new 0.2a still has USB stick/sdcard unmount issues, which is only part of the toshiba framework to handle for now. Im working on getting it to work on stock android.
- Increased the desktop sizing to 7 vert/horz , so more space for widgets and placement.
- media player extract image information.
- Wpa supplicant will not show signal strength for now, but im sure the better functionality might compesate for this.
(this has been tested with my Galaxy S running tetherAP function, and i could go online using my mobile connection)
Tested(v0.2a),
-Gapps,Angrybirds,Movieplayback(Yxplayer)+WMV/WMA, HDMI out, usb mass storage to pc, sdcard,usbstick, websurf+flash
- rotation , Market download, Power off,ad-hoc connectivity,.
I will test it now, downloading (very very slow :S), thank you very much for your work your are my hero
zizouth said:
I will test it now, downloading (very very slow :S), thank you very much for your work your are my hero
Click to expand...
Click to collapse
its very slow, because there is like 20 of us who are downloading the file at the same time.
well the one who gets it up an running first, please post a step by step for the noobs ( like me) and give some impressions how the device works with this first better rom!
Anyone is welcome to post mirrors, i dont needs credits for those.
Btw, im also uploading a stock mod for this folio..not sure it takes bandwidth, maybe too many mods on my hosting solution, as its probably busy somehow..
and we all know Folio100 is not THAT popular yet! so many is so much said
Downloaded but file is corrupt... re-downloading
Great , going to download it and try it ! Thanks
zizouth said:
Downloaded but file is corrupt... re-downloading
Click to expand...
Click to collapse
Re-downloading with download manager --> file is corrupt again, please re-upload it
Dexter_nlb.
regards
No problems with the Download here.
I installed everything through the System Update, but nothing changed at all. Do I have to perform a factory reset before applying the folio mod? (My folio is rooted, I tried to install some google apps and so on...)
The first line when applying the mod says "E: can't mount DEFAULT_PATH" - how about the others?
Anyway: thanks a lot for your work!
At some point you have to select "apply sdcard:update.zip" or something like that with vol - and (i think) power
For me it did a factory reset but nothing else, tried angry birds to see if anything had changed but nope.
zizouth said:
Re-downloading with download manager --> file is corrupt again, please re-upload it
Dexter_nlb.
regards
Click to expand...
Click to collapse
i have uploaded to that site like 100 times, never had problems...
but yes, today the speed seems very slow even when im uploading, maybe its simply timeouts on your download so the zip gets corrupt.
filesize should be 164.256.143
shinebar1001 said:
No problems with the Download here.
I installed everything through the System Update, but nothing changed at all. Do I have to perform a factory reset before applying the folio mod? (My folio is rooted, I tried to install some google apps and so on...)
The first line when applying the mod says "E: can't mount DEFAULT_PATH" - how about the others?
Anyway: thanks a lot for your work!
Click to expand...
Click to collapse
Some people in http://forum.frandroid.com/topic/31757-foliomod-v01/page__gopid__526895#entry526895 who have tested your rom say also nothing changed at all...?
also for me nothing changed. Download and update work fine. After update I try to install Angry Birds but when I
run it I can hear the sound of the game, but I don't see nothing.
Is possibile with this mod install the Android Market?
Oneiros7 said:
For me it did a factory reset but nothing else, tried angry birds to see if anything had changed but nope.
Click to expand...
Click to collapse
Process takes like 1 minute.. so did it reboot instantly or?
zizouth said:
Some people in http://forum.frandroid.com/topic/31757-foliomod-v01/page__gopid__526895#entry526895 who have tested your rom say also nothing changed at all...?
Click to expand...
Click to collapse
are people using the "update.zip" inside the zip i released? or simply putting this one on the sdcard?
when installing it shows text, when HOME button is pressed this is clearly one way to confirm something.. just rebooting does not say much here..
here is another way:
- Reboot into "Firmware Update" menu.. (Press MENU to show actual recovery menu screen when booted into recovery kernel, after the "recovery logo" shows)
- Insert sdcard into slot, and move to "update firmware" second line.. and press power button to execute.
below you should see the information on steps taken..
Dexter_nlb said:
are people using the "update.zip" inside the zip i released? or simply putting this one on the sdcard?
when installing it shows text, when HOME button is pressed this is clearly one way to confirm something.. just rebooting does not say much here..
Click to expand...
Click to collapse
Yes they are using update.zip inside the zip.
Hello, I tried and the message was :
Code:
Extractiong packs...
Done Extraction...
Preparing filesystem...
tun adbd
+---------start adb daemon-------+
+---------installing boot-------+
+---------installing recovery-------+
+---------extracting system-------+
+Instaling system, this takes a while
+-----------------------------------------+
Installation done.now reboot system.
Formating MISC:...
I reboot and same launcher, no gapps, no opengl2.0
Okay, tried the other way:
Booted into Firmware update without the sd-card until the android with an exclamation-mark-sign shows up.
Pressed the Home-Button an got into the system recovery utility.
Second lin is apply sdcard:update.zip (Vol down + Power on)
Code:
Folio100 Open Recovery starts:
Extrackting packs.
Done Extraction
preparing filesystem
rund adbd
+--start adb daemon--+
+--installing boot--+
+--installing recovery--+
+--extracting system--+
+Installing system, this takes a while (correct ;))
+---
Installation done.now reboot system.
Install from sdcard complete.
Formatting MISC:...
Rebooting system (Power)
So, unitil now everything looks fine. After a reboot nothing changed
Hope this helps to debug.
Danny
shinebar1001 said:
Okay, tried the other way:
Booted into Firmware update without the sd-card until the android with an exclamation-mark-sign shows up.
Pressed the Home-Button an got into the system recovery utility.
Second lin is apply sdcard:update.zip (Vol down + Power on)
Code:
Folio100 Open Recovery starts:
Extrackting packs.
Done Extraction
preparing filesystem
rund adbd
+--start adb daemon--+
+--installing boot--+
+--installing recovery--+
+--extracting system--+
+Installing system, this takes a while (correct ;))
+---
Installation done.now reboot system.
Install from sdcard complete.
Formatting MISC:...
Rebooting system (Power)
So, unitil now everything looks fine. After a reboot nothing changed
Hope this helps to debug.
Danny
Click to expand...
Click to collapse
well, it looks correct, so next question is; can you use adb? and login with shell and maybe extract the /tmp/recovery.log file?
if you got no root, just enter "rootme" and you should be disconnected from adb.
kill adb with "adb kill-server" and relogin with adb.
and you got root.
Is this correct?
power vol+
vol+ ->"continue factory data reset..."
vol- ->"continue system update"
vol+ ->"confirm"
when adroid appears HOME button
vol- ->"apply sdcard:update.zip"
power
then
"reboot now"
no need to do any wipe data/factory reset or wipe cache partition?
at the end I have
Finding update package...
Opening update package...
Installing update...
-----------------------------------
| FOLIO100 Open Recovery |
-----------------------------------
Extracting packs...
Done extracting...
Preparing Filesystem...
run adbd
blahblah
Installing system, this takes a while (not really in my case)
Installation done.now reboot system.
Install from sdcard complete.
Formatting MISC...
The picture behind is the little android with a exclamation point.
It's my 5th time doing that and still no luck
hum sorry for the post not fast enough
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?
------------------------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
------------------------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,
There are 2 firmware builds at the bottom,
1st with google play store as an app store.
2nd with Aptiode store.
Choose which version you wish to select Google play version is labelled as GP & Aptiode store is labelled as AP.
______________________________________
This Samsung S7 themed Rom has been personally 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 OR UPDATED
_____________________________________
• 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 for G930F Ui resemblance.
• Lightning Browser (looks like chrome)
• gallery V1.1 with photolocker
• Modded Camera FV-5
• JRD Secure container
• JRD plugger
• Updated music FX
• JRD media container
• Samsung Boot animation
• Samsunf Shut Animation
• G930F boot logo
• G930F icons and theme
• Samsung G930F oreo Ringtone Sounds
• Samsung G930F oreo Notification Sounds
• Samsung G930F oreo UI sounds (where available)
• Build edited to display device as SM-G930F
• Fingerprint updated
• Updated to Release Keys (was test keys)
• 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, no need for root manager
• BUSY BOX binary pre installed to system, no applet's are preinstalled though
Plus alot more stuff i cannot remember as i never made a changelog this is listed as release software as i deem it stable enough for daily use but as the system is customised it should be treated as Beta software, any bugs please report them to me so they can be fixed.
---------☆☆☆MODIFIED BOOT IMG☆☆☆---------
This Rom for now must use the modified boot.img & external SD card should you wish to use either of these roms due to a mounting error somewhere, no app will install despite there being 70mb + on both builds /data partitions so i need to fix, all works perfect with the modified boot.img,
Partition your SD card as follows using Mini partition tool with 2 partitions in this exact order EXT 4 Cannot be first or you will face data decryption error until rectified.
•PRIMARY partition
- FAT32 label it data
•PRIMARY partition
- EXT4 label it mmcblk0p2
To flash with modified boot.img open the scatter file, click on the BOOTIMG file path & select the modified boot.img,
Insert the newly partitioned SD card into the device and flash the firmware using the instructions on how to flash below.
__________________________________________
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
•select the scatter.file
•insert the modified boot.img into BOOTIMG path
•change flash method to download only
•click start
•Wait for it to complete the flash
•Disconnect & Reconnect the usb cord
•Wait for device to start charging
•Turn on & enjoy
DO NOT USE "format all + download" in SP flash tool unless you have a backup of your firmware and security partition or you WILL lose your imei.
_________________________________________
LINKS
GP Build https://drive.google.com/file/d/1gpGH1Wj_JQHFFroV12r1PcHsxeE5zbTV/view?usp=drivesdk
AP Build https://drive.google.com/file/d/1VhZmpZyA-z-N6phAn9nfBifL-Lk0pdWL/view?usp=drivesdk
SP Flash Tool https://spflashtool.com
Modified boot is located within the .zip all credits to luca Roggero for his modified boot.img
can't get it to load with modified boot
i partitioned it as directed on a 32gb card flashed modified boot and it wont load also theres a weird glitch on this rom where once your battery hits about 20% it just instantly drops to 0 also cant install a custom recovery with easy magic (any of them) do u know the code to unlock the bootloader?
thinkotherwize said:
i partitioned it as directed on a 32gb card flashed modified boot and it wont load also theres a weird glitch on this rom where once your battery hits about 20% it just instantly drops to 0 also cant install a custom recovery with easy magic (any of them) do u know the code to unlock the bootloader?
Click to expand...
Click to collapse
Sorry for the late reply ive been busy busy busy making android 6.0.1 for the R11 max its almost finished,
Righto lets get started and get you up and running with the modified boot.img
Firstly how did you partition the Sd card, what partitions were they formatted to exactly and in which order,
They must be formatted in this exact order ill include the info aswell
Label: DATA
Format: FAT32
Type: PRIMARY
Label: MMCBLK0P2 (use lower case letters)
Format EXT4
Type: PRIMARY
i use mini partition magic and it works beautiful,
If the system boots on your device also it means that the boot.img is compatible with the device,
Which means that the modified boot.img is also compatible with your device as the original untouched works and all thats been done to it is the mount points were changed to the ext4 partition on the sd card,
This is everything that was done modifications to files were as follows
mount ubifs ubi @ userdata / data -> mount ext4 / dev / block / mmcblk0p2 / data
mount yaffs2 mtd @ userdata / data -> mount ext4 / dev / block / mmcblk0p2 / data
mount ext4 / emmc @ usrata / data -> mount ext4 / dev / block / mmcblk0p2 / data
mmcblk0p2 is the name of the 2nd EXT4 partition of the sd card, which must be second and not first
The sd card must have 2 partitions, the first FAT32, the second ext4, both primary
Try that and see if it works,
If it dosent boot past the power on logo message back here you may have another revision board as there are a few in which i have a boot.img for 2 of the R11 max boards so will get your phone working with whatever GB storage you set as your partition
Did you also make sure you have the NAND version of R11 MAX also as there is an R11 which is emmc and not nand ? There are 5 variations of the NAND R11 max and 3 or 4 variations of the R11
basic info on the R11 max 5 build versions
Storage type: NAND (typically hynix)
Flash Size: 512mb
DRam 478mb
Radio: 2G GSM
The only diffs for the ones above are the partition infos and the bull**** storage capacity,
Basic info on the R11, 4 build versions
Storage type: EMMC (unknown)
Flash size: 2.5GB
DRam: ( unknown )
Radio: 2G GSM & 3G UMTS
Let me know how you go and sorry for the late reply
Oh by the way what you think is a Glitch isnt actaully a glitch,
Theres nothing i can do about that unfortunately,
In the framework-res.apk battery stats are set in 15% increments to much work for me to fix on the status bar, go to settings then battery and turn your battery % on thats at least accurate
And in physical terms of the battery i hope you dont actually think there a 3000Mah battery,
They are actually cheap chinese lithium cells that produce only 1000Mah and dont last very long at all mine did the same thing around 20% if you know what your doing you can re cell the battery with a samsung cell or similar as long as you are very careful and dont put to much force on the pcb on top of the cell to much and desolder it properly you will have a working battery that actually lasts, i did it to mine but i run a phone repair shop, i dont advise you do it if you are inexperienced in that case find a replacement battery that is decent quality same same size and pin location and youll be sweet.
And about the custom recovery again nothing i can do about that ive built and not used any tools that dont work half the time with so many diff variations of custom recoveries ive made,
Ive packed them with twrp ramdisk and made all edits but they just refuse to boot and only flash white and reset,
The bootloader is pre unlocked as youll notice theres no OEM unlock,
However if you really wanna try yourself,
Connect to the phone via adb and use one if the commands below to get you into fastboot mode, thats as far as youll get though fastboot oem unlock hangs on waiting even though fastboot devices shows the device
Syntax:
adb reboot bootloader
adb reboot-bootloader
adb reboot fastboot
adb reboot-fastboot
Forget which one it is but you can try for yourself,
Ive been trying and trying to get a half decent recovery for the next 6.0 build its still stock but ive done alot of mods to recovery like enabling adb in recovery and redoing the default.prop within it also
guess i'll just hold out
well its working pretty good sans battery life, lol
are you compiling a real marshmallow build? because that will for sure solve the sdcard as internal issue and you can install gapps etc.... the playstore would work etc... it wasn't until marshmallow that google started letting you use your sd a internal, still an awesome job man i love this project, its a hobby of mine taking old bricked or soft bricked phones and trying to get them to optimal standards so far so good! keep me updated on the progress.
I definitely used minitool and followed your instructions to a tee i'm thinking 32gigs is too much for the boot.img i'm going to try and partition it smaller on the fat32 and see if it will boot then, how big do you reccomend i make the mmcblock0p2 partition? i made it 3 gigs could that be the issue? too big?
Hey mate sorry for late reply was finishing up another alcatel U5 custom recovery project,
Yeah battery life isnt the best, next build ive added scripts to optimise battery life, ram and a few other things,
With the build unfortunately i cant fit an entire 6.0 system on a 512mb flash nand it just cant be done unfortunately theres not enough space but im working on that for a later build so at the moment though next build will use SDK23 system components but it will also include mostly SDK20, SDK21 & SDK22 system components that ive managed to merge into it,
Either way the modified boot.img is neccessary regardless, Gapps and play store i can confirm does work perfectly fine on this next build and there will be roughly 50mb so a couple apps can be installed before getting the storage low warning,
Even it if were a proper dedicated 6.0 build though again it would still need the modified boot.img as even though the app has been placed on the sd card it still has to run through the main system at startup and a full memory at startup will not boot the phone so again modified boot.img is necessary,
Shouldnt matter what size you make the partitions either, these boards support up to 32GB TF cards so thats not a problem,
I have a 16GB i made 2 partitions as follows
Data 7.5GB FAT32 primary
mmcblk0p2 7.5GB EXT4 primary
In that exact order & spelt that exact way if it is still not working for you then it is purely a pilot error (being you) as i mentioned normal untouched boot.img packed in with the firmware works correct ?
That means the modified boot.img will work also they are identical apart from the fact that the internal storage has been mapped over to your SD cards mmcblk0p2 instead of your internal mmcblk0p2,
If it is still not working i want you to please take a backup of your firmware and then from that zip up the following into an archive upload it to google drive or whatever you use and post the link to it here so i can download it and have a look at it to see if there are any differences anywhere
RECOVERY
BOOTIMG
MT6572_Scatter_file.txt
I highly doubt there will be any difference as it already works on your PMT info if there were something wrong it wouldnt boot at all even with the untouched stock one,
The boot.img and recovery has been highly modified in the next build so if your facing any probs still ill need to sort it out and possibly make a second version to support it, hopefully not the case tho.
Attention all users of R11 max,
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
#-------------------------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.