[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+)

[gatewave]

Hey guys, I wonder if you could help me with this issue.

I'm currently running CM10.1 20130709 built and was looking to update to CM11 latest version.

I followed the instractions on the first post
"For CM10,10.1,10.2 < 07.11.13 users:
To install KitKat, need update recovery. Do not forget reboot, after install recovery.
defy.bytekiste.de/cm11-nightl...e-recovery.zip
"
and updated my recovery, however after I rebooted and went into the recovery again to install the CM11 image, now every time I go to recovery and select Team Win Recovery the phone reboots.... so pretty much stuck and not sure what to do from here.

Thanks

 

[Proverbs2]

Either I'm dealing with a maverick or nobody has their phone configured for the 802.11 (wifi) network to sleep when the screen is dark but on my device wifi does not come back when the screen has been off more than $timeout minutes.

I have this issue too, but it's not new for me; I had it on CM10.2 and even sometimes on CM7. As a workaround, I use this Wifi Timeout app, which properly powers the wifi off when the screen is off, and back on again when the screen wakes. This app has the added advantage of allowing you to choose a custom wifi timeout length between 1 second and 5 minutes. (The default timeout length with android is 15 minutes after the screen goes off, so using this app to turn the wifi off more quickly may help to save battery.) :good:

---------- Post added at 09:39 PM ---------- Previous post was at 09:25 PM ----------

Hey guys, I wonder if you could help me with this issue.

I'm currently running CM10.1 20130709 built and was looking to update to CM11 latest version.

I followed the instractions on the first post
"For CM10,10.1,10.2 < 07.11.13 users:
To install KitKat, need update recovery. Do not forget reboot, after install recovery.
defy.bytekiste.de/cm11-nightl...e-recovery.zip
"
and updated my recovery, however after I rebooted and went into the recovery again to install the CM11 image, now every time I go to recovery and select Team Win Recovery the phone reboots.... so pretty much stuck and not sure what to do from here.

Thanks

Try resetting your CPU and vsel values to the default stable ones in bootmenu and see if that helps.

Does the phone reboot immediately every time you select Team Win Recovery, or does it go into TWRP briefly, and then reboot after a few seconds? If the latter, try a few more times, and always wait at least 30 seconds before flashing anything. (TWRP is notoriously unstable, and it often takes several tries before it will behave. But if it doesn't reboot within the first 30 seconds, it's usually safe to proceed with flashing.)

 

[gatewave]

Try resetting your CPU and vsel values to the default stable ones in bootmenu and see if that helps.

Does the phone reboot immediately every time you select Team Win Recovery, or does it go into TWRP briefly, and then reboot after a few seconds? If the latter, try a few more times, and always wait at least 30 seconds before flashing anything. (TWRP is notoriously unstable, and it often takes several tries before it will behave. But if it doesn't reboot within the first 30 seconds, it's usually safe to proceed with flashing.)

Well my CPU settings are default as I have have not touched them, but I'll give it a go anyways,

It resets as soon as I select Team Win Recovery.... is there a way to go back to the previous state of the TWRP? before I have applied the changes?

Thanks

 

[Proverbs2]

is there a way to go back to the previous state of the TWRP? before I have applied the changes?

I don't think so, unfortunately. If all else fails, you may have to start from sbf, then use this to install the updated recovery.

 

[Antiga Prime]

Well my CPU settings are default as I have have not touched them, but I'll give it a go anyways,

It resets as soon as I select Team Win Recovery.... is there a way to go back to the previous state of the TWRP? before I have applied the changes?

Thanks

I don't think so, unfortunately. If all else fails, you may have to start from sbf, then use this to install the updated recovery.

IMO, if SBF can be avoided, it should be. This is a perfectly viable option, and it doesn't sound hard at all.

 

[gatewave]

IMO, if SBF can be avoided, it should be. This is a perfectly viable option, and it doesn't sound hard at all.

It doesn't allow me to enable adb in the tools.. it just reverts back to the main page. looks like I need to go back to SBF and start from the beginning....

 

[Antiga Prime]

It doesn't allow me to enable adb in the tools.. it just reverts back to the main page...

Doesn't it always do that?

 

[T_Pratik]

Bug reprt:
After I reboot display can't be off using power button but power button gives pop up for power menu when holded.
I let display off after time out and then it works perfectly.
Any 1 having same issue...?
Sorry for bad english... hope u get my words...

 

[gatewave]

Doesn't it always do that?

Yes I tried it 20 times already but same thing, restarts when going to Team Win and revert back to the main page when going into ADB section

 

[Antiga Prime]

... and revert back to the main page when going into ADB section

Uhm, that's my point... there is no "adb" page, doesn't mean ADB isn't running. Did you check with a computer to see if ADB was running or not?

 

[prateekranka]

Had this issue too.. Took a few days for the system to settle. Give it a few days and see if it's the same for you.

Sent from my MB526 using XDA Premium 4 mobile app

Aaaaannnddd the phone rebooted while i was trying to reply to this message. I hope it does settle down as you say.

---------- Post added at 11:34 AM ---------- Previous post was at 11:30 AM ----------

Regarding the reboot issue, would you try disabling zRAM in Settings/Performance and see if it helps? zRAM is enabled by default in CM11 but from my experience in previous versions, it is not so stable and do cause ramdom reboots sometimes. Since this part of code in kernel hasn't been touched when we move on to 4.4, I guess the problem is still there.

I just did that. Hopefully that sorts the issue out Thanks

 

[Lord_Flaya]

After flashing tether fix my defy reboots like crazy. Totally random and not reproduceable. Forced me to factory reset as I currently don't have access to my .zip on the PC. Now I have 2 battery icons in status bar, no WiFi and trolls running all over my defy. Will restart from sbf to fix this issue. If a helpful soul would be kind enough, please pm the instructions for logcat and dmesg for further use and debugging.

Sent from my MB526 using XDA Premium 4 mobile app

 

[hrk]

If you are able to get a remote shell (which is probasbly the case given that you see the bootanimation) you might just - or just not - catch a whiff of what's ailing the device by 'running a cat on the kernel log' (imagine how that sounds to someone who knows neither about unix commands nor operating system telemetry...)

# cat /proc/kmsg

Would it be useful to get such a log? Maybe I was misunderstood, but after the bootanimation I get the booted ROM ... I wasn't talking about bootloops but about the reboot-to-recovery issue on MB525, after Antiga Prime suggested that it could be due to an incomplete wipe.

 

[bone101]

I got the reboot into bootmenu/recovery and also the adb option inside the bootmenu fixed on my device now: I just had to replace

export PATH=/sbin:/system/xbin:/system/bin
with
export PATH=/sbin

in /system/bootmenu/script/_config.sh

It looks like the lookup path for the executables was messed up somehow. I have no explanation why this seems to affect MB525 devices only, but maybe someone else has

As i know the separation of commands are ;
So replace those : with ;
in

PATH=/sbin:/system/xbin:/system/bin[/FONT]

Sent from my MB525 using xda app-developers app

 

[dkv2222]

After flashing tether fix my defy reboots like crazy. Totally random and not reproduceable. Forced me to factory reset as I currently don't have access to my .zip on the PC. Now I have 2 battery icons in status bar, no WiFi and trolls running all over my defy. Will restart from sbf to fix this issue. If a helpful soul would be kind enough, please pm the instructions for logcat and dmesg for further use and debugging.

Sent from my MB526 using XDA Premium 4 mobile app

As for the two battery icons, you must be using gravity box or xblast which is overlapping with the stock icon and hence, the two batteries.

Sent from my MB526 using Tapatalk

 

[abhinavvaidya90]

same herer

 

[coolshahabaz]

After flashing tether fix my defy reboots like crazy. Totally random and not reproduceable. Forced me to factory reset as I currently don't have access to my .zip on the PC. Now I have 2 battery icons in status bar, no WiFi and trolls running all over my defy. Will restart from sbf to fix this issue. If a helpful soul would be kind enough, please pm the instructions for logcat and dmesg for further use and debugging.

Sent from my MB526 using XDA Premium 4 mobile app

For logcat n dmesg stuff follow this

https://www.dropbox.com/s/l9uocet6dia6lfp/how-to-debug.txt

D5+/cm11/1.2GHz.
Sent from Tapatalk app

 

[slimshady76]

Bug reprt:
After I reboot display can't be off using power button but power button gives pop up for power menu when holded.
I let display off after time out and then it works perfectly.
Any 1 having same issue...?
Sorry for bad english... hope u get my words...

That's normal, as the kernel is really busy doing stuff. Give it a minute or two and it will settle down and the screen will turn off automatically.

 

[irekd]

As i know the separation of commands are ;
So replace those : with ;
in

PATH=/sbin:/system/xbin:/system/bin[/FONT]

Good point. Thanks. I've changed colons to semicolons and it started to work (reboot to recovery). But strange thing is that on linux, the proper PATH separation sign is actually colon sign ( : ) and not semicolon ( ; ) according to the common knowledge, which I can back up with Wikipedia: http://en.wikipedia.org/wiki/PATH_(variable)
The more strange thing is that colon works on Defy+ and doesn't work on Defy.

 

[coolshahabaz]

Good point. Thanks. I've changed colons to semicolons and it started to work (reboot to recovery). But strange thing is that on linux, the proper PATH separation sign is actually colon sign ( : ) and not semicolon ( ; ) according to the common knowledge, which I can back up with Wikipedia: http://en.wikipedia.org/wiki/PATH_(variable)
The more strange thing is that colon works on Defy+ and doesn't work on Defy.

And v use ( ; ) in windowz to separate path

Sent from my P300(Funbook) using Tapatalk