I have already posted this issue on RR thread
https://forum.xda-developers.com/showpost.php?p=76694740&postcount=3973
However, I believe it is not issue related to RR only and don't want to hijack RR thread for this issue, so writing this in separate thread.
So, my problem is, all of sudden my phone can't start and it says Decyption Unsuccessful...
What I did,
I had following status before I started following steps.
Previous version of RR I have followed following steps for this ROM,
https://forum.xda-developers.com/re...opment/rom-resurrection-remix-v6-0-0-t3748465
Treble recovery installed.
Magisk installed.
No pin/pattern/password was set for lock screen.
I started following steps to again clean flash above RR Rom.
1. Wipe data + system + cache + dalvik cache
2. Flashed this ROM + pico gapps
3. Booted successfully
4. Preformed google set-up
5. Setting fingerprint/pin/password/pattern was skipped.
6. Installed whatsapp
7 . Flashed magisk
8. Installed Titanium backup and restored user apps (no system app or data restored)
9. Rebooted with wipe dalvik+cache
10. And this time I am stuck which says, Decyption unsuccessful.
So, the points I am not understanding are,
1. I never gone with data encyption on this ROM or any previous ROM, then what caused data encyption?
2. It says password I entered is correct, then why decryption failed?
3. I have not set any Pin/pattern/password/FP for this ROM? Still TWRP asks pattern. I entered pattern used for last ROM and it works. From where TWRP is getting this pattern? Is there anything to do with this issue?
4. Only formatting data partition only solution?
5. How to avoid such scenario in future?
I have attached snap of phone screen for this.
I'm sorry but I don't think there is any other way to resolve your problem. Do you mind telling me if you had reset your phone once before flashing any non MIUI ROMs?
Lazy_Pickachu said:
I'm sorry but I don't think there is any other way to resolve your problem. Do you mind telling me if you had reset your phone once before flashing any non MIUI ROMs?
Click to expand...
Click to collapse
No, I don't recollect I ever reset my phone.
You'll have to format your device to remove encryption.
Lazy_Pickachu said:
You'll have to format your device to remove encryption.
Click to expand...
Click to collapse
Once I FORMAT DATA, will this issue resolved for ever?
If no, what can be done to avoid this? Because, once problem comes, you need to format and backing up your data again and again is troublesome.
RmatriX1218 said:
Once I FORMAT DATA, will this issue resolved for ever?
If no, what can be done to avoid this? Because, once problem comes, you need to format and backing up your data again and again is troublesome.
Click to expand...
Click to collapse
Yes it will be resolved until you flash MIUI. Since you flashed ROM already i'd suggest to do it again (clean flash) this time properly to avoid further issues.
Formata Data then Wipe System/Vendor/Cache and flash the ROM, Gapps and Magisk.
k3lcior said:
Yes it will be resolved until you flash MIUI. Since you flashed ROM already i'd suggest to do it again (clean flash) this time properly to avoid further issues.
Formata Data then Wipe System/Vendor/Cache and flash the ROM, Gapps and Magisk.
Click to expand...
Click to collapse
Ya..did the same and everything OK now.
Thanks.
Related
every time I install lollipop, have same issue, my phone gets reboot after lock the screen, i try 4 different rom and the problem is persist,
1. full wipe
2. install rom, gapps, supersu
3. boot normally
4. sign in to google
5. lock the screen off
6. turn screen on
7. reboot
i have google for solution and get nothing
i'm sorry if i post to wrong section, seems it should be on help and troubleshoothing
eevoenc said:
every time I install lollipop, have same issue, my phone gets reboot after lock the screen, i try 4 different rom and the problem is persist,
1. full wipe
2. install rom, gapps, supersu
3. boot normally
4. sign in to google
5. lock the screen off
6. turn screen on
7. reboot
i have google for solution and get nothing
Click to expand...
Click to collapse
Try just installing the rom, no gapps and no supersu. Just wondering if its something to do with running out of memory/space. You could try repartitioning as well. I'm assuming you have no problems with kitkat roms?
noppy22 said:
Try just installing the rom, no gapps and no supersu. Just wondering if its something to do with running out of memory/space. You could try repartitioning as well. I'm assuming you have no problems with kitkat roms?
Click to expand...
Click to collapse
yes i did that, same issue, i have repartitioned my internal to 4,5gb/6,3gb
eevoenc said:
yes i did that, same issue, i have repartitioned my internal to 4,5gb/6,3gb
Click to expand...
Click to collapse
When you did this full wipe, did you also wipe the system partition?
gsstudios said:
When you did this full wipe, did you also wipe the system partition?
Click to expand...
Click to collapse
yes i did, wipe system, cache, data, dalvik, and android secure using twrp
also wipe internal storage too but still the same
same case here https://productforums.google.com/forum/m/#!topic/nexus/X6ZjAAauATc
but it happens on my sgs2 and there is no solution
I am on miui 8.1.4.0 rooted rn3p. So my question is can i use dual boot patcher and dual boot lineage os 14.1
Anyone ??
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots, go back into TWRP and check your log again.
Filip013 said:
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots go back into TWRP and check your log again.
Click to expand...
Click to collapse
Thanks buddy trying it now
Filip013 said:
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots go back into TWRP and check your log again.
Click to expand...
Click to collapse
One more thing its a bit off topic but still i am using radon kernel and i am seeing that when i sweep on the black screen it unlocks how to turn this off as its consuming a lot of battery
Androbots said:
One more thing its a bit off topic but still i am using radon kernel and i am seeing that when i sweep on the black screen it unlocks how to turn this off as its consuming a lot of battery
Click to expand...
Click to collapse
Umm... not sure what you're talking about. Maybe DT2W? I tried out Radon, but I haven't tried that feature. I think you just need to reflash Radon and choose default options. If that doesn't work for you, just reflash MIUI, it will get rid of Radon.
Filip013 said:
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots go back into TWRP and check your log again.
Click to expand...
Click to collapse
Filip013 said:
Umm... not sure what you're talking about. Maybe DT2W? I tried our Radon, but I haven't tried that feature. I think you just need to reflash Radon and choose default options. If that doesn't work for you, just reflash MIUI, it will get rid of Radon.
Click to expand...
Click to collapse
Yes d2tw I was talking about that only and now i have disabled it using kernel audiutor as it was consumping a lot of abttery thanks anyway
Androbots said:
Yes d2tw I was talking about that only and now i have disabled it using kernel audiutor as it was consumping a lot of abttery thanks anyway
Click to expand...
Click to collapse
OK. Let me know if you manage to get DBP to work.
Filip013 said:
OK. Let me know if you manage to get DBP to work.
Click to expand...
Click to collapse
Yup
Edit: i forgot that i checked twrp log (my bad)unfortunately it is encrypted so can't use dbp as of now but next month i might factory reset on miui and then use super su to stop encryption. Hope it works...
Filip013 said:
OK. Let me know if you manage to get DBP to work.
Click to expand...
Click to collapse
Ok so here is what i got in the results of this experiment :
I was able to patch minz1 lineage os and gapps pico 7.0 and then booted to zcx and flashed both files i removed the fingerprint and any kind security measures on miui and i flashed both files and it was successful!!!
But now i am not able to boot to either miui or lineage os!!!
Conclusion: DO NOT TRY THIS!!!
Androbots said:
Ok so here is what i got in the results of this experiment :
I was able to patch minz1 lineage os and gapps pico 7.0 and then booted to zcx and flashed both files i removed the fingerprint and any kind security measures on miui and i flashed both files and it was successful!!!
But now i am not able to boot to either miui or lineage os!!!
Conclusion: DO NOT TRY THIS!!!
Click to expand...
Click to collapse
Weird... It seems to me that you are still encrypted. Have you tried flashing DualBootUtilities and switching to MIUI that way? It is possible that you messed up your primary ROM boot image, I think that happened to me once. Whatever the case, reflashing MIUI should allow you to boot into MIUI.
---------- Post added at 04:08 PM ---------- Previous post was at 04:03 PM ----------
Androbots said:
Yup
Edit: i forgot that i checked twrp log (my bad)unfortunately it is encrypted so can't use dbp as of now but next month i might factory reset on miui and then use super su to stop encryption. Hope it works...
Click to expand...
Click to collapse
I didn't see this post until now. Well, of course you can't use DBP when you're encrypted. If you want to try DPB, you have to format data.
Filip013 said:
Weird... It seems to me that you are still encrypted. Have you tried flashing DualBootUtilities and switching to MIUI that way? It is possible that you messed up your primary ROM boot image, I think that happened to me once. Whatever the case, reflashing MIUI should allow you to boot into MIUI.
Click to expand...
Click to collapse
Flashing back miui kicked me out of the situation and btw i backed up the boot.img as well as tried switching roms none worked and also it was glitching zcx a bit.
Its quite irritating seeing xiaomi and miui enforcing so many security measures a bad day for people who like to customize things a lot!
Androbots said:
Flashing back miui kicked me out of the situation and btw i backed up the boot.img as well as tried switching roms none worked and also it was glitching zcx a bit.
Its quite irritating seeing xiaomi and miui enforcing so many security measures a bad day for people who like to customize things a lot!
Click to expand...
Click to collapse
OK. Good to know that at least you have a working system now. I only experienced issues with booting MIUI after I flashed a custom kernel on MIUI and forgot to update the kernel in DBP app, but like we established flashing MIUI solves the problem.
But again, there's no use in experimenting with DBP until you format data. So please report back when you get around to doing that.
As for Xiaomi policies, I don't know the details, but I don't think it's their fault. It seems that Google can be very strict when certifying devices and allowing the OEMs to include Gapps. Google forces OEMs to ship phones with locked bootloaders and forced encryption.
Filip013 said:
OK. Good to know that at least you have a working system now. I only experienced issues with booting MIUI after I flashed a custom kernel on MIUI and forgot to update the kernel in DBP app, but like we established flashing MIUI solves the problem.
But again, there's no use in experimenting with DBP until you format data. So please report back when you get around to doing that.
As for Xiaomi policies, I don't know the details, but I don't think it's their fault. It seems that Google can be very strict when certifying devices and allowing the OEMs to include Gapps. Google forces OEMs to ship phones with locked bootloaders and forced encryption.
Click to expand...
Click to collapse
Anyways I will be resting my device next month maybe and then I can try and let u know
Filip013 said:
OK. Let me know if you manage to get DBP to work.
Click to expand...
Click to collapse
Ok so i installed epic rim today and i erased data 3times here are results:
Data erase#1 reboot recovery data is is still encrypted
Installing epic rim did not help either flashed super su 3 times still data is encrypted!!!!
What to do???
Androbots said:
Ok so i installed epic rim today and i erased data 3times here are results:
Data erase#1 reboot recovery data is is still encrypted
Installing epic rim did not help either flashed super su 3 times still data is encrypted!!!!
What to do???
Click to expand...
Click to collapse
The order of steps is very important.
1st step: Boot to recovery.
2nd step: Format data (not wipe and I don't know what you mean by erase).
3rd step: Flash ROM (Epic ROM should be good, but it also works for Global Stable and others).
4th step: Flash SuperSU.
5th step: Reboot system.
Filip013 said:
The order of steps is very important.
1st step: Boot to recovery.
2nd step: Format data (not wipe and I don't know what you mean by erase).
3rd step: Flash ROM (Epic ROM should be good, but it also works for Global Stable and others).
4th step: Flash SuperSU.
5th step: Reboot system.
Click to expand...
Click to collapse
Gotcha that means in wipe section i have to go to format data right??
Androbots said:
Gotcha that means in wipe section i have to go to format data right??
Click to expand...
Click to collapse
Yes. Good luck.
Filip013 said:
Yes. Good luck.
Click to expand...
Click to collapse
See I have setup everything on epic rom deleting everything again will be tough I will try it next month when I am bored with epic rom
Androbots said:
See I have setup everything on epic rom deleting everything again will be tough I will try it next month when I am bored with epic rom
Click to expand...
Click to collapse
LOL. Fine. Next month then.
Can someone enlighten me how to dirty flash a custom rom? I mean I did it before but it was back in gingerbread days. Now that we use magisk, can someone give me the exact steps to do?
BenParz said:
Can someone enlighten me how to dirty flash a custom rom? I mean I did it before but it was back in gingerbread days. Now that we use magisk, can someone give me the exact steps to do?
Click to expand...
Click to collapse
Just flash the rom, and wipe cache thats it. But be sure ur using the same rom not another one
BenParz said:
Can someone enlighten me how to dirty flash a custom rom? I mean I did it before but it was back in gingerbread days. Now that we use magisk, can someone give me the exact steps to do?
Click to expand...
Click to collapse
wipe system,davik and cache. then dirty flash. remember not to wipe "system" if you flash OTA .zip
Okay, I have Additional questions :
1. Do I have to disable magisk modules or outright uninstall it before flashing?
2. Do I have to mount system and vendor in twrp again?
3. Do I need to install magisk again after dirty flashing?
4. Do I have to flash DFE again?
BenParz said:
Okay, I have Additional questions :
1. Do I have to disable magisk modules or outright uninstall it before flashing?
2. Do I have to mount system and vendor in twrp again?
3. Do I need to install magisk again after dirty flashing?
4. Do I have to flash DFE again?
Click to expand...
Click to collapse
1. Not necessary (unless you are using a module which may cause bootloop)
2. I never did.
3. Most of the times when dirty flashing the same ROM, twrp flashes Magisk (and GApps) automatically (atleast in my case). If it doesn't flash automatically, then you can flash it manually in order to make it certain.
4. Like I always said, flashing DFE is not necessary if you use the TWRP that supports decryption without actually decrypting your device permanently. Infact, I never suggest anyone to use a decrypted device if using it for financial purpose.
Rowdyy Ronnie said:
1. Not necessary (unless you are using a module which may cause bootloop)
2. I never did.
3. Most of the times when dirty flashing the same ROM, twrp flashes Magisk (and GApps) automatically (atleast in my case). If it doesn't flash automatically, then you can flash it manually in order to make it certain.
4. Like I always said, flashing DFE is not necessary if you use the TWRP that supports decryption without actually decrypting your device permanently. Infact, I never suggest anyone to use a decrypted device if using it for financial purpose.
Click to expand...
Click to collapse
Omg, thanks for answering my questions mate, much appreciated!
Depends, but if you are switching from a different ROM then dirty flash will most likely brick your device or cause a lot of errors and it should never be done. But if it is from the same ROM, like going from older PE to new one, then all you do is flash the newer one with the older version already installed. But it is recommended you clean flash because from my experience, dirty flash always caused errors like lag and crashing. Just use Migrate(available on Play store) and use it to backup apps. A lot of these custom ROMs are still early and in BETA so it is recommended you clean flash.
As for DFE, it is optional. Only problem is you will have to use TWRP with SD card support or one that has a working decryption so that you can flash files through the recovery . You can use apps like flashify to flash if you dont want to your device decrypted. If you got any questions you can ask me.
itscooltime said:
Depends, but if you are switching from a different ROM then dirty flash will most likely brick your device or cause a lot of errors and it should never be done. But if it is from the same ROM, like going from older PE to new one, then all you do is flash the newer one with the older version already installed. But it is recommended you clean flash because from my experience, dirty flash always caused errors like lag and crashing. Just use Migrate(available on Play store) and use it to backup apps. A lot of these custom ROMs are still early and in BETA so it is recommended you clean flash.
As for DFE, it is optional. Only problem is you will have to use TWRP with SD card support or one that has a working decryption so that you can flash files through the recovery . You can use apps like flashify to flash if you dont want to your device decrypted. If you got any questions you can ask me.
Click to expand...
Click to collapse
Actually I've got one.
I want to dirty flash a ROM (just an updated version of the same one) but I dont know how i can place a file into my phone's internal storage through TWRP without formatting de data (full wipe). My phone is not recognized by my PC on TWRP mode unless I make a full wipe.
Can you guys assist?
I have a question I'm using a custom rom with gapps, but the custom rom update that is available does not have gapps if I flash the non-gapp version on my gapp version will it cause problems?
gersomfcomiano said:
Actually I've got one.
I want to dirty flash a ROM (just an updated version of the same one) but I dont know how i can place a file into my phone's internal storage through TWRP without formatting de data (full wipe). My phone is not recognized by my PC on TWRP mode unless I make a full wipe.
Can you guys assist?
Click to expand...
Click to collapse
G3's typically have sd card storage available. athat's where I put all my roms, gapp's, other stuff which I have no trouble flashing from TWRP. Beyond that you must seek one more learned than I.
Nfury00701 said:
wipe system,davik and cache. then dirty flash. remember not to wipe "system" if you flash OTA .zip
Click to expand...
Click to collapse
in this case all data & apps will be lost ?
gajanan57 said:
in this case all data & apps will be lost ?
Click to expand...
Click to collapse
You're right. That user is wrong. Do NOT wipe system if you are dirty flashing. Otherwise you are just doing a normal flashing, not updating your rom.
fede01_8 said:
You're right. That user is wrong. Do NOT wipe system if you are dirty flashing. Otherwise you are just doing a normal flashing, not updating your rom.
Click to expand...
Click to collapse
I'd say no.
Android System partition is mounted as readonly after boot and won't be modified anymore then (unless you modify system files with adb/TWRP and mounted system partition).
Your during Android usage installed apps are stored in Data partition.
However you have to reflash gapps and magisk in case you installed them with TWRP/adb.
I load up YouTube app, and the app loads up, but no content.
I tried Lineage with gaaps and pixel experience where you don't need gaaps flashed.
I cleared cache, Dalvik, cache of the app, uninstall and reinstall app. It's just odd the same issue persists with multiple roms.
Plz explain/help?
Hi i av the same problem did you find a solution to fix this thanks
Greetings. Thank you for posting your issue. I've had the same issue recently.
My problem was that the persist partition got wiped for some random reason. This seems to be a common issue on this device, and most likely you're facing the same problem. For me, apart from YouTube, all the sensors of the device stopped working as well (auto-rotation for example).
To fix this do the following:
1) Make sure you're using the latest TWRP from HavocOS (here)
2) Flash MIUI v10. I used MIUI v10.3.1 from xiaomi.eu (here), but you can use whichever you want, without any trouble.
3) Boot the device. Let it load... then back to recovery. Wipe System, Data, Dalvik and Cache
4) Flash the ROM you want to use
hi i tried your method but on boot i keep getting encryption error unsuccessful
daddy2be2015 said:
hi i tried your method but on boot i keep getting encryption error unsuccessful
Click to expand...
Click to collapse
Try doing a wipe /sdcard from your recovery
Plz anybody help this out...
I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery.
Initially console shows decrypted FBE device with default password. But Encryption status : Encryped
So I went into wipe & Formatted Data inorder to get rid of encryption. Then I rebooted recovery & it shows Unable to decrypt FBE device.
[UPDATE] (24/12/20) : The console output Unable to decrypt FBE device was nothing but to tell us that incompatible operating system flashed.
I flashed global version roms which are the main cause for bootloops. I flashed stock rom, then immediately worked out of the box.
1. Format data after going into twrp *It will wipe you device*
2. If you don't want to install a custom rom just mod MIUI, remove your lock screen password or flash orange fox and if it asks for password just put your lock screen password.
3. Else if you want to install a custom rom
Open recovery
Wipe data cache davilk
Flash rom
Format data
Reboot.
LoadOP2 said:
1. Format data after going into twrp *It will wipe you device*
2. If you don't want to install a custom rom just mod MIUI, remove your lock screen password or flash orange fox and if it asks for password just put your lock screen password.
3. Else if you want to install a custom rom
Open recovery
Wipe data cache davilk
Flash rom
Format data
Reboot.
Click to expand...
Click to collapse
Thnx for reply. I've tried Orange fox too. When I format data, internal storage doesn't decrypt. Also when I flash custom roms, they flash, but I'm gonna stuck in bootloop.
My main problem is that I can't decrypt storage. Phone boots only when I'm on MIUI stock. Am I missing something ?
That is odd but still flash fastboot rom and then flash twrp , flash a rom of your choice then format data . Maybe it will help . Btw which rom are you installing.
LoadOP2 said:
That is odd but still flash fastboot rom and then flash twrp , flash a rom of your choice then format data . Maybe it will help . Btw which rom are you installing.
Click to expand...
Click to collapse
Thnx for the reply. I'm trying to have lineage 17.1 & resurrection remix official build. I think rom's not the issue here. I need to know one thing.
To exactly say my issue, I can do flashing. But when I do & then reboot, Internal storage doesn't show the size & mtp doesn't work too, with bootloop issues along together.
There is no official LineageOS for the device.
kalehrl said:
There is no official LineageOS for the device.
Click to expand...
Click to collapse
Oh, I've mistaken, I was about to say resurrection remix official build & lineage unofficial one. Btw what do you think my device is going up to ? How can I decrypt & use internal storage successfully? I can't use internal storage when I flash a rom. Bcaz internal storage renders useless because of encryption.
Which recovery are you using?
Try flashing magisk 20 or 21.
Flash twrp by marounfurio( I am sorry if I slaughtered the name) which is available on xda.
And format data.
It's midnight here and I am going to sleep I will help to tommorow morning.
LoadOP2 said:
Which recovery are you using?
Try flashing magisk 20 or 21.
Click to expand...
Click to collapse
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
I think encrypted data partition is the whole culprit here. How can I decrypt it ?
MPK99 said:
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
Click to expand...
Click to collapse
And what about flashing magisk in twrp.
MPK99 said:
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
I think encrypted data partition is the whole culprit here. How can I decrypt it ?
Click to expand...
Click to collapse
Formatting data normally decrypts it . I don't know why something like this is happening here.
Follow my guide again maybe? Give it a shot step by step.
LoadOP2 said:
Formatting data normally decrypts it . I don't know why something like this is happening here.
Follow my guide again maybe? Give it a shot step by step.
Click to expand...
Click to collapse
Yah, I'm feeling weird too. Normally there are 3 ways to remove decryption...I tried all those.
1. Formatting Data by typing "yes"
2. Formatting data partition from f2fs to ext4
3. Installing Decrypt script v2 zip immediately after flashing stock rom.
I tried everything I could. I know all sorts of common flashing things. I caz I always used to try so many roms on my previous redmi's, but this one is special case.
I'd suggest you use LineageOS recovery. That's how I removed decryption.
kalehrl said:
I'd suggest you use LineageOS recovery. That's how I removed decryption.
Click to expand...
Click to collapse
Sure. Encryption is the whole culprit for me to say exactly. I'm trying to decrypt & flash builds. I'll notify if it works. Nice to get help from you guys.
Try this.
How to decrypt rom/storage so you can easily switch roms without format
First I would thankx to @sakhatlonda for koutiliy.zip
Steps to download file
1. Download koutility.zip from below.
2. Documentation related to koutility
Read from below link (recommended)
Just a utility zip which can be flashed on every rom flash, to do some pre-defined tasks.
Can be used either to copy everything you place in sdcard/sudeep/system_root to respective dirs or to set config and use that to do predefined tasks
This is how it works:
Flash in recovery, every option has Note with it
Available Configs:
brbootdtbo - auto backup/restore boot & dtbo, will do backup if no backup present and will do restore if backup is there
bbootonly - always backup boot
bdtboonly - always backup dtbo
resbootdtbo - always restore boot & dtbo (brbootdtbo won't work if this is enabled)
enalways - encrypt always (edauto won't work if this is enabled)
dealways - decrypt always (enalways & edauto won't work if this is enabled)
edauto - auto change encryption state on each flash
avb - removes avb flags (if decrypted)
quota - removes quota flag (if decrypted)
keep - doesn't over-writes boot/dtbo backups
debloat - removes bloats
rebloat - restore removed bloats
patchD - same as flash but set in config
productsize - makes a product image from your currently flashed rom to sdcard/sudeep and adds 600mb to it. So you can flash gapps etc. without error. (PC needed to flash product.img)
Steps to decrypt rom/storage
1. Flash roms
2. Flash koutility.zip tested on aosp only
3. Format data (required only first time after flashing koutility)
4. Reboot to recovery
5. Flash gapps (optional)
6. Boot into system
Congratulations your storage/rom is decrypted , you can switch roms without format
Next time when you want to switch roms
Steps
1. Wipe data,caches and dalvik caches
2. Flash rom
3. Flash koutility.zip
4. Reboot to recovery
5. Flash gapps (optional)
6. Boot into system
Notes
Remember you need to config koutility.zip in recovery
How to config koutility for decryption
Volume down (set config) > yes
After that "No" till 5th option
Then "yes" for 6th option
Rest "No" till 15th option
Last "yes" to flash
@LoadOP2 Thanx for providing KoUtil & its read me.
But I think we shouldn't reboot to recovery immediately after formatting the data. Because the stock rom will start it's initial encryption process by then & I won't get decrypted storage. Isn't it ?
I think this is the case that's happening to me. I always reboot recovery after formatting data, my storage will encrypt again because of stock rom's existence.
Yes you have to reboot to recovery. Otherwise you won't be able to use data partition.
LoadOP2 said:
Yes you have to reboot to recovery. Otherwise you won't be able to use data partition.
Click to expand...
Click to collapse
Yes, you're correct, we should do that. But can you read my 1st post in this thread. This is about that specific problem. I'm rebooting recovery after formatting data, then recovery shows Unable to decrypt FBE device
Send your recovery logs after formatting data.
LoadOP2 said:
Send your recovery logs after formatting data.
Click to expand...
Click to collapse
That would help. I'll attach screenshots too. Currently I'm on stock & being busy. I'll do this by today night & post logs & screenshots.