Database Develop

android 12 fastboot FAILED (remote: Partition system not found)

I get my pixel 4 xl oem unlocked(auto reset after the unlock) and try to flash Android 12 beta image of below link
https://dl.google.com/developers/android/sc/images/factory/coral-spp1.210122.022-factory-0b84a8a1.zip
but durning run flash-all.sh, it failed in writing system, any idea how to deal with this?
checking product...
OKAY [ 0.070s]
checking version-bootloader...
OKAY [ 0.070s]
checking version-baseband...
OKAY [ 0.070s]
sending 'boot_b' (65536 KB)...
OKAY [ 2.810s]
writing 'boot_b'...
OKAY [ 0.221s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.459s]
writing 'dtbo_b'...
OKAY [ 0.093s]
sending sparse 'system' 1/4 (262140 KB)...
OKAY [ 10.958s]
writing 'system' 1/4...
FAILED (remote: Partition system not found)
finished. total time: 15.109s

finnally I find the issue:
the fastboot on my test machine(ubuntu20.04) need sudo fastboot to run ,and with sudo , it uses the android studio old fastboot bin. after force replace the fastboot bin to newest , the flash is good
but any idea the fastboot flash need a sudo?

[Tools] HCTSW Care OSTRemote Client - Batch Script Replacement of OST LA

Code:
* // Disclaimer! //
*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead OTGs,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
HCTSW Care OSTRemote Client is an open-source replacement of the customer service flash tool OST LA and achieved by fully batch script.
Right now it's Windows only flash tool, and it remains possiblity of porting to other platforms (working in progress).
Prerequisites​
(Windows version)
- Minimal OS is Windows 7 Service Pack 1 - HCTSW Care recommends Windows 10.
- This tool utilized Google Platform Tools v29.0.5 that requires Universal C Runtime - if you're not using Windows 10, your OS must have KB2999226 hotfix installed to allow you use it.
- Your PC must have driver provided by FIH Mobile installed (Phone Nokia USB Driver and Phone F USB Driver).
- If your environment variable PATH contains quote mark ("), this tool will not work properly. You have to remove quote markts inside PATH.
- To allow you flash NB0 firmware directly, you must have Python 3 installed and add it into PATH.
- (For average Chinese users) 360 Total Security and Tencent PC Housekeeper may block some components inside.
- To allow you use MTK EDL flashing, you must extract SP Flash Tool into mtk_sp_flashtool directory, that will have flash_tool.exe with mtk_edl.cmd altogether. We recommend you to use Version 5.1824.
(Linux version)
- Any actively-maintained Linux distro with package manager - HCTSW Care recommends any Debian-based distro under amd64 architecture.
- SuSE-based Linux distros aren't tested yet, you may have to install dependencies yourself.
- Let me know about how to install dependencies respectively on macOS.
Currently it's still under experimental stage, feedbacks and contributions are welcome.
To get started:
- Download and extract "ostremote_client_public_linux_[version].tar.xz"
- Execute
Code:
sudo ./path/to/ostremote/install.sh
- enjoy it
Technical detail​
Functions:
- Regular firmware flashing (either with locked or unlocked bootloader)
- Change SKUID during firmware flashing (requires authentication procedure), including auto SKUID definition
- Erase FRP during firmware flashing (requires authentication procedure)
- Exit factory bar code mode during firmware flashing
- EDL mode (for both Qualcomm or MediaTek)
- Secure flashing detection of judging flashing conditions
Code:
- Battery capacity is lower than 41
- Insecure MTK downgrade attempts for almost all of MTK models
- Insecure MTK upgrade attempts from ROO-1 builds to ROO-2+ builds
- Insecure MTK upgrade attempts from ES2/CO2-0/1/2/3 builds to ES2/CO2-4
- Insecure MTK upgrade attempts from PDA-0/1 builds to 3
- Global conversion attempts for P2C TA-1054 (Chinese Nokia 6.1) to Global firmwares with version PL2-3xxx or older
- Insecure downgrade attempts for PNX, when downgrade from Android 10/11 to 8.1
- Downgrade attempts without erasing userdata
- Detection of prototype units
- Detection of unsupported models
Supported devices:
FRT - Nokia 1
ANT - Nokia 1 Plus
E1M - Nokia 2
E2M - Nokia 2.1
EVW - Nokia 2.1 V
NE1 - Nokia 3
ES2 - Nokia 3.1
EAG - Nokia 3.1 A & C
ROO - Nokia 3.1 Plus
RHD - Nokia 3.1 Plus C
ND1 - Nokia 5
CO2 - Nokia 5.1
PDA - Nokia 5.1 Plus X5
D1C/PLE - Nokia 6
PL2 - Nokia 6.1
DRG - Nokia 6.1 Plus X6
C1N - Nokia 7
B2N - Nokia 7 Plus
CTL - Nokia 7.1
TAS - Nokia X71
NB1 - Nokia 8
A1N - Nokia 8 Sirocco
PNX - Nokia 8.1 X7
AOP - Nokia 9 PureView
VN3 - Sharp Z3
SS2 - Sharp Aquos S2 630 - C10
SAT - Sharp Aquos S2 660
HH1/HH6 - Sharp Aquos S3 630 - D10
SD1 - Sharp Aquos S3 660
SG1 - Sharp Aquos S3 mini
Supported firmware formats:
- Unpacked factory firmware files (including *.mlf firmware description file) : Recommended.
- FIHSW original firmware format (*.nb0) : Requires Python 3.x installed but not recommended to use.
- NOST firmware format (*.qlz) : For T-Virus usage, but not recommended to use.
Syntax:
Code:
Usage: ostremote.cmd [-?|-h|--help] [-v|--verbose] [-m|--mlffile[=]C:\path\to\firmware\description\file.mlf]
[-n|--nb0file[=]C:\path\to\firmware.nb0] [-q|--qlzfile[=]C:\path\to\firmware.qlz] [-e|--erase-user-data]
[-s|--skuid[=][SKUID_value]] [-f|--erase-frp] [-ad|--accept-disclaimer] [-o|--override] [-t|--token[=]some_otp_code_here]
[-E|--edl-mode] [-p|--pretest] [-S|--skip-authentication] [-a|--authentication-only]
[-D|--disable-fac-mode] [-H|--halt] [-c|--no-checksum] [-y|--stay] [-afu|--anti-force-update] [-L|--no-slowdown]
Parameters:
-?, -h, --help : Show this help.
-v, --verbose : Enter verbose mode.
-m [mlf_file], --mlffile=[mlf_file] : Specify the path of mlf format firmware file.
Mandatory for firmware flashing.
-n [nb0_file], --nb0file=[nb0_file] : Specify the path of nb0 format firmware file.
Mandatory for firmware flashing.
-q [qlz_file], --qlzfile=[qlz_file] : Specify the path of QLZ format firmware file used by NOST.
Mandatory for firmware flashing.
-e, --erase-user-data : Erase user data during flashing procedure.
-s [skuid], --skuid=[skuid] : Change SKUID to desired value. Leave empty in
SKUID value for automatic SKUID definition.
-f, --erase-frp : Erase FRP during flashing procedure.
-ad, --accept-disclaimer : Accept the disclaimer of erasing Factory Reset Protection.
It's invalid if -f parameter is not given.
-o, --override : Skip flashing security check. NOT RECOMMENDED
for inexperienced end-users.
-t [otp_code], --token=[otp_code] : Specify OTP code given by HCTSW Care.
-E, --edl-mode : Use Emergency Download mode.
-p, --pretest : List detailed information of the phone.
-S, --skip-authentication : Skip authentication procedure. Can be only used on
supported devices with unlocked bootloader, -s and -f
parameters will become invalid with it provided.
-a, --authentication-only : Grant service permission only. If not using under
service bootloader, -e, -s and -f parameters are invalid.
-D, --disable-fac-mode : Disable Factory Bar Code mode.
-H, --halt : Power off the phone. if specified with firmware
flashing, it will power off the phone after procedure.
-c, --no-checksum : The md4 and md5 partition will not be flashed during flash
with this parameter enabled.
-y, --stay : Stay at Fastboot Mode after flash. Phone will not be rebooted.
-H parameter will not function with this parameter enabled.
-afu, --anti-force-update : Inject anti-force update code into firmware. Firmwares that
push updates via Google are unsupported.
-L, --no-slowdown : Disable Slowdown flash mode for PNX or AOP.
Usage Examples:
Flash DRG-415C-0-00WW-B01.mlf into the phone:
Code:
ostremote.cmd -m C:\path\to\FIHSW_DRG-415C-0-00WW-B01\DRG-415C-0-00WW-B01.mlf -e -s 600WW
Flash E2M-0390-0-00WW-B02.nb0 into the phone with unlocked bootloader:
Code:
ostremote.cmd -n C:\path\to\E2M-0390-0-00WW-B02.nb0 -e -S
Flash T-virus-20201108.qlz into the phone with unlocked bootloader:
Code:
ostremote.cmd -q C:\path\to\t-virus-20201108.qlz -e -S
Flash HH6-350D-0-00A0-B01.mlf into the phone and power it off:
Code:
ostremote.cmd -m C:\path\to\FIHSW_HH6-350D-0-00A0-B01\HH6-350D-0-00A0-B01.mlf -e -H
Output example:
Code:
F:\OSTRemote\Client\ostremote.cmd -m F:\D1C-562H-0-00WW-B01_Exploit\D1C-562H-0-00WW-B01.mlf -e -f -s -v
HCTSW Care OSTRemote Client V0.0.0.3n.Windows
Copyright (C) 2015-2021 Hikari Calyx Tech. All Rights Reserved.
Firmware Type: MLF
Firmware Filename: F:\D1C-562H-0-00WW-B01_Exploit\D1C-562H-0-00WW-B01.mlf
Firmware Path: F:\D1C-562H-0-00WW-B01_Exploit\
OTP
SKUID is not defined in parameters, will enable Auto SKUID.
Please connect your phone under Fastboot / Download Mode or powered off state
Serial Number: D1CGAPxxxxxxxxxx
Project Code: D1C1
Security Version: 0004
Hardware SKU: D1C
Branch SKU: None
FIH Build Version: D1C-331A-0-00CN-A01
Firmware Region: 00CN
Revision: A01
Hardware Revision: 3.0
Frequency Bands:
G_850_900_1800_1900^W_1_2_5_8^C_0^T_34_39^L_1_3_5_38_39_40_
Chip Version: None
MCP Version: None
EMMC Version: Samsung 5.1 32GB
Secure Boot: Yes
Current Slot:
Bootloader Unlocked: No
System Tampered: No
Device Unlock: No
Device Critical Unlock: No
Power-Off Charging Animation: No
Current Battery Capacity is 50
Firmware safety check is passed, you may proceed.
You have requested FRP erase during flash, for that we need you to acknowledge something.
1. Please remind the consumer to back up his own documents, photos, texts, sound files, video files, and any kinds of electric records which may be lost or destroyed before the Handset under repairing. This tool will not be responsible for such lost or destroyed.
2. Request the consumer to enter his password to unlock his screen or account in the Handset before you initial to reset. If the consumer can't provide the password or not unlock it, he shall guarantee the ownership of the Handset by written notice and copy of his ID. Without these guarantee from the consumer, you shall not assist to do a factory reset.
3. HCTSW Care authorized service provider shall have totally covenants and promises to be liable to any damage or lost caused by repair service. All information is provided "AS IS" and without any warranty, express, implied or otherwise, regarding its accuracy or performance.
4. All matters relating to this notice will be governed by the laws of current country or region without regard to its conflicts of law provisions.
5. If any damage or lost attributed to the authorized service provider under his service, the authorized service provider shall be responsible for it. This tool will not be responsible for any damage or lost mentioned previously.
Do you agree with that? If yes, press Y to confirm, otherwise press N to cancel operation. Y
Granting Permission...
========== PLEASE COPY CONTENT BELOW TO HCTSW CARE ==========
Security Version: 0004
Project Code: D1C1
DM-Veracity Challenge: 81b8c[REDACTED]4fb3da
Serial Number: D1CGAPxxxxxxxxxx
========== PLEASE COPY CONTENT ABOVE TO HCTSW CARE ==========
Content above has been copied to clipboard automatically just for your convenience.
Please input encoding message you got from HCTSW Care: YkwIOfeJYT[REDACTED]2I6HNbw==
Permission Granted
Executing "fastboot flash aboot D1C-0-562H-emmc_appsboot_service.mbn"...
Sending 'aboot' (902 KB) OKAY [ 0.032s]
Writing 'aboot' OKAY [ 0.024s]
Finished. Total time: 1.135s
Executing "fastboot flash aboot D1C-0-562H-emmc_appsboot_service.mbn"...
Sending 'aboot' (902 KB) OKAY [ 0.032s]
Writing 'aboot' OKAY [ 0.024s]
Finished. Total time: 1.134s
Rebooting bootloader...
Rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.008s
Waiting for the phone being reconnected...
Granting Permission...
========== PLEASE COPY CONTENT BELOW TO HCTSW CARE ==========
Security Version: 0001
Project Code: D1C
UID: b377[REDACTED]2301
Serial Number: D1CGAPxxxxxxxxxx
========== PLEASE COPY CONTENT ABOVE TO HCTSW CARE ==========
Content above has been copied to clipboard automatically just for your convenience.
Please input encoding message you got from HCTSW Care: 1RNQcAPt/6[REDACTED]DfdFx+gw==
Permission Granted
Executing "fastboot flash partition D1C-0-562H-gpt_both0.bin"...
Sending 'partition' (33 KB) OKAY [ 0.004s]
Writing 'partition' OKAY [ 0.026s]
Finished. Total time: 0.228s
Executing "fastboot flash aboot D1C-0-562H-emmc_appsboot_service.mbn"...
Sending 'aboot' (902 KB) OKAY [ 0.032s]
Writing 'aboot' OKAY [ 0.016s]
Finished. Total time: 0.229s
Executing "fastboot flash abootbak D1C-0-562H-emmc_appsboot_service.mbn"...
Sending 'abootbak' (902 KB) OKAY [ 0.032s]
Writing 'abootbak' OKAY [ 0.015s]
Finished. Total time: 0.240s
Executing "fastboot flash aboot D1C-0-562H-emmc_appsboot_service.mbn"...
Sending 'aboot' (902 KB) OKAY [ 0.031s]
Writing 'aboot' OKAY [ 0.015s]
Finished. Total time: 0.228s
Executing "fastboot flash abootbak D1C-0-562H-emmc_appsboot_service.mbn"...
Sending 'abootbak' (902 KB) OKAY [ 0.031s]
Writing 'abootbak' OKAY [ 0.015s]
Finished. Total time: 0.240s
Executing "fastboot flash rpm D1C-0-562H-rpm.mbn"...
Sending 'rpm' (181 KB) OKAY [ 0.008s]
Writing 'rpm' OKAY [ 0.006s]
Finished. Total time: 0.208s
Executing "fastboot flash rpmbak D1C-0-562H-rpm.mbn"...
Sending 'rpmbak' (181 KB) OKAY [ 0.009s]
Writing 'rpmbak' OKAY [ 0.006s]
Finished. Total time: 0.198s
Executing "fastboot flash sbl1 D1C-0-562H-sbl1.mbn"...
Sending 'sbl1' (357 KB) OKAY [ 0.016s]
Writing 'sbl1' OKAY [ 0.009s]
Finished. Total time: 0.232s
Executing "fastboot flash sbl1bak D1C-0-562H-sbl1.mbn"...
Sending 'sbl1bak' (357 KB) OKAY [ 0.014s]
Writing 'sbl1bak' OKAY [ 0.009s]
Finished. Total time: 0.213s
Executing "fastboot flash tz D1C-0-562H-tz.mbn"...
Sending 'tz' (1519 KB) OKAY [ 0.054s]
Writing 'tz' OKAY [ 0.022s]
Finished. Total time: 0.257s
Executing "fastboot flash tzbak D1C-0-562H-tz.mbn"...
Sending 'tzbak' (1519 KB) OKAY [ 0.051s]
Writing 'tzbak' OKAY [ 0.027s]
Finished. Total time: 0.261s
Executing "fastboot flash hwcfg D1C-0-562H-hwcfg.img"...
Sending 'hwcfg' (78 KB) OKAY [ 0.005s]
Writing 'hwcfg' OKAY [ 0.005s]
Finished. Total time: 0.191s
Executing "fastboot flash dsp D1C-0-562H-adspso.bin"...
Sending 'dsp' (16384 KB) OKAY [ 0.550s]
Writing 'dsp' OKAY [ 0.210s]
Finished. Total time: 0.958s
Executing "fastboot flash cmnlib D1C-0-562H-cmnlib.mbn"...
Sending 'cmnlib' (200 KB) OKAY [ 0.009s]
Writing 'cmnlib' OKAY [ 0.007s]
Finished. Total time: 0.240s
Executing "fastboot flash cmnlibbak D1C-0-562H-cmnlib.mbn"...
Sending 'cmnlibbak' (200 KB) OKAY [ 0.010s]
Writing 'cmnlibbak' OKAY [ 0.008s]
Finished. Total time: 0.214s
Executing "fastboot flash cmnlib64 D1C-0-562H-cmnlib64.mbn"...
Sending 'cmnlib64' (254 KB) OKAY [ 0.011s]
Writing 'cmnlib64' OKAY [ 0.009s]
Finished. Total time: 0.230s
Executing "fastboot flash cmnlib64bak D1C-0-562H-cmnlib64.mbn"...
Sending 'cmnlib64bak' (254 KB) OKAY [ 0.011s]
Writing 'cmnlib64bak' OKAY [ 0.011s]
Finished. Total time: 0.230s
Executing "fastboot flash devcfg D1C-0-562H-devcfg.mbn"...
Sending 'devcfg' (60 KB) OKAY [ 0.005s]
Writing 'devcfg' OKAY [ 0.004s]
Finished. Total time: 0.223s
Executing "fastboot flash devcfgbak D1C-0-562H-devcfg.mbn"...
Sending 'devcfgbak' (60 KB) OKAY [ 0.005s]
Writing 'devcfgbak' OKAY [ 0.006s]
Finished. Total time: 0.206s
Executing "fastboot flash keymaster D1C-0-562H-keymaster.mbn"...
Sending 'keymaster' (220 KB) OKAY [ 0.010s]
Writing 'keymaster' OKAY [ 0.007s]
Finished. Total time: 0.215s
Executing "fastboot flash keymasterbak D1C-0-562H-keymaster.mbn"...
Sending 'keymasterbak' (220 KB) OKAY [ 0.009s]
Writing 'keymasterbak' OKAY [ 0.009s]
Finished. Total time: 0.227s
Executing "fastboot reboot-bootloader"...
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.007s
Granting Permission...
========== PLEASE COPY CONTENT BELOW TO HCTSW CARE ==========
Security Version: 0001
Project Code: D1C
UID: b377[REDACTED]2301
Serial Number: D1CGAPxxxxxxxxxx
========== PLEASE COPY CONTENT ABOVE TO HCTSW CARE ==========
Existing permission granting file detected. Reusing...
Permission Granted
Executing "fastboot flash splash D1C-00WW-026-splash.img"...
Sending 'splash' (2700 KB) OKAY [ 1.203s]
Writing 'splash' OKAY [ 0.041s]
Finished. Total time: 1.830s
Executing "fastboot flash ftmboot D1C-0-562H-ftm.img"...
Sending 'ftmboot' (28805 KB) OKAY [ 0.968s]
Writing 'ftmboot' OKAY [ 0.367s]
Finished. Total time: 1.532s
Executing "fastboot flash multi_splash D1C-00WW-026-multi-splash.img"...
Sending 'multi_splash' (83 KB) OKAY [ 0.005s]
Writing 'multi_splash' OKAY [ 0.005s]
Finished. Total time: 0.234s
Executing "fastboot flash boot D1C-0-562H-00WW-boot.img"...
Sending 'boot' (22093 KB) OKAY [ 0.755s]
Writing 'boot' OKAY [ 0.283s]
Finished. Total time: 1.223s
Executing "fastboot flash system D1C-0-562H-00WW-system.img"...
******** Did you mean to fastboot format this ext4 partition?
Erasing 'system' OKAY [ 0.693s]
fastboot: usage: unknown command D1C-0-562H-00WW-system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/7 (511578 KB) OKAY [ 16.578s]
Writing 'system' OKAY [ 12.841s]
Sending sparse 'system' 2/7 (516906 KB) OKAY [ 16.796s]
Writing 'system' OKAY [ 18.969s]
Sending sparse 'system' 3/7 (484835 KB) OKAY [ 15.967s]
Writing 'system' OKAY [ 30.431s]
Sending sparse 'system' 4/7 (520631 KB) OKAY [ 16.838s]
Writing 'system' OKAY [ 7.631s]
Sending sparse 'system' 5/7 (512021 KB) OKAY [ 16.664s]
Writing 'system' OKAY [ 7.891s]
Sending sparse 'system' 6/7 (523263 KB) OKAY [ 17.011s]
Writing 'system' OKAY [ 8.139s]
Sending sparse 'system' 7/7 (505228 KB) OKAY [ 16.424s]
Writing 'system' OKAY [ 12.106s]
Finished. Total time: 259.476s
Executing "fastboot flash recovery D1C-0-562H-00WW-recovery.img"...
Sending 'recovery' (29339 KB) OKAY [ 1.109s]
Writing 'recovery' OKAY [ 0.377s]
Finished. Total time: 1.698s
Executing "fastboot erase userdata"...
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata' OKAY [ 0.516s]
Finished. Total time: 0.625s
Executing "fastboot flash persist D1C-0-562H-00WW-persist.img"...
Sending 'persist' (32768 KB) OKAY [ 1.099s]
Writing 'persist' OKAY [ 0.419s]
Finished. Total time: 1.731s
Executing "fastboot erase cache"...
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.016s]
Finished. Total time: 0.118s
Executing "fastboot flash sutinfo D1C-00WW-001-sutinfo.img"...
Sending 'sutinfo' (0 KB) OKAY [ 0.003s]
Writing 'sutinfo' OKAY [ 0.003s]
Finished. Total time: 0.198s
Executing "fastboot flash modem D1C-0-562H-NON-HLOS.bin"...
Sending 'modem' (86016 KB) OKAY [ 3.011s]
Writing 'modem' OKAY [ 1.091s]
Finished. Total time: 4.310s
Executing "fastboot flash hidden D1C-0-0020-0001-hidden.img.ext4"...
Sending 'hidden' (40960 KB) OKAY [ 1.373s]
Writing 'hidden' OKAY [ 0.531s]
Finished. Total time: 2.120s
Executing "fastboot flash cda D1C-00WW-026-cda.img"...
Sending 'cda' (8192 KB) OKAY [ 0.307s]
Writing 'cda' OKAY [ 0.109s]
Finished. Total time: 0.655s
Executing "fastboot flash systeminfo fver"...
Erasing 'systeminfo' OKAY [ 0.021s]
fastboot: usage: unknown command fver
Sending 'systeminfo' (36 KB) OKAY [ 0.004s]
Writing 'systeminfo' OKAY [ 0.005s]
Finished. Total time: 0.213s
Executing "fastboot flash ftmlog D1C-0-0020-0001-userdata-ftm.img.ext4"...
Sending 'ftmlog' (4664 KB) OKAY [ 0.149s]
Writing 'ftmlog' OKAY [ 0.111s]
Finished. Total time: 0.529s
Executing "fastboot flash default_nv D1C-0-562H-NV-default.mbn"...
Sending 'default_nv' (1840 KB) OKAY [ 0.064s]
Writing 'default_nv' OKAY [ 0.028s]
Finished. Total time: 0.320s
Executing "fastboot flash sec D1C-0-562H-sec.dat"...
Sending 'sec' (0 KB) OKAY [ 0.004s]
Writing 'sec' OKAY [ 0.002s]
Finished. Total time: 0.185s
Executing "fastboot flash mdtp D1C-0-562H-00WW-mdtp.img"...
Sending 'mdtp' (17390 KB) OKAY [ 0.589s]
Writing 'mdtp' OKAY [ 0.234s]
Finished. Total time: 1.046s
Executing "fastboot flash aboot D1C-0-562H-emmc_appsboot.mbn"...
Sending 'aboot' (902 KB) OKAY [ 0.033s]
Writing 'aboot' OKAY [ 0.016s]
Finished. Total time: 0.250s
Executing "fastboot flash abootbak D1C-0-562H-emmc_appsboot.mbn"...
Sending 'abootbak' (902 KB) OKAY [ 0.032s]
Writing 'abootbak' OKAY [ 0.017s]
Finished. Total time: 0.244s
Flash Complete.
Changing SKUID to 600WW...
...
OKAY [ 0.013s]
finished. total time: 0.014s
Erasing FRP...
Erasing 'frp' OKAY [ 0.018s]
Finished. Total time: 0.112s
Phone rebooted.
rebooting...
finished. total time: 0.005s
Detect an unsupported phone and also a prototype unit:
Code:
F:\OSTRemote\Client>ostremote.cmd -p
HCTSW Care OSTRemote Client V0.0.0.3n.Windows
Copyright (C) 2015-2021 Hikari Calyx Tech. All Rights Reserved.
Pretest Mode
Please connect your phone under Fastboot / Download Mode or powered off state
=== SUSPICIOUS PROTOTYPE UNIT DETECTED ===
=== HMDSW DEVICE DETECTED, PLEASE USE CODENAME "DK2" ===
Serial Number: 100M690[REDACTED]220
Project Code: Daredevil
Security Version: 2
Hardware SKU: Nokia7.2
Branch SKU: None
FIH Build Version: 00WW_2_400_SP02
Firmware Region:
Revision: A01
Hardware Revision: A1-1
Frequency Bands:
Secure Boot: No
Current Slot: a
Bootloader Unlocked: Yes
Verity Mode: Yes
Device Unlock: Yes
Device Critical Unlock: Yes
Power-Off Charging Animation: Yes
Pretest Complete. How would you like to process your phone next?
Press R to reboot your phone, press H to shutdown your phone, and press S to stay at Fastboot Mode.
Known issues​
- The path of OSTRemote itself and the firmware cannot contain brackets.
- Due to the nature of some devices, you shall not flash the phone via USB 3.1 port on your PC - especially Nokia 9.
Implemented components​- GnuWin32 components : gawk, dd, sed, xxd, unzip, zipinfo
- Public domain components : md5
- Google Platform Tools v29.0.5
- fb2 (special build of fastboot.exe extracted from OST LA)
- fb3 (special build of fastboot.exe extracted from "DK")
- findstr7.exe (Extracted from Windows 7 Service Pack 1 32-bit, Version 6.1.7601.17514 for PCs without findstr)
- nb0-unpack.py
- exdupe (binary of QuickLZ)
- fh_loader and qsaharaserver (extracted from QPST)
- MTK SP Flash Tool (not included)
- devcon (Not used yet)
- certutil (Come with Windows)
Special thanks​@EdwardWu6688 for Traditional Chinese localization
Roman Yepishev for NB0 firmware processing script
(linux specific) bkerler for edl tools
FIH Mobile and triple-color company for specific binaries
Current version of OSTRemote Client : V0.3Q

Changelog​V0.3r
- (Linux) Initial release
- Since Chinese OTA server is down, anti force OTA function is now removed
- now installation script should work on Debian/RedHat/Arch based distro
- (Linux) Add specify language option (only zh_CN, zh_TW and en_US are supported yet)
V0.3q
- Added following secure flashing rule:
Code:
- Insecure MTK upgrade from PDA-0/1 builds to 3
- Added unstable USB traffic connection detect
- Fixed EDL mode issue when memory type is not given in MLF file
- Added slowdown workaround for PNX/AOP, which can be disabled with -L or --no-slowdown parameter
- Added -ad or --accept-disclaimer parameter for skipping FRP erasing warning (ideal for bulk flashing)
- Fixed Huawei HiSuite detection
V0.3p
- Fixed issue of flashing sec8 devices (e.g. PNX, AOP)
- Added detection of Mobile Assistant apps : Huawei HiSuite and 360 Mobile Assistant.
If they were installed, you'll be prompted to disable them.
- If the PC currently using has Windows 8.1 or older running, the tool will now resize the window automatically.
V0.3o
- To make this tool suitable for bulk flashing, added -s "serial number" parameter inside all of scripts
- Added following secure flashing rules:
Code:
- Insecure MTK upgrade from ES2/CO2-0/1/2/3 builds to 4
- Global conversion for P2C TA-1054 (Chinese Nokia 6.1) to Global firmwares with version PL2-3xxx or older
V0.3n
- Initial public release

FAQ​
Q1: Can I use it on locked bootloader phones?
A1: Yes, but you cannot pass authentication procedure yourself. You'll have to pay and request the remote flashing service you find online. We cannot mention where to request, please find yourself.
Q2: How to use it on existing unlocked bootloader phones?
A2: Always add "-S" parameter (it's case sensitive).
Q3: Can I use it without Internet connection?
A4: If you do have unlocked bootloader, of course you can. If you don't have unlocked bootloader, once you know how to transfer the encoding message it requires, it can be used.
Q4: Where the OTP code is used?
A4: It was originally used by the paid phone flashing service, but due to technical confidentiality, we removed codes of utilizing this part on purpose.
Q5: Will it support Nokia x.2/x.3/x.4/Cxx/Gxx/Xxx (excluding X71) phones?
A5: This tool only provides detection of these phones, but it will not support them.
Q6: Is this tool crackable?
A6: Feel free to review or tinkering the code of this tool, but you'll find you cannot crack it.
Q7: What can I contribute?
A7: You can contribute translation into your own language and save it into your own language code name.
For language code, please read this : https://www.autoitscript.com/autoit3/docs/appendix/OSLangCodes.htm
For Windows version, the language code should be heximal value:
e.g. Russian language string file should be named as 0419.cmd , and has to be saved as local encoding system (ANSI + windows-1251).
For macOS/Linux version, the language code should be the general country code:
e.g. German language string file should be named as de-DE.sh , and has to be saved as UTF-8.
Q8: Why this tool says "Outdated Fastboot Binary in environment variable detected. Delete your outdated Fastboot Binary (and probably ADB Binary) before you proceed"?
A8: You probably had "Minimal ADB and Fastboot" installed and added into environmental variables. Since binaries from "Minimal ADB and Fastboot" are horribly out of date and will interrupt the usage of this tool, so you have to delete it before using. The output of OSTRemote will tell you the path of your outdated fastboot binary.
Q9: What about OSTRemote Host?
A9: OSTRemote Host is our proprietary tool, we cannot publish it to public.
Q10: Can you port this to Windows XP?
A10: Nope. It's already 2021, why would you still use such 20-year-old OS?
Q11: Why OSTRemote cannot find "reg" executable?
A11: You may either using "Lite" Windows build or you broke the PATH environment variable.
You'll need to change the value of PATH (system variable) into this to ensure this tool will work as expect:
Code:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\
Q12: Why my antivirus app marked "exdupe.exe" inside as virus?
A12: It's the main executable used by NOST for processing *.qlz files. If you don't need to flash qlz files (specifically used by T-Virus), you can safely delete it.

Reserved #3

Hi all.
Because I've brought my own flash tool to fully replace the OST LA, original OST LA is deprecated for me as I've fully understand how it works.
Threads related to old OST LA will be closed.

Can it flash ROM in locked bootloader?

FutureStarz said:
Can it flash ROM in locked bootloader?
Click to expand...
Click to collapse
Yes, but you'll need to exchange service permission code to us, which the algorithm cannot be disclosed yet.

hikari_calyx said:
Yes, but you'll need to exchange service permission code to us, which the algorithm cannot be disclosed yet.
Click to expand...
Click to collapse
I need to downgrade my nokia 6 to nougat. Can I flash ROM directly with this?

To subscribers:
OSTRemote for Linux is now released!
Currently it's under experimental stage, so please send feedback for the issue you encountered.
Right now only Debian-based distro (e.g. Ubuntu) amd64 is tested.

For flashing nb0 file (Windows), command prompt is stuck at "Verifying flash result, please wait..."
Edit: Did ctrl-c, asked if I wanted to exist the script, said no, then said flashing complete. All good

Hi everyone i recenly flash my nokia 6.1 P2C to PL2 but i get this issue:
HCTSW Care OSTRemote Client V0.0.0.3q.Windows
Copyright (C) 2015-2021 Hikari Calyx Tech. All Rights Reserved.
The system cannot find the batch label specified - error_noedldesc

How To Guide Flashing a GSI to redmi note 10 5G KEEPING IT SIMPLE edition.

Flashing a GSI to redmi note 10 5G KEEPING IT SIMPLE edition.
(I dont take responsibility of you destroying your device or causing the world end by flashing. Take proper precautions before proceeding and do your research about the subject and your device)
(Before you proceed, backup important data from your internal storage, i also assume that you have adb tools and drivers installed for your device and bootloader unlocked. Please do also your own research about your device before proceeding.)
adb reboot bootloader (Booting to fastboot)
fastboot reboot fastboot (Booting from fastboot to fastbootd)
fastboot erase system
fastboot -w (deletes userdata, formats the data partition. running this just to be sure personally)
You migth get an error :
/usr/bin/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata (wich is no cause for concern)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (Thanks 1lopes for pointing missing arguments, more information in the first 3 comments)
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.013s]
fastboot fastboot flash system GSIofyourchoice.img
Invalid sparse file format at header magic (no need for concern)
Resizing 'system_a' OKAY [ 0.008s]
Sending sparse 'system_a' 1/7 (262108 KB) OKAY [ 20.939s]
Writing 'system_a' OKAY [ 1.041s]
Sending sparse 'system_a' 2/7 (262120 KB) OKAY [ 21.163s]
Writing 'system_a' OKAY [ 1.217s]
Sending sparse 'system_a' 3/7 (262116 KB) OKAY [ 19.183s]
Writing 'system_a' OKAY [ 1.157s]
Sending sparse 'system_a' 4/7 (262120 KB) OKAY [ 15.908s]
Writing 'system_a' OKAY [ 1.052s]
Sending sparse 'system_a' 5/7 (262088 KB) OKAY [ 19.747s]
Writing 'system_a' OKAY [ 1.045s]
Sending sparse 'system_a' 6/7 (262124 KB) OKAY [ 20.658s]
Writing 'system_a' OKAY [ 1.038s]
Sending sparse 'system_a' 7/7 (166688 KB) OKAY [ 13.939s]
Writing 'system_a' OKAY [ 0.861s]
Finished. Total time: 152.907s
fastboot reboot recovery (Reboots your phone to recovery, do factory reset) (EDITED)
This way, you dont destroy ability to boot to fastboot, fastbootd and you keep your original recovery and bootloader intact. If you boot to recovery after a reboot, do a factory reset from there and try to boot again, should work. IF it dosen't, you can easily try other gsi with the same steps.
vbmeta.img provided in this guide disables Android Verified Boot (AVB), Some devices have problems booting into custom GSI:s it enabled.
EDIT:
I was in stock MIUI13 (bootloader unlocked) , did factory reset, re enabled usb debugging and followed the steps in this guide.
I personally used phusson android 12 gsi
(system-squeak-arm64-ab-vndklite-vanilla-secure)
with the vbmeta.img in this guide.
Origin of vbmeta.img and information. Please use the vbmeta.img provided below. If the drive link does not work, you can find it from the original information source below. :
vbmeta.img
drive.google.com
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/

i have a question. from the other guide to flash pe, why cant we do the command
fastboot delete-logical-partition product
?
thanks for the guide btw, might try later on my redmi note 10 5g flashing pe in it, just this question tho

also i think u forgot a very important step, i think you need to disable verity and verification or that could boot up with dm-verity corruption
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

1lopes said:
also i think u forgot a very important step, i think you need to disable verity and verification or that could boot up with dm-verity corruption
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Thanks for pointing that out mate ! ill be adding it to op. I did not need the arguments personally tough but it is better to be safe than sorry!
The reason i discourage the wiping of logical partition ''product'' is, it contains the original recovery for example, information for fastboot and fastbootd. It is not needed to wipe product partition at all in order to flash GSI:s and use them.
If you have software to replace the functions with 3rd party ones and you know what you are doing, you can do it but just be aware what changes you are doing for your phone's software.
it contains the crucial pieces i want to keep safe in this quide to make it easyer to go back to stock frimware.
Remember to use the vbmeta.img im pointing to in this guide. Im quoting the reason directly from xda. if the vbmeta.img direct drive link does not work, look it up from the original information source :
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
''
On some devices like the Google Pixel 2/2 XL, Android Verified Boot (AVB) needs to be disabled. You can do so by flashing this image to the vbmeta partition (command: fastboot flash vbmeta name_of_vbmeta.img)
''
However if this information is wrong, ill admit it and pull it off. This guide contains the steps i followed personally with success and without hassle with this device.

toonTT said:
Thanks for pointing that out mate ! ill be adding it to op. I did not need the arguments personally tough but it is better to be safe than sorry!
The reason i discourage the wiping of logical partition ''product'' is, it contains the original recovery for example, information for fastboot and fastbootd. It is not needed to wipe product partition at all in order to flash GSI:s and use them.
If you have software to replace the functions with 3rd party ones and you know what you are doing, you can do it but just be aware what changes you are doing for your phone's software.
it contains the crucial pieces i want to keep safe in this quide to make it easyer to go back to stock frimware.
Remember to use the vbmeta.img im pointing to in this guide. Im quoting the reason directly from xda. if the vbmeta.img direct drive link does not work, look it up from the original information source :
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
''
On some devices like the Google Pixel 2/2 XL, Android Verified Boot (AVB) needs to be disabled. You can do so by flashing this image to the vbmeta partition (command: fastboot flash vbmeta name_of_vbmeta.img)
''
However if this information is wrong, ill admit it and pull it off. This guide contains the steps i followed personally with success and without hassle with this device.
Click to expand...
Click to collapse
Thank you so much for the information, especially about deleting the logical partition product.
Maybe that would have had affected the last part of wiping user data in recovery after flashing a GSI? (Unless the fastboot -w already does it) in the other guide. For example, this person couldn't get any GSI booting.
Also, dont you necessarily need to set active a? ( fastboot set_active a )
toonTT said:
I did not need the arguments personally tough but it is be better to be safe than sorry!
Click to expand...
Click to collapse
Didnt mean to make a argument for you, i was just pointing it all!

1lopes said:
Didnt mean to make a argument for you, i was just pointing it all!
Click to expand...
Click to collapse
Oh dear my bad, i wasn't clear enough what i meant by that. did not mean it that way, i was talking about the command arguments what you use with fastboot while flashing vbmeta.img . '' --disable-verity --disable-verification '' i did not personally use them and had not problems.
fastboot -w formats the data partition, where user data is, thats how i understand it.
About the booting problem , that he deleted the logical partition is a red flag for me. Im no expert but thats how i see it.

toonTT said:
Oh dear my bad, i wasn't clear enough what i meant by that. did not mean it that way, i was talking about the command arguments what you use with fastboot while flashing vbmeta.img .
Click to expand...
Click to collapse
Oh! I misunderstood it. I'm sorry. Anyways, lets move on.
toonTT said:
About the booting problem , that he deleted the logical partition is a red flag for me. Im no expert but thats how i see it.
Click to expand...
Click to collapse
Actually, you probably are correct. It basically might delete recovery and fastboot information just like you said, and from here it also refers as it being a system extension, etc. that I really don't understand my self.
toonTT said:
fastboot -w formats the data partition, where user data is, thats how i understand it.
Click to expand...
Click to collapse
Oh, thanks for it, as I was unsure from my last reply. Maybe it's not really necessary, but thanks to you for pointing out that fastboot delete-logical-partition product would delete the original recovery, as for that you don't need to do that command because you only need to do fastboot reboot recovery and then select wipe data and all done.
Again, thank you for pointing the big problem of the logical partition product deleting. I was about to flash PE maybe yesterday or the day before yesterday, and I could, or many more, make this mistake and could go wrong even more than just a soft brick on the phone

delete logical is not necessary. all gsi i have installed go up without do this. if you delete the patition even if uncessary, sure cold cause issues. use your brains and read the guides

Hi friends,
I just tried to flash my Redmi Note 10 5G and my phone freezes on "fastboost" every time it boots.
I tried to flash 2 "Phhusson" files:
- system-squeak-arm64-ab-vndklite-vanilla.img.xz
- system-squeak-arm64-ab-vndklite-gogapps-secure.img.xz
(same fastboot problem on startup with the 2 files)
I tried a "wipe data" in recovery mode.
If you have a solution to find my phone?
Thank you in advance for your help.
Here are the commands I sent:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 12.976s
fastboot erase system
Erasing 'system_a' OKAY [ 0.085s]
Finished. Total time: 0.116s
fastboot -w
Erasing 'userdata' OKAY [ 2.083s]
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 227016640 (110847 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1281] Writing root inode (hot node), 1d000 0 200 at offset 0x00118784
[f2fs_write_default_quota:1357] Writing quota data, at offset 0001d601, 0001d602
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 1d000 0 200 at offset 0x00118785
[f2fs_write_default_quota:1357] Writing quota data, at offset 0001d603, 0001d604
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 1d000 0 200 at offset 0x00118786
[f2fs_update_nat_root:1470] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1667] Writing default dentry root, at offset 0x0001d600
Info: Overprovision ratio = 0.600%
Info: Overprovision segments = 670 (GC reserved = 341)
[f2fs_write_check_point_pack: 827] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1081] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.000s]
Writing 'userdata' OKAY [ 0.501s]
Erasing 'metadata' OKAY [ 0.016s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 8192 4k blocks and 8192 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'metadata' (44 KB) OKAY [ 0.007s]
Writing 'metadata' OKAY [ 0.000s]
Finished. Total time: 3.717s
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.016s]
Finished. Total time: 0.053s
fastboot flash system system-squeak-arm64-ab-vndklite-gapps-secure.img
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 1/11 (261709 KB) OKAY [ 9.121s]
Writing 'system_a' OKAY [ 1.203s]
Sending sparse 'system_a' 2/11 (262124 KB) OKAY [ 8.905s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 3/11 (262116 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.024s]
Sending sparse 'system_a' 4/11 (262124 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 5/11 (262128 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.002s]
Sending sparse 'system_a' 6/11 (262116 KB) OKAY [ 8.820s]
Writing 'system_a' OKAY [ 1.165s]
Sending sparse 'system_a' 7/11 (262124 KB) OKAY [ 8.874s]
Writing 'system_a' OKAY [ 1.187s]
Sending sparse 'system_a' 8/11 (259235 KB) OKAY [ 8.783s]
Writing 'system_a' OKAY [ 1.056s]
Sending sparse 'system_a' 9/11 (260056 KB) OKAY [ 8.767s]
Writing 'system_a' OKAY [ 1.040s]
Sending sparse 'system_a' 10/11 (258520 KB) OKAY [ 8.635s]
Writing 'system_a' OKAY [ 1.065s]
Sending sparse 'system_a' 11/11 (23178 KB) OKAY [ 0.902s]
Writing 'system_a' OKAY [ 0.254s]
Finished. Total time: 109.991s
fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s

Glucksnip said:
Hi friends,
I just tried to flash my Redmi Note 10 5G and my phone freezes on "fastboost" every time it boots.
I tried to flash 2 "Phhusson" files:
- system-squeak-arm64-ab-vndklite-vanilla.img.xz
- system-squeak-arm64-ab-vndklite-gogapps-secure.img.xz
(same fastboot problem on startup with the 2 files)
I tried a "wipe data" in recovery mode.
If you have a solution to find my phone?
Thank you in advance for your help.
Here are the commands I sent:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 12.976s
fastboot erase system
Erasing 'system_a' OKAY [ 0.085s]
Finished. Total time: 0.116s
fastboot -w
Erasing 'userdata' OKAY [ 2.083s]
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 227016640 (110847 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1281] Writing root inode (hot node), 1d000 0 200 at offset 0x00118784
[f2fs_write_default_quota:1357] Writing quota data, at offset 0001d601, 0001d602
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 1d000 0 200 at offset 0x00118785
[f2fs_write_default_quota:1357] Writing quota data, at offset 0001d603, 0001d604
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 1d000 0 200 at offset 0x00118786
[f2fs_update_nat_root:1470] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1667] Writing default dentry root, at offset 0x0001d600
Info: Overprovision ratio = 0.600%
Info: Overprovision segments = 670 (GC reserved = 341)
[f2fs_write_check_point_pack: 827] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1081] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.000s]
Writing 'userdata' OKAY [ 0.501s]
Erasing 'metadata' OKAY [ 0.016s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 8192 4k blocks and 8192 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'metadata' (44 KB) OKAY [ 0.007s]
Writing 'metadata' OKAY [ 0.000s]
Finished. Total time: 3.717s
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.016s]
Finished. Total time: 0.053s
fastboot flash system system-squeak-arm64-ab-vndklite-gapps-secure.img
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 1/11 (261709 KB) OKAY [ 9.121s]
Writing 'system_a' OKAY [ 1.203s]
Sending sparse 'system_a' 2/11 (262124 KB) OKAY [ 8.905s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 3/11 (262116 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.024s]
Sending sparse 'system_a' 4/11 (262124 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 5/11 (262128 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.002s]
Sending sparse 'system_a' 6/11 (262116 KB) OKAY [ 8.820s]
Writing 'system_a' OKAY [ 1.165s]
Sending sparse 'system_a' 7/11 (262124 KB) OKAY [ 8.874s]
Writing 'system_a' OKAY [ 1.187s]
Sending sparse 'system_a' 8/11 (259235 KB) OKAY [ 8.783s]
Writing 'system_a' OKAY [ 1.056s]
Sending sparse 'system_a' 9/11 (260056 KB) OKAY [ 8.767s]
Writing 'system_a' OKAY [ 1.040s]
Sending sparse 'system_a' 10/11 (258520 KB) OKAY [ 8.635s]
Writing 'system_a' OKAY [ 1.065s]
Sending sparse 'system_a' 11/11 (23178 KB) OKAY [ 0.902s]
Writing 'system_a' OKAY [ 0.254s]
Finished. Total time: 109.991s
fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
Click to expand...
Click to collapse
You used vndklite. Thats the problem.
The redmi note 10 5g doesnt has VNDK LITE Treble, only Treble VNDK version 31.0
Check:
{
"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"
}
Please check any ROM carefully that its not "vndklite" after the ROM variant (bgN-vndklite), if theres no variant information, check if it says "arm64-ab" with no vndklite and you are good to go.
Some vndklite systems are only for A slots, others are for a/b, but that doesnt solve the problem as the Redmi doesnt include vndklite treble.

1lopes said:
You used vndklite. Thats the problem.
The redmi note 10 5g doesnt has VNDK LITE Treble, only Treble VNDK version 31.0
Check:View attachment 5668855
Please check any ROM carefully that its not "vndklite" after the ROM variant (bgN-vndklite), if theres no variant information, check if it says "arm64-ab" with no vndklite and you are good to go.
Some vndklite systems are only for A slots, others are for a/b, but that doesnt solve the problem as the Redmi doesnt include vndklite treble.
Click to expand...
Click to collapse
I have unzipped the img file: "fastboot flash system system-squeak-arm64-ab-vndklite-gapps-secure.img"
I chose this file because on the first post of this conversation @toonTT says: "I personally used phusson android 12 gsi (system-squeak-arm64-ab-vndklite-vanilla-secure)"

Glucksnip said:
I have unzipped the img file: "fastboot flash system system-squeak-arm64-ab-vndklite-gapps-secure.img"
I chose this file because on the first post of this conversation @toonTT says: "I personally used phusson android 12 gsi (system-squeak-arm64-ab-vndklite-vanilla-secure)"
Click to expand...
Click to collapse
Thats the problem, Redmi Note 10 5G doesn't support vndklite. Use a ROM that is "arm64-ab" and is not intended for devices with vndklite.

1lopes said:
Thats the problem, Redmi Note 10 5G doesn't support vndklite. Use a ROM that is "arm64-ab" and is not intended for devices with vndklite.
Click to expand...
Click to collapse
OK, thanks
Just tested @phhusson's "system-squeak-arm64-ab-gapps.img" and still the damn "fastboot" on boot.
- PixelExperience-Plus_.imgarm64-ab-12.1-20220722-unofficial
- lineage-19.1-20220511-UNOFFICIAL-arm64_bvS-personal.img
each time it is "fastboot" which launches at each start.
I tried to install
"camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5.tgz"
The flash is done in 1 second and MiFlash tells me that everything is fine. Inevitably in 1 second it is fastboot which launches.
I don't know what else to test...

Glucksnip said:
OK, thanks
Just tested @phhusson's "system-squeak-arm64-ab-gapps.img" and still the damn "fastboot" on boot.
- PixelExperience-Plus_.imgarm64-ab-12.1-20220722-unofficial
- lineage-19.1-20220511-UNOFFICIAL-arm64_bvS-personal.img
each time it is "fastboot" which launches at each start.
I tried to install
"camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5.tgz"
The flash is done in 1 second and MiFlash tells me that everything is fine. Inevitably in 1 second it is fastboot which launches.
I don't know what else to test...
Click to expand...
Click to collapse
Private message me please, i will try to help you there, and so sorry for the wait and inactivity.

1lopes said:
Private message me please, i will try to help you there, and so sorry for the wait and inactivity.
Click to expand...
Click to collapse
No problem we have a life outside the internet ;-)
It's good I managed to recover my phone using a really cool application "XiaomiTool2" it fixed my phone in a few clicks, too strong !!
it installed miui 13 Global_V13.0.2.0.SKSEUXM
Thanks for the help ;-)

Glucksnip said:
No problem we have a life outside the internet ;-)
It's good I managed to recover my phone using a really cool application "XiaomiTool2" it fixed my phone in a few clicks, too strong !!
it installed miui 13 Global_V13.0.2.0.SKSEUXM
Thanks for the help ;-)
Click to expand...
Click to collapse
Im glad it worked. Sorry that I couldnt help you, but atleast you got it working againIf you need any help you can contact anyone here or me

Glucksnip said:
OK, thanks
Just tested @phhusson's "system-squeak-arm64-ab-gapps.img" and still the damn "fastboot" on boot.
- PixelExperience-Plus_.imgarm64-ab-12.1-20220722-unofficial
- lineage-19.1-20220511-UNOFFICIAL-arm64_bvS-personal.img
each time it is "fastboot" which launches at each start.
I tried to install
"camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5.tgz"
The flash is done in 1 second and MiFlash tells me that everything is fine. Inevitably in 1 second it is fastboot which launches.
I don't know what else to test...
Click to expand...
Click to collapse
In my experience, I flash MIUI 12.2 first before flash the GSI and voila it works.
If I flash GSI from MIUI 12.5 or 13, it always boot into fastboot after clear data in recovery mode.
Hope it answer your question

Sorry out of topic
Is there any tutorial/step to flash GSI Using TWRP on Poco M3 pro 5G?

ThinkIt12 said:
Sorry out of topic
Is there any tutorial/step to flash GSI Using TWRP on Poco M3 pro 5G?
Click to expand...
Click to collapse
Nope, since there's not even a official TWRP (but a unofficial one) for both of the devices here or a guide in this forum. Try checking a youtube video.

ThinkIt12 said:
Sorry out of topic
Is there any tutorial/step to flash GSI Using TWRP on Poco M3 pro 5G?
Click to expand...
Click to collapse
flash without twrp, using fastboot commands.. is easy, safe and better than twrp (actually touch dont work, need otg cable)

Android 13 build instructions

We are happy to announce that we now have launched AOSP build instructions for Android 13!
The Xperia Open Source Project (Xperia Open Devices) is an initiative created to guide the developers step-by-step on how to build AOSP for their unlocked Xperia devices. Our instructions will show you how to prepare your environment, how to download all the necessary tools, and how to download and configure the code before you can build AOSP images and flash them on your own device.
New AOSP build instructions for Android 13 - Sony Developer World
developer.sony.com

Hello, i have built android 13 for this phone but when i flashed it and rebooted it, it got stuck at the sony logo. Any help is appreciated.

I am investigating the issue caused by the latest kernel updates
please use an older prebuilt kernel

I'm getting build error. Followed the guide. Except I use Archlinux and to get dependencies i used this https://aur.archlinux.org/packages/aosp-devel. How to build?
Code:
❯ make -j$(nproc)
16:32:44 ************************************************************
16:32:44 You are building on a machine with 15.4GB of RAM
16:32:44
16:32:44 The minimum required amount of free memory is around 16GB,
16:32:44 and even with that, some configurations may not work.
16:32:44
16:32:44 If you run into segfaults or other errors, try reducing your
16:32:44 -j value.
16:32:44 ************************************************************
build/make/core/soong_config.mk:209: warning: BOARD_PLAT_PUBLIC_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PUBLIC_SEPOLICY_DIRS instead.
build/make/core/soong_config.mk:210: warning: BOARD_PLAT_PRIVATE_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PRIVATE_SEPOLICY_DIRS instead.
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=13
TARGET_PRODUCT=aosp_xqau52
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.19.12-arch1-1-x86_64-Arch-Linux
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=TP1A.221005.002
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=device/sony/common device/sony/seine vendor/qcom/opensource/core-utils vendor/qcom/opensource/display/sm8250 vendor/qcom/opensource/display-commonsys-intf/sm8250
============================================
[ 99% 393/396] analyzing Android.bp files and generating ninja file at out/soong/build.ninja
FAILED: out/soong/build.ninja
cd "$(dirname "out/host/linux-x86/bin/soong_build")" && BUILDER="$PWD/$(basename "out/host/linux-x86/bin/soong_build")" && cd / && env -i "$BUILDER" --top "$TOP" --soong_out "out/soong" --out "out" -o out/soong/build.ninja --globListDir build --globFile out/soong/globs-build.ninja -t -l out/.module_paths/Android.bp.list --available_env out/soong/soong.environment.available --used_env out/soong/soong.environment.used.build Android.bp
16:35:28 soong bootstrap failed with: exit status 1
#### failed to build some targets (02:45 (mm:ss)) ####
UPDATE. This broke because of out of memory and no swap. It was enough to fix that to add a swap file (see https://wiki.archlinux.org/title/Swap#Swap_file) .

Thanks for this instructions. I tried to flash it but I also stuck at the Sony logo displayed and response to my pressing buttons or touching the screen. How to install AOSP?
I followed the guide. It is XQ-AU52. Used Software binaries for AOSP Android 11.0 – Kernel 4.14 – Seine. It failed to flash some at first. Then I rebootted to recovery, formated all data, entered fastboot and then all images flashed. See log for flashing. I can exit this loading by pressing VolumeUp+Power.
And when I flash LineageOS from here (wiped out all data), I can't set PIN: it fails with some error, it writes that Settings failed and exits to the main screen. And then when I restart it it can't load main screen, displays the message "Starting smartphone..." in my locale.
Code:
❯ fastboot flash boot out/target/product/pdx201/boot.img
fastboot flash vbmeta out/target/product/pdx201/vbmeta.img
fastboot flash dtbo out/target/product/pdx201/dtbo.img
fastboot flash recovery out/target/product/pdx201/recovery.img
fastboot flash system out/target/product/pdx201/system.img
fastboot flash vendor out/target/product/pdx201/vendor.img
fastboot flash userdata out/target/product/pdx201/userdata.img
fastboot flash product out/target/product/pdx201/product.img
fastboot flash vbmeta_system out/target/product/pdx201/vbmeta_system.img
fastboot flash system_ext out/target/product/pdx201/system_ext.img
fastboot flash vendor_boot out/target/product/pdx201/vendor_boot.img
Sending 'boot_b' (65536 KB) OKAY [ 2.536s]
Writing 'boot_b' OKAY [ 0.359s]
Finished. Total time: 2.914s
Sending 'vbmeta' (8 KB) OKAY [ 0.010s]
Writing 'vbmeta' OKAY [ 0.004s]
Finished. Total time: 0.023s
Sending 'dtbo' (8192 KB) OKAY [ 0.333s]
Writing 'dtbo' OKAY [ 0.046s]
Finished. Total time: 0.386s
Sending 'recovery' (98304 KB) OKAY [ 3.829s]
Writing 'recovery' OKAY [ 0.556s]
Finished. Total time: 4.393s
Sending sparse 'system' 1/2 (720896 KB) OKAY [ 26.695s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vendor' (106548 KB) OKAY [ 3.633s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'userdata' (544 KB) OKAY [ 0.027s]
Writing 'userdata' OKAY [ 0.003s]
Finished. Total time: 0.049s
Sending 'product' (277340 KB) OKAY [ 10.426s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta_system' (4 KB) OKAY [ 0.011s]
Writing 'vbmeta_system' OKAY [ 0.004s]
Finished. Total time: 0.023s
fastboot: error: cannot load 'out/target/product/pdx201/system_ext.img': No such file or directory
fastboot: error: cannot load 'out/target/product/pdx201/vendor_boot.img': No such file or directory
❯ fastboot erase metadata
******** Did you mean to fastboot format this ext4 partition?
Erasing 'metadata' FAILED (remote: 'Erasing is not allowed for partition
')
fastboot: error: Command failed
❯ fastboot flash system out/target/product/pdx201/system.img
fastboot flash vendor out/target/product/pdx201/vendor.img
fastboot flash product out/target/product/pdx201/product.img
Resizing 'system_b' OKAY [ 0.007s]
Sending sparse 'system_b' 1/6 (262140 KB) OKAY [ 10.396s]
Writing 'system_b' OKAY [ 1.635s]
Sending sparse 'system_b' 2/6 (262140 KB) OKAY [ 10.775s]
Writing 'system_b' OKAY [ 1.620s]
Sending sparse 'system_b' 3/6 (262140 KB) OKAY [ 10.727s]
Writing 'system_b' OKAY [ 1.612s]
Sending sparse 'system_b' 4/6 (262140 KB) OKAY [ 10.830s]
Writing 'system_b' OKAY [ 1.606s]
Sending sparse 'system_b' 5/6 (262140 KB) OKAY [ 10.730s]
Writing 'system_b' OKAY [ 1.613s]
Sending sparse 'system_b' 6/6 (58300 KB) OKAY [ 2.414s]
Writing 'system_b' OKAY [ 0.414s]
Finished. Total time: 64.444s
Resizing 'vendor_b' OKAY [ 0.019s]
Sending 'vendor_b' (106548 KB) OKAY [ 4.299s]
Writing 'vendor_b' OKAY [ 0.742s]
Finished. Total time: 5.090s
Resizing 'product_b' OKAY [ 0.046s]
Sending sparse 'product_b' 1/2 (262140 KB) OKAY [ 10.504s]
Writing 'product_b' OKAY [ 1.617s]
Sending sparse 'product_b' 2/2 (15200 KB) OKAY [ 0.628s]
Writing 'product_b' OKAY [ 0.176s]
Finished. Total time: 13.001s

jerpelea said:
I am investigating the issue caused by the latest kernel updates
please use an older prebuilt kernel
Click to expand...
Click to collapse
Is there any progress on this issue? I'd like to build Android 13 but don't want to begin if there are major problems.

The major issue is actually NOT the bootloader bug, but on the open devices project for this phone audio is... Well unusable, because it doesn't work. Just Google sailfish os no sound and you will see the details. (I know sailfish os is a Linux distro but they use the SODP source code)

I think being unable to boot is a more important issue than no sound. I'd really like to hear about any progress on simply building Android 13 for this device. I contacted Sony last week and they confirmed to me that my Xperia 10 II will not bet getting any more patches or upgrades, and the last one was over 5 months ago, so I'm very interested in successfully building AOSP for myself.

Yes, that makes sense, but for some reason (from what i can tell from the logcat) it just doesnt find a lot of the apks required to boot up.

KingProNoob2 said:
Yes, that makes sense, but for some reason (from what i can tell from the logcat) it just doesnt find a lot of the apks required to boot up.
Click to expand...
Click to collapse
I build the Android 13 and there is no apk missing for this device
did you flash all partititons accoring to the guide?

Yes i did, but i am not the best in reviewing logcats, i will send it here in a few moments.

logcat.txt
drive.google.com

How To Guide [STABLE/STOCK/GSI - Android 13] Redmi Note 10 5G (camellian) + Magisk (NO TWRP)

How to flash Google/Pixel Stock Stable Android 13 on Xiaomi Redmi Note 10 5G (in my case camellian) from any MIUI or any GSI rom without custom recoveries:
Download stock (original/unmodified) boot.img from your current MIUI Version
Download LATEST platform-tools (ADB + FASTBOOT) from Google
Download Magisk (in my case Alpha version works best on newer Androids)
Download Android 13 (stable) GSI (ARM64+GMS - Gapps version) from Google:
-- ARM64 without GMS (Gapps) also works, but upon installing Gapps manually I've gotten Bootloops (I tried serveral versions & Magisk Flashable too)
-- After downloading the GSI, extract system.img (you will be flashing this image) and vbmeta.img (and this image)
{
"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"
}
Place stock boot.img with downloaded system.img and vbmeta.img in the platform-tools folder
Run CMD in platform-tools folder (by typing CMD in address bar and hitting ENTER) and connect your phone (OFC enable USB debugging)
Run following adb / fastboot commands:
Boot phone in fastbootD (important)
Code:
C:\adb\platform-tools>adb reboot bootloader
C:\adb\platform-tools>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
Finished. Total time: 12.820s
When booted in fastbootD run:
Code:
C:\adb\platform-tools>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.022s]
Finished. Total time: 0.028s
C:\adb\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_a' OKAY [ 0.006s]
Finished. Total time: 0.050s
C:\adb\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.044s
C:\adb\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
Finished. Total time: 0.043s
C:\adb\platform-tools>fastboot flash system system.img
Resizing 'system_a' OKAY [ 0.014s]
Sending sparse 'system_a' 1/12 (262108 KB) OKAY [ 10.316s]
Writing 'system_a' OKAY [ 1.183s]
Sending sparse 'system_a' 2/12 (262120 KB) OKAY [ 10.677s]
Writing 'system_a' OKAY [ 1.087s]
Sending sparse 'system_a' 3/12 (262104 KB) OKAY [ 10.270s]
Writing 'system_a' OKAY [ 0.953s]
Sending sparse 'system_a' 4/12 (262124 KB) OKAY [ 10.131s]
Writing 'system_a' OKAY [ 1.040s]
Sending sparse 'system_a' 5/12 (262124 KB) OKAY [ 10.749s]
Writing 'system_a' OKAY [ 1.083s]
Sending sparse 'system_a' 6/12 (262124 KB) OKAY [ 11.126s]
Writing 'system_a' OKAY [ 1.082s]
Sending sparse 'system_a' 7/12 (262124 KB) OKAY [ 10.528s]
Writing 'system_a' OKAY [ 1.045s]
Sending sparse 'system_a' 8/12 (262128 KB) OKAY [ 10.397s]
Writing 'system_a' OKAY [ 0.947s]
Sending sparse 'system_a' 9/12 (262088 KB) OKAY [ 10.333s]
Writing 'system_a' OKAY [ 1.207s]
Sending sparse 'system_a' 10/12 (262120 KB) OKAY [ 10.717s]
Writing 'system_a' OKAY [ 1.027s]
Sending sparse 'system_a' 11/12 (243488 KB) OKAY [ 9.380s]
Writing 'system_a' OKAY [ 1.433s]
Sending sparse 'system_a' 12/12 (46444 KB) OKAY [ 1.797s]
Writing 'system_a' OKAY [ 0.336s]
Finished. Total time: 139.687s
C:\adb\platform-tools>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.486s]
Writing 'boot_a' OKAY [ 0.337s]
Finished. Total time: 2.858s
C:\adb\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.340s]
Writing 'boot_a' OKAY [ 0.314s]
Finished. Total time: 2.690s
C:\adb\platform-tools>fastboot flash boot_b boot.img
Sending 'boot_b' (65536 KB) OKAY [ 2.321s]
Writing 'boot_b' OKAY [ 0.317s]
Finished. Total time: 2.671s
Now Reboot to Recovery and WIPE DATA
Code:
C:\adb\platform-tools>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.007s
Reboot and done!
My opinion after one day:
If u like alot of customization it's not for you, you have to install even most basic apps let it's completly stock. But battery life is improved by 35-50% !! I'm using it for over 15 hours and still 30% battery left. Google Cam works great. Performance amazing. Few bugs here and there in the UI but overall pretty stable.
Anyway not a daily driver for everyone yet, needs a bit more polish. Enjoy !!

This looks good. Will it work for camellia?
If u like alot of customization it's not for you, you have to install even most basic apps let it's completly stock.
Click to expand...
Click to collapse
That's the reason I'm still on MIUI. Small things like network speed in status bar is very important to me.

sajalkmr said:
This looks good. Will it work for camellia?
That's the reason I'm still on MIUI. Small things like network speed in status bar is very important to me.
Click to expand...
Click to collapse
I am not sure as I don't have one to test it on, but I don't see why it wouldn't; all other GSI's work so. .
Have in mind that it looks good because of the Lawnchair Launcher (god bless the developer of it, i'm using it over 5 years), otherwise you will get the most basic stock functional android quickstep launcher.

Nice wallpaper. Can you share where I can find it?

iijul said:
Nice wallpaper. Can you share where I can find it?
Click to expand...
Click to collapse
Reddit - Dive into anything
www.reddit.com

iijul said:
Nice wallpaper. Can you share where I can find it?
Click to expand...
Click to collapse
Credit to Mia

What about NFC and Bluetooth working or not?

Kubusi3kk said:
What about NFC and Bluetooth working or not?
Click to expand...
Click to collapse
Yep

Hi,
I just tried this procedure with the latest beta build (Android 13 QPR1 BETA) and it does not boot (it restarts by itself every 30s), I switched back to Lineage OS 19.1
Am I the only one having this problem?
Thanks

doesnt work cannot make calls

NewXiaomiUser said:
Hi,
I just tried this procedure with the latest beta build (Android 13 QPR1 BETA) and it does not boot (it restarts by itself every 30s), I switched back to Lineage OS 19.1
Am I the only one having this problem?
Thanks
Click to expand...
Click to collapse
im having the same problem, can you link me a guide to installing los 19.1?

log:
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot devices
dafi8dfurkmz9dau fastboot
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.008s]
Finished. Total time: 0.009s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.130s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_ "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Sending 'vbmeta_' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_ "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Sending 'vbmeta_' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_a "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.013s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_b "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
Finished. Total time: 0.013s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot flash system "H:\platform-tools_r33.0.3-windows\platform-tools\system.img"
Resizing 'system_a' OKAY [ 0.010s]
Sending sparse 'system_a' 1/12 (262112 KB) OKAY [ 10.126s]
Writing 'system_a' OKAY [ 1.159s]
Sending sparse 'system_a' 2/12 (262120 KB) OKAY [ 9.476s]
Writing 'system_a' OKAY [ 1.118s]
Sending sparse 'system_a' 3/12 (262112 KB) OKAY [ 9.404s]
Writing 'system_a' OKAY [ 1.213s]
Sending sparse 'system_a' 4/12 (262124 KB) OKAY [ 10.100s]
Writing 'system_a' OKAY [ 1.080s]
Sending sparse 'system_a' 5/12 (262128 KB) OKAY [ 9.308s]
Writing 'system_a' OKAY [ 1.295s]
Sending sparse 'system_a' 6/12 (262124 KB) OKAY [ 9.395s]
Writing 'system_a' OKAY [ 1.147s]
Sending sparse 'system_a' 7/12 (262128 KB) OKAY [ 9.416s]
Writing 'system_a' OKAY [ 1.049s]
Sending sparse 'system_a' 8/12 (262120 KB) OKAY [ 9.430s]
Writing 'system_a' OKAY [ 1.260s]
Sending sparse 'system_a' 9/12 (262088 KB) OKAY [ 10.616s]
Writing 'system_a' OKAY [ 1.113s]
Sending sparse 'system_a' 10/12 (262120 KB) OKAY [ 9.648s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 11/12 (260716 KB) OKAY [ 9.342s]
Writing 'system_a' OKAY [ 1.360s]
Sending sparse 'system_a' 12/12 (46712 KB) OKAY [ 1.690s]
Writing 'system_a' OKAY [ 0.308s]
Finished. Total time: 196.646s
H:\platform-tools_r33.0.3-windows\platform-tools>
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot "H:\platform-tools_r33.0.3-windows\platform-tools\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.401s]
Writing 'boot_a' OKAY [ 0.316s]
Finished. Total time: 2.746s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot_a "H:\platform-tools_r33.0.3-windows\platform-tools\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.414s]
Writing 'boot_a' OKAY [ 0.308s]
Finished. Total time: 2.747s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot_b "H:\platform-tools_r33.0.3-windows\platform-tools\boot.img"
Sending 'boot_b' (65536 KB) OKAY [ 2.429s]
Writing 'boot_b' OKAY [ 0.309s]
Finished. Total time: 2.764s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.002s
H:\platform-tools_r33.0.3-windows\platform-tools>

Hi TedFin,
sure, here is how I flash back LineageOS 19.1:
First of all, I assume you have the ADB and fastboot drivers installed, you can find guides here and there.
Download LineageOS here:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.img.xz/download
Download stock firmware here:
https://xiaomifirmwareupdater.com/miui/camellian/stable/V13.0.3.0.SKSEUXM/ (choose Fastboot rom)
Extract the Xiaomi stock firware using 7zip or any other compatible software
Reboot your phone in fastboot mode (long press on volume down while booting)
Open a command prompt on the extracted folder and run
Bash:
flash_all.bat
Once completed, your phone should be back on stock rom
Reboot once again in fastboot mode
Then in cmd:
Go to the LineageOS folder
Bash:
cd /d [the folder where you decompressed lineageos]
Reboot in fastbootd
Bash:
fastboot reboot fastboot
Flash LineageOS
Bash:
fastboot flash system lineage-19.1-20220912-UNOFFICIAL-arm64_bgS.img
fastboot flash system_b lineage-19.1-20220912-UNOFFICIAL-arm64_bgS.img
Clean up
Bash:
fastboot reboot recovery
Wipe all then reboot
If you have a boot loop, reboot in Fastboot
Bash:
fastboot flash boot [the stock rom folder]\images\boot.img
fastboot flash boot_b [the stock rom folder]\images\boot.img
Voila!

NewXiaomiUser said:
Hi,
I just tried this procedure with the latest beta build (Android 13 QPR1 BETA) and it does not boot (it restarts by itself every 30s), I switched back to Lineage OS 19.1
Am I the only one having this problem?
Thanks
Click to expand...
Click to collapse
Do you wipe data at the end before reboot?

Hi, thanks for your response,
yes I did it, I also restore the stock firmware before but it does not change anything

NewXiaomiUser said:
Hi, thanks for your response,
yes I did it, I also restore the stock firmware before but it does not change anything
Click to expand...
Click to collapse
try nother gsi. a question: what stock firmware u have installed? i must start from miui13 because have a12 vendor
second. check the active slot. gsi must be installed into primary
third: flash system without erase system partition
forth: reflash boot stock img before reboot
if your phone dont boot and stuck on logo the problem is boot.img or active slot
if your phone boot into recovery wipe data
the bootloops after flashing gsi are caused by boot.img or data that must be wiped
another thing: FLASH VBMETA DISABLING SECURE VERITY CHECK before reboot
the steps for flash gsi are simply. slect the correct gsi and start from the correct stock is important. mut most important is use your brain. i have flashed at lest 5-6 gsi without problems

Hi,
1. Here is the stock ROM I'm using: camellian_eea_global V13.0.2.0 (SKSEUXM)
2. Active slot is A (anyway, I always flash A and B)
3. System partition is erased when flash stock rom. I do not flash after stock
4. I always flash boot (both A and B) after flashing a GSI, tried with stock boot.img and Magisk's
5. After installing a GSI, I always wipe all data in recovery mode
6. flashing vbmeta is part of your process and, of course, I followed it step by step
The phone is not stuck on logo, it just keep restarting again and again without reaching the OS itself (no boot animation)
By the way, I'm able to flash LineageOS or Pixel Experience using the same procedure works without any quirks, this is the only GSI I'm having problem with.
Thanks

NewXiaomiUser said:
Hi,
1. Here is the stock ROM I'm using: camellian_eea_global V13.0.2.0 (SKSEUXM)
2. Active slot is A (anyway, I always flash A and B)
3. System partition is erased when flash stock rom. I do not flash after stock
4. I always flash boot (both A and B) after flashing a GSI, tried with stock boot.img and Magisk's
5. After installing a GSI, I always wipe all data in recovery mode
6. flashing vbmeta is part of your process and, of course, I followed it step by step
The phone is not stuck on logo, it just keep restarting again and again without reaching the OS itself (no boot animation)
By the way, I'm able to flash LineageOS or Pixel Experience using the same procedure works without any quirks, this is the only GSI I'm having problem with.
Thanks
Click to expand...
Click to collapse
I'll try to give you files and help you when I get on my PC today

Sure, no rush, anyway, LOS is pretty stable except I cannot bypass SafetyNet.
Thanks

NewXiaomiUser said:
Sure, no rush, anyway, LOS is pretty stable except I cannot bypass SafetyNet.
Thanks
Click to expand...
Click to collapse
Sorry I forgot about my post, I'll do it now... As for the Safety Net I highly recommend using Alpha (not official) build of Magisk (pay attention to other builds such as Delta and similar "Alpha" builds everywhere; this Telegram Group link is the one and only trusted place where you can find download link-I'll attach latest version down bellow). Every single problem I had with either stock or modified roms; I solved them when I started using it (except when I overdo it with modules which would be my mistake ofc.). The biggest difference is that it is closed-sourced so there is a risk when using it, but it's being maintained by one of the respected people that worked/works on official Magisk.
Next step is of course installing Universal SafetyNet Fix by kdrag0n.
And finally MagiskHide Props Config By Didgeridoohan. After flashing this one you will have to set it up with any terminal (Termux for example) to spoof your device config so the store thinks you're using - in my case Google Pixel 6 Pro. Also in my case the feature "device emulator - 3rd from above" gave me soft brick so be careful. It's easy to set it up as it guides you via terminal (I use first two options and spoofing as Pixel 6 Pro as I said).
Those things are first things I do on a new rom, and yeah I use LSPosed Framework + Zygisk.
No problems and I'm certified in Google Play/Google Games stores even tho I use modified apks to hack multiplayer games.
I'll go and give you all the files so u can try latest generic GSI by Google if you still want, using this guide.