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!
Yay, I've finally found a reliable way to do this. After completing these steps, you'll be able to install any GSM Hero ROM. Still, neither I, nor anyone else, can be blamed if something goes wrong and you end up with a shiny paperweight.
-2. Changelog
16/11/09
Updated to Amon_RA's latest recovery image
15/11/09
First release of the guide!
-1. Thanks!
This guide would not have been possible without:
TheUnlockr (great guides)
Amon_RA (recovery image)
xda-developers (need I say more?)
MoDaCo (Excellent ROM)
QMAT (GoldCard)
craig0r (first to root the Telus Hero)
pi3ch (copy from cmd)
And everyone involved in rooting the Dream, the Sapphire, the Hero, and Android in general. Many thanks to everyone involved!
0. Before we start!
If you haven't installed all the drivers for your phone already, follow the instructions on this page to do so. It also shows you the basics of ADB.
Also, a forewarning: there are reports that not all microSD cards work. If yours doesn't work, try another one. Hopefully you'll still have some dough in your wallet by the time you find one that works. Just kidding.
Also, not all microSD readers work either. I have one that just refused to write the GoldCard image to the card, but thankfully, my laptop's SD slot worked.
And, these steps have only been tested on Windows XP 32bit. If you use anything newer, it may or may not work, but most importantly, if you want any chance of it working, you'll want to run most of these apps and commands in Administrator mode.
Finally, make sure you have a Wi-Fi connection, as your data connection will be lost at some point while you need to download something from the Market.
1. Downloads!
You'll want to get all your downloads before starting this.
HxD
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
flashrec
Amon_RA's recovery image
Updated radio
2. Prepare your phone!
On your phone, go to:
Settings > Applications > Development
There, check USB debugging.
3. Backup your APN settings!
Go to the Market and install APN Backup and Restore. Run it, and backup your APN settings with it. This is necessary to restore data access after rooting.
4. Get your GoldCard image!
The GoldCard bypasses some weird check on the phone and allows you to flash ROMs that are otherwise rejected, due to them being older versions, or some other reason that HTC decided it'd be so.
With the USB cable plugged in, open the notifications shade and tap HTC Sync. It doesn't matter if it can't sync, but what matters is you can enter the adb shell. If you don't know how, you haven't done step 0.
Now, go in adb shell and run this command:
Code:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
The output is your microSD card's serial number. Right click anywhere in the command prompt, and click on Mark. Then, select the serial number, and right click. The serial is now copied into the clipboard, so open up Notepad and paste it there.
Now, with that serial number written down, paste it into my lame GoldCard hex reverse. Please credit me if you use that page in your guide!
Next, do as my page says, grab the reversed serial number and get your GoldCard image with it.
5. Create your GoldCard!
So now you have your GoldCard image. Remember, this GoldCard image is valid only for the card from which you got the serial number. If you use another card, get another image.
Turn off your phone, take the microSD out and plug it into the your preferred reader. Again, not all readers work. Not all microSDs work.
Now, unplug from your computer any removable storage except for the microSD. This is to avoid confusion in the next step.
Before making the GoldCard, backup anything you need from the microSD, as it may get erased in the process. Most importantly, backup the APN settings that we got earlier, from APN Backup and Restore.
Now open up HxD. From here, you'll open two things. Your microSD in the raw, and the GoldCard image in the raw.
To open your microSD go to:
Extras > Open disk
In the pop up, under Physical disks, select the (supposedly only) Removable Storage. If there are two, I don't know which one is the right one, so unplug more stuff from your computer.
Before you click OK, be sure to uncheck Open as Readonly. We can't make a GoldCard if we can't write on it, right?
To open your GoldCard image, go to:
Extras > Open disk image
There, select your downloaded goldcard.img file, and click Open, and then OK.
Now you should have two tabs open in HxD, one being the microSD, and the other, active one being the GoldCard image.
Press Ctrl+A on your keyboard to select all, then Ctrl+C on your keyboard to copy. Switch to the microSD's tab, make sure the cursor is at the complete top-left corner, and then press Ctrl+B to paste, and then Ctrl+S to save. Accept the risk and your GoldCard should be made.
To verify, close the microSD's tab, eject it, unplug and replug it, and reopen it in HxD like we did earlier. It should still have the GoldCard image written at the beginning of it. If not, either the microSD or the reader or both don't like making GoldCards, so you'll want to try a different combination of card and reader.
6. Downgrade!
Let's flash the downgraded ROM now. Plug your microSD, now a GoldCard, into the phone and turn it on. After it finishes booting, turn on HTC Sync. Again, it doesn't need to actually synchronize.
Now, run the RUU you downloaded earlier and follow the steps. If the GoldCard works, it should flash and you'll end up with a downgraded phone. If not, then you either didn't write down the microSD's serial number correctly, or the microSD doesn't like to do its job.
Set up the downgraded phone with the default settings, and turn on Wi-Fi. Get on your Wi-Fi network and install Linda File Manager.
Now, on the phone, check:
Settings > Applications > Unknown sources
Now turn on USB Storage, and copy flashrec and Amon_RA's recovery image to the microSD. Rename the recovery image to recovery.img to save a headache later. You may as well put the backed up APN files back on the microSD too, if they got erased.
Disconnect USB storage, load up Linda, go in the SD card, and install flashrec using Package Installer. Now, load up Recovery Flasher, press on backup, then type in:
Code:
/sdcard/recovery.img
Now press Flash recovery.
7. Update the radio
The radio that came with the downgrade is quirky in North American networks. We'll update to the latest IU radio, which works with our networks here.
First, reboot into the new patched recovery. Turn off the phone, and then turn it back on while holding the Home button. Keep holding it until you see the recovery menu.
Once you're there, scroll down using the trackball to turn on USB Mass storage. Plug the phone in the computer if it wasn't plugged already. The microSD will show up on the computer. Copy the updated radio zip to the root of the microSD wait a few seconds, then turn off USB Mass storage on the phone.
Now, select Flash update image, and then Apply sdcard:choose zip. There, the radio zip should show up. Select it and flash it.
8. You're pretty much done at this point.
Follow any guide to install a Hero ROM, to partition your microSD, etc. After you install a custom ROM, be sure to reinstall APN Backup and Restore from the market, and restore your APN settings. This will restore data.
well the "asroot" method of rooting from the guide in the CDMA forum may be worth trying...perhaps they haven't fixed the vulenrability?
http://forum.xda-developers.com/showthread.php?t=581577 (all the way up to before the recovery image)
Ya tried that method don't work
yeah I would love to root this thing.
To be honest this is my first smartphone and I'm new at this rooting thing. I did manage to throw on a hack for my ipod nano (colored version)
I'm loving this phone so far - got it first day they announced their new network. I'm so impressed
Did either of you buy another SD card? Where did you grab yours if you did?
My Telus Hero has been rooted since Friday.
Check it:
http://forum.xda-developers.com/showpost.php?p=4909063&postcount=16
Yeah I just saw. I'll get familiar with the process then update the first post.
Thanks a bunch!
I posted in the other thread (so... sorry for the double post), but I think that this thread is more relevant to the question/issue of rooting.
Could someone who still has the stock Telus ROM post the Baseband version? (Home -> Settings -> About phone -> Baseband version)
I'm just curious as to whether we Telus users should upgrade or downgrade the radio version after rooting the phone, as I seem to be having dialing issues (long distance numbers require a "+" in front of the "1" or it won't connect.)
I dunno if this issue would be related to the radio, or to the fact that there are no North American locales selectable within the custom ROM.
Stock Baseband
63.18.55.06DAU_6.35.08.20
Still wating to see how others are successful with rooting their Telus Hero.
sjeffrey said:
63.18.55.06DAU_6.35.08.20
Still wating to see how others are successful with rooting their Telus Hero.
Click to expand...
Click to collapse
Same here. My stock Telus Hero reports the same version as above (just to add to the data pool). I'll be watching this thread for more details on rooting.
I rooted using the goldcard>2.73.405>recovery>modaco2.9>IU baseband and it works no problem. I can dial 611, long distance numbers dont need a + or a 1 for that matter, and market enabler lets me buy paid apps. Device seems quicker. I had to try 3 different sd cards though. I know I was doing the first one wrong, but one of them definately did not work.
I mentioned in the other Telus Hero thread that I updated my radio to the IU version, and my dialing issues have gone away. Thought I should mention it here as well.
I'm still waiting for a method that doesn't require calling Telus to fix settings though.
Say, is your Hero the black or white one? And, is it a HERO130 or a HERO100?
I keep getting an invalid model ID error when I try flashing the downgrade. Is that what you had the times it didn't work for you?
Soaa- said:
I'm still waiting for a method that doesn't require calling Telus to fix settings though.
Say, is your Hero the black or white one? And, is it a HERO130 or a HERO100?
I keep getting an invalid model ID error when I try flashing the downgrade. Is that what you had the times it didn't work for you?
Click to expand...
Click to collapse
Yeah, I'm pretty sure that's the error I got when I didn't have a proper Gold Card. If you've tried the same SD card a number of times and it's still not working, maybe grab a cheap Sandisk 1GB card. That's what I used.
And you shouldn't have to call Telus, because I've already gone through the pain of figuring all this stuff out. Just make sure you grab the APN settings from the other thread, and update to the latest radio (IU) and you're good. A call to Telus was required because I couldn't receive MMS messages, but that had nothing to do with rooting the phone, I would've had to call them anyway.
When I look up "Model Number" in my phone's settings, it just says HTC Hero. So I dunno. The custom ROM probably did that. I guess.
the model name might be written in the battery compartment area. i know on my htc tytn the name is there as "HERM200"
pretty sure it was mentioned that the telus hero is HERO130
As profets said, the model ID is under the battery. Mine says HERO130, and in bootloader mode, it says HERO13000. Since the downgrade ROM is for HERO10000, it threw an invalid model ID error.
Soaa- said:
As profets said, the model ID is under the battery. Mine says HERO130, and in bootloader mode, it says HERO13000. Since the downgrade ROM is for HERO10000, it threw an invalid model ID error.
Click to expand...
Click to collapse
Ah cool. I just checked under the battery, it's a 130. So you should still be able to downgrade.
Really strange. I tried a Kingston 2GB like they said on the guide and verified that the GoldCard image was well written on the card. Yet it still throws error 130.
Soaa- said:
Really strange. I tried a Kingston 2GB like they said on the guide and verified that the GoldCard image was well written on the card. Yet it still throws error 130.
Click to expand...
Click to collapse
I used the 2GB sd card comes with the phone to create goldcard. Rooted.
No problem at all, I don't know why you guys wanna use other SD cards.
I'm pretty sure I've tried all my cards... I'll try again tonight.
Hah! Got it to work. Guide is done.
I also quickly put together a webpage to reverse the CID of the microSD. That way, people won't need to download QMAT anymore. The page can be found here: http://hexrev.soaa.me
Enjoy!
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.
According to the Vibrant forums, Jr33 has fixed and ported the MobileAP (native Infrastructure Wifi Tethering AP) from the Galaxy S i9000 to the Vibrant:
http://forum.xda-developers.com/showthread.php?t=756804
Why this is important and better than the Wifi tethering apps (Barnacle and android-wifi-tether):
This is REAL infrastructure mode. Not the hacked up ad-hoc mode (which android-wifi-tether and barnacle uses) which A LOT of devices (other android phones, ps3, wii, corporate laptops included) cannot connect to.
Because it being infrastructure mode, it supports WPA, a much more secure protection than WEP.
This is natively built into the Galaxy S i9000 phones. But taken out by AT&T and T-mobile. It just works, and works well - because it was MADE for our phones!
android-wifi-tethering hard crashes a lot on start, forcing you to do a battery pull, and may lose connectivity every so often.
Barnacle requires you to change the MTU of your client device, not possible in a lot of cases (consoles, phones, etc), and may cause conflicts when moving to a different wifi AP.
-------------------------------------------------------------------------------------------------------------------------------
Update 8/22:
Designgears has figured out a way to automatically launch the wlp2pservice on boot, therefore, no more manual entry is needed (but requires kernel flashing). Please see:
http://forum.xda-developers.com/showthread.php?p=7785171
The reason why it requires flashing the kernel (while Vibrant did not) can be explained by Jr33:
i know the stock kernel for the vibrant had the iptables included as well as wlp2pservice. what i have been finding is all these different features have just been commented out in different places. the same source was used for all three phones. you can see this when you start decompiling the odex files and comparing files, it is all the same. just needs a little tweaking here and there to activate certain features
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
Update 8/20:
With the help of Jr33 (person that did the port to Vibrant), we *kind* of got it working with a few hoops. Jr33 should be given credit as he created and repackaged the captivate MobileAP update.zip; I was merely a test dummy. This thread will be locked when a solution is made and Jr33 will create a new thread with the final version. Go buy him a red bull!
REQUIREMENTS
Update.zip downloaded below
Rom Manager
ClockworkMod Recovery flashed on your phone (using Rom Manager)
Busybox
An Android Terminal App (ex: http://www.appbrain.com/app/jackpal.androidterm)
DOWNLOAD The Captivate mobileAP update.zip:
http://www.mediafire.com/?ownoqzgo6cbtmoj
File is also attached at the end of this post.
INSTRUCTIONS
Rename to update.zip, put it on your INTERNAL SD card root
Boot into ClockworkMod Recovery (using Rom Manager) and reinstall/update packages.
Reboot - note: first time boot after updating this will take a little while.
Now go into an Android terminal app and type the following:
Code:
su
busybox nohup /system/bin/wlp2pservice &
This starts the wlp2pservice. (Props to designgears for finding out this new command)
Old command (just typing in /system/bin/wlp2pservice in terminal (does not require busybox)) works BUT you will need to keep Terminal open during the duration, if force closed, you will have to retype that command in again.
5. Now you can go into Settings -> Wireless and Networks -> Mobile AP Settings to start your Access point.
Note: if you change any of the settings (AP name or WPA password) it may crash wlp2pservice. Use a task manager to force close "MobileAP Settings." Do step 4 again and your settings should be there.
This works until you reboot your phone. If you reboot, you need to go back into terminal and manually start wlp2pservice again (do step 4 again).
If you do not manually launch wlp2pservice, when you open up MobileAP settings, it just sits there on a black screen and if you check logcat, you see the looping message pasted below. We are currently trying to fix the necessity of manually launching wlp2pservice. This is not how it was intended to be.
-----------------
Developers with a Captivate, we need your help:
Upon opening MobileAP settings WITHOUT manually launching wlp2pservice in terminal, yields the following (from logcat):
Code:
I/ServiceManager( 3459): Waiting for service WLP2PService....
It loops until you force close "MobileAP Settings" in your task manager. Something is not calling wlp2pservice to execute.
Also, rebooting the phone or closing/ending terminal (on the pc or phone) requires you to go back into terminal and execute wlp2pservice manually, otherwise opening MobileAP settings yields the same loop above.
I am guessing that wlp2pservice is not launching on boot, or not executing at all when you open up MobileAP settings. I'm not sure which is supposed to happen.
This *seems* like an easy fix, and because Jr33 does not have a Captivate it is hard for him to help troubleshoot this. This is why we need other people to help figure out a way.
According to the front page: Update: This is a mod to add in the Samsung version of Mobile AP intended for the Galaxy S, but was removed by T-Mobile.
It was also removed by ATT, so wonder if it is possible :/
andy2na said:
According to the front page: Update: This is a mod to add in the Samsung version of Mobile AP intended for the Galaxy S, but was removed by T-Mobile.
It was also removed by ATT, so wonder if it is possible :/
Click to expand...
Click to collapse
This would be excellent to be ported over. While the current wireless tether (found in the associated thread) works... it does it in ad-hoc mode. This apparently supports infrastructure mode which would make it even more useful.
Go mods go!
rickgrob said:
This would be excellent to be ported over. While the current wireless tether (found in the associated thread) works... it does it in ad-hoc mode. This apparently supports infrastructure mode which would make it even more useful.
Go mods go!
Click to expand...
Click to collapse
wireless tether and barnacle "work" but still require you to go through hoops.
Wireless tether hard crashes A LOT.
Barnacle requires you to change MTU in your OS.
Please see OP for Update.
andy2na said:
wireless tether and barnacle "work" but still require you to go through hoops.
Wireless tether hard crashes A LOT.
Barnacle requires you to change MTU in your OS.
Click to expand...
Click to collapse
Yeah i changed my mtu (took like 30 seconds) and barnacle works great now. I was able to register for my fall semester from disneyland last weekend
I hope this isn't too far off topic, but would it then be possible to use a similiar techique to restore usb tethering to captivate ROMS in which AT&T has it removed/disabled?
jsmith8858 said:
I hope this isn't too far off topic, but would it then be possible to use a similiar techique to restore usb tethering to captivate ROMS in which AT&T has it removed/disabled?
Click to expand...
Click to collapse
When did it get removed? And i doubt the mobileAP is anywhere near related to the USB tethering samsung includes.
I currently have the stock rom, it has usb tethering. Mobile ap is related since they're both tethering.
Perhaps I can extract the file out of my phone where I to be instructed how.
Sent from my SAMSUNG-SGH-I897 using XDA App
Bowsa2511 said:
I currently have the stock rom, it has usb tethering. Mobile ap is related since they're both tethering.
Perhaps I can extract the file out of my phone where I to be instructed how.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I guess if you want to be completely broad they are both tethering solutions....
But their implementation i would assume is different and dont affect each other.
thanks Andy for bring this to Jr33's notice to get this implemented for Captivate.
was wondering if there is any app which wld start this service on boot or something like Tasker if it can start a system service.
Thnx
when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??
Edit: removed
pewpewbangbang said:
when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??
Click to expand...
Click to collapse
It's not a signed .zip bro. You need to download rom manager off the market if you don't have it, then reboot recovery from it and it will put you into clockwork recovery mode and then run the update.zip from that. It also lets you run other .zips even if they aren't named update.zip.
Hope that helps ya!
Sent from my GT-I9000 using Tapatalk
anilkuj said:
thanks Andy for bring this to Jr33's notice to get this implemented for Captivate.
was wondering if there is any app which wld start this service on boot or something like Tasker if it can start a system service.
Thnx
Click to expand...
Click to collapse
I thought about that, but because it has to start your terminal program and execute the wlp2pservice (and leave it running), I'm not sure if it had a large impact on battery life.
I setup Better Terminal Emulator to have a shortcut key to type out "/system/bin/wlp2pservice" for me, so its a few taps and Its ready. The amount of tethering I do right now is not that often that this is a big deal, but would be nice..
pewpewbangbang said:
when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??
Click to expand...
Click to collapse
My bad, it should be "Reinstall Packages" then after selecting it, it makes you scroll down past all the No's to Yes, install package.
Make sure when you open up when you open up Rom Manager you see:
Current Recovery: ClockworkMod 2.5.0.4, if not tap Flash ClockworkMod Recovery. (maybe reinstall it just incase) Then tap reboot into recovery.
Ahhh yes got it. Thank you, I didn't flash my rom before. Got it to work now. Thanks =)
As a quick note:
Please mod alert the Original Post to get this moved back to the Captivate development forum, so more developers that know what they are doing can see this thread and hopefully chime in.
This *seems* like it would be an easy fix. wlp2pservice just needs to launch at boot.
New problem. When I try to run the command in android terminal is says
/system/bin/wlp2pservice
not found
Ok I ran into the same problem because my clockworkmod was borked, so I had to reflash Clockwormod Recovery. When you tap Flash Clockworkmod recovery, it replaces update.zip in your root of the SDCard, so when you hit reinstall/update packages, it just reinstalled clockworkmod recovery again, no harm done.
So what you need to do is redownload the mobileAP zip and replace the current update.zip with the one found in this thread.
Go back into Rom Manager and reboot into recovery (dont hit flash clockworkmod), then update/reinstall packages, it should work then.
(UPDATE: 8/24/11 New flashable update.zip for install via recovery, includes Gscript (credit goes to PinkVenture for developing the app!) and my simple on/off scripts already installed. You can link shortcuts directly to the desktop for each ON or OFF through add shortcut on homescreen, see attachments at the end of this post)
I'll start this off by mentioning that all the threads you may find saying "CM7 DIAG Enabled!" such as this one here Etc, are not valid solutions for OUR device. That may/may not work with the eris/hero(haven't tried) etc as those topics discuss. They merely SPECULATE it will for any CM7 based rom - it doesn't for ours.
echo 1 > /dev/qct_diag_enable (to enable diag mode)
..and your phone should go into USB diag mode. when you are done just:
echo 0 > /dev/qct_diag_enable (to disable diag mode)
Click to expand...
Click to collapse
WONT DO ANYTHING for you. In fact, it made my "qct_diag_enable" file disappear. Scroll to the bottom to skip my bantering and explaining of the reason this is a useful feature for people like myself, and to just show the actual findings of this thread.
So you have CM7 and (of course) are lovin' it. The only thing is you have an alternate carrier (cricket personally) and hate the fact that manually switching prl's or needing to change your EPST settings can be a pain (since CM7 has no EPST built-in!). Especially when its [*feature name here] that you would LIKE to have the ability to use, but can live without if it means having to restore (or flash one if you have no backups) a sense rom just to change any of your EPST (##778, etc) settings.
Well, if you know anything about QPST for windows (google), then you know that you need to have your phone in DIAG mode to use it (##3424) and have the hero diagnostic drivers installed on your windows machine. (For the record, I'm an Ubuntu man and my main machine is NOT dual boot, meaning I still have to switch to my windows laptop to use QPST >< but we'll just pretend you have windows and this is more convenient for *you*).
Back to the point, once you've realized all the hassle, yada yada, you just say, "Ill just fix it later, I can live without it for now." AND how sick you are of saying that, here is the solution to no longer switching ROM's for EPST, as there IS a way without the ability to ##3242 in CM7 to enable DIAG mode.
(NOTE: This is also useful for those of you already on CM7 WITH Verizon/Alltell who would like to follow the guide in the Development section Droid Incredible Wiki regarding switching to the whole Verizon PRL/Alltell Hybrid PRL, along with other guides involving EPST or ## codes found there)
Simply go to (via adb shell/terminal emulator) /sys/devices/virtual/usb_composite/diag and run (1 for on and 0 for off, respectively)
Code:
echo 1 > enable
echo 0 > enable
To simplify all this I've included a zip file which includes Gscript.apk for you to install, and two scripts in the Gscript directory (place entire Gscript directory on root of sdcard). Open Gscript application, then once open - menu button>add script>load file>diag on/off.sh>save for each script respectively. Then you can simply toggle on/off DIAG mode from the Gscript application (or even add shortcut>gscript>diag on/off from CM7 home screen, for each script respectively). And without further excess explanation, here's the .zip signed-diagscripts.zip flashable update.zip file for recovery
By the way, if a mod reads this, could you please move to the Development section and remove my restriction? I know I don't have my whole 10 posts etc, etc, but I don't really have enough to say or the patience to say it most of the time to post 10 posts. However, I've lurked these boards and been rooting phones and flashing phones via this forum since my first android phone back from what feels like ages ago. (going on 4 rooted and flashed to cricket android phones now, all sold except my current, Dinc)
cool, thanks, man!!!
Sure thing, let me know if anyone experiences issues by pm or reply. I was thinking about compiling an installable zip so this can be installed after rom in recovery too.
Sent from my ADR6300
Just wondering... Any idea if this will work on Evo as well?
Work on the EVO too?
Yeah, I would really like to know if this would work on the evo!!
hydrosity said:
I'll start this off by mentioning that all the threads you may find saying "CM7 DIAG Enabled!" such as this one here Etc, are not valid solutions for OUR device. That may/may not work with the eris/hero(haven't tried) etc as those topics discuss. They merely SPECULATE it will for any CM7 based rom - it doesn't for ours.
WONT DO ANYTHING for you. In fact, it made my "qct_diag_enable" file disappear. Scroll to the bottom to skip my bantering and explaining of the reason this is a useful feature for people like myself, and to just show the actual findings of this thread.
So you have CM7 and (of course) are lovin' it. The only thing is you have an alternate carrier (cricket personally) and hate the fact that manually switching prl's or needing to change your EPST settings can be a pain (since CM7 has no EPST built-in!). Especially when its [*feature name here] that you would LIKE to have the ability to use, but can live without if it means having to restore (or flash one if you have no backups) a sense rom just to change any of your EPST (##778, etc) settings.
Well, if you know anything about QPST for windows (google), then you know that you need to have your phone in DIAG mode to use it (##3424) and have the hero diagnostic drivers installed on your windows machine. (For the record, I'm an Ubuntu man and my main machine is NOT dual boot, meaning I still have to switch to my windows laptop to use QPST >< but we'll just pretend you have windows and this is more convenient for *you*).
Back to the point, once you've realized all the hassle, yada yada, you just say, "Ill just fix it later, I can live without it for now." AND how sick you are of saying that, here is the solution to no longer switching ROM's for EPST, as there IS a way without the ability to ##3242 in CM7 to enable DIAG mode.
(NOTE: This is also useful for those of you already on CM7 WITH Verizon/Alltell who would like to follow the guide in the Development section Droid Incredible Wiki regarding switching to the whole Verizon PRL/Alltell Hybrid PRL, along with other guides involving EPST or ## codes found there)
Simply go to (via adb shell/terminal emulator) /sys/devices/virtual/usb_composite/diag and run (1 for on and 0 for off, respectively)
Code:
echo 1 > enable
echo 0 > enable
To simplify all this I've included a zip file which includes Gscript.apk for you to install, and two scripts in the Gscript directory (place entire Gscript directory on root of sdcard). Open Gscript application, then once open - menu button>add script>load file>diag on/off.sh>save for each script respectively. Then you can simply toggle on/off DIAG mode from the Gscript application (or even add shortcut>gscript>diag on/off from CM7 home screen, for each script respectively). And without further excess explanation, here's the .zip gscript_diagscripts.zip
By the way, if a mod reads this, could you please move to the Development section and remove my restriction? I know I don't have my whole 10 posts etc, etc, but I don't really have enough to say or the patience to say it most of the time to post 10 posts. However, I've lurked these boards and been rooting phones and flashing phones via this forum since my first android phone back from what feels like ages ago. (going on 4 rooted and flashed to cricket android phones now, all sold except my current, Dinc)
Click to expand...
Click to collapse
so wait let me get this straight. this mod is so we can update our prl??? or is this for people that would like to still run the altel hybrid prl?
because a simple *22899 will let you update it. i know this because i have been on cm7 nightly from day one and there was 1 update of the prl and it worked.
EVO + CM 7 + this solution = GO (GREEN LIGHT) WORKS.
Is there any way of running the ##3282# (if it's a file you run or an APK you install?)
Hows about this
i got one better for ya.
Code:
am start -a com.android.dmcommandservice.START -n com.android.dmportread/.DMPortActivity
what is so great about getting to Diag mode this way you say?
1. well it doesn't require root access.
2. its cross model supported. (well any model with the DMPortRead.apk installed which i have yet to see one without).
btw you can do the ##3282# in the same way... the apk is call EPST.apk. just look in the Android-Manifest.xml for the info.
tronoftroy said:
i got one better for ya.
Code:
am start -a com.android.dmcommandservice.START -n com.android.dmportread/.DMPortActivity
what is so great about getting to Diag mode this way you say?
1. well it doesn't require root access.
2. its cross model supported. (well any model with the DMPortRead.apk installed which i have yet to see one without).
btw you can do the ##3282# in the same way... the apk is call EPST.apk. just look in the Android-Manifest.xml for the info.
Click to expand...
Click to collapse
Remember, Im on CM7 GingerBread, not SENSE....
Ok so it should work on the EVO since the architecture is pretty much the same as the DINC. Now as far as it being for updating the PRL, yes it can be for that. But it is for people who need to use a program such as QPST or CDMA Workshop to change carrier based settings on their phones(IE the "flashing" [no not as in rom flashing, but carrier]). Where *228 and such is not a feasible replacement for doing so and would prevent their phone from functioning correctly, such as with mine which is flashed to cricket.
Any sort of *228 business breaks my cricket flash, and I used to have to make a backup and go back to restore a sense rom to go into the EPST app with ##778 or to be able to dial ##3424 to put the phone into DIAG mode where I could revise the settings again to make it function properly, THEN flash back since CM7 does not have the EPST.apk which supports both of these features.
With this you can avoid the whole hassle of all this if you have the QPST application for your PC by simply putting your phones DIAG mode ON or OFF. Where you can manually put in what ever PRL you want and manually set any carrier-specific settings. Not as convenient as EPST and its ##778 feature, but much more so than the previously described process.
ALSO I've now included all of this in a simple .zip file flashable from recovery to streamline this crude process a little more. Get it HERE. The file in the original post has been updated too.
m4f1050 said:
Remember, Im on CM7 GingerBread, not SENSE....
Click to expand...
Click to collapse
if CM7 doesn't have DMPortRead.apk couldn't you just push it to you framework/app folder? or even install the apk and just run that when ever you need to connect to the Diag port? (for Qpst, or what ever you need it for) i'm not very familiar with CM7 so i could be wrong.
i use it to send my own serial commands. i find qpst to be more of a hassle then helpful. manuf. have been making there own NV items that are not listed in Qpst models for a while now. ie. the ERI banner for some hero's is not pulled from the usual eri.xml but instead read from the NV items. i think NV item 8042.
now, i while i was snooping around with the flash command. i notice that you can use "-s" (i think, i could be thinking of fastboot.) to specify your own memory location to flash an img file to.
now if we can find the mem location of the NV items you can simply read your entire NV items as an .img then use flash cmd to write all your NV items at once, and maybe even with the Recovery update.zip. im looking into the recovery source atm. if anyone knows where the NV items are stored plz let me know. is it mtd or mem location?
Can you check if you have the file /sys/devices/virtual/usb_composite/diag/enable? If you do.. Create a GScript that echoes 0 or 1 (0 for disable and 1 for enable) to the file /sys/devices/virtual/usb_composite/diag/enable it works like a charm!
tronoftroy said:
if CM7 doesn't have DMPortRead.apk couldn't you just push it to you framework/app folder? or even install the apk and just run that when ever you need to connect to the Diag port? (for Qpst, or what ever you need it for) i'm not very familiar with CM7 so i could be wrong.
i use it to send my own serial commands. i find qpst to be more of a hassle then helpful. manuf. have been making there own NV items that are not listed in Qpst models for a while now. ie. the ERI banner for some hero's is not pulled from the usual eri.xml but instead read from the NV items. i think NV item 8042.
now, i while i was snooping around with the flash command. i notice that you can use "-s" (i think, i could be thinking of fastboot.) to specify your own memory location to flash an img file to.
now if we can find the mem location of the NV items you can simply read your entire NV items as an .img then use flash cmd to write all your NV items at once, and maybe even with the Recovery update.zip. im looking into the recovery source atm. if anyone knows where the NV items are stored plz let me know. is it mtd or mem location?
Click to expand...
Click to collapse
Hmmm... Can you write to NVItem 0,1 or 2 this way?
m4f1050 said:
Hmmm... Can you write to NVItem 0,1 or 2 this way?
Click to expand...
Click to collapse
yes. you can write any nv item through DM Mode. well almost any.
i guess some call the NV item image file SPL???... poking about on the forums seems like you are unable to backup the radio and the nvitems maybe stored within. just a guess though.
tronoftroy said:
yes. you can write any nv item through DM Mode. well almost any.
i guess some call the NV item image file SPL???... poking about on the forums seems like you are unable to backup the radio and the nvitems maybe stored within. just a guess though.
Click to expand...
Click to collapse
in EFS you can access NV items locked (on some HTC devices, tested with EVO 3D and EVO 4G) by creating folder "open sesame door" rebooting phone then going back to EFS the folder NVM should not have the lock, allowing you to see / write these NV items. So if you lack an easy to use NV Item browser you can use this approach.
Can you please update the link for the update.zip file to flash in recovery? Or if someone has it can you point me in the right direction?
I am trying to get QPST working with Sensation.
After echo'ing 1 to enable, the USB modem driver shows up. I dunno which driver u have used but I am using this one: http://forum.xda-developers.com/showthread.php?t=801570
and in QPST it doesn't recognize phone model so I can'T pull NV data from it.
any suggestions?
BTW I have QPST 2.7 Build 366
Curious! said:
I am trying to get QPST working with Sensation.
After echo'ing 1 to enable, the USB modem driver shows up. I dunno which driver u have used but I am using this one: http://forum.xda-developers.com/showthread.php?t=801570
and in QPST it doesn't recognize phone model so I can'T pull NV data from it.
any suggestions?
BTW I have QPST 2.7 Build 366
Click to expand...
Click to collapse
yeah, just open up your QPST Configuration. and set the Comport then your phone will show in QPST.
Hmmmm, modem? You're on 64 bit Windows 7? I recommend 32 bit..
Does this work on the evo??