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
Related
I was searching for a way to debrand my AT&T Samsung Focus S to receive the latest update and was at first surprised to find out that none of the registry editors work and secondly, that I could not find a simple way how to unbrand it.
So here is a simple way for anybody who was looking for the same thing.
Please note that this will unlock and debrand your phone (and I’ve also thrown in the 3G toggle tweak) but after you update to 7.10.8107.79 through Zune, you will no longer be able to use the ProvXML method of deploying registry settings (that we are using here).
All credit goes to Deathbyvegemite who told me what to do and Jaxbot and his WindowBreak Project which helped me figure out how to do it. This is really just a simple modification of his work, so I have to thank him and all the other people that have worked on this.
Okay, so to do this, please follow these steps:
1) Open your mobile browser and go to: http://www.kremese.sk/debrand_focus_s.zip
2) The file will be opened. Follow the instructions and tap on “debrandfocuss.xml”
3) Press Start
4) Navigate to Phone
5) Dial ##634#
6) Type *#9908#
7) Select DebrandFocusS
8) Press Save and Reboot
After that, connect to Zune and you will receive the 8107 update.
Thanks for the hack! I'm completing the Zune update to 8107 now, it should be complete in another minute or so.
I have some wifi issues with the Focus S -- as well as several other people I know and I'm hoping that even though this update does not say it fixes the wifi connection issue, I'm crossing my fingers that it does.
Thank you again, I always love having the latest OS version installed.
-John
jfreiman said:
Thanks for the hack! I'm completing the Zune update to 8107 now, it should be complete in another minute or so.
I have some wifi issues with the Focus S -- as well as several other people I know and I'm hoping that even though this update does not say it fixes the wifi connection issue, I'm crossing my fingers that it does.
Thank you again, I always love having the latest OS version installed.
-John
Click to expand...
Click to collapse
Well, it's been a couple hours since I completed the upgrade to 8107 and I just had the phone reboot during a phone call.
Thanks for the update, but I'll go back to my backup and wait patiently for the official update. Not that this one isn't official, but there maybe special tweaks that need to be done for the Focus S/i937 or AT&T.
-John
To be honest, I don't think it's related to the update, but I can of course understand that you want to be safe.
Doesn't seem to work for me. Not seeing any updates.
onesikpuppy said:
Doesn't seem to work for me. Not seeing any updates.
Click to expand...
Click to collapse
Do you have an unlocked device? If you have a registry editor you can check under this path:
HKEY_LOCAL_MACHINE\System\Platform\DeviceTargetingInfo\MobileOperator
The string value should be "000-88". If it still says "ATT-US" then please try again and follow the instructions precisely.
Yes, unlocked. Do you know of a registry editor that works on Focus S?
onesikpuppy said:
Yes, unlocked. Do you know of a registry editor that works on Focus S?
Click to expand...
Click to collapse
There are a couple that work, but currently only in read-only mode.
This one is the most user friendly I think:
EDIT: Argh, can't post outside links. Please google "Registry Editor for Windows Phone 7 Beta Testing".
Got the registry editor working. It still says ATT. I've gone through the process 5 times now. Each time it tells me "debrandfocussProvisioning succeeded" but after the reboot it's back to ATT-US.
but does this just give the OS update? Does this also give you the firmware update?
is the focus s out there for anyone else but ATT?
Not sure about the firmware update, but my firmware version after the update is: 2103.11.10.1.
onesikpuppy said:
Got the registry editor working. It still says ATT. I've gone through the process 5 times now. Each time it tells me "debrandfocussProvisioning succeeded" but after the reboot it's back to ATT-US.
Click to expand...
Click to collapse
Can you please check which version of the Diagnosis tool you have?
ver.0923
Thanks
Well, that's the same as mine. Are you sure you are not on 8107 already?
One thing you can try is to pull out your sim card and see if it works then.
I'll try pulling the sim
Sent from my SGH-i937 using XDA Windows Phone 7 App
Sim pull didn't help
Sent using xda premium
I have the samme issue that onesikpuppy with the same parameters in his attached thumbnails.
I bought a demo phone, can anyone help me get it out of the mode it's in?
works wonderfully. thanks to op
whats the diffrent betwween this unlock to the windows break unlock?
can i use registry editor to edit some enteries?
thank you
So i have seen many guys charging a good amount of money for this, DFS is charging like 50$ per phone. Many guys are struggling to get thr phone working since they are unable to flash Akey/SPC which is needed for some carriers like Reliance, TATA in India atleast.
I'm not going to put usual diag setup stuff right now, or may not able to update it at all.
The below commands should be sent step by step as mentioned through DFS or CDMA workshop or any other tools which you prefer to use. Also you need to first send the 16 digit password for your phone model. I believe for L720 it is "2012112120131219"
----To change SPC to 000000 or any anything
00
4B13030000000000
4B130F006E766D2F6E756D2F383500
4B1308006E766D2F6E756D2F383500
4B13020041020000B60100006E766D2F6E756D2F383500
4B1305000000000000000000303030303030
4B13030000000000
Click to expand...
Click to collapse
In the second last line i.e. "4B1305000000000000000000303030303030", the last 12 digits are your SPC hex value, if you want to change it to anything else like 123456, you need to edit the last 12 digits and make it look like "4B1305000000000000000000313233343536"
----To change the A-Key to anything, in the below case, akey decimal to be flashed is 11111111133333333785 (the akey hex will be: 9A3298B4E238A719)
00
4B13030000000000
4B130F006E766D2F6E756D2F323500
4B1308006E766D2F6E756D2F323500
4B13020041020000B60100006E766D2F6E756D2F323500
4B130500000000000000000019A738E2B498329A
4B13030000000000
Click to expand...
Click to collapse
In the above cmds, if you take a close look at the last 16 characters in the 2nd last line and the mentioned akey hex, you maybe observe that the akey hex in the cmd is in a reverse manner. You can change generate your akey online or via regular tools like DFS and arrange it in the similar manner to flash. You might need to downgrade your modem in order to get this working, please post here if it works without downgrading the modem.
This has been tested on 2xGalaxy Victory and one Sprint L720, so please test and report if this works for you.
funkym0nk3y said:
Mods
if this has been posted in wrong section, then please pardon my ignorance and kindly move it to appropriate section.
Click to expand...
Click to collapse
Good write up. I flash phones and make tutorials. Some people on here claim they can do this and do that but, haven't written a clear guide yet on how to do it. Lol But, my guides are free and to the public.
Also this should be in the general section. Development is only for roms, etc.
as for resetting the SPC, you will need to downgrade the modem from MF9 to MDL or MDC... i have tried it with MF9 and didn't work...
thanks for sharing
PapaDocta said:
as for resetting the SPC, you will need to downgrade the modem from MF9 to MDL or MDC... i have tried it with MF9 and didn't work...
thanks for sharing
Click to expand...
Click to collapse
If you dont mind someone asking, how do you downgrade the modem? I tried to downgrade the complete os from samsung-udpates but nothing has worked for me.... any other suggestions??? thx in advance
to downgrade the modem just download the old modem's tar file and flash it via odin.. it should work without any problems
PapaDocta said:
to downgrade the modem just download the old modem's tar file and flash it via odin.. it should work without any problems
Click to expand...
Click to collapse
I actually tried that and still nothing! Maybe i just have a phone that wont take....? I have tried several os downgrades and last resort was the modem downgrade and still the same result: UNABLE TO USE THE 16 DIGIT PASSWORD TO ACCEPT ON WORKSHOP.....
I appreciate your input and help brother thx again.
If you're serious about flashing phones you should invest the proper amount of money, in the proper tools.
slawson said:
If you're serious about flashing phones you should invest the proper amount of money, in the proper tools.
Click to expand...
Click to collapse
TKS BRO
Thank you this is the only thing i have seen that has actually had some success, at least i did not get any errors but how do i know if the akey is in if i press read i just get a lot of cps errors. DOes the trial version of dfs not let you do anything in the cave ?
anyway thanks again hopefully this works.
Many parameters on a number of phones are write only, so you won't be able to read them.
flashing rom fear
So I got my phone working on my cdma carrier in Indonesia. But now I am concerned about flashing New roms esp using Odin and factory resetting. Will I lose my settings with a factory reset?
How do I flash roms and still keep my network settings?
Thanks
jarcher12 said:
So I got my phone working on my cdma carrier in Indonesia. But now I am concerned about flashing New roms esp using Odin and factory resetting. Will I lose my settings with a factory reset?
How do I flash roms and still keep my network settings?
Thanks
Click to expand...
Click to collapse
To answer my own question since nobody else did
Dont worry i just installed the one click mf9 rom and am now free of nags for reboot and the annoying register phone on sprint. very happy with the phone and its performance, blows my old epic out the water.
Hi,
did anyone try to change the akey for Sprint Note 3... ? N900P
thanks in advance...
Add to my Framily!!!!
A00275186Ak
Thank You!
jarcher12 said:
So I got my phone working on my cdma carrier in Indonesia. But now I am concerned about flashing New roms esp using Odin and factory resetting. Will I lose my settings with a factory reset?
How do I flash roms and still keep my network settings?
Thanks
Click to expand...
Click to collapse
Using cwm to flash another rom
Sent from my SPH-L720 using XDA Premium 4 mobile app
I have a Sprint SPH-L720. I tired to use the command 4B1305000000000000000000303030303030 it accepts it but responds back with a differnt command and the SPC doesn't change.
I did downgrade the baseband to both MDC and MDL with it still not working.
Any ideas how to change the SPC to 000000?
Been awhile but I thought I posted an update. Downgraded to the MDC modem and tired again and it solved my problem.
Thank you for the awesome post.
Using the command
please how will i make use of this command.
i am currently using Sprint SPH-L720T
any other methods of changing spc?
Okijaamaka said:
please how will i make use of this command.
i am currently using Sprint SPH-L720T
any other methods of changing spc?
Click to expand...
Click to collapse
You need a PC software such as DFS to send these command to your phone. You also have to enable diag mode in your phone before connecting it to the PC's USB.
rizapn said:
You need a PC software such as DFS to send these command to your phone. You also have to enable diag mode in your phone before connecting it to the PC's USB.
Click to expand...
Click to collapse
i have DFS but do you have step by step on how to connect it?
please. want to change my spc to 000000
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!
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.
Hello all, been a little while with LG V40 as my second device, and loved it so much but tried to follow the crossflash procedures as mentioned here:
https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and I succeeded with it, only few notes wanted to share as experience/question about them:
- wifi, 3G and 4G are working as it should and no other problem found.
1. after flashing, phone booted successfully to Android 10, giving strange error message :
"WARNING!
Current version is not available for user. Can't find matched carrier. Check NT-Code: 310410310150 310170,311180,310560,310030,3 10280,310950,313100,312670: FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
2. there's no SN for the phone in the settings!
- attached some screenshots for errors, looking forward to seeing some feedback or help if possible with how to fix those problems.
thanks in advance for all for such great efforts done here.
Hi, possible remove simlock after crossflash? Thanks.
P.S.
To remove message "WARNING!
Current version is not available for user. Can't find matched carrier......"
You must have root and edit file cust_path_mapping.cfg
77an said:
Hi, possible remove simlock after crossflash? Thanks.
P.S.
To remove message "WARNING!
Current version is not available for user. Can't find matched carrier......"
You must have root and edit file cust_path_mapping.cfg
Click to expand...
Click to collapse
thank you so much, i overcome it by crossflashing the latest EU Android 10.
and, about sim lock, it can't be done with cross flashing.
abokamel said:
thank you so much, i overcome it by crossflashing the latest EU Android 10.
and, about sim lock, it can't be done with cross flashing.
Click to expand...
Click to collapse
Can you share the rom that you use?
Also, were you root?
oscarillo said:
Can you share the rom that you use?
Also, were you root?
Click to expand...
Click to collapse
no, it's stock, not rooted.
the current rom i use now is here
abokamel said:
no, it's stock, not rooted.
the current rom i use now is here
Click to expand...
Click to collapse
Thanks a lot for your reply.
One more question.
Did you do a Refurbish or Upgrade option?
oscarillo said:
Thanks a lot for your reply.
One more question.
Did you do a Refurbish or Upgrade option?
Click to expand...
Click to collapse
used the command line, i think it's making refurbish
This is a bit of an older thread, but just recently did the same crossflash from pie on att device to korean open Q.
Decided on the KR instead of EBW because KR, I thought, had more of the t-mo LTE bands I needed. Unfortunately, the different sites with firmware specs aren't always accurate (which LTE bands supported). One site has EBW supporting every LTE band of every LG phone! Def inaccurate.
So I tested both EBW and KR Q versions. Use LTE Discovery (from playstore) to view LTE bands in your current location. One thing to note about that, the LTE bands it shows u are going to be the nearest towers it's using. Which means that another tower, a little farther away, won't show up.
So to verify a particular band, that you think the phone might be capable of, but you aren't sure, you have to go into the svc menu and select 'field test' and enable only that LTE band you're searching for. Then use LTE Discovery and see if it's connected with that band. If it isn't connected with it (usually it will default to a 3G band if that one u selected isn't available), that means 2 things; 1) either that band isn't used in your area 2) Your device doesn't support that band (or both 1 and 2).
But in my case, I know band 71 works in my area (from previous testing), but I have to select enable for only that band for it to show up, because other nearby towers with band 66 will 'drown it out'.
Thus, the point here, the KR firmware Band 71 **DOES WORK**. And, btw, no site indicates it included in supported bands. The following screenshot shows it connected to 71 and the KR 409 at the bottom.
Cheers
abokamel said:
Hello all, been a little while with LG V40 as my second device, and loved it so much but tried to follow the crossflash procedures as mentioned here:
https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and I succeeded with it, only few notes wanted to share as experience/question about them:
- wifi, 3G and 4G are working as it should and no other problem found.
1. after flashing, phone booted successfully to Android 10, giving strange error message :
"WARNING!
Current version is not available for user. Can't find matched carrier. Check NT-Code: 310410310150 310170,311180,310560,310030,3 10280,310950,313100,312670: FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
2. there's no SN for the phone in the settings!
- attached some screenshots for errors, looking forward to seeing some feedback or help if possible with how to fix those problems.
thanks in advance for all for such great efforts done here.
Click to expand...
Click to collapse
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
You need to have root access to so you can open your /oem/OP/cust_path_mapping.cfg and a hex editor. I use HxD.
Write down the number you have in the beginning, in my case "FFFFFF,60"
Reboot into 9008, open QFil and backup your FTM by choosing "READ" option
File will be stored at C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_9
Rename file to FTM_original.bin and open in HxD
Press ctrl + G to go to offset 14000
and replace first section with number you wrote down from cust_path_mapping earlier while deleting everything after
Also, if you're missing a serial number you can add that in as well, located at offset 12000 in the FTM file
Replace the red FFFFFFFFFFFFFF with your serial #
Once done, hit "SAVE AS" so you have a backup of the original if things go wrong and rename to FTM_fixed.bin
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
advancedtekniqs said:
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
<snip brevity>
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
Click to expand...
Click to collapse
Wow thanks for that. First I've seen this idea to fix that issue. Other methods didn't work. Will try soon.
There are some other values you can change in cust.prop that can help also. Get's rid of most of the KR language in unexpected places. Will jot them down and add them here shortly.
cheers
AsItLies said:
Wow thanks for that. First I've seen this idea to fix that issue. Other methods didn't work. Will try soon.
There are some other values you can change in cust.prop that can help also. Get's rid of most of the KR language in unexpected places. Will jot them down and add them here shortly.
cheers
Click to expand...
Click to collapse
I've only been using this rom for about 6 hours. I haven't really noticed any KR except on the phone dialer. Doesn't really bother me, but if you have a way to set that to ENG, I'd like to know as well.
advancedtekniqs said:
I've only been using this rom for about 6 hours. I haven't really noticed any KR except on the phone dialer. Doesn't really bother me, but if you have a way to set that to ENG, I'd like to know as well.
Click to expand...
Click to collapse
Yes u need to change the cust.prop in OP. Change the target region country to US (from KR) and same for target country. Change language prop to en_US.
Additionally, change featureset prop to OPENUS from OPENKR.
these changes disable most KR elements in firmware, most noticeably dual clock and call recording in dialer. They **may** also enable volte if supported by carrier.
This is from nice guy Neo on tele group who's played with this much more than I have
Cheers
Oh yeah, lol, just remembered, the main reason I was asking for the info above was to get the 'field test' selection (so you can select LTE bands) in the SVC Menu from dialer. By default, it doesn't show up, but above changes fixes that also.
advancedtekniqs said:
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
You need to have root access to so you can open your /oem/OP/cust_path_mapping.cfg and a hex editor. I use HxD.
Write down the number you have in the beginning, in my case "FFFFFF,60"
Reboot into 9008, open QFil and backup your FTM by choosing "READ" option
File will be stored at C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_9
Rename file to FTM_original.bin and open in HxD
Press ctrl + G to go to offset 14000
and replace first section with number you wrote down from cust_path_mapping earlier while deleting everything after
Also, if you're missing a serial number you can add that in as well, located at offset 12000 in the FTM file
Replace the red FFFFFFFFFFFFFF with your serial #
Once done, hit "SAVE AS" so you have a backup of the original if things go wrong and rename to FTM_fixed.bin
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
Click to expand...
Click to collapse
thank you so much for sharing such detailed fix for that strange problem., as a work around, I managed to flash OPEN US kdz, then reflashed the open KR, then it's gone now, but i can't find mt phone's serial number when showing it on settings.
thanks again for such amazing tutorial. keep up
AsItLies said:
Yes u need to change the cust.prop in OP. Change the target region country to US (from KR) and same for target country. Change language prop to en_US.
Additionally, change featureset prop to OPENUS from OPENKR.
these changes disable most KR elements in firmware, most noticeably dual clock and call recording in dialer. They **may** also enable volte if supported by carrier.
This is from nice guy Neo on tele group who's played with this much more than I have
Cheers
Oh yeah, lol, just remembered, the main reason I was asking for the info above was to get the 'field test' selection (so you can select LTE bands) in the SVC Menu from dialer. By default, it doesn't show up, but above changes fixes that also.
Click to expand...
Click to collapse
that's terrific and brilliant to be honest! thank you so much for information you shared.
So, just found something additional that works on open 409N. The 'buffer fix' can be a bit of a pain. Tried a magisk module supposedly for v40 Q but that didn't work. So did what I've done before and just copy the .so fix to the appropriate directory, but that didn't work, even the oem camera stopped working after that.
So, even though this says it's for 'custom roms' tried it, and boom, works in magisk and does what's needed to fix buffer.
cheers
abokamel said:
thank you so much for sharing such detailed fix for that strange problem., as a work around, I managed to flash OPEN US kdz, then reflashed the open KR, then it's gone now, but i can't find mt phone's serial number when showing it on settings.
thanks again for such amazing tutorial. keep up
Click to expand...
Click to collapse
Try this website to find your seriel# by IMEI
So, interesting updates, for anyone using this Rom.
I went back to my AT&T rom, android 9. Then, just a few hours later... decided to go back to KR Open Don't ask, it's too confusing
But, the point, this time, when flashing the KR rom, I did part DL, and then after booting did Refurbish. Had read on tele that doing that fixes some of the issues crossflashing causes. Sure enough, my NT-code issue went away (couldn't fix that even with hexedit of ftm)!
So, that was cool. But now, my S/N disappeared! IMEI was still okay though. So tried the hexedit ftm and added S/N, boom, now it's fine also. But the funny thing was, with the refurbish and no NT-code problem, I looked at what was in the newer ftm at that address, and it had nothing, no info at that address at all.
One thing to be aware of, attesting to why this is difficult to deal with, these values (IMEI, S/N - and others) get propagated from one partition to another, I don't know the chain of events or criteria involved, but it adds to the difficulty of trying to fix issues. Which specific place it looks for something is confusing also, and if it's doing compares of 2 or more places is a mystery.
But anyway, do a Part DL to crossflash, then do a Refurb and it appears to fix some of the issues.
cheers
Awesome work, fellas!
What program and files do you all have success with during the flashing? Perhaps share a link to it?
Also, is a serial number necessary? For using the phone and having service? Seems you guys are taking the blank serial number very seriously. Thanks!
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
AsItLies said:
But anyway, do a Part DL to crossflash, then do a Refurb and it appears to fix some of the issues.
cheers
Click to expand...
Click to collapse
So for an old sprint v40 running oreo, Just crossflash to the korean Q rom via partition DL, then again, with Refurb option? Or swap between different roms? Haven't done any crossflashing yet..hoping to avoid errors. Serial number loss won't stop the phone from working, right?
fireblade20 said:
Awesome work, fellas!
What program and files do you all have success with during the flashing? Perhaps share a link to it?
Also, is a serial number necessary? For using the phone and having service? Seems you guys are taking the blank serial number very seriously. Thanks!
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
So for an old sprint v40 running oreo, Just crossflash to the korean Q rom via partition DL, then again, with Refurb option? Or swap between different roms? Haven't done any crossflashing yet..hoping to avoid errors. Serial number loss won't stop the phone from working, right?
Click to expand...
Click to collapse
Mine is an AT&T, but afaik, Sprint should be the same. Yes, do the part DL, let it reboot as normal, then shut off and do refurb. Is S/N a big deal? no, everything works, and the S/N is still in the phone, just not displaying properly. It's an individual thing how much effort you put into fixing that. Some people have lost either / or IMEI or dual IMEI (some roms have that), when cross flashing. That's a problem because they get no cell signal, but that's on a different rom.
Look in this thread for how to LGUP / crossflash.
cheers
Thanks man!