Database Users

[GUIDE 16/11/09] Get started rooting Telus HERO130! (No need for QMAT!)

Yay, I've finally found a reliable way to do this. After completing these steps, you'll be able to install any GSM Hero ROM. Still, neither I, nor anyone else, can be blamed if something goes wrong and you end up with a shiny paperweight.
-2. Changelog
16/11/09
Updated to Amon_RA's latest recovery image
15/11/09
First release of the guide!
-1. Thanks!
This guide would not have been possible without:
TheUnlockr (great guides)
Amon_RA (recovery image)
xda-developers (need I say more?)
MoDaCo (Excellent ROM)
QMAT (GoldCard)
craig0r (first to root the Telus Hero)
pi3ch (copy from cmd)
And everyone involved in rooting the Dream, the Sapphire, the Hero, and Android in general. Many thanks to everyone involved!
0. Before we start!
If you haven't installed all the drivers for your phone already, follow the instructions on this page to do so. It also shows you the basics of ADB.
Also, a forewarning: there are reports that not all microSD cards work. If yours doesn't work, try another one. Hopefully you'll still have some dough in your wallet by the time you find one that works. Just kidding.
Also, not all microSD readers work either. I have one that just refused to write the GoldCard image to the card, but thankfully, my laptop's SD slot worked.
And, these steps have only been tested on Windows XP 32bit. If you use anything newer, it may or may not work, but most importantly, if you want any chance of it working, you'll want to run most of these apps and commands in Administrator mode.
Finally, make sure you have a Wi-Fi connection, as your data connection will be lost at some point while you need to download something from the Market.
1. Downloads!
You'll want to get all your downloads before starting this.
HxD
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
flashrec
Amon_RA's recovery image
Updated radio
2. Prepare your phone!
On your phone, go to:
Settings > Applications > Development
There, check USB debugging.
3. Backup your APN settings!
Go to the Market and install APN Backup and Restore. Run it, and backup your APN settings with it. This is necessary to restore data access after rooting.
4. Get your GoldCard image!
The GoldCard bypasses some weird check on the phone and allows you to flash ROMs that are otherwise rejected, due to them being older versions, or some other reason that HTC decided it'd be so.
With the USB cable plugged in, open the notifications shade and tap HTC Sync. It doesn't matter if it can't sync, but what matters is you can enter the adb shell. If you don't know how, you haven't done step 0.
Now, go in adb shell and run this command:
Code:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
The output is your microSD card's serial number. Right click anywhere in the command prompt, and click on Mark. Then, select the serial number, and right click. The serial is now copied into the clipboard, so open up Notepad and paste it there.
Now, with that serial number written down, paste it into my lame GoldCard hex reverse. Please credit me if you use that page in your guide!
Next, do as my page says, grab the reversed serial number and get your GoldCard image with it.
5. Create your GoldCard!
So now you have your GoldCard image. Remember, this GoldCard image is valid only for the card from which you got the serial number. If you use another card, get another image.
Turn off your phone, take the microSD out and plug it into the your preferred reader. Again, not all readers work. Not all microSDs work.
Now, unplug from your computer any removable storage except for the microSD. This is to avoid confusion in the next step.
Before making the GoldCard, backup anything you need from the microSD, as it may get erased in the process. Most importantly, backup the APN settings that we got earlier, from APN Backup and Restore.
Now open up HxD. From here, you'll open two things. Your microSD in the raw, and the GoldCard image in the raw.
To open your microSD go to:
Extras > Open disk
In the pop up, under Physical disks, select the (supposedly only) Removable Storage. If there are two, I don't know which one is the right one, so unplug more stuff from your computer.
Before you click OK, be sure to uncheck Open as Readonly. We can't make a GoldCard if we can't write on it, right?
To open your GoldCard image, go to:
Extras > Open disk image
There, select your downloaded goldcard.img file, and click Open, and then OK.
Now you should have two tabs open in HxD, one being the microSD, and the other, active one being the GoldCard image.
Press Ctrl+A on your keyboard to select all, then Ctrl+C on your keyboard to copy. Switch to the microSD's tab, make sure the cursor is at the complete top-left corner, and then press Ctrl+B to paste, and then Ctrl+S to save. Accept the risk and your GoldCard should be made.
To verify, close the microSD's tab, eject it, unplug and replug it, and reopen it in HxD like we did earlier. It should still have the GoldCard image written at the beginning of it. If not, either the microSD or the reader or both don't like making GoldCards, so you'll want to try a different combination of card and reader.
6. Downgrade!
Let's flash the downgraded ROM now. Plug your microSD, now a GoldCard, into the phone and turn it on. After it finishes booting, turn on HTC Sync. Again, it doesn't need to actually synchronize.
Now, run the RUU you downloaded earlier and follow the steps. If the GoldCard works, it should flash and you'll end up with a downgraded phone. If not, then you either didn't write down the microSD's serial number correctly, or the microSD doesn't like to do its job.
Set up the downgraded phone with the default settings, and turn on Wi-Fi. Get on your Wi-Fi network and install Linda File Manager.
Now, on the phone, check:
Settings > Applications > Unknown sources
Now turn on USB Storage, and copy flashrec and Amon_RA's recovery image to the microSD. Rename the recovery image to recovery.img to save a headache later. You may as well put the backed up APN files back on the microSD too, if they got erased.
Disconnect USB storage, load up Linda, go in the SD card, and install flashrec using Package Installer. Now, load up Recovery Flasher, press on backup, then type in:
Code:
/sdcard/recovery.img
Now press Flash recovery.
7. Update the radio
The radio that came with the downgrade is quirky in North American networks. We'll update to the latest IU radio, which works with our networks here.
First, reboot into the new patched recovery. Turn off the phone, and then turn it back on while holding the Home button. Keep holding it until you see the recovery menu.
Once you're there, scroll down using the trackball to turn on USB Mass storage. Plug the phone in the computer if it wasn't plugged already. The microSD will show up on the computer. Copy the updated radio zip to the root of the microSD wait a few seconds, then turn off USB Mass storage on the phone.
Now, select Flash update image, and then Apply sdcard:choose zip. There, the radio zip should show up. Select it and flash it.
8. You're pretty much done at this point.
Follow any guide to install a Hero ROM, to partition your microSD, etc. After you install a custom ROM, be sure to reinstall APN Backup and Restore from the market, and restore your APN settings. This will restore data.

well the "asroot" method of rooting from the guide in the CDMA forum may be worth trying...perhaps they haven't fixed the vulenrability?
http://forum.xda-developers.com/showthread.php?t=581577 (all the way up to before the recovery image)

Ya tried that method don't work

yeah I would love to root this thing.
To be honest this is my first smartphone and I'm new at this rooting thing. I did manage to throw on a hack for my ipod nano (colored version)
I'm loving this phone so far - got it first day they announced their new network. I'm so impressed
Did either of you buy another SD card? Where did you grab yours if you did?

My Telus Hero has been rooted since Friday.
Check it:
http://forum.xda-developers.com/showpost.php?p=4909063&postcount=16

Yeah I just saw. I'll get familiar with the process then update the first post.
Thanks a bunch!

I posted in the other thread (so... sorry for the double post), but I think that this thread is more relevant to the question/issue of rooting.
Could someone who still has the stock Telus ROM post the Baseband version? (Home -> Settings -> About phone -> Baseband version)
I'm just curious as to whether we Telus users should upgrade or downgrade the radio version after rooting the phone, as I seem to be having dialing issues (long distance numbers require a "+" in front of the "1" or it won't connect.)
I dunno if this issue would be related to the radio, or to the fact that there are no North American locales selectable within the custom ROM.

Stock Baseband
63.18.55.06DAU_6.35.08.20
Still wating to see how others are successful with rooting their Telus Hero.

sjeffrey said:
63.18.55.06DAU_6.35.08.20
Still wating to see how others are successful with rooting their Telus Hero.
Click to expand...
Click to collapse
Same here. My stock Telus Hero reports the same version as above (just to add to the data pool). I'll be watching this thread for more details on rooting.

I rooted using the goldcard>2.73.405>recovery>modaco2.9>IU baseband and it works no problem. I can dial 611, long distance numbers dont need a + or a 1 for that matter, and market enabler lets me buy paid apps. Device seems quicker. I had to try 3 different sd cards though. I know I was doing the first one wrong, but one of them definately did not work.

I mentioned in the other Telus Hero thread that I updated my radio to the IU version, and my dialing issues have gone away. Thought I should mention it here as well.

I'm still waiting for a method that doesn't require calling Telus to fix settings though.
Say, is your Hero the black or white one? And, is it a HERO130 or a HERO100?
I keep getting an invalid model ID error when I try flashing the downgrade. Is that what you had the times it didn't work for you?

Soaa- said:
I'm still waiting for a method that doesn't require calling Telus to fix settings though.
Say, is your Hero the black or white one? And, is it a HERO130 or a HERO100?
I keep getting an invalid model ID error when I try flashing the downgrade. Is that what you had the times it didn't work for you?
Click to expand...
Click to collapse
Yeah, I'm pretty sure that's the error I got when I didn't have a proper Gold Card. If you've tried the same SD card a number of times and it's still not working, maybe grab a cheap Sandisk 1GB card. That's what I used.
And you shouldn't have to call Telus, because I've already gone through the pain of figuring all this stuff out. Just make sure you grab the APN settings from the other thread, and update to the latest radio (IU) and you're good. A call to Telus was required because I couldn't receive MMS messages, but that had nothing to do with rooting the phone, I would've had to call them anyway.
When I look up "Model Number" in my phone's settings, it just says HTC Hero. So I dunno. The custom ROM probably did that. I guess.

the model name might be written in the battery compartment area. i know on my htc tytn the name is there as "HERM200"
pretty sure it was mentioned that the telus hero is HERO130

As profets said, the model ID is under the battery. Mine says HERO130, and in bootloader mode, it says HERO13000. Since the downgrade ROM is for HERO10000, it threw an invalid model ID error.

Soaa- said:
As profets said, the model ID is under the battery. Mine says HERO130, and in bootloader mode, it says HERO13000. Since the downgrade ROM is for HERO10000, it threw an invalid model ID error.
Click to expand...
Click to collapse
Ah cool. I just checked under the battery, it's a 130. So you should still be able to downgrade.

Really strange. I tried a Kingston 2GB like they said on the guide and verified that the GoldCard image was well written on the card. Yet it still throws error 130.

Soaa- said:
Really strange. I tried a Kingston 2GB like they said on the guide and verified that the GoldCard image was well written on the card. Yet it still throws error 130.
Click to expand...
Click to collapse
I used the 2GB sd card comes with the phone to create goldcard. Rooted.
No problem at all, I don't know why you guys wanna use other SD cards.

I'm pretty sure I've tried all my cards... I'll try again tonight.

Hah! Got it to work. Guide is done.
I also quickly put together a webpage to reverse the CID of the microSD. That way, people won't need to download QMAT anymore. The page can be found here: http://hexrev.soaa.me
Enjoy!

EPST code "##778 call" Stopped working

I am on Stock 2.1, Rooted
For some unknown reason I have lost ability to go into EPST from phone by ##778 code.
QPST is working in diagnostic mode.
Does anyone know what could have caused this and more importantly how to get it back.
Any suggestions would help.
I have searched many places but did not find answers.

seconded...
EPST works fine on my rooted/2.1 stock phone... not on my wife's. None of the ##xxx codes works.
Weeks after rooting my DInc w/ unrevoked 3.0, I decided it was safe to go ahead and do the same on my wife's phone. It's 2.1 stock, rooted with unrevoked 3.1/CM 2.5.0.x...plus the wifi tether kernel for AP mode wifi. Deleted CityID and installed root apps Ti Backup (full version), IncrediLite, and AdFree (which required manual symlinking /system/etc/hosts --> /data/data/hosts).
That's IT. Her phone is simpler in terms of apps installed. There's very little there that I haven't also done to my own phone... she has HandCent SMS where I don't; rooting method plus clockwork recovery were/are newer, and I never quite got AdFree working on one of the handsets.
I've no idea why this happened to one phone and not the other...I don't understand the where the config files are stored, or how the dialer accesses the 'hidden' menu. Unless I find an informative answer, I'm just going to try unrooting hers & reverting to stock...

figured out a few things
running ASTRO's process manager on my W's rooted phone, I see that dialing ##778 does invoke an instance of EPST... but you don't get the view/edit mode dialogue.
Trying to launch EPST from the ASTRO process mgr ("go to application") gives the view/edit choice, and if you hit edit you are prompted for the password... but after typing in 000000 it just hangs on 'wait while verifying password'
logcat has lots of entries containing 'epst' but I don't know how to interpret them.
I notice that the com.google.android.epst file lives in /data/data, where one has to muck around when getting a hosts file symlinked for AdFree...but I didn't do anything clumsy, and the permissions are rwxr-xr-x which looks right.
That's about as far as I can go. Anyone know what breaks EPST?

QPST workaround...
I guess this problem must be pretty isolated since no one has responded... but fwiw, as OP alluded, Qualcomm's QPST utility offers a workaround if you can't launch EPST from your phone/dialer:
1. Find a copy of QPST 2.7 build 323 (don't ask me where). Install to PC.
2. Install HTC Sync (for drivers), then Connect phone as 'charge only' via USB with debugging enabled.
3. Open Device Manager and look under Ports to find which COM# is the HTC Diagnostic Interface.
4. Launch QPST Configuration applet. Click the Ports tab, then Add New Port. Select the COM port you found in Step 3 from the list at left, then hit OK. Your phone should now show up under the Active Phones tab as FFA/Surf QSD8650 Rev. 2.0. If not, unplug phone, dial ##DIAG#, wait 10s and plug back in as in Step 2.
5. Open the QPST Start Clients menu & choose Service Programming. Select your phone, hit OK, then click 'Read from Phone' button in the resulting window.
6. You now have access to the same configuration items you normally reach via ##778 on your phone. 'Write to Phone' will commit any changes you make, without further warning.
Obviously it is possible to seriously BORK your phone from here, requiring a restore from backup (which you should have before trying this). I take no responsibility for what you do with QPST. I used it only to change the tethering NAI from <number>@dun.vzw3g.com --> <number>@vzw3g.com so I could tether my wife's DINc. via Windows DUN. That worked, but I can't guarantee the results of other edits.

Same issue
Sorry to resurrect an old thread, but I am having nearly the same issue.
When I try to access epst from dialing ##778# on my girlfriends hero nothing happens at all. I ended up adding a shortcut with anycut and now the view or edit menu comes up. When I hit view it just hangs when I hit edit and enter the password it stays on "please wait verifying password". I can get ##data# to work and a few other ##xx# codes to work but I need access to the epst advanced settings.
Any help would be greatly appreciated, I have tried 1.5 stock 2.1 stock Fresh versions 2.1.3 (i think that's right) Fresh 2.3.3 and Damage control 2.09.....
I have qpst and CDMA workshop 2.7 but I know there are more options I need to change to get data on cricket. I don't have the $100 to spend on the new version on CDMA workshop.
Thanks in advance.

how to regain EPST

I'm on stock 2.2 rooted with s-off. To remove software like CityID I connected using 'adb' ,
mounted /system in clockwork recovery and moved the 'apk'
files to another folder. Now after this when I reboot I'm
not able to ##778.can I regain epst
Regards
Ananth

Try ##778#

Same result .##778# also does not work

I had this same problem while trying to get ad free working on my wifes phone. Some how all the messing about in /system changing permissions and creating symbolic links messed up epst and I couldn't get in except by using qualcomm tools on my pc. That was on 2.1...i only got 778 back when I upgraded the radio to 2.5 and flashed to rmk's froyo rom. Even then, I got a weird error when I tried to edit the dun entry...some thing about the radio and failing to enter low power mode...it went away after the first edit. I don't think doing a data wipe or rom flash clears epst data, so I'm guessing it was the radio upgrade that fixed the problem. I do wish someone could tell us what it is about editing stuff in /system that screws up ##778 access...

cantare said:
I had this same problem while trying to get ad free working on my wifes phone. Some how all the messing about in /system changing permissions and creating symbolic links messed up epst and I couldn't get in except by using qualcomm tools on my pc. That was on 2.1...i only got 778 back when I upgraded the radio to 2.5 and flashed to rmk's froyo rom. Even then, I got a weird error when I tried to edit the dun entry...some thing about the radio and failing to enter low power mode...it went away after the first edit. I don't think doing a data wipe or rom flash clears epst data, so I'm guessing it was the radio upgrade that fixed the problem. I do wish someone could tell us what it is about editing stuff in /system that screws up ##778 access...
Click to expand...
Click to collapse
how did u get qualcomm tools to see the phone? i'm using qpst and it's not seeing the phone at all.
and i get teh same error about 'no response from radio; can't enter low power mode' however it won't go away no matter how many times i try to commit.

shortbushemi said:
how did u get qualcomm tools to see the phone? i'm using qpst and it's not seeing the phone at all.
and i get teh same error about 'no response from radio; can't enter low power mode' however it won't go away no matter how many times i try to commit.
Click to expand...
Click to collapse
I got around that error by turning off every possible radio: 3g, wifi, all the gps stuff, and then putting in airplane mode for good measure. Reboot, make sure it's still in airplane-mode/everything off, and then try ##778 again. Don't know if it matters, but I tried to minimize steps in EPST--ie., open only Security and m.ip and edit only the two relevant entries; don't click on or view anything else. When I did all that, I got the changes to stick, and they stayed with the phone thru several upgrade flashes of Virtuous 2.x ROM
As for QPST, it's been a while... but you must plug the phone into usb (can't remember if you need debugging enabled), then dial ##3424#, wait several seconds (might have to install some htc drivers, but you may be able to ignore) then check your device manager for a new COM port called "htc diagnostic interface... and/or just start qpst config, add new port, and select the one that looks right. it will call the phone something different---ffa./surf or something, but you should be able to view and program service info.

I also got this message when i was trying to edit all that crap to get the 3G Mobile HotSpot app to work. what i realized is that it gives me that error only when i back out of the menu that lists the settings. If you are editing, you should edit, then close the text box (click ok) and then commit changes directly from that menu, and not back out.

[GUIDE] Getting the most out of your SGS [UPDATED: 28.02.2011]

I will try to set up a guide to contain all of the information to get the most out of your I9000 Galaxy S. First the fineprint:
I am not responsible for any damage that any of these instructions may inflict to your phone, computer or any other device that is used in the processes described herein. I am also not responsible if you lose your warranty by flashing your phone with unsupported firmware or if any of these instructions brick your phone, if it will rape your wife or if it will eat your liver with some fava beans and a nice chianti.
I didn't test any of the programs specified herein for viruses/trojans/etc. I run Windows in a VirtualBox that doesn't have access to the internet and doesn't contain any private data, so I don't care for viruses, if you care for your OS though, you should check the programs for viruses before running them.
Use common sense when following such instructions, some of the things may differ because of different program versions, different operating systems or different setups.
Some of these instructions are based on a stock firmware, if your firmware is modded in any way, some of the things described herein may be inappropriate for your device.
1. NOT bricking your phone.
--Why, when, where: Everyone's afraid of bricking their phone. I see the term "bricking" is being a bit overused in these forums though. Everyone is using it, even for the case where the phone can actually be "repaired" with a few simple hacks, IMHO the term "bricking" should only be used in the case where you get your phone in a state where it is inoperable AND you can not in any way repair it yourself.
--Prerequisites: A bit of common sense.
There are a few simple steps that you can follow, to get the risk of "bricking" (as in, you can not repair it yourself and need to somehow get Samsung to either repair it for you, or give you a new device) to a minimum:
1.1. Before trying any of the other steps, make sure that you can get to both the "Recovery mode" and the "Download mode" using the 3-button-combo. If this doesn't work for your device you can try following the steps described here: http://forum.xda-developers.com/showthread.php?t=810686
1.2. Try to avoid flashing stuff that contains a bootloader. The only way to permanently brick your phone so that you can not repair it yourself (at least AFAIK) is to flash a bootloader and then interrupt that flashing. If the bootloader didn't get flashed properly and it's broken, there isn't much you can do about it, and you need to somehow get Samsung to either repair it or give you a new one (if you're lucky). If the bootloader is fine, there is almost always a way to "repair" your phone yourself.
1.3. Do not interrupt the flashing processes. When using Odin or Heimdall to flash stuff to your phone, there is always the risk of bricking it if you interrupt the flashing process. If the bootloader is fine though and you can get into the "Download mode", you might be able to repair it.
If you follow these simple advices, it might save you money, nerves and also some time without your phone (the time that it takes Samsung to repair it, which can sometimes, depending on country, be even a couple of months).
2. Flashing stock firmwares.
--Why, when, where: You should usually do this if your phone doesn't work with your current firmware, if there is a new firmware out that might work better or if you just want to go to a stock firmware.
--Prerequisites: Odin, a stock firmware (from www.samfirmware.com for example).
NOTE: Apparently there are people that report that using Odin v1.3 might interrupt the flashing and leave you with a soft brick and that v1.7 doesn't have this problem. I have always used v1.3 and never had problems because of it, but if v1.3 isn't working for you, you might give v1.7 (or even heimdall) a try before giving up.
The steps to flashing a stock firmware are already described in a couple of other threads, like: http://forum.xda-developers.com/showthread.php?t=818556
Nonetheless, here a quick sum-up of what you have to do:
2.1. Open up Odin.
2.2. Put your phone in the "Download mode" with the 3-button-combo (Volume Down + Home + Power).
2.3. Connect your phone to your computer (DO NOT CONNECT THE PHONE BEFORE OPENING ODIN OR THIS WILL NOT WORK).
2.4. Odin should recognize your phone and one of the "com" boxes should light up yellow. If this isn't the case, try repeating the previous steps and eventually connect your phone to another USB port.
2.5. Select your firmware in Odin.
2.5.1. --OPTIONAL-- If you want your phone to be like new, you can select "Re-Partition" in Odin, which will make it repartition your Internal SD. In this case you also have to use a .pit file (WARNING -- you will lose all of your installed applications and settings).
2.6. Take a deep breath and click the "Start" button.
2.7. Wait for the firmware to be flashed and for the device to be restarted.
2.8. You now have a stock firmware. If you also selected "Re-Partition" in Odin, all your programs and settings will be gone and your device will be like new.
3. Rooting your phone and flashing a custom Kernel.
--Why, when, where: Rooting your phone will get you super-user permissions to Android (super-user is Linux's equivalent of "Administrator rights" in Windows). This will allow you to execute some programs that need root permissions, access partitions that you otherwise couldn't and do other cool stuff with it.
--Prerequisites: Stock firmware (as most --if not all-- of the custom ROMs or kernels have root permissions already), Odin or Heimdall.
There are many ways to get root permissions on your device, like with special apps (OCLF for example), with CWM (aka ClockWork Mod) or, my preferred method, flashing a kernel that has this built-in. For this example I will use the SpeedMod Kernel, which is my preferred one. If you have another kernel that you like and that has root built-in, you can use that one.
3.1. Download your preferred kernel (the version for Odin, not the one for CWM).
3.2. Open up Odin or Heimdall.
3.3. Put you phone into "Download mode" and connect it to your computer (DO NOT CONNECT THE PHONE BEFORE OPENING ODIN OR THIS WILL NOT WORK).
3.4.1. If you are using Heimdall, unpack your kernel until you end up with a file called zImage. Select that in Heimdall in the box for "Kernel (zImage)" and click Start.
3.4.2. If you are using Odin, select the file you downloaded in the PDA box and click Start.
3.5. After your Phone reboots, go into "Recovery mode" and go to "Advanced Speedmod ULK features" -> "ROOT / Install Superuser".
3.6. After rebooting the phone again, you should have root permissions.
4. Deodexing your apps and framework.
--Why, when, where: The system applications and the framework files on the Android OS are normally 'odex'ed. By deodexing, you will get rid of the .odex files that come with every apk and jar file and you will be able to edit the apks like any other apk. It will also save you a wee bit of space, and make your apps launch a wee bit faster.
--Prerequisites: Stock firmware (as most --if not all-- of the custom ROMs are deodexed already), xUltimate (this is what I found to be the easiest, if you know any software that is better, please let me know), root permissions.
You can download xUltimate from here: http://www.droidforums.net/forum/xeudoxus/47283-release-xultimate.html
There are more ways to deodex your apps, but I found xUltimate to be the easiest.
4.1. First of all, you need to get the files from "/system/app" into the subdirectory "origi_app" and all of the files from "/system/framework" into the subdirectory "origi_frame". Both "origi_app" and "origi_frame" should be in the folder you extracted xUltimate to. If they don't exist, create them yourself. There are actually two ways to get the files there, either with xUltimate itself (options 1 and 2) or by copying them to your SD with "Root Explorer" for example and then copying them from your SD to your computer (or with adb of course).
4.2. Deodex the apps and framework with xUltimate, options 3 and 4.
4.3. After deodexing is finished, the deodexed files will be located in the directories "done_app" and "done_frame" in your xUltimate folder. You have to get these files back to their original directories, in /system/app and /system/framework. Again, there are a couple of ways to do this, either with adb (MOST RECOMMENDED ONE), or with "Root Explorer". For the adb method, you should open a command prompt and execute following code:
Code:
adb shell
su
stop
mount -o rw,remount /dev/block/mmcblk1p21 /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
mount -o ro,remount /dev/block/mmcblk1p21 /system
reboot
5. Optimizing and zipaligning your apps.
I wasn't yet successful at optimizing or zipaligning. Optimizing (aka Compressing) the apps gave me a lot of FCs, optimizing the framework files gave me bootloops. If anyone has any advice on this, I'd be very thankful.
Also, see post #2
6. Protecting your screen.
--Why, when, where: This is not about protecting your screen from scratches, but rather about protecting it from degradation over time. As you might already know, AMOLED screens are prone to the "burn-in" effect. To elaborate a little: AMOLED uses Organic LEDs to display the amazing graphics you see on your display. These OLEDs are very good at displaying bright, colorful pictures, they have a downside though -- they fade over time. That means, the more a specific OLED is used, the less light it emits. If the whole screen would degrade at the same pace, that wouldn't be such a BIG problem, but the very nature of the OLED screens makes them degrade unevenly. That means the OLEDs that are used more frequently (like clock, phone signal, wifi, notification bar), get dimmer faster and this leads to ugly "shadows" on fullscreen apps. To be able to keep your screen as beautiful as new, I got a couple of tips, so that the display degrades more evenly and you avoid the ugly "shadows".
!! Most users won't even notice these degradations, also they won't be noticeable in 90% of use-cases and they will only appear after longer use (6 months+), but you can still use these tricks if you want your display to be almost as good as new a couple of years from now !!
6.1. Don't set brightness to 100%. At least not all the time. You should best be using a brightness setting that fits your ambient light, or the "Automatic brightness" setting. This will ensure that the OLEDs don't wear out as fast (the brighter you use them, the faster they will degrade).
6.2. Use a grey notification bar. The notification bar is the biggest "static" element on the screen. Most apps that are not fullscreen, will also show the notification bar, and this leads to an uneven degradation in that area if it isn't a neutral color. If you use a white notification bar, the OLEDs there will get dimmer faster and you will get an ugly shadow when using fullscreen apps, if you use a black notification bar, it will not degrade as fast as the rest of the screen and that area will be "brighter" in fullscreen apps, that's why I recommend a medium grey.
6.3. Use as little static elements as possible. If you don't need the clock in the notification bar, get rid of it. Get a theme that uses grey or green icons (see next step why) and try not to leave the phone on over night displaying the same static image.
6.4. Avoid blue. As you can see here for example: http://img24.imageshack.us/img24/8057/new1ls.png the blue OLEDs are degrading at a much faster pace than the green or red ones, this is why you should avoid using blue wallpapers or blue themes, they will make your display degrade faster than if you use a green theme and a green wallpaper for example.
These tips won't make your screen live forever, it will degrade too, but by using these tips, at least you can assure that you will have the most of your awesome display even in a year or two from now.
7. Theme-ing your phone.
Coming soon...
8. Unlocking your phone.
--Why, when, where: If you bought your phone with a contract, chances are that it might be locked in that specific network. If you want to also use other SIM cards in it, that are from another provider, you will have to unlock the phone (!! WARNING !! in most cases this will lead to a void warranty, please consult your contract).
--Prerequisites: Root privileges, adb.
8.1. Get the /efs/nv_data.bin file from your device to your computer. You can do this either with adb or by copying the file to your SD card with "Root Explorer" and then copying it over to your machine from the SD (Be sure to keep a backup of this file and the /efs/.nv_data.bin.md5 file.)
8.2. Open up the file in a hex editor, go to the address 0x181468, where you will see something like this:
FF 01 00 00 00 00 46 46 46...
We are interested in that first '01', that means the phone is locked. Just change it to '00' and save the file. Copy it back to your SD card and then with "Root Explorer" back to it's original location (or 'push' it directly with adb). Then remove the .nv_data.bin.md5 file and restart the device (Again, be sure to make copies of these files before modifying or deleting them!). After this, you should be able to insert any SIM card into your device and it should work without the need for any further hacks.
9. Setting up 'adb' on your machine.
--Why, when, where: adb (aka "Android Debug Bridge") is a tool that will let you execute remote commands on your android device. It is useful for debugging, accessing and copying files from/to your device and much more.
--Prerequisites: The android SDK, which you can download from here: http://developer.android.com/sdk/index.html and the USB drivers for your phone, which you can get by either installing Kies or by downloading and installing these drivers: http://www.mediafire.com/?a6ni32dk6nn953b (password is 'ragin' -- I didn't test them, so feedback on these is welcome).
9.1. Unpack the downloaded android-sdk.
9.2. Go to the unpacked directory and launch the SDK Manager.
9.3. Go to "Available packages" -> "Third party Add-ons" -> "Google Inc. add-ons" and tick the box next to "Google Usb Driver package" and the click on the "Install Selected" button. This will download and install the Google USB Drivers.
9.4. Whenever you want to connect to your phone through adb, make sure that you have enabled "USB Debugging" under "Settings" -> "Applications" -> "Development".
9.5. You should now be able to open up a command line ("Start" -> "Run..." -> Type "cmd" and click "OK"), cd to the subfolder "platform-tools" under the folder where you unpacked android-sdk and run "adb" in there.
Take some time to get used with the commands that adb offers, as these will help you to debug problems when you encounter some.
10. Lagfixing
--Why, when, where: It is said that the default filesystem that is being used for the partitions on the SGS (RFS) is having slow read times and thus the programs launch a bit slow, sometimes perceived as "lag". This can be fixed by converting the filesystem on the most used partitions to a more modern filesystem, like the ext filesystem, which not only has a bunch of improvements over such old filesystems like RFS, but also seems to be a bit faster.
--Prerequisites: A kernel that supports lagfix.
10.1. Since every kernel has it's own way of converting your FS, you should best look into the documentation of your kernel on how you can apply a lagfix. Some even apply it automatically for you (as in, "lagfix on" is their default setting).
11. Do NOT overcharge
--Why, when, where: Almost all new batteries have an overcharging protection. This means that the protection that is built into the battery will not let it charge to 100%. This is a feature, not a bug! This will help prolong your battery life while also keeping it safe from overheating/explosion/etc. Do not try to trick it and unplug and plug again until you see 100%, just get used to the fact that you can't have 100% battery anymore and live with it, or you risk destroying your battery.
12. Call recording
--Why, when, where: Most Galaxy S firmwares don't have the ability to record both streams of a call. This is not a bug, it was designed like this because in most countries it is illegal to record someone without their permission. Yes, there are apps that will let you record a call, but without software support, it will record the other end from the microphone, which will result in low quality, but there is a workaround.
This might be illegal in your country! I'm not responsible if you get sued for recording someone without their permission.
--Prerequisites: Root permissions, adb/root explorer, a 2.2.1 firmware.
12.1 Download the attached "CallRecord.zip" and unpack it.
12.2 After unpacking you should have 3 .so files. You need to get these files into your /system/lib folder with either adb or by copying them to the phone and then using "Root Explorer" to copy them to the proper folder.
12.3 Reboot.
12.4 After the phone has rebooted, you can use most apps that are on the market to record calls properly (that means not from the microphone). I use AllCallRecorder because it is simple and does the job. There are also Phone.apk's that have call recording built in, you could also install one of those and record your calls with it.
That is all for now. I will add more information as time goes by and I hope this will become a full guide on how to make the best out of our devices. If you have constructive criticism, questions or any ideas or tips on how to improve this, please let me know. If you don't have anything constructive to add to this thread, please DO NOT post. If my troll alarm goes off, I WILL ignore you.
Thanks goes to:
ragin for the USB drivers.
I have learned most of the stuff I put here from various searches on Google and the xda forums and I may not remember the exact threads I got them from. If you feel I have copied your work without giving you credit, I am very sorry for that. Please let me know via a post or a PM and I will link you in the "Thanks".
I am sorry if my English is bad, it's my third language though. I hope that the post is understandable by most people.

This post will contain instructions for *nix based operating systems
Because I am using Linux myself and because it is much easier to do stuff in the command line on Linux than it is on Windows, I will mostly post instructions for *nix systems. If anyone wants to help out by "translating" them over for Windows machines, I can include it in the next post.
Optimizing and zipaligning
I have managed to Optimize and zipalign the apps in /system/apps with the following code.
You need to run this on a *nix distribution (I used Ubuntu) with at least the following packages installed: bash, zip, unzip, optipng. Put all the .apk files from /system/app in a folder on your machine, cd to that folder and execute this code snippet.
Also, beware that some of the apps might not work (I had for example FCs with the camera and the phone app), I'll try to figure this out and make it pretty much foolproof. Currently everything but the .9.png files are optimized (the .9.png files are some special files that can't be treated like normal png files).
Code:
for apk_file in *.apk; do
file_name=`echo $apk_file | sed -r s/.apk//`
echo -ne "Unpacking\t$file_name.apk... "
mkdir $file_name
unzip -qq $file_name.apk -d $file_name
cd $file_name
echo -ne "Done.\n"
echo -ne "Optimizing\t$file_name.apk... "
for pngfile in $(find . -name '*.png' | fgrep -v .9.png); do
optipng -quiet -o 5 $pngfile
done
echo -ne "Done.\n"
echo -ne "Repacking\t$file_name.apk... "
zip -q -0 -r ../$file_name.apk *
cd ..
rm -rf $file_name
echo -ne "Done.\n"
echo -ne "Zipaligning\t$file_name.apk... "
zipalign -fv 4 $apk_file $apk_file.za
mv $apk_file.za $apk_file
echo -ne "Done.\n"
done
EDIT: I added the -0 flag to the zip command, since you should never "compress" apk files, because this leads to the FCs I was experiencing.

Post also reserved.

Last reserved post. You can start flaming now.

shantzu said:
Last reserved post. You can start flaming now.
Click to expand...
Click to collapse
Posted in the wrong place... try reading the faq's about where this belongs.

davidf said:
Posted in the wrong place... try reading the faq's about where this belongs.
Click to expand...
Click to collapse
Well, the rules of the development section state: "Rom Development - only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY."
I'd regard this as an "advanced tehnical discussion", since it also contains information on how to deodex and (to come soon) optimize/zipalign your apps, that's why I thought it would belong here. I would also like this to be a place for advanced discussions on best practices on deodexing, theme-ing, and otherwise modifing a stock ROM manually. If the moderators still think that this doesn't belong here, I'm sorry, and would like to ask them to move it to the proper Forum.

Sticky Material.
Don't you think your Title is misnamed? The thread contains much more than just a guide getting most out of our SGS.
Very good effort anyway.

ragin said:
Sticky Material.
Don't you think your Title is misnamed? The thread contains much more than just a guide getting most out of our SGS.
Very good effort anyway.
Click to expand...
Click to collapse
Well, I didn't know what else to name it, and didn't want to use a really long name. I think this title best describes what it's about...
Thank you for your reply!

very good post. It'll be extremely helpful for new users i reckon.

question
can this method be used on almost any samsung galaxy? (i have galaxy 551)
and about deodexing...is xUltimate a general app for any Android phone or only for SGS ?

Awesome stuff thanks for this cleared up a few things

waveboy2u said:
can this method be used on almost any samsung galaxy? (i have galaxy 551)
and about deodexing...is xUltimate a general app for any Android phone or only for SGS ?
Click to expand...
Click to collapse
Well, the program seems to be posted in the "Motorolla Droid" forum, so I don't think it was even intended for the Galaxy S. If I were to guess, I'd say it might work on any Android device. Just be sure to make a backup in case anything goes wrong.

Thanks alot! Never knew the degrades display.
Sent from my GT-I9000 using XDA App

Shantzu, first, thank you very much for this valuable contribution!
While I agree that it is related to "highly technical discussion", it's not directly connected to ROM cooking/development. In fact, this is the kind of thing that people should read before they start mucking about in the dev section
I've gone ahead and moved it to the general section and made it a sticky topic for now. However, those are starting to pile up in this section, so we'll likely roll up several useful threads like this one into one unified reference sticky here soon.

sirphunkee said:
Shantzu, first, thank you very much for this valuable contribution!
While I agree that it is related to "highly technical discussion", it's not directly connected to ROM cooking/development. In fact, this is the kind of thing that people should read before they start mucking about in the dev section
I've gone ahead and moved it to the general section and made it a sticky topic for now. However, those are starting to pile up in this section, so we'll likely roll up several useful threads like this one into one unified reference sticky here soon.
Click to expand...
Click to collapse
I was thinking about this guide as some kind of "cook your own ROM directly on the device", that's why I was also including tips on how to deodex the apps and I'd also like to include tips on how to set up themes (not install third party themes, but rather explain where each icon can be found and how it can be modified) and other mods. Anyway, if you think it better fits in the General section, I'm fine with that, as you can see I'm pretty new in these forums and not that experienced (for example I have also seen a guide on how to manually unlock the phone that was stickied on the Developers section).
Anyway, sorry again for the trouble and thanks for clearing it up!

Very good post. Thank you!!

Very good work. One thing i noticed though: you use ext fs for the system rw remount. This i think will only work for ext converted system partitions not the original rfs system.
Sent from my GT-I9000 using Tapatalk

liraindon said:
Very good work. One thing i noticed though: you use ext fs for the system rw remount. This i think will only work for ext converted system partitions not the original rfs system.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I know, it normally shouldn't work, but it actually does. I don't have any lagfix applied and it works just fine. I will try and see though if I can come up with a more general command that 100% works in all cases.
EDIT: ok, not specifying any filesystem at all works too. I will have to see if this also works with a lagfix enabled, but I guess there shouldn't be any problems.
Thanks for your comment!

whoa didnt know about degradation... thanks!

nice
very good write up.. +1

[tool] [app] diag mode switch by solcam

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.