Database Develop

I need help. My 3T has no OS and won't mount data partition in twrp.

I guess I wasn't paying close enough attention and I tried installing the 7.0 update from this thread.
I can now only get to TWRP recovery and fastboot. When I'm in TWRP my internal storage says 0MB and it won't let me mount the data partition. Flashing anything fails.

Fastboot format userdata

flammenwurfer said:
I guess I wasn't paying close enough attention and I tried installing the 7.0 update from this thread.
I can now only get to TWRP recovery and fastboot. When I'm in TWRP my internal storage says 0MB and it won't let me mount the data partition. Flashing anything fails.
Click to expand...
Click to collapse
Flash the stock recovery through fastboot. You can use the toolkit found here on xda forums.

Also you can format data in TWRP and then it should work, but you lose everything in internal storage, pics, music, all your own stuff.

Thanks guys. I got the stock recovery installed and it wiped everything, which was fine. I already backed up important stuff. It seems the update went through because I have Nougat now. But I'm having trouble installing any other roms. It wants to decrypt but it doesn't work. I read on the TWRP post that you can set a boot password and it would update the crypto key type or something and it should work after that. Well I did that, but twrp still won't accept my password and let me flash anything.

flammenwurfer said:
Thanks guys. I got the stock recovery installed and it wiped everything, which was fine. I already backed up important stuff. It seems the update went through because I have Nougat now. But I'm having trouble installing any other roms. It wants to decrypt but it doesn't work. I read on the TWRP post that you can set a boot password and it would update the crypto key type or something and it should work after that. Well I did that, but twrp still won't accept my password and let me flash anything.
Click to expand...
Click to collapse
I had the same problem. I used the 3T toolkit to force decrypt (Option 14). This worked for me.

kinfam said:
I had the same problem. I used the 3T toolkit to force decrypt (Option 14). This worked for me.
Click to expand...
Click to collapse
I just did this and it worked in TWRP: I was able to create a backup (which is not possbible in password-bugged state) and then I noticed I still was not able to mount the USB partition and thought I had to boot in to OOS once, so I did it, set up the bare minimum and then checked back at TWRP and voilà: Locked again.
The OOS said "encrypted" as well after I booted it.
I was (am) running 7.0, TWRP, non rooted (because I freaking can't)
Anynone can help here?

Nobody121 said:
I just did this and it worked in TWRP: I was able to create a backup (which is not possbible in password-bugged state) and then I noticed I still was not able to mount the USB partition and thought I had to boot in to OOS once, so I did it, set up the bare minimum and then checked back at TWRP and voilà: Locked again.
The OOS said "encrypted" as well after I booted it.
I was (am) running 7.0, TWRP, non rooted (because I freaking can't)
Anynone can help here?
Click to expand...
Click to collapse
Did you flash SuperSU before booting into OOS? Not sure what to tell you I did the Force Decrypt then went into TWRP and immediately flashed SuperSU.

kinfam said:
Did you flash SuperSU before booting into OOS? Not sure what to tell you I did the Force Decrypt then went into TWRP and immediately flashed SuperSU.
Click to expand...
Click to collapse
I wanted to do so but was not able to because I was not able to mount the relevant partition, nvm though I think I`ll wait a day or two to see if TW releases a new build. Thanks anyways:good:

Nobody121 said:
I wanted to do so but was not able to because I was not able to mount the relevant partition, nvm though I think I`ll wait a day or two to see if TW releases a new build. Thanks anyways:good:
Click to expand...
Click to collapse
,Using the toolkit take the option 14....To push decryption..,
DONT boot to your ROM...With the toolkit push the SuperSU and then flash it...
Now you can boot to your ROM....
If you boot without SuperSU will reenforse encryption.....

cultofluna said:
,Using the toolkit take the option 14....To push decryption..,
DONT boot to your ROM...With the toolkit push the SuperSU and then flash it...
Now you can boot to your ROM....
If you boot without SuperSU will reenforse encryption.....
Click to expand...
Click to collapse
Push with adb sideload? Because I was not able to get that going for me. ADB is installed on my PC. Also is there a way to backup my apps and data without root? I just set everything up. Thanks for the help

Nobody121 said:
Push with adb sideload? Because I was not able to get that going for me. ADB is installed on my PC. Also is there a way to backup my apps and data without root? I just set everything up. Thanks for the help
Click to expand...
Click to collapse
Options 1 and 2 on the toolkit is backup and restore apps and data..

cultofluna said:
Options 1 and 2 on the toolkit is backup and restore apps and data..
Click to expand...
Click to collapse
Nice haha, Ill try it later. Thank you really much

So there is currently no way to root and use TWRP without completely disabling encryption?

I'm having the same issues as the OP here. Whenever I go to use the toolkit it says "the system cannot find the path specified." Any ideas? I've tried within Android and in TWRP..
Sent from my ONEPLUS A3000 using Tapatalk

phone not passing twrp splashscreen

I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please

Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.

Anova's Origin said:
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Click to expand...
Click to collapse
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?

ddaharu said:
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
Click to expand...
Click to collapse
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.

Anova's Origin said:
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Click to expand...
Click to collapse
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...

ddaharu said:
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
Click to expand...
Click to collapse
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img

Anova's Origin said:
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Click to expand...
Click to collapse
One last question. Is there any twrp version you'll recommend? Or anyone is good?

ddaharu said:
One last question. Is there any twrp version you'll recommend? Or anyone is good?
Click to expand...
Click to collapse
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.

Anova's Origin said:
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Click to expand...
Click to collapse
MY PHONE IS RUNNING AGAIN! thanks for your help man.
Btw! Seeing that the positions were somewhat corrupted, I actually had to use stock recovery to sideload the stock ROM then flash TWRP and finally on freedom is 2.6.1
Thanks again, mate. :highfive:

ddaharu said:
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Click to expand...
Click to collapse
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that

9891ishu said:
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
Click to expand...
Click to collapse
Thanks. I got through.

[Solved / Fixed ]Cannot decrypt the phone after flashing the flyme build

Hi ,
I am not a noob, but yesterday out of curiosity flashed the flyme build in the unified section. However, after the TWRP reboot to system, it did not boot. So tried to reboot the recovery and success. But the villian was there, encryption password. I tried giving my phone PIN, it said wrong password.
After half an hour, i installed the stock image(3.5.1) using the msm tool. Well it booted fine and phone is usable. Unlocked the bootloader and flashed the latest TWRP,.
The villian is back, asking for password. Now it is taking any password, always say wrong password. Ok in case i skip the decrypt screen, i cannot access the sdcard to flash new rom.
Is this the end of story of my op3t?

Have you tried "default_password"?

Didgeridoohan said:
Have you tried "default_password"?
Click to expand...
Click to collapse
Tried everything. The phone boots into OOS 3.5.1 after msm tool flash without password. Even it behaves very well. Only after the TWRP installation. It is stuck for password. I think its end of story.

Prashanthme said:
Tried everything. The phone boots into OOS 3.5.1 after msm tool flash without password. Even it behaves very well. Only after the TWRP installation. It is stuck for password. I think its end of story.
Click to expand...
Click to collapse
Then I don't know... Usually if TWRP suddenly starts asking for a password without having set one, using "default_password" will work.
You could try flashing a kernel that disables forced encryption and then format data to unencrypt.

You have to make sure to restore system to the version using the same encryption libraries as used the last time you could decrypt the data partition. If all fails you will have to format your data partition and loose it all.

pitrus- said:
You have to make sure to restore system to the version using the same encryption libraries as used the last time you could decrypt the data partition. If all fails you will have to format your data partition and loose it all.
Click to expand...
Click to collapse
I have already lost the data. TWRP not allowing me to enter the sdcard storage to flash anything. Can u brief me how to format the data partition.

Just bootup phone into fastboot mode from the unlocked bootloader menu, then connect to PC and run "fastboot format userdata" from a path with either fastboot in or anywhere of you've added the folder with fastboot in you PATH variable.

pitrus- said:
Just bootup phone into fastboot mode from the unlocked bootloader menu, then connect to PC and run "fastboot format userdata" from a path with either fastboot in or anywhere of you've added the folder with fastboot in you PATH variable.
Click to expand...
Click to collapse
Did this. But after should i flash the stock image again? Because system is not booting and stuck in oneplus logo.
How about fastboot erase options?

I disabled encryption one year ago to avoid this problem, and therefore have never experienced it. But why don't you do a compete MSM restore? That should restore even the data partition.

pitrus- said:
I disabled encryption one year ago to avoid this problem, and therefore have never experienced it. But why don't you do a compete MSM restore? That should restore even the data partition.
Click to expand...
Click to collapse
Let me try once i go home and update u. Thanks for the response..
Will format the data from fastboot. and flash the stock image. Hope this works.

Finally happened to work.
Installed a different version twrp made the trick. But this time i erased the recovery and flashed again. After that wiped all the data and then sideloaded the rom from adb and it did the trick..

pitrus- said:
I disabled encryption one year ago to avoid this problem, and therefore have never experienced it. But why don't you do a compete MSM restore? That should restore even the data partition.
Click to expand...
Click to collapse
Can you please tell me how you disabled encryption?

Vidicgapi said:
Can you please tell me how you disabled encryption?
Click to expand...
Click to collapse
You do this by flashing the latest no-verity-opt-encrypt zip file after formatting the data partition and also after each update of the OS.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip

data decryption error

Hello, I installed AOSIP, everything works great but into twrp I can't decrypt data...
I've tried twrp R2.3.2.1 and R2.3.2.5, it says wrong password... I use the pin code of the ROM...
What can I do?

lcarolo said:
Hello, I installed AOSIP, everything works great but into twrp I can't decrypt data...
I've tried twrp R2.3.2.1 and R2.3.2.5, it says wrong password... I use the pin code of the ROM...
What can I do?
Click to expand...
Click to collapse
Hey, the same is happening to me since today, i'm looking why but i can't find the reason its drivin' me crazy i can't setup encryption...
edit : couldn't achieve to unlock TWRP with a custom ROM encryption, stock ROM encryption with MIUI is working fine tho... If someone has any infos

lcarolo said:
Hello, I installed AOSIP, everything works great but into twrp I can't decrypt data...
I've tried twrp R2.3.2.1 and R2.3.2.5, it says wrong password... I use the pin code of the ROM...
What can I do?
Click to expand...
Click to collapse
@Displayer
Your data from the last install appears to be encrypted. If you have a backup the easiest way to resolve the issue is to format your storage. You could also use the All in One tool and use its encryption removal option. Please keep in mind that it will wipe out all of your memes, so hopefully those are backed up.

tsongming said:
@Displayer
Your data from the last install appears to be encrypted. If you have a backup the easiest way to resolve the issue is to format your storage. You could also use the All in One tool and use its encryption removal option. Please keep in mind that it will wipe out all of your memes, so hopefully those are backed up.
Click to expand...
Click to collapse
I mean, i formatted to have a custom ROM booting, encrypting my data. I can use the phone, my pin code works in android but it's impossible to decrypt with TWRP...
Édit : found that message from argraur on telegram, so basically we have to wait for an updated twrp ? "Android release 9.0.0_r36 (r37) with May security patch has updated FBE encryption that breaks decryption in TWRP."

Displayer said:
I mean, i formatted to have a custom ROM booting, encrypting my data. I can use the phone, my pin code works in android but it's impossible to decrypt with TWRP...
Édit : found that message from argraur on telegram, so basically we have to wait for an updated twrp ? "Android release 9.0.0_r36 (r37) with May security patch has updated FBE encryption that breaks decryption in TWRP."
Click to expand...
Click to collapse
That doesn't even make sense. Twrp will not decrypt your phone.
Install Miui again, backup your data, to your desktop, by manually dragging your files over.
Go here and download DM-VERITY, FORCED ENCRYPTION, AND DISC QUOTA DISABLER you will use it to flash between updates or for dirty flashing Miui updates.
Next go back to TWRP the choose format and type yes reboot to TWRP ( you will se a message that says you have no OS are you sure?) Yes, reboot to TWRP
TWRP is not your issue, go read
and read the first comment here
Format storage, or wait for the TWRP and you still need to the format storage, Again a TWRP update will not resolve the issue. We have all had this exact issue.

I'm using another workaround:
With the all in one tool, we can flash .zip from a PC.
So I could install a custom kernel file from my pc directly into phone without loosing data.
Annoying thing is that I need the PC... Can't flash files that are in phone memory... Not such a big issue...
Another question, can I make a backup from the PC? Used to do it via twrp, but it is not safe with that issue...

lcarolo said:
I'm using another workaround:
With the all in one tool, we can flash .zip from a PC.
So I could install a custom kernel file from my pc directly into phone without loosing data.
Annoying thing is that I need the PC... Can't flash files that are in phone memory... Not such a big issue...
Another question, can I make a backup from the PC? Used to do it via twrp, but it is not safe with that issue...
Click to expand...
Click to collapse
Today i found a TWRP with decryption for may patch working for me here : https://forum.xda-developers.com/mi-8/development/recovery-unofficial-twrp-recovery-t3893823
I think u can pull img if i remember well but now its working for me

Displayer said:
Today i found a TWRP with decryption for may patch working for me here : https://forum.xda-developers.com/mi-8/development/recovery-unofficial-twrp-recovery-t3893823
I think u can pull img if i remember well but now its working for me
Click to expand...
Click to collapse
This twrp is working! Thanks a lot!

Question Still encryption

TWRP 3.6.2 not work for decrypt a12

ZAHIDx said:
TWRP 3.6.2 not work for decrypt a12
Click to expand...
Click to collapse
For encryption just remove lock screen security and reboot.
TWRP A12
https://androidfilehost.com/?w=files&flid=321666

NOSS8 said:
For encryption just remove lock screen security and reboot.
TWRP A12
https://androidfilehost.com/?w=files&flid=321666
Click to expand...
Click to collapse
That's correct, but in my case I'm running EliteROM wich is decrypted by default, if I want to backup my system with TWRP-3.6.2 the super partition shows "zero MB" even without any lockscreen option... not like in OFox where it shows the real partition size... So, the backup will be done without system or super-partition. Am I right? Thank you.

Hellera said:
That's correct, but in my case I'm running EliteROM wich is decrypted by default, if I want to backup my system with TWRP-3.6.2 the super partition shows "zero MB" even without any lockscreen option... not like in OFox where it shows the real partition size... So, the backup will be done without system or super-partition. Am I right? Thank you.
Click to expand...
Click to collapse
Sure, but full restores with TWRP or O.F tend to work only on the same rom (when it works).
You can use Mi cloud on PC or PHONE eventually MI phone assistant.(data only).

NOSS8 said:
Sure, but full restores with TWRP or O.F tend to work only on the same rom (when it works).
You can use Mi cloud on PC or PHONE eventually MI phone assistant.(data only).
Click to expand...
Click to collapse
I'm testing almost every rom I found... with OFOX I can restore my entire system every time.... I'm not sure the same with TWRP, and I think the reason is android 12. With android 11 every recovery image works fine.

NOSS8 said:
For encryption just remove lock screen security and reboot.
TWRP A12
https://androidfilehost.com/?w=files&flid=321666
Click to expand...
Click to collapse
It did not work, which of the links you give will be good for my ROM?

ZAHIDx said:
It did not work, which of the links you give will be good for my ROM?
Click to expand...
Click to collapse
There are several trying the last one but removing the security from the lock screen is fine.
Your rom is in A12 so yes,phone code name SWEET. (but some TWRP are not yet 100% functional).
What do you want to do with the twrp?

NOSS8 said:
There are several trying the last one but removing the security from the lock screen is fine.
Your rom is in A12 so yes,phone code name SWEET. (but some TWRP are not yet 100% functional).
What do you want to do with the twrp?
Click to expand...
Click to collapse
I am willing to go with any recovery, which can decrypt my ROM

ZAHIDx said:
I am willing to go with any recovery, which can decrypt my ROM
Click to expand...
Click to collapse
ok,but for what to do?

NOSS8 said:
ok,but for what to do?
Click to expand...
Click to collapse
Can I go to any ROM in this situation? Because my partition cannot be wiped

ZAHIDx said:
Can I go to any ROM in this situation? Because my partition cannot be wiped
Click to expand...
Click to collapse
For AOSP rom or Custom Miui roms,first installation requires to format data not just wipe.
Again remove lock screen security and with the TWRP:
If the TWRP ask to "enter password for the user" just select cancel.
Wipe/format data type yes reboot TWRP.(if errors red lines restart the procedure).
rebooting to the TWRP on each try.