Database Users

Android 5.0 - Lollipop

I know - now - is too early, but any plans to prepare Android 5.0 for Mi2S?

Bucci said:
I know - now - is too early, but any plans to prepare Android 5.0 for Mi2S?
Click to expand...
Click to collapse
Officially I don't think so.
By the way I guess Cyanogen will support CM12 for our Mi2S, so we shoud have ROMs L based.

I hope the same, the only official is miui (currently v5 - but plan v6 - problem is on 4.1.2)
I hope CM12 or another CM/AOSP roms should be available for Mi2S

i think that L for mi2s is sure. In fact nexus 4,which has the same HW of mi2s, will be updated officially by google.
In my opinion the big challenge is to achieve 3.10 from our 3.4 kernel

only when m11kkaa will work on it **** miui they suck :silly:

http://m.weibo.cn/u/1697247850

If we knew Chinese, we will know that Autumn Ivan prepares a Lollipop AOSP for MI2s

@akiba is already working on it! So it seems we will have Lollipop based system in our Mi2S:
I wanted to share clickable link for it but not allowed, anyway copy it to address bar with prefix www as usual:
gizchina.com/2014/11/06/breaking-xiaomi-mi2-spotted-running-android-5-0-lollipop/
...but I hope M1cha already working also on Lollipop based CM12 for Mi2S.

CM12 work in progress: https://plus.google.com/app/basic/p...ovi&sview=25&cid=5&soc-app=115&soc-platform=1

Lollipop is here
http://en.miui.com/thread-61384-1-1.html
Android 5 is Up! Thanks to IVAN
...Hours after using it.
I cannot achieve rooting this device, with any Superuser or SuperSU flashable ZIP, neither with xbin/su from ALL CHINISE 6.0.5.1 Ivan Unofficial CWM (OMG). It doesn't officialy support TDB (I don't care, i just mention that), it has not GAPPS but ok, there is a package for Lollipop ready on the Web, and it fits to Mi2s ROM space, without Micha's repartitioning (i think the 4.4.x GAPPS was junk in terms of size as i check that Lollipop needs half the size of 4.4.x). Advanced Reboots don't worked, CM buttons for App kill, neither. But it's a very early stage (alpha i think) and it doesn't have bugs, it works, it boots, you can test it, but not for every day ROM, avoid it, wait for CM12, or sth better from OmniROM
PS. BACKUP everything, and of course, have ready to flash back the Micha's CWM 6.0.5.0. because with the Chinese Recovery i am facing psychological issues.
PS2. After these hours of testing, i am back to CM11 Latest Snapshot!
PS3. You should turn off TDB before flashing Lollipop.
PS4. Again, wait for a release!

"if you have flashed CWM 6.0.5.0, you can flash latest CM11, go to settings "about phone" and set checkbox "update recovery" and reboot. CWM will be 6.0.5.1 english"
M1cha,
can you confirm it? Thanks?

graw2 said:
"if you have flashed CWM 6.0.5.0, you can flash latest CM11, go to settings "about phone" and set checkbox "update recovery" and reboot. CWM will be 6.0.5.1 english"
M1cha,
can you confirm it? Thanks?
Click to expand...
Click to collapse
I don't have such option. Am on Mokee. But I also couldn't find any other link to CWM 6.0.5.1. Can somebody provide such a link?

no_means_no said:
I don't have such option. Am on Mokee. But I also couldn't find any other link to CWM 6.0.5.1. Can somebody provide such a link?
Click to expand...
Click to collapse
there is a link to CWM 6.0.5.1 http://en.miui.com/thread-61143-1-1.html
but who has 6.0.5.0 no necessary to change it just be aware to install and setup system1 only

It looks better then I expected, cant wait to use this with Xposed Framework!
Would love it to look more like KitKat though, it just looks more professional.
Why no screencast?
Well, because I thought this was faster and easier... plus you get to see the M2(S) and the M2S has a great screen which still looks great on video.. I was just amazed by the speed of 5.0

Why didn't you screen cast, i know it works?
btw, thanx for the video

Robin>Hood said:
It looks better then I expected, cant wait to use this with Xposed Framework!
Would love it to look more like KitKat though, it just looks more professional.
Why no screencast?
Well, because I thought this was faster and easier... plus you get to see the M2(S) and the M2S has a great screen which still looks great on video.. I was just amazed by the speed of 5.0
Click to expand...
Click to collapse
xposed won't be released for lollipop

bobanbg said:
xposed won't be released for lollipop
Click to expand...
Click to collapse
Source?
The Xposed developer said that's difficult 'cause ART, but he didn't say that he will not release Xposed at all.

bobanbg said:
xposed won't be released for lollipop
Click to expand...
Click to collapse
Lol.... says who? I totally agree with @Fortinho .... Rovo has never said it won't come, it's just a matter of if and when
And otherwise I'll just go with CM12 ^^
Btw... Impressive Antutu score on the M2S:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

no_means_no said:
I don't have such option. Am on Mokee. But I also couldn't find any other link to CWM 6.0.5.1. Can somebody provide such a link?
Click to expand...
Click to collapse
I have tried the solution what I asked here and working perfectly! So easy to change from CWM6.0.5.0 to CWM6.0.5.1 and keep English CWM menu language. I f you just simple flash CWM 6.0.5.1 than it will be Chinese...

Only problem is, I have tried to clean install CM11 NIGHTLY on system2 and it has stacked at boot logo, but I have successfully installed sMIUI onto system 1. What is the reason? (CWM recovery version is 6.0.5.1 )
Thanks for your reply in advance!

[Lollipop] 1033xt GPE Converted devices Discusssions

Edit : All issue is solved now check this post
Hi
This post is only intended for GPE converted 1033 users. i've seen many guys complaining in Dev section.
im a GPE converted 1033 user since the day i unlocked the bootloader.
in recent past had a issue with all the CM12 based roms like
1. Encryption Error due to EXT4 partition
2. WiFi wont work (CM integrated wifi modules into kernel)
3. Roms recognize my device as Dual SIM after converting to GPE
4. Continuous System UI force closes
earlier, all this problem solved by flashing Donkey Kang Kernel. Recently dev of DKK stopped support for our device
Solution
as a workaround till our devs fix the issue with GPE converted 1033 devices. i took DKK3.8 kernel and CM12 Based Boot.img (exactly RR rom) made a new boot.img which works for me without above mentioned problems. i'm just sharing my experience here. if you feel this workaround is useful please confirm
summary
RAMDISK form DKK3.8
Zimage from CM12 based Kernel(Integrated WiFi Modules)
How to install.
the provided file is boot.img directly (not a flashable zip. )
Latest TWRP supports flashing img files directly. please make use of it else you can also use apps like rashr which is available in playstore.
please make sure you know what you are doing before messing with your device.
PS : i'm not a developer
Edit : i tested with Resurrection Rom and i can confirm everything works as a single sim device on GPE converted 1033
Edit1 : tested with validus build 17-01 works prefectly
Edit2 : all credits to the developers

tell me the changes needed i'll rebuild my base around it..

bharat_goku said:
tell me the changes needed i'll rebuild my base around it..
Click to expand...
Click to collapse
Actually the problem started when cm integrated WiFi modules into the kernel.
Also when i compare ram disk. gpe check has changed in the recent kernels. Earlier separated fstab available for gpe device Now its merged
In my op the boot.IMG consists of ramdisk from DKK 3.8 and zimage from latest cm source

reversegear said:
Actually the problem started when cm integrated WiFi modules into the kernel.
Also when i compare ram disk. gpe check has changed in the recent kernels. Earlier separated fstab available for gpe device Now its merged
In my op the boot.IMG consists of ramdisk from DKK 3.8 and zimage from latest cm source
Click to expand...
Click to collapse
Can these changes be merged in official cm?? @bharat_goku can u pls tell me??
Sent from my Moto G using XDA Free mobile app

Differences between stock kernel and modified kernels
Stock kernel device recognised as dual sim in terminal
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Modified kernel device recognised as gpe in terminal

Flashhhh said:
Can these changes be merged in official cm?? @bharat_goku can u pls tell me??
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
Does this work for u

reversegear said:
Does this work for u
Click to expand...
Click to collapse
I haven't tested yet but it should work
Sent from my Moto G using XDA Free mobile app

can i flash this boot.img on donkey kang kernel or should reflash rom and then flash boot.img?
edit:just flashed it using rashr app on candy rom above donkey kernel and everything is fine...thanks for this fix

Will try now..

worked for me
This worked for me. I couldn't receive SMS after flashing any ROM. Now I can receive. Also my phone is being detected as gpe single sim now. But I have a query. Would multitasking be affected by changing this boot.img ? Or it is only just for setting up boot correctly. Please if u can elaborate. Sorry for being noob.

prasoon27 said:
This worked for me. I couldn't receive SMS after flashing any ROM. Now I can receive. Also my phone is being detected as gpe single sim now. But I have a query. Would multitasking be affected by changing this boot.img ? Or it is only just for setting up boot correctly. Please if u can elaborate. Sorry for being noob.
Click to expand...
Click to collapse
as far as multitasking is concerned it is as good as CM12 roms.
this link might be useful if you are concerned about multitasking http://forum.xda-developers.com/moto-g/general/fix-lmk-fixer-adj-t3007589

reversegear said:
as far as multitasking is concerned it is as good as CM12 roms.
this link might be useful if you are concerned about multitasking http://forum.xda-developers.com/moto-g/general/fix-lmk-fixer-adj-t3007589
Click to expand...
Click to collapse
Thanks for the response. You are right, there are no multitasking issues.

Working perfectly for me... flickering issue also stopped... Super smooth now... using Crdroid..

padhu1989 said:
Working perfectly for me... flickering issue also stopped... Super smooth now... using Crdroid..
Click to expand...
Click to collapse
what is that Flickering issue..
bcoz i never came across Flickering issue with my device.

reversegear said:
what is that Flickering issue..
bcoz i never came across Flickering issue with my device.
Click to expand...
Click to collapse
i think it happen to people who updated to stock lollipop or something like that...i never enconter it too bcz i never gone back to stock

I found the cause of this "bug" gpe converted. In cm11 when has the file persist.radio.multisim.config empty into /data/property is recognized as single sim (the file is created automacally on reboot, even if manually delete). Donkey lp too don't create this file automatically in cm12 (what hack he used i don't know), but if create manually or made a dirty flash from cm11 all kernels recognized as single sim (due file created on cm11), if delete or made a factory reset cm12 back to be recognized as dual.
I hope that info help devs to fix in official roms :fingers-crossed:

Update on the way
In the mean time : anyone using this modified kernel pls confirm whether compass tile works in cm12 based ROMs
For me it is struck in initializing

reversegear said:
Update on the way
In the mean time : anyone using this modified kernel pls confirm whether compass tile works in cm12 based ROMs
For me it is struck in initializing
Click to expand...
Click to collapse
Yeah it not working on rr it getting stuck on initializing

reversegear said:
Solution
as a workaround till our devs fix the issue with GPE converted 1033 devices. i took DKK3.8 kernel and CM12 Based Boot.img (exactly RR rom) made a new boot.img which works for me without above mentioned problems. i'm just sharing my experience here. if you feel this workaround is useful please confirm
Click to expand...
Click to collapse
Based on your solution I've been looking at the RAMDISK of the Donkey Kernel and found that the only file that is required to start system as GPE is his "init" binary within the ramdisk. I've tried with 3 differents kernels from AOSP based roms and worked.

ren2r said:
Based on your solution I've been looking at the RAMDISK of the Donkey Kernel and found that the only file that is required to start system as GPE is his "init" binary within the ramdisk. I've tried with 3 differents kernels from AOSP based roms and worked.
Click to expand...
Click to collapse
Glad to here that..
You can share ur boot.img here with the permission of the actual kernel/rom developers. by giving them credits
Does compass tile work in ur modified kernel
Edit:
I never knew still so many GPE converted 1033 users on XDA :happy:

UPDATE 71 Working(WARNING - Do Not Flash Xposed Framework arm64)

UPDATE! Latest version flashes fine
Just a heads up there at least 2 of us who have flashed Xposed Framework arm64 who are now stuck in a boot loop, whilst we don't have access to any Stock H815 Firmware (or any LG G4 firmware) at the moment we are kind of stuck, I was dumb and don't even have a nandroid to fall back on but others have reported that their nandroid failed to restore anyway. So for the time being steer clear of Xposed on the G4. I can still get into recovery so at least when something does come along i'll be able to try and recover it.
Update: We now have a fully working stock Rom and an updated TWRP that allows you to restore your nandroids so don't despair you can now recover if you missed this warning.

So people who have done a full backup in twrp are unable to boot after restoring the backup?

LancerV said:
So people who have done a full backup in twrp are unable to boot after restoring the backup?
Click to expand...
Click to collapse
No they are unable to restore the backup at all
The bootloop is caused by flashing Xposed Framework

DarthEwok said:
No they are unable to restore the backup at all
The bootloop is caused by flashing Xposed Framework
Click to expand...
Click to collapse
Super alpha software on a just released phone isn't always the best idea. But curious can you get into recovery? And if so disable xposed through the file explorer

There is another thread here asking for the system.img. I plan to dump mine tomorrow when I receive my H815. Will this also help you?
http://forum.xda-developers.com/g4/help/h815-dump-t3126629

The main problem here is that the G4 may not be running in 64 bit mode just 32 bit

macdaddie87 said:
The main problem here is that the G4 may not be running in 64 bit mode just 32 bit
Click to expand...
Click to collapse
No
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

macdaddie87 said:
The main problem here is that the G4 may not be running in 64 bit mode just 32 bit
Click to expand...
Click to collapse
I don't think it is either at least not US version. The processor supports it but not sure it is yet
Sent from my S5 using your mom

LancerV said:
No
Click to expand...
Click to collapse
The kernal maybe 64bit because the chip is 64bit and the kernal contains the drivers. The libs that LG has compiled maybe compiled as 32bit. This makes sense that LG would do it like this since they have plans to bring UX 4.0 to the G3 and possibly the G2. They would have to compile UX 4.0 from the ground up to make it completely 64bit. Then compile a 32bit version of UX 4.0 for the previous models.

macdaddie87 said:
The kernal maybe 64bit because the chip is 64bit and the kernal contains the drivers. The libs that LG has compiled maybe compiled as 32bit. This makes sense that LG would do it like this since they have plans to bring UX 4.0 to the G3 and possibly the G2. They would have to compile UX 4.0 from the ground up to make it completely 64bit. Then compile a 32bit version of UX 4.0 for the previous models.
Click to expand...
Click to collapse
... The os is 64. The 64 bit libs are there.

LancerV said:
No
Click to expand...
Click to collapse
Lance-
Could you tell me which app you are using in that screenshot?
thanks.

sideone said:
Lance-
Could you tell me which app you are using in that screenshot?
thanks.
Click to expand...
Click to collapse
Terminal Emulator

LancerV said:
Terminal Emulator
Click to expand...
Click to collapse
thanks, now i feel at home on my g4.

jupp, did the same mistake, this saved me:
http://forum.xda-developers.com/g4/development/rom-h815-10a-stock-rooted-rom-t3129036

Anyone hear anything regarding an ETA on this working on our phone?

The LG stock rom is odexed; I think the rom needs to be deodexed b4 Xposed Framework can be installed (working on it). Will report back

Sounds good, did you have any luck?

Are you guys trying to flash xposed for 5.0.1 or the one for 5.1? Rovo89 is still working on his xposed for 5.0, but there's another for 5.1 not by him.

I have been able to deodex the rom, but it is not booting (bootloop) so there is an error somewhere in the deodexed rom. Still looking I want a bootable deodexed stock rom first, then I will be able to try to install Xposed Framework again.
I have tried flashing the special version for arm64/sdk22 but no luck so far (ends in bootloop) on the odexed stock rom. Nandroid backup to the rescue!
Edit 1: deodexed system/app and system/priv-app: G4 boots but FC errors with NFC/Bluetooth. Deodexed framework results in bootloop. When i have more time i will try to get a logcat while in bootloop with deodexed framework.
Edit 2 (20-06-2015): edited a flashable zip i found to set stock kernel to permissive/not enforcing (and the zip works) (still can't install xposed though...)

mimefly said:
I have been able to deodex the rom, but it is not booting (bootloop) so there is an error somewhere in the deodexed rom. Still looking I want a bootable deodexed stock rom first, then I will be able to try to install Xposed Framework again.
I have tried flashing the special version for arm64/sdk22 but no luck so far (ends in bootloop) on the odexed stock rom. Nandroid backup to the rescue!
Click to expand...
Click to collapse
I spent many hrs trying to install Xposed. Boot loop every time.
One later version of the arm64/sdk22 zip, did appear to install the framework, but red messag"... wrong chip or architecture..".
Thanks to Team Win, the phone works but not in use. Waiting for Xposed.
If you can fix this issue you'll be very popular!
Yes a de-odexed ROM could help here.
Wonder why no custom ROM yet. The G4 (h815) was unlocked in May.
Will look out for your next post.

Kernel install problem plz help

Hello Guys, I'm living in Korea and I use G900K Korean Variants.
I want to install custom kernel but there are no kernel for korean model.
Can I install G900F's Kernel to my device..? I really want to use custom kernel.
SM-G900K Darthrom EDGE V2.4

Hi. The G900K has the same hardware like the G900F. Perform a nandroid backup and flash a custom kernel from the G900F of your choice. Theoretically it must work.

Umm....I tried it..
Solvin said:
Hi. The G900K has the same hardware like the G900F. Perform a nandroid backup and flash a custom kernel from the G900F of your choice. Theoretically it must work.
Click to expand...
Click to collapse
But after I flash the kernel.. my phone can't boot and into the Odin mode (could not do normal boot )

1. You flashed which kernel?
2. Do you flashed a recovery like TWRP or CWM?
3. Do you have a stock Touchwiz rom?

Re:
Solvin said:
1. You flashed which kernel?
2. Do you flashed a recovery like TWRP or CWM?
3. Do you have a stock Touchwiz rom?
Click to expand...
Click to collapse
1. Speedy kernel or Boeffla and etc. Which support G900F
2.Philz Touch (do you know?)
3.Not stock but touch wiz rom

Ok your phone is booting right now? I mean you flashed the original kernel back?
Don't use Philz because the development and support was stopped. Philz is out of date. Use TWRP or CWM, both recoverys have a touch function like Philz.
Please note that you have to flash the correct Boeffla kernel for your Rom Version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You say you have TW but a modified version. I don't know if that works with Boeffla kernel. You can try the kernel Samsung stock stable 1.2
If that does not work, than your Rom is not supported.

Solvin said:
Ok your phone is booting right now? I mean you flashed the original kernel back?
Don't use Philz because the development and support was stopped. Philz is out of date. Use TWRP or CWM, both recoverys have a touch function like Philz.
Please note that you have to flash the correct Boeffla kernel for your Rom Version.
View attachment 3464621
You say you have TW but a modified version. I don't know if that works with Boeffla kernel. You can try the kernel Samsung stock stable 1.2
If that does not work, than your Rom is not supported.
Click to expand...
Click to collapse
OK then your conclusion is 'change recovery' right?
Have to go to change my recovery.
If it failed, I will return and report. Thx

No that's not a problem of your recovery. That was only a information for you
I don't know...Boeffla kernel supports Darthrom Edge Rom? I don't think so.

Solvin said:
Hi. The G900K has the same hardware like the G900F. Perform a nandroid backup and flash a custom kernel from the G900F of your choice. Theoretically it must work.
Click to expand...
Click to collapse
Hey Solvin. I have a G900W8, would you also know if it has the same hardware as the G900F?

The only difference between G900W8, G900K and so on are the frequencies and basebands for GSM, LTE etc.
This things are included in your modem file and has nothing to do with the kernel or the used rom.
You have which rom? CyanogenMod? Touchwiz? Try to flash a kernel. Should the phone goes into a bootloop go back to recovery mode and flash your currently used rom again (the rom includes the original kernel).
I would try it to flash. But for the best safety: Perform always a nandroid backup before you flash.

Solvin said:
The only difference between G900W8, G900K and so on are the frequencies and basebands for GSM, LTE etc.
This things are included in your modem file and has nothing to do with the kernel or the used rom.
Click to expand...
Click to collapse
Thanks for the reply! I will be flashing custom roms soon. However, some mention that I have to get their own bootloader to use it, and again they say they are for the G900F. Just to confirm what you've mentioned earlier, since its only basebands that are altered in different variants, I should be able to use a G900F bootloader on my G900W8, correct?

Solving..?
Thanks for your advice. I think I Partially solve this problem.
Use Android Image Kitchen to extract boot.img into Ramdisk and split img,
And change boot.img-dtb with my korean kernel's boot.img-dtb.
Then I tryed to input kernel. and it success to boot!!
But small problem like earphone is in.

Gu1da said:
Thanks for the reply! I will be flashing custom roms soon. However, some mention that I have to get their own bootloader to use it, and again they say they are for the G900F. Just to confirm what you've mentioned earlier, since its only basebands that are altered in different variants, I should be able to use a G900F bootloader on my G900W8, correct?
Click to expand...
Click to collapse
You can try to use the other bootloader from the new rom, but before you do that download the original bootloader from the G900W8 to flash it back via odin, if you are in a bootloop. The G900W8 has no locked bootloader, you are free to flash and flash again.

Solvin said:
You can try to use the other bootloader from the new rom, but before you do that download the original bootloader from the G900W8 to flash it back via odin, if you are in a bootloop. The G900W8 has no locked bootloader, you are free to flash and flash again.
Click to expand...
Click to collapse
Thanks again, just concerned about bricking my phone.
Regarding your issue Kim, try plugging in and unplugging a pair of earphones. The issue happens on mine sometimes and that usually fixes it, but I doubt the solution is that simple in your case. Worth a shot.

[ROM][STOCK][7.1.1] ErfanROM | Flashable ZIP

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
###Disclaimer###
I am not responsible if your phone will be damaged, broken, boot looping.
YOU are choosing to make these modifications and accept the fact that something might go wrong.
The main goal of this ROM is to enjoy the Stock Rom without any visual changes fully stock, clean & stable​
Features :
Based on Latest Stock ROM
Force Encryption Disabled
DM Verity Disabled
Partitions trimmed for better performance
Requirements :
Unlocked Bootloader
TWRP Recovery
How To Flash :
Download the latest build
Take a nandroid backup
Recommended(Optional) - Full wipe and factory reset
Flash ROM using latest TWRP 3.x Recovery
Reboot.
Enjoy!
How to root?
Just flash latest magisk
Download :
Download ErfanROM Here
Firmware Dumps :
NPL26.118-20 Dump : Download
NPLS26.118-20-1 Dump : Download
NPL26.118-20-5 Dump : Download
NPLS26.118-20-5-8 Dump : Download
System Image and Boot taken from OTA with IMG Patch Tools
XDA:DevDB Information
ErfanROM for Griffin, ROM for the Moto Z
Contributors
erfanoabdi
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader, TWRP
Based On: Stock
Version Information
Status: Stable
Created 2017-07-26
Last Updated 2017-12-08

Reserved

Any luck with fixing wifi yet - as you mentioned in another thread a few days back that some have issued with wifi?
Thanks.!

Nice! Is the modem image upgraded? (New WiFi firmware for example)
I don't know in detail how much stuff Lineage use from the stock firmware (modem, binary blobbs or whatever they are called). So the question is would it benefit to flash?
Sent from my XT1650-03 using Tapatalk

I'm on Stock 7.0 (NPLS25.86-86-30-12 APRIL PATCH). Can I flash this Rom or do I have to be on 7.1.1?

bert269 said:
Any luck with fixing wifi yet - as you mentioned in another thread a few days back that some have issued with wifi?
Thanks.!
Click to expand...
Click to collapse
Wifi fix is on thread
swejuggalo said:
Nice! Is the modem image upgraded? (New WiFi firmware for example)
I don't know in detail how much stuff Lineage use from the stock firmware (modem, binary blobbs or whatever they are called). So the question is would it benefit to flash?
Click to expand...
Click to collapse
You can try it but we're using old moto driver on LOS, test and report back
bullfinch110 said:
I'm on Stock 7.0 (NPLS25.86-86-30-12 APRIL PATCH). Can I flash this Rom or do I have to be on 7.1.1?
Click to expand...
Click to collapse
Both is good for you
Install This ROM or sideload new OTA

Hi,
I need to flash booth files (boot.img and system.img.zip)? If yes, Is there a order?
Tks

erfanoabdi said:
Wifi fix is on thread
Click to expand...
Click to collapse
Thank you - appreciated.
Sideload does not work for me: OEM Check failure.
I'll try this in the next couple of days and report back - thanks

bert269 said:
Thank you - appreciated.
Sideload does not work for me: OEM Check failure.
I'll try this in the next couple of days and report back - thanks
Click to expand...
Click to collapse
You need twrp to flash this rom

Wifi does not work.
After flash boots in infinite loops

I get that...thanks
lollyjay said:
You need twrp to flash this rom
Click to expand...
Click to collapse
I totally understand - I was "trying" to say that I could not get either NPLS25.86-30-12 (with Sideload) nor NPLS25.86-30-12 (with fastboot) to work.

jimdent said:
Wifi does not work.
After flash boots in infinite loops
Click to expand...
Click to collapse
Even after flashing modem?

erfanoabdi said:
Wifi fix is on thread
You can try it but we're using old moto driver on LOS, test and report back
Both is good for you
Install This ROM or sideload new OTA
Click to expand...
Click to collapse
I was thinking of the WiFi needing reboot or airplaine mode toggle issue. If its more than just a driver issue.
Users coming from stock 7.1.1 would need to work without any issues too. Hopefully they will not have any major issues.
Sent from my XT1650-03 using Tapatalk

swejuggalo said:
I was thinking of the WiFi needing reboot or airplaine mode toggle issue. If its more than just a driver issue.
Users coming from stock 7.1.1 would need to work without any issues too. Hopefully they will not have any major issues.
Click to expand...
Click to collapse
We're waiting for moto new wifi driver to start fixing lineage bug

erfanoabdi said:
Even after flashing modem?
Click to expand...
Click to collapse
yes after flash loop starts

Tried flashing this Rom with TWRP 3.1.1 (official). I skipped wifi-setup and used data Connection. Here it got stuck in "searching for system update" for more than 10 minutes. So i wiped everything and started new by flashing stock rom with Januar Patch (via rsd-lite), took the three ota-updates...now i'm back on stock april patch NPLS25.86-31-5. (weird, because before it was NLS25.86-30-12) Too much for my old brain. I'll be patiently waiting for the official 7.1 ota. Until then, keep up the good work and thanks for your kind contribution!

Hi Erfan, to root is recommended Magisk, but can it be rooted with SuperSU? What could be the difference

lilloscar said:
Hi Erfan, to root is recommended Magisk, but can it be rooted with SuperSU? What could be the difference
Click to expand...
Click to collapse
Take a look here https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113

Will this work on any variant? I'm on RetMX with @erfanoabdi RR ROM.

bullfinch110 said:
Tried flashing this Rom with TWRP 3.1.1 (official). I skipped wifi-setup and used data Connection. Here it got stuck in "searching for system update" for more than 10 minutes. So i wiped everything and started new by flashing stock rom with Januar Patch (via rsd-lite), took the three ota-updates...now i'm back on stock april patch NPLS25.86-31-5. (weird, because before it was NLS25.86-30-12) Too much for my old brain. I'll be patiently waiting for the official 7.1 ota. Until then, keep up the good work and thanks for your kind contribution!
Click to expand...
Click to collapse
Eject your simcard and don't let it to connect to internet in setup wizard
lilloscar said:
Hi Erfan, to root is recommended Magisk, but can it be rooted with SuperSU? What could be the difference
Click to expand...
Click to collapse
SuperSU need patched f2fs driver on kernel
I'm not sure if moto patched it so I'm waiting for moto to release kernel source then i can update turboZ
MuyKurioso said:
Will this work on any variant? I'm on RetMX with @erfanoabdi RR ROM.
Click to expand...
Click to collapse
Yes it works for you
Just wipe data