Related
As the title says the stock slot was wiped on this Bionic. I have tried using BionicRestorer to fxz to 5.5.893 and 5.9.901 and it encountered a couple of errors. I'm not sure exactly what the mean though. The phone boots to the Moto logo, then the screen goes blank and the soft keys stay lit. Nothing else happens and I have to pull the battery. I tried booting into recovery mode but after selecting recovery I get the android laying on his back with a triangle/exclamation point above him.
I'm not sure what else I can do with this and would greatly appreciate some help. I do have a charger so I'm not worried about the battery getting low. I'm using Linux but do have access to Windows as well.
Here is the command line output from the BionicRestorer script:
Code:
Here we go, I don't stop on errors, once it starts there is no stopping
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.007s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbm allow-mbmloader-flashing-mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.023s]
writing 'mbm'... OKAY [ 0.453s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.006s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbmloader mbmloader.bin
sending 'mbmloader' (40 KB)... OKAY [ 0.009s]
writing 'mbmloader'... OKAY [ 0.289s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbm mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.024s]
writing 'mbm'... OKAY [ 0.451s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.006s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash cdt.bin cdt.bin
sending 'cdt.bin' (16 KB)... OKAY [ 0.007s]
writing 'cdt.bin'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux erase cache
erasing 'cache'... OKAY [ 0.012s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux erase userdata
erasing 'userdata'... OKAY [ 0.012s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash lbl lbl
sending 'lbl' (16 KB)... OKAY [ 0.007s]
writing 'lbl'... OKAY [ 0.428s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash logo.bin logo.bin
sending 'logo.bin' (854 KB)... OKAY [ 0.061s]
writing 'logo.bin'... OKAY [ 0.267s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash ebr ebr
sending 'ebr' (16 KB)... OKAY [ 0.008s]
writing 'ebr'... OKAY [ 0.428s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbr mbr
sending 'mbr' (16 KB)... OKAY [ 0.007s]
writing 'mbr'... OKAY [ 0.397s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash devtree device_tree.bin
sending 'devtree' (512 KB)... OKAY [ 0.041s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash system system.img
sending 'system' (262144 KB)... OKAY [ 16.514s]
writing 'system'... OKAY [ 21.258s]
sending 'system' (229120 KB)... OKAY [ 14.442s]
writing 'system'... OKAY [ 18.771s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.533s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash recovery recovery.img
sending 'recovery' (9216 KB)... OKAY [ 0.600s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash cdrom cdrom
sending 'cdrom' (12032 KB)... OKAY [ 0.771s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash preinstall preinstall.img
sending 'preinstall' (262144 KB)... OKAY [ 16.499s]
writing 'preinstall'... OKAY [ 22.208s]
sending 'preinstall' (49152 KB)... OKAY [ 3.106s]
writing 'preinstall'... OKAY [ 3.931s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash webtop grfs.img
sending 'webtop' (262144 KB)... OKAY [ 16.516s]
writing 'webtop'... OKAY [ 23.794s]
sending 'webtop' (262144 KB)... OKAY [ 16.515s]
writing 'webtop'... OKAY [ 23.305s]
sending 'webtop' (262144 KB)... OKAY [ 16.507s]
writing 'webtop'... OKAY [ 21.253s]
sending 'webtop' (262144 KB)... OKAY [ 16.521s]
writing 'webtop'... OKAY [ 22.130s]
sending 'webtop' (262144 KB)... OKAY [ 16.514s]
writing 'webtop'... OKAY [ 22.110s]
sending 'webtop' (54016 KB)... OKAY [ 3.408s]
writing 'webtop'... OKAY [ 5.240s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash radio radio.img
sending 'radio' (21768 KB)... OKAY [ 1.377s]
writing 'radio'... OKAY [ 3.805s]
I think I've tried flashing the wrong file in a mad case of Idon'tknowwhati'mdoingsoIshouldhaveleftittheheckalone. So I'm going to try flashing http://sbf.droid-developers.org/download.php?device=12&file=162 with RSD Lite as suggested in some other posts I've read today.
Well, You could try holding vol down before turning it on, That should get you to ap fastboot, then use rsd
Ryan11271 said:
Well, You could try holding vol down before turning it on, That should get you to ap fastboot, then use rsd
Click to expand...
Click to collapse
That's what I plan on doing. I can still get to recovery and ap fastboot mode. I'm going to d/l rsd now.
The biggest thing is that you cannot flash back to an earlier version than what had been installed. You can only flash the same version or newer.
How about this, I ordered a droid bionic, I'll root and put on safestrap, Once I do all that good stuff I'll make you a stock rom backup and send you the zip. I'll pm you when I get it
Probably doesn't have safestrap installed anymore, so a backup from safestrap wouldn't help.
Ohhh, I didn't think of that XD
Yeah I borked safestrap too but thanks for the offer though. I'm about to reboot into windows and try to rsd what I believe to be the correct version.
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]
We will flash the ubuntu touch boot image which is required temporarily. And the currently latest sfos build for the QX1050.
1. Download ubuntu touch build from here and extract the boot.img
Ubuntu for Pro¹ X build job 2830649718 artifact.zip
2. Download SailfishOS 4.4.0.64 build from here and extract the userdata.simg
SailfishOS for Pro¹ X job 2807435728 artifact.zip
3. Flash using fastboot
Code:
fastboot flash boot_a boot.img
fastboot flash userdata userdata.simg
4. Reboot using fastboot reboot or fastboot continue
Thanks for moving mods! Did not realize its more appropriate here in the guides section than in the development section.
fastboot flash userdata userdata.img
fastboot flash userdata userdata.simg Typo
Nope, the sailfish userdata is in sparse format. So its .simg correctly.
Thats why you will not have the infamous "Invalid sparse file format at header magic" message from fastboot when flashing that .simg. Since fastboot expects sparse images, but *****es about raw images like the ubuntu boot.img above.
Weird I'm getting this error
fastboot flash userdata userdata.simg
error: cannot load 'userdata.simg'
But this command works
fastboot flash userdata userdata.img
target reported max download size of 268435456 bytes
sending sparse 'userdata' (258052 KB)...
OKAY [ 7.558s]
writing 'userdata'...
OKAY [ 1.624s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.864s]
writing 'userdata'...
OKAY [ 1.656s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 8.295s]
writing 'userdata'...
OKAY [ 1.634s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.826s]
writing 'userdata'...
OKAY [ 1.583s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.828s]
writing 'userdata'...
OKAY [ 1.617s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.858s]
writing 'userdata'...
OKAY [ 1.681s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.751s]
writing 'userdata'...
OKAY [ 1.655s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.592s]
writing 'userdata'...
OKAY [ 1.694s]
sending sparse 'userdata' (147988 KB)...
OKAY [ 4.536s]
writing 'userdata'...
OKAY [ 0.971s]
finished. total time: 81.497s
It doesn't boot
bobnot said:
Weird I'm getting this error
fastboot flash userdata userdata.simg
error: cannot load 'userdata.simg'
But this command works
fastboot flash userdata userdata.img
target reported max download size of 268435456 bytes
sending sparse 'userdata' (258052 KB)...
OKAY [ 7.558s]
writing 'userdata'...
OKAY [ 1.624s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.864s]
writing 'userdata'...
OKAY [ 1.656s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 8.295s]
writing 'userdata'...
OKAY [ 1.634s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.826s]
writing 'userdata'...
OKAY [ 1.583s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.828s]
writing 'userdata'...
OKAY [ 1.617s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.858s]
writing 'userdata'...
OKAY [ 1.681s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.751s]
writing 'userdata'...
OKAY [ 1.655s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.592s]
writing 'userdata'...
OKAY [ 1.694s]
sending sparse 'userdata' (147988 KB)...
OKAY [ 4.536s]
writing 'userdata'...
OKAY [ 0.971s]
finished. total time: 81.497s
It doesn't boot
Click to expand...
Click to collapse
what version of the android platform tools are you using? I'm on r33.0.2 and "fastboot flash userdata userdata.simg" works just fine for me
Ah, i guess you are flashing the ubuntu image then?
For sailfish, we need only the boot.img from the first posted ubuntu artifacted.
But the userdata.simg from sailfish contained in the second artifact linked below.
eltmosen said:
Ah, i guess you are flashing the ubuntu image then?
For sailfish, we need only the boot.img from the first posted ubuntu artifacted.
But the userdata.simg from sailfish contained in the second artifact linked below.
Click to expand...
Click to collapse
Neither SFOS or UT will boot
I also updated to latest fastboot from googles source. Still same issue as previously stated.
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 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.