Moto X (1st Gen) work w/ USB keyboard via OTG cable? Screen smashed need help - Moto X Q&A

Hi All. I apologize for begging for help in my first post here.
Just to get it out of the way, I am a complete rube when it comes to tinkering with mobile phones.
I have a Moto X (1st Gen) which has served me well for 20 months, but this morning I dropped it on the sidewalk and the display shattered. I can still make out about 1/2 of the display (right half) but the digitizer is completely shot. The phone is locked with a text pin (not pattern). The phone appears to boot normally and I can see the usual lock screen with notification icons when I power up. However, since the phone recognizes no touch input, I can't unlock it. The phone is not rooted, completely stock, running Lollipop.
I'd be fine just buying a new phone at this point but I have a lot of data (mostly photos) I'd like to back up. But when I connect the phone to a PC with a USB cable, the PC does not recognize it's there. I *think* this is because the phone is locked -- I think when I unlock it, the phone mounts and I can access it's storage from my PC. But while it's locked, the computer doesn't even know it's there. It's possible that even when unlocked I need to click through some confirmation on the phone -- I don't quite remember.
I've been trying to think through some options to get into the phone and am wondering if I just picked up an OTG cable and a cheap USB keyboard if i'd be able to enter the pin and unlock the phone. Could it really be that simple?
Of course at that point I'd face the potentially insurmountable challenge of having to confirm the USB connection without being able to "click" the screen, but i'll cross that bridge when I get there.
Thank you all for your help, I truly appreciate you sharing your expertise to help out a dummy like me. :fingers-crossed:

lowbar said:
Hi All. I apologize for begging for help in my first post here.
Just to get it out of the way, I am a complete rube when it comes to tinkering with mobile phones.
I have a Moto X (1st Gen) which has served me well for 20 months, but this morning I dropped it on the sidewalk and the display shattered. I can still make out about 1/2 of the display (right half) but the digitizer is completely shot. The phone is locked with a text pin (not pattern). The phone appears to boot normally and I can see the usual lock screen with notification icons when I power up. However, since the phone recognizes no touch input, I can't unlock it. The phone is not rooted, completely stock, running Lollipop.
I'd be fine just buying a new phone at this point but I have a lot of data (mostly photos) I'd like to back up. But when I connect the phone to a PC with a USB cable, the PC does not recognize it's there. I *think* this is because the phone is locked -- I think when I unlock it, the phone mounts and I can access it's storage from my PC. But while it's locked, the computer doesn't even know it's there. It's possible that even when unlocked I need to click through some confirmation on the phone -- I don't quite remember.
I've been trying to think through some options to get into the phone and am wondering if I just picked up an OTG cable and a cheap USB keyboard if i'd be able to enter the pin and unlock the phone. Could it really be that simple?
Of course at that point I'd face the potentially insurmountable challenge of having to confirm the USB connection without being able to "click" the screen, but i'll cross that bridge when I get there.
Thank you all for your help, I truly appreciate you sharing your expertise to help out a dummy like me. :fingers-crossed:
Click to expand...
Click to collapse
see if you can access the recovery while the phone is plugged in. i know that I've been able to get access to the phone's internal storage while in recovery mode.

jco23 said:
see if you can access the recovery while the phone is plugged in. i know that I've been able to get access to the phone's internal storage while in recovery mode.
Click to expand...
Click to collapse
Thank you for the great suggestion and for your help. Unfortunately I tried that and did not have any luck. It doesn't help that the part of the screen that's completely shattered is exactly where the menus are located.
When I restarted into the bootloader with the phone plugged into my PC, the PC makes the tone as if a usb device was connected, but no additional drive appears in My Computer. When I go on from there to select recovery mode (second option down, I think? I can't actually see any of the menu options), the PC makes the usb disconnect tone. I did this all again looking at the Device Manager while I was doing this and it seems when I connect the phone the device "ADB Interface" appears, and underneath that "Mot Single ADB Interface." Definitely getting well beyond the point that I have any idea what I'm doing.
Worst of all, I'm pretty sure I messed up the phone worse now because when I try to start it up normally now, instead of getting to my usual lock screen (I could previously still see some remnants of the clock, wallpaper, and notifications), now (after going through the motorola startup animations and new-with-lollipop-update verizon red screen) I just see a blank screen with what appears to be a white box in the middle of it. I can't even turn the screen off with the power button. Before I started messing around with the bootloader it wasn't this so I probably stupidly selected a wrong option somewhere while clicking blind. So frustrating.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

lowbar said:
Thank you for the great suggestion and for your help. Unfortunately I tried that and did not have any luck. It doesn't help that the part of the screen that's completely shattered is exactly where the menus are located.
When I restarted into the bootloader with the phone plugged into my PC, the PC makes the tone as if a usb device was connected, but no additional drive appears in My Computer. When I go on from there to select recovery mode (second option down, I think? I can't actually see any of the menu options), the PC makes the usb disconnect tone. I did this all again looking at the Device Manager while I was doing this and it seems when I connect the phone the device "ADB Interface" appears, and underneath that "Mot Single ADB Interface." Definitely getting well beyond the point that I have any idea what I'm doing.
Worst of all, I'm pretty sure I messed up the phone worse now because when I try to start it up normally now, instead of getting to my usual lock screen (I could previously still see some remnants of the clock, wallpaper, and notifications), now (after going through the motorola startup animations and new-with-lollipop-update verizon red screen) I just see a blank screen with what appears to be a white box in the middle of it. I can't even turn the screen off with the power button. Before I started messing around with the bootloader it wasn't this so I probably stupidly selected a wrong option somewhere while clicking blind. So frustrating.
Click to expand...
Click to collapse
Since you're already getting another device, my advice would be to install the factory image (this, at least clears the lockscreen). Then, once it boots up, you'll be able to access the internal storage via USB.
Sent from my Moto X using XDA Free mobile app

You can't get to the password box with keyboard only, you need to swipe the ring or the screen to get to the password box, a combo of keyboard - mouse - keyboard may work. It will take lots of tickle though.
If you flash system without wiping data will most likely result in soft brick, resort to this if nothing else left.
My advice is to unlock your bootloader, it's all done in fastboot, then flash cwm or twrp and access your storage through there, they both support adb while in recovery. Then it's just simple matter of pull with adb whatever you need.

liveroy said:
You can't get to the password box with keyboard only, you need to swipe the ring or the screen to get to the password box, a combo of keyboard - mouse - keyboard may work. It will take lots of tickle though.
Click to expand...
Click to collapse
Thank you! This actually worked with only a moderate amount of tickle. I had to be very quick from the point of swiping to the PIN screen using the mouse, getting the keyboard plugged in, giving it a second for Moto X to recognize keyboard, then entering the pin -- then getting it plugged into PC via USB before screen locked again. I only have a handful of pixels in the lower right corner still shining on this thing so it was just in the nick of time. Now I can order a new phone instead of spending money on getting a new screen installed in this one. Thanks so much liveroy for the pointer! And thank you jco23 for your advice and guidance as well!
For further fun now that I'm "in" (and I *think* I have USB debugging turned on from using Easy Tether recently), perhaps I can use an app like this to control the phone from my PC? http://www.xda-developers.com/contr...n-screen-from-the-comfort-of-your-windows-pc/
My only worry is when I download this app, I get some savage virus warnings from Symantec endpoint protection which basically say "we are just about certain this contains something malicious...."

Just in case anyone comes upon this post looking for answers to the same issue -- I happened upon a way to unlock an android phone that doesn't have a working display or touchscreen that's a lot more straightforward than jockeying around the mouse and keyboard via an OTG cable. If you give your phone a voice command (e.g., "OK Google Now . . . Navigate To Home") and you use a PIN for security rather than a pattern, you'll be asked to "say or type PIN code." Say your PIN, and the phone unlocks, and you can get your photos and such off it via USB.
I'm not sure if you can unlock by voice if you have a pattern lock, I've never used them...

Related

[Q] Def Bricked!!! Prove me wrong pls.

Okay I used Unleash the Beast to root, etc. And stupidly I thought that I didn't have to Go back to stock w/ odin because I hadn't flashed any roms yet.
I flashed SRE 1.3 and I got a boot loop about installing files. I pulled the battery and now ALL that I can get is White AT&T screen (unplugged) or a loading icon that doesn't move(usb plugged in). I have tried Adb, every combination of vol up/down + power, or without power, and the buttons by themselves. Can't get to Download mode or Recovery.... Any suggestions?
You try vol-up+down while off, hold it down, and plug it in while down?
try plugging in the usb when trying to get it into download mode. I was having some issues till I did that.
I appreciate the ideas guys but yeah I've tried both of those. What I'm really looking for is a way to force the phone into download through usb. Neither Adb or Fastboot work.
the pull SIM card and SD card trick always seems to work for me. My phone is a PITA to get into download mode. Just have to keep at it.
Yea, from reading these threads I'm beginning to think that these phones aren't brickable. Everyone who's been unable to get odin to work, it seems, wasn't doing the dl-mode properly. It seems it's primarily because of two issues
(1). (I gathered this from reading threads)--it seems there are different methods for getting into dl-mode for different phone models. I have no idea what kind of phone you have, but there are apparently several ways to get to dl mode (i'm talking strictly about pushing hard key methods). Something common to all of them, however, is that it's a good idea to remove your battery for a minute prior to attempting to get into dl mode.
(2). (may have made this up)--getting drivers installed for this phone is a pain in the butt. It seems there are different drivers for adb/usb debugging, mass storage mode, kies, each of the memory cards, and dl-mode. It took me forever to get the drivers working properly. What I did was just manually install the driver for each device in device manager. I downloaded a folder of drivers from somewhere, and it contained every driver i needed (i think).
Hope this info helps man, i'm sure you'll get it figured out
Pulled the sim(had to use it a dif phone) and don't have an sd card installed. No dice.
I've followed the standard procedures. Did SOME searching, still haven't found anything.
Hmmm. I got ADB to work before the brick.(Adb reboot recovery)
What are Kies? Any idea about those drivers.
I may just have to send it back to AT&T and get another.
Ps. you can get the Captivate for $99 w/ an upgrade on Amazon(w/ family plan) Cheaper on individual.
This is the method that works for me, always. Like, always always. Never failed.
If you have problems getting into Download Mode try this method:
1. Take out your sim card, sd card, battery and open Odin3.
2. Put the battery in.
3. Plug in USB. (the phone will power on to that screen)
4. Hold down both Volume keys, and then push power. Hold it and dont let go.
5. Wait for it to go black.
6. When it goes black the 2nd time release power and keep holding the Vol Down and Vol Up.
This is from the HOW TO Galaxy S ROms thread over in development.
belyle said:
This is the method that works for me, always. Like, always always. Never failed.
If you have problems getting into Download Mode try this method:
1. Take out your sim card, sd card, battery and open Odin3.
2. Put the battery in.
3. Plug in USB. (the phone will power on to that screen)
4. Hold down both Volume keys, and then push power. Hold it and dont let go.
5. Wait for it to go black.
6. When it goes black the 2nd time release power and keep holding the Vol Down and Vol Up.
This is from the HOW TO Galaxy S ROms thread over in development.
Click to expand...
Click to collapse
Appreciate it but it's not working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stuck at this screen when plugged in. Whether it's this screen or the white AT&T World phone screen if I hold at minimum Power+Up volume the screen will go black and then come right back.
And I have tried all other button combos
kylelipp said:
Appreciate it but it's not working.Stuck at this screen when plugged in. Whether it's this screen or the white AT&T World phone screen if I hold at minimum Power+Up volume the screen will go black and then come right back.
And I have tried all other button combos
Click to expand...
Click to collapse
Read 7th post on this page
If it plugged into USB it will show the battery icon. Hold vol down and up plus power...black screen....at&t logo...black screen and release the power button. key being the black screen
Belaflek said:
If it plugged into USB it will show the battery icon. Hold vol down and up plus power...black screen....at&t logo...black screen and release the power button. key being the black screen
Click to expand...
Click to collapse
That's what I'm saying I doesn't even get the battery it's just that freakin circle(if powered off and then plugged in. Doesn't matter what buttons I'm holding). It doesn't move it just sits there. If I do the button combos it'll go black. and come back. I'll release power on 2nd black screen and no dice. If I don't have it plugged into usb I get the White AT&T screen. Holding Up/Down+Pwr or UP+Power will make the screen flash back, wait til 2nd black screen release power, still AT&T screen. hold power+up, release on second black screen and just hold down, nothing. I'm going to try iceczar1's suggestion(posted below) and see what happens.
@iceczar1
Originally Posted by KCutrer1
Nope adb doesn't work because at the "Phone..!..Computer" screen it can't find the device. Looks like I might be screwed on this one.
Read First! (useless phrase): I am not responsible for any damage you will cause to your phone. No matter if is just bricking or throwing with it out of the window. Is not my fault
Step 0: Make sure you have Samsung Drivers intalled!!!!
No drivers, no way to get your phone back on its feet.
1. Just Take out the battery, SIM and SD Card. Make sure USB is not plugged.
2. Wait a bit ... lets say 1 minute (not really important but whatever).
3. Plug in the battery
4. Push the power button
5. Open Odin
6. No matter what message appears, plug in the USB.
Situation 1: Odin recognizes it: apply the patches that last time worked.
Situation 2: -Recommended- If you dont know what to apply or what to do take a look a this post . It will revert your phone to stock ROM (like it was when you got it)
Situation 3: Odin does not recognize it and you cannot see it in Device manager as Samsung Android Composite ADB Interface (and not even as a device with a question mark) then try booting like this:
1a: Take all out (SIM, SD, Battery, USB cable)
2a: plug in battery
3a: hold volume down + up (or up + down, doesn't matter) and insert USB
If you get the battery, then try again step 1a, 2a and the following:
4a: Hold volume down only + insert the USB.
If still no go then I dont know what to tell you my friend. Your phone is defect, because a normal Galaxy S cannot be bricked unless you find a way to flash the "BIOS" on the motherboard (on a separate chip), which, if I know correctly, is not writable (if someone knows better, please correct me and dont tell me Clockwork Recovery does that and flashes over the stock recovery, coz it doesn't. If it would, we would have it as an option when entering recovery mode for ever and we would have no way to see the stock recovery mode anymore)
PLEASE, WHILE YOU ARE DOING ALL THESE STEPS KEEP AN EYE ON WINDOWS DEVICE MANAGER AND ODIN!! IF ANY CHANGE APPEARS, MAKE A NOTE AND TRY TO REPEAT THE ACTION YOU TOOK TO MAKE THAT CHANGE APPEAR! You can even post it here, we might find it useful.
Click to expand...
Click to collapse
I'll try this when I get home. I'm not holding out hope though.
oooooo just the little circle dealy you get just before the battery shows up. If you are able try this.
Unplug usb
vol up and down + power
When the first at&t logo pops up..plug in the usb (while still holding buttons, and wait for second black screen (if it will get that far) then let off the power button.
Kind of what the above poster said. Power then plug
@Belaflek
If I power on to AT&T then plug in and try the Pwr+Up(or Up&down) it will go black and then back to the circle.
You're having the same problem I had.. My phone the day I recieved it would not go into recovery or downlode mode via the button combinations. There is a thread that some others are having the same problem.
Out of curiousity were the button combinations working for you before?
If they weren't then you're going to have to send the phone back.. Despite people saying "well this combination works for me" Something happened with a batch of these phones and for some reason the button combination doesn't work.
If you can't get the button combinations to work, then you are stuck.. send it back so you can get a new one..
No the button combos didn't work before. Yeah I think I'll have to send it back Means I'll be w/o for about a week... I'm gonna be going through some serious withdrawal.
Okay I've tried everything! I'm done with trying I'm just going to send it back. I'll just have to be more careful next time.
As an aside: Basically you always have to use Odin to Flash back to stock before Flashing a new rom is that about right? Or does the Recovery mode have a wipe data, or other way to get back to Stock?
kylelipp said:
Okay I've tried everything! I'm done with trying I'm just going to send it back. I'll just have to be more careful next time.
As an aside: Basically you always have to use Odin to Flash back to stock before Flashing a new rom is that about right? Or does the Recovery mode have a wipe data, or other way to get back to Stock?
Click to expand...
Click to collapse
You always have to use Odin to flash back to stock unless you have bone stock, just rooted, installed ROM Manager, flash ClockworkMod and back up that setup, then you could use Rom Manager to revert back to stock with root. I think Odin is quicker though. Before you do anything with your replacement phone make sure the button combo works that way you don't get bricked.
Thanks Rhiannon224, for that info.

[Q] NC wont turn on, no power, just a dead device

hi!
bought this NC for my wife last December. For 3 months it was working fine, didnt root it and it was running on 1.0.
The other night, she told me that it wouldnt turn on, so I researched and found the power button + n combination. I charged the NC first and when it became green, I removed it from the charger and performed the power +n combination.
It turned on, Hoorah!
But this afternoon, my wife told me that the browser was taking too long to load. When I had a look, the screen was unresponsive and it was frozen already.
So I turned it off using the power button. When I attempted to turn it on again, I wouldnt anymore. Tried the power+volume+ and n combination, none.
Tried the 8 boots, by holding it at least 20 secs, none.
downloaded and installed the rootpack_X.tar.gz, burned it to an SD, pressed the power button, none.
tried pressing all the buttons but still none.
There is no power, black screen, nothing, zero, dead.
problem is I cant bring it to BN because I'm outside of the US.
I'm exhausted. Appreciate any suggestion, including throwing the NC to the wall :-(
Update
Charging it again... anxiously waiting for it to turn green. Will try to boot with an SD inside.
You using something other than a stock ROM? If so, your /boot is probably corrupted or formatted.
Did you format "SD Card" from the settings? On Nookie Froyo, Honeycomb, and CM7 (at least older versions) that would actually format /boot not the SD card.
marcillus said:
Charging it again... anxiously waiting for it to turn green. Will try to boot with an SD inside.
Click to expand...
Click to collapse
Sounds like the same problem I'm having. Are you stuck at the red battery screen?
Here's a link to the thread I started. http://forum.xda-developers.com/showthread.php?t=996439 If you don't mind maybe if you could read through it and tell me if your having the same problem. This nc is also stock and never been updated like you and mine was also bought in dec.
losing hope
@jvillejoe
mine is totally blank, the screen is black, nothing. no red battery screen
when you charge it, after a while the light will turn green meaning the device is fully charged. when you press the power button for 1-3 seconds, no reaction.
@khaytsus
nope this is the stock ROM, i tried downloading and installing 128mb_rootpack-0.7.tar, but if you cant turn the NC on, i dont think it will boot.
what's bad is that you can't open it. disaster
thanks for your help guys...
It won't boot from the SD card either?
It sounds like what happened to mine. I ended up returning it. I couldn't pinpoint the problem because I had already rooted it and flashed a couple of different custom ROMs by that point but it stopped booting even from an SD card.
Luckily I could get it to boot up one out of every thirty tries or so for a few minutes so I managed to return it to stock before I returned it to the store.
Question, if you plug it into the PC then hold down the power button for ~30 seconds, does your PC make the "device connected" noise then immediately make the disconnect noise?
marcillus said:
@jvillejoe
mine is totally blank, the screen is black, nothing. no red battery screen
when you charge it, after a while the light will turn green meaning the device is fully charged. when you press the power button for 1-3 seconds, no reaction.
@khaytsus
nope this is the stock ROM, i tried downloading and installing 128mb_rootpack-0.7.tar, but if you cant turn the NC on, i dont think it will boot.
what's bad is that you can't open it. disaster
thanks for your help guys...
Click to expand...
Click to collapse
Oh ok so seems like your problem is not the same as mine. Just wanted to tell you another guy that posted on my thread said he opened his nook up and pulled the battery. Just a thought but if you have a stock NC then you might want to take it back to B&N or what ever place you bought it from.
My bro-in-law had this problem today, but we were able to get it back on. It's weird, almost like it thinks there is something wrong with the battery, at least that's what it feels like to me. I told him if it happens even one more time to take it back...his is rooted and CM7 on it. When we got it back on there was no problems. Gonna mess with it a little for him to make sure it doesn't happen again.
marcillus said:
@jvillejoe
mine is totally blank, the screen is black, nothing. no red battery screen
when you charge it, after a while the light will turn green meaning the device is fully charged. when you press the power button for 1-3 seconds, no reaction.
@khaytsus
nope this is the stock ROM, i tried downloading and installing 128mb_rootpack-0.7.tar, but if you cant turn the NC on, i dont think it will boot.
what's bad is that you can't open it. disaster
thanks for your help guys...
Click to expand...
Click to collapse
How did you place the rootpack on the SD CARD? Did you unzip it and burn the image or did you just drag and drop it?
Question, if you plug it into the PC then hold down the power button for ~30 seconds, does your PC make the "device connected" noise then immediately make the disconnect noise?
Click to expand...
Click to collapse
@hitting smoke
yes it does this, it makes a sound, prompt, that it has been connected then after a few seconds it makes the disconnected sound...
any ideas?
How did you place the rootpack on the SD CARD? Did you unzip it and burn the image or did you just drag and drop it?
Click to expand...
Click to collapse
@human0metronome
yup, unzipped and burned it, just as the instructions stated...
Just wanted to tell you another guy that posted on my thread said he opened his nook up and pulled the battery. Just a thought but if you have a stock NC then you might want to take it back to B&N or what ever place you bought it from.
Click to expand...
Click to collapse
@jvillejoe
this I gotta see... I've been wanting to pry the NC open
thanks again for the help
off to buy a Torx T5...
wish me luck
Good luck. Best not do anything wrong or it's the dog kennel for you tonight.
My nook is dead
Okay, i installed cyanogen 7. i didn't like it so i wanted to reboot clockwork recovery, but my ook would just go directly to cyanogen 7 without getting to clockwork recovery menu. I finally just to deal with it another time.
I left it in the power outlet and I noticed for the very first time it didn't turn green.
Anyway, when i disconnected it from power cord, it would not even turn on anymore.
When I connect via usb to my pc, it recognizes the omap processor in other devices for a second before win 7 stops recognizing and it disappears from other devices.
What is going on? it's blank as it wont turn on.
please help!
If you have a SD card in the Nook try removing it and then try turning on the device. I bought a nook Friday and ran in to a similar issue. The device would not power up regardless of how long I held the power button. Once I removed the SD card it turned on ok.
marcillus said:
off to buy a Torx T5...
wish me luck
Click to expand...
Click to collapse
Can we assume from this that you no longer have the NC unit? If you do, connect it to your computer and see if it turns on. I had this issue but using the cable to connect it to my computer caused the unit to turn on, and never had any problems after that.
migrax
opened it and made sure that all connections are good. but still no luck...
might experiment further
here are some pictures
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cant get the right size... sorry I only used a phonecam

Broken Screen, Need USB Debug mode on.

So this is for my dad's phone. He dropped it and the screen and the LCD panel part busted so the whole screen is all black. Can't see a single thing on it. He got a new (read:refurbished) one so that's not an issue. I'm trying to use a screen mirroring program to factory reset the phone before he sends it back to Motorola. Issue seems to be those programs require USB debugging mode to be turned on but since the screen is all black, I can't do that. I even tried doing multiple screenshots and guessing where things were but it didn't work (worried the top of the phone's touch digitizer is busted too but i'm hoping for the best lol). So I need a way to turn on USB debug mode, with a totally black screen (touch still works), NOT ROOTED, so I can then mirror it with the MirrorGo or Vysor mirroring software so I can factory reset the device. If you have any thoughts for a simpler fix then I'm open to suggestions. I'm not tech savvy enough to do anything with Rooting and i'm not confident enough to try doing that with a busted phone (if it's even possible), so that's an option that's out too. :/
Buddha8888 said:
So this is for my dad's phone. He dropped it and the screen and the LCD panel part busted so the whole screen is all black. Can't see a single thing on it. He got a new (read:refurbished) one so that's not an issue. I'm trying to use a screen mirroring program to factory reset the phone before he sends it back to Motorola. Issue seems to be those programs require USB debugging mode to be turned on but since the screen is all black, I can't do that. I even tried doing multiple screenshots and guessing where things were but it didn't work (worried the top of the phone's touch digitizer is busted too but i'm hoping for the best lol). So I need a way to turn on USB debug mode, with a totally black screen (touch still works), NOT ROOTED, so I can then mirror it with the MirrorGo or Vysor mirroring software so I can factory reset the device. If you have any thoughts for a simpler fix then I'm open to suggestions. I'm not tech savvy enough to do anything with Rooting and i'm not confident enough to try doing that with a busted phone (if it's even possible), so that's an option that's out too. :/
Click to expand...
Click to collapse
You can go into recovery mode and do the factory reset there, it's probably the easiest way to do it.
zys52712 said:
You can go into recovery mode and do the factory reset there, it's probably the easiest way to do it.
Click to expand...
Click to collapse
Yea, i tried that with the bootloader/fastboot thing. It didn't seem to work. I can barely tell if the device is even ON, only indication it's on is the volume rocker makes a noise to indicate volume and the bottom buttons light up. So being able to tell if the device is even IN it's bootloader mode thing was a crapshoot. I'm gonna need either a way to screen mirror in real time without debugging mode on, or a way to enable debug mode remotely essentially.

HELP! I've hardbricked my mi 5 :(

Hi all
I have managed to hardbrick my phone without even trying to flash it.
I have a white 128gb Mi 5 with an unlocked bootloader and (i think) running Cyanogenmod13 (but it was such a long time ago that i installed it - before global stable was out) I've always been happy with it but kept meaning to sit down and put global on it, but havent gotten around to it.
Yesterday i was using my phone, put it in my handbag, took it out ten mins later and it was completely dead. But it was definitely at 100% charge at the time as i had it plugged in on the train. No leds, no response, no screen, not recognised by computer or anything.
There have been a few instances when i pulled my phone out of my bag and the fastboot screen has been up and luckily i've cancelled it. I've been doing a bit of research and i'm pretty sure that i somehow managed to enter fastboot mode in my bag by accident and then corrupt it somehow?
I've been playing about a bit with it. (it's still under warranty, but I can't send it back, because it's got an unofficial rom on it)
I've managed to get it to be recognised on my laptop now by following a video tutorial which i'm not able to post because this is my first post, but it's from choimobile,vn and just in case anyone wants to know which steps i've made it to, this is the rest of the address, /threads/unbrick-xiaomi-mi5-repair-boot-xiaomi-mi5-hardbrick-pc-not-detected.
But i've reached a point that i can't go any further. In all the guides i've read, people talk about the pc recognising the phone as Qualcomm HS-USB QDLoader 9008 but mine doesn't. It just recognises it as "android" so then flashing with miflash doesn't work.
Does anyone know what else i can do? I'm a noob at this so if you could keep the explanations simple, that would be great!
Thanks
Angelina
Forgot to add... phone still connects to my computer fine, i can still see everything and can access the internal memory.
Here's some photos
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm pretty sure you can't actually do any damage in fastboot without being connected to a PC.
You say your pc detects your phone storage fine so that means it's either booted or in recovery. Either way, you should have some kind of display being shown so it sounds like your screen is broken.
Do you know what recovery you have installed? I'd advise you try to reboot into it (power off -> hold power and volume up) or boot into fastboot and flash twrp recovery.
If your screen never changes from off after restarting, it's likely the screen that's the issue.
Sent from my MI 5 using Tapatalk
andythedev said:
I'm pretty sure you can't actually do any damage in fastboot without being connected to a PC.
You say your pc detects your phone storage fine so that means it's either booted or in recovery. Either way, you should have some kind of display being shown so it sounds like your screen is broken.
Do you know what recovery you have installed? I'd advise you try to reboot into it (power off -> hold power and volume up) or boot into fastboot and flash twrp recovery.
If your screen never changes from off after restarting, it's likely the screen that's the issue.
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
Hmm, OK that's strange, i've not done anything that would break it, especially in that short period of time. But I guess it could be a loose connection or something. Although that wouldn't explain why there are no leds or why it doesn't respond to being charged? if it was a broken screen, everything else would work fine.
I could only see it on my pc after taking it apart, disconnecting the battery and using tweezers to connect 2 points on the internal board like in the video above. If i disconnect it, then plug it in again, it's not recognised until i use the tweezers on the two points again.
I've tried to reboot it and get into fastboot again, but it definitely isn't responding.
Thanks
hmm have you tried plugging it to power source then hold power button like one min..?
because last week my phone was just dead, and doesn't respond to anything, though it's slightly different because mine stuck forever at 9008 mode, yet still stuck there even though i flashed new rom
the only cure to wake it up was to attach to charger then holding power button for one minute
or you can try using DFC cable to force into EDL mode
Hiya!
Yes i've tried various combinations of holding different buttons whilst fully charged/discharging/connecting to computer via the test point etc
Thanks for the suggestion though.
Unfortunately, the DFC cable won't work, as that is what i've done with the test point method. It will allow me to connect the phone to the computer but that's as far as it gets.
Bumping this in the hope that someone may have an answer.
Your phone was dead because your power button kept pressing accidentally for a long time as you kept it in your bag, i too have the same problem and I showed it in service center but no luck they suggested me to change the motherboard...

Black screen Pixel 4 XL, how to recover data?

My Google Pixel 4 XL fell from the second floor. The screen didn't break but it's now black and won't turn on. It has a small crack in the side plastic. When I connect the charger it vibrates as if it were charging. When I press the power button, it vibrates. When I connect it to my windows laptop, it shows as an "unspecified device" (see picture attached) and I can't access the memory.
Is there any way to recover some data such as whatsapp chat history or even to mirror the phone to my computer or something like that?
Thank you!
There are a lot of ways to do that but you need to unlock the phone first , do you have a lock pin or pattern lock ? Does the touch screen works ?
Deadmau73 said:
There are a lot of ways to do that but you need to unlock the phone first , do you have a lock pin or pattern lock ? Does the touch screen works ?
Click to expand...
Click to collapse
I have a pin. The screen/touch don't work.
Pretty much everything requires that you've done some footwork beforehand. If you had previously authorized a computer with ADB, you could use something like scrcpy to display the screen visuals on your computer. Browsing the phone storage on your computer won't work unless you've unlocked your phone. Which scrcpy could do, if ADB had been authorized.
You have to understand that your phone is encrypted by default and you have to unlock the phone to retrieve the encryption keys from the TPM. If your phone rebooted and is currently locked, you have to unlock it somehow. Even if that means tapping where you think the PIN digits should be to unlock the phone. The PIN input will have haptic feedback to tell you that you're at least doing something.

Categories

Resources