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

Greetings + [Q]'s

Hello there fellow Defy modders ^^
In a week & a half :drools: I'll be getting my hands on one of these bad boys...
I've been modding my Huawei IDEOS U8150 for 1 year or so... <<= Easy to mod... & prior to that it's been all Moto's - V360v & Krzr K3
Some questions: re, defy -
*Do I need to check firmware compatibility before flashing a ROM? (old Moto Krzr K3 hang up) If so - how do I find out what firmware is on ph?
*Does bootloader version also affect which ROM I flash? (my old K3 had a b/l that no-one had ever heard of). Again, how do I find out bootloader version? <<= disregard if doesn't hinder modding process...
*Does the recovery that can be flashed via ROM Manager work for all defy? (seems unlikely, but thought I'd ask)
*No Frills CPU app... I'm guessing it doesn't work on defy. Is this the case? Or, does no-one really use it?
*Blur or not to blur... What's the general consensus?
*Is the bootloader still locked? I've seen a few posts around with leaked b/l... has anyone cracked it?
*Is RSD lite a must? Or can we get away with using the Android part of the ph to do all things?
*I am thinking of doing the following (initially - just to wet the whistle) Please advise if I should be doing other stuff...
a) Root using z4root <<= worked on my 2.2 IDEOS, my defy has 2.2 out of the box -=or=- Superoneclick... (having never used S1C - is it safe i.e. no chance of a soft brick)
b) Get custom recovery up & running... bit hazy on this (extra steps needed when comparing to my Huawei - from what I've read), any advice welcome.
c) [Will del crapware 1st] Make a backup of stock using above... (this is hopefully straightforward).
d) Flash a custom ROM... from what I've read this is a contrived process ^^ colored lenses, fixed SBF's, can't downgrade b/l, etc. etc. etc. (ahh, the rigmarole that is modding Moto is flooding back to me now). Which custom ROM should I be looking @ 1st?
e) Help out with testing & sharing where I can... I'm no dev. but I'll help out anyway I can ;-P
T.I.A

Hi,
Yes the bootloader is locked and (at this time) nobody manage to crack it.
In another hand, coz of this, its almost impossible to brick this phone.
You need to follow the rules about the CG versions of the SBF you use before flashing a new rom (no downgradabilty if you use an highter version than your original)
To root different tools exist. It depends of rom version.
Example: Froyo 2.2 -> Gingerbreak. apk / GB 2.3.4 -> Root3 / 2.3.6 -> S1click... But all are safe.
For the installation of new rom use Defy 2ndinit (bootloader locked) incudind CWM recovery... And for the CPU SetVsel apk
But read this thread first, it will help you I think and give you a lot of answers.;-)
http://forum.xda-developers.com/showthread.php?t=1216982
Oh last ! The general consensus... NO BLUR

Read here (xda - Android app & games) that z4root 1.3.0 works for rooting defy (stated in OP) + in another thread re, Droid2 hack [was this only valid for 2.1? <<= Guess I'll test it out unless someone says it's a sham -=or=- it'll soft brick my new ph
Can't wait to get my modding claws into it

If your defy is 2.2 Froyo use this tool to root (it worked perfectly for me)
http://www.megaupload.com/?d=VFHRCZX8
Put the apk on your SDcard, open it and install with file manager (IO file manager from the market is good)
When it's done use 2ndinit http://forum.xda-developers.com/showthread.php?t=1032212
And enjoy! ;-)

Well... Well... Well...
3 holes in the ground
Couldn't wait, so I went & got my defy early :shh: [don't tell the wife]
What I know/have done to it so far...
*bootloader 9.10
*rooted with Superoneclick
*recovery 2.5.1.8 <<= do I need to upgrade this? xx
*Overclocked 1Ghz with 'Milestone Overclock'. How high can I take this beast?
*Installed RAM script - Juwell
*Backed up
*Installed all my fav apps etc.
*Backed up again
Q's:
#Can/should I install CWM via ROM Manager? (it won't let me use it unless I install CWM) Will this stuff up 2nd init? xx
#Going to try Camera 720p hack soon
#Not going custom ROM yet... want to get to know my ph 1st :chortle:
TIA

Didn't tell your wife !...
Ok I never used ROM manager, too complicated for me (I'm a lazy guy)
For the recovery, the version included in 2ndinit is CWM CyanogenDefy Recovery v5.0.3.1.
About 2ndinit, coz of the locked bootloader, you'll be obligated to use it sooner or later, so... (in this case you don't need to have another recovery)
For the CPU, SetVsel on market is ihmo better. (Be careful this apk is included in the CM7 rom, so delete this apk before flashing CM7)
For save your apk Titanium Backup is great.
IO File manager do well the job...
Edit : CM7 and lot of custom rom are already at 1 Ghz (Omap 3630 is underclock at 800mhz (MB525), normal at 1ghz (MB526), overclock at 1.2 Ghz (Droid2)).

mdt24 said:
For the recovery, the version included in 2ndinit is CWM CyanogenDefy Recovery v5.0.3.1.
About 2ndinit, coz of the locked bootloader, you'll be obligated to use it sooner or later, so... (in this case you don't need to have another recovery)
Edit : CM7 and lot of custom rom are already at 1 Ghz (Omap 3630 is underclock at 800mhz (MB525), normal at 1ghz (MB526), overclock at 1.2 Ghz (Droid2)).
Click to expand...
Click to collapse
I'm thinking if I do a ROM Manager CWM update it'll hopefully dovetail in with 2nd init...
i.e. 2nd init will still work but show the updated CWM :fingers-X:
Read some people have it up to 1.2 - 1.3 OC... but, with no safety valve [used to using No-Frills... it prevents bootloops from to high OC-ing] I'll stay @ 1 Ghz - until I grow some stones :lol:
re, 2nd init - it wasn't available on Market... so I d/l-ed it somewhere else ^^
could you point me to latest 2nd init?
TIA

There ;-)
http://forum.xda-developers.com/showthread.php?t=1032212
Edit : 1ghz is imho a good choice. Good perf/baterry used - Good CPU for me : 300Mhz - Vsel 30 / 600Mhz - Vesl 48 / 1ghz - Vsel 58

thnx mdt24 for answering my questions ^^
So, if you dont mind... I'll keep going :lol:
Above is my info...
I'm thinking about debranding/upgrading - but haven't the foggiest on which sbf to use
I figure I'll use TBU pro to save stuff that I want... & restore later.
Which stock sbf do you recommend upgrading/debranding to... I read somewhere that not wiping the dalvik cache keeps a lot of things in tact...
T.I.A

Hi King_Rat,
As I can see you have the lastest Froyo version (2.2.2)
About upgrading/debranding it depends if you have a green or red camera.
You can check it with catlog after using camera : SOC is green; Bayer is red camera.
If you have Bayer module your defy is able to run all GB rom, if it is green only with froyo rom. Hope you have red camera :fingers X:
If you want use Cyanogen (MIUI, WajkIUI...) roms you have nothing to do, just flashing the rom give you the latest Froyo build version (3.4.2-177/179) and a 2.3.7 GB android version.
You can also flash MS2ginger roms (nandroid and fixed sbf) with or without Blur. Good step before flashing a full GB SBF (fix exists to make green lens working). http://forum.xda-developers.com/showthread.php?t=1140839
If you dont care about warranty and you got a red camera you can also flash the GB 2.3.6 full SBF you want. Work perfectly on red camera Defy (you have a defy+ with defy's battery)... But NO DOWNGRADE to Froyo !!
http://forum.xda-developers.com/showthread.php?t=966537

mdt24 said:
Hi King_Rat,
As I can see you have the lastest Froyo version (2.2.2)
About upgrading/debranding it depends if you have a green or red camera.
You can check it with catlog after using camera : SOC is green; Bayer is red camera.
If you have Bayer module your defy is able to run all GB rom, if it is green only with froyo rom. Hope you have red camera :fingers X:
If you want use Cyanogen (MIUI, WajkIUI...) roms you have nothing to do, just flashing the rom give you the latest Froyo build version (3.4.2-177/179) and a 2.3.7 GB android version.
You can also flash MS2ginger roms (nandroid and fixed sbf) with or without Blur. Good step before flashing a full GB SBF (fix exists to make green lens working). http://forum.xda-developers.com/showthread.php?t=1140839
If you dont care about warranty and you got a red camera you can also flash the GB 2.3.6 full SBF you want. Work perfectly on red camera Defy (you have a defy+ with defy's battery)... But NO DOWNGRADE to Froyo !!
http://forum.xda-developers.com/showthread.php?t=966537
Click to expand...
Click to collapse
Bayer = True :woot:
So, if I flash to 2.3.6... I can't downgrade =>> does that mean no running any custom ROM below 2.3.6?
Defy+ you reckon :mmm: ph was only 800 MHz out of the box, but I'm running along now @ 1200 MHz with no probs :kewl:
re, the GB 2.3.6 - will there be any bugs if I upgrade? i.e. camera issues -=or=- no root?
Think I'm gonna try MIUI 2.1.6 to start. After bordem sets in :lol: do I just restore my nandroid backup before changing ROMs -=or=- do I need to install a clean full sbf to change to a diff. ROM?
thnx again for your time & thoughts

King_Rat said:
Bayer = True :woot:
So, if I flash to 2.3.6... I can't downgrade =>> does that mean no running any custom ROM below 2.3.6?
Exact, but almost all the custom rom have a defy+ version now - The only problem is that u can't go back to froyo
Defy+ you reckon :mmm: ph was only 800 MHz out of the box, but I'm running along now @ 1200 MHz with no probs :kewl:
No problem to run at 1.2 Ghz, maybe the only one is the battery fast drain, coz of the hight vsel u need to prevent FC's
re, the GB 2.3.6 - will there be any bugs if I upgrade? i.e. camera issues -=or=- no root?
No bugs, its a very good GB version. No camera issues if you have a bayer (red) one root with S1Click 2.3.3
Think I'm gonna try MIUI 2.1.6 to start. After bordem sets in :lol: do I just restore my nandroid backup before changing ROMs -=or=- do I need to install a clean full sbf to change to a diff. ROM?
No need to flash a full SBF, you have just to make a wipe data, wipe cache, and -advance- wipe dalvik before flashing the new rom. Sometimes a wipe cache is enought (and u dont loose ur data) but it's always better to clean completly the ph before flashing - A battery calibration is recommended also after flashing a new rom
thnx again for your time & thoughts
Click to expand...
Click to collapse
Ok I think you are ready now. Enjoy! And please tell your wife you got a new phone before she thinks you have another girl in your life...

:lol:
flashed MIUI 2.1.6 [not sure if it's the latest, coz most of links around all forums for other MIUI versions are dead?
It's bloody fantastic!! 2371 on last Quad score & 16.43 MFlops :woohoo:
Having Wifi connection issues :grrr: could be the deal breaker if cannot remedy
Tryng to find fix 1st two solutions are null
Wife knows ;-) [I haven't told her]

Yes MIUI 2.1.6 is the latest.
Are you on froyo? Wifi issues is a well know problem with Defy on froyo, and you'll have this kind of issues with lot of rom (but generaly it's always possible to find some fixes in different threads).
With GB now I haven't wifi issues anymore...

Wifi fixed :woohoo:
Just had to get near modem last night while wife :ZzZz:
Installed some themes & added gps satellite info. :BooM:
Now having usb mass storage not showing? [no biggie as I prefer Android Manager for file transfer].
Will try usb storage on lappy tonight :mwahaha:
Having used CM7 almost exclusively on my 'other' ph. I must say that MIUI is a step up ^^ half the apps I use to run are all automated & part of the MIUI system... + the themes are smokin!
Do CM7 features change that much from model to model?
Will keep MIUI for a 'wee' while then have a look around... maybe :chortle:
thnx for ur time

Hi King_rat ;-)
I like CM7 on defy because it looks like an AOSP gingerbread rom (Nexus S - you can use the AndroidUsersGuide 2.3 to manage this rom).
I think is because of this all the other roms as MIUI, WajkIUI... use CM7 as base to make a custom rom.
My Defy is my first Android phone, so I really don't know if there is some differences with CM7 on the other phone.
... and don't hesitate to give me some advices about the rom you test... ;-)

was dam debug! toggle on for this.... toggle off for that... :lol:
Thinking about now trying wajkIUI 2.1.6 ICS... looks like improved version of current ^^
Can't find any way to change carrier text in my current ROM... have had several <fails>
Themes are outstanding!! Using a Honeybread theme... it's tight
wajkiui... maybe later today.

Xperia M 15.1.B.0.2
mdt24 said:
There
http://forum.xda-developers.com/showthread.php?t=1032212
Edit : 1ghz is imho a good choice. Good perf/baterry used - Good CPU for me : 300Mhz - Vsel 30 / 600Mhz - Vesl 48 / 1ghz - Vsel 58
Click to expand...
Click to collapse
you has xperia M fw 15.1.B.0.2, you use flashtool ..... FW_Xperia_M ...TFT, please, because i use xperia M has 15.1.A.1.9 and screen is blue, thanks,
Sorry because english is bad.

moneylatentoi said:
you has xperia M fw 15.1.B.0.2, you use flashtool ..... FW_Xperia_M ...TFT, please, because i use xperia M has 15.1.A.1.9 and screen is blue, thanks,
Sorry because english is bad.
Click to expand...
Click to collapse
No, it was on this rom when I bought it... French market...

[Q] New defy, want to get ICS/MIUI on it, help?

Hey
I just got a brand new Defy and I'm hoping I can get ICS on it. However, in my country there's no T-Mobile, Verizon, Orange or whatever, I bought it in an electronics store, so I have absolutely no idea about what CG version it is. I've already read the beginner's guide from top to bottom, but I still have some doubts:
1. How do I know which CG version do I have? (I need to know so I can know how to get back to stock in case of warranty)
Nevermind, I found the answer >_> CG 4 SBF 3.4.2 (Froyo)
2. I've seen lots of ROMs for this device, but their instructions aren't very clear and I don't want to brick my device (which, from what I've read it is very hard to do) or get stuck in a higher CG version.
3. The beginner's guide is cool, but I haven't seen any tutorials on installing a specific rom (in my case ICS) so, I'd appreciate some pointers here, if possible
Thanks in advance! =)
- DARKGuy

I have a defy+, so i have 2.3.6 on it. But you don't need to flash any new firmware to get ICS or MIUI, since they both have froyo builds. CG version only changes when you flash full SBF, not when installing zips and custom ROMs. So you shouldn't worry about getting stuck on a higher CG.
So what you need of course is a rooted phone , the SndInitDefy_2.0.apk (to install custom recovery and bootmenu because of locked bootloader), install the latest bootmenu (don't mind installing the old one although it might work on froyo). And there you're ready to flash! (to enter custom recovery on your defy, reboot your phone and press the volume down key when you see the blue led) I assume you know how to use the custom recovery, so I won't go into detail on that.
Since I haven't flashed any froyo ICS builds before, I don't dare to tell you how to myself! So just head over to the main CM9 ICS thread You'll find a guide in the first post. Nevermind, i'll just quote it here:
nogoodusername said:
How to flash ICS (Defy Builds)
1:Head Over To Stable recovery
2:Wipe Data
3:Install Zip from SD Card
4:Select ICS(Defy) .zip
5:Flash
6:Flash CM7 Kernel
7:Clear Cache and Dalvik Cache
First Boot will take some time...
Click to expand...
Click to collapse
You need to flash Google Apps seperately through recovery. You should find the files and links needed in the thread linked above. Know the difference between the Defy+ builds (with gingerbread [gb] kernel), and the Defy builds with froyo kernel.
Please note that ICS for defy is still in it's early stages and you might experience bugs. But most people still think it's worth it! xD Sorry if I made it too detailed for you, but then others can make use of it too! Oh, I hope I haven't said wrong that will soft brick your phone! Flashing the wrong kernel always gives me bootloader error! Anyway bricking really isn't that scary (only the first time i can confirm) It's good to have an SBF with RSDLite and Drivers installed on your PC just in case
Oh! And then If you want MIUI, just do the normal wipes and flash the ROM. Let me recommend MIUI Pikachu edition by TweetyPeety, the best MIUI ROM out there! It even has the touch based AROMA installer in recovery where you can customize the installation!

I was wandering if there is any advantage in flashing a newer kernel (either CM9 kernel or a GB full SBF) on defy if I'm using CM7/CM9/MIUI
Also, I tried CM9 without flashing the kernel, and it works, so I can't figure what difference would that step make. How does changing the default kernel affect the use of custom roms? Any hit in performance/usability? Would I have to use Defy+ roms if I flash CM9 kernel?

Persechini said:
I was wandering if there is any advantage in flashing a newer kernel (either CM9 kernel or a GB full SBF) on defy if I'm using CM7/CM9/MIUI
Also, I tried CM9 without flashing the kernel, and it works, so I can't figure what difference would that step make. How does changing the default kernel affect the use of custom roms? Any hit in performance/usability? Would I have to use Defy+ roms if I flash CM9 kernel?
Click to expand...
Click to collapse
I think you shouldn't flash new kernel for CM9 since it is in alpha
it is better to keep on CM7.1 and wait until a stable version from CM9 (unless you are a real HW or SW developer)

[Q] Defy CM7 to CM9 - which nightly? and what should I take note of?

Hi,
I am trying to update my dad's Defy ROM. It is currently running CM7 on it.
I did the CM7 installation last November (Nov 11 version), and I've kind of forgotten the Defy peculiarities since I am a ZTE Blade user in day to day life.
Is there anything to take note in doing the CM7 to CM9 upgrade, for instance how about the the partition size?
I am not staying near my dad so I can't do the installation myself. I will have to relay instructions to him via Skype for him to do it on his own. My dad is reasonably comfortable with technology but
Can CM9 be flashed in the conventional method via Clockworkmod? (In the same way as Blade ROM updates)
I have got him to download the latest CM9 nightly from here:
http://defy.wdscript.fr/defy-cm9/
This is the 12th July version. Can anyone tell me if this nightly is stable, and if not, which version is recommended?
Many thanks in advance for the help!

CM9 is flashed using CWM.
A full wipe(data/factory reset) will be required.
Can't get why you need to adjust partition size (you mean multiboot partitions?)

Thanks for the info.
I thought that the default ROM partition size may need to be adjusted. If not necessary then I'll just let it be.
So is the latest nightly the best option? Or is there a more stable version I should look into?

You don't need to change the partitions..
What are the specs of your Dad's defy, Is it a green lens or red lens? What kernel does it have? I need details before suggesting the nightly build.

This is a red lens defy I think, using the bayer module.
Kernel version:
2.6.32.9-gb08c3c8
[email protected] #1
Building no: Gingerbread GWK74 Cyanogen Defy 11-11-11

I also seem to have a problem doing a backup using CWM.
Any idea what's causing this error message?

Questions go in the Q&A section

Can anyone please tell me what may be causing problems to the nandroid backup? :-o

Have you seen this post? http://forum.xda-developers.com/showthread.php?t=1663613
I recently changed from 7 -> 9 using this guide word for word with no issues.

Thanks very much for the link on CM9 install.
I'm still trying to fix the nandroid backup problem. I have a feeling it's running out of space. Will clean up SD card and try again.

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