Related
Hello everybody,
I created a tool - initially for the nexus 9 (flounder|flounder_lte) - that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
I enhanced that tool to make it work for nexus 6 (shamu) too.
Background
The Android CDD (Compatibility Definition Document) suggests that all devices SHOULD enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. FDE comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in the case of the nexus 6 (aka shamu) it's the CPU's task. Even though the nexus 6's CPU has 4 quite fast cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any measurements)
There is an ongoing discussion about this topic in cyanogenmod's gerrit for the nexus 9. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome.
Because performance is important to me and my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher)
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
Supported devices
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
v2 - Added Motorola Nexus 6 (shamu) support
v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
v4 - Added support for signed boot-images
v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
What do I need to make this work?
A supported device (Your nexus 6)
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A recovery that includes busybox (TWRP, CWM)
How do I use it?
Make a thorough, conservative backup of your data if there is any on your device
Go into your recovery (TWRP, CWM)
Flash fed_patcher-signed.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Screenshot
Scroll down to the attached thumbnails.
Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
Thank you for this!
I can easily extend support for more devices. Do you guys know of some that have forceencrypt enabled?
Excellent work.
Hello everybody,
I just released version 6!
In this release, FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
Enjoy
Edit: Confirmed as working for latest Chroma build. (9/18)
Can anyone confirm this working for Chroma? Truly don't want to deal with starting from scratch ...
Hello everybody,
just to let you guys know - I just checked the new marshmallow factory image for shamu (MRA58K) => FED-Patcher should work for this new image too.
Enjoy!
This worked perfect for me just flashed then formatted data and boom I'm unencrypted again thank you op
Hello everybody,
I just released v7!
FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
Enjoy!
gladiac said:
Hello everybody,
I just released v7!
FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
Enjoy!
Click to expand...
Click to collapse
This is incredible news! Using this alongside SuperSU, is R/W access accessible on the system partition? (build.prop mods)
spunks3 said:
This is incredible news! Using this alongside SuperSU, is R/W access accessible on the system partition? (build.prop mods)
Click to expand...
Click to collapse
Yes that should work!
//EDIT: No it does not. It keeps looping after installing SuperSU with the following error:
Code:
avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p29" ino=104419 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
Probably some selinux problem :/. I might dive into this later this week. Sorry.
//EDIT #2: Now that I think about it... Doesn't the SuperSU flashable ZIP take care of the needed policy rules so the error that I posted above does not happen? IMHO it is SuperSU's task to take care of these things.
I might have to retest with the actual SuperSU installer. I had used TWRP's SuperSU installer. Maybe that one is broken somehow...
//EDIT #3: Nope! Supersu definitely does not work. I just tried with BETA-SuperSU-v2.50.zip. The SELinux policy-set that comes with the stock marshmallow factory images lacks the necessary rules to enable SuperSU to work.
However, adding these rules is something FED-Patcher was not designed to do. IMHO the SuperSU flashable ZIP should take care of this.
FYI: Nexus 6 is a QUAD core. Not just 2.
doitright said:
FYI: Nexus 6 is a QUAD core. Not just 2.
Click to expand...
Click to collapse
Thanks, I just fixed it. Shame on me.
Thanks for your work. Please can you take moment to answer my question? I am using an Android 6 ROM, however, due to my original configuration, device encryption is active.
I will try as listed below, please critique, I am not sure if I need to wipe the phone after backing up?
1. Back up device
2. Wipe device (data, internal storage and system.)
3. Flash FED patcher
4. Flash suitable Andriod 6 boot loader and radio
5. Flash suitable rom (with encryption disabled)
Thanks
finesse said:
Thanks for your work. Please can you take moment to answer my question? I am using an Android 6 ROM, however, due to my original configuration, device encryption is active.
I will try as listed below, please critique, I am not sure if I need to wipe the phone after backing up?
1. Back up device
2. Wipe device (data, internal storage and system.)
3. Flash FED patcher
4. Flash suitable Andriod 6 boot loader and radio
5. Flash suitable rom (with encryption disabled)
Thanks
Click to expand...
Click to collapse
Hi @finesse,
FED patcher must be run after installing a rom in order to disable the forced encryption flag. If the rom does not have forced encryption enabled (pretty common on non-stock and non-cm12.1 roms) you do not need to run FED patcher at all. Background: What FED-Patcher does is that it just takes the boot-partition of the currently installed rom and modifies it.
Wiping (in TWRP: "Wipe" - "Factory reset") is essential after backing up if the phone is currently encrypted. Sadly, you cannot simply just disable the encryption. Only formatting the partition (=wiping) will get rid of it.
I hope I could help .
Hey everybody!
This project has been moved to HERE! Please post your problems, success stories and so on there from now on.
Cheers, gladiac
Will this work on anyother device having Marshmallow... Its a MY6753 device.
or any way to edit you patch and make it work on my device....
gladiac said:
Hey everybody!
This project has been moved to HERE! Please post your problems, success stories and so on there from now on.
Cheers, gladiac
Click to expand...
Click to collapse
rawdealer said:
You didn't Format the Data It's quite a large button in twrp
Click to expand...
Click to collapse
Emilius said:
OMG, please don't tell anyone
Click to expand...
Click to collapse
rawdealer said:
FORMAT DATA, the extra large button
http://forum.xda-developers.com/and...v8-forceencrypt-disable-t3234422/post63810702
Click to expand...
Click to collapse
haibane said:
Rawdealer, I got it to work lol. Just seemed odd that you had to Format Data instead of doing a full wipe of everything. I'm guessing the Format Data just had to occur after CM was installed.
Click to expand...
Click to collapse
SamS1989 said:
it does not working on my n6 (7.1.1 stock)
what i do :
- flash 7.1.1 factory image
- turned off after the flash, reboot in fastboot
- boot twrp (without flash)
- flashed the V8 fed
- wipe data/cache (in twrp)
and after the reboot the phone stil decrypted
should i do the factory reset from settings or it's good from twrp ?
Click to expand...
Click to collapse
rewrite the instructions in both threads:
flash FED-Patcher.zip
use the Format Data button!!! neither Swipe to Factory Reset! nor Advanced Wipe!
v8 works well for nexus 6 stock 7.1.1, thanks to the op @gladiac and the discoverer @rawdealer, would better someone quote this in the other thread since New members (those with few posts) are not permitted to post to development-related forums
Bump
Thanks for this.
Does FED-Patcher still not work with Nougat?
I tried to use the detailed instructions here:
https://forum.xda-developers.com/nexus-6/general/how-to-disable-force-encryption-nexus-6-t3220273
I am not a pro at any of this, including TWRP.
I downloaded the Factory Image from Google (7.1.1 July for Shamu , Nexus 6)
https://dl.google.com/dl/android/aosp/shamu-n6f27h-factory-718e138f.zip?hl=vi
I unlocked and rooted my N6, flashed TWRP.
I followed all the instructions. When I got to step 8: Flash your ROM, it wouldn't work. I kept getting Zip verification errors in TWRP. I also tried to do it in NRT.
I was told that you can't install a Google factory image via TWRP. I guess the factory image would overwrite the recovery with stock. (my guess)
And when I used NRT, I got a hash mismatch when I tried to flash the factory image it as a ZIP.
NRT would only install the factory image via "Flash Stock and Unroot" which I guess defeats the purpose of this.
So I can go back to those instructions but am unclear which Android ROM to flash at step 8.
Use https://github.com/yoinx/kernel_adiutor/raw/master/download/app/app-release.apk Warning, you _must_ debloat this rom
Download Rom https://mega.nz/#!QZAHHYzb!lfpF2c_gl5Cfrg93S2Dy6KTIzbnwF7Wb_85LFkzz76s
flash this kernel and reboot recovery before installing rom https://github.com/lgrootnoob/andro...a6d28b7b324d9e4ace9239dbcb5f9d9cd0c7/boot.img
then after installing rom flash the kernel again. its far more updated than whats in the rom zip.
Gapps for the brave(probably still doesnt work) https://www.androidfilehost.com/?w=profile&uid=23060877490004802
Hacks for building, and features included:
ubertc 5.4 and justarchi O3 on the rom, ubertc 6.1.1 and Ofast on the kernel. f2fs is recommended and supported on data and cache
This patch is applied http://review.cyanogenmod.org/#/c/120824/2/build/Android.common_build.mk
https://android-review.googlesource.com/#/c/148147/
http://forum.xda-developers.com/showpost.php?p=67211122&postcount=7
my trees are required for building
Ophidian_DarkCore said:
Use opengapps pico.
Should probably remove some of the crap gapps installs also.
Let me know if this flashes from cm11 recovery, and/or omni 5.1 recovery.
Use https://github.com/yoinx/kernel_adiutor/raw/master/download/app/app-release.apk for control of kernel. set cpu min to 200mhz, max 1400mhz, disable animations and all the live display and ambient display crap. then it should run smooth.
Use this supersu https://mega.nz/#!H5AEyI6Z!2FFd91__n2JVJSh-RidwpkMmYj5bfuQhHHLiEGr2LK4
Download Rom
Experimental Release 6(Skipped releasing small internally tested builds that had few changes. This build has a new kernel with CMA and the rom has justarchi optimizations and ubertc 5.3): https://mega.nz/#!9RpHDDiL!3r0A7ox2Vv864mB7SrRqUSFaKIWoEdjpUUbFnVg27yI
Stable Release 3(Latest Omni r43): https://mega.nz/#!xRoFxYbb!mXTzPPfqErND5pOe_B2XC0cEcKKQ4F4YJVWb_oMNhZQ
Release 2(device tree updates): https://mega.nz/#!ANYRnSbL!jAtYHkOpc1Jg_ULyl4TCVFBZ45lxzSx-7WKWeTYX8GM
Initial Release: https://mega.nz/#!xcg0nZzZ!_zTmgEC4SR4fsPAAAmlcphp72T44lGgBPjgLgXGLrD8
cache and system on ext4, data on f2fs. f2fs is buggy for cache.
mount system in twrp before flashing
thanks to everyone that was thanked in the omni 5.1 thread. source is on xc racer's github.
Hacks:
The zip is debloated.
This patch is applied http://review.cyanogenmod.org/#/c/120824/2/build/Android.common_build.mk
My fascinatemtd and aries-common trees need to be used.
We have a special updater_script
The experimental release has another commit not from the trees on my github: https://android-review.googlesource.com/#/c/148147/
With poweramp 703 alpha this is just a music player rom for my device.
Click to expand...
Click to collapse
Wow. Kudos to @Ophidian_DarkCore for doing a marshmallow build for the venerable old Fascinate! How's it work?
I've got a couple old fascinates in desk docks acting as clocks (cm10.1 with clock daydream most of the time). Wi-Fi access needs to work for a Chromecast remote function now and then.
Sent from my One using XDA-Developers mobile app
bmeek said:
Wow. Kudos to @Ophidian_DarkCore for doing a marshmallow build for the venerable old Fascinate! How's it work?
I've got a couple old fascinates in desk docks acting as clocks (cm10.1 with clock daydream most of the time). Wi-Fi access needs to work for a Chromecast remote function now and then.
Sent from my One using XDA-Developers mobile app
Click to expand...
Click to collapse
wifi works fine on this rom. there is a gapps bug that i cant figure out, all the sudden all of the builds crash setup wizard, and now i cant even get my partitions to setup properly. i think it has to do with something i did when i was reflashing my devices from stock to mm again to test everything out before final release. i just have no clue. but it works great for wifi just install everything without gapps i guess. i really need someone to test this tbh
Ophidian_DarkCore said:
wifi works fine on this rom. there is a gapps bug that i cant figure out, all the sudden all of the builds crash setup wizard, and now i cant even get my partitions to setup properly. i think it has to do with something i did when i was reflashing my devices from stock to mm again to test everything out before final release. i just have no clue. but it works great for wifi just install everything without gapps i guess. i really need someone to test this tbh
Click to expand...
Click to collapse
Like I said, I'm running cm10.1 on the fascinate, do you attempt to change the partition arrangement from what cm uses?
Sent from my One using XDA-Developers mobile app
Ophidian_DarkCore said:
wifi works fine on this rom. there is a gapps bug that i cant figure out, all the sudden all of the builds crash setup wizard, and now i cant even get my partitions to setup properly. i think it has to do with something i did when i was reflashing my devices from stock to mm again to test everything out before final release. i just have no clue. but it works great for wifi just install everything without gapps i guess. i really need someone to test this tbh
Click to expand...
Click to collapse
OK... I just downloaded your experimental ROM and pico gapps. Turns out my Fascinate still has CWM 6.0.3.3 recovery. I'm doing a backup of my cm10.1 and then we will see if your ROM will install...
OK. "some symlinks failed". Guess I need a new recovery. I'm out of date on this old device. What's my best choice of recovery?
Sent from my One using XDA-Developers mobile app
bmeek said:
OK... I just downloaded your experimental ROM and pico gapps. Turns out my Fascinate still has CWM 6.0.3.3 recovery. I'm doing a backup of my cm10.1 and then we will see if your ROM will install...
OK. "some symlinks failed". Guess I need a new recovery. I'm out of date on this old device. What's my best choice of recovery?
Sent from my One using XDA-Developers mobile app
Click to expand...
Click to collapse
zimage in odin from the omnirom 5.1 thread. its the same mtd over bml lvm bs from cm11. but something is wrong with it. like ot was causing the zip not to flash or the partitions would become unmountable. i diffed the scripts and i dont see a difference.. so i removed the script from my zips. no big deal. gapps is what i need tested after you confirm the rom works.
@bmeek here is a full unmodified zip. still ubertc 5.3 with justarchi stuff, has cma kernel, and opticharged. the latest device tree code is used. i cant get gapps to work. they just crash. when the zip install fails, reboot to recovery and install again. then it works https://mega.nz/#!QZAHHYzb!lfpF2c_gl5Cfrg93S2Dy6KTIzbnwF7Wb_85LFkzz76s
its hella fast for me, but i have kernel adiutor stuff changed. like laptop fs mode, less entropy generation, 200-1400mhz, no animations etc. and lots of bloat removed
bmeek said:
Like I said, I'm running cm10.1 on the fascinate, do you attempt to change the partition arrangement from what cm uses?
Sent from my One using XDA-Developers mobile app
Click to expand...
Click to collapse
I run CM10.1 too! With devil Kernel. Max clock set to 1200MHz.
Home button, recent apps button do not work, clicking "more" in settings crashes it, quick settings do not work, notifications do not work. in the R3 build.
Can't get the R6 build to install, "Operation not supported on transport endpoint.".
Erase system partition before you flash this, Or you will have problems! btw, the zip will not install from cm10.1 cwm recovery, I had to flash Omni 5.1.1, reboot recovery, then flash this 6.0.1 build. I am on R6 now.
Finally got the R6 to install lastnight. in fact, I am writing on it write now in chrome (36). chrome is the only browser that works.
cool, use the latest link a couple posts up, and whoever needs gapps, this is the proper link.(xc-racer99 linked it said it was officially supported by omni https://www.androidfilehost.com/?w=profile&uid=23060877490004802 ) i cant be arsed to even edit the op with no one looking. you gotta do your own debloating when installing the full unmodified build(the latest one)
pcwizzy37 said:
Finally got the R6 to install lastnight. in fact, I am writing on it write now in chrome (36). chrome is the only browser that works.
Click to expand...
Click to collapse
webview is probably broken in the rom
kernel update: wayy more updated f2fs, exfat in kernel for exfat of course and also for vfat, which means more stability and recent code. sync with xc-racer99 sources for more cma etc... updates and a radix-tree backport from the 3.4 kernel. thanks arter97, dorimanx, xc and cwof
sauce removed, use link in op for the new boot.img
Ophidian_DarkCore said:
kernel update: wayy more updated f2fs, exfat in kernel for exfat of course and also for vfat, which means more stability and recent code. sync with xc-racer99 sources for more cma etc... updates and a radix-tree backport from the 3.4 kernel. thanks arter97, dorimanx, xc and cwof
sauce https://mega.nz/#!4YwASYhT!X91E-f0i7KOGBYvMjxF1NT4qLSujqYYg6G8s9vnZHVQ
6/13/16 11:06pm: these optimizations are about to make the galaxys devices in all variants sky rocket performance wise
Click to expand...
Click to collapse
is this boot.img in the latest download (omni-6.0.1-20160521-fascinatemtd-HOMEMADE.zip)? My fascinate started getting in a reboot loop last week so I decided to wipe and try this.
---------- Post added at 08:40 PM ---------- Previous post was at 08:35 PM ----------
I wiped (all 3),
installed omni 6.0.1 20160521,
installed BaNkS_Dynamic_GApps
installed SuperSU
I cannot get past the got another device screen in wizard. I eventually get 'Google play services has stopped.' I will try again without GApps. What do you suggest I do?
mswells said:
is this boot.img in the latest download (omni-6.0.1-20160521-fascinatemtd-HOMEMADE.zip)? My fascinate started getting in a reboot loop last week so I decided to wipe and try this.
---------- Post added at 08:40 PM ---------- Previous post was at 08:35 PM ----------
I wiped (all 3),
installed omni 6.0.1 20160521,
installed BaNkS_Dynamic_GApps
installed SuperSU
I cannot get past the got another device screen in wizard. I eventually get 'Google play services has stopped.' I will try again without GApps. What do you suggest I do?
Click to expand...
Click to collapse
We have to bug @xc-racer99 trust me ive spent a couple hours trying to figure this one out, btw the op states to flash the boot.img after flashing the rom zip(which _is_ old). we also gotta do hella debloat because banks doesnt actually fit, it leaves an apk or two unwritten cause running out of space. if you can convince xc to figure this out I'll release a package solution, with the latest rom(reworked optimizations and synced with latest omni source yesterday) and gapps all debloated.
Ophidian_DarkCore said:
We have to bug @xc-racer99 trust me ive spent a couple hours trying to figure this one out, btw the op states to flash the boot.img after flashing the rom zip(which _is_ old). we also gotta do hella debloat because banks doesnt actually fit, it leaves an apk or two unwritten cause running out of space. if you can convince xc to figure this out I'll release a package solution, with the latest rom(reworked optimizations and synced with latest omni source yesterday) and gapps all debloated.
Click to expand...
Click to collapse
I have no idea why you guys are having such problems on the Fascinate: with a freshly synced Omni source, freshly downloaded OpenGapps pico, I had no issues getting through the Setup Wizard (I did skip setting up a Google Account) on my Galaxy S 4G - although it was understandably laggy. The default Browser also works just fine afterwards.
Perhaps the gapps package provided removes some essential file/doesn't overwrite properly?
xc-racer99 said:
I have no idea why you guys are having such problems on the Fascinate: with a freshly synced Omni source, freshly downloaded OpenGapps pico, I had no issues getting through the Setup Wizard (I did skip setting up a Google Account) on my Galaxy S 4G - although it was understandably laggy. The default Browser also works just fine afterwards.
Perhaps the gapps package provided removes some essential file/doesn't overwrite properly?
Click to expand...
Click to collapse
i have it written completely and setup wizard blatantly stops right after boot. Then sometimes setup wizard will work and then google play services will crash incessantly. I think this was the case with the 5.1 builds too. I get issues with "you have tried to change the api from what has been previously released in" while building and i have to manually remove 4 lines from the output folder's api txt file. but i was convinced thats just a part of using lunch instead of brunch. i also jacked around with the fingerprint for no real sane reason but reverted it in my local trees. the latest build is dex preopted but the first builds(generic no changes) arent and they still have this issue
wait, could it be that we dont init gps and ril? https://github.com/lgrootnoob/andro...mmit/9f67333ee281c1b7fcc5c2ae04eb899a14b4b1ee https://github.com/lgrootnoob/andro...mmit/5d8effadf263a8a22809f3d3751245351c2c11eb
im basically at your mercy here. whatever you say to do, ill be ready to build and try it
Heyo, guys. I wanna show u my own ROM based on LineageOS 14.1.
Flash it as u flash another ROMs:
Wipe System, data, caches
Flash ROM
Flash Gapps
Flash SuperSu if u want
For update just do dirty flash.
Hope that u'll like this ROM.
Download link:
AFH
Big thanks to @romilparh who was the first man who helped me with beginning things.
Thanks to @jhalayashraj who taught me some things
Thanks to @amardeep434 who also helped me a lot
Thanks to @danieldmm who also helped me with a lot of things
Also thanks to @TechExhibeo my sensei who can help with ton of problems and advise smth
And thanks @jgcaap for some interesting things on github.
LineageOS
Kernel
Device
Have a good use and thanks
umm.. First?
EDIT: Hey Oleg, nice to see your CM. Will download asap.
hey there, I was on resurrection remix 6.0, i followed the given steps
> flashed the latest version of TWRP image
>flashed the Lineage OS 14.1 zip via twrp (yes i wiped everything)
when i try flashing the open gapps mini zip (ARM, 7.1, mini); it says insufficient system storage (error code 70), i even selected advanced options and tried resizing system partition and then flash the gapps zip, but it still says insufficient storage (p.s i would’nt like to downgrade pico version or so)
but it seems like there’s enough storage (1300mb system storage)
how can i resolve this issue?
Thanks in advance.
Tried doing the same with cm 14.1 with the same Gapps and it works.
thank u very much for this awesome rom.
Wow this ROM is awesome! I just saw LineageOS 14.1 for the OnePlus One yesterday. No bugs so far, It seems really stable and a great and probably the best daily driver ROM.
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
nolsen311 said:
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
Click to expand...
Click to collapse
i'm not facing any problem with AdAway and viper in 20170109 build.
NeolWhyt said:
hey there, I was on resurrection remix 6.0, i followed the given steps
> flashed the latest version of TWRP image
>flashed the Lineage OS 14.1 zip via twrp (yes i wiped everything)
when i try flashing the open gapps mini zip (ARM, 7.1, mini); it says insufficient system storage (error code 70), i even selected advanced options and tried resizing system partition and then flash the gapps zip, but it still says insufficient storage (p.s i would’nt like to downgrade pico version or so)
but it seems like there’s enough storage (1300mb system storage)
how can i resolve this issue?
Thanks in advance.
Tried doing the same with cm 14.1 with the same Gapps and it works.
Click to expand...
Click to collapse
Probably u're doing smth wrong...
nolsen311 said:
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
Click to expand...
Click to collapse
Doesn't have any problem. All is ok.
Okeys said:
Doesn't have any problem. All is ok.
Click to expand...
Click to collapse
Oh, OK. Everything's OK. Cool.
I noticed that viper isn't included in the build any more. So everything must be even more OK now, right?
Whatever issues I had seem to have been resolved after updating to 20170109. We'll see after this runs for a couple days. Right now adaway is able to do its thing without error and at least audioFX seems to work.
Thank you for building these for us.
Sent from my A0001 using Tapatalk
nolsen311 said:
Oh, OK. Everything's OK. Cool.
I noticed that viper isn't included in the build any more. So everything must be even more OK now, right?
Whatever issues I had seem to have been resolved after updating to 20170109. We'll see after this runs for a couple days. Right now adaway is able to do its thing without error and at least audioFX seems to work.
Thank you for building these for us.
Click to expand...
Click to collapse
Viper is still included. Just change SELinux mode. I'll change on needed later.
Have a good use
I have tried to flash the OS. I have wiped the data, cache, dalvik cache and system partition (recovery TWRP 3.0.2.0).
After that I have flashed build `lineage-14.1-20170109-Okeys-bacon` and the pico GApps (mini cause insufficient system storage error).
Then when I tries to boot, and it takes more then 20 minutes to boot (the OS still didn't booted).
Is it normal? What should I do?
f2sf it's supported?
hyper_davide said:
f2sf it's supported?
Click to expand...
Click to collapse
Now not.
ppp99 said:
I have tried to flash the OS. I have wiped the data, cache, dalvik cache and system partition (recovery TWRP 3.0.2.0).
After that I have flashed build `lineage-14.1-20170109-Okeys-bacon` and the pico GApps (mini cause insufficient system storage error).
Then when I tries to boot, and it takes more then 20 minutes to boot (the OS still didn't booted).
Is it normal? What should I do?
Click to expand...
Click to collapse
All in ext4?
Okeys said:
All in ext4?
Click to expand...
Click to collapse
Just checked, YES.
https://www.androidfilehost.com/?w=files&flid=132556
Thanks so much Okeys! this is the best ROM I could find so far, it works so perfectly!!
Summary of my attempts:
(1)I tried "lineage-14.1-20170130-nightly-bacon-signed.zip" from lineageos
* lower kernel: 3.4.112
* not support system root, need install supersu.
* System APP: "SoundRecorder" and "Screencast" were merged and replaced with "Recorder", I don't like the new "Recorder", the recorder file is much bigger than "SoundRecorder"
(2)I tried "RR-N-v5.8.1-20170131-bacon-Official.zip" from remix
* Same as lineage above
* Support system root option, not need supersu
(3)lineage-14.1-20170126-Okeys-bacon.zip
* new kernel: 3.4.113
* not support system root, need install supersu.
* keep the original "SoundRecorder" and "Screencast"
* The only problem I met is "Left Wipe" doesn't switch to "Google" with Pixel Launcher for Andriod 7.1, but I find a solution and fixed it.
** see my post: https://forum.xda-developers.com/oneplus-one/help/fix-left-wipe-doesnt-switch-to-google-t3549497
Please change to coloros blobs dude
20170202 Bacon Gesture Settings
lineage-14.1-20170202-Okeys-bacon flashed a few minutes ago. Noticed that the Gestures settings no longer allows control over music and camera gestures. They are on by default, and I guess can no longer be turned off.
Hope this helps,
E.
Samsung Galaxy Note 8 (Snapdragon)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.09-B01 [Nougat:7.1.1]
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 3.3.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
APK install:
Once installed, open up the Safestrap application, Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
APK:
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Open your old Safestrap app and use the "Uninstall Recovery" button
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK, Grant SU access, Use the "Install Recovery" button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again.
- Busybox is now required for the Safestrap APK to work correctly
DOWNLOADS:
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY Note 8 (Snapdragon) [Nougat:7.1.1]
LATEST ZIP: Safestrap-4.09-B01-GREATQLTE-SS-FF-flashable.zip
LATEST APK: Safestrap-4.09-B01-GREATQLTE.apk
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode, DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery.
@jrkruse for pointing me that S8 has permissive root. @partcyborg for getting root on S8.
@me2151 for testing and getting the right configs in place.
CHANGELOG:
4.09-B01 [2019-04-19]
- TWRP updated to 3.3.0.
- Fix reboot function
- Add reboot to safestrap button in reboot menu
- Add Edl button in reboot menu
- Move Boot Options to advanced menu items.
- Safestrap app: Update topjohnwu's libsu to 2.4.0.
- Safestrap app: Update install recovery function.
4.08-B01 [2019-03-01]
- TWRP updated to 3.2.3.
- Fix datamedia mount.
- Add hijack-backup during image flashing.
- Major code clean up.
4.07-B01 [2018-07-16]
- Fix CHARGER_BOOT detection.
- TWRP updated to 3.2.2.
- Update safestrap portrait theme.
- Update safestrap app to use topjohnwu's libsu & internal busybox (busybox app not needed anymore).
4.06-B02 [2018-04-10]
- Fix taskset cpus to 8 cores (thanks to Hashcode).
- Add exfat support for recovery (ext-sdcard fix).
- Blacklist mouse cursor in recovery (thanks to me2151).
- Fix MTP (thanks to me2151).
4.06-B01 [2018-04-03]
- Initial release.
BUGS:
- ROM-slots not working for now.
Mine
Awesome to see this. We might have true development after all.
I hope we can get the rom part of safestrap fixed! Great work
Wahhhh just when i oreo is released for the unlocked note 8. Haha guess i wont be taking oreo update anytime soon and may actually want to root dispite the 80% battery.
I really hope there are still developers that will cook roms or ports of internation version like dr ketans.
Thanks. Cant wait for ur rom portion of safestrap.
I can confirm this is legit guys. backups and restores work. For the moment full custom roms like lineage will not be possible. but ill be working on that
I'd love to see me some Darthstalker ROM's those were my favorite on the Note 5. I don't know if Jovy still makes ROM's though.
Best I can tell I can't Backup or access the external SDCard ... Only the internal
Is that the same for you guys?
jcrompton said:
Best I can tell I can't Backup or access the external SDCard ... Only the internal
Is that the same for you guys?
Click to expand...
Click to collapse
i can access external fine.
why would you back it up though
me2151 said:
i can access external fine.
why would you back it up though
Click to expand...
Click to collapse
Lol
I guess I should have wrote "backup to" ext sd
When I click on microsd in recovery it won't activate
---------- Post added at 12:31 AM ---------- Previous post was at 12:23 AM ----------
I went back into safestrap recovery (for some reason my screenshot didn't save)
But when I tried to mount the microsd or external SDCard I got an error
Invalid argument ..... Blah blah can't mount ext sd
Im running a backup to my sdcard as i type this. Works perfectly. I am however not using the build in this thread. just my own.
me2151 said:
Im running a backup to my sdcard as i type this. Works perfectly. I am however not using the build in this thread. just my own.
Click to expand...
Click to collapse
?
Well maybe that's why
jcrompton said:
Well maybe that's why
Click to expand...
Click to collapse
Doubt it i ha ent changed any mounts on mine
me2151 said:
Doubt it i ha ent changed any mounts on mine
Click to expand...
Click to collapse
Well it's gotta be something since I can't access it
I started a thread a long time ago saying this is possible and someone should start on it, and everyone said I was dumb and didn't know ehat I was talking about. Me121 or what ever his name is said he worked on the fish a little its like safestrap but couldn't get it to work.
So glad someone got it working and am very Happy to be a note 8 owner now my next paycheck I will donate a beer to ya
DroidisLINUX said:
I started a thread a long time ago saying this is possible and someone should start on it, and everyone said I was dumb and didn't know ehat I was talking about. Me121 or what ever his name is said he worked on the fish a little its like safestrap but couldn't get it to work.
So glad someone got it working and am very Happy to be a note 8 owner now my next paycheck I will donate a beer to ya
Click to expand...
Click to collapse
Yup FiSH had the same issue this had with it inits not launchng but this guy figured it out
You guys are simply amazing I just had to say that
jcrompton said:
Best I can tell I can't Backup or access the external SDCard ... Only the internal
Is that the same for you guys?
Click to expand...
Click to collapse
Lets make it clear, jrkruse tested 16GB and 32GB ext-sd and it works on S8+, 64GB and above not working.
I have tested 16GB on my S8 and works.
What size is yours?
afaneh92 said:
Lets make it clear, jrkruse tested 16GB and 32GB ext-sd and it works on S8+, 64GB and above not working.
I have tested 16GB on my S8 and works.
What size is yours?
Click to expand...
Click to collapse
128
I didn't know it mattered .... I guess size does matter ,,eh?
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery - use my twrp
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
almost all
Known Issues
sometimes FC in camera
LineageOS Builds
3. 20180719: cleanup, update hwui\dalvik settings, add bt codecs (aptx, aptx-HD, ldac) https://drive.google.com/file/d/1EDIZPh5SOa36nUErAvFBREzRAhZCtHGa/view?usp=sharing
2. 20180713: https://drive.google.com/file/d/1sItey9421ml2QSyTNQKn5s1frvjASdCc/view?usp=sharing
1. 20180712: https://drive.google.com/file/d/1FWoBISUpbPozdlqkuJxBh7fdksEg-yP9/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM64
Android: 8.1
Variant: any
Sources
Sources: https://github.com/Lineageos
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870
Device: https://github.com/Valera1978/android_device_samsung_gtaxllte
Vendor: https://github.com/Valera1978/android_vendor_samsung_gtaxllte
Thanks
Thanks to LineageOS team
Finally, I had time to check whether it's possible to build a 64bit firmware on the exynos7870. Yes, we have 64bit kernel, but all stock firmwares were 32bit, as result I need a lot of missed 64bit proprietary files.
This is fully 64bit firmware, missed files from a5'17 (it's on exynos7880) - gralloc, gps, ril, gles (mali).
Only own audio\camera still 32bit, but in any case it's working great in 64bit firmware.
I wrote own sensors HAL, because it's very specific for each device, it's still buggy, i'm continue work on it.
Right now I need understand - do we need 64bit at all? I don't see any huge improves.
Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery - use my twrp
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
almost all
Known Issues
buggy sensors (accelerator and light)
LineageOS Builds
1. 20180712: https://drive.google.com/file/d/1FWoBISUpbPozdlqkuJxBh7fdksEg-yP9/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM64
Android: 8.1
Variant: any
Sources
Sources: https://github.com/Lineageos
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870
Device: https://github.com/Valera1978/android_device_samsung_gtaxllte
Vendor: https://github.com/Valera1978/android_vendor_samsung_gtaxllte
Thanks
Thanks to LineageOS team
Click to expand...
Click to collapse
Congrats! I am test it asap!:good::good::good:
new version.
now I can say - it's stable.
sensors - done (back to stock sensors.universal7870.so with prebuild 32bit service for sensors)
flip - done
it's still sometimes fc on camera - I'll check it later
I can confirm it works on SM-T580 (WiFi only) as well. Everything seems to work fine; buttons, WiFi + BT, camera, audio, video (youtube), sensors, smart cover etc.
OpenGApps 8.1 ARM64 installed with no errors.
The only thing I noticed is during first boot screen it says in the top-left corner in red text: 'Kernel is not seandroid enforcing'. Maybe this is on SM-T585 as well.
On the SM-T580 you get unusable sim-card icon in the notification bar and some other places, but that is to be expected.
sanchaz12 said:
I can confirm it works on SM-T580 (WiFi only) as well. Everything seems to work fine; buttons, WiFi + BT, camera, audio, video (youtube), sensors, smart cover etc.
OpenGApps 8.1 ARM64 installed with no errors.
The only thing I noticed is during first boot screen it says in the top-left corner in red text: 'Kernel is not seandroid enforcing'. Maybe this is on SM-T585 as well.
On the SM-T580 you get unusable sim-card icon in the notification bar and some other places, but that is to be expected.
Click to expand...
Click to collapse
Just installing on T585 now, I've flashed the rom and gapps fine.
Problem I have is first there was no keyboard, and now I can't sign in to Google account
It says checking and then screen goes black.
I've wiped cache and davlik but still won't work
Any help would be appreciated
Also, what's a full wipe in twrp?
Sent from my ONEPLUS A5010 using Tapatalk
tolerant said:
Just installing on T585 now, I've flashed the rom and gapps fine.
Problem I have is first there was no keyboard, and now I can't sign in to Google account
It says checking and then screen goes black.
I've wiped cache and davlik but still won't work
Any help would be appreciated
Also, what's a full wipe in twrp?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Those problems may be related to improper wipe, no worries.
Full wipe means in TWRP you go to 'Wipe' -> 'Advanced Wipe' -> Select all partitions except 'Micro SD card' and 'USB OTG'
In my case (SM-T580) that would be;
- Dalvik / ART cache
- System
- Data
- Internal Storage (Optional, but recommended to wipe)
- Cache
Don't forget to first make a backup via TWRP of the 'EFS' partition (on sd-card or USB-stick via OTG cable), just in case the SIM-card functions stop working due to lost IMEI.
Also, some issues may be related to the device still working on stuff when it shows the welcome screen after flashing. In general you should leave the device for around 5 minutes before doing anything after flashing and first boot to let everything finish properly.
sanchaz12 said:
Those problems may be related to improper wipe, no worries.
Full wipe means in TWRP you go to 'Wipe' -> 'Advanced Wipe' -> Select all partitions except 'Micro SD card' and 'USB OTG'
In my case (SM-T580) that would be;
- Dalvik / ART cache
- System
- Data
- Internal Storage (Optional, but recommended to wipe)
- Cache
Don't forget to first make a backup via TWRP of the 'EFS' partition (on sd-card or USB-stick via OTG cable), just in case the SIM-card functions stop working due to lost IMEI.
Also, some issues may be related to the device still working on stuff when it shows the welcome screen after flashing. In general you should leave the device for around 5 minutes before doing anything after flashing and first boot to let everything finish properly.
Click to expand...
Click to collapse
Thanks for that info, that worked brilliant, now fully working.
Thanks sanchaz12
Sent from my SM-T585 using Tapatalk
Rom is running smoothly, only problem I found so far is the camera app, it loads but the soft button only shows a half. It's like the screen is not big enough.
Is there a fix for this?
Sent from my ONEPLUS A5010 using Tapatalk
tolerant said:
Rom is running smoothly, only problem I found so far is the camera app, it loads but the soft button only shows a half. It's like the screen is not big enough.
Is there a fix for this?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Install another good camera. For example i am using Camera FV-5.
It's honestly WORRYING the fact the tablet runs at 10FPS when scrolling through the notification bar. Can't you disable the notification bar background alpha @Valera1978?
Hi. Thanks a lot @Valera1978 . Good job. Even GPS work now.:good:
Great work. I'm new there, i've just buy a T580 and watch your thread for 1 day.
Edit : "Install custom recovery - use my twrp" Where can i find it ? Thanks.
Steelskinz said:
Edit : "Install custom recovery - use my twrp" Where can i find it ? Thanks.
Click to expand...
Click to collapse
This for T585 only. You need install TWRP for T580 official or by @followmsi better from his RR threads.
repey6 said:
Hi. Thanks a lot @Valera1978 . Good job. Even GPS work now.:good:
Click to expand...
Click to collapse
Great! I can confirm that gps gets a fix in gps test app, just as can be seen in the screenshot. Also open camera app can take photos on both cameras and video on back camera. I couldn't record video with front camera, but that doesn't bother me anyway.
repey6 said:
This for T585 only. You need install TWRP for T580 official or by @followmsi better from his RR threads.
Click to expand...
Click to collapse
OK thanks.
Is this rom still OK for T580 ? I read someone flashed it already. Can anyone confirm ? Thanks.
I can't access the SD card in this ROM, maybe there are some leftover files from the previous ROM, that prevent the tablet from accessing it? Anybody has some advice if it's possible to fix that?
mnd123 said:
I can't access the SD card in this ROM, maybe there are some leftover files from the previous ROM, that prevent the tablet from accessing it? Anybody has some advice if it's possible to fix that?
Click to expand...
Click to collapse
External SD card?
Sent from my ONEPLUS A5010 using Tapatalk
tolerant said:
External SD card?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Yes
mnd123 said:
Yes
Click to expand...
Click to collapse
Did you format it as internal storage on the last romyou had installed, if so it possibly will not work unless it's reformatted on the currently installed rom.
Does it actually show up in file manager?
Sent from my ONEPLUS A5010 using Tapatalk