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.
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
Hi guys!
I have tried to get Android onto my phone and I'm stuck. I'm using the files/instructions from this thread. (HSPL has been done and confirmed)
I noticed there's a similar thread, but they seem to be talking about a different problem, even though it happened at the same step.
Looking at the step-by-step list from that thread, I am stuck between step 10, step 11 and step 12:
- I successfully flashed RHODIMG.NBH
- Took out the battery, booted up with USB and there's the blue screen of the miniPoopLoader (tee-hee, it says poop ).
- Text scrolls by, ends with -- suspend --.
That's it, nothing happens. I can reboot, and it just goes there again. One of the snippets of text reads "flash_read_image: failed 0 errors"
I thought this might be all fine afterall and that I just had to use Fastboot erase blabla to go ahead. But obviously that doesn't work. Most likely because step 12 says install drivers, but no request to install any drivers comes up on my Windows (using Win 7 64 - also, drivers in the package are all Vista - will those work?), which I assume is either because the phone never boots up "far enough" for windows to detect the device, OR because I'm a retard to all major phone hackers here, because I just have to copy them somewhere. (didn't find anything on the boards to suggest the later is true, but then again, who knows).
So, where's the stupid newbie mistake that I overlooked? This isn't the first flash I'm doing, flashed win 6.1/6.5 onto my Touch Pro (1 ), using a fine how-to on this board, and constantly tweaking my S2 and S3, but this seems to be too much for me to figure out.
Thanks for any help!
What phone are you using?
Basic trouble shooting would be.
Task 29, re-download & reinstall minipooploader.
This video gives some idea of what you should expect.Useful info starts around 7:00
http://www.youtube.com/watch?v=_qNCHqGPofI
I have never heard of a suspend error/dialog. Perhaps someone else can chime in.
I think he just hasn't prepped for fastboot properly.
Sometimes I have to reboot a few times to get the cable plug timing or *something* right... Not sure what it is, but occasionally when doing a new flash to Android I had issues with fastboot not being recognized - and obviously you won't be able to flash recovery without fastboot being functional.
So before you task29 and reinstall OP - try a few different things - try plugging the cable in BEFORE you boot the phone. Try pulling the battery again, and do the plug in cable before you turn it on. I can't remember what the secret is here, I know for getting into recovery you have to start holding power as soon as you see the blue screen - but obviously this is beyond where you are at.
arrrghhh said:
I think he just hasn't prepped for fastboot properly.
Sometimes I have to reboot a few times to get the cable plug timing or *something* right... Not sure what it is, but occasionally when doing a new flash to Android I had issues with fastboot not being recognized - and obviously you won't be able to flash recovery without fastboot being functional.
So before you task29 and reinstall OP - try a few different things - try plugging the cable in BEFORE you boot the phone. Try pulling the battery again, and do the plug in cable before you turn it on. I can't remember what the secret is here, I know for getting into recovery you have to start holding power as soon as you see the blue screen - but obviously this is beyond where you are at.
Click to expand...
Click to collapse
To enter fast boot you need to have the phone totally off (not rebooted) with the usb cable removed. Then plug usb cable into the phone with the phone off. Then press and hold the power button until the blue screen is done. Sadly I have been doing this all morning trying to resolve a problem of my own.
Tried that, resulting in a slightly different screen (see attached image). Other than that, no difference. I still don't get any request for the HTC drivers and going Fastboot erase recovery results in "waiting for device".
Could you check the list at the thread I linked in the original posting and tell me if I somehow missed something?
Step 10 worked fine.
Step 11 I guess is what Wizardknight commented on.
Step 12 is what confuses me and what's possibly the culprit here?
I bet it's just that without the drivers my PC can't send the Fastboot commands to the phone.
Everything before that worked fine with no errors and everything after that, is just hammering away at the console.
Thanks guys!
Sent from my GT-I9300 using xda premium
Urgh, no idea why it uploaded the picture sideways, sorry.
When instead I press the power button as soon as I see blue (as opposed to hold it all the time), I get the following (see image)
Sent from my GT-I9300 using xda premium
Looks like it is working ok on the phone. I am assuming you installed fastboot and ADB on the PC.
What happens when you open a command prompt and type fastboot devices?
BTW here are the more official install directions.
Lists nothing. After hitting enter, I'm back at the \android-sdk\platform-tools promt.
Sent from my GT-I9300 using xda premium
Was the usb port on the phone working ok in WM? Could you sync and other data related activities?
Does any unknown devices show up in your device manager on the pc?
Have you tried any other usb cables?
Solved.
I tried different ports and a different cable before, even though my cable worked fine before (and so did the port). Guess I have two dead cables here, because the third one did the trick.
Drivers installed at once, Android installed and I feel very stupid now. Thank you very much for being so patient with something this stupid.
wizardknight said:
Was the usb port on the phone working ok in WM? Could you sync and other data related activities?
Does any unknown devices show up in your device manager on the pc?
Have you tried any other usb cables?
Click to expand...
Click to collapse
This might be where you're going to have to go next OP. Sounds like it's all OK - so try different cables, different USB ports on the PC, and if you can - an entirely different PC altogether.
Vortagh said:
Solved.
I tried different ports and a different cable before, even though my cable worked fine before (and so did the port). Guess I have two dead cables here, because the third one did the trick.
Drivers installed at once, Android installed and I feel very stupid now. Thank you very much for being so patient with something this stupid.
Click to expand...
Click to collapse
Had that problem before too. Glad you got it sorted.
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.
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.
Hi,
i broke the Display of my ZTE Axon 7 mini on stock ROM and without USB debugging enabled. No custom recovery or anything done to the device. The touch interface of the screen is at least partially functioning, i'm able to boot it, unlock it by guessing where to draw the pattern (i know bc the fingerprint sensor is working afterwards) and power off as well by clicking on the spot where the button should be. I've read some threats about tools to access your phone with broken screens, but nothing worked. Thing is, i think i set the usb-setting to "charge only" when connected to my pc. So the device won't be recognizedwith adb fastboot. Which means i cannot use the method described here for instance.
So does anybody know how i could change the settings or get at the data generally? I'd be really glad if someone could help.
cheerio