Database Users

[Q] MultiBoot & ICS

Unfortunatelly I don't have permissions to reply in this topic, so I created this one.
I have Installed CM7.2 (from Quarx) on stable recovery and ICS to latest recovery. I use multiboot for this.
Everything worked good, but one of the newest version of ICS has newer kernel, so after I choose it phone just stucks at Moto logo...
So I have 2 questions:
1) Is it possible to get working new ICS on multiboot?
2) If no, how can I delete ICS from latest recovery and install there other firmware?
Thanks

AstorDev said:
Unfortunatelly I don't have permissions to reply in this topic, so I created this one.
I have Installed CM7.2 (from Quarx) on stable recovery and ICS to latest recovery. I use multiboot for this.
Everything worked good, but one of the newest version of ICS has newer kernel, so after I choose it phone just stucks at Moto logo...
So I have 2 questions:
1) Is it possible to get working new ICS on multiboot?
2) If no, how can I delete ICS from latest recovery and install there other firmware?
Thanks
Click to expand...
Click to collapse
Nope its not possible to have the newer versions including 111207 on multiboot!
to get rid of ICS in the latest boot you can just flash an other .zip over it, like miui or stuff...
hope it helped, greetz Esok

It is possible
Yes, it is possible. The only vital pre-requisite is to upgrade the main CM7 system to 2.3.4 kernel version.
But before, take care of:
1. The 2.3.4 kernel has some issue regarding camera, specially green lens (I think it doesn't work yet). Red lens work great, after a few work around with some overlay libs. (all this stuff very well described on CM7 thread).
2. Once you upgrade the kernel, you could install CM9 latest test builds.
pros:
- both systems running latest GB kernel (remember be sure to use 2.3.4)
- great to have CM7 and CM9.
cons:
- be sure to fix your camera in CM7. (of course, hope you have red lens )
- in my case: CM9 boot, but it doesn't detect the baseband (if I check "About phone" Baseband details show "Unknown"). WiFi work Ok.
I really appreciate any advice in this last comment.
Happy holidays

problem from 2.3.4 to room cooked

hi all,
if i flash the 2.3.4. can i flash after any firmware coocked? I have already flashed it to 2.3.4 and when i try to fash any room coocked i have the phone in black screen and doesn't start. there is some problems about the update related to bootloder update ?

Long story short: if you flash the official 2.3.4 rom (kernel), you lose the option (at least at the moment) to downgrade it.
Since most of the current roms for the Milestone 2 (MIUI and CM7 - both "vanilla" by tezet and ICS themed by endless7) use the older kernel, you can't use them anymore.
You could try MS2Ginger by walter79, which is based on the 2.3.4 kernel (the Chinese one).

djlooka said:
Long story short: if you flash the official 2.3.4 rom (kernel), you lose the option (at least at the moment) to downgrade it.
Since most of the current roms for the Milestone 2 (MIUI and CM7 - both "vanilla" by tezet and ICS themed by endless7) use the older kernel, you can't use them anymore.
You could try MS2Ginger by walter79, which is based on the 2.3.4 kernel (the Chinese one).
Click to expand...
Click to collapse
I have just tried to flash MS2Ginger but at startup the phone stays with saver screen. Now, the
rsd motorola doesn't recognize the phone.
DO you have any solution?
thanks

I'm sorry, I have no clue...

djlooka said:
I'm sorry, I have no clue...
Click to expand...
Click to collapse
i'm not able to flash correctly the MD2 version.

I ve succesfull installed MS2 Ginger 2.0.
You have to restore nandroid backup but dont flash the fixed .fsb and do a complete wipe with the stock recovery !
That 's work !!!

[Defy+] Downgraded To CM7 from CM9 & Battery Shows Question Mark

Last night I rooted my Defy+ with CM7(latest nightlies from defy-cm.net), applied battery and camera fix, everything worked perfectly and I enjoyed it.
I tried little experimenting then installed CM9(usedEpsylon builds) and flashed the kernel mentioned here(http://forum.xda-developers.com/showthread.php?t=1432100&page=3) but then I noticed it had lot of bugs and my phone started having a lot of weird reboots.
So I thought of reverting back to CM7 and then problem of the battery popped up. Battery now shows a question mark and I dont know whether it could charge or not. After reading a lot I thought it would be better to revert to CM9 just incase if the battery isn't charging and then I'd have to find a workaround for charging.
Although I love CM( very much but I can't stick to it because of the camera and a lot of instability.
After studying forums I realised it may be because of the incompatible kernel for CM7. So the only way I could get teh original kernel is by flashing the original SBF. But the problem arises is that I cant find the same build for my device and I am little skeptical about flashing with different SBF. Also I have no nandroid backup as such. Nearest I could find a SBF was with 4.5.1-134_DFP-1321. Also I have gone through all the Walter79 posts and his SBF collection too and it doesnt have the SBF for my DEFY+.
Can somebody guide me with the workaround?
My DEFY+ specifications:
system version - 45.0.891.MB526,AsiaRetail.en.03
model number - mb526
android version - 2.3.4
baseband version - epu93_u_00.60.00
kernel version - 2.6.32.9-gbdd614e [email protected]#1
build number - 4.5.1-134_DFP-891

Hi,
My Defy+ also came with the same SBF version however I updated it to another one and now service center updated it to another one(which is unrootable!!) So be careful while choosing the SBF(Don't worry I will tell you which one should be safe! ). First:
There are issues with battery charging with CM9. moreover you should have tried Quarx's build CM9 for Defy+. Both CM7 and CM9_Defy+ of quarx are more stable!! however, as per memory serves I remember flashing CM7 for Defy when I had the version of SBF you have, so I believe even CM9 for Defy should work(No need to flash extra kernels if you flash the Defy versions of CM).
Now coming to the SBF part you may go for this SBF(from my dropbox). It is 4.5.1-134_DFP-1321 version SBF. That will update your phone to 2.3.6 and BL6. Thus you won't be able to downgrade to any Froyo kernels and will have to use CM7 and CM9 for Defy+ builds(use Quarx's build this time). However NEVER flash the version with DFP-231!!! It has BL7 and is still not rootable!!! ( Thanks to dumb service center people I am stuck with this!!)

pranks1989 said:
Hi,
My Defy+ also came with the same SBF version however I updated it to another one and now service center updated it to another one(which is unrootable!!) So be careful while choosing the SBF(Don't worry I will tell you which one should be safe! ). First:
There are issues with battery charging with CM9. moreover you should have tried Quarx's build CM9 for Defy+. Both CM7 and CM9_Defy+ of quarx are more stable!! however, as per memory serves I remember flashing CM7 for Defy when I had the version of SBF you have, so I believe even CM9 for Defy should work(No need to flash extra kernels if you flash the Defy versions of CM).
Now coming to the SBF part you may go for this SBF(from my dropbox). It is 4.5.1-134_DFP-1321 version SBF. That will update your phone to 2.3.6 and BL6. Thus you won't be able to downgrade to any Froyo kernels and will have to use CM7 and CM9 for Defy+ builds(use Quarx's build this time). However NEVER flash the version with DFP-231!!! It has BL7 and is still not rootable!!! ( Thanks to dumb service center people I am stuck with this!!)
Click to expand...
Click to collapse
Your Dropbox Link isn't working any more

iNOXIA2012 said:
Your Dropbox Link isn't working any more
Click to expand...
Click to collapse
Hey. Wait for sometime. I will update the link.

Please allow a short question concerning the downgrade:
I'm currently on CM10 on my Defy+ and want to go back to CM7.
Can I just use the recovery boot and install from a CM7 file or is anything else needed before flashing CM7 file?
Thanks a lot

[Q] Steps to upgrade defy from 2.2.2 to ICS

Hi,
I recently bought Defy MB525 mobile and it is under warranty till feb'13.
Below are current specs of my mobile-----
System version: Moto_version.34.3601.7.MB525.Retail.en.SEA15
Firmware version:2.2.2
Kernel Version: 2.6.32.9-g0671d13
Build number: JEM3.4.3-36-1.7
Camera Hardware: SOC
--------------------------------------------------
Please share the steps i should follow for 1) backup existing stock version 2.2.2, 2) overclock CPU, 3) upgrade to latest stable ICS version, 4)restore stock version 2.2.2.
Let me know if you need any other details.
Thanks

hi there
well to backup your stock rom first of all you need to root your phone with superoneclick google it.Then install latest 2nd init form here http://forum.xda-developers.com/showthread.php?t=1032212.after that reboot and when your phone blinks blue push vol down button to get into bootmenu.select custom recovery/backup all(to backup you rom)
3)either you download epsy/quarks ics build http://forum.xda-developers.com/showthread.php?t=1432100 or aopk http://forum.xda-developers.com/showthread.php?t=1585425 and the ics gapps.then move those to sd card and enter bootmenu again select wipe data/cache and install zip from sd card:chose one of the 2 above and the gapps after finish reboot and VOILA ics

How is camera in ICSROM?

camera works fine but panorama fc

Thank you, have some questions again
Thank you very much for replying, i am half journey way to start updating to ICS
i have downloaded epsy CM9-NIGHTLY-120406-Defy.zip, is it right one? is there a stable version?
when to overlock the cpu after installing ICS or can be done before?

I'm not sure if there's a stable CM9 release for Defy.
when to overlock the cpu after installing ICS or can be done before?
Click to expand...
Click to collapse
After the update..

I'm using 06.04 by Epsylon3 with Froyo kernel and green lens: I find it stable enough, good for day to day usage. There's no CM9 stable version, not even a RC one.
You can overclock the CPU from the bootmenu, although CM9 comes with 1GHz standard. Maybe undervolt it a bit.
Trimis de pe Defy CM9

Confused on updating android
I am bit confused updating android.. We are wiping the data and reloading a ICS right?? why do we need froyo kernel to update to ICS
Can you please share a link explaining it? reasons, procedures.

Rodefy said:
I am bit confused updating android.. We are wiping the data and reloading a ICS right?? why do we need froyo kernel to update to ICS
Can you please share a link explaining it? reasons, procedures.
Click to expand...
Click to collapse
We need froyo kernel because we have SOC (green) camera ;-(
So we need to flash CM7 kernel too. If you use CM9 kernel, then your SOC camera will not work
Procedures in this thread in the first post
I also had to flash ICS Gapps zip (somehow ommited in the procedure)
You can use mentioned nightly - works fine
I would propose to use titanium backup from the market to backup all your apps with data - then you can simply restore them back with all data inside (but your apps - do not restore system apps)

[Q] Please check my approach - Flashing right from UK stock Defy to Quarx CM10 4.1.2

Hi All,
I've done literally weeks of research on this, so hopefully I've not missed any easy posts, but I want to check my approach and ask a final question. This is my daily phone, and while I know the risks and issues with custom roms, I want to get it right. Hope someone can advise.
ROM I want to install is Quarx's JB 4.1.2 CM10.
Phone I have is UK Motorola Defy (Red Lens, original):
System version: Blur_Version_2.21.0.MB525.Retail.en.GB
Model Number: MB525
Firmware version: 2.1-update1
Baseband version: EPU93ST2_U_03.02.00
Kernel version: 2.6.29 [email protected] #1
My plan is:
1. Official upgrade to Froyo - it seems this is not yet done on mine, and custom ROMs require its Kernel, I read
2. Root phone - SuperOneClick
3. Titanium Backup - Needs Root
4. ClockWorkMod Recovery - Needs Root, and gives me Nandroid Backup capability in BootLoader
5. Nandroid Backup - this should provide me a route back to stock (* see question below)
6. Flash ROM - this will give me CM10 based on Jelly Bean 4.2.1
Question is, despite reading many threads, I'm still confused on CG versions and SMG file versions (CG##.smg). I do want to be able to flash back to stock after this, in case I want to sell the phone - if I flash up to Quarx's CM10 JB 4.1.2, what CG version is it and is it higher than I can possibly get back to stock from? Or can I find a Fixed SBF of a Stock ROM that will let me go back? How can I best prepare for this?
Anything else to be aware of or concerned about?
Thanks very much.
Steve.

The easiest approach is to directly flash cm10 first and check off it works(you can flash back your stock sbf if there's any problem) because CM10 WILL NOT INCREASE YOUR CG VERSION
The potential problem you can face(which can not stop you from stock sbf flash) is an incompatibility of 2ndboot with your stock kernel.
If you run into that problem (which I think should not occur) you will have to flash a compatible sbf, with higher cg version and a compatible stock kernel.
Sent from my MB526 using xda premium

Thanks - good to know CM10 has no CG version. I expected the developers to want to get rid of that kind of limitation as soon as they could!
Hmmm, so could someone confirm, that Quarx's CM10 will flash directly over the stock 2.1 Eclair ROM as listed above (with root/CWM), and doesn't need Froyo deployed as a base? That would really help if so - then I have no further considerations and I can just get on with it. I'll take it carefully and I'd rather not be faced with non-booting etc the first time round.
I believe wifi tethering doesn't work on it, though, or there's some problem with restarting regarding wifi tether. That's a shame, but maybe an app like Barnacle or OpenGarden can work instead...?

You could try it yourself by taking a Nandroid backup and if you face the non booting problem then flash stock sbf+ restore. Beware that sometimes first boot hangs or bootloops and in such cases you can fix the problem with a battery pull, or data wipe respectively
Open garden works without issues
Hit thanks!