With the last gingerbread kernel (android 2.3.6) i dont found way to the cam works. Anyone knows how to make it? downgrade to froyo/GB 2.3.4, a new Green Bread Mod.... something that the people who has flashed the gb kernel by error can fx it.
Sorry for my english.
Stock camera app wont work. try lgcamera
I already tried it. Don't works.
DONT downgrade to 2.3.4, youll brick your phone! green lens wont work on gb (2.3) kernels, because official gb roms are for defy+, and defy+ has red lens, so the green lens module is excluded from the kernel. but as far as i know, epsylon3 is working on a cam driver.
I have tried differents methods to dowgrade but anyone has bricked the phone, i only reflash 2.3.6 sbf. would you tell me where i can find about epsylon3 work? Thanks very much.
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...
If you take a picture with the camera on CM7, in the camera model (at the end of the details pop-up) it says: "Camera: Motorola MB525 7dfc0002ffdc0000016b23ba0703601a"
it may be a bug or a mistake of the CM7 developers, there's any way of changing it?
Could you tell if you use a Defy (green or red one) or a Defy+ and which Cyanogenmod7-Version you are using?
Regular Defy, BAYER lens module, Official CM 7.1.0 stable...
I don't know how to change that, but I don't think that's a CM issue.
I'm still running a Barebones (The old 2.2 version...), and I also have a similar value in the camera DCIM field, just with a differen hash/serial-no.
i have problem,
why Camera Model not detect?
i'm using CM7,CM9,CM10, MiUi on Motorola Defy(red lens) ...
how i can fix it?
take a picture from your defy (with all CM version), and upload to regex.info/exif.cgi and see..
Camera Model problem..
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
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.