Related
I'm trying to flash the stock ROM for 5.0.2, and when I try to run the flash-all script, I get an error saying that boot.img is missing. I looked into the zip file where the bat file is looking, and there is definitely a boot.img there. I just updated platform-tools through the SDK manager a few hours ago, so I'm using the newest version.
Full output from flash-all:
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
OKAY [ 1.553s]
finished. total time: 1.685s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
error: update package missing boot.img
Press any key to exit...
Flash the files manually?
nhizzat said:
Flash the files manually?
Click to expand...
Click to collapse
Sorry for abandoning this thread. I flashed the boot and system images manually and it seemed to work. Thanks!
Hi! I trying to compile a kernel for our Lenovo Vibe K5+ and i'm having success on compilling, but, i have two output files in arm (Image and zImage) and just one in arm64 (Image)... I tried to flash via fastboot "fastboot flash boot Image" and zImage, but i always receive:
Code:
target reported max download size of 268435456 bytes
sending 'boot' (18616 KB)...
OKAY [ 0.749s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.750s
The same in both cases... But, i tried to decompress an boot.img of CM13 for our device and recompile with my zImage but when i flash, i reboot and devices stucks in "Lenovo" boot screen...
Since now, thanks!
Hey All,
I wanted to start a thread on compiling AOSP from scratch. I have done a bit of work with the folks over in the unofficial Lineage build (thank you @gee one!).
If you want to recreate my work, I posted helper scripts to include the necessary changes as well as a guide on how to compile there. Those scripts were adapted from lineageOS.
You can download a compiled img files or the recovery-image.zip here (get the vendor image here, and get the bootloader and radio images here). The recovery-image.zip should be able to be flashed in TWRP, or you can execute the following commands in the bootloader for the img files:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot -w (to wipe cache and data)
This is currently based off of build PQ3B.190801.002, last updated 2019-08-30
This ROM is compatible with MicroG, OpenGapps, F-Droid Privileged App, and Magisk
MicroG - Install via NanoDroid: https://nanolx.org/nanolx/nanodroid (Install first NanoDroid-Patcher then NanoDroig-MicroG)
OpenGapps - https://opengapps.org/
Magisk: https://forum.xda-developers.com/apps/magisk
F-Droid Privileged App: https://f-droid.org/en/packages/org.fdroid.fdroid.privileged.ota/
KNOWN ISSUES:
- AT&T does not have "Enhanced 4G LTE" mode, and WiFi Calling doesn't seem to work. I imagine this is a proprietary blob missing.
- eSIM isn't functional. I have a test build for it if you want to try, but it will crash without MicroG or Google Play. When I get confirmation it works I'll add it.
- There are probably other proprietary files I can add so that I can unlock normally stock ROM features, feel free to post and let me know. I am happy to even provide test builds, so if it does work, I will add it to the normal ROM.
NOTICES:
- This is untested in Sprint and Verizon. I removed a bunch of their proprietary files, so if you install and it doesn't work, install this version and see if it works. Please also let me know the results!
- If you do not install the AOSP Vendor above, you get a "device is corrupted" error. This is intentional. Secure boot is still on, so you cannot use the factory vendor image.
- The compiled ROMs will stay as close to AOSP as possible, with the exception of adding proprietary files that unlock stock ROM features. I do this so maintaining the ROM is easy, and I really only make this ROM for myself. I don't mind posting the compiled ROMs here, and I do hope folks find it useful. However, I am not adding non-stock/AOSP features (i.e. Lineage/OmniROM/bootlegger/etc. features). If I did, I have to add and maintain them. I really have neither the time nor the inclination to do that. The only way to change my mind is if I was paid to do it, but I already have a well paying day job, so the paycheck would have to be very well worth my while (which is why I don't have a donote button, I really don't want to feel like I'm obligated to do this).
I was trying to be "smart" and use vendor.img from stock ROM. It failed miserably.
Boot to TWRP first, did factory wipe, reboot to bootloader and flashed ROM:
======================================
AOSP>fastboot flash boot boot.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot flash system system.img && fastboot flash vendor vendor.img && fastboot -w
Sending 'boot_b' (65536 KB) OKAY [ 1.641s]
Writing 'boot_b' OKAY [ 0.328s]
Finished. Total time: 2.453s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.281s]
Writing 'dtbo_b' OKAY [ 0.094s]
Finished. Total time: 0.656s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_b' OKAY [ 0.063s]
Finished. Total time: 0.438s
Sending sparse 'system_b' 1/5 (262140 KB) OKAY [ 6.508s]
Writing 'system_b' OKAY [ 0.047s]
Sending sparse 'system_b' 2/5 (262140 KB) OKAY [ 6.531s]
Writing 'system_b' OKAY [ 0.063s]
Sending sparse 'system_b' 3/5 (262140 KB) OKAY [ 6.455s]
Writing 'system_b' OKAY [ 0.063s]
Sending sparse 'system_b' 4/5 (262140 KB) OKAY [ 6.584s]
Writing 'system_b' OKAY [ 0.359s]
Sending sparse 'system_b' 5/5 (155532 KB) OKAY [ 3.968s]
Writing 'system_b' OKAY [ 1.172s]
Finished. Total time: 39.903s
Sending sparse 'vendor_b' 1/3 (262140 KB) OKAY [ 6.527s]
Writing 'vendor_b' OKAY [ 0.373s]
Sending sparse 'vendor_b' 2/3 (262096 KB) OKAY [ 6.515s]
Writing 'vendor_b' OKAY [ 0.375s]
Sending sparse 'vendor_b' 3/3 (12276 KB) OKAY [ 1.297s]
Writing 'vendor_b' OKAY [ 0.125s]
Finished. Total time: 19.118s
Erasing 'userdata' OKAY [ 4.506s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.188s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 5.147s
======================================
White screen with Google logo popped up for few sec and phone rebooted with following message:
Your device is corrupt. It can't be trusted and may not work properly.
In second attempt flashed stock ROM first, boot, enabled ADB, disabled automatic updates, boot to bootloader, then TWRP, did factory wipe, flash ROM and ends up with the same result.
Compiling my own vendor image using provided instructions doesn't look like something I'm eager to do.
Pogo said:
I was trying to be "smart" and use vendor.img from stock ROM. It failed miserably.
Boot to TWRP first, did factory wipe, reboot to bootloader and flashed ROM:
======================================
AOSP>fastboot flash boot boot.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot flash system system.img && fastboot flash vendor vendor.img && fastboot -w
Sending 'boot_b' (65536 KB) OKAY [ 1.641s]
Writing 'boot_b' OKAY [ 0.328s]
Finished. Total time: 2.453s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.281s]
Writing 'dtbo_b' OKAY [ 0.094s]
Finished. Total time: 0.656s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_b' OKAY [ 0.063s]
Finished. Total time: 0.438s
Sending sparse 'system_b' 1/5 (262140 KB) OKAY [ 6.508s]
Writing 'system_b' OKAY [ 0.047s]
Sending sparse 'system_b' 2/5 (262140 KB) OKAY [ 6.531s]
Writing 'system_b' OKAY [ 0.063s]
Sending sparse 'system_b' 3/5 (262140 KB) OKAY [ 6.455s]
Writing 'system_b' OKAY [ 0.063s]
Sending sparse 'system_b' 4/5 (262140 KB) OKAY [ 6.584s]
Writing 'system_b' OKAY [ 0.359s]
Sending sparse 'system_b' 5/5 (155532 KB) OKAY [ 3.968s]
Writing 'system_b' OKAY [ 1.172s]
Finished. Total time: 39.903s
Sending sparse 'vendor_b' 1/3 (262140 KB) OKAY [ 6.527s]
Writing 'vendor_b' OKAY [ 0.373s]
Sending sparse 'vendor_b' 2/3 (262096 KB) OKAY [ 6.515s]
Writing 'vendor_b' OKAY [ 0.375s]
Sending sparse 'vendor_b' 3/3 (12276 KB) OKAY [ 1.297s]
Writing 'vendor_b' OKAY [ 0.125s]
Finished. Total time: 19.118s
Erasing 'userdata' OKAY [ 4.506s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.188s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 5.147s
======================================
White screen with Google logo popped up for few sec and phone rebooted with following message:
Your device is corrupt. It can't be trusted and may not work properly.
In second attempt flashed stock ROM first, boot, enabled ADB, disabled automatic updates, boot to bootloader, then TWRP, did factory wipe, flash ROM and ends up with the same result.
Compiling my own vendor image using provided instructions doesn't look like something I'm eager to do.
Click to expand...
Click to collapse
You should be able to use the vendor image off of the google website (AOSP drivers, not factory image), all you are doing is unpacking it and then agreeing to the terms of use. You can't use other ones because it trips secure boot. I hesitate to upload it because you have to agree to terms of use when you unpack it.
EDIT: I confirmed, the SHA-512 of the vendor.img off of the google website (AOSP, not stock) is exactly the same as the one I flashed (I.e. the compilation process does nothing to it). You do have to use the AOSP one, or else you trip secure boot.
Pogo said:
I was trying to be "smart" and use vendor.img from stock ROM. It failed miserably.
Boot to TWRP first, did factory wipe, reboot to bootloader and flashed ROM:
======================================
AOSP>fastboot flash boot boot.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot flash system system.img && fastboot flash vendor vendor.img && fastboot -w
Sending 'boot_b' (65536 KB) OKAY [ 1.641s]
Writing 'boot_b' OKAY [ 0.328s]
Finished. Total time: 2.453s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.281s]
Writing 'dtbo_b' OKAY [ 0.094s]
Finished. Total time: 0.656s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_b' OKAY [ 0.063s]
Finished. Total time: 0.438s
Sending sparse 'system_b' 1/5 (262140 KB) OKAY [ 6.508s]
Writing 'system_b' OKAY [ 0.047s]
Sending sparse 'system_b' 2/5 (262140 KB) OKAY [ 6.531s]
Writing 'system_b' OKAY [ 0.063s]
Sending sparse 'system_b' 3/5 (262140 KB) OKAY [ 6.455s]
Writing 'system_b' OKAY [ 0.063s]
Sending sparse 'system_b' 4/5 (262140 KB) OKAY [ 6.584s]
Writing 'system_b' OKAY [ 0.359s]
Sending sparse 'system_b' 5/5 (155532 KB) OKAY [ 3.968s]
Writing 'system_b' OKAY [ 1.172s]
Finished. Total time: 39.903s
Sending sparse 'vendor_b' 1/3 (262140 KB) OKAY [ 6.527s]
Writing 'vendor_b' OKAY [ 0.373s]
Sending sparse 'vendor_b' 2/3 (262096 KB) OKAY [ 6.515s]
Writing 'vendor_b' OKAY [ 0.375s]
Sending sparse 'vendor_b' 3/3 (12276 KB) OKAY [ 1.297s]
Writing 'vendor_b' OKAY [ 0.125s]
Finished. Total time: 19.118s
Erasing 'userdata' OKAY [ 4.506s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.188s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 5.147s
======================================
White screen with Google logo popped up for few sec and phone rebooted with following message:
Your device is corrupt. It can't be trusted and may not work properly.
In second attempt flashed stock ROM first, boot, enabled ADB, disabled automatic updates, boot to bootloader, then TWRP, did factory wipe, flash ROM and ends up with the same result.
Compiling my own vendor image using provided instructions doesn't look like something I'm eager to do.
Click to expand...
Click to collapse
How are you getting the "device is corrupt message". I think that only shows up when your bootloader is locked. Are you sure it's not the orange message " device can't be verified"? You should only get orange or yellow messages. The red message means something is wrong- missing keys or bad/no signature.
I might be a little confused- I've been building and flashing so many variations, I can't keep them straight anymore.
gee one said:
How are you getting the "device is corrupt message". I think that only shows up when your bootloader is locked. Are you sure it's not the orange message " device can't be verified"? You should only get orange or yellow messages. The red message means something is wrong- missing keys or bad/no signature.
I might be a little confused- I've been building and flashing so many variations, I can't keep them straight anymore.
Click to expand...
Click to collapse
I compiled AOSP with the AOSP vendor.IMG, not the factory vendor.img . he is using the factory one, and that triggers the "device is corrupt" error he is getting. It's secure boot detecting the difference in vendor images
kop316 said:
I compiled AOSP with the AOSP vendor.IMG, not the factory vendor.img . he is using the factory one, and that triggers the "device is corrupt" error he is getting. It's secure boot detecting the difference in vendor images
Click to expand...
Click to collapse
If you build it with the stock image as a prebuilt vendor image, the hash and info should be included in the vbmeta.img. The BoardConfigPartial.mk file has
Code:
BOARD_PREBUILT_VENDORIMAGE := vendor/google_devices/sargo/proprietary/vendor.img
which should add whatever vendor image you put in there to the vbmeta data.
However, if I recall correctly, building aosp with the aosp vendor images doesn't enable all the features. I think wifi calling and camera are broken on stock aosp.
There is a great tool for bringing the extra proprietary files into aosp. https://github.com/GrapheneOS/android-prepare-vendor
This will create a drop in replacement for the vendor/google_devices tree. I believe it also replaces the qcom tree as well.
Here is stock aosp built with help from the android-prepare-vendor scripts.
https://brownbagdinner.com/sargo-aosp-prepare-vendor_d6c76ce9.tar
This probably isn't gapps friendly, although there is a --full flag that will pull in more files that could help with gapps.
I don't think that you have to flash system_other.img, but it will probably speed up your first boot.
You can use "fastboot getvar current-slot" to see what slot you are on, and then flash system_other.img to, you know, the other slot with "fastboot flash system_<type in the other slot here> system_other.img"
You might have to wipe data if you are coming from a different rom, and you might have to reflash the stock vendor if you are going to a custom rom that is expecting the stock vendor.
gee one said:
If you build it with the stock image as a prebuilt vendor image, the hash and info should be included in the vbmeta.img. The BoardConfigPartial.mk file has
Code:
BOARD_PREBUILT_VENDORIMAGE := vendor/google_devices/sargo/proprietary/vendor.img
which should add whatever vendor image you put in there to the vbmeta data.
However, if I recall correctly, building aosp with the aosp vendor images doesn't enable all the features. I think wifi calling and camera are broken on stock aosp.
There is a great tool for bringing the extra proprietary files into aosp. https://github.com/GrapheneOS/android-prepare-vendor
This will create a drop in replacement for the vendor/google_devices tree. I believe it also replaces the qcom tree as well.
Here is stock aosp built with help from the android-prepare-vendor scripts.
https://brownbagdinner.com/sargo-aosp-prepare-vendor_d6c76ce9.tar
This probably isn't gapps friendly, although there is a --full flag that will pull in more files that could help with gapps.
I don't think that you have to flash system_other.img, but it will probably speed up your first boot.
You can use "fastboot getvar current-slot" to see what slot you are on, and then flash system_other.img to, you know, the other slot with "fastboot flash system_<type in the other slot here> system_other.img"
You might have to wipe data if you are coming from a different rom, and you might have to reflash the stock vendor if you are going to a custom rom that is expecting the stock vendor.
Click to expand...
Click to collapse
One of my next steps was to try the Graphene OS scripts to see how they work.
I am actually able to use WiFi calling and enhanced LTE on T mobile with the AOSP vendor image, and the camera works fine. If you are compiling AOSP yourself, you can also just swap out the vendor.IMG to the factory one.and recompile, it will do like you said.
I am trying also not to include every single.proprietary thing that is included, just what is needed for desired functionality. Several of them adds functionality for Google Play, and that can be added with openGapps.
kop316 said:
You should be able to use the vendor image off of the google website (AOSP drivers, not factory image), all you are doing is unpacking it and then agreeing to the terms of use. You can't use other ones because it trips secure boot. I hesitate to upload it because you have to agree to terms of use when you unpack it.
EDIT: I confirmed, the SHA-512 of the vendor.img off of the google website (AOSP, not stock) is exactly the same as the one I flashed (I.e. the compilation process does nothing to it). You do have to use the AOSP one, or else you trip secure boot.
Click to expand...
Click to collapse
You are right. Once I extracted vendor.img from AOSP it booted!
I'm looking around, playing, installing... So far so good
Magisk and EdXposed are working ,Google camera is working after installing microG as well as my banking app, Netflix and all other apps I use.
Pogo said:
You are right. Once I extracted vendor.img from AOSP it booted!
I'm looking around, playing, installing... So far so good
Magisk and EdXposed are working ,Google camera is working after installing microG as well as my banking app, Netflix and all other apps I use.
Click to expand...
Click to collapse
Glad to hear It! I didn't add the part to allow signature spoofing....I'm surprised MicroG works. That was something I was going to try.
kop316 said:
Glad to hear It! I didn't add the part to allow signature spoofing....I'm surprised MicroG works. That was something I was going to try.
Click to expand...
Click to collapse
Signature Spoofing require FakeGApps2.apk which is Exposed module. However FakeGApps2 is throwing lots of NullPointerExceptions in EdXposed. If you add signature spoofing into ROM, this module won't be needed.
Pogo said:
Signature Spoofing require FakeGApps2.apk which is Exposed module. However FakeGApps2 is throwing lots of NullPointerExceptions in ExXposed. If you add signature spoofing into ROM, this module won't be needed.
Click to expand...
Click to collapse
OK. I haven't tried Exposed in a long time.
My mobile provider has LTE. Mobile network in Status bar shows 4G+ (ok, no big deal).
In Mobile Network -> Advanced -> Preferred Network type, it also say 4G+ (again no big deal). However when I click to 'Preferred Network type' the available options are 3G and 2G. No 4G+, no LTE option.
The mobile speed is fine, it's definitely as fast as any other ROM.
Any chance to add eSIM into AOSP? I nave tried to install eSIM app from my backup, the app is there, but it won't show in the options (Settings->Mobile network->Advanced->Carrier)
Pogo said:
My mobile provider has LTE. Mobile network in Status bar shows 4G+ (ok, no big deal).
In Mobile Network -> Advanced -> Preferred Network type, it also say 4G+ (again no big deal). However when I click to 'Preferred Network type' the available options are 3G and 2G. No 4G+, no LTE option.
The mobile speed is fine, it's definitely as fast as any other ROM.
Any chance to add eSIM into AOSP? I nave tried to install eSIM app from my backup, the app is there, but it won't show in the options (Settings->Mobile network->Advanced->Carrier)
Click to expand...
Click to collapse
I'm aware of the first issue, I have a feeling there's an app I need to add that I haven't yet.
I recall Gee One saying you need Gapps for the eSIM to work? I know AOSP is aware of it (if you go into reset -> network, it will ask to also wipe your eSIM).
kop316 said:
I'm aware of the first issue, I have a feeling there's an app I need to add that I haven't yet.
I recall Gee One saying you need Gapps for the eSIM to work? I know AOSP is aware of it (if you go into reset -> network, it will ask to also wipe your eSIM).
Click to expand...
Click to collapse
Esim looks for gcs/google services otherwise it will force close.
Oops, hit send too soon. Lineage has LTE as an option. I can't remember if I've ever seen it on aosp. I think yes, because WiFi calls are HD. I'll check when I'm home later.
gee one said:
Oops, hit send too soon. Lineage has LTE as an option. I can't remember if I've ever seen it on aosp. I think yes, because WiFi calls are HD. I'll check when I'm home later.
Click to expand...
Click to collapse
The AOSP one I compiled doesn't have that option. I was wondering if I didn't include a proprietary file to allow that. But it does give me enhanced 4G LTE mode (VoLTE) and it gives my WiFi calling, so I haven't made too hard of an effort to look.
If you know what it is I am missing that'd be great!
gee one said:
Esim looks for gcs/google services otherwise it will force close.
Click to expand...
Click to collapse
I have microG installed and eSIM Manager (pulled from Stock ROM) and it's not crashing.
However, I cannot start it. My guess is that some menu option is missing or has to be enabled in Settings.
If I search for eSIM in Settings it point to 'Carrier', but nothing happen when click on this.
If I try to start some of the eSIM Manager activities I'm getting "permission denied". Don't know if this help.
kop316 said:
The AOSP one I compiled doesn't have that option. I was wondering if I didn't include a proprietary file to allow that. But it does give me enhanced 4G LTE mode (VoLTE) and it gives my WiFi calling, so I haven't made too hard of an effort to look.
If you know what it is I am missing that'd be great!
Click to expand...
Click to collapse
Yup, that sound right. The menu has a toggle for 4G LTE mode, but the network type only allows for 3G/2G.
This is for aosp.
Pogo said:
I have microG installed and eSIM Manager (pulled from Stock ROM) and it's not crashing.
However, I cannot start it. My guess is that some menu option is missing or has to be enabled in Settings.
If I search for eSIM in Settings it point to 'Carrier', but nothing happen when click on this.
If I try to start some of the eSIM Manager activities I'm getting "permission denied". Don't know if this help.
Click to expand...
Click to collapse
https://mega.nz/#F!95wmSAJA!xE1eWAA68AsJax6C90pFxg
See if that get's it to work. I am not confident it will work without Google Play, but maybe?
kop316 said:
https://mega.nz/#F!95wmSAJA!xE1eWAA68AsJax6C90pFxg
See if that get's it to work. I am not confident it will work without Google Play, but maybe?
Click to expand...
Click to collapse
Should I just flash these 3 img files or there are more steps involved?
{
"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"
}
PixelExperience for the Sony Xperia XZ2 Compact apollo
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 10.0
Whats working?
Wifi
RIL
Volte
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
Sony Open Devices bug tracker
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Pixel Experience website (Xperia XZ2 Compact Single Sim)
Download from Pixel Experience website (Xperia XZ2 Compact Dual Sim)
Flash instructions and special recovery coming on Monday 24/02/2020
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Sony Specified Telegram channel
Our blog
Android OS version: 10.0.0_r27
Security patch level: February 2020
Build author/Device Maintainer: fastbooking
Device Source code: https://github.com/PixelExperience-Devices/device_sony_customization
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Hello. What about Tama/Akari? Does it stable on XZ2? What about bugs or work/not work things? Sorry for bad eng.
[email protected]+ said:
Hello. What about Tama/Akari? Does it stable on XZ2? What about bugs or work/not work things? Sorry for bad eng.
Click to expand...
Click to collapse
Hey ! I think the thread you're searching is this one : https://forum.xda-developers.com/xp...om-pixel-experience-xperia-xz2-akari-t4054671
Anyway, to answer your question, it's pretty much stable, I have users testing it and it seem to be rock solid, I'm working hard with the Sony Open Devices on new features and great performance optimizations.
Does this ROM have the same issues as the android 10 stock rom ?
Looking forward to install it
fastbooking said:
Flash instructions and special recovery coming on Monday 24/02/2020
[/LEFT]
Click to expand...
Click to collapse
Where is the instructions?
Noob to flashing on Xperia. Coming from oneplus where everything is pretty straightforward, I'm not very confident trying unlocking the bootloader on my xz2.
Also I've read conflicting accounts of drm issues if you try to go back stock. Is there any truth to this?
Any screenshots or install instructions?
Is there any flashing guide? Or I can simply flash it without any other files in twrp? PS: Pls forgive my poor Eng.:laugh:
is it worth it
Where are the recovery and the instructions?
Not Good
Doesnt charge properly and the camera takes pink photos
Which kernel would you recommend for this rom
I found the instructions
AntonioBiscuit said:
Where are the recovery and the instructions?
Click to expand...
Click to collapse
go check this website
https://sites.google.com/d/1EhBdYBO...KEXb/p/1oI8WuIQKz4rVj2d5Og7p6TYgh60o31Aa/edit
Does not work for me...
logan123456 said:
go check this website
Click to expand...
Click to collapse
I followed the instructions on the website but it does not work for me.
I get stuck in a bootloop where at first I see a message saying that the bootloader is onulocked and cannot verify the device, then the Sony logo for a few times.
After what I get a red warning saying that my device is corrupt and will poweroff in 5 seconds.
I used Kernel 4.14 v5a Tama binaries and tried with the Pixel Experience Plus build from March 30, 2020 and the normal Pixel Experience build from the same date.
My XZ2C is a Dual-SIM one, Revision 6.
I verified that I had the right build (H8324) and verified that I had correctly downloaded the files.
I tried flashing the binaries only on "oem" the first time and another time with "oem_a" + "oem_b".
Maybe I'm doing something wrong or I forgot to flash some file.
I'm worried about the "Invalid sparse file format at header magi" message, I don't know if it may somewhat be the issue.
(I am able to flash and boot from the latest stock ROM without any trouble)
Code:
>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.005s]
writing 'vbmeta'...
OKAY [ 0.003s]
finished. total time: 0.011s
>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.943s]
writing 'boot'...
OKAY [ 0.376s]
finished. total time: 2.321s
>fastboot flash dtbo dtbo.img
target reported max download size of 805306368 bytes
sending 'dtbo' (8192 KB)...
OKAY [ 0.254s]
writing 'dtbo'...
OKAY [ 0.050s]
finished. total time: 0.306s
>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.249s]
sending sparse 'system' (759566 KB)...
OKAY [ 24.189s]
writing 'system'...
OKAY [ 0.003s]
sending sparse 'system' (724540 KB)...
OKAY [ 23.036s]
writing 'system'...
OKAY [ 0.002s]
sending sparse 'system' (738077 KB)...
OKAY [ 23.506s]
writing 'system'...
OKAY [ 0.002s]
sending sparse 'system' (62664 KB)...
OKAY [145.908s]
writing 'system'...
OKAY [ 0.003s]
finished. total time: 216.907s
>fastboot flash vendor vendor.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
sending sparse 'vendor' (55600 KB)...
OKAY [ 1.747s]
writing 'vendor'...
OKAY [ 0.003s]
finished. total time: 1.755s
>fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v5a_tama.img
target reported max download size of 805306368 bytes
sending 'oem' (320708 KB)...
OKAY [ 9.513s]
writing 'oem'...
OKAY [ 9.232s]
finished. total time: 18.748s
Hi,
I flashed the binaries "SW_binaries_for_Xperia_Android_10.0.7.1_r1_v4c_tama" on oem_a and oem_b. This works fine.
Greets Duke
duke864 said:
I flashed the binaries "SW_binaries_for_Xperia_Android_10.0.7.1_r1_v4c_tama" on oem_a and oem_b. This works fine.
Click to expand...
Click to collapse
Seems not to work even if I'm using this version of the binaries, I still have the same issue.
(tested with oem_a and oem_b with the binaries version you advised me and with the March 30, 2020 build of regular Pixel Experience, following the flashing instructions from the website)
There's definetly something that I'm either doing wrong, a file or step which is missing in my case.
I also heard about a bootloader bug or some kind of security, maybe it's messing up with my installation...
I would be glad to have a tutorial from someone who has succeeded with the latest version
Did you have this issue
duke864 said:
Hi,
I flashed the binaries "SW_binaries_for_Xperia_Android_10.0.7.1_r1_v4c_tama" on oem_a and oem_b. This works fine.
Greets Duke
Click to expand...
Click to collapse
did you have any battery problems in pixel experience like not accurate battery percentage
---------- Post added at 04:01 AM ---------- Previous post was at 03:58 AM ----------
AntonioBiscuit said:
Seems not to work even if I'm using this version of the binaries, I still have the same issue.
(tested with oem_a and oem_b with the binaries version you advised me and with the March 30, 2020 build of regular Pixel Experience, following the flashing instructions from the website)
There's definetly something that I'm either doing wrong, a file or step which is missing in my case.
I also heard about a bootloader bug or some kind of security, maybe it's messing up with my installation...
I would be glad to have a tutorial from someone who has succeeded with the latest version
Click to expand...
Click to collapse
maybe try formatting your phone completely and try again
---------- Post added at 04:12 AM ---------- Previous post was at 04:01 AM ----------
AntonioBiscuit said:
I followed the instructions on the website but it does not work for me.
I get stuck in a bootloop where at first I see a message saying that the bootloader is onulocked and cannot verify the device, then the Sony logo for a few times.
After what I get a red warning saying that my device is corrupt and will poweroff in 5 seconds.
I used Kernel 4.14 v5a Tama binaries and tried with the Pixel Experience Plus build from March 30, 2020 and the normal Pixel Experience build from the same date.
My XZ2C is a Dual-SIM one, Revision 6.
I verified that I had the right build (H8324) and verified that I had correctly downloaded the files.
I tried flashing the binaries only on "oem" the first time and another time with "oem_a" + "oem_b".
Maybe I'm doing something wrong or I forgot to flash some file.
I'm worried about the "Invalid sparse file format at header magi" message, I don't know if it may somewhat be the issue.
(I am able to flash and boot from the latest stock ROM without any trouble)
Code:
>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.005s]
writing 'vbmeta'...
OKAY [ 0.003s]
finished. total time: 0.011s
>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.943s]
writing 'boot'...
OKAY [ 0.376s]
finished. total time: 2.321s
>fastboot flash dtbo dtbo.img
target reported max download size of 805306368 bytes
sending 'dtbo' (8192 KB)...
OKAY [ 0.254s]
writing 'dtbo'...
OKAY [ 0.050s]
finished. total time: 0.306s
>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.249s]
sending sparse 'system' (759566 KB)...
OKAY [ 24.189s]
writing 'system'...
OKAY [ 0.003s]
sending sparse 'system' (724540 KB)...
OKAY [ 23.036s]
writing 'system'...
OKAY [ 0.002s]
sending sparse 'system' (738077 KB)...
OKAY [ 23.506s]
writing 'system'...
OKAY [ 0.002s]
sending sparse 'system' (62664 KB)...
OKAY [145.908s]
writing 'system'...
OKAY [ 0.003s]
finished. total time: 216.907s
>fastboot flash vendor vendor.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
sending sparse 'vendor' (55600 KB)...
OKAY [ 1.747s]
writing 'vendor'...
OKAY [ 0.003s]
finished. total time: 1.755s
>fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v5a_tama.img
target reported max download size of 805306368 bytes
sending 'oem' (320708 KB)...
OKAY [ 9.513s]
writing 'oem'...
OKAY [ 9.232s]
finished. total time: 18.748s
Click to expand...
Click to collapse
i am not sure if you are supposed flash it on both slots fastboot flash oem_a
fastboot flash oem_b
was there any battery problem
like severe battery drain
if there was a problem how did you fix it
It works !
I finally managed to install the ROM yesterday using differents instructions.
Here is how I did it if you are struggling to install like me at the beginning (or maybe there was just a fix in between, I don't know).
Before doing anything, the usual, you might want to take some precautions: do backups and remove the SD card from your device before loosing anything. What follows is going to format your internal storage.
Please respond if anything is wrong in here of if you have some details to add.
My installation was done from Android 10 stock 52.1.A.0.618. You can install it from a program called "Emma" from Sony.
You will first need to extract "payload.bin" from the .zip ROM file you have downloaded (Pixel Experience).
You will then need to use a program called "payload dumper" to get the files you'll be installing with fastboot afterwards from the payload.bin you just extracted. (expect around 6GB of files)
You will also need to extract "SW_binaries.img" from the most recent binaries .zip, which you can download on Sony's website.
In your command prompt you will need to do the following:
Code:
> fastboot flash boot boot.img
> fastboot flash dtbo dtbo.img
> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
> fastboot flash system system.img
> fastboot flash vendor vendor.img
> fastboot flash oem_a SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
> fastboot flash oem_b SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
Some things to keep in mind and which I would have liked to be aware of :
If you can't use --disable-verity and/or --disable-verification, try to launch your terminal from the folder of your most recent platform tools. It seems like they don't exist in some adb installers.
Flashing the files to your phone may take a long while to start. Just be patient.
You may see a "Invalid sparse file format at header magi" message at some point. I am not sure what it means (tell me if you know) but I got it and my phone is working just fine right now.
If you see a Google logo after the Sony logo, it means you probably succeeded.
After installing, my phone bootlooped two times. It then showed me a menu where I could format some data. I did it and after that it took a while to boot the first time but finally worked.
Here are the builds I am currently testing on my Xperia XZ2 Compact (H8324 REV6):
PixelExperience_h8324-10.0-20200511-0435-OFFICIAL.zip
SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
I will try to tell you about the bugs and issues I may face in the next few days, but right now the ROM is feeling way snappier than Sony's stock Android 10 ROM in my opinion and the animations are gorgeous.
AntonioBiscuit said:
I finally managed to install the ROM yesterday using differents instructions.
Here is how I did it if you are struggling to install like me at the beginning (or maybe there was just a fix in between, I don't know).
Before doing anything, the usual, you might want to take some precautions: do backups and remove the SD card from your device before loosing anything. What follows is going to format your internal storage.
Please respond if anything is wrong in here of if you have some details to add.
My installation was done from Android 10 stock 52.1.A.0.618. You can install it from a program called "Emma" from Sony.
You will first need to extract "payload.bin" from the .zip ROM file you have downloaded (Pixel Experience).
You will then need to use a program called "payload dumper" to get the files you'll be installing with fastboot afterwards from the payload.bin you just extracted. (expect around 6GB of files)
You will also need to extract "SW_binaries.img" from the most recent binaries .zip, which you can download on Sony's website.
In your command prompt you will need to do the following:
Code:
> fastboot flash boot boot.img
> fastboot flash dtbo dtbo.img
> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
> fastboot flash system system.img
> fastboot flash vendor vendor.img
> fastboot flash oem_a SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
> fastboot flash oem_b SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
Some things to keep in mind and which I would have liked to be aware of :
If you can't use --disable-verity and/or --disable-verification, try to launch your terminal from the folder of your most recent platform tools. It seems like they don't exist in some adb installers.
Flashing the files to your phone may take a long while to start. Just be patient.
You may see a "Invalid sparse file format at header magi" message at some point. I am not sure what it means (tell me if you know) but I got it and my phone is working just fine right now.
If you see a Google logo after the Sony logo, it means you probably succeeded.
After installing, my phone bootlooped two times. It then showed me a menu where I could format some data. I did it and after that it took a while to boot the first time but finally worked.
Here are the builds I am currently testing on my Xperia XZ2 Compact (H8324 REV6):
PixelExperience_h8324-10.0-20200511-0435-OFFICIAL.zip
SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
I will try to tell you about the bugs and issues I may face in the next few days, but right now the ROM is feeling way snappier than Sony's stock Android 10 ROM in my opinion and the animations are gorgeous.
Click to expand...
Click to collapse
please give the review about the performance for gaming use
i would like to change to use PE but still not sure if this form can significantly boost the performance on xz2c for gaming than the stock rom official
because since the android 10 on official stock rom, i feel it drop down the performance for gaming. it makes me struggle alot of time
Gaming performance
3D performance:
I used 3D Mark Sling Shot extreme in the hope that you will find what performance you can expect by running this ROM and binaries:
- PixelExperience_h8324-10.0-20200511-0435-OFFICIAL
- SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama
Stock Android for comparison: https://benchmarks.ul.com/en/hardware/phone/Sony+Xperia+XZ2+Compact+review
(You can test your device if you have stock Android to compare the results)
The scores presented here are averaged from 5 runs and are pretty much the same as what is in the database. There should not be a huge performance difference in games.
OpenGL ES 3.1:
Overall: 4,167.4 (~1% lower)
Graphics: 5,125 (=)
Physics: 2,522.6 (-24%)
Vulkan:
Overall: 3,973.2 (=)
Graphics: 4,664 (-5%)
Physics: 2,620 (+11%)
Detailled scores for the 5 runs:
Run 01:
Open GL ES 3.1
Overall score: 4,161
Graphics score: 5,149
Physics score: 2,490
Vulkan
Overall score 4,047
Graphics score: 4,664
Physics score: 2,767
----------
Run 02:
Open GL ES 3.1
Overall score: 4,250
Graphics score: 5,124
Physics score: 2,661
Vulkan
Overall score: 4,018
Graphics score: 4,668
Physics score: 2,701
----------
Run 03:
Open GL ES 3.1
Overall score: 4,093
Graphics score: 5,120
Physics score: 2,404
Vulkan
Overall score: 3,968
Graphics score: 4,679
Physics score: 2,591
----------
Run 04:
Open GL ES 3.1
Overall score: 4,094
Graphics score: 5,107
Physics score: 2,417
Vulkan
Overall score: 3,851
Graphics score: 4,657
Physics score: 2,398
----------
Run 05:
Open GL ES 3.1
Overall score: 4,239
Graphics score: 5,125
Physics score: 2,641
Vulkan
Overall score: 3,980
Graphics score: 4,652
Physics score: 2,643
AOSP 13
This is a moto-common project release under the codename amogus. This build supports the following devices: rav, rav_t, sofia, sofiap, sofiap_ao, sofiap_sprout, sofiar.
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's AOSP?
AOSP is Android as Google publish without any modifications.
Whats not working?
Speakerphone on sofia variants
Instructions to install the ROM:
Reboot to bootloader:
Code:
adb reboot bootloader
The following will wipe your internal data:
Code:
fastboot -w
Code:
fastboot update package.zip
You may need to install drivers in device manager after running the last command
It will reboot your device to fastbootd, you might get the following warning:
Code:
FAILED (remote: 'Old partitions are not compatible with the new super layout; wipe needed')
, but you can continue with the following commands
Fastbootd:
Code:
fastboot flash product product.img
Code:
fastboot flash system system.img
Code:
fastboot flash vendor vendor.img
Code:
fastboot reboot
Downloads: Here
Source Code: Here
Sept 2: Fixed USB Mode Switching, Switched to new rebased kernel, Switched to EROFS
Sept 12: EGIS Fingerprint gestures fixed, Switch BtAudio to AIDL and September Patch level
Sept 28:
System Responsiveness has been tuned and improved
Introduce Multigenerational LRU Framework
Tune Dalvik Heap Sizes
Switched to QTI Thermal HAL
DT2W has been fixed for RAV (HIMAX) variants of amogus
Signature Spoofing support has been added to the ROM
Jan 26:
January Security Patch
Feb 27:
Feb security patch
Sept 2: Fixed USB Mode Switching, Switched to new rebased kernel, Switched to EROFS
Is anyone has ported the A12 official version from moto g pro who works in moto g8 power (sofiar)?
im guessing this doesnt come with any gapps installed?
if so would I need to flash gapps with It and from what i could tell do i need to downgrade to the stock android 10 rom to be able to flash cus i have attempted before but since it was on the stock android 11 version it would just get stuck
Sept 12: EGIS Fingerprint gestures fixed, Switch BtAudio to AIDL and September Patch level
Where can i get the files named "vendor.img","system.img" and "product.img"
AlejandroCRI said:
Where can i get the files named "vendor.img","system.img" and "product.img"
Click to expand...
Click to collapse
Inside the zip file you downloaded
Electimon said:
Inside the zip file you downloaded
Click to expand...
Click to collapse
sorry, i saw other .zip and that i wanted was in other folder
Any chance this works on Moto G Stylus 2021 Minsk?
afnz said:
Any chance this works on Moto G Stylus 2021 Minsk?
Click to expand...
Click to collapse
No sorry, that uses a different chipset
Electimon said:
No sorry, that uses a different chipset
Click to expand...
Click to collapse
Alright, thank you for your quick reply!
Sept 28:
System Responsiveness has been tuned and improved
Introduce Multigenerational LRU Framework
Tune Dalvik Heap Sizes
Switched to QTI Thermal HAL
DT2W has been fixed for RAV (HIMAX) variants of amogus
Signature Spoofing support has been added to the ROM
Did someone try this in the Moto g stylus US version?
Hi @Electimon First of all thanks for the big effort of A13 , must be kinda difficult to work on a project like this . Hope you can continue with this as long as you can as we all benefit from your effort on this . But I do have a question if I may of course. I see on the title that it is supported sofiap_sprout and I have that device which is Moto G Pro but When I flash your zip with fastboot update package.zip it tells me that
Checking 'product' FAILED
Device product is 'sofiap_sprout'.
Update requires 'trinket' or 'amogus' or 'rav' or 'sofiar' or 'sofia' or 'sofiap' or 'doha'.
fastboot: error: requirements not met!
then I checked the Zip file and there is a txt file that is android-info and contains the following
require board=trinket|amogus|rav|sofiar|sofia|sofiap|doha
which I believe is where that error comes from and im afraid that if I update by changing the txt file to sofiap_sprout and re zip it might be cathastrofic to my device . Any Idea?
Thanks in Advanced
Nanosochoa said:
Hi @Electimon First of all thanks for the big effort of A13 , must be kinda difficult to work on a project like this . Hope you can continue with this as long as you can as we all benefit from your effort on this . But I do have a question if I may of course. I see on the title that it is supported sofiap_sprout and I have that device which is Moto G Pro but When I flash your zip with fastboot update package.zip it tells me that
Checking 'product' FAILED
Device product is 'sofiap_sprout'.
Update requires 'trinket' or 'amogus' or 'rav' or 'sofiar' or 'sofia' or 'sofiap' or 'doha'.
fastboot: error: requirements not met!
then I checked the Zip file and there is a txt file that is android-info and contains the following
require board=trinket|amogus|rav|sofiar|sofia|sofiap|doha
which I believe is where that error comes from and im afraid that if I update by changing the txt file to sofiap_sprout and re zip it might be cathastrofic to my device . Any Idea?
Thanks in Advanced
Click to expand...
Click to collapse
You can edit the file and try again or unpack and flash manually, I need to add sofiap_sprout to the guard but yes it's supported
Thanks @Electimon o for the faster response.
However I did the steps on the Sofiap_sprout by doing step by step and re zipping the files with the modified txt file and got boot loop and then went into a different recovery with an error messsage a the bottom that says
Error: recovery: [libfs_mgr]dt_fstab : failed to find device for partition OEM
and then im at the Fastbootd page .
Any ideas?
My sofiap sprout was on A12 official from Motorola if that helps.
If anything , this is the whole CMD message (btw the files were re zipped to electimon.zip with the modified txt file adding only sofiap_sprout)
C:\Users\**\Desktop\platform-tools>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.008s]
< waiting for any device >
Finished. Total time: 18.826s
C:\Users\**\Desktop\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.212s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.009s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.240s
C:\Users\**\Desktop\platform-tools>fastboot update electimon.zip
--------------------------------------------
Bootloader Version...: MBM-3.0-sofiap_ao-7380af07e7e-220720
Baseband Version.....:
Serial Number........: ZY227ZQ5RM
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.188s]
extracting boot.img (64 MB) to disk... took 0.472s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.844s]
Writing 'boot_a' OKAY [ 1.456s]
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.184s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (24576 KB) OKAY [ 0.689s]
Writing 'dtbo_a' OKAY [ 0.241s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
extracting recovery.img (64 MB) to disk... took 0.421s
archive does not contain 'recovery.sig'
Sending 'recovery_a' (65536 KB) OKAY [ 1.838s]
Writing 'recovery_a' OKAY [ 1.463s]
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition FAILED (remote: 'Old partitions are not compatible with the new super layout; wipe needed')
fastboot: error: Command failed
C:\Users\**\Desktop\platform-tools>fastboot flash product product.img
Sending 'product' (151708 KB) OKAY [ 4.382s]
Writing 'product' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
C:\Users\**\Desktop\platform-tools>fastboot flash system system.img
Resizing 'system_a' OKAY [ 0.007s]
Sending sparse 'system_a' 1/3 (262140 KB) OKAY [ 7.469s]
Writing 'system_a' OKAY [ 2.495s]
Sending sparse 'system_a' 2/3 (262140 KB) OKAY [ 7.545s]
Writing 'system_a' OKAY [ 1.478s]
Sending sparse 'system_a' 3/3 (69652 KB) OKAY [ 1.964s]
Writing 'system_a' OKAY [ 0.468s]
Finished. Total time: 22.635s
C:\Users\**\Desktop\platform-tools>fastboot flash vendor vendor.img
Resizing 'vendor_a' OKAY [ 0.005s]
Sending 'vendor_a' (205840 KB) OKAY [ 5.988s]
Writing 'vendor_a' OKAY [ 1.215s]
Finished. Total time: 7.303s
C:\Users\**\Desktop\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
Hi @Electimon
Just wanted to update the post that I was able to flash it
Had to set active partition a and delete partition a and product partition
and then create logical partition a and product and then
fastboot -w
fastboot --set-active=a
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash vendor vendor.img
and worked .. boot right to AOSP 13 in MOTO G Pro .. RAM usage is awesome... will be trying this as main driver and see what happens so far so good.
Thanks Electimon
Hi @Electimon
Everything is great so far .. Just vfc card cnat be added due to a permission missing but I already checked apps permissions and cache and still showing that but I bypassed that by installing a third party dialer from Fdroid and from there installed the vfc card to the phone contacts and fixed .. Also another thing that its important is the battery that drains so fast .. I mean I was using phhusson GSI for A12 y A11 and the battery was insanely good lasted the whole day with usage but on this rom takes like 5 hours with usage to drain completely the battery .. I know its not mandatory to fix that which im very grateful to you for this but I though you might wanna know .
Thanks in advance
I was asking if updating to stock A11 caused this to not work, happy to report that installing was straightforward
On another note, has anyone figured out getting GApps on this rom?