Develop Bugs

[Q]URGENT !!!!! downgrading failed

WHat i did was:
-restore 2.2 nandroid backup
-flashed 2.2 fixed sbf so i could keep downgradability...
Now when i tried to go back to 2.1 eclair version 2.21
-i flashed 2.21 blur full sbf
and now i have black screen as if downgrading wasn't possible...
What options do i have ?

NO HELP? am i the only one with this problem here?
ANother question i had if there's a way of downgrading kernel? because i've experimented this. On kernel 2.6.29, the multi touch works fine but on kernel 2.6.32, multi touch is buggy, way buggy...

I'm guessing your stuck on 3x roms. So your going to need to see if you can reflash the fixed rom and try downgrading again.
If not that fixed rom wasn't fixed.
Sent from my Defy, with XDA Premium

Jygar said:
If not that fixed rom wasn't fixed.
Click to expand...
Click to collapse
Thanks for THE reply...so now what i can do is flash full sbf (3.4.2.145) which is same version as my earliest fixed sbf, restore nand backup of 2.2 then flash the FIXED sbf CEE one (3.4.2.155) and then try downgrading? would this work?
EDIT: Walter79's sbf's are messed up..i used his fixed sbf version...didn't try CEE one tho

Did you find a solution to downgrading i to did the same thing.

errrm...
righto after reading that post again, i've had to change this :| I have had a similar problem myself, but i did manage to resolve it with 2 nights after work of swearing, redbull binges and many failed attempts :| I finally somehow managed to get Pays-ROM to load :| hope you get it sorted though

Im on a fixed sbf again..but my prob is to go back to 2.1
I hv restored 2.2 nand nd flashed 2.2 fixed cee rom..if i flash a full 2.1 sbf..wud it work?

From what I know, if you have flashed 2.51 or higher full sbf (non fixed) then you cannot go back down to 2.21.
However if you have flashed 2.51 or higher with the system and CDT code groups removed (i.e. fixed SBF), then you should be able to go back to 2.21 just by flashing the complete 2.21 sbf.
DO NOT flash a full sbf 3.4.2.145, because that will upgrade the CGs that prevent downgrade.

What if i flashed 3.4.2-145 (full sbf) and then restored 2.2 froyo nand and then flashed a 3.4.2-155 fixed SBF, now if i flash a full 2.1 sbf, would it work?

No, because once you flash any FULL sbf that is greater than 2.21 then you flash the parts of the ROM that are non-downgradeable. Once those partitons have been flashed then you cannot downgrade. That is why the FIXED sbf's should have those partitions removed.

For your information, the detailed investigation around these non-downgradeble code groups is in this thread:
http://forum.xda-developers.com/showthread.php?t=945035
Some very useful information in there, and they summarise that once you flash Version 2 Code Groups, you cannot go back down to Version 1 code groups.

kashavsehra said:
No, because once you flash any FULL sbf that is greater than 2.21 then you flash the parts of the ROM that are non-downgradeable. Once those partitons have been flashed then you cannot downgrade. That is why the FIXED sbf's should have those partitions removed.
Click to expand...
Click to collapse
Well, i did flash a fixed version of 2.2 sbf and then flashed 2.1 full sbf but that didn't work out and the screen went black...so i flashed 3.4.2-145 full so that atleast i could use my phone but it was a deblur version and i have no contacts...can't import contacts from sim either...so i just want to go back to 2.1 and then give my phone back to motorola...isn't there ANY way to remove those CG's off the rom you're on at the moment`?

as far as anyone here understands it, NO Can't be done

Defy to Bravo
Has anyone tried and tested the Defy ROMS (such as PaYs or JBoogie's) on the Motorola Bravo (MB520)?
I would really like to take the plunge, but I've read Bravo users have bricked trying Defy ROMS?

danxj3 said:
Has anyone tried and tested the Defy ROMS (such as PaYs or JBoogie's) on the Motorola Bravo (MB520)?
I would really like to take the plunge, but I've read Bravo users have bricked trying Defy ROMS?
Click to expand...
Click to collapse
Just dumb to try one phone's firmware on anothers. It is just like installing mac software onto windows

I believe the only to go back to 2.1 is to restore the nandroid backup of 2.1.
there are a few thread posting stock nandroid backup of 2.1 (except it's already rooted).
you have to flash also bootonly sbf based on the same version.
then you can manually remove superuser.apk and su manually using adb shell.

polaris441 said:
I believe the only to go back to 2.1 is to restore the nandroid backup of 2.1.
there are a few thread posting stock nandroid backup of 2.1 (except it's already rooted).
you have to flash also bootonly sbf based on the same version.
then you can manually remove superuser.apk and su manually using adb shell.
Click to expand...
Click to collapse
Did someone acutally used this method and was succesful? I have downloaded a stock nandroid and the related bootonly sbf. Furthermore i have the related full sbf file if i need it.
So you think its probably possible to put the nandroid on the sdcard, go to clockwork, wipe everything and then restore the nandroid. Afterwards i think it would be the best to remove the battery, put it back in and boot directly into the bootloader and from there flash the bootonly via rsdlite.
Im kind of scared to give it a try. What if something goes wrong? Can i go back to my last 3.4.x ROM?
Cu

Jokerchris2000 said:
Did someone acutally used this method and was succesful? I have downloaded a stock nandroid and the related bootonly sbf. Furthermore i have the related full sbf file if i need it.
So you think its probably possible to put the nandroid on the sdcard, go to clockwork, wipe everything and then restore the nandroid. Afterwards i think it would be the best to remove the battery, put it back in and boot directly into the bootloader and from there flash the bootonly via rsdlite.
Im kind of scared to give it a try. What if something goes wrong? Can i go back to my last 3.4.x ROM?
Cu
Click to expand...
Click to collapse
I've done this on 3.4.2.xxx version (full sbf flashed). What happens is that it goes to M screen and then reboot, then goes to M screen and reboots...this goes on and on but i haven't tried flashing bootonly. I don't know what can happen if i flash that but what i know is that you atleast DONT get a black screen, it does show M logo...

kashavsehra said:
From what I know, if you have flashed 2.51 or higher full sbf (non fixed) then you cannot go back down to 2.21.
However if you have flashed 2.51 or higher with the system and CDT code groups removed (i.e. fixed SBF), then you should be able to go back to 2.21 just by flashing the complete 2.21 sbf.
DO NOT flash a full sbf 3.4.2.145, because that will upgrade the CGs that prevent downgrade.
Click to expand...
Click to collapse
my phone came with 2.54 preinstalled i understand i cant get to 2.21. the question is, if i flash full sbf (not fixed) of 3.4.2 , can i get back to my stock 2.54?
thanks!
edit:
after some research, i will lose downgrade-ability. smg versions of 3.4.2 are +1 higher than my 2.54

[Q] Downgrade to 2.59

I am on JRDNEM_U3_2.59.0 INDIA
Is it possible to come on Eclair JRDNEM_U3_2.59.0 after direct flashing any froyo SBF?
So far I have flashed my Defy with fixed SBF method, afraid of loosing warranty if not able to downgrade.
Dont even know the version of cg31.smg and cg39.smg in U3_2.59.0.
Thanks...

downgrade back...
If you have flashed a fixed sbf, then yes...

depends on the sbf file. some full SBFs are downgradable
but to make sure, use a Nandroid backup & a fixed sbf

[Q] Downgrade to original

I flashed froyo on my new defy 2.51 to Pays-ROM Defy v5.0 which is based on 3.4.3-11. It says my kernel version is 2.6.32.9.
I want to downgrade my phone to the original stock rom, to get my warranty back. Should I just flash it to the 2.51 eclair stock with rsd lite? or will that brick my phone?

It depends on whether you flashed a fixed SBF or not. If you flashed a fixed SBF of Android 2.2 (3.4.3-11) than you can flash a full SBF of Android 2.1 to your phone (look for it at the forum) and your phone will be alright. If you flashed a full Android 2.2 (3.4.3-11) SBF than it's not possible to get back to your stock rom (Android 2.1).

There's something I'd like to know about this, even if you go back to 2.1 for warranty, can the warranty guys still know you modded it?

What is the difference between fixed and full sbf ? How do I get to know which one I have?
I followed the steps on this post -
[ROM] Pays-ROM Defy v5.1 Froyo with Ginger feeling
This is what i followed --- :s
README - Step by step flashing guide:
You can go to step 5 if you already flashed 3.4.3-11 SBF, rooted and installed clockwork recovery or have ROM v5.0 or higher.
Don't wipe after you flashed the SPF or the ROM. Also no wipe is needed before or after a ROM update. But wipe before flashing a new SBF!
1.) Wipe your phone in recovery mode
2.) Flash 3.4.3-11 Motorola SBF with RSD Lite in bootloader mode
(The sbf is packed in a archive just extract it and then you get the sbf.)
3.) Enable ADB in the settings and root your device with SuperOneClickRoot for Froyo. Then do a reboot.
4.) Disable ADB and install clockwork recovery image
5.) Put the ROM.zip to your SD Root and boot into clockwork recovery
6.) Flash the ZIP + reboot and enjoy

@LeoD7K
I don't believe they can see which rom you've flashed in the past so you'll be save if you revert to your old rom. (Someone on this forum told me that)
@pragund
I'm not sure whether this is a fixed SBF, you should ask the developer who started the thread. Another way to find out whether it's fixed is to check the file size. A fixed SBF is very small, around 15-40 MB whereas a full SBF is around 300 MB. So if you still have the SBF file you flashed you can check the file size. Also you have to make sure you've never flashed another full SBF before. So if this was your only upgrade and it's a fixed SBF you can downgrade back to Android 2.1.

my sbf file size was 360mb!
Is there any other way to get to an original stock rom? so as to get warranty?

Well the only option left is to check whether your carrier has released an official 2.2 update. If that's the case you could update to that and still claim your warranty as it's an official rom. Every carrier should release an official Android 2.2 rom at some time so if it's not released by your carrier yet it should be just a matter of time. Aside from that there are no other options to get your warranty back. But also I'm not sure if you can update from one Android 2.2 to another Android 2.2.

I bought it outright unlocked in india ... do I get a direct update from motorola?

[Q] So many questions!

I have a Nexus S and I'm attempting to Root/Install ROMs on a Defy. I must admit terms like SBF, 2ndInit, SuperOneClick were new to me. After almost 6 hours of reading and searching, and getting stuck at boot for a long time, I've successfully installed Pays 2.2 ROM on my phone, coming from 2.1 Eclair. But, I still haven't wrapped my head around the proper procedure for flashing ROMs. Can someone please answer the following questions?
1 - What is an SBF? How is it different from a Nandroid?
2 - Why does one have to flash an SBF as well as a ROM? This is confusing! Why do I flash a 2.2 Froyo SBF to install a 2.3.4 ROM? And in some cases why the Froyo SBF AFTER the Gingerbread ROM?
3 - If I want to switch between 2.3.3/4 ROMs (eg: MIUI and CM7) is it sufficient to just restore their Nandroids?
4 - I see a lot of talk about Downgrading. Why would one want to downgrade to 2.1, or even stay at 2.2 for that matter?
5 - How would one switch from a 2.3.4 ROM to a 2.2 ROM? Nandroid? Or SBF or both?
On the Nexus S, we just flash a custom recovery that stays put. Then we're free to restore Nandroids and things as we please. All this SBF stuff is a little beyond me. Any answers to these questions would be really appreaciated. Thanks!

thanx i wanted to ask the same....

What the guys above me said, good to see someone asking questions some of us dare'nt ask for fear of put downs or other negative replies.
Seriously asn thx for replying, about 6 hours earlier nearly wrote your reply word for word but didn't as didn't want to be labeled a stupid noob. FYI I've ROMed 4 winmob devices and a zte blade so im not a stupid noob

Here's what I don't understand (sorry for the noob question and the long post):
Here's what I did so far:
Started with stock US Froyo (Version.34.4.9.MB525.T-Mobile.en.US, Build Number: 3.4.2-107_JDN-9)
Rooted and installed ClockworkMod Recovery v2.5.1.8
Took a nandroid backup
Installed CM7 (as per FAQ):
flashed JRDNEM_U3_3.4.2_177-005_NORDIC
rooted using SuperOneClickv1.9.5-ShortFuse
installed 2ndInit SndInitDefy_1.4_2.apk
installed CM7 RC1v2 using Recovery - Custom Recovery
installed cm7-110715-1018-NIGHTLY by booting 2ndInit -> Recovery -> Stable recovery
This was actually my second install of CM7.
During my first install I did not flash Nordic and installed directly on top of Stock US 2.2.1 Froyo.
Then I only installed RC1v2 (no nightly) and the camcorder had very laggy recording.
So I decided to do it again by first flashing Nordic.
I did this by restoring my nandroid backup and it worked fine without flashing any fixed SBF.
Now I believe that the nightly probably fixed the camera and it wasn't because my I didn't flash Nordic first.
So my questions are:
* To downgrade, do I really need to apply a fixed SBF on top of my nandroid or is this only necessary if I started off on Eclair (and not if I started on Froyo) ?
The CM7 FAQ state that in order to downgrade from CM7 a nandroid backup AND a fixed SBF is needed.
Why would I need a fixed SBF if I have a nandroid backup.
* Is it ok to install CM7 on top of Stock US 2.2.1 Froyo or is it better to flash Nordic or does it not make a differnce at all?
* What are the BOOT179 nightlies (e.g. cm7-110716-0105-BOOT179-Jordan) and do I need to apply it if I'm already on RC1v2 and want to apply the latest nightly build?

Let's start with the big one, Defy has a locked bootloader, hence there's not an easy way to flash a custom rom, unfortunately no flash & go here. The bootloader check for signed moto products at a very low level, it's something like built-in in the hardware.
1) SBF is usually a stock ROM provided by Motorola, i say "usually" because you will find many leaked versions around. It is different from a nandroid backup, you cannot restore a SBF in the way you restore a nandroid. A SBF MUST be flashed with RSD Lite, which is an apposite tool delivered by Motorola.
2) Depending on the custom ROM you're going to install, you have to flash the appropriate SBF. For example, if you try to install a custom ROM based on froyo 2.2.2 to a phone which runs eclair you'll just get stuck at startup. Actually, before the Quarx work (GB) all the custom roms here were just customizations of SBFs. Now with the 2nd init stuff we've new opportunities but, until the bootloader is locked, we'll need the official SBFs as base for any custom rom, otherwise no way to bypass the check at startup.
3) It depends on the bootloader version. Your ROM should have the same bl version of the nandroid backup-ed one.
4) Actually there are two reasons ppl talk about downgrading. First, in case of the phone needs repairs you should reinstall the original ROM in order to avoid to void your warranty. Second, many custom ROM, included GB versions, are still buggy. Some ppl like them much, other ppl prefer going back to slower but more stable official ROMs.
5) I cant tell you for sure since i've never tried any GB so far, but, with RDS Lite + SBF you should be able to revert back.
All this, as far as i know, and i know not much..
EDIT:
I forgot something important, use fixed SBF + nandroids to preserve your downgradability. The way is 1) apply a nandroid 2) flash the fixed SBF with RDS Lite 3) apply a custom rom. If you don't and go directly with RDS Lite and the whole SBF then downgradability will be lost.

Thank you very much! I wish there was an FAQ for noobs. As per your edit, I'm pretty sure I've lost downgradability. Not too worried about it...yet.
But, you've helped a lot. I think I get it now. Thanks again!

[Q] Help! Defy cannot get past blur set up.

After trying to reinstall the factory sbf on my (us t-mobile) defy I cannot get past the initial blur activation. I have tried to skip the set up but it just takes me right back to the first page. Worse yet when I try to activate blur it will freeze up and requires reboot. I have re-flashed the sbf and even tried a few others with the same result. Any idea what is happening here and how to fix it?
JORDN_U3_6.19.0 - no boot
JORDN_U3_6.36.0 - above problem
3.4.2-107 - wont flash
3.4.2-164 - above problem

message me with email address so i can send u right sbf

pmp326 said:
message me with email address so i can send u right sbf
Click to expand...
Click to collapse
What SBF do you have in mind?
I also tried to restore my stock US 2.2.1 after installing CM7 - just to see if it works.
So I restored my 2.2.1 nandroid and the applied this sbf: p3_jordan_umts_jordan-user-2.2.1-3.4.2-107_JDN-4-000000-release-keys-signed-T-Mobile-US.sbf
It worked, however, this will not bring you back to the official 2.2.1 US Froyo because above SBF is an earlier beta version and you will end up with 34.4.4.MB525.T-Mobile.en.US_3.4.2-107_JDN-4.
The official version is 34.4.9.MB525.T-Mobile.en.US_3.4.2-107_JDN-9.

you have to restore through nandroid from 2.2.1 test keys

you did make a backup before you went flashing right?

pmp326 said:
you did make a backup before you went flashing right?
Click to expand...
Click to collapse
Not sure if this question is directed at me but yes, I made a nandroid backup of my stock US 2.2.1 before installing CM7 (nordic + rc1v2 + nightlies).
Then I restored my nandroid (leaving the kernel version at the CEE one from CM7) and applied the p3_jordan_umts_jordan-user-2.2.1-3.4.2-107_JDN-4-000000-release-keys-signed-T-Mobile-US.sbf.
Then you end up with 34.4.4.MB525.T-Mobile.en.US_3.4.2-107_JDN-4, which is not the official US Froyo.
I don't really care about that (I was just testing it out) but if somebody needs to go back to stock US Froyo in order for example to send it to warranty this will not work.

you have to root 221 install clockwork recovery then restore original backup

that's what i did - but the restore will NOT restore the 2.2.1 kernel

there is also a 2.2.1 boot only sbf which is the kernal

I assume you mean T-mobile froyo bootonly.sbf, which is from Jan 26 2011. I haven't applied it but I'm quite sure that's also not the official 2.2.1 version.
My point is that unless there's a different and newer 2.2.1 SBF (other than 2.2.1-3.4.2-107_JDN-4) you will not be able to go back to stock official US 2.2.1 froyo and claim warranty.