Database Users

Droid X Rooting problems after updating to official 2.2

I ran the rage exploit and afterwards, i can't get into adb shell. Gives me an error, device is not connected, but adb says it is

To further clarifiy, we were running the Sebastian Krahmer root process using the rageagainstthecage-arm5.bin. After running the rage step, we ran into trouble because the device no longer connected.

darkonion said:
To further clarifiy, we were running the Sebastian Krahmer root process using the rageagainstthecage-arm5.bin. After running the rage step, we ran into trouble because the device no longer connected.
Click to expand...
Click to collapse
same thing happened to me. however, i restarted the phone and the computer, and then adb would see the device again. i didn't get the # prompt, so i had to run ./rage... again. surprisingly, the second time it worked like a charm.

did you do kill-server?

had the same issue and can confirm the second time around worked no issues

mortodestructo said:
same thing happened to me. however, i restarted the phone and the computer, and then adb would see the device again. i didn't get the # prompt, so i had to run ./rage... again. surprisingly, the second time it worked like a charm.
Click to expand...
Click to collapse
I had a similar experience, however, part of it has to do with having the proper USB drivers and then to that same end, once it does it's first go round, there is a point where you truly have to wait for the phone to show back up in the taskbar before proceeding - otherwise, the next time you are attempting to do the "adb devices" it doesn't recognize that there's a phone there...it's all a matter of waiting for the USB driver to bring the phone back "into existence" from there, you are well on your way to the # prompt. (Trust me on this, I'm a total NOOB and just did this for the first time using the step-by-step method. I was scared as s**t with each command I typed but I was determined to go on...once I saw the #, I knew I was out of the woods..

Stuck big time!!
I'm stuck. I can't get PC Mode to show up with debugging icon (even though debugging icon shows up in all other modes) yet adb devices shows my device correctly, and I can adb shell to it fine and end up with unrooted on 2.2 froyo at the $ after I updated to OTA 2.2 from rooted 2.1
so I follow the guide to the T but as you can see this is my results and I have not yet been able to fix the issue.
$ pwd
pwd
/data/local/tmp
$ chmod 0755 rageagainstthecage-arm5.bin
chmod 0755 rageagainstthecage-arm5.bin
Unable to chmod rageagainstthecage-arm5.bin: Operation not permitted
Click to expand...
Click to collapse
I have no idea how to fix this issue, I've rooted before on the leaked 2.2 without any problems both via the long adb method and via the easyroot method before OTA was released.
I tried the one click method and it hangs in the .bat and tries to pkil the process but there is no process to kill since the chmod 0755 rageagainstthecage-arm5.bin didn't work and thus it can't load ./rageagainstthecage-arm5.bin
%!~#$%~ Any help to get past this would be greatly appreciated! I would already have downgraded to 2.1 if I knew it was safe, but I'm seeing it bricks droid X staying at M logo on the forums if tried and thus we need a new sbf for 2.2 to be leaked.
EDIT: I've also tried via the Charge Only mode with debugging on as recommended by some people on the forums for other people stuck... I still end up with the same results using that mode. :/
EDIT 2: Looked up my default.prop and saw this:
$ more default.prop
more default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
Click to expand...
Click to collapse
and what it needs to be is:
$ more default.prop
more default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
Click to expand...
Click to collapse
Unfortunately I don't have a way of changing it. Already tried copying modifed to sdcard and then using adb to copy it over... unfortunately don't have the permissions!
$ cp /sdcard/default.prop /default.prop
cp /sdcard/default.prop /default.prop
cp: /default.prop: Read-only file system
Click to expand...
Click to collapse

what about benchmark test with the froyo update,how much it scores?

Steebs77 said:
I'm stuck. I can't get PC Mode to show up with debugging icon (even though debugging icon shows up in all other modes) yet adb devices shows my device correctly, and I can adb shell to it fine and end up with unrooted on 2.2 froyo at the $ after I updated to OTA 2.2 from rooted 2.1
so I follow the guide to the T but as you can see this is my results and I have not yet been able to fix the issue.
I have no idea how to fix this issue, I've rooted before on the leaked 2.2 without any problems both via the long adb method and via the easyroot method before OTA was released.
I tried the one click method and it hangs in the .bat and tries to pkil the process but there is no process to kill since the chmod 0755 rageagainstthecage-arm5.bin didn't work and thus it can't load ./rageagainstthecage-arm5.bin
%!~#$%~ Any help to get past this would be greatly appreciated! I would already have downgraded to 2.1 if I knew it was safe, but I'm seeing it bricks droid X staying at M logo on the forums if tried and thus we need a new sbf for 2.2 to be leaked.
EDIT: I've also tried via the Charge Only mode with debugging on as recommended by some people on the forums for other people stuck... I still end up with the same results using that mode. :/
EDIT 2: Looked up my default.prop and saw this:
and what it needs to be is:
Unfortunately I don't have a way of changing it. Already tried copying modifed to sdcard and then using adb to copy it over... unfortunately don't have the permissions!
Click to expand...
Click to collapse
Have you tried rebooting your phone?
How about this, go check out the original 25 step process to root the Droid 2. Instead of pushing rageagainstthecage-arm5.bin, rename it to something else and then run the exploit. Of course after making changes to the commands else where.

My build.prop doesn't have either of those properties. That makes me wonder what you did that changed your build prop if you have no root.
You should have been upgrading from vanilla 2.1 to avoid problems.

android_master said:
what about benchmark test with the froyo update,how much it scores?
Click to expand...
Click to collapse
I got a quadrant score of 1375
Sent from my DROIDX using XDA App

I have a problem that my computer does not reconize adb after i download and extract all the zips files. it gives me adb not reconized as a command

Uilliam said:
I have a problem that my computer does not reconize adb after i download and extract all the zips files. it gives me adb not reconized as a command
Click to expand...
Click to collapse
ADB is an "external" command... i.e. its not native to windows. So you need to either be in, and stay in, the folder/directory where ADB.EXE resides to execute it, OR add that folder to the Windows PATH variable so windows knows where to find it to execute it.
and this was part of Brian's problem (in the OP) after talking with him via Gtalk.
if you want to add it to the path, then you need to do the following...
First you need to know the exact location of your ADB.EXE (for example: c:\android-sdk-windows\tools or c:\sdk\tools or ???)
he had Win7 but the steps are very similar in XP AFTER you know the folder/directory where ADB.EXE is. (tip, you can use Windows Search to find it, when found right click and select properties. On the general tab it will have the location).
Find where your ADB.EXE actually is. You need that for the following steps. Since I don't know where you unzipped to, lets say for the purpose of these steps, your ADB.EXE is located in C:\android-sdk-windows\tools
In windows, right click computer... select properties...
click advanced system settings (from along the left)
click the environment variables button
from system variables at the bottom.. scroll down and highlight path
click the edit button
use the right arrow key on your keyboard to get to the end of the line (it should unselect everything, and still keep the text there..)
on the end of that line...
type the following....
;c:\android-sdk-windows\tools
(yes, you need the semi!! and that line should be exactly where your ADB.EXE really is... remember I'm only using c:\android-sdk-windows\tools as my example!!!)
click OK
and ok
after doing that, when you are at a command prompt, no matter what folder/directory you are in, if you type ADB it should recognize it and run it.

G2 Rooting Problem

Hey all,
I would like to know, what I might have done wrong in the rooting process. I used
This Tutorial hxxp://g2hacks.com/g2-hacks/how-to-root-g2-phone/
I made it to step #18 and was stopped by this error:
Code:
/data/local/tmp/root: data/local/tmp/busybox: not found
/data/local/tmp/root: data/local/tmp/busybox: not found
Unable to chmod /system/xbin/busybox: No such file or directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Ideas?
Thanks,
Danny

Here is a screenshot of what I pushed to the phone:
hxxp://i.imgur.com/No1id.jpg

You have a typo in your push command for busybox (you renamed it to root instead, which then got overwritten when you pushed root). Just push busybox again.

How do I back out and enter that push command again?
What would I type?
I'm a total novice.

On your comp, just type the command again:
Code:
adb push G2TempRoot/busybox /data/local/tmp/busybox
Then on your phone, in Terminal, just run the root command again:
Code:
/data/local/tmp/root
It should complete this time.

I made a mess. Check it:
hxxp://i.imgur.com/y3NRW.jpg

You are still in the adb shell (basically creates a terminal on your phone that you can interact with on your computer).
Type "exit" to leave the shell. This will return you to the regular command prompt (instead of the $). Then try the push command again.

So now the phone terminal gives me this:
Code:
/data/local/tmp/busybox: permission denied

Oh sorry, forgot you needed to set permissions on the file. Run this command again from your computer:
Code:
adb shell chmod 0755 /data/local/tmp/*
Then it should all work fine.

The errors are getting shorter
Now I get this:
Code:
mkdir failed for /system/xbin, File exists

This error doesn't matter (it's really more of a warning in this case) and is actually expected.
You should actually be rooted if you didn't see anything else.

AND I'M ROOTED... THANK YOU!
I'm new to Android from iOS. Any ROMS you would recommend?

Danny.B said:
AND I'M ROOTED... THANK YOU!
I'm new to Android from iOS. Any ROMS you would recommend?
Click to expand...
Click to collapse
Congrats! And there are a few threads about this that you can read through (just search for them). If you like HTC Sense (the interface HTC adds to a lot of their phones---basically lots nice visuals and extra polish to things), you can try Virtuous. If you like the stock look that the G2 comes with, there is a stock DEODEX rom out there. By de-odexing the rom, you can do things like customize the framework (e.g., customize the status bar icons/colors or add a battery percentage to it). Lots of people here (myself included), use CyanogenMod. It's close to stock but with lots of tweaks/extras (it's based on the Android Open Source Project or AOSP). It's also nice because it has frequent updates and constant development (they recently started pushing test builds that are based on Gingerbread---the new Android update only available on Nexus S).
Now that you are rooted though, it's easy enough to install Rom Manager and test them all out. Be sure to create a backup first as well.

ROM Manager installed. I'm backed up.
Thanks again for your help.

i cant flash the engineering hboot keep getting error md5sum : not found Verification of hboot-eng.img failed i re-download the files, re-extracted them to my SD card, and ran the flash_hboot script 3x still nothing plz help but im rooted and backed up

Did not want to create a new thread so I'm posting it here.
First off, I haven't tried rooting any of my phones previously so I'm obviously making a mistake somewhere.Hope someone here can help me out.
I installed visionary+ r14 but it just blacked out the screen with a heading.I've read elsewhere that it has all to do with the new firmware updates.My update for the DZ seems to be country a specific one and came out a couple of weeks back.
Anyway,
I tried this visionary method a few times but the phone just hung and I had to go to the homescreen and uninstall Visionary and reboot to get the phone to run smoothly again.
Then I read another way of rooting the thing and it took me here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
After a couple of tries I was able to push the files to the DZ but got stuck at this command:
adb shell chmod 0755 /data/local/tmp/*
The error it gives me is:
Unable to chmod /data/local/tmp/sqlite3: operation not permitted
Strange thing is, yesterday at the same point it gave me the same error but it was 'busybox' instead of sqlite3 and right before that it was something else.Which should mean that those earlier commands were run successfully by the terminal.
P.S. Debugging mode is on.Visionary is uninstalled. followed all the steps mentioned in the guide.

Okay.So I format the phone memory and I'm now able to move a few steps ahead.
But as soon as it seems that everything is going well, the terminal emulator refuses to open at this step:
"Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell "
waited a while and there is only a blank screen showing up.

mohitanfield said:
Okay.So I format the phone memory and I'm now able to move a few steps ahead.
But as soon as it seems that everything is going well, the terminal emulator refuses to open at this step:
"Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell "
waited a while and there is only a blank screen showing up.
Click to expand...
Click to collapse
It looks like you are trying to root a DZ with a firmeware version >= 1.72.
If yes to have to downgrade it to 1.34 first.
See either the instructions here: http://forum.xda-developers.com/showthread.php?t=905261 or the more comprehensive at http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_Z:_Rooting
But if your CID is other then the ones stated in the the first thread you need a goldcard to downgrade first, which is also described in the first thread.
have fun - Guhl

Thanks a lot for your reply and as is the case, my phones CID is HTC_38 which does not seem to be downgradable without a gold card.
I read the procedure and although its well explained, it will take a bit of time.
Will try it sometime soon hopefully, although I wish someone would just make a simple rooting app for the newer versions!

It took us month without sleep to create the existing rooting tools. So I do not see any simple rooting tools on the horizon

[GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo

[GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo
This guide is written for anyone who has "Stock Gingerbread" and wants to downgrade their phone which originally had "Stock Froyo". The following is a list of phone models this guide is intended for and that are known to work:
Working Phone Models:
G2 (Vision)
Desire Z (Vision)
myTouch 4G (Glacier)
Desire HD (Ace)
It should also be noted, this guide WILL NOT work with the following:
myTouch 4G Slide (Doubleshot)
Desire HD (Ace) w/ Sense 3.x (a recent OTA update as patched this method).*
*See these threads for a fix for the Desire HD (Ace) w/ Sense 3.x:
[GUIDE] Downgrade from 3.13 (Sense 3.0) roms
Temp root on Desire HD (Ace) with Sense 3.x
Special Notes
If you have used HTCDEV unlock your phone, please visit the following guide prior to using this guide, otherwise you will not be able to downgrade.
[GUIDE] How to get root/flash custom roms with HTCDEV unlock written by Nipqer
strawmetal has been kind enough to make an amazing PDF for each of the various phone models this guide supports which may be easier to read and follow for some users. I highly recommend taking a look at these files, especially if you are finding yourself a little confused during this guide (as this guide is written for multiple devices though he has PDFs for each device individually).
STRAWMETAL's Downgrade From Gingerbread to Froyo Guides and Tools
HTC Desire Z-G2 Downgrade & Root *Recently Updated*
Table of Contents
Introduction
Gaining Temp Root
Changing Version Number to Allow Downgrade and Gaining SuperCID with a Goldcard
Temp-Rooting to Backup (*Optional*)
Downgrading
Manual Downgrade
Fastboot Downgrade
Sources
Troubleshooting
Change Log
Attachments
I) Introduction
This guide is written with the assumption that the user has previously used "adb". If you are unfamiliar with "adb" or do not even know what "adb" is, download the Android SDK (found at http://developer.android.com/sdk/index.html). There are a couple guides to help you get started setting up the Android SDK and understanding ADB. If you have not installed the Android SDK or you are unfamiliar with ADB, please take some time and read a couple guides to get a basic understanding of it.
[GUIDE] ADB Workshop and Guide for everyone
[HOW-TO] ADB for Dummies(How-To Learner's Guide)
How To Set Up ADB/USB Drivers for Android Devices
I - 1) Gaining Temp Root
Download the attached files, unzip them, and place the files in your platform-tools folder. To elaborate, place the fre3vo file inside of the View attachment fre3vo.zip file in your platform-tools folder and the misc_version file inside the View attachment misc_version_01.zip file in your platform-tools folder.
Make sure you have your sdcard inserted in your phone, and you are NOT in USB Storage Mode, and your sdcard is NOT FULL.
Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
[B]> adb shell cat /dev/msm_rotator[/B]
[I]/dev/msm_rotator: invalid length[/I]
If you received the same message, you're good to continue on. If not… refer to the troubleshooting section of the guide before you continue.
Run the following commands from your platform-tools directory.
Code:
[B]> adb push fre3vo /data/local/tmp
> adb shell
$ chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF[/B]
After you enter that command, you should see something similar to the last few lines in the following displayed.
(It may take a minute or two. From what I can tell, this appears to be the quickest method as the exploit seems to be found in the latter regions.)
Code:
[I]Buffer offset: 00000000
Buffer size: 8192
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba90000...
Potential exploit area found at address fbb4d600:a00.
Exploiting device...[/I]
If the exploit works, you will be kicked out of ADB shell, proceed to Step #8.
If the above does not work, and fails, you can try the following, and hopefully one will work, try the following (you must reboot your phone before you try another set):
Code:
[B]$ /data/local/tmp/fre3vo -debug -start 10000000 -end 1FFFFFFF
$ /data/local/tmp/fre3vo -debug -start 20000000 -end 2FFFFFFF
$ /data/local/tmp/fre3vo -debug -start 30000000 -end 3FFFFFFF
$ /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF
$ /data/local/tmp/fre3vo -debug -start E0000000 -end EFFFFFFF[/B]
If you did get kicked out of adb shell, open it again. You should now see # instead of $, thus granting you temp root. Go ahead and exit out of shell to proceed to the next stage.
Code:
[B]> adb shell
# exit[/B]
I - 2) Changing Version Number to Allow Downgrade and Gaining SuperCID with a Goldcard
If you followed the first portion of this, you should of unzipped View attachment misc_version_01.zip ad View attachment flashgc.zip in the platform-tools directory.
If you haven't done that yet, do that now and then run the following commands from your platform-tools directory.
Code:
[B]> adb push misc_version /data/local/tmp/misc_version
> adb push flashgc /data/local/tmp/flashgc
> adb shell chmod 777 /data/local/tmp/*
> adb shell
# cd /data/local/tmp
# ./misc_version -s 1.00.000.0[/B]
[I]--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...[/I]
[B]# ./flashgc[/B]
*Note: If you get the following error, please make sure your sdcard is inserted in your phone and is NOT mounted to your computer (ie: make sure you are NOT in USB Storage Mode). This is a fairly common error and/or oversight many people tend to miss. Please double check this before continuing.
Code:
Error opening backup file.
Code:
[B]# sync[/B]
Double check and make sure everything looks good so far by running the following command (still in adb shell).
Code:
[B]# dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10[/B]
[I]1.00.000.010+0 records in
10+0 records out
10 bytes transferred in 0.001 secs (10000 bytes/sec)[/I]
BE SURE TO BACKUP ANY DATA!!!***
I - 3) Temp-Rooting to Backup
If you have nothing to back up or don't care to back anything up, proceed to the next section.
Credit goes to Nipqer from #g2root for providing me with this method.
Download the attached file: View attachment Vision-fre3vo-temp-root.zip
Extract the contents to your platform-tools directory.
Run the following commands in command prompt while in platform-tools directory:
Code:
> adb push su /data/local/tmp/
> adb push busybox /data/local/tmp/
> adb push fixsu.sh /data/local/tmp/
> adb install SuperUser.apk
> adb shell chmod 755 /data/local/tmp/fixsu.sh
> adb shell /data/local/tmp/fixsu.sh
Download a backing up application such as...
Titanium Backup
MyBackup Root
Make a backup!
I - 4) Downgrading
Download the Stock Rom for your device:
G2: PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip (Link not working last time I checked... hopefully it will come back up).
Mirrors:
Vision_G2_1.19.531.1_PC10IMG.zip (Working as of April 2023)
MD5: 531c08dc402e15577b947bf4cd22aec2
Desire Z: PC10IMG.zip
Mirrors:
PC10IMG.zip
Vision_DZ_1.34.405.5_PC10IMG.zip
Vision_DZ_1.34.405.5_PC10IMG.zip
MD5: 2ff42897cd27e0db425a2cf36c8bd078
myTouch 4G: PD15IMG.zip
Mirrors:
http://cmw.22aaf3.com/glacier/stock/1.17.531.2/PD15IMG.zip
http://goo-inside.me/ruu/glacier/fu....140e_26.03.02.26_M_release_155771_signed.zip
Glacier_mT4G_1.17.531.2_PD15IMG.zip
Glacier_mT4G_1.17.531.2_PD15IMG.zip
MD5: 49d07f0ee7de1765a6a84cb12fa53110
Desire HD: RUU_Ace_HTC_WWE_1.24.405.1_Radio_12.27.60.14b_26.02.00.29_M4_release_151852_signed.zip
Mirrors:
Ace_DHD_1.24.405.1_PD98IMG.zip
Ace_DHD_1.24.405.1_PD98IMG.zip
MD5: a107b30a4b397c9238ddc7f4571c2ee8
Follow either Manual Downgrade OR Fastboot Downgrade.
I - 4a) Manual Downgrade
Rename the downloaded rom to it's proper update name:
(Please note, the filenames MUST be all uppercase except for the extension, and if file extensions are hidden, do not include ".zip"):
G2: "PC10IMG.zip"
Desire Z: "PC10IMG.zip"
myTouch 4G: "PD15IMG.zip"
Desire HD: "PD98IMG.zip"
Place the zip file in the root of your sdcard.
Reboot your phone into bootloader by typing the following command:
Code:
[B]> adb reboot bootloader [/B]
After your phone has entered bootloader, press the power button. It will then scan for the associated rom file and ask you to update by pressing a key.
Press the key it requests to perform the update.
DO NOT INTERRUPT THIS PROCESS.
Your phone will reboot once or twice - this is completely normal.
This process will take roughly 5-10 minutes so make sure your phone is plugged in, either to an outlet or your computer.
Once the process is finished, it will ask you to reboot by pressing a key. Press the associated key and it will reboot into the Stock Froyo rom!
After booting into Android 2.2, DO NOT update the OTA that is around 70MB. That is the update to Gingerbread. There is one update that will come before that, that is a lot smaller in size, which is the WiFi-Calling update - that update is okay to install.
I - 4b) Fastboot Downgrade
Rename the downloaded stock rom "StockRom.zip" (if extensions are hidden, rename it "StockRom").
Place the downloaded stock rom zip file in your platform-tools directory.
Download the attached file View attachment fastboot.zip. In the zip archive there are three folders, "windows", "mac", and "linux".
Extract the file from the associated with your operating system and place it in platform-tools directory.
In command prompt, type the following command to reboot into bootloader:
Code:
[B]> adb reboot bootloader[/B]
Make sure your device is recognized by typing the following command.
Code:
[B]> fastboot devices[/B]
If you device is recognized, it should return a serial/model number.
Code:
[B]> fastboot oem rebootRUU[/B]
Your phone should now reboot into a black screen with a gray/silver "HTC" logo on it.
Next we flash the Stock Rom. This may take a few minutes as it transfers the file to the phone then attemps to update (downgrade).
Code:
[B]> fastboot flash zip StockRom.zip[/B]
In rare cases the flash stops and the user gets a warning to repeat the flash immediately - no panic, just run the "fastboot flash zip StockRom.zip" (only this command, not the rebootRUU one) again and it will work.
When it finishes, wait a minute or two (just in case) then reboot your phone by typing:
Code:
[B]> fastboot reboot[/B]
After booting into Android 2.2, DO NOT update the OTA that is around 70MB. That is the update to Gingerbread. There is one update that will come before that, that is a lot smaller in size, which is the WiFi-Calling update - that update is okay to install.
II) Sources:
#g2root: http://fishporn.ca/vision.gingerbread.root.html
Using fre3vo: http://therootofallevo.com/forums/viewtopic.php?f=6&t=120
[GUIDE] ADB Workshop and Guide for everyone
[HOW-TO] ADB for Dummies(How-To Learner's Guide)
How To Set Up ADB/USB Drivers for Android Devices
[ROM]Ace Test & Stock ROMS [RE-UPLOADED]
Instructions for flashgc
Temp-Root Backup Post by Nipqer
[GUIDE] How to get root/flash custom roms with HTCDEV unlock
flashgc by skorgon
Various Chats I've had with individuals.
If anyone needs further help and would prefer messaging me, feel free.
AIM: IgnorantNihilist
G-Talk: [email protected]
MSN: [email protected]
III) Troubleshooting
Cimer said:
[...] If [the downgrade] does not work, Right click your Command prompt, Select All, Right click again. Then go to pastebin.com, paste there, Scroll down, name it and hit submit. After that post the link here and we'll take a look at it.
EVERYONE: If you want a faster diagnostic please do this in advance and other people can see your mistakes.
Click to expand...
Click to collapse
You can also join the IRC channel #g2root on irc.freenode.net and ask questions in there. If you are unfamiliar with IRC, you can go to http://webchat.freenode.net and pick an alias, for channel type in #g2root and enter the reCAPTCHA and connect.
I wanted to give credit to specific individuals whom have helped write this guide, provided important feedback to further improve this guide, and/or in any other way further improved this guide. I think these invidiuals should be recognized, as if it were not for them, this would wouldn't be as elaborate, dynamic, and informative as it is. So a special thanks to, Cimer, strawmetal petarpLab, iDylan1357, asharma5290, guhl, pierre_ja, and skorgon from #g2root. And I would also like to recognize and give a major thanks to Nipqer whom offers a lot of support with constant responses helping assist those whom ask for help both in this thread as well as on IRC. And he is always making sure I keep this as updated as it can be.
IV) Change Log
2023/04/14
I'm no longer supporting this thread anymore however I will try to update it if someone messages me with an issue. I don't have time anymore unfortunately. I did however update the downgrade ROM for the G2. The link in the mirror is currently hosted on my google drive. If there's a problem let me know in a private message.
2013/06/14
Update ratherphallic.co.cc links to ratherphallic.tk. -Nipqer
2012/11/11
Made some minor changes (grammar, spelling, layout/format).
Added links to guides which fix the issue with Desire HD (Ace) w/ Sense 3.x
2012/05/22
Changed "fastboot" attachment to have 3 folders ("windows","linux",and "mac") each with "fastboot" in it instead of having "fastboot-linux", "fastboot-mac", and "fastboot-windows.exe".
Changed fastboot portion of guide to reflect change to attachment for easier usability.
2012/04/21
Updated strawmetal's PDF document for G2/Desire Z Downgrade.
Added link to strawmetal's tools used in his PDF Guide.
2012/03/07
Added a PDF file that strawmetal was kind enough to make for Vision users.
Added links to attached files in the guide where I reference them.
2012/02/03
Changed link to the Stock Vision (G2) Rom and added mirrors.
Changed link to the Stock Vision (Desire Z) Rom and added mirrors.
Added mirrors to the Stock Glacier (myTouch 4G) Rom.
Changed link to the Stock Ace (Desire HD) Rom and added mirrors.
2012/02/03
Added a guide to help individuals whom have used the "official" htcdev.com unlocker method.
2012/02/03
Fixed link for the G2, Desire Z, and Desire HD (thanks to repast & cmstlist.
2012/04/13
Possible exploit found for Desire HD updated to latest OTA update (which patched our current method).
2012/01/28
Fixed link for myTouch 4G as megaupload has been taken down. Also added mirrors for myTouch 4G Stock Rom.
2011/12/20
Clearified which phone models this guide is intended for as well as noting that the Doubleshot does not work.
Made note that a recent OTA patch for the Ace, giving it Sense 3.x, has patched this method and this method will no longer work on Ace models which have Sense 3.x
2011/12/17
Added new goldcard generator and simplified the guide.
2011/10/27
Changed the download link for the Desire HD.
Added MD5 checksums next to the rooms.
2011/10/26
Re-added the manual downgrade method due to people having issues with the fastboot method.
2011/10/23
Fixed a slightly error in code during the temp-root backup section. Had "adb install install Superuser.apk", replaced it with "adb install Superuser.apk"
2011/10/22
Added a method to be able to backup data prior to downgrading! (thanks to Nipqer from #g2root)
2011/10/20
Added Desire HD.
Changed the downgrading method to use fastboot rather than manually downgrading.
Added "Creating A Goldcard" method from http://www.thinkthinkdo.com/trac/project1/attachment/wiki/pierre_ja/flashgc_instructions
2011/08/26
Changed modified version number for each device to 1.00.000 as it is more universal and works for each one.
Made it more clear to extract the attached files and place them in the platform-tools directory for use.
2011/08/06
Added a couple links to ADB guide.
2011/08/05
Added myTouch 4G
Added link to an "adb" guide.
Changed title from "[GUIDE] Downgrade G2 2.13.531.8 (2.3.3 T-Mobile Rom w/ S-ON) & DZ 2.3.3 w/ S-ON" to "[GUIDE] Downgrade G2 (2.3.3) & DZ (2.3.3) & mT4g (2.3.4) w/ S-ON to Stock Froyo"
V) Attached Files
View attachment misc_version_01.zip
View attachment fre3vo.zip
View attachment fastboot.zip
View attachment Vision-fre3vo-temp-root.zip
View attachment flashgc.zip

Wow first guide. Nice! I hope this helps people who have 2.3.3 so they can stop asking how to downgrade
Sent from my HTC Vision using XDA App

Sweet, now I can finally get my phone replaced. Accidentally blew out my LED and was scared of asking for a new one for fear of being unable to root. Thanks for the peace of mind I'll be using this in a few days

Just some suggestions to avoid confusion when you run the command
Code:
adb shell cat /dev/msm_rotator
you should get the return of
Code:
/dev/msm_rotator: invalid length
you do not need to enter in this line.
Also after entering
Code:
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
or one like it and it fails (It should not) you need to reboot the phone between these attempts.
Thanks for writing the guide! We just posted the log lol
Late side note: I've recently read an article on how root exploits are not credited to their original inventors. Just letting everyone know that agrabren should be credited as well for his work with Fr3v0, and his willingness to help during the process

Thanks for the tips Cimer, I edited the post, hopefully that clarifies it a bit more.
I've been a quiet browser here on XDA for quite a while but I believe that was actually the first post I made =3 It took me a while to try to get it formatted... fluently / tried to make it easy to read and follow.
And hey, if it wasn't for you all posting the logs from #g2root, I would of never gotten my G2 back to being rooted. I think I had like 8 different pages open when I was doing it, reading the chat log, reviewing the pastebin data, et cetera. But it worked, after searching every day, the trick has been found.
On a side note, I picked the range "-start FAA90000 -end FFFFFFFF" because it appears that the exploit is most likely within that range. It was for yours "FBB47C00:1400", mine was "FBB4D600:A00", and a friend of mine was also an FBB*.

Does it work for the european desire Z ?

ilbeppez said:
Does it work for the european desire Z ?
Click to expand...
Click to collapse
Personally, I have no idea. I don't imagine it would hurt the phone any if you tried. I know you would have to change the version number (when using misc_version) to a different number, one that would be equivalent to the stock rom that came with the phone. As for the exploit itself, I don't see any harm it could do to try (though I'm no expert). Just be sure to reboot your phone after each attempt of using fre3vo.

ilbeppez said:
Does it work for the european desire Z ?
Click to expand...
Click to collapse
Give me a second, Guhl made a post about this...
http://forum.xda-developers.com/showpost.php?p=15825944&postcount=27
Should explain things for Desire Z users.

Cimer said:
Give me a second, Guhl made a post about this...
http://forum.xda-developers.com/showpost.php?p=15825944&postcount=27
Should explain things for Desire Z users.
Click to expand...
Click to collapse
Ok
thanks

Thank you. I have been searching for this.

Setherio, please divide a section for 2.3.3 DZ owners. the appropriate PC10IMG.zip for them is
http://www.multiupload.com/GH26HXLLES (md5 2ff42897cd27e0db425a2cf36c8bd078)
the mics_version command is: /data/local/tmp/misc_version -s 1.33.405.5
the push command is: adb push PC10IMG.zip /sdcard/

petarpLab said:
Setherio, please divide a section for 2.3.3 DZ owners. the appropriate PC10IMG.zip for them is
multiupload.com/GH26HXLLES (md5 2ff42897cd27e0db425a2cf36c8bd078)
the mics_version command is: /data/local/tmp/misc_version -s 1.33.405.5
the push command is: adb push PC10IMG.zip /sdcard/
Click to expand...
Click to collapse
Thanks for the information. I updated the guide.

thanks a lot

Incase anyone did not know already gfree is the best way to root after the downgrade...visionary bricks phones. You can find gfree in the xda wiki.
Sent from my HTC Vision using XDA App

Great guide. My first downgrade and I haven't bricked my phone
Thanks to all people that made it possible
Cimer said:
Incase anyone did not know already gfree is the best way to root after the downgrade...visionary bricks phones. You can find gfree in the xda wiki.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
So AMT is ok for rooting after downgrade?
This package contains:
- gfree
- gfree_verify
- Superuser
- Busybox
- flash_image
- psneuter
- root_psn
- misc_version
- GingerBreak APK
Click to expand...
Click to collapse

trzype said:
Great guide.
My first downgrade and I haven't bricked my phone
Thanks to all people that made it possible
Click to expand...
Click to collapse
Thank you Glad it helped you.
trzype said:
So AMT is ok for rooting after downgrade?
Click to expand...
Click to collapse
Yes. I downgraded and rooted, went ahead and installed Cyanogen nightly. As did a couple others I've talked to who have downgraded as well.

Used AMT. Got some error about 1.34 and "Double" but cliked Continue button anyway. Everything went fine.
Setherio said:
I downgraded and rooted, went ahead and installed Cyanogen nightly. As did a couple others I've talked to who have downgraded as well.
Click to expand...
Click to collapse
I'm going for Virtuous 2.0.0. Can't live without Sense UI
Thanks again

Should I rename the stock Rom to just PC10IMG before I push it to sd card or can I just put it on sd card before hand
Sent from my HTC Sensation 4G using XDA Premium App

Got it worked great thanks

Thank you so much worked like a charm - Peace

(MAYBE) How to downgrade and root 2.43.661.1 and up! TEST IT!

Anyony give it a try?
How to downgrade and root 2.43.661.1 and up:
http://androidforums.com/desire-hd-all-things-root/382082-how-downgrade-root-2-43-661-1-up.html
I'll try it later this week (see my posts over there)...

wat abt 2.42 ??????????????

And 2.50.405.2? It ins´t for this?

dwyaneW said:
And 2.50.405.2? It ins´t for this?
Click to expand...
Click to collapse
Apparently it works too, this guy has that build number: http://androidforums.com/desire-hd-...downgrade-root-2-43-661-1-up.html#post2995693

Finally we have a way to downgrade from 2.50 !!!
Hi All !
I tested it and it worked, so here are the things you need:
Download the downgrade.zip
An SD card with the 1.32 PD89IMG.zip
Connect your phone in Charge Only mode with USB Debugging enabled.
Run these commands with enter after every line:
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF
If you success you will see this message:
Potential exploit area found at address (maybe fbb6b600:1a00 or something else).
Exploiting device...
Then run the following:
adb shell (you will have to get the "#"
/data/local/tmp/misc_version -s 1.31.405.3
adb reboot bootloader
Run the ROM setup and you will done

This method is the same as CubZ
im all over both threads, please post offsets at which the exploit was found on your device.
so as we can narrow down the searches to make a quick one click method.

JSLEnterprises said:
This method is the same as CubZ
im all over both threads, please post offsets at which the exploit was found on your device.
so as we can narrow down the searches to make a quick one click method.
Click to expand...
Click to collapse
Potential exploit area found at address (maybe fbb6b600:1a00 or something else). This is the address of my phone.

great
great
great
great
greatgreat

CONFIRMED on Telus Desire HD running 2.43!
Follow the instructions on this link here:
http://driphter.com/index.php?topic=3867.0
I just completed Step 7. Step 8 will have to wait until I get home, since I don't have administrative access on this computer, so I can't run the batch to turn off Radio S-Off yet. BUT my phone is rooted now. Now running on Android 2.2 build 1.32.405
Also, just perm rooted using Visionary+. Just tested it with adb shell and got the magical #.
Thank you JSL from Dripther.com!

Totally works! No problems at all on my unbranded DHD.

JSLEnterprises said:
This method is the same as CubZ
im all over both threads, please post offsets at which the exploit was found on your device.
so as we can narrow down the searches to make a quick one click method.
Click to expand...
Click to collapse
It found an exploit area at fbb7f800:1800 on my Telus-branded Desire HD.
EDIT: I've tried the process about 4 or 5 times, and everything goes fine until it boots into the bootloader. Whenever it gets to that stage, nothing appears to get flashed and my phone goes right back to the way it was. Any particular reason for that?

Finaly, i give it a try.
Sent from my Desire HD using XDA Premium App

Now I downgraded 2.50 build !!

We also have a giude from CuBz90 in "Desire HD Android Development" forum: http://forum.xda-developers.com/showthread.php?t=1152233

Works perfect, custom rom, android revolution installed
Sent from my Desire HD using XDA Premium App

Command_HDX said:
We also have a giude from CuBz90 in "Desire HD Android Development" forum: http://forum.xda-developers.com/showthread.php?t=1152233
Click to expand...
Click to collapse
I had the exact same luck with that. I've used this exact same SD card with my old HTC Hero, so it's not the card. Could it just be something as simple as me having a corrupted download of PD98IMG.zip? I'll check the MD5 and report back.

This works for 2.50xxx. Just did it. If it fails 1st time, unplug and try again.
Sent from my Motorola Startac running Atari 2600 software!

Going Out My Mind

I have a HTC Desire Z
Im From the Uk
and the phones already been unlocked
I have restored it many times and the unlock has stayed with the phone.
before this i had a iphone 4
i am trying to root my phone to use gamechi and custom roms
i have tried so many ways, gold cards, adb its all so fkin confusing
i have tried visionary z4root etc.. nothing works.
sw
2.3.3
htc sense v 2.1
htc desire z a7272
software number 2.42.161.2
i have followed steps to use the commands for terminal, followed youtube videos, done gold cards etc... its so confusing even following step by step i end up getting an error or someting doesnt work correctly. i might be wrong but im guessing my software version. 2.3.3 so i have tried to follow steps to downgrade it, still no fkin joy
please .. help?
any help will be appreciated happy christmas

C:\android-sdk-windows\platform-tools>adb shell cat /sys/class/mmc_host/mmc2/mmc
2:*/cid
035344535530384780086c959000a7f2
C:\android-sdk-windows\platform-tools>adb push psneuter /data/local/tmp
push: psneuter/psneuter.c -> /data/local/tmp/psneuter.c
push: psneuter/psneuter -> /data/local/tmp/psneuter
2 files pushed. 0 files skipped.
994 KB/s (561954 bytes in 0.552s)
C:\android-sdk-windows\platform-tools>adb push misc_version /data/local/tmp
989 KB/s (589849 bytes in 0.582s)
C:\android-sdk-windows\platform-tools>adb shell chmod 777 /data/local/tmp/psneut
er
C:\android-sdk-windows\platform-tools>adb shell chmod 777 /data/local/tmp/misc_v
ersion
C:\android-sdk-windows\platform-tools>adb shell /data/local/tmp/psneuter
Failed to set prot mask (Inappropriate ioctl for device)
again stuck

we on the same boat, been trying for 2 days now i follow almost all the guide on here and nothing works<htc vision g2 t-mobile 2.3.4..any help will be appreciated

fank god i did it
first
http://forum.xda-developers.com/showthread.php?t=1178912
follow that guide every step
ignore fast boot downgrade do a manual downgrade
that will downgrade u to 2.2 what is needed
then when done
use this guide
http://www.addictivetips.com/mobile/how-to-gain-permanent-root-on-t-mobile-g2-desire-z-without-adb/
make sure u download all the relevant files
only ones that u need for ur device
after that boom
instal rom manager
and gamechi from the market
and aptoid and aptoid repos etc...
it worked for me
and i been trying for months
the wrong fkin methos
but this works 100%
i got cyanogenmod running.
it got stuck on boot and kept looping and i was like o ****
then i did a restore and bam its perfect all round
good luck mate
it is easy just too much detail is put sometimes
so it gets confusing
but this methos works 1000000% and im so friggin happy im a chew santas knee caps off

Awesome. Was about to say the 'downgrade' here is key to your phone version since it was factory launched with Gingerbread. Glad it's all good.
Sent from my HTC Vision using XDA App