Related
(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??
Hi Everyone,
I just received a brand new ATT Focus from US ( with the SIM unlocking code also ).
The phone is rev 1.3 and running 7392 atm.
Searched and searched on XDA, Google also...couldn't find a definitive answer at all...
What is the easiest/fastest way to get to dev unlocked Mango ?
So far, from what I've read is to revert to 7004-chevron unlock-update NoDo- keep the unlock-update mango ( of course some registry tweaks during the way).
Thanks,
htc9420 said:
So far, from what I've read is to revert to 7004-chevron unlock-update NoDo- keep the unlock-update mango ( of course some registry tweaks during the way).
Click to expand...
Click to collapse
That is the only way except ofc, paying the developer unlock.
OMFG...I'm stuck @ 7008 version. Zune tells me it's the latest update...LOL
this is driving me nuts...can do Silverlight but can't update the freaking phone
htc9420 said:
OMFG...I'm stuck @ 7008 version. Zune tells me it's the latest update...LOL
this is driving me nuts...can do Silverlight but can't update the freaking phone
Click to expand...
Click to collapse
Try on another computer. That solved it for many.
Job done
haha, I wasn't seeing the trees because of the forest.
For anyone that might get interested in this, here are the steps that worked great for me ( didn't put any SIM, nor had the time adjusted):
All info I had maily came from this :
http://forum.xda-developers.com/showthread.php?t=1143999
1. Install/flash 7004. Unlock via chevron. Use any registry editor to erase the values from HKEY_LOCAL_MACHINE > Software > Microsoft > DeviceReg/PortalUrlInt, remove its value data and save it. Do the same with PortalUrlProd
2.Zune upgrade to 7008.
3.Zune upgrade to NODO.
STOP THE UPDATING WHEN DONE otherwise ZUNE will automatically proceed to the last two updates that leads to Mango.
4. Deploy http://forum.xda-developers.com/attachment.php?attachmentid=722646&d=1316284246
5. Deploy http://www.edisk.cz/en/download/38910/New_SMS_unlock.xap_41.01KB.html
6. Make root /provxml. Copy unlock.xml to it.
7. Let Zune do the rest.
In my case, everything worked flawless and updated to the last samsung update: fm 2103.11.8.1; radio: 2103.11.8.1 BL: 5.8.0.2
you forgot to mention that after updating to mango 7720, you need to run the diagnostics app to load the "unlocked" profile. Heres a link to the thread, but this thread i find is unclear;
http://forum.xda-developers.com/showthread.php?p=16809179
What i did was the following AFTER the update to MANGO!
1. Enter the diagnostics terminal by entering "##634#" as a phone number
2. Typed "*#9908#" in the diag. mode, which brought me to the GPRS settings
3. Scrolled through the list of profiles, selected "unlock", clicked "save"
4. now your focus is ready for sideloaded apps!
htc9420 said:
haha, I wasn't seeing the trees because of the forest.
For anyone that might get interested in this, here are the steps that worked great for me ( didn't put any SIM, nor had the time adjusted):
All info I had maily came from this :
http://forum.xda-developers.com/showthread.php?t=1143999
1. Install/flash 7004. Unlock via chevron. Use any registry editor to erase the values from HKEY_LOCAL_MACHINE > Software > Microsoft > DeviceReg/PortalUrlInt, remove its value data and save it. Do the same with PortalUrlProd
2.Zune upgrade to 7008.
3.Zune upgrade to NODO.
STOP THE UPDATING WHEN DONE otherwise ZUNE will automatically proceed to the last two updates that leads to Mango.
4. Deploy http://forum.xda-developers.com/attachment.php?attachmentid=722646&d=1316284246
5. Deploy http://www.edisk.cz/en/download/38910/New_SMS_unlock.xap_41.01KB.html
6. Make root /provxml. Copy unlock.xml to it.
7. Let Zune do the rest.
In my case, everything worked flawless and updated to the last samsung update: fm 2103.11.8.1; radio: 2103.11.8.1 BL: 5.8.0.2
Click to expand...
Click to collapse
Consider me new; can you connect steps 4 and 5 with step 6? 4/5 are each XAP files, what purpose does each serve?
Also (and maybe related), unlock.xml seems to be within one of the linked XAPs if you change it's extension to ZIP. How do I copy it to /provxml? This isn't self evident to me, but maybe it is once in Root Tools? I haven't been in Root Tools yet, but is there somewhere to do step 6 within this and if so, can you summarize where?
Sorry for the many questions, there's a lot of info that's hard to digest on the matter - this is pretty close to being the best (most understandable) step-by-step once the questions I posed are answered. Thanks.
xaeryan said:
Consider me new; can you connect steps 4 and 5 with step 6? 4/5 are each XAP files, what purpose does each serve?
Also (and maybe related), unlock.xml seems to be within one of the linked XAPs if you change it's extension to ZIP. How do I copy it to /provxml? This isn't self evident to me, but maybe it is once in Root Tools? I haven't been in Root Tools yet, but is there somewhere to do step 6 within this and if so, can you summarize where?
Sorry for the many questions, there's a lot of info that's hard to digest on the matter - this is pretty close to being the best (most understandable) step-by-step once the questions I posed are answered. Thanks.
Click to expand...
Click to collapse
When you get to NoDo-cancel search for updates as it will surely get you to Mango without unlock.
Install ''WP7 Root Tools" from the link-yes it is a xap.
Install " New SMS" xap from the link.
Open WP& root tools on phone. Make a provxml folder in root. Navigate to Applications/Install/D19A80F2-..../Install and copy unlock.xml.
Paste unlock.xml inside the previously created PROVXML folder.
Exit.
Go to home screen open Phone.
Go to dialer- dial ##634#. A new program should open.
Type *#9908# and a new dialog comes out.
Choose unlock from the list. Press save. Exit.
Done. Fertig. Listo. Finito.
Hope it's clearer this time. Good luck.
This steps should be posted in a new thread and stickied.. IMO, its really hard to find good collected guide about the focus...
3G not working after Unlock
Hey guys, have you noticed that 3G data doesnt work anymore after loading the unlock.xml profile under Mango? I tried reloading the other presets that were available in the GPRS diag. shell, but my 3G is still knocked out. Any thoughts? I am with Rogers in Canada
htc9420 said:
When you get to NoDo-cancel search for updates as it will surely get you to Mango without unlock.
Install ''WP7 Root Tools" from the link-yes it is a xap.
Install " New SMS" xap from the link.
Open WP& root tools on phone. Make a provxml folder in root. Navigate to Applications/Install/D19A80F2-..../Install and copy unlock.xml.
Paste unlock.xml inside the previously created PROVXML folder.
Exit.
Go to home screen open Phone.
Go to dialer- dial ##634#. A new program should open.
Type *#9908# and a new dialog comes out.
Choose unlock from the list. Press save. Exit.
Done. Fertig. Listo. Finito.
Hope it's clearer this time. Good luck.
Click to expand...
Click to collapse
Yup, it's not much different from your previous steps, but the few bits you added helped make the rest more evident. Danke!
pachuau86 said:
This steps should be posted in a new thread and stickied.. IMO, its really hard to find good collected guide about the focus...
Click to expand...
Click to collapse
Agreed!
---------- Post added at 08:36 PM ---------- Previous post was at 08:29 PM ----------
ssingh819 said:
Hey guys, have you noticed that 3G data doesnt work anymore after loading the unlock.xml profile under Mango? I tried reloading the other presets that were available in the GPRS diag. shell, but my 3G is still knocked out. Any thoughts? I am with Rogers in Canada
Click to expand...
Click to collapse
Look around in the WP7 hacking forum for mango update threads - I remember reading something specific to this very issue - "how to fix 3G after provxml unlock" or similar...
ssingh819 said:
you forgot to mention that after updating to mango 7720, you need to run the diagnostics app to load the "unlocked" profile. Heres a link to the thread, but this thread i find is unclear;
http://forum.xda-developers.com/showthread.php?p=16809179
What i did was the following AFTER the update to MANGO!
1. Enter the diagnostics terminal by entering "##634#" as a phone number
2. Typed "*#9908#" in the diag. mode, which brought me to the GPRS settings
3. Scrolled through the list of profiles, selected "unlock", clicked "save"
4. now your focus is ready for sideloaded apps!
Click to expand...
Click to collapse
Just to confirm, you went through 7392, 7403, and 7720 all BEFORE selecting the unlock profile, right? LOL, I rolled back to Nodo to do this a few days ago, and Zune isn't giving me the option to update anymore, so when (if?) it finally does, I want to make sure I don't screw up and have to roll back again.
Not sure why it continues to tell me no updates are available when I have already gone through the update (using the official process) before, so I know it has been released to me. Perhaps it was only "available" to me briefly before they moved on to a different set of users?
do i have to use the unlock using dialpad BEFORE or AFTER mango update... im in 7392 (i think thats NoDo???) right now, and im confused
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.
Hello, I just bought a new motoactv.. But I now see, that because of the fact they shut down Motoact, I cant create an ID. and therefor I cant use the watch as it is. I could root it, but I dont think it will give me the functionality (advanced interval for running) as it can now.
so..is there anyone who can give me their login as they dont use Motoactv.com anymore?
Would be highly appreciated!!
muish002 said:
Hello, I just bought a new motoactv.. But I now see, that because of the fact they shut down Motoact, I cant create an ID. and therefor I cant use the watch as it is. I could root it, but I dont think it will give me the functionality (advanced interval for running) as it can now.
so..is there anyone who can give me their login as they dont use Motoactv.com anymore?
Would be highly appreciated!!
Click to expand...
Click to collapse
Just register new account from your watch.
VjFill said:
Just register new account from your watch.
Click to expand...
Click to collapse
Yeah, but since the pc doesnt recougnise the watch as a USB storage device, and WIFI cant be installed, I never get to create an account. I now have the account details of the person where I bought it from, but I suppose I can as well throw it away, Motorola doesnt give support either.
muish002 said:
Yeah, but since the pc doesnt recougnise the watch as a USB storage device
Click to expand...
Click to collapse
Stop adbd shell in your watch.
Easiest way - via MotoACTV Root Tool from http://www.cleardroidroms.com/motoactv.php
muish002 said:
WIFI cant be installed, I never get to create an account.
Click to expand...
Click to collapse
Go to 'Settings' screen -> Wireless -> Wifi -> Add network
VjFill said:
Stop adbd shell in your watch.
Easiest way - via MotoACTV Root Tool from http://www.cleardroidroms.com/motoactv.php
Since the watch is not recougnised as storage device, I cant see it in explorer either. So I cant, unfortunality, root it either.
Go to 'Settings' screen -> Wireless -> Wifi -> Add network
Click to expand...
Click to collapse
No, it then sais, add a new network with your pc.
I hope you have THE tip..I tried everything, but sofar nothing worked.
muish002 said:
No, it then sais, add a new network with your pc.
I hope you have THE tip..I tried everything, but sofar nothing worked.
Click to expand...
Click to collapse
Again. Disable adbd - then you will be able to connect Motoactv as a USB storage.
muish002 said:
it then sais, add a new network with your pc.
Click to expand...
Click to collapse
Looks like a custom firmware.
Go to Settings -> General -> Motoactv status -> Software version.
Post it here.
VjFill said:
Again. Disable adbd - then you will be able to connect Motoactv as a USB storage.
Oh, I completely overlooked this last time. Great, that worked
Looks like a custom firmware.
Go to Settings -> General -> Motoactv status -> Software version.
Post it here.
Click to expand...
Click to collapse
It sais 4.54.50
I am goimg to try and root it!
muish002 said:
It sais 4.54.50
I am goimg to try and root it!
Click to expand...
Click to collapse
This is initial release or first maintenance version. A really old software.
Update your Motoactv to latest and root only after that.
Keep in mind that versions for 8Gb and 16Gb are different. Choose firmware only for your device.
OR
Install Motorola Device Manager from here https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Plug in your Motoactv.
MDM has to check it and upgrade to latest (but I have no idea, will it be correct as I have never seen such old firmware like yours)
'Advanced functionality' won't be enabled with root.
Interval training can be enabled/planned via Motoactv portal.
So, upgrade your watch, add new wifi from settings -> wireless, then register new account, go to http://motoactv.com
Voila.
VjFill said:
This is initial release or first maintenance version. A really old software.
Update your Motoactv to latest and root only after that.
Keep in mind that versions for 8Gb and 16Gb are different. Choose firmware only for your device.
OR
Install Motorola Device Manager from here https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Plug in your Motoactv.
MDM has to check it and upgrade to latest (but I have no idea, will it be correct as I have never seen such old firmware like yours)
'Advanced functionality' won't be enabled with root.
Interval training can be enabled/planned via Motoactv portal.
So, upgrade your watch, add new wifi from settings -> wireless, then register new account, go to http://motoactv.com
Voila.
Click to expand...
Click to collapse
I already rooted it I think.
Problem is, when I run motorola device manager, it only says, no updates and at device it says "N/a"? So no clue how to get the latest software on it.
muish002 said:
Problem is, when I run motorola device manager, it only says, no updates and at device it says "N/a"? So no clue how to get the latest software on it.
Click to expand...
Click to collapse
Uninstall Motorola Device Manager.
Install this version - https://drive.google.com/file/d/0B9ZhejL5ANmGQjdreG5jR3YybTg/edit
2.4.5 definitely had correct drivers.
Check that battery on your watch is fully charged.
MDM has to detect your Motoactv correctly, search for software and upgrade it,
If it won't - look here http://forum.xda-developers.com/showthread.php?t=1534073
3) Fastboot:
- Operating System: Windows/Linux/Mac
- Instructions (Windows): Unpack the zip, run flash-all.bat (if it fails, run as administrator)
- Instructions (Linux/Mac): Unpack the zip, run flash-all.sh (it should already have proper permissions)
Click to expand...
Click to collapse
Links are in the first post.
at the end, I got it working. Even wifi, although that was on ly a few times, since then I cant login anymore. I am about to sell the watch, as its realy bad in GPS for running (as it was bought as running watch), so I will just sell it as smart watch. But then I do need some apps installed on it. But when you install one app, its full, now trying to get it to install on the SD memory, but again.. not so easy!
Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
How to enable the experiment:
Download the attached APK
Sideload the APK
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[ ] com.pixeloembypass" is in the list
Type in "cmd overlay enable com.pixeloembypass", and hit enter
Reboot the phone
Go into Developer Options to see if "OEM unlocking" can now be toggled on. If so, congratulations!
If "OEM unlocking" is able to be enabled, do so, and reboot the phone into fastboot mode. Unlock as per directions on the factory images site.
NOTE: As usual, if bootloader is unlocked/relocked, a factory reset will be performed.
How to uninstall the experiment:
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[x] com.pixeloembypass" is in the list
Type in "cmd overlay disable com.pixeloembypass", and hit enter
Go into Settings->Apps, and uninstall "Pixel OEM Bypass"
Reboot the phone
This is amazing! Will try it here in about an hour and report back
Maybe tell these guys. They've been at it for a while. You might even get the bounty.
https://forum.xda-developers.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk
djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So? Come on dj! Lol
Sent from my Pixel 2 using XDA-Developers Legacy app
djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Click to expand...
Click to collapse
have more faith.. john mccain posted it after all
Hope it works
Sent from my Pixel 2 XL using Tapatalk
PresidentMcCain said:
Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
Click to expand...
Click to collapse
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Edit:
I downloaded it on my phone just to see what permissions is calls for and it doesn't open the file.
Didn't work for me. Any tips to try?
thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything
elliwigy said:
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything
Click to expand...
Click to collapse
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.
thompatry said:
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.
Click to expand...
Click to collapse
i understand lol.. when im lazy i just use a file browser n view as an archive lol
collinjames said:
Didn't work for me. Any tips to try?
Click to expand...
Click to collapse
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
That's okay, it's completely understandable. I agree - typically, you wouldn't want to install a random APK built by a stranger.
I wish I could test it myself, but both my Pixels are from the Google Store, and shelling out $650+ for a test device for a shot-in-the-dark experiment doesn't sound like very responsible spending.
Tried on my P2XL device and no luck..
nelsonTituaAa said:
Tried on my P2XL device and no luck..
Click to expand...
Click to collapse
Thanks for volunteering...have you gave this a try?
PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse
nelsonTituaAa said:
oops.. no haha.. will try again
Click to expand...
Click to collapse
PresidentMcCain said:
Thanks for volunteering...have you gave this a try?
Click to expand...
Click to collapse
tried it and still no luck.
PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse
Tried the command and doesn't seem like it disable android.auto_generated_rro__ on the overlay list.
tried this plus added recommendation and no luck. Verizon Pixel, 8.1
Anybody tried this on a Verizon Pixel 2? I'm willing to give it a shot, but would need a little more detail on the procedure if anyone is willing to help out.