I read that others too have got the issue, but how to solve it's not written -.-""
I read that others too have got the issue, but how to solve it's not written -.-""
So I jumped on the bandwagon! Latest build! Latest kernel update. Phone is flying. But, my OCed values are not showing up on CPU spy. It's only showing default values! Is it just me?
Sent from my MB526 using xda app-developers app
yes but the kernel is than compatible? For example, the walter's kernel doesn't work with all other GB builds...I knew@ quarx...can u pls upload the updated kernel only. So that we can use linaro enfused kernel on other jb builds like cna,aokp or pa.???
Would be much appreciated by many ....thnx in advance!
sent from my legendary <<<defy>>>
. Don't forget to hit thanks if I ever helped u!!!!!
me too.So I jumped on the bandwagon! Latest build! Latest kernel update. Phone is flying. But, my OCed values are not showing up on CPU spy. It's only showing default values! Is it just me?
Sent from my MB526 using xda app-developers app
take "kern" from /system/bootmenu/2ndboot for update.zip@ quarx...can u pls upload the updated kernel only. So that we can use linaro enfused kernel on other jb builds like cna,aokp or pa.???
Would be much appreciated by many ....thnx in advance!
sent from my legendary <<<defy>>>
. Don't forget to hit thanks if I ever helped u!!!!!
+1So I jumped on the bandwagon! Latest build! Latest kernel update. Phone is flying. But, my OCed values are not showing up on CPU spy. It's only showing default values! Is it just me?
Sent from my MB526 using xda app-developers app
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editorTo Defy users (NOT defy+), in the about phone screen, the model name is MB526 or MB525?? if it's MB526, there's any way of edit the build.prop on bootmenu or recovery?? i have some other apps (aside from the play store) that relies on the model name...
It's MB526, but it can be changed to MB525 in build.prop successfully if you set the right permissions afterwards <= that was reported by a couple of users.To Defy users (NOT defy+), in the about phone screen, the model name is MB526 or MB525?? if it's MB526, there's any way of edit the build.prop on bootmenu or recovery?? i have some other apps (aside from the play store) that relies on the model name...
I also dislike that animation, maybe it will be optional in future builds (as it was in CM7, if I. remember correctly).3. Really don't like the CRT animation anymore and there's no easy way to turn it off (yet)
ohh, i just find out it can be done with a flashable zip (so i don't boot the phone with the incorrect device name), i'll share it when i try it (tonight)... :cyclops:It's MB526, but it can be changed to MB525 in build.prop successfully if you set the right permissions afterwards <= that was reported by a couple of users.![]()
Try this, Go in to bootmenu by pressing vol down button after u see blue LED and set default boot to 2nd boot... and reboot... u should be fine...All right...
I have done the following:
Reboot to custom recovery.
Clear Cache
Clear Davlik
Flash 10-11-12 zip
Clear Cache
Clear Davlik
Flash Update for 10-11 zip
Clear Cache
Clear Davlik
And reboot. Result is moto logo with blue led, then it quickly changes to red, and bootloops.
I've tried the same procedure with a full wipe, and the rest of the steps the same, and have tried that afore-mentioned fix.zip. Everything results in bootloop and a red led.
Can someone verify what exactly this business of removing the battery is about? I've taken it out, waited several minutes, and tried again... same result. Is there a setting I've missed in my boot settings?
Try this:All right...
I have done the following:
Reboot to custom recovery.
Clear Cache
Clear Davlik
Flash 10-11-12 zip
Clear Cache
Clear Davlik
Flash Update for 10-11 zip
Clear Cache
Clear Davlik
And reboot. Result is moto logo with blue led, then it quickly changes to red, and bootloops.
I've tried the same procedure with a full wipe, and the rest of the steps the same, and have tried that afore-mentioned fix.zip. Everything results in bootloop and a red led.
Can someone verify what exactly this business of removing the battery is about? I've taken it out, waited several minutes, and tried again... same result. Is there a setting I've missed in my boot settings?