[Q] adb install myapp.apk failed after ROOT - Eee Pad Transformer Q&A, Help & Troubleshooting

Hi,
I have my TF101 upgraded to ICS and ROOT with Rogue XM 1.5.0.
Before root I tried 'adb install myapp.apk' and installed the application successfuly. I have uninstalled myapp and then tried the same after root and got:
failed to copy 'myapp.apk' to '/data/local/tmp/myapp.apk': Not a directory
rm failed for /data/local/tmp/myapp.apk, Not a directory
Looking into /data/local I can see a tmp.bak folder and a tmp file. What can I do to be able to install applications using adb as before root?
Regards.

I found that tmp file is a link to /dev/block/mmcblk0p4 but after I ran mount I didn't find it mounted:
.................
/dev/block/mmcblk0p1 /system ext4 ......
/dev/block/mmcblk0p7 /data ext4 .........
/dev/block/mmcblk0p2 /cache ext4 ..........
.............................
Do you have any idea what I can do in order to be able installing apk's using adb install? Is it ok to delete tmp link file and create a tmp folder with proper permissions?
Thanks in advance.

Related

Rc29 - No Root Accesss.

So, nobody answered and I had to create this topic.
1) I have RC29
2) When I try to use the MOUNT command in pTerminal I ALWAYS get:
roootfs / rootfs ro 0 0
etc.
3) When I use
mount -o remount rw /system
I ALWAYS get:
mount: Operation not permitted.
4) When:
cd /system
cat /sdcard/recovery_testkeys.img > recovery.img
I ALWAYS get:
cannot create recovery.img: read-only file system
PS All files are there. The update's name is written right - update.zip. I've used pTerminal.
So, do I have the Root Access or not and am i doing smth wrong??
Appreciate any help\advices.
Thanks.
Have you tried doing this through the telnetd way?
BAD_BOY_KIEV said:
So, nobody answered and I had to create this topic.
1) I have RC29
2) When I try to use the MOUNT command in pTerminal I ALWAYS get:
roootfs / rootfs ro 0 0
etc.
3) When I use
mount -o remount rw /system
I ALWAYS get:
mount: Operation not permitted.
4) When:
cd /system
cat /sdcard/recovery_testkeys.img > recovery.img
I ALWAYS get:
cannot create recovery.img: read-only file system
PS All files are there. The update's name is written right - update.zip. I've used pTerminal.
So, do I have the Root Access or not and am i doing smth wrong??
Appreciate any help\advices.
Thanks.
Click to expand...
Click to collapse
You have to use the telnetd command first to exploit the root access. There are other threads that tell you how. Basically telnet into the phone then execute the commands.
If you look in your PM box. i sent you a link with step by step instructions yesterday!
Cannot root RC29 - read only file error
Hi,
I did it also thru Telnet but get the same message...any tips to root the phone? I am still sending that automatic SMS...
Thanks, M

how do i move a file to /system/bin ?

i rooted my verizon galaxy tab and i can run Root apps, but i cant move a wpa_supplicant file to my /system/root using Astro.
Is this a root issue or do i need something better than Astro? I also tried OI file manager but it just says "cannot move file here".
By default, /system is (usually) mounted read-only. You probably need to remount it read-write.
Code:
adb remount /system
adb push [path-to-file] /system/bin
If remount doesn't work, try
Code:
adb shell mount -t yaffs2 -o rw,remount /dev/block/mtdblock3 /system

Rooted phone, cannot mount /system as rw

I have rooted my phone, it has /system/bin/su but I am unable to actually utilize its functionality. For example, I cannot install openvpn, busybox, a custom /etc/hosts file.
I can run adb remount and when I run "mount|grep system" it shows it being mounted as rw. Then I can write files as normally, but when I reboot, everything is back to its default.
Output of mount|grep system:
/dev/block/mmcblk0p33 /system ext4 ro,seclabel,noatime,data=ordered 0 0
After running adb remount:
/dev/block/mmcblk0p33 /system ext4 rw,seclabel,noatime,data=ordered 0 0
But when I install busybox, nothing is installed into /system/xbin
Anyone know what is up? Using HTC Sense 5.5 on an HTC One mini.

[Q] Restore build.prop can't mount system rw

I have an apex solo 7i (TM772) and I was able to gain root access from adb only. I modified the build.prop file and it is now stuck in a boot loop.
I have the original build.prop file on my PC (I also have the entire /system directory) but from recovery mode the only adb access I can get is to side load a zip.
I can access fastboot through droidboot.
During the boot loop it is found as a device (in production builds so I can not use the "adb root" command).
With the adb device shell I can use the su command, but while trying to mount the system rw it fails and says:
Code:
# mount -o rw,remount -t yaffs2 /dev/block/mccblk0p8 /system
mount: Operation not permitted
Is there any way to make it mount the system partition rw or could I make a flashable zip file to restore the build.prop?

Mount system partition RW

I have tested MIUI 10 and Android P DP2, but, with TWRP and Magisk there is no way to edit file or make any modifications to /system and subdirectory.
In terminal emulator I receive a error "Read-only file system".
I've already tried to sent "mount -o rw,remount /system", but I receive a error "'/dev/block/dm-0' is read-only". This is the permissions of /dev/block/dm-0:
brw------- 1 root root
How can I edit system file?
Up
i have the same problem with vendor partition.
i need write on it for using a NFC CARD EMULATOR
Yes, I have same issue. Any solution?
with xiaomi.eu i dont have this problem

Categories

Resources