I am having a problem with my samsung galaxy note 3. I cannot send text or calls. I am having an error message "not registered on network".
Does anyone experience the same problem and know the fix? thanks a lot!
*#06#
Rojohn said:
I am having a problem with my samsung galaxy note 3. I cannot send text or calls. I am having an error message "not registered on network".
Does anyone experience the same problem and know the fix? thanks a lot!
Click to expand...
Click to collapse
you have your IMEI?? or lost it.
i had this problem once so i went into network settings and changed it to manual, selected the network im on and it said registered, switched it back to automatic and it was all sorted. either try that or check imei
nijom said:
you have your IMEI?? or lost it.
Click to expand...
Click to collapse
i have my imei. do you know how to fix the issue sir?
KevandLynds said:
i had this problem once so i went into network settings and changed it to manual, selected the network im on and it said registered, switched it back to automatic and it was all sorted. either try that or check imei
Click to expand...
Click to collapse
i've done that several times but still not working sir
Rojohn said:
i have my imei. do you know how to fix the issue sir?
Click to expand...
Click to collapse
Does your phone also remember the IMEI? Dial *#06# and check if the number matches the original IMEI. If it's NULL or starts with 0049, that's the cause.
If the IMEI is correct, try a different SIM.
Sent from my SM-N9005 using Tapatalk 2
ShadowLea said:
Does your phone also remember the IMEI? Dial *#06# and check if the number matches the original IMEI. If it's NULL or starts with 0049, that's the cause.
If the IMEI is correct, try a different SIM.
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
The IMEI is not null or it does not start with 0049. The IMEI on the phone and the box is correct is also correct. Also I've tried different SIM card but still getting the same message "not registered on network".
Rojohn said:
The IMEI is not null or it does not start with 0049. The IMEI on the phone and the box is correct is also correct. Also I've tried different SIM card but still getting the same message "not registered on network".
Click to expand...
Click to collapse
Dial *#1234# and tell me what appears.
Rojohn said:
The IMEI is not null or it does not start with 0049. The IMEI on the phone and the box is correct is also correct. Also I've tried different SIM card but still getting the same message "not registered on network".
Click to expand...
Click to collapse
1- First, put your SIM card into another phone to make sure it works fine?
2- Second, open the Debug ServiceMode Menu and do the following: DEBUG SCREEN > NAS INFORMATION > MM INFORMATION (capture screenshot #1) > Menu - Back > MM REJECT CAUSE (capture screenshot #2).
And post these screenshots for further checking.
To open the Debug ServiceMode Menu:
a- If you have root, install Phone INFO ★Samsung★ app > Menu > 'Secret Codes' > *#197328640# > 'Launch 0'.
b- If you don't have root, open the dialer > *#0011# > Menu - Back > Menu - Key Input > Q0 > wait... until Debug ServiceMode Menu appears.
I have a quite similar problem. My phone is a 3UK (service provider) phone. I have 2 sim cards with me (MTN & Etisalat). My phone (note3) works perfectly fine. I have even rooted to resolve this issue.
Now the issue is whenever i put my MTN sim card it works perfectly fine on Note 3, however the moment i enter my Etisalat sim it will work for 10-15 mins & will stop working. I will have network bars but when i try to make any outgoing or incoming call it does not work.
Also if i use the same etisalat sim with my iPhone 5s it works perfectly fine.
I have tried *#1234# & the information that i got is as below:
AP: N9005XXUDMJ6
CP: N9005XXUDMJ4
CSC: N9005H3GDMJ2
Some of my friends told me to upgrade it to Kitkat and that might resolve the issue but when i try to check for updates it says:
Your device has been modified. Software updates are not available.
Please let me know what is the solution
Note: I am new to android world. So please consider that..
anuragjiw said:
I have a quite similar problem. My phone is a 3UK (service provider) phone. I have 2 sim cards with me (MTN & Etisalat). My phone (note3) works perfectly fine. I have even rooted to resolve this issue.
Now the issue is whenever i put my MTN sim card it works perfectly fine on Note 3, however the moment i enter my Etisalat sim it will work for 10-15 mins & will stop working. I will have network bars but when i try to make any outgoing or incoming call it does not work.
Also if i use the same etisalat sim with my iPhone 5s it works perfectly fine.
I have tried *#1234# & the information that i got is as below:
AP: N9005XXUDMJ6
CP: N9005XXUDMJ4
CSC: N9005H3GDMJ2
Some of my friends told me to upgrade it to Kitkat and that might resolve the issue but when i try to check for updates it says:
Your device has been modified. Software updates are not available.
Please let me know what is the solution
Note: I am new to android world. So please consider that..
Click to expand...
Click to collapse
- What does it say when you make a call (incoming/outgoing)?
Please follow my above post and show screenshots for more checking.
- Regarding to upgrading it to KitKat, I doubt that will not fix your issue. However if you want to upgrade, you can flash the stock firmware via Odin. Use Phone INFO ★Samsung★ app > Menu > 'Firmware Browser' to download the correct firmware for your device, and flash it via Odin.
vndnguyen said:
- What does it say when you make a call (incoming/outgoing)?
Please follow my above post and show screenshots for more checking.
- Regarding to upgrading it to KitKat, I doubt that will not fix your issue. However if you want to upgrade, you can flash the stock firmware via Odin. Use Phone INFO ★Samsung★ app > Menu > 'Firmware Browser' to download the correct firmware for your device, and flash it via Odin.
Click to expand...
Click to collapse
When I try to make a call it just says dialing.. And when I try to get incoming call it says switched off..
I have tried to check for firmware in phone info and got N9005XXUGNH1 . Not sure if I should install that or not.
Attached are the NAS info & firmware in phone info.
ShadowLea said:
Does your phone also remember the IMEI? Dial *#06# and check if the number matches the original IMEI. If it's NULL or starts with 0049, that's the cause.
If the IMEI is correct, try a different SIM.
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
I have tried to check the IMEi. My imei is not null or starts with 0049.
anuragjiw said:
When I try to make a call it just says dialing.. And when I try to get incoming call it says switched off..
I have tried to check for firmware in phone info and got N9005XXUGNH1 . Not sure if I should install that or not.
Attached are the NAS info & firmware in phone info.
Click to expand...
Click to collapse
1- Please check and make sure if date/time setting is correct? Or it was not correct?
2- In ServiceMode Menu, select CALL END CAUSE and show the screenshot?
vndnguyen said:
1- Please check and make sure if date/time setting is correct? Or it was not correct?
2- In ServiceMode Menu, select CALL END CAUSE and show the screenshot?
Click to expand...
Click to collapse
i have checked the date & time which is perfect.
Do u want all these screenshots with my Etisalat sim inserted or any sim inserted?
When i click on Call end cause it comes back to Service mode.
anuragjiw said:
i have checked the date & time which is perfect.
Do u want all these screenshots with my Etisalat sim inserted or any sim inserted?
When i click on Call end cause it comes back to Service mode.
Click to expand...
Click to collapse
I asked for the date/time settings as in the MM REJECT CAUSE screenshot there is only log from the past. No any new log.
The screenshots you have shown are from the MTN sim card, right?
All info seem to be fine, I don't know why it cannot make or receive a call.
If possible, try to take screenshots for both SIM cards and compare to see if there is any differences.
EDIT: Oh NO, you need to show me screenshots from the sim card that doesn't work, NOT screenshots from the sim card that works fine.
vndnguyen said:
I asked for the date/time settings as in the MM REJECT CAUSE screenshot there is only log from the past. No any new log.
The screenshots you have shown are from the MTN sim card, right?
All info seem to be fine, I don't know why it cannot make or receive a call.
If possible, try to take screenshots for both SIM cards and compare to see if there is any differences.
EDIT: Oh NO, you need to show me screenshots from the sim card that doesn't work, NOT screenshots from the sim card that works fine.
Click to expand...
Click to collapse
Yes i have taken it from MTN sim which is working perfectly fine. Even my etisalat sim works for like 20 mins before it stops working.
Also i am downloading the N9005XXUGNH1 from Sammobile as you have mentioned before. But will it resolve the issue?
Attached is the screenshot of the same.
OK will attach the Etisalat sim & will upload in 5 mins
Attached are the screenshots of MM info, MM reject cause.
I am unable to open CALL END Cause. The moment i tap on it, it goes back to DEBUG Screen
I have tried to compare MM info, Reject cause with both the sim cards entering one by one & found out everything is same in Reject cause.
But MM info there is a slight change in MMC-MNC: 621-30 (MTN which works fine) & MMC - MNC: 621 - 60 (Etisalat which is not working)
LAC: 2ae8, RAC: 9 (MTN) & LAC: 7d15, RAC: 4
There are some changes in TMSI which is think is some sort of id.
Also want to know if I install N9005XXUGNH1 firmware on my samsung note 3 will this issue resolve?
anuragjiw said:
Attached are the screenshots of MM info, MM reject cause.
I am unable to open CALL END Cause. The moment i tap on it, it goes back to DEBUG Screen
Click to expand...
Click to collapse
From the screenshots it appears to be fine on both sim card.
You should take a screenshots when it becomes not working (after 20 min...)
vndnguyen said:
From the screenshots it appears to be fine on both sim card.
You should take a screenshots when it becomes not working (after 20 min...)
Click to expand...
Click to collapse
OK will send the screenshots once it stops working.. BTW thanks a lot in advance..
Also want to know if I install N9005XXUGNH1 firmware on my samsung note 3 will this issue resolve?
EDIT: I found out the problem but unable to find the solution.
Also want to inform you that I tried to select the network automatically once it stopped working & it worked for around 1-2 hours..
Suggest me what to do..
Hi,
Currently on InvictaOS (4/20 release). I know there are settings that allow me to change the carrier name to whatever I like (on status bar and lockscreen), but when an actual call is made or received, the phone still says "(XXX) XXX-XXXX via Home".
I've searched everywhere for the answer but can't find anything that will change the carrier name globally.
I used my current sim in my old S4 and it correctly displayed AT&T while on KK...however, I noticed the same Home issue when I installed a LP ROM. FWIW, I also received the Home carrier label when I was on stock MM. Is this a "feature" that was introduced with LP? If so, I don't like it.
Anyway, just me being picky. Any advice is appreciated.
Thanks!
mn1968 said:
Hi,
Currently on InvictaOS (4/20 release). I know there are settings that allow me to change the carrier name to whatever I like (on status bar and lockscreen), but when an actual call is made or received, the phone still says "(XXX) XXX-XXXX via Home".
I've searched everywhere for the answer but can't find anything that will change the carrier name globally.
I used my current sim in my old S4 and it correctly displayed AT&T while on KK...however, I noticed the same Home issue when I installed a LP ROM. FWIW, I also received the Home carrier label when I was on stock MM. Is this a "feature" that was introduced with LP? If so, I don't like it.
Anyway, just me being picky. Any advice is appreciated.
Thanks!
Click to expand...
Click to collapse
Just a thought - under Settings > SIM cards, if you tap on your SIM card (e.g. in slot 1) are you able to edit the SIM name there (by tapping on SIM name), and does that then change 'Home' to whatever you typed when you call?
I do not have the Sim Card settings that you speak of. I have the XT1625 (non plus version), so I don't know if I don't have those settings because it's a single sim phone or if the ROM doesn't have those settings. But thanks for the reply!
mn1968 said:
I do not have the Sim Card settings that you speak of. I have the XT1625 (non plus version), so I don't know if I don't have those settings because it's a single sim phone or if the ROM doesn't have those settings. But thanks for the reply!
Click to expand...
Click to collapse
Hmm, that's odd - I'd have thought the SIM card settings would be there regardless of whether it's single or dual SIM... Just asking, what's your device's baseband on Invicta (under Settings > About Phone)? Was this a clean flash of Invicta with BeanGapps or another GApps?
With a clean flash of Invicta 2.0 (20/04 build, BeanGapps mini), I'd have expected that SIM card settings would be visible on the top level of Settings (as in the screenshot), then you'd be able to edit the SIM name (in the screenshot, I've renamed my SIM from 3 to 3 UK), which shows up when you call from that SIM. However, this is on a XT1642 (G4 Plus), so maybe some other XT1625 or G4 users can chime in that are running Invicta too!
You may wish to try clean flashing the 09/05 Invicta build, see if you have any more luck with that one. https://forum.xda-developers.com/showpost.php?p=72222658&postcount=3844
I clean flashed the 4/20 Invicta build with the recommended 7.1.2 slim micro gapps...but I've faced this issue on every MM & Nougat ROM I've tried.
My baseband is M8952_70009.08.03.45R. Never flashed anything special since all the recommended flashes for Nougat were for fingerprint usability- since I don't have a FP button it was/is a moot point.
I've considered upgrading to the 5/09 build but I have my phone set up how I like it. I don't like to re-do everything every time a new build comes out.
The 'Home" issue is just a minor annoyance. If I can tweak it - cool. If not, not big deal.
I was planning to get a new phone with a great display, and that was exactly when RP2 went on sale. I'm otherwise satisfied with the phone, but single SIM is definitely a deal breaker in China. Given that I could not find any other phone matching my criteria, I decided to get the RP2 and tried to enable dual SIM on it. Till now I've had some success, and here is what I have done.
If you have strong demand for dual SIM like I do, you may try these steps. This thread, however, is NOT a proper nor complete guide on this topic. It is just a record of my trials - they are highly experimental, risky, and potentially broken. There is absolutely no guarantee on signal quality, stability, power consumption or even the success rate. Your device can be permanently damaged if any detail goes wrong. Make sure you understand all the risks and you are able to justify every command before typing it to your phone!
I do appreciate suggestions for the correct way, though. Comments are greatly welcomed!
My environment
QPST 2.7.477 - only PDC is used here, so any version with standalone PDC tool might do the job. But new versions required if you want to use other tools.
QXDM Professional 3.14.1144 - this one is optional. It's used to tweak some parameters, but dual SIM does work without the tweaks.
Qualcomm USB drivers 2.1.2.0 from 2015/7/8 - older versions might work as well.
Windows 10, 1803
arter97's kernel and Magisk-patched stock kernel images readily at hand. The latter can be obtained by patching a stock kernel image in Magisk Manager with "Keep dm-verity/avb 2.0" UNTICKED. I had the latter installed on the phone.
Make sure root shell can be obtained during boot with ALL kernel images. This is an important recovery approach if the phone bootloops.
Steps
I've gone through a tricky path to confirm that there is indeed a second IMEI in the phone prior to the steps, which supported follow-up researching. This thread will not cover this part as this is merely trial-and-error. I will provide suggestions on diag connection though.
1. make a backup of all partitions on the phone, leaving out system, vendor and userdata partitions of course. There are 88 partitions in my backup.
2. make a QCN backup of modem NV. This step could be optional as modemst1/2 has already been backed-up in previous step - I'm not sure about this, and have completed this step whatsoever.
3. make a backup of /vendor/etc/vintf/manifest.xml, and add slot2 instances to the following HALs:
android.hardware.radio - this one has 2 interfaces, and both of them need the slot2 addition
vendor.qti.hardware.radio.am
vendor.qti.hardware.radio.qtiradio - this one has 2 versions, and both of them need the slot2 addition
4.
Code:
adb shell su -c setprop persist.radio.multisim.config dsds
5. find any USB mode with rmnet in /vendor/etc/init/hw/init.msm.configfs.rc, and switch to it. I used "diag,serial_cdev,rmnet,dpl,adb", and that's
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb
6. Windows shows a lot of new USB devices. Force-install Qualcomm WWAN driver for the RmNet device. I chose "Network Adapters -> Qualcomm -> Qualcomm HS-USB WWAN Adapter 90B8", but anything named after "Qualcomm HS-USB WWAN Adapter" should do.
7. open PDC. There are 3 dual SIM (DSDS) hardware profiles available:
SR_DSDS-LA-7+7_mode-SDM845
SR_DSDS-WD-7+7_mode-SDM845
SR_DSDS-WP8-7+7_mode-SDM845
The one with WP8 in its name can be ignored, and here comes the hard choice.
I tried the WD one in the first place: activated it in the context menu on Sub0 then Sub1, and clicked Activate twice. PDC complained about malformed packet after second click, and the profile was shown as Active on Sub0, and Pending on Sub1. Nothing bad happened after a reboot, regardless of the errors above. Two SIM slots were present in About Phone, and second IMEI is correctly shown there as well. Upon inserting two SIM cards I got dual VoLTE online, and everything behaved like a normal dual SIM SDM845 device. There were some little glitches though: once or twice a day signal bars disappeared and popped up again in a few seconds. Mobile data also stuttered at random times, though not frequent - sometimes mobile data was stable for the whole day. I was satisfied with the results, and made another backup of partitions.
Then I started comparing the WD and LA profiles. I quickly realized that LA marked the phone as DSDS while WD as SS in the device_mode NV entry (I honestly had no idea why dual SIM just worked with WD). There were other differences unknown to me, but LA seemed more "correct" and I decided to switch to this profile. After deactivating WD on both Sub0 and Sub1, I activated LA on Sub0 but not Sub1. The phone could still make use of two SIMs, but without VoLTE on either card. LTE was still available for both cards though. The glitches with WD were mostly gone (data still stuttered but recovered much faster), and the phone SEEMED cooler and battery SEEMED to drain slower.
Finally I could not understand the lack of VoLTE and switched back to WD (still Sub0 only). This time only the first SIM card could register on IMS/VoLTE. The second one registered on LTE but not IMS, regardless of default data card selection. Activating WD on Sub1 did not solve the problem. Manual checks/corrections on the differences between WD and LA made no effect either. I had to flash the backup made after first WD trial, and dual VoLTE worked again.
I came to the following conclusion after this step:
a. hardware profiles may be applied to Sub0 only (can anyone confirm this?)
b. a profile may not be completely reverted after applying. That is to say, same profile status does not mean same baseband behavior.
c. LA profile does not support VoLTE for some reason.
d. if you want dual VoLTE, your best bet would be activating WD on Sub0 and Sub1 right after previous steps, though Sub1 won't accept the setting.
e. mobile data may stutter with dual SIM (this could also be the fault of my service provider however)
Any clarification on this step is appreciated. If you want to enable dual SIM, you have to make your own choice here. Just remember to backup before every change.
8. apply some NV changes from LA on WD base:
ue_usage_setting: from DATA_CENTRIC to VOICE_CENTRIC
device_mode: from SS to DSDS
disable_global_mode: from 1 to 0
I failed to find any difference after these changes. this step could be optional. I myself use the phone as daily driver with these changes though.
That's all. Don't worry, I'm confused as you Everything just works or fails without any valid reason
Other Details
1. RP2 uses the same SIM card slot as Samsung. I filed an card tray from Samsung S7 so that it fits RP2. Its size naturally() fits RP2, just make it as thin as Razer's tray and it will work.
2. if you want to restore a modemst1/2 backup, do that in TWRP. If this needs to be done in Android system, stop vendor.rmt_storage first.
3. if the phone reboots to recovery right after booting to lock screen, this could be SIM count in baseband and system diverging. Run
Code:
adb shell su -c setprop persist.radio.multisim.config ss
during boot to see if this fixes the problem. If it does, restore all backups then start all over.
4. QPST does not recognize the diag port from the phone upon USB connection. Do this so that diag port works:
Code:
# in adb shell, assuming USB mode has already been switched
su
setenforce 0
stop vendor.per_mgr
# wait a few sec until QPST recognizes SDM845 on the diag port
start vendor.per_mgr
# SDM845 disappears and re-appears after a few sec, and QPST is usable
5. arter97's kernel disables diag drivers, and QPST could never recognize the phone. You have to use stock kernel if you intend to use anything other than PDC.
Screenshots and photos:
Screenshot of About Phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot of dual VoLTE:
Photos of the filed card tray inside RP2:
The original Samsung tray:
And after filing:
Reserved for minor fixes
that's interesting
i have tried this, but the second imei doesn't appears what am I doing wrong?
ps: i find second imei in QCN backup
IMG
I finally got it
i updated to rom deodexed and zipalign from Warrior1988
after that I looked at the settings, the second Imei appeared
then I put sim card, android recognizes then it worked
PS: i modded SIM Card with MicroSD, now i have dual SIM with MicroSD :laugh:
IMG
unfortunately, now i see this message on starting, but starts normally (don't shutdown) :victory:
IMG
Update: you can remove this with command
reboot "dm-verity enforcing"
Hey man! What sim card tray did you use and how did you modify it for dual SIM and sdcard?
Using a command to reverify the DM will get rid of the red text and boot
th3cavalry said:
Hey man! What sim card tray did you use and how did you modify it for dual SIM and sdcard?
Using a command to reverify the DM will get rid of the red text and boot
Click to expand...
Click to collapse
I did this method, and used default sim card tray
and thanks for command
So I'm stuck at step 7. I have the both SIM slots showing in the phone but no IMEI for SIM2. When I open PDC it doesn't show anything.
When we add the slot2, do we add slot1,slot2 or do we add a whole nother line in the file for slot2?
Did you have any issues with PDC in the beginning?
updateing said:
I was planning to get a new phone with a great display, and that was exactly when RP2 went on sale. I'm otherwise satisfied with the phone, but single SIM is definitely a deal breaker in China. Given that I could not find any other phone matching my criteria, I decided to get the RP2 and tried to enable dual SIM on it. Till now I've had some success, and here is what I have done.
If you have strong demand for dual SIM like I do, you may try these steps. This thread, however, is NOT a proper nor complete guide on this topic. It is just a record of my trials - they are highly experimental, risky, and potentially broken. There is absolutely no guarantee on signal quality, stability, power consumption or even the success rate. Your device can be permanently damaged if any detail goes wrong. Make sure you understand all the risks and you are able to justify every command before typing it to your phone!
I do appreciate suggestions for the correct way, though. Comments are greatly welcomed!
My environment
QPST 2.7.477 - only PDC is used here, so any version with standalone PDC tool might do the job. But new versions required if you want to use other tools.
QXDM Professional 3.14.1144 - this one is optional. It's used to tweak some parameters, but dual SIM does work without the tweaks.
Qualcomm USB drivers 2.1.2.0 from 2015/7/8 - older versions might work as well.
Windows 10, 1803
arter97's kernel and Magisk-patched stock kernel images readily at hand. The latter can be obtained by patching a stock kernel image in Magisk Manager with "Keep dm-verity/avb 2.0" UNTICKED. I had the latter installed on the phone.
Make sure root shell can be obtained during boot with ALL kernel images. This is an important recovery approach if the phone bootloops.
Steps
I've gone through a tricky path to confirm that there is indeed a second IMEI in the phone prior to the steps, which supported follow-up researching. This thread will not cover this part as this is merely trial-and-error. I will provide suggestions on diag connection though.
1. make a backup of all partitions on the phone, leaving out system, vendor and userdata partitions of course. There are 88 partitions in my backup.
2. make a QCN backup of modem NV. This step could be optional as modemst1/2 has already been backed-up in previous step - I'm not sure about this, and have completed this step whatsoever.
3. make a backup of /vendor/etc/vintf/manifest.xml, and add slot2 instances to the following HALs:
android.hardware.radio - this one has 2 interfaces, and both of them need the slot2 addition
vendor.qti.hardware.radio.am
vendor.qti.hardware.radio.qtiradio - this one has 2 versions, and both of them need the slot2 addition
4.
Code:
adb shell su -c setprop persist.radio.multisim.config dsds
5. find any USB mode with rmnet in /vendor/etc/init/hw/init.msm.configfs.rc, and switch to it. I used "diag,serial_cdev,rmnet,dpl,adb", and that's
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb
6. Windows shows a lot of new USB devices. Force-install Qualcomm WWAN driver for the RmNet device. I chose "Network Adapters -> Qualcomm -> Qualcomm HS-USB WWAN Adapter 90B8", but anything named after "Qualcomm HS-USB WWAN Adapter" should do.
7. open PDC. There are 3 dual SIM (DSDS) hardware profiles available:
SR_DSDS-LA-7+7_mode-SDM845
SR_DSDS-WD-7+7_mode-SDM845
SR_DSDS-WP8-7+7_mode-SDM845
The one with WP8 in its name can be ignored, and here comes the hard choice.
I tried the WD one in the first place: activated it in the context menu on Sub0 then Sub1, and clicked Activate twice. PDC complained about malformed packet after second click, and the profile was shown as Active on Sub0, and Pending on Sub1. Nothing bad happened after a reboot, regardless of the errors above. Two SIM slots were present in About Phone, and second IMEI is correctly shown there as well. Upon inserting two SIM cards I got dual VoLTE online, and everything behaved like a normal dual SIM SDM845 device. There were some little glitches though: once or twice a day signal bars disappeared and popped up again in a few seconds. Mobile data also stuttered at random times, though not frequent - sometimes mobile data was stable for the whole day. I was satisfied with the results, and made another backup of partitions.
Then I started comparing the WD and LA profiles. I quickly realized that LA marked the phone as DSDS while WD as SS in the device_mode NV entry (I honestly had no idea why dual SIM just worked with WD). There were other differences unknown to me, but LA seemed more "correct" and I decided to switch to this profile. After deactivating WD on both Sub0 and Sub1, I activated LA on Sub0 but not Sub1. The phone could still make use of two SIMs, but without VoLTE on either card. LTE was still available for both cards though. The glitches with WD were mostly gone (data still stuttered but recovered much faster), and the phone SEEMED cooler and battery SEEMED to drain slower.
Finally I could not understand the lack of VoLTE and switched back to WD (still Sub0 only). This time only the first SIM card could register on IMS/VoLTE. The second one registered on LTE but not IMS, regardless of default data card selection. Activating WD on Sub1 did not solve the problem. Manual checks/corrections on the differences between WD and LA made no effect either. I had to flash the backup made after first WD trial, and dual VoLTE worked again.
I came to the following conclusion after this step:
a. hardware profiles may be applied to Sub0 only (can anyone confirm this?)
b. a profile may not be completely reverted after applying. That is to say, same profile status does not mean same baseband behavior.
c. LA profile does not support VoLTE for some reason.
d. if you want dual VoLTE, your best bet would be activating WD on Sub0 and Sub1 right after previous steps, though Sub1 won't accept the setting.
e. mobile data may stutter with dual SIM (this could also be the fault of my service provider however)
Any clarification on this step is appreciated. If you want to enable dual SIM, you have to make your own choice here. Just remember to backup before every change.
8. apply some NV changes from LA on WD base:
ue_usage_setting: from DATA_CENTRIC to VOICE_CENTRIC
device_mode: from SS to DSDS
disable_global_mode: from 1 to 0
I failed to find any difference after these changes. this step could be optional. I myself use the phone as daily driver with these changes though.
That's all. Don't worry, I'm confused as you Everything just works or fails without any valid reason
Other Details
1. RP2 uses the same SIM card slot as Samsung. I filed an card tray from Samsung S7 so that it fits RP2. Its size naturally() fits RP2, just make it as thin as Razer's tray and it will work.
2. if you want to restore a modemst1/2 backup, do that in TWRP. If this needs to be done in Android system, stop vendor.rmt_storage first.
3. if the phone reboots to recovery right after booting to lock screen, this could be SIM count in baseband and system diverging. Run
Code:
adb shell su -c setprop persist.radio.multisim.config ss
during boot to see if this fixes the problem. If it does, restore all backups then start all over.
4. QPST does not recognize the diag port from the phone upon USB connection. Do this so that diag port works:
Code:
# in adb shell, assuming USB mode has already been switched
su
setenforce 0
stop vendor.per_mgr
# wait a few sec until QPST recognizes SDM845 on the diag port
start vendor.per_mgr
# SDM845 disappears and re-appears after a few sec, and QPST is usable
5. arter97's kernel disables diag drivers, and QPST could never recognize the phone. You have to use stock kernel if you intend to use anything other than PDC.
Click to expand...
Click to collapse
th3cavalry said:
So I'm stuck at step 7. I have the both SIM slots showing in the phone but no IMEI for SIM2. When I open PDC it doesn't show anything.
When we add the slot2, do we add slot1,slot2 or do we add a whole nother line in the file for slot2?
Click to expand...
Click to collapse
PDC works for me from the beginning. Please check:
1. Did you install the correct driver for the RmNet device?
2. There is a combo box in PDC window with nothing selected by default. Could you choose HS-USB WWAN Adapter in its dropdown list?
th3cavalry said:
So I'm stuck at step 7. I have the both SIM slots showing in the phone but no IMEI for SIM2. When I open PDC it doesn't show anything.
When we add the slot2, do we add slot1,slot2 or do we add a whole nother line in the file for slot2?
Click to expand...
Click to collapse
for me the second IMEI only worked after I installed this https://forum.xda-developers.com/razer-phone-2/development/rom-mr1-stock-deodexed-zipalign-t3916502
and to PDC work i used this driver https://androidfilehost.com/?fid=11410963190603864074
Wait, so... Even though this is a single-SIM phone, it has a second IMEI in it, and the hardware to read a second SIM? All they had to do to make this officially dual-SIM was make a slightly different SIM tray and change the hardware profile?
Gamesoul Master said:
Wait, so... Even though this is a single-SIM phone, it has a second IMEI in it, and the hardware to read a second SIM? All they had to do to make this officially dual-SIM was make a slightly different SIM tray and change the hardware profile?
Click to expand...
Click to collapse
Maybe they need more resources to fine tune dual SIM experiences (if they have not given up the plan for this variant). For example modem could crash when IMS registration states change on both slots simultaneously (this is why my signal bars disappear from time to time), and radio performance could be drastically degraded when two slots are registered on different bands. Making a product market-ready takes much more resources than making in happen in lab, and Razer might not want to invest that much in this area.
updateing said:
Maybe they need more resources to fine tune dual SIM experiences (if they have not given up the plan for this variant). For example modem could crash when IMS registration states change on both slots simultaneously (this is why my signal bars disappear from time to time), and radio performance could be drastically degraded when two slots are registered on different bands. Making a product market-ready takes much more resources than making in happen in lab, and Razer might not want to invest that much in this area.
Click to expand...
Click to collapse
Makes sense. I suppose I shouldn't trivialize the process. It mostly just surprises me that the hardware (and some of the software) is there at all. They must have had plans to do dual-SIM up until almost the last minute, because otherwise I can't imagine why they wouldn't save the money needed to put that extra hardware in there. And I can't imagine they'll release any such thing at this point. They basically shut down their mobile phone division, and haven't even released a software update in months.
hey guys..
enabling diag is workig on android 8.1.? it was using on pie but didnt work on oreo...anyone faced wtih this pb..?
Code:
aura:/ $ su
aura:/ # setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb
aura:/ #
---------- Post added at 02:27 PM ---------- Previous post was at 02:10 PM ----------
t-mobile_mda said:
hey guys..
enabling diag is workig on android 8.1.? it was using on pie but didnt work on oreo...anyone faced wtih this pb..?
Code:
aura:/ $ su
aura:/ # [B]setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb[/B]
aura:/ #
Click to expand...
Click to collapse
i think it is not working on oreo..tried again on pie and worked again...
Code:
C:\Users\X\Desktop\Razer\Phone_2\Root\8.1>adb shell
aura:/ $ su
aura:/ # [B]setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb[/B]
C:\Users\X\Desktop\Razer\Phone_2\Root\8.1>
hey again guys..
can anyone pls sahre the modemst parts..? single sim or dual it doesnt metter..
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst2 -> /dev/block/sdf3
dd if=/dev/block/sdf2 of=/sdcard/sdf2
dd if=/dev/block/sdf3 of=/sdcard/sdf3
w.b.r.
What are the chances of breaking my phone with these steps?
Just like anything else, trial and error.
So does this kill WiFi calling?
I tried this and I jacked it up a bit. i got it to get both SIMs working (TMOUS and KT). The WiFi calling for TMOUS stopped working and also if I went to "Mobile Data" it reset the radio and never opened the menu. So i tried to revert and it got stuck in a boot loop and when i did get in the cell was completely not working, No sim, no IMEI. Luckily i flashed an older ROM (shipped 8.1MR0) and progressively upgraded through the ROMs from there and have service again. This tells me that the Stock Razer Images from their developer site don't have 'everything' for a full restore.
t-mobile_mda said:
hey again guys..
can anyone pls sahre the modemst parts..? single sim or dual it doesnt metter..
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst2 -> /dev/block/sdf3
dd if=/dev/block/sdf2 of=/sdcard/sdf2
dd if=/dev/block/sdf3 of=/sdcard/sdf3
w.b.r.
Click to expand...
Click to collapse
Grab the Stock ROM for your version then extract it: https://developer.razer.com/razer-phone-dev-tools/factory-images/
All of them have "modem.img" used in there flash script in this command:
Code:
%fastboot_cmd% flash modem_a modem.img
%fastboot_cmd% flash modem_b modem.img
I don't think this works on 9MR2