Related
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.
Hey, so I rooted my Galaxy S7 edge exynos, and everything was great. However, when I boot into recovery, TWRP can't do anything. It can't backup, install images, nothing. It says my memory is 0mb, and if I try to backup it says "cannot mount /data and unable to find crypto footer". I can restart my phone to system and everything works perfectly. Is there a way to fix this? I'm using latest version of TWRP (3.0.2)
Thanks guys!
Byyz said:
Hey, so I rooted my Galaxy S7 edge exynos, and everything was great. However, when I boot into recovery, TWRP can't do anything. It can't backup, install images, nothing. It says my memory is 0mb, and if I try to backup it says "cannot mount /data and unable to find crypto footer". I can restart my phone to system and everything works perfectly. Is there a way to fix this? I'm using latest version of TWRP (3.0.2)
Thanks guys!
Click to expand...
Click to collapse
FORMAT DATA, it's explicitly stated in the instructions. You must format data to wipe encryption.
Sent from my Pebble Time
Brava27 said:
FORMAT DATA, it's explicitly stated in the instructions. You must format data to wipe encryption.
Sent from my Pebble Time
Click to expand...
Click to collapse
Is there no way around this at all? It's really a hassle having to reset my phone every time.
Is there at least a way to install xposed without formatting?
Thanks!
Byyz said:
Is there no way around this at all? It's really a hassle having to reset my phone every time.
Is there at least a way to install xposed without formatting?
Thanks!
Click to expand...
Click to collapse
You only do this once, use flashfire or titanium backup to backup your stuff.
did you flash this after TWRP?
"If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP."
https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt.zip
same here !:<
Same problem a few days ago. Caused by secure startup or encrypt device obviously lol. Only fix for read/write on data/internal storage is factory reset in stock recovery. Unfortunately this was the only fix for my fussy G935F.
TWRP couldn't mount data to wipe anyway I tried and the only way to flash was through selecting extSD.
i dont have escription enabled though ._.
jgalvez21 said:
i dont have escription enabled though ._.
Click to expand...
Click to collapse
I find a solution, just go in wipe and format data , it will removes encryption on internal storage. if not works try a factory reset in stock recovery them try again, S7 is encrypted out of the box and Twrp can't read or mount data. Works for me in G935F.
how long does it take to format? i chose exfat and it's taking ages... am i doing something wrong?
Brava27 said:
FORMAT DATA, it's explicitly stated in the instructions. You must format data to wipe encryption.
Sent from my Pebble Time
Click to expand...
Click to collapse
i unlocked a nexus 5 and got the same problem, formatted data, all seems good now
is there a way to save my data? my phone is oneplusone
if you use twrp to flash xposed, it'll still work. But your data is still encrypted.
Should I do anything else after the Formating data (install TWRP again, root again...)?
I remember that I did format data in my last phone and it completely deleted everything including OS, so now im little afraid.
Currently I can't do nothing in TWRP, not wipe and not backup...
Nitzans said:
Should I do anything else after the Formating data (install TWRP again, root again...)?
I remember that I did format data in my last phone and it completely deleted everything including OS, so now im little afraid.
Currently I can't do nothing in TWRP, not wipe and not backup...
Click to expand...
Click to collapse
Just format data and you will be able to use twrp.
fureedx said:
Just format data and you will be able to use twrp.
Click to expand...
Click to collapse
Thanks, it worked! Too bad that the only way to get this is by loosing all the data .
Hi all,
I followed instruction on installing TWRP and also have root. I also installed the no-verity-opt-encrypt.zip file, but I still can't access internal SD. It says 0mb. Also after installing the zip it similar stated 'unable to mount'.
When I try to format data it can't mount it.
am i missing a step??
ideas?
Thanks in advance...
PS: not sure if this is relevant, but it keep coming up with the same flash screen message: "keep system read only?"
I tick the box says don't display this, and swipe to allow modifications, but get this message every time.
The_Hammer said:
Hi all,
I followed instruction on installing TWRP and also have root. I also installed the no-verity-opt-encrypt.zip file, but I still can't access internal SD. It says 0mb. Also after installing the zip it similar stated 'unable to mount'.
When I try to format data it can't mount it.
am i missing a step??
ideas?
Thanks in advance...
PS: not sure if this is relevant, but it keep coming up with the same flash screen message: "keep system read only?"
I tick the box says don't display this, and swipe to allow modifications, but get this message every time.
Click to expand...
Click to collapse
You have to format the data after you installed twrp. And then you can flash supersu and no verity opt thingie.
Thanks for the reply... It wont let me format it. 'says can not mount'
I'm having the same issue here. Although I can root, I cannot wipe data, so no way to install a custom ROM
Hi
I'm having this very weird issue with my phone (A2017G). I unlocked BL, installed TWRP, updated to TWRP 3.0.3-1, formatted data, factory reset, install A2017G_Nougat_Bootloader+ModemFix, factory reset again, install LineageOS and then boot. The device booted fine.
I noticed root wasn't built-in so I flashed SuperSU V2.65. After a reboot, my phone won't let me boot into the system anymore. I get asked for a password. Whatever password I enter, it says "Decryption Unsuccesful. The password is correct, but data is corrupt". When I reboot to TWRP and format data and then factory reset, nothing changes. I keep getting the prompt before system boots. Even re-flashing the bootstack and lineageOS doesn't help. I know flashing anything else will brick my phone, so I refrained from doing that.
What am I doing wrong here?
Note that TWRP reads both my internal storage and my SDcard. However, internal storage contains only the folder "TWRP". When I go up a level, I can see the normal folders like "boot", "cache", "data", "dev" and so on. In the "backup" menu, DATA also shows as "0MB"
File system says "f2fs". Do I repair/change it?
Thanks
Ah,
I have/had the same error. Looks like this needs to be changed to ext4.
CU
Joerg
Controllerboy said:
Hi
I'm having this very weird issue with my phone (A2017G). I unlocked BL, installed TWRP, updated to TWRP 3.0.3-1, formatted data, factory reset, install A2017G_Nougat_Bootloader+ModemFix, factory reset again, install LineageOS and then boot. The device booted fine.
I noticed root wasn't built-in so I flashed SuperSU V2.65. After a reboot, my phone won't let me boot into the system anymore. I get asked for a password. Whatever password I enter, it says "Decryption Unsuccesful. The password is correct, but data is corrupt". When I reboot to TWRP and format data and then factory reset, nothing changes. I keep getting the prompt before system boots. Even re-flashing the bootstack and lineageOS doesn't help. I know flashing anything else will brick my phone, so I refrained from doing that.
What am I doing wrong here?
Note that TWRP reads both my internal storage and my SDcard. However, internal storage contains only the folder "TWRP". When I go up a level, I can see the normal folders like "boot", "cache", "data", "dev" and so on. In the "backup" menu, DATA also shows as "0MB"
File system says "f2fs". Do I repair/change it?
Thanks
Click to expand...
Click to collapse
I would say the answer lies with issues between f2fs and SuperSU
https://www.xda-developers.com/xda-...upersu-has-trouble-with-f2fs-data-partitions/
Sent from my SM-P600 using XDA-Developers Legacy app
And you flash the wrong SuperSU, the one needed is either v.2.79 or v.2.79-R3. try booting back to TWRP and clean Flash Lineage again and flash either one of the SuperSu I Mention before.
I have the same after install unofficial lineage 14.1 'decryption unsuccessful'
On TWRP 3.0.3-1 I go in 'wipe', then 'advanced wipe' and select 'Data', press 'Repair or Change File System' and then 'Change File System' to EXT4
That's work fine on my 2017G
For root
download.lineageos.org/extras
The arm64 zip
After install with TWRP go in deployment options and activated it!
Lineage is running with root
Thanks, everyone. That worked. I was quite worried for a while, I really don't want tot RMA the device a second time due tot me messing things up.
Where do I find the options in Twrp for deployment
jdg007 said:
Where do I find the options in Twrp for deployment
Click to expand...
Click to collapse
Twrp have no deployment option, what won't you to do.
joergwrage said:
Ah,
I have/had the same error. Looks like this needs to be changed to ext4.
CU
Joerg
Click to expand...
Click to collapse
Probably it is caused by a known bug in the f2fs implementation in the kernel. Only @Unjustified Dev can solve it. Some people who already was using f2fs with TWRP 3.0.4 and LineageOS 13.1 are not having those issues and they were able to dirty flash the new LOS 14.1.
Updating to TWRP 3.0.3-1 is very recommended. TWRP 3.0.2 has some problems when flashing zips. SuperSU is one of them.
i Also need help guys :/ my auto rotate isnt working. neither is mu auto brightness :/
crazynitro said:
i Also need help guys :/ my auto rotate isnt working. neither is mu auto brightness :/
Click to expand...
Click to collapse
I have the same
For some reason I cannot decrypt when booting TWRP. On a normal boot, I get the prompt to enter my PIN, I enter my PIN, and it boots. In TWRP it says "failure to decrypt."
I'm using 3.2.1-7 of TWRP, which worked before, but now it's unable to decrypt my internal data.
Halp?
Edit: I guess when I get home I'll install an older version of TWRP and see if that helps, but I am otherwise sunk.
TPMJB said:
For some reason I cannot decrypt when booting TWRP. On a normal boot, I get the prompt to enter my PIN, I enter my PIN, and it boots. In TWRP it says "failure to decrypt."
I'm using 3.2.1-7 of TWRP, which worked before, but now it's unable to decrypt my internal data.
Halp?
Edit: I guess when I get home I'll install an older version of TWRP and see if that helps, but I am otherwise sunk.
Click to expand...
Click to collapse
First thoughts : Backup internal and format data.
Perhaps try https://androidfilehost.com/?fid=818222786056030640 but that's only for lockscreen but you'll never know
edit : or try like another twrp3.2.1.0 (but will result in repair data too) or 3.2.1.6
raystef66 said:
First thoughts : Backup internal and format data.
Perhaps try https://androidfilehost.com/?fid=818222786056030640 but that's only for lockscreen but you'll never know
edit : or try like another twrp3.2.1.0 (but will result in repair data too) or 3.2.1.6
Click to expand...
Click to collapse
I mean, I know I'll be able to backup all my data since I can access it on a normal boot. Just very weird/annoying. I'm going to try flashing an older version of TWRP and seeing if it works.
...Maybe I should backup my data first
Did you ever find a solution to decrypting in TWRP? Currently having same issue with LOS15.1 and TWRP3.2.3.0.
I wasnt able to get mine to work, so I just backed up all my data and reformated, if you lost root you can still sideload magisk, dunno why but you can
I have a One Plus 6t international version rooted through Magisk. I was debloating some One Plus system apps this morning and removed something I shouldn't have.... now the reboot gets stuck on the loading screen, then boots into TWRP recovery. I'm trying to restore from backup but everything is encrypted and TWRP isn't asking me for a password to decrypt.
I don't have a pin or anything set on the phone at the moment
Tried the twrp decrypt <pin> command with the default password but it just says 'Failed to decrypt data'.
Anything I'm missing here or do I just to reformat and give up on the encrypted data?
devianaviator said:
I have a One Plus 6t international version rooted through Magisk. I was debloating some One Plus system apps this morning and removed something I shouldn't have.... now the reboot gets stuck on the loading screen, then boots into TWRP recovery. I'm trying to restore from backup but everything is encrypted and TWRP isn't asking me for a password to decrypt.
I don't have a pin or anything set on the phone at the moment
Tried the twrp decrypt <pin> command with the default password but it just says 'Failed to decrypt data'.
Anything I'm missing here or do I just to reformat and give up on the encrypted data?
Click to expand...
Click to collapse
Managed to decrypt the files by installing a different version of TWRP: https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Turns out I did not bother to do any backups...
Can copy all of the pictures and documents out though which was what I was primarily after.