yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] jacksmack:
Can you still enter recovery?

If you're stuck in a perpetual bootloop, hold down power and volume up plus volume down at the same time. Let go once the screen turns black.

The msmdownloadtool-0 had to be downloaded from Wu Xianlin's folder: https://pan.baidu.com/s/1qXVAbDy#li...root&twrp教程&parentPath=/android/第三方ROM&page=1 you need to run msmdownloadtool-0 before you run msmdownloadtool and both of them should be in the same folder, the way he had it set up here (watch the mp4 from this folder): https://pan.baidu.com/s/1qXVAbDy#li...root&twrp教程&parentPath=/android/第三方ROM&page=1

I'm assuming you know this but just to make sure: Make sure the appropriate drivers are installed. Turn the phone off. Hold the volume up and volume down keys at the same time. Connect the phone to your computer while holding down these buttons. Launch msmdownloadtool-0, close any warning messages that might pop up, once it's open you should see that your device is recognized. Close msmdownloadtool-0 then open msmdownloadtool. Hit f5, change recovery to the recovery from the folder housing msmdownloadtool. You can also download the most recent boot image from this folder https://pan.baidu.com/s/1qXVAbDy#li...rp教程/root内核&parentPath=/android/第三方ROM&page=1 , change the name to boot, then copy it into the folder where msmdownloadtool is (overwriting any existing boot image). Then, from the dialog window that popped up when you pressed f5, change the boot image to the one in your msmdownloadtool folder. Let it install. After it finishes, you should be able to boot into recovery (the phone will automatically restart once the files have been flashed, you can either let it continue to boot into ColorOS, or you can kill the boot process by holding down vol. up and vol. down plus the power button until the phone shuts down. Then boot into recovery like you normally would.

You may have noticed but there are a bunch of updates to Flyme in Wu Xianlin's Baidu folder. I'm currently using flyme_OPPO-R9s_wuxianlin_6.7.6.13R and it works well.

Another trick, in order to get Flyme to install correctly in TWRP, especially when coming from another rom, I have to go to wipe, advanced, then select system and reformat it as ext4 and do the same thing for cache. I then select data and select repair file system. Then I go to mount, unmount and remount system, cache, and data. After that it usually installs cleanly.
[Android Q&A, Help & Troubleshooting] jacksmack:
Replied to your post yesterday but clicked the wrong button to reply. Check out the above post (on page 26, post number 260).
[Android Q&A, Help & Troubleshooting] Goro1234:
Thank you Jacksmack, the phone is working now again with Lum_Uk CM13 ROM. After numerous atempts on diferents USB ports the Tool finaly run and I have wiped the Flyme and instaled the CM 13 Rom again.
[Android Q&A, Help & Troubleshooting] bobo31:
Help

I

I sure hope u have found a way to root your R9s plus!!! I have been looking everywhere, and found very little to no help. The china sights seem to get taken down pretty fast after post. Please let me know your findings!!! Thanks for your time. I have the Chinese version dual sim. I'm in the
[Android Q&A, Help & Troubleshooting] masbz:
How to know if you have a Chinese version or International version ?
[Android Q&A, Help & Troubleshooting] milkeg:
Awesome work!

Is the speaker issue on CM13 solved ?

Has anyone tried LineageOs on the R9s ?

Thank you
[Android Q&A, Help & Troubleshooting] StellarCode Creator:
How to register an Oppo account (coloros.com)? For registration need a Chinese number, what should I do?
[Android Q&A, Help & Troubleshooting] indef:
Trying to flash my R9S Plus, have downloaded the MSM tool, the 1.7GB "CPH1611EX_11_A.01_161210.tar.bz2" file, recovery.img, and all the other bits and pieces in the guide a few pages back, however I am receiving a "flash package does not exist" error when trying to load the MSM tool.

Redownloaded the bz2 file from Dropbox, same issue. Tried from the original chinese link, same issue.

It seems all the bz2 archives I can find are corrupt - tried launching a Ubuntu LiveCD to read the different archives, says they are corrupt (unexpected end of file at exactly the same spot).

Any suggestions? Is there another flash image I can download?
[Android Q&A, Help & Troubleshooting] sebj84:
did you take the archive from my dropbox folder? i've tested it and it run fine

thread for r9s plus international: https://xdaforums.com/android/help/how-to-root-oppo-r9s-plus-cph1611-t3609586

also in my folder is a screenshot of the file i've used to root. please compare the size of your downloaded file with the screenshot. if it is the same size there should be no issue
[Android Q&A, Help & Troubleshooting] indef:
Yes I downloaded it from the Dropbox link in your post. File size is exactly the same - 1,787,204,324 bytes.

Have tried another PC just in case, issue remains.

Any chance of unpacking the TAR file, repacking it to a ZIP, then I will download the ZIP and repack it to TAR? I assume the MSM tool looks for the TAR file not the BZ2 file...?
[Android Q&A, Help & Troubleshooting] indef:
I appear to be having a little more luck now.

I have loaded up a much older version of Ubuntu as a LiveCD on an older PC, and it seems to be extracting the files fine now - so far around half way through extraction after approximately an hour.

Will keep you posted on the progress - really looking forward to TWRP recovery, rooting the phone, Xposed framework, and a different launcher. The specs of the phone are ideal for me, however the factory software is the sore point! Glad it can be rectified!
[Android Q&A, Help & Troubleshooting] indef:
Success! TAR file has been extracted, MSM tool now working, only issue is I need to wait for the phone to charge as it went flat overnight :( Kept wondering why I was getting a "connection timeout" error message when loading the MSM tool...

---------- Post added 7th July 2017 at 12:16 AM ---------- Previous post was 6th July 2017 at 11:31 PM ----------

Ok it seems I have hit another issue.

Phone has plenty of charge in it (approx 40%), but the MSM tool still gives me the "connection timeout" error when launching. It shows the main program, I can see COM4 is 'Connected' (this is the COM port the Quallcomm QDLoader has assigned itself) but all buttons except for Exit are greyed out.

Suggestions?
[Android Q&A, Help & Troubleshooting] indef:
Phone is fully charged, made sure USB debugging was off, phone is otherwise left how it came out of the box, but I still get "Connect Timeout" when I launch the MSM tool, even though it shows the phone being connected via COM4.
[Android Q&A, Help & Troubleshooting] ulad3:
1 turn off the pod( hold vol+ vol - and power for 10 sec. until vibration)

2 hold the vol+ vol - and plugin the usb cable (on the forums write plug the cable into the OPPO from the kit but I did I used xiaomi r4pro)

in device Manager the com ports tab you should see a device qualckom.

3 MsmDownloadTool run under admin (right click "run as administrator")

4 I get an error, click OK

5 will appear in the workspace MsmDownloadTool

6 DaanavEnabler run under admin (right click "run as administrator")

7 BypassMDT run under admin (right click "run as administrator")

8 click on the program BypassMDT in the space with the left mouse button and then presses F6 ( activate the start button, refresh, etc.)

9 next, click in the open window BypassMDT left the bottom button ( in the empty field, the numbers will appear ( do not know what's they mean))

10 in BypassMDT hit F5 again falls out of the window with checkboxes of file firmware (note to myself)

11 click OK

12 we wait for minutes 5 - 10 look like a colored line flashed firmware

13 in the status field comunication is to write Download Success (body ribotide and loaded into the initial launch of Profit!)
[Android Q&A, Help & Troubleshooting] indef:
Had to Google the software to find it and download it, that was not a drama, got that all going ok.

I got as far as Step 10. Hit F5 in BypassMDT and nothing happened.

Tried F5 in the MSM tool, same screen as always so I selected nothing but boot.img and recovery.img, still cannot start flashing.

Here is a screenshot of as far as I was able to get:

---------- Post added at 10:39 PM ---------- Previous post was at 09:49 PM ----------

Tried again after have a quick read of the PDF file included with the BypassMDT application, managed to get the MSM tool to unlock all the buttons so I am making progress! Will update my post with results later. Thank you for the further instructions!

---------- Post added at 10:45 PM ---------- Previous post was at 10:39 PM ----------

Ok, few more issues... I cannot choose the path for the recovery.img, neither left click or right click, double click or any click anywhere in the F5 popup allows me to choose a custom path for the recovery.img.

Also, after hitting Start, nothing happens at all, it just sits there. I've left it for a while, status bar still says Idle, phone is completely blank, it does not appear to be doing anything at all?
[Android Q&A, Help & Troubleshooting] sebj84:
so my files are working? but not under new computers?

i used ubuntu 14.04 (zorin 9). you? just as info for my own thread on the r9s plus
[Android Q&A, Help & Troubleshooting] indef:
Correct - the ROM files are now working after using a different computer to download the files thru an older version of a Ubuntu LiveCD. My issue now is that I am unable to start flashing with the MSM tool, as pressing the Start button at the top of the application does absolutely nothing. I would try within WINE on Ubuntu, but Ubuntu does not have Quallcomm drivers :p

---------- Post added at 11:23 PM ---------- Previous post was at 11:14 PM ----------

Have installed VirtualBox on my PC, going to try with a completely fresh installation of Windows 7 on a virtual machine. Lets see if I get any luck from that, fingers crossed!
[Android Q&A, Help & Troubleshooting] indef:
Still not working on a freshly installed Virtual Machine :(

Launching the MSM tool without the BypassMDT still has all the buttons greyed out, so followed your guide again and was able to get the buttons to work, however clicking Start still does absolutely nothing. Refresh seems to also do nothing, Verify works, Exit works, not sure about the Stop button as there is nothing to stop.

---------- Post added at 01:24 AM ---------- Previous post was at 12:40 AM ----------

Perseverance is key! Got there in the end!

Searched for a cracked version of the MSM tool, came across this -- http://niu57.com/p/d/807819722226745

Clicked the blue box near the top, took me to a baidu link. Downloaded the file from baidu using my Ubuntu LiveCD, reboot back into my Windows 7 Virtual Machine, launched the freshly downloaded cracked version of the MSM tool (saved in the same folder as the ROM files), which found the ROM files fine and was able to flash the phone as per your original instructions using the cracked MSM tool instead!

Happy days! Many thanks for your assistance and patience with trying to root my new phone!
[Android Q&A, Help & Troubleshooting] sebj84:
thats great will add this tool to the download. thanks for the link. hope this helps everybody.
[Android Q&A, Help & Troubleshooting] rdazevedo:
lineage 14.1 update avaiable!!! I hope the GPS problem has been fixed.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Anyone got the new lineage to work? My phone won't boot with it installed.

E: NVM. It's SuperSU that broke my phone, presumably because it was trying to be systemless. Flash SuperSU from the TWRP prompt, not the flashable ZIP.

E2: GPS and SIM cards not working. Don't bother with this ROM.

E3: Flashed the latest FlyMe before this, seems to have resolved the SIM and GPS issues. At lleast it's managed to lock 3 satellites and is showing others. It's chucking it down with rain so I'm not gonna go outside and get a full lock :) Speakerphone works too!

E4: Home button doesn't work. Can't find a way to enable soft buttons either.

E5: Rebooted and now SIMs don't work either. Sod this I'm going back to CM13
[Android Q&A, Help & Troubleshooting] rdazevedo:
[MENTION=4657592]Lum_UK[/MENTION],

I have installed the latest version of the lineage and it is working perfectly. The only problem that persists is the GPS issue. I installed the addonsu from the root folder and enabled root through the developer settings. And also installed the audio patch. It's all working ...

As I did a dirty install, the first boot took a long time because I had quite a few apps on my phone. Something around 8 to 10 minutes
[Android Q&A, Help & Troubleshooting] edmax:
hi guys,

Need some advice (i read the entire thread but was a little confused...sorry)

I have a R9s (CHP1607). Can i use these technique and CM13 for this model? Thanks in advance.
[Android Q&A, Help & Troubleshooting] indef:
Whats the chances of me being able to flash this CM13 ROM built for the R9S to the R9S Plus, the CPH1611? I noticed on the Lineage OS stats page that one person has manged to get the ROM onto their R9S Plus, but I cannot find any traces anywhere of how it was done or where to download the appropriate ROM...

Not sure what the hardware/chipset differences are between the two models, hopefully not too much!!
[Android Q&A, Help & Troubleshooting] Lum_UK:
Tried that CM14 ROM again, this time as a dirty flash. Doesn't work.

Also, there's a Lineage 15 folder appeared on Baidu, but it just has this text file...

I guess we're gonna be stuck at Nougat for the foreseeable future.
[Android Q&A, Help & Troubleshooting] trillagorilla:
Found a working root for the oppo r9s?

[IMG="1st way"]https://i.stack.imgur.com/L7bSE.png[/IMG]

[IMG="2nd way"]https://i.stack.imgur.com/XXwdh.png[/IMG]

I hope this help you guys out.
[Android Q&A, Help & Troubleshooting] Lum_UK:
So someone made a tool to decrypt OZIPs: here it is! It's linux-only but Windows 10 users can use the Ubuntu on Windows thingy and it works fine.

Here's a flashable firmware package I ripped from the latest international firmware: Download

I attempted to make a zip that flashes the full international ColorOS, but it hangs on transferring system.new.dat and I have no idea why, but maybe someone can fix it: Download
[Android Q&A, Help & Troubleshooting] edmax:
tried to flash the Chinese OS release 005 to my R9s (CHP1607)...failed using stock recovery.

failed using iRoot and Famaroot.

Any idea or suggestion???
[Android Q&A, Help & Troubleshooting] Lum_UK:
I log that CM14.1 ROM working on my R9S without any significant bugs. SIMs, GPS, wifi, data, camera etc. all working. Only bug I have is that the 'long press back to kill' option reboots the phone, so I disabled that feature.

1) First I bricked my phone trying to install the ColorOS3.1 beta. Don't do this as it attempts to encrypt userdata and fails trashing your data. If you start using the ROM, TWRP can't read the userdata partition any more. You may want to skip this stage and go straight to stage 2.

2) Go through the original rooting procedure and flash everything. Instead of boot.img use boot-20170603.img (I have no idea if that last part matters, but it's what I used)

3) Flash Lineage, audio.zip, addonsu and gapps, optionally flash one of the dodgy xposed ports doing the rounds. Don't use SuperSU, don't let TWRP flash SuperSU.

That's it. It works.

Now if anyone knows how to install magisk non-systemlessly, That'd be awesome.

---------- Post added at 02:38 PM ---------- Previous post was at 02:37 PM ----------

I've not kept up with this thread in a while, but have you tried the method using MSMDownloadTool that's earlier in this thread?
[Android Q&A, Help & Troubleshooting] Lum_UK:
Ok, that lineage 14 ROM still isn't perfect. Front camera crashes, and the fingerprint reader has a bug where it takes you to the launcher when you try to add new fingerprints, or get a failed read. ffs.
[Android Q&A, Help & Troubleshooting] vaskas:
Have you noticed any difference in camera performance vs ColorOS?

Are you using encryption? Do you think there is any risk trying to enable it?
[Android Q&A, Help & Troubleshooting] Lum_UK:
I use the ColorOS camera app that someone ported to use with OnePlus CM, but the same bug is there with the CM camera app too.

Not using encryption, but when ColorOS 3.1 tried to encrypt my phone, this TWRP couldn't decrypt it, so best to leave it off.
[Android Q&A, Help & Troubleshooting] edmax:
i am quite confused after reading previous threads...not sure if those methods or for R9s or R9s Plus. is there a step by step for R9s?
[Android Q&A, Help & Troubleshooting] Lum_UK:
All of my posts have been R9S (China version) but yeah there's effectively 4 phones being discussed in this thread :(
[Android Q&A, Help & Troubleshooting] StellarCode Creator:
Hello, I need a tester for a custom rom for Oppo R9S(china ver.). Example roms: Miui 9(Android 7.1) - not patchrom Miui, AOSP Based(7.1), LineageOS Based, etc.
[Android Q&A, Help & Troubleshooting] adjie_sprynt:
how to flash zip file stock rom?

I already decrypt ozip file, but I can't flash it over stock recovery oppo.

need flash tool or can use TWRP recovery to instal.
[Android Q&A, Help & Troubleshooting] venezolano69:
Download you have a download link for lineageos 14?
[Android Q&A, Help & Troubleshooting] romfury88:
Can't manage to connect to device

Hi, I'm trying to follow instructions of post #150 and #152 to flash my Oppo R9s, but running Windows 7 64-bit, the MsmDownloadTool keeps waiting for the device and doesn't do anything. I do plug the device pressing Vol+/Vol- and see it appear as the QDLoader 9008 in COM10, but I don't get past the waiting for device state.

Is there anything I can do?

EDIT: Today I reinstalled Windows 7 and basic drivers. I followed Lum_UK's https://xdaforums.com/showpost.php?p=70778184&postcount=107 debrick instructions, but the download tool crashes every time I try to start the flashing.

Using the other update linked before, the one with the R9s_11_A.11_170106.ofp file I get to start flashing but press the start button and the UI sits there doing nothing, no progress bar, no visual feedback of doing much. This time, however, the column showing the status of the device does show "connected" when I plug in the device, which is a step forward, I guess.

I'm really confused by all the variants of the msdownload tool, is it that hard to make one which works? Every download post seems to have a different new one, so I wonder if by downloading files individually I mixed some of them.

EDIT2: Ok, here was the problem: when the download tool is unlocked through the F6 shortcut of DaanavEnabler.exe the start button just doesn't work. Looking at the log files generated I saw that the verification button worked (it was being logged), but the start button didn't. So I started to click everything, like radio buttons back and force, checks on/off, and then when I hit start the download started and the phone was flashed.

Thanks to R9s_11_A.11_170106.ofp I was able to restore the OS, then use system updates to bring the software up to version R9s_11_a.22_170603. The only downside is that this is a chinese rom so I had to install google play separately and figure out the chinese keyboard a little. Does anybody have an original ROM for international users?
[Android Q&A, Help & Troubleshooting] hungleung:
github.com/wuxianlin/android_device_oppo_r9s

github.com/wuxianlin/android_vendor_oppo_r9s

wuxianlin.com

weibo.com/wuxianlin000000
[Android Q&A, Help & Troubleshooting] Lum_UK:
I've attempted to get the international version of ColorOS to work on the Chinese R9S without success. Short of a custom ROM there's not much you can do. Installing a third party keyboard and launcher (e.g. Kika Keyboard and Nova Launcher) helps a lot, especially paid Nova Launcher as then you can hide all the China-specific apps.
[Android Q&A, Help & Troubleshooting] ithehappy:
Fellas I am looking for the decrypt app which was made to extract the ozip format of OPPO firmware. I need to extract something from one OPPO firmware, I don't or won't have any OPPO phone so pardon my amateur query. I haven't gone through all the pages either.

I am a Windows user if that matters.
[Android Q&A, Help & Troubleshooting] Lum_UK:
Unfortunately the decrypt app is Linux-only, but if you are running Windows 10, you can install Windows Subsystem for Linux which is sufficient to run the decrypt app.

Go to Control Panel -> Programs and Features -> Turn Windows Features on or off, and enable Windows Subsystem for Linux.

If you are on the Fall Creators Update, there is an additional step, go to the Windows Store and install Ubuntu. This step is not needed on Anniversary Update or Creators Update

Then you can run bash.exe from the start menu and it'll set you up a nice little Linux command prompt. You can grab the tool here: https://xdaforums.com/android/software/cofface-oppo-ozip2zip-tool-t3653052
[Android Q&A, Help & Troubleshooting] Lum_UK:
So since Wu Xianlin's sources for CM13 are available, I decided to build the latest CM13 using them

So far it works, has the exact same bugs as Mr. Wu's CM13 (speakerphone, slightly janky lockscreen after boot), but otherwise seems fine. Only real reason to install mine over his is it brings you the latest bugfixes and security patches up to 1st October. Oh, and my installer doesn't trash your recovery, which is a bonus. Dirty flash seems to work fine. So far it feels a little smoother too, but this could be placebo effect.

[Download]
[Android Q&A, Help & Troubleshooting] Lum_UK:
I see your github has an R9S kernel in it. Does this work, and does it fix the audio problems in CM13? :)
[Android Q&A, Help & Troubleshooting] ithehappy:
Thanks for this, but as I possess zero idea about Linux, so it might take me some time to figure out what I need to do just to even do something as easy as running the decrypt app LoL.

In any case I am doing this all just to extract one app from OPPO firmware, Swype keyboard, OPPO phones used to come with a built in Swype keyboard, so anyone using a latest firmware on their OPPO can confirm me whether Swype keyboard is still built in to the firmware? And if possible kindly mention the version no. of it? I will be really grateful then.
[Android Q&A, Help & Troubleshooting] hungleung:
It's not my github, I think the owner is wuxianlin.

Just put the link there for your guys reference

---------- Post added at 01:05 AM ---------- Previous post was at 12:57 AM ----------

I don't have any experience to build the CM, after some search I tried some times but failed.

Would you please share your method and steps of building this latest CM13 at your convinience?

Thank you.
[Android Q&A, Help & Troubleshooting] DigitalMadness:
Anyone that has any idea what the issue is in my post in the R9s Plus forum?

https://xdaforums.com/showpost.php?p=74121270&postcount=94
[Android Q&A, Help & Troubleshooting] Lum_UK:
I followed this guide, but modified roomservice.xml to include Wu Xianlin's two repositories.

You don't need to build it though. I did one yesterday and posted it ready for folk to flash. Using it on my phone now and so far it seems fine.

---------- Post added at 05:51 PM ---------- Previous post was at 05:44 PM ----------

I meant this one :)

https://github.com/hungleung/android_kernel_oppo_r9s
[Android Q&A, Help & Troubleshooting] hungleung:
yes, that's mine. the source is from wuxianlin. and this is the result of my learning of how to use github.

no use for others.

and the guide you followed, i think you missed the link.

I just want to learn how to build lineageos for unsupported device

and now i'm following the lineageos wiki to build the os for r7plus step by step
[Android Q&A, Help & Troubleshooting] Lum_UK:
Ooops, sorry about that :)

https://xdaforums.com/chef-central/android/how-to-build-lineageos-14-1-t3551484

In addition to what's in there you'll need to edit ~/androyd/system/.repo/local_manifests/roomservice.xml and add links to someone's github repos for the r7plus.