[How to] get full ubuntu and your favorite desktop in webtop

jahuang · 2nd June 2012, 06:47 AM

After update to 2.3.6

Jim,

When I update my phone to 2.3.6 from OTA. then run the script again, and get something wrong as below:

tar: ./proc/1721/task/1721/fd/7: Cannot open: No such file or directory
./proc/1721/task/1721/fd/8
tar: ./proc/1721/task/1721/fd/8: Cannot open: No such file or directory
./proc/1721/task/1721/fd/9
tar: ./proc/1721/task/1721/fd/9: Cannot open: No such file or directory
./proc/1721/task/1721/fd/10
tar: ./proc/1721/task/1721/fd/10: Cannot open: No such file or directory
./proc/1721/task/1721/fd/11
tar: ./proc/1721/task/1721/fd/11: Cannot open: No such file or directory
./proc/1721/task/1721/fd/12
tar: ./proc/1721/task/1721/fd/12: Cannot open: No such file or directory
./proc/1721/task/1721/fd/13
tar: ./proc/1721/task/1721/fd/13: Cannot open: No such file or directory
./proc/1721/task/1721/fd/14
tar: ./proc/1721/task/1721/fd/14: Cannot open: No such file or directory
./proc/1721/task/1721/fd/15
tar: ./proc/1721/task/1721/fd/15: Cannot open: No such file or directory
./proc/1721/task/1721/fd/16
tar: ./proc/1721/task/1721/fd/16: Cannot open: No such file or directory
./proc/1721/task/1721/fd/17
tar: ./proc/1721/task/1721/fd/17: Cannot open: No such file or directory
./proc/1721/task/1721/fd/18
tar: ./proc/1721/task/1721/fd/18: Cannot open: No such file or directory
./proc/1721/task/1721/fd/19

Could you point out what's the problem? Thank you!

jimbridgman · 2nd June 2012, 06:09 PM

Quote:

Originally Posted by jahuang

Jim,

When I update my phone to 2.3.6 from OTA. then run the script again, and get something wrong as below:

tar: ./proc/1721/task/1721/fd/7: Cannot open: No such file or directory
./proc/1721/task/1721/fd/8
tar: ./proc/1721/task/1721/fd/8: Cannot open: No such file or directory
./proc/1721/task/1721/fd/9
tar: ./proc/1721/task/1721/fd/9: Cannot open: No such file or directory
./proc/1721/task/1721/fd/10
tar: ./proc/1721/task/1721/fd/10: Cannot open: No such file or directory
./proc/1721/task/1721/fd/11
tar: ./proc/1721/task/1721/fd/11: Cannot open: No such file or directory
./proc/1721/task/1721/fd/12
tar: ./proc/1721/task/1721/fd/12: Cannot open: No such file or directory
./proc/1721/task/1721/fd/13
tar: ./proc/1721/task/1721/fd/13: Cannot open: No such file or directory
./proc/1721/task/1721/fd/14
tar: ./proc/1721/task/1721/fd/14: Cannot open: No such file or directory
./proc/1721/task/1721/fd/15
tar: ./proc/1721/task/1721/fd/15: Cannot open: No such file or directory
./proc/1721/task/1721/fd/16
tar: ./proc/1721/task/1721/fd/16: Cannot open: No such file or directory
./proc/1721/task/1721/fd/17
tar: ./proc/1721/task/1721/fd/17: Cannot open: No such file or directory
./proc/1721/task/1721/fd/18
tar: ./proc/1721/task/1721/fd/18: Cannot open: No such file or directory
./proc/1721/task/1721/fd/19

Could you point out what's the problem? Thank you!

You should be OK, anything in /proc is volatile, and really just a small storage place for kernel and running apps to store running process information. I am guessing that you had something running in webtop recently and did not close everything out, and or reboot before doing this.... that is why you had stuff in /proc.

jahuang · 3rd June 2012, 02:15 AM

OK, got it, ths!

z652366 · 13th June 2012, 02:51 AM

help please~

jim,
i've try many times but the problems still there.
like this

tar: ./usr/lib/pymodules/python2.6/gtk-2.0/gtk: Cannot change mode to rwxr-xr-x:
Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0/pynotify: Cannot utime: Read-only fil
e system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0/pynotify: Cannot change ownership to
uid 0, gid 0: Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0/pynotify: Cannot change mode to rwxr-
xr-x: Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0/gobject: Cannot utime: Read-only file
system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0/gobject: Cannot change ownership to u
id 0, gid 0: Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0/gobject: Cannot change mode to rwxr-x
r-x: Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0: Cannot utime: Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0: Cannot change ownership to uid 0, gi
d 0: Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0: Cannot change mode to rwxr-xr-x: Rea
d-only file system
tar: ./usr/lib/pymodules/python2.6/dbus/mainloop: Cannot utime: Read-only file s
ystem
tar: ./usr/lib/pymodules/python2.6/dbus/mainloop: Cannot change ownership to uid
0, gid 0: Read-only file system
tar: ./usr/lib/pymodules/python2.6/dbus/mainloop: Cannot change mode to rwxr-xr-
x: Read-only file system
tar: ./usr/lib/pymodules/python2.6/dbus: Cannot utime: Read-only file system
tar: ./usr/lib/pymodules/python2.6/dbus: Cannot change ownership to uid 0, gid 0
: Read-only file system
tar: ./usr/lib/pymodules/python2.6/dbus: Cannot change mode to rwxr-xr-x: Read-o
nly file system
tar: ./usr/lib/pymodules/python2.6/OpenSSL/test: Cannot utime: Read-only file sy
stem
tar: ./usr/lib/pymodules/python2.6/OpenSSL/test: Cannot change ownership to uid
0, gid 0: Read-only file system
tar: ./usr/lib/pymodules/python2.6/OpenSSL/test: Cannot change mode to rwxr-xr-x
: Read-only file system
tar: ./usr/lib/pymodules/python2.6/OpenSSL: Cannot utime: Read-only file system
tar: ./usr/lib/pymodules/python2.6/OpenSSL: Cannot change ownership to uid 0, gi
d 0: Read-only file system
tar: ./usr/lib/pymodules/python2.6/OpenSSL: Cannot change mode to rwxr-xr-x: Rea
d-only file system
tar: ./usr/lib/pymodules/python2.6: Cannot utime: Read-only file system
tar: ./usr/lib/pymodules/python2.6: Cannot change ownership to uid 0, gid 0: Rea
d-only file system
tar: ./usr/lib/pymodules/python2.6: Cannot change mode to rwxr-xr-x: Read-only f
ile system
tar: ./usr/lib/pymodules: Cannot utime: Read-only file system
tar: ./usr/lib/pymodules: Cannot change ownership to uid 0, gid 0: Read-only fil
e system
tar: ./usr/lib/pymodules: Cannot change mode to rwxr-xr-x: Read-only file system

tar: ./usr/lib/xorg: Cannot utime: Read-only file system
tar: ./usr/lib/xorg: Cannot change ownership to uid 0, gid 0: Read-only file sys
tem
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 !!thanks!

souljaboy · 13th June 2012, 07:12 PM

Can someone who has it running, just make a (ghost) image of the sd card partition of a clean install ? Please so nobody has to go through this battle.

jimbridgman · 13th June 2012, 07:47 PM

Quote:

Originally Posted by souljaboy

Can someone who has it running, just make a (ghost) image of the sd card partition of a clean install ? Please so nobody has to go through this battle.

That won't work, or I would have done that. This is the only way. If you want to you can thank Motorola for making this so hard.

jimbridgman · 13th June 2012, 07:50 PM

Quote:

Originally Posted by z652366

jim,
i've try many times but the problems still there.
like this

tar: ./usr/lib/pymodules/python2.6/gtk-2.0/gtk: Cannot change mode to rwxr-xr-x:
Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0/pynotify: Cannot utime: Read-only fil
e system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0/pynotify: Cannot change ownership to
uid 0, gid 0: Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0/pynotify: Cannot change mode to rwxr-
xr-x: Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0/gobject: Cannot utime: Read-only file
system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0/gobject: Cannot change ownership to u
id 0, gid 0: Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0/gobject: Cannot change mode to rwxr-x
r-x: Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0: Cannot utime: Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0: Cannot change ownership to uid 0, gi
d 0: Read-only file system
tar: ./usr/lib/pymodules/python2.6/gtk-2.0: Cannot change mode to rwxr-xr-x: Rea
d-only file system
tar: ./usr/lib/pymodules/python2.6/dbus/mainloop: Cannot utime: Read-only file s
ystem
tar: ./usr/lib/pymodules/python2.6/dbus/mainloop: Cannot change ownership to uid
0, gid 0: Read-only file system
tar: ./usr/lib/pymodules/python2.6/dbus/mainloop: Cannot change mode to rwxr-xr-
x: Read-only file system
tar: ./usr/lib/pymodules/python2.6/dbus: Cannot utime: Read-only file system
tar: ./usr/lib/pymodules/python2.6/dbus: Cannot change ownership to uid 0, gid 0
: Read-only file system
tar: ./usr/lib/pymodules/python2.6/dbus: Cannot change mode to rwxr-xr-x: Read-o
nly file system
tar: ./usr/lib/pymodules/python2.6/OpenSSL/test: Cannot utime: Read-only file sy
stem
tar: ./usr/lib/pymodules/python2.6/OpenSSL/test: Cannot change ownership to uid
0, gid 0: Read-only file system
tar: ./usr/lib/pymodules/python2.6/OpenSSL/test: Cannot change mode to rwxr-xr-x
: Read-only file system
tar: ./usr/lib/pymodules/python2.6/OpenSSL: Cannot utime: Read-only file system
tar: ./usr/lib/pymodules/python2.6/OpenSSL: Cannot change ownership to uid 0, gi
d 0: Read-only file system
tar: ./usr/lib/pymodules/python2.6/OpenSSL: Cannot change mode to rwxr-xr-x: Rea
d-only file system
tar: ./usr/lib/pymodules/python2.6: Cannot utime: Read-only file system
tar: ./usr/lib/pymodules/python2.6: Cannot change ownership to uid 0, gid 0: Rea
d-only file system
tar: ./usr/lib/pymodules/python2.6: Cannot change mode to rwxr-xr-x: Read-only f
ile system
tar: ./usr/lib/pymodules: Cannot utime: Read-only file system
tar: ./usr/lib/pymodules: Cannot change ownership to uid 0, gid 0: Read-only fil
e system
tar: ./usr/lib/pymodules: Cannot change mode to rwxr-xr-x: Read-only file system

tar: ./usr/lib/xorg: Cannot utime: Read-only file system
tar: ./usr/lib/xorg: Cannot change ownership to uid 0, gid 0: Read-only file sys
tem
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 !!thanks!

I don't think your root is working. Are you sure that you are rooted correctly?

run the following and post the output as a reply back to me here in this thread.

Code:

adb shell
su
id
which busybox
busybox df -h
which su
exit
exit

z652366 · 14th June 2012, 03:41 AM

i got this

C:\adb>adb shell
su
id
which busybox
busybox df -h
which su
exit
exitshell@edison:/$ su
root@edison:/# id
uid=0(root) gid=0(root)
root@edison:/# which busybox
/system/xbin/busybox
root@edison:/# busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 464.7M 336.0K 464.4M 0% /dev
tmpfs 464.7M 0 464.7M 0% /mnt/asec
tmpfs 464.7M 0 464.7M 0% /mnt/obb
/dev/block/system 477.5M 361.5M 116.0M 76% /system
/dev/block/userdata 4.5G 264.1M 4.1G 6% /data
/dev/block/cache 689.0M 16.7M 637.2M 3% /cache
/dev/block/webtop 1.3G 784.8M 526.8M 60% /osh
/dev/block/pds 3.9M 1.1M 2.8M 28% /pds
/dev/block/preinstall
274.7M 25.6M 249.2M 9% /preinstall
/dev/block/vold/179:1
11.2G 37.6M 11.2G 0% /mnt/sdcard
/dev/block/vold/179:1
11.2G 37.6M 11.2G 0% /mnt/secure/asec
root@edison:/# which su
/system/bin/su
root@edison:/# exit
shell@edison:/$

what's the matter..

z652366 · 14th June 2012, 07:07 AM

that's ok.but it turn up to this now.......

tar: Error exit delayed from previous errors
unmounting your sdcard from the temp mount, now that we are done copying all the
files.

umount: /tmp/osh: not found
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.

fdisk: not found
fdisk: not found
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]: 3669 could not load needed library 'liblog.so' for '/system/b
in/reboot' (link_image[1964]: 3669 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

THanks~

jimbridgman · 03:19 PM

Quote:

Originally Posted by z652366

that's ok.but it turn up to this now.......

tar: Error exit delayed from previous errors
unmounting your sdcard from the temp mount, now that we are done copying all the
files.

umount: /tmp/osh: not found
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.

fdisk: not found
fdisk: not found
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]: 3669 could not load needed library 'liblog.so' for '/system/b
in/reboot' (link_image[1964]: 3669 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

THanks~

Now right off, I see an issue in the other commands you sent me.

Your busybox is installed in the wrong location.

Go to the market and download Jrummy16s busybox installer.
https://play.google.com/store/apps/d...nstaller&hl=en

Then launch it, and in the second dropdown it has a location of where to install busybox. Make sure you select /system/bin, and NOT /system/xbin.
ONLY install version 1.19.4, in the top dropdwon.
Now select install. It may give you an error and tell you that it is already installed in /system/xbin, and if you want to move it, say yes.

This should fix most of your issues. After you do this reboot your phone, and try it again, then if you have more issues, reply back here. I will then see where to go next.

This might be be several tries back and forth with me to get this all fixed up, because it looks like a few other issue may come up too, from what I see in your output. Let's do one thing at a time though, so we know what was done and what fixed or did not fix something.