Database Users

[ROM - 1.2] CyanogenMod 7 nightlies for the GTab [Updated: 07-27-2011]

As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.43 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified):
Latest build: Build 07262011 (Changelog)
2) Modified version of the ROM: CM7Tab build 07272011
Changes in modified version
1) replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2) vold.fstab is setup as sdcard for internal storage & emmc for external card
3) using pershoot's 2.6.32.43 GB kernel for 1.2 bootloader (For more info, check his blog.
4) Read_ahead_kd increased from 128 to 2048.
5) Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6) Replaced Camera libs & apk to stop the 8-bit pixelling.
7) Changed values for lowmemorykiller (07102011).
8- Increased dalvik.vm.heapsize to 64m (07102011)
9) Set some values to improve video playback (07272011)
RC1 version of the rom with changes: 7.1.0 RC1 with Pershoot 42 kernel
(Sorry if this is short but I will improve the thread as it goes)
To-do list:
1) remove some apks (such as Rom manager) & create a removed apks folder.
2) change the EMMC to Sdcard2
If you have suggestions/ideas, do not hesitate to share them.

reserved for future use

AS WE ARE REORGANIZING THE GTABLET FORUM - ALL ROMS/KERNELS/ETC WILL HAVE THEIR Q&A POSTS MOVED TO THE Q&A SECTION.
THE Q&A LOCATION FOR THIS ROM IS HERE
Thanks.

[WIP] Open Bootloader Development for Archos Gen8

Hey geeks,
you might know my hardware hacking thread already:
http://forum.xda-developers.com/showthread.php?t=1199450
Some time ago i started thinking about starting with an open bootloader for Archos Gen8.
So i started from scratch and made use of external boot mode to completely start from external MicroSD and leave the internal memory alone.
Remark: This is a geek project, there's no GUI or something. So don't expect anything useful right now.
At the moment you'll need some hardware hacking, because you'll need a serial console over uart3.
Unfortunately you'll also need a dirty hack to power up the MicroSD permanently.
Don't hesitate to ask for details about it.
So this is for the weird ones out there...
Right now there's work in progress, because stock kernel stucks at some point in the boot process.
Maybe there's some setup missing in the bootcode (it's very basic at the moment) or stock kernel relies heavily on avboot at some point.
I will work on this issue whenever i'll find some time.
Anyway it might be still an interesting project for at least a very few of you, so here's the source code:
- x-loader-archos
- u-boot-2011.09-archos
As pointed out the Archos implementation is very basic at the moment, but the code itself works very well and had been tested on A101IT Gen8.
To further devices, e.g. A70S Gen8, the machine id had to be included in the board file, the rest of the setup in early stage should be very similar.
The code bases:
- x-loader (https://gitorious.org/x-loader/x-loader)
- u-boot (taken from this archive: http://www.technexion.com/images/downloads/ARM_CPU_Modules/TDM-3730/linux-2.6.32-tdm3730.tar.xz)
I'd like to switch to official u-boot release 2011.09 as a base soon.
To start playing with it:
- open your case and start hacking, to get serial console working
- tweak the hardware to power the MicroSD slot permanently
- create a bootable MicroSD for OMAP systems
- place the binaries on your card
- insert the card and use vitalifs kernel module to reboot your device in external bootmode
Please refer to these posts from vitalif (thanks a lot for contributing!!!):
http://forum.xda-developers.com/showpost.php?p=22719203&postcount=105
http://forum.xda-developers.com/showpost.php?p=22765441&postcount=108
You might start digging in the source code and create your own loader:
- use a linux machine with a recent distribution
- setup a cross environment with ARM cross compiler suitable for ARMV7
- extract the sources to directory of your choice
- to compile x-load:
Code:
cd ./x-loader-archos
make archos_config
make
- to compile u-boot-2011.09-archos:
Code:
cd ./u-boot-2011.09-archos
make a101it_config
make
It might be required to tweak the top-level Makefiles to point at your toolchain.
I used my ready to work toolchain (for 32-bit linux only) here:
http://forum.xda-developers.com/showthread.php?t=1328027
Unfortunately i haven't found some time to create a project page at gitorious,
but hopefully i'll manage to do so in the next weeks...
I know this is a very very special project, but anyway if there's some interest, this might lead to something useful in the end.
If the bootcode is working very nice some day, it might also be possible to replace stock loader, but that's fiction yet.
You might ask what for...
I say... it's just for fun!
cheers,
scholbert

Boot console output... so far
Hey,
it had been posted already but her again for completeness...
The console log on UART3 starting custom kernel configured with stock config:
Code:
Texas Instruments X-Loader 1.5.1 (Mar 26 2012 - 20:41:11)
Found 0256 MB
Archos Gen8
Reading boot sector
Loading u-boot.bin from mmc
Done!
U-Boot 2011.09 (Mar 23 2012 - 18:53:39)
OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
Archos 101IT Gen8 + LPDDR/MMC
I2C: ready
DRAM: 256 MiB
MMC: OMAP SD/MMC: 0
Using default environment
In: serial
Out: serial
Err: serial
Die ID #144800029ff800000160a4bb18027009
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
2987000 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-2.6.29-omap1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2986936 Bytes = 2.8 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux.............................................................
................................................................................
..................................................... done, booting the kernel.
<6>Initializing cgroup subsys cpu
<5>Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.1 (GCC) ) #1
PREEMPT Thu Mar 22 23:59:34 CET 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Archos A101IT board
fixup_archos: [console=ttyS2,115200n8 androidboot.console=ttyGS0 init=/linuxrc d
ebug omapdss.debug=0 vram=4915200 omapfb.vram=0:4915200 omapfb.debug=0 mmc_block
.split=0.0001:512M]
Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 65536
<7>free_area_init_node: node 0, pgdat c05fd368, node_mem_map c06a5000
<7> Normal zone: 512 pages used for memmap
<7> Normal zone: 0 pages reserved
<7> Normal zone: 65024 pages, LIFO batch:15
<4>L2 CACHE is enabled in bootloader
<6>OMAP3630 ES1.2
<6>DIE ID: 144800029FF800000160A4BB18027009
<6>FEATURE_STATUS: 00000c00
<6>SRAM: Mapped pa 0x40200000 to va 0xfc800000 size: 0x100000
<6>Reserving 4915200 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
<5>Kernel command line: console=ttyS2,115200n8 androidboot.console=ttyGS0 init=/
linuxrc debug omapdss.debug=0 vram=4915200 omapfb.vram=0:4915200 omapfb.debug=0
mmc_block.split=0.0001:512M
<3>Unknown boot option `androidboot.console=ttyGS0': ignoring
<3>Unknown boot option `omapdss.debug=0': ignoring
<6>Clocking rate (Crystal/DPLL/ARM core): 26.0/332/600 MHz
BTW, i extracted the function from Archos loader setup up PLL and MPU stuff.
Need some time to extract the stock setup for PLL at early stage.
Maybe this will give some answers.
One of my next plans is, to build some kind of bare bone kernel (console only), which may be used for recovery and debug purpose.
Maybe this gives it a kick and things start up to a login shell
TBC
Have fun!
scholbert

One of my next plans is, to build some kind of bare bone kernel (console only), which may be used for recovery and debug purpose.
Maybe this gives it a kick and things start up to a login shell.
Click to expand...
Click to collapse
Seems like an internal monologue... but i like to point out that i stopped this project for a while.
So don't expect anything like a brick recovery tool or similar.
If others will join in it might be possible that it would led to something,
but as long as no one even starts hacking the hardware this is just for me...
Happy days!
scholbert

scholbert said:
Seems like an internal monologue... but i like to point out that i stopped this project for a while.
So don't expect anything like a brick recovery tool or similar.
If others will join in it might be possible that it would led to something,
but as long as no one even starts hacking the hardware this is just for me...
Happy days!
scholbert
Click to expand...
Click to collapse
Shame you stopped your efforts for now, I always followed your posts with much interest. However I can understand it is frustrating being on your own.
Thanks for what you did this far and for posting your info .
divx118

Sorry to read that, this was a very very interesting reading.
But I don't have the knowledge to make the necessary hardware hack, and above all, my wife would kill me if she saw me opening the tab
Thanks again for all that amazing information scholbert

Hey,
first off all thanks for your interest and your replies
Some words on your comments though...
divx118 said:
Shame you stopped your efforts for now, I always followed your posts with much interest. However I can understand it is frustrating being on your own.
Click to expand...
Click to collapse
I did not want to sound frustrated, because i'm not.
All i do with the device and all that hacking stuff is fun and mostly for educational purpose
Maybe i'll continue working with this stuff, but for now i wanted to point out to not expect too much.
Some guys out there, bricked their devices and were looking for a solution.
That's why i wrote it down.
Basically it should be possible to recover bricks by using external boot procedure, but it's still far from a simple solution.
grim-a101 said:
Sorry to read that, this was a very very interesting reading.
But I don't have the knowledge to make the necessary hardware hack, and above all, my wife would kill me if she saw me opening the tab
Click to expand...
Click to collapse
Yeah that's a good point, the barrier for this kind of hacking is little high.
Unfortunately you'll have to tweak the hardware, to gain access to the serial debugging port and cheat the power management of the MicroSD slot.
Most of you simply want to use the device and do some less harder tweaks at system level.
Anyway, there are some other possibilities as well (e.g. using USB and TI Flash) to access the platform. Maybe i'll do some research here as well.
Thanks again for appreciation!!!
Regards,
scholbert

[Start/Here] Hisense Sero 7 Pro Development Home Base

Developers, start here and add a response for your individual ROMs, etc. with different versions listed and download links and any explanatory notes you deem valuable. If there is a particular development thread, list and link it. Each developer can have his or her own reply message that only they will be able to edit and update with new versions and links. They will be able to remove versions if they prefer, link both stable and experimental/test versions. Let's hope for a message from xboxexpert, dolorespark (dopa 2.0 & AOSP), RandomBlame (taktiK), davepmer (CM11), Bdadd34(gummy ROM), and jerbear294 (PAC-ROM) and anyone else I forgot to mention or am unaware of. You can use the simple guide below or use any format to your liking. Thanks to all the developers.
Note to All Non-developers/Regular Users/Sero 7 Pro Owners: Please don't add any responses asking questions, stating opinions, detailing experiences, etc. Go to the individual development threads for that purpose. We want to keep this a simple thread pointing to downloads.
Developer Name
Recoveries
Name/Designation download Recovery-Flashable? Explication
. . .
Kernels
Name/Designation Download Explication
. . .
ROMs
ROM name
Development thread
Version Download Explication

bdadd34 roms/kernels
I am in the process of building various KitKat roms from source with deloresparks aosp repos and posting them in one thread for people to use if they want. But more importantly I would like to help anyone who wants to build and support one or more of these roms with there own thread. I will link to this thread as soon as I make it. In the meantime here is a link to Gummy and a couple new Roms I built today.
GummyKang thread--http://forum.xda-developers.com/showthread.php?t=2670350
Download only...Pics Coming
KANG###LiquidSmooth..Blood.. LS-KK-Blood-v3.0-UNOFFICIAL-2014-03-27-m470.zip - 152.28 MB
KANG###Carbon... CARBON-KK-UNOFFICIAL-20140326-1636-m470.zip - 156.51 MB

davepmer Recovery and CM-11 Builds
TWRP 2.8.1.0 20141026-F2FS selinux enabled using F2FS data and cache
https://drive.google.com/uc?export=download&id=0BwDeRepAacdbc1g5ZXF2UUVEaW8
TWRP 2.8.0.0 20141015-F2FS selinux enabled with F2FS support
The usual I am not responsible if you flash this and something goes wrong
https://drive.google.com/uc?export=download&id=0B8wq9a7FIvh9RXQ0OXFwOVpNaVk
TWRP 2.8.0.0 20141007-F2FS selinux enabled with F2FS support
The usual I am not responsible if you flash this and something goes wrong
https://drive.google.com/uc?export=download&id=0B8wq9a7FIvh9NHNadUlOZ2xyU3c
TWRP 2.8.1.0 20141026-EXT4 selinux enabled using EXT4 data and cache
https://drive.google.com/uc?export=download&id=0BwDeRepAacdbcW01NW5IM3dtYmM
TWRP 2.8.0.0 20141015-EXT4 selinux enabled using EXT4 data and cache
https://drive.google.com/uc?export=download&id=0B8wq9a7FIvh9S2tuQjhncHVBcm8
Philz-touch-6.50.6 sero 7 pro selinux recovery 20140720
https://drive.google.com/uc?export=download&id=0B2ZiR-2Tn5BdVWhYOFRtSGJUTEU
Philz-touch-6.48.5 sero 7 pro selinux recovery 20140702
https://drive.google.com/uc?export=download&id=0B2ZiR-2Tn5BdblZGdG1PYjh5ZTQ
cm-11 M11 20141015 OC OTG EXT4
https://drive.google.com/file/d/0B8wq9a7FIvh9RnB2S2p0YUY2OW8/view?usp=sharing
cm-11.0 M10.909OTG 20140909Least I think M10 android 4.4.4 USBOTG thumb support EXT4 version
https://drive.google.com/uc?export=download&id=0B2ZiR-2Tn5BdUGF0SGUxdlEwSFk
cm-11.0 M9.729OTG 20140729 Least I think M9 android 4.4.4 USBOTG thumb support
https://drive.google.com/uc?export=download&id=0B2ZiR-2Tn5BdcGRBdlNIVEd0M1U
CM-11.0 cm-11.0 M9.729OTG Overclocked version 20140729 Least I think M9 android 4.4.4 USBOTG thumb support
https://drive.google.com/uc?export=download&id=0B2ZiR-2Tn5BdWm15ZEw5TTE1UTQ
cm-11.0 M8.12OTG 20140712 android 4.4.4 USB-OTG Thumb Drive support. Experimental but seems to work with an NTFS formated thumb drive.
Has Overclocked Kernel Best if clean data wipe
https://drive.google.com/uc?export=download&id=0B2ZiR-2Tn5BdelNfYWZ5M2o5VXc
to Remove OverClock tye a no wipe flash with https://drive.google.com/uc?export=download&id=0B2ZiR-2Tn5BdREwwNDVLMWl0OWc
CM-11.0-NIghtly (EXPERIMENTAL) 20140715-7.15OTG Best if clean data wipe. Also I tried to fix the USB/SDCARD unmount issue.
https://drive.google.com/uc?export=download&id=0B2ZiR-2Tn5BdbmpDaFBUR2JUaVk
to overclock do a no wipe flash with https://drive.google.com/uc?export=download&id=0B2ZiR-2Tn5BdMkNSLW9PMkRMUG8
Omnirom for sero 7 pro 20141016 best if clean data wipe. This build is overclocked. USB-OTG EXT
https://drive.google.com/uc?export=download&id=0BwDeRepAacdbRktVRVQxcFR1TGs
Omnirom for sero 7 pro 20140823 best if clean data wipe. This build is overclocked. USB-OTG EXT4
https://drive.google.com/uc?export=download&id=0B2ZiR-2Tn5Bdb2s2cFV4ZllodFE
Omnirom for sero 7 pro 20140809 best if clean data wipe. This build is overclocked. USB-OTG
https://drive.google.com/uc?export=download&id=0B2ZiR-2Tn5Bdc05CNnp3NDVSVlk
F2FS data and cache
WILL ERASE ALL DATA (internal sd card) suggest download both zips first. NOTE F2FS build is not compatible with the stock data and cache format.
To use first flash My newest TWRP F2FS recovery from above.
then boot into recovery, and goto wipe, advanced wipe, select data, then select repair or convert file system, change file system, select F2FS,
then do the same for cache. You must change both partitions data and cache from ext4 to f2fs
Only then will you be able to flash one of the F2FS builds.
Note, if you are flashing from one of my F2FS builds to another one of my F2FS builds you can just wipe data, system and cache as you would normally do.
To reutrn to an ext4 build you must boot into recovery and goto wipe, advanced wipe, select data, then select repair or convert file system,
change file system, select ext4 then do the same with cache you will erase the internal memory but you will be able to flash normal builds.
cm-11 stable 20141015 (M11) F2FS data and cache
https://drive.google.com/uc?export=download&id=0B8wq9a7FIvh9YjVzNHZ6V0g1Tzg
cm-11 stable 20141007 F2FS data and cache
https://drive.google.com/uc?export=download&id=0B8wq9a7FIvh9Qng2WXdoZ0QtVFE
Omnirom for sero 7 pro 20141016 F2FS data and cache
https://drive.google.com/uc?export=download&id=0BwDeRepAacdbUC1CdnU5UDF5Qk0
Omnirom for sero 7 pro 20140809 F2FS data and cache
https://drive.google.com/uc?export=download&id=0B2ZiR-2Tn5BdZVdMbGZqaE1IX2c
If you have a question about my builds just private message me.

DoPa ROMs
AOSP v5.0.2_r1 Beta v3 (US/UK/AU)
See this post for details and downloads.
AOSP v4.4.4_r2 DoPa v2.6 (US/UK/AU)
DoPa v2.6 is the first ROM to support all models of the Sero 7 Pro, regardless of where in the world they were sold. It starts with well-tested AOSP code and adds core functions where needed but skips the frills that are easy to add on. Among its features are extended filesystem support (i.e. NTFS, exFAT, and the most flexible F2FS support on any device), and enhanced USB-OTG support including charging the tablet while USB devices are attached (another DoPa original).
The package includes a handful of apps most people find useful (e.g. SuperSU, GravityBox, etc) but does not contain any of the Google apps. Because its focus is on stable, reliable performance, DoPa v2.6 unlikely to be the fastest Kitkat ROM available. However, those with a need for speed can use the integrated overclocking to give it a boost.
For more info and download links, see Sero 7 Pro (US) - AOSP 4.4.4_r2 DoPa v2.6
DoPa v4.2.1 v2.0
DoPa v2.0 is an enhanced version of the stock ROM based on Hisense's August, 2013 update (JB v4.2.1 - build P756.6.02.20). It debloats and roots the original, and adds a number of useful apps to the package. This version features a custom-built kernel based on Hisense's source that offers bug fixes and enhancements such as USB-OTG support. It is intended for those who want a stable, reliable ROM that adds a few features missing from the original.
See the Sero 7 Pro (US) dopa v2.0 thread for more details and download links.

PAC-ROM (Not supported anymore, I might release a bugfix eventually)
PAC is a combination of Paranoid Android, AOKP, and CyanogenMod, with a bit of flair.
Thread and download link:
http://forum.xda-developers.com/showthread.php?p=50836817
Keep in mind that the current build is unstable- however it's not my fault. PAC had a faulty commit or something. I'm trying to fix it but I might have to do a clean sync to get a working build- all of my recent builds since that commit have failed.
Ubuntu Touch
It's Ubuntu, except packed down onto an ARM device and a 7 inch screen. This is the high-end version of Ubuntu Touch, meaning we have the ability to hook up an external hard drive, a keyboard, and a mouse so the Sero doubles as a portable Ubuntu workstation.
Coming soon!

CM12 || Carbon || Beanstalk || PAC || Slim || Res Remix || CWM || TWRP || PhilZ
CM 12 :
Development thread: http://forum.xda-developers.com/android/development/rom-cyanogenmod-12-hisense-sero-7-pro-t2972413
Links restored!
--------------------------------------------------------------------------------------------------------------------
Carbon KitKat:
Development thread: http://forum.xda-developers.com/showthread.php?p=53474291
Links restored!
More Info on Carbon ROM: http://www.carbonrom.org/
--------------------------------------------------------------------------------------------------------------------
Misc Builds+
Resurrection Remix LP: http://meticulus.co.vu
PAC LP Alpha: http://meticulus.co.vu
SlimRoms LP Alpha: http://meticulus.co.vu
Beanstalk 4.4: http://meticulus.co.vu
--------------------------------------------------------------------------------------------------------------------
Recoveries
ClockworkMod 6.0.50 : http://meticulus.co.vu
TWRP 2.8.0.0: http://meticulus.co.vu
PhilZ Touch 6.57.5: http://meticulus.co.vu

Do not post questions in this thread.
Ask questions in the thread pointed to below:
If you have questions specific to a particular ROM, please go to the thread listed by the developer and ask it there.
I've started a thread for any general questions about the Sero 7 Pro. So, if you were about to post a question here, please ask it in the following thread (http://forum.xda-developers.com/show...php?p=52326773)

[GUIDE]+[FAQ] The ultimate answer to all your bacon flavored questions!

{
"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.

SailfishOS on Nexus 6 (shamu)

Disclaimer WARNING: "Modifying or replacing your device’s software may void your device’s warranty, lead to data loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with this project is responsible for your actions but yourself. Good luck."
What is SailfishOS? Sailfish OS is a GNU/Linux based mobile operating system, which is gesture-driven for the ease of use. It runs natively as glibc (not Android's bionic), has bash and busybox (not toolbox), uses Qt for UX, and other opensource projects in its middleware -- which basically is just like a Linux on your desktop, but needs Android drivers for some of device's hardware.
What works Screen (Display, touch) LED WLAN Audio Buttons (Volume and Power) Vibrate SMS USB (Charging and developer mode) What not works Camera Calling Mobile data Browser Jolla Store ( I've not put required files to mer's OBS system now.) What not tested Other stuffs _з」∠)_ How to install Flash latest stock firmware ( Image can be acquired from Google Developers website ）
Unlock bootloader and flash TWRP Recovery ( TWRP can be acquired from https://twrp.me/motorola/motorolanexus6.html )
Download required files:
lineage-14.1-20180324-nightly-shamu-signed.zip : From Google Drive | From my website sailfishos-shamu-release-2.2.0.zip : From Google Drive | From my website Enter TWRP, transfer downloaded zips to your Nexus 6 and flash them or use adb sideload Flash LineageOS first , and flash SailfishOS without reboot. (Since device encryption is required on Nexus 6's Android while SailfishOS cannot run on a encrypted /data )
Reboot and wait SailfishOS logo appears on your screen, follow the instructions to complete initial settings .
Well done

https://sailfishos.club/topic/152/sailfishos-on-nexus-6-shamu/2

I installed it so I could check it out and its very interesting if everything ends up working in a future release and it became capable of being a daily driver then I would use it to see how well it runs, Thanks for sharing !

This is wonderful to see. Sometime ago I believe there was Ubuntu touch in development for the Nexus 6, but ceased? This is great to see a new OS in development and will follow with great interest

Very nice, very pretty system but need to fix phone functions

Oh hey, you got as far as I did about. I didn't have enough time to polish things up though, and I just kinda lost steam on it all.
I never could figure out the call issue but I got most other things working. Here's my sources, if it helps!
https://github.com/Lyokanthrope/droid-config-shamu
https://github.com/Lyokanthrope/android_kernel_moto_shamu
https://github.com/Lyokanthrope/android_device_moto_shamu