[TOOL] Nightly Updater | 1.5 | Make Your Nexus Perfect | Backup | AROMA | Manta - Nexus 10 Android Development

I only have the NEW Nexus 7 and Nexus 4, so I am relying on you all to test...
Although it should work swimmingly!
{
"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"
}
Make Your Nexus Perfect
WHAT'S NEW?
> VER 1.5 | SEPT 10 2013
-> Quick Install quickened to 4 clicks as opposed to 6
-> Backup/Restore Menu Added
-> Backup/Restore User Apps and be able to remove backups
-> Backup/Restore Anything using keep.txt and be able to remove backups
-> How To section updated with info on Backup/Restore Menu
-> junk.txt Updated with Media and Face Unlock files
-> On the horizon: App deletion in AROMA installer
PREREQS
Nexus Device that has a system app you do not want
Grade school diploma (i.e. ability to read)
THE SKINNY
WHAT IS NIGHTLY UPDATER
Nightly Updater is an AROMA installer for those that
yearn to have the cleanest device. Since I first
owned an HTC Droid Eris, I have been wiping bloatware
off of my device. Flash foward to my latest devices -
LG Nexus 4 and the 2013 Asus Nexus 7 and there ain't
much bloatware... But, all AOSP ROMs tend to come with
at least one or two apps that I can do without (and
sometimes a lot more). Nightly Updater is a simple
tool that allows users to remove unwanted system
applications in an easy manner. NU also allows users
to customize which apps are removed.
HOW DOES IT WORK
Nightly Updater works by relying on scripts that
read txt files. When customizing your script, the
installer looks for junk.txt in the "NU" folder of
your virtual (i.e. internal) SD card. Each line that
has not been "commented out" (i.e. does not have a
"#" at the front of it) or any terms (i.e. app
descriptions) that follow a "#" are removed from the
script. This leaves Nightly Updater with a clean text
file that only has the applications you want to remove.
Review:
Custom Script is called: junk.txt
Custom Script goes here: /sdcard/NU/junk.txt
#Chrome.apk -- NOT DELETED FROM DEVICE
Chrome.apk -- DELETED FROM DEVICE
Chrome.apk #Google Browser -- AFTER "#" IGNORED
HOW DO I ADD MY OWN APPS
You can add your own apps in three ways: [1] name (without
apk), [2] name (with apk), or [3] file path.
[1] Name (without ".apk")... Just type:
Code:
Chrome
The installer will automatically know it is looking for an apk and
delete Chrome.apk.
[2] Name (with ".apk")... Just type:
Code:
Chrome.apk
I think you know what it does.
[3] Full File Path... Now, you can get a little funkier and do the entire
file path like:
Code:
/data/app/Chrome.apk
This comes in
handy for files like pre-loaded wallpapers and
ringtones you may want to remove. Be cognizant of
where the files you are removing are located! This
will become very important when telling Nightly
Updater where to scan.
By the way, Nightly Updater also recognizes wildcards.
This is great for those user apps that end up having
unpredictable file names. For example:
Code:
/data/app/com.google.android.youtub*.apk
com.google.android.youtube*
These are both ways of erasing YouTube regardless of
the "-X" at the end of the file name.
WHAT'S UP WITH SCANNING
When using a Custom Script, Nightly Updater asks
where you would like to scan for apps. By default,
Nightly Updater recommends you only scan in the
System/App folder - which is where (shocker) system
apps are located. Remember, most junk apps are located
in System/App. However, Nightly Updater has also given
the option to scan Data/App. Some developers will put
apps in the Data/App folder, so it may be useful to
remove apps from there. But NORMALLY, these are only
the apps you chose to install. The final option is
to scan EVERYWHERE. Be very cautious with this command!
Remember that it is matching what you write in
junk.txt with the scan parameter. If you accidentally
wrote "system" as an app you wanted to remove instead
of SystemTuner.apk (with full scan on)... you would
erase your system folder... that's REALLY BAD!!!
Now, if you only check this option when you are using
full path and double check your junk.txt file so that
you did not make any mistakes... YOU ARE GOOD!!!
When in doubt, post your junk.txt here and I will
check it over for you
WHAT'S THE DEFAULT SCRIPT
If you download junk.txt from the OP at XDA, then
you have seen the Default Script. The Default
Script is meant to remove apps that MOST people
would consider expendable. If you are nervous to
tinker with your own Custom Script, try running
the Default Script first. If the script deleted
an app you need or did not delete at app you want
to destroy - hit me up and I will walk you
through the steps.
MORE DIRECTIONS ARE IN THE INSTALLER
DOWNLOADS
Check the "Downloads" Tab
NU-1.5.zip - Nightly Updater Installer
junk.txt - Customizable Removal Script
keep.txt - Customizable Backup Script
BUGS
Installer will occasionally hang when you press "< Back" - Reboot Device to fix temporarily
You tell me
HOW YOU CAN HELP
Give me feature ideas
Come up with more pre-loaded apps to be added to junk.txt
SPECIAL THANKS
Patrics83 and the whole ROM Cleaner team for the inspiration of this amazing tool!!! :good:​
XDA:DevDB Information
Nightly Updater, a Tool/Utility for the Google Nexus 10
Contributors
swagstr
Version Information
Status: Stable
Current Stable Version: 1.5
Stable Release Date: 2013-09-10
Created 2013-09-09
Last Updated 2013-09-10

This is a great idea! I've been doing this with shell scripts for the last few months, something I run after installing a new ROM.
One question, does the app work with system apps? The example showed /data/app/*. Is it the scam that does /data/app/* and /system/app?
Also - a nice enhancement would be able to delete an app's data/cache (but not the app) after installing a ROM.
Here's a sample from my script:
Spoiler
#!/system/bin/sh
# Mount /system rw
busybox mount -o remount,rw /system
# Variables to common directories
ei=/system/etc/init.d
tw=/sdcard/_Backup/Tweaks
sa=/system/app
# Copy bootanimation
cp $tw/../bootanimations/bootanimation-GooglePlay.zip /system/media/bootanimation.zip
chmod 755 /system/media/bootanimation.zip
# Setup init.d if needed
mkdir $ei
chmod 755 $ei
# Copy over useful scripts
cp $tw/02log $ei
chmod 755 $ei/02log
# Change build.prop to support TWC streaming app
sed -i 's/release-keys/Nexus 10/' /system/build.prop
sed -i 's/test-keys/Nexus 10/' /system/build.prop
# Remove data for problematic apps
rm -rf /data/data/com.android.providers.contacts/*
rm -rf /data/data/com.android.providers.media/*
rm -rf /data/data/com.android.deskclock/*
rm -rf /data/data/com.tmobile.thememanager/*
# Remove unwanted apps
rm $sa/Accuweather*.apk
rm $sa/Apollo.apk
rm $sa/BlueBalls.apk
rm $sa/Books.apk

sttovo said:
This is a great idea! I've been doing this with shell scripts for the last few months, something I run after installing a new ROM.
One question, does the app work with system apps? The example showed /data/app/*. Is it the scam that does /data/app/* and /system/app?
Also - a nice enhancement would be able to delete an app's data/cache (but not the app) after installing a ROM.
Here's a sample from my script:
Spoiler
#!/system/bin/sh
# Mount /system rw
busybox mount -o remount,rw /system
# Variables to common directories
ei=/system/etc/init.d
tw=/sdcard/_Backup/Tweaks
sa=/system/app
# Copy bootanimation
cp $tw/../bootanimations/bootanimation-GooglePlay.zip /system/media/bootanimation.zip
chmod 755 /system/media/bootanimation.zip
# Setup init.d if needed
mkdir $ei
chmod 755 $ei
# Copy over useful scripts
cp $tw/02log $ei
chmod 755 $ei/02log
# Change build.prop to support TWC streaming app
sed -i 's/release-keys/Nexus 10/' /system/build.prop
sed -i 's/test-keys/Nexus 10/' /system/build.prop
# Remove data for problematic apps
rm -rf /data/data/com.android.providers.contacts/*
rm -rf /data/data/com.android.providers.media/*
rm -rf /data/data/com.android.deskclock/*
rm -rf /data/data/com.tmobile.thememanager/*
# Remove unwanted apps
rm $sa/Accuweather*.apk
rm $sa/Apollo.apk
rm $sa/BlueBalls.apk
rm $sa/Books.apk
Click to expand...
Click to collapse
Most definitely works with system apps. Just add "Apollo" and scan system... /system/app/Apollo.apk is deleted! I really like your script too! Smart idea to back up init.d and boot animation!
Sent from my Nexus 4 using Tapatalk 4

swagstr said:
I really like your script too! Smart idea to back up init.d and boot animation!
Click to expand...
Click to collapse
Ok - will give this a shot when I flash again.
Please feel free to take whatever you want !!!

sttovo said:
Ok - will give this a shot when I flash again.
Please feel free to take whatever you want !!!
Click to expand...
Click to collapse
Good to hear! :good:
Also, if any of you adventurous five people out there that downloaded this bad boy want to post some results for the Manta... that would be nice (As I do not have one)

Question for you… I want to delete all the folders under a certain folder, the OS command would be like this:
rm -rf /data/data/com.android.providers.contacts/*
rm -rf /data/data/com.android.providers.media/*
Looking at the help in the junk.txt file, I'm not sure how to do this, seems I can do one file or one folder, not multiple folders?
# /path/to/file/file.txt > Deletes file.txt
# /path/to/folder/ > Deletes folder ... REMEMBER the trailing "/"

sttovo said:
Question for you… I want to delete all the folders under a certain folder, the OS command would be like this:
rm -rf /data/data/com.android.providers.contacts/*
rm -rf /data/data/com.android.providers.media/*
Looking at the help in the junk.txt file, I'm not sure how to do this, seems I can do one file or one folder, not multiple folders?
# /path/to/file/file.txt > Deletes file.txt
# /path/to/folder/ > Deletes folder ... REMEMBER the trailing "/"
Click to expand...
Click to collapse
Code:
/data/data/com.android.providers.contacts/*
Should do the trick. Still the same scripting you used to use, just easier The script does rm -rf already.
Sent from my Nexus 4 using Tapatalk 4

swagstr said:
Code:
/data/data/com.android.providers.contacts/*
Should do the trick. Still the same scripting you used to use, just easier The script does rm -rf already.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Sorry, it only does rm -f currently. So for now add the "*" and it will delete everything in the folder for ya! If it doesn't break anything I will add the recursive command for folders.

Hey y'all! Working on a sizable update that is trying include several things requested from different devices. Looking for a little help on the testing side. First few that hit me up will get it.
Sent from my Nexus 4 using Tapatalk 4

BIG WARNING! DO NOT use the Data Wipe in version 1.5 and below. The script does not exclude the "media" folder... As some of you know... That's the SD CARD! I just did it and it SUCKED lol It will be fixed in the next version along with many new updates
Sent from my Nexus 4 using Tapatalk 4

Yo. Working diligently on the backup/restore feature. Next update will be sick. Standby
Sent from my Nexus 4 using Tapatalk 4

Related

Debian Lenny now running on Hero! (see post 9!)

Has anyone managed to get Debian running on the Hero (as per the instructions in the Dream forum?)
P
I tried but I'm stuck because ext2.ko needs to be compiled for the Hero (managed to boot debian IN recovery mode with the custom image but not under the stock hero cupcake) and I haven't really had the time to look how to do that.
Also, I had hard time installing debian because of weird sh behaviour (looks like it's also cupcake's fault) and needed to modify the install script so it uses busybox tools.
I was getting a fail on the 'modprobe ext2', because of the lack of kernel modules.
Chmod 4755 on the sdcard also fails because of the way it's mounted, you need to run the installer from somewhere else instead.
P
su <installer.sh does work, but sometimes chmod just says "Operation not permitted" and mount fails when using the stock utils on my phone, using busybox seems ok, and I belive that I'm rooted correctly, so I don't know why some chmod fail.
Can ext2.ko be compiled alone or does someone need to rebuild a brand new kernel for the hero ?
ext2, ext3 & other are compiled into the current hero kernel.
Have you tried to compile a kernel from the magic 32a sources that htc released? maybe it boots on hero too (i'll try today, if i have time)?
What does modprobe actually do?
I guess it's important, because when I try and start debian, it all dies horribly and reboots the device.
Not had time or inclination to really investigate yet!
P
modprobe is a wrapper that calls insmod and rmmod(-r option).
modprobe loads a kernel module into the kernel using insmod
In this case, ext2 seems to be needed in order to mount debian.img (looks like it fails there, even if ext2 is compiled into the kernel). No idea about what makes mount fail, but I know that it works in recovery and doesn't in android
If you want to reseach a little about debian on the Hero, I suggest stripping out the reboot line in bootdeb, you will save a lot of time.
No, I didn't try to compile anything for the Hero personally, basically beacuse I have no clue about how to do so (yet)
OK so the normal mount command won't mount debian.img, but 'busybox mount' will.
Woohoo, success!
My doing 'rm /system/bin/mount' this makes 'bootdeb' use the busybox mount instead, and hey presto!
P
{
"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"
}
I'll build debian support into the next custom ROM...
P
Here is my installer.sh btw... I copied the debian.img to /sdcard/debian/debian.img but everything else to a new directory called /data/debian. This allows chmod 4755 on the installer.sh file.
I used the 2.1 zip from here.
P
Code:
su <./fsrw
modprobe ext2
clear
rm -f /data/local/bin/fsrw
rm -f /data/local/bin/bootdeb
rm -f /data/local/bin/unionfs
rm -f /data/local/bin/installer.sh
rm -f /data/local/bin/mountonly
mkdir /data/local/mnt
clear
cp -f fsrw /system/bin
cp -f bootdeb /system/bin
cp -f unionfs /system/bin
cp -f installer.sh /system/bin
cp -f mountonly /system/bin
cd /sdcard/debian
chmod 777 *
cd /system/bin/
chmod 4777 *
cd /
clear
echo " "
echo "VERSION 2.1"
echo "Custom Debian Bootloader is now installed! Quick huh?"
echo "This process does NO damage to your Android underlying OS!"
echo " "
echo "Courtesy of http://www.androidfanatic.com"
echo "Installer by Mark Walker (ghostwalker)"
echo " "
echo "To enter the Debian Linux console just type 'bootdeb'"
echo "PS: Be sure to run /scripts/onetime.sh as root from the shell after your FIRST 'boot'."
P
modaco said:
Here is my installer.sh btw... I copied the debian.img to /sdcard/debian/debian.img but everything else to a new directory called /data/debian. This allows chmod 4755 on the installer.sh file.
I used the 2.1 zip from here.
P
Code:
...
[b]
cd /system/bin/
chmod 4777 *
[/b]
...
P
Click to expand...
Click to collapse
suid for all /system/bin/ ????
That's from the standard provided installer.sh script.
I don't see any issue or danger with that tho? If you prefer you could do just do the files individually.
P
well... with
Code:
cd /system/bin/
chmod 4777 *
every executable on /system/bin will be executed with the permissions of the executable's owner, and everyone have rwx access to every single binary in /system/bin
What exactly can you do with Debian?
You sohuld be able to do anything on your phone you can do with a full debian distro.
Shame there's no hero with a hardware keyboard tho!
P
modaco said:
You sohuld be able to do anything on your phone you can do with a full debian distro.
Shame there's no hero with a hardware keyboard tho!
P
Click to expand...
Click to collapse
Yeah I figured that out lol, but what can you do with a debian distro?
Still fails here, no idea about what to do.
# busybox mount -o loop,noatime /sdcard/debian/debian.img /data/local/mnt
mount: mounting /sdcard/debian/debian.img on /data/local/mnt failed: No such file or directory
/sdcard/debian/debian.img and /data/local/mnt both exist, and this line works in recovery
Any idea ?
EDIT : Fixed it !
In bootdeb, I needed to replace "mknod /dev/loop2 b 7 0" with "mknod /dev/loop0 b 7 0"
Maybe I'll rebuild a debian zip ready for the hero with a proper install script, or even as an update.zip when I'll look into android customisation
BTW (offtopic) : I'm also really intrested in a stock android (like Cyanogen roms for the G1) with mods for the Hero (with Flac patches for example), and maybe donut ! I'll be glad to help if you need.
EDIT 2 : Also, I don't really like how the script is done. In a world of android multitasting, we only can run one debian shell at the time ?
My idea is easy to do (I think) :
- Don't make bootdeb run chroot directly
- Make a debshell script that will launch a debian shell
- Make a debshutdown script that shuts down debian and doesn't reboot the phone if you throw it arguments.
OR : Make a big debian script that parses the command line and do what the 3 different scripts do, and do like the classic bootdeb if no argument is providen
I hope I explained what I think well
I DIDN'T need to do that, how weird!
P
Why Debian?
Why would we wan't to run Debian(=linux) when we have android(=linux)??
I'm also a bit worried about the permissions in /system/bin.. This means that everyone can make changes to every binary that Android has..
Virusses are not yet in the open, but you really make it very easy to exploit your phone (imagine a virus which acts as a dialer!!)

[KERNEL/TUTORIAL] UPDATE 31/07 Howto mod the stock XXJVR/S/T kernel SU/Init.d Support

Well what do you do when you're bored and need some distraction .....Modify the stock kernel and include SU!
If you just search on the internet and especially on XDA than you find out that this is not so difficult.
The only purpose of this modified kernel is install SU and thus get ROOT
Why superuser and busybox are not installed by default is simple: it takes only 1 minute to download it from the market...
So here I give you the stock kernel + su/Root for XXJVQ/ XXJVR
installation:
1. Flash the tar file with Odin
2. Download superuser from the market and install it
3. Download Busybox installer from the market and install it
Credits to Supercurio, Hardcore, Liliniser for the tools and sources
Tutorial is Linux based!!!
So if i can do it than you can do it also!! All you have to do is read and follow post 2
Update 01/08/11 Added XXJVT
Update 01/08/11 Added Working XXJVR
Update 06/07/11 Howto add init.d support to the kernel (post 3)
Tutorial
1. Download and install the needed tools
2. extract de stock kernel to a temporary directory
3. modify the init.rc script to include your su install script.
4. add in the tmp folder busybox and su
5. add in the sbin directory your install script.
6. Recompile the kernel
7. Tar de kernel
8. Flash the kernel with heimdall or Odin
1. Download and install the needed tools
* Cross compiler: http://www.codesourcery.com/sgpp/li...eabi/arm-2009q3-67-arm-none-linux-gnueabi.bin and install it to /opt/toolchains/arm-2009q3/
* Kernel repacker made by Liliniser / dkcldark : Download from supercurio's github. with (if installed) git clone git://github.com/project-voodoo/kernel_repack_utils or goto the website https://github.com/project-voodoo/kernel_repack_utils and click on download.
* Download busybox,su and the install script from this post, and extract the files.
2. extract de stock kernel to a temporary directory
Copy the original zImage to de directory where you extracted the kernel repacker
Rename it to zImage.org
create a temp directory in the kernel repacker directory
Open a linux shell and go to kernel repacker directory
./extracter.sh -s zImage.org -d temp (hit enter)
3. modify the init.rc script to include your su install script.
Go to the temp directory and edit init.rc with your favourite editor and put this on a new line at the end off the file.
service install_su /sbin/install_su.sh
user root
oneshot
Save the file and exit
4. add in the tmp folder busybox and su
copy busybox and su to the tmp folder in your extracted kernel folder
make sure they are markt als executable.
5. add in the sbin directory your install script.
copy install_su.sh to the sbin folder in your extracted kernel folder
6. Recompile the kernel
Open a linux shell and go to kernel repacker directory
./repacker.sh -s zImage.org -d zImage -r temp -c gzip
congratulations you must cooked your first modified kernel
7. Tar de kernel
tar -H ustar -c zImage >code.tar
8. Flash the kernel with heimdall or Odin
Howto add init.d support to the stock kernel
Whell this is easy to implement
1. Open a linux shell and goto to the extracted kernel directory. (read post 2 howto do that)
add the following lines to the init.rc file
Code:
service initd_support /sbin/initd_support.sh
user root
oneshot
Save the file and exit
2. Create a new file in the sbin directory called initd_support.sh and add the following code
Code:
#!/tmp/busybox sh
if cd /system/etc/init.d >/dev/null 2>&1 ; then
for file in S* ; do
if ! ls "$file" >/dev/null 2>&1 ; then continue ; fi
/system/bin/sh "$file"
done
fi
Save the file and make it executable
3. repack the kernel (see post 2 for the howto)
4. on your device mount system Read/Writable and create the directory /system/etc/init.d
5. Copy your init scripts to /system/etc/init.d/
Make sure the name starts with a S, and set the permissions to 777
Example step 5/6
Code:
adb push Stweakscript /sdcard/
adb shell
su
/tmp/busybox mount -o remount,rw /system
/tmp/busybox mkdir /system/etc/init.d
/tmp/busybox cp /sdcard/Stweakscript /system/etc/init.d/Stweakscript
/tmp/busybox/chmod 777 /system/etc/init.d/Stweakscripts
7. flash the kernel
I'm sorry in advance.
But WTF?
vladoots said:
I'm sorry in advance.
But WTF?
Click to expand...
Click to collapse
If you only want to root your rom don't wait for devs to do it but do it your self
lownoise said:
If you only want to root your rom don't wait for devs to do it but do it your self
Click to expand...
Click to collapse
Yes, and for learning purposes. Thanks for the tips, I was sitting down to do this on another phone the other day actually... it's good to see your ideas, I was getting pretty frustrated with the limited Android init environment (the toolbox commands are so limited!).
Thanks for this nice tutorial.Worked great!
Great! Now we have good rooting kernel.
If I want root - I want root, not tweaks and other "shiny" things.
Cfroot breaks BT in some cases, Fuguroot breaks Kies connection.
Kernel which don't add Superuser.apk as a system application is the best choice - we don't have to delete other system files and there are updates of this app, so why should we have older version on /system and new on /data as an update?
Can I do "adb root" on this kernel ?
Sure Just install superuser and busybox from the market
Wooow! These are the sort of tutorials I miss here sooo much. It's a developer forum, but what we are getting here mainly are ready-products (roms, modded kernels). And why not to do it yourself. But sometimes googling for the information is not so easy, because applies to different conditions(devices, phone models, soft versions). There are many people who would spend their time learning how to compile a kernel or edit framework files. But there are so few tuts on this here... I miss tuts that tell how to do things step-by-step, without any specific linux/java knowledge.
sebarkh said:
Wooow! These are the sort of tutorials I miss here sooo much. It's a developer forum, but what we are getting here mainly are ready-products (roms, modded kernels). And why not to do it yourself. But sometimes googling for the information is not so easy, because applies to different conditions(devices, phone models, soft versions). There are many people who would spend their time learning how to compile a kernel or edit framework files. But there are so few tuts on this here... I miss tuts that tell how to do things step-by-step, without any specific linux/java knowledge.
Click to expand...
Click to collapse
And therefore I did it. Share the knowlegde and safe this forum
Why doesn't XDA have more stuff like this?
Thanks OP!
Yes, I must thank you too.
Now I understand... Sorry for my initial confusion!
I've problem:
after applying script:
line 47: ./out/project/original.cpio -> no such files or directory
Any idea ?
Where is original.cpio files ?
Screen of error:
{
"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"
}
tq man...!!
man this is amazing, I was looking for something simple like this for months. It's right, should be more posts like these in xda
+1
Thank you very much for this, lownoise
We need more topics like that, since I am interested to learn myself...
Members posting tutorials like that are always appreciated, I cannot thank you enough.
Do you know how to replace the recovery 3e with 2e additionally?
It would be great to know since I want to have it CWM compatible (flash unsigned update.zip)
AFAIK recovery is a part of the kernel....
It would be great if you could point me to the right direction.
Others probably would like to know that as well.
Thanks again.
dago said:
I've problem:
after applying script:
line 47: ./out/project/original.cpio -> no such files or directory
Any idea ?
Where is original.cpio files ?
Screen of error:
Click to expand...
Click to collapse
Which kernel did you try to modify
lownoise said:
2. extract de stock kernel to a temporary directory
Copy the original zImage to de directory where you extracted the kernel repacker
Rename it to zImage.org
create a temp directory in the kernel repacker directory
Open a linux shell and go to kernel repacker directory
./extracter.sh -s zImage.org -d temp (hit enter)
Click to expand...
Click to collapse
Two noob questions:
1. from where to copy zImage file? Where can I find zImage file?
2. How to open linux shell? Should I install linux shell application on my PC and run it or?
Sorry for such questions but I want to try.
Thanks.

[ADDON][Xperia S] Generic startup/init.d scripts support for Stock ROM/Kernel

[ info ]
i am attaching a easy to run package which contains the files required for full functionality of executing startup scripts (init.d scripts)...
basically this will allow the user to execute custom shell scripts, placed in /system/etc/init.d/ folder and they will be executed on each boot!
i dont have this device yet!!
thanks to Jozinek for testing this on his phone!
[ requirements ]
stock rooted ROM
windows PC with adb drivers installed
[ how to install ]
download the provided zip package
save it on c:\
extract the contents of the package
connect phone with usb debugging active to PC via ADB
execute "runme.bat"
follow onscreen instructions & enjoy!
incase some issue is there post the output/log of script
[ additional info ]
i have added the following things in the package:
corrected /system/bin/sysint file
run-parts binary in /system/xbin/run-parts (which is basically busybox 1.19.3 binary)
correct /system/etc/install-recovery.sh file (this file gets executed by default on stock kernel too!)
test/example script /system/etc/init.d/99test
to check if this is working the test script (99test) will create a temporary file /data/local/tmp/init.d_log_test.txt on each boot
[ donations/device fund ]
i dont yet have this device but i plan to buy it.... if u guys want to donate to me to get this device OR if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
i am currently channeling all my donations to get this phone asap and to avoid selling my ARC!!!
PAYPAL DONATION LINK
[ download link ]
generic-init.d-support-v01.zip
MD5HASH: 2eda273af4b91c34f868807820cceaee
let me know how it goes!
{
"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"
}
ENJOY!
Nice work, this will enable the Speedy v7 int.d hacks, can you incorporate this in the above? As an addon perhaps.
Done, $50 "AU" dollars coming your way mate.
-smc
somemadcaaant said:
Nice work, this will enable the Speedy v7 int.d hacks, can you incorporate this in the above? As an addon perhaps.
Done, $50 "AU" dollars coming your way mate.
-smc
Click to expand...
Click to collapse
this init.d support can be used to execute ANY shell script/program at startup... u are free to choose the ones u want...
if anyone needs help on how to push the scripts onto device let me know... but script specific info i dont have, u will need to ask the developer of those scripts..
I used this script to move dalvik cache to /cache folder:
Code:
#!/system/bin/sh
#
# relocate dalvik-cache to /cache/dalvik-cache
if [ ! -d /cache/dalvik-cache ]
then
busybox rm -rf /cache/dalvik-cache /data/dalvik-cache
mkdir /cache/dalvik-cache /data/dalvik-cache
fi
busybox chown 1000:1000 /cache/dalvik-cache
busybox chmod 0771 /cache/dalvik-cache
# create symlink
busybox mount -o bind /cache/dalvik-cache /data/dalvik-cache
busybox chown 1000:1000 /data/dalvik-cache
busybox chmod 0771 /data/dalvik-cache
After reboot i saw folder /cache-dalvid in both folders /data and /cache, is it normal?
Thank!
I found that for devices rooted with locked bootloader
Line 21 of runme.bat need to change from
HTML:
@files\adb shell "su -c 'busybox mount -t ext4 -o rw,remount /system /system'"
to
HTML:
@files\adb shell "su -c 'busybox mount -o remount,rw /system'"
This is all great, exactly what I was looking for! But what about if the ROM already has a custom kernel that makes use of /etc/init.d? Do the /etc/init.d scripts get executed twice?
EDIT: in my phone this solution can't work. In the init.rc file the following lines are commented out
Code:
#service flash_recovery /system/etc/install-recovery.sh
# oneshot
Thanks, it's working but I have a question, how we can include this in a rom?
Please respond, I would appreciate that
DooMLoRD said:
run-parts binary in /system/xbin/run-parts (which is basically busybox 1.19.3 binary)
Click to expand...
Click to collapse
That means I don't need run-parts if I've busybox installed?
1-Tell me please if I understand: I've done everything the post says Doomlord ([ADDON] [Xperia S] Generic startup /init.d scripts support for Stock ROM / Kernel) my question is this, after this I can already install scripts from cwm?
2-I try installing ''NullVoid'' tweaK by cmw and apparently well was installed. (I say apparently because i do not know if it is working)
3-Another thing about Tweaks: These have to be installed every time the phone restarts? This tweaks are compatible with the stock ics rom? (With the Doomloard Method ?
DooMLoRD said:
........
[ additional info ]
i have added the following things in the package:
corrected /system/bin/sysint file
run-parts binary in /system/xbin/run-parts (which is basically busybox 1.19.3 binary)
correct /system/etc/install-recovery.sh file (this file gets executed by default on stock kernel too!)
test/example script /system/etc/init.d/99test
to check if this is working the test script (99test) will create a temporary file /data/local/tmp/init.d_log_test.txt on each boot
..........
Click to expand...
Click to collapse
So the "install-recovery.sh" file is executed by system by default and does not need to be executed manually from terminal or what else?
And about the file...that is not a one-run file...right? It is executed at every phone boot...right??
Thank you.
Sent from my GT-I9000 using xda app-developers app
AW: [ADDON][Xperia S] Generic startup/init.d scripts support for Stock ROM/Kernel
Sorry leaving footprint, to see this again after im home.
Gesendet von meinem LT26i mit Tapatalk 2
Hello,
Is this package valid for deodexed rom?
I'm on stock .55, bootloader locked.
Currently the folder /system/etc/init.d doesn't exists
Thank you
marvasten said:
Hello,
Is this package valid for deodexed rom?
I'm on stock .55, bootloader locked.
Currently the folder /system/etc/init.d doesn't exists
Thank you
Click to expand...
Click to collapse
it doesnt matter which ROM you are on... this should work on any ROM as long as the kernel ramdisk executes install-recovery.sh service...
dont worry it creates all required folders/files

Some apps can't get access to (/emulated/0/) folder

Hi,
My device is LG G4 h-815 rooted, marshmallow 6.0 v20e.
A lot of my apps can't see the folder /emulated/0/
Thank you for your help.
Any idea ?!!
shaydzmi said:
Any idea ?!!
Click to expand...
Click to collapse
which apps?
xzfzx said:
which apps?
Click to expand...
Click to collapse
Actually, all my apps, except the stock file manager.
Some apps can show me (0) when I open it, but when I go back to the upper folder I can't go forward again.
I hope this makes sense.
shaydzmi said:
Hi,
My device is LG G4 h-815 rooted, marshmallow 6.0 v20e.
A lot of my apps can't see the folder /emulated/0/
Thank you for your help.
Click to expand...
Click to collapse
If im not mistaken when mm came out they changed they write permissions on sd card i may be wrong. But u have to make a
Sure u grant perms to all apps that need sd write. a lott of people on the g3s were having this issue. I neve did when i run mm so i dont know exactly. Just trying to spit an idea out there
TheMadScientist420 said:
If im not mistaken when mm came out they changed they write permissions on sd card i may be wrong. But u have to make a
Sure u grant perms to all apps that need sd write. a lott of people on the g3s were having this issue. I neve did when i run mm so i dont know exactly. Just trying to spit an idea out there
Click to expand...
Click to collapse
Thank you for your help.
I have no problem with the external SD card.
The problem I'm having is with internal storage, this is a little demonstration how it looks like :
When I open an app for example : Explorer, It shows me this:
{
"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"
}
When I go to the parent folder, it will become like this :
shaydzmi said:
Actually, all my apps, except the stock file manager.
Some apps can show me (0) when I open it, but when I go back to the upper folder I can't go forward again.
I hope this makes sense.
Click to expand...
Click to collapse
as the user above stated it might be a permission problem but i dont believe that is the case because /emulated/0 is the internal storage...
can you please name one app so i can check it? i am running v20d and not rooted but i dont think one letter can make the difference lol and if you can not get access with root than i dont think that it matters.
eidt: just saw you new comment i am downloading es explorer to try and look at the problem
---------- Post added at 10:56 AM ---------- Previous post was at 10:03 AM ----------
ok so i looked into it and it seems to be an android problem
it seems like some why the user t=does not have read permission
since i dont have root i can not fix it but you can (because you have root) i am guiding you blindly with out testing it...but i am sure it will not do any harm if you follow it.
first little guide so you have some kind of knowledge about what you are about to do if you dont already have.
ls - see the content of a folder
cd - enter in to a folder ( or out by ".." )
chmod - change permissions
su - use another user
for the steps:
1. download terminal emulator.
2. cd storage
3. cd emulated
4.(its a small L not a capital i) ls (just to make you sure you have the same error as me)
5. cd ..
6.(its a small L not a capital i) ls -la (just to make sure you see the permissions as me to the emulated folder(the letter on the side))
7. su root
8. chmod -R 775 emulated
and i believe your are done let me know if it worked
xzfzx said:
as the user above stated it might be a permission problem but i dont believe that is the case because /emulated/0 is the internal storage...
can you please name one app so i can check it? i am running v20d and not rooted but i dont think one letter can make the difference lol and if you can not get access with root than i dont think that it matters.
eidt: just saw you new comment i am downloading es explorer to try and look at the problem
---------- Post added at 10:56 AM ---------- Previous post was at 10:03 AM ----------
ok so i looked into it and it seems to be an android problem
it seems like some why the user t=does not have read permission
since i dont have root i can not fix it but you can (because you have root) i am guiding you blindly with out testing it...but i am sure it will not do any harm if you follow it.
first little guide so you have some kind of knowledge about what you are about to do if you dont already have.
ls - see the content of a folder
cd - enter in to a folder ( or out by ".." )
chmod - change permissions
su - use another user
for the steps:
1. download terminal emulator.
2. cd storage
3. cd emulated
4.(its a small L not a capital i) ls (just to make you sure you have the same error as me)
5. cd ..
6.(its a small L not a capital i) ls -la (just to make sure you see the permissions as me to the emulated folder(the letter on the side))
7. su root
8. chmod -R 775 emulated
and i believe your are done let me know if it worked
Click to expand...
Click to collapse
Thank you very much,
This is what I did :
Nothing happened.
It doesn't want to change permission.
shaydzmi said:
It doesn't want to change permission.
Click to expand...
Click to collapse
2 things:
1. you forgot "su root"
2.
you wrote "chmod -R775 emulated"
instead of "chmod -R 775 emulated" between the R and the 775 there is space
xzfzx said:
2 things:
1. you forgot "su root"
2.
you wrote "chmod -R775 emulated"
instead of "chmod -R 775 emulated" between the R and the 775 there is space
Click to expand...
Click to collapse
I did this, doesn't fix the problem, and I couldn't understand what is written :
shaydzmi said:
I did this, doesn't fix the problem, and I couldn't understand what is written :
Click to expand...
Click to collapse
you wrote "chmod -R 775"
instead of "chmod -R 775 emulated"
Again :
Sent from my LG-H815 using Tapatalk
shaydzmi said:
Again :
View attachment 3694608
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
did it worked?...
there is no error....
do "ls" after "cd emulated" to check it if you dont get permission denied that means it worked
No, it didn't work :
Sent from my LG-H815 using Tapatalk
shaydzmi said:
No, it didn't work :
View attachment 3694739
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
:-/ can you do ls -la after cd storage and upload the pic?
and you can try and do cd storage > su root > chmod 775 emulated > cd emulated > chmod 775 0 > chmod -R 775 0 > ls-la (the last is for checking) if it does not work
you can try one last thing reenter terminal than su root > cd mnt > cd user > chmod 775 0 > chmod -R 775 0 > cd 0 > ls-la and if this does not work i am out of ideas...i dont know maybe google did it in purpose somewhy.
in the end it is not such a big problem because you can still see the content of it you just cant just go back to it when browsing in any app which is not big deal because you can always reopen the app.
maybe some one else can help you
Sent from my LG-H815 using Tapatalk
Sent from my LG-H815 using Tapatalk
It is a big deal to me, because I'm not able to select a folder in internal storage as a virtual podcast, because the podcast app can't enter 0.
Sent from my LG-H815 using Tapatalk
try "cd /sdcard"

How to Root | Degoogle (enable Sig Spoofing) on Galaxy S20FE (Qualcomm)

{
"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"
}
Hello Guys/Girls/Non-Binary this should just be some Tutorial because I didn't find a lot about this on xda.
I have Twrp installed check out this thread on how to do it: TWRP FOR S20 FE EXYNOS
TWRP KEY COMBO: Power + VolUP
I will give you the download-link of the right version of the Twrp if you have the SM-G780G because i feel no one has it and searching comments is kinda bothering.
Twrp for SM-G780G (dunno if it works on others but should) is in attached Files on This Post.
This Version of Twrp has a small "bug" or a kinda non see able feature because it doesn't give you a GUI thing for enable Write-Rights in "/system_root" if you are a n00b don't worry explain later.
First of all you need adb and linux is kinda good because i don't know on how to do some zip things in Windows (and it kinda sucks anyway but don't cry )
So the real tutorial starts here (you HAVE TWRP and a boootable system right now) if not check the link i gave you.
First of all you root the phone (You can skip this step if you don't want root rights):
Download Magisk-Zip : Magisk Zip
Connect the Phone and your PC and put the magisk.zip on your phone. -> In Twrp go to install -> Click Magisk.zip.
Wait and some mad voodo magic from your Lord and Savior topjohnwu: https://forum.xda-developers.com/m/topjohnwu.4470081/
appears and you're rooted.
So this is the more complicated part of the tutorial (because we only have android 11 on this phone we need to kinda manually deodex you're services.jar I did a tutorial on that here:
Sig Spoofing on Android 11
You can use the exact same steps!!
short description: download haystack11-attempt, dexpatcher, the zip you need to rename, - pull and deodex your services.jar - flash the zip in Magisk!!
After that boot in system install fdroid (put the apk from your PC to the phone install via Samsung-files or some other app) download signature-spoof checker from fdroid and give the permission if that works youre good to go.
Go in Magisk -> Reboot to Recovery (Or Reboot in Twrp with Key-Combo)
Now we are debloating (the de-bloat in /system_root is necessary the pm uninstall commands and i will add them later forgot to write down and I'am always high(so i forgot them) also they are optional) for real you could de-bloat a lot more here but I doesn't wanna ruin camera app and things real Samsung boys will know what i talk about. but if you have better de-bloating options go and comment!
System_root de-bloat necessary:
adb shell
# Samsung ****
rm /system_root/system/app/ARZone/ARZone.apk
rm /system_root/system/app/BixbyWakeup/BixbyWakeup.apk
rm /system_root/system/app/FBAppManager_NS/FBAppManager_NS.apk
rm /system_root/system/app/Facebook_stub/Facebook_stub.apk
rm /system_root/system/app/YouTube/YouTube.apk
rm /system_root/system/priv-app/Bixby/Bixby.apk
rm /system_root/system/priv-app/BixbyAgentStub/BixbyAgentStub.apk
rm /system_root/system/priv-app/BixbyService/BixbyService.apk
rm /system_root/system/priv-app/GalaxyAppsWidget_Phone_Dream/GalaxyAppsWidget_Phone_Dream.apk
rm /system_root/system/priv-app/GalaxyApps_OPEN/GalaxyApps_OPEN.apk
rm /system_root/system/priv-app/GameHome/GameHome.apk
rm /system_root/system/priv-app/FBInstaller_NS/FBInstaller_NS.apk
rm /system_root/system/priv-app/FBServices/FBServices.apk
rm /system_root/system/priv-app/EasySetup/EasySetup.apk
rm /system_root/system/priv-app/OneDrive_Samsung_v3/OneDrive_Samsung_v3.apk
rm /system_root/system/priv-app/Tips/Tips.apk # stupid Samsung Tips popups
rm /system_root/system/priv-app/DeXonPC/DeXonPC.apk
rm /system_root/system/priv-app/CocktailBarService_v3.2/CocktailBarService_v3.2.apk # Edge panel top right floats
# Google ****
rm /system_root/system/app/Chrome/Chrome.apk
rm /system_root/system/app/ChromeCustomizations/ChromeCustomizations.apk
rm /system_root/system/app/Gmail2/Gmail2.apk
rm /system_root/system/app/GoogleCalendarSyncAdapter/GoogleCalendarSyncAdapter.apk
rm /system_root/system/app/GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk
rm /system_root/system/app/GoogleLocationHistory/GoogleLocationHistory.apk
rm /system_root/system/priv-app/SetupWizard/SetupWizard.apk # Without removal never passes initial setup
# Stuff replaced by MicroG aka NSA eyes
rm /system_root/system/priv-app/GmsCore/GmsCore.apk
rm /system_root/system/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk
rm /system_root/system/priv-app/Phonesky/Phonesky.apk
rm /system_root/system/priv-app/Velvet/Velvet.apk
In Twrp -> Mount System
Now open Terminal on Your PC (in use of ADB) and try to do one of the delete commands in /system_root if you're getting a rights error don't worry I explain how you get it working.
The command is:
mount -o rw,remount /system_root
Go try a delete command in /system_root again. everything should be fine now.
Go through all the de-bloat commands after that download the microG flash-able zip of your linking here: (Or use Nanolux)
https://github.com/FriendlyNeighborhoodShane/MinMicroG_releases/releases/tag/2021.04.28
Put it on your phone and flash it throuh twrp.
Boot and Boom OneUI 3.1 with MicroG and low bloat this Exynos now runs like a beast.
Sorry this my second post on this thread so don't kill me for my bad English or some dumb mistakes!
Credits to all the beautiful guys on xda! This stuff would never happen without those Legends!!
Exynos is SM-G780F any owners of the G i.e. the snapdragon 4G version following your link will have a bad time.
3mel said:
Exynos is SM-G780F any owners of the G i.e. the snapdragon 4G version following your link will have a bad time.
Click to expand...
Click to collapse
My Tutorial says Exynos only like 3 Times
Hello. So happy to see some posts like these about s20 fe Exynos version. Really appreciate your work. Im more than a noob, i can't follow all these steps as they are a bit complicated as i used to root and install twrp, custom roms on my beloved Galaxy S5! But yeah pleasing to see the forum moving abit
Kingslayer9988 said:
My Tutorial says Exynos only like 3 Times
Click to expand...
Click to collapse
not everyone who might want root knows about SoCs.
it wasn't a dig at you.
Hello, How to do safetynet, I tried universal fix riru and it does not work And a few other ways
pepcio03 said:
Hello, How to do safetynet, I tried universal fix riru and it does not work And a few other ways
Click to expand...
Click to collapse
You can't pass safetnet with microg installed, it has been an issue for a while
SafetyNet API · Issue #181 · microg/GmsCore
As of version 0.37 Pokemon Go uses GMS's safetynet feature and I for one can't get past login. What is the implementation status on safetynet, is this out of scope for microg?
github.com
If you want to pass safetynet you'll have to remove microg and reinstall google play services to able to pass it.
Hello, does this microG degoogle work with the S 20 FE Snapdragon
(G781B/DS) ?​

Categories

Resources