newb help please... help with adb copying files.... no permissions?? - Captivate Q&A, Help & Troubleshooting

Sorry... newb question... can not figure out this deal...
Trying to copy the jupiter files to my phone... can not.
I dont have permissions... how can I get permissions opened up?
Below is some of what I am getting in regards to errors -
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb push jupiter.xml /system/etc/jupiter.xml
failed to copy 'jupiter.xml' to '/system/etc/jupiter.xml': Permission denied
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb push jupiter.xml /sdcard/jupiter.xml
failed to copy 'jupiter.xml' to '/sdcard/jupiter.xml': Permission denied
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb shell
$ su
su
Permission denied
$
Note - this is a samsung captivate phone with a fresh cognition 2.36b rom and I used one click root on it to root the phone after the build..... (but I think the rom was rooted to start with??
Sorry ... just need a way to get access to this phone - trying adb.... also is there a windows file manager that would browse/edit the contents of this phone?
thanks in advance Kevin

PLEASE DIVERT ALL QUESTIONS TO Q&A FORUM NEXT TIME.
IF you're on Froyo.. for some reason froyo does not allow pushing to /system .. at least for me that's the case (someone correct me)
root your phone:
1. adb push /sdcard/jupiter.xml
2. adb shell
3. su
4. cp /sdcard/jupiter.xml /system/gps/jupiter.xml (or wherever you need to put it)
5. do the same for the rest of the files.. but tbh
THERE'S NO FIXING GPS YET

darkamikaze said:
PLEASE DIVERT ALL QUESTIONS TO Q&A FORUM NEXT TIME.
THERE'S NO FIXING GPS YET
Click to expand...
Click to collapse
What he said.

If froyo didn't fix your gps then you are sol. But don't be so sure its still broke, it can take some time on the first lock. Once it gets a lock within 5-10 meters it should work decent afterwards with the occasional hiccup usually when its not used every day. But some are reporting poor performance still with froyo.
A factory reset can fix some bugs I have seen on jf7 and ji6 on my phone causing the gps to turn off. Jj4 doesn't seem to have that bug on my phone. Cog2.3b6 is jj4 based
Some claim to have performance degrade over time, I think that's all placebo but others have completely different experiences with gps than I do. I notice it having to occasionally need to get new gps data causing a delay in the initial lock but it seems more random than progressive and I never fail to get a lock.
If you are trying to use the jupiter.xml file in the gps solution thread from clshortfuse our what ever his name is, you will likely see an no improvement to a slight improvement. It gets faster locks on eclair roms but on froyo the jupiter file already resembles his and the major difference being that his forces the google server for gps data.
Sent from my SAMSUNG-SGH-I897

OK thanks for all the help so far -
I had a n82 phone, like 2-3 years ago, it was awesome.... google maps and all... blue dot was where the phone was... I could watch me walk around my house... it would show me getting the mail walking down the drive way to the mail box and back....
I have an iphone 3gs....works fine.... maybe not quite as good as the n82 did, but works ok, locks quick and will the blue dot with in a few feet of me IN MY HOUSE.
While I dont get this whole GPS problem on this phone I hear you about not trying to fix it.
I have some limited unix experience... used vi and other stuff, was able to move,copy, edit and replace files... change permissions and other standard stuff.
So if the cognition rom is rooted as is, and I was rooted before the rom, I assume I still am rooted....
Why wont the commands I tried work?
I did not try the other commands noted in this thread, yet, I will soon.
So is it my phone? or do I have the commands/syntax wrong?
If I am going to stick it out with the phone I need to figure out how to fix it.
thanks again for your help.
Kevin

Any ideas or reasons why this command would not work?
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb push jupiter.xml /sdcard/jupiter.xml
failed to copy 'jupiter.xml' to '/sdcard/jupiter.xml': Permission denied
My file on my PC is in the folder I am working from ....\tools and I assume I should have permissions to the sdcard folder?
Any help would be appreciated.
thanks Kevin

Have you made sure to grant superuser permission on the phone?
I had that issue the first time I tried it and found that I hadn't granted superuser access.
Also to the OP, if you switch to Perception, DG includes the Jupiter fix in the ROM.

You can't push to /system in FROYO.
you have to push it to /sdcard first
adb shell
su
cp /sdcard/jupiter.xml /<LOCATION>
and chmod it
and chown it.

thanks for the help... to make sure I have the right permissions I need to use the chmod and chown commands -
Do I need to mount the system first? Something like -
Code:
adb shell
$ su
# mount -o rw,remount /dev/stl9 /system
# chmod 777 /system/etc/*
thanks again, Kevin

haeffnkr said:
thanks for the help... to make sure I have the right permissions I need to use the chmod and chown commands -
Do I need to mount the system first? Something like -
Code:
adb shell
$ su
# mount -o rw,remount /dev/stl9 /system
# chmod 777 /system/etc/*
thanks again, Kevin
Click to expand...
Click to collapse
I would never do 777 on any file. Jupiter.xml should be 644 and user and group root.
Sent from my SAMSUNG-SGH-I897 using XDA App

Related

cat /sdcard/su > su

I am using the PRS complete rooting guide. And when it tells me to type cat /sdcard/su > su, i am getting this error message - cat: can't open '/sdcard/su': No such file or directory.
Can anyone help with this?
Do you have su on your sdcard?
use unrevoked. one click root
just use the one click method by unrevoleved its easier
Su is not on the SD card. The sd card is a brand new PNY card. I have Su in the sdk/tools folder.
Then obviously, that command will not work. Use the unrevoked method if you are unsure what these commands do/how they work. Less headache on your end.
where is it located?
maybe i'm missing something obvious, but why pipe the text rather than just copy the file?
Sorry if this is the wrong place, but that command is curious.
This is what it's asking me to do.
From PRS Complete Rooting Guide
Now type the following commands to make it persistent through reboot
Code:
adb shell
su
export PATH=$PATH:/system/bin
cd /system/app
cat /sdcard/Superuser.apk > Superuser.apk
cd /system/bin
cat /sdcard/su > su
ln -s /system/bin/su /system/xbin/su /* IF YOU GET AN ERROR HERE DO rm /system/xbin/su THEN REDO */
chmod 06755 su
k_flan said:
maybe i'm missing something obvious, but why pipe the text rather than just copy the file?
Sorry if this is the wrong place, but that command is curious.
Click to expand...
Click to collapse
I don't know what that guide does, but it doesn't seem right --- it'll mess up the privs, that's why the old root was written as an update-payload.
It's redirected I/O since you can't copy across filesystem boundaries -- ie /sdcard to a different mountpoint.
So if I reboot my phone now, do you think I'll lose root and have to start over?
csills said:
So if I reboot my phone now, do you think I'll lose root and have to start over?
Click to expand...
Click to collapse
Either way, it shouldn't matter much. If it didn't work or you lost root for any reason, just go to http://unrevoked.com/ and click on the image for the Incredible. Today unrevoked released version 3 of their tool. This will root your phone and flash the custom recovery all without your needing to do anything in a shell.
askwhy said:
Either way, it shouldn't matter much. If it didn't work or you lost root for any reason, just go to and click on the image for the Incredible. Today unrevoked released version 3 of their tool. This will root your phone and flash the custom recovery all without your needing to do anything in a shell.
Click to expand...
Click to collapse
AND - if you appreciate unREVoked's work - please donate. They do amazing work and they do it all for free! We're the lucky ones to have such [email protected] developers out there who do this kind of stuff so that we don't have to figure out the exact second to push in our SD cards, push files to the SD card, and then push them to the phone at exactly the right time...... just download, run, and you're done.
Just use the unrevoked 3 you will save plenty of pain and struggle
unrevoked3 worked! Thanks for the help guys.
No problem were glad to be of assistance

[Q] adb remount

Hi guys,
sorry if my english isnt so good...
i'm in trouble with ADB..
i want to upgrade my swype keyboard on my NEW M1 rom eu....i got the 1.58 and i want to try the 1.60..
i found a thread on this forum with commands for upgrading the swype like this way:
Code:
adb remount
adb shell
su
pm list packages -f | grep swype
rm /system/app/<restOfApkPathFoundInAboveCommand>
pm uninstall <value after apk= found in result of 2 commands above>
exit
Install normally. If you want the apk in the rom:
adb push <newSwype.apk> /system/app/<newSwype.apk>
adb remount
adb shell
pm install <newSwype.apk>
(found here-> LINK)
I'm stuck at the beginning:
Code:
C:\android\tools>adb devices
List of devices attached
9000ec2a228b device
C:\android\tools>adb remount
remount failed: No such file or directory
my phone is rooted and in debug usb mode..I dont understand how can I go ahead...
what can I do?
thanks
ivan
Same here.
gbates said:
Same here.
Click to expand...
Click to collapse
oh..i'm not the only one! : >
we need to find the solution...but it's not easy..
are u using the NEW M1 rom too?
Rooting doesn't automatically give you remount permissions AFAIK.
i just use this command
Code:
adb push test.txt /sdcard/test.txt
and the copy is ok....i found the file in the sgs sdcard...
The command adb remount is for the /system directory (for set write permission) .... i think it cant find the directory /system on the phone......why?!?!
danmullen said:
Rooting doesn't automatically give you remount permissions AFAIK.
Click to expand...
Click to collapse
mmmm what do u mean? i need to do something else? thanks
Are you using the internal ext2 lagfix? I think that causes problems with the adb remount command. It doesn't work for me either.
Same results using a different ROM?
psychedelic'd said:
Are you using the internal ext2 lagfix? I think that causes problems with the adb remount command. It doesn't work for me either.
Click to expand...
Click to collapse
No lagfix installed at the moment..i installed lagfix when i was on M2 but i think that reflashing removed the lag fix...is it right?
harold4 said:
Same results using a different ROM?
Click to expand...
Click to collapse
Not yet but i think i'm gonna try it this afteroon if i dont find a solution.
Sent from my GT-I9000 using XDA App
adb remount as well
Trying to remap hard keys, adb remount along with push and pull do not work. Depending on whether im in shell or not I get no such file or directory or file not found errors. I can change into directory of each of the folders im trying to work with, and look at the file but I can't push it from my tools folder(locally) or pull it from the system folder. Every tutorial I see has adb remount command first, which fails every time.
Samsung Fascinate
Blackhole-build your own rom
(also tried on jt's latest rom, same issue
Crazy
I'm having the same issue here too. I'm trying to get a custom boot screen on my rooted Samsung Infuse and I've tried every way I can think of and it wont take. Clockworkmod says successfully installed, but its not. Soon as I reboot I see the At&T stock boot. I've fixed all of my permissions and still no luck.
So I saw a solution to do it via adb by typing "adb remount" and I get the same thing u guys are getting. I've got a headache now. Done all I could, even typing "shell", "su", that all goes well then when I tried to push it "adb push bootanimation.zip system/media" I get adb: not found. Smh, is it a device issue?
i think ive got the solution
flash a new kernel..................................worked for me................

BusyBoX

I have busybox 1.6 on my captivate i see on www.busybox.net 1.17.3 is out. I have downloaded it from the site and its a tar file with a folder with a whole bunch of folders and files. How do you install this?
Are you familiar with the phrase, "if it isn't broken, don't fix it?"
I advise you to heed its warning.
But if you must proceed, a quick google search for "how to install busybox manually" brings up this very good result: http://www.droidforums.net/forum/droid-2-hacks/82573-busybox-manual-install-how-guide.html
Edit: By the way, love the avatar. Great album.
Yes i understand if its not broke don't try to fix it but i'm a OCD updater! Would there be any advantages of updating it? P.S. I saw Megadeth and Slayer a month ago they rocked!
Only advantages I can see are having a couple more bug fixes and maybe 4-5 new commands built in.
Download Busybox-1.17.2 HERE
Extract busybox to your SD Card
Make sure you are in PC Mode and Debugging is enabled in Applications options
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/busybox /system/xbin/
cd system/xbin
busybox --install /system/xbin/
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
sync
reboot
You can also use Root Explorer or whatever file browser you may use to copy busybox to your system/xbin folder. Some people use system/bin but I prefer xbin...just a habbit.
Click to expand...
Click to collapse
Ya, I read that and got really scared.
What is PC mode and where do you type these commands? (Vista user)
Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.
Cruton502 said:
Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.
Click to expand...
Click to collapse
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.
miztaken1312 said:
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.
Click to expand...
Click to collapse
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!
Cruton502 said:
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!
Click to expand...
Click to collapse
I think you're seriously confused. The Captivate isn't a NAND locked phone. Generally when you root, busybox is installed. (I think. At least it always was for me.) You could also try installing Titanium Backup and have that install busybox for you.

[Q] Google Music apk sideloading?

Hi all, I'm trying to sideload the new Google Music apk onto my CM7 Nook Color. As i reside outside the US, I don't have it available through the market. I did sign-up for the invite through a proxy network though and got the invite a few days back. Now don't ask me how, but after receiving the invite, somehow the new google music app appeared as a manual update on my Nexus One(2.3.4) and it works like an absolute charm on it. I 'adb pulled' this Music app off my Nexus One and tried to install it on my Nook Color through adb. Here's the steps I followed:
- Connected through adb wireless first.
- Tried 'adb install' first. That didn't work.
$ ./adb install MusicGoogle.apk
493 KB/s (375498 bytes in 0.742s)
pkg: /data/local/tmp/MusicGoogle.apk
Failure [INSTALL_FAILED_DEXOPT]
- Then tried transferring the apk to /system/app
$ adb push MusicGoogle.apk /data/local/tmp/
$ adb shell
# su
# mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system
# chmod 777 /system/app
# cp /data/local/tmp/MusicGoogle.apk /system/app/
# chmod 755 /system/app
# mount -o ro,remount -t ext4 /dev/block/mmcblk0p5 /system
This didn't work either. The icon failed to show up in the app-drawer.
Where am I going wrong here? Is it becuase I took the apk from my N1?..I hardly think that should be a problem. Could someone from the US post their apk which they installed on their NC, from the Android Market?
Thanks.
Sorry if this is a dumb question, but is there any reason you don't just use Market Enabler?
MickMcGeough said:
Sorry if this is a dumb question, but is there any reason you don't just use Market Enabler?
Click to expand...
Click to collapse
I could always do that, but is there a reason why the above method shouldn't work? I've followed the above method many times to install apps on my rooted N1.
hungryTux said:
I could always do that, but is there a reason why the above method shouldn't work? I've followed the above method many times to install apps on my rooted N1.
Click to expand...
Click to collapse
I don't know if there's any reason that wouldn't work. I'm using Google Music Beta in Canada for a week or so now and I spent less time setting it up on my NC than I've spent replying in this thread
I'm not sure if the apk coming from your nexus one is being the reason the apk is not installing but sideloading is vary easy. all you have to do is place the apk on the root of your sd card and navigate from a file manager app like astro to the apk and press on it. the app manager will appear and ask if you'll like to install it, say yes. there, you're all done.
cm7 n111 6/18 OC kernel 300/600/800/1100/1200 conservative

[HOWTO] Root HKTW 2.3.4 - The easier way

I don't know if I am the only one who realized there's su binary already in the build. Anyway, this is a shorter route to have root working on your phone. This only works with the HKTW 2.3.4 build! And this instruction have only be tested by me. So, do take precautionary measures.
DOWNLOAD: http://dl.dropbox.com/u/6418171/SuperUser.zip
INSTRUCTIONS:
1. Extract the zip to your internal storage (i.e. /sdcard)
2. Get into the phone shell i.e.
adb shell
Click to expand...
Click to collapse
3. Then, type and press enter:
su
Click to expand...
Click to collapse
4. Lastly, copy and paste these whole chunk to your phone shell and press enter:
mount -o remount,rw /dev/block/mmcblk0p12 /system && cp /sdcard/SuperUser/su /system/bin/su && chmod 6755 /system/bin/su && cp /sdcard/SuperUser/SuperUser.apk /system/app/SuperUser.apk && mv /system/xbin/su /system/xbin/dosu
Click to expand...
Click to collapse
If there's no error with the output, you should have root access on your phone now. Tada! Do report of this works for you!
Will try and report if it works or not
Sent from my MB860 using XDA App
Well I know I shouldn't say it here...
But is the HKTW rom blurred or blurless?
Different kind of blur but its still blur
Sent from my MB860 using XDA App
Do you mean Blur 4.5?
I don't know what its called lol
Sent from my MB860 using XDA App
Trying it out now. Will report back.
And this has Blur on it. It's not a custom ROM.
Anyone else experiencing issues getting their phone recognize by adb
Sent from my Atrix 4g Ubl 2.3.4
su is throwing me a permission denied
http://pastebin.com/brXVEYDb
i guess i didn't phrase the instruction clearly. sorry. just edited first post.. reread everything and try again.
had to run it a few times.. but it worked! thx!
Works! 10char
reserved *10chars
su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.
jimmer411 said:
su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.
Click to expand...
Click to collapse
having the same issue with SU
Are there any other alternatives to root currently?
jimmer411 said:
su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.
Click to expand...
Click to collapse
Can you be more specifically on those files? Where to download and how exactly did you go about running those files?
Do I need the SDK for rooting it?
THIS WORKS ON WINDOWS, OSX, AND LINUX
once you type in adb shell then type dosu instead of su and see if that helps
I get an error at the last part when I put it in cmd
Whenever I type in 'su', I get permission denied - and dosu doesn't work either.

Categories

Resources