Database Info

[Resolved] [Q] adb install results in "/sbin/sh: pm: not found"

I am using a rooted HTC G2 with Clockwork recovery and Cyanogenmod 6.1.1.
I broke my launcher, ADW EX, using Ninjamorph; the phone now gets stuck on the boot animation.
My planned solution was to use adb install to restore a backup of ADW EX.
Using adb pull I pulled a backup of ADW EX and placed in C:\
I mounted /system and /data in recovery
Using adb from recovery I entered adb shell and removed the broken ADW EX with:
rm /data/app/org.adwfreak.launcher-2.apk
Next, I exited adb shell and entered:
adb install C:\org.adwfreak.launcher-2.apk
This generated the error:
/sbin/sh: pm: not found
I cannot get past this error and successfully install the application. I am learning as I go, any direction or assistance is welcome. I miss my Android

Solved
In case any other doofus' run into this situation.
As I have now learned, the "adb install" command will not work from recovery.
Because I had broken my launcher, and I had no alternative launchers installed, there was no launcher to hand-off to after booting; the result was an endless boot animation. Calls and notifications could still be received, etc. Most importantly, the phone was no longer in recovery and "adb install" could be used.
adb install C:\org.adwfreak.launcher-2.apk
Press "home"
Fixed.

hi,
in adb shell type:
cd /system/bin
cp pm ap_process /sbin/
exit
and now try again to install/uninstall the app.

hosseinb said:
hi,
in adb shell type:
cd /system/bin
cp pm ap_process /sbin/
exit
and now try again to install/uninstall the app.
Click to expand...
Click to collapse
I am getting error at second command
/system/bin >> cp pm ap_process /sbin/
cp pm ap_process /sbin/
cp: can't stat 'pm': No such file or directory
cp: can't stat 'ap_process': No such file or directory
can you tell why

nialexme said:
I am getting error at second command
/system/bin >> cp pm ap_process /sbin/
cp pm ap_process /sbin/
cp: can't stat 'pm': No such file or directory
cp: can't stat 'ap_process': No such file or directory
can you tell why
Click to expand...
Click to collapse
Sorry for my delay;
It's because the files (pm & ap_process) do not exist in /system/bin , try to locate them by "find" command:
adb shell
#find / -name ap_process
good luck

~ # find / -name ap_process
find: /sys/kernel/slab/L2TP/IP: No such file or directory
~ # exit
and now ?!!

kb667 said:
~ # find / -name ap_process
find: /sys/kernel/slab/L2TP/IP: No such file or directory
~ # exit
and now ?!!
Click to expand...
Click to collapse
Do you have root access? Have you installed busybox?

[Q] rooted, but permission change of the updated su not allowed

my atrix 2 was rooted and everything was good. a few days ago I copied a new su file using "Absolute System root toolbox" from sdcard to /system/bin, now i am still struggling to find a way to change the permission of the su file. looks like it's locked as a read-only file, now I can not use root explorer to change permissions of files or folders, and on my laptop using adb it gives me a $ rather than a #, it reads "operation not permitted".
any clues? thanks in advance!

**One quick note** If you got the 2.3.6 update, zerg doesn't work. In that case you will need to wait for a new root method to be made available.
This comes from the rooting thread in the dev forum. None of it is my work... You need a root shell to reset the permissions on su. Here are some instructions that should allow you to do that.
Download exploit ---> Exploit.zip
1) Unzip contents of folder to your Desktop
2) open a command terminal and navigate to the folder (cd Desktop/Exploit)
3) type the following commands
---> adb push zerg /data/local
---> adb shell
---> cd /data/local
---> chmod 777 zerg
---> ./zerg
4) Wait for the root to be gained
5) type the following commands
---> adb shell (only type this if you are no longer in [email protected])
---> mount -o rw,remount /dev/null /system
---> chmod 4755 /system/bin/su
Hope this helps / works...

Yeah you basically need to re-root your device.

[Q] Not prompted for superuser ??

On 4.1.1 completely stock. I used OTA Root Keeper to retain root successfully.
TiBu and Root Explorer were already running as root and still get root access.
Any new apps never prompt for superuser authority??
Root Checker Pro says I'm rooted,
OTA Root Keeper says:
x Superuser app installed
x Device rooted
Root permission granted
x /system supports root protection
x Protected su copy available
I tried to install SuperSU but that also failed, it doesn't
prompt for superuser rights so it can't write the su
binary.
I'm confused, what changed? how do I fix it?

I can't go into details now but your su binary is the problem. Do not uninstall anything that still has root as you will lose it. I can go into more details when I get to the office later this morning.
Sent from my SCH-I510 using xda app-developers app

su binary issues?
Reilly1812 said:
I can't go into details now but your su binary is the problem. Do not uninstall anything that still has root as you will lose it. I can go into more details when I get to the office later this morning.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I do have root access from adb I should be able to push a new binary
then set its perms, from adb shell.
Where would I find the binary I need?
I was using Superuser.apk and its binary.
Shouldn't OTA rootkeeper have saved a copy?
it says I have root, and it has copy somewhere.
--> Root Checker output
Congratulations! You have root access!
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2013-01-29 02:14 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your ASUS Transformer Pad TF300T device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market - http://goo.gl/NcnHn

I had exactly the same problem when I first upgraded from ICS to JB. Thought I had root until I decided to try AdAway. I uninstalled AdFree and attempted to install AdAway. The install failed stating that I did not have root. Of course I did since AdFree worked, ES File Explorer worked, Terminal Emulator worked, etc. Searched and searched and found discussion which highlighted the su binary to be the issue. Attempted to use the app to update the binary and it failed. I believe (and watch how fast I get corrected!) that the implementation of multiuser support in android is what requires the new versions of superuser and the binary. I documented the permissions of the existing su in /system/bin/ and ensured that I did not have another in /system/xbin/. Using ES File Explorer I copied and pasted on top of the existing su in /system/bin, checking to ensure permissions were good. You should then be able to download the latest and greatest binary using the app. This was all done with superuser. I have not worked with SuperSU. I crossed my fingers and restarted the tablet. I was good to go and have full root.
Please note that others have come back and stated that it did not work for them. I can tell you what worked for me and why I believe it did. I will add the link to the post discussing this problem as soon as I find it again.
Check out this thread which worked using adb.
http://forum.xda-developers.com/showthread.php?t=2183105

[Solved] that seems to have worked
downloaded updated su binary
adb pushed to /sdcard
adb shell
Code:
/system/bin/su
mount -o remount,rw /system
mv /system/su /system/su.bak
cat /sdcard/su > /system/bin/su
chmod 6755 /system/bin/su
exit
adb reboot

[ROOT/UNLOCK BOOTLOADER/RECOVERY]LG-D320/N/L70 devices

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 ?

[Release] Palm Debloat & Fixes Script [2020-03-11]

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