Author Topic: Unofficial TWRP build  (Read 2448 times)

spa

  • Newbie
  • *
  • Posts: 10
    • View Profile
Unofficial TWRP build
« Reply #15 on: June 22, 2020, 10:09:40 pm »
Quote from: AP756
Quote from: spa
TWRP is no longer available on V22. It asks for a password. Will I be able to use it as before?

TWRP still works. It asks for a password to decrypt data (AFAIK is only possible using ADB). Just use <back> and you'll see TWRP - no data partition of course

I want to back up and restore the data partition. The current state is lacking in features.

ehem

  • Newbie
  • *
  • Posts: 30
    • View Profile
Unofficial TWRP build
« Reply #16 on: June 27, 2020, 01:44:57 am »
Quote from: Ninji
Source code on GitHub: https://github.com/Treeki/unofficial-twrp-cosmo
They released a built blob which appears to be a build of TWRP, but didn't work for me.  Since I desire to do my own builds of TWRP, I'm trying to get this to build.  TWRP used to depend on the source trees of OmniROM, but apparently they're now supposed to work if used to replace LineageOS's recovery.  There are also minimized versions of OmniROM and LineageOS codebases which are supposed to work for builds.

Which repositories/branch did you use?

Minimal repo repositories are:
https://github.com/minimal-manifest-twrp/pl...ifest_twrp_omni
https://github.com/minimal-manifest-twrp/pl..._twrp_lineageos
(which and which branch?)


Personally I tend to include `fdisk` and `sfdisk` in builds.  `sgdisk` works okay for scripting, but `sfdisk` is much more powerful in a scripting environment.  Whereas `fdisk` is far more usable in interactive use.

ehem

  • Newbie
  • *
  • Posts: 30
    • View Profile
Re: Unofficial TWRP build
« Reply #17 on: July 31, 2020, 09:59:19 pm »
Thank you so much! Yeah, I've tried the lk as well. All img files from he OTA zip, actually. It certainly seems that /data is being decrypted successfully. I haven't tried pulling any of the files with ADB, but I would think if file and folder names are looking right, that the decryption is working.
As near as I can tell, it appears this would require the use of FDE (Full Device Encryption) and not FBE (File-Based Encryption).  Yet so far I've only managed to get FBE and not managed to cause it to do FDE.  One of the dialogs during setup almost sounds like choosing between FBE/FDE, but I chose the one I would expect to generate FDE yet still ended up with FBE.



Then after some persistence I think I've figured out the answer to my own question.  I suspect @Ninji's TWRP build was based on TWRP's minimal OmniROM manifest:
https://github.com/minimal-manifest-twrp/pl...ifest_twrp_omni
Branch twrp-9.0.  Took a bit of adjustment to get my first build operational, but I have a successful build.  Now dealing with the above issue and working on building the kernel from source.