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.
Related
Q&A for [ROM] [STOCK] [XT1069] [ROOT] Stock ROM - XT1069 - KXB21.85-24
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [STOCK] [XT1069] [ROOT] Stock ROM - XT1069 - KXB21.85-24. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
You created two scripts?
adrianom said:
I made some scripts to clean (remove stock apps) and optimize the ROM, instead of modifying the main ROM, I created these scripts that must be run in recovery.
For download go to post 2.
...
Click to expand...
Click to collapse
I packed your recoverys and made a zip flashable recovery, but never said I made a recovery. When a new version appears I pointed to your work.
http://www.htcmania.com/showthread.php?t=907314
You have used my script. I'm not a developer as you are, but I don´t think you like that people use your work and say nothing about your effords.
http://www.htcmania.com/showthread.php?t=909354
Regards.
elperroderoke said:
I packed your recoverys and made a zip flashable recovery, but never said I made a recovery. When a new version appears I pointed to your work.
http://www.htcmania.com/showthread.php?t=907314
You have used my script. I'm not a developer as you are, but I don´t think you like that people use your work and say nothing about your effords.
http://www.htcmania.com/showthread.php?t=909354
Regards.
Click to expand...
Click to collapse
Yes, indeed I use some lines of your post, but to be clear, the script that is in the zip is not what is in your post, it has a lote more, and yours don't work on this device, yes a grab some delete lines to simplified the list of apps, but that was it, and I have not mentioned, simply by forgetting it.
I put the reference now:
http://forum.xda-developers.com/showpost.php?p=56221065&postcount=2
scripts
I saw the lines you included and I hope you don't mine I will use some of them to improve my script for X1068.
If you be so kind to solve a question about deleting some files I would thank you.
Is there any way to delete the updates apk in /data/app?
As you know some of them are in /system and in /data once they are updated, but the name changes if is update again.
For instance:
Books.apk is in /system but, com.google.android.apps.books-1.apk is in /data and if is updated again it will be com.google.android.apps.books-2.apk
I tried using
delete("/data/app/com.google.android.apps.books*.apk");
or
delete("/data/app/com.google.android.apps.books-*.apk");
instead of
delete("/data/app/com.google.android.apps.books-1.apk");
delete("/data/app/com.google.android.apps.books-2.apk");
bud didn't work. Is there any way to delete the files that that have similar name.
Thank you for all your work.
Regards.
Any custom rom or rom adapted for xt1069?
Error
Hello man, I'm brazillian, sorry for my english.
I tried to flash a rom from this website: sbf.droid-developers.org/phone.php?device=36 , the last rom, because my Moto G 2 is Duos TV. When I flashed the rom, my camera stopped, just the frontal camera function, my flashlight too stopped... I really like to know, if you can help me with it... How you know, the cam of Moto G 2 has a button to change between Frontal and main camera, but this button doesn't appears, and the options in the configuration is blocked(some of them).
Please help me, I paid R$799,00 (money of Brazil), thanks a lot for everything!
xdaVTU said:
Hello man, I'm brazillian, sorry for my english.
I tried to flash a rom from this website: sbf.droid-developers.org/phone.php?device=36 , the last rom, because my Moto G 2 is Duos TV. When I flashed the rom, my camera stopped, just the frontal camera function, my flashlight too stopped... I really like to know, if you can help me with it... How you know, the cam of Moto G 2 has a button to change between Frontal and main camera, but this button doesn't appears, and the options in the configuration is blocked(some of them).
Please help me, I paid R$799,00 (money of Brazil), thanks a lot for everything!
Click to expand...
Click to collapse
You are using the Motorola app or the Google camera app? The button to change are in different places.
About the firmware, you have to flash the correct one? Has to be the with dstv in the name. If you flash the wrong one try flash the correct.
help
adrianom said:
You are using the Motorola app or the Google camera app? The button to change are in different places.
About the firmware, you have to flash the correct one? Has to be the with dstv in the name. If you flash the wrong one try flash the correct.
Click to expand...
Click to collapse
Adrianom, thanks for answer my question, but yes, I made the correct download, in the name was wrote DSTV, and about the app.. I don't know what the app that I'm using, is the factory app of the device, probability of Motorola. And all the apps that has the function of camera, neither of them work with me... Thanks for everything, and.... What do you think about my english? Is good or not?
Restarts before finalizing the installation
Friend, did the procedure to install this ROM , already have the unlocked Bootloader and Flash Recovery CWM , however when are installing the phone restarts and crashes in toot screen. Has suggested to solve this?
Using scripts can usually upgrade?
If I install the Rom Stock and use the scripts before the OTA update, I can upgrade later without the applications of Motorola?
Perfect installation
Did all the installation process and everything was perfect, just a detail that installed only by CWM recovey at TWRP was not.
Root is stable? No bootloops? I turn back to kk from 5.0 because link2sd not working in 5.0 rooted and unstable root.
Not W
Its not working on me, i'm getting a black screen at boot time.
Update bootloader
If I flash this rom my bootloader will go to version 46.87?
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
Hello everyone..
am I new here, ók, yes, but you should help me because you maybe the only one can help.
So, I'm with my lovely s3mini tried several ROMs but finally I'm on resurrection remix, my problem its can't run spirit FM radio don't [email protected] that I have to configure it or try with it anymore...I'm not so noon...
8 have seen @lot of mods shipping a working FM app with it but surely failed to use any of it in that ROM, at least most libraries come from 7.1.2 open source project different from native or modded to custom ui or anything..
@nyway, please developers, I need your help, i need one of theese working apps with libraries it uses to get FM works in a flashable zip file, to know I have full [email protected] my mobile so try anything manners. Thanks all in advance.
ahmeddalloul said:
Hello everyone..
am I new here, ók, yes, but you should help me because you maybe the only one can help.
So, I'm with my lovely s3mini tried several ROMs but finally I'm on resurrection remix, my problem its can't run spirit FM radio don't [email protected] that I have to configure it or try with it anymore...I'm not so noon...
8 have seen @lot of mods shipping a working FM app with it but surely failed to use any of it in that ROM, at least most libraries come from 7.1.2 open source project different from native or modded to custom ui or anything..
@nyway, please developers, I need your help, i need one of theese working apps with libraries it uses to get FM works in a flashable zip file, to know I have full [email protected] my mobile so try anything manners. Thanks all in advance.
Click to expand...
Click to collapse
Read this & this to get fm radio. Also a bedtime reading here, about the "thanks in advance".
mauam said:
Read this & this to get fm radio. Also a bedtime reading here, about the "thanks in advance".
Click to expand...
Click to collapse
Really thank you friend, I've tried many versions from @Round..but its the only working one...but I noticed that the other versions became able to access fm,,no accessible fm,,is no more shown,...as if it should be unlocked first...but..again..I should unlock again " open it with that version mentioned" then go to other...so I deleted them..now I'm with working spirit FM app.
That's good, but I wanted the version @LREady come with stock on my 7.1.2 android from one [email protected] developers
. ..
At @ll, thank you very much...sorry for my English...
Feel free to correct me, I'm still learning, and thanks for understand.
I'm using Xperia XZ1 Compact SO-02K (Japanese docomo model) unlocked bootloader via qUnlockTool.
I installed some custom ROMs like LineageOS 18.1, Havoc OS 4.8, 3.11.
Any ROMs doesn't go to deep sleep so the battery drain is so bad. I installed Android 11 ROMs and 10 ROMs, but both not working deep sleep.
Anyone know good solutions?
Hi,
great to see some other user from Japan with the SO-02K. I also recently installed a custom rom and had the same issues as you. The source is the NFC chip. Unfortunately the Japanese version have a different chip/driver because of the Felica services here (Felica was here in Japan well before Google was even thinking to integrate NFC in Android, so nobody to blame here, beside Google, not Sony.)
Anyway the fix is a bit ugly. However, there is help:
Download this image from here: https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/
Yes, this and only this. I know it has not been updated anymore, but the reason comes below.
Please check out this thread: https://forum.xda-developers.com/t/fixed-xz1-au-sov36-japan-deepsleep-on-g8341-custom-roms.4156209/
It is about the XZ1 AU version but it also applies to the compact. I summarize here to make the post complete:
Either you root the phone, which I did not do because I do not need root for anything and with root, some of my app do not work, like Spotify. So I recommend to do those steps in the TWRP. Simply mount all the partitions and go to the file manager under advanced options.
Go to folder: /vendor/lib/modules
and delete or rename file call pn553.ko
Restart your phone and it will go to deep sleep. Otsukaresama.
Now, why only this image. Because it uses the older NFC library. In all other images, this fix this not apply anymore, as the modules are not at that place. I really would appreciate if someone more experienced can point me to the nfc module drives in any newer LineageOS image.
PS: Of course NFC will never work with a custom rom (without trying yourself to find out how to make it work)
Best
mugenXperia said:
Hi,
great to see some other user from Japan with the SO-02K. I also recently installed a custom rom and had the same issues as you. The source is the NFC chip. Unfortunately the Japanese version have a different chip/driver because of the Felica services here (Felica was here in Japan well before Google was even thinking to integrate NFC in Android, so nobody to blame here, beside Google, not Sony.)
Anyway the fix is a bit ugly. However, there is help:
Download this image from here: https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/
Yes, this and only this. I know it has not been updated anymore, but the reason comes below.
Please check out this thread: https://forum.xda-developers.com/t/fixed-xz1-au-sov36-japan-deepsleep-on-g8341-custom-roms.4156209/
It is about the XZ1 AU version but it also applies to the compact. I summarize here to make the post complete:
Either you root the phone, which I did not do because I do not need root for anything and with root, some of my app do not work, like Spotify. So I recommend to do those steps in the TWRP. Simply mount all the partitions and go to the file manager under advanced options.
Go to folder: /vendor/lib/modules
and delete or rename file call pn553.ko
Restart your phone and it will go to deep sleep. Otsukaresama.
Now, why only this image. Because it uses the older NFC library. In all other images, this fix this not apply anymore, as the modules are not at that place. I really would appreciate if someone more experienced can point me to the nfc module drives in any newer LineageOS image.
PS: Of course NFC will never work with a custom rom (without trying yourself to find out how to make it work)
Best
Click to expand...
Click to collapse
Thanks for good solutions!
Actually, I couldn't find pn553.ko on the latest stock ROM(47.2.B.5.38), so I deleted all of NFC files in /Vendor (of cause I took /Vendor backup with TWRP.). The deepsleep little works (please check attached picture) but the battery drain is better than before.
Thanks anyway!
satokun2668 said:
Thanks for good solutions!
Actually, I couldn't find pn553.ko on the latest stock ROM(47.2.B.5.38), so I deleted all of NFC files in /Vendor (of cause I took /Vendor backup with TWRP.). The deepsleep little works (please check attached picture) but the battery drain is better than before.
Thanks anyway!
Click to expand...
Click to collapse
what files did you delete, can you help me to deep sleep?
mugenXperia said:
Hi,
great to see some other user from Japan with the SO-02K. I also recently installed a custom rom and had the same issues as you. The source is the NFC chip. Unfortunately the Japanese version have a different chip/driver because of the Felica services here (Felica was here in Japan well before Google was even thinking to integrate NFC in Android, so nobody to blame here, beside Google, not Sony.)
Anyway the fix is a bit ugly. However, there is help:
Download this image from here: https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/
Yes, this and only this. I know it has not been updated anymore, but the reason comes below.
Please check out this thread: https://forum.xda-developers.com/t/fixed-xz1-au-sov36-japan-deepsleep-on-g8341-custom-roms.4156209/
It is about the XZ1 AU version but it also applies to the compact. I summarize here to make the post complete:
Either you root the phone, which I did not do because I do not need root for anything and with root, some of my app do not work, like Spotify. So I recommend to do those steps in the TWRP. Simply mount all the partitions and go to the file manager under advanced options.
Go to folder: /vendor/lib/modules
and delete or rename file call pn553.ko
Restart your phone and it will go to deep sleep. Otsukaresama.
Now, why only this image. Because it uses the older NFC library. In all other images, this fix this not apply anymore, as the modules are not at that place. I really would appreciate if someone more experienced can point me to the nfc module drives in any newer LineageOS image.
PS: Of course NFC will never work with a custom rom (without trying yourself to find out how to make it work)
Best
Click to expand...
Click to collapse
hy bro, can you tell me list rom xz1 compact docomo that have pn553 ko?
bangsat69 said:
what files did you delete, can you help me to deep sleep?
Click to expand...
Click to collapse
See this:
[ROM] Havoc-OS 4.6 [OFFICIAL] [R]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com