[Q] Bricked***Please read - Vibrant Q&A, Help & Troubleshooting

This will seem long, but I want to ensure whoever may be able to help has all of the info I can give. My vibrant is officially bricked..
1)I was on the newest official software JI6
2)I had installed RyanZA's One click lag fix
3)I reversed the One click lag fix
4)Got creative and decided to try voodoo lag fix for vibrant version 3
5)After installing voodoo, phone will not boot
6)Here are the symptoms after voodoo.....phone will turn on and attempt to boot, but then just sits there with the bottom four buttons lit
7)Next, I have tried the following:
a)Odin JI6 - same result, phone will not move past Galaxy S logo
b)Did a factory reset - then Odin JI6 again = same result
c)Odin stock 2.1 (JFD) with 512 pit = Same result
Please help!

I had to odin my phone like 4 times to get it to work... Odin is the way... Have you tried switching the usb port the phone is plugged into?

Try using Odin and flash back to stock ROM prior to JI6 like JI2 or JFD. This should work

mightykc said:
Try using Odin and flash back to stock ROM prior to JI6 like JI2 or JFD. This should work
Click to expand...
Click to collapse
I have tried 2 times now to go back to JFD. Same result, everything goes smooth, then the Galaxy S logo appears. Once the Galaxy S logo goes away, the bottom four buttons stay lit for a while, and then I just have to power on. It stays in this loop.

clemsonboyz said:
This will seem long, but I want to ensure whoever may be able to help has all of the info I can give. My vibrant is officially bricked..
1)I was on the newest official software JI6
2)I had installed RyanZA's One click lag fix
3)I reversed the One click lag fix
4)Got creative and decided to try voodoo lag fix for vibrant version 3
5)After installing voodoo, phone will not boot
6)Here are the symptoms after voodoo.....phone will turn on and attempt to boot, but then just sits there with the bottom four buttons lit
7)Next, I have tried the following:
a)Odin JI6 - same result, phone will not move past Galaxy S logo
b)Did a factory reset - then Odin JI6 again = same result
c)Odin stock 2.1 (JFD) with 512 pit = Same result
Please help!
Click to expand...
Click to collapse
I believe the reason your phone would not boot is b/c you were running JI6 and flashed the voodoo kernel. To the best of my knowledge ALL of the custom kernels available for the Vibrant are based off of the JFD build. You have to flash the zip from this thread http://forum.xda-developers.com/showthread.php?t=804415 THEN flash the kernel you want to use. I also know that once you flash the .zip from that thread, if you try to revert to the STOCK kernel it will hang at the Vibrant screen. Only way to get back to stock STOCK is to use Odin. Now as to why Odin is not working is beyond me... I almost wonder if it converted your RFS to EXT4 even though it hung at the Vibrant screen. If this happened then to fix it I believe you have to use Odin to flash Eugene373's "Froyo that does not brick" then downgrade back to JFD and then upgrade back to JI6. It won't be fun, but hopefully this will help you get up and running again!

Update!
Tried again using odin to JFD.
I noticed that after the blue bar finished in download mode and the screen starts scrolling things...
there was an error. It said it was unable to reset data.
Afterwards, it reboots while odin is finishing, then it shuts the phone off...

I would love to try this, but I believe this is over my head. (No shame here!) I don't know how to flash using clockwork.

clemsonboyz said:
Tried again using odin to JFD.
I noticed that after the blue bar finished in download mode and the screen starts scrolling things...
there was an error. It said it was unable to reset data.
Afterwards, it reboots while odin is finishing, then it shuts the phone off...
Click to expand...
Click to collapse
I think its safe to say if you are having a data error then voodoo IS enabled on your phone. You either need to do what I said earlier and flash Eugene's Froyo that does not brick and then downgrade back to JFD OR you might be able to use adb to push a file named "disable lagfix" (no extensions) into the "Voodoo" folder on your sdcard to disable voodoo. You need to disable it before your phone will work.

clemsonboyz said:
This will seem long, but I want to ensure whoever may be able to help has all of the info I can give. My vibrant is officially bricked..
1)I was on the newest official software JI6
2)I had installed RyanZA's One click lag fix
3)I reversed the One click lag fix
4)Got creative and decided to try voodoo lag fix for vibrant version 3
5)After installing voodoo, phone will not boot
6)Here are the symptoms after voodoo.....phone will turn on and attempt to boot, but then just sits there with the bottom four buttons lit
7)Next, I have tried the following:
a)Odin JI6 - same result, phone will not move past Galaxy S logo
b)Did a factory reset - then Odin JI6 again = same result
c)Odin stock 2.1 (JFD) with 512 pit = Same result
Please help!
Click to expand...
Click to collapse
Official Instructions for Reverting from a Voodoo Issue:
SOURCE
Did You Flash Something Before Disabling Voodoo? 2 Fixes to Help You Out.
So you forgot to disable the voodoo lagfix before you flashed a new rom and now you're getting an error, similar to the one posted below. Even Odin won't allow you to flash back to stock. Well, pay close attention and with some luck, you'll be good as rain...or something like that.
Fix 1:
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! BAM!
Fix 2: (use only if you know how to use adb commands)
1. Place the 'disable-lagfix' file in your sdk>tools directory
2. Get into clockwork recovery like you normally would
3. Follow these adb commands to push the 'disable-lagfix' file to you sdcard>voodoo
adb push disable-lagfix /sdcard/voodoo
4. File should now be on your sdcard in your voodoo folder.
5. Reboot phone and with luck, you should hear Linda the robot telling you your file system is being converted back to rfs.
6. Because your system directory has already been wiped, you'll still get a black screen when you reboot, but your file system is back to rfs. Just pull the battery, and reflash whatever rom you want. Then reboot again.
Click to expand...
Click to collapse
Taken from the Bionix Instruction Page
As a note this will WIPE all the data on your phone except for the external sd card. The internal 16gb card will get wiped. Using ADB I would pull the entire contents of your /sdcard/ to your Computer so that you can restore completely. The command is as follows:
adb pull /sdcard/
Click to expand...
Click to collapse

xxwhitehawk said:
I think its safe to say if you are having a data error then voodoo IS enabled on your phone. You either need to do what I said earlier and flash Eugene's Froyo that does not brick and then downgrade back to JFD OR you might be able to use adb to push a file named "disable lagfix" (no extensions) into the "Voodoo" folder on your sdcard to disable voodoo. You need to disable it before your phone will work.
Click to expand...
Click to collapse
Thank you sssssssssssooooooooooooooo much WhiteHawk. I am now back to original JFD thanks to you. I am more appreciative than you could ever imagine.

clemsonboyz said:
Thank you sssssssssssooooooooooooooo much WhiteHawk. I am now back to original JFD thanks to you. I am more appreciative than you could ever imagine.
Click to expand...
Click to collapse
That is great! Glad to hear everything worked out ok.

Related

[Q] Phone not starting up

Okay. So I pushed Axura final onto my phones internal sd card and booted into recovery mode. The damned Axura copy ( it downloaded properly via google chrome, no errors) had some issue with it and DID NOT install properly. I tried again and again to make it work, did not load flash from voodoo eclair 2.1 to axura which is 2.2.
Now I want to use ODIN and come back.
I get into download mode BEAUTIFULLY using youtubes """Samsung Vibrant download mode; Corntez" .
and then load Odin, load pit file, and the tar/jar file. detected as COM 6 Odin says "added" . then run it. RUNS perfectly. firmware update start; cache.rfs;modem.bin;factoryfs.rfs; and all, and the blue bar finished completely.
Then restarts, "VIBRANT" says "data wiping failed " , everything else succeeds...lots of small writing....restart' VIBRANT" ; then Samsung Galaxy S shiny logo.
Now.....the plot thickens and my vibrant does not move forward. Black, black screen.
If I touch the bottom touch keys---viz, home etc...they light up fine. But the screen. the beautiful screen, remains as dark as Lord Voldemorts heart.
What to do??
I forgot to mention that I moved from a forward port on my thinkpad to an aft port )); and the COM4 in ODIN changed to COM 6 , promptly.
Odin is causing some issues. seems like. Any suggestions and links for newer, better versions of the T mobile stock firmware.????
Need I mention that I had voodoo before I tried to put Axura on? I did.
Thanks for all the help, in anticipation,
cheers
houston123 said:
Need I mention that I had voodoo before I tried to put Axura on? I did.
Thanks for all the help, in anticipation,
cheers
Click to expand...
Click to collapse
Houston we have a problem. Voodoo MUST be disabled BEFORE you flash. There are plenty of info on the board on how to do this. Then ODIN to stock then FLASH. Not all ROM's need a lag fix, some just run smooth!
my phone is doing the same thing but all i did was hit the voodoo button that was available in the oclf app and it went dumb the women counted down and said complete after a while and then it stuck on the vibrant samsung screen. i flash with stock rom and now its doing what this guys phone is doing please help us
Hey, yes, I read somewhere, that voodoo needs to be disabled. I did not do that, I had issues doing that.
houston123 said:
Hey, yes, I read somewhere, that voodoo needs to be disabled. I did not do that, I had issues doing that.
Click to expand...
Click to collapse
For the dear love of [deity]/self-sufficiency, go read how to solve your problem
(You need to flash Eugene's "froyo that does not brick." Then flash whichever firmware you want.)
Can someone post a link to Eugenes Froyo that does not brick please. Eugene himself has removed all support. Also, I found a zip file for Eugene somewher and NOT a tar or whateva file type ODIN uses to restore firmware.
houston123 said:
Can someone post a link to Eugenes Froyo that does not brick please. Eugene himself has removed all support. Also, I found a zip file for Eugene somewher and NOT a tar or whateva file type ODIN uses to restore firmware.
Click to expand...
Click to collapse
http://eb-productions.proboards.com/index.cgi?board=samsungsgs
I have tried but doesn't work for me. Unfortunatly I too did not disable voodoo before flashing and now I am stuck and can not get into download screen. I guess I will have to take my stuff to a cell phone repair since I have ran out of options.
got eugenes software. Now I am going to try out this:
""""
ok so here is what you have to do:
1. download odin, froyo that doesn't brick, and 2.1 true stock
2. go to download mode, flash the pit and tar file from the froyo that doesn't brick (DON'T RE-PARTITION!)
3. it will boot into recovery and error out, DONT PANIC, that is what is supposed to happen
4. remove battery (from phone) and usb from phone and computer
5. put battery back in, access odin and download mode
6. flash the pit and tar file from the true 2.1 stock (RE-PARTITION THIS TIME!)
7. if done successfully, your phone software will like when you just took it out of the box!"""
If all this does not work out, I have the 6 $ a month insurance from T Mobile---how do I use that? They might just say **** off, you screwed with the ROM and bricked the phone! Should I told them that someone flicked at Swing dance class.....instead of " I bricked it" sorry!!!!
Your opinions on this???
houston123 said:
If all this does not work out, I have the 6 $ a month insurance from T Mobile---how do I use that? They might just say **** off, you screwed with the ROM and bricked the phone! Should I told them that someone flicked at Swing dance class.....instead of " I bricked it" sorry!!!!
Your opinions on this???
Click to expand...
Click to collapse
My opinion on this is not to worry unless it doesn't work. But since you know how to use Odin and your phone can get into download mode okay, it should work.
With the insurance there is a hefty copay. But you should be fine.

[Q] e:Can't mount /dev/block/st110 bricked!

So I went to Odin my phone back to stock JI6 in Odin and I used the tar and pit file and select re-partition to wipe everything. Everything went fine and it rebooted, but now it brings me to the Recovery menu and says:
e:Can't mount /dev/block/st110 (Invalid argument"
E:copy_dbdata_media:Can't mount DBDATE:
copy default media content failed.
I've tried to reboot into download mode via the keys, and through adb, but I can't get there to install the OS...
Any help?
Thanks!
sano614 said:
So I went to Odin my phone back to stock JI6 in Odin and I used the tar and pit file and select re-partition to wipe everything. Everything went fine and it rebooted, but now it brings me to the Recovery menu and says:
e:Can't mount /dev/block/st110 (Invalid argument"
E:copy_dbdata_media:Can't mount DBDATE:
copy default media content failed.
I've tried to reboot into download mode via the keys, and through adb, but I can't get there to install the OS...
Any help?
Thanks!
Click to expand...
Click to collapse
1.) Make sure you are using something that is NOT 'Odin3 1.0' the best versions are 'Odin3 1.3 & Odin3 1.7' IMO
2.) Make sure you are using JFD Stock to odin back.
Master™ said:
1.) Make sure you are using something that is NOT 'Odin3 1.0' the best versions are 'Odin3 1.3 & Odin3 1.7' IMO
2.) Make sure you are using JFD Stock to odin back.
Click to expand...
Click to collapse
I am using Odin3 v1.30.
But how am I going to get JI6 or even JFD on the phone? It won't start up, just keeps going to this menu where my only options are reboot system now, reinstall packages (does nothing) delete all user data and delete cache data..
sano614 said:
I am using Odin3 v1.30.
But how am I going to get JI6 or even JFD on the phone? It won't start up, just keeps going to this menu where my only options are reboot system now, reinstall packages (does nothing) delete all user data and delete cache data..
Click to expand...
Click to collapse
You don't reinstall packages.
Just use JFD that is the one that is most likely to work. Not all work for everyone.
JI6 doesn't work for me.
To use Odin, you go into download mode. You don't use recovery.
Master™ said:
You don't reinstall packages.
Just use JFD that is the one that is most likely to work. Not all work for everyone.
JI6 doesn't work for me.
To use Odin, you go into download mode. You don't use recovery.
Click to expand...
Click to collapse
That's the thing, I can't get into download... Neither the hardware buttons or adb will get me there.. I type adb reboot download, and it takes me to the menu with the above options I mentioned.
sano614 said:
That's the thing, I can't get into download... Neither the hardware buttons or adb will get me there.. I type adb reboot download, and it takes me to the menu with the above options I mentioned.
Click to expand...
Click to collapse
So you are hardware locked? The following MAY or MAY NOT work...
1.) Turn off your phone, remove battery/sim/micro SD
2.) Press & Hold the VOL UP+VOL DOWN
3.) Plug your phone into your computer (Keep holding those buttons)
4.) Download mode should pop up.
Master™ said:
So you are hardware locked? The following MAY or MAY NOT work...
1.) Turn off your phone, remove battery/sim/micro SD
2.) Press & Hold the VOL UP+VOL DOWN
3.) Plug your phone into your computer (Keep holding those buttons)
4.) Download mode should pop up.
Click to expand...
Click to collapse
I shouldn't be hardware locked, I flashed the file to get rid of the hardware lock before I used Odin earlier and was able to get into Recovery via the buttons (didn't try download though.. DOH!)
I was able to get into download mode now, though, and am flashing JI6 while JFD downloads (very slowly). JI6 finished and same error... Will wait for JFD to be done.
Thank you very much, Master. Merry Christmas.
I'm all set now. Thank you for all your help, Master.
how did you get the phone running again, i mean i can go to the download screen, but after any update I still recieve the same recovery screen with error.......... tried so many things none of them work, what to do?
jaiiscool said:
how did you get the phone running again, i mean i can go to the download screen, but after any update I still recieve the same recovery screen with error.......... tried so many things none of them work, what to do?
Click to expand...
Click to collapse
What are you trying to flash? I had to use Odin to flash JFD, not JI6 as that just kept sending me to that same recovery screen with the error.
sano614 said:
What are you trying to flash? I had to use Odin to flash JFD, not JI6 as that just kept sending me to that same recovery screen with the error.
Click to expand...
Click to collapse
I have a Galaxy S with this error, I am trying to flash the DDJP6 firmware with ODIN, I had checked the repartition by mistake and got this error, don't know what to do now.
Hello everyone, if your reading this you likely have the error mentioned above. Recently, a friend of mine came to me with this same problem. I looked long n hard and every link I found was broken. Every odin file I needed was removed. I even noticed that eugene kindly took down his odin to stock package...that was pretty cool of him At any rate, I still had eugenes odin to froyo zip luckily, I tried flashing this normaly thru odin and got the same error. What ended up working for my buddys phone was, using eugenes odin package and putting a check in "re-format" in odin. That fixed it right up. If your having the same errors, please feel free to contact me. Id be happy to link you or do anything else in power to help. This worked like a champ! Good luck. If this helped ya, please feel free to hit my thanks button. I only have 3!
JFD is the only one that carries all the necessary files for the check-repartition ODIN install...
Something to do with flashing both bootloaders.
EricDET said:
JFD is the only one that carries all the necessary files for the check-repartition ODIN install...
Something to do with flashing both bootloaders.
Click to expand...
Click to collapse
Nope, nothing to do with bootloaders. It has to do with jfd being the only realeased odin package that contains dbdata.rfs of the .tar. None of the other ones do.
Sent from my SGH-T959 using XDA App
I went to partition my sd card through rom manager, I have all the files on my computer (all different versions since November). It went into recovery, mounted sd, was formatting and next thing I knew it is stuck on the overstocked logo. I am running Trigger 3.0 & flashed in overstocked (through rom manager) and themed with a splash of color with other modifications.
The thing is, is that I also have the vibrant galaxy s 4g and was using the 16gb sd for both until my 32 came in and realized, not a good idea. So until the 32 came in I decided to just work on this phone but wanted to get any signs of the 4g off this phone so was cleaning it up and now here I am.....
Read the threads here and have gotten into the download mode, with nothing to download but it goes right back to the "overstocked" logo or bouncing to the "vibrant" logo and battery sign.
Any suggestions would be greatly appreciated.
EricDET said:
JFD is the only one that carries all the necessary files for the check-repartition ODIN install...
Something to do with flashing both bootloaders.
Click to expand...
Click to collapse
I used Eugene_2E_JK2_Froyo.tar.md5, and s1_odin_20100512.pit. I checked re-partition and left F. reset time and auto reboot checked. This solved the e:Can't mount /dev/block/st110 error. Idk if this will work for everyone, but using the exact same files but without re-partition checked left the same error, checking it fixed the error. Just thought Id share my results because that can be a very frustrating error which in my friends case caused fc's all over the place, while booting up and a bunch of apps as well.

Help With Odin Problem

I was running Bionix-v 1.1.2 and the DOW kernel and everything was working great. My phone then got stuck on the DOW boot up image so i used Odin to flash back to stock like I have done countless times. I am able to get the phone into download mode and I start Odin and it states All threads completed. (succeed 1/failed 0) >Removed. At witch the phone would normally boot into recovery mode and Odin would finish doing its thing but my phone will now just show the battery charging picture, go black, then the battery charging picture again until I unplug the usb. The phone will power up to the Vibrant splash screen then go black. I can get the phone into download mode but I always get the same results when I try to flash with Odin. Any help would be appreciated... Thanks.
try another .tar... you can grab some in the noob guide/alt method in my signature. Its KA2 froyo leak + root. Others are in the Deb Bible too...
k i flashed another .tar(KA2 froyo leak + root) it boots into recovery and I get the following:
E:Can't mount /dev/blocked/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
copy default media content failed.
drewdude007 said:
k i flashed another .tar(KA2 froyo leak + root) it boots into recovery and I get the following:
E:Can't mount /dev/blocked/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
copy default media content failed.
Click to expand...
Click to collapse
I got the same error when running some test kernels. Try flashing JFD also flash the 512.pit file and check repartition in Odin . If that doesn't work flash Eugenes froyo that doesn't brick .
Sent from my SGH-T959 using XDA App
I downloaded a new copy of JFD and 512.pit checked repartition. Still was not able to get into recovery after Odin even with the new copy. Eugenes froyo that doesn't brick gave me the same can't mount error message.
Having the same issues.....JFD simply won't boot, Eugene's Froyo that wont brick makes it through the boot animations and then locks with the touch buttons lit up, Eugene's JK2+2E boots fine, but has this problem (internal and external storage show up as unavailable). I'm pretty sure it's related to using ODIN with Voodoo enabled and I've been going crazy all day trying to find a fix, but to no avail so far. ANY help would be incredibly appreciated!!
Try older odin programs. Yes u read that right.
Sent from my SGH-T959 using XDA App
I tried Odin3 v1.0, v1.3, v1.7, and v1.81 all with the same results.
drewdude007 said:
I tried Odin3 v1.0, v1.3, v1.7, and v1.81 all with the same results.
Click to expand...
Click to collapse
Then its your files. Download stock jfd again . Pit and tar. Do both. If you can delete your dalvik do.
Sent from my SGH-T959 using XDA App
Drewdude, since we're having the same problems, we should confer about it through some IM system in a little bit... two heads are better than one, right?
Well I have also tried Heimdall as well... no success with Heimdall either. So my final solution to the problem is I called T-Mobile and told them my phone would not turn on. My new Vibrant will be here in 3 days at no charge.
OP,
I just experienced the SAME Exact problem. THE VERY SAME.
Something tells me it's the DOW kernel.
W.T.F.
I've tried all the ODIN files that are available.
In each one, I get Vibrant, then it goes blank and turns off. Nothing else.
My phone is fried.
More likely than not, youre not fried, just soft-bricked same as me. Can you get your phone into download mode? Hold vol + and vol - while inserting your micro-sd cable...it should go to a picture of a yellow android with a shovel. If you can get to this mode, your phone is NOT fried.
THat's the only mode I can get into bud.
I've tried to load JI5 Ji6, Eugene's nonbrickin g Froyo.
None of the roms get past the vibrant screen.
THey just shut off.
Well I have been working on it for a day straight and no luck. I have talked to several people and the phone has readonly partition now so it is ****ed! Nand death!
Try these step from oka1 . He say to flash Eugenes froyo without repartition checked then pull the battery when tries to boots . Then flash JFD with repartition checked.
Probably you will need a couple of things in your tool kit.
You will need Odin 1.3 or higher
Pit file (there are 512 and 831) Guessing you will need the 512pit
Original JFD stock file 2.1
Eugenes froyo that does not brick
Remove the sim and the sd card, remove the battery have Odin up on the computer> then hold down the 3 buttons and plug in the phone to the usb connected to computer. If this works and Odin sees the phone (does not matter if it says com5 or 6 etc.) then you can go from there, If not then you will need a jig, people here sell them, i saw connextion2005 sells them but there are others (like 8bucks) or you could make it is 301k resistors tied to one 2 pins of the usb (do a search if you are interested).
Then the sequence for the fix is to flash the Froyo first that does not brick (do not check repartition) once it begins to reboot pull the battery out (does not need to reboot) then flash the JFD on top and this time check the repartition
Let this finish reboot> then use super one click root or other of your choice. Then download CWM and Titanium backup...... flash your new rom and you are back in business.[/QOUTE]
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
AgentFour20 said:
Try these step from oka1 . He say to flash Eugenes froyo without repartition checked then pull the battery when out boots . Then flash JFD with repartition checked.
Probably you will need a couple of things in your tool kit.
You will need Odin 1.3 or higher
Pit file (there are 512 and 831) Guessing you will need the 512pit
Original JFD stock file 2.1
Eugenes froyo that does not brick
Remove the sim and the sd card, remove the battery have Odin up on the computer> then hold down the 3 buttons and plug in the phone to the usb connected to computer. If this works and Odin sees the phone (does not matter if it says com5 or 6 etc.) then you can go from there, If not then you will need a jig, people here sell them, i saw connextion2005 sells them but there are others (like 8bucks) or you could make it is 301k resistors tied to one 2 pins of the usb (do a search if you are interested).
Then the sequence for the fix is to flash the Froyo first that does not brick (do not check repartition) once it begins to reboot pull the battery out (does not need to reboot) then flash the JFD on top and this time check the repartition
Let this finish reboot> then use super one click root or other of your choice. Then download CWM and Titanium backup...... flash your new rom and you are back in business.[QOUTE/]
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thanks but I have tried this method over and over again and it does not work for me. My phone is dead!
Click to expand...
Click to collapse
So is mine.
Somebody in the DOW thread said to use ODIN to flash the original Bionix Kernel only.
I don't see how that's helpful now since I've already flashed all the other 2.1 Tmobile roms.
This is F(ked.
unless somebody knows how I can flash a bionix rom using ODIN? I might be able to get that Bionix V stock kernel on there too.
Thanks
drewdude007 said:
AgentFour20 said:
Try these step from oka1 . He say to flash Eugenes froyo without repartition checked then pull the battery when out boots . Then flash JFD with repartition checked.
Thanks but I have tried this method over and over again and it does not work for me. My phone is dead!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

[Q] Borked Partition, cant odin back to stock. Boot loop. Help?

This thread has a similar issue to what im having, but ive branched off elsewhere...
http://forum.xda-developers.com/showthread.php?t=883944&highlight=Rom+Manager+partition+recover
The story: Ive had a rooted vibrant for a while. Im no linux noob, either. I was having some issues so i decided to try Darky's Toxic rom...worked GREAT! I made a clockwork backup...now i felt it safe to start to play.
I was having media scanner issues...so i decided to repartition my storage spaces (and to get rid of the avatar movie)...but i used ROM manager...clearly by mistake. whoops.
So after MUCH trouble with boot looping...i was able to ODIN to Eugene's Froyo that doesnt brick. The STOCK rom wouldnt give me video...just hung after the Galaxy S boot seq. Im assuming thats a voodoo issue?
Anyway...able to get Eugene's on there...and i was smart and made a back up of both storage spots. I reloaded CWR, and tried to restore to the backup of Toxic i made with no luck. Matter of fact, i cant get any other ROM to load that ive tried.
Any suggestions to get my restore point back up and running? I thought about trying to go stock...but like i said, i couldnt get to stock through ODIN.
Couple of Ideas........ I am assuming you can get into download and recovery.
If you can get into recovery, clear cache, wipe dalvik then, pull battery and get into download, then try odin back to stock, remember to check repartition.
Or try Heimdall, sometimes it works when Odin does not. But if you can get into download then, there is a way (or some combo of ways) to get you back to stock. Just be patient and logical......... you will get it..........good luck
I CAN get into download and recovery...and was able to get CWR back on...thankfully.
I have tried every combo of wipes i can think of.
If i flash to true stock 2.1...i get black screen with lit buttons.
If i flash to Eugene's...i can boot into a ROM build with no internal storage, therefore no way to install apps.
I just came across this and tried it...with no new results.
Fix 1:
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! BAM!
Click to expand...
Click to collapse
I'll try your suggestion now...thanks!
Still no luck. Same thing...black screen, with lit buttons.
Did i officially brick this thing?! haha...i thought it barely possible with the vibrant.
I tried flashing the JI6 rom too....still no go.
Anything?
When you Odin to stock, what tar are you using? When you repartition, do you use the pit file?
I suggest that you use the JFD Odin image and repartition using 512.pit. I have also heard of some people having more success with Odin when they dont have an SD card or SIM card in the phone (this may be an old wives tale.) Good luck.
Same problem
I had this exact issue two days ago and after many attempts with Odin, like you, the only ROM I could load was Eugene's. Re-Partitioning with Odin had no affect, stock wouldn't work and wiping everything had no affect. With Eugene's it would show no space for apps and wouldn't hold any settings if the phone was rebooted. It seems that clockwork mod is actually removing the apps partition and no tool I could find would actually recreate it. I searched quite a bit and found several posts all with the same issue and in every case they had to replace the phone. Luckily I am still under warranty so T-Mobile is replacing it. I don't know if the Clockwork Mod developer has a thread on here, but that "feature" needs some work or it needs to be removed.
kadashti said:
When you Odin to stock, what tar are you using? When you repartition, do you use the pit file?
I suggest that you use the JFD Odin image and repartition using 512.pit. I have also heard of some people having more success with Odin when they dont have an SD card or SIM card in the phone (this may be an old wives tale.) Good luck.
Click to expand...
Click to collapse
Yes, ive used both the vanilla JFD tmo tar, and the JI6 tar. Neither worked. Triend both the 512 and the 513 PIT file. 512 for the first HUNDRED times...then 513 for the hell of it, since at this point, i was getting nowhere.
And thanks pamulli, thats what im basically resigning to..i just needed to hear it from another person.
REMINDER: It is as easy as fat fingering the keyboard to totally screw your phone. Click carefully!

[Q] Phone bricked?

I sold my friend my Samsung Vibrant and I've never had any problems flashing it, he tried flashing the cyanogenmod rom (tried being the operative word...) and I'm not sure what he did to but when I try to turn it on its has the I9000 boot screen and it goes to the vibrant splash screen and turns off, if it's plugged it gets to the vibrant screen and then has the cycle icon for the battery then it shows the battery and it infinitely loops like this when its plugged in (when I had it, it would be completely dead and I could plug it in and turn it on at the same time and it would boot fine and didn't die). I tried flashing JI6 via ODIN, which seemed to flash correctly (gets to zImage and says removed and then pass), but nothings changed (still I9000 boot screen and still crashes on splash screen with battery loop). Any idea what I can do to fix this?
I think your friend flashed the I900 Version of the Rom. Try odin-ing to stock.
EDIT: You already odin-ed JI6. Try odining to stock JFD with both pit and tar files. That should restore everything (bootloader, kernel, baseband, etc...)
its shows i9000 on boot with the GB bootloaders
http://forum.xda-developers.com/showthread.php?t=849028 have a read through there
if you do have the GB bootloaders its vol up and power for download mode
odin to stock will fix it
Downloaded and tried all three of these things and still nothing different. When I turn it on the boot and splash screen come up but then the device just turns off. Tried JI6 and JFD, and the boot screen keeps showing up as the I9000 (GB), when it should be the stock TMOUS bootscreen, so it seems like the bootloader isn't being flashed correctly, although it says pass and has no errors. I'm thinking that the phone is bricked, is there anything I'm not thinking of that would help?
ddaydude said:
Downloaded and tried all three of these things and still nothing different. When I turn it on the boot and splash screen come up but then the device just turns off. Tried JI6 and JFD, and the boot screen keeps showing up as the I9000 (GB), when it should be the stock TMOUS bootscreen, so it seems like the bootloader isn't being flashed correctly, although it says pass and has no errors. I'm thinking that the phone is bricked, is there anything I'm not thinking of that would help?
Click to expand...
Click to collapse
go there:
http://forum.xda-developers.com/showthread.php?t=1230059
skip the parted part you dont need it and phone would be back to good function asap.
ddaydude said:
Downloaded and tried all three of these things and still nothing different. When I turn it on the boot and splash screen come up but then the device just turns off. Tried JI6 and JFD, and the boot screen keeps showing up as the I9000 (GB), when it should be the stock TMOUS bootscreen, so it seems like the bootloader isn't being flashed correctly, although it says pass and has no errors. I'm thinking that the phone is bricked, is there anything I'm not thinking of that would help?
Click to expand...
Click to collapse
the jfd.tar doesnt have the bootloaders i dont think so you'll still be on GB bootloaders on 2.1, they're backwards compatible anyway so it doesnt matter
demetris_I said:
go there:
http://forum.xda-developers.com/showthread.php?t=1230059
skip the parted part you dont need it and phone would be back to good function asap.
Click to expand...
Click to collapse
I've tried to get into recovery mode for this but I can only get into download mode (tried VOLUP+HOME+POWER (and without home) boots to download mode, tried VOLDOWN+HOME+POWER (and without home) and it does nothing, I've tried to use adb on the download screen but it doesn't find the device). Is there another method that I'm missing?
I remember telling you you dont need parted part -> dont need to enter cwm just download mode.
1.download mode
2.http://www.4shared.com/file/dJiyRz3v...Froyo_PDA.html
unzip it and get odin ready.
Go to download mode, place pda only in phone area pit not needed, flash
Let it boot into recovery, remove battery and re-enter download mode.
Flash JFD with pit file and re-partitions checked.
Done and done.
demetris_I said:
I remember telling you you dont need parted part -> dont need to enter cwm just download mode.
1.download mode
2.http://www.4shared.com/file/dJiyRz3v...Froyo_PDA.html
unzip it and get odin ready.
Go to download mode, place pda only in phone area pit not needed, flash
Let it boot into recovery, remove battery and re-enter download mode.
Flash JFD with pit file and re-partitions checked.
Done and done.
Click to expand...
Click to collapse
Sorry about that, my bad. But I tried just tried that, and when I flashed the Froyo file it booted to recovery (like it sounds like it should have, still with GB bootloader and reversed controls on recovery and not able select since vibrant doesn't have an ok button) and then flashed JFD with the pit and repartition selected and it goes back to turning off after the vibrant screen. I tried redownloading both froyo and JFD thinking one might be corrupt and I still get the same result as before. I've checked the instructions 10+ times and I've used odin for the life of this phone more times than I have counted, and I can't figure out why it doesn't seem to be taking it, it doesn't fail in odin so it doesn't make sense.
After doing what i recommended your phone would be in fully functioning order.
Your problem lies on the bootloader so i would recommend to flash froyo bootloader from here:
http://forum.xda-developers.com/showthread.php?t=1117990
but before md5 check the downloaded file and follow exactly the guide there.
If this dont fix it then i think your phone is a pita.
I kinda agree that its probably just the Bootloaders that is the culprit for the I9000 splash. As mentioned flashing the original FROYO should fix it. At least it did for me. I had to do both these links in the GB bootloader thread for it to take though. 1st one 1st - then either of the 2nd links 2nd.
adyscorpius said:
jfd odin file - for use after installing gingerbread bootloaders
http://www.multiupload.com/hryjkflkfq "thanks to laylovj"
md5: 977e2136996e7138945447a8245d6776
if you have gingerbread bootloaders installed and you end up odining to stock (jfd), you will notice it changes the bootsplash to i9000. You can either reflash a gb bootloader again, or simply use the odin package above to do so.
vibrant stock (froyo) bootloader download link
- dropbox download link
- mediafire download link
md5 sum - 754ecbd8e76d4f81bec49240031f3262
Click to expand...
Click to collapse
Now as far as ODIN. The yellow triangle and android dude digging should be there throughout the entire ODIN flash. If I understand you correctly and the phone goes black during the ODIN flashthats no good. If its doing it after the ODIN flash, then maybe you still have the "reboot after flash" button ticked. Either way the phone needs to stay in download mode during the entire ODIN flash.
*EDIT*
- If all else fails JTAG! but that should be the last option. There is a fix!
- BUY A USBJIG you can get them from either TeamWhiskey or EDT on their sites. If everyone had one we would never see another
"NO DOWNLOAD MODE!!! HELP" thread again. And at the same time you'd be supporting developers which is a good thing.
Good luck!
You should try the "froyo that does not brick" in the early days of froyo eugene released a froyo package that came with bootloaders. Google ftdnb, it may also be in either bricked or eb's threads
Beware of angry gingerbread man

Categories

Resources