Database Info

Moto G CM 12 - Can´t get it on my phone - device not listed in adb

Good morning guys
I have a very huge problem. I tried to install CM on my Moto G (2013) with this walkthrough:
Every worked fine, till the last point. My device is not listed in adb. if I type in "adb devices" it is not listed, therefore I am not able to put CM on my internal storage
I have learnt, that I used to enable USB debug first, but I didn´t. My device is listed in the "Gerätemanager" (sorry, I forgot the english expression) Now I am stucked, either in "warning bootloader unlocked" screen or on the "Team win recovery Project mode" screen (which works fine) or on in the fastboot Flash mode
I have basically two question:
- Is it possible to enable USB debug by any other method?
- Is it possible to get CM on my phone by any other method?
What I did:
Installed Google USB Driver
Installed Moto G Software Suite
What I am using:
Windows 10
I would appreciate some help as my phone is stuck now with no OS
Best regards!

Juventino7 said:
Good morning guys
I have a very huge problem. I tried to install CM on my Moto G (2013) with this walkthrough:
Every worked fine, till the last point. My device is not listed in adb. if I type in "adb devices" it is not listed, therefore I am not able to put CM on my internal storage
I have learnt, that I used to enable USB debug first, but I didn´t. My device is listed in the "Gerätemanager" (sorry, I forgot the english expression) Now I am stucked, either in "warning bootloader unlocked" screen or on the "Team win recovery Project mode" screen (which works fine) or on in the fastboot Flash mode
I have basically two question:
- Is it possible to enable USB debug by any other method?
- Is it possible to get CM on my phone by any other method?
What I did:
Installed Google USB Driver
Installed Moto G Software Suite
What I am using:
Windows 10
I would appreciate some help as my phone is stuck now with no OS
Best regards!
Click to expand...
Click to collapse
Do you have Custom Recovery, like TWRP or ClockworkMod installed? If so, you should be able to copy the .zip of the CM build onto a MicroSD card (maybe with the help of a friend's phone if you don't have a backup phone yourself) and install it via the recovery.

Yes! I am using TWRP. The main issue I am facing is, that I can´t put the files on the internal storage. The Moto G hasn´t a Micro SD Card either.
My device is not listed in adb! If I put "adb devices" in the console there is a blank space where the model of my phone should be

Oh snap, forgot about the missing slot since my 4G has one. In that, sorry for my Bad advice. But: Google "ADB sideload twrp", maybe the web can help?

Schmuppes said:
Oh snap, forgot about the missing slot since my 4G has one. In that, sorry for my Bad advice. But: Google "ADB sideload twrp", maybe the web can help?
Click to expand...
Click to collapse
Don´t worry. I appreciate every advice. Sideload won´t work either, as I always get the error message: "device not found"

You may need to install drivers. Does Windows not see a USB device at all? TWRP supports MTP which should work out of the box on Windows 10 (at least it did when I tested it with a different device on the Win10 preview).
Other alternatives:
* Copy your ROM to the device while running Android
* Use USB OTG storage

One thing that popped into my mind: Have you installed the Android SDK before trying anything? I did that on my Win10 machine and had no problems whatsoever talking to the phone via adb / fastboot.
/edit: Just realized that you probably have adb installed if you say that it doesn't recognize your device there. Try running the command line in admin mode and temporarily disabling anti virus software?

_that said:
You may need to install drivers. Does Windows not see a USB device at all? TWRP supports MTP which should work out of the box on Windows 10 (at least it did when I tested it with a different device on the Win10 preview).
Other alternatives:
* Copy your ROM to the device while running Android
* Use USB OTG storage
Click to expand...
Click to collapse
No, with Windows is everything fine. My PC regocnizes the device.
I can´t run Android, as I already wiped everything!
What is USB OTG storage?
Schmuppes said:
One thing that popped into my mind: Have you installed the Android SDK before trying anything? I did that on my Win10 machine and had no problems whatsoever talking to the phone via adb / fastboot.
/edit: Just realized that you probably have adb installed if you say that it doesn't recognize your device there. Try running the command line in admin mode and temporarily disabling anti virus software?
Click to expand...
Click to collapse
yes
In adb my device is not listed.
If I put "adb devices" in the console there is a blank space where the model of my phone should be

You can flash a zip straight from USB otg (on the go). They sell either USB otg kits to use a regular USB or they also have USBs that act like your standard USB with a mini USB connector on one side and regular USB connector on the other. I use mine all the time.
Just insert in your phones mini USB slot on the bottom. After you have transferred your zip file to it of course, and flash from it in twrp.

n0ts0smart said:
You can flash a zip straight from USB otg (on the go). They sell either USB otg kits to use a regular USB or they also have USBs that act like your standard USB with a mini USB connector on one side and regular USB connector on the other. I use mine all the time.
Just insert in your phones mini USB slot on the bottom. After you have transferred your zip file to it of course, and flash from it in twrp.
Click to expand...
Click to collapse
So that's basically like a USB Memory Stick for the smartphone? Gotta get meself one of those then, eh?

Hi.
If you are in fastboot mode then you should type "fastboot devices" instead of "adb devices"
Adb and fastboot mode are different that's why the console doesn't recognize your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Another option is boot into TWRP and connect the phone to PC and finally copy the ROM. Its easier and faster than sideload.
The moto g doesn't have a microsd card slot but it doesnt matter because TWRP makes the PC recognize the phone in MTP mode.
Hope this helps

Trying to install /e/OS on FP3, but it hangs on fastboot on Windows 10

Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can someone point me into the right direction?

Nijs said:
Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
Can someone point me into the right direction?
Click to expand...
Click to collapse
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I do not see the interface you mention, however, I see 'Android' under 'other devices' and 'FP3' under 'portable devices' and 'Google Nexus ADB Interface' under SAMSUNG Android Phone (I did not install this, I assume Windows did this in the background).
Which option should I select to install the driver manually? Or none of them?

Flashing for beginners!

Hi Guys,
I hope I'm in the right place here !? if not, I apologize, I'm new here
so, after finally unlocking the bootloader, I plan to change my Poco x3 (MIUI Global 12.0.7) to RR 10. In the past I have already changed Rome to LineageOS 10 on my old Leeco Le Pro 3. Now, after browsing the forum, I am very confused! how many things there are to consider! (I bricked my Leeco through a wrong TWRP installation, so I'm very careful). Decrypt (?), Clean / dirty Flash etc. were never an issue back then. Does anyone of you have a simple step-by-step description suitable for beginners of what should / must be observed (preferably in German)! Many thanks in advance!
H0rdak

Start here: https://telegra.ph/How-to-install-Poco-x3-ROM-10-14

Hi Pnin, thanks for the quick help! One question: what do you recommend for the first flash: clean or dirty?! Thx H0rdak

First must always be clean; dirty is only for updates (and sometimes, not even then).

pnin said:
Start here: https://telegra.ph/How-to-install-Poco-x3-ROM-10-14
Click to expand...
Click to collapse
Outdated. There is no need to boot to system after flashing ROM. Reboot to Recovery -> Flash Magisk & Gapps THEN reboot to system.

What about on Pixel 5. I want to flash ProtonAOSP And it says just flash as if you would the stock image, bc there is no TWRP for GP5. So does that mean I just use the flash-all command or fastboot boot ProtonAOSP.zip file? I'm confused as a motherF

hello people, thank you very much for the quick help! here you really get help! after pnin's execution, a few more questions have arisen:
1. is it really necessary to install gapps?
2. why orangefox and not TWRP? In the RR thread, twrp is recommended ?!
3. Which recovery is the most suitable (3.4.0-15 or 3.5.0-0 ???) - what are your experiences?
4. Is a special decrypt program necessary (in some youtube tutorials such a program is used)

1. Optional
2. Your call: OF appears to be a more polished product for the PX3 (some people reported isues with TWRP)
3. ...
4. ?

Thank you guys, and special thanks to Pnin! I have now decided to use OF as a recovery! Unfortunately the whole thing is a bit more difficult than I thought it would be. The problem: my pc doesn't recognize the phone! When I enter the adb command "adb devices", the x3 is not displayed ?! Any ideas?! Thanks in advance!!

drivers, drivers, drivers, check your device manager in windows, if there is an unrecognized device while your phone is connected to pc/notebook, that's the problem you need to solve

thanks jeryll, I feel a little stupid right now because I can't do it! there are dozens of sites offering drivers for the poco (i don't want to post any here). do you or someone have a link ?! it is a simple exe file right? !! sorry i'm a bit ashamed but i really have problems with that!

H0rdak said:
thanks jeryll, I feel a little stupid right now because I can't do it! there are dozens of sites offering drivers for the poco (i don't want to post any here). do you or someone have a link ?! it is a simple exe file right? !! sorry i'm a bit ashamed but i really have problems with that!
Click to expand...
Click to collapse
check this

thank you for your tireless help! but it still doesn't work! But when I enter the adb command this time this message comes up:
C:\adb> adb devices
* deamon not running. starting it now on port 5037 *
???

H0rdak said:
thank you for your tireless help! but it still doesn't work! But when I enter the adb command this time this message comes up:
C:\adb> adb devices
* deamon not running. starting it now on port 5037 *
???
Click to expand...
Click to collapse
this simply tells you that adb deamon is starting, because it was not running before...
check your device manager after you connect your phone to pc/notebook and look for this (picture is just an example)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you see yellow triangle somewhere after you connect your phone and it was not there before, that means you don't have installed correct drivers
I need to know if you have installed recovery already, if not, you can not install it via adb, only via fastboot mode and your phone must be switched to fastboot mode (restart your phone and before it show initial screen hold volume down button until you see picture bellow)
with this on your phone screen connect your phone to your PC/notebook and check your device manager and look for devices with yellow triangle, if you see one you need to install correct driver for your device (for example try to start mipcsuite it *should* react and try to install correct drivers)
if you don't have yellow triangle in device manager try to type in cmd window
Code:
fastboot devices
if your phone is recognized you will see something like this
then you can continue with flashing orange fox recovery (download flashable zip with ofox recovery and extract recovery.img preferable to directory with fastboot app installed)
in cmd window type
Code:
fastboot flash recovery recovery.img
fastboot boot recovery recovery.img
if everything goes well after reboot you should be in orangefox recovery

WOW! this detailed description really helps me !!!! First of all: No, I haven't installed any recovery yet, I thought that could only be done via adb! Unfortunately, as you have described well, I see an orange triangle.
I have installed this mi-suite program but I cannot access the phone there either - it tells me that I have not installed any drivers, but does not give me the opportunity to do so ;-(
thx for your help greetings
H0rdak

people, i need help quickly! I don't know how, but I have now entered the "Poco-Recovery 3.0 mode" and have the option to select under Reboot / Wipe Data / Connect with Mi Assistance what should I do???

people, i need help quickly! I don't know how, but I have now entered the "Poco-Recovery 3.0 mode" and have the option to select under Reboot / Wipe Data / Connect with Mi Assistance what should I do???

H0rdak said:
people, i need help quickly! I don't know how, but I have now entered the "Poco-Recovery 3.0 mode" and have the option to select under Reboot / Wipe Data / Connect with Mi Assistance what should I do???
Click to expand...
Click to collapse
calm down, and choose Reboot (don't select Wipe data it will factory reset your device and you will loose eveything on your internal storage)

Pfewww .... everything is okay now Phone boots normally! Thx jeryll! no idea how that could happen. had a little flashback like with my Leeco; - /!
Okay, I think it depends on the drivers. All the pages I've looked at, however, only offer me strange drivers (like "POCO x3 Quallcomm driver" or things like that). Xiaomi's homepage doesn't offer any drivers at all - at least I can't find any there!
Jeryll, can you tell me what these drivers are called and where you can get them from? Many, many thanks in advance H0rdak

try this (untested, but looks legit)

OnePlus 8 T-Mobile Conversion Problem

Hi all,
I am trying to convert my T-Mobile IN2017 OnePlus 8 to have a global rom. I am currently on 10.5.7.IN55CB and I am following this tutorial here. My bootloader is unlocked (by using the official binaries I got emailed from OnePlus). My PC has driver signature verification off and is in test mode. It seems that my installer is stuck at this point:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
because the driver is not installed for recovery I think:
I have tried installing/reinstalling the OnePlus drivers to no avail. The installer runs perfectly fine while in fastboot mode, but does not work once rebooted into recovery. If someone can send me the driver or show what I am doing wrong, it would be much appreciated!

Costik said:
Hi all,
I am trying to convert my T-Mobile IN2017 OnePlus 8 to have a global rom. I am currently on 10.5.7.IN55CB and I am following this tutorial here. My bootloader is unlocked (by using the official binaries I got emailed from OnePlus). My PC has driver signature verification off and is in test mode. It seems that my installer is stuck at this point:
View attachment 5499393
because the driver is not installed for recovery I think:
View attachment 5499395
I have tried installing/reinstalling the OnePlus drivers to no avail. The installer runs perfectly fine while in fastboot mode, but does not work once rebooted into recovery. If someone can send me the driver or show what I am doing wrong, it would be much appreciated!
Click to expand...
Click to collapse
See my post here:
https://forum.xda-developers.com/t/...with-bootloader-re-lock.4345305/post-86144965
You're having the same issue I had. You need to install the fastboot drivers while it's connected in that state from your screenshot. Grab the drivers from Foxy Drew's post (linked in mine above), run the installer until it hangs, then update the drivers on the PC. When I did this the flash-all installer immediately kicked back into gear and finished the process.
The problem, I, think, is that you need to install adb drivers and fastboot drivers while the phone is in 3 different boot modes: normal, fastboot/recovery, and bootloader. So you need to get the phone to be recognized in all of those states so you can apply the drivers to the device the PC "sees" when it's connected in each of those states. Every boot mode basically presents itself as a different device to the PC, and that 3rd fastboot mode is hidden until you get to the spot you show in your screenshot.
Hope that works for you.

SilverZero said:
See my post here:
https://forum.xda-developers.com/t/...with-bootloader-re-lock.4345305/post-86144965
You're having the same issue I had. You need to install the fastboot drivers while it's connected in that state from your screenshot. Grab the drivers from Foxy Drew's post (linked in mine above), run the installer until it hangs, then update the drivers on the PC. When I did this the flash-all installer immediately kicked back into gear and finished the process.
The problem, I, think, is that you need to install adb drivers and fastboot drivers while the phone is in 3 different boot modes: normal, fastboot/recovery, and bootloader. So you need to get the phone to be recognized in all of those states so you can apply the drivers to the device the PC "sees" when it's connected in each of those states. Every boot mode basically presents itself as a different device to the PC, and that 3rd fastboot mode is hidden until you get to the spot you show in your screenshot.
Hope that works for you.
Click to expand...
Click to collapse
Thank you so much for your help! I was actually able to get it to work by doing something really similar. I'll post what I did just in case someone runs into this exact issue:
1) I made sure that I had all the drivers installed
2) I did the entire process over again until I got to that part where my device was no longer recognized
3) I went into device manager > IN2017 > update driver > drivers installed on this pc > chose from a list > Android phone > Android bootloader interface
I did this all while the converter was running and my phone was plugged into my pc. Once I did this, the program continued and I was able to finish the install.

Costik said:
Thank you so much for your help! I was actually able to get it to work by doing something really similar. I'll post what I did just in case someone runs into this exact issue:
1) I made sure that I had all the drivers installed
2) I did the entire process over again until I got to that part where my device was no longer recognized
3) I went into device manager > IN2017 > update driver > drivers installed on this pc > chose from a list > Android phone > Android bootloader interface
I did this all while the converter was running and my phone was plugged into my pc. Once I did this, the program continued and I was able to finish the install.
Click to expand...
Click to collapse
Yep, I think that's exactly what I did. I can't remember which fastboot drivers I updated to bit I'll bet they're both the same, and that's the point in the process where I updated drivers as well.
Cheers!

Oppo A73: adb works but fastboot won't recognize the device on either Linux or Windows

I'm badly in need of help with my broken Android device. The XDA community is where I always found most information on those matters so I'm hoping someone can help me out. Some background on everything that went on today: I recently bought an Oppo A73 (non-5G version), I live in Romania so the best I can offer are these links for the store I got it from:
Source 1
Source 2
My grievance with the device is how it comes with an Android distribution called ColorOS which is filled with bloatware and things being shoved in my face. I was discussing this today and someone brought up adb explaining how I could use the command to remove unwanted system packages. I used it to get rid of some things I wanted nothing to do with, such as Rakuten and Heytap. For some mind boggling reason it appears those garbage packages were connected even to the core system: The device became unable to start up and entered a boot loop. This forced me to do a factory reset from recovery mode, causing me to lose all contacts and SMS messages as I didn't think to back them up first. After that ordeal I want my phone to use the default Android distribution: I'd rather have just Google involved with my phone over all those insane extra services, I'm not going back to this broken bloated OS.
Someone explained to me the basics of ADB and DSU Loader. After enabling Developer Mode I was able to enable the "OEM Unlock" feature then use the DSU Loader option to download a DSU package. My two options are "GSI ARM64" and "GSI+GMS ARM64" I used the later as advised. After the download completed I was prompted to restart my device in order to boot into the new image which I did from the notification. The phone however would only boot into ColorOS each time. I was told this must be because I need to use the commands fastboot oem unlock and fastboot reboot after adb reboot bootloader. The problem is that while adb recognizes my device, fastboot does not due to driver issues.
I spent hours trying to find some format in which fastboot would detect the device but everything seems to be broken, that's presently what I need your help with. I only use Linux these days, Manjaro KDE more precisely: I have a Windows 7 image and in an attempt to find a solution I downloaded Windows 10 as well: I installed Win 10 in VirtualBox and proceeded to install every update and driver I could find, following articles explaining how to get the driver for Oppo A73. None of them would work however: Even with all those drivers installed, the device manager sees an invalid USB device and neither adb or fastbook see it from the VM... same story with Win 7.
Download Oppo Latest MTK QCOM usb Driver 3.1.9 - ROM-Provider
Download Latest oppo usb driver for Window, here we Share Official oppo usb driver for mediatek and qcom based oppo phone
romprovider.com
Oppo A73 USB Driver Download | Device Drivers
Oppo A73 USB Drivers will help your Windows computer recognize your Android device. Then you can transfer files from computer to Android or even install the stock or custom ROM to your Android device.
oemdrivers.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can someone please tell me what OS and driver I need to get fastboot to recognize the device? If there's no way to, is there an alternative to fastboot to remove whatever's preventing the DSU image from booting and allowing me to flash it? Like I said I have access to adb on my main machine just not fastboot, anything adb can do should work.
I can't change my OS only for this task however. If I need Windows, is it not possible to do it from VirtualBox using the configuration in the screenshot above? If VBox is the issue, I will in an extreme scenario consider using a separate hard drive on my mother's computer to temporarily install Windows just to do this. I strongly hope that won't be necessary however, and this can be solved with a live tool or Linux distribution that has the necessary drivers.

Dynamic System Updates (DSU) | Platform | Android Developers
Dynamic System Updates (DSU) lets developers install a GSI side by side with the device's system image on a DSU-supported device that runs Android 10 or higher.
developer.android.com
Generic System Image releases | Platform | Android Developers
developer.android.com
I've attempted the tutorial described here, including the manual technique using adb commands the downloaded image and of course setting the feature flag as indicated. Even with adb shell am start-activity the custom image refuses to load: The notification says "dynamic system is ready, to start using it restart your device"... I click on "restart" inside this notification, the phone reboots, I see the oppo logo for a little then it goes black then I see it again, but after that I'm back in the original OS. What's breaking it and not letting the DSU load?!

AFAIK the Oppo A73 doesn't support Fastboot.

xXx yYy said:
AFAIK the Oppo A73 doesn't support Fastboot.
Click to expand...
Click to collapse
Is it possible for a device to not have it entirely? What are my options in that case? Can't ADB or another tool or app unlock the bootloader? Is there no safe way to simply get it to use stock Android with just the Google stuff on it by default? Was hoping I could get it to Android 12 too that way.

You flash device's Stock ROM by means of ADB Sideload method.

xXx yYy said:
You flash device's Stock ROM by means of ADB Sideload method.
Click to expand...
Click to collapse
Thanks, I'm looking into that method. The device's recovery mode doesn't have anything with the word "sideload" in it, but does offer the option to install from local storage. Would that do for a full ROM or am I in trouble again?
And where do I get the stock Android ROM from Google? I can only find custom ones, don't want to risk playing with that: I'd like the official Android 12, ideally the same image that would be downloaded by the builtin DSU loader as that seemed to know exactly what it needed.
Generic System Image releases | Platform | Android Developers
developer.android.com
Is this correct or should I look somewhere else?

Google dosn't offer a device's Stock ROM: Google only offers the vanilla Android OS ( AKA AOSP ) what is base for the Stock ROMs OEMs implement on their devices.

xXx yYy said:
Google dosn't offer a device's Stock ROM: Google only offers the vanilla Android OS ( AKA AOSP ) what is base for the Stock ROMs OEMs implement on their devices.
Click to expand...
Click to collapse
I see. So if I install the GSI, can I install Google Play separately to get the apps I need back? Should be all the Google stuff I need. I assume the GSI contains all the other components like call, SMS, camera, loader (homescreen), etc? Is there a risk of missing any base functionality?
I used Treble yesterday and it indicated a valid image I can use. Where do I actually download it from? Then what exactly am I meant to do with it, how do I sideload or install it from recovery and so on?
Sorry for all the questions: First time I'm actually having to flash a phone, very nervous about bricking.