Develop Bugs

[Q] Gfree Rooting!

Hey guys,
I took the advice of tons of people here to try the gfree method instead of the hboot or something, or the visionary permaroot.
the thing is, i did it my way and was too lazy to install ADB cuz it always failed and I don;t know how to use it.
I got a desire z- asian version
with a 1.2 version (NOT 1.7 that can't use gfree)
anyway
here's what i did
1) Installed Visionary to Temproot
2) got superuser for terminal emulator (ON PHONE)
3) chmod 777 the GFREE File on SDCARD
4) Tried to run it with the ./gfree -f command
5) IT SHOWS PERMISSION DENIED....WHYYY!???
WTF?
Anyway, if theres no o
ther way than ADBing this, I'll just go ahead and use the .ko file from the other rooting method..
THANKS GUYS

kwhkkwhk said:
Hey guys,
I took the advice of tons of people here to try the gfree method instead of the hboot or something, or the visionary permaroot.
the thing is, i did it my way and was too lazy to install ADB cuz it always failed and I don;t know how to use it.
I got a desire z- asian version
with a 1.2 version (NOT 1.7 that can't use gfree)
anyway
here's what i did
1) Installed Visionary to Temproot
2) got superuser for terminal emulator (ON PHONE)
3) chmod 777 the GFREE File on SDCARD
4) Tried to run it with the ./gfree -f command
5) IT SHOWS PERMISSION DENIED....WHYYY!???
WTF?
Anyway, if theres no o
ther way than ADBing this, I'll just go ahead and use the .ko file from the other rooting method..
THANKS GUYS
Click to expand...
Click to collapse
Ive seen this before, which files did you put on the sdcard, If you put the entire gfree02.zip file on your sdcard this is worng. You need to unzip the gfree02.zip file and place only the gfree file from the unzipped gfree02.zip file on the root of your sd card.
then re-run using this Code:
Code:
$ su
# cd /sdcard
# chmod 777 gfree
# ./gfree
# sync

i did everything as said, moved only the gfree file onto the sdcard.
everything works until ./gfree
it says: "./gfree: permission denid"
i don't really know whats wrong. the kernels right - its a stock 2.2 asian desire z on 1.2 version or something.
thanks SO MUCH For the reply though. I REALLY APPRECIATE IT

The guide says not to use Visionary for temp root before using gfree, in fact it says to either turn it off (if set to auto-soft-root on boot) or uninstall it altogether.
the gfree method has you use the rage method to obtain temp root.

raitchison said:
The guide says not to use Visionary for temp root before using gfree, in fact it says to either turn it off (if set to auto-soft-root on boot) or uninstall it altogether.
the gfree method has you use the rage method to obtain temp root.
Click to expand...
Click to collapse
Thats if your gonna temp root with Rage, requires ADB to push the files, which he is trying to avoid using ADB, gfree has been done the way he is trying before.

I don't believe you can run the gfree program from the sdcard mount point. You should try moving it to the phone itself (try putting it in /data/local directory as instructed in the wiki). That should take care of your permission denied issue.
Also, you may want to copy over all of the other files as listed in the wiki (except for rage since that's not needed for you). The wiki says you need to run the root command after running gfree (it'll set up things like busybox and su for you). You could also do all it manually yourself if you really wanted to...

But how do I move it off the sdcard? I tried using es file explorer but it says gfree can't be moved. And I cant mount the internal memory. Thanks for the advice though

If you are temp rooted you should be able to remount your file system as read/write, you will need to do this to copy files to the /system path and set permissions.

raitchison said:
If you are temp rooted you should be able to remount your file system as read/write, you will need to do this to copy files to the /system path and set permissions.
Click to expand...
Click to collapse
How would I do that?
remounting the file system? i can't find that option in settings...
and by copying the files, is that done through a file manager on the phone?
or on a computer?
thanks so much guys for the help

It shouldn't make a difference if gfree is on /sdcard or not.
To the OP - do you have a # (root) prompt when you are trying to run gfree ? You need that or it won't work. Have you followed exactly the commands that joemm posted, and you didn't get error messages from any of them ?

Yes I do have that sign. Everythin works (chmod, su) until the last code which is to run it.

kwhkkwhk said:
Yes I do have that sign. Everythin works (chmod, su) until the last code which is to run it.
Click to expand...
Click to collapse
Do "ls -l gfree" and copy and paste up here the output please. Something is still wrong.

It shows
Rwxr-x system sdcard_rw 134401 2010-12-11 08:57 gfree

steviewevie said:
It shouldn't make a difference if gfree is on /sdcard or not.
Click to expand...
Click to collapse
By default on my phone (running CM6), the sdcard mount point is mounted with the noexec option (so no direct execution of any binaries). I assumed it was this way on all roms for security reasons, but I'm not familiar with Visionary. Are you saying that Visionary remounts the sdcard as exec for you? Or that it's already that way by default for the stock rom? If so, then yes, you can leave gfree on your sdcard. You can check by running mount in the terminal. You should see an entry for /sdcard with all of its options after it. If you see noexec in there, you will either need to move the files to the phone or remount your sdcard with the exec option instead.
If you want to copy files over to your phone while rooted, you could use Root Explorer (probably easiest way). I believe there are other free programs that allow r/w access, but I haven't tried anyway. Otherwise, you should be able to copy over the files in Terminal. I think the data partition is mounted as r/w but you can verify with the mount command mentioned above (on the line containing /data, look for either rw or ro). If there is a rw, then just use the copy command to copy the files where you need to:
Code:
su
cp /sdcard/gfree /data/local
If the data partition is mounted as ro, you'll need to remount as rw first:
Code:
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p26 /data
Pretty sure that won't be needed though.

ianmcquinn said:
By default on my phone (running CM6), the sdcard mount point is mounted with the noexec option (so no direct execution of any binaries).
Click to expand...
Click to collapse
ooh, ok, thanks, I never knew that. My apologies, that looks like why it's not running then.
If you want to copy files over to your phone while rooted, you could use Root Explorer (probably easiest way). I believe there are other free programs that allow r/w access, but I haven't tried anyway. Otherwise, you should be able to copy over the files in Terminal. I think the data partition is mounted as r/w but you can verify with the mount command mentioned above
Click to expand...
Click to collapse
Yeah, /data is mounted as rw by default, so should be fine to copy as you said.

Alright. This WORKS for running gfree
but for the step that makes the root "stick" according to the guide here...
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
where i says :
"You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:
# /data/local/tmp/root
# sync
"
I can't find /data/local/tmp/root
so it fails to run..
any suggestions on this?
gfree runs fine. it says done when I did ./gfree -f
thanks guys for all the help!

kwhkkwhk said:
# /data/local/tmp/root
# sync
"
I can't find /data/local/tmp/root
so it fails to run..
any suggestions on this?
Click to expand...
Click to collapse
root is the binary that actually does the rooting, it's included in the gfree_temp-root zip. Did you copy that to /data/local/tmp or did you copy it somewhere else?

the only thing i did, if you were able to see my previous problem,
was just copying the gfree file over to the /data/local and running it
by ./gfree -f
other than that, i copied nothing else, since the guide using adb and the commands used moved nothing other than the gfree file i moved to /data/local
I didn't use the gfree_temp-root.zip folder, i used the gfree_02.zip (permaroot) folder.
and i temp rooted using visionary to get the needed gfree file onboard.
then do i need other filed then?
thank you so much for the quick reply.

kwhkkwhk said:
then do i need other filed then?
Click to expand...
Click to collapse
Yeah, root is actually just a script that installs things like busybox and su for you (see my earlier post).
You should copy those files to the proper locations listed in the wiki (pretty much every file but rage). It'll make life easier (otherwise, you'll have to do all of that stuff manually).
Congrats, you almost have a fully rooted phone.

THank you so much!
and thank you to all of you guys who helped me!
I managed to root my phone finally! Without adb!
YAY

[Q] Moving new hosts into /system/etc

This is a copy post from here when I realised it was in the wrong spot.
I have a rooted Desire using unrevoked and am trying to use AdFree on 2.2 but I am told that the hosts file I need to block ads cannot be written to /system while Android is running. I did some searching but, alas, no luck on an answer.
I do not know how to get to a command prompt to follow the instructions in this thread and have looked in the ClockworkMod Recovery mode for something similar.
Anyone have an idea?
edit:
I also got Root Explorer off the market (which cannot simply copy the hosts file into /system/etc/ as it does not have access whilst Android is running) and I think the command prompt I need is the pc cmd prompt when the device is plugged into USB, but I am unsure which drivers I need. The ones mention in Toastcfh's guide is for the EVO, not the Desire.
edit 2:
I got the Android SDK with adb and made progress, but still stumped.
I connect the Desire to the PC and with the Desire in recovery mode with ClockworkMod I run adb with:
Code:
adb shell
# mount /system
# exit
adb push hosts /system/etc
adb reboot
Following the example from here but it's a different device and dunno what to put for the first argument in '# mount /dev/block/mtdblock4 /system'. Any help at all would be much appreciated.

The symlink option in adfree should work for S-on devices.
If it doesn't try this:
Code:
adb remount
adb push hosts /system/etc
adb reboot
If that doesn't work flash this.

[GUIDE][30/06/2011]Root AND Downgrade Desire Z/G2(S-OFF/ClockWorkMod) -No Gingerbread

This guide is now obsolete. Please use this guide instead.
For Gingerbread Phones, Please use this guide.
Hey guys, this is probably the easiest guide to follow for rooting a branded desire Z. The reason why this can sometimes be hard is cause it uses a unique identifier (INFOCID) and the companies that brand the phones ONLY want roms from their company on them. This stops us from using a WWE rom like every else to downgrade and then root.
But ultimately, the reason I'm making this is because every other guide I've read constantly links you to other guides or other pages and it sorta annoyed me. So after I figured it all out I posted one concise guide that doesn't redirect you 50 times.
Now I’m gonna run you through EVERYTHING so you won’t get stuck anywhere.
This guide will work with:
Device: Desire Z or G2
Firmware Version: Any Firmware version will be fine (All you need to do is downgrade using step 1)
Android Version: Froyo or any previous variation of Android (Absolutely no gingerbread device will root with this method)
Btw, I take no responsibility for any damage taken by using these procedures. Sorry =P
Also if you don't have ADB and Fastboot set up then go ahead and follow the guides on the first two posts here. -Thanks nephron
g4b4g3 said:
If your INFOCID is NOT one of these you need to make a goldcard to downgrade!
HTC__001
HTC__032
HTC__E11
HTC__203
HTC__Y13
HTC__102
HTC__405
HTC__304
HTC__A07
HTC__N34
HTC__J15
Which can be checked by typing the following two commands:
adb reboot bootloader
fastboot oem boot
Click to expand...
Click to collapse
If your CID matches one of the CID's above then you can skip Step 1.
1. Creating a Goldcard:
Prerequisites:
ADB Set up and running fine (to check if it is working just connect your phone and have USB debugging enabled. Then type adb devices in your CMD Prompt)
HxD Hex Editor (see attachments of post 1)
USB Debugging enabled on your phone
1.Firstly we need to mount the memory card on a windows PC.
2. Format the memory card as FAT32 using all the default options.
3. Mount the memory card on your Phone. Then give it a couple of seconds.
4. Remount the memory card on your PC.
5. Find your CID by using the follow command in your cmd prompt (YOU NEED ADB)
Code:
adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid
6. Use the excel sheet provided to reverse the CID (see Attachments)
7. Goto this website and send yourself a goldcard.img
http://psas.revskills.de/?q=goldcard
8. Run HxD hex editor AS AN ADMINISTRATOR! (I can’t stress how important having admin rights is)
9. Go to Extras > Open Disk Image. Then select your goldcard.img
10. Go to Extras > Open Disk. IMPORTANT: Select your memory card UNDER the Physical Drives category. DO NOT open the logical drive.
11. Switch to your goldcard.img tab. Go to Edit > Select All. Then Edit > Copy.
12. Go to the physical drive tab and select the lines 00000000 until you get to the one with 00000170.
13. Go To Edit > Paste Write.
14. You should have a huge block of red characters now. This is good btw.
15. Mount your SD card on your Phone and let it detect it. If it comes up with a corrupt SD card error you have done it wrong and you may have to start over.
16. You are done with the goldcard.
2. Downgrading and Debranding
Before you start this please do the following:
1a. Download the RUU I’ve linked (it should be a ~300mb exe file) -Thanks g4rb4g3
ii. If you are a BELL User. Please download this RUU instead.
1b. Run the setup until you get to the screen with the tick boxes (Some Users may have to run this as an Administrator)
1c. Leave the setup running and go to C:\Users\<your account name>\AppData\local\temp ( Or Try %AppData%\Local\Temp\ ). Then right click and Sort By Date Modified. Look for the most recently created folder which should look like {xxxxxxx-xxxxxx-xxxxxxxx}. Then navigate into it and its then into its one folder. Look for rom.zip and copy that to your goldcard/memory card.
1d. Rename the rom.zip on your memory card to PC10IMG.zip (Make sure it is exactly the same as the way I've typed it there)
1e. Mount your sd card back onto your phone.
2. Download the attachments (misc_version & psneuters) and extract them in a folder like C:\RootVision\
Now you are ready to begin:
1. Open a CMD prompt window
2. Navigate your way to the folder with psneuter & misc_version IN CMD PROMPT. (So the cmd prompt window should be something like this C:\RootVision> )
3. Now we will use the following 5 commands one after the other
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
4. After the last command you should have a # and a flashing line for you to enter text. This is good. (If you get a $ you have done it wrong and should try typing the commands out again)
5. Now you have the # type the following command in: (This will spoof the radio version)
Code:
/data/local/tmp/misc_version –s 1.33.405.5
Then go ahead and type:
Code:
exit
6. Type this command into your cmd prompt (btw you should be back with the normal C:\RootVision>)
Code:
adb reboot bootloader
7. Once on your white screen with colourful text you can go ahead and press the power button ONCE
8. Now just wait for the rom to install and verify. If you get INCORRECT CID your gold card doesn’t work or your CID doesn't match and you'll need a goldcard. (Go to Step 1. and make a goldcard for your phone)
9. Go ahead and install the rom when it asks you.
10. You are done downgrading and can now begin the Rooting process.
See Post 2 For Rooting

Assuming all as gone well and you now have a rom without superuser but you have a baseband version that is 1.34xxxx.
Alright, let’s begin.
Prerequisites:
Download psneuter
Download gfree 0.5
Download root_psn
Download flash_image
Download the Desire Z hboot
Download Clockwork Recovery
ALL of these are in the attachments section
They all should be extracted into the same folder. Use something simple like C:\RootVision\Root
3. Root your Desire Z!
Before you start:
Enable USB Debugging and Allow Unknown Market Installations again.
Also delete the PC10IMG.zip on your phone if you downgraded.
Okay lets go:
1. Now Assuming you succeeded at the last part you should have a stock-ish rom without superuser. What we want to do is start by pushing all the files across with the following adb commands (use in cmd prompt the same way you pushed files in 2.)
Code:
adb push psneuter /data/local/tmp/
adb push gfree /data/local/tmp/
adb push busybox /data/local/tmp/
adb push root_psn /data/local/tmp/
adb push flash_image /data/local/tmp/
adb push su /sdcard/
adb push hboot-eng.img /data/local/tmp/
adb push Superuser.apk /sdcard/
adb shell chmod 755 /data/local/tmp/*
2. Alright now we have all the files we need to root the phone. Input the following command. This is just putting our clockwork recovery in a convenient place with an easy name.
Code:
adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
3. Now we’re gonna temp root again by typing in the following:
Code:
adb shell /data/local/tmp/psneuter
adb shell
4. This should leave us with another #. Now enter the following commands:
Code:
cd /data/local/tmp
./gfree -f -b hboot-eng.img
./flash_image recovery recovery.img
./root_psn
sync
5. Type in: (thanks for the correction john_d1974)
Code:
reboot
6. You should have a rooted phone with superuser after the reboot. Also it will have clockworkmod, SuperCID, secu-flag off & an Unlocked HBOOT-ENG.
If gfree 0.5 doesnt work for you then this section is for you:
Prerequisites:
Download psneuter
Download gfree 0.2
Download root_psn
Download flash_image
Download the Desire Z hboot
Download Clockwork Recovery
ALL of these are in the attachments section
They all should be extracted into the same folder. Use something simple like C:\RootVision\Root
1. Now Assuming you succeeded at the last part you should have a stock-ish rom without superuser. What we want to do is start by pushing all the files across with the following adb commands (use in cmd prompt the same way you pushed files in 2.)
Code:
adb push psneuter /data/local/tmp/
adb push gfree /data/local/tmp/
adb push busybox /data/local/tmp/
adb push root_psn /data/local/tmp/
adb push flash_image /data/local/tmp/
adb push su /sdcard/
adb push hboot-eng.img /data/local/tmp/
adb push Superuser.apk /sdcard/
adb shell chmod 755 /data/local/tmp/*
2. Alright now we have all the files we need to root the phone. Input the following command. This is just putting our clockwork recovery in a convenient place with an easy name.
Code:
adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
3. Now we’re gonna temp root again by typing in the following:
Code:
adb shell /data/local/tmp/psneuter
adb shell
4. This should leave us with another #. Now enter the following commands:
Code:
cd /data/local/tmp
./gfree -f
./flash_image recovery recovery.img
./root_psn
sync
5. Type in: (thanks for the correction john_d1974)
Code:
reboot
6. You should have a rooted phone with superuser after the reboot. Also it will have clockworkmod, SuperCID and secu-flag off.
4. Installing your own custom ROM
This section is just in case you don't know how to install a custom ROM.
Note: Always make sure the ROM you are installing is FOR YOUR PHONE! If you install a ROM meant for another phone you could potentially damage it or brick the phone itself.
1. Download the ROM you want and copy it to your SD Card. (Try to keep it in a folder that is easy to get to)
2. Turn off your phone.
3. Hold down the volume down button and then press the Power Button. This should take you to a white screen with lots of colourful text. One of which says FASTBOOT or FASTBOOT_USB.
4. Press the power button ONCE when BOOTLOADER is selected(BLUE)
5. Navigate using the volume buttons until you get to RECOVERY and then press the Power Button again.
6. The HTC Logo will come up then you will get a black screen with text.
7. From here you should Always do a NANDROID Backup so you can restore a working ROM if something fails.
NANDROID Backup
7a. Navigate to 'backup and restore' and then select it by pressing the trackpad button.
7b. Select 'Backup' and then let it finish. Once done you have a backup of your android.
8. Now you want to do these before you start installing:
a. 'wipe data/factory reset
b. 'wipe cache partition'
c. Go into 'advanced' and select 'Wipe Dalvik Cache'
9. Now you can install the ROM itself. This is done by selecting 'install zip from sdcard' in the main menu. Now you can select 'choose zip from sdcard' and just go ahead and select the ROM you copid to your sd card earlier.
9a. If the phone says verification failed then just toggle the signature verification option.
FAQ - For Anyone with any issues.
1. My version is 1.7xxxx or higher. Can I use this method?
Yes you can. This method will downgrade your phone to 1.34 so your radio is no longer locked thereby allowing you remove the secu-flag, add superCID and allow you to install a custom recovery (like ClockWorkMod)
2. My CID is XXXXXXXX and isn't on that list, will this method still work?
Yes it will. The reason why it will work is because a goldcard is essentially a manufacturers way of bypassing the CID checks used by ROMs. Therefore, by creating our own unique goldcards we can also bypass the CID check.
3. My CID is on the list that you mentioned. Do I need this goldcard?
No, you can skip the 1st step because when the ROM checks your phones CID it will match up perfectly and the phone will install the older radio without issue.
4. What Benefits does rooting a phone grant you?
Simply, it allows you to install any ROM of your choosing onto the phone as well as use custom kernels and certain applications that access locked functions on the phone. This can ultimately lead to; a longer battery life; more stable roms and more frequently updated roms; and finally an overall faster Android experience.
5. What is root access?
Root access essentially gives you access anything locked by the manufacturer on the phone. This most importantly means that you can read and write to any system partitions on the phone that would normally be locked.
6. Whats psneuter?
psneuter is an application used to grant temporary root access. This is done through an exploit in the android system and will give us a window to further exploit the system and ultimately grant us Permanent Root Access.
7. How do I find my CID?
To find your CID you run two commands. Firstly, in your CMD prompt you type 'adb reboot bootloader' when your phone is connected and USB debugging is active. This will restart your phone into its bootloader. Then once you see the words FASTBOOT_USB you type 'fastboot oem boot'. Then look for the words CID and then just read the 8 character CID.
Also there is a post with a screenshot here.
8. My phone will not find PC10IMG.zip
You will need to double check that the PC10IMG.zip is the correct ZIP file from the RUU that has been linked. It should be roughly 250mb in size and should be placed in the root folder of your SD Card. Also your SD Card must be compatible with your device (able to be read/written to). If you cannot access your SD Card from your Desire Z or G2 then there is probably something wrong with your SD Card. It should probably be reformatted.
9. Can I use this on the Desire Z/G2 running Gingerbread?
So far no one has been able to root the gingerbread version of android on the Desire Z/G2. Unfortunately, this guide still cannot root gingerbread desire Zs or G2s.
If there are any more, feel free to post them and I'll add them
10.I'm Missing my AdbWinApi.dll? What now?
espentan[U said:
][/U]
I don't know if you've figured this one out yet, but here's the solution to a potential cause.
You need to add the directory containing the "AdbWinApi.dll" to Windows' path under Environment Variables, so Windows know where to look for the necessary files when you enter commands in the shell.
For this exercise I'm going to assume that you have installed the Android SDK in the directory called "android-sdk-windows" on your C: hard drive. If you have it installed somewhere else, change the path I'm mentioning below accordingly.
Go to the Windows "Control Panel".
Click on "System and Security".
Click on "System".
Click on "Advanced system settings" in the left column of the window you're in.
Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "System variables" box until you find "Path".
Select "Path" and click the "Edit" button.
At the very beginning of the input field called "Variable value" enter the following:
"C:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Now the windows command shell knows where to find the necessary DLL's and whatnot.
Click to expand...
Click to collapse

will this work if i have 1.84.666.2?

anyone? thought?

Should work fine as long as you've got a Desire Z or G2 lol.

hi, manageage to root the DZ sucessfully, however on step 5 you say
"5. Type in:
Code:
Reboot"
i got an Reboot: error not found
i retried with with "reboot" and was sucessful

Hi, im sure this has been covered before in other posts, but, could someone tell me, if i were to use the above method to downgrade and root etc, would this prevent me from doing an official upgrade, to, say gingerbread in the near future? Also is there any real benefits to going to gingerbread? I ask as im sure ive read somewhere its only possible to flash to cooked roms, not official ones (once downgraded and rooted etc).. this would concern me as ive moved over from win mo to android, and in my experiance, EVERY cooked unoficial rom i ever flashed (xperia x1) was simply rubbish, and i tried alot of them. (Even though people would say the roms would be fine, bugs smoothed out etc), i went back to stock in the end after constant dissapointment.
Sorry for the rant, just need to know where i stand.. thanks people..

jmpcrx said:
Hi, im sure this has been covered before in other posts, but, could someone tell me, if i were to use the above method to downgrade and root etc, would this prevent me from doing an official upgrade, to, say gingerbread in the near future? Also is there any real benefits to going to gingerbread? I ask as im sure ive read somewhere its only possible to flash to cooked roms, not official ones (once downgraded and rooted etc).. this would concern me as ive moved over from win mo to android, and in my experiance, EVERY cooked unoficial rom i ever flashed (xperia x1) was simply rubbish, and i tried alot of them. (Even though people would say the roms would be fine, bugs smoothed out etc), i went back to stock in the end after constant dissapointment.
Sorry for the rant, just need to know where i stand.. thanks people..
Click to expand...
Click to collapse
It is pretty difficult to go back to stock updates from your carrier for example Vodafone. This is because of the unique CIDs used and the fact that it is extremely hard to find a stock ROM since no one can give you a NANDROID backup.
Anyways, there are numerous benefits to rooting your phone included with most ROMs. These benefits include longer battery life, faster ROMs & various other things depending on each chef.

Ok, thanks, but are the roms buggy at all, will some of the hardware not work properly, or will i have freezing probs etc, as i found this always to be the case with win mo roms?.. have you personally found a rom that works perfectly that includes htc sense? As i do like the UI..
My goal is to have all security off, full perm root, with a perfecly working sense rom that i can then overclock to a speed that works well with my particular phone, and to underclock when idle etc..
Thanks..

I need to verify that my Tmobile G2's INFOCID is compatible.
I typed in the two commands:
adb reboot bootloader
fastboot oem boot
The first one worked. The second command is not recognized once I'm in the bootloader. Can someone suggest a solution?

Newbie question,
how to unroot if i rooting the phone using this metode?
and how to go back to original rom?

Vader™ said:
Newbie question,
how to unroot if i rooting the phone using this metode?
and how to go back to original rom?
Click to expand...
Click to collapse
Firstly, to root the phone just follow the steps and once you've finished them all you will be done.
Second, it should technically be possible once you've rooted the phone to simply do a NANDROID backup via ClockWorkMod Recovery before you start flashing new ROMs. If you have backed it up and later decide you want to unroot then all you would need to do from there is restore your nandroid backup and unroot the phone through this method.
forceOnature said:
I need to verify that my Tmobile G2's INFOCID is compatible.
I typed in the two commands:
adb reboot bootloader
fastboot oem boot
The first one worked. The second command is not recognized once I'm in the bootloader. Can someone suggest a solution?
Click to expand...
Click to collapse
Using this method you don't have to worry about your CID. If you make a goldcard it will completely bypass the need for one of the CID's listed in the first post. So to put it simply, you don't need to worry about your unique CID if you create and use a goldcard to downgrade.

Aegishua said:
It should technically be possible once you've rooted the phone to simply do a NANDROID backup via ClockWorkMod Recovery before you start flashing new ROMs. If you have backed it up and later decide you want to unroot then all you would need to do from there is restore your nandroid backup and unroot the phone through this method.
Click to expand...
Click to collapse
okay, but we need to root the device first right? before ClockWorkMod Recovery can run, the problem is, if I root the device first, the device must be downgrade to build 1.34.405.5, and now my Desire Z using build 1.82.xxx.x
is it if we backup via ClockWorkMod, the ROM that we backup is 1.34.405.5? not my current build?
please help bro, really confused here

Hi forceonature, im no expert, but when i was having a look myself, i found out it was simply my enviroment variables wernt set up for the directory fastboot was located.. an easy way round this was just to enter the directory fastboot was in (program files, 'some directory'.. do a quick search) within your command prompt, and type the second command from there.. hope that helps..

Everything goes fine until
mmap() failed. Operation not permitted
when I put in
adb shell /data/local/tmp/psneuter
Any help?

Also I can only put su and Superuser.apk on my sdcard if I manually transfer them.

Hi forceonature, im no expert, but when i was having a look myself, i found out it was simply my enviroment variables wernt set up for the directory fastboot was located.. an easy way round this was just to enter the directory fastboot was in (program files, 'some directory'.. do a quick search) within your command prompt, and type the second command from there.. hope that helps..
Click to expand...
Click to collapse
I need to verify that my Tmobile G2's INFOCID is compatible.
I typed in the two commands:
adb reboot bootloader
fastboot oem boot
The first one worked. The second command is not recognized once I'm in the bootloader. Can someone suggest a solution?
Click to expand...
Click to collapse
I tried the same thing to get my DZ phones CID and the first one worked and the second didn't. If I don't have to make a gold card all the better. How can I find out for sure if my CID is on the list or not? Also if I have to make a gold card do I need to have a micro SD card to make the gold card?
Thanks,
Chevy

chevy2410 said:
I tried the same thing to get my DZ phones CID and the first one worked and the second didn't. If I don't have to make a gold card all the better. How can I find out for sure if my CID is on the list or not? Also if I have to make a gold card do I need to have a micro SD card to make the gold card?
Thanks,
Chevy
Click to expand...
Click to collapse
You should get a line that says INFOt.cid=XXXXXXXX or any of the lines that say your 8 Digit CID. However, as you can see there are multiple lines that say it and they should all be the same.
If your CID does match one on that list then you will not need a goldcard.
I've attached a screenshot to make things easier.
forceOnature said:
okay, but we need to root the device first right? before ClockWorkMod Recovery can run, the problem is, if I root the device first, the device must be downgrade to build 1.34.405.5, and now my Desire Z using build 1.82.xxx.x
is it if we backup via ClockWorkMod, the ROM that we backup is 1.34.405.5? not my current build?
please help bro, really confused here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Yeah, you can only have a NANDroid backup of 1.34.xxx because there is no way to get clockwork onto a 1.72+ rom.

Hi, I'm new to rooting the G2. Iv'e been trying to follow this tutorial, but I'm having some trouble. After renaming Rom.zip to PC10IMG.zip I booted into the bootloader and it says 'no image found' or something like that. What am I doing wrong? Am I not supposed to put the zip file on the root of the SD card? Is it possible to just use the RUU to downgrade?
And regarding the downgrade, the build number on my G2 shows 1.22 . Isn't that lower than 1.34?
Any help is appreciated!

I followed the instructions twice and both times I get to
"/data/local/tmp/misc_version –s 1.33.405.5"
I get
/
Patching and backing up partition 17
Error opening backup file.
#
The first time around I iqnored it and went through hboot, the rom PC10IMG.zip was checked and verified and finally failed prompting "the main version is older"
what am I missing?
EDIT: checked SD card, unmount and remounted phone/sdcard no avail.
Will try 1.33 Bell rom next.
EDIT2: Patching and backing up sucessful, problem was I couldn't get my phone to stay in debugged mode without being in DISK DRIVE, had to start HTC Sync to mount the phone in that way to relieve the sd card, allowing adb to patch the file. Now running through PC10IMG.zip with fingers crossed.
EDIT3: Everything went smooth after that! Thanks. Now I will attempt to update to 2.3 and Sense 3.0
EDIT4: Now running on 2.3.3 and Sense 3.0 Virtuous port. Testing...probably going back to more stable gingerbread and sense 2.1

USB dead?

Hello,
i've a little problem with my Desire (GSM):
I flashed a RUU and now the usb share is dead; I can't even root it per unrevoked.
So i tried to replace mtd0.img (with rageagainstthecage; found it somewhere in the net), but no chance; don't work.
What can I do? I just replaced my broken display for 100€ and now i can dump it without root/usb!?

Well you just flash the mtd0.img, you only need to do it the right way.
Were you able to gain root access using rageagainstthecage? If yes you just need to transfer the mtd0.img and flashimage executable file to the phone in order to flash the fixed misc partition.
Also you might want to try booting in fastboot and run "fastboot oem enableqxdm 0" to enable sd-card.

I tried this:
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/shared_prefs/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/shared_prefs/mtd0.img
cd /data/data/jackpal.androidterm/shared_prefs/
chmod 755 rageagainstthecage-arm5.bin
chmod 755 flash_image
http://www.android-hilfe.de/root-ha...usb-brick-ohne-root-reparieren-geht-auch.html
fastboot oem enableqxdm 0 doesn't work neither

you cant edit your misc partition (the one with mtd0) if you dont have root
since you cant run unrevoked, only option you have is visionary+
now i dont know how visionary+ works i only remember someone in the same situation as yours (S-ON and USB-Bricked) and he claimed to fixed it by applying visionary+ then flashing mtd0 (of course you must do 'su' command first in terminal emulator to gain root rights)
apparently in order to gain root (temporarly) with visionary+ you just need to put some files @ SD card and execute them, then go with 'su' and flash mtd0

Well year you might be able to use visionary+ as well to gain temporary root, however rageagainstthecage should do the same thing.
After doing the commands you mention, you should have the files in place so that you can run the rage against the cage:
"/data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin"
And you should have su rights(temporarily) So you can run:
"cd /data/data/jackpal.androidterm/shared_prefs"
"./flash_image misc mtd0.img"
But Just follow the guide from where you got to. And if you can't get root using rageagainstthecage you can try visionary.

i was usb bricked my desire few days ago and when tried to unroot via pb99img.update from hboot. i got stuck on stock froyo 2.2(s-on) with out any usb function and sdcard.then i did the steps below and successfully fix the usb brick.
after i unlocked my sd card via fastboot command"fastboot oem enableqxdm 0" sd card recognized by phone and i can browse it via file explorer.
note-you can access your sdcard only via file explorer nothing else so after execute the command download a file explorer from android market.
then i copied the visionary+(it gave me temporary root access which is needed to work this whole thing out).
root explorer,terminal emulator apk and those usb bricked update file(image_flash,mtd0.img) to sdcard from pc via card reader and installed them.
before copy those update file on sd card i edited the mtd0.img to put correct cid n rom info via hex editor.
after that i copied those update file in phone memory
/data/data/ and set permission for r/w and execute via root explorer.
after that i simply typed this command in terminal emulator
"su
/data/data/flash_image misc /data/data/mtd0.img"
Rebooted my phone and voila usb brick is gone htc sync,usb tethering,sd card mount,charge everything is working and now i am rooted and s-off again
Note-you don't need the rageagainstthecage file which only need if you try to get root access via terminal emulator which is lengthy n complicated but with visionary+ you can get root access with 1 click and it's much easier than typing command in T.E.

Thank you; now USB Share works, but I can't use unrevoked or AlphaRev X cause they can't find my Desire (USB Debugging is on). I even cannot flash a RUU, since it abort with an error message saying, there's an usb error?

Anyone who can help me?

Disciplin said:
Thank you; now USB Share works, but I can't use unrevoked or AlphaRev X cause they can't find my Desire (USB Debugging is on). I even cannot flash a RUU, since it abort with an error message saying, there's an usb error?
Click to expand...
Click to collapse
Have you uninstalled HTC Sync ?

Never installed, only android sdk

can not mount system in read-write mode using adb without recovery mode

I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.

maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop

ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:

THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.

error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?

jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?

i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help

ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help

dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]