Database Info

Huawei P9 [ROM][6.0] NewWorld-7-by-Tecalote

{
"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"
}
Huawei P9 Marshmallow Custom Rom​
* NewWorld Version 7 *​
for EVA L09-AL00-AL10-CL00-DL00-L19-L29-TL00 - but not P9 Plus and not P9 Lite​
Continuation and further development of the popular Custom Rom of Senior Member @Blackball from the Thread: https://forum.xda-developers.com/p9/development/rom-huawei-p9-fromfuture-newworld-t3390820​
NewWorld 7 Thread for German Users is here: http://www.android-hilfe.de/thema/huawei-p9-rom-6-0-newworld-7-by-tecalote.799824/
So far, I develope Custom Roms for Huawei P8: https://forum.xda-developers.com/huawei-p8/development/rom-huawei-p8-gratitude-tecalote-t3468118 and newest creation: https://forum.xda-developers.com/huawei-p8/development/rom-huawei-p8-arrow-custom-rom-based-t3561615/
I am happy to present you now a Custom Rom for Huawei P9! Have much fun with it
Note:
If you don't come from NewWorld 5 or 6.6 - you must be (or go back to) on the latest Official Marshmallow Stock Firmware for your Device - Fingerprint would not work whitout this step!
See Requirements and Instal Instructions...
Features:
- based on Firmware b198 with the KangV Framework (Kang Tools / K-Settings) - which allows you a maximum customation!
- pre rooted with SuperSU 2.79 in System-Mode
- BusyBox 1.26.2 YDS by YashdSaraf
- deodexed and debloaded
- Callrecorder in Dialer-app for manual recording
- Recording of Calls automatically
- NFC ported from latest Marshmallow-Build
- Google Apps are up-to-date (2017-01-19) - (Google Login, Gmail, Exchange, Playstore, Google App, Chrome
- Special Restart Menu: Normal reboot, Hot reboot, Recovery mode, Bootloader mode
- included in K-Settings: Xposed Framework 87.1 from Wanam (install it from there: K-Settings, More settings, Xposed Framework - install Xposed) Reboot about 10 min.
- Management of Xposed Framework and Modules with Material Installer in K-Settings
- Special Phone Manager (Permission Manager, Autostart Manager, Notification Manager, Spamfilter, Virus-scaner, Dropezone Manager...)
- Maximum battery life
- some Apps preinstalled: TitaniumBackup, BlackPlayer and MiXplorer (very good Root-Explorer)
- Dolby/Atmos™ with Viper4AndroidFX™ (Atmos on Homescreen - but Viper4Android in K-Settings, More settings)
- Dual-Window-Mode can be started from 583 Apps - but added in the second window to the started App in the first window can only 28 Apps - experimental feature...
- some nice Themes (Porsche Design from Mate 9, BlackPyramid Theme from blackbell....) by the way, Online-Themes are working, but you have to register a Huawei ID
- a lot of more
Themes:
Some Useres had problems to activate Themes after installing the Rom. This problem occurs normally not and it is not an issue of the Rom.
Thats why I recommend following:
Before flashing the new Rom make a Backup of your Themes.hwt(s) from the folder HWThemes on internal memory and store this in another folder on your external SD. After delete the HWThemes folder on internal memory (it will created automatically again)
If you make a Nandroid Backup before wiping previous system and flashing the new Rom, reboot your TWRP within the main menu of TWRP "Restart" ...restart TWRP. After you can make a wipe and flashing the Rom.
TWRP (everyone for Marshmallow p9, my linked same as the one from paulobrien) has sometimes problems with mount and unmount Partitions.
The result is (not copied) missing files, like Themes. Themes will be installed in NewWorld 7 not in /system/themes (there are just the icons - for saving place in system Rom) but in /data/hw_init/system/themes. If you have already such a problem with Themes, just flash the ThemesFIX.zip with TWRP (without making anything before and no Wipe of Dalvik and Cache after) - this solve the issue. As I said, it occurs just sometimes.
General Requirements:
1) Marshmallow-Bootloader - if you are on Lollipop or Nougat the Rom cannot be flashed!
2) Bootloader unlocked http://emui.huawei.com/en/plugin/hwdownload/download
3) TWRP P9 for Android 6: https://www.androidfilehost.com/?fid=457095661767122229
Note: TWRP has sometimes after an Nandroid Backup problems to unmount data or system. If you do Nandroid Backkup - please restart after TWRP from the main menu (Reboot Recovery) before wiping and flashing new Rom!
4) If you come from NewWorld 4.1 - or from nanoROM MallowPOP - be sure making the steps from the Installation instructions, otherwise Fingerprint-Scanner would not work!
Download Rom:
NewWorld 7: https://www.androidfilehost.com/?fid=529152257862696521
MD5: 749b1ec0ef072274221c7e77ea6bfc40
Themes-Fix: Only for Users which have problems after flashing the Rom with Themes: https://www.androidfilehost.com/?fid=817550096634742413
MD5: 749b1ec0ef072274221c7e77ea6bfc40
Installation instructions:
If you are currently on the latest official Huawei Marshmallow Stock-Firmware it is easy to install this Custom Rom. Your Stock System must not be rooted, because flashing this Custom Rom will Root it during installation.
1) First of all make Backups of your current system with Apps and data...
2) Activate Developer Options and in there USB-Debugging and OEM Unlock. In Advanced Settings activate "Unknown Sources"
3) Connect your Phone with USB to PC (drivers should be installed, how to do see below) and open Minimal ADB and Fastboot as Administrator.
4) With adb command boot your Phone into Fastboot Mode and unlock your Bootloader (everything explained below)
5) Unlocking your Bootloader makes automatic factory reset
6) Make a short setup (without Google Login or Fingerprint...) and activate Developer Options with USB-Debugging and OEM-Unlock again, also activate "Unknown Sources" in Advanced Settings.
7) Download the Rom an place it on your external SD.
8) Flash TWRP, disconnect P9 and PC from USB and boot with the Hardware-Key into TWRP (Vol+ and Power Button)
9) With TWRP make a Nandroid Backup of your Stock-Rom to your external SD (all shown partitions)
10) After go in TWRP to Wipe, but Advanced Wipe and wipe Dalvik, Cache, data and system (Fullwipe, no need to wipe SD Card)
11) Now you go to the main menu "Install" and navigate to the place (change directory), where the Rom.zip is located and swype to install. Wait until the Install-Script is finished, after reboot your Phone.
12) Restart needs between 5 and 10 minutes. Wipe of Dalvik and Cache after flashing the Rom is not necessary, because you have done it before.
If you came from NewWorld 4.1 you must go back to the last official Huawei Firmware for your model. Without these steps your Fingerprint-Scanner would not work! Please check by yourself the Download of the last Full Marshmallow-Firmware for your model. Only for EVA-L09 Cust 432 (official - not Leak) you can Download it here: http://www.carbontesla.com/2016/11/download-huawei-p9-b182-marshmallow-update-europe/
Steps:
1) Unzip the downloaded Firmware - create a folder on your external SD named dload and copy the UPDATE.APP in there.
2) Make a Backup of your Apps with data and everything you want to backup. Maybe also a Nandroid Backup with TWRP
3) Go to K-Settings, More Settings, Flash Recovery - flash official Recovery (grant Root Permissions)
4) Boot with the Restart Menu to the Stock Recovery. Wipe Cache with it. Restart the Phone with the 3 Buttons-Method (press in the middle of Vol+ and Vol- and press the Power Button until P9 restarts and begin with the EMUI Huawei Software Installing.
5) Bootloader will do closing during this operation.
6) Make a short Setup (without Google Login, Fingerprint or anything)
7) Go to Settings and activate Developer Options (7 times tap on build in "About the Phone"). In Developer Options activate USB Debugging and OEM Unlock.
8) In Advanced Settings activate "Unknown Sources"
9) With latest HiSuite: http://consumer.huawei.com/minisite/HiSuite_en/index.html install the Driver for your P9 - connect it with USB to your PC and close HiSuite.
10) Install Minimal ADB and Fastboot and open it as Administrator: https://forum.xda-developers.com/showthread.php?t=2317790
11) With: adb devices you will see if the connection is ready (Phone must be listed with Serialnumber - device)
12) With: adb reboot bootloader you start the Phone into Fastboot Mode
13) With: fastboot devices you check the connection (Phone must be listed with Serialnumber - fastboot)
14) With: fastboot oem unlock xxxxxxxxxxxxxxxx (instead of xxx.... you must write your Unlock-Code from Huawei and enter) your Bootloader will be opened
15) Phone makes automatically Factory Reset!
16) Go to settings, activate Developer Options and in there USB Debugging and OEM Unlock and in Advanced Settings "Unknown Sources"
17) Connect your P9 with USB to your PC
18) With Minimal ADB and Fastboot (opened as Administrator) restart the Phone to Fastboot Mode
19) flash TWRP (Rename the downloaded one to TWRP - its called then TWRP.img) fastboot flash recovery TWRP.img
20) Cut the USB connection between P9 and PC before restart to Recovery
21) With pressing Vol+ and Power Button restart your Phone until Huawei Logo appears, dont press Power then but keep holding Vol+ until TWRP is booting.
22) Setup language, screen timeout, time zone..... and allow Systemmodification
23) Go to Wipe - Advanced Wipe and wipe Dalvik, Cache, data and system
24) Restart Recovery with Restart Recovery in TWRP and flash the Rom! After flashing no wipe of Dalvik and Cache, because you have done it before.
If you came from Nano Rom: https://forum.xda-developers.com/p9/development/rom-ncs-rom-v1-1-08-16-2016-t3440269 - you must do following steps:
1) Download Blackballs NewWorld 4.1: https://www.androidfilehost.com/?fid=24591000424954817
2) Backup your Apps with data
3) With TWRP make Advanced Wipe of Dalvik, Cache, data and system - after flash NewWorld 4.1
4) Do all 24 Steps written above!
Push-Notifications
The Push-Notifications are working for sms, mms, email....
But for WhatsApp, Viber, Skype and other Chat/Net-Call Apps the push-notifications work only perfectly if you convert them into a system app.
After flashing the Rom and the Setup you install your Apps and may restore some Apps with data from a previous backup.
Example: WhatsApp. Install it from the Playstore. Dont open it. Install Link2SD from the Playstore. Link2SD give you a list of all Apps - for example "WhatsApp" - just press long on it and you get a menue - use: convert to system-app. Then reboot your Phone. This time open WhatsApp and you have to authentication WhatsApp again. WhatsApp is searching for a Backup and offer you to restore it. You do this and now Push-Notification will work (dont forget to make a Google-Drive Backup of the Chat-History in Settings of WhatsApp before flashing the Rom)
Additional information: https://forum.xda-developers.com/showpost.php?p=70726169&postcount=30
Switch of chinese Letters:
Go to K-Settings, in there to Notification Settings/Show statusbar lunar - disable it.
After go to Lockscreen und desktop settings/Lunar calender + Desktop wheather lunar - disable it.
HAVE MUCH FUN WITH THIS ROM
At this Point I wanna thank KangV for his great K-Settings Framework
If you like NewWorld- fell free to donate KangV: https://www.paypal.me/KangVIP
And if you like my Work too, feel free to donate to me: https://www.paypal.me/Tecalote
Many thanks and credits to other great Developers:
@guitarededhero (Viper/Atmos) https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
@wanam and @rovo89 and @DVDandroid for the Xposed Framework Development
@HootanParsa (MiXplorer) and @YashdSaraf (BusyBox arm64)
@topjohnwu (systemless Xposed Framework and Magisk)
@Chainfire - SuperSU
@dkionline - Custom Roms for P9
@Blackball - BlackPyramid Theme and Custom Roms for P8 and P9
​

Tutorial for return from NewWorld to Stock Marshmallow Firmware
If there is a reason to return from NewWorld to Marshmallow Original Stock Huawei Firmware - you can use this steps:
1) Backup what you need to backup! Use Huawei Backup and also Titanium Backup. NOTE: In the new Firmware or Rom dont restore system-apps or data from system-apps from previous system! Restore only USER-APPS. For Chat-Apps like WhatsApp, Viber, Skype use the built-in Backup function - but keep or backup the folder from those apps on internal memory (because you need them on the same place if you reinstall those apps)
Battery must have minimal 80% doing those steps....
If you have Xposed Framework installed - uninstall it (K-Settings /Xposed Settings /Install Xposed confirm - Reboot needs about 15min)
2) Open K-Settings /more settings /flash recovery - Flash official Recovery (grant Root-Permission) - this flashes Stock Recovery in half a second.
3) Download the Full Firmware (no OTA.zip) for your model, unzipp it on your PC (mostly you get update.app and meta.inf)
4) Create a folder on internal memory or external SD and name it: dload
5) Copy only update.app and meta.inf (if meta.inf is present) in this folder. After DISCONNECT USB from Phone!
6) Reboot to Stock Recovery - with Restart menu (also possible with pressing Vol+ and Power-Button at the same time as long until Recovery is displayed)
7) Wipe Cache with Stock Recovery (it uses another engine than TWRP) and do after a Factory Reset. There is no need to restart the phone to system now.
8) Press Vol- and Vol+ (in the middle) and Power-Button at the same time, until phone reboots and EMUI-Software-Installing is displayed
9) Let the EMUI-Installing finishing - it reboots automatically to system and starts the EMUI-Optimizing - wait until Language-Selection (new setup for you phone) is displayed.
Now you are back on Stock Firmware - Bootloader was automatically closed during Firmware-Installing
You can stay now on Marshmallow or update to Nougat if you like. But note: Once you are on Nougat - the Downgrade to Marshmallow is possible but not recommended (cause people reporting errors after Downgrade)
If you want to stay on Marshmallow and flash another Marshmallow based Custom Rom, continue from step 9 as follow:
9) In this case make just a short set up (You can skip the most) - but it is important to arrive the homescreen.
10) Go to Settings / About the phone and tap 7x (times) on Build-Number. It activates developer options.
11) Go to Developer options and activate USB DEBUGGING - and OEM-UNLOCK - after open Advanced settings /security and activate "Unknown Sources"
12) Connect Phone with USB to your PC (Accept the Fingerprint query with "always" on your Phone) Look, if Windows installed the right drivers so you have access to phone - if not install HiSuite http://consumer.huawei.com/minisite/HiSuite_en/index.html and make a connection with HiSuite. Allow installing HiSuite on Phone. If you have access now, close HiSuite (also in Background).
13) Copy the new Marshmallow based Rom to your Phone.
14) You need your Bootloader-Unlock-Code from Huawei!
15) With Minimal ADB and Fastboot unlock your Bootloader
16) Your phone will wiped with Factory Reset.
17) With Minimal ADB and Fastboot flash TWRP.
18) DISCONNECT USB Cable now from your Phone
19) Press Vol+ and Power-Button at the same Time until phone reboot (at the moment, Huawei Logo comes you can leave Power Button, but keep holding Vol+ until TWRP is displayed) - Reboot to TWRP takes a while
20) Set up TWRP (allow modification, set language, screen timeout, time zone...)
21) There is no need to wipe internal SD (but if you like to do this, do it at first and restart after TWRP - then you must setup TWRP again)
22) Go to Wipe, Advanced Wipe and wipe: Dalvik&Cache, Cache, data and system
23) Install the new Rom
24) Restore User-Apps, but dont restore any System-Apps (or data from it) Chat-Apps install from Playstore, and use the built-in restore function.
Huawei-Firmware-List:
Use only Marshmallow Full Firmware to retourn from NewWorld to Stock (mostly b182 or b181). Choose the right one for your model and cust! As far as I know all versions over 300 are based on Nougat (those you cannot use)
EVA-L09: http://hwmt.ru/oth/HWFF/info/view.php?find_model=eva-l09
For EVA-L09 - I would recommend following Firmware: http://www.carbontesla.com/2016/11/download-huawei-p9-b182-marshmallow-update-europe/
EVA-L19: http://hwmt.ru/oth/HWFF/info/view.php?find_model=eva-l19
EVA-L29: http://hwmt.ru/oth/HWFF/info/view.php?find_model=eva-l29
EVA-TL00: http://hwmt.ru/oth/HWFF/info/view.php?find_model=eva-tl00
EVA-ALxx: http://hwmt.ru/oth/HWFF/info/view.php?find_model=eva-AL (not sure, but maybe work on CL and DL variants)
Another Thread for Firmwares:
https://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586
How do debrand Huawei Phone by SRK Tool Huawei:
https://forum.xda-developers.com/p9/how-to/vdo-guide-how-to-debrand-huawei-phone-t3410045
More debranding Stuff:
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523

Awesome!! Thank you for bringing in your custom stock rom to XDA!

Z-Blade said:
Awesome!! Thank you for bringing in your custom stock rom to XDA!
Click to expand...
Click to collapse
Your welcome

On 6.6, automatic call recording wasn't working. Did you fixed it?

kye04 said:
On 6.6, automatic call recording wasn't working. Did you fixed it?
Click to expand...
Click to collapse
Hello Thanks for informing me. Nobody told me in the German Thread, that's why I didn't know.
I always use the manual call recording and have not tested the automatic one. I make a test today in the evening and tell you!

Is there anyway to install this on a EVA-L09C34 (Optus/Australia) model.

It was hard for me to go to the german forum and regisster, post etc..... I am glad you moved here...... U`ll have more support, u`ll see...
Also I am happy that someone still works on this rom. It is the best and most complete rom for P9 .

Zac_kha said:
Is there anyway to install this on a EVA-L09C34 (Optus/Australia) model.
Click to expand...
Click to collapse
This rom should work with all L09 variants, the C34 is pretty much the carrier model, so C34 means Optus and I think Vodaphone Australia also has a different carrier model. Ultimately, L09 all have the exactly same hardware.

Vielen Dank!
I downloaded this from android-hilfe.de last week (with the help of Google Translate!). An excellent rom and a worthy successor to @Blackball 's fine efforts. No obvious bugs or glitches that I can see, runs very smoothly.
Can't wait for your efforts with Nougat!

kye04 said:
On 6.6, automatic call recording wasn't working. Did you fixed it?
Click to expand...
Click to collapse
I have tested it on my phone right now and it works in NW 6.6 - and also NW7
You must open Dialer and there the menu symbol right below.
Open settings, in there enable record settings (see Screenshot)
If you call somebody or get calls it will automatically record the calls to external SD in the folder record
Test it again please. If it doesn't work for you, tell me.

colthekid said:
Vielen Dank!
I downloaded this from android-hilfe.de last week (with the help of Google Translate!). An excellent rom and a worthy successor to @Blackball 's fine efforts. No obvious bugs or glitches that I can see, runs very smoothly.
Can't wait for your efforts with Nougat!
Click to expand...
Click to collapse
Hello Thanks for the positive message!
I am working on the Nougat Version.
There are a few impairments at the moment:
TWRP for Nougat doesn't support data encryption yet...
The Google Security Level is very high.. Difficult to manipulate some processes..
Xposed Framework is not released yet for Nougat. Hopefully @rovo89 can get it work for Nougat...
KangVs Framework is working already on Nougat, K-Settings working - but modifications are only possible in system and boot, Root with SuperSU is possible - Manipulations on cust or vendor in the moment not.
The development is in progress

hi friends... how to make the huawei themes working on this rom?
i came from stock B182 where the themes were working fine..!
after flash this rom the themes doesnt apply..
Sorry for my bad english
Edit: i solved the themes issue by flashing throug 3 buttons only the cust from B182, now i have theme working again.. i made a zip flasheable of the rom with the cust if someone want it.. i will upload it to mega and put the link soon

cesarguaro said:
hi friends... how to make the huawei themes working on this rom?
i came from stock B182 where the themes were working fine..!
after flash this rom the themes doesnt apply..
Sorry for my bad english
Click to expand...
Click to collapse
Hi Themes should work. I flashed even from b182 and Themes are working.
Same issue had one Person of the German Thread.
Please check the MD5 on Filehost (I post it later in OP)
Make wipe of Dalvik and Cache, restart TWRP and flash the Rom again please.
Edit :
Before you should go to the folder HWThemes on internal Memory. There is a hidden folder .cache - delete everything in it. Backup in the HWThemes folder the .hwt files you want to store. Store it on another place on external SD. Delete every .hwt in HWThemes on internal Memory.
I don't know, why this issue sometimes occurs, cause normally it does not.
Please inform me.

cesarguaro said:
hi friends... how to make the huawei themes working on this rom?
i came from stock B182 where the themes were working fine..!
after flash this rom the themes doesnt apply..
Sorry for my bad english
Edit: i solved the themes issue by flashing throug 3 buttons only the cust from B182, now i have theme working again.. i made a zip flasheable of the rom with the cust if someone want it.. i will upload it to mega and put the link soon
Click to expand...
Click to collapse
I saw just right now, that you solved the problem. Which cust to you have? Normally the cust of the Rom is working for all...

Tecalote said:
I saw just right now, that you solved the problem. Which cust to you have? Normally the cust of the Rom is working for all...
Click to expand...
Click to collapse
i have the B182 with cust C432..!!!

cesarguaro said:
i have the B182 with cust C432..!!!
Click to expand...
Click to collapse
I have the same cust and was on b182, flashed the Rom and Themes working...
I don't think, its an issue of cust.
I believe it is a problem of TWRP.
If I make a Nandroid Backup and flashed after wiping immediately the Rom, TWRP has sometimes problems to unmount and remount partitions.
This produce then an error in the shown install script (system or data couldn't unmounted, they are busy - something like that...)
The Themes are in this Rom not located in /system/themes (there are just the icons to save place of system Rom)
The Themes are in /data/Hw_init/system/themes
If TWRP produce an error in mounting data after doing something before flashing the Rom, then Themes don't work cause the files were not copied as they should.
That's why I recommend to Reboot TWRP before flashing the Rom.
This was also the reason by a German User from Android Hilfe Thread.
He flashed the Rom again, and with the second flashing, Themes are working..
Edit: if you have flashed cust C432 it could be that the Phone Manager loose some parts like Permission Manager, Autostart Manager and so on?

I want to install sound mod on this rom (arise sound system) can i install this on this rom which has another sound mod? Will it work?

maliniaka said:
I want to install sound mod on this rom (arise sound system) can i install this on this rom which has another sound mod? Will it work?
Click to expand...
Click to collapse
Hello I cannot say. I must test it. Can you give me a link to this sound mode?

Tecalote said:
Hello I cannot say. I must test it. Can you give me a link to this sound mode?
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 I'm trying now, I will say how it works!
EDIT1: It isn't working My p9 stuck on startup :/

[GUIDE] Install Any ROM, GApps, Magisk, TWRP, DolbyAtmos and more for Mi A1

{
"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"
}
Hello, I've seen a lot of community members struggling to install custom ROMs, GApps, Magisk or DolbyAtmos, so I've created a guide. So did I, this took me around 15 tries without bootlooping or breaking my OS. Yes, I was really new at this. Some guides had broken English that I couldn't understand, others were too complicated.
However, now I am presenting you a fully working, detailed (and easy) guide. Hopefully, it'll help at least someone to avoid potential mistakes when flashing or using root. Good luck!
(If you don't install TWRP, the GApps version will mismatch!)
(Probably not anymore, needs a confirmation.)
All-in-One installation .7z package: (NOW ONLY INCLUDES MAGISK, ADB DRIVERS, RECOVERY AND GCAM MOD. CHOOSE THE ROM YOURSELF.)
GDrive: https://drive.google.com/open?id=1tkkVyuGfv2UYvehsV7cmGi9BQ2msodKY
Mediafire: http://www.mediafire.com/file/y146i4satahiper/updatedFiles-Magisk-Recovery-GCam-ADB.7z
Mega: https://mega.nz/#!B34XmbLD!GzZuJthLWrJbsHqRd_r-wxMKOwvi3fQdGOmWmW0Mtlo
(Extract with 7zip or WinRar before using)
Enabled developer options with ADB debugging enabled (Settings->System->About Phone->Tap 7 times on Build Number, go back, Developer Options, scroll a bit down, Android Debugging - Enabled)
Backup any photos or videos, if needed.
Unlocked bootloader (Open a cmd in the folder->adb reboot bootloader->press Yes if your phone asks for a confirmation->fastboot oem unlock)
1. Open a command prompt in the provided folder
2. Use the command adb reboot bootloader
3. Use the command fastboot boot recovery-3.2.1-2-oreo.img
(Press Keep Read Only)
4. Go to Wipe->Advanced Wipe->Select: Dalvik / ART Cache, System, Data, Internal Storage and wipe by swiping right
5. Copy all files to your SD card/Internal Storage: Twrp-recoveryInstaller-3.2.1-2-oreo.zip, Google_Cam_Fix_for_LineageOS_v1.0.zip (not needed for other ROMs other than LineageOS, or at all), lineage-15.1-20180313-UNOFFICIAL-tissot.zip (or any other ROM file), Magisk-v16.4(1642).zip, open_gapps-arm64-8.1-micro-20180526.zip (Download the newest one at https://opengapps.org, ARM64, Android 8.1, micro)
6. Go to Install->and select lineage-15.1-20180313-UNOFFICIAL-tissot.zip (or any other ROM file) and install the zip file by selecting the file and swiping right
7. Reboot->Switch to the other slot (A->B or B->A) (Not needed on the latest ROMs)
8. DO NOT REBOOT (Just press the Back button)
9. Install Twrp-recoveryInstaller-3.2.1-2-oreo.zip by selecting the file and swiping right
10. Go to Reboot->Recovery and swipe
11. Install->Flash open_gapps-arm64-8.1-micro-20180526.zip by selecting the file and swiping right
12. Reboot or continue to the Magisk installation procedure below to get root access
12.5 IMPORTANT! Press Do Not Install
Your device can take a few minutes to boot
1. Reboot to recovery
1. Install->Flash Magisk-v16.4(1642).zip by selecting the file and swiping right
2. Reboot->System
3. Go to Magisk Manager->Modules->Add->Top right corner, three dots, Show internal storage and find the Google_Cam_Fix_for_LineageOS_v1.0.zip and flash it by clicking on it, reboot your device. (Not needed for other ROMs other than LineageOS, or at all)
(If you can't see your SD card because it is formatted as an adoptable storage, copy the file to the Internal Storage again)​
NOTE: MAY NOT WORK ON MOST ROMS ANYMORE, I USE VIPERFX FROM MAGISK REPOSITORY OR DIRECTLY FROM XDALABS HERE INSTEAD.
1. Copy DolbyAtmos_for_Oreo_20180218.zip and magisk-permissive-script_v1.2.zip to your SD card/Internal Storage (Currently only downloadable from the link below, please check the note just above the step 1)
(Please note that if you have your SD card formatted as an adoptable SD card, you'll have to copy your files to the Internal storage, nowhere else.)
2. Go to Magisk Manager, update it (you might need to install the latest apk by clicking on the INSTALL button, let it update before doing anything else)->Modules->Press the + button, top right corner, three dots, Show internal storage and find the magisk-permissive-script_v1.2.zip, tap on it.
3. Reboot
4. Reboot to recovery (Go to Settings->System->About Phone->Tap 7 times on Build Number, go back, Developer Options, Enable Advanced restart. Now you can simply hold the power button, press restart, tap on Recovery.)
5. Install->Flash DolbyAtmos_for_Oreo_20180218.zip by selecting the file and swiping right
(IF IT ENDS UP WITH AN ERROR->Back, go to Mount and check System) Then try flashing it again.
6. Reboot->System
(OPTIONAL STEPS, USE ONLY IF YOU DON'T SEE DOLBYATMOS AFTER REBOOT)
(In recovery)
7. Reboot->Select the other partition (A->B or B->A)
8. Back->Reboot->Recovery (Swipe to Reboot)
9. Install->Flash DolbyAtmos_for_Oreo_20180218.zip by selecting the file and swiping right
10. Reboot->Select the other partition (A->B or B->A)
11. Reboot System
1. Open Magisk Manager->Downloads->Search for GCam Mi A1 Fix->Tap, install, reboot (Please note that this is already enabled in most ROMs out here)
2. Copy the GoogleCamera-Pixel2Mod-Arnova8G2-V7beta-test-9.apk (from the Bonus folder) to your internal storage
3. Use any third-party file manager, (I recommend total commander) and install the .apk
4. Use the recommended settings:
Open the camera app->Settings->Advanced:
Config Camera HDR+: Nexus 6 Auto (This setting might not be neccesary in the provided GCam version anymore)
HDR+ parameters: Super High
Enable Zero Shutter Lag (ZSL): Enabled
Improve in low light: Enabled
5. Restart the app
1. Open Magisk Manager->Downloads->Modded Pixel2 Launcher->Tap, install, reboot (Optionally, you can install other Pixel launchers. I personally prefer Ruthless Pixel Launcher)
2. Tap on Pixel 2 Launcher
3. Press the home button
4. Always
(This sets the Pixel 2 Launcher as your default launcher.)
At this point - MAKE A BACKUP in TWRP (Boot into Recovery, select Backup, Select all partitions (except storage), Backup)
1. Download the OREO_MAGISK_Xiaomi_mi_A1_DualSpeaker.zip file from the attachment section
2. Open Magisk Manager->Modules->The + button->Find the OREO_MAGISK_Xiaomi_mi_A1_DualSpeaker.zip file->Flash it
3. Reboot
1. Download and install XposedInstaller_3.1.5.apk from the attachment section
2. Open it and click on the Xposed version 90-beta3 (or a newer version) in the INSTALL/UPDATE section
3. Install
4. You'll get an error saying that the device is busy
5. Restart to TWRP recovery
6. Install->Find the Xposed_Framework_(SDK_27)-90.1-beta3_(Systemless).zip (or a newer version) in the MagiskManager folder in the root of your internal storage (/storage/emulated/0/MagiskManager)->Flash the .zip file by swiping right
7. Reboot to system
@abhishek987 - the guide has been inspired by his guide
@mohancm - used his recovery
@talk2indrajit - used his Google Cam fix, used some steps from his guide
@Rajeev - for providing link to the latest LineageOS
@Arnova8G2 - his camera mod has been used in this guide
@sad96 - his fps fix has been used in this guide
@guitardedhero - his DolbyAtmos port has been used in this guide
@lelozerien - for letting me know about the DualSpeaker mod
@ydd0ras - for guiding me through the installation of Xposed
@coda00 - for letting me know about the version mismatch when not installing TWRP
@ravinder0003
OpenGApps taken from: http://opengapps.org
LineageOS taken from: https://forum.xda-developers.com/mi-a1/development/rom-lineageos-15-1-t3757938
GCamMod taken from: https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2/
TWRP taken from: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
DolbyAtmos taken from: https://forum.xda-developers.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508 (I've used an older version in this guide. If you are confident enough, you can try the latest one.)
Xposed taken from: https://forum.xda-developers.com/showthread.php?t=3034811
I was writing these steps while actually installing the ROM, so it should work for sure.
I might add guides for installation of other ROMs too.
If you have any issues or questions, feel free to reply to this post.
A newbie tip: If you can't see your internal storage, swipe down the notification bar and change USB Charging to Transfer Files.
Coming from stock Android 8.0? Coming from Android Nougat, 7.1.2? Do you need to reflash your TWRP?
Take a look​
If is anyone interested about the design:
HTML:
https://cooltext.com
Changelog:
HTML:
27/05/18 - Updated the guide and separated the main installation procedure.

Great work!
Thank you for your effort!

@SmallTarzan
Very nice guide. Appreciate it...
I want to ask something.. I am not a LOS fan. I won't flash too. Asking this question for some of my whatsapp friends... My question is...
They have already permanent TWRP installed. So do they need to install twrp installer again? With that A/B slot trick?

Rajeev said:
@SmallTarzan
Very nice guide. Appreciate it...
I want to ask something.. I am not a LOS fan. I won't flash too. Asking this question for some of my whatsapp friends... My question is...
They have already permanent TWRP installed. So do they need to install twrp installer again? With that A/B slot trick?
Click to expand...
Click to collapse
I'm not a developer but I'll try to answer your question as well as I can. By logical thinking and my personal experience, I've came to this conclusion: (Don't take me by word, I might not be totally right!)
If you are coming from stock, Android 8.0, you shouldn't need to flash TWRP again.
If you are coming from Nougat, 7.1.2, you'll need to reflash TWRP again.
If you are coming from other custom ROMs, you shouldn't need to flash TWRP again.
With that said,
I've always reflashed my TWRP with the latest one provided for the ROM I was installing at the moment, just in case.
About that A/B trick, when I was flashing the first LineageOS version, I needed to use the A/B partition trick.
However, in the latest one released on 13/03, I needn't. (I didn't try the version released on 8th March.)

wiping internal storage is necessary?

surajsun22 said:
wiping internal storage is necessary?
Click to expand...
Click to collapse
That depends. First, check if is your internal storage encrypted. If it is, you'll need to wipe it.
There might be workarounds on the forum, but I, personally, haven't tried those, yet.

Thanks for the guide

Sorry, what is bonus folder? And where i can find it?

arjiyunandar said:
Sorry, what is bonus folder? And where i can find it?
Click to expand...
Click to collapse
It's inside the All-in-One package. You can find the download link in the requirements section.

SmallTarzan said:
It's inside the All-in-One package. You can find the download link in the requirements section.
Click to expand...
Click to collapse
Can i download what i need? Without download the whole package? Because the size so big, ?

arjiyunandar said:
Can i download what i need? Without download the whole package? Because the size so big, ?
Click to expand...
Click to collapse
What do you need?

SmallTarzan said:
It's inside the All-in-One package. You can find the download link in the requirements section.
Click to expand...
Click to collapse
SmallTarzan said:
What do you need?
Click to expand...
Click to collapse
Google_Cam_Fix_for_LineageOS_v1.0.zip
fixed_30_60_120fps module_v2.zip
Just that,

arjiyunandar said:
Google_Cam_Fix_for_LineageOS_v1.0.zip
fixed_30_60_120fps module_v2.zip
Just that,
Click to expand...
Click to collapse
Have fun.

SmallTarzan said:
Have fun.
Click to expand...
Click to collapse
Thanks so much ?

Not sure if permissive script is needed for dolby atmos, dolby works well on my MiA1 without this script because this rom is already with permissive sellinux... Thank you for your help, it will sure be helpfull. You should try Dual Speaker mod if you haven't got it on your phone.

Is it alright to flash LOS15.1 from stock Nougat or is it a prerequisite to upgrade to stock Oreo before flashing LOS15.1?
Thanks.

lelozerien said:
Not sure if permissive script is needed for dolby atmos, dolby works well on my MiA1 without this script because this rom is already with permissive sellinux... Thank you for your help, it will sure be helpfull. You should try Dual Speaker mod if you haven't got it on your phone.
Click to expand...
Click to collapse
The magisk's permissive script isn't needed, since LOS 15.1 is already in the permissive state. However, if you'd accidentally/purposely change your SELinux status, the DolbyAtmos would break and you'd possibly face audio issues.
TheMadRuffian said:
Is it alright to flash LOS15.1 from stock Nougat or is it a prerequisite to upgrade to stock Oreo before flashing LOS15.1?
Thanks.
Click to expand...
Click to collapse
There's no need to upgrade to Android 8.0 Oreo first, you delete all files in /system anyway. You can directly flash to 8.1. Don't forget to reflash your TWRP!

I m on LOS 13-03-18 how to install Dolby Atmos separately. Can u please guide me

Rzts said:
I m on LOS 13-03-18 how to install Dolby Atmos separately. Can u please guide me
Click to expand...
Click to collapse
Follow the steps in the DOLBY ATMOS section. Copy required files to your device and start from step 4.
Download the Dolby Atmos and magisk's permissive script here: https://drive.google.com/open?id=1NL_Sq2q05L6RyZQSGsPam3HrGoEoOesY

Be carefull with dualspeaker mod if you use it with dolby atmos.
You must change the volume value manually to 80 maxi (default is 84) in the file...
Read carefully thze original post: https://forum.xda-developers.com/mi-a1/themes/mod-xiaomi-mi-a1-soundmod-dualspeaker-t3741675
You should mention it in order to prevent problems...

[Root] [Recovery] Oppo F3 Plus & R9s Plus - Twrp & SuperSU

So sorry to say this but this only method works in WINDOWS 7 and for Marshmallow ROM ONLY
Supported Devices: Oppo F3 Plus (CPH1613EX) & Oppo R9s Plus (CPH1611EX)
Caution:
Please disable Antivirus for any false Detections
Screenshots
{
"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"
}
TWRP Recovery:
1. Download Drivers and install them (Disable Signed Driver Enforcement)
https://drive.google.com/open?id=1T6MTq1upNt_yxrPD9MfOHR8vTOzRisvs
2. Download Oppo R9s Plus/F3 Plus Marshmallow Firmware (CPH1611EX_11_A.16_180106) and Extract it using Winrar/7-zip into a seperate FOLDER
https://drive.google.com/file/d/1xo-J5Pe65-fXyJbysVrAZYQ1mocfl53s/view
2.1 Also Download Oppo A57 Firmware and extract it anywhere you like
https://drive.google.com/uc?id=0B_0XnEjFCVsPWndzSnp2YTFYSkU&export=download
3. Download TWRP Recovery - Keep the recovery img in the same folder as of extracted firmware folder and make sure recovery file name is set to "recovery.img"
Twrp 3.1.1-0 (Latest) - Material Theme and Inbuilt Super SU Root available for easy rooting BUT Chinese language
Download and Extract only recovery.img and place it under firmware folder. u can delete other files.
https://drive.google.com/file/d/1gkNNx2Ik6oRF-juBDNIilDUu31w6_oI_/view?usp=sharing
To change the chinese language to english please download and flash this zip But in English language you will not get Super SU Root option to root the device from built-in twrp. you have to download SU zip now. So root directly from chinese language and then flash the english language zip to be on safe and easy side
https://androidfilehost.com/?fid=817550096634752414
Twrp 3.1.0-0 (old) (RECOMMENDED) -
Normal appearance of twrp and no inbuilt SU (sometimes it prompts to install SU, if you decline once, it won't prompt again) and totally English language. Most importantly you can flash opposite OTA updates (ozip) via this twrp
https://www.dropbox.com/sh/qbobokagdgme2oa/AABQBtKTmbwChne9z1DaayHca?dl=0&preview=recovery.zip
4. Run the MsmDownloadTool from A57 Firmware folder and you will get Session Timeout error. just ignore it and close the software
4.1. Now run MsmDownloadTool from our F3 plus firmware folder and uncheck "Reset After Download"
5. Switch off ur Mobile and Hold Vol down + Vol Up simultaneously and Plug the usb to pc
5.1 After plugging to pc, open device manager and expand PORTS section and make sure the device is detected as "Qualcomm HS-USB QDLoader 9008 (COM xx)". if not you have drivers issues!
6. Press F5, uncheck all options except Recovery and double click on Recovery option and select the recovery.img from firmware folder.
7. press Start and Flashing will be success (Green color message). press stop and unplug the usb
8. Press and hold Vol Up and Power Button and release them when it vibrates. NOW IMMEDIATELY after seeing oppo logo AGAIN PRESS Vol up + Power button to Power Off your device to prevent booting!!!! (If you fail to turn off your device, mobile will boot and will auto restore the stock recovery. so you will have to re-flash the twrp again)
9. Now press Vol Down + Power button to Enter into TWRP
BONUS - Stock Recovery & New OTA Update
Stock Recovery build: CPH1611EX_11_A.16_180106
https://drive.google.com/open?id=1u2Td1g93FwyAdPuKYNqz_iMHAYMpwrwJ
New Build Version: CPH1611EX_11_A.18_180413
Flash this zip via twrp. if it gives error 7 please ask in comment section
https://drive.google.com/open?id=1UA_DEjSQ4ESQO22VuvEpBsZhW9UepafY
else, flash this ozip from stock recovery
https://drive.google.com/open?id=1u2R65wYrLy2zqIhjww8adYWkqBjXgdq3
ROOTING
Screenshot: No more red line
Boot into TWRP by Holding Vol Down + Power Button
TWRP 3.1.1.0 - Go To Advanced option (Last but one option), Tap on last option: Super SU Root and Swipe to flash
UNROOT: just uninstall the SuperSU app to remove root
TWRP 3.1.0.0 - Download this zip and copy to storage and flash it
https://drive.google.com/open?id=1dIa9jRgh5Jy_cayM4QuOw8nL8ma574jU
UnRoot: Open SuperSU>Settings>Full UnRoot.
Note: After Rooting via twrp your device might reboot twice. dont worry. its not a bootloop. its a sign of success
XPOSED FRAMEWORK - Fix Red Statusbar Warning
Screenshot:
1. Download and add extension (.zip)
https://www.dropbox.com/s/e35zeqf619...bar FIX?dl=0
2. Boot into TWRP and flash the xposed framework zip and reboot (Reboot will take about 15mins. Please dont think its a Bootloop. Have a nap)
3. Install XposedInstaller 3.1.1 apk AND Hookcoloros_1.1_2_new.apk
4. Open ColorsOs3.0 app and make sure all the options (toggles) in chinese are Enabled or leave it as deafult or if you know chinese you can choose what you want
5. Open Xposed Framework > Modules > Enable ColorOs module that you have installed now
6. Reboot. Thadaaaa. No more Red warning statusbar
Note: Flashing Xposeduninstall zip will uninstall the xposed framework. Also, if something went wrong and gone bootloop after installing the xposed framework then use this uninstaller zip to fix the bootloop. bootloop wont occur but just telling this on safety thing
Video Tutorial:
https://www.youtube.com/watch?v=T6yQWCSLZt4
Optional:
IMEI Backup
goto twrp and backup EFS partition
you can also backup using this easy method via pc : https://forum.xda-developers.com/on...click-backup-restore-efs-oneplus-one-t3150883
CREDITS:
Xda, Baidu, bbs.7to.cn
used couple of links and very useful thread: https://forum.xda-developers.com/android/help/how-to-root-oppo-r9s-plus-cph1611-t3609586
@Rimo4099 for sharing 100% working twrp recovery.img
@john_david9000 - For sharing valuable information
@wuxianlin - He is the one who ported twrp :fingers-crossed:
@cjkimlaysico - he gave the instructions to run the msm tool (hard part)

does this have the red line on the notification bar after root anymore? recommend me sth we can do after root this phone pls ty so much ☺

verydp1 said:
does this have the red line on the notification bar after root anymore? recommend me sth we can do after root this phone pls ty so much
Click to expand...
Click to collapse
yes, Statusbar will turn into Red saying Root is enabled but i havent tried fixing by myself
However i have found a way to FIX IT <3
Please check the OP again. im updating the fix

i can't access the download link for msm download tools, help pls sir

shepherd80 said:
i can't access the download link for msm download tools, help pls sir
Click to expand...
Click to collapse
damnnn. something is not legal by sharing that specific file maybe bcoz of paid or cracked content. idk
first please try to flash with stock msmdownloadtool.exe which u get by extracting firmware. if it doesnt work then you need cracked msmdownload tool

iHeymanth said:
yes, Statusbar will turn into Red saying Root is enabled but i havent tried fixing by myself
However i have found a way to FIX IT <3
Please check the OP again. im updating the fix
Click to expand...
Click to collapse
ty so much. and btw show me sth we can do after root :fingers-crossed:
and is this similar to remove the yellow line "develope mode..." ?

verydp1 said:
ty so much. and btw show me sth we can do after root :fingers-crossed:
and is this similar to remove the yellow line "develope mode..." ?
Click to expand...
Click to collapse
show you what ? i dont understand ur first line.
yes, similar to remove the yellow line but not yellow line. just similarly red line will remove. we can also remove the captcha codes and yellow warning lines of developer options etc.. im figuring out to test in f3 plus

iHeymanth said:
So sorry to say this but this only method works in WINDOWS 7 and for Marshmallow ROM ONLY
Caution:
1. Please disable Antivirus for any false Detections
2. After getting Rooted, the statusbar will turn into Red cautioning about root access
check the screenshot
Note: Downloading Firmware is an Optional thing to Install only Recovery. If you want to install both Rom and Recovery then Download the firmware files too
TWRP Recovery:
1. Download Drivers and install
https://drive.google.com/open?id=1T6MTq1upNt_yxrPD9MfOHR8vTOzRisvs
2. Download Oppo F3 Plus Marshallow Firmware and Extract it using Winrar/7-zip into a seperate FOLDER
https://drive.google.com/open?id=0B5ZISKae4wQKeEdfbGNOT3lDa28
3. Download the Tool. zip (extract it) and Recovery.img and place it under the Firmware's FOLDER (step2)
msmdownloadTool link is down. find the cracked tool in google or crack the stock tool manually by this tutorial : techzai.com/crack-msmdownload-tool/
https://drive.google.com/open?id=13AKVz94x6w4-GaSnPTXzgCoGjwm2QqpQ
4. Switch off ur Mobile and Hold Vol down + Vol Up simultaneously and Plug the usb to pc
5. Run the MsmDownloadTool and Load the extracted Firmware from folder (.ofp)
6. Press F5, uncheck all options except Recovery and double click on recovery to Browse the recovery.img
7. press Start and Flashing will be done.
Holding Vol Down + Power Button will boot into Recovery
To Avoid Signal Loss/ IMEI Missing in future, please boot into twrp and take a backup of EFS Partition
ROOTING
Boot into TWRP by Holding Vol Down + Power Button and Flash the SU or Magisk
find the zip somewhere in xda. i will post it later. sorry
Please check the Video tutorial for this Rooting process
I will try to post a clean video tutorial. stay tuned!
FIX to Red Statusbar Warning (Screenshot)
1. Download the zip below and extract them
https://drive.google.com/open?id=1hVLLigAks6ltcHrPL21L5hqDgkUKSwv5
2. Boot into TWRP and flash the xposed framework zip and reboot
3. Install XposedInstaller 3.1.1 apk AND Hookcoloros_1.1_2_new.apk
4. Open ColorsOs3.0 app and make sure all the options (toggles) in chinese are Enabled
5. Open Xposed Framework > Modules > Enable ColorOs module that you have installed now
6. Reboot. Thadaaaa. No more Red warning statusbar
Note: Flashing Xposeduninstall zip will uninstall the xposed framework. Also, if something went wrong and gone bootloop after installing the xposed framework then use this uninstaller zip to fix the bootloop. bootloop wont occur but just telling this on safety thing
Video Tutorial:
https://www.youtube.com/watch?v=T6yQWCSLZt4
CREDITS:
Xda and Developers who made all these zips/apks
@Rimo4099 for sharing the 100% confirmed recovery.img, video tutorial, screenshot and installation steps
@john_david9000 - For sharing valuable information to confirm the source of this recovery img
@Wuxalin - according to info that John david provided me, i believe this recovery is exactly same as OPPO R9S recovery by wuxalin
Click to expand...
Click to collapse
Thank you for the mention, honestly I just said a few details only. We need people like you to shed some light on these unloved phones. XDA community thanks you heartfully for your contribution.
The only thing I can say is : Go Forth, and plant the Nougat to the ground herewith. . . . . . . . . . . . . . . . It's time for Nougat to be rooted.
Also just like to confirm that MSMDownloadTool works for Windows 10 too, as proved by this article and video : http://www.techzai.com/crack-msmdownload-tool/

john_david9000 said:
Thank you for the mention, honestly I just said a few details only. We need people like you to shed some light on these unloved phones. XDA community thanks you heartfully for your contribution.
The only thing I can say is : Go Forth, and plant the Nougat to the ground herewith. . . . . . . . . . . . . . . . It's time for Nougat to be rooted.
Also just like to confirm that MSMDownloadTool works for Windows 10 too, as proved by this article and video : http://www.techzai.com/crack-msmdownload-tool/
Click to expand...
Click to collapse
i think i have the nougat recovery. testing in progress now. will let you know
edit: tested nougat recovery of r9s/r9sk but FAILED
tested windows 10 method of flashing via MiFlash tool. flashing goes success but mobile keeps vibrating but no life
tested twrp 3.1.1.0 and 3.1.0.0. both are working fine but the latest twrp is in chinese language. will figure out to change its language
only windows 7 with msmdownload tool method is working.

Good news:
Root > Magisk v16.0(latest stable) is working flawlessly
Will update OP with magisk installation steps
note: backup ur internal memory in advance xD xD

Hi, i recently update my oppo F3 plus (CPH1613EX_11_A.18_180413 marshmallow), and i try to root it using this method, it's always boot on the stock recovery when i finish (i did step by step every single world you said).
I think that's a security renforcement about this version of colorOs, i wonder if there is a way ton downgrade to the last version without losing my data (lots of apps), because i did root it whit the version that i had once.
Thanks you

Re: So, i flashed my oppo with the msmtool that you put on your post (all images expect datauser partition), and changed the recovery image before the phone boots..... and it woorks perfectly now.
PS: dont upgrade to the version CPH1613EX_11_A.18_180413 if you want root your phone, it won't work.

EniMaX said:
Hi, i recently update my oppo F3 plus (CPH1613EX_11_A.18_180413 marshmallow), and i try to root it using this method, it's always boot on the stock recovery when i finish (i did step by step every single world you said).
I think that's a security renforcement about this version of colorOs, i wonder if there is a way ton downgrade to the last version without losing my data (lots of apps), because i did root it whit the version that i had once.
Thanks you
Click to expand...
Click to collapse
Did you uncheck "Reset After Download" option in msmtool ?

No, i didn't ; in all case i didn't let the phone boot after passing the recovery.img.
Wich version of rom do you have please ?
EDIT: when i downgrade the rom, it worked perfectly
NB: after downgrading , the first time, the phone boot directly and it was the new version (wich causes me problems) that was on it, even when i had flashing all the system

EniMaX said:
No, i didn't ; in all case i didn't let the phone boot after passing the recovery.img.
Wich version of rom do you have please ?
Click to expand...
Click to collapse
1. U need to uncheck reset after download option to not let the tool to reboot it phone into os
2. I have upgraded to a.18 build via ota 65mb and root worked. Tested with my own hands
3. Caution: if you dont CHECK userpartition in msmtool, after reboot it asks for Android password to proceed and we don't know that password. It's a checkmate. You need to wipe everything to boot
4. If you have patience please flash Magical 16.0 and test it. For me Wi-Fi is not turning on after flashing magisk.
5. I suggest you to use the twrp 3.1.0. bcoz the latest 3.1.1 does not flash oppo ota (.ozip)

Thank you for replying, can you please sent me a link for this OTA updates , beacause the one which is proposed for me on my phone weights 1.7Gb , and the only link i found is on a vientnam website wich doesn't work (probabely because i'm in algeria lol)

​
EniMaX said:
Thank you for replying, can you please sent me a link for this OTA updates , beacause the one which is proposed for me on my phone weights 1.7Gb , and the only link i found is on a vientnam website wich doesn't work (probabely because i'm in algeria lol)
Click to expand...
Click to collapse
I forgot to take backup of that 65mb Ota. Sorry. I will restore stock recovery in sometime and will download that 65mb ota
Does our oppo camera supports camera2api feature?

okay thanks you. if you are talking about the "expert mode" , yes the feature is on it

EniMaX said:
okay thanks you. if you are talking about the "expert mode" , yes the feature is on it
Click to expand...
Click to collapse
I have enabled it to check pixel cameras to work but failed.
also if ur willing to do then please enable multi window in ur rooted marshmallow (build prop and developer mode method)
I tried but no multi window option enabled in recent apps

EniMaX said:
Thank you for replying, can you please sent me a link for this OTA updates , beacause the one which is proposed for me on my phone weights 1.7Gb , and the only link i found is on a vientnam website wich doesn't work (probabely because i'm in algeria lol)
Click to expand...
Click to collapse
OTA link for CPH1613EX_11_A.18_180413 (65mb)
Can use this 65mb ota if you are in A16 or A17 build versions
https://drive.google.com/file/d/1u2R65wYrLy2zqIhjww8adYWkqBjXgdq3/view?usp=drivesdk

Pioneer XDP-300R Digital Audio Player - Root, TWRP Recovery, and Mods

{
"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"
}
I've been successful at porting over TWRP (Team Win Recovery Project) Recovery to the Pioneer XDP-300R Digital Audio Player! The recovery can be flashed directly over the stock recovery using Fastboot, or you can temporarily boot into it using fastboot.
First off, TWRP, replaces the stock recovery and allows users to backup and restore system, data, boot and other partitions on their player onto their storage or sdcards. It also can install superuser (root) access if you want that feature to allow editing and modifying of the system folder. That opens the door for additional mods.
You can also install Magisk, which is a systemless root feature that is a little safer since it does not touch your system folder, but instead patches the bootloader and then creates a layer above system that stores the mods and changes within the Magisk system in.
First off, I made system image, bootloader and recovery images of the stock 300R prior to going into this full swing. I had already rooted my device using Kingoroot but this is no longer needed and is much more safe now.
So you'll want to get the recovery first.
https://drive.google.com/open?id=1diqQ8LE-yG4b-WZFB_OPcQp2rDUp9BbV
The link in my google drive will take you to a folder where I have backups of my images. The TWRP recovery is located in the Recovery folder, along with the stock Recovery image.
Tools Needed:
Android USB drivers for ADB and Fastboot
ADB and Fastboot
Terminal or Command Prompt
Some basic knowledge on how to use these tools
Pre-Installation:
In android, go to Settings, and turn on Developer Mode. To do this, click Settings, then Device Information, then scroll to Build Number. Tap this several times until you unlock Developer Options.
Now, go back to the Settings Menu and go to the new Developer Options menu. Check the OEM Unlocking option to allow the bootloader to be unlocked.
Installation of TWRP:
1. Download the TWRP image and place it in the same folder as ADB/Fastboot tools.
2. Open a terminal or cmd prompt window and go to the folder in (1)
Code:
EXAMPLE: cd /android
3. Turn off the 300R. Then hold next track (the button closest to SD slots) and press power and let go while holding the next track button. A Penguin will appear on screen. Then let go, and plug device into computer.
4. In terminal, check to see if fastboot works.
Code:
fastboot devices
5. If it does not show a device, check your drivers! If you see a device, let's go forward!
6. Now we will install the recovery.
First we need to unlock bootloader:
Code:
fastboot oem unlock
If you are nervous, and want to verify it works, you can do a temporary test by typing the command:
Code:
fastboot boot TWRP-XDP-300R.img
This will boot directly into the TWRP recovery and will go away when you restart. But you can see if it works this way and mounts each folder correctly.
If you're ready to take the plunge, use this command:
Code:
fastboot flash recovery TWRP-XDP-300R.img
7. Once it flashes, you can always reboot into recovery by powering off. Then holding PREV TRACK (button closest to power) and power on. It'll show the penguin, and then load recovery soon after.
8. Once you see the TWRP screen youre good to go! I recommend making a System, Data, and Boot backup immediately so you have it ready. I also have the stock recovery in the folder for backup purposes too!
Root Access
When you exit TWRP, you have the option of installing SuperUser (root) access. You're welcome to install or decline it. I recommend using Magisk at this point, by looking up Magisk Manager and loading that onto your device. It'll also provide root access along with other goodies like Xposed, some adblocking stuff, and if you like, Viper4Android, and other mods.
To first start the process of Magisk, you need to unlock the bootloader. Go into Fastboot mode again on the phone, as described above, and go to command prompt:
Code:
fastboot oem unlock
This command will unlock the bootloader. In the future, you can lock it by replacing unlock with lock: fastboot oem lock
Magisk only installs correctly when you use the magisk zip file that can be downloading through Magisk Manager. This zip file needs to be flashed in TWRP Recovery. Once you do that, it'll patch the bootloader and allow Magisk to work correctly. You can verify by opening Magisk Manager in Android, and seeing if it is activated.
Once activate, you can click the menu on the left side of the Manager app, and click DOWNLOADS to find a list of modules available for use. Not all are compatible with the older Android Lollipop that is on XDP-300R, so be careful of that.
Magisk Modules
Some modules I use are:
Xposed Framework - another modding system - see below
LKT - tweaks to the kernel for battery management
Magisk Manager for Recovery Mode - Recovery command line manager (seems buggy)
SafeMode4Magisk - Boots into safe mode for disabling bad modules
Swap Torpedo - Optimizes Swap files for RAM management
Youtube Vanced - Themes and removes ads from Youtube
Greenify - adds additional features to Greenify app
Xposed Framework (now systemless using Magisk!)
Some modules I use are:
Amplify - Standalone app that needs Xposed for disabling or reducing amount of system wakelocks and alarms which greatly save battery life
Greenify - Standalone app that hibernates unused apps to save battery life and uses Xposed for additional features
Youtube AdAway - Removes ads from Youtube
BUILD.PROP MODS
The Drive Link at the top of this page has my modified build.prop in it. You can replace your existing build.prop with this if you want. Make sure you make a backup just in case!
Diverting sound away from Android OS to the DAC:
Open up BUILD.PROP in /System in your android device and look for PCM Offload
There are two lines there, that start with audio.offload...
Remove the Hash in front of each of them if they are present and that's it!
it should read:
Code:
#PCM offload
audio.offload.pcm.16bit.enable=true
audio.offload.pcm.24bit.enable=true
Also verify that this is enabled:
Code:
av.offload.enable=true

Hi ! Thank your for your work ! There are a version for the XDP-100R please ?
(sorry for my bad english)

HI, I'm thankful for your development. But is there any chances to reflash the firmware if something goes wrong?

A few days ago on my xdp300r part of the system spilled out and actually are system applications. Nothing can be installed on it, is there any possibility of restoring the original state? Restarting and recovery mode unfortunately did not help.

Thanks alot. I needed this so bad. A long time after I bought XDP300R I can only dare to use superSU to get root access and that's it. And now xposed and magisk are possible, Thank you soo much.

Hi thanks. I managed it fine. I used su as majisk would not install. Luckily I followed your advice and made a backup(I don't usually bother). I installed your build.prop and the pioneer would not boot. I have restored using twrp and changed my own build.prop so alright now. Thanks.

HI GUYS.
I am trying to unlock my 300R.
When I execute 'fastboot oem unlock' I got DENIED message.
I am stuck. Is there any hope for my player?
Daniel

gavroche33 said:
HI GUYS.
I am trying to unlock my 300R.
When I execute 'fastboot oem unlock' I got DENIED message.
I am stuck. Is there any hope for my player?
Daniel
Click to expand...
Click to collapse
have you enabled the OEM unlock in the developer setting?

I do not have option like that. My player was cleared from data, but it is still locked. I cannot OEM unlock it
Any other way?
Daniel

Grazie mille per il tuo lavoro

gavroche33 said:
I do not have option like that. My player was cleared from data, but it is still locked. I cannot OEM unlock it
Any other way?
Daniel
Click to expand...
Click to collapse
Go to setting, to Device Information, to Build Number. Tap 7 times. You get Developer Options
Back up go to Developer Iptions, select OEM Unlocking.
Re-do OEM unlocking as described in OP

Hi,
I tried to follow this tutorial but my device is not show I checked the drivers!
But still the same, is it possible to had any help ?

Since we already have an open bootloader, is there a chance to make a newer android, I propose version 9 because in newer ones you lose the ability to play some formats, it would certainly give a second life for this model

Dear XDA forum readers/members,
I have an issue with my Pioneer XDP-300R. At this stage I can only boot into it with the TWRP (TWRP-XDP-300R.img) image provided in the first post. I also have downloaded the recovery files, including the (stock?) system image (system-noxposed.img).
When I try to flash the same image from within TWRP, I can only select the "boot" or "recovery" partitions. In this screen, there is no option to boot towards a "system" partition.
If I boot from a ZIP file containing the system-noxposed.img file, I obtain either a different error which complains about a META-INF and binary not found? , or I obtain an error which (of course) writes there is too little space to write a system image in a boot or recovery partition.
My question(s) is/are: Is there any method to flash a system image towards the system partition from within TWRP, and/or how to solve the "unknown chunk type" error?
Any help would be greatly appreciated.
EDIT: The issue has been solved, but there is another problem now. When the device would not boot TWRP anymore (as in: froze at TWRP logo) I decided to look at the partitions (with dd): Now, I had made the mistake of overwriting the very first boot partition, and now the device will not power up anymore. By all means and purposes, he is hard bricked now If there is anyone who would like to help, I'd be very grateful, assuming there are still options left.
Greetings from a new member in need of help

[GUIDE] Xiaomi Qin F21 Pro mt6761 Global — Rooted with Play store

This is intended to be a guide on how to root and add play store to a Qin F21 PRO with a MTK6761 processor and 4GB/64GB. The phone I bought came with android 11 and firmware version 1.0.3 (I was dumb enough to not buy the cracked version). I will come back to this to improve the guide as I have more time, but wanted to share some broad strokes here as a way to thank all of you for the help I got from this forum, from 4pda and from various devs that did great work with tools and modules I used.
-------------------------
DISCLAIMER: I have no f****** idea of what I'm doing. My experience with Android rooting is only 2 days (REALLY!), so take this into consideration and proceed with caution.
-------------------------
I'm running a MAC (Big Sur 11.6), so I can't say for the validity of these steps on other OS, but Linux should be quite similar, and Windows too given that all tools have versions for them.
-------------------------
REQUIREMENTS
A factory reset Qin f21 pro on firmware 1.0.3 — Can't say that I recommend doing this without wiping it clean, but you could try
Python 3.9+ — I used homebrew to install (Python 3.9.12), but google is your friend here
MTK client — I used this tool to flash magisk patched boot image and to revert my bricked phone
Android Debug Bridge (adb) — I installed android-platform-tools via homebrew, but you probably already have this
Magisk 24.2 — would probably work with 24.3 but again, I DON'T KNOW WHAT I AM DOING
Android Developer options enabled and USB debugging enabled — if this is what stops you, big red flag
A Brain — goes without saying, things will go wrong and you will probably have to be creative
Magisk modules I used
MagiskHide Props Config — used to "pass as" a OnePlus N10 on google's eyes
Magisk Gapps Core — this is what installs google play store and services
Universal SafetyNet Fix (ended up not using because had to disable Zygisk, but it's worth knowing about it)
-------------------------
WHAT YOU WILL PROBABLY GET IF THINGS GO RIGHT
Rooted ROM
Play store
Happiness (this one is tricky though)
-------------------------
1. Install everything you need on you machine
Go to MTK client github page and follow the instructions to install it on your machine, do the same for android debug bridge. Downlaod Magisk apk and the modules from the links above too.
2. Backup your phone
First, we are going to backup the current state of the phone. CD into the MTK client folder and with your phone OFF and disconnected from the USB run this command
Bash:
python3 mtk_gui
This will open a GUI and prompt you to connect your phone. You should hold the OWL and RETURN keys on the keyboard while connecting it to the USB. The app will now detect your phone and do its magic.
{
"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"
}
Now that your phone is connected you should be able to dump all the partitions you need to recover it if things go wrong. I did it by selecting all partitions except "userdata" and then clicked "Read partitions". It should take a while, and when it's done you should see various .bin files for all partitions saved somewhere in your computer. Make sure you keep them safe. You can also read the readme from MTKClient on other ways to back your phone (specially for what the "Flash tools" tab is supposed to mean, but this is what worked for me).
Tip: Make sure you don't move the usb cable too much, as I noticed this may cause it to disconnect mid-way and you will need to try again.
3. PUSH THE ZIPS TO YOUR PHONE DOWNLOADS FOLDER
With that out of the way, grab all the zips and move them to your phone.
Open your terminal tool on your computer, cd to where you downloaded Magisk.apk and the 3 modules, and push the files to your phone via ADB USB with this command
Bash:
adb push /path/to/magsik.apk /sdcard/Download
Bash:
adb push /path/to/module.zip /sdcard/Download
You should have all files now on your Downloads folder — you can check by using the native files app.
4. PUSH A BOOT.img TO YOUR PHONE DOWNLOADS FOLDER
Make a copy of the boot_a.bin you just dumped, rename it to boot.img, and push it to your Downloads folder (we will use magisk on it to patch and root your device).
Bash:
adb push path/to/boot.img /sdcard/Download
5. INSTALL MAGISK AND PATCH THE BOOT.IMG
Now, on your phone, go to the Downloads folder and install magisk by clicking the apk, go through all the steps to get it running.
Open the magisk app and on the first card click the install button. On the next screen select the method "Select and patch a file". Magisk will ask you to find the boot.img file. Now you just have to wait for it to finish patching the img.
On the log you will see that Magisk has a path to where it saved the patched img. On your computer run
Bash:
adb pull path/to/magisk/patched/boot.img
This will move the patched boot to your computer which will be helpful in the next step.
6. UNLOCK AND ROOT PHONE
Before we do this, we will need to create an empty vbmeta bin file. On a mac you can do this on your terminal by running
Bash:
touch vbmeta.bin
Now, turn off your phone and disconnect from USB, run this command, and then connect the phone to the USB clicking the buttons from step 2 (this is needed everytime you connect to mtk client, so I won't repeat going forward).
Bash:
python3 mtk da seccfg unlock
Then, after you unlock it, reset the phone by running
Bash:
python3 mtk reset
Now run
Bash:
python3 mtk_gui
With the phone connected to the MTK Client GUI, you will go to the "write partitions" tab:
Find boot_a and set it to the patched boot bin file magisk generated
Find vbmeta_a and set it to the empty vbmeta.bin file you create
Click "write partitions" and wait for it to do its thing.
Bash:
python3 mtk reset
You should now be able to disconnect from USB, start your phone and see "orange state" message on top of the duoqin logo on boot.
Note about partitions: I have little understanding of how the partitions structure are supposed to work on android 11 with MTK processor, but that being said, I had to touch these partitions along the way: seccfg, boot_a, vbmeta_a, vbmeta_b, and super (these last 2, because I bricked my phone). Proceed with caution when writing to them, and with even more caution when writing to other partitions.
7. HIDE MAGISK AND DISABLE ZYGISK (BETA)
Open magisk and hide it by going to settings and click "Hide the Magisk app" — I called mine Houdini, but you can call it whatever you want.
Also, make sure you disable Zygisk on the settings (Reboot if needed).
8. Install MagiskHide Props config
Open magisk again, go to the modules tab and click "install from storage". Find the MagiskHide props config .zip file and install it. Reboot the device.
Now, on your computer, and with USB debugging connected, run:
Bash:
adb shell
This will give you access to your phones shell. Make sure you have internet access on your phone, you can then run:
Bash:
props
(su might be needed here, if so, you can allow it via magisk superuser tab)
Follow the steps from the tool to get your phone fingerprint to be OnePlus N10 5G Global BE2026. This means you will need to navigate the tool on menu options 1 and 2 to do this. Menu option 4 is defined as active by default. You will probably have to reboot a few of times along the way. Just follow what the tool says and check its docs if needed.
Docs: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf
Here is what I have:
9. Install Magisk GApps Core and hope for the best
Open magisk again, go to the modules folder and click "install from storage". Find the magisk gapps core.zip module and install it. Reboot. That's it.
Your browser is not able to display this video.
Tip: If play store keeps crashing try clearing its cache and storage by going to settings > apps > play store and clear storage
If it doesn't work, play around a bit, try different settings, maybe install Universal SafetyNet Fix, add google play store and services to Magisk's denylist and enable Zygisk, google stuff, poke around. What I described above is what worked for me.

reserved for updates — probably will never happen

wow thanks worked great.

Thank you so much for your hard work!! This works perfectly, I appreciate it!

I followed your guide through step 6, but now when I try to turn on my phone it says:
"dm-verity corruption
Your device is corrupt.
It can't be trusted and may not work properly
Press power button to continue.
Or, device will power off in 5s"
It powers off after 5 seconds, even when I press the power button.
I tried flashing the original firmware, and I'm still getting the same message.

The solution to "dm-verity corruption" on the F21 Pro is: (after following the tutorial through step 6)
1. boot into fastboot by running "python mtk payload --metamode FASTBOOT"
2. using fastboot, flash vbmeta_a.bin with the --disable-verity flag and the --disable-verification flag:
"fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta_a.bin"
3. wait until it finishes (it should be pretty quick), and then hold down the power button to reboot.
4. the device should now boot without the "dm-verity corruption" message
Sources:
I used part of method 2 from this tutorial: https://www.droidwin.com/disable-dm-verity-without-twrp/
Instructions to get to fastboot are from the README.md from https://github.com/bkerler/mtkclient

Note: In the guide, the link to download Magisk is from magiskmanager.com. This is not the official website of Magisk. The official place to download it is from https://github.com/topjohnwu/Magisk.
Edit: The link in the guide was fixed.
As per https://www.xda-developers.com/psa-magiskmanager-com-not-official-website-magisk/

Information on how to do this stuff is scarce it seems with the exception of you and some Russian website. Hopefully someone can help (I am a complete Android novice) - My device is the 3gb/32gb version and I'm not entirely sure which configuration I purchased. It was from eBay and the description gave no information other than storage and RAM. If it helps, when turned on it had Amazon App Store installed and I have the ability to download apps from browser and install directly on the phone. It shows version 1.1.1. Any chance you could advise if this ticks the boxes as it were so that I'm not walking in to bricking my phone with no knowledge or skill of how to fix it? Appreciate the help
Should also mention - It doesn't seem to have any root apps or anything like that and no google play store/services etc.

thanks for this

Hi! If anyone has the backup with partitions and doesn't mind sharing it, let me know. Thank you!

Hello, there has been an update. Now the company Duoqin itself provides its devices with official Google Play Services. Could someone who has this updated device help us get such an update?

I was also stuck after the 6th step. What solved it for me was using the `vbmeta_a` partition from this post. Thanks to @Jbazt_katuforzs

my phone bricked

I have MagiskHide Props Config, Universal SafetyNet Fix, and Magisk Gapps Core installed, but it's saying "This device isn't Play Protect Certified". Any ideas?