Develop Bugs

Wifi Region code Connectivity problems: A Solution

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.

Updating twrp without a pc ?

My laptop blew up a capacitor, i have twrp 2.6 x x i we need 2. 7 x x for cm11. Is there a way to update without a pc ?

Download it on the kindle, flash the zip from inside of twrp, reboot into twrp again and you will notice the version is newer. If you have issues downloading the zip on your kindle just tell me I could temporarily host it somewhere for ya.
Sent from my Amazon Kindle Fire HD using Tapatalk

aakashba1001 said:
My laptop blew up a capacitor, i have twrp 2.6 x x i we need 2. 7 x x for cm11. Is there a way to update without a pc ?
Click to expand...
Click to collapse
you can download HashCode's TWRP Here:
http://forum.xda-developers.com/showthread.php?t=2218802
and install from your current TWRP, just as you flash a ROM.

Thanks guys
thanks both of ya, one last question.
for the official cm11 release, the nightly mean u guys keep wiping and installing new os everyday ?
Is there any older release with no bugs ? If they did nightlies for older versions, one of them must have all bugs fixed right ?

aakashba1001 said:
thanks both of ya, one last question.
for the official cm11 release, the nightly mean u guys keep wiping and installing new os everyday ?
Is there any older release with no bugs ? If they did nightlies for older versions, one of them must have all bugs fixed right ?
Click to expand...
Click to collapse
CM nightly build works good for me, you don't need to wiping new buld everyday, just choise one.
CM team will release a new month build every month, that build will be better than nightly build.
It takes time for the CM team to build a ROM with no bugs, so, just be patient.

I installed the 4/14 unofficial CM11 build that Hashcode posted over in development and am stunned at how well it works! I'll be sticking with this one for the interim. The TWRP upgrade is necessary, but Hashcode made it easy (see link in gatalon's post). In my case, I think it may have even fixed a long standing issue I had.
I've had my kindle HD 8.9" for over a year now, and have always been disappointed with it's performance. Even after I rooted it and put the CM10.1 build on it, it still exhibited weird sluggish, unresponsive behavior. This upgrade to TWRP 2.7 and CM11 has made all the difference in the world. All the weird sluggishness is magically gone.
It was noticeable as soon as I used TWRP 2.7 to wipe everything out. I'm half suspecting I had something wonky going on with the file system that wasn't getting addressed with the older version of recovery. I noticed 2.7 explicitly states that it's calling mkfs during the wipe process where the older version didn't. My uneducated theory is that the older version, 2.6.0.0, just deleted everything where the newer version is actually re-formatting the partitions. I could be way off base though. Just happy it's finally working like I thought a piece of hardware like this should! :victory:

aakashba1001 said:
thanks both of ya, one last question.
for the official cm11 release, the nightly mean u guys keep wiping and installing new os everyday ?
Is there any older release with no bugs ? If they did nightlies for older versions, one of them must have all bugs fixed right ?
Click to expand...
Click to collapse
No wipe is needed (normally) when updating from one CM official nightly to a subsequent one. It will even detect if the engine has changed and recompile the davlik cache as needed. Personally, I'm a big fan of wiping cache (and only cache) with each new build and I also install any update PA GApps when available ( http://forum.xda-developers.com/showthread.php?t=2397942 ).
Caveat emptor: The CM team makes ever effort to make builds backwards compatible, but always take a backup and be prepared to do a factory reset / data wipe. It very rarely is needed, but you don't want to need a backup and not have one!

If the problem hasn't already been solved, here is an alternative: fireflash. Look it up.
Sent from my Amazon Jem using Tapatalk

[ROM][LineageOS 13][Marshmallow][6.0.1][MOB31K][Mar.18.2017][XT907][JBBL][Share]

Unofficial LineageOS 13 (Android Marshmallow) for JBBL dated March 18, 2017 from the 4PDA forums courtesy of developer ilichva!
Again, this is only for JBBL. Flash at your own risk and please do a nandroid backup prior to doing so!
All credits and thanks go to the original developer ilichva!
____________________________________________
Latest Build - LineageOS 13:
lineage-13.0-20170318-port-ilichva-xt907_jbbl.zip (405.4 MB)
Mega
SolidFiles
PCloud
MD5 :: 63FB23666399844E5BB7A8D9C347374D
____________________________________________
Prior Build - CM13:
cm-13.0-20161205-ilichva-xt907_jbb.zip (411.9 MB)
Original Link
Mega
SolidFiles
PCloud
MD5 :: 3c786a57929d024010a0fce36287ea7d
____________________________________________
NOTE: If you are on KitKat Bootloader (KKBL), you will need to revert to the JellyBean Bootloader (JBBL) before you can flash this ROM. Instructions on how to do so may be found here and here and here
____________________________________________
Latest TWRP 3.0.2 recovery by ilichva may be found/downloaded here

Updated to 03.25.2016 build

Hallo Rahimali
Thanks for the share. I have tried this and apparently works ok. I'm unable to get WiFi working. Tried different gapps but there are force close issues. Any recommended gapps versions available?

Opengapps usually does the job. Flashing gapps with marshmallow is different than with prior android versions. With MM you have to flash gapps immediately after you flash the ROM (before booting up the ROM for the first time). Try and see if that resolves your FC issues

Updated to April 02, 2016 build!

I managed to get the force close issues resolved. Everything works fine except Wifi. I am unable to enable wifi as the button is greyed out. I tried enabling wifi from terminal using svc wifi enable, it enabled the button but wouldnt detect any available wireless networks. Any fixes for this?

Updated to April 05, 2016 build!
ultrasoniic said:
I managed to get the force close issues resolved. Everything works fine except Wifi. I am unable to enable wifi as the button is greyed out. I tried enabling wifi from terminal using svc wifi enable, it enabled the button but wouldnt detect any available wireless networks. Any fixes for this?
Click to expand...
Click to collapse
Sorry no idea. Nobody is complaining in the 4pda forums about any WiFi issues. Did you do a clean flash? Maybe the developer, @ilichva can help?

bootloader and recovery
My XT907 is showing that my bootloader is "0x109B" and I am unsure what version of TWRP supports 6.0.1 (currently running 2.8.6.0)
Can anyone verify their settings and let me know?
I am running CM12.1 currently, so I should be able to dirty flash correct?
Thanks guys!

KKBL?
Anyone know of a marshmallow based rom that works with the kitkat bootloader for this device?

crzypcdude said:
Anyone know of a marshmallow based rom that works with the kitkat bootloader for this device?
Click to expand...
Click to collapse
Marshmallow not yet available on KKBL

rahimali said:
Marshmallow not yet available on KKBL
Click to expand...
Click to collapse
Are there any significant reasons to stay on the KitKat bootloader? Otherwise I'll just downgrade now that I'm rooted with an unlocked bootloader.

One of the most compelling reasons to stick with the KKBL would be the availability of the 3.4x kernel as opposed to the 3.0x kernel on the JBBL but feel free make your own decision. I was on the JBBL (by choice) for a considerable length of time without any apparent side effects...

Would you mind adding dates to post #1?

Any updatefor this rom?

crzypcdude said:
Would you mind adding dates to post #1?
Click to expand...
Click to collapse
The dates are already present in post #1 as well as in the filenames.
dedik46 said:
Any updatefor this rom?
Click to expand...
Click to collapse
Updated!

Are all the builds being updated in the 4PDA post linked in #1 as well as TWRP builds?

crzypcdude said:
Are all the builds being updated in the 4PDA post linked in #1 as well as TWRP builds?
Click to expand...
Click to collapse
That is correct.

Confirmed Working!
Can confirm this works, flashed the recovery included in the 4pda post, used it to flash the rom, gapps, and supersu. Initially booted up in Russian, but after waiting for 30 seconds or so, switched to English on its own. Setup was flawless after that, no issues to report as of now. Anyone that needs help installing the rom or downgrading from kitkat to jellybean just message me.

I thought I was the only one that ended up with default language in Russian... All the previous builds defaulted to English on install... Also when I downloaded the latest update it downloaded on my phone as a .bin not a .zip I checked the file size and contents vs what is online (after changing the extension to .zip) and everything seemed to be Ok so I installed and been up and running on latest version for 24 hours....
Had a few FC's in the beginning while changing the language to English (I have a feeling that some of my already installed apk's caused the issue) . I did do a test run before restoring my stuff and didn't have any issues during initial setup and the phone auto corrected language based off sim during initial setup.
Haven't gotten a chance to fully test this build, but I know that the issue that I was having with the native tethering soft rebooting the phone every couple of hours when active is gone! After a few more days of messing with it I will post any other issues that I come across
Sent from my Moto Razr M on cm13 4-16-16 using XDA Free mobile app

Any clue about why I'm getting error 7 while finishing the last steps of the ROM flashing procedure?

[ROM] Stock ROM Elephone P9000_Android_6.0_20160401_Beta

Stock ROM Elephone P90000_Android_6.0_20160401 (Beta)
Download - https://mega.nz/#!w4BBnKaR!_WU3BeucmEURhgo8VpvspHMVZngL7ctzd29mx6cn2BQ
XDA:DevDB Information
[ROM] Stock ROM Elephone P9000_Android_6.0_20160401_Beta, ROM for the Elephone P9000
Contributors
Jonny
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 20160401
Beta Release Date: 2016-04-04
Created 2016-04-19
Last Updated 2016-04-19

Has someone give this Beta a try?

Trying now, just be aware that flashing WILL completely wipe your phone again... Everything is gone...
Seriously though, how hard is it to NOT wipe everything like, oh i don't know, every other phone out there...
There is not much difference between this and the last OTA update, I have found the fingerprint sensor a little better but even the security patch level says 1 March 2016... Can't say anything about battery life yet, I find it usually takes 3 days for that to settle but I really haven't seen much difference in UI or settings. Most changes must be "under the hood" so to speak... Doesn't help there's no changelog...
Found the case doesn't seem to register being closed easily so it just leaves the phone on even though I have the original case that has the screen cutout for clock and whatnot.
Keyboard still doesn't support swype...

ultramag69 said:
Trying now, just be aware that flashing WILL completely wipe your phone again... Everything is gone...
Seriously though, how hard is it to NOT wipe everything like, oh i don't know, every other phone out there...
There is not much difference between this and the last OTA update, I have found the fingerprint sensor a little better but even the security patch level says 1 March 2016... Can't say anything about battery life yet, I find it usually takes 3 days for that to settle but I really haven't seen much difference in UI or settings. Most changes must be "under the hood" so to speak... Doesn't help there's no changelog...
Found the case doesn't seem to register being closed easily so it just leaves the phone on even though I have the original case that has the screen cutout for clock and whatnot.
Keyboard still doesn't support swype...
Click to expand...
Click to collapse
Untick the userdata.img if you don't want your data to be wiped.

racer290 said:
Has someone give this Beta a try?
Click to expand...
Click to collapse
Been running this for a number of days now, not run into any problems except it was slightly more difficult to root, lot of trial and error but I'm going to post a tutorial on how I rooted it later today.

Jonny said:
Been running this for a number of days now, not run into any problems except it was slightly more difficult to root, lot of trial and error but I'm going to post a tutorial on how I rooted it later today.
Click to expand...
Click to collapse
Correction, someone has already posted the method here >>> http://forum.xda-developers.com/elephone-p9000/how-to/how-to-root-elephone-9000-stock-rom-t3359315
The tutorial in the link above works for this firmware version as well.... could have saved myself a lot of time if I'd read that first lol. For convenience I've put all the files needed in a zip file (link below). Just use SP Flash Tool to flash the recovery, then flash the 2 other zip files from TWRP
ZIP File >>> https://mega.nz/#!IlgxgDhS!r6_OpFYLVv07o025ecJ9rDul2db1KMsoWAlZbabWMxI

trying to flash this but SPTools (5.1520.00) giving me "Error: Initializing scatter file failed. Please check the name of the scatter file which you load is legal" any ideas as to why? I have tried the other rom listed that isn't the BETA and get the same error...
Also, I don't appear to have the Allinone.bin file for the DownloadAgent, can someone please share that too me?
Thanks
Ignore that, I seem to have got it working.

Where do you get these ROMS from? I'm looking for rom version 20160318 for the p9000 lite.

karl0ss said:
trying to flash this but SPTools (5.1520.00) giving me "Error: Initializing scatter file failed. Please check the name of the scatter file which you load is legal" any ideas as to why? I have tried the other rom listed that isn't the BETA and get the same error...
Also, I don't appear to have the Allinone.bin file for the DownloadAgent, can someone please share that too me?
Thanks
Ignore that, I seem to have got it working.
Click to expand...
Click to collapse
use ever latest sp flashtool!
5.1604 or newer for Android 6 and P10 chipset

megthebest said:
use ever latest sp flashtool!
5.1604 or newer for Android 6 and P10 chipset
Click to expand...
Click to collapse
I could only get 5.1604 working, 5.1612 wouldn't work for me at all on Windows 10 in VirtualBox.

This is officiel or not ? and GPS work for you on this rom ? is it based on 20160315 ?

Bradco said:
This is officiel or not ? and GPS work for you on this rom ? is it based on 20160315 ?
Click to expand...
Click to collapse
please read.. is not based on 20160315 .. is a new stock rom 1st of April.. but still in beta stage..
I hear about a new OTA here http://forum.xda-developers.com/elephone-p9000/help/ota-update20160319-t3364691

megthebest said:
please read.. is not based on 20160315 .. is a new stock rom 1st of April.. but still in beta stage..
I hear about a new OTA here http://forum.xda-developers.com/elephone-p9000/help/ota-update20160319-t3364691
Click to expand...
Click to collapse
Ok thanks

How to roll back to Nougat OOS 4.5.1

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