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.
Related
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.
Hello all, I'll give my story chronologically.
1. Installed Clockwork Recovery.
2. Did a nandroid backup. Everything OKAY at this point.
3. Tell Clockwork to partition my SD card.
---- It does its thing, reboots phone into recovery to partition SD, then upon reboot, it will get past initial T-Mobile Spash and Galaxy S splash but will not proceed further (black screen when phone would normally load up).
Figuring I'm ****ed, I try p much everything. Even going back into recovery for some reason brought me back into stock recovery instead of clockwork.
Damn.
4. Installed Odin, flash back to stock, no problems or errors detected during odin-ing process.
5. Phone goes through start-up, same issue.
Whaaa? Please help, as this really sucks. The phone is obviously not bricked, but it might as well be because it's about as useful as... well, it's not very useful in the current state.
Thanks for any help that can you offered.
edit: All my datas are gone. D:
Also, I can get into download mode (obviously) and recovery mode. Here is what I see in recovery mode.
" -- Movi_check Start..!!
checksum confirmation need_checksum[1301305579]
MBR_ChkSum in header : 4.1
MBR checksum : EC0063A432AFDBA2B104C3F0DF52FE3D
MRB Checksum Error
Movinand Checksum Confirmation Fail
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC "
Click to expand...
Click to collapse
You need to odin 'eugenes froyo that doesnt brick' first, search for that thread, then odin stock
Sent from my SGH-T959 using XDA App
metalfan78 said:
You need to odin 'eugenes froyo that doesnt brick' first, search for that thread, then odin stock
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yep, that's what you have to do and then make sure NOT to partition your sd card again. Bad things happen with that. As you have seen
Yea, never partition with clockwork. Just out of curiosity why did you partition in the first place
Sent from my SGH-T959 using XDA App
metalfan78 said:
Yea, never partition with clockwork. Just out of curiosity why did you partition in the first place
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The clockwork app said there was some advantage or another. I can't quite recall anymore.
Anyways, working on following all of the advice now, guys. Thanks a bunch.
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!
Thanks. Typing this from eugenes froyo now. I almost do not want t go back to 2.1 now. Haha
edit: does eugene have any fully-functioning 2.1 builds? i really love the stockyness of his froyo. reminds me of when i was playing with the i9000 in korea over the summer and doesn't have all of the disgusting gradients that the tmo builds have.
edit: I think I can deal with the switched volume, non-functioning 3.5mm jack, and no home button. This version of android is what i've always wanted. TMOBILE TAKE NOTE. Haha. Can't wait for this to be bug-free.
Edit again... ok i miss the home button
I have the same exact issue.
Only problem is that the steps explained here do not fix the problem.
Shouldnt this procedure wipe out your internal SD?
Mine is never wiped out. I get to Froyo/ no brick with no issues.
No errors in recovery once I "adb reboot"
Flash back to stock with repartition and back to the same checksum error.
Cant figure out why this wont erase and rebuild the NAND.
Anyone???? Maybe an ADB commant to manually repartition and erase the entire internal SD?????
sknobs said:
I have the same exact issue.
Only problem is that the steps explained here do not fix the problem.
Shouldnt this procedure wipe out your internal SD?
Mine is never wiped out. I get to Froyo/ no brick with no issues.
No errors in recovery once I "adb reboot"
Flash back to stock with repartition and back to the same checksum error.
Cant figure out why this wont erase and rebuild the NAND.
Anyone???? Maybe an ADB commant to manually repartition and erase the entire internal SD?????
Click to expand...
Click to collapse
Did you download the correct "Eugenes Froyo That Does Not Brick"? Its titled exactly that.
Click here for the thread
cthach11 said:
Did you download the correct "Eugenes Froyo That Does Not Brick"? Its titled exactly that.
Click here for the thread
Click to expand...
Click to collapse
Yep, thats the one.
It even saved some of my email settings. I was shocked!!!
I did the adb reboot
It booted and after boot.......ding, you have a new email. Had all my account settings and all.
I have done the odin flash over and over, never erased the nand once?????
metalfan78 said:
You need to odin 'eugenes froyo that doesnt brick' first, search for that thread, then odin stock
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thank you so much for this info...I thought I was going to have a nice paper weight after only 8 days of owning my Vibrant!
Do exactly what this says.
First EUGENE373_SamsungS_Froyo_PDA.tar and s1_odin_20100512.pit
then when phone reboots, use
s1_odin_20100512.pit and Original.tar and and all is good
hi
Did you repair your phone？
where to download the 2.1 true stock
I searched but didnot find
thanks
The Tech Game said:
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!
Click to expand...
Click to collapse
said323 said:
where to download the 2.1 true stock
I searched but didnot find
thanks
Click to expand...
Click to collapse
Having the same issue, ended up ODIN with eugene and had a somewhat working phone, just couldnt download anything. Once in Euegne froyo, should I load anything onto SD card (mounting it to computer) or adb push anything somewhere???
After reverting to a stock image Im back where I started
Have tried the following 2.1 tars: JI6 & JFD
I'm able to get back to stock but not sure if its the correct stock rom. I still get the mbr checksum error when rebooting into recovery. If I did the correct rom would the mbr checksum error be done with?
I can't seem to get this to work either.
Tried Eugene a thousand times.
Stock ROM- MBR error in recovery
Only 4 lights at bottom...
Have read about 20 hours of same problem on multiple forums with no avail.
Was it Voodoo Lagfix? How do I remove it or FIX MY INTERNAL PARTITION SIZES?
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
dude that's not even close to a brick as the phone is still responsive somehow..
do this:
1. pull out battery wait 5-10secs
2. connect USB to computer and phone
3. hold down the vol +/- buttons
4. plug in battery
5. you should be in download mode now
6. do what you gotta do with ODIN
good luck
Dont use that method to get to DL mode . Do it this way . First turn off your phone , then plug the usb cable into your computer ONLY . Next hold both volume buttons and plug the micro usb into your phone . Also use odin v1.3 and flash the rom of your preference .
Edit : xtone beat me to the punch
trill12 said:
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
Click to expand...
Click to collapse
Yes using ROM Manager to repartition your phone will create the "soft-brick" you are experiencing. But as one person has already noted, this can pretty much be recovered using ODIN.
Definitely follow the advice given in Posts 2 and 3 of this thread to get into Download mode. If you're not getting the desired results using ODIN, what settings are you using? For example, what are the names of the .pit and .tar files you are using? Did you check or leave unchecked the "re-partition" option?
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
trill12 said:
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
Click to expand...
Click to collapse
What ROM did you flash. You might want to perform a factory reset and then flash the stock JFD ROM and see if that fixes your problem.
Good luck.
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
blizzard1017 said:
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
Click to expand...
Click to collapse
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Just get to DL mode as xtone and I stated in post 2 & 3 . Then flashed to JFD with odin v1.3 and click the repartition box in odin and you'll be fine .
Sent from my SGH-T959 using XDA App
I had this problem for the last two days, but I found a way to fix it thanks to a user (whom I don't know the name of)
I did this to go back to stock firmware (JFD), make sure you have that downloaded.
Look for Eugene's Galaxy S Froyo PDA, for the i9000, not the Vibrant. Flash it through Odin with the 512 pit file. It's not going to boot up but take you to recovery mode instead, and it's going to remap your Volume buttons, but you can still get into DL mode (up is now down, and vice versa but whatever)
Now Odin back to stock, using the same 512 pit and there you go! Should boot up with no problem. Now you can redo everything, but remember to never partition through ROM Manager ever again!
Sent from my SGH-T959 using XDA App
Is there a link you could provide him?
AgentFour20 said:
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
His exact symptoms happened to me when the noob in me decided to repartition in Rom Manager awhile back. I am just suggesting he uses this tool as an option. It's definitely a good tool to use regardless of how he got where he got.
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Mr.Duck said:
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Click to expand...
Click to collapse
Eugenes rom are on his new site www.eb-production.proboards.com
Sent from my SGH-T959 using XDA App
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
trill12 said:
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
Click to expand...
Click to collapse
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
AgentFour20 said:
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
Click to expand...
Click to collapse
Apparently. Completely forgot I attempted to enable it. I was freaked all the way out trying to repair the damn thing.
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
Hi I have a samsung vibrant that was running bionix v and it suddenly bricked itself. So i decided to use odin as I have in the past but this time when I get into download mode, it says key pressed, 164 on the top. I then use odin and it flashes successfully but once it reboots it stays on the vibrant screen for about 5-10 seconds and then it shuts itself off. I think its because im using an ld version of odin, which is odin 3 v1.7. I really need help please
Where you using a stock kernel?
Sent from my MB200 using Tapatalk
I am having this same exact exact problem.
I am soo pissed. I have been running fine with Bionix, then day 2 after installing DOW kernel, my internal memory card is fried.
I mean absolutely FRIED.
I can't get past boost screen *(It shuts off like yours does too)
I can't ODIN with anything, because it shuts off. If I try to plug it in, it will just battery charge loop.
I'm at a loss here too.
I've installed Eugene's OC kernel, TTbal's OC kernel, and the old DOW OC kernel's fine. Everything has been great. My phone handled 1.4 like a champ.
But now, nothing works. NOTHING.
*sigh
I also installed dow kernal and then a few days after that it just suddenly decided to shut itself off
Sent from my T-Mobile myTouch 3G Slide using XDA App
If it turns on its NOT bricked....this term is soooo loosely used.
odin back,reflash and allow 10-15 minutes to set up after full boot
Sent from my SGH-T959 powered by TW's Bionix V1.2.1,DOW.
ameedi600 said:
Hi I have a samsung vibrant that was running bionix v and it suddenly bricked itself. So i decided to use odin as I have in the past but this time when I get into download mode, it says key pressed, 164 on the top. I then use odin and it flashes successfully but once it reboots it stays on the vibrant screen for about 5-10 seconds and then it shuts itself off. I think its because im using an ld version of odin, which is odin 3 v1.7. I really need help please
Click to expand...
Click to collapse
If it turns on then it is not bricked, although it can be frustrating to fix it.
I will suggest following
1) Start ODIN and get Vibrant in download mode
2) ODIN Eugene's Froyo-that-does-NOT-brick. Do not check re-partition in ODIN. Do not use PIT512 file to re-partition
3) Reboot
4) Start ODIN again and get your Vibrant in Download mode again
5) ODIN PIT512 file and UVJFD stock, make sure you check repartition in ODIN this time.
6) Reboot
7) Re-root and install ROM Manager from Market
8) CWR flash or ODIN whichever version of ROM you like.
I hope this help.
You're probably in luck because the phone still turns on. In the future try to be real specific about what you were doing leading up to the bricking, things usually don't suddenly brick themselves. Follow ssiddiqi1's instructions and you should be fine.
Sent from my Vibrant using XDA App, Bionix-v 1.21
Try this: http://forum.xda-developers.com/showthread.php?t=954509
There have been several people, including myself, who have had this problem. No matter what you Odin, Including Eugene's no brick fix, the phone will not boot into recovery mode after Odin flashes a .tar file. No combo of .pit and .tar files work and it dose not matter what version of Odin you use. Nothing works. Trust me people the phone is BRICKED and there is no fix for it. Sorry.
Some threads about the same problem.
http://forum.xda-developers.com/showthread.php?t=955593
http://forum.xda-developers.com/showthread.php?t=956164
http://forum.xda-developers.com/showthread.php?t=955623
http://forum.xda-developers.com/showthread.php?t=957675
drewdude007 said:
There have been several people, including myself, who have had this problem. No matter what you Odin, Including Eugene's no brick fix, the phone will not boot into recovery mode after Odin flashes a .tar file. No combo of .pit and .tar files work and it dose not matter what version of Odin you use. Nothing works. Trust me people the phone is BRICKED and there is no fix for it. Sorry.
Click to expand...
Click to collapse
Version of ODIN does not matter, I agree. But if phone turns on, it is not bricked. Probably partition is messed up. Eugene no brick froyo (without a PIT file and no repartition) should get the phone to boot into a buggy vibrant 1900 version, then ODIN with PIT512 and repartition should get you back into bootable phone with fixed partition.
As I said it is frustrating but it is fixable. I had exact same scenario with Eugene Dead Horse kernel. The steps I wrote in my other posting, fixed the problem.
EDIT: You do not need Recovery mode. Recovery is not going to do any good due to messed up partition. You need only Download mode for ODIN to ODIN no-brick-froyo then UVJFD.
ssiddiqi1 said:
Version of ODIN does not matter, I agree. But if phone turns on, it is not bricked. Probably partition is messed up. Eugene no brick froyo (without a PIT file and no repartition) should get the phone to boot into a buggy vibrant 1900 version, then ODIN with PIT512 and repartition should get you back into bootable phone with fixed partition.
As I said it is frustrating but it is fixable. I had exact same scenario with Eugene Dead Horse kernel. The steps I wrote in my other posting, fixed the problem.
Click to expand...
Click to collapse
So I just tried it again to be sure. I flashed Eugene's no brick Froyo with no .pit and re-partition NOT checket. I then flashed JFD with the 512.pit and checked re-partition. I get the same results... Odin flashes and says completed at which point it should boot into recovery and finnish doing its thing. However all the phones with this problem fail to boot into recovery and just keep showing the battery charging, turn off, and show the battery charging picture over and over until I unplug the usb. At which point I press the power button and it boots up to the Vibrant splash screen the shuts off. This happens every time.
Sent from my MB200 using Tapatalk
Drewdude
Why should it boot into recovery after you ODIN JFD and repartition. It should reboot normal. Are you sure, you have a good UVJFD.tar file? A while ago, UVJFD odining messed up my phone. It was bad UVJFD.tar file. I would recommend go to Teamwhisky web site at http://www.teamwhiskey.com and look for Shorty's File Locker. I used UVJFD, PIT and ODIN from Shorty last week and it worked. Here is a direct link to it http://board.teamwhiskey.com/viewtopic.php?f=3&t=1322
Also successful Odining of Eugene's no-brick-froyo should boot you into a normal boot with a few errors, no Recovery. If needed, I can upload my copy of Euegen's no-brick-froyo, which had always helped me.
The ONLY .tar file that would flash and boot up the phone is the JK2 .tar found in this thread.
http://forum.xda-developers.com/showthread.php?t=799105
However, after flashing it I get the this error message and the phone does not access to the internal or external memory card.
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.
After Odin the phone will not boot up at all. I have downloaded the .pit and .tar files from Team Whiskey's site and i get the same thing.
drewdude007 said:
The ONLY .tar file that would flash and boot up the phone is the JK2 .tar found in this thread.
http://forum.xda-developers.com/showthread.php?t=799105
However, after flashing it I get the this error message and the phone does not access to the internal or external memory card.
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 think, you are not getting your Internal SD card partitioned properly, therefore mounting issue. Maybe download again pit512 file from Shorty's File locker? Sometime during download files get corrupted. Its worth downloading it again. Also in ODIN check options Re-Partition, Auto Reboot and F. Reset Time. Do not check Flash Lock, Do not check Phone EFS Clear and Phone Bootloader.
I had been using ODIN3 v1.81. Karylon360 posted it on XDA a few days ago. YOu should find it in Vibrant Dev Section.
EDIT: See dan0zone post below
drewdude007 said:
The ONLY .tar file that would flash and boot up the phone is the JK2 .tar found in this thread.
http://forum.xda-developers.com/showthread.php?t=799105
However, after flashing it I get the this error message and the phone does not access to the internal or external memory card.
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
There are files on the data side of JDF that is needed to boot if you wiped everything ... so if you got JK2 to boot to this error then ODIN to JDF and you should be good ....
No matter what when I Odin JFD, and I have downloaded and re-downloaded the .pit and .tar files from from Team Whiskey's site as well as others, I get the same results and the phone won't boot.
I am getting a replacement phone, thank god. However, I would really like to find a fix for this so I do appreciate all the help!
I did post this problem on Team Whiskey's Facebook page if anyone would like to see all the things I did yesterday. Just scroll down and look for my (Andrew Neubauer) post.
http://www.facebook.com/home.php?sk=group_180393771989565&ap=1
I still need help, I am now stuck on the setupconnection on odin, I was going to try to flash eugenes no brick but I cant find it on xda. Can someone please help me and can someone also maybe post a link to eugenes no brick
nevermind I got through the setup connection part Thank you to all that helped