Hi, all...
After hours of searching, I finally decided to patch the diag drivers to include the HTC Zara (Desire 601). Any of you with the CDMA version may want to play with radio settings, etc.
To use this, unzip the file. Then, in an adb shell, type:
Code:
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
This got me into diag mode, and I could read the phone on the full version of CDMA workshop. I was trying to flash the phone to another carrier, but my settings for NV_ONLY wouldn't seem to stick.
It looks like a lot of settings are locked down now, so either a CDMA WS update will fix it, or someone with far more knowledge than me will have to actually patch the radio.
Credit to XDA User twistedumbrella for the adb shell command.
Enjoy....
Stovepipe said:
Hi, all...
After hours of searching, I finally decided to patch the diag drivers to include the HTC Zara (Desire 601). Any of you with the CDMA version may want to play with radio settings, etc.
To use this, unzip the file. Then, in an adb shell, type:
Code:
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
This got me into diag mode, and I could read the phone on the full version of CDMA workshop. I was trying to flash the phone to another carrier, but my settings for NV_ONLY wouldn't seem to stick.
It looks like a lot of settings are locked down now, so either a CDMA WS update will fix it, or someone with far more knowledge than me will have to actually patch the radio.
Credit to XDA User twistedumbrella for the adb shell command.
Enjoy....
Click to expand...
Click to collapse
Is that command for getting into diag mode without the MSL or something? I had no problems using QPST or CDMA WS with the device as-is, didn't even have to install the diag drivers like with older devices. I think HTC sync installs them now, so you can just install sync for the drivers and then uninstall just the sync app.
Also, are those drivers 32-bit or 64-bit?
If you need your MSL, MSL Reader gets it quick and easy on this device and ##3424# opens diag mode.
These are 32 Bit drivers.
I guess my original post was redundant.. the back story is that I was working on a nTelos Desire 601, which didn't have the ##3424# option. Having just acquired a VM Model, you're correct, 3424 does work.
Windoze still installed the diag driver I'd patched, so they still may be useful to some people.
I'm gonna put this phone on PagePlus.
U have a Zaru_ul and would like to know if anybody has been able to unlock the AWS band on this phone, and if so what was the procedure? Thanks
Related
After I seen two threads regarding QPST/CDMA Workshop, I decided to give it a try too.
However, I had the problem with drivers, which I luckily solved.
Drivers source: http://catalog.update.microsoft.com...updateid=14df499c-c71f-4152-a63b-1c1e40cfc14c
So, here's the solution for everyone:
1. Unzip the attached archive.
2. adb shell, su, echo 1 > /sys/devices/virtual/usb_composite/modem/enable
3. Open Device Manager. Under unknown devices you'll find two "SEMC HSUSB" devices.
4. For both, install drivers from the folder.
You'll get unsigned driver warning, ignore and continue with installation.
5. Reboot phone.
6. adb shell, su, echo 1 > /sys/devices/virtual/usb_composite/diag/enable
7. QPST/CDMA workshop should detect the phone now.
I won't link QPST (I don't know if there are any copyright barriers), but you can find it extremely easy on Google. You want QPST 2.7 build 355.
If you're asked for SPC code, it's default 000000.
Now, I need testers: anyone with locked bootloader, or bootloader unlocked with Omnius/SEtool, please open EFS Explorer and tell me if there's anything inside cert, client-cert and client-key folders. Alternatively, try to find any SE/SEMC certificates in EFS.
Best regards
64 bit vista won't let me install. any chances you can make this.
trent6gol said:
64 bit vista won't let me install. any chances you can make this.
Click to expand...
Click to collapse
Strange. What error are you getting?
Thanks no error messages at all!
Good. Is your bootloader locked?
No new hardware are detected, even with modem enable set to 1
Im in Xperia arc unlocked by setool
Alejandrissimo said:
No new hardware are detected, even with modem enable set to 1
Im in Xperia arc unlocked by setool
Click to expand...
Click to collapse
Just turn on modem mode and install provided drivers for both HSUSB devices in Device Manager.
Blagus said:
Just turn on modem mode and install provided drivers for both HSUSB devices in Device Manager.
Click to expand...
Click to collapse
When I set the modem to 1 the adb stop working and the sa102 dissapear from the device manager but there is now new hardware detected.
Yes, that's what should happen - you should have two or three HSUSB devices under unknown ones. Install drivers for them.
Blagus said:
Yes, that's what should happen - you should have two or three HSUSB devices under unknown ones. Install drivers for them.
Click to expand...
Click to collapse
Nop. There is no unknown devices at all :S
Im runing a custom kernel, maybe need to run stock?
link up my video also and claim its yours atleast give credit
also guys if your on stock rom verizon to enter DIAG mode you enter ##3424
edokassiah said:
link up my video also and claim its yours atleast give credit
also guys if your on stock rom verizon to enter DIAG mode you enter ##3424
Click to expand...
Click to collapse
Which video?
Fyi for those using cdma workshop, You dont need to do the adb commands, phone wont "read" the info for general stuff, just goto security, send the spc code, it will unlock, then continue to upload your PRL stuff and change nam settings. Worked fine. =)
what is this exactly? and what is DIAG/QPST/CDMA workshop?
For cdma phones to change out which carrier its on, you need diag mode (which is the programming mode thats seperate from rom flashing as it tells the phone which tower to connect to) qpst and cdma workshop, are tools we use to program this stuff easier. Cdma workshop costs 100$ for a license tho.
x64 Drivers that WORK!!!!!!!!!!!
i dunno if this even matters anymore but i just made these x64 drivers and they have been tested and work just fine htey are not signed but they will install on win 7 x64
Will this driver let us who use custom rom to using DIAG mode?
since most of custom ROM kill the DIAG ability, so nothing will happen when u press #3424
no they wont unforutnatly
Ok so Iv manged to finally get the screen to say "waiting for device" But thats when the phone is on..
If i restart with VOL DOWN and power into FAST BOOT USB AND I GO type in the cmd " fastboot oem get_identifier_token."
It says >>>>>> <Bootloader> [ERR] COMMAND ERROR wTF is the issue? I downloaded a ADB tool that installed in my CMD, I tried the SDK and it never would take always threw up error etc, so I ran across something else and its the Furthest iv gotton so far..
Only issue now is This ERROR when im in FASTBOOT USB.. Ive got a Virgin Mobil.. HBOOT 1.58.0000
Also on the HTC DEV site when i would go to DL the Zip for windows, At one point it kept saying ADB etc is missing.. So i found a program with the main tools that makes it do what it needs to without all the extra stuff SDK installs, Which again BTW would never fully extract and work..
So i go to the zip file i download for windows and now i go to run it, and it throws up the CMD window for half a sec and i can see allot is filled out but it goes rite away... So as i said this is the furthest ive gotton to unlocken it.. What could be causing this???
I can walk you through it, I don't know what is in the zip you down loaded
Cant view code sent in email from htc dev
jcfunk said:
I can walk you through it, I don't know what is in the zip you down loaded
Click to expand...
Click to collapse
So ive manage to get my Phn to work for me and the program i DL/// . I got my token from HTC DEV, But now my only issue is The email they sent me with the code in it, I cant view it??
Does it take some kinda special view? It says its a UDF code or something? like that.. IM SOO CLOSE to unlocking it but so far at same time..
I never could get sdk tools to DL i found a ADB program that managed to make everything work just fine. It went from Pulling up NOTHING IN CMD for my phone, then with that simple download of the ADB program, It was a program someone just put the main things needed together and left out all the XTRA BS that SDK tools come with, SDK tools never once downloaded or open rite..
But as i said Ive pasted the TOKEN!! GOT SENT THE EMAIL, But the code attachment sent is not viewable, I have never run across something like this.... Ive also posted in EVO 3D about this issue, But anyone have a idea what i need to view the code?
BTW THIS IS THE SITE I DL THE PROGRAM FROM THAT FINALLY got me to get my CMD prompt to work for my phone and eventually give mmmmme my token..... Take a look at it... It might be allot easier new way for newbies in the future.
http://dottech.org/21534/how-to-install-adb-and-fastboot-on-your-windows-computer-for-use-with-your-android-phone/
It's not viewable easily, you send file to phone using fastboot commands. The phone will bring up a screen asking you if you want to unlock
jcfunk said:
It's not viewable easily, you send file to phone using fastboot commands. The phone will bring up a screen asking you if you want to unlock
Click to expand...
Click to collapse
Im new to this whole thing, My issue also is I only have one smartphone, the one im unlocking and im just running it on wifi.. But Could i still send it to my phone somehow? Or is there another way to view the damn code>? I cant believe This one thing is holding me up..
it says this " VLC does not support the audio or video format "undf". Unfortunately there is no way for you to fix this.
Ive saved it to the Folder that Has FastBoot and adb (The code sent to my email).. Then i go past in cmd" fastboot flash unlocktoken Unlock_code.bin"
But it just says error Cannot open Unlock code bin.
When i saved the program with the fastboot etc in it, I just made a New Folder, How do i make it a spefic location.. ? Like for example
C:\ANDROID
OR C:\ADB tHAT way i can type it into the CMD prompt an it recognize it? Im thinking thats one of my main problems now as well...
At first i saved my new files to My documents.. Then i sent the ones with ADB &FASTBOOT to lOCAL DISK C:\
Where am i going wrong?
You need to be in the directory with the fastboot.exe and unlock.bin
Man it has been awhile for me to use Windows.
Maybe easier to make a folder in c:\
everything needs to be in same folder
---------- Post added at 11:22 PM ---------- Previous post was at 11:19 PM ----------
Use Linux it's easier
Forget about HTC DEV it won't work with hboot 1.5+. You'll want s-off to be truly rooted anyways, and HTCdev will only unlock you.
You'll need to downgrade the bootloader to 1.4 and ROM(main) version to 1.13. Then run Revolutionary S-OFF, then reupdate the hboot back to 1.58 and main version back to 2.95.
I only know the process for my sprint cdma. However, none of my carrier settings were altered during that process, so I can say with quite a bit of certainty that the same process / RUU files can all be used on your phone as well
I put together a pretty clear noob guide in the first post of the lnk below. Took me 3 or 4 days with the help of two other members here, so when I finally got S-OFF I put together a summary of the whole process include all the links to the tools / files needed.
You'l need
blank CD and burner, know how to boot from a CD
data USB cable
Micro-sd adapter so you can load files onto your phone's micro-sd from your PC
http://forum.xda-developers.com/showthread.php?t=2794935
Good luck
---------- Post added at 01:55 AM ---------- Previous post was at 01:24 AM ----------
As for the HTCdev unlock....I used ROOTEVO3DNEW instead of the fastboot binares that HTCdev gives you(C:\Android). Create a new folder in C:\ and name it rootevo3dnew. Unzip all rootevo3dnew.zip contents into that folder. This is the folder where you will do everything instead of C:\Android...place the unlock key .bin file directly in the main directory of rootevo3dnew . Type cd \rootevo3dnew in cmd to change the directory and repeat the process as you would with C:\Android
Chances are that will not work either, you will need to do the brick / downgrade
I have an M9, it has
the original radio version 1.32.651.17,
Baseband 1.10.C11
Kernel 3.10.49
Android 5.0.2
Sence 7.0
Why can't I get Diag mode? Every howto about this phone seems to just state "put in DIAG mode" but seem to skip the step of getting the MSL(SPC) in all the tutorials??? I put TWRP on it it, obviously rooted... Every time I do ##DIAG# it asks for MSL(SPC). EVERY cell phone for the last ten+ years has been a CDMA HTC, starting with my Apache in 2005. EVERY single one of them you could access DIAG mode, then use PSAT or Revskills to overwrite the MSL(SPC).
I can't get to DIAG, so I cant get the MSL(SPC), to gain DIAG mode.... lol!
What is the deal with this and how do I get around it?
cheers,
disco
Are you trying to get your MSL code by entering DIAG mode and then use a program like CDMA workshop? That way doesn't work anymore since the M8 i believe. You need to call Sprint to get code or look in the forum for other alternative ways.
P.S. DIAG mode works fine here, I can turn it on and off no MSL code needed. Im also on the lastest firmware though.
schmeggy929 said:
Are you trying to get your MSL code by entering DIAG mode and then use a program like CDMA workshop? That way doesn't work anymore since the M8 i believe. You need to call Sprint to get code or look in the forum for other alternative ways.
P.S. DIAG mode works fine here, I can turn it on and off no MSL code needed. Im also on the lastest firmware though.
Click to expand...
Click to collapse
CDMA workshop has not worked on all HTC's for a long time. WS kinds sucks I think. As far as I know Revskills will still work once in DIAG mode. If you don't mind, which radio are you on and are you using OEM rom or custom rom.
Thanks for the info bro!
cheers,
disco
disco_y2k said:
CDMA workshop has not worked on all HTC's for a long time. WS kinds sucks I think. As far as I know Revskills will still work once in DIAG mode. If you don't mind, which radio are you on and are you using OEM rom or custom rom.
Thanks for the info bro!
cheers,
disco
Click to expand...
Click to collapse
im on Badboyz ROM 5.1
baseband 2.10.C1144070
Build 2.11.651.19
Yeah I haven't used workshop since the M7
Verified, Revskills will read and write the MSL(SPC) once S-OFF. I just did it.
Thanks for help bro and have a Happy New Year!
cheers,
disco
i read spc with revskill after root., no need of soff, You can put your phone into diag mode without any spc., if you know how to turn on diag via ADB. i did it on my m9.
disco_y2k said:
I have an M9, it has
the original radio version 1.32.651.17,
Baseband 1.10.C11
Kernel 3.10.49
Android 5.0.2
Sence 7.0
Why can't I get Diag mode? Every howto about this phone seems to just state "put in DIAG mode" but seem to skip the step of getting the MSL(SPC) in all the tutorials??? I put TWRP on it it, obviously rooted... Every time I do ##DIAG# it asks for MSL(SPC). EVERY cell phone for the last ten+ years has been a CDMA HTC, starting with my Apache in 2005. EVERY single one of them you could access DIAG mode, then use PSAT or Revskills to overwrite the MSL(SPC).
I can't get to DIAG, so I cant get the MSL(SPC), to gain DIAG mode.... lol!
What is the deal with this and how do I get around it?
cheers,
disco
Click to expand...
Click to collapse
with ROOT...
Code:
abd shell
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
exit
exit
To get MSL there are many programs... I like this as it is small download and easy to use https://code.google.com/p/cdmaworkshoptool/downloads/detail?name=CdmaDevTermV.2.zip&can=2&q=
DONE
I have an old Coolpad Quattro 2 (model 801 ES) that I was given to play around with. The phone hasn't had service in a couple years and I wanted to poke around in CDMA workshop or DFS to see what I could find. I have the MTP, ADB, and fastboot drivers all installed and working properly, but I can't for the life of me figure out how to get this phone to connect as a modem / COM device so I can use it in the programs I want. I tried entering ##3424# (##diag#) from the dialer, which brings up the diagnostic menu, but also prompts me for my MSL code. I don't have it, but I did find a workaround by going into terminal emulator on the phone and running "su setprop sys.usb.config diag,adb" whici should put the phone into diagnostic mode. It does something. when I type it the phone disappears from device manager and shows back up as unknown device. I'm assuming this is because I don't have the correct diagnostic drivers installed, but as far as I can tell they don't exist. A weeks worth of Googling has led me to the conclusion that this is a ghost phone. the only info I can turn up is instructions on how to root (extremely outdated), an inbuilt security backdoor called "cool reaper", and multiple websites listing specs and reviews. No drivers, no firmware files, nothing. Not even on the manufacturers home page. I'm at a complete loss. Any ideas?
This is what I had to do to fix the Unknown caller ID issue with 4G Calling enabled in the respective SIM settings:
Installed QPST Tool on my computer.
With USB debugging enabled in Developer Settings and Magisk for root access, enabled DIAG mode using adb:
Code:
$ adb shell
surya:/ $ su
surya:/ # setprop sys.usb.config diag,serial_cdev,rmnet,adb
In QPST >> PDC activated the respective profile for Sub0 and Sub1 and removed the originally automatically chosen profile (otherwise it kept reversing the desired setting on reboot).
Checked status with *#*#INFO#*#*.
Can this be done without root, I'm having the same issue on a Meizu device without root access & don't have a option to disable VoLTE
TheInfiniteAndroid said:
Can this be done without root, I'm having the same issue on a Meizu device without root access & don't have a option to disable VoLTE
Click to expand...
Click to collapse
If on an original ROM, there should be a way to access a service menu where you can switch on the diag mode that's necessary to be able to use PDC by using the phone dialer.
You may want to search for how to enable diag mode for your device (on my previous OnePlus with OxygenOS firmware it was somthing like *#*#801#*#* or *#*#808#*#*).
Master One said:
If on an original ROM, there should be a way to access a service menu where you can switch on the diag mode that's necessary to be able to use PDC by using the phone dialer.
You may want to search for how to enable diag mode for your device (on my previous OnePlus with OxygenOS firmware it was somthing like *#*#801#*#* or *#*#808#*#*).
Click to expand...
Click to collapse
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
TheInfiniteAndroid said:
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
Click to expand...
Click to collapse
Do you happen to know if there's a way to find it through Activity Manager, finding it hard to navigate
@TheInfiniteAndroid, sorry, can't help with this, don't know Activity Manager.
Hi, I have switched my profiles on my Mi 8 to DT_Greece to activate VoWiFi and deleted the original ROW_Commercial profile.
Whenever a call is getting through VoWiFi or VoLTE i still get unknown caller ID.
Do you perhaps have any other idea to fix that?
razenxd said:
Hi, I have switched my profiles on my Mi 8 to DT_Greece to activate VoWiFi and deleted the original ROW_Commercial profile.
Whenever a call is getting through VoWiFi or VoLTE i still get unknown caller ID.
Do you perhaps have any other idea to fix that?
Click to expand...
Click to collapse
You may want to try another profile in that case, as there is no other way to solve this.
Master One said:
You may want to try another profile in that case, as there is no other way to solve this.
Click to expand...
Click to collapse
Aah really? That sux
Ι've tried more than the half configs listed and only DT_greece seems to enabling VoWiFi for Vodafone Greece carrier
razenxd said:
Aah really? That sux Ι've tried more than the half configs listed and only DT_greece seems to enabling VoWiFi for Vodafone Greece carrier
Click to expand...
Click to collapse
Indeed, sucks if not working, but I have no other idea. Try the second half of configs as well, maybe there is one that just works with your carrier.
Master One said:
Indeed, sucks if not working, but I have no other idea. Try the second half of configs as well, maybe there is one that just works with your carrier.
Click to expand...
Click to collapse
That's what i'm doing at the moment.
No luck so far
On RN10 Pro my carrier works just fine, I already have extracted the .mbns from RN10 Pro's firmware but now i need to find which one is actually is using and a way to insert it to my device!
Master One said:
This is what I had to do to fix the Unknown caller ID issue with 4G Calling enabled in the respective SIM settings:
Installed QPST Tool on my computer.
With USB debugging enabled in Developer Settings and Magisk for root access, enabled DIAG mode using adb:
Code:
$ adb shell
surya:/ $ su
surya:/ # setprop sys.usb.config diag,serial_cdev,rmnet,adb
In QPST >> PDC activated the respective profile for Sub0 and Sub1 and removed the originally automatically chosen profile (otherwise it kept reversing the desired setting on reboot).
Checked status with *#*#INFO#*#*.
Click to expand...
Click to collapse
Thanks for posting on this, but what do you mean by qpst>>pdc? When I run qpst I see no active devices, pdc doesn't either. So no clue how to proceed.
treebaard said:
Thanks for posting on this, but what do you mean by qpst>>pdc? When I run qpst I see no active devices, pdc doesn't either. So no clue how to proceed.
Click to expand...
Click to collapse
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after connecting?
Master One said:
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after
Master One said:
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after connecting?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yes, up to the step of my phone being recognized, as it isn't automatically recognized at all by qpst config. And since there is no faq of any kind on what to do if the phone isn't recognized by QPST, I'm stuck.
I presume the issue is that I don't see any ports listed in the ports view. But I installed the Qualcomm usb driver already, so not sure how to fix that
per https://forum.xda-developers.com/t/rom-11-lineageos-official-surya-karna.4202533/post-85746887 , did you fix this in LOS 17.1, or 18?
treebaard said:
per https://forum.xda-developers.com/t/rom-11-lineageos-official-surya-karna.4202533/post-85746887 , did you fix this in LOS 17.1, or 18?
Click to expand...
Click to collapse
I'm not a developer and I can't really help as I'm not currently using LOS. You may want to find out if DIAG mode is supported and working in LOS.
TheInfiniteAndroid said:
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
Click to expand...
Click to collapse
PDC you will find it in the folder with the installed program QPST.
I did it. Sorry for my English.
Master One said:
I'm not a developer and I can't really help as I'm not currently using LOS. You may want to find out if DIAG mode is supported and working in LOS.
Click to expand...
Click to collapse
Another user said this procedure worked with LOS 17.1, but not 18.1 which we now run. I don't see a new device added in windows task manager, so I guess something's changed, and the QPST folks need to look into it.
treebaard said:
Another user said this procedure worked with LOS 17.1, but not 18.1 which we now run. I don't see a new device added in windows task manager, so I guess something's changed, and the QPST folks need to look into it.
Click to expand...
Click to collapse
The QPST folks have nothing to do with this, maybe (I mean hopefully) @gardiol can comment on DIAG mode support in the current version of LOS.
Can this have anything to do with the MUIU vs. OSS vendor?
I'm still running an older version of ArrowOS with the MIUI vendor, but possibly the DIAG mode problem came up with the move to OSS vendor?