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.
Related
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
I have a US996 with an unlocked bootloader. I installed TWRP (although I still can't get it to decrypt data). I installed the latest SuperSU - and there were no errors (although without the ability to decrypt, TWRP couldn't wipe Dalvik/cache).
But after rebooting, Root Checker still says I'm not rooted.
What am I doing wrong?
Figured it out. Unless I disable the default encryption to formatting Data, installing SuperSU fails. Once I format Data, the install works properly.
Haphim said:
Figured it out. Unless I disable the default encryption to formatting Data, installing SuperSU fails. Once I format Data, the install works properly.
Click to expand...
Click to collapse
How did you disable default encryption? I flashed twrp but in recovery it always says it had to decrypt in order to mount. I don't know the password twrp is asking for. Thanks
I followed the instructions and flashed TWRP. However it asks for a decrypt password when TWRP loads. How do I get past this? I formatted data twice and I am unable to flash SuperUser since I can't see any mount points. Its read only. Thank you to anyone that can help.
SOLVED:
Here is what I did wrong. After I ran all the dirtycow commands and got permissive root access I rebooted into TWRP. TWRP showed that the sdcard was encrypted. What I kept doing at this step was formatting the sd card which is correct, however I kept rebooting back into system. That was my mistake. I needed to immediately reboot back INTO TWRP RECOVERY instead. Once I rebooted directly back into TWRP recovery after the format I was able to view file system information move su.zip to sd card and install SuperUser.zip from TWRP.
When rooting my H990ds the guide said when TWRP asks for a password just press cancel. It should be the same for you too.
inurb said:
How did you disable default encryption? I flashed twrp but in recovery it always says it had to decrypt in order to mount. I don't know the password twrp is asking for. Thanks
Click to expand...
Click to collapse
Sorry, the text you quoted from me should have read that disabled default encryption *by* formatting Data. Formatting Data is what takes care of it.
I'm not sure what happened, I was flashing a kernel, and suddenly my device stopped booting, getting stuck at the OnePlus logo, with 'Powered by android". TWRP was installed, so I tried restoring a backup, but that didn't help. I tried flashing the stock 4.5.5 full zip, it would still stay at the OP logo screen. I tried wiping the phone, flashing the stock full zip, still stuck at boot. I tried going back to the stock recovery (I know, risky), and it succeeded in flashing, but when I boot to recovery, the screen just goes black, and I have to hard-reboot. I can however flash TWRP back, and it seems to work fine. When I look in the file manager on TWRP, I can see things in the system partition, but I still can't boot to it.
I'm starting to panic now, so any help would be appreciated.
To clarify, even doing fastboot boot OP5_recovery.img brings be to the black screen
It may be that you have an issue with encrypted data partition which you cannot recover otherwise
Try flashing TWRP, then in TWRP select "Wipe", "Format data" and answer with "yes" when asked for confirmation.
NOTE: when doing the steps above the whole data partition will be erased, including internal storage - so when in doubt back up your data before proceeding
s3axel said:
It may be that you have an issue with encrypted data partition which you cannot recover otherwise
Try flashing TWRP, then in TWRP select "Wipe", "Format data" and answer with "yes" when asked for confirmation.
NOTE: when doing the steps above the whole data partition will be erased, including internal storage - so when in doubt back up your data before proceeding
Click to expand...
Click to collapse
I had already done that a few times.
However, wiping fixed it, but not in TWRP. doing fastboot -w fixed it, and the phone was able to boot to stock recovery. After that I flashed system zip, and TWRP again, and I'm back up (just got it working 15 mins ago)
Thanks for the answer, though!
0xTJ said:
I had already done that a few times.
However, wiping fixed it, but not in TWRP. doing fastboot -w fixed it, and the phone was able to boot to stock recovery. After that I flashed system zip, and TWRP again, and I'm back up (just got it working 15 mins ago)
Thanks for the answer, though!
Click to expand...
Click to collapse
Please change the title of this thread to: "[SOLVED] Soft-Bricked OnePlus 5, TWRP works, but nothing else". That will help others who may get into a similar plight.
Seems, I need to lock bootloader to take official update. Is it worth the hassle of backing up all data, and upgrading to oreo?
SysAdmNj said:
Seems, I need to lock bootloader to take official update. Is it worth the hassle of backing up all data, and upgrading to oreo?
Click to expand...
Click to collapse
Just flash the full zips from TWRP and reflash Magisk to maintain root.
SysAdmNj said:
Seems, I need to lock bootloader to take official update. Is it worth the hassle of backing up all data, and upgrading to oreo?
Click to expand...
Click to collapse
I didn't need to lock the bootloader again to update to Oreo from rooted and encrypted Nougat. This is what I did:
Downloaded OnePlus5Oxygen_23_OTA_028_all_1801031502_04d7cc5. zip, twrp-3.2.1-0-universal-codeworkx-cheeseburger.img and Magisk-v15.3.zip.
Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP.
Rebooted to TWRP again to make sure that my TWRP was updated.
Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
This deleted my Internal Storage so I had to backup everything beforehand.
Then used advanced wipe to wipe Cache and Dalvik.
Mounted the internal storage by using the Mount option from TWRP main menu.
I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
Copied the OnePlus full update and Magisk zip file.
Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots.
Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
Booted into TWRP and flashed Magisk.
I am now on Oreo and I hate the way Ambient Display looks right now.
pleomaxell said:
I didn't need to lock the bootloader again to update to Oreo from rooted and encrypted Nougat. This is what I did:
Downloaded OnePlus5Oxygen_23_OTA_028_all_1801031502_04d7cc5. zip, twrp-3.2.1-0-universal-codeworkx-cheeseburger.img and Magisk-v15.3.zip.
Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP.
Rebooted to TWRP again to make sure that my TWRP was updated.
Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
This deleted my Internal Storage so I had to backup everything beforehand.
Then used advanced wipe to wipe Cache and Dalvik.
Mounted the internal storage by using the Mount option from TWRP main menu.
I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
Copied the OnePlus full update and Magisk zip file.
Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots.
Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
Booted into TWRP and flashed Magisk.
I am now on Oreo and I hate the way Ambient Display looks right now.
Click to expand...
Click to collapse
beningodfrey4 said:
Just flash the full zips from TWRP and reflash Magisk to maintain root.
Click to expand...
Click to collapse
Yes but is there a way to dirty flash so you don't have to wipe your data?
Yes, obviously a lot more steps to remain encrypted, but worth it if you want to keep your data intact. Do try it out and reply the outcome on that thread.
https://forum.xda-developers.com/oneplus-5/how-to/guide-upgrade-nougat-rooted-encrypted-t3734779
You guys don't understand. Any tutorial that includes "format data" means EVERYTHING gets wiped - even internal storage.
The OP is asking for a way to avoid it, and I think there isn't any. So you either bite the bullet or stay where you are.
Also, I had trouble flashing Magisk 15.3 with codeworkx recovery. Worked fine with bluspark.
Rhoban said:
You guys don't understand. Any tutorial that includes "format data" means EVERYTHING gets wiped - even internal storage.
The OP is asking for a way to avoid it, and I think there isn't any. So you either bite the bullet or stay where you are.
Also, I had trouble flashing Magisk 15.3 with codeworkx recovery. Worked fine with bluspark.
Click to expand...
Click to collapse
Do you think its worth the jump? Are you seeing better battery life or any other improvements?
SysAdmNj said:
Do you think its worth the jump? Are you seeing better battery life or any other improvements?
Click to expand...
Click to collapse
It feels a bit faster, but I used to run Boeffla Kernel with battery optimized interactive governor on Nougat. So that's probably why.
As for battery, I don't really see a big improvement.
The biggest benefit was a clean system and internal storage. Don't even have face unlock, so can't comment on that.
I am happy with oreo!
Magisk
xposed framework sdk26 v90beta1
greenify + boost
Hi there, I have an Axon 7 with LineageOS that was working like a charm until I rebooted it today. It was in the normal lineage OS boot animation with the blue circle moving from right to left, except it never stopped. Now after trying a few more times, it just keeps playing the animation except the phone will vibrate slightly every several seconds. The phone is encrypted but that hasn't been a problem. When I reboot to TWRP, it says Unable to mount storage.
I tried wiping Cache and Dalvik / ART Cache, but this didn't help. Finally, I do have a backup from 7-20-2017 but I'd rather not have to go back to that...
Any recommendations?
Chrono7x said:
Hi there, I have an Axon 7 with LineageOS that was working like a charm until I rebooted it today. It was in the normal lineage OS boot animation with the blue circle moving from right to left, except it never stopped. Now after trying a few more times, it just keeps playing the animation except the phone will vibrate slightly every several seconds. The phone is encrypted but that hasn't been a problem. When I reboot to TWRP, it says Unable to mount storage.
I tried wiping Cache and Dalvik / ART Cache, but this didn't help. Finally, I do have a backup from 7-20-2017 but I'd rather not have to go back to that...
Any recommendations?
Click to expand...
Click to collapse
So you can't see the internal storage from TWRP? I'm guessing encryption actually plays a part here. Formatting data is probably the best course of action, though you should flash magisk or superSu if you do, to get rid of encryption. But you obviously lose everything that's on the internal storage.
Maybe make a system and boot backup and clean flash Lineage. Like, wipe system and caches, then flash the bootloader, modem, LOS and whatever else you flash
Choose an username... said:
So you can't see the internal storage from TWRP? I'm guessing encryption actually plays a part here. Formatting data is probably the best course of action, though you should flash magisk or superSu if you do, to get rid of encryption. But you obviously lose everything that's on the internal storage.
Maybe make a system and boot backup and clean flash Lineage. Like, wipe system and caches, then flash the bootloader, modem, LOS and whatever else you flash
Click to expand...
Click to collapse
Is it easier to just use the backup I have currently? If so, what are the steps necessary for that (sorry for newb questions, haven't messed with it in a while)
EDIT: Also, TWRP claims decryption is successful when it is loading up.
Chrono7x said:
Is it easier to just use the backup I have currently? If so, what are the steps necessary for that (sorry for newb questions, haven't messed with it in a while)
EDIT: Also, TWRP claims decryption is successful when it is loading up.
Click to expand...
Click to collapse
Again. Can you see the internal storage?
Don't restore the backup. Your problem is basically either on /system (clean flash of the ROM will do) or on /data (complete format of data is needed). So try the non destructive one first
Choose an username... said:
Again. Can you see the internal storage?
Don't restore the backup. Your problem is basically either on /system (clean flash of the ROM will do) or on /data (complete format of data is needed). So try the non destructive one first
Click to expand...
Click to collapse
I don't see any storage folder. So if I want to install the latest LOS and frankly just start from scratch, can I follow the guide here https://wiki.lineageos.org/devices/axon7/install#installing-lineageos-from-recovery starting from "Installing LineageOS from recovery"? Will I still need to install something to wipe the encryption?
Chrono7x said:
I don't see any storage folder. So if I want to install the latest LOS and frankly just start from scratch, can I follow the guide here https://wiki.lineageos.org/devices/axon7/install#installing-lineageos-from-recovery starting from "Installing LineageOS from recovery"? Will I still need to install something to wipe the encryption?
Click to expand...
Click to collapse
What? No... That's for normal phones. How did you manage to install LOS without knowing that you need the univ. bootloader and modem?
So, you can't access the internal storage via the file manager on TWRP i'm guessing.
Wipe - Format data, after that flash the Universal bootloader, modem, LOS, Magisk, GApps. Magisk takes care of dm-verity and disables encryption. Don't try to uninstall it though or your internal storage will get encrypted as soon as you do. But if you want to change ROMs you can just fpash it before booting and it won't ger encrypted.