Related
Hi, I want to crypt my internal OnePlus X memory but I have some questions...
How it will affect the modding?
Will be TWRP able to flash mount partitions etc (using my decription key)? I've read that it supports Qualcomm encryption but nothung more...
Steccas said:
Hi, I want to crypt my internal OnePlus X memory but I have some questions...
How it will affect the modding?
Will be TWRP able to flash mount partitions etc (using my decription key)? I've read that it supports Qualcomm encryption but nothung more...
Click to expand...
Click to collapse
don't try it ..
i made some horrible experiences when i tried to decrypt my device again, my onyx got stuck in a bootloop when i tried to format my data via twrp (data corrupt).
the only possibility i had was flashing a /data partition image via fastboot which was generated during a source built android version
I dunno if this error is still present, but i can't recommend it because of personal experience
EDIT: Well thats not the answer to your question. So yes it works (TWRP and Encryption) but with already mentioned exception
Hope it helped ..
I want my ROM to receive OTA-updates, so instead of downloading and flashing a new version manually, users would get it updated for them automatically. All source codes are available for my device (Wileyfox Storm (kipper)), so building a custom kernel, recovery, TWRP, OS itself is trivial - generally you command brunch and everything just works™.
So I wonder - how do I enable OTA-updates for a ROM, while still keeping an option for users to use TWRP recovery? (yes, I got a place to host files & I generally understand how OTA works). I know that official TWRP app can queue zip files for installation in recovery mode, which is almost the same functionality I need for my OTA updates. Generally I'm looking for a way to make TWRP run a script located in /cache/recovery/command right after boot without offering any kind of user interaction. Can it be done with a TWRP, built from official sources or do I need to patch something to support that behavior?
So the question is how do I create OTA-updates that are compatible with official TWRP or how do I create a custom TWRP, that supports OTA-updates (whichever suits more for my task)?
Look up OpenDelta, its exactly what you're asking for I believe.
^^^Link please. im also looking same
OFFICAL TWRP RELEASED, this thread is no longer active. 3-30-2018
https://twrp.me/motorola/motorolamotox4.html
---
UNOFFICIAL BUILDS -- USE AT YOUR OWN RISK AND KNOW HOW TO GET YOURSELF OUT OF TROUBLE IF IT ARISES. I ASSUME NO RESPONSIBILITY FOR YOUR BROKEN THINGS.
UPDATED 01-11-2018
There are now 7.1 based and 8.0 based builds. Obviously, be careful to select the proper download. While I don't think flashing/booting the wrong one would permanently brick the device, let's not find out
For now I will not be attempting to make data decryption work. It is REQUIRED that you unencrypt your device by formatting userdata, so back up your stuff first.
IMPORTANT NOTES: TWRP for OREO is a bit of a pain as it currently requires manually editing your fstab. I have tried to automate this process, but it breaks stuff. So just be aware before you begin that it is a rather time consuming process.
If you make any change to your boot partition after flashing SuperSU, you will need to reflash it or you will get a bootloop.
8.0 OREO TWRP INSTALLATION:
OREO SEEMS VERY FINICKY AND DOES NOT LIKE CHANGES TO ITS FILESYSTEM -- BE PREPARED TO REFLASH STOCK.
0. FLASH OREO FACTORY IMAGE (may work otherwise, but we should be starting from fresh stock here)
1. Download FASTBOOT BOOTABLE TWRP for 8.0/OREO below
2. Download SuperSU 2.82 SR5 below
3. Move SuperSU to external SD or USB OTG
4. From bootloader, fasboot BOOT TWRP
5. Flash SuperSU (note: do not format /data now... not necessary and will cause errors on boot)
6. Reboot system
7. With any root file editor/text editor (Amaze, Total Commander, etc) open /system/vendor/etc/fstab.qcom as a text file for editing.
8. At the end of the /data partition entry, delete "fileencryption=ice" and replace it with "encryptable=footer".
9. Save fstab.qcom (and make sure it is actually saved properly!)
10. Reboot to bootloader and fasboot BOOT TWRP
11. Go to Wipe, hit the FORMAT DATA button, and type "yes" to format /data. This will erase your data, obviously:silly:
12. Reboot system (should now be unencrypted, verify in Settings>Security or by booting TWRP and checking /data with File Manager.
If you later choose to flash TWRP (not the bootable we used here!), you may need to flash SuperSU again to avoid bootloops.
7.1.1 NOUGAT TWRP INSTALLATION:
1. Download current TWRP for 7.1.1 build below
2. Download SuperSU 2.85 SR5 (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
3. Move SuperSU to your external Micro SD card.
4. Fastboot flash the TWRP image.
5. Reboot to TWRP.
6. FORMAT data (not wipe...use the "FORMAT DATA" button and type "yes". OBVIOUSLY THIS WILL ERASE YOUR DATA)
7. Install SuperSU 2.85 SR5
8. Reboot to system (it WILL bootloop a couple times...don't panic!) and confirm that device is unencrypted by checking that SETTINGS>SECURITY>ENCRYPTION now prompts "encrypt" (don't do it).
DOWNLOADS:
TWRP FOR 7.1.1 (Nougat) DOWNLOAD: https://drive.google.com/open?id=1Et-AQgCNx7WDAwzihlI51euUa2ixKHEP
TWRP FOR 8.0 (Oreo) DOWNLOAD: https://drive.google.com/open?id=1WcVS_3rloF7jxPulj_jKxfsp3zy5pB5N
FASTBOOT BOOTABLE TWRP IMAGE (OREO BASED): https://drive.google.com/open?id=12ClviqtEjtflB63UQ1CZQNKEqkprBO0u **For temporary TWRP boot using "fastboot boot". Do not flash or you will be stuck in recovery!**
DEVICE TREE: https://github.com/mightysween/android_device_motorola_payton (NEEDS TO BE UPDATED WITH OREO BRANCH)
changelog:
BETA4
-reverted to 3.2.0 for current build (release candidate rebased to 3.2.1).
-fixed "format data" button
-finalized fstab for OTG/SD/INTERNAL mounting
-target is now UNENCRYPTED devices only (/data decrypt will not be fixed)
BETA3
-Rebased to TWRP 3.2.1
-USB OTG working
-all partitions mounting correctly
-considered working except for decrypt and MTP/ADB
BETA2
-fixed internal storage mount
BETA1
- updated source to TWRP 3.2.0
ALPHA3
- Fixed USB mounting (adb/mtp still nonfunctional) BROKEN IN BETA1
ALPHA2
- SD Card fixed
ALPHA1
- /system is now properly mounted.
- now plays nice with our working root method.
- ramdisk is patched to prevent first boot encryption once /data is decrypted (now requires flashable ZIP)
NOT WORKING:
adb/mtp/sideload
/data decryption (abandoned -- /data access requires unencryption)
CREDITS: @kraatus90 for kernel fix, @Chainfire for SuperSU, @jcadduono for no-verity-opt-encrypt scripts.
---
Thanks so much for all your work!
hi,
you said this is really unstable and could brick the device easily. however, you seem to be testing and experimenting with your device a lot, so i'd like to ask if you have any particual unbrick method that you use when something goes wrong.. like, a via fastboot flashable image or something simmilar...?
thanks for your work!
Thanks for you work. If you have any unbrick methods pls tell.appreciated your work ?
I am not going to provide step by step "unbrick" methods, because until the partitioning is properly set up, TWRP has potential access to things that can not be fixed.
Again, this is still highly experimental.
All that said, my entire process to protect any device remains the same: Have a backup for every partition you will be testing, make as few changes as possible at a time, test boot images before flashing (fastboot boot), and test restore methods frequently (flashing back to stock or backups), and don't do anything unless you are highly certain of the outcome.
By those standards, there is nothing to gain by installing TWRP right now, as its basic function (install/backup/restore) is not set up yet.
Found the BoardConfig flag to enable FBE (TW_INCLUDE_CRYPTO_FBE := true) but do not have the lib it is dependent on (libe4crypt) and I don't see it anywhere yet...
For reference (not sure this is most current, but it demonstrates the process)
https://github.com/nijel8/TWRP/commit/bd7492de28963b7e74e8e5d3f17ec9a5a287d9c3
I have confirmed that FBE support is present in the source, dependent on this missing module... so need to figure out where/how to enable it.
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Obvious workaround is to not be encrypted to begin with -- but that isn't a "solution".
mightysween said:
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Click to expand...
Click to collapse
This appears to be the case, unfortunately. Seems that the TWRP FBE support was built specifically for the Google implementation of FBE which was merged into kernel sources for Nexus and Pixel. Not even using the qseecomd I assumed it was... will remove on next build.
Info on FBE:
https://source.android.com/security/encryption/file-based
Will be testing options to disable forced encryption, and if necessary dm-verity...
Anyone who wants to dig through kernel for related flags and props, it would be greatly appreciated!
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Making good progress this morning.
Seem to have a build with properly decrypted /system, and working SD Card. I also have patched the boot.img to disable forced encryption on the first boot. But now, I can not find a safe way to fully format (not "wipe") the /data partition. As mentioned in the previous post, the "FORMAT DATA" button is missing. The fastboot command "fastboot format userdata" returns an error that it does not support RAW format.
Need to figure out why this is happening... and once I do, I believe I can reformat /data without encryption and then will have an almost fully working TWRP build. Obviously, the ideal solution would be to have TWRP work out of the gate with an encrypted /data, but until then this is going to be our best option.
Will post an updated test build in the OP soon.... needs further testing before I would recommend non-expert users to try it.
Getting very close now!
UPDATE: ADDED NEW BUILD TO OP
---
Also, just occurred to me that the ramdisk will need to be patched every time, so now that I have SD card support will be testing some of the existing flashable ZIPs out there that are designed specificially to prevent first-boot encryption and/or disable dm-verity.
---
mightysween said:
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Click to expand...
Click to collapse
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
mightysween said:
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
Click to expand...
Click to collapse
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
johnjingle said:
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
Click to expand...
Click to collapse
I have 3.1.1-0 (same version I am building here) on several other devices, and the button is there. It has to be triggered by something during compile, but I can't figure it out. Driving me nuts
Looking through TWRP source, and can find actions for every other button (wipe, backup, restore, install, etc) but not for format. Hmm.
I posted over on an old but semi-active TWRP flags thread, maybe someone will have some insight.
Wondering if I make a stock boot image without the encryption tag in fstab, and then wipe data and reboot... then flash my image. That may make it so the data partition is never encrypted in the first place and allow TWRP to work.
But that is an ugly, non-user friendly fix. Why can't we just format /data?
---
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
No crypto support was compiled into this build.
Click to expand...
Click to collapse
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
mightysween said:
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
Click to expand...
Click to collapse
Thanks for doing all of this! I wish I had the time and knowledge to help.
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
mightysween said:
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
Click to expand...
Click to collapse
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
vivek638 said:
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
Click to expand...
Click to collapse
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
mightysween said:
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
Click to expand...
Click to collapse
Keep searching. wish i could have helped but dont know anything about compiling n all..
I'm not much of a programmer, but I can look through the files. Is there anything in particular we're searching for?
OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Changelog:
- Initial Official build.
- Decrypts Android 11
Contents:
Overview
Why OrangeFox?
Features
Screenshots
Links
Installation procedure
OVERVIEW:
Probably the most beautiful recovery out there.
Synced with the latest Teamwin changes.
Designed with latest Material design 2 guidelines.
Included customization.
Inbuilt patches, like Magisk and password reset patch.
Password protection.
Fully open-source.
Frequently updated.
Why OrangeFox?
OrangeFox has been operating for over two years. In that time OrangeFox have improved the quality, stability, and device support of the recovery. Today OrangeFox is the leader in stability, UI design, and UX. Installing OrangeFox means being with the latest code and fastest fixes.
Treble & Non-Treble Support
No compatibility.zip error while flashing OxygenOS
A lot of customisations
Extremely beautiful UI ready to please your eyes.
Dev team is always ready to fix your problems
F2FS support
Screenshots
Screenshots at
https://imgur.com/a/Ai8KWX9
and on Sourceforge
Links:
Support group: https://t.me/orangefoxop5t
Download: https://orangefox.download/
Installation procedure:
There are two methods to install OrangeFox
A) Via a recovery (for those with TWRP installed):
1. To install an OrangeFox zip, flash it with OrangeFox (or any TWRP-compatible custom recovery) without any wipes.
2. Do the same thing if you want to upgrade OrangeFox
3. When you flash an OrangeFox zip, there is no need to flash any DFE or any other such thing
4.To install an OrangeFox img file, boot into fastboot mode, and run the command: fastboot flash recovery OrangeFox-xyz.img
B) Via Fastboot (For those without a recovery):
You need a PC for this. If you do not have a PC, or access to a PC, then you are stuck!
1. Unlock your bootloader (if not already unlocked)
2. Install adb, fastboot and the relevant USB drivers onto your PCs)
3. Download the correct OrangeFox zip file to your phone, and to your PC
4. Extract recovery.img from the OrangeFox zip file, and copy recovery.img to your PC’s adb directory
5. Reboot your phone into fastboot/bootloader mode
6. Open up a command line window / terminal emulator on your PC
7. Change to the adb directory on your PC
8. Flash OrangeFox Recovery by using the fastboot flash recovery recovery.img command
9. Reboot into OrangeFox by pressing the power + volume down keys, until you see the OrangeFox splash screen
11. After OrangeFox has booted up, check that everything is working – eg, that it has mounted the data partition successfully, and that the touchscreen works.
12. Find and select the OrangeFox zip on your phone, tap on it, and swipe to install it (because OrangeFox Recovery needs some files from the zip)
After installation, the phone will automatically reboot into OrangeFox
Enjoy!
Congratulations
Now official.
Long live the Fox
Device: Oneplus 5T
8GB 128GB.
UI 10/10
Installation 10/10.
Keep it up
Nice to see this recovery for oneplus
Maitreya29 post: 84100659 said:
OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Changelog:
- Initial Official build.
...
Click to expand...
Click to collapse
Hi Maitreya29, and users,
Thank you for this! Will be trying this out soon...
I'm currently on the unofficial build from here:
[UNOFFICIAL] [RECOVERY] [OnePlus 5T] OrangeFox Recovery Project [R10.1]
OrangeFox Recovery /* * Your warranty is now void. * * We're 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...
forum.xda-developers.com
Does this official build have any major changes or other functionality?
Has anyone tested a full backup and restore? Encryption? Custom ROM flash on A11?
Cheers
thkgop001 said:
Hi Maitreya29, and users,
Thank you for this! Will be trying this out soon...
I'm currently on the unofficial build from here:
[UNOFFICIAL] [RECOVERY] [OnePlus 5T] OrangeFox Recovery Project [R10.1]
OrangeFox Recovery /* * Your warranty is now void. * * We're 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...
forum.xda-developers.com
Does this official build have any major changes or other functionality?
Has anyone tested a full backup and restore? Encryption? Custom ROM flash on A11?
Cheers
Click to expand...
Click to collapse
I would recommend switching for stability purposes only. This recovery is beautiful to say the least and everything as far as I can tell works completely well. I am on crDroid Android 11 flashed with this recovery.
Maitreya29 said:
OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Changelog:
- Initial Official build.
...
Enjoy!
Click to expand...
Click to collapse
Hey OP, users,
I noticed something weird and I don't know if it's related to this build or just something wrong on my end (of course, running on a dumpling).
When I make a backup, the Fox directory (inside my storage root) looks empty inside Solid Explorer (and a couple of other file managers) inside A11. As if the directory is completely empty... No theme folder, no backup folder, like totally nothing. This is of course, with the option chosen of Solid Explorer showing all files, including hidden files.
But Fox's own file manager (and AromaFM) shows me my backups, and other files inside the Fox directory. The backups look like they are the right size too.
Something wrong with my set up? How come Fox's files are invisible to other file explorers?
Also, may I make a small cosmetic request for OP?
Please could you include the customisation option to hide the Fox logo on the splash screen? That way it wouldn't overlay on a user chosen splash wallpaper.
Thanks
thkgop001 said:
Hey OP, users,
I noticed something weird and I don't know if it's related to this build or just something wrong on my end (of course, running on a dumpling).
When I make a backup, the Fox directory (inside my storage root) looks empty inside Solid Explorer (and a couple of other file managers) inside A11. As if the directory is completely empty... No theme folder, no backup folder, like totally nothing. This is of course, with the option chosen of Solid Explorer showing all files, including hidden files.
But Fox's own file manager (and AromaFM) shows me my backups, and other files inside the Fox directory. The backups look like they are the right size too.
Something wrong with my set up? How come Fox's files are invisible to other file explorers?
Also, may I make a small cosmetic request for OP?
Please could you include the customisation option to hide the Fox logo on the splash screen? That way it wouldn't overlay on a user chosen splash wallpaper.
Thanks
Click to expand...
Click to collapse
Personally I use MiXplorer Silver, and I can see all of the Fox recovery files within the storage root. You may want to have a look at storage permissions from the file explorer you're using. If your willing to try another explorer I'd recommend MiX but I'm not entirely sure it'd solve your issue. Can you see anything with your default explorer, the one that came with your rom? Most if not all custom roms have a default. While bare bones it can at least give you an idea on if its your fault or the systems..
Mr.Conkel said:
Personally I use MiXplorer Silver, and I can see all of the Fox recovery files within the storage root. You may want to have a look at storage permissions from the file explorer you're using. If your willing to try another explorer I'd recommend MiX but I'm not entirely sure it'd solve your issue. Can you see anything with your default explorer, the one that came with your rom? Most if not all custom roms have a default. While bare bones it can at least give you an idea on if its your fault or the systems..
Click to expand...
Click to collapse
Hey Conkel
Thanks for the tips.
My default explorer (Files on MSM-Xtended 2.0) also shows that folder as blank - screenshot attached
Solid Explorer shows empty, but the correct modified date and time - screenshot attached
I installed MiXplorer 6.9.3 and gave it file system permissions as well as root permissions.
Fox folder Still empty - screenshot attached.
I'm stumped!
No big deal though, I can always use the Fox File Manager, but it's just so weird!
I'm going to delete the whole Fox folder later on tonight and start afresh. Maybe that might just work...
thkgop001 said:
Hey Conkel
Thanks for the tips.
My default explorer (Files on MSM-Xtended 2.0) also shows that folder as blank - screenshot attached
Solid Explorer shows empty, but the correct modified date and time - screenshot attached
I installed MiXplorer 6.9.3 and gave it file system permissions as well as root permissions.
Fox folder Still empty - screenshot attached.
I'm stumped!
No big deal though, I can always use the Fox File Manager, but it's just so weird!
I'm going to delete the whole Fox folder later on tonight and start afresh. Maybe that might just work...
Click to expand...
Click to collapse
I don't currently have any backups myself but as you can see here the fox folder + files are indeed visible. Keep in mind we're not on the same Android version or rom I'm on Android 10 CrDroid v6.13 I'm not sure why MsmExtended would be doing this but personally I've never used it.
Mr.Conkel said:
I don't currently have any backups myself but as you can see here the fox folder + files are indeed visible. Keep in mind we're not on the same Android version or rom I'm on Android 10 CrDroid v6.13 I'm not sure why MsmExtended would be doing this but personally I've never used it.
Click to expand...
Click to collapse
OK, so deleting the Fox folder seems to have fixed it... I can see the Fox files now.
Weird - probably a file system issue (not?) related to the ROM.
Or maybe because I was running the unofficial Fox and then flashed this official build on top.
Anyways, thanks for your help!
thkgop001 said:
OK, so deleting the Fox folder seems to have fixed it... I can see the Fox files now.
Weird - probably a file system issue (not?) related to the ROM.
Or maybe because I was running the unofficial Fox and then flashed this official build on top.
Anyways, thanks for your help!
Click to expand...
Click to collapse
Well incase it was for further reference I would recommend using fastboot to flash Orange Fox with the recovery.img it flashes right over top of the current recovery so nothing can go wrong like that. Anytime no problem.
Is there any ETA on the possibility of decrypting systems where a password is used (instead of pattern)?
Or is it something that will never be implemented for Android 11?
riki66 said:
Is there any ETA on the possibility of decrypting systems where a password is used (instead of pattern)?
Or is it something that will never be implemented for Android 11?
Click to expand...
Click to collapse
Much needed, now that we have twrp supporting android 11 pin/password decryption. @Maitreya29
Hello!
Received an Oneplus 5T from China a few days ago, (still) running OxygenOS 9.0.9 A5010_43_191008. Gonna install some custom ROM as usual, so just unlocked its bootloader.
Saw this these posts about OrangeFox recovery, and considering what I've been reading in the [OFFICIAL][RECOVERY] [TWRP] TWRP for OnePlus 5T thread I feel like I'm going to put my faith in this recovery.
I have a question, though. According to what I read in the TWRP thread, the custom recovery gets killed by the stock ROMs. Is this serious?
Just
curiosity. I guess that means I should straight install my custom ROM of choice just after the recovery, period.
What is the difference between cheeseburger and dumpling builds?
Self-answering myself: cheeseburger is for OnePlus 5, dumpling is for 5T.
Merry Christmas and Happy New Year, by the way.
Barkuti said:
Hello!
Received an Oneplus 5T from China a few days ago, (still) running OxygenOS 9.0.9 A5010_43_191008. Gonna install some custom ROM as usual, so just unlocked its bootloader.
Saw this these posts about OrangeFox recovery, and considering what I've been reading in the [OFFICIAL][RECOVERY] [TWRP] TWRP for OnePlus 5T thread I feel like I'm going to put my faith in this recovery.
I have a question, though. According to what I read in the TWRP thread, the custom recovery gets killed by the stock ROMs. Is this serious?
Just
curiosity. I guess that means I should straight install my custom ROM of choice just after the recovery, period.
What is the difference between cheeseburger and dumpling builds?
Self-answering myself: cheeseburger is for OnePlus 5, dumpling is for 5T.
Merry Christmas and Happy New Year, by the way.
Click to expand...
Click to collapse
Welcome to the family!! Also yes stock roms kill any custom recovery only way to avoid this is with a custom rom of your choosing, the recovery is replaced upon booting into system, if you need to reboot into recovery or bootloader for any reason it should work just fine. This is a beautiful recovery I highly recommend! As far as roms there are plenty to choose from. Good luck, have fun and most importantly enjoy your new device!
Thanks for the nearly instant reply Mr.Conkel.
Of course I am into custom ROMs, needless to say. I like stable, featured and powerful software (software as God commands I like to say). Right now I am still running AospExtended 5.7 on a Z2 Pro, you can guess I don't like to unnecessarily mess with my software when it works.
I am wondering what to choose for the 5T (which is not for me but it has to be like if it were), my intuition is leaning me for a crDroid build. Suggestions are welcome.
I also see people speaking about the “encrypted vs unencrypted” storage thing (I have never encrypted my storage), and the need to flash a no-verity-opt-encrypt zip (?) patch. Suffice to say I am green in this respect, just read Download no-verity-opt-encrypt All Versions @ Android Infotech, which still does not make much sense to me regarding the encrypted vs unencrypted thing. However, since I am rooting it smells like flashing no-verity-opt-encrypt is mandatory for me.
LoL sorry for the long off-topic.
Barkuti said:
Thanks for the nearly instant reply Mr.Conkel.
Of course I am into custom ROMs, needless to say. I like stable, featured and powerful software (software as God commands I like to say). Right now I am still running AospExtended 5.7 on a Z2 Pro, you can guess I don't like to unnecessarily mess with my software when it works.
I am wondering what to choose for the 5T (which is not for me but it has to be like if it were), my intuition is leaning me for a crDroid build. Suggestions are welcome.
I also see people speaking about the “encrypted vs unencrypted” storage thing (I have never encrypted my storage), and the need to flash a no-verity-opt-encrypt zip (?) patch. Suffice to say I am green in this respect, just read Download no-verity-opt-encrypt All Versions @ Android Infotech, which still does not make much sense to me regarding the encrypted vs unencrypted thing. However, since I am rooting it smells like flashing no-verity-opt-encrypt is mandatory for me.
LoL sorry for the long off-topic.
Click to expand...
Click to collapse
If your looking from a daily perspective I highly recommend running Android 10 as A11 is still pretty rough around the edges and isn't as feature heavy yet. Although that will come in time. For now I would recommend crDroid A10 or Resurrection Remix A10 (A11 isn't out yet). I use Rr as a daily with MadKernel it works great. All these threads are relatively easy to find. But for stability over features always go with LineageOS. Cr and Rr hardly have any bugs but they do exist and you can run into a few issues. Just let me know if you need more information.
Cheers!!
Thanks for the advice concerning A10 vs A11 Mr.Conkel.
One of the things I love from AEX is
a proper task switcher. Guess I got traumatized back in the day with the LAME Lollipop card task switcher which I swear to have seen on much more modern OSes. It also is super stable, the only noticeable issue I have found in it is the settings app crashing when I hit “root management” in the settings menu (an irrelevant hiccup).
Thanks for the tips in any case.
Barkuti said:
Thanks for the advice concerning A10 vs A11 Mr.Conkel.
One of the things I love from AEX is
a proper task switcher. Guess I got traumatized back in the day with the LAME Lollipop card task switcher which I swear to have seen on much more modern OSes. It also is super stable, the only noticeable issue I have found in it is the settings app crashing when I hit “root management” in the settings menu (an irrelevant hiccup).
Thanks for the tips in any case.
Click to expand...
Click to collapse
If task switching is what your looking for then I highly recommend Resurrection Remix OS I use slim recents and its wonderful. Here's a screenshot for perspective. Mad Kernel is what I use it with but that isn't mandatory.
Mmm, but Slim Recents can be installed onto whatever ROM, doesn't it?
We'll see, we'll see.
Important information:
This thread is for LineageOS 19.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi. The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Magisk
What's not working:
SELinux Permissive
Encryption
Connecting to some Bluetooth Classic devices
Installation:
If you are on the stock OS, you will first need a custom recovery. You can get the recommended Lineage recovery here.
If you are coming from stock or other ROMs, you need to do a factory reset, and resize your partitions with this tool. It is highly recommended to flash it using ADB sideload.
As always, make sure to backup before installing this ROM.
For more detailed instructions, please visit:
Install LineageOS on wt88047
Download link:
SourceForge
Recommended Google Apps package:
MindTheGapps
Recommended Firmware:
Google Drive
Bug reports:
How to submit a bug report
Gitlab Issues
Donate to support development:
Donate via PayPal to tipzrickycheung
Donate via PayPal to nicknitewolf
Donate via PayPal to LineageOS
Source Code:
Device tree
Kernel
LineageOS Github
Contributors
@tipzrickycheung, @althafvly, @nicknitewolf, Lineage Team
ROM OS Version: 12.x S
ROM Kernel: Linux 3.10.x
ROM Firmware Required: M8936FAAAANUZM-1.33887.1.41528.1
Based On: LineageOS
Reserved
New update!
20220218
- Fixed Bluetooth
- Baseband and IMEI now detected
Download
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
Yup, I am on Coolapk
pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
About the expansion zip, you need to have the stock partition layouts to start with.
New update!
20220219
- Fixed LiveDisplay
- Added SEPolicy Changes
- Added Binder and lmk kernel backports
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
I'm just popping in to say this looks very promising! Thanks for caring about this device. Please don't give up with this build
New update!
20220227
- Fixed Hotspot (Can be fixed for 18.1 too)
- Software navkeys now works properly
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
hi developer wt88047 @tipzrickycheung how fixed for twrp error E2001 : Failed to update vendor image? for flashing build lineageos unofficial 19
now iam dowgrade lineage os unofficiall 18.0 build from @nicknitewolf its work
BangJhon.id said:
hi developer wt88047 @tipzrickycheung how fixed for twrp error E2001 : Failed to update vendor image? for flashing build lineageos unofficial 19
now iam dowgrade lineage os unofficiall 18.0 build from @nicknitewolf its work
Click to expand...
Click to collapse
Use the partition expand package first
pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
I think I might have fixed bug 3, will push an update when appropriate.
one by one step i try, no fixed this message, from recovery all path, partisi, i not working instal lineage os based 19.0
New update!
20220228
- Fixed TimeKeep (?)
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
Thanks for the release! Today I tried to install this, but I got error 1 in TWRP saying "failed to update vendor image". Is it required to add a dedicated treble vendor partition with this tool? Just asking because this may have to do with the system partitioning otherwise.
RandomNewbie said:
Thanks for the release! Today I tried to install this, but I got error 1 in TWRP saying "failed to update vendor image". Is it required to add a dedicated treble vendor partition with this tool? Just asking because this may have to do with the system partitioning otherwise.
Click to expand...
Click to collapse
No, and we don't support using that tool.
tipzrickycheung said:
Use the partition expand package first
Click to expand...
Click to collapse
I am unable to install the partition expand package that you have provided (resize_wt88047x_v6.zip) on my device. TWRP gives me this error - "Can not extract update-script. Do you have it in package?". I have the 8gb variant. Any help is appreciated!
SaneComputing said:
I am unable to install the partition expand package that you have provided (resize_wt88047x_v6.zip) on my device. TWRP gives me this error - "Can not extract update-script. Do you have it in package?". I have the 8gb variant. Any help is appreciated!
Click to expand...
Click to collapse
Update your TWRP.
New update!
20220323
Android 12L!
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
Still using latest twrp but error show up everytime