Develop Bugs

Help, I need some tips to compile a kernel...

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!

Stuck on TWRP after accidental factory reset

I was about to manually install the lineageOS update, but I accidentally swiped factory restore. Is there anyway I can get the update file online? I tried starting from the top by wiping everything and reinstalling the rom but it only boots me into TWRP. I also tried restoring backup files but is also boots me into TWRP. I am stuck.
PS: I tried the "fastboot continue" method but it boots me into TWRP.

reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually

sukhwant717 said:
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
Click to expand...
Click to collapse
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?

lemuelermita said:
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
Click to expand...
Click to collapse
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash

sukhwant717 said:
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
Click to expand...
Click to collapse
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?

lemuelermita said:
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
Click to expand...
Click to collapse
raw is definitely best option. are you able to mount data and cache partition in TWRP

sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?

sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
Defensively smartest guy about phones in the world!!! ahaha <3

lemuelermita said:
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
Click to expand...
Click to collapse
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

sukhwant717 said:
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Thank you very much, Sir! I will give you an update soon.

lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
Followed the instructions on the link but my phone boots up on a blinking screen with an android saying "Error". The command prompt failed at steps 4,5, and 11.
C:\Users\Lemuel\Documents\RESTOCK>fastboot devices
F5AZFG14A156 fastboot
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem erase_osip_header
...
OKAY [ 0.217s]
finished. total time: 0.219s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 0.228s]
finished. total time: 0.231s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.194s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.384s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.205s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.394s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem partition /tmp/partition.tbl
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.560s]
finished. total time: 0.561s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase data
******** Did you mean to fastboot format this ext4 partition?
erasing 'data'...
OKAY [ 1.447s]
finished. total time: 1.448s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase APD
******** Did you mean to fastboot format this ext4 partition?
erasing 'APD'...
OKAY [ 0.290s]
finished. total time: 0.294s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase ADF
******** Did you mean to fastboot format this ext4 partition?
erasing 'ADF'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem wipe splashscreen
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning
OKAY [ 0.210s]
finished. total time: 0.212s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash splashscreen splash_sign.bin
target reported max download size of 536870912 bytes
sending 'splashscreen' (270 KB)...
OKAY [ 0.192s]
writing 'splashscreen'...
OKAY [ 0.236s]
finished. total time: 0.431s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash token MFG_BOM_Full.bin
target reported max download size of 536870912 bytes
sending 'token' (3 KB)...
OKAY [ 0.194s]
writing 'token'...
OKAY [ 0.370s]
finished. total time: 0.566s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash ifwi ifwi-prod.bin
target reported max download size of 536870912 bytes
sending 'ifwi' (4096 KB)...
OKAY [ 0.294s]
writing 'ifwi'...
OKAY [ 1.027s]
finished. total time: 1.326s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash boot boot_sign.bin
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.648s]
finished. total time: 1.182s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash recovery recovery_sign.bin
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.520s]
writing 'recovery'...
OKAY [ 0.636s]
finished. total time: 1.163s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash fastboot droidboot_sign.bin
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.558s]
writing 'fastboot'...
OKAY [ 0.739s]
finished. total time: 1.302s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash APD APD.img
target reported max download size of 536870912 bytes
erasing 'APD'...
OKAY [ 0.204s]
sending 'APD' (183963 KB)...
OKAY [ 4.927s]
writing 'APD'...
OKAY [ 0.912s]
finished. total time: 6.049s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.233s]
sending sparse 'system' 1/5 (518551 KB)...
OKAY [ 27.274s]
writing 'system' 1/5...
OKAY [ 5.563s]
sending sparse 'system' 2/5 (523662 KB)...
OKAY [ 22.886s]
writing 'system' 2/5...
OKAY [ 6.964s]
sending sparse 'system' 3/5 (520607 KB)...
OKAY [ 24.630s]
writing 'system' 3/5...
OKAY [ 8.077s]
sending sparse 'system' 4/5 (500735 KB)...
OKAY [ 23.704s]
writing 'system' 4/5...
OKAY [ 7.983s]
sending sparse 'system' 5/5 (188368 KB)...
OKAY [ 8.849s]
writing 'system' 5/5...
OKAY [ 1.187s]
finished. total time: 137.827s
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>fastboot reboot
rebooting...
finished. total time: 0.126s

lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!

lemuelermita said:
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
Click to expand...
Click to collapse
hmm good to know device working again. strongly recommend you to perform a factory reset even device working perfectly.

Compiling AOSP From Scratch

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?

Flash a custom rom without recovery (using fastboot)

Are there roms to flash with fastboot ? Since I can't boot to recovery (local on my pc or on the phone).

robuser007 said:
Are there roms to flash with fastboot ? Since I can't boot to recovery (local on my pc or on the phone).
Click to expand...
Click to collapse
TrebleGSI - Browse /LiR/2022.03.25 at SourceForge.net
sourceforge.net

How do I flash this? I only find an img file
which one do I need?
How do I flash this? I only find an img file
which one do I need?
kirichen said:
TrebleGSI - Browse /LiR/2022.03.25 at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse

robuser007 said:
which one do I need?
Click to expand...
Click to collapse
Install TrebleInfo.apk from google play and run, give me the screenshot
kirichen said:
Install TrebleInfo.apk from google play and run, give me the screenshot
Click to expand...
Click to collapse
<ARCH>_xyZ
<ARCH> can be arm, a64(arm32_binder64) or arm64
x can be a or b
y can be v, o, g or f
Z can be N, S or Z
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no built-in gapps)
f = floss (free & open source apps instead of gapps)
N = no phh-superuser and su (no root)
S = integrated with su, sometimes with phh-superuser
Z = extended dynamic root, su plus phh-superuser (you can enable/disable root without rebooting)
-vndklite, -lite = Android 11 builds for VNDK Lite vendors (view via Treble Info app)
that is, for example, "arm64_avN" is ARM64 A-only vanilla (without gapps) and without root
robuser007 said:
How do I flash this?
Click to expand...
Click to collapse
unzip systemA11.img
install fastboot for your platform
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
kirichen said:
unzip systemA11.img
install fastboot for your platform
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Click to expand...
Click to collapse
Install Android 11 GSI for App Testing | Android Developers
In this codelab, you will install Android 11 Generic System Image (GSI) to Android 9 (Pie) devices. After that, you can develop and validate your application with the new OS!
developer.android.com
robuser007 said:
How do I flash this?
Click to expand...
Click to collapse
In general, 3 things are needed to use Android GSI:
a device is fully Treble compliant (Treble support is mandatory for devices launched with Android 9 or later).
the device's bootloader could be unlocked.
the tools and procedures to update OS for the device.
robuser007 said:
Oneplus Nord
Click to expand...
Click to collapse
old phone!!! not this one

kirichen said:
In general, 3 things are needed to use Android GSI:
a device is fully Treble compliant (Treble support is mandatory for devices launched with Android 9 or later).
the device's bootloader could be unlocked.
the tools and procedures to update OS for the device.
adb devices
adb reboot bootloader
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system systemA11.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Thanks, I'll try, can't boot to the system and booting to a recovery is crashing my phone (f.e
fastboot boot twrpname.img). I guess it's a hardbrick.
I get an error trying this command:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --disable-verity --disable-verification flash vbmeta D:\P2a42_S244_170725_ROW_fastboot\P2a42_S244_170725_ROW_fastboot\SW\vbmeta.img
fastboot: unknown option -- disable-verity
https://sourceforge.net/projects/treblerom/files/LiR/2022.03.25/lir-v316-220325-arm64-bvZ.img.xz is ok to use?
It's my old backup phone that once crashed, not for the Nord I have.

robuser007 said:
How do I flash this? I only find an img file
which one do I need?
Click to expand...
Click to collapse
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system systemA11.img
fastboot -w
fastboot reboot
robuser007 said:
is ok to use?
Click to expand...
Click to collapse
it depends on screenshot of TrebleInfo.apk
robuser007 said:
my old backup phone that once crashed
Click to expand...
Click to collapse
what is the name of your phone? Have you backup? Can you give me the link to google disk with back up?
robuser007 said:
fastboot: unknown option -- disable-verity
Click to expand...
Click to collapse
fastboot --version
fastboot version 33.0.2-8557947 ?????
Did you unlock your bootloader?
fastboot getvar unlocked
(true OR false) (yes OR no) ?????

kirichen said:
fastboot --version
fastboot version 33.0.2-8557947 ?????
Did you unlock your bootloader?
https://www.getdroidtips.com/unlock-bootloader-mediatek-device/
fastboot getvar unlocked
(true OR false) (yes OR no) ?????
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar unlocked
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
unlocked: unlocked
finished. total time: 0.025s
It's a Lenovo p2 (Eu version). I don't have any backup anymore since I couldn,'t boot into recovery.

robuser007 said:
It's a Lenovo p2 (Eu version
Click to expand...
Click to collapse
forget about all we talk before....It was for Android 9 and higher A10, A11/ Your firmware is Android 6 or 7
Яндекс
Найдётся всё
disk.yandex.ru
I don't know what was your official firmware , here is the instruction to flash your phone
--------------------------------------------
Instruction to flash a firmware via fastboot
For unlocked devices!
Applies to firmware 6/62;7/232;7/233;7/244;7/251
1. Download the firmware, unpack it on a PC.
2. Install all drivers for ADB/FASTBOOT operation.
3. Download and unpack the attached archive- Attached file RESTORE_UNLOCK_DEVICES.zip ( 613.53 KB )
4. Move the files from the RESTORE_UNLOCK_DEVICES folder to the SW folder with the firmware files. In firmware 251, move the files to the Images folder.
5. Reboot the phone into FASTBOOT mode (disconnect the phone from the PC, turn off the phone, hold the power and volume down at the same time) and connect the phone to the PC.
6. Run the shortcut - START in the firmware folder.bat
Wait for the firmware installation to finish. The phone will reboot into the system .
7. After switching on, apply the regional code by dialing ###682 in the dialer#
Addition:
If there is a need to flash the phone without losing user data, then in the START file.bat you need to delete the line - fastboot flash userdata userdata.img
To do this, right-click on the file and open it using any text editor on a PC. Then save it.
robuser007 said:
since I couldn,'t boot into recovery.
Click to expand...
Click to collapse
May be simple
fastboot -w
help you? erase all your data( wipe, format) and you can boot into system.
Lenovo Vibe P2 - Получение ROOT прав
Получение ROOT прав на Lenovo Vibe P2 - Android 6.0 Установка TWRP и получение ROOT возможно только после разблокировки загрузчика! ...
lenovo--forums-ru.translate.goog

kirichen said:
May be simple
fastboot -w
help you? erase all your data( wipe, format) and you can boot into system.
Lenovo Vibe P2 - Получение ROOT прав
Получение ROOT прав на Lenovo Vibe P2 - Android 6.0 Установка TWRP и получение ROOT возможно только после разблокировки загрузчика! ...
lenovo--forums-ru.translate.goog
Click to expand...
Click to collapse
Tried, but didn't help
fastboot boot d:\recovery_kuntao.img f.e. crashes my fastboot and doesn't boot to recovery.
kirichen said:
forget about all we talk before....It was for Android 9 and higher A10, A11/ Your firmware is Android 6 or 7
Яндекс
Найдётся всё
disk.yandex.ru
I don't know what was your official firmware , here is the instruction to flash your phone
--------------------------------------------
Instruction to flash a firmware via fastboot
For unlocked devices!
Applies to firmware 6/62;7/232;7/233;7/244;7/251
1. Download the firmware, unpack it on a PC.
2. Install all drivers for ADB/FASTBOOT operation.
3. Download and unpack the attached archive- Attached file RESTORE_UNLOCK_DEVICES.zip ( 613.53 KB )
4. Move the files from the RESTORE_UNLOCK_DEVICES folder to the SW folder with the firmware files. In firmware 251, move the files to the Images folder.
5. Reboot the phone into FASTBOOT mode (disconnect the phone from the PC, turn off the phone, hold the power and volume down at the same time) and connect the phone to the PC.
6. Run the shortcut - START in the firmware folder.bat
Wait for the firmware installation to finish. The phone will reboot into the system .
7. After switching on, apply the regional code by dialing ###682 in the dialer#
Addition:
If there is a need to flash the phone without losing user data, then in the START file.bat you need to delete the line - fastboot flash userdata userdata.img
To do this, right-click on the file and open it using any text editor on a PC. Then save it.
Click to expand...
Click to collapse
Spoiler
PS D:\P2a42_S244_170725_ROW_fastboot\P2a42_S244_170725_ROW_fastboot\SW> .\start.bat
Active code page: 1251
ECHO is off.
...
OKAY [ -0.000s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'partition' (33 KB)...
OKAY [ 0.047s]
writing 'partition'...
OKAY [ 0.031s]
finished. total time: 0.079s
target reported max download size of 536870912 bytes
sending 'boot' (23381 KB)...
OKAY [ 0.655s]
writing 'boot'...
OKAY [ 0.186s]
finished. total time: 0.852s
target reported max download size of 536870912 bytes
sending 'recovery' (27119 KB)...
OKAY [ 0.736s]
writing 'recovery'...
OKAY [ 0.248s]
finished. total time: 1.000s
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.459s]
writing 'dsp'...
OKAY [ 0.129s]
finished. total time: 0.607s
target reported max download size of 536870912 bytes
sending 'system' (257817 KB)...
OKAY [ 6.948s]
writing 'system'...
OKAY [ 2.095s]
finished. total time: 9.073s
target reported max download size of 536870912 bytes
sending 'system' (257941 KB)...
OKAY [ 7.120s]
writing 'system'...
OKAY [ 1.784s]
finished. total time: 8.904s
target reported max download size of 536870912 bytes
sending 'system' (257344 KB)...
OKAY [ 7.215s]
writing 'system'...
OKAY [ 1.846s]
finished. total time: 9.061s
target reported max download size of 536870912 bytes
sending 'system' (257491 KB)...
OKAY [ 7.029s]
writing 'system'...
OKAY [ 1.832s]
finished. total time: 8.887s
target reported max download size of 536870912 bytes
sending 'system' (260519 KB)...
OKAY [ 7.220s]
writing 'system'...
OKAY [ 1.953s]
finished. total time: 9.185s
target reported max download size of 536870912 bytes
sending 'system' (257935 KB)...
OKAY [ 7.024s]
writing 'system'...
OKAY [ 1.890s]
finished. total time: 8.914s
target reported max download size of 536870912 bytes
sending 'system' (254719 KB)...
OKAY [ 7.045s]
writing 'system'...
OKAY [ 2.001s]
finished. total time: 9.047s
target reported max download size of 536870912 bytes
sending 'system' (261754 KB)...
OKAY [ 7.188s]
writing 'system'...
OKAY [ 2.119s]
finished. total time: 9.322s
target reported max download size of 536870912 bytes
sending 'system' (262142 KB)...
OKAY [ 7.140s]
writing 'system'...
OKAY [ 1.936s]
finished. total time: 9.077s
target reported max download size of 536870912 bytes
sending 'system' (261321 KB)...
OKAY [ 7.251s]
writing 'system'...
OKAY [ 1.841s]
finished. total time: 9.092s
target reported max download size of 536870912 bytes
sending 'system' (254468 KB)...
OKAY [ 7.046s]
writing 'system'...
OKAY [ 1.812s]
finished. total time: 8.873s
target reported max download size of 536870912 bytes
sending 'system' (262142 KB)...
OKAY [ 7.205s]
writing 'system'...
OKAY [ 1.841s]
finished. total time: 9.061s
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 7.234s]
writing 'system'...
OKAY [ 1.890s]
finished. total time: 9.139s
target reported max download size of 536870912 bytes
sending 'system' (260859 KB)...
OKAY [ 7.218s]
writing 'system'...
OKAY [ 1.927s]
finished. total time: 9.145s
target reported max download size of 536870912 bytes
sending 'system' (69256 KB)...
OKAY [ 1.910s]
writing 'system'...
OKAY [ 0.475s]
finished. total time: 2.394s
target reported max download size of 536870912 bytes
sending 'userdata' (297806 KB)...
OKAY [ 8.046s]
writing 'userdata'...
OKAY [ 2.155s]
finished. total time: 10.216s
target reported max download size of 536870912 bytes
sending 'fsg' (304 KB)...
OKAY [ 0.031s]
writing 'fsg'...
OKAY [ 0.016s]
finished. total time: 0.077s
erasing 'cache'...
OKAY [ 0.032s]
finished. total time: 0.032s
...
OKAY [ -0.000s]
finished. total time: 0.016s
Press any key to continue . . .
rebooting...
finished. total time: 0.016s
PS D:\P2a42_S244_170725_ROW_fastboot\P2a42_S244_170725_ROW_fastboot\SW>
Done, boot stays on Lenovo boot logo, I guess it's really hard bricked (something must be broken). Thanks for your help!

[ROM][13][amogus] AOSP 13.0

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?