I have a Vibrant that I believe may have hard bricked when odin crashed/froze during last 10% of install and now the phone wont turn on and boot, go into download mode by means of jig, pressing both vol up and down at the same time as the power button or other various jump start methods, as well as wont go into recovery. I've just ordered a new break out jig and I'm curious to see if it will work for this or like my other jig be ineffective. The Vibrant came to me disassembled, and immediately upon reassembly I experienced booting issues with it. Sometimes it would boot up revealing the home screen before it would shut off and others it would barely flash the first splash before shut off. I'd see similar behavior when I attempted to boot to recovery, but then when ever the phone was in download mode it would stay on. I flashed it several times with odin but it would never really stick. The last couple attempts had shown promise when it would start making it further into the boot process before the attempt when odin froze during the install of the rom and I can only think that now it's hard bricked. Now that my friend has brought me his Fascinate that is showing similar characteristics within his phone, I'm hoping for some help with understanding whats causing these problems. His phone wont boot unless it is plugged in, however it will continue to function after unplugging the charger from phone. That just makes me think of the Vibrant and how it would only stay on in download mode, but the 2 situations could be completely unrelated in the cause of the boot issues, if you can please help.
[email protected] said:
I have a Vibrant that I believe may have hard bricked when odin crashed/froze during last 10% of install and now the phone wont turn on and boot, go into download mode by means of jig, pressing both vol up and down at the same time as the power button or other various jump start methods, as well as wont go into recovery. I've just ordered a new break out jig and I'm curious to see if it will work for this or like my other jig be ineffective. The Vibrant came to me disassembled, and immediately upon reassembly I experienced booting issues with it. Sometimes it would boot up revealing the home screen before it would shut off and others it would barely flash the first splash before shut off. I'd see similar behavior when I attempted to boot to recovery, but then when ever the phone was in download mode it would stay on. I flashed it several times with odin but it would never really stick. The last couple attempts had shown promise when it would start making it further into the boot process before the attempt when odin froze during the install of the rom and I can only think that now it's hard bricked. Now that my friend has brought me his Fascinate that is showing similar characteristics within his phone, I'm hoping for some help with understanding whats causing these problems. His phone wont boot unless it is plugged in, however it will continue to function after unplugging the charger from phone. That just makes me think of the Vibrant and how it would only stay on in download mode, but the 2 situations could be completely unrelated in the cause of the boot issues, if you can please help.
Click to expand...
Click to collapse
I have Jtag solve for Hard brick phone
Please PM me or check out at my signature.
Related
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
itsjuztin said:
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
Click to expand...
Click to collapse
Here's some tips:
1. NEVER restore non-cm7 nandroid backups on a cm7 based rom.
2. Flash stock JFD with repartitioning checked to go back to stock.
3. Reflash vibrant bootloaders. You may have some captivate bootloaders or a mismatched param.lfs that's causing the AT&T bootsplash. It could be one or the other and mismatching captivate and vibrant bootloaders or params could lead to a brick so just flash the vibrant bootloaders since it contains both bootloaders and param.lfs.
4. DL mode depends on the bootloaders you run.
Froyo bootloaders-------------
1. Volume up and down with USB inserted and with battery disconnected
2. Insert battery without letting go of buttons
Gingerbread bootloaders-------
1. hold power and volume up with the battery inserted and with the phone powered off
2. connect USB to pc when booted into DL mode.
P.S. Can you take a picture of the front and the back of the phone so I can identify the kind of phone you are using at this moment?
The name you are using for the device you have is kinda confusing me.
I believe I'm running ICS Passion, I'm not sure what version
Last night I turned my Vibrant off. It wasn't anything special, just a boot because my messenger app wouldn't open. However, when I got home and tried to turn my phone back on the phone will take an unusually long time to get past the loader, and then the boot animation seems to run forever. I left it on overnight and my phone was not booted in the morning. The process seems to take up a lot of battery as well. I'd like to avoid flashing another rom because I haven't had preparation, but I need to update soon anyway so it's not completely out of the question. How can I attempt to fix this?
Odin back to stock
djquick said:
Odin back to stock
Click to expand...
Click to collapse
I figured I'd have to do this.
I used my home made jig to get into download mode (because the three button combo isn't working) however my computer is refusing to recognize the device when I open Odin. I'll try on my desktop when I get home, but for now I'm just going to let the phone boot and see what happens.
I'll post back if I still can't odin to stock.
Ok snoot sure if anyone has experienced this but randomly after using my phone this morning I noticed it was getting really warm in my pocket. I took it out only to realize I am stuck in a boot loop. I can hold volume down and power and get into hboot, but none of the options....even factory reset do anything, just sends the phone into another boot loop. The kicker is that I have never even attempted to REIT my phone yet. Any suggestions other than going to Verizon and taking my chances there?
Have you tried holding down the power button for 10 seconds to hard reboot the device?
If that doesn't work, try getting the phone into the bootloader, connect it to your computer and try to flash an RUU from there. There's a link to the download for it in the development section, along with guides on how to use it. If you can't flash the RUU, post back here and we can help with that, but if the RUU flashes successfully and it still boot loops, there's probably not much to do except take it back.
Hi All,
I've run into an odd problem. My S4 completely died on me last Saturday. I can access recovery and Odin Mode, but only if the phone is plugged in. No response from any combination of buttons should I try them without the plug in.
When I plug the phone in, it brings me to a boot loop of the battery icon with a circle indicator through it. Leave it long enough, and it'll turn off, vibrate, and do the same thing again. From what I understand, this is a problem with the main board, or the PBA. However, I figure I should try everything before I send it into Samsung for a repair.
I want to flash a factory image through Odin, just in case that could possibly be an issue. If the phone flashes correctly, but still won't boot, is that dangerous? (i.e. the phone needs a complete boot after flashing with Odin).
If I can freely flash without any side effects due to my issue, what would be the safest image to flash to it? I don't remember the name of it off-hand, but I think there were three I knew about.
My phone does come up as COM9 through Odin, so it recognizes there's a device.
Are there any risks to doing this, or should I skip all this work and just send it to Samsung?
Thanks in advance.
Odin help
buckoman said:
Hi All,
I've run into an odd problem. My S4 completely died on me last Saturday. I can access recovery and Odin Mode, but only if the phone is plugged in. No response from any combination of buttons should I try them without the plug in.
When I plug the phone in, it brings me to a boot loop of the battery icon with a circle indicator through it. Leave it long enough, and it'll turn off, vibrate, and do the same thing again. From what I understand, this is a problem with the main board, or the PBA. However, I figure I should try everything before I send it into Samsung for a repair.
I want to flash a factory image through Odin, just in case that could possibly be an issue. If the phone flashes correctly, but still won't boot, is that dangerous? (i.e. the phone needs a complete boot after flashing with Odin).
If I can freely flash without any side effects due to my issue, what would be the safest image to flash to it? I don't remember the name of it off-hand, but I think there were three I knew about.
My phone does come up as COM9 through Odin, so it recognizes there's a device.
Are there any risks to doing this, or should I skip all this work and just send it to Samsung?
Thanks in advance.
Click to expand...
Click to collapse
In the past the only time when I odin back to stock and It did not boot up I went to the stock recovery and did a factory wipe and started like a charm
Hey guys, I have some serious problems.
So after reading threads and forums for 3 days now, I still can't make my g2 work again. So the problem is that my phone, out of nowhere just turned itself off, and now is in a bootloop. I had that once before, I did a factory reset with the buttons, and it was working again. Now it happened again, but when I try to do a factory reset, it freezes, and doesn't do anything at all. I tried this several times, nothing. I want to say, I don't know anything about custom roms, ive never tried to do a firmware update on my own, or tried to unlock bootloader, so you know I can't even do any of these. I always left my phone's system in its factory shape. But still this happens to me, and I can't boot into download mode even, my computer recognizes my phone as an USB charge only interface. I read about lots of solutions, and i can't even do them because my phone doesn't load the download mode. I hold volume up, plug in the cable, it tells me to keep holding, and after 30 secs, it goes to something thats gotta be fastboot mode (the last entry is fastbootrocessing commands). I don't know anything about developing or what, so please guys help me