Please bare with me because i am a complete noob at this... but not stupid.
i have been trying to adb push .apk files to the phone, and the adb devices command shows that it is connected correctly, i get this error when i attempt to push: Permission denied
does anyone know what to do? ive tried seaching google and these forums and couldnt find anything. but that might be just because im a noob.
self-bump....
does anyone know what to do???
thefunkbot said:
self-bump....
does anyone know what to do???
Click to expand...
Click to collapse
Try not pushing it to read only memory and see if that works for you.
adb push FILE.apk /sdcard/
If that works
adb shell
su
mv /sdcard/FILE.apk /system/app/
I don't think my Vibrant will let me push to /system & that's what I did to work around (or just put the file on the sd card in mass storage mode & root explorer it over to where I want it to go).
tjhart85 said:
adb push FILE.apk /sdcard/
If that works
adb shell
su
mv /sdcard/FILE.apk /system/app/
Click to expand...
Click to collapse
i tried to push to the sd card and still got the same error.... : Permission denied
Mounted and added the apk to the sd card normally and then tried to move it with adb shell, and gives this error:
Failed on /sdcard/FILE.apk - cross-device link
I tried using the rm and mv command to remove the coresponding app from the system/app/ folder and I get an error that the file/directory does not exist.
Sent from my SCH-I500 using XDA App
Hi all...when in adb shell I can't seem to access certain commands without a segmentation fault occuring.
Specifically:
ls
chmod
and I'm sure there are others.
Running
Droid 1 - Motorola
CyanogenMod v6 (latest stable release)
Android SDK on my PC
I am trying to get busybox installed. I have it copied into /data/local and can CD to that directory but cannot chmod the file to 755 perms nor can I do an ls.
I opened the terminal emulator in this ROM and I have the same problem too. So...not likely an issue with ADB.
I've made it this far and am most decidedly STUCK. Done a lot of hunting and can't find anywhere anyone has run into this. Any help appreciated.
i have. did you lose root? thats why mine says it. i was unrooted and now my permission are only read only so i dont think i can get root back.
I have read many posts about ADB push/remount permission issues, etc. But unfortunately I still have not figured out what's wrong with my situation. First of all, I don't have a micro SD card, so I have to push files directly to the phone memory.
I firstly tried "adb push" but seems it doesn't work for me
$ adb push email.apk /system/app
failed to copy 'email.apk' to '/system/app/email.apk': Read-only file system
Click to expand...
Click to collapse
Then I searched online and people said you need to remount first. Then I got the infamous permission problem
$ adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Then I tried open shell first. no go
$ adb shell
$ mount -o remount rw system/app
mount: Operation not permitted
Click to expand...
Click to collapse
I searched more and found it can get su permission so to make things work. But when I hit "su(enter)" after open adb shell, I don't see the "#" showing up but still got an error message after waiting for a while
$ adb shell
$ su
Permission denied
Click to expand...
Click to collapse
Any one can please tell what's wrong with my operation? I rooted my G2x but didn't flash it. I installed the ROM manager and installed CWM but didn't proceed to reboot into recovery mode.
tangyoulei said:
I have read many posts about ADB push/remount permission issues, etc. But unfortunately I still have not figured out what's wrong with my situation. First of all, I don't have a micro SD card, so I have to push files directly to the phone memory.
I firstly tried "adb push" but seems it doesn't work for me
Then I searched online and people said you need to remount first. Then I got the infamous permission problem
Then I tried open shell first. no go
I searched more and found it can get su permission so to make things work. But when I hit "su(enter)" after open adb shell, I don't see the "#" showing up but still got an error message after waiting for a while
Any one can please tell what's wrong with my operation? I rooted my G2x but didn't flash it. I installed the ROM manager and installed CWM but didn't proceed to reboot into recovery mode.
Click to expand...
Click to collapse
you need to look at your phone and allow superuser app to grant permission
crazythunder said:
you need to look at your phone and allow superuser app to grant permission
Click to expand...
Click to collapse
su app? how should I set it? I didn't see anyone mentioned that. Do you care to give a bit more details? Thanks.
I think I figured out. I have to manually run the superuser app and let it say in active. Then when I type in "adb shell" the app on the handset will ask my permission. Thanks for the reminder.
Plus I am doing the following as the following that I read from another thread
adb shell
$ su
# mkdir /data/yourname
# chmod 777 /data/yourname
# exit
$ exit
adb push gps.conf /data/yourname
adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock6 /system (copy biggrin.gif)
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system (copy biggrin.gif)
# mv /data/yourname/gps.conf /system/etc
Click to expand...
Click to collapse
Update: Friday November 2nd 2012
Fixed a bad upload of the su file, must of become corrupt sorry.
Silly permission bug again, but w/e. LG should know better, from what I am told this is a recently released device. This is a long standing known issue. Lg get your sh*t together.
Directions:
unzip su.zip into the current path (directory) you are in.
adb shell
(while in adb shell)
rm /data/local/tmp/profile_calib_m
ln -s /data/local.prop /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device shell
(once in the adb shell again)
echo 'ro.kernel.qemu=1' > /data/local.prop
rm /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
Once rebooted install superuser from the market:
https://play.google.com/store/apps/details?id=com.noshufou.android.su
As usual thanks for all your work for this GREAT community!!! :good:
Thanks for letting me watch you work & getting root for my wife's phone.
Edit: DroidHost of Androidarea51.com has made a OneClick for this phone using Jcase's root. it also installs a recovery & Superuser all at the same time.
androidarea51.com/***-all-things-
root-***-174/
Help Me Please
what do you do when it says permission denied or not permitted when waiting for device, remounting, or pushing su?
lol now all we need is someone to write different roms :>
cyanogen would be nice :> lol
thank you for rooting this phone :>
jcase, i pmd you i need help please
TechManPro said:
what do you do when it says permission denied or not permitted when waiting for device, remounting, or pushing su?
Click to expand...
Click to collapse
run adb shell
make sure your prompt is a # not a $. If it is a $ start over, if it is a # make sure you run adb remount.
jbach44 said:
lol now all we need is someone to write different roms :>
cyanogen would be nice :> lol
thank you for rooting this phone :>
Click to expand...
Click to collapse
No problem.
You actually left out a step. In order to push su to the phone you have to adb remount -o rw. Otherwise it is a read-only filesystem and it cannot be pushed to the phone. Most people would probably get this, but the novices who end up with bricked phones will be angry.
Great work!
iliekandroid said:
You actually left out a step. In order to push su to the phone you have to adb remount -o rw. Otherwise it is a read-only filesystem and it cannot be pushed to the phone. Most people would probably get this, but the novices who end up with bricked phones will be angry.
Great work!
Click to expand...
Click to collapse
Actually no, you are incorrect.
adb remount without the additional parameters is correct, and not possible of bricking a phone with adb remount. No novice would be angry, because there is not possible brick from this guide, as long as it is followed.
I got the LG for my daughter (13 going on 30), and now it works fine. Thanks jcase.
Did not unlock my lgl35g
Yes I am a Noob... nobody likes me
I have exhausted every resource that I could find on this phone. I thought that this post was the answer to my problem, however it did not seem to help at all. Everything seemed as if it was working fine as I went step by step through the process. However, I rebooted my phone and there is no difference then when I started. The "su.zip" file enclosed in this post was not able to extract into the directory of my ADB client. It kept saying root already existed, but I was unable to see it in windows explorer? Is this "su.zip" a modified version of a pre-existing file in the SDK kit? I really need to unlock this phone so that I can clean up the junk. Any help would be greatly appreciated.
jcase said:
Update: Friday November 2nd 2012
Fixed a bad upload of the su file, must of become corrupt sorry.
Silly permission bug again, but w/e. LG should know better, from what I am told this is a recently released device. This is a long standing known issue. Lg get your sh*t together.
Directions:
unzip su.zip into the current path (directory) you are in.
adb shell
(while in adb shell)
rm /data/local/tmp/profile_calib_m
ln -s /data/local.prop /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device shell
(once in the adb shell again)
echo 'ro.kernel.qemu=1' > /data/local.prop
rm /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
Once rebooted install superuser from the market:
Click to expand...
Click to collapse
anyone know of a way to SIM unlock this device? I have AT&T and would like to use it om there, i bought it for $30 on clist thinking net 10 would work with an AT&T SIM but was wrong, any help would be appreciated...
anyone know of a way to SIM unlock this device? I have AT&T and would like to use it om there, i bought it for $30 on clist thinking net 10 would work with an AT&T SIM but was wrong, any help would be appreciated...
Click to expand...
Click to collapse
What is weird about that is i put the sim in a iphone and it worked just fine!!! Best bet would be ebay for unlock...
I have the Net10 one that I put a Straight Talk SIM in with no problems if I can get my hands on a AT&T SIM today I'll check it out.
---------- Post added at 07:39 AM ---------- Previous post was at 07:34 AM ----------
NateDoggTN said:
Yes I am a Noob... nobody likes me
I have exhausted every resource that I could find on this phone. I thought that this post was the answer to my problem, however it did not seem to help at all. Everything seemed as if it was working fine as I went step by step through the process. However, I rebooted my phone and there is no difference then when I started. The "su.zip" file enclosed in this post was not able to extract into the directory of my ADB client. It kept saying root already existed, but I was unable to see it in windows explorer? Is this "su.zip" a modified version of a pre-existing file in the SDK kit? I really need to unlock this phone so that I can clean up the junk. Any help would be greatly appreciated.
:
Click to expand...
Click to collapse
Did you push the su binary file or the whole folder? If you pushed the whole folder you will have to remove the directory & start over.
how to run root
Sorry for sounding like a noob, but I am...when it comes to LG. im trying to root my homies LG optimus logic but im not sure where to run the command from. if some one could help me out on to where the zip should actullay be placed and unziped to that would be a big help, thanks. and if there is a thread already for this please hook up a link.
thanks
thanks mate for this
i appreciate your time.
Anyone know of a rooted ROM
I have looked all over, but it doesn't look like a dev has created a ROM for this device. Has anyone come across one? If I knew programming I would give it a shot, but it's a mystery to me. I know that CyanogenMod 9 for the L3 (e400) works, but there is a problem with the radios, hence no cellular, wifi, or bluetooth.
Source code......
http://www.lg.com/global/support/opensource/opensource-detail.jsp
http://forum.xda-developers.com/showthread.php?p=34104009
This guy had some success with CM9, but no radio. Anyone know how to extract the radio? I've never built a rom, but this is tempting.
According to sony, the lollipop update brings back the ability to move the apps to the SD, i move the apps but they are still in the internal memory, apps like asphalt 8 that has a single file over 1.5 gigs and i cant move it to the sd, the app control says that its on the sd bus its on the internal memory as i said, some one else got this problem?
Idk. Saw this in the threads today and figured I'd copy it for later. I have the same problem.
By running code below inside your giefroot_v?\files\ folder did the trick on .77!!
(Reboot your device for changes to take effect)
adb push systemrw.sh /data/local/tmp
adb push modulecrcpatch /data/local/tmp
adb push wp_mod.ko /data/local/tmp
adb shell
chmod 777 /data/local/tmp/systemrw.sh
chmod 777 /data/local/tmp/modulecrcpatch
chmod 777 /data/local/tmp/wp_mod.ko
su
cd /data/local/tmp
./systemrw.sh
/system is mounted as r/w (see pics)!! lol
tweker said:
Idk. Saw this in the threads today and figured I'd copy it for later. I have the same problem.
By running code below inside your giefroot_v?\files\ folder did the trick on .77!!
(Reboot your device for changes to take effect)
adb push systemrw.sh /data/local/tmp
adb push modulecrcpatch /data/local/tmp
adb push wp_mod.ko /data/local/tmp
adb shell
chmod 777 /data/local/tmp/systemrw.sh
chmod 777 /data/local/tmp/modulecrcpatch
chmod 777 /data/local/tmp/wp_mod.ko
su
cd /data/local/tmp
./systemrw.sh
/system is mounted as r/w (see pics)!! lol
Click to expand...
Click to collapse
That is not the solution here. That code fixes the system partition as read write, where as the user here wants to write to his SDcard.
Furthermore, the OP is on 5.0.2 not 4.4.4 and is trying to use a stock feature of lollipop. We do not know if he is even rooted.