[Q] Any way to get ADB fully working on GT-P5110 ?? - Galaxy Tab 2 Q&A, Help & Troubleshooting

Hey guys!
I want to replace the original frmaework-res with my modded apk but ADB does not fully work Is there any Kernel which solves this problem or any other way?
Please HELP!
BTW: I am running official Android 4.1.1

mrlollog said:
Hey guys!
I want to replace the original frmaework-res with my modded apk but ADB does not fully work Is there any Kernel which solves this problem or any other way?
Please HELP!
BTW: I am running official Android 4.1.1
Click to expand...
Click to collapse
ADB works fully, what are you talking about?

WTF??!!
DigitalMD said:
ADB works fully, what are you talking about?
Click to expand...
Click to collapse
So for you "adb remount" and push to /system works??
FOLLOWING PROBLEM:
I get the following error when I try "adb remount"
remount failed: Operation not permitted
HELP PLS

mrlollog said:
So for you "adb remount" and push to /system works??
FOLLOWING PROBLEM:
I get the following error when I try "adb remount"
remount failed: Operation not permitted
HELP PLS
Click to expand...
Click to collapse
"adb remount" requires you to have the "ro.secure = 0" line in /default.prop on your tablet.

You need adbd insecure from Chainfire or KK-Boot boot image.

k1mu said:
"adb remount" requires you to have the "ro.secure = 0" line in /default.prop on your tablet.
Click to expand...
Click to collapse
Or you can use adb shell
Asuming your rooted, and mount -o rw, remount
Sent from my GT-P3113 using Tapatalk HD

sickysticky said:
Or you can use adb shell
Asuming your rooted, and mount -o rw, remount
Click to expand...
Click to collapse
Of course. (as long as you get it right: "mount -o remount,rw /system")
But the OP claimed that having to do that meant that ADB doesn't "fully work" because "adb remount" doesn't work. That requires ro.secure to be set to zero.

Related

ADB question

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

Root and ADB

My Xoom is rooted and running tiamat 1.41.
I'm trying to push a file onto the xoom and having trouble with it.
I have the Android SDK installed.
When I type ADB DEVICES, it shows my xoom listed as a long string of letters and numbers.
I figured out I could get into the shell by using ADB -s ###### shell (where #### is the numbers/letters shown as the device).
If I type remount, i get permission denied.
If I try to push a file onto the Xoom, I get permission denied.
What am I missing here and how do I mount the Xoom so that I can push files onto the it?
Anyone know where the libflashplayer.so goes? I have the official flash installed and don't see it in /system/lib
you have to cd into the directory where adb is. most people put it right on the root of there C drive so in terminal type "cd c:\android-sdk-windows\platform-tools" without quotes then type "adb remount" and you should be mounted
if you need more help with adb check out this guide http://androidsamurai.com/forum/viewtopic.php?f=12&t=4&sid=b8c229b771793d03bb84efbcf562e55b
I have tools and platform-tools directories in my PATH so I can run them from any directory. Even running it from the directory containing the executable fails with 'remount failed - operation not permitted'
you could try uninstalling and reinstalling android sdk
shobirama said:
If I type remount, i get permission denied.
If I try to push a file onto the Xoom, I get permission denied.
Click to expand...
Click to collapse
What does running "getprop ro.secure" say? (in adb shell/terminal on the tablet)
ydaraishy said:
What does running "getprop ro.secure" say? (in adb shell/terminal on the tablet)
Click to expand...
Click to collapse
Running getprop ro.secure in both adb shell and in terminal emulator on the tablet returns 1
shobirama said:
Running getprop ro.secure in both adb shell and in terminal emulator on the tablet returns 1
Click to expand...
Click to collapse
You're not in insecure mode. I thought flashing that kernel would put you into insecure mode? Maybe you need to reflash?
If you still actually have a working su binary, copy the file somewhere writeable, then su to root, then copy it from there again to the location.

Need help with adb :\

Hey everyone!
Recently I've had problems with using the command "adb remount". I thought it was a kernel problem but it happened with both Trinity and
Elementalx kernel. I have installed the universal naked drivers 0.73 for my nexus 5. I think it is a root problem since nothing pops up on my phone
when entering "adb root". I have tried to retype it several times and it doesn't say "adb is already running as root" or something like that like it used
to. It keeps repeating "restarting adbd as root" whenever I type that command. Sorry if I'm not clear :/
Thanks everyone!
I personally prefer to run adb via recovery. Have you tried this?
I have also failed to use remount in android.
The solution is as rootsu suggests.
Boot to recovery and do
Adb shell mount /system
Or
Adb shell mount /data
Which ever partition you want to be changing
Sent from my Nexus 5 using xda app-developers app
rootSU said:
I personally prefer to run adb via recovery. Have you tried this?
Click to expand...
Click to collapse
It does work that way but am I stuck on using this method?
Lxve said:
It does work that way but am I stuck on using this method?
Click to expand...
Click to collapse
I don't think so. It's just easier.
With SlimKat and elementalx*
I have adb and apps set as root in slimkat although I doubt this is a requirement in non-AOSP roms that do not have this option. Need USB debugging on and the screen unlocked
Code:
C:\Users\rootsu\Desktop\tools>adb root
adbd is already running as root
C:\Users\rootsu\Desktop\tools>adb shell
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # exit
exit
C:\Users\rootsu\Desktop\tools>adb push test.txt /system/
C:\Users\rootsu\Desktop\tools>adb shell
[email protected]:/ # cd system
cd system
[email protected]:/system # ls
ls
addon.d
app
bin
build.prop
core
etc
fonts
framework
lib
lost+found
media
priv-app
[B][COLOR="Red"][B]test.txt[/B][/COLOR][/B]
tts
usr
vendor
xbin
[email protected]:/system #

Root user cannot 'remount'

Hi,
after a lots of hassle I finally accessed the root access into my Sony z2 tablet. But the Root Checker Basic app says
Sorry! Root access is not properly installed on this device.
Click to expand...
Click to collapse
I can still run
Code:
adb root
without error. And the
Code:
adb shell whoami
returns "root".
Still when I run
Code:
adb remount
it says
remount of /system failed; couldn't make block device /dev/block/platform/msm_sdcc.1/by-name/system writable: Permission denied
remount failed
Click to expand...
Click to collapse
I need to remount the device because I want to move an APK to the "/system/priv-apps" folder.
Did you try remounting directly from an adb shell ?
mount -o remount,rw /system
ddscentral said:
Did you try remounting directly from an adb shell ?
mount -o remount,rw /system
Click to expand...
Click to collapse
Yes I tried. it says
mount: Operation not permitted
Click to expand...
Click to collapse
Toriq100 said:
Yes I tried. it says
Click to expand...
Click to collapse
Are you trying to mount as root ? (your shell prompt should start with # and not $). If not, use "su" command to get root and then try mounting again.
If remount fails even from a root shell, check your SELinux status with "getenforce" command.
ddscentral said:
Are you trying to mount as root ? (your shell prompt should start with # and not $). If not, use "su" command to get root and then try mounting again.
If remount fails even from a root shell, check your SELinux status with "getenforce" command.
Click to expand...
Click to collapse
Yes, I am trying to mount as root so that I can move an APK to "system/priv-apps". My shell prompt does start with #. I cannot use "su", it says "[-] Daemon is stop".
I checked SELinux status. It says "Enforcing", then I tried "adb shell setenforce 0" it says "setenforce: Couldn't set enforcing status to '0': Permission denied". :'(
Likely SELinux is preventing remount.
Are you still using the original software or a custom ROM ?
ddscentral said:
Likely SELinux is preventing remount.
Are you still using the original software or a custom ROM ?
Click to expand...
Click to collapse
Original software (I gained the root access using KingRoot, tried everything else, didn't work)
I would either flash SuperSU with a custom recovery (assuming you can unlock the bootloader) or flash a third party ROM.
ddscentral said:
I would either flash SuperSU with a custom recovery (assuming you can unlock the bootloader) or flash a third party ROM.
Click to expand...
Click to collapse
I tried recovering with custom ROM but failed. Here I asked a question for reference, but didn't find working solution.

"Not running as root. Try "adb root" first." despite trying "adb root" above

C:\Users\HieAnh>adb root
restarting adbd as root
C:\Users\HieAnh>adb remount
Not running as root. Try "adb root" first.
Click to expand...
Click to collapse
after i do :"adb root" to cmd,
then i get :"restarting adbd as root"
next i do :"adb remount"
but i get :"Not running as root. Try "adb root" first."
a big question for this problem
my phone is rooted, switch ro.secure=0, ro.debuggle=1
pls help me
What response do you get when you type su in shell?
ze7zez said:
What response do you get when you type su in shell?
Click to expand...
Click to collapse
i get :
C:\Users\HieAnh>adb shell
gracerlte:/ $ su
gracerlte:/ #
Click to expand...
Click to collapse
The ADB driver does not care at all whether phone's Android is rooted or not. As you correctly stated one have to run adb root for ADB to gain root access device's Android.
I don't want to examine why adb root in your case doesn't work.
Anyways the following should be a workaround:
Code:
adb devices
adb shell "su -c 'mount -o remount,rw /system'"
...
...
jwoegerbauer said:
The ADB driver does not care at all whether phone's Android is rooted or not. As you correctly stated one have to run adb root for ADB to gain root access device's Android.
I don't want to examine why adb root in your case doesn't work.
Anyways the following should be a workaround:
Code:
adb devices
adb shell "su -c 'mount -o remount,rw /system'"
...
...
Click to expand...
Click to collapse
hmm, i just run
adb pull /data/data
Click to expand...
Click to collapse
but i get
/data/data/: 0 files pulled, 0 skipped.
Click to expand...
Click to collapse
why ?
You have to mount /data partitton as RW.

Categories

Resources