I tried to root my Desire Z running Andorid 2.2.1 by following guide on Cyanogen wiki.
Since my software version is 1.82.405.1 I had to downgrade it first. I gained temporary root but when I reboot to bootloader and try to flash PC10IMG.zip it start loading but It fails when cheking file. I'm sure I downloaded it correctly because I checked md5. What am I doing wrong, or have I missed something?
Try fastboot, very easy (just rename the file,look at the wiki)! It's really easy, I downgraded and rooted in about one hour.
I also have problems with downgrading. I'm currently using stock 2.3.4 on my G2. When I try to downgrade it to 1.19.531.1 using the guide from CyanogenMod Wiki I face a problem. When I insert this line "/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF" into cmd it says: "/data/local/tmp/fre3vo: not found"
How can I fix this?
...follow this guide (temp root & downgrade):
http://forum.xda-developers.com/showthread.php?t=1178912
...for perm root use the wiki:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
EDIT: @kepos: you may need a goldcard / @Isstatu1: you first need to push fre3vo to data/... and then chmod 777 it...
I push the fre3vo and it shows a lot of text in cmd. then I write "adb shell", everything works, the $ sign appear, then I write the "chmod 777 /data/local/tmp/fre3vo" part, it says: "Usage: chmod <MODE><FILE>". After that i write "/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF" and it says that fre3vo is not found..
Isstatu1 said:
I push the fre3vo and it shows a lot of text in cmd. then I write "adb shell", everything works, the $ sign appear, then I write the "chmod 777 /data/local/tmp/fre3vo" part, it says: "Usage: chmod <MODE><FILE>". After that i write "/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF" and it says that fre3vo is not found..
Click to expand...
Click to collapse
If you type adb devices, your device is listed?
What does it show if you push fre3vo? ...because as far as i remember it should only show you how long it took to push
Yes it shows my device.
Now, when I type "> adb shell cat /dev/msm_rotator"
it shows
/dev/msm_rotator: not found"
Nvm the underline part, it works now. But still having problems with fre3vo..
Can I PM you?
Isstatu1 said:
Yes it shows my device.
Now, when I type "> adb shell cat /dev/msm_rotator"
it shows
/dev/msm_rotator: not found"
Nvm the underline part, it works now. But still having problems with fre3vo..
Can I PM you?
Click to expand...
Click to collapse
sure you can
EDIT: where did you put the fre3vo file on your pc? because either you have to put the files you want to push directly into the adb tool folder or you have to tell adb where it is...
Related
okay i'm following these steps, and once i get to adb shell su cd /data/local
Code:
cd\
cd c:\AndroidSDK\Tools
adb devices (A serial number should pop up saying your phone can be seen by ADB, if so continue typing the following with hitting enter at the end of each line)
adb push flash_image /data/local
adb push mtd0.img /data/local (that is a zero, not an oh in “mt0.img”)
adb shell su cd /data/local
chmod 04755 *
/data/local/flash_image misc /data/local/mtd0.img (again that is a zero, not an oh in “mt0.img”)
it tells me permission denied... i have full root, and am able to su and get #... im stuck at this part and don't know what to do, i've searched and can't find an answer.
Please help!
Are you sure that adb push actually pushed the files?
Did you get a confirmation?
Faud said:
Im blind..one sec
Click to expand...
Click to collapse
ummm okay.....
I am trying to unroot my g2 in order to send it in. I used gfree method on Wiki to root the phone and to unroot it. However, I am stuck trying to turn s-on. When I enter:
$ adb shell /data/local/tmp/psneuter
I am getting:
/data/local/tmp/psneuter: permission denied
Any ideas?
I believe you have to do "chmod 755 /data/local/tmp/psneuter" on it (I'm not -too- sure on the numbers, but I think it's 755)
EDIT: chmod 777, my bad - thanks posters below
Well the steps from the wiki are:
$ adb push psneuter /data/local/tmp/psneuter
$ adb shell chmod 777 /data/local/tmp/psneuter
$ adb shell /data/local/tmp/psneuter
$ adb shell
It's the 3rd one that I am stuck on.
Since I am unable to get temp root following the wiki, would I be able to use visionary to get temp root and then s-on following the wiki?
flat4grl said:
Since I am unable to get temp root following the wiki, would I be able to use visionary to get temp root and then s-on following the wiki?
Click to expand...
Click to collapse
Hi !
Are you sure that you got a valid copy of psneuter?
Try to download the zip from psneuter.zip unpack it and try it again with the file that is called psneuter in it.
have fun - Guhl
Thanks for the help! Unfortunately that didn't work either. Not sure whats going on, but I think it's something with the phone. I just cannot figure it out. At least it works for now.
Type:
1)adb shell
***you should see the '$' symbol (if you have '#', then do nothing, you're already root)
2)chmod 777 /data/local/tmp/psneuter
3)/data/local/tmp/psneuter
4)exit
5)adb shell
6)su
If you have the '#', then you're root
I don't know if this will work, but this is not dangerous at all to try
Max) said:
Type:
1)adb shell
***you should see the '$' symbol (if you have '#', then do nothing, you're already root)
2)chmod 777 /data/local/tmp/psneuter
3)/data/local/tmp/psneuter
4)exit
5)adb shell
6)su
If you have the '#', then you're root
I don't know if this will work, but this is not dangerous at all to try
Click to expand...
Click to collapse
Thanks you for trying to help! When I got to the third step it told me permission denied again.
I was able to FINALLY get s-on. I thought I would post how I did just in case anyone else ends up having this problem.
I used visionary to temp root my phone and then used the wiki to turn s-on. Only problem I had was trying to remove the psneuter file from the phone. Other than that no problems. Now I shall see if I can get away with sending the phone in.
Hello.
I've tried to root my Desire Z. I wanted to achieve only the ROOT not S-off and so on. Just to be able to use some root requiring applications like DSP Manager or Adds free.
1. So I've downloaded and installed Android SDK.
2. Started ADB
3. "adb devices" gave me the proper answer
4. Then I've copied and started psneuter and misc_vesion:
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
/data/local/tmp/misc_version -s 1.33.405.5
exit
5. Then I've tried to root the phone:
Ive copied the required files:
adb install AndroidTerm.apk
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push rage /data/local/tmp
adb push root /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*
adb push su /sdcard/
adb push Superuser.apk /sdcard/
And then from the Terminal Emulator I've entered
/data/local/tmp/root
I've got some messages that the everything is read only so I've tried rage first:
/data/local/tmp/rage
I've got the proper "Forked #### childs" output
and then I've tried the "/data/local/tmp/root" again. But I'm getting the "cannot fork" message.
I'm new in this stuff s please help me. What do I do wrong?
I only want the simple root access I don't want to downgrade my phone and install any custom roms.
Please help.
ps. my "compilation number" is: 1.72.405
As far as I remember your supposed to flash 1.34 Rom after changing the version number to 1.33 as the rooting is only possible via 1.34 Rom and not 1.72 Rom .... And you clearly missed that step .... Open desire z wiki and read the psneuter guide ... Follow it word for word .... You will root your phone
Maxymo123 said:
Hello.
I've tried to root my Desire Z. I wanted to achieve only the ROOT not S-off and so on. Just to be able to use some root requiring applications like DSP Manager or Adds free.
1. So I've downloaded and installed Android SDK.
2. Started ADB
3. "adb devices" gave me the proper answer
4. Then I've copied and started psneuter and misc_vesion:
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
/data/local/tmp/misc_version -s 1.33.405.5
exit
5. Then I've tried to root the phone:
Ive copied the required files:
adb install AndroidTerm.apk
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push rage /data/local/tmp
adb push root /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*
adb push su /sdcard/
adb push Superuser.apk /sdcard/
And then from the Terminal Emulator I've entered
/data/local/tmp/root
I've got some messages that the everything is read only so I've tried rage first:
/data/local/tmp/rage
I've got the proper "Forked #### childs" output
and then I've tried the "/data/local/tmp/root" again. But I'm getting the "cannot fork" message.
I'm new in this stuff s please help me. What do I do wrong?
I only want the simple root access I don't want to downgrade my phone and install any custom roms.
Please help.
ps. my "compilation number" is: 1.72.405
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Just out of curiosity, if you only want to root to use some applications and such, why don't you just temp root using visionary and just redo it whenever you restart your phone?
Thanks for the answers guys.
your supposed to flash 1.34 Rom after changing the version number to 1.33
Click to expand...
Click to collapse
hispeedworm - I don't want to downgrade my phone. I don't need it and I don't want to loose whole the settings and apps and start from the beginning just for using some special apps.
mmduluth - I've used the visionary method from this topic while it seemed the easiest one for the beginner. However after taping the "TempRoot Now!" the VISIONary+ seemed to hang. The screen was black for several minutes.
So I've decided it does not work.
Anyway, I'd prefer to have permanent root than a temp one for example for using "autostarts" - which as far as I'm concerned works AFTER rebooting the phone.
So anyone could tell me where is a mistake in what I did?
I suppose I've omitted one thing in former trials so I've tried to root it again.
After entering the Terminal Emulator I've run rage:
/data/local/tmp/rage
I've got the Forked #### childs message so everything was ok till then.
Then I've reset terminal --> menu-->reset term
And then I've run the terminal again.
I should get the # sign but what I get is the totally white screen with no possibility to write any command. It's not responding. I can only get out from it by pressing the home button.
So what's going wrong?
Maxymo123 said:
I suppose I've omitted one thing in former trials so I've tried to root it again.
After entering the Terminal Emulator I've run rage:
/data/local/tmp/rage
I've got the Forked #### childs message so everything was ok till then.
Then I've reset terminal --> menu-->reset term
And then I've run the terminal again.
I should get the # sign but what I get is the totally white screen with no possibility to write any command. It's not responding. I can only get out from it by pressing the home button.
So what's going wrong?
Click to expand...
Click to collapse
If you read enough threads/post, at the moment, the only way to gain permaroot is to downgrade your ROM. Unless, somebody finds a way to do it without the need to downgrade.
And, as I understand, using Visionary apps would cause damage to your device. Be careful!
Cheers...
Thank you silverwind. Now it's clear.
So anyone is working on this?
Cheers
I am following these steps
http://theunlockr.com/2011/07/22/how-to-downgrade-a-gingerbread-t-mobile-g2-so-it-can-be-rooted/
I typed /data/local/tmp/fre3vo -debug -start FBA90000 -end FFFFFFFF
it then says exploiting device and then goes back to C:\androidsdk\tools and I never get the # command prompt. Looking for advice on what to do next.
Thanks in advance.
Did you retry 'adb shell' when it sends you back to C:\androidsdk\tools?
Cause the exploit is meant to kick you out of shell, then you have to go back in it.
-Nipqer
Nipqer said:
Did you retry 'adb shell' when it sends you back to C:\androidsdk\tools?
Cause the exploit is meant to kick you out of shell, then you have to go back in it.
-Nipqer
Click to expand...
Click to collapse
Yes, and I am now following this guide http://forum.xda-developers.com/showthread.php?t=999796 .
Am I ok to proceed even though I am getting permission denied below?
C:\AndroidSDK\tools>adb push hboot_7230_0.76.2000_100820.nb0 /data/local
1709 KB/s (1048576 bytes in 0.599s)
C:\AndroidSDK\tools>adb shell
$ md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum: permission denied
$
obas said:
Yes, and I am now following this guide http://forum.xda-developers.com/showthread.php?t=999796 .
Am I ok to proceed even though I am getting permission denied below?
C:\AndroidSDK\tools>adb push hboot_7230_0.76.2000_100820.nb0 /data/local
1709 KB/s (1048576 bytes in 0.599s)
C:\AndroidSDK\tools>adb shell
$ md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum: permission denied
$
Click to expand...
Click to collapse
i also get this following this guide http://forum.xda-developers.com/showthread.php?t=999796 .
Am I ok to proceed even though I am getting permission denied below?
C:\AndroidSDK\tools>adb push hboot_7230_0.76.2000_100820.nb0 /data/local
1709 KB/s (1048576 bytes in 0.599s)
C:\AndroidSDK\tools>adb shell
$ md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum: permission denied
$
That guide is for removing eng hboot, if you have eng hboot, there would be easier ways to remove it.
You need to get a root shell to proceed.
You could get help faster if you went to the #g2root channel on freenode irc [link]
-Nipqer
Nipqer said:
That guide is for removing eng hboot, if you have eng hboot, there would be easier ways to remove it.
You need to get a root shell to proceed.
You could get help faster if you went to the #g2root channel on freenode irc [link]
-Nipqer
Click to expand...
Click to collapse
I went to that page and got no help . I was wondering if you could look over my steps before I attempt this any further, does this look like it will work.
C:\AndroidSDK\tools>adb push fre3vo /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
956 KB/s (9796 bytes in 0.010s)
C:\AndroidSDK\tools>adb push misc_version /data/local/tmp/misc_version
1405 KB/s (15837 bytes in 0.011s)
C:\AndroidSDK\tools>adb shell chmod 777 /data/local/tmp/fre3vo
C:\AndroidSDK\tools>adb shell chmod 777 /data/local/tmp/misc_version
C:\AndroidSDK\tools> /data/local/tmp/fre3vo -debug -start FBA90000 -end FFFFFFFF
---- Also if the above process looks good can my next command be the following
$ adb push PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b _26.02.01.15_M2_release_149459_signed.zip /sdcard/PC10IMG.zip ????
Yeah should be working.
If no one responds immediatly in irc just wait a bit. It's not the most active channel, but someone will come along to help.
I'm not sure why it's not working for you.
-Nipqer
Nipqer said:
Yeah should be working.
If no one responds immediatly in irc just wait a bit. It's not the most active channel, but someone will come along to help.
I'm not sure why it's not working for you.
-Nipqer
Click to expand...
Click to collapse
Actually everything worked up till this command
$ adb push PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip /sdcard/PC10IMG.zip
when I did that it said "file not found" I do believe. So I then tried $ adb push PC10IMG.zip /sdcard/PC10IMG.zip and I got the same error.
I have both the PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip and PC10IMG.zip in the androidsdk\tools folder so this should work right? not sure why I am getting file not found.
Thanks for all you help also I am also there I can feel it
You can use the TAB key to auto-complete file names, so you can make sure you're not misspelling anything.
Make sure the adb push command is done in a C:\> prompt, not $/# (push before adb shell)
-Nipqer
Nipqer said:
You can use the TAB key to auto-complete file names, so you can make sure you're not misspelling anything.
Make sure the adb push command is done in a C:\> prompt, not $/# (push before adb shell)
-Nipqer
Click to expand...
Click to collapse
Ok, now I'm confused because this link http://forum.xda-developers.com/showthread.php?t=1178912 has this command under the "downgrade" section.
$ adb push PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip /sdcard/PC10IMG.zip
$ adb reboot bootloader
That seems to me they are saying to do adb push from the $ command.
I'm trying to root my Bell HTC Desire Z and I'm getting stuck pretty early just trying to downgrade to Froyo.
No matter what guide I've followed this is far as I'll get typing in the terminal:
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell
chmod 777 /data/local/tmp/fre3vo
I'll then get a response saying unable to chmod /data/local/tmp/fre3vo: no such file or directory.
I've placed the fre3vo file in the same folder as adb so I'm super confused.
Any help would be super appreciated!
edit you first post and change the title of the post... it will change the title of the thread's name too
Now, I'm making even less progress.
adb push fre3vo /data/local/tmp
turns back with:
cannot stat 'fre3vo': No such file or directory
That error means fre3vo is not in the directory cmd/terminal is pointed at.
You need to either use the 'cd' command (change dir) or, if you're on windows, you can hold shift and right click in the dir fre3vo is, and select 'open cmd here'
-Nipqer
Alright, so I'm having slightly more luck following this guide http://forum.xda-developers.com/showthread.php?t=1178912&highlight=root+bell+desire+z
I've got to the portion about "Changing Version Number to Allow Downgrade and Gaining SuperCID with a Goldcard" but when I type:
# cd /data/local/tmp
I get cd /data/local/tmp: not found
I thought I was making progress...
EDIT: Never mind - I just decided to re-type the command in and it worked...moving on to downgrading
Success! Rooted my phone and flashed CM 7.2. Big thanks to Nipqer on #G2Root!!!!
Mods this thread could probably be deleted.
I am stuck on the same spot the OP was. I have done as nipqer suggested and opened a cmd window directly in the platform-tools folder and now the response coming back is
Code:
C:\platform-tools>adb shell
$ chmod 777/data/local/tmp/fre3vo
chmod 777/data/local/tmp/fre3vo
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: permission denied
suggestions ?
I have read a lot of threads and tutorials on this and honestly there's so many it has become confusing. Help a fella out! :good:
follow this guide first
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Firmware_Downgrade_(Gingerbread)
now go to this guide when complete
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Rooting
dont skip steps and if you need more help log onto freenode
You ran the chmod command wrong, didn't put a space between the 777 and the /data/local/tmp/fre3vo
-Nipqer
righto, thanks guys, will take a look at the threads you linked and try again. will post back one way or the other as soon as I have something.
ok I have run into a real problem. it looks as if I have semi bricked. I skipped nothing, followed the guide to a T.
Code:
NOTE: Take note of this number, we will need it later. For the remainder of this guide, we will refer to this number md5 #3.
If md5 #1 & md5 #3 match, then gfree 0.7 failed to powercycle the eMMC chip on the device. Either the software version is too high and the device was not downgraded per the previous section, or you did something wrong. Try again or join #G2Root on Freenode for further help..
If md5 #2 & md5 #3 match, then everything should be fine and you continue on.
Code:
md5 #1 - b532ca54a073f0c4043bd7be69ebce8d
md5#2 - 2ce1bdd5e4c1119ccfcecb938710d742
md5#3 - 2ce1bdd5e4c1119ccfcecb938710d742
as you can see they match so reboot command should have been fine but all O get now is hanging at the HTC screen, unless I reboot holding the volume down button then that takes me to hboot screen. What do I do?
UPDATE - As I worked out how to use clockwork I realized I had s-off so I downloaded CM7 and followed the instructions on wiping cache and what not then installed. All seems to be working now.
Thank you.
for future reference these is very common when switching hboots (part of the rooting process) you will not be able to boot into your previous rom as partition checks will have changed. when you have completed rooting you should either boot into fastboot or recovery to flash rom of choice
Sent from my HTC Vision using xda premium