I have a problem with SMS. I can't send any message. SMS center is ok i have 601000310 (PLUS GSM in poland). Where I find solution?
[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+)
- Thread starter Quarx
- Start date
Updated bug list / Question about bug #22, reboot to recovery
@ all other users: Please give some feedback if I can mark bug #22 as solved.
Many thanks for the new bug fixes! :good: I just updated the bug list accordingly.New update for 29dec build
For me it works too (I never had problems with it under CM11), @pilson66 reported the same and also @Fight4Music wrote to me that this bug is fixed for him. Nevertheless, today two users still reported that it's not working:
@sokool27 and @justjr: We need more infos. Are you on the latest 12-29 nightly? Have you installed update from 2014-01-03? Did you do a clean install (data wipe / factory reset) when installing CM11?
@ all other users: Please give some feedback if I can mark bug #22 as solved.
I added it to the bug list, since it was already confirmed by @sokool27.
Last edited:
As far as I remember it was:
CM11 10.12.13 clean install -> CM11 29.12.13 + battery fix (without data wipe) -> kernel update (no data wipe) -> 3.01 update (no data wipe)
@ all other users: Please give some feedback if I can mark bug #22 as solved. [/B]
I added it to the bug list, since it was already confirmed by @sokool27.[/QUOTE]
Bug #22 seems to be resolved for me
Sent from my MB526 using xda app-developers app
[/B]I added it to the bug list, since it was already confirmed by @sokool27.[/QUOTE]
Bug #22 seems to be resolved for me
Sent from my MB526 using xda app-developers app
So the critical bug that phone is randomly muted when bt was used before is very difficult to solve?
and @okij@ all other users: Please give some feedback if I can mark bug #22 as solved.
I added it to the bug list, since it was already confirmed by @sokool27.
For me bug #22 is not solved. Can't boot into recovery using extended power menu
I did a clean install of 29.12. starting with flashing sbf. Both updates are installed (of cause the latest one installed at last
) wiped cache and dalvik after installing.I have a MB525 green lense.
Well, actually i am on 3.4.2-177-3 and i haven't flashed yet any BL7-based sbf (>DFP-188)...because if i'm not mistaken, the BL7 is the locked bootloader, and under BL7 are unlocked.
Anyway, since I had some problems with this CyanogenMod concerning to the small size of /system, i asked how to enlarge /system partition because i can't flash any gapps package larger than 40 MB, like BaNkS GApps 4.4.2 Standard or pa-gapps full package
and since the defy has 2 GB of NAND memory, I'd like to take advantage of more space for the /system partition. I've looked everywhere and i didn't find anything that could help me, so i'd like to know how to change the size of the partition Idem for me. This has ignited a real debate!and @okij
For me bug #22 is not solved. Can't boot into recovery using extended power menu
I did a clean install of 29.12. starting with flashing sbf. Both updates are installed (of cause the latest one installed at last
I have a MB525 green lense.
Last edited:
No you have completely misunderstood, NO software version is ever bootloader unlocked for our phone. Please do not try any such thing or you will definitely have to buy a new phone. The BL7 vs lesser than BL7 is something else entirely...
Just flashed 29th update on 10th release. Mute button was my problem as i get on to conference calls a lot. That is already fixed. All other i will test and let you know
Sent from my MB526 using XDA Premium 4 mobile app
---------- Post added at 09:02 PM ---------- Previous post was at 08:44 PM ----------
Sent from my MB526 using XDA Premium 4 mobile app
Sent from my MB526 using XDA Premium 4 mobile app
---------- Post added at 09:02 PM ---------- Previous post was at 08:44 PM ----------
FM works perfect
Sent from my MB526 using XDA Premium 4 mobile app
@ all other users: Please give some feedback if I can mark bug #22 as solved.
I added it to the bug list, since it was already confirmed by @sokool27.
I never suffered from this bug. My flashing path was Stock SBF --> CM10 --> CM10.2 --> Update Recovery --> CM11-12202013 w/Minimal Gapps --> all the recent Updates, just with Dalvik/Cache wipes before and after flashing them.
Thank you, I apologize
On my old logic board (I changed it because had broken the power button) i had BL7, and I really believed that I could no longer change the kernel or something like, because once i bricked the phone by flashing the same kernel that i had flashed on cm10 before i flashed the BL7 sbf and by reading some posts i believed that BL7 was definitely locked and below of it would have been different.So if i understand correctly, the size of the various partitions, including the system, are prescribed in the bootloader and can not be changed because of the locked bootloader, and it will be impossible to get the space you need to flash these gapps. Is that so?
Last edited:
Does not work for me, too (actually I don't care, just tried it for the first time ever). Mine is also MB525 green lens with BL6 (at least I think so, but it's definitely not BL7).@ all other users: Please give some feedback if I can mark bug #22 as solved.
Possibly related to this, I noticed today that the bootmenu in general is mostly broken on my device. E.g. format to ext3/ext4 does not work, and most importantly, adb daemon simply reboots the device: I broke my kernel this afternoon and the only way I could fix this eventually was via SBF
Afterwards I tried an older version of the bootmenu (from latest Quarx CM10) and all functions are working fine there.
Can anyone confirm this issue?
This may sound noobish, but can I go back to BL6 after flashing BL7 to see if this is the cause? Or is there any drawback in updating to BL7 at all?
Yes is updated to the last date, always. I already did a lot of clean installs since KitKat, even without data restore it stills the same.
Last edited:
#22 still occurs on my BL4 MB525 Defy. Clean instal from SBF.
Sent from my MB526 using Tapatalk
Sent from my MB526 using Tapatalk
Im still in two minds about installing the 3/01/14 update.
I don't want my phone to wake up in my pocket (as stated by many) also don't want it to lock while typing something (as stated too).
Sent from my MB526 using Tapatalk
I don't want my phone to wake up in my pocket (as stated by many) also don't want it to lock while typing something (as stated too).
Sent from my MB526 using Tapatalk
Then you must not activate the S2W function.
The bugs are related to that function.
Sent from my MB526 using Tapatalk
Well this is how all this "BL" stuff works:Does not work for me, too (actually I don't care, just tried it for the first time ever). Mine is also MB525 green lens with BL6 (at least I think so, but it's definitely not BL7).
Possibly related to this, I noticed today that the bootmenu in general is mostly broken on my device. E.g. format to ext3/ext4 does not work, and most importantly, adb daemon simply reboots the device: I broke my kernel this afternoon and the only way I could fix this eventually was via SBF
Afterwards I tried an older version of the bootmenu (from latest Quarx CM10) and all functions are working fine there.
Can anyone confirm this issue?
This may sound noobish, but can I go back to BL6 after flashing BL7 to see if this is the cause? Or is there any drawback in updating to BL7 at all?
It's technically not related to the bootloader. The numbers 4,5,6,7,etc are versions of the signature that the different partitions are signed with inside the sbf files. When moto released an update they genereally resigned with a higher version, and if you flash a ROM with signature version 5 for the system and boot partitions then you cannot flash an sbf that contains system and boot signed with v4 or below, for example. I think these were the two main partitions that were checked by the bootlaoder for the signature version.
Generally Eclair was at 3 or 4, Froyo ROMs were 4, GB (for Defy+) were 5, 6, and later 7. Now the main drawback with updating a Defy green lens beyond 6 was that the boot partition (kernel) for sbf's signed 7 didn't contain the soc module (green lens) driver, they only had bayer module (red lens) drivers. So camera stopped working on mb525 with sig ver 7. These days that doesn't matter ofc because of 2nd boot and custom kernels, where quarx and the guys added both drivers.
So if you want to test a version 7 boot partition (stock kernel) then you can do so (by flashing BL7 sbf) as long as you do not need to use the camera in stock ROMs beause you cannot flash "BL6" sbfs again. So finally the name "BLx" is actually a misnomer. It's more accurately described as signature version of the system and boot partitions, which are located in the CG31.smg and CG39.smg inside the .sbf files I believe.
Also did you try the newer bootmenu after flashing the sbf? A few times such random problems are solved by formatting the partitions in stock recovery or by flashing sbfs, for example the cache partition seems to become corrupted in some circumstances. I think in custom recovery we do not format, but just remove all files in them. Not sure about this though.
Last edited:
UNhappy !
Very unhappy with the 3/1 update having so many problems........
1)Random reboots
2)Battery loosing..sudden drops.
3)Slow performance than b4.
4)wifi restarts
has many bugs i guess
Very unhappy with the 3/1 update having so many problems........
1)Random reboots
2)Battery loosing..sudden drops.
3)Slow performance than b4.
4)wifi restarts
has many bugs i guess
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone