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.
Related
Hello there. I need some urgente help here.
I was trying to update my Mi A2 flashing some images on fastboot, and the following happened:
Code:
PS D:\ADB Fastboot\platform-tools> .\fastboot flash devcfg_a devcfg.img
>> .\fastboot flash devcfg_b devcfg.img
>>
>> .\fastboot flash dsp_a dsp.img
>> .\fastboot flash dsp_b dsp.img
>>
>> .\fastboot flash modem_a modem.img
>> .\fastboot flash modem_b modem.img
>>
>> .\fastboot flash rpm_a rpm.img
>> .\fastboot flash rpm_b rpm.img
>>
>> .\fastboot flash tz_a tz.img
>> .\fastboot flash tz_b tz.img
>>
>> .\fastboot flash keymaster_a keymaster.img
>> .\fastboot flash keymaster_b keymaster.img
>>
>> .\fastboot flash cmnlib64_a cmnlib64.img
>> .\fastboot flash cmnlib64_b cmnlib64.img
>>
>> .\fastboot flash cmnlib_a cmnlib.img
>> .\fastboot flash cmnlib_b cmnlib.img
>>
>> .\fastboot flash boot_a boot.img
>> .\fastboot flash boot_b boot.img
>>
>> .\fastboot flash system_a system.img
>> .\fastboot flash system_b system.img
>>
>> .\fastboot flash vendor_a vendor.img
>> .\fastboot flash vendor_b vendor.img
>>
>> .\fastboot flash mdtp_a mdtp.img
>> .\fastboot flash mdtp_b mdtp.img
>>
>> .\fastboot flash aboot_a aboot.img
>> .\fastboot flash aboot_b aboot.img
>>
>> .zfastboot flash sbl1_a sbl1.img
>> .\fastboot flash sbl1_b sbl1.img
Sending 'devcfg_a' (40 KB) OKAY [ 0.008s]
Writing 'devcfg_a' OKAY [ 0.005s]
Finished. Total time: 0.018s
Sending 'devcfg_b' (40 KB) OKAY [ 0.008s]
Writing 'devcfg_b' OKAY [ 0.003s]
Finished. Total time: 0.018s
Sending 'dsp_a' (16384 KB) OKAY [ 0.625s]
Writing 'dsp_a' OKAY [ 0.004s]
Finished. Total time: 0.659s
Sending 'dsp_b' (16384 KB) OKAY [ 0.545s]
Writing 'dsp_b' OKAY [ 0.004s]
Finished. Total time: 0.555s
Sending 'modem_a' (131072 KB) OKAY [ 4.949s]
Writing 'modem_a' OKAY [ 0.003s]
Finished. Total time: 4.993s
Sending 'modem_b' (131072 KB) OKAY [ 4.329s]
Writing 'modem_b' OKAY [ 0.005s]
Finished. Total time: 4.338s
Sending 'rpm_a' (172 KB) OKAY [ 0.018s]
Writing 'rpm_a' OKAY [ 0.004s]
Finished. Total time: 0.042s
Sending 'rpm_b' (172 KB) OKAY [ 0.012s]
Writing 'rpm_b' OKAY [ 0.003s]
Finished. Total time: 0.021s
Sending 'tz_a' (1500 KB) OKAY [ 0.070s]
Writing 'tz_a' OKAY [ 0.004s]
Finished. Total time: 0.101s
Sending 'tz_b' (1500 KB) OKAY [ 0.060s]
Writing 'tz_b' OKAY [ 0.004s]
Finished. Total time: 0.070s
Sending 'keymaster_a' (268 KB) OKAY [ 0.024s]
Writing 'keymaster_a' OKAY [ 0.004s]
Finished. Total time: 0.038s
Sending 'keymaster_b' (268 KB) OKAY [ 0.018s]
Writing 'keymaster_b' OKAY [ 0.004s]
Finished. Total time: 0.027s
Sending 'cmnlib64_a' (264 KB) OKAY [ 0.014s]
Writing 'cmnlib64_a' OKAY [ 0.005s]
Finished. Total time: 0.039s
Sending 'cmnlib64_b' (264 KB) OKAY [ 0.017s]
Writing 'cmnlib64_b' OKAY [ 0.004s]
Finished. Total time: 0.027s
Sending 'cmnlib_a' (212 KB) OKAY [ 0.011s]
Writing 'cmnlib_a' OKAY [ 0.004s]
Finished. Total time: 0.027s
Sending 'cmnlib_b' (212 KB) OKAY [ 0.015s]
Writing 'cmnlib_b' OKAY [ 0.004s]
Finished. Total time: 0.025s
Sending 'boot_a' (27220 KB) OKAY [ 1.050s]
Writing 'boot_a' OKAY [ 0.004s]
Finished. Total time: 1.085s
Sending 'boot_b' (27220 KB) OKAY [ 1.137s]
Writing 'boot_b' OKAY [ 0.003s]
Finished. Total time: 1.145s
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 18.973s]
Writing sparse 'system_a' 1/4 OKAY [ 0.013s]
Sending sparse 'system_a' 2/4 (524284 KB) OKAY [ 21.103s]
Writing sparse 'system_a' 2/4 OKAY [ 0.005s]
Sending sparse 'system_a' 3/4 (487210 KB) OKAY [ 19.443s]
Writing sparse 'system_a' 3/4 OKAY [ 0.003s]
Sending sparse 'system_a' 4/4 (470645 KB) OKAY [ 22.815s]
Writing sparse 'system_a' 4/4 OKAY [ 0.004s]
Finished. Total time: 123.482s
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/4 (524284 KB) OKAY [ 19.237s]
Writing sparse 'system_b' 1/4 OKAY [ 0.003s]
Sending sparse 'system_b' 2/4 (524284 KB) OKAY [ 22.565s]
Writing sparse 'system_b' 2/4 OKAY [ 0.003s]
Sending sparse 'system_b' 3/4 (487210 KB) OKAY [ 18.924s]
Writing sparse 'system_b' 3/4 OKAY [ 0.003s]
Sending sparse 'system_b' 4/4 (470645 KB) OKAY [ 18.155s]
Writing sparse 'system_b' 4/4 OKAY [ 0.003s]
Finished. Total time: 228.714s
Invalid sparse file format at header magic
Sending sparse 'vendor_a' 1/2 (513365 KB) OKAY [ 18.165s]
Writing sparse 'vendor_a' 1/2 OKAY [ 0.003s]
Sending sparse 'vendor_a' 2/2 (43596 KB) OKAY [ 8.365s]
Writing sparse 'vendor_a' 2/2 OKAY [ 0.003s]
Finished. Total time: 160.975s
Invalid sparse file format at header magic
Sending sparse 'vendor_b' 1/2 (513365 KB) OKAY [ 18.292s]
Writing sparse 'vendor_b' 1/2 OKAY [ 0.004s]
Sending sparse 'vendor_b' 2/2 (43596 KB) OKAY [ 9.543s]
Writing sparse 'vendor_b' 2/2 OKAY [ 0.003s]
Finished. Total time: 82.975s
Sending 'mdtp_a' (17392 KB) OKAY [ 0.711s]
Writing 'mdtp_a' OKAY [ 0.005s]
Finished. Total time: 44.537s
Sending 'mdtp_b' (17392 KB) OKAY [ 0.675s]
Writing 'mdtp_b' OKAY [ 0.004s]
Finished. Total time: 0.685s
Sending 'aboot_a' (672 KB) OKAY [ 0.055s]
Writing 'aboot_a' OKAY [ 0.005s]
Finished. Total time: 0.152s
Sending 'aboot_b' (672 KB) FAILED (remote: 'No such partition.')
Finished. Total time: 0.009s
.zfastboot : O termo '.zfastboot' não é reconhecido como nome de cmdlet, função, arquivo de script ou programa
operável. Verifique a grafia do nome ou, se um caminho tiver sido incluído, veja se o caminho está correto e tente
novamente.
No linha:40 caractere:1
+ .zfastboot flash sbl1_a sbl1.img
+ ~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (.zfastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Sending 'sbl1_b' (396 KB) OKAY [ 0.028s]
Writing 'sbl1_b' OKAY [ 0.003s]
Finished. Total time: 0.080s
PS D:\ADB Fastboot\platform-tools> .\fastboot reboot
Rebooting
Finished. Total time: 0.005s
I pasted everything so maybe someone can find some error and help me out.
After I hit reboot, the phone flashed and I immediately disconnected USB cable. Was it the problem?
Now it won't turn on, and won't even light on the led indicator, as if it is not even charging.
I need some URGENT help.
Click to expand...
Click to collapse
SOLVED.
How to do it, in case you find yourself in the same situation:
1- Download and extract twice stock ROMfrom xiaomi official website.
-(first extract the .tgz file, which will give you a .tar file. Then extract the .tar)
2- Download and install Qualcomm HS-USB 9008 driver.
3- Download and install Mi Flash Tool.
4- Open Mi Flash tool
4.1 - "select" the folder extracted from what you downloaded as Stock ROM. Should be like this: D:\Mi A2 ROM\jasmine_global_images_V9.6.16.0.ODIMIFE_8.1
4.2- hit "refresh".
4.3- hit "flash". Mi flash should recognize device as "COM3".
4.4- Wait until finished and power on device.
Smile.
Look at how many typos you have
What is aboot_a?
What is zfastboot?
Nebrassy said:
Look at how many typos you have
What is aboot_a?
What is zfastboot?
Click to expand...
Click to collapse
Yeah... mistyping on that .zfastboot. Meant to be .\fastboot. That was surely an error I hadn't even seen.
But before that, aboot_b.img failed to be flashed on the device. That code line was copied from a post here on XDA, one which I'm not having much success on finding it again.
Well, anyways, my computer recognized the device only as Qualcomm HS-USB 9008 (COM3). I managed to install a qualcomm driver.
After that, I installed Mi Flash Tool, which was able to identify the Qualcomm device (something that fastboot wouldn't do).
Following that, I download stock ROM from Xiaomi official website, on .tgz format. Extracted it twice until I got the images folder.
I disabled integrity check function on windows 10, restarted my PC.
Opened Mi Flash Tool, selected the folder which contained the stock ROM images, refreshed the software to recognize the qualcomm on COM3, and hit flash.
It worked! It's been a few seconds since I managed to turn my phone on again. I'm configuring and installing my most used apps right now.
It's boot_a and boot_b, there is no aboot_b partition
Nebrassy said:
It's boot_a and boot_b, there is no aboot_b partition
Click to expand...
Click to collapse
I just download the folder and ran the code (almost) exactly as estated on the topic I read here. I just added the "." because I was running it on powershell, not cmd.
But... I get what you're saying. It totally makes sense, but what about the following lines?
Code:
Sending 'aboot_a' (672 KB) OKAY [ 0.055s]
Writing 'aboot_a' OKAY [ 0.005s]
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?
Hi,
I'm getting an error trying to install stock rom from xiaomirom.com via fastboot.
Code:
D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea\images/super.img ||
Sending sparse 'super' 1/10 (754376 KB) OKAY [ 17.399s]
Writing 'super' OKAY [ 0.006s]
Sending sparse 'super' 2/10 (785128 KB) OKAY [ 18.135s]
Writing 'super' OKAY [ 18.411s]
Sending sparse 'super' 3/10 (754660 KB) OKAY [ 17.565s]
Writing 'super' OKAY [ 19.702s]
Sending sparse 'super' 4/10 (738992 KB) OKAY [ 17.297s]
Writing 'super' OKAY [ 19.035s]
Sending sparse 'super' 5/10 (750936 KB) OKAY [ 17.450s]
Writing 'super' OKAY [ 20.112s]
Sending sparse 'super' 6/10 (720896 KB) OKAY [ 17.004s]
Writing 'super' OKAY [ 23.257s]
Sending sparse 'super' 7/10 (737084 KB) OKAY [ 17.226s]
Writing 'super' FAILED (remote: 'failed to check sparse crc')
fastboot: error: Command failed
"Flash super error"
It's consistently crashing on 7/10 or 7/11 (depending on chosen MIUI version).
I tried multiple MIUI versions (12.5/13 Europe/Global) and fastboot versions (Xiaomi/Google)
Sometimes fastboot stops responding and I have to reconnect/restart my phone.
Did anyone encounter a similar problem or am I on my own?
SOLUTION:
For me, problem was fastboot itself. Using fastboot from xiaomi.eu distribution solved my problem with flashing stock MIUI.
I attached zip with working fastboot for convenience but you can get it with any xiaomi.eu rom zip.
Cubiss said:
Hi,
I'm getting an error trying to install stock rom from xiaomirom.com via fastboot.
Code:
D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea\images/super.img ||
Sending sparse 'super' 1/10 (754376 KB) OKAY [ 17.399s]
Writing 'super' OKAY [ 0.006s]
Sending sparse 'super' 2/10 (785128 KB) OKAY [ 18.135s]
Writing 'super' OKAY [ 18.411s]
Sending sparse 'super' 3/10 (754660 KB) OKAY [ 17.565s]
Writing 'super' OKAY [ 19.702s]
Sending sparse 'super' 4/10 (738992 KB) OKAY [ 17.297s]
Writing 'super' OKAY [ 19.035s]
Sending sparse 'super' 5/10 (750936 KB) OKAY [ 17.450s]
Writing 'super' OKAY [ 20.112s]
Sending sparse 'super' 6/10 (720896 KB) OKAY [ 17.004s]
Writing 'super' OKAY [ 23.257s]
Sending sparse 'super' 7/10 (737084 KB) OKAY [ 17.226s]
Writing 'super' FAILED (remote: 'failed to check sparse crc')
fastboot: error: Command failed
"Flash super error"
I tried multiple It's consistently crashing on 7/10 or 7/11 (depending on chosen MIUI version).
I tried multiple MIUI versions (12.5/13 Europe/Global) and fastboot versions (Xiaomi/Google)
Sometimes fastboot stops responding and I have to reconnect/restart my phone.
Did anyone encounter a similar problem or am I on my own?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/error-failed-remote-update-sparse-crc-list-failed.4265453/
NOSS8 said:
https://forum.xda-developers.com/t/error-failed-remote-update-sparse-crc-list-failed.4265453/
Click to expand...
Click to collapse
Every google attempt lead me to this. Sadly it's a not the same error (flashing 'sparsecrclist'). I'm getting a different error when flashing 'super'.
I tried removing the sparsecrclist flashing line but sadly it doesn't change anything.
I even tried to edit sparsecrclist.txt (empty file, just header, remove line specific for super partition), but everything fails at a different spot.
Cubiss said:
Every google attempt lead me to this. Sadly it's a not the same error (flashing 'sparsecrclist'). I'm getting a different error when flashing 'super'.
I tried removing the sparsecrclist flashing line but sadly it doesn't change anything.
I even tried to edit sparsecrclist.txt (empty file, just header, remove line specific for super partition), but everything fails at a different spot.
Click to expand...
Click to collapse
try https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
and post the Miflash log.
Cubiss said:
Hi,
I'm getting an error trying to install stock rom from xiaomirom.com via fastboot.
Code:
D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea\images/super.img ||
Sending sparse 'super' 1/10 (754376 KB) OKAY [ 17.399s]
Writing 'super' OKAY [ 0.006s]
Sending sparse 'super' 2/10 (785128 KB) OKAY [ 18.135s]
Writing 'super' OKAY [ 18.411s]
Sending sparse 'super' 3/10 (754660 KB) OKAY [ 17.565s]
Writing 'super' OKAY [ 19.702s]
Sending sparse 'super' 4/10 (738992 KB) OKAY [ 17.297s]
Writing 'super' OKAY [ 19.035s]
Sending sparse 'super' 5/10 (750936 KB) OKAY [ 17.450s]
Writing 'super' OKAY [ 20.112s]
Sending sparse 'super' 6/10 (720896 KB) OKAY [ 17.004s]
Writing 'super' OKAY [ 23.257s]
Sending sparse 'super' 7/10 (737084 KB) OKAY [ 17.226s]
Writing 'super' FAILED (remote: 'failed to check sparse crc')
fastboot: error: Command failed
"Flash super error"
It's consistently crashing on 7/10 or 7/11 (depending on chosen MIUI version).
I tried multiple MIUI versions (12.5/13 Europe/Global) and fastboot versions (Xiaomi/Google)
Sometimes fastboot stops responding and I have to reconnect/restart my phone.
Did anyone encounter a similar problem or am I on my own?
Click to expand...
Click to collapse
i got same type error with both stock rom MIUI versions 12.5/13, when flashed MiMix rom no error phone started normally.
Have a look.
MiuiMix V13.0.6.0 [MIUI 13] | Android 12
MiuiMix V13.0.2.0 [MIUI 13] | Android 12 It's based on Global EU 13 build Download: AFH | SF Flashing instructions All credits to MMX Team Follow MOD EDIT: Link Removed Update: MiuiMiX 13.0.3.0 Stable Download: AndroidFileHost | SourceForge...
forum.xda-developers.com
djkrish5610 said:
i got same type error with both stock rom MIUI versions 12.5/13, when flashed MiMix rom no error phone started normally.
Have a look.
MiuiMix V13.0.6.0 [MIUI 13] | Android 12
MiuiMix V13.0.2.0 [MIUI 13] | Android 12 It's based on Global EU 13 build Download: AFH | SF Flashing instructions All credits to MMX Team Follow MOD EDIT: Link Removed Update: MiuiMiX 13.0.3.0 Stable Download: AndroidFileHost | SourceForge...
forum.xda-developers.com
Click to expand...
Click to collapse
So I tried downloading the latest xiaomi.eu rom and it flashed fine.
The issue seems to be fixed using fastboot distributed with xiaomi.eu roms.
I managed to flash stock MIUI with it now, I'll try it again to check if it wasn't a fluke but if it goes through I'll edit the original post.
Cubiss said:
So I tried downloading the latest xiaomi.eu rom and it flashed fine.
The issue seems to be fixed using fastboot distributed with xiaomi.eu roms.
I managed to flash stock MIUI with it now, I'll try it again to check if it wasn't a fluke but if it goes through I'll edit the original post.
Click to expand...
Click to collapse
I used Miflash (2020-3-14-0 version) to go from the EEA version to the Global version without any problem.
NOSS8 said:
I used Miflash (2020-3-14-0 version) to go from the EEA version to the Global version without any problem.
Click to expand...
Click to collapse
I ran the script directly. Usually it's one click process but this time it got me good.
I tried using mi flash but it got stuck at the step where running the bath file crashes.
Cubiss said:
I ran the script directly. Usually it's one click process but this time it got me good.
I tried using mi flash but it got stuck at the step where running the bath file crashes.
Click to expand...
Click to collapse
The error you have may come from:
Files and Miflash are not installed at the root.
The File has too many characters (vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea) rename V125210 for example.
It comes from the configuration of the PC.
Usb port 3 instead of 2.
Try another version of Miflash.
NOSS8 said:
The error you have may come from:
Files and Miflash are not installed at the root.
The File has too many characters (vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea) rename V125210 for example.
It comes from the configuration of the PC.
Usb port 3 instead of 2.
Try another version of Miflash.
Click to expand...
Click to collapse
Thank you. I already solved it in the post above and edited the title and original post.
The error was caused by wrong version of fastboot.exe.
i want to go back to stock rom, which way i should i prefer ?
Indian rom gave me same super error, so i jumped on MMX rom to start phone atleast.
All good, but banking apps not working on MMX hence switch back on V12.5
djkrish5610 said:
i want to go back to stock rom, which way i should i prefer ?
Indian rom gave me same super error, so i jumped on MMX rom to start phone atleast.
All good, but banking apps not working on MMX hence switch back on V12.5Install
Click to expand...
Click to collapse
Install a XIAOMI EU ROM(play store certified)
https://forum.xda-developers.com/t/...t-pro-v13-0-2-0-skdmixm.4374297/post-86702043
NOSS8 said:
Install a XIAOMI EU ROM(play store certified)
https://forum.xda-developers.com/t/...t-pro-v13-0-2-0-skdmixm.4374297/post-86702043
Click to expand...
Click to collapse
How do i lock bootloader ??
As soon as i run this fastboot oem lock
Phone is getting locked, but boot looping a warning as the system has destroyed.
When trying to flash the OS Again, getting error as flashing not allowed in lock state
How do i go on stock mode.
djkrish5610 said:
How do i lock bootloader ??
As soon as i run this fastboot oem lock
Phone is getting locked, but boot looping a warning as the system has destroyed.
When trying to flash the OS Again, getting error as flashing not allowed in lock state
How do i go on stock mode.
Click to expand...
Click to collapse
You say you tried MMX rom, to install this rom the bootloader must be unlocked.
Did you flash a stock rom and lock the bootloader?
With this tool?https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
State exactly what you did.
Currently using MMX rom
Flashed New build V13.0.3.0.SKDMIXM as per ur recommendation (Bootloader is still unlocked)
I want to go completely back to stock rom, so tried to lock oem with fastboot mode (Failed with Error as bootloader got locked)
So Unlocked the phone by (MiUnlock)
As of now its on stock rom V13.0.3.0.SKDMIXM
djkrish5610 said:
Currently using MMX rom
Flashed New build V13.0.3.0.SKDMIXM as per ur recommendation (Bootloader is still unlocked)
I want to go completely back to stock rom, so tried to lock oem with fastboot mode (Failed with Error as bootloader got locked)
So Unlocked the phone by (MiUnlock)
As of now its on stock rom V13.0.3.0.SKDMIXM
Click to expand...
Click to collapse
To lock with Miflash check the "Clean all and lock" box instead of "Clean all".
No need to repeat the initial operation since it has already been unlocked.
Unlocked
Now you can use a XiAOMi EU ROM
Extract the zip rom
In fastboot mode use the update script bat or first install(data removed).
Cubiss said:
Hi,
I'm getting an error trying to install stock rom from xiaomirom.com via fastboot.
Code:
D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea\images/super.img ||
Sending sparse 'super' 1/10 (754376 KB) OKAY [ 17.399s]
Writing 'super' OKAY [ 0.006s]
Sending sparse 'super' 2/10 (785128 KB) OKAY [ 18.135s]
Writing 'super' OKAY [ 18.411s]
Sending sparse 'super' 3/10 (754660 KB) OKAY [ 17.565s]
Writing 'super' OKAY [ 19.702s]
Sending sparse 'super' 4/10 (738992 KB) OKAY [ 17.297s]
Writing 'super' OKAY [ 19.035s]
Sending sparse 'super' 5/10 (750936 KB) OKAY [ 17.450s]
Writing 'super' OKAY [ 20.112s]
Sending sparse 'super' 6/10 (720896 KB) OKAY [ 17.004s]
Writing 'super' OKAY [ 23.257s]
Sending sparse 'super' 7/10 (737084 KB) OKAY [ 17.226s]
Writing 'super' FAILED (remote: 'failed to check sparse crc')
fastboot: error: Command failed
"Flash super error"
It's consistently crashing on 7/10 or 7/11 (depending on chosen MIUI version).
I tried multiple MIUI versions (12.5/13 Europe/Global) and fastboot versions (Xiaomi/Google)
Sometimes fastboot stops responding and I have to reconnect/restart my phone.
Did anyone encounter a similar problem or am I on my own?
SOLUTION:
For me, problem was fastboot itself. Using fastboot from xiaomi.eu distribution solved my problem with flashing stock MIUI.
I attached zip with working fastboot for convenience but you can get it with any xiaomi.eu rom zip.
Click to expand...
Click to collapse
How do you use the fastboot.zip that you sourced from Xiaomi.eu? Where do you put it? How do you make Mi Flash tool interact with it?
RivaLCF said:
How do you use the fastboot.zip that you sourced from Xiaomi.eu? Where do you put it? How do you make Mi Flash tool interact with it?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...led-to-check-sparse-crc.4429745/post-86731713
Xiaomi eu rom not Xiaomi EEA rom
Cubiss said:
Hi,
I'm getting an error trying to install stock rom from xiaomirom.com via fastboot.
Code:
D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea\images/super.img ||
Sending sparse 'super' 1/10 (754376 KB) OKAY [ 17.399s]
Writing 'super' OKAY [ 0.006s]
Sending sparse 'super' 2/10 (785128 KB) OKAY [ 18.135s]
Writing 'super' OKAY [ 18.411s]
Sending sparse 'super' 3/10 (754660 KB) OKAY [ 17.565s]
Writing 'super' OKAY [ 19.702s]
Sending sparse 'super' 4/10 (738992 KB) OKAY [ 17.297s]
Writing 'super' OKAY [ 19.035s]
Sending sparse 'super' 5/10 (750936 KB) OKAY [ 17.450s]
Writing 'super' OKAY [ 20.112s]
Sending sparse 'super' 6/10 (720896 KB) OKAY [ 17.004s]
Writing 'super' OKAY [ 23.257s]
Sending sparse 'super' 7/10 (737084 KB) OKAY [ 17.226s]
Writing 'super' FAILED (remote: 'failed to check sparse crc')
fastboot: error: Command failed
"Flash super error"
It's consistently crashing on 7/10 or 7/11 (depending on chosen MIUI version).
I tried multiple MIUI versions (12.5/13 Europe/Global) and fastboot versions (Xiaomi/Google)
Sometimes fastboot stops responding and I have to reconnect/restart my phone.
Did anyone encounter a similar problem or am I on my own?
SOLUTION:
For me, problem was fastboot itself. Using fastboot from xiaomi.eu distribution solved my problem with flashing stock MIUI.
I attached zip with working fastboot for convenience but you can get it with any xiaomi.eu rom zip.
Click to expand...
Click to collapse
Any instruction on using this particular fast boot to flash stock miui? i am too getting same error
Cubiss said:
Every google attempt lead me to this. Sadly it's a not the same error (flashing 'sparsecrclist'). I'm getting a different error when flashing 'super'.
I tried removing the sparsecrclist flashing line but sadly it doesn't change anything.
I even tried to edit sparsecrclist.txt (empty file, just header, remove line specific for super partition), but everything fails at a different spot.
Click to expand...
Click to collapse
have you found a solution?
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)
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