I have been round all these forums X-times, have had well-meaning and helpful replies but no solutions. (Thank you Animatechnica). To recap:
My Galaxy Tab forgets all settings changes, uninstalls, and any newly installed files on reboot.
This means I cannot apply USB debugging before going into downloading mode and adb will not work FROM DOWNLOADING MODE.
(When I apply USB debugging on the tablet once booted and using MS cmd moad, and then launch adb, it DOES return a device number, but this does not work in download mode, when the USB debugging setting has been forgotten on reboot)
I have tried :
- Soft reset
- Factory reset through "settings", and also with power and volume buttons
(The latter gives me an error and the comment : "Can't access to /system/CSC/XEU/System"
- Tried using Odin and re-flashing the Pit file with re-partition checked
- Tried using Odin and re-flashing all the correct files to get back to stock
All to no avail.
Please, Please someone who has seen this problem and found a solution, follow up:
please don't recommend a solution which involves a reboot :IT DON'T WORK!!!!
Finally: probably a noob question: is it possible to apply USB debugging in adb to get some communication going?
FG
Hey everyone.
So I updated my Atrix 2 to the ICS leak earlier today, and can't for the life of me get it to show up in ADB.
What I've done:
1) Tried on Windows (7) and Mac (10.7) using the SDK and downloaded versions of ADB.
2) Installed different Moto drivers on the PC. Ones that I found via a Google search, and the ones on the phone when mounted.
3) Toggled USB Debugging on and off 100+ times, and checked through all the settings.
4) Tried different mount modes- MTP, PTP, and Mass Storage, all while toggling USB debugging.
5) Tried adb kill-server, adb start-server, adb devices, adb usb, adb wait-for-device way too many times.
6) Tried different USB ports and different cables on both computers
7) Tested my Galaxy Nexus (verizon) which was detected by ADB on both setups with no trouble
8) Booted into Fastboot and tried ADB, but no luck.
At this point I'm ready to smack my head against the wall. Why in the world won't the phone get detected by ADB?
Any advice or help is greatly appreciated!
On Mac try sudo adb whatever
Always with sudo
Sent from my MB865 using xda app-developers app
xxDriveNxx said:
Hey everyone.
So I updated my Atrix 2 to the ICS leak earlier today, and can't for the life of me get it to show up in ADB.
What I've done:
1) Tried on Windows (7) and Mac (10.7) using the SDK and downloaded versions of ADB.
2) Installed different Moto drivers on the PC. Ones that I found via a Google search, and the ones on the phone when mounted.
3) Toggled USB Debugging on and off 100+ times, and checked through all the settings.
4) Tried different mount modes- MTP, PTP, and Mass Storage, all while toggling USB debugging.
5) Tried adb kill-server, adb start-server, adb devices, adb usb, adb wait-for-device way too many times.
6) Tried different USB ports and different cables on both computers
7) Tested my Galaxy Nexus (verizon) which was detected by ADB on both setups with no trouble
8) Booted into Fastboot and tried ADB, but no luck.
At this point I'm ready to smack my head against the wall. Why in the world won't the phone get detected by ADB?
Any advice or help is greatly appreciated!
Click to expand...
Click to collapse
I had the same problem initially as well. I did some research and found a thread on the Moto support forum in which people with the official Razr ICS had the same problem. What finally fixed it for me was:
-Uninstall all drivers for your A2, reboot
-Install THESE drivers, reboot
-Factory reset (Settings->Privacy->Factory Reset, or something like that). Yes I know it's annoying but it's necessary.
-Once your phone reboots, just sign into google. Don't uninstall any apps or do anything like that. Don't enable USB debugging either.
-Connect for all 3 different connection modes. Wait for the drivers to download each time. If a driver fails to download, then uninstall it (not the MotoHelper), reboot your computer, enable the installation of unknown sources on your phone, then repeat this step.
-Once you have all those drivers installed, time to reinstall them with ADB! Enable USB debugging and repeat the previous step
-Once all your drivers are installed, reboot for good measure. But you should be good to do whatever you want now.
Hope this helps. I know it's a pretty roundabout way, but it works :\.
cogeary said:
I had the same problem initially as well. I did some research and found a thread on the Moto support forum in which people with the official Razr ICS had the same problem. What finally fixed it for me was:
-Uninstall all drivers for your A2, reboot
-Install THESE drivers, reboot
-Factory reset (Settings->Privacy->Factory Reset, or something like that). Yes I know it's annoying but it's necessary.
-Once your phone reboots, just sign into google. Don't uninstall any apps or do anything like that. Don't enable USB debugging either.
-Connect for all 3 different connection modes. Wait for the drivers to download each time. If a driver fails to download, then uninstall it (not the MotoHelper), reboot your computer, enable the installation of unknown sources on your phone, then repeat this step.
-Once you have all those drivers installed, time to reinstall them with ADB! Enable USB debugging and repeat the previous step
-Once all your drivers are installed, reboot for good measure. But you should be good to do whatever you want now.
Hope this helps. I know it's a pretty roundabout way, but it works :\.
Click to expand...
Click to collapse
I guess I'll have to give the factory wipe a shot tonight. I was really hoping it wouldn't come to that since I can't use Titanium Backup due to lack of root.
all i did was have my phone plugged in while i was installing the drivers. but i did have to download the ones from your post.
I followed the steps as above except the factory reset part (as that's a painful experience) but no joy. After ICS OTA upgrade, no adb for me. Looks like I'll bite the bullet and do a factory reset finally.
Before that I'll wait if anyone can post an easier workaround here. I have a 32-bit windows vista. (And a Ubuntu virtual machine on vmplayer)
ADDED Finally `Factory reset' had to be done and that did the trick. Without factory reset, the phone will not present itself as a ADB interface - hence ADB driver won't load - hence ADB will not detect it. So I don't know if all the driver uninstall/install/reboot in 3 modes ritual is necessary ... if you have all the drivers, just factory reset/wipe data and the phone shows up in adb.
kousik said:
I followed the steps as above except the factory reset part (as that's a painful experience) but no joy. After ICS OTA upgrade, no adb for me. Looks like I'll bite the bullet and do a factory reset finally.
Before that I'll wait if anyone can post an easier workaround here. I have a 32-bit windows vista. (And a Ubuntu virtual machine on vmplayer)
ADDED Finally `Factory reset' had to be done and that did the trick. Without factory reset, the phone will not present itself as a ADB interface - hence ADB driver won't load - hence ADB will not detect it. So I don't know if all the driver uninstall/install/reboot in 3 modes ritual is necessary ... if you have all the drivers, just factory reset/wipe data and the phone shows up in adb.
Click to expand...
Click to collapse
I had the same problem and did a factory reset yesterday. It worked fine, so I re-rooted.
But that was yesterday. Now today, adb will not connect again. Something more is going on here. I suspect it is related to the fact that I did the OTA update from ATT without first un-rooting or doing a factory reset. I also had added files to system memory (ringtones - which are still there).
EDIT: Sorry, I spoke too soon. One thing I hadn't done was to "Connect for all 3 different connection modes." I had only connected in Mass Storage and Media Device modes, so I connected in "Camera (PTP)" mode, allowed the drivers to install on my PC, and then adb started working again (in Camera or Media Device modes, but still not in Mass Storage Mode).
Bob G said:
I had the same problem and did a factory reset yesterday. It worked fine, so I re-rooted.
But that was yesterday. Now today, adb will not connect again. Something more is going on here. I suspect it is related to the fact that I did the OTA update from ATT without first un-rooting or doing a factory reset. I also had added files to system memory (ringtones - which are still there).
EDIT: Sorry, I spoke too soon. One thing I hadn't done was to "Connect for all 3 different connection modes." I had only connected in Mass Storage and Media Device modes, so I connected in "Camera (PTP)" mode, allowed the drivers to install on my PC, and then adb started working again (in Camera or Media Device modes, but still not in Mass Storage Mode).
Click to expand...
Click to collapse
FYI adb will not work in mass storage mode.adb needs the phone memory and other access which are not there when you connect your phone in mass storage where it acts merely as a card reader
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...
Just in case anyone else was on the fence about doing this: I had tried a million things (trying different computers, different USB cables, installing and uninstalling different drivers, editing driver inf files, editing adb_usb.ini, etc) for several days and nothing worked. I was skeptical about the factory reset helping, but now that I did it I can finally connect to my phone. Yay!
So I just successfully installed Lineage 14.1 on my Galaxy S6 (International), using TWRP, and the OS works wonders.
Additionally I wish to have root access over my phone, so through TWRP I installed this: https://forum.xda-developers.com/ga...at-supersu-t3570740/post71367695#post71367695
The installation of the above goes through fine and afterwards I can go to developer options and enable "ADB Only". My question is: Why can't I also pick "Storage"?
Screenshot of how my "Root access" tab looks, under "Developer options": https://i.imgur.com/NxYr2jD.png
I'm trying to install Xposed and it says I don't have sufficient root access, my guess is because I don't have the option to also gain root access over storage.
Any help is greatly appreciated!
Flash SU Addon
download.lineageos.org/extras
hi, my phone ulefone armor 6e, I cannot upload firmware because the computer cannot see the phone. I tried all methods on 3 different cables and 3 different computers, in normal mode and fastboot mode, the computer does not see the phone. I installed the drivers properly, but when I connect the phone to the computer, there is no reaction or movement in the device manager section. The interesting thing is that the fast charging feature is lost. It also charges slowly when I plug it into wireless charging.
So i m trying this way, wifi debug and root using adb. but attach files not here, what can i do? please help. I have to one way wifi adb, how can i make root the phone, or flash recovery?
Greetings.
I have a Samsung Galaxy Note 4 with a completely broken screen (no display, no touch response).
Android version is 4.2.2.
The phone is working, as pressing the power button lights up the bottom bar.
The phone is rooted, however, USB debugging is disabled. The phone is also pattern locked.
I am aiming to gain remote access to the phone through my PC, ideally mirroring the screen so I can manually backup everything from my phone. In the worst case, backup through ADB is also acceptable.
Initially, I attempted to mirror the screen using:
https://forum.xda-developers.com/showthread.php?t=2786395
However, it requires ADB, which in turn requires USB debugging to be enabled.
To enable USB debugging, I attempted to modify the build.prop through ADB shell in recovery mode:
https://forum.xda-developers.com/showthread.php?t=2335799
However, it is done so using custom recovery (TWRP) which I assume cannot be done in stock recovery (not confirmed, please respond if untrue).
I attempted to edit the build.prop manually:
https://forum.xda-developers.com/sprint-g4/themes-apps/tool-edit-build-prop-pc-t3312517
But It requires USB debugging to be enabled as well, and I assume it to be true for most such tools.
I also attempted to install a custom recovery (TWRP):
https://www.xda-developers.com/how-to-install-twrp/
However, out of the 3 installation methods listed, 2 require USB debugging and 1 requires application installation on the phone.
Using a USB OTG mouse to enable USB debugging would be difficult, since display is broken.
Since 4.2+ also shows a prompt to allow access to USB debugging to PCs, I assume I could use this:
https://forum.xda-developers.com/galaxy-s2/help/bypass-secure-usb-debugging-prompt-t2965462
However, I would need ADB first, which also comes back to USB debugging.
I would prefer not repairing the phone or getting a new screen, the phone is old, i'm trying to change phones.
Data in the phone must be preserved, as much as possible. I am willing to compromise, somewhat.
ADB seems powerful enough that I could achieve my goals if only I could access my phone through it.
Is it possible to enable USB debugging remotely through some other method to allow me to use ADB?
Is it possible to flash a custom rom with an edited build.prop without screen input and while preserving phone data?
Please suggest options.
Problem:
When I tried to turn on my Samsung week back, it got stuck at "SAMSUNG" logo, eventualy it always turn off itself after some time. I wasn't doing anything crucial at that time when it broke (no system update, no new app installed). I can't turn on my phone to get my internal data.
What I need
I have some important photos/notes in internal storage and I can't reach for them. I only need the internal data. I know that SAMSUNG stuck logo boot issue can be fixed by wipe data/factory reset, but I would lost all my important data.
What I tried:
Removed SD card
Removed SIM card
Removed battery for few days
Let battery drop to 0% and charged back to 100%
Wiped cache partition in system recovery
Installed newest Samsung USB driver (from official Samsung site), restarted PC
Installed Kies - after connecting Samsung to PC, showing only "connecting" and after time it fails
Downloaded ADB - via CMD (/w admin priv.) tried command "adb devices" - returns empty list
Downloaded Dr.Fone (device unsupported)
FonePaw for Android (device unsupported)
I know I can get internal data via ADB, but ADB can't recognise my device for some reason. I tried 2 different cables, different USB ports (USB 2.0 / USB 3.0) / (front / back USB ports).
Also in my Device Manager, my Samsung Phone shows under "Modem" category.
What's interesting - in Odin3 (v3.13) I can see my Samsung as 0:[COM13] always without problem in any port with any cable.
I tried command "adb devices" when my Phone was in "Download Mode", "Android system recovery <3e>". In both situations - always returned empty list. In that time I was watching device manager and Odin3 to see, if my phone was really connected to my PC (it was).
Any ideas how to get those data? Btw I am newbie, just started dealing with all those things today and may not understand things clearly. Much thanks for any guidance, tips or info!
Specs:
Device: Samsung Galaxy Core Prime (SM-G360F)
Fastboot: Doesn't exist on this device
Rooted? No (tried KNOX, it remained in system but is not rooted)
USB Debugging: Was ON before logo boot stuck (Can't tell 100% sure)