Development [ROM] [ 8.0.0 ] Official madOS - Oukitel K6000 Plus [MT6750]

Search This thread

CraschTD

Senior Member
Sep 7, 2009
74
20
Twrp oreo fails to start

****... 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...
I have the same problem. Flashing twrp oreo, when starting the phone flashes five times and then remains gray.
With Jemini TWRP 3.1.1 it start in recovery correctly, but when I try to install Oreo ROM I got "Updater process ended with ERROR: 7"
Tried to redownload zip files and reinstall, but I've got same behaviour.
 

DerTeufel1980

Inactive Recognized Developer
Jul 31, 2011
10,368
27,668
I have the same problem. Flashing twrp oreo, when starting the phone flashes five times and then remains gray.
With Jemini TWRP 3.1.1 it start in recovery correctly, but when I try to install Oreo ROM I got "Updater process ended with ERROR: 7"
Tried to redownload zip files and reinstall, but I've got same behaviour.
If the oreo trwp does not work, chances are almost 100% the rom would not work as well.
Are you familiar with adb shell?
 

CraschTD

Senior Member
Sep 7, 2009
74
20
If the oreo trwp does not work, chances are almost 100% the rom would not work as well.
Are you familiar with adb shell?
Yes, i'm familiar with adb...
I found a workaround...
I modified updater-script removing the first two lines when it checks for version and model... (I know it's dangerous :p)

Anyway rom installs ok, now I'm installing gapps... finger crossed...
edit: Oreo installed and everything seems working fine!!! So far so good.
Waiting for 8.1... great job!!
edit 1: screen turned off and didn't came back... Phone still alive. Tried to reboot it but after the oreo logo it went black and restarts itself.
Tried reinstalling ROM but till now same behaviour :(
Edit 2: restarting phone in safety mode (press Vol- on restart) I got to the rom. So it's something loaded on startup. How can I troubleshoot that?
Edit 3: attached adb bugreport done with phone working but with black screen
Edit 4: installing gapps solved the problem! But now lots of FC on gapps! Retrying with pico version.
Edit 5: formatting f2fs cache partition with TWRP Jemmini screws up things
Edit 6: attached logcat of google play services fc
Edit 7: repeated everything from the beginning and now no more FC, when screen turns off it didn't come back (phone is working fine except this)
It seems that to solve this problem we have to know why Oreo TWRP is not working (blank screen) and Jemmini 3.1.1 does.
  • put phone in fastboot mode
  • Attach to pc
  • start with TWRP Jemmini with
    HTML:
    fastboot boot recovery.img
  • In TWRP full wipe and install MadOs, gapps
  • After starting MadOs enable debug mode (to ease restarting from adb)
attached logcat of display not showing (screenblack.txt)
 

Attachments

  • bugreport.7z
    692.3 KB · Views: 7
  • GooglePlayFC.txt
    52 KB · Views: 5
  • ScreenBlack.txt
    5.8 KB · Views: 1
Last edited:

CraschTD

Senior Member
Sep 7, 2009
74
20
I know that I shouldn't ask for ETA, but...

I have to decide if it's better to wait for 8.1 (hoping my problem will be fixed) or returning to 7.
Thanks
 

Breathewave

Senior Member
Oct 6, 2014
79
15
Redmi Note 10 Pro
I wanted to know with return version nougat android 7. factory version. wanted to know procedure
You need Oukitel's Stockrom from the website and a recent version of the SPFlashTool (I'm using it on Arch Linux -> AUR package). The scatter file you need is part of Oukitel's Stockrom archive.

-> Backup you stuff first, especially the internal storage! Your SD card won't change at all.

-> Turn off your phone, start SPFlashTool, select the driver and scatter file.

-> Use "Download only" from the drop down menu below and hit the "Download" button above.

-> Remember: the entire internal space will be overwritten!

-> Hold Volume + and plug in your USB cable. If you get an error message, use another driver for flashing your phone.

Good Luck :)
 
  • Like
Reactions: DerTeufel1980

bakker_be

Member
Jan 18, 2006
31
1
Orange State, any fix?

Hello, after a previous f***-up, resulting in a "Red state" bootloop, I seem to have succeeded in flashing this ROM. It still gives an "Orange State" warning though. Is that "as expected" or is there a fix for that?
EDIT: it seems that quickcharge doesn't work in this ROM ...
 
Last edited:

Breathewave

Senior Member
Oct 6, 2014
79
15
Redmi Note 10 Pro
Hello, after a previous f***-up, resulting in a "Red state" bootloop, I seem to have succeeded in flashing this ROM. It still gives an "Orange State" warning though. Is that "as expected" or is there a fix for that?
EDIT: it seems that quickcharge doesn't work in this ROM ...
In order to remove the "Orange State" message, you need to lock the bootloader again with "fastboot oem lock" + Volume up.

The battery capacity is wrong within the ROM (4500 mAh vs. "real" 6080 mAh), so turn off the phone to make use of the quick charge feature used by the device's firmware. I noticed no severe additional time while charging it.
 
Last edited:

bakker_be

Member
Jan 18, 2006
31
1
It seems that Bluetooth isn't working very well ... I have several bizarre symptoms, all when connected to my cars (VW Golf VII) infotainment system. I don't use Bluetooth anywhere else. None of these symptoms were present in the original ROM
-Streaming off-lined Spotify or Tidal content isn't always fluent. I get a lot of "stuttering", as if it's rebuffering
-I can't use it to make a phone-call. It just reverts to the handset
-It doesn't seem to really save the connection. Each time I get into my car I get a new pairing request. On the phone I only see the one device for my car, but in the car's paired devices list a new entry is added on each connection
-It doesn't keep a custom name after a reboot. I renamed it to "K6000" in stead of the default "Oukitel k6000_plus", and after a reboot it has reverted to the default
 

bakker_be

Member
Jan 18, 2006
31
1
In order to remove the "Orange State" message, you need to lock the bootloader again with "fastboot oem lock" + Volume up.

The battery capacity is wrong within the ROM (4500 mAh vs. "real" 6080 mAh), so turn off the phone to make use of the quick charge feature used by the device's firmware. I noticed no severe additional time while charging it.

Hmmm, that gave me "red state" again :( Trying to solve it again, using this thread https://xdaforums.com/android/general/fix-orange-bootloop-oukitel-k6000-plus-t3747273 as before ...

EDIT: That didn't work. Thinking it was because of the locked bootloader, I unlocked it again, and now at least my phone starts up again ...
 
Last edited:

DerTeufel1980

Inactive Recognized Developer
Jul 31, 2011
10,368
27,668
  • Like
Reactions: bakker_be
D

Deleted member 8900137

Guest
How much time we need to wait for a perfect version offline Oreo 8.1? 1/2/3/6 month?
 

b3stw4y

New member
Jul 5, 2015
4
0
Hi everybody,

my battery lifetime has decreased significantly since i flashed this rom, had the stock android 7.0 on it before
is it normal?
and also my touchscreen is not working sometimes, but this was also on the stock rom a problem, so i think it's a hardware failure.
someone got the same symptom?

greetz
 

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    VmDiDSr.png

    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
    8
    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)
    4
    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: mediatekandr0iddevelopers@gmail.com



    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...
    3
    I need to check/fix some performance issues on 8.1 first
    3
    New version coming soon? :)

    8.1.0 had some issues on this device initially...
    finnaly all seems nice now, 8.1.0 r14 (february patch level) is currently under testing


    cheers ( no ETA)