[Q] QPST and getting T-Mobile HSPA+/LTE Bands - Galaxy S 4 Q&A, Help & Troubleshooting

I have a new I9505G running Kit Kat 4.4.2. It consistently gets HPSA but does not get HPSA+ or LTE even though I am in a T-Mobile LTE service area (New York City).
I called Google device support and they referred me to this Youtube http://www.youtube.com/watch?v=eb0iCtG4T6I
It advises installing a phoneutil.apk on the phone and QPST on a Windows computer. I verified that the Samsung USB drivers are installed. But where I reach the step where I enter *#0808# on the phone to get to the menu where I can select DM+MODEM+ADB the procedure fails. Entering *#0808# gets me "USSD code running..." shown briefly before showing "Unable to process request" and an OK button. Without this step, the Samsung USB Modem drivers did not show under Ports in Device Manager when the phone is connected via USB. I have used the original S4 USB cord. No com ports show with 0 in the Phone column in QPST and I am led to believe that I can't install the 337_AWS.qcn file to get the additional bands.
My bootloader *is* unlocked (and the phone is rooted). I read this thread which refers to *#0808# as well. Ihttp://forum.xda-developers.com/showthread.php?t=2370466
I even tried the older *#7284# with the same result.

I'm having a similar issue with some USSD Codes. I can access *#*#4636#*#* but not *#7284# or many other USSD codes.
I have the I9505G running Android 4.4.2. It's rooted and unlocked. I installed the phoneutil.apk, but I think it's not working properly in the latest KitKat.

I did get the LTE bands working with a new SIM. Apparently mine was so old that it only supported 3G.

I know this is an old thread, but I only went through the same situation yesterday. Though it is not likely to benefit the OP, it may for someone who still owns this phone. When you set your phone to DM+MODEM+ADB, your Windows driver can no longer work with it UNLESS you have enabled CP LOGGING. Many rooted phones have for example TWRP installed to replace the stock recovery. For this exercise, you need to temporarily return to the STOCK RECOVERY to enable this option.
However, even if you overcome the Windows driver issue, you may still have challenges trying to flash the I337 AWS qcn to an I9505 phone. When I tried it yesterday, the flashing stopped at 5% into it and prompted me this error message, "received an invalid command from the phone" or something like that.
Since I have previously backed up my existing config to an XQCN file, I tried to restore this file just to see what would happen. Again, it failed at 5% with the same error. Why would the phone reject an XQCN generated from itself?
Worry not! When it fails at 5%, you will get your radio back simply by rebooting. No harm has been done.
In summary, even though I could get QPST fired up and create a backup, I am not able to write a QCN to an I9505. If anyone has successfully done it, plz share your experience. Thank you

Related

Droid X crashed, uh oh.

Got the Droid X to activate it on Alltel like I did very successfully with my Eris.
Installed HW virtual serial port software, created the virtual serial port, phone was detected and showing up correctly in QPST, went directly to CDMA Workshop and ripped the NV file from the phone, edited all the NV information to alltel's 3G provisioning with a HEX translator, uploaded the NV file to the phone and uploaded the Alltel PRL... all seemed well. Restarted the phone, it now shows no service. When I go to Settings, it tells me the baseband version is "unknown" and it doesnt know the ESN or anything, that isn't good. I tried reconnecting to CDMA workshop, if I try to restore original NV file, it doesn't know the SPC anymore so it doesn't allow it, SPC 000000 isn't recognized now. How can I recover the radio ? I tried restoring it (hard reset) through the settings, security menu AND the Power+home buttons way. After restoring, still no service and SPC is still incorrect, how do I get the radio back to default values ? CAn I reflash the phone? Anyone know where the factory rom is so I can do this ? Ah man, help me please :O
Other than that, I guess I'll have to have motorola take a look at it since I don't have it signed up to a verizon account, my bet is that verizon won't help me. thanks
Did a system "full reboot" help any??
No it hard resets normally and reboots to the welcome wizard, functions perfectly, but still "No Service" and "unknown" baseband in the settings...
I'm thinking I'll have to have the stock Rom file to flash my phone, hopefully this will flash the factory baseband too or maybe tomorrows update will fix my broken baseband, looks like from the information, it updates the baseband, wonder if it will update a totally dysfunctional baseband?
Yikes,.. this blows.
I don't understand why you didn't back up the rom if you were attempting something like this.
There is a Droid X update coming pretty soon, so I'm sure by that time the new rom will be available.
Well, I backed up the NV items, I figured that would be sufficient, guess not, Trial and error I suppose, but you're right.
What software do I use to back up the rom of the Droid X ? I know there is a key sequence on the Droid, what about the droid X ? The recovery screen (Power + Home) brings me to a menu allowing system recovery/wipe install update.zip from memory card, and thats it.
I have a buddy right here in town down the block that got the droid x with me, can I back the rom up off of his and flash that rom to my phone?
Help is SO appreciated...
EDIT
The system dumps that are floating around the web, is that a ROM backup ? http://www.droidxforums.com/forum/droid-x-hacks/114-new-droid-x-retail-dump-straight-out-pot.html
Can I put that file in the SD card as update.zip and flash it?
stevey500 said:
Got the Droid X to activate it on Alltel like I did very successfully with my Eris.
Installed HW virtual serial port software, created the virtual serial port, phone was detected and showing up correctly in QPST, went directly to CDMA Workshop and ripped the NV file from the phone, edited all the NV information to alltel's 3G provisioning with a HEX translator, uploaded the NV file to the phone and uploaded the Alltel PRL... all seemed well. Restarted the phone, it now shows no service. When I go to Settings, it tells me the baseband version is "unknown" and it doesnt know the ESN or anything, that isn't good. I tried reconnecting to CDMA workshop, if I try to restore original NV file, it doesn't know the SPC anymore so it doesn't allow it, SPC 000000 isn't recognized now. How can I recover the radio ? I tried restoring it (hard reset) through the settings, security menu AND the Power+home buttons way. After restoring, still no service and SPC is still incorrect, how do I get the radio back to default values ? CAn I reflash the phone? Anyone know where the factory rom is so I can do this ? Ah man, help me please :O
Other than that, I guess I'll have to have motorola take a look at it since I don't have it signed up to a verizon account, my bet is that verizon won't help me. thanks
Click to expand...
Click to collapse
why not use QXDM to modify the ESN?
Worth a shot...
You can try using the motorola troubleshooter. Its what they use to update your phone anyways and since the new update came out you might be able to install over what you did...I cant post a link because Im new but follow the instructions below and it will walk you through the update process via computer. I figure with a phone thats not working its worth a shot.
Go to Motorola's website and click the droid advert right on the left side of the screen.
Under the "Support" tab in the upper right hand corner is another tab called "Owner Support" click on that.
On the left hand side there are more tabs so this time click on "Update My Software"
It will give you a list of options, choose "Via Computer"
From here it will check your computer for their software and prompt you to download it. Its the troubleshooting software and it will ask you a few questions, its also what they use to update your software via computer so it may be capable of flashing your phone for you. Best of luck and let us know what the end result is.
I haven't tried either of these... but I'm about to start flashing a droid X to cricket and bookmarked these posts in case I mess something up. Proceed with caution as I have no first hand experience with these.
I'm still trying to get a handle on if the service programming parameters (the spc, MDN, MIN, SID, etc.) are updated as part of baseband updates, it sounds like they are since they are saying the device needs to be re-activated after applying either of these updates.
If a baseband update refreshes the service programming parameters here are the two ways I've found of updating the baseband:
Here's a link to a post for updating the baseband portion of your device (without updating the ROM):
http://alldroid.org/Default.aspx?tabid=62&g=posts&t=246
I don't know if this will work on a device that doesn't have a valid baseband prior to the update. Regardless, if your phone is bricked this may be a valid option to try.
There is also a 2.1 SPL file floating around which is the entire system image, the baseband and the rom. You will need to use rsdlite to apply this image to your phone. DO NOT APPLY THIS IF YOU ARE RUNNING FROYO.

[Q] Failed to get HSPA+ AWS Bands now nothing works

Hello,
I was following the guide on how to get the HSPA+ AWS Bands enabled for my phone. I am very new at this and now know that my phone version is different to the one the guide was for (i337).
I have a i9505 version.
During the installation attempt I installed QTSP, and under the ports tab I stupidly removed one of the COM ports as I was attempting to get it to work. I managed install a 337_AWS.qcn onto a port that was showing the phone connected, and this file was the one that is suppose to get the other bands to work. However - now my phone cannot recognise any sim card. - it simply says that none is in the phone (ive tried multiple cards)
I understand that I am stupid, and will never attempt anything like this again.
Does anyone know how to get my default .qcn files back so I can go back to normal? I have tried flash over my New Zealand providers stuff, but it appears the bands are still not working as I still have the no sim problem.
I'm really lost at what to do now - do you think I have to send it in to get it fixed?
I could put the guide up I used if that helps? (thinking it might be against the rules so i'll keep it off until someone more knowledgable asks)
Many thanks,
Matt

idoneapps.com Domestic Sim Unlock for SM-G900P (Review)

Hello this thread is my experience and review of idoneapps.com Sprint S5 domestic sim unlock.
REQUIREMENTS
-Running Lollipop or higher (I was on stock rooted 6.0.1)
-must be rooted
-Different carrier sim, for example I have At&t.
-Around $30, I know paid ughhh but honestly it's worth every penny.
Okay so here is my story that lead to this. I repair cellphones for a living and we do a lot of business with Verizon, well one of the workers offered me a Sprint S5 for $50. It was tempting as it was in great condition, the problem? I have AT&T. Anyways I bought the phone on impulse, as if I couldn't use it, I could still tweak and develop on it. So win/win for me.
Well after tons of research to domestically unlock the SM-G900P, I found idoneapps.
idoneapps have created an apk that will permanently sim unlock your Sprint and Boost mobile devices. (Check to see device compatibility on their website.)
Go to idoneapps.com
Go to Android unlocking services
{
"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"
}
Then go to "Samsung Phone unlock for final user" and hit "download unlock apk"
Install the apk and open the app.
Now that the app is opened, you now have to buy your license, when you confirms your purchase, it will send a confirmation .zip to your email. Open that .zip and it will grant you the unlock permission.
Now go back to the unlock apk, and go ahead and hit the unlock button, the phone should reboot twice, the first time it reboots, go back into the app so it can reboot for the second time.
After that you should now be unlocked, if you are rooted, the app will automatically install APNs, but if not then you can go ahead and add your APN.
The app does other helpful things as well.
It debrands your phone as well. Getting rid of hands free activation.
CONS
Ahh there has to be a catch somewhere right?
Because the sprint S5 is a CDMA phone, it doesn't get all the benefits of a GSM carrier. The only downside that I have personally experienced is that I don't get 4G or LTE.
At&t is very strong in my area so I'm fine with just 3g. Also if you run a custom ROM with Xblast tools, you can throttle your 3g.
Anyways, it's great for unlocking your phone to use with At&t or T-Mobile.
http://uploads.tapatalk-cdn.com/20160625/dc1823c5dcfa737c87d2bfdf820983installation
Also you are free to flash as many custom/stock ROMs/recoveries as you like as its permanent. (Proof in screenshots as I'm now running CM13) There are ways to relock the device if you aren't careful, but that requires a special dialer code and or messing with service mode. But you have unlimited unlocks incase that ever happens.
Also for some reason it says disconnected for my network but I assure you that I get calling/data/texting, I believe that is from "tricking" the phone during the unlock installation.
Hopefully this guide helps someone else!
Sent from SM-G900Pkltespr
the unlock does indeed work on the g900p as ive unlocked 2 of them personally via idoneapps. I also only get the hspa connection, but that is very likely due to the LTE bands preselected on the phone. I have tried to do the stuff in this thread, but ive not got qpst to find the diag port on the g900p. Ive only half a$$ed in my attempts, so im not convinced that it cant be done, quite the opposite actually. Modder beware, if you brick your phone trying this, its not my fault, but its been said to work on many phones
youdoofus said:
the unlock does indeed work on the g900p as ive unlocked 2 of them personally via idoneapps. I also only get the hspa connection, but that is very likely due to the LTE bands preselected on the phone. I have tried to do the stuff in this thread, but ive not got qpst to find the diag port on the g900p. Ive only half a$$ed in my attempts, so im not convinced that it cant be done, quite the opposite actually. Modder beware, if you brick your phone trying this, its not my fault, but its been said to work on many phones
Click to expand...
Click to collapse
I actually managed to edit using qpst/qxdm and got those LTE values to stick after reboot. But with all my persistence, no LTE. I've done build.prop edits as well but soon learned that the firmware I'm on cannot edit GSM properties on build.prop. at least not for g900p
SM-900P CM13
youdoofus said:
the unlock does indeed work on the g900p as ive unlocked 2 of them personally via idoneapps. I also only get the hspa connection, but that is very likely due to the LTE bands preselected on the phone. I have tried to do the stuff in this thread, but ive not got qpst to find the diag port on the g900p. Ive only half a$$ed in my attempts, so im not convinced that it cant be done, quite the opposite actually. Modder beware, if you brick your phone trying this, its not my fault, but its been said to work on many phones
Click to expand...
Click to collapse
Also are you rooted? I can provide some information on how to connect to qpst. I had a really difficult time trying to get it to recognize my device. (Assuming you are on marshmallow)
SM-900P CM13
im very rooted LOL i rooted it 3 days after getting it, which was 7 days after release 2+ years ago. I wasnt too keen on MM, so im still using ol' reliable MOAR 7.0. And yeah, id appreciate the heads up on what part im missing!
youdoofus said:
im very rooted LOL i rooted it 3 days after getting it, which was 7 days after release 2+ years ago. I wasnt too keen on MM, so im still using ol' reliable MOAR 7.0. And yeah, id appreciate the heads up on what part im missing!
Click to expand...
Click to collapse
Well I'm not too sure if this is the right answer for you considering the software differences, I'm running windows 8 with Marshmallow based 6.0.1 CM13
What you'll need:
Terminal emulator
QXDM
QPST
EFS Professional
NV Calculator app
USB cable (no hub)
Patience
So I found it to be rather difficult to enable diag mode for the S5 with marshmallow as its so new that hardly anybody found a method to successfully activate it.
1. Turn on usb debugging in developer settings
2.Set USB to DM-Modem-Adb
-Open terminal app
Use the following commands
su
setprop sys.usb.config diag,acm,adb
Now verify w/ command
getprop sys.usb.config
It should tell you if the commands did indeed stick. (diag,acm,adb)
This method should install a driver if you are connected to a usb with debugging on.
METHOD 2
Plug in your phone to your pc and open EFS Professional and click on the Samsung Tools tab.
You then should see a pull down setting to change the usb mode to DM-MODEM-ADB. This method should automatically install a driver and enforce diag/adb server (if your diag driver hasn't yet been installed.) Which is where I had the most difficulty in getting it to connect to my PC. EFS needs to berunning and be ready/connected before you open QXDM.
3. Open QXDM (Run as administrator)
(DISCLAIMER! It's important to understand that you should run QXDM AFTER you successfully connected to DM-MODEM-ADB server in EFS Professional)
-In QXDM hit options > communication
You should see a COM port that is opened up and active. If this isn't working. Restart process 1/2 from complete scratch.
4. Click the target port pulldown menu in the communications window and select the COM channel that is displayed in PortType that is active. After hitting the "OK" button, close the window.
Now you should be able to read and write your nv memory.
5. Click View > Common > Nv browser.
Use NV calculator app for the bands you need. The phone itself only has 850-2100mhz through WCDMA.
I would advise to only edit 6828/6829. If it says you need to edit RF band config, in my version of QXDM reads 1877 as a CDMA property, not a GSM or WCDMA property. While messing with this I learned that it might possibly be something of unimportance to the mod, correct me if I'm wrong.
Try it at your own risk.
If you can't still connect to your pc, close all your programs. And start over every time it doesn't work.
Also I noticed that there is never an actual diag driver in device manager like there used to be in windows 7. Once in diag mode, device manager should recognize the device as COM. And possibly as a Modem as well.
Make the edits and reboot when you are done. Please report back with results as I have the exact phone and would like to see if it works to get a final answer if this can actually be done. Test around with your hiddenmenu and apns to see if you can get it.
If you have any questions, report back here so if there is a solution it can help others!
SM-900P CM13
Also check here
http://forum.xda-developers.com/showthread.php?t=2948822
SM-900P CM13
xholomovementx said:
well i'm not too sure if this is the right answer for you considering the software differences, i'm running windows 8 with marshmallow based 6.0.1 cm13
what you'll need:
Terminal emulator
qxdm
qpst
efs professional
nv calculator app
usb cable (no hub)
patience
so i found it to be rather difficult to enable diag mode for the s5 with marshmallow as its so new that hardly anybody found a method to successfully activate it.
1. Turn on usb debugging in developer settings
2.set usb to dm-modem-adb
-open terminal app
use the following commands
su
setprop sys.usb.config diag,acm,adb
now verify w/ command
getprop sys.usb.config
it should tell you if the commands did indeed stick. (diag,acm,adb)
this method should install a driver if you are connected to a usb with debugging on.
Method 2
plug in your phone to your pc and open efs professional and click on the samsung tools tab.
You then should see a pull down setting to change the usb mode to dm-modem-adb. This method should automatically install a driver and enforce diag/adb server (if your diag driver hasn't yet been installed.) which is where i had the most difficulty in getting it to connect to my pc. Efs needs to berunning and be ready/connected before you open qxdm.
3. Open qxdm (run as administrator)
(disclaimer! It's important to understand that you should run qxdm after you successfully connected to dm-modem-adb server in efs professional)
-in qxdm hit options > communication
you should see a com port that is opened up and active. If this isn't working. Restart process 1/2 from complete scratch.
4. Click the target port pulldown menu in the communications window and select the com channel that is displayed in porttype that is active. After hitting the "ok" button, close the window.
Now you should be able to read and write your nv memory.
5. Click view > common > nv browser.
Use nv calculator app for the bands you need. The phone itself only has 850-2100mhz through wcdma.
I would advise to only edit 6828/6829. If it says you need to edit rf band config, in my version of qxdm reads 1877 as a cdma property, not a gsm or wcdma property. While messing with this i learned that it might possibly be something of unimportance to the mod, correct me if i'm wrong.
Try it at your own risk.
If you can't still connect to your pc, close all your programs. And start over every time it doesn't work.
Also i noticed that there is never an actual diag driver in device manager like there used to be in windows 7. Once in diag mode, device manager should recognize the device as com. And possibly as a modem as well.
Make the edits and reboot when you are done. Please report back with results as i have the exact phone and would like to see if it works to get a final answer if this can actually be done. Test around with your hiddenmenu and apns to see if you can get it.
If you have any questions, report back here so if there is a solution it can help others!
Edit* make sure you connect the active state and that is reading your baseband under phone.
Sm-900p cm13
Click to expand...
Click to collapse
sm-900p cm13
Right on man! Thanks!! I'll have to give this a whirl later today. And as for the differences in Roms, I have zero issue flashing a ROM to get this working because it should stick once complete and I can then go back to moar if I want. Thanks again!
Sent from my SM-G900P using XDA Free mobile app
OK, so I tried several times and I can't get the diag port to show. Tried different modems and nothing. I flashed the modem with the idone unlock app but not with Odin. Might try that later. I know this is a few weeks back now, life got a tad hectic for me to spend much time on the computer and fiddling with odin
Thanks, this indeed worked. It's worth the money!!
I was able to unlock mines using the free version of idoneapps 3.1.8 (GTv3.1.8) just fine, however I haven't tested mines to see if it would work on AT&T. I just purchased an AT&T Service and will be getting my SIM card by mail in a few more days.
Does the free version of idoneapps 3.1.8 unlocks it domestically, or is it just an international unlock?
FNetV1 said:
I was able to unlock mines using the free version of idoneapps 3.1.8 (GTv3.1.8) just fine, however I haven't tested mines to see if it would work on AT&T. I just purchased an AT&T Service and will be getting my SIM card by mail in a few more days.
Does the free version of idoneapps 3.1.8 unlocks it domestically, or is it just an international unlock?
Click to expand...
Click to collapse
I have not tried it, but I have read that for domestic unlock to work, the steps are the same except that you also have to turn GCF settings off. It can be done by the IOTHiddenMenu. The steps are found here: https://idoneapps.com/settings.php. hopefully it works
FNetV1 said:
I was able to unlock mines using the free version of idoneapps 3.1.8 (GTv3.1.8) just fine, however I haven't tested mines to see if it would work on AT&T. I just purchased an AT&T Service and will be getting my SIM card by mail in a few more days.
Does the free version of idoneapps 3.1.8 unlocks it domestically, or is it just an international unlock?
Click to expand...
Click to collapse
This is a ridiculous question, but when I looked online and searched for the free version of idoneapps 3.1.8 and downloaded, the app I see doesn't have an obvious way to unlock the screen; this is what I see:
The only thing that's close is "SIM UICC Unlock." When I click on that it brings up a Network Unlock prompt. I downloaded the non-free one and it looks dead simple, but if there's a way to do it and save $35 I'm all for it
Did I download the wrong app?
For my Sprint Samsung Galaxy S5 (SM-G900P) there was an extra step that I needed to perform in order to unlock it for domestic usage according to: https://idoneapps.com/settings.php (Thanks @eurohunder for pointing this out for me). According to this quoted info, I am supposed to click on GCS settings on their paid for version of IDONEAPPS, but dont worry, I know that on the free version there is no such fancy button labeled "GCF", but fear no more! I will show you how to access the same exact menu where that fancy "GCF" button on the paid-for version leads to, its none other than simply clicking on the IOTHIDDENMENU button that I can see on your screenshot as button #2 on the bottom list, there you will see a series of menu, I believe the one labeled"Testmode" or something like that from the big menu leads you exactly to the same spot (which is the "SERVICE MODE") as if you were to click on the "GCF" button fron the paid for version, there you can just continue to follow the instructions on that page as it will be exact, depending on many factor and firmware version you are running.
Now that you have access the SERVICE MODE (or in other words "GCF"'s target destination if you were using the paid-for version) You would go to [2] UE Settings & Info, then [1] Settings, then [1] Protocol, then [4] GCF (note: MAYBE the "GCF" button on the paid for version leads you directly to this spot, bypassing the other menu options directly, maybe yes, maybe no, but it doesn't matter, the point is that you made it there), then finally you would tap "[1] GSM/(E)GPRS/WCDMA GCF ON", you will see a confirmation that the command succeeded, and as per the instructions from your own device you shall reboot your device using the power buttons and then tap on "restart/reboot". Thats all. At least in my case that should be it for unlocking GSM bands, according for further research I did, the Sprint Galaxy S5 would only work in 3G mode because all the 4G LTE GSM bands are blocked and the ones aren't compatible with the AT&T network (which is the network that I plan to use very soon on this device), so to fix that predicament because I dont want to be stuck on 3G mode I downloaded QPST and QXDM, I had to downgrade my firmware to kit-kat thorugh ODIN (was a b*tch sourcing the original .tar image on the internet, most servers that used to have it no longer had the file and when I was finally about to give up and pay sammobile their $15 to be able to download it from their servers at a speed greater than 15 kbps I finally found a server that was still hosting the NE5 firmware for free!)
For my particular device, beginning on Lollipop Samsung took measures (on the kernel) to prevent users from having access to QPST/QXDM, installing a customer kernel would have given access to QPST/QSDM without having to downgrade firmwares, but the custom kernel that I needed was nowhere to be found, so my only option was to do the firmware downgrade and thanks God that I didn't have the stock Marshmallow bootloader because downgrading would have been impossible then (Samsung implemented a downgrade check - blocker for the S5 starting on Marshmallow) so I was running the BO6 bootloader/baseband, the last ones of the safe bootloader version that allows downgrades.
So anyways, on QPST I made sure that all the 3G bands that I needed for AT&T were indeed enabled, and on QXDM I enabled all LTE bands (thanks to someone who posted the string value to enable all LTE bands for GSM).
So hopefully, when my AT&T SIM card arrives on Thursday Oct 26 not only should I have 3G access, but I also should have 4G LTE access as well, and after my AT&T SIM card arrives I would finally put all this to a test, how effective all this was and most importantly, if this method for domestic GSM unlock really works for me.
FNetV1 said:
For my Sprint Samsung Galaxy S5 (SM-G900P) there was an extra step that I needed to perform in order to unlock it for domestic usage according to: https://idoneapps.com/settings.php (Thanks @eurohunder for pointing this out for me). According to this quoted info, I am supposed to click on GCS settings on their paid for version of IDONEAPPS, but dont worry, I know that on the free version there is no such fancy button labeled "GCF", but fear no more! I will show you how to access the same exact menu where that fancy "GCF" button on the paid-for version leads to, its none other than simply clicking on the IOTHIDDENMENU button that I can see on your screenshot as button #2 on the bottom list, there you will see a series of menu, I believe the one labeled"Testmode" or something like that from the big menu leads you exactly to the same spot (which is the "SERVICE MODE") as if you were to click on the "GCF" button fron the paid for version, there you can just continue to follow the instructions on that page as it will be exact, depending on many factor and firmware version you are running.
Now that you have access the SERVICE MODE (or in other words "GCF"'s target destination if you were using the paid-for version) You would go to [2] UE Settings & Info, then [1] Settings, then [1] Protocol, then [4] GCF (note: MAYBE the "GCF" button on the paid for version leads you directly to this spot, bypassing the other menu options directly, maybe yes, maybe no, but it doesn't matter, the point is that you made it there), then finally you would tap "[1] GSM/(E)GPRS/WCDMA GCF ON", you will see a confirmation that the command succeeded, and as per the instructions from your own device you shall reboot your device using the power buttons and then tap on "restart/reboot". Thats all. At least in my case that should be it for unlocking GSM bands, according for further research I did, the Sprint Galaxy S5 would only work in 3G mode because all the 4G LTE GSM bands are blocked and the ones aren't compatible with the AT&T network (which is the network that I plan to use very soon on this device), so to fix that predicament because I dont want to be stuck on 3G mode I downloaded QPST and QXDM, I had to downgrade my firmware to kit-kat thorugh ODIN (was a b*tch sourcing the original .tar image on the internet, most servers that used to have it no longer had the file and when I was finally about to give up and pay sammobile their $15 to be able to download it from their servers at a speed greater than 15 kbps I finally found a server that was still hosting the NE5 firmware for free!)
For my particular device, beginning on Lollipop Samsung took measures (on the kernel) to prevent users from having access to QPST/QXDM, installing a customer kernel would have given access to QPST/QSDM without having to downgrade firmwares, but the custom kernel that I needed was nowhere to be found, so my only option was to do the firmware downgrade and thanks God that I didn't have the stock Marshmallow bootloader because downgrading would have been impossible then (Samsung implemented a downgrade check - blocker for the S5 starting on Marshmallow) so I was running the BO6 bootloader/baseband, the last ones of the safe bootloader version that allows downgrades.
So anyways, on QPST I made sure that all the 3G bands that I needed for AT&T were indeed enabled, and on QXDM I enabled all LTE bands (thanks to someone who posted the string value to enable all LTE bands for GSM).
So hopefully, when my AT&T SIM card arrives on Thursday Oct 26 not only should I have 3G access, but I also should have 4G LTE access as well, and after my AT&T SIM card arrives I would finally put all this to a test, how effective all this was and most importantly, if this method for domestic GSM unlock really works for me.
Click to expand...
Click to collapse
Thanks for taking the time to type all of this out...I didn't have any luck getting this to work with TMobile, but it's possible I screwed up something in the process before I made it to the GCF settings. I tried to set the towers to GSM and register the phone on T-Mobile's network, but it just wouldn't register, and I never could get the "invalid SIM" to go away. No big deal; I had a Moto E4 that I bought from Amazon, so I figured by the time I returned the Moto and paid for the $35 I might as well just use the Moto.
Do you have the .zip file he sent you?
Honestly...best damn unlock service ive ever used...and ive used alot but for samsung devices, and mainly sprint devices, its instant, theres a live chat, and if theyre unavailable on live chat, if you leave a message they get back to so fast...i will use them every single time i can.
I have done this on my Not4 using idoneapps, you do not need another carrier sim to domestic unlock... When it is unlocked, pop in a sim from another carrier and your all set to go.
i got mine unlocked thru Ebay for around $8, the seller used GT tools i believe and it is successful. By the way, did you guys update ROM after unlocking? if yes what custom rom did you update?

Is it possible to unlock more LTE bands?

Hello, everyone! I was hoping maybe you could give me your opinion on the following issue:
About a year ago I purchased a Moto X Play XT1562 in Europe with dual sim support (Asian ROM). I knew beforehand that I'd probably have limited LTE coverage in my country (Argentina), since the bands used by carriers here are B4 and B28, and XT1562 only supports B28 (which is used mostly for coverage in suburbs and rural areas). Band 4 is the main band used in Argentina for LTE coverage in cities and XT1563 is the model that supports it.
For quite some time I've had the theory that most phones should support more bands than they show, and that the differences between various models of the same phone are there to introduce region restrictions, which in turns means that some LTE bands are disabled and that it should be possible to somehow enable them by tweaking the software. For what I've read, there seems to be some support for my theory: there's a thread in this very same forum which claims that it should be possible to unlock all LTE bands in devices with Qualcomm processors by rooting the phone, installing a custom ROM and kernel and changing a few values.
LINK: https://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
Now, I'd really want that to be the last thing I try. I've rooted my phone before and I even unrooted it by flashing stock ROM, so I know my way around, but flashing a custom ROM and kernel are things I'd rather not do right now.
So, that brings me to my second theory: since XT1562 and XT1563 are basically the same device, their hardware specifications are the same and only differ in the LTE bands they support... and since LTE bands seem to be software-restricted...
1) Could it be possible to unlock Band 4 by flashing XT1563 stock ROM to my XT1562 Moto X Play?
2) Has anyone tried to do that (even by mistake) without bricking the device?
3) If there's no option but to flash a custom ROM and kernel, does anyone know for sure if LTE bands in Moto X Play are software restricted? Or is there a hardware limitation?
Probably my secornd theory won't work because I don't think the solution would so simple, and there would be threads about it... but I guess I don't lose anything by asking
Thank you!! =)
Just realized this thread shouldn't go in General. Could someone please move it to Q&A? Thanks!
The frequency bands that your phone supports is region specific (as you guessed) and has legal implications. And just like your device IMEI, these values are found in the non-volatile memory of your phone. The values are basically on partitions that are much secure and not so easily editable (like by fastboot or recovery). But nevertheless, the values are "software" only, and so it must be possible to edit the values anyway (just like it is possible to edit the IMEI), one way of doing so is using Qualcomm software as in the link you had posted.
But this varies from device to device, vendor to vendor, so your second theory could actually work on our phones (really don't think so though).
While it might be possible to run ROMs for XT1563 on XT1562, the baseband/ modem for XT1563 would not work on XT1562; it would probably make your device show "unknown" for IMEI, and so you would get no SIM network. Flashing back the modem for XT1562 would probably fix it.
You could always try and find out...
You would need the NON-HLOS.bin and fsg.mbn files from the XT1563 stock image to try, and the same files from the XT1562 stock to revert back.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
There's chance that you would be stuck with an "unknown" IMEI and then you would have to manually edit volatile memory values after all. This all is just theory, someone who has tried or someone who has more knowledge will be able to help you better.
DragonClawsAreSharp said:
The frequency bands that your phone supports is region specific (as you guessed) and has legal implications. And just like your device IMEI, these values are found in the non-volatile memory of your phone. The values are basically on partitions that are much secure and not so easily editable (like by fastboot or recovery). But nevertheless, the values are "software" only, and so it must be possible to edit the values anyway (just like it is possible to edit the IMEI), one way of doing so is using Qualcomm software as in the link you had posted.
But this varies from device to device, vendor to vendor, so your second theory could actually work on our phones (really don't think so though).
While it might be possible to run ROMs for XT1563 on XT1562, the baseband/ modem for XT1563 would not work on XT1562; it would probably make your device show "unknown" for IMEI, and so you would get no SIM network. Flashing back the modem for XT1562 would probably fix it.
You could always try and find out...
You would need the NON-HLOS.bin and fsg.mbn files from the XT1563 stock image to try, and the same files from the XT1562 stock to revert back.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
There's chance that you would be stuck with an "unknown" IMEI and then you would have to manually edit volatile memory values after all. This all is just theory, someone who has tried or someone who has more knowledge will be able to help you better.
Click to expand...
Click to collapse
Thank you for your kind reply =)
So, if I understood correctly, there's no need to flash the full XT1563 stock image. I'd just have to flash those two files from XT1563 stock rom, and then if it doesn't work then I'd just flash the XT1562 files again, which I already have. Seems worth to try and with low risk of bricking my phone.
Now, if that doesn't work, then my only option would be to use the other method. I don't want to try that one yet because I don't have everything figured out: I'm stuck in step 6, "Open the USB settings screen on your phone." I haven't yet found the correct code to input in the phone's dial screen to edit USB settings. I think in Android 6 the USB options have all been moved to developer mode, but I'm not 100% sure yet.
floydian86 said:
Thank you for your kind reply =)
So, if I understood correctly, there's no need to flash the full XT1563 stock image. I'd just have to flash those two files from XT1563 stock rom, and then if it doesn't work then I'd just flash the XT1562 files again, which I already have. Seems worth to try and with low risk of bricking my phone.
Now, if that doesn't work, then my only option would be to use the other method. I don't want to try that one yet because I don't have everything figured out: I'm stuck in step 6, "Open the USB settings screen on your phone." I haven't yet found the correct code to input in the phone's dial screen to edit USB settings. I think in Android 6 the USB options have all been moved to developer mode, but I'm not 100% sure yet.
Click to expand...
Click to collapse
At step 6, you are basically trying to connect the phone to your PC in a vulnerable mode (Modem + Diag mode) so you could access the NV. On Moto phones this is not really possible by dialing a service code I think.
Did you try to boot your phone in BP tools (or QCOM?) mode from fastboot? Then connect to PC and it should be connected in diag mode (check in Device Manager to confirm). You might need some specific drivers, see last thread, or may be Google.
There is a lot of discussion about this on the internet (for other devices, mostly). Mostly because people with locked devices that work only on specific carriers use a similar edit of values in NV of the phone to get out unlocked.
I think you should Google and try out some of the things people have been suggesting.
Read here, post number 21, for example (the entire thread is pretty informative): https://forum.xda-developers.com/moto-x/moto-x-qa/unlock-lte-bands-moto-x-t2933475/
And here (for Moto X Play),
http://forum.xda-developers.com/moto-x-play/help/trouble-writing-nv-settings-moto-x-play-t3368261
Edit: Most of these NV and QPST threads do seem to repeatedly point out that writing on the NV is extremely risky.
DragonClawsAreSharp said:
At step 6, you are basically trying to connect the phone to your PC in a vulnerable mode (Modem + Diag mode) so you could access the NV. On Moto phones this is not really possible by dialing a service code I think.
Did you try to boot your phone in BP tools (or QCOM?) mode from fastboot? Then connect to PC and it should be connected in diag mode (check in Device Manager to confirm). You might need some specific drivers, see last thread, or may be Google.
There is a lot of discussion about this on the internet (for other devices, mostly). Mostly because people with locked devices that work only on specific carriers use a similar edit of values in NV of the phone to get out unlocked.
I think you should Google and try out some of the things people have been suggesting.
Read here, post number 21, for example (the entire thread is pretty informative): https://forum.xda-developers.com/moto-x/moto-x-qa/unlock-lte-bands-moto-x-t2933475/
And here (for Moto X Play),
http://forum.xda-developers.com/moto-x-play/help/trouble-writing-nv-settings-moto-x-play-t3368261
Edit: Most of these NV and QPST threads do seem to repeatedly point out that writing on the NV is extremely risky.
Click to expand...
Click to collapse
Thanks again!
So, I flashed the XT1563 modem files. It took me a while because when I unrooted my phone, I also locked the bootloader (I honestly don't know why I did it), so I had to unlock it again and of course make a back-up.
While at first it seemed that I'd be stuck with "unknown" IMEI just as you said, after a minute or so both sim cards started working. I still don't know if it worked, though, because I haven't yet seen the 4G sign on my phone, but I did notice a change: after flashing the files I started getting the H+ sign (H was the best I'd get before, both here and in Europe, even after flashing an XT1562 stock image). So, it wasn't a complete waste of time
It could be that LTE reception is just bad where I live, but I doubt it because other phones have 4G connection here. I'll see what happens tomorrow in another place, but but most likely I'll have to try with a custom image and kernel, so I'll take a look at the links you have provided.
EDIT: in Europe the best I'd get was 4G, of course. What I wanted to point out was that H was the best 3G connection I'd get anywhere.
floydian86 said:
Thanks again!
So, I flashed the XT1563 modem files. It took me a while because when I unrooted my phone, I also locked the bootloader (I honestly don't know why I did it), so I had to unlock it again and of course make a back-up.
While at first it seemed that I'd be stuck with "unknown" IMEI just as you said, after a minute or so both sim cards started working. I still don't know if it worked, though, because I haven't yet seen the 4G sign on my phone, but I did notice a change: after flashing the files I started getting the H+ sign (H was the best I'd get before, both here and in Europe, even after flashing an XT1562 stock image). So, it wasn't a complete waste of time
It could be that LTE reception is just bad where I live, but I doubt it because other phones have 4G connection here. I'll see what happens tomorrow in another place, but but most likely I'll have to try with a custom image and kernel, so I'll take a look at the links you have provided.
EDIT: in Europe the best I'd get was 4G, of course. What I wanted to point out was that H was the best 3G connection I'd get anywhere.
Click to expand...
Click to collapse
Dial *#*#4636#*#* (4636 stands for INFO) on dialer and you can select LTE only from network modes to force 4G detection. In this mode, it will pick 4G network (4G only, even if its weak), whenever it's available.
To really check supported bands by your phone, I think you would need to use the QPST app, it was possible earlier by *#*#SERVICE#*#*, the service menu. Maybe somewhere in *#*#2486#*#*?
Edit: I can think of two scenarios now. The sad one... while you flashed the XT1563 modem (that supports LTE Band 4, 8, etc. (values on the lower row, check attached), your NV still says it supports 19 and 8 and so on (not 4). This could mean you are now able to use only 8 (and the other common bands supported by the two variants) and neither of 19 or 4.
Or, Moto X Play decides which bands it supports depending only on the modem files, and you actually managed to get working LTE band 4 on your XT1562. .
DragonClawsAreSharp said:
Dial *#*#4636#*#* (4636 stands for INFO) on dialer and you can select LTE only from network modes to force 4G detection. In this mode, it will pick 4G network (4G only, even if its weak), whenever it's available.
To really check supported bands by your phone, I think you would need to use the QPST app, it was possible earlier by *#*#SERVICE#*#*, the service menu. Maybe somewhere in *#*#2486#*#*?
Edit: I can think of two scenarios now. The sad one... while you flashed the XT1563 modem (that supports LTE Band 4, 8, etc. (values on the lower row, check attached), your NV still says it supports 19 and 8 and so on (not 4). This could mean you are now able to use only 8 (and the other common bands supported by the two variants) and neither of 19 or 4.
Or, Moto X Play decides which bands it supports depending only on the modem files, and you actually managed to get working LTE band 4 on your XT1562. .
Click to expand...
Click to collapse
I did try to select LTE only, but it didn't work.
I also tried using service menu, but I didn't find any of the tests to be useful to check which LTE bands are supported.
About the scenarios you propose, I also thought maybe all I achieved was to restrict LTE bands to the ones supported by both models :S. At work my phone picks band 28, but both models support it, so there's no way to check it by discarding...
There's a third possibility, though, which is that both models' modems are exactly the same and bands are only limited by NV.
After work I'll see which custom roms and kernels are there for X Play and start studying the process to edit NV. Still it might not be possible to do so because the post claims that rom and kernels must be compiled from source code, so the ones made from stock won't work... That means I depend on there someone making a rom and kernels that meet those requirements.
In the second link, the person says he can't save the changes he makes to the NV, which is what is supposed to happen if you're using stock rom and kernel, according the link I've shared.
So, I ended up editing the NV in order to remove Band 4 restriction. It took me a while because I had to figure out how to bypass all the obstacles I found on the way but, once everything was set up, the process was quite simple.
I had to boot my phone in BP Tools mode and configure the QC Diag port driver correctly. Also, I had to use a newer version of QPST because the one I donwloaded first didn't work.
The tutorial claims that your phone must be rooted and that you need a custom rom and kernel in order to avoid the "anti-tamper" mechanisms in newer Qualcomm devices. My first approach was not to do such things (i.e.: unrooted phone with stock rom and kernel).
I edited the NV values as suggested in order to enable Band 4. The good news are that the custom values that I added didn't revert back to the original ones after I rebooted and also that I didn't brick my phone and it's working properly
Right after I rebooted my phone, it picked 4G signal, but after just a few seconds it switched to H. I forced my device to LTE only, and it connected to 4G, but then again it completely lost signal. My phone does pick LTE Band 28 sometimes, but not at my place, so I thought that I must have been picking up Band 4 (I tried to leave it set to LTE only, but it picked no signal at all).
Also, when I'm at work, it sometimes picks Band 28, but signal must be very weak because it never lasts more than a few minutes, after which goes back to H.
So far I'm not sure if the mod worked because I can't find a way to see which bands my phone currently supports or which LTE band it's connected to. I tried an app called LTE Discovery, but it labels it as "unknown band" (I suspect that my phone needs to be rooted in order for that feature to work).
Right now, I'm thinking of three possible things that could have happened:
1) The mod worked and LTE signal is just very poor by my place.
2) It worked and it connected to Band 4 for a few seconds, but then the anti-tamper mechanism detected that situation and software-blocked it (without reverting NV changes I made). In this case, I'll have to flash a custom kernel and see what happens.
3) There's a hardware limitation after all, in which case there's nothing I can do (I don't think this is the case)
Right now I'm at work and my phone has been picking up 4G for over an hour already. Since it usually only lasts a few minutes (connected to Band 28), then I guess there are reasons to be optimistic that it worked after all and it is currently using Band 4.
If I succeed, I'll open a new thread with a tutorial for Moto X Play.
I'll keep updating my progress on the issue in order to leave a record of everything I tried. Also, it could be helpful to other people who are trying to do the same thing or maybe someone who has done this before will see this and point me in the right direction . Again, if I succeed I'll write a more detailed guide.
I can confirm that what I did so far didn't work, I've modified the necessary NV values and even flashed Squid kernel, but still no success: I'm definitely not picking Band 4 anywhere, only Band 28.
While flashing the custom kernel, I also wanted to use the opportunity to root my phone, but for some reason I soft-bricked it in the process, so I had to flash XT1562 stock rom again (with XT1563 modem). This reverted the NV values to the default ones, so I had to customize them again.
The user fffft says that custom rom and kernel are needed in order to avoid the anti-tamper code, but also that it is most likely in the kernel. I could try another kernel, maybe Phoenix, but if that doesn't work either, then we can confirm that the anti-tamper code is actually in stock rom.
This leaves three final possibilities to succeed in unlocking LTE Band 4:
_Flashing another custom kernel
_Flashing a custom rom
_Flashing the whole XT1563 stock rom, as I proposed at first, and see what happens. If this works, this should both set the NV values to enable XT1563 default LTE bands (which includes Band 4) and also set a different anti-tamper code, which should not bother. Worst case scenario I'll soft-brick my phone again and I'll have to flash XT1562 rom.
Daily update:
First thing I tried yesterday was what I wanted to do from the beginning, which is to flash the whole XT1563 rom on XT1562. Kids, don't try that at home! At first it looks like it's working and that the device is going to boot normally, but then it gets stuck in the apps configuration screen or after the boot animation.
The only thing left now was to try with a custom rom, so I flashed Cyanogenmod 13 and Squid kernel. This, however, brought other issues: for some reason, when booting the phone in BP tools mode or Qcom, the device's QC Diag Port isn't detected by PC. It seems to be something implied to happen with custom roms: https://forum.xda-developers.com/moto-g-2014/help/diagnostic-mode-moto-g-flashing-cm-12-1-t3254756
Has this happened to any of you? Is there a way around it?
I also found this: http://www.howardforums.com/showthread.php/1692461-HTC-Evo-and-Cyanogenmod-Diagnostic-mode
There they mention that changes should be made on stock image and just then install the custom rom. That would mean to flash stock image, then change the required NV values, and finally install the custom rom.
That makes some sense, but unless I can find a way to enable Diag mode on Cyanogenmod, this will be the last thing I try and if it doesn't work then I'll give up
floydian86 said:
Daily update:
First thing I tried yesterday was what I wanted to do from the beginning, which is to flash the whole XT1563 rom on XT1562. Kids, don't try that at home! At first it looks like it's working and that the device is going to boot normally, but then it gets stuck in the apps configuration screen or after the boot animation.
The only thing left now was to try with a custom rom, so I flashed Cyanogenmod 13 and Squid kernel. This, however, brought other issues: for some reason, when booting the phone in BP tools mode or Qcom, the device's QC Diag Port isn't detected by PC. It seems to be something implied to happen with custom roms: https://forum.xda-developers.com/moto-g-2014/help/diagnostic-mode-moto-g-flashing-cm-12-1-t3254756
Has this happened to any of you? Is there a way around it?
I also found this: http://www.howardforums.com/showthread.php/1692461-HTC-Evo-and-Cyanogenmod-Diagnostic-mode
There they mention that changes should be made on stock image and just then install the custom rom. That would mean to flash stock image, then change the required NV values, and finally install the custom rom.
That makes some sense, but unless I can find a way to enable Diag mode on Cyanogenmod, this will be the last thing I try and if it doesn't work then I'll give up
Click to expand...
Click to collapse
On step 14 of the first post you shared, it says you could check the active bands on your phone. Do you see something useful there?
AFAIK, once you successfully edit the NV Memory, the changes are there to stay, even if you reflash stock ROM.
I can confirm one thing. BP tools + stock ROM gives you diag mode, but that doesn't work on AOSP based ROMs. And it seems not even on CM based ROMs. However it should be easier to do it on custom ROMs, try enabling and looking into Developer Options. Or may be some service code in phone app?
https://forum.xda-developers.com/showthread.php?t=1626638
On my phone running an AOSP based ROM, I have files that indicate a possible diag mode at /system/sys/class/Android_USB. Need to dig in more.
If you are not able to get your phone connect in diag mode successfully, the route I would now suggest is this:
1. Flash stock ROM (for XT1562)
2. Flash custom kernel
3. Root the stock ROM (use Magisk)
4. Edit NV Values, make sure it is successfully done (step 14 on the first post you shared?).
5. Check if its working.
6. Format /system, /data, and cache partitions, and flash ROM. So your baseband files (and ofc NV memory) is not affected.
7. Try again.
DragonClawsAreSharp said:
On step 14 of the first post you shared, it says you could check the active bands on your phone. Do you see something useful there?
AFAIK, once you successfully edit the NV Memory, the changes are there to stay, even if you reflash stock ROM.
I can confirm one thing. BP tools + stock ROM gives you diag mode, but that doesn't work on AOSP based ROMs. And it seems not even on CM based ROMs. However it should be easier to do it on custom ROMs, try enabling and looking into Developer Options. Or may be some service code in phone app?
https://forum.xda-developers.com/showthread.php?t=1626638
On my phone running an AOSP based ROM, I have files that indicate a possible diag mode at /system/sys/class/Android_USB. Need to dig in more.
If you are not able to get your phone connect in diag mode successfully, the route I would now suggest is this:
1. Flash stock ROM (for XT1562)
2. Flash custom kernel
3. Root the stock ROM (use Magisk)
4. Edit NV Values, make sure it is successfully done (step 14 on the first post you shared?).
5. Check if its working.
6. Format /system, /data, and cache partitions, and flash ROM. So your baseband files (and ofc NV memory) is not affected.
7. Try again.
Click to expand...
Click to collapse
Thanks!
When I edited the NV, the changes were saved (I closed QPST and QXDM, then rebooted my phone and checked the values). However, when I flashed stock rom, the values reverted to the original ones. I also thought that shouldn't happen, but nevertheless it did :S
About getting Diag mode on custom roms, I took a quick look at developer options but I didn't see anything useful. I read a few posts that claim it can be done using a terminal emulator, so there has to be a way around it.
The steps you mention are the ones I had in mind, except for rooting. Do you think it's really necessary? (phone will be rooted after flashing custom rom, anyway).
I'll try it tonight and see what happens =)
EDIT 1: If I understood correctly, step 14 of the thread I've shared is only for 3G bands, so I don't need to change anything there. LTE bands NV's can only be seen and modified using QXDM and that's where I checked if the changes were saved. However, I have seen that there are a few holes in the tutorial, some of which I had to figure out myself. Maybe there's one extra step I'm missing on QPST? Step 24 seems to indicate otherwise.
EDIT 2: I've found this thread. It's about a Lenovo phone, but chances are they are the same: http://www.teamsuperluminal.org/forums/topic/open-diag-port-in-cm-12-1-for-qpst/
This is what it says: "To open the diag port, connect the phone to a PC and use ADB:
adb shell
su
setprop sys.usb.config diag,adb"
Changing the NV and then flashing custom ROM didn't work (I deleted system, data and cache before but still didn't work).
I tried enabling diag mode using ADB with the code I found but it didn't work. No diag port gets enabled.
I'm ready to give up. It seems it can't be done, at least not on X Play
Unless maybe someone know how to use diag mode on Moto X play running Cyanogenmod?

GTI9505 - Lollipop - IMEI null/null

I'm not an Android developer but really stuck here. My IMEI is reporting null/null. I have rooted the phone and tried various tools to try and fix the problem. Nothing works so far. I've have replace the modem.bin but that hasn't fixed the problem. When I put the phone in diag mode it's not recognised by my PC - it comes up as unknown USB device. Updated to the latest Samsung drivers and that doesn't fix the problem. Most fixes I've seen involve fastboot but the I9505 doesn't support fastboot so that's no good. When I try Qualcom NV Tools it recognises the COM port but when I try and connect it reports 'Unable to send SPC to Phone' and 'Connection to Phone Lost'.
Any help appreciated.
You tried flashing the latest stock ROM with Odin?
audit13 said:
You tried flashing the latest stock ROM with Odin?
Click to expand...
Click to collapse
Thanks.
That was the first thing I tried... No joy. I've reverted to KitKat hoping that would do it - or at least let me try out some new lines of attack. I figured I could try NV reader/writer - but I hit the same problem with the SPC code. So for the moment I'm really stuck.
You may have to have the phone restored via jtag.
audit13 said:
You may have to have the phone restored via jtag.
Click to expand...
Click to collapse
I was hoping for something less extreme...
In Qualcomm NV Tools via EFS Pro there's an IMEI read/write option. But to unlock this I need a diagnostics pass code. Where does this come from? Is this specific to my phone or something specific to the model?

Categories

Resources