Database Users

Best way to temp root HTC Desire Z?

I want to perm root my phone..
But to do that i need to downgrade first. And i would like to be able to backup and maybe extract rom first.
So whats the best way to temp root a DZ?
Via HTC Desire Z

Afaik when you downgrade, you loose your rom before you downgrade, so let say you downgrade from 1.82 to 1.34, you can perma root 1.34 hence backup your current rom which is 1.34 not 1.82.
I have the same worry as you, in fact I face a dillema upon not able to backup my current rom, but I simply being bold and try to downgrade the whole day until 2 hours ago where I get stuck where I'm ready to flash the PC10IMG.zip, btw I use amt tool, just search 'amt tool' here in this sub forum, and also check the sticky thread in development section there are various guide to root and downgrade, however in principle they work the same, just remember to stick to one guide to make life easier.
Sent from my HTC Vision using Tapatalk

As far as i know. The downgrade procedure is only for perm root. There should be a way to temp root. Extract rom, and then being able to downgrade and perm root with a little less risk.
But then again.. im not sure of how to extract a rom.. so right now im just hoping that temp root + extraction is possible before downgrading.
Can you extract a rom using titanium backup?
Via HTC Desire Z

Best temp root methods that proved to work in IRC #G2ROOT
in the IRC channel #G2ROOT on freenode.net we helped some people to temp root their HTC Desire Z and G2 phones (commonly also known as HTC Vision).
The best methods that worked for us are:
* zergRush (works good for Froyo / 2.2 and Gingerbread / 2.3 ROMs)
* tacoroot
* fre3vo
== zergRush ==
Usage see http://forum.xda-developers.com/showthread.php?t=1296916
== Tacoroot ==
Usage see http://forum.xda-developers.com/showthread.php?t=1424023
Do NOT download "1.32 PD98IMG.zip"!
Only download tacoroot, extract the zip file into platform-tools (directory that contains adb) and connect your phone to computer using an USB data cable, enable "adb debugging" in menu settings / applications / development and make sure you are in "USB charge only" mode.
Then run:
adb push tacoroot.sh /data/local/tmp/tacoroot
adb shell chmod 755 /data/local/tmp/tacoroot
adb shell
/data/local/tmp/tacoroot --setup
This command will reboot the phone to recovery. Once it is done, use vol up/power then choose 'reboot' to reboot the phone. After it boots (it will bootloop, that's expected)
adb shell
/data/local/tmp/tacoroot --root
this command will kick you out of adb shell, so we need to return there:
adb shell
Now you should see "#" as sign of root access.
To uninstall tacoroot use:
adb shell /data/local/tmp/tacoroot --undo
== fre3vo see ==
Usage see http://forum.xda-developers.com/showthread.php?t=1178912
To test if fre3vo works on your phone you can use the command:
adb shell cat /dev/msm_rotator
The output should be: /dev/msm_rotator: invalid length
One of the following commands for using fr3vo should work from phone shell, which you can open by "adb shell":
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/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
Enjoy!

First off no reason to backup stock rom, contacts saved in google, sms and call log can be saved in various apps. App cache is who cares start over on your game or what have you. Also you can always unroot and go stock whenever. Find a custom build be it aosp or whatever your liking you'll be way happier. Just having root access is what makes your phone a good phone. So follow the wiki, downgrade, root, be happy. Still can't think of a reason not to going all the way back to the days of the g1, no reason not to root.
Sent from my T-Mobile G2 using xda premium

EVO Shift Temp Root for 2.3.3 and HBoot Downgrade

To downgrade your HBOOT to go back to 2.2 visit this link http://forum.xda-developers.com/showthread.php?t=1255474
This will allow you to flash 2.2 to perm root the phone
If you wish to help with perm root status for Android 2.3.3, please visit this thread http://forum.xda-developers.com/showthread.php?t=1218580
Thanks to everyone in this post who has helped get this far. You will need to have the Android SDK installed and working knowledge of ADB and basic file system structure.
Major help from minneyar
TEMP ROOT Instructions:
Download http://tinyw.in/1lI
Unzip if required and put in your ADB folder
Launch command prompt and navigate to your ADB folder
adb push fre3vo /data/local/tmp/
adb shell
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF (if this doesn't work, try rebooting phone)
Download these 2 files here and put them in your ADB directory: http://forum.xda-developers.com/showthread.php?p=14927732#post14927732
exit back to command prompt if you aren't there already
adb push Superuser3-beta1.apk /data/app/
adb push su-3.0-alpha7 /data/local/tmp
adb shell (should now see # instead of $)
cd /data/local/tmp
chmod 777 su-3.0-alpha7
./su-3.0-alpha7
cd /
mount -o remount,rw -t rootfs rootfs /
rm vendor
mkdir vendor
mkdir vendor/bin
cat /data/local/tmp/su-3.0-alpha7 > /vendor/bin/su
chmod 4755 /vendor/bin/su
You now have temp root. Disregard any notification about outdated SU binary. Root will go away if you reboot. If you reboot your phone you can obtain root again by just running the following
adb shell
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF
adb shell (should now see # instead of $)
cd /data/local/tmp
chmod 777 su-3.0-alpha7
./su-3.0-alpha7
cd /
mount -o remount,rw -t rootfs rootfs /
rm vendor
mkdir vendor
mkdir vendor/bin
cat /data/local/tmp/su-3.0-alpha7 > /vendor/bin/su
chmod 4755 /vendor/bin/su
I haven't found a way to re-root after rebooting without connecting to a PC

Type su and see if it gives you root permissions
Sent from my MiuiSpeedy

says su: not found.

You are saying you cannot install the superuser app? From reading in the Evo3D forums, you could install Superuser, even without being rooted, but it obviously won't allow root access, until you run a root exploit.
Try rebooting the phone, installing superuser, run fre3vo, and then try the adb shell, and su method.
This is getting interesting. Hopefully you are on to something.

Stuke00 said:
See screenshot. Doesn't the # mean temp rooted? Tho I cannot install SU and Root Explorer isn't working. Anything else I need to do first or something?
Click to expand...
Click to collapse
Looks hopeful!

tokuzumi said:
You are saying you cannot install the superuser app? From reading in the Evo3D forums, you could install Superuser, even without being rooted, but it obviously won't allow root access, until you run a root exploit.
Try rebooting the phone, installing superuser, run fre3vo, and then try the adb shell, and su method.
This is getting interesting. Hopefully you are on to something.
Click to expand...
Click to collapse
Okay let me clarify
I can install SU but it wouldn't install the binaries. I did all of the above. Says su: not found.
I then tried something else.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cat /system/bin/sh > /system/bin/su
# chmod 4755 /system/bin/su
I was then able to get the SU binaries to install but Titanium Backup says:
"Busybox works but the "su" command does not elevate to root: "whoami" reports "app_135" instead of root/uid 0.
then su from the command prompt was saying "link_image[1935]: 3160 missing essential tablesCANNOT LINK EXECUTABLE" and now back to su: not found again....

I don't know enough about linux commands to give you any real info. Like in the other thread, talk to agrabren, to see what he has to say.

tokuzumi said:
I don't know enough about linux commands to give you any real info. Like in the other thread, talk to agrabren, to see what he has to say.
Click to expand...
Click to collapse
Yeah I tweeted him with what I could provide with 160 characters. Just waiting now.

Well here's a tweet he put out a couple of hours ago.
@agrabren: For those with the SHIFT, it's a known bug in my code that we missed the address. One too many zeroes in the list. I'll try to fix it soon.
Sent from my PG06100 using XDA App

crump84 said:
Well here's a tweet he put out a couple of hours ago.
@agrabren: For those with the SHIFT, it's a known bug in my code that we missed the address. One too many zeroes in the list. I'll try to fix it soon.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Yeah he posted that right after I gave him the memory address for the exploit. Just means that I did it the manual way through debugging. At least I think so... hopefully soon!

Good news, everybody! I have successfully acquired temp root on my Shift!
First, fre3vo has to be pointed at the right address. After copying it over to my phone, I did "adb shell" and then ran it like so:
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF
That printed out a message that it found an exploit and kicked me out of the shell. After doing "adb shell" again, I got a command prompt. I tried installing the 2.3.6.3 version of Superuser, but it complained about being unable to install "su"; I tried to find a separate su binary and copy it over manually, but it didn't work due to a linker error.
After searching around, I found a beta version of Superuser 3:
http://forum.xda-developers.com/showthread.php?p=14927732#post14927732
First I uninstalled the old version of Superuser and then used adb to install the new one from that thread. I ran it and it said it was unable to install su, so I downloaded the version of su provided there and installed it manually. The process went something like:
Code:
adb push su-3.0-alpha7 /data/local/tmp
adb shell
# cd /data/local/tmp
# chmod 4755 su-3.0-alpha7
# ./su-3.0-alpha7
# mount -o remount,rw -t ext3 /dev/block/mmcblk0p26 /system
# cat su-3.0-alpha7 > /system/bin/su
# chmod 4755 /system/bin/su
I don't know if explicitly running "./su-3.0-alpha7" is necessary, it just seemed like a good idea at the time. I don't know if everybody's block device will be named "mmcblk0p26", I used "mount" to figure out what was mounted at /system.
Anyway, after all that was done, I ran Superuser again and it didn't complain. To test it out, I started up Wireless Tether. It asked me for superuser permissions, which I granted it, and it's working fine.
Root successful!

Good job!!
Sent from my Speedy HTC EVO shift on XDA Premium app

I followed those steps exactly and got what I would call a partial root. Some of the 'you need root' errors are gone but "su" still results in 'not found' even though "mkdir su" results in 'file exists.'
mmcblk0p26 exists on this unit.
The weirdest part is that Adfree will accept the device as rooted and with superuser but says it can't find a partition to modify. And after a reboot root is definitely gone.
I think you're on to it but it isn't quite there yet.

It seems to be fully temprooted to me; I have to redo it if I reboot, but otherwise it's working perfectly. After following the steps I listed above, running "ls -l /system/bin/su" should produce this output:
Code:
# ls -l /system/bin/su
ls -l /system/bin/su
-rwsr-xr-x root root 22228 2011-07-25 19:14 su
If it says "No such file or directory" instead, then the su binary isn't in the right place.
Looking back over what I wrote, I think I left out a step -- if you were following what I listed exactly, it probably won't work, because I forgot to change to the /data/local/tmp directory. I'll update that...
Update: after playing around with it for a while, something is definitely not quite right. Everything works fine at first; I've tested Wireless Tether and Titanium Backup and they're both fine. After leaving my phone for a while and coming back, though, applications that try to get root access mysteriously fail. The dialog prompt doesn't even appear.
Going back into the adb shell, /system/bin/su is still there, but trying to run "su" causes this to happen:
Code:
# su
su
link_image[1935]: 3802 missing essential tablesCANNOT LINK EXECUTABLE
But if I use cat to overwrite su and then chmod it again, everything works. su must somehow be getting modified by something else and replaced with a bad version... but I'm not sure where to look.

I caught something like that.
I think there should be a chmod 777 su-3.0-alpha7 after cd /data/local/tmp

minneyar said:
It seems to be fully temprooted to me; I have to redo it if I reboot, but otherwise it's working perfectly. After following the steps I listed above, running "ls -l /system/bin/su" should produce this output:
Code:
# ls -l /system/bin/su
ls -l /system/bin/su
-rwsr-xr-x root root 22228 2011-07-25 19:14 su
If it says "No such file or directory" instead, then the su binary isn't in the right place.
Looking back over what I wrote, I think I left out a step -- if you were following what I listed exactly, it probably won't work, because I forgot to change to the /data/local/tmp directory. I'll update that...
Update: after playing around with it for a while, something is definitely not quite right. Everything works fine at first; I've tested Wireless Tether and Titanium Backup and they're both fine. After leaving my phone for a while and coming back, though, applications that try to get root access mysteriously fail. The dialog prompt doesn't even appear.
Going back into the adb shell, /system/bin/su is still there, but trying to run "su" causes this to happen:
Code:
# su
su
link_image[1935]: 3802 missing essential tablesCANNOT LINK EXECUTABLE
But if I use cat to overwrite su and then chmod it again, everything works. su must somehow be getting modified by something else and replaced with a bad version... but I'm not sure where to look.
Click to expand...
Click to collapse
YES! I have root! I was able to install a screenshot app and test it this is amazing progress! Thanks for that.
So now when I reboot, you have to do the entire thing again? SU and all?

Stuke00 said:
So now when I reboot, you have to do the entire thing again? SU and all?
Click to expand...
Click to collapse
Yes, every time you reboot you'll have to redo the whole process, including running fre3vo and then copying su into /system/bin. Hopefully somebody will figure out a permanent root soon.

Wow those SU binaries are disappearing before I even reboot! Already gone and I haven't rebooted the phone

I think I had that issue too. I just couldn't believe the files just disappeared and thought I did something wrong somewhere.

Would a logcat help anyone at all? Anything I should look for?

[Q] Help - trying to downgrade 2.3.3....

All Sorted Guys
Only had to restart the process from sctratch
MODS: please delete my posting as I cant see this being of any help to anyone
thanks
hi Guys
After a year of putting up with stock Sense I decided to root my DezireZ.
Unfortunately, I am expiriencing a problem I think...
I am following the wiki downgrade guide and I managed to get to point 6:
------
6.After you enter that command, with luck 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:
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...
7.
a.If the exploit works, you will be kicked out of ADB shell, proceed to Step #8.
b.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:
$ /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
---------------
now, the first set of addresses didnt work (I didnt get the sentence about exploiting the device) and I only got the '$' sign
so I have rebooted the phone and copy/pasted the first line with addresses 10000000-1FFFFFFF (as per guide)
and here my problem starts...
it started scanning different regions, the last one being 102d0000... and after that nothing ???
I got a flashing cursor (as if it were still running) but it is good 20 minutes now (?) and guide says about a minute or two!!!
is it safe just to disconnect the fone and restart the whole process
help, anyone?
thanks in advance

Cant perm root Mytouch 4G please help before you move my thread

I have spent hours on xda, downloading gfree, trying to downgrade, trying taco root. I even unlocked bootloader at htc dev and cannot get my phone perm rooted
I have 2.3.4
software 2.32.531.1
i used the guide on how to downgrade to 2.2.1 for the visionary exploit
i keep getting permission denied
Potential exploit area found at address fbb80e00:200.
I am sorry for sounding like "noob" but i wasted the day trying to do this and have given up
Someone please help me, ill even donate a cup of coffee to whoever helps me fix this. No joke from 9 am to 530 pm, i have been going in circles, i downloaded the htc easy root tool all failed
the farthest i made it was getting temp root with taco root, but there are no clear cut instructions for what to do after, these guides are over a year old prior to my version of android

I'm not sure where your going wrong but the guides work fine. I used them to downgrade, perm root, and flash the engineering bootloader. Have you tried asking in the q and a section? I'm sure you will find a solution, if you ask in the proper place.
Sent from my HTC Glacier using Tapatalk

I would try this guide http://forum.xda-developers.com/showthread.php?p=15851661
Sent from my HTC Glacier using xda premium

i have been on here for 9 hours going through the q/a this is a brand new str8 from t-mobile mytouch 4g with the newest possible rom, a year ago i successfully did this dozens of time with visionary, its this new rom thats the problem, i put virtuous rom successfully on my first mytouch a year ago, and ive rooted my hd2 for friends and family, so i know my way around xda, this is the first time im truly stuck

cnote 74 i tried that guide my expolit area "fbb80e00:200" is not covered by that guide, if you look at the 5 or 6 lines
$ /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
mine is different than all of these

this is what ive been getting, i followed the guide to the T
C:\AndroidSDK\platform-tools>adb shell cat /dev/msm_rotator
adb server is out of date. killing...
* daemon started successfully *
/dev/msm_rotator: invalid length
C:\AndroidSDK\platform-tools>adb push fre3vo /data/local/tmp
869 KB/s (9796 bytes in 0.011s)
C:\AndroidSDK\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Potential exploit area found at address fbb6c400:c00.
Exploiting device...
C:\AndroidSDK\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
# exit
exit
C:\AndroidSDK\platform-tools>adb push misc_version /data/local/tmp/misc_version
1718 KB/s (15837 bytes in 0.009s)
C:\AndroidSDK\platform-tools>adb shell chmod 777 /data/local/tmp/
C:\AndroidSDK\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version: permission denied
#

1st off.......THIS IS THE DEVELOPMENT SECTION! NOT Q&A! THATS WHAT THE Q&A IS FOR!
2nd....its because you unlocked via htcdev, which we have warned users multiple times if you did read the Q&A and General forums.
Htcdev method makes it harder to root/flash a ROM. We warned you. And then you complain and post in the wrong section!
Edit: also.....If you knew to put "DON'T MOVE THREAD", why did you post it here in the first place?
Sent from my HoneySmartDroid Port using XDA Premium.

Edit: I like that better /\
Sent from my HTC Glacier using Tapatalk

Chek this out bro hope it help ;-) http://forum.xda-developers.com/showthread.php?p=9551846
Sent from my HTC Mytouch 4G using xda premium

still stuck invasion2 you have a solution

michael.racelli said:
still stuck invasion2 you have a solution
Click to expand...
Click to collapse
Sorryf for flaming.....anyway I did find something... http://www.forum.xda-developers.com/showthread.php?p=21563546
Sent from my HoneySmartDroid Port using XDA Premium.

michael.racelli said:
I have spent hours on xda, downloading gfree, trying to downgrade, trying taco root. I even unlocked bootloader at htc dev and cannot get my phone perm rooted
I have 2.3.4
software 2.32.531.1
i used the guide on how to downgrade to 2.2.1 for the visionary exploit
i keep getting permission denied
Potential exploit area found at address fbb80e00:200.
I am sorry for sounding like "noob" but i wasted the day trying to do this and have given up
Someone please help me, ill even donate a cup of coffee to whoever helps me fix this. No joke from 9 am to 530 pm, i have been going in circles, i downloaded the htc easy root tool all failed
the farthest i made it was getting temp root with taco root, but there are no clear cut instructions for what to do after, these guides are over a year old prior to my version of android
Click to expand...
Click to collapse
no need to downgrade
http://forum.xda-developers.com/showthread.php?t=803682

I relocked the bootloader, still the same thing permission denied, am i the only one who has encountered this issue, i cannot root downgrade right now if my life depended on it right now

adb push misc_version /data/local/tmp/misc_version
> adb push flashgc /data/local/tmp/flashgc
> adb shell chmod 777 /data/local/tmp/* <--------(THIS LINE IS YOUR MISTAKE)
> adb shell
# cd /data/local/tmp
# ./misc_version -s 1.00.000.0
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
# ./flashgc
Click to expand...
Click to collapse
Click to expand...
Click to collapse
From what I gathered on your post, I am thinking you did a pastebin which is good. If you did, and it copied straight from you command prompt, than you are missing an (*) at the end of the adb chmod 777 /data/local/tmp/.
I recently used the guide to downgrade/root/flash e-bootloader/flash rom on 2 brand new 2.3.4 mytouch 4gs 2 weeks ago.
Also if you can manage to safe some time and headache reformat your SD card with the PD15IMG on to to fat32. If you dont you have a very likely chance that when you attempt to flash the PD15IMG to get a no image or bad image error in your bootloader when downgrading.
Slow down, step away from the computer, take a break and come back and START OVER. I spent 2 days getting that damned error on the pd15img.
edit:The quoted text is from the downgrading guide.

thank you for responding but that link you sent me shows up as a dead link, didnt go anywhere bro

michael.racelli said:
thank you for responding but that link you sent me shows up as a dead link, didnt go anywhere bro
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=15851661
This is the downgrading guide that I believe you have been using. Its the same I used. Like I said start over, and make sure every line in your cmd is typed exactly the way it is written in the thread.
If you feel you must, you can even copy and paste line by line into command prompt

Heh, sorry. Here you are! http://forum.xda-developers.com/showthread.php?p=21563546

hellmonger said:
no need to downgrade
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
Hellmonger, I never got superoneclick to work on 2.3.4 mytouch 4g. Tried it and it gets stuck on the psneuter
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
invasion2 said:
Heh, sorry. Here you are! http://forum.xda-developers.com/showthread.php?p=21563546
Click to expand...
Click to collapse
This is for the desire/g2 it wont work. Use the link I posted.

. . .
knew someone was gonna take me the wrong way. deleted.
seeing from what other users have posted, it seems that you have "unlocked" your bootloader the Official HTC way. then there's not much anyone here can do for you, since that way wasn't recommended anyway.
but since your bootloader is now "unlocked", i don't see why you need to follow the downgrade procedure anymore. from looking at other device forums, i see that all you gotta do is get a custom recovery on there somehow, flash a rooted ROM, flash the boot image of that ROM (since you decided to do it the HTC way) and that's pretty much it...
Contacting a mod at once...

^^^^^^^ I did the same -______-

Someone please HELPP! Before...

Okay...so here Iam once more driving myself insane. I'am pretty intermediate with devices and rooting and can usually do things solo or with slight help...but!!. So just received the device from a friend of mine and I actually want to unlock it to allow Simple Mobile (sim card) and services...when i Hboot it says Radio ON...to what i presume will be the freedom I need. Okay so here goes my trouble... I know that your supposed to downgrade the device to root, or temp root, I have been following the instructions to the T (or at least I'm hoping so) on http://forum.gsmhosting.com/vbb/f62...ouch-4g-2-3-4-hb-0-89-0005-stock-rom-1344617/ and even on this site which is where i also have tried following the directions. Okay so what confuses me is that one post says tools, the other says platform-tools..and if i'm incorrect the directory has both. Okay so I've opened up a command line from both and it's around
$ adb push fre3vo /sdcard/fre3vo
$ adb shell
$ chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
that I start to have my trouble!! I was actually able to copy this...
C:\AndroidSdk\platform-tools> adb push fre3vo /sdcard/fre3vo
adb server is out of date. killing...
* daemon started successfully *
cannot stat 'fre3vo': No such file or directory <---is this the error file im supposed to get?? so I rewrite it connecting the sdcard to fre3vo and then wallah!! A whole bunch of writing like ...
C:\AndroidSdk\platform-tools> adb push fre3vo/sdcard/fre3vo
Android Debug Bridge version 1.0.31 <------------------------Right over here (excessive content so i deleted)
C:\AndroidSdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
Unable to chmod /data/local/tmp/fre3vo: No such file or directory
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo: not found <---------------------------So I go down through the line of codes I'm supposed to trty and all say not found
$
Now as you can see this is where my problems arise. Every code or set of codes I get result in not found?? What am I doing wrong? I saw a tutorial on youtube and when he added this coding it was immediately followed by a massive amount of writing and then ADB seems to have shut down...Am i supposed to have ADB running while I do this? I've even tried rewriting the codes thinking that maybe a space was misplaced or such. Please help guys. Also what I did was manually created a directory at C;\Adroidsdk since there was none and placed all of the adb tools there or hope I did. Before that every time I'd open the executable the adb program would open from C\users\appdata\local\temp. I honestly don't know where i went wrong. I really want to root this phone. I went as far as spending 30 dollars on one of those bogus websites that can "root your device guaranteed" only to find that the programs they had like Superoneclick I already had on my desktop. Go figure..Ok I will sit here miserably until one of you rescues me. Thanks.

Some people said they used this tool to root.
http://forum.xda-developers.com/showthread.php?t=1870652
I personally have not tried it, but hey, you never know

Did you unzip the files before putting them in platform tools?
Also shouldn't you be pushing the file to the folder you are trying to chmod? It looks like you are pushing it to sdcard and I'm pretty sure it needs to be in the tmp folder:
adb push fre3vo /data/local/tmp
Instead of sdcard, but don't quote me on that I haven't done this in ages. Trying it *shouldn't* break anything... I think
If you can't push it to tmp then you are missing steps.
Edit:
Found an xda thread that verifies the file should be pushed to data local tmp
http://forum.xda-developers.com/showthread.php?t=1178912
Shame on the person who wrote the other guide.

If u already got s-off (cuz u might have to downgrade) or still in fryo u can try vissionary+ method efficient stressless

N_otori0us_ said:
Some people said they used this tool to root.
http://forum.xda-developers.com/showthread.php?t=1870652
I personally have not tried it, but hey, you never know
Click to expand...
Click to collapse
yeAh this is one of the tools the $30 dollar spot gave me. Funny because it actually says it worked..Su installed Busybox installed and once process is done..Nada..zip..is still the same now to convince them of a refund.

Relsig said:
Did you unzip the files before putting them in platform tools?
Also shouldn't you be pushing the file to the folder you are trying to chmod? It looks like you are pushing it to sdcard and I'm pretty sure it needs to be in the tmp folder:
adb push fre3vo /data/local/tmp
Instead of sdcard, but don't quote me on that I haven't done this in ages. Trying it *shouldn't* break anything... I think
If you can't push it to tmp then you are missing steps.
Edit:
Found an xda thread that verifies the file should be pushed to data local tmp
http://forum.xda-developers.com/showthread.php?t=1178912
Shame on the person who wrote the other guide.
Click to expand...
Click to collapse
Yeah, I've actually tried it this way and the other. the thing is one site says tools..the other platform tools, and then this last one sd card?? I've tried them all I think...Maybe my adb is installed in the wrong area? could that be why possibly after i chmod and start putting in the files to finally root the phone it says "file not found"? I know it's alot of writing but I'm going to copy and paste everything on a new reply to see if you or anyone can see what I'm doing wrong. I even copy and paste to the cmd and nothing.

ughoji said:
If u already got s-off (cuz u might have to downgrade) or still in fryo u can try vissionary+ method efficient stressless
Click to expand...
Click to collapse
If you could find me a place to download visionary from I'd be eternally grateful to you. It seems when they banned the app from google they must've done so everywhere else. Everytime I try to download my PC stops the download and says virus detected even with anti-virus off. Every time I go to the Visionary website and click the download link it takes me to some bogus website and never to the download link. The other sites I've found them on them on the PC says Virus detected...or maybe it's google chrome. Think I should try downloading on Internet Explorer?

what i'm gonna do guys is try the process from the xda website and then post it to see if one of you detect where I went wrong. Crossing Fingers...

now here it is ladies and gents...maybe we can find the problem here somewhere
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Jorge>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\Users\Jorge>cd c:\androidsdk\platform-tools
c:\AndroidSdk\platform-tools>adb push fre3vo /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
cannot stat 'fre3vo': No such file or directory <-- here also i get the no file or directory error so then i rewrite putting fre3vo and data together which follows with fre3vo/data
c:\AndroidSdk\platform-tools>adb push fre3vo/data/local/tmp
Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
c:\AndroidSdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
Unable to chmod /data/local/tmp/fre3vo: No such file or directory <--when i input chmod 777 /data/local/tmp/fre3vo it says no such file...so i
$ chmod 777/data/local/tmp/fre3vo rewrite it and connect the 777 to data like chmod 777/data and then
chmod 777/data/local/tmp/fre3vo the usahe chmod ...etc.
Usage: chmod <MODE> <FILE>
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo: not found
$ <-----I can continue and write the other passwords but it says not found.
I'm wondering if i might've installed adb in the wrong place and if so how do i change the variables? should i put C:android or as currently ANDROID_SDK_HOME then C:\AndroidSdk

There's no wrong place to install adb. If your in GingerBread, I don't think visionary will work. Try ginger break. But you have to downgrade to root your phone. If your on 2.3.4, you gotta get on 2.2.1 I think
Sent from my myTouch 4G using xda app-developers app

N_otori0us_ said:
There's no wrong place to install adb. If your in GingerBread, I don't think visionary will work. Try ginger break. But you have to downgrade to root your phone. If your on 2.3.4, you gotta get on 2.2.1 I think
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
yeA
YEAH PHONE IS ON 2.3.4...ooops sorry for caps! so can you see where i might've went wrong? I mean is it supposed to say file not found or those things? somewhere i messed up..sigh...

c:\AndroidSdk\platform-tools>adb push fre3vo /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
cannot stat 'fre3vo': No such file or directory
Is fre3vo in C:\AndroidSdk\platform-tools?
cause thats where you need to unzip the files to
-Nipqer

Found the problem...
Thanks to you guys I went back step by step and figured out the problem . So apparently when i had originally downloaded the fre3vo and misc files they were the wrong files. I looked inside of platform tools and both files were there as applications?? yeah like actual install type applications..finally it has all seemed to work so i'll now move on to step two...won't say im done till ive succesfully rooted and ill keep you posted but thank you guys.,.for your time and dedication towards helping me :_)

Playdoe said:
Thanks to you guys I went back step by step and figured out the problem . So apparently when i had originally downloaded the fre3vo and misc files they were the wrong files. I looked inside of platform tools and both files were there as applications?? yeah like actual install type applications..finally it has all seemed to work so i'll now move on to step two...won't say im done till ive succesfully rooted and ill keep you posted but thank you guys.,.for your time and dedication towards helping me :_)
Click to expand...
Click to collapse
Just in case u wanted to root an s-off phone search pd15img(2.2.1).zip got mine from 4shared rename it to pd15img.zip and move it to root of your SD card boot into bootloader navigate to the second option then OK with power on to downgrade. here is a working visionary but note most cases play store doesn't agree to download make sure u got explore or es in another phone to send it run your rooting and every.the visionary process is in the dev part its pinned

I used visionary and it worked for me