Hey guys!
I'm, currently running Maximum OvrDriVE v7.1.1.
So, I dropped my phone and my lcd is out, but somehow the glass and my tempered glass didn't crack one bit haha!
Anyways, can someone walk me through the process of enabling ADB using the recovery?
I'm currently using TWRP, I'm not sure if TWRP responds to volume controls but if I need to install clockwork so I can navigate the menus thats fine.
And remember, my screen is out so I can't see anything. I just need someone to walk me through the process of what sequence of buttons to press in order to flash a zip file, using clockworkmod recovery.
If someone can do that let me know what version you're running of the recovery so we can make sure our keypresses are the same.
If someone though can explain an easier way to enable ADB without having a screen let me know please, thanks!
ps. I can already access my internal SD, i just need ADB to backup my apps. Thanks!
Use an hdmi cable so you can use your tv as monitor. Hopefully the touch screen still works so you navigate.
Sent from my SM-N910T3 using Tapatalk
aznmode said:
Use an hdmi cable so you can use your tv as monitor. Hopefully the touch screen still works so you navigate.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
I have a broken lcd too, and this.. is a smart idea
As far as I can tell, my touchscreen still works.
And I hope that HDMI could work but I'm not certain if it would. But that's a good idea.
Related
I have this captivate whose screen went completely kaput on me, and I don't have a clue how to access the internal storage blind. I have sensitive information that I had on it before the screen broke. Should I adb? Or try and mount it?
You could do either, hell one better, look on Google for a program that allows you to have an interface like apk explorer or I think thats what its called.. anyways I have a glide now so this phone is my girls and I just mod it when she gets bored and wants to try something new...
johnd.the.cuban said:
I have this captivate whose screen went completely kaput on me, and I don't have a clue how to access the internal storage blind. I have sensitive information that I had on it before the screen broke. Should I adb? Or try and mount it?
Click to expand...
Click to collapse
ADB is probably your best bet here.
BWolf56 said:
ADB is probably your best bet here.
Click to expand...
Click to collapse
But right now, without the screen working at all, I don't have a way of turning on the usb debugging. I tried doing it blind, but I'm not even sure that the touch digitizer is even working either.
Is there a work around? Maybe like something I could do in download mode.
johnd.the.cuban said:
But right now, without the screen working at all, I don't have a way of turning on the usb debugging. I tried doing it blind, but I'm not even sure that the touch digitizer is even working either.
Is there a work around? Maybe like something I could do in download mode.
Click to expand...
Click to collapse
You can use adb commands through your pc, you won't need your phone's screen to force mount.
Another option would be to replace your screen.
Sent from my SGH-I897 using xda app-developers app
lapdock hack for non moto roms
in 3 easy steps
1: setprop persist.hwc.mirroring.region 0:0:540:960
2: download http://www.mediafire.com/file/3qvatv41t92u330/mirror.zip
copy dssmgr to /system/bin/ and hwcomposer.omap4.so to /system/vendor/lib/hw/
3. reboot, attach lapdock then hdmi and kill and restart dssmgr (otherwise you'll get 640x480 instead of 1366x768)
Enjoy! no warranties, 1366x768 only.
http://www.mediafire.com/file/blhonnzxflghb8u/dssmgr
this one shouldn't need to be killed and restarted, but it may reset the display occasionally. ymmv
Edit: http://www.mediafire.com/file/1wy1j2x8rivj3gd/dssmgr(2)
this one fixes teh one minute display resets. but only sets teh resolution once on hdmi detect.
Sorry I don't understand the first step you listed. "1: setprop persist.hwc.mirroring.region 0:0:540:960" what does this part mean?
crzayalex said:
Sorry I don't understand the first step you listed. "1: setprop persist.hwc.mirroring.region 0:0:540:960" what does this part mean?
Click to expand...
Click to collapse
Type that into a root shell. Terminal emulator after running su on phone or via adb shell on pc.
Ohh okay. Thanks kfazz!
Hey kfazz,
Sorry to bother again but right now I plugged my phone into the dock and the dock's screen wont turn on. The mouse shows on the phone's screen and it works just fine. What step am I missing?
crzayalex said:
Hey kfazz,
Sorry to bother again but right now I plugged my phone into the dock and the dock's screen wont turn on. The mouse shows on the phone's screen and it works just fine. What step am I missing?
Click to expand...
Click to collapse
Same here.
I'm having the same problem as well. Only have the mouse pointer on the phone and still a blank screen on the lapdock.
are you guys running dssmgr after you attach the lapdock?
otherwise it wont work.
attach phone to lapdock
open terminal on phone
su
killall dssmgr
/system/bin/dssmgr
then open lid
it should work
it's a pain, but its due to the hdmi event not being debounced properly. jb kernel has a fix for this, so once i stop being lazy i'll probably rewrite this prog.
i do have a rom with lapdock working properly tho:
http://forum.xda-developers.com/showthread.php?p=38953989
but it isn't cm.
i think i'll wait for you to rewrite the prog then x)
Sorry to necropost, but will this enable all dock support, such as car docks or is this specific to the lapdock? Also should this be able to work on CM10.2? I am planning to try it out tomorrow, just want to see if there are any others who have tried.
IndiaBhai said:
Sorry to necropost, but will this enable all dock support, such as car docks or is this specific to the lapdock? Also should this be able to work on CM10.2? I am planning to try it out tomorrow, just want to see if there are any others who have tried.
Click to expand...
Click to collapse
I would like to know this as well.
Khiraji said:
I would like to know this as well.
Click to expand...
Click to collapse
Just tried this with my HD dock and could not get it to load into Dock Mode. Have not tested HDMI.
I tried it on CM 10.2 but it only bootloops and gives blackscreen. phone wont turn on again.
Tried on CM 10.1. Got the mouse and keyboard to work but no hdmi
This probably has an easy fix!! I use the lapdock often, only the lack of compatibility with it is keeping me from using CM.
ive had my droid 4 For awhile now and I just recently bought an HDMI cable and when I plug it into the TV the popup comes up to select mirror mode or something else I don't remember now but the problem is as soon as that popup come up nothing on th touchscreen works iI have to use the arrow keys to make it work I don't know if I'm doing something wrong or if that's the way it works I don't know any help would be greatly appreciated
paintballspk said:
ive had my droid 4 For awhile now and I just recently bought an HDMI cable and when I plug it into the TV the popup comes up to select mirror mode or something else I don't remember now but the problem is as soon as that popup come up nothing on th touchscreen works iI have to use the arrow keys to make it work I don't know if I'm doing something wrong or if that's the way it works I don't know any help would be greatly appreciated
Click to expand...
Click to collapse
The touchscreen is supposed to basically turn itself into a trackpad like you'd get on a laptop.
Is there a mouse pointer on your TV display at all?
Yes it is supposed to become a track pad... accept when it was on GB on GB the screen was just black and needed an external pointing device... although I am sure that you have upgraded to at least ICS...
Sent from my XT907 using xda app-developers app
thanks for the info will be trying it again tonight when i get home
If i boot looped and had to load the maserati .xml, had spotty touch screen response, now its just dead. Replaced touch screen, re flashed multiple times both the last JB sbfs. Still no touch screen control.
What controls the touch screen then? Where is the firmware and does it get replaced/reinstalled with flashing a .xml?
I was able to push safestrap over and after installing it, all the sudden i had access to my other partitions. I cannot get into SS because i have no touch screen but is there a good chance my other partitions are interfering with my stock rom? Is it possible Kexec that i believe is ran for liquid smooth possibly the problem? Is it the kernal that controls the touch screen? b/c it doesnt work even in SS and that is before any roms are loaded....
HELP!!!
If you have twrp installed, check to see if touch screen works there before rom loads. I am having a goofy touch screen problem in a related thread. Wondering if problem lies with digitizer controller, the little magnet sensor for the slide, or worse, something on the motherboard.
Sent from my XT894 using Tapatalk 4
nowell29 said:
If you have twrp installed, check to see if touch screen works there before rom loads. I am having a goofy touch screen problem in a related thread. Wondering if problem lies with digitizer controller, the little magnet sensor for the slide, or worse, something on the motherboard.
Sent from my XT894 using Tapatalk 4
Click to expand...
Click to collapse
It doesn't work in twrp, plus ive replaced the digitizer(touch screen) so unless i flashed it wrong somehow, its the MB.
Unfortunately this also occurs when moisture finds it's way to certain components through sweat mostly. Not saying that's your case just a possibility
Sent from my XT894 using xda app-developers app
I wish i could say that i have found or will find a solution. But I cannot. this is my work phone so I need a working replacement right away, which I have now done.
i will add that my screen works about 2% of the time. i have to catch it and be lucky. Then watch that i dont turn off the screen or slide it closed again. So, it HAS to be a sensor that is messed up. Yes, it could be sweat. There is a lot of that on the side of my head these days in Phoenix!
Good luck guys with this. It is on to an S4 for me!
Sent from my TF300T using Tapatalk 4
I couldnt output the file so i ran /proc/kmsg and copy pasted the results. Are all the init: cannot find '/system/bin/...." entries in the beginning normal? Or is that my problem? And can i get around it?
Hello
My friend has Nexus 6, or should I say had. Unfortunately, he dropped his phone really hard on concrete. LCD is completely dead. He is dumb enough to never make a backup of his photos etc. Is there any way to get his data back ? Phone is pure stock.
Thanks for any help
grzechu51 said:
Hello
My friend has Nexus 6, or should I say had. Unfortunately, he dropped his phone really hard on concrete. LCD is completely dead. He is dumb enough to never make a backup of his photos etc. Is there any way to get his data back ? Phone is pure stock.
Thanks for any help
Click to expand...
Click to collapse
Does he have USB debugging enabled?
grzechu51 said:
Hello
My friend has Nexus 6, or should I say had. Unfortunately, he dropped his phone really hard on concrete. LCD is completely dead. He is dumb enough to never make a backup of his photos etc. Is there any way to get his data back ? Phone is pure stock.
Thanks for any help
Click to expand...
Click to collapse
If the phone turns on and boots just plug it in the PC and you might be able to port them to the PC.
Sent from my Nexus 6 using XDA-Developers mobile app
grzechu51 said:
Hello
My friend has Nexus 6, or should I say had. Unfortunately, he dropped his phone really hard on concrete. LCD is completely dead. He is dumb enough to never make a backup of his photos etc. Is there any way to get his data back ? Phone is pure stock.
Thanks for any help
Click to expand...
Click to collapse
Well a very annoying thing about Marshmallow is that the phone requires you to unlock it and select file share over usb mode otherwise it will only charge off a computer, if he had ADB enabled AND had it used on a computer in the past then you can do an ADB pull, but again on a new computer you'll have to confirm that you trust the computer to get adb to work. And even if he had TWRP recovery installed you'll still need to decrypt the phone using a passcode unless he used a unsecure lockscreen. Also if you have ADB access then you can use a chrome extension called "vysor" which mirrors the phone screen onto your computer to interact with it.
EDIT: just read pure stock...
Debugging is unfortunately off.
Is the actual screen destroyed, or just the digitizer?
If the actual screen is toast along with the digitizer, replacing the screen is the only means of retrieving his data. The good news in that regard is that taking apart the Nexus 6 is actually quite easy, based upon iFixit's teardown of the device.
If only the digitizer is gone, there may be some hope. Grab a USB OTG cable and a PC mouse. Connect the mouse to the OTG cable and plug the OTG cable into the MicroUSB port. Android should then generate a mouse cursor that you can use to maneuver around the device. From there you should be able to enable USB debugging if you want, or simply copy his data to Mega, Mediafire, Dropbox, or Google Drive for later retrieval.
I had the same thing happen to my N6. With nothing to lose, I banged it against my palm and saw the screen flicker. After a few more taps, I got the screen to come back long enough to back up data and get me through till a replacement arrived.