Database Info

[Q] adb install myapp.apk failed after ROOT

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.

[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?

Can't mount filesystem in RW mode

I m unable to mount my filesystem in rw mode, I have used so many scripts in order to remount it rw, terminal emulator displays that's its in rw mode but when I chmod a file in xbin or try to to create a folder it displays read-only filesystem. I have used few scripts & terminal commands but to no avail also on Supersu beta. I m using s3 Verizon with the latest safestrap(twrp) recovery. Please help !!!

Android P preview5 rooted, gain su,but i/o error after remount /vendor partition

Have flash my new pixel 2 with latest android P preview5, rooted with twrp and magisk 16.04, I can get su under adb shell
I can remount the system as rw but fail in /vendor, an mount: '/dev/block/dm-0'->'/vendor': I/O error is coming accross
130|walleye:/ $ su
walleye:/ # mount -o rw,remount -t auto /system
walleye:/ # mount -o rw,remount -t auto /vendor
mount: '/dev/block/dm-0'->'/vendor': I/O error
1|walleye:/ # cp /mnt/sdcard/xxxx.so /vendor/etc
cp: /vendor/etc/xxx.so: Read-only file system
I'm pretty sure this is working in a rooted pixel XL of android OREO,
copy the file in TWRP file manager can't work either, I can see the file is copied into the vendor in TWRP, but file gone away after reboot into system, any suggestion is pretty appreciated !

misslebulletttttt said:
Have flash my new pixel 2 with latest android P preview5, rooted with twrp and magisk 16.04, I can get su under adb shell
I can remount the system as rw but fail in /vendor, an mount: '/dev/block/dm-0'->'/vendor': I/O error is coming accross
130|walleye:/ $ su
walleye:/ # mount -o rw,remount -t auto /system
walleye:/ # mount -o rw,remount -t auto /vendor
mount: '/dev/block/dm-0'->'/vendor': I/O error
1|walleye:/ # cp /mnt/sdcard/xxxx.so /vendor/etc
cp: /vendor/etc/xxx.so: Read-only file system
I'm pretty sure this is working in a rooted pixel XL of android OREO,
copy the file in TWRP file manager can't work either, I can see the file is copied into the vendor in TWRP, but file gone away after reboot into system, any suggestion is pretty appreciated !
Click to expand...
Click to collapse
Why not use the latest magisk? Btw this is the wrong section.
Sent from my Pixel 2 using Tapatalk

joetheshmo said:
Why not use the latest magisk? Btw this is the wrong section.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Have tried magisk 16.7, but in vain, system partition can be remounted as "RW", however not the case in /vendor,
any tool can help to remount a partition during runtime ?

I found disable AVB2.0 / dm-verity can do the trick, now I can remount /vendor partition without I/O error !

If i can ever get my Gf to stop playing with my pixel 2 ( she has an iphone ). Ill update from DP4>DP5 and see how far i get.

Im having no issues after the update.
- flashed DP5 with Deuces Script.
- Flashed Twrp 3.2.2
-Booted system to setup initially.
-Booted to twrp installed Magisk 16.7
-reboot system .
havent had an I/O error. rooted fine.

misslebulletttttt said:
I found disable AVB2.0 / dm-verity can do the trick, now I can remount /vendor partition without I/O error !
Click to expand...
Click to collapse
after unchecking Preserve AVB v2.0/dm-verity in app, Magisk needs to be reinstalled. Quoted from here:
in Magisk Manager, “Uninstall > Restore Images” to restore the images, check “Preserve AVB 2.0/dm-verity” box in Advanced Settings, then reinstall Magisk via the app.

Can't mount vendor and system image as RW

I try to mount system and vendor partitions by using command below
Code:
sudo mount -o loop -t ext4 vendor.img vendor
got this error message
Code:
mount: xxx/xxx/vendor: wrong fs type, bad option, bad superblock on /dev/loop20, missing codepage or helper program, or other error
This command use to work on system image on different phone with same android version.
But I'm able to mount as RO using achieve mounter on Ubuntu.
Is there any way that I can mount those image as RW then edit some file in there?

OOS locks the system partition. No way in as of yet.

BeardKing said:
OOS locks the system partition. No way in as of yet.
Click to expand...
Click to collapse
Thank you