Hopefully this is the right place to post this.
I have a Samsung Galaxy S4 (completely stock as it is my work phone), however I have some personal data on it (photos etc.).
The screen and digitiser are completely broken, however the phone still boots; I'm just unable to see what is occurring, or interact with the device.
The device broke without USB debugging enabled, so I am unable to use adb to access the device. I have tried booting into both recovery and download modes (but I have been unable to access using adb regardless of mode). The device is also not set to act as USB mass storage, so it only displays as a media device within Windows.
I have also tried using Kies to access the data, however I receive a message saying that the phone needs to be unlocked. Obviously I am unable to do this, as neither the screen nor adb commands work. Using the Samsung website to unlock the device is out of the question too, as I do not have a Samsung account.
In addition, I have tried booting into download mode and using ODIN to flash ClockworkMod to the device, but ODIN was unable to connect.
I do not have another S4, so swapping the screens temporarily isn't possible, and obviously using an OTG mouse wouldn't work, as I cannot see the screen.
I am really at a loss here, is there any way I can get the data off of this device?
Any help is greatly appreciated.
Only way without replacing the screen is going to be a custom recovery and adb at this point. I'm hard pressed to understand why Kies recognizes your phone but Odin doesn't. Only thing I can think of is that once you boot to Download Mode via Power + Home + Volume Down is that starts the caution message about installing custom stuff and you need to hit Volume Up at that point to continue to actually be able to use the mode. Either that or check your Device Manager for driver issues as the driver loaded for that is a little different than like for MTP.
es0tericcha0s said:
Only way without replacing the screen is going to be a custom recovery and adb at this point. I'm hard pressed to understand why Kies recognizes your phone but Odin doesn't. Only thing I can think of is that once you boot to Download Mode via Power + Home + Volume Down is that starts the caution message about installing custom stuff and you need to hit Volume Up at that point to continue to actually be able to use the mode. Either that or check your Device Manager for driver issues as the driver loaded for that is a little different than like for MTP.
Click to expand...
Click to collapse
The only way I can tell it is in any mode other than normal boot is due to the red LED. After the first vibrate I repeatedly pressed Volume Up to ensure I'd got past the disclaimer, but obviously I'll never know for sure.
I found a tutorial for flashing CWM, however it was for an older version of ODIN (3.07). It mentions to put the CWM tar file in the "PDA" field, however this field is not present in the newer version (3.10 I think?).
As such, I was unsure how to proceed.
PDA is now the AP slot in newer versions of Odin.
Thank you, I'm going to give it another go today.
Does the device need to be rooted in order to use ODIN? I've used it once before but it was a long time ago, so I don't fully remember.
I also don't want to void the warranty on the device, as it's technically not mine.
Root is not necessary to use Odin, however, if you are able to install a custom recovery, and your phone has Knox, it will be tripped, thus voiding the warranty. There are plenty of people who have returned phones with it tripped without issue, but no way to guarantee they won't care. Most likely since it's obviously a physical issue, and not from any attempt at modding, they shouldn't care. However, they do reserve the right to refuse warranty claims if they so chose.
Just in case anyone comes across this via Google, I managed to get my files using the following method:
First, I loaded up Samsung Kies on my PC, and plugged in a standard USB male to microUSB male cable.
Then I used an OTG adapter (USB female to microUSB Male) and plugged a USB keyboard into the phone. After a few attempts, I felt the phone vibrate when I typed my PIN in and pressed return.
I then quickly unplugged the OTG cable from the phone, and plugged in the PC USB cable. This allowed Kies to connect to the phone, and I was able to pull my files.
Hopefully this helps someone if they are having the same issue.
Good work! Glad you were able to find a solution.
Related
Hi,
So I just purchased a Samsung Galaxy S II, and I've been trying a few different ROM's found on this site. The last thing I did was actually revert back to a stock Samsung Kernel and firmware. This worked fine, but it unrooted my device, which I knew would happen, but now I'm not able to root it again because when I put the device into download mode, ODIN, or better yet, my computer won't detect the device.
I have all the drivers installed, and I also deleted them all, and Kies, and started from scratch again after searching XDA for similar issues.
I don't believe this to be a driver issue, since I was able to root my device, and swap roms before I went back to the official kernel and firmware. I'm with Bell in Canada, so the versions I went back to were not the official Bell versions, since Samsung has not made them available.
I have a Mac, but I've been using Windows 7 and Odin under VMWare. I can connect my device to either OSX, or Windows 7 when the device is not in download mode, and everything works fine, and Odin detects the device (Not that that does any good of course)
When I connect the device under download mode, the Mac detects the device and asks me if I want to connect it to my Mac, or to Windows (As it should) but no matter which one I select, neither OS acknowledges the device after that point, where as when I'm not in Download mode, both OS's detect the device fine.
After all my troubleshooting with my computer based off of what I found online here, The only conclusion I have left is that there is something missing on the device that allows it to be found under download mode, but that aspect of all this is beyond my current skill level.
Anyone have any ideas?
Are you pressing the Volume Up button to continue in Download mode? Besides, Virtual machine isn't recommended I think.
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Scott56 said:
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Click to expand...
Click to collapse
Have you found anyway to Make Odin recognize to phone in download mode?? Im still struggling with that. my phone is on stock kernel and not rooted yet, ODIN finds it fine when the phone is on and USB Debugging is on, but once I put the phone on download mode it wont recognize it, I dont know why..
Could it be because of the ''SAMSUNG Mobile MTP Device'' driver failed to install correctly??
all other drivers are installed correctly.. I have tried to get the driver mentioned above to install correctly but it fails every time, with USB debugging on and off, i have wiped the phone and installed Kies and the drivers several times, Im clueless right.. anyone have any idea please help??
I myself am also suffering from this problem. However, USB seems to function fine while the phone is booted up or in recovery (For ADB). I'm wondering if necessary files may have become corrupted or deleted in reference to USB drivers (phone side mind you) that are used in download mode.
edit: It's also recognized in recovery mode.
Even if it can't be fixed I'd still like to understand why.
-Simply D
was looking for help on this and saw this thread, same problem too..
Connects to Odin and Kies fine when switched on "normally", can use USB mass storage mode Etc.
comes up with a USB device has malfunctioned message on PC when I connect USB cable when switched on and in download mode
EDIT:- just to add, if I try upgrading firmware via Kies it gets to the point where it switches the phone to download mode to upgrade it and has the same issue even with an official upgrade
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
SimplyD said:
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
Click to expand...
Click to collapse
Tried this and it didn't work for me :/ going to give it another try later, thanks for the suggestion either way
The thing is that I cant to get into the CW Recovery Mode either because the phone appears to be charging even without any cable. I know it is not a battery issue, because I have tried with other batteries and nothing changes.
I'd really appreciate any thought that anyone can throw in this because I have read and tried so many things that I'm starting to think that I have bricked it.
You do not make it clear whether you are unable to get into download mode, or you get download mode but odin does not recognize the phone.
Attempt to enter download mode and connect to Odin while the battery is out:
Open odin on the desktop. Pull the battery, then hold the vol down button while plugging in the usb cable. let us know what happens.
creepyncrawly said:
You do not make it clear whether you are unable to get into download mode, or you get download mode but odin does not recognize the phone.
Attempt to enter download mode and connect to Odin while the battery is out:
Open odin on the desktop. Pull the battery, then hold the vol down button while plugging in the usb cable. let us know what happens.
Click to expand...
Click to collapse
Im sorry if I didnt make myself clear.
I can make it to download mode but Odin doesnt recognize my phone, even though I have Samsung kies installed and it worked before with other roms. The thing about the battery is that the phone "thinks" that is charging all the time, which means that I can make it to the CW Recovery mode when I press Volume up + home + power button :crying:
gonzobongo said:
Im sorry if I didnt make myself clear.
I can make it to download mode but Odin doesnt recognize my phone, even though I have Samsung kies installed and it worked before with other roms. The thing about the battery is that the phone "thinks" that is charging all the time, which means that I can make it to the CW Recovery mode when I press Volume up + home + power button :crying:
Click to expand...
Click to collapse
So, did you try to connect to odin while the battery was pulled? What result did you get?
creepyncrawly said:
So, did you try to connect to odin while the battery was pulled? What result did you get?
Click to expand...
Click to collapse
Nothing either, neither Odin nor the system recognized the phone in any moment.
Any other idea??
Start by assuming it is not the phone. Suspect the usual possibilities, and eliminate them one by one. It could be a problem with driver, usb port, usb cable, or PC.
1. Check in Windows uninstall programs dialog. You should have "Samsung USB driver for Mobile Phones." If not, install it. If so, uninstall it and reinstall the latest version.
2. Try another usb port. If a desktop computer, be sure to use a usb port that is directly connected to the motherboard. Try all the ones that are available.
3. Try another usb cable. Use the original cable that came with the phone. Try any other cable you can put your hands on.
4. Try another computer. One person even said they could never get their phone to connect on Windows and with Odin, but were able to flash it with a Mac using Heimdall.
If you exhaust all of those possibilities without success, then it is a fairly good bet that the problem is with the phone.
creepyncrawly said:
Start by assuming it is not the phone. Suspect the usual possibilities, and eliminate them one by one. It could be a problem with driver, usb port, usb cable, or PC.
1. Check in Windows uninstall programs dialog. You should have "Samsung USB driver for Mobile Phones." If not, install it. If so, uninstall it and reinstall the latest version.
2. Try another usb port. If a desktop computer, be sure to use a usb port that is directly connected to the motherboard. Try all the ones that are available.
3. Try another usb cable. Use the original cable that came with the phone. Try any other cable you can put your hands on.
4. Try another computer. One person even said they could never get their phone to connect on Windows and with Odin, but were able to flash it with a Mac using Heimdall.
If you exhaust all of those possibilities without success, then it is a fairly good bet that the problem is with the phone.
Click to expand...
Click to collapse
I tried uninstalling the samsung driver and installing it, but nothing. I'm pretty sure is a phone issue, most likely related with the ROM that had installed before, because i tried with my brother's phone, same model galaxy s2 I-777 and Odin recognizes it perfectly.
The thing is that if I cannot connect it to Odin, is there any other way I can flash it? like from a external micro SD card or something? Or any way I can access to the phone in download mode??
gonzobongo said:
The thing is that if I cannot connect it to Odin, is there any other way I can flash it? like from a external micro SD card or something? Or any way I can access to the phone in download mode??
Click to expand...
Click to collapse
Heimdall performs the same basic operation as Odin, but it is built by a private individual, not by Samsung. You could try Heimdall from your PC, or if you could get a hold of a mac you could try Heimdall from it. I'd suggest the command line version, although it has a nice UI as well.
If you've tried all of the four points I posted, then that's all I know to do. But I wouldn't just try #1 and then pass up the other three because you are convinced the problem is in the phone.
Oh, and the final resort would probably be to send it to Josh at Mobile Tech Videos. (not free)
creepyncrawly said:
Heimdall performs the same basic operation as Odin, but it is built by a private individual, not by Samsung. You could try Heimdall from your PC, or if you could get a hold of a mac you could try Heimdall from it. I'd suggest the command line version, although it has a nice UI as well.
If you've tried all of the four points I posted, then that's all I know to do. But I wouldn't just try #1 and then pass up the other three because you are convinced the problem is in the phone.
Oh, and the final resort would probably be to send it to Josh at Mobile Tech Videos. (not free)
Click to expand...
Click to collapse
Ok, I don't know why but now Odin started to recognize it. It seems there is something wrong with the usb port and that's why the system couldn't recognize it. But now the problem is that the phone "thinks" that it is always charging and therefore I can't make it to the CW recovery mode, only to the download mode. So now, is there any way I can install some stable ROM on the phone from Odin???
gonzobongo said:
Ok, I don't know why but now Odin started to recognize it. It seems there is something wrong with the usb port and that's why the system couldn't recognize it. But now the problem is that the phone "thinks" that it is always charging and therefore I can't make it to the CW recovery mode, only to the download mode. So now, is there any way I can install some stable ROM on the phone from Odin???
Click to expand...
Click to collapse
Use Odin to flash one of the stock plus root firmwares; I suggest (4.0.4) I777UCLL6. See the link in my signature for correct thread. The OP of that thread also has full instructions for installing a custom kernel, and which one to use. Use Mobile Odin Lite or Mobile Odin Pro to flash a custom kernel with contains ClockworkMod Recovery. Then use CWM recovery to flash the firmware of your choice. Profit.
I tried flashing CWM recovery onto my AT&T Galaxy S4 and because my phone does not connect to my computer via USB for some reason (the phone charges and my computer recognizes that there's a device in, but I cannot actually do anything with it) I flashed it with Flashify. I rebooted into recovery mode, and I got slapped with the "Unauthorized software has been detected on your phone!" message. So I tried rebooting, and I got stuck in a recovery mode bootloop with the same message. Eventually, I realized if I just go into download mode and reboot by pressing the volume down key, it doesn't try to go into recovery mode. I have already endlessly researched my USB problem, and yes, I DO have USB debugging on. ODIN recognizes that I have an external device in as well, but I haven't tried flashing anything onto my phone with it because I don't want to brick my phone because the connection to my PC is faulty. I'm using the charger that came with the device as my USB drive, so that's not faulty either. I know rooting my phone did this, and I'm pretty sure it's because I missed a step. I used this tutorial to root my phone:
[droid views dot com] /root-att-galaxy-s4-sgh-i337-android-4-4-4-kitkat-firmware-i337ucufnj4/ (I'm not allowed to post links yet, so fix the URL if you're gonna have a look)
When I flashed the I337_NC1_Stock_Kernel, my phone refused to go into download mode and I couldn't flash the I337_NJ4_Stock_Kernel as a result. I'm pretty sure that's what caused it, but I have no idea how to fix it. I'm not an expert with my phone and, despite almost soft-bricking my phone via a corrupt CWM .zip, I'm not a newbie at this either. If I could figure out how to fix this problem, I wouldn't have to worry about throwing myself into a bootloop because I can just use ODIN. I was a sitting duck before download mode rescued me, so I'd like some help as to how I can accomplish this. Any and all help is appreciated. I am 100% certain my device is the right version for that tutorial, I wouldn't try to root my phone without checking all of the simple things first.
Hi all,
I wonder if somebody could help me.
At the moment I have a Z5 compact with a broken screen (totally black) and touch. I know it still can boot, because it responds to my fingerprint when booted up. However, it does respond to my finger, but still needs a patern on first boot, which I cannot do on account of the broken touch screen. Also, my computer detects the phone.
I want to access my data, but for that I would have to use the onscreen menu which pops up when I connect the phone with usb. That's impossible.
I looked around on the internet and it is possible to remotely control the screen or access via adb. However, for that I either need to install some app on the phone, enable usb-debugging or authorise access via adb. All of those are impossible.
My phone has un unlocked bootloader and is rooted, so as a last resort I've tried to flash a modified kernel to enable usb debugging by default. This fails. Probably because I make some mistake in modifying the kernel, but I don't know. There's not a lot of response from my phone, as you understand ... Besides, I've absolutely no experience modding myself.
Anybody any idea, please?
So I just fixed the same issue you're having this week. It required opening up the phone.
Basically the ribbon cable that connects the screen to the motherboard had become unseated and needed to be plugged back in for me.
The Z5C isn't the easiest phone to take apart but it's not that difficult either. Just requires some basic tools (Hair dryer, tweezers and some precision screw drivers). There's a bunch of videos showing you how on ifixit or youtube. You just have to go all the way to the part where they flip over the motherboard and unplug the two ribbon cables, one of those two will be the culprit.
This is the first and only phone I've taken apart so any amateur can do this.
Boot to recovery and connect your phone to PC
Nutchos said:
So I just fixed the same issue you're having this week. It required opening up the phone.
Basically the ribbon cable that connects the screen to the motherboard had become unseated and needed to be plugged back in for me.
Click to expand...
Click to collapse
Yes, actually I've had problems with a broken backlight before and opening the phone and re-adjusting the cable solved that. Not in this case however. Thanks for your suggestion, anyways.
mlleemiles said:
Boot to recovery and connect your phone to PC
Click to expand...
Click to collapse
Would recovery provide me with some way to enter my pattern via a PC, e.g. with ADB?
Actually, I'm not sure I had any recovery installed at all. I've tried this before and just tried it again. I press the on/off-button while holding volume down. After that no response whatsoever. My computer does not see any device when connected. I suppose my recovery does not work properly, but without screen I can't be certain.
mlleemiles, you are a _hero_!
After reading your post I decided to try flashing another recovery to try if that might work. Now I can access my files without ever having entered any pattern .
Nevermind that it turns out my files weren't encrypted and I thought they were.
If anyone has a similar problem in the future, this is what worked for me:
My exact situation:
- My phone runs a stock rom (downloaded from XperiCheck) with version 32.4.A.1.54. When my phone was still running ok I had the bootloader unlocked and my device rooted with Rootkernel.
Working solution:
- I downloaded Twrp, version 3.2.1, from this page:
https://forum.xda-developers.com/z5-compact/development/twrp-twrp-3-2-1-z5-compact-t3748952
- Shut down my phone by disconnecting the battery and reconnecting it again
- Started my phone in fastboot mode and flashed recovery to my phone with:
Code:
fastboot flash recovery recovery_suzuran_220218_2.img
- Booted my phone in recovery with volume down + on/off-button.
- Connected my phone to my PC, et voila.
Turns out I can also access my phone with ADB as root, so after backing up the entire internal memory, I might try to get some remote screen tool working.
So thanks for the help and if I find something interesting and new, I'll post that too.
Small update:
After successfully flashing Twrp I backed up the internal memory, so must of the important stuff was safe by then.
However, it turned out that my phone now wouldn't boot into anything other then Twrp. I decided to flash my rom again. First I installed my apb keys using Twrp:
Code:
adb push adbkey.pub /data/misc/adb/adb_keys
It turned out I already had usb debugging enabled.
I then flashed my original firmware again, and connected with adb. This time it connected correctly, without me having to click any dialogue on my phone. I fiddled with several remote control Android tools most of which didn't work. Finally, it turned out Vysor does exactly what I want to do. It is a bit unstable, but workable.
Anyways, I've finally managed to copy all the stuff I wanted from my phone.
This latest tool also allows you to boot your Samsung Smartphone and tablets into the download mode without pressing the physical keys. If in case your Samsung device physical keys are not working, then this latest Samsung tool is useful for all of you. The best thing about this tool is that it is not necessary to have the USB debugging active. The tool only detects your device and restarts it in download mode to do the flashing by ODIN.
How to use Samsung 300K Tool
This latest tool is useful for those users who have Samsung devices that do not enter download mode with the failure of keys.
After download file is complete simply Run for install.
Make sure that the Samsung drivers are installed
Before connecting the device open the program and the following screen instructions.
Now connect your device to the computer and make sure that the cable is properly or correctly connected, and the screen will change.
In this last step click on the figure of the image where the strain point and your cell phone connected or not enter the download mode quickly in 2 seconds, but I recommend doing the operation with the phone is connected.
Done.
Admin Edit: Attachment has been removed as it was flagged by Google as "uncommon download". Also locking thread.
speechless said:
This latest tool also allows you to boot your Samsung Smartphone and tablets into the download mode without pressing the physical keys. If in case your Samsung device physical keys are not working, then this latest Samsung tool is useful for all of you. The best thing about this tool is that it is not necessary to have the USB debugging active. The tool only detects your device and restarts it in download mode to do the flashing by ODIN.
How to use Samsung 300K Tool
This latest tool is useful for those users who have Samsung devices that do not enter download mode with the failure of keys.
After download file is complete simply Run for install.
Make sure that the Samsung drivers are installed
Before connecting the device open the program and the following screen instructions.
Now connect your device to the computer and make sure that the cable is properly or correctly connected, and the screen will change.
In this last step click on the figure of the image where the strain point and your cell phone connected or not enter the download mode quickly in 2 seconds, but I recommend doing the operation with the phone is connected.
Done.
Click to expand...
Click to collapse
The attached Samsung 300k file gives a CRC error when extracted. also its an exe and doesnt run on Windows 10. Is there an equivalent file that will allow my samsung galaxy T4 (sm-231 v4.4.2 Kitkat) to enter download mode? Its home key is not working right now. Using ADB i am able to enter Manual mode, but not Download mode! So ODIN does not recognize it ( ID:COM is not highlighted). I have installed the latest Samsung USB drivers.
any help will be most appreciated.
sifar786 said:
The attached Samsung 300k file gives a CRC error when extracted. also its an exe and doesnt run on Windows 10. Is there an equivalent file that will allow my samsung galaxy T4 (sm-231 v4.4.2 Kitkat) to enter download mode? Its home key is not working right now. Using ADB i am able to enter Manual mode, but not Download mode! So ODIN does not recognize it ( ID:COM is not highlighted). I have installed the latest Samsung USB drivers.
any help will be most appreciated.
Click to expand...
Click to collapse
When the phone is booted up normally and the way you would normally use it, when you connect your phone and open ODIN, does it still not pick up the phone on the COM port?
And (I'm sure you do), do you have USB debugging turned on and all the other usual things (like you mentioned, having installed the latest drivers)?
Samsung galaxy tab 4 (sm-t231) kitkat v4.4.2
Max_Terrible said:
When the phone is booted up normally and the way you would normally use it, when you connect your phone and open ODIN, does it still not pick up the phone on the COM port?
And (I'm sure you do), do you have USB debugging turned on and all the other usual things (like you mentioned, having installed the latest drivers)?
Click to expand...
Click to collapse
yes, i finally used "adb reboot download" to boot into download mode. Now when i am using ODIN and trying to root my cell by installing TWRP 3.2.1-0-degas.img.tar, it says PASS (success 1/fail 0), but my mobile still shows "DOWNLOADING..." with a horizontal blue line. I can also reboot and load normally, but it seems TWRP has not got installed and still ROOTCHECKER says my mobile is not rooted. Am i using the wrong versions of TWRP recovery or ODIN etc? Can you advice next steps?
sifar786 said:
yes, i finally used "adb reboot download" to boot into download mode. Now when i am using ODIN and trying to root my cell by installing TWRP 3.2.1-0-degas.img.tar, it says PASS (success 1/fail 0), but my mobile still shows "DOWNLOADING..." with a horizontal blue line. I can also reboot and load normally, but it seems TWRP has not got installed and still ROOTCHECKER says my mobile is not rooted. Am i using the wrong versions of TWRP recovery or ODIN etc? Can you advice next steps?
Click to expand...
Click to collapse
When you've flashed TWRP, the phone will stay in download mode. Nothing will change on screen, that is normal. You have to reboot the device manually, using the button combination it says, then immediately as the device restarts, you change the combination to boot into TWRP. All of these steps are explained in whichever thread or wherever you found TWRP.
As far as rooting is concerned; TWRP doesn't inherently root the device. It just replaces the bootloader to allow you to flash custom packages, like the one needed to root the device.
If you're struggling to get the device rooted and there isn't a very specific reason why you need root, then my best recommendation would be to rather just leave it stock.
As far as I know, flashing TWRP won't trigger Knox, so you'll still have that functionality. Recently, it's become less and less necessary to have root and fewer apps require it, as well.
Like I said, unless there is a very specific reason, you'll likely be better off just leaving it the way it is.
EDIT: I'm realising now the original problem was that your home button wasn't working. In that case, it'll be difficult to get into TWRP, anyway. I also made some assumptions about Knox, because this is on the Note8 sub forum. I don't know if your device has Knox. And You're on a rather old version of Android also, so I understand why you may want to root, but without your home button working, it could become difficult to get into the places where you need to be to make that possible.