Related
FEATURED ON THE PORTAL
Thanks @Doug Lynch for the mention!
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
TWRP 3.0.2-0 for LAVA Pixelv1, Tool/Utility for the OEM Cross Device Development
Contributors
MSF Jarvis, varun.chitre15
Version Information
Status: Stable
Created 2016-04-06
Last Updated 2016-04-20
Reserved
Credits
varun.chitre15 for his base trees
@DHARMESH17 for being a great tester
@arvinquilao for making me jealous!
Reserved
I would like you to recognize some misunderstanding.
On the official website of TWRP are 2 different Android One devices listed.
The first is "sprout" which stand for MTK powered devices
The other entry is called "2nd generation MTK (seedmtk)" which is simply wrong and might mislead some people. 2nd gen devices are powered by Snapdragon 410 CPUs.
You may want to change the listing on your website for a better understanding.
body150165 said:
I would like you to recognize some misunderstanding.
On the official website of TWRP are 2 different Android One devices listed.
The first is "sprout" which stand for MTK powered devices
The other entry is called "2nd generation MTK (seedmtk)" which is simply wrong and might mislead some people. 2nd gen devices are powered by Snapdragon 410 CPUs.
You may want to change the listing on your website for a better understanding.
Click to expand...
Click to collapse
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
@body150165 thanks for bringing up your concern. Official TWRP build for the Snapdragon variant is already available via dl.twrp.me/seed, but the website is yet to be updated (probably in the next couple of days). As soon as it's updated I'll make a new thread here for the Snapdragon variant.
Second Partitiin (SD partition) working??
Sent from my SM-J500F using XDA-Developers mobile app
Nur_Alom said:
Second Partitiin (SD partition) working??
Sent from my SM-J500F using XDA-Developers mobile app
Click to expand...
Click to collapse
Who needs it?
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
cuvetto said:
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
Click to expand...
Click to collapse
I'll get back to you in a while after checking these. And this is TWRP 3.0.2-0, not 3.0.0-2.
I would like to know what steps have you taken to port it to determine whether I can source build for the device and make it official.
cuvetto said:
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
Click to expand...
Click to collapse
@cuvetto : No, these bugs don't exist in my build. Tested as working fine by @DHARMESH17.
Will these work on 1st generation android one device i mean sprout 4 ?
DarkHeart Z said:
Will these work on 1st generation android one device i mean sprout 4 ?
Click to expand...
Click to collapse
It will not, sadly. TWRP seems to have not updated sprout devices for ages, so I'll run you guys a 3.0.2-0 build in some time and post it here.
MSF Jarvis said:
It will not, sadly. TWRP seems to have not updated sprout devices for ages, so I'll run you guys a 3.0.2-0 build in some time and post it here.
Click to expand...
Click to collapse
Then I am waiting for that
Bootloop
My device is lava pixel v1. After flashing this recovery from fastboot my device goes into bootloop. It always start with recovery and then says failed to mount /data etc and again reboots.
ashokvishnoi1994 said:
My device is lava pixel v1. After flashing this recovery from fastboot my device goes into bootloop. It always start with recovery and then says failed to mount /data etc and again reboots.
Click to expand...
Click to collapse
After fastboot flash recovery twrp-3.0.2-0-seedmtk.img, what exactly did you do?
You need to press both Volume Up + Power for about 15 seconds till device reboots back into bootloader mode and then go to recovery mode and open it. This has been tested as working. What steps did you take?
MSF Jarvis said:
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
Click to expand...
Click to collapse
It should be Infinix Hot 2. Also I tried flashing via flashify and the recovery does not boot on Hot 2.
anarchtic said:
It should be Infinix Hot 2. Also I tried flashing via flashify and the recovery does not boot on Hot 2.
Click to expand...
Click to collapse
That's bad.... Can you provide me with your boot image? I will have to end up deunifying this recovery if it isn't booting :/
I would recommend that you also try a fastboot flash to see if it's a flashify thing.
MSF Jarvis said:
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
Click to expand...
Click to collapse
MSF Jarvis said:
That's bad.... Can you provide me with your boot image? I will have to end up deunifying this recovery if it isn't booting :/
I would recommend that you also try a fastboot flash to see if it's a flashify thing.
Click to expand...
Click to collapse
I will when I get home, I am at work now which is why I used Flashify. Did you test using Hot 2?
anarchtic said:
I will when I get home, I am at work now which is why I used Flashify. Did you test using Hot 2?
Click to expand...
Click to collapse
Don't own one. I believed it would boot, just like it does for Android One first gen devices(One recovery for all devices)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Jump to...
ROM Index (#2) | Kernel Index (#3) | Changelog (#4)
Whaddup, XDA? ^_^
This began as a modest little post, aptly named Post#3333 in the Resurrection Remix thread to help keeping the thread clean. Many thanks to @varund7726 for his support and making it the official RR Bacon FAQ!
It gained more attention than I thought it would so I decided to make a more general version in a dedicated thread.
This is not my work but a collection of answers by amazing people that roam these digital lands. Of course, I do appreciate you clicking that Thank you button . I hope people looking for answers will find their way here. If someone has any input, feel free to drop it in the thread or send me a PM and I'll update the post if needed. It may be best to not ask new questions here, you'll find more satisfying answers in the appropriate threads of the custom ROM you're using or in the general Help thread.
Now, let's get this out of the way first:
Code:
What are you reading this for? There isn't a single Bacon owner with valid warranty anymore. Anyway, here's the original disclaimer:
You have the [U]right[/U] to unlock your device, not the [U]obligation[/U] to do so.
Anything you flash can and will be used against you in a court of technical dispute.
If you get your device bricked, you will [B]not[/B] be provided with a new one.
If your mother in law disappears as a result of something mentioned in this thread,
I will happily take your donations to thank me but I will not be held responsible!
Mind that this is – and probably will continue to be – a work in progress.
This is an attempt to collect general solutions, which will not always work in every case.
Please DO NOT QUOTE THIS ENTIRE POST! Thanks.
▂▃▅▇█▓▒░INDEX░▒▓█▇▅▃▂
New items are indicated with
; Updated items are indicated with
GENERAL
How can this FAQ help me? Why did you make this?
Why isn’t anyone helping me?
Creating a logcat
PREPARING
EXT4 vs. F2FS
What else do I need? (Prerequisites)
C6 or C7, which is the best firmware? (troubleshooting network issues)
What kernel should I use?
FLASHING
Installing TWRP
How to flash (with links!)
I'm seeing two red errors in TWRP while flashing
I'm getting an error while flashing Gapps
I dirty flashed and something doesn't work anymore
CRITICAL
My screen is going black, I can only see notifications
My device just exploded!
The other person (nearly) can't hear me during a call
I have another audio/microphone problem
Can't read or write to internal storage (/sdcard)
QUICK FIXES
The camera app can't connect to the camera
Google Assistant isn't working or "OK Google" detection fails
QS toggle 'drops' when trying to add it
OTHER
How do I apply themes and which ones can I use?
Fast/Quick Charge isn't working
MODS
ViPER4Android
Camera mods
1. GENERAL
1.a. How can this FAQ help me? Why did you make this?
My goal is to maintain a one-size-fits-all thread where people can find answers to the most common current problems for the OnePlus One a.k.a. Bacon. It also serves as a detailed guide through the flashing process. The reason I'm doing this is threefold: 1) Despite the fact that this is a 2014 device, the 1+1 community is still booming. Best proof of that is that our very own Bacon is by far the most popular device for LineageOS with currently over 80,000 installs! I'd love to honor that fact. 2) This is my first support thread, I hope to learn a great deal from it. 3) I honestly enjoy helping people =)
1.b. Why isn’t anyone helping me?
Keep in mind that XDA is not your personal tech support. The idea is that we help each other as a community, not to expect an immediate answer to your problem. If you do not add any useful technical information to your query, your post may not be considered, this is even more so the case in development threads.
There are three ways (that can be combined) to achieve a technically sound post:
Attach a logcat! See 1.c. on how to do this.
Provide screenshots, especially handy with aesthetic issues.
Provide the exact steps to reproduce the problem (be VERY specific).
Tip: use the time that you’re waiting for an answer to find it yourself. If you managed to resolve it yourself, follow-up on your own post and explain how you did it, it may be helpful to other users in the future.
1.c. Creating a logcat
This'll only take a minute and may provide invaluable information for any developer or someone trying to help. There are a number of ways to create them, this tutorial explains a remote technique. I do believe this is the easiest way:
Download CatLog from the Play Store
Make sure you have a dedicated 'menu' button (CatLog is old skool)
Run the app, give it root rights, [optional] pause the current flow with the pause button and then clear the window tapping the circle with the X in the middle top right (this will provide peace of mind, the constant stream can be a bit overwhelming)
Tap the menu button, press Record followed by OK. Any activity is now being recorded
Press your home key and launch the app that's giving you trouble, let the crash happen and repeat it a few times
Drag down notifications and tap the cat, it'll state "select to stop recording"
CatLog will now show you what it has recorded, use the search feature to check if no privacy sensitive information (your e-mail, a phone number etc.) has been collected, you can edit this out manually with a text editor if needed
You can simply tap the menu key again and select Send to share the log, this feature will also add device info (brand, model, Android version ...)
If you'd like to share it manually or want to make some edits first, you'll find the file in [internal storage]/catlog/saved_logs
2. PREPARING
2.a. EXT4 vs. F2FS
A lot can be said about filesystems but I won't go into any technical debates on here. The main difference boils down to this:
F2FS is arguably faster than EXT4; EXT4 is arguably more stable than F2FS.
In real use performance, not much difference will be noticed in terms of speed. Since the release of Oreo for Bacon, however, stability on F2FS has decreased drastically or it is unsupported entirely. If you have never changed this yourself, the system will most likely be formatted to EXT4. You can check with DiskInfo or in recovery. In case you want to run Nougat on F2FS or you want to return to EXT4 but forgot how, here's a refresher:
In recovery, go to Wipe > Advanced Wipe
Select a single partition
Tap “Repair or Change File System” (if you see “Invalid partition selection” appearing, it means the partition’s file system cannot be changed
On top you can see the current file system, tap “Change File System” followed by the one you want (stick to either EXT4 or F2FS)
Swipe to confirm
I found this XDA article (interview with Francisco Franco) quite interesting on this topic.
2.b. What else do I need? (Prerequisites)
A good working TWRP
The ROM zip of your choosing
Gapps (ARM/8.1/nano, there are plenty alternatives, check with your ROM maker which one is advised)
last CM13 snapshot (only if you didn't have CM13 before)
You should place all downloaded files in the root of your internal storage (/sdcard). It's stongly recommended to check md5 hashes! In case of Gapps, download the md5 checksum file and place it together with the zip.
2.c. C6 or C7, which is the best firmware? (troubleshooting network issues)
None. There are mixed results on both, depending on which network(s) you use. Which one works best for you? The only way to find out is by flashing one of the three versions below (that differs from your current version, check under About phone > Baseband version. The recommended one for most users is C6-00241 (the most likely one you currently have).
Here are three very common firmwares and a Frankenstein release:
Download DI.3.0.c6-00241
Download 4.0.1.c7-00013 (2016)
Download 4.0.1.c7-00011 (2016)
@MrSHME's Frankenstein Release
[instructions and credits]
There's a whole load of them available in this thread. I've done some elaborated testing there, read my findings here.
Important note when flashing firmware: backup your modem and EFS partitions first! It may happen that the system hangs in boot animation after a firmware flash (I experienced this a few times). Give it some time and it should automatically boot back to recovery. In recovery, reboot back to system (don't do any wiping or anything) and it should boot just fine. If the system keeps hanging for over 20 minutes, manually force a shutdown (long press power) and try booting regularly again. Still no luck? Boot to recovery and flash other firmware or restore your modem backup.
2.d. What kernel should I use?
You don't have to use any. Want to take the plunge anyway? Sure, check out post #3 for a list. You can make a backup of your kernel/blobs with Flashify
Read (much much) more about tweaking in this excellent guide by @Saber
3. FLASHING
Always make a nandroid backup before you flash anything!
3.a. Installing TWRP
Before flashing anything, make sure you are using a compatible TWRP! You'll find a download link to the one I'm using in this FAQ, I'll keep it updated. I know this is basic information but to avoid any mistakes, I'm providing all needed steps:
Download a TWRP .img file
Move it to the adb (official download) folder where adb and fastboot exe's are located
[this is no requirement but let's do this for the clarity of these steps] rename it to recovery.img
Reboot device into fastboot via advanced reboot menu, 'adb reboot bootloader' command or – if the device is off – press and hold "Power + Volume UP" until "Fastboot Mode" appears
Setup the correct drivers and connect the device to the PC/Mac
Open a command line (terminal on Mac I guess) in the adb folder
type "fastboot devices" to see if the system picks up the device
type "fastboot flash recovery recovery.img" to flash TWRP
Disconnect the device from the PC
Press and hold power until the device turns off
Hold "Power + Volume DOWN" to boot into the newly flashed TWRP recovery
3.b. How to flash
Always make a nandroid backup before you flash anything!
Clean Flash:
In TWRP, wipe by swiping factory settings. If you're experiencing issues, it's best to do a full wipe (Advanced > select System + Data + Cache + Dalvik-ART Cache)
[optional] Flash last CM13 snapshot and do another full wipe. This step is crucial when you've never been on CM13 before. This flash will fix/prevent a wide variety of issues! You only need to do this once.
Flash the ROM zip
[optional] Flash a custom kernel
Flash Gapps (ARM/nano, version should be the same as ROM), check Gapps compatibility in ROM thread.
[optional] If root is desired, flash Magisk (stable or beta)
[optional] Flash other mods
Wipe Cache/Dalvik-ART Cache and reboot
Dirty Flash (update):
Reboot to TWRP
Flash the ROM zip
Wipe Cache/Dalvik-ART Cache and reboot
Semi-Dirty Flash:
This is basically the clean flash procedure but you backup the /data partition before wiping and restore it afterwards (or don't wipe /data at all). I do not recommend this method.
Example (my flashing procedure for a specific Oreo ROM):
Download ROM and Open Gapps to root. Check ROM md5 hash with MiXplorer
Backup all user apps + a few system elements (messages, call logs etc.) with TitaniumBackup (+pro key)
Copy the TitaniumBackup folder to my PC
Reboot to latest TWRP, create Nandroid backup of System and Data (sometimes copy that one to PC as well)
Wipe /system + /data + /cache + /art-dalvik cache
Flash ROM + Gapps + OP5 camera mod + iYTBP + Magisk beta (all in one go), wipe caches after flashing and reboot
I let Google setup install all apps, then restore app data with TiBu, this feels more clean
Restore system elements with TiBu + apply AdAway lists + restore Android ID (for my banking app) and reboot
Enjoy awesomeness!
This seems like a lot of work but it doesn't take more than an hour. Since releases are currently pretty far apart, it's only a small effort for many days of smooth sailing. If release frequency would increase, I wouldn't make a Nandroid and wouldn't copy everything to PC every single time. If I don't have Wi-Fi for some reason, I restore all apps + data with TiBu instead of using Google setup.
3.c. I'm seeing two red errors in TWRP while flashing
They are LOS related and have no effect on the flash procedure, don't worry about it, you can safely ignore them.
3.d. I'm getting an error while flashing Gapps
Error 70: You're trying to flash a package that is too large such as Stock. Try a smaller package.
Error 64: Wrong architecture, you need an ARM package, not ARM64/x86/x86_64.
Error 20: Wrong version, you need 6.x for Marshmallow, 7.x for Nougat
3.d. I dirty flashed and something doesn't work anymore
Please do not inquire about issues after (semi-)dirty flashing. The first step for you to take is to perform a clean flash. If the issue is still present and it hasn't been posted before (PLEASE use search!), then post your inquiry in the ROM thread.
4. CRITICAL
4.a. My screen is going black, I can only see notifications
This behavior is caused when a profile has lock screen disabled. The only way to recover from this condition is to clean flash, or restore a backup that was made prior to setting up the profile. It may be possible to reboot successfully if one is in a location or situation that triggers a profile that doesn't have lock screen disabled, then change the problem profile settings (unconfirmed).
4.b. My device just exploded!
It's most likely unrelated to a software problem but please, feel free to share pictures!
4.c. The other person (nearly) can't hear me during a call
Can't be heard
In /system/build.prop, change
ro.qc.sdk.audio.fluencetype=fluence
to
ro.qc.sdk.audio.fluencetype=none
Edit /system/etc/audio_platform_info.xml (in Oreo this file moved to /system/vendor/etc)
<device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="40" />
to
<device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="4" />
Audio comes out low
remove
ro.qc.sdk.audio.fluencetype=fluence
change
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=false
(flashable version)
Reboot.
Still having problems? Test your sensors and mic more thoroughly with an app like this, there may be a hardware failure. Before opening her up, you can do a last software check by trying another ROM or by returning to 100% stock.
4.d. I have another audio/microphone problem
Please refer to the OnePlus One Audio Mods Collection, a genious collection of all sorts of fixes and workarounds to achieve fully featured audio on the OPO.
4.e. Can't read or write to internal storage (/sdcard)
Your /sdcard partition is most likely corrupt! Now what? When this happens to /system or /data we can simply perform a clean flash. Wiping our internal storage, however, means wiping a lot of precious data that is not included in a Nandroid backup so it's crucial to make regular backups manually. A lot of trouble can be avoided with cloud syncing (Dropbox, Google Photos, etc.). When read/write errors present themselves (camera can't save photos, not enough space errors while there's plenty, folders disappear, etc.) it's important to work fast before all your data becomes unavailable indefinitely. Here's how you can reset your internal storage in a non-destructive manner:
Copy the entire content of your internal storage (/sdcard) to an external location (PC or OTG drive). Make sure the real important things are immortalized (e.g. your cat photos/videos are synced with Google Photos and/or are trending on YouTube)!
Reboot to TWRP
You may want to create a nandroid backup at this point but do not forget to copy the backup to your PC or make the backup via OTG as we're about to wipe the internal storage (and with it, all internal backups)
Go to Wipe > Advanced and select only Internal storage, confirm to wipe (you may experience some discomfort at this point, this is normal)
Reboot to TWRP (from recovery to recovery, that's right)
Now copy all content back from the folder on your computer to the internal storage. You should be able to do this simply over USB while TWRP is active. If you don't, go to the main TWRP menu, tap 'Mount' followed by 'Enable MTP'
When the copy is complete, reboot to System and your trouble should be gone!
We're doing the wipe AND the restore inside recovery because if you would boot your device with an empty /sdcard partition, the Android system and all running apps would start freaking out and get going on all sorts of crazy, recreating their folders and files.
Tip: this is the perfect opportunity to sieve through those files! I recommend not just copying everything back but only the things you still need. Exclude folders of apps that aren't installed anymore and skip unused media files. This will decrease the chance of future corruption. Take some time to make your internal storage shipshape!
5. QUICK FIXES
5.a. The camera app can't connect to the camera
If you flashed something like OxygenOS Blobs, your camera will not work unless you set SELinux to Permissive. You should find this in your ROM settings (e.g. for RR this is under Settings > Configurations > Miscellaneous > Selinux mode > Permissive) or you can easily do this with SELinuxModeChanger.
Why this is a bad idea: SELinux or Security Enhanced Linux prevents malicious apps from gaining unlimited system level access by exploiting security holes. By setting it to Permissive, you’re disabling this extra layer of security. Infections due to this are rare but do happen, you’ve been informed.
5.b. Google Assistant isn't working or "OK Google" detection fails (this may be obsolete by now, please notify me if it is)
See 4.c., “Audio comes out low”.
5.c. QS toggle 'drops' when trying to add it
This may happen when attempting to add one of the lower QS toggles. There are two ways to work around this bug:
By lowering the display size: go to Settings > Accessibility > Display size (or under custom ROM configurations) and change it to Smaller or Smallest
By messing around: move icons from the top to the QS panel until you're able to slide the QS toggle you need without 'dropping' it
This video shows it works fine:
6. OTHER
6.a. How do I apply themes and which ones can I use?
OMS compatible ROMs only! To start, install Substratum from the Play Store, open it and grant it root rights (both substratum and masquerade). Then search the Play Store for substratum themes that are compatible with your Android version. Some will cost you something but most are really worth it and there are some great free ones as well. After installing a theme, apply it in Substratum. Don't forget to read the theme creator's instructions, some combinations can cause trouble!
6.b. Fast/Quick Charge isn't working
That's because the OnePlus One doesn't support it. You can, however, tweak charging rates with kernel tweaks (which is still limited, don't expect dash charge speeds). Equip yourself with proper hardware. A ‘smart’ charging station and quality cables can go a long way. Mind that faster charging is not better charging per se. You may shorten the lifespan of your battery when pushing it to the limits. Charging with the official charger/cable (which should take about 2 hours from 0 to 100%) is still the best way to treat your battery. Also note that if you got your device back in 2014, there's a good chance your battery doesn't have its full capacity anymore, longer charge rates and shorter lifespans can be expected. That being said, the OPO was equipped with a kickass quality battery, even after abusing it for all these years, many users have reported it still works great!
7. MODS
7.a. ViPER4Android
Since Magisk is more widely adopted, installing V4A has become very easy.
In Magisk Manager, tap the three lines top left
Tap Downloads
Scroll down to ViPER4Android FX and tap the download icon
Tap Install followed by Reboot
Once booted, go into Magisk > Downloads again
ViPER will now be on top, tap it
You'll find a link to the latest APK, download and install it
That's it. Open it and change all the settings you want, then reboot once more to make sure it all runs fine.
7.b. Camera mods
The OnePlus 5 camera software has been ported (download here) to Bacon and it works great, this is my current favourite.
Great camera mod: CameraNextModV2. It's just a simple flash away.
Not much of a mod but a Camera app optimized for our OPO: Bacon Camera!.
And good to know: Google Camera 4.1.006.135988111 is the last compatible version for Bacon.
Thank you for contributing, @venky716 @bdwilk @Baldesarra @Mr.Ak @Silverview @abhi08638 @tazzkiller @Genericxx @Turpb (PM me if your name should be here!)
Bacon ROM INDEX
For your convenience, I've listed *most* (maybe all of them, who knows) Nougat+ Bacon ROMs below. Please feel free to post in the thread if you found one not mentioned below. Cheers!
Original Android Development
PIE!!!!!
[ROM][9.0.0_r3] POSP v2.0 - BETA [OFFICIAL]
Oreo
[ROM][8.1.0_r29] AOSP Oreo for OnePlus One [Discontinued][23/05/2018]
[ROM][OPO][8.1.0_r43] Candy8.1 [OFFICIAL][SUBS]
[ROM] [UNOFFICIAL][8.1.0] Dot OS v2.x [BACON [30/03/2018][DISCONTINUED]
[ROM][8.1.0_r33] POSP v1.0 [OFFICIAL]
Nougat (not updating this list anymore)
[OFFICIAL][7.1] LineageOS 14.1 - OnePlus One [bacon]
[ROM][7.1.1_r13] Android Open Source Project | NOF26W [DATE]
[ROM][OPO][7.1.1_r26] Slim7 - Bacon [OMS][NOF27C][Nougat]
[ROM][OPO][7.1.1_r26] Candy7 - Bacon - OOS+Sultan camera [NOF27C][OMS][Nougat]
Android Development
PIE!!!!!
[ROM][9.0.0_R8][PIE] PixysOS [BACON][OFFICIAL]
[OFFICIAL] [AOSP] [WEEKLY] Arrow OS [Pie] [9.0.0_r8] | Bacon [2018-09-22]
[ROM][LineageOS][Android 9.0.0r6]] TugaPower™ 0.6 Beta
[ROM][9.0.0][UNOFFICIAL][Alpha] LineageOS 16.0 for Oneplus One [bacon]
Oreo
[ROM][8.1.0_r4][OMS] LineageOS-15.1 [bacon][BETA][UNOFFICIAL]
[ROM][BACON]RESURRECTION REMIX 6.0[OFFICIAL]
[ROM][LineageOS][Android 8.1.0r36][OMS] TugaPower™ 23.0
[ROM][8.1.0_r36][OFFICIAL] AospExtended ROM V5.7 [DUI]
[ROM][BACON][8.1][OMS] hyperUnicorns - Optimized Dirty Unicorns (discontinued?)
[ROM][8.0.0_r17] halogenOS 8.0 OREO [Testing] [UNOFFICIAL] (unavailable for now)
Dirty Unicorns 12.2 (20180513) (download only). No XDA support! Contact @deadlyindian for a Telegram invitation.
Crdroid ROM for OnePlus ONE crdroid-4.6 (TOP PICK!)
[8.1.x][WEEKLIES] CarbonROM | cr-6.1 [bacon]
[ROM][8.1.0_r42] AOSiP 8.1 [OPO][OFFICIAL]
Validus (shared by @pratikone1 here, have yet to check this) (newer version, still have to check it )
[ROM][8.1.0][OFFICIAL] Cosmic-OS v3.1 - Universe[BACON]
[ROM][8.1.0][UNOFFICIAL] BootleggersROM 3.0-STABLE [BACON]
Nougat (not updating this list anymore)
LineageOS[OMS][DATE][Make CM great again!][Optimized]
[ROM][OFFICIAL][7.1.1_r9][BACON][OPTIMIZED]RESURRECTION REMIX [5.8.0]
[7.1.1] [ROM] Android Ice Cold Project [Official Nightlies] [OMS]
[ROM][7.1.1][OFFICIAL]Android Open Kang Project[AOKP][NIGHTLIES][OMS7]
[DATE][OFFICIAL] 7.1.1 || Ground Zero ROMs || Validus - Tesla - Tipsy
[ROM][OFFICIAL][7.1.1_r6]CypherOS 3.5.1 Jamocha[Bacon]
[OFFICIAL][7.1.1_r9][BACON] XenonHD 7.1[OPTIMIZED][OMS]
[ROM] [7.1.1_r9] [OFFICIAL] [OTA] XOSP - Xperia Open Source Project 7.2
[ROM][OFFICIAL][7.1.1_r4] Zephyr-OS V6.2 [AOSP/Substratum/DUI]
[ROM][7.1][NOUGAT][NIGHTLY] Official Mokee Open Source Project
[ROM][7.1.1_r9][OFFICIAL] AospExtended ROM V3.1 [OMS/DUI]
[ROM][Bacon][7.1][OFFICIAL] Cosmic OS for OnePlus One
[DATE] Unofficial LineageOS 14.1 [OMS7][OPTIMIZED][PERFORMANCE]
[ROM] [bacon] [7.1.1] [LOS-based] **crDroid**v2.0
[ROM][7.1.1_r13] AOSPlusone 7.1 [SultanXDA's Camera HAL][OMS] | 22
Nitrogen OS ► [7.1.1 ► NMF26O] [OMS7] [DATE]
[ROM] [UNOFFICIAL] FLIVERCOD'S CUSTOM AICP-12.1 Android 7.1 [NOUGAT - Bacon] [Linaro]
[ROM/KERNEL][UberTC4.9/Linaro4.9] NucleaRom[Android 7.1.1_r6
[ROM][LineageOS-14.1][7.1.1_r9][OMS7] LegendROM
[ROM][Android 7.1.1]Unofficial Okeys Builds[LineageOS 14.1][OMS7]
[NIGHTLIES] idprophecy's unofficial optimized LineageOS 14.1 builds
[ROM][LineageOS][Android 7.1.1][OMS7] TugaPower 15.1
[ROM] [7.1.1] DarkobasROM [OMNI-ROM]
[ROM][7.1.2][UNOFFICIAL] AIM ROM v2.5 [OMS/DUI][Bacon]
[OFFICIAL][NOUGAT]dotOS-v1.0[Bacon] (this is probably the best one...)
CAF
[ROM][CAF][DATE] halogenOS 7.0 for OnePlus One
Kernel Index
Thunder (Oreo), click here!
FrancoKernel (N + Oreo), click here!
ab123321 Kernel, click here!
Boeffla official, click here!
Boeffla unofficial, click here!
Lightning, click here!
[Changelog]
2018-08-23
Howdy! I've been away (or at least very inactive) for a few weeks due to family vacation and other stuff – including two quite tragic events. That's life I guess
Anyway, interesting development seems to be never ending for this amazing device. The immortality of Bacon has yet again been confirmed with the release of PIE! This was predicted by my teenage antiheroes "Weebl and Bob" back in 2002; they are true visionaries :')
That's not one (KitKat), not two (Lollipop), not three (Marshmallow), not four (Nougat), not five (Oreo) but SIX (PIE!) major Android iterations that have seen light on this chunck of awesomeness. At this rate we might even see Android Queijadinha on the OPO! But let's not get ahead of ourselves. Let's celebrate and enjoy Pie's release first. Time to take a P (Captain Underpants, anyone?). Tra-la-laaa!
Created "PIE!!!!!" section
Added POSP to both Oreo and Pie sections
Added PixysOS
Updated Oreo titles.
2018-05-25
Added Cosmic-OS
Updated all ROM Index Oreo titles
The legendary AOSP by the equally legendary @Agent_fabulous is being discontinued more to come, though?...
Disclaimer: while you are reading this thread, I am shamelessly collecting your personal data. Including but not limited to your shoe size, favourite colour, romantic preferences, how many times you've shouted my username, your failure to use search properly (yes, again!), social security number, blood type, flash habits, flash hobbits (for "precious" ROMs), cookies (both edible and non-edible), the way you're hovering this text with a cursor, etc. You have no right to view, alter or delete this data in any way, I will gain massive profits from it and there's nothing you can do about it. (...) Of course I'm kidding! #GDPRday -_-
2018-04-01
Added CrDroid ¯\_(ツ)_/¯
Added [8.1.x][WEEKLIES] CarbonROM | cr-6.1 [bacon]
Added [ROM] [UNOFFICIAL][8.1.0] Dot OS v2.1 [OMS] [BACON [30/03/2018]
Updated all ROM Index Oreo titles
Free Bacon pr0n: click here (warning: explicit content!)
Happy Easter everyone! ?
2018-03-29
Added RR Oreo added to the ROM Index! LoL, I was so occupied with that ROM today I totally forgot to add it to this list
2018-03-18
Added DU v12.0 Oreo unofficial to the ROM Index because it's just so awesome (and because dev allowed me, lol). There's no XDA thread so don't expect any support. So just.. eh.. #staydirty I guess ^_^
Check out my new animated sig! Created it myself in Photoshop. Let me tell ya, it was a long night
2018-03-15
Added thread jumper on top of OP for people who really hate scrolling :silly:
Oh and a late happy bday, little thread of mine!
older
2018-02-28
Updated Oreo ROM list @ post 2
Moved Franco Kernel up in kernel list (now Oreo compatible) @ post 3
Added CM13 snapshot step in flashing procedure (3.b.)
Updated prerequisites (2.b.) to complement flashing procedure
Added more elaborate info and resources on firmware flashing (2.c.)
Updated all TWRP links to direct download for 3.1.1-5-TugaPower (last stable release of my preferred recovery)
Fixed 'how to check MD5 hash link (was censored?)
Updated file info in 4.c. as audio_platform_info.xml moved to /system/vendor/etc in Oreo
Updated To Do list below
Getting pretty 'ultimate' looking back on first release below, nearly one year since I launched this
2017-12-4
Added 4.e. Can't read or write to internal storage (/sdcard)
Removed changelog bits in OP
Added changelog reference and new/updated legend in index
2017-11-21
Added '1.c. Creating a logcat'
2017-11-15
Reworked the disclaimer
Changed 1.a. stat: from 50,000 to 80,000 installs!
Added Frankenstein Release to firmware (using it myself, quite happy with it)
Replaced "can't find the current release of a ROM" with "EXT4 vs. F2FS"
Updated TWRP links to thread instead of direct download
Made a reference to post #3 instead of listing kernels again
Added link for SDK Platform Tools
Removed optional LOS flash suggestion (obsolete)
Reworked flashing procedure (kernel doesn't need in-between reboot anymore)
Added Magisk reference as root solution
2017-11-12
Updated ROM and Kernel section for Oreo (and Mr.Ak, naturally)
2017-06-27
Added kernel index (post3)
2017-04-07
Bug Fixes and Improvements, lol.
Added '3.a. Installing TWRP' and updated '7.a. ViPER4Android' (to Magisk standard)
2017-03-12
Post #2 is now a Nougat ROM index!
2017-03-12
Added '5.c. QS toggle 'drops' when trying to add it' + video
2017-03-05
First release, not very "ultimate" YET
[To Do]
Elaborate more on kernels (kinda given up on this as Oreo doesn't offer the same freedom we once had in Nougat)
Meh, you tell me!
@Timmmmaaahh
Thanks mate for your helping nature...
I don't know anybody feel or not but you're one of the most helping people of XDA at least for me. I have GOOD memory of your help when my BACON has died and then you helped me a lot, Many people helped me but your help I can't forget...
Thanks mate keep it up..[emoji120]
Unbeatable!
This is going to be fun.
Thanks! @Timmmmaaahh
Edit:
Add Q. What is the codename of Oneplus One?
A. Bacon.
Q. How is this device in over all usage and stuff?
A. Two Word- Bacon FTW!
For those who want TL;DR
There you go
Many thanks for your time
You are our tech Angel
Enviado desde mi A0001 mediante Tapatalk
nachomagic said:
Many thanks for your time
You are our tech Angel
Enviado desde mi A0001 mediante Tapatalk
Click to expand...
Click to collapse
Angel? Lol.
Added 5.c. QS toggle 'drops' when trying to add it + video
[Post#3333] for RR is now the official FAQ.
Nougat ROM INDEX now live!
2017-04-07
Bug Fixes and Improvements, lol.
Added '3.a. Installing TWRP' and updated '7.a. ViPER4Android' (to Magisk standard)
I am planning on a clean flash soon and often refer to your guide as the best source. After all it is titled "The Ultimate OnePlus Guide", so it must be true.
May I request that you begin updating posts #1-#4 to include Oreo? I find the tips you posted here (link) helpful.
cfedata said:
I am planning on a clean flash soon and often refer to your guide as the best source. After all it is titled "The Ultimate OnePlus Guide", so it must be true.
May I request that you begin updating posts #1-#4 to include Oreo? I find the tips you posted here (link) helpful.
Click to expand...
Click to collapse
I honestly thought no one paid any attention to this, lol. Sure thing, I'll try to work on an update this weekend!
How much fat there is in 1kg of bacon?
Timmmmaaahh said:
I honestly thought no one paid any attention to this, lol. Sure thing, I'll try to work on an update this weekend!
Click to expand...
Click to collapse
Don't forget to add roms compiled by me,though.Kthnxbye.
---------- Post added at 12:57 AM ---------- Previous post was at 12:56 AM ----------
Fatsodonkey said:
How much fat there is in 1kg of bacon?
Click to expand...
Click to collapse
The same amount of fat as in 1kg of v0lte.
4.b. My device just exploded!
It's most likely unrelated to a software problem but please, feel free to share pictures!
This made me laugh! :good:
2017-11-12
Updated ROM and Kernel section for Oreo (and @Mr.Ak, naturally)
Mr.Ak said:
Don't forget to add roms compiled by me,though.Kthnxbye.
Click to expand...
Click to collapse
romS? as in plural?
Did I miss any Oreo releases? I'm sure I did...
I'll refresh the OP later, more procrastination first!
Timmmmaaahh said:
romS? as in plural?
I'll refresh the OP later, more procrastination first!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/development/rom-aim-rom-v2-5-t3693630
I can see you're not as active as before sur.You need to get some v0lte in your life.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to the NitrogenOS Q&A Megathread. Here you can find answers for the most popular problems and questions about NitrogenOS. I started this thread, so that new users don't repeatedly ask the same questions multiple times. While I am fairly new to coding in Java, I can definitely say I know a lot about Android phones and NitrogenOS, but you'll have to trust me on that. If you need any more help, you can even PM me and I'll try to reply as soon as I can.
You can find the original NitrogenOS thread here.
ROM info
Developer: xyyx
Latest Android version: 8.1 Oreo
NOS Download (latest): https://sourceforge.net/projects/nitrogen-project/files/kenzo/kenzo_test/8.1/
Bugs and updates
- A (very) small amount of users reported Google Dialer not working properly while installed through OpenGapps or the Play Store, you can still use stock dialer
1. Test or stable?!?!
Test in this case doesn't mean less stable. xyyx named the two versions a little confusingly.
Test means Oreo (Android 8.0 and 8.1) and Stable means Nougat (Android 7.1.2).
So let's make this a little less confusing:
Oreo (8.0) builds -> Download from here
Oreo (8.1) builds -> Download from here
Nougat (7.1.2) builds -> Download from here
2. Youtube PiP (Picture in Picture mode)
Google has patched PiP a long time ago, so it doesn't work with the latest Youtube releases. The last official release working with PiP is 12.34.55, which you can download from ApkMirror.
My preferred option however is iYTBP (injected YouTube Background Playback), a modified version of Youtube, but it gets a little confusing as there are multiple options.
You can download it from this thread.
Now the tricky part - choosing the right version. I always prefer the Vanced version, which can be found in the 2nd post. Again you have multiple options, but I will not go through all of them since they are explained pretty good in the post itself. While iYTBP enables PiP, it also blocks ads and adds a lot of useful settings and new updates come very frequently. There are multiple installation methods, but I prefer the Magisk one, since it offers options like detaching the Youtube app from Play Store. What this means is, that you don't have to disable auto-updates and it will not bug you to constantly update it.
You can try these methods:
Magisk Module (Easiest):
1. Open Magisk Manager
2. Go to Downloads
3. In the search bar type "Youtube", you should see two results
4. Choose either the normal or the black theme (I personally prefer the black one)
5. Press the download arrow and then "Install"
6. Wait for a while (it's a big package to download and unpack)
7. Reboot
This is by far the easiest option and the module is updated fairly often.
Manual:
1. Delete or uninstall any previous release of Youtube. If you installed it as a system app, disable it or delete the /system/app/YouTube folder. If you had to delete the folder, reboot.
2. Download the Youtube apk
3. Make a folder called YouTube (watch the caps!)
4. Move the apk to this folder and rename it as YouTube (again with the caps)
5. Copy/move the folder to /system/app (The directory should look like this: /system/app/YouTube/YouTube.apk)
6. Reboot
Magisk (manual):
1. Download the Youtube apk, the iYTBP universal installer and the use_this_settings.sh file. Check that they are in the downloads folder.
2. Edit the use_this_settings.sh file if you want. Since we're installing from Magisk, you'll need to set MAGINSTALL to YES (MAGINSTALL="YES"). I usually also enable detach (DETACH="YES"). This will make the Play Store think Youtube isn't installed and it will not bug you for updates.
3. Open Magisk Manager, go to Modules and press the + button. Now select the universal installer zip and flash it in Magisk.
4. Reboot
Recovery method:
Same as for Magisk, but MAGINSTALL is set to NO (MAGINSTALL="NO"). In case you didn't read the Magisk method, here is the recovery method...
1. Download the Youtube apk, the iYTBP universal installer and the use_this_settings.sh file. Check that they are in the downloads folder.
2. Edit the use_this_settings.sh file if you want. I usually enable detach (DETACH="YES"). This will make the Play Store think Youtube isn't installed and it will not bug you for updates.
3. Reboot to recovery, go to Install and choose the universal installer zip, flash it.
4. Reboot
If you open a video in fullscreen mode and press the home button, it should open it in PiP mode. If you want to change some advanced settings, you can go to your Account (the round icon with your profile picture) -> Settings -> iYTBP Settings
3. Goodix & FPC - What are they
Goodix and FPC are two different types of fingerprint sensors (or rather sensor manufacturers). They both work in Android 8.1 builds. Custom kernels or mods may break the fingerprint sensor functionality.
4. Rooting
tl;dr: rooting NitrogenOS is the same as rooting any other custom rom, just flash Magisk, SuperSU, phh's superuser or anything else.
Now for the extended version.
Magisk:
Magisk is a great open-source root manager, developed by topjohnwu. It features a feature rich app, but most people prefer it because of it's "modules", packages which can do a bunch of things, from installing apps like Viper4AndroidFX or Dolby Atmos, to modifying system settings, like the volume steps increase. Magisk also features an option called "Magisk Hide", which can bypass Android's SafetyNet.
Check out the Magisk thread.
You can directly download the latest version of Magisk from https://tiny.cc/latestmagisk
SuperSU:
SuperSU is an alternative root manager. It used to be developed by Chainfire, but has recently been purchased by another company. I still prefer Magisk, but SuperSU is a great alternative for new users. My problem with it though is, that it is not open-source and the new buyer is pretty secretive so I don't really trust them.
Check out the SuperSU website for the download link.
phh's SuperUser:
Another open-source root manager, but the great thing about this one is, that it's very minimalistic and very small in size.
Check out the SuperUser thread and phh's Build Bot.
5. Google Apps (gapps)
Google apps are a vital part of custom roms. You might not know this, but AOSP and CM based roms are made from Google source code. Google actually makes Android open-source, but the Play Store and other Google apps are not. That's why roms like NitrogenOS do not come with the Play Store preinstalled. That is where Open Gapps come in. They are prepackaged apps, updated almost daily. They come in various sizes and versions, but they can all be flashed in TWRP like a normal zip file.
Platform: arm/arm64/x86/x86_64 - RN3 has an arm64 processor (Think of it as a 64-bit CPU for phones)
Android: 8.0/7.1/7.0... - This is the android version, NOS is Oreo based so choose 8.0 (Or 7.1 for Nougat) [Check below for OpenGapps 8.1]
Variant: This is where it gets complicated. There are a LOT of versions to choose from. For more in-depth resources check the OpenGapps' package comparison.
But OpenGapps are a lot more customisable, to the level where you can choose individual apps you want installed. The easiest way to do this, is to flash the Aroma package, which enables you to choose exactly which packages you want installed. Another option is to configure any of the selected packages using a gapps-config.txt file. You can learn more about that in the Advanced Features and Options section.
You can download daily builds for any Android version from https://opengapps.org/
6. TWRP (Recovery)
A recovery is a partition, used to flash files like ROMs, gapps and any other modifications. You do (in most cases) need an unlocked bootloader to use it. Unlocking your bootloader will not be described on this thread, as there are a lot of resources for our device.
Official TWRP - This is the official TWRP (Team Win Recovery Project) for our device
You can find the latest updates for TWRP on their website.
Red Wolf - This is a modified version of TWRP, my absolute favourite because of it's custom features.
Flashing TWRP:
If you don't have a custom recovery installed and you have unlocked your bootloader, then download the latest version of your preferred recovery and follow these steps:
1. Download Minimal ADB and Fastboot on Windows, or use sudo apt install android-tools-adb android-tools-fastboot if you're on Linux.
2. Enable USB Debugging (Settings -> About phone -> Press "Build number" 7 times to enable Developer options). You should find the Developer options in settings above "About Device". Find USB Debugging and enable it.
3. Connect your PC to the phone via a cable. Open Minimal ADB and Fastboot (which will open CMD) or Terminal on Linux and type this (same for both OSs): adb devices. Select "Always allow on this computer" and confirm access on your phone.
4. Reboot your phone to fastboot/bootloader (By holding Power and Vol-, releasing the power button after a vibration and holding the Vol- button until you see the Xiaomi mascot).
5. Type (In CMD/Terminal): fastboot devices, to confirm if the phone has been recognised, then fastboot flash recovery /path/to/recovery.img
6. After it has succesfully finished, remove the cable and reboot directly to recovery (Power and Vol+, release power after vibration, but keep holding the Vol+ button until you see the TWRP or RedWolf logo).
If you do already have a custom recovery installed and just want to update it, flash the .img or .zip file in your already installed recovery and select "Reboot to recovery".
7. NOS asks me for a password after flashing?!!?!?
This is actually not NitrogenOS's fault, it's a byproduct of your previous rom, most often MIUI. What this means is, that your internal storage is encrypted and the only way to fix this, is to backup everything on your internal storage, which you can do by connecting your phone to your pc while in recovery. You should be able to access the phone's storage and move the files from there. If you for some reason can't do that, you can still put in an sdcard and copy the files to it in TWRP. Bottom line, backup the files and then go to "Wipe" and find the "Format data" button. You might see a "wipe data" button, but this is not the same. When you "wipe data" you are wiping your system, cache, dalvik cache and data partitions, but formatting data will format your internal partition as well and thus remove the encryption.
You can finally reflash NOS and gapps or whatever other modification you want.
8. Firmwares
Check out this link to download the latest firmware for our device.
What is firmware? - It's what connects hardware to software (don't confuse it with a kernel). It's what, for example, makes the camera work.
Do I really need firmware - Yes (but it's already installed, even after completely wiping the stock rom, since it's on separate partitions).
Do I need the most up-to-date firmware - Actually no, the only difference you will notice is in the signal and WiFi strength. If yours are good enough, you don't need to update, otherwise feel free to download the newest version from the link above.
What is emmc_appsboot.mbn? - It's a bootloader update. Bootloader or fastboot is the partition in which you have unlocked your bootloader and flashed the recovery. If you have officially unlocked your bootloader, then you can flash firmware with emmc_appsboot.mbn, but if you have unofficially unlocked your bootloader, do not flash these files as they will re-lock it. But you can still flash the version without emmc_appsboot.mbn.
Kenzo? Kate? - Kate devices are the same as kenzo ones but are a little bigger.
Some comparisons:
Kenzo
Size: 150 * 76 * 6.85 mm
Weight: 164g
Kate
Size: 152 * 76 * 6.85 mm
Weight: 167g
Model numbers:
Kenzo: 2015116
Kate: 2015161
Kate devices are 32/3 GB, and some kenzo devices are as well (some are 16/2 GB), not really sure about this part.
Global stable or developer? - Most people use developer roms, but again, this is not the actual ROM, just the firmware extracted from the rom, it doesn't really matter which one you choose.
When do I need to flash firmware? - If you're coming from MIUI8 (or 9), then you probably have the newest firmware. In this case you don't need to flash it, because MIUI roms already have firmware included in the update. If you're coming from a CM or AOSP based rom you also probably don't have to flash it, but I suggest you update it just in case. If your signal is good enough though, there really is no need.
9. How to flash the rom
Flashing is pretty straight forward. Just go to the Install section of TWRP and flash it like any normal zip, nothing special.
If you're coming from MIUI, then the full procedure is this:
1. Unlock your bootloader (google it, useless explaining it here)
2. Flash TWRP
3. Make a full device backup (Nandroid backup)
4. Copy or move all important files from the internal storage to an sdcard or your pc
5. Format data, or in other words, wipe EVERYTHING (excluding external storage) - This will delete all your photos and anything else in internal storage
6. Flash the latest NOS "test" build (Oreo)
7. Flash gapps (I recommend opengapps.org, check above)
8. Reboot to system
10. OTA?
What is OTA? - OTA means Over The Air (Update)
Does NOS have OTA? - Actually yes and no, newer updates (from March 2018 on) do have partial OTA (it does check for updates and notify you, while also giving a direct download link to SourceForge, but you will have to manually flash every update in your recovery.
What about incremental updates? - Sorry, but no. You'll have to download full packages every time. If you have a bandwidth cap then just download an update every week or two, you can check the changelog to see if you think it's worth updating to.
11. Google Camera
If you're having problems with the official Google Camera or just want some added features then look no further than modded camera apps. Check out this thread by emime12, it's very frequently updated and features a lot of different camera mods, including Google Camera, MIUI Camera, MOTO Camera and many more.
Recommended settings:
3x3 Grid - For better photos
I usually disable "Save location" and "Camera sounds"
Model: Pixel XL (corr) - default
Config camera HDR+: NEXUS 6
HDR+ parameters: Default
Panorama resolution: High
Advanced: Enable both
Experimental: I usually leave this disabled but it's your choice.
Back camera video resolution: UHD 4K (30 fps)
In case your camera doesn't work check if you have these two files and delete them:
/System/framework/com.google.android.camera.experimental2016.jar
and
/System/etc/permissions/com.google.android.camera.experimental2016.xml
Credits go to: @emime12 and Njaiker.
You can find more info about problems and updates on emime12's thread.
Settings may differ a lot, so check emime12's recommended or just test until you find ones that work for you
12. RAM Management - Low free RAM
Android's RAM (Read Only Memory) management doesn't work like Windows'. Android manages RAM very well, "Free RAM is wasted RAM" is a very common expression on XDA. Android loads the first couple of apps into the RAM and priorities the open one. More used ram means more apps loaded in ram which means faster load times. Don't worry about it too much and just enjoy the fast loading speeds.
13. VoLTE?
VoLTE should work on Android 8.1. Magisk, Viper or any other mods may break it.
14. Custom kernels
While there are a lot of custom kernels, I suggest you stick with the stock one, as it is made specifically for NOS and thus it is the most stable. If you still want a custom kernel, you can try Radon or Agni but they might break VoLTE or your fingerprint sensor.
Agni XDA Thread - By psndna88
Radon XDA Thread - By Umang96
15. Daily driver or not?
Yes, NitrogenOS Oreo is very stable, definitely enough for a daily driver. It is the best Oreo rom for our device (in my opinion), as it offers just the right amount of customization and stability.
15. GPS
Some users have reported low accuracy, but you should be fine if you turn on High Accuracy mode and/or install Faster GPS.
Update: In recent updates GPS shouldn't be a problem anymore as xyyx has fixed it, but some users have still reported low accuracy.
16. Viper4Android FX
(There may be other ways, but I haven't tested them yet so I can't confirm if they work) By far the easiest way to install Viper4Android FX is using Magisk. There is Magisk module called ViPER4Android FX Materialized. Download and install that module from the Magisk repo, choose your preferred installation option (By pressing Vol+ or Vol- to select which version you want installed and if you want it materialized - for newest materialized version press Vol+ 2 times) and finally reboot. Try playing some music and open the Viper app. Turn on the "Master Power" switch and the "Playback Gain Control" (the easiest way to tell if it worked). If after a little time the volume increases, it means that Viper4Android FX works. If not, press the three dots and choose "Exit" (without turning off the master power or gain control). Now open the app again and it should work. You can also check that in the side menu under "Driver status", if it's enabled and processing, then everything works.
You may or may not have to exit and re-enter the app after reboot to enable processing (in my case I had to).
I would show you my recommended settings (as requested), but to be honest I only use:
Headset
Viper Bass (Natural bass, 40 HZ frequency, 8 dB)
Viper Clarity (Natural, 6 dB)
Sometimes I use Field surround with default settings
Phone speakers
eXtra loud (Slight, 4x max gain, -1.9 dB max output)
Bluetooth device
Playback gain control (Moderate, 6x max gain, -1.9 dB max output)
If I'm at a party with my bluetooth speaker I pump it up to Extreme and 8x max gain
Viper Bass (Natural, 40 HZ frequency, 8 dB), 17 dB for parties
Viper Clarity (Natural, 3.5 dB)
I don't use equalizers or if I do, they are song-specific. I also don't USB/Dock, so I can't recommend anything there.
Of course these settings can vary depending on the song, so choose those, which you like the most and don't stick with just those I chose, try all the functions to see which you prefer.
17. AdAway (Root)
AdAway is a great open-source root ad blocker, which can automatically download and update sources and works by adding those to the hosts file. It work well on the internet, but also inside apps (most of the time).
Check out the official AdAway website. You can also download it from F-Droid.
Adaway v3.2 (60) (direct download link)
Adding custom host sources:
Go to "Host sources" and add your own sources or check out these: AdAway's host sources
Be careful when adding all of them, since some can block legitimate links like goo.gl.
AdAway also offers an option to scan for Adware, which can be found under "Scan for adware". This will bring up a new window, press "Start scanning". If you don't need/want the mentioned apps you can uninstall them, but AdAway can't block their ads.
You can also check out my recommended settings:
wow,really appreciated that sir., it is very helpful specially for those who wanted to try, flashing rom or any mods on their device like me. thanks and keep up the good work sir God bless!
i think i can add up little bit here.
1) u r on miui & u want to flash nitrogen so u go to recovery and backup ur current rom in case if u dont like nitrogen u can restore back to miui with all ur setting & app. now assume u r on nitrogen, after 4-5 days u dont like nitroge & u decided to come back to miui, so u go to recovery and restore yr backup that u have taken earlier. after success booting the screen with pin or password will appear. so u would enter/guess any previous password, pin u used earlier but it will not open. here the real problem come. i have also faced same issue & got upset searching endless solution on google . u will get mad on u. security bypass will also not work. after spending endless hour i come with solution. download aroma zip search on net. flash it through recovery this will help u to get in system its ike file manager. then head to data, system and delete all file u see below
locksettings.db, locksettings.db-shm, locksettings.db-wal, gatekeeper.password.key, gatekeeper.pattern.key
and then restart, yr problem would be solve.
2) nitrogen os does not support video calling via jio. none custom rom other then then miui support.
3)xposed is not available for oreo.
4)i have used nitrogen oreo for about 2 weeks it is stable but not as miui. some time r net would not work, jio call drop, lagging u have to restart on every time u faced problem. i suggest that wait for some time to roll out nought port for kenzo with zero bug & this will happen soon.
saifuk said:
i think i can add up little bit here.
1) u r on miui & u want to flash nitrogen so u go to recovery and backup ur current rom in case if u dont like nitrogen u can restore back to miui with all ur setting & app. now assume u r on nitrogen, after 4-5 days u dont like nitroge & u decided to come back to miui, so u go to recovery and restore yr backup that u have taken earlier. after success booting the screen with pin or password will appear. so u would enter/guess any previous password, pin u used earlier but it will not open. here the real problem come. i have also faced same issue & got upset searching endless solution on google . u will get mad on u. security bypass will also not work. after spending endless hour i come with solution. download aroma zip search on net. flash it through recovery this will help u to get in system its ike file manager. then head to data, system and delete all file u see below
locksettings.db, locksettings.db-shm, locksettings.db-wal, gatekeeper.password.key, gatekeeper.pattern.key
and then restart, yr problem would be solve.
2) nitrogen os does not support video calling via jio. none custom rom other then then miui support.
3)xposed is not available for oreo.
4)i have used nitrogen oreo for about 2 weeks it is stable but not as miui. some time r net would not work, jio call drop, lagging u have to restart on every time u faced problem. i suggest that wait for some time to roll out nought port for kenzo with zero bug & this will happen soon.
Click to expand...
Click to collapse
Thanks for the tip, will update the thread.
@JustMeErazem volte on 2nd sim works well. I myself use it. After flashing magisk just v need to hide root from all system apps to make sure volte works flawless even after reboot. Plz edit it in the description. I hav been using nos since many time so with experience i am giving my feedback. Thanks?
@saifuk what kind of nougat port u are expecting of ?
Aditya1011 said:
@JustMeErazem volte on 2nd sim works well. I myself use it. After flashing magisk just v need to hide root from all system apps to make sure volte works flawless even after reboot. Plz edit it in the description. I hav been using nos since many time so with experience i am giving my feedback. Thanks
Click to expand...
Click to collapse
I haven't rooted my phone, VoLTE still not working.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
@justmerazem Change VoLTE point again to previous. I installed NOS on mine & my other two friends' phone. They've not used magisk or superSU nor me. But VoLTE doesn't work on 2nd Sim for us.
AtomR said:
I haven't rooted my phone, VoLTE still not working.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
@justmerazem Change VoLTE point again to previous. I installed NOS on mine & my other two friends' phone. They've not used magisk or superSU nor me. But VoLTE doesn't work on 2nd Sim for us.
Click to expand...
Click to collapse
Flash latest firmware of developer rom. And volte is sure shot working.
Aditya1011 said:
Flash latest firmware of developer rom. And volte is sure shot working.
Click to expand...
Click to collapse
Mate, I'm already on 7.9.22 firmware. Lots of people are reporting it. Yours is working, must be some kind of random.
@Aditya1011 Mate, what happened? No reply? Huh. Latest firmware. No magisk, no any kind of root. No sound mod. Still Volte not working on 2nd Sim on 3 different Kenzos.
@JustMeErazem Please include in your post that VoLTE is indeed buggy.
how to install via dualboot patcher as secondary rom?
AtomR said:
@Aditya1011 Mate, what happened? No reply? Huh. Latest firmware. No magisk, no any kind of root. No sound mod. Still Volte not working on 2nd Sim on 3 different Kenzos.
@JustMeErazem Please include in your post that VoLTE is indeed buggy.
Click to expand...
Click to collapse
Idk bro y that happening to u. Flash miui EU rom n thn the nos rom. Mayb that should work.... Bcuz I had done that for the 1st time whn my volte wasn't working at any cost. Best of luck.
smjhh said:
how to install via dualboot patcher as secondary rom?
Click to expand...
Click to collapse
I don't think dual boot patcher supports oreo roms. Try asking on their thread to see if it does.
Google HDR camera 5 or 5.1 work with this ROM??
sagar13190 said:
Google HDR camera 5 or 5.1 work with this ROM??
Click to expand...
Click to collapse
Read op!
I tried google HDR camera v5 n v5.1 on lineage Oreo, MAOSP Oreo nitrogen Oreo ROM bt its not working...bt in ROM based on nogut 7.1.2 its work great
sagar13190 said:
I tried google HDR camera v5 n v5.1 on lineage Oreo, MAOSP Oreo nitrogen Oreo ROM bt its not working...bt in ROM based on nogut 7.1.2 its work great
Click to expand...
Click to collapse
It works for many users. Did you flash my zip or install an apk?
Sim card detection issue
Sometimes nitrogen os Oreo does not detect sim cards after reboot so I changed ROM and installed aosp extended. I know that Xyyx has already mentioned this as bug. Due to this bug it is not daily driver. Hope xyyx will fix this as soon as possible. If you have solution, please share it.
dhavalmehta said:
Sometimes nitrogen os Oreo does not detect sim cards after reboot so I changed ROM and installed aosp extended. I know that Xyyx has already mentioned this as bug. Due to this bug it is not daily driver. Hope xyyx will fix this as soon as possible. If you have solution, please share it.
Click to expand...
Click to collapse
Dude, it's really not a big problem, it detects it like 95% of the time. Just reboot and you're done. Or wait about 2 min and it should detect it. You could also just remove the sim and reinsert it. But since the latest few updates for me it gets detected 100% of the time. So update to 28/10/2017 build and you should be fine.
@JustMeErazem You're giving flase info. to others saying that VoLTE works on both sim. Actually, it works only on first sim. Tried, tested on 3 different Kenzo's. Clean flashed.
Conclusion: VoLTE doesn't work on 2nd sim.
I guess global version will come within 2 days.
http://www.oneplusbbs.com/forum.php?mod=viewthread&tid=3876301&mobile=2
Step by Step Guide - Android 8.0 Chinese beta. Clean/dirty flash lock/UL BL.
Hello Guys,
To make things easy heres a step by step guide to install the chinese oreo beta on locked/unlocked Bl for the 5T
So I got my hands on the android oreo chinese beta (H2OS) and flashed it on my oneplus 5t which was on a locked bootloader and running stable 4.7.6 with star wars theme enabled. Here's a step by step guide to install H2os Oreo beta rom wtihout losing any data.
WARNING : BACKUP - BACKUP - BACKUP and flash at your own risk. I would not be responsible for any loss.
METHOD 1 : FOR LOCKED/UNLOCKED BL BUT WITH STOCK RECOVERY
1) Download the rom from this link : https://goo.gl/4nPrxx
2) Ensure you have backed up all your important data and make sure you have atleast 50% battery.
3) Copy the downloaded zip to phones internal memory (make sure its in the main directory and not in any folder.
4) Go to settings > system updates > top right hand corner tap the settings icon > tap local upgrade > tap on the downloaded file > tap update now and wait for it to finish installing the update. ( first boot will take 8 to 10 minutes so please dont panic.
5) Once first boot is done you may have a force close for 1 or 2 apps just uninstall them and reinstall from the play store and you are good to go. Also star wars theme continues to work and all basic functions work as expected.
6) If you want a clean install or having many force closures please perform a factory reset and everything should be resolved.
https://forum.xda-developers.com/oneplus-5t/how-to/step-step-guide-android-8-0-chinese-t3726772
Yup, I'm downloading now. This should be fun.
Mike02z said:
Yup, I'm downloading now. This should be fun.
Click to expand...
Click to collapse
When you're done, can you tell us what exactly has changed? I went to the chinese page, but google translator wasn't so helpful tbh.
devil188 said:
When you're done, can you tell us what exactly has changed? I went to the chinese page, but google translator wasn't so helpful tbh.
Click to expand...
Click to collapse
This update ushered in based on the new Android O (8.0) hydrogen OS
【desktop】
- Optimized application shortcut menu
- Integrate icon options with app shortcuts
- Shot on OnePlus Add photos upload function
【system】
New shortcut settings panel design
- Android O new features, including but not limited to:
****1. Add Picture in Picture function
****2 new auto-fill (Auto-Fill) function
****3 new smart text selection (Smart Text Selection)
- Update Android system patch
Known Issues
1. WeChat fingerprint payment can not be used temporarily
2. Third-party applications may not compatible list, please download the attachment compression package. Android O may not be compatible with the application list. Rar (25.83 KB, Downloads: 364)
This a translation of the update. I used g translate. :good:
It seems to run OK. Obviously some stuff is still in Chinese. I tried to flash TWRP and TWRP booted but even after a clearing cache/Div the ROM then would not boot. I just got a white light.
For initial install I did a complete data format then loaded the stock recovery ,and the latest stable OOS, then flashed the Chinese O.. You do need to pull a PlayStore .APK and reload all the Google apps after a flash.
Unless this one is different than the one they have on their main site, it's not Oreo. I flashed it, tried flashing Gapps and Gapps said I had to flash appropriate Gapps for 7.1 :/
Very nice. Thanks for the write-up!
Already open beta 3 now.
What's this?
First of all, I'm not the original developer.
He post it on other Chinese forum, and I am just to ask for his permission and post it here.
All credits to Coolapk user: Tutoo.
This is an unofficial build of Pixel Experience Pie for Oneplus 5T (dumpling).
The original is for Oneplus5, you can find it here : Click here
The dev make a port version of this
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
WiFi
Bluetooth
Camera (but same as other Pie ROM, a little laggy in third apps)
Flashlight
Camcorder
Sound / vibration
GPS
AOD
Hotspot
NFC
VPN
And device specific addition (same as OP5 thread)
Known issues:
Permissive
or other issue same as OP5
Fingerprint gesture to view notification also not working
But you can try the solution provide by @Sabissimo at #16
Although that didn't work for me, some report they success, still looking into the problem
If that work for you, don't forget to give him a thank
If you find any bugs, you can PM me or leave comments below, I'll reported it to original dev
Instructions :
First, backup your data to PC or laptop
Second, you HAVE TO wipe data,system,cache AND INTERNAL STORAGE (some reported that it didnt boot if no wipe internal storage)
Third, flash the ROM and No verity zip (In my case, I use v3, but it seems with no problem)
Now you can boot up your device, it'll boot up TWO TIMES, and this is normal
CAUTION !!!
Version1 already include Gapps,Magisk (16.7), firmware, gcam and Redflare kernel (1.13 build)
So it is unnecessary to flash other zips
But in Version2, it didn't have firmware, but with Magisk (17.1) and Redflare kernel (1.16 build)
you guys need to take notice of this
Downloads:
Because original was on Baidu Cloud, and it may block some countries IP (Example: Taiwan)
So I upload it to Google Drive
If it is needed to upload to AFH or other cloud, just PM me, I'll upload it when I'm free
Here is the GD link:Version1
Version2
Credits:
Coolapk user "Tutoo" for his awesome work
and XDA user @bhageerathreddyy for help testing
Because of the forum rule, TG group link are not allow to post publicly here.
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.4.152, RedFlare EAS kernel
ROM Firmware Required: TWRP, Unlocked bootloader
Based On: AOSP
Version 2 changelog:
VoLTE reset on reboot Fixed
Proximity Sensor Fixed for FP and Gestures (Now phone won't start dialling numbers when in your pocket )
Added more Off screen Gestures and fixed V gesture
Improved OMNI slider switch
RedFlare kernel 1.16+
Linux 4.4.154
(Well... I copied these from original 5's thread. Don't forget to thank him for fix !!)
thanks
Thanks
Sent from my ONEPLUS A5010 using Tapatalk
This was much faster than expected for this rom, been swapping between this and OOS, will have to test this tonight and Pie for the first time, ty for fast release.
HI, just flashed this. Looks and feels good but the fingerprint swipe gesture doesn't seem to work properly, It treats it like arrow keys and navigates around the UI.
rijads said:
This was much faster than expected for this rom, been swapping between this and OOS, will have to test this tonight and Pie for the first time, ty for fast release.
Click to expand...
Click to collapse
Can u tell me dose it includes the adaptive battery and gcam ? And how are the animations ? And notification slider options
ROM is awesome! Adaptive battery, gcam, slider - all working
To make fingerprint gestures work, put this file in /system/usr/keylayout , and give it 755 permissions
https://drive.google.com/file/d/1Nhjs7YWulTHy-6d-AM1R1cLN_TfK-ieY/view?usp=sharing
MyStyle0714 said:
What's this?
First of all, I'm not the original developer.
He post it on other Chinese forum, and I am just to ask for his permission and post it here.
All credits to Coolapk user: Tutoo.
Click to expand...
Click to collapse
THREAD MOVED TO HOW-TO
Per the Device Forum Rules, all threads posted in the Development section must be your own work. ROM shares may be posted in the How-To section.
@Sabissimo how long does the boot took for you ? im on google bootanimation but nothing has happened since last 5 minutes ! can you also explain your installation process !
didn't help
Sabissimo said:
ROM is awesome! Adaptive battery, gcam, slider - all working
To make fingerprint gestures work, put this file in /system/usr/keylayout , and give it 755 permissions
https://drive.google.com/file/d/1Nhjs7YWulTHy-6d-AM1R1cLN_TfK-ieY/view?usp=sharing
Click to expand...
Click to collapse
i did what you wrote,
now swiping doesn't do anything
tids2k said:
@Sabissimo how long does the boot took for you ? im on google bootanimation but nothing has happened since last 5 minutes ! can you also explain your installation process !
Click to expand...
Click to collapse
First boot took about 1 min max. You have to be decrypted, flash rom, flash noverity (I flashed v3) - and you should be good.
---------- Post added at 11:06 AM ---------- Previous post was at 11:00 AM ----------
korm85 said:
i did what you wrote,
now swiping doesn't do anything
Click to expand...
Click to collapse
Well, it's definitely working for me tho, be sure to give it permissions.
Also, don't know if it matters, but I've searched for "swipe" in settings, and got in "Swipe fingerprints for notifications" menu, which is (weirldy) not available in "Gestures", there was no toggle there, tho, just instructions video. Maybe just entering that menu enabled that, try it out.
@Sabissimo did you update your firmware to 5.1.5 ? and have you installed vendor partition data ?
tids2k said:
@Sabissimo did you update your firmware to 5.1.5 ? and have you installed vendor partition data ?
Click to expand...
Click to collapse
I was on OB15, so whatever firmware it uses - I have it And had vendor of OB15, but I don't think that vendor matters, since this is not treble rom, and doesn't use /vendor, it uses /system/vendor
Sabissimo said:
Well, it's definitely working for me tho, be sure to give it permissions.
Also, don't know if it matters, but I've searched for "swipe" in settings, and got in "Swipe fingerprints for notifications" menu, which is (weirldy) not available in "Gestures", there was no toggle there, tho, just instructions video. Maybe just entering that menu enabled that, try it out.
Click to expand...
Click to collapse
Well... the dev said that the ROM doesnt have that function, but how can you enable ? I also follow your steps and give them permission then reboot again, but nothing happen.
Step-by-step of what I did:
1. Wiped everything except internal storage
2. Flashed ROM
3. Flashed no-verity v3
4. Rebooted, it rebooted twice, then started booting up with google animation
5. Noticed that fingerprint is working as cursor, went to settings, searched for "swipe", entered that menu, there's no toggle there
6. Pasted gf_input.kl in /system/usr/keylayout, gave it 755 permissions
7. Rebooted and everything is working!
Try doing it in the same sequence (First try to to enter swipe menu before pasting gf_input.kl, then paste it), maybe that did the trick.
Sabissimo said:
Step-by-step of what I did:
1. Wiped everything except internal storage
2. Flashed ROM
3. Flashed no-verity v3
4. Rebooted, it rebooted twice, then started booting up with google animation
5. Noticed that fingerprint is working as cursor, went to settings, searched for "swipe", entered that menu, there's no toggle there
6. Pasted gf_input.kl in /system/usr/keylayout, gave it 755 permissions
7. Rebooted and everything is working!
Try doing it in the same sequence (First try to to enter swipe menu before pasting gf_input.kl, then paste it), maybe that did the trick.
Click to expand...
Click to collapse
Confirm this was the exact process I followed and works like a charm. Just need a couple of days with it to test battery life.
just have one thing to say thankyou so much and this rom is just smooth
For anyone that wants to flash this ROM, don't worry about your firmware. This ROM's .zip file contains a firmware ALREADY so it will flash the necessary firmware itself!
Sabissimo said:
Step-by-step of what I did:
1. Wiped everything except internal storage
2. Flashed ROM
3. Flashed no-verity v3
4. Rebooted, it rebooted twice, then started booting up with google animation
5. Noticed that fingerprint is working as cursor, went to settings, searched for "swipe", entered that menu, there's no toggle there
6. Pasted gf_input.kl in /system/usr/keylayout, gave it 755 permissions
7. Rebooted and everything is working!
Try doing it in the same sequence (First try to to enter swipe menu before pasting gf_input.kl, then paste it), maybe that did the trick.
Click to expand...
Click to collapse
where is this gf_input.kl?? why should i do this for the pill gestures?