Develop Bugs

Long road almost there, error 67 :( calls & text ) but no data :( [evo on boost]

Long road almost there, error 67 :( calls & text ) but no data :( [evo on boost]
THE GOOD AND BAD NEWS... THE GOOD NEWS FIRST! i got my evo4g over to boost mobile with my boost account i already had open i can outgoing text and recieve text (no mms right now) i can call out and get calls in, works great shows my boost cell phone number on my evo and everything..
NOW THE PROBLEM...
my DATA doesn't work at all... i get the error 67
I TRIED THESE INSTRUCTIONS AFTER SEEING MY DATA DIDNT WORK..
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If data is not working move on to the next steps...
(Note: These are steps not verified by me as I still dont have neither 1x nor Evdo working but some people say 1 or 2 or all of these following steps combined worked for them, so i guess it depends on the network you are trying to get on)
1. First attempt to update your profile if it can or update PRL
Menu>Settings>About Phone>System Updates>Update Profile
Reboot and see if data works....
2. If still no Data, plug in your Hero to the computer, dial ##3424#, go to QPST folder and open QPST Configuration app.
Under the Ports Tab if the active COM port your phone is on is not in that list Click Add Port and add it.
Then go to Active Phones Tab, select the phone and then go to Start Clients>Service Programming
A new window opens, hit ok, then click Read From Phone on the bottom left, its gonna ask you for your MSL type it in
Then go to the M.IP Tab and under user profiles click on profile 0, click edit, and then deselect Profile Enabled, hit ok, then click Write to Phone.
Close the program unplug your hero, reboot it, and try your data again.
3. If still no data, plug in your old phone to the computer, open up QXDM
check Connections and make sure your COM port is being read.
Go to View>New>Common>NV Browser , in the Category Filter drop down menu, filter only Data
Then scroll down to ID numbers 1192 and 1194
Click read and copy down all the values in there until u reach 0x00
Then unplug your old phone and plug in your hero, dial in ##3424# and go to NV Browser
navigate to the same ID numbers 1192 and 1194, (just to be safe copy all the values here so you can revert back to the originals)
Then double click each value under the input column and it becomes changeable and change all the values to the ones from your old phone and hit write
Close QXDM unplug and reboot your hero, test Data again
4. If still no data, plug in your old phone to the computer, open up QXDM
check Connections and make sure your COM port is being read.
Go to View>New>Common>NV Browser , in the Category Filter drop down menu, filter only Data
Then scroll down to ID numbers 465 and 466
Click read and copy down all the values in there until u reach 0x00
Then unplug your old phone and plug in your hero, dial in ##3424# and go to NV Browser
navigate to the same ID numbers 465 and 466, (just to be safe copy all the values here so you can revert back to the originals)
Then double click each value under the input column and it becomes changeable and change all the values to the ones from your old phone and hit write
Close QXDM unplug and reboot your hero, test Data again
NONE OF IT WORKED.... SO I WENT TO THE SECOND SET OF INSTRUCTIONS.
Run the QPST config and plug in your phone, make sure your phone is detected in the COM port list. If not click Add New Port and add the one that it has detected your phone on. What it says may vary but USB will often be in the description.
Run QXDM click Options -> Communications and set the Target Port for the same one QPST config listed for your phone.
In the command box at the top type "spc 000000"
Note: If your SPC is not 000000 then you need to use the correct number instead!
If successful you will see a window titled "Command Output" that will output some text with the final line reading "SPC Result = Correct"
Next in the command box type "requestnvitemread ds_mip_ss_user_prof"
This will get you a lot of stuff in the Command Output window. It will start with the "DIAG TX item" section, ignore this one, we are interested in the "DIAG RX item" part.
The actual keys are 16 lines and marked in the output as 0-15. You will notice that quite handily both HA and AAA are both there. Take the part after the "0x" and that is actual key data. Just write down (or use word, notepad, whatever) to record this for safe keeping.
If you are doing this right then you have a long string of 30 characters all strung together for each key. DOUBLE CHECK YOUR COPYING! A single mistake will cause this to fail.
Putting the keys back into the phone:
Load QPST service programming, go to the M.IP tab. Double click profile 0 (in the white box) and use "Enter hex value" to enter your backups of your HA and AAA keys.
Write to phone.
Soft reset. (may not be required but I do it for good measure)
do "requestnvitemread ds_mip_ss_user_prof" for the sprint info and "requestnvitemread ds_mip_ss_user_prof 1" for the boost info
I'm telling you.. If you're getting the error 67, the following these steps above will fix it.. I'm on the Sprint network and the problem i was having was, in "Profile 0" The username which began with A000000 (this is actually your ESN #) Was from the original phone, not the donar phone... So i took the battery out the donor phone and looked at the ESN (not DEC) and began to type A00000 etc.
Then i used the steps above to get AAA Shared Secret from the Donor phone.. My AAA Shared Secret was 32 Alpha numeric characters...
i did that and still no dice.... i got the AAA key and the HA key .. both were 32 characters...
i even went as far as to get the profile info from the incognito phone, for profile 0 and 1, and made it exactly the same on my evo and addresses for the HA and alternate HA ADDRESS... still no dice.. i went into debug mode on my evo and even hit the restore to start fresh , and let it download the data via the servers... still didnt work...
i even re-entered the profile info and etc, for profile 0 and 1, and still not working
i know im close i just need to finish the puzzle please help.
oh yea, and when i go into debug mode it shows the authentication as failed.. i dont know how thats even possible I've triple checked the HA AND AAA keys via QXDM and they are the correct keys from the incognito boost phone.

Epic 4g to metropcs/cricket

I am going to show you how to get the epic 4g to to metropcs.
First thins is first, you need to get the esn added to metropcs.
If you cant add the esn in the inventory it will not work.
You can how ever use a boost mobile tutorial to clone the esn from your phone, just look on you tube.
The short bit of cloning is that its very very easy, you have to zero out, then use qxdm to load a new one.
Thats all i have to say about that.
Things you are going to need.
A computer with administrative acess
CDMA workshop 2.7
QPSP that can read the phone
HTML:
http://thepiratebay.org/torrent/6388346/Qualcomm
Metropcs prl
HTML:
http://www.corolada.com/prl/metropcs/02001.prl
samsung drivers
HTML:
http://downloadcenter.samsung.com/content/SW/201009/20100901010102890/Samsung_Mobile_Driver_V1.3.800_For_SPH-d700_Epic_4G.zip
A samsung epic with a data cable, not all cables are equal. Keep several handy.
First were going to change the msl to 000 so that metropcs Over The Air activation can work.
Turn your phone one and dial ##8778# and select modem under usb, and under uart modem.
Once you do this your phone will be readable by qpst and cdma workshop.
Drivers and Com Ports
Install the samsung drivers, once that finishes you can plug the phone in and the drivers will install.
You will need to find out what port your phone is under, and posibly change it to any open port under 25
Go to the start menu, then my computer and right click on it, select manage.
In vista/seven allow administrative acess. A window live this appear.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click on device manager then under modems you should see Samsung Mobile Modem.
Right click on that and then select properties
Once this opens click on 2 then select advanced port settings.
This will be your port number for cdma workshop and QPSt. If you notice on my computer its at 32.
I need to change it to any number below 25 so that cdma workshop 2.7 will open it.
click on where 3 is pointing to and select a port from the list below 25. Then close that out
CDMa Workshop msl change
What ever port you had from the previous section we need to enter it on CDMA Workshop
Open CDMA WS.
4 Select your comport
5 Click connect, on my screenshot i was already connected so it says disconnect.
6 Read from them phone and information on the side will appear like your phone number when its connected.
7 Go to the security tab
8 in the spc field put 000000 (six zeros)
9 CLick on SPC Write.
Once that done you can close CDMA Workshop, it will ask you to reset.
Do it .
With part done you can slip the esn change here from the boost tutorial
QPST, PRL, INTERNET
Install QPST
Go to the start menu, all programs, QPST, then QPST Configurator
10 Go to the ports tab
11 Add New Port
12 Click on Show Serial USB/QC Diagnostic ports
13 You should see something like COM32-USB/QC Data Modem. Select it and clikc ok
14 you should see a phone in the list
15 go to Start Clients
16 Select Service Programming
A new windows will open up
17 on the phone selection windows make sure your phone is selected
18 click on ok to enter programing on selected phone.
19 Once the window opens click on read from phone
20 make sure the spc is 000000, we changed it in CDMA WS
21 click ok to
22 go to the CDMA tab
23 if you cloned your esn put your mdn or min here I dont know which is which
24 if you cloned your esn put your mdn or min here I dont know which is which
25 Select the roam tab
26 click browse and select your metropcs prl downloaded from colorado prl
27 select the display tab
28 Change the Banner to Metropcs or what ever you want. You can even leave it at sprint
29 click on the right arrow to reveal more tabs on top
30 Select the M.I.P. tab
31 Change mobile Ip to Simple Ip only
32 Change the Initial Registration to 1750ms
33 Click on RF2002 authentification calculation
34 Change registration Retries to 2
35 Change deregistration Retries 1
36 Change Lifetime-expiry registration 0
37 Now double click on user profile 0 and change to steps 39-49
38 double click on user profile 1 and change to steps 50-59
39 Change the nai to [email protected] or [email protected]
40 Change Tethered nai to [email protected] or [email protected]
41 On Ha shared secret click on enter text string
42 enter metropcs
43 on AAA shared secret select enter text string
44 enter metropcs
45 MIN HA SPI change to 12C
46 MIN-AAA SPI change to 2
47 Change the primary HA adress to 0.0.0.0
48 Change the Secondary HA adress to 0.0.0.0
49 click ok
50 Change the nai to [email protected] or [email protected]
51 Change Tethered nai to [email protected] or [email protected]
52 On Ha shared secret click on enter text string
53 enter metropcs
54 on AAA shared secret select enter text string
55 enter metropcs
56 MIN HA SPI change to 12C
57 MIN-AAA SPI change to 2
58 Change the primary HA adress to 0.0.0.0
59 Change the Secondary HA adress to 0.0.0.0
60 click ok
61 there is no 61 i skipped a number, but i know someone is going to notice. I know
62 Now click on PPP Config tab
63 in the rm tab change config tries of all 3 to 20
64 make sure the request time out is 1000 on all 3
65 make sure NAK tries are 3 on all 3
66 make sure terminate tries are 2 on lcp 3 on ipcp and 3 on ipcpv6
67 make sure request time out is 3000 on lcp and 1000 on ipcp and ipcpv6
68 click on compression setting for ipcpv6 to ignore
69 make sure require pw enc is enabled/checked
70 make sure ppp detect is enable/checked
71 change retries to 5
I seem to have lost the rest of my captures thanks to acronis!!! so i will continue with blodykiller86's pics which are not labeled
72 make sure you click on Um
73 in the Um tab change config tries on lcp 20 ipcp 20 and ipcpv6 to 0
74 make sure the request time out is 1000 on lcp and ipcp, but on ipcpv6 change it to 0
75 make sure NAK tries are 2 on lcp and ipcp but on ipcpv6 change it to 28
76 make sure terminate tries are 2 on lcp 3 on ipcp and 0 on ipcpv6
77 make sure request time out is 3000 on lcp and 1000 on ipcp and 0 on ipcpv6
78 Click on compression setting for ipcp to disable
79 click on compression setting for ipcpv6 to ignore
80 make sure Optimized domant handoff is enabled/checked
81 change retries on ppp authentication to 5
82 change tethered nai on ppp authentication to [email protected] or [email protected]
83 change User ID on ppp authentication to [email protected] or [email protected]
84 go to http://www.whiterabbit.org/android/ and put your esn where it says "Enter 1 MEID/ESN per line in the text area to your left, then click the calculate button."
The ESN is on the top of your qpst windows, copy the short number that starts with an 8 and calculate.
It will return a six digit metropcs msl code.
85 take the generated code and put it in the password
86 click on AN
73 in the AN tab change config tries on lcp 20 ipcp 20 and ipcpv6 to 0
74 make sure the request time out is 1000 on lcp and ipcp, but on ipcpv6 change it to 0
75 make sure NAK tries are 2 on lcp and ipcp but on ipcpv6 change it to 28
76 make sure terminate tries are 2 on lcp 3 on ipcp and 0 on ipcpv6
77 make sure request time out is 3000 on lcp and 1000 on ipcp and 0 on ipcpv6
78 Click on compression setting for ipcp to disable
79 click on compression setting for ipcpv6 to ignore
81 change retries on ppp authentication to 5
82 change tethered nai on ppp authentication to [email protected] or [email protected]
83 CHange the password to the msl code you got from white rabbit a six digit code.
Then just click write to phone, wait for the phone to reboot before closing qpst.
The if you want to activate your phone if its not in your account already just dial *228
to enter Over The Air activation, it will ask for english or spanish. select either
once it gets past that it will ask why you called.
Dial 2 to change number, dial 1 proced, then 1 to proced, enter your phone number, enter your security code (usually birthdate of account holder), and follow the rest of what she says.
1 is for yes 2 is for no, i usually mute the microphone.
and then its activated to an account.
Next make sure you dial *228 this time select 5 to update your prl and reboot.
All done.
I dont know how to get the mms working yet., I have tried u2nl. wap, proxies, flashing zips that change the mms settings and no luck yet.
ill let you know when i get it working or if anything comes up in the thread.
I stay very busy, so dont be surprised if i dont answer, but if you send me a message it should get to my email.
P.S. to all you cricket people i am so sorry for forgetting about you when i started writing this, please change all apropriate settings but it should work.
I will change them asap, right now though i gots to go.
P.s.s. I cant post in the development section because of the stupid stupid stupid stupid stupid stupid (you get the point) post count rules.
Update: Mms
Okay ibfound out something very useful on how to get mms to WORK, basically I sent myself a small 46k pic to gmail. But I kept messing with the phone, without even realizing I had it working. Basically before I knew it I has killed it.
Here is what I used to get it work.
Autostart.sh
#######
export PATH=$PATH:/data/local/bin
IP_ADDR="10.223.2.4"
chmod 755 /data/local/iptables
chmod 755 /data/local/u2nl
/data/local/u2nl $IP_ADDR 3128 127.0.0.1 8888 &
/data/local/iptables -t nat -o ppp0 -A OUTPUT -p tcp -d ! $IP_ADDR -j REDIRECT --to-port 8888
/sbin/remount rw
cat /data/local/telephony.db > /data/data/com.android.providers.telephony/databases/telephony.db
cat /data/local/Mms.apk > /system/app/Mms.apk
sleep 5
kill `ps | /data/local/busybox grep autostart | /data/local/busybox awk {'print $2'}`
##########
I will post post iptables binary once I figure out where to upload it. For now if you need it just msg me.
Also to be clear if you use the autostart.sh you won't have a working messages apk. In other words no text or mms untill you factory reset.

Mms
Okay i got mms, but first to vent.
First of all In my experiences with this phone, its not worth the hazle.
Get an evo or a shift.
also this phone should be defecated on, and flushed down the toiled.
The keyboard is cheap, the amoled screen is not noticeably better than evo(unlike iphone4, and not worth the 100 part price), the keyboard is cheap, gps is half decent, ui is horrible. The epic is by no means an evo killer, i have had it for 2 months and all the time i have been cursing this phone. I have bricked it 2-3 times while at work to where cw recovery wont help you any.
Then there is the issue of the kernel, you need a kernel that has iptables support.
You guessed it the stock kernel doesn't have such a thing, so compiling is the best option. Until you go to the samsung page and cant download the source. I tried opera, firefox, marthon, ie, chrome, and UC. When i get my hands on the source code i will provide the a kernel.
Next up is get a rom that has a kernel with support, oh yeah that sounds easy.
No luck so far, i have reason to think that epic experience has iptables support.
But its become abandoned and its not updated to work with the new version of clockwork recovery (edify). Just so you know simply aosp does not have support
Do yourself a favor and sell it, but if youre like me and have 2 of then.
This phone cannot be flashed just like any other phone, you always have to jump trough hoops.
Okay so lets say you got an old cw , flashed experience and were able to get a kernel with iptables.
you would get this
http://www.4shared.com/file/yofYy6uB/epic_4g.html
it comes with
u2nl
autostart.sh
iptables
telephony.db
Mms.apk
apn back up xml file.
what you need
Autostart
es file explorer and enable the root features
apn backup and restore
busybox installer
first off you need to do what the autostart.sh says.
copy u2nl, iptables, telephony.db, Mms.apk, and a copy of busybox to /data/local
then copy autostart.sh to /data/opt and you need to create the folder called opt make the autostart.sh executable. You should run the autostart.sh manually on the terminal like so ./autostart.sh. If you get a FIX ME!, it means your kernel doesnt do iptables.
the last thing is to restore the apn with apn backup and restore with the one i provide, but you need to edit it with your phone number.
edit this file acordingly in the apn xml
mmsc="http://mms.metropcs.net/mmsc?X-Device-MIN=5555555555
rerplace with your phone number like so
<apn type="null" mmsc="http://mms.metropcs.net/mmsc?X-Device-MIN=2222222222
then resotore it.
that should be ready.
I dont have it right now like i said because of stupid problems.
but like i have said, i have sent AN mms once already. But right after that i bricked the phone so i had to delete everything.

Thanks for the post missingxtension. Looking at the posted files they all seem to contain Sprint info within each file. The telephony.db file, autostart files, apns file and so on. Was this an accident or....??
I know you said you bricked your phone so i'm not sure if you meant all files are coming soon or it should work as it minus the apns-config. I was so excited until I looked in each of them.. lol

sorry to necro an old thread but i followed your steps exactly. for some reason my phone wont connect to a metro tower. i then went back into qpst and changed the sid and still cant connect to a metro tower. what am i missing?

I am one of the few, if not only members on XDA who has their Epic to MetroPCS.
If you're having issues with the internet, there's a file foating on the net that calculates the metropcs wap password needed in order to be online. Its calculated based off of your MEID.
My phone was flashed as the 2nd poster said. With the autostart u2nl crap. It sucked. My phone did not last long and the autostart was hogging my battery. It was possible with Shiziopunk's Epic Experience 2.1 eclair. (Outdated) though sine I've moved, MetroPCS towers no longer reach me in the state of Oregon so I roam 24/7. Using wifi and third party apps for mms and whatnot. I use EG22 deodexed stock now. Still have service. I still have the MetroPCS rom backed up in clockwork mod, but unless I was instructed on how to strip my personal data from it, I'm not sharing.. Donations would be appreciated to any interested. Afterall I did pay 75$ for my rom.

Shinydude100 said:
I am one of the few, if not only members on XDA who has their Epic to MetroPCS.
If you're having issues with the internet, there's a file foating on the net that calculates the metropcs wap password needed in order to be online. Its calculated based off of your MEID.
My phone was flashed as the 2nd poster said. With the autostart u2nl crap. It sucked. My phone did not last long and the autostart was hogging my battery. It was possible with Shiziopunk's Epic Experience 2.1 eclair. (Outdated) though sine I've moved, MetroPCS towers no longer reach me in the state of Oregon so I roam 24/7. Using wifi and third party apps for mms and whatnot. I use EG22 deodexed stock now. Still have service. I still have the MetroPCS rom backed up in clockwork mod, but unless I was instructed on how to strip my personal data from it, I'm not sharing.. Donations would be appreciated to any interested. Afterall I did pay 75$ for my rom.
Click to expand...
Click to collapse
im not worried about internet or anything like that yet. i need to get the phone to connect to a metro tower first. ill figure out mms and internet afterwards. i also plan on doing a metropcs version of any syndicate rom i do. it will be what the rom is plus all the **** to make the phone run on metropcs smoothly

Honestly if all that worried you was getting it to connect to a metro tower, then get your esn added with Metro. That simple.

Shinydude100 said:
Honestly if all that worried you was getting it to connect to a metro tower, then get your esn added with Metro. That simple.
Click to expand...
Click to collapse
like i mentioned before i follwed the steps in the op. one of the first steps was to clone the esn or get it added to metropcs. i cloned my esn and still cant connect to a metro tower.

Again. You need to add it to MetroPCS's ESN database, cloning over your Boost ESN is retarded. Boost Mobile is owned by Sprint. Nothing to do with Metro pcs.

ESN must be a metro esn or ported esn
MysteryEmotionz said:
like i mentioned before i follwed the steps in the op. one of the first steps was to clone the esn or get it added to metropcs. i cloned my esn and still cant connect to a metro tower.
Click to expand...
Click to collapse
I might be able to help on getting a metro esn pm me.
Also about the sprint stuff, I am 100 percent sure that the only problem i am having is a crappy kernel. I still cant download the source code to give a shot at netfilter.
I can send mms no problem, so if i send "hey" to [email protected] it goes thru no problem.
The picture messages are the problem.
I was able to install epic experience 1.9 and it didn't boot.
I downgraded the recovery to 2.5 and it looked promising.
I am not done working on this, but luckily i am to the point to where i can already start using my shift again.
I am currently also working on an evo 3d and nexus s 4g.
Again once i find out, i will post all the information I have.
Also sorry about the pictures, I took a lot of time to write and make screen shots.
But i got the thumbnail links, ill update the links asap.
I will keep an eye out on this thread, its not dead at all.
Also if you pm me, i do get a message on email.

Hey Shiny, can you pm me with info about your epic on MetroPCS? My wife has her phone already on MetroPCS, and all the basics work just fine, but her eclair has bugs, and I wanted to try to upgrade her Rom. Just wanted yours or anyone else's input. Thanks
Sent from my PG06100 using xda premium

You can upgrade her rom, but in the process, you'll more than likely lose Metro's 3G service with only 1x working (due to iptables I believe) so no picture messaging, or internet if upgraded. You should use clockworkmod for a nand backup an upgrade it once its backed up. I upgraded mine because MetroPCS is non-existent in Oregon but they have roaming here, so I wasn't going to be needing to stay on the MetroPCS friendly rom when I have wifi at home for internet/picture emailing. I'm on EH17 GB and loving it.

Unfortunatly, we do not have 3g here yet, so i guess i'll tackle that when time comes. What is the difference with the GB17? Do you have a link or should i just google it, or is it in a forum? Thanks for your help again
Sent from my PG06100 using xda premium

cbernardo13 said:
Unfortunatly, we do not have 3g here yet, so i guess i'll tackle that when time comes. What is the difference with the GB17? Do you have a link or should i just google it, or is it in a forum? Thanks for your help again
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
It still has issues but they are VERY miniscule now. Here is my own Changelog on differences.
Major GPS Lock Improvement.
On Froyo & GB: Adobe Flash Player 10.3 Works Excellent.
Apps 2 SD. (This is a *big* plus, you won't be hoggin the internal Memory Space on her Epic.)
Graphical User Interface Upgraded. The Icons in the settings Menu are now color, instead of the old Eclair look.
Battery Use now has a Graph showing your Battery Life.
Battery Life should improve after you upgrade to EH17, compared to Eclair.
~There are a few more nice things you can get, but you need to upgrade to EH17 before they will work.~ Like CRT Off animation when your screen turns off on her Epic. And a Battery Percentage inside the battery Icon in the Android Status Bar.
Make sure you get clockworkmod installed, nandroid backup her Metro Rom, before you flash anything, that rom is valuable.
Once you decide to upgrade you'll need:
-Samsung Drivers Installed.
If Windows Vista/7 it should install using your internet. If Windows XP, you'll need to look online for the Samsung Drivers. If you're on a 32-bit computer, get the X86 drivers, if on 64-Bit, get the X64 Drivers.
You'll need to download Odin, found in the the Epic Section Titled "Android Development" You can also find it online..
Once you have that, you'll need to power off her Epic, slide open the keyboard, hold down the "1" key and the power button, you'll be in Download mode. Find clockworkmod, follow the instructions and flash that using Odin. (Notice your computer should pick up her Epic as Modem, etc.) Odin will show COM1, 2..3..4.. a diff # for all of us, that's just the port assigned by your computer. Once you flash clockworkmod, next is the nandroid backup.
Turn the phone off it Odin rebooted it. Hold the down button, camera button, and power button. (Have a firm grip, don't let go until the clockworkmod recovery comes up, (should be purple if you odin'd the latest one) go to advanced/backup. Hit yes, and the Nandbackup will begin. This will save you from semi-bricking your girl's epic in the future.
Next you'll want to pick a rom to Flash, you can go with whatever you want, but I reccommend you startoff with roms using the RFS file format until you get the hang of flashing. I'm personally usng Deca's EH17 deodexed rom. Its stock. It has minor reboots, but they aren't too often. Good luck & happy flashing.

MysteryEmotionz said:
sorry to necro an old thread but i followed your steps exactly. for some reason my phone wont connect to a metro tower. i then went back into qpst and changed the sid and still cant connect to a metro tower. what am i missing?
Click to expand...
Click to collapse
When you dial *228 does it give you MetroPCS or Another Carriers Prompt? If another carriers prompt then you need to download the MetroPCS .prl to the phone. Thats how the phone locates the towers.

Exactly. And I was assuming you had flashed your phone with metro PCS already, which would have included the PRL, if you're in a rural area, it is possible to hear a diff operator if roaming. Bu if its sprint, then the prl isn't there.

I have Cricket and have everything working on the $45 plan...except MMS. Guess I'll read through some of these solutions and give em a try.
Thanks!

up-yours said:
ok cricket is going national on sept 25 2011.
i have an epic 4g and want to use it on cricket.
their are no coporate or other cricket stores here.
i will have to flash it my self right?
were do i get a cricket prl?
i can follow the guide here and hopes it all works....
any advice?
http://www.androidcentral.com/cricket-goes-national-new-phones-best-buy-stores-sept-25
Click to expand...
Click to collapse
You have to get your esn added to Cricket's system one way or another, wether that be finding a source who will add it for you for a fee, or getting a phone pre-programmed to cricket, sold to you by someone who lives near a cricket location and shipped to you. If you get the esn added, you can use google to find the appropriate prl, and if you get it preprogrammed or flashed at a location outside your area, prl will be included.

Does anyone have issues with youtube playing on wifi, but not on the 3G?

tried to clone my half broken motorola photon to epic 4g, but when i execute
scp xxxxxx
requestnvitemread ds_mip_ss_user_prof
requestnvitemread ds_mip_ss_user_prof 1
i get
15:29:20.748DIAG RX item:
15:29:20.763SPC Result = Correct
15:29:37.725requestnvitemread ds_mip_ss_user_prof
15:29:37.850DIAG TX item:
15:29:37.850index = 0
15:29:37.850mn_ha_shared_secret_length = 0x00
15:29:37.850mn_ha_shared_secret[0] = 0x00
15:29:37.850mn_ha_shared_secret[1] = 0x00
15:29:37.850mn_ha_shared_secret[2] = 0x00
15:29:37.850mn_ha_shared_secret[3] = 0x00
15:29:37.850mn_ha_shared_secret[4] = 0x00
15:29:37.850mn_ha_shared_secret[5] = 0x00
15:29:37.850mn_ha_shared_secret[6] = 0x00
15:29:37.850mn_ha_shared_secret[7] = 0x00
15:29:37.850mn_ha_shared_secret[8] = 0x00
15:29:37.850mn_ha_shared_secret[9] = 0x00
15:29:37.850mn_ha_shared_secret[10] = 0x00
15:29:37.850mn_ha_shared_secret[11] = 0x00
15:29:37.850mn_ha_shared_secret[12] = 0x00
15:29:37.850mn_ha_shared_secret[13] = 0x00
15:29:37.850mn_ha_shared_secret[14] = 0x00
15:29:37.850mn_ha_shared_secret[15] = 0x00
15:29:37.850mn_aaa_shared_secret_length = 0x00
15:29:37.850mn_aaa_shared_secret[0] = 0x00
15:29:37.850mn_aaa_shared_secret[1] = 0x00
15:29:37.850mn_aaa_shared_secret[2] = 0x00
15:29:37.850mn_aaa_shared_secret[3] = 0x00
15:29:37.850mn_aaa_shared_secret[4] = 0x00
15:29:37.850mn_aaa_shared_secret[5] = 0x00
15:29:37.850mn_aaa_shared_secret[6] = 0x00
15:29:37.850mn_aaa_shared_secret[7] = 0x00
15:29:37.850mn_aaa_shared_secret[8] = 0x00
15:29:37.850mn_aaa_shared_secret[9] = 0x00
15:29:37.850mn_aaa_shared_secret[10] = 0x00
15:29:37.850mn_aaa_shared_secret[11] = 0x00
15:29:37.850mn_aaa_shared_secret[12] = 0x00
15:29:37.850mn_aaa_shared_secret[13] = 0x00
15:29:37.850mn_aaa_shared_secret[14] = 0x00
15:29:37.850mn_aaa_shared_secret[15] = 0x00
15:29:37.850DIAG RX item:
15:29:37.850requestnvitemread - Error response received from target
15:29:56.938requestnvitemread ds_mip_ss_user_prof 1
15:29:57.063DIAG TX item:
15:29:57.063index = 1
15:29:57.063mn_ha_shared_secret_length = 0x00
15:29:57.063mn_ha_shared_secret[0] = 0x00
15:29:57.063mn_ha_shared_secret[1] = 0x00
15:29:57.063mn_ha_shared_secret[2] = 0x00
15:29:57.063mn_ha_shared_secret[3] = 0x00
15:29:57.063mn_ha_shared_secret[4] = 0x00
15:29:57.063mn_ha_shared_secret[5] = 0x00
15:29:57.063mn_ha_shared_secret[6] = 0x00
15:29:57.063mn_ha_shared_secret[7] = 0x00
15:29:57.063mn_ha_shared_secret[8] = 0x00
15:29:57.063mn_ha_shared_secret[9] = 0x00
15:29:57.063mn_ha_shared_secret[10] = 0x00
15:29:57.063mn_ha_shared_secret[11] = 0x00
15:29:57.063mn_ha_shared_secret[12] = 0x00
15:29:57.063mn_ha_shared_secret[13] = 0x00
15:29:57.063mn_ha_shared_secret[14] = 0x00
15:29:57.063mn_ha_shared_secret[15] = 0x00
15:29:57.063mn_aaa_shared_secret_length = 0x00
15:29:57.063mn_aaa_shared_secret[0] = 0x00
15:29:57.063mn_aaa_shared_secret[1] = 0x00
15:29:57.063mn_aaa_shared_secret[2] = 0x00
15:29:57.063mn_aaa_shared_secret[3] = 0x00
15:29:57.063mn_aaa_shared_secret[4] = 0x00
15:29:57.063mn_aaa_shared_secret[5] = 0x00
15:29:57.063mn_aaa_shared_secret[6] = 0x00
15:29:57.063mn_aaa_shared_secret[7] = 0x00
15:29:57.063mn_aaa_shared_secret[8] = 0x00
15:29:57.063mn_aaa_shared_secret[9] = 0x00
15:29:57.063mn_aaa_shared_secret[10] = 0x00
15:29:57.063mn_aaa_shared_secret[11] = 0x00
15:29:57.063mn_aaa_shared_secret[12] = 0x00
15:29:57.063mn_aaa_shared_secret[13] = 0x00
15:29:57.063mn_aaa_shared_secret[14] = 0x00
15:29:57.063mn_aaa_shared_secret[15] = 0x00
how can i read password out of this phone??

Epic 4G, Data Not Working Boost

I Know There Are Lots Of How To's On This But I Follow The Steps And I Just Cant Get It To Work Properly. Iv'e Done The Voice & Text Correctly. But The Data Just Doesn't Work
Im Using My Epic 4G 2.2.1
&
As The Donor Phone Im Using A Samsung Rant (Boostmobile)
If You Have Possible Help Please Post

I Guess The 1192 1194 NV items Don't Read Correctly From The Rant, Because When I Try To Write Them To The Epic, It Says 0 Nv Item Successfully Copied :/

Results For 1192:
[NV Items]
[Complete items - 0]
1192 (0x04A8) - Access denied
Results For 1194:
[NV Items]
[Complete items - 0]
1194 (0x04AA) - Inactive item
Seems As If It Is Still Locked Or Something Like That. It Shouldn't Be, If I Entered The SPC Correctly

the rant is known as a bad phone to get that info from...

I have gotten this to work using DFS cdmatool. this is the only program i found that can easily show the ha aaa passwords correctly. you can use the demo for this to work. DO NOT edit the ha and aaa passwords with this tool - only use it to see them.
1. connect your donor phone and open dfs.
2. click manager in the top left
3. double click on your phone
4. type in your spc and click the button directly to the left
5. navigate to the programming->mobile ip tab
6. click read
this will enable you to see exactly what your passwords are. copy these values or use print screen to save the images. make sure you get the passwords for prof 0 and prof 1. close dfs.
7. disconnect your donor and connect to your epic using qpst.
8. click read and enter your spc/msl.
9. navigate to the m.ip tab and double click prof 0
you will now click the "enter hex value" circles which will enable you to enter the ha and aaa passwords from your donor. it is CRITICAL that you click these circles even if one of your donor passwords came back blank in dfs as this will write it blank. then click ok and change the passwords for prof 1. now click write to phone.
10. unplug usb. reboot phone.
i hope this helps

Did you by any chance follow re-Odin your phone with "Phone EFS Clear" checked?

[Q] Phone rebooting AFTER random button presses

My phone started restarting constantly today in apps. It was always after I clicked a button to do something.
I restored factory defaults and tried to do setup but even during setup random buttons will freeze the UI then reboot the phone.
I followed this guide http://forum.xda-developers.com/showthread.php?t=1626895 and completely reflashed the phone and it still does the same thing. Randomly one of the first couple button presses (like hitting next or sign in on gmail, or opening the gmail browser menu) will freeze the UI and reboot the phone.
What steps should I go forward with to attempt to fix this? Can I somehow get logcat to work from bootloader so I can see what's going on?
Thanks

Record a logcat via from boot until the crashes happen.

063_XOBX said:
Record a logcat via from boot until the crashes happen.
Click to expand...
Click to collapse
[Edit] Thanks, trying to figure out how to get USB debugging working for adb now.

picklefish said:
[Edit] Thanks, trying to figure out how to get USB debugging working for adb now.
Click to expand...
Click to collapse
I can't seem to get adb working on the SETUP front page. Is there some way to enable USB Debugging via a flash or root from recovery so that I can logcat?
EDIT:
My attempt to get USB debugging enabled from recovery.... I still just get a black screen on launch after doing all of this. I'm guessing I'm missing another setting somewhere...
following this http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
Installed clockworkmod recovery
http://wiki.cyanogenmod.org/w/Install_CM_for_toro#Unlocking_the_device
Section: Installing recovery using fastboot
With CWM installed I could then adb in. (I mounted system and data in the recovery menu)
updated build.prop
> adb pull /system/build.prop build.prop
open build.prop in notepad++ and add "persist.service.adb.enable=1" (without quotes)
> adb push build.prop /system/build.prop
then edited adb_enabled to 1 in settings db
> adb pull /data/data/com.android.providers.settings/databases/settings.db
edit
> adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
following this guide if you need help editing settings.db
http://forum.xda-developers.com/showthread.php?t=774507 (i would use this sqlliteadmin though http://sqliteadmin.orbmu2k.de/ but replace the dll following this stack overflow top answer http://stackoverflow.com/questions/9991162/viewing-dumping-encrypt-android-sms-database)
[EDIT 2]
I ended up just installing Cyanogen to see if it crashes on that. I am logcating it since it has USB logging on by default apparently.
[EDIT 3]
So this reboot even happens in cyanogenmod. I managed to get to USB Debugging checkbox, but when the popup showed up it froze and crashed It only happens if i click on buttons in the ui. If i never click anything (just swipe around the desktop) it will never reboot. This is so weird. as long as I don't press any UI buttons it won't reboot. I wish I could get logcat to work.
[EDIT 4]
Here's a logcat right before it crashed. I can attach the whole thing but I am not sure if there are any serial numbers in it or not that I would need to sanitize.
Code:
W/ActivityManager( 313): Permission denied: checkComponentPermission() owningUid=1000
W/BroadcastQueue( 313): Permission Denial: broadcasting Intent { act=android.appwidget.action.APPWIDGET_UPDATE_OPTIONS flg=0x10 cmp=com.android.settings/.widget.SettingsAppWidgetProvider (has extras) } from android (pid=550, uid=10045) is not exported from uid 1000 due to receiver com.android.settings/com.android.settings.widget.SettingsAppWidgetProvider
I/HeadsetService( 776): Headset=false; Bluetooth=false
I/HeadsetService( 776): Selected configuration: speaker
D/EventHub( 313): No input device configuration file found for device 'sec_jack'.
I/EventHub( 313): New device: id=12, fd=230, path='/dev/input/event6', name='sec_jack', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/sec_jack.kl', keyCharacterMap='/system/usr/keychars/sec_jack.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=true, usingClockIoctl=false
I/InputReader( 313): Device added: id=12, name='sec_jack', sources=0x00000101
V/WiredAccessoryObserver( 313): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=1, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=4580, ACTION=change, SWITCH_NAME=h2w, SWITCH_TIME=102717987063}
V/WiredAccessoryObserver( 313): updateState name: h2w state 1
V/WiredAccessoryObserver( 313): updateState switchState: 1
V/WiredAccessoryObserver( 313): newState = 1, headsetState = 1,mHeadsetState = 0
V/WiredAccessoryObserver( 313): device h2w connected
I/HeadsetService( 776): Headset=true; Bluetooth=false
I/HeadsetService( 776): Selected configuration: headset
D/PhoneStatusBar( 401): disable: < expand icons alerts TICKER* system_info back home recent clock >
W/InputMethodManagerService( 313): Window already focused, ignoring focus gain of: [email protected] attribute=null
D/PhoneStatusBar( 401): disable: < expand icons alerts ticker* system_info back home recent clock >
W/ThrottleService( 313): unable to find stats for iface rmnet0
I/ActivityManager( 313): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.mms/.ui.ConversationList bnds=[428,1040][565,1168] u=0} from pid 550
I/EventHub( 313): Removing device sec_jack due to epoll hang-up event.
I/EventHub( 313): Removed device: path=/dev/input/event6 name=sec_jack id=12 fd=230 classes=0x1
D/dalvikvm( 313): GC_FOR_ALLOC freed 946K, 39% free 7497K/12288K, paused 52ms, total 52ms
I/dalvikvm-heap( 313): Grow heap (frag case) to 16.786MB for 380496-byte allocation
I/InputReader( 313): Device removed: id=12, name='sec_jack', sources=0x00000101
I/EventHub( 313): Removing device '/dev/input/event6' due to inotify event
V/WiredAccessoryObserver( 313): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=0, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=4835, ACTION=change, SWITCH_NAME=h2w, SWITCH_TIME=106985137942}
V/WiredAccessoryObserver( 313): updateState name: h2w state 0
V/WiredAccessoryObserver( 313): updateState switchState: 0
V/WiredAccessoryObserver( 313): newState = 0, headsetState = 0,mHeadsetState = 1
V/WiredAccessoryObserver( 313): device h2w disconnected
I/HeadsetService( 776): Headset=true; Bluetooth=false
D/libEGL ( 891): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 891): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 891): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/OpenGLRenderer( 891): Enabling debug mode 0
I/ActivityManager( 313): Displayed com.android.mms/.ui.ConversationList: +452ms
I/HeadsetService( 776): Headset=false; Bluetooth=false
I/HeadsetService( 776): Selected configuration: speaker
I/ActivityManager( 313): START {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.cyanogenmod.trebuchet/.Launcher u=0} from pid 313
D/dalvikvm( 313): GC_CONCURRENT freed 1000K, 39% free 8502K/13763K, paused 3ms+12ms, total 95ms

Is there anything left I can do to track down this problem before I go out and buy a new phone? I have several logs now but nothing in common at the point of the crash. I imagine the error isn't even making it to logcat. The fact that the reboot crash still occurs during cyanogen screams hardware problem. But what on earth kind of hardware problem only happens randomly when you open and close random apps or click on random app buttons?
Is there anything left I can do to track down this problem before giving up and buying a new phone?

Alas, I am giving up and going to buy a new phone. The phone is unusable because it reboots in about 4-5 app clicks. or going back to home screen. Sorry to anyone that comes along with this problem. I HAVE FAILED YOU.

One last question if anyone stops by. Is there anything else that could be corrupt that I can reinstall? I've completely cleared everything i can in CWM and reflashed the entire phone to factory settings. Is there anything I'm missing that could be corrupt that i could re-flash?

I have the same exact issue with my wife's GNex. It was unrooted when it began. I rooted it, installed CWM Touch recovery and Slimbean Rom but the exact same thing happens. Tapping home will crash the UI and reboot. Tapping any app to open will do the same. Has anyone else had this issue? Sorry to revive a dead thread, just trying to avoid buying a new phone.
---------- Post added at 04:39 PM ---------- Previous post was at 04:34 PM ----------
mantis92gsr said:
I have the same exact issue with my wife's GNex. It was unrooted when it began. I rooted it, installed CWM Touch recovery and Slimbean Rom but the exact same thing happens. Tapping home will crash the UI and reboot. Tapping any app to open will do the same. Has anyone else had this issue? Sorry to revive a dead thread, just trying to avoid buying a new phone.
Click to expand...
Click to collapse
I also noticed something weird in the logcat
I/EventHub( 394): Removing device sec_jack due to epoll hang-up event.
I/EventHub( 394): Removed device: path=/dev/input/event6 name=sec_jack
What is an epoll hang-up event. Googling this part of my logcat led me to this thread, so I am assuming this error occurs in the OP's original logcat.

[Guide] Enabling DIAG for QPST (updated)

Hi everyone, I have finally figured out how to get proper diag support on our device. This will allow us to use QPST and such.
It will be a pretty short guide as it's quite simple, but it does enable us to do a whole lot of things we couldn't do before.
Downloads
* QPST
* AsusVoLTE app
Prerequsities
* Both methods require root, at least initially. There are several threads on how to do that, so look those up if you need help.
USB method
Downloads
* Qualcomm USB drivers
Step 1
Install the drivers and QPST from above. If you've already done this from my VoLTE/VoWiFi guide there's no need to reinstall them.
Step 2
When you've done that, install the AsusVoLTE app and connect the phone to the computer and open up it up. Press the Enable DIAG button, and you should hear/see a new device attaching. This should hopefully be enough, but if not, try rebooting the phone. If that still doesn't work try the Remote method below.
Remote method
Prerequsities
* Both your computer and phone have to be connected to the same network. You may also need to allow port 2500 in your firewall.
Step 1
Start by downloading and installing QPST from the link above, no drivers or such required. If you've already done this from following my VoLTE/VoWiFi guide you can safely skip this step.
Step 2
Now run QPSTConfig.exe from the bin folder of the QPST install and wait for it to open up. Head to the IP Server tab and tick the Accept client connections box - we need to do this as we will be connecting to QPST remotely. Take a note of the Server IP Address (this should simply be the ip address of your computer), and potentially the Server Port below if you have changed it from the default value of 2500.
Step 3
Open up the AsusVoLTE app on the phone, and enter the IP address from the Server IP Address in the field, and optionally, change the port number.
After this you can simply press the Start button.
Now that you have done this, you should, momentarily, see a new port appear in QPST Configuration under the Ports tab with a Port number like COM30001 and the Phone column should hopefully say SDM855 (0). If you do see this you are good to go! You can now start exploring EFS and such.
Troubleshooting
Some people have had issues connecting to the diag port, with EfsTools from the VoLTE guide returning BadCmd and QPST not working either. If you have this problem, try restoring modem settings by running this in bootloader (adb reboot bootloader, or press volume up while rebooting):
Warning: This may cause issues with no service for some, do not run this without a full backup of all of the partitions (in particular, modemst1, modemst2, fsg and fsc) on the device!
Code:
REDACTED because people still run these commands without taking a backup
Do note that this will reset any changes you may have done (like enabling VoLTE through PDC).
Thanks to @xbamaris1` for troubleshooting this with me, and for confirming this worked!
Let me know if this has worked for you, and if you have any questions!

I'm getting this:
Code:
ASUS_I001_1:/ # diag_socket_log -a 10.30.1.10 -p 2500
diag_socket_log: Diag_LSM_Init succeeded.
diag: In diag_register_socket_cb, registered socket callback function
diag_socket_log: Translating address: 10.30.1.10
diag_socket_log: Trying to connect to address: 10.30.1.10, port: 2500
diag_socket_log: Error calling connect: Operation already in progress, errno: 114
I'll try to restart my computer and phone. Maybe there were some remnants of tools running still.

dennis96411 said:
I'm getting this:
Code:
ASUS_I001_1:/ # diag_socket_log -a 10.30.1.10 -p 2500
diag_socket_log: Diag_LSM_Init succeeded.
diag: In diag_register_socket_cb, registered socket callback function
diag_socket_log: Translating address: 10.30.1.10
diag_socket_log: Trying to connect to address: 10.30.1.10, port: 2500
diag_socket_log: Error calling connect: Operation already in progress, errno: 114
I'll try to restart my computer and phone. Maybe there were some remnants of tools running still.
Click to expand...
Click to collapse
I had this problem to until I realized that its network based and your phone should be connected to your WIFI (at least thats what fixed it for me).
However, Despite this, i am still not getting data from it. COM30001 from an IP of 192.168.1.211 (which is my phone) and it is still not able to browse data from QPST

Wait, I think I got it. I had to use the USB tethering feature of my phone to bypass whatever my router's doing. I also had to run ipconfig to grab the IP address that was assigned to my computer, and manually set that in the "Use specified IP address" box.
Is this IP-based method necessary? I can already see my phone in normal USB mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update: It turns out I didn't need the IP-based method as my phone's already seen through USB. I'm not sure how I managed that.

dennis96411 said:
Wait, I think I got it. I had to use the USB tethering feature of my phone to bypass whatever my router's doing. I also had to run ipconfig to grab the IP address that was assigned to my computer, and manually set that in the "Use specified IP address" box.
Is this IP-based method necessary? I can already see my phone in normal USB mode.
Update 2: It turns out I didn't need the IP-based method as my phone's already seen through USB. I'm not sure how I managed that.
Click to expand...
Click to collapse
I really hope we can get QPST fully working. I'm in the same boat as you, was able to get SDM855(0) but nothing after that with QPST. Glad you got it to work though!
I really want to try enabling some LTE bands (just want two as a start, 12 / 17. And MAYBE 66.

xbamaris1` said:
I really hope we can get QPST fully working. I'm in the same boat as you, was able to get SDM855(0) but nothing after that with QPST. Glad you got it to work though!
I really want to try enabling some LTE bands (just want two as a start, 12 / 17. And MAYBE 66.
Click to expand...
Click to collapse
Does your phone not show up as a USB device like mine? I wonder how I got it to show up. It would be nice to find out so it would be easier to use QPST.

dennis96411 said:
Does your phone not show up as a USB device like mine? I wonder how I got it to show up. It would be nice to find out so it would be easier to use QPST.
Click to expand...
Click to collapse
Yeah it shows up as a USB device with SDM855(0) as the device. I actually had a different diagnostic driver that was the ANDROID Diag mode at some point, not sure if that was useful at all, but still no QPST data. Not sure how I managed to get the Qualcomm ANDROID Diag to show up (The exact interface / driver that showed up was: Qualcomm HS-USB Android DIAG 901D) it just magically appeared after trying to change the sys.usb.config at some point. Haven't been able to recreate it and not sure of the significance of it. But I believe QPST still registered it.

xbamaris1` said:
Yeah it shows up as a USB device with SDM855(0) as the device. I actually had a different diagnostic driver that was the ANDROID Diag mode at some point, not sure if that was useful at all, but still no QPST data. Not sure how I managed to get the Qualcomm ANDROID Diag to show up (The exact interface / driver that showed up was: Qualcomm HS-USB Android DIAG 901D) it just magically appeared after trying to change the sys.usb.config at some point. Haven't been able to recreate it and not sure of the significance of it. But I believe QPST still registered it.
Click to expand...
Click to collapse
Try these drivers: https://androidfilehost.com/?fid=11410963190603864074
This is what mine shows up as after running "setprop sys.usb.diag2 1":

dennis96411 said:
Try these drivers: https://androidfilehost.com/?fid=11410963190603864074
This is what mine shows up as after running "setprop sys.usb.diag2 1":
Click to expand...
Click to collapse
Thats what I have now, and usually do have when I enable it. I just thought it was strange when I suddenly got that other interface to connect. Again, not sure the significance of what I had since QPST still didn't work. But just was something I came across while trying to tinker.

xbamaris1` said:
Thats what I have now, and usually do have when I enable it. I just thought it was strange when I suddenly got that other interface to connect. Again, not sure the significance of what I had since QPST still didn't work. But just was something I came across while trying to tinker.
Click to expand...
Click to collapse
Which version of QPST Configuration do you have? This is mine.

dennis96411 said:
Wait, I think I got it. I had to use the USB tethering feature of my phone to bypass whatever my router's doing. I also had to run ipconfig to grab the IP address that was assigned to my computer, and manually set that in the "Use specified IP address" box.
Is this IP-based method necessary? I can already see my phone in normal USB mode.
Update: It turns out I didn't need the IP-based method as my phone's already seen through USB. I'm not sure how I managed that.
Click to expand...
Click to collapse
It's not necessary, no - if you get it to show up in usb you won't need to do any of this. I could, however, never get the phone to connect in usb mode - it just shows as No phone.
I will try those drivers you posted and update the guide.

I've updated the guide in the first post - it now has both the usb method and remote method. I managed to get diag working through USB, but it seems to be a bit fiddly and sometimes required that I reboot the phone before it started working.
If you don't want to use the app to enable diag you can simply run this in a root shell:
setprop sys.usb.diag 2

HomerSp said:
I've updated the guide in the first post - it now has both the usb method and remote method. I managed to get diag working through USB, but it seems to be a bit fiddly and sometimes required that I reboot the phone before it started working.
If you don't want to use the app to enable diag you can simply run this in a root shell:
setprop sys.usb.diag 2
Click to expand...
Click to collapse
Oh did those drivers make a difference for you?

HomerSp said:
I've updated the guide in the first post - it now has both the usb method and remote method. I managed to get diag working through USB, but it seems to be a bit fiddly and sometimes required that I reboot the phone before it started working.
If you don't want to use the app to enable diag you can simply run this in a root shell:
setprop sys.usb.diag 2
Click to expand...
Click to collapse
How to change imei with EFS

QPST via remote using your guide worked for me. I am able to use EFS Explorer. Thank you @HomerSp!

Will doing this, to eventually turn on VoLTE and VoWiFi, lock me out of Google Pay and similar services?
Sorry if it's a stupid question, I've not toyed around with rooting since it began disabling pay and bank features that I have enjoyed using.

XavierBK said:
Will doing this, to eventually turn on VoLTE and VoWiFi, lock me out of Google Pay and similar services?
Sorry if it's a stupid question, I've not toyed around with rooting since it began disabling pay and bank features that I have enjoyed using.
Click to expand...
Click to collapse
Magisk (the root method) hides itself from bank apps and such, but you can do a SafetyNet check in the magisk manager app, and if that passes so you should be good to go.
Only thing you won't be able to get with the bootloader unlocked is HD video in Netflix and Amazon video.

This is very interesting. I read in another thread that with nvram access you can try to enable bands (but it may not work). Is this to the point where that can be tried?

ChronoReverse said:
This is very interesting. I read in another thread that with nvram access you can try to enable bands (but it may not work). Is this to the point where that can be tried?
Click to expand...
Click to collapse
Yes indeed, but we have yet to find a way to enable additional bands. We are working on it though, so hopefully we'll have something soon.

Hi, can we use QPST to unlock LTE band on 8G/128G version?