How To Guide ( 2023).Using FastbootD .
- Thread starter tom.android
- Start date
Test FastbootD with CatalystOS A13.GSI
-Not supported exFAT micro-sdcard.
-Home Launcher very old.(from ArrowOS)
-Not supported exFAT micro-sdcard.
-Home Launcher very old.(from ArrowOS)
Last edited:
Test FastbootD with PixelExtended A13.GSI
READ/WRITE SYSTEM
same Launcher as before.
READ/WRITE SYSTEM
same Launcher as before.
Last edited:
Test FastbootD RiceDroidOS A13 v10.1
update 31-01-2023
>adb reboot fastboot
>fastboot erase system
>fastboot flash system riceDroidOSS-13_arm64-bgN-slim-lite.img
option: if you founded ‘Not enough space to resize partition’) error.
>fastboot delete-logical-partition product
and rerun fastboot flash system xxx again.
>fastboot -w
-Enter Recovery
-Wipe data/Factory reset
-Reboot system
-Not supported exFAT
-Launcher same functions as SparkOS
+5 Stars GSI
+waiting for supported exFAT microSD-Card.
( Don't format your sdcard it is not support .)
update 31-01-2023
>adb reboot fastboot
>fastboot erase system
>fastboot flash system riceDroidOSS-13_arm64-bgN-slim-lite.img
option: if you founded ‘Not enough space to resize partition’) error.
>fastboot delete-logical-partition product
and rerun fastboot flash system xxx again.
>fastboot -w
-Enter Recovery
-Wipe data/Factory reset
-Reboot system
-Not supported exFAT
-Launcher same functions as SparkOS
+5 Stars GSI
+waiting for supported exFAT microSD-Card.
( Don't format your sdcard it is not support .)
Last edited:
I tried to put PixelExtended A13.GSI with your instructions but it failed. System resize. I put back my other pixel with fastboot and works.
try this command before fastboot flash system xxxx.
fastboot delete-logical-partition product
if not success please return to Stock A13 .
Test FastbootD project elixirs update 20230130
>adb reboot fastboot
>fastboot erase system
>fastboot flash system ProjectElixir_3.5_gsi-13.0-20230130-2235-OFFICIAL.img.
option: if you founded ‘Not enough space to resize partition’) error.
>fastboot delete-logical-partition product
rerun fastboot flash system xxxx. again.
>fastboot -w
-Enter Recovery
-Wipe data/Factory reset
-Reboot system
Nothing new.
>adb reboot fastboot
>fastboot erase system
>fastboot flash system ProjectElixir_3.5_gsi-13.0-20230130-2235-OFFICIAL.img.
option: if you founded ‘Not enough space to resize partition’) error.
>fastboot delete-logical-partition product
rerun fastboot flash system xxxx. again.
>fastboot -w
-Enter Recovery
-Wipe data/Factory reset
-Reboot system
Nothing new.
Last edited:
**new android_13.0.0_r24 ci-20230131( AOSP.A13.PHH.TrebleDroid)
How to update version.
0. Download and extract archrive to platform-tools folder.
1. Disable all magisk modules.
(if you used another Launcher or Port it from another GSI , pleases uninstall it first.)
Also disable magisk.gapps module.
-reboot
adb devices
adb reboot fastboot
FastbootD screen showup
2. Flash new GSI with FastbootD
*if error Not Enough Space to resize partition
"fastboot delete-logical-partition product"
rerun
3. Reboot system without wipe data or factory reset.
4. Get rid of SU
Device will reboot ifself.
5. After this magisk will works again. (icon showup)(no error Unsupported Magisk Version)
- enable magisk modules back.
- reboot
![IMG_20230131_210609_(1)[1].jpg](https://forum.xda-developers.com/attachments/img_20230131_210609_-1-1-jpg.5824433/ "IMG_20230131_210609_(1)[1].jpg")
5 stars AOSP GSI quickly updating.
How to update version.
0. Download and extract archrive to platform-tools folder.
1. Disable all magisk modules.
(if you used another Launcher or Port it from another GSI , pleases uninstall it first.)
Also disable magisk.gapps module.
-reboot
adb devices
adb reboot fastboot
FastbootD screen showup
2. Flash new GSI with FastbootD
Code:
fastboot flash system system-td-arm64-ab-vndklite-vanilla.img*if error Not Enough Space to resize partition
"fastboot delete-logical-partition product"
rerun
Code:
fastboot flash system system-td-arm64-ab-vndklite-vanilla.img3. Reboot system without wipe data or factory reset.
Code:
fastboot reboot4. Get rid of SU
Code:
adb shell
su 0
chmod +x /system/bin/phh-securize.sh
/system/bin/phh-securize.sh5. After this magisk will works again. (icon showup)(no error Unsupported Magisk Version)
- enable magisk modules back.
- reboot
5 stars AOSP GSI quickly updating.
Last edited:
update-Feb 1-2023
Download-overlay Adaptive brigness for SM-T225 (A13).(Magisk module) (Attachment)
Adaptive brightness is an Android feature that adjusts your display's brightness levels based on the surrounding lighting and your preferences.
Don't forgot to enable Adaptive Brightness. (Show up after your flash my overlay magisk module)
Note: T220 not test
You can check this by covering the top ear piece portion of the tab. if your sensor works perfectly screen brightness will get reduced.
OPTION: (if you feel that my overlay had set too low minimum brightness screen.)
Display Brightness Limit (From AOSPmod)
Show Brightness Slider
Download-overlay Adaptive brigness for SM-T225 (A13).(Magisk module) (Attachment)
Adaptive brightness is an Android feature that adjusts your display's brightness levels based on the surrounding lighting and your preferences.
Don't forgot to enable Adaptive Brightness. (Show up after your flash my overlay magisk module)
Note: T220 not test
You can check this by covering the top ear piece portion of the tab. if your sensor works perfectly screen brightness will get reduced.
OPTION: (if you feel that my overlay had set too low minimum brightness screen.)
Display Brightness Limit (From AOSPmod)
Show Brightness Slider
Last edited:
i got it working , had to turn on in magisk sharedUID shell. but still couldnt get /system/bin/phh-securize.sh it says that it doesnt exist.
then no su (if you don't update aosp gsi again.) no need to clean su again ... install magisk.apk if you can't saw magisk icon
but it has a problem , it says its in abnormal state, A SU binary not from Magisk has been dected. please remove any competing root solution
Are there su in system/xbin? or you fortgot to give a permission
chmod +x /system/bin/phh-securize.sh
Sorry I forgot it in tutorial.
Last edited:
OK give it pemission before.
chmod +x /system/bin/phh-securize.sh
/system/bin/phh-securize.sh
there is no file ..so i dont get itOK give it pemission before.
chmod +x /system/bin/phh-securize.sh
/system/bin/phh-securize.sh
its not giving me errors now, so magisk is working, long as i turn on the sharedUID shell in superuser
thanks Tom for your guidance..
delete with root file manager.
system/xbin/su
system/bin/phh-su
system/etc/init/su.rc
system/bin/phh-securize.sh
there is no system/bin/phh-su ,or system/etc/init/su.rc,system/bin/phh-securize.sh
i deleted the xbin su , so no more pop up saying abnormal su, its working good, thanks you again Tom
Last edited by a moderator:
Top Liked Posts
-
There are no posts matching your filters.
-
1
Here your patched file. (Extract the tar file and flash At AP Slot with odin) -
4This step by step tutorial is all about*Disable AVB verification when uses "fastbootD' here.
[A13-GSI] DerpFest (July) +Introduction with how to flash a GSI handbook.(fastbootD) p1-p9
# New derpfest here...
forum.xda-developers.com
☆☆☆ 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:
--info--
Sam did not provided " fastboot mode" for all devices. only "Odin flashing tool".
What is the FasdtbootD?
*Limitation of FastbootDWhat is FastbootD? How to Boot to FastbootD Mode
In this tutorial, we will explain you what is...
www.droidwin.com
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
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 GSIsUsing Fastboot without CustomAP 》Save your time.Example_use AOSP A13 from phhusson TrebleDroid GSI.Requirement:
Complete Cycle From Fastboot Flashing >>>ROOT (Magisk,SU)>>Customized UI >>Update without Lost Data and Magisk.
-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/
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 ROMSelect "Enter recovery menu"
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.-Device will turn display into FastbootD modeCode:adb reboot fastboot
2.option: if you founded ‘Not enough space to resize partition’) error.Code:fastboot erase system
3.Code:fastboot delete-logical-partition product4. FastootD (pic below)Code:fastboot flash system gsi-filename.img
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 shellCode:suCode:chmod +x /system/bin/phh-securize.shNote: After this magisk will works again. (with all modules you had installed .)Code:/system/bin/phh-securize.sh
>Step to Recovery back toThe First Boot with Magisk (hidden 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..
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.
General Section
--End update--
Happy Chinese New Year!
** 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.
How to Install Fastboot Drivers in Windows 11
In this comprehensive tutorial, we will show...
www.droidwin.com
✓ [Add pre-patch-recovery-FastbootD]
*** S2 = can't downgrade (Android version) even firmware version.
SM-T220 A13 SM-T225 A13 SM-T 227U A13 SM-T 225N A13 T220XXS2CWA7 T225XXS2CWA8 T227UVLU3CVLA T225NKOU1CWA3 T220XXU1CWA2 T225XXS2CWA6 T220XXU1CWA1 T225XXU1CWA2 T220XXU1CVL7 T225XXU1CVL6 T220XXU1CVL5 T225XXU1CVL5 T220XXS2CWA8 T225XXU2CWB3
✓ Howto install "adb &fastboot" on PC
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing...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...
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?
Note: (Read/Write System should uses variant "vndklite".)Releases · TrebleDroid/treble_experimentations
Scripts to automatically build/CI/Release...
github.com
✓Changes PHH-SU to Magisk.
- Connect device with your computer. run below command.
May be didn't found phh-securize.sh only uses root file manager deleted "/system/xbin/su"Code:adb shell Enter su Enter chmod +x /system/bin/phh-securize.sh Enter /system/bin/phh-securize.sh Enter
√ 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-patch2
SparkOS 13.5.5
Detail here
- Retuned the ui of the ls affordance icons
- Reworked the app lock implementation
- Added support for desktop mode
- Retuned seekbar design
- Made night light transition more gradual
- Improved the ripple animation
- Improved some ui animations
- Updated oos clear all button design
- Addressed some lags and issues that were caused of SparkSystemManager
- Reworked Parallel space
- Added support for toggling gms
- Reworked edge haptics
- Added support for clo boost fwk
- Updated the colors and functionality of work profiles
- Reworked the power menu implementation and added support for power Menu Styles
- Merged crowdin translation updates
- Updated SparkThemedIcons
- Updated the lock app feature
- Added support to set hotseat opacity in launcher
- Reworked the recents ui style
- More under the hood changes aimed to improve battery life and performance
The interesting new feature is support desktop mode and toggling GMS.
Waitting for GSI.
1Reserved:
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.1
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.1
Here your patched file. (Extract the tar file and flash At AP Slot with odin)
New posts
-
-
Remove the "Wi-FI debugging enabled" notification- Latest: Oswald Boelcke
