Python Script for Copy and Reinstall all Third Party apps from Device - Asus ZenFone Max Pro M1 Themes, Apps, and Mods

i have created python script for copy all third party apps installed in your device and copy all the apps in your pc.
NON-ROOT script.
script uses adb shell commands for copy and reinstall apps in your device so no need of root access.
for now i only manage to test it on X00TD(Android 9.0) for now. Update me for other device/android versions.
Steps for backup apps :-
1) Download python 3 from python.org and install it in your pc.
2) Download python script files from the link below.
3) Run "windows-backup.py" if you are on Windows OS, else "linux-backup.py" for linux based OS.
Steps for reinstall apps:-
*first 2 steps are same
3) Run "install-apps.py" for install apps OS dosent effect on this script.
YouTube :- www . youtube . com / watch?v=EEoPo7Hqt3k
File Download link :- bit.ly / 2Lhqe0T (remove spaces).

I'm getting error.
Zenfone max pro m1
Android: 8.1 (stock, No root, bootloader unlocked, TWRP recovery)
PC: Windows 8.1
USB debugging enabled, USB mounted as storage
ERROR msg in screenshot

foxonfox said:
I'm getting error.
Zenfone max pro m1
Android: 8.1 (stock, No root, bootloader unlocked, TWRP recovery)
PC: Windows 8.1
USB debugging enabled, USB mounted as storage
ERROR msg in screenshot
Click to expand...
Click to collapse
Install adb in your pc first

Can you tell me why I'm getting this error?
[email protected]:~/Documents/App backup-restore$ python3 linux-backup.py
Folder Created
Fetching Packages list from device
error: no devices/emulators found
Packages are fethced
Copying Started
Total 1 Apps
b'
1 : .apk
/bin/sh: 1: Syntax error: Unterminated quoted string
Traceback (most recent call last):
File "linux-backup.py", line 47, in <module>
os.rename("base.apk",name)
FileNotFoundError: [Errno 2] No such file or directory: 'base.apk' -> '.apk'
[email protected]:~/Documents/App backup-restore$
What's wrong or what am i doing wrong?
OS 9 MSM Extended with MicroG installed (No Google)
EDIT:
got it after enabling USB DeBugging

Related

Galaxy Player 5.0 Root (linux)

Hello
This will be my first tutorial on rooting a galaxy player 5.0 using Ubuntu 12. please let me know if there are some changes you believe needs to be made. i will also update this document with photos and add a second part for flashing a custom ROM. i have it as an attachment as well as copied into this post.
Root and Flash Galaxy Player 5.0 (linux)
Hello after some searching I deiced to learn how to root and flash my Galaxy Player 5.0 loaded with GingerBread (2.6.35-Kernal, 2.3.5-firmware).
**First we need to prep your player**
1) go to settings
2) now to applications
3) now open development
4) finally check the USB debugging box
**Install needed Apps**
5) download and install terminal emulator
**Install android SDK**
6) open terminal and use the command (adb) we are looking for “Android debug bridge”
1) if you get android bridge move to step 3 if you do not get android bridge move to step 2
7) adb= Android SDK
1) open terminal and use type sudo apt-get install eclipse-jdt allow the install to complete
2) now lets install the android sdk using this link android-sdk
3) use the software defaults allow it to complete the install process
4) open the eclips application
1) go to help → install new software click add end enter this URL //dl-ssl.google.com/android/eclipse/
2) check the available boxes and choose next followed by finish (restart eclips)
3) now click window → preferences choose browse locate your android SDK folder
4) Apply → OK
5) now choose window → SDK manager
1) select all the packages you will be working with (I choose 4.0.3 and above)
**Lets Root your Player**
8) plug your micro USB into player and Linux box
9) download the following files rootme files //papousek.org/downloads/galaxy_player/rootme.tar.gz
10) extract the file to your home dir
11) open terminal and use the following command
1) cd root/
2) chmod +x rootme.sh
3) ./rootme.sh
12) this will take a few mintutes let the program run **you will know the process is done when your player reboots**
**Lets check if your player is Rooted**
13) open the terminal emultaor you installed on your player
14) in the command line enter the following command
1) su
2) enter
15) you should get a “Allow super user box” choose allow
16) in the terminal emulator type
1) you should see a $ symbol
2) type su
3) you should now see a # symbol this means you are root.
I rooted mine using Oneclick Root. Version 2.2.2.It took less than 5 minutes. My player has the 2.3.5 stock firmware.

[Q][XU][JB] Unable to dev - Permission denied

Hello guys, I have a little problem with developing apps in my phone.
I installed Stock Android 4.1.2 v4 for my Xperia U ST25i ( http://forum.xda-developers.com/showthread.php?t=2284394 ) (I wanted to post this issue in this thread but i'm new here and I just can't... anyways, rules are rules), and i'm have some issues when I want test APK's in my phone via ADB or Eclipse-ADT.
When I click excecute ( or do adb install), the process will fail, showing me that:
Code:
[2013-07-23 16:40:48 - AWifiSignal] ------------------------------
[2013-07-23 16:40:48 - AWifiSignal] Android Launch!
[2013-07-23 16:40:48 - AWifiSignal] adb is running normally.
[2013-07-23 16:40:48 - AWifiSignal] Performing net.elsemieni.awifisignal.SplashActivity activity launch
[2013-07-23 16:40:48 - AWifiSignal] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2013-07-23 16:40:51 - AWifiSignal] WARNING: Unknown device API version!
[2013-07-23 16:40:51 - AWifiSignal] Uploading AWifiSignal.apk onto device 'YT9002B59S'
[2013-07-23 16:40:52 - AWifiSignal] Installing AWifiSignal.apk...
[2013-07-23 16:40:53 - AWifiSignal] Installation failed due to invalid APK file!
[2013-07-23 16:40:53 - AWifiSignal] Please check logcat output for more details.
[2013-07-23 16:40:53 - AWifiSignal] Launch canceled!
In simple words, doesn't install beacuse [INSTALL_FAILED_INVALID_APK] error code.
Of course, i have Debugging activated in my phone and install 3rd party applications.
By the way, Logcat gives me that
Code:
07-21 18:05:23.663: W/zipro(25492): Unable to open zip '/data/local/tmp/AWifiSignal.apk': Permission denied
07-21 18:05:23.673: W/PackageParser(25492): Unable to read AndroidManifest.xml of /data/local/tmp/AWifiSignal.apk
That's curious I can't write inside it. I searched the forums and I applied a workaroud solution (http://forum.xda-developers.com/showthread.php?p=40040546&postcount=4), to make a link from tmp to sdcard folder. It worked in this way, but ruined the phone sys after reboot ( crashes randomly, most critical app's frezzes, etc), so doesn't work.
I know that's a firmware bug, but... any ideas about this? There's another workaround to make tmp safely writable, or any way to change the folder who ADB uses to install apps remotely?
Thanks! :laugh:

[Help!] Update System with Terminal Emulator with Error "no space left on device"

[Help!] Update System with Terminal Emulator with Error "no space left on device"
I follow the following instruction to update my Meizu Pro5 with success for several times, but i got an error message "no space left on device" this time. Is there any way to solve this?
1. Enable root
Enable root by tapping on Settings-> Accounts-> My Flyme-> Personal settings (first option) -> System privileges and set it to open - accept disclaimer and confirm.
2. Download and successfully install Busybox (from Google Play or see .apk below)
3. Download and install a Terminal Emulator (from Google Play or see apk below)
4. Download the correct and desired international (i) ROM/firmware (update.zip) for your device
5. Download and use the update.zip (firmware) converter that creates the required system-i.img
Click here to download converter first
Copy system.new.dat and system.transfer.list (from the update.zip) to the folder “in” (see converter folder)
Then start the converting process by starting System-conVERTER.cmd and pressing option 1 [enter]
If successfully converted you can find the system-i.img in the ‘‘out’’ folder.
6. Copy the converted system-img from ‘‘out’’ to the internal memory of your Meizu device
7. Go to Settings-> Display-> Sleep and set it to at least 10 minutes
8. Start the Terminal Emulator and run (type) the super user command
su
A permission popup will come; give permission by tapping allow (always allow).
9. Now run (type) the command for installing the system-img.
dd if=/sdcard/system.img of=/dev/block/platform/XXXXXXX/by-name/system
Replace XXXXXXX with the correct partition system for your device
MX4 Pro = 15540000.dwmmc0
M2 note = mtk-msdc.0
MX4 = mtk-msdc.0 (OR mmcblk0p6)
MX5 = mtk-msdc.0 (OR mmcblk0p18)
Pro 5 = 15570000.ufs
Example for MX5 : dd if=/sdcard/system.img of=/dev/block/platform/mtk-msdc.0/by-name/system
Note: Pro5 might require: dd if=/storage/emulated/0/system.img instead of /sdcard/
10. The installation should start after the ‘‘dd if’’ command, but please note…
…it may seem that the copying/process did NOT start because you didn’t notice it, but it DID start.
do NOT type a new command or whatsoever, just…
…be patient and give your device 5-10 minutes to process.
11. When the process is done you’ll see a # at the very end
Your device should be unresponsive by now - this is normal
12. Now just shutdown your phone (hold power button) and reboot it
13. Once successfully booted your device should be running an I-rom
Once in Flyme again it is wise - but not necessary - to completely reset your phone. Go to settings->about phone->memory->factory data reset-> check both boxes and click start cleaning (this could take 5-10minutes). Always backup your stuff if necessary.

Dual boot Redmi 9(GSi with miui)

prove:
I give a zip file.download and extract it.you can find a video watch it as the prove of this post
You can test GSi ROM without any data loss.....
Requirements:
1.Need a laptop with Linux (window also can do...but Linux is batter for CMD line)
2.Unrooted phone.(magisk patch boot not boot gsi for my case try it if it work or not)
3.vbmeta.img(flash it via 'fastboot flash vbmeta vbmeta.img')
3.java installed in your machine...
4.Working brain to solve Errors.:fingers-crossed::fingers-crossed:
Step 1:
Go to the link and download any official gsi arm64-ab version (I can not boot unofficial gsi..Descendant X....any room which it not boot remember you cannot boot it even fastbood method )
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0IRaTTGUOyl04z17LCE96H
Step 2:
Extract and rename file as 'system.img'...
Step 3:
Now open CMD terminal from where your system.img located and paste this cmd...
simg2img system.img system_raw.img
Error and slove...
You need to install simg2img on Linux...
After install and run this CMD you found error like about header file magic or like something...do not worry... that's mean your system.img file already a raw file and do not need to convert it..just rename this file as 'system_raw.img'
Step 4:
Now open CMD terminal from where your system_raw.img located paste this cmd...
gzip -c system_raw.img > system_raw.gz
Wait for finish..
Step 5:
Now connect your phone with via cable and in developers options turn on usb debugging mood and run this CMA...
adb push system_raw.gz /storage/emulated/0/Download/
Wait for finish........
Step 6:
Now run this CMD..
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
Step 7:
Now run this CMD...
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
You need to varying your identity by fingerprints or parttern if your device has lock function on...after varify you will notice a notification like this...
Dynamic system update
That's mean you can successfully do my instructions....:cyclops::cyclops:..
Wait for finish....
Now you have two option restart or discard....
Tap restart to go to your gsi or discard to destroy gsi install....
On gsi you can do what you want..
If your work or discover finis then reboot the phone with power button option.
After reboot you are now miui and yes no data lost...
After some moments you can again get two options (Restart or discard)...
This process go untill you discard gsi...
If you stay gsi after reboot then run the CMD....
adb shell gsi_tool enable
Now you can stay gsi after reboot how many time you want...
Disable this feature now type this CMD ...
adb shell gsi_tool disable
If you face some problems....tell me want is your problem......
If you can dual boot your device the thanks is free...
Go throw below link for more information...
https://developer.android.com/topic/dsu
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Halloul said:
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Click to expand...
Click to collapse
I think it's better to provide your questions in Redmi note 9 fourms in Xda.
Check it :https://forum.xda-developers.com/redmi-note-9
Halloul said:
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Click to expand...
Click to collapse
Redmi note 9 supporting dynamic storage if it come with android 10 out of box..if you hava fastboot rom then go to image folder on it and find super.img.
If super.img found that's mean your are good to go...
Or if you find system.img and vendor.img then sorry
1st time its works great
Then i want to check another gsi but not showing in the notification menu
Mantipallykrishna said:
1st time its works great
Then i want to check another gsi but not showing in the notification menu
Click to expand...
Click to collapse
If you use two GSI. That's mean you install a a dynamic GSI over a GSI then the problem will happen. Because all GSI can not capable with it. If you flash dynamic GSI over MIui Rom then the problem not happened.when you in MIui then restart to go dynamic GSI.when you are in dynamic GSI then do not reboot your device just power off and then power on your device to go MIui.then you find the dynamic GSI restart option again.even if you can not find the notification then go to your device recovery option and reboot device from recovery mood.
Even if your problem not solve then you can activate GSI from adb cmd
adb shell gsi_tool enable
Then you can go GSI and when you reboot you can not go back MIui but it is good option to use GSI without data loss.to deactivate just run this adb cmd
adb shell gsi_tool disable
Now reboot and then you can back MIui again..
But remember to check if your dynamic GSI can connect you PC via adb.
This method work for me.I also face the same problem like you.hope you can solve your problem.and remember one thing that if you use magisk patched boot.img then you can not boot your dynamic GSI.I think it is a bug hopefully it will solve soon
the first time worked fine, then i tried the command: adb shell gsi_tool enable, for some reason i wasn't able to connect to gsi with adb to turn it off: adb shell gsi_tool disable
i flashed miui with miflash, but now the installation won't start again
just found out that when a micro sd card ist in the phone, for some reason dsu won't show up, i removed the micro sd card, restarted the phone, and now dsu shows in the notification bar
Shas45558 said:
prove:
I give a zip file.download and extract it.you can find a video watch it as the prove of this post
You can test GSi ROM without any data loss.....
Requirements:
1.Need a laptop with Linux (window also can do...but Linux is batter for CMD line)
2.Unrooted phone.(magisk patch boot not boot gsi for my case try it if it work or not)
3.vbmeta.img(flash it via 'fastboot flash vbmeta vbmeta.img')
3.java installed in your machine...
4.Working brain to solve Errors.:fingers-crossed::fingers-crossed:
Step 1:
Go to the link and download any official gsi arm64-ab version (I can not boot unofficial gsi..Descendant X....any room which it not boot remember you cannot boot it even fastbood method )
https://www.google.com/url?sa=t&source=web&rct=j&url=https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list&ved=2ahUKEwj04pKZwfnrAhVLfXAKHV8FAFcQFjAAegQIARAB&usg=AOvVaw0IRaTTGUOyl04z17LCE96H
Step 2:
Extract and rename file as 'system.img'...
Step 3:
Now open CMD terminal from where your system.img located and paste this cmd...
simg2img system.img system_raw.img
Error and slove...
You need to install simg2img on Linux...
After install and run this CMD you found error like about header file magic or like something...do not worry... that's mean your system.img file already a raw file and do not need to convert it..just rename this file as 'system_raw.img'
Step 4:
Now open CMD terminal from where your system_raw.img located paste this cmd...
gzip -c system_raw.img > system_raw.gz
Wait for finish..
Step 5:
Now connect your phone with via cable and in developers options turn on usb debugging mood and run this CMA...
adb push system_raw.gz /storage/emulated/0/Download/
Wait for finish........
Step 6:
Now run this CMD..
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
Step 7:
Now run this CMD...
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
You need to varying your identity by fingerprints or parttern if your device has lock function on...after varify you will notice a notification like this...
Dynamic system update
That's mean you can successfully do my instructions....:cyclops::cyclops:..
Wait for finish....
Now you have two option restart or discard....
Tap restart to go to your gsi or discard to destroy gsi install....
On gsi you can do what you want..
If your work or discover finis then reboot the phone with power button option.
After reboot you are now miui and yes no data lost...
After some moments you can again get two options (Restart or discard)...
This process go untill you discard gsi...
If you stay gsi after reboot then run the CMD....
adb shell gsi_tool enable
Now you can stay gsi after reboot how many time you want...
Disable this feature now type this CMD ...
adb shell gsi_tool disable
If you face some problems....tell me want is your problem......
If you can dual boot your device the thanks is free...
Go throw below link for more information...
https://developer.android.com/topic/dsu
Click to expand...
Click to collapse
its give me proble when in start activity at the end.
===========================================================
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
Exception occurred while executing 'start-activity':
java.lang.IllegalArgumentException: No intent supplied
at android.content.Intent.parseCommandArgs(Intent.java:7790)
at com.android.server.am.ActivityManagerShellCommand.makeIntent(ActivityManagerShellCommand.java:341)
at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:438)
at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:189)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:11390)
at android.os.Binder.shellCommand(Binder.java:936)
at android.os.Binder.onTransact(Binder.java:820)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:5216)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3162)
at com.android.server.am.OppoActivityManagerService.onTransact(OppoActivityManagerService.java:169)
at android.os.Binder.execTransactInternal(Binder.java:1166)
at android.os.Binder.execTransact(Binder.java:1130)
=========================================================
Here Is the error code. Im on A11. Realme C3. But when Im use Dsu and download and install from dsu it works im confused ??
fire7ly said:
its give me proble when in start activity at the end.
===========================================================
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
Exception occurred while executing 'start-activity':
java.lang.IllegalArgumentException: No intent supplied
at android.content.Intent.parseCommandArgs(Intent.java:7790)
at com.android.server.am.ActivityManagerShellCommand.makeIntent(ActivityManagerShellCommand.java:341)
at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:438)
at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:189)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:11390)
at android.os.Binder.shellCommand(Binder.java:936)
at android.os.Binder.onTransact(Binder.java:820)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:5216)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3162)
at com.android.server.am.OppoActivityManagerService.onTransact(OppoActivityManagerService.java:169)
at android.os.Binder.execTransactInternal(Binder.java:1166)
at android.os.Binder.execTransact(Binder.java:1130)
=========================================================
Here Is the error code. Im on A11. Realme C3. But when Im use Dsu and download and install from dsu it works im confused ??
Click to expand...
Click to collapse
Use dsu..it is easy method
Shas45558 said:
Use dsu..it is easy method
Click to expand...
Click to collapse
Yeah You Are Right ! . But Dsu gives Only Aosp Gsis. Which Is not So Great. If Any Ways I use Pixel Gsis it Would Be Great.
fire7ly said:
Yeah You Are Right ! . But Dsu gives Only Aosp Gsis. Which Is not So Great. If Any Ways I use Pixel Gsis it Would Be Great.
Click to expand...
Click to collapse
Hmm...thats is the point...use linux and when you input any cmd you must open cmd pannel from where you kept the rom which you try to installed...
Shas45558 said:
Hmm...thats is the point...use linux and when you input any cmd you must open cmd pannel from where you kept the rom which you try to installed...
Click to expand...
Click to collapse
you mean same directory where gsi present.
fire7ly said:
you mean same directory where gsi present.
Click to expand...
Click to collapse
Yes..
work in poco m3?
how about redmi note 9 pro sir? can you give me a link for the tut?

How To Guide ( Rewrite).Using FastbootD .

This step by step tutorial is all about
☆☆☆ FastbootD video tutorial : https://m.youtube.com/playlist?list=PLvggR4skCxYzhB3SXxpSx4LvRzGwx9k45​Full round-trip of "GSIs flashing process".​
Step to install Stock ROM with Fastboot ability.(need 3in1.tar)
Step to flash GSI on top of Stock ROM.
get rid of SU.which came with "bvS" or "bgS" Variant.(option if you want Magisk)
Step to update GSI without lost your data include magisk.
Step to Recovery back to the First Boot with Magisk (hidden).
<<Additional for PHH AOSP>>
Add Adaptive Auto-brightness for T225 (magisk module) here
Add Face Unlock. here
<< Additional for Stock SAM A13 based>>
Add Restore Samsung Knox features.(had lost from unlocked and root)
Add Advanced Setup New LeOS
ADD DUAL BOOT WITH Vega Bobo DSU Sideloader. (SAM Stock A13 Base) Example here:
**FastbootD Help.
fastboot commands
fastboot commands. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
--info--
Sam did not provided " fastboot mode" for all devices. only "Odin flashing tool".
What is the FasdtbootD?
What is FastbootD? How to Boot to FastbootD Mode
In this tutorial, we will explain you what is FastbootD Mode in Android, how to boot to FastbootD Mode and how to exit this mode.
www.droidwin.com
*Limitation of FastbootD
FastbootD not the same as regular "fastboot", impossible to use fastbootd without " Dynamic partition. etc., dynamic partitions are automatically created, resized, or deleted as needed.
*FastbootD has access in logical partition like Super Partition.
( have odm +product+vendor+system partition inside) , Because dynamic partitions are implemented in userspace, partitions needed by the bootloader can't be made dynamic. For example, boot, dtbo, and vbmeta are read by the bootloader, and so must remain as physical partitions.
then
You can't uses by fastbootD performed
Code:
fastboot --disable-verity flash vbmata vbmeta.img
✓ Not enough space to resize partition solution
Solution:
Removing stock system_ext and/or product from fastbootd is enough, like so:
***Don't uses this command
"fastboot delete-logical-partition product"
why ?
the product partition, with around 1.3GB in size isn’t even required by the GSIs.
then you can delete data on product partition.
*(Didn't delete product partition itself but deletes only data inside this partition , then android will auto-resize product'spartition.)
Do this.
Code:
adb reboot fastboot
Code:
fastboot erase product
set the size of the product partition to 0
Code:
fastboot resize-logical-partition product 0x0
To verify if the partition size has become 0.
Code:
fastboot getvar all
If one of the lines shows the below code, then the process is a success.
Code:
(bootloader) partition-size:product:0x0
{
"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"
}
or
>fastboot erase system_ext
>fastboot resize-logical-partition system_ext 0x0
---End Info--
Resource:
Basic knownledge.
my customAP tutorial.
** When using FastbootD you should knows
Set of fastbootd command.
-content-​
Flashing Any GSIs​Using Fastboot without CustomAP 》Save your time.​Example_use AOSP A13 from phhusson TrebleDroid GSI.
Complete Cycle From Fastboot Flashing >>>ROOT (Magisk,SU)>>Customized UI >>Update without Lost Data and Magisk.​Requirement:
-Unlocked BootLoader
-(Recommend) Stock Firmware Update to A13 such as
"SM-T225XXU1CWA2" etc.,
Why? Used Android 13 GSIs.
1. MTP works
2. Offline Charging works
3. Google Assistant can call for you. (Ok Google call xxx) Stock A13 didn't do it.
etc.,
>Step to install Stock ROM together with Fastboot ability at the same time.
(clean install with stock firmware)
Extract AP Framework File for "recovery.img.lz4" and patch to add FastbootD ability. [ Download Attach file ] or patch by yourself here https://github.com/Johx22/Patch-Recovery.
Flash Stock Framework File with odin. (AP , BL, CP, CSC_not_home) + Magisk patch-boot & vbmeta & patch-recovery at (USERDATA Slot) ( include 3 patch-files to one tar file) [ Download Attach file ] -After reboot must connects internet and set "Developer options = enable OEM unlocking + USB debugging"
(Computer) Download and extract Platform tools to C:\ https://developer.android.com/studio/releases/platform-tools.
(Computer) Download and install Fastboot interface Driver. https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/
Note:
1.you can dirty flash patched fastbootD-recovery at AP slot. When you had any firmware or gsi installed.
2.Howto magisk-patch (boot.img.lz4 + vbmeta.img.lz4). in General Section.
>Step to flash GSI on top of Stock ROM
Set of Command to install GSIs on top of Stock Firmware.
-Connect device with USB cable to Computer.
-Download your GSIs.
-Extract "GSI.img file into platform tools directory.
-open CMD inside the platform-tools folder and then type in the below command
** Check device was already connected with computer.
*** Check bootloader version (patched) is the same as your device's firmware.
0.
Code:
adb devices
1.
Code:
adb reboot fastboot
-Device will turn display into FastbootD mode
2.
Code:
fastboot erase system
option: if you founded ‘Not enough space to resize partition’) error.
Code:
fastboot delete-logical-partition product
3.
Code:
fastboot flash system gsi-filename.img
4. FastootD (pic below)​Select "Enter recovery menu"
5.Recovery (pic below)
Select "wipe data/factory reset" menu
6. Recovery (pic above)
Select "reboot system now" menu
​>>Finished " Flashing with FastbootD"<<​
After installation.
- This variant was included with " PHH-SU".
>Step get rid of SU.(option if you want Magisk) (bvS or bgS variant)
adb shell Enter
su Enter
chmod +x /system/bin/phh-securize.sh Enter
/system/bin/phh-securize.sh Enter
* Device will auto reboot.
After this Magisk icon will show up.
Click Magisk icon to continue setup additional files and reboot.
-----------------------------------------------------------------​
*Step to update GSI without lost your data include magisk.
*** (Recommended: use Magisk-Gapps, if you don't want to re-process install gapps again.)
Disable all magisk modules. (if you used another Launcher or Port it from another GSI , pleases uninstall it first.)
Flash New-Update-GSI with FastbootD
Code:
fastboot flash system new-gsi.IMG
then REBOOT System (No factory reset or wipe data)
Code:
fastboot reboot
After get rid of SU , magisk will show up.
get rid of SU
Code:
adb shell
Code:
su
Code:
chmod +x /system/bin/phh-securize.sh
Code:
/system/bin/phh-securize.sh
Note: After this magisk will works again. (with all modules you had installed .)
===End of Update Version info===
Scripts by phhusson to automatically build/CI/Release TrebleDroid GSI
more than 2 times per month
Then I write this easy additional way to update without lost your data..
​>Step to Recovery back toThe First Boot with Magisk (hidden installed).
​1.Run Factory Reset From Recovery by press and hold (Power+ Vol down)
2. Connect internet and enable Developer options.
3. Enable OEM unlocking & USB debugging.
4. Reboot after that Magisk setting icon will show up again.
--End update--
Happy Chinese New Year!​General Section
** Compared 2 projects
** Restore Samsung Knox features.​
✓ How to create Magisk patch for boot.img + vbmeta.img
extract (vbmeta.img.lz4 + boot.img.lz4) from your AP Stock
create compress one file xxx .tar with 7zip
move (vbmeta.img.lz4 + boot.img.lz4).tar (xxx.tar) to tab a7 lite
install magisk.apk on you tab a7 lite
patch the tar file. (with magisk manager)
result magisk-patch file at Tab a7 :-Download folder.
✓ Howto install fastboot driver.
How to Install Fastboot Drivers in Windows 11
In this comprehensive tutorial, we will show you the detailed steps to install the Fastboot Drivers onto your Windows 11 PC
www.droidwin.com
✓ [Add pre-patch-recovery-FastbootD]
*** S2 = can't downgrade (Android version) even firmware version.
SM-T220 A13SM-T225 A13SM-T 227U A13SM-T 225N A13T220XXS2CWA7T225XXS2CWA8T227UVLU3CVLAT225NKOU1CWA3T220XXU1CWA2T225XXS2CWA6T220XXU1CWA1T225XXU1CWA2T220XXU1CVL7T225XXU1CVL6T220XXU1CVL5T225XXU1CVL5T220XXS2CWA8T225XXU2CWB3
✓ Howto install "adb &fastboot" on PC
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
You should also replace your adb with the latest binaries by Google.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download the platform tools for windows zip file. Find out where your current adb.exe file is located. Extract the zip into that location, overwrite the old file(s).
Note: Don't delete any files from platform-tools
>>>>>>>>>>>>>>
√ Download:
Where are New AOSP A13 official?
Releases · TrebleDroid/treble_experimentations
Scripts to automatically build/CI/Release TrebleDroid GSI - TrebleDroid/treble_experimentations
github.com
Note: (Read/Write System should uses variant "vndklite".)
✓Changes PHH-SU to Magisk.
- Connect device with your computer. run below command.
Code:
adb shell Enter
su Enter
chmod +x /system/bin/phh-securize.sh Enter
/system/bin/phh-securize.sh Enter
May be didn't found phh-securize.sh only uses root file manager deleted "/system/xbin/su"
√ You can install "GAPPS" by adb shell or by Magisk-Gapps module.
(Cause we didn't have TWRP, but don't worry about TWRP.)
*install Bromite Systemwebview
*Vega Bobo DSU Sideloader (Root mode with magisk)
*this firmware can't downgrade.**S2**​T225XXS2CWA6 , it will no longer be possible to roll back even to the previous firmware .
( A13"SM-T225XXU1CWA2)
* Add some T220 FastbootD -Recovery-patch
Reserved:
Option tools for customize your AOSP GSI.
Install Gapps modules with Magisk. ( For Android 13)​DOWNLOAD: https://litegapps.site/index.html
CLICK NAME FOR DOWNLOAD
1. [MAGISK]LiteGapps_Nano_arm64_13.0_v2.8_official.zip (Base)
2. GoogleSearch_LiteGapps_Addon_arm64_13.0.zip. (add-on)
3. GoogleAssistant_LiteGapps_Addon_arm64_13.0.zip. (add-on)
Note: you can add add-on mod from here.
STEP. ( with magisk manager )
Flash 1 and Reboot
Flash 2 and Reboot
Flash 3 and Reboot
How to configure Google Assistant . ( For make a call )
-Set Default Digital Assistant.
Open Setting and Search with keyword " digital assistant or assistant"
-Configure OK Google.
Open Setting 》Google 》Setting for Google apps 》Search Assistant & Voice 》 Google Assistant 》Hey Google & Voice match
ENABLE Hey Google.
tom.android said:
You can install "GAPPS" by adb shell .
Click to expand...
Click to collapse
Where can I download a compatible package and what command besides adb shell do I have to run in order to install?
nirogu325 said:
Where can I download a compatible package and what command besides adb shell do I have to run in order to install?
Click to expand...
Click to collapse
readme inside archrive.
tom.android said:
readme inside archrive.
Click to expand...
Click to collapse
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
nirogu325 said:
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
Click to expand...
Click to collapse
nirogu325 said:
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
Click to expand...
Click to collapse
1. install root explorer app. (such as Mixplorer)
2. create directory "gapps" or anyname at /data
such as /data/gapps
3. extract archrive " TitaTheGapps.zip" to dir from 2
4. open terminal adb shell ----then su then
cd /data/gapps/tita
chmod +x ./installer.sh
5. add more space for new gapps by delete some unuseful from "/system/system_ext/apex"
Del "android.vndk.v.28,29,30,32 keep only v31
6. run script---> sh ./installer.sh
note you can use command "mount -o rw,remount /system" or used root explorer do it. (changes RO to RW) before mod system.
nirogu325 said:
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
Click to expand...
Click to collapse
Here is what I did to install GApps on AOSP A13:
Get TheGappsInstaller-Tita archive here: https://github.com/ChonDoit/TheGappsInstaller/releases/tag/Tita (specifically: TitaTheGapps_Terminal_20221225.tar.xz)
Extract the tar archive from the tar.xz file
Follow instructions below (credits: ozmage)
adb push TitaTheGapps_Terminal_20221225.tar /sdcard/Download
adb root
adb shell
cd /data
mkdir GAPPS
mv /sdcard/Download/TitaTheGapps_Terminal_20221225.tar GAPPS
cd GAPPS
tar xvpf TitaTheGapps_Terminal_20221225.tar
cd TitaTheGapps_Terminal_20221225
chmod a+x ./installer.sh
sh ./installer.sh
tom.android said:
1. install root explorer app. (such as Mixplorer)
2. create directory "gapps" or anyname at /data
such as /data/gapps
3. extract archrive " TitaTheGapps.zip" to dir from 2
Click to expand...
Click to collapse
dapr0b said:
Here is what I did to install GApps on AOSP A13:
Get TheGappsInstaller-Tita archive here: https://github.com/ChonDoit/TheGappsInstaller/releases/tag/Tita (specifically: TitaTheGapps_Terminal_20221225.tar.xz)
*instructions*
Click to expand...
Click to collapse
Thank you both, THAT is real support.
Update: Howto update GSI without lost your data.
Update.
Flashing Any GSIs​Using Fastboot without CustomAP any longer.​
tom.android said:
Update.​Flashing Any GSIs​Using Fastboot without CustomAP any longer.​
Click to expand...
Click to collapse
Thank you.
I have one question though.
My tab is already updated to SM-T225XXU1CWA2. In the firs step, can I just simply flash with ODIN your attached fastbootd-recovery.tar in AP slot and the 3-in-1.tar in USERDATA slot without including the stock framework file (AP, BL, CP, CSC)?
jtrakx said:
Thank you.
I have one question though.
My tab is already updated to SM-T225XXU1CWA2. In the firs step, can I just simply flash with ODIN your attached fastbootd-recovery.tar in AP slot and the 3-in-1.tar in USERDATA slot without including the stock framework file (AP, BL, CP, CSC)?
Click to expand...
Click to collapse
1. flash only 3in1.tar at AP slot. (magisk 25.2 + vbmeta + recovery-patch)
-install gsi
2. remove SU by
adb shell Enter
su Enter
bra bra bra
look at my tutorial
tom.android said:
1. flash only 3in1.tar at AP slot. (magisk 25.2 + vbmeta + recovery-patch)
2. remove SU by
adb shell Enter
su Enter
bra bra bra
look at my tutorial
Click to expand...
Click to collapse
Thank you. That's a big help.
update iconify v6.0 (extract zip file run iconify.apk ) or update from app.
Iconify • Customize Boring Android UI
Updated to v6.0.0
What's new?
• Custom battery color
• Semi Transparent Brightness bar style
• Semi Transparent QS tile style
• Semi Transparent Notification style
• 5 styles of volume panel
• Improved UI roundness
XPosed Menu: (LSPosed recommended)
• Transparent Qs Panel (Supports more rom)
• Window Level Blur and Force blur enabler for unsupported ROMs
• Vertical QS tiles
• Custom header image (GIF supported)
• Custom header clocks
• Custom lockscreen clocks (custom font supported)
• Clock and status icons background chip
Full Changelog: Click Here
Teamfly Launcher (Didn't test)
TeamFiles Launcher
A launcher which aims to provide stability, speed & customizationMore info at github.com/TeamFiles/TeamFiles-LauncherJoin t.me/loopprojects to get more updates!
store.kde.org
May be compatible with quick switch of OneUI 5.
I also have a question, is this only for SM-T225XXU1CWA2 only ? or T220 can do this too . I have T220 XAR us version android 13 gsi pixel Experience plus with magisk. I want to install fastbootD and install gsi without custom AP.. do I use this guide?
abc1054 said:
I also have a question, is this only for SM-T225XXU1CWA2 only ? or T220 can do this too . I have T220 XAR us version android 13 gsi pixel Experience plus with magisk. I want to install fastbootD and install gsi without custom AP.. do I use this guide?
Click to expand...
Click to collapse
yes u can , extract AP file>>recovery.img.lz4. boot.img.lz4. vbmeta.img.lz4. upload here if you can't patch.
Can you explain how to patch it. Thanks
abc1054 said:
Can you explain how to patch it. Thanks
Click to expand...
Click to collapse
1.boot.IMG.lz4. 2. vbmeta.IMG.lz4. patch with magisk
2.recovery.IMG.lz4. patch follow with https://github.com/Johx22/Patch-Recovery
tom.android said:
yes u can , extract AP file>>recovery.img.lz4. boot.img.lz4. vbmeta.img.lz4. upload here if you can't patch.
Click to expand...
Click to collapse
Here is my files

Categories

Resources