[UNOFFICIAL] MultiROM v33 + TWRP 3.1.1 for ZUK Z1 (ham)

[UNOFFICIAL] MultiROM v33 + TWRP 3.1.1 for ZUK Z1 (ham) - Zuk Z1 Android Development

** Work in progress (Original thread here) **
To be able to run multiple ROMs on your system you need a Modded TWRP version (for flashing ROMs as secondary systems) and MultriROM utility to choose which ROM you want to boot, in this case, the NO-KEXEC version (no patched kernel needed).
Screenshots:
{
"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"
}
Disclaimer:
Remember: You use this under your own risk!
Notes:
I can't maintain this project... I don't have the device... and no time... so don't expect to be updated frequently, sorry.
If you are a developer and want to maintain, update or upgrade this project, let me know... I will try to give proper support.
Download (Latest TWRP and MultiROM):
Androidfilehost
MultiROM Uninstaller
MultiROM Manager (APK). Updated version here.
Guide (short version....):
Flash TWRP-MROM modded and reboot in recovery mode
Flash MultiROM ZIP
Set No-Kexec option in settings for MultiROM from TWRP
Inject boot sector
Flash your favorite ROM as secondary from MultiROM menu
Reboot
Select ROM to boot from
*Your device must be unencrypted or MultiROM won't work !
Known Bugs:
Still a bug that prevents it from flashing IMG files, like recovery images, from TWRP...
Thanks:
To @Tasssadar for all awesome MultiROM dev
To @nkk71 for NO_KEXEC work
To TeamWin for TWRP (Specially @Shivver for his port for ZUK Z1)
To @acuicultor and all guys who have tested and for their support
To @sahu.prashant for screenshots
XDA:DevDB Information
MultiROM, Tool/Utility for the Lenovo Zuk Z1
Contributors
BitOBSessiOn, acuicultor
Source Code: https://github.com/BitOBSessiOn/android_device_zuk_ham/tree/mm6.0-twrp-mrom
Version Information
Status: Testing
Current Beta Version: 2017.08.18
Beta Release Date: 2017-08-18
Created 2016-12-01
Last Updated 2017-08-18

Reserved

screenshot pls

rockzvishu17 said:
screenshot pls
Click to expand...
Click to collapse
I don't have the device, sorry, so, if somebody can provide any screenshot I will nicely add to OP.
Thx.
PS: Initial thread:
http://forum.xda-developers.com/zuk-z1/general/multirom-unofficial-v33-t3492262

I'll surely post the screenshots soon

sahu.prashant said:
I'll surely post the screenshots soon
Click to expand...
Click to collapse
Thnx !!

TWRP Screenshots

MultiROM Screenshots

Wow, awesome work!!!! Slowly this device is getting what deserves. Thanks BitOBSessiOn for all your efforts for this community,you're great!! Even without the device you're pushing it to a next level with this awesome tool.
Enviado desde mi ZUK Z1 mediante Tapatalk

woah finally...thanks...awesome man

Mega thx
Wysłane z mojego ZUK Z1 przy użyciu Tapatalka

This is awesome! Thanks for your dedication. I didn't expect this because you said you left zuk on the table. Than this happened. It escalated very quickly. Watching the development of this project has been really fun. I am so happy about the point where we arrived.

Hi, is there a possibility that the phone will lose sound when using this? I recently lost sound in all my ROMs including the primary rom after I used and flashed ROMs via multi rom twrp.
Any insights to this? Thanks.
Base ROM: ZUI 2.3.045

rradix said:
Hi, is there a possibility that the phone will lose sound when using this? I recently lost sound in all my ROMs including the primary rom after I used and flashed ROMs via multi rom twrp.
Any insights to this? Thanks.
Base ROM: ZUI 2.3.045
Click to expand...
Click to collapse
Roms share partitions, means the firmware used in primary rom is same for all roms so if you flash a secondary rom not compatible with the current firmware you will face weird bugs, in your case roms not zui based will not work properly unless you flash the correct firmware.
Enviado desde mi ZUK Z1 mediante Tapatalk

rradix said:
Hi, is there a possibility that the phone will lose sound when using this? I recently lost sound in all my ROMs including the primary rom after I used and flashed ROMs via multi rom twrp.
Any insights to this? Thanks.
Base ROM: ZUI 2.3.045
Click to expand...
Click to collapse
That may happen if you use the Stock ZUI rom also with multi rom. ZUI is using another kernel then all the roms on xda. You may remove ZUI and reflash other cm roms. That should work.

OrdenKrieger said:
That may happen if you use the Stock ZUI rom also with multi rom. ZUI is using another kernel then all the roms on xda. You may remove ZUI and reflash other cm roms. That should work.
Click to expand...
Click to collapse
The use case is to get zui as the daily driver rom. Is it possible to do that if I make zui as a secondary rom (but auto boot to it?) Will the sound problem still exist?
Or is it really necessary to stop using zui rom altogether to avoid sound problems with multi rom?
Also, what is the cause of the sound problem? Is it the kernel? Cause based from what I read, multi rom uses a different kernel for each rom. So, it should not matter if my primary is zui since flashing secondaries won't touch the primary kernel. Any insights to this? Thanks!
---------- Post added at 02:28 PM ---------- Previous post was at 02:12 PM ----------
acuicultor said:
Roms share partitions, means the firmware used in primary rom is same for all roms so if you flash a secondary rom not compatible with the current firmware you will face weird bugs, in your case roms not zui based will not work properly unless you flash the correct firmware.
Enviado desde mi ZUK Z1 mediante Tapatalk
Click to expand...
Click to collapse
Okay. But why is sound in all ROMs primary and secondaries were bugged? Flashing secondaries should in theory not affect the primary ROM right? So the sound bug will appear on secondaries but not on the primary ROM. Am I getting this correct?

rradix said:
The use case is to get zui as the daily driver rom. Is it possible to do that if I make zui as a secondary rom (but auto boot to it?) Will the sound problem still exist?
Or is it really necessary to stop using zui rom altogether to avoid sound problems with multi rom?
Also, what is the cause of the sound problem? Is it the kernel? Cause based from what I read, multi rom uses a different kernel for each rom. So, it should not matter if my primary is zui since flashing secondaries won't touch the primary kernel. Any insights to this? Thanks!
---------- Post added at 02:28 PM ---------- Previous post was at 02:12 PM ----------
Okay. But why is sound in all ROMs primary and secondaries were bugged? Flashing secondaries should in theory not affect the primary ROM right? So the sound bug will appear on secondaries but not on the primary ROM. Am I getting this correct?
Click to expand...
Click to collapse
Yes secondary roms don't affect primary in any way and kernels aren't shared between roms so doesn't matter what kernel you have in secondaries, the only kernel which can affect multirom is the one in primary rom if it have the kexec hardboot patch or not, if it have then you can boot secondaries without any work around in twrp, that's the only difference between kernels in mrom afaik.
Enviado desde mi ZUK Z1 mediante Tapatalk

acuicultor said:
Yes secondary roms don't affect primary in any way and kernels aren't shared between roms so doesn't matter what kernel you have in secondaries, the only kernel which can affect multirom is the one in primary rom if it have the kexec hardboot patch or not, if it have then you can boot secondaries without any work around in twrp, that's the only difference between kernels in mrom afaik.
Enviado desde mi ZUK Z1 mediante Tapatalk
Click to expand...
Click to collapse
Okay. Thanks for clarifying.
So secondaries should not mess up my kernel, recoveries and other partitions used by the primary rom. However, after flashing some secondaries, my old ZUK boot splash was replaced by a Linux penguin. I'm not that concerned about it but secondaries might be messing with my primary partitions (not sure).
Update : got sound working now. Un installing multirom is not enough. I refreshed the official twrp for Zuk Z1.
I'm still wondering what went wrong. Also I'm still getting that penguin in boot splash.
Update 2: after a second reboot, sound is gone again.

rradix said:
Okay. Thanks for clarifying.
So secondaries should not mess up my kernel, recoveries and other partitions used by the primary rom. However, after flashing some secondaries, my old ZUK boot splash was replaced by a Linux penguin. I'm not that concerned about it but secondaries might be messing with my primary partitions (not sure).
Update : got sound working now. Un installing multirom is not enough. I refreshed the official twrp for Zuk Z1.
I'm still wondering what went wrong. Also I'm still getting that penguin in boot splash.
Update 2: after a second reboot, sound is gone again.
Click to expand...
Click to collapse
Without any log is difficult to know what's happening btw i strongly doubt that multirom has nothing to do with any sound issue, for the changed boot image that can only happens if you flash a different one in primary slot. I'm using mrom since it wasn't public released, flashed several secondary roms and didn't face any issue.
Enviado desde mi ZUK Z1 mediante Tapatalk

acuicultor said:
Without any log is difficult to know what's happening btw i strongly doubt that multirom has nothing to do with any sound issue, for the changed boot image that can only happens if you flash a different one in primary slot. I'm using mrom since it wasn't public released, flashed several secondary roms and didn't face any issue.
Enviado desde mi ZUK Z1 mediante Tapatalk
Click to expand...
Click to collapse
Any tips on how to get logs?
I guess I'm on my own then. I'll try to figure this on out. Thanks for the info! ?
Update 3: got the sound working again. Refreshed zui except for the system partition. Let's see if this will stick.

Related

[ROM][CM12.1][OFFICIAL] CyanogenMod 12.1

Hooray! And good stuff.
Thanks for all the work on this!
Also, might be worth mentioning the need for the LP bootstack
Edit: Adding link to the LG-Devs bootstacks. You'll probably want the D800 bumped version, though the loki one should work as well.
https://github.com/lg-devs/bootstacks/tree/master/d800/lp
You'll have to click on the file, then click the "Raw" button to start the download.

Are you saying it's best to flash back to stock as in "LGD800AT-01-V10o-310-410-OCT-19-2013+0.tot" , and then root, recovery, flash, etc? (just to be clear).

faheyd said:
Are you saying it's best to flash back to stock as in "LGD800AT-01-V10o-310-410-OCT-19-2013+0.tot" , and then root, recovery, flash, etc? (just to be clear).
Click to expand...
Click to collapse
Flash back then apply all stock updates, so you are on stock lollipop. After that root, and install cm. This will provide the best experience and is the only method that bug reports will be accepted from.
That said there are other situations your phone can be in and cm-12.1 work. Coming straight from cm-12.0 however will result in an assert check failing or a bootloop of the kernel not booting. We've broken compatibility, but its needed. There was no way to provide a proper experience and allow people to be on original jellybean firmware.

I'm good on flashing the tot, but 'Stock Updates', I have no idea where they would be nor how to get them. Do you have a link? Thanks for putting up with a noob, it's just I want clarification. Thanks. (I'm asking, because I'm sure others want to know also).

Flashing Blastagator's modem and bootloader inside TWRP then installing CM12.1 won't work?

praetorzero said:
Flashing Blastagator's modem and bootloader inside TWRP then installing CM12.1 won't work?
Click to expand...
Click to collapse
Like I said there is more than one way to get it to work but the only official way is to tot back to stock and make sure you are updated to lollipop.
Sent from my LG-ls990 using XDA Free mobile app

Shelnutt2 said:
Like I said there is more than one way to get it to work but the only official way is to tot back to stock and make sure you are updated to lollipop.
Sent from my LG-ls990 using XDA Free mobile app
Click to expand...
Click to collapse
These are the only tots, and I have no idea where to find 'updates', that I could find, which one, 20c?
http://forum.xda-developers.com/showthread.php?t=2663369
Noobs like me are going to need some clear cut instructions, not just some 'updates' thing.

The first nightly build of cm12.1 for d800 is online!!
Enviado desde mi LG-D800 mediante Tapatalk

Shelnutt2 said:
Flash back then apply all stock updates, so you are on stock lollipop. After that root, and install cm. This will provide the best experience and is the only method that bug reports will be accepted from.
That said there are other situations your phone can be in and cm-12.1 work. Coming straight from cm-12.0 however will result in an assert check failing or a bootloop of the kernel not booting. We've broken compatibility, but its needed. There was no way to provide a proper experience and allow people to be on original jellybean firmware.
Click to expand...
Click to collapse
"...so you are on stock lollipop." What stock lollipop are you talking about, where can I get that stock lollipop?

praetorzero said:
Flashing Blastagator's modem and bootloader inside TWRP then installing CM12.1 won't work?
Click to expand...
Click to collapse
blastagator's bump'd LP bootstack zip should get you past the assert on the value of TZ. However you'll also want the LP radio at the least. This may not be the most supported, but it'll probably get things working for you.

While it may not be officially supported, I at least got it working for me.
Backed up everything under /sdcard (adb pull /sdcard/ . )
Backed everything up in TWRP. (saved to USB, included Boot, System, Data, Cache, EFS, modem, Recovery, and Sensors)
Performed a factory wipe
Flashed bootstack-d800-LP_30f-bump-v1.1-blastagator-signed.zip
Flashed d800-30f-modem-blastagator-signed.zip
Flashed cm-12.1-20150804-NIGHTLY-d800.zip
Flashed open_gapps-arm-5.1-stock-20150804.zip
Flashed UPDATE-SuperSU-v2.46.zip
Backed everything up in TWRP (again) to have a clean CM12.1 base to start from. Included the same options as before (everything)
It worked for me, YMMV.

Please could you provide some feedback on camera and audio in whatsapp message? Thanks.
Enviado desde mi LG-D800 mediante Tapatalk

Camera's broken by an errant patch, should be working hopefully in another nightly or two.

praetorzero said:
While it may not be officially supported, I at least got it working for me.
Backed up everything under /sdcard (adb pull /sdcard/ . )
Backed everything up in TWRP. (saved to USB, included Boot, System, Data, Cache, EFS, modem, Recovery, and Sensors)
Performed a factory wipe
Flashed bootstack-d800-LP_30f-bump-v1.1-blastagator-signed.zip
Flashed d800-30f-modem-blastagator-signed.zip
Flashed cm-12.1-20150804-NIGHTLY-d800.zip
Flashed open_gapps-arm-5.1-stock-20150804.zip
Flashed UPDATE-SuperSU-v2.46.zip
Backed everything up in TWRP (again) to have a clean CM12.1 base to start from. Included the same options as before (everything)
It worked for me, YMMV.
Click to expand...
Click to collapse
At least we didn't have to wait for a dev to show how to do it. Good job.

Camera and flashlight working on tonight's nightly for me.
Sent from my LG-D800 using Tapatalk

ukguy115 said:
Camera and flashlight working on tonight's nightly for me.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
What about the time to open and the pic quality? Are ok? Whastapp audio message works? Thkx
Enviado desde mi LG-D800 mediante Tapatalk

luchardi said:
What about the time to open and the pic quality? Are ok? Whastapp audio message works? Thkx
Enviado desde mi LG-D800 mediante Tapatalk
Click to expand...
Click to collapse
Camera opens and takes pics. Speed and use will be subjective, its good enough for me but I am not a photography. I can say it is functional now though for me.
Sent from my LG-D800 using Tapatalk

Anyone figured out a way to remove the superuser hash mark from the status bar?
Never mind, I flashed SuperSU and it took care of it.

Before I go too much further down the rabbit hole, has anyone else had issues with voice calls? I cannot be heard unless I am on speakerphone or hold the bottom of the phone perpendicular to my mouth and speak directly into the bottom of my phone. Using a VOIP app (ie Hangouts) to make a call appears to work just fine.
I've tried switching persist.audio.dualmic.config from endfire to disable and back again with no benefit.
---------- Post added at 06:31 PM ---------- Previous post was at 06:26 PM ----------
Shelnutt2 said:
Flash back then apply all stock updates, so you are on stock lollipop. After that root, and install cm. This will provide the best experience and is the only method that bug reports will be accepted from.
Click to expand...
Click to collapse
Are we talking flashing the Kitkat TOT then taking the OTA upgrades to Jellybean? I ask because I've yet to find a TOT for Jellybean for the D800.

Marshmallow 6.0.1 8/03/16 ASOP D2203

Code:
*** Disclaimer
This software is without warranty and
I will not be held accountable
if it blows up, bricks or starts a zombie apocalypse.
I am a developer BUT I am not a kernel/android rom dev!
Pure AOSP Marshmallow
This all started because I wanted to get my wife a cheap android phone that would stay up to date with the latest android. A cheap phone with SD storage and Marshmallow seemed like a great combination hence the E3. Sony has been great at supporting the developer community by providing Marshmallow binaries and working on open source components.
I am providing this rom in my spare time and all of what I have done can be done by anyone with AOSP code. Any changes I make I will endeavour to release to github should I stop developing this rom.
Click to expand...
Click to collapse
supports D2203
Guide to flashing
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img --> if it doesn't work first time
If you are having booting issues flash the cache image as well.
you also probably want the newest recovery of TWRP or CWM
repo with all the kernel patches I added to the E3 if someone wants to build it for themselves
https://github.com/mikey0000/kernel-patches-for-xperia-E3
Changelog
Code:
[B]21/03/2016[/B]
boot image update
new unified display driver with flamingo specific fixes for display not turning on (seems to affect some devices worse than others)
19/03/2016
6.0.1 Release - updated boot image should get rid of display issues. Updated system image with security patches
New releases are in the downloads section and dated.
8/03/2016
6.0.1 Release, thank you all for waiting, stock build first. I really need to learn how to do nice release notes..
updated blobs which should mean a more stable build. Also we are getting closer to getting a working camera.
17/11/2015
Two new system builds
with modem files and one without
25/11/2015
Phone has arrived in the country should receive it soon
this will mean I can continue work on this device, I cannot just take my partners phone and mess with it unfortunately ;-D
26/11/2015
Phone arrived, have got a working system image, am uploading a backup from twrp now.
26/11/2015
Yay I have a working system.img for you all to flash and I put some extra effort to add a nice boot animation
I have also added the stock kernel(boot.img) as it seems to be more stable than erikcas one at the moment.... possibly
I've also attached the bootanimation should you want to use it on stock or whatever. Is not mine, can't remember the person who made, it, was posted to reddit/r/android if I find it again I'll attribute it.
02/12/2015
New boot.img with improved io performance, you should see significant improvements if you've experienced lag. Thanks goes to @vinay for his work on the flamingo kernel. One small change removes CRC checking which improves performance by up to 30%
20/01/2016
Hi Guys am in the process of producing a new kernel and ROM with ZRAM support. Hoping to get something in your hands soon.
Click to expand...
Click to collapse
FAQ
Whats working
wifi
bluetooth
sound
screen
touch etc
boots up
modem aka LTE, sim
internal storage
GPS
Not working
camera
Fix play services issues
Code:
adb shell pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
adb shell pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
Click to expand...
Click to collapse
Thanks guys
Old downloads
Slowly I am going to release newer builds to the downloads page.
Gapps
www.opengapps.org
TWRP
Vinays TWRP seems to work go grab it from the forum.
Thanks/Credits
Code:
Thanks [user=985241]@erikcas[/user] for the kernel fixes and help
sony for releasing marshmallow binaries
XDA:DevDB Information
Pure AOSP[Marshmallow], ROM for the Sony Xperia E3
Contributors
mikey0000
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Beta
Created 2016-03-10
Last Updated 2016-03-12

mikey0000 said:
Hi guys,
I've brought my partner an E3 and compiled marshmallow for it from ASOP, I will post links as soon as I can.
Anyone game to test?
As usual, the usual disclaimers apply. I won't be blamed if it does anything weird.
Thanks guys
Click to expand...
Click to collapse
I can test it if you post link for download

moznoadam said:
I can test it if you post link for download
Click to expand...
Click to collapse
https://drive.google.com/folderview?id=0B3jDRHAxbOx4N1ZWaEdfVkdhVXc&usp=sharing
heres the link, uploading the system image and userdata now, broke through our internet cap (at dial up speeds) so doing it over my phone lol.
So should be there in about half an hour.
EDIT: it's all up now
I can't test it because the phone hasn't arrived.

You will make a marshmallow´s rom for xperia E3?? we needed!!

Tutorial
mikey0000 said:
Hi guys,
I've brought my partner an E3 and compiled marshmallow for it from ASOP, I will post links as soon as I can.
Anyone game to test?
As usual, the usual disclaimers apply. I won't be blamed if it does anything weird.
Thanks guys
Click to expand...
Click to collapse
It makes a tutorial on installing via please ASOP ? :crying:

can this apply to D2202?
yes, this will better if you tell us for what variant of E3 in this Marshmallow thread

Will it work on D2212??? Which is your variant???
I have downloaded all the img files. Give step wise tutorial for flashing. What is the ramdisk.img and ramdisk-recovery.img and how to flash them???

Ramdisk is probably kernel. One without and one with recovery. Everything is flashable from fastboot

Okay, means this rom will work on D2212 /D2202 as they don't have seperate recovery partition

OK i´m downloading it i will write here and post screens if you want

{
"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"
}
system.img is too large ...

Maybe for new bootloader? If i good remember for E3 here was 2 bootloader types

Can you please create a quick installation guide and/or requirements (bootloader), i will be pleased and please can you tell us the bugs

Do i need to flash ramdisk OR ramdisk-recovery OR recovery OR all of them??? I am confused

this is no gonna boot at all. were is kernel?
and sony upload stuff for compiling rom,s for lte varriant,s so test it on d2203.
and system.img is bigger than our system partition it could mean you compiled rom for a different device.

ChetanLokhande said:
Will it work on D2212??? Which is your variant???
I have downloaded all the img files. Give step wise tutorial for flashing. What is the ramdisk.img and ramdisk-recovery.img and how to flash them???
Click to expand...
Click to collapse
See top post

vinay said:
this is no gonna boot at all. were is kernel?
and sony upload stuff for compiling rom,s for lte varriant,s so test it on d2203.
and system.img is bigger than our system partition it could mean you compiled rom for a different device.
Click to expand...
Click to collapse
Sorry uploading kernel now. I followed the sony developer world instructions for the D2203 variants
http://developer.sonymobile.com/kno...aosp-marshmallow-for-unlocked-xperia-devices/
please be nice this is my first attempt at supplying a rom. Am re-compiling again as I think your right I misread and compiled for the D5503 instead of D2203, I don't have the device yet as I am waiting for it to be delivered.
I have messed around with building roms before but haven't handed them out.

Again for D2203 and not for D2212/D2202. I think i must throw this phone, nothings gonna happen.

mikey0000 said:
Sorry uploading kernel now. I followed the sony developer world instructions for the D2203 variants
http://developer.sonymobile.com/kno...aosp-marshmallow-for-unlocked-xperia-devices/
please be nice this is my first attempt at supplying a rom. Am re-compiling again as I think your right I misread and compiled for the D5503 instead of D2203, I don't have the device yet as I am waiting for it to be delivered.
I have messed around with building roms before but haven't handed them out.
Click to expand...
Click to collapse
thank you for quick guide and im waiting impatiently for your relase ;P lets make it work more than lollipop and i have 1 question if i have ramdisk(kernel) i need to flash it through flashtool in fastboot mode?

edi194 said:
Maybe for new bootloader? If i good remember for E3 here was 2 bootloader types
Click to expand...
Click to collapse
I flashed a new bootloader
---------- Post added at 11:17 AM ---------- Previous post was at 11:14 AM ----------
So, are you rebuilding it ? Let me know i can´t wait to flash it

[ROM] [OFFICIAL] LineageOS for the Shield Tablet

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds : https://download.lineageos.org/shieldtablet
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/
Firmware Update : N/Stock 5.0
Known Issues
Hardware video decoding does not work
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console_ramoops. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
LineageOS for the Shield Tablet, ROM for the Nvidia Shield Tablet
Contributors
Steel01
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Current Stable Version: 15.1
Created 2017-02-25
Last Updated 2019-05-02

Note: There were problems getting the migration builds built for 13.0, so a full wipe is required to install this rom when coming from anything else.

Thank you, much appreciated! Is there any chance for the Shield tablet (original, not just K1) to be getting LineageOS 14.1 in the future?

Thanks so much!!! I wait LineageOS 14.1 [emoji14]
Good work!!
Enviado desde mi SHIELD Tablet K1 mediante Tapatalk

This is great news and fate. Just bought this great tablet and soft bricked it trying to root Nougat. Nice to see it back and now have a working tablet with root. Without the bloat!
Sent from my iPhone using Tapatalk

I am trying to update my device using the steps above, i am coming from Stock 3.1.1. But when i try to reboot it keeps stuck on Nvidia Boot logo. What am i doing wrong?

amnguerreiro said:
I am trying to update my device using the steps above, i am coming from Stock 3.1.1. But when i try to reboot it keeps stuck on Nvidia Boot logo. What am i doing wrong?
Click to expand...
Click to collapse
Remove any sd card you have attached and if you didn't when you flashed it factory reset it
Sent from my iPhone using Tapatalk

srdempster said:
Remove any sd card you have attached and if you didn't when you flashed it factory reset it
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Already did that, didn't worked
Enviado do meu ONEPLUS A3003 através de Tapatalk
---------- Post added at 10:20 AM ---------- Previous post was at 10:09 AM ----------
amnguerreiro said:
Already did that, didn't worked
Enviado do meu ONEPLUS A3003 através de Tapatalk
Click to expand...
Click to collapse
I'm coming from a Lollipop ROM. May that be problem? Do i have to flash anything else?
Enviado do meu ONEPLUS A3003 através de Tapatalk

Copy paste error: it's marshmallow not nougat!

amnguerreiro said:
Already did that, didn't worked
Enviado do meu ONEPLUS A3003 através de Tapatalk
---------- Post added at 10:20 AM ---------- Previous post was at 10:09 AM ----------
I'm coming from a Lollipop ROM. May that be problem? Do i have to flash anything else?
Enviado do meu ONEPLUS A3003 através de Tapatalk
Click to expand...
Click to collapse
Make sure you're using TWRP for your recovery. If you are I'd suggest downloading the rom again and if that doesn't work download the stock rom in this forum first and flash and then reflash this rom again.
Sent from my iPhone using Tapatalk

Very great !
So what about performances ? It's better than official nougat ?
---------- Post added at 12:10 PM ---------- Previous post was at 11:58 AM ----------
Oh but... This is Android 6.0 ?

Bryandu13 said:
Very great !
So what about performances ? It's better than official nougat ?
---------- Post added at 12:10 PM ---------- Previous post was at 11:58 AM ----------
Oh but... This is Android 6.0 ?
Click to expand...
Click to collapse
Yes, this ROM is android 6.0.1...
Android 7.1.1. is in development... I wait LineageOS 14.1!!
Enviado desde mi S3 mediante Tapatalk

Me too ! Waiting for 14.1.
But I saw on other devices that gaming is not very good on CyanogenMod Roms is it real ?

Waiting for 14.1 too. 13 is working fine up till now

I had an issue getting root with supplied root add on at the beginning. Ended up flashing SuperSU zip
Sent from my iPhone using Tapatalk

amnguerreiro said:
I am trying to update my device using the steps above, i am coming from Stock 3.1.1. But when i try to reboot it keeps stuck on Nvidia Boot logo. What am i doing wrong?
Click to expand...
Click to collapse
You need to update the bootloader. M roms will not boot on the L bootloader. There's a link in my CM thread. I'll get them added here when I have a few more minutes.
edisso10018 said:
Copy paste error: it's marshmallow not nougat!
Click to expand...
Click to collapse
Thank you... Fixed.
srdempster said:
I had an issue getting root with supplied root add on at the beginning. Ended up flashing SuperSU zip
Click to expand...
Click to collapse
Didn't realize the 13.0 su addon zips weren't released yet. I hear they should be ready for the next release cycle next week, but as always, something might come up, so I can't guarantee anything.
Edit:
Tamirwig said:
Thank you, much appreciated! Is there any chance for the Shield tablet (original, not just K1) to be getting LineageOS 14.1 in the future?
Click to expand...
Click to collapse
This is already for all variants of the tablet. Just like the vast majority of shieldtablet custom roms. I know of at most two roms that were K1 specific and I don't think they're even maintained anymore.

Great! Video bug is gone! Can finally use lineage on my shield.

Tamirwig said:
Thank you, much appreciated! Is there any chance for the Shield tablet (original, not just K1) to be getting LineageOS 14.1 in the future?
Click to expand...
Click to collapse
it's possible. i tried an unofficial lineageOS 14.1 for shieldtablet

fedetrevi1 said:
it's possible. i tried an unofficial lineageOS 14.1 for shieldtablet
Click to expand...
Click to collapse
I tried, but it gave me "bootloader unknown" error, so decided to wait for the official version.
Btw, still suffering from the video bug in the official nightly...

Tamirwig said:
I tried, but it gave me "bootloader unknown" error, so decided to wait for the official version.
Btw, still suffering from the video bug in the official nightly...
Click to expand...
Click to collapse
I had the same bootloader error. I ended up downloading the full recovery image (latest available is 4.0.0 MM), flashing it, then doing a system update in the stock ROM to Nougat. Flashing worked after.

LineageOMS 14.1 [Substratum] [NIGHTLY]

{
"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"
}
OMS supported LineageOS version. You can use them by downloading Substratum from Google Play.
What's working :
Boots
Wifi
Bluetooth
Camera ( Videos And Photos )
Video Playback
Audio ( Record and Playback )
Sensors
GPS
What's not working:
Please tell me.
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds : https://www.androidfilehost.com/?w=files&flid=181589&sort_by=date&sort_dir=DESC
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/?arch=arm64&api=7.1
XDA:DevDB Information
LineageOMS 14.1, ROM for the Xiaomi Mi Mix
Contributors
Cenkay, asderdd, pappschlumpf, LuK1337, luca020400, bgcngm, h2o64
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Created 2017-05-18
Last Updated 2017-05-18

Hi Cenkay, thanks for the rom. I guess this is based on the new device tree so it should have the same bugs as RR.
There have been some complains about the proximity sensor. They say that (when the phone is locked) and you receive a phone call, the proximity sensor doesn't work and the screen would stay on during the entire call. So If someone could test because I'm currently testing private RR builds. And i need more time to test and reproduce the issue. Can't really test both the same time. Anyways, Thanks again Cenkay!.
Sent from my MI Mix using Tapatalk

Thanks a lot @Cenkay
Which root do they offer?
Magisk also is possible?

mohammed510 said:
Hi Cenkay, thanks for the rom. I guess this is based on the new device tree so it should have the same bugs as RR.
There have been some complains about the proximity sensor. They say that (when the phone is locked) and you receive a phone call, the proximity sensor doesn't work and the screen would stay on during the entire call. So If someone could test because I'm currently testing private RR builds. And i need more time to test and reproduce the issue. Can't really test both the same time. Anyways, Thanks again Cenkay!.
Sent from my MI Mix using Tapatalk
Click to expand...
Click to collapse
Now there are reports that it is not working if you make a call yourself. And that it works if a call comes in screen off. Both situations work without problems on my phone. Proximity is fine. So there's nothing to do. The proximity is a little slow, so it sometimes happens that you pulldown statusbar. But screen and digitizer are off during call. Always on my device. @mohammed510 on your phone it is fine too, right?
Gesendet von meinem MI Mix mit Tapatalk

pappschlumpf said:
Now there are reports that it is not working if you make a call yourself. And that it works if a call comes in screen off. Both situations work without problems on my phone. Proximity is fine. So there's nothing to do. The proximity is a little slow, so it sometimes happens that you pulldown statusbar. But screen and digitizer are off during call. Always on my device. @mohammed510 on your phone it is fine too, right?
Gesendet von meinem MI Mix mit Tapatalk
Click to expand...
Click to collapse
I'm using the latest private build and no problems here with proximity. I have tried many scenarios but couldn't find the problem. maybe user error? And For me, the proximity is not slow. It's normal, just like any other phone i used before.
Sent from my MI Mix using Tapatalk

The proximity issue turned out to be a user error. Other than this, everything else seems to be working fine here.
Better to remind users to do a clean install before reporting bugs to avoid wasting time. Thanks.
Sent from my MI Mix using Tapatalk

I will try this. Can you tell me if this passes safetynet without installing magisk?

Too many variables to call it a bug.. but I dirty flashed this over the latest LOS from pappschlumpf, then flashed the SchlumpfKernel 1.02 and didn't make it passed the boot-loader. Anyone else?

blinksilver said:
Too many variables to call it a bug.. but I dirty flashed this over the latest LOS from pappschlumpf, then flashed the SchlumpfKernel 1.02 and didn't make it passed the boot-loader. Anyone else?
Click to expand...
Click to collapse
Yes, the dev himself. The kernel needs a recompile to work again. Use included kernel until i push an update, please.

I can't get fingerprint sensor to work. I may have installed it wrong though. My previous rom was an old EPIC version (android 6.x). I wiped system, caches and data, and installed rom + gapps using twrp. Is there anything else I should do?

Alxandr said:
I can't get fingerprint sensor to work. I may have installed it wrong though. My previous rom was an old EPIC version (android 6.x). I wiped system, caches and data, and installed rom + gapps using twrp. Is there anything else I should do?
Click to expand...
Click to collapse
Are you able to get it to boot? You're the first one who has reported it being bootable

It booted just fine. It may be cause of other things I flashed though. Also I got fingerprint sensor to work . In case someone are interested this is the order I did things in:
1. Start with old EPIC rom (don't remember which one. Installed in January or February).
2. Wipe system, data and cache.
3. Flash RR rom. - Fingerprint sensor didn't work.
4. Wipe system, data and cache.
5. Flash linage (from this thread). - Fingerprint sensor didn't work.
At this point I figured flashing (even after wiping system) didn't clear everything, and I read something in the RR thread about needing MIUI dev rom before flashing RR for things to work so I did this:
1. Download and flash Chinese (not global) dev rom (latest atm is v7.5.11).
2. Boot phone. - this will remove TWRP or any other custom recovery.
3. Flash TWRP from fastboot.
4. Wipe System, data and cache.
5. Flash RR + gapps + magisk.
6. Profit.
Granted, I'm now running RR, but from what I saw this should likely work with lineage too. Hopefully someone finds this helpful

I dont find Fingerprint in setting

I guess it's using the newest version of Pappschlumpf's device tree and vendor, or do u use a personal one?
And do u use any other toolchain then the standard one?
If u need help in changing the toolchain or any other question feel free to hit me up.

its a nice rom have a good day sir

All is running fine...

vergilbt said:
All is running fine...
Click to expand...
Click to collapse
Same

skittishwind said:
I dont find Fingerprint in setting
Click to expand...
Click to collapse
Flash fastboot global stable rom, and install this rom.

Cenkay said:
Flash fastboot global stable rom, and install this rom.
Click to expand...
Click to collapse
Hmm, i would recommend china dev

In Korea, when you use the " Lineage OS ", your phone number and my phone number are
In Korea, when you use the " Lineage OS ", your phone number and my phone number are displayed together.
Ex) 0104444444401055555555
I hope this error fixes quickly.

[ROM][7.1.2][OpenKirin's LineageOs 14.1 For Honor 6X ]

{
"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"
}
Latest update: July 26th 2017
Disclaimer:
Although we are working hard to deliver a bug-free rom, things may break and we are not responsible if something goes wrong and your hardware becomes damaged or if you have any problem, you are taking a risk flashing roms.
Instructions:
If you come from stock EMUI 5.0:
Install TWRP (Available in this subforum)
Format data
Copy vendor.img to your sdcard
Run adb shell dd if=/sdcard/vendor.img of=/dev/block/bootdevice/by-name/vendor (From TWRP)
Flash LineageOS's zip
Downloads:
Find them inside this DevDB project section called 'Downloads' (you might need to use a computer)
Bugs:
Encryption
HwComposer
Camera
Changelog:
Code:
07/26 - Fixed screen deepsleep issue
07/25 - First release
Asking for help...
There are still some little bugs to fix and things will break from time to time, so in order to properly help you and keep the thread organized every help petition should include:
Brief description of the issue
A way to replicate it
Screenshots/Logs
Without that information, your post will be futile so please meet those easy conditions and try to keep the thread clean!
This rom has been brought to you by the OpenKirin team ( @surdu_petru @OldDroid @XePeleato ).
XDA:DevDB Information
OpenKirin's LineageOs for Honor 6X, ROM for the Honor 6X
Contributors
XePeleato, surdu_petru, OldDroid
Source Code: https://github.com/OpenKirin
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 5.0
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2017-07-25
Created 2017-07-25
Last Updated 2017-07-26

Great release & work by team. Good going

Do it support volte
Sent from my BLN-L22 using Tapatalk

awesome ready to flash

Can I help in development ?

You're so fast guys, a full of good notices from you!

Forgive me for asking a stupid question, but are you developers on the official Lineage team or are you just using the logo ? Is this a modification of LOS/Cyanogen ?
I really have faith in the official version. No disrespect at all. It' s great to see so much action all of a sudden.

I'm not sure because my carrier doesn't support volte, if it doesn't work I'll add it to the bugs list.
Sohail65 said:
Do it support volte
Click to expand...
Click to collapse
I don't know, can you? This is an opensource project, if you can contribute just submit a pull request and I'll be glad to review it.
Notagenericmember said:
Can I help in development ?
Click to expand...
Click to collapse
It's unofficial, if you have a look at the zip file name it says unofficial, as well as inside Settings.
Nollie8969 said:
Forgive me for asking a stupid question, but are you developers on the official Lineage team or are you just using the logo ? Is this a modification of LOS/Cyanogen ?
I really have faith in the official version. No disrespect at all. It' s great to see so much action all of a sudden.
Click to expand...
Click to collapse

XePeleato said:
I'm not sure because my carrier doesn't support volte, if it doesn't work I'll add it to the bugs list.
I don't know, can you? This is an opensource project, if you can contribute just submit a pull request and I'll be glad to review it.
It's unofficial, if you have a look at the zip file name it says unofficial, as well as inside Settings.
Click to expand...
Click to collapse
I will flash the rom today.. And tell u the results
Sent from my BLN-L22 using Tapatalk

This is exciting. I will have to wait until the weekend but I am looking forward so much!
But perhaps I might have to wait for camera fix. I trust you guys but for the moment I kinda need the camera to work.
HWC is a different challenge. I hope there is a breakthrough with that some time!
Sent from my Honor 6x using XDA Labs

XePeleato said:
Asking for help...
There are still some little bugs to fix and things will break from time to time, so in order to properly help you and keep the thread organized every help petition should include:
Brief description of the issue
A way to replicate it
Screenshots/Logs
Click to expand...
Click to collapse
Bug for me:
Install zip, install gapps (or not, same bug) :
1. First boot ok
2. Without any install, any other flash zip, juste lineageos zip: shutdown phone, when press power to boot again, the rom won't boot, stuck to bootanimation.
3. I'm format data again to boot. But same bug, if i shutdown, or reboot .... stuck to bootanimation.
I can do a video if need
edit: BLN-L21

Have you flashed vendor.img from TWRP? Follow the instructions from the OP and you'll be fine.
sanjay.rup said:
Bug for me:
Install zip, install gapps (or not, same bug) :
1. First boot ok
2. Without any install, any other flash zip, juste lineageos zip: shutdown phone, when press power to boot again, the rom won't boot, stuck to bootanimation.
3. I'm format data again to boot. But same bug, if i shutdown, or reboot .... stuck to bootanimation.
Click to expand...
Click to collapse

New update released! I forgot to add the fix for the screen deepsleep issue, it's now fixed and the zip is uploaded. Keep in mind that you won't need to flash vendor.img again.

XePeleato said:
New update released! I forgot to add the fix for the screen deepsleep issue, it's now fixed and the zip is uploaded. Keep in mind that you won't need to flash vendor.img again.
Click to expand...
Click to collapse
Okay. Thanks! What about HWC Bug?
Gesendet von meinem BLN-L21 mit Tapatalk

XePeleato said:
Have you flashed vendor.img from TWRP? Follow the instructions from the OP and you'll be fine.
Click to expand...
Click to collapse
Yes i was on RR rom before. Flashing vendor change nothing. Is vendor.img différent from RR surdu rom ?

Still working on it, does it make a big difference for you? Let me know what do you exactly notice so that I can use it as a test.
Felix__L-01 said:
Okay. Thanks! What about HWC Bug?
Gesendet von meinem BLN-L21 mit Tapatalk
Click to expand...
Click to collapse
It's exactly the same, I suggest you to try with the new update, if it doesn't work I'd need a log to check what's going on.
sanjay.rup said:
Yes i was on RR rom before. Flashing vendor change nothing. Is vendor.img différent from RR surdu rom ?
Click to expand...
Click to collapse

video from 11:00 AM is still uploading. Rom update 20170526 is downloading.
If bug is still here with your update, i will try to enable usb debug before reboot and an adb shell, if i'm not wrong, bootanimation mean kernel boot, so adb shell must work (adb secure is set or not ?).
edit: add quote
XePeleato said:
Still working on it, does it make a big difference for you? Let me know what do you exactly notice so that I can use it as a test.
It's exactly the same, I suggest you to try with the new update, if it doesn't work I'd need a log to check what's going on.
Click to expand...
Click to collapse

XePeleato said:
Still working on it, does it make a big difference for you? Let me know what do you exactly notice so that I can use it as a test.
It's exactly the same, I suggest you to try with the new update, if it doesn't work I'd need a log to check what's going on.
Click to expand...
Click to collapse
About HwComposer. Apps are working as fast as normal but the UI is slower than normal. If you want to swipe down Status bar its slow and when you are at homescreen and slide from side to side its slower than normal. And when I Press Power Button to Turn Screen on/off Phone needs 1-2 seconds longer than normal. It would be very cool if we see a HWC fix for this Rom.
Gesendet von meinem BLN-L21 mit Tapatalk

here is the bug video
https://youtu.be/zgrwy5HP3WQ
XePeleato said:
Still working on it, does it make a big difference for you? Let me know what do you exactly notice so that I can use it as a test.
It's exactly the same, I suggest you to try with the new update, if it doesn't work I'd need a log to check what's going on.
Click to expand...
Click to collapse
---------- Post added at 01:32 PM ---------- Previous post was at 01:02 PM ----------
same bug with new update.
I have not unable adb, and nothing change for the moment. Because if enable adb, or doing something else, maybe the bug will not be there.
Now i will try to force language to english. And if not work, i wil re re-format data to boot, and set adb secure to 0 to look at the log.

Database Info

welcome