[Q] Broken screen / debug off - T-Mobile Samsung Galaxy S II SGH-T989

Hi folks, I've searched and have gone what seems like the right direction but ultimately am stuck.
My mother dropped her phone, screen is cracked and it is PIN locked with debug mode not enabled.
ADB will not show any devices when phone is powered up regularly, but will show devices when I put the phone into recovery mode.
I am somewhat familiar with linux command line but it will not allow me to mount any partitions from the adb shell when it's in recovery.
This is somewhat urgent since she got a new/refurb phone through the insurance and they want the broken one within 10 days or they will bill her tmobile account.
The contents of the phones internal sdcard is what I'm after, there are pictures/videos of my recently deceased grandfather.
What step(s) am I missing? adb shell won't let me mount the sdcard partition or run su so i can try and mount it myself while in recovery.
please help, thank you in adance.

figured it out.
jay4reals said:
Hi folks, I've searched and have gone what seems like the right direction but ultimately am stuck.
My mother dropped her phone, screen is cracked and it is PIN locked with debug mode not enabled.
ADB will not show any devices when phone is powered up regularly, but will show devices when I put the phone into recovery mode.
I am somewhat familiar with linux command line but it will not allow me to mount any partitions from the adb shell when it's in recovery.
This is somewhat urgent since she got a new/refurb phone through the insurance and they want the broken one within 10 days or they will bill her tmobile account.
The contents of the phones internal sdcard is what I'm after, there are pictures/videos of my recently deceased grandfather.
What step(s) am I missing? adb shell won't let me mount the sdcard partition or run su so i can try and mount it myself while in recovery.
please help, thank you in adance.
Click to expand...
Click to collapse
Luckily I have the same model phone so I was able to accomplish the following with some sort of sense of what I was doing. I hope this is useful for others.
You will need odin installed and running on your PC. Also you will need a compatible clockworkmod recovery image in tar format (I found odin and the usable clockworkmod recovery in these forums by searching)
Turn phone off, hold volume up & down at the same time and plug in USB cable into phone (continue holding volume up & down 2 seconds after phone vibrates and release).
Press volume up to confirm odin download mode, phone will go into download mode and odin should detect your phone. click PDA and select the clockwork recovery tar, then click start(let it do its thing till odin says successful, disconnect USB cable)
Phone will reboot, remove battery and reinsert then hold volume up and down while pressing the power button (two seconds again), it takes roughly 15-30 seconds for it to completely boot into recovery mode.
Press volume up twice then the power button once. (This is the mounts and storage menu)
Press volume up twice then power button once. (This is mount USB storage)
Now connect USB cable and USB mass storage should pop up (if using Windows)
I used clockworkmod recovery touch 6.0.1.5 so it may be different with other versions.

Related

Need urgent help accessing data on my rooted t989 with broken screen

My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
So the display is damaged but the digitizer is fine correct? As for data just pull files with adb....I believe you can do that unless you never had USB debugging on
Sent from my SGH-T989 using Tapatalk
CptCrackers said:
My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
Click to expand...
Click to collapse
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
I have been in usb debugging. It may be in usb debugging mode right now.
When I connect it, it shows the drive, but they show as empty. Which is the same thing that happens on my GS4G when it's in debugging.
If you could tell me how to go about extracting files, that would be great, assuming there is even a way.
Is the digitizer the touch portion of the touch screen? If so, then no, that's not working. The phone boots, it receives texts, makes other sounds like it's working, but the screen is black. The LCD is cracked, and it will not accept touch input. I have haptic feedback on and it's definitely not letting me attempt to do the unlock screen.
slm4996 said:
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
Click to expand...
Click to collapse
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
CptCrackers said:
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
Click to expand...
Click to collapse
To get into recovery, pull your battery then put it back in, then hold both vol up and vol down and hit the power button.
Type "help" without quotes in ADB to get a list of commands.
Sent from my SGH-T989 using xda premium
try this http://forum.xda-developers.com/showthread.php?t=628138
It got me out of a jam once on my vibrant, when the same thing happened to me and needed some pictures for my work. USB debuggin has to be on though.
To backup the data from a damaged phone using ADB:
1) Enter Recovery mode:
Turn the phone off, remove the battery. Insert battery, hold volume up AND down while turning on. Plug in usb cable.
2)Open up your terminal/console. Enter the following commands (one command per line, press enter after each)
(this backs up the entire data partition)
Code:
mkdir phoneDataBackup
adb shell mount data
adb pull /data phoneDataBackup
You now have a copy of your phones /data folder, this contains the settings and data from your apps. Get a new phone and then install you app on it. Once you do that simply put the correct named folder from the phoneDataBackup back into your new phones /data folder.
Code:
adb push phoneDataBackup/data/com.rds.itsabouttime /data/data/
This should work just fine for you, I assume you already have ADB installed or can install it first.
THANKS ALL!!!
I am currently using the suggested Android commander to dump everything out of the phone. Lucky the usb debugging got left on when I was cleaning out bloatware last week!!!
Once it's done, or if even if it doesn't work, I'll be playing with the adb connection since it's not like I can break the phone worse... good learning opp!
Thanks for all the tips from everyone.
Quick update, and info in case someone later finds this thread in a search. The android commander did get back what I needed most. However, it also did some strange things. It can see a lot of stuff on the phone, but when pulling things from the phone, for some reason, some files and directories do not come over. I imagine this may have to do with permissions on those items.
I'm basically making thsi note here in case someone finds the thread, thinks they have dumped heir whole phone... just make sure you pick through the important directories before you think you've got everything and discard the phone.
Thanks again everyone. Ass officially saved.
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
soundwave4 said:
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
Click to expand...
Click to collapse
If you have adb setup just do adb pulls. You can get anything that way. Slow, but a plan b if nothing else. I would count for you but I run twrp and I don't have time or battery to flash it over to cwm right now.
Edit: for whatever reason tapatalk didn't load anything past the OP...disregard.
Tapatalked from my Galaxy S II.

[Q] Help! Accidentally deleted system and can't restore or install

Coming from a phone with microSD extension, I had never encountered such an issue:
I bought this phone with a stock 4.2 Rom installed and tried to install a custom Rom. I first installed the latest version of touch recovery (tried it and it seemed to work fine) and did a backup using the default settings. Then I erroneously chose to format system and data, thinking that I could then "install from zip". Strangely, these steps deleted everything in the /sdcard directory and I couldnt select "external SD" (because the phone isnt equipped with it anyways?). Then I made a second mistake and restarted the phone, despite the message warning that I no longer had an OS installed. I took the battery out, and then held the power down while pressing the power button. The phone couldn't get into recovery, but instead showed a screen with the android logo, a large "Start" sign above it, and "Downloading...", "Do not turn off target !!" below it. Pressing the power button now got the phone to show just "Google" and a lock logo under it. The PC (windows 7) can not detect the phone throughout the process.
I tried the latest tool kit and samsung's USB driver but couldnt get the phone recognized by the PC.
Does this mean that the phone is doomed???
Please help!!!
Trent
Relax, it's not easy to 'doom' your Nexus. Especially with all the hard-workers in XDA
Try accessing Recovery mode by holding down BOTH vol up + vol down, as well as power. Holding just vol down + power is 'Download Mode', and at the least you can get to this. Means your phones far from doomed
Thanks a lot for the reply!
As a matter of fact, I also figured out how to get back to recovery (if only I had read your post earlier, my pain would've been much less!). But the problem remains that I can not get a target ROM onto the phone, since: 1. whatever I did seemed to have gotten rid of the nand backup supposedly stored in /data/media/TWRP/BACKUPS/ (I'm using TWRP V. 2.3.2.1). 2. I can not get my PC(or Mac, for that matter) to recognize the phone or the internal storage.
Any pointer from here?
Thanks again!!!
Trent
You can download a factory image and install with fastboot. It's quite easy and instructions are readily available on this forum. You can then install a custom ROM afterwards if stock is not your thing.
Found the answer finally!
It's the adb push method. Basically, it's to install adb drivers and execute a few commands via the command window. Not too bad... Don't know much about fastboot yet though ... If anyone else needs more details, please PM me (to save public bandwidth).
Thanks a lot anyways, whpnhp and jocalderone!!!
Trent

S4 mini with broken screen, no more data after 'blind' reboots to recovery

Dear All!
(I already searched Google and xda - However, since my problem is rather specific, I may be using the wrong keywords to come up with a solution that is also applicable here; so also links are highly appreciated!)
I will give you the whole story in order not to skip anything important:
While hiking with my family I somehow managed to break my screen (LCD and Touch, as far as I could tell). However, the phone was still powered on, which i could tell from using the volume keys and hearing the normal sounds. Also the phone was ringing when called.
Unfortunately, USB Debugging wasn't activated, so I booted to recovery (some CWM, can't be more specific, sorry) via several tries. It was a bit tricky at first, but i managed to come up with a routine that would work (Holding VolUp+Home, then Power additionally; releasing the power button after the first vibration and then holding the other two for another 3-5 sec did the trick).
I then could gain usb debugging the way described in this thread: [Tool][Windows] Control a device with a broken screen. Now with touchscreen support!!
Using a Linux machine I then used adb commands (ls; cd; pull) to copy my mmssms.db; however I had to leave my workplace for a short while. Afterwards my device wasn't shown in adb devices, because it powered off for some reason.
Here comes the crucial part: At this point I mistakenly booted into Download Mode (and wasn't aware that I did it, cofused VolUp and VolDown - I couldn't see that, so I'm not 100% sure). I pulled out the battery at this point and rebooted into recovery.
Booting into recovery still works and "adb shell" -> "ls" shows the folders, however apart from the top level folders there are no more files/folders left (e.g. "ls mnt" gives "fuse secure shell"; "ls data" gives "media"; "ls data/media" doesn't return anything)
At this point I mainly want to get the contents of my internal sd (now no files are shown).
tl;dr: Broke screen; accidentially booted into Download Mode; Pulled out battery; Can't access my files/files gone in adb shell
Is there a way to recover the file structure? I still can get into recovery and use adb but the phone won't boot to CyanogenMod (I suppose it gives me a soft brick screen, but i can't confirm that as my screen is broken).
I really hope someone could point me in the right direction!
Lukas

Rooted G7 Play: Forgot pattern lock, can't factory reset either

I searched and didn't see anything that relates to my specific problem.
I have a 1952-4 that I rooted per instructions on here (Magisk). I dropped it and broke the screen about 9 months ago and just fixed it today...and I can't remember my pattern. I'm up to 50 tries, so now I have to wait 120 seconds before it lets me try the next one.
Since the root process requires you to reboot recovery for root, doing that just sends it to the normal lock screen. When I hit Vol Down/Power, my options on the bootloader screen are:
-Start
-Restart Bootloader
-Recovery Mode (restarts it, sends to lockscreen)
-Power Off
-Factory Mode (restarts, sends to lockscreen)
-Barcodes
-BP Tools (restarts, back to lockscreen)
-QCOM (restarts, back to lockscreen)
-Bootloader Logs
-Switch Tools Mode (enables/disables "Tool Mode Config" option on the bootloader screen)
My computer beeps the "something USB has been plugged in" chime when I connect it, but it doesn't pull up in File Explorer (unless it's off, but just shows that a USB drive has been connected but won't pull up anything when I click on it), nor can I connect through ADB. It's not a cable/USB port issue either as ADB finds my Note 8 when I plug it in and check via "adb devices."
Can't wipe it via Find my Phone either because it's been 270 days since my account pinged the phone, so it just shows up as "Android" device.
Any suggestions on how to either get my computer/ADB to recognize it (with root) so I can just delete the lock database, or how I can factory reset it? Am I forgetting a reboot option?
Thanks in advance.
veryspecialagent said:
I searched and didn't see anything that relates to my specific problem.
I have a 1952-4 that I rooted per instructions on here (Magisk). I dropped it and broke the screen about 9 months ago and just fixed it today...and I can't remember my pattern. I'm up to 50 tries, so now I have to wait 120 seconds before it lets me try the next one.
Since the root process requires you to reboot recovery for root, doing that just sends it to the normal lock screen. When I hit Vol Down/Power, my options on the bootloader screen are:
-Start
-Restart Bootloader
-Recovery Mode (restarts it, sends to lockscreen)
-Power Off
-Factory Mode (restarts, sends to lockscreen)
-Barcodes
-BP Tools (restarts, back to lockscreen)
-QCOM (restarts, back to lockscreen)
-Bootloader Logs
-Switch Tools Mode (enables/disables "Tool Mode Config" option on the bootloader screen)
My computer beeps the "something USB has been plugged in" chime when I connect it, but it doesn't pull up in File Explorer (unless it's off, but just shows that a USB drive has been connected but won't pull up anything when I click on it), nor can I connect through ADB. It's not a cable/USB port issue either as ADB finds my Note 8 when I plug it in and check via "adb devices."
Can't wipe it via Find my Phone either because it's been 270 days since my account pinged the phone, so it just shows up as "Android" device.
Any suggestions on how to either get my computer/ADB to recognize it (with root) so I can just delete the lock database, or how I can factory reset it? Am I forgetting a reboot option?
Thanks in advance.
Click to expand...
Click to collapse
In Bootloader
factory reset with
Code:
fastboot -w
fastboot reboot
sd_shadow said:
In Bootloader
factory reset with
Code:
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
I'm on the bootloader screen (PWR/Vol-)
Computer does not show it connected, either in FIle Explorer or ADB.
veryspecialagent said:
I'm on the bootloader screen (PWR/Vol-)
Computer does not show it connected, either in FIle Explorer or ADB.
Click to expand...
Click to collapse
Window 10?
Yeah. It should remember this phone, since I used this computer to root it when I first got it a year and a half ago.
I used a different cable and got it to pick up the phone (as an unknown device) in Windows but NOT ADB, and the phone to realize it was connected (see last line on phone screen) but they're not talking.
If I boot it all the way up, either regular or recovery (root), it doesn't show at all on my computer.
Like I said, I'd be fine with wiping it, but can't even get to that option.
Install the moto drivers. If that doesn't work then make sure your using a usb2 port and not a usb3 port as its a known issue with moto phones.
I just ordered a new OEM cable.
Also ordered an OTG cable to see if I can force it to startup into a different mode that'll allow me to do something with it.
I'll update this thread once I'm able to test them out.
I got a new cable. My USB ports are not labeled, and my Moto drivers reinstalled.
After rebooting to the recovery screen, I plugged it in and apparently I have fastboot. I checked the bootloader logs and it says:
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Volume down key pressed
USB connected
Windows doesn't pick up anything connected by USB. I can't restart to get root because then adb doesn't pick up the phone either because of the screenlock preventing me from hitting ok to trust my computer.
I'm asking the following because I can't find answers: Can you delete the screen lock file with the only bridge being fastboot, not adb. How can I do a factory reset if rebooting to recovery is our normal way of turnin gon the device with root access? Or would reflashing something work?
command line commands are a perishable skill and it's been a couple years since I did this stuff.
Thanks in advance.
To recap, I either need to be able to get into the directory to delete the pattern lock, or factory reset the phone.
I've tried the pattern lock 79 times, which means I have to wait 300+ seconds between tries. I think an error is causing that though.
Fastboot is my only option at this point as far as using commands goes. Rebooting recovery just reboots it with root permissions, but neither adb or Windows 10 picks it up. Using a brand new factory cord and tried every USB port on my computer, even the USB-C to USB-C. But I can't find anywhere that shows how to get into the directory using fastboot.
In Device Manager, I've been getting an error with Android ADB Interface (The device cannot start; Code 10). I uninstalled, reinstalled various drivers, killed adb.exe, etc., Still happening.
HOWEVER, Motorola ADB Interface is working just fine and goes away when I unplug my phone, returns when I plug it in. Only when it's in recovery/fastboot mode though.
I got into Safe Mode, but computer won't pick it up.
I can't get into Field Test Mode. I did reboot it into something else. I don't know what, but the screen was off and the home button was illuminated. EDL mode? I don't know. Neither my computer or adb read that anything was attached, and i can't figure out how I did it.
I also tried sideloading some pattern lock removers, but apparently you can't do that in fastboot.
Thoughts?
Just to close this out with a solution: I had forgotten that in order to get to the recovery menu, you have to hold the buttons when you reboot recovery. Didn't realize that until I was rooting my Moto e6.
Factory reset complete. No more pattern lock. Though since I've now tried rooting it 4 times with 4 different images and have not succeeded even though I had root before all this, I wish I could have realized the above and possibly gotten in and deleted the gesture.
Lesson learned.
Hold what buttons? I'm afraid I'm in same spot.
onefstfoknv6 said:
Hold what buttons? I'm afraid I'm in same spot.
Click to expand...
Click to collapse
Volume up button and power button
sd_shadow said:
Volume up button and power button
Click to expand...
Click to collapse
Just found this. Timing is everything apparently.
Press and hold the Volume Down and Power buttons simultaneously until the Android Recovery screen appears.
Press the Volume Down button to navigate to Recovery.
With Recovery displayed, press the Power button.
When you see the 'Droid' with 'No Command,' hold Power and tap Volume Up just once and immediately release both buttons.
Scroll to wipe data/factory reset by pressing the Volume Down button
Press the Power button.
Scroll to YES by pressing the Volume Down button.
Press the Power button.
The 'phone will wipe all contents.
Press the Power button.
The 'phone will now reboot to the initial setup screen.

Dead screen Data Recovery?

Hi,
sadly I broke my one plus after dropping it the other day, the phone is still working but the screen is completely cracked and wont turn on.
Do I have any chance of accessing my data?
Info:
Android OOS 10.0.16
Bootloader unlocked
TWRP Recovery 3.4.0.2 HotDog
ADB sadly unauthorized...
ADB Shell in TWRP (seems useless tho)
I tired accessing the data via adb in twrp but as we know the decryption is not working.
I was thinking maybe booting a patched boot image would allow me to access the data via adb?
Any ideas would be appreciated I tinkered with the phone for a few ours.
Thanks
Replace screen?
I assume pc can't see your internal sd?
HueyT said:
Replace screen?
I assume pc can't see your internal sd?
Click to expand...
Click to collapse
Yeah I cant see the internal SD sadly.
I already got a replacement 7t so I wont be repairing the screen.
I just found a solution thats working for me mileage may vary:
Requirements:
USB Debugging enabled but the phone was NOT authorized
Win 10 with a ADB terminal ready
Type C cable (the original one is prefered)
USB OTG Adapter
A USB Keyboard
Turn On Sound if your Phone is silent this will help you since we are flying blind
1. Open a terminal type "adb devices"
2. Restart your phone (hold Power + VolUp for about 15 sec it should vibrate
3. Connect the OTG Adapter with they keyboard and press spacebar, next type your PIN and press enter (as far as I know your out of luck if you have a pattern setup
4. DONT TOUCH the screen. Connect your Phone to the PC
5. One the Phone will be a popup asking if you want to allow USB Debugging
6. Connect the OTG Adapter again and be careful not to touch the screen.
Press TAB once and press spacebar to permanently remember the PC.
Next press TAB twice and press Enter.
Thats it!
If you did it correctly you can connect back to the pc and the phone should be authorized.
Now to backup the Data from the phone just type
adb pull /mnt/sdcard .
this backups all data to the current folder
If your screen is still working than this is much easier of course, I had to give it 5 to 6 tried before I got it working!

Categories

Resources