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.
Situation, i have bootloader unloacked but recovery stock, so i flash "twrp-3.0.3-x_blu_spark_v14-op3.img" but the recovery won't start.
Last twrp i have installed was it e it works well, but after install last beta i have this problem.
What i do wrong?!?
fraizzo said:
Situation, i have bootloader unloacked but recovery stock, so i flash "twrp-3.0.3-x_blu_spark_v14-op3.img" but the recovery won't start.
Last twrp i have installed was it e it works well, but after install last beta i have this problem.
What i do wrong?!?
Click to expand...
Click to collapse
That is not the latest TWRP by bluspark. Flash the latest one.
tnsmani said:
That is not the latest TWRP by bluspark. Flash the latest one.
Click to expand...
Click to collapse
where i can find .img last bluspark?
fraizzo said:
where i can find .img last bluspark?
Click to expand...
Click to collapse
https://forum.xda-developers.com/devdb/project/dl/?id=25628
Sent from my ONEPLUS A3003 using Tapatalk
fraizzo said:
where i can find .img last bluspark?
Click to expand...
Click to collapse
Here you go
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Thanks, now i have another problem, when i enter in recovery i cannot decrypt with my sequence.
And when i reboot to system, then i try to enter to recovery i find stock recovery
fraizzo said:
Thanks, now i have another problem, when i enter in recovery i cannot decrypt with my sequence.
And when i reboot to system, then i try to enter to recovery i find stock recovery
Click to expand...
Click to collapse
If you can access the OS, change pin/password within the OS to something else, then back to the one you always use then go back to recovery and it should work.
Renosh said:
If you can access the OS, change pin/password within the OS to something else, then back to the one you always use then go back to recovery and it should work.
Click to expand...
Click to collapse
The OS works well, i change my sequence, then back to first sequence, flashed the twrp, it ask me to insert password (not sequence) i try but without success...
I try to translate pattern to number but without success
Code:
1 2 3
4 5 6
7 8 9
fraizzo said:
The OS works well, i change my sequence, then back to first sequence, flashed the twrp, it ask me to insert password (not sequence) i try but without success...
I try to translate pattern to number but without success
Click to expand...
Click to collapse
Means you are encrypted and somehow ****ed. Gotta love force encryption in OOS.
Puddi_Puddin said:
Means you are encrypted and somehow ****ed. Gotta love force encryption in OOS.
Click to expand...
Click to collapse
So what i have to do now?
fraizzo said:
So what i have to do now?
Click to expand...
Click to collapse
Well, if you are sure that you are on the right twrp version by Bluspark. Then I would start with a factory reset. Your phone is encrypted, somehow TWRP asks for a password that never has been setup.
Let's get into business.
On Android go to security settings and select swipe or none in security lock.
Reboot to fastboot, flash the latest TWRP V39, since you are already using bluspark TWRP I won't need to recommend it.
Reboot imediatly to TWRP, Data should get mounted now.
The TWRP version you are on at the moment is outdated, always use the latest build.
Chaplan said:
Let's get into business.
On Android go to security settings and select swipe or none in security lock.
Reboot to fastboot, flash the latest TWRP V39, since you are already using bluspark TWRP I won't need to recommend it.
Reboot imediatly to TWRP, Data should get mounted now.
The TWRP version you are on at the moment is outdated, always use the latest build.
Click to expand...
Click to collapse
I have wiped data and now i can enter in recovery, but if i reboot to os the recovery return stock. Why?
Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
fraizzo said:
I have wiped data and now i can enter in recovery, but if i reboot to os the recovery return stock. Why?
Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
Click to expand...
Click to collapse
Reflash TWRP, reboot to recovery, when prompted to give permission to modify system partition you should slide to Yes.
That will keep TWRP in place.
My phone is cripted! on settings i read phone cripted so when i flash twrp it ask me password...
I try to set NONE to security lock but some problem...
I don't want format data again...
After a bit of trial and error, I managed to find a combination of files and actions that allowed me to successfully root my 64GB Pixel C on 8.0.0 by installing SuperSU via TWRP.
Steps:
Perform a clean installation of the official release, found here
Use the unofficial 3.0.0 TWRP release found in this thread (direct download link here) and boot to recovery ("fastboot boot [TWRP filename].img") - the latest official 3.1.1 TWRP did not work, either via flashing or booting
ADB sideload SuperSU 2.82SR3 found in this thread (direct download link here)
Hope this helps!
Stuck at TWRP after
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?
Jeff Z. said:
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?
Click to expand...
Click to collapse
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk
MadManMoon said:
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thanks. My problem was my pixel kept booting to TWRP even selecting to boot the system, kind of strange. I think I missed your first step, the pad was OTA updated to 8.0 from 8.0 Beta release. I will try again with flash the factory image of 8.0 first.
Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.
NitroSS said:
Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.
Click to expand...
Click to collapse
Still works for me as of the September 2017 update. About to try it again with the October update.
It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.
CatThief said:
It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.
Click to expand...
Click to collapse
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.
Huffy1 said:
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.
Click to expand...
Click to collapse
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.
CatThief said:
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.
Click to expand...
Click to collapse
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up
Huffy1 said:
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up
Click to expand...
Click to collapse
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?
CatThief said:
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?
Click to expand...
Click to collapse
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.
Huffy1 said:
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.
Click to expand...
Click to collapse
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.
CatThief said:
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.
Click to expand...
Click to collapse
Use FDE then and it reportedly works.
Huffy1 said:
Use FDE then and it reportedly works.
Click to expand...
Click to collapse
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?
CatThief said:
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?
Click to expand...
Click to collapse
Don't know, only telling you what I did cause I had the same problem as you
Well I'm finally rooted. I didn't change the encryption, just tried a different method and after several tries it finally worked. I used adb sideload inside TWRP after canceling the password screen. Odd that it took several tries, though, to get through it without generating errors. We'll see how it goes next month.
I have had a lot of trouble with rooting Oreo...
I started out trying to use Magisk but gave up after many attempts. Every version, and every kernel I tried resulted in booting to recovery and not system. I could have tried the ADB method but I actually want to have TWRP so I didn't try that.
By the time I tried SuperSU my factory image had had an OTA and many apps & files installed so I can't say my system is "clean" but I have Fastboot flashed the stock boot image many (many) times to recover from whatever Magisk does to the kernel. I never looked all that hard for this unofficial TWRP people talk about so I used 3.1.1-1. At some point I converted to File Based Encryption because it is so much nicer to use, and so TWRP cannot decrypt my internal storage, but the workaround is to put zips and images on a USB drive. It also does not ask for a password. So far so good, I have my workarounds. I do also have this weird error where TWRP cannot unmount the system but I can flash kernels without problems. I have chosen to keep system read-only for superstitious reasons. I think it will fail if I look at it funny sometimes lol.
From this state I flashed the latest SuperSU and it booted! So I do have root. I still would like to try Magisk for the modules but it seems this isn't ready. However, my trusty old terminal app hangs at the su command... and several kernels will crash my tablet... so it's "working" but there is more to do. And literally just now I see I have an OTA. lol.
I followed the original instructions and got rooted with the latest version of Oreo. But, TWRP still wouldn't flash correctly without causing boot loops.
I finally got it resolved by using the original instructions, then loading the Official TWRP app from Google Play. I used the app to flash twrp-3.1.1-1-dragon.img.
Everything is working properly now. I have 8.0.0 (OPR1.170623.032, Nov 2017) loaded and rooted, and the Pixel C will boot into TWRP and see the encrypted data.
Is it posible to flash latest Oreo stock factory image https://developers.google.com/android/images ryu-opr1.170623.032-factory-020f1cf9.zip using stock TWRP or do I have to side load it ?
I'm getting a Invalid zip file format error in TWRP when I try and flash it
Hi Friends
pleas help , i wanted install Oreo so i went to lock boat-loader by TOOL_ALL_IN_ONE
and i didnt see the alert message and above message appeared "Your device is corrupt. It can't be trusted and will not boot"
so please advise
If you alter the system in any way you can't lock the bootloader as it will not boot due to possible safety issues by modying the system. In order to use the device with a locked bootloader, you need to flash the original OS.
If you want to use a modified system, keep the bootloader unlocked. Unfortunately, there is no other way.
how can i flash rom please help
MsuatafaKhatab said:
how can i flash rom please help
Click to expand...
Click to collapse
It would be helpful to know what you want to flash.
Is it OxygenOS?
Then flash it in e.g. TWRP and then lock the bootloader again.
Is it something else?
Keep the bootloader unlocked.
Macusercom said:
It would be helpful to know what you want to flash.
Is it OxygenOS?
Then flash it in e.g. TWRP and then lock the bootloader again.
Is it something else?
Keep the bootloader unlocked.
Click to expand...
Click to collapse
Is it OxygenOS?
yes it is
Did you modify it in any way? Root, Magisk, Xposed, Recovery, flashable ZIPs or anything else?
yes, the problem i used tool "TOOL_ALL_IN_ONE" to lock boat-loader
Use "fastboot flashing unlock" to unlock it again, install TWRP, use adb push to copy OxygenOS to it, flash OxygenOS, use "fastboot flashing lock" and it should work just fine again.
not allow to me to unlock again
https://imgur.com/a/fIYqZ
I assume this is due to "Allow OEM Unlock" not being enabled. I don't know if anyone has a workaround.
Otherwise, I suggest contacting OnePlus and getting support by an L2 technician.
Macusercom said:
I assume this is due to "Allow OEM Unlock" not being enabled. I don't know if anyone has a workaround.
Otherwise, I suggest contacting OnePlus and getting support by an L2 technician.
Click to expand...
Click to collapse
Thanks pro
I contacted them and they gave file to downlod and will log in to my pc tommorrow to fix
Really appreciate your help
Sent from my LG-H870S using Tapatalk
MsuatafaKhatab said:
Thanks pro
I contacted them and they gave file to downlod and will log in to my pc tommorrow to fix
Really appreciate your help
Sent from my LG-H870S using Tapatalk
Click to expand...
Click to collapse
thanks pro , the session finished with succeed thanks
but why the delete the files after finish installation
MsuatafaKhatab said:
thanks pro , the session finished with succeed thanks
but why the delete the files after finish installation
Click to expand...
Click to collapse
They keep their tools private. So unless you back them up during the session in the background and use a keylogger to get the password, you will never get your hands on the tools. No one does.
But you can contact them again at any time and they will assist you so just don't do this again and you should be fine
this could be avoided if we had fastboot images of OxygenOS..
you can flash any image from fastboot, even if it's locked.
Seven_of_Nine24 said:
this could be avoided if we had fastboot images of OxygenOS..
you can flash any image from fastboot, even if it's locked.
Click to expand...
Click to collapse
How bro
I already fixed by one plus technical support , but to learn
Sent from my ONEPLUS A5010 using Tapatalk
I didn't do anything in my phone n still I got the device is corrupt.
Tejesh.D said:
I didn't do anything in my phone n still I got the device is corrupt.
Click to expand...
Click to collapse
Open ticket in one plus website
They will fix by logging to your PC
Don't worry
They are very friendly
Sent from my ONEPLUS A5010 using Tapatalk
MsuatafaKhatab said:
Open ticket in one plus website
They will fix by logging to your PC
Don't worry
They are very friendly
Click to expand...
Click to collapse
It's working now....but still ll open a ticket
I also faced similar problem yesterday & following steps worked for me
1. I unlocked the bootloader
2. Flashed TWRP & wiped everything (system data cache, internal) I wiped internal because I was seeing random folders in my internal, you can skip it while trying first time but if it doesn't work. Try again with wiping internal.
3.I flashed stock recovery via fastboot.
4. ADB side loaded oxygen OS (any version) using stock recovery.
I side loaded rom because I was unable to select file from stock recovery option "install from internal"
*don't boot now*
5. Reset everything from stock recovery option and then boot it.
I haven't tried to lock bootloader again but it should lock if you try now without rooting it again (⅛)
(⅛) I think the problem was that I mistakenly tried to lock bootloader with magisk installed which made this issue.
(That's what I was able to notice)
Please report back if this was the case for you too.
Sent from my ONEPLUS A5010 using Tapatalk
Try this
https://r.tapatalk.com/shareLink?ur...share_tid=3733012&share_fid=3793&share_type=t
Sumanyu Sinha said:
I also faced similar problem yesterday & following steps worked for me
1. I unlocked the bootloader
2. Flashed TWRP & wiped everything (system data cache, internal) I wiped internal because I was seeing random folders in my internal, you can skip it while trying first time but if it doesn't work. Try again with wiping internal.
3.I flashed stock recovery via fastboot.
4. ADB side loaded oxygen OS (any version) using stock recovery.
I side loaded rom because I was unable to select file from stock recovery option "install from internal"
*don't boot now*
5. Reset everything from stock recovery option and then boot it.
I haven't tried to lock bootloader again but it should lock if you try now without rooting it again (⅛)
(⅛) I think the problem was that I mistakenly tried to lock bootloader with magisk installed which made this issue.
(That's what I was able to notice)
Please report back if this was the case for you too.
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Sent from my ONEPLUS A5010 using Tapatalk
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.