Related
While rooting the phone will allow for all sorts of stuff I am mostly interested in getting past the second NAI check Sprint has (which was easy to do with the Instinct.) I found some directions at http://www.insiderforums.com/forums/showthread.php?t=31642 but these aren't working right for me. Perhaps someone else can give them a try?
Also, when I bought my Hero from Best Buy I did get a sheet of paper with the phones "password" on it. I thought this was the MSL but it doesn't work to actually unlock the ##DATA# editing (though put in by itself it will show the ESN info.) If this isn't the true MSL what can I tell Sprint is the reason for giving it to me? (A factory reset use to be a good excuse but this is built-in command on the Hero.)
Thanks.
Hi, I finally got my MSL, so I'm going to try this now...will report back with the results.
Also, I got my MSL today by doing an ecare chat session, and told her that I was having problems with my voicemail, and that I'd like her to walk me through a manual provision so we could properly set up my number and MSID number. She didn't ask any suspicious questions, just helped me and immediately gave me my MSL.
EDITS:
-So far I have a different version of QPST, and it didn't recognize my hero, so I'm downloading his new version. will post back soon.
-I put the new build of QPST on my Vista machine, and it still doesn't recognize my phone model. I can add the USB port (on mine COM 8) but it still says unknown phone...crap. I'm going to try it at home on my XP Machine to see if that makes a difference. Will post back with results.
-Tried on an XP laptop we have here at the office. Still no go. It's not recognizing my phone model. I see that you posted exactly the same thing I'm seeing in that forum. Want to relay that to him? I don't have an account. Also, I COULD get into it on my other version of QPST, however, I just chose one of the umpteen models in there, none of which applied to my hero. They were all like "FFA-1330" and stuff like that. Nothing hero looking. I noticed when doing some more research that this can happen with older versions of QPST. Wondering if a newer version would make a difference, or maybe Chris is using a different version than 2.7.301.
-Found a newer version of QPST, version 2.7.323, downloading now at a painfully slow rate.
JACKPOT!
This version of QPST properly works and found my phone as a "FFA/SURF 7600" phone. I'm now following his guide to see if I can't get it to work.
Since this was a success, I felt it should be in another post
EDIT:
OK, so I followed his guide, copied my NAI into tethered NAI, and when choosing "Write to phone" I got a write error reported. It states under the NV Item column "NV_UE_IMEI_I" and under the Status column "NV_READONLY_S"
When I again chose to read from phone, it seems that the change is still in there. I'm going to do the all important test, and will report back as to if it actually works. I'm giddy like a schoolboy right now.
--Well, I still get the error 67 and error 65, so it appears it didn't work. Phooey. I'm still going to mess with it more to see what happened. I felt good about it, and maybe there's still some hope.
Same. I updated both Profile 0 and Profile 1. Same "read only" error but after a reboot, update profile, and rerunning QPST the changed values appeared to be there but still 65/67 errors.
Any one else try this yet?
Just wondering if any one has any luck with this now? I am downloading QPST now.
It would be great if someone who already has a grandfathered PAM ability for their Hero to try this and report what they are seeing. Also the output from ##DATA# to see what if anything there is different.
Same Thing
No Joy.
I just followed the same steps and had the same thing happen as kmartburrito.
I'll get this to work, I've enabled PAM on every sprint phone I've had since they introduced the unlimited data plan bout 5-6 years ago
we're going to get the MSL number and instead of writing to phone we'll just edit the settings in phone (safer than hard writing stuff that might screw with your MEID & ESN settings)
I'll post when I get it to work, just wanted to let yall know I'm hot on it.
**********************************************************
This is a modified guide I wrote for the instinct that will walk you through how to get your MSL code and what to do with it.
DISCLAIMER, I am ###NOT### responsible for any damage you do to your phone or your phone network with this information
**********************************************************
some uers still getting errors, if you fall into this catagory, you can recover via SPRINT RUU which will wipe your phone
ftp://xda:[email protected]rs.co...U_Hero_C_Sprint_1.29.651.1_signed_release.exe
---- How to access programming and service menus---
On your phone go to the dialer, then dail in any one of these codes below and after the last # you should get the menu or it will ask for "current code" aka your MSL #
##data# (##3282#)
##debug#(##33284#)
##diag#(##3424#)
##svn#(##786#)
##prl#(##775#)
##prev#(##7738#)
##akey#(##2539#)
##vocoder# (##8626337#)
-------How to get your MSL code---------------
1) download required 3rd party apps
download demo version of CDMA WORKSHOP from
http://www.cdma-ware.com
newest version of qpst 2.7b323
http://rapidshare.com/files/297770360/qpst.zip
download of sprint's official phone as modem (PAM) software
Smartview for Windows
http://www4.sprint.com/pcsbusiness/down ... s_1.16.exe
Smartview for Macs
http://www4.sprint.com/pcsbusiness/down ... c.mpkg.zip
download HTC Sync
http://www.htc.com/us/SupportDownload.aspx?p_id=300&cat=3&dl_id=716
2) install the HTC HERO DIAG drivers
http://rs79.rapidshare.com/files/293529424/HTC_Hero_DIAG_Drivers.zip
3)connect your phone via usb cable
4)dial ##diag# (##3424#) on your phone for diag menu, when prompted direct windows to diag drivers listed above
5)run CDMA WORKSHOP, settings at main screen on the right are as follows
com settings (AT mode)
---------------
Port (com#) <--- click port and it should say "HTC DIAG COM PORT"
Baud rate (115200) <--- use this setting
com settings (DM mode)
---------------
Baud rate (115200) <--- use this setting
6) you should now be able to hit <connect> if it was successful you'll see in status bar <connected to com#>
7) now click <read> after a moment all your info will come up on left panel, phone # etc
8) click on security tab change the right panel setting and look for the following block
SPC/User Lock
----------------
Defualt (nv_read) <--- use this setting
9)now click read if done sucessfully you'll see the block below this option flash red and give you a number
10)note the 6 digit number under <SPC/USER LOCK> the one that flashed red, ****this is your MSL number***
***** just an additional warning***** you can REALLY and I mean REALLY screw up your phone if you change one of the settings in those menus if you don't know EXACTLY what you are doing. This isn't for the faint of heart or the random tinkerer.... just be warned
;;;;;;;;;;;;;;;;;;;;;;
So in reading your post, it seems the only thing I haven't done is modify my profile 0 in qpst, since I've already modified profile 1 per the guide on insiderforums in the original post by gilroykilroy. Does all that sound correct?
Thanks for writing up that guide Johnson!
If I understand the directions johnsongrantr posted you are replacing the profile 0 NAI with the profile 1 NAI. I tried that and after it initially seemed to work it gave me error 67 when I booted my phone and tried to connect to the network and/or trying Update Profile.
Also note that my phone has [email protected] (not mcs.sprintpcs.com).
I seem to have better luck leaving the settings along and using the race-condition method.
Alas still no luck getting my Mac to recognize the phone connection.
Updated profile 0 as described but still getting error 65/67. Is there some other step to turning on the PAM other than in the setting "Mobile network sharing"?
Update:
Just tried to update profile: cannot update profile and get Error 67.
redcloud said:
Updated profile 0 as described but still getting error 65/67. Is there some other step to turning on the PAM other than in the setting "Mobile network sharing"?
Update:
Just tried to update profile: cannot update profile and get Error 67.
Click to expand...
Click to collapse
it worked on mine, but it may be something to do with your account.... you can recover via SPRINT RUU which will wipe your phone
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
UPDATE: the [email protected] is hcm, I wasn't paying attention, I'll try copying that over and see if I have the same results.... my [email protected] worked on my htc mogul as well... let me give it a shot though
UPDATE2:the number you deleted is your ESN in hex format you'll see it at the top right in service programming just replace it with "number"@hcm.sprintpcs.com and paste it in tethered NAI, sorry for any confusion
johnsongrantr said:
it worked on mine, but it may be something to do with your account.... you can recover via SPRINT RUU which will wipe your phone
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
UPDATE: the [email protected] is hcm, I wasn't paying attention, I'll try copying that over and see if I have the same results.... my [email protected] worked on my htc mogul as well... let me give it a shot though
UPDATE2:the number you deleted is your ESN in hex format you'll see it at the top right in service programming just replace it with "number"@hcm.sprintpcs.com and paste it in tethered NAI, sorry for any confusion
Click to expand...
Click to collapse
Nope, still 65/67 errors here with NAI and Tethered NAI of profile 0 being the same string:
[email protected]
There must be something else to change.
I've also tried this to no avail... tried a few different things:
1) tried replacing the Profile 0 NAI with the Profile 1 NAI
2) tried copying the Profile 1 NAI to the Profile 0 Tethered NAI
3) tried copying the Profile 1 NAI to the Profile 1 Tethered NAI
4) tried replacing all Profile 0 settings with Profile 1 settings
5) tried copying Profile 1 settings to Profile 2
Nothing seemed to help.... still errors.
Yep...same for me, I've updated the tethered NAI in both profile 0 and 1, reset the phone, waited for a half hour, and still get the error 67. Keep on brainstorming guys, we'll beat this thing
can anyone put the rapid share files up on a different server or sharing place, rapid share is terrible. plus i can't download. it says there are no more open slots to download from. i need the qspt and the drivers. thanks in adavance
WRMG3 said:
can anyone put the rapid share files up on a different server or sharing place, rapid share is terrible. plus i can't download. it says there are no more open slots to download from. i need the qspt and the drivers. thanks in adavance
Click to expand...
Click to collapse
Here you go man, this is to a zip file called "HTC Stuff" that has both QPST 2.47.323 and the HTC Diag Drivers.
http://www7.zippyshare.com/v/50608704/file.html
thanks man, i figured i would give this a try when i got home. rapid share for some reason wouldn't let me download it and kept telling me that i had to be a premium member to download the files.
have you had any luck getting this to work on your phone?
WRMG3 said:
thanks man, i figured i would give this a try when i got home. rapid share for some reason wouldn't let me download it and kept telling me that i had to be a premium member to download the files.
have you had any luck getting this to work on your phone?
Click to expand...
Click to collapse
Nope, no luck yet. I along with a few others have had the same resulting 65/67 errors after updating the NAI settings on both profiles, so still now it's a no-go. I don't know if it's working on anyone's CDMA Hero at this point, so we may have to wait until it is rooted, which I can only imagine when that will happen, although hopefully soon!
This was posted on another forum just passing it on to help people get better call quality on the DI....
below_radar_00 said:
I too was experiencing terrible signal problems. I dropped two calls yesterday and I've NEVER dropped a single call in my 3-4 years with VZW. I looked in my phone status and my signal was a -101 which apparently isn't good. Anyways I found a site that has the newest PRL and another site with how to install. With this new PRL installed, my signal is now -91!!!!
First go to this site: HowardForums: Your Mobile Phone Community & Resource - Newest 650XX Hybrid PRL and find the post from 5/10/10 that has two zip files. Download the 65133 zip and unzip it. You'll find an RLA file in there. Copy the RLA to the root of your SD card. Then dial ##778 and send. You'll get a popup to view or edit. Hit edit. A password prompt comes up and your password is 000000 (six zeroes). Then scroll down to PRL and hit update PRL. It'll take a few seconds for the screen to change. When it does select for it to find all files and scroll down to the 65133 file and hit okay. Then you'll be back at the previous menu. You aren't done yet though. You have to hit the MENU key and select commit. Your phone will update and restart. Congrats you have updated your PRL!
To help others it may be beneficial to go to your phone settings BEFORE you update and post your before signal and then after the update go in again and post your after signal. If this was helpful please thank me!
Click to expand...
Click to collapse
Updating the PRL via *228 will overwrite the manual change.
More about it here.... http://forum.xda-developers.com/showthread.php?t=673661&highlight=update
Altell PRL
You can also just hit ##775 call and enter the six zeros and it will take you directly to the PRL update. you won't have to navigate the menu.
Hi everyone... when I dial ##775 or ##778 it just tells me thank you for calling verizon but my call cannot be completed as dialed. I've tried someones suggestion to put a # after the number as well and that gets me the same result.
Any ideas why this happens?
maly01801 said:
Hi everyone... when I dial ##775 or ##778 it just tells me thank you for calling verizon but my call cannot be completed as dialed. I've tried someones suggestion to put a # after the number as well and that gets me the same result.
Any ideas why this happens?
Click to expand...
Click to collapse
I would have to say user/phone error. Phone | ##778 | Call You will be prompted for a password.
maly01801 said:
Hi everyone... when I dial ##775 or ##778 it just tells me thank you for calling verizon but my call cannot be completed as dialed. I've tried someones suggestion to put a # after the number as well and that gets me the same result.
Any ideas why this happens?
Click to expand...
Click to collapse
This can't be done on some custom roms because the epst pack is left out.
maly01801 , I have never tested this, but I have heard that ##7764726 will work for roms without the EPST module. Let me know if it works.
Inc specific directions included in wiki btw...
Incredible PRL altering in Wiki
I am on Stock 2.1, Rooted
For some unknown reason I have lost ability to go into EPST from phone by ##778 code.
QPST is working in diagnostic mode.
Does anyone know what could have caused this and more importantly how to get it back.
Any suggestions would help.
I have searched many places but did not find answers.
seconded...
EPST works fine on my rooted/2.1 stock phone... not on my wife's. None of the ##xxx codes works.
Weeks after rooting my DInc w/ unrevoked 3.0, I decided it was safe to go ahead and do the same on my wife's phone. It's 2.1 stock, rooted with unrevoked 3.1/CM 2.5.0.x...plus the wifi tether kernel for AP mode wifi. Deleted CityID and installed root apps Ti Backup (full version), IncrediLite, and AdFree (which required manual symlinking /system/etc/hosts --> /data/data/hosts).
That's IT. Her phone is simpler in terms of apps installed. There's very little there that I haven't also done to my own phone... she has HandCent SMS where I don't; rooting method plus clockwork recovery were/are newer, and I never quite got AdFree working on one of the handsets.
I've no idea why this happened to one phone and not the other...I don't understand the where the config files are stored, or how the dialer accesses the 'hidden' menu. Unless I find an informative answer, I'm just going to try unrooting hers & reverting to stock...
figured out a few things
running ASTRO's process manager on my W's rooted phone, I see that dialing ##778 does invoke an instance of EPST... but you don't get the view/edit mode dialogue.
Trying to launch EPST from the ASTRO process mgr ("go to application") gives the view/edit choice, and if you hit edit you are prompted for the password... but after typing in 000000 it just hangs on 'wait while verifying password'
logcat has lots of entries containing 'epst' but I don't know how to interpret them.
I notice that the com.google.android.epst file lives in /data/data, where one has to muck around when getting a hosts file symlinked for AdFree...but I didn't do anything clumsy, and the permissions are rwxr-xr-x which looks right.
That's about as far as I can go. Anyone know what breaks EPST?
QPST workaround...
I guess this problem must be pretty isolated since no one has responded... but fwiw, as OP alluded, Qualcomm's QPST utility offers a workaround if you can't launch EPST from your phone/dialer:
1. Find a copy of QPST 2.7 build 323 (don't ask me where). Install to PC.
2. Install HTC Sync (for drivers), then Connect phone as 'charge only' via USB with debugging enabled.
3. Open Device Manager and look under Ports to find which COM# is the HTC Diagnostic Interface.
4. Launch QPST Configuration applet. Click the Ports tab, then Add New Port. Select the COM port you found in Step 3 from the list at left, then hit OK. Your phone should now show up under the Active Phones tab as FFA/Surf QSD8650 Rev. 2.0. If not, unplug phone, dial ##DIAG#, wait 10s and plug back in as in Step 2.
5. Open the QPST Start Clients menu & choose Service Programming. Select your phone, hit OK, then click 'Read from Phone' button in the resulting window.
6. You now have access to the same configuration items you normally reach via ##778 on your phone. 'Write to Phone' will commit any changes you make, without further warning.
Obviously it is possible to seriously BORK your phone from here, requiring a restore from backup (which you should have before trying this). I take no responsibility for what you do with QPST. I used it only to change the tethering NAI from <number>@dun.vzw3g.com --> <number>@vzw3g.com so I could tether my wife's DINc. via Windows DUN. That worked, but I can't guarantee the results of other edits.
Same issue
Sorry to resurrect an old thread, but I am having nearly the same issue.
When I try to access epst from dialing ##778# on my girlfriends hero nothing happens at all. I ended up adding a shortcut with anycut and now the view or edit menu comes up. When I hit view it just hangs when I hit edit and enter the password it stays on "please wait verifying password". I can get ##data# to work and a few other ##xx# codes to work but I need access to the epst advanced settings.
Any help would be greatly appreciated, I have tried 1.5 stock 2.1 stock Fresh versions 2.1.3 (i think that's right) Fresh 2.3.3 and Damage control 2.09.....
I have qpst and CDMA workshop 2.7 but I know there are more options I need to change to get data on cricket. I don't have the $100 to spend on the new version on CDMA workshop.
Thanks in advance.
I'm on stock 2.2 rooted with s-off. To remove software like CityID I connected using 'adb' ,
mounted /system in clockwork recovery and moved the 'apk'
files to another folder. Now after this when I reboot I'm
not able to ##778.can I regain epst
Regards
Ananth
Try ##778#
Same result .##778# also does not work
I had this same problem while trying to get ad free working on my wifes phone. Some how all the messing about in /system changing permissions and creating symbolic links messed up epst and I couldn't get in except by using qualcomm tools on my pc. That was on 2.1...i only got 778 back when I upgraded the radio to 2.5 and flashed to rmk's froyo rom. Even then, I got a weird error when I tried to edit the dun entry...some thing about the radio and failing to enter low power mode...it went away after the first edit. I don't think doing a data wipe or rom flash clears epst data, so I'm guessing it was the radio upgrade that fixed the problem. I do wish someone could tell us what it is about editing stuff in /system that screws up ##778 access...
cantare said:
I had this same problem while trying to get ad free working on my wifes phone. Some how all the messing about in /system changing permissions and creating symbolic links messed up epst and I couldn't get in except by using qualcomm tools on my pc. That was on 2.1...i only got 778 back when I upgraded the radio to 2.5 and flashed to rmk's froyo rom. Even then, I got a weird error when I tried to edit the dun entry...some thing about the radio and failing to enter low power mode...it went away after the first edit. I don't think doing a data wipe or rom flash clears epst data, so I'm guessing it was the radio upgrade that fixed the problem. I do wish someone could tell us what it is about editing stuff in /system that screws up ##778 access...
Click to expand...
Click to collapse
how did u get qualcomm tools to see the phone? i'm using qpst and it's not seeing the phone at all.
and i get teh same error about 'no response from radio; can't enter low power mode' however it won't go away no matter how many times i try to commit.
shortbushemi said:
how did u get qualcomm tools to see the phone? i'm using qpst and it's not seeing the phone at all.
and i get teh same error about 'no response from radio; can't enter low power mode' however it won't go away no matter how many times i try to commit.
Click to expand...
Click to collapse
I got around that error by turning off every possible radio: 3g, wifi, all the gps stuff, and then putting in airplane mode for good measure. Reboot, make sure it's still in airplane-mode/everything off, and then try ##778 again. Don't know if it matters, but I tried to minimize steps in EPST--ie., open only Security and m.ip and edit only the two relevant entries; don't click on or view anything else. When I did all that, I got the changes to stick, and they stayed with the phone thru several upgrade flashes of Virtuous 2.x ROM
As for QPST, it's been a while... but you must plug the phone into usb (can't remember if you need debugging enabled), then dial ##3424#, wait several seconds (might have to install some htc drivers, but you may be able to ignore) then check your device manager for a new COM port called "htc diagnostic interface... and/or just start qpst config, add new port, and select the one that looks right. it will call the phone something different---ffa./surf or something, but you should be able to view and program service info.
I also got this message when i was trying to edit all that crap to get the 3G Mobile HotSpot app to work. what i realized is that it gives me that error only when i back out of the menu that lists the settings. If you are editing, you should edit, then close the text box (click ok) and then commit changes directly from that menu, and not back out.
Hey Folks,
So over in the republic, we are working to root our phone so that we can enjoy the life of a rooted user, but unfortunately RW has not provided us with the SPC and sadly it is not 000000. We have tried many methods of recovering the SPC, like parsing logcat logs while accessing ##DATA# ##SVN#, etc. We have tried getprop with zero luck also.
I wanted to know, if there is a way to validate the SPC via adb cli. For instance, I was thinking of attempting to change a setting on the phone by passing through an SPC code and either getting a success or error. This way I could create a script to attempt all possible SPC codes until it hits success.
Any advice or insight would be much appreciated.
Want to be on this thread.
Also looking for any suggestions about how to get the Defy XT 557 into DIAG mode so COM port can be opened for connection to QPST, QXDM, RadioComm, CDMA workshop, etc.
Thanks in advance.
Diagnostic COM port (COM13) opens on Defy XT557 (Republic Wireless) using SUT LR 1.82, but without the MSL/SPC, not able to finish the process to obtain root.
cmm324 said:
Hey Folks,
So over in the republic, we are working to root our phone so that we can enjoy the life of a rooted user, but unfortunately RW has not provided us with the SPC and sadly it is not 000000. We have tried many methods of recovering the SPC, like parsing logcat logs while accessing ##DATA# ##SVN#, etc. We have tried getprop with zero luck also.
I wanted to know, if there is a way to validate the SPC via adb cli. For instance, I was thinking of attempting to change a setting on the phone by passing through an SPC code and either getting a success or error. This way I could create a script to attempt all possible SPC codes until it hits success.
Any advice or insight would be much appreciated.
Click to expand...
Click to collapse
Bump, still need help with this issue.
cmm324 said:
Bump, still need help with this issue.
Click to expand...
Click to collapse
+1
Sent from my XT557 using xda premium
Moved to Q&A. Please ask all questions there, thanks.