Hey everyone! This could be a shot into the dark since people have basically stopped posting on this portion of the website for years. I have a Samsung Vibrant that was bricked over a year ago. If I'm correct the way to get into recovery mode is Vol Down + Home + Power for the Samsung Vibrant. Here's the thing: Normally when the Samsung Vibrant boots, the bottom 4 buttons light-up and respond to when I touch them. Bur now that the device has been bricked due to some sort of error when installing a custom ROM, I can't access recovery mode. I have also tried to access download mode using various button combinations I've found online but to no avail. The phone simply just turns on and is stuck on the Samsung Vibrant screen. It never shuts off and boot loops. It simply just freezes on the Samsung Vibrant screen. When I plug it into a wall, the phone shows me a frozen loading icon which I assume is supposed to be the battery indicator when the phone is powered off. I've tried connecting it to my PC regardless of not being able to get into download mode but my pC does not detect it at all. Nothing in Device Manager either. I've also tried to install Samsung's official USB drivers for the device but my PC still does not detect it. I've tried connecting it to Odin. Nothing. I've tried ADB. Nothing. I am not one to solder or make a USB jig so my options are running out. I understand that it's 2020 and it's likely no-one will see this but if anyone does, please help!
Related
First thank you for viewing my question and issue.
I'm new in here hoping to find a solution to my problem. I bought a used S4 I9500 last year it was lagging acting up slow did a search and read online that I might need to install better version via Odin (I'm totally new to the android world so I think I did a mistake here somewhere). So I did install I9505 version which I thought will work fine. (sorry for not doing enough researches coming from IOS which is less complicated). The phone apparently did a restart and got stuck on the Samsung logo which kept glowing for few minutes.
It was mid night by the time I was cracking this stuff out, so thought to myself to keep it plugged and go n rest for few hours. I woke up and the Phone was still stuck on the Samsung logo which was glowing not like paused or something. The phone was hot so i thought I should stop the whole operation before something worst happen. Did some searches and found that people are fixing this issue by going to recovery mode or download mode etc.
The thing is Vol+ and home button + power or Vol+ and power trick doesn't show the menu anymore. When i click any of these it just does a random reboot showing Galaxy I9500 logo and then back to the glowing samsung logo. notice that I was able to go to download mode and recovery mode prior to this issue but now I just can't for some reasons.
Would appreciate any help. Thank you
Find someone that can use Jtag maybe they can fix it.
Hard lesson for you. Never flash a firmware for another device onto your phone.
If they can't fix it, then you can buy a new phone. You bricked it.
So, I rooted and tried flashing the stock ROM (from Sammobile, same country, same exact model [SM-G950F], I already had the stock ROM and had never flashed anything else to the phone other than root, June security update, my phone had July's) to see if I could fix a problem that couldn't be fixed with any other method I had tried.
Everything in Odin seemed to go well, I got the PASS green box at the end. But then the phone couldn't go pass the Samsung logo when booting up. I left it quite a few minutes, before trying to boot into recovery mode and wiping data. Only to realize that I couldn't boot into recovery mode. In fact, I can't even turn the phone off. No combination of hardware keys works other than power button + bixby + vol down, to get into download mode. But that's of no use, because when I plug my phone into my PC (with the same cable and port I used before to root and flash the firmware into it) it is not recognized by Odin or the PC.
It just has the Samsung logo flashing slowly over and over because I can't turn the device off. By the time the battery dies out I'll most likely have the logo burnt into the display.
I also haven't been able to find any help online. Everyone's suggestion is “boot into recovery and wipe data”, but I can't do that.
Is my phone gone for good?
My device restarted and after a software update and got stuck on a boot loop. I was able to get the phone initially into download mode as I thought I would try flashing it with ODIN back to the previous firmware. But since I haven't been to Sammobile in years, I didn't realize that the download would take hours.
So i tried force rebooting the phone again (vol down+power) in the meantime and nothing happened it was still stuck on the boot screen. So I left the phone connected to the charger and after a while I saw that it was back in downloading mode (but no ODIN mentioned in the top left corner)? I thought that was strange and since I had the download ready to flash, thought to make sure it was in download mode (proper) by pressing power+vol down+home. But this time the screen went black and now seems to be hard bricked and completely unresponsive (with only the blinking blue led) -. I've scoured the interent and the consensus seems to be that a USB jig won't work, will try it though. I'm really looking for an unbrick image to try booting it from the SD card. Would really appreciate the help! I've already tried the adb reboot download etc, but my computer and another one doesn't seem to detect the device. Please help!
I recently got a wifi model S5e and I believe the previous owner did not know what he was doing, and tried to updated the firmware through Odin and messed it up. Whenever the tablet is plugged into power or a USB port, it will boot to "An error has occured while updating the device software. Use the Emergency recover function in the Smart Switch PC Software" screen, then restart itself after a couple seconds. It does this the entire time it is plugged in. I can hold the VOL keys then plug it in and I get to the "Custom OS" screen, but it does the same thing and reboots after a couple seconds. Is there anything I can do to get it to stay on long enough to flash new firmware to it?
nighcore said:
I recently got a wifi model S5e and I believe the previous owner did not know what he was doing, and tried to updated the firmware through Odin and messed it up. Whenever the tablet is plugged into power or a USB port, it will boot to "An error has occured while updating the device software. Use the Emergency recover function in the Smart Switch PC Software" screen, then restart itself after a couple seconds. It does this the entire time it is plugged in. I can hold the VOL keys then plug it in and I get to the "Custom OS" screen, but it does the same thing and reboots after a couple seconds. Is there anything I can do to get it to stay on long enough to flash new firmware to it?
Click to expand...
Click to collapse
Call Samsung at 1-800-SAMSUNG. I messed up my tablet the same way. I had someone local look at it, but they couldn't fix it. I sent it to Samsung and they fixed it for free, but only because it was still under warranty. They can check your serial number to see if yours is still under warranty.
Seeing as they have a customOS installed on their device. Samsung won't touch it as it has been rooted, which breaks the warranty.
Reboot to your "custom recovery" and flash that "custom os" again?
I have an HTC U Ultra and it suddenly froze last night. Upon rebooting it, it started until the HTC logo screen and then shut down. I tried several times but got the same results. As a last hope I tried going into the Recovery by holding volume button and power but the same thing happens here as well, HTC logo pops up ( a different logo, this one has a reflection under the HTC text, which means the phone did try to access it) but then it shuts down again. Since I cannot access the Recovery I cannot know what is going on. Kindly help me out in finding how I can access recovery mode or any other workaround.
I cannot use ADB either as it would need an opened phone with debugging enabled. Kindly help me out.