I managed to break the screen on my TMO Galaxy S2 last night. It doesn't display anything or register touch. Kies detects the phone but it won't access it because of the lock screen...which I can't unlock.
I've tried going into Recovery Mode, but I'm having trouble finding blind navigation guides for it. The one I found on the forum (for a different S2 model) instructs:
-> Get into recovery mode
-5x down
-enter
-2x up
-enter
Doesn't seem to work. It's for CWM, which I don't believe is installed any more (I was rooted at one point but something glitched and my phone started rebooting constantly, so I unrooted and flashed back to stock). I updated to ICS via Kies about a week ago.
The phone appears as an Unspecified device named SGH-T989 in Windows' device list when I'm in Recovery Mode. In normal mode, it appears with two drive letters, but I can't access either (presumably because I can't get it into USB mode).
Is there a way to bypass the lock screen and access my phone in Kies, or can someone else with a stock phone walk me through the recovery mode menu to mount the internal SD card?
Edited--Nevermind. A friend pointed me to ADB, and after reading a bit, I was able to use 'adb pull /sdcard/ backup' and get all my data while it's connected to USB, right through the lockscreen that stops kies.
Related
Here is my issue..I have been rooted since I got the phone and actually rooted both of my EVO's. Last week I decided to go back to Fresh Rom 1.0 and inadvertently flashed a new theme at the same time. Did not flash the ROM and then go back in and flash the theme. As a result, the phone went into a continual cycle of rebooting the loading screen ( for Fresh users you know it has the little guys and says FRESSSHHH). Well that happens over and over again.
The only option I have is to take battery out and go into the bootloader mode. MY problem is this:
* Once in bootloader mode, I can't reflash because when I go into the recovery mode, the recovery says " ADB server is out date" and scrolls thru a few lines an disappears. I've tried every thing suggested to me and still have not been able to fix that.
* Cannot access root of SD card because system doesn't recognize the phone is attached.
* Tried to load PC36IMG file on the card manually and that loaded but I can't get to the restart option. It finds the file but does not give me the restart commands.
I'm at wits end right now. I tried the OTA Recovery but since I cannot connect to the computer, it won't run either.
Please help......
Restore a nandroid.
RUU start over.
I tried to do that but the computer - htc sync won't recognize the phone so I can't RUU again. When I get to the end of the process it tells me either the phone isn't connected to the USB or the USB isn't connected to the computer.
You phone says the ADB server is out of date when you boot into recovery?
It sounds like you are not completely rooted.
You should be able to volume down and power on. Then choose recovery. From there you can restore a backup. That should also give you ADB access to the phone (if you are fully rooted)
If you are not fully rooted, and you have to run some bat file on your computer to get the phone into full recovery, you may be skrewed.
No, the computer says that when I go into recovery mode and have the black screen and red triangle on it. I then go to the computer and try and run the recovery file that I've been running as I've flashed 10-12 ROMS already. The CMD screen on the computer comes up as ADB Server is out of date...and another line or two scrolls by and then it disappears, never connecting to the phone and going into the next screen where I can wipe or flash from SD..etc..
Sounds like you did not complete step 2 of the root process. You should be able to enter recovery without the use of a computer.
Reboot your computer and try again, if you still get errors then I am out of tips.
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,
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
Without usb debugging turned on, you won't be able that way (or any ADB based way).
You can try to get in recovery and mounting your sd card. (will have to use you other S3 to know how many times you need to go down).
One thing though, even with the PIN to unlock, when the phone is on and plugged to the pc, shouldn't you be able to see the storage?
damn PIN
BWolf56 said:
Without usb debugging turned on, you won't be able that way (or any ADB based way).
You can try to get in recovery and mounting your sd card. (will have to use you other S3 to know how many times you need to go down).
One thing though, even with the PIN to unlock, when the phone is on and plugged to the pc, shouldn't you be able to see the storage?
Click to expand...
Click to collapse
A computer can see the device but when you go into it no drives/shares appear until you enter the PIN in the phone, as soon as you enter the PIN the storage appears with all pics and such.
androidnoob10 said:
A computer can see the device but when you go into it no drives/shares appear until you enter the PIN in the phone, as soon as you enter the PIN the storage appears with all pics and such.
Click to expand...
Click to collapse
Ah ok. Well flashing a ROM will remove the PIN lock so that's another option (stock included).
Never tried, but just a thought: what if you connect USB keyboard through micro USB port, then enable Debugging.
Sent from my SGH-I747 using xda app-developers app
Hi,
My brother's SGH-T989D phone (Koodo / Telus) crashed during an android update. Now, the phone boots to a black screen with the taskbar on top. There is no menu screen anymore. No apps at all. Doing a factory reset via the recovery mode does not change anything.
My PC does not detect the phone. Therefore, I am unable to install a new ROM with Odin. Here are all the infos I have :
1. The phone boots, but there is absolutely nothing except the task bar (I can toggle the wifi and bluetooth on and off, thats it...). There phone says preparing SD storage upon booting. There are no SD card and SIM card.
2. The phone is able to go into recovery and download modes.
3. My PC does not detect the phone. I know the Samsung drivers, Odin v3.07 and USB cable are working properly because I am able to connect my own phone which is also a SGH-T989D.
4. In recovery mode, there is a dead android with a red triangle with an "!" in the background.
5. It used to have the stock gingerbread Koodo ROM, and was probably updated over the air to the newest ICS from Koodo.
6. The phone was never rooted or messed with. I don't think it was ever connected to a computer before.
7. It is not under warranty anymore.
I've spent hours trying to get it recognized by the computer. I've tried putting the ROM on the SD card and applying the update via external storage in recovery mode. I get a message about Signature verification failure.
I've tried cleaning the micro-usb slot. Blowing in it resulted in the computer saying "Unknown device malfunctioned" a single time, which leads me to believe it only did that because some saliva created a short somewhere in there. The connections look clean.
I'm about to throw this phone off the building. What is wrong with it?
**EDIT**
Forgot to mention...the phone does charge when connected to the usb cable.
kamikazee1989 said:
Hi,
My brother's SGH-T989D phone (Koodo / Telus) crashed during an android update. Now, the phone boots to a black screen with the taskbar on top. There is no menu screen anymore. No apps at all. Doing a factory reset via the recovery mode does not change anything.
My PC does not detect the phone. Therefore, I am unable to install a new ROM with Odin. Here are all the infos I have :
1. The phone boots, but there is absolutely nothing except the task bar (I can toggle the wifi and bluetooth on and off, thats it...). There phone says preparing SD storage upon booting. There are no SD card and SIM card.
2. The phone is able to go into recovery and download modes.
3. My PC does not detect the phone. I know the Samsung drivers, Odin v3.07 and USB cable are working properly because I am able to connect my own phone which is also a SGH-T989D.
4. In recovery mode, there is a dead android with a red triangle with an "!" in the background.
5. It used to have the stock gingerbread Koodo ROM, and was probably updated over the air to the newest ICS from Koodo.
6. The phone was never rooted or messed with. I don't think it was ever connected to a computer before.
7. It is not under warranty anymore.
I've spent hours trying to get it recognized by the computer. I've tried putting the ROM on the SD card and applying the update via external storage in recovery mode. I get a message about Signature verification failure.
I've tried cleaning the micro-usb slot. Blowing in it resulted in the computer saying "Unknown device malfunctioned" a single time, which leads me to believe it only did that because some saliva created a short somewhere in there. The connections look clean.
I'm about to throw this phone off the building. What is wrong with it?
**EDIT**
Forgot to mention...the phone does charge when connected to the usb cable.
Click to expand...
Click to collapse
IDK if this will help you. IF the phone isn't rooted or a custom recovery installed I don't believe you can reinstall the ROM. It does say 'signature verification error' so you might be able to turn off MD5 checking before install. It will be in the settings menu if TWRP is used. I don't believe its an option to do if on stock recovery.
I found, after months of searching, a customized recovery (TWRP 2.8.7.0) for my Tab, and the Android SDK (ADB & Fastboot).
I backupped all of my files and things, and I wiped everything out (accidentally).
Now, my Tab can access Recovery, but when I try to copy a ROM into it's internal storage, after some minutes it exits automatically (I turned the Screen Timeout off), failing the copy operation and not giving any option to restart it at a later time (dumb Windows), and no ROM that I have seen so far is small enough (100-200MB) to copy before the Recovery auto-closes. My USB picks it up (but only for accessing through Windows - Fastboot and ADB don't pick it up).
My Android version is 4.1.2, and I haven't tried many methods apart from Kies (does not detect anytime) and the ones descripted here. The Tab can't charge, and I have 86% battery. I believe that the Samsung firmware is too big for the auto-exit cycle.
However, it can access Download Mode but the USB nor the computer respond, and ADB & Fastboot either.
When I start my Tab up, it gets stuck in the bootloader screen, and Odin (v3.09) shows 1 "Added!!!" message, but I can't do anything with the PC/Tab connection.
So my Tab is stuck until I can find a 100-200MB rom that can be copied without the Recovery shutting down automatically.
Can anyone help me out?
Fixed, installed Odin 3.07 and it somehow made the recovery not close itself, so I flashed RocketTab 3.0!
I have a non-rooted VS986 (probably 26A).
Recently I ran out the battery and the phone died. When I charged it and turned it back on, it stayed stuck at the Verizon boot screen.
I hadn't really changed anything recently, and I did not take the most recent OTA (27C) so this just seems like a random hardware failure.
I can boot into Recovery, but if I choose "Safe Mode" or "USB Debug Mode" the phone just hangs at the Verizon Screen.
I tried to Wipe Cache and restart, but it just hangs at the Verizon screen.
I *can* boot into Download mode.
I would really like to back up the internal SD card--photos, settings etc. if possible.
Is there anything I can do at this point just to get an ADB prompt or something that might allow me to perform a backup (even if limited)?
Sounds like a motherboard failure. You could try booting into download mode and using adb to pull your files but you'll have to know the exact path to their location. And to do that you would have had to have USB debugging activated.
If that doesn't work then your SOL. Time to use your insurance or warranty if it's still good.