FORUMS

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

339 posts
Thanks Meter: 30
 
By snoopy20, Senior Member on 17th February 2020, 03:00 PM
Post Reply Email Thread
19th March 2020, 06:06 PM |#21  
OP Senior Member
Thanks Meter: 30
 
More
Quote:
Originally Posted by al07th

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

Quote:
Originally Posted by al07th

No, I DID check your readme. 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).
--------------------------------------------------

I thought I stated you can't do erase all data after running this script, but I need to make it more obvious.

If /system and /vendor are remounted with -o rw without error then you're guaranteed to have write access, so something doesn't look right here at all.
19th March 2020, 06:11 PM |#22  
OP Senior Member
Thanks Meter: 30
 
More
OK do the following.

1. print me ALL the output of what happens when you run exec.sh.

2. do adb shell, su, then the following -

mount -o rw,remount /system
touch /system/test

print me the output
19th March 2020, 06:25 PM |#23  
OP Senior Member
Thanks Meter: 30
 
More
cd /sdcard && su - -c "sh palm.sh"

You are copying it straight from the text file. You should be running that exec.sh file (which pushes the apks) and copying the output, which is the same without the escapes.

I ran it again on my already cleaned phone. Please use the [ code ] [ /code ] tags for console output.

Code:
Pepito:/ $ cd /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]
Removing system bloatware...
Fixing APN list...
Removing Verizon traces...
Removing Unsold-product-on-shelf battery decay limit...
Removing adb debugging nag
Done! - rebooting
Terminated
19th March 2020, 07:56 PM |#24  
Junior Member
Thanks Meter: 1
 
More
Breakthrough! I think I've solved the issues I was having regarding script permissions. Within the main screen of Magisk Manager there is dropdown menu labeled "Advanced Settings." On every installation of the Magisk Manager apk that I made, there were two options in that menu that were always enabled by default:
  • Preserve force encryption
  • Preserve AVB 2.0/dm-verity

By disabling these two settings, then once again using the Magisk "Direct install" option (not sure if reinstalling is necessary), I was able to use the debloat script without any major edits. The only thing I still needed to change was adding a second backslash to the "sdcard" folder commands ("/sdcard/" instead of "/sdcard").

Also, Google Play Services was uninstalled through running the script, but still displayed in my apps list, and would give a "stopped running" error when launching Chrome. I went to the Google Play Services listing in Settings > Apps, uninstalled any updates that had been made to it, then it eventually recognized that it wasn't installed on the phone and removed itself from the apps list. After that, opening Chrome no longer results in the error.

Thanks again for making the script. Even with my troubles getting it to work, it made what would be a very lengthy process fairly quick. I'm looking forward to using this phone more often!
The Following User Says Thank You to tmrodden For This Useful Post: [ View ] Gift tmrodden Ad-Free
19th March 2020, 10:04 PM |#25  
Junior Member
Thanks Meter: 2
 
More
Quote:
Originally Posted by snoopy20

OK do the following.

1. print me ALL the output of what happens when you run exec.sh.

2. do adb shell, su, then the following -

mount -o rw,remount /system
touch /system/test

print me the output

No errors
Code:
PS D:\palm> adb shell
Pepito:/ $ su
Pepito:/ # mount -o rw,remount /system
Pepito:/ # touch /system/test
Pepito:/ #


Quote:
Originally Posted by snoopy20

cd /sdcard && su - -c "sh palm.sh"
You are copying it straight from the text file. You should be running that exec.sh file (which pushes the apks) and copying the output, which is the same without the escapes.

That's a clear run of exec.sh (a fresh, unzipped, all folders and files/apk are present, shell permissions are granted, Magisk and mannager are the latest ver):
Code:
PS D:\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
OK, some essential apps have been installed. If you see errors above exit now, permit debugging and re-run.
Do these next steps before continuing.

1. Ensure the device is connected to WIFI then run MagiskManager and click install then "Direct Install".
   Do this even if it says already installed. Click Reboot. Re-run MagiskManager and allow it to do the extra setup screen if asked.
   Finally, disable the auto update check in the App's settings.
2. Go to Settings -> System -> Languages & Input -> Virtual Keyboard -> Manage Keyboards
   Enable "Simple Keyboard". Ignore the warnings, we'll make it a system keyboard in a bit.
Ready?y
Copy the following: cd /sdcard && su - -c "sh palm.sh"
Don't forget after the next step to check the Palm Screen for a 'Superuser Grant' alert.
Now, run 'adb shell', paste and hit enter.
PS D:\palm> adb shell
Pepito:/ $ cd /sdcard && su - -c "sh palm.sh"
sh: palm.sh: No such file or directory
127|Pepito:/sdcard $

-----------------------------------------
Quote:
Originally Posted by tmrodden

  • Preserve force encryption
  • Preserve AVB 2.0/dm-verity

Those settings were turned off for me by default
19th March 2020, 10:50 PM |#26  
OP Senior Member
Thanks Meter: 30
 
More
Quote:
Originally Posted by tmrodden

Breakthrough! I think I've solved the issues I was having regarding script permissions. Within the main screen of Magisk Manager there is dropdown menu labeled "Advanced Settings." On every installation of the Magisk Manager apk that I made, there were two options in that menu that were always enabled by default:

  • Preserve force encryption
  • Preserve AVB 2.0/dm-verity

By disabling these two settings, then once again using the Magisk "Direct install" option (not sure if reinstalling is necessary), I was able to use the debloat script without any major edits. The only thing I still needed to change was adding a second backslash to the "sdcard" folder commands ("/sdcard/" instead of "/sdcard").

Also, Google Play Services was uninstalled through running the script, but still displayed in my apps list, and would give a "stopped running" error when launching Chrome. I went to the Google Play Services listing in Settings > Apps, uninstalled any updates that had been made to it, then it eventually recognized that it wasn't installed on the phone and removed itself from the apps list. After that, opening Chrome no longer results in the error.

Thanks again for making the script. Even with my troubles getting it to work, it made what would be a very lengthy process fairly quick. I'm looking forward to using this phone more often!

Google Play auto updates (installs) the most recent version onto the phone as soon as there's an internet connection. I did add a second uninstall line to try and nuke this but it may not catch it. These failed services errors usually disappear once the phone restarts.

I guess the /sdcard/ is a Windows thing, on Linux I have no issue.

I have not touched those magisk settings but frequently I loose 'su' (the phone reports as unrooted) until I restart.
19th March 2020, 10:54 PM |#27  
OP Senior Member
Thanks Meter: 30
 
More
Quote:
Originally Posted by al07th

That's a clear run of exec.sh (a fresh, unzipped, all folders and files/apk are present, shell permissions are granted, Magisk and mannager are the latest ver):

Code:
PS D:\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
OK, some essential apps have been installed. If you see errors above exit now, permit debugging and re-run.
Do these next steps before continuing.

1. Ensure the device is connected to WIFI then run MagiskManager and click install then "Direct Install".
   Do this even if it says already installed. Click Reboot. Re-run MagiskManager and allow it to do the extra setup screen if asked.
   Finally, disable the auto update check in the App's settings.
2. Go to Settings -> System -> Languages & Input -> Virtual Keyboard -> Manage Keyboards
   Enable "Simple Keyboard". Ignore the warnings, we'll make it a system keyboard in a bit.
Ready?y
Copy the following: cd /sdcard && su - -c "sh palm.sh"
Don't forget after the next step to check the Palm Screen for a 'Superuser Grant' alert.
Now, run 'adb shell', paste and hit enter.
PS D:\palm> adb shell
Pepito:/ $ cd /sdcard && su - -c "sh palm.sh"
sh: palm.sh: No such file or directory
127|Pepito:/sdcard $

-----------------------------------------

Those settings were turned off for me by default

That's not a clear run, you can clearly see errors at the top. It even tells you to stop if you see errors.

exec.sh: line 8: adb: command not found

So you need to add adb to your path.
19th March 2020, 11:00 PM |#28  
OP Senior Member
Thanks Meter: 30
 
More
Quote:
Originally Posted by tmrodden

using the Magisk "Direct install" option (not sure if reinstalling is necessary),

1. Ensure the device is connected to WIFI then run MagiskManager and click install then "Direct Install".
Do this even if it says already installed. Click Reboot. Re-run MagiskManager and allow it to do the extra setup screen if asked.

RTFM
20th March 2020, 12:09 AM |#29  
Junior Member
Thanks Meter: 0
 
More
Can the services that require root to be removed instead be disabled for those who are not rooted?
20th March 2020, 01:34 AM |#30  
Junior Member
Thanks Meter: 2
 
More
Quote:
Originally Posted by snoopy20

That's not a clear run, you can clearly see errors at the top. It even tells you to stop if you see errors.

exec.sh: line 8: adb: command not found

So you need to add adb to your path.

I can't understand you What should I add and where?
Those lines already has 'adb' in it.
Code:
## required
line 8: adb push push/apns-conf.xml /sdcard/

## apks
line 11: for file in apks/required/*.apk; do adb install $file; done
line 12: for file in apks/optional/*.apk; do adb install $file; done
line 13: for file in apks/myapps/*.apk; do adb install $file; done

## main script
line 16: adb push push/palm.sh /sdcard/
I didn't tweak your commands or anything! I just do exactly what is said in readme file "Run ./exec.sh in a terminal and follow the instructions." I've unpacked the zip and executed 'exec.sh'. Usb debugging is always on.
Attached Thumbnails
Click image for larger version

Name:	Capture123.PNG
Views:	24
Size:	13.2 KB
ID:	4974809   Click image for larger version

Name:	Capture124.PNG
Views:	20
Size:	9.4 KB
ID:	4974811   Click image for larger version

Name:	Capture125.PNG
Views:	18
Size:	9.6 KB
ID:	4974813   Click image for larger version

Name:	Capture126.PNG
Views:	18
Size:	28.6 KB
ID:	4974815  
20th March 2020, 01:32 PM |#31  
OP Senior Member
Thanks Meter: 30
 
More
Quote:
Originally Posted by mmopfjfd

Can the services that require root to be removed instead be disabled for those who are not rooted?

Some but not all. There are some very questionable services on this device such as mmid and a few which phone home.

Personally I would not feel comfortable running this phone without clearing those services out.
Post Reply Subscribe to Thread

Tags
palm-palm

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes