{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have Trouble with unistalling Facebook?
Try my Script
NFO:
Code:
• Helpful for [B][URL="https://forum.xda-developers.com/android/apps-games/bullshified-version-facebook-okay-to-t3586318"]Facebook LC[/URL][/B] Installation
• Deletes Facebook, Facebook Installer & Facebook Manager,
after this its clearing the Cache & Dalvik-Cache automatically
Usage:
Flash it via TWRP, done
Download:
AFH
Note:
App Updates need a manually uninstall via Google Play Store, App Drawer or whatever
Wonder if it will work on Samsung? I'll test it later. Saved the topic for future! Thanks for this [emoji106]
Edit: no it doesn't work on Note 8 (SM-N950F) 8.0.0.
The names on Samsung data/app partition have names generated on instalation:
https://imgur.com/gallery/pg3MEVw
joluke said:
Wonder if it will work on Samsung? I'll test it later. Saved the topic for future! Thanks for this [emoji106]
Edit: no it doesn't work on Note 8 (SM-N950F) 8.0.0.
The names on Samsung data/app partition have names generated on instalation:
https://imgur.com/gallery/pg3MEVw
Click to expand...
Click to collapse
New Version with more Lines
You could try
Reports are very welcome
K3V1991 said:
Reports are very welcome
Click to expand...
Click to collapse
Here is shell script equalent to your edify one...
Code:
#!/sbin/sh
FD=$2
ui_print() {
echo -e "ui_print $1\nui_print" > /proc/self/fd/$FD;
}
is_mounted() { test "$(mount | grep " $1 " | grep "rw,")"; return $?; }
abort() { ui_print "$1"; exit 1; }
ui_print "############################################"
ui_print " "
ui_print "Facebook Uninstaller Script"
ui_print " "
ui_print "Mounting partitions: /system /data /cache"
is_mounted /data || mount /data || abort "Unable to mount /data"
is_mounted /system || mount /system || abort "Unable to mount /system"
is_mounted /cache || mount /cache || abort "Unable to mount /cache"
ui_print "Partitions mounted"
ui_print " "
ui_print "Removing FB, FB Installer & FB Manager"
files="
/system/app/Facebook_AppManager
/system/priv-app/Facebook_Installer
/data/app/com.facebook.katana
/data/app/com.facebook.orca
/data/app/com.facebook.android
/data/app/com.example.facebook
/system/priv-app/FBInstaller_NS
/system/app/FBAppManager_NS
/system/app/Facebook_stub
/system/app/FBAppManager
/system/priv-app/FBInstaller
/system/priv-app/FBServices
/system/priv-app/SNS_v2_N
"
for i in $files; do
rm -rf "$i"
done
ui_print "Done!"
ui_print " "
ui_print "Cleaning Cache and Dalvik-cache"
rm -rf /cache/*
rm -rf /data/dalvik-cache/*
ui_print "Unmounting partitions: /system /data /cache"
umount /system
ui_print " "
ui_print "############################################"
Just make a empty text file update-binary and fill the above script in it....
To make all archs compatible...
Related
GingerMod Apps2SD Beta 1.0a for All ROMs!
This script is a part of GingerMod 2.1a (Galaxy Mini) (Soon)
NOTE:
I DON'T TAKE ANY RESPONSIBILITY IF YOU GET BOOTLOOPS YOUR SYSTEM/ROM/PHONE
Make a Backup first!
Click to expand...
Click to collapse
Prerequisite :
- Superuser
- busybox
- init.d run-parts
Features
move /data/app | /data/app-private | /data/dalvik-cache | /data/data | /cache to /sd-ext
set sdcard read ahead to : 2048 kb
how it work??
move /data/app | /data/app-private | /data/dalvik-cache | /data/data | /cache to /sd-ext
create symlinks of /data/app | /data/app-private | /data/dalvik-cache | /data/data | /cache to (/sd-ext)
for first boot (after installation)
move all apk's from /data/app to /sd-ext/app
remove /data/app folder
create symlink from /data/app to /sd-ext/app
mount /cache to /sd-ext/download
how to install??
open terminal
su
gmod install
All Commands
- gmod install
Install GingerMod Apps2SD if not Installed
- gmod uninstall
remove all GingerMod Apps2SD files & move back all data on /sd-ext to /data
- gmod all2sd
move /data/(app + app-private + dalvik-cache + data + cache) to /sd-ext
- gmod app2sd
move /data/app & /data/app-private to /sd-ext
- gmod cache2sd
move /data/dalvik-cache to /sd-ext/dalvik-cache
- gmod data2sd
move /data/data to /sd-ext/data
- gmod dl2sd
move /cache to /sd-ext/download
- gmod noall
move /sd-ext/(app + app-private + dalvik-cache + data + cache) to /data
- gmod noapp
move /sd-ext/app & /sd-ext/app-private to /data
- gmod nocache
move /sd-ext/dalvik-cache to /data/dalvik-cache
- gmod nodata
move /sd-ext/data to /data/data
- gmod nodl
move /sd-ext/download to /cache
Click to expand...
Click to collapse
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download Link:
GingerMod Apps2SD Beta 1.0a
http://www.mediafire.com/?fpsdg3u5kq895mg
Changelog:
http://forum.xda-developers.com/showpost.php?p=24863010&postcount=2
Sorry for my bad English
Thanks for this interesting mod.
Could you explain what's advantage off your tool compare with traditional scripts?
For experienced users only.
As the thread title suggests, this is a guide to backup, protect and restore root (su) as is sometimes needed after a system upgrade, broken Superuser update, etc...
Yes, there is an app for this, but if your like me, and enjoy full control over your system and don't mind working from the terminal, than this guide is for you.
What's involved:
We will be using two Linux commands orignially for the Linux second extended file system (ext2) but also works on ext3 and ext4.
- chattr (change file attributes)
- lsattr (list file attributes)
What's needed:
1. Terminal Emulator - there is an excellent one by Jack Palevich HERE
2. BusyBox compiled with the aforementioned utils/applets - an excellent pre-built binary by Linus Yang can be found HERE
-- I've also created a flashable zip for Linus Yang's BusyBox HERE
3. Extended file system as previously mentioned
A picture is worth a 1000 words:
Let's start with that and then review below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
su ~ we need root access rights to make changes to the system
mount -o remount ~ we remount the system rw (read/write) to make the changes
cp -p ~ we copy/backup the su binary preserving (-p) the current file attributes/permissions, i.e. [rwsr-sr-x root root]
lsattr ~ list attributes; shows the files immutable bit is unset (not protected)
chattr +i ~ the +i is to set the immutable bit on the file
lsattr ~ list attributes; shows the files immutable bit is now set (protected)
chattr -i ~ the -i is to unset the immutable bit on the file
lsattr ~ list attributes; again, shows the files immutable bit is unset (not protected)
mount -o remount,ro ~ we remount the system read-only when finished making changes (always - don't forget)
Now what:
To restore root (su), i.e. after a system upgrade, we call the (su)protected /system/su-bak from terminal and use it to restore root access rights to /system/bin/su
Code:
/system/su-bak
mount -o remount,rw /system
chown 0.0 /system/bin/su
chmod 06755 /system/bin/su
mount -o remount,ro /system
Notes:
-In all my examples above, my su binary is in the /system/bin folder, however yours may very well be in the /system/xbin folder, so handle accordingly
-As long as the upgrade (OTA) is an in-place file system update then this should work, it is essentially the same process as the OTA RootKeepers
Sources and info:
chattr:
http://en.wikipedia.org/wiki/Chattr
http://linuxcommand.org/man_pages/chattr1.html
lsattr:
http://en.wikipedia.org/wiki/Lsattr
http://linuxcommand.org/man_pages/lsattr1.html
-JR-
I made this script just now to have the ability to edit files from the phone, opened directly in your default text editor on your pc, when saving the file and pressing enter in the script the file will be pushed back to your phone and sets it to the right permission. Just some handy little script which becomes very useful when you want to test out scripts on your phone
the platform-tools path of android sdk must be accessible globally for adb.
.bashrc
Code:
export PATH=${PATH}:~/android-sdk/platform-tools
~/bin/remedit (set to rwx)
Code:
#!/bin/bash
#Edit files on your phone like editing local files
#Copyright 2013 broodplank.net
#Revision 2
DIR=${1%/*}
FILE=${1##*/}
if [[ -e mode ]]; then
rm -f mode
fi;
adb -d shell ls -l ${1} | awk '{k=0;for(i=0;i<=8;i++)k+=((substr($1,i+2,1)~/[rwx]/) \
*2^(8-i));if(k)printf("%0o ",k);print}' > mode
if [[ -e modenew ]]; then
rm -f modenew
fi;
head -c 3 mode > modenew
export FILEMODE=`cat modenew`;
if [[ -e mode ]]; then
rm -f mode
fi;
if [[ -e modenew ]]; then
rm -f modenew
fi;
echo
echo "Remote Path: '${DIR}'"
echo "Remote File: '${FILE}'"
echo "Remote Mode: '${FILEMODE}'"
echo
cd ${PWD}
if [[ -e $FILE ]]; then
rm -f $FILE
fi;
adb pull $1 $FILE
xdg-open $FILE
echo
echo "Press enter when you're done editing the file"
read -p [enter]
echo
adb remount
adb push $FILE $1
adb -d shell busybox chmod ${FILEMODE} ${1}
echo
echo "Pushed new version of: ${FILE} located in: ${DIR} with mode: ${FILEMODE}"
if [[ -e $FILE ]]; then
rm -f $FILE
fi;
Output:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just a simple TWRP Flashable BootSplash Zip for example to replace the warnings when you unlocked/rooted your device.
It will open up_param.bin and repack it with the jpg,s inside the zip.
Simply replace svb_orange.jpg and logo.jpg with a jpg of your own choice.
Make sure the images don't exceed 500kb, and keep exact same resolution (1440x3040 24bbp)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*** Download ***
Script:
Code:
#!/sbin/sh
OUTFD=$2
ZIP=$3
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
cd /tmp
rm -rf arter97
mkdir arter97
cd arter97
unzip -o "$ZIP"
ui_print " - mounting data partition"
mount /data
if [ ! -e /data/media/0/up_param.bak ]; then
ui_print " - backing up current up_param to /sdcard/up_param.bak"
cat /dev/block/platform/13d60000.ufs/by-name/up_param > /data/media/0/up_param.bak
chown 1023:1023 /data/media/0/up_param.bak
chmod 664 /data/media/0/up_param.bak
fi
ui_print " - installing new logo.jpg"
chmod 755 tar
mkdir tartemp
cd tartemp
/tmp/arter97/tar -xf /dev/block/platform/13d60000.ufs/by-name/up_param
cp /tmp/arter97/logo.jpg .
chown root:root *
chmod 444 logo.jpg
touch *
/tmp/arter97/tar -pcvf ../new.tar *
cd ..
cat new.tar > /dev/block/platform/13d60000.ufs/by-name/up_param
ui_print " - installing new svb_orange.jpg"
chmod 755 tar
mkdir tartemp
cd tartemp
/tmp/arter97/tar -xf /dev/block/platform/13d60000.ufs/by-name/up_param
cp /tmp/arter97/svb_orange.jpg .
chown root:root *
chmod 444 svb_orange.jpg
touch *
/tmp/arter97/tar -pcvf ../new.tar *
cd ..
cat new.tar > /dev/block/platform/13d60000.ufs/by-name/up_param
ui_print " - unmounting partition /data"
umount /data > /dev/null 2>&1
ui_print " "
ui_print "finished"
ui_print "Edited for s10+ by Whiskey103"
cd /
rm -rf /tmp/arter97
sync
Installation method with terminal command without TWRP (pushing up_param.bin using dd cmd on phone):
Download up_param.bin
https://www.whiskey103.nl/index1.php?dir=SamsungS10-Plus/BootSplash/s10plus/
Place in root of internal memory
Open terminal on phone like Material Terminal for example:
command:
su
command:
dd if=/sdcard/up_param.bin of=/dev/block/platform/13d60000.ufs/by-name/up_param
Credits:
@Radzian - used his base zip and edited for s10+
@ianmacd for pointing to the error in my first attempt.
Can you make for S10?
1jkan said:
Can you make for S10?
Click to expand...
Click to collapse
Yea, that's on my to do list.
Just have to get my hands on a s10 up_param.bin still.
The files are most likely the same, the zip will probably just work already.
Perhaps you can upload me your up_param.bin?
Where is this file?
1jkan said:
Where is this file?
Click to expand...
Click to collapse
Run the follow commands on your device in terminal.
su
cat /dev/block/platform/13d60000.ufs/by-name/up_param > /data/media/0/up_param.bak
It will pull up_param.bin and place it as up_param.bak on your internal SD card
Share it here please.
I can not handle it.
I try all the time but I can not. Maybe someone more experienced will help
1jkan said:
I try all the time but I can not. Maybe someone more experienced will help
Click to expand...
Click to collapse
Judging by the fact you are lookin to remove the boot warnings it's safe to say you're rooted.
Once rooted, go to playstore, grab a terminal app like Material Terminal.
Open it, typ su on first line. It will show #.
Then the command I gave you, it should be easy
1jkan said:
I try all the time but I can not. Maybe someone more experienced will help
Click to expand...
Click to collapse
try this:
https://www.whiskey103.nl/index1.ph...plash/&file=TWRP-Flashable_BootSplash_S10.zip
will this work for at&t s10+ snapdragon? please advise, thank you!
PTJunkie1975 said:
will this work for at&t s10+ snapdragon? please advise, thank you!
Click to expand...
Click to collapse
I cant test that obviously, at least needs root/unlocked bootloader etc.
I have Terminal Material. I have entered commands several times but there is always a failure. Not found
Whiskey103 said:
try this:
https://www.whiskey103.nl/index1.ph...plash/&file=TWRP-Flashable_BootSplash_S10.zip
Click to expand...
Click to collapse
This file works great. For full happiness is only missing, so that there is no Magisk stamp ...
Can I flash this with flashify?
daveuk87 said:
Can I flash this with flashify?
Click to expand...
Click to collapse
no, needs twrp.
Maybe i will add a different way with pre-made up_param.bin to be pushed with terminal later.
daveuk87 said:
Can I flash this with flashify?
Click to expand...
Click to collapse
Installation method with terminal command without TWRP (pushing up_param.bin using dd cmd on phone):
Download up_param.bin
Place in root of internal memory
Open terminal on phone like Material Terminal for example:
command:
su
command:
dd if=/sdcard/up_param.bin of=/dev/block/platform/13d60000.ufs/by-name/up_param
@Whiskey103 Will there be bootlog update for android 10? first of all, Thanks
Note: the "by android" logo change and the size of the samsung s10 (x) name too.
note2: I have a galaxy 10+
:fingers-crossed:
I don’t know what to do - appreciate some help please. another Error is:”unknown command”
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You probably don't have ro.product.device set.
If you're sure that you actually do have a "viennalte".
Code:
setprop ro.product.device viennalte
If that doesn't work you can always delete the first line or so of META-INF/com/google/android/updater-script in the zip.
Renate said:
You probably don't have ro.product.device set.
If you're sure that you actually do have a "viennalte".
Code:
setprop ro.product.device viennalte
If that doesn't work you can always delete the first line or so of META-INF/com/google/android/updater-script in the zip
Click to expand...
Click to collapse
Thanx for replying. Where I put that code?
Adb command on cmd?
Yes, adb shell.
Renate said:
Yes, adb shell.
Click to expand...
Click to collapse
My pc doesn’t recognise my p905 when I’m in download mode (it dosnt exist on device manager from some reason) so couldn’t unlock bootloader ..and didn’t unlock oem either cause I couldn’t find it/::
I do rooted my device with Odin.
Do you Think delete the first line or so of META-INF - will be enough?
Just delete the line that starts with getprop("ro.product.device")...
If there is a line before/after that includes getprop("ro.build.date delete that too.
Renate said:
Just delete the line that starts with getprop("ro.product.device")...
If there is a line before/after that includes getprop("ro.build.date delete that too.
Click to expand...
Click to collapse
amazing!!! thx!!!
trying to install nikgapps - same Error. wich line to delete here?
#!/sbin/sh
# Shell Script EDIFY Replacement
#Variables
OUTFD=/proc/self/fd/$2;
ZIPFILE="$3";
addToLog() {
echo "$1" >> "/tmp/NikGapps.log"
}
contains() {
case $2 in
*"$1"*) echo true ;;
*) echo false ;;
esac
}
decrypt() {
mkdir -p "$(dirname "$2")"
addToLog "- decrypting $COMMONDIR/busybox"
addToLog " -> source $1"
addToLog " -> destination $2"
unzip -o "$COMMONDIR/busybox" "$1" -p >"$2"
chmod 755 "$2";
}
ui_print() {
until [ ! "$1" ]; do
echo "ui_print $1
ui_print" >> "$OUTFD";
addToLog "$1"
shift;
done;
}
find_zip_type() {
addToLog "- Finding zip type"
if [ "$(contains "-arm64-" "$ZIPNAME")" = "true" ]; then
I don't know what's going on there.
It's obviously trying to be invoked like an Edify script.
You'll have to explicitly state the error and quote the entire shell script.
thanx!!!
Renate said:
You'll have to explicitly state the error and quote the entire shell script.
Click to expand...
Click to collapse
Apparently??? what you quoted above as a script is in a file named "update-binary"???
They're doing something goofy by using a shell script instead of an Edify script???
Or else update in recovery can run without an update-binary???
Apparently there is some problem with fstab so it can't remount system (right after it unmounted it)?
Does this thing have a super partition?
Renate said:
Apparently??? what you quoted above as a script is in a file named "update-binary"???
They're doing something goofy by using a shell script instead of an Edify script???
Or else update in recovery can run without an update-binary???
Apparently there is some problem with fstab so it can't remount system (right after it unmounted it)?
Does this thing have a super partition?
Click to expand...
Click to collapse
Super partition? I don’t know /: how I can check?
Please post a link to this NitGapps.apk
Renate said:
Please post a link to this NitGapps.apk
Click to expand...
Click to collapse
https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/01-May-2021/NikGapps-stock-arm64-11-20210501-signed.zip/download
I thought that that would expedite matters, but I don't have any interest in downloading 600 Megs.
Just post the script, identify the file name and tell me if there is only one file in META-INF/com/google/android
I think we're exceeding the bounds of my expertise/interest.
2 files: update - binary, updater - script.
Updater-script text is:
#!/sbin/sh
# Shell Script EDIFY Replacement
#Variables
OUTFD=/proc/self/fd/$2;
ZIPFILE="$3";
addToLog() {
echo "$1" >> "/tmp/NikGapps.log"
}
contains() {
case $2 in
*"$1"*) echo true ;;
*) echo false ;;
esac
}
decrypt() {
mkdir -p "$(dirname "$2")"
addToLog "- decrypting $COMMONDIR/busybox"
addToLog " -> source $1"
addToLog " -> destination $2"
unzip -o "$COMMONDIR/busybox" "$1" -p >"$2"
chmod 755 "$2";
}
I don't believe that that's the entire extent of updater-script.
You're telling me that the size of that file is ~412 bytes?
@Daniel.aru I own a P900 and not a P905 but for me it seems that this LOS Rom needs a higher TWRP version.
3.0.2 is the latest official available.
That's what it says as well in #1 of the thread you downloaded it from.
The dev even offers it's own version so why don't you follow his suggestion?
bmwdroid said:
@Daniel.aru I own a P900 and not a P905 but for me it seems that this LOS Rom needs a higher TWRP version.
3.0.2 is the latest official available.
That's what it says as well in #1 of the thread you downloaded it from.
The dev even offers it's own version so why don't you follow his suggestion?
Click to expand...
Click to collapse
the 3.0.2 version is an IMG file and odin flash just a TAR. tried to convert the file drom img to tar but the odin process failed. what can i do ?
Daniel.aru said:
the 3.0.2 version is an IMG file and odin flash just a TAR. tried to convert the file drom img to tar but the odin process failed. what can i do ?
Click to expand...
Click to collapse
The TWRP installed should be able to flash the img.
Afaik all after 2.8.7 are able to.
Gotta select that option after selecting "install" in TWRP.
bmwdroid said:
The TWRP installed should be abtle to flash the img.
Afaik all after 2.8.7 are able to.
Gotta select that option after selecting "install" in TWRP.
Click to expand...
Click to collapse
it worked i have the right version . tried to flash the rom again and got eror number 1