MD5 Sums Mistmatch? 2.2 - Vibrant Q&A, Help & Troubleshooting

I recently flashed FroyoCollab with ULF kernel applied a lagfix, then decided to restore an old ROM using CWM recovery... So I disabled the lagfix via clockwork, then when I go to restore it says MD5 Sums mismatch...
Any fix for this?
Can I ODIN back to stock or will that cause problems as I'm not totally sure if that would work.
I first began with the voodoo lagfix in cwm then went back and changed it to overkill, then went back again and disabled all my lagfixes.
EDIT: Ok I ODIN'd, however, I flashed to Fusion 2.1 and now my apps don't reinstall when I use TB?? WHy?

I don't think backups store the kernel I could be wrong though odin to stock should work
V5 custom vibrant

Cwr will not backup kernel so you will have to Odin to stock
Sent from my SGH-T959 using XDA App

Flash the stock 2.1 kernel first, then restore.
Or flash a new rom that includes a kernel.

Related

what is the procedure to ensure everything clean before ROM flash

To all experienced Custom ROM installers,
I have a rooted vibrant, during the holidays I performed my first custom ROM flashing
During these days, I installed and re-installed a stock and custom ROMS a number of times. I think I got remmants of ROMS that I installed.
I want to go back to the stock android 2.1 JI6. I have a rom manager backup before I installed the custom rom
What is the procedure for a good wipe to ensure that the system is clean before I flash the stock t-mo vibrant 2.1 JI6 ROM ?
thanks
Reverting back to stock through Odin is more preferable. But if you're going to nand restore a stock 2.1 via clockwork, then you MUST flash a 2.1 kernel or any 2.1 custom rom that has the stock kernel. I'm not sure wether you flash the stock kernel beforehand or after the nand restore. But yeah, if you're currently on a 2.2 rom, revert that kernel to stock 2.1 before restoring the 2.1 stock nand or risk soft bricking your device!
Sent from my GT-I9000 using XDA App
thank you for the tip.
That is why when I restore my ROM manager backup (which was a 2.1 nackup) it froze and will ot boot. I will try restoring the 2.1 kernel first before restoring the backup
make sure the 2.2 rom you're using is compatible with a 2.1 kernel coz that will soft brick too

ClockworkMod Recovery restore

Hey guys, I made a backup with clockworkmod before I flashed Nero. Now I want to return to stock to try the official Froyo. I tried to restore my backup via Rom Manager, but after my phone booted the only thing on the screen is the status bar and "searching" and the date. The phone keeps refreshing once in a while but I can't do anything with my phone. I disabled voodoo before I flashed the backup. Is it supposed to take this long on the first boot? Any help would be appreciated.
When going from a 2.2 build back to a stock 2.1 build, you have to flash a 2.1 kernel at the same time. Your backup doesn't include the stock kernel.
You will have to use odin.
Sent from my nuclear powered submarine!

[q] someone help

I downloaded Rom Manager from the market and through that program, I flashed the latest CWM recovery image (3.1.0.0), I rebooted into recovery to check the work and sure enough it was the right recovery....I then found out that Franco had released a new kernel so before I even flashed it, I backed up the phone, than I flashed the franco kernel, that being v18.1 cfs, since I do not have 2.3 I didnt use v18.1 bfs...Its now stuck at the LG screen is franco's kernel's compatible with Clockworkmod recovery ?
Root: Gingerbreak 1.2
Rom: Devoid Froyo Final
Recovery: CWM 3.1.0.0
P.S.- Ive also attempted at flashing franco kernel v17 since I know that was the kernel I was using before I attempted to flash the new kernel
Im not to sure if it's a partial brick or my phone's completely ****ed
I would like to go back to using AmonRA's recovery image considering Ive always used AmonRa....the only reason I even attempted anything with CWM is because I heard it provided more options in recovery
What should I do ?
francos kernel is compatible...its something messed up with the phone....install the backup you had earlier...before flashing a new kernel you have to wipe everything...that may be the cause of error..
If you can boot into recovery then your phone is recoverable. Restore your backup and try again, this time by wiping cache (not everything). And you can easily switch between recoveries, click the ciaox's flashable recoveries link in my signature.
Sent from my LG-P500 using XDA App

[Q] CWR Backup

I'm thinking of Odin back to a 2.2 ROM from Miui. But I can't remember if the CWR back-up of my Project V contains the Kernel as well? I'm wondering if I can just Odin back to stock. and run the back-up or if I need to Odin back to stock, and flash Proj V and start over with the individual tweaks I put in????
does not have kernel, but you should be able to odin back to stock, boot in CWR, flash a 2.2 kernel, and then restore your backup

Which kernel do I have?

I checked my settings>about phone and it says I have 2.6.32.9 kernel and T959UVKA7 baseband
When I go to clockworkmod recovery, it says Voodoo Lagfix recovery
So which one do I have? Voodoo or Stock?
The reason why I'm asking is because yesterday I got bricked while trying to recover back to nandroid from ICS, and had to odin my way back to stock, and then reroot, and then restore from nandroid. Also, why did I get bricked in the first place?
cashboxz01 said:
I checked my settings>about phone and it says I have 2.6.32.9 kernel and T959UVKA7 baseband
When I go to clockworkmod recovery, it says Voodoo Lagfix recovery
So which one do I have? Voodoo or Stock?
The reason why I'm asking is because yesterday I got bricked while trying to recover back to nandroid from ICS, and had to odin my way back to stock, and then reroot, and then restore from nandroid. Also, why did I get bricked in the first place?
Click to expand...
Click to collapse
What rom was your nandroid, stock or a custom rom? And if you are restoring a nandroid from ICS to a pre ICS rom you will soft brick because of the kernel incompatibility since nandroid does not backup or restore the kernel. That's why you always have to odin to stock when you want to come back from an AOSP rom like CM7, MIUI, or ICS.
I already bricked it just now before i read ur message. I had axura 2.2.7.2. And yes, I odin'd to stock, i rerooted, installed rom manager, and then I tried to restore nandroid.
I am stuck in a bootloop, which takes me to Samsung Recovery Utils blue screen.
I go to reinstall packages, and then it takes me to green clockwork mod screen. I format user data, and I then restore from the nandroid. Then it takes me to vibrant logo. Phone goes off for a sec, restarts to vibrant logo, and I'm at the Samsung Recovery Utils screen again. Been trying to fix it for hours now.

Categories

Resources