Database Users

I think I cooked my USB functionality.

Hey gang. Wondering if you can help me with a strange issue I've got. I can't seem to connect my phone to my computer via USB. Wondering if anyone could help determine if there's a possibility of repair or not.
==Possibly relevant info==
Samsung Vibrant
Android 2.2 Froyo
Kernel version: 2.6.32.9
Build number: FROYO.UVKB5
==End relevant info==
So, my USB is acting up. Has been for the last few months, where although it charges when I plug into a computer, it's not connecting to allow data transfer. I haven't been too terribly worried, this happened before then cured itself when I did a factory reset. The thing that usually triggered it was when I tried connecting to my linux box in media player mode. The phone would just kinda lock up, I'd have to restart it and then USB wouldn't connect. But after doing the factory reset it was fine the first time. THIS time however, since I'd just left it stock now I'm itching to flash a custom rom but even though I've wiped the whole stupid phone totally clean, it still won't connect. I'm trying to follow a method on an article on dkszone.net called "Bypass E - Signature Verification Fail Issue On Vibrant Android 2.2".
So it seems I need USB for the debug mode.
What I think my main problem is, and where I need some help, is that I had purchased a super cheapwad USB car charger off of amazon for like 35 cents. Every time I connected to it, my phone would ask me if I wanted to connect using kies, media player mode, or data storage mode. I thought it was annoying but didn't really think it would harm anything. But now that I'm thinking about it, it's probably been pumping 5v into each pin on the USB port, whereas the USB functionality uses probably 3.3v, and I'm afraid I cooked something.
The random part here though is that about 5% of the time it does (sortof) connect. It brings up the USB options when I want to connect, brings up the icon saying it's using debug mode, etc. But my machine just reports that it didn't recognize the USB device. So, I'm thinking it's on the fritz, but figured I'd check here to see if I could possibly find a ray of hope.

Scooterx3 said:
So it seems I need USB for the debug mode.
Click to expand...
Click to collapse
You can use ADB over tcpip. There's many a free widget to enable it on google play or Do it manually

Thanks for that, I had been wondering if there wasn't a way to do that over wifi. My issue is that sadly I haven't even rooted the phone. ADB over WiFi requires root, whether I do it manually or use one of those super sweet apps.

So anyways, guess what?
My brother in law has the same phone I do, and I grabbed his phone one day and plugged it into my computers and had the same problem as with my own, and I know he hadn't plugged into the same charger I had, hadn't tried the media mode on Linux like I had (which were what I thought were the big contributing factors). SO, I kept digging, found that I hadn't quite yet cleaned it properly. I'd tried my best to clean it but until I swabbed it well with some rubbing alcohol it wasn't as clean as it should've been.
Long story short, I'm backing everything up so I can start flashing roms.
Moral: just clean the dang thing really well

[Q] Connecting to PC with CM7 -- no communication

Hey y'all, appreciate the help in advance.
I have been running CM7 on an SD card for the Nook Color. I like it, and haven't had many problems at all. However, one thing that has been buggy is connecting to a PC.
At first, I could connect sometimes, and see both the internal device memory and the SD card. Then it seemed sort of hit and miss.
Now, I can't connect to my PC at all. I rebooted back into the stock Barnes and Noble system, but my PC won't recognize that either.
I tried a different PC, and two "drives" showed up, but when I tried to look at them, the computer asked me to insert a device. In other words, I still couldn't access either the SD or the emmc.
I see that in Cm7 I have some sort of "debug" or "USB" mode. But when I plug in, nothing happens on either the PC or the NC, whether it is in CM7 or the stock OS.
I can't find where to turn "debugging" on in CM7.
I can pull out the micro SD and the computer will read it -- but only the boot sector, not the part where I keep all my books.
Any help is DEEPLY appreciated. Thanks.
Also (unrelated) does anyone know if ICS CM9 has netflix working yet?
THANKS,
RevTom

RevTom said:
Hey y'all, appreciate the help in advance.
I have been running CM7 on an SD card for the Nook Color. I like it, and haven't had many problems at all. However, one thing that has been buggy is connecting to a PC.
At first, I could connect sometimes, and see both the internal device memory and the SD card. Then it seemed sort of hit and miss.
Now, I can't connect to my PC at all. I rebooted back into the stock Barnes and Noble system, but my PC won't recognize that either.
I tried a different PC, and two "drives" showed up, but when I tried to look at them, the computer asked me to insert a device. In other words, I still couldn't access either the SD or the emmc.
I see that in Cm7 I have some sort of "debug" or "USB" mode. But when I plug in, nothing happens on either the PC or the NC, whether it is in CM7 or the stock OS.
I can't find where to turn "debugging" on in CM7.
I can pull out the micro SD and the computer will read it -- but only the boot sector, not the part where I keep all my books.
Any help is DEEPLY appreciated. Thanks.
Also (unrelated) does anyone know if ICS CM9 has netflix working yet?
THANKS,
RevTom
Click to expand...
Click to collapse
USB debugging is under settings, applications, development, Android debugging (or USB debugging under older roms). To turn on USB mass storage, after plugging in, swipe up notification area and choose to turn on storage. It is not automatic on cm7 like it was on stock.
No, Netflix still not working on CM9.

Hmmm. I had it on already, but no notification pops up when I plug into the computer via usb. I also have the "debugging notify" option selected. I did think I had it on, since it *used* to work.
ON the PC I get a "USB device not recognized" message. ON the NC itself, I get no message at all. It behaves as if it is not plugged in -- no notifications, nada.
Tried plugging into my wife's mac also, to no effect.
When I go back to Nook Stock OS, I no longer get the little black box that tells me I'm in usb connect mode. In the stock OS, it also behaves as if I'm not even plugged in, and I get the exact same message from the PC.
Could it possibly be that my cord has gone bad? I've done a little research, and I know some stock Nook users have had trouble with cords. Mine is almost two years old, but I haven't abused it. It still seems to work fine for charging.
Very frustrating....

RevTom said:
Could it possibly be that my cord has gone bad? I've done a little research, and I know some stock Nook users have had trouble with cords. Mine is almost two years old, but I haven't abused it. It still seems to work fine for charging.
Very frustrating....
Click to expand...
Click to collapse
It could be, but the fact that your nook shows USB debugging notification makes me wonder. But the fact that you are having trouble with both roms suggests that it is the cable.

To clarify: debugging, and debugging notification are ON, but when I plug in, there is NO notification.
However, like you, the fact that the stock ROM won't connect either makes me wonder.
An SD card root like I've done wouldn't mess with the stock ROM on the emmc, would it? Would it change the hardware or firmware to cause this problem?
'Preciate your time!

RevTom said:
To clarify: debugging, and debugging notification are ON, but when I plug in, there is NO notification.
However, like you, the fact that the stock ROM won't connect either makes me wonder.
An SD card root like I've done wouldn't mess with the stock ROM on the emmc, would it? Would it change the hardware or firmware to cause this problem?
'Preciate your time!
Click to expand...
Click to collapse
No, it does nothing to stock. You have a bad cable. The 'data' lines are broken somewhere along the cable or fittings. You can still charge with it because the power and ground lines are intact.
Edit: If you don't want to spend a lot of money getting a new nook cable, you can use your defective cable for charging and a standard micro USB cable for data transfer. Those work fine for hooking to PC as long as you don't try to charge with them.

Thanks,
I took it to a B&N store. I removed the SD card because I felt like a boot legger -- but anyway, they tried a new cable and it worked with Stock, so it WAS the cable.
Thanks!

You may get ADB and/or Storage working if you (re)install the drivers:
scour through Device Manager:
View menu... check show hidden devices
Look for any of the following sections and remove tem:
"Android Phone"
"Android ADB Interface"
"Android Composite ADB Interface"
"Android Bootloader Interface"
Additionally... in USB controllers... you want to check each device listed ... (Properties / Details / Hardware IDs) and remove any that begin with any of the followng:
USB\VID_0451
USB\VID_18D1
USB\VID_2080
USB\VID_22B8
USB\VID_0BB4
USB\VID_0BDA
Then re-install the drivers.

Thanks Dizzy. It was just the cord. I reloaded CM7 (i.e. put the sd card back in) and all my computers recognize it again, and I get the USB/debug notification on the NC again. As computerist diagnosed, I must have broken the internal data carrying cables without hurting the power connections. I did some research and a LOT of people have had issues with NC cables. Mine lasted 18 months, and I did not abuse it, so it isn't a great system. Hopefully this next one will last longer.

RevTom said:
Thanks Dizzy. It was just the cord. I reloaded CM7 (i.e. put the sd card back in) and all my computers recognize it again, and I get the USB/debug notification on the NC again. As computerist diagnosed, I must have broken the internal data carrying cables without hurting the power connections. I did some research and a LOT of people have had issues with NC cables. Mine lasted 18 months, and I did not abuse it, so it isn't a great system. Hopefully this next one will last longer.
Click to expand...
Click to collapse
I had seen your post about it being your cable... but thought others might benefit from my suggestions... as well as yourself... IF you still had ADB issues.

Windows 7 will not detect device

When I plug my wife's phone in, most of the time it does not even recognize that anything is plugged in at all, but the phone charges. Sometimes in device manager the phone comes up with a yellow exclamation point and the error
Windows has stopped this device because it has reported problems. (Code 43)
I installed the Android SDK and USB driver.
I installed the Samsung Driver from the site.
I thought possibly it was a software issue, so I was going to try to set the phone to factory settings. When I go into recovery, there is an Android logo with a red exclamation point, then eventually it boots back into Android with no change.
I manually added the driver into android_winusb.inf as I saw on another post here, but no matter what it is not picking it up.
I want to just be able to connect so I can root the phone and put a ROM on it. The phone is pretty hosed and slow. Any suggestions?

I had this at one point. It was the device, I had to get a replacement.
Sent from my SCH-I815 using Tapatalk 2

esoh said:
I had this at one point. It was the device, I had to get a replacement.
Sent from my SCH-I815 using Tapatalk 2
Click to expand...
Click to collapse
Well I do have insurance on it, and I agree that is the easy way, but I really don't think the hardware is broken.
I mean it charges, so the USB port works. I think if I was able to reload Android from scratch onto it, it would work. However, every solution I see requires rooting and you can't root without USB. It is a frustrating catch 22. Any other possible solutions? If not, I guess we are screwed.
The most frustrating part is factory reset not working.

I am currently having similar problems like you, I have one USB port from memory card reader and on that port phone isn't even charging but a flash drive works without problems. On other ports (back of case and front) there is charging but computer can't recognize the device. Try uninstalling all phone related drivers or cleaning them with some sort of driver cleaner. Then reinstall driver, or let Windows update it automatically. Mine worked for a while, and in device manager it was recognized as Acer ADB.
EDIT: Hi, just to report reason of my problems, my USB cables started failing for no apparent reason, my original Samsung USB cable and one other no name have both failed. I'm currently using my old LG USB cable, wrapped up in insulating tape, but everything is working good. So try some other micro USB cable, it maybe the source of your problems.

[Q] Of TF101 and Possums

I have a TF101 that's seemingly dead after being dropped. Currently, it does not power on. When plugged in with the ac charger, it shows no sign of charging, i.e., no light of any kind - amber, green or otherwise. I assume the mainboard has gone south.
When I connect it to my laptop, however, Windows 7 gives a chime and recognizes it as an MTP device, and even lists it as a TF101 in device manager. Linux also acknowledges that much. I can pretty much browse and access the content of the internal SD card like an external HD. Holding the power button long enough will unmount the device in either OS, which suggests that the device has turned itself off, and thus still responding to physical commands, or functioning on some level.
So it appears dead but not really. Being totally unfamiliar with this model, I'm not sure what possibilities the current state of affairs might indicate insofar as the device's vitality. Any input as to what this means is greatly appreciated.
If is it determined that the mainboard is done for, can anyone point me to a source for a replacement? If this kind of info solicitation is proscribed by regulation, my apology. Thank you.

My guess is, if the board was dead, you wouldn't be able to mount the device at all. It would suggest that it's actually alive and well, but the graphic/monitor part is dead, so you have no display at all. Mine also shows no signs of life (assuming I don't check the display) while it's charging and not on the dock. Only the dock has charging status lights as far as I can tell.
Sadly I can't help you further than that. I know they sell replacement parts on ebay and such, but I never even opened mine up, so I have no idea how easy it would be to replace any part. I know there's repair videos on youtube for the tf101, it might give you a clue if you open it up and run some tests.
Also check this out.

Lethe6 said:
My guess is, if the board was dead, you wouldn't be able to mount the device at all. It would suggest that it's actually alive and well, but the graphic/monitor part is dead, so you have no display at all. Mine also shows no signs of life (assuming I don't check the display) while it's charging and not on the dock. Only the dock has charging status lights as far as I can tell.
Sadly I can't help you further than that. I know they sell replacement parts on ebay and such, but I never even opened mine up, so I have no idea how easy it would be to replace any part. I know there's repair videos on youtube for the tf101, it might give you a clue if you open it up and run some tests.
Also check this out.
Click to expand...
Click to collapse
On second thought, I'm not too keen on replacing the MB just yet. Cracking the thing open is no big deal. I am dexterous enough. However, I am more intrigued by what is possibly going on.
If you guessed right, and transferring PC knowledge to this, the board would have a video chip integrated, with the other part consisting of an inverter and the LCD. If the integrated video circuit is dead, then connecting the device via HDMI to a TV would show nothing. If the device shows up, for instance, it's just the display part from the inverter on and so forth.
But I'm hesitant to go down that route. If it's the video part, then I should be able to do everything else like putting it in APX Mode, or flashing as with a normal device. Unfortunately, my computer never registered such activities; the tablet does not respond beyond the symptoms I described above.
As a matter of fact, I'd entertain any mad proposal on what should be tried on the thing at this point, just for the fun of it. I stand to lose little. So you can use your imagination and shoot some crazy ideas my way, and we'll see what.

So you tried with HDMI and it didn't work? You're right about APX though unless you're missing the drivers.. so maybe there really is some damage to the board. Sadly I don't have any crazy/mad suggestions at this point

My normal approach to possums (and the only legal thing I can do with them once captured) is to kill them or get someone else to kill them for me. :good:
As for your TF101, I seem to remember reading on another forum that when these devices are dropped and show the symptoms you describe, it can be caused by a ribbon cable that connects the display to the motherboard being jolted loose. It might be worth opening it up and check both ends of the appropriate cable for secure fit.

Mike_NZ said:
My normal approach to possums (and the only legal thing I can do with them once captured) is to kill them or get someone else to kill them for me. :good:
As for your TF101, I seem to remember reading on another forum that when these devices are dropped and show the symptoms you describe, it can be caused by a ribbon cable that connects the display to the motherboard being jolted loose. It might be worth opening it up and check both ends of the appropriate cable for secure fit.
Click to expand...
Click to collapse
Hey I totally agree that killing it may be the only option right now. And I don't mind that, just that I'd prefer the scalpel to the cleaver, and doing it in such a way that I would learn something about it that may be of benefit to me and incidentally, to others. I did open the thing, and you're again right, people have run into this problem of the LCD cable being jarred loose on impact from Asia to the Western Hemisphere to Eastern Europe. But it's not that, as I did unseat and reseat the cable on both ends, for naught.
As to the APX drivers, I did try both Easy Flasher and PERI 0.4. They act as if they finish the job. However, the tablet remains consistently inert. Lethe6, am I missing something here? How do you tell if the APX drivers are missing? Normally Windows would show the USB device as in APX mode right? Mine did not do that. When I tried to update the driver in Device Manager, Windows refused to do it claiming it was not necessary. Is there a way to force-install the drivers just to see?
Oh well, I'd just let the issue hang at this point and see what else comes this way.

Yeah if you connect your device in APX mode it should pop up in the device manager, just right-click uninstall then re-install the drivers. I don't remember what's the exact device name but iirc it's something generic. Sorry I can't check I'm on a Mac at work and my TF101 is at home.
What about HDMI? Did you ever get a signal through there? Tried having it connected when assuming to do a full boot?

Lethe6 said:
Yeah if you connect your device in APX mode it should pop up in the device manager, just right-click uninstall then re-install the drivers. I don't remember what's the exact device name but iirc it's something generic. Sorry I can't check I'm on a Mac at work and my TF101 is at home.
What about HDMI? Did you ever get a signal through there? Tried having it connected when assuming to do a full boot?
Click to expand...
Click to collapse
I never had the chance to try the HDMI output. Still waiting for the adapter to arrive. Ebay can be a pain during holiday season. But I'd sure to report the result. When I plugged the thing in, Win recognized it as an MTP device and proceeded to install drivers automatically. After which it showed in Device Manager as TF-101. So apparently the drivers are correct, though they dated back to 2006!!?? However, with other devices like the Acer A500, the USB device symbol normally would appear at the right bottom bar with the designation "APX device." With this thing, nothing - not even the icon. What's your thought on this?

I don't have any other devices that I can boot into APX (HTC won't tell anyone and my other tablet is a craplet, have to ADB on the live FS, which is awesome lol) so I can't compare here, but have you tried these drivers for APX? It's been a while but I seem to remember needing special drivers for APX. The device had a weird name.. like a bunch of numbers and letters... haven't used it since easyflasher though.
When I plug it in APX the device is called "NVIDIA USB Boot-recovery driver for mobile devices" and it's dated 1/31/2011.
When I plug it in Rogue Recovery the device is called "Asus Android MTP Device" dated 7/17/2012.
When I plug it in booted to 4.0.3 the device is called "Transformer TF101" dated 7/17/2012.
So I'm guessing yours never enters APX or has the wrong drivers? Maybe try installing the ASUS Sync software? Not sure but it may bring newer drivers...
I assume you're doing all this undocked as well?

SM-G900V - Broken screen. MHL/Mouse/Keyboard(?) possible all at once? [SOLVED]

Phone fell out of my pocket and got run over. Screen is completely black and the digitizer is done as well. If I connect it to my PC, it comes right up, but I have no way to enable USB file transfer mode so I can't "see" the SD card or internal memory. I tried to use [email protected] with Android Control, but it appears USB Debugging is turned off on the phone as ADB tells me the device is "unauthorized" and [email protected] gives me a "Rejected" status when it connects with the phone. (Yes, I did remove the ADB keys from my PC's ./user/.android folder and tried again)
Recovery is stock so no ADB access to open a shell and tweak anything. I haven't run across an ADB enabled recovery that I can install on this unlocked bootloader. (I can get into download mode and Odin recognizes the phone.) so I thought I'd try the "simple" route.
I bought an MHL adapter and an OTG cable thinking I could use a spare monitor and a mouse to turn on USB debugging or, at a minimum, turn on USB file transfer so I can get my data off the phone. I connected everything up and I can see the display, but mouse movement isn't being passed through the MHL cable assembly. If I plug the OTG cable directly into the phone, the phone does react to mouse movement and clicks and I can get lucky and launch apps, but I can't see WTH I'm doing. The odds of me turning on USB debugging like this are slim.
Anyone know of an MHL adapter that will allow "piggybacking" a USB mouse or an ADB enabled recovery I can flash to the phone? Maybe some uber-secret method to turn on USB debugging without access via ADB?

(Skiddz) said:
Phone fell out of my pocket and got run over. Screen is completely black and the digitizer is done as well...
Click to expand...
Click to collapse
I don't have this device but, I believe that one or both of the following threads may be helpful for what you need and don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=2786395
https://forum.xda-developers.com/showthread.php?t=3607259
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Ibuprophen said:
I don't have this device but, I believe that one or both of the following threads may be helpful for what you need and don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=2786395
Click to expand...
Click to collapse
Yep, have all this working. Replacement phone works so my config is correct. The issue is USB debugging got turned off somehow. If I can get in via ADB, I can tweak the files I need to turn it back on. Or, I can find a MHL/OTG combo that works and just turn it on via the screen. Hell, if I could view the ADB key on the phone, I'd modify that file on my PC and it'd probably work.
https://forum.xda-developers.com/showthread.php?t=3607259
Click to expand...
Click to collapse
Read this one as well. I'm not sure what all gets nuked in the process nor have I researched ADB enabled ROMs. I have 2 files I *need* to get off the phone before I send it back. If I had local copies, I wouldn't sweat it and I'd boot into recovery and since I'm familiar with the order of the menus in there, I can probably do a factory restore. Unfortunately, the 2 files I need were updated/created while I was doing the errands that resulted in the broken screen.

(Skiddz) said:
Yep, have all this working...
Click to expand...
Click to collapse
If you are unable to obtain any member guidance, within any of those threads, the only other thread, that I can point you to, is the following Q&A thread that's specific for all S5 Variants.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Looks like it should be a cable with 11-pin connector.
Something like this: https://www.ebay.com/itm/252931732046

bbsc said:
Looks like it should be a cable with 11-pin connector.
Something like this: https://www.ebay.com/itm/252931732046
Click to expand...
Click to collapse
Yeah, I've seen a bunch of those, but have read several reviews that state it does not work with the S5. I wish I could find one locally just to try it out and if it doesn't work, I can return it without too much hassle.

Just spent almost an hour on the phone with Verizon and Samsung. The 2nd tier person at Verizon said that if the phone was still activated, they *might* be able to get in remotely and tweak the USB Debugging setting for me. I would have to acknowledge the request on the screen, but that may have been doable via blind mouse clicks after seeing where the dialogue was located on the display. Unfortunately, the phone was already deactivated and without a working digitizer, I would not have been able to temporarily reactivate it.
Samsung was slightly better than useless. I had to explain several times, to two different people, the specifics of my situation and they couldn't seem to grasp the idea that both the display and the digitizer were dead and all I was looking for was a way to get MHL and OTG working at the same time. That concept seemed completely foreign to them and they couldn't tell me if the dock they manufactured for the S5 would do what I wanted. The capper was the last person I spoke to all of a sudden said, "Thank you. Have a nice day." and hung up while I was asking a question.
I called Asurion again to see if I could send the replacement phone back (Because the sound quality is so bad it's almost useless. Even the Samsung Advanced Support guy said the quality on his end was crappy.) and just get this screen replaced. They told me "That service is not available in your area (I'm in a city of approximately 1.3 million - surely they'd have a vendor here?) and "we don't replace the digitizer, only the glass." When I asked, "How is that possible when the glass, the LCD and the digitizer are all one unit (At least I've not seen the separate components in my searches) that you can replace the glass?" The response was a seemingly scripted, "We don't replace the digitizer." When I asked if I could just send this replacement back and replace the screen myself, they said the phone would no longer be insured. Same as if I had a "professional" swap it out.
At this point, it appears I'm dead in the water. I'm still going to research the feasibility of cobbling my own cable(s) together before I have to return this phone. This seems so simple to solve, but it's proving to be an exercise in frustration.

Having a little success in "driving" the phone now with the use of an MHL adapter and some swapping of MHL and OTG cables and a keyboard. I've verified USB debugging *IS* enabled, turned it off, revoked previous privs, turned developer options off, rebooted the phone, turned developer options and USB debugging back on.
I installed the Samsung USB drivers on my notebook and installed Android Control and [email protected] and tried again. Still getting an unauthorized response from ADB with a request to check the screen for messages. Unfortunately, as soon as I unplug the USB cable from the phone to plug in the MHL adapter, any message that may have been there disappears. I did this same thing on my replacement phone and after a couple tries, I got the Authorization message and was able to get that one "talking" again.
At some point I had installed a screen mirroring app on the old phone and managed to get WiFi working with some blind mouse clicks and got the mirroring working with a keyboard plugged in. It's VERY slow, but I was able to turn on BlueTooth as well. I ran out of time for the trial version of the mirroring app and can't seem to make it work again so....
I'm off to buy a BT keyboard and mouse. The plan is to try and sideload Samsung Smart Switch, use the BT KB/Mouse to "drive" and the MHL adapter to "see" and transfer data that way. Alternately, if I can get the screen mirroring working with BT KB for control, I could, in theory, reauthorize the USB stuff.
Alternately, what's the trick to making ADB work via TCPIP? I've been reading a few threads about it and actually got a brief response (Still unauthorized) early this morning (0230-ish) but have been unable to repeat that. Trying with my new phone ADB tells me it can't "see" any devices and "unable to connect to :5555"
Found a thread on Stack Overflow that mentions adbd insecure needing to be disabled, but I have no idea where that might be done.

Continuing from other thread...
(Skiddz) said:
If I could get an ADB shell up, I can turn on USB debugging *and* copy my key to the phone, but I've got no ADB ability in recovery mode..
Click to expand...
Click to collapse
And here is a chicken and egg. For you need USB debugging activated in order to provide you with an ADB shell. At least as I understand it.
Smart Switch is already installed, but I can't access the confirmation dialogue(s). If I can get the thing talking to the PC, I'm golden. I can pull my data and then do a factory reset.
Click to expand...
Click to collapse
That's strange. I managed to get it working on my Core Prime with a dead screen. Well broken enough. With no OTG support. And I wasn't aware of any dialogue on screen. I loaded up Switch in Windows and it communicated with Switch on the mobile fine AFAICT.
I can the phone recognized by ODIN and wouldn't mind attempting to flash something if it'll help. At this point, I'm considering this pretty much a lost cause so if something gets jacked, I don't care.
Click to expand...
Click to collapse
If your phone has a supported custom recovery then you have a chance.
Was able to recover an ADB key file pair from Saturday afternoon's initial attempt to get in to the phone. Still no joy. However! I *was* able to drive through the settings menus with a keyboard. USB debugging IS on and I was able to revoke USB debugging Authorizations
Click to expand...
Click to collapse
This started off well but if your phone had a list of keys already, even if you didn't know it is, then revoking the keys pulls rug from under your feet. So to speak. However, if you can satisfy the dialogue to authorise a new computer, then that's no problem and your in!
Am I on the right track with revoking authorizations? Any way to make the phone think I've never "touched" it with ADB? Again, the new phone connected right up with no input required from me.
Click to expand...
Click to collapse
I wouldn't have done that given it freshens the slate. But if you wanted to clear it to a near untouched state that is the way to do it. Strange the new phone was easy that way. In that case it would be a good idea to clear it if the old one acts the same.
Here is my story about trying to get USB debugging working:
https://forum.xda-developers.com/ga...how-recover-data-core-prime-sm-g360g-t3681433
Here is a guide I wrote from my story detailing how I hacked my adb key in to authorise my computer for USB debugging:
https://forum.xda-developers.com/android/help/guide-modfying-cf-autoroot-kit-to-t3725596
Now this details what's involved but my phone was fully unsupported by everything but the CFAR kit. Which I needed to hack. You shouldn't need to go to such measures. Just need a recovery with ADB enabled.

Hypexed said:
Continuing from other thread...
And here is a chicken and egg. For you need USB debugging activated in order to provide you with an ADB shell. At least as I understand it.
Click to expand...
Click to collapse
USB debugging *is* on. I was able to verify that once I figured out how to drive "blind" with a keyboard. I was able to turn it off, turn off debugging options, reboot, turn debugging options back on, then turn on USB debugging.
That's strange. I managed to get it working on my Core Prime with a dead screen. Well broken enough. With no OTG support. And I wasn't aware of any dialogue on screen. I loaded up Switch in Windows and it communicated with Switch on the mobile fine AFAICT.
Click to expand...
Click to collapse
I'll have to try again but when I used Switch to move my wife's data from her Droid Mini to an S5, there was a confirmation dialogue on the Mini.
If your phone has a supported custom recovery then you have a chance.
Click to expand...
Click to collapse
G900V. Locked bootloader (Thanks Verizon) and I haven't found a custom recovery I can install without rooting.
This started off well but if your phone had a list of keys already, even if you didn't know it is, then revoking the keys pulls rug from under your feet. So to speak. However, if you can satisfy the dialogue to authorise a new computer, then that's no problem and your in!
Click to expand...
Click to collapse
I was getting the "unauthorized" status of the device via ADB and had no way to compare keys. I revoked keys so I had a known starting point. Yes, if I can get to the dialogue to confirm the access, I'm golden. Going to try the BT keyboard/Mouse and screen mirroring this evening when I'm done for the day. Even if I get Switch to start talking and get my data moved over, I'm going to figure out the ADB thing - it's become personal.

(Skiddz) said:
USB debugging *is* on. I was able to verify that once I figured out how to drive "blind" with a keyboard. I was able to turn it off, turn off debugging options, reboot, turn debugging options back on, then turn on USB debugging.
Click to expand...
Click to collapse
Then you're half way there. Almost living on a prayer. And if you can do the above it should be a cinch to get over the line and get that computer authorised.
I'll have to try again but when I used Switch to move my wife's data from her Droid Mini to an S5, there was a confirmation dialogue on the Mini.
Click to expand...
Click to collapse
It may work different from a non-Samsung phone. I used Switch on Windows to back up data from my Samsung phone. It was able to do so without intervention on the phone. Well I didn't see any prompt on the phone. Since my screen was blank.
G900V. Locked bootloader (Thanks Verizon) and I haven't found a custom recovery I can install without rooting.
Click to expand...
Click to collapse
Aha. Well hopefully you can get it going without need of that. In my case my under supported phone wasn't locked.
I was getting the "unauthorized" status of the device via ADB and had no way to compare keys. I revoked keys so I had a known starting point. Yes, if I can get to the dialogue to confirm the access, I'm golden. Going to try the BT keyboard/Mouse and screen mirroring this evening when I'm done for the day. Even if I get Switch to start talking and get my data moved over, I'm going to figure out the ADB thing - it's become personal.
Click to expand...
Click to collapse
Haha. Yes I know what you mean. You can see by the links I posted how personal I got.
I managed to CF-AutoRoot my phone before I got USB debugging even close to on. Of course I still couldn't do much with a broken rooted phone since all actions needed acknowledgement on screen. Later when I finally broke in and got the authorisation I still didn't have root access from an adb shell since that needed the screen working.
I had AirDroid installed. So once USB debugging was working I could do screen mirroring right away. That was a reward in itself. But it was the darnedest thing. The time I got it up and working suddenly the screen started responding to touch which didn't work before. I could brush my finger across the screen and hear the waters. So I quickly backed up my data. The next day, the screen stopped detecting my touch again. As well as AirDroid being unable control input. It's stuck in the corner and I can't use the mirroring to echo any touch to the phone. Most bizarre! I backuped my data just in time.
I used Helium to do a non root backup even though it was rooted. Worked well. Needed the mirror to see on screen.

I'm in! I was able to use my MHL adapter and a mouse via OTG to get the trial version of Stream Screen Mirror going. Once I got that going, I was able to pair a BT mouse/keyboard and use an MHL adapter to "see". Out of "spite", I fired up Android Control and authorized ADB access and voila! Remote screen and control. Pretty slow, but it works.
Sideloaded Switch via SMB and got it transferring data. It's grinding along now but will likely be another hour or so.
Thanks to everyone for the help.

That's good you got it going. Well done, I knew you would get there. Now if only there was a better solution than all this fiddling around.

Hypexed said:
That's good you got it going. Well done, I knew you would get there. Now if only there was a better solution than all this fiddling around.
Click to expand...
Click to collapse
No kidding... I can't imagine someone without any technical knowledge being able to move their data over in this type of situation. Oh well, it was a nice learning experience. I got a BT keyboard and Mouse for use with my Rapsberry Pi and now have a solution for the next time.
Actually, I think I'm going to root this thing and avoid all the hassle in case this happens again.

I agree with you there!