Code:
DISCLAIMER:
I am not responsible for any lost files, bricked devices, thermonuclear war,
zombie holocaust or your dog dropping dead after using these scripts.
You take full responsibility for your actions when using these scripts, and
consequently you should read the instructions, and gather enough knowledge
to know what these scripts are doing before running them on your device.
This is a series of scripts I call Android System Scripts for PowerShell, which I intend to expand upon over time. My goal is to provide some easy to use scripts to perform more or less trivial tasks that makes it easier to customize your Android system, and especially in relation to Android system upgrades on a custom ROM. (These scripts are completely ROM and device independent.)
I have chosen PowerShell because it’s a powerful scripting language that enables you to do most of the things you could in another .NET programming language (except I’m no programmer).
These scripts are made to easily replace some of your Android system files with alternate versions, primarily intended for use when upgrading your ROM. In this way you can easily further customize your ROM with alternate system APK’s, bootanimation.zip, or any other file you can think of. These scripts were primarily written out of my own need to replace Camera, MMS, Calendar and bootanimation.zip etc. in my custom ROM.
BEFORE USING THIS, please consider carefully which system files you want to replace !! Just know what you're doing, this is intended for experienced users only. This is why the script makes a backup of the old files so you can roll back. (For instance, I replaced the browser.apk with another version, which resulted in force closes, and I had to roll back to the previous version - be prepared to do so!)
Prerequisites
You must have ADB root access on your device.
A custom recovery is highly recommended.
Windows PowerShell 2.0 or higher.
Installing and preparing PowerShell
Most importantly, you need PowerShell 2.0 or higher - if you haven't already got it, download it from Microsoft here: (PowerShell is installed by default from Windows 7 and onwards)
http://support.microsoft.com/kb/968929
To use this script you also need to have the proper ADB executable present on your system, and you need to enable PowerShell to run scripts (which is disabled by default).
First, choose the folder in which you wish to install this script. This could very well be the same folder where your ADB executable files are, and it also has to be this folder where you later put the APK files to be installed.
I have installed mine into this folder: C:\Unified_Android_ToolKit\ADK tools
So if you haven't already, go grab a copy of ADB/Fastboot executables (although I don't use fastboot for anything yet), you can get them here:
http://forum.xda-developers.com/showthread.php?p=42407269
Install them into the chosen folder, and unzip the attached file with the script, so that the file android-system-scripts.ps1 is in the same folder as adb.exe. You can add this folder to your path, if you want to be able to execute the commands from anywhere.
Ok, so now ADB and the script is installed, but PowerShell still needs to be enabled to run any scripts at all. This is done by setting the Execution Policy in PowerShell, so you need to open a PowerShell console (found in Start->All Programs->Accessories->Windows PowerShell).
In PowerShell, type: Get-ExecutionPolicy
This will show you the current policy, which would be Restricted if you haven't set anything else. Now you have to set the execution policy to Unrestricted, meaning that all scripts will run.
So type: Set-ExecutionPolicy Unrestricted
Now the script is ready to be run in PowerShell.
The System-File-Replacer script
This script contains a function called System-File-Replacer. When this function is run, the script looks for a file called ass-filetable.tbl in the script folder, and any files listed in the data file will be written to the system of the attached device. A backup will be provided, both on the devices and pulled to your PC, so you can manually roll back at any time (revert function not included yet). The data file have the following format where 3 parameters are given, and each filename has its own line:
Code:
Filename Folder Permissions
firstfile.apk /system/app 644
etc.
An example ass-filetable.tbl is included in the zip. You can also define your own data file name as a parameter to the System-File-Replacer function, if you wish to maintain different file tables, like this:
Code:
System-File-Replacer mydatafile
What's important to understand about PowerShell is that running the script file android-system-scripts.ps1 only loads the function System-File-Replacer into memory. Afterwards, the function needs to be called by name (or by its alias sysfilerepl) to actually perform the task.
It is recommended to run this script while in your custom recovery, because you should clear your caches after the new system filess are installed to ensure everything works correctly.
Here is a screenshot of my first run on my N7:
{
"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"
}
The screenshot shows 3 system files being replaced - or rather 1 installed and 2 replaced, as LockClock does not exist on the device (which is why the pull fails), while Apollo.apk and bootanimation.zip gets pulled and then replaced.
The System-App-Replacer script
This is a much simpler script that reads a list of APK's in the current directory, and then performs the same operation as the System-File-Replacer script. This is simpler if you only need to install system APK's, and don't want to list them in the data file.
Step-by-step guide
Start Windows PowerShell
Go to the folder where the files you want to install on your device (and other required files) are located
Make sure that ADB and this script is in the folder as well (or added to your path)
Connect your device
Boot your device into recovery (or if you just flashed a ROM, you're already in recovery)
Mount your system partition from recovery (Important!)
From PowerShell run:
Code:
. android-system-scripts.ps1
(Yes the above command is: dot space <filename>)
From PowerShell run:
Code:
sysfilerepl
Confirm the onscreen instructions
Clear cache and dalvik cache (if you use dalvik that is)
Reboot your device
Done!
Possible developments
I plan to expand upon this collection of scripts over time, and some possible future developments could be:
Bootanimation installer (provided with System-File-Replacer)
Install more file types (provided with System-File-Replacer)
Data files and directory for more devices (provided with System-File-Replacer)
Revert function
Update.zip maker
I'm also open to ideas and suggestions if you have any particular needs, and I'll see if it fits into the toolbox to be added in the future.
:: AM ::
Changelog:
Code:
[B]v1.2.1 - 2014/1/24[/B]
System-File-Replacer: remove all files instead of only apk in pulled folder
[B]v1.2.0 - 2014/1/23[/B]
System-File-Replacer: new function included
[B]v1.0.0 - 2013/7/29[/B]
System-App-Replacer: new function included
Q: I don't feel like setting my Execution Policy to Unrestricted - is there another option?
A: Neither do I, so yes there is. It's possible to set the policy to RemoteSigned instead, in which case you can run unsigned scripts only if they're created locally. This also means that you have to convert my remote script to a local script. This is pretty easy, as all you have to do is open the script file in a text editor, copy all the text, create a new blank text file locally and paste the entire contents into this new file. Now you can delete my remote file, and rename the local file to android-system-scripts.ps1 - the script file is now a locally created file and can be run with the policy set to RemoteSigned.
Related
Its a free Root Explorer without Ads and without network use.
When busybox and root modes are enabled, you can make dumps of your nand partitions and export Kernel and initramfs (Menu/Tools)
{
"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"
}
https://market.android.com/details?id=fr.wdscript.yaffsexplorer
You can report here bug and feature requests...
Example : Dump and Rename The /cdrom partition (p17)
change dump file ext from .raw to .iso and you get your Windows drivers (MotoHelper 2.0.44 Driver 4.9.0 - 27 Jan 2011)
Version 1.9.9.8 attached
Awesome thanks, will def check this out.
useful tool
How can i dump the roofs?
can i restore it after backup?
Thank you.
This tool execute this command :
dd if=/dev/block/<partition> of=/sdcard/<partition>.raw ibs=8192 obs=8192 conv=notrunc
So you can do the reverse command (not in the tool because dangerous)
Update v1.1 : You can create yaffs images now
Epsylon3 said:
This tool execute this command :
dd if=/dev/block/<partition> of=/sdcard/<partition>.raw ibs=8192 obs=8192 conv=notrunc
So you can do the reverse command (not in the tool because dangerous)
Click to expand...
Click to collapse
Do you know, how to dump and remount the rootfs?
Thank you.
in fact, i dont know... rootfs is mounted before android (initrd on some devices)
Epsylon3 said:
in fact, i dont know... rootfs is mounted before android (initrd on some devices)
Click to expand...
Click to collapse
Ok, thank you.
Ok, been using this for a while now; couple suggestions.
1. Copy feature needs to work more like Root Explorer.
---- So when you long-press and copy a file, two buttons popup, Paste and Cancel - Maybe you could even add a third to paste quickly to a favourites folder without leaving working directory ?
2. Be able to change text size of file browser. I have big fingers heh.
3. Have a Mount/Unmount button similar to the Mount R/W in Root Explorer.
--- I find I cant copy anything to anywhere, am I just missing something ?
4. Select multiple files, and copy, delete, zip, move . . . . . to favourites ?
5. Compress files or folders and save zip to a saved favourites without leaving working directory.
6. Load apk icons maybe; easier to find things sometimes.
7. Show favourites picker on program startup. I'm always working in the same directories.
A built in text editor with line numbers would be awesome. Maybe an sqlite editor addon too ?
I like what this looks like so far; I really like that you can see symlinks, the dropdown with recent paths, nandroid dumps of any partitions (nice), and the favorites are cool. Just hoping it can take over for root explorer.
Keep up the great work so far. Will be keeping on eye on this for sure.
Thanks for your report
First, i dont want to copy Root Explorer or all these slow and "3 lines" explorers... So no image/movies preview... This tool is focused on system files exploration
Apk icons maybe but not in my prority (filter by name is nice), line size : not for the moment (maybe a zoom or something later)
The multiselect on click is almost ready (for files), to keep folder navigation
the Mount/Unmount will be in tools menu later (in mounted devices menu) i need to make a new window for that... but that need work (and could make lot of reports from unknown devices, like chinese ones)
Compression.... yea hmm v2.0
Hm. I tried this, but it is a lot slower than Root Explorer. Perhaps this is because it shows a lot more objects, or due to it having a lot of features I do not directly associate with a program to manage files. Still, I can not say that having more competition is a bad thing, so keep up the good work
its because the tool use a terminal process to list folders, and a new one on each refresh... I think i can optimize that if i keep the shell process opened.
but Root enabled, its 5x slower (220ms instead of 40ms)... i think there could be a problem with superuser tool, will try to uninstall it to check...
johnw.xda said:
Do you know, how to dump and remount the rootfs?
Thank you.
Click to expand...
Click to collapse
to remount In fact like others :
Code:
mount -o rw,remount,relatime -t rootfs rootfs /
This feature will be available in some minutes (v1.3.0)
But to dump... you need to skip /proc /tmp and /sys
Hi.
I´m using your app in a Samsung galaxy S.
I lost one file and I want to recover it from a CWM backup.
Your app lets me read the backup, but I cant save the needed file ...
Is there a possibility to extract it from the backup?
Thanks in advance
Its the next step yaffs extraction...
sorry, not for the moment (but soon)
just made an update v1.3.2 which really enhance exploration speed...
I hope you release it soon
Thanks
I can't Dump Partition. A circular thing shows up then it disapear and no text saying records in+out and that it finished (like in the screenshot). And there is no file on my SD card and yes I have plenty of space.
Tried several of the small 512k partitions and the Boot and Recovery partitions.
I'm running rooted froyo 3.4.2-155, few bloat APK's removed.
this feature uses busybox "dd" applet, try to set another busybox in setting window
you can search for them in other apps, do a search in /data/data/
Namiga said:
Hi.
I´m using your app in a Samsung galaxy S.
I lost one file and I want to recover it from a CWM backup.
Your app lets me read the backup, but I cant save the needed file ...
Is there a possibility to extract it from the backup?
Thanks in advance
Click to expand...
Click to collapse
Done... in v1.5.0 Single file or Folder for the moment... (file/folder context menu)
full extraction will be possible in next version... not linked
Introducing AAM -> Android Application Manager (PC) Version 0.1 (alpha) !! India Independence day - 15th August!!
I'm Back with Bang
New features on 0.2 3th Sept 2012 version
Link2sd support
- Right click to application and select Link to SD-Ext
- Compatible to Links2SD app
Speed Improvements
sort
- 3 levels
- Asc or Desc
- Sorting by table column header click
filter
- Text filter
- predefined filters like User apps, System apps, Linked apps, Installed on SD apps
Config directory selection dialog
- Safe mode check (to enable backup of app/data on every action, for just safe side)
Quick backup option in tools menu
Device details box
What is AAM?
AAM is a tool by which yoy can manage your applications from your computer. Main aim is to take backup of system or user application (.apk file) as well as its data, which can be restored back - all form your computer. Basically I am replicating some of the Titanium backup functionality on this PC based tool.
Who can use this?
Any android phone can use this. However currently its supported on windows only, but future versions definitely support Linux.
Where are download links?
Executable Exe - http://www.mediafire.com/?st2bdes6u7sceuq
Jar file - http://www.mediafire.com/?5il859gga8db5b3
What are features of AAM?
To list down, main features would be -
Link app to SD ext to increase internal memory (NEW)
Move apps to SD card (NEW)
List applications installed on Phone along with details like App name, package, APK file location, Freezed or Unfreezed, etc.
Backup System APK
Backup User APK
Backup data of any application
Restore / Install APK
Install by push method - Push apk to /system/app or /data/app
Restore DATA of System or user application
WIPE data of a application
Freeze/Unfreeze application (yes, this is FREEZE facility similar to titanium)
Uninstall App (user app as well as system app )
Kll app process
Reboot device in 3 modes - Normal, Recovery and Download
Universal tool - for all phones!!!
What are supported platforms and requirements to run this?
Currently I am releasing exe as well as jar file. but future versions definitely support Linux.
You need
java 1.5+ installed on your system
Android platform tools (adb.exe and aapt.exe) which comes with Android SDK. (In next versions, i am planning to package those also )
And yes, you DONT NEED TO INSTALL ANYTHING ON PHONE
Where are screenshots?
{
"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"
}
Does everything works?
No. Hence this is Alpha version. I have tested it on my phone Samsung Galaxy 3 i5801 as well as a Jelly bean emulated device. Other devices are supported but not tested. This tool dose not brick your phone but improper use may result in loss of data. Please Use at your own risk.
[Technical]
Internally, its all based on adb and aapt tools. Using adb commands and shell commands everything is done. Using aapt tool, a apk file is parsed to get app name and icon.
Written in java, and windows exe is created with JSmooth
How to use AAM?
Connect phone via usb cable. Make sure your system passes requirements mentioned above.
When AAM runs for first time, it will ask for ADB home directory (where adb.exe and aapt.exe are present) and a directory for storing backup data.
AAM will load apps installed on device. Please note that when there is no backup of a application, its icon, app name can not be retrieved.
You can start using AAM by selecting applications from list and clicking on action buttons listed on right hand side.
For quick selection, use select check-box options - To select all, system apps, user apps, Uninstalled system and user apps.
Reboot options are mentioned on menu-bar above application list.
You can change backup directory as well as ADB home directory using 'Configuration' menu.
Installing an application can be done in 2 modes. Normal mode and force mode. Normal mode will try to install app using adb. Forse mode will push application apk to user or system app directory.
If you like AAM, don't forget to give donation form Donate menu or About AAM button.
(Uninstalled apps means applications whose backup is present in AAM but its not installed on device.
Does AAM requires device rooted?
No. non-rooted devices are partially supported. In fact, AAM uses busybox. sometimes. If your device has busybox, you can use all AMM functions. Withtou busybox, some functionality may affect but core functions will work.
Limitations and known issues?
I have not tested AAM on all devices.
Contacts and messages are not restored across different versions of Android.
Operates on one device at a time.
While AAM is running, device disconnect is not detected.
Still may be more.
What are future plannings of AAM / Wish List?
(DONE)
Also, to make CWM flashable zip file of selected applications backups to restore them on phone recovery.
Do not hesitate to add items in wish-list.
Where are source files?
current source files are raw develper D) files. I will spend some time on beautification of source like create license text, comments etc and upload.
I will appreciate and welcome any feedback and suggestions.
Work in progress for integrating link2sd features....
it will mount sd-ext partition and can create links of apk files to this partitoin == more internall memory .
I will try to make this compatible with 'link2sd' app so that both (AAM and link2sd app) should be on same page.
init.d support needed from kernel to use this functionality.
I'm Back with Bang
New features on 0.2 3th Sept 2012 version
Link2sd support
- Right click to application and select Link to SD-Ext
- Compatible to Links2SD app
Speed Improvements
sort
- 3 levels
- Asc or Desc
- Sorting by table column header click
filter
- Text filter
- predefined filters like User apps, System apps, Linked apps, Installed on SD apps
Config directory selection dialog
- Safe mode check (to enable backup of app/data on every action, for just safe side)
Quick backup option in tools menu
Device details box
Links - EXE - http://www.mediafire.com/?st2bdes6u7sceuq
or
Jar - http://www.mediafire.com/?5il859gga8db5b3
help
Hello great post and congratulations to the project, I did everything to the letter and if you recognize my tablet sometimes if sometimes you could not help me? I also do not have the sdk tools aappt.exe in capreta plataform tools
Tablet china velocity
So hi folks i m gonna create this guide which will solve everyone's problem in any matter
So before we start the things required are(with links):-
-Android SDK
-Microsoft Powerpacks
-Notepad++
-Photoshop or GIMP or any other photo editing software.
-Java JRE
-Cygwin
-Android Kitchen
-Android ApkTool
And will be updating when i come to the topic
Setting Up the ADT Bundle
The ADT Bundle provides everything you need to start developing apps, including a version of the Eclipse IDE with built-in ADT (Android Developer Tools) to streamline your Android app development. If you haven't already, go download the Android ADT Bundle. (If you downloaded the SDK Tools only, for use with an existing IDE, you should instead read Setting Up an Existing IDE.)
Install the SDK
Unpack the ZIP file (named adt-bundle-<os_platform>.zip) and save it to an appropriate location, such as a "Development" directory in your home directory.
Caution: Do not move any of the files or directories from the adt-bundle-<os_platform> directory. If you move the eclipse or sdk directory, ADT will not be able to locate the SDK and you'll need to manually update the ADT preferences.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ANDROID APKTOOL
Requirements:
Winows OS
Installed Java on Windows
Installed Microsoft Powerpacks
- Easy handling: Select your apk and push the "decompile" button!
- This tool makes modding much faster and easier, no cmd handling any more.
- You can read the log which is integrated in the tool to find your mistake in the 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"
}
How to use this tool?
Follow this small how to!
Here you go..
-Well, first extract the AndroidApktool folder to C:\. Otherwise it won´t work, maybe
-copy your framework-res.apk and the apk you want to mod in the AndroidApktool folder
-Next you have to start AndroidApktool.exe
-select your framework-res.apk and push the "install" button (check log for errors)
-select the apk you want to mod/decompile and push the "decompile" button (check log for errors again)
-your decompiled apk will be located in C:\AndroidApktool\"apkname" as a folder
-if you want to compile your apk again, select your decompiled folder and compile it again (check log for errors again)
!!!NOTE!!! After compiling you have to copy the AndroidManifest.xml and the META-INF folder from your old apk to your newly compiled one!! Otherwise you´ll get bootloop !!!NOTE!!!
-your recompiled apk will be located in C:\AndroidApktool\"apkname"\dist
-you want to sign your apk? Just select your .apk and push the "sign" Button! Your signed .apk will be saved as "apkname_signed.apk"
Download
Android ApkTool
Thnx to Flextrix for this apktool
Will be updating it...............
Setting up the Android kitchen
1. Before you do anything install the java jdk(find it in dsixda's thread)
2. Download and extract the cygwin_packages.zip provided by dsixda
3. Run the set up(make sure there is no previous cygwin installation)
4. Follow the kitchen read me txt!!!
5. local package directory *must* be the path to the cygwin_packages folder that you just extracted
6, when it shows all the package names, go to the top and select "all <-> default" until it changes to "all <-> install" (you must click on the arrows)
7. Run the cygwin at least once and close, now you will see a folder inside the cygwin installation like this: Home\your user name\
8. Download the kitchen and extract to the home\your user name\
9. Rename the dsixda-android-kitchen-*** folder to just "kitchen"
10. Now your ready to run the kitchen type:
Code:
cd kitchen(enter)
./menu(enter)
11. If you did things right you should see this:
Step Two: Setting up a working folder
1. First our folder structure should look like this:
Code:
cygwin folder/home/your user name/kitchen
2. Inside the kitchen it should look like this:
3. Now we need a rom to work on, for this tutorial. Place the original rom zip in the original_update folder inside the kitchen.
4.run the cygwin.exe again type:
Code:
cd kitchen(enter)
./menu(enter)
5.now enter option 1, enter again. You should see your rom listed, choose and enter
6.you will be asked about changing the working folders name, at this point it makes no difference so just continue.
7.you will be asked to convert to update-scrip do it and continue
8. Now you can view the roms info
9. congratulations you have a working folder!!!
Step Three :repackaging the rom
Now that you have made some changes it's time to test!!
1. Run the kitchen and enter option 99 - "biuld rom from working folder"
2. Choose mgldr or clk
3. I recommend that you go with all default options until you get more experience with the kitchen.
4. When its all done you will find a folder inside "cygwin/home/yousername/kitchen" called output_zip
5. Inside the folder is your new rom ready to be flashed and tested!!!
Reserved 2
Reserved 3
Reserved 4
Cool guide..btw there are many guides on this topic..but i still respect your hardwork..gud luck for ur future guides..
{
"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"
}
Welcome to this subject where I'll share the following information to activate the terminal init.d our support, as well as the development of the topic is addressed primarily to the developer community roms in order to implement and improve its development in each of the phones and better autonomy thereof is provided.
Warning: Before continuing please read the documentation that will expose so they can check its development, those who only discuss other issues please abtenerse as this issue is not in order to respond is only to well that development develop properly targeted by this issue.
The tools I used for the development of the init.d support they can find at the end of the subject for downloading and asu same time the use so you can verify some of the things we will discuss on this issue.
no script can be universal because it is different and its code and some values and parameters are only applicable for each smartphone
Requirements: root access and SuperSU
1.- proceed with the most basic thing is to give root access to our terminal this method according in each terminal is indispensable as the first requirement
2.- as a second step this would be related to the installation of busybox in the terminal and ending with the installation of the same proceed with checking the same watching the following path with a file browser /system/xbin, if you have any doubts use the application busybox checker to verify the installation of the same
3.- as a third step needs a file browser and asu time they open the routes to them to enter and to edit text files comfortably
4.- as fourth step is to go to the /system /etc there init.qcom.post_boot.sh locate file name to open it proceed traditionally files editor of exploring and we should be on the part of all the way just to add the following lines
Code:
# support init.d
/system/xbin/busybox run-parts /system/etc/init.d
and finished we proceed to save changes to the file
5.- In this step we will create a folder called init.d name is created only once we proceed with changing the permissions would be: 0755 attached screenshot for more details of the permits, download the file will come a script called 99SuperSUDaemon and moved to the /system/etc/init.d apply the same route that takes the folder permissions ie the file 99SuperSUDaemon 0755 will have permission to run properly without any problem because if you put 0644 permits will not run
6.- proceed with terminal power cycle this is to enable support init.d our terminal as seen was not very complicated because they bring roms have actually proven but have not convecid me a story to execution of script obtaining a negative result this method I show a positive result :good:
-Tools
I bring a tool that enables init.d support only run automatically and ready
the end of the song I'll let the files that I used for this topic
1. As a first step it will be necessary to know what we are going and we want to remember that there is no script and not the same parameters with a value change at each terminal
2.- we will create in the internal memory of the terminal a folder called tools this may be optional but we'll use as an example to notice what we do at every step and can understand a bit about this topic
3.- after the tools created folder create a script so that they will ask is to copy the files that are present on that route in this case I will take as an example the following path: /proc/sys/vm is where some values are saved by heart
Code:
#!/system/bin/sh
# copying files
# script by kaiiori xda-developers
sleep 2
echo "creating internal memory directory"
busybox mkdir /storage/emulated/0/tools/vm
sleep 2
echo "copying files"
sleep 2
cp -r /proc/sys/vm /storage/emulated/0/tools
sleep 2
echo "copying completed"
exit 0;
save file vm.sh
4.- install android terminal in the terminal run the following commands
root permissions
Code:
su
go to the directory of your internal memory in this case this is my directory
Code:
cd /storage/emulated/0/tools
find files in the directory
Code:
ls
run the script through the terminal
Code:
sh vm.sh
in the directory /storage/emulated/0/tools/vm has been created a folder called VM and see if open files that have been copied to the internal memory of the terminal
5.- if you open the file values that have default in this case if you to installed scripts should the value applied to the parameter of the same appear if it is not is because there is a problem with the script in content and has to reahacer to carry just the change you want to apply
checking values applied
1.- after you created the script with the content you need to check to see if the value applied is that we have written script is the file we should show the same value as if it does not show is because the code is not right
2.- I leave a script will help them review the values and see if they were applied correctly
Code:
#!/system/bin/sh
# copying files
# script by kaiiori xda-developers
echo " " >>/storage/emulated/0/tools/info.log
echo "-------------------------------" >>/storage/emulated/0/tools/info.log
cat /proc/sys/vm/swappiness >>/storage/emulated/0/tools/info.log
echo " " >>/storage/emulated/0/tools/info.log
echo "-------------------------------" >>/storage/emulated/0/tools/info.log
root permissions
Code:
su
go to the directory of your internal memory in this case this is my directory
Code:
cd /storage/emulated/0/tools
find files in the directory
Code:
ls
run the script through the terminal
Code:
sh script_log.sh
in the directory you create a log file there appear the value that was applied in this case is 100 by default but as I modify it appears 40 that is the result we must apply
with this information I will end my subject just adding the init.d support users should provide updates and other improvements because honestly the code they use and check it when I get the same default the script I use for this and to apply the changes not be able to release it in no way is the greetings own development
reserv
reserved
I am really lost with this problem as i cannot find any other instance of it...
device: Redmi note 9S, not rooted, developer options enabled, Android 10, MIUI 12.0.4.0
in the android/data/ directory, under the com.[author].[app] files, i can't seem to find any apk files, it just appears to be empty except for an additional "files" folder that doesn't contain any useful files, while the tutorials i was following need access to a base.apk file that, in my case, does not exist. I need to know if this is a new version general android change, a device specific one ? where are the apps running from? are they all web shortcuts? if they use an apk file, where can i find it? I'm unexperienced in all those things, but I felt this would be the best place to get an answer.
LasevIX_ said:
I am really lost with this problem as i cannot find any other instance of it...
device: Redmi note 9S, not rooted, developer options enabled, Android 10, MIUI 12.0.4.0
in the android/data/ directory, under the com.[author].[app] files, i can't seem to find any apk files, it just appears to be empty except for an additional "files" folder that doesn't contain any useful files, while the tutorials i was following need access to a base.apk file that, in my case, does not exist. I need to know if this is a new version general android change, a device specific one ? where are the apps running from? are they all web shortcuts? if they use an apk file, where can i find it? I'm unexperienced in all those things, but I felt this would be the best place to get an answer.
Click to expand...
Click to collapse
Go through your file manager settings and find the option to show hidden files.
@LasevIX_
An app's APK-file is housed in folder /data/data. The APK-file itself gets installed in folder /data/app as base.apk.
Example:
/data/app/[your_package_name]-[1,2,n]/base.apk
jwoegerbauer said:
@LasevIX_
An app's APK-file is housed in folder /data/data. The APK-file itself gets installed in folder /data/app as base.apk.
Example:
/data/app/[your_package_name]-[1,2,n]/base.apk
Click to expand...
Click to collapse
yes, i know that path. my problem was that it isn't available/doesn't exist on my machine
Droidriven said:
Go through your file manager settings and find the option to show hidden files.
Click to expand...
Click to collapse
I have done that already, but the apk files still don't show up.
also, I think this thread may benefit from further precisions:
the .apk files do not show up either in the phone's built in file manager, windows explorer or in ADB ls commands.
I am practically sure it isn't hidden files, I have all the settings for viewing them enabled.
if there's some secret setting that may provide access to those files, please do tell where.
after further checking, the app i was trying do copy to my computer reports an app size of 106MB, but the com.____._____ folder reports 21B, so i suspect it may be some sort of shortcut to another folder.
.
Typically one makes use of ADB commands to pull an APK file ( Android must NOT be rooted ):
Step 1: Get location of desired app in Android's filesystem
Code:
adb shell "pm path com.example.someapp"
The output will look something like
package:/data/app/com.example.someapp-2.apk
or
package:/data/app/com.example.someapp-nfFSVxn_CTafgra3Fr_rXQ==/base.apk
Step 2: Using the full path name from Step 1, pull the APK file from the Android device to the Windows computer
Code:
adb pull /data/app/com.example.someapp-2.apk <PATH-ON-PC>
jwoegerbauer said:
Typically one makes use of ADB commands to pull an APK file ( Android must NOT be rooted ):
Step 1: Get location of desired app in Android's filesystem
Code:
adb shell "pm path com.example.someapp"
The output will look something like
package:/data/app/com.example.someapp-2.apk
or
package:/data/app/com.example.someapp-nfFSVxn_CTafgra3Fr_rXQ==/base.apk
Step 2: Using the full path name from Step 1, pull the APK file from the Android device to the Windows computer
Code:
adb pull /data/app/com.example.someapp-2.apk <PATH-ON-PC>
Click to expand...
Click to collapse
I wasn't aware that you could use adb to find the location of apps, but the command you suggested gives an unexpected result (screenshot attached). it gives multiple results of files despite them being invisible to file explorers. Once i try to pull the package with the method you suggested, it gives an error as if it wasn't there. Did I type the wrong syntax? does the "pm path" command only give expected locations for files?
{
"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"
}
for clarification, I am trying to access the netflix client APK in order to manually make it recognise widevine L1 certificates, as described in this thread: https://forum.xda-developers.com/t/netflix-hd-on-tab-s2.3274295/#post-65001865 .
The NETFLIX APK you want to extract from Android is a so-called Split-APK. IMO you've to turn this Split-APK into a normal non-Split-APK.
How to:
How to turn a split APK into a normal non-split APK - Platinmods.com - Android & iOS MODs, Mobile Games & Apps
Hey guys, recently many modders contacting me about how to mod a split APK. We have already many tutorials about how to download or extract the split APKs, mod a split APK as it is and how to use a split APK installer to make the mod apply to the device. Here some examples of the mentioned...
platinmods.com
jwoegerbauer said:
The NETFLIX APK you want to extract from Android is a so-called Split-APK. IMO you've to turn this Split-APK into a normal non-Split-APK.
How to:
How to turn a split APK into a normal non-split APK - Platinmods.com - Android & iOS MODs, Mobile Games & Apps
Hey guys, recently many modders contacting me about how to mod a split APK. We have already many tutorials about how to download or extract the split APKs, mod a split APK as it is and how to use a split APK installer to make the mod apply to the device. Here some examples of the mentioned...
platinmods.com
Click to expand...
Click to collapse
This will be helpful for teh future, thank you for directing me to that tutorial.
but it still requires to pull the apk, which i have not been able to do.
as described in my previous reply, ADB seems to be able to return the location of the apk, but can't pull it, as if it never existed.
According to the screenschot you provided earlier I think the package ( APK ) you want to pull is stored as
/data/app/com.netflix.mediaclient-YUY-VwSu3KeCc44bkA
shorthanded as
base.apk
but don't really know it: this is not my world.