[Recovery][TWRP] Team Win Recovery Project v3.2.3 [Treble][F2FS][08/06] - LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D

Custom Treble-ready TWRP with F2FS encryption
Features:
Code:
* Treblize button for automated Treble conversion;
* New /vendor mount points in place;
* F2FS encryption and decryption support;
* Upstreamed Lambda Kernel tailored down for recovery.
Downloads:
All prebuilt recovery images are available on Github, the current tag is 08062018.
XDA:DevDB Information
Unofficial Treble-ready TWRP with F2FS encryption, Tool/Utility for the LeEco Le Pro3
Contributors
GalaticStryder, codeworkx
Source Code: https://github.com/GalaticStryder/android_bootable_recovery
Version Information
Status: Testing
Stable Release Date: 2018-04-20
Created 2017-03-11
Last Updated 2018-08-07

Reserved

Reserved

It sounds like if you are already rooted and have twrp installed all you need to download the multi rom apk. Is it that easy to have two three rom to jump back and forth?
Sent from my LEX727 using XDA-Developers Legacy app

toanau said:
It sounds like if you are already rooted and have twrp installed all you need to download the multi rom apk. Is it that easy to have two three rom to jump back and forth?
Sent from my LEX727 using XDA-Developers Legacy app
Click to expand...
Click to collapse
MultiROM app will install a new TWRP and the trampoline chainloader.
You can have as many as you'd like to test... Just don't put a password on lockscreen to avoid the credentials bug.
The vanilla TWRP is the latest you can get and has decryption support for testing, so it's a good shot flashing it as well if you're not going to multirom.
Sent from my LEX720 using Tapatalk

Does all rom have to be rooted? I usually like rom to be none rooted for work related email dam app checks for root
Sent from my LEX727 using XDA-Developers Legacy app

toanau said:
Does all rom have to be rooted? I usually like rom to be none rooted for work related email dam app checks for root
Sent from my LEX727 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Only first slot ROM needs root but it's not mandatory as trampoline integrates the Kernel not the system and so won't need root for the basic functions. You'll only need root when using the app to install the modification, manual install doesn't need as I said but it's strongly recommended on first slot.
Sent from my LEX720 using Tapatalk

GalaticStryder said:
Only first slot ROM needs root but it's not mandatory as trampoline integrates the Kernel not the system and so won't need root for the basic functions. You'll only need root when using the app to install the modification, manual install doesn't need as I said but it's strongly recommended on first slot.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
Hey @GalaticStryder,
I flashed this Recovery on my x727 but it looks like it's not passing encryption. :crying: Any ideas on what I can do? It asks me to decrypt with password upon booting recovery.

Ascertion said:
Hey @GalaticStryder,
I flashed this Recovery on my x727 but it looks like it's not passing encryption. :crying: Any ideas on what I can do? It asks me to decrypt with password upon booting recovery.
Click to expand...
Click to collapse
Probably system's vold didn't work for decryption. Could you flash previous version on fastboot? I have a script to extract the blobs from system just in case but I wanted to test the built-in feature from TWRP.
I've tested on LineageOS and it worked but my device is Chinese.
Sent from my LEX720 using Tapatalk

GalaticStryder said:
Probably system's vold didn't work for decryption. Could you flash previous version on fastboot? I have a script to extract the blobs from system just in case but I wanted to test the built-in feature from TWRP.
I've tested on LineageOS and it worked but my device is Chinese.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
Unfortunately, same thing. I am greeted by a Enter Password screen upon booting either after flashing in Fastboot. I am using command below.
Fastboot flash recovery TWRP_zl1_20170302.img
It looks like it'd work perfect but has the encryption issue on x727 variants. My guess is Lineage is also based on the x720 and doesn't encrypt the OS when it boots?

Ascertion said:
Unfortunately, same thing. I am greeted by a Enter Password screen upon booting either after flashing in Fastboot. I am using command below.
Fastboot flash recovery TWRP_zl1_20170302.img
It looks like it'd work perfect but has the encryption issue on x727 variants. My guess is Lineage is also based on the x720 and doesn't encrypt the OS when it boots?
Click to expand...
Click to collapse
Not actually that way, but we can say that. Does any other recovery decrypt properly on your device? Probably recoveries with built-in blobs or blobs extracted from system.

Hello. I have a problem with the kernel of VillarLeg AOKP. The problem is that as soon as I try to change some parameters of some governor you restart the device. I reported the problem to this Centre dev and he said that without MultiROM there are no such problems. Can it be solved?
Inviato dal mio LEX720 utilizzando Tapatalk

Can someone make a zip file that erases lock screen realted files in data/system folder?
TWRP offers file manger only on primary rom, not on other multi roms. So if you have locks on 2nd, 3rd... roms, you are screwed.
If such zip file can be made, it would be easy to fix the mistake/problem.

4K2K said:
Can someone make a zip file that erases lock screen realted files in data/system folder?
TWRP offers file manger only on primary rom, not on other multi roms. So if you have locks on 2nd, 3rd... roms, you are screwed.
If such zip file can be made, it would be easy to fix the mistake/problem.
Click to expand...
Click to collapse
if you swipe rom?
Inviato dal mio LEX720 utilizzando Tapatalk

GalaticStryder said:
Not actually that way, but we can say that. Does any other recovery decrypt properly on your device? Probably recoveries with built-in blobs or blobs extracted from system.
Click to expand...
Click to collapse
The one from the Lineage thread works fine, but it's TWRP 3.0.2.0. I don't see a source for it though.

Ascertion said:
The one from the Lineage thread works fine, but it's TWRP 3.0.2.0. I don't see a source for it though.
Click to expand...
Click to collapse
My TWRP device tree uses Lineage 13.0 to build but different Kernel and no blobs. Could post here the screens asking for passwd and a dmesg inside recovery?

GalaticStryder said:
My TWRP device tree uses Lineage 13.0 to build but different Kernel and no blobs. Could post here the screens asking for passwd and a dmesg inside recovery?
Click to expand...
Click to collapse
Unfortunately, it looks like /system or /storage doesn't mount either so I'm not able to get a dmesg log or take screenshots. This is a picture from my other phone. Is there a different way to grab the log?

In vanilla TWRP_zl1_20170311 if i choose reboot in recovery mode it always reboot in system mode

Can this new TWRP version be used without MultiROM? I currently use the build of codeworkx (https://forum.xda-developers.com/le-pro3/development/lineageos-development-t3553180).

flotux said:
Can this new TWRP version be used without MultiROM? I currently use the build of codeworkx (https://forum.xda-developers.com/le-pro3/development/lineageos-development-t3553180).
Click to expand...
Click to collapse
Sure. TWRP is vanilla, TWRP_multirom (suffix) is for MultiROM which can also be used without MultiROM without problems.
Vanilla: TWRP_zl1_20170311.img
MultiROM: TWRP_multirom_zl1_20170302-01.img
MultiROM stuff is never pushed to Android File Host because I need a static download URL for the MultiROM app and AFH servers aren't static, they shut down every day and switch the file in their servers so it rotates every time.
giogio1 said:
In vanilla TWRP_zl1_20170311 if i choose reboot in recovery mode it always reboot in system mode
Click to expand...
Click to collapse
Seems to boot fine to recovery for me, not encrypted.

Related

[UBL] Latest TWRP with f2fs support for Xperia SP (huashan)

http://forum.xda-developers.com/xpe.../recovery-twrp-3-0-0-touch-recovery-t3309938/
This is deprecated.
In this thread I'll share the .img files of the latest TWRP available for our device, so you can flash them with Rashr/PhilZ/Cyanogen recovery.
Disclaimer:
you are responsible for what you do. If your device stops working after you follow this guide, it's not my fault. However, as usual, if you do things in a correct way, you won't face any problems.
Requirements:
any ROM with any kernel
unlocked bootloader
Don't flash it if you have got a locked bootloader!
Features:
up-to-date source
flashable signed zip
f2fs support
Changelog:
TWRP 2.8.7.0_8
- other cleanups
- startup now is not slow! It just takes 3 - 4 seconds!
- Reboot bug is fixed - maybe
TWRP 2.8.7.0_7
- optimizations and cleanups
TWRP 2.8.7.0_6
- f2fs for /system is supported (this is for Temasek users)
TWRP 2.8.7.0_5
- f2fs support improved
- minor optimizations
- less overheating
TWRP 2.8.7.0_4
- attempt to fix issues with reboot option
TWRP 2.8.7.0_3
- signed flashable zip added
TWRP 2.8.7.0_2
- f2fs bugs fixed
- fixed overheating
How to install:
flash the zip through any recovery (even Cyanogen recovery!)
Download from Android File Host:
[url]https://www.androidfilehost.com/?fid=24052804347826443[/URL]
Stock FOTAKernel to remove any recovery (included this one): [url]http://forum.xda-developers.com/xperia-sp/general/stock-components-flashable-zips-t3184111[/URL]
Be sure to select the right variant of your device!
Thanks to:
@[NUT]
@antr34
@TechnoSparks
This work in miui v6
Thanks a lot for this quick update :thumbup:
Working fine on AICP's official nightlies with stock kernel.
The TITAN has landed. Hide your works from this critic! The official maintainer of the XSP Lollipop and M Hub.
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
pilger said:
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
Click to expand...
Click to collapse
I use it and i cant flash nothing
Guizão BR said:
I use it and i cant flash nothing
Click to expand...
Click to collapse
What is the output of the command? Does it throw you an error or anything?
@pilger i'm here, what to do next?
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
pilger said:
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
Click to expand...
Click to collapse
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
J73 said:
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
Click to expand...
Click to collapse
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
pilger said:
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
Click to expand...
Click to collapse
Thanks to you! All's well now, I'm so glad to have TWRP again thank you!
pilger said:
What is the output of the command? Does it throw you an error or anything?
Click to expand...
Click to collapse
Sorry i Forgot to edit the play, this have more time to flash
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Tomoms said:
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Click to expand...
Click to collapse
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
kunal9007 said:
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Tomoms said:
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Click to expand...
Click to collapse
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
kunal9007 said:
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Well, strange. f2fs volumes couldn't be mounted.
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Adrian DC said:
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Click to expand...
Click to collapse
just realized that I didn't had tangerine installed i was on first build of official cm and then before flashing radium i formated to f2fs
Sent from my XT1033 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------
and i flashed tangerine after atleast 1 day use of stock kernel
Sent from my XT1033 using Tapatalk

(Discontinued) Prime 6.5/6.6/7.4.2 OEM V12/V17 flashed Twrp recovery (Discontinued)

http://www.gsmarena.com/blu_r1_hd-8171.php
BLU R1 HD - 16 GB - Black - Prime Exclusive - with Lockscreen Offers & Ads
This is a Prime stock 6.5 rom, this rom comes from my phone, not rooted unmodified stock rom.
The purpose of this thread is to be able to flash stock or custom roms for Prime R1HD via Twrp.
You need to either have twrp installed or be able to boot into twrp to install this rom.
I currently just boot into twrp, I still have stock recovery installed, my bootloader is unlocked.
I have downloaded @ColtonDRG normal-stock-oob which is V12 non prime version, I checked the permissions on the system to see if 6.5 and V12 used different permission they use the same.
So a V12 rom can be made from my exact stock_rom_R1HD_6.5.zip, I may or may not provide a non prime version, even if I don't all a user has to do it open my stock_rom_R1HD_6.5.zip replace system and boot.img with non prime zip and flash.
There are two twrp recoveries one I just made and one made by @lopestom I had to get the rom compliant with both recoveries, @lopestom was the first recovery available for R1HD and allows backing up and restoring of many partitions, I am going to use his recovery.fstab, but remove the partitions backup and restore I don't use.
both recoveries at one time or other would throw an error
Code:
ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
I have now fixed that so neither recovery error, any other recovery that might show up, that person will have to fix his own, for now two recoveries can flash my rom, the one I made and @lopestom
To install download rom and recovery if you don't already have twrp.
Rom 0cee0d831502a2a867f036d951c3c78c stock_rom_R1HD_6.5.zip
https://www.androidfilehost.com/?fid=24713784966774808
Twrp recovery fbfe25ff742b2e994e45deeff0e3cfb7 R1HD_TWRP_recovery.img
https://www.androidfilehost.com/?fid=24713784966774807
@ColtonDRG non prime rom 77e85918d63de289423006ee3911f580 normal-stock-oob.zip
https://www.androidfilehost.com/?fid=24713784966774846
stock_rom_R1HD_6.6.zip (stock 6.6 rom is stock 6.6 rom minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img from 6.6, so this rom is safe to use.)
https://www.androidfilehost.com/?fid=24727338994368677
Modified_rom_R1HD_6.6.zip (Modified_rom is stock 6.6 rom minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img from 6.6, as well as amazon apps, no ads, updater disabled, so this rom is safe to use.)
https://www.androidfilehost.com/?fid=24727338994368678
Modified_rom_R1HD_7.4.2.zip (Modified_rom is stock 7.4.2 rom minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img from 7.4.2, as well as amazon apps, no ads, updater enabled, so this rom is safe to use.)
https://www.androidfilehost.com/?fid=313042859668275704
stock_V17_OEM_rom.zip minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img
https://www.androidfilehost.com/?fid=457095661767119968
Settings_V17.zip , This is settings from v12 ported to V17 to allow OEM unlocking and Navigation bar.
https://www.mediafire.com/?ui1r5w1khg8k5j7
place on sdcard
boot into twrp
install
reboot
Credits
@ColtonDRG
@lopestom
@bluefirebird
@onlykhaz
@ss2man44
@AtomicFizzle
I like your recovery. Do you mind if I mirror it?
ColtonDRG said:
I like your recovery. Do you mind if I mirror it?
Click to expand...
Click to collapse
No problem, upload it, where ever you need to.
If it's okay I'll get a non-Prime one up in a bit.
Edit 1: Dang it I can't get the system.img file to extract. Using this tool on Windows 10 Pro x64 - http://forum.xda-developers.com/and...tool-tool-unpack-repack-dat-img-v2-0-t3284806
AngryManMLS said:
If it's okay I'll get a non-Prime one up in a bit.
Edit 1: Dang it I can't get the system.img file to extract. Using this tool on Windows 10 Pro x64 - http://forum.xda-developers.com/and...tool-tool-unpack-repack-dat-img-v2-0-t3284806
Click to expand...
Click to collapse
I just mounted it via Linux it's ext4, I don't use windows, only Linux.
Sent from my NS-P08A7100 using Tapatalk
so, since the rest of partitions have been hidden from new recovery. are they generaly safe from change. or should a backup still be kept for them?
mrmazak said:
so, since the rest of partitions have been hidden from new recovery. are they generaly safe from change. or should a backup still be kept for them?
Click to expand...
Click to collapse
There are two twrp recoveries, use the one that you want, if you want to back up and restore more partitions use first recovery.
Blu has put out official splash tool ROM for Prime version today, will restore entire phone to stock.
Will be sometime before we get it, nothing on non prime.
Sent from my BLU ENERGY X PLUS using Tapatalk
vampirefo said:
There are two twrp recoveries, use the one that you want, if you want to back up and restore more partitions use first recovery.
Blu has put out official splash tool ROM for Prime version today, will restore entire phone to stock.
Will be sometime before we get it, nothing on non prime.
Sent from my BLU ENERGY X PLUS using Tapatalk
Click to expand...
Click to collapse
thats big news. do you have any links, i do see blu website has link for R1 support but cant find anything downloadable
mrmazak said:
thats big news. do you have any links,
Click to expand...
Click to collapse
They are private links right now, once I get the ROM we will go from there.
Sent from my BLU ENERGY X PLUS using Tapatalk
vampirefo said:
I just mounted it via Linux it's ext4, I don't use windows, only Linux.
Click to expand...
Click to collapse
I found an ext4 extract program for Windows. Placed the /system directory into the ROM folder along with the boot.img but it failed to install. I'll investigate further tomorrow unless if you manage to put up an flashable ROM with the stock/OEM non-ad stuff.
AngryManMLS said:
I found an ext4 extract program for Windows. Placed the /system directory into the ROM folder along with the boot.img but it failed to install. I'll investigate further tomorrow unless if you manage to put up an flashable ROM with the stock/OEM non-ad stuff.
Click to expand...
Click to collapse
Uploading now.
77e85918d63de289423006ee3911f580 /home/vampirefo/Downloads/normal-stock-oob/normal-stock-oob.zip
My computer has been running hard today, between son doing his school work, me making roms, recovery, and just now got cm13 to finish compiling, it's for a similar device, it's an mtk phone, the point is to get the source set up to build.
Code:
make: Leaving directory '/home/vampirefo/Desktop/cm13'
#### make completed successfully (05:17:01 (hh:mm:ss)) ####
[email protected]:~/Desktop/cm131$
@ColtonDRG non prime rom has been added to first page.
vampirefo said:
@ColtonDRG non prime rom has been added to first page.
Click to expand...
Click to collapse
thanks for stock flashable zip
vampirefo said:
@ColtonDRG non prime rom has been added to first page.
Click to expand...
Click to collapse
when i try to install
non prime rom 77e85918d63de289423006ee3911f580 normal-stock-oob.zip
i just rename it to test-Ril
getting this error 7
ColtonDRG how to create update script
rameshurfrnd1 said:
ColtonDRG how to create update script
Click to expand...
Click to collapse
It says your system is mounted, your system needs to be unmounted.
Device or resource busy, means twrp can't mount system.
Sent from my BLU ENERGY X PLUS using Tapatalk
vampirefo said:
It says your system is mounted, your system needs to be unmounted.
Device or resource busy, means twrp can't mount system.
Sent from my BLU ENERGY X PLUS using Tapatalk
Click to expand...
Click to collapse
after wiping i just reboot to recovery and flashed successfully
rameshurfrnd1 said:
how to fix it
Click to expand...
Click to collapse
Click mount uncheck system, and uncheck mount system as ro
Sent from my BLU ENERGY X PLUS using Tapatalk
rameshurfrnd1 said:
after wiping i just reboot to recovery and flashed successfully
Click to expand...
Click to collapse
What ever works. [emoji2] [emoji2] [emoji2]
Sent from my BLU ENERGY X PLUS using Tapatalk
vampirefo said:
What ever works. [emoji2] [emoji2] [emoji2]
Sent from my BLU ENERGY X PLUS using Tapatalk
Click to expand...
Click to collapse
i am try to get 4g lte band in india
by changing the baseband
kindly help me to fix this

[ROM][DEB|FLO][7.1.1][UNOFFICIAL] LineageOS/CyanogenMod 14.1 Nightlies

So... CyanogenMod is dead. LineageOS is taking it's place. The ROM is basically CyanogenMod but with changes to the name.
This is completely 'stock' from their source code and will be prerooted (under Developer options in Settings)
Changelog is available at LineageOS Gerrit
There are no apparent bugs, but any bug reports will be welcome.
Gapps are available at OpenGapps.
These should build almost every night
Installation
Download latest release from here
Install it in TWRP recovery
Install the downloaded opengapps package
XDA:DevDB Information
LineageOS/CyanogenMod 14.1 Nightlies, ROM for the Nexus 7 (2013)
Contributors
hazzer
Source Code: https://github.com/LineageOS/
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: Nightly
Created 2017-01-08
Last Updated 2017-01-08
May you upload some Screenshots? Can I dirty flash? I'm on CyanogenMod 14.1 20161225
Just clean installed, no big difference from Cyanogen,.. Not even the logo.
Everything seams to be working as it did on cyanogen nightly.
Regards,
Me
Thank you
Sent from my Nexus 6 using XDA Free mobile app
Thanks for this, great job.
@hazzer I'd like to grab your image but your website seems down?
Edit: I see it's back up, thanks!
Can you enable your rom to use the built in updater?
Which opengapps do you suggest?
Poslano z mojega ONE E1003 z uporabo Tapatalk
@hazzer there are still two bugs first being hangouts crashes when you try to message someone over unless it's from the notification. This works fine on my other lineage devices. Second is Allo's message sounds use a don't play because it doesn't like the codec. This works in regular Android but seems to be a Lineage specific bug.
@jstsmblaz
pico works fine for me.
Sent from my Nexus 7 using XDA Labs
Edit :
(I use pico for testing. If I need more I use a gapps-config file.)
Lost Root
Root access in Developer Options is greyed out. Only options are Disable and ADB. I am using TWRP 3.0.2. Yes, bootloader is unlocked. I had root with CM 1/25/2016 and when restored to that version, Root returned.
When I installed 1/16/2017, I did not wipe Data.
Am I missing something in Developer Options? Any thoughts?
I stated at the start of this 'project', I am balancing this alongside school work. Unfortunately, it's just become too much to manage alongside time consuming A levels.
This means:
Builds will be less frequent (perhaps once or twice a week)
I'm not going to be available on XDA or IRC very often (if at all)
I apologise I haven't been the best at communicating or fixing issues, but I just didn't envisage having to invest the amount of time I have.
If anyone would like to take over, give me a shout. You can borrow my server for hosting and my blog article if you're willing to learn.
You might see me again sometime around July. Thanks everyone for helping me with an incredible learning process into the depths of Android.
pclewis said:
Root access in Developer Options is greyed out. Only options are Disable and ADB. I am using TWRP 3.0.2. Yes, bootloader is unlocked. I had root with CM 1/25/2016 and when restored to that version, Root returned.
When I installed 1/16/2017, I did not wipe Data.
Am I missing something in Developer Options? Any thoughts?
Click to expand...
Click to collapse
When I first starting doing builds (before Lineage rebrand, and before CM shutdown), I disabled root for personal reasons (passing SafetyNet by default). I achieved this by building the ROM as 'user' instead of 'userdebug', which disables and also doesn't install the su binary to /system.
When the project transitioned to Lineage (after the CM shutdown), I began to build as userdebug (this is the default) again, to be close to official nightlies as possible.
Members of the Lineage team decided to (by default) remove root from Lineage builds (in the last few days), so the ROM will pass SafetyNet by default. This means root is now disabled in my builds (as I haven't explicitly enabled root).
If you would like root in the ROM, (SuperSU) or (Magisk+phh) is the way to go
SuperSU
hazzer said:
When I first starting doing builds (before Lineage rebrand, and before CM shutdown), I disabled root for personal reasons (passing SafetyNet by default). I achieved this by building the ROM as 'user' instead of 'userdebug', which disables and also doesn't install the su binary to /system.
When the project transitioned to Lineage (after the CM shutdown), I began to build as userdebug (this is the default) again, to be close to official nightlies as possible.
Members of the Lineage team decided to (by default) remove root from Lineage builds (in the last few days), so the ROM will pass SafetyNet by default. This means root is now disabled in my builds (as I haven't explicitly enabled root).
If you would like root in the ROM, (SuperSU) or (Magisk+phh) is the way to go
Click to expand...
Click to collapse
SuperSU will not root with TWRP, since root is built into TWRP. It just looks for a missing binary,
@pclewis
That's odd. What version of twrp and SuperSU are you using?
I have been using SuperSU with no problems since the cm-20161231 build.
- I didn't try phh, normally I use phh when SuperSU does not work.
Note :
I initially installed the rom, gapps and SuperSU using twrp. - Completely clean install.
Sent from my Nexus 7 using XDA Labs
ipdev said:
@pclewis
That's odd. What version of twrp and SuperSU are you using?
I have been using SuperSU with no problems since the cm-20161231 build.
- I didn't try phh, normally I use phh when SuperSU does not work.
Note :
I initially installed the rom, gapps and SuperSU using twrp. - Completely clean install.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
I use TWRP 3.0.2 and it has root built in. Works fine with 1/25/2016 but root is lost with the Linage. I tried SuperSU 2.79, but it is looking for binary that does not exist.
The decision to not support root is not consistent with the Linage teams. I have updated two phones to Linage since CW and both maintain root. I think they need to reconsider. Most of us run TWRP and simply want to root with that.
So im on the 1112017 build and was wondering if anyone else is experiencing screen rotation issues. Is it a software issue or just my tablet being old?
pclewis said:
I use TWRP 3.0.2 ….. I tried SuperSU 2.79
Click to expand...
Click to collapse
Thanks, I wanted to make sure I was using the same files.
I think you may have a few things mixed up.
pclewis said:
The decision to not support root is not consistent with the Linage teams.
Click to expand...
Click to collapse
Lineage changed that. (With the current and newer builds the biggest change the user will see, is selinux enforcing and non rooted. This way clean installs with work with banking apps and pass SafetyNet.)
pclewis said:
I use TWRP 3.0.2 and it has root built in. Works fine with 1/25/2016 but root is lost with the Linage.
Click to expand...
Click to collapse
This has nothing to do with TWRP itself. Lineage removed root access from their builds.
TWRP has root access to modify your device. - All recoveries do.
(Recovery is limited by the developer depending on what they allow the user to do. This is why we can not just install what we want with stock recovery and need custom recoveries like TWRP or Clockwork.)
TWRP will NOT root your rom automatically, you will need to install a su and manager.
SuperSU (Download link in OP of thread.)
SR3-SuperSU-v2.79-SR3-20170114223742.zip
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
SuperSU-v2.79-201612051815.zip
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
- - - Now back to your prior post.
pclewis said:
SuperSU will not root with TWRP ..... It just looks for a missing binary,
Click to expand...
Click to collapse
Initially you can not install su binary from the apk.
Install one of the following using twrp. (These are the current SuperSU zip files.)
SR3-SuperSU-v2.79-SR3-20170114223742.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
SuperSU-v2.79-201612051815.zip
All three worked for me regardless.
I installed 20170113 and pico gapps only. Ran through the setup and then dirty flashed 20170116. (Lost root access.) Rebooted into twrp and installed SuperSU-v2.79-201612051815.zip. Rebooted and SuperSU took over root access.
Sent from my Nexus 7 using XDA Labs
20170120 : lineage boot animation?
Sent from my SM-G935F using XDA-Developers Legacy app
ipdev said:
Thanks, I wanted to make sure I was using the same files.
I think you may have a few things mixed up.
Lineage changed that. (With the current and newer builds the biggest change the user will see, is selinux enforcing and non rooted. This way clean installs with work with banking apps and pass SafetyNet.)
This has nothing to do with TWRP itself. Lineage removed root access from their builds.
TWRP has root access to modify your device. - All recoveries do.
(Recovery is limited by the developer depending on what they allow the user to do. This is why we can not just install what we want with stock recovery and need custom recoveries like TWRP or Clockwork.)
TWRP will NOT root your rom automatically, you will need to install a su and manager.
SuperSU (Download link in OP of thread.)
SR3-SuperSU-v2.79-SR3-20170114223742.zip
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
SuperSU-v2.79-201612051815.zip
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
- - - Now back to your prior post.
Initially you can not install su binary from the apk.
Install one of the following using twrp. (These are the current SuperSU zip files.)
SR3-SuperSU-v2.79-SR3-20170114223742.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
SuperSU-v2.79-201612051815.zip
All three worked for me regardless.
I installed 20170113 and pico gapps only. Ran through the setup and then dirty flashed 20170116. (Lost root access.) Rebooted into twrp and installed SuperSU-v2.79-201612051815.zip. Rebooted and SuperSU took over root access.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
Thanks, I get it. I really don't root the phones I use. I let them update OTA and need the security. The older ones I used to use Titanium and needed root. Now a TWRP BU is fine and I really don't need root I suppose. Thanks for your reply and I understand the logic.
Why do some devices allow root to be turned off and on in developer options for either apps, adb or both?
BTW, just installed 11/20/2017. Seems to work fine and does not have root. I will run this for a while. Thanks again?
Phil

[RECOVERY][G3][F400] TWRP-3.1.1 (Testing/170519)

TeamWin's TWRP Touch Recovery for LG G3 - currently available only for F400 variants​https://twrp.me/
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/​
Flashing Instructions
To install recovery images use Flashify / Rashr from Play Store or flash in your current recovery. Otherwise do the following:
1. Go to install, find and select the Images... button.
2. Browse to the image that you downloaded and select it.
3. Choose recovery and swipe to flash.
OR
1. Move recovery.img to internal storage.
2. Open terminal window/command prompt to execute following commands
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
About this TWRP
compiled on LineageOS-14.1 source
always up-to-date
fixed screen brightness
permissive selinux
disabled logd/logcat in recovery
fuse exfat, ntfs-3g, jpeg, usb-otg support
external storage as default storage
touch to wake
backup of all partitions including modem, efs
crypto/decryption may work or not..
Changelog
* 170430
- Initial Build
- Disabled HW crypto due to build fails
* 170501
- Deleted unused flags
- Add back HW crypto
- exfat support
* 170507
- Disabled logd/logcat (fix for "device or resource busy", hopefully)
* 170519
- Updated to v3.1.1
- Fix Aroma Installer crash (hopefully)
Known issues
ZIP files with date check assert can't be installed (eg. crDroid) - Users should delete date check assert in binary by themselves.
AROMA Installer stucks at loading - will be fixed soon..
Download Links
Unofficial | Official
Sources​
https://github.com/TheNoFace/android_device_lge_g3-common-TWRP/tree/twrp
(Based on https://review.lineageos.org/#/c/160056/)​
Remember to do backup of your current recovery before installing​
Any plans for suporting other G3 variants in future?
@fprhqkrtk303: Now have 2 version twrp to flash. Which one to choose to flash? Unofficial or official? Thanks!
Official TWRP for D855 is so bad... sorry to say that. It doesn't work properly and even if LineageOS recommends it it's just not able to flash LOS builds.
When you want to reboot in recovery it hangs in a bootloop and when you want to shut the device off it just turns on back. So far we only have the unofficial version for D855 fully working.
ahk31 said:
Any plans for suporting other G3 variants in future?
Click to expand...
Click to collapse
Planning to support more devices when F400 version is stable.
You can build your own TWRP using my source.
@chuyennho184 @andrewKode Official version from TWRP uses older device tree and actually no one maintains. Recommend using unofficial version.
@fprhqkrtk303: I saw update firmware on March 22th for F400 variants but I don't have a link. Do you have a link? Thanks for bother you.
Updated to v3.1.1 (170519)
fprhqkrtk303 said:
Updated to v3.1.1 (170519)
Click to expand...
Click to collapse
Is aroma bootloop problem fixed in this new version?
MESA said:
Is aroma bootloop problem fixed in this new version?
Click to expand...
Click to collapse
Not tested yet. Can you check?
fprhqkrtk303 said:
Not tested yet. Can you check?
Click to expand...
Click to collapse
Yes. Tried it yesterday. Bootloop problem is still present.
andrewKode said:
Official TWRP for D855 is so bad... sorry to say that. It doesn't work properly and even if LineageOS recommends it it's just not able to flash LOS builds.
When you want to reboot in recovery it hangs in a bootloop and when you want to shut the device off it just turns on back. So far we only have the unofficial version for D855 fully working.
Click to expand...
Click to collapse
LoL i maintain twrp for d855 i don't have any issue with that recovery(3.1.1) fully tested..
and this problem cause by bootloader..
or you mean this
Fixed rebooting when no OS is present (Dees_Troy)
"unofficial version for D855 fully working."
Nope dadi11 twrp encrypt no work.. ;]
ZjemCiKolege said:
LoL i maintain twrp for d855 i don't have any issue with that recovery(3.1.1) fully tested..
and this problem cause by bootloader..
or you mean this
Fixed rebooting when no OS is present (Dees_Troy)
"unofficial version for D855 fully working."
Nope dadi11 twrp encrypt no work.. ;]
Click to expand...
Click to collapse
Dude, Idk what you're maintaining but this is what happens:
- TWRP sometimes does not reboot back in recovery (it hangs on LG screen)
- hangs on flashing LineageOS
- When chosed to turn off the device from the recovery it turns back ON right after it shuts down.
andrewKode said:
Dude, Idk what you're maintaining but this is what happens:
- TWRP sometimes does not reboot back in recovery (it hangs on LG screen)
- hangs on flashing LineageOS
- When chosed to turn off the device from the recovery it turns back ON right after it shuts down.
Click to expand...
Click to collapse
1. I try but did not happen.
2. Build of lineage?(i flash each version from february to 21.04) no any issue.
3. Issue of custom rom(problem with turn on charger and boot same issue..) ;]
MESA said:
Is aroma bootloop problem fixed in this new version?
Click to expand...
Click to collapse
Hello, apparently no...
https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
If it's a software problem, it would be the problem of AROMA devs, but if it's related to software keys incompatibility it's will be the work of TWRP devs.

[RECOVERY][UNOFFICIAL][09/26] TWRP 3.1.1 w/F2FS for Shamu

No longer supported
Unofficial TWRP 3.1.1 w/F2FS
> For the Nexus 6 Shamu
This work is inspired by @The Flash's F2FS TWRP builds. I based this build off of the TWRP Minimal Repo.​​Features:
TWRP 3.1.1
F2FS Mounting and Formatting supported (En/Decryption not supported, however)
Built atop my kernel
Works
Changelog:
3.1.1-3
Updated sources to 7.1.2_r33, which includes updated f2fs-tools (1.8.0)
Minor GUI tweaks (splash screen, odd gap under "Advanced")
Bump to subversion 3
Installation:
You should know the drill of installing custom recoveries if you found this thread, but anyways:
Have an UNLOCKED Bootloader
Boot to fastboot/bootloader mode (Power + Vol Down from power off)
In adb (replace X with appropriate subversion):
Code:
fastboot flash recovery twrp-3.1.1_X-f2fs-unofficial-shamu.img
You can now reboot to your shiny, new TWRP!
How Do I convert to F2FS?
Backup important data to an EXTERNAL source; if formatting /data, entire internal sd will be wiped.
Ensure your kernel/kernel you will flash supports F2FS. You can use my kernel if you desire.
Reboot to this (or any other) F2FS supported TWRP
Go to -> Wipe -> Advanced Wipe
Tick the desired partition you want to format (ONLY do /data and/or /cache)
Select "Repair or Change Filesystem"
Select "Change File System"
Select "F2FS"
Swipe to Change
Done. Flash all your stuff!
Disclaimer:
I am not responsible for broken devices etc... Flash at your own risk. I am also not affiliated with the official TWRP crew nor Omni ROMs, so please don't complain to them about bugs unique to my own builds. ​
Sources:
Manifest
TWRP Recovery
Device Tree
Kernel​
XDA:DevDB Information
Unofficial TWRP for Shamu w/F2FS, Tool/Utility for the Nexus 6
Contributors
Black_Hat01, Omni Rom, and the great devs of TWRP itself
Source Code: https://github.com/BlackHat01/
Version Information
Status: No Longer Updated
Current Stable Version: 3.1.1-3
Stable Release Date: 2017-09-26
Created 2017-06-27
Last Updated 2018-02-10
Downloads
Download Latest 09/26 Build - 3.1.1-3
How do i make it keep my settings. Every time i boot into twrp i have to swipe to allow modifications and need to set settings again. Also it does not see my backups i made with previous twrp 3.1.1-0
Thanks a lot for this. Does it properly decrypt F2FS data?
Neejay said:
Thanks a lot for this. Does it properly decrypt F2FS data?
Click to expand...
Click to collapse
I don't use encryption so I cannot say. If you can test it for me that would be appreciated
UPDATE:
TWRP Official 3.1.0 changelog states TWRP will try to mount both ext4 and f2fs on decrypt, so It should work.
TMG1961 said:
How do i make it keep my settings. Every time i boot into twrp i have to swipe to allow modifications and need to set settings again. Also it does not see my backups i made with previous twrp 3.1.1-0
Click to expand...
Click to collapse
It should not reset your settings every time you boot into recovery, unless there is something wrong with your /sdcard/TWRP folder. Can you send a recovery log (Advanced > Copy Log)?
Will do that after finishing the install of the rom i am doing now.
TMG1961 said:
Will do that after finishing the install of the rom i am doing now.
Click to expand...
Click to collapse
Thank you. I ask because I am not having that issue at all. Maybe also try re-flashing recovery via fastboot before everything too.
what i did was this. Booted into bootloader. erased recovery, flashd your recovery and booted into it. wiped to allow changes and made changges to settings. Then booted back into rom. The rom i tried it with was stock 7.1.1.
I just finished installing velocity rom and flashed your twrp, same result. I did copy the log. said in twrp that it was copied to /data/media/recovery.log but the log is no were to be found on the phone. Did search the whole phone with root explorer
---------- Post added at 20:00 ---------- Previous post was at 19:59 ----------
when i try to do a backup i get error unable to mount storage
---------- Post added at 20:10 ---------- Previous post was at 20:00 ----------
I think the problem is something else. Not sure but twrp does not see my storage
Black_Hat01 said:
I don't use encryption so I cannot say. If you can test it for me that would be appreciated
UPDATE:
TWRP Official 3.1.0 changelog states TWRP will try to mount both ext4 and f2fs on decrypt, so It should work.
Click to expand...
Click to collapse
Unfortunately, it doesn't work. It doesn't recognize my unlock pattern and won't decrypt. I had to go back to xanaxdroid's 3.0.2.0 twrp for it to work
I did flash the previous twrp and copied the log file. Not sure if that contains what you need ut adding it so you can have a look
Neejay said:
Unfortunately, it doesn't work. It doesn't recognize my unlock pattern and won't decrypt. I had to go back to xanaxdroid's 3.0.2.0 twrp for it to work
Click to expand...
Click to collapse
Thanks for the update. Will look into it.
Black_Hat01 said:
Thanks for the update. Will look into it.
Click to expand...
Click to collapse
No problem. I tried to look for his source, but couldn't find one for shamu directly. Here's where I downloaded his img (if it helps at all): https://forum.xda-developers.com/showpost.php?p=70452221&postcount=29
TMG1961 said:
I did flash the previous twrp and copied the log file. Not sure if that contains what you need ut adding it so you can have a look
Click to expand...
Click to collapse
Can you flash my twrp and send log please? It is the correct log. I just need to see what's going on with mine. Thanks.
i can but after flashing your twrp then flash the old one again and copy the log to the sdcard ? Cause yours says it copies the log but there is no log on the sdcard.
TMG1961 said:
i can but after flashing your twrp then flash the old one again and copy the log to the sdcard ? Cause yours says it copies the log but there is no log on the sdcard.
Click to expand...
Click to collapse
That's odd. I was on Flash's 3.1.0-4 F2FS build and flashed mine right over that build and everything works fine for me (log copying works, settings stick fine, etc..), so maybe try flashing his build, then mine. Without a log, I can't really do much, since I, and nobody else yet has experienced the same issues. I'm going to do some work on it today, and I'll try to get a new build out tonight.
Thanks for your time and help. I downloaded 3.1.0-4 F2FS and 3.1.1-6 F2FS but on both the same. All version dont show anything on the sdcard when i go to advanced/file manager in twrp. So no idea what is causing it but almost sure the problem is on my side.
TMG1961 said:
Thanks for your time and help. I downloaded 3.1.0-4 F2FS and 3.1.1-6 F2FS but on both the same. All version dont show anything on the sdcard when i go to advanced/file manager in twrp. So no idea what is causing it but almost sure the problem is on my side.
Click to expand...
Click to collapse
Perhaps it is just your device. Anyways, I uploaded a new build, maybe try this one out. If it does not, try reflashing stock twrp 3.1.1 and then coming back to an F2FS modified one. Hope the best.
Is there any difference between this and the TWRP F2FS builds found at http://nchancellor.net/Downloads/TWRP/shamu/ ?
TMG1961 said:
...I just finished installing velocity rom
Click to expand...
Click to collapse
I thought that ROM ceased development a long time ago? Happen to have any links with more info on it? https://www.android-port.de/themen/rom-n-7-1-1-velocity-shamu.9596/
espionage724 said:
Is there any difference between this and the TWRP F2FS builds found at http://nchancellor.net/Downloads/TWRP/shamu/ ?
Click to expand...
Click to collapse
Thing is, by the time I posted, I hadn't realized he updated his. But the things that are different are basically the kernel the recovery image is built with (we use our own kernels), and the support. I will be actively building and supporting while The Flash has pretty much moved on from shamu to angler. Any bugs that arise I will try to fix and I will always be trying to keep everything updated. Over time our builds will start to become more and more different.

Categories

Resources