MДЯCЦSДИT said:
This thread is to assist porting of Android 4.1 (Jellybean) to ICS devices
A good base ROM for porting: http://forum.xda-developers.com/showthread.php?t=1737849
Ramdisk diff
This is a diff file for the Jellybean ramdisk from ICS. This is from the galaxy nexus and will have to be changed for your specific device. Some notes that are not shown in the diff are that /sbin/adbd and init changed -- These are both binaries so they need to be manually taken from the jb ramdisk.
http://pastebin.com/xwCLRrT0
Files changed in /system/
This is a list of files that have changed in JB... Please check /vendor/{device vendor}/{device name}/ and[/SIZE][/SIZE] /device/{device vendor}/{device name}/ in the CM source to make sure they don't overlap... If any do, just keep your cm9 versions.
/system/app/ - Basically every apk, don't even bother copying individual changed files
/system/bin/
adb.p dumpsys.p mksh.p sdptool.p
applypatch.p fsck_msdos.p mtpd.p sensorservice.p
app_process.p gzip.p ndc.p servicemanager.p
bluetoothd.p hciattach.p netcfg.p service.p
bootanimation.p hostapd.p netd.p setup_fs.p
brcm_patchram_plus.p installd.p pand.p smc_pa_ctrl.p
bugreport.p ip6tables.p ping.p surfaceflinger.p
dalvikvm.p ip.p pppd.p system_server.p
dbus-daemon.p iptables.p racoon.p tc.p
debuggerd.p keystore.p rild.p tf_daemon.p
dexopt.p linker.p run-as.p toolbox.p
dhcpcd.p logcat.p schedtest.p vdc.p
dnsmasq.p logwrapper.p screencap.p vold.p
drmserver.p make_ext4fs.p screenshot.p wpa_supplicant.p
dumpstate.p mediaserver.p sdcard.p
NEW
atrace content e2fsck mdnsd requestsync uiautomator
/system/xbin/
dexdump.p/system/etc/apns-conf.xml.p fallback_fonts.xml.p permissions
audio_effects.conf.p gps.conf.p ppp
dhcpcd media_profiles.xml.p security
event-log-tags.p NOTICE.html.gz.p system_fonts.xml.p
NEW
audio_policy.conf media_codecs.xml security
fallback_fonts-ja.xml preferred-apps
/system/media/ & /system/fonts/ - Just take it all from jb as pretty much none is device specific.
/system/framework/ - Everything
Click to expand...
Click to collapse
credit by http://forum.xda-developers.com/showthread.php?t=1739561
wow.. interesting mate..
#stillhaven'tpcfordevelopfb0
wow...
thank you for the tutorial..
hopefully...our device still can use JB as it only minor changing on system..
i'm excited to see development will go on with CM10 or MIUI v4.1..
Hope soon we got jb rom ...
Dev is not difficult for you .
Sent from my FIH-FB0 using xda premium
hi
ooh God we are just at the level of getting a clean totally working ICS and now that the JB has come people are gona start dev on this and drop ICS i assume:victory::laugh:
Take chances, make mistakes. That's how you grow. Pain nourishes your courage. You have to fail in order to practice being brave.
Go for it guys/gals
Sent from my Desire HD using xda app-developers app
Anyone may can help the CM10 dev team to fix the camera app on Jelly Bean CM10??
Here: http://forum.xda-developers.com/showthread.php?t=1832192
I have not succesfully ported Android 4.1 Jelly Bean to our devices HELP NEEDED
Now i have one problem it's not booting
i see the Galaxy Tab 8.9 Logo after that a nexus s booting logo and the boot logo fades away really fast after that black screen on boot and not booting into Android 4.1
Any help is welcom
safariking said:
I have succesfully ported Android 4.1 Jelly Bean to our devices
Click to expand...
Click to collapse
it's not booting
Click to expand...
Click to collapse
Rrrright
If it's not booting you didn't successfully port it, so i'm wondering how someone could help you.
There is no point in trying to port it. We will have Jelly Bean source in about two weeks. If ICS drivers work with JB, like everyone seems to think, then it should be easy to make it work.
But if you just want to play with it... What kernel and which Rom are you using as base? Did you extract the boot image and use our ICS kernel and rc files in ramdisk? Did you use libs from our ICS rom?
poisike said:
There is no point in trying to port it. We will have Jelly Bean source in about two weeks. If ICS drivers work with JB, like everyone seems to think, then it should be easy to make it work.
But if you just want to play with it... What kernel and which Rom are you using as base? Did you extract the boot image and use our ICS kernel and rc files in ramdisk? Did you use libs from our ICS rom?
Click to expand...
Click to collapse
Used CM9 Nightly's and copied apps,framework,fonts and media from JB to CM9/ICS after that i have changed the updater-script and the build.prop file after that i have copied some other thing from JB to CM9/ICS!
safariking said:
Used CM9 Nightly's and copied apps,framework,fonts and media from JB to CM9/ICS after that i have changed the updater-script and the build.prop file after that i have copied some other thing from JB to CM9/ICS!
Click to expand...
Click to collapse
I would try it the other way, copy our libs to JB rom. You probably need to copy our graphics libs, egl folder and hw folder. You probably need to use JB ramdisk and copy our rc files (with our device name) to it. You should also enable adb at boot, so you can see where it hangs. Then repack the boot.img with our kernel.
poisike said:
I would try it the other way, copy our libs to JB rom. You probably need to copy our graphics libs, egl folder and hw folder. You probably need to use JB ramdisk and copy our rc files (with our device name) to it. You should also enable adb at boot, so you can see where it hangs. Then repack the boot.img with our kernel.
Click to expand...
Click to collapse
Im in the infuse forums and accidentally stumbled across this, but i have to point this out... You cannot simple take the ramdisk from another JB device and repackage it with yours. The ramdisk contains device specific information/files that differ from phone to phone.. So i dont think i need to explain what happens if you do what you suggested without making the necessary changes..
scott.hart.bti said:
Im in the infuse forums and accidentally stumbled across this, but i have to point this out... You cannot simple take the ramdisk from another JB device and repackage it with yours. The ramdisk contains device specific information/files that differ from phone to phone.. So i dont think i need to explain what happens if you do what you suggested without making the necessary changes..
Click to expand...
Click to collapse
You are correct. I was in hurry when i wrote this and i didn't think about the possibility that the person who asked possibly doesn't know that.
Hi
we are a team of devs trying to port jelly from s advance to xperia u.
when i extract the jelly system.tar i get files:
- kernel.bin.md5
- kernel2.bin.md5
- power_mangement.bin.md5
Can you please tell me if these are all three related to kernel?
Can you please tell me how to extract these kernel files, as i need to merge the "zimage" inside (?) with our ramdisk?
Or can anyone upload the boot.img from his jelly bean rom?
Thx
thebrainkafka said:
Hi
we are a team of devs trying to port jelly from s advance to xperia u.
when i extract the jelly system.tar i get files:
- kernel.bin.md5
- kernel2.bin.md5
- power_mangement.bin.md5
Can you please tell me if these are all three related to kernel?
Can you please tell me how to extract these kernel files, as i need to merge the "zimage" inside (?) with our ramdisk?
Or can anyone upload the boot.img from his jelly bean rom?
Thx
Click to expand...
Click to collapse
Someone is uploading the kernel dump iirc.
Other file is pretty self explanatory!
Sent from my GT-I9070 using xda premium
Shaaan said:
Someone is uploading the kernel dump iirc.
Other file is pretty self explanatory!
Sent from my GT-I9070 using xda premium
Click to expand...
Click to collapse
Thx,
but please explain... im used to sony file system
U want to just replace zImage In sony device? I think u need to build the kernel again :0
Sent from my GT-I9070 using xda app-developers app
I downloaded jb kernel source codes from opensource.samsung.com. When I try to build it, I stuck at error:
from arch/arm/mach-ux500/pm/suspend.c:13:
arch/arm/mach-ux500/pm/suspend.c: In function ‘ux500_suspend_init’:
arch/arm/mach-ux500/include/mach/id.h:68:13: error: inlining failed in call to always_inline ‘cpu_is_u9500’: function body not available
arch/arm/mach-ux500/pm/suspend.c:295:18: error: called from here
make[2]: *** [arch/arm/mach-ux500/pm/suspend.o] Error 1
make[2]: *** Waiting for unfinished jobs....
CC kernel/sched.o
make[1]: *** [arch/arm/mach-ux500/pm] Error 2
make: *** [arch/arm/mach-ux500] Error 2
Click to expand...
Click to collapse
Did someone succesfully build it? Or have advice to resolve this error?
A. Why change RIL?
Hey, everyone.
As a user that's been using custom roms since our bootloader was unlocked, I'm aware that some of us have some issue with telephony & mobile data (in short, RIL) - occasionally IMEI wouldn't be read on boot, which would lead to device not being registred on network. Sometimes, the network would "die" in a way - you'd get an error when trying to dial a number, and when someone would call you, they'll hear the ringing tone while your cell phone would not ring at all.
The cause of the problem seems to be some lazy coding by official CM developers/maintainers for our device. This was picked up by a developer named kholk, so he did his best to recode it properly, however it was never included into official CM device tree for reasons unknown to me (more info about the issue can be found here: http://review.cyanogenmod.org/#/c/47980/).
Kholk did include his own custom RIL into his EPRJ roms, but the roms are kinda old and have iffy baseband (which seems to be kernel issue, as he's using his own, 3.4 kernel instead of CM's 3.1 kernel in other custom roms).
So, with the help of Adam77Root, I've learned a way on how to implement EPRJ RIL into other custom roms (since I still had RIL issue with default CM RIL in 4.3 roms even) - so far I've tested it with Vanir 4.3, Carbon 4.3, Carbon 4.3.1, and few 4.2.2 roms, and I havent had ANY issues I had in CM RIL.
So, this is a tutorial to show you how you can import EPRJ RIL to any custom rom you'd like, in case you have issues with cell connection.
-this should work on any kernel and any custom rom (4.2.2+)! Tested so far, as far as kernel goes, are iodak 8/8.5, WWJB8/8b, Optimus Prime several versions, Optimus Play! 2.53.
-KK roms tested are P.A. by @dcos which has eprj ril by default, official CM nightlies and several others
-some KK roms, for some reason, don't have x3ril.smali file in their telephony-common.jar. To implement EPRJ RIL in these roms, follow the tutorial up to point 5, and skip that one, since you don't have anything to delete. After point 13, you need to do one additional thing - you need to edit ROM's build.prop settings, look for this line: "#ro.telephony.ril_class=X3RIL", and delete "#" so this line would be included in build.prop. After that, you're ready to flash. Thanks goes to @gerciolisz for the tip on the build.prop settings.
-/As of 24.01.2014. i've added another zip file which contains x3ril.smali taken from P.A. port by dcos - i'd recommend using this one for 4.4.2 roms/
-as of 11.06.2014., I've added x3ril.smali (it's in omni-v1.rar) made by adam, which is based on omni's RIL but has eprj RIL recovery. if you're on 4.4.3 kitkat rom and have issues, i suggest you give this file a try first before others
B. What's needed?
First off, you'll need a few things:
- Android Multitool from http://forum.xda-developers.com/showthread.php?t=2326604, many thanks to @Flextrick
- Read the linked topic - it's the instruction on how to use it, and in case you encounter any errors, that's the place to search for solutions
- Attached is a RAR with two files in it, X3RIL_old.smali and X3RIL_new.smali. You need only one of those - but more info about them will be in the other steps.
- Custom ROM you want to edit
- Common sense
- WinRAR & JAVA
C. How to change RIL?
Steps:
1. First step is to open the .zip of your custom ROM you want to edit, and search for system/framework/telephony-common.jar
2. Extract it to AndroidMultitool/Files, and after extract is done, delete it from .zip
3. Open Android Multitool, under Decompiling select .jar, then select telephony-common.jar in AndroidMultitool/Files, click "decompile"
4. After you're done, check if there were any errors in the Log, in AndroidMultitool main window
5. Head over to AndroidMultitool/Decompiled_jar/telephony-common/com/android/internal/telephony and look for X3RIL.smali. This is CM's RIL implemented in custom roms, which we dont need anymore, so delete it
6. Now, you need to decide wether to use X3RIL_old.smali, which is RIL from EPRJ CM10.2 built on 20130813, or X3RIL_new.smali which is RIL from EPRJ CM10.2 built on 20131007. I'm using 20131007 atm, and it's working without issues
7. When you've decided, move it back into AndroidMultitool/Decompiled_jar/telephony-common/com/android/internal/telephony and rename it to X3RIL.smali
8. Back in AndroidMultitool, under Compilin, select jar, and for folder select AndroidMultitool/Decompiled_jar/telephony-common, press "compile", and check for errors in Log
9. Output should be classes.dex file under AndroidMultitool/Compiled_jar
10. Open telephony-common.jar in AndroidMultitool/Files with WinRar - you should see META-INF folder, with classes.dex file
11. Delete classes.dex file in WinRAR
12. Move classes.dex file from AndroidMultitool/Compiled_jar to telephony-common.jar opened in WinRAR
13. Paste telephony-common.jar into system/framework inside the custom rom .zip file
14. You now have modified ROM ready to flash on our device!
D. Thank You's
Thank you's go out to @kholk for his RIL programming, @dcos for first implementing EPRJ RIL into a rom (his P.A. unofficial port for our device) different than EPRJCM10.2, @Adam77Root for his tutorial that I basically beutified and made sure is easier to understand & his modification of x3ril.smali from omni, @gerciolisz for the tip about build.prop settings, @Flextrick for his Multitool with neat GUI to extract .jar files, and all the other devs of p880 making our device worth every dime I've spent on it.
Flying_Bear said:
Kholk did include his own custom RIL into his EPRJ roms, but the roms are kinda old and have iffy baseband (which seems to be kernel issue, as he's using his own, 3.4 kernel instead of CM's 3.1 kernel in other custom roms).
Click to expand...
Click to collapse
Dude, i think you missed out the clarification for the users on whether or not they need to use the EPRJ Kernel and if anykernel will still work or normal kernels will work etc. Because your bound to have the first person to ask a question will either be, "How do i declare java paths" and "Will 'kernel name here' work with it", this isnt me asking, more of an fyi post (Y)
I do apologize about it, but saves you the time and effort of answering the question every day
MOD EDIT: watch your language please.
penguin449 said:
Dude, i think you missed out the clarification for the users on whether or not they need to use the EPRJ Kernel and if anykernel will still work or normal kernels will work etc. Because your bound to have the first person to ask a question will either be, "How do i declare java paths" and "Will 'kernel name here' work with it", this isnt me asking, more of an fyi post (Y)
I do apologise about it, but saves you the time and effort of answering the question every day
Click to expand...
Click to collapse
np, thanks for the tip. i'll add in OP that it works with any kernel
MODERATOR EDIT: @penguin449 watch your language
I flashed Vanir nightly 171013 with Optimus Prime 2.70 kernel and telephony was completely disabled. I was not able to find or register to the mobile network. I tried modifying the RIL file as explained in this post; initially with the "new" file which didn't seem to solve the problem (still didn't get signal) but I didn't wait I immediately tried flashing the ROM with the "old" RIL instead. Initially there was no signal although I was able to find networks, but after a reboot the phone finally managed to connect to the mobile network.
I'm not sure whether it would've worked after a reboot with the "new" but I'm guessing if it's working with the "old" RIL I got nothing to worry about right?
Vanir is 4.3.1 while OP is for 4.3, i think thats your problem. Different RIL would not help in that case. Flash Anykernel version of OP, or find a version repacked with 4.3.1 ramdisk. Good luck!
Flying_Bear said:
Vanir is 4.3.1 while OP is for 4.3, i think thats your problem. Different RIL would not help in that case. Flash Anykernel version of OP, or find a version repacked with 4.3.1 ramdisk. Good luck!
Click to expand...
Click to collapse
As far as I understood, the 171013 version did not have the RamDisk issue so I figured the CM10.2 version of Optimus Prime kernel should've worked correctly?
So I get it from you that if I flash the original rom with the AnyKernel version of OP it should work fine? (no need for any RIL modifications?)
Yep, anykernel versions of all our kernels xcept iodaks should work on any android version without any modifications.
Is there a way to do this with Linux?
If not, how about uploading modified telephony-common.jar for CM ROMs?
I tried just replacing the whole telephony-common.jar file but I couldn't send or receive any messages. Everything else seemed to work though.
Sent from my LG-P880 using Tapatalk
MilkyJoePD said:
Is there a way to do this with Linux?
If not, how about uploading modified telephony-common.jar for CM ROMs?
I tried just replacing the whole telephony-common.jar file but I couldn't send or receive any messages. Everything else seemed to work though.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
not sure really, since i havent worked on linux systems.
and i dont think telephony-common.jar is universal for all roms (i might be mistaken though), so there's no use to upload it. however, if you want, upload your original telephony-common.jar file here and i'll do my best to mod it for you!
Flying_Bear said:
not sure really, since i havent worked on linux systems.
and i dont think telephony-common.jar is universal for all roms (i might be mistaken though), so there's no use to upload it. however, if you want, upload your original telephony-common.jar file here and i'll do my best to mod it for you!
Click to expand...
Click to collapse
I meant it would be a good idea to have a place to download the modified files for specific ROMs.
Here's the (unmodified) file for Vanir.
https://app.box.com/s/embcq9kuemfdkdb1qw63
Thanks.
Sent from my Optimus 4X HD using Tapatalk
MilkyJoePD said:
I meant it would be a good idea to have a place to download the modified files for specific ROMs.
Here's the (unmodified) file for Vanir.
https://app.box.com/s/embcq9kuemfdkdb1qw63
Thanks.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
well, we have way too much roms for me to download each one and replace the RIL ^^
anyway, here's your modified telephony-common ^^ enjoy!
Flying_Bear said:
well, we have way too much roms for me to download each one and replace the RIL ^^
anyway, here's your modified telephony-common ^^ enjoy!
Click to expand...
Click to collapse
I suppose there is a lot.
I'll test the Vanir one and report back.
If it works then there's a start. I can send messages so it works so far. The only thing keeping me from staying on a CM ROM is the random signal loss.
Sent from my Optimus 4X HD using Tapatalk
MilkyJoePD said:
I suppose there is a lot.
I'll test the Vanir one and report back.
If it works then there's a start. I can send messages so it works so far. The only thing keeping me from staying on a CM ROM is the random signal loss.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
check it out, this should fix that issue completely. and report when you have time ^^
Flying_Bear said:
check it out, this should fix that issue completely. and report when you have time ^^
Click to expand...
Click to collapse
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
In CM ROMs I get crazy data switches from 3g to E and G. Everything is good so far. Time will tell...
Sent from my Optimus 4X HD using Tapatalk
---------- Post added at 01:22 AM ---------- Previous post was at 01:08 AM ----------
penguin449 said:
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
Click to expand...
Click to collapse
If you can then that would be great. A download for each CM ROM would open up custom ROMs like never before.
Sort out the SD card/internal memory paths and stock ROMs would be not worth installing.
Sent from my Optimus 4X HD using Tapatalk
penguin449 said:
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
Click to expand...
Click to collapse
if you've got the time and the will, be my guest - however, i don't think it's quite worth it. Not many people have this issue, and those that do would be better off fixing it by themselves then downloading aged nightlies for the rom they're looking for.
MilkyJoePD said:
In CM ROMs I get crazy data switches from 3g to E and G. Everything is good so far. Time will tell...
Click to expand...
Click to collapse
hm, switches from 3g to 2g seems to show that there is a bad connection where you're at. try enabling 2g only or 3g only in custom rom options or quick tiles, most roms support it these days. that should save your battery for few more %.
Just wanted to say that since replacing the file I haven't had to reboot once to get SMS or network to work.
That's over a month, whereas I was having to reboot about every 2 days.
The G/3G switching has improved, but still more sensitive than stock.
Sent from my Optimus 4X HD using Tapatalk
hey what if.... there is no x3ril.smali?XD there is only ril.smali or many others
edit: its ok there just x3ril was missing
I'm on a odexed ROM (mokee 4.2.2 release) so I don't know what to do with classes.dex file multitool generates.It was meant to be used for deodexed telephony-common.jar files.So I tried these steps:
1_)deodex the ROM (using deodexer 4.3),
2_)implent RIL
3_)odex the ROM(using universal odexer 6.3.1) again which I failed to do as something was wrong with decompiling before odexing.This is probably happening due to deodex process.
I got bootloop after odexing the ROM.So I'm curious if there is a way to do this on an odexed jar file without having to deodex first.
I also tried to simply delete the odex & jar file and replace it with deodexed and eprj RIL implented jar file but the rest of the ROM was odexed so it gave me a bootloop.
I don't know much about these stuff, but I did my best searching for a solution and I'm out of ideas.All I want is to have an odexed rom with EPRJ RIL implented, I'd appreciate any help
ottomanhero said:
I'm on a odexed ROM (mokee 4.2.2 release) so I don't know what to do with classes.dex file multitool generates.It was meant to be used for deodexed telephony-common.jar files.So I tried these steps:
1_)deodex the ROM (using deodexer 4.3),
2_)implent RIL
3_)odex the ROM(using universal odexer 6.3.1) again which I failed to do as something was wrong with decompiling before odexing.This is probably happening due to deodex process.
I got bootloop after odexing the ROM.So I'm curious if there is a way to do this on an odexed jar file without having to deodex first.
I also tried to simply delete the odex & jar file and replace it with deodexed and eprj RIL implented jar file but the rest of the ROM was odexed so it gave me a bootloop.
I don't know much about these stuff, but I did my best searching for a solution and I'm out of ideas.All I want is to have an odexed rom with EPRJ RIL implented, I'd appreciate any help
Click to expand...
Click to collapse
unfortunately, i encountered the same issue, and it's beyond my knowledge on what to do with odexed roms. i bypassed the issue by using a nightly which came after the stable was released (not sure if there are any for mokee though)
please can annyone help me or teach me how to finish up this cm11 source from surdu petru to get this working or can annyone start this project with cm12.1
i think this device need cm because it is a great device and emui gives not enough settings to use your device like you would do it with cm...
here is his data; github.com/surdupetru/cm11-p7
sry but icant post links yet
@surdu_petru
:crying::crying::crying:
Here's the official Huawei source for the kernel: http://emui.huawei.com/en/plugin.php?id=hwdownload&mod=detail&mid=71
I'd love to help, but I only have a ****ty laptop, so building CM would take a week or so...
Best bet is to try and base it on CM11 for P6: https://github.com/surdupetru/cm11-p6
tinyXperia said:
Here's the official Huawei source for the kernel: http://emui.huawei.com/en/plugin.php?id=hwdownload&mod=detail&mid=71
I'd love to help, but I only have a ****ty laptop, so building CM would take a week or so...
Best bet is to try and base it on CM11 for P6: https://github.com/surdupetru/cm11-p6
Click to expand...
Click to collapse
I took a look to Surdu's files but I decided to make the files based on my own device (P7L10). I've been trying for almost 1 week to build the source but without success on Mac's environment (also downloading the source some couples of time). Now I'm using a virtual machine based on the latest version of Ubuntu and it seems like it's compiling. Now I have to investigate how I'd use the original kernel (downloaded from Huawei's website) to put it on the build.
My repo's: https://github.com/nirodg/HuaweiAscendP7L10
Simply use prebuilt kernel. Extract zImage from boot.img
Kostyan_nsk said:
Simply use prebuilt kernel. Extract zImage from boot.img
Click to expand...
Click to collapse
is this because of the poor quality of the released kernel sources ?
l.capriotti said:
is this because of the poor quality of the released kernel sources ?
Click to expand...
Click to collapse
You'll waste a time to fix all compilation errors and as result you'll get the same stock zImage as prebiult one. So what's the point?
maybe some advanced features can be implemented with the kernel sources, but if the stock kernel is ok for proper CM, that's the easiest path
... and your Ascend P6S / P7 K-Tuned Kernel is exactly what I was referring to
Finally after some hard days trying to compile it finally I did it buut I don't know why the .zip file it's not created. Is strange because I didn't have any error the last time I tried to compile it.
l.capriotti said:
... and your Ascend P6S / P7 K-Tuned Kernel is exactly what I was referring to
Click to expand...
Click to collapse
Looks interesting, I'm gonna take a look.
edit: I have the zip file, but when I try to flash the phone TWRP says me that for some reason can not be flashed, without any kind of error code. I leave the recovery.log under
Installing '/sdcard/Android/cm-11-20150613-UNOFFICIAL-hwp7.zip'...
Checking for MD5 file...
MD5 matched
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Android/cm-11-20150613-UNOFFICIAL-hwp7.zip'
Error flashing zip '/sdcard/Android/cm-11-20150613-UNOFFICIAL-hwp7.zip'
Updating partition details...
Iata backup size is 1453MB,
Click to expand...
Click to collapse