Related
I'm a newb in the sense that I'm new to the whole Windows Mobile Devices. As my location of this thread, I have a T-Mobile Wing.
I'm a current web designer and I'm learning to program/code. Especially for mobile devices first. So I am computer literate just a newb using roms, windows mobile in general. I believe I can follow on very easily.
I will edit this post to add the answers and explain them in more details, etc. as I learn them for future cookers/newbies/etc.
I have searched around the forums, learned a lot but still have questions hopefully some pro cookers could answer and maybe use this as a ref for all beginner newbs. I have the link to the wing/herald xda wiki/atlas, etc.
BUT STILL....
I'm on Windows Vista 64 bit. Maybe this is my problems? I take that into possibility. Within a week I'll have XP back on this computer as well.
[1]
I understand if your SPL/IPL is above 4.0+ you can hardspl your device. (DO NOT ATTEMPT TO HARDSPL YOUR DEVICE IF IT IS UNDER 4.0! IT WILL BRICK IT!)
I aslo heard of a uspl method where it hardspls your deivce JUST FOR THE NEW ROM YOU"RE INSTALLING.
I read that hardspl will hardspl your device forever but since then it's now reversable correct? Just curious about this, not a big deal either way.
NEWBS IF YOU WANT TO CHECK YOUR IPL/SPL VERSIONS : take your stylus out and soft reset your device by pushing your stylus into the small hole just under the volume slider on the left side of your phone and hold the camera button as it boots up until you see 3 grad colors. red blue, etc. it will then display your version numbers.
[2]
I wanted to learn how to cook, since I felt it wouldn't be too hard since I have a good background with computers, etc.
So.... I started following this thread:
http://forum.xda-developers.com/showthread.php?t=341243
I found a few others including the ones displayed with the hypercore download thread. But I stuck with this one as a first attempt and have not tried any others yet. I know I should but this one just bugged me, haha.
I did all steps accurately and did them again to double check...... but when I go to BuildOS.exe the top of the screen displays:
"the system cannot find the batch label specified"
Is this bad? I remember reading a long time ago about the format being unix and not dos, yatta yatta it would bring this error up but that can NOT be the possibility since everyone else has used this guys thread to create custom roms. Any ideas?
[3] (Cont'd from Question [2])
I also get some error trying to do step 2 in the BuildOS.exe menu, which is.... build OS.nb from SYS and Oem..... that error is file not specified... so i believe it has something to do with the batch error at the top, maybe? Ive tried this step 2 several times and actually got it to work and displayed new os.nb is saved in hypercore/build.... which i went there and didnt see it, but i see one inside the ROM folder... I assume this is the one I want? Perhaps?
[4] (Cont'd from Question [2])
When I try option number 3 in the BuildOS.exe menu I get this message
Save to desktop as........ as what? lol. I assumed the same name, leave it the same.... well the OS.nb was not at the location it specified. (hypercore/tools/convert) lol.
Again tho the save as problem.... I believe it all has to do with the batch file, it's like not fetching/displaying the file name.... if not it meant to leave it the same name? Anyway why is it not in the location specified?
[5]
This is what it displays after clicking enter, of course again no RUU folder found, I figured this with the previous errors. But heres what the flash option in the BuildOS.exe menu does err.... rather displays......
Again Place the _____ here..... still all the batch file problem?
[6]
Again dealing with this screen, is it ok that after Device: its blank? aka not displaying the propper htc model for the wing 3450 or whatever it is, I forget.
(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??
I’ve been helping a buddy get his A500 back to working order, so I thought I’d add the steps taken here which lead to successful replacement of boot loader and ability to flash roms again.
First off Blackthun3r is a genius and you cats should totally donate and thank him if this stuff helps.
The info is a bit spread out so I hope this helps consolidate things. We all owe big ups to jnktechstuff for starting this post here:
http://forum.xda-developers.com/showthread.php?t=1699277 go thank him too.
One thing everyone is right about: You must secure your ID just in case, which is needed to properly reprogram the stock/crappy recovery boot. Two options I saw:
1) From a nandroid backup (inside the clockwork recovery folder or wherever your previous bootloader stored them) there is a uid.txt file.
2) When you run Afterota if it can’t find a uid it will generate a file “AcerIDs.txt”.
Afterota is great too but wouldn’t fix/attached to our A500 in APEX mode, but this feature alone is huge.
For AfterOTA, Thanks and Salute to Gersma:
http://forum.xda-developers.com/showthread.php?t=1675939
Next is just getting the thing to boot.
http://forum.xda-developers.com/showthread.php?t=1699277
Mentioned in “How to unbrick” , as stated they suggest you get 3 files. Here’s what we got :
1) Decrypter (mandatory)
2) 2 ICS roms (you only need one, but he suggests to get both just in case, or even an older Honeycomb if those fail you).
The one that worked for us was ICS 4.0.3: 7.014.01_41.203.01.
Extract the decrypter and use on the rom/zip you downloaded. It will make a separate rom/zip with the words ‘decrypted’ at the end. EXTRACT THIS FILE!
Inside the newly extracted zip file should be 3 files. If you don’t have it or your zip program says it’s corrupted then you don’t need to decrypt it, use the non-encrypted version of the rom pack you just downloaded (i.e. it wasn’t encrypted)!
3 files will look like:
1) Update.zip
2) AMSS.zip
3) Acer_A500_7.014.01_041.203.01_COM_GEN1.txt (or whatever rom you had downloaded)
These 3 files need to be on the root of your external SD micro card (either put it into a reader for pc access or if your system is functional copy it over via USB cable while mounted in the A500). The basic bootloader does nothing but check for an update.zip and apply it. However, it cannot replace itself (saw with a CWM or TWRP) and thus what I think is the ‘rub’ with this device.
After the update.zip applies, boot the system normally. You should have a locked OTA version of ICS with USB Debugging enabled, if not, hit Options, Developer and turn on USB Debugging. If it doesn’t boot, try another rom/decrypt combo. If it boots moved these three files into a sub folder on your SD Card and save for next time you brick it
Next, get the right driver for Windows from Acer site (this is important because it has the ICS USB and the APEX/boot USB driver needed):
http://www.acer.be/ac/nl/BE/content/drivers
You now need to unlock, add SU and Super User. Hit the following link and get Blackthund3r’s Root app (ICS7.1.x for Windows) top of page:
http://forum.tegraowners.com/viewtopic.php?f=30&t=350
When you hit some of this download links be sure to check for things like the skip ad button top right corner, else you’ll download the wrong thing:
Extract and run “ICS Root 2.exe”
1) DO NOT mess with the bundles tabs right now, but ensure all checks minus bottom two are selected and ‘Do it!’
2) You should see that it does confirm for you that it is connected and USB Debugging turned on.
You should now have the device setup to run a proper APEX adjustment, which lets you replace the bootloader and then apply all the little zips and roms your heart desires. Blackthund3r has the last tools we need:
Get APXFlash: http://a500bootloaderflash.tk/#download-links (again watch out for the adfly and click skip add to get to your zips).
APXFlash has all the bundles from proper Blackthund3r repository, the FAQ below may have suggested certain types but that info is kinda old SO just grab a bundle 15, 16 or whatever you are looking for (16 is a great team wiz recovery version combo Skrilax has done, we used that one).
1) Go to Bundle Market and follow the wizard:
2) After downloading the bundle of choice you’ll now be prompted to put in your SBK number from that Acer ID or uid txt file.
3) You should then back up your dump file as it is recommended in the process.
4) Hit blue arrow ‘next’ to see your flash options below, we used the Automatic method, smooth as butter.
5) Follow the prompts for APX mode and click blue once the device is blacked out and the mode has changed on status. This is where that official Acer driver comes in handy.
6) Complete the process as instructed and you’ll be good to go!
Last tool used is:
A500 Manager: http://a500bootloaderflash.tk/#download-links (again watch out for the adfly and click skip add to get to your zips).
This app rocks to help you get into recovery mode (or test your new bootloader) until you get a rom on there that allows you to do it from the power off button or notification tray.
Most of these links and info are at the bottom of Blackthund3r’s FAQ page, which were also super helpful:
http://a500bootloaderflash.tk/
Again this helped my friend and he was thinking several of you could benefit. Even when typing this up I figured some better/quicker ways to maybe get some of the data but this is the thorough steps we took and I hope it helps you! I also had screen caps so once I figure out how to add those, if it'll help or someone needs it will look into that ;p
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 All,
First let me say thanks to all XDA Developers, and without this forum I would still be a pleb when it comes to unbricking. :highfive:
The link to QPST: androidbrick.com/download/latest-qpst-2-7-build-422-425-430-437-qfil-qualcomm-flasher/
(Sorry, I haven't passed 10 posts yet, so you have to manually enter into the address bar)
I came to this forum seeking answers to unbrick my hardbricked Note 4, and after many hours of heartbreak and headache, I have come across a tool called QPST.
This tool is used by Qualcomm, and if you read carefully through the accompanying documentation, you will find some interesting stamps - such as "Confidential" etc.
While I am no expert in the use of QPST, from my own incomplete research I am convinced this tool can be used on any device which sports a Qualcomm chipset (Snapdragon etc.) to unbrick it from certain death.
I have not yet succeeded with my attempts at unbricking, but it is now only a matter of time and kind people pointing me in the right directions. :fingers-crossed:
I am looking for the right files to go in the "phone image" and "boot image" lines in the QPST Software Download program.
I hope we can all see the opportunity this tool represents and spread the word among the greater community, not just developers.
Edit:
Using Software Download:
Phone image files will have a .hex extension and I do not believe they can be found on sammobile. I still haven't found the right one.
Boot image files: I still don't know what they will look like. Likely a .hex file.
Using QFIL:
I suspect all these files can be acquired from a service ROM (whatever a service ROM is - I don't think it is a ROM for android as I know them). I am not completely sure of this however.
Using the flat build option will let you select the programmer. It will have a file name like:
prog_emmc_firehoseXXXX.mbn
(Replace XXXX with the correct numbers for your snapdragon. I don't know what the right ones for the Snapdragon 805 are, but I strongly suspect 8084, with a remote possibility of 8064. Edit: I don't know, don't take my word.
There are posts for other phones on XDA, I don't know if they use the 805 chipset or if the files are compatible.) <--- If anyone wants to research, feel free. Team efforts make a big job seem easy! Please post your results!
Accompanying your firehose file will be a bunch of other files in the same folder.
You will need two .xml files to go with the above (usually in the same folder), which will look like as follows:
rawprogram0XXXX.xml (here XXXX denotes some numbering system which will be determined by the internal memory of the device eg 16GB, 32GB, 64GB. I saw an example for a OnePlus One which had rawprogram0_64G.xml.
I'm NOT 100% SURE on this numbering system, as elsewhere on XDA I have come across different file names!
Here's the truncated link: androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/)
patch0.xml
When I find the above, I will post or hassle an admin to post, as these will likely unbrick any Snapdragon 805. Happy hunting!
Here's a truncated link to XproZayd's thread, where a different avenue is explored (and where I got my idea about the 8084 number for firehose -- Remember, I could be wrong!)
forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
This thread is for discussing QPST and how to use it - if you have a hard bricked phone I am not able to help at this stage. However, should anybody find / 'acquire' the right files to use with QPST, we will all benefit.
What made your device hard brick
Sent from my SM-N910G using Tapatalk
Mistake 1: I bought the phone with the known problem of a USB port not working.
Mistake 2: I bought a replacement USB board and replaced it myself, after which the fun and games began. The one time the screen did light up I got an error message about mmc read fail and could not boot.
Mistake 3: Like a fool, I pulled the battery. Now I have a hard bricked / useless Note 4.
Unless the mmc is physically damaged (which I refuse to believe) the phone should be salvageable from its hard brick state. Provided I can find the right files to go with QPST.
Edit:
I have tried contacting Qualcomm to get the files, who have pointed out that they are proprietary to the licensee, ie Samsung. Here's the e-mail below.
Any information other than what is listed on our website (URL listed below for your reference) is Proprietary to Licensees.
However, the following link should help you with the information you're looking for:
http://www.mydragonboard.org
Alternatively, we recommend you follow-up with a vendor that carries this product and seek their feedback on your technical questions.
Please note, Qualcomm is the technology provider, not a manufacturer of consumer products and therefore we are unable to answer your product specific question. We hope this direction helps.
Thank you for your inquiry,
Qualcomm Technologies Inc.
can you explain to me everything that is happening?
i got my note 4 hardbricked from......
i really dont know
i was modifying my phone but then it would not boot
AlexanderDAB said:
can you explain to me everything that is happening?
i got my note 4 hardbricked from......
i really dont know
i was modifying my phone but then it would not boot
Click to expand...
Click to collapse
Is it going in download mode or recovery ?
What were you exactly flashing ?
Is it detected in pc as qhsb loader ?
Is the splash screen GALAXY NOTE 4 showing up ?
Sent from my SM-N910G
Update:
So far I have contacted Qualcomm, Intrinsyc (they sell Snapdragon development boards), and a Samsung retail outlet.
All have come back as a negative - the closest I could get was the Samsung retail outlet where a dude used to work in the repair centre and had access to the files then.
Unfortunately, Samsung revoked his permissions now that he only works in a retail outlet.
He knew what I was talking about, but due to Samsung and their encryption etc, he couldn't provide me with the files.
C_dog_1 said:
Mistake 1: I bought the phone with the known problem of a USB port not working.
Mistake 2: I bought a replacement USB board and replaced it myself, after which the fun and games began. The one time the screen did light up I got an error message about mmc read fail and could not boot.
Mistake 3: Like a fool, I pulled the battery. Now I have a hard bricked / useless Note 4.
Unless the mmc is physically damaged (which I refuse to believe) the phone should be salvageable from its hard brick state. Provided I can find the right files to go with QPST.
Edit:
I have tried contacting Qualcomm to get the files, who have pointed out that they are proprietary to the licensee, ie Samsung. Here's the e-mail below.
Any information other than what is listed on our website (URL listed below for your reference) is Proprietary to Licensees.
However, the following link should help you with the information you're looking for:
http://www.mydragonboard.org
Alternatively, we recommend you follow-up with a vendor that carries this product and seek their feedback on your technical questions.
Please note, Qualcomm is the technology provider, not a manufacturer of consumer products and therefore we are unable to answer your product specific question. We hope this direction helps.
Thank you for your inquiry,
Qualcomm Technologies Inc.
Click to expand...
Click to collapse
I have the same problem and also looking for a solution. I will contribute to this post as I find something.
There is a similar post here:
http://forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
---------- Post added at 07:10 PM ---------- Previous post was at 06:30 PM ----------
Try this manual.
http://dl-1.va.us.xda-developers.co....rar?key=yrJPiZgu63c6RxNIbU_xVA&ts=1474829412
I've found it earlier today but haven't had a chance to try it yet.
Says the file is gone
Sent from my SM-N930W8 using XDA Labs
It's just the pdf and .pit that i used here: http://forum.xda-developers.com/note-4/help/hard-brick-phone-off-long-help-fellow-t3468792
yashthemw said:
Is it going in download mode or recovery ?
What were you exactly flashing ?
Is it detected in pc as qhsb loader ?
Is the splash screen GALAXY NOTE 4 showing up ?
Sent from my SM-N910G
Click to expand...
Click to collapse
it won't boot at all
i was messing around with the system on the factory binary firmware
yes, it is
nope, it will not boot
i have same problem does any one sucess with this process ?
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Reporting Via N910G.
yashthemw said:
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Reporting Via N910G.
Click to expand...
Click to collapse
can you get me a dude with an AT&T note 4?
same boat with my N910F
C_dog_1 said:
Hello All,
First let me say thanks to all XDA Developers, and without this forum I would still be a pleb when it comes to unbricking. :highfive:
The link to QPST: androidbrick.com/download/latest-qpst-2-7-build-422-425-430-437-qfil-qualcomm-flasher/
(Sorry, I haven't passed 10 posts yet, so you have to manually enter into the address bar)
I came to this forum seeking answers to unbrick my hardbricked Note 4, and after many hours of heartbreak and headache, I have come across a tool called QPST.
This tool is used by Qualcomm, and if you read carefully through the accompanying documentation, you will find some interesting stamps - such as "Confidential" etc.
While I am no expert in the use of QPST, from my own incomplete research I am convinced this tool can be used on any device which sports a Qualcomm chipset (Snapdragon etc.) to unbrick it from certain death.
I have not yet succeeded with my attempts at unbricking, but it is now only a matter of time and kind people pointing me in the right directions. :fingers-crossed:
I am looking for the right files to go in the "phone image" and "boot image" lines in the QPST Software Download program.
I hope we can all see the opportunity this tool represents and spread the word among the greater community, not just developers.
Edit:
Using Software Download:
Phone image files will have a .hex extension and I do not believe they can be found on sammobile. I still haven't found the right one.
Boot image files: I still don't know what they will look like. Likely a .hex file.
Using QFIL:
I suspect all these files can be acquired from a service ROM (whatever a service ROM is - I don't think it is a ROM for android as I know them). I am not completely sure of this however.
Using the flat build option will let you select the programmer. It will have a file name like:
prog_emmc_firehoseXXXX.mbn
(Replace XXXX with the correct numbers for your snapdragon. I don't know what the right ones for the Snapdragon 805 are, but I strongly suspect 8084, with a remote possibility of 8064. Edit: I don't know, don't take my word.
There are posts for other phones on XDA, I don't know if they use the 805 chipset or if the files are compatible.) <--- If anyone wants to research, feel free. Team efforts make a big job seem easy! Please post your results!
Accompanying your firehose file will be a bunch of other files in the same folder.
You will need two .xml files to go with the above (usually in the same folder), which will look like as follows:
rawprogram0XXXX.xml (here XXXX denotes some numbering system which will be determined by the internal memory of the device eg 16GB, 32GB, 64GB. I saw an example for a OnePlus One which had rawprogram0_64G.xml.
I'm NOT 100% SURE on this numbering system, as elsewhere on XDA I have come across different file names!
Here's the truncated link: androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/)
patch0.xml
When I find the above, I will post or hassle an admin to post, as these will likely unbrick any Snapdragon 805. Happy hunting!
Here's a truncated link to XproZayd's thread, where a different avenue is explored (and where I got my idea about the 8084 number for firehose -- Remember, I could be wrong!)
forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
This thread is for discussing QPST and how to use it - if you have a hard bricked phone I am not able to help at this stage. However, should anybody find / 'acquire' the right files to use with QPST, we will all benefit.
Click to expand...
Click to collapse
Im in the same boat with my NOTE 4 N910F. Totally blacked out but still picking it up on the PC with QFIL files have found some files but there not the right phone I think.
so fails to load with SAHARA.
cannot find firehose for 910F. Wish someone could solve this one and then publish it all. someone will eventually but QFIL will unbrick all Qualcomm provided you can make the files.
Let me know if you or anyone does. cheers
Lofhario said:
Im in the same boat with my NOTE 4 N910F. Totally blacked out but still picking it up on the PC with QFIL files have found some files but there not the right phone I think.
so fails to load with SAHARA.
cannot find firehose for 910F. Wish someone could solve this one and then publish it all. someone will eventually but QFIL will unbrick all Qualcomm provided you can make the files.
Let me know if you or anyone does. cheers
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3488114
Tried this?
Reporting Via N910G.
Hi, got a Phicomm Energy M+ (E551). It turned off as the battery was empty, so I charged it overnight.
But:
-Switching it on only shows the phicomm logo
-Trying to enter recovery, shows phicomm logo for a second and then the screen stays lit. Nothing else happens.
-On Windows 7 device manager shows it as "RELINK HS-USB QDLoader 9008 (Com3)" (VOL Up+VOL Down + Power)
-fastboot/adb wont find it
-I tried this http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
I dont have a emmc backup but an unzipped Stock ROM of the E551L which support told me to use. (put on SD card and reboot into recovery, but I cant get into recovery)
Hence I use the unzipped ROM with the Qualcomm FLasher :S (http://na.phicomm.info/release/E551L...TA package.zip)
-It starts the process but then says "Failed to enter EDL" (Emergency) mode
Another thing I stumbled across is :
E551L has Qualcomm MSM8916 and Android 4.4.2
E551M has Qualcomm MSM8915 and Android 4.4.4
Will I have to quire a deepflash cable or am I missing something here ?
yashthemw said:
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Click to expand...
Click to collapse
tried but not working
waiting for other solution