Related
Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
hikari_calyx said:
Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
Click to expand...
Click to collapse
I was thinking of buying N7P instead of Xiaomi Redmi Note 5,but I read that Nokia doesn't allow users to unlock the bootloader, so no custom ROMs, no TWRP and no root. That is a big no for me personally.
How did you root your phone? Care to share some info?
_Raziel666 said:
I was thinking of buying N7P instead of Xiaomi Redmi Note 5,but I read that Nokia doesn't allow users to unlock the bootloader, so no custom ROMs, no TWRP and no root. That is a big no for me personally.
How did you root your phone? Care to share some info?
Click to expand...
Click to collapse
Prototype phones already have bootloader unlocked...
What I did are:
1. Enter Qualcomm EDL Mode with an EDL cable, then use QFIL to dump the whole emmc to get image.
2. Dump boot partition.
3. Use Magisk Manager to patch boot.img separately.
4. Flash this boot.img on either fastboot mode or EDL cable.
That's it.
I wonder if a retail phone can achieve these.
NOTE: Nokia 6 TA-1000 with locked bootloader requires an extra procedure to process boot.img in order to root the phone.
hikari_calyx said:
Prototype phones already have bootloader unlocked...
What I did are:
1. Enter Qualcomm EDL Mode with an EDL cable, then use QFIL to dump the whole emmc to get image.
2. Dump boot partition.
3. Use Magisk Manager to patch boot.img separately.
4. Flash this boot.img on either fastboot mode or EDL cable.
That's it.
I wonder if a retail phone can achieve these.
NOTE: Nokia 6 TA-1000 with locked bootloader requires an extra procedure to process boot.img in order to root the phone.
Click to expand...
Click to collapse
I didn't know that prototypes have their bootloader unlocked!
Hopefully, by the time it hits European stores, the Chinese who got it first might have figured something out. Or maybe, as it's part of Android One, it will be obligatory to allow users to unlock the bootloader.
hikari_calyx said:
Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
Click to expand...
Click to collapse
I have the firmare will upload it tomorrow. Is there a forum created for Nokia 7+ already ??
Thank you, if root will be avaible I'll definitely consider buying the phone.
What do you think of the phone? Quality of screen, performance, battery...
How were you about to get a prototype device? What about the retail chinese phones? I was thinking about importing them from ebay/aliexpress but im not sure if they'll be able to have their bootloader unlocked, no one has tried so far to my knowledge.
reeved said:
How were you about to get a prototype device? What about the retail chinese phones? I was thinking about importing them from ebay/aliexpress but im not sure if they'll be able to have their bootloader unlocked, no one has tried so far to my knowledge.
Click to expand...
Click to collapse
I still have no idea of if the bootloader on China Variant is unlockable.
But, if you're going to buy Nokia 7+ from China, here's some warning:
1. Only Chinese (both Simplified and Traditional) and English is available on the phone.
2. You can install Play Store manually, but you must told the seller that preserves everything on stock to prevent from tampered system.
3. If the system got damaged, you have to find someone who can provide service support to flash your phone. I don't know if you can flash Android One firmware for global release since I don't have one.
hikari_calyx said:
I still have no idea of if the bootloader on China Variant is unlockable.
But, if you're going to buy Nokia 7+ from China, here's some warning:
1. Only Chinese (both Simplified and Traditional) and English is available on the phone.
2. You can install Play Store manually, but you must told the seller that preserves everything on stock to prevent from tampered system.
3. If the system got damaged, you have to find someone who can provide service support to flash your phone. I don't know if you can flash Android One firmware for global release since I don't have one.
Click to expand...
Click to collapse
Thanks for that info, on point 2 regarding play store does that extend to Google services also? Wifey is holidaying in China and just bought one and thought to buy another for me but I'm holding her off until I can be sure as I rely on Google services a great deal. Also why must the seller be informed, is that a warranty issue or software update issue?
And on point 3, presuming she brings the phone back to New Zealand is there a way I can help the community to explore flashing Android One global release firmware?
maomaoliu-bright said:
Thanks for that info, on point 2 regarding play store does that extend to Google services also? Wifey is holidaying in China and just bought one and thought to buy another for me but I'm holding her off until I can be sure as I rely on Google services a great deal. Also why must the seller be informed, is that a warranty issue or software update issue?
And on point 3, presuming she brings the phone back to New Zealand is there a way I can help the community to explore flashing Android One global release firmware?
Click to expand...
Click to collapse
If you can buy it from China directly, informing seller is not necessary. For example, if you can buy it from Jing Dong or Suning, you needn't to worry about tampered OS, and that means you can receive further updates.
If you buy it from eBay or AliExpress, the system is probably tampered by seller which you can't get further updates.
As for install Play Store, it's really easy - just find Play Store APK from APKPure, APKMirror whatever and install it on the phone, this will allow you to get access to Play Store. Then you can install any other Google Apps on Play Store manually. You needn't to root your phone and install opengapps.
Since Android One firmware hasn't released yet and the bootloader isn't unlockable, you can't flash it right now.
Nokia 7 plus is available on Amazon europe sites like Germany and Italy and others and also ships worldwide and release date showing 12 to 14 or 15 april
hikari_calyx said:
Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
Click to expand...
Click to collapse
pls pls pls
Post system image of oreo 8.1
thank you!
Big question here! I am going to europe and want to buy this phone there, the problem is that the model they are selling don't have band 4 (1700/2100) and i need it in my country. Is there a way to fix this? Is a model in europe with band 4? Can i flash the modem with band 4? Thanks a lot!
As the phone should be available, are there any news about the firmware of Europe phones? Is the bootloader unlocked / unlockable?
flo.ei said:
As the phone should be available, are there any news about the firmware of Europe phones? Is the bootloader unlocked / unlockable?
Click to expand...
Click to collapse
According to this post, the official bootloader unlocking from HMD themselves is imminent.
I heard the Chinese Firmware supports navbar gestures where you can disable navbar and use gestures and this isnt available in Global version
That SUCKS! its such a good feature NOKIA give it to all!
varun.gid said:
I heard the Chinese Firmware supports navbar gestures where you can disable navbar and use gestures and this isnt available in Global version
That SUCKS! its such a good feature NOKIA give it to all!
Click to expand...
Click to collapse
Try searching in settings for 'nav'. It will reveal the Navigation key of fingerprint setting.
TA-1046, Android 8.0
hikari_calyx said:
Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
Click to expand...
Click to collapse
How you dumped emmc of nokia 7 plus oreo 8.1.0 ?
Does anyone have the build.prop from the Nokia 7 Plus they can post?
hikari_calyx said:
Prototype phones already have bootloader unlocked...
What I did are:
1. Enter Qualcomm EDL Mode with an EDL cable, then use QFIL to dump the whole emmc to get image.
2. Dump boot partition.
3. Use Magisk Manager to patch boot.img separately.
4. Flash this boot.img on either fastboot mode or EDL cable.
That's it.
I wonder if a retail phone can achieve these.
NOTE: Nokia 6 TA-1000 with locked bootloader requires an extra procedure to process boot.img in order to root the phone.
Click to expand...
Click to collapse
Bro can we dump emmc of ta-1046 by using same method
Having unlocked bootloader???
Yesterday I got my OP8T which I updated to Oxygen OS 11.0.1 right away. I played around a bit and had some fun testing that new Canvas AOD feature. The next step obviously was unlocking the bootloader (rooting is the crucial reason I find Android superior) but after the initial boot I noticed that Canvas AOD is gone. Is it possible that this app was NOT in the system partition and simply got deleted when wiping user data? If so, I'd really appreciate someone provide this apk here.
@MaxFTW , try this APK https://drive.google.com/file/d/1arqhlSvTP_k66qGGysuDEegKKj80urKO/view?usp=sharing , it was present in reserve/CanvasResources .
Out of curiosity, what is the output of adb shell getprop ro.build.version.ota ?
I wonder if your reserve.img has been wiped like on carrier devices once their bootloader is unlocked, as this could be a side effect of OnePlus using Google's OTA servers on international build, see https://oxygenupdater.com/api/v2.5/news-content/157/EN
Some_Random_Username said:
@MaxFTW , try this APK https://drive.google.com/file/d/1arqhlSvTP_k66qGGysuDEegKKj80urKO/view?usp=sharing , it was present in reserve/CanvasResources .
Out of curiosity, what is the output of adb shell getprop ro.build.version.ota ?
I wonder if your reserve.img has been wiped like on carrier devices once their bootloader is unlocked, as this could be a side effect of OnePlus using Google's OTA servers on international build, see https://oxygenupdater.com/api/v2.5/news-content/157/EN
Click to expand...
Click to collapse
Code:
OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
Thanks, works like charm! Basically all the other OnePlus stuff such as Community or Weather for example got deleted as well.
Some_Random_Username said:
@MaxFTW , try this APK https://drive.google.com/file/d/1arqhlSvTP_k66qGGysuDEegKKj80urKO/view?usp=sharing , it was present in reserve/CanvasResources .
Out of curiosity, what is the output of adb shell getprop ro.build.version.ota ?
I wonder if your reserve.img has been wiped like on carrier devices once their bootloader is unlocked, as this could be a side effect of OnePlus using Google's OTA servers on international build, see https://oxygenupdater.com/api/v2.5/news-content/157/EN
Click to expand...
Click to collapse
..thanks a lot! Works great
Canvas AOD was missing on my phone as well (rooted, 11.0.1.2 KB05BA, KB2003)
After new year or 11.0.5.1 update, widevine certificate went from L1 to L3. I never unlocked, rooted or modded my phone. Model is Oneplus 7 Pro GM1910 256gb. What is your widevine level?
Same for me, although I am not sure of the timing. Ever find a fix?
Try flashing latest OOS 11 image from MSM tool. Internet says it fixes the L3 issue.
Note:
1) Flashing ROM from MSM tool will wipe data so backup first.
2) The image necessarily needs to be Oxygen OS 11. Version 10 won't fix anything.
I have this issue as well. But I am living with it as I don't use Netflix stuffs. Let the community know if it fixes
I attempted to convert my t-mobile oneplus 9 to international firmware by first flashing the Indian firmware.
I mistakenly downloaded the oneplus 9 PRO Indian msm.
I didn't realize this as the file has a very similar name. Lemonade_22.I.07_210412 vs Lemonadep_22_I.07_210412
I've tried everything since then, with no success. I tried to flash the correct oneplus 9 indian msm but it says incorrect device.
So I'm stuck with the oneplus 9 pro Indian firmware and can't get back to indian oneplus 9 firmware....
I have been developing and flashing android devices since the early days of Cyanogenmod... dozens of devices. And guess what? I did EXACTLY the same thing as you.
The link I downloaded from said it was Oneplus 9 firmware, and given the filenames being virtually identical, I never noticed it was the Oneplus 9 PRO firmware.
So don't feel too bad. Even experienced people can make mistakes when trying to flash phones!
I am working on a solution, but so far no luck because:
1. Msm Tool will not flash the Oneplus 9 firmware as it thinks it is the incorrect device (why did it let us flash the incorrect device firmware before???)
2. The bootloader is re-locked and the OEM Unlocking feature is greyed out in Developer options, therefore fastboot can't be used to re-flash the correct firmware.
3. The System Update "local upgrade" feature does not find ZIP files in the root folder and will not allow us to browse to the correct file.
So for now, we are stuck. I think solving #3 will be the solution. If we can make the "local upgrade" work, we should be able to flash the stock firmware ZIP.
@Derek6091 @mightysween did you fix it yet? I had my device screw up so bad today that the only MSM I could use on my global unit was the Indian 9 Pro firmware and I have gotten my device mostly working.
You can see my drama with it and how I finally got it working here.
[SOLVED] Can anyone help me unbrick? I have tried lite firehose, MSM for global, MSM for Indian 9 Pro, none work
I modded the global MSM so that it will flash to this frankenphone. https://forum.xda-developers.com/t/all-of-those-stuck-on-indian-firmware-rejoice-i-modded-the-global-msm.4442473/ EDIT: For anyone else trying this and getting unsupported...
forum.xda-developers.com
I can get it working with 11.2.10.10 but not OOS 12, in OOS 12 the touchscreen doesn't work and it shows dual SIM icons so it's still doing something that makes it think it's a foreign variant. I ended up just going back to StagOS where I was before everything got mucked up.
Unfortunately the MSMs still see it as an Indian variant so I can only flash the Indian OP9P firmware to it, tried all the other MSMs and none work. I have been reading threads here and people claim they got it back to global but I tried all of the suggestions and none of them restored the device enough to where the global MSM Tool didn't see it as an Indian model and refuse to flash so I think we are stuck with this frankendevice.
@EtherealRemnant Yes I had to do oem unlock while on the Indian firmware. If your phone has the oem unlock greyed out, there's a guide on how to fix that with a simple command line.
Then I unlocked bootloader, flashed lineage recovery then a custom ROM. Haven't tried to get back to stock rom, and I don't think we can.... But I love this rom I'm currently on which is stagos.
Feel free to message me for any questions you may have!
[ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonade][FINAL][08/09/2022]
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might...
forum.xda-developers.com
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Nice glad you figured it out.
go17lyonjon said:
Nice glad you figured it out.
Click to expand...
Click to collapse
haha yeah I was a dog with a bone, wasn't gonna drop it lol.
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Excellent. How did you do it? I would like to try with the T-Mobile MSM
Derek6091 said:
@EtherealRemnant Yes I had to do oem unlock while on the Indian firmware. If your phone has the oem unlock greyed out, there's a guide on how to fix that with a simple command line.
Then I unlocked bootloader, flashed lineage recovery then a custom ROM. Haven't tried to get back to stock rom, and I don't think we can.... But I love this rom I'm currently on which is stagos.
Feel free to message me for any questions you may have!
[ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonade][FINAL][08/09/2022]
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might...
forum.xda-developers.com
Click to expand...
Click to collapse
I can't find a working command line fix for the greyed out OEM unlock... which one did you use?
mightysween said:
I can't find a working command line fix for the greyed out OEM unlock... which one did you use?
Click to expand...
Click to collapse
Go to your home screen on your phone and connect to computer with usb debugging and run this command in cmd,
adb shell pm disable-user com.qualcomm.qti.uim
Then go to developer options and oem unlock should be able to toggle.
mightysween said:
Excellent. How did you do it? I would like to try with the T-Mobile MSM
Click to expand...
Click to collapse
You have to use the Oppo Decrypter tools. Decrypt the OPS file and open settings.xml. At the bottom of it there's a Target area. I just edited that to IN instead of O2 and re-packed it.
Derek6091 said:
Go to your home screen on your phone and connect to computer with usb debugging and run this command in cmd,
adb shell pm disable-user com.qualcomm.qti.uim
Then go to developer options and oem unlock should be able to toggle.
Click to expand...
Click to collapse
Perfect... thanks.
EtherealRemnant said:
You have to use the Oppo Decrypter tools. Decrypt the OPS file and open settings.xml. At the bottom of it there's a Target area. I just edited that to IN instead of O2 and re-packed it.
Click to expand...
Click to collapse
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
mightysween said:
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
Click to expand...
Click to collapse
Manually flashing partitions in Fastboot does work, FYI. So it is possible to go back to stock that way once the bootoader is re-unlocked.
I wonder where the "target" data is stored on the actual device. If it is simply a numerical/text value in an accessible partition, seems like it would be pretty easy to make a TWRP flashable that can change it.
mightysween said:
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
Click to expand...
Click to collapse
Strange that it didn't work for you. That was indeed all I changed. Did you change it to what the unsupported target message said your device was? I was comparing the settings between India and global and besides the change of target ID, the target number on India was 3 instead of 1. No idea if that makes a difference though because I didn't try it.
You made sure to re-encrypt and replace the OPS, right?
Also yeah you can flash with fastboot, it doesn't fix that flag though and when I tried to go back to OOS 12 with the messed up flag it thought my device was a dual SIM device so there was no signal and the touchscreen didn't work. Happened twice. With the modified MSM I went back to global and am running OOS 12 right now.
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Do you still have this file ? I flashed the OnePlus 9 pro indian firmware in msm since it's the only thing that worked and I want to go back to global
taintsx said:
Do you still have this file ? I flashed the OnePlus 9 pro indian firmware in msm since it's the only thing that worked and I want to go back to global
Click to expand...
Click to collapse
All you have to do to go back to global is download the full OTA for your device and flash it with the system updater.
EtherealRemnant said:
All you have to do to go back to global is download the full OTA for your device and flash it with the system updater.
Click to expand...
Click to collapse
Yea I tried that and had touchscreen not responding issues
taintsx said:
Yea I tried that and had touchscreen not responding issues
Click to expand...
Click to collapse
Then use the downgrade package. It will wipe your phone again but I will get you back to full OOS11 firmware and that issue won't happen.
EtherealRemnant said:
Then use the downgrade package. It will wipe your phone again but I will get you back to full OOS11 firmware and that issue won't happen.
Click to expand...
Click to collapse
Yea i tried that with
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
downgrade indian version 11.2.5.5 , unfortunately it just tells me it cannot read the file when i attempt to sideload
Booted up a oneplus 9 pro boot image, it fixed my phone being stuck in fastboot because I didn't have stock image.
Now updates don't work.
Oneplus 9 T-Mobile, stock rom, pro boot image, unlocked bootloader, unlocked sim - Any help would be appreciated.
Was thinking MSM tool but unsure what one to use.
I'm in a similar situation but I can't get out of fastboot. What OnePlus Pro boot image did you flash to your phone and what firmware are you on?
I gave the pro boot.img a try and it worked!
I grabbed it from this post: https://forum.xda-developers.com/t/...t-keep-root-oos-12-c-48.4252373/post-87096189
I want to back a few things up before tinkering anymore but will report back on how I try to fix it.
Thinking ahead, did Oxygen Updater not allow you to change your device back to a OnePlus 9, download the software update, flash and revert back?
Glad you could get your phone fixed...
I wish my system updates worked though lol ugh
Harley1979 said:
Glad you could get your phone fixed...
I wish my system updates worked though lol ugh
Click to expand...
Click to collapse
Are you using Oxygen Updater or the native update tool?
If the latter I would try the former.
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com
No I'm on a t-mobile oneplus 9 with android 12.
Soooo have you tried Oxygen Updater?
No it doesn't work for my version of this phone.
Thanks though
I wish I had a copy of the original boot image of my phone, T-Mobile variant boot.imge I'm guessing and for the non-pro version. I'm assuming that may fix my issue with the T-Mobile system updates and my incompatibility app issues with Google Play...
Harley1979 said:
I wish I had a copy of the original boot image of my phone, T-Mobile variant boot.imge I'm guessing and for the non-pro version. I'm assuming that may fix my issue with the T-Mobile system updates and my incompatibility app issues with Google Play...
Click to expand...
Click to collapse
If your bootloader is unlocked and Google Play is telling you that your device is not supported, it's because of the unlocked bootloader most likely. Are you successfully passing both basic and CTS safetynet profiles?
Not sure sry... Only few apps are incompatible.
This is what the OnePlus updater shows.
Harley1979 said:
Not sure sry... Only few apps are incompatible.
This is what the OnePlus updater shows.
Click to expand...
Click to collapse
I think your problem is that your bootloader is unlocked and it needs to be locked in order to pass safeynet. More and more apps are not allowing for detected unlocked bootloaders in which makes safetynet fail.
Wish I knew how to relock it... Little reluctant to use a random site's information... Xda probably has information on relocking it, wish I had a link to a good post.
Could it possibly brick my phone if I'm using a pro boot image an try to lock bootloader?
Any advice or help would be much appreciated thanks for your time.
I will follow-up more later as I'm walking out the door. I'm not convinced that we are on a different or should I say, incompatible boot.img. When I get home I need to do some research to see what is actually different in the boot.img when being compared each other (C.61 boot.img on OP9 and OP9 Pro).
Back history for anyone following along... I was unlocked, rooted, Google Play certified and on C.48. I upgraded via OTA, no reboot and chose an inactive slot. It did not work and soft bricked slot a. I lost root, was on C.48 still but on slot B. I successfully upgraded to C.61 but didn't have root. I could not find a good boot.img or patched_boot.img. I tried a stock OP9 Pro image and that got me working. That same user provided a patch img too so I tried that and obtained root as well.
Soooo what is the difference between the boot images on C.61 pro and non-pro OP9 models?
Stay tuned....!
Thanks I'll keep checking back on this
Unfortunately the difference is that the pro version is available to tinker with and the non pro version isn't. Sorry to state the obvious.
My phone so far is working fine on the OP9 Pro kernel. C.61 is rooted and Google Play is certified. All my previous Magisk config is there as well and modules. I'm not sure what the difference between the kernels are at this point but also not a kernel expert either.
Once the next full release comes out for OP9, I will swap it out.
@Harley1979 I got your PM and will follow-up with you there.