Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16], a Tool/Utility for the HTC One S
Contributors
Dees_Troy, bigbiff
Version Information
Status: Stable
Current Stable Version: 2.6.3.0
Stable Release Date: 2013-09-16
Created 2013-09-16
Last Updated 2013-09-16
You guys are doing an amazing job, ROM will come these days!
Well, this is version 2.2.1 but wheres the changelog for it ?
I installed it anyway, but I like to see what changed :-3
EDIT:
Nevermind, this is for S3 >.<
Love it! Glad to see s3 getting some love too!
Sent from my HTC VLE_U using Tapatalk 2
Yeaaaaaaaaaah! Yes! Yes! Yesssss! Yeeees! Thank you million times!
Fantastic!
@Dees_ Troy
I seemed to find a little bug. The battery in recovery always shows 66%.
Hmmm. Using twrp I can't flash kernels unless I use Fastboot but others can. This isn't my first rodeo, and I'm able to flash roms fine. Actually I flah a rom with a stock boot.img in it and it still keeps the old kernel that I fast booted days before. Anyone know what this may be? Or of there is something I can do to correct this? I've tried unlock and relock. I've tried reinstalling twrp. I tried erasing boot but was unable to do so assuming cause I don't have s- off. I'm out if ideas.
Sent from my HTC VLE_U using xda premium
dsellers2 said:
Hmmm. Using twrp I can't flash kernels unless I use Fastboot but others can. This isn't my first rodeo, and I'm able to flash roms fine. Actually I flah a rom with a stock boot.img in it and it still keeps the old kernel that I fast booted days before. Anyone know what this may be? Or of there is something I can do to correct this? I've tried unlock and relock. I've tried reinstalling twrp. I tried erasing boot but was unable to do so assuming cause I don't have s- off. I'm out if ideas.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Yeah I've learned that yesterday that this is a well known issue with some of the htc. There is two waya,one you have described to flash it manually in fastboot and the other is a workaround that twrp supports. It is called HTC dumlock,just search on their official page how to use it.
Sent from my HTC One S using xda app-developers app
Thank dev. For S3 development.
Sent from my HTC One S using xda app-developers app
I got my Villec2 Unlocked with htcdev.com site
but i can't flash any recovery, Why?
I found that this recovery works on my hts one s (my i mean villec2)
i tried to do it couple of times with cmd and fastboot, and then with HTS ONE S AIO KIT
every time it says that sending is ok, and writing i ok... but can't go into recovery got only htc sentence...
Do you guys got any solution? whey on that threat above some people with s3 says that they flashed recovery and i can't do it?
Download GooManager at Playstore and then use it to "Install OpenRecoveryScript" That will install TWRP
Wyall said:
Download GooManager at Playstore and then use it to "Install OpenRecoveryScript" That will install TWRP
Click to expand...
Click to collapse
I tired that method also without any progress,
GooManager downloaded img then i saw little box that recovery installed successfully, But unfortunately still cant use recovery
Do you have root? And did you use the Reboot to Recovery Option in GooManager?
Wyall said:
Do you have root? And did you use the Reboot to Recovery Option in GooManager?
Click to expand...
Click to collapse
I just got unlocked Phone with htcdev, i thought that i need to Flash Recovery before i can Flash superSu like i saw in torxx guide. Can i Flash superSu like i try to Flash Recovery? Which one shall i choose?
With GooManager i restart to Recovery, the result was the same....
And still i count on your help in flashing Recovery on my HTC
Regards in advance
First you need to unlock, then you can root and after that install a Custom Recovery
To Root your device, follow that guide: http://www.modaco.com/topic/355509-testing-villec-superboot/
Wyall said:
First you need to unlock, then you can root and after that install a Custom Recovery
To Root your device, follow that guide: http://www.modaco.com/topic/355509-testing-villec-superboot/
Click to expand...
Click to collapse
So now i got root (method from link above) and i got custom recovery installed with gooManager method. Sweet. i for other users it's very important to got root first
Updated to 2.2.2.0!
Dees_Troy said:
Updated to 2.2.2.0!
Click to expand...
Click to collapse
Hi!! Has full wipe partitions in this recovery?
Thanks?
Do it work with S4 or just only S3? Thanks
Hey all, I read somewhere (cant remember where anymore) that due to the extra security (encryption) TWRP and CWM would be having issues with android 5.0 as they cant make backups of the data and restore it properly, is this true or have it perhaps been fixed in new versions of TWRP?
cheers all!
Natherul said:
Hey all, I read somewhere (cant remember where anymore) that due to the extra security (encryption) TWRP and CWM would be having issues with android 5.0 as they cant make backups of the data and restore it properly, is this true or have it perhaps been fixed in new versions of TWRP?
cheers all!
Click to expand...
Click to collapse
If you manually encrypt the Dev preview, TWRP cannot access the storage, so cannot flash zips etc. There was a belief that encryption will be enforced by default on the full release. I am still not sure if that will be teh case. The AOSP builds that came out over the last 2 days are not encrypted by default. So currently, by default you are OK. If you choose to encrypt, You're screwed from a recovery perspective. When the final, full release comes out - I don't know what will happen.
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 other devices too. (See the list below to see if your device is supported)
Disclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about the features in this tool
* before using it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Background
The Android CDD (Compatibility Definition Document) suggests demands that all devices with the appropriate horse power SHOULD MUST enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. Full-disk-encryption 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 current devices it's the CPU's task. Even though modern devices have quite fast CPU 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 scientific measurements though)
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. Additionally, Google's stock ROMs always have forced encryption enabled on newer devices.
Because performance is important to me and at least 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, if necessary, 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)
LG Nexus 5X (bullhead)
Huawei Nexus 6P (angler)
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.
v8 - Added support for LG Nexus 5X (bullhead) and Huawei Nexus 6P (angler)
What do I need to make this work?
A supported device
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.
GibHub: https://github.com/gladiac1337/fed-patcher
XDA:DevDB Information
FED-Patcher, Tool/Utility for all devices (see above for details)
Contributors
gladiac, rovo89
Version Information
Status: Beta
Current Beta Version: v8
Beta Release Date: 2015-10-27
Created 2015-10-27
Last Updated 2016-10-23
Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.
I'm currently running stock Marshmallow on my Nexus 6 and i plan to stay like that, but would like to test my device with ForceEncrypt disabled. Here are my doubts.
1 - Does this work on stock?
2 - Would i be able to flash the monthly security update images without having to wipe my device every time?
3 - In your opinion, do the speed gains justify the all the work?
Thanks in advance.
cyberon said:
Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.
I'm currently on stock Marshmallow and i plan to stay like that, but would like to test my device with forcencrypt disabled. Here are my doubts.
1 - Does this work on stock?
2 - Would i be able to flash the monthly security update images without having to wipe my device every time?
3 - In your opinion, do the speed gains justify the all the work?
Thanks in advance.
Click to expand...
Click to collapse
Hi @cyberon,
good questions!
Yes, FED-Patcher works on stock! Marshmallow made it necessary to do a new release, v7, to get rid of an error message at boot but other than that, FED-Patcher works just fine on Android 6.
Well, I don't know how the monthly security-updates will be deployed. I guess it will be done by OTA (Over the Air) updates. OTA will probably not work after modifying the boot-image. However, flashing factory images should work just fine. Additionally, most of the time, OTA-zips are being posted here on xda or androidpolice whenever they become available so doing manual OTA updates is another possibility to do updates.
To get back to your question - wiping should not be necessary after an upgrade - be it via OTA or factory images. Google did a fantastic job with the upgrade-functionality in newer Android versions. However, whenever you do an update, be sure to run FED-Patcher afterwards because, in case the boot-partitions got updated, forced encryption will be in place again and on the first boot it will encrypt you device.
Well, I do all my tests on a HTC Nexus 9 (flounder). It is a pretty fast beast. However, on an unmodified stock rom, it was clearly tangible that the GUI had more latency than necessary. Apps loaded pretty slowly - compared to my Sony Xperia Z1 (honami) it took like twice as long to start youtube - and in general it just did not behave like a beast. This was why I started writing FED-Patcher. In my opinion it was worth my time. (it wasn't that much actually)
I hope I could help.
Enjoy, gladiac
Thanks for the quick and detailed answer @gladiac, now regarding point number 2.
I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.
Am i missing something?
cyberon said:
Thanks for the quick and detailed answer @gladiac, now regarding point number 2.
I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.
Click to expand...
Click to collapse
That's pretty much how I would do it. You don't even have to flash TWRP if you just skip flashing the recovery.img which is included in the factory-image package.
Thanks @gladiac, will try that way.
PS: I have a feeling that if we had this option added to a toolkit like Wugfresh Nexus Root Toolkit, it would be an instant success.
hi @gladiac
first of all thanks for your patch
I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?
Thanks a lot
Worked on my N9 - thanks!
provolinoo said:
hi @gladiac
first of all thanks for your patch
I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?
Thanks a lot
Click to expand...
Click to collapse
Hi @provolinoo,
well, FED Patcher will disable the forced encryption for you. However, SuperSU will not work so easily. The reason for that is that the stock ROM has SeLinux enabled in "enforcing" mode. SuperSU does not work without adding more SeLinux Policies to the stock ROM. Unfortunately, it's not in the scope of FED Patcher to add SeLinux policies for SuperSU. This should be done inside the flashable ZIP of SuperSU instead.
The last time I tested SuperSU with marshmallow stock was with version 2.52 BETA. It did not work. The result was a boot-loop because of one or more SeLinux denials. A little more info on that matter is here.
So, to get SuperSU working you would have to set SeLinux to "permissive" mode. Alternatively, you can use @Chainfire's boot.imgs to make SuperSU work.
Have fun, gladiac
Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9. Edit: I am using TWRP 2.8.7.1
The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?
Don't some major vendors allow the disabling of encryption from within Android?
Anyway, thanks for the patcher.
dmantilal said:
Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9.
The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?
Don't some major vendors allow the disabling of encryption from within Android?
Anyway, thanks for the patcher.
Click to expand...
Click to collapse
I agree, I love CM roms but their decision to force encryption when most of cm users are power-user is a nonsense
Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?
EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.
jamesalfred said:
Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?
EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.
Click to expand...
Click to collapse
Did you follow the directions and format the entire "data" partition?
dmantilal said:
Did you follow the directions and format the entire "data" partition?
Click to expand...
Click to collapse
I too have the same problem didnt work for me.
im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.
Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.
nextelbuddy said:
I too have the same problem didnt work for me.
im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.
Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.
Click to expand...
Click to collapse
It did not work because you did not follow the directions.
Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "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.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.
Give us more info so we can help (assuming you fid it right initially).
P.S. - 6.0 is M(arshmallow), not L(ollipop).
dmantilal said:
Did you follow the directions and format the entire "data" partition?
Click to expand...
Click to collapse
dmantilal said:
It did not work because you did not follow the directions.
Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "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.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.
Give us more info so we can help (assuming you fid it right initially).
P.S. - 6.0 is M(arshmallow), not L(ollipop).
Click to expand...
Click to collapse
i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED
THANKS!
so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?
nextelbuddy said:
i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED
THANKS!
so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?
Click to expand...
Click to collapse
Side-loading the OTA then following that with a FED flash seems much safer.
Loading an OTA directly would over-write the boot.img with a ForceEncrypt boot.img, logically Forcing Encryption (derp) at boot.
I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?
jamespat93 said:
I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?
Click to expand...
Click to collapse
You can if you want But if you want to unencrypt your phone, backup your ROM, copy sd content to your computer, wipe everything! in recovery (twrp) including Format Data, Factory reset, internal storage etc. Connect your phone while in recovery to your computer (you'll see 25.98GB instead of 23.03GB), copy sd content back to your phone, restore your rom backup and you'll be fine.
I can't get it work on Nexus 6 and chroma rom r26.
My steps: wipe everything, push folder (rom,patcher and gapps), flash chroma, flash gapps, flash patcher, wipe everything but system
after boot in setting/security it is again encrypted. what I am doing wrong?
Preliminary operations/infos
First of all: what's Treble?
Find it out here.
How do I obtain my bootloader unlock code?
GO HERE, FAST!
Huawei officially ceased the unlocking service.
How do I get Treble on my device?
At the moment of this write down, EMUI it's still in private BETA.
The only chance to obtain it it's to follow this guide CAREFULLY.
What if I want to revert to EMUI 8/5?
Follow the steps described in the guide to get treble on your device using EMUI 8 files if you want to revert to EMUI 8, or EMUI 5 if you wish to revert to it.
The road it's long...
So, you're sitting there, not understanding why there are so much ROMs in this section and why you shouldn't use the ones appearing in Treble-Enabled Device Development since you worked so hard to get Treble on it.
Let's try to answer a universal question.
What's the difference from the "standard" GSIs and the ROMs in this section?
Well, the ROMs here were made keeping an eye on the "optimization per-platform" concept, basically tracking down some proprietary stuff inheriting them under /system .
**WHAT FOLLOWS ARE PERSONAL OPINIONS**
I honestly think, that we should cut off this approach.
Inheriting stuff under /system has no more sense.
Am I saying that what I did till now had no sense?
Yes.
The whole Treble concept relies on moving away from system, any vendor related stuff.
So why in the hell should we inherit proprietary stuff in our system partition again?
When we have other ways to don't mess with it?
The only stuff that still "deserves" to have something to do with /system it's the Huawei Camera.
Everything else, belongs to /vendor.
Furthermore, our goal, as developers and users, should be to track down specific-platform bugs and report them.
Co-operation is the sake of open-source and the key to success in a wonderful GSI experience for everyone.
Is my device ready to use a "standard" GSI?
Pretty much.
Huawei doesn't ship any overlay under /vendor in our PRA, because it's inherited in EMUI under /system.
But, you can follow this guide, to include the needed overlay to be fully GSI-ready.
Also, you need this thread too to fix offline charging on your Huawei device.
Known Bugs on GSI and "specific-GSI"
NFC has been an annoying issue all along the development process on some Huawei devices.
But this flashable zip, seems to solve the issue on our PRA.
Indeed it needs more testing.
Available tools/software for your PRA
ADB and Fastboot
TWRP
MindTheGapps
Huawei Camera Magisk
OEMInfo (TWRP backup)
HuRU
Stock Ramdisk (ramdisk partition)
Stock Recovery (recovery_ramdisk partition)
Specific-GSI available
Lineage OS https://forum.xda-developers.com/p8...t/rom-lineage-os-huawei-p8-lite-2017-t3787193
CrDroidhttps://forum.xda-developers.com/p8.../rom-crdroid-4-2-huawei-p8-lite-2017-t3785615
AospExtendedhttps://forum.xda-developers.com/p8.../rom-aospextended-5-4-huawei-p8-lite-t3778938
AOSPhttps://forum.xda-developers.com/p8...ent/rom-aosp-r23-huawei-p8-lite-2017-t3779115
Resurrection Remix 6https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-rros-pra-t3774444
SlimRom 8
AICP
Specific GSIs are now discontinued.
Go to the Treble Enabled Development sub to get some ROMs to flash!
NOTE:
This ROMs will be discontinued in a couple of weeks, since the installation of the overlay (previously highlighted in the paragraph "Is my device ready to use a "standard" GSI?") will give access to a full fledged GSI experience without the need of specific GSIs.
Custom kernels
Labyrinth
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
If this isn't clear enough, please, check this contribution.
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
From 16.6 version, Magisk it's fully working.
Please, refer to this thread for a correct installation.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
adb logcat > file.txt
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or
adb logcat > file.txt
send file.txt to the developer
Hey you!
If you're reading this message I want you to help this community.
Share your thoughts about this posts or post your un-answered questions below.
The more we share, the best experience we'll get.
Also, please respect my work.
If you do integrate some of this infos in your thread/website or whatever, add me in the credits.
Furthermore, feel free to join us at @GSI_HI6250 on Telegram, we're funny people, I swear.
Is this non-clear somehow?
Or you just need help?
Fill the help form below.
Device Variant:
Device Firmware:
Is your device rebranded?:
How frequently this issue happens?
Is this happening now?
Describe the issue:
Describe steps to reproduce the issue:
Attach logcats/full bugreports as described on the paragraph "How to report bugs"
Or simply join the telegram group.
Peace.
Dil3mm4 said:
Kaioken reserved
Click to expand...
Click to collapse
Super Saiyan reserved
Lol
Dil3mm4 said:
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or
adb logcat > file.txt
send file.txt to the developer
Click to expand...
Click to collapse
THAT WORKED. FINALLY 8.1 WITH BOOTLEGGERS GSI, 128GB micro SDXC as INTERNAL. I AM HAPPY
for beginners:
boot after working rom in twrp
go in advanced
go to file manager
go to /vendor/etc/
open file "fstab.hi6250" (after copying with and having a recovery of it, open with notepad++ or something else)
there should be a line with: "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
erase the part: ",fileencryption=aes-256-xts:aes-256-cts"
save
erase the original fstab.hi6250 file in vendor/etc
and put the new fstab.hi6250 file in
reboot in bootloader
flash stockrecovery.img
reboot recovery
factory reset in stock recovery
reboot
DONE.
now you can see the SD card as internal and use for apps.
Need your help
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them
Mister746 said:
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them
Click to expand...
Click to collapse
Updated last post, please submit the infos needed via that form.
Thanks.
Hi, i am experiencing a weird bug on every GSI, specifically, snapchat video recording is fine and smooth, but after tapping on the "send" button it says "failed to add" and doesnt even give a chance to resend the same snap. It happens on all treble roms i've teted so far (i tested every specific GSI for PRA, and some openkirin and otger ones). @dill3m4 do you have any idea how to fix it? I hope there is a way to do a flashable zip or something like the NFC fix. Once i get back home (2-3 days) i will post some logs, in the meantime, can someone please confirm if the issue persists, and gather logs? ?
can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/
jedtan025 said:
can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/
Click to expand...
Click to collapse
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?
neondragon1909 said:
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?
Click to expand...
Click to collapse
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file
jedtan025 said:
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file
Click to expand...
Click to collapse
I couldn't find the file using TWRP either. Had to use root explorer to find and edit the file. As for hurupdater, I'm not sure if it's the same for your region, but for pra-la1 there were 3 files.
And as for the the 2 files, I successfully flashed using the updater with only the update.zip so try updating anyway. If that doesn't work, use the eRecovery
Update:
Added Magisk news;
Added stock PRA ramdisk
UPDATE:
Added Offline Charging Fix in post #2
Added references to Treble Enabled device development;
New Huawei Magisk Camera;
Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.
cyprian99 said:
Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.
Click to expand...
Click to collapse
Obtain what?
Treble roms?
Yay! Emui 8.0 has arrived on my c432 pra-lx1 (b360) . Everything is perfect.
The guide to get treble is unclear, how can the very first step be to download update.zip? I did and now i have a trojan, thanks a lot
How to unlock bootloader? Now the Huawei site is unavailable
Wysłane z mojego PRA-LX1 przy użyciu Tapatalka
Is there any benefit to doing so? You're nuking your security and that's basically it.
Am I missing something?
HeliX99 said:
Is there any benefit to doing so? You're nuking your security and that's basically it.
Am I missing something?
Click to expand...
Click to collapse
At least one point is that custom recoveries cant decrypt /data on Android 12 based ROMs. So it is just necessary.
kosmatyj said:
At least one point is that custom recoveries cant decrypt /data on Android 12 based ROMs. So it is just necessary.
Click to expand...
Click to collapse
I've read in an Arrow OS flashing guide a step that says "[OPTIONAL] Download the latest version of Encryption Disabler". The "optional" part confuses me, can you flash a rom *without* disabling encryption or does it say "optional" because you could use a different tool for the job?
HeliX99 said:
I've read in an Arrow OS flashing guide a step that says "[OPTIONAL] Download the latest version of Encryption Disabler". The "optional" part confuses me, can you flash a rom *without* disabling encryption or does it say "optional" because you could use a different tool for the job?
Click to expand...
Click to collapse
"Optional" - means that you can use this ROM without encryption disabler as usual if you dont planning to do anything in recovery (rooting, backup, restore, etc.). If you are just a normal user with no extra requirements - forget about it. Just flash the ROM and enjoy.
A very useful optional way to see internal contents using twrp based recovery when your using android 12 rom which in current has not custom recovery working in android 12 encryption yet
Where can I read more about encription in android in general and changes in 12?
yasen6275 said:
Where can I read more about encription in android in general and changes in 12?
Click to expand...
Click to collapse
Android 12 | Android Developers
Android 12 now available. Try it today!
developer.android.com
The benefit of disabling encryption is, avoiding the need for formatting data every single time you install a new rom. Imo it's a life saver for anyone who has a lot of data stored on their internal storage.
AmmarHaseeb said:
The benefit of disabling encryption is, avoiding the need for formatting data every single time you install a new rom. Imo it's a life saver for anyone who has a lot of data stored on their internal storage.
Click to expand...
Click to collapse
Do you need to format the data for a "dirty" flash, ie upgrading your existing rom to a new update?
HeliX99 said:
Do you need to format the data for a "dirty" flash, ie upgrading your existing rom to a new update?
Click to expand...
Click to collapse
No you don't need to format data unless it is explicitly stated by the developer/maintainer.
Edit: To dirty flash, you can just use adb sideload (if you're using aosp based recoveries like Pixel Experience Recovery or ArrowOS recovery, or use and External Micro SD Card, or USB OTG (if you're using TWRP or OrangeFox)/
JSGuangco said:
No you don't need to format data unless it is explicitly stated by the developer/maintainer.
Edit: To dirty flash, you can just use adb sideload (if you're using aosp based recoveries like Pixel Experience Recovery or ArrowOS recovery, or use and External Micro SD Card, or USB OTG (if you're using TWRP or OrangeFox)/
Click to expand...
Click to collapse
Thanks for the info