Database Users

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

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
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0

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.

New 6P owner, returning to Android after a few years away, seeking recommendations

Hey, was big into the android scene years ago, switched to other platforms for a bit just to play with them. Got a used 64 gig 6p and was thinking about dropping a custom rom onto it, but I don't know what's good anymore. What's the most stable, daily driver, minimalist rom out there? Wouldn't mind SOME extra features like task/notification bar customization and things like that. Stability and rock solid performance with great battery life are the concerns. Thank you!

GunnermanBill said:
Hey, was big into the android scene years ago, switched to other platforms for a bit just to play with them. Got a used 64 gig 6p and was thinking about dropping a custom rom onto it, but I don't know what's good anymore. What's the most stable, daily driver, minimalist rom out there? Wouldn't mind SOME extra features like task/notification bar customization and things like that. Stability and rock solid performance with great battery life are the concerns. Thank you!
Click to expand...
Click to collapse
I'm running f2fs file system with ABC oreo build & superUber kernel. I'm on latest radio & bootloader from 8.1. it has been pretty solid. I was on Pure Nexus nougat & Flash kernel; this set-up is tried & true. The Superxe ROM is aroma based and has 8.1 preview although I haven't got to try it yet. Hopefully this might point you in the right direction; there is a f2fs twrp build(s) in the 6p development thread if your interested.

Samuel Holland said:
I'm running f2fs file system with ABC oreo build & superUber kernel. I'm on latest radio & bootloader from 8.1. it has been pretty solid. I was on Pure Nexus nougat & Flash kernel; this set-up is tried & true. The Superxe ROM is aroma based and has 8.1 preview although I haven't got to try it yet. Hopefully this might point you in the right direction; there is a f2fs twrp build(s) in the 6p development thread if your interested.
Click to expand...
Click to collapse
Awesome reply, thank you for the heads up. F2FS is new to me, I'm guessing
https://forum.xda-developers.com/ne...recovery-twrp-2-8-7-0-touch-recovery-t3234976
is the thread you were talking about? I need to get it bootloader unlocked and rooted still, i'll probably tackle it when i get home and drop that version of TWRP onto it. Thanks again!

so it looks like the tools like Wug's are all very outdated, are they safe to use anyway on my device that has all the latest stock stuff? like 8.0 and my version aren't listed in Wug's at all.

GunnermanBill said:
Awesome reply, thank you for the heads up. F2FS is new to me, I'm guessing
https://forum.xda-developers.com/ne...recovery-twrp-2-8-7-0-touch-recovery-t3234976
is the thread you were talking about? I need to get it bootloader unlocked and rooted still, i'll probably tackle it when i get home and drop that version of TWRP onto it. Thanks again!
Click to expand...
Click to collapse
Here's the link to the unofficial twrp for 6p with f2fs support. Don't forget to check the box in twrp "Use rm -rf instead of formatting" after changing data and cache to f2fs. Make sure your rom and kernel support f2fs with kernel being mandatory for best results. Here's the link:
https://forum.xda-developers.com/nexus-6p/development/unofficial-twrp-3-0-3-x-f2fs-support-t3543450
---------- Post added at 12:27 PM ---------- Previous post was at 12:15 PM ----------
GunnermanBill said:
so it looks like the tools like Wug's are all very outdated, are they safe to use anyway on my device that has all the latest stock stuff? like 8.0 and my version aren't listed in Wug's at all.
Click to expand...
Click to collapse
I'm sure that unlocking the phone with the toolkit is safe. It's the method I used. Also in the link above or in the 6p section it should have any info you may need. You can flash recovery by vol dn & power button into bootloader(fastboot), and once you "cd /path tofolder with recovery image/" & "fastboot devices" to make sure you can see your 6p and drivers are installed correctly, you can rename twrp.img to recovery.img & they command is:
fastboot flash recovery recovery.img
I recommend going to xda 6p section; general, & questions, & answers & reading up on everything just to be on the safe side and very important; make backup at all times just to make sure if there is a "booboo" you can easily restore. If you need adb & fastboot installed, there is a thread here on xda "15 sec adb & fastboot installer".
I hope this could help and I hope you enjoy as much as I have.

Latest ROMs which gives me good performance and battery life are paranoid (still nougat, but always a winner), latest 8.1 with pixel 2 mod and aicp rom with kernvatore kernel.

Buying a 6P for good battery life may have been a mistake...

gman88667733 said:
Buying a 6P for good battery life may have been a mistake...
Click to expand...
Click to collapse
Battery life on stock has been as good as my iPhones 6s. Does charge slower though, even when it's rapid.

GunnermanBill said:
Hey, was big into the android scene years ago, switched to other platforms for a bit just to play with them. Got a used 64 gig 6p and was thinking about dropping a custom rom onto it, but I don't know what's good anymore. What's the most stable, daily driver, minimalist rom out there? Wouldn't mind SOME extra features like task/notification bar customization and things like that. Stability and rock solid performance with great battery life are the concerns. Thank you!
Click to expand...
Click to collapse
Clockwork mod is no more, TWRP is the new standard recovery.
Nexus/Pixel line by google gives you the minimalistic ROM you would need,ie. stock ROM :laugh:
Try stock rom for a while. Heck, i got so used to stock , I havent rooted my phone since ages. Atm i have moved on to pixel, and i am perfectly comfortable with stock ROM. I guess custom ROMs only attracted me when i had devices whose software cycle were abandoned by their OEM's.

NoobInToto said:
Clockwork mod is no more, TWRP is the new standard recovery.
Nexus/Pixel line by google gives you the minimalistic ROM you would need,ie. stock ROM :laugh:
Try stock rom for a while. Heck, i got so used to stock , I havent rooted my phone since ages. Atm i have moved on to pixel, and i am perfectly comfortable with stock ROM. I guess custom ROMs only attracted me when i had devices whose software cycle were abandoned by their OEM's.
Click to expand...
Click to collapse
Just now finally rooted etc. My issue with stock was it would crash and reboot sometimes when unlocking it while something was playing over bluetooth. Not going nuts with advanced feature roms, but honestly at this point trust the devs here over the crazies that Google hires these days. Just keeping it safe simple and solid.

You should try the SuperXE Custom ROM on 8.0 with the Pixel 2 features/addons. You should also give PureNexus a try, if you're not so satisfied with Oreo just yet. I'm currently running the Android 8.1 developer preview and I love it, the battery life is great and the ROM is fluid with little bugs.

alright, i thought i had rooted, i guess not. I'm unlocked, i used wug's to root, but it's not sticking. I don't have super user, and i cannot boot into recovery without using ADB. If recovery is selected from the bootloader menu it just brings me to the default android recovery with no options and I have to hold the power button down. I've tried manually flashing the recovery via fastboot and it's the same story. I tried booting into twrp via fastboot and flashing the superuser zip there but it's not in my app drawer. Everything seems to be successful when the operations are running. What gives?

GunnermanBill said:
alright, i thought i had rooted, i guess not. I'm unlocked, i used wug's to root, but it's not sticking. I don't have super user, and i cannot boot into recovery without using ADB. If recovery is selected from the bootloader menu it just brings me to the default android recovery with no options and I have to hold the power button down. I've tried manually flashing the recovery via fastboot and it's the same story. I tried booting into twrp via fastboot and flashing the superuser zip there but it's not in my app drawer. Everything seems to be successful when the operations are running. What gives?
Click to expand...
Click to collapse
the recovery does not stick on stock ROM if you don't flash either supersu or magisk. So you need to put the .zip of either one of those on your phone, then boot to bootloader and fastboot flash the recovery. Next, you boot into the recovery and flash the zip that you put on your phone.
you are now rooted, and your recovery will stick.
I'm currently on stock 8.0 waiting for paranoid android 8.0 update

knevelsg-j said:
the recovery does not stick on stock ROM if you don't flash either supersu or magisk. So you need to put the .zip of either one of those on your phone, then boot to bootloader and fastboot flash the recovery. Next, you boot into the recovery and flash the zip that you put on your phone.
you are now rooted, and your recovery will stick.
I'm currently on stock 8.0 waiting for paranoid android 8.0 update
Click to expand...
Click to collapse
I had flashed the super user zip in the wug kit myself while in TWRP but it still didn't stick. I mentioned that previously but i said a lot of other stuff too i'm not suprised you missed it. I guess I'm probably flashing the wrong SU and will look for another.
edit - grabbed the latest stable super user and it seems good now

What's this vendor image that's a thing now? You have to be tethered to a PC to flash most roms due to it nowadays it seems. Radios used to come in zips i could flash in twrp as well, what happened to that?

Lineage does not work

It's been 5 days since i installed lineage in my Oneplus One.
Yesterday it started to randomly shut down or reboot, now it hardly boots.
Procedure followed:
Original cyannogenmod --> oxygen os --> lineage os
Formated all partitions befre installing lineage OS
Any idea?, it rushes!

garfius said:
It's been 5 days since i installed lineage in my Oneplus One.
Yesterday it started to randomly shut down or reboot, now it hardly boots.
Procedure followed:
Original cyannogenmod --> oxygen os --> lineage os
Formated all partitions befre installing lineage OS
Any idea?, it rushes!
Click to expand...
Click to collapse
I doubt LOS is the root cause. Did you somehow restore apps? Did you install something new yesterday? Did you change settings of installed apps?

i think not..?
kurtn said:
I doubt LOS is the root cause. Did you somehow restore apps? Did you install something new yesterday? Did you change settings of installed apps?
Click to expand...
Click to collapse
Let's recap.:
1-original CyannogenMod
1.1 -- Screen+battery is replaced
2-install Oxygen OS
2.1 -- flash firmware (antennas+something+recovery)
2.2 -- flash oxygenOS
3 - Install latest twrp for oneplus: https://eu.dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
3.1 -- erase system,cache and dalvik cache
3-2 -- flash https://mirrorbits.lineageos.org/full/bacon/20180425/lineage-14.1-20180425-nightly-bacon-signed.zip
3 days perfect
yestarday found powered off (1st time ever!)
today rebooted about 4 times
Any idea?

garfius said:
Let's recap.:
1-original CyannogenMod
1.1 -- Screen+battery is replaced
2-install Oxygen OS
2.1 -- flash firmware (antennas+something+recovery)
2.2 -- flash oxygenOS
3 - Install latest twrp for oneplus: https://eu.dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
3.1 -- erase system,cache and dalvik cache
3-2 -- flash https://mirrorbits.lineageos.org/full/bacon/20180425/lineage-14.1-20180425-nightly-bacon-signed.zip
3 days perfect
yestarday found powered off (1st time ever!)
today rebooted about 4 times
Any idea?
Click to expand...
Click to collapse
Delete data for clean install.

garfius said:
It's been 5 days since i installed lineage in my Oneplus One...
Click to expand...
Click to collapse
I don't have this device but, if the support/guidance here, for any reason, doesn't work out here then you can always post your question within the following Official LineageOS thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3543489
If needed, and you don't receive any responses from the above thread, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2731638
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Can't save update script for lineage version 14.1
I recently have tried to flash lineage version 14.1. however i get an error that says cant flash because incorrect device. I have tried to edit the update script to remove the line of code that triggers that. after i edit saving it doesnt work and i cant flash lineage. Any suggestions?

asadc said:
I recently have tried to flash lineage version 14.1. however i get an error that says cant flash because incorrect device. I have tried to edit the update script to remove the line of code that triggers that. after i edit saving it doesnt work and i cant flash lineage. Any suggestions?
Click to expand...
Click to collapse
What twrp?

Probably found it!
It seems to be a problem with the wifi firmware, seems to be pretty common :crying: :crying:
Anyways, thank you for your time.
Regards.
Ibuprophen said:
I don't have this device but, if the support/guidance here, for any reason, doesn't work out here then you can always post your question within the following Official LineageOS thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3543489
If needed, and you don't receive any responses from the above thread, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2731638
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse

Try latest
I used lineage tuto, and flashed the latest TWRP and worked like a charm (wifi issue apart).
asadc said:
I recently have tried to flash lineage version 14.1. however i get an error that says cant flash because incorrect device. I have tried to edit the update script to remove the line of code that triggers that. after i edit saving it doesnt work and i cant flash lineage. Any suggestions?
Click to expand...
Click to collapse

Vendor, Bootstack and Kernel questions for running AEX V6 GSI

Hey guys!
Just a couple of quick regarding the right vendor, bootstack and custom kernels I can use for my Axon 7
Im running...
AOSP Extended V6 GSI
Lineage 15.1 vendor
B20_Bootstack_by_Verequies.zip
I wonder if anyone can point me to the best bootstack and vendor for running AEX V6 GSI. Ive used the universal bootstack provided by Draken from here https://androidfilehost.com/?w=files&flid=270519. Which one of these would run the best if you know? Also with the bootstack I want to retain all of my button combination options (recovery and EDL) and offline charging but I can do without the warning screen.... ok I REALLY want to get rid of the warning screen.
Also I found this page https://github.com/AospExtended/platform_vendor_aosp that claims to have a AOSP vendor platform and I wanted to know if this would work.
My device was Treble checked and is Treble enabled so Im guessing I dont have to flash an EDL package with MiFlash anymore and just flash the partitions. (Confirm).
The only kernel I have is whatever came with the AEX ROM. I havent flashed anything custom yet other than the files I used for the initial install. Reason Im asking about a kernel is because Ive noticed the battery life isnt that great so Im looking for one that can give me more in that area first and foremost. Any other perks come secondary.
Thanks in advance and XDA has saved me and my phone tinkering more times than I can count. I appreciate all of your hard work! :highfive:

juniorD said:
Hey guys!
Just a couple of quick regarding the right vendor, bootstack and custom kernels I can use for my Axon 7
Im running...
AOSP Extended V6 GSI
Lineage 15.1 vendor
B20_Bootstack_by_Verequies.zip
I wonder if anyone can point me to the best bootstack and vendor for running AEX V6 GSI. Ive used the universal bootstack provided by Draken from here https://androidfilehost.com/?w=files&flid=270519. Which one of these would run the best if you know? Also with the bootstack I want to retain all of my button combination options (recovery and EDL) and offline charging but I can do without the warning screen.... ok I REALLY want to get rid of the warning screen.
Also I found this page https://github.com/AospExtended/platform_vendor_aosp that claims to have a AOSP vendor platform and I wanted to know if this would work.
My device was Treble checked and is Treble enabled so Im guessing I dont have to flash an EDL package with MiFlash anymore and just flash the partitions. (Confirm).
The only kernel I have is whatever came with the AEX ROM. I havent flashed anything custom yet other than the files I used for the initial install. Reason Im asking about a kernel is because Ive noticed the battery life isnt that great so Im looking for one that can give me more in that area first and foremost. Any other perks come secondary.
Thanks in advance and XDA has saved me and my phone tinkering more times than I can count. I appreciate all of your hard work! :highfive:
Click to expand...
Click to collapse
how would your phone not be 'treble-enabled' if you are using a GSI? Food for thoughts
Also, which bootstack are you running? Draken's or Verequies's? If Ver's, download the NO-SPLASH bootstack. That one's going to do what you want.
When I installed it for some reason it blackscreened my phone, the solution is just to get Oki's B12 EDL bootstack from his androidfilehost profile and flash it via edl (if you get dfu, use MultiDL).
Use the stock kernel or try Schwifty kernel, maybe Crimson too. Just test yourself

Choose an username... said:
how would your phone not be 'treble-enabled' if you are using a GSI? Food for thoughts
Also, which bootstack are you running? Draken's or Verequies's? If Ver's, download the NO-SPLASH bootstack. That one's going to do what you want.
When I installed it for some reason it blackscreened my phone, the solution is just to get Oki's B12 EDL bootstack from his androidfilehost profile and flash it via edl (if you get dfu, use MultiDL).
Use the stock kernel or try Schwifty kernel, maybe Crimson too. Just test yourself
Click to expand...
Click to collapse
As I said in the initial post Im using the Verequies boot which is the No Splash which I dont mind but i want to get rid of the warning screen. Also if this is the one with the gold boot screen I am definitely gonna have to change that as it is ugly. LOLOL!
Im asking about who's tested what especially with kernels so I dont brick my phone as Ive already done this twice so I know what Ive used and will not use again.
But as I said I also found an AEX specific vendor or one labeled as one. I put the link in my OP so before I test it Im asking if anyone knows about it before I wipe my phone for no reason.
Im definitely going to try those kernels cuz like I said the battery life on the stock for the AEX V6 GSI isnt that great. LOS 16 was better but for some reason Lineage OS kept causing my phone to freeze and randomly reboot. I was using it for 3 days and it rebooted prolly 5-6 times running normally. So I dont think Im going back to LOS and will prolly stick to Havoc, Arrow or AEX for now.

juniorD said:
As I said in the initial post Im using the Verequies boot which is the No Splash which I dont mind but i want to get rid of the warning screen. Also if this is the one with the gold boot screen I am definitely gonna have to change that as it is ugly. LOLOL!
Im asking about who's tested what especially with kernels so I dont brick my phone as Ive already done this twice so I know what Ive used and will not use again.
But as I said I also found an AEX specific vendor or one labeled as one. I put the link in my OP so before I test it Im asking if anyone knows about it before I wipe my phone for no reason.
Im definitely going to try those kernels cuz like I said the battery life on the stock for the AEX V6 GSI isnt that great. LOS 16 was better but for some reason Lineage OS kept causing my phone to freeze and randomly reboot. I was using it for 3 days and it rebooted prolly 5-6 times running normally. So I dont think Im going back to LOS and will prolly stick to Havoc, Arrow or AEX for now.
Click to expand...
Click to collapse
verequies's splash hasn't got the 5 sec screen, but it has a weird 3 logo splash. I'm using Oki's B12 bootstack (the gold splash one, really ugly lol) but I made my own splash to replace it. it has no 5 sec screen. Oki's is based on B12 though.

Choose an username... said:
verequies's splash hasn't got the 5 sec screen, but it has a weird 3 logo splash. I'm using Oki's B12 bootstack (the gold splash one, really ugly lol) but I made my own splash to replace it. it has no 5 sec screen. Oki's is based on B12 though.
Click to expand...
Click to collapse
Yeah the Splash version takes away the offline charging and the EDL button combo which I want to keep. I just wanna get rid of the Warning screen I guess and keep all the other functionality and Im good!

How To Guide Convert Verizon UW OnePlus 8 To Global

Hello everyone! I have managed to get Global firmware on VZW UW OnePlus 8 and thought I would share.
Donations are appreciated. PayPal user @igp1490
You will need to download to get started.
1. FastbootEnhance: https://github.com/libxzr/FastbootEnhance/releases
2. Jaguar Rom Full: https://drive.google.com/file/d/1RIIZzz0IyVXeFdjjKRjgqdSphLxaE--w/view
3. Recovery: https://androidfilehost.com/?fid=15664248565197198941
4. PayloadDumper GUI. Download version 2.3: https://forum.xda-developers.com/t/...and-other-img-files-from-payload-bin.4442149/
5. Global OTA Firmware 11.0.11.11.IN21AA: https://www.thecustomdroid.com/download-oneplus-8-pro-oxygenos-ota-updates/
6. OnePlus 8 Visible OTA firmware: https://oxygenos.oneplus.net/OnePlu..._OTA_0080_all_2203082133_56fdf9c8718742cb.zip
7. Platform-tools, I'm using 33.0.3: https://www.techspot.com/downloads/downloadnow/5425/?evp=de0a68064118855fcddcc3980a2143c4&file=6062
Now to get started. First have bootloader unlocked of course.
1. Extract payload.bin from Visible OTA, then dump payload.bin with payload dumper. next find modem.img and move to desktop
2. Install Recovery
3.Be on A11 rom with A11 custom recovery or Install Jaguar Rom and go through setup.
Thanks to Bishop1312! for pointing out any A11 rom with A11 custom recovery works in step 3.
4. When Jaguar is setup reboot to fastboot
5. Run FastbootEnhance, double click your device that says fastboot
6. When in fastbootenhance click fastbootd then click little box to the left of "ignore unknown partitions" then select flash payload.bin and select global firmware zip. When flash is complete "select activate slot" my second slot to flash was slot B, you want to flash global to both slots.
7. After it installs click back in in Jaguar recovery and select "Factory reset", I did f2fs and regular format options
8. Afterformat is done reboot system
9. It may take a few minuets to get into the setup and you may get a message saying phone app has stopped working, don't worry just go through the setup process and connect to wifi.
10. when phone is setup turn off phone and boot into fastboot holding power+Vol down, when in fastboot connect to computer and run FastbootEnhancer. You should see your fastboot device, double click on fastboot, now in fastbootenhancer click reboot to Fastbootd. when in fastbootd go to Partitions tab in fastbootenhancer and look for Modem_b, click on modem_b to highlight it, then click erase then click flash and look for modem.img you put in desktop and select it to flash and after look for modem_a and follow same steps then reboot phone to system.
11. When phone is booted go to system updates and update. After update is finished reboot, after reboot follow steps 10 again for modem, continue step 10 until fully updated to Android 13. Verizon service will work in Android 13 but not 11 or 12.
One problem I have is if I turn on then off airplane mode it wont reconnect to Verizon service, you have to reboot phone and it will work again. I'm thinking maybe because it's an older modem.img, so if anyone can get there hands on the newer modem from Verizon or Visible newest OTA maybe that will fix the issue but no sure. This is my first guide so If anyone has problems let me know and i'll do my best to help you.
Hope ya'll enjoy.
Edit: I got EvolutionX A13 rom working! also airplane mode is working in EvolutionX A13 rom. You have to do step 10 every time after setting up new A13 roms. I Tried step 10 before going through setup but it just goes to bootloader, So make sure to complete rom setup before step 10.

Good work, man!!! This method fully work! I have some little notations:
In step 3, it can be any rom, based on Android 11, but recovery must be from custom A11 rom;
After another installing or updating rom, we must do step 10 every time, for working cellular data. But i think, it's small price for getting fully working custom A13 roms.
UPD. On every reboot, cellular data appears after ~1 min, so don't worry))

Bishop1312 said:
Good work, man!!! This method fully work! I have some little notations:
In step 3, it can be any rom, based on Android 11, but recovery must be from custom A11 rom;
After another installing or updating rom, we must do step 10 every time, for working cellular data. But i think, it's small price for getting fully working custom A13 roms.
Click to expand...
Click to collapse
Thank you. I'll edit step 3.

Bishop1312 said:
Good work, man!!! This method fully work! I have some little notations:
In step 3, it can be any rom, based on Android 11, but recovery must be from custom A11 rom;
After another installing or updating rom, we must do step 10 every time, for working cellular data. But i think, it's small price for getting fully working custom A13 roms.
UPD. On every reboot, cellular data appears after ~1 min, so don't worry))
Click to expand...
Click to collapse
Have you tried watching a video on youtube or any movie/video app? I'm having video playback freeze for a few seconds then video plays for another few seconds then freezes and continues this cycle. I'm wondering if it's just EvolutionX.

Incognit420 said:
Have you tried watching a video on youtube or any movie/video app? I'm having video playback freeze for a few seconds then video plays for another few seconds then freezes and continues this cycle. I'm wondering if it's just EvolutionX.
Click to expand...
Click to collapse
No, video playback i don't test for now. I tried to flash two roms and i apologize for unchecked words - after first flashing modem.img at the beginning, in the future no needs to flash modem, cellular data work fine.

Great work @Incognit420. A video guide will also be helpful for noob like me.

Zombify01 said:
Great work @Incognit420. A video guide will also be helpful for noob like me.
Click to expand...
Click to collapse
Even though reading is fundamental - a how-to video would take it over the top.

Does anyone know if OOS13 is working with this method? Don't you need the OOS12/ 13 firmware in order to be able to use the latest custom ROMs?

Xryphon said:
Does anyone know if OOS13 is working with this method? Don't you need the OOS12/ 13 firmware in order to be able to use the latest custom ROMs?
Click to expand...
Click to collapse
Yes OOS13 works. This method flashes OOS11 global firmware then you update to OOS12 in setting and then update to OOS13 in settings. Make sure to flash modem.img in fastbootd after each update. OOS13 works. Data and calling are not working in OOS12 global, don't know why but does work in OOS13. the only problem I have is OOS13 is if you turn off wifi it won't turn back on but data, calling and text work. I'm on a custom OOS13 rom and it fixed wifi.

Zombify01 said:
Great work @Incognit420. A video guide will also be helpful for noob like me.
Click to expand...
Click to collapse
I'm horrible at making videos lol but I'll give it a try.

hi, after step 7, i chose to back recovery , but show default recovery, and i go next step wipe data and reboot goot qualcom crush dump. any idea?

faritz1903 said:
hi, after step 7, i chose to back recovery , but show default recovery, and i go next step wipe data and reboot goot qualcom crush dump. any idea?
Click to expand...
Click to collapse
What rom were you on before flashing global firmware?

Incognit420 said:
What rom were you on before flashing global firmware?
Click to expand...
Click to collapse
oos 11, then install jaguar rom

after more try, it success. but in after upgrade to OOS 13 my wifi dont work, but cell is work, any idea?

faritz1903 said:
after more try, it success. but in after upgrade to OOS 13 my wifi dont work, but cell is work, any idea?
Click to expand...
Click to collapse
Glad to hear you got it working. Yeah I just realized that yesterday that wifi doesn't work. Install a custom a13 rom and you will get wifi back. I recommend starting with crdroid a13. I was using evolutionx but screen was flashing a little bit when typing so I installed crdroid and it is working perfectly. We need an actual developer to figure out the wifi issue in stock oos13. I'm not by any means a developer. I just messed around with firmware for months to figure out how to get a13 on our vzw devices since verizon is garbage for updates.I personally like the stock oos a13, so it would be nice to have wifi. I think the opeque look in the pixel roms is ugly, Google should have implemented blur in QS and notifications.

Incognit420 said:
Glad to hear you got it working. Yeah I just realized that yesterday that wifi doesn't work. Install a custom a13 rom and you will get wifi back. I recommend starting with crdroid a13. I was using evolutionx but screen was flashing a little bit when typing so I installed crdroid and it is working perfectly. We need an actual developer to figure out the wifi issue in stock oos13. I'm not by any means a developer. I just messed around with firmware for months to figure out how to get a13 on our vzw devices since verizon is garbage for updates.I personally like the stock oos a13, so it would be nice to have wifi. I think the opeque look in the pixel roms is ugly, Google should have implemented blur in QS and notifications.
Click to expand...
Click to collapse
i will try but link recovery and vbmeta is not found, can u share it?
can you try isntall Coloros 13?

faritz1903 said:
i will try but link recovery and vbmeta is not found, can u share it?
can you try isntall Coloros 13?
Click to expand...
Click to collapse
Install EvolutionX 13 and then install Crdroid 9.0. or you can try just using EvolutionX vbmeta and recovery to install Crdroid, both roms use the same method.

Incognit420 said:
Glad to hear you got it working. Yeah I just realized that yesterday that wifi doesn't work. Install a custom a13 rom and you will get wifi back. I recommend starting with crdroid a13. I was using evolutionx but screen was flashing a little bit when typing so I installed crdroid and it is working perfectly. We need an actual developer to figure out the wifi issue in stock oos13. I'm not by any means a developer. I just messed around with firmware for months to figure out how to get a13 on our vzw devices since verizon is garbage for updates.I personally like the stock oos a13, so it would be nice to have wifi. I think the opeque look in the pixel roms is ugly, Google should have implemented blur in QS and notifications.
Click to expand...
Click to collapse
The reason why the various issues on the ROMs exist is because the OOS12/ OOS 13 firmware has not been released by Verizon officially, and there are fundamental changes in the firmware such as the modem (since the Verizon model has the mmWave functionality). This leads to various networking issues such as Wi - Fi not working, cell data not working sometimes, etc. IN2019/ Verizon OnePlus 8 users will never get a stable OOS12/ OOS13 build unless Verizon decides to release the firmware for it - the custom ROMs are the same way since they rely in the OOS12/ OOS13 firmware in order to function properly.

Before I attempt this, is there an easy way to return to stock? Does flashing to stock with MSM undo these changes?

The0919 said:
Before I attempt this, is there an easy way to return to stock? Does flashing to stock with MSM undo these changes?
Click to expand...
Click to collapse
Yes, MSM will bring you back to vzw firmware.