Database Info

[Help Thread][ Nokia 3.1](2018) Ask Any Question, Noob Friendly

This thread has been created
for
Questions & Answers/Troubleshooting
Specific to
Nokia 3.1
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button, in lieu of simply posting "Thank you".
{
"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"
}
Please keep the discussion focused, on questions pertaining to this Device
List of supporters​...​...​...​...​
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.​If you have ROM-related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!​​Supporters: If you want to be put on or off the list, just make a request here in the thread!​Before posting anything, I strongly advise you to read​
Forum Rules
[Index] XDA 2021: How to navigate the new site
[Index] XDA 2021: Navigating the New Forum App
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here. ​

saved 2

Hello. I've been trying to unlock the bootloader but the volume keys don't work in fastboot mode.
When I give the command "fastboot oem unlock" the phone shows a message asking me to either press volume up to choose "yes" or volume down to choose "no". However, in this mode the volume buttons don't work so I can't choose an option. What's up with that?

I got Nokia 3.1 from Amazon, brand new, no carrier. Out of the box I see two issues:
1. Device is not getting OS updates. About dialog shows patch level of "May 2018". I expect Android One device to have an update by now. In two weeks since I've got the phone there have been no OTA update.
2. Google play app shows device as "uncertified". However, google apps work just fine.
Otherwise, the phone is great for the price. How do I fix these issues? Nokia support forum has a few posts describing the same issue, but no replies from Nokia.

Some questions:
- Is the lowest brightness low enough for comfortable reading at night?
- Does it have a fullscreen / scaling option (since it's 18:9 screen)? I saw some Nokia phones have an icon in the recent apps window (for each app).

I have a Nokia 3.1 plus..
The recent system updates are not being installed.. I've tried downloading and installing several times but the same message "couldn't install system update" is shown

nick_white said:
- Is the lowest brightness low enough for comfortable reading at night?
Click to expand...
Click to collapse
I just set mine up. I found that 0% is too bright on its own, but 0% brightness plus night light works, so I put that on my quick settings.
The showstopper for me with this phone is poor noise levels on the 3.5mm audio output. I must have been spoiled by higher-end phones before this one if this is par for a budget phone. The lack of a notification LED was also not called out in the reviews I read.
I don't think I'll keep this as my daily phone. I hear the LG Q7+ calling.

Need ROM for Nokia 3.1 India firmware
Please add ROM for this device. I am not getting the firmware for this device.

I want to unlock the bootloader and root the phone (rooting is the purpose !) but it doesn't work as it says on websites.
I get the phone to the fastboot menu but it doesn't work :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ES2BA80801000972 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command.)
finished. total time: 0.007s
any ideas ??
UPDATE :
It's interesting that the phone accepts this :
>> fastboot flashing lock_bootloader
but rejects this :
>> fastboot flashing unlock_bootloader
Am I missing something here ???

how to improve the battery life..i almost charge everyday for 1.5 - 2hrs.

Got the bootloader unlocked
Sent from my Nokia 3.1 using XDA Labs
Sent from my Nokia 3.1 using XDA Labs

Hello, please tell me what to do. The phone does not turn on, vibrates when connected to power, the computer does not see.

Ok so I am working with a
nokia 3.1/ ta1141
Android 9
Cricket network locked
No original sim
I want to unlock root and knock it down to basic factory ..
Developer options are on
OEM UNLOCK is grayed out
But I can talk to device with ADB and Fastboot and can load into download mode but not recovery mode ( no command when power and volume + key is pressed )
So with that said what am i missing and why can't I get root
I have...
ADB / Fastboot
Magsik
...
I would like to pull and load original factory boot without carrier bloatware
Thanks in advance for any direction with this !!

417techandgrow said:
Ok so I am working with a
nokia 3.1/ ta1141
Android 9
Cricket network locked
No original sim
I want to unlock root and knock it down to basic factory ..
Developer options are on
OEM UNLOCK is grayed out
But I can talk to device with ADB and Fastboot and can load into download mode but not recovery mode ( no command when power and volume + key is pressed )
So with that said what am i missing and why can't I get root
I have...
ADB / Fastboot
Magsik
...
I would like to pull and load original factory boot without carrier bloatware
Thanks in advance for any direction with this !!
Click to expand...
Click to collapse
That's a Qualcomm device correct?
Try messaging @sltushar

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.

ASUS TABLET P00I (CGH017984) frp unlocking help

i got a nice ASUS TABLET P00I (CGH017984) from ebay and as you guessed it it is locked with the frp. i tred all i know and even some you tubes and so far nothing works. so is there a chance someone here has a way to unlock one of these. or i will need to send it back to the seller. along with some neg feedback. they said when i asked them if it was unlocked and they said it was networked unlocked and it was usable, well they lied i guess. it even came with a sim and that number was in it, i called that number and it rang busy. my guess is because it is not activated so google sent the busy signal. i asked the seller to see if they could get the last username and password. the device comes up with the phone and then wants the last user's name first and last and i do not know what is will ask for after that.
i know they make these hard to bypass so people will not just steal them for a fast buck. i got this from a pawnshop seller so maybe the owner needed some fast money or a crook did. anyway now it is my issue if can figure out how to fix it or maybe i can send it back. i would like to keep it but if i can't get it to go back it goes.
thanks, for any ideas or help

enter fastboot mode and confirm model ZT500KL then find firehose programmer and erase FRP partition from EDL mode

mine will not show the arrow or the clock when i get to the point of going to yourtube. mine wants to updated youtube and when trying to update you tube i have to have the account setup because it want me to enter my user name and password. and i do not have them. so that procedure will not work for me. i spent hours yesterday looing for a way around that and could not fine it. i even found that asus frp program in the rar format and could not find any unzipping program to open the rar and then try to get thet into the tablet. i connected the table to may win10 pc

sorry but I won't explain anything about EDL mode if you're not even able to unpack rar file

ok not a problem it is going back thanks for the help.

i tried to open the asus rar file and 7 zip failed WinRAR failed WinZip failed. it needs some type of password to get into the program to unpack it and i can't seem to find the password so that is why i just quit. if you know the password that might help. providing that file with manage to get into the table without me being able to get past the user name and password section. thanks

read the site where you got download from

i did i have used all of those unpacking programs. i did not see on that asus site where they had the password posted. but i will go back and see if i can find it
ok i think i got the tool open turns out htey have different passwords anyway i ahve a window open on the s4tri0 team site and i have 3 options fastboot tool the edl tool and the asus mtk tool so now to figure out how to use them. in the fastboot tool i see quite a few options but i do not quite know yet what one to pick? i think these are the models but i do not see the p001 model and i do not know yet how to find one of these models if mine is one of these.
i think i need the last photo that show the p001 z170mg button. but then how would i get the tablet and the pc to talk to each other? i had the tablet plugged into the laptop usb port and it did not show up in the files section.
{
"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"
}

share link please, curious about asus provides frp bypass files

Asus FRP Bypass Tool Download free
Download Asus FRP Bypass Tool Latest Verison Free 2021 FRP TOOL you can unlock the Factory Reset Protection from most Asus device
bypassfrp.net

yours is Qualcomm MSM8956 Snapdragon 650 processor? so check specifications for each model if one of these is same SoC like yours
Asus Zenpad Z10 ZT500KL - Full tablet specifications
gsmarena.com
@Renate do you have prog_emmc_firehose_8956_ddr_asus1.mbn

ok if i click in the fastboot tool page it comes up and says waiting for devide. so if i connect the tablet and click on the wrong tab in that page will that mess with the device \? in the next page the edl page i click on the a001 button and it comes up and says comport erro quailcome not found. on the last page nothing shows it open a new tab and then sayd not there.
so if i boot the tablet to the fastboot and have the tablet connected to the pc and then click on one of the first-page fastboot tools will that tool try to unlock the tablet? and if i pick the wrong button that button will not brick the tablet will it? so if that button i pick is not correct nothing should happen?
i click all those buttons and not of them did come up and tell me the info you posted for this p001 tablet. thanks

please power off device, hold volume down + power + plug in usb cable computer to enter fastboot mode.
when tablet connected in fastboot mode, install android_winusb.inf and select Android Bootloader Interface driver.
once drivers installed, download fastboot.exe and type the following command in cmd.exe (from within platform-tools directory)
Code:
fastboot devices
if it shows serialno you are connected in fastboot mode. you can now get some device info to figure out it's mediatek or qualcomm.
Code:
fastboot oem device-info
fastboot getvar all

i did that i powered it down held vol down and power and the back page came up i have these options in the fast boot menu i arrow down to the reboot fast boot with the tablet plugged into the pc and it it comes bact to this same page.
then i went to the asus page in that tool and clicked on the a001 button and it tells me itis waiting for device.
so i tried the usb debug mode and it came up to the log in page and i can't log in because is want the last users info

it just is not connecting to the pc. i changed cables and now the pc beeps when i plug in the tablet but it does not show in the folder on the left like the phone does. and it fails to connect when plugged into the pc in the fastboot menu and the frp tool will not see it either.

yes, that fastboot options menu actually is fastboot mode. proceed with installing drivers from windows device manager.

ok when i let it just bootup i see p001 in the folder section but in fastboot i do not see it. when i see p001 in the folders i can't copy anything into the p001 folder. so i'm at a loss i guess. i asked that frp site if they have a file for the ZT500KL tablet so now i have to wait and see if they do. they answer in that sites question section and i did send them an email so they may reply back in my email as well.
outside of that do you know in the attschment i sent that show the fastboot page what else i may try? thanks

kindly read post #14 again. you're not reading carefully

ok i thnk i got it by using that youtube. i can turn it off and back on and it comes back. i'm kind of scared to do a reset because it may go back the other owner. what do you think? thanks

Access phone on computer with broken screen

Basically, my Redmi note 8 pro screen broke and I can neither touch nor see anything on the screen I can't authorize it to connect to MTP because it defaults to charging, ADB only shows up in recovery, and fastboot the phone is connected to the internet via mobile data. My objective is to get vysor to recognize the device so I can mirror the screen I have Pixel Experience 13 any help would be awesome the device is still connected and accessible by google because i can ring it in find my devices
Maybe turning talkback on would help but it doesn't wanna turn on

Mystic1243 said:
Basically, my Redmi note 8 pro screen broke and I can neither touch nor see anything on the screen I can't authorize it to connect to MTP because it defaults to charging, ADB only shows up in recovery, and fastboot the phone is connected to the internet via mobile data. My objective is to get vysor to recognize the device so I can mirror the screen I have Pixel Experience 13 any help would be awesome the device is still connected and accessible by google because i can ring it in find my devices
Maybe turning talkback on would help but it doesn't wanna turn on
Click to expand...
Click to collapse
You can use scrpy via usb.
Download it here

mvikrant97 said:
You can use scrpy via usb.
Download it here
Click to expand...
Click to collapse
I can't authorize USB Debugging without unplugging from the computer and then plugging in the mouse to press Yes
And double clicking on the scrcpy executable flash a terminal window really quickly then exits

If USB Debugging successfully got enabled on phone, then you can run ADB shell commands when phone gets booted into Recovery mode.

jwoegerbauer said:
If USB Debugging successfully got enabled on phone, then you can run ADB shell commands when phone gets booted into Recovery mode.
Click to expand...
Click to collapse
I can see the phone through recovery mode yes but what commands can help me in this case

Mystic1243 said:
I can see the phone through recovery mode yes but what commands can help me in this case
Click to expand...
Click to collapse
The recovery is TWRP

Mystic1243 said:
I can't authorize USB Debugging without unplugging from the computer and then plugging in the mouse to press Yes
And double clicking on the scrcpy executable flash a terminal window really quickly then exits
Click to expand...
Click to collapse
I fixed my Nokia 8 Sirocco display today but the thing is my phone was already authorised to access ADB before,
so I have no problem in accessing it on my computer through SCRPY.
{
"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"
}

mvikrant97 said:
I fixed my Nokia 8 Sirocco display today but the thing is my phone was already authorised to access ADB before,
so I have no problem in accessing it on my computer through SCRPY.
View attachment 5867593
Click to expand...
Click to collapse
I can access ADB in Fastboot and recovery though and bootloader is unlocked , Know of any solutions?

You can't access ADB when in Fastboot mode: simply technically not possible.

jwoegerbauer said:
You can't access ADB when in Fastboot mode: simply technically not possible.
Click to expand...
Click to collapse
I can use fastboot commands is what i mean but idk what commands to use in either TWRP or fastboot

OMG: Take note that Fastboot deals with device's bootloader, whereas Recovery deals with device's Android OS.
Because phone has an SD-card slot ( ready for microSDXC cards - uses shared SIM slot ) then if the SD-card gets mounted by default at boot time then you can try to copy the Android data in question onto microSDXC card using Android's dd command.
FYI: Before copying the data make sure the partition where the data are housed gets decrypted.

jwoegerbauer said:
You can't access ADB when in Fastboot mode: simply technically not possible.
Click to expand...
Click to collapse
It's a bit of an uncommon combination, but you could configure to use both fastbootd and adb.

Mystic1243 said:
The recovery is TWRP
Click to expand...
Click to collapse
I'm aware that you might have thought about this but just out of curiosity.
I contacted a trusted local spare parts vendor in my area and he said that the display costs around ₹950.00 only in India which comes to $11.51 USD.
I repair phones so if you stay here in India I can assisst you in that. Please let me know.

mvikrant97 said:
I'm aware that you might have thought about this but just out of curiosity.
I contacted a trusted local spare parts vendor in my area and he said that the display costs around ₹950.00 only in India which comes to $11.51 USD.
View attachment 5867673
I repair phones so if you stay here in India I can assisst you in that. Please let me know.
Click to expand...
Click to collapse
No sadly im not in india sorry

jwoegerbauer said:
OMG: Take note that Fastboot deals with device's bootloader, whereas Recovery deals with device's Android OS.
Because phone has an SD-card slot ( ready for microSDXC cards - uses shared SIM slot ) then if the SD-card gets mounted by default at boot time then you can try to copy the Android data in question onto microSDXC card using Android's dd command.
FYI: Before copying the data make sure the partition where the data are housed gets decrypted.
Click to expand...
Click to collapse
I can access the data already in TWRP i just cant extract it because its encrypted and TWRP doesn't support PE encryption AFAIK

What is PE encryption? Never heard of this.

PE = Pixel Experience FBEv2 encryption. one can enable usb-debugging and authorize RSA from init script, no need to decrypt userdata in TWRP. we can place init scripts in system/etc/init or vendor/etc/init or if rooted with Magisk in boot.img overlay.d
Accessing my phone with a dead screen
So my phone screen connector was liquid damaged. No touch or display. It's an Essential Phone which supports HDMI output, however I can't unlock it because I don't see the lock screen on the monitor I just see a lock icon. I have...
forum.xda-developers.com

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.