Related
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
I am working on a startup script to allow browser2RAM to work with other browsers that don't use the android.browser.com agent (Chrome, Firefox) and don't know where to put this 00script file I wrote in the system. This device has no etc/init.d directory. Where should this go to get executed on boot?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Re: User startup script location in system partition?
elfaure said:
I am working on a startup script to allow browser2RAM to work with other browsers that don't use the android.browser.com agent (Chrome, Firefox) and don't know where to put this 00script file I wrote in the system. This device has no etc/init.d directory. Where should this go to get executed on boot?
Click to expand...
Click to collapse
If you have a custom ROM like CleanROM Inheritance, you should have a (/system)/etc/init.d - which ROM are you running?
Re: User startup script location in system partition?
_that said:
If you have a custom ROM like CleanROM Inheritance, you should have a (/system)/etc/init.d - which ROM are you running?
Click to expand...
Click to collapse
Hi-
Thanks for your reply. I am locked and rooted on stock ROM.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
elfaure said:
I am locked and rooted on stock ROM.
Click to expand...
Click to collapse
OK, that means no support for init.d by the kernel's init.rc. You can try the following:
Create a shell script named "/system/etc/install-recovery.sh" with the following content:
Code:
#!/system/bin/sh
/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
Remember to make it executable and to create the /system/etc/init.d directory. Put your init script there and make it executable.
If you have busybox installed in /system/xbin and a little luck, this could enable support for running init.d scripts with the stock ROM. Tell us if it worked.
_that said:
OK, that means no support for init.d by the kernel's init.rc. You can try the following:
Create a shell script named "/system/etc/install-recovery.sh" with the following content:
Code:
#!/system/bin/sh
/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
Remember to make it executable and to create the /system/etc/init.d directory. Put your init script there and make it executable.
If you have busybox installed in /system/xbin and a little luck, this could enable support for running init.d scripts with the stock ROM. Tell us if it worked.
Click to expand...
Click to collapse
I thank you for the method but I'm a newb (nOOb) and this looks a little scary. I found two market apps that can do it (execute a script as root on boot): Autostart-Root and ROM Toolbox (Lite or Pro). I'm using the latter's Scripter tool to execute this script on boot as root. Seems to be working. (Appended the .txt extension to the filename in order to upload the file)
Here's another thead i found here on the subject
http://forum.xda-developers.com/showthread.php?t=690564
_That
Using your method above, how would you run the script as root (su)? This script needs to run as root to properly mount the /data partition.
elfaure said:
Using your method above, how would you run the script as root (su)? This script needs to run as root to properly mount the /data partition.
Click to expand...
Click to collapse
It should run as root because it's started by init - /data is already mounted at that time. If I understand your intention correctly, you don't need to (re)mount /data anyway, just /data/data/<whatever_directory_your_browser_uses>.
_that said:
It should run as root because it's started by init - /data is already mounted at that time. If I understand your intention correctly, you don't need to (re)mount /data anyway, just /data/data/<whatever_directory_your_browser_uses>.
Click to expand...
Click to collapse
If I run my script as normal user (not as root ie su) then I get script /data mount errors.
exec /system/bin/sh '/Removable/MicroSD/Scripts/autostart.sh'
[email protected]:/ $ exec /system/bin/sh '/Removable/MicroSD/Scripts/autostart.sh'
failed: Invalid argument
rm failed for -rf, No such file or directory
mount: Operation not permitted
failed: Invalid argument
rm failed for -rf, No such file or directory
mount: Operation not permitted
failed: Invalid argument
rm failed for -rf, No such file or directory
mount: Operation not permitted
failed: Invalid argument
rm failed for -rf, No such file or directory
mount: Operation not permitted
But when I run it as root user
exec /system/bin/sh '/Removable/MicroSD/Scripts/autostart.sh'
failed: Invalid argument
rm failed for -rf, No such file or directory
failed: Invalid argument
rm failed for -rf, No such file or directory
failed: Invalid argument
rm failed for -rf, No such file or directory
failed: Invalid argument
rm failed for -rf, No such file or directory
The rm failed for -rt really isn't an error, just an indication there was no cache file to delete, correct?
elfaure said:
If I run my script as normal user (not as root ie su) then I get script /data mount errors.
Click to expand...
Click to collapse
I don't see where "/data" is mentioned in your error messages. You get "invalid argument" from umount because there is nothing mounted on that directory, and "operation not permitted" from mount because only root is allowed to mount filesystems.
elfaure said:
The rm failed for -rt really isn't an error, just an indication there was no cache file to delete, correct?
Click to expand...
Click to collapse
Correct.
_that said:
I don't see where "/data" is mentioned in your error messages. You get "invalid argument" from umount because there is nothing mounted on that directory, and "operation not permitted" from mount because only root is allowed to mount filesystems.
Correct.
Click to expand...
Click to collapse
Thanks very much for that explaination. Sorry, I'm just getting started with scripts. In fact, this is my first one. Another question:
I added: (got the idea from this post, pg 2 http://forum.xda-developers.com/showthread.php?t=690564)
>/data/opt/autostart.out 2>/data/opt/autostart.errto the end of the script.
The original call is shown here:
"I simulate it by the following contents in /system/etc/init.d/20autostart :
/system/bin/sh /data/opt/autostart.sh >/data/opt/autostart.out 2>/data/opt/autostart.err
which not only calls /data/opt/autostart.sh at boot time, but
also dumps its stdout to /data/opt/autostart.out
and dumps its stderr to /data/opt/autostart.err
which is very helpful for debugging the commands in /data/opt/autostart.sh
Note that you need to enter recovery mode before you can write to /system/etc/init.d/" Now when it runs it dumps the two files, which are sucessfully created. But both files are blank, no data, and autostart.err does not have any error messages like I show above. What's wrong with this call statement? Can't it be executed from within this same script, or do I have to use another script to call this one to make that work?
_that said:
OK, that means no support for init.d by the kernel's init.rc. You can try the following:
Create a shell script named "/system/etc/install-recovery.sh" with the following content:
Code:
#!/system/bin/sh
/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
Remember to make it executable and to create the /system/etc/init.d directory. Put your init script there and make it executable.
If you have busybox installed in /system/xbin and a little luck, this could enable support for running init.d scripts with the stock ROM. Tell us if it worked.
Click to expand...
Click to collapse
From that another post, he calls:
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
which looks quite similar. Can you describe the differences between them? Is this one only for CWM?
Is this even possible on stock ROM?
_that said:
OK, that means no support for init.d by the kernel's init.rc. You can try the following:
Create a shell script named "/system/etc/install-recovery.sh" with the following content:
Code:
#!/system/bin/sh
/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
Remember to make it executable and to create the /system/etc/init.d directory. Put your init script there and make it executable.
If you have busybox installed in /system/xbin and a little luck, this could enable support for running init.d scripts with the stock ROM. Tell us if it worked.
Click to expand...
Click to collapse
I got a bit educated then got brave and tried it and it doesn't seem to work. I added the file tracer output line, files> /data/opt, to my startup script, made yours executable via "chmod 776 install-recovery.sh", put it where you said, put mine where you said, made mine executable same way except had to mount system R/W to do it (should have done this before I put it there but I am learning), ran your script without error, then rebooted. I see no files in data/oct so my script did not run at boot? I even renamed my script 00autostart1.sh and still didn't work.
Also, both other methods failed to run my script at boot. Any other ideas on stock ROM or is this just not possible?
elfaure said:
>/data/opt/autostart.out 2>/data/opt/autostart.errto the end of the script.
Click to expand...
Click to collapse
You need to add these redirections to each command whose output you want to redirect, not to the end of the script. So to capture the output of your script, write another script that calls your original one with these redirections, as suggested by that other person.
elfaure said:
From that another post, he calls:
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
which looks quite similar. Can you describe the differences between them? Is this one only for CWM?
Click to expand...
Click to collapse
The above is the block that needs to be added to /init.rc, but this is part of the kernel's ramdisk which you can only modify on an unlocked device.
elfaure said:
I got a bit educated then got brave and tried it and it doesn't seem to work.
Click to expand...
Click to collapse
Post the output of:
su
ls -l /etc/install-recovery.sh
cat /etc/install-recovery.sh
ls -ld /etc/init.d
ls -l /etc/init.d
ls -l /system/xbin/busybox
_that said:
You need to add these redirections to each command whose output you want to redirect, not to the end of the script. So to capture the output of your script, write another script that calls your original one with these redirections, as suggested by that other person.
The above is the block that needs to be added to /init.rc, but this is part of the kernel's ramdisk which you can only modify on an unlocked device.
Post the output of:
su
ls -l /etc/install-recovery.sh
cat /etc/install-recovery.sh
ls -ld /etc/init.d
ls -l /etc/init.d
ls -l /system/xbin/busybox
Click to expand...
Click to collapse
I created a script called that_script.sh that contains your command set above. I make it executable and run it (as root) and:
****************************************
There is no output because the script never completes execution? Just runs forever (Script Manager) or times out (ROM Toolbox Lite Scripter). Some kind of script-loop is created?? Upon break (exit) I get the following output:
exec sh -c '/Removable/MicroSD/Scripts/that_script.sh '
exit
-rw-rw-r-- root sdcard_rw 90 2013-03-19 18:28 install-recovery.sh
#!/system/bin/sh
/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.ddrwx------ root root 2013-03-19 18:45 init.d
-rwxrwxrw- root root 938 2013-03-19 18:35 00autostart1.sh
-rwsr-xr-x root root 497964 2013-03-03 17:59 busybox
elfaure said:
I created a script called that_script.sh that contains your command set above. I make it executable and run it (as root) and:
****************************************
There is no output because the script never completes execution? Just runs forever (Script Manager) or times out (ROM Toolbox Lite Scripter). Some kind of script-loop is created??
Click to expand...
Click to collapse
I don't know what strange tools you are using, the commands were meant to simply type into an interactive shell (adb or a local terminal app).
However, the original problem why your script doesn't run at boot is obvious from your output:
Code:
-rw-rw-r-- root sdcard_rw 90 2013-03-19 18:28 install-recovery.sh
You forgot to make install-recovery.sh executable (or you forgot to become root first).
I use these script tools so I can copy all the text into a file and run the file (script) rather than typing each line individually into the terminal. My tools show the script is executable (I ran "chmod 776 filename.ext" = "chmod +x filename.ext" on the script file) and ran it as root? I'll try it again and post back. I'll also try it from the terminal app.
Thks
_that said:
It should run as root because it's started by init - /data is already mounted at that time. If I understand your intention correctly, you don't need to (re)mount /data anyway, just /data/data/<whatever_directory_your_browser_uses>.
Click to expand...
Click to collapse
I'm not (re)mounting /data.
So the mount is still needed, that's the key to the whole process. *The mount isn't (re)mounting the data partition, it's creating a mount point inside the data partition for the RAM cache.
What the script is doing is creating a tmpfs filesystem where the browsers expect to put their cache files. This filesystem is actually fully in memory (RAM), and never backed by any permanent storage. The -t tmpfs option tells mount to create a tmpfs filesystem, and -o size=50m tells it to reserve 50 MB of memory. The unmount is for when I use a different browser (one that doesn't use the com.android.browser agent like chrome, firefox, naked, etc.) and need to create a new mount point but want to reuse the 50MB already allocated for the existing mount point. Hope this clarifies my intent with creating this script and how it is supposed to work.
elfaure said:
I'm not (re)mounting /data.
So the mount is still needed, that's the key to the whole process. *The mount isn't (re)mounting the data partition, it's creating a mount point inside the data partition for the RAM cache.
What the script is doing is creating a tmpfs filesystem where the browsers expect to put their cache files. This filesystem is actually fully in memory (RAM), and never backed by any permanent storage. The -t tmpfs option tells mount to create a tmpfs filesystem, and -o size=50m tells it to reserve 50 MB of memory. The unmount is for when I use a different browser (one that doesn't use the com.android.browser agent like chrome, firefox, naked, etc.) and need to create a new mount point but want to reuse the 50MB already allocated for the existing mount point. Hope this clarifies my intent with creating this script and how it is supposed to work.
Click to expand...
Click to collapse
Assumed that you script is working, you could use "script manager - SManager" from the market. This app will allow yours to run as root and during start up. All you need is root. The script can be at any location (even on sdcard if you like). I used to use this with my cell phone.
elfaure said:
I'm not (re)mounting /data.
Click to expand...
Click to collapse
Well, you originally wrote:
This script needs to run as root to properly mount the /data partition.
Click to expand...
Click to collapse
Does it work now as it should?
Be sure to read also this thread about mounting in Android 4.2:
http://forum.xda-developers.com/showthread.php?t=2227123
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?
Quick guide for people having trouble rooting/unlocking bootloader and custom recovery LG-D320/N/L70 devices running 4.4.2 with a new 3.4.0+ kernel
This way is easier then any root method and NO PC is required
Simple, straight forward, takes not even 5 minutes.
First download and install these 3 apps.
CPU Benchamark
Terminal Emulator
KingoRoot.apk
Second, download this zip file and extract the "mrw" folder to your phones internal memory(/sdcard)
ReplaceKingoRoot.zip
Third, open CPU Benchtest app and press the "stress test" box, then minimize the app and open Kingo ROOT app and press the "ROOT" bubble
Fourth, Kingo ROOT says your device is rooted open Terminal Emulator and type the following
Code:
su
Your device will ask if Terminal Emulator can be granted root permissions, allow it then proceed to type the following
Code:
sh /sdcard/mrw/root.sh
Then SuperSU will automatically open and ask to update SuperSU binaries, select the "update" box and when it asks you how you want to update it select the "normal" box
Five, Restart your phone when SuperSU says you need to restart for the update to take effect
Now, unlocking the bootloader and flashing a custom recovery, fortunately i made a tool for this with the required files.
simply download this, unzip it onto the desktop and run LGTOOL.BAT by double clicking it and follow the instructions.
LG TOOL BY RICKY DIVJAKOVSKI
ENJOY GUYS
Credits:
jeffta74
wanako1
MrW0lf
updated.
I'm AndroidAddict aka MikeHoncho at AF btw. Glad to see someone post something even though we never got a forum here
AndroidAddict||AA said:
I'm AndroidAddict aka MikeHoncho at AF btw. Glad to see someone post something even though we never got a forum here
Click to expand...
Click to collapse
every device should be able to gain full flexibillity, no matter how old, how new, how popular or unpopular and device i get my hands on will gain full access
time to make a custom rom now
I think everything is done "custom ROM" wise. AOSP, cm11, cm12, carbon (by me) and other ROMs
AndroidAddict||AA said:
I think everything is done "custom ROM" wise. AOSP, cm11, cm12, carbon (by me) and other ROMs
Click to expand...
Click to collapse
ofcoarse its done custom rom wise, you can modify a rom with root access but to safely modify a rom and test recovery is mandatory
Terminal emulator not working
Thx for this guide.
terminal emulator can't install SuperSU.
Here's the log, whats wrong?
Tried also to install supersu manually, but can't update it so is absolutely useless.
[email protected]:/ $ su
l_SD/ReplaceKingoRoot/mrw/root.sh <
---------------------------------------
---------- Made By : Mr.W0lf ----------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
---------------------------------------
----- UPDATED BY RICKY DIVJAKOVSKI ----
---------------------------------------
Failure
Failure
rm failed for /system/app/KingoUser, No such file or directory
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[20]: cat: sdcard/mrw/busybox: No such file or directory
rm failed for /system/xbin/ku.sud, No such file or directory
rm failed for /system/xbin/su, Operation not permitted
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[33]: can't create /system/xbin/su: Permission denied
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[35]: cat: /sdcard/mrw/su: No such file or directory
Unable to chown /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
daemonsu: invalid option -- d
Usage: su [options] [--] [-] [LOGIN] [--] [args...]
Options:
--daemon start the su daemon agent
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-u display the multiuser mode and exit
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk
rm failed for /data/data-lib/com.kingoapp.root, No such file or directory
rm failed for /data/data-lib/com.kingouser.com, No such file or directory
rm failed for /data/data/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data-lib/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data/com.kingroot.kinguser, No such file or directory
rm failed for /data/data-lib/com.kingroot.kinguser, No such file or directory
rm failed for /data/data/com.kingroot.master, No such file or directory
rm failed for /system/bin/.usr/.ku, No such file or directory
rm failed for /system/bin/rt.sh, No such file or directory
rm failed for /system/bin/su, Operation not permittedrm failed for /system/bin/ddexe, No such file or directory
rm failed for /system/bin/install-recovery.sh, No such file or directory
rm failed for /system/bin/install-recovery.sh-ku.bak, No such file or directory
pkg: /sdcard/mrw/superuser.apk
Failure [INSTALL_FAILED_INVALID_URI]
rm failed for /system/usr/iku, No such file or directory
rm failed for /dev/reportroot, No such file or directory
rm failed for /system/app/Kinguser, No such file or directory
rm failed for /data/data-lib/king, No such file or directory
rm failed for /sdcard/Kingroot, No such file or directory
Error type 3
Error: Activity class {eu.chainfire.supersu/eu.chainfire.supersu.MainActivity} does not exist.
[email protected]:/ #ll
Ggcost said:
Thx for this guide.
terminal emulator can't install SuperSU.
Here's the log, whats wrong?
Tried also to install supersu manually, but can't update it so is absolutely useless.
[email protected]:/ $ su
l_SD/ReplaceKingoRoot/mrw/root.sh <
---------------------------------------
---------- Made By : Mr.W0lf ----------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
---------------------------------------
----- UPDATED BY RICKY DIVJAKOVSKI ----
---------------------------------------
Failure
Failure
rm failed for /system/app/KingoUser, No such file or directory
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[20]: cat: sdcard/mrw/busybox: No such file or directory
rm failed for /system/xbin/ku.sud, No such file or directory
rm failed for /system/xbin/su, Operation not permitted
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[33]: can't create /system/xbin/su: Permission denied
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[35]: cat: /sdcard/mrw/su: No such file or directory
Unable to chown /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
daemonsu: invalid option -- d
Usage: su [options] [--] [-] [LOGIN] [--] [args...]
Options:
--daemon start the su daemon agent
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-u display the multiuser mode and exit
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk
rm failed for /data/data-lib/com.kingoapp.root, No such file or directory
rm failed for /data/data-lib/com.kingouser.com, No such file or directory
rm failed for /data/data/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data-lib/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data/com.kingroot.kinguser, No such file or directory
rm failed for /data/data-lib/com.kingroot.kinguser, No such file or directory
rm failed for /data/data/com.kingroot.master, No such file or directory
rm failed for /system/bin/.usr/.ku, No such file or directory
rm failed for /system/bin/rt.sh, No such file or directory
rm failed for /system/bin/su, Operation not permittedrm failed for /system/bin/ddexe, No such file or directory
rm failed for /system/bin/install-recovery.sh, No such file or directory
rm failed for /system/bin/install-recovery.sh-ku.bak, No such file or directory
pkg: /sdcard/mrw/superuser.apk
Failure [INSTALL_FAILED_INVALID_URI]
rm failed for /system/usr/iku, No such file or directory
rm failed for /dev/reportroot, No such file or directory
rm failed for /system/app/Kinguser, No such file or directory
rm failed for /data/data-lib/king, No such file or directory
rm failed for /sdcard/Kingroot, No such file or directory
Error type 3
Error: Activity class {eu.chainfire.supersu/eu.chainfire.supersu.MainActivity} does not exist.
[email protected]:/ #ll
Click to expand...
Click to collapse
Yea i have the same problem with this i've done everything right step by step but seems cant find the location of the root can anyone help me or the topic is dead ?
It's safe to run this if you've already cleared parts out. It's ideal for right after you've rooted.
You will be left with a very clean Palm phone. If you use Fdroid, love open-source, and loath Google then this is for you!
Everything works well. There is one issue with the dialer where you scroll to the top with the scrollbar and it crashes. Instead of using the scrollbar just swipe on the names to scroll.
# Objectives:
1. remove all bloatware, including Google
2. Fix incorrect APN settings
3. Remove traces of Verizon
4. Battery life enhancement
5. Suppress adb debugging warning
# TODO
1. Make the script ask whether Google apps are to be removed, and differentiate.
# Pre-requisites:
1. device is rooted!
# Usage
Run ./exec.sh in a terminal and follow the instructions.
Thanks for releasing this. Do you have any data on performance or battery life increases after making all of these changes? Also, since this script seems to remove Google services, would I be able to do a factory reset of the device to restore Google services?
All Google crap is removed. You can modify the script to exclude those removals if you want (please share your changes and I'll include for others).
All changes are to /system and /vendor, so considered permanent.
If you do a factory reset chances are it won't boot and you'll need to re-root again. Best avoid.
Battery life difference is significant, as is to be expected by removing so much junk, specifically services.
One issue, it somehow removed the clock app. I'll have to remove that from the list when I find out which one it is. For now you can install it again via "Clock" on apkpure.com
snoopy20 said:
One issue, it somehow removed the clock app. I'll have to remove that from the list when I find out which one it is. For now you can install it again via "Clock" on apkpure.com
Click to expand...
Click to collapse
It's on line 30 of the palm.sh
DeskClock
g60madman said:
It's on line 30 of the palm.sh
DeskClock
Click to expand...
Click to collapse
Ah I thought that was a home widget. Now fixed.
Please let me know if there's any other bloatware crap which I've missed.
I've found /vendor/bin/mmid is writing to logcat and responsible for a lot of wakeups. Prevented it from respawning with chmod 000. No negative effect so far so will add it to the next script revision.
Also by killing that I now get new battery information in logcat and a lot less logcat messages. I believe that process was responsible for killing something related to power details as I kept getting process startup details. I now get a lot less messages and also proper battery stats in logcat -
02-18 14:01:38.354 1223 2332 D BatteryService: Processing new values: chargerAcOnline=false, chargerUsbOnline=true, chargerWirelessOnline=false, maxChargingCurrent500000, maxChargingVoltage5000000, batteryStatus=2, batteryHealth=2, batteryPresent=true, batteryLevel=97, batteryTechnology=Li-ion, batteryVoltage=4397, batteryChargeCounter=715903, batteryFullCharge=796000, batteryTemperature=240, mBatteryLevelCritical=false, mPlugType=2
Really appreciate your work on this. I edited the palm.sh file to the following to try to keep all the extra Google stuff intact:
#!/usr/bin/env sh
mount -o rw,remount /system
mount -o rw,remount /vendor
## OBJECTIVE: 1 ##
echo "Removing user installs..."
pm uninstall -k --user 0 'com.verizon.cloudsetupwizard'
pm uninstall -k --user 0 'com.verizon.mips.services'
pm uninstall -k --user 0 'com.vzw.hss.myverizon'
pm uninstall -k --user 0 'com.jrd.verizonuriintentservice'
pm uninstall -k --user 0 'com.verizon.messaging.vzmsgs'
pm uninstall -k --user 0 'com.verizon.llkagent'
pm uninstall -k --user 0 'com.vzw.apnlib'
pm uninstall -k --user 0 'com.tcl.vzwintents'
pm uninstall -k --user 0 'com.tct.vzwwifioffload'
pm uninstall -k --user 0 'com.vzw.ecid'
pm uninstall -k --user 0 'com.vzw.easvalidation'
pm uninstall -k --user 0 'com.customermobile.preload.vzw'
pm uninstall -k --user 0 'com.vcast.mediamanager'
echo "Removing system bloatware..."
cd /system/app
## WARN: no remove (will brick): GoogleExtShared SecureExtAuthService
rm -rf VerizonUrintentService verizon-wifi-offload vzwintents
cd /system/priv-app
rm -rf VerizonNameID com.customermobile.preload.vzw VZWAPNLib verizon-llk-agent
cd /vendor/app
rm -rf VzwDMClient
cd /vendor/priv-app
rm -rf MVM_vzw_app-release-phone-13.1.1-278.apk VZMessages-mobile-6.7.12-94-market-release-signed.apk Verizon_LocationAgent_vzw_v0.0.3.120_Production_NoDebug_release_signed.apk
In case anyone else wanted to try out a different version.
snoopy20 said:
I've found /vendor/bin/mmid is writing to logcat and responsible for a lot of wakeups. Prevented it from respawning with chmod 000. No negative effect so far so will add it to the next script revision.
Click to expand...
Click to collapse
Don't use "chmod 000" on mmid. If you do, you can see in the kernel log (via "dmesg") that the phone is constantly trying to restart the mmid service:
Code:
init: starting service 'mmid'..
init: cannot execve('/vendor/bin/mmid'): Permission denied
...
init: starting service 'mmid'..
init: cannot execve('/vendor/bin/mmid'): Permission denied
...
init: starting service 'mmid'..
init: cannot execve('/vendor/bin/mmid'): Permission denied
But if you remove or rename mmid (mv /vendor/bin/mmid /vendor/bin/mmid.bak), init gives up and doesn't try to restart the mmid service:
Code:
[10081.043211] init: cannot find '/vendor/bin/mmid', disabling 'mmid': No such file or directory
---------- Post added at 08:41 PM ---------- Previous post was at 08:09 PM ----------
snoopy20 said:
#TODO (please assist if you can!)
1. Verizon boot animation.
Click to expand...
Click to collapse
To get rid of the Verizon boot animation, you can just rename/remove the bootanimation.zip file.
Code:
mount -o rw,remount /vendor
mv /vendor/JRD_custres/media/bootanimation.zip /vendor/JRD_custres/media/bootanimation.zip.bak
This will give you a default pulsing "android" boot animation instead of the Verizon boot animation.
Alternatively, you can use the below "PALM" boot animation that I put together. I don't know what boot animation the non-Verizon phone uses, but it's probably similar to this.
drive [dot] google.com/file/d/114Q9BUSrkjjIt9fPT4B-s3VH0ExGClDi/view
Code:
adb push bootanimation.zip /data/local/tmp/
adb shell
su
mount -o rw,remount /vendor
mv /data/local/tmp/bootanimation.zip /vendor/JRD_custres/media/bootanimation.zip
hi
does anyone know how to remove/change the boot image of "Your device has loaded a different operating system"?
thanks in advance
hi
will deleting all the bloatware from verizon make it unable to work on the CDMA network?
Doubt it, should be fine.
Funny that mmid didn't show in journalctl but does show with dmesg. I'll make the change. I'll remove the boot animation as well. - CHANGES MADE
If you want to modify the script to ask the user whether they want to keep Google crap, I can add that.
I'm just now trying to run this script, but I'm not all that familiar with running terminal scripts and I'm having an issue that I couldn't find the answer to. I'm rooted on the 1AMG software.
I keep getting "Read-only file system" errors, which searching tells me I have some permissions issues. The script says to grant access for Superuser, which I've done. Below is a screenshot of my terminal with the errors. I've received the same errors on Windows 10 and in Linux terminal on Chromebook.
https://imgur.com/a/XTkrHN8
Any help would be appreciated. Thanks!
tmrodden said:
I'm just now trying to run this script, but I'm not all that familiar with running terminal scripts and I'm having an issue that I couldn't find the answer to. I'm rooted on the 1AMG software.
I keep getting "Read-only file system" errors, which searching tells me I have some permissions issues. The script says to grant access for Superuser, which I've done. Below is a screenshot of my terminal with the errors. I've received the same errors on Windows 10 and in Linux terminal on Chromebook.
https://imgur.com/a/XTkrHN8
Any help would be appreciated. Thanks!
Click to expand...
Click to collapse
When the SU request came up did you grant or deny?
What happens when you run mount -o rw,remount /system?
snoopy20 said:
When the SU request came up did you grant or deny?
What happens when you run mount -o rw,remount /system?
Click to expand...
Click to collapse
I have got the same "not permitted" problem
When I'm trying to mount the /system it says:
Code:
PS C:\adb\palm> adb shell
Pepito:/ $ mount -o rw,remount /system
mount: '/dev/block/platform/soc/7824900.sdhci/by-name/system' not user mountable in fstab
I've tried to execute ANY "palm.sh" commands manually:
Code:
Pepito:/ $ cd /sdcard && su - -c \"sh palm.sh\"
: sh palm.sh: not found
On any other command I'm getting "Read only" reply
snoopy20 said:
When the SU request came up did you grant or deny?
What happens when you run mount -o rw,remount /system?
Click to expand...
Click to collapse
I granted the SU request, and it shows as enabled within Magisk, just as it does in the screenshot in al07th's post above.
The mount -o rw,remount /system command you suggested gives the following responses when I tried:
https://imgur.com/i0UWfWx
This is all after having completely wiped the phone, restored to the latest stock firmware using Sugar (1AMGGFG0), and going through the whole process again with a fresh root.
Also wanted to mention that any commands involving the "/sdcard" folder usually result in an error. Only adding a second backslash ("/sdcard/") allows them to be accepted.
tmrodden said:
I granted the SU request, and it shows as enabled within Magisk, just as it does in the screenshot in al07th's post above.
The mount -o rw,remount /system command you suggested gives the following responses when I tried:
https://imgur.com/i0UWfWx
This is all after having completely wiped the phone, restored to the latest stock firmware using Sugar (1AMGGFG0), and going through the whole process again with a fresh root.
Also wanted to mention that any commands involving the "/sdcard" folder usually result in an error. Only adding a second backslash ("/sdcard/") allows them to be accepted.
Click to expand...
Click to collapse
>> So this fails - adb push push/palm.sh /sdcard
>> But this works? adb push push/palm.sh /sdcard/
Strange!
mount -o rw,remount /system -> you are not running as su, hence the error you have.
In the console enter su bash then run mount -o rw,remount /system and it should work without error.
This is what the cd /sdcard && su - -c "sh palm.sh" command is doing. Assuming everything is pushed already and you've in a su bash shell then you can cd to the /sdcard directory and run the palm.sh directly.
al07th said:
I have got the same "not permitted" problem
When I'm trying to mount the /system it says:
Code:
PS C:\adb\palm> adb shell
Pepito:/ $ mount -o rw,remount /system
mount: '/dev/block/platform/soc/7824900.sdhci/by-name/system' not user mountable in fstab
I've tried to execute ANY "palm.sh" commands manually:
Code:
Pepito:/ $ cd /sdcard && su - -c \"sh palm.sh\"
: sh palm.sh: not found
On any other command I'm getting "Read only" reply
Click to expand...
Click to collapse
If you don't have the script in the /sdcard directory you haven't run the exec.sh first. This implies you didn't look at the README.
snoopy20 said:
This implies you didn't look at the README.
Click to expand...
Click to collapse
No, I DID check your readme. :silly: It has the same description as your topic
When I'm trying to execute "exec.sh", I get this:
Code:
C:\adb\palm> bash exec.sh
We're about to install some APKs. If you have ones you'd like to install stick them into apks/myapps now.
Ready?y
exec.sh: line 8: adb: command not found
exec.sh: line 11: adb: command not found
exec.sh: line 12: adb: command not found
exec.sh: line 13: adb: command not found
exec.sh: line 16: adb: command not found
That's why I've tried to execute "palm.sh" manually.
--------------------------------------------------
Executing
Code:
su -c mount -o rw,remount /system
su -c mount -o rw,remount /vendor
didn't resolve any problem.
I have manually added "palm.sh" to sdcard and executed it:
Code:
C:\adb\palm\push> adb shell
Pepito:/ $ cd /sdcard
Pepito:/sdcard $ su - -c "sh palm.sh"
Removing user installs...
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Failure [not installed for 0]
Removing system bloatware...
rm: YouTube: Device or resource busy
rm: AutoKillService.apk: Read-only file system
rm: AutoKillService.odex: Read-only file system
rm: AutoKillService.vdex: Read-only file system
rm: Fota.apk: Read-only file system
rm: Fota.odex: Read-only file system
rm: Fota.vdex: Read-only file system
rm: ConfigUpdater.apk: Read-only file system
rm: ConfigUpdater.odex: Read-only file system
rm: ConfigUpdater.vdex: Read-only file system
rm: GoogleBackupTransport.apk: Read-only file system
rm: GoogleBackupTransport.odex: Read-only file system
rm: GoogleBackupTransport.vdex: Read-only file system
rm: GoogleServicesFramework.apk: Read-only file system
rm: GoogleServicesFramework.odex: Read-only file system
rm: GoogleServicesFramework.vdex: Read-only file system
rm: StatementService.apk: Read-only file system
rm: StatementService.odex: Read-only file system
rm: StatementService.vdex: Read-only file system
rm: VerizonNameID.apk: Read-only file system
rm: VerizonNameID.odex: Read-only file system
rm: VerizonNameID.vdex: Read-only file system
rm: GmsCore.apk: Read-only file system
rm: GmsCore.odex: Read-only file system
rm: GmsCore.vdex: Read-only file system
rm: GmsCore.odex: Read-only file system
rm: GmsCore.vdex: Read-only file system
rm: TagGoogle.apk: Read-only file system
rm: TagGoogle.odex: Read-only file system
rm: TagGoogle.vdex: Read-only file system
rm: WiFiActivation.apk: Read-only file system
rm: WiFiActivation.odex: Read-only file system
rm: WiFiActivation.vdex: Read-only file system
rm: com.customermobile.preload.vzw.apk: Read-only file system
rm: com.customermobile.preload.vzw.odex: Read-only file system
rm: com.customermobile.preload.vzw.vdex: Read-only file system
rm: Elabel.apk: Read-only file system
rm: Elabel.odex: Read-only file system
rm: Elabel.vdex: Read-only file system
rm: GoogleFeedback.apk: Read-only file system
rm: GoogleFeedback.odex: Read-only file system
rm: GoogleFeedback.vdex: Read-only file system
rm: GoogleOneTimeInitializer.apk: Read-only file system
rm: GoogleOneTimeInitializer.odex: Read-only file system
rm: GoogleOneTimeInitializer.vdex: Read-only file system
rm: GooglePartnerSetup.apk: Read-only file system
rm: GooglePartnerSetup.odex: Read-only file system
rm: GooglePartnerSetup.vdex: Read-only file system
rm: Phonesky.apk: Read-only file system
rm: Phonesky.odex: Read-only file system
rm: Phonesky.vdex: Read-only file system
rm: SetupWizardOverlay.apk: Read-only file system
rm: SetupWizardOverlay.odex: Read-only file system
rm: SetupWizardOverlay.vdex: Read-only file system
rm: SetupWizard.apk: Read-only file system
rm: SetupWizard.odex: Read-only file system
rm: SetupWizard.vdex: Read-only file system
rm: VZWAPNLib.apk: Read-only file system
rm: VZWAPNLib.odex: Read-only file system
rm: VZWAPNLib.vdex: Read-only file system
rm: VZWAPNLib.odex: Read-only file system
rm: VZWAPNLib.vdex: Read-only file system
rm: Velvet.apk: Read-only file system
rm: Velvet.odex: Read-only file system
rm: Velvet.vdex: Read-only file system
rm: verizon-llk-agent.odex: Read-only file system
rm: verizon-llk-agent.vdex: Read-only file system
rm: verizon-llk-agent.apk: Read-only file system
mv: bad '/data/app/rkr.simplekeyboard.inputmethod-*': No such file or directory
Removing Verizon traces...
Removing Unsold-product-on-shelf battery decay limit...
Removing adb debugging nag
Done! - rebooting.
Still getting 'Read-only file system' even though /system /vendor was mounted with no errors.
--------------------------------------------------
After reboot i got multiple system.android stopped working
'Erase all data (factory reset)' "bricked" the phone on Verizon's welcome screen 'initialization'. Whatever app is needed for the fresh setup - needs to be freezed, not deleted.
To anyone who have executed the script I do not recommend doing 'Erase all data (factory reset)' on your device. Otherwise you'll be forced to flash and root the firmware again (in case you did make a rooted backup).
--------------------------------------------------
snoopy20 said:
>> So this fails - adb push push/palm.sh /sdcard
>> But this works? adb push push/palm.sh /sdcard/
Click to expand...
Click to collapse
Yes, exactly. Here is a screenshot showing the results of both commands: https://imgur.com/9QqSxwo
snoopy20 said:
mount -o rw,remount /system -> you are not running as su, hence the error you have.
In the console enter su bash then run mount -o rw,remount /system and it should work without error.
Click to expand...
Click to collapse
Thank you. The su bash command did seem to allow the mount -o rw,remount /system to execute correctly without errors, but the rm commands in the palm.sh script still result in "Read-only file system" errors. You can see in the below screenshot all the commands I entered.
https://imgur.com/ztAjkdc