Related
Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
March 19,2014
Added new Version for newer CM11 nightlies
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
March 25 Note: Added zip for new versions of Commotio Rom
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk
arifqur said:
Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk
Click to expand...
Click to collapse
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later
atifsh said:
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later
Click to expand...
Click to collapse
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.
arifqur said:
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.
Click to expand...
Click to collapse
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.
atifsh said:
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.
Click to expand...
Click to collapse
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.
arifqur said:
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.
Click to expand...
Click to collapse
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.
atifsh said:
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.
Click to expand...
Click to collapse
Yup it is pretty simple. Glad this problem has been sorted out, kind-of
arifqur said:
Yup it is pretty simple. Glad this problem has been sorted out, kind-of
Click to expand...
Click to collapse
yeah flashing every time you update is a mess
atifsh said:
yeah flashing every time you update is a mess
Click to expand...
Click to collapse
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL
arifqur said:
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL
Click to expand...
Click to collapse
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone
atifsh said:
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone
Click to expand...
Click to collapse
Not all phones have this problem and also a lot of custom rom devs apply this patch directly in their roms.
I have an S3, S4, HTC One, Note 2, S2 Skyrocket, Nexus4 and none of them have this problem. Even on OGP this problem started from CM11 Jan 22, 2014 build. The Jan 21st build flashes without this issue.
Flashable zip added for new Commotio Rom Nightlies
Any chance to apply the patch to a stock rooted rom?
Thanks
Region Code
Hi can someone fix this file for region code?
nagi_007pk said:
Hi can someone fix this file for region code?
Click to expand...
Click to collapse
Sorry man.
Tried to patch it but seems to be way different in code from the rest of the roms that I have seen.
Can someone post the patch for latest cm nightlies?
nagi_007pk said:
Can someone post the patch for latest cm nightlies?
Click to expand...
Click to collapse
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based
nagi_007pk said:
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based
Click to expand...
Click to collapse
Here you go.
Hope it works
arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
just tried it latest nightly, still the same.
Hello. First of all , I'd like to apologize if my question is dumb and has already been answered... But I'm running out of ideas , i would like to install the Pure Nexus Rom because I'm on Cyanogen but the last build completely messed up my phone... And I don't know what Vendor image I should download ... I don't even know what that is... Thanks a lot for your future answers!
Rozalina340 said:
Hello. First of all , I'd like to apologize if my question is dumb and has already been answered... But I'm running out of ideas , i would like to install the Pure Nexus Rom because I'm on Cyanogen but the last build completely messed up my phone... And I don't know what Vendor image I should download ... I don't even what that is... Thanks a lot for your future answers!
Click to expand...
Click to collapse
Either use fastboot or TWRP 3.0 to flash the MMB29Q vendor before flashing the February OTA based Pure Nexus build. Check a rom's changelog to see which OTA it is based on, then flash that vendor image if need be. I must also add, several roms are based on the latest February AOSP branch which is MMB29U, the 5X MMB29Q vendor is what still needs to be installed. This is not a stupid question, you want to ask things like this to be sure you are in the know.
SlimSnoopOS said:
Either use fastboot or TWRP 3.0 to flash the MMB29Q vendor before flashing the February OTA based Pure Nexus build. Check a rom's changelog to see which OTA it is based on, then flash that vendor image if need be. I must also add, several roms are based on the latest February AOSP branch which is MMB29U, the 5X MMB29Q vendor is what still needs to be installed. This is not a stupid question, you want to ask things like this to be sure you are in the know.
Click to expand...
Click to collapse
Thank you so much for your answer ! I'm going to try that! Thank you again , I was so lost and desperate
Rozalina340 said:
Thank you so much for your answer ! I'm going to try that! Thank you again , I was so lost and desperate
Click to expand...
Click to collapse
Not problem, that's why this forum exists!
Sent from my Nexus 5X using Tapatalk
So what exactly does the vendor image do? Why do we need to update to update the ROM after a new android version is released?
am2012 said:
So what exactly does the vendor image do? Why do we need to update to update the ROM after a new android version is released?
Click to expand...
Click to collapse
From what I understand it's the drivers specific for that device, created by the device manufacturer. What I can't figure out is whether I should download those from this site of if they should be provided by the manufacturer somewhere? Like on lg.com?
macdabby said:
From what I understand it's the drivers specific for that device, created by the device manufacturer. What I can't figure out is whether I should download those from this site of if they should be provided by the manufacturer somewhere? Like on lg.com?
Click to expand...
Click to collapse
I've never used LG's website, but the vendor image is included in each 5X factory image:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
Hi and sorry for the potential newb post
Been using CM / Lineage for years and never come across an individual firmware upgrade requirement until now.
I am on Lineage nightly Feb 8th and cant go any further due to:
comparing tz version TZ.BF4.0.1-83199 to tz.bf.4.0.1-76917
assert failed: oppo.verify_trustzone("TZ.BF.4.0.1-81399") == "1"
updater process ended with ERROR: 7 error installing zip file
I have the working 1+3 TWRP installed so Is it possible to upgrade the firmware only?
Or do I have to wipe and install the latest OOS then go back to Lineage?
I downloaded OOS 41 and there is a firmware folder in there with a few bin / mbn files so kinda hoping I can somehow flash just the firmware and keep my build.
Appreciate any help....
Cheers
Gaz
Here is the latest firmware (4.0.3). Download firmware + modem and flash in TWRP before LineageOS.
Spot on - thanks Fam im sorted
Familotel said:
Here is the latest firmware (4.0.3). Download firmware + modem and flash in TWRP before LineageOS.
Click to expand...
Click to collapse
great work!thanks
Familotel said:
Here is the latest firmware (4.0.3). Download firmware + modem and flash in TWRP before LineageOS.
Click to expand...
Click to collapse
Hey there, sorry to bug you guys. Unfortunately I'm noob so I can't comment on the main LOS thread, but I have an issue that hopefully someone can help with. Originally on CM14 nightlies, without any dramas, obviously with the change from CM on LOS I've flashed the experimental build, then the LOS nightly to get started, all went fine until the change to unified requiring the firmware update. I've installed 2nd March nightly (by editing the file to ignore the trustzone version) in case it was that, but no seems not.
I've flashed the latest FW as mentioned, and the Baseband version is M8996FAAAANAQM-1.85373.1.86546.1 so it appears I'm running definitely running the latest FW (and there were no errors on install) I then reboot to system, download the latest nightly and go to install - still getting the TZ.BF.4.0.1-83199 to TZ.BF.4.0.1-85373 error.... Have I missed a step somewhere? or is this blindingly obvious and I'm a muppet?
Any helps appreciated! cheers
Same issue with the same parameters!
Z-master said:
Hey there, sorry to bug you guys. Unfortunately I'm noob so I can't comment on the main LOS thread, but I have an issue that hopefully someone can help with. Originally on CM14 nightlies, without any dramas, obviously with the change from CM on LOS I've flashed the experimental build, then the LOS nightly to get started, all went fine until the change to unified requiring the firmware update. I've installed 2nd March nightly (by editing the file to ignore the trustzone version) in case it was that, but no seems not.
I've flashed the latest FW as mentioned, and the Baseband version is M8996FAAAANAQM-1.85373.1.86546.1 so it appears I'm running definitely running the latest FW (and there were no errors on install) I then reboot to system, download the latest nightly and go to install - still getting the TZ.BF.4.0.1-83199 to TZ.BF.4.0.1-85373 error.... Have I missed a step somewhere? or is this blindingly obvious and I'm a muppet?
Any helps appreciated! cheers
Click to expand...
Click to collapse
Hi, I have the exact same issue. I've flashed the firmware to 4.0.3 and successfully installed the nightly from 08/02/2017. Now when I try to flash the nightly from 09/03/2017 I get this issue again! This time nothing helps so far.
Please, if you find a solution - let me know!
devianity said:
Hi, I have the exact same issue. I've flashed the firmware to 4.0.3 and successfully installed the nightly from 08/02/2017. Now when I try to flash the nightly from 09/03/2017 I get this issue again! This time nothing helps so far.
Please, if you find a solution - let me know!
Click to expand...
Click to collapse
Install the firmware from the Open Beta here:
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Yeah i had the same issue - open beta 12 is required for the 9th Mar build
I've spent a bunch of time trying to understand why the modem in a particular E980 doesn't work in Cyanogenmod 12. Others should benefit from my efforts.
Searching reveals several posts about the modem issue, but quite a few of the responses are either links or references that require significant background to understand.
The community consensus is that one must flash "madmack's modem" when using CM with the E980 & variants. Without it, many phones can't enter deep sleep and thus drain the battery. Others can't use the modem at all.
(Madmack's modem post: https://forum.xda-developers.com/showthread.php?t=2430456)
(Current source of CyanogenMod 12.1: http://www.cyanogenmodroms.com/2014/01/cyanogenmod-rom-lg-optimus-g-pro.html)
"Madmack's modem" is the image for the BM9615A-CEFWMAZM-3.0.113012. Some users had a driver for a CM9615A[...] variant instead. For those users, flashing the BM9615A driver allowed the phone to go into deep sleep. Hooray!
---
Unfortunately, other E980 owners have a completely different modem: the APQ8064/MDM 9x15M. In this case, flashing the BM9615A file doesn't help.
If your modem appeared as an APQ8064/MDM9x15M on stock, it appears as the BM9615A upon flashing CM12. Unfortunately, its still an APQ8064 on the inside. This makes it seem like CM 12.1 is hard-coded to the BM9615A modem. When CM tries to speak BM9615A-ese to an APQ8064, the result is "No Sim" (or rather intermittently detecting and dropping the SIM).
Flashing the BM9615A image on an APQ8064 doesn't help -- the modem can't understand itself. CM and the modem firmware may speak the same language, but the image that runs the modem isn't right for the hardware.
At least, thats what I think is happening. I would appreciate it if someone with experience could please let me know if my understanding is incorrect.
Until someone finds a way around this, those people whose modem is APQ8064/MDM9x15M on stock may want to hold off on trying the available roms. Most are based on CyanogenMod and thus can be expected to have the same problem.
I wrote this post both to consolidate information and to ask for help. Does anyone have a way of getting an E980 with a APQ8064/MDM9x15M to work with CM 12.1?
(Note: Tried Emmanuel's wild kernel. Didn't help.)
No custom ROM changes (or should change) change your modem firmware, so neither should you unless told to do for your variant.
That specific modem was for AT&T variant of G Pro and many people who upgraded to stock kitkat and then tried to flash anything else, required it. No other variant should ever use that modem - if the need arises, just reflash back to last available jellybean stock firmware.
If you have deep sleep issues on any other variant but E980, just revert your phone to stock jellybean and flash whatever you want. Never had any modem-related deep sleep issues with Jellybean base, while with kitkat base there were some issues in KK roms, but not later... that I remember. I've used E988, built ROMs and kernels for it so I should kind of know
No SIM issues were solved later in 2015? if I'm not wrong. It was just a change in LGE RIL subclass, required after cyanogenmod updated their telephony framework.
ShadySquirrel said:
No custom ROM changes (or should change) change your modem firmware, so neither should you unless told to do for your variant.
That specific modem was for AT&T variant of G Pro and many people who upgraded to stock kitkat and then tried to flash anything else, required it. No other variant should ever use that modem - if the need arises, just reflash back to last available jellybean stock firmware.
If you have deep sleep issues on any other variant but E980, just revert your phone to stock jellybean and flash whatever you want. Never had any modem-related deep sleep issues with Jellybean base, while with kitkat base there were some issues in KK roms, but not later... that I remember. I've used E988, built ROMs and kernels for it so I should kind of know
No SIM issues were solved later in 2015? if I'm not wrong. It was just a change in LGE RIL subclass, required after cyanogenmod updated their telephony framework.
Click to expand...
Click to collapse
Thanks for the reply.
I guess I'm not understanding things well. How would one change the LGE RIL subclass appropriately, assuming a move from stock JB to CM 12.1 without any modem flashing?
facepalm5 said:
Thanks for the reply.
I guess I'm not understanding things well. How would one change the LGE RIL subclass appropriately, assuming a move from stock JB to CM 12.1 without any modem flashing?
Click to expand...
Click to collapse
Which CM build are you trying to use?
ShadySquirrel said:
Which CM build are you trying to use?
Click to expand...
Click to collapse
This one: http://www.cyanogenmodroms.com/2014/01/cyanogenmod-rom-lg-optimus-g-pro.html
facepalm5 said:
This one: http://www.cyanogenmodroms.com/2014/01/cyanogenmod-rom-lg-optimus-g-pro.html
Click to expand...
Click to collapse
October of 2016? I'm pretty sure there were no 5.1.1 builds for e980 back then. Can you try SlimLP from my downloads? That's a build from February 2016.
ShadySquirrel said:
October of 2016? I'm pretty sure there were no 5.1.1 builds for e980 back then. Can you try SlimLP from my downloads? That's a build from February 2016.
Click to expand...
Click to collapse
Thanks. That does seem to make the SIM work, but with a couple of quirks.
Tapping "build number" repeatedly doesn't activate developer options. Has this been moved?
Also, the usual root method seems to be disallowed and SuperSU disappears after being installed.
facepalm5 said:
Thanks. That does seem to make the SIM work, but with a couple of quirks.
Tapping "build number" repeatedly doesn't activate developer options. Has this been moved?
Also, the usual root method seems to be disallowed and SuperSU disappears after being installed.
Click to expand...
Click to collapse
SuperSU should be available via Settings menu (if something hasn't changed with newer versions) and Developer mode is on by default if I remember correctly, if not, taping on build number 7 times should tell you 'you're a developer now' and enable it.
Intended a direct reply. See below.
ShadySquirrel said:
SuperSU should be available via Settings menu (if something hasn't changed with newer versions) and Developer mode is on by default if I remember correctly, if not, taping on build number 7 times should tell you 'you're a developer now' and enable it.
Click to expand...
Click to collapse
Thank you for your reply and the work that you have put into making this device usable.
Developer mode normally lives under Settings-> System. The Feb 6 2016 SlimLP build includes "Date & Time", Accessibility, Printing, Kernel Auditor, Check for Updates and About Phone.
Was developer mode moved somewhere else?
Naturally, I've tried tapping "build number" many times. I don't get the usual "almost a developer" and "you are now a developer" response sequence.
facepalm5 said:
Thank you for your reply and the work that you have put into making this device usable.
Developer mode normally lives under Settings-> System. The Feb 6 2016 SlimLP build includes "Date & Time", Accessibility, Printing, Kernel Auditor, Check for Updates and About Phone.
Was developer mode moved somewhere else?
Naturally, I've tried tapping "build number" many times. I don't get the usual "almost a developer" and "you are now a developer" response sequence.
Click to expand...
Click to collapse
It should be somewhere near the end of settings menu, nowhere else. I guess something got borked somehow, so you may want to reboot.
P.S. Use SlimLP build from 16.02.2016, it has some new things fixed, and refflash rebuilt kernel I've mentioned in SlimLP post.
ShadySquirrel said:
It should be somewhere near the end of settings menu, nowhere else. I guess something got borked somehow, so you may want to reboot.
P.S. Use SlimLP build from 16.02.2016, it has some new things fixed, and refflash rebuilt kernel I've mentioned in SlimLP post.
Click to expand...
Click to collapse
Thanks. I'll give it a try, but let me make sure that I understand which one. There are two mirrors on the EOL thread: basketbuild & androidfilehost.
The newest build on basketbuild is 02072016. Androidfilehost has a 021816, however there is a note in the EOL thread that 021916 shouls be deleted because it doesn't work. Is that the same as 021816 or is 021616 really the same as 021616?
Sorry, I totally forgot that my mirrors are a bit different.
You should use this one (md5sum, it's the last stable build. Don't let date scheming confuse you, I've used kind of weird build system because my machine isn't as powerful as it's needed and builds sometimes take up to two days... nightmare. Later just flash kernel mentioned in the op over after the flash.
EDIT: You may want to drop SuperSU now or use some older version (before acquisition) and freeze it from updating.
ShadySquirrel said:
Sorry, I totally forgot that my mirrors are a bit different.
You should use this one (md5sum, it's the last stable build. Don't let date scheming confuse you, I've used kind of weird build system because my machine isn't as powerful as it's needed and builds sometimes take up to two days... nightmare. Later just flash kernel mentioned in the op over after the flash.
EDIT: You may want to drop SuperSU now or use some older version (before acquisition) and freeze it from updating.
Click to expand...
Click to collapse
Thanks.
The core items seem to be OK. I noticed a few odd items within the build. Since its been on an advertising host, I'd like to confirm that the file which you uploaded hasn't been modified. Could you please share your sha256 sum (md5 has been retired for a while now) for Slim-e980-5.1.1.beta.0.15-UNOFFICIAL-20160218.zip from your own hard drive?
facepalm5 said:
Thanks.
The core items seem to be OK. I noticed a few odd items within the build. Since its been on an advertising host, I'd like to confirm that the file which you uploaded hasn't been modified. Could you please share your sha256 sum (md5 has been retired for a while now) for Slim-e980-5.1.1.beta.0.15-UNOFFICIAL-20160218.zip from your own hard drive?
Click to expand...
Click to collapse
Sorry, I had two hard drive failures in last year and a half so only copies I have are uploaded to AFH with their original MD5 sums (sum which site shows you is sum they are generating after upload; sum I've linked you is sum generated after file was created). You can compare these two if you need some reassurance, but files are uploaded by me and were used by me, too, so should be no issues if no server-side corruption happened.
ShadySquirrel said:
Sorry, I had two hard drive failures in last year and a half so only copies I have are uploaded to AFH with their original MD5 sums (sum which site shows you is sum they are generating after upload; sum I've linked you is sum generated after file was created). You can compare these two if you need some reassurance, but files are uploaded by me and were used by me, too, so should be no issues if no server-side corruption happened.
Click to expand...
Click to collapse
I can confirm the builds he has uploaded work for me, including the kernel fix for LMK which he posted this past year. ROM runs great
Hello Everyone
Since I haven't flashed any custom ROM on my device in a while (I didn't like Pie much), and I am pretty bored with OOS 5.0.8 now, I would like to roll back to Nougat OOS 4.5.1 build. I've heard from multiple sources that Nougat has much better battery life and usual UI is more fluid that Oreo ROMs. Also, a user has intrigued me by saying that games in general perform much better than oreo builds.
So, I would like to give it a shot. But, I've found out so far that it isn't as easy as flashing the OOS build on top of 5.0.8. Many websites claim that I need to flash some special nougat build that will downgrade me to nougat and then I can flash OOS 4.5.1.
So, if anyone has rolled back from 5.0.8 or 5.0.7 to Nougat before, can you please guide me through the process?
abhibnl said:
Hello Everyone
Since I haven't flashed any custom ROM on my device in a while (I didn't like Pie much), and I am pretty bored with OOS 5.0.8 now, I would like to roll back to Nougat OOS 4.5.1 build. I've heard from multiple sources that Nougat has much better battery life and usual UI is more fluid that Oreo ROMs. Also, a user has intrigued me by saying that games in general perform much better than oreo builds.
So, I would like to give it a shot. But, I've found out so far that it isn't as easy as flashing the OOS build on top of 5.0.8. Many websites claim that I need to flash some special nougat build that will downgrade me to nougat and then I can flash OOS 4.5.1.
So, if anyone has rolled back from 5.0.8 or 5.0.7 to Nougat before, can you please guide me through the process?
Click to expand...
Click to collapse
Use this https://forums.oneplus.com/threads/guide-how-to-go-from-oreo-to-stock-nougat.661713/
That's the guide I also have gone through which advised to download the special build. Now the issue is that special build link is not working anymore. That's why I can't proceed with that one
abhibnl said:
That's the guide I also have gone through which advised to download the special build. Now the issue is that special build link is not working anymore. That's why I can't proceed with that one
Click to expand...
Click to collapse
https://downloadmirror.co/Waa/O2N_OBT_15811_OXYGEN_SIGN_wipe.zip
This is a link for an op3 build found on the last page of that link i gave you
v.konvict said:
https://downloadmirror.co/Waa/O2N_OBT_15811_OXYGEN_SIGN_wipe.zip
This is a link for an op3 build found on the last page of that link i gave you
Click to expand...
Click to collapse
Yeah sorry i was the one who posted that there. I did some digging on google yesterday and found that. The thing is, now i just need to have assurance from someone who did it on 5.0.8
That guide is old af and the original poster don't even have a oneplus 3 to test it.
OP changed few things with latest firmware and i hope it won't mess with my partitions if i flash the special build. This is my primary phone so, want to be sure before I do this procedure
abhibnl said:
Yeah sorry i was the one who posted that there. I did some digging on google yesterday and found that. The thing is, now i just need to have assurance from someone who did it on 5.0.8
That guide is old af and the original poster don't even have a oneplus 3 to test it.
OP changed few things with latest firmware and i hope it won't mess with my partitions if i flash the special build. This is my primary phone so, want to be sure before I do this procedure
Click to expand...
Click to collapse
Why don't u backup your existing data elsewhere and try flashing the nougat build because I am sure there will be quite a few of them who might have rolled back to Nougat.
Jigneshg said:
Why don't u backup your existing data elsewhere and try flashing the nougat build because I am sure there will be quite a few of them who might have rolled back to Nougat.
Click to expand...
Click to collapse
You still didn't read my last post properly. I have no issues if it formats my data partition. I'm concerned about the other partitions. I don't want to corrupt my partition table because of downgrading to a lower and older firmware. That's all my concern is.
Was on Omni 8.1 > then Leaked OOS 9.0 build > Official LOS16 > then downgraded to special Nougat build > and now on OOS 4.5.1 with latest Magisk build & Tolyan's last Gcam 5 (1.015 final fix version) release.
No issues with partitions or modems/firmware.
Only back up your data and internal memory as they will be wiped out.
abdozoon said:
Was on Omni 8.1 > then Leaked OOS 9.0 build > Official LOS16 > then downgraded to special Nougat build > and now on OOS 4.5.1 with latest Magisk build & Tolyan's last Gcam 5 (1.015 final fix version) release.
No issues with partitions or modems/firmware.
Only back up your data and internal memory as they will be wiped out.
Click to expand...
Click to collapse
Thanks! That's all the assurance I needed. I shall try it next weekend when I'll be free to do so.
i bricked my phone last week i finally unbricked with this tool it was so easy all u have to do is click on msm tool exe in folder after extracting and press start and that fixed my device and flash noughat stock rom on device,it will relock bootloader though,just make sure u put device in adb mode though with vol up when conecting to pc,hope that helps was soo easy heres link https://forum.xda-developers.com/oneplus-3/how-to/unbrick-phone-msmdownloadtool-v3-0-6-t3575801