Related
I'm not responsible for what might happen on your phone if you choose to dial any of these!
These are the codes that work on the standard phone dialler app on the Orange San Francisco, but I'm pretty sure they'll be almost identical on other models that we collectively know as "ZTE Blade". Known small differences (in texts) are down to whether the firmware expects to be running on an OLED or TFT display, and whether you've deleted seemingly unused apps like ChiperTest.apk, fcctest.apk and QcNvTest.apk. Most are prefixed with "*983*", which is "*ZTE*" in phone letters -- I've added a mnemonic for the other part where I think it's obvious (feel free to suggest better ones!).
"Automatic Inspection" runs through the basic tests automatically (usually you need press a button to move on to the next bit -- don't get thrown by any blank colour test screens!). There are a number of interesting items for developers, with hardware info and other goodies. If any of the descriptions don't make the function obvious then it's either poorly written or I don't know exactly what it does (I'll happily update this if others can explain better).
If the code has been recognised by the dialler then it will react immediately when you enter the final "#". If nothing happens when you've done that, don't press Dial!
Edit: on the ROMs based on the Japanese 2.2 you need to put the phone into "Engineering Mode" first, by dialling *ZTE*OPENEM# (*983*673636#) -- this action will be confirmed by a quick pop-up. To close this mode, dial *ZTE*CLOSEEM# (*983*2567336#) -- this then prompts whether you want to do a Factory Reset, which you do not have to do (you can simply Back away from this screen).
Dial Mnemonic Operation
*983*0# Menu (20:Battery/OLED/Back Light/Vibrator/Ringer/LED/Key/OLED off/SD/BT address/Radio Info/Memory/TouchPaint Test/Audio Loop/FM/Camera/GPS Test/IMEI/IMSI)
*983*3640*01# IMSI
*983*25# Battery Info[/COLOR]
*983*31# OLED Test
*983*26# Backlight Test
*983*850# Radio Test 0
*983*86# Vibrator & LED Test
*983*84# Ringer Test
*983*07*01# Headset Test
*983*07*02# Key Test
*983*3470# LCD Test
*983*81# SD Test
*983*890# -
*983*26*# Radio Test 1
*#06# IMEI
*983*27274# CRASH Reboot
*#08# Test Flag [Note: requires QcNvTest.apk in /system/app]
*#09***# BT Test
*983*1275# _ASK Dev Info
*983*7# Menu (4:Version/IMEI/IMSI/BT address)
*983*3640# DOH+ Phone Info (inc ping test, radio on/off)
*983*636# MEM Memory Test
*983*28# BT Emode BT Test
*983*477# GPS GPS Test
*983*21# Audio Loop Test
*983*70# Automatic Inspection
*#18# LED Test
*#19# TouchPaint Test
*983*36# FM FM Test
*983*57# Factory Reset
*983*473# Camera
*#23# Video Camera
*983*10# Delete (Touchscreeen) Calibration File
*#25# FM Test
*983*2726# SIM Contacts Op 1
*983*37# SIM Contacts Op 2
*983*6726# SIM Contacts Op 3
*983*154# "test" Menu (12:Self-starting/Software
Version/Hardware Version/PSN/Test Flag/[Completed]/Board Serial/Bluetooth
Address/SMS security/SMS Registration Status/Flash Type/PRL Version/Serial Configuration)
*983*07# Menu (9LED/Ringer/Vibrator/Key Test/Audio Loop/Headset Test/FM/Camera/SD)
*983*5182# Dev Info
*983*7469# SHOW Automatic Inspection
*#26***# Sensor Test
*983*7936# QXDM Save Qxdm in log system
*987*0# Menu (4roduce Information[->"test" Menu]/Automatic Inspection/Factory data reset/Battery information)
*#27***# Compass Test
*983*87274# USBSI USB Switch Test
*983*06# BT Test
*983*564738# LOGSET LOG Set (inc sys_rw)
*983*93# FCC Test [Note: requires fcctest.apk in /system/app]
*983*2377# CFQP Call Forwarding Query with PowerOn
*983*24474636# CHIPINFO Chiper Test (chip info) [Note: requires
ChiperTest.apk in /system/app]
*983*29873283# AXUPDATE Touchscreen Updater
*983*73564# SDLOG SD Log
Note: the above are for the standard ROM (well, apps) running 2.1. The current Froyo ROM (with standard dialler, etc.) does not have the Touchscreen Updater, but adds:
Dial Operation
*987*123456# DM Test
IN modaco
Hello, what code shude I use to know if my SF is TFT or Amoled?
Regards!
Check the build number in Settings>About Phone. AMOLED ends in 05, LCD ends in 08. IIRC all white SF models are 08 and most grey are 05 (unless its a newer unit which will likely be 08).
Thank´s man.
Mine is 01. What that means?
Looking at the screen characteristics it seems like LCD.
Thanks man. great post
Really nice. Works on Boost Mobile Warp Sync N9515.
Would you happen to have a code that forces prompt for unlock? (Changing sim cards doesn't trigger anything)
same here... up for this....
No Boost Mobile ZTE Warp Sync N9515 Unlock Screen
chinnyss said:
same here... up for this....
Click to expand...
Click to collapse
I think unlocking the Boost Mobile is a lost cause. I've tried several other sims and the only codes I've found to show the unlock menu don't work:
1) Alright then please remove the SIM card and try this code ###825*09#,
2) Got the prompt for code? Please enter the code you received,
3) Failed above, try *983*8284# to access the Unlock Menu,
4) Failed above, finally try *983*865625# to access the Unlock Menu.
zte warp elite n9518 rooted but still i can't use MSL reader or alogcat it says in root checker verify root congrats and after rebooting i got to root again please help just need to get SPC and or MSL code
You the MAN! THA KS.
kelvinpacquette said:
zte warp elite n9518 rooted but still i can't use MSL reader or alogcat it says in root checker verify root congrats and after rebooting i got to root again please help just need to get SPC and or MSL code
Click to expand...
Click to collapse
Can u tell me rhat what do i need to enable usb debigging or adb mode ?? I have to connect my zte z982 device to miracle sodtware, but unable to connect because frp lock.
I cant enable usb debugfing
techeligible3322 said:
Can u tell me rhat what do i need to enable usb debigging or adb mode ?? I have to connect my zte z982 device to miracle sodtware, but unable to connect because frp lock.
I cant enable usb debugfing
Click to expand...
Click to collapse
Edit: on the ROMs based on the Japanese 2.2 you need to put the phone into "Engineering Mode" first, by dialling *ZTE*OPENEM# (*983*673636#) -- this action will be confirmed by a quick pop-up. To close this mode, dial *ZTE*CLOSEEM# (*983*2567336#) -- this then prompts whether you want to do a Factory Reset, which you do not have to do (you can simply Back away from this screen).
Dialing the first set of numbers made it possible for me to turn on abd....
Sent from my SM-G550T using Tapatalk
Alright
paigesdavis1996 said:
Edit: on the ROMs based on the Japanese 2.2 you need to put the phone into "Engineering Mode" first, by dialling *ZTE*OPENEM# (*983*673636#) -- this action will be confirmed by a quick pop-up. To close this mode, dial *ZTE*CLOSEEM# (*983*2567336#) -- this then prompts whether you want to do a Factory Reset, which you do not have to do (you can simply Back away from this screen).
Dialing the first set of numbers made it possible for me to turn on abd....
Sent from my SM-G550T using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply
How did you enter / enable adb? I have a 971 and the 2nd code from your site doesn't work, I am able to enable eng. mode
I also tried the connect to computer in control panel and that doesn't do anything either.
Frp locked
Trick
techeligible3322 said:
Thank you for your reply
Click to expand...
Click to collapse
This worked for me and I have the ZTE z blade max thank you
Has this been proven to root the phone yet ? Please leave feedback .
Good News
#Starlord37# said:
This worked for me and I have the ZTE z blade max thank you
Click to expand...
Click to collapse
That's very good to know you are welcome
I haven't had a chance to try it fully yet as I have been trying to root my girlfriends Moto e4 with magisk which I will probably have done by the end of the night and then I plan to tackle my z982 will keep you posted though
Introduction:
This post is a guide to show how to perform the NV edit required to unlock US GSM carriers(AT&T and T-Mobile etc.) on the VZW XT907/926 RAZR M/HD stock modem using a Motorola serviceware tool called RadioComm.
This is simply a different method to perform the same hack that was discovered by Arnold Snarb in the main thread about ATT/T-Mobile here.
http://forum.xda-developers.com/showpost.php?p=37123644&postcount=158
Despite the fact that he thanked me for leading the way in that post, he did some really brilliant analysis of the logs in QXDM to isolate this NV Item and saw something in the them that I had missed as well as guessing correctly about it's significance, and deserves all of the credit for this hack.
Everyone should please go and thank him in that post for the outstanding work.
He used a tool called DFS to access and edit NV Item 8322 and change the value of the first byte from 01 to 00 which disables the checking of the MCC/MNC against a list of banned networks and flags MCC 310 as Invalid Country Code.
That method requires booting into BP Tools mode from the boot menu and loading the Qualcomm diagnostic device interfaces.
The problem is that there are no signed 64bit drivers available and you must force load the drivers on Win7/8 64 bit for the diagnostic port in order to see the device properly and have NV read/write access.
This has been a stumbling block for many users and makes the NV editing unnecessarily difficult.
This method uses Factory boot mode and allows RadioComm to have full diagnostic mode access via the Motorola USB Networking driver that loads normally with the standard USB driver set. I will demonstrate 2 different ways to perform the edit, one manual and one using a preconfigured SEEM table file that writes the value in a single operation.
Neither of these methods is as easy as an update.zip install from custom recovery would be, but we don't have a binary that supports the motorola.update_nv function that we used for prior MDM6600 based devices available to us for the MSM8960 devices.
Given that some form of diagnostic mode software and a PC is required, I feel that RadioComm is probably an easier option for most users as it avoids the driver problems and has a clearer and simpler interface for NV read/write access than DFS.
Once you have the latest Motorola drivers installed and RadioComm loaded, this guide should make it very easy and safe to perform what is generally a complicated and potentially dangerous task of editing the radio NVM(Non Volatile Memory).
RadioComm itself is a terrifyingly complex piece of software with a GUI that can bring even the most seasoned and experienced phone hacker to their knees wondering what all the various windows, modules and buttons do.
It is the premier Motorola serviceware application and is designed by and intended for use by top level radio engineers and technicians.
It is an extremely powerful application that can access all models and chipsets of Motorola devices and perform a vast array of diagnostic testing and configuration operations and can be fully automated via multiple scripting languages.
It's just plain scary and confusing and very dangerous if not taken seriously.
Warning and disclaimer:
DO NOT PLAY AROUND WITH ANY FEATURES OR RANDOMLY HIT ANY BUTTONS IN RADIOCOMM!!!
YOU CAN RENDER YOUR PHONE DYSFUNCTIONAL OR UNBOOTABLE IN SECONDS!!!
This cannot be emphasized strongly enough!
Follow the instructions exactly as they are written and shown in the screenshots and you will find it very simple to use have no trouble doing the edit with either method.
You, the user, are the only person responsible for your actions and performing this hack will absolutely void your warranty the same way rooting or any other modifications to your device's software does!
That said, this hack will be undetectable and have no outward visible signs of having been performed other than the fact that any GSM SIM should work afterward.
Root is NOT required and this can be safely done and undone at will without making any other changes on the device and all normal services function properly on VZW's network with the edit in place. It appears to only affect the US GSM network block and nothing else.
Prerequisites:
You need to have a recent set of Motorola USB drivers v. 5.9.0 or greater installed on your PC with a full USB 2.0 compatible port.
You need a standard Motorola micro USB cable.
RadioComm 11.12.xx I have included a link to 11.12.2 below.
https://dl.dropbox.com/u/7632904/RadioComm_v11.12.2_Install.zip
This has been tested on Win7 64bit and WinXP SP3 32bit with .NET Framework 4.0 installed.
Method:
This guide assumes you already have RadioComm and the drivers properly installed and have rebooted both PC and the phone afterward.
The first instructions and screenshots describe the initial setup and manual method using the FTM Common 1 tab and the NV Access window in RadioComm.
When you first open RadioComm you will get a popup stating that the version is more than 2 months old. Just close it and continue.
Now go to the top left corner and hit the Main button and select the MA: Common/MDM6x00 as shown in the first screenshot.
{
"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"
}
Next, go to Settings/USB and select PST USB Driver as shown in the second screenshot.
Test Command Format should default to P2K05 lower in Setings menu.
Leave all other options default.
Now we are ready to connect the phone and perform the edit.
Make sure you have Connect as Media Device in USB settings and USB Debugging enabled in Developer Options.
Power off the phone and then hold both Vol Up and Down + Power to enter the boot menu.
Use the Vol Down key to scroll down in the menu to Factory and then Vol Up key to select and the phone will boot.
Connect the USB cable and RadioComm will enumerate the phone and the radio button in the top right will change colors.
It will cycle sever times red to yellow and eventually go green when the device is fully enumerated and shows as XT907 in the status bar
at the bottom of the screen. You can read the Software Version and MEID/ESN/pESN buttons to make sure everything is working properly.
Each successful read the GUI will flash green and the Command buffer will turn green and any selected button will be green.
Any unsuccessful attempt will turn red.
If not, then restart everything and check over all settings again before proceeding.
Now go to the tabs bar across the top middle of the GUI and select FTM Common 1 tab and go to the NV access window in the center right of that tab and select the top menu Item "FFFF Manual Entry" as shown in the third screenshot.
Now hit the Read button and you will get 2 popup windows.
In the first window you will enter the Decimal NV Item ID 8322 and in the second you will enter the byte length to be read 1 as shown in the fourth screenshot.
When you hit ok it will read the NV Item and flash green and display the data in the hex output buffer below and you will see 01 for the value as shown in the fifth screen shot.
Now highlight the 01 and change it to 00 and hit the write button and this time it will only popup once asking for the Decimal NV Item ID 8322. When you hit OK the item will be written and the GUI will again flash green for a successful write as shown in the sixth screenshot.
You are now finished and can either use the restart button at top right of RadioComm to reboot or manually restart the phone.
The last screen shot is edited to show the steps to use the NV/SEEM feature with a SEEM table file I have provided below to do all of the steps as a single operation. Some users may find this easier than manually editing in the NV Access window but it's really almost the same number of steps.
Go to the top left and hit Features and select NV/SEEM and another window will open and the radio button will cycle again a couple time as it re enumerates the device again it will go green finally. Follow the instructions in the seventh screenshot and be sure to use the Restart button in the main window after you close NV/SEEM because its suspends the phone and it will be black screen and unresponsive and require holding Vol keys and Power for 10 secs to reset it otherwise.
Congrats! All done now and the rest is just putting in a SIM and selecting GSM/UMTS in Network Settings and everything should just work!
Below is the link for the .NVM SEEM table file.
https://dl.dropbox.com/u/7632904/TBH_RAZR_M_GSM_Unlock.NVM
Please use this thread to discuss issues relating to this method and RadioComm and keep general discussion of the phone on US carriers in the other thread, thank you!
<Reserved>
Thanks man.. gonna try this when I get home tonight. I was actually just thinking about switching vendors from VZW to someone else and didn't really want to buy a new phone.
Maybe now I don't have to. Proof is in the pudding though, maybe I'll by a cheap month of Straight Talk to see if it works?
Yehudah said:
Thanks man.. gonna try this when I get home tonight. I was actually just thinking about switching vendors from VZW to someone else and didn't really want to buy a new phone.
Maybe now I don't have to. Proof is in the pudding though, maybe I'll by a cheap month of Straight Talk to see if it works?
Click to expand...
Click to collapse
Running RAZR M in US on straight talk now. Works wonderful!!!
Thanks a lot! im a total noob when it comes to most of this, but it worked perfect for me!!
Hmm, MDM6x00? Won't that work on the OG RAZR XT912 / Droid 4 as well?
Skrilax_CZ said:
Hmm, MDM6x00? Won't that work on the OG RAZR XT912 / Droid 4 as well?
Click to expand...
Click to collapse
The MA used in RadioComm is the same chip set base as the RAZR/D4 because it's the closest to the MSM8960 available in this version, which is more than 18 months old now.
What we really need is an updated version of RadioComm with full support for the newer chip sets.
This specific NV Item 8322 does not exist on the MDM6600 chip set devices and I have not been able to find a similar boolean switch item for those phones, unfortunately.
I have been logging with QXDM extensively searching for a way to disable the MCC/MNC block on MDM6600 without success so far.
I have dumps of all of the readable NV items from 0000-12000 from many devices running various builds and even a dump from Chinese engineering build on P3Droid's Dev model where everything is working as it should with open GSM on US carriers.
I would love some help from someone with a better understanding of the radio and diagnostic mode access than myself.
Very few people know how to use the software to even start analyzing the problem.
Remember to install the latest Motorola drivers and *especially* highlight the entire 01 and type 00. I was backspacing only the 1 and it did not "stick" when writing. So HIGHLIGHT, don't backspace. Works perfectly.
is it possible to write the NV item to the Droid 4 then edit ? ?
cellzealot said:
The MA used in RadioComm is the same chip set base as the RAZR/D4 because it's the closest to the MSM8960 available in this version, which is more than 18 months old now.
What we really need is an updated version of RadioComm with full support for the newer chip sets.
This specific NV Item 8322 does not exist on the MDM6600 chip set devices and I have not been able to find a similar boolean switch item for those phones, unfortunately.
I have been logging with QXDM extensively searching for a way to disable the MCC/MNC block on MDM6600 without success so far.
I have dumps of all of the readable NV items from 0000-12000 from many devices running various builds and even a dump from Chinese engineering build on P3Droid's Dev model where everything is working as it should with open GSM on US carriers.
I would love some help from someone with a better understanding of the radio and diagnostic mode access than myself.
Very few people know how to use the software to even start analyzing the problem.
Click to expand...
Click to collapse
Can I use a similar way to unlock XT902(Japanese Razr M)? I can't find 8322 in XT902.......
Followed instructions and worked perfectly. The key for me was the latest Motorola drivers AND the Motorola USB cable that came with the phone. I tried other cables that both charged and synced but the only that worked for this was the Moto cable. Using Win XP SP3 ( 12 year old OS on brand new work laptop. WTF!)
i was wondering if this works on other networks such as boost mobile,net10, criket etc...? i honestly dont have enough money to buy a new phone and whatnot. the whole reason why i did this is because i lost my job and now i cant pay my phone bill and it keeps getting higher and higher.
AKG0214 said:
i was wondering if this works on other networks such as boost mobile,net10, criket etc...? i honestly dont have enough money to buy a new phone and whatnot. the whole reason why i did this is because i lost my job and now i cant pay my phone bill and it keeps getting higher and higher.
Click to expand...
Click to collapse
Boost - No
Cricket - No
They're both cdma. This is to allow the GSM side (SIM CARD based) of the phone to work on other carriers. With that said, your best options are
Net10, Straight Talk, ATT, T-Mobile, Simple Mobile, H20, Orange, and there's a plethora of others out there. Post paid and pre-paid.
@DSDD
I beleive your XT902 is GSM by default. So if what your asking is will this bypass the network lock, no, the device needs to be unlocked by code. Then you can use it outside of the current carrier/country.
after boot, it is set back to 01 again @ address 8322
my phone version is Bsmq_vzw-user 4.1.1 9.8.1Q_27-2 4 release-keysSM_BP_1139.000.32.62P
after write to 8322 with zeros, I read it again the confirm it is written, but after rebooting the phone, the value is back to 01 again.
I guess the verizon driver may override this value during rebooting?
any help?
should I root the phone?
==
thanks
cellzealot said:
Introduction:
This post is a guide to show how to perform the NV edit required to unlock US GSM carriers(AT&T and T-Mobile etc.) on the VZW XT907/926 RAZR M/HD stock modem using a Motorola serviceware tool called RadioComm.
This is simply a different method to perform the same hack that was discovered by Arnold Snarb in the main thread about ATT/T-Mobile here.
http://forum.xda-developers.com/showpost.php?p=37123644&postcount=158
Despite the fact that he thanked me for leading the way in that post, he did some really brilliant analysis of the logs in QXDM to isolate this NV Item and saw something in the them that I had missed as well as guessing correctly about it's significance, and deserves all of the credit for this hack.
Everyone should please go and thank him in that post for the outstanding work.
He used a tool called DFS to access and edit NV Item 8322 and change the value of the first byte from 01 to 00 which disables the checking of the MCC/MNC against a list of banned networks and flags MCC 310 as Invalid Country Code.
That method requires booting into BP Tools mode from the boot menu and loading the Qualcomm diagnostic device interfaces.
The problem is that there are no signed 64bit drivers available and you must force load the drivers on Win7/8 64 bit for the diagnostic port in order to see the device properly and have NV read/write access.
This has been a stumbling block for many users and makes the NV editing unnecessarily difficult.
This method uses Factory boot mode and allows RadioComm to have full diagnostic mode access via the Motorola USB Networking driver that loads normally with the standard USB driver set. I will demonstrate 2 different ways to perform the edit, one manual and one using a preconfigured SEEM table file that writes the value in a single operation.
Neither of these methods is as easy as an update.zip install from custom recovery would be, but we don't have a binary that supports the motorola.update_nv function that we used for prior MDM6600 based devices available to us for the MSM8960 devices.
Given that some form of diagnostic mode software and a PC is required, I feel that RadioComm is probably an easier option for most users as it avoids the driver problems and has a clearer and simpler interface for NV read/write access than DFS.
Once you have the latest Motorola drivers installed and RadioComm loaded, this guide should make it very easy and safe to perform what is generally a complicated and potentially dangerous task of editing the radio NVM(Non Volatile Memory).
RadioComm itself is a terrifyingly complex piece of software with a GUI that can bring even the most seasoned and experienced phone hacker to their knees wondering what all the various windows, modules and buttons do.
It is the premier Motorola serviceware application and is designed by and intended for use by top level radio engineers and technicians.
It is an extremely powerful application that can access all models and chipsets of Motorola devices and perform a vast array of diagnostic testing and configuration operations and can be fully automated via multiple scripting languages.
It's just plain scary and confusing and very dangerous if not taken seriously.
Warning and disclaimer:
DO NOT PLAY AROUND WITH ANY FEATURES OR RANDOMLY HIT ANY BUTTONS IN RADIOCOMM!!!
YOU CAN RENDER YOUR PHONE DYSFUNCTIONAL OR UNBOOTABLE IN SECONDS!!!
This cannot be emphasized strongly enough!
Follow the instructions exactly as they are written and shown in the screenshots and you will find it very simple to use have no trouble doing the edit with either method.
You, the user, are the only person responsible for your actions and performing this hack will absolutely void your warranty the same way rooting or any other modifications to your device's software does!
That said, this hack will be undetectable and have no outward visible signs of having been performed other than the fact that any GSM SIM should work afterward.
Root is NOT required and this can be safely done and undone at will without making any other changes on the device and all normal services function properly on VZW's network with the edit in place. It appears to only affect the US GSM network block and nothing else.
Prerequisites:
You need to have a recent set of Motorola USB drivers v. 5.9.0 or greater installed on your PC with a full USB 2.0 compatible port.
You need a standard Motorola micro USB cable.
RadioComm 11.12.xx I have included a link to 11.12.2 below.
https://dl.dropbox.com/u/7632904/RadioComm_v11.12.2_Install.zip
This has been tested on Win7 64bit and WinXP SP3 32bit with .NET Framework 4.0 installed.
Method:
This guide assumes you already have RadioComm and the drivers properly installed and have rebooted both PC and the phone afterward.
The first instructions and screenshots describe the initial setup and manual method using the FTM Common 1 tab and the NV Access window in RadioComm.
When you first open RadioComm you will get a popup stating that the version is more than 2 months old. Just close it and continue.
Now go to the top left corner and hit the Main button and select the MA: Common/MDM6x00 as shown in the first screenshot.
Next, go to Settings/USB and select PST USB Driver as shown in the second screenshot.
Test Command Format should default to P2K05 lower in Setings menu.
Leave all other options default.
Now we are ready to connect the phone and perform the edit.
Make sure you have Connect as Media Device in USB settings and USB Debugging enabled in Developer Options.
Power off the phone and then hold both Vol Up and Down + Power to enter the boot menu.
Use the Vol Down key to scroll down in the menu to Factory and then Vol Up key to select and the phone will boot.
Connect the USB cable and RadioComm will enumerate the phone and the radio button in the top right will change colors.
It will cycle sever times red to yellow and eventually go green when the device is fully enumerated and shows as XT907 in the status bar
at the bottom of the screen. You can read the Software Version and MEID/ESN/pESN buttons to make sure everything is working properly.
Each successful read the GUI will flash green and the Command buffer will turn green and any selected button will be green.
Any unsuccessful attempt will turn red.
If not, then restart everything and check over all settings again before proceeding.
Now go to the tabs bar across the top middle of the GUI and select FTM Common 1 tab and go to the NV access window in the center right of that tab and select the top menu Item "FFFF Manual Entry" as shown in the third screenshot.
Now hit the Read button and you will get 2 popup windows.
In the first window you will enter the Decimal NV Item ID 8322 and in the second you will enter the byte length to be read 1 as shown in the fourth screenshot.
When you hit ok it will read the NV Item and flash green and display the data in the hex output buffer below and you will see 01 for the value as shown in the fifth screen shot.
Now highlight the 01 and change it to 00 and hit the write button and this time it will only popup once asking for the Decimal NV Item ID 8322. When you hit OK the item will be written and the GUI will again flash green for a successful write as shown in the sixth screenshot.
You are now finished and can either use the restart button at top right of RadioComm to reboot or manually restart the phone.
The last screen shot is edited to show the steps to use the NV/SEEM feature with a SEEM table file I have provided below to do all of the steps as a single operation. Some users may find this easier than manually editing in the NV Access window but it's really almost the same number of steps.
Go to the top left and hit Features and select NV/SEEM and another window will open and the radio button will cycle again a couple time as it re enumerates the device again it will go green finally. Follow the instructions in the seventh screenshot and be sure to use the Restart button in the main window after you close NV/SEEM because its suspends the phone and it will be black screen and unresponsive and require holding Vol keys and Power for 10 secs to reset it otherwise.
Congrats! All done now and the rest is just putting in a SIM and selecting GSM/UMTS in Network Settings and everything should just work!
Below is the link for the .NVM SEEM table file.
https://dl.dropbox.com/u/7632904/TBH_RAZR_M_GSM_Unlock.NVM
Please use this thread to discuss issues relating to this method and RadioComm and keep general discussion of the phone on US carriers in the other thread, thank you!
Click to expand...
Click to collapse
---------- Post added at 11:14 PM ---------- Previous post was at 10:48 PM ----------
tried again for couple of times, this time it actually works.
maybe last time I reboot the phone too early?
sipida said:
my phone version is Bsmq_vzw-user 4.1.1 9.8.1Q_27-2 4 release-keysSM_BP_1139.000.32.62P
after write to 8322 with zeros, I read it again the confirm it is written, but after rebooting the phone, the value is back to 01 again.
I guess the verizon driver may override this value during rebooting?
any help?
should I root the phone?
==
thanks
Click to expand...
Click to collapse
Glad you got it working. There is no VZW software on the phone capable of writing to the radio NV, so it's not being reverted by anything.
If anyone else has similar issues I would suggest trying the NV/SEEM method as that will definitely write the item properly.
queberican351 said:
@DSDD
I beleive your XT902 is GSM by default. So if what your asking is will this bypass the network lock, no, the device needs to be unlocked by code. Then you can use it outside of the current carrier/country.
Click to expand...
Click to collapse
XT902 has sim lock, and there is no way to key in unlock code. So I think it maybe unlocked by modifying another NV item.
Does this tutorial unlock mobile data usage on other carriers. I cannot seem to get data working on my XT907 in Australia. GSM and MMS work fine, so why doesnt Data?
I don't know for certain because I only have experience with domestic US GSM carriers, but I tend to doubt it.
You can try it and see and revert it easily if it doesn't work. You can also try flashing the Telstra XT905 NON-HLOS.bin(modem) and fsg.mbn(carrierEFS/NVM config).
This was the method used to get US GSM service on XT907 before the method shown here was discovered.
It works but is limited to GSM/EDGE data services here in the US.
I am inclined to think it is some other problem with the device because it should work as a global capable phone by default.
dsdd said:
XT902 has sim lock, and there is no way to key in unlock code. So I think it maybe unlocked by modifying another NV item.
Click to expand...
Click to collapse
If it has a sim lock and you can acquire the code open your dialer and press #073887* (#0SETUP*) and it'll prompt you for the code.
Several people have PMd me questions about this method and I would much prefer that they be posted here in the thread so that everyone may benefit from the information.
Please include as much information about your PC and driver versions and be as thorough as possible in explaining your problems.
Helo from Slovenia,
perhaps i found a way to boost signal or unlock bands in Yotaphone 2.
Go to android secret menu *#*#4636#*#*
Then go information about phone menu and scroll down.
There is a option for choosing priority band, normaly its choosen LTE/WCDMA
Klick on this and switch the options to TD-SCDMA,GSM/WCDMA and LTE or TD-SCDMA,LTE,CDMA,EvDo GSM, WCDMA
Now watch the signal boosting
I checked same locations driving yesterday and today with car. Where i yesterday got no signal, today i got fully edge signal.
And no signal outage today no matter the location
Check this option and let me know if it works there too. I tried on Android 4.4.3 and 5 work both.
I put the first one, but how can I see the difference? the problems was not getting the 2G signal at all if I force in 2G. But if I force it now, your suggested settings will change.
What is the difference between TD-SCDMA,GSM/WCDMA and LTE or TD-SCDMA,LTE,CDMA,EvDo GSM, WCDMA?
May I ask you which mobile operator you have and which radio & firmware you use on your YotaPhone2?
TheArt. said:
I put the first one, but how can I see the difference? the problems was not getting the 2G signal at all if I force in 2G. But if I force it now, your suggested settings will change.
What is the difference between TD-SCDMA,GSM/WCDMA and LTE or TD-SCDMA,LTE,CDMA,EvDo GSM, WCDMA?
May I ask you which mobile operator you have and which radio & firmware you use on your YotaPhone2?
Click to expand...
Click to collapse
you have to go to spots/locations where you got no signal before and try it now ?
Setting your phone to the wrong settings so it fails over to 2G will no doubt improve your signal strength no end. But personally I would prefer to get fast internet on the move, and leave your radio settings well alone!
There are apps you can get that are called 'signal boosters' they just work by turning off your phone radio and then on again. If you were not connected to a nearby cell but one farther away this will 'boost your signal' ...
You're probably experiencing either or both of these effects. as well as the 4G effect - which is that if you have a local 4G aerial all the cellphones that can do so will be connecting to that, leaving you free to connect to an empty 3G cell instead with lots of bandwidth. Maybe not what you had planned to do, but actually improving your performance by setting the wrong settings
Did anyone already find the secret USB menu code to put the device into Modem mode? As the YotaPhone has a Qualcomm processor, this could be used to enable additional LTE bands, which really would help with reception like in [GUIDE] Add all GSM and LTE bands to your phone.
seems cool! We have to test
Crazyphil01 said:
Did anyone already find the secret USB menu code to put the device into Modem mode? As the YotaPhone has a Qualcomm processor, this could be used to enable additional LTE bands, which really would help with reception like in [GUIDE] Add all GSM and LTE bands to your phone.
Click to expand...
Click to collapse
Modem mode can setted by change buildprop sys.usb.config=diag.
Next read this.
w()$k said:
Modem mode can setted by change buildprop sys.usb.config=diag.
Next read this.
Click to expand...
Click to collapse
Ah, I haven't noticed that post, so we're making progress but no clear results yet :fingers-crossed:
here on XDA there's also this thread about unlocking frequencies: https://forum.xda-developers.com/yotaphone-one/help/unlocking-additional-radio-basebands-t3523000
TD-WCDMA won't work in spain. TD stands for Time Division and many countries work with FD (Frecuency Division)
Hi,
I am much interested in changing the LTE of YD206, has anyone suceed yet on this phone? A tuto would be really awesome! As I am new to android it would definitly help!
@TheArt. could you eventually translate the post please? My russian is far not good enought and google translated does not make much sens...! Did you succeed modifying the bands?
UNLOCK LTE BAND B20 - 800Mhz and B38
I will translate here the work of three 4pda users who must be thanked a lot for their work! unkernet, ssho and BoyNG. Thank also to mamant1988 who put everything together.
The original 4pda guide can be found here (in russian): http://4pda.ru/forum/index.php?showtopic=797643&view=findpost&p=59716629
UNLOCK B20 LTE BAND ON YD206
Starting point is a rooted YD206 with latest RU 134 firmware, TWRP and ADB-USB-debug enabled. Do this procedure carefully and write down all the modifications and default values. The changes are performed on NVRAM level, so flashing firmwares will not affect them. Flashing firmwares will, however, affect modified baseband, as any other "radio" part as usual.
Download here the .zip archive which contains what is needed for this guide, including some screenshots of how things should be displayed.
Download the modified baseband RU-CN here and put it into the internal memory of the phone: it will be flashed in the end.
Install QPST and QXDM Qualcomm programs on Windows, they are in the above archive.
Enable the installation of unsigned drivers in Windows (like this). This is needed to install drivers for the diagnostical port later on.
Download Terminal Emulator from Play Store.
In the Terminal, write the following to get root access:
Code:
su
then:
Code:
setprop sys.usb.config diag,adb
Connect the phone via USB to the PC, in the Device Manager it should pop up as "Android Device" or similar, without a specific driver.
Right click on it and perform these actions: update drivers, search on this computer, choose driver from already installed drivers, show all devices, next, install from disk, there point to the .inf file corresponding to your system (32bit -> x86, 64bit -> x64) found in \YotaLTE\Modified HTCDiagDriver\Win x64HtcUsbMdmV64.inf (for 64bit).
After installation, go to properties of this new driver HTC USB Modem and check the number of the port displayed there, COM3 or COM4, for example.
Lower the 38400 value which you find there, click OK.
Execute as an admin C:\Program Files (x86)\Qualcomm\QPST\bin\QPSTConfig.exe.
Choose the second section Ports, then "Add new port".
In the field Port put the one which was displayed in the modem section, COM3 for example.
In Port Label field write "Yota" or whatever, and then OK.
In the first section Active Phones the smartphone should be displayed.
KEEP QPSTConfig.exe PROGRAM OPENED.
Also, start C:\Program Files (x86)\Qualcomm\QXDM\Bin\QXDM.exe using admin privileges
Here, click Option, then Communications.
In the Target Port choose the same port as before, then OK.
Click View, New, Common, NV Browser. In the Category Filter choose LTE.
Choose 06828 LTE BC Config and then press "read".
Correct the number you see, for example 1099511627781 in 1099512152069 for B20 and click Write to save.
Close all the programs, and reboot the phone directly into TWRP (VOL UP + POWER), here find the update_S01_003_4240_RU1_M05_patched.zip baseband and flash it.
At this point it is advised to clean dalvik cache and cache with TWRP.
Done! Reboot.
If it is not working, reset everything by flashing stock baseband, putting back the values changed above and start again. It is not necessary to flash the modified RU-CN baseband, if with the CN one the phone is performing at 100%. I suggest to flash to see the differences. By the way, remember to unlock one band at a time.
To unlock B38 band (there is lack of information about YD206 already having it or not) the number is 1236951105541. For example, if the initial number found in LTE config was: 1236950581253, it means that the bands LTE B1/B3/B38/B41 were active. To verify by yourself download LTE Band Calculator.
Some attempts have been made also to unlock B7 band, but without success for now. It seems that the baseband crashes after a second when triying to connect to that LTE band. Further research needed!
After all the hassle I just went through to obtain a YD201 instead of a YD206 so I could have Band 20
Great news for YD206 owners anyway, thanks for sharing!
hippy dave said:
After all the hassle I just went through to obtain a YD201 instead of a YD206 so I could have Band 20
Great news for YD206 owners anyway, thanks for sharing!
Click to expand...
Click to collapse
Me too.
Tried drivers installation with a yd201 (just for take a look about the wifi issue) and they are not compatible.
I guess modifying the inf files would do the trick.
Hi, I try to unlock LTE band, but su command doesn't work in terminal .... it said su: not found.
velociraptor68 said:
Hi, I try to unlock LTE band, but su command doesn't work in terminal .... it said su: not found.
Click to expand...
Click to collapse
Do you have root? Do you give root permission to Terminal Emulator?
Just did the procedure, can't confirm if it's working on 800MHz B20 yet because I can't find a way to force it or even know if its available in my region from my Network, because I live in the city and they use mostly the 1800MHz, 2G Only works correctly and it seems that somehow it also solves the Proximity Sensor, I will give feedback at how it behaves tomorrow when I will be on the move, but until now everything seems well and smooth, Many Thanks for the persons that worked on the fix, I guess Yota should be hiring! And to @TheArt who translates all the good stuff!
band17
Hello,
Would it work to unlock band 17 At&t? Is that enough modify config 6828 number by calculator?
Hello,
I am from Bosnia and got Yotaphone 2 from China (YD206) and installed latest RU software 1.132, but I noticed that my phone only works in big cities. As soon as I leave for the countryside, there is no signal/service.
Is there another version of software I can try to upgrade to, to get these bands in the countryside as well, or the problem is with the limitation of phone's hardware?
Thanks!
Miroslav1999 said:
Hello,
I am from Bosnia and got Yotaphone 2 from China (YD206) and installed latest RU software 1.132, but I noticed that my phone only works in big cities. As soon as I leave for the countryside, there is no signal/service.
Is there another version of software I can try to upgrade to, to get these bands in the countryside as well, or the problem is with the limitation of phone's hardware?
Thanks!
Click to expand...
Click to collapse
Whats the coverage in your contry?
Maybe outside big cities there are not mobile connection in the frequency that yotaphone can support
borekon said:
Whats the coverage in your contry?
Maybe outside big cities there are not mobile connection in the frequency that yotaphone can support
Click to expand...
Click to collapse
GSM : 900 (E-GSM) 1800 (DCS)
UMTS: B1(2100) UMTS B8 (900 GSM)
That is what I found out from google. I am not sure what is the better way to find out what Yota covers and what is available here.
If someone knows please let me know.
If I perhaps flash the phone with EU software rather than RU which I currently have, would that unlock some bands?
if you have a problematic firmware that won't allow you to edit your APN settings in the dialer hidden menu, this may be what you need.
first, the warnings:
1. THIS IS ONLY FOR SPRINT SAMSUNG PHONES RUNNING TOUCHWIZ ROMS!!! never attempt on any other carrier or manufacturer's device or alternate roms! it should most likely work on other Samsung Sprint devices with stock/touchwiz roms.
2. DEPENDING ON DEVICE, YOU ARE MOST LIKELY TO BE FORCED TO FACTORY RESET YOUR DEVICE IN THE PROCESS, which likely includes LOSS OF ALL DATA ON INTERNAL SD!! take all necessary precautions.
3. ROOT REQUIRED
4. you will STILL NEED your MSL number!!!
5. have a FULL backup in TWRP ready in case anything goes wrong. INCLUDE your EFS in the backup!!! again, INCLUDE YOUR EFS. make sure it's stored on EXTERNAL sd card. again, EXTERNAL SD CARD!!! or copy it to your PC if you don't have an external card.
here's the short but sweet guide.
1. download "Samsung Phone Info" from Google Play
2. swipe over to the CSC section.
here you should see:
Firmware's CSC Code
Active CSC Code
Available CSC Code
3. if Firmware's AND Active both say XAS, you should already be able to edit your APNs using your MSL number.
if Firmware and Active codes do not match, you have a dirty rom and I am unable to help you correct it, you'd best try a different stock based rom or 3rd party that allows it by default.
if Available CSC Codes does NOT include "XAS" then whoever modified the customized stock touchwiz rom you're using removed it and you'd best try a different stock based rom or 3rd party that allows it by default.
4. using any CSC editor, change "SPR" in ALL places it appears as only the 3 letters "SPR" to XAS
5. confirm changes and reboot. you will now most likely lose ALL personal data on your phone and should now be able to edit your APN using your MSL inside the dialer's hidden menu.
Sterist said:
if you have a problematic firmware that won't allow you to edit your APN settings in the dialer hidden menu, this may be what you need.
first, the warnings:
1. THIS IS ONLY FOR SPRINT SAMSUNG PHONES RUNNING TOUCHWIZ ROMS!!! never attempt on any other carrier or manufacturer's device or alternate roms! it should most likely work on other Samsung Sprint devices with stock/touchwiz roms.
2. DEPENDING ON DEVICE, YOU ARE MOST LIKELY TO BE FORCED TO FACTORY RESET YOUR DEVICE IN THE PROCESS, which likely includes LOSS OF ALL DATA ON INTERNAL SD!! take all necessary precautions.
3. ROOT REQUIRED
4. you will STILL NEED your MSL number!!!
5. have a FULL backup in TWRP ready in case anything goes wrong. INCLUDE your EFS in the backup!!! again, INCLUDE YOUR EFS. make sure it's stored on EXTERNAL sd card. again, EXTERNAL SD CARD!!! or copy it to your PC if you don't have an external card.
here's the short but sweet guide.
1. download "Samsung Phone Info" from Google Play
2. swipe over to the CSC section.
here you should see:
Firmware's CSC Code
Active CSC Code
Available CSC Code
3. if Firmware's AND Active both say XAS, you should already be able to edit your APNs using your MSL number.
if Firmware and Active codes do not match, you have a dirty rom and I am unable to help you correct it, you'd best try a different stock based rom or 3rd party that allows it by default.
if Available CSC Codes does NOT include "XAS" then whoever modified the customized stock touchwiz rom you're using removed it and you'd best try a different stock based rom or 3rd party that allows it by default.
4. using any CSC editor, change "SPR" in ALL places it appears as only the 3 letters "SPR" to XAS
5. confirm changes and reboot. you will now most likely lose ALL personal data on your phone and should now be able to edit your APN using your MSL inside the dialer's hidden menu.
Click to expand...
Click to collapse
Have you found a way to retrieve your MSL without calling sprint? I've tried all the tool apps in the play store and using a logcat within the ##3282# menu with no luck. Getprop ril.MSL yields nothing, not even a not found error.
I've tried calling sprint for my MSL but refuse to release it.. I'm not exactly on their "nice" list - they've even called to tell me I'm "using too much of my [UNLIMITED] data" many times so I don't expect much from them anymore..
Any help or direction would be greatly appreciated
try the Sprint chat -- through the website, NOT Facebook, and have a good reason ready as to why you need the MSL, other than for bypassing their security lol
Holy **** after searching high and low I have FINALLy found a way to get back editing my APNS for hotspot on my rooted Sprint Note 5! AND I keep Android Pay! Thanks so much!!
This works perfectly! Only thing is turn on hotspot option disappeared from settings. I can turn it on and off from the top bar if I swipe down. OR I can download a hotspot shortcut app and access it from that app.
Also I noticed my icons for LTE now say 4G and the bars are different too - more old school.
I noticed I changed EVERY SPR to XAS - do ALL of them NEED to be changed to enable APN editing? Can I switch back the ones that give me back hotspot option in settings and stock LTE & bars icons?
Sterist said:
if you have a problematic firmware that won't allow you to edit your APN settings in the dialer hidden menu, this may be what you need.
first, the warnings:
1. THIS IS ONLY FOR SPRINT SAMSUNG PHONES RUNNING TOUCHWIZ ROMS!!! never attempt on any other carrier or manufacturer's device or alternate roms! it should most likely work on other Samsung Sprint devices with stock/touchwiz roms.
2. DEPENDING ON DEVICE, YOU ARE MOST LIKELY TO BE FORCED TO FACTORY RESET YOUR DEVICE IN THE PROCESS, which likely includes LOSS OF ALL DATA ON INTERNAL SD!! take all necessary precautions.
3. ROOT REQUIRED
4. you will STILL NEED your MSL number!!!
5. have a FULL backup in TWRP ready in case anything goes wrong. INCLUDE your EFS in the backup!!! again, INCLUDE YOUR EFS. make sure it's stored on EXTERNAL sd card. again, EXTERNAL SD CARD!!! or copy it to your PC if you don't have an external card.
here's the short but sweet guide.
1. download "Samsung Phone Info" from Google Play
2. swipe over to the CSC section.
here you should see:
Firmware's CSC Code
Active CSC Code
Available CSC Code
3. if Firmware's AND Active both say XAS, you should already be able to edit your APNs using your MSL number.
if Firmware and Active codes do not match, you have a dirty rom and I am unable to help you correct it, you'd best try a different stock based rom or 3rd party that allows it by default.
if Available CSC Codes does NOT include "XAS" then whoever modified the customized stock touchwiz rom you're using removed it and you'd best try a different stock based rom or 3rd party that allows it by default.
4. using any CSC editor, change "SPR" in ALL places it appears as only the 3 letters "SPR" to XAS
5. confirm changes and reboot. you will now most likely lose ALL personal data on your phone and should now be able to edit your APN using your MSL inside the dialer's hidden menu.
Click to expand...
Click to collapse
elcidroyale said:
Holy **** after searching high and low I have FINALLy found a way to get back editing my APNS for hotspot on my rooted Sprint Note 5! AND I keep Android Pay! Thanks so much!!
This works perfectly! Only thing is turn on hotspot option disappeared from settings. I can turn it on and off from the top bar if I swipe down. OR I can download a hotspot shortcut app and access it from that app.
Also I noticed my icons for LTE now say 4G and the bars are different too - more old school.
I noticed I changed EVERY SPR to XAS - do ALL of them NEED to be changed to enable APN editing? Can I switch back the ones that give me back hotspot option in settings and stock LTE & bars icons?
Click to expand...
Click to collapse
this **might** be fixed by renaming (or deleting, if you're brave) the features.xml file, if I remember correctly, stored in system/csc/ or system/etc/ not sure honestly
features.xml.backup should do just fine.
if the rom doesn't boot afterwards or if the dragons catch all your apps on fire, go back to recovery and use TWRP's file manager to change it back
also, any xposed app (like wanam's) or other feature.xml adjusting apps (like GalaxyTools or Samsung Phone Info) can cause the problem to happen again.
the alternative / temporary / dirty-fix would be to create a shortcut to hotspot on your home screen:
1. download Activity Launcher from Google Play
2. launch and change recent activities to all activities
3. wait approximately 72 years for it to load
4. scroll to Settings and tap it
5. scroll to Hotspot and long-press it
6. tap create shortcut
7. never uninstall Activity Launcher -- instead just make it a hidden app (it's very small anyways)
I can just longpress hotspot toggle in slide down drawer from top no probz. Which CSC settings modifies the ability to edit APN? I want to put the rest back to SPR.
Sent from my SM-N920P using Tapatalk
I used the msl code and everything appears the way you say it should... but the phone STILL says invalid sim!
What internal file must be deleted, the thing is unlocked on sprints end it just wont let go !
Phyzic said:
Have you found a way to retrieve your MSL without calling sprint? I've tried all the tool apps in the play store and using a logcat within the ##3282# menu with no luck. Getprop ril.MSL yields nothing, not even a not found error.
I've tried calling sprint for my MSL but refuse to release it.. I'm not exactly on their "nice" list - they've even called to tell me I'm "using too much of my [UNLIMITED] data" many times so I don't expect much from them anymore..
Any help or direction would be greatly appreciated
Click to expand...
Click to collapse
see this thread.. https://forum.xda-developers.com/sprint-galaxy-s5/general/guide-how-to-msl-code-t3628728 ....theres the rooted way...and i also posted the non rooted way....
Hello,
I rooted Sprint Note 5 from Nougat to Magisk and went ahead to replace SPR into XAS in all files under system/CSC folder. APN Type is still coming greyed out. Any help will be appreciated.
-Sunny
Hi.
May i ask if someone can provide a WORKING solution to modify without rooting via methods like sideload, usb debugging and adb a working method to replace the existing
CSC Files to have some important features back without triggerung any samsung modify checkings when the rest of the system still untouched.
To prevent here huge manual shell typings, is there still a working "gui" based "commander" which can speed up such operations, which is still working with Android 10 ?
The existing Solutions are mostly from 2013-2016 and Android 5-7.
It looks like it needs much more time for a working twrp solution or updated magisk method comes out, so i don´t talk about a root solution, just a solution to easyly debloat a little bit and make nessassary
changes on my actualy running CSC settings.
Further more i have the question is there any working "hidden" dial-code for using the IMS settings system app without having root. The IMS-Settings App is another great solution to fix local problems
with VoWifi and VoLTE without the need of modify CSC files. Whatever works. Or can i start the IMS Settings via a adb command to just make one time manual nessassary changes ?
Such things are nessassary when you use Dual SIM from different countrys and you use just one CSC set from the primary country. This results in not correct setted VoLTE/VoWifi Settings for the 2nd Card, to have it basicly working in Roaming when the priority and Data-Mode is changed to the 2nd slot. In the past i overcome this issues by creating a custom CSC for the ENTIRE DACH-Region where i include any Provider from any country without the need to change the CSC code later.
Actualy the A51 is heavyly bloat-overloaded and many of the samsung bloat it is not possible to "deactivate" completly with the usual on board features. like Bixbly completly....