22
TCL A509DL NO FASTBOOT-ABILITY??
source link: https://forum.xda-developers.com/t/tcl-a509dl-no-fastboot-ability.4356737/page-5#post-87906273
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Top Liked Posts
Success
Orange State magisk installed. Want to clarify the following:
Edit: Remove entire app, not just the icon from the home page.
02_magisk* is mtkclient "write partition" tab set to boot.bin?
Edit: use the write partition tab - not the flash tools tab.
Your guide lpmake command references an Andy Yan's 18.1 build (Android 11) which ran. Your mega.nz has a vanilla Lineage 18.1 as a "no-issues" rom. For some of Phh rom's there are mediatek options that need to be enabled in treble settings.
Realme C2 (mediatek P22) w/ Phh GSI
I'd like to work toward a debloated phone running degoogled, open source apps (Bromite, Bromite system webview, K-9 Mail etc). Would you recommend a Vanilla version and sideloading the apps or use an *.img with the apps built in? An example is Phh floss apps:
Phh android 12.1 releases
Last question.; Treble check indicated my TCL A30 was vndk compatible. Is there a reason not to try a vndklite image?
Edit: The vndklite image is working well.
Orange State magisk installed. Want to clarify the following:
Removing Magisk with the generic icon is not just removing the icon but the entire app?10) Launch the Magisk, it will prompt to download. Accept and let it download and install. Once installed, there will be an app called "Alpha" installed. You can now remove the Magisk app with the generic icon.
11) At this point, go ahead and launch MTK Client and reboot again. We are going to flash the 02_magisk* boot img now. This enabled Magisk with root. Once you have flashed the 02 image, disconnect and close MTKClient. Reboot phone and wait for it to load up.
Edit: Remove entire app, not just the icon from the home page.
02_magisk* is mtkclient "write partition" tab set to boot.bin?
Edit: use the write partition tab - not the flash tools tab.
Your guide lpmake command references an Andy Yan's 18.1 build (Android 11) which ran. Your mega.nz has a vanilla Lineage 18.1 as a "no-issues" rom. For some of Phh rom's there are mediatek options that need to be enabled in treble settings.
Realme C2 (mediatek P22) w/ Phh GSI
I'd like to work toward a debloated phone running degoogled, open source apps (Bromite, Bromite system webview, K-9 Mail etc). Would you recommend a Vanilla version and sideloading the apps or use an *.img with the apps built in? An example is Phh floss apps:
Phh android 12.1 releases
Last question.; Treble check indicated my TCL A30 was vndk compatible. Is there a reason not to try a vndklite image?
Edit: The vndklite image is working well.
Thanks to heavy lifting by @malfuncion , I can report a successful Android 12.1 arm64 a/b vanilla, vndklite install from Phh release 416.
I chose this image because Phh had reported a number of Mediatek fixes/patches earlier this year and I'm not sure they ware backported to Android 11. The older webview shell cannot be uninstalled but I was able to use bromite, after sideloading it, for my default system webview..
Wireless, sim, brightness, audio work and I was able to browse to f-droid.org. Using systemwebview v95, download requests showed packets on router but nothing showed up in the Downloads folder. Will try adb sideloading work-around and report back. adb install * worked great for Bromite, Bromite system webview and f-droid. I installed the rest of the applications from f-droid.
I don't have cloud storage but will provide my linsuper.img via email. Private message me w/ your address.
I chose this image because Phh had reported a number of Mediatek fixes/patches earlier this year and I'm not sure they ware backported to Android 11. The older webview shell cannot be uninstalled but I was able to use bromite, after sideloading it, for my default system webview..
Wireless, sim, brightness, audio work and I was able to browse to f-droid.org. Using systemwebview v95, download requests showed packets on router but nothing showed up in the Downloads folder. Will try adb sideloading work-around and report back. adb install * worked great for Bromite, Bromite system webview and f-droid. I installed the rest of the applications from f-droid.
I don't have cloud storage but will provide my linsuper.img via email. Private message me w/ your address.
A summary of a successful flash on a TCL A30:
Needed Software tools:
1. Android Platform tools with adb.
Platform Tools - Upstream Android
Android tools - Arch Linux
2. @malfunction zip file
3. A recent version of mtkclient. Note that in Arch Linux the version of mtkclient (1.52.1) uses an older command syntax to unlock/lock the bootloader. mtkclient-git has the newer syntax and numerous fixes and was used. The Arch linux install does not provide a mtk_gui.
AUR mtkclient-git
It is easier with a _gui but I will provide copy/paste commands for command line syntax. Executing the mtk command and then connecting the powered-off phone to usb consistently established brom mode and executed the command. Once connected in brom mode, additional mtk commands can be run until the instructions call for a phone reboot
Process.
1. Make a backup dump of all partitions:
Note that in Arch linux with a system mtkclient-git you do not need to specify python in the command. "out" is the output directory.
With Arch Linux system wide install, drop [python] on all subsequent commands.
For example the previous command would be
You should see these files:
2. Unlock the bootloader
3. Erase metadata,userdata,md_udc
4. Overwrite all Verified Boot (vbmeta) with the blank vbmeta
5. Overwrite boot.bin with the first Magisk patched boot file
6. Disconnect usb to the phone an reboot. The phone will have no configuration and you essentially need to establish a wifi connection. Once the phone is online, long press the Magisk icon and enable the Magisk app to install additional applications. Relaunch Magisk and follow the prompts to install "Alpha" version of Magisk. Reboot the phone and then power it off.
7. Overwrite the 01_magisk patched boot.bin with 02_magisk_patched-25205_yIaU6.bin
disconnect usb and reboot the phone.
8. Launch "Alpha". It now alerts you that a new version of Magisk is available and asks you to install it. It is easiest to not update. If you want to update later, you will need the factory boot.bin on /sdcard/Download and follow the Magisk Install instuctions:
9. Unpack your super.bin, delete the product and system.bin's. Copy your chosen gsi into the unpacked super.bin and repack it. The instructions are described in this post:
XDA post 87742419
I did not load the factory boot image although it would have been helpful to have in storage (Downloads or SDcard for subsequent patching by Magisk. Do not relock the bootloaderj; you will get a "Red State" on boot.
@malfunction provides a tested repacked super.bin with Cherish Android 11 on his download site. I have two Phh GSI repacks that have been tested but have no download site. Both *super.bins are under 6GB.
10. Erase metadata, md_udc, userdata and write the repacked super.bin over the phones super
11. Install your apps. Initially, using F-Droid, some of the apks did not fully function. Specifically Geometric weather widgets were not available. Instead, download your apks directly from the F-Droid site, and use
I specifically tested these apps:
Needed Software tools:
1. Android Platform tools with adb.
Platform Tools - Upstream Android
Android tools - Arch Linux
2. @malfunction zip file
3. A recent version of mtkclient. Note that in Arch Linux the version of mtkclient (1.52.1) uses an older command syntax to unlock/lock the bootloader. mtkclient-git has the newer syntax and numerous fixes and was used. The Arch linux install does not provide a mtk_gui.
AUR mtkclient-git
It is easier with a _gui but I will provide copy/paste commands for command line syntax. Executing the mtk command and then connecting the powered-off phone to usb consistently established brom mode and executed the command. Once connected in brom mode, additional mtk commands can be run until the instructions call for a phone reboot
Process.
1. Make a backup dump of all partitions:
Note that in Arch linux with a system mtkclient-git you do not need to specify python in the command. "out" is the output directory.
Code:
[python] mtk rl "out"
For example the previous command would be
Code:
mtk rl "out"
Code:
boot.bin lk2.bin otp.bin spmfw.bin
boot_para.bin lk.bin para.bin sspm_1.bin
cache.bin logo.bin persist.bin sspm_2.bin
dtbo.bin logs preloader_bangkok_uscc.bin super.bin
efuse.bin md1img.bin proinfo.bin swversion.bin
expdb.bin md_udc.bin protect1.bin tee1.bin
flashinfo.bin metadata.bin protect2.bin tee2.bin
frp.bin nvcfg.bin recovery.bin userdata.bin
gpt_backup.bin nvdata.bin scp1.bin vbmeta.bin
gpt.bin nvram.bin scp2.bin vbmeta_system.bin
gz1.bin oembin.bin sec1.bin vbmeta_vendor.bin
gz2.bin oempersist.bin seccfg.bin vendor_boot.bin
Code:
[python] mtk da seccfg unlock
Code:
[python] mtk e metadata,userdata,md_udc
Code:
[python] mtk w vbmeta vbmeta.bin
[python] mtk w vbmeta_system vbmeta.bin
[python] mtk w vbmeta_vendor vbmeta.bin
Code:
[python] mtk w boot 01_magisk_patch_boot.bin
7. Overwrite the 01_magisk patched boot.bin with 02_magisk_patched-25205_yIaU6.bin
Code:
[python] mtk w boot 02_magisk_patched-25205_yIaU6.bin
8. Launch "Alpha". It now alerts you that a new version of Magisk is available and asks you to install it. It is easiest to not update. If you want to update later, you will need the factory boot.bin on /sdcard/Download and follow the Magisk Install instuctions:
XDA post 87742419
I did not load the factory boot image although it would have been helpful to have in storage (Downloads or SDcard for subsequent patching by Magisk. Do not relock the bootloaderj; you will get a "Red State" on boot.
@malfunction provides a tested repacked super.bin with Cherish Android 11 on his download site. I have two Phh GSI repacks that have been tested but have no download site. Both *super.bins are under 6GB.
10. Erase metadata, md_udc, userdata and write the repacked super.bin over the phones super
Code:
[python] mtk e metadata, md_udc, userdata
[python] mtk w super linsuper.bin
Code:
adb install
- Bromite
- Bromite System webview
- FairEmail
- Simple Launcher
- Geometric Weather
- NewPipe
- Organic Maps
- Barcode Scanner
- Termux
- Wikipedia
GPL'd source for TCL5102 just released
The [tgz] link at the end of the commit line is AOSP 4.19-stable source:
https://android.googlesource.com/kernel/common/+/refs/heads/android-4.19-stable
My approach will be
The [tgz] link at the end of the commit line is AOSP 4.19-stable source:
https://android.googlesource.com/kernel/common/+/refs/heads/android-4.19-stable
My approach will be
- Setup my Arch Linux build box for android kernel compilation
- Build a generic aarch64 gki using Google's config file
- Import TCL config build into Google kernel tree and see what does not configure
- Resolve missing configuration - hopefully by staying in Google source tree.
- Be mindful of propriatary drivers and firmware. Will choose open source drivers and firmware over propritary drivers if possible
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK