Hi guys,
I hope all of you are fine, now after more than one year of usage of OPPO R7Plusf which was really amazing, it seems like OPPO has no plans to upgrade our phones, when I purchased my device a ColorOS version 2.0 was installed already and recently, it was upgraded to ColorOS version 2.1.0i (based on 5.1.1 Android Lollipop). Nowadays, all of us heard about the Nougat upgrade when we still dreaming with Marshmallow!!
So please, any suggestions for a custom ROM (tested) to upgrade my OPPO phone to Nougat version with no usual known errors or bugs. I will be grateful.
Notice: I contacted both customer support (the local one and the international) and I received the usual formal disappointed answer: "we will inform you when the update is available", which I think it will not be.
So thanks
Anybody here!?
Depends what you like
I currently use Resurrection remix on mine however there are some issues with apps force closing is my main one. Lineage OS also had issues for me with bluetooth causing the phone the reboot over and over. CM 13 was the best but I can't find any download links for it any more (rip CM) I think they both have updates coming outside but I recommend trying some out and then making a decision. Also if your phone is on one of the latest oppo updates (one of the 2016 updates) you'll have to downgrade to a 2015 software as they locked the bootloader so you won't be able to root! It's easy to do just find an old firmware from the internet (I would post links but I can't, also has to be a 2015 one) turn off the phone and turn it back on whilst holding down the volume down button and then go install and install the old firmware and then follow any guides on the internet for installing custom ROMs
Hope this helped
Meroslave said:
Anybody here!?
Click to expand...
Click to collapse
Lol, yeah. There is not much traffic here, but the R7Plusf is still awesome and up to date. Mainly due to good people at LineageOS keeping the device fresh.
I don't have serious issues with AICP on Nougat. No reboots. It is build "on top of" LineageOS, but have more features plus a working theming system. Latest build uploaded today.
Try RR, AICP and LineageOS and see what you like. Wait with Lineage untill the next release (current is Feb 14), if you want to avoid reboots.
ccrocks426 said:
I currently use Resurrection remix on mine however there are some issues with apps force closing is my main one. Lineage OS also had issues for me with bluetooth causing the phone the reboot over and over. CM 13 was the best but I can't find any download links for it any more (rip CM) I think they both have updates coming outside but I recommend trying some out and then making a decision. Also if your phone is on one of the latest oppo updates (one of the 2016 updates) you'll have to downgrade to a 2015 software as they locked the bootloader so you won't be able to root! It's easy to do just find an old firmware from the internet (I would post links but I can't, also has to be a 2015 one) turn off the phone and turn it back on whilst holding down the volume down button and then go install and install the old firmware and then follow any guides on the internet for installing custom ROMs
Hope this helped
Click to expand...
Click to collapse
So, you recommend the CM13 in case it's available?
And what's the cons and pros?
teemo said:
Lol, yeah. There is not much traffic here, but the R7Plusf is still awesome and up to date. Mainly due to good people at LineageOS keeping the device fresh.
I don't have serious issues with AICP on Nougat. No reboots. It is build "on top of" LineageOS, but have more features plus a working theming system. Latest build uploaded today.
Try RR, AICP and LineageOS and see what you like. Wait with Lineage untill the next release (current is Feb 14), if you want to avoid reboots.
Click to expand...
Click to collapse
Sure I will try one of your recommendations, but all I was afraid of was the disappointed bugs after updat such as battery drain, camera errors, wifi issues ... etc. Of course my ColorOS became boring to me, but still stable with no errors
Any pros or cons for those above I will be great full
Meroslave said:
Sure I will try one of your recommendations, but all I was afraid of was the disappointed bugs after updat such as battery drain, camera errors, wifi issues ... etc. Of course my ColorOS became boring to me, but still stable with no errors
Any pros or cons for those above I will be great full
Click to expand...
Click to collapse
Battery drain on MM has improved compared to Lollipop and N has improved over MM. With 4 email accounts running (on Aqua Mail) and Location on "High accuracy", Viber messenger and other stuff running, I had not much drain on AICP 11 (MM). Drain during night with Location on "Device" was 0.5% per hour. On MM and especially N, you have many ways in settings you can fine tune battery drain. Many apps are automatically shut down when not in use. You can decide which to limit and which to keep running when phone is off. Without extra apps (as ColorOS has), you can limit what apps are allowed to do and see. All built into the system.
A final word on drain: With Googles and others services running all the time, tracking everything you do, some drain is expected. Luckily this can be turned off by you
The number one reason to upgrade in these hacker friendly times: N is updated with much improved security. Updated every month with the latest security patches.
For me, AICP 11 is error free. The latest MM builds are complete in features and practically error free. Features are still being merged one at the time on N, but is useable as is now with only some minor issues.
I have not tried RR. My guess is that it has more features than AICP, but also more issues.
Lineage is the mother of all, I expect it to be stable with a good set of features.
All the N builds have more or less issues with speaker-phone. It may or may not bother you (or the person in the other end). MM was not affected as much as N, for some unknown reason.
I use Resurrection Rom and very happy with this rom!
i am beginer
i have oppo r7 plus f. tried the auto root tool but ended up hard bricking my phone. i am a beginer and i do not have much knowledge .
want to install lineage os on my oppo r7 plus f please tell me some easy ways.
Meroslave said:
Hi guys,
I hope all of you are fine, now after more than one year of usage of OPPO R7Plusf which was really amazing, it seems like OPPO has no plans to upgrade our phones, when I purchased my device a ColorOS version 2.0 was installed already and recently, it was upgraded to ColorOS version 2.1.0i (based on 5.1.1 Android Lollipop). Nowadays, all of us heard about the Nougat upgrade when we still dreaming with Marshmallow!!
So please, any suggestions for a custom ROM (tested) to upgrade my OPPO phone to Nougat version with no usual known errors or bugs. I will be grateful.
Notice: I contacted both customer support (the local one and the international) and I received the usual formal disappointed answer: "we will inform you when the update is available", which I think it will not be.
So thanks
Click to expand...
Click to collapse
supriyo_rana said:
i have oppo r7 plus f. tried the auto root tool but ended up hard bricking my phone. i am a beginer and i do not have much knowledge .
want to install lineage os on my oppo r7 plus f please tell me some easy ways.
Click to expand...
Click to collapse
Rana, first I'm sure you have been a good phone user and your Oppo R7 plus is upto date, unfortunately this is a problem. So first thing you need to do (Assuming you have unbricked your phone) is find a older version of the genuine R7+ firmware. Preferably some time between 2015- mid2016. The reason for this is OPPO locked the bootloader on later versions, these earlier versions are what the autoroot tool was designed to work on. Once you have this firmware, flash through recovery (provided you still have genuine OPPO recovery), if not you also need to flash this. Once you have the older firmware on your phone you should be able to proceed as usual steps to install lineage on your phone using typical walkthroughs.
what to do next?
DooganAU said:
Rana, first I'm sure you have been a good phone user and your Oppo R7 plus is upto date, unfortunately this is a problem. So first thing you need to do (Assuming you have unbricked your phone) is find a older version of the genuine R7+ firmware. Preferably some time between 2015- mid2016. The reason for this is OPPO locked the bootloader on later versions, these earlier versions are what the autoroot tool was designed to work on. Once you have this firmware, flash through recovery (provided you still have genuine OPPO recovery), if not you also need to flash this. Once you have the older firmware on your phone you should be able to proceed as usual steps to install lineage on your phone using typical walkthroughs.
Click to expand...
Click to collapse
thanks for your reply
yeah i went to the ofiicial service centre for the unbricking , noy it is working fine with letest firmware . now according to you i should downgrade the firmware . but how to do it ? should i do it via oppo stock recovery? or via the local update option of system updater in the menu?
supriyo_rana said:
thanks for your reply
yeah i went to the ofiicial service centre for the unbricking , noy it is working fine with letest firmware . now according to you i should downgrade the firmware . but how to do it ? should i do it via oppo stock recovery? or via the local update option of system updater in the menu?
Click to expand...
Click to collapse
i have the same concern also. Can someone please provide a step by step instruction on how to downgrade the firmware to the old version?
supriyo_rana said:
thanks for your reply
yeah i went to the ofiicial service centre for the unbricking , noy it is working fine with letest firmware . now according to you i should downgrade the firmware . but how to do it ? should i do it via oppo stock recovery? or via the local update option of system updater in the menu?
Click to expand...
Click to collapse
bu11et said:
i have the same concern also. Can someone please provide a step by step instruction on how to downgrade the firmware to the old version?
Click to expand...
Click to collapse
Try here: https://forum.xda-developers.com/showpost.php?p=73786100&postcount=139
unlock bootloader still stuck..
Hi Guys..
First i don't know if i am posting this in right thread or not... but I need help... after lots of search i couldn't find anything to unlock my oppo R7 plus running r7plusEx_11_160922 on color os 2.1.o1 android 5.1.1.. As per my study the first thing I need to do it unlock bootloader, then do TWRP, then install any custom rom. (Please correct me if m wrong). Now please tell me how can i unlock my bootloader when I dont have access to fastboot by pressing power and Volume + key. Is there some other way. I have also tried the adb version 1.4.3 to get to the fastboot mode but it restarts my mobile to lock screen.
x_master1987 said:
Hi Guys..
First i don't know if i am posting this in right thread or not... but I need help... after lots of search i couldn't find anything to unlock my oppo R7 plus running r7plusEx_11_160922 on color os 2.1.o1 android 5.1.1.. As per my study the first thing I need to do it unlock bootloader, then do TWRP, then install any custom rom. (Please correct me if m wrong). Now please tell me how can i unlock my bootloader when I dont have access to fastboot by pressing power and Volume + key. Is there some other way. I have also tried the adb version 1.4.3 to get to the fastboot mode but it restarts my mobile to lock screen.
Click to expand...
Click to collapse
Download this rom https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0. Place it in your internal drive and flash it. It will install the ColorOS with an unlockable bootloader.
Even I'm facing the same issue. There are no such methods available on internet. I have ended bricking phone several times. Because since the last update oppo had limited tho access to bootloader. And the phone OPPO r7 plus f is quite old now so there's no people dealing with the issue. The only methods remain is to downgrade the firmware and repay the process again. Better look for some firmware version around mid 2015-2016early. I read somewhere that has access to bootloader. I haven't tried it personally but I hope the methods will work. Please let me know whatever the result is..
need your help badly
ccrocks426 said:
I currently use Resurrection remix on mine however there are some issues with apps force closing is my main one. Lineage OS also had issues for me with bluetooth causing the phone the reboot over and over. CM 13 was the best but I can't find any download links for it any more (rip CM) I think they both have updates coming outside but I recommend trying some out and then making a decision. Also if your phone is on one of the latest oppo updates (one of the 2016 updates) you'll have to downgrade to a 2015 software as they locked the bootloader so you won't be able to root! It's easy to do just find an old firmware from the internet (I would post links but I can't, also has to be a 2015 one) turn off the phone and turn it back on whilst holding down the volume down button and then go install and install the old firmware and then follow any guides on the internet for installing custom ROMs
Hope this helped
Click to expand...
Click to collapse
please pm me your email . i have an oppo r7 plus f (the international version ) and i do not have much knowledge about the rooting and installing custom recovery. and since oppo has closed the bootloader now please tell me which rom to download for downgrading( if possible please provide the link) and then how to flash the custom roms and which rom is best for oppo r7 plus? which one are you using?
DooganAU said:
Rana, first I'm sure you have been a good phone user and your Oppo R7 plus is upto date, unfortunately this is a problem. So first thing you need to do (Assuming you have unbricked your phone) is find a older version of the genuine R7+ firmware. Preferably some time between 2015- mid2016. The reason for this is OPPO locked the bootloader on later versions, these earlier versions are what the autoroot tool was designed to work on. Once you have this firmware, flash through recovery (provided you still have genuine OPPO recovery), if not you also need to flash this. Once you have the older firmware on your phone you should be able to proceed as usual steps to install lineage on your phone using typical walkthroughs.
Click to expand...
Click to collapse
Where can i find the 2015 firmware for oppo r7 plus f
Just check the link in my post above.
kishd said:
Just check the link in my post above.
Click to expand...
Click to collapse
Don't know why but the link is not working
Guys i want to root my device - Honor 6X BLN-L21. how can i do this?
after rooting my device ill be able to update my software ? i have the latest android 7 official update from huawei installed. i havent unlock the bootloader or anything like that.
thank you and soory for my english.
Follow this guide https://forum.xda-developers.com/honor-6x/how-to/root-huawei-honor-6x-install-twrp-t3671822
And for obtain your bootloader unlock code, note that the listed procedure is impossible to follow at the moment, because the necessary pages to ask for the code are unavailable on Huawei sites. But you should be able to have a work around thanks to the module available here https://forum.xda-developers.com/ho...cial-request-bootloader-unlock-codes-t3785100
I am resurrecting this thread as I have the **same** issue a year after.
I have recently aquired a BLN-L21 Honor 6x europe, with EMUI 5.0.3
This is the exact ROM version: BLN-L21C432B382
It has been rooted using dc-unlocker, but now I have some problems with rooting (that was my entire objective since start)
Compatible TWRP are scarce, I can only make it work with OpenKirin TWRP 3.1.1.0, linked in the guide above, or EliteTWRP-3.2.1.0, but this one cannot read any internal partitions, so I guess it's not very useful.
As soon as I flash Magisk-19.3.zip the device boots and asks me for a decryption password, that I clearly don't have.
So Flashing Magisk this way makes the terminal useless.
Can anyone suggest me a couple of TWRP + ROM that supports root quite well on this device?
EDIT: ouch, I defeated myself. I just tried to use SuperSU-v.2.82-201705271822 and it works like a charm on stock rom.
I wonder why Magisk makes a mess of the partition
It's November now, I'm wondering if the Mha-l29 will get the gpu turbo update or not. I was exited when they said the mate 9 was supported, but they didn't include all of the models?
huawei fake , nothing in Firmware Finder too
The Japanese version has it with the latest update. I have that version, but my device is not approved yet.
MHA-L29C636B377 here, I installed the update early through HWOTA but it seems to have been approved for the past few days now in FF. I didn't notice much difference in graphics performance to be honest. And there seems to be even more bloatware than before. I ended up going to OmniROM and graphics performance seems just as quick.
Just got updated to v380 and as far as changelog is concerned, GPU Turbo is included.
LOL, of course we in the USA will have to wait a couple months to get this one. I just got the 375/October update
yesterday.
Got mine. Via OTA. MHA-L29
And just zuuus said. Its just the same.
Im just hyped for pie because of better navigation (finger crossed).
get update to October patch MHA L29 C636 (B378)
need
mha-l29c636b377 dload
aureliolage said:
need
mha-l29c636b377 dload
Click to expand...
Click to collapse
Sorry, not sure did you already try Firmware Find and are the firmwares installable by DLOAD':
Huawei Firm Finder
Quickly, easily and freely find your Huawei phone's firmware. HiSuite Proxy's official integrated firmware finder.
www.firmfinder.ml
For the Phone Model, enter MHA-L29, Region c636 and scroll down to EMUI 8.0 firmwares.
E.g., to b378, as on the screenshot
Take the URL of the File List (e.g., open and Share the address, Copy to Clipboard), here it will be:
http://update.dbankcdn.com/download/data/pub_13/HWHOTA_hotaMigrate_900_9/13/v3/f2a0f38f024f49348c3e62f4b94008ef/full/filelist.xml
Replace filelist.xml by e.g. update.zip to download the file:
http://update.dbankcdn.com/download/data/pub_13/HWHOTA_hotaMigrate_900_9/13/v3/f2a0f38f024f49348c3e62f4b94008ef/full/update.zip
Similarly for the other two zip files:
http://update.dbankcdn.com/download/data/pub_13/HWHOTA_hotaMigrate_900_9/13/v3/f2a0f38f024f49348c3e62f4b94008ef/full/public/update_data_full_public.zip
and
http://update.dbankcdn.com/download/data/pub_13/HWHOTA_hotaMigrate_900_9/13/v3/f2a0f38f024f49348c3e62f4b94008ef/full/MHA-L29_hw_spcseas/update_full_MHA-L29_hw_spcseas.zip
Check the names and subpaths in the filelist.xml, e.g., this is also the ChangeLog:
http://update.dbankcdn.com/download/data/pub_13/HWHOTA_hotaMigrate_900_9/13/v3/f2a0f38f024f49348c3e62f4b94008ef/full/changelog.xml
Edit: I see now you asked for b377 (not b378) but it would be the same/similar
According to b377 ChangeLog, GPU Turbo comes with b377.
Be aware that it also means that Bootlader has been upgraded with the installation of b377.
Therefore, downgrading from b377 (or newer) to b376 (or older) would brick the phone
Hello, I had bought a tablet from Lenovo previousely, being Lenovo P11 which has Sm6115 qualcomm.
They did release the kernel source but for an old version of the oem firmware. As a result, it is missing drivers for newer variant of machines (They have different panels and touchscreens on newer variants) and as a result the touch screen does not work for the machine I own (Wifi variant)
Luckliy the "5G" variant of the tablet has SD765 in it but has the same touch panel (Novatek NT36523) so I tried to copy that driver to my device's kernel and I'm unable to fix this error while compiling.
This is the repo for my kernel (Yes, I did not restore git history yet because I'm lazy) : https://github.com/HexagonWin/m11_row_kernel_temp
And this is the error message : https://pastebin.com/90XAsb2X
This is 5g variant kernel : https://download.lenovo.com/consumer/mobiles/tb-j607z_opensource_tb-j607z_s130035_210706_row.tar.gz
The weird thing is that the 5g variant kernel builds properly with that same touch panel driver included in defconfig. The defconfig I'm using for my kernel tree right now is "arch/arm64/configs/m11_defconfig". Could somebody please see what is causing the issue? I'm not able to understand.. Thanks. (Including -fPIC in root makefile's KBUILD_CFLAGS didn't help.)
Correction: It's bengal (Snapdragon 662), not sm6115.
Edit: Ok it seems that sm6115 is actually bengal
You've taken the driver from a kernel source for Android 11. So either backport it or merge the kernel with an Android 11 CAF tag and use the kernel on the Android 11 firmware.
adazem009 said:
Correction: It's bengal (Snapdragon 662), not sm6115.
Edit: Ok it seems that sm6115 is actually bengal
You've taken the driver from a kernel source for Android 11. So either backport it or merge the kernel with an Android 11 CAF tag and use the kernel on the Android 11 firmware.
Click to expand...
Click to collapse
My device is not upgrade to lenovo's android 11 fw. Did you upgrade your device?
I did not upgrade yet because i was uncertain if lenovo's android 10 oss kernel would even boot on the android 11 bootloader, and i was unsure if i can revert to the android 10 firmware later on.
it can be because the android 11 caf tag's changes aren't merged, i'm not sure.. maybe we can try loading the lenovo's android 10 firmware nvt kernel module using something like ghidra and compare that with the module that gets built with the nvt driver code from another device's android 11 kernel
LegendOcta said:
My device is not upgrade to lenovo's android 11 fw. Did you upgrade your device?
I did not upgrade yet because i was uncertain if lenovo's android 10 oss kernel would even boot on the android 11 bootloader, and i was unsure if i can revert to the android 10 firmware later on.
it can be because the android 11 caf tag's changes aren't merged, i'm not sure.. maybe we can try loading the lenovo's android 10 firmware nvt kernel module using something like ghidra and compare that with the module that gets built with the nvt driver code from another device's android 11 kernel
Click to expand...
Click to collapse
Yes, I've already upgraded, but it's possible to downgrade. However, Lenovo didn't release any complete firmware package. Android 10 will boot after downgrading, but OTA updates won't work anymore. Also downgrading works only with a specific firmware package. I'll send the package ID later...
adazem009 said:
Yes, I've already upgraded, but it's possible to downgrade. However, Lenovo didn't release any complete firmware package. Android 10 will boot after downgrading, but OTA updates won't work anymore. Also downgrading works only with a specific firmware package. I'll send the package ID later...
Click to expand...
Click to collapse
Hmm, interesting.
As my device's still on Android 10, maybe I should backup the partitions (manually via dd?) and try using them later..?
Honestly I'm a bit worried about doing anything that can't be reverted because unlike my other Android-based devices this one is something i've actually bought, lol.
So, the kernel you built from your modified tree (with prima wlan included) boots on the Android 11 bootloader/firmware? The subversion of the Android 10 is significantly lower than the Lenovo Android 11 kernel AFAIK, not sure if it's just the CAF patches or anything else..
LegendOcta said:
Hmm, interesting.
As my device's still on Android 10, maybe I should backup the partitions (manually via dd?) and try using them later..?
Honestly I'm a bit worried about doing anything that can't be reverted because unlike my other Android-based devices this one is something i've actually bought, lol.
So, the kernel you built from your modified tree (with prima wlan included) boots on the Android 11 bootloader/firmware? The subversion of the Android 10 is significantly lower than the Lenovo Android 11 kernel AFAIK, not sure if it's just the CAF patches or anything else..
Click to expand...
Click to collapse
No, I haven't been able to run it on Android 11, only Android 10. Also the device doesn't use prima wlan but a kernel module in /vendor/firmware, it wasn't working because of kernel module signature checks.
adazem009 said:
No, I haven't been able to run it on Android 11, only Android 10. Also the device doesn't use prima wlan but a kernel module in /vendor/firmware, it wasn't working because of kernel module signature checks.
Click to expand...
Click to collapse
Then, even if we make the oss kernel working most people won't be able to benefit from it as most people already have android 11 running.
Maybe we might go with the mainline route instead, I remember hearing that people got the mainline kernel booting on sm6115, was on a oneplus device probably..
Any news?