Hello everyone.
My S2 had a water-damage. My friend wanted to be kind to wash my pants after spilling some tomato-dinner on it, so everything got to rumble a bit in the washer
Then, the only thing that doesn't work is the display.
It's all black, but the boot-sound comes, I can swype away the lock-screen (of course without seeing it) and with a bit of coordination turn it off ..
It's detected in Windows 7 as Composite Device and Modem. I had it detect "ADB Device" at one point, but it wouldn't show up in "adb devices" whatsoever, since then Win has only detected Composite and Modem.
I also tried to boot it in recovery mode, since another brand new S2 I got can actually ADB in Recovery with XWKI8 firmware delivered stock, although this doesn't work for the broken one, or maybe I just haven't reached recovery yet, I am trying to count seconds of booting to time it right, most of the time it just boots fully with boot sound if I keep holding vol+home ..
I am thinking if I could put some custom kernel on it by putting it to download mode, or somehow reach a state where I could transfer files with the display off.
Any ideas?
And is the phone in USB debugging when it shows as Composite Device / Modem or is this a bad sign of driver-fault, bad recognisition, or is it indeed a confirmation that the phone is in debug-mode?
Related
Uh hi.
I'm a herp.
So I may have accidently tried to root and flash my friend's Samsung Vibrant. It was going smoohtly but now, I'm all sorts of messed up.
The problem: I may have used the wrong kernel (zImage) when using heimdall-frontend (which I downloaded from xda). This is causing the phone to power on; it shows the Samsung Galaxy S 4g load screen, then Overstock, then the T-Mo logo sign (with the music), and then a longer Galaxy S load screen. After the load screen, the screen goes completely black, but all the touch buttons light up. Once like this, I can turn it off, and make it go back into recovery mode and also download mode.
Please help. I've been trying to solve this with my friend for about.. 4 hours.
P.S. I've looked up all the guides for using ODIN to get back to JFS, none works due to the reason that when I put it back into download mode, the computer does not recognize it. But it does at the same time. (it shows the "safetly remove hardware" and says that is an "USB mass storage device" ((but does not appear in "My Computer" when in the unresponsive screen-- but when in the download screen, it shows the same thing, only labeled "SAMSUNG USB Composite Device", which also cannot be accessed through "My Computer")
P.P.S. I'm sure it is a Samsung Galaxy S Vibrant, exclusive from T-Mobile. My computer is Windows Vista 32-bit, and I have as many Samsung drivers as humanly possible when it comes to the Vibrant.
Can anyone help a poor fool?
Try this, get in to download mode, open Odin, then disconnect the usb cable, then reconnect the usb cable and Odin should recognize it then. Good luck!
Using XDA premium, you should be too!
johnny12times said:
Try this, get in to download mode, open Odin, then disconnect the usb cable, then reconnect the usb cable and Odin should recognize it then. Good luck!
Using XDA premium, you should be too!
Click to expand...
Click to collapse
Sorry. That did not work. It just doesn't recognize it in ODIN when in download mode. My computer doesn't even see it. But it does say "Safely Remove Hardware" -- "SAMSUNG USB Composite Device"
Sounds really odd. Do you have any roms you can try reflashing from recovery?
Using XDA premium, you should be too!
depaer said:
Uh hi.
I'm a herp.
So I may have accidently tried to root and flash my friend's Samsung Vibrant. It was going smoohtly but now, I'm all sorts of messed up.
The problem: I may have used the wrong kernel (zImage) when using heimdall-frontend (which I downloaded from xda). This is causing the phone to power on; it shows the Samsung Galaxy S 4g load screen, then Overstock, then the T-Mo logo sign (with the music), and then a longer Galaxy S load screen. After the load screen, the screen goes completely black, but all the touch buttons light up. Once like this, I can turn it off, and make it go back into recovery mode and also download mode.
Please help. I've been trying to solve this with my friend for about.. 4 hours.
P.S. I've looked up all the guides for using ODIN to get back to JFS, none works due to the reason that when I put it back into download mode, the computer does not recognize it. But it does at the same time. (it shows the "safetly remove hardware" and says that is an "USB mass storage device" ((but does not appear in "My Computer" when in the unresponsive screen-- but when in the download screen, it shows the same thing, only labeled "SAMSUNG USB Composite Device", which also cannot be accessed through "My Computer")
P.P.S. I'm sure it is a Samsung Galaxy S Vibrant, exclusive from T-Mobile. My computer is Windows Vista 32-bit, and I have as many Samsung drivers as humanly possible when it comes to the Vibrant.
Can anyone help a poor fool?
Click to expand...
Click to collapse
Sounds like you used the wrong odin files. if your screen is showing a galaxy s 4g logo then you must have mistakenly flashed a galaxy s 4g odin/heimdall package. on the back of your phone what is the model number. What on earth is JFS? ive heard of JFD which is the stock firmware that the phone shipped with.
If you flashed the wrong bootloader you are more or less stuck between a rock and a hardplace and will require a jtag. now the fact that teh screen does turn on is a good thing.
You need to keep trying to get it into download mode maybe try using a jig. Once youve gotten it into download mode try every single usb port you can find on your pc. When i need to odin i need to use one of my usb ports on the rear io panel none of the others will work. Once you get odin running and recognizing your device use the files posted in my sig as the odin files. any others and i cant help you cuz i dont know what your source is. Odin should be able to recover your device if it is still booting to the splash screen.
If for whatever reason you cant boot into download mode but can get into recovery here is what you do: make sure you have the android SDK installed (dont know what that is go here: http://developer.android.com/sdk/index.html and follow their directions) then open up command prompt while in recovery type the following command: adb reboot bootloader this should put you into download mode. If nothing ive mentioned works you may require a JTAG there is a company called MOBILETECHVIDEOS (http://mobiletechvideos.mybigcommerce.com/) that has a JTAG service.
Good luck
-Cheers
Picked up a new HDX 7. Powered it on for the first time today and run into a white, what looks like diagnostic, screen. I tried a reboot and it just comes back to this screen it never actually boots into the os. Has anyone ever seen this before? Any recommendations?
Very interesting!
Is the device detected by your computer?
Yes i believe it is. It did install drivers when i connected it but I couldn't tell you what off hand. I'm away from my pc at the moment but I'd be happy to post whatever.
Thanks again
Please tell us as what it presents itself to the pc.
looks like it has some kind of factory debug firmware installed. some devs may be very interested in this indeed.
If you manage to boot into Android please don't let it upgrade before we can get our hands on the (hopefully) juicy debug build.
I tried everything i could think of to get it to boot normally. I even booted with power and the + button and did a factory reset and it still boots to the same white screen. I received a replacement from Amazon and was planning on shipping this one back today. I have a few more days before i have to ship it back though. I'll plug it back into a pc and see what it shows up as.
Alright. At the white screen when I connect to the PC I get two devices.
USB Composite Device
Remote NDIS based Internet Sharing Device
If i boot with the - held down I get to fastboot. If i connect it to the PC I get a Ready message on the screen and two devices show up.
android USB Composite Device
Unknown device USB\VID_1949&PID_000C&REV_0100&MI_00
Thanks,
shorts
shorts said:
Alright. At the white screen when I connect to the PC I get two devices.
USB Composite Device
Remote NDIS based Internet Sharing Device
If i boot with the - held down I get to fastboot. If i connect it to the PC I get a Ready message on the screen and two devices show up.
android USB Composite Device
Unknown device USB\VID_1949&PID_000C&REV_0100&MI_00
Thanks,
shorts
Click to expand...
Click to collapse
Is the device properly detected/can you actually run commands in fastboot?
http://forum.xda-developers.com/showthread.php?t=2799793
I was just looking at that page. I tried to run fastboot -i 0x1949 devices and got nothing, but from my brief browsing of that thread it sounds like i may need to try it in linux, my other concern is it sounds like i need a special usb cable to make this work in fastboot?
shorts
Maybe we should collect some money and buy you a new one, that you can give that device to some advanced developer here. Is that some option for you shorts? And would there be dev here who is interested in doing the job?
Did you get another networking device from the NDIS connection? Maybe there are services listening on the device so you should try scanning for open ports.
hi there,
recently I was using Meldrak's stock rom, my device went dead so I plugged it in to charge it, I went to use it and nothing happened.
I noticed that when I tried to turn it on, it would vibrate on, and then vibrate off straight away.
I can get into apx mode, so I thought I would try and use nvflash/wheelie to see if i could recover it, but on the first step of
"wheelie --blob blob.bin"
it comes up with error 3 receiving response from command.
any ideas on this? I've noticed people have said use a different nvflash and all that but it didn't seem to work for me.
I'm using win7.
I've installed the newest naked drivers
thank's, I think i got all the details.
(my girlfriend is going to kill me if I cant get this going)
addtional info:
as I have somewhat given up for now, my girlfriend has come in and tried to turn it on, my laptop has picked it up like normal, its come up as a portal media drive.
edit#2: somehow managed to get into fastboot, I am able to do the reboot command, so thats something, I think I might just keep putting up my progess, not sure how much further i'll get though.
edit#3: seems i can write with fastboot, but not making any difference, but when i go "fastboot reboot" computer is finding it as a mpt device but drivers have an error by the looks of it. heres a thought, could my screen be broken? id really kick myself if it was.
edit#4: so i just did the steps off http://forum.xda-developers.com/showthread.php?t=2800506 post #5, only did the fist part, only getting 1 vibration now, and computer is picking it up as a mpt device but still no screen.
just realised its not going into fastboot now. oh no......
malgora said:
hi there,
recently I was using Meldrak's stock rom, my device went dead so I plugged it in to charge it, I went to use it and nothing happened.
I noticed that when I tried to turn it on, it would vibrate on, and then vibrate off straight away.
I can get into apx mode, so I thought I would try and use nvflash/wheelie to see if i could recover it, but on the first step of
"wheelie --blob blob.bin"
it comes up with error 3 receiving response from command.
any ideas on this? I've noticed people have said use a different nvflash and all that but it didn't seem to work for me.
I'm using win7.
I've installed the newest naked drivers
thank's, I think i got all the details.
(my girlfriend is going to kill me if I cant get this going)
addtional info:
as I have somewhat given up for now, my girlfriend has come in and tried to turn it on, my laptop has picked it up like normal, its come up as a portal media drive.
edit#2: somehow managed to get into fastboot, I am able to do the reboot command, so thats something, I think I might just keep putting up my progess, not sure how much further i'll get though.
edit#3: seems i can write with fastboot, but not making any difference, but when i go "fastboot reboot" computer is finding it as a mpt device but drivers have an error by the looks of it. heres a thought, could my screen be broken? id really kick myself if it was.
edit#4: so i just did the steps off http://forum.xda-developers.com/showthread.php?t=2800506 post #5, only did the fist part, only getting 1 vibration now, and computer is picking it up as a mpt device but still no screen.
just realised its not going into fastboot now. oh no......
Click to expand...
Click to collapse
If you can fastboot with no display on, there might be some hardware defect.
As a last resort you can try following:
1. reset tab physically (put needle in little hole above hdmi slot)
2. unplug battery for 10 min.
3. fastboot another recovery.img
4. try the hdmi out to an extern screen (your tv f.i.)
das chaos said:
If you can fastboot with no display on, there might be some hardware defect.
As a last resort you can try following:
1. reset tab physically (put needle in little hole above hdmi slot)
2. unplug battery for 10 min.
3. fastboot another recovery.img
4. try the hdmi out to an extern screen (your tv f.i.)
Click to expand...
Click to collapse
Thanks for the reply, unfortunately it will not go into fastboot anymore, as many times as I tried it will only come up as android mpt device, my computer wont even pick that up right, (yellow triangle next to the icon in device manager) only other thing is apx mode but as ive stated i cant wheelie --blob blob.bin just returns error 3. might save and upgrade, to a newer tablet.
thanks for your suggestions though, much appreciated.
hi. so my problem is that my phone does not turn on, i cant go to recovery or do hard reset. the phone react when i plug it in PC without battery, but its always connect and disconnect over and over again. i have downloaded the omap drivers and instaled it. now i have in the device manager a OMAP4430 FastBoot USB device. by the drivers was a fastboot emulator. but when i will flash rom, kernel or recovery a just get partition does not exist. can someone help me please? srry for english.
Does your phone not turn on at all when holding down the power button? If it boots up, and gets stuck on a loop or has an error message, that is different. But if it doesn't turn on at all, then your battery is dead or something is wrong with your phone's hardware. If you connect your phone to the PC (with the battery on), does it at least show a light? Or does it boot up at all when you hold the power button? If it doesn't show a light or boot up, it is not your battery, but your phone's hardware. Your phone might have been dropped or water inside it or it was microwaved? I know it sounds silly, but something happened to the phone physically. Now if you connect it to the PC and you see a light but it never boots, your device is bricked. Not accusing you, but you might have tried rooting it or writing over a partition on your phone which caused to brick. Also, try typing in fastboot devices. If it shows up a device, that means it is connected. Cheers!
No the phone does not turn on and it shows nothing, even when i put it on charger. If i connect to pc with battery after i installed the omap driver it just connect and disconnect over and over again, windows make this sound when you connect and disconnect something. I have flashed a new rom. It has worked but after some time its stoped. So i have try flashed it again but i could not get in recovery. A files was missing and after i try flashing thhe recovery its just dead. I can connect it just with the fastboot emulator because it's don't connect when i just put it on pc. I must connect it without battery wait 4 sec and then put the battery back. Than i can see in the emu my phone but not able flash anything because of partition does not exist
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.