Related
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.
(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??
OK, I thought I saw this mentioned -somewhere- on this forum, but I've tried searching in vain.... Most likely I just can't put together the correct search phrase.
I'm currently running ManualNootered B&N 1.3. I've read very conflicting info as to whether B&N can or will update a rooted OS, but is there a way that I can prevent it? I vaguely remember someone mentioning that they had a rooted 1.2 and woke up one morning to a screwed up 1.3. My biggest concern, of course, is the upcoming 1.4. Don't want to try that until someone figures out what might be needed to apply ManualNooter.
That happened to me. I had nootered a 1.2 and it was working beautifully!
Then I turned on wifi, checked my email and got force fed the update to 1.3.
I've just found an old text file on my PC that had directions to block the update though so I tried it out, it requires that you buy the SQlite editor from the market.
It is priced a $2.99 but I feel it was worth it if it works!!
You can still side load the updates if and when you choose to also!
So I bought the editor and followed these directions:
*Open SQLite. It will scan your entire Nook and find every SQL database file there. Even the hidden ones. It only takes ~10 seconds. (You may see a message about granting super-user permissions, which is normal.)
*Scroll down to DeviceManagerService, and tap on it. Then tap on devicemanager.db.
*Tap on the "registry" entry. It's easier now if you rotate to landscape, so you can see more of the fields in each entry.
*All the entries in this table start with "com.bn.device....". Look for the one that's labeled '...fota.mode" at the end.
*In the far right Value column, you'll see "Auto". Tap on that to select it. Then go down to the Status Bar at the bottom, and tap the Menu button (3 horizontal lines), and pick Edit Field.
*You'll then see a black screen with one entry, the field editing form. You should see the field name of "value" there, and its contents will be "auto". If it turned out that your selection picked some other field (they are pretty small!), don't panic! :smileywink: Just go back and retry until you get the right one.
*Tap on "auto" and the keyboard will come up. Backspace to delete the current contents, and enter "manual" in its place. Then tap Done. Then tap Save. Until you tap Save, you've changed nothing, so poking about is fairly safe.
*You can now exit out of SQLite if you like (it's not necessary), but you're not quite done yet, so don't enable WiFi immediately. To make sure that the system is using the settings you just modified, you need to force it to reload and "see" them. So just power your Nook off and back on. After it reboots, it will use your new settings from then on. That's it.
This file was signed ~Mark, and unfortunately I didn't add the username or anything, so Thanks go to "Mark"
Another method?
I found this over on the B&N forum. I don't know if it is more or less effective than the method above. Perhaps a belt-and-suspenders approach would be best - do both.
Link:
http://bookclubs.barnesandnoble.com...be-possible/m-p/1220616/highlight/true#M68396
And the complete OP:
Title:
Declining the 1.4 update should be possible
Text:
I am looking at build.prop from the 1.4 OS released with the Nook Tablet, with an eye to testing an edit of a system file, build.prop, to update the file and make a Nook Color look as if it is already on 1.4. So far, I'm not seeing anything which looks like a showstopper in the new build.prop for drawing elements out of it for a modded build.prop.
Once the actual update is out, I think I should be able to create a modified file very quickly that will tell the BN servers a device does not need the update as it is already running 1.4.
This is the technique I've used successfully to keep my device at 1.2, which I prefer to 1.3.
If my experiments work, I'll post both the raw build.prop, for folks with root who know how to mount /system as rw to simply copy in (after backing up their original build.prop) and as a set of Clockwork installable files. These will need to be run from a Clockwork disk but will not require rooting the device. One script will move your current build.prop and put in an edited one; a second script would remove the modified build.prop and restore your original so you can receive the update if you choose.
If you have a custom recovery in place, ie clockworkmod, it will prevent installation of the update. Your device will still download the update, but when it boots into recovery for install, it will fail. Reboot and you are back to normal. This has worked for me twice.
Ok so here is my question ....
I have done all the LTE Verizon flashed to PP but for some reason im having trouble ....
When i re-boot the phone goes back to R-UIM instead to NV Only .... My PRL sticks but doesnt let me write the NAM settings....
Im gonna be having the phone for a week hopefully someone can help ...
And if i get it to work ill make a GUIDE for it ...
There are issues with getting 4G phones to work on Page Plus at the moment since they aren't supported. Some have had luck removing the 4G SIM as from what I understand 4G won't work with Page Plus.
spunker88 said:
There are issues with getting 4G phones to work on Page Plus at the moment since they aren't supported. Some have had luck removing the 4G SIM as from what I understand 4G won't work with Page Plus.
Click to expand...
Click to collapse
Yeah i know but this model is weird ... I done other 4G LTE phones with no problem ...
I've tried this, and I'm getting the same result. Any idea why yet?
takochan1 said:
I've tried this, and I'm getting the same result. Any idea why yet?
Click to expand...
Click to collapse
I can also confirm that the R-UIM settings return to "R-UIM only" after a reset.
Any Progress
Just wandering if anyone has made progress on this I just got the droid razr m and would like to put it on page plus.
I have a friend who is using the droid bionic on page plus with everything working not sure if the process would be the same.
I've been checking out a droid razr forum on howardforums (xda want let me post link yet) but not really sure if it would work or not. This is my first smart phone been holding out for awhile, coming from an old LG Chocolate 3, really like the phone but would really like to save some money by putting it on page plus.
JUSMEJOSE said:
Ok so here is my question ....
I have done all the LTE Verizon flashed to PP but for some reason im having trouble ....
When i re-boot the phone goes back to R-UIM instead to NV Only .... My PRL sticks but doesnt let me write the NAM settings....
Im gonna be having the phone for a week hopefully someone can help ...
And if i get it to work ill make a GUIDE for it ...
Click to expand...
Click to collapse
I was playing around with build.prop hoping that the resetting has something to do with the values in that file, but I had little success with that. Any updates on your end?
Any progress on this?
I'm running into the same problem trying to get a friends RAZR M activated on PP. I've successfully set up two Droid Bionics using DFS to set NV-Only, configure the EVDO settings and then manually entering the MDN, MIN, etc. But I've been working with this phone for three days now and it absolutely will not keep the NV-Only setting and the Done button is not available in the 01 User Activation settings on the Program menu.
I'm reaching here but could this have anything to do with needing to "unlock" the phone?
At any rate, any help or progress on this would be greatly appreciated!
EDIT: By the way, I don't know if this matters/helps, but this phone is running the stock Jelly Bean from OTA update.
TechSlinger said:
I'm reaching here but could this have anything to do with needing to "unlock" the phone?
Click to expand...
Click to collapse
If you are thinking about bootloader unlock, then no that does not help (at least directly). I am wondering if the R-UIM Config gets reset from NV only to R-UIM on boot with the stock rom.
Hi..here's the solution. (only for rooted Ics, not available for razr m/hd with OTA Jelly bean)
1. If you are on Jelly Bean, return to stock ICS.
2. You MUST root the phone.
3. Download Sqlite Editor from Play store. (Available for purchase)
4. Download ES Root Explorer from Play store.(Available for purchase)
5. Using explorer, go to data/data/com.android.provider.settings/databases
6. find Settings.db inside the folder, copy and paste this file in the same folder.
7. Open the new file(settings-copy.db) with sqlite editor.
8. Find Preferred CDMA subscription, change the value from 0 to 1, save and exit.
9. Delete the original settings.db files, then rename settings-copy.db to settings.db
10. Return to home screen. Restart into boot loader. Choose BP tool to program.
11. From this point, you can do Nam programming on your phone with dfs/cdma-ws/qpst and the value will stick.
This method works on new Droid RAZR M, RAZR HD, RAZR MAXX HD with Rooted ICS only. Not working with Jelly Bean OTA, because there's no pref.cdma subscription inside the settings.db. Maybe we have to wait for full stock JB file.
Happy flashing guys..
droidan said:
Hi..here's the solution. (only for rooted Ics, not available for razr m/hd with OTA Jelly bean)
1. If you are on Jelly Bean, return to stock ICS.
2. You MUST root the phone.
3. Download Sqlite Editor from Play store. (Available for purchase)
4. Download ES Root Explorer from Play store.(Available for purchase)
5. Using explorer, go to data/data/com.android.provider.settings/databases
6. find Settings.db inside the folder, copy and paste this file in the same folder.
7. Open the new file(settings-copy.db) with sqlite editor.
8. Find Preferred CDMA subscription, change the value from 0 to 1, save and exit.
9. Delete the original settings.db files, then rename settings-copy.db to settings.db
10. Return to home screen. Restart into boot loader. Choose BP tool to program.
11. From this point, you can do Nam programming on your phone with dfs/cdma-ws/qpst and the value will stick.
This method works on new Droid RAZR M, RAZR HD, RAZR MAXX HD with Rooted ICS only. Not working with Jelly Bean OTA, because there's no pref.cdma subscription inside the settings.db. Maybe we have to wait for full stock JB file.
Happy flashing guys..
Click to expand...
Click to collapse
I can confirm that the prefererd_cdma_subsctiption item does exist in settings.db of the official OTA JB 4.1.1 in my Droid Razr HD (XT926, Verizon version). I changed the value from 0 to 1, but I still got the "Failed to get call NAM information" when click "User Activation", and I still couldn't write to the phone in service programming in QPST (version 2.7.378), a "NV Write Errors" windows popped up showed "NV_SPC_CHANGE_ENABLE_I" with status "NV_FAIL_S". Any idea what was going on?
droidan said:
Hi..here's the solution. (only for rooted Ics, not available for razr m/hd with OTA Jelly bean)
1. If you are on Jelly Bean, return to stock ICS.
2. You MUST root the phone.
3. Download Sqlite Editor from Play store. (Available for purchase)
4. Download ES Root Explorer from Play store.(Available for purchase)
5. Using explorer, go to data/data/com.android.provider.settings/databases
6. find Settings.db inside the folder, copy and paste this file in the same folder.
7. Open the new file(settings-copy.db) with sqlite editor.
8. Find Preferred CDMA subscription, change the value from 0 to 1, save and exit.
9. Delete the original settings.db files, then rename settings-copy.db to settings.db
10. Return to home screen. Restart into boot loader. Choose BP tool to program.
11. From this point, you can do Nam programming on your phone with dfs/cdma-ws/qpst and the value will stick.
This method works on new Droid RAZR M, RAZR HD, RAZR MAXX HD with Rooted ICS only. Not working with Jelly Bean OTA, because there's no pref.cdma subscription inside the settings.db. Maybe we have to wait for full stock JB file.
Happy flashing guys..
Click to expand...
Click to collapse
Ok first let me say thanks. This is a push in the right direction I was able to get voice and text working. Razr M XT907
Followed the steps laid out but after changing setting to nv_only "done" was still grayed out when phone rebooted.
Booted phone back into bptools and using dfs checked setting sure enough nv_only had taken. So I manually pushed the min/mdn, cdma system id
after restarting the phone and going back to the user activation screen the fields were populated and the "done" button was available so I was able to write the settings to the phone.
After phone reboots settings have taken but the strange thing is when I try to activate the phone I get an Alltel activation that fails.
Not sure what is happening here but phone appears to be on Alltel network instead of Verizon as expected.
I booted back into bptools and manually loaded a new pageplus prl. Reboot the phone prl it is set to new one.
Then the phone dials out *28899 trying to activate on verizon but it also fails. Tried dialing *22800 to activate but the screen comes up
with " A Verizon Wireless SIM card has activated your service and updated your phone's roaming capabilities".
Doing a quick check of my setting and my cdma system id and prl have been changed. cmda 1015, prl 52952.
So it would seem that after the *28899 tried to activate it changed my settings.
Anyway to make a long story short voice and text work but cant get 3G to work, and apparently the phone is not activated
and the *28899 is dialing at random trying to activate. I have gone and changed my cdma back 443 and that seems to keep the
*28899 from coming up as often that could be my imagination.
Sorry if this rambles first time flashing a phone if anything needs clarification let me know I will try to explain better.
Don't we already have a Stock Verizon JB FastBoot ?
We also have a Aussie JB Stock FastBoot
neelhow said:
Ok first let me say thanks. This is a push in the right direction I was able to get voice and text working. Razr M XT907
Followed the steps laid out but after changing setting to nv_only "done" was still grayed out when phone rebooted.
Booted phone back into bptools and using dfs checked setting sure enough nv_only had taken. So I manually pushed the min/mdn, cdma system id
after restarting the phone and going back to the user activation screen the fields were populated and the "done" button was available so I was able to write the settings to the phone.
After phone reboots settings have taken but the strange thing is when I try to activate the phone I get an Alltel activation that fails.
Not sure what is happening here but phone appears to be on Alltel network instead of Verizon as expected.
I booted back into bptools and manually loaded a new pageplus prl. Reboot the phone prl it is set to new one.
Then the phone dials out *28899 trying to activate on verizon but it also fails. Tried dialing *22800 to activate but the screen comes up
with " A Verizon Wireless SIM card has activated your service and updated your phone's roaming capabilities".
Doing a quick check of my setting and my cdma system id and prl have been changed. cmda 1015, prl 52952.
So it would seem that after the *28899 tried to activate it changed my settings.
Anyway to make a long story short voice and text work but cant get 3G to work, and apparently the phone is not activated
and the *28899 is dialing at random trying to activate. I have gone and changed my cdma back 443 and that seems to keep the
*28899 from coming up as often that could be my imagination.
Sorry if this rambles first time flashing a phone if anything needs clarification let me know I will try to explain better.
Click to expand...
Click to collapse
Are you running Android 4.0.4? Is there a full system image for XT907 with Android 4.0.x because my phone came with 4.1.1 installed and I want to downgrade.
As for 4.1.1, I believe that the "Find Preferred CDMA subscription" is now under com.android.providers.settings -> settings.db -> secure -> subscription_mode (see https://github.com/android/platform...ster/core/java/android/provider/Settings.java and search for subscription_mode). The issue however is that that value gets reset back to 0 after a restart, but I cannot find where that happens. I am guessing one of the init files or build.prop maybe.
Wojei said:
Are you running Android 4.0.4? Is there a full system image for XT907 with Android 4.0.x because my phone came with 4.1.1 installed and I want to downgrade.
Click to expand...
Click to collapse
Yes I'm on 4.0.4 There is a thread under the development section but I could not get that download to work but the post was helpful b/c there are a couple of lines that have to be removed from the xml to get it to work right. I downloaded from a phonearena post just google VZW_XT907_4.0.4-7.7.1Q-144_SMQ_S1-36-10_CFC.xml and it should be the first link. I would post link but cant yet.
Actually just went and looked at the ICS thread again and the link to phonearena is in post #16.
Wish I could do more to help but hope this gets figured out. Getting itchy to upgrade to a razr m or hd on page plus from my OG Razr.
mkarps said:
Wish I could do more to help but hope this gets figured out. Getting itchy to upgrade to a razr m or hd on page plus from my OG Razr.
Click to expand...
Click to collapse
Razr M 4.0.4 works great on PagePlus with calls, texts, 3g data.
Wojei said:
Razr M 4.0.4 works great on PagePlus with calls, texts, 3g data.
Click to expand...
Click to collapse
Any one can confirm that Razr HD 4.0.4 works? Hate to flash back to 4.0.4 and find out it doesn't work ...
Wojei said:
Razr M 4.0.4 works great on PagePlus with calls, texts, 3g data.
Click to expand...
Click to collapse
Wait what 3G how did you get that
Sent from my XT907 using xda app-developers app
At first I set the phone to NV only mode, then followed one of the many guides online for Droird Razr flashing to page plus using CDMA workshop. After setting all the values in CDMA and EDVO, I had calls, texts and 2g data. Then, I put in a blank Verizon 4g sim and called *228, and clicked 1 to program. Once it was done, i restarted the phone and 3g started working.
This is a tool I made (with the help of this thread >> http://forum.xda-developers.com/showthread.php?t=1060184 << thanks hydrosity) that will install GScript and scripts to your HTC THUNDERBOLT and allow you to use QPST, QXDM, DFS cdma tool, and cdma workshop on your phone. It is meant to put the device into DIAG mode after you have flashed to a custom rom that doesn't have ##3424# capabilities built in. It is flashable thru recovery mode. It is very useful if you have flashed your TB to another carrier (i.e. Cricket, Metro, etc.) and need to re-write nv and/or nam settings. This took me 3 and a half days to create because of the tedious work of creating an updater-script with notepad++. This is my first flashable package i have ever created and it works nicely. Instructions are as follows...
1. Reboot to Recovery mode that uses edify.
2. Enable signature checking.
3. Choose flash rom from sdcard.
4. After rebooting, run GScript app.
5. Touch menu button.
6. Choose load.
7. Touch diag_on.sh and save.
8. Touch diag_off.sh and save.
9. Run GScript again.
10. The 2 scripts are there so, its a no brainer from then on.
11. Enjoy.
If you have any problems with anything not working properly, reboot to recovery again and choose fix permissions. That should help with FCs. I hope I have helped someone the way XDA has helped me numerous times. My way of giving back to the community. BTW, making flashable packages WAS very very hard for me to do. Now it's only kind of hard. LOL. I wonder if i could kang a SG3 JB rom and compile it to run on our aging Thunderbolt? Hmmm....To DEVS, if this is not in the correct place please move it. Thanks. Peace out.
Thanks for the tool man.
I REALLY wish I could flash my old Thunderbolt to Page Plus but I need some good step by step instructions. I found a decent video but only half of the process and I can't afford CDMA workshop.
But this tool will definitely be useful for those who can do it. Thank you for that.
Sent from my XT912 using xda app-developers app
Thanks for downloading my tool. And you need to follow this guide for your task. http://forum.xda-developers.com/showthread.php?t=1473141 I hope this helps. If so hit thanks. Then hit thanks on that thread also. That tool will definitely help you as you don't have to flash back to stock nor reboot your phone to get into diagnostic mode. :good:
Page plus from what I have researched, is like an mvno (virtual network operator) if my memory serves me right. And they are under verizon kinda like boost mobile under sprints network. And u can use DFS CDMA Tool and/or QPST. Both are free. I recommend DFS though. It's what I use for most of my phone programming driver.
You could also use a text file in the init.d with the contents:
Code:
echo 1 > /sys/devices/virtual/usb_composite/diag/enable
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
echo 1 > /sys/class/android_usb/android0/enable
echo 1 > /sys/class/android_usb/f_diag/on
Thanks for replying. I didn't know that. I'm in the process of compiling a custom rom for the thunderbolt based on the new VZW ICS update, but with parts from jellybean. Would love to get a total dump of the new HTC One, as it would probably be easier to build.
tb script
Solcam
thank you so much - I have been searching how to get into Diag mode. I thought going thru bootloader and getting to USB would do it - it gave me a com port, but the computer could not talk to the phone. I am trying to put pageplus on a thunderbolt, problem is I rooted it first and it is a little bit of a hassle to get it back to stock
I ran the script but I get this on the bottom of the screen after running it stderr: sh: <stdin>[1]: cannot create /sys/devices/virtual/android_usb/android0/f_diag/on: no such file or directory, what is supposed to happen? It is supposed to reboot into diag mode?
thanks again.
BoilermanAres
solcam said:
This is a tool I made (with the help of this thread >> http://forum.xda-developers.com/showthread.php?t=1060184 << thanks hydrosity) that will install GScript and scripts to your HTC THUNDERBOLT and allow you to use QPST, QXDM, DFS cdma tool, and cdma workshop on your phone. It is meant to put the device into DIAG mode after you have flashed to a custom rom that doesn't have ##3424# capabilities built in. It is flashable thru recovery mode. It is very useful if you have flashed your TB to another carrier (i.e. Cricket, Metro, etc.) and need to re-write nv and/or nam settings. This took me 3 and a half days to create because of the tedious work of creating an updater-script with notepad++. This is my first flashable package i have ever created and it works nicely. Instructions are as follows...
1. Reboot to Recovery mode that uses edify.
2. Enable signature checking.
3. Choose flash rom from sdcard.
4. After rebooting, run GScript app.
5. Touch menu button.
6. Choose load.
7. Touch diag_on.sh and save.
8. Touch diag_off.sh and save.
9. Run GScript again.
10. The 2 scripts are there so, its a no brainer from then on.
11. Enjoy.
If you have any problems with anything not working properly, reboot to recovery again and choose fix permissions. That should help with FCs. I hope I have helped someone the way XDA has helped me numerous times. My way of giving back to the community. BTW, making flashable packages WAS very very hard for me to do. Now it's only kind of hard. LOL. I wonder if i could kang a SG3 JB rom and compile it to run on our aging Thunderbolt? Hmmm....To DEVS, if this is not in the correct place please move it. Thanks. Peace out.
Click to expand...
Click to collapse
boilermanAres said:
Solcam
thank you so much - I have been searching how to get into Diag mode. I thought going thru bootloader and getting to USB would do it - it gave me a com port, but the computer could not talk to the phone. I am trying to put pageplus on a thunderbolt, problem is I rooted it first and it is a little bit of a hassle to get it back to stock
I ran the script but I get this on the bottom of the screen after running it stderr: sh: <stdin>[1]: cannot create /sys/devices/virtual/android_usb/android0/f_diag/on: no such file or directory, what is supposed to happen? It is supposed to reboot into diag mode?
thanks again.
BoilermanAres
Click to expand...
Click to collapse
Your phone won't reboot at all. Thats the other reason I made this, because it is faster than ##DIAG#>auto reboot phone>program phone>##DIAG#>auto reboot phone. GOD forbid you didn't program it right the first time. You are supposed to open your app drawer, (the button that shows all apps) touch gscript app to run it, (its blue) hit menu, load and save both scripts. The 2 scripts are on your sdcard inside a folder called 'gscript' without the '' of course. So you could probably use srcipt runner app from playstore to execute the scripts. I just tried with root explorer app and it force closed, so thats not an option. So look here -->http://forum.xda-developers.com/attachment.php?attachmentid=1923849&stc=1&d=1367296728 then you should see this after you hit the menu button-->http://forum.xda-developers.com/attachment.php?attachmentid=1923850&stc=1&d=1367296728 and this after you've added both scripts-->http://forum.xda-developers.com/attachment.php?attachmentid=1923851&stc=1&d=1367296728 If your phone still complains that the files are not found, download and extract this http://forum.xda-developers.com/attachment.php?attachmentid=1923852&stc=1&d=1367296728 folder to the root of your sdcard and try to add the scripts again. So it will look like this /sdcard/gscript/diag_on-diag_off (there is no -, I'm just saying both scripts will be in the gcript folder). After you add the scripts, go back to gcript app, open it and touch 'diag_on' to activate diag mode. I dont know why it did not flash correctly for you in this first place. It should have placed all files in the correct places. By the way, which rom are you running? And did you flash that file from the OP from recovery? I kept compiling and flashing it over and over again until I got it to put all files in the right places. Which recovery are you using? I hope this helps you get your phone flashed over to PP. Good luck. :good:
Thank you! I have 3 Bolts on page plus and have always had to nandroid back to GB to connect to my radios. I'll be giving this a shot soon, the old way of using g_script stopped working after some updates but it seems your tool has brought it back to life....
You are welcome gimmeitorilltell. GScript IS a great app. When used with scripts like this, it streamlines the tedious process of nam/nv programming. I'm just happy that I have helped out some people on XDA, because it's is my number 1 source of alot of stuff for all the phones that I have to program or hack. Just glad to be giving something back to the community. (offtopic)- Why do some of the smartest people on here not know how to speak 2nd grade English? Seems like no one uses the conjunction 'you're' anymore...they say your, which is possessive. Or 'than' instead of 'then'. EX- Your not going anywhere fast than= You're not going anywhere fast then. I don't get it. SMH. Sorry for the rant...it just burns me up. LOL. Hit the thanks button if I've help you...even if it is just taking them back to grade school. LOL.
You are very welcome gimmeitorilltell. I'm happy to help out fellow members. Just glad to give back to the community finally. XDA is my number 1 source of information on how to program or hack devices that I need to program. Hey twistedumbrella, when are you gonna drop your next AOSP rom update? Are you waiting for HTC to release their source code? I'm downloading your ROM (Multisource) right now to check it out. I love AOSP roms because i can play games on my phone with Wii or PS3 gamepads. Plus it sticks it to the MAN (HTC). LOL. MODS please delete this post. I can't seem to be able to.
I used the other script and it went in. I think because there were already some directories made up in the root. So I got into diag mode, I then tried flashing with the site "cyberflashing". It seems like everything gets blocked from writing to the phone.
I rooted it with Revolutionary, Running Liquid ICS android 4.0.4. Nice setup, I should have waited to root and flashed it with the stock rom then rooted it later. I have QPST and DSF plus the free ones from CDMA for ulocking the sps.
After flashing with cyberflash (which did not seem to do anything -$10 gone like that!) they want you do the following (which I did not know if there is a script for this??) info below.
I imagine i could do everything with the right software, just have not found all the videos and tutorials to get it done. It almost makes you want to give it to a guy that does it all the time and pay him for his services, but I am stubborn too, and it has been a learning experience.
What is interesting is that the only number that dialing from the phone that works is the one below
Dial *#*#4636#*#*
Phone information
Scroll down to the CDMA LTE/EVDO box
Change it to CDMA LTE/EVDO
Press back button until back at home screen.
Upon completion of flash restart the phone again by removing the battery.
Then dial ##3424 then press Send
Press Menu
Select Re-boot to enable embedded mode
After the phone reboots dial ##778 then press SEND
Go to edit mode, password 000000
Then go to Modem Settings and match what is below...
-Slot Cycle Index = 2
-Preferred Serving System = Automatic
-Preferred Mode = CDMA Only
-Preferred Mode(9k) = HDR LTE only
-HDR Hybrid Preferred = Enable
-HDR Hybrid Preferred(9k) = Enable
-Clear All MRU Entry = No
-Rev. A = Disable
-1X Diversity = Disable
After this is complete press menu, commit modifications and phone will reboot
Replace LTE Sim card in phone to restore call ability.
Menu, Settings, Wireless and Networks, Mobile Networks, Network Type, CDMA Only
used to work
I don't know why it won't create the directory on the phone, It used to work. I have tried it on two rooted phones and I get the errors. I have found the directories on the phone, but not same structure. Tried to change it - but phone won't let me create new directories on it.
solcam said:
Your phone won't reboot at all. Thats the other reason I made this, because it is faster than ##DIAG#>auto reboot phone>program phone>##DIAG#>auto reboot phone. GOD forbid you didn't program it right the first time. You are supposed to open your app drawer, (the button that shows all apps) touch gscript app to run it, (its blue) hit menu, load and save both scripts. The 2 scripts are on your sdcard inside a folder called 'gscript' without the '' of course. So you could probably use srcipt runner app from playstore to execute the scripts. I just tried with root explorer app and it force closed, so thats not an option. So look here -->http://forum.xda-developers.com/attachment.php?attachmentid=1923849&stc=1&d=1367296728 then you should see this after you hit the menu button-->http://forum.xda-developers.com/attachment.php?attachmentid=1923850&stc=1&d=1367296728 and this after you've added both scripts-->http://forum.xda-developers.com/attachment.php?attachmentid=1923851&stc=1&d=1367296728 If your phone still complains that the files are not found, download and extract this http://forum.xda-developers.com/attachment.php?attachmentid=1923852&stc=1&d=1367296728 folder to the root of your sdcard and try to add the scripts again. So it will look like this /sdcard/gscript/diag_on-diag_off (there is no -, I'm just saying both scripts will be in the gcript folder). After you add the scripts, go back to gcript app, open it and touch 'diag_on' to activate diag mode. I dont know why it did not flash correctly for you in this first place. It should have placed all files in the correct places. By the way, which rom are you running? And did you flash that file from the OP from recovery? I kept compiling and flashing it over and over again until I got it to put all files in the right places. Which recovery are you using? I hope this helps you get your phone flashed over to PP. Good luck. :good:
Click to expand...
Click to collapse
Solcam I have not had much luck with this script running 4EXT recovery. Are you using CWM or something different? I would love to be able to do my programming without restoring the ole GingerBread nandroid. Lol
HTC One
Anyone know if this will work with an HTC One
freduser said:
Anyone know if this will work with an HTC One
Click to expand...
Click to collapse
Highly unlikely
Sent from my HTC6500LVW using Tapatalk
Sorry I haven't replied to this thread in a long time. I'm not sure which phones and/or roms this will work on! I just remembered I had posted this and am currently trying to get this working on cm10.x for the Eco 4g LTE. BTW I built this with titanium backup but have forgotten exactly how I did it as I hate Linux scripts. I'm gonna download this and compare the Evo's file system to the Thunderbolt's. Probably will report back but idk...
twistedumbrella said:
You could also use a text file in the init.d with the contents:
Code:
echo 1 > /sys/devices/virtual/usb_composite/diag/enable
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
echo 1 > /sys/class/android_usb/android0/enable
echo 1 > /sys/class/android_usb/f_diag/on
Click to expand...
Click to collapse
last one works for HTC desire 510 -> echo 1 > /sys/class/android_usb/f_diag/on
solcam said:
This is a tool I made (with the help of this thread >> http://forum.xda-developers.com/showthread.php?t=1060184 << thanks hydrosity) that will install GScript and scripts to your HTC THUNDERBOLT and allow you to use QPST, QXDM, DFS cdma tool, and cdma workshop on your phone. It is meant to put the device into DIAG mode after you have flashed to a custom rom that doesn't have ##3424# capabilities built in. It is flashable thru recovery mode. It is very useful if you have flashed your TB to another carrier (i.e. Cricket, Metro, etc.) and need to re-write nv and/or nam settings. This took me 3 and a half days to create because of the tedious work of creating an updater-script with notepad++. This is my first flashable package i have ever created and it works nicely. Instructions are as follows...
1. Reboot to Recovery mode that uses edify.
2. Enable signature checking.
3. Choose flash rom from sdcard.
4. After rebooting, run GScript app.
5. Touch menu button.
6. Choose load.
7. Touch diag_on.sh and save.
8. Touch diag_off.sh and save.
9. Run GScript again.
10. The 2 scripts are there so, its a no brainer from then on.
11. Enjoy.
If you have any problems with anything not working properly, reboot to recovery again and choose fix permissions. That should help with FCs. I hope I have helped someone the way XDA has helped me numerous times. My way of giving back to the community. BTW, making flashable packages WAS very very hard for me to do. Now it's only kind of hard. LOL. I wonder if i could kang a SG3 JB rom and compile it to run on our aging Thunderbolt? Hmmm....To DEVS, if this is not in the correct place please move it. Thanks. Peace out.
Click to expand...
Click to collapse
Any Simular tool with latest Android Support?
My XIAOMI 6 is root, not enable Diag yet.