Database Develop

oreo n950n kt branded ims settings locked with otp key code

Upgraded to oreo on note 8 n950n
Volte and video phone deleted from dialer as they have on any past update. No biggie. Get into ims settings. Either through hidden kt menu or shortcut lite
But now ims settings requires a one time passcode
And supplies a key code that correlates to a password
No idea where to get key from.. please help!
T Mobile sucks without volte

In my country, the carrier requires you to take the device to activate VOLTE, maybe you need to go in person with your device to your carrier service center

When I was on Oreo I couldn't even access IMS settings on my F. Phone INFO/Shortcut Master wouldn't find the IMS settings menu for me. But I'm rooted & T-Mobile CSC still activated VoLTE & Wifi calling fine for me. But whatever, I'm back to Nougat & won't be running Oreo until things get worked out.

shouren04 said:
When I was on Oreo I couldn't even access IMS settings on my F. Phone INFO/Shortcut Master wouldn't find the IMS settings menu for me. But I'm rooted & T-Mobile CSC still activated VoLTE & Wifi calling fine for me. But whatever, I'm back to Nougat & won't be running Oreo until things get worked out.
Click to expand...
Click to collapse
How did you go back to Nougat from Oreo? Wouldn't that trip the Knox flag?
I know you are rooted, however just asking if I downgrade will I hit the Knog flag. I am extremely concerned as I am registered to my Org email and other apps which requires no trip of Knox flag along with no root.
Please suggest.
Thanks.

deepakrsarangi said:
How did you go back to Nougat from Oreo? Wouldn't that trip the Knox flag?
I know you are rooted, however just asking if I downgrade will I hit the Knog flag. I am extremely concerned as I am registered to my Org email and other apps which requires no trip of Knox flag along with no root.
Please suggest.
Thanks.
Click to expand...
Click to collapse
You can flash back to Nougat & flashing official FW in Odin should not trip Knox but I'm not taking any responsibility if somethig happens.
I have Exynos with TWRP installed so my Knox is already tripped. I switch back & forth from Oreo & Nougat with nandroids in TWRP.

shouren04 said:
You can flash back to Nougat & flashing official FW in Odin should not trip Knox but I'm not taking any responsibility if somethig happens.
I have Exynos with TWRP installed so my Knox is already tripped. I switch back & forth from Oreo & Nougat with nandroids in TWRP.
Click to expand...
Click to collapse
Thanks. Unfortunately I read from somewhere that even downgrading ROM trips knox. Not sure though. In case someone who has already tried please confirm.
Additionally if I flash G950U1 official ROM on a G950U phone would that still trip knox?

deepakrsarangi said:
Thanks. Unfortunately I read from somewhere that even downgrading ROM trips knox. Not sure though. In case someone who has already tried please confirm.
Additionally if I flash G950U1 official ROM on a G950U phone would that still trip knox?
Click to expand...
Click to collapse
I've never heard that either. Generally if you are are flashing official FWs in Odin Knox will not be tripped. And as you probably know you can't flash anything in Odin that is not for your specific device so Knox shouldn't be tripped.
I didn't realize you have a S8 since you are posting in the Note 8 forum but it should be the same. You can flash the unlocked FW on a carrier device but you have to use the PrinceComsy modified Odin to do so. Still it should not trip Knox. What's mainly important is you have to flash FWs with the same version bootloader you are on now. You can not downgrade BL, even if you tried Odin will not let you.

shouren04 said:
I've never heard that either. Generally if you are are flashing official FWs in Odin Knox will not be tripped. And as you probably know you can't flash anything in Odin that is not for your specific device so Knox shouldn't be tripped.
I didn't realize you have a S8 since you are posting in the Note 8 forum but it should be the same. You can flash the unlocked FW on a carrier device but you have to use the PrinceComsy modified Odin to do so. Still it should not trip Knox. What's mainly important is you have to flash FWs with the same version bootloader you are on now. You can not downgrade BL, even if you tried Odin will not let you.
Click to expand...
Click to collapse
Thanks a lot. Since Note 8 and S8 has almost similar in everything apart from few hardware enhancements in Note 8, from firmware prospect both should be considered as same..
But I read in one of the thread in XDA forum that after Oreo upgrade the bootloader has been changed and you can't downgrade.
As you confirmed if the Odin doesn't even allow FWs which would not be officially compatible then that is an awesome idea. My fear is and always be with KNOX trip since a lot is dependent on that including my work profile email and stuff.
If you/someone knows a way to turn on IMS service switch in Oreo then I won't require downgrade. Essentially I need the VoLTE to turn ON.
Tuff luck it is.

deepakrsarangi said:
Thanks a lot. Since Note 8 and S8 has almost similar in everything apart from few hardware enhancements in Note 8, from firmware prospect both should be considered as same..
But I read in one of the thread in XDA forum that after Oreo upgrade the bootloader has been changed and you can't downgrade.
As you confirmed if the Odin doesn't even allow FWs which would not be officially compatible then that is an awesome idea. My fear is and always be with KNOX trip since a lot is dependent on that including my work profile email and stuff.
If you/someone knows a way to turn on IMS service switch in Oreo then I won't require downgrade. Essentially I need the VoLTE to turn ON.
Tuff luck it is.
Click to expand...
Click to collapse
Yes Oreo has a new bootloader but you can still go back to Nougat, but latest Nougat. When they say you can't downgrade BL, you can't downgrade versions.
I don't know what variant you have but for example, I have F. Latest Nougat is 3BRB5 or 3BRA8. Oreo is 3CRC1. The 5 digit from the end is the BL version. If the number is the same, you can flash. If the number you have now is higher than a FW you wish to flash tbat has a lower number, you can't, that's what is meant by can't downgrade BL.
Oreo, IMS setting, yes I do know how to launch it. I'm assuming you are Using Phone INFO or Shortcut Master & can't launch. But with Shortcut Master you still can. Instead of launching 467 as you normally would, click on Explore instead to open App Explorer. From there click the second option, IMS Settings will launch.
If you have a N & have the passcode issue as mentioned in this thread, that I don't know anything about. Although I believe I remember a post somewhere that someone posted the codes.

shouren04 said:
Yes Oreo has a new bootloader but you can still go back to Nougat, but latest Nougat. When they say you can't downgrade BL, you can't downgrade versions.
I don't know what variant you have but for example, I have F. Latest Nougat is 3BRB5 or 3BRA8. Oreo is 3CRC1. The 5 digit from the end is the BL version. If the number is the same, you can flash. If the number you have now is higher than a FW you wish to flash tbat has a lower number, you can't, that's what is meant by can't downgrade BL.
Oreo, IMS setting, yes I do know how to launch it. I'm assuming you are Using Phone INFO or Shortcut Master & can't launch. But with Shortcut Master you still can. Instead of launching 467 as you normally would, click on Explore instead to open App Explorer. From there click the second option, IMS Settings will launch.
If you have a N & have the passcode issue as mentioned in this thread, that I don't know anything about. Although I believe I remember a post somewhere that someone posted the codes.
Click to expand...
Click to collapse
Thanks for this detailed info.
Apologies for being so naive. Mine is 2CRC5 Oreo. Unfortunately I don't know which variant you referred when you say F or N.
But going by your instructions I tried and got an error while invoking the 2nd option i. e. imsserviceswitchactivity. I assume this is related to rooting as it says " su not found. "
If yes, then please suggest me something without rooting to enable the ims switch.
Attached here the screenshot of the error message. Please help.

deepakrsarangi said:
Thanks for this detailed info.
Apologies for being so naive. Mine is 2CRC5 Oreo. Unfortunately I don't know which variant you referred when you say F or N.
But going by your instructions I tried and got an error while invoking the 2nd option i. e. imsserviceswitchactivity. I assume this is related to rooting as it says " su not found. "
If yes, then please suggest me something without rooting to enable the ims switch.
Attached here the screenshot of the error message. Please help.
Click to expand...
Click to collapse
Ah I forgot you have S8, that's why I'm not familiar with 2CRC5. F & N are international models. You have a U which is US.
Says su not found which means you need root access to open it. I don't know of any other way. Be sure to verify with the S8 guys before trying to go back to Nougat. Guys on Note 8 have done it but I wouldn't want you to brick your phone in case something is different with the S8.
Since you have a U, that's got me thinking. Are you using your carrier's firmware? If yes VoLTE should already be enabled if they support VoLTE.
---------- Post added 04-07-2018 at 12:00 AM ---------- Previous post was 04-06-2018 at 11:51 PM ----------
In Settings/About Phone under Service Provider SW Ver, what is you CSC (XXX/XXX/XXX)?

shouren04 said:
Ah I forgot you have S8, that's why I'm not familiar with 2CRC5. F & N are international models. You have a U which is US.
Says su not found which means you need root access to open it. I don't know of any other way. Be sure to verify with the S8 guys before trying to go back to Nougat. Guys on Note 8 have done it but I wouldn't want you to brick your phone in case something is different with the S8.
Since you have a U, that's got me thinking. Are you using your carrier's firmware? If yes VoLTE should already be enabled if they support VoLTE.
---------- Post added 04-07-2018 at 12:00 AM ---------- Previous post was 04-06-2018 at 11:51 PM ----------
In Settings/About Phone under Service Provider SW Ver, what is you CSC (XXX/XXX/XXX)?
Click to expand...
Click to collapse
Yeah mine is US model G950U S8 Sprint branded, officially network unlocked by Sprint.
The CSC in my case is SPR/XAA/SPR. I haven't changed the carrier firmware yet in fear of Knox trip. SPRINT does have VoLTE but through their CallingPlus app in beta, not native VoLTE calls.
Moreover after network unlock I moved to India and through IMS settings I did enable VoLTE and enjoyed native calls with Indian operators. After upgrade to Oreo on March 16th, the IMS switch was auto disabled and the ims application didn't get invoked. So now stuck in a no man's land.
Is there any other method (adb or something else) to enable VoLTE?

deepakrsarangi said:
Yeah mine is US model G950U S8 Sprint branded, officially network unlocked by Sprint.
The CSC in my case is SPR/XAA/SPR. I haven't changed the carrier firmware yet in fear of Knox trip. SPRINT does have VoLTE but through their CallingPlus app in beta, not native VoLTE calls.
Moreover after network unlock I moved to India and through IMS settings I did enable VoLTE and enjoyed native calls with Indian operators. After upgrade to Oreo on March 16th, the IMS switch was auto disabled and the ims application didn't get invoked. So now stuck in a no man's land.
Is there any other method (adb or something else) to enable VoLTE?
Click to expand...
Click to collapse
Oh man, totally didn't expect that one. Unfortuantely in your case the only way I know is to root which is out of the question. I could be wrong but I don't think there is anything that can be done through adb, generally it's enabled by CSC. Hopefully the dev for Phone INFO/Shortcut Master will figure out how to get the secret codes working with Oreo.

shouren04 said:
Oh man, totally didn't expect that one. Unfortuantely in your case the only way I know is to root which is out of the question. I could be wrong but I don't think there is anything that can be done through adb, generally it's enabled by CSC. Hopefully the dev for Phone INFO/Shortcut Master will figure out how to get the secret codes working with Oreo.
Click to expand...
Click to collapse
The other way could be downgrading to 7.0, where the IMS setting was accessible. My fear is knox trip, if not I can downgrade. What would you suggest?

deepakrsarangi said:
The other way could be downgrading to 7.0, where the IMS setting was accessible. My fear is knox trip, if not I can downgrade. What would you suggest?
Click to expand...
Click to collapse
Yeah, the knox part is the questionable part as obviously it can't be reversed if tripped. I don't want to say something & mistakenly have it trip. But as we talked about flashing in Odin back to Nougat should not trip knox however you stated you read otherwise?

shouren04 said:
Yeah, the knox part is the questionable part as obviously it can't be reversed if tripped. I don't want to say something & mistakenly have it trip. But as we talked about flashing in Odin back to Nougat should not trip knox however you stated you read otherwise?
Click to expand...
Click to collapse
Thanks. I tried the app earlier too. The VoLTE option is not there. I don't want to downgrade unless I find a way to enable it.
I have searched over internet a lot and found mixed responses about KNOX tripping during downgrade or any unofficial try related to firmware.
I will wait for next few days for any help regarding the VoLTE enabler app or procedure. If not, I have the Nougat latest firmware ready with me(as you suggested earlier - same bootloader version). Eventually I have to go back. VoLTE is a must for me use this device in India with 4G connections.
Hope you may show some new light towards this fix.

shouren04 said:
Yeah, the knox part is the questionable part as obviously it can't be reversed if tripped. I don't want to say something & mistakenly have it trip. But as we talked about flashing in Odin back to Nougat should not trip knox however you stated you read otherwise?
Click to expand...
Click to collapse
Finally I downgraded to the latest Nougat ROM available for this device. Everything was smooth. I was able to enable VoLTE as we discussed. Thanks to you for providing me confidence.
I'll still wait for anyone confirming IMS app invoke on Oreo (without Root) before upgrade. Till then Happy with Nougat ROM.
Thanks again.

deepakrsarangi said:
Finally I downgraded to the latest Nougat ROM available for this device. Everything was smooth. I was able to enable VoLTE as we discussed. Thanks to you for providing me confidence.
I'll still wait for anyone confirming IMS app invoke on Oreo (without Root) before upgrade. Till then Happy with Nougat ROM.
Thanks again.
Click to expand...
Click to collapse
Nice, good to hear! :good:
I did ask the dev for Phone INFO/Shorcut Master about Oreo support for the secret codes. He's aware of the issue & said he'll try to find a way to fix it. Hopefully he figures it out.

shouren04 said:
Nice, good to hear! :good:
I did ask the dev for Phone INFO/Shorcut Master about Oreo support for the secret codes. He's aware of the issue & said he'll try to find a way to fix it. Hopefully he figures it out.
Click to expand...
Click to collapse
Thanks. Many of us are waiting for this fix btw. There are several threads on this on XDA.
I too hope for an efficient fix soon.

Hi, I have cracked the password for the otp key, you can get the java program from below
https://1drv.ms/u/s!AnEZ2ptLoUQKgfV6fNSZIyQlf-cC5Q
Your pc must have Java installed.
1. run the java program by:
java OTP_Cracker yyit4(replace this key with your otp key)
the program output should be：
key:yyit4 pwd:1406604358
key:yyit4 pwd:1405418437
key:yyit4 pwd:1404232516
key:yyit4 pwd:1403046595
key:yyit4 pwd:1401860674
key:yyit4 pwd:1400674753
One of the pwd should be ok for the key. Entering the pwd in your phone then you can get in the volte settings.

Note 8 Root Advancement Query

Hello, I'm wondering if they've made any advancement on the Samfail root method for the Note 8 AT&T version. I'm finding that I'm running into circumstances where I need to be able to flash a zip. This is still not possible, correct?

2Tone23 said:
Hello, I'm wondering if they've made any advancement on the Samfail root method for the Note 8 AT&T version. I'm finding that I'm running into circumstances where I need to be able to flash a zip. This is still not possible, correct?
Click to expand...
Click to collapse
Just check the Samfail thread. It's up to v3 for the latest 7.1.1 software we have. It does not root Oreo, but it will downgrade you from it back to 7.1.1 to be able to root.

Jammol said:
Just check the Samfail thread. It's up to v3 for the latest 7.1.1 software we have. It does not root Oreo, but it will downgrade you from it back to 7.1.1 to be able to root.
Click to expand...
Click to collapse
Thank you, Jammol. I'm actually rooted, but I was out of the loop due awhile and I was wondering if full root had been managed. They finally achieved it on the Note 5 AT&T version, only after I got rid of it. Hoping lightning will strike twice, you know?

2Tone23 said:
Thank you, Jammol. I'm actually rooted, but I was out of the loop due awhile and I was wondering if full root had been managed. They finally achieved it on the Note 5 AT&T version, only after I got rid of it. Hoping lightning will strike twice, you know?
Click to expand...
Click to collapse
Full root as in TWRP and such? We have full root but with a locked bootloader. Flashfire can be used to flash stock roms for the Snapdragon variant. Safestrap was just released for it as well but currently only the "Stock" slot can be used. And yes the 80% battery limit is very much still there.

So I can actually flash custom roms with this lock bootloader on this variant? Also, safestrap will allow me to flash custom roms as well?

Jammol said:
Full root as in TWRP and such? We have full root but with a locked bootloader. Flashfire can be used to flash stock roms for the Snapdragon variant. Safestrap was just released for it as well but currently only the "Stock" slot can be used. And yes the 80% battery limit is very much still there.
Click to expand...
Click to collapse
So I can actually flash custom roms with this locked bootloader on this variant?. Also, safestrap will allow me to flash custom roms as well? I hope I understand you right, Jammol. To be able to finally do that would make me a happy man. Also, is there any advantage to using Safestrap over Samfail? I used Safestrap with my S5.

2Tone23 said:
So I can actually flash custom roms with this locked bootloader on this variant?. Also, safestrap will allow me to flash custom roms as well? I hope I understand you right, Jammol. To be able to finally do that would make me a happy man. Also, is there any advantage to using Safestrap over Samfail? I used Safestrap with my S5.
Click to expand...
Click to collapse
Correct, but you can't get to Safestrap without being rooted first, which requires Samfail.

Jammol said:
Correct, but you can't get to Safestrap without being rooted first, which requires Samfail.
Click to expand...
Click to collapse
Thanx. I'm Samfail rooted already. Going to install safestrap. Can you direct toward some custom stock roms that might flash? I've had no luck thus far.... And thank you for all the info. If not for you I wouldn't even know Safestrap and flashing was even available.

2Tone23 said:
Thanx. I'm Samfail rooted already. Going to install safestrap. Can you direct toward some custom stock roms that might flash? I've had no luck thus far.... And thank you for all the info. If not for you I wouldn't even know Safestrap and flashing was even available.
Click to expand...
Click to collapse
Currently there are only 2 roms we can flash. FENNEC and Culpeo.
FENNEC is based on the U1 (unlocked firmware), so there's no carrier bloatware.
Culpeo is based on U or carrier firmware. The bloat will come with the CSC you flash for your particular firmware. There are CSC edits in there for things such as VoLTE, Wi-Fi Calling, etc.
These are both based on the latest 7.1.1 version respectively. I have personally ran both but I was partial to FENNEC because I hate carrier bloat.
Both are located on the Development section. There are more roms coming so don't be deterred.

Jammol said:
Currently there are only 2 roms we can flash. FENNEC and Culpeo.
FENNEC is based on the U1 (unlocked firmware), so there's no carrier bloatware.
Culpeo is based on U or carrier firmware. The bloat will come with the CSC you flash for your particular firmware. There are CSC edits in there for things such as VoLTE, Wi-Fi Calling, etc.
These are both based on the latest 7.1.1 version respectively. I have personally ran both but I was partial to FENNEC because I hate carrier bloat.
Both are located on the Development section. There are more roms coming so don't be deterred.
Click to expand...
Click to collapse
Jammol, I really appreciate your responsiveness and all of the knowledge you've provided. Thanks you!

Jammol, trying to figure out why Safestrap won't take. Busybox up and running. After hitting install it goes thru its paces and says I install successfully, or something similar, but above that where it says State it still reads not installed. I see it with granted access in Su. But when rebooting I do not get the splash screen. Any ideas?

2Tone23 said:
Jammol, trying to figure out why Safestrap won't take. Busybox up and running. After hitting install it goes thru its paces and says I install successfully, or something similar, but above that where it says State it still reads not installed. I see it with granted access in Su. But when rebooting I do not get the splash screen. Any ideas?
Click to expand...
Click to collapse
I have the free version of Busy Box installed. Tried installing the pro version in case that would somehow facilitate the installation of Safestrap and the pro version won't install either. The notice suggests I try installing in another location. Not sure how to do that. Can anyone advise me on this and /or how I can get Safestrap to install?

2Tone23 said:
Jammol, trying to figure out why Safestrap won't take. Busybox up and running. After hitting install it goes thru its paces and says I install successfully, or something similar, but above that where it says State it still reads not installed. I see it with granted access in Su. But when rebooting I do not get the splash screen. Any ideas?
Click to expand...
Click to collapse
In the Safestrap thread there were a few users that had that issue occur. I don't know what the Fix was for them, if it was fixed, as I haven't followed that development for a few days now. I suggest giving the OP of that thread a full read through again and read through the comments/replies of what others have done so far to solve their issues.

Thanx Jammol. Actually perused that before my last post. Will look again. Hope I missed something, but I dont think so.

Jammol said:
In the Safestrap thread there were a few users that had that issue occur. I don't know what the Fix was for them, if it was fixed, as I haven't followed that development for a few days now. I suggest giving the OP of that thread a full read through again and read through the comments/replies of what others have done so far to solve their issues.
Click to expand...
Click to collapse
Thanx Jammol. Actually perused that before my last post. Will look again. Hope I missed something, but I dont think so.

2Tone23 said:
Thanx Jammol. Actually perused that before my last post. Will look again. Hope I missed something, but I dont think so.
Click to expand...
Click to collapse
No problem. Let me know. There are some bugs with it though so posting Safestrap related questions there would be the best thing to do. I merely fiddled with it for about a day at most and had to return to stock(work reasons).

Thanks, J. Really appreciate your feedback. Will let you know if something gives.

Jammol said:
No problem. Let me know. There are some bugs with it though so posting Safestrap related questions there would be the best thing to do. I merely fiddled with it for about a day at most and had to return to stock(work reasons).
Click to expand...
Click to collapse
Thanks, J. Really appreciate your feedback. Will let you know if something gives.
(Eventually, I'm going to get this reply thing right. ?)

2Tone23 said:
Thanks, J. Really appreciate your feedback. Will let you know if something gives.
(Eventually, I'm going to get this reply thing right. ?)
Click to expand...
Click to collapse
Lol, no problem.

Canadian P20 Pro version CLT-L04, Questions about Magisk and bootloader unlock

Hi! I picked up my Canadian P20 Pro last week and couldn't be happier. It's been many years since I've owned a rootable device though and a lot has changed! I've done my best to read through all the guides for rooting the P20 Pro and it's only lead to further confusion as there seem to be many recent advancements. There seem to be a lot of different versions of this phone too. So I have some questions I'm hoping someone can answer easily! Let's assume my bootloader is already unlocked....
1) there's a really great guide on rooting the P20 Pro using All In One tool. But that requires flashing TWRP to achieve root using Magisk. I do not require TWRP as I only want root and do not wish to flash any roms.
a) is there a way to root with Magisk and NOT flash TWRP? I can't seem to find a straight answer on this...
b) failing that, can TWRP safely be removed and keep root afterward?
2) after unlocking the bootloader I was welcomed by a terrifyingly orange warning about my now 'unsafe' phone. I've read mixed things on hiding this. Is there currently a way to hide it?
3) how does the process work for OTA updates on an unlocked bootloader assuming there is no TWRP? I've read differing opinions on the necessity of flashing a no_check.img to the ramdisk and have no understanding of the new security checks on these phones. Can I run risk of bricking my phone through an automated update?
Ultimately I'm scared of forgetting TWRP is on my phone and accepting an update that'll brick it. Any information is welcome as are similar questions!

I am also curious if there is a good root process for this phone. Find anything yet?

djparent said:
Hi! I picked up my Canadian P20 Pro last week and couldn't be happier. It's been many years since I've owned a rootable device though and a lot has changed! I've done my best to read through all the guides for rooting the P20 Pro and it's only lead to further confusion as there seem to be many recent advancements. There seem to be a lot of different versions of this phone too. So I have some questions I'm hoping someone can answer easily! Let's assume my bootloader is already unlocked....
1) there's a really great guide on rooting the P20 Pro using All In One tool. But that requires flashing TWRP to achieve root using Magisk. I do not require TWRP as I only want root and do not wish to flash any roms.
a) is there a way to root with Magisk and NOT flash TWRP? I can't seem to find a straight answer on this...
b) failing that, can TWRP safely be removed and keep root afterward?
2) after unlocking the bootloader I was welcomed by a terrifyingly orange warning about my now 'unsafe' phone. I've read mixed things on hiding this. Is there currently a way to hide it?
3) how does the process work for OTA updates on an unlocked bootloader assuming there is no TWRP? I've read differing opinions on the necessity of flashing a no_check.img to the ramdisk and have no understanding of the new security checks on these phones. Can I run risk of bricking my phone through an automated update?
Ultimately I'm scared of forgetting TWRP is on my phone and accepting an update that'll brick it. Any information is welcome as are similar questions!
Click to expand...
Click to collapse
I have a Canadian CLT-L04 that i rebranded and rooted to CLT-L29 with the guide on here.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
if you want better firmware compared to version 109 thats still on clt-l04 you can follow this guide, it worked well for me. (don't wait canadian OTA it'll take too long)
1) quite sure that TWRP is the easiest and safest way to root. Currently unaware of a better way to root the phone.
b) if you remove TWRP by flashing a stock recovery_ramdisk, root is kept. If you do an OTA though you might lose root.
2) thats here to stay i believe. Cannot find a way to hide it currently.
3)In this guide under the "install an OTA Stock Update: PC Method" you will find all the information you need.
cheers

I finally found the info I needed in this thread:
https://forum.xda-developers.com/hu...ide-getting-started-unlock-twrp-root-t3806180
Overall it was a very simple process and took less than an hour including reading. Once you've got your bootloader unlock code the all in one tool handles it from there. Unlock the bootloader, flash TWRP, reboot into TWRP, flash Magisk and you're done. You can flash the no_check file over TWRP if you want to be ready for updates but I decided to leave TWRP on for now. Loving having root on this phone so far!

On a different note, has anyone discovered any ROMs for this phone yet that can handle the notch? I almost tried Lineage until I found out there is no notch support. I've grown strangely fond of the thing for some reason lol

rhinogator said:
I have a Canadian CLT-L04 that i rebranded and rooted to CLT-L29 with the guide on here.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
if you want better firmware compared to version 109 thats still on clt-l04 you can follow this guide, it worked well for me. (don't wait canadian OTA it'll take too long)
1) quite sure that TWRP is the easiest and safest way to root. Currently unaware of a better way to root the phone.
b) if you remove TWRP by flashing a stock recovery_ramdisk, root is kept. If you do an OTA though you might lose root.
2) thats here to stay i believe. Cannot find a way to hide it currently.
3)In this guide under the "install an OTA Stock Update: PC Method" you will find all the information you need.
cheers
Click to expand...
Click to collapse
Did you by any chance find a way to go back to CLT-L04 by any chance?

mrnovanova said:
Did you by any chance find a way to go back to CLT-L04 by any chance?
Click to expand...
Click to collapse
unfortunately no

mrnovanova said:
Did you by any chance find a way to go back to CLT-L04 by any chance?
Click to expand...
Click to collapse
If you do a full backup of the L04 in TWRP before rebranding you should be able to go back to it easily at any time, just remember to save it somewhere safe other than the phone itself. If you've already flashed and are looking to go back you may find someone willing to share a stock backup if you ask around. But always best to do your own backup first, then you can go back whenever you like!

djparent said:
If you do a full backup of the L04 in TWRP before rebranding you should be able to go back to it easily at any time, just remember to save it somewhere safe other than the phone itself. If you've already flashed and are looking to go back you may find someone willing to share a stock backup if you ask around. But always best to do your own backup first, then you can go back whenever you like!
Click to expand...
Click to collapse
I never thought of backing up my L04. ??? I guess I'm stuck with L29. Oh well... Thanks for the reply.

help with rebranding tutorial
mrnovanova said:
I never thought of backing up my L04. I guess I'm stuck with L29. Oh well... Thanks for the reply.
Click to expand...
Click to collapse
bro did u use the same files as the main tutorial that you share? cause I have the L04 but the mexican one, and I want to rebrand it
but i'm a noob in this things, hope you can help me.:good:

Search for dladz's tutorial.
ON THIS THREAD : https://forum.xda-developers.com/hu...to-root-debrand-remove-retail-t3788326/page46
Page 16
Sent from my Google Pixel 2 XL using XDA Labs

Anyone unlocked bootloader and rooted recently for the L04 model with 120(C792) Sept-2018 update?
Im scared to update before unlocking and rooting as the update might do something to fastboot etc. (this has happened to LG)
If not, then Ill update but if so, Ill just not update and unlock it as it is.

JF-GINO said:
Anyone unlocked bootloader and rooted recently for the L04 model with 120(C792) Sept-2018 update?
Im scared to update before unlocking and rooting as the update might do something to fastboot etc. (this has happened to LG)
If not, then Ill update but if so, Ill just not update and unlock it as it is.
Click to expand...
Click to collapse
It's really easy to update once you've unlocked, I would suggest unlocking first if you have concerns. I have an L04 as well and just updated to 120 with no problems.

djparent said:
It's really easy to update once you've unlocked, I would suggest unlocking first if you have concerns. I have an L04 as well and just updated to 120 with no problems.
Click to expand...
Click to collapse
Hey, Thanks djparent, I unlocked and updated as you suggested.
Everything working properly, just need to root/twrp etc. now.
Thnaks again

No problem, glad it worked for you. I've soft bricked and recovered my phone a few times now experimenting so if you run into any problems I'm happy to help! Lots to learn with the P20.

I have a CLT-L04 8.1.0.136 C69 with October security patch from Mexico I want to rebrand it to CLT- L29 to get wifi calling and get rid of all the bloatware. Could I use this tutorial from dladz's tutorial:
ON THIS THREAD : https://forum.xda-developers.com/hua...3788326/page46
Page 16
One of the notes mentions the following: I) ]NOTE*** If you are on a later firmware than 120, please do not attempt this guide!!
I have only rooted one phone before in my life so I am no expert. I do no want to mess up my phone becuse it is the only one that I have. Also If I unlock the boot loader and rebrand can i get OTAs and the upcoming Pie release? Thanks for the help!

LineageOS 15.1 on L04
I installed LineageOS 15.1 on my L04 with out any issue. Some things to consider. USB-C will only charge the device, Titanium Backup will install but doesn't get root access and you'll miss the camera application.

Vedrick said:
I installed LineageOS 15.1 on my L04 with out any issue. Some things to consider. USB-C will only charge the device, Titanium Backup will install but doesn't get root access and you'll miss the camera application.
Click to expand...
Click to collapse
Did you install it with a locked bootloader ? I really dont feel like paying for an unlock code. Would like to try Lineage though.

matever said:
Did you install it with a locked bootloader ? I really dont feel like paying for an unlock code. Would like to try Lineage though.
Click to expand...
Click to collapse
I do have an unlocked bootloader. Truth is i'm addicted to Rom's lol. That in mind I have tried every Rom, kernel, flash-able zip within this Forum and I can't brick this thing. L04 Canadian. Lineage is the best Rom for our device.
Roms that work:
- Lineage - Hauwei camera can be installed and works, dark mode works well.
------- Doesn't work: USB-C audio, NFC, RAW Option in the camera, Second ear piece as speaker, main speaker works well.
- First Ever Android 9 - Being the first build it works well. (Note: When I installed this rom I never installed the RemoveEncryption-P20Pro.zip) Seemed to work just fine without it. I did run it just because I wanted to see if it would brick my phone. It didn't.
-------Doesn't work: Dark mode, NFC, RAW Option in camera, Second ear piece as speaker, main speaker works well, seems to kill TWRP. eRecovery needed to get TWRP to function.
- AOSP 9 - Berkeley-Flex - Do Not Use...not ready.

Vedrick said:
I do have an unlocked bootloader. Truth is i'm addicted to Rom's lol. That in mind I have tried every Rom, kernel, flash-able zip within this Forum and I can't brick this thing. L04 Canadian. Lineage is the best Rom for our device.
Roms that work:
- Lineage - Hauwei camera can be installed and works, dark mode works well.
------- Doesn't work: USB-C audio, NFC, RAW Option in the camera, Second ear piece as speaker, main speaker works well.
- First Ever Android 9 - Being the first build it works well. (Note: When I installed this rom I never installed the RemoveEncryption-P20Pro.zip) Seemed to work just fine without it. I did run it just because I wanted to see if it would brick my phone. It didn't.
-------Doesn't work: Dark mode, NFC, RAW Option in camera, Second ear piece as speaker, main speaker works well, seems to kill TWRP. eRecovery needed to get TWRP to function.
- AOSP 9 - Berkeley-Flex - Do Not Use...not ready.
Click to expand...
Click to collapse
What did you use to unlock your bootloader ? Funky ? Also I know what you mean I am addicted to Roms as well :laugh: Thanks for all the info I really appreciate it.

SM-N960F/D Odin flashing - blunder after blunder.... :(

Ok... So where to begin...
I've searched the threads for a few days now and tried several flashing methods and tools, but I'm having no luck. So please bare with me, and I will get into it...
I recently purchased a new Note 9 international unlocked model. I was super excited and ready to get it running. Except, I started it up and then no Bixby Voice. Unlike most, I prefer to use it and find it helpful to me regularly, so I'd like to keep it. Anyway, when pressing the button I received the much noted "Bixby Voice is not available in your country" message. Well, I found from Samsung support live chat, that this is because of two reasons. One, I currently live in Japan. Two, the phone is a Singapore model phone. My immediate thought was "Oh, ok well, I'll just flash it with another country's firmware then". Seemed easy enough. I flashed it with firmware baring an OXM csc, and after booting up I noticed the the VoLTE feature that was not select-able before was now able to turned on. "Ooow, extra win!" I thought, but of course same issue with bixby. So I searched and found a csc for a location that has bixby is available and is also a carrier unlocked Exynos chipset firmware (XEU). I flashed this, but guess what... still no Bixby Voice. Frustrated, I began looking into changing the Sales code. Using the *#272*IMEI# code and found that MM1 was the sales code for some reason. I changed this to XEU and the phone rebooted. I restored and then tried Bixby Voice again... same. Except, I noticed I also lost the VoLTE option completely. It doesn't even show in the menu bar anymore. I tried the code again to change the sales code back, but now I get error "Connection problem or invalid MMI code." So now, I lost that too. "To hell with it", I thought. I'll flash it back to the old firmware... nope. Now I get:
SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1
This will sometimes change slightly if I try to flash a single part of the new firmware, BL, AP, CSC, etc...
I have done some research and found via the serial number that the firmware I should have installed is: N960FXXU1ARH5_N960FOXM1ARGD_N960FXXU1ARGC_N960FXXU 1ARH5_XSP (according to the Chimera Mobile tool)
I've obtained this, but I still get the same Revision error. I found that the one last one I successfully flashed is a newer version than the others. So now what can I do? Is it possible I can just manually manipulate the CSC details? I rooted the phone and got ES Explorer going, set all the access rights to R/W but I cant find the /System/CSC folder that people keep going on about. Did they do away with that on the Note 9?
It looks like I also have some regional troubles with the Play store too.
WTH... I'm really not sure what to do here. Can anyone please help? I'll be satisfied if I can just get it back to the stock firmware...

Decoding SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1 come out to: Software Revision check fail, you have 2 and it's expecting 1.
That does indeed sound like you've installed a newer version and it's not letting you roll back the device. You may now need to wait for Singapore's stock firmware to be updated to the same or newer and get a copy of that.

who uses bixby use google assistant for peats sake!!!"!!!!

willhemmens said:
Decoding SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1 come out to: Software Revision check fail, you have 2 and it's expecting 1.
That does indeed sound like you've installed a newer version and it's not letting you roll back the device. You may now need to wait for Singapore's stock firmware to be updated to the same or newer and get a copy of that.
Click to expand...
Click to collapse
Hi willhemmens! Thanks for replying back.
I was also speculating the same thing about having to wait for the revision, but I know the people here are significantly more knowledgeable, so I thought I'd try to pick some brains. My first though was that there must be something in one of the package files that identify to the phone what "version" it is, and then perhaps that can be modified and then re-packaged. But if that were the case, this would be the best place on the planet to verify that. I have tools to un-package and repackage, maybe I'll make a duplicate copy and tinker around in it.
It looks like everyone is complaining about it. It's been a while since I rooted a device (7 years maybe?), so I hadn't realized Samsung took a dump in the downgrade pool. I also found some other new 'glorious' features they've graced us with-after the fact of course. Now, when I un-root... it's still flagged as modified! Woohoo. ....Fricken' KNOX. Now all of the nifty Samsung apps are blocked. Is it just me, or has Samsung turned a little extra Ass-hat recently?
Anyway, I guess I'll have to deal with this lame iOS quality version of Oreo until then... By the way, off the top of your head do you know where I can go to keep an eye out for that update to happen? All I know is SamMobile.com
Thanks again.

mikey_sk said:
who uses bixby use google assistant for peats sake!!!"!!!!
Click to expand...
Click to collapse
Hi Mikey! Yeah, I suppose your right. I've just been using it a lot and have gotten accustomed to it. Plus I enjoy creating my own custom Bixby voices, attitudes, and responses. Bixby on my Note 8 has split personality.
Luckily she doesn't randomly laugh in the dark like Alexa. If she did she'd fly out the window like a Note 7.

csc was omc and now odm.

bober10113 said:
csc was omc and now odm.
Click to expand...
Click to collapse
HI Bober10113! Thanks for your reply. I was able to find my way there, but It seems the csc feature files are encrypted now. I'm still looking through the threads for something about how to decrypt/encrypt them, but I haven't found anything yet.

VetteMike69 said:
HI Bober10113! Thanks for your reply. I was able to find my way there, but It seems the csc feature files are encrypted now. I'm still looking through the threads for something about how to decrypt/encrypt them, but I haven't found anything yet.
Click to expand...
Click to collapse
Actually, I just found a video on YouTube where Yakapa40 is able to unpack the xml files using some "cscfeature" executable.
@yakapa40
Is there any chance you might be willing to share your "cscfeature.exe" file for unpacking the feature XML files in the CSC?

VetteMike69 said:
Actually, I just found a video on YouTube where Yakapa40 is able to unpack the xml files using some "cscfeature" executable.
@yakapa40
Is there any chance you might be willing to share your "cscfeature.exe" file for unpacking the feature XML files in the CSC?
Click to expand...
Click to collapse
Ah sorry, nevermind... I was able to make a ps1 for it instead. I'm good one decoding and encoding the XMLs now.

@VetteMike69
if you need it , you have an automatic encode/decode feature here in post 5 : https://forum.xda-developers.com/galaxy-note-9/how-to/n960f-n960n-n960u-n960u1-n960w-n9600-t3833721
regards
edit : sorry no licence , but you can make your own patch file

yakapa40 said:
@VetteMike69
if you need it , you have an automatic encode/decode feature here in post 5 : https://forum.xda-developers.com/galaxy-note-9/how-to/n960f-n960n-n960u-n960u1-n960w-n9600-t3833721
regards
Click to expand...
Click to collapse
you made the exe with freeware(advance bat to exe converter)that only works on your PC. read the software policy.. its clearly written that what you compile only works on 1 computer.
anyways for everyone else, here is a proper tool:
https://1drv.ms/f/s!AhXVLDDj8g3Agdl8B0jk3H1dqccrXw

bober10113 said:
you made the exe with freeware(advance bat to exe converter)that only works on your PC. read the software policy.. its clearly written that what you compile only works on 1 computer.
anyways for everyone else, here is a proper tool:
https://1drv.ms/f/s!AhXVLDDj8g3Agdl8B0jk3H1dqccrXw
Click to expand...
Click to collapse
Hi bober, don't know where else to post this, so posting it here...I have seen a bunch of your posts and it seems you've figured out a way to use Canadian CSC on the 960 F/DS...i have a few questions:
1- First step is install TWRP?
2- then root?
3- do I have to change the actual firmware of the device? Mine is a singapore unit
4- Once I change CSC, how are updates handled after that if I want to keep using stock firmware?
5- If I can't do OTA, then how will I update to the latest version and security patches? Do I download these for the Canada version? or the Singapore version?
Any help would be highly appreciated!!

hkalltheway said:
Hi bober, don't know where else to post this, so posting it here...I have seen a bunch of your posts and it seems you've figured out a way to use Canadian CSC on the 960 F/DS...i have a few questions:
1- First step is install TWRP?
2- then root?
3- do I have to change the actual firmware of the device? Mine is a singapore unit
4- Once I change CSC, how are updates handled after that if I want to keep using stock firmware?
5- If I can't do OTA, then how will I update to the latest version and security patches? Do I download these for the Canada version? or the Singapore version?
Any help would be highly appreciated!!
Click to expand...
Click to collapse
i think you should weigh in what you want to achieve by changing csc and if it really is worth rooting for.
i rooted for custom roms, sound mods and just sheer control over my device.
but this comes with a price:
no samsung pay ( yet)( can always unroot)
tripped knox fuse, so probably no warranty. depends.(once tripped, this cannot be reverted)
misc apps detect root and might no longer root.(can always unroot)
so you should read up and get informed on what you need and if you need root/twrp.
concerning updates once rooted:
either use custom roms. BL and CP can be manually updated via stock firmware while custom rom keeps the system up to date.
or flash full stock firmware each time then re-root.
in both cases above, firmware files to be used are for exynos F devices. forget the canadian firmware, you cant flash that since it's for snapdragon devices.

yakapa40 said:
@VetteMike69
if you need it , you have an automatic encode/decode feature here in post 5 : https://forum.xda-developers.com/galaxy-note-9/how-to/n960f-n960n-n960u-n960u1-n960w-n9600-t3833721
regards
edit : sorry no licence , but you can make your own patch file
Click to expand...
Click to collapse
Hi @yakapa40!
Thank you, this looks like it'll be a bit more convenient than the one I made previously. I'll put it on record for next time. Luckily I was able to find what prevented me from flashing the older revision CSC and modify that. So now I was able to use Odin to drop down my PDA and CSC while keeping the newer Bootloader and Baseband. I guess it's a bit of a Frankin'-Firm now. Whats weird though, is that now my knox sometimes shows tripped and sometimes doesn't; sometimes root checker fails and sometimes it passes.
I wonder if I grazed on something that's related to the knox handler... Nagh... probably just wishful thinking. Still weird though.

bober10113 said:
i think you should weigh in what you want to achieve by changing csc and if it really is worth rooting for.
i rooted for custom roms, sound mods and just sheer control over my device.
but this comes with a price:
no samsung pay ( yet)( can always unroot)
tripped knox fuse, so probably no warranty. depends.(once tripped, this cannot be reverted)
misc apps detect root and might no longer root.(can always unroot)
so you should read up and get informed on what you need and if you need root/twrp.
concerning updates once rooted:
either use custom roms. BL and CP can be manually updated via stock firmware while custom rom keeps the system up to date.
or flash full stock firmware each time then re-root.
in both cases above, firmware files to be used are for exynos F devices. forget the canadian firmware, you cant flash that since it's for snapdragon devices.
Click to expand...
Click to collapse
Hi @hkalltheway!
Bober10113 is absolutely right on this. Really, you need to know what exactly you are rooting the device for. If you don't have a set reason, it may be better not to root it. You can flash stock firmware and CSC all day long without needing a root. But if you want to customize the features (there's not really a lot right now by the way) and setup custom menus, layouts, or run CFW... Then you'll have to go the way of rooting. But again, there is currently no definitive way to "untrip" your knox. As he said, you can "unroot" but you cannot "technically" regain your unmodified status; even though you can revert back to a stock rom. By loosing this status you loose access to Pay, Secure Folder, and a few other things. I think there is a mod out there to get Samsung Health working again, but as far as I'm currently aware, that's the only one you can re-gain. Most of them validate against your knox value.
Regarding your questions.
YES! You should always install TWRP first before doing any 'messin'. This is your ultimate line of recovery and the best mulligan your gonna get from your device. Always follow the two step wonder on this:
1. Install TWRP
2. Boot into TWRP and create a full backup of your partitions (Before anything else). I do this to the SD card in the tray. That way it's always handy.
After this, feel free to play around, but keep in mind what versions/revisions your flashing. If you jump to a new one, it's not easy to downgrade -it'll take hours to download and rewrite the firmware you need and trick the phone into thinking it's flashing the latest update.
Regarding a changed CSC and the updates... You should have no problem getting updates. But Samsung sends out updates to devices based on the CSC. So, if you flash the CSC, the updates you get will come at the same time interval of the country and location of the CSC that you flashed. For example, you have a Sin model with Sin CSC just like me, but if you flash to a UK CSC, then you will get your updates at the same time that the UK get their updates. Etc, Etc...
For the OTA Updates, if your on a stock firmware you should get these fine. If they do not automatically update you can just tap the update button manually in settings to check for new updates and then download them. Some have said you need to turn off automatic updates, and some say you do not. This, I'm not 100% sure on this one. Also, you can manually update by flashing the newest version through Odin as the come in. Usually SamMobile.com is good about keeping up to date firmware that you can download with all 4 packs, nicely labeled for you.
Hopefully that helps you out a bit.

VetteMike69 said:
Hi @hkalltheway!
Bober10113 is absolutely right on this. Really, you need to know what exactly you are rooting the device for. If you don't have a set reason, it may be better not to root it. You can flash stock firmware and CSC all day long without needing a root. But if you want to customize the features (there's not really a lot right now by the way) and setup custom menus, layouts, or run CFW... Then you'll have to go the way of rooting. But again, there is currently no definitive way to "untrip" your knox. As he said, you can "unroot" but you cannot "technically" regain your unmodified status; even though you can revert back to a stock rom. By loosing this status you loose access to Pay, Secure Folder, and a few other things. I think there is a mod out there to get Samsung Health working again, but as far as I'm currently aware, that's the only one you can re-gain. Most of them validate against your knox value.
Regarding your questions.
YES! You should always install TWRP first before doing any 'messin'. This is your ultimate line of recovery and the best mulligan your gonna get from your device. Always follow the two step wonder on this:
1. Install TWRP
2. Boot into TWRP and create a full backup of your partitions (Before anything else). I do this to the SD card in the tray. That way it's always handy.
After this, feel free to play around, but keep in mind what versions/revisions your flashing. If you jump to a new one, it's not easy to downgrade -it'll take hours to download and rewrite the firmware you need and trick the phone into thinking it's flashing the latest update.
Regarding a changed CSC and the updates... You should have no problem getting updates. But Samsung sends out updates to devices based on the CSC. So, if you flash the CSC, the updates you get will come at the same time interval of the country and location of the CSC that you flashed. For example, you have a Sin model with Sin CSC just like me, but if you flash to a UK CSC, then you will get your updates at the same time that the UK get their updates. Etc, Etc...
For the OTA Updates, if your on a stock firmware you should get these fine. If they do not automatically update you can just tap the update button manually in settings to check for new updates and then download them. Some have said you need to turn off automatic updates, and some say you do not. This, I'm not 100% sure on this one. Also, you can manually update by flashing the newest version through Odin as the come in. Usually SamMobile.com is good about keeping up to date firmware that you can download with all 4 packs, nicely labeled for you.
Hopefully that helps you out a bit.
Click to expand...
Click to collapse
phone info tool and other root detect apps are notorious for reporting wrong Knox status.....
he wants a csc from a snapdragon to a exynos. so flashing csc from SD in odin is ill advised. so it will require root and files be either manualy modded or i have updated tkkg1994 csc pack to work on note 9. ive only added canadian region.
https://1drv.ms/u/s!AhXVLDDj8g3AgdkwkPIxwDu5ZFASuQ
in twrp backup:
EFS
carrier files
then flash zip.
i wont be held responsible for anything. Ive tested on my N960N.
should work on any F or FD/DS too.
all credits to tkkg1994.

bober10113 said:
phone info tool and other root detect apps are notorious for reporting wrong Knox status.....
he wants a csc from a snapdragon to a exynos. so flashing csc from SD in odin is ill advised. so it will require root and files be either manualy modded or i have updated tkkg1994 csc pack to work on note 9. ive only added canadian region.
https://1drv.ms/u/s!AhXVLDDj8g3AgdkwkPIxwDu5ZFASuQ
in twrp backup:
EFS
carrier files
then flash zip.
i wont be held responsible for anything. Ive tested on my N960N.
should work on any F or FD/DS too.
all credits to tkkg1994.
Click to expand...
Click to collapse
Thanks for the help guys! The only reason I wanted root was for having VoLTE and Wifi calling working in Canada. One more reason is titanium backup so I can back up the device completely so it's easy to restore. Finally, I was curious how the scene is now and what else I can play with in magisk, as I've never used it. Thanks!

hkalltheway said:
Thanks for the help guys! The only reason I wanted root was for having VoLTE and Wifi calling working in Canada. One more reason is titanium backup so I can back up the device completely so it's easy to restore. Finally, I was curious how the scene is now and what else I can play with in magisk, as I've never used it. Thanks!
Click to expand...
Click to collapse
well then root might be food for you.
have a read at Dr Ketan roms thread for the root procedure and details of what it involves.

hkalltheway said:
Thanks for the help guys! The only reason I wanted root was for having VoLTE and Wifi calling working in Canada. One more reason is titanium backup so I can back up the device completely so it's easy to restore. Finally, I was curious how the scene is now and what else I can play with in magisk, as I've never used it. Thanks!
Click to expand...
Click to collapse
what is your carrier?
because Rogers blacklists non carrier phones. i believe bell might also do that too. So even if all is there and options appear, your phones imei code will be blocked from enrolling for wifi calling.

bober10113 said:
what is your carrier?
because Rogers blacklists non carrier phones. i believe bell might also do that too. So even if all is there and options appear, your phones imei code will be blocked from enrolling for wifi calling.
Click to expand...
Click to collapse
I'm currently with fido but thinking of switching to freedom mobile. Still too worried about all this rooting stuff that it seems the best thing to do is stay away from now and choose from one of the 2:
1- use wifi calling / VoLTE by getting the rogers/fido phone directly; that phone will not have dual sim capability
2- forget wifi calling / VoLTE and use this dual sim version, which has a lot of advantages while traveling
Seems like I'll stick to the 2nd option for now. Thanks for the help!

Note 8 converted to a dualsim lost imei in Pie

Hi, i convert my note 8 from single sim to dual, work great in android 8 but when update to android 9 it lost imei, i try to flash 9 with the modem of 8 but dont work in the same way try with flash BL + Modem from 8 and system from 9, and again the same happen, i feel good with android 8 but if one day wanna try android 9 i whish to can update without a problem.
Any can help or know what happen?
Thank
Sent from my [device_name] using XDA-Developers Legacy app

Looks like you need to input your device's IMEI number back in again.

Nope Samsung stopped that from happening on android pie. It now checks for that.
What I read you have to root your phone and replace your service.jar file with the older version for dual sim to work.
But you'll lose Knox and Knox related stuff (Samsung pay, secure folder) so read before you'll root.
Hopefully down the road someone will find a non-root method.

BluePhnx said:
Nope Samsung stopped that from happening on android pie. It now checks for that.
What I read you have to root your phone and replace your service.jar file with the older version for dual sim to work.
But you'll lose Knox and Knox related stuff (Samsung pay, secure folder) so read before you'll root.
Hopefully down the road someone will find a non-root method.
Click to expand...
Click to collapse
Thank by you reply, well i will wait to find how to do it, i dont want to lose knox
Sent from my [device_name] using XDA-Developers Legacy app

J.Elis85 said:
Thank by you reply, well i will wait to find how to do it, i dont want to lose knox
Click to expand...
Click to collapse
If you really need it you can go back to oreo.
edit:
This will require a factory reset though....

BluePhnx said:
If you really need it you can go back to oreo.
edit:
This will require a factory reset though....
Click to expand...
Click to collapse
I'm actually on Oreo, prefer dualsim option

i have bought new galaxy note 8
n950n and i surprised it from inside n950f
now i confused
i need to put original firmware from sammobile android 9 (950n)
what will happen ?
will it converted to one sim ?
will i lose arabic language?
will it be locked carriers?
please i need help...

J.Elis85 said:
Hi, i convert my note 8 from single sim to dual, work great in android 8 but when update to android 9 it lost imei, i try to flash 9 with the modem of 8 but dont work in the same way try with flash BL + Modem from 8 and system from 9, and again the same happen, i feel good with android 8 but if one day wanna try android 9 i whish to can update without a problem.
Any can help or know what happen?
Thank
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Same thing has happened to me and I am now perplexed how to restore my phone back.
Can you please inform how did you recover your phone to have Modem, IMEI and signal back - as I have lost them while doing a factory update of samsung stock 9 Pie image.

fixed by @hainguyenthao