Download and install the drivers for your device or at least Google's driver.
Download and unzip platform-tools (For ADB) somewhere you can find it like
C:\platform-tools\
Use CMD as an admin:
Microsoft Windows [Version 10.0.19045.2193]
(c) Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd\
C:\>cd platform-tools
C:\platform-tools>
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Android Debug Bridge (adb) | Android Studio | Android Developers
Find out about the Android Debug Bridge, a versatile command-line tool that lets you communicate with a device.
developer.android.com
Enable developer options on your device toggle ADB debugging enabled, OEM Unlock Enabled
type adb devices in the CMD window and grant access for ADB (CHECK THE BOX!) on your device.
Configure on-device developer options | Android Studio | Android Developers
Learn how to configure system behaviors that help you profile and debug your app performance.
developer.android.com
UNLOCK THE BOOTLOADER:
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot oem unlock
(T-Mobile has extra steps)
https://www.oneplus.com/support/answer/detail/op588
This phone is compatible with ARM64 VNDKLITE A/B GSI Images
Pick one and download it.
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Some Recommended ROMs:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
https://github.com/phhusson/treble_experimentations/releases/download/v416/system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
[UNOFFICIAL] crDroid R Mod //crDRom11
crDroid 7.16 Your warranty is now void! We're 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...
forum.xda-developers.com
https://sourceforge.net/projects/treblerom/files/crDRom11/2022.03.30/crdrom-v316-220330-arm64-bgZ-lite.img.xz/download
[GSI][Official][12.1][PHH] CorvusOS vS4.0 Leviathan
/* * Your warranty is... still valid? * * 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...
forum.xda-developers.com
https://sourceforge.net/projects/tipzbuilds/files/GSIs/CorvusROM/Official/20221015/Corvus_vS4.0-Leviathan-treble_arm64_ab_vndklite-Gapps-Official-0103.img.xz/download
Download and Extract the Stock Firmware for Your Phone
(In this example I'll be using 11.0.7.BE86AA for the BE2026 YOURS MAY BE DIFFERENT!!!)
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
https://oxygenos.oneplus.net/OnePlusN10Oxygen_14.O.37_OTA_0370_all_2207061538_b507495088804473.zip
Extract the payload.bin with payload-dumper-go.exe or payload_dumper.py
Releases · ssut/payload-dumper-go
an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.
github.com
GitHub - vm03/payload_dumper: Android OTA payload dumper
Android OTA payload dumper. Contribute to vm03/payload_dumper development by creating an account on GitHub.
github.com
This will give you the *.img files for flashing. If your device has a higher level fimware for example 11.0.8.BE86AA;
the only way to get the *.img files is to fastboot boot to a TWRP.IMG and dump the firmware with a pull command or use Oxygen Updater with advanced options.
Oxygen Updater
Oxygen Updater is an open-source app for OnePlus devices that allows you to install official OTA (over-the-air) updates ASAP. Ensure your device is up-to-date — it's quick, easy, and free!
oxygenupdater.com
Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img | by EduardoA3677 for OnePlus Nord N10 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot boot Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
C:\platform-tools>ROOT_TWRP_ADB_DUMP.BAT
Flashing a GSI requires a bone stock firmware, no root, no magisk, no mods! We are going to want to disable encryption and verification so the GSI doesn't freak out and can see the host files like on a virtual machine.
Put boot.img, dtbo.img, recovery.img, vbmeta.img and vbmeta_system.img in C:\platform-tools>
FLASH STOCK BOOT AND VBMETA (ROOT AND FLASH BLANK VBMETA LATER!!!):
If you extracted the firmware:
fastboot flash --disable-verity --disable-verification boot_a boot.img
fastboot flash --disable-verity --disable-verification dtbo_a dtbo.img
fastboot flash --disable-verity --disable-verification recovery_a recovery.img
fastboot flash --disable-verity --disable-verification vbmeta_a vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system_a vbmeta_system.img
fastboot flash --disable-verity --disable-verification boot_b boot.img
fastboot flash --disable-verity --disable-verification dtbo_b dtbo.img
fastboot flash --disable-verity --disable-verification recovery_b recovery.img
fastboot flash --disable-verity --disable-verification vbmeta_b vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system_b vbmeta_system.img
DO BOTH SLOTS!!!
If you dumped the firmware:
fastboot flash --disable-verity --disable-verification boot_a boot_a.img
fastboot flash --disable-verity --disable-verification dtbo_a dtbo_a.img
fastboot flash --disable-verity --disable-verification recovery_a recovery_a.img
fastboot flash --disable-verity --disable-verification vbmeta_a vbmeta_a.img
fastboot flash --disable-verity --disable-verification vbmeta_system_a vbmeta_system_a.img
fastboot flash --disable-verity --disable-verification boot_b boot_b.img
fastboot flash --disable-verity --disable-verification dtbo_b dtbo_b.img
fastboot flash --disable-verity --disable-verification recovery_b recovery_b.img
fastboot flash --disable-verity --disable-verification vbmeta_b vbmeta_b.img
fastboot flash --disable-verity --disable-verification vbmeta_system_b vbmeta_system_b.img
DO BOTH SLOTS!!!
For flashing the GSI we have to use FastbootD not Fastboot!!!
FASTBOOTD:
Execute the below command to boot your device to the FastbootD Mode (It will look like recovery mode.)
fastboot reboot fastboot
Time to Flash the ROM
FOR GSI IMAGES:
--AB devices--
fastboot devices (IS THE PHONE CONNECTED? MAKE SURE USB DEBUGGING IS ENABLED UNDER DEVELOPER OPTIONS?)
fastboot reboot fastboot (FASTBOOTD NOT FASTBOOT!)
fastboot getvar is-userspace (SHOULD BE YES!)
fastboot erase system_a
fastboot erase system_b
fastboot flash system_a "(GSI System Name of Firmware File)".img (Corvus_vS4.0-Leviathan-treble_arm64_ab_vndklite-Gapps-Official-0103.img)
fastboot flash system_b "(GSI System Name of Firmware File)".img
fastboot --set-active=b
fastboot -w
fastboot --set-active=a
fastboot -w
reboot to recovery (Use Menu)
Wipe Everything (The Bottom One)
Reboot From the menu to start the phone.
ONLY IF YOU GET THIS ERROR WHEN FLASHING!
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
Then Continue From:
fastboot flash system_a "(GSI System Name of Firmware File)".img (Corvus_vS4.0-Leviathan-treble_arm64_ab_vndklite-Gapps-Official-0103.img)
Generic system images | Android Open Source Project
source.android.com
After Android Setup Completes (JUST DO A QUICK AND DIRTY ONE JUST IN CASE!)
adb reboot bootloader
(FLASH BLANK VBMETA NOW!)
fastboot flash --disable-verity --disable-verification vbmeta_a vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system_a vbmeta_system.img
fastboot flash --disable-verity --disable-verification vbmeta_b vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system_b vbmeta_system.img
Start the phone
Install Magisk via ap apk
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Patch the bootloader from the installed GSI and then reboot to the bootloader once you have copied the patched images to your computer.
boot_patched_a.img
boot_patched_b.img
FLASH boot_a AND boot_b!
fastboot flash --disable-verity --disable-verification boot_a boot_patched_a.img
fastboot flash --disable-verity --disable-verification boot_b boot_patched_b.img
From the menu start the phone.
Build and install an overlay for functional adaptive brightness etc.
GitHub - phhusson/vendor_hardware_overlay: This includes hardware-specific overlays for Treble ROM
This includes hardware-specific overlays for Treble ROM - GitHub - phhusson/vendor_hardware_overlay: This includes hardware-specific overlays for Treble ROM
github.com
How to create an overlay?
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Change the value of an app's resources at runtime | Android Open Source Project
source.android.com
Empty vbmeta files and dump script batch file below.
Related
I unlocked bootloader,and able to root etc. But unable to flash vbmeta via fastboot .each time I got system destroyed. Any has detailed information about how to flash ? Any thread ?
I Used this command on fastboot mode
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Not working.
Problem solved by installing updated ADB installer 1.4.5
https://androiddatahost.com/up9hg
drmuruga said:
Problem solved by installing updated ADB installer 1.4.5
https://androiddatahost.com/up9hg
Click to expand...
Click to collapse
fastboot flash boot path to patched boot img
and then
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
this command?
That's it? just these two commands? I wonder if the second one is even necessary. someone help. I am currently stuck at MIUI logo!
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I have a problem with it on newer ADB editions as it is not working...any ideas?
vassiliszacharis said:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I have a problem with it on newer ADB editions as it is not working...any ideas?
Click to expand...
Click to collapse
try this
I'm curious if anyone has loaded a gsi on the oneplus 7t and if they know what boots and any workarounds that might be needed.:fingers-crossed:
on fastbootd
fastboot -w
fastboot flash system_a GSI.img
fastboot flash system_b GSI.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img " use the vbmeta.img from oxygen "
All those should be flashed in one go without rebooting. boot and vbmeta are those taken from OOS stock rom.
i have looked and i can not find the t-mobile stock rom i can get these files from. i have the files used by the msm tools but can find one that can be used. could you explain or link me please
On firmware C.47 after changing any settings the system stops booting. Flashing a modified vbmeta which helped to solve the problem on C.44 firmware doesn't work anymore and also leads to problems with booting the system. Perhaps someone knows how to get Konabess to work on the latest C.47 firmware?
For me it works like before. Please try following commands and use extracted images from c.47:
fastboot flash boot root.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verification --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verification --disable-verity flash vbmeta_vendor vbmeta_vendor.img
corneo said:
For me it works like before. Please try following commands and use extracted images from c.47:
fastboot flash boot root.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verification --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verification --disable-verity flash vbmeta_vendor vbmeta_vendor.img
Click to expand...
Click to collapse
please share the files if you have them.
You can extract it by yourself with using payload dumper go. Please try forum search.
GitHub - ssut/payload-dumper-go: an android OTA payload dumper written in Go
an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.
github.com
corneo said:
For me it works like before. Please try following commands and use extracted images from c.47:
Click to expand...
Click to collapse
corneo said:
You can extract it by yourself with using payload dumper go. Please try forum search.
GitHub - ssut/payload-dumper-go: an android OTA payload dumper written in Go
an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Thank you! It worked!
Mi Bodya said:
Thank you! It worked!
Click to expand...
Click to collapse
Can you share your konabess configs?
rejectedjs said:
Can you share your konabess config
Click to expand...
Click to collapse
what about in oos 13 f72? tried several combinations with vbmeta and vendor partitions, no luck. always ends up dmverity crashdump or constant reboot cycle to fastboot.
gsser said:
what about in oos 13 f72? tried several combinations with vbmeta and vendor partitions, no luck. always ends up dmverity crashdump or constant reboot cycle to fastboot.
Click to expand...
Click to collapse
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verification --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verification --disable-verity flash vbmeta_vendor vbmeta_vendor.img
...
It works in me
Mi Bodya said:
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verification --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verification --disable-verity flash vbmeta_vendor vbmeta_vendor.img
...
It works in me
Click to expand...
Click to collapse
For some reason it didnt for me. I tried flashing in each slot one by one and it works
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_a vbmeta_vendor.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_b vbmeta_vendor.img
Here is my config, i made it for my previous mi 11 ultra but it works just as fine for my 9 pro.
D
Mi Bodya said:
On firmware C.47 after changing any settings the system stops booting. Flashing a modified vbmeta which helped to solve the problem on C.44 firmware doesn't work anymore and also leads to problems with booting the system. Perhaps someone knows how to get Konabess to work on the latest C.47 firmware
Click to expand...
Click to collapse
Disable vbmeta
I haven't tried this, running OOS 13. Does this wipe any data? Or it keeps all data in place?
Is there a guide about this (for first timers)? Or have I got to just follow the post #2
Thanks
observingi said:
Is there a guide about this (for first timers)? Or have I got to just follow the post #2
Thanks
Click to expand...
Click to collapse
there is a telegram group with guides and support. Search adreno_konabess in telegram
Hi, how can i use this files ? i dont know anything about konabess, can you help me? i have rooted LE2123 F72 version
sefai77 said:
Hi, how can i use this files ? i dont know anything about konabess, can you help me? i have rooted LE2123 F72 version
Click to expand...
Click to collapse
Join the telegram group mentioned above or visited the Konabess GitHub. The info is there. There are also YouTube videos. Lots of info about it if you simply search for it.
Peeps kept asking me in Telegram and in xda so here is what you do to update OOS without crash dump.
From your CURRENT ROM payload.bin, extract dtbo, vendor_boot, vbmeta, vbmeta_system, vbmeta_vendor. Then use the commands i put below. After that just local flash the ota and use magisk to patch inactive slot.
Spoiler: Reverting Kona Changes and Restoring Verity.
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash boot magisk.img - the magisk patched boot.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vbmeta_system_a vbmeta_system.img
fastboot flash vbmeta_system_b vbmeta_system.img
fastboot flash vbmeta_vendor_a vbmeta_vendor.img
fastboot flash vbmeta_vendor_b vbmeta_vendor.img
------------------------------------------------------------------
To re-use Konabess after the update, extract the images above from the OTA payload.bin and just use the commands down below.
Spoiler: Using Kona
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_a vbmeta_vendor.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_b vbmeta_vendor.img
This works for me in OOS 13 ROMs.
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon) - Looked into it. This is being flaky once enabled. Will need more time to fix this.
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
thanks for the amazing work on this rom
sultanahamer said:
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon)
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
Click to expand...
Click to collapse
Thank you, guys, for your awesome work. Hope we'll get a stable update. Good luck
sultanahamer said:
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon)
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
Click to expand...
Click to collapse
So installed fine on a G10 now the problem is a lack of google apps I want it and I need magisk for half the apps to to add a custom way to run apps that need root.
I cannot get gapps on it for starters as can't go into a recovery menu it's twrp I need to do all this with and the recovery on this is stock really, I will say though that is is an amazing firmware I mean really clean brilliant work but I must have twrp so I can root but also so I can add google apps which is my primary necessity root is a distant second if at all needed i do newed my apps to make images and other tools I use it for daily driver wise.
l Tried to use this TWRP https://cloudhazy.com/download/motorola-moto-g10-xt2127-2-twrp-recovery-3-5-2/ and it fails but I know the model number XT2127-2 is correct so it just doesn't allow installing or launching it, from inside platform tools openeing in a command window here mode????
I am stuck completely now.
@PHYSC-1 you should be able to find magisk inside the attached lineageos zip. Flash that to boot and you should be rooted. I am working on gapps and dual sim currently. Also, don't feel like you are stuck. At any moment, you can flash the stock firmware and go back to stock if you are not able to daily drive lineage os without gapps.
I don't want to have gapps on my phone so I didn't work on it at all until now. I see that many people are asking for gapps, so giving it a try.
In case you don't find the magisk boot image in the lineage os zip, you can create one yourself by installing magisk app and passing this lineageos boot image to it.
@PHYSC-1 we are testing gapps on this ROM now. Me and two users present on our group are testing GAPPS on this ROM. As of now, its running smooth, will publish the update in a week or so.
sultanahamer said:
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon) - Looked into it. This is being flaky once enabled. Will need more time to fix this.
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
Click to expand...
Click to collapse
Thank you for this work! I'm also anxious to get a stable, dual chip working version too.
I think the Gapps should be separate to ROM. Of course if it is possible.
Gapps works 2 problems found in testing 1 is a big one for anyone using screen cast the network auto switches from 2.4ghz to 5ghz and back intermittently causing screen cast to drop out mid use and this stuns it and creates constant bad image quality and freezing completely up.
Secondly this could be unrelated to the OS but it doesn't happen on official Motorola OS's when using the app from F-Droid called simple gallery pro if you edit an image and try to draw on an image the drawing occurs in the wrong position the pointer is below where you draw on?
Hello, i am trying to install android 13 gsi on GM8. I installed system.img but when i try to install vbmeta.img it says
fastboot flash vbmeta vbmeta.img
Sending 'vbmeta' (4 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
I don't know what to do, I would be glad if you help me.
try to flash in slot directly. use proper flags.
Code:
fastboot flash --disable-verity --disable-verification vbmeta_a vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_b vbmeta.img
aIecxs said:
try to flash in slot directly. use proper flags.
Code:
fastboot flash --disable-verity --disable-verification vbmeta_a vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_b vbmeta.img
Click to expand...
Click to collapse
thank you but it doesn't work for me
afowd007 said:
thank you but it doesn't work for me
Click to expand...
Click to collapse
Were you able to figure out?
You may not be on fastbootD. If you are, then it should work. And for some reason it was deleted. You can re-add it with command:
Code:
fastboot create-logical-partition vbmeta 800000
if you are on fastboot 1, then use command:
Code:
fastboot reboot recovery
then you should be able to select fastboot from menu and fastbootd should show up