I am currently on Froyo Kernel 2.6.32.9, using MIUI ROM from Will5.
What I would like to achieve:
1. I want to try the Stock UK GB ROM (with Kernel that fix the multitouch thing) for some time, play with the motoblur stuff
2. I would like to still be able to install custom ROM (CM7/9 and MIUI) after I play enough with stock ROM
What I think I understand:
1. Only CH GB Kernel that fix the multitouch issue, so I would have to flash this kernel / ROM.
2. CH GB doesn't have GApps & MotoBlur, so I would need UK GB ROM to have this
3. After flashing CH GB, I can reflash Asia WWE Froyo to get back to Froyo
4. After flashing UK GB, I cant get back to either Froyo or CH GB
5. CM7 & 9 Can use CH GB Kernel, while MIUI must use Froyo only
So the question is:
1. If I install CH GB, can I restore santiemanuel's NANDROID backup (http://forum.xda-developers.com/showpost.php?p=19926327&postcount=408) onto it? will this give me a UK GB Stock ROM with CH GB Kernel?
2. If the answer to #1 is no, then is there any way to achive #1?
3. Anyone know if #1 step is downgradeable to Froyo? (I would only need this when I want MIUI back)
thx
I think the answer to your question should be yes. Though don't blame me if it isn't possible to downgrade or you brick your phone
The steps to do so might be:
1. Install CH GB from sbf using RSDLite.
2. Flash UK GB nandroid back up from santiemanuel.
3. Extract the attached CH GB kernel sbf using 7-zip and flash it using RSDLite.
Please do a complete fresh install if you wanna give it a try.
Though it seems harmless, do it at your own risk.
OK, I got issue. I am now stuck with CH GB, because I cant restore UK GB's Nandroid as I am using bootmenu 0.8.6 (and I think the Nandroid made from bootmenu 1.0.4 based on the file name). I have tried the bootmenu 1.0.5 twice, but only to have bootloop and re-doing from scratch (from flashing sbf) both time.
Is there anyone can tell me how to use the bootmenu 1.0.5? I have installed it, then when I run and choose menu #1 then restart, I got bootloop. I dont know what each menu are for as I dont understand chinese.
The version of bootmenu should not matter. However the version of CWM can matter. So what you need to do probably is flash the CWM 5.x.x coz that might be the one with which the nandroid back up has been created.
You can find CWM 5.x.x somewhere in the forum I suppose or from Koush's website.
Sent from my MotoA953 using xda premium
sahilarora911 said:
The version of bootmenu should not matter. However the version of CWM can matter. So what you need to do probably is flash the CWM 5.x.x coz that might be the one with which the nandroid back up has been created.
You can find CWM 5.x.x somewhere in the forum I suppose or from Koush's website.
Sent from my MotoA953 using xda premium
Click to expand...
Click to collapse
thank you, I managed to restore the nandroid backup using bootmenu 0.8.6 available in Endless7's "How to instal cyanogen/miui" thread. I have the bootmenu's files with me all the time, I just didnt test it because I though need higher version of bootmenu >.<
now I have managed to get UK GB running with CH kernel (or so I think), play around for 2 days, doesnt like it
I am now using Tezet's CM7 for GB kernel, but I want to go back to MIUI (I love the fancy themes), so I tried to flash (yes using RSD lite) the Froyo sbf, but alas, RSD Lite doesnt recognize the UK Froyo sbf (http://and-developers.com/sbf:milestone2, 2.2.2 Froyo UK). When I choose this sbf, RSD Lite didnt show the file info like it supposed to, and I dont think this is related to non-downgradeable issue as I havent plug my phone to USB.
does anyone tried the UK 2.2.2 Froyo before? does it work?
or, when you guys need to return to Froyo sbf, which one do you choose?
you cant go back to froyo from official gingerbread, once you've updated your stuck
DreadPirateDan said:
you cant go back to froyo from official gingerbread, once you've updated your stuck
Click to expand...
Click to collapse
I didnt use UK GB sbf, I only use the chinese one which "should" be downgradeable.
But my issue now is RSD lite doesnt recognize the UK Froyo 2.2.2, it might because of broken download of mine or the file is broken to begin with. It will takes me half day minimum (and 1/3 of my monthly data plan) to download that 300MB+, so if anyone can let me know if the file is broken or not before hand, that would be very appreciated.
You can flash UK Froyo 2.2.2 over CH GB as far as I know. I even think I have tried this with success (I mean flashing UK Froyo 2.2.2 over CH GB retail, though it was quite a while ago).
If RSDLite does not recognize it, it could be some other issue. I don't know if it can be linked to a broken download. You can try to download it again or if you are sure that the download is okay, you can try a different computer. May be a friend's PC.
Good Luck!!
Edit: And before you do that, can you post a screenshot of your phone's 'About' menu, showing the CH kernel version.
Attached is screenshot of my phone. I have tried downloading the UK 2.2.2 froyo again, but still rsd cannot recognize. I tried with pc running windows 7 x86 and Laptop running windows 7 x64, both cannot
EDIT: i am using RSDLite 4.9, what version were you using when you're able to get RSD Lite to recognize that UK 2.2.2 Froyo Sahil?
Sent from my A953
Update:
I managed to download hongkong (AsiaRet 2.2.2 Froyo) (thx to a friend of mine), which can be recongnized by RSD lite. unfortunately, I cant flash it, error 0x0017 (iirc) and FAIL shown.
So i guess its not true that I can go back to Froyo if I only flashed CH GB using RSD Lite?
btw, a question not related to above matter: is there any app that can give me quick settings on status bar (like the one in CM or MIUI, when I pull the status bar down) that works on stock rom? unavailability of this feature is why I hate stock rom the most
That's pretty strange. I was quite sure that CH GB was downgradable. Even Tezet said so if I remember correctly. Did you do all wipes?? May be try the wipes from Moto recovery once i.e. if you can access it.
The architecture in GB was changed in some way which made it not support those notification toggles. There is a software by J4velin (a dev from xda itself) which does provide it but it isn't exactly the same thing. Search with that name in market.
Edit: And I was asking for the screenshot when you had UK 2.3.4 and CH GB kernel. You posted screenshot with CM I suppose. And you can try changing the RSDLite version, may be 5.6
Sent from my MotoA953 using xda premium
alexyie said:
Update:
I managed to download hongkong (AsiaRet 2.2.2 Froyo) (thx to a friend of mine), which can be recongnized by RSD lite. unfortunately, I cant flash it, error 0x0017 (iirc) and FAIL shown.
So i guess its not true that I can go back to Froyo if I only flashed CH GB using RSD Lite?
btw, a question not related to above matter: is there any app that can give me quick settings on status bar (like the one in CM or MIUI, when I pull the status bar down) that works on stock rom? unavailability of this feature is why I hate stock rom the most
Click to expand...
Click to collapse
please reboot your computer and phone and try again.this issue sometimes will happen.
sahilarora911 said:
That's pretty strange. I was quite sure that CH GB was downgradable. Even Tezet said so if I remember correctly. Did you do all wipes?? May be try the wipes from Moto recovery once i.e. if you can access it.
The architecture in GB was changed in some way which made it not support those notification toggles. There is a software by J4velin (a dev from xda itself) which does provide it but it isn't exactly the same thing. Search with that name in market.
Edit: And I was asking for the screenshot when you had UK 2.3.4 and CH GB kernel. You posted screenshot with CM I suppose. And you can try changing the RSDLite version, may be 5.6
Sent from my MotoA953 using xda premium
Click to expand...
Click to collapse
sorry for the mistaken screenshot
I'm back to UK GB with CH Kernel, but dont have screenshot app with me
System Version : 64.1.22.A953.Retail.en.GB
Model Number : MotoA953
Android version : 2.3.4
Baseband version : EPU93_U_00.60.00
Kernel version : 2.6.32.9-g5db7937
[email protected]#1
Build number : MILS2_U6_4.1-22
Are you a 100% sure that you can't downgrade?
Sent from my MotoA953 using xda premium
If by CH GB you are reffering to ROMS such as ms2ginger, blurless and argen2stone, then I can personally confirm that yes you can down grade back to froyo as I have done this several time.
The froyo version I use is Optus AU if it's of any relevance. (there's only one)
I always just use the latest version of RSD lite available, I've only ever ran into that error once. All I remember doing was rebooting and changing the USB slot I used.
Failing that you could try the Linux method of flashing since it's meant to save you when all else fails.
Edit: Just to add, if it were me in your shoes I'd be trying everything to avoid flashing official gingerbread, no way do I wanna get tied down to that beast D:
Even I'm almost 100% sure that CH GB is downgradeable. I have flashed it using RSDLite and then flashed back UK Froyo 2.2.2. (Almost since it was a long time ago )
sahilarora911 said:
Are you a 100% sure that you can't downgrade?
Sent from my MotoA953 using xda premium
Click to expand...
Click to collapse
Yes, with the above configuration (which I think is UK GB ROM with CH GB Kernel), using RSD Lite v.4.9 on Win7 32 Bit PC, I cannot revert back to Official AsiaRet 2.2.2 Froyo (I tried 4times, even right after clean instal using your first instruction on 2nd post).
However I cannot try the UK 2.2.2 Froyo as my RSD Lite cannot recognize it.
I will try to look for a newer / older version of RSD Lite and see if it can somehow recognize the UK sbf and try that again.
DreadPirateDan said:
If by CH GB you are reffering to ROMS such as ms2ginger, blurless and argen2stone, then I can personally confirm that yes you can down grade back to froyo as I have done this several time.
Click to expand...
Click to collapse
no, by CH GB Kernel I meant the SBF, by UK GB ROM I meant Nandroid backup (see post #1)
DreadPirateDan said:
Edit: Just to add, if it were me in your shoes I'd be trying everything to avoid flashing official gingerbread, no way do I wanna get tied down to that beast D:
Click to expand...
Click to collapse
dont blame me for wanting fix on mutitouch bugs
Yeah but what I'm saying is once you put the official one on there is no going back and that kernel has the multi-touch bug.
Now I get what you mean, you have taken the official gingerbread and just gotten the system backup from somewhere, restored that, and are then flashing the CH kernel in RSD lite. Correct?
I hope there isn't something in place that detects whats going on in the system backup then, you could potentially be stuck on it
No. Just read carefully what he written...
1) he flashed chinese GB SBF - which should be downgradeable (even I read that several times there)
2) the he restored nandroid backup (we can't write into /boot right? So he restored /system, but stayed in the Chinese GB kernel, which does not suffer from the multitouch bug...)
3) so he had UK GB /system with Chinese GB kernel (best kernel for M2 as far as I know)
But now he is unable to downgrade back - which is strange, because nandroid should not break e-fuse or something like this (it just restores files onto /system) and Chinese GB SBF should be downgradeable...
Do you get it now?
Related
I have asked to my telecoms operator the unsimlock code for my Defy, it said is yet unlocked but it is not
I have flash a full sbf 2.3.6. Before it was a 2.3.4.
Motorola can't give any code.
Is there a way to show to the operator that is still locked? Or a non paid way to have the unlock code (it's free with my operator)
I know that is a way to have a soft unock but only with cm7 or miui.
But i prefer a hard unlock for motorola rom.
THX.
Defy+ / 4.5.1-134_DFP-139 / 45.0.1390.MB526.Retail.en.FR
Bouygues telecom fr.
Always complain in a retail center. Take your defy, show him, let him call to services. Be persistent, not rude.
Indeed you could use a softunlock for CM7 or MIUI, don't know if you could for stock.
Thx for the answer. I have try this morning the softunlock with cm7 Nightly ( the only one cm7 i can install) but don't work . I think that the softunlock is only for 2.2.
Could you please try to install the nightly again and then flash the zip from my latest post on that threat?
Edit:
The zip
http://forum.xda-developers.com/attachment.php?attachmentid=908455&d=1329605492
Also you can try to write at russian forum - motofan.ru ( i'm not able to post link there...)
Just write IMEI and your model to them, probably you'll receive unlock code.
If you won't, only way is patch.
labsin said:
Could you please try to install the nightly again and then flash the zip from my latest post on that threat?
Click to expand...
Click to collapse
Thx. i have try but don't work anymore. I have flashed the cm7 zip, then, before reboot, flashed your zip. Trying to change baseband too but don't work.
Hellmanor said:
If you won't, only way is patch.
Click to expand...
Click to collapse
Yes, but for the moment not possible to find any patch for 2.3
Witch CM7 version are you using? Could you attach the files in defy_simlock_originals on your sdcard?
Could do the froyo for bl6 patch it from there and re install cm7
teamwork makes the dream work
labsin said:
Witch CM7 version are you using?
Click to expand...
Click to collapse
cm72-120127.0846-NIGHTLY-Defy+.zip
others don't work because of a 2.3.6 full sbf.
labsin said:
Could you attach the files in defy_simlock_originals on your sdcard?
Click to expand...
Click to collapse
Sorry but i don't understand what you want to say.
Could do the froyo for bl6 patch it from there and re install cm7
Click to expand...
Click to collapse
Do you mean to follow this way below? But i'm afraid this way don't work with Defy+?
Common Problems/Questions
Black Screens when booting up: (!) Tried to install a version of Android with a lower CG Version than the one currently on the phone.
Weird behavior after installing a Fixed SBF: Install a matching Nandroid backup with your SBF, and remember to clear Cache/Dalvik Cache using Recovery.
Installed full Gingerbread SBF and can’t go back to another rom: (!) aha! We have a issue here!, latest Stock Gingerbread full SBFs comes with a Version 5 of the CG, meaning until not long ago you were pretty much screwed. But wait, there is hope! A one kind Éclair has been found in China Defys that comes with Version 5 CG!.
How to fix it:
Download this SBF and Flash it
Root your Phone
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
Download and install this Nandroid Backup
Enter Recovery, Wipe Data/Cache
After wiping, turn off your phone
Turn it on and get immediately into Bootloader mode
Flash this Fixed SBF
Delete Data/Cache again and reboot.
You WONT be able to install full SBFs of any Éclair or Froyo since these Androids have lower CG Versions.
**NOTE*: I just rephrased the original post since it can be a bit confusing, it is linked as source below.
**NOTE2**: If you are using a non-Chinese defy, DO NOT USE THE CAMERA FLASH while on the Chinese rom, it WILL kill your LED.
Source: ((Original post here))
How to Install CM7 after Installing a Full Gingerbread SBF: (!) Ok, first of all do all the steps above on "Installed full Gingerbread SBF and can’t go back to another rom"
Root your Defy (Using SuperOneClick 1.7 and not 1.9).
Install SystemRecovery from GoAPK. If you install 2nd init, you'll just get into a boot loop and have to start over.
Reboot to recovery. Do a factory wipe, then do the cache wipe.
Install CM7 .Zip and then gapps zip file. DO NOT wipe again, you'll just go back to 2.2.2 CEE (if you accidentally do this, you can pick up again from step 3).
profit!
Click to expand...
Click to collapse
Yes it works with Defy+ if you are on a bld6 rom (not for the bld7 roms)
My patch from a couple posts back makes a copy of the patched file on your sdcard in the folder defy_simlock_originals. Could you post them here?
Don't know if the module works with the gingerbread kernel. That's why it is a good idea to try to get CM7 with froyo kernel. It's also handy if you wan't to install other roms (WIUI ...)
But could you fist give those files? Maybe i've made a mistake again ^^.
Edit:
Sorry you don't have the right guide. That one is for bld5 downgrade.
Here is for bld6: http://forum.xda-developers.com/showthread.php?t=1486731
labsin said:
My patch from a couple posts back makes a copy of the patched file on your sdcard in the folder defy_simlock_originals.Could you post them here?
Click to expand...
Click to collapse
Again, thank you for your help and time
(I have put .txt for upload)
The file is similar to the normal defy one as far as I can tell that must have done it... So prob. faullt of different kernel. You could try to downgrade and use CM7 on froyo kernel.
labsin said:
The file is similar to the normal defy one as far as I can tell that must have done it... So prob. faullt of different kernel. You could try to downgrade and use CM7 on froyo kernel.
Click to expand...
Click to collapse
Ok i'll try tomorrow
labsin said:
The file is similar to the normal defy one as far as I can tell that must have done it... So prob. faullt of different kernel. You could try to downgrade and use CM7 on froyo kernel.
Click to expand...
Click to collapse
I have change the kernel with THIS METHOD
after, try with WIUI 2.2.17: no network; then with update-cm-7.1.0-11-Defy-signed: no network, even when changing baseband.
So, if all that i have made is right, maybe it's not fault of kernel.
Other difference between MB526 and MB525?
You get 'no network' all the time, even with the sim from the right provider, also without the patch?
I think you're the fist to try on a defy+. Maybe look to the Russian fora...
edit: And can you tell me what your Baseband version is? (in settings > about)
edit2: If it is EPU93_U_00.59.01 Try it after installing RC1.5 from here: http://www.defy-cm.net/jordan-cm7.1-RC/
labsin said:
You get 'no network' all the time, even with the sim from the right provider, also without the patch?
I think you're the fist to try on a defy+. Maybe look to the Russian fora...
edit: And can you tell me what your Baseband version is? (in settings > about)
edit2: If it is EPU93_U_00.59.01 Try it after installing RC1.5 from here: http://www.defy-cm.net/jordan-cm7.1-RC/
Click to expand...
Click to collapse
no network only with wrong provider: with the patch no code ask, but no network even with other baseband.
Yes it is EPU93_U_00.59.01 (cm7.2 working on defy+ as well)
with RC1.5 no boot after files install, stuck on google logo.
Now i have flash fix sbf to use 2.3.6 rom because of no battery problems and better battery life. So i'll wait and ask again to my operator.
Now baseband is EPU_U_00.60.03
Do you think if i'm able to put a official operator rom it will see that is no desimlocked? i don't have made backup of my official rom (newbie mistake ) so i have ask here if it's possible with this method.
Blocking by TI OMAP 3630
I have read this:
Blocking the Bootloader by TI OMAP 3630
Why and how is it locked Defy?
While Linux is Open Source Motorola keeps the Defy the locked bootloader. Why?
For commercial reasons of course: avoid too many warranty returns from sorcerer's apprentices who brické their phone, for example (although care is denied you still have to manage the folders!) But also the traders (who manage some of the guaranteed returns, but not that ... we shall see below).
So Motorola maintains bootoader of our favorite phone is not locked and ready to unlock the last views of Roma making the switch to SBF rootage and even more difficult. But the fact how this lock is it made?
Unlike other phones (other brands, but also other brand models *) easy to unlock, the Defy is equipped with a TI OMAP 3630 chip that manages its technology via "M-Shield technology 'in this block. So we did not do a software problem but rather a problem if one CPU is addressing this release.
This technology also manages the simlockage phone which also explains why the operators are far from favorable to the release of Defy.
No one arrived today to crack this lock: it should have the tool from Texas Instruments where he provided to authorized repairers to put the Motorola Defy mode "SE" (Systems Engineering) for this.
* These phones using Qualcomm chips or other, do not bénéfiecient techonologie the M-Shield and are much easier to unlock.
Click to expand...
Click to collapse
(Google trad) Or here in french
stucked at jrdan u97.21.51
I am new at this my defy went dead when tried to upgrade to 2.2 did not have backup. I searched the web and only jrdan u 97.21.51 will work and canot go back or change any more to any other roms. tried the rsd lite to flash diferent roms and nothing works. tried rom manager and 2ndinit recovery and nothing i get black screen. Is there anyway to get out of this? Please help
sion123 said:
I am new at this my defy went dead when tried to upgrade to 2.2 did not have backup. I searched the web and only jrdan u 97.21.51 will work and canot go back or change any more to any other roms. tried the rsd lite to flash diferent roms and nothing works. tried rom manager and 2ndinit recovery and nothing i get black screen. Is there anyway to get out of this? Please help
Click to expand...
Click to collapse
Wrong thread i think.
Have you try a wipe cache and data in stock recovery before rsdlite? see here how to do with Froyo
Sorry to ask a question that im sure has been answered before, also for the bad heading clicked post to early. Ive spent the last day tring to find the answer. (well most of it trying to get the right sbf to get the phone back from a 2ndinit gone wrong)
I found the right sbf in this thread and used the 2ndinit 1.7 in here and it has worked.
http://forum.xda-developers.com/showthread.php?t=1498560
I can get into the bootloader, i tried the gb ones from here http://forum.xda-developers.com/showthread.php?t=1432100 but it doesnt work, just goes back to the stock bootloader. I used RSDlite to go back to stock. Now im wondering is there any thing im not doing right with these programs?
My phone details are:
System Version
45.0.1321.MB526.AsiaRetail.en.03
Android Version
2.3.6
Kernal Version
2.6.32.9-gbdd614e
[email protected]#1
Build Number
4.5.1-134_DFP-1321
It also said it was a group 35 when i was flashed the SBF to it
.What can i put on this phone? I only just bought it as a replacement for my last defy (non plus) which was running cm7. I actually lost it in a gutter and found it 2 days later in a drain using "planb", sadly it had been run over and the screen and case were damaged but thats another story.
Thanks.
I flashed the same sbf that you used and have installed 2nd-init 2.0 successfully.
does that answer your question?
I am now using MS2ginger 3.0 installed via NANDROID back up and multiboot is not working too well on this ROM yet.
But earlier on my stuck ROM I had installed 2nd init and dual booted CM9.
I used this guide:
http://blog.s0ulless.net/?p=2324
shrek8421 said:
I flashed the same sbf that you used and have installed 2nd-init 2.0 successfully.
does that answer your question?
I am now using MS2ginger 3.0 installed via NANDROID back up and multiboot is not working too well on this ROM yet.
But earlier on my stuck ROM I had installed 2nd init and dual booted CM9.
I used this guide:
Thanks, ill give this a try.
Which cm9 did you use? i tried the quarkx one and couldnt get it to work.
Click to expand...
Click to collapse
I followed that guide, cant get the cm9 to boot. So im using the stock rom, i like the ability to dual boot though.
I'll try for the miui now. pokemon edition sounds good.
my defy was flashed with defy+ sbf with kernel version 2.6.32.9-ge281b6e. i hate it cause my battery wont work i need to use desktop charger since battery cant be recognize by the phone and the status is "?". also camera is not working.
i tried to flashed it with different sbf's found in this forum but none of it work! after flash phone wont boot unlike when you flash it with my current firmware.
i want at least to have my battery back to normal also camera if possible. i tried flashing it with other defy rom but i always got stuck. it seems that ICS was installed but the phone wont load it.
is there anyway to get back to my original firmware? or any upgrades that can fix this. please help.
Reply!
Hey there!
Before you do anything, you gotta root your phone. Then install 2ndint to get recovery mode menu. Only from there can you successfully flash roms and get it to work.
i have the same prob.
i can flash any rom for defy+
my phone is defy green.
i flash dfp 4.5.1-231 (bootloader 7)
my battery and camra not work.
any solution ?
Help
The bootloader is locked !!!
Hi ...
Is almost impossible to downgrade from 2.3.6 to 2.2.
Motorola Defy with green lens work just with 2.2. With "update" the camera will NOT work more and until now is not possible to downgrade !!!
All this, because Motorola don't want to unlock the bootloaders. I personally I have this problem and now am nervous on Motorola...
Most of HTC's and Samsung's have unlocked bootloaders. In this conditions, I wil not buy more Motorola.
gorillaz07 said:
my defy was flashed with defy+ sbf with kernel version 2.6.32.9-ge281b6e. i hate it cause my battery wont work i need to use desktop charger since battery cant be recognize by the phone and the status is "?". also camera is not working.
<snipped>
is there anyway to get back to my original firmware? or any upgrades that can fix this. please help.
Click to expand...
Click to collapse
If you want any help, we need to know your build number (not kernel). We can then find out what bootloader version you have (6 or 7). If you are on bootloader6 you can downgrade to froyo with a workaround, but on bootloader7, you're stuck.
Sent from my MB526 using Tapatalk 2
im on bootloader 9 i think
Root then install a rom..it's gonna work fine
Sent from my MB526 using Tapatalk 2
gorillaz07 said:
im on bootloader 9 i think
Click to expand...
Click to collapse
You're not on bootloader 9.10. That's not what we're talking about. If you find your build number under system settings -> about phone, we'll try to find out what firmware you flashed to find out what "e-fuse level" you're on. Or just give us a link to the sbf you have flashed.
pjgowtham said:
Root then install a rom..it's gonna work fine
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
No, we're talking about kernels here. If he is a green lens user on 2.3.6 kernel his camera will not work. He needs to downgrade to froyo. This is only possible on bl6. He can't flash a froyo kernel over bl6 or bl7 without flashing a special sbf.
Ya we can't downgrade..it's not possible..but that special sbf s not there too..an i rite?
Sent from my MB526 using Tapatalk 2
i flash dfp 4.5.1-231 on green lens (bootloader 7)
my battery and camra not work.
any sbf for downgrade to froyo ?
jalal-jap said:
i flash dfp 4.5.1-231 on green lens (bootloader 7)
my battery and camra not work.
any sbf for downgrade to froyo ?
Click to expand...
Click to collapse
Nope, sorry. No going back from there
theres rooting for bl7s i think...so the only solution would be using custom roms
Sent from my MB526 using Tapatalk 2
He can root, he can flash custom ROM's, but the only kernel he can use is the GB kernel, so camera won't work (he has green-lensed camera) and if he tries to flash a Froyo kernel, he will end up with a BL error.
Oh..i didn't know that...thanks auris...that's because I'm safe on Froyo and i haven't tried bl7 in practical..
Sent from my MB526 using Tapatalk 2
I just will my battery back and charge.
yes im on bootloader 9.10 no hopes then to downgrade?
gorillaz07 said:
yes im on bootloader 9.10 no hopes then to downgrade?
Click to expand...
Click to collapse
Bootloader 9.10 is not the same as the bootloader version, my friend (yes, it is confusing). If you de-pack an sbf , you'll find a lot of images for different partitions of your phone. The images are all called CG__.smg where __ is a number, e.g. CG31.smg or CG39.smg. Most of these images are signed by motorola with a special version number (e.g. 6 or 7 on defy+ roms).
Our TI Omap processor has an e-fuse built into it which is some sort of a flash counter. It doesn't count how many times you flash, but the level of the CG__.smg you have flashed onto your device. If you flash an sbf with a CG31 (the bootloader) on version 7, you'll never be able to flash a CG31 lower than 7. Motorola increases this number for every update they make, to ensure that a user always uses the latest motorola software. This means it is impossible for let's say a defy+ user on 2.3.6 to downgrade to 2.3.5.
everybody has bootloader 9.10 (EDIT: Most do, but I've seen 90.73 and some others as well), but it has been re-signed and made only to accept the newest kernels, so your green lens is stuck without camera. Only the latest Motorola sbfs are bootloader7 (as of june 2012)
yeah i figure that our cause in flashing you will see codes and code 39 takes time i guess we cant help but wait, thanks guys if theres any solution pop out hope someone will keep us up to date. thanks!!!
fiskenigaten said:
Bootloader 9.10 is not the same as the bootloader version, my friend (yes, it is confusing). If you de-pack an sbf , you'll find a lot of images for different partitions of your phone. The images are all called CG__.smg where __ is a number, e.g. CG31.smg or CG39.smg. Most of these images are signed by motorola with a special version number (e.g. 6 or 7 on defy+ roms).
Our TI Omap processor has an e-fuse built into it which is some sort of a flash counter. It doesn't count how many times you flash, but the level of the CG__.smg you have flashed onto your device. If you flash an sbf with a CG31 (the bootloader) on version 7, you'll never be able to flash a CG31 lower than 7. Motorola increases this number for every update they make, to ensure that a user always uses the latest motorola software. This means it is impossible for let's say a defy+ user on 2.3.6 to downgrade to 2.3.5.
everybody has bootloader 9.10 (EDIT: Most do, but I've seen 90.73 and some others as well), but it has been re-signed and made only to accept the newest kernels, so your green lens is stuck without camera. Only the latest Motorola sbfs are bootloader7 (as of june 2012)
Click to expand...
Click to collapse
Thanks.
---------- Post added at 02:35 PM ---------- Previous post was at 02:34 PM ----------
Auris 1.6 vvt-i said:
He can root, he can flash custom ROM's, but the only kernel he can use is the GB kernel, so camera won't work (he has green-lensed camera) and if he tries to flash a Froyo kernel, he will end up with a BL error.
Click to expand...
Click to collapse
Thanks.
Hello, I recently tried to get a custom recovery on my phone. tar yielded `bad magic` on the archive and the installation failed.. I thought nothing was actually changed on my phone, but when I did a reboot my phone didn't start back up. It's in a boot-loop. I tried clearing cache, data, and everything else but it's stuck. I'm convinced I need to reflash a stock ROM.
My only problem is I can't tell which ROM I need. I wasn't careful enough to write down the exact version numbers of everything for my MB525. I just know this:
It's a red-lense model.
Came with Android 2.1, but later upgraded to 2.2 (via the built-in carrier provided software update method)
The carrier for it is T-Mobile US.
I checked the list ( droid-developers.org/umts_jordan/list.php) , but there are two firmwares listed for T-Mobile US. I'm really afraid of getting a higher version that what I was at because of the whole fixed-system partition bit explained in the beginners guide. So I'll ask here before I break my phone. Basically, I want to eventually get CM running on it and such, but I want to always be able to fall back to the version of Android 2.2 that I was running previously.
Basically, which ROM is the one I need to get my phone booting again?
T-Mobile_MB525_6.19.0_1FF.zip - this one is CG39.smg version 2, so this one should be an Eclair.
JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf - this one is CG39.smg version 4 - therefore - Froyo.
If you have previosly been on Froyo, don't try to flash the Eclair, or you'll end up with a BL error.
That worked! That's the one I figured I should use, but the version number on it is `6` unlike every other version 4 CG which is `3.4`.
Now that I got a good ROM to fallback on, time to get a custom recovery and try some custom ROMs
Actually, that version is Android 2.1. The firmware version is "2.1-Update1"
It worked for my phone anyway though. Not quite sure how.
Weird! Its CG39 version is 4, therefore I assumed it was Froyo... Didn't know there was a version 4 Eclair...
Sent from my MB526 using XDA
Auris 1.6 vvt-i said:
Weird! Its CG39 version is 4, therefore I assumed it was Froyo... Didn't know there was a version 4 Eclair...
Sent from my MB526 using XDA
Click to expand...
Click to collapse
Is that an other downgrade sbf like bl6 froyo?
sent from my Defy+
Hello, I got a Motorola Defy (MB525) red lens (Bayer Module). At the moment I'm using Froyo 2.2.1 Retail, without root. This is my first smartphone and I want try CM9 out, but I don't have any experiences about install custom ROMs, I've read many tutorials on the internet, but they are very different, so I would like that you solve those doubts:
1. Should I use build 120705 by Epyson or 120707 by Quarx?
2. Should I use Froyo or Gingerbread build?
3. If I should use Gingerbread build, which kernel should I use?
4. Should I install battery fix?
I MAINLY want to be able to go back to my stock ROM because if something goes wrong my phone still on warranty, what should I do then? After reading many tutorials I though the better way is like this:
1. Root phone
2. Install 2ndInit 2.0
3. Create a Nandroid backup
4. Flash the ROM
5. Flash the kernel (?)
6. Flash gapps
7. Done?
Then if I want everything back, I should just restore the Nandroid backup + uninstall 2ndInit 2.0 + unroot and everything on my phone will be like when I was running Froyo 2.2.1 and warranty will be back? Or should I flash a Full SFB?
Here are the informations at 'About the phone':
System Version: Version.34.4.709.MB525.Brasil.en.BR
Build number: 0
Model number: MB525
Android Version: 2.2.1
Version number: 3.4.2-107_JDNL-9
I'm using epsylon's build and it works flawlessly for me, didn't try quarx's so I can't compare.
If you want to keep downgrade ability you have to use froyo kernel so froyo build too.
For the battery fix afaik it's only needed for Defy+.
In your steps to upgrade you forgot doing wipe of user data, cache and dalvik cache (and also battery stats) before flashing.
What llamatron said PLUS:
You can use a build for Defy, then flash CM7 kernel. Or you can use Defy+ build (works for red lens defy too) and flash the cm9 kernel.
Edit: obviously, in your case, you would have to use CM7/Froyo kernel + defy build.
Proper instructions can be found here:
http://forum.xda-developers.com/showthread.php?t=1432100
After your step 3 wipe data as llamatron said. Then proceed with 4,5,6.
Llamatron said:
I'm using epsylon's build and it works flawlessly for me, didn't try quarx's so I can't compare.
If you want to keep downgrade ability you have to use froyo kernel so froyo build too.
For the battery fix afaik it's only needed for Defy+.
In your steps to upgrade you forgot doing wipe of user data, cache and dalvik cache (and also battery stats) before flashing.
Click to expand...
Click to collapse
It is not flashing a kernel that prevents the downgrade ability - it's the full SBF flashing that does this. As long as you stay away from RSD Lite and SBF files, you are safe.
Regarding GB or Froyo, IMHO GB builds are better - faster, smoother, longer battery life. I have a red lens Defy and prefer Quarx's Defy+ builds. The beauty of the red-lensed Defy is that you can try everything - Froyo builds, GB builds and decide which one suits you best. Green-lensed Defy is limited to Froyo builds only and most of Defy+ are limited to GB builds only. If the OP wants, he can try Quarx's latest GB and Froyo builds with fully functional HWA and Apps2SD. Check my thread in General - you will find anything you need, including Battery fix and when should you flash it.
Auris 1.6 vvt-i said:
It is not flashing a kernel that prevents the downgrade ability - it's the full SBF flashing that does this. As long as you stay away from RSD Lite and SBF files, you are safe.
Click to expand...
Click to collapse
That's right, sorry for the mistake I had read the all in one defy guide long time ago and didn't understand well this part apparently
Vitor_Hugo said:
1. Should I use build 120705 by Epyson or 120707 by Quarx?
Click to expand...
Click to collapse
I reccomend you Epsylon's build. I use it on daily basis and hasn't disappointed me so far.
Also check out the new Froyo kernel release kernel-froyo-222-179-4-signed
Oh! And if you'll use both, don't forget to enable HWA. It will perform great!
Thanks, I'll go with Gingerbread builds, now I have more 2 doubts:
1. Would Nandroid backup restore my Froyo ROM successfully from a CM9 Gingerbread build?
2. I saw that there are 2 gingerbread kernels on Auris's topic: CM9 Kernel signed and 4.5.2_DHT-22_kernel. Which one should I use?
Vitor_Hugo said:
2. I saw that there are 2 gingerbread kernels on Auris's topic: CM9 Kernel signed and 4.5.2_DHT-22_kernel. Which one should I use?
Click to expand...
Click to collapse
Use CM9-kernel when first flashing CM9. If you flash 4.5.2_DHT the first time, phone won't boot. You can flash this kernel after the inital boot with CM9 kernel.
Vitor_Hugo said:
1. Would Nandroid backup restore my Froyo ROM successfully from a CM9 Gingerbread build?
Click to expand...
Click to collapse
No. In order to return your phone to stock, you need to flash Stock SBF file via RSD Lite. Before flashing an SBF file, make sure it is the correct one, as there is no downgrade, so if you flash wrong sbf with higher BL version (for example stock 2.3.6), you will never be able to go back to Froyo.
Auris 1.6 vvt-i said:
No. In order to return your phone to stock, you need to flash Stock SBF file via RSD Lite. Before flashing an SBF file, make sure it is the correct one, as there is no downgrade, so if you flash wrong sbf with higher BL version (for example stock 2.3.6), you will never be able to go back to Froyo.
Click to expand...
Click to collapse
Sorry, but why on your CM9 Thread you do recommend to make a Nandroid backup?
I've been reading CM9 topics and I came to the conclusion that it still unusable for me, so I'll try CM7.2 stable and wait for CM9 RC1.
Will gapps 20120429 works on CM7.2 or is there another version for CM7.2?