[ROM][13][amogus] AOSP 13.0

[uwucake2020]

is there currently a way to install gapps?

 

[uwucake2020]

Never mind i just downgraded to stock A10 with a stocm ROM i just got from Lolinet.com

Flashed using MotoFlashPro and it worked

What phone and codename? I tried the same but just got into a bootloop tho.
(Moto G8 XT2045-2 rav)

 

[uwucake2020]

I got Gapps to work using magisk.
Just in case anyone needs it here is how I did it:
BEFORE DOING THIS BACK UP YOUR DATA, JUST IN CASE YOU GET INTO A BOOTLOOP AND NEED TO FACTORY RESET IT!

Please note that these Gapps do have an issue that I noticed.
I noticed that my device boot loops after restarting from safe mode, so try not to use safe mode at all. From what I tested, it seems that only factory reset fixes it, I couldn't even boot into safe mode again.

Now onto the steps:

Basic Gapps:​

1: Install Magisk managerlike a normal app (using a pc 'adb install magisk.apk' or simply transfer it to the phone and install it that way. 2: You will need to get the boot.img which you can get by unzipping the update.zip 3: Transfer the .img file to the phone. 4: Open Magisk manager, click install next to "Magisk" 5: Select "Select and patch a file" then choose the boot.img and let it do it's thing. 6: Transfer the Magisk-modified boot.img to the pc. 7: Reboot your phone into bootloader or fastboot and flash the modified boot image. Upon boot check the Magisk app and it should say "installed {version number}" 8: Now that you (hopefully) have root you can go and download the MagiskGapps zip file. (this is A13_alpha) Do not download the whole folder, select the version you want!! 9: Once you have downloaded the zip file go into Magisk manager, and on the bottom right click on modules -> Install from storage and select the MagiskGapps.zip 10: Wait for it to finish, reboot your phone and you should (if everything went well) now have Root and Gapps.

Play Store Fix:​

The following does not appear to be necessary, as Gapps seem to work just fine.

Spoiler: Play Store Fix

The following are the steps which fixed my issue, but your might be different. Google Play Store fix: 1: Download a Play Store apk. (I used this one) 2: Try to install it and open it 3: Open Play Store and log in if necessary. 4: In case you get an error at the end (after you type in the email and password) just click on try again, and if the second time it says that account is already on your device, just close the app, remove from recent apps and reopen it. I have no way of knowing if it works with other devices or other Play Store apks but this worked for me.

Hope this helps someone.

 

[spiral777]

I got Gapps to work using magisk.
Just in case anyone needs it here is how I did it:
BEFORE DOING THIS BACK UP YOUR DATA, JUST IN CASE YOU GET INTO A BOOTLOOP AND NEED TO FACTORY RESET IT!

Also before you start please note that the Play Store may not be included, but the google services are working, so install another app store like Aurora (basically a modified Play Store client) from F-droid.
Found a fix, I will put it on the bottom of this post.

Basic Gapps:​

1: Install [URL='https://magiskmanager.com/downloading-magisk-manager/']Magisk manager[/URL] like a normal app (using a pc 'adb install magisk.apk' or simply transfer it to the phone and install it that way. 2: You will need to get the boot.img which you can get by unzipping the update.zip 3: Transfer the .img file to the phone. 4: Open Magisk manager, click install next to "Magisk" 5: Select "Select and patch a file" then choose the boot.img and let it do it's thing. 6: Transfer the Magisk-modified boot.img to the pc. 7: Reboot your phone into bootloader or fastboot and flash the modified boot image. Upon boot check the Magisk app and it should say "installed {version number}" 8: Now that you (hopefully) have root you can go and download the MagiskGapps zip file. (this is A13_alpha) Do not download the whole folder, select the version you want!! 9: Once you have downloaded the zip file go into Magisk manager, and on the bottom right click on modules -> Install from storage and select the MagiskGapps.zip 10: Wait for it to finish, reboot your phone and you should (if everything went well) now have Root and Gapps.

Play Store Fix:​

The following are the steps which fixed my issue, but your might be different. Google Play Store fix: 1: Download a Play Store apk. (I used this one) 2: Try to install it and open it 3: In case the app closes almost instantly you can try going to the Magisk Manager -> go to the settings (top right) and scroll down untill you find 'Systemless hosts' EDIT: I don't know if this fixed it or the reboot, so try only rebooting before this!
4: Click on it and it will say that a new module was installed, verify that in the modules tab and if it is there reboot your device. 5: Open Play Store and log in if necessary. 6: In case you get an error at the end (after you type in the email and password) just click on try again, and if the second time it says that account is already on your device, just close the app, remove from recent apps and reopen it. I have no way of knowing if it works with other devices or other Play Store apks but this worked for me.


Hope this helps someone.

Thank you for figuring this out if no other solutions come along I'll give this a try

 

[uwucake2020]

Ok so this doesn't have anything to do with GApps but the camera app is too old/basic and i tried to follow a "tutorial" on xda, and it's not working. Also when i go to the camera settings it detects only 2 modules, the back camera with "system id = 0" and front camera with "system id =1".
So I am just wondering can I get it to work or is something that has to do with the A13? Is it a known issue?

 

[XSOARER]

Ok so this doesn't have anything to do with GApps but the camera app is too old/basic and i tried to follow a "tutorial" on xda, and it's not working. Also when i go to the camera settings it detects only 2 modules, the back camera with "system id = 0" and front camera with "system id =1".
So I am just wondering can I get it to work or is something that has to do with the A13? Is it a known issue?

It is a known issue. I think there is a workaround to it, using specific camera apps, probably those you already tried, but I very well may be wrong.

 

[Electimon]

Jan 26:
January Security Patch

 

[Bmonek]

Jan 26:
January Security Patch

I have a question, I'm not very experienced, for which I'm sorry
please tell me how should i upgrade my system to a newer version without losing data
should i normal flash update.zip via fastboot?
sr for bad english

 

[Electimon]

I have a question, I'm not very experienced, for which I'm sorry
please tell me how should i upgrade my system to a newer version without losing data
should i normal flash update.zip via fastboot?
sr for bad english

Yes just follow the guide without executing the wipe data steps

 

[Bmonek]

Yes just follow the guide without executing the wipe data steps

should i install magisk again with new boot image?

 

[thatguy222]

Weird issue that I've never seen on another ROM, when I put in a private DNS address in my network settings, only websites I've been to before will work but everything else cannot be reached. I'm using this exact same DNS server address on multiple other devices with no issue.

 

[HeyImJ]

I got Gapps to work using magisk.
Just in case anyone needs it here is how I did it:
BEFORE DOING THIS BACK UP YOUR DATA, JUST IN CASE YOU GET INTO A BOOTLOOP AND NEED TO FACTORY RESET IT!

Also before you start please note that the Play Store may not be included, but the google services are working, so install another app store like Aurora (basically a modified Play Store client) from F-droid.
Found a fix, I will put it on the bottom of this post.

Basic Gapps:​

1: Install Magisk managerlike a normal app (using a pc 'adb install magisk.apk' or simply transfer it to the phone and install it that way. 2: You will need to get the boot.img which you can get by unzipping the update.zip 3: Transfer the .img file to the phone. 4: Open Magisk manager, click install next to "Magisk" 5: Select "Select and patch a file" then choose the boot.img and let it do it's thing. 6: Transfer the Magisk-modified boot.img to the pc. 7: Reboot your phone into bootloader or fastboot and flash the modified boot image. Upon boot check the Magisk app and it should say "installed {version number}" 8: Now that you (hopefully) have root you can go and download the MagiskGapps zip file. (this is A13_alpha) Do not download the whole folder, select the version you want!! 9: Once you have downloaded the zip file go into Magisk manager, and on the bottom right click on modules -> Install from storage and select the MagiskGapps.zip 10: Wait for it to finish, reboot your phone and you should (if everything went well) now have Root and Gapps.

Play Store Fix:​

The following are the steps which fixed my issue, but your might be different. Google Play Store fix: 1: Download a Play Store apk. (I used this one) 2: Try to install it and open it 3: In case the app closes almost instantly you can try going to the Magisk Manager -> go to the settings (top right) and scroll down untill you find 'Systemless hosts' EDIT: I don't know if this fixed it or the reboot, so try only rebooting before this!
4: Click on it and it will say that a new module was installed, verify that in the modules tab and if it is there reboot your device. 5: Open Play Store and log in if necessary. 6: In case you get an error at the end (after you type in the email and password) just click on try again, and if the second time it says that account is already on your device, just close the app, remove from recent apps and reopen it. I have no way of knowing if it works with other devices or other Play Store apks but this worked for me.


Hope this helps someone.

Thank you very much worked just fine. Also the reboot worked and I didnt need systemless hosts

 

[Electimon]

Feb 27:
Feb security patch

Check OP

 

[QuantumDumb]

Hi -

(bootloader) Unsupported super image format, rejecting...

What happened?

aosp_amogus-img-23022705.zip

--------------------------------------------
Bootloader Version...: MBM-3.0-rav_retus-e792a32534b-220524
Baseband Version.....: M6125_43.45.03.49R RAV_NA_CUST
Serial Number........: [snip]
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.246s]
(bootloader) snapshot-update-status: not found
extracting boot.img (64 MB) to disk... took 0.105s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 3.516s]
Writing 'boot_a' OKAY [ 0.994s]
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.058s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (24576 KB) OKAY [ 1.324s]
Writing 'dtbo_a' OKAY [ 0.384s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
extracting recovery.img (64 MB) to disk... took 0.121s
archive does not contain 'recovery.sig'
Sending 'recovery_a' (65536 KB) OKAY [ 3.523s]
Writing 'recovery_a' OKAY [ 1.378s]
extracting vbmeta.img (0 MB) to disk... took 0.003s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 21
OKAY [ 0.010s]
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
(bootloader) super-partition-name: not found
extracting product.img (147 MB) to disk... took 0.978s
extracting system.img (580 MB) to disk... took 2.460s
archive does not contain 'system_other.img'
extracting vendor.img (196 MB) to disk... took 0.829s
archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/2 (745236 KB) OKAY [ 39.796s]
Writing 'super' (bootloader) Unsupported super image format, rejecting...
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed

 

[QuantumDumb]

aosp_amogus-img-23022705.zip

 

[Electimon]

Hi -

(bootloader) Unsupported super image format, rejecting...

What happened?

aosp_amogus-img-23022705.zip

--------------------------------------------
Bootloader Version...: MBM-3.0-rav_retus-e792a32534b-220524
Baseband Version.....: M6125_43.45.03.49R RAV_NA_CUST
Serial Number........: [snip]
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.246s]
(bootloader) snapshot-update-status: not found
extracting boot.img (64 MB) to disk... took 0.105s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 3.516s]
Writing 'boot_a' OKAY [ 0.994s]
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.058s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (24576 KB) OKAY [ 1.324s]
Writing 'dtbo_a' OKAY [ 0.384s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
extracting recovery.img (64 MB) to disk... took 0.121s
archive does not contain 'recovery.sig'
Sending 'recovery_a' (65536 KB) OKAY [ 3.523s]
Writing 'recovery_a' OKAY [ 1.378s]
extracting vbmeta.img (0 MB) to disk... took 0.003s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 21
OKAY [ 0.010s]
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
(bootloader) super-partition-name: not found
extracting product.img (147 MB) to disk... took 0.978s
extracting system.img (580 MB) to disk... took 2.460s
archive does not contain 'system_other.img'
extracting vendor.img (196 MB) to disk... took 0.829s
archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/2 (745236 KB) OKAY [ 39.796s]
Writing 'super' (bootloader) Unsupported super image format, rejecting...
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed

Use platform tools r32, google broke updatepackages on the latest one.

 

[QuantumDumb]

Use platform tools r32, google broke updatepackages on the latest one.

OK.

Using platform-tools_r31.0.3-windows
Using aosp_amogus-img-23022705.zip
Using Moto G Fast

Can't find r32. Found r31 here: https://androidsdkmanager.azurewebsites.net/Platformtools

In the defined process:

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
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

As shown below, at <============== reboots to fastbootd, but then does not re-mount the device for subsequent fastboot flash product product.img

Tried fastboot flash product product.img from another commend line, but bonks.

extracting super_empty.img (0 MB) to disk... took 0.001s

suggests---perhaps---the image was not built and an empty image was generated???

Any thoughts??

Perhaps Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 21

results in a system that can't bootload

=====================================================

--------------------------------------------
Bootloader Version...: MBM-3.0-rav_retus-e792a32534b-220524
Baseband Version.....: M6125_43.45.03.49R RAV_NA_CUST
Serial Number........: [snip]
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Setting current slot to 'a' OKAY [ 0.222s]
(bootloader) snapshot-update-status: not found
extracting boot.img (64 MB) to disk... took 0.156s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 3.603s]
Writing 'boot_a' OKAY [ 0.999s]
extracting dtbo.img (24 MB) to disk... took 0.045s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (24576 KB) OKAY [ 1.368s]
Writing 'dtbo_a' OKAY [ 0.417s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
extracting recovery.img (64 MB) to disk... took 0.151s
archive does not contain 'recovery.sig'
Sending 'recovery_a' (65536 KB) OKAY [ 3.642s]
Writing 'recovery_a' OKAY [ 1.346s]
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' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 21
OKAY [ 0.010s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >

 

[Skib32]

does no fix for Speakerphone ?

 

[uwucake2020]

DT2W has been fixed for RAV (HIMAX) variants of amogus

I just updated but DT2W does not seem to work? I have an xt2045-2 (rav) board and have the option enabled in the settings but still nothing. I know that it is possible as TWRP fully shuts the screen off and turns on whenever the screen is touched so it's not a hardware issue it seems. Is there anything that I can try to fix it?

 

[Electimon]

I just updated but DT2W does not seem to work? I have an xt2045-2 (rav) board and have the option enabled in the settings but still nothing. I know that it is possible as TWRP fully shuts the screen off and turns on whenever the screen is touched so it's not a hardware issue it seems. Is there anything that I can try to fix it?

Twrp only does that because it doesn't turn the panel off it sets it to 0 brightness upon idle. On some panels dt2w isn't supported currently.