Database Users

secret code Zte blade (san francisco)

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

How modify a qcn file to enable AWS band

Hi.
I come from another post looking for a solution to my dilemma (http://forum.xda-developers.com/galaxy-s5/help/switch-stock-rom-t2866861#post55236673), thanks to fffft member found that I can open the band 4 of my cell S5 using the QPST program, however I can not find a modified .qcn file that corresponds to my model (G900F).
What I have done is make a backup of my original .qcn (which understand not share because there goes my IMEI) and I need advice from someone who knows that is the parameter that should change to open the AWS band 4.
Much appreciate your help.

I see that nobody has answered, if it was not for lack of cooperation, or because no one has had this problem.
Continue researching and achieve get qcn file G900M, which is super, but not left so installed as well, the QPST program generates an error and does not let install, so proceeded to compare them to see how different they are, and actually they are very different in their hexadecimal setting.
The issue now is, I need someone to tell me what are the parameter I have to modify my original qcn (my G900F) to enable AWS band 4.
Thank you for your help.

..

Hello again fffft.
I will try to explain everything in the best way. I can not send the file qcn G900M, because I have understood that within the IMEI can be identified, and the first thing I asked the person I give it to me was that change could not deliver it to anyone.
Now step by step to do was the following (taken from this forum http://forum.xda-developers.com/showthread.php?t=2291589 ):
Install phoneutil.apk in my phone.
Install QPST 2.7 build 323.
Choose the usb connection “RNDIS + DM + MODEM” from the menu that comes by typing *#0808#.
On the Ports tab of the program QSPT set the COM port corresponding to the cell (seeing that port recognizes the cell through Device Manager).
Choose “Start Clients” and choose “SOFTWARE DOWNLOAD”.
Hit the “Restore” tab, set port to COM number, choose the QCN file, and start.
Attached two images, one in which it is seen that the process is running smoothly, and a second in which shows the error.
With regard to your question about the RMNET protocol, for I must say I have no idea regards, because as I said I am still a newbie.
Finally and with respect to qcn file G900T me would be very very difficult to get the file G900M was relatively easy (not as easy lol) but because here in my country is the model that is sold, but the model does not get G900T no way.
I remain attentive to your suggestions, and thanks again for the help.

..

I thought S5 supports AWS band as well as other bands? I bought S5 from Rogers and use it with Wind mobile (Canada).

..

Hi.
Well, with my answer are attached to the two qcn files, not if it's okay to post them because I do not know which is the information that I'm giving, but I'll trust you fffft.
Review the entries with IMEI and clear, making this process and I thought this would be a very good explanation of why not to overwrite the original file leaves the cell, because the second IMEI not for the phone, but even if this were true, no understand how in the above forum they spread a qcn file for S4 that everyone could use.
Anyway, I hope that with this we can advance the issue to see if I can get out of this mess.
Thanks again.

..

Ok fffft, I found the parameter you say, but now my question is, as I edit the file qcn? I need some special program?

Loperaco said:
Ok fffft, I found the parameter you say, but now my question is, as I edit the file qcn? I need some special program?
Click to expand...
Click to collapse
Well, download the program XVI32 to edit the hexadecimal, apparently was successful but eventually the program generated the same mistake I had already seen, indicating "Could not reset the phone. COmmunication Errors Occurred".
Will you help me?

..

Hi there.
I have an interesting fact to share, because I could not properly complete the process to overwrite the qcn file then started to review the QPST program and its functions, among these I found the display content on qcn files through this for any entries who had been unable to write and determine that it was possible to write the file so qcn "hot" (ie directly on the phone) Oh and surprise! when I saw that the code / parameter that indicated fffft if I had changed even though the restore process had not been successful.
Anyway achieved modify the parameter in question and probe the cell after this, but still not achieve even connect AWS band 4, so despite the success the result was a failure.
Knowing this now accept suggestions from all of you experts.

..

Got a little further, but the bands did not get enabled...
fffft said:
Docx? Shouldn't those be .qcn files?
Anyway, you should try encouraging someone to post a NV dump from their 900T for comparison. You can check the existing AWS threads to confirm, but as I recall to enable AWS on earlier Galaxy models, required editing NV_RF_BC_CONFIG_l from 80 03 e8 04 to 80 03 e8 06
So ostensibly you will want to make the same change on your 900F. Comparing your NV to a 900T would lend confidence to that presumption.
.
Click to expand...
Click to collapse
fffft, Laperaco,
I am pursuing the same Band change as described here and have an update of the things that I was able to discover:
1) I was able to use QPST and pull NV backup from my phone - see my JJ_ATT_S5_Bands_Tester_No_IMEI (IMEI removed in Line 550)
**Note that I was not able to restore any QCN back to my phone in either USB mode (and I think this is what Loperaco was talking about), but...
2) I was able to program my phone directly using RF NV Item Manager, but did not get desired results (see below):
- a) I changed 1877 NV_RF_BC_CONFIG_l from 80 03 e8 04 to 80 03 e8 06 and nothing changed - i.e. radio still worked and I was still getting EDGE (no HSPA+)
- b) I tried changing the next line 1878 NV_RF_HW_CONFIG_I from f6 to 2c, because I saw that in another QCN file I found online. That actually "killed" my radio altogether, at least until I changed it back to f6
- c) Upon further inspection of the SM-N900T file I found online (too big to upload here), I saw that there are quite a few differences, which leads me to believe that additional configurations must be made to take advantage of the HSPA+ bands.
!! Please !! If someone with T-Mobile SGS5 looking at this, could you pull your QCN, mask IMEI if you'd like and post it here for comparison.
Otherwise, fffft, do you have any other thoughts regarding the changes needed...?
Last note that files are posted as .qcn.txt, becuase forum does not allow posting of qcn file extensions. Just remove .txt and you will have original qcn.
Thanks,
JJ

fffft said:
Your reluctance to document what you have done in detail is unfortunate because it prevents us from confirming that you did as you summarized or possibly discern any errors along the way. Nor did you tell us how you concluded that the phone did not connect to AWS, whether the changes were persistent after a reboot or what the service mode showed for activity after using the diagnostic menu to lock the handset to AWS, et cetera.
Of particular value would be a before and after NV dump from your phone, alongside a 900T NV dump. Which would illustrate both the required changes and any progress made with the attempted write.
To reply to your question, two obvious possibilities are apparent
1. That you changed the parameter as you summarized and that was insufficient to effect the desired change. Which would mean that the required parameter is different for the S5 than preceding Galaxy models for some reason e.g. that a different parameter needs editing or that radio changes are needed as well, even though that was not the case for the S3 & S4.
2. That you made some inadvertent error in your procedure that you didn't discern. No one can look for possible errors in the absence of you providing a detailed, step by step description of what you did though.
.
Click to expand...
Click to collapse
Ok ok, let me see how I can solve this.
First of all is not reluctance, I tried to be clear in how I do things, but I'll try again:
1. I bought a model of cell G900F that has disabled the AWS band 4.
2. I tried using the QPST program to replace the qcn file with one that corresponded to a G900M model, since in this model if the band 4 is enabled, but the process to make it in the program generated the error "Could not reset the phone. Communication Errors Occurred ".
3. I do not know how or if the QPST program writes an error log, so I do not know where to look it can be sent. I explain how to install and run the program each button is a bit wasteful, but I followed the steps in this forum http://forum.xda-developers.com/showthread.php?t=2291589
4. After this, and having received suggestions from fffft, I tried modifying the original qcn file from my phone, because I thought that perhaps the problem was because they were different models and finally the phone would not allow me to put a qcn file of another model. The modifications I did was change the parameter NV_RF_BC_CONFIG_l from 80 03 e8 04 to 80 03 e8 06. This is done by the program XVI32 modifying the hexadecimal.
5. I tried again using the option to restore the qcn file in QPST program, but got the same error "Could not reset the phone. Communication Errors Occurred".
6. I assumed I had to think of something else so it was when using the RF NV Manager (included in the installation program QSPT) for locate the actual file contents qcn on my phone, and I realized that despite the error obtained in restoring the file using the QPST program the parameter indicated in paragraph 4 of this list if it had changed.
7. I proceeded to check the signal and actually still had no access to the 4G network, the most that is connected to the HSDPA + network.
8. I read the comments from fffft and now I'm writing this.
I hope I was clear in my problem and have made a good step by step.
Now the issue is that:
A. I do not know how to access the diagnostic menu that enables or disables the AWS band, so I do not understand fffft what you're talking about.
B. I agree that modify only the parameter in question is not sufficient, otherwise the matter would be solved.
C. It is possible that I made ​​a mistake as you point out, I finally am new to this, but still I explained my process so I am attentive to suggestions.
Thanks for the help.

JJ_Boja said:
fffft, Laperaco,
I am pursuing the same Band change as described here and have an update of the things that I was able to discover:
1) I was able to use QPST and pull NV backup from my phone - see my JJ_ATT_S5_Bands_Tester_No_IMEI (IMEI removed in Line 550)
**Note that I was not able to restore any QCN back to my phone in either USB mode (and I think this is what Loperaco was talking about), but...
2) I was able to program my phone directly using RF NV Item Manager, but did not get desired results (see below):
- a) I changed 1877 NV_RF_BC_CONFIG_l from 80 03 e8 04 to 80 03 e8 06 and nothing changed - i.e. radio still worked and I was still getting EDGE (no HSPA+)
- b) I tried changing the next line 1878 NV_RF_HW_CONFIG_I from f6 to 2c, because I saw that in another QCN file I found online. That actually "killed" my radio altogether, at least until I changed it back to f6
- c) Upon further inspection of the SM-N900T file I found online (too big to upload here), I saw that there are quite a few differences, which leads me to believe that additional configurations must be made to take advantage of the HSPA+ bands.
!! Please !! If someone with T-Mobile SGS5 looking at this, could you pull your QCN, mask IMEI if you'd like and post it here for comparison.
Otherwise, fffft, do you have any other thoughts regarding the changes needed...?
Last note that files are posted as .qcn.txt, becuase forum does not allow posting of qcn file extensions. Just remove .txt and you will have original qcn.
Thanks,
JJ
Click to expand...
Click to collapse
Hi JJ.
We are indeed talking about the same issue, however I see a difference and that is that despite not having the band 4 AWS enabled on your phone, this only gives you the edge band, however my phone without enabling the band 4 gives me HSDPA+, so my question, just out of curiosity, is what is the frequency at which your operator transmits the EDGE network?

Loperaco said:
5. I tried again using the option to restore the qcn file in QPST program, but got the same error "Could not reset the phone. Communication Errors Occurred".
6. I assumed I had to think of something else so it was when using the RF NV Manager (included in the installation program QSPT) for locate the actual file contents qcn on my phone, and I realized that despite the error obtained in restoring the file using the QPST program the parameter indicated in paragraph 4 of this list if it had changed.
Click to expand...
Click to collapse
Laperaco,
1) I was also unable to load qcn file from backup even without modifications, so...
2) I made modifications directly to the phone using RF NV Item Manager*
*Note from my post that changing line 1877 made no difference in connectivity for me.
3) This specific connection is below (although it naturally fluctuates):
Network Type: EDGE:2
GSM RSSI: -89db (63%) 12 asu
GSM Signal Strength: 13db (42%)
Preferred Network Type is LTE/GSM autio (PRL)*
*Non-GSM selections (WCDMA, LTE-only, etc) simply do not connect, so no HSPA+ for me
JJ

JJ_Boja said:
Laperaco,
1) I was also unable to load qcn file from backup even without modifications, so...
2) I made modifications directly to the phone using RF NV Item Manager*
*Note from my post that changing line 1877 made no difference in connectivity for me.
3) This specific connection is below (although it naturally fluctuates):
Network Type: EDGE:2
GSM RSSI: -89db (63%) 12 asu
GSM Signal Strength: 13db (42%)
Preferred Network Type is LTE/GSM autio (PRL)*
*Non-GSM selections (WCDMA, LTE-only, etc) simply do not connect, so no HSPA+ for me
JJ
Click to expand...
Click to collapse
Ok JJ, we are going through the same steps, we must wait for more help, I'll keep researching but I see that not many people have our problem.
I have a question is that with that code or through option that could see data that you send me.
Any information or change that has put it in the post.

..

V3.90 Debloater(Lets remove all that carrier bloat !! Root not required..)

Debloater by Gatesjunior
Disclaimer:
I nor XDA are responsible for anything that you choose to do with this program to your device or others. Modifying my code or redistributing it is not allowed without prior approval from me. Yes, that includes Kanging it, I will be able to tell. Neither is trying to use any of my code to create an apk file with my code logic allowed without prior approval from me.
Donations:
"If this application helps you out, please consider a small monetary donation to further improve development of this application. You can Donate by clicking the "Donate to Me" button on your left, underneath my Profile picture.
Background:
So after many times of going back and forth blocking / disabling apps on my devices through the command line and or shell, I decided to write a program to make this all much easier for myself. Well, after I got it all finally running and doing what I wanted, for each particular device I own, I decided that his was a pretty nice program and I wanted to share it with the community. After all, this community is where I started and learned a lot of the things I know today. So why not share with my family of Android enthusiasts.
Requirements:
The program requires that your manufacturer USB drivers are installed for your specific device as well as the following:
• Windows Operating System
• USB Debugging turned on for your device
• Root or KitKat and above running on your device
Some people have had trouble getting their PC to see their device, even with the device manufacturer drivers installed. Watch your device when you plug it in and authorize your computer to access it, the device should display a popup something for you to grant access to the PC. If it does not, go into Settings, Developer Options and look for an option that says something about Revoke USB debugging authorizations and tap it. Click ok. Now, unplug your device and plug it in while watching your device and click on the option to always allow this computer and then grant when the popup window displays.
What does it do?:
• Block / Disable applications on your device
• UnBlock / Enable applications on your device
• Allow UnBlock / Enable all applications at once on your device
• Allows filtering of the displayed packages for quicker decision making
• Allows exporting your blocked / unblocked listing to a file (Right click on Read Device Packages after list is loaded)
• Allows importing your blocked, or someone else's, listing (Right click on Read Device Packages after list is loaded)
• Allows complete removal of application(s) if you have root (It will backup the original folder structure and apk for you, just in case you need to restore the application(s) back to your device.
So, essentially what it does is this. It will disable / block any system and third party application on your device with ease and allow you to enable / unblock the application just as easy. It also reads everything, real-time, directly from your device, so that there are no messy batch files, scripts and txt files, etc. that you have to maintain and keep track of for every device you own. I mean let’s be honest, most of us own more than one device. Phones, tablets, etc. Who wants to maintain all those scripts and files for every device? The other nice thing that this program does is allow you to, at a granular level, control what is blocked/disabled and what is not. There are quite a few scripts and things like this available in the community that give everyone a start on what to disable/block, but who wants to scour through these scripts and decide what they want or don’t want with something someone else put together. The other nice feature of the program is it will display information for you about your device. Such as Model number, Serial number and battery status. As well as whether or not your device is rooted or not.
What audience of device does it support?:
This program supports many devices. It will support any device running KitKat or above, whether rooted or not. That’s right, if your running KitKat or above, your device does not need to be rooted. If you’re running anything other than KitKat or above, your device does need to be rooted. As long as these requirements are met the program will run. The program will also auto-detect whether or not your device is supported. So if you are not sure, plug it in and let the program tell you. If your device is not supported, it will put up a message saying as much and close the program.
Program Functionality:
The first thing you need to make sure of is that USB debugging is turned on for your device. The video at the end of this OP is a must to watch. It will describe this process as well as allowing adb shell permissions.
So when you first connect your device you will need to wait for the program to detect your device and whether or not it is supported. Once this is established, usually within a couple of seconds, it will display a warning message to you reminding you to be careful with what you disable and block. Yes, it will allow you, if your device is supported, to disable/block even system dependent applications. This message will also include, if your device does not support block mode, a message indicating that block mode is not supported and that it will disable the applications. Here is a sample screenshot of this.
{
"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"
}
Once the program has initialized, and the warning message has been presented, it will put you into the main program screen itself which will look like the following.
From here the first thing you need to do is click the Read Device Packages button on the upper left. This will initiate the process to start reading all of the applications on your device and then list them in a list in the window. It will also indicate to you what it detects as applications that are already disabled/blocked on your device by putting a checkmark in the box next to the application. It will look similar to this.
As you can see it will tell you in the upper right how many applications it detects as blocked and not blocked. You will notice that on the bottom left it has an indicator that is labeled Synced. As you make changes to the device application listing this will turn red. In other words, it will indicate whether you have made changes to the device application listing since the last sync. Also, in the upper right there is a counter labeled Changed. This indicates the number of changes you have made to the device application listing since last sync.
Once you have made any changes to the device application listing an Apply button will show up in the upper left replacing the existing Read Device Packages button, it will look like the following.
Once you click the Apply button the existing changes you made to the device application listing will be applied to your device. Keep in mind that you can disable/block and enable/unblock applications all at the same timeand then apply those changes to your device. After you have applied the changes to your device a message will be displayed stating the status of your changes as seen below.
Once the changes are applied to your device you now just click the Read Device Packages button again to reload the information from your device and you will now notice that the application(s) you just made changes to will indicate as much in the refreshed listing. As seen below.
You will notice that the particular application I asked it to disable/block has now a check mark next to it indicating that the device itself has disabled/blocked this application.
So now on to filtering. Lets say you want to limit the listing to specific items you are searching for within the package name. Like packages that contain "vzw" for Verizon. You will see below by clicking the filter checkbox and then typing in what I want to filter on, it will limit the list to your specific filter criteria immediately.
And here is the results of our filter below.
From here I can make changes to the listing, by checking the box next to the packages or I can simply uncheck the filter checkbox and return back to the full listing unfiltered.
O.k., so far so good. Now let’s say that you want to enable/unblock all the applications on your device. Maybe you’re selling it or maybe you have an issue with it and you want your carrier to take a look at it. By clicking the Unblock All Packages button and then click Apply this will enable/unblock all applications on your device. As if it is back to factory with no changes made.
Remove mode turned on. For all you root users, this will completely remove the application(s) in the exact same manner and will keep a backup for you in the install folder under Backup of the original apk files. They will also be kept in the original file structure they came from on the device so that it will make it easy for you if you have to push one back to your device. Here is an example of the remove mode turned on and the warning you will receive when it is active for the device that is rooted.
Also, after you have removed the application(s) you want, if you Reload Device Packages again, you will notice them in the list and checked. This is in fact accurate, it sees them as removed / uninstalled. To not have them show up in the list any longer, just reboot your phone and run the program again and you will see that they no longer show up in the listing.
Sharing your blocked list or re-import it to your device:
So there are times when you get a replacement device and do not want to have to go through all the pain remembering what you had blocked. Well to the rescue comes the export/import functionality of the application. This will allow you to export and import your blocked list. You also might want to share it with someone. So this is how it works:
Once you launched the program and have clicked the Read Device Packages and your list is up, you can right click on the Read Device Packages button and export the blocked packages to a file and share it. Then the person receiving it just does the same process, but when they right click on the Read Device Packages, they just choose import blocked packages and then click the Apply button. Done.. You of course can do this yourself to your device. This can come in very handy if you have to Wipe Data, because you blocked something you should not have and your device is experiencing issues.
Well community people that is it. I hope you enjoy the program as much as I do and look forward to your feedback. Gatesjunior signing out…
Full Install:
Download link: https://1drv.ms/u/s!AjfH26Z4pHaFk1V8rA5Zj_p5vtkx
Upgrade Install: (Just replace debloater.exe in your "Crogram Files (x86)DebloaterDebloater" folder)
Download link: http://rootjunkysdl.com/?device=Gates&folder=DeBloater
OSX Version (dmg file): Thank @eyekyu for the port over with Wineskin..
Download link: http://rootjunkysdl.com/?device=Gates&folder=DeBloater
Mirror: https://onedrive.live.com/redir?resid=8576a478a6dbc737!831
Video by our own RootJunky:
Credits:
RootJunky - For finding the original KitKat weakness
Misterxtc - For all of his hard work already on helping people with a script process for this purpose
Er. Aditya - For testing with me and going back and forth with builds to finally resolve the no packages issue
XDA:DevDB Information
Debloater, Tool/Utility for the Android General
Contributors
gatesjunior
Version Information
Status: Stable
Current Stable Version: 3.85
Stable Release Date: 2015-02-07
Created 2015-02-07
Last Updated 2018-01-12

Change Log:
01/09/2015: Initial Release
01/10/2015: Updated the handling of application filtering determining what is disabled / blocked
01/11/2015: Updated application (v2.1) to hopefully help address the local Administrator issues
01/12/2015: Major update v2.8 (Fixes all the users not being able to see packages - Xposed Framework fix)
1/13/2015: (v2.9) Fixed an issue with an Out of Bounds Exception in certain cases.
1/15/2015: (v2.10) Complete rewrite of the filter engine, all interactive and immediate now. Also some cleanup.
1/16/2015: (v3.0) Root mode added with ability to completely remove application(s), with backup feature.
1/17/2015: (V3.1) Added new intro screen as well as import blocked list functionality.
1/18/2015: (V3.2) Added some hover helper text. If you hover over a major item it will display helper text.
1/19/2015: (V3.3) Fixed some more Xposed framework issues that would impact rooted users and removing packages as well as fixed some import logic to make it more reliable and optimized.
1/23/2015: (V3.4) Major update and bug fixes as follows:
•Interactive search now also supports searching through the package name(s) as well as the apk file(s)
•Bugs related to duplicate entries showing up when you Read Device Packages multiple times with filter on and off are fixed. This could have caused issues with some users saying it will not remove something.
•Blocking mode fully supported on 4.4.x, found a major bug that was preventing this with rooted devices
•APK file backups now include Odex files if they exist with the APK
•Remove option now completely removes both apk and odex, so yes, previous builds would have left the odex files behind. They will not hurt anything, but take up space. I will release a quick fix for the cleanup of those soon, if you cannot do it yourself.
•Buttons appearing where they should not at times with filter is fixed
•If you have disabled something on the phone itself or in a script, and are rooted, the program will not care any longer and will unblock them anyway.
(1/31/2015: (V3.5) Major logic update. I think I finally put a nail in the coffin with the Xposed Framework issues and removing applications. Also added the functionality where once you import a blocked list all the items will turn red for the changes it has made.
(2/6/2015): V3.6 Quite a few additional options. Including the following:
Ability to only show blocked packages, unblocked packages and all packages. (Just right click on either Read Device Packages button or Apply button after initial package listing is displayed.)
Ability to right click now on not only the Read Device Packages button, but also the Apply button.
Ability to import unblocked listing (Yes, changes will be made red to identify what would be unblocked before Applying)
Ability to sort by either APK Filename or Package Name and be able to sort in either Ascending order or Descending order in each area.
Complete removal of all associated data and folders that pertains to a package if the Remove option is selected (Root Mode only)
(2/7/2015): V3.7 Added a checkbox identifier on Display mode to let users know which Display Mode they are in currently.
------ (Fix was placed into this build later that fixes the UnBlock All Packages button bug..)
(3/28/2015): V3.8 Added Lollipop support for rooted / non-rooted users. It will now support hiding the packages, if you are rooted it will disable them instead. Also, you will notice if you right click on the Read Device Packages after it loads there is also a Backup / Restore menu option. Do not use those yet, I am still working on them.
(4/4/2015): V3.85 Fixed issue with base.apk flags being read incorrectly from device. Logic issue.
(4/12/2015): Updated a logic issue in the detection of the device and it's abilities. Same release number, v3.85
(5/24/2015): Fixed an issue during import of a blocked list that would flag all "base.apk" files..
(1/7/2018): Added newer Android Debug Bridge Files..

Hold
For me..

Looking Good video coming soon

I can't wait to give this a run.

Well be getting a note edge soon for testing, and looking forward to giving this a shot.

OP updated now with Video..

Great application but not working on my Droid Razr M (XT907) with latest OTA firmware on it.
Pressing "Read Device Packages" and nothing comes up.

Just tried it on my AT&T Note 4. It seemed to work, great job and thanks for building this app.

0rtli said:
Great application but not working on my Droid Razr M (XT907) with latest OTA firmware on it.
Pressing "Read Device Packages" and nothing comes up.
Click to expand...
Click to collapse
Try this one and let me know:
https://drive.google.com/file/d/0B31X8bH_5Gl-OHpva0dCbHBTb2c/view?usp=sharing

Great idea. Tried it with my ASUS MeMO Pad 8 (ME581CL) but after "Read Device Packages" nothing happens

[email protected] said:
Great idea. Tried it with my ASUS MeMO Pad 8 (ME581CL) but after "Read Device Packages" nothing happens
Click to expand...
Click to collapse
Look back a post and try that one.. Also, send me a screen shot.. Make sure USB debugging is on and in the correct mode as well.

This version works, thanks!
Will be great if this soft give option to disable modem fast dormancy service without root access.
Anyway, thanks.

My AV detects Malware.

Using licensed ESET - no malware detected.
Just disabled FastDormancy.apk (com.motorola.fastdormancy) - how to check if its disabled? In Running programs still see this service is running.

Maximus1a said:
My AV detects Malware.
Click to expand...
Click to collapse
It doesn't like the behavior of the program LOL

I cant get it to download from the webpage. I tried the one in the drive folder and it does not see my phone. Verizon Note 4. Looks awesome, cant wait to get it working!
Got it. I guess the server is overloaded!

Great job on this project addition. I'll be adding your link to my XDA signature this afternoon. Like you and many others, I too believe that until root is achieved on our devices (for those unable to at this time) that having this capability to do with our devices is the next best thing; hands down!
Again, great job to you and to the others like RootJunky and Misterxtc for making this possible for the community here at XDA.

Dear gatesjunior,
I wonder how you'r software disable/enable apk's?
For example: on my device (xt907) I'm not able to complete disable fast dormancy service (see screenshot) only "Force stop" it for a while.
Wonder which method you are using to disable it complete (are you disable it or just force stop it?)

howellcp said:
I cant get it to download from the webpage. I tried the one in the drive folder and it does not see my phone. Verizon Note 4. Looks awesome, cant wait to get it working!
Got it. I guess the server is overloaded!
Click to expand...
Click to collapse
Make sure your USB debugging is on and in the right mode.

[WIP] Enable additional 3G / LTE Band on YU Yureka

WORK IN PROGRESS.. UNTIL NOW NOT GETTING 100%
This was for CM11s, Don't try on CM12s
As soon as we found right procedure we'll Update here
This tutorial is not for newbies.. If you are not little advance user don't do this
After reboot Values reset to Orignal setting (Reset)
need to prevent NV recovery
1. Download Files Here containing all the necessary files and extract it on desktop.
2. Enable Android Debugging on your phone and connect it to your computer,
3. Open up ADB and type the following:
Code:
adb shell
su
setprop sys.usb.config diag,adb
4. Launch Device Manager go to & expand Other Devices,
Right click Android (or something related) listed under that menu
Choose Update Driver Software,
Browse my computer for driver software,
Let me pick from a list of device drivers on my computer,
Just Click Next,
Have Disk,
Browse to where you extracted YU Diagnostics Driver folder
Inside you will find 32bit and 64bit versions, pick one as per your OS
Select htcdiag.inf (for 32bit) or HtcUsbMdmV64.inf (for 64bit) file that you will Open.
Accept all warning messages and let the installation of the driver complete.
5. Once everything is done installing, under Modems or Ports (Com & LPT) in Device Manager you will find HTC USB Modem.
Right click and select Properties; in this you will see Port: COM<number>. Remember that COM<number> or write it down.
6. Open QPST v2.7 Build 4.11 > run as administrator setup.exe (Don’t run QPST.2.7.411.msi)
7. Open QPST Configuration from Start Menu,
Go to the Ports tab,
Click on Add New Port (right bottom corner);
In the Port field type in the COM<number> you wrote down/remembered from step 5 and in Port Label type YU and finally click OK (left bottom corner).
If you've followed all the steps correctly until here, you should be able to see something like this in the Active Phones tab:
View attachment 3258366
Keep QPST Configuration window open
8. Open QXDM-3.12.714 > run as administrator setup.exe (Don’t run QXDMInstaller.msi)
9. Open QXDM Professional (run as administrator),
go to Options menu,
Select Communications
Set Target port to your phone COM<number> you wrote down/remembered from step 5 from dropdown list, Press OK.
View attachment 3258367
10. Back to QXDM main window, in the "View" drop-down menu, selects NV Browser
View attachment 3258368
now the fun part begins
View attachment 3259381
Put check mark on Dual SIM (as shown above SS) for apply all setting to both SIMs (Thanks to @tirta.agung)
11. Inside the NV Browser window,
Scroll down and click on line 01877 (rf_bc_config)
Click the Read button save original value in notepad in case something goes wrong.
Replace Input value with 3460734838925427584
Click on Write button.
12. Inside the NV Browser window,
Scroll down and click on line 00946 (band_pref_16_31);
Click the Read button, save original value in notepad in case something goes wrong.
Replace Input value with 0x0FF8 (please don't be an idiot and don't edit the empty one with "nam" in the name)
Click on Write button.
13. Inside the NV Browser window,
scroll down and click on line 02954 (band_pref_32_63);
click the Read button, save original value in notepad in case something goes wrong.
replace Input value with 805765120 (please don't be an idiot and don't edit the empty one with "nam" in the name)
click on Write button.
14. Inside the NV Browser window,
scroll down and click on line 00441 (band_pref);
click the Read button, save original value in notepad in case something goes wrong.
replace Input value with 0x380 or 0xFFFF (please don't be an idiot and don't edit the empty one with "nam" in the name)
click on Write button.
If you have problem with selection, you can edit it directly from your phone: *#*#4636#*#* /Phone information /Menu /Select radio band > Automatic
15. Inside the NV Browser window,
scroll down and click on line 06828 (lte_bc_config);
click the Read button, save original value in notepad in case something goes wrong.
replace Input value with 1904863 (please don't be an idiot and don't edit the empty one with "ext" in the name)
click on Write button.
16. Now Close QXDM; Wait 30 seconds,
disable Android Debugging on your phone,
unplug it and reboot your device;
Once it comes back on, it might take a minute or two for it to acquire signal so don't panic.
DO this on your own risk.. No body is responcible for any lost
Conclusion:
The only real way to know if the whole thing got applied is to do steps 1 through 10 again (obviously skipping installations)
and reading all values or if you are in an area where you previously had bad or no reception.
You can see unlocked GSM/UMPTS bands from the *#*#4636#*#* /Phone information /Menu /Select radio band
For more features of QXDM i.e. recover lost IMEI or ESN go HERE (Thanks to @tirta.agung)
Credits:
Thanks to @BlackSoulxxx for his original work with the Qualcomm baseband software, for the modified Drivers and for the LTE NV values
Thanks to @olokos for his original tutorial
Thanks to @devilsshadow for his original tutorial
Thanks to @Albirew for his original tutorial
Thanks to @tirta.agung for bringing the original thread to my attention & Guide me in many ways
Thanks to @fards for finding the diagnostics command that made all this possible
Thanks to @hem12 who raised my will for finding these tutorials.
Thanks to @d3athwarrior for post this tutorial.

Reserved

Don't forget to put check marks on dual sims, and apply all settings to sim0 and sim1 (see attachment). By the way before u messed things up, back up your modemst1, modemst2, fsc, and fsg.
By the way we can also use qxdm to recover lost imei, just go to 0550, and insert your imei for SIM 1 (sim0 in qxdm) and SIM 2 (sim1 in qxdm), for example:
Code:
If your IMEI was: 954091051099226, then the boxes would look like so:
8
9a
45
90
1
15
90
29
62
or also recover lost esn (item no 0 and 5597) or meid (1943 and 5598).

Great guide, guys !:good::good::good:
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
Some error down there: "OPO" and huge load of credited people that seem dont fit in here. Clearly copied from OPO thread?

BlackSoulxxx said:
Great guide, guys !:good::good::good:
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
Some error down there: "OPO" and huge load of credited people that seem dont fit in here. Clearly copied from OPO thread?
Click to expand...
Click to collapse
Yes you'r right.. I don't want to leave anyone in credit for them work :good:
OPO removed :Hawkeye:
but that works for me..
Need help for prevent NV recovery from you all

If it's the same as the 1+1, replacing /system/bin/rmt_storage with a version not locked would prevent nv recovery (do you know if NV values were sticking in an older version? If so, take it's rmt_storage and try to replace current one with older one, I think it's worth trying)

Albirew said:
If it's the same as the 1+1, replacing /system/bin/rmt_storage with a version not locked would prevent nv recovery (do you know if NV values were sticking in an older version? If so, take it's rmt_storage and try to replace current one with older one, I think it's worth trying)
Click to expand...
Click to collapse
Hmmm, as far as I know, all NV settings, including IMEI, or MEID, ESN, etc, resides in your modemst1 and modemst2 partition. If you don't believe me and eager to try, first make a backup of those two partitions, then format or wipe the two partition inside your phone (use fastboot to do this), I'll bet for your YU, now your IMEI and NV settings are all gone.
To be honest, I just found out from this thread that there is an rmt_storage in CM phones, wkwkwkwkw, . If the rmt_storage function is trough, then CM is locking the phone NV settings from the HLOS side not Non-HLOS side. I'll do some research on this rmt_storage.

Need Help from your side
tirta.agung said:
Don't forget to put check marks on dual sims, and apply all settings to sim0 and sim1 (see attachment). By the way before u messed things up, back up your modemst1, modemst2, fsc, and fsg.
.....
or also recover lost esn (item no 0 and 5597) or meid (1943 and 5598).
Click to expand...
Click to collapse
BlackSoulxxx said:
Great guide, guys !:good::good::good:
Some error down there: "OPO" and huge load of credited people that seem dont fit in here. Clearly copied from OPO thread?
Click to expand...
Click to collapse
Albirew said:
If it's the same as the
.....
current one with older one, I think it's worth trying)
Click to expand...
Click to collapse
Now current status is
when I connect mobile
it shows me like that
Even I change USB config to diag,adb
thru ADB or manually
this time its present in default.prop
I try both
trying to disable MTP in mobile USB connection is not working
Window for Settings > Storage > 3dot > USB computer connection is working
but when I disable MTP.. its not working3
So need help from your side..
how I enter / install diag mode

@tirta.agung
I read your complete Guide regarding unbrick YU
but as that post has multipal guides ... I little confused ..
Sorry I am Xtreme noob for all that
Can you guide me an easy way to connect with QPST for enable LTE band
Can I try
Guide #3. REVIVING YOUR IMEIs (That for 32bit or 64bit)??
for connect QXDM

ekhasti said:
@tirta.agung
I read your complete Guide regarding unbrick YU
but as that post has multipal guides ... I little confused ..
Sorry I am Xtreme noob for all that
Can you guide me an easy way to connect with QPST for enable LTE band
Can I try
Guide #3. REVIVING YOUR IMEIs (That for 32bit or 64bit)??
for connect QXDM
Click to expand...
Click to collapse
Yes use guide number three, and download the necessary file there. By the way, to use the guide you have to be in stock CM kitkat.

How to use these tools for Xperia C6602

Long story short, did it work in the end for more than 1 person?

thanks for the post. but i have a Lollipop rom. I will wait for you to update the thread ....

Can we try this in lollipop??? Is there any update on this???

ekhasti said:
WORK IN PROGRESS.. UNTIL NOW NOT GETTING 100%
CM12s
As soon as we found right procedure we'll Update here
Click to expand...
Click to collapse
Hi there, attached is boot.img and a hack rmt_storage for CM 12.1. Just flash the boot.img to your phone and connect it with QXDM. Your phone will be recognized as qualcomm diagnostic port 903A. Copy and paste (you can use TWRP's file manager to do this) the rmt_storage to "/system/bin" and change its permission (chmod) to 0755. This will make your changes stick upon reboot.
By the way, to use all these files, you need to be on stock CM 12.1. I haven't tried it on any other ROM.

Bro...im on cm12.1 ...rooted...I didn't understand the procedure... Pls can u explain step by step ..pls....wats that qxad ..? Is a software...? Wer I get that..,pls reply bro
Sent from my AO5510 using XDA Free mobile app

tirta.agung said:
Hi there, attached is boot.img and a hack rmt_storage for CM 12.1. Just flash the boot.img to your phone and connect it with QXDM. Your phone will be recognized as qualcomm diagnostic port 903A. Copy and paste (you can use TWRP's file manager to do this) the rmt_storage to "/system/bin" and change its permission (chmod) to 0755. This will make your changes stick upon reboot.
By the way, to use all these files, you need to be on stock CM 12.1. I haven't tried it on any other ROM.
Click to expand...
Click to collapse
Now i upgraded to cm13.....can these two files work for me....pls reply
Sent from my AO5510 using XDA Forums

@ekhasti
I have tried doing this on Yureka - CM11 XNPH05Q. Installed all the drivers & softwares successfully. When I startup the QPST config to add a new port,
1. I have to uncheck the "Show serial and USB/QC diag ports only" to make the HTCUSBModem port visible.
2. Although I am able to add the port successfully I am unable to see the phone number, it says "No Phone".
Since it is unable to get the phone details I am unable to proceed further. Nothing is visible/editable QXDM. either.
I have manually edited the build.prop file to make sure USB debugging is enabled but to no avail. Please check the attached files, what is it that I am missing?
P.S - I am able to get my IMEI number using *#06#

Any suggestion Guys???

bluebl0od said:
Any suggestion Guys???
Click to expand...
Click to collapse
Guys, I am eagerly waiting for your updates

Programming modem with QPST/QXDM on Boost Desire 626S

Hello everyone. It's been heavily requested that I create a guide on how to program the values I provided in one of the posts on my previous boot image thread into the Boost Desire 626S modem so I decided to take the job into my own hands for your convenience.
First you will need QPST, QXDM, and the modem diag usb driver if it is not already installed on your computer. Here are the links:
QPST:
https://www.sendspace.com/filegroup/XynIcslf8H6Qm2TsJ5z4ZEocT85CdvbS
QXDM:
https://www.sendspace.com/filegroup/XynIcslf8H6Qm2TsJ5z4ZEocT85CdvbS
DIAG DRIVER:
https://www.sendspace.com/filegroup/XynIcslf8H6Qm2TsJ5z4ZEocT85CdvbS
1 --- INSTALLING SOFTWARE / DRIVERS
Run QPST.2.7.425 from the QPST folder in the QPST.zip archive and install it by clicking next through the dialog box at each step.
Run QXDMInstaller from the QXDM folder in the QXDM.zip archive and install it by clicking next at each step as well.
Run HTC CDMA LTE DIAG Modem Driver v3.0.2.0 from the inside the DIAGDRIVER.zip archive and you've got everything you need to now program the Boost Desire 626S modem.
2 --- SETTING UP USB DEBUGGING
---First you will need to enable usb debugging.
---Connect your Desire 626S to a usb port on your computer.
---Open the settings app and scroll to about and select it.
---Next, select software information then select more and tap on build number 7 times.
---This will enable access to Developer Options in the settings app.
---Tap back three times and you will now see developers options as selectable in the settings app.
---Tap on developer options and scroll down a bit to USB debugging option.
---Make sure it has a blue checkmark next to it so it is enabled.
3 --- SETTING UP DIAG USB ACCESS
---Now we will enable usb diag access to allow communications with QPST/QXDM.
---On your computer with the phone still connected, open a command prompt as administrator and type adb shell then hit enter.
---Or if you are using minimal adb and fastboot installation, open the shortcut for it as administrator and type adb shell then hit enter.
---On your phone, tick the box next to always allow and tap ok.
---You might have to type in adb shell again and hit enter.
---Do so and you will see [email protected]_a32ewhl:/ $ at the prompt which means you have shell access.
---Now we need root shell access.
---With the shell access, type in su and hit enter.
---Allow the root access for adb shell in the supersu prompt that pops up on your phone.
---You will now see [email protected]_a32ewhl:/ # in the command prompt window.
---Congrats you now have root access.
---With root shell access type this in and hit enter in the command prompt window:
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
---You might hear a ding and you have now enabled diag access to use QPST/QXDM in order to program the modem.
4 --- SETTING UP MODEM DIAG COMMUNICATION
---To open QXDM, click the orb in the bottom left hand corner to open the start menu and then click all programs.
---Scroll to QXDM Professional and click it and then click the next QXDM Professional shortcut under it.
---QXDM will now open so now it's time to access the diag port to the modem.
---Click on options in the bar towards the top of the window and then click on communications.
---Under target port, click on the box that says disconnect and click on the available COM port whether it might be COM1-5 then click ok.
5 --- PROGRAMMING MODEM NV ITEM VALUES
---Now we are down to the nitty gritty, actually programming the values for the bands in the modem. It is actually quite easy to do if you figure out what needs to be done.
---Click on the box next to view on the second bar down and click on the NV browser option to open it.
---In the NV browser window you will see some of the first typical NV items that might be included in a modem firmware but we are looking for the certain ones we want to edit to change bands and functionality.
---Left click the up and down arrows on the scroll bar and hold the left mouse button to slowly scroll from item value to item value if you need to, and slowly drag the knob on the scroll bar up and down if you require quicker navigation through the NV items.
---Once you reach an NV item you want to change, for instance, item 1877, click it and in the box under fields section you will see the input field used to change the following value field are both 0, followed by the respective nv items true name.
---To retrieve the content of each field for item 1877 or any nv item, click the read button in the bottom right hand side of the nv browser window, and you will be presented with the fields contents.
---For example NV item 1877 has a default value field content of 78135687 on my Boost Desire 626S so input field is also the same but this input field is what we change.
---Click the value under input once to select it then click it again and it will be editable with the caret blinking and 78135687 highlighted.
---Type in or copy and paste the value you wish to use for the value field in this input field once it is highlighted then hit enter on the keyboard and click write in the bottom right hand side of the window to make the new value stick.
---Congrats you have changed the value for an NV item.
---After writing new values, click offline in the bottom right hand side of the nv browser and wait 5 seconds.
---You will see the signal bar on your phone go blank.
---Click reset and the signal on your phone will be restored.
---Follow these last few steps when writing new values to ensure they stick.
---Reboot your phone and the values will stick.
6 --- GETTING MSL/SPC CODE FOR YOUR PHONE
---Scroll to item ID 00085 with description security code and click it to select it then click read in the bottom right hand side of the NV browser window
---In the input and value fields you will be presented with the MSL/SPC for your phone.
---Use this MSL/SPC code to program/edit the modem nv item values in EPST menus accessed by using ##3282# in the dialer.
---Also type in spc ****** in the text field in the command bar below the view bar in the QXDM window and hit enter, the six stars being the six digits of your MSL/SPC.
---Enter the MSL/SPC in the latter manner before writing new values to the modem for safe measure to ensure they stick.
---Quick note, enter *#*#4636#*#* in the dialer to open the testing menu, and tap phone information then scroll down to set preferred network type, and tap the down arrow to the right then scroll to and tap the network type you would like to use.
7 --- HERE ARE SOME RELEVANT NV ITEMS AND THE VALUES TO WRITE TO THEM....
----------------
Items 6828 and 6829
35184372088830
all lte
----------------
Item 65633
0x00001FFFFFFFFFFE
all LTE Bands
----------------
Item 441
32767
all 3G
----------------
Item 946
65535
all 3G
----------------
Item 1878
32
max HW band
----------------
Item 2954
4294967295
all 3G
----------------
Item 1877
18446744073709551615
all 3G
----------------
Item 4548
18446744073709551615
all 3G
----------------
Item 11
B only
Channel 384 and 777
----------------
Item 12
B only
Channel 384 and 777
----------------
Item 441
0x2
Channel B
----------------
Item 442
0xFFFF
All Roam
----------------
Item 10
LTE Only
Band Pref
----------------
Item 5
0x0
Slot Cycle Index
-------------------
Item 4
0x9A
Station Class Mark
----------------
Item 179
0
Voice Privacy
----------------

What next?
---------- Post added at 11:36 AM ---------- Previous post was at 11:19 AM ----------
I meant how do I use d softwares to edit LTE bands

Thanks a lot man. I've successfully programmed the values and although I have a Sprint version and the LTE bands are different in my country, I was able to get the values from NV calculator on play store. I've not had time to check if they work albeit I programmed 3g bands a while back and band 2100 which works in my country failed to work, I hope the LTE works. Thanks once again

You're Welcome
doyin116 said:
Thanks a lot man. I've successfully programmed the values and although I have a Sprint version and the LTE bands are different in my country, I was able to get the values from NV calculator on play store. I've not had time to check if they work albeit I programmed 3g bands a while back and band 2100 which works in my country failed to work, I hope the LTE works. Thanks once again
Click to expand...
Click to collapse
You're Welcome. Glad it worked for you.

@anthonykb
---With root shell access type this in and hit enter in the command prompt window:
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
---You might hear a ding and you have now enabled diag access to use QPST/QXDM in order to program the modem.
Click to expand...
Click to collapse
Great work !!
Do you have any reference to other commands for switching the download / service modes?
To flash boot-loaders and such !!
I have the board support package for the msm8909 chipset and I am working on building the required programmers.
Just need to write my partition.xml ( I have the GPT info. )
My plan is to make a Qfil flashable Service Rom.

Update: Bands were successfully programmed as I stated earlier but sadly, they don't work. I just hope and pray someone somewhere is making a from scratch custom kernel for this device

@doyin116
Did that for Lollipop ( Completed ) For Marshmallow they didn't release the source yet.
I don't think it will be a problem to use the CAF source. ( Will Find out soon. )
Here is my kernel.
http://forum.xda-developers.com/desire-626/development/kernel-wip-port-lollipop-5-1-source-t3470476
Here's my source.
https://github.com/Bigcountry907/kernel_htc_a32eul
I just synced the CAF Android 7.0 source.
It's gonna be a wile cause I been developing this by my self but it is in the works.
I have built the UBERTC cortex a9 toolchains and compiled the kernel inline with the recovery both in omnirom 6.0 and omnirom7.0.
Omnirom 7.0 uses Ninja for building. https://ninja-build.org/
I didn't know if this would cause a problem but it didn't. None I couldn't fix anyway.
So I have used the 5.1 kernel source and built it successfully in newer android versions.
It could be the combination of ninja and the UBERTC toolchain that make it work. IDK.
What do you need in the kernel? I might have it built.

BigCountry907 said:
@doyin116
Did that for Lollipop ( Completed ) For Marshmallow they didn't release the source yet.
I don't think it will be a problem to use the CAF source. ( Will Find out soon. )
Here is my kernel.
http://forum.xda-developers.com/desire-626/development/kernel-wip-port-lollipop-5-1-source-t3470476
Here's my source.
https://github.com/Bigcountry907/kernel_htc_a32eul
I just synced the CAF Android 7.0 source.
It's gonna be a wile cause I been developing this by my self but it is in the works.
I have built the UBERTC cortex a9 toolchains and compiled the kernel inline with the recovery both in omnirom 6.0 and omnirom7.0.
Omnirom 7.0 uses Ninja for building. https://ninja-build.org/
I didn't know if this would cause a problem but it didn't. None I couldn't fix anyway.
So I have used the 5.1 kernel source and built it successfully in newer android versions.
It could be the combination of ninja and the UBERTC toolchain that make it work. IDK.
What do you need in the kernel? I might have it built.[/QUOTE
Came across your kernel but from my understanding, it was meant for the METRO PCs version of 626s while mine is the Sprint version. I also tried to downgrade from marshmallow to lollipop but wasn't successful because it seemed the tutorial again was for METRO PCs. As to what I need in the kernel, I heard Qualcomm has an anti-tamper settings or so that prevents flashed bands from working but can be by passed by a built from scratch kernel.
My questions now are: can I flash your kernel on my 626s albeit the Sprint version and if yes, how do I downgrade to 5.1 on my Sprint version. If no, could you please create a custom kernel for the Sprint version? Thanks
Click to expand...
Click to collapse

Maybe I can get you a ruu of lolipop.
Let me go see.
Most likly I need to build you a kernel.

BigCountry907 said:
@doyin116
Did that for Lollipop ( Completed ) For Marshmallow they didn't release the source yet.
I don't think it will be a problem to use the CAF source. ( Will Find out soon. )
Here is my kernel.
http://forum.xda-developers.com/desire-626/development/kernel-wip-port-lollipop-5-1-source-t3470476
Here's my source.
https://github.com/Bigcountry907/kernel_htc_a32eul
I just synced the CAF Android 7.0 source.
It's gonna be a wile cause I been developing this by my self but it is in the works.
I have built the UBERTC cortex a9 toolchains and compiled the kernel inline with the recovery both in omnirom 6.0 and omnirom7.0.
Omnirom 7.0 uses Ninja for building. https://ninja-build.org/
I didn't know if this would cause a problem but it didn't. None I couldn't fix anyway.
So I have used the 5.1 kernel source and built it successfully in newer android versions.
It could be the combination of ninja and the UBERTC toolchain that make it work. IDK.
What do you need in the kernel? I might have it built.
Click to expand...
Click to collapse
BigCountry907 said:
Maybe I can get you a ruu of lolipop.
Let me go see.
Most likly I need to build you a kernel.
Click to expand...
Click to collapse
Would really appreciate you building me a kernel. Thanks in advance

@doyin116
I got my hands on a RUU for sprint lolipop.
I will upload when I get a chance.
Right now i'm in kernel mode so you might get lucky.
Hopefully I can add the sprint config to my tree and build it.
I'm trying that with the vzw 526. So if all goes well........
After I make recovery for 526 I will compile you a kernel.

BigCountry907 said:
@doyin116
I got my hands on a RUU for sprint lolipop.
I will upload when I get a chance.
Right now i'm in kernel mode so you might get lucky.
Hopefully I can add the sprint config to my tree and build it.
I'm trying that with the vzw 526. So if all goes well........
After I make recovery for 526 I will compile you a kernel.
Click to expand...
Click to collapse
I'm glad. Is there a time frame for all of this to be done?

I will upload this ruu tonight. Over the weekend I will put together the kernel over the weekend.
You will have to test it. I don't think I can flash sprint to my device. It's metro. But I am s-off.

BigCountry907 said:
@doyin116
I got my hands on a RUU for sprint lolipop.
I will upload when I get a chance.
Right now i'm in kernel mode so you might get lucky.
Hopefully I can add the sprint config to my tree and build it.
I'm trying that with the vzw 526. So if all goes well........
After I make recovery for 526 I will compile you a kernel.
Click to expand...
Click to collapse
BigCountry907 said:
I will upload this ruu tonight. Over the weekend I will put together the kernel over the weekend.
You will have to test it. I don't think I can flash sprint to my device. It's metro. But I am s-off.
Click to expand...
Click to collapse
No problem. I'm up for it

@doyin116n116
Here is the 5.1 ruu for sprint.
https://drive.google.com/open?id=0B8jitdIyh2NtUHQ2YWd5T2RCUFk
Download it and rename the file 0PM9IMG.zip.
See the downgrade post for metro pcs and edit the mainver in the misc partition as shown there.
You can just flash the misc.img that is posted on that thread.
Copy the 0PM9IMG.zip to your sdcard.
Boot the phone into download mode.
It will ask you if you want to install the ruu.
Hit the vol up key to install it.
If it reboots the first time back to download mode then hit vol up again.
It will flash for sure.
And don't worry.....it is easier to go back to MM than it is to go to LP.

BigCountry907 said:
@doyin116n116
Here is the 5.1 ruu for sprint.
https://drive.google.com/open?id=0B8jitdIyh2NtUHQ2YWd5T2RCUFk
Download it and rename the file 0PM9IMG.zip.
See the downgrade post for metro pcs and edit the mainver in the misc partition as shown there.
You can just flash the misc.img that is posted on that thread.
Copy the 0PM9IMG.zip to your sdcard.
Boot the phone into download mode.
It will ask you if you want to install the ruu.
Hit the vol up key to install it.
If it reboots the first time back to download mode then hit vol up again.
It will flash for sure.
And don't worry.....it is easier to go back to MM than it is to go to LP.
Click to expand...
Click to collapse
@BigCountry907 I'm having issues flashing the misc.img. I flashed through adb fastboot flash misc.img and it said unknown partition 'misc.img' error: cannot determine image file name for 'misc.img'. I flashed through twrp and it said could not find meta-inf/com/Google/Android/update-binary in the zip file. Through adb I did adb push misc.img /sdcard/".
"adb shell"
"su"
"dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc" and it succeeded but when I flashed the 5.1 ruu it said ru_zip_error.
Could it be that the downgrading process is for metro PCs/ do I have to be unrooted or can I get detailed process of flashing it if I did it wrong. Alternatively, is there a tool I can use to access the misc.img partition and edit it myself?

@doyin116
I am creating a new how to thread.
We have got this thread way off topic.
The new thread is here.
http://forum.xda-developers.com/desire-626/general/how-to-downgrade-sprint-desire-626s-to-t3498653
Give me a little wile to write it up.
If a Moderator would like to move post #7 through post #17 to there that would be good.
How do we request a moderator to do that?

Old thread on old phone, I realize... but hoping someone might catch this & assist me. Having issues with gather SPC using QXDM 03.14.594 on 626s 0PM92 - Sprint MM ROM running on I-Wireless [T-Mobile].
While attempting READ on 00085, response is: "No DIAG response received".
Concerned about programming NV values in EPST w/o it. Any thoughts?
Update: After upgrading both qxdm/qpst, I'm getting a return on read from phone. Has it possibly been set as: 000000?