After almost a brick, with lots of help from forums I am partially back to normal. I am hoping I can get all the way there.
Installed JI6 back on. Now when I go to boot menu I get MBR Checksum Error and Movinand Checksum Confirmation Fail messages in there, but it seems to boot fine.
The whole problem started when I stupidly went into Clockworkmod recovery 2.5.1.2 and selected under advanced menu, partition sd. I selected 1024mb and I forget the next selection.... But that of course hosed everything up. Couldn't boot.
Put on Eugene no brick froyo, and back to JI6 (after hours of getting no where).
So now I am on JI6, but still not right due to checksum fails...
I can get into Clockworkmod recovery still, is there anything in there that would let me put the internal sd that I messed up back to factory partition? Many options, but no manual on the thing.
I tried wipe data/factory reset, but leaves me in same boat with checksum fail.
What about under mounts and storage, there is format sdcard, format boot etc...
Basically, can the cwr partition sd be undone to factory?
Any help from the experts appreciated.
Try Supercurio's kernel+Voodoo, it fixes MBR.
Find your kernel in the thread here
http://forum.xda-developers.com/showthread.php?t=870480
Stay away from JK and JL builds since they are Froyo kernels and you have Eclair still running.
Looks like they are all JK and JL in there.
My whole goal last night was to backup ji6 that I had, and put on Nero 3 to try out froyo. Would that be a problem? I basically want to put Froyo on, but be able to go back to JI6 should the official release from tmo eventually arrive.
You did almost all the correct steps. the only part you forgot was to ODIN JFD onto your phone after using Eugene's Froyo the doesnot brick and before ODIN JI6 onto your phone.
In the bible sticky, there should be links that contain JFD. When you odin with JFD, select the repartition box. But only do this for JFD. Hopefully that helps you to fix your issue.
I searched and found JFD. What does that do? I went to Nero 3 seemingly fine. Hope no issues since I didn't do JFD. I guess if I try to go back to stock should an official release ever happen, I would include that int eh steps.
Thanks.
dpoliteski said:
Looks like they are all JK and JL in there.
My whole goal last night was to backup ji6 that I had, and put on Nero 3 to try out froyo. Would that be a problem? I basically want to put Froyo on, but be able to go back to JI6 should the official release from tmo eventually arrive.
Click to expand...
Click to collapse
Look through that thread, I am pretty sure I've seen supercurio provided JI6 kernel+voodoo on a user request.
EDIT: looks like 2.1 kernels came out broken with Voodoo.
Try ODIN back to JFD, flash a latest 2.2 ROM like TW nerov4.1, it contains the latest Voodoo CWR that should fix the MBR issues.
dpoliteski said:
I searched and found JFD. What does that do? I went to Nero 3 seemingly fine. Hope no issues since I didn't do JFD. I guess if I try to go back to stock should an official release ever happen, I would include that int eh steps.
Thanks.
Click to expand...
Click to collapse
Jfd is actually for our phones. It also includes all the information to "reset" the partitions and the mbr. The Eugene rom, while a life saver, is an i9k Rom. But yeah, if you have anymore issues, odin jfd with reparation checked and it should clear up a lot of issues.
"if you amplify everything, nothing is heard"
Moved of: Samsung Vibrant > Vibrant General
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
Related
So, I messed up. The plan was to uninstall RyanZA's lagfix, then flash JAC's new OC/UV kernel with Voodoo. I got distracted, and didn't uninstall the lagfix before flashing (through Clockwork, if that matters). My phone didn't boot after an hour, so I figured I'd nandroid back and not be so stupid this time. When I tried, I found that I couldn't because of the change to the /data from Voodoo. So then I figured I'd just use Odin to go back to stock, I've done it a couple of times before. That didn't work either, Odin went just fine, but it still doesn't get past the black screen. I read the Voodoo thread, and saw the "disable-lagfix" thing you can do, but now I can't mount my sdcard, and when I try to push it with ADB, it says permission denied. How can I fix this? Also, as an aside, since I flashed the stock back on, with the T-Mobile boot anim and all that, will I be able to get it replaced, if need be?
Flash this first:
http://forum.xda-developers.com/showthread.php?t=740558
Then flash back to stock with odin, worked for me.
Yeah, reading into the voodoo thread some more, I found it, and just fixed everything. Thanks for the quick reply! Odd that the froyo rom fixes it, but whatever, happy to not have to go to T-Mo tomorrow!
Zaphodb2002 said:
Yeah, reading into the voodoo thread some more, I found it, and just fixed everything. Thanks for the quick reply! Odd that the froyo rom fixes it, but whatever, happy to not have to go to T-Mo tomorrow!
Click to expand...
Click to collapse
Yeah, I soft bricked my phone yesterday and couldn't get it back up and running with the stock rom until after I flashed eugenes froyo rom first. My guess is that because eugene codes his roms to automatically format your OS drive it clears everything out and sets a fresh slate so you can than flash the stock rom back without issues.
Pure speculation on my part though. Glad you got it fixed.
This is my second time trying to restore a backup using clockwork and it just hangs on the vibrant screen. The first time I forgot to disable voodoo so that was the problem then, but this time I was on obsidian froyo rom and had issues where I was not able to get any data reception (3g/edge) so I figured to try and got back to stock to see if that solved the issue but no I'm stuck on vibrant screen. It went through the process of restoring then rebooting but it got suck. I am very frustrated because I can't never get it to work so what is the point of backing up stuff. I will be using odin again to restore and not use backups anymore. Just wanted to vent as I am very frustrated about this. If there is some out there that could shed some light as to why I keep getting stuck on the vibrant screen I would appreciate it.
Will be getting a replacement phone from my date issue, and yes my voice still works just not data part.
Sent from my T-Mobile G1 using XDA App
Froyo has a differnt kernel than eclair. You were trying to restore an eclair build, but you did not flash the stock eclair kernel first.
s15274n said:
Froyo has a differnt kernel than eclair. You were trying to restore an eclair build, but you did not flash the stock eclair kernel first.
Click to expand...
Click to collapse
what eclair kernel can i use for the future???
i odin back to JFD and my 3g/edge is working again i wonder why i lost it?
Probably the easiest thing to do would have been to flash a new custom rom with the kernel included, like Fusion/Bionix.
You could have flashed the stock kernel and then restored a JI6 nandroid too though I imagine. I've not tried yet. The stock kernel can be found in my signature or in the development section. I have a copy on my internal memory just in case.
I rooted my Vibrant yesterday, first timer, and everything went smoothly. I used the Classic way, had no problems. I got ROM Manager, to flash ROMs of course (I've gotten pretty impatient with Samsung and my Froyo) and I decided to partition the SD because I thought it would be a good idea. I did not know that it would partition the INTERNAL SD and brick my phone. After countless hours of Odin, rereading the instructions on this thread, trying to get it back to stock, I managed to get it running Eugene's Unofficial TMO Froyo Image. I am able to boot [Froyo] totally fine, but then when I try to revert back to build JFD or J16, I get the same black screen with only the capacative buttons on. My question is, is there any other possible way to fix this? I've tried almost every single method I've come across, read so many threads, and I've been unable to get back to stock. I've even created an elaborate scheme to walk into T-Mo to tell them I dropped my phone (playing the technologically disabled customer, of course) and asking for a replacement. I apologize for so much text, but I felt that explaining myself might work. Ideas would be much appreciated
With Odin -
Use this 512.pit
and this JI6.tar
These will take you to bone stock 2.1.
Thanks Drew, but I've tried that countless times and all I end up with is a black screen and lit up capacitive buttons. I want to go back to stock because for some reason, Eugene's version of Froyo doesn't allow me to install apps because the supposed, "internal memory" is full. Plus, going back to stock will allow me to redo everything from the beginning.
make sure you flash a 2.1 compatible kernel 1st before downgrading from 2.2 to 2.1..
Try flashing "Eugene's Froyo that doesn't brick" on odin then flash JFD/JI6 whichever you wanna go back to..
WARNING: Flashing Froyo that doesnt brick will wipe internal SD..
Good luck..
$0.02, why not just flash the rom you want over the stock 2.2?
just factory reset, wipe partitions, wipe dalvik cache, fix permissions ALL in CWM
Then flash ROM of choice.. Clean flash.
Can you link that file for me please?
Also, I just factory reset, and I'm still unable to getapps from the market ,so flashing from 2.2 would be impossible. For app space, it says I have 0.00 B
Had same issue, didn't want to go back to stock though . Look for a post with mbr check sum error, quick walk through
Really? I looked it up, but i don't remember getting that error.message.
Hello,
I tried to recovery my phone by using Odin3 to install the stock 2.1 vibrant rom. I am using the rom from the official sticky about fixing a bricked phone.
Odin3 1.0 did not work and it would always freeze on a process even after trying it over and over again at least 5 times. So, I changed to use Odin3 1.7 which I found a link to on xda. This one installed successfully and went through the whole process and my phone rebooted. When it rebooted I saw the Samsung Vibrant Screen, then the T-Mobile screen then the Galaxy S screen fine like normal. But once it got passed the S screen a black screen would come up and all the button lights stay lit up and nothing happens for hours. I tried installing the rom several times, tried different links to the offical JFD stock rom, but everytime I try to install the same thing would happen. What do you recommend I should do to fix this problem?
wipe cache partitin , factory reset in rrecovery ?
Yes, I did. I wiped cache and data, but it still is is still stuck at the black screen.
Your using the JFD.tar in PDA and 512.pit in PIT and Repartition is NOT checked?
Yes, I made sure it was not checked and It was checked automatically the first time and I didn't realize that odin checks that automatically, so I unchecked it and did it a second time. The phone still gets stuck at the black screen with light up buttons.
I am trying the Eugene's Unofficial Froyo rom right now because what initially bricked my phone was installing 2.2 from Kies and that failing. When that failed I unplugged the phone and got the computer to phone icon screen and could no longer boot, so I went to install the stock rom.
The problem I am having with Eugene's Unofficial Froyo rom I am having now is that I have 0 space for applications and cannot install applicants even after doing a wipe and factory reset. Does this have to do with accidently setting it to re-partition and if so, how can I fix the no application storage issue so that I can install applications?
Thanks
I was thinking he designed this ROM just specifically to help bricked vibrants...I think you just use it as a means to reflash another ROM or back to stock or whatever.
I did what you had phone ! PC.. last night to my wife's phone....left it on that screen and plugged into pc with ODIN open..it showed a COM port so I flashed it like that and it boots right up.
I wonder if it has anything to do with Voodoo? I had a Voodoo Lagfix installed prior to doing the upgrade to Froyo 2.2 using the official method. May be why it failed. so I decided to flash back to stock. When I flashed stock 2.1 the phone would boot up then show the Vibrant Screen then the T-Mobile intro then the Galaxy S intro but once it got passed that the screen would go black and the buttons would stay lit up. I flashed Eugene's unofficial 2.2 ROM (no longer posted on xda, but it is on his website). That booted up perfectly, but the problem was that I now had 0 application storages and apps could not be installed on internal memory (could still install apps on SD card, I used this to install Rom Manager to the SD Card to flash Clockwork Recovery just in case)
Today, I tried flashing the Stock 2.1 rom back onto it (Phone was currently running Eugene's rom), but I have the same result with the black screen and lit buttons.
I looked at the FAQ for removing Voodoo and added a folder named "disable lagfix" in the Voodoo folder on the internal SD card. I ran this, but the problem still persisted, so I decided to flash again to see if it would be fixed. Still the same thing occured.
If this is a Voodoo problem, is there another method for removing Voodoo that I could try? I need to make sure that it is restored to the default RFS file structure that came with the phone and flash stock 2.1
Hmmm...odin back to eugenes froyo & unmount ur internal sd & format...go ahead and remove ur microsd & sim also...& then try to odin just the. Tar for jfd no pit ...no repartition..try to use ka6 instead of a 2.1..
Sent from Bionix V powered Vibrant
flash back to JFD eclair from bible with 512 pit and repartition ticked .
just for record JFD.zip goes in to pda
ViralCipher said:
I wonder if it has anything to do with Voodoo? I had a Voodoo Lagfix installed prior to doing the upgrade to Froyo 2.2 using the official method. May be why it failed. so I decided to flash back to stock. When I flashed stock 2.1 the phone would boot up then show the Vibrant Screen then the T-Mobile intro then the Galaxy S intro but once it got passed that the screen would go black and the buttons would stay lit up. I flashed Eugene's unofficial 2.2 ROM (no longer posted on xda, but it is on his website). That booted up perfectly, but the problem was that I now had 0 application storages and apps could not be installed on internal memory (could still install apps on SD card, I used this to install Rom Manager to the SD Card to flash Clockwork Recovery just in case)
Today, I tried flashing the Stock 2.1 rom back onto it (Phone was currently running Eugene's rom), but I have the same result with the black screen and lit buttons.
I looked at the FAQ for removing Voodoo and added a folder named "disable lagfix" in the Voodoo folder on the internal SD card. I ran this, but the problem still persisted, so I decided to flash again to see if it would be fixed. Still the same thing occured.
If this is a Voodoo problem, is there another method for removing Voodoo that I could try? I need to make sure that it is restored to the default RFS file structure that came with the phone and flash stock 2.1
Click to expand...
Click to collapse
When you do the disable lagfix are you rebooting and letting it convert the filesystem back to rfs or are you just powering down and going to d/l mode and trying to ODIN? You need to reboot the phone and let Linda do her thing and power up, then power down etc etc..
jmcghee1973 said:
When you do the disable lagfix are you rebooting and letting it convert the filesystem back to rfs or are you just powering down and going to d/l mode and trying to ODIN? You need to reboot the phone and let Linda do her thing and power up, then power down etc etc..
Click to expand...
Click to collapse
Yes, I rebooted after applying the disable lagfix, but it booted normally and didn't seem like it was doing the Linda thing....I wasn't sure if it worked or not. How would I know if it is back to using the RFS system?
I tried different roms and I had no luck. The KA6 Rom that flashes via odin installs fine, but it goes to the Recovery Screen the E3 one I think, and when it tries to mount DATA and other partitions it fails to do so, and somethings fail to be wiped. It doesn't boot.
When I run the JFD odin, when it goes to recovery for the first time it has one error where it fails to wipe DATA. Not sure if these are the reasons why I am having problems though.
I formated all partitions including the internal sdcard. Still no luck.
So far the only ROM that I got working is Eugene's 2.2..but I can't install applications with that one.
I tried installing the Bionix V Rom via ClockWork Recovery, but once it begins to Copy Files it errors out with an Error on line 13 and copy's out an error log. I posted a response to the thread about this ROM. I redownloaded to ensure it wasn't corrupted.
*****If you need more information on the EXACT Rom I installed prior to the brick here is the thread to the rom I installed. Maybe that will help you help me more ******
This is the rom I had before attempting to upgrade to Froyo:
http://forum.xda-developers.com/showthread.php?t=791478
I installed the Stock Recovery version.
Edit: I know this rom above is a kernal mod. I did flash the stock Vibrant kernel prior to installing the JFD ROM from this link: http://www.justanotherdev.slackdev.com/kernel-vibrant-stock.tar.md5.tar
crap dude do yo uhit repartition when u flash ka6 ? if so dont do so if its only update , dont check partiton if you flash just an update , hit partitoon if u flash offical release .
yes go back to jfd repartiton update to ka6 withou repartiton
bartek25 said:
crap dude do yo uhit repartition when u flash ka6 ? if so dont do so if its only update , dont check partiton if you flash just an update , hit partitoon if u flash offical release .
yes go back to jfd repartiton update to ka6 withou repartiton
Click to expand...
Click to collapse
When I install the JFD with or without repartition I get passed all the boot screens, but it screen goes black and buttons light up..Sorry if I am being a noob and missing something obvious...but I followed those instructions, and I did it multiple times as well.
FIXED!!!
I fixed it wohooo!!!! I flashed Eugene's Froyo that doesn't brick version then flash back to stock JFD and its working perfectly! Thanks XDA! Found out that a lot of people with this issue after having Voodoo installed and installing a different rom, and that this rom was made to fix the Voodoo brick. Funny thing is the Eugene's rom fails on recovery with errors in this case, but it still unbricks the phone lol
Ahhh see lagfix didnt disable..glad you got it working..
Thanks for your help. I now am using the Bionix-V Rom with the Dragon-Kernel Voodoo and let me tell you I love this phone even more now with this Rom. Loving the Gingerbread theme and it runs super fast. Stock is too slow for me lol Anyway, this is resolved no more offtopic posts lol...
ViralCipher said:
I fixed it wohooo!!!! I flashed Eugene's Froyo that doesn't brick version then flash back to stock JFD and its working perfectly! Thanks XDA! Found out that a lot of people with this issue after having Voodoo installed and installing a different rom, and that this rom was made to fix the Voodoo brick. Funny thing is the Eugene's rom fails on recovery with errors in this case, but it still unbricks the phone lol
Click to expand...
Click to collapse
would you please tell all the steps you did to make it work
Hi I'm a new member,
I rooted my fascinate easily enough. Then searching and learning about ROMs and Kernels I decided to do use ODIN CWM Recovery to 'backup' or whatever most forums tell you to before installing a new ROM. Point is my phone is stuck in manual boot mode and I cannot undo it.
I have tried multiple times using ODIN plus the four stock files
Stock-i500-VZW-Kernel.tar.md5
Stock-i500-VZW-pit.pit
Stock-i500-VZW-Recovery.tar.md5
Stock-i500-VZW-System.tar.md5
(I always would try to implement them in order pit/system, pit/kernel, pit/recovery)
Unfortunately after the first one (pit/system) ODIN says the process fails, I go ahead with the other two and they both amount to nothing happening. My phone does not reset or do anything for this matter and I am forced to shut down ODIN and unplug my phone (upon which it dies with no battery).
Then I put back in the battery and Im back to before in manual boot mode with
Reboot system Now
Apply sdcard:update.zip
wipe data/factory rset
wipe cache partition
Btw wiped data and wiped cache and it didn't help me =(.
Please someone help me, I really don't want this new phone to be dead... Thanks in advance
Oh and when I press "apply sdcard:update.zip" I receive
E:Can't mount \dev\block\vold\179:9
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
I really don't care at all about keeping the phone rooted or not or whatever. I just want to be able to make calls again!
So it looks like you're stuck in blue recovery ... sounds like something that Odining a stock package should fix.
Here is a nice thread for getting back to stock (it's a sticky in the general section). The packages include system, recovery, kernel, and radio in a single file (I've actually never odin'd four separate files to get back to stock, or even ever flashed a system-only file), though no pit file.
So open up odin with your phone in download mode (with the battery out, otherwise there's a small chance of odin stalling at the end), and use:
- either the DI01 all-in-one, EB01 all-in-one, or this DL09 package in PDA
- the pit file in PIT (the link says DI01/EB01 but it also works with DL09)
- check "re-partition" if it isn't already checked
- run odin and hopefully in five minutes your phone will work again If for some reason it doesn't, that thread has instructions for using heimdall, although I've never had to resort to it.
So try this and see if it works! (For which package to use, I'd suggest trying DL09 first (since you'll need it to get to the official froyo build) and DI01 if that fails. If you're wondering whether DL09+pit actually works, I've used it to get out of a "stuck in blue recovery after odining stuff" situation myself so yes, it works.)
Thank you for the response! It's encouraging to hear any support and I think yours is promising.
So unfortunately I tried D101 and no go. Turns out this was before I realized this was for 2.1 and I'd prefer 2.2 for the upgrades. Although would you suggest 2.1 for the purpose of rooting/ROMing/Kerneling in the future? I ask because I'm slowly gaining confidence that after fixing this I might be willing to try this again...
Odin (1.7 -> I decided at your poster friend's advice to upgrade from 1.3) worked well said 'pass' and everything. Unfortunately when booting my phone it went straight to the boot screen as always.
Meanwhile I'm downloading the EB01 and your suggested DL09 to test those two.
Hopefully one of those will work but if not, I guess I'll try that heimdall technique the poster suggested in the other forum. Hopefully not tho b/c it looks a bit more complicated.
I'll let ya know if one of these others works.
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
mattjac1 said:
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
Click to expand...
Click to collapse
Definately stay away from rom manager cwm if you have the voodoo lagfix enabled, but since all the new fascinate roms are edify scripted, flashing through cwm in rom manager would be ok.
Sent from my Froyo'd Evil Fascinate full of PB&J