Related
{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
[SIZE="2"]* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
[/SIZE]
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Working:
Boots
RIL (Calls, SMS, Data, 2G/3G Switch)
MSIM
Wi-Fi
Bluetooth
GPS
Camera ( Videos And Photos )
Video Playback
Enforcing SELinux
Not Working:
You say!
Read post 2 before reporting bugs.
Install instructions:
Reboot into recovery (TWRP recommended).
Wipe Data, System and Cache if it's a fresh install.
No wipes required if you're updating from a previous version of CM 13.0 (Wipe Cache and Dalvik Cache recommended).
Flash ROM + Gapps.
Reboot.
Download links:
ROM: https://goo.gl/3XdMnF (IMPORTANT: READ THIS)
Gapps: http://opengapps.org
Kernel source: https://github.com/TheStrix/android_kernel_cyanogen_msm8916
Device Tree:
msm8916-common: https://github.com/TheStrix/android_device_cyanogen_msm8916-common/tree/cm-13.0
lettuce: https://github.com/TheStrix/android_device_yu_lettuce/tree/cm-13.0
XDA:DevDB Information
CyanogenMod 13 for YU Yuphoria, ROM for the YU Yuphoria
Contributors
TheStrix
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 13.0
Created 2015-12-18
Last Updated 2016-01-23
Bug reports:
CyanogenMod 13 is in development and has several small bugs and missing translations. Complaints/demands/bug reports without logs will be ignored.
Explain how to reproduce the bug and attach logcat and dmesg (if you had a random reboot, also attach last_kmsg). If you don't know how to get those, you can use this app. Please, do not report bugs if you use any kind of mods (like xposed) or third party kernel.
Frequently Asked Questions:
Q) Will I get facebook/messenger app fc?
A) You shouldn't! Adreno blobs are now updated and now no dirty hacks required to boot up which in turn broke something.
Q) Where are Developer options?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I enable root access?
A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.
Q) I don't like superuser icon in statusbar, can I install SuperSU?
A) Ok yes, but read this. First enable root access from Developer options. Then flash SuperSU zip. Now open SuperSU app. It will say, 'SuperSU binary not installed'. So use TWRP/CWM method to install binaries. (This worked for me)
Q) How can I set 3G only network mode?
A)Method 1: Open Settings, Cellular Networks, now you can select LTE/3G/2G modes in 'Preferred network type' menu.
Method 2: Open dialer, dial *#*#4636#*#* , open first option "Phone Information", there you can set your preferred network mode.
Q) How do I update Gapps? (Also useful if you have Gapps related problems).
A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + Gapps. (Yep, at a time) Reboot.
Reserved
Finally!! Great work
Solved : Gapps not able to flash
which gapps works best for this rom?arm,arm64 or x86.Im unable to flash open gapps.Please help.
Solved : Flashed ARM64-6.0-pico.Now it works great.Thanks developer for the wonderful ROM.Keep up your good work
Great Work!
Uc browser not working......
jayent said:
Uc browser not working......
Click to expand...
Click to collapse
Download UC Browser from here
please help
Hey I am facing problem while flashing thus ROM. Please help please
sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
wipe/factory reset
Yash98 said:
wipe/factory reset
Click to expand...
Click to collapse
"GPS" not working.. phone getting restarted
---------- Post added at 04:59 AM ---------- Previous post was at 04:58 AM ----------
TheStrix said:
Bug reports:
CyanogenMod 13 is in development and has several small bugs and missing translations. Complaints/demands/bug reports without logs will be ignored.
Explain how to reproduce the bug and attach logcat and dmesg (if you had a random reboot, also attach last_kmsg). If you don't know how to get those, you can use this app. Please, do not report bugs if you use any kind of mods (like xposed) or third party kernel.
Frequently Asked Questions:
Q) Will I get facebook/messenger app fc?
A) You shouldn't! Adreno blobs are now updated and now no dirty hacks required to boot up which in turn broke something.
Q) Where are Developer options?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I enable root access?
A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.
Q) I don't like superuser icon in statusbar, can I install SuperSU?
A) Ok yes, but read this. First enable root access from Developer options. Then flash SuperSU zip. Now open SuperSU app. It will say, 'SuperSU binary not installed'. So use TWRP/CWM method to install binaries. (This worked for me)
Q) How can I set 3G only network mode?
A)Method 1: Open Settings, Cellular Networks, now you can select LTE/3G/2G modes in 'Preferred network type' menu.
Method 2: Open dialer, dial *#*#4636#*#* , open first option "Phone Information", there you can set your preferred network mode.
Q) How do I update Gapps? (Also useful if you have Gapps related problems).
A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + Gapps. (Yep, at a time) Reboot.
Click to expand...
Click to collapse
"GPS" not working.. phone getting restarted
Update!
CyanogenMod 13.0 R2 Update:
Download: http://goo.gl/h7CkVJ
Changelog:
AOSP 6.0.1_r10 tag.
January 2016 security patches.
Fix offline charging issue (Screen didn't go completely off while offline charging earlier).
Fix Google+ app installation bug present in previous build.
Increased in-call volume speaker gain (reported by some users).
Updated build fingerprint from YU's latest COS release.
Some Wi-Fi updates.
Fix for external SD Card in CM file manager.
Replaced Toybox with Busybox (This may cause some root apps to crash, but CM now uses Toybox!).
Latest CyanogenMod sources with much new patches..
CyanogenMod 13.0 Jan 23rd update:
Download: https://www.androidfilehost.com/?fid=24385658843824514
Just don't hurry up. Read the whole post for once!
Changelog:
Support for F2FS for /data and /cache
Update audio configs to cope up with CyanogenMod's latest changes in audio HAL.
Switch to qcom libhealthd.msm standard library for offline charging (Also it shows battery % now while offline charge)
Switch to Snap camera
Enable USB MIDI support
RIL and connectivity updates
Update new regenerated blobs from crackling
CyanogenMod updates. (CM API v5, new wallpaper, etc. find out own ) [Many changes are made in CyanogenMod repo everyday, so of course can't list all]
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Damn, that was just copy paste from wikipedia and I just didn't get it! So what is F2FS in our language?
It a better file system than ext4 in terms of performance.
Useful Link: http://www.xda-developers.com/f2fs-put-to-the-test-against-ext4/
To get a better idea, XDA forum have a dedicated thread highlighting F2FS features and a very detailed comparison between EXT4 (file system we use by default) and F2FS!
Have a look here: http://forum.xda-developers.com/showthread.php?t=2697069
So, I liked F2FS and wanna try it! But, how do I?
First of all, backup your internal SD Card as it will be wiped if you are switching to F2FS.
So, to start with, first you'll need a new recovery. I compiled modified TWRP recovery with F2FS support and some other cool features like pressing power button will now switch device display off, also wiping the partitions should not take much time now as it did earlier! (EXT4 users can use the same recovery. I just made it for my convenience)
1. Download TWRP: https://www.androidfilehost.com/?fid=24385658843824749
2. In recovery, go to 'wipe' -> 'Advanced Wipe'
3. Check only 'Data' and tap on 'Repair or Change File System' -> 'Change File System'
4. Here select 'F2FS' and Swipe to Change
5. Repeat step 3 and 4 for 'Cache' by checking only 'Cache' in Wipe menu.
6. Reboot! Enjoy!
I want to get back to EXT4 again from F2FS, how should I?
Again, while you are changing your file system, the partition gets wiped. So do backup your data of Internal SD Card and proceed!
1. In recovery, go to 'wipe' -> 'Advanced Wipe'
2. Check only 'Data' and tap on 'Repair or Change File System' -> 'Change File System'
3. Here select 'EXT4' and Swipe to Change
4. Repeat step 2 and 3 for 'Cache' by checking only 'Cache' in Wipe menu.
5. Reboot
PS: Only support for F2FS is added on /data and /cache. It still uses EXT4 by default and is just same as it was in previous builds!
first of all
its an amazing rom
but would absolutely love it if i know how to activate power save mode
and a small request " can you add the theme engine from cyanogen os??????"
i really hate the cm theme engine
hello, why cm13 isn't official because there aren't no bugs?
aminvishwas said:
which gapps works best for this rom?arm,arm64 or x86.Im unable to flash open gapps.Please help.
Solved : Flashed ARM64-6.0-pico.Now it works great.Thanks developer for the wonderful ROM.Keep up your good work
Click to expand...
Click to collapse
Can't we use the gap 6.0 Full
problm in 5.0.2 ?
there is problm of wake up while charging that it may not happen while m charging phone sir can u pls tell me to fix this problm it will be appreciated could you help me pls....??
sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
bro before flashing the zip file.
do following in TWRP
wipe davlik
wipe data
wipe cache
wipe system
and install the zip file the above error will not appear
reserved
sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
wipe data and system and install and that will fix the error and one more thing can you make a system backup with twrp and give me i need this rom but my devices is irulu v3 and i try cm12 but its old now.
{
"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 Oukitel K6000 Plus with MTK 6750 SoC
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.
*/
Installation Instructions:
Download ROM from M.A.D. Facebook
OR from xda DevDB
Download OpenGapps nano or pico from OpenGapps
(choose Arm64 and Android 8.0 )
Backup
Unlock Bootloader Bootloader unlock
Flash new mandatory new Oreo TWRP (available on downloads)
Boot to the new TWRP recovery
full Wipes (dont come crying if you didn't .. ;p )
Install rom (optionally following by GAPPS if you use them)
Optional: go to: wipe --> Advanced Wipe, tick 'cache' and klick 'repair or change File System' --> change File System --> F2FS --> swipe to the right (hit back several times, and proceed the same way with 'data').
Reboot System
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors (including fingerprint)
Lights; HW Keys
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:
nothing known
XDA:DevDB Information
madOS_O_K6KP, ROM for all devices (see above for details)
Contributors
DerTeufel1980, superdragonpt, fire855
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: bootloader unlocked, twrp
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2017-11-19
Created 2017-11-19
Last Updated 2017-12-31
Reserved
How-To unlock Bootloader and install TWRP
ATTENTION: This is voiding your warrenty
Install minimal adb and fastboo to your PCt: Minimal ADB and Fastboot
On the smartphone: Go to Settings --> About Phone and hit 'build Number' seven times, to enable 'Developer Options'
Go to Settings --> Developer Options, and allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
Start 'Minimal adb and Fastboot' at Pc. In the command window, type: "adb reboot bootloader" and press Enter (this is restarting the smartphone into the bootloader)
WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty! In the command window, type "fastboot oem unlock" and press Enter (to unlock the bootloader). You probably need to press some button of the phone to confirm (check the display for this)
Download the Twrp image: Oukitel K6000 Plus TWRP, and copy the recovery.img file to the installation folder of 'minimal adb and fastboot'
In the command window, type "fastboot flash recovery recovery.img" and press Enter. After successful flash, enter "fastboot reboot" in the command window, press 'Enter'. Then immediately press and hold 'volume up key' on the smartphone (Until a small menu appears)
3 options appear on the smartphone: Recovery, Fastboot, Normal. You can navigate with 'volume up key' and confirm your selection with 'volume down'. Navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
F.A.Q
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: Where to report bugs ?
A: madOS issue tracker
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP recovery
--> Download Section
Q: How do i flash a new recovery or new boot from previous TWRP?
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 RECOVERY or BOOT image file > Select "Recovery" or "Boot" as partition to flash.
Reboot
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, where f2fs might be faster
Q: is the Data connection issue of going to / from 4G present?
A: nope data switchs pretty fast on our new RIL
2G>3G>4G | 4G>3G>2G pretty fast
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
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: 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 Magisk v14 onwards.
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/mini
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...
Changelogs
[Stable] Build [8.0.0] 20171119
First Release
Patch Level: 8.0.0 [OPR1] November 6, 2017
Kernel: 3.18.80( Oreo branch)
one more
reserved
DerTeufel1980 said:
Changelogs
[Stable] Build [8.0.0] 20171119
First Release
Patch Level: 8.0.0 [OPR1] November 6, 2017
Kernel: 3.18.80( Oreo branch)
Click to expand...
Click to collapse
Hi guys,
Thanks for your incredible work for the K6000 Plus!
I have a Doogee Y6. It uses the same kernel as K6000 plus. So, I've been trying to compile the k6000 plus kernel in order to work on my phone (I have made the necessary adjustments regarding my device's specific drivers such as LCM, Touchscreen, fingerprint etc.)
But I am running into errors. The compiler complains about not finding some files like: mt_gpufreq.h, cmdq_engine.h etc.
Can you assist me with this?
Thank you.
Great ROM! Many thanks for your work M.A.D team
I found one bug in camera. When you turn on HDR mode and after taking picture camera force close with toast: "Media server died, closing camera." but photo still save so not big deal
--- edit ---
More bugs:
1. I can't change cpu governor
2. WiFi icon and battery icon in statusbar are always black: - bug gone after restart
3. Phone freeze sometimes for a sec.
Eselter said:
Great ROM! Many thanks for your work M.A.D team
I found one bug in camera. When you turn on HDR mode and after taking picture camera force close with toast: "Media server died, closing camera." but photo still save so not big deal
--- edit ---
More bugs:
1. I can't change cpu governor
2. WiFi icon and battery icon in statusbar are always black: - bug gone after restart
View attachment 4337841
3. Phone freeze sometimes for a sec.
Click to expand...
Click to collapse
Thx for your feedback. I'll take a look.... Changing CPU governors is more than less just a left over from older phones... We may just remove this option. There aren't actually useful governors to switch to.
In which situations did it freeze?
Sent from my uhans h5000, running Android 8.0.0
I dont know why, but when i trying to boot in new TWRP recovery, the phone's screen just glows gray.
Can u help me with this? Firmware v23, bootloader unlocked. What's wrong?
DerTeufel1980 said:
Thx for your feedback. I'll take a look.... Changing CPU governors is more than less just a left over from older phones... We may just remove this option. There aren't actually useful governors to switch to.
In which situations did it freeze?
Sent from my uhans h5000, running Android 8.0.0
Click to expand...
Click to collapse
Most often while scrolling (ex in app drawer or browser) and click on some button (ex keyboard). I think it can be releated to CPU hotplug.
xasdfx_ said:
I dont know why, but when i trying to boot in new TWRP recovery, the phone's screen just glows gray.
Can u help me with this? Firmware v23, bootloader unlocked. What's wrong?
Click to expand...
Click to collapse
You flashed the recovery from the download section, right?
Does it show the twrp logo in the beginning?
Eselter said:
Most often while scrolling (ex in app drawer or browser) and click on some button (ex keyboard). I think it can be releated to CPU hotplug.
Click to expand...
Click to collapse
OK. I'll try to reproduce it
Sent from my uhans h5000, running Android 8.0.0
And one more minor bug. In quick settings on weather tile button more settings don't work. If someone wonder it can be adjusted in madOS extras.
DerTeufel1980 said:
You flashed the recovery from the download section, right?
Does it show the twrp logo in the beginning?
Click to expand...
Click to collapse
Yes, of course.
Nope., it doesnt show anything. Oukitel logo - gray sreen. I changed the display on my phone(the old one cracked), maybe the reason is this?
Next two minor bugs:
1. Changing implementation of webview don't work. Phone always using chromium engine.
2. Normal reboot freeze phone. Soft and reboot to recovery works fine.
BTW: do you have some bug tracker ?
And one more:
Battery capacity are wrongly reported.
xasdfx_ said:
Yes, of course.
Nope., it doesnt show anything. Oukitel logo - gray sreen. I changed the display on my phone(the old one cracked), maybe the reason is this?
Click to expand...
Click to collapse
****... Unfortunately I have no idea how to fix it then... We can only use the drivers shared by oukitel. If there's something missing, we're out of luck...
Eselter said:
Next two minor bugs:
1. Changing implementation of webview don't work. Phone always using chromium engine.
2. Normal reboot freeze phone. Soft and reboot to recovery works fine.
BTW: do you have some bug tracker ?
And one more:
Battery capacity are wrongly reported.
Click to expand...
Click to collapse
Webview implementation... We'll check as well, but that's not very important.
Does it always freeze? And where/when? During the new boot, or before shutting down?
In which situations/apps is the battery capacity reported wrong?
Sent from my uhans h5000, running Android 8.0.0
DerTeufel1980 said:
Does it always freeze? And where/when? During the new boot, or before shutting down?
Click to expand...
Click to collapse
Until now always (I try more than 10 times) before shutting down on message rebooting, but now is working fine (magic ;>).
DerTeufel1980 said:
In which situations/apps is the battery capacity reported wrong?
Click to expand...
Click to collapse
In apps: CPU Info and AccuBattery. I don't know if this have impact on battery status in system?
And one glitch very paintful for me :/
Android Auto has problem with displaying on car screen (and Android Studio):
View attachment 4338823
Eselter said:
And one glitch very paintful for me :/
Android Auto has problem with displaying on car screen (and Android Studio):
View attachment 4338823
Click to expand...
Click to collapse
I'll try to check this. We unfortunately don't own a car which supports this
Sent from my uhans h5000, running Android 8.0.0
https://developer.android.com/training/auto/testing/index.html
@DerTeufel1980 my screenshot was made from above tool for devs but in car it look exactly the same
So you can use it to reproduce and debug the glitch.
One more thing related to car. Calls via car speakers not working. Music, call log, contacts working fine via Bluetooth but calls always switch to phone speakers/microphone.
{
"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 8.1.0 ) for Vernee Apollo Lite & X with MTK 6797 SoC
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.
*/
Installation Instructions:
The latest 7.1.2 build must be flashed in SPFT with firmware upgrade mode before this ROM can be flashed (Downloads: VAL, VAX)
Download ROM from M.A.D. Facebook
OR from xda DevDB
Download 8.1 GApps from xda devdb (Mirror)
Backup
Flash new mandatory new Oreo TWRP (available on downloads)
Boot to the new TWRP recovery
full Wipes (dont come crying if you didn't .. ;p )
Install rom (optionally following by GAPPS if you use them)
Optional: go to: wipe --> Advanced Wipe, tick 'cache' and klick 'repair or change File System' --> change File System --> F2FS --> swipe to the right (hit back several times, and proceed the same way with 'data').
Reboot System
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors
Fingerprint
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)
Bugs:
-
XDA:DevDB Information
madOS_O_VAL_VAX, ROM for all devices (see above for details)
Contributors
fire855, DerTeufel1980, superdragonpt
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2017-12-25
Created 2017-12-25
Last Updated 2018-01-13
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
--> Check xda Download Section
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file (LP rom layout)
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: is the Data connection issue of going to / from 4G still present?
A: nope data switchs pretty fast on our new RIL
2G>3G>4G | 4G>3G>2G pretty fast
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
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)
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 Vulkan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: Does 4k video recording work?
A: Yes, but not every phone supports it. If 4k worked in the stock rom, it will work in madOS too.
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/mini
Since there's no Official GAPPS for 8.1.0 just yet...
... we had built OpenGapps nano and pico versions
--> Check Download Section
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.
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...
Changelogs
[Stable] Build [8.1.0] 20171225
First Release
madOS version: 2.1
Patch Level: 8.1.0 [OPM1] December 5, 2017
Kernel: 3.18.89 (o-8.1.0 branch)
[Stable] Build [8.1.0] 20180102
madOS version: 2.1.1
Fixed UI lags / hangs
Fixed deepsleep
Fixed screen recording
Fixed video playback issues
Updated graphics system
Improved GSM/LTE signal handling
Fixed alarms
Fixed FMRadio
Fixed wallpaper scrolling setting in madLauncher
Fixed 5GHz hotspot issues
Improvements in bluetooth for A2DP
Updated included APNs list
madOS color Engine:
Rebased & many improvements on the engine
Better support on theming Quick Settings
New option to override default Google 8.1 QS theming
New reset button to get back to default 8.1 theming
New MAD mode
Merry Christmas !!
Thanks. Merry Christmas.
The computer died. I will not make the sd card backup.
Marry Xmas to all.
Wow.... Oreo release and directly 8.1 weeeeeeeeeeee!
Didn't expect this before the new year, what a surprise.
Thanx you @fire855
Thank you MAD-team
Hi,
How to install ROM and gapps?
On TWRP or using flash?
Thank you
Should we come from the last 7.1.2 build (which has different partitions from stock)?
I really appreciate the work, but it's somewhat unflashable. New recovery is not stable, it gets stuck sometimes. Also I didn't manage to bring 8.1 to run with Gapps yet.
€: To provide somewhat more information: System crashes when running playstore.
€2: Full wipe made, advanced wipe and wiped every partition. It gets stuck coincidential, there's no proper reason for it, it got stuck once when I flashed MadOS itself, second time it got stuck flashing gapps, so I hope I get it run that night...
€3: Recovery freezes and after 30 seconds (approx) phone reboots.
€4: Nope, I don't get it to work, goddamnit. It freezes almost immediately after I enter my pin.
Help please...
I install new TRWP OREO on old twrp...
when reboot the phone shutoff and does nothing... i cant turn on...
TJFA81 said:
Help please...
I install new TRWP OREO on old twrp...
when reboot the phone shutoff and does nothing... i cant turn on...
Click to expand...
Click to collapse
Hold VOL+ and POWER when rebooting. Then you can choose to boot into TWRP. There you copy the new recovery image and then flash Oreo.
Xorianator said:
Hold VOL+ and POWER when rebooting. Then you can choose to boot into TWRP. There you copy the new recovery image and then flash Oreo.
Click to expand...
Click to collapse
I cant...
When choose recovery the phone freezes. black screen
To install new TWRP OREO its only necessary flash the file recovery.img???
TJFA81 said:
I cant...
When choose recovery the phone freezes. black screen
To install new TWRP OREO its only necessary flash the file recovery.img???
Click to expand...
Click to collapse
Yes, you only have to bring the recovery up again.
What you can also do is: Go back to 7.1 (flash it with SPflashtool) and then do the steps
Xorianator said:
Yes, you only have to bring the recovery up again.
What you can also do is: Go back to 7.1 (flash it with SPflashtool) and then do the steps
Click to expand...
Click to collapse
I cant go to recovery...
Can start the phone but cant go to recovery after flash new recovery file posted on MAD facebook.
I dont have 8.1 because of that, just did the first step anda now cant go to recovery
TJFA81 said:
I cant go to recovery...
Can start the phone but cant go to recovery after flash new recovery file posted on MAD facebook.
I dont have 8.1 because of that, just did the first step anda now cant go to recovery
Click to expand...
Click to collapse
Reflash 7.1 image using SPflashtool, I made a guide for this There you go. Then you can repeat.
Okay so 8.1 is not working at all... I get somewhat a weird failure on screen, the screen "sacks" down (main UI Activity just "fall down", status bar is still up) and then it freezes... Looking forward to get this fixed soon.
€: And the boot time is horrible, before I see a screen it's black for idk 2 Minutes
€3: Nvm lol, actually the phone is now unable to boot in System....
€4: Give it a try with "optional" F2FS File system step, let's see.
€5: Nope, didn't fix a thing. So well, at least I could capture this "sack down" thing:
The red line is where the display ends. As you can see the symbols are still in place. The blue line marks where the activity "sack down" and if this happens (which happens just on coincidence) nothing will happen any further, system's frozen and it reboots afterwards.
TJFA81 said:
Hi,
How to install ROM and gapps?
On TWRP or using flash?
Thank you
Click to expand...
Click to collapse
TWRP
Xorianator said:
Reflash 7.1 image using SPflashtool, I made a guide for this There you go. Then you can repeat.
Okay so 8.1 is not working at all... I get somewhat a weird failure on screen, the screen "sacks" down (main UI Activity just "fall down", status bar is still up) and then it freezes... Looking forward to get this fixed soon.
€: And the boot time is horrible, before I see a screen it's black for idk 2 Minutes
€3: Nvm lol, actually the phone is now unable to boot in System....
€4: Give it a try with "optional" F2FS File system step, let's see.
Click to expand...
Click to collapse
Thank you, already did it... reflash recovery.img but by spflashtool. Now im inside twrp3.2.1...
Now its time to try install oreo and gapps
cedricboquiren said:
Should we come from the last 7.1.2 build (which has different partitions from stock)?
Click to expand...
Click to collapse
Yes, the latest 7.1.2 is mandatory. Added this to the first post now too.
I tried to install the new rom, after I installed the new twrp, the phone is still restarting, I tried to return to 7.1.2 with spft but no success even does not connect with the laptop, what I could do they do?
{
"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
{
"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 Vernee Thor (not thor E and not thor Plus) with MTK 6753 SoC
This is only working on devices, manufactured before October 2016. If the pre-installed software was dated October already, your device does not work! Don't ask me/us to fix this...ask Vernee to release the kernel source code! No updated kernel source code --> no updated software.
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 (incl. fingerprint)
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:
nothing
XDA:DevDB Information
madOS_O_THOR, ROM for Vernee Thor (see above for details)
Contributors
DerTeufel1980, fire855, superdragonpt
Source Code: [url]https://github.com/MediatekAndroidDevelopers[/URL]
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.18.y
ROM Firmware Required: phone manufactured before october 2016
Based On: AOSP
Version Information
Status: Stable
Created 2018-03-20
Last Updated 2018-03-20
Reserved
First time Install Instructions
0) Preparation
0.1) Backup your important data to PC
0.2) Download “twrp_vernee_thor_oreo.img“:
http://www.mediafire.com/file/m58f5ifmopyb209/twrp_vernee_thor_oreo.img
0.3) Download “madOS_8.1.0_thor_2018xxyy.zip“ https://www.facebook.com/MediatekAndroidDevelopers/
0.4) Optional, Download “Google Apps (aka Gapps)“: http://opengapps.org/. Choose: “ARM64“, “Android 8.1“, “nano“ or “pico“ package
1) Flash the recovery and boot to it. (choose option a) if you don't have another TWRP already installed, else choose b))
1.1a) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader").
Then execute command “fastboot flash boot twrp_vernee_thor_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).
1.1b) Boot to your current TWRP. Choose install --> image, and select twrp_vernee_thor_oreo.img“. Then choose “recovery“ as the target. After few seconds, and succesful installation, hit “back“ several times, then go to “reboot --> recovery“
2) Install
2.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".
2.1) While already in recovery (TWRP), connect your phone to pc, and copy “madOS_8.1.0_thor_2018xxyy.zip“ and the Google Apps to your phone.
2.2) Go to "Wipe", and directly slide the slider to the right.
2.3) Get back to main menu with the "back" button
2.4) Go to "Install" and hit “madOS_8.1.0_thor_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.
2.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: Can I install this rom on any other device, than the one mentioned in the title/description?
A:
WTF! Of course not! It is not mentioned in the title/description for some reason...how stupid can one be?!
If you still come to my thread and ask this stupid question, I'll answer some random nonsense. Don't come to me to complain when you break your device!
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...
Reserved
Can I install it on my K4 Note?
Pritam Tumma said:
Can I install it on my K4 Note?
Click to expand...
Click to collapse
Can you read?
Is it possible to roolback to nougat (7.1.2) after install this update?
drifeter said:
Is it possible to roolback to nougat (7.1.2) after install this update?
Click to expand...
Click to collapse
Yes, you would need to flash the N twrp, wipe and flash the N rom
"Size of image is larger than target device" trying to flash new recovery. I just wiped everything, now I'm out of OS for this moment xD
Can you help me?
I used your last OS on this phone. It's before october(received it on may of that year) and MT6753
I have twrp 3.0.... from megthebest
Thank you for your patience
--
EDIT: Can I wipe "internal storage"? I didn't wipe everything :v
ZeDdYRov said:
"Size of image is larger than target device" trying to flash new recovery. I just wiped everything, now I'm out of OS for this moment xD
Can you help me?
I used your last OS on this phone. It's before october(received it on may of that year) and MT6753
I have twrp 3.0.... from megthebest
Thank you for your patience
--
EDIT: Can I wipe "internal storage"? I didn't wipe everything :v
Click to expand...
Click to collapse
I'll check the size error in a bit...
Of course you can wipe internal storage, but keep in mind that this is where your pictures are.
edit: checked/flashed the twrp_vernee_thor_oreo.img.... all fine with it...its size is 13.4mb, the recovery partition is 16mb. i suppose this 'megTheBest recovery' just isn't the best....
DerTeufel1980 said:
I'll check the size error in a bit...
Of course you can wipe internal storage, but keep in mind that this is where your pictures are.
Click to expand...
Click to collapse
Thank you for your quick response!
I wiped internal storage, data, cache, and system. Do I should wipe anything more in order for this to work? I'm still stuck on the error. I go to Install - Install Image, pick the twrp_vernee_thor_oreo.img file on Recovery Partition, and receive the message on the comment above.
ZeDdYRov said:
Thank you for your quick response!
I wiped internal storage, data, cache, and system. Do I should wipe anything more in order for this to work? I'm still stuck on the error. I go to Install - Install Image, pick the twrp_vernee_thor_oreo.img file on Recovery Partition, and receive the message on the comment above.
Click to expand...
Click to collapse
Since you already removed everything, I'd suggest to just install the stock 6.0 rom with flashtool and 'firmware upgrade' option
DerTeufel1980 said:
I'll check the size error in a bit...
Of course you can wipe internal storage, but keep in mind that this is where your pictures are.
edit: checked/flashed the twrp_vernee_thor_oreo.img.... all fine with it...its size is 13.4mb, the recovery partition is 16mb. i suppose this 'megTheBest recovery' just isn't the best....
Click to expand...
Click to collapse
lol, I just gave the name of the dev because could help you figure it out. I'm n00b on this :V
I just did sh** with the files. I was trying to flash with a file called twrp_blablabla.img that was 422MB. For some reason I missclicked on the file while saving :v
EDIT: SORRY and Thank you
Yeahhhhhh finally 8.1 on our Thor.... So great!
Thank you so much Mad-team.
Weeeeeeeeeeeeee!!!
DerTeufel1980
Thank you for your work
Everything works without problems.
:good:
I'm on madOS for 40min and I'm loving it. This is fully customize as you want this machine working. Well played!!! LOVE YOU MAD TEAM
Hello again! Software buttons get bugged when we enter on opened apps menu, and its has a ghost start buttons I'm n00b and I found a bug: D
ZeDdYRov said:
Hello again! Software buttons get bugged when we enter on opened apps menu, and its has a ghost start buttons I'm n00b and I found a bug: D
Click to expand...
Click to collapse
I am using softbuttons for a long time and they always work good. Maybe you can try to go back to default settings... Wipe cache/dalvik and try again
This is for the first revision, is it possible for you to make it for the second? Please...
RalphMalph said:
I am using softbuttons for a long time and they always work good. Maybe you can try to go back to default settings... Wipe cache/dalvik and try again
Click to expand...
Click to collapse
If I could be able to change what buttons do... the back button on soft button is on the right, and I'm used to it on the left. There's any option on madOS to change what I'm telling to you?
EDIT: I read second time and notice what you said. I'll try! Thank you for the tip
ppdua said:
This is for the first revision, is it possible for you to make it for the second? Please...
Click to expand...
Click to collapse
Re-read at least the first ten lines of the first post, before asking things like this