LineageOS development - Nexus 10 Q&A, Help & Troubleshooting

LineageOS development - Nexus 10 Q&A, Help & Troubleshooting

Hi
How is the status on development of LineageOS for manta? Is anyone working on this?

Would be great LineageOS on Nexus 10....nougat flavour please!!!

To get LOS on our beloved Nexus 10 would be awesome. :victory:

Apparently, Manta is on the list of devices that will be getting Lineage. However, the initial release is likely to be Marshmallow based still.

I'm fine with mm since there is no Xposed for nougat so far.

I've bee trying to build for three days now. My last attempt ended right before making the zip after six hours on my old Acer laptop (because it has Ubuntu) with the error:
Code:
TypeError: argument of type 'nonetype' is not iterable android

AgentOrange96 said:
I've bee trying to build for three days now. My last attempt ended right before making the zip after six hours on my old Acer laptop (because it has Ubuntu) with the error:
Code:
TypeError: argument of type 'nonetype' is not iterable android
Click to expand...
Click to collapse
I managed to get a nougat build but, it will not go past the google logo.
I am using bbqlinux.
Kernel source from binkybear for nethunter support.
The kernel works I just cant get it to go further

Got a working LineageOS 13 build for manta without too much of a hitch.
The build guide ///wiki.lineageos.org/manta_build.html#extract-proprietary-blobs) is missing the required package libxml2-utils. If you install that and follow the guide closely it should run fine.
Remember to activate caching really helps speed up build times. I'm down to 15 minutes on consecutive builds on a ubuntu headless server on virtualbox with 4 cores & 8G RAM.
Getting the build installed was a bit trickier. TWRP flash over the last CM13 build didn't work.
I needed to flash the official ROM first, then install the latest TWRP version (//twrp.me/devices/samsungnexus10.html)
It's been running reasonably stable for two days with the 6.0 micro opengapps package apart from some PlayStore installation issues, but I haven't tested extensively.
Cheers

Your VM has twice the cores and twice the RAM as my laptop. I wish I could run this on my desktop, but the Linux subsystem is nearly impossible to build on >.<
I'll see if I didn't have that package installed and give it another go I suppose.

Build success! And in an hour fifteen minutes this time! (Last time it failed after six hours) I already had libxml2-utils installed. I did use distcc with another computer, but I'm not sure if it was even used. I suspect the majority of the speedup was due to caching from my last attempt.
Edit: I can't for the life of me get the home button to work...
I'm having the exact issue described here, but no solutions will work.

Hmm, home button works fine for me.
I've only got one bug that I had infrequently on the official CM builds, too: I can only install one app from the play store at a time.
Have to close the playstore and reopen it. That's probably related to GAPPS, though.
If you want, you can try out the build I'm currently running. Not absolutely fresh, but haven't had any problems except the one above:
Code:
//androidfilehost.com/?fid=745425885120704233

I compiled lineage os yesterday in 1,5h. I will try to install it this evening. I could upload it for everyone until there are official builds.

My build doesnt boot. I don't know if the file size of the zip is right. Mine is 283 mb . @zerebruin

@XxM4tzexX not sure, if build size is a good indicator. My build from Jan 27 build was 278.4 MB (291,889,838 Bytes).
Just built again with a fresh repo sync and that was 278.4 MB (291,885,568 Bytes). So not much of a difference.
Your installation works, just not the system bootup? which bootloader are you using?

zerebruin said:
@XxM4tzexX not sure, if build size is a good indicator. My build from Jan 27 build was 278.4 MB (291,889,838 Bytes).
Just built again with a fresh repo sync and that was 278.4 MB (291,885,568 Bytes). So not much of a difference.
Your installation works, just not the system bootup? which bootloader are you using?
Click to expand...
Click to collapse
Installation is fine although the install process is quite fast compared to a installation of cm. What do you mean by 'which bootloader'?

sorry, I meant the recovery, of course. still getting mixed up with terms here sometimes :|
Are you using the stock recovery or a custom one like TWRP or CWM?
They might give more/better feedback on installation errors.

zerebruin said:
sorry, I meant the recovery, of course. still getting mixed up with terms here sometimes :|
Are you using the stock recovery or a custom one like TWRP or CWM?
They might give more/better feedback on installation errors.
Click to expand...
Click to collapse
i'm using TWRP.
Are you using repo sync or repo sync -c (to downoad only the current brunch, should not make any difference)?

I've been using the full repo sync...
I'm using TWRP 3.02 and If I remember correctly, I needed to do a full wipe for the first install to work. Then again, after the installation went through it all worked fine.
I guess the next step would be to go through the build log...

I finally got it working now.

Congrats!
Out of interest: What was the fix?

Related

ZTE Open Firefox OS build thread (Mar25, updated for 3.0 build)

Hi,
I am new to Firefox OS, just got my ZTE Open last week. (used $10 from eBay)
I followed the instruction on the internet and XDA developers, compiled and flashed Firefox OS 2.1 into the ZTE Open.
Here is a link to the *.img files, feel free to play around with it.
https://drive.google.com/file/d/0B7HdrUmGwI8GRGlSZDdjMTBLMkk/edit?usp=sharing
2.1 seems running fine (so far so good), haven't seen it crashes since I flashed it this morning.
I can make phone call, surf the web, install new apps from the market, play mp3 and video files and the GPS is working.
It still has the same problems as the 1.3 build, the FM radio only works with speaker, the keyboard always display capital, recording video crashed the camera app after 2 seconds.
Here are the steps.
1. Update to official 1.1 release B06
2. Flash the 1.3 *.img built by linr76. (BTW, mine is a US version, but linr76's build is UK version, but it seems OK)
3. Flash my 2.1 *.img files. (pull the files from git on June 19, backup the system files from my phone on the 1.3 build)
BTW, I actually want to build 1.3 running BRANCH=1.3 VARIANT=user ./build.sh, but somehow the build script compiled 2.1 for me.

hevangel said:
2.1 seems running fine (so far so good), haven't seen it crashes since I flashed it this morning.
I can make phone call, surf the web, install new apps from the market, play mp3 and video files and the GPS is working.
It still has the same problems as the 1.3 build, the FM radio only works with speaker, the keyboard always display capital, recording video crashed the camera app after 2 seconds.
Click to expand...
Click to collapse
Thanks for the v2.1 compile! I flashed it to my Open today as well.
I noticed the same issues as you, as well as some new ones:
"Home" orb light doesn't work
Screen timeout doesn't work properly (10 seconds no matter what you set it to)
However, it is really awesome of you to get this compile out there for people to test and use
I'm trying (unsuccessfully) to get my 1.4 user to compile.

hevangel said:
Hi,
I am new to Firefox OS, just got my ZTE Open last week. (used $10 from eBay)
I followed the instruction on the internet and XDA developers, compiled and flashed Firefox OS 2.1 into the ZTE Open.
Here is a link to the *.img files, feel free to play around with it.
https://drive.google.com/file/d/0B7HdrUmGwI8GRGlSZDdjMTBLMkk/edit?usp=sharing
2.1 seems running fine (so far so good), haven't seen it crashes since I flashed it this morning.
I can make phone call, surf the web, install new apps from the market, play mp3 and video files and the GPS is working.
It still has the same problems as the 1.3 build, the FM radio only works with speaker, the keyboard always display capital, recording video crashed the camera app after 2 seconds.
Here are the steps.
1. Update to official 1.1 release B06
2. Flash the 1.3 *.img built by linr76. (BTW, mine is a US version, but linr76's build is UK version, but it seems OK)
3. Flash my 2.1 *.img files. (pull the files from git on June 19, backup the system files from my phone on the 1.3 build)
BTW, I actually want to build 1.3 running BRANCH=1.3 VARIANT=user ./build.sh, but somehow the build script compiled 2.1 for me.
Click to expand...
Click to collapse
BRANCH=v1.3 instead. And use VARIANT=userdebug would be better since it gets you more or less the same as eng build but not enabled by default (root acces, etc.).
Regarding the bugs you are mentionning, I have no issue on other devices with FM Radio app. Keyboard displaying capital is not a bug, it's a change from UX. Video recording crashing is a legit bug however.

lissyx said:
Keyboard displaying capital is not a bug, it's a change from UX.
Click to expand...
Click to collapse
That does not seem, to me, to be a change made for the better. The iOS keyboard has this same behavior, and it feels broken there as well.
What is the reasoning behind making the soft-keyboard case insensitive/static?
hevangel said:
BTW, I actually want to build 1.3 running BRANCH=1.3 VARIANT=user ./build.sh, but somehow the build script compiled 2.1 for me.
Click to expand...
Click to collapse
Hevangel, I issued my build with BRANCH=v1.4 VARIANT=userdebug ./build.sh and it build v2.1 for me as well.

Hevangel,
I was informed by gerard-majax on the #b2g IRC channel that the reason you and I got the v2.1 build was because we issued the commands wrong. You need to set the BRANCH and VARIANT during the ./config.sh stage, not at the ./build.sh stage like you and I did.
I have successfully compiled the BRANCH=v1.4 VARIANT=userdebug 2014-06-19(svn) FirefoxOS and flashed it to my Open.
I ran ./flash.sh gaia && ./flash.sh gecko over my v1.2(zte) install and then rebooted and cleared the cache partition. This gives me a working, but highly unstable Inari.
Working:
Prox/light sensor
Light orb on Home button
Everything else except known limitations (FM only over speaker)
Not Working:
All apps are unstable
b2g will crash randomly
Link to compiled images:
http://1drv.ms/Vp6rz4

Why it still says 13./1.4 Prerelease?

LinuxHolic said:
Why it still says 13./1.4 Prerelease?
Click to expand...
Click to collapse
What do you mean?
If you want to change branches to build v2.1, you'll need to do this.
$home\username\B2G
git pull
BRANCH=master VARIANT=userdebug ./config.sh inari
./repo sync

Saijin_Naib said:
What do you mean?
If you want to change branches to build v2.1, you'll need to do this.
$home\username\B2G
git pull
BRANCH=master VARIANT=userdebug ./config.sh inari
./repo sync
Click to expand...
Click to collapse
No i mean if i install 1.3 or 1.2 on my phone than why it still says 1.2/1.3 Prerelease in the Device Information?

LinuxHolic said:
No i mean if i install 1.3 or 1.2 on my phone than why it still says 1.2/1.3 Prerelease in the Device Information?
Click to expand...
Click to collapse
OH! Any image compiled by a non-official source/partner will always be tagged Pre-Release. Quality control thing, I think? Not sure.

Saijin_Naib said:
OH! Any image compiled by a non-official source/partner will always be tagged Pre-Release. Quality control thing, I think? Not sure.
Click to expand...
Click to collapse
I can't download your v2.0 and 2.1 builds from One Drive

Here you can find updated for 1.3 and 2.1 for ZTE Open images.
http://157.88.55.36:8080/job/master-inari/
http://157.88.55.36:8080/job/1.3-inari/
To update use these steps:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot ramdisk.img
fastboot flash system system.img
fastboot flash userdata userdata.img

elav said:
Here you can find updated for 1.3 and 2.1 for ZTE Open images.
http://157.88.55.36:8080/job/master-inari/
http://157.88.55.36:8080/job/1.3-inari/
To update use these steps:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot ramdisk.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Please, which boot.img you used? And what partition for the ramdisk.img you has taken?

2.1 build and Keon??
Hello,
I have a ZTE Open and it's currently running Prerelease 1.3. I must say I'm quite happy with its performance and the bugs aren't crippling at all. I was thinking of upgrading to the 2.1 build from this thread. I was wondering though since I saw that there's a Geeksphone Keon 2.0 build. Since it looks exactly like a ZTE Open, the question popped into my head: "would that build work on a ZTE Open?". SO I turn that question over to the community here at XDADevelopers
Also, can I jump from 1.3 to 2.1? or would I have to do more of a 1.3 -> 1.4 -> 2.0 -> 2.1 sort of upgrade path?
Thanks!

TheEternalAbyss said:
Hello,
I have a ZTE Open and it's currently running Prerelease 1.3. I must say I'm quite happy with its performance and the bugs aren't crippling at all. I was thinking of upgrading to the 2.1 build from this thread. I was wondering though since I saw that there's a Geeksphone Keon 2.0 build. Since it looks exactly like a ZTE Open, the question popped into my head: "would that build work on a ZTE Open?". SO I turn that question over to the community here at XDADevelopers
Also, can I jump from 1.3 to 2.1? or would I have to do more of a 1.3 -> 1.4 -> 2.0 -> 2.1 sort of upgrade path?
Thanks!
Click to expand...
Click to collapse
No, Geeksphone Keon builds won't work on ZTE Open because both phones have different hardware
And yes you can directly jump from V1.3 to V2.1
Precompiled images by Saijin_Naib of ZTE Open

LinuxHolic said:
No, Geeksphone Keon builds won't work on ZTE Open because both phones have different hardware
And yes you can directly jump from V1.3 to V2.1
Precompiled images by Saijin_Naib of ZTE Open
Click to expand...
Click to collapse
Please see my thread here: ZTE Open (Inari) Build Versions & Issues for an overview of the various issues & limitations I've encountered on each SVN compile version using my ZTE Open.
If you want full hardware functionality, you're stuck with the official ZTE ROMs only. If missing GPS & home orb light don't bother you, then you can pick and choose the other versions at will.

Saijin_Naib said:
Please see my thread here: ZTE Open (Inari) Build Versions & Issues for an overview of the various issues & limitations I've encountered on each SVN compile version using my ZTE Open.
If you want full hardware functionality, you're stuck with the official ZTE ROMs only. If missing GPS & home orb light don't bother you, then you can pick and choose the other versions at will.
Click to expand...
Click to collapse
I'll definitely check them out. I don't use gps on my ZTE Open, so that is a non issue for me. In my 1.3 pre-release the home light works just fine. I don't think it would bother me much really. I'll just have to see. I may just wait for some new phones to come out before spending time on my poor broken ZTE Open lol
Thank you though for the info.

TheEternalAbyss said:
I'll definitely check them out. I don't use gps on my ZTE Open, so that is a non issue for me. In my 1.3 pre-release the home light works just fine. I don't think it would bother me much really. I'll just have to see. I may just wait for some new phones to come out before spending time on my poor broken ZTE Open lol
Thank you though for the info.
Click to expand...
Click to collapse
No problem.
So far in my testing, v1.4 seems to be the most recent SVN that will have a working Home Orb light, but it was also far and away the most unstable version I have tested yet (surprisingly).

Flash steps
TheEternalAbyss said:
I'll definitely check them out. I don't use gps on my ZTE Open, so that is a non issue for me. In my 1.3 pre-release the home light works just fine. I don't think it would bother me much really. I'll just have to see. I may just wait for some new phones to come out before spending time on my poor broken ZTE Open lol
Thank you though for the info.
Click to expand...
Click to collapse
Hi!! Thank you very much for the information and the images, it really helps when you try to compile the source from a computer that is not debian 64...
I am in the way of flashing my ZTE open to 2.0 and i found in the Precompiled images by Saijin_Naib there is only a ramdisk,userdata and system images, ¿which are the correct steps to get the update? do i need any other boot.img or recovery.img that is not present in the repository?
BTW, i have tried to do just fastboot flash boot ramdisk.img as @elav said below but i get an error: FAILED (remote: image is not a boot image)
Thanks!!

LinuxHolic said:
No, Geeksphone Keon builds won't work on ZTE Open because both phones have different hardware
And yes you can directly jump from V1.3 to V2.1
Precompiled images by Saijin_Naib of ZTE Open
Click to expand...
Click to collapse
Hi!! Thank you very much for the information and the images, it really helps when you try to compile the source from a computer that is not debian 64...
I am in the way of flashing my ZTE open to 2.0 and i found in the Precompiled images by Saijin_Naib there is only a ramdisk,userdata and system images, ¿which are the correct steps to get the update? do i need any other boot.img or recovery.img that is not present in the repository?
BTW, i have tried to do just fastboot flash boot ramdisk.img as @elav said below but i get an error: FAILED (remote: image is not a boot image)
Thanks!!

mahdsip said:
Hi!! Thank you very much for the information and the images, it really helps when you try to compile the source from a computer that is not debian 64...
I am in the way of flashing my ZTE open to 2.0 and i found in the Precompiled images by Saijin_Naib there is only a ramdisk,userdata and system images, ¿which are the correct steps to get the update? do i need any other boot.img or recovery.img that is not present in the repository?
BTW, i have tried to do just fastboot flash boot ramdisk.img as @elav said below but i get an error: FAILED (remote: image is not a boot image)
Thanks!!
Click to expand...
Click to collapse
Connect your phone in USB Debugging Mode and enter the following commands:
adb reboot-bootloader
fastboot erase userdata
fastboot erase cache
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache ramdisk.img
And you're good to go

MultiROM with Lollipop builds coming out...

14 November 2014
There are several great lollipop builds out there currently with a lot of work being done to give us all a great product. So far multirom is working perfectly in Primary slot as well as secondary slots in multirom with @scrosler AOSP builds 5-7, Build 7 here as well as @scrosler Factory Stock Rooted ROM LRX21P which can be found here
If your favorite dev is making a Lollipop build for the Nexus 7 and you have successfully used it with multirom, please let us know so we can tag it and place a link for future users to this thread.
06 November 2014 (ORIGINAL POST)
Ever since I mentioned this in an email, I have received a few requests on how I got @scrosler Pure AOSP 5.0 Build to work with MultiROM on my Nexus 7 flo.
First off, I have only done this with the build by @scrosler which can be found HERE, but I would guess that it can work with similar builds.
Secondly, this worked perfectly on my device. If you mess up your device, I am not responsible.
Thirdly, and most importantly thank you to:
@scrosler for the lollipop build and all the extras
@Chainfire for SuperSU
@sykopompos for the permissive boot image
@flar2 for the ElementalX Kernel
@Tasssadar for MultiROM
if I forgot to mention someone, please holler at me
Okay, on to the easy stuff...
This has been tested and is successful on Nexus 7 flo (2013). For information on Deb procedures, please refer to this post by @drewski_1 but at the request of @scrosler, please bring all multirom questions back to this thread. Also for Nexus 7 deb, @darkobas has given us a modified boot image to use which can be found here
This ROM (this particular build I've been working with) cannot go into a secondary slot of MultiROM, I have tried everything. If you found a way, please share it.
1. go HERE and read the OP, download necessary files, (latest build, latest gapps, busybox flashable, etc), update bootloader if needed, and goto step 2.
2. go HERE to get ElementalX Kernel for Lollipop
3. go HERE to get a very permissive boot image that works perfectly with this setup.
4. go HERE to get the latest SuperSU
After you have everything in order, reboot into recovery...
1. Move your primary ROM into a secondary slot in TWRP recovery.
2. Go back out to the main TWRP page (outside of Advanced/MultiROM)
3. Install Scotts Pure AOSP build 5.0
4. Install Recovery Saver
5. Reboot Recovery (just to make sure your recovery is still intact)
6. Install GAPPs
7. Install Permissive boot image
8. Install SuperSU
9. Install ElementalX Kernel
10. Reboot and Enjoy
When you get into your ROM, check to verify that your SuperSU is functioning properly and set your ROM up to your likings. :good:

appreciated clarification
OP said:
I've gotten a few requests about multirom with this build since I posted something earlier. If you need to know how to do it (you should already if you're using multiROM), you can check it out HERE.
I didn't want to post the info in here and muddy up the dev thread.
http://forum.xda-developers.com/showpost.php?p=56558107&postcount=802
Click to expand...
Click to collapse
I know but tend to forget details over time - THANKS. I like to verify procedures before committing anyway - saves me from bricks soft or hard. With the file structure changes, etc I like to know what I'm getting into and how best to do it safely.
I'm in the process of moving roms and should have this latest L in slot #1 before dusk, heh.

Heads up, the modified boot image does not stick after booting into secondary ROM (IE KitKat or other earlier based ROM), so if this happens just reflash modified boot image. You will be good to go and back to root. :good:
Also, @darkobas has created updated boot images for both FLO and DEB. Would be great if OP could be modified as such. The new images can be found in @scrosler 's thread.
Make sure to have MultiROM zip and recovery installed when trying this method, as the MultiROM code must be injected for it to work well.

hhairplane said:
Heads up, the modified boot image does not stick after booting into secondary ROM (IE KitKat or other earlier based ROM), so if this happens just reflash modified boot image. You will be good to go and back to root. :good:
Also, @darkobas has created updated boot images for both FLO and DEB. Would be great if OP could be modified as such. The new images can be found in @scrosler 's thread.
Make sure to have MultiROM zip and recovery installed when trying this method, as the MultiROM code must be injected for it to work well.
Click to expand...
Click to collapse
I had no issues with the modified boot image sticking after booting into either of my secondary Roms.
I will look at the modified boot images in a few. I'm reading through scrosler's thread now.

Megaflop666 said:
I had no issues with the modified boot image sticking after booting into either of my secondary Roms.
I will look at the modified boot images in a few. I'm reading through scrosler's thread now.
Click to expand...
Click to collapse
It might just be with Deb, then...

hhairplane said:
It might just be with Deb, then...
Click to expand...
Click to collapse
Would be my guess. I am currently reading through the section in scrosler's thread that you mentioned. Is the new boot image you mentioned for deb only?

Megaflop666 said:
Would be my guess. I am currently reading through the section in scrosler's thread that you mentioned. Is the new boot image you mentioned for deb only?
Click to expand...
Click to collapse
Yes, but I think there is a different boot image in scrosler's thread (not for Lollipop preview, but for AOSP scrosler build). It is attached in OP and made by darkobas. Not sure what is different than older boot image.
Also, my secondary are KitKat and earlier ROM's, not Lollipop-should be a different boot image. Not sure if that's the same for you? Perhaps, flashing a KitKat boot may solve the problem, since it seems that MultiROM has to mod Lollipop's for KitKat to work?

hhairplane said:
Yes, but I think there is a different boot image in scrosler's thread (not for Lollipop preview, but for AOSP scrosler build). It is attached in OP and made by darkobas. Not sure what is different than older boot image.
Also, my secondary are KitKat and earlier ROM's, not Lollipop-should be a different boot image. Not sure if that's the same for you? Perhaps, flashing a KitKat boot may solve the problem, since it seems that MultiROM has to mod Lollipop's for KitKat to work?
Click to expand...
Click to collapse
OP has been updated, I think I found all the pertinent info you mentioned regarding making deb part of this thread. If I missed something, please let me know. Thanks

Megaflop666 said:
OP has been updated, I think I found all the pertinent info you mentioned regarding making deb part of this thread. If I missed something, please let me know. Thanks
Click to expand...
Click to collapse
This one is the better Deb Modified Boot.img http://forum.xda-developers.com/showpost.php?p=56564714&postcount=856 Sorry, I should have more clearly laid it out myself.

hhairplane said:
This one is the better Deb Modified Boot.img http://forum.xda-developers.com/showpost.php?p=56564714&postcount=856 Sorry, I should have more clearly laid it out myself.
Click to expand...
Click to collapse
Its all good. There's been conversation scattered everywhere, that's one of the biggest reasons I wanted to start this thread.
Edit: Link has been updated to the correct post.

I followed the OP instructions very closely (twice) and can get the primary L rom installed, rooted and running smooth - very smooth, in fact. Nice rom scrosler! But the rest of my multirom roms won't load even the boot ani - I get only to the Google screen and loop there on any rom - I have a jellybean, a couple of kitkats and one of the dev releases of L and they all do the same. I've not yet tried to install a secondary rom but will.
Anyone with a suggestion? I have the new primary backed up and have some nandroids of a couple of the secondarys. I'm not that worried about losing them and have considered starting from scratch if nec.. tia!

dadeo1111 said:
I followed the OP instructions very closely (twice) and can get the primary L rom installed, rooted and running smooth - very smooth, in fact. Nice rom scrosler! But the rest of my multirom roms won't load even the boot ani - I get only to the Google screen and loop there on any rom - I have a jellybean, a couple of kitkats and one of the dev releases of L and they all do the same. I've not yet tried to install a secondary rom but will.
Anyone with a suggestion? I have the new primary backed up and have some nandroids of a couple of the secondarys. I'm not that worried about losing them and have considered starting from scratch if nec.. tia!
Click to expand...
Click to collapse
Try going into twrp into one of the secondary ROMs and fixing it's boot? Something must've gotten missed in the setup or something happened because this issue is new.

Megaflop666 said:
Try going into twrp into one of the secondary ROMs and fixing it's boot sector?
Click to expand...
Click to collapse
I should use the remove/add boot.img function? I've never done this but will look into how. If you have a link to some specifics it would be much appreciated.
Thanks! :good:
edit to add:
I am able to install/add roms, btw. I successfully re-added a jellybean rom from nandroid backup just fine. I'll probably throw them out except one anyway. I'm not sure what happened or when but I followed your steps verbatim. thanks again.

dadeo1111 said:
I should use the remove/add boot.img function? I've never done this but will look into how. If you have a link to some specifics it would be much appreciated.
Thanks! :good:
Click to expand...
Click to collapse
All the multiform specifics can be found in that thread here.
I would try restoring your backup first and see if that fixes the secondary ROMs. Especially since you don't have much time in the lollipop ROM yet. If you restore and it works, let me know.

@scrosler has build 4 up, please see his thread which can easily be found in the OP, second paragraph.
OP will be updated shortly if necessary.
Okay, I've gone through this a few times now. @scrosler work is perfect unless we want to use it on multirom. Continue the same steps listed in the OP or you will lose root, as well as the ability to boot multiple Roms.

Build 6 is out from @scrosler. Follow the same installation process listed in the OP. Only add on would be that scrosler added a flashable busy box zip on his threads OP that you can flash in twrp around the same time you flash SuperSU. :thumbup:

Megaflop666 said:
Build 5 is out from @scrosler. Follow the same installation process listed in the OP. Only add on would be that scrosler added a flashable busy box zip on his threads OP that you can flash in twrp around the same time you flash SuperSU. :thumbup:
Click to expand...
Click to collapse
I have successfully installed @scrosler's latest (build 6) as a secondary rom and in the usual fashion - Flash ROM, Flash GAPPS. I then booted into the new install and allowed Google to update me (successfully). Everything worked but root apps, of course. I then rebooted to TWRP, flashed the beta superuser zip - rebooted and checked and have root. All per usual and as expected.
Titanium bup didn't work after accepting root permissions but it was from the play store so this is also per usual. I'll try the one I got from twitter and expect that to work too - as usual. If not I'll post so here.
This is going to be my daily driver now. :good:
I'll add a custom kernel later. ElementalX 3.x has been solid for me on all lollypop roms so probably that one.

dadeo1111 said:
I have successfully installed @scrosler's latest (build 6) as a secondary rom and in the usual fashion - Flash ROM, Flash GAPPS. I then booted into the new install and allowed Google to update me (successfully). Everything worked but root apps, of course. I then rebooted to TWRP, flashed the beta superuser zip - rebooted and checked and have root. All per usual and as expected.
Titanium bup didn't work after accepting root permissions but it was from the play store so this is also per usual. I'll try the one I got from twitter and expect that to work - as usual. If not I'll post so here.
This is going to be my daily driver now. :good: I'll add a custom kernel later. ElementalX 3.x has been solid for me on all lollypop roms so probably that one.
Click to expand...
Click to collapse
Awesome. I was going to try it with the latest build later when I had some time but you saved me the work. :thumbup:
Besides checking tibu, also check es file explorer. I have both working on this build in the primary slot but I know a lot of people are struggling with es.

Megaflop666 said:
Awesome. I was going to try it with the latest build later when I had some time but you saved me the work. :thumbup:
Besides checking tibu, also check es file explorer. I have both working on this build in the primary slot but I know a lot of people are struggling with es.
Click to expand...
Click to collapse
ES seems fine - even sees my lan. Also sees and navigates sd card but am unable to do root tasks in system folder (rename, copy, delete). When I do a root action it requests root and I accept then the task fails.

dadeo1111 said:
ES seems fine - even sees my lan. Also sees and navigates sd card but am unable to do root tasks in system folder (rename, copy, delete). When I do a root action it requests root and I accept then the task fails.
Click to expand...
Click to collapse
Are you using the permissive boot image from the OP and elementalX kernel 3.01? Just curious why I have full function with ES and other people don't.

How to Install Official CyanogenMod 13 on OnePlus X [Guide]

OnePlus X is the only nonflagship device from OnePlus. The X is not a flagship but definitely worth buying because of its High-end specs and relatively low price with a wide-open attitude towards user customization which makes OnePlus X more popular. The OnePlus Company is getting a big boon today, as official CyanogenMod support comes to the smaller, cheaper OnePlus X. The X is equipped with the custom Oxygen OS, but for those who prefer the community-built ROM, Official CM 13 is now available.
Oxygen still hasn't been updated to Marshmallow code on OnePlus X, except for a beta available on the OnePlus 2. CyanogenMod 13 is based on Android 6.0.1, plus the various tweaks and customizations built by the CM team. The Latest build provides all the Android 6.0.1 Marshmallow features and a great battery life on your device. It is a great custom ROM that runs blazing fast and smooth. You will able to install this Official CM 13 in your OnePlus X using this tutorial. It is necessary to Root your phone and has a custom recovery installed in order to install this CM 13 zip file because Cyanogen zips are not a Signed Zip of official OnePlus firmware.
TWRP Custom Recovery is Available for OnePlus X. If you've already rooted your phone, you can install TWRP via the official app. If not, grab the images from the web and install them via fastboot with your PC. You may know the drill. Or just Google it up.
If this is your very first time installing a custom ROM, we understand you would want to make sure your installation process go as smooth as possible. So before installation, make sure you have backed up your important Apps and Data with Titanium Backup (Recommended). When installing this Official CM 13 ROM based on Android 6.0.1 Marshmallow, your entire Data + System will be cleaned — like a brand new phone.
All set and ready? Good. Now, let’s proceed with the tutorial below and install Official CM 13 ROM based on Android 6.0.1 Marshmallow on your OnePlus X.
Download CM 13 Onyx Latest Build :
This is the Officially Updated download page of CyanogenMod where you will find the latest Nightly or Snapshot build from CyanogenMod. We suggest you to download the snapshot build (if available) as the snapshot builds are highly Stable. If you rely on your OnePlus X as a "daily driver" phone you might not want to flash the very first nightly.
Mod edit: link removed.
Download Official Google Apps :
Make sure to Select ARM > Android 6.0 > Pico to download for the best result. Later on you can download all the GApps of your choice from Play Store.
Click here to Download GApps
I have put together a detailed step by step installation instruction so that the first time users doesn't face any problem. If you are used to installing custom ROMs with TWRP recovery, then this should not be any different for you. Please read every step carefully so that your installation goes smooth without facing any problem.
As I mentioned earlier, you need to have a custom recovery (TWRP for this tutorial) installed on your phone. Please do that first and then get back to this tutorial. Make sure you read this tutorial once before actually performing it on your device.
Step 1 : Download Official CM 13 ROM and GApps from the above link for OnePlus X to your computer.
Step 2 : Connect and mount your OnePlus X USB memory to your computer using the USB cable.
Step 3 : Now copy/paste the downloaded CM 13 zip and Google Apps zip files to your
phone memory / SD card. Make sure the files are in the phone memory root (not in any folder).
Step 4 : Then turn OFF your phone and disconnect from the USB cable.
Step 5 : Now to get in the Recovery Mode. Switch ON the phone while pressing and holding Volume Down + Power buttons together.
Step 6 : Once you are in TWRP Recovery, perform a full data wipe by tapping on the ‘Wipe’ button. Then swipe on the “Swipe to Factory Reset” option at the bottom.
Step 7 : Now go back to the main menu and then tap on the ‘Install’ button. From the list, choose the ZIP file that you copied to your phone memory in Step 3.
Step 8 : Confirm installation on the next screen by swiping on the “Swipe to Confirm Flash” option. The installation procedure should start now.
Google Apps: Once the ROM installation is completed, repeat the above steps from Step 7 to Step 8 for the Google Apps zip file as well and install it on your phone.
Step 9 : Tap on the “Wipe cache/dalvik” button if you get into any boot loops or other issues.
Step 10 : You can now reboot your phone by selecting the “Reboot System” button.
Your One will boot now and it might take about 5 minutes to boot on your first time after flashing a new ROM. So, please wait.
That’s it! Your OnePlus X should now have Official CyanogenMod 13 ROM based on Android 6.0.1 Marshmallow installed on your phone! Go to Settings > About phone to verify.
Any problem during installation ? Do let us know by commenting below! Also, don't forget to share, if you found this post helpful.

It remains to wait for a strong response from OnePlus.
Nothing so well does not strengthen as competition.

Very good guide for the first official release of cm13. The future looks bright enough.
Omicron Technics

ze7zez said:
It remains to wait for a strong response from OnePlus.
Nothing so well does not strengthen as competition.
Click to expand...
Click to collapse
Oxygen Team is the Slowest Team to update their OS. RIP..! OnePlus X got CM officially

sniper20 said:
Very good guide for the first official release of cm13. The future looks bright enough.
Omicron Technics
Click to expand...
Click to collapse
I will not go back to OOS again even this is nightly build

I hope noise cancelation mic works.
Sent from my SM-G935T using Tapatalk

slow charging
showing Charging Rapidly (4hrs until full)
now all ok

Nightlies include ota updates? Or we have to manually flash all d updates or updated versions

So how is batterylife ?

3rd NIGHTLY update
cm-13.0-20160426-NIGHTLY is up :good:

shakeelsaraf said:
Nightlies include ota updates? Or we have to manually flash all d updates or updated versions
Click to expand...
Click to collapse
You will receive OTA updates from Nightly.

Hello mates
I am new in root phones and Custom mod files
Can u tell me how can I root my one plus 2 and how can I install cyanogenmod 13

Well, my installation fails everytime? Tried the latest and second latest versions. "installation failed" after 10sec of start.
Any ideas?
edit. Tried all versions, same result. Somethings f*cky now?

FWIW, this guide works well but unfortunately I got into a constant loop around Google Play Services and Setup Wizard crashing.
I resolved this by copying the CM and Gapps packages to internal memory (not external SD), removing the SD card and then re-flashing both, making sure to flash Gapps straight after CM (ie. not rebooting in-between).

BruintjeDeBart said:
So how is batterylife ?
Click to expand...
Click to collapse
Battery life is good even it is nightly. I use Greenify with Xposed.

E1001
Mine is 1+ x china version but root already for google service. Is there any problem witt cm13 upgrade ?

bricky23 said:
I hope noise cancelation mic works.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
no, it doesn't

Is this need root phone?

There is an existing thread for this here:
http://forum.xda-developers.com/one.../rom-cyanogenmod-13-x-oneplus-x-onyx-t3279784
Thread closed.

New Nexus 6P, endless problems after flashing CM13

Hello,
Bought a Nexus 6P the other day and now attempting to install CM13, latest official snapshot. Of course, I ran into issues., and I am in dire need of help.
I unlocked the bootloader via Fastboot. Then installed the latest TWRP, also using Fastboot. All fine so far. Then I tried flashing CM13, which first failed because I missed to wipe the data/cache. I realised my mistake, re-did it and successfully flashed CM13.
The installation process was successful, yet when I boot the phone up and it finishes loading CM, I get the following error message:
"Android-system
An internal problem has occurred. Contact the manufacturer if you want more information."
Why is this happening? And more importantly, how do I fix it?
I did try and ignore the warning and proceeded to install OpenGAPPS from TWRP. As soon as CM loads up again however, there is an infinite stream of Google Play Service and "first time setup" crash messages, making the phone unusable.
On a related note. The guide at https://wiki.cyanogenmod.org/w/Install_CM_for_angler tells me to "update the vendor.img", but it never tells me how I figure out which Build ID I need for my version of CM13. The guide hints at MTC19V, but I am not sure if this is right. I did try flashing this, but nothing changed.
Please advice, I am stuck.

First off you need to figure out what Vendor you need, this can be done by going to about phone/ settings and looking at what security patch level you are on. The latest is August and that would be vendor image MTC20F. you can google search or go to androidfilehost.com to download that or any other vendor image.
To flash you boot into TWRP and choose install and then choose install image in the bottom right hand corner then you choose the file and select Vendor image, then flash and you're all set.
Here's a lazy link for the last 2 vendor files: http://download.dirtyunicorns.com/files/misc/vendor_images/angler/

You need to flash CM13 and Gapps before booting and not separately.
Like the above post you need to check what vendor you need.

Wickidmasshole said:
First off you need to figure out what Vendor you need, this can be done by going to about phone/ settings and looking at what security patch level you are on. The latest is August and that would be vendor image MTC20F. you can google search or go to androidfilehost.com to download that or any other vendor image.
To flash you boot into TWRP and choose install and then choose install image in the bottom right hand corner then you choose the file and select Vendor image, then flash and you're all set.
Here's a lazy link for the last 2 vendor files: http://download.dirtyunicorns.com/files/misc/vendor_images/angler/
Click to expand...
Click to collapse
Ahh, I see. That makes sense now. Thanks!
therock3181 said:
You need to flash CM13 and Gapps before booting and not separately.
Like the above post you need to check what vendor you need.
Click to expand...
Click to collapse
Really? I didn't think it would matter. Anyways, even with this part fixed, would it not continue to claim being corrupted? I understood it as if CM itself has an issue and not GApps.

Wickidmasshole said:
First off you need to figure out what Vendor you need, this can be done by going to about phone/ settings and looking at what security patch level you are on. The latest is August and that would be vendor image MTC20F. you can google search or go to androidfilehost.com to download that or any other vendor image.
To flash you boot into TWRP and choose install and then choose install image in the bottom right hand corner then you choose the file and select Vendor image, then flash and you're all set.
Here's a lazy link for the last 2 vendor files: http://download.dirtyunicorns.com/files/misc/vendor_images/angler/
Click to expand...
Click to collapse
Actually, latest is from 2nd April. The only later builds of CM I see for this phone is Nightlies.
therock3181 said:
You need to flash CM13 and Gapps before booting and not separately.
Like the above post you need to check what vendor you need.
Click to expand...
Click to collapse
Sadly, I still get the warning once CM finishes loading. It did however get rid of the infinite crashes. Progress!

I was saying the latest available vendor.img was from august. I use DU so i don't know how far behind CM nighties are.

NodCom said:
Actually, latest is from 2nd April. The only later builds of CM I see for this phone is Nightlies.
Sadly, I still get the warning once CM finishes loading. It did however get rid of the infinite crashes. Progress!
Click to expand...
Click to collapse
The current GitHub for angler on cyanogen is showing mtc20f updated ten days ago. So if your nightly was built after that, then it would be that Vendor image.

Gizmoe said:
The current GitHub for angler on cyanogen is showing mtc20f updated ten days ago. So if your nightly was built after that, then it would be that Vendor image.
Click to expand...
Click to collapse
I am only willing to use stable builds, not nightlies.

Next time do some research before you just start flashing stuff.. especially since 5x and 6p came out Google updates every month.
So the best thing to do when you buy a new device is read and learn and i learned on both devices the best thing you can do first is flashing the latest factory images.
Also i find it strange that the first thing you flash on a nexus is cm, but that's all up to you of course. There are so many great roms out there that are way better then cm in my opinion.
Sent from my Nexus 6P using XDA-Developers mobile app

Pollie81 said:
Next time do some research before you just start flashing stuff.. especially since 5x and 6p came out Google updates every month.
So the best thing to do when you buy a new device is read and learn and i learned on both devices the best thing you can do first is flashing the latest factory images.
Also i find it strange that the first thing you flash on a nexus is cm, but that's all up to you of course. There are so many great roms out there that are way better then cm in my opinion.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
I agree. CM was great on the N4 and N5 but not so much on the 6P

NodCom said:
I am only willing to use stable builds, not nightlies.
Click to expand...
Click to collapse
Why would I care which release you prefer? You asked how you messed up flashing CM and people responded. It's because of mismatched Vendor images. And no one seemed to know for sure which one it is so I looked for you. I've compiled CM with the right proprietary blobs and I have had no stability issues.

Stock ROMs Factory v6.1 , v8.3 , v8.4 , v8.5 , v8.7, V9.0, V9.2-patch : v21

CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs

I flashed this but I didn't get the custom boot logo.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine

Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.

It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo

mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?

Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out

Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.

Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?

detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.

The app downloaded from f-droid worked for me as well, many thanks!

Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.

Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.

Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!

OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install

Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3

mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.

Database Users

welcome