Database Develop

Metro flashed Diamond trouble

alright guys still can't get this damn thing to work. I somehow have the last off digit incorrect on my phone number. I found this out when I tried to call my voice mail . So I assume this could be part of my problem . So I dial ##778# and go in to edit mode and try to fix the phone number. I go through and edit the incorrect number on everything I saw that had it. Then saved the settings and the phone restarts and when it does it sets everything back. . So I tried the Gaurdian removing cab file with no luck . Still can't edit my nam settings. So I took to my Metro guy who tried everything he could he even reflashed it with Houdini and still no luck. I know someone here knows what is causing this.

Have you read this:
http://www.howardforums.com/showthread.php?t=1443845
If not, I would start there.

mr.horndoctor said:
Have you read this:
http://www.howardforums.com/showthread.php?t=1443845
If not, I would start there.
Click to expand...
Click to collapse
Yes I have read that thread . Thanks

happens to a lot of people.
http://forum.xda-developers.com/showthread.php?t=645799

I figured it out lastnite. Had to flash back to the stock Sprint rom then edit all the settings to get them to stick. Then flashed back to a custom rom and all is good now .

Sprint HTC One flash to Boost Mobile

I can confirm through my own personal experience that the "open sesame door" method works on this phone just as it does on every other Sprint HTC phone. I've already used it to get the first step out the way & I am now having a hard time getting this phone to perform an OTA, a PRL Update & a Profile Update in spite of correctly programming NV Items 465, 466, 1192 & 1194 to the phone. It appears that Sprint has something to do with blocking OTAs, PRL Updates & Profile Updates on its newer LTE phones when flashed. Anyone has any thoughts on how to solve this problem?

Ok, so I've fully flashed my Sprint HTC One to Boost Mobile, but I had to go about doing so manually. Just like the Sprint Note 2 & the Sprint Galaxy 4, I cannot get the phone to activate OTA, I cannot perform PRL & Profile Updates, and I encounter a nagging Activation screen whenever I reboot the phone. Whatever system that Sprint has put into place on these newer phones to interfere with them doing updates really blows!

How did you go about doing it manually? I'm using DFS, how about you?

rbrown24 said:
How did you go about doing it manually? I'm using DFS, how about you?
Click to expand...
Click to collapse
Use the "open sesame door" method to change your you know what on your HTC One. From there, activate your donor phone on the Boost account that you want your HTC One to work on & program the donor phone with your account's information. From there, extract NV Items 465, 465_1, 466, 466_1, 1192 & 1194 from the donor in whatever way works best for you and program them to your HTC One with your phone flashing program of choice. Just like the Galaxy 4, this phone will bring up a nagging activation screen if you don't flash it while it's on an active Sprint account, and just like the HTC EVO LTE, this phone will not perform PRL & Profile Updates whatsoever, so forget about it lol.

Thanks for the quick reply. I understand the open sesame door and all. But how do I program the 465, 465_, etc into the HTC. I have always used dfs and wrote profile 0 manually then done the ota update to get profile 1. Obviously this will not work for the htc one. What program/method did you use? I've read about qxdm but couldnt get it to install on my windows 7.

Joey
RioSoul said:
I can confirm through my own personal experience that the "open sesame door" method works on this phone just as it does on every other Sprint HTC phone. I've already used it to get the first step out the way & I am now having a hard time getting this phone to perform an OTA, a PRL Update & a Profile Update in spite of correctly programming NV Items 465, 466, 1192 & 1194 to the phone. It appears that Sprint has something to do with blocking OTAs, PRL Updates & Profile Updates on its newer LTE phones when flashed. Anyone has any thoughts on how to solve this problem?
Click to expand...
Click to collapse
Did you try the S3 method. No need to flash files. The lte radio ota's the needed info to the phone. Just reset the phone to handsfree activation and set up your wifi to connect before allowing to run. It should do everything on its own once on wifi. How did you access your 0 and 1943 files? I tried and the "open sesame door" worked but couldn't find 0 or 1943, and it wouldn't let me just write them in.

rbrown24 said:
Thanks for the quick reply. I understand the open sesame door and all. But how do I program the 465, 465_, etc into the HTC. I have always used dfs and wrote profile 0 manually then done the ota update to get profile 1. Obviously this will not work for the htc one. What program/method did you use? I've read about qxdm but couldnt get it to install on my windows 7.
Click to expand...
Click to collapse
You can use whatever program works best for you so long as the appropriate information makes it way into your phone. 465 = the NAI from Profile 0, 465_1 = the NAI from Profile 1, 466 = the AAA Shared Secret & HA Shared Secret passwords for Profile 0, 466_1 = the AAA Shared Secret & HA Shared Secret passwords for Profile 1, 1192 = the HDR AN Long password, 1194 = the UID for the HDR AN Long.

Joey, If you are using qpst and dont see 0 and 1943, try using and updated version. This happened to me but when I upgraded to the latest version it worked like a charm.
--------------------------------
Okay. So could I just extract those files from my donor then use the efs explorer to paste them to my htc? Dfs is having me manually enter these fields and I dont think everything is writing correctly because I have talk and text with no data. What program are you using? I wanna use qxdm like everyone else but it gives me trouble on installation with windows 7

im sure there is no lte on this phone for boost right?

DruoGaby said:
im sure there is no lte on this phone for boost right?
Click to expand...
Click to collapse
That is correct.

Hey Rio, which version of QPST are we supposed to use..i keep getting error 264 trying the open sesame hack...im supposed to right click it and add new directory right?
i tried QPST 402 378 & 366 so far
EDIT: nevermind...its been awhile...root directory duh lol

12manytimes said:
Hey Rio, which version of QPST are we supposed to use..i keep getting error 264 trying the open sesame hack...im supposed to right click it and add new directory right?
i tried QPST 402 378 & 366 so far
EDIT: nevermind...its been awhile...root directory duh lol
Click to expand...
Click to collapse
Lol yeah, the root directory bro lol, but I use QPST 378. Anyhow, let me know how things are looking with your HTC One when you're done flashing it

joeynreggie said:
Did you try the S3 method. No need to flash files. The lte radio ota's the needed info to the phone. Just reset the phone to handsfree activation and set up your wifi to connect before allowing to run. It should do everything on its own once on wifi. How did you access your 0 and 1943 files? I tried and the "open sesame door" worked but couldn't find 0 or 1943, and it wouldn't let me just write them in.
Click to expand...
Click to collapse
What should happen and what does happen are two entirely different things. The S3 hands free activation method does not work on this phone. Flashing this phone is for advanced flashers who know how to do more than just program Profile 0 and the corresponding AAA Key. If you can't locate NV Items 0 & 1943, you must be using an old version of QPST, but I have copies of NV Items 0 and 1943 stored on my computer which are already zeroed out that I program to every Sprint HTC phone that I flash, so I never pay attention to whether I see the files within the NVM folder, and I don't have to zero them out each time I flash a phone.

Ok so last night I changed the u know what and it did..this morning I tried it again and it keeps failing on step 2 ive factory reset the phone dropped the open sesame hack again and still nothing..any ideas rio?
EDIT EDIT EDIT LOL
sorry Rio!! Another false alarm!!
Sent from my SPH-L720 using Tapatalk 2

Same here ... i finally got to mess around ... and everything went good ... 3g/talk/text ....

Cdma ws works on this phone i've used the htc dev method before but with cdma is much quicker can i or it won't work?

mocoyombiflash said:
Cdma ws works on this phone i've used the htc dev method before but with cdma is much quicker can i or it won't work?
Click to expand...
Click to collapse
It wont you have to use qpst ...

Okay, I am dumbfounded... Any help, suggestions, ideas, solutions, theories, or just a shot in the dark will help!! AND better yet, I am not totally sure that this issue is pertaining to the flash at all but this is where I am starting.
I fully flashed the HTC One M7_WLS to boost mobile (no sim) with 3g and all the other goodies, my problem is that all of the sudden people only hear static when I answer the phone or call them. I have even tried speaker phone and the same applies. My reception bars are at 3-4. I ran a stock RUU to see if it was a problem with the software or something but the problem remains. I am S-off hboot 1.44 and radio 1.00.20.0315 software version is 1.29.651.10 stock right now.
Thanks in advance for any help.

FineTune123 said:
Okay, I am dumbfounded... Any help, suggestions, ideas, solutions, theories, or just a shot in the dark will help!! AND better yet, I am not totally sure that this issue is pertaining to the flash at all but this is where I am starting.
I fully flashed the HTC One M7_WLS to boost mobile (no sim) with 3g and all the other goodies, my problem is that all of the sudden people only hear static when I answer the phone or call them. I have even tried speaker phone and the same applies. My reception bars are at 3-4. I ran a stock RUU to see if it was a problem with the software or something but the problem remains. I am S-off hboot 1.44 and radio 1.00.20.0315 software version is 1.29.651.10 stock right now.
Thanks in advance for any help.
Click to expand...
Click to collapse
Considering that you flashed your phone correctly, it sounds like what you are experiencing is a network problem. You might want to check and see if Sprint (Boost) is working on towers in your area.
Sent from my SPH-L710 using xda app-developers app

Flash HTC One
RioSoul said:
Ok, so I've fully flashed my Sprint HTC One to Boost Mobile, but I had to go about doing so manually. Just like the Sprint Note 2 & the Sprint Galaxy 4, I cannot get the phone to activate OTA, I cannot perform PRL & Profile Updates, and I encounter a nagging Activation screen whenever I reboot the phone. Whatever system that Sprint has put into place on these newer phones to interfere with them doing updates really blows!
Click to expand...
Click to collapse
Can you you help me >> I want get my MSL on Sprint HTC ONE ?
thank you

##778# no longer working for PRL update in 4.4.2 KitKat???

I did the KitKat update yesterday. I'm stock, S-OFF with FireWater and rooted (verified by RootChecker). I made the change ro.build.type=dev in /system/build.prop. The change remained over reboot. I also have developer options enabled. I dialed ##778#, as listed in the FAQ, but nothing happens. I've used ##778# to change the PRL on my EVO 4G LTE, but I actually never tried it on the ONE to see if it worked prior to the KitKat update. ##3282# will bring up EPST and prompt for MSL if "Edit" is chosen, but the menus that come up don't seem to have any options to change PRL.
Any suggestions on what to do? Is there anything else that needs to be changed? Cache wipe or something?? I did a lot fooling around on the EVO 4G LTE before I got the PRL change to work, including installing an EPST.apk at one point, but I don't know if that acutally did anything. I think my issues were due to initially being S-ON with hboot 2.09, and fixed when I went to S-OFF.
Thanks!

jbhtexas said:
I did the KitKat update yesterday. I'm stock, S-OFF with FireWater and rooted (verified by RootChecker). I made the change ro.build.type=dev in /system/build.prop. The change remained over reboot. I also have developer options enabled. I dialed ##778#, as listed in the FAQ, but nothing happens. I've used ##778# to change the PRL on my EVO 4G LTE, but I actually never tried it on the ONE to see if it worked prior to the KitKat update. ##3282# will bring up EPST and prompt for MSL if "Edit" is chosen, but the menus that come up don't seem to have any options to change PRL.
Any suggestions on what to do? Is there anything else that needs to be changed? Cache wipe or something?? I did a lot fooling around on the EVO 4G LTE before I got the PRL change to work, including installing an EPST.apk at one point, but I don't know if that acutally did anything. I think my issues were due to initially being S-ON with hboot 2.09, and fixed when I went to S-OFF.
Thanks!
Click to expand...
Click to collapse
From what I can tell ##778# does not work on stock no matter what changes you make (changing from user to dev or flashing the modded EPST) I have tried, never got it to work on stock.
There is a modded EPST.apk floating around the general section that will work on a custom rom if you change the ro.build=dev

BD619 said:
From what I can tell ##778# does not work on stock no matter what changes you make (changing from user to dev or flashing the modded EPST) I have tried, never got it to work on stock.
There is a modded EPST.apk floating around the general section that will work on a custom rom if you change the ro.build=dev
Click to expand...
Click to collapse
Is that your experience as well on the EVO 4G LTE? I am stock on the EVO 4G LTE, and did manage to get it to work there.

jbhtexas said:
Is that your experience as well on the EVO 4G LTE? I am stock on the EVO 4G LTE, and did manage to get it to work there.
Click to expand...
Click to collapse
I just updated my Evo 4G LTE to 4.3 last week and it would not work on a stock rom.
Something changed with both devices once they hit 4.3 (no longer able to use ##778# on stock)

BD619 said:
I just updated my Evo 4G LTE to 4.3 last week and it would not work on a stock rom.
Something changed with both devices once they hit 4.3 (no longer able to use ##778# on stock)
Click to expand...
Click to collapse
Thanks for the update. I haven't done the 4.3 stock update yet on my EVO 4G LTE

Would the CDMA workshop method for changing PRL work on the stock 4.4.2? If there's a reasonable chance it should, I can round up the files and give it a try...

jbhtexas said:
Would the CDMA workshop method for changing PRL work on the stock 4.4.2? If there's a reasonable chance it should, I can round up the files and give it a try...
Click to expand...
Click to collapse
I could never get the drivers to install...so not sure

chas posted the hacked epst for kitkat.... http://forum.xda-developers.com/showthread.php?t=2517223

BD619 said:
I could never get the drivers to install...so not sure
Click to expand...
Click to collapse
From Device Manager (and I was doing this on XP), it looks like the HTC diagnostic port has a Device ID of USB\VID_0BB4&PID_0FAB&MI_03. I found several versions of posted HTC diagnostic drivers, and checked the .inf file with the driver, but none of them supported a "model" matching this device ID (in particular, the bolded part). IT looks like a newer set of diagnostic drivers is needed...

O.M.J said:
chas posted the hacked epst for kitkat.... http://forum.xda-developers.com/showthread.php?t=2517223
Click to expand...
Click to collapse
Just for reference, I tried both of the EPST zips in that post with the stock ROM, but neither of them worked.

jbhtexas said:
Just for reference, I tried both of the EPST zips in that post with the stock ROM, but neither of them worked.
Click to expand...
Click to collapse
how are u installing on a stock ROM? it does work...

O.M.J said:
how are u installing on a stock ROM? it does work...
Click to expand...
Click to collapse
Copy KK_EPST.zip to sdcard
Boot to TWRP, press "Install", and select KK_EPST.zip
After install completes, press "Wipe Cache/Dalvik"
Reboot

I believe there is a solution to the problem of getting diagnostic drivers installed for the ONE. My wife has the ONE at work, so I can't test that right now, but I played around a bit with my EVO 4G LTE, for which I also previously could not get the diagnostic drivers installed. I added a line to the [Models] section of the driver's htcdiag.inf file that matched the Device ID obtained from Device Manager as described in my post above. This allowed the diagnostic driver to install, and I was able to access the EVO 4G LTE, and successfully send the MSL from CDMA Workshop. That's all I had time for this morning.
Again, this testing was done on the EVO 4G LTE, but since it seems that this driver is just installing some kind of USB serial port, it seems reasonable that it should work with the ONE as well; I will try the ONE tonight and report back.

I was able to get a PRL downloaded to the HTC ONE with the KitKat 4.4.2 stock ROM from CDMA Workshop. In order to do so, it was necessary to make a small change to the htcdiag.inf file that is part of the HTC Diagnostic driver. This change is described below. I was working with Windows XP SP3 32-bit. The procdure can probably be adapted to Windows 7. You will need CDMA Workshop (trial edition works) and a set of HTC diagnostic drivers. I would recommend making a backup of the phone and the htcdiag.inf file.
PLEASE NOTE THAT YOU USE THIS PROCEDURE AT YOUR OWN RISK. WORKING WITH CDMA Workshop CAN POTENTIALLY DAMAGE/BRICK YOUR PHONE IF YOU ARE NOT CAREFUL. INSTALLING FAULTY DRIVERS MAY DAMAGE YOUR WINDOWS INSTALLATION. YOU ARE RESPONSIBLE FOR ANY DAMAGE TO YOUR EQUIPMENT.
1. Dial ##DIAG# (##3424#) on the HTC ONE, and select "YES" to enable diagnostic mode. If you a trying this on a different phone or different ROM, diagnostic mode may already enabled after dialing ##DIAG#. This should cause Windows to present several prompts for installing drivers. Cancel all of these requests.
2. After this, open Device Manager, and you should find the "unkown" devices shown in the attached image xd1.png. The HTC ONE presents two devices "HTC DIAG" and "HTC 9K DIAG". For the ONE, I could only get "HTC 9K DIAG" to work. For the EVO 4G LTE on Android 4.4.1, only the "HTC DIAG" device is presented, and it does work.
3. Right-click on the "HTC 9K DIAG" device, select "Properites", and then the "Details" tab. You should see something similar to what is shown in attachment xd2.png. Note the part of the Device Instance ID inside the red box.
4. Find the htcdiag.inf file in your set of HTC diagnostic drivers. In my driver set, this file was located in the "Win x86" foler. The version of my driver is shown in attachment xd3.png.
5. Locate the [Strings] section of the inf file, as shown in attachment xd4.png. Note the variable assigned to "HTC Diagnostic Interface" . In the case of this inf file, that variable is "OEMDevice02".
6. Locate the [Models] section of the inf file, as shown in attachment xd5.png. Find a line in this section that begins with the variable identified in step 5. Copy this line to a new line in the [Models] section. Modify the Device Instance ID portion of the copied line to match the portion of the Device Instance ID inside the red box as described in step 3. Save the inf file.
7. Right-click on the "HTC 9K DIAG" device in Device Manager and select "Update Driver..." The steps below may vary a bit, but ultimately you want to get to the point where you can select the htcdiag.inf file modified in step 6.
6a. Select the "Install from a list or specific location (Advanced)" radio button, and click"Next"
6b. Select the "Don't Search. I will select the driver to install" radio button, and click"Next"
6c. Select "Show All Devices" in the listbox and click "Next"
6d. Select the "Have Disk" button and click "Next"
6e. Select the "Browse" button, locate and select the htcdiag.inf file modified in step 6, and click "Open"
The driver should now install if the inf file has been correctly modified. You will have to ignore the complaints about the driver being unsigned.
7. After the driver is installed, you should see an "HTC Diagnostic Interface" in Device Manager's "Ports" tree, as shown in attachment xd6.png. The "(COMx)" portion indicates the port that will be used with CDMA Workshop. From this point, the procedure documented at http://forum.xda-developers.com/showthread.php?t=1673490 can be used to load the PRL of your choice. Be sure to reboot the phone after installing the PRL.
This worked for me. Given the fickle nature of computers, it may or may not work for you. Thanks!

*#*# not working

Anyone able to get into the hidden menu using *#*#4636*#*# ? I could have sworn it worked not to long ago, but there is something I want to check there, and when I do it, the USSD Code Running pop up shows up, the circle spins, then it goes away. Running newest MM, unlocked bootloader with TWRP, but thats it. Not rooted at all. I did update the Google Dialer not to long ago (before it was pulled, then reposted on the PlayStore), could that have something to do with it, or do I need to be rooted?

its *#*#4636#*#*, do it right and it should work. amyways, i use an app for that instead. btw, just checked, it still works

grumbles...yep I just typed in the wrong code..I even researched the heck out of it before posting here!! Thank you!

Tower1972 said:
grumbles...yep I just typed in the wrong code..I even researched the heck out of it before posting here!! Thank you!
Click to expand...
Click to collapse
:angel:

Problems with new Droid Turbo in UK - help needed please

Hi
Newbie here
I bought a new 'unlocked' Droid Turbo from a Chinese ebay seller with good feedback.
When I set it up it seemed ok, and picked up a 3G signal on my UK carrier network (no 4G LTE here).
The signal seemed weaker than my existing (old) device, so I went into settings and tried a few changes (from Global to the other options etc)
The signal didn't seem to improve, so after a bit of Googling I downloaded an app called Network and tried a few setting changes,
Anyway, you guessed it I can't get a signal at all now, even after a factory reset
Can anyone offer me any simple help as to what I should do?
Is it useless now?
Thanks in advance

monkey-prince said:
Hi
Newbie here
I bought a new 'unlocked' Droid Turbo from a Chinese ebay seller with good feedback.
When I set it up it seemed ok, and picked up a 3G signal on my UK carrier network (no 4G LTE here).
The signal seemed weaker than my existing (old) device, so I went into settings and tried a few changes (from Global to the other options etc)
The signal didn't seem to improve, so after a bit of Googling I downloaded an app called Network and tried a few setting changes,
Anyway, you guessed it I can't get a signal at all now, even after a factory reset
Can anyone offer me any simple help as to what I should do?
Is it useless now?
Thanks in advance
Click to expand...
Click to collapse
If that app made any changes to the system partition (the OS, basically), a factory reset will not fix it. If you want to get the stock, unmodified software back on it, you can try following section 0, steps 4-13 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.

TheSt33v said:
If that app made any changes to the system partition (the OS, basically), a factory reset will not fix it. If you want to get the stock, unmodified software back on it, you can try following section 0, steps 4-13 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
Click to expand...
Click to collapse
Thanks for the help, I'm downloading them now. Is it a relatively risk-free process, if I follow the instructions to the letter?

monkey-prince said:
Thanks for the help, I'm downloading them now. Is it a relatively risk-free process, if I follow the instructions to the letter?
Click to expand...
Click to collapse
Yes. If you want to make the process even more automated, you could install the Verizon Upgrade Assistant (that annoying popup you get every time you plug your phone into a computer) and select the "repair" option. That will do the same thing as this.

TheSt33v said:
Yes. If you want to make the process even more automated, you could install the Verizon Upgrade Assistant (that annoying popup you get every time you plug your phone into a computer) and select the "repair" option. That will do the same thing as this.
Click to expand...
Click to collapse
Many thanks for the super quick and helpful reply, I'll report back when I'm done in case it's of use to others

TheSt33v said:
Yes. If you want to make the process even more automated, you could install the Verizon Upgrade Assistant (that annoying popup you get every time you plug your phone into a computer) and select the "repair" option. That will do the same thing as this.
Click to expand...
Click to collapse
I tried to install the upgrade assistant, and it seemed to install ok, but there's no icon on the desktop or anything under apps (windows 10)
It does appear in the uninstall programs page in settings though.
I then tried the first method, but couldn't extract directly to the folder (error message came up) so I extracted to a folder on the desktop then dragged the contents into the correct folder and double clicked the batch file.
The phone is now showing the battery level, and the command box on the laptop screen is showing 'waiting for device'
Am I on the right tracks, or am I making newbie errors and I should get back in my lane?

Following the steps (as you suggested) has worked perfectly - thanks again.
I appreciate the ultra quick help from across the pond

monkey-prince said:
Following the steps (as you suggested) has worked perfectly - thanks again.
I appreciate the ultra quick help from across the pond
Click to expand...
Click to collapse
Happy to help! God save the queen, and all that.