Downgrade help - G2 and Desire Z Q&A, Help & Troubleshooting

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.

Related

flashing new rom issue please help

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.....

[Q] Please help with Rage Temproot during Gfree root process

Please help, I've searched around and can't find the solution to my issue, I'm rooting following the XDA wiki for Gfree and using the Android SDK....I've managed to get the ADB to recognize my phone and I "think" that the ADB has been able to push the first 5 files to the SD....but I'm stuck on the last command line.
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
when I run $ adb shell chmod 0755 /data/local/tmp/*
I get the following:
Usage: chmod <MODE> <File>
so then I go to terminal emulator on the phone and type
$ /data/local/tmp/rage
I get: /data/local/tmp/rage: not found
Where have I screwed up?
G2_Gordon_G1 said:
Please help, I've searched around and can't find the solution to my issue, I'm rooting following the XDA wiki for Gfree and using the Android SDK....I've managed to get the ADB to recognize my phone and I "think" that the ADB has been able to push the first 5 files to the SD....but I'm stuck on the last command line.
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
when I run $ adb shell chmod 0755 /data/local/tmp/*
I get the following:
Usage: chmod <MODE> <File>
so then I go to terminal emulator on the phone and type
$ /data/local/tmp/rage
I get: /data/local/tmp/rage: not found
Where have I screwed up?
Click to expand...
Click to collapse
looks like you screwed up the last command ... didnt write the syntax properly thats why it showed its usage.....
(adb shell chmod 0755 /data/local/tmp/*) this command that is.....
also the last thing showing file not found means the files were never pushed to the phone..... connect your phone to your pc in chagre only and usb debigging connected mode and in command prompt in the adb folder write "adb devices"
it should show somehting like this.....
adb list of devices attached
SH034N34GF
this number over here (SH034N34GF) is an example ... it will show your phone ID... which would be different....
if you see list of devices attached and an empty line below and no serial number as shown in example....
than it means your android usb drivers for adb shell are not set up correctly
in that case ... get the drivers set up properly....
check with adb devices command to confirm your phone is recognized....
than start over with the commands
I've started over and have typed VERY CAREFULLY...
On each of the first five command prompts I get a 40 or so line message that starts with:
Android Debug Bridge version 1.0.26
.......
(list of commands)
.......
and ends with
bug tags are printed.
OK so I guess that's good
So then I type C:\> adb shell chmod 0755 /data/local/tmp/*
and NOW I get
adb server is out of date. killing...
*daemon started successfully*
Bad Mode
Clearly, I'm a noob.....
Now what?
read this guide .... on it search for .... "out of date" author explains how to tackle it
G2_Gordon_G1 said:
I've started over and have typed VERY CAREFULLY...
On each of the first five command prompts I get a 40 or so line message that starts with:
Android Debug Bridge version 1.0.26
.......
(list of commands)
.......
and ends with
bug tags are printed.
OK so I guess that's good
So then I type C:\> adb shell chmod 0755 /data/local/tmp/*
and NOW I get
adb server is out of date. killing...
*daemon started successfully*
Bad Mode
Clearly, I'm a noob.....
Now what?
Click to expand...
Click to collapse
hispeedworm said:
read this guide .... on it search for .... "out of date" author explains how to tackle it
Click to expand...
Click to collapse
In the ADB guide it says:
"By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output."
So apparently that's not a problem?
G2_Gordon_G1 said:
In the ADB guide it says:
"By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output."
So apparently that's not a problem?
Click to expand...
Click to collapse
im uploading my adb... its minimal with just adb fastboot and few other files.... unzip into a folder on your pc.....use these instead of the android sdk and all..
make sure that folder is linked in windows..... Step 4 of the adb for noobs guide..... reinstall the android usb drivers again following the guide.....
when thats done restart and press F8 ... disable signature verification ... when windows loaded... go to command prompt.... do into the adb directory.....than write adb devices....if it shows you device than start over with the commands.... you should not get the error saying out of date... as i just used this adb shell 2 days back to root my desire Z.....
hope this helps
Thanks! Will try again soon!

[Q] problem downgrading my DHD(1.84)

this is the error i m facing(in bold):
E:\Setup\android\root\Downgrade>adb push misc_version /data/local/tmp
1104 KB/s (15837 bytes in 0.014s)
E:\Setup\android\root\Downgrade>adb shell chmod 777 /data/local/tmp/psneuter
E:\Setup\android\root\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
E:\Setup\android\root\Downgrade>adb shell /data/local/tmp/psneuter
mmap() failed. Operation not permitted
what should i do?
Well you did not push psneuter there, so you cannot run it You just pushed misc_version.
jkoljo said:
Well you did not push psneuter there, so you cannot run it You just pushed misc_version.
Click to expand...
Click to collapse
i did it its just that i missed it while copying the the text from cmd. here it is:
e:\Setup\android\root\Downgrade>adb push psneuter /data/local/tmp
1661 KB/s (557962 bytes in 0.328s)
e:\Setup\android\root\Downgrade>adb push misc_version /data/local/tmp
1189 KB/s (15837 bytes in 0.013s)
e:\Setup\android\root\Downgrade>adb shell chmod 777 /data/local/tmp/psneuter
e:\Setup\android\root\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
e:\Setup\android\root\Downgrade>adb shell /data/local/tmp/psneuter
mmap() failed. Operation not permitted
phone connected to Windows7 in charge only mode with usb debugging enabled.
hey,
I am facing the exact same problem, I live in India and my DHD isn't carrier branded or anything.
Earlier when i tried to downgrade, I was getting CID failed...so i did a goldcard and now I am getting the exact same error as mentioned above...can anyone plz help?
Yea, i got that error when i was trying to downgrade too, just a week ago!
my phone was branded, and when i didn't do the GoldCard, i didn't get the error.
but as soon as i did the goldcard, then the error came twice.
what i did was restart the phone, the computer and formatted the SD card and did the whole process again, then i typed
>adb shell /data/local/tmp/psneuter
and i got the error again. I waited like 3-6 seconds and tried the above command again, and it worked.
honestly, i dont know where the problem comes from. but good luck
wrong n missing image files error in bootloader
after the temp root.. when it goes in bootloader , it does say that the image files are missing and wrong image file…
m running on htc desire hd 1.84 stock rom unlocked.
please help me out

[Q] Turning S-on help

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.

[Q] downgrade problem

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...

Categories

Resources