Database Users

[Q] Screen broken on Droid 2 Global on Froyo USB Debugging off

Greetz
My sister had a Droid 2 Global with Verizon and then one day she accidentially got some coffee spilled over it... it was never soaked, but it was affected enough to render the phone useless... and ever since she got a replacement phone I have been trying to figure out how to make use of this puppy.
It is running Froyo and I know that USB Debugging is NOT enabled.... it is off. So I cant do anything with this without usb debugging.
The video above - thats the extent of the screen turning on. I cant give up on this thing -- it turns on, it vibrates, and the green LED light flashes with a message. I just cant see the runtime. DroidExplorer, AndroidCommander, QDBADB are not picking it up and forget about adb commands because my sis is not the kind to root or mess with her phone so I know she did not have USB debugging enabled.
I have followed the guides here and there... http://droid.koumakan.jp/wiki/Android_Recovery and nothings happenin.. just the screen light comes on.
I want to try flashing SBF or flashing recovery or FORCING usb debugging on.... if I can at least root this thing, it is going to be useful with or without a screen. Does anyone have ideas for me to try? Or is my only option to mess with hardware? Its literally brand new.
So a long post short... how do I force usb debugging? there MUST be a way...
short and fugly video here to basically show the screen light coming on.
http://youtu.be/gz2FudevWCw
Heres a link to force USB debugging -- http://forum.xda-developers.com/showthread.php?t=1146358 suggested to obtain a backup and flash it or restore it with USB enabled... however need root to do that...
Then I am wondering about somehow getting build prop and changing it to "persist.service.usb.setting=1" -- again you need root... right?

All you need to do to SBF is to get into bootloader, which shouldn't be an issue. Odds are the digitizer just needs to be replaced if you'd like a functional device.

no kiddin? Thanks for giving me hope! Everyone else is telling me to throw it off a cliff, but I cant do it yet. Ok... I am going to learn about SBF now... (my first dabble with a moto device) thanks mate!

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] Formated Nexus 7 2012, now what?

Hello all!
I'm just guna say, this might get long winded so, TLDR, Nexus 7 has no OS, I can get into the boot loader, the only thing I can actually do is get into TWRP v2.8.01, computer doesn't recognize it, can't get it to even see a flash drive that I've formatted to Fat32, now what?
For those who want some background. I got my N7 refurbished from ebay, if that matters at all. First thing I did was update it to Kitkat and root it. Installed some apps and was happy with it for a few months. About a month or so ago it stopped connecting to the Google Play Store. I wasn't bothered by it too much. But as time goes on, I find new apps and would like to use them. But obviously can not.
So, just to be safe, I wrote down all the apps I still had on it just in case they didn't want to load back up. Did a factory reset, still couldn't connect. Looked online and cleared caches and stopped services. Still didn't work. When I went onto the GPS, heh, on my computer it said that I had no devices so that was a clue of some sort. I could still go onto Youtube and log in and use it just fine. Just nothing in the store. So I decided to try something else.
What that was was to clear all my data with TWRP. Went to put in my email and password, couldn't connect, tried another wifi connection, still no go. I was able to use it, but the Play Store still didn't want to play nice. So in a bit of, "rage" we'll call it. I formatted it and now I'm where I am now. With a tablet that won't boot, just sit at the Google logo for up to 5 mins, as long as I've let it sit there for anyway. I have downloaded the Nexus Root Kit and tried to use that, but my computer won't even see my N7 now. In the bootloader or TWRP. So I can't even get anything onto it now.
So, what now? Do I have a bricked tablet that won't do anything or is there something an Android Guru out there can help me with? I'd like to keep it. I mainly used it to read and for various videos.
I have posted on forums.androidcentral but after a week and almost 300 views, no one has made any comments. I'm sorry for my ignorance if I'm missing something.
Thanks! I shall be hoping for good news.

So, does ADB recognize your tablet or not when you type "fastboot devices"?

I take it you mean shift+right clicking in the platform tools folder, open command window here, and typing that into the command prompt? If so, then no, it doesn't show up.

Waslow said:
I take it you mean shift+right clicking in the platform tools folder, open command window here, and typing that into the command prompt? If so, then no, it doesn't show up.
Click to expand...
Click to collapse
Can you go into the bootloader? Did you install the right drivers?

I can get into the boot loader just fine. Recovery sends me to TWRP 2.8.01. I've got the drivers from the Android SDK Manager, Rev. 11 apparently. Would that be any different from the standard drivers that get installed when you hook up the N7? Well, when it works?

Waslow said:
I can get into the boot loader just fine. Recovery sends me to TWRP 2.8.01. I've got the drivers from the Android SDK Manager, Rev. 11 apparently. Would that be any different from the standard drivers that get installed when you hook up the N7? Well, when it works?
Click to expand...
Click to collapse
That is correct. Use this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
And if doesn't work check in device manager.
If it works flash the latest factory image and then you will be good to go

I've already had that installed and set up and nothing pops up in the device manager. I've also tried all the usb ports on my computer to no avail.

Waslow said:
I've already had that installed and set up and nothing pops up in the device manager. I've also tried all the usb ports on my computer to no avail.
Click to expand...
Click to collapse
Then try the driver manual in nexus root toolkit

I can follow the instructions, but that doesn't resolve the fact that my computer can't see the Nexus .

go into device manager and delete every single entry that suggests anything to do with a phone, tablet, google device, nexus device, ETC. if you dont do that first, this will probably not work.
once you delete every single entry in there, go to the top command bar and somewhere in those menus is an option to show disconnected devices. delete everything again as above.
now, does your tablet still charge on the AC plugged into the wall? does it still charge when plugged into the computer usb? drivers are NOT required for usb to supply power. if so, the usb connector is probably OK. if not, your usb connector may be toast.
next, connect to the computer. does windows show any device connected? if not, try a different usb cable. report your findings back.

Sorry for the late reply.
There is nothing in the device manager related to my Nexus, which is odd, it had entries for flash drives, a camera, and my phone. All of which were in the disconnected devices. I got rid of just for the sake of it. Nexus charges just fine, either from the wall or any of my usb ports. If there is no way to make ANY computer see my Nexus, is it safe to say it's bricked?
I do have a cousin who's fluent in Linux if that means anything. I know that Android is a flavor of it. Might work better if both devices speak the same language. Grasping for straws I know.
Again, thanks for the help fwayfarer, GtrCraft, and Fobos531!

If I am reading right, you did NOT try a new USB CABLE yet, did you?
Try a known good USB cable, what I mean by that is try a cable you KNOW works for data transfer on another device and report back.
Connecting it to a Linux machine isn't going to make any difference in my opinion.

I have 2 cables and they transfer things just fine with my phone and my Kindle. I just downloaded everything off of both things, and transferred them back. No issue with the cables. I just popped open my Nexus and it looks like the usb connector and ribbon are fine. I did wiggle them a little but to no avail.

Pull the battery cable, smash the power button for a few minutes, reconnect and try again. It won't recognize a USB thumb drive in bootloader or recovery to my knowledge, BTW. I noticed you mentioned it not seeing one.

I unplugged the battery, hit the power switch for a while, plugged the battery back in, plugged the usb back in, nothing. Still nothing. I had read before that you can put the version of android you wanted on a flash drive. With an otg cable you could use that to update/install what you wanted.

You're probably right, I haven't tried using one in recovery for a long time. You didn't change the battery or anything recently did you?

Nope, haven't replaced anything in the Nexus. The only thing that I could think of that could be wrong is the usb connector. But for it to "fail" at the same time I formatted everything, too much of a coincidence.

Over a week bump

I ran into a similar problem about a year ago. Unless your tablet is connected to the computer you will not see it show up it the windows device manager. You should be able to connect your N7 to a work computer & it should go out for the drivers. If not, then you are Sol. You might have a blown main board.

The only thing my N7 does when I plug it in, is that it charges. That's the only thing I can get it to do. Well, this sucks. If I really have a bricked, or worse, tablet, it's still good for its screen and other bits.

Unlock phone without touchscreen

Ok, so it seems I have a problem.
Some time ago I have dropped my N4. Not the first time, bit this was the one that resulted in a broken screen. Touchscreen doesn't work in the bottom 1/3-1/2 of the screen preventing me from unlocking my phone. I've actually bought a N5X almost immediately (I was planning on the switch for some time, guess the decision was meade for me), but I'd still like to get some data off the old phone (not only data, I'll need to run some apps to export).
I guess my problem is twofold:
1. Unlock phone without a touchscreen (not sure if I remember my lock pattern, I've been using N5X with a new one for a while)
2. Run some apps etc, basically operate the phone without touchscreen.
My problems would have one easy solution - connecting a mouse to the phone - if only N4 had OTG.
I've tried getting on the phone via ADB, but I"m getting a message:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Could you point me in a right direction?
Thanks for the help
Rgds,
Michael
PS. As far as I remember I do have the USB Debugging enabled. ROM was the latest stock android (5.1.1, was it?)

testmail001 said:
Ok, so it seems I have a problem.
Some time ago I have dropped my N4. Not the first time, bit this was the one that resulted in a broken screen. Touchscreen doesn't work in the bottom 1/3-1/2 of the screen preventing me from unlocking my phone. I've actually bought a N5X almost immediately (I was planning on the switch for some time, guess the decision was meade for me), but I'd still like to get some data off the old phone (not only data, I'll need to run some apps to export).
I guess my problem is twofold:
1. Unlock phone without a touchscreen (not sure if I remember my lock pattern, I've been using N5X with a new one for a while)
2. Run some apps etc, basically operate the phone without touchscreen.
My problems would have one easy solution - connecting a mouse to the phone - if only N4 had OTG.
I've tried getting on the phone via ADB, but I"m getting a message:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Could you point me in a right direction?
Thanks for the help
Rgds,
Michael
PS. As far as I remember I do have the USB Debugging enabled. ROM was the latest stock android (5.1.1, was it?)
Click to expand...
Click to collapse
If your bootloader is unlocked, you should at least be able to access your data by flashing TWRP, and connecting to a computer from there. Unfortunately, I don't know how you can access the phone normally without adb working.
Sent from my Nexus 4 using XDA Labs

Hmm so basically I need to replace my screen to get to my data... It sucks to spend lots of money on the repair only to get data from 2 or 3 apps... But if there is no other way then I guess I have a decision to make.
Thanks for the reply, @elonus

Nexus 4 HAS otg if you flash a kernel that supports it and get a Y-shaped powered microUSB-female USB cable. I have one so I can confirm that it works.

Plug in a mouse?
Plug in a mouse? I think it would work...

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!