Related
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)
Hello guys:laugh:
I searched every forum thoroughly but didn't found a proper and working solution for Xperia devices
I am trying to make a custom ROM from stock using dsixda kitchen
I used stock 12.1.A.201 as the base ROM
I believe that it's either the updater script error or kernel probelm as I am using stock kernel and my zip is like this
Data
META-INF
system
boot.img
check_data_app
Click to expand...
Click to collapse
This happens when rom is created
De-odexed it rooted it and added X-Reality engine and created the rom
First on installing I got error of status 0 so I changed my update binary file from same de-odexed version from this link http://forum.xda-developers.com/showthread.php?t=2704312 by @dipesh1502 (thanks to him for that awesome rom)
Next I am getting error status 7
ROM Starts flashing then it comes to this part
formatting system bla bla
expected 5 args got 3
Click to expand...
Click to collapse
something like that and then it stops on error status 7
here is the updater-script please have a look. I really want to create this ROM. Please help
Updater-Script Download
here is my build prop build.prop download
Help guys please I'll be highly grateful
My device is C5302 rooted and unlocked bootloader with 12.1.A.205 stock kernel
EDIT : Got past the error status 7 now ROM gets installed
But unfortunately now it ends in a bootloop :/ Got stuck on Sony splash logo and then reboots constantly :/
Had a nandroid backup ready x)
Had to flash the ftf file over and over again. :/
Phone is allright just want to catch this error of bootloop.
I changed kernel with the dipesh1502's ROM but still no luck. Modified Updater script but still no luck. help me I am soo confused and screwed!! :'( :'(
My new Updater-Script
There's a HUGE difference in creating boot animations and creating a ROM.
Don't expect to teach yourself how to make a ROM in just a few days.
It takes, weeks, months, years...
If you're mainly planning to make some exterior changes, which I think you're currently doing, I would focus on making complete themes and not ROMs.
People are not waiting for a ROM which is already available but that looks somewhat different and maybe has some extra or removed apps.
Regarding your problem, I will not be able to help you since I don't have that kind of knowledge.
Anyway, good luck!
Gamm86 said:
There's a HUGE difference in creating boot animations and creating a ROM.
Don't expect to teach yourself how to make a ROM in just a few days.
It takes, weeks, months, years...
If you're mainly planning to make some exterior changes, which I think you're currently doing, I would focus on making complete themes and not ROMs.
People are not waiting for a ROM which is already available but that looks somewhat different and maybe has some extra or removed apps.
Regarding your problem, I will not be able to help you since I don't have that kind of knowledge.
Anyway, good luck!
Click to expand...
Click to collapse
Thanks for the reply.
Yeah I know that it's not easy to create ROM and also it takes a lot of time. I am ready to give it a shot
I am just making some small changes just for my sake I'll be using this ROM personally for my own use I know that there are a thousand times better ROM's than mine
Anyway glad you considered my probelm.
Bootloop can be cause by:
- Wrong permissions
- Corrupt installation
It is nice if you collect either the last_ksmg or logcat when bootlooping. (if possible)
~~Regard
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
But first:
Share me the .zip you have created perhaps I can take a small look
~~ Regards
mrjraider said:
Bootloop can be cause by:
- Wrong permissions
- Corrupt installation
It is nice if you collect either the last_ksmg or logcat when bootlooping. (if possible)
~~Regard
Click to expand...
Click to collapse
Thanks for the reply
Can you please have a look at my new updater-script and tell me what is wrong?
I will surely try to get logcat but before that if you can just analyze this updater-script and pinpoint the mistakes it'll make my work a lot easier.
Thanks in advance :good:
Sent me the entire .zip file instead (but start with updater-script)
~~Regards
mrjraider said:
Sent me the entire .zip file instead (but start with updater-script)
~~Regards
Click to expand...
Click to collapse
Sure thing I'll
I am compressing it to maxium extent using KGB archiver and it'll become around 10~20 mb only
It's still compressing so it'll take some time before it reaches it's max compression.
I'll surely send you asap
Hello to all guys , I just got this fantastic Lenovo phablet , but I do not like the translation and Vibe UI , I want to find a pure Android rom . I know that almost certainly there are devices that have the Lenovo compatible roms . Can anyone help me out ? :crying::crying::crying:
I have the same problem, I just changed to new version of VibeUI and had some problems with google apps HELP!
I'm pretty sure as this phone is, new rooting and roms are still being developed. Be patience.. or learn to make one yourself
To those who find this thread do be careful! I've already seen posts about people who have bricked this phone trying to root it.
Got the same phone. Liking the layout etc. Not the official VIBE UI rom.
It's set to English, but still finding Chinese icons/text everywhere.
Since I don't speak/read Chinese; issue...
Also sometimes laggy, due to lots of processes/apps running in the background, which can not be deleted or stopped.
Looking forward to when the community embraces this phone, and stock Android ROMS will be available on short term.
It's a (edit: potential!) flag-ship killer, in my eyes...
Hi,
I am trying to port cm12 to this device. It is the first time I am doing although I have previously created custom ROMs by editing system.img, so I am a noob.
I managed to get a stock rom: K50-T5_USR_ST1516_5.654.1_1504152228_MP6V3_CN.rar.
I have slightly modified build/tools/device/mkvendor.sh to be able to work with mediatek files which have a 512 bytes extra header.
I've triedt to create a recovery but I am not sure if it will work as I have some errors in the output
./build/tools/device/mkrecoveryzip.sh /home/vagrant/android/system/out/target/product/aio_otfp /home/vagrant/android/system/out/host/linux-x86/framework/signapk.jar
cp: cannot stat ‘/home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/recovery/root/etc’: No such file or directory
cp: cannot stat ‘/home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/recovery/root/sbin’: No such file or directory
cp: cannot stat ‘/home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/recovery/root/res’: No such file or directory
cp: cannot stat ‘/home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/system/bin/updater’: No such file or directory
zip -ry /home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/utilities/unsigned.zip . -x *\[* *\[\[*
adding: META-INF/ (stored 0%)
adding: META-INF/com/ (stored 0%)
adding: META-INF/com/google/ (stored 0%)
adding: META-INF/com/google/android/ (stored 0%)
adding: META-INF/com/google/android/updater-script (deflated 51%)
Error: Unable to access jarfile /home/vagrant/android/system//home/vagrant/android/system/out/host/linux-x86/framework/signapk.jar
Recovery FakeFlash is now available at /home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/utilities/update.zip
Click to expand...
Click to collapse
Should I copy anything from boot or recovery's ramdisk?
You can find attached the information I've been able to collect (info.txt and build.prop.txt) and build.log which was in a folder in the stock ROM.
Thanks
One Chinese port AOSP to K3-Note.
Its can be daily use and without any bug now. If somebody need it. Just try it.
http://pan.baidu.com/share/link?shareid=2842642895&uk=2251472345
Sent from my Lenovo K50-t5 using XDA Free mobile app
got it in cheinese
can you send a link to an english site?
AOSP
I got some questions
-is it multilanguage
-is it Android 5.0
-gapps included?
-can someone post some screens
Yours faithfully
LeetjeDanhoff said:
I got some questions
-is it multilanguage
-is it Android 5.0
-gapps included?
-can someone post some screens
Yours faithfully
Click to expand...
Click to collapse
-yes
-yes
-only play store but that what important
-maybe later
This ROM is pretty laggy and the ram is mostly full, and the worse part is that it can't play any video or jifs. For now I will recomand not to install this ROM until it will be modify correctly. Link from megahttps://mega.co.nz/#!3UcAkaaK!uEtthUPkeD1q7T4Nyn0MFtpLe9AtwQf-lOwqtz5RU-I
Lenovo K3 Note T50-T5 multilang firmware
This is Lenovo K3 Note T50-T5 multilang firmware: kimmobile "dot" com/tin-tuc/rom-tieng-viet-lenovo-k3-note-k50-t5-lenovo-k3-note-k50-t5-multilang-firmware-id2674
System Update Problem
Hello,
When I go to the the About Phone settings I do not have the option to check for updates on my phone.
Please can you help?
Thank you,
Awais
AOSP based 5.0 build for the K3 Note
Nanj at a Chinese forum had released an AOSP based 5.0 build for the K3 Note
http://bbs.ydss.cn/thread-551335-1-1.html (in Chinese but with captures)
The download link:
http://pan.baidu.com/s/1hqAdrrY
No gapps are included. The build functions ok. Camera, phone / data, and wifi seem to work. However please note that there is an undesirable apk, posed as a system component, at /system/app/SystemServer/SystemServer.apk. It sends frequent packets back to 622b6.romdu.com in China, similar to the issue in another post for a different rom -
http://forum.xda-developers.com/showpost.php?p=55315205&postcount=54
The ROM also comes with a Chinese version of the Opera browser, Oupeng, which also sends analytics packets in the background.
With the two programs removed suspicious packets are no longer obvious from logcat.
headuck said:
Nanj at a Chinese forum had released an AOSP based 5.0 build for the K3 Note
http://bbs.ydss.cn/thread-551335-1-1.html (in Chinese but with captures)
The download link:
http://pan.baidu.com/s/1hqAdrrY
No gapps are included. The build functions ok. Camera, phone / data, and wifi seem to work. However please note that there is an undesirable apk, posed as a system component, at /system/app/SystemServer/SystemServer.apk. It sends frequent packets back to 622b6.romdu.com in China, similar to the issue in another post for a different rom -
http://forum.xda-developers.com/showpost.php?p=55315205&postcount=54
The ROM also comes with a Chinese version of the Opera browser, Oupeng, which also sends analytics packets in the background.
With the two programs removed suspicious packets are no longer obvious from logcat.
Click to expand...
Click to collapse
Does notification led work?
LeetjeDanhoff said:
I got some questions
-is it multilanguage
-is it Android 5.0
-gapps included?
-can someone post some screens
Yours faithfully
Click to expand...
Click to collapse
https://youtu.be/Wf4kkRq0ork review video on the K3 Note
cccho said:
One Chinese port AOSP to K3-Note.
Its can be daily use and without any bug now. If somebody need it. Just try it.
http://pan.baidu.com/share/link?shareid=2842642895&uk=2251472345
Sent from my Lenovo K50-t5 using XDA Free mobile app
Click to expand...
Click to collapse
does it come with gapps?
narithlot said:
does it come with gapps?
Click to expand...
Click to collapse
Sadly, no... But you can flash it with CWM
revert to stock ROM
Lataman said:
I have the same problem, I just changed to new version of VibeUI and had some problems with google apps HELP!
Click to expand...
Click to collapse
you can revert to stock ROM
if you have stock Recovery(Not CWM)
then flash this whith stock recovery
this is official stock chinese/english ROM
https://mega.co.nz/#!MwAxGACR!CNyHABuPxbMpHTHRAhbYJWl_IO4z7jAz8szgIMGt_jQ
instuctions:
make sure you have stock recoveyr
then put this ROM on external memory card
rename the zip file to update.zip
then go to stock recovery select update
New VIBE UI
There has been a new update released by Lenovo.
VIBEUI_V2.5_1524_5.955.1_ST_K50-T5
I have not updated as of yet, for the reason being I am very dissatisfied with the VIBEUI. I currently run 1522, despite the obvious and numerous complications of using the Asian based firmware. I have had to replace the dialer and sms, mms apps as well as install a font manager, even so I am still unable to get 4G working. I would much prefer a pure Android rom and for the past month have been considering beginning a project to build a new Lollipop rom supporting the 67xx MTK chipsets. It would be my first attempt at doing so since all my previous phones have been LG, HTC and NEXUS devices which have always proved easy enough to manipulate and customize.
If anyone out there has experience in building custom roms, especially for devices using the newer 64bit Mediatek chipset, please feel free to contact me. I would appreciate any help offered in this endeavor and I know there are many other MTK device owners out there that are just waiting for someone, or a group of someones', to pioneer a solution for those of us in the western hemisphere using these MTK devices. I am constantly on the look out for new information and projects pertaining to this, additionally I have a dedicated computer with all the SDKs needed to begin the project.
PM me if you are interested in helping kick start this project. Thanks.
What is the significance of this ROM string? I see that "ST" prob means (stable).
Know what "CC", "WCA2" and "WCA8" means in these I found below?
Do you know where is the (official) location to find the latest English language ROM?
My proximity sensor is not working and I'm wondering if moving to a diff ROM will fix that.
VIBEUI_V2.5_1520_7.128.1_CC_K50-T5_WCA2.zip (Android 5.0)
VIBEUI_V2.5_11520_5.827.1_ST_K50_T5 (Android 5.0) <------ the one my phone came with; multi-language
VIBEUI_V2.5_1524_5.955.1_ST_K50-T5_WCA8.zip (???)
VIBEUI_V2.8_1526_7.80.1_CC_K50-T5.zip (VIBE 2.8, Android 5.1)
BurntCircuitz said:
There has been a new update released by Lenovo.
VIBEUI_V2.5_1524_5.955.1_ST_K50-T5
I have not updated as of yet, for the reason being I am very dissatisfied with the VIBEUI. I currently run 1522, despite the obvious and numerous complications of using the Asian based firmware. I have had to replace the dialer and sms, mms apps as well as install a font manager, even so I am still unable to get 4G working. I would much prefer a pure Android rom and for the past month have been considering beginning a project to build a new Lollipop rom supporting the 67xx MTK chipsets. It would be my first attempt at doing so since all my previous phones have been LG, HTC and NEXUS devices which have always proved easy enough to manipulate and customize.
If anyone out there has experience in building custom roms, especially for devices using the newer 64bit Mediatek chipset, please feel free to contact me. I would appreciate any help offered in this endeavor and I know there are many other MTK device owners out there that are just waiting for someone, or a group of someones', to pioneer a solution for those of us in the western hemisphere using these MTK devices. I am constantly on the look out for new information and projects pertaining to this, additionally I have a dedicated computer with all the SDKs needed to begin the project.
PM me if you are interested in helping kick start this project. Thanks.
Click to expand...
Click to collapse
Here where you can find the Rooting and Custom ROMs
https://www.reddit.com/r/lenovok3note/wiki/index
https://www.youtube.com/watch?v=g4PQqRXSUa4
https://www.youtube.com/watch?v=wCwMQkX-1sw
Someone has already Deodexar the Stock Rom Zenfone Laser?
Would very much welcome a Tutorial,
help at all ..
Mandrakerj said:
Someone has already Deodexar the Stock Rom Zenfone Laser?
Would very much welcome a Tutorial,
help at all ..
Click to expand...
Click to collapse
use superr kitchen, linux based.
http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296
for windows based
http://forum.xda-developers.com/showthread.php?t=2639400
every thread has very good tutorial, hope it will help you. :good:
Well I can not do with these two applications because not Linux but Windows use. And then it would be nice a file ready update-binary and compatible updater-script to instalart then Deodex the device.
not do with these two applications because not Linux but Windows use. And then it would be nice a file ready update-binary and compatible updater-script to instalart then Deodex the device.
Someone has already Deodexar the Stock ROM and install the device?
Can anyone help ??
I will deodex the stock ROM later when I get back. I currently have kitchen running on my Mac.
Rizzed said:
I will deodex the stock ROM later when I get back. I currently have kitchen running on my Mac.
Click to expand...
Click to collapse
I also needed to Zenfone selfie ZD551KL
Alright. I will try to get it done by today..
*Link deleted*
FOR ZD551KL VARIANTS ONLY. Any attempt to flash this ROM on other ZenFone 2 series' variants would result in getting stuck at the manufacturer's logo. In that case, you would need to flash the stock ROM back to get it back to a working condition.
I do not have the ZD551KL variant of the ZenFone 2 Selfie with me now, thus, I can't test it out. Please do report back the results after flashing, and inform me immediately if "errors" or "signals" appear upon installation. Thanks!
EDIT: If this works out fine, I will be doing the same for the other variants of the ZenFone 2 series and then place them all into another thread!
this is for the ze551kl?
install from root with twrp?
rooted?
thanks
beenkenobee said:
this is for the ze551kl?
install from root with twrp?
rooted?
thanks
Click to expand...
Click to collapse
Nope, only for ZD551KL devices. I just found out that there's essentially no point in removing the verification checks, as even if it installs on the other variants, it would fail to boot as the kernel files are different. That is, unless you are willing to flash the boot.img yourself, which requires downloading the original ROM, extracting, and using the fastboot commands "fastboot flash boot boot.img".
Following up on your other questions, no. No root is required to install this ROM, only a custom recovery, such as TWRP or CWM. The ROM is also NOT pre-rooted (well, I need to learn HOW first.)
I could compile a deodex-ed ROM for you later. Though I would suggest you to wait out a while for the people with the ZD551KL variants to test it out first and see if the Android Kitchen's modifications really worked.
As for now, I will leave the download file as it is (no verification checks). I will update it tomorrow, together with the compiling for the deodex-ed ROM for ZE551KL variants (as well as others, if time permits).
Rizzo, what application you are using to Deodexar the Rom? Here I only use Windows 7 x64
Rizzed said:
https://drive.google.com/file/d/0B6QXDUz9wzc9dWIyTUJ1a05TMzA/view?usp=sharing
FOR ZD551KL VARIANTS ONLY. Any attempt to flash this ROM on other ZenFone 2 series' variants would result in getting stuck at the manufacturer's logo. In that case, you would need to flash the stock ROM back to get it back to a working condition.
I do not have the ZD551KL variant of the ZenFone 2 Selfie with me now, thus, I can't test it out. Please do report back the results after flashing, and inform me immediately if "errors" or "signals" appear upon installation. Thanks!
EDIT: If this works out fine, I will be doing the same for the other variants of the ZenFone 2 series and then place them all into another thread!
Click to expand...
Click to collapse
Rizzo, I still do not understand anything.
This Stock ROM that you made available for download, it would be for selfie ZD551KL? What would be the version of this Stock Rom? She has not estarai Deodexada, correct? What do I do here with her in my ZD551KL? Install from sdcard or would the TWRP? I would like to learn how to Unzip the System Image Stock Rom ZD551KL. I do not know how to do this. How can I help you?
Sorry for the confusion guys.... I will be testing it out on my ZE550KL first and see if the tool works properly. If it does, I will help to de-odex the ZD551KL variants (and possibly others too) and post it on an entirely new thread.
Rizzed said:
Sorry for the confusion guys.... I will be testing it out on my ZE550KL first and see if the tool works properly. If it does, I will help to de-odex the ZD551KL variants (and possibly others too) and post it on an entirely new thread.
Click to expand...
Click to collapse
Hi there friend thank you for your help. I will wait for the results with your Laser ZE550KL. I'm hoping that everything goes well. So I will wait for the procedure for Variant selfie ZD551KL because this is what I need right now.
Alright! Everything appears to be working... I have not tried flashing yet, but, it should be able to boot up fine.
I've deodexar the Stock rom selfie ZD551KL. I just can not install because of the error in updater-script.
Mandrakerj said:
I've deodexar the Stock rom selfie ZD551KL. I just can not install because of the error in updater-script.
Click to expand...
Click to collapse
In that case, could you upload the updater-script so that I could have a look at it?
So my friend..
In fact I do not even have the original file to the selfie ZD551KL.
What I was tested in a template JoelDroidLollipopBatchDeodexer the page.
This man did not work ...
I found no script created for Deodexar Rom in selfie ZD551KL.
Here for you ..http://www.mediafire.com/download/84m7v0qubav1m32/InstallerTemplate.zip
Rizzed said:
In that case, could you upload the updater-script so that I could have a look at it?
Click to expand...
Click to collapse
So my friend Rizzed..
In fact I do not even have the original file to the selfie ZD551KL.
What I was tested in a template JoelDroidLollipopBatchDeodexer the page.
This man did not work ...
I found no script created for Deodexar Rom in selfie ZD551KL.
Here for you ..http://www.mediafire.com/download/84...erTemplate.zip
Hey all,
the problme is that the international version has another cam module (13mp) than the chinese version (18mp).
Therefore the custom roms , which are always based on the chinese version and cant use the camera.
Now I need some help on how to implement the driver from the original firmware:
http://rom.download.nubia.com/Germany/Z9mini/NX511J-update.zip
Into this custom rom from mokee:
http://download.mokeedev.com/?device=nx511j
My phone is already rooted and has a custom reovery. I already tried to "zip-edit" the mokee rom and copied/replaced files from the stock rom into the mokee rom , base on this info from here and here e.g.:
Libcamalgo.so
Libcameracustom.so
Libcameraclient.so
Libcameraservice.so
Libcamerametadata.so
and
system/lib/ libcamdrv.so
system/lib/libcamalgo.so
system/lib/libcameracustom.so
system/lib/libdpframework.so
system\etc\permissions\android.hardware.camera.xml
and then rezipped the rom and signed the zip with the autosign tool.
This "custom" rom than could even be successfuly installed with twrp without an problem, but then didnt
get beyond the mokee boot logo.
Now my question is:
Can this be due to the fact that the stock rom is 5.02 and the custom rom/mokee is 6.01 and the drivers simply cant work due to another android version?
Am I thinking way to easy with this simple "copy/paste zip editing" and something more complex like editing the kernel has to be done?
Any tip for what to do is very appreciated, as I think I have to solve it by myself due to a lack of mass-interest in this device.
Does it support Indian version?
Sent from my NX511J using XDA-Developers mobile app
Sorry for my late reply, I've been on vacation.
I dont know if it supports the indian version. My device is the EU version I guess...
It has a different camera module whith only 13mp-
Hi!
Just replacing those files can't work. The drivers for the t4k37 camera sensor aren't built in in the mokee release.
When it boots, it only polls those Sony IMX sensors. Furthermore the librarys for the t4k37 sensor arent't in the rom.
I'vre tried to build my own mokee rom, but with no luck, got only to boot animation. The device isn't supported officialy by
Mokee any longer. As I didn't build android before, my knowledge is obviously too little for this kind of task... perhaps some
more experienced guys could help...
Also it's hard to understand what is the exact difference in the chinese, indian , international an german modells of the phone, there are little informations.
Just flashed Mokee MK51.1-nx511j-160420-HISTORY.zip and moved the appropriate libraries to the flash, it seems, that the t4k37 sensor initializes and works. Sadly there's no camera app preinstalled.
Tested with Open Camera App from Playstore. I'll now try to get the original camera app.
Libraries where taken from germans stock rom in vendor folder.
kai4065 said:
Just flashed Mokee MK51.1-nx511j-160420-HISTORY.zip and moved the appropriate libraries to the flash, it seems, that the t4k37 sensor initializes and works. Sadly there's no camera app preinstalled.
Tested with Open Camera App from Playstore. I'll now try to get the original camera app.
Libraries where taken from germans stock rom in vendor folder.
Click to expand...
Click to collapse
Hi kai4065!
Can you give me more info please. Which file list I need to replace. I need to create patch for one of localized firmware. Also may be you know where I can get last de firmware? My device was flashed with NX511J_DECommon_V1.01 now but buyed with 1.02.
Thx for any help.
falkolab said:
Hi kai4065!
Can you give me more info please. Which file list I need to replace. I need to create patch for one of localized firmware. Also may be you know where I can get last de firmware? My device was flashed with NX511J_DECommon_V1.01 now but buyed with 1.02.
Thx for any help.
Click to expand...
Click to collapse
Here's the list:
# Camera
etc/firmware/cpp_firmware_v1_4_0.fw
etc/firmware/cpp_firmware_v1_2_0.fw
etc/firmware/cpp_firmware_v1_1_6.fw
etc/firmware/cpp_firmware_v1_1_1.fw
-lib/libmm-qcamera.so
-lib/libmorpho_jpeg_io.so
-lib/libmmjpeg_interface.so
-lib/libqomx_core.so
-lib/libmorpho_memory_allocator.so
-lib/libmmcamera_interface.so
-lib/libmorpho_strobe_photo_jni.so
-lib/libmorpho_image_converter.so
-lib64/libmorpho_jpeg_io.so
-lib64/libmorpho_memory_allocator.so
-lib64/libmorpho_image_converter.so
lib/hw/camera.msm8916.so
bin/mm-qcamera-daemon
bin/mm-qcamera-app
vendor/lib/libmmcamera_faceproc.so
vendor/lib/libchromatix_ov5648_p5v18g_common.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_snapshot.so
vendor/lib/libactuator_rohm_bu64297gwz.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_preview.so
vendor/lib/libmmcamera_t4k35.so
vendor/lib/libmmcamera2_stats_modules.so
vendor/lib/libactuator_bu64291gwz.so
vendor/lib/libmmcamera2_stats_algorithm.so
vendor/lib/libjpegdhw.so
vendor/lib/libmmcamera_t4k37_qtech_f4k37ab.so
vendor/lib/libmmcamera2_c2d_module.so
vendor/lib/libmmcamera2_cpp_module.so
vendor/lib/libmmcamera2_vpe_module.so
vendor/lib/libmmcamera_ov2720.so
vendor/lib/libmmcamera_S5K4E1_13P1BA.so
vendor/lib/libchromatix_t4k35_nightmode_1.so
vendor/lib/libmmipl.so
vendor/lib/libchromatix_t4k35_common.so
vendor/lib/libchromatix_ov2720_preview.so
vendor/lib/libmmcamera_sunny_q5v22e_eeprom.so
vendor/lib/libjpegehw.so
vendor/lib/libmmcamera2_sensor_modules.so
vendor/lib/libchromatix_ov5648_q5v22e_zsl.so
vendor/lib/libchromatix_ov5648_oty5f03_common.so
vendor/lib/libmmcamera_sp1628.so
vendor/lib/libmmcamera_skuf_ov5648_p5v23c.so
vendor/lib/libmmQSM.so
vendor/lib/libactuator_bu64291gwz_t4k35.so
vendor/lib/libmmcamera_wavelet_lib.so
vendor/lib/libchromatix_t4k35_preview.so
vendor/lib/libchromatix_t4k35_hfr_120.so
vendor/lib/libmmcamera2_pproc_modules.so
vendor/lib/libmmcamera_imx132.so
vendor/lib/libmmjpeg.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_snapshot.so
vendor/lib/libchromatix_ov5648_oty5f03_default_video.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_nightmode.so
vendor/lib/libactuator_bu64291gwz_camcorder.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_common.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_default_video.so
vendor/lib/libmmcamera_tintless_algo.so
vendor/lib/libmmcamera_ov5648_oty5f03.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_video_hd.so
vendor/lib/libactuator_bu64291gwz_camera.so
vendor/lib/libchromatix_t4k35_default_video.so
vendor/lib/libmmcamera2_wnr_module.so
vendor/lib/liboemcamera.so
vendor/lib/libactuator_bu64291gwz_t4k35_camcorder.so
vendor/lib/libchromatix_ov5648_preview.so
vendor/lib/libmmcamera_ov5648.so
vendor/lib/libmmcamera_ov5648_p5v18g.so
vendor/lib/libchromatix_ov5648_q5v22e_preview.so
vendor/lib/libchromatix_t4k35_snapshot.so
vendor/lib/libchromatix_ov5648_p5v18g_preview.so
vendor/lib/libmmcamera2_isp_modules.so
vendor/lib/libchromatix_ov5648_q5v22e_snapshot.so
vendor/lib/libmm-qdcm.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_hfr_120.so
vendor/lib/libchromatix_t4k35_nightmode.so
vendor/lib/libmmqjpeg_codec.so
vendor/lib/libchromatix_ov5648_q5v22e_common.so
vendor/lib/libmmcamera2_imglib_modules.so
vendor/lib/libmmcamera_tintless_bg_pca_algo.so
vendor/lib/libchromatix_ov5648_p5v18g_default_video.so
vendor/lib/libchromatix_ov5648_q5v22e_default_video_hd.so
vendor/lib/libchromatix_ov5648_common.so
vendor/lib/libchromatix_ov5648_oty5f03_snapshot.so
vendor/lib/libmmcamera_imglib.so
vendor/lib/libmmcamera_hdr_gb_lib.so
vendor/lib/libchromatix_ov5648_p5v18g_default_video_hd.so
vendor/lib/libmmcamera2_frame_algorithm.so
vendor/lib/libmmcamera_hi256.so
vendor/lib/libmmcamera2_iface_modules.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_liveshot.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_common.so
vendor/lib/libchromatix_ov5648_default_video.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_default_video.so
vendor/lib/libchromatix_ov5648_p5v18g_zsl.so
vendor/lib/libqomx_jpegdec.so
vendor/lib/libchromatix_ov5648_snapshot.so
vendor/lib/libchromatix_ov5648_oty5f03_preview.so
vendor/lib/libmmcamera_hdr_lib.so
vendor/lib/libmmcamera_ov5648_q5v22e.so
vendor/lib/libactuator_bu64291gwz_t4k35_camera.so
vendor/lib/libchromatix_ov5648_oty5f03_zsl.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_pre4zsl.so
vendor/lib/libchromatix_ov5648_zsl.so
vendor/lib/libqomx_jpegenc.so
vendor/lib/libchromatix_ov5648_q5v22e_default_video.so
vendor/lib/libmmcamera_ov5645.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_nightmode_1.so
vendor/lib/libmmcamera2_is.so
vendor/lib64/libmmcamera2_stats_algorithm.so
vendor/lib64/libchromatix_imx214_hfr_60fps.so
vendor/lib64/libchromatix_imx219_q8n13a_common.so
vendor/lib64/libactuator_rohm_bu64297gwz_camcorder.so
vendor/lib64/libchromatix_imx214_default_video_4k.so
vendor/lib64/libchromatix_imx214_nightmode_1.so
vendor/lib64/libchromatix_imx219_q8n13a_default_video.so
vendor/lib64/libchromatix_imx219_q8n13a_liveshot.so
vendor/lib64/libchromatix_ov8858_q8v19w_common.so
vendor/lib64/libchromatix_imx234_liveshot.so
vendor/lib64/libchromatix_imx219_q8n13a_snapshot.so
vendor/lib64/libchromatix_imx234_hfr_120.so
vendor/lib64/libchromatix_ov16825_common.so
vendor/lib64/libchromatix_imx214_snapshot.so
vendor/lib64/libchromatix_imx234_snapshot_nightmode_1.so
vendor/lib64/libchromatix_imx214_liveshot.so
vendor/lib64/libchromatix_ov8858_snapshot.so
vendor/lib64/libchromatix_imx234_snapshot_nightmode.so
vendor/lib64/libchromatix_ov8858_liveshot.so
vendor/lib64/libchromatix_imx179_preview.so
vendor/lib64/libchromatix_ov8858_hfr_60fps.so
vendor/lib64/libchromatix_imx234_common.so
vendor/lib64/libchromatix_ov8858_q8v19w_snapshot.so
vendor/lib64/libchromatix_ov13850_default_video.so
vendor/lib64/libchromatix_imx219_q8n13a_preview.so
vendor/lib64/libchromatix_imx234_default_video.so
vendor/lib64/libmmcamera2_frame_algorithm.so
Probably not all files are necessary, but i was too lazy to test it out one by one. I just replaced all of them. The libs for the imx sensor probably aren't needed.
Latest german rom is V1.01, as far as I know. Never ever seen a german localized V1.02. Files above were taken from 1.01.
Just works for 5.1, as in Mokee 60.1 there's some sort of timeout when it tries to initialize the driver. Some patching would be needed, but trying to build Mokee myself
didn't resume a working ROM.
kai4065 said:
Here's the list
Click to expand...
Click to collapse
Thank you! I'll try. :good:
Just wanted to let you know,that I was sick of copying the files in every new release, so I just swapped the main camera sensor with the Sony sensor found in the Chinese model. Works like a charm.