bootstrap recovery...

[wildman]

Try Names like "TEST_123456789_V1" because the app is finicky when the name is the case.

 

[wugawug621]

with the name of nothing but 2011 it still says MD5 mismatch. when i highlight it in recovery, it still has a dash next to the 2011

exactly as it looks on the screen

Choose an Image to restore

- 2011


clockworkmod recovery v2.5.0.6
checking MD5 sums...
MD5 mismatch!


i did not add the - or the /

 

[wugawug621]

ok ill try the test one

 

[wugawug621]

no go with the test name either, still says MD5 mismatch

 

[wildman]

no go with the test name either, still says MD5 mismatch

Strange, well I am drawing a blank, maybe another user gets a ideal.

Good Luck

 

[wugawug621]

Or would there be anywhere to get a STOCK 2.2.1 with .345 ?? that would work fine coming off f GJ 2.5? and let google's service bring back most of it? and ill just re-root and go from there. if anything this has been one hell of learning experience. Maybe we shouldn't make renaming something an option if it screws everything up

 

[wildman]

You can install the SBF to restore to stock if all else fails.

 

[wugawug621]

Don't you need a linux based computer to do that?

 

[wildman]

No you can do it with a windows pc, you can read up on it from DROID X 2.3.340 System SBF Released for 2.3.320 Leak Users - Droid Life: A Droid Community Blog , this is only the system SBF but if you read up on the process over at How to upgrade from 2.3.320 to 2.3.340 (.340 is the verizon official) and maybe get it up and running.

 

[wugawug621]

hmmm. idk, says for .320 leaked people only, i was on .345 i got via it being pushed to the phone, and to be quite honest, it'd be my luck that id' screw that all up and brick the phone, like those threads say RSD lite can do

 

[wildman]

I have used the system version and so have other but if you do not feel comfortable then I understand, it took me a while to risk it. Check out this one http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html

 

[wugawug621]

that one seems more complicated then the rest, lol. im not 100% in the know with this stuff like with install specific files and such within recovery, i take it that the stock 2.2 avalible in ROM manager would be bad, being that it says must have 2.1 installed

 

[wildman]

Not wise to install anything made for 2.1 because this will brick the device or place in boot loop. My suggestion is read up on flashing sbf because this will be you only option if your bootstrap image isn't working..

 

[wugawug621]

thats what i figured, i just didnt know if anyone had an untouched 2.2.1 rom available or if there is anyway around the MD5 deal and still use the Nandroid

 

[wildman]

I have learned so many tricks around the error you reported but you report the didn't work for you but I have been able to get all mine worked out, the name is the main reason that you get the m5 error. And as for a untouched image that is what the sbf is and until you figure out flashing them you wont find a simple solution.

 

[wugawug621]

would there be anyway to get a Full SBF? i have RSDlite now, but is just using the system SBF ok to use going from this rom? GJ 2.5 (idk if that has anything to do with it) or will just the .340 SBF from the droid-life site do the job? i just dont want to brick the phone lol

 

[wugawug621]

or would using the advanced section of recovery help, like doing each selection one at a time, would that get around the MD5?

 

[.46caliber]

anything i can name it or put it somewhere that clockwork will use it? or can i go into clockworkmod manually (rebbot into recovery) and do it on the menus?

Did you bootstrap?

 

[xliderider]

By any chance did you rename the backup after making it? If you did, don't use any spaces in the backup filename.

 

[wildman]

By any chance did you rename the backup after making it? If you did, don't use any spaces in the backup filename.

We already cover that angle in depth with no luck..