[Q] i need help with my webtop~ - Motorola Atrix 2

i've read the <get full ubuntu and your favorite desktop in webtop>
but i've got some problems like this
tar: ./usr/lib/xorg: Cannot change mode to rwxr-xr-x: Read-only file system
tar: ./usr/lib/firefox-8.0/distribution: Cannot utime: Read-only file system
tar: ./usr/lib/firefox-8.0/distribution: Cannot change ownership to uid 0, gid 0
: Read-only file system
tar: ./usr/lib/firefox-8.0/distribution: Cannot change mode to rwxr-xr-x: Read-o
nly file system
tar: ./usr/lib/firefox-8.0: Cannot utime: Read-only file system
tar: ./usr/lib/firefox-8.0: Cannot change ownership to uid 0, gid 0: Read-only f
ile system
tar: ./usr/lib/firefox-8.0: Cannot change mode to rwxr-xr-x: Read-only file syst
em
tar: ./usr/lib: Cannot utime: Read-only file system
tar: ./usr/lib: Cannot change ownership to uid 1001, gid 1001: Read-only file sy
stem
tar: ./usr/lib: Cannot change mode to rwxr-xr-x: Read-only file system
tar: ./usr/bin: Cannot utime: Read-only file system
tar: ./usr/bin: Cannot change ownership to uid 1001, gid 1001: Read-only file sy
stem
tar: ./usr/bin: Cannot change mode to rwxr-xr-x: Read-only file system
tar: ./usr: Cannot utime: Read-only file system
tar: ./usr: Cannot change ownership to uid 1001, gid 1001: Read-only file system
tar: ./usr: Cannot change mode to rwxr-xr-x: Read-only file system
tar: .: Cannot utime: Read-only file system
tar: .: Cannot change ownership to uid 0, gid 0: Read-only file system
tar: .: Cannot change mode to rwxr-xr-x: Read-only file system
tar: Error exit delayed from previous errors
unmounting your sdcard from the temp mount, now that we are done copying all the
files.
Now we will mount the sdcard with webtop copied over to it, to the correct place
, so we can patch it, and remove the FACLs and MACLs. These are what prevent you
accessing application and making changes in the ubuntu install.
mount: wrong fs type, bad option, bad superblock on /dev/block/mmcblk0p2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
We are done and your phone will now reboot, go visit the xda-developers thread a
nd perform the next steps when your phone starts back up.
link_image[1964]: 5631 could not load needed library 'liblog.so' for '/system/b
in/reboot' (link_image[1964]: 5631 could not load needed library 'libgcc_s.so.1
' for 'liblog.so' (load_library[1106]: Library 'libgcc_s.so.1' not found))CANNOT
LINK EXECUTABLE
help me,please~

I already replied to your other thread. Please go look at that one, this is a duplicate post. Please have this thread deleted.
Take a look here, at your original thread, where I have replied and asked for more information:
http://forum.xda-developers.com/showthread.php?t=1685086

Related

Speedtweak.sh

export PATH=/data/local/bin:$PATH
# export PATH=/data/local/bin:$PATH
#speedtweak.sh
mount: permission denied (are you root)
You appear to be running safe mode.
---
Please enter a number: 5
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
Unable to chmod /system/etc/init.d/01vdd_levels: Read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
This is what I get when tried to make battery saver I look everywhere could not find the answer
go on the terminal on your phone...
type "su" then hit enter
then type "speedtweak.sh"
and go from there
I will try that
Sent from my ADR6400L using XDA App
Please enter a number: 5
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
Unable to chmod /system/etc/init.d/01vdd_levels: Read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
/sbin/speedtweak.sh: cannot create /system/etc/init.d/01vdd_levels: read-only file system
You appear to be running normal before it was showing running in safe mode
Now I get this only
Sent from my ADR6400L using XDA App
Are you sure root is working? Open a different app that requires root and try to use it.
Yes all my apps that require root access are working like cache cleaner titanium back ect..
Sent from my ADR6400L using XDA App

[Q] repack-zImage.sh

I am trying to use the script in this post to unpack the kernel and I get a bunch of errors that look like this:
Code:
Unpacking initramfs
9923 blocks
cpio: misc: Cannot change mode to rwsrwsrwx: Operation not permitted
cpio: busybox: Cannot symlink to `sbin/chgrp': Operation not permitted
cpio: busybox: Cannot symlink to `sbin/uuencode': Operation not permitted
cpio: busybox: Cannot symlink to `sbin/printenv': Operation not permitted
cpio: busybox: Cannot symlink to `sbin/df': Operation not permitted
cpio: ../init: Cannot symlink to `sbin/ueventd': Operation not permitted
And I was wondering if anyone would know if that's normal or if something's wrong.
I did post this in the above mentioned thread, but it's pretty old so I'm not sure if I was going to get an answer from it.

how can i get full ubuntu??

there are some problem with my webtop when i want get full ubuntu....like this
tar: ./usr: Cannot change mode to rwxr-xr-x: Read-only file system
tar: .: Cannot utime: Read-only file system
tar: .: Cannot change ownership to uid 0, gid 0: Read-only file system
tar: .: Cannot change mode to rwxr-xr-x: Read-only file system
tar: Error exit delayed from previous errors
unmounting your sdcard from the temp mount, now that we are done copying all the
files.
Now we will mount the sdcard with webtop copied over to it, to the correct place
, so we can patch it, and remove the FACLs and MACLs. These are what prevent you
accessing application and making changes in the ubuntu install.
help me
You need to mount the system as read/write.
In adb type.
su
mount -o remount, rw
Sent from my Atrixperia using xda premium
z652366 said:
there are some problem with my webtop when i want get full ubuntu....like this
tar: ./usr: Cannot change mode to rwxr-xr-x: Read-only file system
tar: .: Cannot utime: Read-only file system
tar: .: Cannot change ownership to uid 0, gid 0: Read-only file system
tar: .: Cannot change mode to rwxr-xr-x: Read-only file system
tar: Error exit delayed from previous errors
unmounting your sdcard from the temp mount, now that we are done copying all the
files.
Now we will mount the sdcard with webtop copied over to it, to the correct place
, so we can patch it, and remove the FACLs and MACLs. These are what prevent you
accessing application and making changes in the ubuntu install.
help me
Click to expand...
Click to collapse
Hi,
I assume you are using my how-to?
I have a few questions, and need you to get me a few things as well, before I can be of more help.
1) I assume you are already rooted? Are you already rooted?
2) Do you have busybox installed? And have it in /system/bin, and not /system/xbin?
3) Did you run my script as root?
I am thinking that it is either just that you are not running this as root, or that your root install did not work.
Can you run the following commands from the command line on your computer, with your phone connected and post them back in here?
Code:
adb shell
su
cd /data/local
id
busybox df -h
ls -l
mount -o remount, rw /system
touch /system/bin/test
rm /system/bin/test
exit
exit
Post the output back in here, and we will see if there is an issue with your root access.
Each line is a single command, and you must ONLY copy one line and paste it to one command line, do NOT copy all of the commands and paste them to your command line window, it will not work.

[Q] Unable to root Huawei MediaPad 7

hi all,
I am trying very hard to root my huawei mediapad but not getting success.
Following are my setup -
My device - Huawei MediaPad 7
OS - Android 4.0.3
I have enabled USB debugging mode
My PC is on Windows 7 Home Premium.
I following so many posts for rooting this device. I followed the following posts.
Link1
Link2
In link1, i downloaded the zip file and run the Install Root.cmd script. But it shows me following errors
Code:
failed on '/data/local/tmp' - Permission denied
link failed File exists
ÅÑαѺáúαπªáѼ (1/3)
/system/bin/sh: cannot create /data/local.prop: Permission denied
ÅÑαѺáúαπªáѼ (2/3)
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
sh: /system/xbin/install_bb: No such file or directory
rm failed for /system/xbin/install_bb, No such file or directory
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
ÅÑαѺáúαπªáѼ (3/3)
éßÑ ú«Γ«ó«!!!
Press any key to continue . . .
On Link2 - the download link does not work and shows error as follows
Code:
Oops! Google Chrome could not connect to depositfiles.com
Suggestions:
Access a cached copy of depositfiles.*com/*files/*9f8mfimjz
Try reloading: depositfiles.*com/*files/*9f8mfimjz
Search on Google:
Someone please help.

Can't access RUU mode (goes directly to bootloop)

Hello,
(English is not my mother tongue but I’ll try to do my best )
I don’t usually ask for help and do my own researchs, but I reached a dead end! So I need some experts here
My Nexus got stolen 3 days ago, so I took back my HTC Sensation from the drawer to use it again for some time. When I was using it before, I flashed 3 or 4 differents roms, I updated the firmware, and so on… Never had a single problem, but I don’t know what I did when I switched with my Nexus, but when I tried to power on my Sensation today, it got stuck on cyanogen boot.
I tried to access the recovery (4ext recovery touch) with ADB, and it worked, so I was kind of relieved! I wiped everything I needed to wipe (following instructions for the rom) and that was unusually long! VERY long! In my memories it took only few minutes to do that, and now it takes 1 hour (actually every action I perform with the recovery takes at least 50 minutes. Was not the case before)! But it goes all the way and I had a success message, so okay.
I tried to flash the rom again (the one I had before and knew it worked), it took once again a very long time to install, but success message at the end. I rebooted and... still stuck on boot loop.
I, then, tried to change the recovery (from 4ext to twrp) (with fastboot), everything went fine (no error during the process), when I rebooted, I was still with the same recovery (4ext). (I also tried to access directly to the recovery without rebooting because I read it was maybe because of the reboot but it’s the same).
I also tried to change the firmware (PG58IMG) from 3.33 to 3.32, I flashed it, process is okay, I rebooted, and… still on 3.33
I finally tried to flash an official ROM from HTC, it worked once again during the process, but the boot screen was… Cyanogen boot, and still boot loop ???
So, I can do anything I want, I don’t get any message of errors, but nothing changes! Nor the firmeware, nor the recovery, nor the rom (which doesn’t work). I’m completely stuck… I tried, and tried again… No apparent changes on my phone.
My last attempt was going to be with RUU, but I can’t find one that fits my configuration :/
Thank you for any help, I’m desesperate :/
For information, this is what my bootloader looks like :
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012, 17:33:34
EDIT :
Before I post this, I tried one last thing :
In the recovery (4ext), I formatted all partitions (except sdcard) - no error during the process.
But when I check the info I have :
mount point | fs | size | free
system | ext4 | 787.4mb | 295.4mb
data | ext4 | 1.1gb | 132.0mb
cache | ext4 | 118.1mb | 114.0mb
sdcard | fat32 | 7.2gb | 4.3gb
Current ROM : 11-20140525-Sultan-pyramid
How is that possible? I just wiped everything, and it did nothing. :crying:
since you are on S-OFF you can use any ruu you want
here is the latest 4ext recovery version
http://d-h.st/rG7
extarct the recovery.img and flash it via fatsboot
then try to wipe again
Ok, I flashed it like you said, but once again, no changes! I'm still on the version 1.0.0.6 RC2 (and not RC3)
I'm going to try with a RUU
did the info change in recovery? u know system,cache, current rom info etc? coz when u full wipe then check info it doesnt change untill u reboot recovery.
No the info doesn't change. Even after a reboot.
Okay so I tried with RUU. First with the .exe file : Everything goes well until the first step when the RUU wants to reload to the bootloader. I have an error 171. I don't think it's a driver problem because it recognized the phone before that step.
1. I am in fastboot usb.
2. I execute the .exe
3. It finds the phone and ask me to update
4. RUU says "reboot in bootloader" - my phone turns off
5. RUU says "waiting for bootloader" - my phone does not turn on in bootloader
6. RUU says 'failed error 171 usb connection error"
So I guess once the phone is turned off, it can't find it anymore. During the "waiting for bootloader" step, I also tried to help the RUU and rebooting to the bootloader myself (either with adb and the combination VOLUME - and Power on), the phone restart but the RUU doesn't detect the bootloader and fails.
I tried to flash the RUU manually as well, with PG58IMG in the bootloader, but the phone turns off before the process is finished, and changes nothing.
And with adb, I'm stuck when I ask to "fastboot oem rebootRUU". The phone turns off and doesn't reboot into RUU mode.
(I followed this guide (4.4.2 With a PC, via fastboot USB) : http://forum.xda-developers.com/showthread.php?t=1672425)
EDIT : Different problem now : The RUU can reboot my phone, but not in RUU mode, my phone restart to the bootloop (the rom which doesn't work)
I retrieved the recovery.log from 4ext for a ROM I tried to flash a couple of days ago, and I see a lot of "failed to" - "not such file or directory" - "read-only file system" - "unmount of /system failed" - ... So I put it here maybe it could help to understand the problem!
Code:
Starting recovery on Fri Jan 2 00:00:00 1970
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
Welcome to 4EXT Recovery Touch
by madmaxx82
I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 1I:st.f_bsize: 4096
I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p20 (null)
3 /cache ext4 /dev/block/mmcblk0p24 (null)
4 /data ext4 /dev/block/mmcblk0p23 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext4 /dev/block/mmcblk0p22 (null)
7 /misc emmc /dev/block/mmcblk0p31 (null)
I:end load volumes..
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
Command: "/sbin/recovery"
ro.build.date=Thu May 8 17:34:43 CEST 2014
ro.build.date.utc=0
ro.product.model=HTC Sensation
ro.product.brand=htc
ro.product.name=htc_pyramid
ro.product.device=pyramid
ro.product.board=pyramid
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.board.platform=msm8660
ro.build.product=pyramid
ro.com.android.dateformat=MM-dd-yyyy
net.bt.name=Android
ro.serialno=SH1BTV809020
ro.baseband=11.24A.3504.31_M
ro.carrier=HTC-FRA
ro.bootloader=1.27.1100
ro.cid=HTC__203
ro.mid=PG5813000
init.svc.choice_fn=stopped
init.svc.htcbatt=running
init.svc.adbd=running
init.svc.recovery=running
ext.version="1006.2.0"
ext.feature.version_check=yes
ext.build=33
ext.edition=ng
I:preparing..
Preparing boot.. 1I:prep sys1: 0
Preparing boot.. 1 Preparing boot.. 2 Preparing boot.. 2 Preparing boot.. 2 Preparing boot.. 2 Preparing boot.. 2 Preparing boot.. 3 Preparing boot.. 3I:preparing.. fin
Preparing boot.. 3 Configuring settings..
Your configuration settings:
Using button backlights level: 90
4EXT SmartFlash: enabled
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: disabled
Backups: exclude dalvik-cache: disabled
Preserve theme: enabled
Hide useless directories: disabled
Haptic feedback: enabled
Haptic feedback strength: 25
Timezone: configured
Using 24h-hour time format
I:theme propok
Recovery is ready..
I:have tz_data
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
About to install:
Sensation_3.33.401.53_odexed.zip
Continue install?
-- Installing: /sdcard/Sensation_3.33.401.53_odexed.zip
Finding update package...
I:Update location: /sdcard/Sensation_3.33.401.53_odexed.zip
Opening update package...
Installing update...
unmount of /system failed; no such volume
Creating filesystem with parameters:
Size: 838859776
Block size: 4096
Blocks per group: 32768
Inodes per group: 7315
Inode size: 256
Journal blocks: 3200
Label:
Blocks: 204799
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/51205 inodes and 6651/204799 blocks
===============================================
| Android Revolution HD |
| by mike1986 |
| Be patient - 1st boot may take a while |
===============================================
>>> Formatting partitions
(system is unmounted already)
Creating filesystem with parameters:
Size: 125787136
Block size: 4096
Blocks per group: 32768
Inodes per group: 7677
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 30709
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/7677 inodes and 1518/30709 blocks
>>> Mounting partitions
>>> Cleaning process
minzip: Extracted file "/system/app/AdobeReader.apk"
minzip: Extracted file "/system/app/AppSharing.apk"
minzip: Extracted file "/system/app/AppSharing.odex"
minzip: Extracted file "/system/app/ApplicationsProvider.apk"
minzip: Extracted file "/system/app/ApplicationsProvider.odex"
minzip: Extracted file "/system/app/BackupRestoreConfirmation.apk"
minzip: Extracted file "/system/app/BackupRestoreConfirmation.odex"
>>> Writing Data & System
minzip: Extracted file "/system/app/BlueSky.apk"
minzip: Extracted file "/system/app/Bluetooth.apk"
minzip: Extracted file "/system/app/Bluetooth.odex"
minzip: Extracted file "/system/app/BrcmBluetoothServices.apk"
minzip: Extracted file "/system/app/BrcmBluetoothServices.odex"
minzip: Error touching "/system/app/Browser.apk"
>>> Creating toolbox symlinks
symlink: failed to remove /system/bin/cat: Read-only file system
symlink: failed to symlink /system/bin/cat to toolbox: File exists
symlink: failed to remove /system/bin/chmod: Read-only file system
symlink: failed to symlink /system/bin/chmod to toolbox: File exists
symlink: failed to remove /system/bin/chown: Read-only file system
symlink: failed to symlink /system/bin/chown to toolbox: File exists
symlink: failed to remove /system/bin/cmp: Read-only file system
symlink: failed to symlink /system/bin/cmp to toolbox: File exists
symlink: failed to remove /system/bin/date: Read-only file system
symlink: failed to symlink /system/bin/date to toolbox: File exists
symlink: failed to remove /system/bin/dd: Read-only file system
symlink: failed to symlink /system/bin/dd to toolbox: File exists
symlink: failed to remove /system/bin/df: Read-only file system
symlink: failed to symlink /system/bin/df to toolbox: File exists
symlink: failed to remove /system/bin/dmesg: Read-only file system
symlink: failed to symlink /system/bin/dmesg to toolbox: File exists
symlink: failed to remove /system/bin/getevent: Read-only file system
symlink: failed to symlink /system/bin/getevent to toolbox: File exists
symlink: failed to remove /system/bin/getprop: Read-only file system
symlink: failed to symlink /system/bin/getprop to toolbox: File exists
symlink: failed to remove /system/bin/hd: Read-only file system
symlink: failed to symlink /system/bin/hd to toolbox: File exists
symlink: failed to remove /system/bin/id: Read-only file system
symlink: failed to symlink /system/bin/id to toolbox: File exists
symlink: failed to remove /system/bin/ifconfig: Read-only file system
symlink: failed to symlink /system/bin/ifconfig to toolbox: File exists
symlink: failed to remove /system/bin/iftop: Read-only file system
symlink: failed to symlink /system/bin/iftop to toolbox: File exists
symlink: failed to remove /system/bin/insmod: Read-only file system
symlink: failed to symlink /system/bin/insmod to toolbox: File exists
symlink: failed to remove /system/bin/ioctl: Read-only file system
symlink: failed to symlink /system/bin/ioctl to toolbox: File exists
symlink: failed to remove /system/bin/ionice: Read-only file system
symlink: failed to symlink /system/bin/ionice to toolbox: File exists
symlink: failed to remove /system/bin/kill: Read-only file system
symlink: failed to symlink /system/bin/kill to toolbox: File exists
symlink: failed to remove /system/bin/ln: Read-only file system
symlink: failed to symlink /system/bin/ln to toolbox: File exists
symlink: failed to remove /system/bin/log: Read-only file system
symlink: failed to symlink /system/bin/log to toolbox: File exists
symlink: failed to remove /system/bin/ls: Read-only file system
symlink: failed to symlink /system/bin/ls to toolbox: File exists
symlink: failed to remove /system/bin/lsmod: Read-only file system
symlink: failed to symlink /system/bin/lsmod to toolbox: File exists
symlink: failed to remove /system/bin/lsof: Read-only file system
symlink: failed to symlink /system/bin/lsof to toolbox: File exists
symlink: failed to remove /system/bin/mkdir: Read-only file system
symlink: failed to symlink /system/bin/mkdir to toolbox: File exists
symlink: failed to remove /system/bin/mount: Read-only file system
symlink: failed to symlink /system/bin/mount to toolbox: File exists
symlink: failed to remove /system/bin/mv: Read-only file system
symlink: failed to symlink /system/bin/mv to toolbox: File exists
symlink: failed to remove /system/bin/nandread: Read-only file system
symlink: failed to symlink /system/bin/nandread to toolbox: File exists
symlink: failed to remove /system/bin/netstat: Read-only file system
symlink: failed to symlink /system/bin/netstat to toolbox: File exists
symlink: failed to remove /system/bin/newfs_msdos: Read-only file system
symlink: failed to symlink /system/bin/newfs_msdos to toolbox: File exists
symlink: failed to remove /system/bin/notify: Read-only file system
symlink: failed to symlink /system/bin/notify to toolbox: File exists
symlink: failed to remove /system/bin/printenv: Read-only file system
symlink: failed to symlink /system/bin/printenv to toolbox: File exists
symlink: failed to remove /system/bin/ps: Read-only file system
symlink: failed to symlink /system/bin/ps to toolbox: File exists
symlink: failed to remove /system/bin/reboot: Read-only file system
symlink: failed to symlink /system/bin/reboot to toolbox: File exists
symlink: failed to remove /system/bin/renice: Read-only file system
symlink: failed to symlink /system/bin/renice to toolbox: File exists
symlink: failed to remove /system/bin/rm: Read-only file system
symlink: failed to symlink /system/bin/rm to toolbox: File exists
symlink: failed to remove /system/bin/rmdir: Read-only file system
symlink: failed to symlink /system/bin/rmdir to toolbox: File exists
symlink: failed to remove /system/bin/rmmod: Read-only file system
symlink: failed to symlink /system/bin/rmmod to toolbox: File exists
symlink: failed to remove /system/bin/route: Read-only file system
symlink: failed to symlink /system/bin/route to toolbox: File exists
symlink: failed to remove /system/bin/schedtop: Read-only file system
symlink: failed to symlink /system/bin/schedtop to toolbox: File exists
symlink: failed to remove /system/bin/sendevent: Read-only file system
symlink: failed to symlink /system/bin/sendevent to toolbox: File exists
symlink: failed to remove /system/bin/setconsole: Read-only file system
symlink: failed to symlink /system/bin/setconsole to toolbox: File exists
symlink: failed to remove /system/bin/setprop: Read-only file system
symlink: failed to symlink /system/bin/setprop to toolbox: File exists
symlink: failed to remove /system/bin/sleep: Read-only file system
symlink: failed to symlink /system/bin/sleep to toolbox: File exists
symlink: failed to remove /system/bin/smd: Read-only file system
symlink: failed to symlink /system/bin/smd to toolbox: File exists
symlink: failed to remove /system/bin/start: Read-only file system
symlink: failed to symlink /system/bin/start to toolbox: File exists
symlink: failed to remove /system/bin/stop: Read-only file system
symlink: failed to symlink /system/bin/stop to toolbox: File exists
symlink: failed to remove /system/bin/sync: Read-only file system
symlink: failed to symlink /system/bin/sync to toolbox: File exists
symlink: failed to remove /system/bin/top: Read-only file system
symlink: failed to symlink /system/bin/top to toolbox: File exists
symlink: failed to remove /system/bin/touch: Read-only file system
symlink: failed to symlink /system/bin/touch to toolbox: File exists
symlink: failed to remove /system/bin/umount: Read-only file system
symlink: failed to symlink /system/bin/umount to toolbox: File exists
symlink: failed to remove /system/bin/uptime: Read-only file system
symlink: failed to symlink /system/bin/uptime to toolbox: File exists
symlink: failed to remove /system/bin/vmstat: Read-only file system
symlink: failed to symlink /system/bin/vmstat to toolbox: File exists
symlink: failed to remove /system/bin/watchprops: Read-only file system
symlink: failed to symlink /system/bin/watchprops to toolbox: File exists
symlink: failed to remove /system/bin/wipe: Read-only file system
symlink: failed to symlink /system/bin/wipe to toolbox: File exists
symlink: failed to remove /system/bin/sh: Read-only file system
symlink: failed to symlink /system/bin/sh to /system/bin/mksh: File exists
symlink: failed to remove /system/fonts/DroidSans.ttf: Read-only file system
symlink: failed to symlink /system/fonts/DroidSans.ttf to /system/fonts/Roboto-Regular.ttf: File exists
symlink: failed to remove /system/fonts/DroidSans-Bold.ttf: Read-only file system
symlink: failed to symlink /system/fonts/DroidSans-Bold.ttf to /system/fonts/Roboto-Bold.ttf: File exists
symlink: failed to remove /system/vendor/firmware/hdcp.keys: Read-only file system
symlink: failed to symlink /system/vendor/firmware/hdcp.keys to /factory/hdcp.keys: Read-only file system
set_perm: chown of /system/bin/iptables to 0 1000 failed: Read-only file system
set_perm: chmod of /system/bin/iptables to 4750 failed: Read-only file system
set_perm: chown of /system/bin/netcfg to 0 3003 failed: Read-only file system
set_perm: chmod of /system/bin/netcfg to 2750 failed: Read-only file system
set_perm: chown of /system/bin/ping to 0 3004 failed: Read-only file system
set_perm: chmod of /system/bin/ping to 2755 failed: Read-only file system
set_perm: chown of /system/bin/reboot to 0 2000 failed: Read-only file system
set_perm: chmod of /system/bin/reboot to 6755 failed: Read-only file system
set_perm: chown of /system/bin/run-as to 0 2000 failed: Read-only file system
set_perm: chmod of /system/bin/run-as to 6750 failed: Read-only file system
set_perm: chown of /system/bin/tc to 0 1000 failed: Read-only file system
set_perm: chmod of /system/bin/tc to 4750 failed: Read-only file system
set_perm: chown of /system/etc/bluetooth to 0 0 failed: Read-only file system
set_perm: chmod of /system/etc/bluetooth to 755 failed: Read-only file system
set_perm: chown of /system/etc/bluetooth/a2dp_avrcp.conf to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/bluetooth/a2dp_avrcp.conf to 644 failed: No such file or directory
set_perm: chown of /system/etc/bluetooth/auto_pairing.conf to 1000 1000 failed: No such file or directory
set_perm: chmod of /system/etc/bluetooth/auto_pairing.conf to 640 failed: No such file or directory
set_perm: chown of /system/etc/bluetooth/blacklist.conf to 3002 3002 failed: No such file or directory
set_perm: chmod of /system/etc/bluetooth/blacklist.conf to 444 failed: No such file or directory
set_perm: chown of /system/etc/dbus.conf to 1002 1002 failed: No such file or directory
set_perm: chmod of /system/etc/dbus.conf to 440 failed: No such file or directory
set_perm: chown of /system/etc/dhcpcd/dhcpcd-run-hooks to 1014 2000 failed: Read-only file system
set_perm: chmod of /system/etc/dhcpcd/dhcpcd-run-hooks to 550 failed: Read-only file system
set_perm: chown of /system/etc/init.goldfish.sh to 0 2000 failed: No such file or directory
set_perm: chmod of /system/etc/init.goldfish.sh to 550 failed: No such file or directory
set_perm: chown of /system/etc/init.qcom.sdio.sh to 1000 1000 failed: No such file or directory
set_perm: chmod of /system/etc/init.qcom.sdio.sh to 555 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/left_eye-y0-yi45-p0-pi45-r0-ri20.2d_n2/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/left_eye-y0-yi45-p0-pi45-r0-ri20.2d_n2/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/left_eye-y0-yi45-p0-pi45-rn7-ri20.2d_n2/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/left_eye-y0-yi45-p0-pi45-rn7-ri20.2d_n2/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/left_eye-y0-yi45-p0-pi45-rp7-ri20.2d_n2/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/left_eye-y0-yi45-p0-pi45-rp7-ri20.2d_n2/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/nose_base-y0-yi45-p0-pi45-r0-ri20.2d_n2/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/nose_base-y0-yi45-p0-pi45-r0-ri20.2d_n2/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/nose_base-y0-yi45-p0-pi45-rn7-ri20.2d_n2/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/nose_base-y0-yi45-p0-pi45-rn7-ri20.2d_n2/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/nose_base-y0-yi45-p0-pi45-rp7-ri20.2d_n2/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/nose_base-y0-yi45-p0-pi45-rp7-ri20.2d_n2/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/right_eye-y0-yi45-p0-pi45-r0-ri20.2d_n2/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/right_eye-y0-yi45-p0-pi45-r0-ri20.2d_n2/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/right_eye-y0-yi45-p0-pi45-rn7-ri20.2d_n2/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/right_eye-y0-yi45-p0-pi45-rn7-ri20.2d_n2/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/right_eye-y0-yi45-p0-pi45-rp7-ri20.2d_n2/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/right_eye-y0-yi45-p0-pi45-rp7-ri20.2d_n2/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.3/head-y0-yi45-p0-pi45-r0-ri30.4a/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.3/head-y0-yi45-p0-pi45-r0-ri30.4a/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.3/head-y0-yi45-p0-pi45-rn30-ri30.5/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.3/head-y0-yi45-p0-pi45-rn30-ri30.5/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.3/head-y0-yi45-p0-pi45-rp30-ri30.5/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.3/head-y0-yi45-p0-pi45-rp30-ri30.5/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/recognition/face.face.y0-y0-22-b-N/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/recognition/face.face.y0-y0-22-b-N/full_model.bin to 644 failed: No such file or directory
>>> Creating additional symlinks
>>> Setting permissions
>>> Flashing boot.img
>>> Unmounting partitions
about to run program [/sbin/busybox] with 4 args

Categories

Resources