Database Info

A few problems - IMEI, Rom, Root, recovery

Hi I succesfully flashed my brother in laws Lenovo A369i with the latest firmware Lenovo_A369i_4.2.2_(by_xdafirmware.com).zip found at http://firmwarefile.com/lenovo-a369i
I followed this guide and used the flash tool included in the firmware package above, and the latest usb drivers from below:
http://www.modifyandroid.com/stock-roms/lenovo/how-to-install-stock-rom-in-lenovo-a369i/
https://androidmtk.com/download-lenovo-usb-drivers
According to the phone, this version is A369I_S110_140108 - and when checking for updates it says that this is the latest one - but how can I be sure?
I searched on google and most of the times there are sites that claim to have the latest but they don't write which version it is(very anoying) so I can spend many hours(very slow internet connection) on downloading the one I already have or one older.
The information and guides on here Xda has not been updated for a while.
The Phone works with both phone calls and sms, but the IMEI is not written - so should I do that with SN_Write_Tool_v2.1504.00.zip, MTK Droid Tools or is there an easier way to do it - or should I just forget about it?
UPDATE: I got this sorted out now, by rooting with framaroot and using Chamelephon to first make random IMEI then reboot and change the IMEI to the correct ones.
-----------------------------------------------------------------------------------------------------------
My second problem is that the phone were unlocked before I flashed it and now its locked again - are there a guide to unlock it?
The phone were not bought with subscription, we bought it here in the philippines from Lenovo Mobile( not real Lenovo company but dealer/importer allowed to use the name(for god sake stay away from them)) and after repair the dealer sent back different older model(this A369i) with less battery and locked to Globe. After trying for 2 months to get them to give us the unlock code, I gave up fighting them and had it unlocked at phone repair shop were they had to use a box to do it, so I never got any code.
---------------------------------------
Third problem: I need to root it but not sure which tool to use?
Update: This is sorted out, see above.
--------------------------------------------------------------------------
Fourth problem: I like to install custom recovery on it - but which one work best and allow to flash from SD card?
As this is the first time I have flashed an Mediatek phone, are there anything else that I need to do?
Hope an expert can help me
JBJ

URGENT! Need Help with my ZF3U

UPDATE:
I have now installed the manual update for Android 7.0 and this helped to resolve some of the issues:
-I can now make and receive calls fully with voice enabled
-Bootloader updated from 1.26 to 3.11
BUT:
-Fingerprint Recognition still not working
-Device serial number still shows as 111111111111111
-Device shows as encrypted- could this be the cause and how?
If anyone has any suggestions please assist.
MY ORIGINAL POST RE ISSUES:
Following release of Android 7 for ZF3U, I updated and then wanted to unlock the bootloader and carry out root. All went fine but now after unlocking the bootloader and root I have a major problem. My ZF3U does not show the correct device serial number in the initial setup wizard and in about phone section of settings. All I get is "111111111111111". Secondly, whilst all other functions are working fine, I can no longer hear the sound of any made or received phone calls.
I also tried to use the ASUS Flash Tool to reinstall the firmware but could not and at one point I saw a message stating that the device was being encrypted . I have no idea what implications this has but I my phone does not allow use of internal speakers or microphone for the other side to hear me. It appears that the serial number issue started with my use of the Asus Flash Tool. I am also not sure if this encryption issue caused the issue as it may have locked certain parts of the device.
Also, as a result I am unable to set the fingerprint recognition in initial setup or after setup. Pin code, pattern etc can be setup but not fingerprint security.
Tried to use TWRP to reinstall the firmware. All installs fine but the problem is still there. I pressed the decrypta button inside TWRP settings but still no fix. Also, did all the usual wipes etc.... still no fix. I don't know what to do. I now wish I had not played around with the phone and simply used it as it was. With the bootloader unlocked no Android 7 anymore until manual firmware becomes available. My device serial number still shows as "111111111111111" but when I launch the fastboot/recovery mode I do see the correct serial number but the device boots to UI with the incorrect serial number. My theory is that the Asus Flash Tool caused the problem but I am not sure how.
Also if anyone has the original factory boot.img and other relevant .img files for me to fix the bootloader in case this is the problem thatI would be very appreciated. Also, I have read that the .raw firmware files for this device could fix the problem but not sure and the files cannot be found anywhere online.
I also by removed the root and did a fresh install of the previous firmware Android 6.0 and the problems still exist. I am not sure if the downgrade from Android 7 could have caused these problems too but I am trying to pinpoint the problem somehow. So if anyone has a full manual .Raw or normal .zip version of the Android 7.0 firmware then please provide a download link. If all fails then I would have to see if I could get Asus to fix it for me.
All suggestions and workarounds desperately welcome. Thanks.

1. Try posting about your issues in Taiwanese Asus forums under this topic:
https://www.asus.com/zentalk/tw/thread-216020-4-2.html
Use Google Translator in order to navigate the Taiwenese forum. Post your message in English.
2. Try posting about your issues in XDA Asus Zenfone 3 forums (regular Zenfone 3, not Zenfone 3 ultra), because regular Zenfone 3 community is larger, however devices should be quite similar:
https://forum.xda-developers.com/zenfone-3
As always, keep Zenfone 3 ultra community informed with your future findings, so we all could learn something new and help each other.

Help with downgrade?

What i have: a brand new carrier unlocked samsung galaxy s7 sm-g930w8 - came with 7.0
What Id love to do: downgrade to 6.0.1 official touchwiz rom but rooted
What im reading: that the security patch is from february of 2018, which means the bootloader is too new, which means downgrading using odin wont work ( https://www.sammobile.com/forum/threads/36282-Does-Region-Matter )
... so what can i do? i bought this phone with the sole intention of downgrading, as ive seen that it is possible for that phone model (s7) in general
i hate the look of the newer OS. They took the touchwiz out of touchwiz which i loved, although mine is a rare opinion. I want the operation and exact feel of 6.0. the menus are simpler, the notifications area isnt completely stripped of features differing from total stock android. i hate having to pull down twice to see everything. I just really want that older look and feel, but all around, not just a theme.
is there anything i can do to either downgrade or fool the bootloader into letting me carry this out? is this a true limitation, or si that info i found false/old? and if I can downgrade, which build version should I use?
ive been looking here for versions
https://samsung-firmware.org/model/SM-G930W8/ but im not sure which region to go with, or if i can technically use any region
sammobile doesnt list that version anymore at all ( https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/ )
https://mobiletech360.co/samsung-galaxy-s7-sm-g930w8-stock-firmware-rom-android-6-0-1-marshmallow/ there are a number of options here but unsure of the different numbers/builds. or if since its carrier unlocked, i could pick any?
I know most will think im silly for wanting to downgrade or caring that much about appearance, but silliness aside... is this even possible??
a while ago, i purchased an s5 mini, and downgraded that with no issues at all.... but its honestly been so long and i cant for the life of me remember the steps i took or if i needed to care about region codes or other numbers. but it did sucessfully work.... it was really built unwell/cheap, but it did work.... its also slower than my captivate glide which is still my current phone, until/if i can get this s7 working the way i desire.
any help and guidance is appreciated. If it is needed, ill be using it with a Koodo mobile sim.

well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in

teddytsen said:
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
Click to expand...
Click to collapse
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Sent from my [device_name] using XDA-Developers Legacy app

Pawprints1986 said:
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Click to expand...
Click to collapse
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)

Hello,
I can understand you and also understand what you want but Samsung installed a downgrade lock in their bootloader in early 2018,
if you installed this version you can't go back to an older version, I think that was in February.
You can go back from a 6.2018 version to a 4.2018 version for example but not to a 1.2018 version!
If you have a version of for example 12.2017, you can also go back to a version of 2016, so you can also go back to Android 6.01,
if not you only have the last versions of Android 7 or update to Oreo.
I hope I could help.

teddytsen said:
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Click to expand...
Click to collapse
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.

Pawprints1986 said:
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Click to expand...
Click to collapse
TL;DR
your bootloader is currently on version 3, and you cant downgrade to marshmallow
see that "U3BRB2"? that "U3" means your bootloader is on version 3. i assume the marshmallow firmwares use bootloaders pre-version 3 so you cant downgrade to firmwares using bootloaders with version 1 or 2. (this is how it works for F/FD models and im pretty sure samsung made it like that too for the W8 models)
eta 1) unrelated
eta 2) F/FD/W8/S/K/L variants (basically all the exynos models) have unlocked bootloaders. only SD variants have locked bootloaders so it's just your misconception

So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app

Pawprints1986 said:
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.

AoEKiller said:
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
Click to expand...
Click to collapse
You'll trip knox (which breaks features like secure folder, private mode, shealth and Sbrowser private mode) and lose the comfort of OTA updates if you do this tho. Not to mention that you can encounter signal reception problems because your flashed ROM is on marshmallow and your bl/cp is on Oreo or nougat. So I wouldn't advise this method as it may break so many things.

My progress: LG V20 H918/7.0+ FRP bypass in 2018?

After putting my FRP-stuck T-Mobile V20 away for a couple months, I was unfortunately surprised to learn that very little public progress has been made on the subject since my last give-up. I dedicated the last day to trying to figure out FRP bypass for my LG V20, and upon re-researching, I have...
1. Managed to downgrade my V20 to H91810j, though this version still has all exploits patched to get through FRP (to my knowledge).
2. Upon further research, I concluded that what I need is to successfully downgrade to H91810d, as it's the only pre-December 2016 update available (pre-December updates have un-patched exploits to be able to get into the phone). Unfortunately, this update was the one released on the phones stock from the factory, which made it next to impossible to find a KDZ file as they were't "pushed" to the general public.
3. Through researching countless other threads, I've come across this link (I can't share as I still haven't posted 10 times, can DM if needed for reference) which appears to be the closest possible file to the needed H91810d, except the download is a .ZIP that contains Boot.img and Modem.img, which I'm not familiar with using, and no .KDZ file.
4. Further research concluded that I could TWRP-push these files to a TWRP unlocked device, but because of the locked FRP, such a thing isn't possible. My last and final method (which I will try tomorrow as it's 8 AM and i've been trying to get this damned phone unlocked for hours and need sleep) will be one recommended on another forum, which is to downgrade, reset the phone, upgrade, reset the phone, and continue on until FRP is no longer on the device.
Researching into other devices proves that it's definitely possible, though the V20 (especially the H918 model at that) seems to have far less information available towards achieving this. After giving a selection of paid services a look as well, the majority didn't have the ability to unlock the V20 either, which makes me question what the V20 is doing differently from other devices. If anybody has any information that could help me or the community in the matter, please let me know!

caldermody said:
After putting my FRP-stuck T-Mobile V20 away for a couple months, I was unfortunately surprised to learn that very little public progress has been made on the subject since my last give-up. I dedicated the last day to trying to figure out FRP bypass for my LG V20, and upon re-researching, I have...
1. Managed to downgrade my V20 to H91810j, though this version still has all exploits patched to get through FRP (to my knowledge).
2. Upon further research, I concluded that what I need is to successfully downgrade to H91810d, as it's the only pre-December 2016 update available (pre-December updates have un-patched exploits to be able to get into the phone). Unfortunately, this update was the one released on the phones stock from the factory, which made it next to impossible to find a KDZ file as they were't "pushed" to the general public.
3. Through researching countless other threads, I've come across this link (I can't share as I still haven't posted 10 times, can DM if needed for reference) which appears to be the closest possible file to the needed H91810d, except the download is a .ZIP that contains Boot.img and Modem.img, which I'm not familiar with using, and no .KDZ file.
4. Further research concluded that I could TWRP-push these files to a TWRP unlocked device, but because of the locked FRP, such a thing isn't possible. My last and final method (which I will try tomorrow as it's 8 AM and i've been trying to get this damned phone unlocked for hours and need sleep) will be one recommended on another forum, which is to downgrade, reset the phone, upgrade, reset the phone, and continue on until FRP is no longer on the device.
Researching into other devices proves that it's definitely possible, though the V20 (especially the H918 model at that) seems to have far less information available towards achieving this. After giving a selection of paid services a look as well, the majority didn't have the ability to unlock the V20 either, which makes me question what the V20 is doing differently from other devices. If anybody has any information that could help me or the community in the matter, please let me know!
Click to expand...
Click to collapse
Are you rooted, with TWRP installed?

pawar21 said:
Are you rooted, with TWRP installed?
Click to expand...
Click to collapse
I am not, I would attempt to root but without being able to enable USB debugging, I'm sort of at a stalemate.

Have you looked at this........https://youtu.be/NWTmVIXkFDI

caldermody said:
After putting my FRP-stuck T-Mobile V20 away for a couple months, I was unfortunately surprised to learn that very little public progress has been made on the subject since my last give-up. I dedicated the last day to trying to figure out FRP bypass for my LG V20, and upon re-researching, I have...
1. Managed to downgrade my V20 to H91810j, though this version still has all exploits patched to get through FRP (to my knowledge).
2. Upon further research, I concluded that what I need is to successfully downgrade to H91810d, as it's the only pre-December 2016 update available (pre-December updates have un-patched exploits to be able to get into the phone). Unfortunately, this update was the one released on the phones stock from the factory, which made it next to impossible to find a KDZ file as they were't "pushed" to the general public.
3. Through researching countless other threads, I've come across this link (I can't share as I still haven't posted 10 times, can DM if needed for reference) which appears to be the closest possible file to the needed H91810d, except the download is a .ZIP that contains Boot.img and Modem.img, which I'm not familiar with using, and no .KDZ file.
4. Further research concluded that I could TWRP-push these files to a TWRP unlocked device, but because of the locked FRP, such a thing isn't possible. My last and final method (which I will try tomorrow as it's 8 AM and i've been trying to get this damned phone unlocked for hours and need sleep) will be one recommended on another forum, which is to downgrade, reset the phone, upgrade, reset the phone, and continue on until FRP is no longer on the device.
Researching into other devices proves that it's definitely possible, though the V20 (especially the H918 model at that) seems to have far less information available towards achieving this. After giving a selection of paid services a look as well, the majority didn't have the ability to unlock the V20 either, which makes me question what the V20 is doing differently from other devices. If anybody has any information that could help me or the community in the matter, please let me know!
Click to expand...
Click to collapse
This is the guide i used & im on h91810p & i had mine bypassed & ready to setup in just under an hour.....
https://www.hardreset.info/devices/...ication/frp-lg-google-account-2018-x-power-2/
Sent from my LG-H918 using XDA Labs

pump0666 said:
This is the guide i used & im on h91810p & i had mine bypassed & ready to setup in just under an hour.....
https://www.hardreset.info/devices/...ication/frp-lg-google-account-2018-x-power-2/
Sent from my LG-H918 using XDA Labs
Click to expand...
Click to collapse
Well for those trying, I have a phone on H91810q, and the above process (hardreset link) does not work. when getting to the step to allow unsigned binaries it will not toggle. I tried a few other approaches that might get USB enabled (e.g. via LDB in SVC mode, but it also failed to toggle).
Does any know if you can downgrade an FRP locked phone without USB enabled? e.g. using the process described in the thread http://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
Asking before I have to go find a windows box and spend an hour or so trying, in vain, if it is not possible.

drinnovation said:
Well for those trying, I have a phone on H91810q, and the above process (hardreset link) does not work. when getting to the step to allow unsigned binaries it will not toggle. I tried a few other approaches that might get USB enabled (e.g. via LDB in SVC mode, but it also failed to toggle).
Does any know if you can downgrade an FRP locked phone without USB enabled? e.g. using the process described in the thread http://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
Asking before I have to go find a windows box and spend an hour or so trying, in vain, if it is not possible.
Click to expand...
Click to collapse
Have you tried downgrading to h91810p first? H91810q might be patched as not to allow this method. Both h91810p & q are ARB1 so you CAN roll back before proceeding
Sent from my LG-H918 using XDA Labs
I should also add that I used the method with Bluetooth earpiece. & comp method-

Unlock bootloader confusion

Hey Guys,
I have been googling for a while now and I seem to constantly come across conflicting and at times worrying posts which has very much left me stuck right were I am. I just recently purchased a Mate 9 in the hope I would be able to, like all my previous mobiles install a custom rom and tweak it to my specific needs. This however hasn't been the case.
Firmware:
System 8.0.0.046
Dataver MHA-L09 8.0.0.371(C34)
Things that have been tried:
1. No I didn't get a boot unlocker code from the Huawei
2. Yes I have contacted them personally via two different channels and both returned with a we are happy to give it to you, that's not an issue, but this code doesn't exist anymore.
3. DC-Unlock tool didn't detect my mobile in manufacture mode, in which I found another forum post stating to use HCU 3.22 client instead which worked to the point of detecting my mobile, but told me that the current security patch not supported.
4. Contacting DC-Unlock, told me there is no ETA on getting this patch level to work
5. I have read people downgrading to a previous version, unlocking and then installed the custom rom via HiSuite, this doesn't give me that option.
6. I have read people downgrading to a previous version, unlocking and then installed the custom rom via firmware finder.
6.1 Issues with this is that I seen someone claim to upgrade to version 8.0.0.3.75, which is higher then mine, which enabled the rollback feature, is this correct?
6.2 Issues with this is that I have read that gpu turbo has been enabled and many have warned that rolling back to a pre-gpu turbo enabled firmware will brick you mobile and would result in a motherboard needing to be replaced for nearly the cost of the mobile itself.
I am tempted to try another site which I can't remember the name of, which if you pay considerably more then DC-Unlock. at least if they can't get the code, would be refunded. but I think that site is down now as I feel they were playing on people who didn't know how to have done it for free via the Huawei site back in 2018.
So I want to know is there a safe way to unlock my bootloader I think my only option is option 6 but just want more details from others who have done it this way before, or have I pretty much exhausted all my option and just bite the bullet and upgrade to 9.0.1.187 and possibly further through the OTA update process and just enjoy the mobile for what it is and it's limitations?
Thanks again.

You can try the spoofing method here on xda I updated from 8 to 9 with that, as long as firmware finder says your imei is approved

mucski said:
You can try the spoofing method here on xda I updated from 8 to 9 with that, as long as firmware finder says your imei is approved
Click to expand...
Click to collapse
Thanks for that, I can already upgrade to 9, my system updates app is just waiting for me to accept. The issue is that I don't want to go forward. I really want to go backwards, so I can unlock my bootloader first. I'm already at the stage where I have tried most if not all the safe ways to unlocking my bootloader, but with my currently installed android version I can't. The only way forward for me it seems is the firmware finder app and SD force flash back to EMUI 5 aka Android 7 to use DC-Unlocker to unlock it first, then that gives me the freedom of installing the official Android 9 or openkirin.
I just worried as some people have stated that if you attempt a downgrade after a specific point, something about GPU turbo being enabled in later firmwares, which will brick your mobile.
I just want to hear from others who have done this successfully or if it's not possible in my case.