{
"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"
}
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* DO NOT LEECH MY DOWNLOADS, PLEASE RE-DIRECT YOUR FORUM /PAGE
* TO THIS THREAD, IF YOU LIKE MY WORK, YOU CAN SAY THANKS,
* AND MAYBE BUY ME SOME BEERS
*/
Hello Guys !
In this thread you will find my custom ROMs and Recoverys for the ASUS Memo PAD HD 7.
You'll also find how to Unlock the bootloader (mandatory to flash any custom Recovery and Rom)
Please be sure to read (and re-read) this carefully in order to avoid unnecessary questions.
My Custom ROMs / Recoverys and also the provided Stock Rom will work on both 8 GB / 16GB WW and US Models
(The RU Model is also supported, however with limited GPS support)
Code:
[COLOR="blue"]For Instructions:Check Posts #2 and #3
Downloads on Post #4
To Flash the Asus Stock Firmware: Check Post #5 [/COLOR]
AOSP Rom
AOSP JB4.2.2:
Changelog Build 01 - 20160929
Compiled from source (except Kernel - prebuilt ... only modifications on kernel's initramfs)
Everything working (as far as i tested)
Latest GAPPS included + some Google newest Goodies
Latest Stable SuperSU v2.78 included (rom is rooted ye)
Some special goodies added on rom's source (battery % , etc), not part of AOSP
Requires: Unlock Bootloader + Custom Recovery (the usual)
Full wipes recommended , so backup , backup...
Download: https://www.androidfilehost.com/?fid=529141701856462352
I'll upload Rom later into XDA DevDB , always good to have a mirror...
Changelogs Rom 4
Asus VibeUI JB4.2.2:
Changelog v2.0 (August 02 2015)
New Build
Both Cameras working (front and rear)
Added Custom (stock) Asus camera is also working (AOSP/ASUS cameras included)
New Modified working MTK Engineer Menu ( settings> Mod)
Multi-User support (settings> Mod)
Improved Dolby Sound
Gapps included (updated and working)
Some VibeUi Lenovo apps updated (including new Launcher/ theme Manager)
Ported more Asus apps (widgets)
There's several other fixs, this build was being worked out for some time ...
Changelog v1.0 (August 31 2014)
Based on Lenovo's VibeUI, ported to our tablet and with extra features:
--> Lenovo's VibeUI, it's still AOSP Based
Dolby Surround Sound (Only tested on 16GB Model)
Multi language
Theme Manager
Advance Power Manager features
Beutifull Lenovo's apps
Other features
Also Merged The following Asus apps:
AsusCalendar
AsusStory
ASUSStudio
AsusTask
Other features:
Front Camera works (Only tested on 16GB model)
Up to date GAPPS included
Rooted
busybox
Patched hosts file
GPS config improved
Not working:
Main camera (rear) --> Depending in your hardware revision; Most users will have working rear camera
Flash Instructions / Requirements:
Unlocked Bootloader
CWM / Carliv recovery
Instalation:
- Full wipes
DEPRICATED ROMs
Changelogs Rom 1
Android 4.2.2 (JB) Based custom ROM (Stock Based):
Changelog Build v1.1 R2 (November 13 2013)
Camera buttons layout fix
Calendar sync fix
Old Builds ChangeLogs:
Changelog Build v1.1 (November 10 2013)
Added the following Android 4.4 kitkat Goodies:
Apps
Bootanimation
QuickOffice
And other necessary system files
Added both USB connection modes:USB Storage and MTP Mode(internal storage now available via MTP)
Removed CPU Governor switcher
Added Performance Control (in System Settings) with several CPU/System Mods
Added in-built Xposed framework and Gravity BOX (Several System Modifications and tweeks)
Added AsusAppLocker (Requested by several Users)
Added pictures and video tweeks
Cleaned and modified some System Interface Code
Fixed some init.d perms
Changelogs Rom 2
AOSP Android 4.2.2 (JB) ROM:
Changelog BETA v2.0 (February 08 2014)
Fixed alot of issues on the core system
Internal Storage is now readable/writable
Emulated Storage is now readable/writable
App Instalation is Fixed
Update BusyBox
Update SuperSU
Update GravityBox; Xposed Framework (Fully Working since this is AOSP)
And several other Fixs
NOT Working:
Cameras (front and rear)
Needs further work:
External Storage, will be available once you take your SDCard off, and insert again.BUT can cause random reboots.
BT, will give you FC when you turn on, but it works OK
You tell me
In addition to the ROM changelog:
External SDCard: as I said it can cause random reboots, also if you reboot the TAB it can cause bootloops,in this case just remove the SDCard and the TAB will boot just fine. Last case scenario, remove the SDCard and wipe dalvik
Benchmarks: Well its noticeable the increase in speed and less RAM usage on the AOSP Betas.
Some guys are asking me why the Antutu scores are so similar with the stock Asus/And my custom ROM?
Well you should check the ram usage/FPS between the ROMs And since the Aosp doesn't fully support the external SDCard, this will give about less 2k on Antutu scores (Storage IO / database IO)
So... If you really want to compare Antutu scores, remove your External SDCard from the stock Asus/ V1.1r2 Roms.
Changelogs Rom 3
Android 4.2.2 (JB) Based custom ROM:
Based on the new official Android 4.2.2 ROM
WW OTA (ME173X_WW_user_4.2.4.04152_20140714)
From July 14 2014
Kernel 3.4.5
Stock Flashable ROM
Replace the new OTA kernel from the older one (November 28 release), since the last one is more stable
Rooted
Flash Instructions / Requirements
Unlocked Bootloader
CWM / Carliv recovery
Instalation:
- Full wipes
GPL Compliance:
Kernel 3.4.5
(My repo containing ASUS released Kernel Source, that are FAKE... )
All the ROMs, and Recoverys are using the Stock prebuilt Kernel
My Github Repo
Credits
SuperDragonPT laugh: )
Carliv (For the awesome Carliv Touch Recovery)
Koush (For the CWM Base)
Enriki (from the forum 4pda.ru),(For the "Service Firmware/Unlocked Bootloader")
shoxxy (for letting me know the Russian's work)
iBotPeaches, brut.all (for apktool)
amarullz (for AROMA Installer)
Chainfire (for SuperSU)
rovo89 (for the AWESOME Xposed Framework), Learn More Here
C3C076 (For the AWESOME Xposed GravityBox module), Learn More Here
h0rn3t and educk (for Performance Control), Learn More Here
ViPER520 and zhuhang (for ViPER4Android Audio Effects ), Learn More Here
XDA:DevDB Information
[RECOVERY] [ROMs] ASUS Memo Pad HD 7 (me173x) [MULTILANG], ROM for the Android General
Contributors
superdragonpt
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2013-11-10
Last Updated 2016-09-28
Unlocking Bootloader and Flashing the Custom Recovery: PART #1
Unlocking Bootloader and Flashing the Custom Recovery: PART #1
Unlocking Bootloader and Flashing the Custom Recovery: PART #1
- Special TAB Format:
Make Sure your Tablet is fully Charged
Make Sure the Drivers are installed (For Detailed Drivers instalation Instructions, please check this thread)
Copy my Custom ROM (Asus_ME173X_v x.xx.zip), to the EXTERNAL SD Card, BEFORE you start the next steps...
Now in the "Download Section" get the Stock Asus Rom-and-bootloader.zip[/URL]
Included in the .zip are :
-The USB VCOM drivers and the SP_Drivers_v1.5 (Last Ones are Opcional), the VCOM Drivers alone should be enought.
- The Flash Tool
-The Asus Stock Firmware ME173X_WW_user_4.2.4.06716_20130918 (STOCK Rom; Locked Bootloader; Stock Recovery)
Open the Flash_tool.exe.
(1) Click on Scatter_Loading and choose the "MT6589_Android_scatter_emmc" from the "signed_bin" thats inside the Firmware Folder.
(2) At Flashtool Click Window and choose Write Memory
Next, Click Write Memory, Open Raw and choose the "sro-default-lock-sign.img" file from the "signed_bin" Folder.
Memory Settings must be "EMMC"
Before Flashing: Everytime when you Click on the button to Flash , the Memopad must be TURNED OFF and DISCONNECT from the PC.
After you Click on the write memory Button Connect the Pad to your PC.
The Flash Progress should beginn, when it succesfully Finished A Green Ring will shown.
Disconnect The Pad from PC
Click: Special Format #1 Settings just like in the Picture.
Click "OK" and Start the Flash Progress shown above !
After pressing "OK" connect your Tab to PC
Disconnect The Pad from PC
Next:
Click: Special Format #2 Settings just like in the Picture.
Click "OK" and Start the Flash Progress shown above !
After pressing "OK" connect your Tab to PC
Disconnect The Pad from PC
Your MemoPad is Sucessfully Formated Now lets Flash the Preloader :
Go to the Flashtool main Screen Click "Scatter_loading"
Now this Time choose the " MT6589_Android_scatter_emmc " from the root Folder.
(See next Pictures)
When you finnaly click on "Download" the following warning will appear, just press "YES"
After pressing "YES" connect your Tab to PC
Then, When The Green Ring appears Your MemoPad is Sucessfully Formated :fingers-crossed:
Disconnect The Pad from PC
(Tut from our Russian Friends and translated by our friend shoxxy)
Now You can jump to PART #2
Unlocking Bootloader and Flashing the Custom Recovery: PART #2
Unlocking Bootloader and Flashing the Custom Recovery: PART #2
Unlocking Bootloader and Flashing the CWM Based Recovery: PART #2
Download From the "Download Section" the Unlock_Bootloader install_Recovery.zip
Turn OFF the TAB
Do NOT Connect your TAB at the PC at this Stage
On the "Flasher" folder open the "Flash_tool.exe"
Then select "scatter loading" , go to the "Unlock_Bootloader install_Recovery" folder, and select the "MT6589_Android_scatter_emmc.txt"
Then press "Download"
This Message will pop-up, press "Yes"
Now Connect the TAB to PC (USB), DONT Turn it ON, keep the TAB OFF
You will hear an sound, and the flash will start
In the end, IF all is done correctly, you will see this Picture.
Congrats you now have your TAB with an CWM Based Recovery (the Carliv Touch Recovery), and the Bootloader is Unlocked
Now all you need is, is to flash my Custom Rom :laugh:
Navigation under recovery mode / Flashing the Rom:
Turn the TAB On, with the Power and Volume UP Keys (Keep The keys Pressed)
You will see the "Select Boot Mode" Menu (Check the picture)
Using the Volume UP Key, navigate to the "Recovery Mode", then Press the Volume Down Key to Select.
NOW, you will have acess to your Costum Recovery (The Recovery is Up side Down), this is NORMAL, and this happens on some new SoC's.
To Navigate on the Recovery you can use the Volume UP/Down Keys, OR You can use the Touch Buttons
Flashing The ROM:
Wipe Data / factory Reset
Wipe Cache
Advanced > Wipe Dalvik Cache
Install zip> Choose zip from sdcard
And just follow the on-screen instructions ...
System will reboot itself, when the instalation is completed
Don't worried, the first boot takes an little bit more time !
If you didnt copied the ROM to your SD Card:
Navigate on Recovery:
Mounts and storage>mount USB storage (now you can copy/paste the ROM to the SD card)
Or if you cant connect the phone to PC (Bad drivers, etc), use adb sideload:
This Recovery Supports the Aroma File Manager
Whats this? Check here
Download the Aroma File Manager
Then just copy the aroma .*zip into the "Clockworkmod" folder on the root of your SD Card
Download Aroma File Manager
MD5:19c8e9cb2e833cad74a09ad11af40445
DOWNLOADS
ROMS:
ROM VibeUI v1.0
https://www.androidfilehost.com/?fid=95916177934535008
ROM ME173X_v1.1_R2
https://www.androidfilehost.com/?fid=95916177934535951
ROM ME173X_WW_user_4.2._20140714 (Modified Official ASUS OTA)
https://www.androidfilehost.com/?fid=95916177934535953
CUSTOM RECOVERYS:
Carliv Touch Recovery (CWM) v2.1
https://www.androidfilehost.com/?fid=95916177934535012
Carliv Touch Recovery (CWM 6.0.4.4) v2.5
https://www.androidfilehost.com/?fid=95916177934535952
OTHERS:
Unlock_Bootloader+install_Recovery
https://www.androidfilehost.com/?fid=95916177934535013
Stock+Asus+Rom-and-bootloader
https://www.androidfilehost.com/?fid=95916177934535113
Asus_stock_camera
https://www.androidfilehost.com/?fid=95916177934535114
RETURNING to The Stock ASUS Rom, and Locked Bootloader
RETURNING to The Stock ASUS Rom, and Locked Bootloader Returning your Tablet Back to Stock
Download the "Stock Asus Rom-and-bootloader.zip" available in the "Download" Section.
It includes the Asus Vcom Drivers, Flash Tools and the Stock Firmware (Rom, Locked Bootloader, etc)
This will flash The STOCK ASUS Odex ROM/ Locked Bootloader / Stock Recovery
Your Tablet will be 100% Stock (This is good in case you need to return your Tablet/ Guarantee)
INFO:
Buid: ME173X_WW_user_4.2.4.06716_20130918
Android OS: JB 4.2.2
OTA Works (The Official ASUS Update) Recap Instructions:
Tablet MUST BE TURNED OFF, and with full battery
The VCOMM Drivers MUST be installed
Flashing:
Open the Flasher Folder:
Open the *.exe file "Flash_tool.exe"
Click on "Scatter-loading"
Open the "MT6589_Android_scatter_emmc.txt" That's inside the "signed_bin" Folder
Press "Download"
-- Now connect the Tablet to PC, the flash will start.
If all works OK, you will see an green circle in the End.
--Disconnect your Tablet from the PC
Now Click again on "Scatter-loading"
Open the "MT6589_Android_scatter_emmc.txt" BUT THIS TIME select the other scatter file from
the main firmware folder
You will see that this time ONLY the preloader is selected to be flashed...
Press "Download"
-- Now connect the Tablet to PC, the flash will start.
If all works OK, you will see an green circle in the End.
CONGRATS your Tablet is in STOCK Condition now !
Thank you very much, you add the last image rom too
awesome....
thank you verymuch
Wow. Any screenshots? I'm downloading the ROM now.
Thanks!
Awesome!!! I was a litter expecting 4.3 though. But the custom recovery is too good already.
Got this error, couldn't flash the custom recovery
Fixed that error, now I get this
BROM ERROR : S_SECURITY_SEC_CFG_IMAGE_CUST_NAME_MISMATCH (6074) , MSP ERROE CODE : 0x00.
Great work man. Only one question. How to lock bootloader again?
Sent from my GN
@superdragonpt thanks a lot man, finally we can backup our systems and install other roms. Great work.
tt2
ericmaxman said:
Got this error, couldn't flash the custom recovery
Fixed that error, now I get this
BROM ERROR : S_SECURITY_SEC_CFG_IMAGE_CUST_NAME_MISMATCH (6074) , MSP ERROE CODE : 0x00.
Click to expand...
Click to collapse
EDITED:
New Instructions in the OP
Please check Posts # 2 and 3
superdragonpt said:
Strange, did you tried downloading The file again and test?
last case scenario, it was an bad upload,.
if someone else is getting the same error, please Report .
Click to expand...
Click to collapse
Tried from 2 separate notebooks, same error..
Maybe you have to follow the first steps described here:
http://forum.xda-developers.com/showthread.php?t=2339895&page=30
Here the sro-default-lock-sign.img is preloaded
The preloader is included on The .zip
The flash tool wont load if The preloader isnt present.
i will look at it, on my launch break, dont worry.
but i still need to know if enyone else is getting this error
EDITED:
New Instructions in the OP
Please check Posts # 2 and 3
Is it possible to flash without loosing all user apps and data?
Do a TB backup first.
Powered by Galaxy Note
kanefan67 said:
Is it possible to flash without loosing all user apps and data?
Click to expand...
Click to collapse
First root with farmaroot (search in xda)
Than instal titanium backup and backup all user apps.
Than do all the things n the fiat poat of this thread.
And restore with titanium backup afterwards.
Sent from my GT-I9070 using xda app-developers app
Related
DISCLAIMER:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* DO NOT LEECH MY DOWNLOADS, PLEASE RE-DIRECT YOUR FORUM /PAGE
* TO THIS THREAD, IF YOU LIKE MY WORK, YOU CAN SAY THANKS,
* AND MAYBE BUY ME SOME BEERS
*/
Hello Guys !
In this thread you will find my custom ROM And Recovery for the Wiko DarkMoon
Please be sure to read (and re-read) this carefully in order to avoid unnecessary questions.
Instructions and Frequently asked questions (FAQ):
For Instructions jump into post #2.
FAQ jump into post #3.
Wiko DarkMoon internal memory re-partition, jump into post #4.
How to Revert to the STOCK Rom / Recovery / Partition Layout, jump into post #4.
Recovery INFO
The salient features of Carliv Touch Recovery include:
Based on CWM 6.0.4.4
Full Touch Support
With features of Cannibal Open Touch
Aroma File Manager Support
Support for both Edify and Amend scripting allows flashing all ROMs
Touch screen button controls
Advanced Backup
Advanced Restore
Delete old backups
Persistent settings
User-defined backup locations
ADB Sideload
Update CTR v2.5 (30/07/2014)
Changelogs:
New Menu Layout
Tar + Gzip Backup Compression : ( "Backup/Restore" -> "Default Backup Format" )
Your Backups will be smaller now, just like on the old native CWM
Removed "wipe all" option from wipe menu ( if you need to wipe system, use "format system" from "mounts/storage")
Rearanged menu order in root menu to restore CWM order
There's now an "nvram backup/restore" menu in "carliv" section
The nvram partition will be backed up in clockworkmod/backup folder as nvram.img. This will help if you lose IMEI and other communication features. It will work only if you have the nvram partition of size 0x500000 (check your scatter) and if you have the nvram defined as /dev/nvram path in recovery.fstab. If the nvram partition is damaged (as in flashing an oversized recovery) this will not help you, and you need SPFlashTools to reflash with format your phone official firmware, and after that flash this recovery, boot in recovery and restore nvram.
some other small changes.
Changelogs
Android 4.2.2 (JB) Based custom ROM:
Changelog Build v1.0 (February 22 2014)
Based on official Android 4.2.2 ROM (WIKO DARKMOON Version 8)
Kernel 3.4.5
Custom Mods:
User customize-able installation based on AROMA installer
Pre-rooted with SuperSU (v1.93)
Debloated
Added BusyBox (v1.22.1 - Stericson)
Added Ad blocker (patched "host" file)
Ziplagned apks (better performance)
init.d support with performance scripts
Network, wifi, power saving, and several other tweeks
Updated APN's from CyanogenMOD repo
Added Performance Control (several CPU/System Mods)
Added in-built Xposed framework and Latest Gravity BOX module v2.9.7 (Several System Mods)
Acess To the Mediatek MTK Eng Mode
Added the following Android 4.4 KitKat Goodies:
Apps (Including Google Launcher - GEL, with Voice Search )
Bootanimation
QuickOffice
And other necessary system files
Kernel:
Insecure
Removed Mediatek debugger (mtk.aee.aed Daemon; etc)
USB Mass Storage as Default (instead of MTP)
GPL Compliance:Kernel 3.4.5
Github Kernel Repo
Downloads:Dev-Host
WIKO_DarkMoon_JB_4.2.2_Stable_v1.0.zip - 386.12 MB
Mod_extended_USRDATA_2.5GB.zip - 7.07 MB
MT65xx_USB_VCOM_drivers.zip - 403.65 KB
Wiko_Recovery_and_FlashTool.zip - 12.54 MB
Credits:
SuperDragonPT
Wiko
Carliv (Awesome CWM based Recovery)
iBotPeaches, brut.all (for apktool)
amarullz (for AROMA Installer)
Chainfire (for SuperSU)
rovo89 (for the AWESOME Xposed Framework), Learn More Here
C3C076 (For the AWESOME Xposed GravityBox module), Learn More Here
bgcngm(For Maintaining the Gbox JB Branch)
h0rn3t and educk (for Performance Control), Learn More Here
XDA:DevDB Information
[RECOVERY] [ROM] Wiko DarkMoon (MT6582) [MULTILANG] , ROM for the Android General
Contributors
superdragonpt
Source Code: https://github.com/dragonpt/Kernel_Wiko_DarkMoon_Custom
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2014-02-22
Created 2014-02-22
Last Updated 2015-02-14
How to flash custom recovery:
Make Sure your Phone is fully Charged
Make an Full Backup of your files (Photos/Contacts, etc)
Download The MT65xx_USB_VCOM_drivers.zip
Install The Mediatek VCOM Drivers (For Detailed Drivers instalation Instructions, please check this thread)
Download The Wiko Recovery and FlashTool
Extract the .zip and you'll see two folders "Recovery" and "SP_Flash_Tool"
Open "SP_Flash_Tool" > Flash_tool.exe > Scatter-Loading> And select the "MT6582_Android_scatter.txt" from the "Recovery" Folder
Turn OFF your Phone
Press "Download" (don't worry with the pop-up "Download-Warning" Message), press YES
Connect Your Phone to PC (Turned OFF) , The Flash Progress should beginn, when its succesfully Finished A Green Ring will shown.
Congrats The Recovery is installed
How to enter into recovery mode:
With the Phone completely turned off...
Press and hold VOL. UP + VOL DOWN + POWER keys and turn on the phone.
Keep holding the keys, wait until you see on Phone:
Code:
"Recovery Mode: Volume UP"
"Factory Mode: Volume Down"
Then Press on VOL. UP key, and Recovery will load.
Navigation under recovery mode:
As soon as the splash logo disappears, Carliv Touch Recovery menu will appear. Navigation is Full Touch.
You can also use VOLUME keys (navigate up with VOL. UP and navigate down with VOL. DOWN) and POWER key to apply the action.
Scroll Pages under Recovery: To Scroll page down you have to swipe right, and for scroll page up to swipe left. Also swipe left for Go Back.
Aroma File Manager:
This Recovery Supports the Aroma File Manager
Whats this? Check here
Download the Aroma File Manager
Then just copy the aroma .*zip into the "Clockworkmod" folder on the root of your SD Card
Flashing The ROM:
Copy The ROM to The External SDCard
On Recovery:
Wipe Menu> Wipe All Data - PreFlash (Select YES - Wipe All)
Wipe Dalvik Cache (Select YES - Wipe Dalvik Cache)
Install zip > Choose zip SDCard (Select the location of the ROM.zip)
And Follow The On-Screen AROMA Installer Instructions
In the End the Phone will Reboot Itself
The first Boot will take some minutes (it's normal)
F.A.Q
Q: How Can i acess The MTK Eng Mode?
A: GravityBox >Engineering Mode
Q: What Mods can i do on the Eng.Mode?
A: There are alot of things you can do, the two most common are:
Increasing volume Level:
MTK Menu> Hardware Testing> Audio> On the "headset mode" and "LoundSpeaker Mode" set max values to 145 (The max is 160, but i dont advise it, stay safe and use the 145 value)
Speed up the GPS reception :
(Before Going to the MTK Menu)
Open the app "FasterGPS", and give it root permissions
Choose your Continent, your region (at this point, your gps is properly configured with your country *.ntp values)
(Now on MTK Menu ...)
MTK Menu> Location> Location Based Service> On the "AGPS" tab, tick the "Enable A-GPS", and on the "EPO" tab, tick "Enable EPO" and "Auto Download" , this last option will download the EPO files it requires an data connection.
Start the app "GPS Status", in the first Satts Lock, you need to wait a little bit (it can take up to 15m, be sure you are in an Open Area).
When you get an good lock, on Satts, your DONE.
A: I dont see the Development Options, how can i acess it?
Q: Unlocking the Development Options:
Go to "Settings" > "About Phone"
Then tap 7 times on the "Build Number"
Q: Where are the Development Options?
A: Settings> Developer Options
Q: What is the Performance Control?
A: Its an Control Panel, where you can Change / managed the CPU Governors/ IO Shedulers / among several other things.
Q: The Launcher sometimes seems an bit laggy
A: Go to Settings> Developer Options> on "Window animation scale" set it to .5x, and on "Transition animation scale" set it to .5x
Q: I really like your work, how can i thank you?
A: You can press the "THANKS" button, and if you want, you can donate some beers to me
Wiko DarkMoon internal memory re-partition
Mod Extended Userdata v1 ( 2GB ) --> Removed / Use the v2
This Mod will extend userdata partition to 2GB (stock size is 1GB) and the rest of the space will remain for the internal sdcard
NOTE: Make an FULL backup of your Rom under Recovery, and don't forget to also backup your Internal SDCard since it will be full erased
Instructions:
Download the Mod extended USRDATA.zip
Shutdown your phone
Extract the .zip
Open SP_Flash_Tool dir > Flash_tool.exe
In scatter-loading load the MT6582_Android_scatter.txt from the Internal_2GB_Mod Dir
Press Download
After flashing is complete, boot into recovery mode and format /data (under Mounts and Storage Menu)
Optionally, if you want to restore previously saved userdata, go to backup / restore > and restore data (advanced restore feature)
Profit
Mod Extended Userdata v2 (2.5 GB)
This Mod will extend userdata partition to 2.5GB (stock size is 1GB) and the rest of the space will remain for the internal sdcard
NOTE: Make an FULL backup of your Rom under Recovery, and don't forget to also backup your Internal SDCard since it will be full erased
Instructions:
Download the Mod extended USRDATA_2.5GB.zip
Shutdown your phone
Extract the .zip
Open SP_Flash_Tool dir > Flash_tool.exe
In scatter-loading load the MT6582_Android_scatter.txt from the Internal_2.5GB_Mod Dir
Press Download
After flashing is complete, boot into recovery mode and format /data (under Mounts and Storage Menu)
Optionally, if you want to restore previously saved userdata, go to backup / restore > and restore data (advanced restore feature)
Profit
Reverting to the Stock ROM
This will revert back your phone to STOCK (including the stock recovery), in case you need to send your phone to the Service Center
Instructions:
Go to Wiko's website and download the latest Rom Version:
http://fr.wikomobile.com/maj.php?telephone=131
Follow the instructions given ...
Older instructions:
Download the DARKMOON_JB4.2.2._Stock Rom-wiko_rev8.zip
Use the SPFlashTool that i provided with the CWM Recovery .zip
Make sure phone is fully charged
Shutdown your phone
Extract the .zip
Open SP_Flash_Tool dir > Flash_tool.exe
In scatter-loading load the MT6582_Android_scatter.txt
Press Download
After flashing is complete,you'll see an green circle
Profit
Thanks. Can you add some screenshots?
h3lder said:
Thanks. Can you add some screenshots?
Click to expand...
Click to collapse
Was Uploading, check under the ScreenShots TAB
Regards
I doubt:
on step "How to flash custom recovery" - before you can do this you need to have already rooted the device?
can you please add how to root the device? it will be nice to complete better all the info.. but is already great!
congrats and thanks you! as soon as i by my wiko darkmoon i will definitely try it!
sapoide said:
I doubt:
on step "How to flash custom recovery" - before you can do this you need to have already rooted the device?
can you please add how to root the device? it will be nice to complete better all the info.. but is already great!
congrats and thanks you! as soon as i by my wiko darkmoon i will definitely try it!
Click to expand...
Click to collapse
Hi
You can root with framaroot, but i dont think thats necessary.
Just flash The recovery, then The ROM.
Regards
superdragonpt said:
Hi
You can root with framaroot, but i dont think thats necessary.
Just flash The recovery, then The ROM.
Regards
Click to expand...
Click to collapse
Ok understood, thanks
Do this rom will work with my Xolo Q700S?
Sent from my Q700S using xda app-developers app
superdragonpt:
Where can you please downloaded the source code for kernel mt6582? Can you give me a link please?
Or: Your sources kernel what you gave to download are original (unchanged)?
Edit:
OK. I found where you can download the source. Sorry for the spam.
http://forum.xda-developers.com/showthread.php?t=2645756
http://forum.xda-developers.com/showthread.php?t=2650513
Hi
You guys are all crazy with the MTK leaked sources, but do you even have an clue what those sources are?
You cant just compile an source that's customize for other phone , thinking it will work on yours.
There's a lot of work to be done, and you need an huge amount of luck to have your phone drivers available in that source.
This said, I will appreciate that people avoid off-topic and other phones talk in this thread.
This ROM and recovery will only work on wiko darkmoon and Micromax a200 (clone).
If your using this ROM as a base for another MT6582 phone, please be an gentlemen and give proper credits.
Regards
Added Internal USRDATA Mod to the OP
Check post #4
Enjoy
superdragonpt said:
Added Internal USRDATA Mod to the OP
Check post #4
Enjoy
Click to expand...
Click to collapse
Great work, thanks.
Do you know by any chance if there is any option to add languages to this rom? Wiko doesn't include many languages. I can use locale2 from google play, but that only translates some of the functions.
skydancer79 said:
Great work, thanks.
Do you know by any chance if there is any option to add languages to this rom? Wiko doesn't include many languages. I can use locale2 from google play, but that only translates some of the functions.
Click to expand...
Click to collapse
The ROM is multi language.
What language where you looking for?
Regards
superdragonpt said:
The ROM is multi language.
What language where you looking for?
Regards
Click to expand...
Click to collapse
Slovenian...most android phones have it. Moto G had the same "problem"
skydancer79 said:
Slovenian...most android phones have it. Moto G had the same "problem"
Click to expand...
Click to collapse
Hi
Yes i know, when i made a MIUI rom for my old ZTE v970, i had an hard time trying to find the proper strings for your language.
Even on stock roms from big brands, its very rare to find support for that language.
Im trying to merge and revise some strings from various sources, maybe in an future version.
Regards
superdragonpt said:
Hi
Yes i know, when i made a MIUI rom for my old ZTE v970, i had an hard time trying to find the proper strings for your language.
Even on stock roms from big brands, its very rare to find support for that language.
Im trying to merge and revise some strings from various sources, maybe in an future version.
Regards
Click to expand...
Click to collapse
Great, that would be awsome.
As for rarity of my language, I find it quite well supported. Google Nexus has it, all Samsungs have it, so does HTC, Sony... I know Prestigio and Gsmart have it. CM also. It's not a big deal, but nevertheless - I wouldn't mind having it
Great ROM btw, very customizable.
skydancer79 said:
Great, that would be awsome.
As for rarity of my language, I find it quite well supported. Google Nexus has it, all Samsungs have it, so does HTC, Sony... I know Prestigio and Gsmart have it. CM also. It's not a big deal, but nevertheless - I wouldn't mind having it
Great ROM btw, very customizable.
Click to expand...
Click to collapse
Hi
Well good news and bad news
The good:
I managed to Build an UNOFFICIAL Lewa Rom for our device, currently fixing the lastest issues and adding multi-language support.
So since im currently working on this language strings, might as well use that work for this rom also.
Preview pics:
http://i.imgur.com/VAGpQI3.png
Http://imgur.com/1IADxZx
Http://imgur.com/1C56EO6
The bad:
From what i gather until now, only about 100 slovenian strings are compatible (this is less than 5% of overall translation files), will keep looking
Regards
superdragonpt said:
Hi
Well good news and bad news
The good:
I managed to Build an UNOFFICIAL Lewa Rom for our device, currently fixing the lastest issues and adding multi-language support.
So since im currently working on this language strings, might as well use that work for this rom also.
Preview pics:
http://i.imgur.com/VAGpQI3.png
Http://imgur.com/1IADxZx
Http://imgur.com/1C56EO6
The bad:
From what i gather until now, only about 100 slovenian strings are compatible (this is less than 5% of overall translation files), will keep looking
Regards
Click to expand...
Click to collapse
So is this ROM fully functional? I mean no bugs? For English language.. I could test it on my Turbo mini
(Click on the image above to download my MultiROM Manager App)MultiROM for the Samsung Galaxy S3 i9305, brought to you by Alexander_the_B0ss
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy S3 4G. It can boot any Android ROM . Besides booting from device's internal memory, MultiROM could boot from external SD card(untested). The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system.
Features:
* Multiboot any number of Android ROMs (as many as your internal memory can hold)
* Restore nandroid backup as secondary ROM (damn useful feature)
* Boot from Internal memory and MicroSD Card
Warning!
This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong (even if never happened until now) and you will have to flash stock firmware with Odin. Make backups. I personally can't stress enough for you people to make nandroids becuase you never know.
Installation
Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app Install my modified app and select MultiROM and recovery on the Install/Update card the app is still in alpha, so don't select install, use manual install below. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are choosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM itself - download the ZIP file and flash it in recovery.
Modified recovery - download the ZIP file and flash it in recovery or Mobile Odin app to flash the recovery.img contained inside ZIP.
Patched kernel (Only TWO: AGNi PureCM or AGNi PureSTOCK) - Download the ZIP file and flash it in recovery (seems like kexec-hardboot isn't activated by psndna88, so menu won't show up on boot)
*Downloads in Post #2*
If your MAIN ROM is TouchWiz or TouchWiz based, please use AGNi PureSTOCK kexec-hardboot status unknown, someone with stock rom please install app and tell me if kexec-hardboot is enabled.
If your MAIN ROM is not TouchWiz, but CM or AOSP (basically custom rom except MIUI) use AGNi PureCM no kexec-hardboot, tested.
You current rom will not be erased by the installation.
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using MicroSD Card (UNTESTED)
During installation, recovery lets you select install location. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to MicroSD Card takes a bit more, because the external memory is (usually) slower and it needs to create the images. Also boot process is longer, highly depends on card's class. You can find ROMs installed on SD card in the "External" tab in boot menu.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
Add ROM - Add ROM to boot manager
List ROMs - List installed ROMs and manage them
Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
Settings - Well, settings
Manage ROM
Rename, delete - I believe these are obvious
Flash ZIP (only Android ROMs) - Flash ZIP to the ROM, for example GApps
Add/replace boot.img - Replaces boot.img used by the ROM, this is more like developer option.
Screenshots
Application
Recovery (Sorry for pictures...)
Bonus pic(zoom to see the RGBG-Matrix (PenTile))
My Homescreen and Lockscreen (for those interested)
Big thanks to Tasssadar for this awesome utility.
XDA:DevDB Information
MultiROM, multiboot tool for Samsung Galaxy S3 4G (i9305), Tool/Utility for the Samsung Galaxy S III I9300
Contributors
Alexander_the_B0ss
Version Information
Status: Beta
Current Beta Version: v32
Beta Release Date: 2015-08-30
Created 2015-08-29
Last Updated 2015-09-02
Reserved
DOWNLOADS
MultiROM itself: HERE (Check NOTE 2 below for testing zip)
Uninstaller: HERE
Recovery: HERE
Note 1: For recovery use 720x1280 multirom theme from here.
Note 2:
MultiROM Installer with MultiROMManager app and TWRP theme installation testing zip here. Basically what this zip does is, after MultiROM is installed, it copies to system/app my own version of MultiROM Manger to support i9305, then copies to the internal sdcard the theme for TWRP and sets the correct attributes.
What is that? I dont understand
a possibility to install more than just one operating system
Quick update for you guys:
Recovery works, but the theme is kinda weird, so use the theme provided for 'perfect' recovery
MultiROM menu won't show on boot, sent PM to Tassadar for help request. Meanwhile, i am trying to modify MultiROM Manager app to support i9305 to possibly have a workaround for the menu not showing up.
Stay tuned for more development and an OP update after everything is working. CYA
Another quick update for the ones interested in the project. I have succesfully compiled MultiROM Manger app that detects our device (after twenty attempts, then gave up and updated Android Studio to the latest version and redownloaded Android SDK and NDK. First attempt after reinstall worked).The APK fresh from the oven is here. This represents a milestone in MultiROM development because with the app now detecting the device one can avoid the boot menu not showing bug. BUT WAIT, THERE'S MORE
The bug i talked about is related to kernel, because the app doesn't detect kexec-hardboot.
Stay tuned for updated OP soon™.
Error in flashing. 'E: Error executing updater binary in zip '/external_sd/Roms/MultiRom/multirom-20150829-v32-UNOFFICIAL-i9305.zip'
Tried both with unmodified TWRP and MultiRom TWRP
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
fs71gh said:
Error in flashing. 'E: Error executing updater binary in zip '/external_sd/Roms/MultiRom/multirom-20150829-v32-UNOFFICIAL-i9305.zip'
Tried both with unmodified TWRP and MultiRom TWRP
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
Click to expand...
Click to collapse
Are you really trying to install this on Note 4? Damn. It is only for i9305, aka m3xx aka m3 aka S3 4G. So WRONG FORUM
Alexander_the_B0ss said:
Are you really trying to install this on Note 4? Damn. It is only for i9305, aka m3xx aka m3 aka S3 4G. So WRONG FORUM
Click to expand...
Click to collapse
Sorry for your confusion but we also have an Eclipse for S3 LTE which is already in this forum and my device is undoubtedly also S3 LTE and not Note 4
fs71gh said:
Sorry for your confusion but we also have an Eclipse for S3 LTE which is already in this forum and my device is undoubtedly also S3 LTE and not Note 4
Click to expand...
Click to collapse
I don't want to keep this on, but check this post out http://forum.xda-developers.com/not...-x-teamwin-t2956011/post57742832#post57742832 and see the codename for the SM-910F and check your reply from before
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
Alexander_the_B0ss said:
I don't want to keep this on, but check this post out http://forum.xda-developers.com/not...-x-teamwin-t2956011/post57742832#post57742832 and see the codename for the SM-910F and check your reply from before
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
Click to expand...
Click to collapse
I guess the problem is with the rom specifically (some things left out while porting), as I got your your apk working with two other cm11 roms.
@Alexander_the_B0ss
Hi boss.
I like this dual-boot initiative but i have some problem with apk (device not supported (trelte)) but i think you can solve this.
I edit the updater-script and remove this line (assert(getprop("ro.product.device") == "i9305" || getprop("ro.build.product") == "i9305");) (i test now in terminal command: getprop ro.product.device and show me i9305 ..i dont now why i can't install zip package. but i solve this with removed line.
So, i install recovery (multirom recovery) and i install zip. I install your modded apk and i have error.
On recovery, i try to install a new rom, and was installed (but on internal_memory/multirom directory i dont see any folder/file..but my space on rom was used by "new rom")
I try to inject my kernel (pureSTOCK 5.9.2). Nothing happen when i reboot my phone. I think need to show a menu with "What rom do you want to boot"..but nothing.
I can help you with tests to dev this project.
Keep up
EDIT: And, i dont now how can install a theme for TWRP..because text buttons not aligned
il3gal said:
@Alexander_the_B0ss
Hi boss.
I like this dual-boot initiative but i have some problem with apk (device not supported (trelte)) but i think you can solve this.
I edit the updater-script and remove this line (assert(getprop("ro.product.device") == "i9305" || getprop("ro.build.product") == "i9305");) (i test now in terminal command: getprop ro.product.device and show me i9305 ..i dont now why i can't install zip package. but i solve this with removed line.
So, i install recovery (multirom recovery) and i install zip. I install your modded apk and i have error.
On recovery, i try to install a new rom, and was installed (but on internal_memory/multirom directory i dont see any folder/file..but my space on rom was used by "new rom")
I try to inject my kernel (pureSTOCK 5.9.2). Nothing happen when i reboot my phone. I think need to show a menu with "What rom do you want to boot"..but nothing.
I can help you with tests to dev this project.
Keep up
EDIT: And, i dont now how can install a theme for TWRP..because text buttons not aligned
Click to expand...
Click to collapse
Heh, the updater-script bug is well-known to me, i'll try to fix it in the upcoming updates. The manager app issue happens is because you are running a Note 4 ROM from this forum and that rom changes the ro.product.device if not mistaken. If I can make this work, which i will do, i will have a talk with the ROM developers to not alter the ro.product.device for the app to work. To install a TWRP theme you have the instructions along with the download here. Just make sure to download for 720p.
Alexander_the_B0ss said:
Heh, the updater-script bug is well-known to me, i'll try to fix it in the upcoming updates. The manager app issue happens is because you are running a Note 4 ROM from this forum and that rom changes the ro.product.device if not mistaken. If I can make this work, which i will do, i will have a talk with the ROM developers to not alter the ro.product.device for the app to work. To install a TWRP theme you have the instructions along with the download here. Just make sure to download for 720p.
Click to expand...
Click to collapse
Thanks for your "talk with ROM Developers". Hope kexec-hardpatch is enabled (if I am right) soon and we will have boot menu working
@Alexander_the_B0ss
Any update? I devices is see like: m3 not i9305
il3gal said:
@Alexander_the_B0ss
Any update? I devices is see like: m3 not i9305
Click to expand...
Click to collapse
The actual codename for i9305 is m3 or m3xx, i9305 is the 'commercial name'. About any updates: for now i have a dead hdd, so at least for a couple of weeks no updates. Sorry. And also I am sick and need to go to hospital.
Alexander_the_B0ss said:
The actual codename for i9305 is m3 or m3xx, i9305 is the 'commercial name'. About any updates: for now i have a dead hdd, so at least for a couple of weeks no updates. Sorry. And also I am sick and need to go to hospital.
Click to expand...
Click to collapse
Get well brother.
Get well soon friend
any news ?????
hi, does this work on the older i9300 model (3g)?
{
"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"
}
This is a thread for the ZTE T815/Telstra Tempo T815. I hope other users who have this device might get some benefit and enjoyment out of this thread.
BACKUP!
Start here for a guide to extracting a ROM dump from your T815 and processing it to create a backup you can use to restore your phone if anything goes wrong for you
Custom Recovery and Root Method
I have ported PhilZ Touch Recovery V6 (6.59.0 - based on CWM 6.0.5.1) to the T815. Installation method and rooting instructions can be found here
Custom ROMs (list will be updated as new ROMs are posted)
[ROM] [PussyFap V3][KitKat] ZTE T815 - here
[ROM] [Pure LG G3][KitKat] ZTE T815 - here
[ROM] [Cherry ROM Lite v2.1][KitKat 4.4.2] ZTE T815 - here
[ROM][Amgoo OS][KitKat4.4.4] ZTE T815 - here
How install custom recovery and root ZTE T815
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
I have been able to port PhilZ Touch Recovery V6 (6.59.0 - based on CWM 6.0.5.1) to the ZTE T815. To flash this recovery to your device you will need the following:
- USB VCOM Driver - Installation tutorial and download of driver here (Don't worry that it says MTK6577, it works fine with MTK6572 based devices)
- Smart Phone Flash Tool - Download for all versions can be found here - scroll to the bottom of the list to find latest version
- Scatter file and custom recovery image - download here
- PC and USB cable
Method:
1. Follow the tutorial and install the USB VCOM driver.
2. Install SP Flash Tool - once installed, run as administrator.
3. On the "Download" tab page, click the box on the right hand side named "Scatter-loading". Browse to the location where you saved the downloaded "MT6572_Android_scatter.txt" file, select it and click "Open".
4. In the lower section of SP Flash Tool screen, tick the box next to RECOVERY. This is the ONLY box that is to be selected.
5. On the RECOVERY line, go across to the to the blank cell under the "Location" heading and click on it. Now browse to the location where you saved the downloaded "recovery.img", select it and click "Open". The line should now show the location of the file.
6. Turn off your phone and remove the battery.
7. On SP Flash Tool, click the "Download" button at the top of the page and THEN connect your phone to the PC via the USB cable (battery still out).
8. All going well, you should now see the download progress being displayed across the bottom of the screen. Once completed, you will see a big green tick displayed in the middle of the screen. Success! Your phone now has PhilZ Touch Recovery installed.
To access Recovery Mode, from power off hold down the volume up button and power button together for around 6 seconds (press and hold volume up first then press and hold power). You will now see the recovery main menu.
Root: (after you have your custom recovery installed)
1. Download supersu.zip (latest version) here - thanks to @Chainfire
2. Send zip file to your SD card.
3. Boot into recovery and install zip from SD card.
4. Reboot - your device is now rooted.
Important:
Make yourself a backup. (Note: the external SD card is /storage/sdcard1 - if you try to backup to sdcard0, you will run out of memory.)
To bring this PhilZ Touch Recovery to you, thanks and credit must be given to the following:
- Phil3759
- Koush for having created and maintaining cwm
- Cyanogenmod for making all this possible
- Tallustus from Team Skyfire for his great support over IRC: MAJOR CREDITS
- Dees_Troy from TWRP team for pigz source and many great ideas in their recovery + source for backups compatibility
- Chenglu for his unpacking tools and porting i9505: Huge credit
- kbc-developers for the base semi-touch code and much more
[email protected] for his great job / support
- sk8erwitskil for his recovery source, a great place to start learning
- shoe63 for his help from the start across many devices
- DooMLoRD for his work and help with Sony
- [NUT] for his ports to Sony
- wanam for compiling sensors-free kernels for N71xx/i317M, i9500 and i9505 to fix boot delay for custom kernels, exfat support and much more
- dougiebee for his work on fixing time on many Qualcom devices
- ausdim for all the support in developing kernels for i9505
- dr.ketan for his precious help in porting to the N7000 & N7100 (I don't own one) and all the support in threads
- Chainfire for his support (stock recovery flash) and all his work for the Android community
- 1966zippy for bringing it to the ZTE T815!
[ROM] [PussyFap V3][KitKat] ZTE T815
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I have had my first success at porting a custom ROM to the T815, so I present to you ***** Fap V3.
Requirements
BACKUP BEFORE DOING ANYTHING ELSE - If this ROM isn't for you then this is your fallback position.
You must be rooted.
You must have a custom recovery installed
You must have experience flashing but if not, feel free to ask questions before flashing.
Patience as the ROM takes a while to boot
To Install
Download zip file from link below and then send the file to your device's SD card. Boot into recovery, go to "Wipe and Format Options", use "Clean to Install a New ROM" and let finish then back to main menu. Choose "Install Zip" and select "choose zip from /storage/sdcard1 (second option from top). Navigate to the PussyFap_v3_T815.zip file and install. Go back to "Wipe and Format Options"and wipe Cache and wipe Dalvik/ART Cache. Go back to main menu and hit "Reboot System Now". Enjoy exploring this custom ROM.
Note: Google Play Store is an older version but it will update to the latest version once you have signed in and have an active internet connection.
Download ***** Fap V3 ROM for ZTE T815 here
Features:
Full Lollipop UI
Lollipop Framework
Tinted Status Bar
Nice settings
Smooth performance
Performance Control
Engineer Mode
Init.d Tweaks
Battery Icon Styles
Dynamic system bars
Progress bar animation
Known Bugs:
- GPS not working Appears it is working, just MT6572 GPS is really crap!
- shows 2 sim slots instead of 1
- I have not used this ROM to make calls so there may be issues that are radio/sim related. Let me know what you find and I will try to fix.
Screenshots:
Full Credits:
Team *****
Thanks for your helpful information
PetaX8 said:
Thanks for your helpful information
Click to expand...
Click to collapse
You're very welcome.
Sent from my GT-I9506 using XDA-Developers mobile app
[ROM] [Pure LG G3][KitKat] ZTE T815
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Another ROM for you to enjoy - Pure LG G3
Requirements
- BACKUP BEFORE DOING ANYTHING ELSE - If this ROM isn't for you then this is your fallback position.
- You must have a custom recovery installed
- You must have experience flashing but if not, feel free to ask questions before flashing.
- Patience as the ROM takes a while to boot
To Install
Download zip file from link below and then send the file to your device's SD card. Boot into PhilZ recovery, go to "Wipe and Format Options", use "Clean to Install a New ROM" and let finish then back to main menu. Choose "Install Zip" and select "choose zip from /storage/sdcard1 (second option from top). Navigate to the "Pure LG G3_T815.zip" file and install. Go back to main menu and hit "Reboot System Now".
Download Pure LG G3 ROM for ZTE T815 here
Features:
- 99% LG G3 UI
- LG G3 boot animation
- Smart Pause
- Palm Motion
Bugs:
- Let me know
Screenshots:
Credits:
- Muhammad Restu
- Team LG Developers
- needrom
- Smart Four Team
Thanks for updating me on this 1966zippy. Its worked perfectly for me
millsb0mb said:
Thanks for updating me on this 1966zippy. Its worked perfectly for me
Click to expand...
Click to collapse
Glad to hear. Hope you enjoy the ROMs.
1966zippy said:
Glad to hear. Hope you enjoy the ROMs.
Click to expand...
Click to collapse
Works significantly better thanks
zte t815 it says recovery mode i updated it from then it is happening
frank bird said:
zte t815 it says recovery mode i updated it from then it is happening
Click to expand...
Click to collapse
If you are in recovery mode with a purple background and a green android in the middle then you are in the recovery mode that we set out to achieve. Just touch "go back" on the screen until you are at the main menu and then select "reboot phone now" and you will boot to your stock OS.
If you are on the black recovery screen (stock recovery), it means that some part of the process did not work and you didn't get the custom recovery flashed correctly. You can navigate through the stock recovery menu by pressing volume down to select the line with the option you want and then confirm your selection with volume up (which I think goes against "normal" thinking and is a trap for making incorrect selections, so be careful, says he who has fallen for this same trap and blitzed his phone!).
You need to get back to the "reboot now" option and then try the process again (be sure you have the USB VCOM drivers installed properly.):good:
[ROM] [Cherry ROM Lite v2.1][KitKat 4.4.2] ZTE T815
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Here is another ROM for you to explore - Cherry ROM Lite v2.1
Requirements
- BACKUP BEFORE DOING ANYTHING ELSE - If this ROM isn't for you then this is your fallback position.
- You must have a custom recovery installed
- You must have experience flashing but if not, feel free to ask questions before flashing.
- Patience as the ROM takes a while to boot
To Install
Download zip file from link below and then send the file to your device's SD card. Boot into PhilZ recovery, go to "Wipe and Format Options", use "Clean to Install a New ROM" and let finish then back to main menu. Choose "Install Zip" and select "choose zip from /storage/sdcard1 (second option from top). Navigate to the "Cherry ROM Lite_v2.1_T815.zip" file and install. Go back to main menu and hit "Reboot System Now".
Download Cherry ROM Lite v2.1 for ZTE T815 here
Features:
- Amazing performance
- Audio enhancements
- Cyanogen file manager and browser
- Added GPS settings for better access to satellites
- SuperSU pre-installed
- Excellent RAM management
Bugs:
- Let me know
Screenshots:
Credits:
- Dertio Acos
- Unknown Porting Team
- Computer+Android
- 1966zippy for porting to T815
is there any new roms coming in? what about CyanogenMod? are you guys making a "pure" android ROM for T815? i didn't like the ***** fap rom as it doesn't work well with small screen, lg rom is perfect but slow, is the cherry rom near stock??
PS: great work keep up. if you could maybe remove the dual sim notification as i only have 1 sim slot, also maybe its a good idea to upload de-bloated stock rom for t815
Jesus Chen said:
is there any new roms coming in? what about CyanogenMod? are you guys making a "pure" android ROM for T815? i didn't like the ***** fap rom as it doesn't work well with small screen, lg rom is perfect but slow, is the cherry rom near stock??
PS: great work keep up. if you could maybe remove the dual sim notification as i only have 1 sim slot, also maybe its a good idea to upload de-bloated stock rom for t815
Click to expand...
Click to collapse
Thanks for your feedback. I do have plans to upload more ROMs as I port them and get most of the bugs squashed but, as I am on a massive learning curve regarding porting myself, it is taking a bit of time. I don't reckon I've done too bad so far for only a couple of weeks! I will leave the CyanogenMod ROM for a while, as it looks like it is one of the more complicated ROMs to port, but I will try to get it up here at some stage. I am working with a pure android ROM at the moment so hopefully that works out and I can upload it soon. The Cherry ROM is debloated and has some nice features but the only way to find out is to give it a whirl.
As for the dual sim thing, I am still trying to work out how to modify the ROM to only show the one sim (as I said, still got "L" plates on) and once I work out how to do this I will repost the corrected ROMs. I agree that a debloated stock ROM is a great idea so I will work on that when time permits.:highfive:
thanks
1966zippy said:
Thanks for your feedback. I do have plans to upload more ROMs as I port them and get most of the bugs squashed but, as I am on a massive learning curve regarding porting myself, it is taking a bit of time. I don't reckon I've done too bad so far for only a couple of weeks! I will leave the CyanogenMod ROM for a while, as it looks like it is one of the more complicated ROMs to port, but I will try to get it up here at some stage. I am working with a pure android ROM at the moment so hopefully that works out and I can upload it soon. The Cherry ROM is debloated and has some nice features but the only way to find out is to give it a whirl.
As for the dual sim thing, I am still trying to work out how to modify the ROM to only show the one sim (as I said, still got "L" plates on) and once I work out how to do this I will repost the corrected ROMs. I agree that a debloated stock ROM is a great idea so I will work on that when time permits.:highfive:
Click to expand...
Click to collapse
thanks for the lightning fast reply, ill be looking forward to pure stock android with support for single sim. keep up the good work and you da real MVP. perhaps check out alcatel pixi 3 xda http://forum.xda-developers.com/android/general/root-alcatel-one-touch-pixi-34-official-t3193624 as the 4 inch version have very similar spec with t815. (i have 4.5 inch with much fast/newer chipset,alias it doesn't have any custom rom) :good::good::good:
Jesus Chen said:
thanks for the lightning fast reply, ill be looking forward to pure stock android with support for single sim. keep up the good work and you da real MVP. perhaps check out alcatel pixi 3 xda http://forum.xda-developers.com/android/general/root-alcatel-one-touch-pixi-34-official-t3193624 as the 4 inch version have very similar spec with t815. (i have 4.5 inch with much fast/newer chipset,alias it doesn't have any custom rom) :good::good::good:
Click to expand...
Click to collapse
LOL!:laugh: Around 6 month ago I was looking for a cheap phone to mod and my final choice was between the Tempo T815 and Pixi 3(4), the Pixi winning out because it was $5 cheaper. It was the right choice as I found @kirito9's thread which was crammed full of info and ROMs. I learned a few things about working with the Mediatek MT6572 chipset and porting ROM's (thanks again to @kirito9 here, absolute legend) over there, all the while watching a small thread about the Tempo T815 where they had all stopped posting as no one could get root on the T815. I thought I could take the bits that I have worked out and apply them to this little supported device so here we are. I am no expert on all things MT6572 but I am working things out slowly so hang in there and I will put more ROMs and helpful info up here when I can.
[ROM] [Amgoo OS][KitKat 4.4.4] ZTE T815
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements
- BACKUP BEFORE DOING ANYTHING ELSE - If this ROM isn't for you then this is your fallback position.
- You must have a custom recovery installed
- You must have experience flashing but if not, feel free to ask questions before flashing.
- Patience as the ROM takes a while to boot
To Install
Download zip file from link below and then send the file to your device's SD card. Boot into PhilZ recovery, go to "Wipe and Format Options", use "Clean to Install a New ROM" and let finish then back to main menu. Choose "Install Zip" and select "choose zip from /storage/sdcard1 (second option from top). Navigate to the "Amgoo OS_T815.zip" file and install. Go back to main menu and hit "Reboot System Now".
Download Amgoo OS for ZTE T815 here
Features:
- Android Lollipop Inspired UI
- Deodexed
- Zipaligned
- Debloated
- Rooted (KingUser)
- Updated GAPPS (Google Chrome(Default Browser), Google App, Google Play Services, Hangouts(Default Messenger), Google Play Music(Default Music Player), Google Now Launcher(Default Launcher), Google Play Store)
- Modded System App (Lollipop Themed)
- Xposed Modules Integrated in Settings.apk
- Amgoo os Boot Logo
Bugs:
- Sound works OK but I can't get it as loud as I would like
- Anything else, let me know
Screenshots: (Apologies for poor screens but this ROM is worth trying for it's UFO live wallpaper alone!)
Credits:
- Nayeem Hossen For Porting This ROM
- Mou For making the boot logo
- 1966zippy for porting to T815
Full ROM Dump Backup & Read Back Method
This guide will show you how to make a full ROM dump of your ZTE T815 (Mediatek MT6572) device. It can be used to make a full backup at anytime but I strongly suggest that you follow this procedure prior to making any modifications to your device. That way you will always have a completely stock unmodified image to return to if things go bad or aren't what you expected. Don't say you haven't been warned!
Things you will need:
- ADB Drivers - here or here
- USB VCOM Driver - Installation tutorial and download of driver here (Don't worry that it says MTK6577, it works fine with MTK6572 based devices)
- MTK Droid Tools - here - scroll to the bottom of the list to find latest version
- Smart Phone Flash Tool - Download for all versions can be found here - scroll to the bottom of the list to find latest version
- Notepad++ - here
- A PC and USB Cable
Preparations:
- Install ADB Drivers system wide and follow tutorial to install USB VCOM Driver
- Install Notepad++
- Create a folder somewhere convenient (e.g. desktop) and give it a name related to phone/mods etc.
- Into this folder, install MTK Droid Tools and SP Flash Tool.
Process:
Make Scatter File
Run MTK Droid Tools as administrator. Once the program has started, connect your phone via the USB cable and you will see that your phone information loads up on the left side of the page. Below this you will see a button that says "Block Map". Press it. You will now see a screen displaying Block Info and at the bottom left a button "Create scatter file". Press this button and save the "MT6572_Android_scatter.txt" file to the folder that you made earlier. Don't close MTK Droid Tools, just minimise it at this stage and unplug your phone.
Read Back ROM From Phone
Run SP Flash Tool as administrator. By default it starts on the Download tab. You will see a button labelled "Scatter-loading" at the top right of the screen. Press this button and direct it to the "MT6572_Android_scatter.txt" that you just saved. Once loaded, change to the "readback" tab along the top and then click "Add". A line is added below and you need to click in the blank area under the heading "File". Browse to the location where you want to save your ROM dump (in that same folder again would be appropriate) make sure you retain the file name of "ROM_0" and press "Save".
There is now a dialogue box that pops up, "Readback block start address". The "Type" must remain as Hex. The "Start address" should also remain as it is - 0x0000000000000000. The "Length" address is determined by the address of the partition we wish to finish our ROM dump at. I would suggest that we use the address of the last partition in the phone. To find out this address we need to examine the scatter file. Open the scatter file with Notepad++ (this will keep the formatting in place). Easy way is to right click on the file and select "Edit with Notepad++" from drop down menu. Scroll to the bottom of the page and find the FAT partition information. The "linear_start_addr:" value here is where to end the ROM dump so carefully copy the address and paste into the "Readback block start address" dialogue in the "Length" field. (e.g. the linear start address of my FAT partition is 0x97140000 so this is the figure I enter into "Length").
Note: If you have already been using your phone before doing this backup method, you may wish to create a ROM dump that excludes your personal info. If so, you might choose not include the CACHE and USERDATA partitions in the backup so you would end the ROM dump at the linear start address of the CACHE partition (in my phone this is 0x36340000, for example).
Once the "Length" value is entered, press OK. Turn your phone off at this stage. Once it is fully powered down, click "Read Back" and then connect your powered off phone to the USB cable and all things going well you should see the progress bar at the bottom go blue and start moving. Once completed successfully you will see a green circle with a tick in it. Done! Disconnect your phone.
Process ROM For Use With SPFT
Turn your phone back on and when ready reconnect to MTK Droid Tools. Change to "root, backup, recovery" tab and press on the button labelled "To process file ROM_ from Flash Tool". Browse to your modding folder location and open "ROM_0". The processing will start and you will be prompted to make a CWM recovery automatically. Answer "No" and then "Cancel" when it asks to choose recovery. You will see the process in action and it will end with the message "Task is complete" at the end of the script. The folder containing this processed backup is located in yourmoddingfolder/Mtk_Droid_Tool_v2.5.3/backups. If you examine the contents of this processed ROM backup you will note that the output folder now also contains a scatter.txt file.
Restore process to follow - edit soon:good:
1966zippy said:
This guide will show you how to make a full ROM dump of your ZTE T815 (Mediatek MT6572) device. It can be used to make a full backup at anytime but I strongly suggest that you follow this procedure prior to making any modifications to your device. That way you will always have a completely stock unmodified image to return to if things go bad or aren't what you expected. Don't say you haven't been warned!
Click to expand...
Click to collapse
Can I borrow this post?
kirito9 said:
Can I borrow this port?
Click to expand...
Click to collapse
Assuming port was supposed to be post, you absolutely can borrow it, mate. [emoji106]
Sent from my GT-I9506 using XDA-Developers mobile app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.InstallationManual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install + one optional (deprecated) :
MultiROM (multirom-YYYYMMDD-v33x-taoshan.zip) - download the ZIP file from second post and flash it in recovery.
Modified Recovery (multirom-YYYYMMDD-recovery-taoshan.zip) - download the ZIP file from second post and use a recovery to flash it into the FOTA partition (see TWRP 3 thread for more informations).
DEPRECATED: Patched kernel - You can use those kernels on most Marshmallow and Lollipop based primary ROMs to add kexec boot support.
Be aware that those patchers will be updated when possible after kernel sources updates
Kexec support no longer required thanks to the no-kexec workaround by nkk71.
For convenience reasons, I enabled the workaround by default if kexec is not found.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Recommended values are :
Cache : Keep default value
Data : Minimum 4000
System : 1000 is enough for most installs
Updating/changing ROMs1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
OPTIONAL: Reflash the kernel patcher to add kexec support
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menusMain menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source codeMultiROM - https://github.com/STRYDER-007/multirom_xperia (branch multirom-7.1)
Modified TWRP - https://github.com/nkk71/android_bootable_recovery/ (branch android-7.1-mrom)
Device Tree - https://github.com/STRYDER-007/multirom_device_sony_taoshan (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/STRYDER-007/android_kernel_sony_msm8930 (branch multirom)
MultiROM available for Taoshan also thanks to :- Tasssadar
- The XperiaMultiROM team
- The MultiROM HTC team
- @Olivier and @Adrian DC for lot of precious help and guidance in fixing many things
- @nkk71 for no-kexec workaround
- @Agent_fabulous for testing
- My Xperia L for surviving this!
XDA:DevDB Information
MultiROM for Xperia L, Tool/Utility for the Sony Xperia L
Contributors
STRYDER~007
Source Code: http://forum.xda-developers.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011
Version Information
Status: Stable
Created 2016-06-13
Last Updated 2016-09-24
Downloads
1. Main downloads
MultiROM: multirom-2017MMDD-v33x-taoshan.zip
Modified recovery (based on TWRP 3): multirom-2017MMDD-recovery-fota-taoshan.zip
OPTIONAL: Kernel w/ kexec-hardboot patch (msm8930 Marshmallow based):
multirom_kernel-2016MMDD-taoshan.zip
If used, kernel with kexec-hardboot patched needs to be only in your primary ROM!
* No longer required thanks to the no-kexec workaround.
2. Third-party kernels with kexec-hardboot patch
* None, No longer needed due to no-kexec implementation.
3. MultiROM Uninstaller
MultiROM uninstaller: multirom_uninstaller.zip
* Flash uninstaller zip from recovery to remove MultiROM completely. This will also remove all your secondary ROMs.How to install for the first time
Flash the 2 MultiROM zips as explained
Reboot to the FOTA Recovery (Volume +)
In MultiROM TWRP, Add a ROM, set everything properly
Wait for the ROM to be installed (can take a while)
In MultiROM screen, choose the ROM location
For the concerned ROM, "Flash zip" for wished zips (GApps, SuperSU, Addons...)
OPTIONAL: Read about the no-kexec workaround by nkk71
Reboot the phone and Enjoy MultiROM!
Changelogs
Code:
=========================================
MultiROM v33x - TWRP 3.1.1 - 02/10/2017
=========================================
* Fixed incorrect mounting of partitions in TWRP
* Removed unused and deprecated flags in TWRP
* Fixed MultiROM TWRP versioning
=========================================
MultiROM v33x - TWRP 3.1.1 - 24/09/2017
=========================================
* [B]Fixed touchscreen issue in MultiROM UI[/B]
* cyttsp3: Update multi-touch protocol for display driver
* defconfig: Compress kernel with XZ (Smaller TWRP Size)
* MultiROM UI dimensions completely fixed
* Access to MultiROM color themes and Shutdown
* Include all recent improvements from TWRP 3.1.1
* Updated to no-kexec workaround v4.1 by nkk71
* Autoboot accessible for external / MicroSD
* Improved versioning with header showing build date
* Built in a clean new tree of Android 7.1.2 (replaces 6.0)
* Multiple fixes to support 7.1 changes
* Fix the 7.1 busybox cpio corruption, needed for MultiROM
=========================================
MultiROM v33x - TWRP 3.1.0 - 15/06/2016
=========================================
* Fixed MultiROM logo in UI
* Some Minor changes in the UI
=========================================
MultiROM v33x - TWRP 3.0.2 - 13/06/2016
=========================================
* Initial public release
FAQ and other notes
FAQ and other notesAbout security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive./external SD card. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside?
Yes.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
The installation fails with "trampoline not found -1"
Often the issue appears because the ROM zip has a nested zip for rooting methods. Best solution is to remove the root zip from the ROM and flash it separately later.
Something wrong happened, I lost something or it's really laggy
You have been warned about making backups & the fact this is more experimental than stable.
You alone will be responsible for loosing data or having an usable ROM when you really needed it.
Everyone in this thread will try to help you, but we can't do backups of your data ourselves.
Thanks for your understanding, remember to read the previous comments and please try to help each other.Current local manifest of the MultiROM build
Code:
<!-- https://github.com/STRYDER-007/multirom_device_sony_taoshan -->
Awesome work bro,thanks!!!
You are the best
Honestly, I never imagined that I'll be able to see multiRom on Xperia L
Thanks Dev. :laugh:
Awesome dev!
Will test it as soon as possible!
Thanks!
Awesome! Will test it for sure
WTF (What The Fantastic)
You're the best I'll try it ASAP
Just wanna make things clear
1. Can I install it without reflashing the current ROM?
2. Installing Rom to external SD Card Won't format and delete all the data?
So it doesn't mess with memory partition??
That means there's no hardbrick just (maybe) softbrick.
Again thank you very much. For your hard work
Mouaz Kaadan said:
Just wanna make things clear
1. Can I install it without reflashing the current ROM?
2. Installing Rom to external SD Card Won't format and delete all the data?
Click to expand...
Click to collapse
1. Yes
2. Yes. You can keep your data along with ROM installation on ext sd.
n78 shadow said:
So it doesn't mess with memory partition??
That means there's no hardbrick just (maybe) softbrick.
Again thank you very much. For your hard work
Click to expand...
Click to collapse
No chances of bricking at all if you follow instruction and flash it correctly.
Wow. Extremely awesome, thanks for making this for Xperia L!
Just two questions: Does this work by "unpacking" the rom on external memory and booting as if it was internal? Also, how do we get Ubuntu (or any other Linux distro) to run on our device? (are there flashable zips for that?)
Sent from my taoshan using XDA Labs
Aenadon said:
Wow. Extremely awesome, thanks for making this for Xperia L!
Just two questions: Does this work by "unpacking" the rom on external memory and booting as if it was internal? Also, how do we get Ubuntu (or any other Linux distro) to run on our device? (are there flashable zips for that?)
Sent from my taoshan using XDA Labs
Click to expand...
Click to collapse
1. Yep.
2. There is no Ubuntu OS ported for Xperia L.
Thanks for this awesome Multirom. I have question. Can i install both stock rom and custom rom as a dual boot.?
kumardeepu said:
Thanks for this awesome Multirom. I have question. Can i install both stock rom and custom rom as a dual boot.?
Click to expand...
Click to collapse
Please go through entire thread. Everything is written there.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive./external SD card. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside?
Yes.
Click to expand...
Click to collapse
STRYDER~007 said:
Please go through entire thread. Everything is written there.
Click to expand...
Click to collapse
First Stockrom through flashtool>then multirom zip>modified recovery> custom rom am i right?
kumardeepu said:
First Stockrom through flashtool>then multirom zip>modified recovery> custom rom am i right?
Click to expand...
Click to collapse
Yes.
Well actually in detail, First stock rom via flashtool->Root->Install SuperSU->Install Recovery via Recovery Installer app->Flash MultiROM Recovery zip->Reboot to MultiROM recovery->Flash MultiROM zip->Add Custom ROM!
MultiROM Updated
MultiROM updated with minor UI changes. Check OP.
Changelogs-
Code:
** 15-06-2016
- Fixed MultiROM logo in UI
- Some Minor changes in the UI
It fails when i try to flash the multirom zip
Why??
Sorry for my bad English
ShadowA9 said:
It fails when i try to flash the multirom zip
Why??
Sorry for my bad English
Click to expand...
Click to collapse
Flash MultiROM recovery zip first then boot into new recovery and flash multirom zip.
{
"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"
}
This is a Official Build of madOS ( based on AOSP Oreo ) for Wiko Fever (2gb ram and 3gb ram) with MTK 6753 SoC and its clones:
Micromax Canvas 5 E481
Blu Life One X
Myphone 36
Qmobilez10
madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors
Lights;
Both storages & MTP
HW de/encoding
Camera (photos and video)
GPS & aGPS
Audio
madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)
Not working:
XDA:DevDB Information
madOS_O_FEVER, ROM for all devices (see above for details)
Contributors
DerTeufel1980, fire855, superdragonpt
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: unlocked bootloader, twrp
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2018-03-19
Created 2018-03-13
Last Updated 2018-03-22
First time Install Instructions
0) Preparation
0.1) Backup your important data to PC
0.2) Ensure you are running Wiko Fever Android 6 already (also/especially when your device is not wiko fever, but a clone). If you are not, please update to it, before continuing here (replace the preloader from the wiko rom with your stock one, then use 'firmware upgrade' mode in sp flashtool. NEVER use 'format all + download')
Extra steps, if you are on blu life one x:
https://forum.xda-developers.com/showpost.php?p=76003104&postcount=81
0.3) Download “twrp_wiko_fever_oreo.img“: [url]http://www.mediafire.com/file/e96x8ltlyka392e/twrp_wiko_fever_oreo.img[/URL]
0.4) Download “madOS_8.1.0_fever_2018xxyy.zip“ [url]https://www.facebook.com/MediatekAndroidDevelopers/[/URL]
0.5) Optional, Download “Google Apps (aka Gapps)“: [url]http://opengapps.org/[/URL]. Choose: “ARM64“, “Android 8.1“, “nano“ or “pico“ package
1) Unlock bootloader (if not done already):
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking” and “USB debugging” (if not enabled already), and choose to alollow usb debugging in the popping up window.
1.2) Boot the device in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
2) Flash the recovery and boot to it. (choose option a) if you don't have another TWRP already installed, else choose b))
2.1a) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader").
Then execute command “fastboot flash boot twrp_wiko_fever_oreo.img”;
and then “fastboot reboot” (this is a trick to directly bring you to the newly flashed recovery. You can't boot up your current/stock rom at this point anymore).
2.1b) Boot to your current TWRP. Choose install --> image, and select “twrp_wiko_fever_oreo.img“. Then choose “recovery“ as the target. After few seconds, and succesful installation, hit “back“ several times, then go to “reboot --> recovery“
3) Install
3.0) Optional, but recommended: Go to "Wipe --> Advanced Wipe", click "Cache" and then "Repair or Change File system". Then select "Change File system" and choose "F2FS". Swipe to confirm.
Hit "back" three times (you can again choose a partition to change now). Choose "Data" and do as above.
Hit "back" several times, to get back to the main menu. Choose "Reboot --> Recovery".
3.1) While already in recovery (TWRP), connect your phone to pc, and copy “madOS_8.1.0_fever_2018xxyy.zip“ and the Google Apps to your phone.
3.2) Go to "Wipe", and directly slide the slider to the right.
3.3) Get back to main menu with the "back" button
3.4) Go to "Install" and hit “madOS_8.1.0_fever_2018xxyy.zip“, then uncheck all boxes and hit "Add more zips", now choose the Google Apps.
Confirm installation by swiping the slider to the right.
3.5) Reboot System
Click to expand...
Click to collapse
Follow up Install Instructions
Download rom and gapps
boot to recovery
flash rom and gapps
optional: flash superSu/Magisk
reboot system
General F.A.Q.
Q: What the hell is madOS ?
A: madOS, (M.A.D. Team OS), is a ROM based on pure A.O.S.P. with extended capabilities and customizations made by or merge/adapted by M.A.D. Team.
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP 3.2.1-0 recovery for OREO 8.1.0
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file
2: You can simply flash it from the existing twrp recovery: Install> Install image> Select Oreo TWRP> Select "Recovery" as partition to flash.
Reboot to recovery to use new one
Q: Do i need to make full wipes?
A: YES, dont come crying at me, if you didn't .... ;p
Q: What is "full wipes" ?
A: To Wipe : Cache; System; DATA ...
Q: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Update: On Oreo 8.1.0:
- We have extended Theme support even further ( madLauncher, messaging, etc)
- As well as many fixes
Q: Some translations are missing for my language, can I help?
A: Sure you can, please check our translations repo available here , you can either do a pull request, or if you don't know how to work with git, sent us the XML. Strings for your language ( Check Readme on repo).
Q: I want to report a bug(s) do you have an issue tracker?
A: Yeah... madOS issue tracker
Q: What's working ?
A: Check first Post for current status
Q: App "x" doesn't work, why?
A: Probably not compatible with OREO yet, feedback is welcome
Q: Is the rom rooted?
A: NO, But you can easily root with :
1: Magisk ( v14 onwards.)
2: Super SU ( v2.82 onwards)
IF there are problems in rooting, you need to report it to the root-threads...There's nothing we can do
Q: Should i root together with rom ?
A: Not advised.. mainly the Magisk that gives some weird issues...
Flash ROM and GAPPS (if you use gapps), after first boot get back to recovery and flash your desire rooting method
Q: Does xposed work?
A: Is there Xposed for O? ... then no ;p
Q: How is battery life with Oreo?
A: Pretty awesome
Q: Does this build support Vulcan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: when will (feature/issue here) be fixed?
A: NO ETA , please
Porting F.A.Q.
No porting support, no port questions allowed on this thread, and porting PMs will be auto-deleted, porting replies will be reported as well
G.APPS F.A.Q.
Q:What GAPPS package should I use?
A: openGapps arm64 nano/pico
Q: How to properly install GAPPS?
A:Flash Rom + Flash Gapps at once
CREDITS and Thanks
madOS Team
Our translators, credits list here
A.O.S.P.
Pure Nexus
AOSPA
DU (Dirty Unicorns)
Omni
HELP supporting madOS
We do this on our free time, however we do have costs on maintaining this :/
Any donation is highly appreciated
You can donate by using
this link
If the above doesn't work in your country, then you can directly donate by using this e-mail adress: [email protected]
About madOS Proprietary Apps
You are NOT allowed by any means, to use our madOS apps on any other build, your rom
This is exclusively for OFFICIAL madOS ROM releases
@To Moderators: Feel free to clean the thread, whenever users start spamming, severe OT, or questioning about porting...
Changelog 19th March 2018:
fixed offline charging
fixed proximity and light sensor
fixed applying smartwake settings after reboot
Facebook release post: https://www.facebook.com/notes/mad/rom-810-official-mados-wiko-fever-mt6753/1640799096003857/
for whatever reason, devDB is not working (very well) at the moment...causing this thread to be shown up, hours after i created it....now it's finally here and updated...and can be used
Thank u so much sir...we owe you?
superdragonpt said:
Android Oreo released
https://forum.xda-developers.com/android/development/rom-official-mados-wiko-fever-clones-t3762804
Click to expand...
Click to collapse
superdragonpt said:
The ROM was made using an Wiko device in the bring up
I know very well this TINNO devices, that are rebranded to many OEMs
In case of baseband (ie: BLU,Qmobile, MMX, you should use your stock baseband modem and place it under vendor/etc)
Cheers
PS: can you, that have other clones ( non-wiko) send us your working baseband?
(This way, we could perhaps just made an flashable zip for baseband or so)
Click to expand...
Click to collapse
Here is firmware folder(baseband) from Life One X with MM update.
Opened an issue about some sensors
https://bitbucket.org/maadteam/mado.../103/some-sensors-light-proximity-not-working
mrmazak said:
Here is firmware folder(baseband) from Life One X with MM update.
Click to expand...
Click to collapse
FERRARI81 said:
Opened an issue about some sensors
https://bitbucket.org/maadteam/mado.../103/some-sensors-light-proximity-not-working
Click to expand...
Click to collapse
Great
This .zip is pushing to system/etc, so this .zip won't work here on Oreo, where everything is moved to vendor/etc
For the time being for the blu, you can either updated the updater-script to push to "vendor" instead of "system" or root it, and move your baseband manually to vendor/etc
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
superdragonpt said:
Great
This .zip is pushing to system/etc, so this .zip won't work here on Oreo, where everything is moved to vendor/etc
For the time being for the blu, you can either updated the updater-script to push to "vendor" instead of "system" or root it, and move your baseband manually to vendor/etc
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
Click to expand...
Click to collapse
So the sensor.lib from Blu?
I will pull it and share.
superdragonpt said:
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
Click to expand...
Click to collapse
Ehm...I have not blue, I have original Wiko Fever
And...I'm noob ...in wich way I could check what's the sensor?
FERRARI81 said:
Ehm...I have not blue, I have original Wiko Fever
And...I'm noob ...in wich way I could check what's the sensor?
Click to expand...
Click to collapse
just because adaptive brightness is not working , does not mean it is the sensor.
If sensor was not working , there is another test (check) you can do.
make a call, then put phone to head and see if screen goes off.
I had before when light sensor was not set correctly, when making a call the screen went black as soon as start a call, then could not get screen back on till 30 seconds after other end hung up the call.
I am away from my LOX now and for few days , so cant give direct test of light sensor.
attached just in case is usefull here are sensor libs from BLU-LOX. They are in /system/lib/hw and /system/lib64/hw.
I believe on oreo they go into /vendor/
Can we flash it over stock Lollipop ROM of Micromax Canvas 5 ??
I have a question that Can I flash it over the stock Lollipop ROM ?? existing kernel is 3.10.65.
Thanks
mrmazak said:
just because adaptive brightness is not working , does not mean it is the sensor.
If sensor was not working , there is another test (check) you can do.
make a call, then put phone to head and see if screen goes off.
I had before when light sensor was not set correctly, when making a call the screen went black as soon as start a call, then could not get screen back on till 30 seconds after other end hung up the call.
Click to expand...
Click to collapse
It doesn't work in call too : the screen is always on.
QUIZILLA said:
I have a question that Can I flash it over the stock Lollipop ROM ?? existing kernel is 3.10.65.
Thanks
Click to expand...
Click to collapse
Please remove the quote of the whole FAQ. This is totally useless to ask your question...
You need to flash wiko mm rom first
FERRARI81 said:
It doesn't work in call too : the screen is always on.
Click to expand...
Click to collapse
I'll check it today
Hello, I write from Padova, Italy,
I have the WIKO FEVER 3GB,I have the problem that after upgrading to MM (Android 6.0), device not connects to PC and no charge. The device is recognized ONLY if it turns off.
Can I do this update procedure with this problem?
I can not connect to the PC because device is not recognized. Can you help me? Can I root through an app installed by the playstore without using pc? Thank you so much for the answers.
Riccardo
ianto:
Rikadoo said:
Hello, I write from Padova, Italy,
I have the WIKO FEVER 3GB,I have the problem that after upgrading to MM (Android 6.0), device not connects to PC and no charge. The device is recognized ONLY if it turns off.
Can I do this update procedure with this problem?
I can not connect to the PC because device is not recognized. Can you help me? Can I root through an app installed by the playstore without using pc? Thank you so much for the answers.
Riccardo
ianto:
Click to expand...
Click to collapse
Why root? To update to oreo, you don't need root... But you still need to copy the new rom to your phone, as well as unlock the bootloader and install the twrp recovery. This needs to be done in fastboot mode by pc. I'd suggest to just try it
Unfortunately I am not very experienced, but I am very interested in solving my problem. I want to install this ROM, but without having to connect the device to the PC.
If I copy the ROM on the SD card. Can I then install?
I am in process of installing new oreo twrp and MADOS.
During install of TWRP, I loose adb authorization. (adb session is "unathorized")
in "prop.default" it has
Code:
ro.secure=1
security.perf_harden=1
ro.adb.secure=1
ro.allow.mock.location=0
ro.debuggable=0
is this intentional?
additional question,
Adb authorize connection window comes up multiple times even after putting check mark on remember this choice.
I think the adb auth problem is my pc, my other phone just started to do this too.
edit:
I have tried couple times to use blu firmware inside vendor folder. But not able to get baseband to be known.
tried just adding blu files ontop of original rom files.
tried removing rom files and adding blu files
tried removing whole folder then adding blu folder
each time I get unknown baseband.
I checked permission and ownership each way I tried and I set it to rw:r:r and root:shell just like original rom version, but not working for me.
One and more questions,....
1. Our bootloader is blocked or already unlocked?
2. If is locked, to unlock the bootloader of our device wiko fever which app I have to install?
3 if isn't locked, how I install a custom recovery like twrp manager?
4 how I boot the custom recovery twrp manager? Maybe if I switch off the device and reboot it, starts automatically the custom recovery?
5 at the end, from twrp can I flash the ROM Oreo?
AHH , last question, can I flash this ROM from my phone with Android MM?
mrmazak said:
I am in process of installing new oreo twrp and MADOS.
During install of TWRP, I loose adb authorization. (adb session is "unathorized")
in "prop.default" it has
is this intentional?
additional question,
Adb authorize connection window comes up multiple times even after putting check mark on remember this choice.
I think the adb auth problem is my pc, my other phone just started to do this too.
edit:
I have tried couple times to use blu firmware inside vendor folder. But not able to get baseband to be known.
tried just adding blu files ontop of original rom files.
tried removing rom files and adding blu files
tried removing whole folder then adding blu folder
each time I get unknown baseband.
I checked permission and ownership each way I tried and I set it to rw:r:r and root:shell just like original rom version, but not working for me.
Click to expand...
Click to collapse
Someone already uploaded vendor files for his model... Was it you? If not, please upload it for us