Database Develop

activate usb debugging over adb without recovery

The one of my gf stucked in bootloop. Everthing is stock and she didn´t updated it a long time. The problem is we want to backup some things, for example the pictures. I thought about backup with adb but usb debugging isn´t turned on. I don´t know how to activate over adb or if this is possible without recovery. When i install a recovery i need to unlock the bootloader an all thing are deleted.
So is it possible to activate usb debugging over adb without an recovery or is there an other way to backup?

hansi66627 said:
The one of my gf stucked in bootloop. Everthing is stock and she didn´t updated it a long time. The problem is we want to backup some things, for example the pictures. I thought about backup with adb but usb debugging isn´t turned on. I don´t know how to activate over adb or if this is possible without recovery. When i install a recovery i need to unlock the bootloader an all thing are deleted.
So is it possible to activate usb debugging over adb without an recovery or is there an other way to backup?
Click to expand...
Click to collapse
You can only get adb connectivity when booted in a custom recovery or when booted in the OS with USB debugging turned on (USB debugging doesn't matter when in a custom recovery). When booted in bootloader mode, you'll only get fastboot connectivity.
There is nothing you can do to backup the files, like you v said, unlocking the bootloader will wipe everything.
There are 2 possibilities to recover the phone:
Unlock the bootloader, flash a recovery, flash a rom ---> will wipe the phone
Flash a RUU (if any available for your version) ---> will wipe the 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"
}

I have the same problem - but I was able to get the USB working.
Even though it is in a bootloop, as soon as you have access to the phone, go into the Settings and "About", the click the build number over and over until the phone tells you that you are a developer (i think it is 12 times).
Then go back (or if the phone bootloops, wait until you can access the system menu again) - then go into the Settings again and click Developer, and allow the USB debugging.
You should then be able to connect your phone to the USB, and access the hard drive of the phone.
From there, you have about 2 min during every bootloop to get any data/ pictures/ etc off of the phone.....
(sadly I'm in that bootloop craziness too, and trying to figure out how to get out of it without rooting the phone)

elisaw99 said:
I have the same problem - but I was able to get the USB working.
Even though it is in a bootloop, as soon as you have access to the phone, go into the Settings and "About", the click the build number over and over until the phone tells you that you are a developer (i think it is 12 times).
Then go back (or if the phone bootloops, wait until you can access the system menu again) - then go into the Settings again and click Developer, and allow the USB debugging.
You should then be able to connect your phone to the USB, and access the hard drive of the phone.
From there, you have about 2 min during every bootloop to get any data/ pictures/ etc off of the phone.....
(sadly I'm in that bootloop craziness too, and trying to figure out how to get out of it without rooting the phone)
Click to expand...
Click to collapse
You got something very wrong. Bootloop means the phone won't boot up. It stays on boot animation and can't boot Android, so that means he can't go to settings or anywhere except bootloader menu or recovery. Most likely you had "system crash" error which is not anywhere near bootloop

Cannot get device shown in "List of devices" while trying to root

I'm trying to unlock bootloader. Checked all options in dev options like USB debugging and enable unlock bootloader.
Installed all the drivers. Booted into bootloader.
But when trying to see "adb devices", it doesn't show any devices.
For sometime, it shows some kedacom usb driver. I tried googling and tried to uninstall it and use google driver also. Even in device manager, it shows Android Device - Android ADB Interface, but still it shows nothing in list of devices attached in adb.
Also tried this thread - https://forums.oneplus.net/threads/solved-adb-is-not-working.347296/, but still doesn't work. Can someone help me out here?
{
"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"
}

Do you have TWRP installed? In that case flashing Super Su or Magisk from within TWRP should get you rooted. If TWRP isn't installed, Check for Funk Wizards thread in the official forum https://forums.oneplus.net/threads/...a-help-thread-ask-your-questions-here.477285/
Also, adb doesn't work from bootloader. It's fastboot in the bootloader. Enter recovery and check then

Seems like your phone is in bootloader/fastboot mode instead of in-rom ADB or TWRP ADB mode. This is the mode you're phone has to be in to be able to flash other recoveries like TWRP which however also requires your phone to be OEM bootloader unlocked (which completely wipes your phone), and from there you enter TWRP recovery using bootloader menu or power plus volume down, and there flash the latest 2.79 SR3 SuperSU to archive root/sudo functionality.
Either that or you actually did activate ADB under development options and accidentally installed the ADB device using the fastboot/bootloader driver instead of the ADB device driver.

When your in fastboot, you need to use fastboot devices as the command and other fastboot commands. You use adb devices command when your using adb, and connected with phone in recovery or booted.
I just installed the drivers that are on the phone when you plug it in in windows and minimal adb and fastboot from xda.

Thank you all. I followed ur inputs and now it worked fine. I installed a custom rom too.
Thanks again.

Akhyll said:
Thank you all. I followed ur inputs and now it worked fine. I installed a custom rom too.
Thanks again.
Click to expand...
Click to collapse
Excellent, enjoy.

Yet another unlock bootloader question

I have a Nokia 8 model TA-1052 (this is NB1, correct?). It has a locked bootloader and is running Android 9.
I understand the HMD service for unlocking the booloader is no longer available and the only option now is using a Hikari's website.
Before I try Hikari's method I want to make sure that fastboot is working (I understand it is required?).
With the phone connected, the command "adb devices" show the phone listed but any fastboot command seems to not being able to find the phone (e.g. "fastboot devices" returns nothing).
Am I missing anything?
Thank you.

Assuming you are on Windows what does device manager show when you put the phone into fastboot mode?
Obviously you need a working driver for fastboot mode which is separate from the adb driver - how did you install the drivers and which ones did you use?

dt_matthews said:
Assuming you are on Windows what does device manager show when you put the phone into fastboot mode?
Obviously you need a working driver for fastboot mode which is separate from the adb driver - how did you install the drivers and which ones did you use?
Click to expand...
Click to collapse
I don't have any specific Nokia drivers installed. The only USB driver showing (that seem to be related) is "ADB Interface".
I know that for some people the Nokia driver comes on the phone but mine isn't. Where can I get the driver from?
EDIT: in download mode the Win10 Device Manager shows an unknown "Android" device under other devices

There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/

emufan4568 said:
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
Click to expand...
Click to collapse
Thanks that worked

emufan4568 said:
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
Click to expand...
Click to collapse
This is an essential part of unlocking the bootloader.

emufan4568 said:
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
Click to expand...
Click to collapse
i just unlocked my phone with this tool and somehow it's back to android 8.1 oreo, is that the normal behavior?

Hi, i used the methode in the link above but now my phone is stuck on the Nokia logo and won't boot to OS.
I can let the batterij drain and power it on but then i get this message in the picture.
Manually getting it into download mode is impossible (holding combo keys volume down and power looks like that doesn't work)
{
"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"
}
Some idea how to fix this? Luckely its not my daily driver but a testdevice.

I have it working again, let battery fully drain, then i could get into download mode (holding vol- while plugging usb) then I could run the tool again (had to request new OTP) and now it just boot normally

'fastboot devices' command not working

Hi guys, I specially made an account due to this frustrating event of not being able to use the fastboot devices command after unlocking my Max Pro M1's bootloader, so as to install a Custom ROM.
Tried everything possible but to no avail. The adb devices command works fine and my phone shows up on the computer. But on fastboot, when i execute the command 'fastboot devices' i get a response with "????????" and my phone screen turns black with a message on the top left corner stating press any key to shut down. PLEAAASE HELP!

D0CT0RFATE said:
Hi guys, I specially made an account due to this frustrating event of not being able to use the fastboot devices command after unlocking my Max Pro M1's bootloader, so as to install a Custom ROM.
Tried everything possible but to no avail. The adb devices command works fine and my phone shows up on the computer. But on fastboot, when i execute the command 'fastboot devices' i get a response with "????????" and my phone screen turns black with a message on the top left corner stating press any key to shut down. PLEAAASE HELP!
Click to expand...
Click to collapse
Enable oem unlock in developer options
and does your phone show when you do " adb devices "

flairepathos.info said:
Enable oem unlock in developer options
and does your phone show when you do " adb devices "
Click to expand...
Click to collapse
Hey, I'm unable to locate the "oem unlock" option under developer options. However, i tried unlocking the bootloader yesterday with help of USB debugging. That didn't initially work, so i did the bootloader unlocking through the Asus app that i downloaded externally, which was successful (without PC).
That aside, adb seems to be working fine as the command "adb devices" results in showing my phone as connected. But 'fastboot devices' command simply does not work, so now I'm just left with a Bootloader unlocked phone.

Attaching a picture for more clarity.
These are the commands I typed after my phone entered fastboot mode.
After the last result, my phone screen turns black with a message on the top left corner saying press any key to shut down.
There seems to be a problem only with fastboot.
It would be great if anyone could provide a solution or help in any way possible!
{
"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"
}

D0CT0RFATE said:
Attaching a picture for more clarity.
These are the commands I typed after my phone entered fastboot mode.
After the last result, my phone screen turns black with a message on the top left corner saying press any key to shut down.
There seems to be a problem only with fastboot.
It would be great if anyone could provide a solution or help in any way possible!
View attachment 5400501
Click to expand...
Click to collapse
It's probably something in the boot partition or tee partition, this is first time i see this but i did some research and found that it's not a hard locked device and releases with the developers proprietary engeneering drivers and user drivers
so the commands must be done in succession when enter fast boot using a bat script : here is the guide
[GUIDE][UNLOCK/RELOCK] Bootloader Unofficailly and Flash TWRP+Root
DATA WILL BE WIPED SO MAKE A BACKUP (instructions are there in rar too) Unlocking 1. Download this rar and you'll get 2 folders namely unlock and ASUS_Android_USB_drivers_for_Windows 2. Install the drivers according to your OS and go the unlock...
forum.xda-developers.com

Thanks man, will try it sometime and give an update. As of now, this is my sole phone, so i'll work around with all this once i get a replacement. Until then, stock ROM it is

Quick update! 'Fastboot devices' command worked fine on my old PC with Windows 7 on it. Didn't require any extra steps nor did I go through any hassle like on the newer Windows 10. And ofc I was also able to install the custom recovery as well.
This clearly looks to be a Windows 10 issue.

Question Bricked My Redmi note 10 5g Device

Hello guys..
I have a Redmi note 10 5g global and was trying to fastboot flash Indonesian ROM using Mi Flash Tool ,it started well and stopped due Preloaded error, I tried again but it persisted so I unplugged my device and tried powering it up but it wont power on,won't show charging but only makes sound when Connected to PC,I tried alot of things to fix the Preloaded but with no success.
I badly need help To fix this problem guys..

dannykuma said:
Hello guys..
I have a Redmi note 10 5g global and was trying to fastboot flash Indonesian ROM using Mi Flash Tool ,it started well and stopped due Preloaded error, I tried again but it persisted so I unplugged my device and tried powering it up but it wont power on,won't show charging but only makes sound when Connected to PC,I tried alot of things to fix the Preloaded but with no success.
I badly need help To fix this problem guys..
Click to expand...
Click to collapse
try booting into fastboot, if not, boot into brom and flash stock miui via sp tool
open up device manager to make sure everything is right.
boot into brom by holding VOL-, VOL+ and POWER, at the same time connect the phone to ur pc. if it does the connected sound, check on device manager if the driver is missing. it should have a warning sign, if it does then install the drivers i annexed below the post (ive used them and it worked, up to u)
after installing them, by the meantime ur phone probably has restarted, so reboot it into brom once again and check devices manager. if it worked it should look something like this:
{
"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"
}
with sp tool ready to flash. but first you might need to auth bypass because of MIUI account.

1lopes said:
try booting into fastboot, if not, boot into brom and flash stock miui via sp tool
open up device manager to make sure everything is right.
boot into brom by holding VOL-, VOL+ and POWER, at the same time connect the phone to ur pc. if it does the connected sound, check on device manager if the driver is missing. it should have a warning sign, if it does then install the drivers i annexed below the post (ive used them and it worked, up to u)
after installing them, by the meantime ur phone probably has restarted, so reboot it into brom once again and check devices manager. if it worked it should look something like this:
View attachment 5733123
with sp tool ready to flash. but first you might need to auth bypass because of MIUI account.
Click to expand...
Click to collapse
Thank you very much for the help....
Let me try

indonesian rom is fully compatible. sure u made something bad.
your bootloader is unlocked???? u have downloaded fastboot version? clean flash selected? write al steps u did with precision. i'm 100% sure is not a compatibility problem. i have installed indonesian rom more then one time without any problems
IF U CAN ENTER INTO FASTBOOT, U CAN RESTORE YOUR PHONE WITHOUT PROBLEMS. stay away from advanced procedures like restore preloader. First try the easyest solutions. If didnt work i suggest mtkclient under arch linux for reflash boot vbeta and preloader. But follow my tip: enter into fastboot and reflash stock using adbdastboot tool. Is the easyest solution