[GUIDE] Important partitions you must backup after you have the phone rooted, Stock firmware reinstallation guide at worst case - Nokia 8.3 5G (8V 5G UW) Guides, News, & Discussion

These partitions are important when you'll have to restore the phone back to normal from worst case.
Code:
elableinfo (/dev/block/sda4) - This partition contains Certification Image, may not important.
imeilock (/dev/block/sdg1) - This partition contains your device IMEI.
persist (/dev/block/sda8) - This partition contains your device PSN, MAC, Bluetooth.
oemowninfo (/dev/block/sda2) - This partition contains SKUID, exclusive info, etc.
simlock (/dev/block/sde63) - Carrier locked TA-1251 only. Mandatory to allow your phone boot if your phone isn't carrier locked.
Other Snapdragon 765G based Android phones can also refer this, although we can't guarantee it will 100% apply on your phone. DO NOT FOLLOW THIS GUIDE IF YOU ARE USING TA-1257 (NOKIA 8 V 5G UW from Verizon Wireless).
WARNING:
1. DO NOT SHARE YOUR CRITICAL PARTITION BACKUP IMAGES TO ANYONE ELSE TO PREVENT ABUSE, PLUS, SHARING THIS VIOLATES THE RULE OF XDA.
2. CRITICAL PARTITION BACKUP IMAGES FOR BOTH TA-1243 AND TA-1251 AREN'T INTERCHANGEDABLE.
Click to expand...
Click to collapse
To backup these partitions:
1. Unlock the bootloader and root your phone with Magisk.
2. Execute these commands:
Code:
adb shell mkdir /storage/emulated/0/bgt-critical/
adb shell su
(Confirm root permission on your phone - if you missed that or didn't confirm it, open Magisk app and grant it manually)
adb shell su -c dd if=/dev/block/bootdevice/by-name/imeilock of=/storage/emulated/0/bgt-critical/imeilock.img
adb shell su -c dd if=/dev/block/bootdevice/by-name/persist of=/storage/emulated/0/bgt-critical/persist.img
adb shell su -c dd if=/dev/block/bootdevice/by-name/oemowninfo of=/storage/emulated/0/bgt-critical/oemowninfo.img
adb shell su -c dd if=/dev/block/bootdevice/by-name/simlock of=/storage/emulated/0/bgt-critical/simlock.img
adb pull /storage/emulated/0/bgt-critical/
3. Save entire bgt-critical directory at safe place.
Additionally, you must do QCN backup in case you erased NVRAM at worst case.
To do that:
1. Root your phone with Magisk.
2. Execute this command on your PC with ADB shell for enabling Qualcomm Diag Port:
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,adb
3. Install QPST 2.7.496 and use QPST Software Download to backup both XQCN and QCN images, and save both of them at bgt-critical partition you have saved.

Here's how to reinstall stock firmware, in case you bricked the phone at worst situation.
Please disable automatic translation on your web browser if you can't click "CLICK TO SHOW CONTENT" button.
Click to expand...
Click to collapse
Assuming you have UFS lun0-lun6 erased, or the phone is currently at Qualcomm 900E which are considered worst situation.
1. Download following firmware, and extract it 3 times - you'll get tons of files inside.
bgt-2210-0-00WW-B01.HMDSW.7z | by Hikari Calyx for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
2. Use text editor to open rawprogram0_sparse.xml and delete the string super.img inside to save time when doing part 1 flashing.
Use text editor to open rawprogram4.xml and replace the string abl.elf into BGT-abl.elf , then save it.
3. Copy prototype ABL into the firmware directory, and make sure the filename is BGT-abl.elf .
4A. (For Windows users)
Please install QPST 2.7.496 or newer and Qualcomm USB Driver before you proceed. You'd better to erase all other incompatible drivers to increase success rate.
Once installed, please copy QSaharaServer.exe and fh_loader.exe from QPST installation directory (C:\Program Files (x86)\Qualcomm\QPST\bin by default) to firmware directory.
4B. (For macOS / Linux users)
Please install Python EDL from following website:
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
5. If your phone is currently at 900E, you must disassemble the phone by opening the back cover and make sure the motherboard is exposed.
Disconnect the battery, use a pair of tweezers to short the test point, then connect your phone to PC. Using USB 2.0 port is strongly recommended for best stability.
{
"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"
}
If you're using PC that only has USB 3.1 port you may like encounter USB port throttling issue. In this case you must buy an USB hub as workaround.
To check if your phone is properly connected:
(For Windows users)
Please open Device Manager and check if your phone is listed as Qualcomm HS-USB QDLoader 9008 / Qualcomm HS-USB Diagnostics 9008. If not you need to disconnect the phone, short the test point and connect the phone to PC again. Once it's listed you can remove the tweezer.
(For macOS / Linux users)
Please execute this command:
Code:
lsusb
and see if a device started from 05C6:9008 is listed. If yes, you can remove the tweezer and proceed to next step.
6A. (For Windows users)
Please check the COM port in Device Manager, assuming the COM port number is 8.
Open a Command Prompt or PowerShell window at directory where you have tons of firmware files extracted.
Execute this command (replace the COM port number to actual COM port number you see in Device Manager)
Code:
.\QSaharaServer -p \\.\COM8 -s 13:prog_firehose_ddr.elf
If you see a message says image uploaded successfully, you can proceed to next step.
Execute this command to upload rawprogram XML configuration:
Code:
.\fh_loader --port=\\.\COM8 --search_path=. --sendxml=rawprogram0_sparse.xml,rawprogram1.xml,rawprogram2.xml,rawprogram3.xml,rawprogram4.xml,rawprogram5.xml,rawprogram6.xml --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=UFS
Wait for image files being uploaded, now write patch XML configuration:
Code:
.\fh_loader.exe --port=\\.\COM8 --search_path=. --sendxml=patch0.xml,patch1.xml,patch2.xml,patch3.xml,patch4.xml,patch5.xml,patch6.xml --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=UFS
Once these commands are executed successfully, you can disconnect the phone, reconnect the battery and power it on.
Your phone should boot straight into Fastboot mode. If it doesn't boot the battery might be drained, recharge it a little bit before you proceed.
6B. (For macOS / Linux users)
Assuming you have Python EDL installed properly.
Open a terminal under the directory where you have firmware extracted, and execute this command:
Code:
edl qfil rawprogram0_sparse.xml,rawprogram1.xml,rawprogram2.xml,rawprogram3.xml,rawprogram4.xml,rawprogram5.xml,rawprogram6.xml patch0.xml,patch1.xml,patch2.xml,patch3.xml,patch4.xml,patch5.xml,patch6.xml /path/to/where/firmware/images/arelocated/ --memory=ufs --loader=prog_firehose_ddr.elf
Wait for image files being uploaded. If the flashing procedure is throttling, you may want to execute this command before connecting phone with test point shorted.
Once this command is executed successfully, you can disconnect the phone, reconnect the battery and power it on.
Your phone should boot straight into Fastboot mode. If it doesn't boot the battery might be drained, recharge it a little bit before you proceed.
7. Reinstall all other partitions with Fastboot command.
If you're Windows user, please DO NOT USE Minimal ADB and Fastboot, but use this instead: https://developer.android.com/studio/releases/platform-tools
Code:
fastboot flash partition:0 gpt_both0.bin
fastboot --set-active=a reboot-bootloader
fastboot flash xbl xbl.elf
fastboot flash xbl_config xbl_config.elf
fastboot flash abl abl.elf
fastboot flash tz tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash storsec storsec.mbn
fastboot flash pwinfo pwinfo.img
fastboot flash bluetooth BTFM.bin
fastboot flash modem NON-HLOS.bin
fastboot flash core_nhlos Core_NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash logfs logfs_ufs_8mb.bin
fastboot flash keymaster km4.mbn
fastboot flash featenabler featenabler.mbn
fastboot flash toolsfv tools.fv
fastboot flash metadata metadata.img
fastboot flash aop aop.mbn
fastboot flash qupfw qupv3fw.elf
fastboot flash imagefv imagefv.elf
fastboot flash uefisecapp uefi_sec.mbn
fastboot flash multiimgoem multi_image.mbn
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
By doing this will allow your phone boot as the bare minimal situation, but not ideally functional.
Next you must restore critical partitions you have backed up before.
Code:
fastboot erase fsc
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fs_image.img
fastboot flash elableinfo /path/to/bgt-critical/elableinfo.img
fastboot flash imeilock /path/to/bgt-critical/imeilock.img
fastboot flash persist /path/to/bgt-critical/persist.img
fastboot flash oemowninfo /path/to/bgt-critical/oemowninfo.img
fastboot reboot
8. Once your phone boots into normal OS, use Magisk to root your phone, and execute this command to enable Qualcomm Diag Port:
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,adb
9. (For Windows users) Use QPST Software Download to restore the QCN/XQCN image you backed up before. Eject SIM before you doing so to prevent issues.
10. (Skip if you're not using Carrier locked TA-1251) Reboot the phone into Fastboot mode and flash simlock partition:
Code:
adb reboot bootloader
fastboot flash simlock /path/to/bgt-critical/simlock.img
fastboot reboot
11. Enjoy your fully revived Nokia 8.3.

Reserved #3

Related

[TOOL] Fastboot and ADB helper v1.0

Hey there,
I've wrote a little script to make it easier to flash with fastboot for newbies and for those who are flashing very often.
Just run it, and you are able to type a number and the script will do the rest, instead of typing every command in the console.
I WILL NOT GUARANTEE THAT IT WORKS! YOU CAN BRICK YOUR DEVICE! JUST USE IT IF YOU KNOW WHAT YOURE DOING!!!
Windows only!
Functions:
-Flash with fastboot:
-boot.img
-data.img
-reovery.img
-system.img
-Erase with fastboot:
-erase boot partition
-erase recovery partition
-Reboot options
-reboot device (ADB)
-reboot device into recovery (ADB)
-reboot device into bootloader (ADB)
-reboot device with fastboot
Installation:
Simply extract the zip everywhere you want and run the "runme.bat"
Using:
Copy the boot.img/recovery.img/data.img/system.img to the 'flashhelper' folder and run the script.
To Do:
-ADB Commands (Push/Pull/Install etc.)
-Fastboot flash all
Bugs:
Tell me!
Changelog:
V1.0 - August-19-2012:
-Release
Please feel free to distribute!
This script is freeware!
I make no guarantees that it works!
Please give me feedback if it worked for you!

Unable to load modded System.img on Pixel 2 using kitchen

Is anyone successful in loading modded system.img to a system-as-root device like Pixel 2+? With the nexus 5x I use to make some changed to the build.prop and init.rc to get adb on boot/OOBE but due to the new system-on-root with the Pixel devices, I need to modify the system image. I bought the paid version of Kitchen to do just that, and I can build an image (signed and non-signed... not sure the difference, so I've tested both). Below are the steps I've used but the device always fails to load after.
boot-slot: a
Console: DISABLED
Secure Boot: yes (Production)
Device state: unlocked
"ERROR: LoadImageAndAuth Failed: Load Error"
Code:
1. Download Pixel2 8.1.0 firmware from google
2. Pull the system.img
3. Run Kitchen tool and create a new project
4. add the system.img to the project folder
5. Extract the system image (#4 Extract for new rom)
6. Give it a name: TEST
7. Which perm type would you like to use?: #4 raw_img
8. Don't make any changes yet.... testing to see if it can load
9. Go to #8, -> #7 Build Menu -> #2 build ext4 img -> #1 system -> #2 sparse -> #4 system.img
Code:
fastboot flash system_a C:\Users\username\Desktop\Pixel2_Images\system_new.img
fastboot flash system_b C:\Users\username\Desktop\Pixel2_Images\system_new.img
and/or
Code:
fastboot flash system C:\Users\username\Desktop\Pixel2_Images\system_new.img
and/or
Code:
1. rename system_new.img to system.img
2. Repack the system.img in the Pixel Firmware zip
3. Run flash-all.bat
Update 1:
I have also tried the following.
Code:
1. Boot Pixel 2 Image from firmware site
2. Reboot device into recovery mode
2. Wait till you see a Android icon with !
3. Hold Power and hit up arrow
4. Select Wipe data/factory reset
5. When it boots to OOBE, reboot to bootloader
# load the latest TWRP.img
6. fastboot boot C:\Users\username\Downloads\twrp-3.3.0-0-walleye.img
# Device will boot once to TWRP
# Select Wipe -> swipe for factory reset
7. adb push <The image i created using Kitchen> /sdcard/Download
8. select Install and select the Image
Device Boots with error "Can't load Android system. Your data may be corrupt."

How To Guide [ROM][MIUI][mojito/sunny] Xiaomi.eu ROM for Redmi Note 10

How to install Xiaomi.eu ROM for Redmi Note 10
We will release fastboot ROM versions until TWRP for mojito/sunny is released
UPDATE:
- TWRP for mojito/sunny is RELEASED
- From now, we will release RECOVERY version of ROM for install via TWRP, so this guide is obsolete
Steps to install xiaomi.eu ROM for first time from China ROM via fastboot (All your data and files on internal storage will be deleted!)
- Update Global ROM to the latest via updater app first..
- Unlock your bootloader by Mi Unlock tool https://en.miui.com/unlock/
- Download our ROM zip file xiaomi.eu_multi_HMNote10_V12.0.5.0.RKGMIXM_v12-11-fastboot.zip
- If you are on Windows: Right click on downloaded zip - Settings - Unblock zip content
{
"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"
}
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via original USB cable
- Run fastboot installation script as administrator from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_first_install_with_data_format.bat
For Linux ./linux_fastboot_first_install_with_data_format.sh
For MacOS ./macos_fastboot_first_install_with_data_format.sh
- After reboot its done (first boot may take up to 15min)
Steps to install update of xiaomi.eu ROM (All your data and files on internal storage will NOT be deleted!)
- Download our ROM zip file STABLE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_update_rom.bat
For Linux ./linux_fastboot_update_rom.sh
For MacOS ./macos_fastboot_update_rom.sh
Update guide on the video
- After reboot its done (first boot may take up to 10min)
Update via OTA:
Installation via OTA is currently not possible due to missing TWRP
Updater will notify you about new version and download it to your device for you
You have to copy it to your PC, unpack it and run fastboot_update_rom sctipt
Enjoy..
@ingbrzy Will be Xiaomi.Eu version for sweet?
got stuck at fastboot - bootloop after ran the bat file.
sweat...
redmi note 10 - sunny
Edit: managed to flash it after removed _ab in the script.
abc9999 said:
got stuck at fastboot - bootloop after ran the bat file.
sweat...
redmi note 10 - sunny
Click to expand...
Click to collapse
which ROM did you had before?
ingbrzy said:
which ROM did you had before?
Click to expand...
Click to collapse
global rom
Edit: managed to flash it after removed _ab in the script.
abc9999 said:
global rom
Edit: managed to flash it after removed _ab in the script.
Click to expand...
Click to collapse
ok.. flashing by windows or linux?
ingbrzy said:
ok.. flashing by windows or linux?
Click to expand...
Click to collapse
windows
abc9999 said:
windows
Click to expand...
Click to collapse
Did you cd to unzipped folder and execute script from there? Seems fastboot.exe wasn't used from our folder..
Shermo1208 said:
@ingbrzy Will be Xiaomi.Eu version for sweet?
Click to expand...
Click to collapse
@ingbrzy any comments about that? Thanks
Shermo1208 said:
@ingbrzy any comments about that? Thanks
Click to expand...
Click to collapse
yes..
ingbrzy said:
yes..
Click to expand...
Click to collapse
I really look forward to it, man. Didn't have a Xiaomi since the Redmi Note 2 and even back then you were there. Thanks for the effort. I still have 5 days left to be able to unlock the bootloader, so I have to wait anyway. Will sweet get a TWRP support? I don't know, if they still work on TWRP, the latest posts I saw were from end of 2020
ingbrzy said:
yes..
Click to expand...
Click to collapse
When?
abc9999 said:
global rom
Edit: managed to flash it after removed _ab in the script.
Click to expand...
Click to collapse
So please tell us your experience with the rom? Is it stable, are there any performance or lag issues with the rom?
Is network and radio working properly? Is call recording working?
ingbrzy said:
How to install Xiaomi.eu ROM for Redmi Note 10
We will release fastboot ROM versions until TWRP for mojito/sunny is released
Steps to install xiaomi.eu ROM for first time from China ROM (All your data and files on internal storage will be deleted!)
- Update Global ROM to the latest via updater app first..
- Unlock your bootloader by Mi Unlock tool https://en.miui.com/unlock/
- Download our ROM zip file xiaomi.eu_multi_HMNote10_V12.0.2.0.RKGMIXM_v12-11-fastboot.zip
- If you are on Windows: Right click on downloaded zip - Settings - Unblock zip content
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via original USB cable
- Run fastboot installation script as administrator from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_first_install_with_data_format.bat
For Linux ./linux_fastboot_first_install_with_data_format.sh
For MacOS ./macos_fastboot_first_install_with_data_format.sh
- After reboot its done (first boot may take up to 15min)
Steps to install update of xiaomi.eu ROM (All your data and files on internal storage will NOT be deleted!)
- Download our ROM zip file STABLE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_update_rom.bat
For Linux ./linux_fastboot_update_rom.sh
For MacOS ./macos_fastboot_update_rom.sh
Update guide on the video
- After reboot its done (first boot may take up to 10min)
Update via OTA:
Installation via OTA is currently not possible due to missing TWRP
Updater will notify you about new version and download it to your device for you
You have to copy it to your PC, unpack it and run fastboot_update_rom sctipt
Enjoy..
Click to expand...
Click to collapse
What about Redmi Note 10 Pro India? Will this work in that phone which has 64MP Cam and SD732G?
njaya95 said:
What about Redmi Note 10 Pro India? Will this work in that phone which has 64MP Cam and SD732G?
Click to expand...
Click to collapse
Note 10 Pro and Pro Max(india) are same and same ROMs work on those device, but Note 10 is different.
Is there a way to revert back to global MIUI after flashing the Xiaomi eu version?
ahmedwaseem said:
Is there a way to revert back to global MIUI after flashing the Xiaomi eu version?
Click to expand...
Click to collapse
https://bigota.d.miui.com/V12.0.2.0.RKGMIXM/mojito_global_images_V12.0.2.0.RKGMIXM_20210226.0000.00_11.0_global_06f2a9e26b.tgz
Use official xiaomi flash tool to flash it via fastboot.
I'm having error when flashing the fastboot file. it says "platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mojito" || echo Missmatching image and device"
my unit is sunny ( as per mi unlocker )
but there is no file specified for MOJITO or SUNNY.
thank you.
SSEFIROSU said:
I'm having error when flashing the fastboot file. it says "platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mojito" || echo Missmatching image and device"
my unit is sunny ( as per mi unlocker )
but there is no file specified for MOJITO or SUNNY.
thank you.
Click to expand...
Click to collapse
open .bat file and replace content by this code and save
Bash:
@echo off
cd %~dp0
set /p CHOICE=You are going to wipe your data and internal storage. It will delete all your files and photos stored on internal storage. Do you agree? (Y/N)
if /i "%CHOICE%" neq "y" goto END
platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *sunny" || echo Missmatching image and device
platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *sunny" || exit /B 1
platform-tools-windows\fastboot %* flash dsp images\dsp.img
platform-tools-windows\fastboot %* flash xbl_config images\xbl_config.img
platform-tools-windows\fastboot %* flash boot images\boot.img
platform-tools-windows\fastboot %* flash modem images\modem.img
platform-tools-windows\fastboot %* flash vbmeta_system images\vbmeta_system.img
platform-tools-windows\fastboot %* flash tz images\tz.img
platform-tools-windows\fastboot %* flash vbmeta images\vbmeta.img
platform-tools-windows\fastboot %* flash bluetooth images\bluetooth.img
platform-tools-windows\fastboot %* flash abl images\abl.img
platform-tools-windows\fastboot %* flash dtbo images\dtbo.img
platform-tools-windows\fastboot %* flash vendor_boot images\vendor_boot.img
platform-tools-windows\fastboot %* flash keymaster images\keymaster.img
platform-tools-windows\fastboot %* flash uefisecapp images\uefisecapp.img
platform-tools-windows\fastboot %* flash qupfw images\qupfw.img
platform-tools-windows\fastboot %* flash xbl images\xbl.img
platform-tools-windows\fastboot %* flash cmnlib images\cmnlib.img
platform-tools-windows\fastboot %* flash cmnlib64 images\cmnlib64.img
platform-tools-windows\fastboot %* flash devcfg images\devcfg.img
platform-tools-windows\fastboot %* flash hyp images\hyp.img
platform-tools-windows\fastboot %* flash imagefv images\imagefv.img
platform-tools-windows\fastboot %* flash aop images\aop.img
platform-tools-windows\fastboot %* flash cust images\cust.img
platform-tools-windows\fastboot %* flash super images\super.img
platform-tools-windows\fastboot %* set_active a
platform-tools-windows\fastboot %* erase metadata
platform-tools-windows\fastboot -w
platform-tools-windows\fastboot %* reboot
:END
thank you, after flashing it says not play protect certified. i can't access playstore to install apps.

Redmi 9 各种手机 (super.img) 自制ROM 完整教程

感谢@bynarie @AndyYan 他们两位给我了很大帮助解决了关键问题!Thank you.
第一步:
1:自备固件fastboot包,可以在互联网自行下载.
2:电脑安装虚拟机,同时下载 ubuntu桌面版系统,并在虚拟机里面安装好!并且获取root登录,设置电脑和虚拟机的文件共享问题!
(详情设置请自行百度;google)
第二步:
1:下载安卓工具包,并解压复制到ubuntu
安卓工具包 (大陆需要VPN)
2:先前下载的固件进行解压共享给ubuntu,虚拟机启动ubuntu,进入桌面后点击左侧文件- 计算机-其他位置在任意文件夹或者根目录下新建文件夹名字随意。然后将之前解压的安卓工具包放到这个文件夹里面。只需要其中几个文件和驱动其他都是不需要的。请看我的截图:
{
"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"
}
Step 3: Share the previously downloaded firmware and decompress settings to ubuntu (please google for specific settings). After starting the virtual machine ubuntu and entering the desktop, click on the file on the left-computer-other locations in any folder or the root directory, create a new folder with any name . Then put the previously unzipped Android toolkit into this folder. Only a few files and drivers are needed. Please see my screenshot:
第四步:解压修改固件.我们需要修改其中的 cust.img userdata.img super.img 前面2个img 修改都很简单 google就有详细的教程不做详说。只贴出具体的执行代码!今天重点讲 suer.img 解包和打包。
Step 4: Unzip and modify the firmware. We need to modify the cust.img userdata.img super.img. The first two img modifications are very simple. Google has a detailed tutorial that will not go into details. Only post the specific execution code! Today I will focus on unpacking and packaging suer.img.
cust.img userdata.img 代码:
Code:
1:./simg2img XXXX.img XXX.img (解包)(Unpack)
2:mount -t ext4 -o loop XXX.img ./temp (挂载前一步解包的映像文件)(Mount the image file unpacked in the previous step)
(在ubuntu中删除img镜像中的文件,会生成一个.Trash的隐藏文件夹,即回收站.必需ctrl+H将其显示并删除,否则,所有删除的软件文件,
在system.img刷进手机后仍会起作用)
(Deleting the files in the img image in ubuntu will generate a hidden folder of .Trash, which is the recycle bin. It must be displayed and deleted by ctrl+H, otherwise, all deleted software files will be swiped into the phone in system.img Will still work)
3:sudo umount temp (修改完成后卸载挂载映像)(Uninstall the mount image after the modification is completed)
4:./img2simg XXX.img XXX.img (最后再打包成之前的映像文件 替换即可)(Finally package into the previous image file and replace it)
第五步:suer.img的解包和打包
Step 5: Unpacking and packaging suer.img
1:安装小米手机驱动 开启usb调试 下载adb工具运行命令(打开adb命令一闪而过请参考 https://www.jb51.net/diannaojichu/95294.html)
Install the Xiaomi mobile phone driver, turn on the usb debugging, download the adb tool to run the command (open the adb command for a flash, please refer to https://www.jb51.net/diannaojichu/95294.html)
Code:
开始解包super.img之前,需要连接手机,电脑安装好驱动并下载adb工具包,手设置-开发者模式-打开usb调试.
code:
adb shell lpdump
(请一定不要关闭窗口或截图保存数据,打包super.img 需要里面的参数)
2:./simg2img super.img super.raw.img
3:./lpunpack --slot=0 super.raw.img (命令完成出现三个。.img文件 我们只需要对其中system.img进行修改)
(There are three .img files after the command is completed. We only need to modify the system.img)
4:mount -t ext4 -o loop system.img ./temp
(删除小米那些垃圾应用时需要去除卡米限制 我自己做的redmi9去卡米限制。其他机型自行google 关键词 去除卡米限制。 替换路径system/framework/services.jar 替换后需要设置权限,具体可以选择没有替换的文件右键 权限 对比 设置一模一样即可。下载地址:https://wwa.lanzous.com/iFA4Lmze3va)
(When deleting those rubbish applications of Xiaomi, you need to remove the Kami restriction. I made my own redmi9 to remove the Kami restriction. Other models remove the Kami restriction by using Google keywords. Replace the path system/framework/services.jar After replacement, you need to set permissions. You can choose the right-click permission comparison setting of the file without replacement to be exactly the same. Download address: https://wwa.lanzous.com/iFA4Lmze3va)
5:sudo umount temp
6:./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:7516192768 --group main:6012043264 --partition system:readonly:3132657664:main --image system=./system.img --partition vendor:readonly:767078400:main --image vendor=./vendor.img --partition product:readonly:220844032:main --image product=./product.img --sparse --output ./super.img
(现在需要用到前面查询的数据 数字填上即可。super:7516192768这个数据 就是没有进行解包时的数据右键在ununtu里面右键能看到其大小填上即可 后面三个分区亦可这样操作)
(Now you need to use the previous query data and fill in the numbers. Super:7516192768 This data is the data when it is not unpacked. Right click in ununtu and you can see the size and fill in the next three partitions operating)
第六步:修改后替换原始文件 现在你可以进入fastboot 快乐刷机。
Step 6: Replace the original file after modification Now you can enter fastboot happy flashing.
第七步:刷机完成后再次进入fastboot 执行如下指令 才能进入系统 否则会无限重启 操作方法:插上数据线+按着音量下键不放 直至手机自动重启后即可进入fastboot
Step 7: After the flashing is completed, enter fastboot again and execute the following commands to enter the system, otherwise it will restart indefinitely. Operation method: plug in the data cable + press and hold the volume down button until the phone automatically restarts to enter fastboot
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
lkj00 said:
感谢@bynarie @AndyYan 他们两位给我了很大帮助解决了关键问题!Thank you.
小米线刷包可以去官方网站 线刷工具网页下翻列出了所有机型的线刷包点击下载即可.
You can go to the official website for the Mi Line Brush Pack. Scroll down the line brush tool page and list the line brush packages for all models. Click to download.
第一步:安装虚拟机 同时下载 ubuntu最新桌面版系统 并在虚拟机里面安装好!并且获取root(具体安装详情设置请google)
Step 1: Install the virtual machine. At the same time, download the latest ubuntu desktop version system and install it in the virtual machine! And get root (please google for specific installation details)
第二步:下载安卓工具包 并解压共享给ubuntu 下载地址:https://forum.xda-developers.com/t/guide-ota-tools-lpunpack.4041843/ 大陆需要VPN
Step 2: Download the Android toolkit and unzip it and share it with ubuntu. Download address: https://forum.xda-developers.com/t/guide-ota-tools-lpunpack.4041843/ The mainland needs a VPN
第三步:将之前下载固件进行解压设置共享给ubuntu(具体设置请google) 在启动虚拟机ubuntu 进入桌面后点击左侧文件- 计算机-其他位置在任意文件夹或者根目录下新建文件夹名字随意。然后将之前解压的安卓工具包放到这个文件夹里面。只需要其中几个文件和驱动其他都是不需要的。请看我的截图:View attachment 5250303
Step 3: Share the previously downloaded firmware and decompress settings to ubuntu (please google for specific settings). After starting the virtual machine ubuntu and entering the desktop, click on the file on the left-computer-other locations in any folder or the root directory, create a new folder with any name . Then put the previously unzipped Android toolkit into this folder. Only a few files and drivers are needed. Please see my screenshot:
第四步:解压修改固件.我们需要修改其中的 cust.img userdata.img super.img 前面2个img 修改都很简单 google就有详细的教程不做详说。只贴出具体的执行代码!今天重点讲 suer.img 解包和打包。
Step 4: Unzip and modify the firmware. We need to modify the cust.img userdata.img super.img. The first two img modifications are very simple. Google has a detailed tutorial that will not go into details. Only post the specific execution code! Today I will focus on unpacking and packaging suer.img.
cust.img userdata.img 代码:
Code:
1:./simg2img XXXX.img XXX.img (解包)(Unpack)
2:mount -t ext4 -o loop XXX.img ./temp (挂载前一步解包的映像文件)(Mount the image file unpacked in the previous step)
(在ubuntu中删除img镜像中的文件,会生成一个.Trash的隐藏文件夹,即回收站.必需ctrl+H将其显示并删除,否则,所有删除的软件文件,
在system.img刷进手机后仍会起作用)
(Deleting the files in the img image in ubuntu will generate a hidden folder of .Trash, which is the recycle bin. It must be displayed and deleted by ctrl+H, otherwise, all deleted software files will be swiped into the phone in system.img Will still work)
3:sudo umount temp (修改完成后卸载挂载映像)(Uninstall the mount image after the modification is completed)
4:./img2simg XXX.img XXX.img (最后再打包成之前的映像文件 替换即可)(Finally package into the previous image file and replace it)
第五步:suer.img的解包和打包
Step 5: Unpacking and packaging suer.img
1:安装手机驱动 开启usb调试 下载adb命令并打开(打开adb命令一闪而过请参考 https://www.jb51.net/diannaojichu/95294.html) 查询 分区大小
Install the phone driver, open the usb debugging, download the adb command and open it (open the adb command for a flash, please refer to https://www.jb51.net/diannaojichu/95294.html) to check the partition size
Code: adb shell lpdump (请一定不要关闭窗口或保存好显示的数据,最后打包super.img 需要用到这里面的数据)
(Please do not close the window or save the displayed data, and finally package super.img to use the data inside)
2:./simg2img super.img super.raw.img
3:./lpunpack --slot=0 super.raw.img (命令完成出现三个。.img文件 我们只需要对其中system.img进行修改)
(There are three .img files after the command is completed. We only need to modify the system.img)
4:mount -t ext4 -o loop system.img ./temp
5:sudo umount temp
6:./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:7516192768 --group main:6012043264 --partition system:readonly:3132657664:main --image system=./system.img --partition vendor:readonly:767078400:main --image vendor=./vendor.img --partition product:readonly:220844032:main --image product=./product.img --sparse --output ./super.img
(现在需要用到前面查询的数据 按照数字填上即可。super:7516192768这个数据 就是没有进行解包时的数据右键在ununtu里面右键能看到其大小填上即可 后面三个分区亦可这样操作)
(Now you need to use the previous query data and fill in the numbers. Super:7516192768 This data is the data when it is not unpacked. Right click in ununtu and you can see the size and fill in the next three partitions operating)
第六步:修改后替换原始文件 现在你可以进入fastboot 快乐刷机。
Step 6: Replace the original file after modification Now you can enter fastboot happy flashing.
第七步:刷机完成后再次进入fastboot 执行如下指令 才能进入系统 否则会无限重启 操作方法:插上数据线+按着音量下键不放 直至手机自动重启后即可进入fastboot
Step 7: After the flashing is completed, enter fastboot again and execute the following commands to enter the system, otherwise it will restart indefinitely. Operation method: plug in the data cable + press and hold the volume down button until the phone automatically restarts to enter fastboot
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
what is this?

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