I recently received the July AQG5 UK update for my Galaxy S8+ G955F (Exynos) and the service mode menu (*#2683662#) now says not supported when in the prior firmware version it worked fine. the service mode menu allows you to lock onto specific LTE bands and enable more advanceed features such as 4x4 MIMO and 256QAM as well as other things, as i mentioned earlier it worked fine in the previous update but now just says not supported.
The service mode code •#0011# still works fine, its just the other one mentioned that no longer works, anyone know why or if can get it back without having to flash back to a previous firmware version?
bump
bump, come on people someone must have some info
have you tried *#2263# ??
It's disabled on my Indian set also.
Maybe the 6gb set suffers with this aspect
esjames said:
have you tried *#2263# ??
Click to expand...
Click to collapse
that is for the snapdragon version, i have the international exynos version and the *#2683662# code used to work but after the update it now says unsupported
bluheart said:
It's disabled on my Indian set also.
Maybe the 6gb set suffers with this aspect
Click to expand...
Click to collapse
possibly yes, im not sure which soc the indian version has whether its snapdragon or exynos but if its exynos then seems samsung have disbaled it after a recent update for whatever reason
After months there is still no information for it on the Internet other than that it's not working, so, let's start.
What's in
Code:
logcat -b all -s RILD -s RILD2 -s RILS -s ServiceModeApp_RIL -s XMLParser
?
Which CSCs have it disabled?
Is it accessible with root?
That menu *#2683662# allowed the selection of antennas on a cell tower; channel selection (12 channels in UMTS band 1 as an example); band selection; CA enable/disable; LTE CAT selection; UMTS/LTE Release selection; viewing of 2G/3G neighbours by arfcn/uarfcn; 256QAM/4x4(but no one got it to rank 4, not working? no antenna for the BTS?); reject codes; displayed supported bands and CA Combinations; etc.
Bryan48765 said:
After months there is still no information for it on the Internet other than that it's not working, so, let's start.
What's in
Code:
logcat -b all -s RILD -s RILD2 -s RILS -s ServiceModeApp_RIL -s XMLParser
?
Which CSCs have it disabled?
Is it accessible with root?
That menu *#2683662# allowed the selection of antennas on a cell tower; channel selection (12 channels in UMTS band 1 as an example); band selection; CA enable/disable; LTE CAT selection; UMTS/LTE Release selection; viewing of 2G/3G neighbours by arfcn/uarfcn; 256QAM/4x4(but no one got it to rank 4, not working? no antenna for the BTS?); reject codes; displayed supported bands and CA Combinations; etc.
Click to expand...
Click to collapse
the logcat command you provided doesn't really give any useful information which can pinpoint any potential solution.
With regards to the CSC's, i can only comment on the XEU CSC which is part of the OXM multi csc and the one my phone is on and on that it says not supported for the code.
I haven't checked on root, don't really want to root my device
hamzahshakeel said:
the logcat command you provided doesn't really give any useful information which can pinpoint any potential solution.
Click to expand...
Click to collapse
But it could be compared with the logs of a working 2683662. How many of those names appear? Maybe Samsung has changed those names. It's the system wide no-root logcat "adb logcat"?(not sure about the /data/log one) It's while the RIL service mode is starting?
Bryan48765 said:
But it could be compared with the logs of a working 2683662. How many of those names appear? Maybe Samsung has changed those names. It's the system wide no-root logcat "adb logcat"?(not sure about the /data/log one) It's while the RIL service mode is starting?
Click to expand...
Click to collapse
i tried the logcat using the filters you provided (i.e. RILS, RILD etc) and yes it does bring back logs relating to those services however its not enough, all it outlines is when i type the code and monitor the logs subsequnt to the typing of the code the log just shows it trying to open the process associated with the menu, it doesnt show what it tries to do in between me sending the code and the response coming back so comparing that with a working code log will bring back nothing of note
however having said that i did try the full system wide log which was a bit teidous given it logs everything so going through it and pinpointing the relevant piece of log was a bit hard, i will attempt to log again using my s8+ and another samsung phone for which the same code works on and then post it here
try install phone info . this programm has all codes inside
Guys, the same in brazil. Since the begining of the year I've tried to activate 256QAM+MIMO 4x4 in my sumsung galaxy s8 using *#2683662# and by now it doen't work as return the message "not supported". Do you guys has reached some progress on it?
Seems they changed something inside the CP (modem.bin) and disabled the code. Flashing back the AQF7 - CP file will get back the code, but don't know the effect.
Yes I also noticed this a couple months back and made my own thread on it. So far there has been no progress except to flash a previous older update
Hi, you can get into advanced service menu with the app called phone info. Look for code 27663368378 and click Launch 0. Tested on rooted android 7, exynos galaxy s7.
no_name_no said:
Hi, you can get into advanced service menu with the app called phone info. Look for code 27663368378 and click Launch 0. Tested on rooted android 7, exynos galaxy s7.
Click to expand...
Click to collapse
Ive tried this but not work
Enviado desde mi SM-G935F mediante Tapatalk
hamzahshakeel said:
I recently received the July AQG5 UK update for my Galaxy S8+ G955F (Exynos) and the service mode menu (*#2683662#) now says not supported when in the prior firmware version it worked fine. the service mode menu allows you to lock onto specific LTE bands and enable more advanceed features such as 4x4 MIMO and 256QAM as well as other things, as i mentioned earlier it worked fine in the previous update but now just says not supported.
The service mode code #0011# still works fine, its just the other one mentioned that no longer works, anyone know why or if can get it back without having to flash back to a previous firmware version?
Click to expand...
Click to collapse
Unfortunately starting with Android v8.x.x (Oreo), test codes sent to the RilServiceModeApp via android_secret_code://<code> even by root are being denied.
If the test menu *#2263# or *#2683662# or *#2766338378# doesn't work with your current sim card, then try the following.
Find a couple of other active or inactive sim cards (can be another local carrier or from abroad), let the phone reboot and reconfigure its CSC while on the blue bootup screen, then try the code again, since test codes are CSC specific. It's a hit and miss affair, so be persistent.
If your phone is rooted, you can try these methods one at a time.
After each step, reboot the phone and try the test codes *#2263# or *#2683662# or *#2766338378#.
1. Using Shortcut Master (free version) from the PlayStore, tap on the menu, Secret Code Explorer, scroll down to 2263 or 2683662 or 2766338378 (or Menu > Search for "band"), tap on Launch0.
2. On combination firmware edit the file /efs/carrier/HiddenMenu and /efs/FactoryApp/keystr to be "ON", which will persists even after flashing back to stock firmware.
3. Copy the <CSC>_keystrings.dat from system/etc to root/etc and set permissions to 0744.
4. Try replacing the /system/priv-app/ModemServiceMode/ModemServiceMode.apk=com.sec.android.RilServiceModeApp from a previous Android version which had the codes working, and set the permissions to 0744.
5. Flash an earlier radio (CP) which had the codes working, if the current bootloader allows it to be downgraded.
This last method works on all Samsung models/firmwares without root, but requires a special test cable, which is only available for micro-USB ports at this time.
If you can find a similar cable with a USB-C connector, then it should work just fine. By the way, using an micro to C adapter does not work.
The following is only for phones with a micro-USB port, nonetheless it makes an interesting way to enable the hidden test menus.
You can actually enable most test codes (including RIL test codes which fail to execute on Oreo of newer even while rooted, such as *#2263# band change, *#2683662 lab test mode, and *#2766338378# engineering test menu, etc) on pretty much any model/firmware/region by simply plugging in a test cable into the phone (the other end doesn't have to be plugged in anywhere, it's just the built in resistor which enables test mode/FactoryMode).
It's important to follow the next steps exactly in this order: Open the dialer, exit the dialer with the Back key (not the Home button!), reopen the dialer and now it should accept most test codes.
These cheap test cables can be found on Ebay or AliExpress, just search for "Samsung 523K uart cable" or "Samsung 619K uart cable". Some come as a combo where you can simply switch the resistor values via a switch, but you must try both values, since only one or the other will work on certain models/firmwares/regions.
I've been using this method successfully for many years (currently on my Samsung S7 with the latest 2019 firmware), unfortunately these test cables are only available for micro-USB connectors, so it won't work on the newer USB-C phones even with an adapter (because it doesn't extend the resistor lines, only the data lines). If anyone finds a solution for USB-C, please post a message here.
Related
Hello, Recently I have bought an Unlocked At&T LG G3 The seller told me that the phone has a bad IMEI But it's unlocked to be used interntionally. When I received it, It's working fine, except the data network speed trough EDGE is too slow. As yo can see on the screenshot below I couldn't find the option to change the network type. and I'm stuck at "E" which mean EDGE.
http://s14.postimg.org/8r7vs0x27/Quick_Memo_2015_09_09_11_41_43_1.png
The phone's model is LG-D850 and it's running android 4.4.2 KitKat. it has no IMEI when I dial *#06# it shows IMEI: 0-05 on Settings/about phone/Status... it says IMEI: 0
Anyone here to help?
First, here are the possible reasons why you don't have an IMEI:
The phone was reported lost or stolen in the past.
The phone is still active on the owner's wireless carrier account.
There is money owed on the wireless carrier account to which the ESN/MEID/IMEI is connected.
For the reasons above, this community does not support such devices and you will probably not get any help.
But, this can also happen during a bad flash, so to fix the issue, you have 3 options:
Reset, unroot, then root and flash again
Try the suggested steps in this video
Find a company that can fix the problem by sending the phone to them
youngunix said:
First, here are the possible reasons why you don't have an IMEI:
The phone was reported lost or stolen in the past.
The phone is still active on the owner's wireless carrier account.
There is money owed on the wireless carrier account to which the ESN/MEID/IMEI is connected.
For the reasons above, this community does not support such devices and you will probably not get any help.
But, this can also happen during a bad flash, so to fix the issue, you have 3 options:
Reset, unroot, then root and flash again
Try the suggested steps in this video
Find a company that can fix the problem by sending the phone to them
Click to expand...
Click to collapse
Thanks for your reply, I'm not seeking to restore the IMEI. I just want to have the option to switch mobile network type. Should I root the phone and install a custom ROM?
AminhoVic said:
Thanks for your reply, I'm not seeking to restore the IMEI. I just want to have the option to switch mobile network type. Should I root the phone and install a custom ROM?
Click to expand...
Click to collapse
My bad, thought you wanted the IMEI back. In that case, the E (edge) is showing up could be due to Maroc Telecom throttling your connection or their towers could be far way (happens when you travel cross country too). Anyway, if you want to fiddle with network settings and try to get it to work BEFORE attempting to flash any ROM, try the following [3845#*855# 3845#*850#] USSD code from your stock dialer. You will get a hidden menu containing a juicy list of options and settings, so what you are probably looking for is the "LTE-Only" option (I am not sure though, but you can look through the settings).
And as always, attempt the suggestions AT YOUR OWN RISK.
youngunix said:
My bad, thought you wanted the IMEI back. In that case, the E (edge) is showing up could be due to Maroc Telecom throttling your connection or their towers could be far way (happens when you travel cross country too). Anyway, if you want to fiddle with network settings and try to get it to work BEFORE attempting to flash any ROM, try the following [3845#*855# 3845#*850#] USSD code from your stock dialer. You will get a hidden menu containing a juicy list of options and settings, so what you are probably looking for is the "LTE-Only" option (I am not sure though, but you can look through the settings).
And as always, attempt the suggestions AT YOUR OWN RISK.
Click to expand...
Click to collapse
I'm living at a major city, here the 4G works great. So yeah I have to change the mobile network type since it is on EDGE by defaut I guess.
I attemted the USSD code however it says "connection problem or invalid mmi code" after I hit dial. I have also tried a bunch of codes before but no luck.
I think I will falsh the phone that's the option left. I just have rooted the phone, then I will install TWRP and I will try to flash a ROM in it. What do youu suggest me to use from those ROMs posted here ?
AminhoVic said:
I'm living at a major city, here the 4G works great. So yeah I have to change the mobile network type since it is on EDGE by defaut I guess.
I attemted the USSD code however it says "connection problem or invalid mmi code" after I hit dial. I have also tried a bunch of codes before but no luck.
Click to expand...
Click to collapse
I get the same error if I use a third party dialer app (i.e., Dialer) until I tried the stock phone app.
I think I will falsh the phone that's the option left. I just have rooted the phone, then I will install TWRP and I will try to flash a ROM in it. What do youu suggest me to use from those ROMs posted here ?
Click to expand...
Click to collapse
I haven't flashed any custom ROMs on my LG, but from experience, each device somehow reacts differently to custom ROMs. For instance, I've flashed my S.G. Note (i717) over 30 times and some ROMs were stable at first then started having issues with them.
The best advice I can give you, is to pick a ROM from the list you posted and check the comments to see if it is stable or too many users have issues with it.
AminhoVic said:
I'm living at a major city, here the 4G works great. So yeah I have to change the mobile network type since it is on EDGE by defaut I guess.
I attemted the USSD code however it says "connection problem or invalid mmi code" after I hit dial. I have also tried a bunch of codes before but no luck.
I think I will falsh the phone that's the option left. I just have rooted the phone, then I will install TWRP and I will try to flash a ROM in it. What do youu suggest me to use from those ROMs posted here ?
Click to expand...
Click to collapse
Ever think that it does not have the correct bands for your carrier?
As was shown here: https://www.xda-developers.com/enable-preferred-wifi-calling-option-verizon-pixel-pixel-xl/ you could enable WiFi calling as your preferred calling method with this nice little ADB command. I can confirm with Oreo it worked, and stuck through reboots and all. I have however now sideloaded my Verizon Pixel with the Developer Preview of Android P. It was a smooth upgrade, however I can no longer get WiFi calling to be preferred with the ADB command. It was originally still listed there, and was still containing the "2" value, but the setting no longer worked. I did a factory reset to start fresh, and I notice that the setting is no longer present when doing the “settings list global” command. I tried adding the line and it still does not work. Anyone have a workaround or any ideas on what I can try to get the WiFi calling to be preferred again? I really rely upon it at work, as we have almost no cell signal, and I have come to love the previous ability I had to have it be the Preferred method for all my calls. Since I have one of the jacked Verizon Pixels, I was never able to unlock the Bootloader, so there is no going back for me! I do also want to say on that note though, for the last week, since I did the factory reset and re-did everything, my phone has been rock solid on the "P" Developer Preview!
Stealth111 said:
As was shown here: https://www.xda-developers.com/enable-preferred-wifi-calling-option-verizon-pixel-pixel-xl/ you could enable WiFi calling as your preferred calling method with this nice little ADB command. I can confirm with Oreo it worked, and stuck through reboots and all. I have however now sideloaded my Verizon Pixel with the Developer Preview of Android P. It was a smooth upgrade, however I can no longer get WiFi calling to be preferred with the ADB command. It was originally still listed there, and was still containing the "2" value, but the setting no longer worked. I did a factory reset to start fresh, and I notice that the setting is no longer present when doing the “settings list global” command. I tried adding the line and it still does not work. Anyone have a workaround or any ideas on what I can try to get the WiFi calling to be preferred again? I really rely upon it at work, as we have almost no cell signal, and I have come to love the previous ability I had to have it be the Preferred method for all my calls. Since I have one of the jacked Verizon Pixels, I was never able to unlock the Bootloader, so there is no going back for me! I do also want to say on that note though, for the last week, since I did the factory reset and re-did everything, my phone has been rock solid on the "P" Developer Preview!
Click to expand...
Click to collapse
I know there was a flashable magisk module that enabled the options, but it doesn't help with the actual ims status(*#*#4636#*#*, phone settings, ims status). It might be that you need the official Verizon rom that includes the necessary lib files, or that the dev preview doesn't include those and therefore you can't yet enable it?
Xdevillived666 said:
I know there was a flashable magisk module that enabled the options, but it doesn't help with the actual ims status(*#*#4636#*#*, phone settings, ims status). It might be that you need the official Verizon rom that includes the necessary lib files, or that the dev preview doesn't include those and therefore you can't yet enable it?
Click to expand...
Click to collapse
I though about the Verizon thing as well, but I also used the Developer Preview for Oreo, and it worked with it just fine, so I am thinkning they have just moved it somewhere else in the "P", or something of that nature, but I am hoping that someone here can possibly figure it out!
Stealth111 said:
I though about the Verizon thing as well, but I also used the Developer Preview for Oreo, and it worked with it just fine, so I am thinkning they have just moved it somewhere else in the "P", or something of that nature, but I am hoping that someone here can possibly figure it out!
Click to expand...
Click to collapse
I'm having the same problem after a recent update. WiFi calling no longer works, and the option has disappeared from settings.
Dialing *#*#4636#*#* no longer brings up the menu, either.
I tried via adb shell to set wfc_ims_mode=2, but that doesn't work. `settings list global` shows that it is set to 2, but even after reboot wifi calling still doesn't work.
euhn said:
I'm having the same problem after a recent update. WiFi calling no longer works, and the option has disappeared from settings.
Dialing *#*#4636#*#* no longer brings up the menu, either.
I tried via adb shell to set wfc_ims_mode=2, but that doesn't work. `settings list global` shows that it is set to 2, but even after reboot wifi calling still doesn't work.
Click to expand...
Click to collapse
Probably just something that handy yet been implemented, being it is a Dev preview . Same thing with the lockscreen shortcut icons for camera and phone.
Just an update. I stuck a T-Mobile SIM card in my phone and after using the magisk module I mentioned, the options appeared for the advanced and wifi calling. I'll do it again tomorrow and pay a screen . It's almost midnight here so gonna crash
I'm running stock p on verizon. Hoping someone comes up with a solution.
Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first
Xdevillived666 said:
Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first
Click to expand...
Click to collapse
Experiencing this issue after upgrading my Pixel XL and my wife's Pixel 2 to the Verizon Pie.
Details for my Pixel XL:
Android Version 9
Android Security Patch Level: August 5th, 2018
Kernel Version: 3.18.10-ga765425
Build Number: PPR1.180610.009
I used to use the ADB hack flawlessly, now I can't seem to make WiFi Calling Preferred over mobile network. So even though I have one bar that goes in and out, it uses the network then drops.
murraj2 said:
Experiencing this issue after upgrading my Pixel XL and my wife's Pixel 2 to the Verizon Pie.
Details for my Pixel XL:
Android Version 9
Android Security Patch Level: August 5th, 2018
Kernel Version: 3.18.10-ga765425
Build Number: PPR1.180610.009
I used to use the ADB hack flawlessly, now I can't seem to make WiFi Calling Preferred over mobile network. So even though I have one bar that goes in and out, it uses the network then drops.
Click to expand...
Click to collapse
I'm gonna pm ya
I haven't even updated to P yet and mine stopped working on the last security patch. I can set it back using adb. Reboot and wifi calling comes on. The first phone call works for about 5 minutes, then drops. The settings database values go back to default. The only way to get it to work again is to go through the whole process again.
Too much trouble. Sure would be nice to just turn it on and have it work.
Sent from my Pixel using Tapatalk
If you've already had WiFi calling working previously with pixel (I can only confirm first gen works with this)
Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first and then add the following (see doc).
Doc here
Just copy paste all lines according to instructions from previous post. Check and make sure under phone menu that you are instructions registered
Xdevillived666 said:
If you've already had WiFi calling working previously with pixel (I can only confirm first gen works with this)
Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first and then add the following (see doc).
Click to expand...
Click to collapse
I'm new to all this, what do you mean by, "Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first"
XDA won't let me put the text needed in the comments. Dload my PDF and copy paste the text from there to your buildprop
Does Google Pay still work after you edit the build.prop file?
Sent from my Pixel 2 XL using Tapatalk
abuttino said:
Does Google Pay still work after you edit the build.prop file?
Click to expand...
Click to collapse
I didn't not know. Can't use it in France anyways so I'm not worried about it.
Doesn't work in DP5
Hoping that someone else here can verify it in the regular version of pie.
I didn't switch to the RTM because WiFi calling is too important and I did want to test it though.
Sent from my Pixel 2 XL using Tapatalk
Hello all!
I have a Canadian A8 (SM-A530W) which was bought used. I currently live in Poland and it works fine here with my Polish T-Mobile SIM.
However, I recently went to Norway and it stopped working completely (no calls/text/data) and it says Unregistered SIM. If I tried to e.g. select a provider manually, I just got the message that searching for providers was not available at the moment.
I tried switching from LTE preferreed network mode to GSM/WDCMA, and I was able to search providers but it still wouldn't connect. I put a local SIM in the phone and it showed the same symptoms, but after switching back to the Polish one it worked for a while (LTE as well) so there is no problem with the radio/bands. However, after enabling/disabling flight mode, it no longer worked.
Anyone have any ideas? From the *#1234# info screen I have the following:
AP: A530WVLS1ARF1
CP: A530WVLS1ARF1
CSC: A530WOYV1ARF1
And the *#272*IMEI# menu shows BMC (Bell mobile canada) as the current CSC.
I saw somewhere that XAC is the "provider-ignorant" CSC for Canada, would it be worth trying to switch to this?
And, does anyone know the difference between the Canadian SM-A530W and the Euro SM-A530F? The hardware looks identical, so if it is only about the firmware maybe I can "switch" to SM-A530F if it would help with my problems...
I still have to try using a foreign SIM here in Poland to see if the same problems occur.
Any ideas and help is appreciated!
Update: I tried a Norwegian SIM here in Poland (so roaming) and it worked perfectly. I switched back and forth several times, no problems...
Anyone have any clue as to what can be causing this behaviour?
snolsen said:
Hello all!
I have a Canadian A8 (SM-A530W) which was bought used. I currently live in Poland and it works fine here with my Polish T-Mobile SIM.
However, I recently went to Norway and it stopped working completely (no calls/text/data) and it says Unregistered SIM. If I tried to e.g. select a provider manually, I just got the message that searching for providers was not available at the moment.
I tried switching from LTE preferreed network mode to GSM/WDCMA, and I was able to search providers but it still wouldn't connect. I put a local SIM in the phone and it showed the same symptoms, but after switching back to the Polish one it worked for a while (LTE as well) so there is no problem with the radio/bands. However, after enabling/disabling flight mode, it no longer worked.
Anyone have any ideas? From the *#1234# info screen I have the following:
AP: A530WVLS1ARF1
CP: A530WVLS1ARF1
CSC: A530WOYV1ARF1
And the *#272*IMEI# menu shows BMC (Bell mobile canada) as the current CSC.
I saw somewhere that XAC is the "provider-ignorant" CSC for Canada, would it be worth trying to switch to this?
And, does anyone know the difference between the Canadian SM-A530W and the Euro SM-A530F? The hardware looks identical, so if it is only about the firmware maybe I can "switch" to SM-A530F if it would help with my problems...
I still have to try using a foreign SIM here in Poland to see if the same problems occur.
Any ideas and help is appreciated!
Click to expand...
Click to collapse
The only difference I noticed is it actually needs its kernel because A530W uses different touchscreen firmware, all the rest seems same as A530F. Anyway de-brand Samsung phones is almost impossible without root, since they implemented multi-CSC (OMC) and the phone sets the correct one via checking the sales code in /efs
BlackMesa123 said:
The only difference I noticed is it actually needs its kernel because A530W uses different touchscreen firmware, all the rest seems same as A530F. Anyway de-brand Samsung phones is almost impossible without root, since they implemented multi-CSC (OMC) and the phone sets the correct one via checking the sales code in /efs
Click to expand...
Click to collapse
what no a530w doesnt have different touchscreen firmware than other variants, its actually the same...
SaboorTheCool said:
what no a530w doesnt have different touchscreen firmware than other variants, its actually the same...
Click to expand...
Click to collapse
Wrong lol. Check yourself kernel and you see A530W calls different touchkey drivers (here the firmware file, don't have under my eyes the jackpotlte_can dts file to show you it loads that file instead of classic a5y18 one).
BlackMesa123 said:
Wrong lol. Check yourself kernel and you see A530W calls different touchkey drivers (here the firmware file, don't have under my eyes the jackpotlte_can dts file to show you it loads that file instead of classic a5y18 one).
Click to expand...
Click to collapse
is there a way to flash the touchkey drivers to fix touch problems with custom roms?
935U 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 bootloader before installing, you may not be able to install carrier firmware afterwards.
I'll put the files in this Google Drive folder
1. Download Odin3_v3.13.1_3B_PatcheD.zip
2. Download SM-G935UB.zip (this is about 3 gigs)
3. Extract both zips
4. Open Odin
5. Place the files from SM-G935Ub9.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.
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
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
________________________________________________________________________________
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
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.
Second Post for 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#
It's all good
I can also confirm this is multi-csc. I just loaded it to my Sprint S7 Edge (SM-G935P) and everything is just like it was before (except for new firmware version!). Just use the HOME_CSC file when you flash in Odin and everything will be fine. I always wondered why Samsung released carrier versions of "Unlocked" firmware. Unlocked is unlocked. It's not carrier specific. I never had the nerve to try flashing any of the other carrier versions of the "U" firmware, until now. It's all good. Also, security patch level is October 1, 2018. And hotspot/Shortcut Master APN editing still works as before.
This should really be a boon to all the people with Sprint phone models stuck on higher bootloader versions of carrier firmware. Now you can finally get some unlocked goodness!
Enjoy!
Cooljb said:
I can also confirm this is multi-csc. I just loaded it to my Sprint S7 Edge (SM-G935P) and everything is just like it was before (except for new firmware version!). Just use the HOME_CSC file when you flash in Odin and everything will be fine. I always wondered why Samsung released carrier versions of "Unlocked" firmware. Unlocked is unlocked. It's not carrier specific. I never had the nerve to try flashing any of the other carrier versions of the "U" firmware, until now. It's all good. Also, security patch level is October 1, 2018. And hotspot/Shortcut Master APN editing still works as before.
This should really be a boon to all the people with Sprint phone models stuck on higher bootloader versions of carrier firmware. Now you can finally get some unlocked goodness!
Enjoy!
Click to expand...
Click to collapse
Are you on Sprint? Wifi Calling works with Sprint, but since Sprint doesn't have VoLTE, I can't test that. Yeah, I switched from Shortcut Master Lite to Quick Shortcut Maker because the former was removed from the play store.
Thanks for confirming!
lvpre said:
Are you on Sprint? Wifi Calling works with Sprint, but since Sprint doesn't have VoLTE, I can't test that. Yeah, I switched from Shortcut Master Lite to Quick Shortcut Maker because the former was removed from the play store.
Thanks for confirming!
Click to expand...
Click to collapse
Yes I'm on Sprint. I didn't know they had removed Shortcut Master (Lite) from the Play Store. I've just had it forever. I'd seen others mention using Quick Shortcut Maker as well. I might give it a try just for kicks. It obviously works similarly to Shortcut Master.
Cheers.
Been waiting on this a while, thanks OP for posting and hosting on GDrive!!
FYI - I wasn't sure the difference between the CSC and Home_CSC so I looked it up:
https://forum.xda-developers.com/showpost.php?p=68763638&postcount=2
let's say you wanna update your phone without wiping the data u have on it. you use the home csc. If u have custom recovery and custom rom and you wanna go back to stock firmware you flash the csc file.
rocket321 said:
Been waiting on this a while, thanks OP for posting and hosting on GDrive!!
FYI - I wasn't sure the difference between the CSC and Home_CSC so I looked it up:
https://forum.xda-developers.com/showpost.php?p=68763638&postcount=2
let's say you wanna update your phone without wiping the data u have on it. you use the home csc. If u have custom recovery and custom rom and you wanna go back to stock firmware you flash the csc file.
Click to expand...
Click to collapse
You're welcome. I would probably use the csc because of the difference, but only a suggestion
lvpre said:
You're welcome. I would probably use the csc because of the difference, but only a suggestion
Click to expand...
Click to collapse
I used CSC for a full wipe and the flash worked with no problems. Doing the google auto-restore so it will be downloading apps for a while but everything is looking good so far. LTE data on Sprint & SMS messaging both working as expected right out of the gate.
rocket321 said:
I used CSC for a full wipe and the flash worked with no problems. Doing the google auto-restore so it will be downloading apps for a while but everything is looking good so far. LTE data on Sprint & SMS messaging both working as expected right out of the gate.
Click to expand...
Click to collapse
WiFi calling works too, but it is in the phone settings app. You can also sideload the Sprint voicemail app too
lvpre said:
WiFi calling works too, but it is in the phone settings app. You can also sideload the Sprint voicemail app too
Click to expand...
Click to collapse
Do you have a source for the Sprint voicemail app/apk?
Cooljb said:
Do you have a source for the Sprint voicemail app/apk?
Click to expand...
Click to collapse
Let me know if this works and I'll add it to the OP:
https://drive.google.com/open?id=1uSGjlM1AlV6W8XFofVpbd1YnBZsah-Iq
lvpre said:
Let me know if this works and I'll add it to the OP:
https://drive.google.com/open?id=1uSGjlM1AlV6W8XFofVpbd1YnBZsah-Iq
Click to expand...
Click to collapse
I tried, but could not get it to work. None of the test voicemails I left ever showed up in the app. I tried restarting my phone but still nothing. I've tried to get it to work before and have never been successful. It's just as well anyway. Why in the world does a voicemail app need access to my location???!!! I hate apps that ask for broad, unnecessary permissions. That's why I don't run the Sprint firmware on my phone. What a horrible bloated mess it is. I don't see how people put up with all that crap on their phones. So many useless background processes running for all the bloatware that you can't uninstall. No thanks.
Thanks to Package Disabler Pro, I have a grand total of 11 processes running at any given time on my phone. And it runs fast and smooth, like it's supposed to. No lag, no stuttering ever. It really is a crime what carriers (and even Samsung) do with loading all their crapware on their phones.
Just curious, are you able to use this app on your phone with the U firmware? Did you have to jump through any hoops to make it work?
Cooljb said:
I tried, but could not get it to work. None of the test voicemails I left ever showed up in the app. I tried restarting my phone but still nothing. I've tried to get it to work before and have never been successful. It's just as well anyway. Why in the world does a voicemail app need access to my location???!!! I hate apps that ask for broad, unnecessary permissions. That's why I don't run the Sprint firmware on my phone. What a horrible bloated mess it is. I don't see how people put up with all that crap on their phones. So many useless background processes running for all the bloatware that you can't uninstall. No thanks.
Thanks to Package Disabler Pro, I have a grand total of 11 processes running at any given time on my phone. And it runs fast and smooth, like it's supposed to. No lag, no stuttering ever. It really is a crime what carriers (and even Samsung) do with loading all their crapware on their phones.
Just curious, are you able to use this app on your phone with the U firmware? Did you have to jump through any hoops to make it work?
Click to expand...
Click to collapse
I use google voice and forward to it for voicemail. Yeah, I just did a little research and apparently unlocked editions (Sprint calls them Special Editions) of the S7 and S8 have to use the old fashion voicemail because the system is only provision to work with the S9. Simple fix by Sprint, but then again..... I read a small lead about a tech who could reset something in the system to change it from the current system back to the old 9016 method. I'll check more into it. Sorry about it not working.
lvpre said:
I use google voice and forward to it for voicemail. Yeah, I just did a little research and apparently unlocked editions (Sprint calls them Special Editions) of the S7 and S8 have to use the old fashion voicemail because the system is only provision to work with the S9. Simple fix by Sprint, but then again..... I read a small lead about a tech who could reset something in the system to change it from the current system back to the old 9016 method. I'll check more into it. Sorry about it not working.
Click to expand...
Click to collapse
Thanks for trying anyway. :good:
Works great
Thanks very much for this. I loaded the this firmware on my SM-G935P and it works great with no problems at all. I put an activated AT&T sim card and an activated Tracfone sim card in my G935P with this firmware. Both were automatically configured with the correct bands when the phone booted up and everything I have checked seems to work perfectly and very fast with very little bloatware. Thanks again
Will it work with the cellphone above v4 Binary?
Will it work with the cellphone above v4 Binary?
coz i have updated the mobile and i m pretty sure that it updated my binary version too.
now i have to go back to U firmware will this work? or im still stuck with this?
mayocube said:
Will it work with the cellphone above v4 Binary?
coz i have updated the mobile and i m pretty sure that it updated my binary version too.
now i have to go back to U firmware will this work? or im still stuck with this?
Click to expand...
Click to collapse
Yes, this will work if you are above b4. If you are on b4, I would stay, but this will get you out of the Sprint screw job on that.
RCS features not working on U firmware?
Flashed U firmware just today and i was wondering if anyone else was able to get the RCS features to work? When i was previously on sprint firmware it was working just fine but now i see no option for the chat messages setting in the messages app. Everything else seems to be working though. Data and wifi calling. No bloatware!
izzy0101 said:
Flashed U firmware just today and i was wondering if anyone else was able to get the RCS features to work? When i was previously on sprint firmware it was working just fine but now i see no option for the chat messages setting in the messages app. Everything else seems to be working though. Data and wifi calling. No bloatware!
Click to expand...
Click to collapse
Are you still with Sprint? I'm using Android messages app by Google. It supports RCS on Sprint.
lvpre said:
Are you still with Sprint? I'm using Android messages app by Google. It supports RCS on Sprint.
Click to expand...
Click to collapse
Yes i am. I'm also using Google messages but the default messages app doesn't seem to have the same features.
I've a VoLTE/VoWiFi activated Telstra/Boost SIM that's confirmed to work fine with both stock-standard Moto G 5G Plus & iPhone 11 Pro Max, delivering those features in Australia.
Rog Phones in general & Rog phone 5 in particular are known to lack VoLTE/VoWiFi features with all of the Australian carriers. ASUS Zentalk forum has a few threads about it. (Of course, I too escalated it there for any official help, but none will be forthcoming anytime soon, from what I understand ). I'm genuinely in need of VoLTE at work due to terrible 3G but decent 4G there; and at home in need of VoWiFi due to terrible 3G but excellent WiFi backed by snappy fibre Internet connection.
My phone is an ASUS_I005DA model with build number WW_18.0840.2106.86. Neither "4G Calling" nor "Wi-Fi calling" settings are visible by default, but upon dialling "*#*#3642623344#*#*", those options become available. Though those features can be activated/toggled (and they stick around till the next reboot), they actually don't really make those features work (i.e., phone still drops down to 3G when making phone calls; similarly, calls simply don't go through WiFi, as is proven in airplane mode with WiFi on). This I understand is due to lack of .mbn files for the modem to support Australian carriers in general, Telstra in particular. (I gather that with previous Rog phone models, by injecting .mbn file(s) into the modem image, folks were able to get VoLTE and VoWiFi working in Australia.) I'm essentially looking for precise/tested/proven steps to accomplish just that but on Rog Phone 5.
This is where I've had it both boot loader unlocked & the system rooted with Magisk, in preparation for undertaking any and all such steps.
Has anybody been able to successfully access modem (i.e., Qualcomm Snapdragon X60 modem on Snapdragon 888 SoC found on this phone) from Windows or Linux systems for this sort of work? If yes, especially for Windows, what drivers did you use? (name, version info & where to download them from would greatly help) What additional software did you use on the Windows computer end (such as QPST) & on the phone end (such as QCOMDiagMode.apk & what version & from where was it sourced please?) etc. would be of great help.
A dumb question: Would it be at all possible to flash modem with updated image (incorporating the necessary .mbn file(s)) from within Android itself? Or Android itself doesn't have ADB to help with such tasks?? Just curious as I'm fine to work off either Windows or Linux end.
Thanks in advance for any useful guidance & direction.
The most likely answer would be to find how they made or picked the files with the 3 and try to make or find parallel 5 versions. The files should be compatible with fastboot (mbn is one of the extensions they use for firmware images).
[Guide] Enabling VoLTE/VoWiFi v2
Preface With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier...
forum.xda-developers.com
It's also going to be an extremely experimental process, so the only tested and proven way will be to let someone else do it first. Hopefully you can find someone else in Australia with the same issue that is willing to put their device up for testing.
Is there a working guide to enable the AsusVoLTE App on Android 11 ?
Mine keeps saying root is not available,
and the USB command to enable PDC mode -
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
doesnt work for me..
any ideas ?
JazonX said:
Is there a working guide to enable the AsusVoLTE App on Android 11 ?
Mine keeps saying root is not available,
and the USB command to enable PDC mode -
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
doesnt work for me..
any ideas ?
Click to expand...
Click to collapse
Can't detect root · Issue #2 · HomerSp/AsusVoLTE
Hi, I'm trying to use your app but any button returns: Failed enabling <feature>, are you rooted? The strange thing is that I have rooted my phone with Magisk and root checker is successful... Can ...
github.com
If you look at the code for the app, it is basically performing the setprop commands on your behalf. Not sure how far you'll get with the app fixed.
Regardless, I sent along a pull request to fix root detection
Do not hardcode su binary path by AbandonedCart · Pull Request #3 · HomerSp/AsusVoLTE
This fixes an issue where rooted devices are not recognized (#2)
github.com
twistedumbrella said:
Can't detect root · Issue #2 · HomerSp/AsusVoLTE
Hi, I'm trying to use your app but any button returns: Failed enabling <feature>, are you rooted? The strange thing is that I have rooted my phone with Magisk and root checker is successful... Can ...
github.com
If you look at the code for the app, it is basically performing the setprop commands on your behalf. Not sure how far you'll get with the app fixed.
Regardless, I sent along a pull request to fix root detection
Do not hardcode su binary path by AbandonedCart · Pull Request #3 · HomerSp/AsusVoLTE
This fixes an issue where rooted devices are not recognized (#2)
github.com
Click to expand...
Click to collapse
The setprop command didn't trigger anything like it did on the ROG II.
That why I wanted to try the app..
Just noticed the pull request! Hope @HomerSp would look into it.
JazonX said:
The setprop command didn't trigger anything like it did on the ROG II.
That why I wanted to try the app..
Just noticed the pull request! Hope @HomerSp would look into it.
Click to expand...
Click to collapse
AsusVoLTE/MainActivity.java at master · HomerSp/AsusVoLTE
Enable VoLTE/VoWiFi on the ROG Phone 2. Contribute to HomerSp/AsusVoLTE development by creating an account on GitHub.
github.com
It's literally running the setprop commands, but...
[MOD-ish] AsusVoLTE w/ Root Fix
This is a temporary solution to a pending pull request. This thread will be deprecated if or when the official release is updated. I don't have the original signing key, but there is really no reason to attempt reverse engineering an app that's...
forum.xda-developers.com
Edit: moved to a separate thread, since it is not specific to this issue
I've had VoLTE show up on mine from day one with no problems, using Vodafone AU. I don't get VoWifi though - I don't know if that's dependent on your ISP. I use TPG for broadband at home.
That's great to hear! Thanks for your confirmation.
"Vodafone Wi-Fi Calling is not available to customers on prepaid plans" in Australia, according to this: https://www.vodafone.com.au/support/device/wi-fi-calling
Perhaps you're their prepaid user?
Hopefully, official VoLTE and VoWiFi support for Telstra and Optus isn't too far, seeing how unofficial community support isn't ready just yet.
Did you managed to find a way to write .mbn? In AsusRogPhone2 it was easy (via Diag mode, efstools etc, with A10 though), but in AsusRogPhone5 efstools freezes every time at port listening stage, so this methos it's a no go for now, for some unknown reason.
Vodafone in Australia has VOLTE and WIFI calling for Rog 5. I went from Vodafone (had Volte) to Telstra (Had literally nothing, had 10 support tickets with telstra that first month in regards to getting volte, wifi calling and reception issues) said screw it, went right back to Vodafone, and boom had both Wifi calling and VOLTE on the Rog 5. Plus my reception is god tier. Telstra only supports certain phones (literally like 2 series) and thats it. So yeah. Thats how I solved the VOLTE issue. Should have just stuck with Voda to begin with, but wanted to give Telstra a go. Never again. Garbage service.
Just to wrap-up my original request, as of Nov 2021 firmware update, thanks to ASUS incorporating necessary MBN file(s) for Telstra (and Optus too from what I've heard at other forums) in that firmware update, after dialling Enhanced-4G code, VoLTE and VoWiFi functionalities become available in Settings. Toggling those options does successfully activate both of those functionalities on Telstra network. According to what I've heard on Whirlpool, even Optus is now supported in the same way.
Alas, those settings don't stick over a reboot, so what procedure needs to be done after every reboot. Perhaps ASUS will make them stick in a future firmware update.
It's possible to make them stick across reboots on a rooted phone, using setprop tool.
Thanks