Related
After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??
eid_elageeb said:
After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??
Click to expand...
Click to collapse
You need modified TWRP 3.0.2-28 to get TWRP working with Beta 8. I had the same issue witrh my installation.
Also you need to make sure to remove your lock screen, then you will be able to use TWRP
strumaticjoker2 said:
Also you need to make sure to remove your lock screen, then you will be able to use TWRP
Click to expand...
Click to collapse
even without protection, twrp asking pw, need to erase use data and system.
I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys
eid_elageeb said:
I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys
Click to expand...
Click to collapse
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx
yiphoming said:
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx
Click to expand...
Click to collapse
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased
eid_elageeb said:
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased
Click to expand...
Click to collapse
No luck, can erase the storage, but it is still in encrypted.
yiphoming said:
No luck, can erase the storage, but it is still in encrypted.
Click to expand...
Click to collapse
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.
rarog said:
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.
Click to expand...
Click to collapse
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.
AcmE85 said:
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.
Click to expand...
Click to collapse
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.
rarog said:
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.
Click to expand...
Click to collapse
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
Do you also get the dm-verity bootscreen?
AcmE85 said:
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
Click to expand...
Click to collapse
Hm... Interesting, do you have a link? And perhaps a link to a thread with all the available versions? I searched, but found only several tutorial threads with just one or another version linked, no thread for specific modified version.
AcmE85 said:
Do you also get the dm-verity bootscreen?
Click to expand...
Click to collapse
As far as I know - no.
When would this error message pop up?
LS.xD said:
As far as I know - no.
When would this error message pop up?
Click to expand...
Click to collapse
Right at boot before or after the screen which shows that the bootloader is unlocked.
AcmE85 said:
Right at boot before or after the screen which shows that the bootloader is unlocked.
Click to expand...
Click to collapse
No such error message for me
LS.xD said:
No such error message for me
Click to expand...
Click to collapse
Did you flash SuperSU?
AcmE85 said:
Did you flash SuperSU?
Click to expand...
Click to collapse
Yes, 2.78 SR5
I have done format userdata in fastboot but my phone still shows up as encrypted. Flashed 3.0.2-1.28 and I still get a password screen when booting to recovery. Not really sure what else I can do.
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Edit : Nougat running on my op3.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
anshulajain said:
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Click to expand...
Click to collapse
I don't have any issues with ext4, infact i do feel ext4 is more stable than f2fs so file system is my last concern. Thanks for your method, but then how did u root again? Installing nougat is fine but what after that? I have read that you can't use modified twrp without formatting internal memory first, as it'll show you the pin issue. Let me know how do you propose a safe method to achieve root.
Renosh said:
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
Click to expand...
Click to collapse
Yes i am encrypted, rooted, stock OOS 3.2.8 + Franco kernel. Official TWRP(not modified). I am using ext4, never used f2fs at all. The time to backup data and then to restore it all back is the reason formatting is not an "preferred" option for me. I can do it, but i would have to wait until i find enough time to do the whole process. I am in a full time job, so i hope you would understand.
Puddi_Puddin said:
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
Click to expand...
Click to collapse
Well this again defeats the purpose of my original question, but thanks mate. I would definitely read the guide if decide to switch to f2fs.
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Puddi_Puddin said:
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
Click to expand...
Click to collapse
Thanks a lot for informing me mate. I really don't want to decrypt my storage as of now. I guess flashing stock recovery is the only solution now. Will hope someone would pick up the twrp and update it.
anshulajain said:
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Click to expand...
Click to collapse
Seems like stock recovery is the best way as of now. Seems like I'll have to love without root until someone updates twrp to support encrypted storage.
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Zielony360 said:
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
Click to expand...
Click to collapse
That i already knew mate. But i WANT my storage to remain encrypted. And that's the issue with modified TWRP. You can't enter into recovery on that if your storage is encrypted.
kpmohamedhussain said:
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Click to expand...
Click to collapse
Again, "You can't enter into recovery on modified TWRP if your storage is encrypted." So i won't be able to enter into twrp in the first place, let alone flash anything.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Go to twrp. Press backup. Select only data. Save to PC youre backup for safety..
3.2.8 it's Android 6, 4.0 it's Android 7. Some apps might not work from base to base.
If you want to change to F2FS it will format youre phone, wipe phone full internal memory. If you want to change it back to ext4, same.
Clean flash, full wipe it's always better.
dmoses1969 said:
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Click to expand...
Click to collapse
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
anshulajain said:
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
Click to expand...
Click to collapse
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
abhibnl said:
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
Click to expand...
Click to collapse
I dont know. I found this on Oneplus forum. May be worth trying. Just not 100% sure.....
Thanks! Will try and let you know
abhibnl said:
Thanks! Will try and let you know
Click to expand...
Click to collapse
Well, I tried something, waiting on it to finishing booting and see how it went.
I flashed twrp-3.0.2-1.28-oneplus3p version,
Flashed the OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip inside TWRP,
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip right after flashing OTA zip.
Its rebooting and says Android is upgrading. Fingers crossed.
EDIT: Its booted and I am on Nougat, didnt lose my data and phone is still encrypted!
Edit: Ended up having issues with settings app locking up. So, I went a different route and its all working great now.
Downloaded the stock recovery image and renamed it to recovery.img
Make sure after you rename it its not named recovery.img.img, If you have show file extensions enabled on your pc you should already see the file extension.
Rebooted to bootloader - adb flash recovery recovery.img
Using the volume keys and power button selected - reboot recovery.
Now in stock recovery - flashed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
After rom is done flashing, went right back into bootloader. Did not let my phone reboot to start the OS.
Renamed twrp-3.0.2-1.28-oneplus3p.img to recovery.img
adb flash recovery recover.img
Powered off phone and Manually boot it into recovery by holding Power + Volume Down button.
Phone booted into TWRP
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip
Wiped cache / dalvik
Rebooted system from TWRP and waited. System is really smooth now, no issues yet. Been playing with it for awhile now.
During the booting up process it might take a minute and it will reboot twice. Dont get nervous like I did thinking it was going to start bootlooping. It booted just fine. I read in a nother thread that SuperSU is what causes it to boot twice.
So......Now I have OOS 4.0 Nougat, Rooted, Encrypted and everything seems to be working fine.
Hey there,
I have been really annoyed since i installed OOS 4.0.0. First because it took ages the first time to get it right, and then because i had to start from scratch with every little 30MB update AGAIN.
I didn't find any reliable source to what happens in the folowing cases, thus this thread :
1- Flashing official recovery + updating through android
=> Will it work/DM-Verity error appear ?
2- Flash official recovery and sideload OTA/Full ZIP
=> Is /data getting wiped ? Same question about DM-Verity
3-Flash full Zip in latest eng.stk TWRP followed with supersu
Has anyone explored these solutions ?
Thanks in advance
EDIT: Working way for updating:
1: Dirty flash full ROM in latest modified TWRP
2: Flash SuperSU WITHOUT booting into system
3: Wipe dalvik/cache
4: reboot to system.
For explanation about what triggers DM-Verity check out post 19
DM verity is triggered by the firmware. You can't avoid it unless you want to run old firmware
It is not an error nor a bug - it is a notification. There is no impact to performance
2x4 said:
DM verity is triggered by the firmware. You can't avoid it unless you want to run old firmware
It is not an error nor a bug - it is a notification. There is no impact to performance
Click to expand...
Click to collapse
I do know that. I simply try to find the best way to update without hassle and without getting the DM-Verity message.
Nobody07 said:
I do know that. I simply try to find the best way to update without hassle and without getting the DM-Verity message.
Click to expand...
Click to collapse
update everything (ROM/TWRP), flash old (non-4.x) firmware
FYI you're fixing an aesthetic issues and there may be more bugs from using the old firmware.
2x4 said:
update everything (ROM/TWRP), flash old (non-4.x) firmware
FYI you're fixing an aesthetic issues and there may be more bugs from using the old firmware.
Click to expand...
Click to collapse
I don't have the issue right now with a 4.x firmware ... You are not helping... My guess is using OnePlus recovery and updating through android there wont be a DM Verity message. Do you know if this is true ? If not you aren't telling me anything i do not know.
Nobody07 said:
I don't have the issue right now with a 4.x firmware ... You are not helping... My guess is using OnePlus recovery and updating through android there wont be a DM Verity message. Do you know if this is true ? If not you aren't telling me anything i do not know.
Click to expand...
Click to collapse
if you use stock recovery you won't get the dm-verity notice either.
not sure why you mentioned eng.stk TWRP if you're not trying to run TWRP.
2x4 said:
if you use stock recovery you won't get the dm-verity notice either.
not sure why you mentioned eng.stk TWRP if you're not trying to run TWRP.
Click to expand...
Click to collapse
Thank you for answering, but seriously, did you even read the first post ?
So i can flash OnePlus firmware, update android within the system and then flash twrp again. With no DM Verity appearing ?
Nobody07 said:
Thank you for answering, but seriously, did you even read the first post ?
So i can flash OnePlus firmware, update android within the system and then flash twrp again. With no DM Verity appearing ?
Click to expand...
Click to collapse
no - it's not the flashing process.
DM verity notification will always be present while you have TWRP (unless you go back to old firmware)
2x4 said:
no - it's not the flashing process.
DM verity notification will always be present while you have TWRP (unless you go back to old firmware)
Click to expand...
Click to collapse
That's were you are wrong...
I currently have twrp and no dm-verity.
Nobody07 said:
That's were you are wrong...
I currently have twrp and no dm-verity.
Click to expand...
Click to collapse
because you are on pre-nougat ROM and/or firmware
2x4 said:
because you are on pre-nougat ROM and/or firmware
Click to expand...
Click to collapse
Im getting tired of you ignoring what i say.
I'm on OOS 4.0.1. I did a clean sideload through OnePlus recovery, and flashed twrp/root afterwards. No DM-Verity. I DID NOT flash an old firmware.
it's a compilation of things not just one thing, the firmware thing is just the easy way out, if you decrypt the phone data (just wipe it) and rooted then re encrypted it, you wont get the dm verity issue...
so simply, sideload or flash the full rom , if you sideloaded immediately fastboot TWRP (the latest official or modified) , then immediately flash SuperSU... reboot to system, no dm verity will appear.
---------- Post added at 09:46 PM ---------- Previous post was at 09:45 PM ----------
2x4 said:
no - it's not the flashing process.
DM verity notification will always be present while you have TWRP (unless you go back to old firmware)
Click to expand...
Click to collapse
not true, i have the latest 4.0.2 firmware and TWRP and no DM verity .
theduke7 said:
it's a compilation of things not just one thing, the firmware thing is just the easy way out, if you decrypt the phone data (just wipe it) and rooted then re encrypted it, you wont get the dm verity issue...
so simply, sideload or flash the full rom , if you sideloaded immediately fastboot TWRP (the latest official or modified) , then immediately flash SuperSU... reboot to system, no dm verity will appear.
Click to expand...
Click to collapse
What you are saying is i can flash full ROM through twrp, followed by supersu, reboot, and i wont get dm-verity nor loose any data?
Nobody07 said:
What you are saying is i can flash full ROM through twrp, followed by supersu, reboot, and i wont get dm-verity nor loose any data?
Click to expand...
Click to collapse
yes , idid exactly that updating from 4.0.1 to 4.0.2, dirty flashed the full rom , then immediately SuperSU, and then TWRP again just to be sure...and Viola
2x4 said:
because you are on pre-nougat ROM and/or firmware
Click to expand...
Click to collapse
Did a clean flash (beta 10) with the stock recovery, flashed TWRP with SuperSU afterwards.
No dm-verity.
After dirty flashing beta11 full zip + SuperSU through TWRP the dm-verity screen is still NOT there.
Btw, this has been already discussed weeks ago.
Do your homework.
dm verity is a fail safe present in system boot.img . Nothing related to firmware. Don't know from where people getting all this hoax
cpt.macp said:
dm verity is a fail safe present in system boot.img . Nothing related to firmware. Don't know from where people getting all this hoax
Click to expand...
Click to collapse
BC whether it's a band-aid or fixes the issue, if u flash an old fw outside of nougat with trwp, it gits rid of the nag
Bradl79 said:
BC whether it's a band-aid or fixes the issue, if u flash an old fw outside of nougat with trwp, it gits rid of the nag
Click to expand...
Click to collapse
it's the worst way to "fix" the issue, you're using an old firmware that's more than likely have incompatibility issues with the OOS updated rom, so unless you're using a custom rom (not OOS or OOS based) where it doesn't matter what firmware you use it's not a recommended practice.
Neither flashing twrp, nor OOS would trigger dm-verity (unless you already have that message)
If you however boot into system, dm-verity will be triggered. The idea is to patch that before it gets triggered.
Flashing SuperSU patches DM verity. Which is great if you want root access. Again this patch won't work if you already have dm-verity warning. Once you flash the ROM, do not boot into system. Flash SuperSU 2.79 or above and verity will be patched. You will also see a line "patching dm-verity" in SuperSU installation process. Now verity message won't appear.
If you don't want root, there is a no-verity zip that you can flash which will have the same effect. I use SuperSU so I don't have any links to this but Google is your best friend.
- if you already have verity
- if you forgot patching verity, booted into system and now warning screen has appeared.
Now here is where things get tricky. Boot to fastboot, connect phone and type
fastboot format userdata
Remember the above step will wipe internal storage completely
Reboot to recovery
Format data (not wipe but format. This step is very important)
Flash OOS
Flash SuperSU
Reboot to system. Now there will be no dm-verity warning
@ungeeked great detailed explanation that should put an end to all chatter TBH your reply should be pinned in this section for some while and titled DM-Verity explained.
I just updated to global beta 9.3.28 and my twrp is now showing data encrypted and it asks for the password (my lockscreen password doesnt work), internal storage is showing 0 Mb & I'm unable to flash anything. Somehow i rooted my device with magisk patch boot image method and twrp started flasing things, i flashed "no-verity-opt-encrypt-6.0" & its not doing anything as well. So i took the bold step and wiped cache,dalvik,data & internal storage then twrp worked correctly w/o asking for any password but after flashing the rom again(flashed lazyflasher too) and rebooting to twrp gets me to the same problem of data encryption!!!....what am i doing wrong here??...please help
Solution- change recovery to one which supports pie(like to orangefox).
Did you tried to flash another TWRP that supports miui pie?
Try orangefox recovery.
[email protected] BOY said:
Did you tried to flash another TWRP that supports miui pie?
Try orangefox recovery.
Click to expand...
Click to collapse
What you are suggesting is to use orangefox and then wipe all the data,internal storage and then flash the rom again, well i guess i have to try it.... Thanks for the suggestion.
rick_th1 said:
I just updated to global beta 9.3.28 and my twrp is now showing data encrypted and it asks for the password (my lockscreen password doesnt work), internal storage is showing 0 Mb & I'm unable to flash anything. Somehow i rooted my device with magisk patch boot image method and twrp started flasing things, i flashed "no-verity-opt-encrypt-6.0" & its not doing anything as well. So i took the bold step and wiped cache,dalvik,data & internal storage then twrp worked correctly w/o asking for any password but after flashing the rom again(flashed lazyflasher too) and rebooting to twrp gets me to the same problem of data encryption!!!....what am i doing wrong here??...please help
Click to expand...
Click to collapse
Try this twrp it supports miui 10 pie encryption
https://forum.xda-developers.com/showpost.php?p=79215432&postcount=42
01Thesam said:
Try this twrp it supports miui 10 pie encryption
https://forum.xda-developers.com/showpost.php?p=79215432&postcount=42
Click to expand...
Click to collapse
Will try this for sure, orangefox is working as of now...
[email protected] BOY said:
Did you tried to flash another TWRP that supports miui pie?
Try orangefox recovery.
Click to expand...
Click to collapse
Thanks bro, its working, i never thought that twrp was the culprit.
rick_th1 said:
Thanks bro, its working, i never thought that twrp was the culprit.
Click to expand...
Click to collapse
You're welcome :good:
Had the same problem, but I am using Redfox... Will check for an update or change to orange.
so dudes very confused.what to do to flash pie?I am still on Oreo.Will I flash oreo with my current recovery and afterwars when system boots I have to flash orange recovery?
Στάλθηκε από το SM-G955F μου χρησιμοποιώντας Tapatalk
It happened to me.
When redwolf recovery ask you to enter passwords just Cancel it.
Goto wipe. Slide to wipe.
Goto reboot. Reboot recovery.
unfortunately This solution cause my phone need to fatory reset before reboot
The same happened to me, after flashing weekly (thru my redwolf recovery) 9.3.28 my storage has encrypted.
My question is the following,
Do I have possibility of decyripting storage w/o data factory reset ?
and,
Shall I loose my data if I implement the below method explained below web page ?
http://www.androwide.com/2017/08/unable-to-mount-storage-twrp-internal-storage-0mb.html
Or is there any method (with any type recovery) to decrypt storage w/o loosing data in storage ?
updated TWRP by GuaiYiHu TWRP-20190330-3.2.3.0-whyred
changelog
Update prebuilt kernel for pie firmware decryption
download link
https://github.com/GuaiYiHu/android_device_xiaomi_whyred/releases
==> not tested by me
sas_sas said:
The same happened to me, after flashing weekly (thru my redwolf recovery) 9.3.28 my storage has encrypted.
My question is the following,
Do I have possibility of decyripting storage w/o data factory reset ?
and,
Shall I loose my data if I implement the below method explained below web page ?
http://www.androwide.com/2017/08/unable-to-mount-storage-twrp-internal-storage-0mb.html
Or is there any method (with any type recovery) to decrypt storage w/o loosing data in storage ?
Click to expand...
Click to collapse
The solution is to flash a recovery with support of pie decryption, i dont know about redwolf but orangefox recovery definitely works for me & it will for you as well, just flash it & all your problems will be solved.
I was on RN 5 Pro Oreo with Orange Fox R9.0.1
Got Pie update today n updated OTA.
But when i boot into Orange Fox recovery Data encrypted,asking for password.
It is not accepting screen lock PIN or password.
Even tried to boot recovery by removing screen lock n finger print data , still no use.
Any solution for this without formatting my data?
Thank You in advance.
[email protected] BOY said:
You're welcome :good:
Click to expand...
Click to collapse
I don't if I messed up installing orange but, at the beginning it showed:
"
<Heading> Mount
Unmodified System Partition
TWRP can leave your system partition unmodified to make it easier for you to take official updates.
TWRP will be unable to prevent the stock ROM from replacing TWRP and will not offer to root your device.
<in red> Zip Installations or ADB operations may still modify the system partition. </in red>
Swipe to allow modifications
"
I swiped, installed orange zip from my sdcard, then it rebooted to my lock screen instead of rebooting into recovery mode.
---------- Post added at 05:16 PM ---------- Previous post was at 04:59 PM ----------
in_out said:
updated TWRP by GuaiYiHu TWRP-20190330-3.2.3.0-whyred
changelog
Update prebuilt kernel for pie firmware decryption
download link
https://github.com/GuaiYiHu/android_device_xiaomi_whyred/releases
==> not tested by me
Click to expand...
Click to collapse
I installed TWRP, but lazyflasher got "Updater process ended with ERROR 1: Error installing file"
TechBT said:
I was on RN 5 Pro Oreo with Orange Fox R9.0.1
Got Pie update today n updated OTA.
But when i boot into Orange Fox recovery Data encrypted,asking for password.
It is not accepting screen lock PIN or password.
Even tried to boot recovery by removing screen lock n finger print data , still no use.
Any solution for this without formatting my data?
Thank You in advance.
Click to expand...
Click to collapse
My problem solved simply by installing OF 9.0.2 over 9.0.1 . Rooted with latest Magisk, enabled cam2api by editing build props. GCam working good.
Hello, I've just installed the latest xiaomi.eu rom (MIUI 12.5) for my Redmi Note 8T (willow), now i would like to root and install magisk, someone can tell me what i need to flash for my device and rom version? Thanks in advance.
Hydra1704 said:
Hello, I've just installed the latest xiaomi.eu rom (MIUI 12.5) for my Redmi Note 8T (willow), now i would like to root and install magisk, someone can tell me what i need to flash for my device and rom version? Thanks in advance.
Click to expand...
Click to collapse
Rename Magiskxx.apk to zip and flash it like any zip in recovery
loopypalm said:
Rename Magiskxx.apk to zip and flash it like any zip in recovery
Click to expand...
Click to collapse
Thanks for the answer! I was reading the official installation guide from Magisk, and they listed the recovery method as risky, but I've seen the method you said being used with my same device and custom recovery without issues, so is 100% safe? What are the risk? Thanks.
Hydra1704 said:
Thanks for the answer! I was reading the official installation guide from Magisk, and they listed the recovery method as risky, but I've seen the method you said being used with my same device and custom recovery without issues, so is 100% safe? What are the risk? Thanks.
Click to expand...
Click to collapse
Instaling as a zip is risky on some device because magisk is not only for RN8
the same zip can be flashed on all device so certainly there will be risk because not all devices are the same
but for RN8 you can flash it as a zip without any risk
some users reported bootloop ,and that's because of encryption
follow the clean flash steps and you will be fine
loopypalm said:
follow the clean flash steps and you will be fine
Click to expand...
Click to collapse
I always flash the rom that way, first "format data", and then the others partitions (chache/dalvik and so on) and after flashing the rom, format data again and then reboot to system, everything is always went smoothly so far. But i've never flashed the DFE, this will cause encryption problems when flashing Magisk now?
Hydra1704 said:
I always flash the rom that way, first "format data", and then the others partitions (chache/dalvik and so on) and after flashing the rom, format data again and then reboot to system, everything is always went smoothly so far. But i've never flashed the DFE, this will cause encryption problems when flashing Magisk now?
Click to expand...
Click to collapse
Roms encrypt storage by default for security reasons, but this is not very stable especially with A11/12, so most devs recomand flashing DFE to disable encryption and to avoid bootloops when changing a rom or flashing magisk ...
loopypalm said:
Roms encrypt storage by default for security reasons, but this is not very stable especially with A11/12, so most devs recomand flashing DFE to disable encryption and to avoid bootloops when changing a rom or flashing magisk ...
Click to expand...
Click to collapse
So now or either i risk it flashing without DFE o i need to do "Format Data" again to remove the encryption right? Anyway, as custom recovery I'm using MIUI Hellas Team Win Recovery like this guy and it seems to remove encryption when you enter recovery, i can see all the internal memory folders and files.
Hydra1704 said:
So now or either i risk it flashing without DFE o i need to do "Format Data" again to remove the encryption right? Anyway, as custom recovery I'm using MIUI Hellas Team Win Recovery like this guy and it seems to remove encryption when you enter recovery, i can see all the internal memory folders and files.
Click to expand...
Click to collapse
idk why you choose that recovery ...
i said what have to be done according to my experiance/people commun problems ...
you are free to whatever you want ...
For GG