Related
Hello everyone
I've got a problem and I need your help. My Legend fell on the ground and now the glass and display are both broken. To access my device with adb, which I previously installed, I used DroidAtScreen. But recently I deactivated USB-Debugging eek, and now I can't enable it. I need to "recreate" every single step from the unlocked screen to Menu->Settings->Applications->Development->USB-Debugging. The first step (Menu->Settings) is easy and abvious, but I need the other ones.
Could some of you take some screenshots and upload them? I.e.:
1. Menu->Settings, then scroll down to bottom **Screenshot**
2. Scroll a little bit up until "Applications" reaches first entry **Screenshot**
3. Press first entry (=Applications) **Screenshot**
4. Press fourth entry (=Development) **Screenshot**
5. Press first entry (=USB-Debugging) *Screenshot**..
I know it may seem complicated, but it would be of tremendous help! My idea is to print out the images and lay them over the Legend to find my way to USB-Debugging
THANK YOU A LOT in advance!
memo9
Good thinking, you actually only need 4 screens, here you go...
Good luck replacing the screen! There's plently of material to work with in accesories section
If the digitiser (top glass) is broken i doubt your presses will be in the right place, I have a desire in front of me that has a crack in the top left corner of the digi and pressing "a" on the keyboard pull notification bar down
Thank you very much for the effort of taking the screenshots, but I couldn't access the settings.
The only question that remains is: Does the phone need to be in "charge only"-mode? Because right now, in fact I can access the SD-Card when mounted, so I may have to switch to charge only?
@bonesy: Thank you for the input, but the touchscreen seems to be working fine as I can turn on the phone and enter the PIN-code to unlock it, as well as call a number after opening the phone-application
ADB should work no matter what the mode...why weren't you able to access it?
I don't know... I followed all the steps, connected the phone to my Mac... all this several times, trying to press on the exact location... but haven't succeeded.
I have adb configured as well as DroidAtScreen running and also tried to access it with DDMS..., but when i use the command "adb devices" none is shown. I can access my SD-Card but can't use adb...
I may try again a few times but can't really think of any other alternative than to replace the screen, although I need to access my phone immediately.
Thanks again for all the fast answers and if anyone has an idea or some sort of walkthrough... I would appreciate it.
ADB wont work unless you are using a custom rom OR its selected already.
Maybe a USB port failure?
What do you mean? I have accessed my phone in this environment several times before, everything should be set up correctly. It may be a USB port failure, altough I have tried to plug it into other USB ports.
The only thing I'm struggling with right now is accessing the Debug-mode in the settings.
memo9 said:
What do you mean? I have accessed my phone in this environment several times before, everything should be set up correctly. It may be a USB port failure, altough I have tried to plug it into other USB ports.
The only thing I'm struggling with right now is accessing the Debug-mode in the settings.
Click to expand...
Click to collapse
Ah i see, i meant the phones usb port... Could be 1 pin failed on it stopping certain things working?
Doesn't seem to be the problem since I can mount the phone and access the SD-card, but thanks anyway.
Hi all,
I'm new here, a friend refered me this page to ask for some troubles I'm having with my Nexus 4.
I bought it from ebay about 4 months ago. For all this time, it worked perfectly, no problems at all, running fine.
The thing is that this last week the telephone is doing strange things. While using it, at a few minutes of use, "phantasmal touches" occurs, getting hit the buttons from back, back to desktop and last applications.
Also, after some minutes, or just touching the screen for scroll, the slide malfunction, getting harder to slide, even sometimes this doesn't works, but touching stills operative (sometimes not).
The only way that temporarily works, is locking and unlocking the screen, but problem still appear again and again.
Tried also to restore it (like as it was new). But nothing.
Hope you can help me with this. Thanks.
the-cheshire-cat said:
Hi all,
I'm new here, a friend refered me this page to ask for some troubles I'm having with my Nexus 4.
I bought it from ebay about 4 months ago. For all this time, it worked perfectly, no problems at all, running fine.
The thing is that this last week the telephone is doing strange things. While using it, at a few minutes of use, "phantasmal touches" occurs, getting hit the buttons from back, back to desktop and last applications.
Also, after some minutes, or just touching the screen for scroll, the slide malfunction, getting harder to slide, even sometimes this doesn't works, but touching stills operative (sometimes not).
The only way that temporarily works, is locking and unlocking the screen, but problem still appear again and again.
Tried also to restore it (like as it was new). But nothing.
Hope you can help me with this. Thanks.
Click to expand...
Click to collapse
Have you noticed if it stops or starts doing it if you plug it into a charger (preferably the stock or a decent quality one)
sp99 said:
Have you noticed if it stops or starts doing it if you plug it into a charger (preferably the stock or a decent quality one)
Click to expand...
Click to collapse
The charger is wich it came with the original mobil, and does it also when charging
Is it stock?
sp99 said:
Is it stock?
Click to expand...
Click to collapse
I'm sorry, what you mean with stock.
Have you rooted it or put a custom ROM on it?
sp99 said:
Have you rooted it or put a custom ROM on it?
Click to expand...
Click to collapse
No, it's not.
the-cheshire-cat said:
No, it's not.
Click to expand...
Click to collapse
Is the os up to date? (Settings-> about phone->Software updates->check for updates) Also try wiping the cache partition (I will post instructions of you need them).
sp99 said:
Is the os up to date? (Settings-> about phone->Software updates->check for updates) Also try wiping the cache partition (I will post instructions of you need them).
Click to expand...
Click to collapse
It's updated, and thanks for spending your time with this, I apreciate it, sincerely. Will wait for that instruction!
the-cheshire-cat said:
It's updated, and thanks for spending your time with this, I apreciate it, sincerely. Will wait for that instruction!
Click to expand...
Click to collapse
No problem.
This is from an email from Google regarding my nexus 7, it should be the same:
Hold the*Power Button*until the device powers down completely.Press and hold*Power Button*and*Volume Downsimultaneously.Once at the Android bootloader screen, pressVolume down*until you see the option*Recovery mode.Press*Power*button to restart into*Recovery mode. You should see an image of an Android with a red exclamation point.While holding down the*Power button, pressVolume Up.Use the Volume keys to scroll down to*wipe cache partition*and press*Power*Button*to select it. The device should clear the cache instantly.*Select and press the*Power Button*on*Reboot System Now, then see if the issue is resolved.
sp99 said:
No problem.
This is from an email from Google regarding my nexus 7, it should be the same:
Hold the*Power Button*until the device powers down completely.Press and hold*Power Button*and*Volume Downsimultaneously.Once at the Android bootloader screen, pressVolume down*until you see the option*Recovery mode.Press*Power*button to restart into*Recovery mode. You should see an image of an Android with a red exclamation point.While holding down the*Power button, pressVolume Up.Use the Volume keys to scroll down to*wipe cache partition*and press*Power*Button*to select it. The device should clear the cache instantly.*Select and press the*Power Button*on*Reboot System Now, then see if the issue is resolved.
Click to expand...
Click to collapse
Ok, it's done, I gonna test it for a while and see if it's solved
Nothing, less than a minute to the slider started to fail when moving up and down
the-cheshire-cat said:
Nothing, less than a minute to the slider started to fail when moving up and down
Click to expand...
Click to collapse
Don't quite understand, does that mean it has worked or it still has a problem?
sp99 said:
Don't quite understand, does that mean it has worked or it still has a problem?
Click to expand...
Click to collapse
The problem stills, for example, im in facebook or whatsapp, i slide up and down for reading, and from the nothing it's harder to slide/scroll... it's not that sensitive as before. I mean, with just a slide of the finger at early is scrolls fast, as it must be, but for some reason, after a few slides, with the same finger slide, it just scrolls a bit.
the-cheshire-cat said:
The problem stills, for example, im in facebook or whatsapp, i slide up and down for reading, and from the nothing it's harder to slide/scroll... it's not that sensitive as before. I mean, with just a slide of the finger at early is scrolls fast, as it must be, but for some reason, after a few slides, with the same finger slide, it just scrolls a bit.
Click to expand...
Click to collapse
Have you tried cleaning the screen with (alcohol free) screen wash? Otherwise it sounds like a hardware issue or something wrong with the touch drivers.
Sent from my Nexus 4 using Tapatalk
sp99 said:
Have you tried cleaning the screen with (alcohol free) screen wash? Otherwise it sounds like a hardware issue or something wrong with the touch drivers.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Even with the screen protector? Can try it. If it's the touch drivers, how can they be "reparired"?
the-cheshire-cat said:
Even with the screen protector? Can try it. If it's the touch drivers, how can they be "reparired"?
Click to expand...
Click to collapse
It's probably the screen protector causing the problem, take it off and then try using the phone again and see what happens.
Sent from my Nexus 4 using Tapatalk
the-cheshire-cat said:
Even with the screen protector? Can try it. If it's the touch drivers, how can they be "reparired"?
Click to expand...
Click to collapse
Well, for the moment I've done a wipe from all data, the other option from the "recovery menu", and it's been a while using it, and the problem doesn't shows, non of both i mention.
Let's see if this continue like this. Tomorrow I'll let you know.
thanks for all!
after this post, it came again T-T
the-cheshire-cat said:
Well, for the moment I've done a wipe from all data, the other option from the "recovery menu", and it's been a while using it, and the problem doesn't shows, non of both i mention.
Let's see if this continue like this. Tomorrow I'll let you know.
thanks for all!
Click to expand...
Click to collapse
You're welcome Remember to press the thanks/thumbs up button!
Sent from my Nexus 4 using Tapatalk
Nothing, the problem still persist.
I'll see if I must clean the screen (it has a screen-protector althought). If not, I don't know what to do, unless I send it to someone if can repair it or something... :crying:
Hi all,
I have a major problem with my Samsung galaxy tab 4. When I power on the tab sometimes it will hang on the splashscreen.
Then if and when I get through the frozen splashscreen the screen will flicker extremely badly, almost like interference and will freeze.
I done a factory reset, disconnected the battery, still the same issue.
Any ideas what the issues are?
Thanks in advance
skalicioustimes said:
Hi all,
I have a major problem with my Samsung galaxy tab 4. When I power on the tab sometimes it will hang on the splashscreen.
Then if and when I get through the frozen splashscreen the screen will flicker extremely badly, almost like interference and will freeze.
I done a factory reset, disconnected the battery, still the same issue.
Any ideas what the issues are?
Thanks in advance
Click to expand...
Click to collapse
I would find the correct firmware for your tab (from the Samsung site) and reflash the full Odin tar. If that doesn't help I'd contact Samsung about the issue.
Is there any point in getting in touch with Samsung after opening the tablet up?
There is horizontal and vertical lines approximately 5mm apart, coloured.
I can see the logo behind these lines but and the whole system has frozen.
This still happens after a factory reset which makes me think it may be a hardware issue.
Would it be a digitizer issue?
skalicioustimes said:
Is there any point in getting in touch with Samsung after opening the tablet up?
There is horizontal and vertical lines approximately 5mm apart, coloured.
I can see the logo behind these lines but and the whole system has frozen.
This still happens after a factory reset which makes me think it may be a hardware issue.
Would it be a digitizer issue?
Click to expand...
Click to collapse
That would be your display, not your digitizer. since you're thinking of opening the tab, check the connector
to the board from the display screen, just be patient, steady handed, and keep a light touch.
use a magnifying glass of you can't see the layout clearly, the connector may be seated wrong/crooked
there should/may be clips on either side that need to be slid out before disconnecting the ribbon.
I would get a replacement if you haven't opened the tab already.
questions belong in q&a. :good:
m
just a thought, check for moisture/corrosion anywhere, at the point you open the device, you're pretty
much S.O.L. but hey.
Yes unfortunately the Tab 4 has been opened.
By disconnecting and reseating the battery sockets i believe the warranty is void. The back has been opened.
I find if i get the device running momentarily then by gently plexing "twisiting" the unit in my hands can cause the screen to switch back to normal.
But soon after the dreaded horizontal and vertical lines appear then the device becomes frozen again, the intermitent lines jump around the screen with whatever is in the background leaving the display frozen.
Only solution is to gently open up the device and disconnect the battery and then reconnect again.
This is only a temporary solution as the problem reappears very soon after.
moonbutt74 said:
That would be your display, not your digitizer. since you're thinking of opening the tab, check the connector
to the board from the display screen, just be patient, steady handed, and keep a light touch.
use a magnifying glass of you can't see the layout clearly, the connector may be seated wrong/crooked
there should/may be clips on either side that need to be slid out before disconnecting the ribbon.
I would get a replacement if you haven't opened the tab already.
questions belong in q&a. :good:
m
just a thought, check for moisture/corrosion anywhere, at the point you open the device, you're pretty
much S.O.L. but hey.
Click to expand...
Click to collapse
So you reckon it is not the digitizer that has failed? I was thinking of replacing that.
Hmmm..
skalicioustimes said:
So you reckon it is not the digitizer that has failed? I was thinking of replacing that.
Hmmm..
Click to expand...
Click to collapse
I'm not so sure after what you said about twisting the tab, can you get into the system through adb ?
After the tab "freezes" hook up to your comp and get adb shell running, run any/all of the following
logcat -d
mount
ps
dmesg
and do some directory hopping to see what you can access, reason being we narrow it down to display/digitizer/something loose on board.
just to refresh my memory, the same behavior occurs in recovery ?
also tap your power button to screen-off/lock.
and at the end after adb test, force reboot to recovery with button combo.
m
moonbutt74 said:
I'm not so sure after what you said about twisting the tab, can you get into the system through adb ?
After the tab "freezes" hook up to your comp and get adb shell running, run any/all of the following
logcat -d
mount
ps
dmesg
and do some directory hopping to see what you can access, reason being we narrow it down to display/digitizer/something loose on board.
just to refresh my memory, the same behavior occurs in recovery ?
also tap your power button to screen-off/lock.
and at the end after adb test, force reboot to recovery with button combo.
m
Click to expand...
Click to collapse
I'm unsure about your suggestions, as i don't know were to locate those commands.
I have done a factory reset, so i am just waiting for the device to charge before attempting to load new firmware through Samsung Kies which i downloaded through this link... http://www.samsung.com/uk/support/usefulsoftware/KIES/#versionInfo
are the commands you suggested within the Samsung Kies software?
ahh, no. You need to run adb on windows [ewww]
or adb on linux [yay!]
can't help you with windows.
but what about in recovery ? did you encounter the same issue or no ?
m
moonbutt74 said:
ahh, no. You need to run adb on windows [ewww]
or adb on linux [yay!]
can't help you with windows.
but what about in recovery ? did you encounter the same issue or no ?
m
Click to expand...
Click to collapse
When i was having the problems initially, i could not for the life of me get into recovery mode using the button combo's. Eventually i did get into recovery, so as a last resort i cleared cache, and done a factory reset. Now it is booting up as normal but i was going to use Kies on windows to see if it is a software issue.
So were do i go about getting
adb
logcat -d
mount
ps
dmesg.
And what would you suggest as a step by step guide from were i am at now?
Note: i haven't physically messed with the device to see if the Horizontal and Vertical screen issue is still there.
Thanks
XDA search bar
adb install
moonbutt74 said:
XDA search bar
adb install
Click to expand...
Click to collapse
i tried running adb but i'm getting unaturiosed, clicked on the revoke debugging and then adb just ran through all the commands.
then the device screen problem has arisen again and i can't get it to boot.
skalicioustimes said:
i tried running adb but i'm getting unaturiosed, clicked on the revoke debugging and then adb just ran through all the commands.
then the device screen problem has arisen again and i can't get it to boot.
Click to expand...
Click to collapse
You're not supposed to revoke adb debugging.
Look, i'm at a loss, the thing is, do you blow more cash on a quess, or cut your losses.
As to learning how to use adb, XDA searxh box, using adb.
m
not a bother.
thanks for your help :good:
skalicioustimes said:
not a bother.
thanks for your help :good:
Click to expand...
Click to collapse
Hi,
you're not bothering me, i'm just saying you have to jump in all the way. :good:
m
moonbutt74 said:
Hi,
you're not bothering me, i'm just saying you have to jump in all the way. :good:
m
Click to expand...
Click to collapse
ah i understand, it's just it's driving me crazy. a bit like a crossword puzzle that i can't finish and i'm looking for someone to give me the answer without me having ta look up the answer in a dictionary....hahaha.
i suppose i am looking for someone who had a similar problem, a few clicks here and there
skalicioustimes said:
ah i understand, it's just it's driving me crazy. a bit like a crossword puzzle that i can't finish and i'm looking for someone to give me the answer without me having ta look up the answer in a dictionary....hahaha.
i suppose i am looking for someone who had a similar problem, a few clicks here and there
Click to expand...
Click to collapse
dude are you on hangouts ? if so pm me.
moonbutt74 said:
dude are you on hangouts ? if so pm me.
Click to expand...
Click to collapse
sent you a message on hangouts. thanks
Flashed the stock kernel using Odin, i hope that gets rid of the screen issue :fingers-crossed:
Well 3 hours later and the Tab is going good
My daughter is delighted that it's sorted and she hopes it stays that way
Many thanks to Moonbutt74 for your time and effort, it's very much appreciated.
Would you say that it's good to go? And is there anything else i need to do to the device before handing it over to her?
Cheers
I dropped my LG G2 D802, the screen went black but it still works, and I bought another. I'd like to copy the data exactly with all setting from the old phone to the new one. ADB won't connect, so I guess usb debugging is off. I can't get On Screen Phone to work, so that's not enabled. I can't enable anything because the screen doesn't work. I tried just clicking things, but couldn't enable what I needed to. Is there anything I can do besides copy the internal storage?
lg g2
shaolefen said:
I dropped my LG G2 D802, the screen went black but it still works, and I bought another. I'd like to copy the data exactly with all setting from the old phone to the new one. ADB won't connect, so I guess usb debugging is off. I can't get On Screen Phone to work, so that's not enabled. I can't enable anything because the screen doesn't work. I tried just clicking things, but couldn't enable what I needed to. Is there anything I can do besides copy the internal storage?
Click to expand...
Click to collapse
u can replace old motherboard to new phone.
if display is black that means its the fault of dock port flex cable.
i was facing same issue on my lg g2 d800 i replaced flex cable and its working fine.
kp263 said:
u can replace old motherboard to new phone.
if display is black that means its the fault of dock port flex cable.
i was facing same issue on my lg g2 d800 i replaced flex cable and its working fine.
Click to expand...
Click to collapse
a month earlier my phone screen went black, i can only see the backlight lit. I replaced my LCD and its working fine now. I doubt flex cable has to do anything with the screen going black ? I might be wrong
Two separate questions :
1. Do you have a custom recovery installed? If yes, abd may be pre-enabled when booted into recovery(depending on the recovery used).
2. Is your Phone detected by the LG PC suite? If yes, you can use the "QMove" feature to transfer your data. If you are on Lollipop, this feature doesn't work very well due to security permissions
@shaolefen
If you got stock Android try to use OSP to copy everything over
shaolefen said:
I dropped my LG G2 D802, the screen went black but it still works, and I bought another. I'd like to copy the data exactly with all setting from the old phone to the new one. ADB won't connect, so I guess usb debugging is off. I can't get On Screen Phone to work, so that's not enabled. I can't enable anything because the screen doesn't work. I tried just clicking things, but couldn't enable what I needed to. Is there anything I can do besides copy the internal storage?
Click to expand...
Click to collapse
did you try connecting a mouse via usb/otg?
if you can't click on things using your screen - usb mouse might help...
or you can't see anything on the screen...
60nine said:
did you try connecting a mouse via usb/otg?
if you can't click on things using your screen - usb mouse might help...
or you can't see anything on the screen...
Click to expand...
Click to collapse
The screen actually works. I can click on the screen and hear that it's clicking on something. I just can't see what I'm clicking so I can't enable
@wulsic
Is there any tutorial on how to use that? This is the first I've heard of it.
shaolefen said:
The screen actually works. I can click on the screen and hear that it's clicking on something. I just can't see what I'm clicking so I can't enable
@wulsic
Is there any tutorial on how to use that? This is the first I've heard of it.
Click to expand...
Click to collapse
Sorry for the late reaction, but try this:
https://www.youtube.com/watch?v=ycjGnaK0EB8
you could still try to blindly enable USB debugging just by watching some videos onyoutube to see the settings app, and just scroll down and those steps.
wulsic said:
Sorry for the late reaction, but try this:
https://www.youtube.com/watch?v=ycjGnaK0EB8
you could still try to blindly enable USB debugging just by watching some videos onyoutube to see the settings app, and just scroll down and those steps.
Click to expand...
Click to collapse
Can you use this without "authorization" from the phone? I have the same problem but the phone won't pass from the pin/puk screen and you cannot type the code.
Trompipan said:
Can you use this without "authorization" from the phone? I have the same problem but the phone won't pass from the pin/puk screen and you cannot type the code.
Click to expand...
Click to collapse
Do you also own another g2? If so then you or perhaps if you have a friend could switch the motherboards out so you could enter your passcode and transfer the data to your pc. If you don't have a second g2, or a pc then you could try and this is probably the simplest method. Use an otg and connect a mouse to your g2 and you should be able to control it again. About the pin/puk code. If you can't get acces to your sim, then just eject the sim card and use the mouse to unlock your phone etc. I hope this will help you with your issue.
Verstuurd vanaf mijn LG-H850 met Tapatalk
Hello guys,
I have broken the screen of my Nexus 6P and I really want to save my data before moving to a new phone.
I've found several applications to control phone from PC, but all of them needs USB debugging mode enabled, which is unfortunately disabled on my phone.
I read here on the forum some method to enable USB debugging from PC via USB cable, but I'm not an expert and I can't do it.
My phone is locked by screen lock (PIN code, of course I know the code), and the phone is NOT rooted, OS is the original one (with all the updates installed.)
If any of you guys would be able turn on USB debugging on my phone without losing my data, I will be glad to reward his efforts by $125 and a HUGE "Thank you"! Money will be sent via PayPal, remote session could be done via TeamViewer.
I really hope someone of you can do it!
Thank you in advance!
How is the screen broken?
Is it just not responding to touch? Is the lcd shattered or dead black?
---------- Post added at 12:49 AM ---------- Previous post was at 12:46 AM ----------
If you can see even a little of the screen, grab a usb-c OTG cable ( https://goo.gl/BzUKno ) and use a wired pc mouse to make all entries needed.
InkSlinger420 said:
Is it just not responding to touch? Is the lcd shattered or dead black?
---------- Post added at 12:49 AM ---------- Previous post was at 12:46 AM ----------
If you can see even a little of the screen, grab a usb-c OTG cable ( https://goo.gl/BzUKno ) and use a wired pc mouse to make all entries needed.
Click to expand...
Click to collapse
Unfortunately it is dead black, and not responding to touch.
sawwee said:
Unfortunately it is dead black, and not responding to touch.
Click to expand...
Click to collapse
i have good news for you as other have said you need an otg cable i tested with this one https://www.amazon.com/gp/product/B01COOQIKU/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 and it worked with this mouse and keyboard combo https://www.amazon.com/gp/product/B005DKZTMG/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 im sure other will work but thats what i tested with once it is connected swiping up is a bit hard i was just trying to drag it all the way up at first but to get to the pin screen you will need to do it in a flicking up motion then just you the the number keys on the keyboard and unlock then the next best this is probably to try and cast the screen so your not blind if you cant and you get it unlocked these are the steps ...
1. unlock clicking and swiping mouse up then enter pin and hit enter.
2. down twice on keyboard and then enter to get to app drawer
3. type settings hit enter twice
4. down 11 times enter.
5. down 3 times enter.
6. down 13 times enter right once and enter.
usb debugging should be enabled that is for android 8.0
ps if you dont have developer mode enabled it will be different if so tell me ill count it out for you for that too.
For $125.....
For damn near the cost of the reward, you could get another screen/assembly and swap the guts, having a fully working device again....
billycar11 said:
i have good news for you as other have said you need an otg cable i tested with this one https://www.amazon.com/gp/product/B01COOQIKU/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 and it worked with this mouse and keyboard combo https://www.amazon.com/gp/product/B005DKZTMG/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 im sure other will work but thats what i tested with once it is connected swiping up is a bit hard i was just trying to drag it all the way up at first but to get to the pin screen you will need to do it in a flicking up motion then just you the the number keys on the keyboard and unlock then the next best this is probably to try and cast the screen so your not blind if you cant and you get it unlocked these are the steps ...
1. unlock clicking and swiping mouse up then enter pin and hit enter.
2. down twice on keyboard and then enter to get to app drawer
3. type settings hit enter twice
4. down 11 times enter.
5. down 3 times enter.
6. down 13 times enter right once and enter.
usb debugging should be enabled that is for android 8.0
ps if you dont have developer mode enabled it will be different if so tell me ill count it out for you for that too.
Click to expand...
Click to collapse
Thanks a lot, I'll order it from Amazon and try it. If it works I'll send you the reward, thank you very much again! (P.S. Developer mode is enabled. However I'm not sure if I have Android 7 or 8.0 on my device. Is it different on 7?)
InkSlinger420 said:
For damn near the cost of the reward, you could get another screen/assembly and swap the guts, having a fully working device again....
Click to expand...
Click to collapse
Thank you!
Yes, I saw that for this price I can order another screen, but it takes for a while to receive it and I need some of my data pretty urgently, that's why I prefer a quick solution.
sawwee said:
Thank you!
Yes, I saw that for this price I can order another screen, but it takes for a while to receive it and I need some of my data pretty urgently, that's why I prefer a quick solution.
Click to expand...
Click to collapse
If OEM unlocking is on / bootloader is unlocked, you can try flashing twrp recovery(after unlocking bootloader) and check if files show up on pc (I think MTP mode is on by default in twrp).
Perhaps trying this.
sawwee said:
Hello guys,
I have broken the screen of my Nexus 6P and I really want to save my data before moving to a new phone.
I've found several applications to control phone from PC, but all of them needs USB debugging mode enabled, which is unfortunately disabled on my phone.
I read here on the forum some method to enable USB debugging from PC via USB cable, but I'm not an expert and I can't do it.
My phone is locked by screen lock (PIN code, of course I know the code), and the phone is NOT rooted, OS is the original one (with all the updates installed.)
If any of you guys would be able turn on USB debugging on my phone without losing my data, I will be glad to reward his efforts by $125 and a HUGE "Thank you"! Money will be sent via PayPal, remote session could be done via TeamViewer.
I really hope someone of you can do it!
Thank you in advance!
Click to expand...
Click to collapse
Perhaps you could try this app herehttps://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 and it's self explanatory. There's a setting for you to retrieve files from your phone, as long as you remember the path to those files. Good luck!
without usb debugging.
try adb push/pull or sideload recovery, i think no need for usb debugging to be enabled here.
sawwee said:
Thanks a lot, I'll order it from Amazon and try it. If it works I'll send you the reward, thank you very much again! (P.S. Developer mode is enabled. However I'm not sure if I have Android 7 or 8.0 on my device. Is it different on 7?)
Click to expand...
Click to collapse
It would be different for 7 because in 8 they redid the settings
NoobInToto said:
If OEM unlocking is on / bootloader is unlocked, you can try flashing twrp recovery(after unlocking bootloader) and check if files show up on pc (I think MTP mode is on by default in twrp).
Click to expand...
Click to collapse
Thank you for your suggestion!
I'm afraid I'm not able to do what you described (I'm not an expert at all), that's why I need someone who will help me. Moreover I need not only the files but it would be optimal to get full access to the phone, first of all because I need to use google authenticator. That's why I need usb debugging mode to be turned on so badly.
BenAmirul said:
Perhaps you could try this app herehttps://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 and it's self explanatory. There's a setting for you to retrieve files from your phone, as long as you remember the path to those files. Good luck!
Click to expand...
Click to collapse
Thank you for your suggestion!
If possible, I prefer to be able to turn on usb debugging mode because then I can get full control on my phone and control it from my laptop, not only getting able to save my files. I need it mostly because I need to use Google Authenticator on my phone.
braheem12 said:
try adb push/pull or sideload recovery, i think no need for usb debugging to be enabled here.
Click to expand...
Click to collapse
Thank you for your suggestion, too! Unfortunately I don't really know what do the things you mentioned mean. (I'm sorry, I'm a simple user without any special knowledge about android, so I don't know what is adb or a sideload recovery. That's why I offered a reward for some remote help.) Could you please explain it slightly more detailed?
billycar11 said:
It would be different for 7 because in 8 they redid the settings
Click to expand...
Click to collapse
Thanks! Is there a way to get to know the android version of my phone (in case of black screen)? And... could you (or someone else) please tell me the proper order of key hits for Android 7, too?
Thanks a lot again!
sawwee said:
Thanks! Is there a way to get to know the android version of my phone (in case of black screen)? And... could you (or someone else) please tell me the proper order of key hits for Android 7, too?
Thanks a lot again!
Click to expand...
Click to collapse
Yeah I will he able to test on my Nexus 6 if those keys don't work for you
billycar11 said:
Yeah I will he able to test on my Nexus 6 if those keys don't work for you
Click to expand...
Click to collapse
Thanks a lot, I really appreciate! I'll let you know once I received the OTG cable I've ordered.
Please see this thread here on Xda. It has the commands to enable usb debugging and also control a phone with broken screen. I seen your thread and thought this could help. Good luck & God bless.
[Tool][Windows] Control a device with a broken screen. Now with touchscreen support!!
https://forum.xda-developers.com/showthread.php?t=2786395
billycar11 said:
i have good news for you as other have said you need an otg cable i tested with this one https://www.amazon.com/gp/product/B01COOQIKU/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 and it worked with this mouse and keyboard combo https://www.amazon.com/gp/product/B005DKZTMG/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 im sure other will work but thats what i tested with once it is connected swiping up is a bit hard i was just trying to drag it all the way up at first but to get to the pin screen you will need to do it in a flicking up motion then just you the the number keys on the keyboard and unlock then the next best this is probably to try and cast the screen so your not blind if you cant and you get it unlocked these are the steps ...
1. unlock clicking and swiping mouse up then enter pin and hit enter.
2. down twice on keyboard and then enter to get to app drawer
3. type settings hit enter twice
4. down 11 times enter.
5. down 3 times enter.
6. down 13 times enter right once and enter.
usb debugging should be enabled that is for android 8.0
ps if you dont have developer mode enabled it will be different if so tell me ill count it out for you for that too.
Click to expand...
Click to collapse
I've tried to do it as you described.
1. I successfully unlocked the screen by typing my pin code, I can even hear the audio confirmation (ie. unlock sound). Fortunately I have to do it only once because after the first successfully unlock I can use the fingerprint reader to unlock the screen
2. Once the screen is unlocked, I hit twice the "down" button on the attached keyboard. I think something is going wrong here, because after the first "down" I can hear the audio confirmation (ie. keyboard sound), and after the second one I can't hear anything as if I stepped down on a list which has ended already. Any idea what do I do wrong?
Samuel Holland said:
Please see this thread here on Xda. It has the commands to enable usb debugging and also control a phone with broken screen. I seen your thread and thought this could help. Good luck & God bless.
[Tool][Windows] Control a device with a broken screen. Now with touchscreen support!!
https://forum.xda-developers.com/showthread.php?t=2786395
Click to expand...
Click to collapse
Thanks a lot for your suggestion!
The thread you linked says I should enable usb debugging via recovery using this code:
Code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
Unfortunately I have no idea how to do that.
My $125 reward is still available for anyone who could help me with that via TeamViewer (or any other way.)