Related
Hello friends , i want help to change SELinux mode to permissive.
Im using Indian Variant on Oreo Beta.
setenforce 0 in terminal command didnt work.
Thanks
The same issue on P10 lite EMUI8.0
There is an app called selinux switch but only works on rooted phone
There currently isn't a way to make it passive from what I can tell. The switch app doesn't do anything on oreo/emui 8
TabTapper said:
There is an app called selinux switch but only works on rooted phone
Click to expand...
Click to collapse
Doesn't work on the devices mentioned.
Can you change the title to read as a question please? This leads readers to think that this is an instruction on How to change SELinux mode.
You can set it to permissive by downloading the Morfuz kernel in the Kernel section, then using the SELinux Permissive module in Magisk, but if you are doing this to try and install Viper4Android, it only has 32 bit drivers and the honor 7x is 64 bit, so it won't work.
Update 180914:
Always believe something wonderful is just going to happen.
WARNING:I‘m not responsible for any consequences at all.This is an OEM rom ported from Redmi phone so it may cause wrong behaviors including partition overwritting and may brick your phone or break hardwares.I strongly recommend you take a completely full backup of your device and know how to recovery firmwares in case of any problems.
This is still in early stage and should be normal if some features are broken.
Working on Qualcomm fully-Trebled deivces.
Maybe working on other platfrom fully-Trebled deivces.
8.1 vendor (vndk27) should be needed.
Bugs:
Light HAL(Brightness acting strange, this is a MIUI traditional)
SELinux
Credits:
@erfanoabdi
Install for A-only:
1.enable Treble ,flash a fully-trebled 8.1 rom
2.Extract the .7z to your TWRP backup folder (/.../TWRP/BACKUPS/$(yourserialnumber)/
3.Restore MIUI10 /system with TWRP
4.flash two patch zip
5.wipe data,flash fbe_disabler and Permissiver (from tools) if needed for your device.
6.Reboot.
Normally it will boot to bootanimation.If it doessn't pass bootanim then take logs with
adb logcat > logcat.txt via PC.
NOTE:
IF YOU STUCK AT MI ACCOUNT LOGIN, make sure you flashed permissiver
If the device says your device has mi account locked, then pull simcard out and reboot to complete the setup.
If you're stuck at logo , please make sure you can boot sGSI
Telegram Group:
https://t.me/funtouchosp
For Chinese users you can contact me via Coolapk.See my signature.
v1:
Initial release
Download
GDrive https://drive.google.com/open?id=1hyyErzDrl-cre13AX4_A5aSAbRHurZvU
This for Aonly or A/B?
how about huawei device？
山海蓝精灵 said:
how about huawei device？
Click to expand...
Click to collapse
Idk, maybe need 8.1 vendor huawei device
fxsheep said:
WARNING:I‘m not responsible for any consequences at all.This is an OEM rom ported from Redmi phone so it may cause wrong behaviors including partition overwritting and may brick your phone or break hardwares.I strongly recommend you take a completely full backup of your device and know how to recovery firmwares in case of any problems.
This is still in early stage and should be normal if some features are broken.
Working on Qualcomm fully-Trebled deivces.
Maybe working on other platfrom fully-Trebled deivces.
8.1 vendor (vndk27) should be needed.
Bugs:
Light HAL(Brightness acting strange, this is a MIUI traditional)
SELinux
Credits:
@erfanoabdi
Install for A-only:
1.enable Treble ,flash a fully-trebled 8.1 rom
2.Extract the .7z to your TWRP backup folder (/.../TWRP/BACKUPS/$(yourserialnumber)/
3.Restore MIUI10 /system with TWRP
4.flash two patch zip
5.wipe data,flash fbe_disabler and Permissiver (from tools) if needed for your device.
6.Reboot.
Normally it will boot to bootanimation.If it doessn't pass bootanim then take logs with
adb logcat > logcat.txt via PC.
NOTE: If you're stuck at logo , please make sure you can boot sGSI
Telegram Group:
https://t.me/funtouchosp
v1:
Initial release
arm builds WIP
Download
GDrive https://drive.google.com/open?id=1hyyErzDrl-cre13AX4_A5aSAbRHurZvU
Click to expand...
Click to collapse
is volte working?
fxsheep said:
WARNING:I‘m not responsible for any consequences at all.This is an OEM rom ported from Redmi phone so it may cause wrong behaviors including partition overwritting and may brick your phone or break hardwares.I strongly recommend you take a completely full backup of your device and know how to recovery firmwares in case of any problems.
This is still in early stage and should be normal if some features are broken.
Working on Qualcomm fully-Trebled deivces.
Maybe working on other platfrom fully-Trebled deivces.
8.1 vendor (vndk27) should be needed.
Bugs:
Light HAL(Brightness acting strange, this is a MIUI traditional)
SELinux
Credits:
@erfanoabdi
Install for A-only:
1.enable Treble ,flash a fully-trebled 8.1 rom
2.Extract the .7z to your TWRP backup folder (/.../TWRP/BACKUPS/$(yourserialnumber)/
3.Restore MIUI10 /system with TWRP
4.flash two patch zip
5.wipe data,flash fbe_disabler and Permissiver (from tools) if needed for your device.
6.Reboot.
Normally it will boot to bootanimation.If it doessn't pass bootanim then take logs with
adb logcat > logcat.txt via PC.
NOTE: If you're stuck at logo , please make sure you can boot sGSI
Telegram Group:
https://t.me/funtouchosp
v1:
Initial release
arm builds WIP
Download
GDrive https://drive.google.com/open?id=1hyyErzDrl-cre13AX4_A5aSAbRHurZvU
Click to expand...
Click to collapse
AB support please!!!
wmfanboy25 said:
AB support please!!!
Click to expand...
Click to collapse
I don't have A/B devices ,so I don't get familiar with how A/B devices work,also this MIUI port is from an Aonly device, converting Aonly to A/B image is more difficult than vice versa
Global or Chinese?
Bootloop on Xiaomi Redmi Note 4 SD ( Mido ).
[email protected] said:
Bootloop on Xiaomi Redmi Note 4 SD ( Mido ).
Click to expand...
Click to collapse
take log or try clean flashing
Im flashing now to op5t and will report back soon.
Status:
1. Booted
2. Stucked in Sign in to your Mi Account, even if i disabled use cloud sync. I see is Couldn't check device security info.
Does this sgsi has arb feature?
Stuck at mi account log in. Couldn check device status
fxsheep said:
...
Click to expand...
Click to collapse
I want try at MiPad 4. It is arm64, aonly.
What do u think?
Can this be flashed on redmi note 3 pro (kenzo)?
other dead Rom
fountoutch Dead
Oos Dead
miui 10 Dead
I tried flashing this on the huawei p20 lite and I can't flash the patch 2. Gives error 1
ebautista said:
Im flashing now to op5t and will report back soon.
Status:
1. Booted
2. Stucked in Sign in to your Mi Account, even if i disabled use cloud sync. I see is Couldn't check device security info.
Click to expand...
Click to collapse
yogasetyaadi said:
Stuck at mi account log in. Couldn check device status
Click to expand...
Click to collapse
Reboot and retry, so many people booted
dcduartee said:
I tried flashing this on the huawei p20 lite and I can't flash the patch 2. Gives error 1
Click to expand...
Click to collapse
Mount vendor in twrp
dcduartee said:
I tried flashing this on the huawei p20 lite and I can't flash the patch 2. Gives error 1
Click to expand...
Click to collapse
Vendor mounted?
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
Click to expand...
Click to collapse
What's your phone's specifications?
Lanreallenjay said:
What's your phone's specifications?
Click to expand...
Click to collapse
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
Ask for help here
https://t.me/phhtreble/283195 <---
Read before any question ^^^
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
Click to expand...
Click to collapse
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
rupert3k said:
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
Click to expand...
Click to collapse
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
rupert3k said:
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
Click to expand...
Click to collapse
Have you tried formatting data with TWRP (to the part when it asks you to write "yes") then flash no-verity?
You should at least be able to flash TWRP. If you can't, just download the proper USB drivers for your device, it might be the culprit.
Cheers!
itShouldWork said:
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
Click to expand...
Click to collapse
Phh just hinted it's likely Pie vendor causing panics:
"First you need to flash stock rom. Then install magisk and then this gsi.
Though please note that on Pie vendor, S9 kernel panics and reboot every few minutes, so it is highly unusable."
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
I have tried Android 10 GSI , using latest Q update
ZoiraP said:
I have tried Android 10 GSI , using latest Q update
Click to expand...
Click to collapse
Is it usable? any random reboots/ annoying instability?
itShouldWork said:
Is it usable? any random reboots/ annoying instability?
Click to expand...
Click to collapse
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
ZoiraP said:
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
Click to expand...
Click to collapse
Camera quality might be fixed with Google cam, if you find a good port.
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
rupert3k said:
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
Click to expand...
Click to collapse
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
A\B
itShouldWork said:
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
Click to expand...
Click to collapse
No real experience but A\B devices have two slots ie double the partitions (OnePlus has 67) .
This allows updates to be installed while running from slot A while the updated system is copied to B.
Apparently Q requires A\B so now we're on Q may as well try that next time we're curious
Phh just released:
AOSP 10.0 v208
Fix suspend/dt2w for Samsung Q vendor
Fix backlight for Samsung Q vendor
Samsung Q's fine, love gestures but the bloat is killing me.
You can tell Q's going to be so much leaner without bixby & friends.
Glad we installed it to get compatible but I think now we probably stand a better chance with 10 GSI's, hopefully LOS17 & Pixel Experience get updated again soon.
Wondering whether to following the rooting instructions yet?
Phh did say "flash stock rom then magisk and then gsi"
https://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
ZoiraP's wondering why we sooo slow lol!
Wow this looks good: https://forum.xda-developers.com/ga...-s9--s9-cross-device-development/rom-t4020939
Project Treble for F8131/2 [Android 10]ReadMe
Hello, everyone, I'm Sjll. Tone family(Xperia msm8996 devices) will stay at kernel 4.9 for Android 10. Our treble support for Android 10 has been released. There are some differences between Treble Pie, you need to know that:
1. GSI should be A/B ARM64. NOT A only as Pie.
2. TWRP should use a new version for Android 10.
3. Never flash software binaries from SODP, it has been included in vendor.img
I am not responsible for bricked devices, dead SD cards
Required Files
Treble Files::
AndroidFileHost: Download Link
TWRP for Android 10.0::
Download Link
How to flash:
1. Download Treble Files and extract it.
2.
Code:
fastboot flash boot boot.img
fastboot flash oem vendor.img
fastboot flash system <Path of GSI.img>
3.Flash Twrp and other MODs.
4.Boot and enjoy
For F8132:
Flash a dual patch in twrp: You can download it from here.
For Devs:
See @local__hero's post: Link
Update and bugs:
V2.10:
Update to android-10.0.0-R31.
V1.96:
Update: Minimum brightness fixed.
V1.90:
Update: Rotation is fixed.
V1.86:
Update: Hotspot is fixed.
Bugs: Rotation is wrong.
V1.0:
Bugs: Hotspot is broken.
XDA:DevDB Information
Treble, ROM for the Sony Xperia X Performance
Source Codes
Link
Contributors
Sjll
ROM OS Version: 10.0
ROM Kernel: Linux 4.x
Paypal
I am very happy to receive your donation.
Version Information
Status: Beta
Created 2020-01-25
Last Updated 2020-03-18
Reserved
Reserved
hi sjjll ... thanks a lot .. the rom is very good and nice to use ... but this treble project doesn't support erfan GSi like your AOnly treble project ... almost all erfan ported ROMs that can boting the AOnly treble project can't boot at this treble project .. is there a solution ..? Thank you very much
edy sunanto said:
hi sjjll ... thanks a lot .. the rom is very good and nice to use ... but this treble project doesn't support erfan GSi like your AOnly treble project ... almost all erfan ported ROMs that can boting the AOnly treble project can't boot at this treble project .. is there a solution ..? Thank you very much
Click to expand...
Click to collapse
Hello, I think you'd better ask the GSI devs for help.
ok ... thanks a lot ... very good project ... bluetooth can't be connected in my device
Finally new treble project.. Thanks sjll.. Very appreciate it!
hi! i have a problem, my phone dont start, i try few gsi's ( AB arm64 format) and no one dont start, only trying finish bootanimations, can you help me? I have a f8132, and trying flash your fix for dual, but with it or whithout - dont work..
Hello.. Which gsi you were trying to use?
This vendor based on aosp pure gsi.. This will compatible with phhuson's gsi,expressluke's gsi,..you can try Pixel Experience by expressluke latest build.. Its already tested and booted.. Havoc os 3.1 Expressluke also working fine with this sjll's vendor..
Fhcker90 said:
Hello.. Which gsi you were trying to use?
This vendor based on aosp pure gsi.. This will compatible with phhuson's gsi,expressluke's gsi,..you can try Pixel Experience by expressluke latest build.. Its already tested and booted.. Havoc os 3.1 Expressluke also working fine with this sjll's vendor..
Click to expand...
Click to collapse
yes this treble project works well on havoc 3.1 expressluke .. i've tried it .. cooler and feels lighter ..
Thank's to sjll
Z3r0.v said:
hi! i have a problem, my phone dont start, i try few gsi's ( AB arm64 format) and no one dont start, only trying finish bootanimations, can you help me? I have a f8132, and trying flash your fix for dual, but with it or whithout - dont work..
Click to expand...
Click to collapse
Try lineage GSI please.
https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Sjll said:
Try lineage GSI please.
https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Click to expand...
Click to collapse
I trying lineage from you, trying havoc 3.1 expressluke and nothing
On lineage bootanimation dont start, on havoc problem with bootloop, idk how i cat solved this problem..
Sjll said:
Try lineage GSI please.
https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Click to expand...
Click to collapse
f8132. The patch for dual sim does not work. in single SIM card mode - it doesn’t work with all operators, I live in Kazakhstan - the beeline and the asset work without problems, Altel and Body 2 do not work. Wi-Fi also turns off after 10 minutes of use. is there any way to solve the communication problem? I liked everything, but for work I need two sims - Beeline and Altel. And it’s not convenient to carry two phones with you.
DAC doesn't work
what is the difference between v1 and v2?
OTG does not work
Cannot get this to work. Installing latest Oreo stock rom via flashtool. Booting it once. Then I put the device into fastboot mode, flashing everything exactly as described. I have tried several GSIs (PixelExperience, Lineage, HavocOS 3.1). Of course arm64 AB. When I reboot, I always end in a boot loop after the boot logo. When I boot into TWRP recovery, I see error messages like "cannot mount /data and unable to find crypto footer. Failed to mount /data…" and so on. But formatting /data in TWRP does not help: When I reboot afterwards it is just the same. Boot logo, reboot, boot logo, reboot.... forever.
Am I missing something? Do I have to disable encryption or soemthing like that? Thanks for any hints.
atlantix1 said:
Cannot get this to work. Installing latest Oreo stock rom via flashtool. Booting it once. Then I put the device into fastboot mode, flashing everything exactly as described. I have tried several GSIs (PixelExperience, Lineage, HavocOS 3.1). Of course arm64 AB. When I reboot, I always end in a boot loop after the boot logo. When I boot into TWRP recovery, I see error messages like "cannot mount /data and unable to find crypto footer. Failed to mount /data…" and so on. But formatting /data in TWRP does not help: When I reboot afterwards it is just the same. Boot logo, reboot, boot logo, reboot.... forever.
Am I missing something? Do I have to disable encryption or soemthing like that? Thanks for any hints.
Click to expand...
Click to collapse
After flashing stock and booting it once. Make sure to wipe everything except internal storage and SD and then flash the files. Also, have you tried flashing trough a PC?
Some random said:
After flashing stock and booting it once. Make sure to wipe everything except internal storage and SD and then flash the files. Also, have you tried flashing trough a PC?
Click to expand...
Click to collapse
Okay, I now also wiped everything *before* flashing the treble Images. But the result is the same. I flash via PC and the current version of fastboot. I have also tried now version 1.96 of the treble Images (tried 2 before) with no luck. Anyway, thanks for the advice.
atlantix1 said:
Okay, I now also wiped everything *before* flashing the treble Images. But the result is the same. I flash via PC and the current version of fastboot. I have also tried now version 1.96 of the treble Images (tried 2 before) with no luck. Anyway, thanks for the advice.
Click to expand...
Click to collapse
Hmmmmmmmm.
Sad
Sadly, thats all that comes to mind... What Rom Were you trying to install? (GSI)
TeamWin Recovery Project 3.4.0-0 for Nubia Z17 (nx563j)
Differences from official builds:
Support /vendor partition
Support FDE encryption
Support System-as-Root
Source code
Device tree
Kernel
Download
AndroidFileHost.com
Changelog
20200715:
- Update to TWRP 3.4.0-0
20200211:
- TWRP upstream
- Add missing blobs for decryption /data mount
20191211:
- First build
20200211.img There is an error
Error:Card die on Your Deprired Is Corrupt.
Official twrp is fine
Zjh0094 said:
20200211.img There is an error
Error:Card die on Your Deprired Is Corrupt.
Official twrp is fine
Click to expand...
Click to collapse
Logs or something ?
BeYkeRYkt said:
Logs or something ?
Click to expand...
Click to collapse
E:Unable to decrypt FBE device
I start ADB logcat in the terminal. Terminal feedback is: / sbin / sh: logcat: not found
Zjh0094 said:
E:Unable to decrypt FBE device
I start ADB logcat in the terminal. Terminal feedback is: / sbin / sh: logcat: not found
Click to expand...
Click to collapse
The device does not support FBE encryption. You can ignore it.
BeYkeRYkt said:
The device does not support FBE encryption. You can ignore it.
Click to expand...
Click to collapse
OK, I have solved it. Format DATA。
ok to flash it to z17s?
New build:
- Updated to TWRP 3.4.0-0
https://androidfilehost.com/?fid=8889791610682892862
BeYkeRYkt said:
New build:
- Updated to TWRP 3.4.0-0
https://androidfilehost.com/?fid=8889791610682892862
Click to expand...
Click to collapse
Is it now possible to install gsi with this twrp mean havoc 3.7 for example cause i don't get it with your 3.3.1 even bootsigning was no longer possible since last build maybe you can also build in ? Or could you explain how it works?
aljoscha81 said:
Is it now possible to install gsi with this twrp mean havoc 3.7 for example cause i don't get it with your 3.3.1 even bootsigning was no longer possible since last build maybe you can also build in ? Or could you explain how it works?
Click to expand...
Click to collapse
Sorry, but I don’t do and did not do the GSI builds.
Dear sir,
This TWRP doesn't have root function, I then flash Magisk, after that the Phone cannot boot. It shows 'the device is corrupt, it cannot be trusted and will not boot.'. Can you please advise how to resolve it?
backboycn said:
Dear sir,
This TWRP doesn't have root function, I then flash Magisk, after that the Phone cannot boot. It shows 'the device is corrupt, it cannot be trusted and will not boot.'. Can you please advise how to resolve it?
Click to expand...
Click to collapse
in TWRP sign boot
can you please anyway show how recovery you use .....?
still 3.2.3 ?
sry i was a bit tired of testing with new rom i was not getting done sign boot with any recovery by now
can you share a hole procedure step by step to have realized?
:angel::highfive:
aljoscha81 said:
can you please anyway show how recovery you use .....?
still 3.2.3 ?
sry i was a bit tired of testing with new rom i was not getting done sign boot with any recovery by now
can you share a hole procedure step by step to have realized?
:angel::highfive:
Click to expand...
Click to collapse
check here: https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Sry maybe we don't mean the same we can't sign boot.img with lineageos 17.1 we need to compile the eas kernel android 10 version from:ttps://forum.xda-developers.com/nubia-z17/development/nx563j-nx595j-eas-kernelunofficial-t3911048
I give it a try but stuck by havent found the needed toolchain by linux is acting for.......so sry dude?
P.s. you have to wrote the h at beginning of link if you want to visit or use the homepage of this device forum
twrp 3.5 is offical for our device ?
i don't got the vendor partition shown up in 3.5 .....
but i think i could remember because if not treble compatible?
but still i can install system .img i think .... so there is a need for to got control over vendor partition?
BeYkeRYkt said:
New build:
- Updated to TWRP 3.4.0-0
https://androidfilehost.com/?fid=8889791610682892862
Click to expand...
Click to collapse
thx