Unable to "push su" in rooting my Xoom (push: not found) - any ideas? - Xoom General

So I just got to one of the final steps in rooting my xoom, but for some reason, when I enter the "push su /system/bin/" command, I get a "push: not found" response. I'm completely stuck at this step...anyone have any ideas on this one??

Was adb remount succesful before you tried?

joeski27 said:
So I just got to one of the final steps in rooting my xoom, but for some reason, when I enter the "push su /system/bin/" command, I get a "push: not found" response. I'm completely stuck at this step...anyone have any ideas on this one??
Click to expand...
Click to collapse
I ran in to this. Make sure your Xoom is not on the lock screen. Should be good to go.

PaulG1488 said:
Was adb remount succesful before you tried?
Click to expand...
Click to collapse
Yes, adb remount was in fact successful.
Edit - now I'm getting "cannot stat 'su': No such file or directory"

just to be clear, is it supposed to be:
adb push su /system/bin/
or
adb shell push su /system/bin/
???

syntax is "adb push ..."

bcgaynor82 said:
syntax is "adb push ..."
Click to expand...
Click to collapse
thats what I thought, and when I do this I get the "cannot stat 'su': No such file or directory" error message.
I have no idea what's going on here. Its almost as if I dont have the xoomroot files (including su) in the correct place, but they are there in the SDK tools folder as they are supposed to be. UGH!?!!?

joeski27 said:
thats what I thought, and when I do this I get the "cannot stat 'su': No such file or directory" error message. ?????
Click to expand...
Click to collapse
Make sure that one of the following is true:
the files you want to push are in the same folder as adb
adb is in your path and you are in the directory that the files are
Also make sure you are running this from your computer and not the Xoom, although it sounds like you are bumping into one of the two scenarios above.

nindoja said:
Make sure that one of the following is true:
the files you want to push are in the same folder as adb
adb is in your path and you are in the directory that the files are
Also make sure you are running this from your computer and not the Xoom, although it sounds like you are bumping into one of the two scenarios above.
Click to expand...
Click to collapse
yes they are in the same folder as adb, and I'm in the adb directory while in terminal. still getting the same error message. I'm so lost on this one.

Is there any chance that the unlock didn't take? Though I can't see how it didn't - I went through the entire procedure, answered all the prompts during fastboot, and it did erase/reset the tablet afterwards, so I'm guessing that isn't it.

joeski27 said:
yes they are in the same folder as adb, and I'm in the adb directory while in terminal. still getting the same error message. I'm so lost on this one.
Click to expand...
Click to collapse
Any chance you can screenshot your sdk tools folder

They're supposed to be in the 'platform-tools' folder, not tools. The files go in the same folder as adb so it knows where they are.

PaulG1488 said:
Any chance you can screenshot your sdk tools folder
Click to expand...
Click to collapse
Screenshot of my sdk tools folder:
EDIT: heres the link:
http://i869.photobucket.com/albums/ab259/olesweski/Screenshot2011-03-03at122552AM.png?t=1299130486

Elysian893 said:
They're supposed to be in the 'platform-tools' folder, not tools. The files go in the same folder as adb so it knows where they are.
Click to expand...
Click to collapse
I know, but I had already moved adb into the tools folder earlier on. So they are in the same folder.

send a screenshot of everything in your command prompt if u can please

PaulG1488 said:
send a screenshot of everything in your command prompt if u can please
Click to expand...
Click to collapse
here's the screenshot of my terminal:
http://i869.photobucket.com/albums/ab259/olesweski/Screenshot2011-03-03at124929AM.png?t=1299131460

Do you have the 3.0 sdk installed
Wait I see the problem after you remounted you have to direct it back into your tools foledr before doing the adb push command

PaulG1488 said:
Do you have the 3.0 sdk installed
Click to expand...
Click to collapse
all I know is that i have the latest sdk installed, but are you referring to something additional to that? such as "SDK Platform Android 3.0, API 11, revision 1" ?

joeski27 said:
all I know is that i have the latest sdk installed, but are you referring to something additional to that?
Click to expand...
Click to collapse
After u did adb remount it took you back to your main folder make sure you direct it back to your tools folder then run the adb push command and problem will be solved

PaulG1488 said:
After u did adb remount it took you back to your main folder make sure you direct it back to your tools folder then run the adb push command and problem will be solved
Click to expand...
Click to collapse
So I just did the remount again (successfully), and now instead of just entering "adb push ...", I would need to do what?
EDIT - just tried this, and got this result:
Joseph-Olesweskis-iMac:~ olesweski$ /Users/olesweski/Desktop/android-sdk-mac_x86/tools adb push su /system/bin/
-bash: /Users/olesweski/Desktop/android-sdk-mac_x86/tools: is a directory

Related

Mac os x Adb problem

I downloaded and installed the latest mac intel sdk 1.6 to link with my new rogers magic which is running 1.5. I unpacked everything and restarted my computer. I also enabled debugging on my Magic 3g. When I plug my Magic in, I open terminal in su (root) and once inside the folder, i try running the "adb devices" command however it doesnt work. I get "bash adb command not found". Any ideas from the mac users on here?
should I install the 1.5 sdk, not that it will make a difference since I cant even run the command in 1.6?
any ideas?
Are you putting ./adb devices or just adb devices? because the ./ is very important
tristyB said:
Are you putting ./adb devices or just adb devices? because the ./ is very important
Click to expand...
Click to collapse
.... I am a moron. thank you. I was to excited!!!
ryrules1 said:
.... I am a moron. thank you. I was to excited!!!
Click to expand...
Click to collapse
It's fine, it happens to all of us!
The other options is to add your <android_sdk>/tools folder to your path. That way, you don't need to cd into the folder and use ./adb...you can just use adb from anywhere in the prompt.
Google around but I believe you need to add a line like this:
export PATH=<android_sdk_location>/tools:$PATH
to your .profile file in your home directory.
where <android_sdk_location> is where you extracted the sdk.

How to push files through ADB

Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
usadevil7193 said:
hi mate...i m new to android..i own a nexus1..hav rooted without unlockin d bootloader..i am tryin to push d track ball to wake mod...evry time i type adb remount it says permission denied..any ideas to get things workin...???????
Click to expand...
Click to collapse
Welcome to XDA and Android! Are you trying to get help for your Nexus One? This forum here is specifically for the HTC Hero CDMA.
You will probably find better and more specific help in the Nexus One forums which are here: http://forum.xda-developers.com/forumdisplay.php?f=556
Great post, very easy to follow, thank you.
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
this also works for the samsung Galaxy S in recovery mode.
mikeybonez28 said:
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
Click to expand...
Click to collapse
mine shows up but then says error, device offline
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
yogi2010 said:
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
Click to expand...
Click to collapse
i had the same issue with something i was trying to push. I think you need to make sure you have exactly the same file name like caps and all. i was trying to push rootexplorer.apk and i got the same message but i then changed it to RootExplorer.apk and it work.(notice the difference in caps)
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
{LCD}Stelios said:
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
Click to expand...
Click to collapse
Make sure your have the drivers for your phone installed first of all.....Then, in your command prompt you have to change directories to the sdk (which you made harder by not installing to C:\
Try: cd Program Files\Android\android-sdk\tools
Then type: adb devices
That should return "xxxxxxdevice" connected....Then you know you have it set up.
Look in kyouko sig he has all the commands for adb
Sent from my HERO200 using XDA App
Bierce22 said:
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Click to expand...
Click to collapse
great video arse....thanks for the help donkey
Flashing fresh ROM via ADB in Linux
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
pacut said:
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
Click to expand...
Click to collapse
There is a thread somewhere on how to flash without a SD card and flashed using adb I believe, but don't take my word for it. Adb works fine with Linux, just have to set it up differently. Look in my sig and select the compile aosp on Ubuntu one and follow instructions on getting the USB set up.
Sent from Dorian's HTC Hero CDMA
Yes, I saw it. It's http://forum.xda-developers.com/showthread.php?t=911228
The fact is...still have to navigate through menu via VolumeUp/volumeDown buttons
Maybe through ROM manager, premium, I can install ROM direclty.
I am gonna trying
YES ! It works !
Hi I need help. I accidentally wipped my phone in CWM and now I'm trying to use adb push to push the update.zip into my phone sd everything seems to work but then in CMW it says there are no files..
any suggestions?
[Edit]
nevermind
I kept trying different locations
not sure which one did the trick but I'll list the one's I tried
so \update.zip /sdcard/
.... /sdcard/update.zip
(note I put "/update.zip" thinking maybe it needed to be reallocated to the same file/destination
Can i use adb push *.apk /system/app to push several files at once, and then repeat but using *.odex instead of *.apk? I keep ending up getting the same error, and i want to find out which app is messing with me...
rulermon said:
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
Click to expand...
Click to collapse
Hey guys ...
I have also rooted my phone , everything was OK until one day i tried to write something to /system/app and i recieve this error:
in Addition , i am writing "adb shell" and it shows me $
if i am doing adb shell --> $ --> su --> it shows #
Can some1 knows what is the problem?

ADB in Win 7

ADB was working for awhile then quit.
Can someone please help me?
In command prompt it says "ADB is not an internal or external command, operable program or batch file"
Do you install the Sync software?
laufine said:
Do you install the Sync software?
Click to expand...
Click to collapse
Yes, I've tried it with and without.
I recently deleted the Sync, should I reinstall it?
I'll post the drivers. Here is the link.
http://www.megaupload.com/?d=PU08Q26S
You can try manual install the drivers.
Hero's Hero said:
ADB was working for awhile then quit.
Can someone please help me?
In command prompt it says "ADB is not an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
You have to either put it in your path, or cd to the directory where adb is contained.
Example:
cd \android-sdk-windows\tools
Then run your adb commands. That error message you're getting is because the OS doesn't know the adb executable exists.
smw6180 said:
You have to either put it in your path, or cd to the directory where adb is contained.
Example:
cd \android-sdk-windows\tools
Then run your adb commands. That error message you're getting is because the OS doesn't know the adb executable exists.
Click to expand...
Click to collapse
i was just about to type this up then saw this as the last post. Good work man
laufine said:
I'll post the drivers. Here is the link.
http://www.megaupload.com/?d=PU08Q26S
You can try manual install the drivers.
Click to expand...
Click to collapse
I have all the drivers
smw6180 said:
You have to either put it in your path, or cd to the directory where adb is contained.
Example:
cd \android-sdk-windows\tools
Then run your adb commands. That error message you're getting is because the OS doesn't know the adb executable exists.
Click to expand...
Click to collapse
I have them in the path, but no beauno
Hero's Hero said:
I have them in the path, but no beauno
Click to expand...
Click to collapse
Where is your SDK installed to?
DevinXtreme said:
Where is your SDK installed to?
Click to expand...
Click to collapse
It's in C:/
Hero's Hero said:
It's in C:/
Click to expand...
Click to collapse
And you've tried running this before any adb commands, right?
Code:
cd C:\android-sdk-windows*\tools
*Or whatever you named that folder
I've Had this issue. I Had to un-install the sync And sdk. Then install them right back on lol.Reloaded the vista drivers then Im back Tim. That is if its a Driver issue
-------------------------------------
Sent via the XDA Tapatalk App
Do you still need help with this? I can help you out
regaw_leinad said:
Do you still need help with this? I can help you out
Click to expand...
Click to collapse
Yes I do.
Would really appreciate it.
It seems you're on your way to receiving help. However, if you're still in limbo, locate your android folder or adb executable, right click, copy the location, and paste it into a follow-up reply. This is with respect to the diagnosis process.
Either way, I hope you're headed in the right direction to solve your slight dilemma.

[TUTORIAL] How to root locked bootloaders PLAY/ARC/NEO

To start off I want to say, I am NOT claiming to have created this exploit, I am merely letting people know that it works on the arc.
All credit for this goes to Chainfire and The Android Exploid Crew
The origional thread is here: http://forum.xda-developers.com/showthread.php?t=1044765
Download here
Install the APK and run it.
For people getting "could not extract assets" error execute
adb shell rmdir /data/local/tmp
and then
adb shell mkdir /data/local/tmp
Click to expand...
Click to collapse
Quote posted by jassired
works for me
So just push the apk to the phone, install and you're done?
no need to "push", just stick it on your sd card and install
diggedy said:
no need to "push", just stick it on your sd card and install
Click to expand...
Click to collapse
I get the error thing...and I can't find the effing map where I need to remove stuff....
where do I find the god damned map to remove the files I need to remove when it only fails to install?????
I've checked every single map on the memory card, going nuts here...
Cim_XII said:
where do I find the god damned map to remove the files I need to remove when it only fails to install?????
I've checked every single map on the memory card, going nuts here...
Click to expand...
Click to collapse
What do you mean?
double post :s will use this later
I have put the .apk in my download map on the sd card of the phone, installed the apk and run it and I get the: "could not extract assets" error execute
and then when I get that I am supposed to remove some files from a map on the sd card, and I cannot find said map....I hava rebooted the phone, and I still cannot find data/local/tmp or what ever map I need to find.....
Cim_XII said:
I have put the .apk in my download map on the sd card of the phone, installed the apk and run it and I get the: "could not extract assets" error execute
and then when I get that I am supposed to remove some files from a map on the sd card, and I cannot find said map....I hava rebooted the phone, and I still cannot find data/local/tmp or what ever map I need to find.....
Click to expand...
Click to collapse
you need to execute the commands in the origional post via ADB with USB debugging enabled, because the location is in the system and ironicly you dont have the root privelages to delete them
I don't even know what ADB is....that's how much I know...
Cim_XII said:
I don't even know what ADB is....that's how much I know...
Click to expand...
Click to collapse
I have attached it to this post. ADB is the Android Debug Bridge. It is used to excecute commands on android devices. Just extract the zip, then open a command prompt and change to the directory of ADB, then excecute the commands.
if you get the error for esset you need to remove all the files inside to /data/local/tmp/
press: adb shell
press ls /data/local/tmp
and remove one by one the files as my example:
$ ls /data/local/tmp/
ls /data/local/tmp/
Superuser.apk
Gingerbreak
runscript
sysrun
$ rm /data/local/tmp/Superuser.apk
rm /data/local/tmp/Superuser.apk
$ rm /data/local/tmp/Gingerbreak
rm /data/local/tmp/Gingerbreak
$ rm /data/local/tmp/runscript
rm /data/local/tmp/runscript
$ rm /data/local/tmp/sysrun
rm /data/local/tmp/sysrun
and now try again with app and may it works (in my case, works)
dh2311 said:
I have attached it to this post. ADB is the Android Debug Bridge. It is used to excecute commands on android devices. Just extract the zip, then open a command prompt and change to the directory of ADB, then excecute the commands.
Click to expand...
Click to collapse
maybe I should've mentioned I'm on a Mac computer with no access to windows....damn, this is so frustrating....
Ah... Its still possible you just have to get the android sdk for mac.
Get the SDK from here
Then in the tools folder ADB should be there
Then its commands as normal I think... not sure tho, don't have a mac.
Search around on here for tutorials, I'm sure someone has put up a tutorial on setting up adb on mac
dh2311 said:
Ah... Its still possible you just have to get the android sdk for mac.
Get the SDK from here
Then in the tools folder ADB should be there
Then its commands as normal I think... not sure tho, don't have a mac.
Search around on here for tutorials, I'm sure someone has put up a tutorial on setting up adb on mac
Click to expand...
Click to collapse
kewl, and the exact commands is in post #1 right?
so this root's the OS, title is confusing, does it enable fastboot? allow you to flash custom roms?
should be....
dh2311 said:
you need to execute the commands in the origional post via ADB with USB debugging enabled, because the location is in the system and ironicly you dont have the root privelages to delete them
Click to expand...
Click to collapse
did exactly what you said, but get the message
adb: permission denied
No does not enable fastboot

Messed up my Nexus 4 :(

Guys i have a problem...
I wantes to delete all data on my N4 and start again with a fresh device, My phone is rooted and i had an custom rom installed, i deleted all data pictures and everything else, after that i also formated the sd card, cache etc etc and thats where it went wrong Now i can go into cwm but nothing more... when i reboot i see the black screen with google on it and after that nothing happens...
How can i solve this problem? I hope that i didnt bricked my phone
should still be able to mount usb storage in cmw, that or push files using adb, if you can get into recovery then you can always get your device back
I just helped a user with the same problem yesterday.
Here's the link with steps how to push a rom to your phone with adb: http://forum.xda-developers.com/showthread.php?t=2137976
can you get into fastboot? if you can then all you have to do is follow this thread:
http://forum.xda-developers.com/showthread.php?t=2010312
coffmad said:
should still be able to mount usb storage in cmw, that or push files using adb, if you can get into recovery then you can always get your device back
Click to expand...
Click to collapse
No, you can't mount USB in recovery. The Nexus 4 does not use UMS.
Ok thanks for the fast reply, im gonna try to push a rom with adb.
''I know you don't have a rom on your phone. This is how you can push one to your phone.
You must be booted in recovery
Put the rom in the same directory on your PC where you have adb.exe
Open up the command prompt from that directory. (hold shift and right click--then choose open command window here)
Then type the command-- adb push nameofrom.zip /sdcard/
The file with push to your phone and then your can select it and flash it from recovery''.
I see this in another thread, Where can i find adb.exe? Im terrible with computers...
Adb is part of of the platform tools for android. Since you unlocked and flashed a custom rom you should have it on your computer.
If you need it, it is located as an attachment at the bottom of this post: http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
I got the attachment, its called platform tools v16, i dragged and dropped an rom in that platform tools file and after that i dont know what to do...
''Open up the command prompt from that directory. (hold shift and right click--then choose open command window here)
Then type the command-- adb push nameofrom.zip /sdcard/''
This is what i dont understand.
Mr Djoegoe said:
I got the attachment, its called platform tools v16, i dragged and dropped an rom in that platform tools file and after that i dont know what to do...
''Open up the command prompt from that directory. (hold shift and right click--then choose open command window here)
Then type the command-- adb push nameofrom.zip /sdcard/''
This is what i dont understand.
Click to expand...
Click to collapse
Extract the files in that .zip into a folder and name it something like "Android."
Move the Rom.zip into that folder as well.
Then do the shift and right click and open the command window pointed to that directory. (as I explained above)
Make sure its connected properly and there isn't a driver issue by typing the command: adb devices. If it returns your serial number you are good to go. (If not, you need to install the correct drivers, which are linked in Section A of the post I linked earlier.)
Then type the command. adb push nameofRom.zip /sdcard/
When i type adb devices i can see my serial number and recovery after it.. when i type ''adb push nameofRom.zip /sdcard/ '' i get a message cannot stat 'nameofRom.zip' No such file or directory
What am i doing wrong?
Edit: hahahaha i see what i do wrong nameofRom.zip
Are you actually typing "nameofrom.zip" ?
Sent from my Nexus 4 using xda app-developers app
Mr Djoegoe said:
When i type adb devices i can see my serial number and recovery after it.. when i type ''adb push nameofRom.zip /sdcard/ '' i get a message cannot stat 'nameofRom.zip' No such file or directory
What am i doing wrong?
Click to expand...
Click to collapse
You replace "nameofRom" with the name of your ROM your trying to push
moses992 said:
Are you actually typing "nameofrom.zip" ?
Click to expand...
Click to collapse
hahaha Yes!
@El Daddy: Thanks for your help Im gonna donate a bottle of wine :good:
Mr Djoegoe said:
hahaha Yes!
@El Daddy: Thanks for your help Im gonna donate a bottle of wine :good:
Click to expand...
Click to collapse
Thanks for that. Unneeded, but very appreciated!
Sent from my Nexus 7 using Tapatalk HD
You certainly haven't bricked it. The fact you can get to recovery means, you can get to fastboot. Simply open fastboot and reflash stock and be more careful next time

Categories

Resources