Development [ROM][13][borneo] AOSP 13

Search This thread
By:
Advanced…
H

hamidrezarezai

Member
Jun 12, 2020
7
0
Hey , thanks for the rom. it gave a new life to my phone. the only problem i have is with gps. i dont know how to make it work properly. let me explain. in apps like Uber, lift even though they have location access it doesn't get location. in google map it is very hit and miss sometime it works sometimes doesn't.

I downloaded the app called GPS LOCKER in there it shows I do have a 3D GPS lock. but when I open the Google map sometimes it has a lock sometimes it doesn't even though I do have a 3d lock in the other app.

and in Uber and lift, and Tineder no matter what I do I can't get gps even though they have location access permission.

any help/support?
 
H

hamidrezarezai

Member
Jun 12, 2020
7
0
the issue gets fixed if I add the following in the adb shell.

pm grant com.google.android.lyft android.permission.ACCESS_FINE_LOCATION
pm grant com.google.android.lyft android.permission.ACCESS_COARSE_LOCATION

so i am thinking the permission for location access has some sort of bug
 
G

graewulf1

Senior Member
Apr 19, 2012
177
36
AT&T Samsung Galaxy S5
ZTE Axon 7 Mini
bbbbbbbbbbbbbbbbbbbb said:
Yes, it works. Twrp also works to an extent (https://forum.xda-developers.com/t/...7-0-11-borneo-android-11-based.4559849/unread), even on 13, but I used adb to flash aosp 13 so idk if it'd work for that. Wasn't able to use twrp or adb to flash gapps, but that might've been me doing something wrong. I was able to use it to flash magisk, however. Don't know if you're willing to root, but I used this to get gapps instead: https://github.com/wacko1805/MagiskGapps. This seems to have made it a little glitchy, though. Core didn't work, so I used go. I also tried full and that worked. Stock exists (https://mirrors.lolinet.com/firmware/motorola/borneo/official/), but I couldn't get it to work, so I just used Lenovo RSA, which worked.
Click to expand...
Click to collapse
Before I do this, you say you were able to flash AOSP using ADB, and TWRP to flash Magisk? I just want to be sure I read that right before I try this.
 
G

graewulf1

Senior Member
Apr 19, 2012
177
36
AT&T Samsung Galaxy S5
ZTE Axon 7 Mini
i get this error when flashing the ROM

Sending sparse 'super' 1/3 (785608 KB) OKAY [ 17.648s]
Writing 'super' (bootloader) Unsupported super image format, rejecting...
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
 
G

graewulf1

Senior Member
Apr 19, 2012
177
36
AT&T Samsung Galaxy S5
ZTE Axon 7 Mini
graewulf1 said:
i get this error when flashing the ROM

Sending sparse 'super' 1/3 (785608 KB) OKAY [ 17.648s]
Writing 'super' (bootloader) Unsupported super image format, rejecting...
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
--------------------------------------------
(bootloader) version-bootloader[0]: MBM-3.0-borneo_retail-22355d27121-23
(bootloader) version-bootloader[1]: 0201
Bootloader Version...: Done
Baseband Version.....: HA10_29.11.02.95.02R BORNEO_NA_CUST
Serial Number........: ZY22BVMVLR
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Setting current slot to 'b' OKAY [ 0.242s]
(bootloader) snapshot-update-status: not found
extracting boot.img (96 MB) to disk... took 0.144s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.162s]
Writing 'boot_b' OKAY [ 0.836s]
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.040s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (24576 KB) OKAY [ 0.541s]
Writing 'dtbo_b' OKAY [ 0.182s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
extracting recovery.img (100 MB) to disk... took 0.159s
archive does not contain 'recovery.sig'
Sending 'recovery_b' (102400 KB) OKAY [ 2.251s]
Writing 'recovery_b' OKAY [ 1.158s]
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' (bootloader) WARNING: vbmeta_b anti rollback downgrade, 0 vs 20
OKAY [ 0.043s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_system_b' OKAY [ 0.006s]
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'vendor_kernel_boot.img'
extracting boot.img (96 MB) to disk... took 0.174s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.159s]
Writing 'boot_b' OKAY [ 0.837s]
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (24576 KB) OKAY [ 0.540s]
Writing 'dtbo_b' OKAY [ 0.175s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
extracting recovery.img (100 MB) to disk... took 0.184s
archive does not contain 'recovery.sig'
Sending 'recovery_b' (102400 KB) OKAY [ 2.250s]
Writing 'recovery_b' OKAY [ 1.173s]
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' (bootloader) WARNING: vbmeta_b anti rollback downgrade, 0 vs 20
OKAY [ 0.015s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_system_b' OKAY [ 0.006s]
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.000s
(bootloader) super-partition-name: not found
extracting product.img (269 MB) to disk... took 1.218s
[liblp] Partition product_b will resize from 0 bytes to 282415104 bytes
extracting system.img (1083 MB) to disk... took 5.270s
[liblp] Partition system_b will resize from 0 bytes to 1135669248 bytes
archive does not contain 'system_other.img'
extracting vendor.img (527 MB) to disk... took 3.552s
[liblp] Partition vendor_b will resize from 0 bytes to 552931328 bytes
archive does not contain 'vendor_other.img'
archive does not contain 'system_other.img'
archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/3 (785608 KB) OKAY [ 17.648s]
Writing 'super' (bootloader) Unsupported super image format, rejecting...
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
 
H

hamidrezarezai

Member
Jun 12, 2020
7
0
graewulf1 said:
--------------------------------------------
(bootloader) version-bootloader[0]: MBM-3.0-borneo_retail-22355d27121-23
(bootloader) version-bootloader[1]: 0201
Bootloader Version...: Done
Baseband Version.....: HA10_29.11.02.95.02R BORNEO_NA_CUST
Serial Number........: ZY22BVMVLR
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Setting current slot to 'b' OKAY [ 0.242s]
(bootloader) snapshot-update-status: not found
extracting boot.img (96 MB) to disk... took 0.144s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.162s]
Writing 'boot_b' OKAY [ 0.836s]
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.040s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (24576 KB) OKAY [ 0.541s]
Writing 'dtbo_b' OKAY [ 0.182s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
extracting recovery.img (100 MB) to disk... took 0.159s
archive does not contain 'recovery.sig'
Sending 'recovery_b' (102400 KB) OKAY [ 2.251s]
Writing 'recovery_b' OKAY [ 1.158s]
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' (bootloader) WARNING: vbmeta_b anti rollback downgrade, 0 vs 20
OKAY [ 0.043s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_system_b' OKAY [ 0.006s]
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'vendor_kernel_boot.img'
extracting boot.img (96 MB) to disk... took 0.174s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.159s]
Writing 'boot_b' OKAY [ 0.837s]
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (24576 KB) OKAY [ 0.540s]
Writing 'dtbo_b' OKAY [ 0.175s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
extracting recovery.img (100 MB) to disk... took 0.184s
archive does not contain 'recovery.sig'
Sending 'recovery_b' (102400 KB) OKAY [ 2.250s]
Writing 'recovery_b' OKAY [ 1.173s]
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' (bootloader) WARNING: vbmeta_b anti rollback downgrade, 0 vs 20
OKAY [ 0.015s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_system_b' OKAY [ 0.006s]
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.000s
(bootloader) super-partition-name: not found
extracting product.img (269 MB) to disk... took 1.218s
[liblp] Partition product_b will resize from 0 bytes to 282415104 bytes
extracting system.img (1083 MB) to disk... took 5.270s
[liblp] Partition system_b will resize from 0 bytes to 1135669248 bytes
archive does not contain 'system_other.img'
extracting vendor.img (527 MB) to disk... took 3.552s
[liblp] Partition vendor_b will resize from 0 bytes to 552931328 bytes
archive does not contain 'vendor_other.img'
archive does not contain 'system_other.img'
archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/3 (785608 KB) OKAY [ 17.648s]
Writing 'super' (bootloader) Unsupported super image format, rejecting...
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
i remember encountering something like this, i think 2 things solved it, install a few adb drivers on your pc (mine was recognized but still I think was missing something ) and then use the exact version of the adb which was mentioned in one of the previous comment (i think was 1.4.3 ) the newer one changed something and broke something.

lastly, i remember at some point it was rejecting the rom no matter what i did, i installed the latest official rom with RSD LITE (i also went in the system and got the latest updates as well ) then installed the rom and it worked.

so try this three thing and see if it works if not someone else who know more might be able to help you.
 
G

graewulf1

Senior Member
Apr 19, 2012
177
36
AT&T Samsung Galaxy S5
ZTE Axon 7 Mini
hamidrezarezai said:
i remember encountering something like this, i think 2 things solved it, install a few adb drivers on your pc (mine was recognized but still I think was missing something ) and then use the exact version of the adb which was mentioned in one of the previous comment (i think was 1.4.3 ) the newer one changed something and broke something.

lastly, i remember at some point it was rejecting the rom no matter what i did, i installed the latest official rom with RSD LITE (i also went in the system and got the latest updates as well ) then installed the rom and it worked.

so try this three thing and see if it works if not someone else who know more might be able to help you.
Click to expand...
Click to collapse
Thanks for the help but i cannot get this to work. I am using platform-tools r32, installed the optional windows updates, rebooted, same problem. I tried the RSD lite tool but it doesn't recognize the phone and there are no docs on it anywhere. I have flashed back to stock rom using RSA several times, so I know it works that way, but I cannot get this ROM to load no matter what I do.
 
H

hamidrezarezai

Member
Jun 12, 2020
7
0
graewulf1 said:
Thanks for the help but i cannot get this to work. I am using platform-tools r32, installed the optional windows updates, rebooted, same problem. I tried the RSD lite tool but it doesn't recognize the phone and there are no docs on it anywhere. I have flashed back to stock rom using RSA several times, so I know it works that way, but I cannot get this ROM to load no matter what I do.
Click to expand...
Click to collapse
as i said did you try adb 1.4.3? in later version of adb something is changed that is not compatible with this ROM.

if yes idk. maybe someone else who know more could help you.
 
G

graewulf1

Senior Member
Apr 19, 2012
177
36
AT&T Samsung Galaxy S5
ZTE Axon 7 Mini
hamidrezarezai said:
as i said did you try adb 1.4.3? in later version of adb something is changed that is not compatible with this ROM.

if yes idk. maybe someone else who know more could help you.
Click to expand...
Click to collapse
ok i must be missing something. the only adb I can find 1.4.3 is an installer, but it doesn't seem to install anything. platform-tools doesn't install, you just run it.

1686145233088.png
 
H

hamidrezarezai

Member
Jun 12, 2020
7
0
graewulf1 said:
ok i must be missing something. the only adb I can find 1.4.3 is an installer, but it doesn't seem to install anything. platform-tools doesn't install, you just run it.

View attachment 5927575
Click to expand...
Click to collapse
okay now use the platform-tools_r31.0.3-windows and see if it works but just try it with that exact version!

basically go to the folder of platform-tools_r31.0.3-windows open PowerShell in there and use ./fastboot update (the name of the rom zip file ).zip
 
G

graewulf1

Senior Member
Apr 19, 2012
177
36
AT&T Samsung Galaxy S5
ZTE Axon 7 Mini
hamidrezarezai said:
okay now use the platform-tools_r31.0.3-windows and see if it works but just try it with that exact version!

basically go to the folder of platform-tools_r31.0.3-windows open PowerShell in there and use ./fastboot update (the name of the rom zip file ).zip
Click to expand...
Click to collapse
THANK YOU!!!!

Now, that having been said, I can't make calls now. It recognized my sim card and phone number but says emergency calls only. It complains about a hardware error when it boots. :(

Getting closer!
 
G

graewulf1

Senior Member
Apr 19, 2012
177
36
AT&T Samsung Galaxy S5
ZTE Axon 7 Mini
merith-tk said:
I did notice an "oddity" on my device,

when it turns on it shows an "Android System" alert
"There's an internal problem with your device. contact your manufacturer for details."

I assume this is just a quirk of the ROM and would be fixed on an later date?

if not tell me what to give you cuz I got magisk working (alert showed before magisk was added)
Click to expand...
Click to collapse
i am getting this also. I can't get is to make calls or send SMS.
 
H

hamidrezarezai

Member
Jun 12, 2020
7
0
graewulf1 said:
i am getting this also. I can't get is to make calls or send SMS.
Click to expand...
Click to collapse
this one idk. i do get the same error "There's an internal problem with your device. Contact your manufacturer for details" anytime i turn on my phone as well but did not cause me any problem. my phone and sms just worked from the get-go. i know there is a way to manually set it up but I have not done so. maybe google it around and see how to do so. i remember people were saying they basically used the stock rom boot it up and then grab the provider data and stuff from the stock rom and then flash the custom rom and manually put it in the custom rom and that made it work. but i have not done such so idk how.
 
HemanthJabalpuri

HemanthJabalpuri

Senior Member
Feb 19, 2018
1,239
481
Andhra Pradesh, INDIA 🇮🇳
t.me
Realme C12
Electimon said:
If you've taken an OTA update on stock you will be fine
Click to expand...
Click to collapse
Is it sufficient to flash latest bootloader to _b to ensure we are on safe side?
Like `fastboot set-active other && fastboot flash bootloader bootloader.img && fastboot set-active other` ?
In case we brick because of empty _b, what's the state of mobile? Is it will be in EDL? Can we use blank-flash to unbrick?

Thanks
 
You must log in or register to reply here.

Similar threads

sd_shadow
  • Poll
General [Moto G Power 2021](borneo) Stock firmware
Replies
52
Views
23K
Human Person
Human Person
whoshotjr2006
Development [RECOVERY][UNOFFICIAL] TWRP 3.6.0-11 [BORNEO] Android 11 Based (updated 12/11/2021)
Replies
48
Views
16K
Triple25
Triple25
lifeoffamouskiing
Question Moto g power 2021 twrp
Replies
28
Views
13K
P
Phazmos
LilaWiya
Question Help Rooting moto G power 2021 on Android 10
Replies
21
Views
12K
C
cxskate
W
Question Motorola Moto G Power (2021) Cricket locked device (New) help me
Replies
14
Views
11K
D
Devariz

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 4
    E
    Electimon
    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

    June 19th 2023: Pushed June patch update
    Fix fingerprint gestures for egis
    Fix color mode listings
    Fix aux cameras
    Improve memory management
    Improve Wi-Fi 5GHz strength
    Numerous other changes
    View
    1
    DefinitelyDetermined
    DefinitelyDetermined
    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?
    View
    1
    S
    sdembiske
    DefinitelyDetermined said:
    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?
    Click to expand...
    Click to collapse
    @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
    View
    1
    E
    Electimon
    Renate said:
    @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.
    Click to expand...
    Click to collapse
    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.
    View
    1
    E
    Electimon
    Feb 27th 2023: Pushed Feb update
    View

New posts