Man, I'm talking about my pc... though I do have a gentoo chroot (chroot means basically a seperate install, but using same (running) kernel and network) on my phone too
[Recovery][Unofficial]TWRP 3.3.1-1 : 2019-10-25
- Thread starter Phoenix591
- Start date
Man, I'm talking about my pc... though I do have a gentoo chroot (chroot means basically a seperate install, but using same (running) kernel and network) on my phone too
You had me super excited for a bit there... Imagine v20 with full blown native Linux kernel... I could use it to modify my phones then. Ultra Portable phone modification! My 2006 MacBook is getting a little old. For Linux on your phone are you using userland?
Not sure what you mean by userland in this context.. android kernels are linux kernels with added drivers, and yes the chroot is a "regular" gnu userland (a full arm64 gentoo install), but compiling from an android source checkout (which twrp requires), takes up loads of diskspace (8.1 G of sources, producing another 8.3 G of output, though for a single device it would be just 1.1G of output) and uses prebuilt compilers and other tools that are only provided for x86.
Could build the kernel, though it'd take longer than my desktop.
Last edited:
It always takes excessive amounts of space to build for Android doesn't it? Like 100s of GBs right? Though yes I thought it would be quite a process. There has only been a few Linux alternative to Android over the years for a reason. Only one I know of that didn't come with specific phones built for it. Halium and it's a ubuntu touch. As for userland take a look at this from Google play, it's neat but didn't quite work the way I wanted it to.
https://play.google.com/store/apps/details?id=tech.ula
Hundreds? More like 20-30ishfor a full rom depending on how many devices, building TWRP is literally building part of a rom.
Chrooting, is the same general thing as that app, but I do it with a root method (I made an image, basically a partition within a partition by using dd to write to a file, then making a filesystem on that file, then mounting it (making it available to write inside), and extracting a gentoo stage 3 (basically core system) inside) , and I've migrated from using a specific app to do it to just using a terminal emulator and setting it up myself.
Just thought I'd ask. What "base" (sorry if that's not the correct term) are you using to build your H990 TWRP images? I'm using lineageos-15.1.
Just making sure I'm doing everything as similar as possible while I work on my own build to fix the decryption issue I mentioned.
EDIT: Think I see your usage of OmniRom in your device tree, this is making more sense now.
Just making sure I'm doing everything as similar as possible while I work on my own build to fix the decryption issue I mentioned.
EDIT: Think I see your usage of OmniRom in your device tree, this is making more sense now.
Last edited:
yeah, omnirom 7.0 but an oreo based kernel ( a very slightly tweaked version of mk2000 actually).
able? probably. Willing? no thanks, I really want to keep the differences from regular mk2000 as few as possible. I'm mostly doing those builds for myself and want to keep it easy to stay in sync.
Hey man, since I couldn't open my 3.2.3-1 TWRP, I wanted to update to this 3.3.0 version but since I couldn't get to the recovery i flashed through adb/fastboot. It went ok but when I try to access it, its just black screen. What should I do? How I can install TWRP without using it? BTW. Its H990DS version.
Hey @Phoenix591 @seaders seems to have solved the /data decryption problem for LG V30 on Oreo (8.1).
He/she even thanks you in the post.
Can this work for the V20? or is it a different vold implementation?
He/she even thanks you in the post.
Can this work for the V20? or is it a different vold implementation?
Last edited:
@Phoenix591
Recent LS997 builds fail to keep /system mounted for me, it gets unmounted after a few seconds after I mount it from Mount menu. /system gets mounted briefly, I can see it mounted in df output for a few seconds.
Error messages in the log:
I don't see anything else relevant (AFAIK) in recovery.log or dmesg output. /system partition is clean, ran e2fsck on it, no problems.
Don't see any processes locking the partition, running "lsof 2>&1 | grep sda18" lists nothing.
Builds exhibiting this problem:
2018-08-17 build of 3.2.3-0 works.
I have an LS997 running Nougat-based AlphaROM (stock-based, non-AOSP).
Recent LS997 builds fail to keep /system mounted for me, it gets unmounted after a few seconds after I mount it from Mount menu. /system gets mounted briefly, I can see it mounted in df output for a few seconds.
Error messages in the log:
Failed to unmount '/system' (Device or resource busy)
...
Failed to mount '/system' (Device or resource busy)
...
Failed to mount '/system' (Device or resource busy)
I don't see anything else relevant (AFAIK) in recovery.log or dmesg output. /system partition is clean, ran e2fsck on it, no problems.
Don't see any processes locking the partition, running "lsof 2>&1 | grep sda18" lists nothing.
Builds exhibiting this problem:
- recovery-twrp-ls997-2019-04-07.img
- recovery-twrp-ls997-2019-04-01.img
- recovery-twrp-ls997-2018-10-18.img
- recovery-twrp-ls997-2018-09-30.img
2018-08-17 build of 3.2.3-0 works.
I have an LS997 running Nougat-based AlphaROM (stock-based, non-AOSP).
Uploading some new builds that redo how encryption is handled (back to more like the much older builds), that may help.
Just for information and so others are able to find a reason via google:
I tried flashing the newest Alpha Omega 1.3.0 on my H918 with TWRP 3.3 and was unable to do so.
I got some decryption error on every start and that the data would be corrupted. Using 3.2.3.4 (2018-10-18) fixed this. Seems like other devices are affected too.
I tried flashing the newest Alpha Omega 1.3.0 on my H918 with TWRP 3.3 and was unable to do so.
I got some decryption error on every start and that the data would be corrupted. Using 3.2.3.4 (2018-10-18) fixed this. Seems like other devices are affected too.
That link doesn't work, the one on the first post does.
I tried the beta build, /system read only button can be depressed now (a problem I posted before here).
It still does not mount /data on stock Oreo, I do not have a password set, do I need to set one?
It also takes much longer to load, I am guessing trying to mount something.
Last edited:
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
91Inspired by Backcheck building for the VS995, I've decided to build the latest TWRP for the US996 and now most other V20 variants as well. I'm an amateur, but so far in my own use it seems to be working fine (flashes Open Gapps, Lineage, and Magisk fine, and tested a small backup and restore). That being said, use at your own risk. Any advice and contributions are welcome.
My device tree
Made possible by:
The TWRP team
Jcadduono for the kernel and initial device tree
@askermk2000 for continuing work on stock based kernels
@emdroidle for creating Kdzwriter: a useful tool for flashing all or part of a kdz (stock firmware file) without a pc.
Known Issues
- Occasionally the battery will incorrectly display 50% usually after rebooting from recovery into recovery
- Decryption doesn't work on stock based Oreo roms
Please post and let me know anything else!
Changelog
2019-10-25
Changed one last thing to try to fix stock Oreo decryption.
There were an upstream TWRP change that should fix the issue where formatting was still leaving /data encrypted as well (this was actually in the last build, but I didn't notice it then)
2019-05-17-NOT Beta
Made sure the decryption process is setup exactly like it used to be in the past so it should hopefully work if the BETA builds don't (do try the beta build first if you're using encryption, it would be so much easier going forward if the beta way of doing decryption would work), and fresh build for 3.3.1
2019-05-17-ENC Beta
Added a few other services to try to fix encryption again, if someone using encryption would give today's builds a try I'd appreciate it.
2019-04-22-ENC Beta
Redid how encryption is handled so its much more like the older builds.. still can't handle stock oreo encryption unfortunately, but should have less issues with /system mounting, and might work with something x86cpu is working on for lineage 16.
Basically if you're having issues with 3.3.0 try this one
2019-04-07
Not a whole lot, but TWRP officially decided to tag version 3.3.0 along with some small changes, such as being able to check zip integrity using .sha256 sum files in addition to .md5 and .md5sum files
2019-04-01
Updated kernel
Updated kdzwriter to latest version
2018-10-18
Fixed crash on startup (by updating the kernel again)
2018-10-16
Properly updated H990 build
Hopefully fixed F800 build
Minor kernel update for all variants
2018-10-06
Fixed crash/reboot on stock Oreo so that it doesn't take 10 tries to get in (by changing to an oreo kernel), /data decryption still broken.
2018-09-30
Enabled quota features in the kernel to fix stock based oreo
2018-08-17
/vendor partition support, x86cpu and I got it working and setup so that if a split vendor partition exists we'll be able to back it up or flash to it in TWRP, and of course keep /data decryption working. For those without a /vendor partition it will only show up on the twrp mount page.
Adjustments to the time so that it will be correct with Lineage 15.1
Adjustments to scripts to prevent things from getting confused and mounting and unmounting /system repeatedly as has been reported by some.
Provided nothing crazy happens with these builds, this will likely be the revision we go official with.
Older Changelogs
If the clock and/or date (check by going to advanced->terminal then typing date(enter)) is wrong, first try rebooting to normal Android for a while, then if its still wrong after rebooting into recovery let me know your model, and the time/date it claims to be and the correct time (or just the difference)
Download
TWRP-3.3.1-1: 2019-10-25
(Is linking just the folder alright for ya'll? If enough people say something I'll go back to direct links to each device, but copy and pasting individual links for each device gets to be kind of a drag)
Optional: DO NOT USE THIS OPTIONAL ENCRYPTING ZIP WITH LINEAGEOS
Since Magisk and supersu disable mandetory encryption by default unless installed with an already encrypted /data and stock and stock based roms have no ui option to encrypt, I've created a flashable zip encrypt-v2.zip (uses the anykernel template by osm0sis ) that makes encrypts /data without data loss. Requires a charged battery (if the power is cut during encryption you could lose all data!) and it checks if you're using one of my twrp builds since afaik none of the others work with encryption.
Stock users it will stay on the LG boot animation while encrypting! Do not even think about pulling the battery unless you didnt want your data anyway.
DO NOT USE THIS OPTIONAL ENCRYPTING ZIP WITH LINEAGEOS, it has it's own option to encryption in settings under security.
Old versions
14I'm still around, just released a minor update, just bringing up kdzwriter and the kernel to the newer versions.9
So what was wrong was that you wern't doing the ln -s part of the directions in the kdzwriter thread. so it couldnt find the linker (the second paragraph under unix-like describes exactly what happened) needed to run the program (it was looking in /system) It was working in the old twrp because it mounts /system by default and new versions don't.
Anyway today's build flat out includes kdzwriter and is ready to use.9
Maybe once I can get pie working I can revisit things again. Stuck in a couple places still. No nfc, fingerprint or Bluetooth yet.
---------- Post added at 03:05 AM ---------- Previous post was at 03:03 AM ----------
The vendor split it is not needed for pie to work. It only it's needed to run gsi images, which is a LineageOS vendor and gsi system. The LineageOS build had the vendor and system, so a split out is not required.9
Well someone needed to be taking care of TWRP, at the time I started only the vs995 had a 3.2.x build. Figured might as well be me since TWRP is simpler than a full ROM like LineageOS. (Re:the system is busy issue its a nonissue, just twrp trying to unmount it before I end one of the services necessary to decrypt. I unmount it immediately after)
