[Q] Compiled OmniRom not booting

[Q] Compiled OmniRom not booting - Omni Q&A

Hi everyone,
I've successfully built OmniRom from source for my Nexus 5 using this guide: http://forum.xda-developers.com/google-nexus-5/general/guide-how-to-build-fav-kk-rom-cm-aokp-t2617919
The ROM builds fine and the omni-4.4.2-xxx-hammerhead-homemade.zip is created in /out/target/product/hammerhead.
However, when I flash that zip file, my phone is stuck on the Google logo and it won't boot into the system.
Is there anything I am missing?
A Google search didn't reveal anything.
Thanks in advance!

I'm assuming you've already downloaded and extracted the proprietary blobs, yes?
---
Posted from whatever phone booted today

I knew I was missing something. Can you point me to the right direction how to do it?
edit:// Nevermind, found it and building as we speak! Thanks!
edit2:// The missing proprietary blobs were the issue indeed. My phone just booted into my first self-built ROM. Cheers!
For anyone having the same issue: Here's a good guide for getting and extracting the missing files.

Related

Wifi error

Immediately after rooting my phone my wireless was permanently disabled. When trying to re-enable, the gui displayed "error" and nothing else.
I'm not new to linux and have successfully gotten adb and fastboot working under gentoo.
I have all the apks I need to root, but I erased my boot and recovery images when I tried to install the cyanogen mod. The cyanogen mod loops at the mytouch animated logo when I flash it to boot.
I have three simple questions:
First, has anyone successfully resolved the wifi "error" message? When I looked (yesterday) there were tons of confirmations about the problem, but not a single fix I could find.
Second, has anyone gotten cyanogen or clockworkrecovery working on the mt4g? It was very frustrating trying to get out-of-band access to the android market. It makes no sense to me whatsoever that access to free software should be controlled in any way by google. Have they been deliberately uncooperative in letting apks be downloaded to pcs?
Third, would anyone be willing to mail me copies of their boot.img or recovery.img? As I was unable to get clockwork recovery, I didn't backup my roms before trying to flash an attempted fix.
Help would be greatly appreciated.

Google hosts the market and the Market app itself is not open source, which if why they can and do prevent distribution of it. There's no restrictions of people distributing apks (license notwithstanding) through other means.
I think there's an alternate method to installing clockworkmod via fastboot. I reinstalled stock recovery this way, though I don't think that helps you without a signed system image.
There's also an ruu available but I don't think I've heard of anyone trying to user it yet.
Sent from my HTC Glacier using XDA App

poseidon1157 said:
Immediately after rooting my phone my wireless was permanently disabled. When trying to re-enable, the gui displayed "error" and nothing else.
I'm not new to linux and have successfully gotten adb and fastboot working under gentoo.
I have all the apks I need to root, but I erased my boot and recovery images when I tried to install the cyanogen mod. The cyanogen mod loops at the mytouch animated logo when I flash it to boot.
I have three simple questions:
First, has anyone successfully resolved the wifi "error" message? When I looked (yesterday) there were tons of confirmations about the problem, but not a single fix I could find.
Second, has anyone gotten cyanogen or clockworkrecovery working on the mt4g? It was very frustrating trying to get out-of-band access to the android market. It makes no sense to me whatsoever that access to free software should be controlled in any way by google. Have they been deliberately uncooperative in letting apks be downloaded to pcs?
Third, would anyone be willing to mail me copies of their boot.img or recovery.img? As I was unable to get clockwork recovery, I didn't backup my roms before trying to flash an attempted fix.
Help would be greatly appreciated.
Click to expand...
Click to collapse
the reason it's not working is because, I'm assuming, you followed the guide about forcing your update. When you did this it patches the kernel, but does not update the bcm4329.ko kernel module. There are a bunch of guides on how to root in the dev section. It looks to me like you started following my guide. If you look at my guide (entitled forcing update 2.2.1 and rerooting) it will give you the steps to complete the process with all files linked.
There are a bunch of us in IRC who would be willing to help.

Please post questions in Q&A section.

Black screen :(

Hi guys just wanted to ask for help from the expert porters.
I've been porting on my own this past weeks and my first try booted up well.
Tried another and still booted well.
But after sometime when I try porting again, it won't boot anymore.
It would pass the splash screen then after that would be BLACK SCREEN.
I'm just curious why this is happening when I did the same procedure I did with the other roms I ported and got it to boot well.
Hope someone could help me.
THANK YOU!

Please specify, which device's ROM were you porting and was it stock or CM7 based?
If it was CM7 based, I am sure there shouldn't be a problem porting it of you have read the guide correctly (rishabhraj one)
If it is stock based ROM of device other than S5830i, it can't be directly ported and you will have to add features and png manually to your device's framework

you must explain the "port" process you did,
what codes you reconfigured and binaries to get working,

I just copied the app,xbin,framework,font,media,lib,etc, and bin folders from port to base and edit buildprop. that's what I did with my first port and it booted well.. It was MIUI 3.4.5.. but when I'm trying to port the updated version, it won't boot anymore.

Take a log cat first

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.

Problems booting the open source kernel on the shield 2017

hi,
this was the first time compiling a kernel from android source. I'm actually a java and app dev, so this was actually new to me.
I wanted to have full ntfs support and maybe some other features on my shield so i thought i'll give it a try.
the first thing i tried was pulling the whole android source code from the nvidia git server. Then I followed the instructions except i changed "mp dev" to "mp bootimage -j5" to just build the kernel. (I also did no modifications to the kernel). All went well and I got the boot image.
I used this repo: rel-24-uda-r1-partner.
I flashed the boot image with fastboot, but when it boots up, the nvidia sign comes and after some time I get a message with a red exclamation mark, which says that the partitions are corrupted or something like that. Then I get a black screen.
I also dont want to open up the device to access the uart to read out the kernel messages.
I dont know what else to do. Am I missing something? Does the open source kernel even work on stock android rom?

have u tried wiping the data partition?

yes i have

Take a look at the last few posts on this thread https://forum.xda-developers.com/sh...ecovery-twrp-shield-android-tv-t3510456/page4

so do you mean i have to use a another toolchain?

Jahusa said:
so do you mean i have to use a another toolchain?
Click to expand...
Click to collapse
I believe so

It works now. I copied the kernel from the repo into a another folder, set the env variables for the cross compilers and compiled it.
With the help of some threads in the nvidia forum and google, i got everything compiled.
The kernel boots now. But there's still the red sign at boot. I have to figure it out later.
Edit: OK, i think I got it now. To remove the annoying sign, I have to somehow disable the boot verification.

@AndroidUser00110001 did you sign your trwp recovery image when you created it. If you didn't, then it would also trigger the boot verification. That's what I think.
Also thanks for your recovery image

That warning pops up once you unlock bootloader.
Jahusa said:
@AndroidUser00110001 did you sign your trwp recovery image when you created it. If you didn't, then it would also trigger the boot verification. That's what I think.
Also thanks for your recovery image
Click to expand...
Click to collapse

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