yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] je2854:
Install Kingroot (not kingoroot) Click Here

-root and reboot

Install Supersu me from the market Click Here

- follow in-app instructions

Install FlashFire version .52 Click Here

-No more, no less or it will not work

Install Xposed 3.0 Alpha 4 Click Here

-find it on XDA

FlashFire Xposed version SDK 22 version 80, *arm* Click Here

-hit add button, flash zip or OTA, select Xposed.zip, untick mount /system read/write option

FLASH

Google is always your friend but since I found a proper root, found all the links for you, and gave the links.

Please hit the thanks button!
[Android Q&A, Help & Troubleshooting] princedare:
Thank You Sir. You are awesome. I want to thank you and I couldn't find Thanks button instead clicked thumbs up icon (as like button in Facebook). Pls let me know if it helps.

Thanks again and am starting to root my tab.

Thanks,

Prince
[Android Q&A, Help & Troubleshooting] princedare:
Hi JE,

Hope I get some help here. I followed steps You provided in order.

Installation of kingroot worked fine.

Having trouble with super su me. After I click blue icon it's stucked saying Processing from more than 7 hours. Pls let me know if I can get rid of this.

Thanks,

Prince
[Android Q&A, Help & Troubleshooting] je2854:
Super SU me is a paid for app...

I cannot help with 3rd party locations.

I've ran through the process multiple times and it works...

Do you have USB debugging on?
[Xperia Z2 Q&A, Help & Troubleshooting] BackyardFixer:
Hi guys,

After the smallest of drops my Z2 has gone a bit odd. It thinks there is a constant touch in the top right of the screen/notification bar. Unfortunately this is rendering it fairly useless.

Does anyone know of a way I can disable touch in a specified region (X,Y coords?), I had a quick search but everything I found was for app development rather than usability. Perhaps I wasn't using the right terms.

Any insight would be wonderful!

Screenshot of the current problem - touch in the top right on the clock is a ghost/phantom touch that is constant.

Apparently I can't link outside urls because I'm new but if you were to go to i.imgur.com/nqT4nxA.png you would see a screenshot of the situation
[Xperia Z2 Q&A, Help & Troubleshooting] mr.loverlover:
I think there's not such an app yet.

Sent from Xperia Z2

Luckily not from an iPhone = Yesterdays technology at tomorrows prices
[Xperia Z2 Q&A, Help & Troubleshooting] BackyardFixer:
Update:

Flashed phone to KitKat (17.1.A.2.55) and there was no touch at all in the top status bar!

Thinking I had perhaps somehow fixed it I then flashed phone to Lollipop (23.1.A.1.28), 5.0.2, and the spot/touch came back in the status bar :(

Anyone able to make some suggestions? I probably should have made a more detailed thread for this problem.

I may unlock the bootloader and try a custom rom and just pray? Or I guess I'm stuck running KitKat?
[K3 Note General] Syaoran Lord:
Can you add some image :3
[K3 Note General] sandeep.sethi:
i can add but image of what should i add
[K3 Note General] Ufoner:
Porting to Ulefone be touch 2

Hi! Nice tutorial. Will this method work with Ulefone be touch 2? I want to port Aerom v5 from elephone p7000 to Ulefone be touch 2. My kernel version is 3.10.61 and port rom kernel is 3.10.91 so I have to port kernel? Thanks in advance :)
[K3 Note General] sandeep.sethi:
yes it will work

no need to do anything about kernel u just proceed as the guide says
[K3 Note General] Ufoner:
Thank you so much! And one more question please. Some guy try to port CM12.1 for BT2 and volume down button stopped working and screen is laggy. Installing stock ROM not solve that problem. Can happend this when i port android 5.0 or 5.1? Sorry for my bad English. Thanks in Advance.
[K3 Note General] sandeep.sethi:
try taking logcat while pressing the vol down key
[K3 Note General] jordandroid64:
Hello, I don't undestand that : ALWAYS REMOVE RECOVERY-FROM-BOOT.P before you do anything else. please someone could explain for me ?
[K3 Note General] Ufoner:
You need to delete file "recovery-from-boot.p" from system folder of your stock ROM and of port :) :good:

---------- Post added at 07:55 PM ---------- Previous post was at 07:53 PM ----------

I ended again with black screen when porting cm12.1 from redmi note 2 :( Is it caused by another size of ram :confused: Because my device has 3gb ram and redmi note 2 has 2gb.
[K3 Note General] jordandroid64:
thanks but it's an img on my port rom and I don't find this file... and same on my stcok rom (androium) but there are files name recovery i need to delete all of them ?
[K3 Note General] Ufoner:
You need to extract system.img with ext4unpacker and then make it folder with ext2explore. [YOUTUBE]http://m.youtube.com/watch?v=yU1MFYUj6zc[/YOUTUBE]

You dont need recovery so delete it
[K3 Note General] jordandroid64:
I have already extract the img but with ext2explore only that will be good also?

thanks for your answer

edit: edit : on the port rom at the last when i search recovery that whow me that :

http://www.hostingpics.net/viewer.php?id=839697recovery.jpg
[K3 Note General] Ufoner:
Help me with bootloop please

Hi sandeep.sethi!

Today i port your aicp 5.1.1 from k3 note to be touch 2(stock rom is android 5.0.1) and i got bootloop :(. I edited mount points and replaced all files as your guide says.

Do i need to port kernel or anything else when my device has 3gb ram and k3 note has 2gb ram :confused: All specs are same except the ram size.

Stock rom is 5.0.1, but alex1112 port cm12.1(5.1.1) to be touch 2, so do i need to port kernel from alex1112 cm12.1 or from my stock rom to AICP?

Is this guide for same android version ex. 50.1 to 5.0.1?

Thanks in advance and have a good day :)
[K3 Note General] sandeep.sethi:
then try using his kernel in the boot.img with my roms' ramdisk
[K3 Note General] Ufoner:
Thanks but i have problem

Thank you it worked, but when device start after bootanimation it show aicp is upgrading optimizing app starting apps ..... and then it restart and then again starting apps... and reboot. Please help. Thank you so much for your support.
[K3 Note General] sandeep.sethi:
what files did u replace from lib/hw and lib64/hw

or try taking cm12 of ur phone as base
[K3 Note General] Ufoner:
I replaced all files except in lib and lib64 lenovopower.default.so and in drm i don´t replaced drm\libfwdlockengine.so because my stock rom don´t have these files. I tried this method to fix stuck in starting apps... http://www.mtkroms.com/2016/01/bugless-lollipop-exodus-for-mt6592.html and it not worked :( I searched that some people say the problem is in system apps and i need to replace them, is it true? Thanks, today i will try to port rom again with cm12.1 files :) If you help me and rom will boot i will donate to you bro :good:
[K3 Note General] AnStu00:
Help with porting

Hello! Thanks for this awesome tutorial! :D

But now i need some help with porting a ROM

I am porting your BlissPOP rom from Lenovo K3 Note to my Elephone P7000 device!

when i install it with TWRP i get stuck in a bootloop

Can you please help me with this problem, i have followed the tutorial exactly as i should!¨

What should i do? :D

please help!

//AnStu00
[K3 Note General] Ufoner:
I got bootloop too and sandeep.sethi told me how to fix it!

1. You need to change mount points in updater-script

2.Extract blisspop´s rom boot.img and extract boot.img from Elephone CM12.1 http://www.needrom.com/download/elephone-p7000-cyanogenmod-12-1/ and then copy blisspop rom ramdisk and copy it to cm12.1 boot.img and then repack it :)
[K3 Note General] sandeep.sethi:
okay try porting again and this tym in ramdisk replace factory rc files
[K3 Note General] sandeep.sethi:
dont replace any bin files and try :good:
[K3 Note General] yui90:
Hallo sir sandeep.sethi..

I try port ROM colorOS (5.0) from oppo R7 mt6795 to my stock rom (5.1) mt6735, but stuck on bootanimation.

Any solution.??

Thanks before, for your guide..
[K3 Note General] sandeep.sethi:
I think it is possible to port 5.0 with 5.1 as miui can be done but i need to ask my friends what did they replaced to port gimme some time i will reply as soon as posiible.
[K3 Note General] yui90:
I was ready to wait, thank you very much for your help sir.
[K3 Note General] sandeep.sethi:
#Try this

* LIB & LIB64

* HW (foldser)

* EGL (foldser)

* And all libcam_XXX except :

* libcamera_client.so

* libcamera_metadata

* libcameracustom.so

ETC

* Delete and copy from stock:

* firmware (folder)

* mddb (folder)

* copy and replace from stock:

* agps_profiles_conf2.xml

* apns-conf.xml

* custom.conf

* recovery.xml

* recovery.fstab

* recovery-resource.dat

* spn-conf.xml

* trustzone.bin.

Boot:

boot.img-kernel [replace from stock to port] fstab.mt67xx [replace from stock to port] compare all init.67xx files ________________________________________ MT6735/35M/35P/53 to new MT6737 or viceversa (who is enhanced MT6735 platform)

* LIB & LIB64

* HW (folder)

* EGL (folder)

* lib3a.so

* lib3a_sample.so

* lib3m.so

* libacdk.so

* All libaudio_xxx.so

All libcam_XXX.so except [replace all other than the libcams listed below]libcamera_client.so libcamera_metadata libcameracustom.so libcustom_nvram.so libdrmframework.so libexif.so libft2.so All libimageio_xxx.so libjni_eglfence.so libjnigraphics.so libjpeg.so libJpgDecPipe.so libJpgEncPipe.so libjtranscode.so libm.so libm4u.so libmhalImageCodec.so libmp4enc_sa.ca7.so libmp4enc_xa.ca7.so All lib files between libmtkcamera_client.so libMtkVideoTranscoder.so libn3d3a.so libpng.so libSwJpgCodec.so libvc1dec_sa.ca7.so libvcodec_cap.so libvcodec_oal.so libvcodec_utility.so libvcodecdrv.so libvorbisidec.so

Boot :

boot.img-kernel [replace from stock to port] fstab.mt67xx [replace from stock to port] compare all init.67xx files
[K3 Note General] yui90:
Thank you sir, I will try now and give a report.
[K3 Note General] Jansxel:
[MENTION=5450421]sandeep.sethi[/MENTION] Can ROM from MT6750 be ported to MT6753 or MT6752?
[K3 Note General] sandeep.sethi:
yes
[K3 Note General] danielepescin:
Hello everyone! Is there Someone Who knows onda v919 4g mtk 8752 and if there is a stable cm rom for that device?

Thanks guys its a nice device but unfortunately no upgrade of android for it...
[K3 Note General] rahulsinh:
How to port rom to gionee f103

How to port mtk 6735 processor rom to mtk 6735 same processor i have gionee f103

Thx
[K3 Note General] ImArlet:
Hello

I have an very strange problem with ported rom...

Ported ROM: cm13

Stock ROM: 6.0

Kenel Version: 3.18.19

SoC: MT6753 64bit

Device: Just5 Freedom X1 (similar to Vernee thor or Elephone P6000)

Port ROM Device: Lenovo K4 Note

PROBLEM: Cant turn on device when reboot/turn off - port rom installed... Only Flashmode(VCOM) works to go back stock

Any Solution/Fix
[K3 Note General] Flounderist:
Is ported ROM booting or not? If doesn't boot at all check boot.IMG file.
[K3 Note General] sandeep.sethi:
what your flashable zip contains bro
[K3 Note General] sandeep.sethi:
follow my same chipset guide
[K3 Note General] ImArlet:
You need full file index?

But fist i managed to get it properly reboot by flashing all other partitons except "system, userdata, cache, boot and recovery"

And all the way important - i read somewhere that MTK LP & MM ported build has no working GPS and never will...is that true?
[K3 Note General] sandeep.sethi:
who said that GPS wont work

It is up to you if you can fix it (if you get bug)
[K3 Note General] VictorR9:
hey can you port this nougat rom for lenovo k3 note from the mad team they have fixed audio and video recording on jiayu s3 mt6752

http://www.mediafire.com/file/gqz9f6c7x6c9bjp/jiayu_s3-20161123-user.zip

Jiayu S3 Adv/Basic/Pro (mt6752) - Android 7.1

Build 20161123 - Stable 2

Changelog:

- Updated to NDE63X (security patch level: 6th November)

- fixed camera recording

- fixed all audio quality issues

- fixed NFC

- Updated bluetooth system (incall audio still broken :( )

- Added partial screenshot feature (long press on screenshot in power menu)

- Improved sim switch

- Fixed flashlight tile

- Various other improvements
[K3 Note General] sandeep.sethi:
Same Bug and its due to our tfa (sound driver problem) We have already ported this
[K3 Note General] :
works fyn on porting miui rom ... but unable to port cm 13 ... and bootloop occurs
[K3 Note General] sandeep.sethi:
dont replace all bin files
[K3 Note General] :
can i port cm13 if i have lollipop boot.img ?

it works but camera not work and audio not works ...

Is it problem of boot.img ?
[K3 Note General] sandeep.sethi:
it can be of boot.img or system i cant say because i dont have your device

you have to find out by the use of logcat
[K3 Note General] Alfredosp:
Blu pure xl MTK6795

Hello from Brazil Sandeep, my problem is theTesla 7.0 unnoficial for Redmi note 3 and i am trying to port for my BLU PURE XL same chipset mt6795.

Unssucessfull, error in update-script, error in update-binary and mount in wrong point.

Can you help me to port or if you can port this for me, tell me a value for this and if its good, i donate. Big hug and thank you so much. Alfredo
[K3 Note General] saurab007*_*:
To get mount points use mtk droid tools.
[K3 Note General] SanketMohapatra:
Bhai,I am also from BBSR.So I want to if I can use this guide to port ur rom to MT6735 or not .

Please have a look at the details of my mobile from google and tell if it will work.

Thanks

Sent from ls 4505 lyf flame 8
[K3 Note General] RawMain:
Same chipset (MT6795) SIM issues

Hello

SOC : MT6795

Kernel : 3.10.56 / 3.10.72

Android versions : 5.1

First of all thanks Sandeep for your instructions.

Following same chipset guide & fixing libraries for audio/camera/sensors I've managed to test some MT6795 (Helio X10) ports with ROM Android 5.1 based.

Yet - even though I restore IMEI (through MTK Engineer Mode and/or MAUI META ) & sim gets detected (it asks for unlock PIN) - I always get the "no service" message & I can't make calls or enable data connection with any ROM I've ported.

I've already checked with RIL files replacing, but nothing has changed. Do You have any suggestion ?
[K3 Note General] sandeep.sethi:
5.1 roms ported from Redmi Note 2?
[K3 Note General] RawMain:
Hello

Thanks for your reply.

The device I'm working on is AMOI L861 (aka Stonex One).

I'm porting Android 5.1 ROMS from Creo MARK 1 (AOSP-based) & PPTV King 7 (AOSP-based & FlyMe-port), that are devices having same SOC / GPU / Rear Camera / WiFi-Bluetooth / storage settings.

SIM gets detected (it asks for unlock PIN) & device also acknowledges radio support ON for SIM. Yet, it keeps on saying "NO SERVICE" even after I fix IMEI.
[K3 Note General] sandeep.sethi:
what things have you replaced could you say me
[K3 Note General] RawMain:
Hello

I've replaced :

- Kernel Zimage on boot.img

- system/etc/firmware & system/etc/mddb

- libraries related to audio / camera / sensors in system/lib - system/lib/hw - system/lib64 - system/lib64/hw

- MTK RIL files in system/bin - system/lib - system/lib64
[K3 Note General] sandeep.sethi:
In bootimg try replacing the files i have mentioned
[K3 Note General] SanketMohapatra:
Can the same thing be followed for MT6735?

Device : Gionee P5W
[K3 Note General] RawMain:
Hello

Thanks again. However nothing changes even comparing / replacing fstab & init.mt6795 files in RAMDISK.

It seems related anyway to a RIL/baseband mismatch even though I've followed instructions to replace etc/firmware + etc/mddb + RIL related libraries/files in /bin - /lib - /lib64 - /etc.

I've also tried to edit build.prop in order to match stock RIL/baseband settings with no changes = there are some differences since STOCK ROM is for single-sim device, while PORTED ROM is for dual-sim.

According to stock / port build.prop I have the following differences (see attached screenshots).

[IMG="Screenshot 1"]http://imgur.com/Fb4QNdn[/IMG]

[IMG="Screenshot 2"]http://imgur.com/yQtppyv[/IMG]

.

Do You have any suggestions ? Thanks in advance.
[K3 Note General] sandeep.sethi:
Yours is single sim?

If yes then that issue i too get that bug
[K3 Note General] RawMain:
Hello

Yes, AMOI L861 is a single-sim device while CREO MARK-1 & PPTV KING-7 are dual-sim with shared slot for 2nd SIM & SD Card.

Now I'm trying to edit only telephony part in framework.jar = when I edit telephony part in teleservices.apk (com.android.phone related) I get NO SIM DETECTED status.
[K3 Note General] sandeep.sethi:
Remove mtk-rilmd2.so and try and change dsds to dsda in buid.prop
[K3 Note General] RawMain:
Hello

I've done the replacements, removed mtk-rillmd2.so from /lib & /lib64, edited build.prop dsds->da... but it's not working yet = it still keeps on returning NO SERVICE state even after IMEI fixing with MAUI META or chamelephon app (after root).

When I go into settings \ cellular networks \ network operators, it allows searchs for available networks and returns an updated list according to the inserted SIM -> that's OK.

However when I try to manually register on SIM Telco's own 3G or 4G/LTE network it hangs with "Registering on..." message and nothing happens. Same when I try to manually register on roaming allowed Telco's network.

Besides, it doesn't allow me to switch preferred network connection type between 2G / 3G / 4G .

Notice : I haven't edited yet telephony section in smali-ed framework.jar .
[K3 Note General] sandeep.sethi:
I will find out about single sim files and let you know
[K3 Note General] arditjaha:
Does this work for mt6735 devices ? I have cubot dinosaur
[K3 Note General] RawMain:
Hello

In the end it seems that I've managed to get OK service status with such a 'weird' & mixed solution :

- Kernel : third last stock kernel-image (May 2016)

- Baseband : Even older stock APDB-MDDB files & secro.img (August 2015)

- RIL binaries/libraries : Original files from ported ROMs

- build.prop : dsds multisim settings & adapt RIL settings for modem-share/default values if required

At the present time I've managed to fix service issue on 3 L 5.1 Ported ROMs.
[K3 Note General] sandeep.sethi:
Very Nice :good:
[K3 Note General] RawMain:
Hello & Happy New Year

After having successfully ported 4 5.1 fastboot ROMs on AMOI L861 (unlockable bootloader) I've started to check/test following porting scenario such device :

==

- Port devices having Same CPU / GPU = MT6795 + PowerVR G6200

- Same Kernel Build for stock / port devices : 3.10.72+

- Stock Boot/ROM : Lollipop 5.1 (there isn't available any stock/custom 6.0.x ROM for L861)

- Port Boot/ROM : Marshmallow 6.0 / 6.0.1

I'm trying indeed to port Infinix Zero 3 & Sony Xperia M5 Android 6.0 official ROMs + CM13 (6.0.1) Unofficial port for PPTV King 7 = these 3 ROMs have same kernel build 3.10.72+ .

However, until now - removing DM-verity (,verify) in fstab.mt6795 & trying different replacements/editings for ramdisk init files - I'm experiencing the following situation = device boots, then stays up to max. 10 seconds on first logo, then reboots. According to init editings, it keeps on boot-looping, otherwise enters recovery at 2nd/3rd reboot.

ADB isn't available yet when everything happens (because before android system start) and this is last kmsg logged before recovery reboot :

ram console header, hw_status: 0, fiq step 0.
[ 0.106979]<5> (5)[1:swapper/0][SYS_CIRQ] cirq_num = 168
[ 0.106992]<5> (5)[1:swapper/0][SYS_CIRQ] spi_start_offset = 72
[ 1.253877]SysRq : Emergency Remount R/O
[ 1.454432]<0> (0)[1:init]Restarting system with command 'recovery'.

Instead getting a "CIRQ handler init success" I get a kernel failure for CIRQ Init.

Have You tried porting 6.0.x ROMS using kernel zImages extracted from 5.1 boot images and/or do You have any suggestion ?

I'm using Superr Kitchen v2.1.3.9 + plugins (AndroidImageKitchen / Carliv Kitchen) to unpack/repack 6.0.x boot images (in order not to mess with file ownerships/permissions).

Thanks in advance.
[K3 Note General] sandeep.sethi:
Using 5.1 kernel porting MM roms is always failure
[K3 Note General] RawMain:
Hello

Thanks.

We're indeed working on kernel sources in order to add Marshmallow support (cfr. selinux and other stuff).

We did our first trials using device/vendor of Elephone Vowney Lite (provided by team M.A.D. on their Github Repo) because of its common HW features.

However, we had some issues (mainly because of partial device tree), so now we're checking with other available device/vendor for MT6795 devices.
[K3 Note General] sandeep.sethi:
Very Nice

You can do it i have faith in you :good:
[K3 Note General] arditjaha:
Cubot dinsaur mt6735 works ?
[K3 Note General] yogi saka:
game rotation vector sensor not working on android 7. how to porting it ?
[K3 Note General] sandeep.sethi:
this thing you have to do yourself and check if working or not
[K3 Note General] sandeep.sethi:
do you have it in stock rom working?
[K3 Note General] Cpt.mactavish:
[MENTION=5450421]sandeep.sethi[/MENTION] I'm facing issue with offline charging animation...... Animation just comes up for a second and then it's gone....screen stays off...but.charging animation doesn't come up anymore when I press the power button once
[K3 Note General] sandeep.sethi:
kpoc_charger in bin/

and maybe symlinks issue
[K3 Note General] Cpt.mactavish:
What should I do? I Replaced that kpoc_charger from another working rom . now screen don't even get sleep...stays up with lenovo logo..what to do ?......is there anything to do for symlinks
[K3 Note General] Cpt.mactavish:
Well charging fixed :D now bluetooth headphone issue.....can hear calls but no music :( [MENTION=5450421]sandeep.sethi[/MENTION]
[K3 Note General] freibergisch:
Hi,

I edited a mt6735 CM14-project for getting it working on my mt6735-powered smartphone. After I copied the files you mentioned in your first post (some lib/hw files and the kernel inside the stock boot.img to port boot.img), the flashed installation does not boot. I stuck on the Android 6 Splash Screen.

Are there some more files to copy, or some more edits to do? I just copied some libs and the kernel. And now? Both are same chipsets (mt6735), so I hoped it would be easier to port the rom to my device.. Any hints?

Thank you :)

Edit: Want a port from Android 6 to 7.1
[K3 Note General] SanketMohapatra:
The problem is in your boot loader as well as your kernel which must be supported by the os

---------- Post added at 06:54 PM ---------- Previous post was at 06:53 PM ----------

I was stuck in a exactly same problem when i was porting cm 13 to my mt6582 phone but it was solved when i edited the mount points of the /system ,/data, /emmc of updater-script

---------- Post added at 06:59 PM ---------- Previous post was at 06:54 PM ----------

Devs, keep the work up ,i am also trying to port mt6735 ROM but can anyone give me a link to any other mt6735 cm 13/14 rom
[K3 Note General] sandeep.sethi:
your kernel should support android 7

and no need of bootloader

still try replacing full sbin folder in boot.img
[K3 Note General] SanketMohapatra:
Ok i am here again to help you a bit , if u have mt6735 board then you can search for lineage os from the links i have given and give it a try by porting it.

Remember to port sbin folder and all necessary other files

https://yadi.sk/d/ck_Dg5nE33W89D
[K3 Note General] freibergisch:
Thank you for helping me. I downloaded the lineage zip and edited the boot.img by copying the kernel file from stock android 6 boot.img to the port-boot.img without any success. (flashed the ROM with my edited boot img but it stucks on the android 6 splash screen)

BTW: Is my kernel (not 3.10.x) related to this issues?

Then I copied the etc/firmware and /mddb folder to the port-folders and tried it again, without success, again. I see the android 6 screen, all the time.

I do not know what I made wrong, but there must be some mistakes I did. Something I did not copy, maybe.. Strange... Every step leads in stucking on splash screen... Strange...

My kernel version is 3.18.19..

sbin folder from stock boot.img to port-boot.img is also there..
[K3 Note General] sandeep.sethi:
you are using stock kernel to boot Nougat ?

It wont boot