[ROM][UNOFFICIAL][7.1.2][NIKEL] LineageOS-14.1 For Xiaomi Redmi Note 4

[BelalElbeik]

That's because it's not MIUI 9 yet, it's coming in September for Nikel.

---------- Post added at 09:48 AM ---------- Previous post was at 09:47 AM ----------





Not unless the 4X is also named Nikel.

Hmm....x.x I see neither of them named like that o.o...sorry dunno a lot about xiaomi devices and their roms

 

[LewAngell]

In this link below, there is a ROM version dated 08/22.
Anyone know if there is a bug yet ???

https://www.androidfilehost.com/?w=files&flid=201596

 

[Davenron]

Hi,

I installed it an hour ago, but something is not ok with this build. In my case it hanged at boot animation (previous one from 0812 was loading correctly). Clearing dalvic, cache didnt helped

Im waiting for working cam too

Best regards, KB

 

[nedpals]

This would be very confusing but...
Redmi Note 4 (India) / Redmi Note 4X (China) = MIDO
Redmi Note 4 (China) / Redmi Note 4X(Global) = NIKEL

 

[Davenron]

This would be very confusing but...
Redmi Note 4 (India) / Redmi Note 4X (China) = MIDO
Redmi Note 4 (China) / Redmi Note 4X(Global) = NIKEL

Snapdragon Version is MIDO & Mediatek Version in Nikel
Processor is different.

 

[nedpals]

Thanks for reply... That means there is no need to install this rom. We made a big mistake by buying mediatek note 4. Stuck at marshamallow... Even my samsung S4 still the best with all latest custom roms compatibility... Feel so much bad... Xiaomi even didn't update it to nougat...

It's not just Xiaomi but also MediaTek. Qualcomm released sources for 625 chip used in 4X that made Xiaomi possible to update the os.

 

[LewAngell]

In this link below, there is a ROM version dated 08/22.
Anyone know if there is a bug yet ???

https://www.androidfilehost.com/?w=files&flid=201596

Anyone testing this Lineage 7.1.2 update???
Any bug???

 

[Davenron]

Anyone testing this Lineage 7.1.2 update???
Any bug???

Around #63 was discussion about this build from 0822. It does not work. I does not want to boot.

Best regards

 

[Vainpixel]

Hello! Sorry guys but I'm a bit confused, yes，4x（4G RAM version）uses x20，too

 

[xxx01x]

Anyone testing this Lineage 7.1.2 update???
Any bug???

Hello! I tested this rom and it did not boot so I will wait the oficial lineageos for this device. Maybe some day it will come

 

[joead2010]

installation error

after the installation displays a black screen which says '' cause of broken files you need to reset system press here ....ect'' but still nothing happens what can i do ?

 

[zoltan1]

fingerprint scanner not working

 

[JohnMelson]

Hello! I tested this rom and it did not boot so I will wait the oficial lineageos for this device. Maybe some day it will come

As I know, there's no official LineageOS for Xiaomi MTK devices. So don't hope. The best thing we can expected now is Unoffical LineageOS or MIUI 9.

 

[xxx01x]

That's right!

 

[BaBuJI0H]

after the installation displays a black screen which says '' cause of broken files you need to reset system press here ....ect'' but still nothing happens what can i do ?

You need to wipe data in TWRP
Go to Wipe - Data (button) then swipe to give rights to wipe and then install ROM
It will work

 

[joead2010]

You need to wipe data in TWRP
Go to Wipe - Data (button) then swipe to give rights to wipe and then install ROM
It will work

I did this but the result it's the same

 

[yarden95]

Should I install this rom is it usable? Calls internet and stuff?
Thanks

 

[Davenron]

Hi,

Any1 managed to build lineage using sources published by SamarV-121 and run it on device?

I tried to build sources from:
https://github.com/SamarV-121/android_device_xiaomi_nikel
https://github.com/SamarV-121/android_vendor_xiaomi_nikel

Build is successfull, but image does not want to boot after instalation on the device,

I tried:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="SamarV-121/android_device_xiaomi_nikel" path="device/xiaomi/nikel" remote="github" revision="cm-14-1" />
<project name="SamarV-121/android_vendor_xiaomi_nikel" path="vendor/xiaomi/nikel" remote="github" revision="cm-14.1-2" />
</manifest>


And:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="SamarV-121/android_device_xiaomi_nikel" path="device/xiaomi/nikel" remote="github" revision="cm-14-1" />
<project name="SamarV-121/android_vendor_xiaomi_nikel" path="vendor/xiaomi/nikel" remote="github" revision="cm-14.1" />
</manifest>

Image is building successfully, but after instalation via TWRP device does not want to boot. Any1 can send me working branch combination?

Any1 tried to build working OS from those sources?

I always receiving CPU is going to die:

<4>[ 57.218734] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.218791] (0)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.219501] (0)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.219717] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.219756] (0)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.228990] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.229030] (0)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<3>[ 57.229703] (0)[241:mtk-tpd]<<-GTP-ERROR->> buffer not ready
<4>[ 57.239531] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.239570] (0)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.240237] (0)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.240311] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.240348] (0)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<7>[ 57.241254] (0)[63:cfinteractive][name:mt_cpufreq&][Power/cpufreq] @_CPufreq_set_locked(), MT_CPU_DVFS_LL15,0): freq=897000(897000), volt =92000(92000), on=1, cur=221000, cci(169000,533000)
<4>[ 57.249542] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.249552] (0)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.250072] (0)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.250091] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.250101] (0)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.260051] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<6>[ 57.260060] -(1)[0:swapper/1]Detected VIPT I-cache on CPU1
<6>[ 57.260078] -(1)[0:swapper/1]CPU1: found redistributor 1 @ffffff80000a0000
<4>[ 57.260094] (0)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<6>[ 57.260199] -(1)[0:swapper/1]CPU1: update cpu_capacity 316
<4>[ 57.260645] (0)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.260680] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.260690] (0)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.262209] (1)[215:hps_main][HPS] (0xFF00)<1>(0)(0) action end (99)(200)(0) (0)(0)(0) (4)(0)(0)(1)(0)(0) (0)(0)(200)(1) <2>(0)(0)
<4>[ 57.270225] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.270246] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.270793] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.270821] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.270830] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.280537] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.280558] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.281123] (0)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.281153] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.281162] (0)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<3>[ 57.288328] (1)[265:recovery][DISP][_config_ovl_input #4739]ERROR:invalid overlayed layer num 4, fix it to 2
<3>[ 57.288452] (1)[265:recovery][DISP][_config_ovl_input #4739]ERROR:invalid overlayed layer num 4, fix it to 2
<4>[ 57.290801] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.290812] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.291350] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.291378] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.291386] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.301076] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.301086] (0)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.301609] (0)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.301625] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.301633] (0)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.311406] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.311415] (0)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.311934] (0)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.311948] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.311956] (0)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.321699] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.321707] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.322224] (0)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.322239] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.322246] (0)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.332056] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.332077] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.332675] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.332715] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.332724] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.342368] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.342388] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.342942] (0)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.342969] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.342977] (0)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.352716] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.352738] (0)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.353303] (0)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.353336] (0)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.353344] (0)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<3>[ 57.354454] (1)[265:recovery][DISP][_config_ovl_input #4739]ERROR:invalid overlayed layer num 4, fix it to 2
<3>[ 57.354569] (1)[265:recovery][DISP][_config_ovl_input #4739]ERROR:invalid overlayed layer num 4, fix it to 2
<4>[ 57.362984] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.363007] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.363547] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.363575] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.363583] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.373299] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.373319] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.373858] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.373884] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.373892] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<7>[ 57.381230] (1)[63:cfinteractive][name:mt_cpufreq&][Power/cpufreq] @_CPufreq_set_locked(), MT_CPU_DVFS_LL15,0): freq=1391000(1391000), volt =112000(112000), on=2, cur=1222000, cci(754000,923000)
<4>[ 57.383655] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.383676] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.384242] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.384273] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.384280] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<3>[ 57.388146] (0)[265:recovery][DISP][_config_ovl_input #4739]ERROR:invalid overlayed layer num 4, fix it to 2
<3>[ 57.388228] (0)[265:recovery][DISP][_config_ovl_input #4739]ERROR:invalid overlayed layer num 4, fix it to 2
<4>[ 57.394031] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.394052] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.394586] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.394611] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.394618] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.404478] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.404496] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.405031] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.405054] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.405060] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.414557] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.414575] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.415129] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.415159] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.415166] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<3>[ 57.419210] (0)[265:recovery][DISP][_config_ovl_input #4739]ERROR:invalid overlayed layer num 4, fix it to 2
<3>[ 57.419314] (0)[265:recovery][DISP][_config_ovl_input #4739]ERROR:invalid overlayed layer num 4, fix it to 2
<4>[ 57.424915] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.424940] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.425657] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.425710] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.425720] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.435184] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.435203] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.435747] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.435771] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.435778] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.445476] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.445496] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.446033] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.446055] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.446062] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<3>[ 57.452566] (0)[265:recovery][DISP][_config_ovl_input #4739]ERROR:invalid overlayed layer num 4, fix it to 2
<3>[ 57.452647] (0)[265:recovery][DISP][_config_ovl_input #4739]ERROR:invalid overlayed layer num 4, fix it to 2
<4>[ 57.455760] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.455767] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.456296] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.456319] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.456326] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.462820] (1)[215:hps_main][Power/PPM] (0x210)(10620)(1)[LL_ONLY]->[L_ONLY]: (15)(0)(0)(0) (8)(0)(1)(4) (15)(0)(0)(0)
<3>[ 57.462839] (1)[215:hps_main][hps_task_wakeup_nolock]hps task wake up fail 0
<6>[ 57.465129] -(4)[0:swapper/4]Detected VIPT I-cache on CPU4
<6>[ 57.465203] -(4)[0:swapper/4]CPU4: found redistributor 100 @ffffff8000100000
<6>[ 57.465442] -(4)[0:swapper/4]CPU4: update cpu_capacity 432
<4>[ 57.466112] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_read, 890
<4>[ 57.466125] (1)[241:mtk-tpd]~~liml_tp i2c_read_bytes_non_dma, 840
<4>[ 57.466675] (1)[241:mtk-tpd]~~liml_tp tpd_calibrate_driver, 2418
<4>[ 57.466700] (1)[241:mtk-tpd]~~liml_tp gtp_i2c_write, 1010
<4>[ 57.466707] (1)[241:mtk-tpd]~~liml_tp i2c_write_bytes_non_dma, 958
<4>[ 57.467704] (4)[215:hps_main][Power/cpufreq] MT_CPU_DVFS_L freq = 325000
<3>[ 57.467751] (4)[215:hps_main][CPUHVFS] (0) [001bcaac] cluster1 on, pause = 0x0, swctrl = 0x27f0 (0xfd200)
<6>[ 57.469411] -(5)[0:swapper/5]Detected VIPT I-cache on CPU5
<6>[ 57.469423] -(5)[0:swapper/5]CPU5: found redistributor 101 @ffffff8000120000
<6>[ 57.469536] -(5)[0:swapper/5]CPU5: update cpu_capacity 432
<6>[ 57.470441] (5)[215:hps_main]MobiCore mcd: Cpu 1 is going to die
<5>[ 57.471278] (5)[215:hps_main]CPU1: shutdown
<6>[ 57.472157] (5)[215:hps_main]psci: CPU1 killed.
<6>[ 57.472800] (5)[215:hps_main]MobiCore mcd: Cpu 1 is dead
<6>[ 57.473052] (5)[215:hps_main]MobiCore mcd: Cpu 0 is going to die


Best regards, Konrad

 

[Vainpixel]

Wishing for your early update...

 

[KonterBiER]

Is there an ETA for an update with working camera?