Completely broken screen - how to enable adb debugging? - Xiaomi Redmi Note 7 Questions & Answers

Hi and sorry if this is answered elsewhere. I have a Note 7 with a shattered and nonfunctional screen. There is no way to get any info from it, except for whether the backlight is on or off.
I want to get as much data off of it as possible before I go any further, and to do that I was going to run the "scrcpy" utility. However, this depends on adb debugging being enabled. I've tried to find info online on how to do this on this particular model, but info is scarce and the vast majority seem to be either for other models or assuming I have access to a screen of some kind. Which, I don't, which is the entire point.
Does anyone have an idea of how to pull this off? Unfortunately without the screen, I am very much operating blindly here.
Thanks.

Replace the display or navigate it blindly (if the touchscreen still works). Otherwise it's a little late for data backup...

Related

[q] getting past pattern protection screen

Hi,
During this week, I dropped my 1-year old Nexus 7 and cracked bottom left 1/3 of the screen. It looks as if the device is still functional, but I am not able to get past the pattern protection that I have used as a security feature. Is there a way to get beyond this screen to see if it still is a functional device and if so, then disable the pattern recognition. I am resigned to the fact that I may have to buy a new device, but I do not like to discard it without trying if I can get some additional service out of it somehow. By the way, it is an unlocked, but unrooted device.
Thank you for any help/suggestions.
Best Regards,
RaliR
the display is ON right?
RALIR said:
Hi,
During this week, I dropped my 1-year old Nexus 7 and cracked bottom left 1/3 of the screen. It looks as if the device is still functional, but I am not able to get past the pattern protection that I have used as a security feature. Is there a way to get beyond this screen to see if it still is a functional device and if so, then disable the pattern recognition. I am resigned to the fact that I may have to buy a new device, but I do not like to discard it without trying if I can get some additional service out of it somehow. By the way, it is an unlocked, but unrooted device.
Thank you for any help/suggestions.
Best Regards,
RaliR
Click to expand...
Click to collapse
The same happened to my Nexus. The device is good. Just get a replacement Screen+Digitizer (cost around 66$ with free shipping in ebay(tools free), let me know if you need the link). And you can fix it by yourself(I did) with the help of "How to replace glass in Nexus 7" video in youtube by Android Authority!
nijom said:
The same happened to my Nexus. The device is good. Just get a replacement Screen+Digitizer (cost around 66$ with free shipping in ebay(tools free), let me know if you need the link). And you can fix it by yourself(I did) with the help of "How to replace glass in Nexus 7" video in youtube by Android Authority!
Click to expand...
Click to collapse
Hi Nijom,
Thank you for your reply. Before I spend money to get a replacement glass(& digitizer), I want to see if there is a way to get past the Pattern Protection screen to make sure that my device is fully functional. I do not want to spend $66, replace the glass and then find that the device is not working. Any thoughts, Anyone?
Thank you,
Regards,
RaliR
The only way to do it is to erase the file that contains the password. You won't be able to do this from a booted device, at least assuming you are running 4.2+ and USB debugging is off/your computer isn't authenticated with the device. You will need to flash a custom recovery if you do not have one already. Once you boot into recovery, you have two options. You can either use the file manager built into TWRP recovery, or you can use ADB. You need to delete the file /data/system/gesture.key. Use the file manager to delete it, or run from your computer:
Code:
adb shell rm /data/system/gesture.key
This will only work if your screen is still partially functional; it doesn't disable the passcode lock, but it erases your saved pattern so that any pattern will unlock the device. If you are able to touch any of the points on the pattern lock, it will unlock the device. Once unlocked, you can remove the lock screen, assuming your touch screen is functional.
And yes, this is an inherent security risk with unlocked devices.

[Q] Cracked Screen, backup/restore options..Pro's needed.

Hey guys,
I cracked my s5 screen and need to backup everything and restore it onto another s5.
Phone info: NO ROOT, Pattern-locked screen.
I tried a lot (I mean A LOT) of different methods, and if I would be able to successfully backup/restore with a few easy steps, I still would like to have the following questions/methods answered.
They are as follows:
1. USB debugging mode is enabled, so i can use adb commands, which I have already. I have done the pull /sdcard/ command. I was able to get pictures, videos, downloads, etc. But I dont think it backed up any apk's. Any idea as to which pull command can fully backup the phone including apps, and if possible also text messages??
2. I have purchased a usb OTG (On-the-go) which allows me to connect my mouse to my phone. I cannot see the screen so i tried to randomly swipe my lock pattern, but i wasn't able to. So, what I thought of was to connect my phone to my mac, and use android screencast (which shows my phones screen on my mac monitor) while also using my mouse to control my phone. However, the USB OTG only has 1 usb slot, so I can either connect my mouse, or take out the usb otg adapter and connect the micro usb directly to my phone that connects to my laptop.
So the question is. Can I connect two micro-usb's into my phone simultaneously? One would be the usb-otg adapter( to connect my mouse into) and the other would be the micro-usb that would connect to my mac(in order to see the screen.) This way I would be able to control my phone with a mouse, and see my screen on my laptop monitor. I use mac btw.
3. If I can't connect two micro-usb's into my s5, can I enable bluetooth to connect to a wireless mouse via abd commands or any other method?
3. Can I root my cracked-screen phone? And without losing any data?
4. Is there a way to disable the pattern-lock on my phone using adb commands? I have read solutions to this for older galaxy models, but they didn't work for my phone.
Yes, these are tough questions, and I hope some of you have the proper knowledge and patience to answer them.
Please be specific, and note the Question # you are providing an answer to.
Thanks
The Puma
Your post doesn't quite make sense, which I think is because you're leaving something critical out or making an assumption that you aren't telling us about. e.g. you cracked your screen.. okay. I'm sure that is frustrating but how does it cause you any significant difficulty in using your phone?
There is something that you're not telling us. We can't see your phone or tell what you are thinking.. did you forget to mention that you broke your digitizer? Or perhaps broke the LCD, so that your screen doesn't power up? Or something else?
Tell us what the actual problem is, because a cracked screen per se would not impair normal phone use. If we don't know what is going on, it's hard to offer good advice on how to proceed.
If you do a search, you can find posts describing how to bypass a pattern lock if USB debugging is enabled. If you can't view your screen directly for some reason, there are various ways to root or even easier, assuming an unlocked bootloader, simply install a custom recovery.. which is only a few clicks. Then boot to recovery mode, allowing you to run a root ADB session and use the dd command to backup your partitions.
.
..
fffft said:
Your post doesn't quite make sense, which I think is because you're leaving something critical out or making an assumption that you aren't telling us about. e.g. you cracked your screen.. okay. I'm sure that is frustrating but how does it cause you any significant difficulty in using your phone?
There is something that you're not telling us. We can't see your phone or tell what you are thinking.. did you forget to mention that you broke your digitizer? Or perhaps broke the LCD, so that your screen doesn't power up? Or something else?
Tell us what the actual problem is, because a cracked screen per se would not impair normal phone use. If we don't know what is going on, it's hard to offer good advice on how to proceed.
If you do a search, you can find posts describing how to bypass a pattern lock if USB debugging is enabled. If you can't view your screen directly for some reason, there are various ways to root or even easier, assuming an unlocked bootloader, simply install a custom recovery.. which is only a few clicks. Then boot to recovery mode, allowing you to run a root ADB session and use the dd command to backup your partitions.
.
Click to expand...
Click to collapse
Yes, the digitizer is cracked as well, and my screen is black. That is the reason I am using Screencast to view my screen on my laptop monitor.
puma224 said:
Yes, the digitizer is cracked as well, and my screen is black. That is the reason I am using Screencast to view my screen on my laptop monitor.
Click to expand...
Click to collapse
I am guessing you can see the screen on your PC. Well, you can open up Google Play on your PC browser, search for the app "Helium backup" and let it install on your phone. That app can backup all your app data and other stuff as well I think, but I know for sure that it can backup the app data, which I assume is what you desire. The data can even be backed up to a Cloud. From there it should be easy to restore on your new S5. Also, the messages etc. are backed up on your Samsung account, that shouldn't be a problem as well.

[Q] Enable usb debugging on smashed screen S4

TL;DR Screen broken, usb debugging not enabled. How can I enable it to access /data and remote control screen via pc
So, I've been foolish. In a fit of Geocaching (don't judge me!) I dropped my beloved S4 and smashed the screen and digitiser - it's black and won't work. It will, however, still receive touch commands as I can turn vibrate on/off in the quick settings as I know where it is, other than that I'm buggered.
Stock rom 5.0.1, tiny font size, dev mode enabled, but I cannot work out where to press to get adb debugging on.
I really want to get Android Commander working or at least a screen mirroring app for controlling it via my laptop to get some stuff off it from /data but I can't adb as usb debugging isn't enabled.
I'm rooted, I've twrp 2.8.4.0 in recovery which I think I can get in to (again, I'm doing this blind) - is there a way I can enable usb debugging via a Windows app/recovery/if someone set in tiny font display could post exact screenshots so I could try it blind by scrolling and approximating presses for usb debugging and if needed any confirmation dialogue boxes. I'm running Nova launcher which might be easier to open settings?
If anyone could help I'd most appreciate it!
Edit: Q&A move please if a mod sees this.
I've a usb keyboard if that's able to open settings and move/select through them, can anyone confirm this works?
there's a thread in the android section that lets you control a phone with a broken screen via your pc (has a gui now too apparently)
have a look there
(btw, this belongs in q&a not general)
DSA said:
there's a thread in the android section that lets you control a phone with a broken screen via your pc (has a gui now too apparently)
have a look there
(btw, this belongs in q&a not general)
Click to expand...
Click to collapse
Thanks- I've searched but all require usb debugging enabled, which I'm trying to do in the first place...
edit
Here's the problem. Android 4.3 and later require authentication for USB Debugging to become active. In other words, when you enable USB Debugging you get a prompt specifically asking if you want the device to talk to the PC. While you could blindly hit the right button to activate it, you can't activate it unless you can somehow navigate to Developer Options. A bit of a Catch-22, as this is one of those instances where a security feature comes back to bite you in the a**.
As expensive as it is, you may want to invest in a new screen.
Strephon Alkhalikoi said:
Here's the problem. Android 4.3 and later require authentication for USB Debugging to become active. In other words, when you enable USB Debugging you get a prompt specifically asking if you want the device to talk to the PC. While you could blindly hit the right button to activate it, you can't activate it unless you can somehow navigate to Developer Options. A bit of a Catch-22, as this is one of those instances where a security feature comes back to bite you in the a**.
As expensive as it is, you may want to invest in a new screen.
Click to expand...
Click to collapse
Thanks, it's as I thought. Not the screen doesn't respond so I've decided as it's fairly battered anyway I've taken the plunge and bought a new one from eBay again - and I'll be getting a tempered glass screen for it, too! I tried adb-enabling usb debugging via build.prop editing but now luck it seems - there must be a prompt I cannot see.
I'll re-flash the phone and eBay it for parts - less hassle than screwing up a replacement screen and I got a decent price for the new one.

Enabling USB Debugging with completely unuseable screen

I know there's a lot of threads on this, and some guides, but they're all so vague. It seems like a lot of people are making suggestions based on assumptions that the people having the problem have a slight idea of what to do.
I don't. At all. All I know is there's a program that lets you control your phone with your PC, but you have to do something that NORMAL people DO NOT think to do with their phone. (Enable USB Debugging.)
Now I'm stuck with an entirely, repeat, entirely non-functioning screen. As in, no display, no response to touch, nothing.
What I want to get off the phone, as far as I know, can't be done just by copying and pasting the files to my computer.
I have some game save files on there that I didn't upload to Cloud, so I can't exactly get them back.
It's really irritating to start games over constantly, and I had a fair bit of progress on a number of them, so I really DON'T want to start over again.
If someone could PLEASE help me with this, properly, with more detailed instructions, I would be grateful. I already downloaded [email protected], but again, since I don't have USB Debugging enabled, and NO WAY to do so by means of the phone, it's kind of useless.
I had a similair situation myself and I just gave up.
You need to enable it in the build.prop and you need to disable rsa signature.
The only way you can do that is by flashing it trough a custom recovery. But you cannot select the file. Thus unless you can figure out a way to flash that trough Odin.....
See, now if it's possible, it would be great to get a walkthrough of how to do so.
Either that, or just be told how to grab the save files of my mobile games so I don't have to start over again.

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!

Categories

Resources