Question [ROM][13][borneo] AOSP 13 [Monthly Builds]

Search This thread

Electimon

Recognized Developer
AOSP 13
This is a moto-common project release under the codename borneo
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/

What's Moto-Common?
Moto-Common is a set of trees common to every 4.14+ QCOM Motorola device, making it easier to do bringups based on SODP.

What's AOSP?
AOSP is Android as Google publish without other modifications.

Known issues:
  • You tell me
  • IF YOU DONT HAVE SLOT B FILLED YOU CAN BRICK
Instructions :
  • Download the latest build
  • Reboot to bootloader
  • Code:
    fastboot -w
  • Code:
    fastboot update PACKAGE.zip
  • You may need to install drivers in device manager after running the last command

Downloads :

Telegram Groups

Source Code:
https://github.com/moto-common

Changelog:
Jan 25th 2023: Initial release on XDA

Feb 27th 2023: Pushed Feb update
 
Last edited:

sdembiske

Senior Member
Jan 4, 2015
1,389
1,901
Hi I recently installed this as its the only ROM currently available for my phone that I've seen, and I'm just wondering how would someone go about installing gapps?
@Electimon

See the following links:
- https://stackoverflow.com/questions/71001696/how-to-include-opengapps-in-aosp-12-build
Use tau instead of sigma for aosp-13 (in the notes at bottom checked answer)\

- https://github.com/opengapps/aosp_build

- https://www.droidwin.com/how-to-download-and-install-android-13-gapps/
Note: Requires a working TWRP
 
  • Like
Reactions: jumpup

JR4450

New member
Feb 5, 2023
1
0
Does this rom bring unlimited google photos???
 
Last edited:

Electimon

Recognized Developer
@Electimon Do you know anything about "range restricted" in Firehose loaders for EDL?
It prevents you from reading (and probably writing?) most partitions in EDL.
If your CID is 0xff or if you have a flag set (which I haven't traced down yet) you can bypass the restriction.
Yeah thats known, sadly CID partition is signed and the flag is usually burned qfuse in the SoC which is burnt on all retail devices.
 
  • Like
Reactions: Renate

Renate

Recognized Contributor / Inactive Recognized Dev
... the flag is usually burned qfuse ...
I'm using the Firehose loader size=609,484, MD5=153a904c54963cb21b901b0dd10f0641
I can see that the CID is validated by cert chains.
But I also see lots of stuff like "ssm_flash_cid", "write_cid_store".
I see a bunch of smc (Secure Monitor Calls) and a bunch of SCM (Secure Channel Monitor) calls and functions for reading/writing fuses.
I also see one small function that writes a byte into memory that can disable restrictions.
It seems like a back door, but I haven't seen what activates it.
 

Electimon

Recognized Developer
having an issue where I cant flash it, its saying that it cannot flash

if you want to reach out to me quickly, DM me on discord, Merith#5829
Use platform-tools r32, in the latest version google broke fastboot update.
 

merith-tk

Member
Aug 27, 2020
11
1
Use platform-tools r32, in the latest version google broke fastboot update.
Small problem, phone has fastbootd, bootloader, recovery, and system (system being rom)
when you tell the phone to boot to fastboot, it goes to fastbootd which does not show up in fastboot.exe's list,
but if I send it to bootloader, it shows up


Edit, Updating drivers fixed it, IOBit Driver notified of out of date driver
 

merith-tk

Member
Aug 27, 2020
11
1
Use platform-tools r32, in the latest version google broke fastboot update.
Still broken, just differently

It flashed, rebooted, showed the AOSP android boot animation, rebooted then brought me to stock recovery (TWRP not flashed) saying the system was corrupt and could not boot


Reflashing fixed it but I dont have Cell Service (I have an carrier unlocked device on USC network)
 
Last edited:

Electimon

Recognized Developer
Still broken, just differently

It flashed, rebooted, showed the AOSP android boot animation, rebooted then brought me to stock recovery (TWRP not flashed) saying the system was corrupt and could not boot


Reflashing fixed it but I dont have Cell Service (I have an carrier unlocked device on USC network)
Wipe data in recovery and let me know if its still an issue
 

Top Liked Posts