Related
Hi guys,
This is all about developing the Focus S, since we are on our own on this one I thought id start the ball moving but it would be great if others can help, my first target is to try and download as much of the device as possible
Can I promise anything at all? nope
Have I achieved anything yet? well id say 1 step above doing nothing at all, if you can call that progress then yes, there is progress
Is it even possible to do anything? i dunno
Could i brick my device? possibly, i honestly don't know
in short, this is me blindly wondering in the dark with absolutely no direction what so ever!
So what have i done, well, i managed to get the Focus S talking to Qualcomms diagnostic utility, QPST and RevSkills CDMA Workshop
I cant get QXDM to install on Win 8 x64 and im not sure we need that one anyway
it is possible to edit stuff on the phone at a very low level, NOT OS level, it should be possible to download the various images on the phone, but ive yet to have any luck with that, it keeps coming up with "Arm9 fatal error"
ive been able to download and backup various phone settings but this is still outside of the OS#
I can play about with the EFS but there are several folders that i cant get in to yet
So far,both the samsung download mode and the ARM9 (?) download mode IS visible and installes as a com port, but there is no response on that port, i can only get a response within windows when i enable USB diag mode....
i decided not to link to the various tools ive mentioned here, i dont know the legalities of it all so use google, they are all easy to find.
Samsung studio 3 drivers
http://downloadcenter.samsung.com/c...813082717640_Samsung_USB_Driver_Installer.exe
Install it with compability for windows vista.
Samsung Focus info (note that most of this doesn't work, its for the older focus but some does)
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Focus
Handy Diagnostic codes
*#7284# - USB Path control (select to change how your phone communicates with your computer)
*#197328640# - The Root Menu (seriously, don't get too cocky, you could bugger up your device)
Samsung USB Download mode
Turn off Device
hold the camera button and the Volume UP
Whilst holding those two push and hold the power button until it vibrates
Samsung Device Hard reset
Turn off Device
hold the camera button and the Volume Down
Whilst holding those two push and hold the power button until it vibrates
Follow on screen instructions
Enable Diagnostic mode and Connect to QPST or other GSM/CDMA software
Download and install the Samsung drivers above
open the diagnostic app and dial code *#7284#
Select Modem,USB Diag
Reboot
When you plug the phone in you should see a COM port install and appear in device manager
load QPST configuration
Click on the Ports Tab then Click add new port
Select your Phone com port
Click OK then select the phone from the list, hit enable
Click on start clients then you can play with a bunch of options
Please note that this is a serious piece of kit, its designed for low level editing, what I mean by that is that it couldn't care less about if it works or not after you finish playing, a couple of other software options to play with are CDMA tools and RevTools both have the potential to paperweight your phone!
NOTE: Zune will not connect and whilst connected to PC you may lose all GSM connectivity whilst connected as well.
Enable FTM (Factory Test Mode)
open Diagnostic app and dial code*#197328640#
select 6 (common)
Select 1 (FTM)
Select 1 (on)
Click return save (it doesn't always persist unless you do)
Hit Back until you back to the main menu then win key to Windows
REBOOT to enable
NOTE: You will lose ability to connect to GSM with this enabled, a reboot is required to enable it after its set and to deactivate it, ive not found a noticeable difference with this on
If im not wrong, WP uses arm v7.
Good luck with this, it would be nice to see a 7.8 ROM on this device before I go buy the ATIV.
tayfelix said:
If im not wrong, WP uses arm v7.
Click to expand...
Click to collapse
yes your right, but that's what it says, it reboots in to some sort of QC download mode, QPST is the waiting for it to talk to it which it doesn't do, it just sits there with this error message.
I have been able to backup the Important bits that make the phone work, and I have access to the EFS, I can change all sorts at a very low level but any time I try and download some of the various "partitions" it reboots to this special download mode. because we don't have any form of ROM I thought the first priority should be to see if we can make a backup of it, outside of MS encrypted zune backup I mean
the software is old so perhaps it doenst work with newer hardware, but then it does with android soooo.....
LudoGris said:
Good luck with this, it would be nice to see a 7.8 ROM on this device before I go buy the ATIV.
Click to expand...
Click to collapse
don't hold your breath, I still don't really know what im doing, consider this playing.....in a mine field
Hmmm. If this does work. Will it ever work on focus flash/ omnia w? Cuz it got the same spec except different screen sizes
tayfelix said:
Hmmm. If this does work. Will it ever work on focus flash/ omnia w? Cuz it got the same spec except different screen sizes
Click to expand...
Click to collapse
That depends what you mean by work, will the focus flash connect to various diagnostic tools? yes probably, will it be possible to download the ROM? maybe, beyond that I haven't got a clue
starting to run out of ideas, I think either the download mode via QPST is disabled or, and more likely, the driver isn't correct, when it enters the arm9 fatal error screen it is still using same driver, the same driver samsungs download mode uses, but both won't talk to QPST unless I enable diagnostic mode within windows phone OS, the prob with that is that it won't then allow access to the file systemSent from my fake Lumia 900 using XDA Windows Phone 7 App
It also have diagnostic tools .
tayfelix said:
It also have diagnostic tools .
Click to expand...
Click to collapse
be careful, you can bugger up your device!i will write a more detailed guide later
First things first, you will need to make sure you have the samsung diagnostic tool install
bring up the phone dialer and dial
##634#
you will now see a diagnostic app on your app list, run it and type in
*#7284#that will enable you to change the USB connection mode,select
Modem USB diag
OPTIONAL - Typing in the following code will bring up the diagnostic root menu
#197328640#you can find a full list Here Many of the codes on that list just run functions found in the root menu
Bare in mind that pissing around with some of the things in there will bring about a swift crappy end to your day!
plugging in your your phone at this point will install a Samsung COM driver
next download and install QPST on your computer, run the config part of that, it will ask you to select your phone, you will need to add a com port, it should then list your phone to connect to it
you can then edit the EFS, service/phone settings, download settings
you will need to know your SPC number, mine was already 0000000, there are ways of working out your number if leaving it all at zeros doesnt work.
use the service editor to read the phone settings, it will ask for your SPC, once loaded,you can save those settings to a file, very important ifyou screw something up
Cool, I will try it when I'm free. Hmm what's UR focus s BOOTLOADER, firmware version and diagnostic version ?
tayfelix said:
Cool, I will try it when I'm free. Hmm what's UR focus s BOOTLOADER, firmware version and diagnostic version ?
Click to expand...
Click to collapse
as reported in windows phone about screen, note that the Focus S and Omnia 7, has a firmware update that will stop any interop unlocking, i had it installed but it killed my battery life and my phone reception so i took it off, id suspect the bootldt vs will be different between devices, even though they were released at the same time
bootldr 6.5.16.0
firmware 2103.11.10.1 (not the Samsung update that breaks interop)
diagnostic 0923 (not the Samsung update that breaks interop)
Er it's focus, focus s , focus flash/omnia w and omnia 7 that are affected by the freakin update. This is my version from the about info
Firmware: 2424.12.04.1
Bootloader: 6.4.4.0
Diagnostic : 1109
Note : I cant interlop unlock my omnia as Samsung fixed the exploit in the new firmware version
How did u remove the firmware ?
tayfelix said:
Er it's focus, focus s , focus flash/omnia w and omnia 7 that are affected by the freakin update. This is my version from the about info
Firmware: 2424.12.04.1
Bootloader: 6.4.4.0
Diagnostic : 1109
Note : I cant interlop unlock my omnia as Samsung fixed the exploit in the new firmware version
How did u remove the firmware ?
Click to expand...
Click to collapse
I made a backup before I installed it
I think we can get an xap of my version of the diagnostic tools, but the firmware update also changes drivers an a few other things, those cant be changed, if we could send custom cabs to the device we are laughing, but we cant, to cab send requires the cab to be signed, and the device would need to have that certificate, which cant be put on whilst its all in use
:S don't think so as diagnostic tool is based on firmware I think.
tayfelix said:
:S don't think so as diagnostic tool is based on firmware I think.
Click to expand...
Click to collapse
try this, remove your existing diagnostic app and install this xap
How can u install a xap..
Is your device still unlocked? The Samsung update will stop you applying the unlock but if you had it already installed it will still work, if it is unlocked then use an cap deployed, my link to the wee guide details how to do it, if it's interop unlocked but you can't install an xap deplorer the use the xap deplorer included with the WP SDK
Sent from my Lumia 900 using XDA Windows Phone 7 App
it's ok. I will just wait for someone to be able to unlock the device as I already got the exploit for interlop unlock patched
tayfelix said:
it's ok. I will just wait for someone to be able to unlock the device as I already got the exploit for interlop unlock patched
Click to expand...
Click to collapse
well there isn't anyone working on unlocking it as far as I know, so if its going to happen then we need to do it ourselves.
Ive exhausted just about every avenue I can think of getting access to the device, ive been able to dump parts of the RAM but still not the ROM,
EFS is writable but I cant get in to the secure folders. The only way I can think of for getting the ROM is to get it working in one of the two download modes, both will not talk to anything tho, perhaps if I had the commands to copy the ROM I could just send them in the hope it will reply but it sure as hell isn't saying anything to the commands I have sent.
Hmmm. Must there be a exploit? Zzz there's are very little/no hackers having a focus s or a focus flash/omnia w. they all have 1st gen devices I think.
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
I've installed all kinds of motorola drivers including the one that the device manager from motorola website, still I cannot read the qc diag serial port. Does anyone have these drivers?! I'm working on sim unlocking the sprint moto x and I gotta be able to get into the modem and see what I'm dealing with. Get me usb serial access to issue QC commands and hopefully I'll be able to post instructions for simunlock and cricket/metropcs flash (that opens up pretty much every carrier except verizon for the sprint model). I wont know until I can qxdm to it, I wish I had a radiocomm version that supported the msm8960 but the version I have goes up through the 6x00 not even close. I still think I can get done what I need to do with qxdm.
Thanks in advance.
+1,did you find then?
thundercles said:
I've installed all kinds of motorola drivers including the one that the device manager from motorola website, still I cannot read the qc diag serial port. Does anyone have these drivers?! I'm working on sim unlocking the sprint moto x and I gotta be able to get into the modem and see what I'm dealing with. Get me usb serial access to issue QC commands and hopefully I'll be able to post instructions for simunlock and cricket/metropcs flash (that opens up pretty much every carrier except verizon for the sprint model). I wont know until I can qxdm to it, I wish I had a radiocomm version that supported the msm8960 but the version I have goes up through the 6x00 not even close. I still think I can get done what I need to do with qxdm.
Thanks in advance.
Click to expand...
Click to collapse
looks like you're booted into bp tools for those interfaces to be dectected, correct? i'm not sure whether or not the moto device manager has drivers for these interfaces as i always use the standalone drivers. here's a link to the latest available as of this posting:
http://batakang.com/ftp/?dir=devs/mhous33/drivers
whichever driver installer you use, the drivers have to be installed manually. iirc motorola qc diag interface is the only one you need to communicate with qpst/qxdm.
in device manager, right click on motorola qc diag interface > update driver software > browse my computer for driver software > let me pick from a list of device drivers on my computer > ports (com & lpt).
under manufacturer, select motorola.
under model, select motorola qc diag port.
click next, driver should be installed successfully.
looks like you're using windows 8, so you may have to temporarily disable driver signing for it to install.
hope this helps.
Q9Nap said:
looks like you're booted into bp tools for those interfaces to be dectected, correct? i'm not sure whether or not the moto device manager has drivers for these interfaces as i always use the standalone drivers. here's a link to the latest available as of this posting:
http://batakang.com/ftp/?dir=devs/mhous33/drivers
whichever driver installer you use, the drivers have to be installed manually. iirc motorola qc diag interface is the only one you need to communicate with qpst/qxdm.
in device manager, right click on motorola qc diag interface > update driver software > browse my computer for driver software > let me pick from a list of device drivers on my computer > ports (com & lpt).
under manufacturer, select motorola.
under model, select motorola qc diag port.
click next, driver should be installed successfully.
looks like you're using windows 8, so you may have to temporarily disable driver signing for it to install.
hope this helps.
Click to expand...
Click to collapse
Lmao I posted this same rant on facebook and a phone flashing friend did these things with team viewer and went ahead and helped me retrieve my MSL code as well. It is all coming down to the UICC unlock, this is what is holding back our ability to sim unlock the sprint version of this phone (because without the UICC unlock it wont read any other Sim cards anyways) I'm working on that right now but I have a headache so it will be later.
ok,please if you have sucefully unlock gsm i will love to pay you if you give me the way.
MSL code
thundercles said:
Lmao I posted this same rant on facebook and a phone flashing friend did these things with team viewer and went ahead and helped me retrieve my MSL code as well. It is all coming down to the UICC unlock, this is what is holding back our ability to sim unlock the sprint version of this phone (because without the UICC unlock it wont read any other Sim cards anyways) I'm working on that right now but I have a headache so it will be later.
Click to expand...
Click to collapse
Does this mean getting the MSL code is useless in unlocking the device for GSM use?
do you have that moto x drivers? i dont find it anywhere.. will you please reupload it some where.. Thanks.
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!
Title.
All I really want to do is find my MSL code. I don't really want to call sprint though. I would very much appreciate it if someone could give me a working method.
I'm also rooted (in-case that helps)
you can read msl if your diag mode is enable, if diag mode is disable. you need to enable it, but for that root is required.
##3424# you can check your diag status or also in your pc device manager.
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
now diag is enable.
you can read spc from cdma workshop, its quite easy and google is your friend
sunilromy said:
you can read msl if your diag mode is enable, if diag mode is disable. you need to enable it, but for that root is required.
##3424# you can check your diag status or also in your pc device manager.
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
now diag is enable.
you can read spc from cdma workshop, its quite easy and google is your friend
Click to expand...
Click to collapse
Google has not been my friend recently. I was using oriax123's flash tool to find it. I wasn't able to find it because it would always come up blank. I then relized you needed to be in DIAG mode. I was able to find it after that. Thanks for your reply though.
I know u dont wanna here it but i called them and they gav3 me mine no ?s asked. I told them i needed it and that was it