Database Users

Cannot Load KITKAT 4.4 on my defy + (MB526) ?? Help me pls !!

hello here all , :fingers-crossed:
i have my defy + moded and rooted one, where i was using cm 10 Jb 4.3.2 running smoothly on it . As soon as Kitkat was released by QURAX i made a chech thro ..many threads over here at forum. Lots were posted like only for testing and not for common usage. Though i put update in my SD card and also update 10.1 V4.4 on it.
Rebooted > Entered CW mode Flashed with new update it said it cannot not be done and signature failure > also i made a try with 10.1 directly it made a start and stopped all of sudden. It has cleaned all my data though i had back up of them . Well my doubt is how to properly do it all once again from first .Now i've flased it with GB2.3.6 MB526 firm ..

kartrikpal said:
hello here all , :fingers-crossed:
i have my defy + moded and rooted one, where i was using cm 10 Jb 4.3.2 running smoothly on it . As soon as Kitkat was released by QURAX i made a chech thro ..many threads over here at forum. Lots were posted like only for testing and not for common usage. Though i put update in my SD card and also update 10.1 V4.4 on it.
Rebooted > Entered CW mode Flashed with new update it said it cannot not be done and signature failure > also i made a try with 10.1 directly it made a start and stopped all of sudden. It has cleaned all my data though i had back up of them . Well my doubt is how to properly do it all once again from first .Now i've flased it with GB2.3.6 MB526 firm ..
Click to expand...
Click to collapse
From CM10 flash the updated recovery from the 4.4 thread and then flash KitKat.
Sent from my Nexus 7 using Tapatalk

kartrikpal said:
hello here all , :fingers-crossed:
i have my defy + moded and rooted one, where i was using cm 10 Jb 4.3.2 running smoothly on it . As soon as Kitkat was released by QURAX i made a chech thro ..many threads over here at forum. Lots were posted like only for testing and not for common usage. Though i put update in my SD card and also update 10.1 V4.4 on it.
Rebooted > Entered CW mode Flashed with new update it said it cannot not be done and signature failure > also i made a try with 10.1 directly it made a start and stopped all of sudden. It has cleaned all my data though i had back up of them . Well my doubt is how to properly do it all once again from first .Now i've flased it with GB2.3.6 MB526 firm ..
Click to expand...
Click to collapse
-" and signature failure". Also disable MD5 verification if you didn't copy the MD5 file to your SDCard
To succesfully install gapps I had to remove some ringtones and fonts.

hotdog125 said:
From CM10 flash the updated recovery from the 4.4 thread and then flash KitKat.
Click to expand...
Click to collapse
Hi hotdog, i was at this point before, but i still wasn't able to apply the cm11 rom after that. Here is what i did:
I rebooted into 2nd-init, then chose recovery, then custom recovery. There i selected apply zip file from sd, then chose the update-recovery [1], then i rebooted and again went from 2nd-init to custom recovery (by the way, i was expecting it to be a different recovery, but it was the same..) then applied the latest cm11 zip, but that failed with set_metadata_recursively, which (after reading a little about it) seems to still be the problem that should be solved by applying the update-recovery.zip, right?
[1]: http://defy.bytekiste.de/cm11-nightly-defy+/update-recovery.zip

tmcookies said:
Hi hotdog, i was at this point before, but i still wasn't able to apply the cm11 rom after that. Here is what i did:
I rebooted into 2nd-init, then chose recovery, then custom recovery. There i selected apply zip file from sd, then chose the update-recovery [1], then i rebooted and again went from 2nd-init to custom recovery (by the way, i was expecting it to be a different recovery, but it was the same..) then applied the latest cm11 zip, but that failed with set_metadata_recursively, which (after reading a little about it) seems to still be the problem that should be solved by applying the update-recovery.zip, right?
[1]: http://defy.bytekiste.de/cm11-nightly-defy+/update-recovery.zip
Click to expand...
Click to collapse
I think flashing CM10.2, then flashing the update recovery zip and finally the CM11 zip will help.
Sent from my Nexus 7 using Tapatalk

kartrikpal said:
hello here all , :fingers-crossed:
i have my defy + moded and rooted one, where i was using cm 10 Jb 4.3.2 running smoothly on it . As soon as Kitkat was released by QURAX i made a chech thro ..many threads over here at forum. Lots were posted like only for testing and not for common usage. Though i put update in my SD card and also update 10.1 V4.4 on it.
Rebooted > Entered CW mode Flashed with new update it said it cannot not be done and signature failure > also i made a try with 10.1 directly it made a start and stopped all of sudden. It has cleaned all my data though i had back up of them . Well my doubt is how to properly do it all once again from first .Now i've flased it with GB2.3.6 MB526 firm ..
Click to expand...
Click to collapse
Get to CM10.2 again, install update-recovery.zip, REBOOT (without any wipe), get into recovery again and install CM11 and GApps. :cyclops:

[Q] cant install android 4.4 on my defy plus

Hi,
My phone detail --
MB526, have android 4.1.2 and have rom -CM-X MIG 2.02
I have two issues :-
1. my wifi disconnects after some time and i have to disable it for long time and then enable it to work ,so any way to solve it -on my other phone
there is no issue about wifi atall.
2.I been trying to install kitkat 4.4 on my defy plus but always fails to do in recovery with message like this:--
error in /sdcard/.....zip, installation aborted"
tried both recoveries but now on touch TWRP -- any idea ?
Thanks

vaibhavm said:
Hi,
My phone detail --
MB526, have android 4.1.2 and have rom -CM-X MIG 2.02
I have two issues :-
1. my wifi disconnects after some time and i have to disable it for long time and then enable it to work ,so any way to solve it -on my other phone
there is no issue about wifi atall.
2.I been trying to install kitkat 4.4 on my defy plus but always fails to do in recovery with message like this:--
error in /sdcard/.....zip, installation aborted"
tried both recoveries but now on touch TWRP -- any idea ?
Thanks
Click to expand...
Click to collapse
I tooo faced the same problem at the beginning with cm11 (cm-11-20140117-NIGHTLY-mb526) by quarx, though I was able to install cm11(cm-11-20131229-NIGHTLY-mb526) by quarx successfully.... Im a noob to this flashing stuff still managed and understood a bit of this procedure... I believe I read this some where on this forum that if you want to install ***cm11 (cm-11-20140117-NIGHTLY-mb526)*** then you need to go back to the custom rom first then from there you can install , though I'm not 100% Sure and afraid to do any experimentation with my Defy+.... As of now Im on
"Android 4.3.1"
Kernel 2.6.32.9-Aerokernel
10.2-20131030-NIGHTLY-mb526
I am facing almost the same problems as yours "Installation failed" as if there is a problem with the zip file which I'm sure of that isnt the case :/
Please somebody help the noobs...!!!
Thank you.

imdroid87 said:
I tooo faced the same problem at the beginning with cm11 (cm-11-20140117-NIGHTLY-mb526) by quarx, though I was able to install cm11(cm-11-20131229-NIGHTLY-mb526) by quarx successfully....
Thank you.
Click to expand...
Click to collapse
Did you update recovery?
Link for that is in OP of http://forum.xda-developers.com/showthread.php?t=2515036

becer said:
Did you update recovery?
Link for that is in OP of http://forum.xda-developers.com/showthread.php?t=2515036
Click to expand...
Click to collapse
Yes I did the recovery Update and then rebooted and then tried installing cm11 (cm-11-20140117-NIGHTLY-mb526) but unfortunately it failed "Aborted"

imdroid87 said:
Yes I did the recovery Update and then rebooted and then tried installing cm11 (cm-11-20140117-NIGHTLY-mb526) but unfortunately it failed "Aborted"
Click to expand...
Click to collapse
Try maybe installing from scratch (starting with original sbf).
I reinstalled Kitkat on my Defy+ tonight - sbf, rooted sbf, 2ndInit, cm-10-20131030, recovery update and then 140120.

becer said:
Try maybe installing from scratch (starting with original sbf).
I reinstalled Kitkat on my Defy+ tonight - sbf, rooted sbf, 2ndInit, cm-10-20131030, recovery update and then 140120.
Click to expand...
Click to collapse
Buddy "becer" can u please guide me step wise to go back to the Stock Rom then 2init what ever it is I dont understand a thing
I know what stock Rom is but don't know how to degrade to the stock rom from 4.3.1 and how to install this 2init thing
would be a great help if you could guide me through the procedure step wise
Thank You.

1. root with Framaroot http://forum.xda-developers.com/showthread.php?p=37508806
2. Install 2nd init http://forum.xda-developers.com/showthread.php?p=12837303
3. Update recovery with this http://forum.xda-developers.com/showthread.php?p=48501247
4. Install CM11
Sent from my MB526 using Tapatalk

cyrusct82 said:
1. root with Framaroot http://forum.xda-developers.com/showthread.php?p=37508806
2. Install 2nd init http://forum.xda-developers.com/showthread.php?p=12837303
3. Update recovery with this http://forum.xda-developers.com/showthread.php?p=48501247
4. Install CM11
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
Buddy Im already running cyanogenmod on my defy+ and in the second link what you gave for installing the 2ndinit Recovery it says:
DO NOT INSTALL THIS IF ARE YOU ALREADY RUNNING CYANOGENMOD. That ROM already has bootmenu pre-installed, and you'll probably end up having to flash an SBF file to recover your phone.
NOTE: You need ROOT installed on your Defy to use this application.
What should I do ???

I will try from start by using original sbf file using RSD and then CM11 and updating recovery after that Kitkat ,btw can you mention which ROM you tried because i tried these 2 earlier --> omni-4.4.2-20140117-mb526-HOMEMADE .zip and AOSPA 4.0+ PARANOIDANDROID [beta]
Kitkat 4.4.2 KOT49H android-4.4.2_r1.
Also can some1 help me with my wifi frequently disconnection problem too please .

vaibhavm said:
I will try from start by using original sbf file using RSD and then CM11 and updating recovery after that Kitkat ,btw can you mention which ROM you tried because i tried these 2 earlier --> omni-4.4.2-20140117-mb526-HOMEMADE .zip and AOSPA 4.0+ PARANOIDANDROID [beta]
Kitkat 4.4.2 KOT49H android-4.4.2_r1.
Also can some1 help me with my wifi frequently disconnection problem too please .
Click to expand...
Click to collapse
I tried this
Mokee
"MK43.1-jordanplus-201312040138-NIGHTLY"
with Gapps
gapps-jb+-20130730_defy-minimal
and
update-recovery
CM11 by Quarx
"cm-11-20131229-NIGHTLY-mb526"
with Gapps
1-16_GApps_Standard_4.4.2_signed
They both worked for me but unable to install the latest one.... I'm trying the method just mentioned by the senior member but unable to root again using framaroot as its showing me this error
"Half-Success :-/ ... system partition is read-only, use local.prop trick. Reboot your device and use adb to see if it run as root"
I don't know what to do now :silly:

imdroid87 said:
I tried this
Mokee
"MK43.1-jordanplus-201312040138-NIGHTLY"
with Gapps
gapps-jb+-20130730_defy-minimal
and
update-recovery
CM11 by Quarx
"cm-11-20131229-NIGHTLY-mb526"
with Gapps
1-16_GApps_Standard_4.4.2_signed
They both worked for me but unable to install the latest one.... I'm trying the method just mentioned by the senior member but unable to root again using framaroot as its showing me this error
"Half-Success :-/ ... system partition is read-only, use local.prop trick. Reboot your device and use adb to see if it run as root"
I don't know what to do now :silly:
Click to expand...
Click to collapse
Mine sbf is rooted alredy so maybe try it first then go to CM10 .
its DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar
downloaded it earlier from here only.

I have tried Mokee, but direct return to Quarx compilation made big stability problems too. Solution was to flash with original rom, then rooted one, 2ndInint and Quarx cm10, then cm11.
As I had Android 2.3.6 (3.4.5.1 - 231), I used these roms - http://forum.xda-developers.com/showthread.php?t=1542956.
It is very important to wipe data and cache just after first, original flash - otherwise you will have infinite boot loop and cannot run phone.
Look at http://forum.xda-developers.com/showthread.php?t=966537 too.

becer said:
I have tried Mokee, but direct return to Quarx compilation made big stability problems too. Solution was to flash with original rom, then rooted one, 2ndInint and Quarx cm10, then cm11.
As I had Android 2.3.6 (3.4.5.1 - 231), I used these roms - http://forum.xda-developers.com/showthread.php?t=1542956.
It is very important to wipe data and cache just after first, original flash - otherwise you will have infinite boot loop and cannot run phone.
Look at http://forum.xda-developers.com/showthread.php?t=966537 too.
Click to expand...
Click to collapse
Im phone is f***** , what I did is install this framaroot and installed rootchecker..... I tried to do the rooting using "installsu" and then clicked Gilmo and it gave me this message:
“Half-Success :-/ … system partition is read-only, use local.prop trick. Reboot your device and use adb to see if it runs as root”
then I restarted my phone and check with root checker and found its saying its saying Root access successful and then I wondered which I suppose I shudnt have wondered :crying: to user framaroot and do the "unroot" and again restarted , and now after restart I tried to do the regular thing wipe cache ,Dalvik , Data and the phone is not even mounting them its sayin
E: Can't mount /cache/recovery/command etc
Im able to open the android 4.1.2 (Jb - quarx)
but not able to install a thing in my internal memory coz I messed up bad with the partition table bad:crying:
I tried to fix it through this
http://forum.xda-developers.com/showthread.php?t=1759558&highlight=status+0
but no luck :/

I been able to flash and run cm-10.2-20140120-NIGHTLY-mb526.zip thts-- android 4.3 ,so do factory reset and go here http://quarx2k.ru/roms/defy-cm10.2/ --get latest build .
my problem is only wifi disconnects frequently -seems on this working fine ,will check it for few days ,anyway 4.4 will still have bugs so better be on some lower version.

For the opening post: the first issue is a known bug in 4.4, I did not know it is wrong even in 4.1...

vaibhavm said:
I been able to flash and run cm-10.2-20140120-NIGHTLY-mb526.zip thts-- android 4.3 ,so do factory reset and go here http://quarx2k.ru/roms/defy-cm10.2/ --get latest build .
my problem is only wifi disconnects frequently -seems on this working fine ,will check it for few days ,anyway 4.4 will still have bugs so better be on some lower version.
Click to expand...
Click to collapse
Oooh in that case even if I can install the latest Cm11 by Quarx then I should not be doing it as the problem your saying about the wifi getting disconnecting frequently is not acceptable :silly:
anyways just fighting with my Defy+ as of now , Installing the Stock sbf on it as I bricked the phone
So the new Question arises what CM version is more stable or can I ask whose performance is Better in terms of speed.... As I don't mind with Features but I dont want Lags.... Previously I installed 4.2.1 I Suppose and installed the mininal gapps and was have around 240mb free of RAM...
is that good ???
Thank you for the responses buddies :fingers-crossed:

imdroid87 said:
Oooh in that case even if I can install the latest Cm11 by Quarx then I should not be doing it as the problem your saying about the wifi getting disconnecting frequently is not acceptable :silly:
anyways just fighting with my Defy+ as of now , Installing the Stock sbf on it as I bricked the phone
So the new Question arises what CM version is more stable or can I ask whose performance is Better in terms of speed.... As I don't mind with Features but I dont want Lags.... Previously I installed 4.2.1 I Suppose and installed the mininal gapps and was have around 240mb free of RAM...
is that good ???
Thank you for the responses buddies :fingers-crossed:
Click to expand...
Click to collapse
vaibhavm I have installed this 4.4.2 Android Panroid
http://forum.xda-developers.com/showthread.php?t=2576930
[AOSPA 4.4.2 KOT49H] [Beta] Defy(+) PARANOIDANDROID 4.0+ [18/01/2014]
Working awesome fast and seems stable until now and I have gone through some reviews about it on defy+ on that forum even they are giving it positive reviews..
Check it out for sure:good::fingers-crossed:

[Q] Please help mates, I got a problem with a kernel!

Hello everybody, I was wondering if you could help me with this problem.
I got an lg g2 D802, I was on the official kit kat rom with knock code, with Dorimanx kernel 7.1, everything was ok, Im using the right baseband from kit kat, but I changed the rom to Paranoid Android new version, doing a full wipe/ clean install. But the first hours of use I noticed that my phone was overheating, so I started to read bout that, and I realize that Dorimanx kernel wasn't for PA Roms, only for stock based, so I decided to change my kernel, I wasn't sure what kind of kernel I need, so I search a bit and a page says that PA Roms was AOSP based, then I downloaded Furnace Kernel 2.5.1, AOSP version, flashed it and when the phone reboots, it repeatedly say: com. android.phone process has stopped. So technically I wasn't able to do anything. I boot into recovery again and try to flash stock kernel for kit kat, and when the phone tries to boot, an lg logo appears and say: Security error. I reboot into recovery once again and try to re- flash Dorimanx kernel, because it was late night and I wanted to sleep, so I though, just need the phone to boot and tomorrow I will change the kernel to a correct one, but when the phone tries to boot, got stuck in lg logo and the led flashing, since that, I ve been trying to flash so many kernels, included furnace stock version and cm version, with no result, I tried too cloudyfa, auxilium, stock, PAEK and nothing seems to work.
I did my backup when I flashed PA, but cause first hours seemed to be ok , I deleted it for storage reasons, so now i cant restore any backup, and I know doing a full wipe /clean install again will solve this problem, but I don't want to lose all my files and photos and stuff from years ago, and I know that is possible to flash a kernel and boot with this rom because when I flash furnace AOSP the phone turn on and show my lock screen and desktop, but the com.android.phone has stopped problem appears and don't let me do anything.
So, I ask to you: What can I do to flash the right kernel and don't lose my stuff?
Thank you for your answers and sorry for my bad English.

@Delintg2 Why don't you just flash paranoid android again? Flashing the rom changes the kernel as well

Art Vanderlay said:
@Delintg2 Why don't you just flash paranoid android again? Flashing the rom changes the kernel as well
Click to expand...
Click to collapse
Ive tried too, with no result, stuck o lg logo, and now the adb sideload say sending package and when 100% nothing happens on the phone :S

Delintg2 said:
Ive tried too, with no result, stuck o lg logo, and now the adb sideload say sending package and when 100% nothing happens on the phone :S
Click to expand...
Click to collapse
You have to flash the sideload zip when that's done. If you still can't boot into your ROM then its back to stock town for you I'm afraid. We've all been there :highfive:

Art Vanderlay said:
You have to flash the sideload zip when that's done. If you still can't boot into your ROM then its back to stock town for you I'm afraid. We've all been there :highfive:
Click to expand...
Click to collapse
Ok backing to stock :S, ty anyway m8

[Q] Stuck on boot animation -- all ROMS

My Nexus 4 was previously running 4.4.2 ... I had a modified kernel patch (done via an app and I can't remember the name of it) and it was rooted. On occasion I would pickup the phone just to find out it had shut down. I would reboot it and it would be fine for days. One day it got stuck on the boot animation. It just wouldn't pass that point. Then the battery died (I assume) so I plugged it in via USB to both wall and PC and it would not charge. I had to put in on my wireless charging pad and it charged right up .. but still would not pass the animation.
Since then I have individually flashed each file manually from the newest lolipop ROM. Tried the nexus toolkit including most of the 4.X.X stock ROMS. Did a format and erase. Booted Clockwork Recovery and installed 5.0 from sdcard. (I can access the sdcard via USB on CWM). I flashed the kernel, Radio and bootloader several times each. I tried the Cyan ROM 10.x too
After the second attempt installing 5.0 (using the toolkit) I did get "Android is upgrading ... Optimizing apps" then it hung on "starting apps" and the animation continued for hours. I have had no other success since then.
I am at a complete loss. So I turn to the experts in hope of salvation.
Any idea what I'm doing wrong or what else I should be doing?

Your emmc chip is fried.. Take the phone to a service center
Sent from my Nexus 4 using XDA Free mobile app

http://forum.xda-developers.com/showthread.php?t=2964619

Well, here's a new twist. I'm able to flash 4.2 and 4.2.2 with no problems .. but 4.3 OTA and even manual flash will reproduce the stuck on animated logo problem.
I installed a sensor app and it seems like all sensors are working fine.
I remember that I was using the franco kernel before my problems started. Maybe I have a botched kernel. But I have flashed it when I did all the ROMs did I not?
What is the earliest kernel version that is compatible with 4.3, 4.4 and 5.0?

Does anyone know why I can't flash beyond 4.2.2?
Is there a way to systematically test each .img to discover the problem?
Also, even though I have USB debugging enabled, I can't use ADB to sideload at all. I keep getting ADB was not found. I can use ADB without problems on my nexus 5.

bump

Same issue here. Could flash 4.2.2 and update with ota to 4.4.4, after that the boot animation stay's for more then an hour. Any idea how to solve this?

Just to share my own experience on similar issue..
my N4 was official Lollipop 5.0.1 unrooted & locked.
Unlocked & installed clockworkmod & latest official pa rom -> stuck in boot screen. (had done all resets etc )
full wipe & latest official CM nightly -> stuck in boot screen.
full wipe & installed full official google 4.4.4 image -> phone booted ok.
full wipe & install cwm & latest official pa rom (same as earlier) -> phone booted ok.
So my conclusion was that it had something to do with lollipop modem etc part, that didnt quite work with roms i tried to run.
BTW for some reason wasnt able to get adb sideload to work for me neither, so installed the factory images on fastboot / flash-all.bat

If you have a backup with USB debugging enabled, you could restore it and try to take a logcat while booting. This would make finding the culprit a lot easier.

PLEASE HELP! I think I messed my phone up... it won't boot...

I just recently re-rooted my OnePlus 8 Pro... Everything was a breeze as I have been doing this since 2012. Anyways I am on the latest Android 11 and flashed ElementalX Kernel 1.08... Did not realize it said Android 10! Now I am stuck in a bootloop that keeps sending me to recovery where I can pick my language. It also gives me the message (Boot Reason : fs_mgr_mount_all) "Unable to parse kernel log. For more information, adb pull/mnt/vendor/op2/rbr_log or pull op2.img... Please advise. Thank you

akinkoff85 said:
I just recently re-rooted my OnePlus 8 Pro... Everything was a breeze as I have been doing this since 2012. Anyways I am on the latest Android 11 and flashed ElementalX Kernel 1.08... Did not realize it said Android 10! Now I am stuck in a bootloop that keeps sending me to recovery where I can pick my language. It also gives me the message (Boot Reason : fs_mgr_mount_all) "Unable to parse kernel log. For more information, adb pull/mnt/vendor/op2/rbr_log or pull op2.img... Please advise. Thank you
Click to expand...
Click to collapse
Have you tried flash stock boot.img?

akinkoff85 said:
I just recently re-rooted my OnePlus 8 Pro... Everything was a breeze as I have been doing this since 2012. Anyways I am on the latest Android 11 and flashed ElementalX Kernel 1.08... Did not realize it said Android 10! Now I am stuck in a bootloop that keeps sending me to recovery where I can pick my language. It also gives me the message (Boot Reason : fs_mgr_mount_all) "Unable to parse kernel log. For more information, adb pull/mnt/vendor/op2/rbr_log or pull op2.img... Please advise. Thank you
Click to expand...
Click to collapse
Extract and flash the kernel for your firmware.
Or recovery and wipe phone, wiping system alone will not work.

There's no need to wipe the phone, fastboot flash the stock boot.img or you can use the clean slate boot.img from here: https://forum.xda-developers.com/oneplus-8-pro/development/kernel-cleanslate-1-0-0-t4096065
You should be able to boot