A friend has a stock S7 with a broken screen and USB debugging disabled.
I have read posts here about this situation and it looks like the prognosis is bleak, but it has been more than a year since the last one I found, and things do change with time as more is learned, especially on popular phones like the Galaxy line, so it seemed like a good idea to ask again. His wife has baby pictures on it that are worth a good bit to them. Why they weren't backed up to the cloud is anyone's guess - I get that some folks dislike sharing private lives with Google, but there are plenty of Boxcryptor type apps one can use - but the point is moot. They have their privacy and no baby pictures. It is what it is.
A quick Google search finds lots of proprietary software that claims that it doesn't need USB debugging to be enabled or that it can enable it, but the sparse details provided about this superhuman ability makes this seem unlikely.
Someone mentioned a way to sideload a custom kernel in order to somehow enable USB debugging via ADB. Is this possible? Can USB debugging be enabled from stock recovery on the S7, or any other route?
There are all sorts of Octopus / Miracle Box type gadgets and software packages that claim to make various phones dance and sing, but I can't find one that will recover files from the S7. It might be worth buying such a package, if it existed.
Some posts, articles and videos suggest using an OTG to connect a mouse or keyboard and navigate the broken screen, either from memory or by taking screenshots and retrieving them from phone storage. We have not tried this yet, and any tips specific to the S7 would be really appreciated.
Someone posted an application here, that is apparently intended to help with this situation, but mirroring a phone screen requires USB debugging to be enabled.
https://forum.xda-developers.com/showthread.php?t=2786395
Thanks to anyone who might be able to help, and I apologize for adding a redundant question. I am just hoping that there is something new in the Galaxy world that might have made this situation salvageable.
SmilingPerson said:
A friend has a stock S7 with a broken screen and USB debugging disabled.
I have read posts here about this situation and it looks like the prognosis is bleak, but it has been more than a year since the last one I found, and things do change with time as more is learned, especially on popular phones like the Galaxy line, so it seemed like a good idea to ask again. His wife has baby pictures on it that are worth a good bit to them. Why they weren't backed up to the cloud is anyone's guess - I get that some folks dislike sharing private lives with Google, but there are plenty of Boxcryptor type apps one can use - but the point is moot. They have their privacy and no baby pictures. It is what it is.
A quick Google search finds lots of proprietary software that claims that it doesn't need USB debugging to be enabled or that it can enable it, but the sparse details provided about this superhuman ability makes this seem unlikely.
Someone mentioned a way to sideload a custom kernel in order to somehow enable USB debugging via ADB. Is this possible? Can USB debugging be enabled from stock recovery on the S7, or any other route?
There are all sorts of Octopus / Miracle Box type gadgets and software packages that claim to make various phones dance and sing, but I can't find one that will recover files from the S7. It might be worth buying such a package, if it existed.
Some posts, articles and videos suggest using an OTG to connect a mouse or keyboard and navigate the broken screen, either from memory or by taking screenshots and retrieving them from phone storage. We have not tried this yet, and any tips specific to the S7 would be really appreciated.
Someone posted an application here, that is apparently intended to help with this situation, but mirroring a phone screen requires USB debugging to be enabled.
https://forum.xda-developers.com/showthread.php?t=2786395
Thanks to anyone who might be able to help, and I apologize for adding a redundant question. I am just hoping that there is something new in the Galaxy world that might have made this situation salvageable.
Click to expand...
Click to collapse
Try the solution in the link you've posted, i'm sure you no longer need debugging enabled.
Also the real issue is you need to unlock the phone, so if the screen is just black?? You can usualy guess where the patterns or numbers appear etc, easy if you have another s7 next to it.
Also other options here
cooltt said:
Try the solution in the link you've posted, i'm sure you no longer need debugging enabled.
Also the real issue is you need to unlock the phone, so if the screen is just black?? You can usualy guess where the patterns or numbers appear etc, easy if you have another s7 next to it.
"]here [/URL]
Click to expand...
Click to collapse
Thank you! This is very helpful.
I think debugging must be enabled for that solution, but I hadn't read far enough or close enough to find Msmtx's solution for enabling it from ADB.
https://forum.xda-developers.com/showpost.php?p=66731042&postcount=260
My blind spot now rectified, I am going to give this a try. I know nothing about stock recoveries - is the one in the S7 going to allow me to do this, or will I have to install or boot TWRP or Safestrap?
Thanks again mate, it will be great to get those pics back. I just hope they have learned from this the great value of backups...
Sent from my unknown using Tapatalk
Hi @SmilingPerson - Did you get this resolved? I'm facing the same issues, and on top of all the OTG ideas, the phone I need to access has a swipe lock, so I'm pretty sure connecting a mouse without seeing anything is useless. Would appreciate any tips.
I wish I could tell you something, but nothing worked, sadly, and I used the old phone for parts.
Good luck though, hope you fare better than I.
Related
First things first This Forum has a LOT of different places to post so if this is in the wrong place please dont yell at me, just kindly assist me in moving it to the appropriate location. I think once we get this solved it might be a huge step for the Android community.
OK So long story short G2's digitizer is dead, glass shattered, i can still see the screen and i'm getting a USB OTG cable tomorrow, that will make all of this completely null and void(maybe wednesday). (ALSO Caps is being used for things i think are important, i'm going to be posting this in a few places so i need it to be universal, i hope you all understand)
BUT i still want to try my damndest to get into this phone and backup files, JUST BECAUSE I BELIEVE I SHOULD BE ALLOWED TO.(or at the very least "able")
So for those as adventurous as i am, I'd like to hear any suggestions on how to get access to the device (MOUNT STORAGE) in its current state. Details below:
-Sprint ls980
-Digitizer is shattered
-lcd is completely fine
-all buttons work (theres only three lol)
-i have sound and vibration
-wireless storage is off(turned it off right before it fell from my hands to the douchebag floor below)
-USB DEBUGGING(although i distinctly remember enabling it many times) Is NOT ON. (Or at least adb will not recognize the device.)
-adb WILL recognize the device in SIDELOAD MODE
-no custom recovery
-no custom roms
-literally purely stock
-And of course USB Connection is set to CHARGE ONLY(i didnt do this, but apparently it remembers your LAST choice and uses that as default, stupid lg, why let me chose the option to "ask every time", if you're going to default to my last choice anyway?)
Now i really just want to access my pictures(there's a pic of my mom that i took and she REALLY wants it and bugs me daily about it)(You can blame the G2's amazing camera)
Now here's what i HAVE TRIED:
-ADB
-moborobo sp? (some program)(and a few others like it)
-android control
-fastboot
-download mode
-tried making my own OTG cable....failed miserably (i'd upload a pic...but yea...)
-adb via wifi
-tried flashing a custom recovery, but USB debugging wasnt enabled so it failed
-_-
-had the idea of using chrome Remote desktop, but i cant connect to it in its current state lol
-thought about bluetooth, but my lame laptop doesnt have bluetooth (i'd be willing to explore this option tho, sounds fun)
-nothing "illegal"......yet.....totally kidding, i want to be able to do this as legally as possible
So brothers and sisters, does anyone have any options they'd like to try out?
If we try anything CRAZY is there a way to force the phone to make a backup?
Is there a way to disassemble the phone and connect it straight to the onboard storage?
i'm just throwing ideas out there.
Thanks in advance!!
and yes i'm a new poster, but i've been lurking on these forums since 2010
And i'll add this, because i know someone is thinking it right now, "Why didnt you root your g2?" Simple answer is this:
I wanted to experience Android in its most Basic state, Getting people to move from any other platform to Android is not easy, When you show them your modded out custom g2 it scares them, but the second they see my phone completely stock and realize how great Android is they start regretting their iPhone purchase or even heir midrange Android purchase. My [email protected] and Nexus 7 in their "Vanila" state have Wowed many people and converted longtime iphone users. Solving this problem would only aid in that effort.
Thanks again guys.
Is there a way to move this to the Developers forum? i'm sure they've got some ideas
Right then. First things first, I apologize if I don't use the proper lingo associated with everything; I'm as super nooby as can be.
So, here's my problem: My rooted, Samsung Galaxy S3 has had it's screen shattered and its digitizer broken. The screen is completely black and the touchscreen does not respond. It didn't have a password (it was just swipe to open), which I suppose makes things easier, though. The phone itself still turns on, and I receive notifications and all that, but I am completely unable to do anything about. I understand that I am able to view and operate an Android phone through my computer, so I was hoping that'd work. Well, as the title of this topic hinted at, I didn't USB debugging enabled on my phone, which pretty much every program I found requires. So, I searched around, and learned that ADB can activate USB debugging through a usb cable and some tech magic. Unfortunately, I am not a tech magician and the articles I found were hieroglyphics. I spent some time reading, researching, reading researching, but it still doesn't make sense to me. I have ADB installed, but I don't know how to use it at all. I can launch "adb.exe" in administer mode but nothing occurs. I'm wondering if anyone would be able (or want to) explain to me, preferably step-by-step on how to enable USB debugging be it through ADB or some other, miraculous technique.
For anyone interested, these were the articles I looked at:
http://forum.xda-developers.com/showthread.php?t=1725858&page=2
http://android.stackexchange.com/qu...ndroid-if-forgotten-pattern-for-screen-unlock
http://android.stackexchange.com/questions/120394/can-i-enable-usb-debugging-using-adb
http://android.stackexchange.com/qu...bug-mode-was-disabled-how-can-i-re-enable-adb
http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
http://developer.android.com/tools/help/adb.html
http://forum.xda-developers.com/showthread.php?t=2786395
Hey dude, what you are talking that can enable USB Debugging from ADB is possible only on custom ROMs. But on stock ROM this is not possible.
Forgive me as there may be a simple solution for SDK to detect it, been many years since I've messed with any Android devices to this extent. I bought an LG Stylo G at a flea market. Of course it's FRP locked. Reset, tried all the superficial ways of bypassing (including the TalkBack one, never presented with the "feedback" option to get outside of the menu, and don't have a Google Keyboard). Installed SDK Manager, installed LG drivers, adb can't detect, PC doesn't even seem to detect. I have no way to enable USB debugging, and presented with no options upon plugging in the phone to PC.
Did recent updates prevent any way around this entirely? Maybe if I'm lucky I can re-sell it for what I paid for it at least, but I'd like to try and get into it.
Have you found a solution to your issue... If not I may be able to help but I will need more information
im in the same boat
SoonersChuck said:
Have you found a solution to your issue... If not I may be able to help but I will need more information
Click to expand...
Click to collapse
what kind of info do u need\ i cant get anywhere with it
I was fortunate to have my MS631 back when Android was at 5.1.1 I didnt have to even hook it to a PC. they changed it on 6.0.1 but it was still possible. Im actively searching thru all my software i finally had some of my stuff returned to me from my ex. only took 3 years, but who's counting? LoL.
you might find yourself sitting messing around on accessibility options. i think there is still a small exploit you can bypass frp you just gotta be connected via WiFi . somewhere in the settings you can find terms of Service agreements and stuff...if you scroll thru these and you happen across a url (doesnt matter what url) click to get a web browser to come up, if you get that, stay in browser. do a search via browser searchbar for settings.
it should suggest a local apk. click on it and you should be on the other side of the door and behind the frp lock.
first thing you gotta do if find system apps like google one time init. and go in and disable it. there are a couple others i am pretty sure . Disable phone admins as well. i hope this helps... and i hope like hell i am giving you information
This is the video I used to get past FRP on mine.
Its in arabic but just do everything he does and it should work.
Background: my wife arrived home yesterday with a Samsung Galaxy Tab A 10.1 2016 model (SM-P585) that had been written off by her company due to lockscreen protection being enabled and no one knowing who the last person was that it was issued to.
I kid you not.
Anyhow, one quick Odin flash later and it's booting up happily. However, FRP was enabled and now requires sign-in from the last person to have signed in on it, which is unknown. So I find myself one last step away from an awesome - and surprisingly well looked after - tablet but with no idea of what to do about FRP.
I've done a fair amount of reading and, outside of all those sites that seem to be run by the same Asian gent who is adamant I can only do it with his absolutely-not-suspicious-at-all application, understand that I can either flash 1) a combination file or 2) an old firmware in which the old workarounds are still effective, both of which will allow me to bypass it, but neither of which will work without USB debugging enabled and that can only be done via the developer options. And obviously I can't get to that.
If anyone has any advice on how I can make this work in my favour without having to get rid of it, I would sincerely appreciate it.
Alternatively, if this is the wrong place to post this question, a quick point and a kick in the ass in the right direction.
[Quick edit] I have no issues with rooting if that's what's required. Again, requires developer tools so...
Hint: Add " SM-P585 " to front of this thread's titel thus mainly people who owns such device get addressed, too.
I thought of that, but I don't believe this is an issue limited to my specific device model. I think it could apply to most, if not all, Android devices at some point.
Hello,
Recently a friends son passed away and the family wants to recover whatever is in his phone including his last text messages and phonecalls.
Xiaomi only offered a full wipe which cannot happen even though the phone and receipt is on his mother's name ( the person who currently has the phone).
I'm uncertain if the phone has USB debugging turned on as I havent got it in my hands yet, trying to gather as much info as I can before I try anything on it.
The family also has a second Poco x3 so the idea was to try anything I find on the 2nd phone first to make sure it doesnt wipe.
It is locked with a pattern and face recognition, but they told me it doesnt ask for the face recognition unless its turned off and on again so they keep it charged at all times to prevent that from happening for obvious reasons.
Any ideas or ways or direction is welcome and very much appreciated.
Doesn't matter if phone has USB debugging turned on, you need to actually allow access from inside the phone to allow debugging on untrusted machine. Sorry, don't think there is any way, unless you know the password, or maybe try to face unlock by pointing the phone at a picture of their son? Don't know if this will work.
Popletenec said:
Doesn't matter if phone has USB debugging turned on, you need to actually allow access from inside the phone to allow debugging on untrusted machine. Sorry, don't think there is any way, unless you know the password, or maybe try to face unlock by pointing the phone at a picture of their son? Don't know if this will work.
Click to expand...
Click to collapse
The picture is worth a try. Theres also a google recovery thing when you fail multiple times on the pattern to answer a secret question, so im hoping that he put an easy one so the family can figure it out. Thanks for your suggestion