Please follow the updated directions provided by Bendrexl below before attempting any other methods.
bendrexl said:
Here's a roundup of essential steps from this thread that worked for me...
:good: HUGE THANKS to: Whoareyou, docna, caspar347, Dishe
Prepare for battle:
Ensure your Verizon Moto E 2015 is configured for USB debugging.
Ensure your Verizon Moto E 2015 has airplane mode enabled.
Ensure your PC/Mac has the Android SDK Platform Tools installed & accessible via your terminal / command line (added to $PATH var).
Download 5.0.2 factory image: http://forum.xda-developers.com/moto-e-2015/general/stocks-firmwares-moto-e-t3113235/page2?nocache=1 (Thanks to caspar347!)
Unzip / expand this .zip archive.
Open a terminal session in the directory you just unzipped (containing NON-HLOS.bin & fsg.mbn)
Execute!
In your terminal with phone plugged in:
$ adb reboot bootloader (your phone should now reboot into bootloader, wait for this)
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot (WAIT for phone to fully boot before continuing)
$ adb shell (your command prompt will change to something like [email protected]_cdma:/ $. If you get kicked out of the session while entering the next commands, just type adb shell again and pick up where you left off)
[email protected]_cdma:/ $ pm clear com.android.providers.telephony
[email protected]_cdma:/ $ settings put global preferred_network_mode 9
[email protected]_cdma:/ $ settings put global preferred_network_mode1 9
[email protected]_cdma:/ $ settings put global preferred_network_mode2 9
[email protected]_cdma:/ $ pm hide com.motorola.setupwizard.phoneservice (optional)
[email protected]_cdma:/ $ exit (or just unplug & reboot phone)
$ adb reboot (or just unplug & reboot phone)
On the phone:
Turn off Airplane mode
Open Settings app > More > Cellular Networks
Ensure Preferred network type selected is "4G (recommended)"
Under Access Point Names, add the appropriate APNs for your specific carrier. (for Fi data, I only needed "h2g2").
Disable all Verizon apps through settings or Titanium Backup. (Optional)
CREDITS: Whoareyou, docna, caspar347, Dishe
Click to expand...
Click to collapse
IF YOUR DEVICE IS RUNNING 5.1, FOLLOW THE GREEN INSTRUCTIONS!
In order to attempt to get Verizon/Motorola to push out a new update with a fix for the removal of the option to switch to GSM, please sign this petition on Change.org and share it to anyone who you know will sign it! https://www.change.org/p/verizon-daniel-s-mead-stop-carrier-locking-motorola-moto-e-lte-xt1528
Background Info: I work at Walmart in the Connection Center, and today I had a customer wanting to switch to Family Mobile from AT&T, so I showed them our Family Mobile devices and T-Mobile Devices, they didnt seem interested in them and said they wanted somthing that had Android 5.0 Lollipop, I thought about it for a minute and remembered that the Moto E (2015) shipped with Lollipop installed, I also knew that Verizon phones come unlocked, so I showed them the device and they decided to go with it, they bought the Family Mobile Micro SIM starter kit, and the Moto E, but once I powered it on, I couldn't get it to connect to Family Mobile, so I tried to access the advanced radio menu (*#*#4636#*#*) to no avail, but I eventually got it working, with full LTE support, heres how:
POSSIBLE SIM SWAP WORKAROUND (Reported by wogeboy):
Disable vzwAPNpermissions.apk and vzwAPNservice.apk using this program: http://bit.ly/1HHyVao
I have not tested this as I dont have a VZW Moto E to test it on.
5.1 Updated Instrcutions:
With the SIM you want to use the the phone :
1. Put the phone into Airplane mode (I'm not sure this is needed, but it doesn't hurt)
2. Go to Settings -> About Phone and tap on "Build Number" until it says you are in Developer Mode (~10 times)
3. Go back one menu, and right above About Phone there should now be an option for Developer Options, go into that.
4. Turn on USB Debugging
5. Connect the phone to your computer and type "adb shell" in your CMD window
6. Run the following commands in adb shell :
pm clear com.android.providers.telephony
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
settings put global preferred_network_mode2 9
7. Turn off Airplane mode
8. Power off and Restart the phone
9. Open up the settings app, go to the mobile networks panel, select "Prefered Network Mode" and change it to "4G"
10. Input the appropriate APNs for your specific carrier
11. (Optional). Disable all Verizon apps through settings or Titanium Backup.
CREDIT: docna
.
5.0.2 Instructions:
1. Power on the device with the GSM SIM card in the SIM card slot
2. Connect to WiFi and complete Google Sign-In
3. Go to the Play Store and search "Network" download the first app (A white circle with a black phone in it) (This will allow us access to the advance radio options)
4. Open the "Network" shortcut
5. Change the radio mode from "CDMA/LTE PRL" to "GSM/LTE Auto"
6. Open up the settings app, go to the mobile networks panel, select "Prefered Network Mode" and change it to "4G"
7. Input the appropriate APNs for your specific carrier
8 (Optional). Disable all Verizon apps through settings or Titanium Backup.
The only thing I couldnt solve was how to remove the "SIM Card is not from Verizon Wireless" error in the status bar permanently, but thats just an annoyance, and causes no usability decrease.
This Works!
Thanks a lot, had been trying to get the GSM working. The "Network" app in the Play Store give access to the hidden radio selection menu. Verizon was able to disable all other way to enter the radio selection menu but this one did it. I think there is a apk file somewhere which disables the annoying "NOT verizon SIM" message. I will post here if I find that works.
That's a lot easier than poking around in NVram! Thanks, OP. And yeah, there's a Setup app or something you need to freeze for then sim error. I'll have to get mine out and find it.
Here are screen snaps. The VZ phone is actually picking up LTE for Ting (T-Mobile).
{
"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"
}
Nice. This is definitely some progress. Still waiting for the sprint version to be unlocked.
Whoareyou said:
Background Info: I work at Walmart in the Connection Center, and today I had a customer wanting to switch to Family Mobile from AT&T, so I showed them our Family Mobile devices and T-Mobile Devices, they didnt seem interested in them and said they wanted somthing that had Android 5.0 Lollipop, I thought about it for a minute and remembered that the Moto E (2015) shipped with Lollipop installed, I also knew that Verizon phones come unlocked, so I showed them the device and they decided to go with it, they bought the Family Mobile Micro SIM starter kit, and the Moto E, but once I powered it on, I couldn't get it to connect to Family Mobile, so I tried to access the advanced radio menu (*#*#4636#*#*) to no avail, but I eventually got it working, with full LTE support, heres how:
1. Power on the device with the GSM SIM card in the SIM card slot
2. Connect to WiFi and complete Google Sign-In
3. Go to the Play Store and search "Network" download the first app (A white circle with a black phone in it) (This will allow us access to the advance radio options)
4. Open the "Network" shortcut
5. Change the radio mode from "CDMA/LTE PRL" to "GSM/LTE Auto"
6. Open up the settings app, go to the mobile networks panel, select "Prefered Network Mode" and change it to "4G"
7. Input the appropriate APNs for your specific carrier
8 (Optional). Disable all Verizon apps through settings or Titanium Backup.
The only thing I couldnt solve was how to remove the "SIM Card is not from Verizon Wireless" error in the status bar permanently, but thats just an annoyance, and causes no usability decrease.
Click to expand...
Click to collapse
Thanks a ton for this! Do you know what the APN setting should be for T-Mobile? That's my current challenge. Every site has a different opinion. Including T-Mobile.
APN: fast.t-mobile.com
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
that should be all you have to set
Method Works on SPRINT AND BOOST too
Thanks
This method works on Boost and Sprint too.
Tested in INDIA working fine with indian GSM carriers.
Whoareyou said:
Background Info: I work at Walmart in the Connection Center, and today I had a customer wanting to switch to Family Mobile from AT&T, so I showed them our Family Mobile devices and T-Mobile Devices, they didnt seem interested in them and said they wanted somthing that had Android 5.0 Lollipop, I thought about it for a minute and remembered that the Moto E (2015) shipped with Lollipop installed, I also knew that Verizon phones come unlocked, so I showed them the device and they decided to go with it, they bought the Family Mobile Micro SIM starter kit, and the Moto E, but once I powered it on, I couldn't get it to connect to Family Mobile, so I tried to access the advanced radio menu (*#*#4636#*#*) to no avail, but I eventually got it working, with full LTE support, heres how:
1. Power on the device with the GSM SIM card in the SIM card slot
2. Connect to WiFi and complete Google Sign-In
3. Go to the Play Store and search "Network" download the first app (A white circle with a black phone in it) (This will allow us access to the advance radio options)
4. Open the "Network" shortcut
5. Change the radio mode from "CDMA/LTE PRL" to "GSM/LTE Auto"
6. Open up the settings app, go to the mobile networks panel, select "Prefered Network Mode" and change it to "4G"
7. Input the appropriate APNs for your specific carrier
8 (Optional). Disable all Verizon apps through settings or Titanium Backup.
The only thing I couldnt solve was how to remove the "SIM Card is not from Verizon Wireless" error in the status bar permanently, but thats just an annoyance, and causes no usability decrease.
Click to expand...
Click to collapse
Hello. It does not work in Ukraine. Tried many operators. Line GSM only emergency calls and all.I choose the network settings and 2G and 3G. Prompt what to do please.
_Z_x_Z_ said:
Hello. It does not work in Ukraine. Tried many operators. Line GSM only emergency calls and all.I choose the network settings and 2G and 3G. Prompt what to do please.
Click to expand...
Click to collapse
The device may not support Ukrainian bands, check with your carrier to see what band they use for HSPA/LTE
I'll have to get mine out and find it.
This only kinda works with T-Mobile. No LTE or 3G, just edge - and that keeps disconnecting and reconnecting about once every minute or so. I'll have to look into the return/exchange policy if I can't get data working.
brotherswing said:
This only kinda works with T-Mobile. No LTE or 3G, just edge - and that keeps disconnecting and reconnecting about once every minute or so. I'll have to look into the return/exchange policy if I can't get data working.
Click to expand...
Click to collapse
You must be in a non-refarmed area, in Shawnee, KS i was able to get Edge/3G/HSPA+/LTE
Whoareyou said:
You must be in a non-refarmed area, in Shawnee, KS i was able to get Edge/3G/HSPA+/LTE
Click to expand...
Click to collapse
Yep. See my snapshot above for Ting GSM (T-Mobile) in Florida. 4G LTE indicated.
I figured it out. With WiFi on my cell signal strength fluctuates wildly, but as soon as I turn off the WiFi the signal settles down, and I get a solid LTE connection averaging about 32Mbps. Strange, but I've seen crazier things.
Side note, the XT1528 is not eligible for the Motorola unlock program, and cannot be rooted by any method currently available. Several "one click root" tools claim to support it, but don't actually work.
Sent from my XT1528 using Tapatalk
Will the boost variant work on net10
Sent from my N800 using XDA Free mobile app
syrkles said:
Will the boost variant work on net10
Sent from my N800 using XDA Free mobile app
Click to expand...
Click to collapse
I personally haven't had any luck with the Sprint variants (Virgin Mobile, Boost) but I also didn't get to try using an activated Sim card, you could try, but I'm not sure
brotherswing said:
I figured it out. With WiFi on my cell signal strength fluctuates wildly, but as soon as I turn off the WiFi the signal settles down, and I get a solid LTE connection averaging about 32Mbps. Strange, but I've seen crazier things.
Side note, the XT1528 is not eligible for the Motorola unlock program, and cannot be rooted by any method currently available. Several "one click root" tools claim to support it, but don't actually work.
Sent from my XT1528 using Tapatalk
Click to expand...
Click to collapse
That root thread won't root the XT1528?
Root must be flashed with a custom recovery, which in turn requires that the boot loader be unlocked. Since the boot loader on the XT1528 can't be unlocked, we can't use that root technique.
brotherswing said:
Root must be flashed with a custom recovery, which in turn requires that the boot loader be unlocked. Since the boot loader on the XT1528 can't be unlocked, we can't use that root technique.
Click to expand...
Click to collapse
Ahh that's for clearing that up for me!
Related
Main thread: http://forum.xda-developers.com/z3-compact/general/unlock-bands-regions-z3c-root-required-t2940959
Originial thread here: http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
This thread server as a step-by-step guide for the unlocking process, but please takecare of all your personal/important information before modding your phone.
It is your own responsibility to backup all your data, including online and offline backup. I take no responsibility for any broken devices/sdcards/your house going down on fire and everything else.
This mod in fact does NOT unlock any sim lock, don't ask such a question.
And I do NOT think it will unlock [email protected], [email protected] (TBC, no such environment)
What you need:
Sony Xperia Z3 Compact (can be D5803/5833/SO-02G...)
Firmware rooted
Win7 PC with z3c ADB driver installed (I use the one come with flashtool)
QPST / QXDM / mzTool / z3c diag driver (http://goo.gl/pyN5fo, password: [email protected])
terminal emulator installed on z3c (can be optional, but will be easier when switching engineer mode on usb)
Give thanks to @BlackSoulxxx
Optional: FlashTool
Optional: Firmware stock FTF, the version must match your z3c running build (in case of recovery) you can get using XperiFirm
The following Guide assume you have: gain root access, installed SuperSU on phone, installed QPST/QXDM on PC.
I only tested on my D5833 and SO-02F, using Windows 7 Pro x64 SP1.
My originial plan is modding my SO-04E, to enable LTE in my area.
But I pass it to my girlfriend few days before I found this mod.
(her F-07E always boot to safe-mode, should be hardware failure)
Part 1: Connect to the phone's diagnostics mode
1. Enable superuser access in SuperSU if you have disabled it.
2. Go to: Setting -> Developer Option, make sure you turn on "Developer Option" on the top and turn OFF "USB Debugging"
3. Open terminal emulator, type the following command one by one:
Code:
su
setprop persist.usb.eng 1
4. Turn on "USB Debugging" under "Developer Option"
5. Connect your phone to PC via USB. Windows should found a few new hardware, wait until all driver installation fail.
6. Open "Device Manager" in "Computer Management", you should see some device named same as your device model, icons with yelow exclaimation mark.
7. Right-Click the first one, select Properties. Go to Detials tab, and under "Property" label, find the item called "Hardware Ids".
8. There should be some lines under the label Value. Notice the longest one, which should end with something like MI_01/MI_02 etc.
9. Your job is to find the correct device, which should end with MI_04. If you cannot find such device, either you have done something wrong, or your PC's usb fail to operate correctly. In later case, please switch to another PC. (My first trial end with this situation)
10. Once you find the correct device, go to Driver tab and press "Update Driver". Install the usb diag driver from the package, when asked about driver signature, just force insall it. Please make sure driver build match your window build, and do NOT use x86 driver on x64 windows.
Part 2: Unlock GSM/CDMA band(s)
11. Go to Start -> All Programs -> QPST, open "QPST Configuration". In the "Ports" tab, click the "Add New Port..." button in lower right corner.
12. In the Add New Port window, untick the option called "Show Serial and USB/QC Diagnostic ports only".
13. You should find an entry with the name saying z3c USB Modem. Select it and press OK.
14. Make sure the newly added port is "Enabled", under "Phone" block is MSM8974, Link is "USB".
15. Keep the configuration application running in background. Close the application will loose your connection to the phone.
16. Navigate to the installation path of QPST, in the /bin folder, find and execute "RF_NV_Manager.exe".
17. Go to "Setting" -> Comport, select the correct port you created in step 14.
18. In the top menu, "File" -> "Read from Phone". It should start reading your phone but take times.
19. After reading operation finished, in the lower left panel find the item with number 1877 (NV_RF_BC_CONFIG_I).
20. In the right panel, take a note on the originial value in case of recovery need.
21. Open mzTool, under "Band Preference (Bit info)", select "Decimal" under "Input Radax". In the "RF BC Config", enter the number you noted at step 20. It will list out all your current band supported by your headset, in the bit information box.
22. Still in mzTool, go to next tab named "Band Preference (NV Value)", select the band(s) you need. You can select all, but I personally recommand what you really need plus "[60] Reserved for BC10-1700", at lest those originally come with your phone.
23. After selecting band(s) you need, Copy the decimal value in the "RF BC Config" box below the selection area, and remove all space in between.
24. Go back to QPST again, find item #1877 (NV_RF_BC_CONFIG_I), paste the new value you calculated in step 23 into the right panel, and press the "Write NV"Button.
25. Go to "File" -> "Write Changes NV Items To Phone".
26. Close and reopen "RF_NV_Manager.exe", repeat step 17-19. If #1877 show you the value same as the one you calculated in step 23, then you are OK to proceed. If it revert back to the originial value (you should noted down at atep 20), sorry this mod is NOT for your headset and proceed to last part for quitting diagnositc mode.
27. Close RF NV Manager, unplug your headset and reboot it. If you got reception after reboot, then you are good. Please give thanks to @BlackSoulxxx
27a. Open dialer, type *#*#7378423#*#* (*#*#SERVICE#*#*), goto "Service info" -> "Configuration", you should see your unlocked band. If not, that means your phone reset it while reboot. You can do nothing unless you know how to disable the reset.
27b. If your phone cannot get signal after the mod, flash your phone with the stock FTF, do NOT select anyone under "Wipe:", select all under "Exclude:" but keep "BASEBAND" selected. This should flash the originial baseband firmware, hence remove this mod.
27c. If you still cannot get any reception, flash the whole stock FTF. This will wipe all your data, but reset it to factory installed status.
28. You are done for this section, you may continue for LTE band(s) unlock, or jump to last part for quitting diagnositc mode.
Part 3: Unlock LTE band(s)
29. Make sure you have unlocked "[60] Reserved for BC10-1700" in previous part.
30. Go to Start -> All Programs -> QXDM Professional, open "QXDM Professional". In the top menu select "Option" -> "Communication".
31. Under "All Ports in System:" select your port (should me same port as you use in QPST) and press "OK. QXDM should load all data automatically once you press ok.
32. In top menu, select "View" -> "New" -> "Common" -> "NV Browser". In the newly opened window, select "LTE" next to the "Category Filter".
33. Select the item with ID 06828 (Description = LTE BC Config, Full Path Name = LTE_BC_CONFIG). It should display "input" and "Value" of 0 under "Fields".
34. Press the "Read" button in the lower right corner, it should show a non-zero number under "Value". Please also write it down for recovery.
35. Convert the number, noted at step 34, to binary form. It will show which LTE bands your phone currently supported ...
35a. Start reading from right to left, the 1st digit from the right (right-most) will be corresponding to LTE Band 1, the 2nd digit will be for LTE Band 2, the 3rd digit will be for LTE Band 3. So the rule will be [ N-th digit will be for LTE Band N ].
35b. For each digit, 1 means the phone support that particular band while 0 means no support. For example in D5833, it should be 549890031829 = "1000000000001000000000000000000011010101" (LTE Band 1,3,5,7,8,28,40).
35c. So if you want to unlock some LTE band(s), filp such bit to 1. In case you have a gap like band 28-40, make sure you fill it with 0, or you will fail to unlock such channel.
36. Please work out our own value that suit your need. In my case I need LTE Band 1,3,5,7,8,9,19,21,28,38,39,40,41 so my value will be "11110000000001000000101000000000111010101" = 2061719830997
37. Go back to QXDM, double-click the 0 under "Input", replace it with the number you calculated at step 36 in decimal form.
38. Write the value to your phone by pressing the "Write" button next to "Read" button.
39. Close and reopen QXDM. Repeat step 31-35 and double check the number under "Value".
40. Close QXDM, unplug your phone and reboot it. If you got reception after reboot, then you are good. Please give thanks to @BlackSoulxxx
40a. Open dialer, type *#*#7378423#*#* (*#*#SERVICE#*#*), goto "Service info" -> "Configuration", you should see your unlocked band. If not, that means your phone reset it while reboot. You can do nothing unless you know how to disable the reset.
40b. If your phone cannot get signal after the mod, flash your phone with the stock FTF, do NOT select anyone under "Wipe:", select all under "Exclude:" but keep "BASEBAND" selected. This should flash the originial baseband firmware, hence remove this mod.
40c. If you still cannot get any reception, flash the whole stock FTF. This will wipe all your data, but reset it to factory installed status.
41. If you still cannot connect via LTE, open dialer and type *#*#4636#*#* (*#*#INFO#*#*), find "preferred network" and select "LTE".
41a. If it fail to connect, either is hardware restriction, or more software setting has to be done (some carrier has different APN for 3G/LTE)
42. You are done for this section, please continue for quitting diagnositc mode.
Part 4: Quit Diagnostics mode
43. Unplug your headset if you still connect it.
44. Turn off "USB Debugging" in "Developer Option".
45. Open terminal emulator, type the following command one by one:
Code:
su
setprop persist.usb.eng 0
46. You may either turn on "USB Dibugging", or just leave it as is.
46a. You can also turnoff superuser access in SuperSU, to enjoy Puzzle and Dragon (JP).
99. Don't forget to give thanks to @BlackSoulxxx
Thanks very much for this guide... before I attempt it, a dumb question;
Is this only of benefit for people that roam internationally often? Or can it improve the phone signal overall? (im in the UK)
Kind regards
Still Lte band 20 is not working in D5833, while it is listed in service menu((( I guess there are some hardware differences in radio module between D5833 and D5803
mamumba said:
Still Lte band 20 is not working in D5833, while it is listed in service menu((( I guess there are some hardware differences in radio module between D5833 and D5803
Click to expand...
Click to collapse
Thanks for the confirmation.
I own D5833, but live in Europe, and the available LTE bands in my country are 3 and 20.
I guess I won't be able to use the band 20, shame.
Can anyone, who own D5803 using this manual copy configuration of their phone in QXDM and PM me this file?
Wow, Much thanks. Very good. Great guide...
{
"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"
}
Excellent guide I will try it later, I had a D5833 and I need to get working the LTE 1700/2100 band
Noob question;
If you flash the FTF BASEBAND to revert de mod to it's original state, flashing the BASEBAND of a D5803 FTF to a D5833 model would not do the same trick?? (i suposse not but I'm asking anyway )
nmercy said:
Excellent guide I will try it later, I had a D5833 and I need to get working the LTE 1700/2100 band
Noob question;
If you flash the FTF BASEBAND to revert de mod to it's original state, flashing the BASEBAND of a D5803 FTF to a D5833 model would not do the same trick?? (i suposse not but I'm asking anyway )
Click to expand...
Click to collapse
You may try that, I won't take any production device on such risk anymore:angel:
Why do you flash d5803 Baseband to d5833 device ?
Quick note: someone reported Band4 AWS will not work even we modded the phone to support it ...
Every time I try this, I get a note that write protection on and read only? What am I doing wrong?
i want to try this with a xperia m2 model d2306 i need the band 3 for my lte please some help
Works great for me. Thanks heaps.
Has anyone successfully done this with a a D5803 to unlock TMobile's LTE Band 12 (700mHz)?
I have D5833 and tried to enable LTE band 4(AWS) and 2 to use it with T-Mobile.
Sadly, it doesn't work. The configuration page tells me that both 4 and 2 are enabled, but my phone can't get the signal.
I guess it's because of a hardware difference between D5833 and D5803
Quick note that worked for me on Windows 8 though I don't know if it's the limitation.
When I try to enter the new decimal for 3g bands, it doesn't seem to matter what I choose because as long as I select band 60 the software won't accept the number because its too long. If I change to selecting hex then there's fewer digits and it writes to the phone correctly without issue.
Anybody manage to unlock LTE band 20 ( 800 MHz ) on D6653 ( Z3 ) ???
Do you guys think it's possible or is it hardware limitation ( hope not ) ?
bofis said:
Has anyone successfully done this with a a D5803 to unlock TMobile's LTE Band 12 (700mHz)?
Click to expand...
Click to collapse
Bump. In the same boat (D5803 on T-Mobile) and wondering if it is worth performing all of the steps to unlock Band 12.
930U FIRMWARE
Those of you on Sprint that have been locked into the Sprint only firmware now can go back to the beloved U firmware...or flash a carrier firmware of your choice. If you are still on b4, I would stay, but if not, now is the chance to install the U firmware.
Check your current bootloader version. You may not be able to odin carrier firmware after install the U firmware.
I'll put the files in this Google Drive folder
1. Download Odin3_v3.13.1_3B_PatcheD.zip (Check Odin Folder)
2. Download SM-G930U_B.zip this is the newest U firmware (Check G930U Firmware Folder)
SM-G930U_A.zip if you are on 'A' firmware and want to go back to carrier
SM-G930Ub9.zip if you are on '9' firmware and want to go back to carrier
3. Extract both zips
4. Open Odin
5. Place the files from SM-G930Uxxxxxxxx.zip into the correct BL, AP, CP, CSC blanks.
6. Put phone into download mode (power, home, volume down)
7. Connect phone to computer. Odin should now say phone is added. If not, install the Samsung phone drivers
8. Press START. This process will take about 10 minutes
9. Phone will reboot with new U firmware and Oreo installed.
HotSpot
1. download the QuickShortcutMaker app from the playstore.
2. Search for lte
3. Expand com.test.LTEfunctionality
4. Click on the new com.test.LTEfunctionality
5. Press Try
6. Scroll to LTE APN Settings
7. Click APN2 LTE internet (may be different outside of sprint)
8. Scroll to APN Type
9. Add " ,dun " The line should show read < default,mms,dun >
10. Click 3 dots to save
Random Questions/Answers:
1. Is it multi-csc? Yes, it should support any US carrier if your phone is carrier unlocked
2. Wifi Calling/VoLTE supported? Wifi Calling=yes; VoLTE=not sure, sprint doesn't support it.
3. Are XXX bands used with my carrier unlocked? All bands with major US carriers appear to be working. You can follow this guide for unlocking additional LTE bands to confirm or unlock more international bands. Change the dial code for the USB settings to ##3424#
________________________________________________________________________________
Old Stuff
The "U" Firmware will work on any G930 Galaxy S7 (basically, USA variants) and is the Samsung Galaxy Touchwiz OS without carrier bloat. There is Samsung Bloat, but some can be uninstalled or disabled with a program like Package Disabler Pro or just disable it under application manager.
This should not trip Knox and will allow you to flash back to your original stock firmware. Warranty should not void, but I'm not responsible for bricked devices, exploding batteries, crying babies, Earth crushing meteors. If you have a question, best to ask it first!
There is an OTA to PG9 after you install this firmware. Feel free to upgrade after you flash this!
Installation:
1. Download
Updato Firmware Website or Sammobile Firmware Website or PL2 Firmware Google Drive (post 365 for MD5)
2. Extract files. May be best to download files over a wired connection!
3. Open ODIN and place the BL; AP; CP; CSC from the rar in the corresponding slots.
4. Place phone in download mode. Power + Vol Down + Home
5. Connect Phone to computer
6. Odin should recognize your phone. If not, you need to download and install the Samsung Driver Files
7. Press Start
8. It should flash the "U" Firmware.
____________________________________________________
Pit Mapping Error Fix
1. Download the Pit File Here
1a. You will have to down the Sprint PE1 firmware from Pit File Here or Pit File Here
The bootloader changed from v3 to v4 after the PGx update. If you are going to odin the latest firmware, you shouldn't have any issue. Going back to PGx to PCx/PEH will require this.
2. In Odin click the tab that says "Pit"
3. Odin will pull up a Warning dialogue. Click ok.
4. Click the long rectangular "Pit" button to select the pit file
5. Select the file that says "HEROQLTE_USA_SPR.pit" from the files you downloaded from my link.
6. With the pit file nw included, Add the AP, CP, and CSC files again and flash. (may need to reboot and go back into download mode)
7. Now odin the older 'U' firmware
____________________________________________
You cannot root this firmware with the Sprint model. Here are some apps that will give you some root/xposed features without them.
HotSpot
1. Download Shortcut Master Lite
2. Search for LTEfunctionality
3. Click on com.test.LTEfunctionality
4. Launch
5. Scroll down to LTE APN Setting
6. Add " ,dun " to APN2 LTE and EHRPD internet under APN type. That line should read default, mms, dun when you finish.
7. Native Hotspot should work. You may have to do this hack again if you update Profile.
Ad Blockers
None of these block ads on Youtube completely. Some will let you route through their servers to filter ads on Youtube via a VPN.
1. Adhell Uses Samsung Knox to block ads and trackers. Blocks most things on webpages and apps (no youtube), but saves a ton a battery since it doesn't require VPN. Also, it is FREE and well supported!
2. Disconnect Pro Similar to Adhell, but a paid app. Search the Galaxy App Store to buy it. Uses Samsung Knox too.
3. Ad Guard. Best I've used, but is a paid app for the good features.
4. AdClear. Some have had success with this, I've had mixed results.
5. BlockThis! Works well, but caused issues on some webpages.
Youtube Ads
This doesn't block ads, but it does silent and auto skip them. Cygery
Skip Tracks With Volume Keys
1. Frinky Music Controller Allows you to skip tracks with screen off.
2. Noyze Not sure if still being developed, but works. Let's you skip tracks by long pressing with screen off.
Voicemail Issue
I use Google Voice, so this worked for me. It is/was free to integrate your number with Google Voice...highly recommend if they still do it.
Install this apk for Sprint Visual Voicemail apk It will give you an error, but will take away the annoying voicemail notification. Then you can just hide the notification in the android settings and your problem will be solved. May work if you have regular voicemail, but probably not since it needs to write to system.
Doze Related
Remember to whitelist apps you want running in the background...like Pandora, Google Music, etc. I would leave them off at first and if it cuts off when the screen is off, you need to white list it.
For me, these both work best together and I saw a difference running both as opposed to either solely.
1. ForceDoze puts your phone into doze mode without the motion detectors and 30 minute wait. Great app! Does require you to install adb (adb installer) since you have to run a command to get it to run properly. Check Disable motion sensing and turn off while charging
2. Greenify The auto hibernation works great if we had root, but we don't. It works, but can be extremely annoying at times and can drain battery because it may continuously try to force stop/close an app you greenify. Plus, it will take a few seconds to re-unlock your phone immediately after you turn off the screen. However, I use it with force doze for the aggressive doze. I saw a difference in battery life by using them both.
Other Tips
Besides the obvious of gmail/facebook/whatspp/twitter/snapchat syncing
1. Turn off wi-fi scanning
2. Back up my data for Samsung and Google under back up and reset
3. Turn off some features under advanced features in settings...for example, palm swipe to capture if you never use it
4. Location History under Location
5. Change locating method...I leave mine on GPS, wi-fi, mobile, but some people want more battery life and turn it off.
6. Turn on developer options and change animations to 0.5
7. Turn off Always on Display under settings > display. I like it, so I leave it on...but takes about 2% an hour
Old stuff
Has anyone tried the 930U firmware for our Sprint phones (930P)? They seem to have success with it (935U) over at the Sprint S7 Edge forums.
On the Edge forums, they said you can root, but it messes with LTE/call abilities. However, it removes all Sprint bloatware and apparently allows for hotspot tethering.
According to the Edge forums, it is the universal firmware, so it should work on any qualcomm chipset phone. The firmware is for the Galaxy S7 Special Edition ( Link to Sprint site about it )
Anyway, here is the thread on the AT&T forum about it if you are interested. Didn't see a thread or info about here, so I was just wondering.
1. Download
https://drive.google.com/file/d/0B17W2gA_VROXV0M1NTZSaUxaajQ/vieworhttps://mega.nz/#!Gp9gXYKY!CQV9FcZTiW7wf9vUeEtUck-5mF_QOQFy-vbcjRrd5kA
http://forum.xda-developers.com/att-galaxy-s7/how-to/xda-community-love-g930u-t3415875
AdHell AdBlocker
1. Download two apk files from this folder
2. You need a Samsung Key
Sign in here with your Samsung account.
Go here to view your keys or generate new ones.
Click on Generate License Key. (Left corner)
Go to Samsung SDK section.
Select Development license key
Give the key a name in Add a key alias
Press Generate license key
Copy the key. The key should start with KLM
I copied it into Google Keep 3. Install and Open the other apk that isn't adh3v3.1.1.236_79a11719.apk
4. Select an APK File
5. Go to the file name adh3v3.1.1.236_79a11719.apk
6. Click Common Edit
7. Change the package name to com.XXXXXXXX.XXXXXXXXX replace the Xs with random letter/numbers. remember the first set has 8 replacements and the second set has 9.
8. Press Save
10. Click Install
11. Give permissions if asked
12. Click Enable Admin inside Adhell
13. For the code, put in the KLM key you just created
14. Accept the Samsung terms
15. Adhell should be working
Credit for links above (let me know if I left you out):
Ae3NerdGod
Tom Barrasso
Snoop05
cygery
Suyash Srijan
epicman_1200
turbozapekanka
jrkruse
micallan_17
If you have a good tip or trick, let me know and I'll add it to the OP for easy reference.
I flashed it on my G930P and its working very well. Samsung pay is also working. The only problem is that it didn't get the latest security update. Hope this helps.
After flashing...does data, calling, texting and all that work fine?
Euronymous88 said:
After flashing...does data, calling, texting and all that work fine?
Click to expand...
Click to collapse
Ive had this issue..i tried to find a way around it but nope, as soon as i flash the root file my phone reboots and all services r gone
shooterlgk said:
Ive had this issue..i tried to find a way around it but nope, as soon as i flash the root file my phone reboots and all services r gone
Click to expand...
Click to collapse
Yeah, that's a known issue about rooting the U firmware
What if I just flash the U firmware and don't root? Would data and all that work then?
Euronymous88 said:
What if I just flash the U firmware and don't root? Would data and all that work then?
Click to expand...
Click to collapse
Yea it works that way..but once u root it, it breaks everything
shooterlgk said:
Yea it works that way..but once u root it, it breaks everything
Click to expand...
Click to collapse
Can you Edit APN setting so the Hotspot will work or APN setting still Grey, I'm talking about flashing the Rom without Root, can I edit APN Setting?
---------- Post added at 10:23 AM ---------- Previous post was at 10:23 AM ----------
lvpre said:
Has anyone tried the 930U firmware for our Sprint phones (930P)? They seem to have success with it (935U) over at the Sprint S7 Edge forums.
On the Edge forums, they said you can root, but it messes with LTE/call abilities. However, it removes all Sprint bloatware and apparently allows for hotspot tethering.
According to the Edge forums, it is the universal firmware, so it should work on any qualcomm chipset phone. The firmware is for the Galaxy S7 Special Edition ( Link to Sprint site about it )
Anyway, here is the thread on the AT&T forum about it if you are interested. Didn't see a thread or info about here, so I was just wondering.
http://forum.xda-developers.com/att-galaxy-s7/how-to/xda-community-love-g930u-t3415875
Click to expand...
Click to collapse
Can you Edit APN setting so the Hotspot will work or APN setting still Grey, I'm talking about flashing the Rom without Root, can I edit APN Setting?
Not without root on this firmware. Some have said Hotspot works without issue, but I had to use the hurry and turn it on at boot technique.
Sent from my SM-G930P using Tapatalk
Mine is unlocked atm, running on koodo network. I was wondering if I try it and if I want to go back for some reason, how do you do that and will I loose my unlock?
lvpre said:
Not without root on this firmware. Some have said Hotspot works without issue, but I had to use the hurry and turn it on at boot technique.
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
how do you do it man (the hurry and turn it on at boot technique), I tried it many times, it's not working, any useful tips to make it work for me, by the way I'm on (G930PVPU2APE1), I really like the Hotspot
ahmadxbox360 said:
how do you do it man (the hurry and turn it on at boot technique), I tried it many times, it's not working, any useful tips to make it work for me, by the way I'm on (G930PVPU2APE1), I really like the Hotspot
Click to expand...
Click to collapse
That technique won't work with that version. I only got it to work on PE1 by rooting. I read that you can use PDAnet via the USB tether option.
lvpre said:
That technique won't work with that version. I only got it to work on PE1 by rooting. I read that you can use PDAnet via the USB tether option.
Click to expand...
Click to collapse
Which version will it work, I can downgrade to an version except for AB5
Mine had the APN settings grayed out under Settings but I found another way to edit them so I could do the hotspot trick.
1. Download Shortcut Master Lite
2. Look for com.test.LTEfunctionality
3. Scroll down to LTE APN Setting
4. You can now edit your APN settings
colin0998 said:
Mine had the APN settings grayed out under Settings but I found another way to edit them so I could do the hotspot trick.
1. Download Shortcut Master Lite
2. Look for com.test.LTEfunctionality
3. Scroll down to LTE APN Setting
4. You can now edit your APN settings
Click to expand...
Click to collapse
Awesome. And your stock, not rooted. And it let you turn it on and off without issue
Sent from my SM-G930P using Tapatalk
lvpre said:
Awesome. And your stock, not rooted. And it let you turn it on and off without issue
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Yes. Running it Stock without root. Ran into the same problem like everyone else with root. Currently looking around trying ways to get it to work.
colin0998 said:
Mine had the APN settings grayed out under Settings but I found another way to edit them so I could do the hotspot trick.
1. Download Shortcut Master Lite
2. Look for com.test.LTEfunctionality
3. Scroll down to LTE APN Setting
4. You can now edit your APN settings
Click to expand...
Click to collapse
I downloaded the app and searched but didn't find what you said to look for. I even used the search function and got no results.
Euronymous88 said:
I downloaded the app and searched but didn't find what you said to look for. I even used the search function and got no results.
Click to expand...
Click to collapse
{
"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"
}
Weird. That's all I searched for in it and was able to. You must be on the G930U or G935U firmware for it to work.
colin0998 said:
Weird. That's all I searched for in it and was able to. You must be on the G930U or G935U firmware for it to work.
Click to expand...
Click to collapse
you must be Rooted to Flash G930U or G935U, Right?
I just want the hotspot to work without Root
ahmadxbox360 said:
you must be Rooted to Flash G930U or G935U, Right?
I just want the hotspot to work without Root
Click to expand...
Click to collapse
No. You flash the G930U firmware in Odin.
follow the steps here to install it.
Hello-
Does anyone have Verizon working on their G4?
I'm in the US but cannot seem to get it to work.
I get a 3G signal and can make calls and text but cannot get 4G. It also drops out constantly saying I left the home network.
I can go into the hidden menu settings (#*#4636#*#*) and select the radio band as United States and I will get LTE. Works great but won't be able to make any phone calls or send texts as it complains the mobile service is not available.
When I change the radio band the APNs all change as well. I figured I could just edit an APN to make it all work but I don't get an option to edit or add an APN.
Thanks for any insight anyone might have.
Happy new year.
Working here, the network is crummy, but it's 4G for sure
ldeveraux said:
Working here, the network is crummy, but it's 4G for sure
Click to expand...
Click to collapse
Any tweaks you had to make to get it working?
fictitiousexistence said:
Any tweaks you had to make to get it working?
Click to expand...
Click to collapse
No of course not, it works perfectly out of the box. Sounds like you got a bad phone, bad SIM, or just bad coverage.
Did you get it to work? Rumor is it works best with an already activated sim card from another phone. I put mine in and it worked instantly. I get 4g LTE in AZ with Verizon Prepaid. Just got off the phone with my sister. LTE seems to drop when making a call so if you're forcing it, it might be causing the call issues.
{
"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"
}
The reason to use an already activated sim is because verizon did not want to support phones on their network they had not tested (or sold I'm sure). My Amazon G4 worked without problems straight out of the box. I would try a different already in use SIM anyway. If it doesn't improve service, reset phone and try again. Also if the sim you have doesn't work after happening to get the phone working this way, you"ll need to use that SIM in a Verizon phone first. Then put it back in your phone.
Also, are you on stock? I had 4g LTE on stock, and LOS 14.1, but on OMNIROM 8.1 I only have 3G which could just mean it's APN issues. Maybe switch to a more configurable ROM like LOS 14.1, and edit the APN settings? Rooting Omni atm to see if I can edit those apn settings.
edit: rooted and edited the APN settings to match stock, still stuck on 3G. Not sure what to do. Putting the sim card into my other stock G4 shows LTE.
edit2: missed a bunch of apn stuff the first time around
Reverted back to rooted stock copied everything from:
(adb shell)
content query --uri content://telephony/carriers/preferapn
loaded/rooted Omnirom8.1
updated as much info in default APN to stock as possible ... back to full LTE speeds!
superceege said:
Also, are you on stock? I had 4g LTE on stock, and LOS 14.1, but on OMNIROM 8.1 I only have 3G which could just mean it's APN issues. Maybe switch to a more configurable ROM like LOS 14.1, and edit the APN settings? Rooting Omni atm to see if I can edit those apn settings.
edit: rooted and edited the APN settings to match stock, still stuck on 3G. Not sure what to do. Putting the sim card into my other stock G4 shows LTE.
edit2: missed a bunch of apn stuff the first time around
Reverted back to rooted stock copied everything from:
(adb shell)
content query --uri content://telephony/carriers/preferapn
loaded/rooted Omnirom8.1
updated as much info in default APN to stock as possible ... back to full LTE speeds!
Click to expand...
Click to collapse
In Omni ROM you were able to edit the APN settings?
In RR everything is greyed out.
Also, the sim I have is an already activated working sim from a Verizon phone.
fictitiousexistence said:
In Omni ROM you were able to edit the APN settings?
In RR everything is greyed out.
Also, the sim I have is an already activated working sim from a Verizon phone.
Click to expand...
Click to collapse
Also, again, any way you could send the info you copied from stock?
superceege said:
Also, are you on stock? I had 4g LTE on stock, and LOS 14.1, but on OMNIROM 8.1 I only have 3G which could just mean it's APN issues. Maybe switch to a more configurable ROM like LOS 14.1, and edit the APN settings? Rooting Omni atm to see if I can edit those apn settings.
edit: rooted and edited the APN settings to match stock, still stuck on 3G. Not sure what to do. Putting the sim card into my other stock G4 shows LTE.
edit2: missed a bunch of apn stuff the first time around
Reverted back to rooted stock copied everything from:
(adb shell)
content query --uri content://telephony/carriers/preferapn
loaded/rooted Omnirom8.1
updated as much info in default APN to stock as possible ... back to full LTE speeds!
Click to expand...
Click to collapse
Tried LOS 14.1 like you mentioned and still was unable to edit the apn settings. No option to add and everything in the apn is greyed out. I tried the adb shell command you gave above and this is the output I get. Don't know why there isn't any permissions to write the apns.
athene:/ $ content query --uri content://telephony/carriers/preferapn
Error while accessing provider:telephony
java.lang.SecurityException: No permission to write APN settings
at android.os.Parcel.readException(Parcel.java:1684)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:183)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
at android.content.ContentProviderProxy.query(ContentProviderNative.java:421)
at com.android.commands.content.Content$QueryCommand.onExecute(Content.java:552)
at com.android.commands.content.Content$Command.execute(Content.java:418)
at com.android.commands.content.Content.main(Content.java:623)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:264)
athene:/ $
fictitiousexistence said:
Tried LOS 14.1 like you mentioned and still was unable to edit the apn settings. No option to add and everything in the apn is greyed out. I tried the adb shell command you gave above and this is the output I get. Don't know why there isn't any permissions to write the apns.
athene:/ $ content query --uri content://telephony/carriers/preferapn
Error while accessing provider:telephony
java.lang.SecurityException: No permission to write APN settings...
athene:/ $
Click to expand...
Click to collapse
Hey sorry, really busy these days.
The command only works if you have root.
adb shell
su
content query --uri content://telephony/carriers/preferapn
Note: content also has create, delete, and update.
example for changes: (xxxx is the id number from your previous command)
content update --uri content://telephony/carriers --where "_id=xxxx" --bind bearer:s:"0"
Magisk 15.3 rooted both stock and Omni8.1 for me. Even with root the APNs were grayed out for me too.
**Note: This is my Verizon Prepaid stock APN, yours might be slightly different if it's Verizon postpaid**
Row: 0 _id=2493, name=Verizon Internet, numeric=311480, mcc=311, mnc=480, apn=VZWINTERNET, user=, server=, password=, proxy=, port=, mmsproxy=, mmsport=, mmsc=http://mms.vtext.com/servlets/mms, authtype=-1, type=default,dun,supl, current=1, protocol=IPV4V6, roaming_protocol=IPV4V6, carrier_enabled=1, bearer=0, bearer_bitmask=63239, mvno_type=, mvno_match_data=, sub_id=-1, profile_id=0, modem_cognitive=1, max_conns=20, wait_time=0, max_conns_time=300, mtu=1428, mode=1, op_pco_id=65280, pco_mcc=311, pco_mnc=480, pco_mnc_inc_pcs_digit=1, edited=4, user_visible=1
I'm back on stock as I'm about to travel and stock functions the bestt with txts/calls/and internet atm.
VZW Prepaid doesn't like this phone, and won't allow setting VoLTE on the website. On stock LTE drops for phone calls but then comes back on.
From what I can tell, Omni8.1 has 47 APNs for 311480 and they weren't bouncing around right, messages wouldn't send on some APNs, LTE only worked on certain ones, a phone call would drop LTE and it would come back on another APN at 3G (but then the messages would send) and then take 10 minutes before going back to LTE, user selected default APN would drop back to the first one the system loaded. Couldn't get it right no matter what configs I put in. the two main APN _ids for Omni are 1541 and 1551, if you want to look at what it's doing.
If you data ever drops and comes back on a ROM with multiple APNs, that content query command will tell you the current APN you're on.
I'm on vzw prepaid mvno with a retus XT1625 no problems. Live in a rural area with only vzw towers and I buy service through puppywireless.
superceege said:
Hey sorry, really busy these days.
The command only works if you have root.
adb shell
su
content query --uri content://telephony/carriers/preferapn
Note: content also has create, delete, and update.
example for changes: (xxxx is the id number from your previous command)
content update --uri content://telephony/carriers --where "_id=xxxx" --bind bearer:s:"0"
Magisk 15.3 rooted both stock and Omni8.1 for me. Even with root the APNs were grayed out for me too.
**Note: This is my Verizon Prepaid stock APN, yours might be slightly different if it's Verizon postpaid**
Row: 0 _id=2493, name=Verizon Internet, numeric=311480, mcc=311, mnc=480, apn=VZWINTERNET, user=, server=, password=, proxy=, port=, mmsproxy=, mmsport=, mmsc=http://mms.vtext.com/servlets/mms, authtype=-1, type=default,dun,supl, current=1, protocol=IPV4V6, roaming_protocol=IPV4V6, carrier_enabled=1, bearer=0, bearer_bitmask=63239, mvno_type=, mvno_match_data=, sub_id=-1, profile_id=0, modem_cognitive=1, max_conns=20, wait_time=0, max_conns_time=300, mtu=1428, mode=1, op_pco_id=65280, pco_mcc=311, pco_mnc=480, pco_mnc_inc_pcs_digit=1, edited=4, user_visible=1
I'm back on stock as I'm about to travel and stock functions the bestt with txts/calls/and internet atm.
VZW Prepaid doesn't like this phone, and won't allow setting VoLTE on the website. On stock LTE drops for phone calls but then comes back on.
From what I can tell, Omni8.1 has 47 APNs for 311480 and they weren't bouncing around right, messages wouldn't send on some APNs, LTE only worked on certain ones, a phone call would drop LTE and it would come back on another APN at 3G (but then the messages would send) and then take 10 minutes before going back to LTE, user selected default APN would drop back to the first one the system loaded. Couldn't get it right no matter what configs I put in. the two main APN _ids for Omni are 1541 and 1551, if you want to look at what it's doing.
If you data ever drops and comes back on a ROM with multiple APNs, that content query command will tell you the current APN you're on.
Click to expand...
Click to collapse
Thanks. I figured out how to edit the apns now with the commands above but nothing is working. Still the same. I just dont understand how I can get 4g if I switch the radio band to US but then loose any phone service.
Are you on the XT1625 version? What baseband are you on?
fictitiousexistence said:
Thanks. I figured out how to edit the apns now with the commands above but nothing is working. Still the same. I just dont understand how I can get 4g if I switch the radio band to US but then loose any phone service.
Are you on the XT1625 version? What baseband are you on?
Click to expand...
Click to collapse
XT1625
Baseband: M8952_70009.08.03.45R ATHENE_RETUSA_CUST
Android 6.0.1
Build: MPJ24.139-64
I believe I got this stock zip online, I can look up the website when I get home on Tuesday.
superceege said:
XT1625
Baseband: M8952_70009.08.03.45R ATHENE_RETUSA_CUST
Android 6.0.1
Build: MPJ24.139-64
I believe I got this stock zip online, I can look up the website when I get home on Tuesday.
Click to expand...
Click to collapse
Does the baseband get updated each time you flash a ROM?
Mine appears to be on a much higher version. Does the one your on work with android 7 and up or do you have to flash it before going to a different ROM? Sorry I've been out of the ring for a long time. Thanks for all your help.
fictitiousexistence said:
Does the baseband get updated each time you flash a ROM?
Mine appears to be on a much higher version. Does the one your on work with android 7 and up or do you have to flash it before going to a different ROM? Sorry I've been out of the ring for a long time. Thanks for all your help.
Click to expand...
Click to collapse
I tried to take the Android 7 update but I forgot I was still rooted at the time, so it failed. If you have a copy of your current modem, you could try downloading my version and fastboot flash it and see if it works.
Found the link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#
Although I always thought newer was better. When you do a speed test what Mbps are you getting down/up? Where I live in Mesa, AZ I average ~30down/~20up, currently around Riverside County, CA
getting ~12down/~8up.
Good luck!
superceege said:
I tried to take the Android 7 update but I forgot I was still rooted at the time, so it failed. If you have a copy of your current modem, you could try downloading my version and fastboot flash it and see if it works.
Found the link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#
Although I always thought newer was better. When you do a speed test what Mbps are you getting down/up? Where I live in Mesa, AZ I average ~30down/~20up, currently around Riverside County, CA
getting ~12down/~8up.
Good luck!
Click to expand...
Click to collapse
So I flashed the modem using these commands:
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
but after rebooting the bootloader it shows the same as before. I'm on M8952_70030.25.03.64R ATHENE_RETUSA_CUST
With 3g the speeds seem like normal 3g speeds. But it cuts out all the time and so does the cell service. Now if I change the radio band to USA then 4G works and the download speed is around 30 mbps. But the cell service is not there, can't make any calls or send texts.
Just an quick suggestion to try out Lineage OS 14.1 maybe. I've noticed quite a bit better performance on VZW towers with lineage compared to the stock rom. Got full LTE/talk/text no problems on my prepaid sim ($10/mo). Stock ROM would drain my battery in 8 hours if set to Global, but lineage has no problems on Global.
d0gZpAw said:
Just an quick suggestion to try out Lineage OS 14.1 maybe. I've noticed quite a bit better performance on VZW towers with lineage compared to the stock rom. Got full LTE/talk/text no problems on my prepaid sim ($10/mo). Stock ROM would drain my battery in 8 hours if set to Global, but lineage has no problems on Global.
Click to expand...
Click to collapse
What's the secret to getting service for $10/month?
fictitiousexistence said:
So I flashed the modem using these commands:
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
but after rebooting the bootloader it shows the same as before. I'm on M8952_70030.25.03.64R ATHENE_RETUSA_CUST
With 3g the speeds seem like normal 3g speeds. But it cuts out all the time and so does the cell service. Now if I change the radio band to USA then 4G works and the download speed is around 30 mbps. But the cell service is not there, can't make any calls or send texts.
Click to expand...
Click to collapse
That was happening to me on Omni8.1. LTE around 30 down, but no voice/text. Do you have just one APN that semi-resembles the one I posted earlier?
There's a few more stock roms here [found in a random xda thread], if you can't go back, maybe you can go forward:
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/XT1625/
**no idea if they're legit or not**
I like Dogzpaw recommendation on LOS 14.1, like CM before it, it tends to be easier to customize than stock.
Also, have you check logcat and logcat radio for any clues?
adb shell, then:
logcat -d > /sdcard/logcat.txt
logcat -db radio > /sdcard/radio.txt
Recommendation: It's a lot of machine data to sort through...
kill wifi, kill data
you can clear the log buffers with:
logcat -c and logcat -b radio -c
toggle on data and wait for 3G
then repeat the original logcat commands with logcat2.txt/radio2.txt
exit the shell and adb pull them to your computer for easier analysis.
filter for lines containing: NetworkManager, NetworkController, ConnectivityManager, ConnectivityService or MotoNetwCtrlr
Might give you some idea of what's going on.
Feel free to post them, (check for personal data to redact first) I'll have some free time on Tuesday to help look at them.
superceege said:
What's the secret to getting service for $10/month?
Click to expand...
Click to collapse
at mypuppywireless I'm getting 250 min, 250 sms, and 100MB data for $10 a month.. if I ever go over (rare) then it just eats into the $10 cash balance I loaded over a year ago at a rate of $0.015/MB. Good stuff.
Unlocking more bands (specifically band 12) is on the way, please be patient as there are a lot of bugs with having a modified modem firmware.
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE! YOUR WARRANTY IS VOID IF YOU FOLLOW THIS TUTORIAL!
This took like 2 weeks to figure out, I was about to give up, but then it worked. VoLTE on band 4 and 2 for T-Mobile in the USA!!
I have only tested this on my phone, but it should work on others (assuming it is still an A2). I have not verified if this works for phones converted to the 6X so if you want to try please be careful.
Alright, enough with the warnings and stuff.
1. First, enable usb debugging and plug your phone into your computer.
1. Download qpst and install it. You will also need this file . Just save it somewhere, we will use it in a minute.
2. run the following commands (note that you MUST be rooted to enable this. The mod survives returning to stock unrooted, and even survives OTA so you can unroot when finished if you want.):
'''
adb shell
su
setenforce 0
setprop sys.usb.config diag,serial_cdev,rmnet,adb
'''
3. once installed there should be an entry in your start menu. open the folder labelled qpst and select the program "PDC".
4. click the Device dropdown and select the Qualcomm device. (it may not show up first time, make sure you have installed the drivers for your device)
5. once you select your device you should see a lost of items, this can take a minute depending on the speed of your computer.
6. click the load button and select the mcfg_sw.mbn you downloaded earlier.
7. "Commercial-TMO" should now be a listing in the description. Highlight it and right click on it, hover over "SetSelectedConfig" and select "sub0". Let it load for a bit.
8. it should now say pending on the Sub0 column of the Commercial-TMO. Now click activate and let it load.
9. on your phone, you must disable reigon checking. To do so go to your phone app and type in the following: *#*#86583#*#*
10. reboot your phone.
This worked for me, I have not verified that it works for others yet, so if it works for you, please let me know. Also let me know of any bugs.
Shreenshots below
{
"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"
}
Can this phone work on Metro PCS network
I tried and tried, but i cannot get PST to see my phone. I loaded qualcomm drivers and ADB drivers, nothing. Any suggestions?
Daha3ker said:
Unlocking more bands (specifically band 12) is on the way, please be patient as there are a lot of bugs with having a modified modem firmware.
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE! YOUR WARRANTY IS VOID IF YOU FOLLOW THIS TUTORIAL!
This took like 2 weeks to figure out, I was about to give up, but then it worked. VoLTE on band 4 and 2 for T-Mobile in the USA!!
I have only tested this on my phone, but it should work on others (assuming it is still an A2). I have not verified if this works for phones converted to the 6X so if you want to try please be careful.
Alright, enough with the warnings and stuff.
1. First, enable usb debugging and plug your phone into your computer.
1. Download qpst and install it. You will also need this file . Just save it somewhere, we will use it in a minute.
2.once installed there should be an entry in your start menu. open the folder labelled qpst and select the program "PDC".
3. click the Device dropdown and select the Qualcomm device. (it may not show up first time, make sure you have installed the drivers for your device)
4. once you select your device you should see a lost of items, this can take a minute depending on the speed of your computer.
5. click the load button and select the mcfg_sw.mbn you downloaded earlier.
6. "Commercial-TMO" should now be a listing in the description. Highlight it and right click on it, hover over "SetSelectedConfig" and select "sub0". Let it load for a bit.
7. it should now say pending on the Sub0 column of the Commercial-TMO. Now click activate and let it load.
8.on your phone, you must disable reigon checking. To do so go to your phone app and type in the following: *#*#86583#*#*
9. reboot your phone.
This worked for me, I have not verified that it works for others yet, so if it works for you, please let me know. Also let me know of any bugs.
Shreenshots below
Click to expand...
Click to collapse
This sounds scary. I thought volte works on band 12. If the band is missing how would it work. How can you confirm it actually works.
Hi!
I am running into the same issue of two computers (Win 7 and Win 10) that cannot see the phone. Anyone willing to help in getting PDC to see the phone? Thanks!
I have a couple questions for OP
Will this prevent any OTA?
Could you also take a screenshot of 4g while on a call?
What bugs do you experience?
I definitely see that your method unlocks some options in phone info, in the screenshots, but it doesn't necessarily prove anything if you can't see 4g while in a call and see a difference in speed. I notice the difference in speed when trying to do things on a call while on 3g, so if I were to do this I would definitely be able to tell it worked or not.
mymeatb18 said:
I have a couple questions for OP
Will this prevent any OTA?
Could you also take a screenshot of 4g while on a call?
What bugs do you experience?
I definitely see that your method unlocks some options in phone info, in the screenshots, but it doesn't necessarily prove anything if you can't see 4g while in a call and see a difference in speed. I notice the difference in speed when trying to do things on a call while on 3g, so if I were to do this I would definitely be able to tell it worked or not.
Click to expand...
Click to collapse
I would like to know this as well.
Ulver said:
I would like to know this as well.
Click to expand...
Click to collapse
If you want a specific screenshot let me know, I have been using this for a while though with no issues. The Band 12 has a lot of tuning data required and may not be compatible with all a2 devices without buying tuning equipment. (I used a friend's and hoped this was not the case) :/ I will keep working on it though. All is not lost yet.
As for the device not showing in the computer, it does require root as of the pie update because xiaomi disabled diag mode by default... :/
To enable it in the pie update you need to enter the following in adb shell for it to show up in qpst:
su
setprop sys.usb.config diag,adb
Note, do not reboot yet, rebooting resets these values..
Then re- insert the phone into your computer and it should show up.
The nice thing is that this survives ota and root removal once put on so if you want ota you can have it, just unroot once you get the mod working.
Hi Daha3ker,
I tried to enable with the mentioned commands and still PDC cannot see my phone.
Daha3ker said:
If you want a specific screenshot let me know, I have been using this for a while though with no issues. The Band 12 has a lot of tuning data required and may not be compatible with all a2 devices without buying tuning equipment. (I used a friend's and hoped this was not the case) :/ I will keep working on it though. All is not lost yet.
As for the device not showing in the computer, it does require root as of the pie update because xiaomi disabled diag mode by default... :/
To enable it in the pie update you need to enter the following in adb shell for it to show up in qpst:
su
setprop sys.usb.config acm,diag,mtp,adb
setprop persist.sys.usb.config acm,diag,mtp,adb
Note, do not reboot yet, rebooting resets these values..
Then re- insert the phone into your computer and it should show up.
The nice thing is that this survives ota and root removal once put on so if you want ota you can have it, just unroot once you get the mod working.
Click to expand...
Click to collapse
Can't seem to make the phone appear in PDC as well, I've rooted the device with magisk and have tried to input the commands as suggested but it is still not being detected...
This is what I have
Any word on this?
Update, with stock you need to enter the command
setprop sys.usb.config diag,adb
While the phone is plugged in to the computer for it to work. I was using a different set of debug tools.
I had to use the following command to get PDC to work.
su
setenforce 0
setprop sys.usb.config diag,serial_cdev,rmnet,adb
Im running Pixel Experience 20190320 rom with Magisk 18.1.
QPST 2.7.460
I used the QUD.WIN.1.1 Installer-10040.5 drivers on Windows 10 x64.
Could you unroot and relock bootloader and have this continue working and survive OTA updates?
---------- Post added at 11:18 PM ---------- Previous post was at 10:25 PM ----------
Looks like this survives a complete fastboot flash/relock. How would you reverse this and go back to stock?
---------- Post added at 11:30 PM ---------- Previous post was at 11:18 PM ----------
I want to switch back because sometimes when I make calls, it's high pitched and quiet. I can turn off voLTE to go back to the way it was, but would be nice to be stock again.
What bands it's unlocked?
In Brazil is primordial that b28 is unlocked to use Volte (700 MHz)
joaomiguelsm said:
What bands it's unlocked?
In Brazil is primordial that b28 is unlocked to use Volte (700 MHz)
Click to expand...
Click to collapse
Doesn't unlock any bands, just enables voLTE on T-Mobile in the USA. Unfortunately, it's pretty buggy, maybe due to recent updates.
Ulver said:
Doesn't unlock any bands, just enables voLTE on T-Mobile in the USA. Unfortunately, it's pretty buggy, maybe due to recent updates.
Click to expand...
Click to collapse
Oh, sad
This is the worst thin of Xiaomi in Brazil
PDC not recognizing phone
Hi,
I've been trying to get this working off and on for a couple of weeks. I can't get PDC to populate the drop down menu. I am able to get QPST to recognize the phone after doing :
su
setprop sys.usb.config diag,adb in an adb shell. After those commands, the Qualcomm driver loads (according to device manager). QPST configuration finds the phone on COM9. But when I load PDC I get nothing. Any thoughts? The voice calling on 2g in New York is horrible.
Thanks, Mike
mtrohan said:
Hi,
I've been trying to get this working off and on for a couple of weeks. I can't get PDC to populate the drop down menu. I am able to get QPST to recognize the phone after doing :
su
setprop sys.usb.config diag,adb in an adb shell. After those commands, the Qualcomm driver loads (according to device manager). QPST configuration finds the phone on COM9. But when I load PDC I get nothing. Any thoughts? The voice calling on 2g in New York is horrible.
Thanks, Mike
Click to expand...
Click to collapse
im getting same problem... can solve??
pleaaaase... need help.
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