Related
I am going to root my Nexus 5x very soon. I have some doubts, please help me to clarify those.
1. If I want to go with systemless root, I wouldn't have to flash modified boot.img. In that case will I be able to disable force encryption? If yes how?
2. If I have understood it correctly, in order to have disabled force encryption, I have to wipe user data after flashing SuperSU zip. Now in order to keep the encryption disabled, I have to wipe user data each time I flash a custom ROM or kernel?
I may seem noob in this question, but I am going through these encryption business for the very first time, so I thought its better to clarify rather than bricking my first Nexus [emoji6]
Thanks in advance.
Sent from my C6902 using Tapatalk
nondroid said:
I am going to root my Nexus 5x very soon. I have some doubts, please help me to clarify those.
1. If I want to go with systemless root, I wouldn't have to flash modified boot.img. In that case will I be able to disable force encryption? If yes how?
2. If I have understood it correctly, in order to have disabled force encryption, I have to wipe user data after flashing SuperSU zip. Now in order to keep the encryption disabled, I have to wipe user data each time I flash a custom ROM or kernel?
I may seem noob in this question, but I am going through these encryption business for the very first time, so I thought its better to clarify rather than bricking my first Nexus [emoji6]
Thanks in advance.
Sent from my C6902 using Tapatalk
Click to expand...
Click to collapse
You need to reformat userdata to remove the encryption. You do not need to continue to wipe after that for encryption purposes since it wont get re-encrypted unless forced encryption is enabled or you encrypt it. You will need to have a kernel/boot.img without forced encryption or it will re encrypt itself.
Systemless root has nothing to do with encryption and you could flash TWRP and root with SuperSU 2.6+ and still be encrypted.
A good starting place here
If I have got it right then I have to either flash boot.img or a kernel that disables force encryption in order to continue disabled force encryption.
Thanks for the clarification.
Sent from my C6902 using Tapatalk
Keithn said:
Systemless root has nothing to do with encryption and you could flash TWRP and root with SuperSU 2.6+ and still be encrypted.
Click to expand...
Click to collapse
Right and wrong at the same time...
Systemless root does disable force encryption: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The stock kernel will force encryption.
The stock kernel + systemless SuperSU will not force encryption.
Assuming you have all stock but TWRP installed, you would format data to remove encryption, then flash systemless root to stay unencrypted.
berndblb said:
Right and wrong at the same time...
Systemless root does disable force encryption: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The stock kernel will force encryption.
The stock kernel + systemless SuperSU will not force encryption.
Assuming you have all stock but TWRP installed, you would format data to remove encryption, then flash systemless root to stay unencrypted.
Click to expand...
Click to collapse
I see that the posted boot images don't have forced encryption along with other changes, but I didn't see anything saying it was necessary to use a kernel without forced encryption to have root. Does flashing 2.60+ also modify the kernel to disable force encryption (If enabled) when it does the necessary modifications for root? You can still be encrypted with systemless root so I figured that forced encryption would have no impact on the systemless root.
Edit- Looked at the script and it looks like it is supposed to. So whether it actually matters or not, it won't force encrypt after flashing SuperSU.
Update (May 20): Update to latest version 2.74-2
All versions after SuperSU 2.72 has force encrypt support built in. However it will still disable force encryption by default, you have to set flags manually.
I only modified the default value of the force encrypt flag in the flashing script, so no need to worry that this might break things
If your OCD forces you to use the official version, please look here for instructions to set the flag manually by yourself.
Hi, many people have their hands on the HTC 10, and you may found out that wiping data after rooted with SuperSU, your signal will be broken.
This is caused by the fact that by default, SuperSU's flashing script will change the data encryption flag from "forceencrypt" to "encryptable". If you wiped data after the flag is set to "encryptable", your data partition will be decrypted. In many times, decrypted data is good, but on the HTC 10, for some unknown reason the signal will break with data decrypted.
More info here:
[PSA][MUST SEE] New HTC Policy : Things You Should Know Before Unlocking Bootloader
This issue has caught more attention after an S-OFF method is available. You're required to have root and wipe data after gaining S-OFF. The developer of the S-OFF tool has created a tutorial for this particular problem, you can find it here:
[Guide] Root (Optionally s-off) and Keep your radio working
I slightly modified the SuperSU flashing script, so now it won't change the encryption flag.
This zip will remain useful until we find a way to decrypt our data partition with working signal.
Hi,
this works without problems, big tanks. Device is rooted now.
regards
starbase64
Big thanks. I wish I would have had this yesterday afternoon!
Now I just need to get a stock 1.21.617.3 image to start again with my US unlocked. If anyone has it, please let me know.
Is there a way to manually change the flag back to forceencrypt?
MNoisy said:
Big thanks. I wish I would have had this yesterday afternoon!
Now I just need to get a stock 1.21.617.3 image to start again with my US unlocked. If anyone has it, please let me know.
Is there a way to manually change the flag back to forceencrypt?
Click to expand...
Click to collapse
I have TWRP images for system_image and boot if you need them to fix broken signal as per @jcase. We're both 1.21.617.3
datafoo said:
I have TWRP images for system_image and boot if you need them to fix broken signal as per @jcase. We're both 1.21.617.3
Click to expand...
Click to collapse
Yes yes yes please! THANK YOU!
Where can I find them?
Nice buddy, will update the method used in my build, makes life a lot easier.
I had considered making similar modifications but you appear to have beaten me too it
topjohnwu said:
Hi, many people have their hands on the HTC 10, and you may found out that wiping data after rooted with SuperSU, your signal will be broken.
This is caused by the fact that by default, SuperSU's flashing script will change the data encryption flag from "forceencrypt" to "encryptable". If you wiped data after the flag is set to "encryptable", your data partition will be decrypted. In many times, decrypted data is good, but on the HTC 10, for some unknown reason the signal will break with data decrypted.
More info here:
[PSA][MUST SEE] New HTC Policy : Things You Should Know Before Unlocking Bootloader
This issue has caught more attention after an S-OFF method is available. You're required to have root and wipe data after gaining S-OFF. The developer of the S-OFF tool has created a tutorial for this particular problem, you can find it here:
[Guide] Root (Optionally s-off) and Keep your radio working
Here I come up with a more elegant solution. I slightly modified the SuperSU flashing script, so now it won't change the encryption flag, and also won't remove dm-verify.
NOTE: If your boot image is already modified, it will not reset the flag back to forceencrypt. You have to restore to the stock boot image, then flash this zip. The way I accomplished this is reverting a few modification from the previous ramdisk, so the ramdisk itself has to be stock.
Devs can include this zip into their rom, so users can wipe their whole data with your rom installed.
This zip will be useful until we find a way to decrypt our data partition with working signal.
Click to expand...
Click to collapse
I would NOT use this zip to root the HTC 10, you really need to remove verity, this is going to cause many many many issues, its going to softbrick a huge number of phones, anything from a lot of root apps, to restoring a twrp backup is going to trip dm-verity
SuperSU v2.72 has all of this built in via KEEPVERITY and KEEPFORCEENCRYPT flags. It's not publicly released yet but will be within a few days.
Chainfire said:
SuperSU v2.72 has all of this built in via KEEPVERITY and KEEPFORCEENCRYPT flags. It's not publicly released yet but will be within a few days.
Click to expand...
Click to collapse
Out of curiosity, where will we put those flags? /data/.supersu isn't an option, because /data is encrypted and unmountable, and /system/.supersu isn't an option if /system is read-only and we want to preserve dm-verity.
jcase said:
I would NOT use this zip to root the HTC 10, you really need to remove verity, this is going to cause many many many issues, its going to softbrick a huge number of phones, anything from a lot of root apps, to restoring a twrp backup is going to trip dm-verity
Click to expand...
Click to collapse
My system is modified, but everything is working fine. I'm using this without a problem so I shared it.
Is it because my device is S-OFF? If this is the case, then I'll remove the link. Thanks for the kind remind.
topjohnwu said:
My system is modified, but everything is working fine. I'm using this without a problem so I shared it.
Is it because my device is S-OFF? If this is the case, then I'll remove the link. Thanks for the kind remind.
Click to expand...
Click to collapse
I'd have to look at the zip and test to see why. It could be that your particular firmware isn't actually enforcing dm-verity (I believe google mandates this on 6.0+), that HTC disables enforcing when s-off or the zip isn't properly enforcing verity.
Best advice is not to enforce verity on system if you are rooted.
What should (and did for my phone) happen if you have dm-verity enabled on system and a modified system is the phone shouldn't successfully boot.
Captain_Throwback said:
Out of curiosity, where will we put those flags? /data/.supersu isn't an option, because /data is encrypted and unmountable, and /system/.supersu isn't an option if /system is read-only and we want to preserve dm-verity.
Click to expand...
Click to collapse
I've added /cache/.supersu as location specifically for those devices with a TWRP that can't read encrypted /data.
Still, you can echo to /data/.supersu even if /data isn't mounted and that'll still work. It just will not persist between boots.
Custom ROM devs should put it in /system/.supersu, though, or set the variable in shell and export that variable (important!) before running the SuperSU ZIP.
Chainfire said:
I've added /cache/.supersu as location specifically for those devices with a TWRP that can't read encrypted /data.
Still, you can echo to /data/.supersu even if /data isn't mounted and that'll still work. It just will not persist between boots.
Custom ROM devs should put it in /system/.supersu, though, or set the variable in shell and export that variable (important!) before running the SuperSU ZIP.
Click to expand...
Click to collapse
Will that cause complications for users who wipe cache often?
Sorry everyone, didn't though much about the dm_verity.
Re-uploaded one with dm_verity removed.
Everyone should re-flash this zip if you've used the old one, thanks a lot.
@LeeDroid, could you please test if this works on your rom?
topjohnwu said:
Sorry everyone, didn't though much about the dm_verity.
Re-uploaded one with dm_verity removed.
Everyone should re-flash this zip if you've used the old one, thanks a lot.
@LeeDroid, could you please test if this works on your rom?
Click to expand...
Click to collapse
Will have a bash tonight mate
topjohnwu said:
Sorry everyone, didn't though much about the dm_verity.
Re-uploaded one with dm_verity removed.
Everyone should re-flash this zip if you've used the old one, thanks a lot.
@LeeDroid, could you please test if this works on your rom?
Click to expand...
Click to collapse
still no go on boot
LeeDroid said:
still no go on boot
Click to expand...
Click to collapse
Yeah... Just tested myself and it won't boot.
It's weird though, it can boot on my modified system
I might need more investigation, or just wait for Chainfire to release the new update.
Is it OK to use SYSTEMLESS with your current build?
Thanks
ah, perhaps encountered a blarf
you wanna stick with blarp ... he's much nicer
topjohnwu said:
Yeah... Just tested myself and it won't boot.
It's weird though, it can boot on my modified system
I might need more investigation, or just wait for Chainfire to release the new update.
Click to expand...
Click to collapse
Ahh, I knew why.
I cannot separate the forceencrypt flag patch and verify flag by modifying the script.
Had to wait for Chainfire to release new version, or we have to manually modify the boot image.
You miss Full-Disk Encryption on your OnePlus 5?
Here's a fix.
Flash the zip below after flashing your kernel (which means after every ROM update as well!).
The very first time you flash this mod, you'll have to format userdata, or bad things will happen.
First-time Install instructions:
Flash your ROM
Flash the attached Zip
(Optional) Flash Magisk
Format userdata. In TWRP, go to Wipe -> Format Data
Reboot
You are now unencrypted.
To encrypt in Full-Disk Encryption mode, go to Settings -> Security -> Encrypt
You're now in FDE mode!
Profit!
And don't forget to reflash this module every time you flash a new boot image.
XDA:DevDB Information
Full-Disk-Encryption Enabler for OP5, Device Specific App for the OnePlus 5
Contributors
Fif_
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-09-12
Created 2017-09-13
Last Updated 2017-09-13
Here's the Zip.
@Fif_ should i erase "internal storage" or just data partition!Thank You!
Sent from my ONEPLUS A5000 using Tapatalk
dragoi90 said:
@Fif_ should i erase "internal storage" or just data partition!Thank You!
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
You need to format the data partition. That all also nuke the internal storage by the way, so your phone will be back to factory reset.
Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?
BlueEffect said:
Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?
Click to expand...
Click to collapse
No this is for people that want to run FDE rather than FBE. Eg. to have Xposed working.
Fif_ said:
No this is for people that want to run FDE rather than FBE. Eg. to have Xposed working.
Click to expand...
Click to collapse
You can have Xposed working with FBE by just soft rebooting using Xposed installer.
alukarulz said:
You can have Xposed working with FBE by just soft rebooting using Xposed installer.
Click to expand...
Click to collapse
You are right, but I don't want to have to do that, I want Xposed on the first boot...
BlueEffect said:
Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?
Click to expand...
Click to collapse
If you want the go under settings and security and encrypt your phone
BlueEffect said:
Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?
Click to expand...
Click to collapse
ndarkside93 said:
If you want the go under settings and security and encrypt your phone
Click to expand...
Click to collapse
This is used to change encryption type from FBE to FDE. You can also use it to run decrypted.
Fif_ said:
This is used to change encryption type from FBE to FDE. You can also use it to run decrypted.
Click to expand...
Click to collapse
I know.I was just answering his question.
alukarulz said:
You can have Xposed working with FBE by just soft rebooting using Xposed installer.
Click to expand...
Click to collapse
Fif_ said:
You are right, but I don't want to have to do that, I want Xposed on the first boot...
Click to expand...
Click to collapse
Ahh... I see... I am getting tired of having to soft reboot after each reboot. It looks like this FDE mod/hack would resolve this problem, right? Are there any real drawbacks to using FDE over FBE? What about if/when I decide to switch to another ROM?
sjamie said:
Ahh... I see... I am getting tired of having to soft reboot after each reboot. It looks like this FDE mod/hack would resolve this problem, right? Are there any real drawbacks to using FDE over FBE? What about if/when I decide to switch to another ROM?
Click to expand...
Click to collapse
I downside is you have to flash the fde flash file Everytime you flash an update. Plus the first time you need to erase data.
alukarulz said:
I downside is you have to flash the fde flash file Everytime you flash an update. Plus the first time you need to erase data.
Click to expand...
Click to collapse
Would I have to also erase my data when switching to a different ROM?
alukarulz said:
I downside is you have to flash the fde flash file Everytime you flash an update. Plus the first time you need to erase data.
Click to expand...
Click to collapse
I'm already flashing Magisk after every ROM update, so it's just one more zip to flash.
Actually stock OOS doesn't seem to care, you only have to flash this mod once, before you convert to FDE.
OOS 4.5.10 will happily boot in FDE even without the mod, provided that the data partition is already FDE.
That's not the case for every ROM.
Another downside is that no unattended boots are possible. You have to type in the FDE password to boot into Android.
sjamie said:
Would I have to also erase my data when switching to a different ROM?
Click to expand...
Click to collapse
No. Only once.
Fif_ said:
I'm already flashing Magisk after every ROM update, so it's just one more zip to flash.
Actually stock OOS doesn't seem to care, you only have to flash this mod once, before you convert to FDE.
OOS 4.5.10 will happily boot in FDE even without the mod, provided that the data partition is already FDE.
That's not the case for every ROM.
Another downside is that no unattended boots are possible. You have to type in the FDE password to boot into Android.
Click to expand...
Click to collapse
Thanks! I'll definitely give this mod a try if I truly get tired of having to soft boot after each normal boot. Is there a tasker profile or some other way to automate that?
sjamie said:
Thanks! I'll definitely give this mod a try if I truly get tired of having to soft boot after each normal boot. Is there a tasker profile or some other way to automate that?
Click to expand...
Click to collapse
Yes you can, run in a root shell:
Code:
setsid sh -c 'stop; start'
But I always run into strange things in Xposed if it's not running at boot, so YMMV.
Be careful not to just restart the system UI but the full zygote stack.
Fif_ said:
Yes you can, run in a root shell:
Click to expand...
Click to collapse
Thank you. What exactly is that command doing? Do I have to run it after each boot?
sjamie said:
Thank you. What exactly is that command doing? Do I have to run it after each boot?
Click to expand...
Click to collapse
"stop" stops all Android services.
"start" starts them again.
The "setsid sh" wrapper is there so that the commands will survive the Android shutdown and run to completion even if the parent process calling root is killed (which will happen as soon as "stop" runs).
Yes you'd have to run this after every boot.
But be careful that the second time Android starts after a boot is not detected as a second boot event or you'll end up in a restart loop.
I was with Resurrection rom and I took a nandroid backup (as I am doing always when I want to flash a new rom). I flashed the dirty unicorn without knowing that I need to be decrypted (I am encrypted). After being in boot screen for long time I decided to restore nanddroid backup having in otg flash drive. Everything was ok but after some time I had force close to android system, nova launcher and other things I don't remember right now. I decided to flash a new rom (omni) and from that moment and then I can't adjust password for fingerprint. I am aware about /data/system lockscreen.db and other possible files but i had only lockscreen.db. I was removing (I did this procedure for more that 10 times) but when i restarted my phone and set up a new password, after that asked me again to retype the password and every time was incorrect.
I really do not know what else to do. I made a search for long time but I didn't find something else except the guide about data/system I already mentioned and didn't help me.
Can anyone help me because i am right now without any password?
ostvarivanje said:
I was with Resurrection rom and I took a nandroid backup (as I am doing always when I want to flash a new rom). I flashed the dirty unicorn without knowing that I need to be decrypted (I am encrypted). After being in boot screen for long time I decided to restore nanddroid backup having in otg flash drive. Everything was ok but after some time I had force close to android system, nova launcher and other things I don't remember right now. I decided to flash a new rom (omni) and from that moment and then I can't adjust password for fingerprint. I am aware about /data/system lockscreen.db and other possible files but i had only lockscreen.db. I was removing (I did this procedure for more that 10 times) but when i restarted my phone and set up a new password, after that asked me again to retype the password and every time was incorrect.
I really do not know what else to do. I made a search for long time but I didn't find something else except the guide about data/system I already mentioned and didn't help me.
Can anyone help me because i am right now without any password?
Click to expand...
Click to collapse
Back up your app data with swift backup or titanium and wipe every partition except internal. This is assuming you can still get into the rom. I can't tell if you're stuck in TWRP or the rom. If you're stuck in the rom I would wipe all partitions except internal and restore your RR backup then use titanium/swift to back up all your user data then do a clean flash. You can only use encrypted roms from here on out unless you do a format.
preference said:
Back up your app data with swift backup or titanium and wipe every partition except internal. This is assuming you can still get into the rom. I can't tell if you're stuck in TWRP or the rom. If you're stuck in the rom I would wipe all partitions except internal and restore your RR backup then use titanium/swift to back up all your user data then do a clean flash. You can only use encrypted roms from here on out unless you do a format.
Click to expand...
Click to collapse
Thank you very much for your answer and wiping everything else except internal twrp notify me that there is no os. Actually i found an nandroid backup in my computer from 17th of March (lineage) and i am trying to restore it right now. So... waiting for the results.
Before that i tried to flash again omni rom and in the initial setup i put pattern instead of pin for fingerprint configuration and then it went to the next step without let me configure the fingerprint. When I tried in settings to adjust a lockscreen password or pin or pattern the settings forced close
ostvarivanje said:
Thank you very much for your answer and wiping everything else except internal twrp notify me that there is no os. Actually i found an nandroid backup in my computer from 17th of March (lineage) and i am trying to restore it right now. So... waiting for the results.
Before that i tried to flash again omni rom and in the initial setup i put pattern instead of pin for fingerprint configuration and then it went to the next step without let me configure the fingerprint. When I tried in settings to adjust a lockscreen password or pin or pattern the settings forced close
Click to expand...
Click to collapse
When I told you to wipe it was because you had a backup of RR. Do you still have it? Lineage should restore fine if you did the typical default Nandroid backup
preference said:
When I told you to wipe it was because you had a backup of RR. Do you still have it? Lineage should restore fine if you did the typical default Nandroid backup
Click to expand...
Click to collapse
I was wrong, the nandroid backup i had was from omni. I finished restoring but again the same thing. I really don't know what to do and in /data/system there is only lockscreen.db file and when i delete it I have the same thing again.
ostvarivanje said:
I was wrong, the nandroid backup i had was from omni. I finished restoring but again the same thing. I really don't know what to do and in /data/system there is only lockscreen.db file and when i delete it I have the same thing again.
Click to expand...
Click to collapse
Which twrp are you using? Are you on the latest from codeworkx
preference said:
Which twrp are you using? Are you on the latest from codeworkx
Click to expand...
Click to collapse
Yes, today I put the latest from codeworkx (I think from 9th of March). I even tried official twrp without some changes about my problem
ostvarivanje said:
Yes, today I put the latest from codeworkx (I think from 9th of March). I even tried official twrp without some changes about my problem
Click to expand...
Click to collapse
It sounds like you're locked out permanently. The best bet is restore to RR since that was your last working Nandroid. I have a feeling the lock code will work if you restore to that build.
Did restoring to lineage hell at all?
preference said:
It sounds like you're locked out permanently. The best bet is restore to RR since that was your last working Nandroid. I have a feeling the lock code will work if you restore to that build.
Did restoring to lineage hell at all?
Click to expand...
Click to collapse
No, I was wrong and i didn't have linage but omni. Even with RR I couldn't to adjust a password. Now I don't have it anymore.
Is it possible I am the only one with this problem?
Because I have as a secondary device OnePlus 3T I never had a problem like this.
So what's next? Using my phone without lockscreen or there is something to do? Is it a good idea to flash an Oxygene (or oxygene based rom) or there is no any difference?
ostvarivanje said:
No, I was wrong and i didn't have linage but omni. Even with RR I couldn't to adjust a password. Now I don't have it anymore.
Is it possible I am the only one with this problem?
Because I have as a secondary device OnePlus 3T I never had a problem like this.
So what's next? Using my phone without lockscreen or there is something to do? Is it a good idea to flash an Oxygene (or oxygene based rom) or there is no any difference?
Click to expand...
Click to collapse
You dirty flashed multiple time and tried to hop onto a build that's decrypted by default. You kept trying to save your data and unfortunately you ended up locking yourself out. I'm personally decrypted but have read enough telegram and xda posts to know that the latest codeworkx's recoveries can decrypt the pin. So you basically put yourself into a corner with your actions. Unfortunately you didn't back up your data with titanium or swift. I think you're going to have to fully clean flash (wipe every partition except internal), install a rom and have Google restore your app data. I'm sorry to say this. You can keep trying to avoid it but I think it's your best solution. Don't flash a decrypted rom then try to restore backups without wiping the partitions first. You'll have to start from scratch imo. Maybe someone more experienced can help you.
preference said:
You dirty flashed multiple time and tried to hop onto a build that's decrypted by default. You kept trying to save your data and unfortunately you ended up locking yourself out. I'm personally decrypted but have read enough telegram and xda posts to know that the latest codeworkx's recoveries can decrypt the pin. So you basically put yourself into a corner with your actions. Unfortunately you didn't back up your data with titanium or swift. I think you're going to have to fully clean flash (wipe every partition except internal), install a rom and have Google restore your app data. I'm sorry to say this. You can keep trying to avoid it but I think it's your best solution. Don't flash a decrypted rom then try to restore backups without wiping the partitions first. You'll have to start from scratch imo. Maybe someone more experienced can help you.
Click to expand...
Click to collapse
Let's make things clear. I never flash dirty and always doing wipe everything except internal. Of course i have backup with titanium of all my apps, I don't know how you concluded that I don't have it (maybe it's my fault because english is not my native language). You suggested me to make a fully clean flash (ok, except internal), but this is what i am doing always.
Actually I don't avoid something and i am willing to do everything if i have the result to be able to lock my phone.
ostvarivanje said:
Let's make things clear. I never flash dirty and always doing wipe everything except internal. Of course i have backup with titanium of all my apps, I don't know how you concluded that I don't have it (maybe it's my fault because english is not my native language). You suggested me to make a fully clean flash (ok, except internal), but this is what i am doing always.
Actually I don't avoid something and i am willing to do everything if i have the result to be able to lock my phone.
Click to expand...
Click to collapse
Then I don't understand how the issue is still happening. If you're restoring and doing clean flashed your pin will work. I know this sounds like an attack but it isn't. I'm saying start fresh, and since you have titanium that will only take ten minutes of your time to restore. I'm not trying to say you're stupid or not careful, I'm saying there's likely no solution so why not start over and just use a back up of your app data through titanium? Based on the situation so far, you're making it sound like the pin is essential, so I made assumptions that you didn't have a backup. The solution is to start over. I apologize, your English is very good by the way.
preference said:
Then I don't understand how the issue is still happening. If you're restoring and doing clean flashed your pin will work. I know this sounds like an attack but it isn't. I'm saying start fresh, and since you have titanium that will only take ten minutes of your time to restore. I'm not trying to say you're stupid or not careful, I'm saying there's likely no solution so why not start over and just use a back up of your app data through titanium? Based on the situation so far, you're making it sound like the pin is essential, so I made assumptions that you didn't have a backup. The solution is to start over. I apologize, your English is very good by the way.
Click to expand...
Click to collapse
I am flashing roms at least for the 7-8 years (from Samsung Nexus S when it was my first Android phone and earlier from Windows 6). I am always doing a clean flash and always taking titanium backup and nandroid. This is what I did also today. Already I flashed 3-4 roms and restored 2 or 3 times from nandroid with the same result, I can't adjust pin no matter if I am doing that in initial setup for fingerprint or in settings.
About pin I faced the same thing before a month when I tried to flash omni rom. And then I found a guide about not setting up a pin in initial setup but to finish the initial setup and to restart the phone to twrp and with the file manager to remove files related to lockscreen from /data/system. I followed this guide and everything was great, after restarting my phone I could set up a new pin. But today is a nightmare. I am trying to resolve this problem from last night!
ostvarivanje said:
I am flashing roms at least for the 7-8 years (from Samsung Nexus S when it was my first Android phone and earlier from Windows 6). I am always doing a clean flash and always taking titanium backup and nandroid. This is what I did also today. Already I flashed 3-4 roms and restored 2 or 3 times from nandroid with the same result, I can't adjust pin no matter if I am doing that in initial setup for fingerprint or in settings.
About pin I faced the same thing before a month when I tried to flash omni rom. And then I found a guide about not setting up a pin in initial setup but to finish the initial setup and to restart the phone to twrp and with the file manager to remove files related to lockscreen from /data/system. I followed this guide and everything was great, after restarting my phone I could set up a new pin. But today is a nightmare. I am trying to resolve this problem from last night!
Click to expand...
Click to collapse
Yeah man the only choice I see is a full format or wipe all partitions. I hate saying that but if your phone is stuck at the pin entry on every rom there is a bug occurring that might need to be completely wet to default, which a format will do. Let me know if someone is more helpful and you figure it out, I've never heard of a pin entry issue across multiple roms.
preference said:
Yeah man the only choice I see is a full format or wipe all partitions. I hate saying that but if your phone is stuck at the pin entry on every rom there is a bug occurring that might need to be completely wet to default, which a format will do. Let me know if someone is more helpful and you figure it out, I've never heard of a pin entry issue across multiple roms.
Click to expand...
Click to collapse
So we arrived in the end, i mean i need to format internal storage, right? So I will firstly transfer my files to my computer and then i will do that. But is it sure that will resolve the problem. And one more thing. Do i need to make my phone decrypted now when i will remove everhyting from my phone? Some roms have compatibility with encrypted and some others with decrypted. I think somewhere that you can flash to the decrypted phone a rom for encrypted phones with flashing something but i am not sure. For now i thing that mostly rom for oneplus 5t are for encrypted phones, right?
ostvarivanje said:
So we arrived in the end, i mean i need to format internal storage, right? So I will firstly transfer my files to my computer and then i will do that. But is it sure that will resolve the problem. And one more thing. Do i need to make my phone decrypted now when i will remove everhyting from my phone? Some roms have compatibility with encrypted and some others with decrypted. I think somewhere that you can flash to the decrypted phone a rom for encrypted phones with flashing something but i am not sure. For now i thing that mostly rom for oneplus 5t are for encrypted phones, right?
Click to expand...
Click to collapse
To stay decrypted flash no verity v2 zip after flashing rom and gapps. Magisk enforces the no encrypt along with the no verity zip.
When you format your phone you will be fully decrypted. If you want to stay decrypted then flash rom, gapps, no verity then boot. Configure your ROM then reboot to recovery after first fill boot. Flash magisk, it should force encrypt.
If you're paranoid about losing decryption then do what u do. - flash no verity after everything. It won't break anything.
I attached the one that works so you don't have to worry about tracking it down. Again you can flash this after flashing any file.
preference said:
To stay decrypted flash no verity v2 zip after flashing rom and gapps. Magisk enforces the no encrypt along with the no verity zip.
When you format your phone you will be fully decrypted. If you want to stay decrypted then flash rom, gapps, no verity then boot. Configure your ROM then reboot to recovery after first fill boot. Flash magisk, it should force encrypt.
If you're paranoid about losing decryption then do what u do. - flash no verity after everything. It won't break anything.
I attached the one that works so you don't have to worry about tracking it down. Again you can flash this after flashing any file.
Click to expand...
Click to collapse
Thank you very much for the instructions. Actually I am confused if I need to stay decrypted or not. That means, if i have a rom for encrypted phones and i want to flash a new one for decrypted the only thing i need to do is to flash in the end the no verity zip? In advance, I need to do the same when i restart to twrp to flash the magisk then again no verity?
Is your file you posted correct? Because its filename is op5 and not op5t, except if it's the same.
ostvarivanje said:
Thank you very much for the instructions. Actually I am confused if I need to stay decrypted or not. That means, if i have a rom for encrypted phones and i want to flash a new one for decrypted the only thing i need to do is to flash in the end the no verity zip? In advance, I need to do the same when i restart to twrp to flash the magisk then again no verity?
Is your file you posted correct? Because its filename is op5 and not op5t, except if it's the same.
Click to expand...
Click to collapse
It's the same, works on both devices. There isn't a special one for the 5t.
If you want to try all roms, stay decrypted. All roms appear to work on decrypted phones.
If you want to stay encrypted, then you can only use roms that support force encryption. So you wouldn't be able to flash a rom like DU.
I personally stay decrypted because it's easier to back up and restore roms. It's all a personal choice. If you go encrypted you just might miss out on a couple roms. Most support force encrypt.
Just remember:
Decrypt and first boot = flash rom, gapps, no verity on first flash. Then boot/start the rom and configure rom. Reboot to recovery after finishing first boot and install magisk or superSU. Optionally flash no verity but it's not needed.
Decrypt and any rom update flash = flash rom, no verity, flash gapps if your ROM requires it (ask first, only a few roms like liquid remix require this)
Encrypted and first boot = flash rom, gapps, boot into rom, reboot back into recovery, flash magisk/superSU
Encrypted and update = flash updated rom file, optionally flash gapps if your ROM requires it (again ask in the thread or on telegram for this info)
preference said:
It's the same, works on both devices. There isn't a special one for the 5t.
If you want to try all roms, stay decrypted. All roms appear to work on decrypted phones.
If you want to stay encrypted, then you can only use roms that support force encryption. So you wouldn't be able to flash a rom like DU.
I personally stay decrypted because it's easier to back up and restore roms. It's all a personal choice. If you go encrypted you just might miss out on a couple roms. Most support force encrypt.
Just remember:
Decrypt and first boot = flash rom, gapps, no verity on first flash. Then boot/start the rom and configure rom. Reboot to recovery after finishing first boot and install magisk or superSU. Optionally flash no verity but it's not needed.
Decrypt and any rom update flash = flash rom, no verity, flash gapps if your ROM requires it (ask first, only a few roms like liquid remix require this)
Encrypted and first boot = flash rom, gapps, boot into rom, reboot back into recovery, flash magisk/superSU
Encrypted and update = flash updated rom file, optionally flash gapps if your ROM requires it (again ask in the thread or on telegram for this info)
Click to expand...
Click to collapse
I just finished with the backup of my files. So if i want to flash a rom like du i need in the end to flash no verity but if it's for encrypted i don't need it. So with this way i can flash every rom i can find.
One more thing, wiping everything (every partition) getting the phone decrypted? I mean that i don't need to do something else?
Your help is more than important for me. I really appreciate it and thank you for that!
ostvarivanje said:
I just finished with the backup of my files. So if i want to flash a rom like du i need in the end to flash no verity but if it's for encrypted i don't need it. So with this way i can flash every rom i can find.
One more thing, wiping everything (every partition) getting the phone decrypted? I mean that i don't need to do something else?
Your help is more than important for me. I really appreciate it and thank you for that!
Click to expand...
Click to collapse
You can't use normal wipe, go to wipe then choose the option on the right (I think it says wipe device) and then it will tell you to type "yes". If you type yes then hit enter it will format the phone. That's a true format and it will decrypt your device. You can't just wipe all partitions because it's not a complete format.
So if you typed "yes" in TWRP you have a formatted phone. It will stay decrypted until you flash an encrypted rom.
So if you flash DU, you don't need no verity because the rom is decrypted. If you flash RR 6.0 then your phone will encrypt UNLESS you flash no verity. So the file I gave you is a way to stop encryption on encrypted roms.
You flash RR 6.0, gapps, no verity = RR but no encryption.
You flash DU, gapps = decrypted rom so you don't need no verity zip
Most roms are encrypted, so you flash rom, gapps, no verity to stay decrypted. The zip I gave you should be flashed after flashing rom and gapps on every encrypted rom if you want to stay decrypted.
Hello !!!
Gsi Rom for realme Q
This is the best version for realme Q.Works well, but fingerprint error, hope someone can fix it
Installation Instructions:
1. Download the GSI from the links above, and uncompress it.
2. Wipe Data, Dalvik, and Cache,system . No wipe vendor
3. Remove Magisk if it was previously installed, by using its uninstaller script. Magisk files are stored in the kernel image, and in the /data/adb folder, which are left untouched when wiping data and flashing the GSI. Another option is to flash your stock rom and manually delete the content of the /data/adb folder.
4. Flash the GSI to system partition (AB devices : flashing a vbmeta.img file for your device may also be required).
5. Boot and perform a factory reset.
6. (Optional) Reboot and flash Magisk, and maybe additional files.
7. Reboot and Enjoy.
If you want to update rom, you can also always try to dirty flash, i.e. wipe Dalvik and Cache (not Data) and flash System image. But if you experience a strange behavior, a clean flash may be required
Note : if flash Gapps you need resize system in teamwin,then flash gapps
Which vendor to use?
1. Always use your actual device's vendor
2. Always use OEM unmodified vendor, not some custom vendor
3. This includes boot.img. boot.img and vendor MUST BE the same version.
Rom download :
Link download android 9 rr7.0 : https://drive.google.com/file/d/1--pQfJlNR2V9OEFeLCoT--tmftT8OFGZ/view?usp=drivesdk
link download android 10 AOSP : Download
Link download Rom Msm 9 : Download
How to fix bug any rom:
Link download fix lag,fix bt audio,fix mtp,fix power rom havoc,magisk stable for android Q and more ..
Folder click here
Great, found your thread on telegram, this is what I need, I am fed up with Color OS
It's not half bad but there are two major problems with the ROM. First it seems it can't read exfat 128 GB as card which is a shame for I won't format it to inferior fat32 to lose all my stuff. Second, whenever I set a screen lock, no matter what kind of it'll tell me that I entered incorrect code. Means I cannot lock the screen with any kind of security measure. I could solve the external as card issue by flashing lineage os boot.img but I couldn't the screen lock issue. Aside these I have no problem. Testing other gsi ROMs.
Edit.: No. Screen lock isn't rom but vendor issue. I accidentally wiped vendor partition before flashing the image.
greenys' said:
It's not half bad but there are two major problems with the ROM. First it seems it can't read exfat 128 GB as card which is a shame for I won't format it to inferior fat32 to lose all my stuff. Second, whenever I set a screen lock, no matter what kind of it'll tell me that I entered incorrect code. Means I cannot lock the screen with any kind of security measure. I could solve the external as card issue by flashing lineage os boot.img but I couldn't the screen lock issue. Aside these I have no problem. Testing other gsi ROMs.
Edit.: No. Screen lock isn't rom but vendor issue. I accidentally wiped vendor partikon before flashing the image.
Click to expand...
Click to collapse
I will note that people do not wipe vendor
29y6145 said:
I will note that people do not wipe vendor
Click to expand...
Click to collapse
I just noticed that I didn't wipe vendor either. It's not even in the wipeable section if you try advanced wipe. For some reason if I go from one gsi to another lock screen password/pattern will not work. I have to flash stock zip first, then wipe data, system, cache, davlik and at last flash gsi image. Between going from one gsi to another you have to do this in order to keep lock screen password function. Right now I'm struggling with Magisk Safetynet. Any good method to bypass?
greenys' said:
I just noticed that I didn't wipe vendor either. It's not even in the wipeable section if you try advanced wipe. For some reason if I go from one gsi to another lock screen password/pattern will not work. I have to flash stock zip first, then wipe data, system, cache, davlik and at last flash gsi image. Between going from one gsi to another you have to do this in order to keep lock screen password function. Right now I'm struggling with Magisk Safetynet. Any good method to bypass?
Click to expand...
Click to collapse
I realized that. Today I tested android Q on realme Q, it worked. I cannot set the screen password, the system only allows swiping. I am looking into this problem.
29y6145 said:
I realized that. Today I tested android Q on realme Q, it worked. I cannot set the screen password, the system only allows swiping. I am looking into this problem.
Click to expand...
Click to collapse
Flashing stock vendor img solved the issue on my device. Although I tried AOSP Pie not Q.
update android 10 and permissiver for andoid 10
Update Installation Instructions .
Hi, awesome thread, congrats to you @29y6145.
I see now that you added two more ROMs, the AOSP10 and the MSM-Xtended 9. Any of them are more stable than the others? I was looking for stability in the entire OS and Camera that any other thing.
By the way, Why you remove the links to TWRP and Permissiver_v5?
I installed the Resurrection Remix 7.0.2 and see that doesn't have Magisk by default. I should install Magisk via your TWRP built-in Magisk installer or from the official Magisk website?
Tmv_Josue said:
Hi, awesome thread, congrats to you @29y6145.
I see now that you added two more ROMs, the AOSP10 and the MSM-Xtended 9. Any of them are more stable than the others? I was looking for stability in the entire OS and Camera that any other thing.
By the way, Why you remove the links to TWRP and Permissiver_v5?
I installed the Resurrection Remix 7.0.2 and see that doesn't have Magisk by default. I should install Magisk via your TWRP built-in Magisk installer or from the official Magisk website?
Click to expand...
Click to collapse
I am editing some posts, and will re upload important files.
Both of the 2 Roms you speak are fine. I will give you a tutorial about the Havoc rom.
I have upload permissiver #1
29y6145 said:
I am editing some posts, and will re upload important files.
Both of the 2 Roms you speak are fine. I will give you a tutorial about the Havoc rom.
I have upload permissiver #1
Click to expand...
Click to collapse
Did you manage to pass safetynet with gsi?
greenys' said:
Did you manage to pass safetynet with gsi?
Click to expand...
Click to collapse
You try
@29y6145
This Petnoire's_SafetyNet_Spoofer_magisk.zip should be used instead of the Realme5ProColorOSMagiskFixBETA.zip?
Or both should be flashed?
Tmv_Josue said:
@29y6145
This Petnoire's_SafetyNet_Spoofer_magisk.zip should be used instead of the Realme5ProColorOSMagiskFixBETA.zip?
Or both should be flashed?
Click to expand...
Click to collapse
You use Petnoire's_SafetyNet_Spoofer_magisk or module safeynet in magisk .
Im use module safety in magisk It works perfectly.
@29y6145
What is exactly the name of that Magisk's Safety module that you mentioned?
I searched in Magisk and only found hackintosh5's SafetyPatch and Didgeridoohan's MagiskHide Props Config.
Is any of them?
My realme Q device has unlocked BL and installed TWRP, while using lineage oS 16 Android P, how to refresh this Android Q GSI image? Is it refreshed directly with TWRP REC?
@TrancyMeng.
*Any ROM in IMG format should be flashed trought Fatboot, but you need to wipe the other installation first, in adb run this to enter in TWRP:
adb reboot recovery
Then in TWRP:
*Wipe > System, Data, Cache, Dalvik
*Reboot > BootLoader (Fastboot)
Then in Fastboot/Bootloader run this command:
fastboot flash system romNAME.img
Reboot to recovery/TWRP and flash:
Permissiver_v5.zip
After refresh the Andrews Q GSI ROM, why the speaker will have a current sound, and call and play the local media file will not. How to troubleshise the patch to do it? Can you trouble with you to provide a patch for the repair sound?
THREAD CLOSED!
@29y6145 Please consult the inbox of your private messages.