Develop Bugs

[DEPRECATED][GUIDE] Temporary root your Desire Z

HTC Vision // Desire Z Temporary Rooting
1. Download this package: MegaUpload
2. Copy the content of the package in a folder called "temproot" in your SDCard root.
3. Execute this script:
Code:
#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/
cd /data/local/tmp/
chmod 755 *
./rageagainstthecage-arm5.bin
ps
4. Restart Terminal Emulator
5. Execute this script:
Code:
#!/system/bin/sh
/data/local/tmp/busybox killall rageagainstthecage-arm5.bin
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
/data/local/tmp/busybox cp /sdcard/temproot/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /sdcard/temproot/su /system/bin/su
/data/local/tmp/busybox cp /sdcard/temproot/busybox /system/bin/busybox
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
Now your phone is temporairily rooted and you can even get root on adb.
Thanks to:
*- C-Skills for the exploit
*- Guys in G2 section for testing it.

Sweet
but what do we do to get full root access?

There is no full root yet for either this device or g2. You will see that later

M9x3mos said:
There is no full root yet for either this device or g2. You will see that later
Click to expand...
Click to collapse
excited
wonder if the "z" and G2 can use the same Recovery image and Roms..or wil it be like htc magic and My touch ?

G2 and Z are the same device.... HTC Vision.
Radio ROMs and BootLoaders should be compatible, we only need someone that can verify, but AFAIK a G2 owner flashed a full Desire Z ROM and worked without problems.

kholk said:
G2 and Z are the same device.... HTC Vision.
Radio ROMs and BootLoaders should be compatible, we only need someone that can verify, but AFAIK a G2 owner flashed a full Desire Z ROM and worked without problems.
Click to expand...
Click to collapse
any idea if the G2 is a test unit or retail unit? i want senseui (sad i know, but im a sucker for nice graphic)

Correction. The Desire Z rom currently be flashed to G2 but the PC10IMG.zip original G2 rom does work on the Desire Z

I try using this but My G2 didn't work, I got stock here at this step:
"#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/"

Anyone try overclocking it yet?

waiting89 said:
I try using this but My G2 didn't work, I got stock here at this step:
"#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/"
Click to expand...
Click to collapse
Are there any errors?
Please provide more details, it's only a file copy...

kholk said:
Are there any errors?
Please provide more details, it's only a file copy...
Click to expand...
Click to collapse
Link is down kind sir. I found this one Droid2Root.rar from another forum.

waiting89 said:
I try using this but My G2 didn't work, I got stock here at this step:
"#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/"
Click to expand...
Click to collapse
It gives you an axxs denied when you try that. says "cp: permission denied." I can't ls inside of /data either.

do changes persist?
If I do this temp root and install busybox or tether, will the changes be wiped out on restart?

"cp: permission denied." Yes this is the error code I get.
"export PATH=/data/local/bin:$PATH
$ $ #! /system/bin/sh
$ cp -R /mnt/sdcard/temproot/* /data/local/tmp/
cp: permission denied
$"
That's exactly what it appears on the terminal.

I read this on androidspin :
If you root your new G2 phone, HTC has embedded a chip that will detect this and return the phone back to its original factory settings. So much for open source!
They can do this?

The file is no longer available. Can someone repost it?
Thanks

Hmm, yep same problem, cp gives me a permission denied, and the folder /data is a system file seems like we don't have any access to it. on the example, seems like there's # instead of $ which means it has admin access, how did you get to that state? sorry android noob here :-\

stian230 said:
I read this on androidspin :
If you root your new G2 phone, HTC has embedded a chip that will detect this and return the phone back to its original factory settings. So much for open source!
They can do this?
Click to expand...
Click to collapse
Actually no, and its covered in many threads, and I'm sure the op doesn't want the discussion started again.

There isn't any chip that will magically transform your HTC Vision in an airplane / automobile / house / cigarette industry.

script?
Could somebody help with packaging this as a script so we could re-root simply?

[Q] Another unroot/s-off problem

Im hoping someone can point me in the right direction here.
Clearly I did something wrong. I could use a little direction here to get back
to factory state phone. I have a "factory phone" without root and stock apps but
S-OFF and I need to get back to S-ON
1) Rooted using Rage/Gfree method for temp root/s-off/perma root
2) Wanted to roll back(please don't ask why)
3) Tried to follow step 1a) on http://forum.xda-developers.com/showthread.php?t=835971
4) Receive following message
-- Installing: SDCARD:/stock_root.zip
E:Board does not support mtd utils.E:Failure at line 344:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
5) Recovered from clockwork backup
5) Went to step 1b successfully
6) Followed step 2 successfully
7) Phone patched itself OTA(step 3)
8) checked bootloader to find S -off
Steps I have taken
1) Regain temp root using rage
2) copied gfree back to phone
3) from terminal "# ./gfree -s on"
4) "#sync"
5) Reboot into bootloader to find S-OFF *sigh*
Bootloader items
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
**Amendment* I don't have the gfree partition backup that gets created the first time you root

brandonmcgrew said:
Steps I have taken
1) Regain temp root using rage
2) copied gfree back to phone
3) from terminal "# ./gfree -s on"
4) "#sync"
5) Reboot into bootloader to find S-OFF *sigh*
Bootloader items
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
**Amendment* I don't have the gfree partition backup that gets created the first time you root
Click to expand...
Click to collapse
You have the regular bootloader (not the eng one), so the fact you have S-OFF still means your "gfree -s on" didn't work. You need to try that again, and look for what error messages were produced at the time.

You have the regular bootloader (not the eng one), so the fact you have S-OFF still means your "gfree -s on" didn't work. You need to try that again, and look for what error messages were produced at the time.
Can you give me the steps for that. I got temp root with rage and ran the s-on and sync commands. do you want the output from that???

brandonmcgrew said:
Can you give me the steps for that. I got temp root with rage and ran the s-on and sync commands. do you want the output from that???
Click to expand...
Click to collapse
Yes, please post up the output from when you run "./gfree -s on", that's the bit that sounds like it's failing.

# export PATH=/data/local/bin:$PATH
# cd data
# cd local
# ./gfree -s on
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.17-g9ab3677
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Searching for mmc_blk_issue_rq symbol...
- Address: c029c72c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029c000
Kernel memory mapped to 0x40001000
Searching for brq filter...
- Address: 0xc029c72c + 0x34c
- 0x2a000012 -> 0xea000012
Patching and backing up partition 7...
Done.
#

Well that's odd, that looks liked it worked ok.
What about if you try the stuff at http://forum.xda-developers.com/wik...ion#3._.28OPTIONAL.29_Verify_you_did_it_right to verify that S-ON has been set ?

Ok at this point I decided to get back to a spot where I felt comfortable. So I permarooted using rage/Gfree. I have also installed Clockwork and done a nandriod. So at this point here is my status. Perhaps you can help me get back to factory
1) Factory Stock w/OTA
2) Root
3) gfree verify
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
At this point I can't do anymore today but if you could/would give me a little help getting back to factory stock no root s-on simlock on I would REALLY appreciate it.

I'll do my best not to derail, but I cannot even install the stock ROMs anymore, and I think it is because of the version of CWR I am running. Since I wanted CM7, I had to install CWR 3.x. Is it safe to assume that any Android 2.3 ROM needs CWR 3.x, and any Android 2.2 or previous required CWR 2.x?

OK I finally got back to working on this and got a FIX!
See previous post(s) to get caught up......done ok GOOD
**THIS REQUIRED ADB TO BE WORKING**
**IF YOU TAKE THESE STEPS BELOW I TAKE NO RESPONSIBILTY IF SOMETHING GOES CRAZY AND YOU BRICK YOU PHONE. IM A NEWB TO THIS SO THIS IS JUST WHAT I DID**
Where I left off is I was Stock OTA rooted using the gfree/rage method. I had Clockwork installed and a nice nandroid backup(Such a good feeling). Copied backup to computer
1) Followed steps to a tee downgrade from OTA -->http://forum.xda-developers.com/showthread.php?t=831398
2) With a fresh preOTA phone I unmounted my sdcard
3) Formatted SDCard(no idea if this helped but made me happy)
4) Copied Visionary R14 to root of sdcard-->http://android.modaco.com/content/h...m/320722/19-nov-r14-visionary-one-click-root/
5) Enabled Unknown Sources install from Manage application
6) Installed File Manager from Market
7) Used File Manager to install Visionary
8) TempRoot using Visionary
9) Downloaded latest gFree from -->http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/gfree/gfree_02.zip
10) unzip gfree_02.zip
11) open command prompt
12) enter following commands to confirm you have root
adb shell
$ su
**on phone should see superuser prompt...press allow**
if you see a "#" you got temp root
# exit
$ exit
13) Push gfree to phone
c:\adb push gfree_02 /data/local
c:\adb shell
$ su
# cd /data/local
# chmod 777 gfree
14) Set S-On
# ./gfree -s on
15) Set CID
# ./gfree -c TMO010
# exit
$ exit
16) Power off
17) Boot phone to bootloader (Hold Power +Vol Down) and confirm
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-0425
RADIO -26.02.01.15.M2
eMMC-boot
18) Reboot Device. ALL DONE!!!
**If you want you could temproot again and remove all files copied for gfree to /data/local or you could do a factory reset from the bootloader**

[Q] Desire Z with 2.42.405.2 Able to downgrade? ( i'm able to temproot )

Hi all
I have a European HTC Desire Z with this info:
Android 2.3.3
Sense 2.1
Build 2.42.495.2
Vision PVT Ship S-ON
Hboot-0.85.0013
MicroP-0425
Radio 26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
I am able to temproot this phone with the method provided here:
http://forum.xda-developers.com/showpost.php?p=15851661&postcount=1
using the code:
Code:
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
However the downgrading part fails on me.
After entering the bootloader menu is scans the SDCARD and finds the PC10IMG.zip
telling me: loading...[PC10IMG.zip], after that it's saying: Checking..[PC10IMG.zip].
After checking it just goes back to the Menu without asking me to update etc.
I did however changed the misc_version and followed the guide precisely.
I searched and found some Threads saying this version isn't rootable yet. though they were couple months old, and I am able to get temp root. it should be do-able right?
Can someone please confirm this and tell me how to, or what i'm doing wrong and let this baby free.

I followed the guide to the letter, without changing misc_version or anything, and I managed to downgrade and root without problems on first try. Same version as you, Desire Z bought in Poland.
Just be sure to grab the file for Desire Z and not for T-Mobile G2 and it should work

costipl said:
Just be sure to grab the file for Desire Z and not for T-Mobile G2 and it should work
Click to expand...
Click to collapse
What file are you referring to here?
Also, how is it possible to downgrade without changing the misc_version, i thought it was all about changing that in order to make it work haha.

Sorry, I think I misunderstood your post...
I did this to change misc_version:
Code:
$ adb push misc_version /data/local/tmp/misc_version
$ adb shell chmod 777 /data/local/tmp/misc_version
$ adb shell
# /data/local/tmp/misc_version -s 1.00.000.0
I assumed you changed the "1.00.000.0" to something else (while browsing the forum I found in some threads that people used a different value on DZ).
As for the file I was referring to, I meant the stock rom image - 1.34.405.5_PC10IMG.zip
Maybe you grabbed the file "PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09 b_26.02.01.15_M2_release_149459_signed.zip", which is for G2?
Other than that, I'm not familiar enough with the bootloader to be of any help.

costipl said:
Sorry, I think I misunderstood your post...
I did this to change misc_version:
Code:
$ adb push misc_version /data/local/tmp/misc_version
$ adb shell chmod 777 /data/local/tmp/misc_version
$ adb shell
# /data/local/tmp/misc_version -s 1.00.000.0
I assumed you changed the "1.00.000.0" to something else (while browsing the forum I found in some threads that people used a different value on DZ).
As for the file I was referring to, I meant the stock rom image - 1.34.405.5_PC10IMG.zip
Maybe you grabbed the file "PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09 b_26.02.01.15_M2_release_149459_signed.zip", which is for G2?
Other than that, I'm not familiar enough with the bootloader to be of any help.
Click to expand...
Click to collapse
I redownloaded the zip file and you just made my day i had a other zip from another thread. but with the exact same name.. maybe corrupted ? THANKS!

Radio's get flashed AFTER you flash your ROM, not before ;P
Remember to rename your PC10IMG.zip to something else after you're done rooting/installing a new ROM, cos if anything happens and your phone crashes and you need to enter recovery, having PC10IMG.zip on the root of your SD will ensure that you never get into recovery
Power + Vol Down boots into bootloader, and it automatically scans for updates, PC10IMG.zip being one of them. Only when there are no update files on SD root will it give you a choice of booting into Recovery to well, recover your phone

[Q] Problems downgrading/rooting Desire Z Gingerbread.

Hello everyone!
Not my phone, just helping a friend
We got problems downgrading from Gingerbread to earlier version of Android.
So, wanted to root, flash custom recovery, then MIUI.
Started with this tut, then understood, that Gingerbread isn't rootable and it needs to be downgraded.
So, tried [GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo and HTC Desire Z: Firmware Downgrade (Gingerbread).
So, installed JRE, JDK, SDK (ADB), drivers.
With phone plugged to PC (USB Debuggind ON), ADB & Device manager sees it.
So, moved files to C:\android-sdk\platform-tools and ran cmd (administrator privileges). Till "adb shell it's good". But, after that, when ran chmod, it says, that permissions denied.
Question:
What we're doing wrong and how to fix it?
We've read so many guides, but unsuccessfully so far..
Device HTC Desire Z
Android 2.3.3
Kernel version 2.6.35.10-g7b95729
Baseband 12.56.60.25U_26.10.04.03_M
Build 2.42.405.2 CL84109
Thanks about helping!

Is it permission denied when u try to change the version? If permission denied during change the version, run this command:
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Sent from my HTC Vision using XDA App

Are you sure your temp root is working?

aDeQ666, no, it wont chmod when typing chmod 777 /data/local/tmp/fre3vo, so - no temp root for us. Tried visionary, z4root, SuperOneClick - nothing works
It was updated from Froyo to Gingerbread via OTA, i think that's the issue? What else we can do? Thanks!

Could you post a copy/pastebin of your cmd when running it? It'll be much easier to spot the error if we can see exactly what you did/are doing.
-Nipqer

I have one problem when i tried to root htc desire. i already done the downgrade and now i am want to root... i folllowed the instructions on the link you gave untill this
[chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
NOTE: You will drop out of the shell after this command. Restart the shell using:
adb shell
cd /data/local/tmp
./busybox md5sum /dev/block/mmcblk0p18]
well after command:
chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
i`m not dropping out of the shell and the next instruction results with a "cd: bad substitution" msg. what should i do?
sorry for my bad english

When do u received the error? Is it when u downgrading or try to root? Are u using the wiki guide?

What I've down a few times now (and this does work) is use the fre3vo guide (the one you linked) to downgrade then continue with the guide below from step 14 or 15 to gain perm root.
http://forum.xda-developers.com/showthread.php?t=905261
Hope that helps.
Edit: You're better off flashing 1.34.405.5 as the one on the CM wiki may not be working. Its worth a shot IMO.

aDeQ666 said:
Is it permission denied when u try to change the version? If permission denied during change the version, run this command:
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Hi, i have been trying to change my misc version but it gives me permission denied and i have # (root) already. So i tried chmod after cd which didn't have a problem but now when i try harder./misc_version it says the file not found.
Please help

I used this guide. it worked fine for me =)
http://forum.xda-developers.com/showthread.php?t=905261
*faceslapps self* sorry. I was a tad too fast. I didn't see that someone allready posted that guide here.

This is the command that i use before this:
adb push misc_version /data/local/tmp/misc_version
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Sent from my HTC Desire Z using XDA App

I used this guide when I had to go through the pain of downgrading my desire z http://forum.xda-developers.com/showthread.php?p=15851843 . It worked very easily, just follow the instructions nice and carefully, the problem is that you need ADB set up for you to use that guide though.
Once you downgrade though, I would use the guide here for rooting your phone http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 .
I hope that helps, that's what I used for my phone.
To be more precise in regards to the problem though, i just realised that i had the same problem as you when i was trying to run the chmod command where i had temproot but i kept getting "permission denied". As it turned out, i had accidentally written "adb push fre3vo /data/local/tmp/" instead of "adb push fre3vo /data/local/tmp" when i was following that downgrading guide. Basically what my mistake did was, it pushed fre3vo into a new folder within /tmp instead of just placing fre3vo in /tmp. So what you can do to figure out where fre3vo is, navigate to the /tmp folder using CD (in adb shell) and once you get to /tmp, type "ls". This will then display all the contents of /tmp and then you will be able to see if you accidentally created a folder like i did. Then once you check that, when you go to run the chmod command, you have to run it like "chmod 777 /data/local/tmp/**possible accidental folder name**/fre3vo", see if that works now .

Use this guide should do the job for you www.desirez.strawmetal.com

aDeQ666 said:
This is the command that i use before this:
adb push misc_version /data/local/tmp/misc_version
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Sent from my HTC Desire Z using XDA App
Click to expand...
Click to collapse
were you able to fix this problem?

I had the same problem with my Desire Z with OTA 2.3.3.
Finally I've unlocked bootloader as show at htcdev.com.
Then I used this guide http://forum.xda-developers.com/showthread.php?t=1453066 (great thx for it), and CM 7.1 works like a charm.
All best.

allendon said:
were you able to fix this problem?
Click to expand...
Click to collapse
For my case, yes.
Sent from my HTC Vision using XDA App

[Q] Errors in running "fixsu.sh"

Dear all,
I'm trying to root my G2. I was following the instructions described in the Strewmetal's PDF file. It went very smoothly until I hit this issue. I was in the section of "[OPTIONAL] TEMP-ROOTING TO BACKUP". It went fine until the last command which is:
adb shell /data/local/tmp/fixsu.sh
I had the following error:
/data/local/tmp/fixsu.sh: cannot create /system/etc/passwd: I/O error
Unable to chmod /system/etc/passwd: I/O error
/data/local/tmp/fixsu.sh: cannot create /system/etc/group: I/O error
Unable to chmod /system/etc/Group: I/O error
cp: can't create '/system/bin/su": Invalid argument
I tried the previous commands a few times just in case, but it seems there are no issues with the previous commands.
It would be great if someone can shed some light here.
Thank you very much!
- kazs

well for the most part you will probably never need your back up so you can definitely skip this part if youd like
but if you must id go to freenode #g2root
youll get real time help from people who have seen it all - when your done make sure you post the problem and the fix so the next person who reads this will learn

demkantor, thank you very much for the reply. I actually skipped the section and went ahead. Then, I just completed the entire process according to the PDF file. It went fine everything. But, I think I had an issue after I enter:
# reboot
My G2 automatically started the reboot process with the white screen with green "htc" logo, but it stuck there. I waited 10 minutes, but it doesn't change.
Did I screw up?

well not necessarily, if you have a g2 and flashed the dz hboot then your emmc partitions are different and your current rom wont start up. same thing if you have a dz and flashed the g2 hboot.
if you followed either the xda wiki or the cyanogen wiki then everything should be just fine.
pull battery and wait a few seconds... reinstall
boot while holding volume down and write down everything you see here
(you may have to take out sdcard or at least remove the pc10img.zip from your card at this point)
you should see something very similar to this:
VISION PVT ENG S-OFF
HBOOT-0.76.200 (PC1010000)
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Aug 20 2010, 16:15:01
then some options,
write down your screen and well see if your good

Thanks again for the quick reply. I really appreciate it.
It says:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1010000)
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 8 2010,15:56:38
Is it good? If so, what should I do next?
Thanks!

you should be just fine, looks like you have the dz hboot.
next step would be to pick your rom, do something simple and known stable at first to make sure all is well and then move on and try a bunch
recommend elitemod cm7 (youll find this and many many others in the dev section, look for a compilation in the 2nd or 3rd post
boot into hboot holding volume and down
wait a second or two after image check completes (no pc10img.zip on sd card!)
now hit volume down and select recovery with the power button
(the guide you followed should have brought you to clockworkmod recovery)
in here toggle (with volume keys but select with trackpad) to mounts>usb mount
put your rom on sdcard ---- unmount
toggle to wipe options (wipe everything you can)
toggle to apply update from sd card (recommend to flash a superwipe script here)
flash rom
now reboot
in the future look into updating radio (lots of threads on this)
update to 4et touch recovery (my opinion way better)
try some roms
do full wipes and superwipes between flashes
always do a nandroid backup before you flash or wipe anything
most importantly have fun!
rooting a friends g2 as i am writing this (got it down to about 15mins!)
time to do all i recommend for myself now! - we are in the same boat!

Thank YOU very much! I just installed EliteMod & Kernel CM7 according to your recommendation and it's working just fine so far. I really appreciate your big help!
I will check for the radio update tomorrow (it's getting very late here...) and I will try other ROMs as well.
May I ask the last question at this time? So, my G2 is not rooted. Does it mean the phone is unlocked as well? I mean I have a plan to go to Asia in August and I would like to buy and use another SIM instead of my T-Mobile SIM over there. I'm sorry for the novice questions though...
Thanks!!!

i think you mean now that you are rooted...
anyway here is the best way to check your work:
5. Verify the success of gfree
You can verify the success of gfree by using gfree_verify.
Download gfree_verify.zip from gfree_verify_v01.zip (md5sum 8e3535fd720d19fa0aec4eb711b897c4)
Unzip gfree_verify_v01.zip to a place on your PC.
Open a terminal (or command window) on your PC and change the current directory to where the files are on your PC and execute these commands:
$ adb push gfree_verify /data/local/tmp
$ adb shell chmod 755 /data/local/tmp/gfree_verify
$ adb shell
In this shell:
Remark: When you run su for the first time in the adb shell make sure the the screen of the phone is unlocked. Because when you enter the command the Superuser app will show up and ask you if you want to grant superuser access to app Unknown (2000).
Check the Remember check box and click allow.
$ su
# cd /data/local/tmp
# stop ril-daemon
# ./gfree_verify
You should see the following output:
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
Start the interface layer again (IN THE ADB SHELL ON YOUR PC):
# start ril-daemon
Did it work? Here's what you're looking for:
@CID: 11111111 <--- this response means you have superCID!
@SIMLOCK= 00 <--- this means your simlock is off.
@secu_flag: 0 <--- this means your radio is S-OFF.
if simlock =00 then you can put in any simcard and use anywhere that supports the proper cellular bands

Thank you very much! I have confirmed that the simlock is off on my phone.
PS Sorry for the typo and that I confused you. I wanted to type "now", but typed "not"...