I'll get straight into the matter at hand.
DFE basically disables all the encryption the phone uses. Now that is explained let's get into the benefits of disabling it.
-Battery Life Improvement
-Slighty Better Response Times
So from looking at this you can say that it hardly does anything in terms of making your life easier.
Let's get to the verdict:
If you don't care about security and you trust yourself then i encourage you to disable it
Any mods that will make your experience better is a plus in my book.
P.s: If you are installing any type of gsi then you don't have any choice but to disable it.
Hope this helped you in someway or another.
It's more convenient. Everything else is a bonus.
Does my phone get re-encrypted when i flash a new rom build (pixel experiance) or a new firmware ? I dont get that part.
KabalLV said:
Does my phone get re-encrypted when i flash a new rom build (pixel experiance) or a new firmware ? I dont get that part.
Click to expand...
Click to collapse
DFE patches vendor.
Martensite said:
DFE patches vendor.
Click to expand...
Click to collapse
That's actually wrong information it only patches the android framework so like @KabalLV says the phone gets encrypted every time you wipe and install.
MechaNarutoSucks said:
That's actually wrong information it only patches the android framework so like @KabalLV says the phone gets encrypted every time you wipe and install.
Click to expand...
Click to collapse
I find fix.sh in the dfe.zip. I think this is how magic happen.
#!/sbin/sh
find /vendor/etc -name "fstab.*" -exec sed -i 's/forceencrypt/encryptable/g' {} +
find /vendor/etc -name "fstab.*" -exec sed -i 's/forcefdeorfbe/encryptable/g' {} +
find /vendor/etc -name "fstab.*" -exec sed -i 's/fileencryption/encryptable/g' {} +
And it was fine when I forget to flash dfe with already patched vendor.
MechaNarutoSucks said:
That's actually wrong information it only patches the android framework so like @KabalLV says the phone gets encrypted every time you wipe and install.
Click to expand...
Click to collapse
No.
Encryption is defined in late-stage fstab, and on treble devices that fstab is at /vendor/etc/
CosmicDan said:
No.
Encryption is defined in late-stage fstab, and on treble devices that fstab is at /vendor/etc/
Click to expand...
Click to collapse
Encryption happens in vendor/etc partition thats why when you try to update your device's vendor/firmware, the patch (DFE) will be overwritten with the new files thus enabling the encryption again. But updating only the system (like dirty flashing new LineageOS Rom like OTA update via TWRP [old build > new build]) it won't overwrite vendor/firmware thus the encryption stays the same (if enabled or disabled via patch)
Darklouis said:
Encryption happens in vendor/etc partition thats why when you try to update your device's vendor/firmware, the patch (DFE) will be overwritten with the new files thus enabling the encryption again. But updating only the system (like dirty flashing new LineageOS Rom like OTA update via TWRP [old build > new build]) it won't overwrite vendor/firmware thus the encryption stays the same (if enabled or disabled via patch)
Click to expand...
Click to collapse
Why are you replying to me lol....
Anyway, MIUI ROMs (the custom ones) all seem to include vendor too, which may or may not have FDE disabled.
It's perfectly fine to just flash FDE disable/optional any time, if it's already applied then it won't hurt. Unless it's a toggle script, which I haven't seen anywhere because that'd be annoying.
Sent from my POCOPHONE F1 using Tapatalk
CosmicDan said:
Why are you replying to me lol....
Anyway, MIUI ROMs (the custom ones) all seem to include vendor too, which may or may not have FDE disabled.
It's perfectly fine to just flash FDE disable/optional any time, if it's already applied then it won't hurt. Unless it's a toggle script, which I haven't seen anywhere because that'd be annoying.
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Just giving out additional info.. Hahahaha
CosmicDan said:
Why are you replying to me lol....
Anyway, MIUI ROMs (the custom ones) all seem to include vendor too, which may or may not have FDE disabled.
It's perfectly fine to just flash FDE disable/optional any time, if it's already applied then it won't hurt. Unless it's a toggle script, which I haven't seen anywhere because that'd be annoying.
Click to expand...
Click to collapse
That may be true but everytime i reflash the encryption turns on. So i don't know the exact answer but that's the out outcome of reflashing at least for me.
after flashing each update via twrp, should i flash DFE then magisk or it is needed once?
MechaNarutoSucks said:
That may be true but everytime i reflash the encryption turns on. So i don't know the exact answer but that's the out outcome of reflashing at least for me.
Click to expand...
Click to collapse
Because you're flashing MIUI? The ROM you're flashing, whatever it is, must have its own vendor. Open the ZIP on PC and check yourself if it has vendor.new.dat.br - there is your answer.
hosseinito said:
after flashing each update via twrp, should i flash DFE then magisk or it is needed once?
Click to expand...
Click to collapse
Just flash it again if in doubt, as said it can't do any harm.
Sent from my POCOPHONE F1 using Tapatalk
Is there a reason to still be using 18.0 DFE and not 18.1? Also I have magisk v19 installed. If I update this rom (10.3.4.0|9.4.1) should I flash dfe 18.1 and re-flash magisk v18.1 for the purpose? Thanks
CosmicDan said:
Because you're flashing MIUI? The ROM you're flashing, whatever it is, must have its own vendor. Open the ZIP on PC and check yourself if it has vendor.new.dat.br - there is your answer.Just flash it again if in doubt, as said it can't do any harm.
Click to expand...
Click to collapse
Ok then. Thank you?
CosmicDan said:
Because you're flashing MIUI? The ROM you're flashing, whatever it is, must have its own vendor. Open the ZIP on PC and check yourself if it has vendor.new.dat.br - there is your answer.Just flash it again if in doubt, as said it can't do any harm.
Click to expand...
Click to collapse
Like i said i don't know the exact idea on it so thx for the explanation.
And its true that i only update my rom when there is a new firmware update.
Can I just flash the DFE file in TWRP without wiping data or anything else? Right now I have Lineage installed with everything set up and I would not wipe everything right now just to flash DFE.
Hi i am on global 10.3.5 stable, rooted with magisk and twrp is not installed (only hot booted).
1. Can i just flash dfe?
2 what about ota update? If i just flash dfe Will it ask for any pin after doing ota update?? Or i can just update and then flash dfe again
3. Also i have one doubt. i flashed pixel rom once and i decided to revert back to miui. So i restored my twrp backup of miui and got bootloop. Then i flashed the 10.3.5 zip and vendr/firmware also. But after booting it asked me for pin. i had to fastboot flash the rom again. It wiped all my data. So what did i do wrong here. And how to restore miui twrp backup. Coz its really difficult to back up all the data in my phone every time i flash a rom. Thats holding me back from enjoying the custom roms. So any clarification would be highly appreciated. Thanks
MechaNarutoSucks said:
I'll get straight into the matter at hand.
DFE basically disables all the encryption the phone uses. Now that is explained let's get into the benefits of disabling it.
-Battery Life Improvement
-Slighty Better Response Times
So from looking at this you can say that it hardly does anything in terms of making your life easier.
Let's get to the verdict:
If you don't care about security and you trust yourself then i encourage you to disable it
Any mods that will make your experience better is a plus in my book.
P.s: If you are installing any type of gsi then you don't have any choice but to disable it.
Hope this helped you in someway or another.
Click to expand...
Click to collapse
but how do i do it? i only read dfe dfe dfe everywhere but can't find anywhere how to disable encryption
How can you tell the benefits without providing concrete proof? I am running encrypted since I got my POCO and installed LOS16. I haven't encountered any issues at all with regards to performance or battery life.
Related
DISCLAIMER:
I'm not the developer of any of those Roms, so don't cry on me if your device gets bricked!
INTRODUCTION:
So, as many of you guys know, the Homor 9 is Treble compatible which means you can get any Treble Rom on it although the support of our device on XDA is really poor on our forum.
IMPORTANT ISSUES:
Since we don't even have an official TWRP for the Honor 9 but only some kind of a buggy one with missing encryption on Android 8.1 (I mean I'm thankful for what we have, but it's still sad), I was NOT able to flash Gapps afterwards, which means, either you have to get a Rom with implemented Gapps or live without them.
If anyone finds out a way to install them, please let me know!
REQUIREMENTS:
- Unlocked bootloader
- Any Android Oreo firmware installed
- Stock Recovery (as our TWRP can't wipe stuff)
INSTALLATION:
1. Look for your favorite Rom on the following link and download it:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
2. Reboot your device to bootloader
3. "fastboot flash system [downloaded img file]"
4. Reboot to stock recovery
5. Wipe cache and factory reset
6. Reboot and enjoy!
I hope I was able to get some of your hopes up for Honor 9 and custom roms!
Thank u! But i have one question about this Treble Rom's... is all working? ( BT, WLAN, Sound ect.?)
nscounter said:
Thank u! But i have one question about this Treble Rom's... is all working? ( BT, WLAN, Sound ect.?)
Click to expand...
Click to collapse
Look at the bug list of each rom. As I said, I'm not the developer of any of those roms.
But I'm using the pure AOSP rom by phhusson and it's working perfectly fine without any issues as far as I can tell.
Is it compulsory to wipe data for a new ROM to work, say for example i'm going form AOSP 8 to AOSP 8.1, should the data partition be compatible and not require wiping?
Iv'e always wiped /data in the past, but i cant be bothered this time since i don't want to re-install everything.
ambitiousButRubbish said:
Is it compulsory to wipe data for a new ROM to work, say for example i'm going form AOSP 8 to AOSP 8.1, should the data partition be compatible and not require wiping?
Iv'e always wiped /data in the past, but i cant be bothered this time since i don't want to re-install everything.
Click to expand...
Click to collapse
I dirty flashed a few times - even going from AOSP to RROS for example and it went fine for me. So just try it out, reboot with only wiping cache and if you experience bugs you can still do a factory reset. But just keep in mind that many developers don't support dirty flashing because bugs can happen easily when doing that and it's also not recommended.
PS: Don't dirty flash a Rom without Gapps if you're using a launcher that requires Google Play Services!
_lucx_ said:
I dirty flashed a few times - even going from AOSP to RROS for example and it went fine for me. So just try it out, reboot with only wiping cache and if you experience bugs you can still do a factory reset. But just keep in mind that many developers don't support dirty flashing because bugs can happen easily when doing that and it's also not recommended.
PS: Don't dirty flash a Rom without Gapps if you're using a launcher that requires Google Play Services!
Click to expand...
Click to collapse
Excellent, thanks, I'll give it a try, I'll make sure I disable or uninstall xposed and disable substratum beforehand, I guess the worst that can happen is a bootloop, and I can just reflash old system image if it doesn't work .
How does ADB work for you on the AOSP treble rom?
Really_Rekt said:
How does ADB work for you on the AOSP treble rom?
Click to expand...
Click to collapse
Just tested it... I don't seem to be able to get it to work. :/ I don't know what the issue is either...
Hi,
currently i have installed RRR from OpenKirin (https://forum.xda-developers.com/honor-9/development/rom-t3754856) with magisk. But i think this ROM isn't updated anymore.
My question is: Can i install Treble Roms directly over OpenKirins ROM?
---------- Post added at 09:37 ---------- Previous post was at 09:31 ----------
Really_Rekt said:
How does ADB work for you on the AOSP treble rom?
Click to expand...
Click to collapse
Hi,
there are problems with magisk and adp: https://forum.xda-developers.com/showpost.php?p=76777735&postcount=282.
Saftpresse99 said:
Hi,
currently i have installed RRR from OpenKirin (https://forum.xda-developers.com/honor-9/development/rom-t3754856) with magisk. But i think this ROM isn't updated anymore.
My question is: Can i install Treble Roms directly over OpenKirins ROM?
---------- Post added at 09:37 ---------- Previous post was at 09:31 ----------
Hi,
there are problems with magisk and adp: https://forum.xda-developers.com/showpost.php?p=76777735&postcount=282.
Click to expand...
Click to collapse
Yes, you can flash it on top of any Project Treble (Oreo) Rom or EMUI 8 (Oreo) using my guide.
Magisk is kind of working for me although it crashes quite often and I have to reinstall the Manager or reflash it entirely fron time to time.
_lucx_ said:
Yes, you can flash it on top of any Project Treble (Oreo) Rom or EMUI 8 (Oreo) using my guide.
Magisk is kind of working for me although it crashes quite often and I have to reinstall the Manager or reflash it entirely fron time to time.
Click to expand...
Click to collapse
Thank you.
I read about problems with magisk and phhusson's gsi roms. I think to uninstall magisk before installing. I flashed magisk with fastboot, because i'm on stock recovery. So i have to read howto unroot with fastboot before i update.
_lucx_ said:
Just tested it... I don't seem to be able to get it to work. :/ I don't know what the issue is either...
Click to expand...
Click to collapse
The issue is talked about on PHH threads, it's caused by Magisk.
_lucx_ said:
Look at the bug list of each rom. As I said, I'm not the developer of any of those roms.
But I'm using the pure AOSP rom by phhusson and it's working perfectly fine without any issues as far as I can tell.
Click to expand...
Click to collapse
May I ask you how battery lie is, on AOSP?
enban said:
May I ask you how battery lie is, on AOSP?
Click to expand...
Click to collapse
Battery life was pretty good during my use without Xposed. I can't give you a specific battery life time now since I've installed Xposed which obviously made it a bit worse.
_lucx_ said:
Look at the bug list of each rom. As I said, I'm not the developer of any of those roms.
But I'm using the pure AOSP rom by phhusson and it's working perfectly fine without any issues as far as I can tell.
Click to expand...
Click to collapse
Hi,
I've several question for you :
1/ I wonder about security and privacy, do you think using aosp treble is better, than stock rom for that ?
2/ i don't care about gapps (gmail...), but i need the framework and google playstore.
If i take pure aosp without gapps does it have playstore and google frameworks ?
3/ which version do you use ? can you link me the version ?
Thanks.
Aqwel said:
Hi,
I've several question for you :
1/ I wonder about security and privacy, do you think using aosp treble is better, than stock rom for that ?
2/ i don't care about gapps (gmail...), but i need the framework and google playstore.
If i take pure aosp without gapps does it have playstore and google frameworks ?
3/ which version do you use ? can you link me the version ?
Thanks.
Click to expand...
Click to collapse
1. Well you kind of get a security risk anyway by unlocking the bootloader, rooting, etc. Other than that the Roms themselves are just what Android provides in terms of security.
2. No
3. for A-Only arm64 with Gapps and SU (https://forum.xda-developers.com/pr...development/experimental-phh-treble-t3709659)
_lucx_ said:
1. Well you kind of get a security risk anyway by unlocking the bootloader, rooting, etc. Other than that the Roms themselves are just what Android provides in terms of security.
2. No
3. for A-Only arm64 with Gapps and SU (https://forum.xda-developers.com/pr...development/experimental-phh-treble-t3709659)
Click to expand...
Click to collapse
Few questions for you buddy:
Does the camera work well?
Is fingerprint working well?
Do navkeys work?
I'm talking about aosp phh Treble.
And one thing, how to return to stock?
Extract system.img from stock rom with Huawei firmware extractor, flash it from fastboot like the aosp image, go to recovery and wipe cache and data, reboot and voila?
Double Chin Bigot said:
And one thing, how to return to stock?
Extract system.img from stock rom with Huawei firmware extractor, flash it from fastboot like the aosp image, go to recovery and wipe cache and data, reboot and voila?
Click to expand...
Click to collapse
Yes but you may use the os you had before flashing to treble, refer to https://forum.xda-developers.com/honor-9/help/help-to-stock-treble-custom-rom-t3804064
By the way thanks @_lucx_ for you answers
Double Chin Bigot said:
Few questions for you buddy:
Does the camera work well?
Is fingerprint working well?
Do navkeys work?
I'm talking about aosp phh Treble.
And one thing, how to return to stock?
Extract system.img from stock rom with Huawei firmware extractor, flash it from fastboot like the aosp image, go to recovery and wipe cache and data, reboot and voila?
Click to expand...
Click to collapse
- Yes 4K video is working (screen recording as well)
- Fingerprint is fully working with home button gestures set to Huawei's default for one button navigation - can be tweaked by editing the fingerprint.kl tho.
- Navbar is working fine for me but might have to do with the EMUI firmware you were on previously (although there's a fix for it now but I don't know if this fix works on Android 8.1)
_lucx_ said:
- Yes 4K video is working (screen recording as well)
- Fingerprint is fully working with home button gestures set to Huawei's default for one button navigation - can be tweaked by editing the fingerprint.kl tho.
- Navbar is working fine for me but might have to do with the EMUI firmware you were on previously (although there's a fix for it now but I don't know if this fix works on Android 8.1)
Click to expand...
Click to collapse
I think there's a misunderstanding. I was talking about the physical navigation keys (the ones near the fp sensor). Do they work as intended? Is it possible to deactivate the on screen navigation keys without root(because I want only the aosp Rom without anything else added)?
Today I flashed Pixel Experience GSI on my whyred after much trouble so here is a guide to make things clear.
if you are coming from MIUI you have to format data from twrp. this is a must to disable encryption.
after you are done formatting data. just do factory reset from twrp and then go to advanced wipe and then do the regular dalvik, cache, system, data and then swipe to wipe.
now the thing is whyred officially supports treble but the implementation is shoddy according to XDA folks. so if you flash GSI over miui's vendor there will be many bugs. like brightness slider not working and many things. so they(all credit goes to them) created a vendor zip which makes things really good. there are no bugs and it also supports volte. here is the download link .
https://www.androidfilehost.com/?w=files&flid=273660
now flash this zip file in twrp.
after that download the GSI of your choice from here.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
remember to download arm64 A only system image.
here is pixel experience GSI which I prefer:
https://download.pixelexperience.org/treble_gsi/
now extract the zip and you will get a single .IMG file which is your system image. now go to twrp and then go to install then go to select install image downward. (don't flash directly, it's an .IMG file) then select the extracted .IMG file and then choose system and then flash.
then reboot system. that's it. you should boot fine.
download latest official twrp from here: https://dl.twrp.me/whyred
if you want root you will have to flash magisk beta 16.6 which works better on GSI. download here.
https://github.com/topjohnwu/Magisk/releases/download/v16.6/Magisk-v16.6.zip
to use Google camera you will have to enable camera2api. arnova's gcam doesn't work on this build. you will have to use BSG's gcam. here is the link. enable nexus style and active portrait mode from settings.
https://www.celsoazevedo.com/files/android/google-camera/f/MGC_5.2.022.apk
few tips: if your device is not booting and going to fastboot, flash magisk. it will definitely boot up.
if your device shows decryption failed, just format data from twrp. it will delete all user data btw.
no need to flash lazyflasher.
there are no uncertified device pop up from Google. so no need to worry.
playstore shows uncertified btw and magisk shows CTS false.
all the links that I have linked here, the credit goes to the creators. I am a normal user of XDA. thanks to them.
happy flashing and all hail the XDA lords.
How is Pixel experience gsi though?....faced any bugs till now?
it's good but there where few bugs. anyway pixel experience rom specifically for whyred has been released. you can flash that. it's great and bug free. download it here. it's not GSI though. normal ROM.
https://download.pixelexperience.org/whyred/
mr._.nobody said:
How is Pixel experience gsi though?....faced any bugs till now?
Click to expand...
Click to collapse
mr._.nobody said:
How is Pixel experience gsi though?....faced any bugs till now?
Click to expand...
Click to collapse
I was on the June build, I had issues with bluetooth audio (didn't work) and USB connection to computer (did not work). I think the USB issue was due to Magisk but I never did figure out the bluetooth issue.
No issues with the whyred version of Pixel Experience.
I also faced the same issue. But I see July build of GSI is up so those bugs might be fixed. anyway the PE ROM for whyred is excellent.
btw GSI will help us when P will release next month.
goofball2k said:
I was on the June build, I had issues with bluetooth audio (didn't work) and USB connection to computer (did not work). I think the USB issue was due to Magisk but I never did figure out the bluetooth issue.
No issues with the whyred version of Pixel Experience.
Click to expand...
Click to collapse
mearjunsha said:
I also faced the same issue. But I see July build of GSI is up so those bugs might be fixed. anyway the PE ROM for whyred is excellent.
btw GSI will help us when P will release next month.
Click to expand...
Click to collapse
So should I flash the ROM or the gsi?....are there any differences?
you should flash the ROM as it's specifically for whyred. its flashing instruction is different than GSI. but easy. just wipe and then flash the ROM. and reboot. that's it.
you may have to format data to disable encryption.
here is the forum discussion: https://forum.xda-developers.com/redmi-note-5-pro/development/rom-pixel-experience-t3816099
mr._.nobody said:
So should I flash the ROM or the gsi?....are there any differences?
Click to expand...
Click to collapse
Thanks mate for your experience, no detailed information in PE thread about wipes to do, before or after, can help with it? May be also with magisk release to install and best gcam to use?
remove all security like fingerprint, pattern etc.
go to twrp
go to wipe
do factory reset
go to advanced wipe
select dalvik, cache, system and data and then wipe
go to install
flash the pixel experience rom
reboot to system
that's it
if you get a prompt to enter password to start android then you will have to go back to twrp and go to wipe and format data and type yes. it will delete all your files btw. so backup everything. then reboot it will boot up fine.
after you have done booting and set up, go back to twrp and flash magisk v16. reboot to system. all done.
I have already given details of gcam in my OP. Kindly check that. The same works great on this ROM.
ask me if you face any problem. happy to help ?
trazalca said:
Thanks mate for your experience, no detailed information in PE thread about wipes to do, before or after, can help with it? May be also with magisk release to install and best gcam to use?
Click to expand...
Click to collapse
You are the man!!! 10 hours remaining for unlock bootloader, i'm ready and now, with your help, more confident... Thanks a lot!!
I understand your excitement but do check your build whether you are on Anti rollback. if you are on 9.5.19 you should absolutely not proceed right now.
read about it on XDA.
trazalca said:
You are the man!!! 10 hours remaining for unlock bootloader, i'm ready and now, with your help, more confident... Thanks a lot!!
Click to expand...
Click to collapse
I'm on global 9.5.6... never used phone and upgraded, i think that i can do it, i'm wrong?
you can go ahead. happy flashing! ?
trazalca said:
I'm on global 9.5.6... never used phone and upgraded, i think that i can do it, i'm wrong?
Click to expand...
Click to collapse
[dupe sorry]
You should by all means read about antirollback to be sure, but my understanding is that the antirollback refers to the firmware, not the rom. MIUI roms all include different firmware, so you can't rollback a MIUI rom (unless it's been modded to be firmwareless). But as far as I know, no custom roms include firmware, so you should be fine even if your firmware is ARB triggered if all you're doing is installing custom roms.
Hi, someone flashed latest Pie Phh GSI? I tried with PE CAF, AOSIP, and Mokee vendors but doesn't boot, always stuck at the Mi logo, even I flashed the permissiver patch without luck.
Is GSI better than respective Rom (say Havoc GSI as compared to Havoc OS rom)?
ShadowFax said:
Is GSI better than respective Rom (say Havoc GSI as compared to Havoc OS rom)?
Click to expand...
Click to collapse
Nope.
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Maj3sty said:
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Voodoojonny said:
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Click to expand...
Click to collapse
I tried it and doesnt work. It seems the module changed any files in system(via root).
wenna.speedy said:
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
Click to expand...
Click to collapse
Nice try, but looks like you are not the only person with the same issue! I'm using Jetaudio and I have great sound with my JBL (Bluetooth) & Sennheiser wired headsets. I'm pass!!!
Mi A2 Lite using Tapatalk
lbsilva said:
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Click to expand...
Click to collapse
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Voodoojonny said:
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Click to expand...
Click to collapse
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
You can try install twrp and mount internal storage. I dont know if exists new version with working mounting.
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you try using MiFlashTool?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
Hmm, as told above, then your only option is a backup with twrp. If you can't decrypt data with twrp (after you installed it - not booting) you can try to boot to slot b - that sometimes help. Just select under reboot in twrp or type "fastboot set_active b"...
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
There is no wipe required, I just got caught in the loop as well.
Two things you need:
-TRWP installed
-Uninmod installed (magisk module remover)
1. If you are stuck in the loop, boot into fastboot,
- connect your pc and run ADB & fastboot cmd, run the command fastboot boot recovery.img(or your TRWP image) and run TRWP
2. Download Uninmod zip, transfer to phone. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
- Use TWRP to install Uninmod,
- remove the Notchkiller mod
- credits to veez21
3. find this file overlays.list and delete it from /data/resource-cache/overlays.list https://github.com/Magisk-Modules-Repo/NotchBarKiller/issues/3
- credits to MatChung
Reboot and there was like a minute of delay on same boot screen, but then it should boot fine.
If you are not stuck in the loop but just installed the module:
-remove the module in magisk
-find the file and delete it.
TLDR: remove the Notchbarkiller mod and remove overlays.list file. Reboot!
Hope it works. It did for me. Poco F1
I flashed this madule last night and found that it break calls. Could not make and receive phone calls. Huawei P20 Pro with EMUI 8.1 running.
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
D1stRU3T0R said:
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
Click to expand...
Click to collapse
Written in the first post...
wenna.speedy said:
Written in the first post...
Click to expand...
Click to collapse
I know...
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
SnoopDoggyStyleDogg said:
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
Click to expand...
Click to collapse
UPDATE: This thread is a false alarm as I managed to install the module on the March update and the only crash I get is from google play services with no bootloop and everything working. Maybe the OP has another phone and except that a module that is on the Mi A2 Lite thread should work on any phone or he's done something wrong. I will attach some screenshots to confirm that the module is indeed working and OP's post is a false alarm for stock A2 Lite ROMs (No custom ROM and not other phones)
NOTE: As you can see in the YouTube screenshot there's no black back on the left side of the screen as it should be without the module installed
Hi all,
I'm presenting here my ROM for S10e (whose main thread is https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915 ).
It is generic, but it doesn't mean anything bad!
Pretty much every works, and this is my daily driver (Exynos variant).
What works:
- Camera
- Wifi
- 2G/3G/4G, including signal level
- Phone calls
- Fingerprint sensor
- Encryption
- Proximity sensor
What doesn't work
- VoLTE
- stock OneUI camera app
- MTP
You can install some modded Google Camera on it for acceptable Camera quality.
Download links:
- With included gapps
- Without included gapps
How to flash:
- Flash back latest stock ROM
- Extract the img.xz into .img
- Flash it to system partition using Heimdall: https://glassechidna.com.au/heimdall/
- Flash this to vbmeta partition https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img (also using Heimdall)
- Boot once. The device will reboot into recovery, that's okay! Just do a factory reset and boot to system again.
- If it didn't reboot into recovery on its own, that's not normal (perhas you have magisk installed?), but still reboot into recovery and do a factory reset.
- Enjoy!
Recommended after installing:
- Default Launcher is AOSP's. It sucks. You should really install another Launcher. I recommend and use Lawnchair
- Pretty much no Google app is preinstalled, only Play Store and Chrome. You'll probably want to install Google, Google Assistant apps, Gmail, ...
free post for me and myself
Support for G9700?
Could system.img possibly be flashed through recovery? And you could've made it a flashable zip, we have a pretty ok recovery when you flash multidisabler
DeHuMaNiZeD said:
Could system.img possibly be flashed through recovery?
Click to expand...
Click to collapse
Yes
And you could've made it a flashable zip, we have a pretty ok recovery when you flash multidisabler
Click to expand...
Click to collapse
TBH I recommend not to flash any disabler, they bring more issues than they fix.
Android security is already not ideal, disabling encryption sounds like a very bad idea
(And disabling dm-verity is totally useless, because when flashing a GSI it already is)
NisseGurra said:
Support for G9700?
Click to expand...
Click to collapse
Yes G9700 is supported, though bear in mind that since it's not the same device, you don't really have the same guarantees. I'll help you through your issues either way.
Ok, tested on G9700, latest stock rom installed (android 9).
TWRP with multidisabler installed, format data, reboot recovery. Install V120 gsi, reboot.
Boots nicely.
Findings: no autobrightness, slider ok tho. Wifi/BT/NFC ok. No MTP (as stated)
Dual sim ok, voice calls ok, data ok. 3.5 output ok
Edit: Best way to root?, addonsu-16.0-arm64-signed.zip?
im gonna try this right away
i have one simple question before trying does magisk work with this and can i just use a magisk pachted system
---------- Post added at 07:32 AM ---------- Previous post was at 07:16 AM ----------
To my knowledge s10e is A-only and you linked A/B. What's up with that?
Edit:// It seems it is not, I have no idea why treble testing app from app store does not detect, that it is A/B
mikk150 said:
To my knowledge s10e is A-only and you linked A/B. What's up with that?
Edit:// It seems it is not, I have no idea why treble testing app from app store does not detect, that it is A/B
Click to expand...
Click to collapse
In the true sense, it is A-only, it doesn't have seamless update.
The difference between A-only and A/B was that A/B included the init, while A-only didn't.
But since Pie, A-only also includes init, like A/B. I didn't update the naming convention (because it just gets even messier).
Hackintosh5 developed Treble Info ( https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=en_US ) to make things clearer.
Do you have PHH for Android 10 for this device?
vlubosh said:
Do you have PHH for Android 10 for this device?
Click to expand...
Click to collapse
It is still unstable, that's why I haven't shown it in this forum yet.
Do these steps apply to any devices? Or only specific models? I have an Elephone Soldier, and I notice different website have different procedures. Not sure which one is right. Thanks.
"How to flash:
- Flash back latest stock ROM
- Extract the img.xz into .img
- Flash it to system partition using Heimdall: https://glassechidna.com.au/heimdall/
- Flash this to vbmeta partition https://dl.google.com/developers/and...gsi/vbmeta.img (also using Heimdall)
- Boot once. The device will reboot into recovery, that's okay! Just do a factory reset and boot to system again.
- If it didn't reboot into recovery on its own, that's not normal (perhas you have magisk installed?), but still reboot into recovery and do a factory reset."
I just installed AOSP 9.0 v119 for my Elephone Soldier. I can confirm the system boots up, but there is no sound. (ie. ring tone, media, notification) None of these sound work.
One question guys. If i root my s10e and flash custom rom, and then if i want to back to full 100% stock rom, o just need to flash it with odin and everything will be same like before? All apps will work like samsung health and pay? Thanks
BratoMo225 said:
One question guys. If i root my s10e and flash custom rom, and then if i want to back to full 100% stock rom, o just need to flash it with odin and everything will be same like before? All apps will work like samsung health and pay? Thanks
Click to expand...
Click to collapse
No as I have heard. The knox fuse is a physical fuse which can never be reset so these apps will not work.
Has anyone been successful in running the new Open Beta build unencrypted? It's driving me absolutely nuts! It's a matter of time until whatever OnePlus changed makes it into the stable builds, I very much prefer to keep my phone unencrypted.
H4X0R46 said:
Has anyone been successful in running the new Open Beta build unencrypted? It's driving me absolutely nuts! It's a matter of time until whatever OnePlus changed makes it into the stable builds, I very much prefer to keep my phone unencrypted.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-decrypt-oneplus-7-pro-t3951131
aaryan45 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-decrypt-oneplus-7-pro-t3951131
Click to expand...
Click to collapse
This zip no longer works. I've always used it, but OnePlus changed something in the beta builds where this zip no longer works. I've spoken with the dev and he's stumped too.
H4X0R46 said:
This zip no longer works. I've always used it, but OnePlus changed something in the beta builds where this zip no longer works. I've spoken with the dev and he's stumped too.
Click to expand...
Click to collapse
u tried the latest version of the zip right?
aaryan45 said:
u tried the latest version of the zip right?
Click to expand...
Click to collapse
Yeah, on the open beta builds, it leads to an endless boot animation, never boots.
yes, same here.. hate to run encrypted.. OB 16 was the last that could be decrypted with this zip
raikkoni27 said:
yes, same here.. hate to run encrypted.. OB 16 was the last that could be decrypted with this zip
Click to expand...
Click to collapse
Yeah I miss it too! Very much so. I like the freedom to go between customs roms and never have to format my userdata! Hopefully soon someone will come up with a solution..... @topjohnwu Comes to mind. Any idea or expertise on the newer OnePlus devices not being unencryptable?
H4X0R46 said:
Yeah I miss it too! Very much so. I like the freedom to go between customs roms and never have to format my userdata! Hopefully soon someone will come up with a solution..... @topjohnwu Comes to mind. Any idea or expertise on the newer OnePlus devices not being unencryptable?
Click to expand...
Click to collapse
What are the steps to switch between custom roms by staying unencrypted and not formatting our internal storage .
insaneparnoid said:
What are the steps to switch between custom roms by staying unencrypted and not formatting our internal storage .
Click to expand...
Click to collapse
You download zackptg5's unencrypt zip and flash that before booting a new rom. He has an XDA thread here if you Google "no forceencrypt" and his own website, zackptg5.com. what you're looking for is his dm verity zip. Flash before booting a new rom if you're already unencrypted and you'll be fine. IF you're encrypted (just never messed with it at all), you will need to flash his zip and FORMAT (not wipe) your data. Clean slate. Lose everything.
EDIT: This currently doesn't work on beta builds of OOS.
H4X0R46 said:
You download zackptg5's unencrypt zip and flash that before booting a new rom. He has an XDA thread here if you Google "no forceencrypt" and his own website, zackptg5.com. what you're looking for is his dm verity zip. Flash before booting a new rom if you're already unencrypted and you'll be fine. IF you're encrypted (just never messed with it at all), you will need to flash his zip and FORMAT (not wipe) your data. Clean slate. Lose everything.
EDIT: This currently doesn't work on beta builds of OOS.
Click to expand...
Click to collapse
Keep Decrypt between Roms:
-Wipe Data only in twrp!!! (NEVER WIPE SYSTEM OR - VENDOR ON OP7P)
-Flash Rom
-Flash TWRP
-Reboot Recovery
-Flash any other zips you want like Gapps-Kernels- ex.....
-Flash No Verity Mod
-Flash Magisk
-Reboot System
is this right?
aaryan45 said:
Keep Decrypt between Roms:
-Wipe Data only in twrp!!! (NEVER WIPE SYSTEM OR - VENDOR ON OP7P)
-Flash Rom
-Flash TWRP
-Reboot Recovery
-Flash any other zips you want like Gapps-Kernels- ex.....
-Flash No Verity Mod
-Flash Magisk
-Reboot System
is this right?
Click to expand...
Click to collapse
Mostly, I'd flash Magisk before the verity zip. The rest is correct!
@H4X0R46 till now did you get any success in decrypt latest Beta 19?
Zhuang zhuang said:
@H4X0R46 till now did you get any success in decrypt latest Beta 19?
Click to expand...
Click to collapse
No unfortunately. I had a talk with zackptg5 and he's stumped too. I tried to get him a logcat on boot so he could see what's wrong, but my phone bootloops on beta's with his zip and will not let me take a logcat. He's as stumped as I am [emoji21]
H4X0R46 said:
No unfortunately. I had a talk with zackptg5 and he's stumped too. I tried to get him a logcat on boot so he could see what's wrong, but my phone bootloops on beta's with his zip and will not let me take a logcat. He's as stumped as I am [emoji21]
Click to expand...
Click to collapse
Oh, quite sad I hope he can find out the solution soon
H4X0R46 said:
Has anyone been successful in running the new Open Beta build unencrypted? It's driving me absolutely nuts! It's a matter of time until whatever OnePlus changed makes it into the stable builds, I very much prefer to keep my phone unencrypted.
Click to expand...
Click to collapse
Damn
I have been decrypted on the stable builds since a long time now. Was planning to switch to beta once OOS11 drops. But now it seems like I shouldn't.