Listen i'm somewhat new so forgive me if i posted in the wrong place.
Just hear me out please.
Ok heres a little s/a. I have a samsung vibrant, last night i flashed my vibrant which was on a rooted vibrant9 rom. To bionix 1.9.1 w/ jacs oc kernal and the voodoo lagfix. Before flashing to the bionix i switched the boot logo and .wav file to one i perfered, i also did the same for the shutdown logo. Now, per the instructions for installing bionix 1.9.1 i took a nandroid backup of my phone on vibrant9 before performing the flash. After i did i flashed using clockwork. Everything went fine, the phone flashed, rebooted and was working great. However i rebooted the phone and relized that the shutdown screen wasnt working as it should because i forgot to include the shutdown.cfg thats required. What i did was took the bionix.zip off my sd card went into it and added the .cfg file i needed. I added it back to the sd card and figured i'd just reflash and all would be fine. Not so lucky however, i tried to reflash using clockwork (which took me to the regular recovery menu you would get to holding down the volume buttons and power) and it failed giving me an error which said "error on line 80". Relizing that the instruction said that if you had the voodoo lagfix you should disable it, i decided to do a factory wipe of all data (thinking that would definitly disable voodoo) after the factory wipe i attempted to flash bionix 1.9.1 again with no luck. After the last attempt i decided to just restore using the nandroid backup of vibrant9 i had taken earlier, the phone went through the restore process with waht appeared to be no problems. After it finished i rebooted from the recovery menu then bammmm. The phone is stuck in a boot loop. Its not a normal boot loop though the initial samsung logo will pop up for a sec then the phone screen will show what looks like tv static for a sec, it just keeps repeating this. To get it to stop i have to pull the battery. Ive tried booting into recovery by holding the volume buttons and the power button, but all that happens is the phone starts into the above mentioned bootloop. As a note whenever i plug the phone up via usb to my computer a grey battery screen pops up but it dosent charge it just sits there, and if i unplug the usb it goes right back into the bootloop. Also my computer will not recognize the phone so using odin seems like a lost cause. I read in a forum for this phone just a bit earlier that its nearly impossible to brick this phone. Have i done the impossible?
Well it sounds like you have hardware locked phone. Also you cannot do a nand restore w/ voodoo enable. That's your problem. There are threads on xda about recovering hardware lock phones. You need to search. If you can get into download mode, you need to flash eugene373's "Froyo that does not brick". Also, once you get phone working, isuggest you keep a disable-lagfix zip on your internal sd.
Sent from my SGH-T959 using Tapatalk
Great Success
Ok, ok after what seems like a million tries i finally got my vibrant working. After finally getting my vibrant into download mode (by removing the battery, putting the battery back into the phone, holding down both volume buttons and plugging in the phone via usb) i used odin to try and flash back to the factory rom. The flash worked except for an error i noticed when the phone was kicked into factory recovery mode to format itself. There i noticed that at the point when all user data was supposed to be wiped it would have a failure to wipe data. After the flash completed with this error i was able to get past the boot loop. At this point my phone would finish the boot sequence but after the samsung s disappeared the screen would just stay black. However, when ever i pushed any of the soft keys on the front they would light up. So what i did was followed the instructions in the above post and used odin to flash eugenes froyo rom that wont brick. Again the flash would complete but when the phone was kciked into factory recovery mode i got an error and it wouldnt complete it would just hang. So what i did next was use odin to again flash the factory rom and to my surprise it worked. So my vibrant is now restored to its full glory. I owe everything to the patrons of this community. Thanks all.
I recently used Odin to update to froyo 2.2 from my eclair 2.1, and it "pass"ed but now my phone goes into recovery mode. Boot screen then recovery, even when its off and begins charging goes straight to recovery.
At recovery it says:
"update media, please wait
E: Cant mount /dev/block/mmcblk0p1
(Invalid argument)
E;copy_dbdata_media: Cant mount SDCARD:
your storage not prepared yet. please usee UI menu for format and reboot"
But UI menu doesnt work, doesnt let me select anything, and download mode wont load so Odin gets stuck at "Setup Connection".
Help?
Thanks!
- try different versions of Odin's this is the most common issue.
- Make sure your using the correct Eclair 2.1 files the ones by Eugene the unbrickable one.
Mostly, try a different ODIN, and the one that works, don't switch from it.
Odin is the only thing keeping my phone good as new, and i dont need any updates on that.
xrider is correct, I would recommend the 1.7 Odin. You can then Odin back by first flashing Eugenes Froyo that does not brick, then back to JFD2.1
you can get all you need in the Stickies
From there you can root and then flash away
good luck,
Thanks for the replys.
But for Odin to work, wouldn't the device need to be in Download Mode? Which would explain why it doesn't go beyond "SetupConnection". I used the same Eclair rom as I did for my previous recovery. But it fails now, I also tried different versions of Odin from 1.0 to 1.7. Oh an Odin recognizes my phone as a COM6, if that means anything.
I might just go ahead and call Tmo and get a new one. I still have insurance and a warranty.
Hmmm...
Dark619Cloud said:
Thanks for the replys.
But for Odin to work, wouldn't the device need to be in Download Mode? Which would explain why it doesn't go beyond "SetupConnection". I used the same Eclair rom as I did for my previous recovery. But it fails now, I also tried different versions of Odin from 1.0 to 1.7. Oh an Odin recognizes my phone as a COM6, if that means anything.
I might just go ahead and call Tmo and get a new one. I still have insurance and a warranty.
Hmmm...
Click to expand...
Click to collapse
Wait, if you can't get into Download mode, then how are you getting COM6 on ODIN?
I have no idea. Phone just sits in recovery, I plug in USB and it says
<ID:0/006> Added!!
But when I try flashing anything, it stays at SetupConnection.
When I WAS able to get into download mode, it was COM8.
Wait for more replies, idk the solution. Sorry
Maybe new version of odin?
I really appreciate your help though.
I think it's just bricked. The froyo which I had updated to was probably faulty, causing this to occur. I mean, even the recovery menu is messed up. Up and down are inverted, and power button does nothing. Phone doesn't show charging screen(well it does for a second then go straight to recovery).
I'll just call T-mobile tomorrow. I wouldn't get charged right? I tried updating to THEIR firmware, had they made it OTA this wouldn't have occurred, right?
The fact it sees com 6 or com8 or com 4 really isn't important, sometime mine say com2 sometimes it say 6......... this is unimportant.
Follow this ...this should work, the only other thing I can think of is to get into factory recovery and wipe, cache, and memory, go into advanced and wipe the dalvik, then back to Odin and perform the following:
1. Odin 1.3 or higher I use 1.7 but not real important
2. Have the original JFD Vibrant rom
3. You will need the .pit file (this is for mapping)
4. You will Eugene froyo that does not brick rom.
The order is as follows:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! You will have flashed back to the original software. From there, you can do anything !!!
Next root the phone if you are confused about this go to youtube and look up the video by unlocker.com they do a great job showing how it is done.
After all this you can now flash a new rom.
The reason he's getting a COM port without being in D/L mode is because of the secondary bootloader in the sbl.bin. You may just be able to flash JI6.tar without a pit file and get past the Setup Connection
Whoa, nice feedback.
Downloading both Eugenes "Froyo that does not brick" and the JI6.tar.
Will try both methods and reedit my post.
Thanks a lot.
I can't press "Thanks" more than 5 times a day...
UPDATE:
Eh still nothing...Odin gets stuck at SetupConnection.
I believe this will persist until I find a way into download mode. Odin recognizes phone, hence the COM6, but doesn't fully connect since it does not go beyond SetupConnection. The recovery menu also isn't functioning properly, since I can't select anything.
Losing patience with this phone...
I called T-mobile and their sending in a new one.
Told them I was updating and this happened. Do you think I'll get charged?
Well, while you still got time with it...try a different version of ODIN and see if that works... 1.0, 1.3 or 1.7 dunno if there are more
All three versions get stuck at SetupConnection.
I looked into making a JIG, but I only have one USB cord and don't wanna go through the hassle. A JIG would put my phone into download mode, right? Even though it's not really bricked, just completely messed up.
Just now I was messing around with phone, and I got to a different screen!
RST_STAT = 0x1
PMIC_IRQ1 = 0x0
(and some other stuff like that)
Then " POWER RESET OR UNKOWN UPLOAD MODE"
It shows up as COM7 in ODIN But still stuck at SetupCOnnection...grrr
I FIXED IT.
I got the android SDK, and did "adb reboot" which rebooted the phone, and I have froyo and everything.
But ONE problem. T-mobile is sending me a new phone already....what the hell do I do? I can't send this one in, because it's working now.
Nevermind, everytime I rebooted phone it stayed in recovery and I had to always do "adb reboot".
So I did abd reboot download which took me into download mode, but ODIN still stayed at SetupConnection, i took out battery, now I have the indigenous PHONE ! PC error.
NOW I HAVE NO POSSIBLE WAY TO GET INTO DOWNLOAD MODE, Nor have adb connect to phone. No devices are shown when I do "adb devices".
I also tried every variation to get into DL mode, USB, VOl +/-, Battery...etc. Now I think the phone is completely bricked, honestly.
Dark619Cloud said:
I FIXED IT.
I got the android SDK, and did "adb reboot" which rebooted the phone, and I have froyo and everything.
But ONE problem. T-mobile is sending me a new phone already....what the hell do I do? I can't send this one in, because it's working now.
Nevermind, everytime I rebooted phone it stayed in recovery and I had to always do "adb reboot".
So I did abd reboot download which took me into download mode, but ODIN still stayed at SetupConnection, i took out battery, now I have the indigenous PHONE ! PC error.
NOW I HAVE NO POSSIBLE WAY TO GET INTO DOWNLOAD MODE, Nor have adb connect to phone. No devices are shown when I do "adb devices".
I also tried every variation to get into DL mode, USB, VOl +/-, Battery...etc. Now I think the phone is completely bricked, honestly.
Click to expand...
Click to collapse
if you look at ODIN while you plug the phone in with that screen you'll notice it giving you a COM port....weird...but you can still ODIN the phone while on that screen. Flash back to JFD from there.
Yeah I know ODIN should recognize it, because it happened before and it did. But this time it's not. I tried different versions of ODIN as well.
tsk tsk ;P lol
u fixed it? or it remains broken ?
I did fix it, partially. It loaded and everything, but sound wasn't working, and volume rocker was inverted, I guess the rom I flashed was corrupted. So I did "adb reboot download" which took me to download mode to go back to JFD stock, and I did ODIN and everything but it stayed at SetupConnection again. I removed battery to put in download mode manually, and now it's bricked. PHONE /!\ PC. PC doesn't recognize it, and I tried every combo to get into download mode.
So no, it's not fixed.
Okay weirdest thing that has ever happened to my vibrant happened today. I woke up as always to the alarm on my vibrant and got ready, on my way to work I taped the power button on my vibrant to see what time it was (make sure I had time to get my coffee), but it would not turn on. So out of habit I just opened the back of my vibrant and pulled the battery. I have been running Bionix 1.3.1 since the day it came out and never have had any problems. When I turned it back on it just sat at the Green Android chick screen and would not pass. Normally I don't get upset when my vibrant freaks out, because its usually my fault, but the one time I cant figure out why it wont boot I had not done anything to it. I cant get into recovery but I can get into download though.
Now I have tried a few different odin files to get my vibrant working, starting with T959UVJFD.tar. This one just goes into a loop at the Vibrant screen. Then I tried T959UVJI6.tar, same result. By trying Eugene_JK2_Froyo.tar it would finally let me into the recovery mode but it gives me the following errors
Code:
-- movi_checking done!...
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI me
nu for format and reboot actions.
okay so I will hit the format button...
Code:
E:coby_dbdata_media:format SDCARD:
Formatting SDCARD:...
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI me
nu for format and reboot actions.
copy default media content failed.
Upon resetting the device and letting it boot from this one, it goes past the vibrant, then to the t-mobile jingle (oh how I hate that sound), and last to the Galaxy S screen, then goes black. If I hit the capacitive buttons it just lites them up but does nothing beyond that.
I am at a loss as to what to do from here. I don't really care about the data on my phone, anything I really needed is on my computer anyway. Any help with this would be awesome! Thanks in advance!
SirGed/UnoLax
/* Okay all is well now with your guys help! following those steps helped the only change that was needed is to make sure that you check phone EFS Clear and Phone Bootloader Update. As soon as I did that it worked perfect! Thank you guys T-mo has another one on its way to me anyway for warranty. I get to call them in the morning and tell them to cancel that! Thanks again guys! */
Ok I think you got some extra cache or some other piece of data that did not get wiped. either way, do this in this sequence and you should be ok
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Load the JFD rom for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine!
15. Then, root the phone and you can flash your new Rom.
doing this method will get everything back to normal and the phone will work just like it did right out of the box
It is #7 that is important when it reboots into recovery after froyo that does not brick then pull the battery and go back into download mode and flash the JFD, This will clear everything out and put you back into stock
Good luck
On the One that goes into a loop at the Vibrant screen, do these steps:
1. Use three button method to get into recovery mode.
2. Click delete all user data.
3. Enjoy!
BTW I like Bi-Winning with the bi-sense theme as well
Good Luck!!!
Pit
when you use the tar do you use the same pit with both? because when I follow the instructions to install both after I install the JFD it goes into an infinite loop of the vibrant screen.
1234567890
I am in the same boat.. stuck in infinite vibrant loop
i'm even worse.
my vibrant is hard-bricked right now.
i can't access download mode, it's totally blank.
can anybody here help me find a clue or something?
any help will be appreciated.
thanks
Hi guys:
So I have made so mistakes with this phone. When I got it I thought it was a Samsung Galaxy S 4G...
1. Rooted it using SuperOnClickRoot
2. Almost bricked it triyng to install a CFW done for SGS4G.
Then I realized that it was not a SGS4G and came here looking for some information...
I did that: Return to stock JFD (2.1) using that guide:
http://rootzwiki.com/showthread.php?t=702&p=11409&viewfull=1
And now I am a little more happier because the phone turns on, now the recovery works... But... When it get turn on it boot loop endlessly.
I tried so many times to do the same thing and I don't have a chance to get it fixed. Tried to move an update.zip to the external sd card without luck, I was triying to install ClockworkRecoveryMod.
So now I come here... The phone is boot looping and when Its turning on a lot of line with colors appear...
I know this have solution, just I want to know how to approach it.
Thanks for reading!
Redo the flash back to stock But this time 1st go into recovery and delete the cache then go into the advanced and delete the dalvik.
Then shutdown the phone and re open but this time you want to be in download mode (hold down the volume down only (or could just be the up only)) and on button at the same time to get you there.
Then hook up the phone to your comp after you have Odin up and then reflash stock
Then root> then flash whatever you want from there
good luck
oka1 said:
Redo the flash back to stock But this time 1st go into recovery and delete the cache then go into the advanced and delete the dalvik.
Then shutdown the phone and re open but this time you want to be in download mode (hold down the volume down only (or could just be the up only)) and on button at the same time to get you there.
Then hook up the phone to your comp after you have Odin up and then reflash stock
Then root> then flash whatever you want from there
good luck
Click to expand...
Click to collapse
I just have stock recovery... I don't have Advance button...
I have done it in Download Mode, then connected to Odin (PC), box turn yellow saying COM4 and then selected PDA and PIT file in the guide and hit START.
Everything seems to run fine on ODIN and finalize saying PASS but the phone continue doing the problems I have said in my first post.
So I have previously used a rom on my phone and I didn't like it, so I decided to try Gummy for Fassy 0.7.2. I wiped my data, etc before the installation of the .zip. I ran the FassyGum0.7.2.zip as instructed. In recovery I could see that it was installing as it should..then it rebooted to a loading screen that shows Gummy and a scrolling dots as though it is loading/installing something.
Well the next step according to the dev of the ROM mentions that after installing FassyGum0.7.2.zip that I need to install ModifiedGummyGapps.zip. Well due to this loading screen that hasn't gone away in over an hour I can't run the second .zip. I have tried to hold the power button to recycle the phone...nothing happens. I pulled the battery, and turned it back on and held the correct buttons to try and get it back into recovery...nothing it comes back to the Gummy loading screen every time so I can't even recover to an old ROM.
Any Advice??
Cheers
Sounds like you need to use Odin to go back to stock, and then re flash a recovery and try again
Sent from my SCH-I500 using XDA App
brakemynek said:
So I have previously used a rom on my phone and I didn't like it, so I decided to try Gummy for Fassy 0.7.2. I wiped my data, etc before the installation of the .zip. I ran the FassyGum0.7.2.zip as instructed. In recovery I could see that it was installing as it should..then it rebooted to a loading screen that shows Gummy and a scrolling dots as though it is loading/installing something.
Well the next step according to the dev of the ROM mentions that after installing FassyGum0.7.2.zip that I need to install ModifiedGummyGapps.zip. Well due to this loading screen that hasn't gone away in over an hour I can't run the second .zip. I have tried to hold the power button to recycle the phone...nothing happens. I pulled the battery, and turned it back on and held the correct buttons to try and get it back into recovery...nothing it comes back to the Gummy loading screen every time so I can't even recover to an old ROM.
Any Advice??
Cheers
Click to expand...
Click to collapse
The problem was you didnt flash teamhacksung build 1 or 2 first before flashing gummy...if you need proper instructions for flashing ics roms look up section 4 of my guide in general section.
I'm having a similar problem, except after it was stuck in a boot loop, I attempted to odin it, which froze and then led to more problems. Currently all I can do with my fascinate is get it into download mode. But, it isn't recognized in odin or heimdall, or windows. It shows up as unknown device in device manager. Uninstalling/reinstalling samsung drivers hasnt helped. I also installed Android SDK with Google Driver Package to see if it would help but it didnt. As of now I'm not sure what the next step should be as i can not odin, heimdall, recovery, or boot it. I am on Windows 7 64bit.