Hi guys I'm about to blow my brains out, I've gone through so many guides and nothing has worked to help me with this catch-22 like loop I'm in. Any help would be most appreciated.
So I want to install a custom ROM, but to do that I need to decrypt my phone's storage, right?
So TWRP is giving me an error that my password is invalid even though it is the correct password (when trying to decrypt on TWRP recovery startup.
So I format data to fix that, but if I format data then I lose ROOT access.
I can mount the zip fine after I format data, but if I try to install the ZIP I get ERROR 255, which I found is related to not having root.
If I go and reboot into my stock boot, everything's wiped obviously so I need to re-install magisk to grant superuser/root access. But in doing that it RE ENCRYPTS EVERYTHING, DELETES HAVOCOS's ZIP, and basically I'm back at square one if I try to reboot into recovery and decrpyt everything???
What the heck am I missing here? Surely it has to be possible and I'm missing something simple? Please?
If it wasn't already clear, OEM is unlocked as well as USB debugging. I can boot into bootloader and have no trouble flashing imgs.
I have been trying to do this for 3 days now to no avail. I will not give up, but I could really use assistance.
Related
Hello
Really bad morning.
Woke up to find my OPO (was running COS 12.1 with TWRP), which I had plugged in to charge overnight, stuck on an android screen which said please enter your password. I entered my Google account password and then the next screen says, decryption unsuccessful. "Your password is correct but your data is corrupted. You need to factory reset your device and once you reboot you will have an opportunity to retrieve data backed up with your Google account".
I tried to reboot, just to make sure, and the same set of screens reappeared.
I tried to boot into recovery. The 'teamwin' screen kept flashing to no avail.
Entered fastboot. Flashed recovery, TWRP-2.8.7.0-bacon.
Tried to factory reset but the prompt flashed an error as follows:
'E: Could not mount /data and unable to find crypto footer' and then a series of others, but " could not mount '/data' " was repeated over and over
I'm still stuck here. How to get out of this situation?
PS: When I try to look at the mount options in recovery, the internal storage is labelled as 0 MB. This is scary.
I'm more screwed than you are. Twrp 2870 does not properly support encryption. Great to know an official release is that broken, right? Flash an older twrp, I believe 2860 or 61 are what you want. Try to reflash your cm zip. You're going to have to resetup your device but your internal sd should be fine, it says 0 mb because it's not decrypted so it can't read it. Then you should be okay... Well, except I've never seen that screen you described in the first paragraph. But that usually related to apps, not your internal sd. Good luck. I've accidentally erased all my system and data so I can't adb flash and can't flash from internal sd. My last hope before reformating everything and losing my pictures is to install via USB OTG. Which you could also do.
Good luck
Sent from my Nexus 5 using Tapatalk
Hey, I just found out that there is a way to flash a system image via fastboot! This is why I buy unlocked developer minded phones! If only OP hadn't dropped the ball on the OP2 (I actually got an invite which I didn't even use).
Anyway, go here: https://forums.oneplus.net/threads/...lashing-recovery-roms-kernels-rooting.291274/
and scroll down to "The Bad" In ORANGE text: 2. Recovering from no OS installed and no access to TWRP, fastboot does work.
Since TWRP is basically useless for us, I followed the instructions. I flashed everything EXCEPT the userdata img. AND, instead of flashing the extracted recovery, I just reflashed TWRP 2861 which I have on the PC.
Unfortunately! All my pics are gone. Pretty sure removing encryption with TWRP (before reading it was broken) did it. Try installing a good ROM via USB OTG and let me know if that saves your internal sd. I'd love to know for the future.
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So, I have years of experience rooting and flashing Samsung phones with minimal adb experience. My buddy from work asks me if I can try to fix his shield tab that he F'd up trying to flash a rom on. Come to find out he never unlocked the bootloader or flashed a recovery or rooted the dang thing, just tried to flash the rom over stock like a numbskull. We thought it was dead forever because the only thing that would mount or connect in adb was the side load through the stock recovery. So, I finally got it to connect to fastboot (don't ask me how, I don't know), unlocked the bootloader, and flashed twrp. Now it won't flash supersu in adb sideload, so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent even though it says "success" at the top after flashing. I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so, which one? I have no idea which version bootloader, kernel, or os is, or was, on this device, I'm not familiar with any of the roms for it, and I'm not sure what prerequisites there may be for some of them....
Thanks for the help!
rom fiend said:
it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent even though it says "success" at the top after flashing. I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so, which one?
Click to expand...
Click to collapse
I had the same Problem with the partitions you discribed, have tried wipe them, change the file format and change it back?
I flashed a lot of Roms from the external SD Card and it worked every time.
I think you should go with Bliss Rom. ( Just try Lollipop and Marshmallow)
OverBit said:
I had the same Problem with the partitions you discribed, have tried wipe them, change the file format and change it back?
I flashed a lot of Roms from the external SD Card and it worked every time.
I think you should go with Bliss Rom. ( Just try Lollipop and Marshmallow)
Click to expand...
Click to collapse
I can't wipe them because they won't mount. It's as if the partitions were erased completely. Not like the partitions were wiped, but like they don't exist at all anymore...
What do you mean by changing the file format? Format of what?
rom fiend said:
What do you mean by changing the file format? Format of what?
Click to expand...
Click to collapse
TWRP, wipe ,Advanced wipe
If that doesn't work just try installing a rom, boot it
If that doesn't work try this
Tried all recovery options and tried flashing bliss 6.2 with no luck. It says that it flashes successfully but also shows some errors about not being able to mount the system and data partitions. Then when I try to reboot it gets stuck at the nvidia logo (this is the closest that I've gotten to booting a rom). I can provide pictures if you want. I'm going to try the steps that you linked to as soon as the files download.
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password
#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though
Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!
#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?
you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.
I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine
Hi Guys
Okay so i managed to boot into twrp via fastboot/cmd
After wiping cache/Davlik and data, i cant seem to flash stock rom or custom rom. Im getting something about SUPER and needing to boot into recovery again etc However after flashing recovery, it just takes me to the screen showing the bootloader unlock screen.
is there something im doing wrong? or have i deleted something by accident etc
says devices on super may not mount until rebooting recovery. to flash additional zips, please reboot recovery to switch to the updated slot
any idea?
i would really appreciate any sort of assistance
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
sergio-bodyweb said:
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
Click to expand...
Click to collapse
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
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...
forum.xda-developers.com
plegdroid said:
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
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...
forum.xda-developers.com
Click to expand...
Click to collapse
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
plegdroid said:
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
Click to expand...
Click to collapse
Of course, thx.