Related
Ok, so i was creating a bash profile following a tutorial to use ADB through terminal
- Download the Android SDK for Macintosh at: Android SDK | Android Developers
- Extract it
- Download Fastboot for OSX (If not included with SDK)
- Extract fastboot and place it in your /tools folder.
- Open up a terminal window
- type: pico .bash_profile (this will create a .bash_profile)
- type the following in the new screen: export PATH=$
{PATH}:<sdkfolder>/tools
- Hit CNTRL + X
- Hit Y (for yes to save)
- It will return you to the terminal screen… type: exit
- Restart terminal.
Click to expand...
Click to collapse
it worked the first time, but i just tried opening terminal again and it wouldn't work, so i started doing it again and i got to where i type export path=$ etc etc. now i screwed up and terminal thought my android SDK was in /users/myname/sdkfolder and not users/myname/android.....no worries i just renamed android to asdkfolder and all was well....
but now when i open terminal i get
-bash: {PATH}:: command not found
i can type
cd /users/myname/sdkfolder/tools and it will change directories but adb shell or fastboot devices doesn't work.
i'm super confused and i've tried googling solutions and found this thread
http://www.droidforums.net/forum/ha...-changing-path-terminal-new-bash-profile.html
who had a similar problem but i'm still stuck.
Last login: Fri Jul 2 21:51:52
-bash: {PATH}:: command not found
new-host:~ myname$ cd /users/myname/sdkfolder/tools
new-host:tools myname$ adb shell
-bash: adb: command not found
new-host:tools myname$ fastboot devices
-bash: fastboot: command not found
new-host:tools myname$
bump for help
i started off using a bash profile and decided it wasn't necessary. just navigate to the folders you need to via terminal. from what i understand it causes more problem then its worth. i know this doesn't answer any questions just my .02 good luck.
I think the new SDK moves ADB to platform-tools.
So if you installed in folder "SDK" the new path should be...
"export PATH=${PATH}:/SDK/platform-tools"
you have to tell the terminal where to look for the command if it isn't in your profile.
I just navigate to the folder my sdk stuff is in then use a ./ infront of the command
Example
./adb shell instead of adb shell
OK...I'm beginning to think that rooting is not for me!!!! Getting a bit frustrated!!!
OK, so I installed SDK on my pc (Win XP Ver 2002 SP3), and I cannot get it recognize the device.
I tried the guide for dummies here on XDA, and I follow all the indications, server starts up, I can kill it too....but every time I try to run it I get:
"error: device cannot be found"
The line that I am writing is as follows:
Code:
c:\android-sdk-windows\tools>adb shell
and I get the error above.
When I try to see if devices are connected, and Use this:
Code:
c:\android-sdk-windows\tools>adb devices
I get:
"List of Devices attached", but there is no list!!!!!
But I can see the SDCARD from my computer....I can access the files...
Maybe I can try to pull instead of push, but I'm not sure how that would be written (line wise), not if will work.
BTW...I have never done anything like this on android....very new to this!!!!
umm.. HELP!!!
OK changed pc's,....on this one it does recognize the device, but does not allow me to push anything.....when i try:
Code:
adb push su /sdcard/su
I get adb: permissions denied
------
I tried su +, and that got me to the # prompt. So I tried typing
Code:
# adb push su /sdcard/su
and I get adb: not found???
Running out of options here!
...
Thanks!
I think you are mounting the sdcard. You don't want to do that. Just connect your phone to the computer and run ADB. Don't click "USB Connected. Select to copy files to/from your computer" on your phone.
funkeee said:
I think you are mounting the sdcard. You don't want to do that. Just connect your phone to the computer and run ADB. Don't click "USB Connected. Select to copy files to/from your computer" on your phone.
Click to expand...
Click to collapse
Funkeeeeeee thank you for the reply.
OK...I am not getting an option when I connect to the pc..on the one I get it, I shose do nothing. I have also disabled mass storage on the device once loaded, adn I get the same error. Here is some of the code that I get thorught the PC's terminal:
C:\>cd android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT09YR200737 device
C:\android-sdk-windows\tools>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
$ adb kill-server
adb kill-server
adb: permission denied
$
Click to expand...
Click to collapse
Notice that once I get the initial permission denied, the terminal seems to get locked up on that no matter what I type....see above...
Anything else to try??? AM I missing something here?
That's fine. There are a few things I can suggest for you to try..
First, I want you to enable USB debugging on your phone by going to Settings > Applications > Development and check that first option.
Then connect the phonoe, but don't use 'adb shell' before pushing files. It should look like this:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Funkz>cd c:\g2
c:\g2>adb pull /system/build.prop
501 KB/s (3596 bytes in 0.007s)
c:\g2>
Click to expand...
Click to collapse
If you are trying to run it from within adb shell, it will spit back 'adb: not found.' That should do fix it for you.
If it does not, go to Control Panel > System > Advanced > Environment Variables. Then click on Path and Edit, then ";C:\android-sdk-windows\tools\" at the very end and try again.
By the way, you don't have to run adb from the installation directory. After adding the path I just mentioned, you should be able to run it from anywhere.
funkeee said:
That's fine. There are a few things I can suggest for you to try..
First, I want you to enable USB debugging on your phone by going to Settings > Applications > Development and check that first option.
Then connect the phonoe, but don't use 'adb shell' before pushing files. It should look like this:
If you are trying to run it from within adb shell, it will spit back 'adb: not found.' That should do fix it for you.
If it does not, go to Control Panel > System > Advanced > Environment Variables. Then click on Path and Edit, then ";C:\android-sdk-windows\tools\" at the very end and try again.
By the way, you don't have to run adb from the installation directory. After adding the path I just mentioned, you should be able to run it from anywhere.
Click to expand...
Click to collapse
Thanks.....I finally can run it without having to type the entire path!!!! That was great help!!!
AS for the permission denied.....still having that issue! The one thing I didn't understand was when you changed the path to >g2.....what do you mean???? path to be g2?
Thanks again for the help!
Just a note...I am trying to do this post OTA, which I downloaded, never got the push...Would having the OTA have any effect on this? DO I need to consider reverting to stock and trying from there? If so how? run recovery?
Dude thanks for the help!
did you try typing SU? IMO you cant tamper with ADB Shell if you dont have su access so try typing down SU to ask for permission.
Alright first things first. ADB requires special drivers to work. Which is probably why it didn't work on the original PC. If you download the PDANet client on the PC that you need to do adb it will install the necessary drivers and you can uninstall the program without losing the drivers.
Another ADB requirement is to enable USB Debugging. MENU>Settings>Applications>Development and check the USB Debugging Box.
I don't know about anyone else but with my phone will automount the card. It is recommended to pull down the notification bar and make sure that your SD card isn't mounted.
You need to navigate your command prompt to whatever folder you keep ADB.exe for me
Code:
C:\Users\etnie>cd C:\Users\etnie\Downloads\G2\Android\tools
for me this returns
Code:
C:\Users\etnie\Downloads\G2\Android\tools>
to confirm this
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb devices
I won't post all the code but it should start the daemon successfully and list your device.
to be able to push files to your phone they also need to be in the same folder as the ADB.exe ie the tools folder. of course you can push it from any folder if you type the full path
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb push C:\Users\etnie\Downloads\G2\bootanimation.zip /data/local
the above code would push the bootanimation.zip from my G2 folder located in my Downloads folder to /data/local on the phone. changing the boot screen animation when you turn on the phone. I actually have the BIOS one. Because I am huge nerd lol. Moving on...
I think I covered everything necessary....If you are still having problems either PM me or reply here.
Thanks guys for the replays...here are some comments...
Acid_Wir3 said:
did you try typing SU? IMO you cant tamper with ADB Shell if you dont have su access so try typing down SU to ask for permission.
Click to expand...
Click to collapse
I have tried SU, and it does grant access, BUT!!!! so here is what happens...
I get to .....\tools> adb shell ... then i get.... the $ prompt. At this point I type $su .... then my prompt changes from $ to #. I understand that it should be $ # In any case once I get to # it says adb: not found code looks like this:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ su
su
# adb push su /sdcard/su
adb push su /sdcard/su
adb: not found
#
BTW, the path has been predfined to C:\android-sdk-windows\tools\
Not sure how to navigate from #prompt
RuncaProfundus said:
1Alright first things first. ADB requires special drivers to work. Which is probably why it didn't work on the original PC. If you download the PDANet client on the PC that you need to do adb it will install the necessary drivers and you can uninstall the program without losing the drivers.
2Another ADB requirement is to enable USB Debugging. MENU>Settings>Applications>Development and check the USB Debugging Box.
3I don't know about anyone else but with my phone will automount the card. It is recommended to pull down the notification bar and make sure that your SD card isn't mounted.
4 You need to navigate your command prompt to whatever folder you keep ADB.exe for me
Code:
C:\Users\etnie>cd C:\Users\etnie\Downloads\G2\Android\tools
for me this returns
Code:
C:\Users\etnie\Downloads\G2\Android\tools>
to confirm this
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb devices
I won't post all the code but it should start the daemon successfully and list your device.
to be able to push files to your phone they also need to be in the same folder as the ADB.exe ie the tools folder. of course you can push it from any folder if you type the full path
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb push C:\Users\etnie\Downloads\G2\bootanimation.zip /data/local
the above code would push the bootanimation.zip from my G2 folder located in my Downloads folder to /data/local on the phone. changing the boot screen animation when you turn on the phone. I actually have the BIOS one. Because I am huge nerd lol. Moving on...
I think I covered everything necessary....If you are still having problems either PM me or reply here.
Click to expand...
Click to collapse
Runca thanks for the detailed reply....going in order here:
1 - I did and I still have pdanet isntalled
2 - it's been like that since the first day I got the phone.
3 - How do I ensure??? you are talking about from the phone....I should turn off USB Storage? Will try this one.
UPDATE: tried unmounting and re running without success....
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
$
4 - It's pretty much what I have. Other that I'm not running su before doing so......
Any thoughts?
Crey23 said:
AS for the permission denied.....still having that issue! The one thing I didn't understand was when you changed the path to >g2.....what do you mean???? path to be g2?
Click to expand...
Click to collapse
The "g2> " bit is just his command prompt. He's changed directory to one called "g2" on his phone but that's nothing to do with how adb works etc (just that if he pushes or pulls files then that'll be the current directory on the PC for that).
Crey23 said:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ su
su
# adb push su /sdcard/su
adb push su /sdcard/su
adb: not found
#
Click to expand...
Click to collapse
Those "adb push" commands should be done from your PC's command prompt, not from within an Android shell prompt on your phone.
"adb shell" starts a command shell on the phone. Which is fine for doing some stuff. But "adb" commands won't work because now you're issuing them to your phone, not your PC.
steviewevie said:
Those "adb push" commands should be done from your PC's command prompt, not from within an Android shell prompt on your phone.
"adb shell" starts a command shell on the phone. Which is fine for doing some stuff. But "adb" commands won't work because now you're issuing them to your phone, not your PC.
Click to expand...
Click to collapse
Thanks Steve.....that makes a lot of sense, and in part why i am a bit lost here....but knowing that....how can I get to "push" things to my phone?
Don't run the adb shell command. That takes you into the phone's prompt. Any commands you run from adb shell with $ or # are run within the phone. You want to run adb push from command prompt. Look at my previous post. It should look like:
C:/>adb push ...
not
#adb push...
Sent from my HTC Vision using XDA App
Funkeee,x thank you I will try that as soon as I can.
funkeee said:
Don't run the adb shell command. That takes you into the phone's prompt. Any commands you run from adb shell with $ or # are run within the phone. You want to run adb push from command prompt. Look at my previous post. It should look like:
C:/>adb push ...
not
#adb push...
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
Finally progress
Guys thank you for your help!!!!!
I was finally able to push all the files to the phone. Now my problem has changed..., still dealing with Permission denied....when executing rage I get a buch of errors, please see image:
Code:
$ $su
# /data/local/tmp/rage
I get this.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I then figured that since I was temp rooted through Visionary r10, that was the reason for the errors above. I then proceeded to reboot without temp-rooting.
When I come up to the terminal I get:
Code:
export PATH=/data/local/bin:$PATH
$ $su
su: permission denied
$
SO if I understand this correctly, I need NOT be temp-rooted in order to run rage, but if I'm not temp-rooted, I don't have permissions to get to execute rage....there a chicken and egg story here somewhere! lol
Can I use a hybrid of the visionary temp root and perm root in that post?
From what I recall you need to uninstall visionary and reboot prior to using the rage method.
Sent from my HTC Vision using XDA App
Thanks funkeee...I will try in the morning.
But part of the problem is that without visionary I cannot get su access to run any of this. I'll backup VIS r10 before removing, and try again.
I post my results...goodnight and thanks!
funkeee said:
From what I recall you need to uninstall visionary and reboot prior to using the rage method.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
I looked at the rage instructions and the prompt is misleading. You may forgetting to use chmod to change permssions. I've put my version of the instructions (just the start).
Uninstall visionary, reboot and from command prompt on your pc, navigate to the folder where you have these files and run:
c:/> adb push su /sdcard/su
c:/> adb push Superuser.apk /sdcard/Superuser.apk
c:/> adb push rage /data/local/tmp/rage
c:/> adb push busybox /data/local/tmp/busybox
c:/> adb push root /data/local/tmp/root
c:/> adb shell chmod 0755 /data/local/tmp/*
Don't forget the last entry, which changes the permissions.
Then on your phone, open terminal and put in:
$ /data/local/tmp/rage
It will say Forked Childs...
Then Menu > Reset Term. It will close, then launch terminal again, it will force close and then launch it again and you will have rage root.
If you get to there, you're in good shape. You can then follow those instructions to to push hboot and wpthis. Be careful with the dd command and be sure you have it exactly right. There are no do-overs with 'dd'.
http://forum.xda-developers.com/showthread.php?t=834228
Thanks man I will try it shortly.
funkeee said:
I looked at the rage instructions and the prompt is misleading. You may forgetting to use chmod to change permssions. I've put my version of the instructions (just the start).
Uninstall visionary, reboot and from command prompt on your pc, navigate to the folder where you have these files and run:
c:/> adb push su /sdcard/su
c:/> adb push Superuser.apk /sdcard/Superuser.apk
c:/> adb push rage /data/local/tmp/rage
c:/> adb push busybox /data/local/tmp/busybox
c:/> adb push root /data/local/tmp/root
c:/> adb shell chmod 0755 /data/local/tmp/*
Don't forget the last entry, which changes the permissions.
Click to expand...
Click to collapse
Up to here I am fine.
funkeee said:
Then on your phone, open terminal and put in:
$ /data/local/tmp/rage
It will say Forked Childs...
Then Menu > Reset Term. It will close, then launch terminal again, it will force close and then launch it again and you will have rage root.
If you get to there, you're in good shape. You can then follow those instructions to to push hboot and wpthis. Be careful with the dd command and be sure you have it exactly right. There are no do-overs with 'dd'.
http://forum.xda-developers.com/showthread.php?t=834228
Click to expand...
Click to collapse
But is with this part that I have issues with......
I uninstalled VISONary as suggested, and I got the same result as before.....error, error, error.....permission denied! Basically without visionary and su I cannot get access to the run rage. I gave me this error:
Code:
$ /data/local/tmp/rage
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
mount: Operation not permitted
mkdir failed for /system/xbin, Read-only file system
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
Unable to chmod /system/xbin/busybox: no such file or directory
/data/local/tmp/rage: /data/local/tmp/busybox: not found
cp: Permission denied
cp: Permission denied
Unable to chmod /system/xbin/su: no such file or directory
Mount: Operation not permitted
$
SO as i interpret this as I dont have the rights or permission to run the rage script. What puzzles me is the fact the it cannot "mount" the sdcard...after running this, I cannot take a picture (screenshot) bcs it does not recognize the sdcard. I have to Reboot.
Any ideas?
Thanks!
Crey23 said:
Up to here I am fine.
But is with this part that I have issues with......
Code:
$ /data/local/tmp/rage
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
mount: Operation not permitted
mkdir failed for /system/xbin, Read-only file system
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
Unable to chmod /system/xbin/busybox: no such file or directory
/data/local/tmp/rage: /data/local/tmp/busybox: not found
cp: Permission denied
cp: Permission denied
Unable to chmod /system/xbin/su: no such file or directory
Mount: Operation not permitted
$
Click to expand...
Click to collapse
I think there's something majorly wrong here. Funny, I saw someone else with a similar problem recently. It looks like when you're running "rage" it's actually running the "root" script that you use at a later stage, and not "rage" at all. Double check what you've got, I think "rage" is a binary and not a script. Are you sure you didn't push "root" to "rage" ?
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!
Hi can someone explain to me in nice and easy terms how to downgrade from this user guide please as I have seen a few people asking so it would help them too.
http://forum.xda-developers.com/showthread.php?t=905003
Section 2b [For Gingerbread ROMs, 2.x]
Connect Desire HD to a computer. Charge only, USB Debugging enabled!
Open up a cmd and go to Downgrade folder, execute commands:
Right this is where I get stuck what exactly do you put in the command line in cmd? is the Downgrade folder the PD98IMG.zip file you put on your SD card or what do you actually type?
The PD98IMG.zip file is on my K: drive on the SD card if that's relevant in anyway.
and then after obviously I could then follow on with the next steps of the rest being the following
execute commands:
Code:
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak
Section 3
If you got "#" in the result, you have temporary root! Proceed with commands:
Code:
cd /data/local/tmp
./misc_version -s 1.31.405.6
Close the CMD. Reboot while holding volume down, it will go to the bootloader
Follow the instructions (start the update)
Hi,
Where did you put the downgrade folder? The attachment from the first post?
If you placed it directly on your C: Drive, the example would be, from within a cmd window -
Code:
cd C:\Downgrade
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak
Hi Andy,
From Section 1 I put the PD98IMG on my desktop and then copied it onto my SD card which is on my K: drive where my DHD is attached via USB cable.
Do I need to put the PD98IMG on my desktop in a folder called 'Downgrade' or something?
No, look at the first post again. Download the Downgrade_v2.zip file right at the bottom of the post. Extract the contents to your C:\
For the sake of ease make sure its
C:\Downgrade\<files should be in here>
andyharney said:
Hi,
Where did you put the downgrade folder? The attachment from the first post?
If you placed it directly on your C: Drive, the example would be, from within a cmd window -
Code:
cd C:\Downgrade
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak
Click to expand...
Click to collapse
one thing @andy.... maybe i´m talking about the same thing like you.... sometimes the languaje bothers me
maybe he can´t execute adb commands from c:/ if he don´t fixed it for the adb parameters works from all directories(supposing he use Windows)...
maybe he should to write it from this directory:
Code:
c:/cd sdk
c:/sdk/cd platform-tools
c:/sdk/platform-tools
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak
[
maybe i´m mistaken... i don´t have any idea about windoze lol
I'm assuming ToneyEricsson hasn't added adb to his Windows environment. I think it would be simplest to put the directory on his C:\
I know what you mean, I float between XP, archlinux, and Ubuntu. Remembering what in where can get confusing.
EDIT: /Off Topic does clicking this link make you feel better?
@toney... you have installed into your computer htc sync (for obtain drivers for "android usb debug "adb) and installed the "SDK of ANDROID into your sistem?
if not take it:
http://developer.android.com/sdk/index.html
andyharney said:
I'm assuming ToneyEricsson hasn't added adb to his Windows environment. I think it would be simplest to put the directory on his C:\
I know what you mean, I float between XP, archlinux, and Ubuntu. Remembering what in where can get confusing.
Click to expand...
Click to collapse
aaaaahhh ok ok i supossed it and
in adition...ouch! i wrote my post of avobe before read your last post, sorry..
i said the same think like you... sorry @andy
I'm using Windows 7 64bit Ultimate - I have only HTC Sync installed.
I have put the Downgrade onto C: drive and get this when running the Section 2b [For Gingerbread ROMs, 2.x] command
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\user>cd C:\Downgrade
C:\Downgrade>adb push misc_version /data/local/tmp
1546 KB/s (15837 bytes in 0.010s)
C:\Downgrade>adb push GingerBreak /data/local/tmp
2054 KB/s (16830 bytes in 0.008s)
C:\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
C:\Downgrade>adb shell chmod 777 /data/local/tmp/GingerBreak
C:\Downgrade>adb shell
$ ./data/local/tmp/GingerBreak
./data/local/tmp/GingerBreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found system: 0xafd17fd5 strcmp: 0xafd38065
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0[*] vold: 5483 GOT start: 0x00014360 GOT end: 0x000143a0[*] vold: 5483 idx: -3072 fault addr: 0x000132b4
[+] fault address in range (0x000132b4,idx=-3072)
[+] Calculated idx: -2005
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
Backup files from your SDcard to your computer and format your SDcard. Its failing to see it. Or put it in, if you removed it.
andyharney said:
Backup files from your SDcard to your computer and format your SDcard. Its failing to see it. Or put it in, if you removed it.
Click to expand...
Click to collapse
The 32GB SD card is in my DHD. I have a few SD cards here I'll format a smaller one put the PD98IMG on it and try again.
So you have seen this before?
Ok, any SDcard will do. Yes I've seen this before.
Toney, when you have your HD connected to the PC at that stage, also make sure it is in Charge mode only, not disk mode.
Done formatting an 8GB SD card and put PD98IMG on the SD card and now back in Charge only mode with USB debugging enabled.
I have now both HTC Sync and Android SDK on my pc I will try the commands again as before.
nednapalm said:
Toney, when you have your HD connected to the PC at that stage, also make sure it is in Charge mode only, not disk mode.
Click to expand...
Click to collapse
Completely forgot about that. That could be the cause.
andyharney said:
Completely forgot about that. That could be the cause.
Click to expand...
Click to collapse
caught me out once too!
Well I got HTC Sync and Android SDK installed, Charge only, USB debugging enabled and just ran the same command line as earlier and get the exact same
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\user>cd C:\Downgrade
C:\Downgrade>adb push misc_version /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
1718 KB/s (15837 bytes in 0.009s)
C:\Downgrade>adb push GingerBreak /data/local/tmp
1494 KB/s (16830 bytes in 0.011s)
C:\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
C:\Downgrade>adb shell chmod 777 /data/local/tmp/GingerBreak
C:\Downgrade>adb shell
$ ./data/local/tmp/GingerBreak
./data/local/tmp/GingerBreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found system: 0xafd17fd5 strcmp: 0xafd38065
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 1226 GOT start: 0x00014360 GOT end: 0x000143a0
[*] vold: 1226 idx: -3072 fault addr: 0x000132b4
[+] fault address in range (0x000132b4,idx=-3072)
[+] Calculated idx: -2005
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
ToneyEricsson said:
Well I got HTC Sync and Android SDK installed, Charge only, USB debugging enabled and just ran the same command line as earlier and get the exact same
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\user>cd C:\Downgrade
C:\Downgrade>adb push misc_version /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
1718 KB/s (15837 bytes in 0.009s)
C:\Downgrade>adb push GingerBreak /data/local/tmp
1494 KB/s (16830 bytes in 0.011s)
C:\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
C:\Downgrade>adb shell chmod 777 /data/local/tmp/GingerBreak
C:\Downgrade>adb shell
$ ./data/local/tmp/GingerBreak
./data/local/tmp/GingerBreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found system: 0xafd17fd5 strcmp: 0xafd38065
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 1226 GOT start: 0x00014360 GOT end: 0x000143a0
[*] vold: 1226 idx: -3072 fault addr: 0x000132b4
[+] fault address in range (0x000132b4,idx=-3072)
[+] Calculated idx: -2005
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
Click to expand...
Click to collapse
you need to enter the commands like the post 5 of this thread....
ensure you that you are leaved in platform-tools folder of the sdk the downgradev2 folder
Toney, I would also try downloading the RUU for 2.36 from XDA and flashing that to get a clean start (don't set up any accounts just skip the setup till you get to the launcher and start the process again).
nednapalm said:
Toney, I would also try downloading the RUU for 2.36 from XDA and flashing that to get a clean start (don't set up any accounts just skip the setup till you get to the launcher and start the process again).
Click to expand...
Click to collapse
I have the 2.3 RUU already downloaded but I need to downgrade to 1.32, get rooted with Visionary and and S-OFF with the tool and then after that update with 2.3 RUU.
Edit: All done, S-OFF and rooted in 2.3 with Gingerbreak.
P.S Sergie is the man! a big thanks!
Im trying to downgrade my Desire Z. Using this code:
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
When i type:
adb push psneuter /data/local/tmp
I get this message:
cannot stat 'psneuter': No such file or directory
I then tried to push the same file if i added .txt at the end of psneuter.
This still did not work.
I then typed cd [directory] and tried it (without .txt) and it still did not work.
I then tried it with .txt and it works.
So i had to cd the directory and then add the file extension? Guessing this isn't normal, but i could deal with it.
However when i got to the third line, i don't know the file extension of misc_version, so i was unable to continue. Can anyone shed some light please? What am i doing wrong or what haven't i done?
Thanks
NthZ said:
Im trying to downgrade my Desire Z. Using this code:
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
When i type:
adb push psneuter /data/local/tmp
I get this message:
cannot stat 'psneuter': No such file or directory
I then tried to push the same file if i added .txt at the end of psneuter.
This still did not work.
I then typed cd [directory] and tried it (without .txt) and it still did not work.
I then tried it with .txt and it works.
So i had to cd the directory and then add the file extension? Guessing this isn't normal, but i could deal with it.
However when i got to the third line, i don't know the file extension of misc_version, so i was unable to continue. Can anyone shed some light please? What am i doing wrong or what haven't i done?
Thanks
Click to expand...
Click to collapse
Sounds like you didn't set your path; either set a path to adb or make sure all the files are in the same directory of adb and run the commands from that directory
Sent from my T-Mobile G2 using XDA App
OriginalGabriel said:
Sounds like you didn't set your path; either set a path to adb or make sure all the files are in the same directory of adb and run the commands from that directory
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
i thought i did set a path though. and it doesn't explain why i need to add the file extension...or is that normal?
can you remind me how to set a path please? i went to computer and path>edit then added the directory of platform-tools and tools to the list. is that all thats needed? where should i save the files such as psneuter?
thanks
All I do is rip out the needed adb files and put them in a folder on my dekstop. Then you can push the files you need to your device.
Sent from my SCH-I500 using Tapatalk
NthZ said:
i thought i did set a path though. and it doesn't explain why i need to add the file extension...or is that normal?
can you remind me how to set a path please? i went to computer and path>edit then added the directory of platform-tools and tools to the list. is that all thats needed? where should i save the files such as psneuter?
thanks
Click to expand...
Click to collapse
Sounds like you added the path correctly; if you did, you should be able to run adb from anywhere. It doesn't matter where the files are on your computer, what matters is that you're running the commands from that folder.
For example, if all the files are in C:\root_files then when you open up a command prompt, you need to type 'cd C:\root_files', hit enter and then run the adb commands from there.
Sent from my T-Mobile G2 using XDA App
Can you not drag and drop the files into the terminal in Windows like you can on Mac?
thanks for all the comments. will have another go tomorrow.
i made another thread but no one has answered, my desire z is running android 2.2.1. do i need to downgrade to 2.2, then 1.74, then 1.34 to root it, or can i go straight from 2.2.1 to 1.34?
Thanks
The 2.2.1 is android version, not sense version.
You need to downgrade to 1.34 sense version, which is also running 2.2 I think.
-Nipqer
i solved the above problem but now have a new problem.
After i typed "adb shell /data/local/tmp/psneuter"
to try and get temporary root, i got this message: /data/local/tmp/psneuter: permission denied
I googled about a bit and tried another command:
C:\Root_Files>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 0755 psneuter
chmod 0755 psneuter
$ ./psneuter
./psneuter
property service neutered.
killing adbd. (should restart in a second or two)
Then tried adb shell again.
It granted me root access, but i figured i'd try and stick to the tutorial i was on.
so i went back and typed adb shell /data/local/tmp/psneuter again, and now i get this message:
mmap() failed. Operation not permitted
however if i typed "adb shell" i get #.