S3 screen is totally dead including touch. We cannot enter the PIN to unlock the device due to dead screen. We need to get the pictures from the internal SDcard/built-in storage.
We tried booting into recovery mode (we used another S3 to test the timing since we can't see the screen). Once in recovery mode we used the Samsung Galaxy S3 Toolkit, it recognizes the device/serial number but trying to pull data it says "waiting for USB debugging" - how can we get past this?? I even tried with a working S3 and even in recovery mode it still says waiting for USB debugging.
How can we get to the files?
Thank you,
But you're in a galaxy s4 forum. Or i probably need my coffee.
Sent from my Nexus 4 using xda app-developers app
androidnoob10 said:
S3 screen is totally dead including touch. We cannot enter the PIN to unlock the device due to dead screen. We need to get the pictures from the internal SDcard/built-in storage.
We tried booting into recovery mode (we used another S3 to test the timing since we can't see the screen). Once in recovery mode we used the Samsung Galaxy S3 Toolkit, it recognizes the device/serial number but trying to pull data it says "waiting for USB debugging" - how can we get past this?? I even tried with a working S3 and even in recovery mode it still says waiting for USB debugging.
How can we get to the files?
Thank you,
Click to expand...
Click to collapse
I hope you dont mean s4 and you already broke it
Related
I'm having the following problems with my TAB and would like to know it's fixable. I treid almost everything to fix it without success. I'm hoping someone can help me. Anyone have these problems before?
1. Doesn't charge normally. It would charge but charge really slow like it's connected via us. It shows an x next to the lightening icon when I charge it using the original charger and cable.
2. I cannot go into recovery mode. I get the black screen with the white line. There's also no boot animation when it boots up.
3. The camera doesn't work. I get a fail message when I open it.
4. My computer doesn't detect it in download mode, kies or mass storage. My computer detect my samsung galaxy s i9000 without any problems so I know it's not the computer. I cannot change the firmware because my computer doesnt detect it.
5. I dont have the receipt to do a warranty repair. What are my other option?
AT&T SGH-i987
Firmware 2.2
Baseband P1000XXJHA
Kernel 2.6.32.9 [email protected] #19
Build XXJMA
Any help is much appreciated! Thanks!
Did you register your Tab with Samsung?
If so, they have a record of your purchase and will be able to provide support.
If not, then try this which I got from their online chat: Hope it helps.
"Kyle: To recover the device via the hardware keys, do the following:
Kyle: 1. Power off the handset.
Kyle: 2. Hold the Vol Down Key + Vol Up Key + Power Key for 15 seconds then release.
Kyle: 3.When the recovery screen comes up, use the volume up key and volume down key to navigate through the selections and the power key to select item.
Kyle: 4. Select Delete all user data to recover the device. To confirm, scroll down and select Yes – delete all user data. The phone reboots and again displays the recovery screen.
Kyle: 5. Select Reboot system to restart the handset again. "
Thanks but I cannot get to that recovery screen like I said above. All I get is a black screen with a white line when I try to go into recovery mode. I also purchase this used with no receipt.
U just need to flash a working rom. Try roto jm... in the dev forum
Your tab was modified. I wont blame Samsung if they wont fix it for u
Sent from my SGH-I987 using XDA App
How do i flash to a different rom if a computer wont detect it?
Do you have the latest kies installed? Is USB Debug on? If it still doesn't detect, have you tried android-sdk or heimdall. Each comes with usb driver. I find it hard to believe your PC doesn't detect the tab. I never heard such thing before unless you're the real first victim then...yeah, try to call Samsung and pay a fee.
Yes, I tried to use android-sdk and heimdall but they don't detect my TAB for me to do anything. I also installed the newest KIES software. I also don't understand why it doesn't detect it in download mode. This is the first time I encounter this problem. I flashed my Galaxy S I9000 phones many times without a problem. Is the combination of the firmware and kernal I have that is causing my computer not to detect the TAB?
Is there a way to root my TAB via an APK? I tried Z4Root but it's not working. It tries to acquirer shell and closes after a few vibrate. yes, debugging mode is on.
starbuck123 said:
Yes, I tried to use android-sdk and heimdall but they don't detect my TAB for me to do anything. I also installed the newest KIES software. I also don't understand why it doesn't detect it in download mode. This is the first time I encounter this problem. I flashed my Galaxy S I9000 phones many times without a problem. Is the combination of the firmware and kernal I have that is causing my computer not to detect the TAB?
Is there a way to root my TAB via an APK? I tried Z4Root but it's not working. It tries to acquirer shell and closes after a few vibrate. yes, debugging mode is on.
Click to expand...
Click to collapse
You've followed Heimdall's README and installed the included driver? Make sure you follow the instructions exactly.
If you have done that and your device still isn't recognised consider trying a another cable, USB port or entirely different PC.
Benjamin Dobell said:
You've followed Heimdall's README and installed the included driver? Make sure you follow the instructions exactly.
If you have done that and your device still isn't recognised consider trying a another cable, USB port or entirely different PC.
Click to expand...
Click to collapse
Thanks for your advice but I already tried above. I didn't have any problems/trouble connecting my Verizon Tab and Galaxy S phone to the computers to change the roms. There is most likely something wrong with the Tab. I gave up and contacted Samsung yesterday. I sent the Tab to them yesterday and hopefully they won't charge me to fix it.
I ran over my phone and broke the screen on my s5. It will boot up and everything works accept my screen is black, digitizer is not responding to finger touch. My phone didn't have a passcode only swipe to unlock. Its running Marshmellow OS. When I connect to kies it reports the phone is locked and I need to enter the passcode on the device. I used "findmymobile" to unlock the phone and I can hear it unlock but Kies still says its locked. Can someone please help?
Try this
http://forum.xda-developers.com/showthread.php?t=2786395
unfortunately I do not have USB bugging on. This is going to be challenging but I'll give it a try
If you put a new screen on the phone you won't loose your data, just get a new digitizer.
Sent from my SM-N910V using Tapatalk
yeah but the digitizer is like $150 CAN, Are there cheaper ones available?
Read a post on another forum saying someone with the same problem, USB Debugging disabled and broken screen, managed to backup by booting the phone in recovery mode / safe mode, and using KIES to create a backup
Recovery mode
http://wccftech.com/galaxy-s5-recovery-mode-how-to/
Hey everyone,
I drove into a big issue with my sister’s phone. The phone is a Samsung Galaxy S5 NEO (SM-G903F). Some days ago, I did root the phone of my sister. Everything was allright and worked afterwards. I just had to unlock the OEM lock in the developer options. Additionally, I flashed a custom recovery from “TWRP”. To that point everything did just worked fine as it should be. Now we come to the issue. My sister accidently hit the OEM lock button. Now she can’t boot the phone anymore as the phone shows the message: "Custom binary blocked by FRP lock". Also, if I try to go into the recovery system the message pops of with: "Custom binary blocked by FRP lock" and "Recovery is not seandroid enforcing"! If I turn on the power button or either go into the recovery, I can see the start samsung boot display for 3 seconds after that the phone shuts down automatically. On top on all of that, the phone generally has an overheating issue as it gets really easy very hot and closes application automatically. Now the only options I thought I have is to go into the download mode and connect the phone via USB to “Odin” to flash a new firmware. Easy as it is I started “Odin” on the pc went into the download mode, plugged the USB cable into the pc and waited for the "added" message. Unfortunately, nothing popped up. Therefore, I tried all different cables (Original Samsung, Multi-USB and cables from other phones) on the pc but still no "added" message. After that I tried 3 different PC's even a MAC, I tried all cables on all PC's but it didn't worked. Also I tried it on diffrent USB-Ports. I checked the Device-Manager and also there couldn't find the phone anywhere. I installed “Kies”, tried to somehow connect the phone and installed new drivers. Really nothing worked... I am just not sure if the USB-Debugging button was checked or activated in the developer options or not. Anyway, I guess it shouldn't matter as it should connect in download mode the phone via usb. I really do hope someone is out there who can help me or might has a good tip/advice for me except something like: "You tried already everything", "There is nothing you can do" or " You can throw your phone away".
Thanks in advance.
Kind regards,
Cossack007
Cossack007 said:
Hey everyone,
I drove into a big issue with my sister’s phone. The phone is a Samsung Galaxy S5 NEO (SM-G903F). Some days ago, I did root the phone of my sister. Everything was allright and worked afterwards. I just had to unlock the OEM lock in the developer options. Additionally, I flashed a custom recovery from “TWRP”. To that point everything did just worked fine as it should be. Now we come to the issue. My sister accidently hit the OEM lock button. Now she can’t boot the phone anymore as the phone shows the message: "Custom binary blocked by FRP lock". Also, if I try to go into the recovery system the message pops of with: "Custom binary blocked by FRP lock" and "Recovery is not seandroid enforcing"! If I turn on the power button or either go into the recovery, I can see the start samsung boot display for 3 seconds after that the phone shuts down automatically. On top on all of that, the phone generally has an overheating issue as it gets really easy very hot and closes application automatically. Now the only options I thought I have is to go into the download mode and connect the phone via USB to “Odin” to flash a new firmware. Easy as it is I started “Odin” on the pc went into the download mode, plugged the USB cable into the pc and waited for the "added" message. Unfortunately, nothing popped up. Therefore, I tried all different cables (Original Samsung, Multi-USB and cables from other phones) on the pc but still no "added" message. After that I tried 3 different PC's even a MAC, I tried all cables on all PC's but it didn't worked. Also I tried it on diffrent USB-Ports. I checked the Device-Manager and also there couldn't find the phone anywhere. I installed “Kies”, tried to somehow connect the phone and installed new drivers. Really nothing worked... I am just not sure if the USB-Debugging button was checked or activated in the developer options or not. Anyway, I guess it shouldn't matter as it should connect in download mode the phone via usb. I really do hope someone is out there who can help me or might has a good tip/advice for me except something like: "You tried already everything", "There is nothing you can do" or " You can throw your phone away".
Thanks in advance.
Kind regards,
Cossack007
Click to expand...
Click to collapse
hey!
don't panic try thisfirst update the samsung usb drivers. then try to restore the phone with the original samsung smart switch software (grab it here)
first of all, i'm sorry if i'm posting this o the wrong section (i'm new here seeking help)
second, I NEED HELP!
i tried using Dr. Fone for recovery and unlock but i'm getting "flash recovery packaged failed" on the end. when on recovery device mode, i can hear the new device/unplugged sound.
if only i can use OTG and mouse to enable USB debugging. but obviously i cant see. when i open the phone normally and try using screenshot, i can hear the sound. so that means that my phone is not dead and only have broken lcd/screen. i also cant open the device folder because its locked (i think its locked). i also looked some class a ldc/screen digitizer but its kinda expensive and going to technician doubles the cost. from this point, i don't know what to do anymore. i just want to get important pictures and video. been trying to find a solution for hours.
I have not seen a method to enable USB debugging without a working screen.
Im an Idiot. I went to twrp recovery and wiped everything, since I wanted to install a higher version of the Samsung tab e, and even when twrp told me that there was no OS installed, I rebooted anyways. I was new to this all thing, and had no idea what exactly that meant and thought, 'What could go wrong?' . . . I just wanted a higher device model, man.
Ugh. Now im stuck in the 'Powered by Android' logo screen, and cant boot into recovery or Download mode.
- What's even worse was that I didn't even enable USB Debugging so Adb is out.
- However, it is Rooted, if that even helps.
- Trying to use the Samsung 300k tool to force enter download mode ends up with 'Write file function failed (error 995)'
- My sibling has the same device model as me, but using T Flash via Odin and my 32GB micro SD card doesn't have a reaction to my device. (Or maybe im doing it wrong, since I don't see anything in the sd card when I plug it to the computer)
- Tablet gets recognized via Odin and Computer, but only as 'MTP USB Device', and in Devices, it is in Unspecified as 'Samsung Android'
- Only good thing that came out of this was the info that I had obtained over the past few days that has shocked my siblings as to why I have this much knowledge over Samsung devices and its functions (AKA I feel cool)
But honestly, at this point I am at a loss of what to do, and will not be surprised if I have to get a USB jig to force it to download mode (my only other option left), or take it to a service center to get it fixed. (the other option I have)
But if there is something you guys are aware of, that I had not tried yet, Please guide me.
Anybody?
norakana said:
Anybody?
Click to expand...
Click to collapse
The simplest way to get an operating system again is to put the ZIP file on a working MicroSD card and put it in your tablet, Then boot into the boot loader and choose to install the file by choosing the external micro sd card.
If you're stuck on a boot screen or download, get out of it by holding the power key + volume down, until the tablet resets.
Note for the future:
always backup your device to an external MicroSD card before deleting your existing operating system, or installing a new one.