Related
Disclaimer: I have done these steps multiple times and haven't come across any issues
Read All Step carefully. Any issues or damage to your phone that occurs while doing this I am not responsible.
If TWRP asks you for Password to decrypt data & maybe you have important data in you device, So you can't format data.
Follow these steps:
1. Download the OxygenOS full zip file (tested on 4.0.1 & above)
2. Open TWRP.
3. When It asks for password, cancel it.
4. Click "Read Only" button.
5. Install the OxygenOS zip file.
6. Reboot.
7. The OS may misbehave.
8. Open TWRP again. & Boom! No encryption password.
9. Connect to PC and copy the Important data.
10. Flash Any ROM now.
Thanks!
Recently I had to type in the password but I didn't know that it is possible to bypass it with this...
svandasek said:
Thanks!
Recently I had to type in the password but I didn't know that it is possible to bypass it with this...
Click to expand...
Click to collapse
Glad it helped you
ah.... if i only knew :crying:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
TWRP Encryption ByPass
maddler said:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
Click to expand...
Click to collapse
Agree .... that seems like a gaping security vulnerability. :-/
maddler said:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
Click to expand...
Click to collapse
There's no need to be concerned (about this, specifically).
tk8lm6 said:
Agree .... that seems like a gaping security vulnerability. :-/
Click to expand...
Click to collapse
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
smaeul said:
There's no need to be concerned (about this, specifically).
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
Click to expand...
Click to collapse
No arguing that previous versions were less secure. But, still, as long as there's a way to bypass encryption that's a security failure.
Encrypted data shouldn't be made available unless proper key(s) or passwords have been provided.
If that's the way that's meant to work, then that's flawed by design.
smaeul said:
There's no need to be concerned (about this, specifically).
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
Click to expand...
Click to collapse
I've tried many times. OOS replaces TWRP only on CLEAN Instal for me.
hey guys, i tried to flash oos 5.0 zip, before that i was on another rom. wiped data, system, cache and flashed oos 5.0. and now internal storage is encrypted. how do i flash the zip in twrp now?
manchitro said:
hey guys, i tried to flash oos 5.0 zip, before that i was on another rom. wiped data, system, cache and flashed oos 5.0. and now internal storage is encrypted. how do i flash the zip in twrp now?
Click to expand...
Click to collapse
Just flash it.
Wait, are you saying by just installing a zip, the encrypion hardware pass is gone? WTF.. Is such "hack" available on other devices? Xiaomi redmi(s) for example?
hey i am not able to see any of my files or the zip itself within? is there anything to resolve that?
i can boot into os but for whatever reason cant get to twrp. i have the backup .imgs on my pc now too can i sideload a restore?
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
SourPower said:
hey i am not able to see any of my files or the zip itself within? is there anything to resolve that?
i can boot into os but for whatever reason cant get to twrp. i have the backup .imgs on my pc now too can i sideload a restore?
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
Click to expand...
Click to collapse
Yeah same issue here, as soon as I go in twrp and can't type the password, I can't access my files which is expected behavior, so I don't understand how you can access the file to flash from twrp.
Can someone detail please?
---------- Post added at 07:06 PM ---------- Previous post was at 06:40 PM ----------
Actually I just found a way out to get to previous twrp version, and all is back to normal
From your running ROM, you can download the application twrp (root needed oc)
Then you can use it to flash recovery.
I always keep former version file so I could revert to bluspark twrp that was working before. All worked as expected!
Still not solving the encryption password issue when flashing new recent twrp..
Android 10 Encryption / Security Issue - ADB Encryption Bypass?
rahulrs0029 said:
Disclaimer: I have done these steps multiple times and haven't come across any issues
Read All Step carefully. Any issues or damage to your phone that occurs while doing this I am not responsible.
If TWRP asks you for Password to decrypt data & maybe you have important data in you device, So you can't format data.
Follow these steps:
1. Download the OxygenOS full zip file (tested on 4.0.1 & above)
2. Open TWRP.
3. When It asks for password, cancel it.
4. Click "Read Only" button.
5. Install the OxygenOS zip file.
6. Reboot.
7. The OS may misbehave.
8. Open TWRP again. & Boom! No encryption password.
9. Connect to PC and copy the Important data.
10. Flash Any ROM now.
Click to expand...
Click to collapse
Does this only affect the TWRP -encryption, because when you set your lockscreen password (for the auto-encrypted userdata partition in Android 10, for example) the data can't be decrypted without this password..?
I have discovered another security issue however on a rooted device:
On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!
This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!
Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?
Is this issue related to Magisk? And can it be fixed?
monicaONxda said:
Does this only affect the TWRP -encryption, because when you set your lockscreen password (for the auto-encrypted userdata partition in Android 10, for example) the data can't be decrypted without this password..?
I have discovered another security issue however on a rooted device:
On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!
This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!
Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?
Is this issue related to Magisk? And can it be fixed?
Click to expand...
Click to collapse
Anyone with thoughts on this...?
monicaONxda said:
Anyone with thoughts on this...?
Click to expand...
Click to collapse
There are two, separate passwords. One for the encryption and one for the lock screen. And they don't have to be the same.
If you remove the encryption by formatting /data and then boot up on stock OOS, it will encrypt /data with a default password. TWRP can decrypt /data because it knows the default password that's used.
When you set the lock screen password you have the option to set the encryption password to be the same or not.
So, you could set the lock screen and encryption password to be something and then change the lock screen password only to be something different.
ADB can only access /data after it has been decrypted, ie the phone has booted up. But only if: 1. ADB is enabled, 2. You have given permission on your phone to trust the PC connecting to the phone.
So, there's no back doors here. If you have set an encryption password, you can't access the data without having entered the password. And you can't access the phone data without entering the lock screen password. And you can't access the data via ADB unless you have given the specific PC permission from your phone.
Of course, if you use the default encryption password and have TWRP installed, you might just as well not have a password at all. But that's up too you.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
When you set the lock screen password you have the option to set the encryption password to be the same or not.
So, you could set the lock screen and encryption password to be something and then change the lock screen password only to be something different.
Click to expand...
Click to collapse
For which roms is this working? I guess this behaviour is rom spefic. E.g. for all lineageos 15.1 and 16.0 roms and all roms based on tje same code base, the above procedure (setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password".
The only way I know of to get a seperate passphrase for boot and lockscreen on los15, los16 and roms based on these is this:
https://forum.xda-developers.com/on...eplus-3-3t-t3866517/post80390263#post80390263
nvertigo67 said:
For which roms is this working? I guess this behaviour is rom spefic. E.g. for all lineageos 15.1 and 16.0 roms and all roms based on tje same code base, the above procedure (setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password".
The only way I know of to get a seperate passphrase for boot and lockscreen on los15, los16 and roms based on these is this:
https://forum.xda-developers.com/on...eplus-3-3t-t3866517/post80390263#post80390263
Click to expand...
Click to collapse
'setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password"' - Ah, sorry, I didn't realise that. I was saying this based on what I had done on another phone.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
'setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password"' - Ah, sorry, I didn't realise that. I was saying this based on what I had done on another phone.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I'm pretty sure this behavior is rom dependent and not device dependent. E.g.: in los14 and early los15 builds the user was able to set lockscreen passphrase and boot passphrase seperately from rom's settings. This has been removed from aosp (officially because of "security concerns"; but I guess these "concerns" has been too many users with too less knowledge have locked up the boot process).
For me the cryptfs cli is perfectly ok, for the average user the behaviour you've expirienced may feel more comfortable. But the longer I think about, the more I like the seperate setting... YMMV.
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information
mikekote666 said:
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information
Click to expand...
Click to collapse
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918
mikekote666 said:
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918
Click to expand...
Click to collapse
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
you need to format data first time
noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
Format data
gandyprakoso said:
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
Format data
Click to expand...
Click to collapse
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)
noddledizzy said:
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)
Click to expand...
Click to collapse
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L.. and since your TWRP has been nuked, youll have to reflash TWRP again yes? ?
Or, if youbdont want to downgrade TWRP, you can use AOSP based rom such as LOS15.1.. i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.
gandyprakoso said:
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L..
Or, you can use AOSP based rom such as LOS15.1.
i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.
Click to expand...
Click to collapse
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep
noddledizzy said:
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep
Click to expand...
Click to collapse
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591
gandyprakoso said:
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591
Click to expand...
Click to collapse
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?
noddledizzy said:
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?
Click to expand...
Click to collapse
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051
gandyprakoso said:
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051
Click to expand...
Click to collapse
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.
noddledizzy said:
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.
Click to expand...
Click to collapse
Ok then and happy flashing m8 ?
noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
Where? Right in the portion where it says Known Issues of the first link.
Downgrading TWRP to 3.2.3-4 will fix it. I had the same issue.
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
From TWRP thread:
Changed one last thing to try to fix stock Oreo decryption.
There were an upstream TWRP change that should fix the issue where formatting was still leaving /data encrypted as well (this was actually in the last build, but I didn't notice it then)
Click to expand...
Click to collapse
If you still have your non-Encryption-supporting TWRP as download mode, wipe data from there. For some reason which was documented in the TWRP thread, most versions of V20 TWRP doesn't remove the encryption flag even on a full wipe. I've gone through the pain several times, but here's roughly what I went through about a month ago. It's possible that using the latest TWRP may allow you to skip straight to step 8. As of this latest wipe, I'm finally at a point again where my phone works properly and TWRP can still see my data.
Basic process to hopefully have a working ongoing phone and TWRP:
1. Reboot to download-mode TWRP
2. Wipe dalvik/cache/data from the older download-mode TWRP
3. Factory reset with YES, still in older download-mode TWRP
4. Reboot to system; it should give you the new-system-setup past the Decryption unsuccessful screen on your wiped device
5. Setup without a Google account or fingerprint
6. Reboot back to recovery, not download TWRP; use download mode to get there if you need to
7. Flash the latest TWRP version from the thread (no older than October 25, 2019)
8. Reboot back to recovery
9. Wipe dalvik/cache/data
10. Reboot back to system
11. Setup as you like
12. Reboot back to recovery and make sure you can see your storage
If it gets a decryption error on latest TWRP at step 12 and you can't see data while in Recovery, try skipping adding a fingerprint during setup (run through steps 8-12, no fingerprint on 11) and see if that fixes it.
frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
My solution turned out to be formatting /data. Wiping it was apparently not really wiping it clean. Formatting it got me back to a working phone, though I had to re-install everything.
Thanks everyone for the help!
Rob
anyone knows how to fix fingerprints not working? h990 oreo rom mk2000 kernel is there any fix?
do i need to return to nougat but than what? please help
edit: was able to fix that by flashing nougat modem
now wifi wont turn on tho anyone know how to fix?
Ok guys so , I never set-up a password for TWRP , I tried to enter TWRP for installing YouTube VANCED
and I can't because I don't know the password , I tried every password that I can think about , and nothing , I'm sure this is TWRP bug , someone has a clue? Thanks
leftsaray said:
Ok guys so , I never set-up a password for TWRP , I tried to enter TWRP for installing YouTube VANCED
and I can't because I don't know the password , I tried every password that I can think about , and nothing , I'm sure this is TWRP bug , someone has a clue? Thanks
Click to expand...
Click to collapse
Whatever your password is to unlock screen in android
If your phone unlock password doesn't work, it sounds like you have the wrong version of TWRP installed. What ROM and version if TWRP are you running? Easiest work around at the moment will likely to be just temporarily remove your password in Android. That or boot into Fastboot and load a version of TWRP that can decrypt your data.
Newest TWRP
Hi friend , sure password of phone not working ,
TWRP is update . Have other soultion?
leftsaray said:
Hi friend , sure password of phone not working ,
TWRP is update . Have other soultion?
Click to expand...
Click to collapse
Are you using the official one, or the one from this thread? I'm not sure if the official one has patch for latest security patch, but the 3.3.1-6 in that thread should decrypt it. That thread is from the official maintainer too
As stated too, worst case you can remove your password temporarily, which will also delete all your fingerprints. So you'll have to set all that up again if you go that route.
I will try to delete the phone password , should I flash TWRP again? I download from their official site!
leftsaray said:
I will try to delete the phone password , should I flash TWRP again? I download from their official site!
Click to expand...
Click to collapse
I don't believe the one on the official site works with the latest security patch, you need to use the one from the thread above that I linked to. That is from the maintainer of the official version.
Why not just install YouTube vanced thru magisk? Unless you're not rooted.
I have a well working Note 7 with unlocked and rooted 10.3.5.0 Global PFGEUXM (TWRP recovery and magisk).
Today I got the OTA notification to update ROM to 10.3.6.0.
What I will lose if I update?
What's the best way to proceed?
Thank you
Nothing will be lost from a regular OTA Just check around for any bugs or problems that other people are having if any? And update if you like.
rockerduck said:
I have a well working Note 7 with unlocked and rooted 10.3.5.0 Global PFGEUXM (TWRP recovery and magisk).
Today I got the OTA notification to update ROM to 10.3.6.0.
What I will lose if I update?
What's the best way to proceed?
Thank you
Click to expand...
Click to collapse
You have to download the full rom then go to twrp and wipe cache and dalvik flash the rom and magisk without reboot to system. After the flash of magisk you can reboot to the system. If you don't flash magisk before rebooting MIUI overwrite the twrp with the stock recovery and you have to reinstall twrp with fastboot
---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
darhma said:
You have to download the full rom then go to twrp and wipe cache and dalvik flash the rom and magisk without reboot to system. After the flash of magisk you can reboot to the system. If you don't flash magisk before rebooting MIUI overwrite the twrp with the stock recovery and you have to reinstall twrp with fastboot
---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
Click to expand...
Click to collapse
Thank you very much darhma.
Should I reflash Disable_Dm-Verity before magisk?
rockerduck said:
Thank you very much darhma.
Should I reflash Disable_Dm-Verity before magisk?
Click to expand...
Click to collapse
You're welcome. I don't think it's needed the disable_dm-verity (but also i don't think that's a bad thing if you reflash it). If you want to thanks somebody in xda forum just press the thanks button (the ok button).
Hi!
I am new here so please don't be angry for my next questions
I just want root my Redmi Note 7 and keep OTP updates.
I read so many threads and this is my conclusion:
First I must apply for unlocking bootloader. Then flash TWRP recovery from here. After this flash Magisk through TWRP and that is it!
When phone notifies me that there is a new software update, I must download recovery rom from here, put it in internal memory, flash it and flash immediately Magisk again (flashing Magisk is mandatory after every software update to keep root).
Can anybody confirm that this is right way?
Thank You in advance.
wheelnut said:
Hi!
I am new here so please don't be angry for my next questions
I just want root my Redmi Note 7 and keep OTP updates.
I read so many threads and this is my conclusion:
First I must apply for unlocking bootloader. Then flash TWRP recovery from here. After this flash Magisk through TWRP and that is it!
When phone notifies me that there is a new software update, I must download recovery rom from here, put it in internal memory, flash it and flash immediately Magisk again (flashing Magisk is mandatory after every software update to keep root).
Can anybody confirm that this is right way?
Thank You in advance.
Click to expand...
Click to collapse
Yes that's the right way.
---------- Post added at 01:34 PM ---------- Previous post was at 01:26 PM ----------
Another thing: if you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
darhma said:
Yes that's the right way.
---------- Post added at 01:34 PM ---------- Previous post was at 01:26 PM ----------
Another thing: if you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
Click to expand...
Click to collapse
Can I do that in TWRP or I must unpack rom on computer and pack it as zip again?
wheelnut said:
Can I do that in TWRP or I must unpack rom on computer and pack it as zip again?
Click to expand...
Click to collapse
I think that you can do that from twrp but i'm not 100% sure. From computer you don't need to unpack and repack, just open the zip with 7zip or unrar (i'm on linux and don't know which program you use for zip files) and delete the file
darhma said:
I think that you can do that from twrp but i'm not 100% sure. From computer you don't need to unpack and repack, just open the zip with 7zip or unrar (i'm on linux and don't know which program you use for zip files) and delete the file
Click to expand...
Click to collapse
I'm using Windows and WinRAR. Will try after I download recovery rom (my dl speed is ****ty so it wont be soon)
I'm getting Error: 7 and am unable to update through TWRP on Redmi Note 7. Anyone else facing this?
thelastprime said:
I'm getting Error: 7 and am unable to update through TWRP on Redmi Note 7. Anyone else facing this?
Click to expand...
Click to collapse
Are you sure you downloaded the right rom? Error 7 is a mismatch of the firmware
Just come to say that everything went fine.
I didn't need to wait for unlock bootloader. I bought phone 2 weeks ago and using it normally and when I start unlock procedure it unlock without waiting time (I saw that someone must wait 720 hours!!).
I flash twrp and magisk (I had fingerprint lock so after flashing I did data erase) and now I have rooted phone
So, I have a my Redmi Note 7 keeps telling me that there is a new update which is V10.3.10.0.PFGMIXM
I didn't want to install it since I was happy with my phone. But now the notification is not going away and it is always there. So I tried to install it from OTA but since my phone is unlocked and has TWRP on it, the update can't be installed.
My questions are:
- Should I download the rom and flash it through TWRP?
- How should I flash it without being have to make a factory reset? Is it posible not to loose any data? And if so, is it bad to flash it just like that?
- There is a kernel which is called EVIRA that I want to flash, too. So the order should be:
Rom + Kernel + Minsk, is that correct?
Thanks in advance.
EDIT: There are 2 versions of the new rom:
Recovery Rom and Fastboor Rom.
https://c.mi.com/thread-2432115-1-0.html
What is the difference? Which one should I download?
kaplanfa said:
So, I have a my Redmi Note 7 keeps telling me that there is a new update which is V10.3.10.0.PFGMIXM
I didn't want to install it since I was happy with my phone. But now the notification is not going away and it is always there. So I tried to install it from OTA but since my phone is unlocked and has TWRP on it, the update can't be installed.
My questions are:
- Should I download the rom and flash it through TWRP?
- How should I flash it without being have to make a factory reset? Is it posible not to loose any data? And if so, is it bad to flash it just like that?
- There is a kernel which is called EVIRA that I want to flash, too. So the order should be:
Rom + Kernel + Minsk, is that correct?
Thanks in advance.
EDIT: There are 2 versions of the new rom:
Recovery Rom and Fastboor Rom.
https://c.mi.com/thread-2432115-1-0.html
What is the difference? Which one should I download?
Click to expand...
Click to collapse
1) download the full recovery rom
2) reboot to twrp
3) wipe dalvik art/cache and cache
4) flash the rom, the kernel and magisk in this order. Don't reboot to system until you have flashed magisk
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete the file compatibility.zip from the rom zip
Is updating ota with full recovery rom via twrp erase internal data or installed app?
darhma said:
1) download the full recovery rom
2) reboot to twrp
3) wipe dalvik art/cache and cache
4) flash the rom, the kernel and magisk in this order. Don't reboot to system until you have flashed magisk
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete the file compatibility.zip from the rom zip
Click to expand...
Click to collapse
Is installed app or data lost?
m.nav7854 said:
Is installed app or data lost?
Click to expand...
Click to collapse
If you do an update there should be no data loss however it is always recommended to have a backup of your data
Hello guys! I installed twrp but it doesnt allow me to decrypt data so i cant flash anything. Any solutions??
Thanks in advance!!!
ionakos said:
Hello guys! I installed twrp but it doesnt allow me to decrypt data so i cant flash anything. Any solutions??
Thanks in advance!!!
Click to expand...
Click to collapse
What is your ROM and which TWRP do you use?
Use the official TWRP.me twrp-3.6.0_9-0-davinci.img and it will work with up to MIUI 12.5, A11, supporting Data encryption
For A12, there is no TWRP yet supporting its Data encryption. You could use OTG stick - e.g., put the zip file you want to flash to OTG
zgfg said:
What is your ROM and which TWRP do you use?
Use the official TWRP.me twrp-3.6.0_9-0-davinci.img and it will work with up to MIUI 12.5, A11, supporting Data encryption
For A12, there is no TWRP yet supporting its Data encryption. You could use OTG stick - e.g., put the zip file you want to flash to OTG
Click to expand...
Click to collapse
Iam using 3.6.0 and iam on miui 12.1.4 global and it doesn't even ask for pin to decrypt data. I even tried previous versions of twrp
ionakos said:
Iam using 3.6.0 and iam on miui 12.1.4 global and it doesn't even ask for pin to decrypt data. I even tried previous versions of twrp
Click to expand...
Click to collapse
Try changing unlock from pin to pattern, or disable screen unlock
For me, on EEA it worked fine
zgfg said:
Try changing unlock from pin to pattern, or disable screen unlock
For me, on EEA it worked fine
Click to expand...
Click to collapse
I've tried all these things and it still doesn't ask me for encryption password
ionakos said:
I've tried all these things and it still doesn't ask me for encryption password
Click to expand...
Click to collapse
I'm on Xiaomi.eu Stable 12.5.2, it's better ROM:
MIUI 12.0 - MIUI 12.0/12.1/12.2/12.5 STABLE RELEASE
STABLE RELEASE RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
zgfg said:
What is your ROM and which TWRP do you use?
Use the official TWRP.me twrp-3.6.0_9-0-davinci.img and it will work with up to MIUI 12.5, A11, supporting Data encryption
For A12, there is no TWRP yet supporting its Data encryption. You could use OTG stick - e.g., put the zip file you want to flash to OTG
Click to expand...
Click to collapse
Hi, need some more info about the OTG to flash, I was on LOS 18.1, upgraded to LOS 19.0, only realized now no TWRP to decrypt A12, you mean we still can flash the system update or zip (magisk) via TWRP with OTG even though it does not decrypt internal data? flash system update or magisk zip via TWRP will goes through? I thought encryption would be whole phone?
gl7 said:
Hi, need some more info about the OTG to flash, I was on LOS 18.1, upgraded to LOS 19.0, only realized now no TWRP to decrypt A12, you mean we still can flash the system update or zip (magisk) via TWRP with OTG even though it does not decrypt internal data? flash system update or magisk zip via TWRP will goes through? I thought encryption would be whole phone?
Click to expand...
Click to collapse
It will read from OTG and flash to System or Boot, hence Data and Internal storage are not needed
Nevertheless, I would suggest for Magisk to Patch the boot.img and to flash from Fastboot