Database Info

So I have one of those dreaded 2.51 stock ROMs, what now?

Greetings,
I just bought and legally unlocked a Motorola Defy from Spain, and the carrier was Vodafone.
Checking the ROM in it, it says the following:
System version:
Blur_Version.2.51.1.MB525VF360Blur.Vodafone.en.ES
While the build number says:
JRDNEM_U3_2.51.1
So it's a 2.51.
What exactly does this mean?
I've searched the forum up and down and I still don't quite get it.
The only info I got was:
walter79 said:
!!!!!!!!! Flash only if you come from a 2.21 or 2.34 rom "That is because it has version 2 for CG31 and CG39, if you are on stock 2.51 those versions are 3 and if you flashed leaked froyo those are 4 and you cannot flash any firmware with lower versions. if you are on 2.21 or 2.34 you can flash this, otherwise you will brick your phone. !!!!!!!!!!!!!!!
Click to expand...
Click to collapse
And I don't understand what this means. What's version 2 and 3? What's CG31 and CG39?
There's no official 2.2 Froyo update for my phone, and AFAIK there's no news saying when that may happen.
I don't want Blur (I want to be able to use stock Android widgets), and I don't want the Vodafone or any other operator's stuff.
I know there's no stock ROM without those things so I'll have to do with a modded ROM (I'm very compelled to getting this one).
I'd also like to have the oportunity to reflash the phone to its stock ROM, in case I need to send it to warranty.
I flashed my girlfriend's Milestone with the latest UK official ROM through RSD Lite (after the phone bricked when I used the official update procedure!), and it was a rather simple procedure.
So given that I have one of those "bad" 2.51 ROMs, what additional procedures do I need to make, besides the sbf flashing through RSD Lite?

don't worry mate.. i have 2.51 too.
where to start it..
um.. maybe this.
CMIIW.
SBF is just like RAR and ZIP, it is packaging file.
inside SBF there many files, two of those are CG31.SMG & CG39.SMG.
some newer release SBF (froyo) might have EARLIER "version" of CG31.SMG and CG39.SMG
than CG31.SMG and CG39.SMG on your phone (2.51).
which mean it can't be done to flash it (flash to earlier version).
as long as you not flashing CG31.SMG and CG39.SMG when you apply froyo (leaked or official) update. it's fine..
i think someone here (fritolays) found method to FIX the SBF to exclude CG31.SMG and CG39.SMG. name of that SBF is FIXED SBF.
so if you want to upgrade to froyo, do not flash FULL SBF.
but use clockwork recovery to wipe data and wipe cache, then apply the nandroid backup, then flash the FIXED SBF using RSD Lite 4.9.
----------------------------------------
my advice before you doing anything,
do a factory reset, get root, install custom recovery,
then just create a nandroid backup of your stock 2.51 with custom recovery,
and make sure you have a FULL SBF of 2.51 of your region, and you have FIXED SBF 2.51 of your region.
so if you want to go back to eclair stock:
-install custom recovery, go to custom recovery, wipe data and wipe cache,
-apply restore nandroid backup of your stock
-flash the FIXED SBF 2.51 of your region.
-----------------------------------------

Ok, I now have a nice brick, for the moment.
After rooting, installing the clockwork mod and backing up my original ROM, I flashed a "fixed" SBF from the 3.4.3-11 version.
After the flash, the phone just hangs in the motorola symbol on and off (by about 2 minutes).
I tried both this SBF:
http://forum.xda-developers.com/showpost.php?p=12596803&postcount=845
and this one:
http://forum.xda-developers.com/showpost.php?p=12357943&postcount=62
Both give me the same result: Motorola logo on and off, and no boot.
The bootloader is still accessible.
RSD Lite says to power up the phone manually, but it does so by itself.
Is there some hidden ritual that I don't know of? (like unplugging the USB at a certain time or pressing some buttons?)
Any suggestions?
I've seen this one:
http://forum.xda-developers.com/showpost.php?p=12620475&postcount=7
But I don't even know if it's a fixed ROM or not.. should I try it?

Tried the following ROM with the same result:
3.4.2_155-Fixed.CEE_DEBLUR.sbf
I'm starting to get a bit preocupied here.
Help?

Try restoring a nandroid backup first, then right when you reboot go into stock recovery and flash the fixed sbf for that nandroid backup you installed and it should work fine. It sounds like you may have flashed a fixed sbf before you installed a nandroid backup. Hope this helps.
Sent from my MB525 using XDA App

Dewman4life said:
Try restoring a nandroid backup first, then right when you reboot go into stock recovery and flash the fixed sbf for that nandroid backup you installed and it should work fine. It sounds like you may have flashed a fixed sbf before you installed a nandroid backup. Hope this helps.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
How can I restore the nandroid I did previously?
The clockwork restore boot has been uninstalled, and the restore boot I have right now only has "wipe data", "wipe cache" and "apply update.zip"..

As far I know, you can't enter custom recovery from a boot loop. I don't know if this is correct, but the only way i see to you is flash the full SBF of your stock rom, that you can find here:
http://forum.xda-developers.com/showthread.php?t=966537
Tons of JRDNEM_U3_2.51.1, choose that best fits your phone and go. Next time, BEFORE flashing the fixed SBF, restore nandroid.

ToTTenTranz said:
Ok, I now have a nice brick, for the moment.
After rooting, installing the clockwork mod and backing up my original ROM, I flashed a "fixed" SBF from the 3.4.3-11 version.
After the flash, the phone just hangs in the motorola symbol on and off (by about 2 minutes).
I tried both this SBF:
http://forum.xda-developers.com/showpost.php?p=12596803&postcount=845
and this one:
http://forum.xda-developers.com/showpost.php?p=12357943&postcount=62
Both give me the same result: Motorola logo on and off, and no boot.
The bootloader is still accessible.
RSD Lite says to power up the phone manually, but it does so by itself.
Is there some hidden ritual that I don't know of? (like unplugging the USB at a certain time or pressing some buttons?)
Any suggestions?
I've seen this one:
http://forum.xda-developers.com/showpost.php?p=12620475&postcount=7
But I don't even know if it's a fixed ROM or not.. should I try it?
Click to expand...
Click to collapse
oh damn..
you just bricked your phone right...
the steps are wrong... the steps are:
root>install custom recovery>apply nandroid backup of froyo>reboot but immediately go to bootloader>flash fixed sbf of froyo.
you have to restore nandroid backup of froyo 3.4.3-11 first before you flash the fixed SBF of 3.4.3-11.
from your explanation,
you create backup of your 2.51 then flash the fixed sbf of 3.4.3-11?
if it is true, the ROM is still eclair 2.51 and you install the 3.4.3-11 firmware,
i think that's the problem.
you should restore nandroid backup of froyo 3.4.3-11 first before you flash the fixed sbf of 3.4.3-11.
after that, you follow what pays thread says to do to install his rom.
just because your defy cannot be started,
what you can do now is just flash your phone back to eclair 2.51 first with full SBF, not fixed.
the condition now is you have FIXED firmware of 3.4.3-11, but with 2.51 ROM inside.
just because it is fixed, you still have a chance going back to eclair 2.51
search Full SBF Eclair 2.51 of your region, and flash it with RSD Lite.
hope and make sure your battery is full enough to flash the full SBF, maybe 60-80% is enough.
because with that condition, i think the battery is not charging, even you charge it.
after everything is back to normal (eclair 2.51)
then if you still want to use pays, follow this method
-root
-install custom recovery, reboot to custom recovery
-restore nandroid backup of froyo 3.4.3-11 (if you can't find it pm me)
-immediately flash fixed sbf of froyo 3.4.3-11
-now your phone should froyo 3.4.3-11
-install pays rom with custom recovery

I flashed this sbf and I now have a working phone with a 3.4.2-155 firmware. Phew...
So I should have "restored the nandroid backup of 3.4.3-11" while still having the 2.51 firmware and only then I should have flashed the fixed firmware?
Sorry, this is really confusing for me.
With this 3.4.2-155 firmware, can I still do that procedure to get the pays rom?

ToTTenTranz said:
I flashed this sbf and I now have a working phone with a 3.4.2-155 firmware. Phew...
With this 3.4.2-155 firmware, can I still do that procedure to get the pays rom?
Click to expand...
Click to collapse
oh no...
you flash the FULL SBF of 3.4.2-155??
you should flash FULL SBF of 2.51...
i think you lost your downgradeability now...
but you still can use pays,
just follow like pays thread says.
just because you lost your downgradeability,
you shouldn't even care to flash the full SBF 3.4.3-11 now..
(you don't have to use any nandroid backup now to upgrade to newer build)
ToTTenTranz said:
So I should have "restored the nandroid backup of 3.4.3-11" while still having the 2.51 firmware and only then I should have flashed the fixed firmware?
Sorry, this is really confusing for me.
Click to expand...
Click to collapse
yea, you should do that...
while still having 2.51 firmware,
you should restore the nandroid backup of 3.4.3-11 first,
and then you flash the fixed sbf of 3.4.3-11.

Now you are +1 that can't go back to 2.1 \o/ (like me kkkk)
If you have flashed the full SBF from 2.51.1 you could still have a chance.
And yes, you can go to any ROM that is 2.2 now, test Pays, LiquidArc and BluelessGinger from JBoogie3 and Barebones from Fritolays(my favourite). Don't worry about nandroid backups anymore, just do the full SBF when you install a new ROM (it's what I do).

But as soon as the Spanish Vodafone release a Froyo ROM, I should be able to flash to that and still get the warranty if I need to, right?
Truth be told, I would never want to go back to 2.1, except for warranty procedures.

The problem is that, only if you can find a SBF from Vodafone ES you will have your warranty. And this is just a possibility, since this SBF was not released yet. Good luck for you (and for me, since I'm in the same situation, heheheh)

ToTTenTranz said:
But as soon as the Spanish Vodafone release a Froyo ROM, I should be able to flash to that and still get the warranty if I need to, right?
Truth be told, I would never want to go back to 2.1, except for warranty procedures.
Click to expand...
Click to collapse
as long as the official spanish vodafone SBF have the latest version of CG31.SMG and CG39.SMG inside (newer than CG31.SMG and CG39.SMG inside 3.4.3-11), it should be fine..
otherwise there's workaround though.
if just in case the CG31 and CG39 are in lower version,
you should restore nandroid of official froyo spanish (when it released)
then you flash the fixed sbf of that release.
i am sorry for your lost...
but you can still go back to 2.51 though..
but not in proper "real eclair 2.51"
i will post this method if you ask.

Helps to read all the threads on the process as there are many. Now the problem lies your on froyo and can't get back to eclair if you need to send it in for repair. The main thing tho is your back up and running.
Sent from my MB525 using XDA App

[Q] CM7 / ICS Flashing issues

I soft bricked my phone playing with ICS, I got a JIG and solved the problem
I can now ODIN back to any version and once rooted I can install any samsung based rom, the problem comes when I try to flash aosp both CM7 and any ICS beta
What happens is I select the zip, it runs a script and the phone reboots, I see the AT&T logo and then it mounts the sd card, it says it can't find the zip file.
I've tried Froyo, Eclair, even gingerbread (I know your not supposed to flash cm7 from gingerbread, I'm just running outta ideas) I have froyo bootloaders, I reinstalled them with heimdal. I've also done a master clear and erased the internal sd card
Does anyone have an idea of why this is happening?

Are you trying to install the zip from ClockworkMod?

Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.

Another problem
Ok, everything I see says I should flash from a captivatemtd recovery, but when I install Rom manager and select captivatemtd, it says their are no offical recoveries for it, I'm currently running cognition froyo 2.2 with froyo bootloaders
Does anyone know where I can manually get the captivatemtd CWM? and how do I install it?

kataishin said:
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Click to expand...
Click to collapse
I can't flash cm7 either

movielover76 said:
Ok, everything I see says I should flash from a captivatemtd recovery, but when I install Rom manager and select captivatemtd, it says their are no offical recoveries for it, I'm currently running cognition froyo 2.2 with froyo bootloaders
Does anyone know where I can manually get the captivatemtd CWM? and how do I install it?
Click to expand...
Click to collapse
I'll go over my method of installing(I've had ZERO issues flashing from/to any ROM)
1. I FTS/MC using Odin 1 Click. My phone build is 1008
2. Root with 1 click root(I have to do steps 2 and 3 because I do not have 3 button recovery)
3. Sideload and install ROM Manager(Rom manager, and CWM update.zip are in the Sideload zip that's attached)
4. Copy CWM Update.zip and ROM to device. Reboot and install CWM
5. Reboot into recovery and install ROM
Odin 1 Click(If you can use it)
http://dl.dropbox.com/u/12100225/Odin I897UCJF6-final-OCD-REV0.zip
Root 1 Click
http://dl.dropbox.com/u/12100225/Root.zip
Sideload Wonder Machine and ROM Manager
http://dl.dropbox.com/u/12100225/Sideloading.zip
Edit** What is the build number of your phone?

Here's what you need
Just download this rom
http://download.cyanogenmod.com/get/cm_captivatemtd_full-181.zip
And then watch this video!
http://www.youtube.com/watch?v=iBPu-GqM9RE
Flash CM7 using odin
then flash ICS using clockwork mod using the instructions I gave you before.
That's the easiest way I found to do it and that's how I went from stock rom to CM7 rom and then finally to ICS

kataishin said:
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Click to expand...
Click to collapse
Tried this to the letter still doesn't work, could it be because of rom manager not finding a recovery for captivatemtd, some pages say I need that recovery but it isn't available in rom manager.

Finnally
Finnally got CM7 installed the problem was I had to do the three button boot into recovery twice, the first time updates clockworkmod to version 5.x
Now to try ICS again, wish me luck

Thanks
Thanks for all the suggestions, the tip in the video about flashing the speedmod kernel did help I think, I've successfully flashed
teamhacksung's ICS Port for Captivate (BUILD 9) again.

A couple notes here:
1 when your flashing cm7 from cwm( NOT 3e RECOVERY THOUGH) you need to flash the. Zip file, then reboot system, IT WILL PROBABLY BOOT LOOP, three button back to recovery and flash again, then while in recovery still flash gapps. Reboot and it will install fine. You should ONLY need to do the two time flash the first time going to cm7.
2. When you go to rom manager and choose manual flash overide from hitting the menu button you will get the unsupported recovery, DON'T WORRY about it and hit ok. Then another popup will come up and choose 3.x and it will work.
Sent From My KickAss ATT SGS2 SPORTING CM7

flashing back to froyo baseband

i want to flash back to the froyo baseband to flash the newline v3 rom but i can't get it done...
i treid the 2 diffrent options they give on the forum but these don't work for me.
does somebody know another way to get the froyo baseband??

Just flash one of the official froyo ROMs and it comes with the baseband, then root it, CWM it and install over the top
Its what I had to do when not being able to get just the baseband to flash

If you are flashing from GB back to froyo then you can't do it w/o first flashing to stock froyo via lgtool.
Step 1
http://forum.xda-developers.com/showthread.php?t=1244490
Dont bother with the cable since the standard cable which comes with O3D is fine.
Step 2
Root the phone and install CW
Step 3
Boot in recovery do all the wipes and install the acura v3 froyo...

i treid it like the link tells me but that doesn't work for me.

3dspeed said:
i treid it like the link tells me but that doesn't work for me.
Click to expand...
Click to collapse
What you need is:
-Download kdz v10x Rom (Latest one suffers from rebooting issue when setting wifi sleep policy to never).
- Flash it using adixstra tutorial:
http://forum.xda-developers.com/showthread.php?t=1287236
And do not forget to apply this tutorial in order to get it flashing:
http://forum.xda-developers.com/showthread.php?t=1473781
Note: If you got a bootloop after flashing back to froyo, just turn off the device, boot into recovery and wipe data.

You can download all official kdz files from here:
http://lg-phone-firmware.com/index.php?id_mod=2
Here is an easy guide for flashing:
http://forum.xda-developers.com/showthread.php?t=1186406

no boot with ics roms on tf101g

Hi. If i flash an ics Rom on my t 101g i cant boot... only the old Revolver is booting... and if i flash there other Kernel IT disabled wifi. A and Problem with recovery restart everytime in it.
some help?
Sorry for my englisch!

I've a same problem...
Morning everything was okay, I tested Codename 1.5.5.
E: TF101 32GB, SBKv2 - B70

try wiping everything, and flash back to stock...

I tried wipe all, but it didn't help me.
Back to stock is as a last possibility.

After flash to stock i must root again?
Ca you give mehr a Link for ww Version with 3g?
Or is it on asus hp?
Thx!

Yes, after back to stock you must add root and CWM.
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101G/#download
E: Problem solved!
I made back to stock, I downloaded 9_2_1_11 version for my TF, it flashed in CWM, reboot (wait on extracting blob file), full wipe - factory reset, boot to stock ROM > root (Viper) > flashed recovery > in recovery flashed EOS ROM and work for me

a bit lol for me....
i download and install the stock rom but im allready on the last, what make i wrong?

Download .zip package and extract second package "WW_epad-user-9.2.1.11.zip" from it on sdcard and flash in CWM. Wait several minutes on install and when install finish with succesful report so you can reboot. Over wait several minutes on flash blob file and then you can make factory reset.

Need some help flashing Clean Rom 5.1

I have downloaded CleanRom 5.1 from a long time ago, now the link is not up for that rom. The size is 598 mb.I have flashed this rom before but now I can't get it to flash. In recovery I have wiped, dalvic,cache, system, and factory. After I choose what to flash from Aroma it goes to flash a couple of seconds then goes to the other screen to finalize, but when going to reboot, I get "no OS , do you really want to reboot".
S-OFF
unlocked
on 2.20
Tried this with HBOOT 1.09 and now on HBOOT 1.14, I would redownload but the link is gone now , and I can't figure out how to get it to flash, luckily I do have a back up that works

Downgrade your recovery to twrp 2.3 bet you are using a 2.4 version
Sent from my HTC One X using Tapatalk 2

jerrycoffman45 said:
Downgrade your recovery to twrp 2.3 bet you are using a 2.4 version
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I had 2.4 downgraded to 2.3 but having troubles now. Seems Clean Rom 5.1 is the only one I have trouble with even on TWRP 2.3

Sorry maybe someone else will know what to do I am out of ideas
Sent from my HTC One X using Tapatalk 2

leesumm said:
I had 2.4 downgraded to 2.3 but having troubles now. Seems Clean Rom 5.1 is the only one I have trouble with even on TWRP 2.3
Click to expand...
Click to collapse
Don't know if you have the MD5: C8D3304C4120F5B0AEBE75BC6B4F733C But check that. If it doesnt match, lemme know and I think I have a copy of this rom to upload for you at home assuming Dev won't mind.
Also, after downgrading from twrp 2.4 to 2.3 did you do fastboot erase cache? Regardless I would recheck checksum twrp if you have the image saved or redownload and check checksum, reflash (fastboot flash recovery "recoveryname.img" (sans "") and then do fastboot erase cache.
Lemme know.

exad said:
Don't know if you have the MD5: C8D3304C4120F5B0AEBE75BC6B4F733C But check that. If it doesnt match, lemme know and I think I have a copy of this rom to upload for you at home assuming Dev won't mind.
Also, after downgrading from twrp 2.4 to 2.3 did you do fastboot erase cache? Regardless I would recheck checksum twrp if you have the image saved or redownload and check checksum, reflash (fastboot flash recovery "recoveryname.img" (sans "") and then do fastboot erase cache.
Lemme know.
Click to expand...
Click to collapse
NO. I don't have the md5 for that rom. I downloaded it some time ago and sitting idle in the folder on the PC. I was messing around in places that I shouldn't have been and somehow things got deleted. My backup of that rom I had flashed works fine. Its when I go to flash the rom from zip that I have a problem.

I am really scratching my head now!!!
The same rom, the same zip that I have been asking about that wouldn't flash, now flashes fine and installs. I was using TWRP 2.4.1 for a long time and was having a little problems with different things and trying to flash some add ons to the rom playing with it. Reading some of the posts I read some were having problems with TWRP above 2.3 so I downgraded the recovery,thats when I couldn't flash the zip I had of Clean Rom 5.1. So, for the fun of it, I upgraded back to TWRP 2.4.1 and tried to reflash the same zip package, everything works fine now it flashed and booted. Got me scratching my head ...

leesumm said:
The same rom, the same zip that I have been asking about that wouldn't flash, now flashes fine and installs. I was using TWRP 2.4.1 for a long time and was having a little problems with different things and trying to flash some add ons to the rom playing with it. Reading some of the posts I read some were having problems with TWRP above 2.3 so I downgraded the recovery,thats when I couldn't flash the zip I had of Clean Rom 5.1. So, for the fun of it, I upgraded back to TWRP 2.4.1 and tried to reflash the same zip package, everything works fine now it flashed and booted. Got me scratching my head ...
Click to expand...
Click to collapse
Makes sense to me, sounds like you didn't do fastboot erase cache after switching recoveries. When you flash a new recovery you need to do fastboot erase cache.