Related
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.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What are UNOFFICIAL builds? A version of CyanogenMod not compiled by CyanogenMod's build servers and may contain code not yet committed to the repository. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Downloads
ROM:http://d-h.st/myfiles?fld_id=28773#files (just look for the one with the newest date on it
Gapps:http://forum.xda-developers.com/showthread.php?t=2012857
use what ever gapps you want but i personally use these ones since its just the basic stuff and its art compatible
Installation
- First time flashing CM11 to your Galaxy S (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM7/CM9?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM10/10.1?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
You will finally see a "set_metadata_recursive" status 7 error. That is normal.
Reboot back into recovery (the reboot is required)
Install the ROM again from internal sdcard using ClockworkMod Recovery
Optionally restore /data from Nandroid Backup (the update will wipe your /data)
Optionally install the Google Addon
- Upgrading from CM10.2?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from another build of CM11?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Warning: You may get set_metadata_recursive related-errors during install if you're using a custom kernel without SELinux support. In that case, revert to the stock kernel before continuing or follow the instruction for upgrading from CM10.1.
Note: The partition layout of CM11 is the same as CM10.2.
Known Issues
Please do not report bugs if it is already listen in the list of known issues
No access to TV-Out menu
Layout issues in lockscreen
Menu soft-buttons appearing where they shouldn't
Some CyanogenMod features a missing - please do not file bug reports for those.
Privacy guard icon not disappearing when exited app
Broken layout of quick message popup (SMS)
Cannot set value via custom brightness "Edit" menu
If back button is pressed during incoming call, you can't answer the call.
FC when changing image sharpness
Pressing "menu" unlocks swipe lockscreen
Browser: FC in incognito mode and Advanced -> Website settings)
Quick Access Ribbon gone when switching from Quick Settings
2G/3G toggle does not work
Cannot flash CM10.2 from recovery (workaround: restore a 10.2 backup or flash a 10.2 kernel before flashing)
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
FAQ
Why is there no transparent status bar/lockscreen widget/"OK Google"?
Those features have been disabled by Google for low RAM device in order to save RAM. You can try enabling it by removing "ro.config.low_ram=true" from /system/build.prop, however, it is not an officially supported setup.
Is there a changelog for gapps?
I did not create the packages and do not know. (Please don't annoy the original developer of the packages by asking him either.)
Does this ROM support FM radio?
I've checked and the new FM API in CM is not really compatible with our device without heavy modification. Applications using the new API expect to be able to read the FM input as it if were another stream, but FM on our device only does pass-through from FM receiver to speaker/headset, which causes certain functionalities to not work such as volume control. Maybe one can modify the audio routing table in the kernel to have it behave like the API expected, but I'm not really interested in investing time to do that.
TL;DR: No built-in FM radio except if someone else does it and submits a patch.
the above gapps are what i personally use you can use what ever ones you would like though
Thanks to
pawtip
CM team
FaultException
Kasper_h
anyone else who i forgot pm me and il add you
Is the problem with the phone speaker solved? On receiving calls, speaker didn't work..
is it fixed??
n205des said:
Is the problem with the phone speaker solved? On receiving calls, speaker didn't work..
is it fixed??
Click to expand...
Click to collapse
Deleted
Could you expain what you did to create this ROM? Did you do straight what was said in the Cyanogenmod building instructions for captivatemtd?
ankamar92 said:
Could you expain what you did to create this ROM? Did you do straight what was said in the Cyanogenmod building instructions for captivatemtd?
Click to expand...
Click to collapse
Basicly
New build soon with some kernel modifications to make it even smoother
All the post is C&P from Pawitp i9000 post lol (except links and credits)
But, whatever, I'll download the rom right now, and will try it later..
BTW, gapps links doesn't work.
And..
cannondaleV2000 said:
Deleted
Click to expand...
Click to collapse
What do you mean with "DELETED"? Fixed?
Thanks for your work ^^
When i installed this, all i got was the little cyanogen robot with the rotating arrow, that lasted for about an hour until i got frustrated with it and just went back to my old rom, any ideas on why this is happening?
Boots fine for me. Did you dirty flash or flash anything else with it?
And yeah it is a c&p from pawtip because it is completely stock cm for now at least
Sent from my SGH-I897 using xda app-developers app
Link gapp error ,file not found
cannondaleV2000 said:
Boots fine for me. Did you dirty flash or flash anything else with it?
And yeah it is a c&p from pawtip because it is completely stock cm for now at least
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Ok, ok, but that not answer my question, the problem with the speaker on receiving call, is fixed?
You answered that to another user --> "Deleted", Deleted == Fixed?
Thanks.
should be. i have not run into the isue so far been running since lastnight.
new build up. syncd with cm sources and tweeked kernel to give more usable available ram
cannondaleV2000 said:
new build up. syncd with cm sources and tweeked kernel to give more usable available ram
Click to expand...
Click to collapse
I think the link you posted, isn't for public, when entering, I can't see anything, only you can see the files on the folder.
OK will fix
Sent from my SGH-I897 using xda app-developers app
Sorry guys I just realized I uploaded the wrong file. Il fix it tomorrow and post a new link
ManaSV93 said:
I think the link you posted, isn't for public, when entering, I can't see anything, only you can see the files on the folder.
Click to expand...
Click to collapse
He linked the myfile link in d-h its goes to my own uploaded file when I logged on in dev- host
Make direct link bro
mohammad.afaneh said:
He linked the myfile link in d-h its goes to my own uploaded file when I logged on in dev- host
Make direct link bro
Click to expand...
Click to collapse
Yep noticed that will fix after school. Because I also uploaded the wrong file top
Downloaded first version, and, have to say that the performance is awesome.
Ram: constant 170 mb free, using BBM, and listening some music.
Web Browser performance was better on CM 10.1
And, with all the KK builds I have tried on the cappy, Every time I turn ON the phone, When OS is completely loaded, I get a message, of invalid IMEI, and that, I can have some problems..
How can I solve this? If I go back to stock rom, and then to CM 10.1, I don't have any problem with this, but when I update to CM 11, I have this error, and don't know wich errors can this give me on future.
Any screenshot ?
ULTRA Kernel installer is an AIO kernel tool that uses AROMA installer (what's that?).
This tool is capable to backup, install ULTRA kernel, and restore a kernel backup.
Make a Nandroid backup before using it, to stay safe.
ULTRA kernel features
+ OC support
+ Lot of governors and schedulers added:
-- New governors --
Hotplug
ZZmove
OndemandQ
LulzactiveQ
Smartassv2
InteractiveQ
-- New schedulers --
BFQ
ROW
ZEN
VR
+ PhilZ Recovery (what's that?). Thanks Phil3759!
DOWNLOAD
Android File Host
Dev-Host
Thanks @iiD4x for the idea and logo. And @AndyMcMars!, he spent lot of time on this too.
XDA:DevDB Information
ULTRA Kernel Installer, Kernel for the Samsung Galaxy S Advance I9070
Contributors
t4n017, cocafe, Phil3759, TeamCanjica, TeamNova, AndyMcMars, iiD4x
Kernel Special Features:
Version Information
Status: Beta
Created 2014-03-18
Last Updated 2014-05-28
Changelog
CHANGELOG
20140401 (v4.01)
- Deleted all previous kernels varieties
- Added an all-in-one kernel (called ULTRA)
- Now the installer is compatible with CM-11 users too (choose the right option when prompted)
- UKSM is back (KSM --> UKSM) [testing]
- UKSM now disabled by default
- Added UKSM toggle in Galaxy S Advance settings (advance tab)
- PhilZ recovery updated (v6.25.4)
---x---x---x---
20140328 (v3.28)
- KSM is back (UKSM --> KSM)
- Fixed Aroma FM copy process
- PhilZ recovery updated (v6.24.6)
---x---x---x---
20140325 (v3.25)
- Kernel sources update (lot of performance improvements!)
- PhilZ recovery updated (v6.23.3)
- Script a bit more clean
---x---x---x---
20140323 (v3.23)
- Fixed modules install/restore process. (NOW REALLY!)
---x---x---x---
20140320
- Fixed modules restore process.
---x---x---x---
20140319C
- Now the script will also backup modules files (thanks @darcik for the suggestion).
---x---x---x---
20140319B
- All kernels were rebuilt from scratch
- No more Wi-Fi bug!
- Added Smartassv2, InteractiveQ and Interactive to PLUS (and therefore PLUS+OC) kernel.
---x---x---x---
20140319A
- Temporary deleted PLUS and PLUS+OC due to Wi-Fi bug.
---x---x---x---
20140318
- Initial build
---x---x---x---
Reserved
Very good, I waiting PhilZ Kernel a long time xD
Thank you!
Well, after lot of test I think the Wi-Fi bug is only happening on PLUS and, therefore, PLUS+OC kernel.
It's weird because I didn't touch anything related to Wi-Fi.
I apologize to those who installed them, and further to those who tried the alternative installation method without result.
I'll built them again from scratch and report back.
"I told you..." :victory:
Is the OC kernel stable? Is it possible to under volt?
fbs said:
"I told you..." :victory:
Click to expand...
Click to collapse
Yes, but lot of user reported PLUS was working fine. Maybe they thought they were installing PLUS but instead, they were restoring the default kernel backup.
marlock87 said:
Is the OC kernel stable? Is it possible to under volt?
Click to expand...
Click to collapse
Not all the Advances can handle the same freq, you should try if you can OC without reboots.
It should be, but I didn't tested UV. If you do, please report
Philz Kernel working fine in RR 5.0.5
i flashed philz kernel on cm11 05/03 build(dalvik runtime).it installed fine but after restarting i always get process.android,phone has stopped.even factory reset including wipe dalvik cache wouldnt resolve the issue.flashing the beanstalk rom since i wanted to try it out anyway.the recovery work fine though including power off(the feature which is actually why i installed it in first place).anyways thanks bringing the kernel for our device and hoping to see more development:good:
wingryder said:
i flashed philz kernel on cm11 05/03 build(dalvik runtime).it installed fine but after restarting i always get process.android,phone has stopped.even factory reset including wipe dalvik cache wouldnt resolve the issue.flashing the beanstalk rom since i wanted to try it out anyway.the recovery work fine though including power off(the feature which is actually why i installed it in first place).anyways thanks bringing the kernel for our device and hoping to see more development:good:
Click to expand...
Click to collapse
for now , PhilZ wont work on CM ..
I get the "process.android,phone has stopped" error after installing (wipe cache, wipe, dalvik, install zip), and I used the DEFAULT kernel. Why?
I use Carbon KitKat rom,
So happy to see this topic, thanks for posting!
GREAT NEWS!
I've built all the kernels from scratch, now Wi-Fi bug is fixed! Please test and report.
Check changelog for more changes.
Are these kernels supposed to work with the i9070-P version??? Just to be sure...
elementbt said:
Are these kernels supposed to work with the i9070-P version??? Just to be sure...
Click to expand...
Click to collapse
Yes ofc, when you flash a ROM (like RR) you're using the DEFAULT kernel posted here.
Just installed DEFAULT KERNEL and I get the "process.android,phone has stopped" error.
Nothing helped.
CM 11 by Macław.
darcik said:
Just installed DEFAULT KERNEL and I get the "process.android,phone has stopped" error.
Nothing helped.
CM 11 by Macław.
Click to expand...
Click to collapse
It seems that the kernels aren't working fine on CM 11. I don't know why, but I'll ask TeamCanjica for help.
Tnx for fast answer.
Btw, your script is making backup of kernel and coping new modules to system/modules folder,
but if is needed restore old kernel, modules files are new and is problem because they are not working with old kernel
Good, that I did myself copy of these files.
darcik said:
Tnx for fast answer.
Btw, your script is making backup of kernel and coping new modules to system/modules folder,
but if is needed restore old kernel, modules files are new and is problem because they are not working with old kernel
Good, that I did myself copy of these files.
Click to expand...
Click to collapse
Thanks for report bro!, I forgot the modules backup. Anyway you can use DEFAULT kernel to restore them.
But I'll edit the script to backup those files and I'll re-upload them.
Really thank you!
{
"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.
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.2.0-0:
-Allow restoring adb backups in the TWRP GUI (bigbiff)
-Fix gzip backup error in adb backups (bigbiff)
-Fix a bug in TWRP’s backup routines that occasionally corrupted backup files (nkk71)
-Better support for installing Android 8.0 based zips due to legacy props (nkk71)
-Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
-Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
-Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
-v2 fstab support (Dees_Troy)
-Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
-Various other minor bugfixes and tweaks
CHANGELOG for 3.1.1-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
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!
DOWNLOAD:
TWRP CANCRO
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
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 here
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
[RECOVERY][cancro] TWRP 3.1.0-0 touch recovery, Kernel for the Xiaomi Mi 3
Contributors
Shivam Kumar Jha, Dees_Troy, linuxxx
Source Code: Recovery, Device, Vendor
Kernel Special Features:
Version Information
Status: Testing
Created 2017-03-11
Last Updated 2017-03-11
Changelog:
20171026: Initial build 3.1.1.0
20171203: Updated to 3.2.0.0
20171210: Updated to 3.2.1.0
20180228: based on new MM kernel xiaomi released last november
20180304: attempt to fix battery drop on reboot
20180305: Added exfat & sdfat support in kernel
Great
look ss
wht thts mean ?
eddy_nugroz said:
Great
look ss
wht thts mean ?
Click to expand...
Click to collapse
Size of /data partition only, excluding your internal sd-card
Shivam Kumar Jha said:
Size of /data partition only, excluding your internal sd-card
Click to expand...
Click to collapse
ah ok
btw this ur build ? suport aroma? I think we need aroma suport for recovery
last version of ur build have graphical issue on aroma
eddy_nugroz said:
ah ok
btw this ur build ? suport aroma? I think we need aroma suport for recovery
last version of ur build have graphical issu on aroma
Click to expand...
Click to collapse
Ofcourse this is my build. AROMA support should already be there
This is the first time i'm sharing my TWRP build so I dont know what you are saying about the last build
Shivam Kumar Jha said:
Ofcourse this is my build. AROMA support should already be there
This is the first time i'm sharing my TWRP build so I dont know what you are saying about the last build
Click to expand...
Click to collapse
im try last aroma file manager 2.00b7 auto reboot to system
i mean this twrp-3.0.3.0-shivam-cancro.img
thnx
thanks but aroma doesn't work,performing a reboot.
Any bugs?? Shahan_mik3's twrp has flashing bug. I hope that bug is not present in this one. Like always thanks shivam
Sleep time fixed or not(
eddy_nugroz said:
im try last aroma file manager 2.00b7 auto reboot to system
i mean this twrp-3.0.3.0-shivam-cancro.img
Click to expand...
Click to collapse
LKc丶 said:
thanks but aroma doesn't work,performing a reboot.
Click to expand...
Click to collapse
vishal24387 said:
Any bugs?? Shahan_mik3's twrp has flashing bug. I hope that bug is not present in this one. Like always thanks shivam
Click to expand...
Click to collapse
If you see user comments here aroma installer is not working for many devices since 3.0.3.0 update. Hence my guess is problem lies in TWRP source not in device sources used. I'm not sure about Anykernel script either.
hanuraiga said:
Sleep time fixed or not(
Click to expand...
Click to collapse
Actually its a feature not a bug, I have used flags to not allow screen to be turned off (TW_NO_SCREEN_TIMEOUT := true & TW_NO_SCREEN_BLANK := true) .
Shivam Kumar Jha said:
If you see user comments here aroma installer is not working for many devices since 3.0.3.0 update. Hence my guess is problem lies in TWRP source not in device sources used. I'm not sure about Anykernel script either.
Actually its a feature, I have used flags to not allow screen to be turned off (TW_NO_SCREEN_TIMEOUT := true & TW_NO_SCREEN_BLANK := true) .
Click to expand...
Click to collapse
So i can edit that vakue via TWRP's terminal??
hanuraiga said:
So i can edit that vakue via TWRP's terminal??
Click to expand...
Click to collapse
Did a build for you with screen timeout support twrp-3.1.0.0-cancro-shivam.img
Shivam Kumar Jha said:
Did a build for you with screen timeout support twrp-3.1.0.0-cancro-shivam.img
Click to expand...
Click to collapse
Woow.. thank's a lot it's working...
vishal24387 said:
Any bugs?? Shahan_mik3's twrp has flashing bug. I hope that bug is not present in this one. Like always thanks shivam
Click to expand...
Click to collapse
Like always there is a thanks button
For me kernel flash is working but can't boot....
Always going into boot loop.....
But same kernel flashing working with 3.0.2-0....
Don't know what's the problem..
Does this support f2fs format ? Is there any ROM that can be flashed this way ?
Already flash but not yet try to flash any ROM
Thank You for your support for our device
somebody provided a potential fix for the aroma issue https://github.com/blastagator/andr...mmit/368276d38caad7d5f64f324c39bb53e8cfee0f5a
source: https://disqus.com/home/discussion/...ckup_ab_ota_zips_and_more/#comment-3199258713
EDIT: btw, the unofficial TWRP 3.0.3.0 by @Shahan_mik3 did not have the Aroma reboot problem, but it had graphical issue where the Aroma installer background becomes transparent. While the official TWRP 3.0.2.0 will result in a reboot when using Aroma installer.