[Q] Vibrant Passes Boot Screen, Then all black - Vibrant Q&A, Help & Troubleshooting

Hello!
I'm new here, love the forums. However, I may have bricked my device and the threads I have read so far (I've read a lot of them), aren't helping.
I flashed (via ODIN) the stock JID and PIT files according to http://forum.xda-developers.com/showthread.php?t=734475. The flash was successful however when I go through the boot Cycle, I get the 'Vibrant' boot screen, then the T-Mobile splash, and finally the Galaxy S screen with the pulsating S.
However, after this the phone goes black, and I only have the four buttons lit up. They do respond to touch.
Please help with this situation. Thanks in advance!

Hey Swaadg,
I had this happen when I first got my vibrant. Try Odin again and if it fails, redownload it and try again. If that fails, try downloading Odin from a different source: http://forum.xda-developers.com/showthread.php?t=821625. If that still fails, check out this program: http://forum.xda-developers.com/showthread.php?t=954509 Good luck!

As long as you can get into download mode, there is hope.
If you flash a good JFD image with a good Odin and it still doesn't work, that's a weird one.
You might fix what you've got by getting into recovery mode and doing a factory reset.

So I flashed the T959UVJFD.tar via ODIN3 v1.70. Now I get the Vibrant (Samsung Boot Screen), followed by the T-Mobile splash, followed by the Galaxy S pulsating screen.
Then it goes black. The four LED buttons on the bottom do however respond to touch. I just see a black screen.
One irregularity during the flash is that it fails to wipe the data during the reboot after flash.

Are you checking any extra options in Odin, or just what's checked by default?
I would recommend flashing with only auto reboot and F. reset time checked.

See the attachment showing how I flash with Odin.
Thanks for all your help!

I have sucessfully booted this helped for anyone with the issue in the future:
http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150

Related

[Q] Endlessly boot loop...

So this phone is really frustrating me...
I tried this method:
http://forum.xda-developers.com/showthread.php?t=849028
I think I make all the step correctly.
1. Installed drivers on my pc.
2. Downloaded 3 files: ODIN, PIT and PDA.
3. Put the Vibrant on Download mode.
4. ODIN detected it, I selected the 2 files... I tried with RePartition check and uncheck...
5. Then hit start, everything runs fine and ODIN indicate PASS.
But... Still boot looping...
When I boot to recovery I have the original recovery (2e).
Can someone help me please? Im really frustrated.
All of this begin because I made a mistake and used a Samsung Galaxy S 4G rom to flash it using ODIN...
I know it has solution because its boot looping.
Best regards,
Omar
I'll link you to some files that may do a better job. I can't tell for sure if you're actually using the right files to flash your phone back to stock or not. Chances are, you're not. Check your messages, and I'll link you to the files in my Dropbox to download.
can you show links here or link me as well. I am having the same problem and i have tried flashing a whole bunch of vibrant roms/kernels but cant stop the phone from boot looping. Thank you.
I would also like to get these files, having the same problem and tried the same methods to fix it and nothing...
Once you got to the point to boot up, did wipe Dalvik, cache and reset first and then try to boot? This is ususally the reason for bootloops.
For some reason I can't get into recovery (holding the 3 buttons) now... I can get to download mode, though.
This phone was bricked and could restore the bootloader with a Riff Box. Now, after the Vibrant screen, the phone turns off.

[Q] Boot loop after flashing JFD via Odin3

Hello again fellas, I'm hoping someone helps me out of a bind I'm currently in. I just flashed JFD, but the phone is stuck in a boot loop. Here are the symptoms:
After Odin3 shows PASS:
1) Phone turns off, but instead of rebooting, shows transparent battery icon with spinning splash, blank screen, transparent battery icon with spinning splash.
2) If I disconnect from the PC, then turn on, the phone shows a WHITE screen, then the VIBRANT screen with Samsung at the bottom, then white screen, and back to the Vibrant screen.
I have obtained the same results wether "Re-Partition" was clicked or not. I am in the process of d/l AIO Vibrant Toolbox from Bay-Wolf. In the meantime, if anybody has any ideas, I'm all ears (eyes in this case). Thanks.
Did you put the proper pit and tar files in their place? Just try to flash again, you might have just had a bad flash.
Hey, thanks for the reply. After reading your reply, I checked the .pit and .tar files but it checks out.
I have also tried using AIO toolbox and used the files provided by the program but I get the same results. The odd thing is that Odin shows pass. Could it be bootloaders? I know those are sometimes an issue with Captivates, but I don't know about Vibrants.
I have a similar problem, haven't been able to solve it but try this: http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150
Hope it helps.
Just to be sure...can you try with the files available on this post, following the provided steps:
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Look fellas this has been said hundreds of times around here.
When you flash JFD, untick reboot, when using Odin, because then it gives you a chance to do the data wipe and then the cache wipe, this has been the main culprit in almost all boot looping. and do the same with other roms as well, people just immediately reboot after a successful load, and forget to wipe this data factory reset and cache, clearing this out allows no other ghost data from previous install and the present loaders to interfere with the first time boot up, I used to make this mistake, but since doing this it stopped the boot looping.
I want to thank you guys for replying and trying to help. I will look into the links provided above, and see what I can do. I apologize if I have asked a question that has already been covered here. I'm a frequent visitor to the Captivate forums, and I'm aware what's expected of every member before they ask aquestion. However, I am doing this as a favor to friend, and I'm not familiar with the nuances of flashing a Vibrant back to stock. I also didn't have the time to peruse the forums untill I came across a solution. Thanks for all the help, and I'll update you soon on my progress.
Sent from my SAMSUNG-SGH-I897 using XDA App
dseldown said:
Look fellas this has been said hundreds of times around here.
When you flash JFD, untick reboot, when using Odin, because then it gives you a chance to do the data wipe and then the cache wipe, this has been the main culprit in almost all boot looping. and do the same with other roms as well, people just immediately reboot after a successful load, and forget to wipe this data factory reset and cache, clearing this out allows no other ghost data from previous install and the present loaders to interfere with the first time boot up, I used to make this mistake, but since doing this it stopped the boot looping.
Click to expand...
Click to collapse
Can you clarify what you mean be "it gives you a chance to do the data wipe..."?
I tried Odin and unticked reboot and then after Odin says successful, nothing happens. There is no window that pops up on the computer or the phone that gives the option to do a data wipe.
I know there's a data wipe and cache wipe option in CWM, but I can't get into CWM or any sort of recovery mode right now...
you're clarification would be greatly appreciated so that I can get out of this bootloop nightmare
So....
kafepuya said:
Hello again fellas, I'm hoping someone helps me out of a bind I'm currently in. I just flashed JFD, but the phone is stuck in a boot loop. Here are the symptoms:
After Odin3 shows PASS:
1) Phone turns off, but instead of rebooting, shows transparent battery icon with spinning splash, blank screen, transparent battery icon with spinning splash.
2) If I disconnect from the PC, then turn on, the phone shows a WHITE screen, then the VIBRANT screen with Samsung at the bottom, then white screen, and back to the Vibrant screen.
I have obtained the same results wether "Re-Partition" was clicked or not. I am in the process of d/l AIO Vibrant Toolbox from Bay-Wolf. In the meantime, if anybody has any ideas, I'm all ears (eyes in this case). Thanks.
Click to expand...
Click to collapse
Did this get resolved? I am in the same boat working on a friend's phone. Have never had an issue with Odin that I couldn't figure out. But now I'm four days in and about to pull my hair out so the magic fix would be greatly reassuring right now! Help.
You need to enter recovery mode and do data wipe. If it still don't work, try another Odin image.

[Q] No Boot After ODIN'd to stock

Hey all,
I had CM7 running on my Vibrant for about 2 months until today when I decided to try out some other ROMs. I got Team Toxic's Crazy8 installed but had an issue where the stock bootloader and recovery were reflashed somehow (I must have screwed something up while trying to edit my sd card partition). So every time Crazy8 would boot, it would act as if I made no changes whatsoever. After each reboot, it would boot without any of my settings, apps, etc. from the last boot.
So I decided to try Bionix instead and figured I'd have to get back to stock. I used ODIN to do this and after reflashing the stock JFD ROM, everything passes. My issue is that now when the phone boots up (after seeing the T-Mobile animation and jingle and the Galaxy S animated logo) the screen just goes black. Power button does nothing. If I hit any of the soft buttons, they light up but the screen doesn't respond at all.
I've reflashed using ODIN multiple times now and the same thing is happening. I've also followed the bootloop fix (http://forum.xda-developers.com/showthread.php?t=1108499) step by step but to no avail. I know my phone isn't bricked and I'm far from panicked. I just want my phone back.
Thanks in advance,
Luke
EDIT: Also, in the stock recovery (after resetting user data and clearing cache), when I hit reinstall packages it says:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
And then it just hangs there and the progress bar does nothing.
After some more research, I realized I'm getting the notorious mbr checksum error. Found this thread (http://forum.xda-developers.com/showthread.php?t=888084) and am currently downloading Eugene. I'll update this thread with my results.
EDIT: Finally got it flashed to stock, and it boots up past the black screen. It took quite a bit of digging and dead links to figure it out. Here is the exact procedure I followed:
1. Download Eugene's Froyo-that-does-not-brick here: http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.html
2. Open ODIN (as administrator if Vista or Win7).
3. Use the 512 PIT file and Eugene's PDA file (that you just downloaded).
4. Uncheck re-partition.
5. With the phone in download mode, start the flash.
6. When it is done, it will reboot into stock recovery and you won't be able to do anything. Unplug the phone and remove the battery for a second or two.
7. Put the battery back in, but DO NOT try and turn on the phone yet. Hold down just the volume up and down buttons.
8. Plug the USB cable back in. It should go straight to download mode. If you go back into the stock recovery, go back to step 6.
9. Check the re-partition box in ODIN and select the JFD PDA file.
10. Flash again.
You might still get the MBR error message, but you should at least be able to get back into your phone and it should otherwise operate normally.
After trying to fix my phone (black screen with lit soft keys, 2e recovery (no workie), MBR Checksum Error) for 2 days this finally has done it!!!
Thank you SO MUCH for posting this WITH a working link!! I won't ever delete that file again. You really are awesome!!

Rooted, Bricked Samsung and Repair Centers

I rooted my T-Mobile Sidekick 4G successfully yesterday and bit off more than I could chew by installing a custom ROM Revolution HD to be exact. Loaded it through ROMmanager with CWM recovery but when loaded was stuck in a splash screen boot loop (it would give the error vibrations (4 buzz) seen when a program is unresponsive (over and over).
I used ODIN to try to restore the original ROM and was successful through the process until ODIN rebooted my phone. Now I loop through color bar screens and when trying to enter download mode (3 button combo (I'm doing it right because thats how I ran ODIN in the first place)) get the a cycle between the 'loading circle animation, white screen, black screen and repeat. Note: Did not unroot
Phone does not enter recovery through button combo nor download mode with USB+button combo. Basically no way for it to connect to ODIN (Haven't used a Jig to force download mode but read it won't work because I can't even get to recovery.
Question (finally i know): If there are no other solutions, I am considering sending the phone through device replacement, is there anyway Samsung can tell if the phone is rooted even if the device is completely unbootable and can't communicate through usb?
I've read a lot of 'probablys' and 'maybes' online but haven't found a solid answer yet.
Thanks!
pictures attached to get a better idea.
EDIT: Repartitioned option was select during ODIN process, just read I WASNT supposed to do that?

[Q] I-9300 bootloop and no recovery

Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Varjo said:
Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Click to expand...
Click to collapse
You can Try this:
1.) Pull out battery
2.) Put it in again
3.) Press Vol up + home + power
4.) When the Samsung Logo appears let it off
I think you press the Buttons too long.
I had the same problem!
S1ay3r666 said:
I think you press the Buttons too long.
Click to expand...
Click to collapse
i really tried everything, it's not working. btw with i am stuck at the very first image, where it says "samsung Galaxy sII GT-I9300".
i dont think it's just the way i press the buttons because i can reach it on my s1 and s2 without a problem, it's just not working on this device.
could some setting like "nand erase all" in odin help? in other threads there is sometimes mentioned that the internal file system might be screwed up and in those cases a simple odin reflash does not help anymore...
Nand erase will usually hard brick it. Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Click to expand...
Click to collapse
thx, but i already did that (multiple times) and flashing via odin always succeeds. then the phone reboots and is stuck at the first samsung galaxy s.. screen. twice i managed somehow to get into recovery (after flashing cwm6) but it then randomly rebooted.
and i dont think that the power button is stuck because when i am in download mode it is perfectly fine it never reboots itself unexpectedly.
Had a similar issue on my tab2 p3100. It all happened when I tried flashing a custom recovery from rom manager.
A bad flash of anything related to recovery or bootloader could be a probable cause.
I remember a knowledge share on one of the threads describing this issue and as mentioned on it all I had to do is this:
1) switch off the device and plug in the charger. This would light up the display showing you the charging status. The status has to show if at least your bootloader part of the phone is fine.
2) plug out the charger and immediately press the three buttons (home + vol up + power) get into recovery mode. This step has to work and help you get to recovery mode.
***Note : the interval within which this step has to be performed is too short since the display would turn off immediately as soon as you plug out the charger. A bit tricky too so you have to be fast. If this misses getting you into recovery, pull out the battery and put it back again. Repeat step1 and 2 again.
3) upon successfully getting into recovery, perform wipe data, cache and select reboot phone from option available on recovery again.
Allow the device to boot. This could take a while since you have performed a data wipe and may prompt for first time set up.
I was able to restore functionality on my tab after these steps and like ppl learn from their mistakes, I then learnt that recoveries and bootloaders are things that needs to be done with a pc only.
Worth a try if you have tried other alternatives and found no go. may help. Who knows..
all the best.
thats also not working. i tried to get into recovery since two days now...
i also tried the steps from this thread: http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
but again, after i flash the cf-root (successfully) the phone does neither boot into recovery by itself nor can i do it by hand...
its crazy... in download mode i can see the model number (GT-I9300) and i thought as long as the model number is there and i can enter download mode there should be a way to recover the device.
but i cannot think of anything to try that i have not done yet
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Click to expand...
Click to collapse
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Varjo said:
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gala...-help-t2737707
Same here, still didn't found how to fix it.. I guess our motherboard just died..
Howewer I have a solution that "almost" worked for me.
Get a stock firmware in odin and turn on Nand erase and T-flash
When it's done phone reboots and you'll see just "Downloading..." mode when you turn it on.
Then got to Kies and Select firmware recovery...
Enter s/n and model name and wait for the flash to complete.
With it , I got past boot logo and actually booted into android but the phone crashed because I guess I have a memory issue..
Well , gl. If you don't find anything else helpful , try going with this method..

Categories

Resources