Hey guys , anyone have a way to enable usb debugging via fastboot ?
Flashing something may do it ?
Leonardo_f said:
Hey guys , anyone have a way to enable usb debugging via fastboot ?
Flashing something may do it ?
Click to expand...
Click to collapse
i also need to find out because i cant even get into my phone due to bootloop issues...i bought my HTC MyTouch 4G from someone & been trying to fix my bootloop, every forum says to make sure "usb debugging" is enabled but i have no idea if it is or if it isnt
also when i use "adb devices" in cmd nothing shows up under list of devices...i just hope there is a command in adb or fastboot to enable/disable usb debugging
GarciaGotti said:
i also need to find out because i cant even get into my phone due to bootloop issues...i bought my HTC MyTouch 4G from someone & been trying to fix my bootloop, every forum says to make sure "usb debugging" is enabled but i have no idea if it is or if it isnt
also when i use "adb devices" in cmd nothing shows up under list of devices...i just hope there is a command in adb or fastboot to enable/disable usb debugging
Click to expand...
Click to collapse
I don't know whether you can enable USB debugging through fastboot ... i'll leave that to the experts.
However you can see your devices when connected to a PC in fastboot mode!
just run ...
fastboot devices
khajoor said:
However you can see your devices when connected to a PC in fastboot mode!
just run ...
fastboot devices
Click to expand...
Click to collapse
yeah i got that part, but when i try to flash or write anything to the device using fastboot i get nothing but errors so im guessing usb debugging must not be enabled
I'm sorry to say, you cannot enable USB Debugging through fastboot.
Hit the thanks button if i helped answer your question
Those errors have nothing to do with USB debugging. Your bootloader might not be unlocked so the flashing commands aren't working, or you're using wrong commands. USB debugging is at the ROM level and is for enabling adb while booted into the ROM. At the bootloader level, only fastboot commands work if the bootloader is unlocked. adb does not work. You need a custom recovery like CWM/TWRP for adb to work, and this recovery has to be flashed via 'fastboot flash recovery <recovery name>.img' on an unlocked bootloader.
Sent from my Nexus 7 using xda premium
Hello,
I'm also interested on this topic. My screen is broken, but the phone is working. I can boot and I feel the phone working and recognising my finger to unlock. However, because I'm stupid and I didn't have the "USB debugging ON" I can't access my files via ADB or any recovery software.
However, I can boot on fastboot and I see my device on "fastboot devides". Can I do something to access my files from there? I don't know... maybe unlock bootloader and flash any kind of TRWP with full adb or something like that.
THanks ¡
lotuxete said:
Hello,
I'm also interested on this topic. My screen is broken, but the phone is working. I can boot and I feel the phone working and recognising my finger to unlock. However, because I'm stupid and I didn't have the "USB debugging ON" I can't access my files via ADB or any recovery software.
However, I can boot on fastboot and I see my device on "fastboot devides". Can I do something to access my files from there? I don't know... maybe unlock bootloader and flash any kind of TRWP with full adb or something like that.
THanks ¡
Click to expand...
Click to collapse
As its name implies, Fastboot operates on device's bootloader and not on device's Android files as ADB does.
BTW: You always can access the user-data stored in Android's file system if USB-MTP mode got enabled on Android device.
jwoegerbauer said:
As its name implies, Fastboot operates on device's bootloader and not on device's Android files as ADB does.
BTW: You always can access the user-data stored in Android's file system if USB-MTP mode got enabled on Android device.
Click to expand...
Click to collapse
True, I can see my Xiaomi on "Windows Explorer", but it's an empty folder because I can't select MTP mode instead of "only charge" mode that it's launched by default.
What if I flash a TWRP recovery (I'll need to open bootloader first) and then from TRWP I try adb?
It must be a solution... if profesional people can do it so we do.
Thanks.
Related
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
anyone knows?
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
Yes, you can access ADB while in a bootloop.
Theonew said:
Yes, you can access ADB while in a bootloop.
Click to expand...
Click to collapse
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
runingwild said:
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
Click to expand...
Click to collapse
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
yes you can I have this before and it's working
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again
Click to expand...
Click to collapse
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
mustafah822000 said:
yes you can I have this before and it's working
Click to expand...
Click to collapse
that can be helpful for me. How did you do it?? was it in bootloop too? not rooted?
Theonew said:
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
Click to expand...
Click to collapse
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
Click to expand...
Click to collapse
Theonew said:
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
Click to expand...
Click to collapse
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
runingwild said:
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
Click to expand...
Click to collapse
Its a driver issue. Check device manager for your "unknown device," then associate adb drivers with it.
you can use adb once the kernel has loaded so root or any other factor shouldn't affect it
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
runingwild said:
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
Click to expand...
Click to collapse
if u are bale to get into fastboot flash a stock ruu and it should work fine
well, what if i cannot access recovery mode or fastboot menu as you have said so. my HTC desire 310 is having bootloop and cant enter recovery. HELP PLEASE!!
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Tommyboy77 said:
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Click to expand...
Click to collapse
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
es0tericcha0s said:
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
Click to expand...
Click to collapse
adb devces does not work in clockwork mod either.....what is the easiest way to get this custom rom sent to my internal sd card if the phone wont boot up and os is wiped off the phone? it is an htc one...
adb should work in CWM... You might have to manually load the driver. Even if every driver works when the phone is booted and all, Windows can still have issues finding the right one in recovery. Check in your device manager. If that doesn't work, then you'll have to see if your recovery supports USB OTG and see if you can load like that. If none of that works, you'll have to reload the OS via RUU and start over with root/recovery/etc.
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
C13v3r0n3 said:
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Neither of those things are options for the OP. He can't boot, so he can't mount USB (mounting USB in recovery hasn't worked for most phones since JB where most phones don't support USB mount - only MTP) and he can't sideload because he hasn't been able to get ADB working.
His options now are:
Find out why the adb driver isn't loading so he can just adb commands to push the file or sideload
USB OTG
Return to stock via RUU
OEM unlocking and USB Debugging enabled.
ADB never finds the phone in my windows 10 install no matter what drivers I force it to use. - Tried USB 2 and 3.
Fastboot does find it if I manually start it in fastboot mode, but it can't do anything to it
Fails to write when doing oem unlock
Just sits there if I tell it to write the recovery image.
Phone functions fine, I just want root and a 3rd party rom to be rid of any built in spyware.
Any ideas? any way to root it without flashing then I can just have the twrp app flash it?
Nevermind, found a way around it. This dialpad command made it work
Personmans said:
Hope this will help someone with trouble getting ADB/Fastboot to work. I assume you have a similar environment to me: Windows 10, with working ADB drivers on another device (LG G4 in my case)
Set up LeMax2 in developer mode and enable USB debugging as usual.
Plug in usb and dial *#*#76937#*#* check the box that says "Enable AT Port"
The device should immediately give you the approval message for USB debugging.
Note: This will not stick after a reboot.
Once I had this working, I did an adb reboot recovery, but fastboot still did not work. With the device connected and at the stock recovery screen, I had to open device manager, delete the LeMax device, and allow it to detect again. Finally it appeared in fastboot devices and I was able to flash recovery.
Click to expand...
Click to collapse
I have Samsung Galaxy Tab S2 that I attempted to root earlier today. I used Odin and CF auto root method. Everything appeared to go fine, until it restarted itself after it was done. When it booted back up, the WiFi was not working. When I turn it on, it is simply stuck on "Turning on...." and nothing happens.
Problem 2: When I connect the tablet to a computer via USB cable, it does not recognize it. I'll hear a chime, so it detects it, but it does not show up in the file explorer. The tablet is set for a MTP USB configuration.
I tried a factory reset, but that did nothing.
I'm not sure what to do now. I do have a micro SD card, so I'm able to move it back and forth from the tablet to my PC to install APKs and other files. I'd like to try flashing a custom ROM to see if that fixes it, but now I'm not rooted. I used the SD card to install a couple of the one click root apps, but they were either unsuccessful, or require an internet connection to use.
I don't know if it's possible to actually install a custom ROM on a device that doesn't have internet access and can't use a USB cable.
If anyone has suggestions as to either of my problems, I'd love to hear it, because as of now I can't do anything with my tablet.
You can try to:
wipe data/cache from recovery and reboot it again to see if the wifi error still exists, or you can flash it again.
You can get and use adb/fastboot, if you haven't already, and check if fastboot (execute fastboot devices in cmd) recognizes your device after the chime sound. If you're lucky and your device is displayed, you can flash it again. All the best!
daphr said:
You can try to:
wipe data/cache from recovery and reboot it again to see if the wifi error still exists, or you can flash it again.
You can get and use adb/fastboot, if you haven't already, and check if fastboot (execute fastboot devices in cmd) recognizes your device after the chime sound. If you're lucky and your device is displayed, you can flash it again. All the best!
Click to expand...
Click to collapse
Thanks. Executing "fastboot devices" returns an empty list, however "ADB devices" returns some sort of serial number with "offline" next to it.
edit: I've been running adb kill-server and adb-start server commands, followed by adb devices, and that will switch the device status from "offline" to "unauthorized". I'm not sure how to fix that. I navigated to my .android folder on my PC and deleted the adbkey file but that didn't help.
In developer settings Enable USB debugging, revoke current USB debug authorizations and allow your PC's fingerprint. You can also enable OEM unlock in case you plan to play with the bootloader and custom ROMs.
Next in cmd after plugging the device in, check if it gets detected: adb devices
If you get the list you've mentioned, execute: adb reboot bootloader
This should boot your device into the fastboot mode where you have full access to your phone, so be careful what you're doing.
If you need more info on fastboot and adb, check out the forums.
Good luck!
daphr said:
In developer settings Enable USB debugging, revoke current USB debug authorizations and allow your PC's fingerprint. You can also enable OEM unlock in case you plan to play with the bootloader and custom ROMs.
Next in cmd after plugging the device in, check if it gets detected: adb devices
If you get the list you've mentioned, execute: adb reboot bootloader
This should boot your device into the fastboot mode where you have full access to your phone, so be careful what you're doing.
If you need more info on fastboot and adb, check out the forums.
Good luck!
Click to expand...
Click to collapse
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
febtober said:
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
Click to expand...
Click to collapse
Have you been asked for a new computer ID to accept after revoking old ones and plugging the device in again?
As long as you don't add new fingerprint of your computer to the device, your device will be unauthorized.
febtober said:
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
Click to expand...
Click to collapse
You need to restock your tablet via odin (to put modem back aka Wifi)
After you restock Install Twrp and install magisk to root, instead of cf-root like you did (this will not breaking the safety net or knox even the modem)
(Note:before install magisk backup your "BOOT" via TWRP)
I am having trouble rooting my Galaxy J7 Prime sm-j727t
Every Odin version I use with every TWRP tar file I try to use doesn't work. They either Fail or Odin stops responding when I try to load the tar file into the AP.
I've tried just using the CF Auto Root and those fail as well.
Any ideas what the issue is? I've been trying for two days with no success
Is your bootloader unlocked?
Emir Çetin said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
I thought Samsung phones come with bootloader unlocked already??
BramaKnox said:
I thought Samsung phones come with bootloader unlocked already??
Click to expand...
Click to collapse
You can check bootloader with dialer (search it).
Of phone has fastboot mode you can check bootloader with fastboot commands (search it too)
Emir Çetin said:
You can check bootloader with dialer (search it).
Of phone has fastboot mode you can check bootloader with fastboot commands (search it too)
Click to expand...
Click to collapse
When I put the phone in FastBoot mode I have the following options
Reboot System Now
Reboot to Bootloader
Apply update from ADB
Apply Update from SD card
Wide data/factory reset
Wipe Cashe partition
Mount /system
View recovery logs
Run graphics test
Power off
Lacking storage booting
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Emir Çetin said:
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Click to expand...
Click to collapse
Am I doing something wrong here ? see attached for screnshot
Emir Çetin said:
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Click to expand...
Click to collapse
I tried a some other steps. Tried using the video on youtube on a tut. When I get to the oem unlock I just get stuck with a msg sayng "waiting for any device" my device is plugged in, from what I know I have updated the samsung drivers (from previous attempt of other methods) the adb bootloader cmd did put my phone into fastboot mode
(White box, blue arrow point down with a straight line under the point)
(Blue screen with Downloading...)
do not turn off target
What am I missing here?
I tried rooting TWRP 3.2.3. with Odin on the phone again and it still failed
Does anyone else have any more insight to a possible solution?
Have you checked bootloader with dialer?
BramaKnox said:
I am having trouble rooting my Galaxy J7 Prime sm-j727t
Every Odin version I use with every TWRP tar file I try to use doesn't work. They either Fail or Odin stops responding when I try to load the tar file into the AP.
I've tried just using the CF Auto Root and those fail as well.
Any ideas what the issue is? I've been trying for two days with no success
Click to expand...
Click to collapse
Witch android you are?