I have a hardware locked Vibrant, tried a billion combinations, nothing works. Phone is functioning fine and is 100% stock. The Vibrant I returned which was soft bricked did the same.
When at the charging screen (green battery), an unknown device, per Windows, is detected for a few moments before it disappears. I have the Samsung drivers installed, which work fine for Odin and ADB.
What is this mode/device that is being detected momentarily? Searched around and read countless threads but could never find an explanation.
Related
Hey folks,
Sooo yeah, won't bore you with the sordid details of how incredibly careless I am, but all you really need to know is that the Vibrant and Diet Code are not what I would call simpatico. Yeah, so it was saturated in Diet Coke for what could have been as long as 20 or so minutes. FML.
So I did the typical hurriedly drying it off, popping out everything I could (SIM, SD Card, and Battery), drying all off best I could, and when I got a few hours later I let the phone and battery "soak" overnight in a bowl of uncooked rice.
Where we are now:
1. When off and plugged in via USB cord, the charging battery icon displays on screen.
2. When turned on, phone will display Vibrant screen for a few moments, then go dark, then loop back to Vibrant screen, rinse, repeat, etc...
3. I am able to get into Recovery mode, however it gives me an "Unable to mount sdcard" error msg when I select reinstall packages. (Hence have been thus unable to access my Nandroid backups.)
4. Phone loads into Download Mode just fine, but ODIN will not detect it. Have tried multiple combinations (plugged in with ODIN running, without ODIN running, unplugged and replugged with ODIN running, without, USB port on front and back, etc...). However, my computer itself DOES appear to recognize the Vibrant once plugged in as it does beep and says "Successfully installed SAMSUNG Composite Device", etc etc...
I have uninstalled and re-installed the Samsung drivers found in the forums here to no effect (running WinXP 32bit, made sure I had the right drivers). At this point I am WELL aware of the possibility that my beloved Vibrant is TOAST as no doubt Diet Coke is even worse than water, BUT the phone HAS made some slight improvements... before it would not even display the battery icon or Vibrant screen.
One thing I haven't tried yet is ADB (largely due to the fact that I do not know ADB commands/abilities well enough to know how and if it could even help in this case).
Unfortunately I had no need/want to use ODIN before the mishap, so I don't know if ODIN would have just picked it right up before...
Any thoughts or feedback would be welcome if you see some gross error or just something I haven't tried yet.
Thanks for reading!
What version of Odin are you using?
That would be Odin3 v1.00
themoebius said:
That would be Odin3 v1.00
Click to expand...
Click to collapse
There is a stable release of ODIN in the bible under development section give it a try
Yeah unfortunately just tried it (ver 1.52 now). No joy.
I am having the same problem trying to play with custom ROMs. I was wondering if you got your phone back. Or is it gone for good ! :'( I thought SGS phones were unbrickable !
I am pretty sure that someone has posted something similar to my problem, but I can't find anything that gives a straight up answer or seems to kind of deviation of the problem.
So I do have cyanagen mod 10 stable installed on my phone and it has been great... No problems what so ever. I'm not sure if something happened or if it was something that I had changed, but the only thing system wise that I had changed was under the ROM Tool Box, I had edited the screen settings to change the dpi of the screen. However, everything worked fine after it changed and rebooted. In fact, I loved the fact that screen was now "bigger..." Meaning that it made the icons and text smaller.
So, now the problem comes, now the phone doesn't load up. The battery died and I plugged the phone into charge it and it turned on like normal with the little loading image of a circle (like the one you seen when a flash file is loading) and then it blinked and did it again, but then nothing. Normally if you let it sit for a second and press the power button, it would show an image of the battery charging. But it doesn't. If I press and hold the power button, it starts to laod up and says "Samung Vibrant" then goes black, and then repeats Samung Vibrant again and again....
Now I am not a super genius on the android thing, but I have flashed many different ROMs and thought I had bricked my phone many times as well, but always have been able to bring it back to life. I am actually starting to think of my phone as "Frankenstien" since it has died and came back so many times...
Now, I have tried to reboot into recovery mode but doing the volume + and - and power, didn't work.
I have tired to boot into download as well...
The phone can be plugged into the computer and it recognizes it as far as sending out a charge to "charge" the phone, but it does not recognize it in Kies or in Odin. I reinstalled the drivers as well and still not recognized... I know the phone is "old" as far as that goes, but it was working fine and currently unemployed, so every penny counts.
Suggestions?
I've seen many posts about this but none of them actually has a solution that worked for me.
I have a Sensation XE, I don't know the cause of the problem exactly, but I had it on recovery and it discharged (deep discharge).
Now whenever I try to turn it on, the red led on the left top corner turns on, sometimes the device vibrates, but the screen stays off.
I tried to go into bootloader but with no luck, same for recovery.
The charging orange led does light up when the device is plugged in, and I've checked the battery, it's functional. I even tried another battery just to make sure.
I tried to charge it overnight, and I tried to charge the battery on it's own, with no luck.
One thing I found right before I post this is charging the phone with the battery out!
Now I don't know how that might help as the device doesn't boot with no battery, but I tried it anyways just to make sure I haven't left anything to chance, and it didn't work.
This thread might come in handy for other people with the same situation.
Windows 7 recognizes the device when plugged in as "Android ADB Interface" but when I use "adb devices" it doesn't show anything.
I tried the Sensation Unbricking Project, the terminal always said "Bricked device found on." but it doesn't give me the next line "sdX", I think it doesn't recognize the device.
In the video when the device is plugged in, Ubuntu immediately recognizes it and it even opens up the device's files, that does not happen with my device.
I don't remember exactly my bootloader information, but I think my HBOOT version is 1.27, not sure about that.
I have bootloader unlocked with S-ON, and I had a custom ROM running for over 3 months when all this happened.
I hope you have all the info you need to help me, if not just ask me, any help would be much appreciated.
Thanks in advance.
My S9+ was acting quite weird this morning. Some apps continuously crashed or wouldn't start.
So i rebooted my phone (just from the normal power button menu) and then it went completely black.
It doesn't charge (or at least, it doesn't show it charging), it doesn't respond to forced resets and the screen is completely black.
The only thing it does, is briefly show a USB device when connecting it to a PC.
I've connected it to a Linux dev computer i have laying around and i see the following device connected briefly:
VID: 0x04e8
PID: 0x1234
It stays connecting longer if i hold the power button (about 8 seconds before power cycling).
The only things i could find online were some very old threads about Samsung's DNW mode, but nothing from this decade.
I think my Flash chip might be cooked, but i hope i'm wrong.
Anyone got any experience with this?
Update
I've sent it back to Samsung for repair under warranty.
The flash chip was gone. It started corrupting writes and finally it was so far gone that it couldn't load the bootloader.
They've replaced the main board and battery (probably because they tested it and saw it was going bad), that fixed it.
Hi to all the XDA community,
It looks like that I am a new member but I have been for several year on XDA (but I lost all the log in details).
The problems I am facing is with a Samsung J6 that my mother in law gave me because one morning didn't show anything on the screen. These are the steps I did:
1. Screen is black, first thought lets charge it. I kept on the charger for ages. When I got back home I was sure that the phone is fully charged (it shows it on my usb hub). Tried to switch it on - Result, nothing is coming up to the screen
2. Hard reset by pressing power button and volume up or down - Result, nothing is coming up to the screen
3. Connect the phone on a laptop to check if the laptop recognises it. The laptop is doing the noise that something is connected and start installing drivers. Seconds later the device disconnected and connected again and this loop of connection and disconnection is happening for ever -Result nothing, only question marks.
4. Thought that is a hardware failure and since the screen doesn't shows anything I bought a new screen. I didn't by an OLED, I bough the cheap one. - Result, nothing is coming up to the new screen
5. I disconnected the battery and install the screen again connect the battery and try the same steps 1 & 2. - Results the same as the steps 1 & 2.
For me it looks like that the phone is bricked (I forgot to mention that my mother in law gave it to someone else before she pass the phone to me, no trust ) and the other guy probably tried to change the ROM or something similar. The boot loop that the phone is doing when I connected on my laptop is not normal (noise of connection and after 1sec noise of disconnection).
Additionally, I am not sure if the screen is working and I am on dilemma, do I have to return the screen to the seller of keep it until find out what is the problem with the phone. Maybe the screen is the faulty part that cause another issue. When I connect the phone on the laptop without the screen is doing the boot loop noise of connection/disconnection. I found out that when the phone is connected on the laptop and I press the power button the disconnection noise is delayed by couple more seconds.
Any help or guidance will be more than welcome.
Obtain the Stock image for your fone from samsung, load it into the version of Odin they suggest, but dont start it yet.
Disconnect fone from pc, and turn it off.
Start Odin flashing
plug fone in
Mb a few steps dif since I last flashed a samsung, but this will fix your fone.
Make sure you got the samsung driver installed in your pc
Pachacouti said:
Obtain the Stock image for your fone from samsung, load it into the version of Odin they suggest, but dont start it yet.
Disconnect fone from pc, and turn it off.
Start Odin flashing
plug fone in
Mb a few steps dif since I last flashed a samsung, but this will fix your fone.
Make sure you got the samsung driver installed in your pc
Click to expand...
Click to collapse
Thanks for your response.
Samsung drivers are already installed.
The problem that I am encountering is that I can put the phone on download mode. Firstly because I can't see anyhting on the screen and secondly because my laptops can see the device. I tried different cables too but nothing worked.
Since the phone cannot be recognised by the PC, the Odin app cannot see it either.