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] 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!

Earpice don't work after update to cm7 rc1.5

Hi, before 4 days i update cm7 to rc1.5 after that my earpiece stop working, after reboot it's starting to work but just for a day and than stop work again, how to fix this please help me!
Please forgive me for my bad language

are you not aware of the famous defy earpiece problem? read here:
https://supportforums.motorola.com/thread/41152
it's just a coincident that your earpiece has failed after you flashed rc1.5. i'm sure it has nothing to do with it.
i'm sorry but it's time for you to flash back to stock rom and send your phone in for repair.

No it's not from the phone I'm sure about that because i was using cm7 rc1 and couple nightly building and with them everything worked just fine. And i never have issues with earpiece before!

I have nandroid back up, can i restore the back up or first i have to flash to original sbf which is 3.4.2-179-2 CEE

you can restore it. But if you want to send it to repair center, just flash the sbf as you can't have it rooted and wipe everything in stock (Private data etc). Don't forget to do backup first...

Sorry i don't understand, what sbf to flash fixed or full ? And what you mean to back up first? to make new nandroid backup or to restore the exist one ?
Please some body to help me i just wanna back to froyo and send the phone to repair if the problem still exist, i'm not sure what sbf i have to flash full sbf or fixed ?

No, with backup I mean of apps etc. Just flash the sbf that is stock on your region. I'm guessing CEE. You can restore nand, but then it is still rooted and probably a bit tweaked and if the problem then presists, you will still have to flash the sbf. Fixed sbf's are only if the official released software is lower than the one you wan't to flash like 2.3.3 defy+ rom or froyo if your country doesn't have an froyo update.

Thank you very much, you don't know how much you help me.

labsin said:
You can restore nand, but then it is still rooted and probably a bit tweaked and if the problem then presists, you will still have to flash the sbf.
Click to expand...
Click to collapse
sorry labsin, i'm still a bit of a noob in the rooting/custom rom subjects. i'm a little confused by your statement above. you were implying that flashing a full sbf would unroot the phone? i was of the understanding that you have to unroot it using superoneclick, full sbf or or otherwise?
besides if you did a nandroid backup of the original stock rom, why would it be tweaked?

Same thing happened with my defy.
It was the speaker...maybe you'll have better luck, but it's an easy fix
Sent from my MB525 using Tapatalk

[Q] serval question for JORDN_U3_97.21.51

Well... it's a long story.
I bought my China Retail Defy ME525 this May, accidentally flashed 3.4.2-155 deblur as stock rom. Two day before I accidentally flashed JORDN_U3_97.21.51 (again ).
Now I stuck there and unable to flash any other roms in RSDlite. I'm trying to update it to froyo and later restore my CM7 backup.
Here's my questions:
According to here, it is possible to get an OTA update. But did anyone actually make that?
Would ME525 be unable to get T-Mobile update due to its IMEI?
(This is a silly one, however I really don't find the answer). How could it be possible to install an nandroid backup after flashing a fixed sbf? my led never turn blue after I flashed the sbf. Cannot enter bootmenu PS: The fixed sbf is based on 3.4.2-107 TMobile US full sbf)
Is it possible to make up a update.zip that acts as installing nandroid backup?
Would it be the same to install a nandroid backup first and later flash fixed sbf?

you install the nandroid backup first and then flash the sbf...

JORDN_U3_97.21.51 is an eclair sbf which contains CG39.smg and CG31.smg ver=5. You can no longer flash ANY froyo sbf. In fact the only sbf you can flash now are 2.3.4 and 2.3.6 sbf and of course JORDN_U3_97.21.51. 2.3.6 sbf is ver=6 and has no know downgrade possibility. Follow this guide to get back to froyo http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143
Keep in mind that this is a "dirty" method of getting back to froyo and you are ALWAYS stuck on ver=5. What that means is that even after getting to froyo using this guide you are NOT free to flash any sbf you like. You can however, use this guide to get to froyo and install cm7 from there

[Q] defy bricked!

hi all,
i flashed my defy (red lense) with defy+ sbf file :
DEFYPLUS_U3_4.5.1-134_DFP-125_GR_SIGN_SIGNED_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P019_A020_HWp3_WIG148090_Service1FF
before this i used miui rom but then i just want to try with cyanogenmod9. so i flash the above sbf. there is no problems with the flashing. after root, when i want to install cm9 rom, the kernel & gapps in cwm, my phone bricked. i figured maybe i flash the wrong sbf. then i try to flash diferent sbf but still bricked. i even try to flash eclair version but still did't solve my problem
i've no choice to flash back with defy+ sbf. so far my phone can only turn on with this sbf file. what should i do now? i want to use cm9 rom.

You didn't have to flash this sbf -.-'. You could have went for a nand backup if you wanted that rom or just flash the kernel if you wanted defy+ CM rom.
Ok to go from here, flash this sbf again. Then root (if you get bootloop, wipe data from stock recovery). Then if you want CM9, you just have to flash the defy+ cm9 zip and the gapps. You can flash the defy+ kernel but you don't have to. And wipe before you flash the rom.
From now on you can only flash bl6 rom's (or bl7 but then you can't flash bl6 rom's anymore). If you want to go to froyo kernel again, there is an bl6 froyo sbf. You can find it in the dev part.

thanks labsin,
i tried your method & every single step but when i try to flash the cm9 rom, i got :
-- installing: sdcard:cm9-nightly-120330-defy+.zip
finding update package...
opening update package...
installing update...
E:can't make /tmp/update_binary
installation aborted.

thank god!
i manage to flash froyo now. i use chinese sbf, JDGC_U6_2.13.0 China Unicom, i found here :
http://forum.xda-developers.com/showthread.php?t=1486731
amazing! i manage to downgrade from 2.3.6 to 2.2.2.

i have another problem. after flashing the china unicom sbf, i flash wiui rom. it happen to have a lot of bugs. but i figured that the wiui moderator suggested to flash 2.2 cee. im thinking of giving it a try. but every time i flash 2.2 cee (rsd lite), i get bricked again.
any idea?

You can only flash the Chinese froyo our gb roms as your now on bl6 and froyo is 4. The Chinese one is an exception. Flash the Chinese again, root, instal 2nt init and flash the froyo kernel from epsy's site (check CM9 threat) and then flash your froyo based custom ROM. With wiui your best of with the gingerbread ROM. The merged gingerbread with some ics could be a bit bugy.
Edit:
From here http://defy.wdscript.fr/kernel/
Sent from my MB525 using XDA

thanks labsin,
you have help me a lot. thanks again