yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Lum_UK:
Ok, so now I'm bricked. Can't boot into recovery and the main OS is hanging on boot. This happenned after I tried to TWRP flash one of the stock ROM images, followed by the R9S-specific SuperSU.

I have a .ofp file of an old version of the ROM and MsmDownloadTool.exe, and have got the QCom HDLoader 9008 driver loaded, but I can't get the tool to work. On Win10 it won't start and on Win7 it just says "Connect Timeout". I also have QFIL and QPST installed, but they don't seem to know how to handle a .ofp file.

Anyone got any idea what I do now?
[Android Q&A, Help & Troubleshooting] Lum_UK:
If anyone else needs to debrick, here's all the stuff you need. There's an instructions.txt inside:

https://mega.nz/#!fx8RERiT!LAfx-eHJlwtEY_Wigcrn8rb7O3oSnWJrc1-4XQTiksE

Also here's an updated version of my root script, since bricking myself and having to wipe everything means I got to test it properly! :)

https://mega.nz/#!ulVyUIjQ!fUnBhq1dwy7gYAjSyTQyhU5qlEU3vEzNFTYMOi75utE
[Android Q&A, Help & Troubleshooting] celoxocis:
Those are pretty good findings.

I think it's worth creating a seperat thread summarizing all those findings.

I will have a look in the next next or so about why my TWRP didn't work for you.

I will extract the working TWRP and see if he added anything special to make it work.

My version should have worked, that is on a unlocked bootloader. So I'm guessing his TWRP is somehow patched.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Again, copied from Mr. Wu, only he used a Chinese ungrey app that doesn't work on English OS, so a bit of Google Translate to figure out what the app does and find an equivalent.

I think this phone still has a locked bootloader, no idea how he's getting around it. In the past, on other Oppos, 3rd party stuff flashable in Stock recovery has turned up, so I wonder if they have Oppo's private key or something?

Do you have any info of which firmware files are safe to take from other Roms (NON-HLOS.bin etc) I'm hoping to try and get the radio/modem from a later ColorOS to try and fix Bluetooth & signal issues etc. but don't know which ones to rip.

Wish there was an R9* section on XDA to make things more organised.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Can anyone on an R9S still running stock firmware, have a look in about phone for me, and post up their firmware version and baseband version. I need it to know if my baseband updater actually works!
[Android Q&A, Help & Troubleshooting] Lum_UK:
Some basebands that I ripped from the Chinese ROMs, flashable in TWRP. Both seem to work with CM13. Not sure what has changed:

[2017-01-11 v-0180] - released ROM (China)

[2017-01-24 v1470] - ALPHA ROM (China)

I'm currently downloading the international firmware (Australia & Singapore) which should, hopefully, support LTE bands more suited to use outside China. Depends if the support is down to firmware or actual hardware differences. Also depends on whether I can get this ROM rooted or decrypted in order to RIP them... here goes...
[Android Q&A, Help & Troubleshooting] pancmp:
I am using r9s plus
[Android Q&A, Help & Troubleshooting] Lum_UK:
Interesting, it has the same baseband version.

I suspect, having studied the root exploit some more, that it has a reasonable chance of working on the R9SPlus, but given on the R9S it only works on one specific OS release, you may have to do a bit of trial and error. I woudn't attempt to flash TWRP though, unless you manage to get hold of the unbrick files for the R9SPlus.

Also I made a separate thread for my root tool: https://xdaforums.com/android/general/root-oppo-r9s-auto-root-tool-t3547546/post70795809 Do not use it on the R9SPlus as it will flash TWRP!
[Android Q&A, Help & Troubleshooting] mikejasonsmith:
Great work.

Hopefully we are getting close to a R9s PLUS exploit too particularly with the international Roms now beginning to surface...
[Android Q&A, Help & Troubleshooting] mikejasonsmith:
Hi all.

Does anyone know where I can Downland the Google installer for my 9s plus? I need to do a factory reset so will probably need to reinstall the whole thing????

Thanks.
[Android Q&A, Help & Troubleshooting] Lum_UK:
If it's the same as the r9s you can just search for 'Google play' in one of the Chinese marketplaces. Yes it's all in Chinese but it isn't too hard.
[Android Q&A, Help & Troubleshooting] mikejasonsmith:
Thanks for the prompt response mate.

Sorry...I'm a bit of noon with this.

Where would I find a Chinese market place?
[Android Q&A, Help & Troubleshooting] Lum_UK:
After you wipe your phone it will be a preinstalled app called "market" or similar.

I think the app then gives you a choice of 12 different ones. I just left them all ticked, did a search for Google play, then pressed buttons at random until I found the install button :)
[Android Q&A, Help & Troubleshooting] mikejasonsmith:
You are a super star!
[Android Q&A, Help & Troubleshooting] mikejasonsmith:
Hi mate.

I've downloaded Google play thanks. Is that all I need. No framework etc?
[Android Q&A, Help & Troubleshooting] Lum_UK:
Ok, I did a goodle translate of more of Wu Xianlin's Baidu repository. It turns out that this phone has a locked bootloader, so honestly I have no idea how he managed to get TWRP to work!

I've done my best to fix up the google translate of his rant, but I can't work out all of it, but here goes.

---------- Post added at 12:57 AM ---------- Previous post was at 12:53 AM ----------

Eventually an app will require google play services and you'll be prompted to install it. Until then don't worry about it.
[Android Q&A, Help & Troubleshooting] mikejasonsmith:
Thanks mate.

Such a brilliant but equally frustrating phone.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Ok, this speakerphone issue. I think the issue is in /system/etc/mixer_paths_mtp.xml. Unfortunately every change I make to this file kills my sound until I reflash CM13.

Can someone who actually knows this file give me a few pointers. I've attached both the CM13 and the Oppo stock one to this post.
[Android Q&A, Help & Troubleshooting] :
So, I'm really confused right now. Is this phone able to root and have the bootloader unlocked at this moment? If so, with custom rom installed?

Thanks.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Can't unlock the bootloader but it doesn't really matter as Mr. Wu managed to make a version of TWRP that works with a locked bootloader, somehow.

From there it looks like custom ROMs etc are all good to go,
[Android Q&A, Help & Troubleshooting] mikejasonsmith:
Anything on the 9splus yet?
[Android Q&A, Help & Troubleshooting] mikejasonsmith:
Anybody seen anything on the 9splus yet?

I may downgrade and get the r9 plus from an Oz supplier with international ROM...
[Android Q&A, Help & Troubleshooting] mikeysteele:
I know right, it seems all the good guys went to OnePlus :(
[Android Q&A, Help & Troubleshooting] UltraM8:
Can someone share stock rom system dump?? There is no way to unpack .ozip files.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Check Wu Xianlin's Baidu repository, linked earlier in the theread, he has .zip versions posted.
[Android Q&A, Help & Troubleshooting] jacksmack:
CM14

Good news. Wu Lin dropped another ROM in his Baidu folder, Lineage CM14. Direct Baidu link.

Lum_UK may have already posted this link for folks without a Baidu account but I’ll post it anyway for those that may have missed it: https://www.youtube.com/watch?v=vwcPGnSxdEA

I’ve been giving it a spin and it seems to be a bit finicky in some areas. Notes so far:

-I’m running into the same lockscreen issue I was running into with CM13. I can initially set a pattern or pin lock but after a couple reboots I get locked out. This often happens after rebooting into recovery and then booting back into Android. I’ve tried the lockscreen both with and without the fingerprint scanner and get the same results.

-Editing the build.prop in CM’s native file manager (the same thing might happen editing it in other file managers too) somehow makes the telephone cease to recognize your SIM card. I have no clue how this is happening, especially since the only value I’m changing is the dpi. Restoring the original build.prop values after editing them doesn’t fix the SIM card issue. As an alternative, I downloaded Easy DPI Changer, applied the values I wanted, and everything remained intact and working after a reboot.

-The speaker phone issue Lum_UK spotted on the CM13 ROM persists in this ROM.

Aside from that, it seems to be working ok. I’ve installed GAPPS and Viper for Nougat and haven’t as yet had any issues with either.

Again,

this is 100% Wu Lin’s work

and I’m simply relaying what I’ve found in hopes that it can be of benefit to others.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Grabbing it for people who can't DL from Baidu. I'll edit this post with links, most likely in the morning as I'm about to go to bed :)

Personally I'm not gonna try this rom. The speakerphone is still broken, and CM14 can't (yet) run xposed, so there doesn't seem to be a lot of point in upgrading.
[Android Q&A, Help & Troubleshooting] jacksmack:
CM14 MEGA

Here's the MEGA link: https://mega.nz/#!AE5F3DyS!lDdxu8I_SrDuIhVafX4-Tbkd87nOhQpROTKwWvCSfr8

The build.prop issue I mentioned earlier seems to be limited to editing build.prop with the CM File Manager's Editor. I tried it in ES File Explorer Pro and didn't experience the same missing SIM card issue.

Also, there's a file in there called fix-sensors-test.zip. After testing it out, it fixes the auto-rotate issue but breaks the fingerprint scanner. Just FYI.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Another CM13 ROM had dropped. I'm downloading it now.

I'm not entirely sure what this means. I think that his CM ROMs went into closed beta and are now being released again, and that there is also a phone variant called the R9sk, so we need to make sure we're downloading the correct version or risk bootloops.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Download link here: https://mega.nz/#!up8AHDgb!WidY9drslbrvrYdrW0MX3vBD4ekoJM5Sx-IiFSxmi24

EDIT: DO NOT USE ROM IS MISLABELLED AND IS FOR A DIFFERENT PHONE!

I dirty flashed it and it bricked my phone :( currently unbricking and going to try a clean flash.
[Android Q&A, Help & Troubleshooting] jacksmack:
I did the same thing earlier today. Was about to write and warn you to be careful (after getting an email notification that you'd written earlier) but see now that I was too late. Hopefully you'll get your phone up and running soon.

I noticed the thing with the r9sk too and did a few Google searches but only came up with non-English content. Apparently, from my Google translates, it has a different screen than our model (JCI, I think) and came out in December of last year. There's a new TWRP in his folders too but I wouldn't recommend flashing it. I tried and it bricked me.

I keep checking his folder in hopes he'll build an MIUI ROM... my attempts with patchrom have utterly failed so far.
[Android Q&A, Help & Troubleshooting] Lum_UK:
I'm unbricked and have managed to get the ROM to boot with the following procedure:

1) Flash ROM

2) Take TWRP backup

3) Unbrick phone and re-root

4) Restore only System partition in TWRP (not even kernel!)

The ROM is based on a newer version of CM as it now has the Lineage bootscreen and branding, however the speakerphone bug is STILL present, and also wireless doesn't work. I think we can conclude that this ROM is definitely for a different phone :(

i guess what we really need is to find wherever the Chinese equivalent of github is and someone who knows how to actually build Cyanogen take his work and run with it.

---------- Post added at 12:53 AM ---------- Previous post was at 12:51 AM ----------

Also as part of this, I happenned to have my phone set to warn when any app attempts to send any text message, even the stock SMS app, and guess what.

On a freshly booted ColorOS, it attempts to send out a text message right at the start of the initial setup. No idea who to or what for, but naughty naughty Oppo.
[Android Q&A, Help & Troubleshooting] tad004:
Does this process work for international versions of the R9S?
[Android Q&A, Help & Troubleshooting] Lum_UK:
No idea. No-one has tried it yet.

Try it and see?
[Android Q&A, Help & Troubleshooting] (dylanger):
[please delete]
[Android Q&A, Help & Troubleshooting] Lum_UK:
I've managed to get myself a Weibo account, and have messaged Wu Xianlin asking for the source for his CM13 ROM. Fingers crossed!

Given his criticism of Oppo for GPL violation, I'd hope he will be willing to share source. :)
[Android Q&A, Help & Troubleshooting] Lum_UK:
That exploit has been copied from this thread and my thread. It even has a screenshot of my rooting script!

I'm famous!
[Android Q&A, Help & Troubleshooting] Lum_UK:
Got a response. Translates as "CM is still a problem". So I'm guessing no new ROMs because things aren't working properly.
[Android Q&A, Help & Troubleshooting] olBlueEyes:
I might be able to help

Hi, all,

I just bought an Oppo R9s after I moved to China from the USA on February 8, and after finding out I can't change the default SMS app, I wanted to install stock android 7 onto it. I found this forum, and figured I'd extend an offer to help.

I've studied Chinese for nine years, and I may be able to help with some translation, if it would help make the issue more clear. I don't have much technical experience, but if it helps serve as a reference of my level of general computer knowledge, I am an Arch Linux user running i3 window manager (no Windows dual-boot). I have a stock OPPO R9s, and I may be willing to play guinea pig for somebody who knows what they're doing.

I spent half my day off today just reading this forum, and I may try some of the things here, but I'd like to know if there's a way to install stock Android 7 on the device (sans-Google Play, etc).

Thanks, Lum_UK and everyone else who's been active in this thread up to this point! 加油！
[Android Q&A, Help & Troubleshooting] Lum_UK:
Someone who can actually speak Chinese is going to be very useful! The offer is very much appreciated.

I'd reallp appreciate if if you could follow wuxianlin000000 on Weibo and try to see if he is publishing his source code anywhere that would be really useful. It's most likely going to be a file repository with a name like android_device_oppo_r9s and will have files with names like BoardConfig.mk inside. Other potential ones are android_vendor_oppo, propietry_vendor_oppo/r9s and msm8953_common.

He's also made a utility for decrypting Oppo's OTAs but I can't tell if he posted it anywhere.

I'm away for the weekend now, so sorry for the short and rushed reply. Thank you for offering to help!
[Android Q&A, Help & Troubleshooting] pancmp:
I actually from hk and can read both Chinese and English..just I don't have the knowledge of creating root, rom etc..I search through all Chinese web and no many are mentioning how to root or diy the oppo , maybe they are satisfied just using the coloros...

---------- Post added at 05:08 PM ---------- Previous post was at 05:03 PM ----------

To me, if a raw Android rom would be perfect
[Android Q&A, Help & Troubleshooting] Slayne123:
I have download everything that requires to root Oppo r9s. But i have no idea how to root it. Can anyone teach me step by step PLEASE!!! appreciate.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Use my tool in this thread: https://xdaforums.com/android/general/root-oppo-r9s-auto-root-tool-t3547546/
[Android Q&A, Help & Troubleshooting] jacksmack:
New update on Baidu

Wu Xianlin released a new update for our phone as well as the r9sk. I couldn't quite tell from Google translate if this will also work on the r9s+.

His new twrp recovery allows you to flash .OZIPs.

What you'll need:

Download r9s_11_a.11_170106.tar.bz2 from this folder as well as the recovery image (it's actually twrp). Also download the drivers and .reg file if you don't already have them installed as well as msmdownloadtool-0. Grab the boot image from this folder.

There's a nice little video there that gives a good visual walkthrough of what to do. It should be pretty self-explanatory. The .docx is the document he references in the video. The only thing that might not be immediately apparent is that you have to press "f5" after the msmdownloadtool is loaded to bring up the flash options.

NOTE: First time you do this, don't "uncheck all". You can substitute the "boot" and "recovery" images with Wu Xianlin's boot and recovery images just by clicking on the name field (like in the video). You can also uncheck "userdata" if you don't want to wipe your stuff. Thanks to Lum_UK for pointing this out.

CM14 as an OZIP (this update fixes the speaker phone issue Lum_UK addressed earlier). While you're in that folder, you can also download the flashable "addonsu" in the "root" folder.

For those that are new to this thread, in order to enter flash mode, turn off your phone, connect a usb cable to your computer (don't attach the phone yet), press and hold volume up and volume down simultaneously, connect your phone to the usb cable while still holding the aforementioned buttons. After that just do exactly what he does in the video and it should work just fine.

I also install this firmware package for nougat. I'm not sure if it's necessary but I thought it couldn't hurt. There's some other firmware packages available here that might resolve the speaker-phone issue for those not wishing to ride on nougat, though I haven't tried any of them and have no idea what they do.

On a side note, you can download all of these files without a baidu account by using a live linux distro like Ubuntu.

As before, this is in no way my work. Just spreading the news.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Grabbing now, and I'll mirror to make it easier for people (Baidu is sooooo slooowwwww)

BTW, to save anyone else the effort, no you can't flash that recovery.img in flashify or with dd, and trying to do the boot.img will brick your phone.

If anyone else can mirror that massive tbz2 so I don't have to wait 9 hours to get my phone back, that'd be really nice :)
[Android Q&A, Help & Troubleshooting] jacksmack:
I can upload it to mega. Just been busy so I couldn't get around to it yesterday.

---------- Post added at 01:37 PM ---------- Previous post was at 12:37 PM ----------

Here's the link to R9s_11_A.11_170106.tar.bz2

https://mega.nz/#!gRoxULIZ!dyD-dq-4WeOdNHtPTZSNIUCJogOVeBzr-StBvkeOCUY

cm14.ozip with the recovery and boot images as well as Wu Xianlin's walkthrough:

https://mega.nz/#!tQh3BJyB!6pVIAULZ6lrnQP8YiweW-tDFYtxO55CvWCs-5Mu1W8E

The other files should be easily accessible without a Baidu account on any platform (Baidu usually allows you to download files smaller 30mb without an account).
[Android Q&A, Help & Troubleshooting] Lum_UK:
How are you extracting that tar file? I've downloaded it twice and 7zip chucks up a "data error" trying to unbz2 it. Same happenned with the one downloaded from baidu

Edit: Extracted it with bunzip2 from the GNUWin32 project.

Also, I found that, unlike in the walkthrough video, I had to flash everything except userdata to get the phone to boot after flashing the custom boot and recovery, and you need to remove any existing TWRP directory (can be done from within TWRP) or the new version will reboot instead of flashing.
[Android Q&A, Help & Troubleshooting] jacksmack:
In Linux. I'm on Ubuntu Gnome. I ran into the same issue with 7zip on our other machine running Windows. With Linux, no problems, it just trucks right through it.

---------- Post added at 04:12 PM ---------- Previous post was at 03:35 PM ----------

I should've mentioned in my previous post that I did a full flash the first time to take advantage of whatever firmware upgrades the update might provide, then flashed the boot and recovery images.

Glad it's working for you!

This update fixes the lockscreen issue I was having with the previous roms. Aside from the fingerprint reader not working, I haven't spotted any other bugs/non-working features.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Fingerprint reader is working for me on CM14.

Flashing magisk gets me a "boot loader has been destroyed" error, and I had to reflash CM to fix it. This is annoying, especially with no xposed on nougat.
[Android Q&A, Help & Troubleshooting] Lum_UK:
On this new ROM the alarm clock doesn't work (no sound, vibrate only), there doesn't seem to be a way to disable the charging LED and the thing to change the colour temperature at night doesn't trigger automatically.

Anyone found a way to boot the old ROMs after using this new root and recovery?
[Android Q&A, Help & Troubleshooting] jacksmack:
That's weird. The alarm's been working for me. Did you install the mini-firmware package? I also have Viper and Dolby installed though I can't imaging that would have an effect on the alarm.

Not yet. I've wondered if that CM13 rom from 2-18 (the one that bricked both our devices) would work on this recovery with the new boot, though I haven't tried it.

BTW, you were right about the fingerprint reader. Eventually got it to work.
[Android Q&A, Help & Troubleshooting] jacksmack:
Ok, tried it. The speaker phone bug persists but you can flash the CM13 ROM from 2-18 and everything else seems to be working so far. After you flash the ROM, it'll replace the new TWRP with an older one that won't allow you to flash .OZIPs. You also won't be able to flash any of the older CM13 ROMs as they were built for the previous TWRP that we initially had through the dirtycow hack. There was a document I read awhile ago where Wu Xianlin was talking about one set of ROMs for one recovery version and a second set of ROMs for another. I'm assuming this is what he was talking about. It's sometimes hard to pin down exactly what's going on through Google translate. From what I've read, they're aim is to have a root-rom solution that works across the board for the r9s, r9sk, and the r9s+.

There's a couple other firmware packages available in the Baidu folder that might resolve the speaker phone issue on CM13, but I haven't tried them yet.

Side note, if you try to use msmdownloadtool to reflash the new boot image from the latest dump after flashing the CM13 ROM from 2-18, the ROM will just bootloop. You can, however flash the recovery image through msmdownloadtool or simply make a TWRP backup before flashing the CM13 rom and then restore the recovery after you flash the CM13 rom.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Anyone else got front camera issues with this 03/25 CM14 ROM?

Also I've been blocked from posting on OppoForums for some reason, so apologies to anyone who asked me questions on there.
[Android Q&A, Help & Troubleshooting] jacksmack:
Try this camera: https://xdaforums.com/one-e8/themes-apps/htc-sense-7-camera-lollipop-root-t3102554
[Android Q&A, Help & Troubleshooting] Goro1234:
How to extract the files with windows 7 ? Any program that working ? Please assit I am desperate to change my ROM.

---------- Post added at 03:03 PM ---------- Previous post was at 02:36 PM ----------

Jacksmack, Lum_UK, guys I have downloaded and extracted 2 folders from MEGA. They are on my computer now:

1. R9s_11_A.11_170106 - 3.5 GB big

2. oppor9s-2017-cmrootpack - 605 GB big

Can you please post quick instruction (for idiots like) what to do next step by step with numbers..

1. do this

2. do that

3. do next...

I saw the video but it is in Chinese, and I am lost... Please post some step by step instructions for dummies like me.

Your help will be appreciated !
[Android Q&A, Help & Troubleshooting] jacksmack:
Did you read my little spiel from a couple pages back? On this page, at the bottom.

As far as extracting goes, I used Linux's file-roller. You can download an Ubuntu Live DVD here, drop it onto a USB using Rufus, reboot into the Live session, choose "TRY", and then just decompress the file. You could also try Bzip2 for Windows, which is what Lum_UK used.