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

Totally n00b question - from not-a-n00b

I just received the Pixel 2. Connected it to a Windows 10 box. Windows installed Microsoft drivers. I can't install Google drivers because Winblows says that the best drivers for my device are already installed. So I open an Explorer window, and there's the Pixel 2. I open that and it's a totally blank window. No, it's not the phone - ES shows directories in internal storage. (To make sure, I took a picture. It's in /DCIM/Camera.)
Enable debugging. Enable unlock. adb devices. No devices.
Okay, manually reboot to the bootloader. (The last line is Device State: locked) Fastboot sees the device.
fastboot boot twrp.img (I renamed it to make it easier). "FAILED (remote: Operation is not allowed in Lock State)"
I've owned Samsungs for so long I forgot that there were other manufacturers. What am I doing wrong? (I know it's got to be me, not the phone.)
How do I force Windows to replace the drivers (or do I really have to boot into Linux?) And how do I get the thing unlocked? Yes, I googled it. I searched here. I'm still stumped.

Maybe try this all in one tool
https://forum.xda-developers.com/pixel-2/development/tool-tool-one-driversunlocktwrpfactory-t3730228

Then check this out:
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417

flashing unlock did it. Thanks. Now to see if I can install everything (TWRP, Magisk, etc.) then a day of reinstalling all my apps and data.

Okay, TWRP and Magisk installed - thank you. Now only one thing is driving me crazy - plugging the Pixel into the PC doesn't show the Pixel. I hear the USB recognizing the phone, Device Manager sees the phone, but I can't find it as a drive, so I can copy data to it.
Oh, and when it's time to update to the next monthly, do I have to back my data up, flash stock, restore my data and reinstall Magisk? Or how does it work every month with a Pixel? (One update says it failed - I'm on the January update.)

Rukbat said:
Okay, TWRP and Magisk installed - thank you. Now only one thing is driving me crazy - plugging the Pixel into the PC doesn't show the Pixel. I hear the USB recognizing the phone, Device Manager sees the phone, but I can't find it as a drive, so I can copy data to it.
Oh, and when it's time to update to the next monthly, do I have to back my data up, flash stock, restore my data and reinstall Magisk? Or how does it work every month with a Pixel? (One update says it failed - I'm on the January update.)
Click to expand...
Click to collapse
To get your device to show up you have to pull the notification shade down and then change the device mode to mtp storage mode. As for updating to new security patchs I usually just use the factory image from Google and the flash-all script with the -w option removed in order to keep my data. Then flash my kernal and magisk.

I already had it set - I guess unlocking the bootloader resets it.

Rukbat said:
I already had it set - I guess unlocking the bootloader resets it.
Click to expand...
Click to collapse
It resets Everytime you disconnect the device or reboot for some dumb reason. It gets annoying.

Maybe in an update far away ...

Hi, I may be wrong and silly. I want you to check this option when you connected your mobile to PC.
As in attached screen shot when you connect your mobile to pc there will be a notification "Android system" (Not USB debugging connected one) click it and will provide you options screen "Use USB to.." from there select "Transfer files" option instead of "charge this device"
{
"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"
}
Thank You

_satish_ said:
Hi, I may be wrong and silly. I want you to check this option when you connected your mobile to PC.
As in attached screen shot when you connect your mobile to pc there will be a notification "Android system" (Not USB debugging connected one) click it and will provide you options screen "Use USB to.." from there select "Transfer files" option instead of "charge this device"
Thank You
Click to expand...
Click to collapse
Attaching Screen shot

adb android not support on security

Hello, when im trying to change charge mode with command "fastboot oem off-mode-charge" i got message
Minimal ADB and Fastboot>fastboot oem off-mode-charge disable
...
FAILED (remote: not support on security)
finished. total time: 0.013s
Phone is unlocked (checked in fastboot getvar all unlocked: yes)
Phone is Alcatel 1x 2019 with android 6.0
Anyone can help me with it?

I also have the same problem with Hotwav (wheatek) H1 device. Unlocked the bootloader, but when trying to disable off-mode-charge I get the same error. Maybe there is some security setting that needs to be disabled first?

You both are speaking of FASTBOOT, and not of ADB as cited in this theads header.

Yes, but this is changed in fastboot, no? It should work, bu doesn't

I get the same error. And when I enter "adb devices" I get "1023456789ABCDEF unautorized". "fastboot devices" does not show anything

To fix this "unauthorized" error you
1. Revoke USB Debugging on phone
If the device is shown as unauthorized, go to the developer options on the phone and click "Revoke USB debugging authorization" .
2. Restart ADB Server:
Then restarted adb server
Code:
adb kill-server
adb start-server
3. Reconnect the device
The device will ask if you are agree to connect the computer id. You need to confirm it.
It is now authorized!

Doesn't change the original problem. The device appears as "0123456789ABCDEF", and setting "boot on charge" fails with cryptic error message "remote: not support on security". Typical chinese error message.
I am stuck. Can anyone help me? I bought this phone (Soyes XS12) to use it as a GPS car tracker, but what use is it if it doesn't automatically boot when charged.
{
"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"
}

time2fly said:
Doesn't change the original problem. The device appears as "0123456789ABCDEF", and setting "boot on charge" fails with cryptic error message "remote: not support on security". Typical chinese error message.
I am stuck. Can anyone help me? I bought this phone (Soyes XS12) to use it as a GPS car tracker, but what use is it if it doesn't automatically boot when charged.
View attachment 5899259
Click to expand...
Click to collapse
First of all: The command fastboot is for fastboot. The command adb is for adb. When booting into fastboot then adb doesn't work.
To use it in your car as GPS tracker. With an additionally mobile connection? Or only pure GPS? Where is the phone? Somewhere outside the car on the top or well hidden inside the glove box?
Let's assume your phone is able to get a GPS signal. How to track it?

Forget all the GPS info. I just want the phone to boot when I connect it to the charger. I know of the difference between adb and fastboot. I was just experimenting which tool could detect my device. While adb can, fastboot can't, because "0123456789ABCDEF" is obviouslly not a valid device id.

Looking at it, this seems intentional from manufacturer's side. They can enable it and you updated firmware if you pay a large sum of money. I've tried all the tricks and hacks mentioned in this forum – nothing helped. I don't know why these Chinese phones are so "secured". Trying to force businesses to pay when they discover that something rarely used by ordinary people but essential for some business project is disabled in the stock firmware?

Well, I don't consider "boot on charge" as rarely needed. Everyone who goes to bed at night and uses his phone as an alarmclock needs this. It's not understandable that this is not an option in the settings. And we're talking about Android 9 here!

0123456789ABCDEF instead of serialno indicates that is either a fake/clone device or someone has tinkered with that device already. most likely usual fastboot commands won't work. if you have possibility to root that device you can modify the para partition and set off-mode-charge manually.

time2fly said:
Forget all the GPS info. I just want the phone to boot when I connect it to the charger. I know of the difference between adb and fastboot. I was just experimenting which tool could detect my device. While adb can, fastboot can't, because "0123456789ABCDEF" is obviouslly not a valid device id.
Click to expand...
Click to collapse
Try fastboot oem help to see the available options/features. Maybe there is another corresponding option that needs to be enabled.

alecxs said:
0123456789ABCDEF instead of serialno indicates that is either a fake/clone device or someone has tinkered with that device already. most likely usual fastboot commands won't work. if you have possibility to root that device you can modify the para partition and set off-mode-charge manually.
Click to expand...
Click to collapse
Yes, that was my backup strategy. But how do I root it? There is no TWRP version for the Soyes XS12, and I have no other knowledge of how to root phones. I can seem to send adb commands, but not fastboot.

either with WwR MTK v2.51 beta + SP Flash Tool or with mtkclient. your first goal: dump the para partition or the ROM/boot.img off the phone while in preloader mode. once you have it, you can modify it or root the phone.
mtk-su could also work.

There is nothing you can do even if you root the phone. The system partitions cannot be mounted in r/w mode.

don't need to mount system rw on systemless-root.

Mi projector MJJGYY02FM crashed

Good morning,
I'm new here, and i hope you can help me with my problem.
I have a mi MJJGYY02FM projector and i did a update with USB stick with files from Xiaomi.
Now after the update the projector start with MI logo and than shuts down, after that he start up with no screen and do nothing.
Can someone help me how to fix this. i can't get the projector in a boot menu with the remote, maybe he dont recognize the remote.
Kind Regards,
Bas

Reflash projector's Stock ROM.

jwoegerbauer said:
Reflash projector's Stock ROM.
Click to expand...
Click to collapse
I have the stock ROM on USB now, but hè will not install it. When i press the home and enter button and plug the power cable. Hè start up with the MI logo and shuts down, then start up with no screen.
Are there other ways to install the stock ROM?

AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>

jwoegerbauer said:
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
Click to expand...
Click to collapse
Thanks
Im gonna search out and try that option.
I let it know when it works. maybe i have some questions.

jwoegerbauer said:
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
Click to expand...
Click to collapse
Im trying something, but do you have a discription how to make that USB with the Stock Rom?
I got your files on my pc. I have a 16GB USB format FAT32.
What is the way to make that sideload with the ROM version?
Im sorry for the questions, but i have never done this before.

I have done thist thing
{
"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"
}

The USB-stick, once plugged into Windows computer, in Windows OS is recognized as a drive: note down this drive letter returned. Then sequentially run the ADB commands listed above.

jwoegerbauer said:
The USB-stick, once plugged into Windows computer, in Windows OS is recognized as a drive: note down this drive letter returned. Then sequentially run the ADB commands listed above.
Click to expand...
Click to collapse
Must i do the commander when the stock ROM is on the USB?
By what command must i write the letter from the USB?

Vross46 said:
Must i do the commander when the stock ROM is on the USB?
By what command must i write the letter from the USB?
Click to expand...
Click to collapse
My drive letter is :e

Didn't think it can be so difficult.
Assumed the Stock ROM's file is located in root of E: drive then the ADB command in your case becomes
Code:
adb sideload E:\<NAME-OF-STOCK-ROM-ZIP-FILE>
where you have to substitute
<NAME-OF-STOCK-ROM-ZIP-FILE>
by ROM's true file name

jwoegerbauer said:
Didn't think it can be so difficult.
Assumed the Stock ROM's file is located in root of E: drive then the ADB command in your case becomes
Code:
adb sideload E:\<NAME-OF-STOCK-ROM-ZIP-FILE>
where you have to substitute
<NAME-OF-STOCK-ROM-ZIP-FILE>
by ROM's true file name
Click to expand...
Click to collapse
ah ok. lets try.
It seems not so difficult but, for the first time is everything more difficult

What do i wrong. sorry! I do really my best
1, i have a format 16gb usb FAT32
2. i have install ADB installer.
3. i have download the stock rom (see picture)
4. my drive name is e:
5. When i zip my stock rom file, i got an another zip file, and an file of 1kb
in the next picture is what i do in CMD
anglee_full_9.0.0.1911 is my zipped stock rom downloadfile
the other 2 are the unzipped files from the first file

1st screenshot provided above shows
1. Device isn't connected via USB-cable with PC or, if, not powered on
2. The ROM's archive name you entered is without fileextension -> required :ZIP
If ROM's archive is packed as .RAR file then you have it to repack to .ZIP file

I think it will not gonna help.
When i connect my projector to the pc, the pc dont recognize him.
What i try, nothing works.

but thanks for your help anyway

Have you ever enabled "USB Debug" in Android's Settings -> Developer otions?

I dont know if its enabled. But now in can not come in the menu.
MI logo shine for 1 second. And it turns off.
So i have no possibillity to check

Vross46 said:
I dont know if its enabled. But now in can not come in the menu.
MI logo shine for 1 second. And it turns off.
So i have no possibillity to check
Click to expand...
Click to collapse
Hello Vross46, have you been able to solve your problem? I’m stuck with the logo as well

Radiant max 5g sytem crash

OK I could use a hand if anyone can help. I have an att radiant max 5g, not a super popular device already, and not a whole lot of support from manufacturer. I had been playing around learning to root a few months ago, but gave up after none of the file downloads could be found online. Last week was screwing around and showing someone the gsi updates that can be applied through the dynamic systems updates on Android 11, and without even thinking downloaded the first build, without enabling USB debugging or unlocking the bootloader. And on reboot, all I get now is the "your device is corrupt and cannot be trusted screen" which then turns back off immediately afterword. So these are the methods I have tried, and the tools I have to use. I do not have a pc, and the only device to device connections I can establish is a phone to phone USB link using the bugjaegar app. It will establish a limited connection and allow me to boot the phone into fastboot, but that is all. Recovery mode only pops up the same corrupted system screen and shuts off. So no recovery mode. I can issue fastboot commands tho. I found online some of the factory os image files and downloaded, have them stored in a zip, but the target phone still has USB debugging locked, so I have not found a way to remotely unlock the bootloader to apply new image file. The getvar fastboot tells me all the specs, and that the bootloader is registering a successful boot from slot a after 1 attempt. I tried switching the bootloader to boot from slot b, hoping my original would have been pushed there after the update. It still gave me the corrupt message, but the successful boot took 7 attempts to achieve that time. I've looked through pages and pages trying to find a way around this, but am running out of ideas. Things I absolutely cannot get access to are a pc tho I may be able to get my hands on a tablet that may run the standard debug tools, or a repair center of any kind I am in a remote area and when I say remote I mean remote. But I would very much like to salvage this thing if possible in anyway. Thanks anyone for any help am taking the time t read.

Just to add, without USB debugging enabled everything I've tried keeps getting roadblocked, flashing anything to the partitions like a custom recovery or sytem image, or even tried to see if any way to sideload the files onto the device and activate them remotely, but get the same result for the same reason. I can screen shot the variables I get back if it would help. Also I am able to establish an adb bridge and issue normal shell commands, although this is not easy, bc when I attach the USB cords, it automatically tries to turn the corrupted device on, which almost immediately goes to the warning screen, and I have a 30 second window where the shell is active before the device turns off and the connection is lost and has to be established. Also bugjaegar app is limited in what commands it will execute. But it does work. Ish.

ADB is used to operate on Android platform's system files, Fastboot is used to operate on Android platform's bootloader - what initializes the Linux kernel : 2 totally different things.
To enable dealing with the bootloader - means successfully run Fastboot commands - on phone the option OEM Unlock must get turned on
{
"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"
}
and the command
Code:
fastboot flashing unlock
must be run.

Thats the brick wall I keep circling around in too. Without the USB enabling turned on, I can't remotely unlock the bootloader thru command window and flash the file, but I cannot get the device to boot up in any form to be able to enable that option. So looking for door #3, although now that I think of it that seems weird, bc I can interact with the bootloader, I ran the command 'fastboot set_active b' and it took that command and successfully ran the boot process from the backup slot. And it did that without USB debugging enabled....

Update: even tho looks like there is going to be no help coming, things have taken a turn for the unfortunate anyway. Had connection to target device with this phone via bugjaegar app, had an idea that got myself all excited and in my rush to attempt, tapped command 'fastboot reboot fastbootd', whatever the f that is, instead of 'fastboot reboot bootloader' and whatever fastbootd did, it fd my system, with a very large falice. Completely lost my ability to boot into bootloader mode now, using either shell commands or using vol/power buttons. Unable to establish any type of device connection with host device now. For all intents and purposes fastboot is now extinct, there is little to zero info online about what could possibly have happened, and looks like jig is up. Yay. Lol.

TnKnight said:
Update: even tho looks like there is going to be no help coming, things have taken a turn for the unfortunate anyway. Had connection to target device with this phone via bugjaegar app, had an idea that got myself all excited and in my rush to attempt, tapped command 'fastboot reboot fastbootd', whatever the f that is, instead of 'fastboot reboot bootloader' and whatever fastbootd did, it fd my system, with a very large falice. Completely lost my ability to boot into bootloader mode now, using either shell commands or using vol/power buttons. Unable to establish any type of device connection with host device now. For all intents and purposes fastboot is now extinct, there is little to zero info online about what could possibly have happened, and looks like jig is up. Yay. Lol.
Click to expand...
Click to collapse
Since Android 10 fastbootd resides in user-space, so these commands are needed to directly start system in fastbootd mode:
Code:
adb devices
adb reboot fastboot
or
Code:
fastboot devices
fastboot reboot fastboot

jwoegerbauer said:
Since Android 10 fastbootd resides in user-space, so these commands are needed to directly start system in fastbootd mode:
Code:
adb devices
adb reboot fastboot
or
Code:
fastboot devices
fastboot reboot fastboot
Click to expand...
Click to collapse
The problem Im finding now is that the whole thing is gone wonky. Originally, when I connect USB from host phone to target phone, it will automatically turn target phone on and attempt to boot. The white screen with android will pop up, and this small window of about 20 to 30 seconds is all the time I have that the host phone recognizes a device it connected. I get a command prompt on host to allow access to the M65 preloader, I OK it, and then can quickly hit the fastboot reboot bootloader command. After the initial boot attempt, I would get thrown to the 'device is corrupt screen' the connection will drop off and then the target phone will shut itself off. If left plugged in the target will repeat the process only this time the connection has been established connects a little quicker, or it goes ahead and reboots in bootloader. Or I could use power/vol key to bring up menu and enter bootloader that way.
But now after hitting that fastbootd, the key functions will not bring up the menu anymore, and there is no delay in the preload startup. It goes immediately from white screen to corrupt warning and then shuts off. By the time the prompt to allow connection hits screen the target phone is already powering down. And it just keeps repeating this short cycle. I dunno at a loss on this one.