Related
Factory Resets do not remove encryption with TWRP recovery. It will reset the phone like normal, but the encryption will still remain.
I am looking to try and remove encryption entirely so I can install 4.4 and CWM Recovery. I've heard you have to flash to stock but I don't know what packages, where to get them, and which way I should flash them. Any help is appreciated.
ThomasBags said:
Factory Resets do not remove encryption with TWRP recovery. It will reset the phone like normal, but the encryption will still remain.
I am looking to try and remove encryption entirely so I can install 4.4 and CWM Recovery. I've heard you have to flash to stock but I don't know what packages, where to get them, and which way I should flash them. Any help is appreciated.
Click to expand...
Click to collapse
You need to use the FORMAT DATA option, which will wipe the entire device, if you still get asked for password after that, flash factory image.
Flash the stock recovery....
ThomasBags said:
Factory Resets do not remove encryption with TWRP recovery. It will reset the phone like normal, but the encryption will still remain.
I am looking to try and remove encryption entirely so I can install 4.4 and CWM Recovery. I've heard you have to flash to stock but I don't know what packages, where to get them, and which way I should flash them. Any help is appreciated.
Click to expand...
Click to collapse
I had an Encrypted HTC One that I installed TWRP Recovery. TWRP could not decrypt the phone and the phone would not factory reset. Fixed by using Fastboot to flash the stock recovery and then was able to factory reset my phone.
Fastboot flash recovery recovery.img
Got the Sprint stock recovery image from viperboy (I'm too new to post links) the file name is: Sprint_One_stock_recovery.img
Search XDA with this file name you you will find it.
Too late for you I'm sure but maybe it will help some others.
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
kunal_07 said:
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
Click to expand...
Click to collapse
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
kunal_07 said:
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
Click to expand...
Click to collapse
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Heisenberg said:
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Click to expand...
Click to collapse
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
kunal_07 said:
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
Click to expand...
Click to collapse
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Heisenberg said:
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Click to expand...
Click to collapse
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
the log says:
E:Unable to decrypt with default password, you may need to perform a format data.
E:unable to mount storage
E:unable to mount settings storage during GUI startup.
kunal_07 said:
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
Click to expand...
Click to collapse
That's odd, I can't think of why 3.0.0-1 wouldn't boot, but 2.8.7.2 definitely won't work as it obviously can't decrypt. You might not be able to backup.
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
kunal_07 said:
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
Click to expand...
Click to collapse
I think you're pretty much stuck, you could try disabling all security.
is it possible to sideload supersu somehow?
kunal_07 said:
is it possible to sideload supersu somehow?
Click to expand...
Click to collapse
Maybe, you could try adb sideload in TWRP, but SuperSU needs to access the data partition which TWRP can't decrypt.
I tried it and it got to
**Boot image patcher**
patching sepolicy.
Failure, aborting.
i seem to have the same issues too. unable to access recovery and lost root. phone cant be detected in fastboot.
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Great news
1. Yes.
2. I don't think such a command exists. You'd need to use the "fastboot format userdata" command instead if you want to decrypt anyway. Just remember to backup all your data first.
3. You'd need to flash a custom kernel today doesn't force encryption. Otherwise your data well will automatically encrypt on the first boot after formatting.
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
kauemelhado said:
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
Click to expand...
Click to collapse
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
kunal_07 said:
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
Click to expand...
Click to collapse
Tks,
I found it 2 seconds later I asked you. LOL
Anyhow, thank you bro.
I was messing around with Magisk and everything was good until I trying replacing my bootanimation using Magisk where it would display part of the animation and then freeze. Couldn't figure out how to remove the offending flashed Magisk module I booted into TWRP and uninstalled Magisk. Doing so left me in a boot loop so I went back into TWRP and flashed SuperSU. now when I boot up regularly I'm told encryption was stopped abruptly and that I have to wipe data. going back into TWRP I'm asked to decrypt the /data partition and neither "default_password" or my lockscreen password is decrypting... am I royally screwed? HELP!
dimm0k said:
I was messing around with Magisk and everything was good until I trying replacing my bootanimation using Magisk where it would display part of the animation and then freeze. Couldn't figure out how to remove the offending flashed Magisk module I booted into TWRP and uninstalled Magisk. Doing so left me in a boot loop so I went back into TWRP and flashed SuperSU. now when I boot up regularly I'm told encryption was stopped abruptly and that I have to wipe data. going back into TWRP I'm asked to decrypt the /data partition and neither "default_password" or my lockscreen password is decrypting... am I royally screwed? HELP!
Click to expand...
Click to collapse
Close the decryption screen in TWRP and wipe everything: data, system, internal storage, cache.
It sounds like you neglected to do that when you rooted originally. Without doing that, you can't actually flash anything in TWRP.
You'll be left with a blank device, so you'll have to ADB something to your phone in TWRP to flash.
Zacharee1 said:
Close the decryption screen in TWRP and wipe everything: data, system, internal storage, cache.
It sounds like you neglected to do that when you rooted originally. Without doing that, you can't actually flash anything in TWRP.
You'll be left with a blank device, so you'll have to ADB something to your phone in TWRP to flash.
Click to expand...
Click to collapse
Don't need to wipe system. Its actually better if you just hit the "Format Data" button instead of going into advanced.
me2151 said:
Don't need to wipe system. Its actually better if you just hit the "Format Data" button instead of going into advanced.
Click to expand...
Click to collapse
Oh right, I did do that. Forgot
Zacharee1 said:
Oh right, I did do that. Forgot
Click to expand...
Click to collapse
Lol. Yup. If you do "Format Data" it actually decrypts the partitions but if you just go to advanced and select the options it just erases them leaving them encrypted. Its weird.
Hello,
I have tried to root multiple times but everytime I flash TWRP and format Data and then restart the data partition keeps getting encrypted again, I am using the official 8.0 Oreo UK version which recently got released, I have tried installing Magisk and Xposed both are installed successfully but with error that /data is not mounted and like I said if I format data to decrypt it and then restart it automatically encrypts it. I also tried flashing Samsung anti root and no opt zips but it also didn't help.
It was released a few days ago, just go with custom or wait for working solution
1 workaround for now :
flash rom via odin /
flash twrp via odin /
flash no_encrypt 6.0, full wipe, reboot to recovery /
flash MoroKernel 1.5 (magisk already included) /
reboot and have fun with no encryptation anymore
No-verity didn't work for me but remove encryption.zip did.
this didn't work for me, it resulted in a bootloop
ric69 said:
1 workaround for now :
flash rom via odin /
flash twrp via odin /
flash no_encrypt 6.0, full wipe, reboot to recovery /
flash MoroKernel 1.5 (magisk already included) /
reboot and have fun with no encryptation anymore
Click to expand...
Click to collapse
fre78 said:
this didn't work for me, it resulted in a bootloop
Click to expand...
Click to collapse
Sorry for you. check Mount system or data or enable MTP. Internal storage was probably still at 0
I rebooted more than 10times it's ok here
zainbfaisal said:
Hello,
I have tried to root multiple times but everytime I flash TWRP and format Data and then restart the data partition keeps getting encrypted again, I am using the official 8.0 Oreo UK version which recently got released, I have tried installing Magisk and Xposed both are installed successfully but with error that /data is not mounted and like I said if I format data to decrypt it and then restart it automatically encrypts it. I also tried flashing Samsung anti root and no opt zips but it also didn't help.
Click to expand...
Click to collapse
sir may i ask how come ur able to have twrp .
how dd u install twrp on android 8.0 UK firmware?
thanks for help
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
OREO stock keeps encrypting DATA partition
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
fre78 said:
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
Click to expand...
Click to collapse
Yes, I can confirm that I can do whatever I want on TWRP.
I used a .zip found somewhere on a 8.0 thread. I feel like the no-verity zip doesn't work on some devices as it didn't on mine.
Let me grab the link for you : https://drive.google.com/file/d/1tCLamw9j07bhRgEd6qhymqUxExazy04c/view?usp=sharing
Here you go, try this. It should work now. Try doing the exact same steps as you did before but with this zip instead of no-verity.
Good luck mate
NewbieFTW said:
Yes, I can confirm that I can do whatever I want on TWRP.
I used a .zip found somewhere on a 8.0 thread. I feel like the no-verity zip doesn't work on some devices as it didn't on mine.
Let me grab the link for you : https://drive.google.com/file/d/1tCLamw9j07bhRgEd6qhymqUxExazy04c/view?usp=sharing
Here you go, try this. It should work now. Try doing the exact same steps as you did before but with this zip instead of no-verity.
Good luck mate
Click to expand...
Click to collapse
Can anyone confirm that magisk should be installed in twrp before encryption disabler?
skydivider said:
Can anyone confirm that magisk should be installed in twrp before encryption disabler?
Click to expand...
Click to collapse
Magisk removes the encryption disabler .zip for some reason.
Sounds good dosen´t work.
When you flash Magisk it flashes its own boot or system img and remove encrypt flashes its own, if you flash the magisk itll flash the img but if you then flash encryption disabler it will overwrite the magisk img and magisk will uninstall or if you flash the encrypt and then magisk then you will have magisk but encryption will be enabled.
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
zainbfaisal said:
Sounds good dosen´t work.
When you flash Magisk it flashes its own boot or system img and remove encrypt flashes its own, if you flash the magisk itll flash the img but if you then flash encryption disabler it will overwrite the magisk img and magisk will uninstall or if you flash the encrypt and then magisk then you will have magisk but encryption will be enabled.
Click to expand...
Click to collapse
I'm sorry then, I don't know what to say. It worked for me.
I needed reinstal magisk after boot for root, but worked for me...
fre78 said:
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
Click to expand...
Click to collapse
When this happend to me, i hit format data and typed yes, when i mount on TWRP i can see my storage again
I can root with patched boot image, but Samsung Healt and Samsung Pay don't works. Anyone?
miguelan.ruiz said:
I can root with patched boot image, but Samsung Healt and Samsung Pay don't works. Anyone?
Click to expand...
Click to collapse
Samsung Pay will, at the moment, probably never work again because it trips Knox.
For Samsung Health the fix is still the same: install a build.prop editor and change the value of RO.Config.Tima from 1 to 0.
not for me
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
doesn't work for me
Apparently there are 2 kind of users here.
One part did manage to install stock Oreo (BTU? other CSC?) , with root (magisk? superSu?) and a working TWRP (3.2.1?) which is not read-only on our beloved S7 Edge (SM-G935F)
The other part did not manage to setup this particular config.
It would be nice to have a detailed step-by-step guide from scratch by someone who managed to do it, so we can reproduce it.
Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk
Dr4In said:
Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk
Click to expand...
Click to collapse
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?
strongst said:
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?
Click to expand...
Click to collapse
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.
Dr4In said:
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.
Click to expand...
Click to collapse
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:
strongst said:
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:
Click to expand...
Click to collapse
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?
Dr4In said:
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?
Click to expand...
Click to collapse
If you mean your encrypted twrp of your internal storage = no.
I would start from scratch with decrypted.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I used this and solved the problem
I was facing to the same problem today, and the problem was the Magisk version! Same problem for Pixel 3/XL users...
The way you can fix it: Install v19.1 BETA (not the stable)! It should boot up!