Unofficial TWRP and OrangeFox builds.
TWRP : https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/
OrangeFox - deprecated : https://sourceforge.net/projects/ep...overy/OrangeFox-Unofficial-sagit.img/download
This is TWRP-3.3.1 unofficially updated with lots of new improvements!
What's here but not in the official one?
Compiled with Pie blobs and in pie environment
Updated kernel, based on CAF's latest pie tag and compiled with latest Clang 9.0.3 by Google
Additional debug support - This TWRP won't overwrite /sys/fs/pstore
F2FS support
Cleaned unused HALs from manifests
System as Root variant available
How to install this TWRP?
Boot into fastboot mode by pressing volume down + power when the device is turned off
Connect your device to your computer
Download the TWRP build
Open a shell at the download folder
Rename the downloaded file to twrp.img
Type
Code:
fastboot flash recovery twrp.img
To leave the fastboot mode type
Code:
fastboot reboot
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers
Click to expand...
Click to collapse
- Wikipedia
How to use F2FS for /data and /cache?
Reboot into this TWRP
Select wipe > format data then type yes and reboot into recovery again
Then select wipe > advanced wipe select cache then select repair or change file system and select F2FS
Do the same step with Data
Install a supported ROM and GApps
Reboot into the ROM
Thank you for your great work . keep it up
Thanks,I'm following the topic
Sorry for my ignorance....but can somebody tell me the difference between these two?
Shiw Liang said:
Sorry for my ignorance....but can somebody tell me the difference between these two?
Click to expand...
Click to collapse
Between orange fox and twrp? Orange fox is a fork of twrp with some special features and a redesign.
Shiw Liang said:
Sorry for my ignorance....but can somebody tell me the difference between these two?
Click to expand...
Click to collapse
Have a look here - https://orangefox.tech/
DarthJabba9 said:
Have a look here - https://orangefox.tech/
Click to expand...
Click to collapse
happy to see you here, Will sagit devices have an official version? We are looking forward
fr0bs said:
happy to see you here, Will sagit devices have an official version? We are looking forward
Click to expand...
Click to collapse
In due course
New TWRP test build is available!
TWRP was updated to version 3.3.0 and is usable with f2fs.
Download : https://drive.google.com/file/d/1UwT5UBz_8PVugEhWLYlcwKM3VAi25jkI/view
This build is possible due to Ultraschorsch 's support by providing a Google Cloud trial ?
Good evening!
A new build of TWRP is published here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.0
Decryption problem
NeoArian said:
Good evening!
A new build of TWRP is published here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.0
Click to expand...
Click to collapse
I have tryed your latest update with AEX 6.5 and I can't decrypt data. What am I wrong?
perspicio said:
I have tryed your latest update with AEX 6.5 and I can't decrypt data. What am I wrong?
Click to expand...
Click to collapse
There is a problem with decrypting devices formatted with may ASB, I see about it. You could go f2fs or setup rom on April build and upgrade to new one for now.
Edit:// should be fixed here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.1
I am currently on LineageOS 15 (8.1), and using TWRP 3.2.3. Everything works OK.
But if I try to boot into latest 3.3.1 (both with SAR and without) it doesn't request pattern for decrypting data, and I can't figure out how to force it to.
Without decrypt it shows /sdcard and /data/data as garbage...
Hi @NeoArian, it seems that at least your latest TWRP-sar version has issues with mounting external usb storages: at least my sandisk 64GB key that I always used to save nandroids to is not detected, thus I have to rely on internal memory to save nandroids, fw, and user data.
Using TWRP version 3.2.3-sagit-shev.img I have no issues (but unfortunately no support for your lineageos unofficial builds if I'm not mistaken).
Am I doing something wrong? Do you have any suggestions?
Cavaler said:
I am currently on LineageOS 15 (8.1), and using TWRP 3.2.3. Everything works OK.
But if I try to boot into latest 3.3.1 (both with SAR and without) it doesn't request pattern for decrypting data, and I can't figure out how to force it to.
Without decrypt it shows /sdcard and /data/data as garbage...
Click to expand...
Click to collapse
I thought it was some codes in twrp that cause the problem.
If I use 3.3.1.0 everything works fine. but it won't decrypt my data even I had no pattern for lock screen with 3.3.1.2.
( all mentioned above are official builds )
This version TWRP have arch bug.
This version TWRP can not install the right latest OpenGapps. It will back error 64 and ask user install arm version gapps not the arm64 version.
The details can visit here https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070
Can you fix it in your version?
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444
New twrp update available: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.1-20191204
AmaoBilibili said:
This version TWRP can not install the right latest OpenGapps. It will back error 64 and ask user install arm version gapps not the arm64 version.
The details can visit here https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070
Can you fix it in your version?
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444
Click to expand...
Click to collapse
I assume that's a problem with OpenGapps installer.
Hi, I'm running twrp 3.3.1-20191204 with your Lineage 17 very happily thanks!
For the last couple of lineage installs though (2019-12-24 and 2020-01-08) I'm getting a failure in twrp when running a backup, on data partition specifically:
createTarFork() process ended with ERROR: 255
recovery.log is far more helpful:
Code:
# tail -n 50 /tmp/recovery.log
I:addFile '/data/anr/anr_2020-01-10-11-49-31-592' including root: 1
==> set selinux context: u:object_r:anr_data_file:s0
I:addFile '/data/per_boot' including root: 1
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/per_boot' - '0eb5afb598811574'
I:Error adding file '/data/per_boot' to '/data/media/0/TWRP/BACKUPS/161a6490/2020-01-10--16-29-03_lineage_sagit-userdebug_10_QQ1B200105004_en/data.ext4.win008'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
There's an (empty) folder '/data/per_boot' which seems to be breaking the backup process. I'm not sure if it's lineage itself or one of my apps creating this dir, but if I manually delete it the backup works... then it gets recreated next boot.
A somewhat minor issue, in case it's either easy enough to fix and/or other's run into the same problem!
I assume this twrp version use for flashing gsi. Am I correct?
Related
Disclaimer: Usual disclaimer applies. I've tested this recovery but it might not work due to a different ROM / device / moon phase / etc. Use at your own risk.
Introduction
After working with upstream TWRP developers and fixing some bugs (in TWRP itself and in this port) this device finally has an official port
There were various builds available at different times (some with bugs) but most of them should now be fixed.
Features
Works
backup/restore
installing zips
ADB
MTP
Screen turns off
Basically the rest of this list
format /data
Adoptable storage
Decrypt /data
Doesn't work (please ask if you need this)
Encrypted backup (set password for /data/data)
USB-OTG
Untested
Backup/restore of stock system / data.
Installation instructions
Warning: only use it on the G800F/M/Y, NOT on the G800H! I only tested the G800F, but think G800M/Y will also work. G800H will most likely NOT work, as it is based on a different SoC (Qualcomm).
Download the recovery image from twrp.me. It also includes some installation instructions.
There are more extensive installation instructions over at the LineageOS ROM installation instructions.
I personally prefer using Heimdall, but you can also use Odin. Commands in Download/Odin mode (power off, then press home+Volume-Down+power):
Code:
heimdall flash --RECOVERY recovery.img
If you're using the stock ROM, use:
Code:
heimdall flash --RECOVERY recovery.img --no-reboot
When you come from the stock ROM you have to make sure the stock ROM doesn't overwrite TWRP: Pull the battery, wait 5 seconds, insert it again, and press home + volume up + power to enter TWRP and replace the stock ROM from there.
If you already have TWRP or LineageOS, it's much easier to install from there, see twrp.me.
Another method is using ADB (from your computer). I used it a lot during testing:
Code:
adb root
adb push twrp-3.1.1-1-kminilte.img /dev/block/mmcblk0p10
Changelog
Code:
2017-07-10:
* fix formatting /data while the partition is encrypted
(device is not encrypted by default)
* add support for adoptable storage
* accept kminiltexx etc. for flashing basebands
2017-06-20:
* ADB
* MTP at the same time as ADB
* Screen turns fully off
* fix for restoring backups made using `adb backup --twrp`
Source code
Kernel: https://github.com/TeamWin/android_kernel_samsung_kminilte/tree/cm-14.1
Device: https://github.com/TeamWin/android_device_samsung_kminilte/tree/cm-14.1
This recovery is built using a LineageOS tree. Instructions are similar to the instructions for building LineageOS for the S5 mini. Differences are: you don't need to patch the source (skip that step) and the last step is mka recoveryimage instead of mka bacon - this only builds the recovery resulting in much faster builds. Also see the official build instructions.
Thanks
Other people who have worked on this project:
Team Win, of course, for the recovery itself! In particular bigbiff which has worked with me to make this device official.
hennymcc
RVR
---
Note to moderators: this is my first DevDB thread started on XDA so I may have made mistakes.
XDA:DevDB Information
Team Win Recovery Project, ROM for the Samsung Galaxy S5 Mini
Contributors
ayke, hennymcc, RVR
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2017-06-20
Created 2017-06-24
Last Updated 2017-07-09
Thanks!
OFFICIAL TWRP...I can't believe it
Great work on this one...many thanks.
Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
P.S. Is it possible to add support for adopted storage, that would be awesome!
Nevertheless - thanks for making this device officialy supported!
Friedensfurz said:
Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
Click to expand...
Click to collapse
The current kernel used upstream is somewhat older and hasn't enabled SELinux yet. I don't see why you would want enforcing SELinux in TWRP, though.
Friedensfurz said:
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
Click to expand...
Click to collapse
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Friedensfurz said:
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
Click to expand...
Click to collapse
Nice!
Friedensfurz said:
P.S. Is it possible to add support for adopted storage, that would be awesome!
Click to expand...
Click to collapse
I might look into it. I don't use it at the moment but am considering it.
EDIT: I have fixed it, it will be included in the next build.
any chance for g800h support?
sasukesama said:
any chance for g800h support?
Click to expand...
Click to collapse
Not from me. The G800H is a completely different device. I have a G800F so I can't test it.
ayke said:
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Click to expand...
Click to collapse
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]
Friedensfurz said:
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]
Click to expand...
Click to collapse
Can you give a link to where you downloaded this zip? Then I can test it myself.
I also get the device error with latest official and 2017-06-25-recovery-fix-ota-asserts.img.
Tried to flash one of Spookcity's kernels, you can find it here (search for "test9" that is what I used lately).
https://github.com/Spookcity/ROMS-G800F/issues/10#issuecomment-301915315
The latest pre-official TWRP 3.1.1-0 works (says kminiltexx).
ayke said:
Can you give a link to where you downloaded this zip? Then I can test it myself.
Click to expand...
Click to collapse
This file causes problems with the device id: http://pt.tapatalk.com/redirect.php...1_22.05.2017_DRE-flashable.zip&au_id=13587482
It is a TWRP flashable baseband file, hope this helps
@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.
ayke said:
@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.
Click to expand...
Click to collapse
Yeah,I removed all of my test build links from my google drive, but have a thread on here. I already sent you this though. I will test your new build and see if it helps.
Edit:
Yep,fixed. Good work Ayke!
Sent from my SM-G800F using Tapatalk
Friedensfurz said:
...
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
...
Click to expand...
Click to collapse
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I have the same problem
Here also this message in unofficial builds, don't tried it, but I think its still present in this version.
fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/data ext4 /dev/block/mmcblk0p21 length=-16384
...
fidoedidoe said:
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/dataext4/dev/block/mmcblk0p21length=-16384
...
Click to expand...
Click to collapse
I got it to work by formatting/repairing/changing filesystem in TWRP. Just try some combinations, it will work eventually
Yes, I think it's because of the 'auto' in the fstab. I've set it to ext4 in this build (for data and cache):
https://aykevl.nl/download/2017-07-03-recovery.img
This build also contains the previous fixes (adoptable storage, fixing the kminiltexx error).
If it fixes the issue for you, I'll push the change for inclusion in the next official build.
I didn't see any negative consequences of changing the FS type in fstab. Even setting the fstab entry to 'f2fs' mounts /data as usual (as ext4) so I think it's safe.
ayke said:
https://aykevl.nl/download/2017-07-03-recovery.img
Click to expand...
Click to collapse
Can someone test this change? Then I'll integrate it in the official build.
This is a TWRP fully Treble-ready with "Treble enabler" option in order to repartition safely the device.
Features:
TWRP fully Treble-ready;
Maintained with latest TWRP version;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
USB-OTG fixed
Has 'TWRP survival' function for automatically re-installing TWRP recovery when installing ROMs and kernels;
Adds a "Treble enabler" option that allows you to repartition your device in order to support Treble.
Has the option to shrink userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
If you shrink Userdata, it will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Instructions
Flash the recovery.
Reboot Recovery
Optional - Use the "Advanced > Treble enabler" option for repartition option.
If you opted to repartition for Treble, you are ready to flash a Treble ROM/Vendor pack.
About TWRP survival
TWRP survival is a simple hook that detects if a boot.img will be installed and restores TWRP after it's flashed. This only works if you have booted TWRP with Tissot Manager 2.0 from a real recovery boot - NOT from a recovery 'hot boot' (fastboot boot method).
You will see in the install log if a TWRP survival attempt is successful in the flash text output.
Automatic TWRP survival works when:
Flashing a ROM ZIP (or AIO) with TWRP
Flashing a boot.img in TWRP "Install Image" mode
Automatic TWRP survival does NOT work when:
Flashing a boot.img via fastboot
Restoring boot in a TWRP backup
Any other way of flashing a boot.img
In these cases, be sure the use the TWRP Installer immediately after flashing or restoring a backup - otherwise you may get the device into a confused state (especially if you restore a non-TWRP boot then try to install an AIO ROM without installing a new TWRP first).
Download
https://zenfone3-dev.gitlab.io/recovery/twrp-treble/
FAQ
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) My PC can't see the MTP (storage) device from TWRP!
A) For dualboot compatibility, MTP is automatically disabled at various points. Just enable it manually in the Mounts menu to get access.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes!
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM.
Thanks to:
@CosmicDan for his files for Tissot Manager & this thread template
@makorn645, @planet9, @Oki for Party
XDA:DevDB Information
TWRP Recovery for Zenfone 3, Tool/Utility for the Asus ZenFone 3
Contributors
Giovix92, makorn645,
Source Code: https://github.com/Giovix92/android_device_asus_zenfone3/tree/twrp-8.1
Version Information
Status: Stable
Current Stable Version: 20190312
Stable Release Date: 2019-03-12
Created 2019-03-12
Last Updated 2019-03-12
@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.
dVinsmoke said:
@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.
Click to expand...
Click to collapse
Just the treble los16 zenfone3 on our forum for now
iamROOTX said:
Just the treble los16 zenfone3 on our forum for now
Click to expand...
Click to collapse
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol
dVinsmoke said:
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol
Click to expand...
Click to collapse
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.
makorn645 said:
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.
Click to expand...
Click to collapse
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?
dVinsmoke said:
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?
Click to expand...
Click to collapse
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )
makorn645 said:
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )
Click to expand...
Click to collapse
Also, when vendor img will be split from the ota package, with (if necessary) some adjustments we can flash GSI ROMs easily.
Great work guys!! Waiting for vendor partition, for some tests!
Williknot said:
Great work guys!! Waiting for vendor partition, for some tests!
Click to expand...
Click to collapse
Well, repartition works fine. After repartition a new /vendor partition of 1024mb will be made.
Although, you'll loose your data (apps+personal). So make sure to do a full backup of your device.
Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.
Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?
[QS said:
;79165451]Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?
Click to expand...
Click to collapse
A bugfix release will be coming along with the next LineageOS build.
fcbn98 said:
Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.
Click to expand...
Click to collapse
Well, that's normal.
Since you're going to make a new /vendor partition of about 1024mb, /data should be deleted & recreated in order to give some space to the new partition.
Also, what do you mean with "can be resized to the wrong size"?
The tool is pretty stable tho. Can you give more info such as model (ex. ZE552KL 4/64), script version (ex. 4.3b) & other?
Thanks.
I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.
Kaisogen said:
I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.
Click to expand...
Click to collapse
Did you follow these steps properly?
https://zenfone3-dev.gitlab.io/tutorials/repartition
can i flash android q gsi images using treble recovery.
Switching back to stock rom
If I have made the treble partition using this recovery is there any way to go back to stock rom?
Avinash007 said:
If I have made the treble partition using this recovery is there any way to go back to stock rom?
Click to expand...
Click to collapse
Wipe vendor, data, cache, dalvik partition and flash any ROM normally.
Can i flash android Q gsi image using this recovery on ze520kl
Thread template from CosmicDan's thread.
About
This is a TWRP Installer ZIP and bootable IMG with extra capability such as Treble-izing and other power-user tools with integrated TWRP-powered submenus that CosmicDan originally called Tissot Manager.
Few months ago, CosmicDan officially decided to leave Tissot development, and his twrp was stuck on 3.2.3. So I decided to update that to 3.3 and convert all the aroma stuff into TWRP-powered menus etc, in order to preserve better future compatibility.
HIGHLY recommended reading and guide for everyone new to Treble - [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan. It also has some general protips hidden within there, for example the seamless/slot system interactions and nuances, so it's worth reading for anyone who wants to be a master of the Android flashing domain
Features:
TWRP fully Treble-ready based on 3.3.1-0;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
Full USB-OTG support;
Full MTP support;
Optional TWRP Survival function, that works both in hotboot and real recovery;
Optional Active slot install method, selectable right before the zip flash;
Option to ignore Payload<>Recovery certificate failures (fix for newer LOS-based ROMs);
Added a Tissot Manager list item under Advanced Menu, totally built-into TWRP itself that allows you to do:
Has the option to shrink Userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
Treble-izing will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Adds a "Patches" section with the following current options:
Patch kernel from Enforcing to Permissive and vice versa
More features coming!
All of this info is detailed inside the Tissot Manager GUI.
See screenshots in post 2.
Since this is an early version (still stable), some original features from 3.2.3 are still not available. I'll do my best to constantly add new functions when possible!
Instructions
Optionally boot the boot-recovery.img to get a temporary TWRP if you don't have it installed, unzipped from TWRP-3.3-withTM-BOOT.zip
Code:
fastboot boot boot-recovery.img
Warning - do not EVER flash this img - hotboot it only.
Flash the TWRP Installer. Any slot, any ROM, any existing Recovery - it doesn't matter - it will be installed to both slot kernels.
Reboot Recovery
Optional - Use the "Advanced > Tissot Manager" option for repartition options and other advanced ROM patches, this time built-in TWRP itself for better compatibility with future versions.
About TWRP survival
Starting from 1.0, TWRP Survival will be able both in hotboot mode 'n real recovery mode. Just tick the checkbox 'n flash!
Download
All downloads (and source code) always at:
https://github.com/Giovix92/twrp_device_xiaomi_tissot/releases
Additional sources not able to be listed in DevBB:
Modified update_engine: https://github.com/Giovix92/android_system_update_engine
What's next?
See [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan for detailed instructions and learning on how to Treble like a pro.
FAQ
Q) After I flash TWRP, I get kicked into a Recovery loop when trying to boot the ROM!
A) This is probably because you have a kernel that does not disable dm-verity. To fix this, flash Magisk.
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest way for using stock ROM on Treble repartition. May also require a custom kernel with dm-verity disabled (see Questions above regarding fastboot kick and recovery loop).
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM. This may occur while flashing in the active slot.
Q) What "Inject TWRP after install" option does?
A) It's TWRP Survival. If you check that checkbox, then after the installation of your zip file the TWRP will automatically reinstall TWRP into your slot.
Bugs Report
If any bug/problem may occur, feel free to report it here! Explain the problem and attach the recovery log. You can get it by going to Advanced - Copy Log and sliding. Kernel log isn't necessary.
If, for some strange reasons, you are unable to get into that menu', connect your phone to PC, open up CMD (aka command prompt) and type:
Code:
adb pull /tmp/recovery.log
Credits and Thanks
- @CosmicDan for tips, helps and his amazing work on TWRP 3.2.3, which I've taken many things from
- @nicknitewolf for his DT
- @chondoe for always being present in testing and reporting bugs/good news
- @flex1911 for DT stuff
- @mauronofrio for inject twrp function
XDA:DevDB Information
TWRP 3.3.1-0 with Tissot Manager, ROM for the Xiaomi Mi A1
Contributors
Giovix92
Source Code: [url]https://github.com/Giovix92/device_xiaomi_tissot[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-10-01
Created 2019-10-01
Last Updated 2019-10-01
Reserved
Changelog:
**10-11-2019**
- Fixed error 28 and 13, this led to some issues while doing a clean installation.
- Restored active slot install functionality, now it's fully working.
**18-10-2019**
Version: 2.0 (MAJOR UPDATE)
- Fixed all kind of problems while flashing:
- Error 51, 15, 31, 17, 35 (postinstall)
- Unability to make a clean flash
- Removed changelog section from Tissot Manager
- Added ADB God Mode
- Added missing binary, required in order to let selinux changer work properly
- Now the 2 new checkboxes won't stay checked anymore after any zip install
- Added system remount to r/w after zip flash in order to flash multiple zips in the same recovery session (like ROM + magisk + gapps and then reboot)
- Fixed linker problem that was causing some options in Tissot Manager to fail
- Smoother experience
Older changelogs:
**01-10-2019**
Version: 1.0
- Initial release with Tissot Manager, now powered by TWRP
- Optional TWRP Survival
- Ability to install into same slot
- Ability to repartititon to Treble and vice versa
- More features coming!
Reserved
Great work.
Sent from my Mi A1 using Tapatalk
Thanks ??
Nice. Bro you carried legacy ?
nice work waiting for shrp version of this ??
Noice :good:
Sent from my Mi A1 using XDA Labs
This is an update of TWRP Comic Dan?
manchirua said:
This is an update of TWRP Comic Dan?
Click to expand...
Click to collapse
Read op
Any way to flash it using cosmic dan's twrp? I don't have any pc now
Anikur Rahman said:
Any way to flash it using cosmic dan's twrp? I don't have any pc now
Click to expand...
Click to collapse
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Great job dude ?
Awesome work!
Thank you so much for this.
@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?
sdeft said:
@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?
Click to expand...
Click to collapse
You can check current slot from reboot menú.
Where is the survival checkbox??
What is this "inject twrp" does ?
oskrprez said:
Where is the survival checkbox??
Click to expand...
Click to collapse
Anikur Rahman said:
What is this "inject twrp" does ?
Click to expand...
Click to collapse
That's the TWRP survival option
Unipo said:
That's the TWRP survival option
Click to expand...
Click to collapse
So, Isn't it automatically reinstalled like Comic Dan's version?
I'M NOT RESPONSIBLE FOR ANY BRICKED DEVICES, DATA LOSS, OR THE WORLD WAR III...
FLASH THIS AT YOUR OWN RISK
ALWAYS READ THE INSTRUCTIONS BEFORE INSTALLING ANYTHING CAREFULLY.
IF YOU ARE NOT SURE, ASK IN THE COMMENTS BELOW OR IN THE TELEGRAM GROUP FOR HELP. OTHERWISE, DON'T BLAME ANYONE OTHER THAN YOURSELF
Bugs
-Userdata decryption is not working. You can flash multi disabler (check this before flashing) to disable encryption or use an external SD or USB OTG for putting ZIPs and IMGs on it in order to flash them
- Data backup is not working due to device encryption
How to Install
0. READ F.A.Q section first here
1. Unlock your bootloader
2. Boot to Odin mode
3. Check AP box and select TWRP tar file
4. Hit start
5. Reboot to TWRP and flash multi disabler if you want (check this before flashing it)
6. Have fun
Download
TWRP 3.5.1_10 - Beta 2
Multi Disabler
Sources
TWRP device tree
Kernel source
Change Log:
Beta 2 - 24th of March 2021
- Update to latest kernel 4.14.190
- Fix MTP on the latest kernel
- Clean up dynamic partitions
- Released kernel 4.14.190 source
Beta 1 - 20th of March 2021
- Initial Release
F.A.Q:
What is data encryption and why doesn't it work on TWRP?
Samsung M51 uses file-based encryption that encrypts the user data partition.
By default, TWRP can't decrypt user data partition, which makes it impossible for us to access the internal device storage from TWRP or recovery MTP, which means you can't put ROM files on your internal phone storage and flash them from there.
What is Multi disabler and how does it affect your phone?
- Multi disabler disables and removes the encryption on the data partition, which makes it possible for you to access your internal storage from TWRP or recovery MTP. thus, making it possible for you to flash files from internal storage.
- Removing the encryption on your device's internal storage makes it possible for you to access your files from recovery directly, which makes it possible for anyone to access your private files without your permission from recovery.
- All of the above means that your device will be less secure. So if you care about device encryption then don't flash the multi disabler and use a USB OTG or a sdcard to flash ROMs, which I recommend. Otherwise, flash the multi disabler at your own risk!!!
- FLASHINF MULTI DISABLER REQUIRES PERFORMING A FULL DATA WIPE WHICH MEANS YOU WILL LOSE YOUR DATA. SO BACKUP YOUR DATA BEFORE FLASHING IT.
My device keeps rebooting to recovery after flashing TWRP, why?
Most probably you will need to wipe your data partition and flash multidisabler
Data backup is not working even after flashing multidisabller, why?
Current multidisabler still can't fully disable FBE encryption, which means that TWRP can't read data partition at all, hence creating backups will always fail.
Reserved just in case
Thank you so much for your efforts,
Does backup, restore, work smoothly in this version of twrp? Does it fully restore after making a backup? Or are there still mistakes?
In Twrp 3.4.0 Data backup is not loading. Nonoperating. But the system is loading.
Oh, thank you, thank you.
onurmemo77 said:
Thank you so much for your efforts,
Does backup, restore, work smoothly in this version of twrp? Does it fully restore after making a backup? Or are there still mistakes?
In Twrp 3.4.0 Data backup is not loading. Nonoperating. But the system is loading.
Oh, thank you, thank you.
Click to expand...
Click to collapse
Currently I have no working ROM so I can't test back and restore functionality. But backing data should be working.. don't take that for granted tho..
It would be great if you can test that and report if it's working or not, or wait until I or someone else test that.
thank you for your efforts. i installed this twrp and flashed mutlidisabler. also formatted data before reboot. Unfortunately twrp does not allow to create backups. Cannot unmount system partition etc...Your android 10 TWRP version is creating and restoring backups allright. So for now have to continue using android 10!
ilya33 said:
thank you for your efforts. i installed this twrp and flashed mutlidisabler. also formatted data before reboot. Unfortunately twrp does not allow to create backups. Cannot unmount system partition etc...Your android 10 TWRP version is creating and restoring backups allright. So for now have to continue using android 10!
Click to expand...
Click to collapse
What error do you get? Can send me the recovery log?
LahKeda said:
What error do you get? Can send me the recovery log?
Click to expand...
Click to collapse
i do not remember how to retrieve recovery log. this is a screenshot after I tried to do twrp backup:
ilya33 said:
i do not remember how to retrieve recovery log. this is a screenshot after I tried to do twrp backup:
Click to expand...
Click to collapse
backups will not work because of device encryption. Even after flashing mutldisabler, the device will keep encrypting the data.
LahKeda said:
backups will not work because of device encryption. Even after flashing mutldisabler, the device will keep encrypting the data.
Click to expand...
Click to collapse
Thanks.
Do you think that Magisk prerooting prior to TWRP flash might help here?
Or maybe we should just for full official Android 11 twrp release...
TeamWin updates TWRP to 3.5.1, Android 11 support coming soon
They're calling it a 'mini release' with a few notable feature improvements
www.androidpolice.com
LahKeda said:
backups will not work because of device encryption. Even after flashing mutldisabler, the device will keep encrypting the data.
Click to expand...
Click to collapse
Fyi -i have spare m51 device with android 11 installed. Ready to use it for any kind of twrp test builds. This is a good phone and we must have twrp for android 11 developed here. Thanks
ilya33 said:
Thanks.
Do you think that Magisk prerooting prior to TWRP flash might help here?
Or maybe we should just for full official Android 11 twrp release...
TeamWin updates TWRP to 3.5.1, Android 11 support coming soon
They're calling it a 'mini release' with a few notable feature improvements
www.androidpolice.com
Click to expand...
Click to collapse
prerooting won't solve encryption issues. Maybe when TWRP can be build using android 11, we can fix encryption issues or at least partially fix it.
ilya33 said:
Fyi -i have spare m51 device with android 11 installed. Ready to use it for any kind of twrp test builds. This is a good phone and we must have twrp for android 11 developed here. Thanks
Click to expand...
Click to collapse
Then go ahead and test this one. plus lineage 18.1 will drop here soon!
Backup failed
Error code: 255
saleem137 said:
Backup failed
Error code: 255
Click to expand...
Click to collapse
Did you even read the FAQ section?
anyways, backups will fail because of data encryption
Does this TWRP require to format data after installing without Multi disabler?
smallKING81 said:
Does this TWRP require to format data after installing without Multi disabler?
Click to expand...
Click to collapse
Nope, but you may need to install multidisabler to prevent the phone from reverting back to stock recovery. Don't formate the data after flashing Multidisabler and see if the phone boots or not
LahKeda said:
Then go ahead and test this one. plus lineage 18.1 will drop here soon!
Click to expand...
Click to collapse
well i already tested that twrp build and it does not allow to create backup (which is the main reason i need twrp to start with). i will test your lineage roms no problem. Do you think that twrp will work properly with lineage 18?
ilya33 said:
well i already tested that twrp build and it does not allow to create backup (which is the main reason i need twrp to start with). i will test your lineage roms no problem. Do you think that twrp will work properly with lineage 18?
Click to expand...
Click to collapse
Data backup doesn't work because of data encryption.
Yes! it's working without any problems with lineage 18
Hey!
I unlocked the phone (LLD-L31) with PotatoNV and installed TWRP 3.2.1-0 (from this page: https://ministryofsolutions.com/2020/03/honor-9-lite-emui9-1-twrp-and-root-lld-l31-l21-l22-al10.html), so far so good.
Now I found LOS 18 and 19 (testing) for this device: https://sourceforge.net/projects/andyyan-gsi/
But the sideload doesn't work.
Error: insufficient permissions for device.
I can see the phone via 'adb devices' (in the main menu of the TWRP)
BUT if I start adb sideload in TWRP I get no permissions.
tried sudo, but with the same result.
best regards
lay
#Edit1:
I restarted the adb server with as sudo
adb kill-server
sudo adb start-server
Now it shows Total xfer: 0.00x and breaks.
I think it has something to do with the img.xz files.
I just deleted the xz and tried to sideload it as img.
#Edit2:
ok, the ISOs are compressed.
'unxz blabla.iso.xz'
But the same result: Total xfer: 0.00x and breaks
Simply flash image in fastboot
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
-Alf- said:
Simply flash image in fastboot
https://forum.xda-dlinelineage-19.1-20220410-UNOFFICIAL-arm64_bvS.imgage-19.1-20220410-UNOFFICIAL-arm64_bvS.imgeveloplineage-19.1-20220410-UNOFFICIAL-arm64_bvS.imgers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
Click to expand...
Click to collapse
THANKS!
so it works via 'sudo fastboot flash system blabla.img'
So... LineageOG 19 (testing) gets 'invalid sparce file format at header magic' while flashing, but installes then everything, after that, it's hanging.
After that I tried this step from the link above:
"4. Run command fastboot reboot, unplug your phone, when appears on screen yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'.Reboot ."
Now it does not start the system, but the TWRP (without touchscreen), So i can not use it. Even if I flash LineageOS 18. If I now flash TWRP again and restart, I get to eRecovery and have no TWRP. If I reboot then in eRecovery, I get to LineageOS 18. For my understanding.... VERY strange!
The LineageOS boots and boots and boooooots now...
#Edit1:
tried now the ROMs from your link.
18.1 shows 'invalid sparce file format at header magic' and fails on install.
17.1 without GAPPS succeeds the flashing, but did not reboot in eRecovery, but the TWRP. There I did the same (wipe data, cache, davlik / factory reset) with the error 'unable to wipe cache'.
and it also does NOT boot the system, but TWRP without touchscreen
#Edit2:
I think the phone is dead
maby because of the TWRP wiping the data
The strange thing is, I can still write to the system partition and flash another LineageOS. But it never reboots to system, just to TWRP (in TWRP I can not mount 'system')
#Edit3:
I can not even reboot to fastboot. It always boots the TWRP
#Edit4:
formated (repaired) system in ext4 again
Now it can be mounted, but I can not get to fastboot-mode and get no device via adb.
I can just boot to eRecovery now. So I try the only one thing, that is there: recovery via wifi. It's downloading now the EMUI 9.1. So we'll see.
It's just crazy!
layalala said:
Now it does not start the system, but the TWRP (without touchscreen), So i can not use it. Even if I flash LineageOS 18. If I now flash TWRP again and restart, I get to eRecovery and have no TWRP
Click to expand...
Click to collapse
Your problem is that you don't read carefully.
Why do you have TWRP installed???
layalala said:
It's just crazy!
Click to expand...
Click to collapse
Indeed!
the problem was, that I first followed enother tutorials and then swiched to yours
so the TWRP was already there.
The point is, I got it!!!
After downloading new EMUI via wifi in eRecovery, I got everything back. Meanwhile my VM in the QubesOS did not want to accept the USB-Controller I used for adb-fastboot. So i switched to Windows and followed your tutorial. BUT with the ROMs from Andy Yan (https://4pda.to/forum/index.php?showtopic=896420&st=10780#entry100487186). And everything works! Even the testing LOS 19! Android 12 on that old phone, yeah! but it works rather good.
Your ROM (LOS 18.1) did not work for me. It showed error in header while flashing and broke the process. The ROM from Andy Yan (LOS 19) also showed an error in header while flashing, but the process worked after that.
now I'll try to root it and hope that this will work well
layalala said:
now I'll try to root it and hope that this will work well
Click to expand...
Click to collapse
did rooting succeed?
epicmann24 said:
did rooting succeed?
Click to expand...
Click to collapse
yes!
layalala said:
yes!
Click to expand...
Click to collapse
may i ask which gsi image and which magisk zip did you flash? as for me rooting does not work.
epicmann24 said:
which magisk zip did you flash
Click to expand...
Click to collapse
Running EMUI 9.1 you have to flash magisk_patched recovery_ramdisk (on EMUI 9.1 ramdisk is included in the recovery_ramdisk).
Also you can follow this guide:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
You can use files linked in this post, recovery_ramdisk and erecovery are the same for ANE and LLD devices. Use TWRP linked on this post (important!).
Edit: you can get root rights also via SuperUser:
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed)
https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE
layalala said:
the problem was, that I first followed enother tutorials and then swiched to yours
so the TWRP was already there.
Click to expand...
Click to collapse
Hello,
Everything worked; even to the Lineage 19 rom, but, I couldn't install OpenGapps 12l (error 70).
I tried to replace the system "LOSQ - LineageOS 17.1-[10]-unofficial-GSI" via TWRP (system install) and I had the same problem, in addition to not being able to boot by eRecovery to download EMUI by Wi-Fi.
also, on TWRP, I don't have the option to mount "system"
How did you do?
[2022/07/06 - EDIT]
--> eRecovery done
--> Download in progress
--> EMUI 9 Install done
--> go test lineage 18.1 first
Rahinsoo said:
I don't have the option to mount "system"
Click to expand...
Click to collapse
This option is only on GSI vndk-lite version
Keep in mind, that on the Honor 9 lite, in the latest firmwares, the system partition is only 2312 Mb, if I'm not mistaken (on ANE-LX1, the system is 3270 Mb). So those GSI ROMs that work on ANE (Losq, LiR, PE+ etc.) probably won't work on LLD.
https://forum.xda-developers.com/t/kernel-emui-9-p20-lite-phenix-kernel.4241503/post-87085313
-Alf- said:
This option is only on GSI vndk-lite version
Keep in mind, that on the Honor 9 lite, in the latest firmwares, the system partition is only 2312 Mb, if I'm not mistaken (on ANE-LX1, the system is 3270 Mb). So those GSI ROMs that work on ANE (Losq, LiR, PE+ etc.) probably won't work on LLD.
https://forum.xda-developers.com/t/kernel-emui-9-p20-lite-phenix-kernel.4241503/post-87085313
Click to expand...
Click to collapse
That's right, I managed to install open gapps pico in some instance, especially on the bvs_vndklite versions.
What is the difference between bvs version and bvs_vndklite version?
Rahinsoo said:
That's right, I managed to install open gapps pico in some instance, especially on the bvs_vndklite versions.
What is the difference between bvs version and bvs_vndklite version?
Click to expand...
Click to collapse
Very simplistically written:
generally, vndk-lite build are designed for vndk-lite vendors, vndk for vndk vendors.
But on Phhusson AOSP based GSI ROMs there is one change from v300 version (or so): A/B non-lite builds are read-only (due to new phh patches),
A/B vndk-lite builds are in r/w mode, i.e. allow mount system and system modifications.
-Alf- said:
Very simplistically written:
generally, vndk-lite build are designed for vndk-lite vendors, vndk for vndk vendors.
But on Phhusson AOSP based GSI ROMs there is one change from v300 version (or so): A/B non-lite builds are read-only (due to new phh patches),
A/B vndk-lite builds are in r/w mode, i.e. allow mount system and system modifications.
Click to expand...
Click to collapse
Can I use this version without particular problems on my honor 9 lite?
Rahinsoo said:
Can I use this version without particular problems on my honor 9 lite?
Click to expand...
Click to collapse
Read carefully.
Oh, I'm sorry, I misunderstood ^^'
my question was for the vndklite version because I'm having a hard time figuring out the difference.
Rahinsoo said:
my question was for the vndklite version
Click to expand...
Click to collapse
I answered you, didn't I?
Currently I tested several roms. Only certain Andy Yan roms in the version without Gapps work correctly and allow the installation of Gapps.
OK test:
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite
+ Open Gapps pico OK
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite.img --> OK
+ Gaaps --> pico OK ---> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lineage-19.1-20220613-UNOFFICIAL-arm64_bgS-vndklite.img --> OK
+ Gaaps --> pico OK --> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lir-v316-220325-arm64-bgZ-lite.img --> OK
+Gaaps --> pico OK --> play store OK --> factory reformat impossible (automatic boot on TWRP)
What is the procedure for factory reformatting to work normally without booting to TWRP?
Rahinsoo said:
Currently I tested several roms. Only certain Andy Yan roms in the version without Gapps work correctly and allow the installation of Gapps.
OK test:
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite
+ Open Gapps pico OK
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite.img --> OK
+ Gaaps --> pico OK ---> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lineage-19.1-20220613-UNOFFICIAL-arm64_bgS-vndklite.img --> OK
+ Gaaps --> pico OK --> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lir-v316-220325-arm64-bgZ-lite.img --> OK
+Gaaps --> pico OK --> play store OK --> factory reformat impossible (automatic boot on TWRP)
What is the procedure for factory reformatting to work normally without booting to TWRP?
Click to expand...
Click to collapse
Why do you have TWRP there? You don't need it to install GSI. And if you have TWRP installed instead of Recovery, then it should be clear...