[Could a mod please move this post to the moto g4 plus section? I accidentally posted it here though I doubt it changes any of the solutions. Thanks anyway]
Hello, my phone recently fell screen down on the floor. The screen itself is fine but the digitizer has stopped working and I can't access my phone. I already ordered a replacement screen/digitizer assembly but I still need access to my phone in the meantime. I thought about using this screen mirroring program https://forum.xda-developers.com/showthread.php?t=2786395 but my phone is stock and non rooted (for once). I can't get my phone to show up in adb devices except in recovery sideload mode (stock recovery). It does show up in fastboot but I'm not trying to root and erase all my data, at least until I have access to my phone.
I've already been at it for two days so I'm pretty frustrated at seeing notifications on my phone and not being able to do anything.
Any help is appreciated
Related
Okay so after I was getting off work last night, I went to pull my keys out of my hoodie and my lanyard evidently caught the corner of my phone and it belly flopped straight onto the front screen. I've never broken a phone before so this is a pretty traumatic experience for me. But anyway I want to take it back to T-Mobile and get it replaced (it's insured) but it was rooted and ROM'd. Using the Nexus 4 Toolkit I was able to flash stock and unroot, but now I'm stuck on the setup screen with no way to get to the settings to re-enable ADB to do the OEM relock. The digitizer is completely screwed, It kinda worked for like 15 mins and then it started freaking out like someone was touching everywhere on the screen at the same time, after that finally stopped it became totally useless. The lcd is completely fine so I can still see my screen but it's essentially useless. If anyone could tell me if there's a way to remotely activate ADB or possibly some super easy way of relocking it that uses only buttons or something, that'd be awesome.
Just go to bootloader ( volume up + volume down + power)
Then type, " fastboot oem lock", without the quotes. Good luck
Then type, " fastboot oem lock"
Click to expand...
Click to collapse
I'm assuming you're meaning in cmd, so I tried that and I cant get my phone to show up as a fastboot device. And of course the list for adb devices is blank :/
RomminNudels said:
I'm assuming you're meaning in cmd, so I tried that and I cant get my phone to show up as a fastboot device. And of course the list for adb devices is blank :/
Click to expand...
Click to collapse
Install drivers.
Okay so I installed the drivers and I still am having no luck. I don't know if you would know but since it's going to be replaced through Asurion insurance and not T-Mobile's warranty service, does it really matter if it's just unlocked? No root or rom, just unlocked. I'm thinking since it's obviously not a software issue then they won't care if it's unlocked.
*** Scratch that, my adb folder got messed up or something and it didn't have fastboot in it. A thousand times thank you! The universal drivers totally worked and everything went great once I realized that I overlooked something so simple. Now I won't have to worry about T-Mobile giving me any problems!
Hi!
First of all, yes I've browsed and tried the different solutions in the forum but none of them worked for me.
My Nexus 4 fell from my car (a long story) and the screen is completely destroyed, and yes I mean DESTROYED. The phone works cause the screen lights up and some colours still work, but I can't see anything, and the touchscreen of course does not work.
Problem is: I had a lock pattern so I can't access the data in my computer. I've tried Droidbrowser and the unified Android Toolkit, the last one always gets stuck on "waiting for adb mode" or something like that. I'm pretty sure I had USB debugging activated and all that, but except that, phone is factory, no root, no ROM, no unlocked bootloader.
I've been struggling with this for a while now, would appreciate some help!
Thanks in advance
dari1495 said:
Hi!
First of all, yes I've browsed and tried the different solutions in the forum but none of them worked for me.
My Nexus 4 fell from my car (a long story) and the screen is completely destroyed, and yes I mean DESTROYED. The phone works cause the screen lights up and some colours still work, but I can't see anything, and the touchscreen of course does not work.
Problem is: I had a lock pattern so I can't access the data in my computer. I've tried Droidbrowser and the unified Android Toolkit, the last one always gets stuck on "waiting for adb mode" or something like that. I'm pretty sure I had USB debugging activated and all that, but except that, phone is factory, no root, no ROM, no unlocked bootloader.
I've been struggling with this for a while now, would appreciate some help!
Thanks in advance
Click to expand...
Click to collapse
With out an unlocked bootloader or a custom recovery I'm afraid you're sol. Otherwise you'd need to boot into the os which you can't do with a lock pattern to use adb.
Sent from my Nexus 9 using XDA Free mobile app
>Install vysor on Windows.. Then connect to your phone..
semdoc said:
>Install vysor on Windows.. Then connect to your phone..
Click to expand...
Click to collapse
Well, vysor doesn't look like detecting my phone...
I ran over my phone and broke the screen on my s5. It will boot up and everything works accept my screen is black, digitizer is not responding to finger touch. My phone didn't have a passcode only swipe to unlock. Its running Marshmellow OS. When I connect to kies it reports the phone is locked and I need to enter the passcode on the device. I used "findmymobile" to unlock the phone and I can hear it unlock but Kies still says its locked. Can someone please help?
Try this
http://forum.xda-developers.com/showthread.php?t=2786395
unfortunately I do not have USB bugging on. This is going to be challenging but I'll give it a try
If you put a new screen on the phone you won't loose your data, just get a new digitizer.
Sent from my SM-N910V using Tapatalk
yeah but the digitizer is like $150 CAN, Are there cheaper ones available?
Read a post on another forum saying someone with the same problem, USB Debugging disabled and broken screen, managed to backup by booting the phone in recovery mode / safe mode, and using KIES to create a backup
Recovery mode
http://wccftech.com/galaxy-s5-recovery-mode-how-to/
Hi,
I recently broke the screen. Phone's display is working while the touch panel isnt. I was able to recover all the data via adb pull.
I want to use this device for computational purposes. Any suggestions for a ROM which is prerooted ?(i dont need a gui either).
Remember, if su via adb pops put a dialog box on the screen, i wont be able to accept it since touch isnt working.
Current rom : Stock 4.4.4 (rooted)
Recovery : twrp
Bootloader : unlocked
Much thanks.
You can use that phone from your computer like normal
http://forum.xda-developers.com/showthread.php?t=2786395
I had nexus 4 in the same condition. Bad thing that no one posted this info in my thread (not on this site) So i tried to change digitizer and broke LCD too
Hi all,
I'm an idiot.
I dropped my 6P and totally destroyed the screen. Occasionally I get some small amount of display but definitely no touch response. Everything else seems to be working as far as I can tell.
I'd like to recover some data and then wipe it.
The phone is running rooted stock (June Update) with TWRP, USB Debugging is enabled, the device isn't encrypted.
Theoretically, I'd just connect with ADB and pull what I wanted and then use Android Device Manager to do a remote wipe.
However, as specified above, I'm an idiot. I also broke my laptop, so I can't connect with ADB as I can't approve the new RSA key for another computer.
I suspect that there must be some magical bootloader / recovery / fastboot magical kind of workaround I could use to pull some data but I'm working blind, and when you're as much of an idiot as I feel after the last few days (did I mention that I also crashed my car) then working blind isn't easy.
Could anyone help me out with some instructions? Obviously bearing in mind that I have no display.
Never mind. I figured it out. Power off, boot to bootloader, fastboot into recovery. ADB then worked fine.