So I was able to successfully encrypt my phone (kenzo) on CM13 10/10 Nightly. Everything is working fine, phone asks for my PW on boot, etc. However, if I reboot to recovery, TWRP cannot decrypt my partition, even when given the proper password. I even changed my password on my device, rebooted to confirm that the new password successfully decrypted my phone, yet it still does not work in TWRP. Can anyone tell me what I need to do to get TWRP to be able to access my partitions?
Thanks!
How did you Encrypted your Kenzo? I've tried it before, but phone just restarts...
Are you using official CM or Santosh?
fcsprovenzano said:
How did you Encrypted your Kenzo? I've tried it before, but phone just restarts...
Are you using official CM or Santosh?
Click to expand...
Click to collapse
Official CM13. 10/10 Nightly. I just selected the encryption option and it worked. Only problem is this twrp issue.
Which twrp version are you using? It looks like a known problem with some versions.
http://forum.xda-developers.com/showthread.php?t=3286287
Sent from my Redmi Note 3 using Tapatalk
purple.epod said:
So I was able to successfully encrypt my phone (kenzo) on CM13 10/10 Nightly. Everything is working fine, phone asks for my PW on boot, etc. However, if I reboot to recovery, TWRP cannot decrypt my partition, even when given the proper password. I even changed my password on my device, rebooted to confirm that the new password successfully decrypted my phone, yet it still does not work in TWRP. Can anyone tell me what I need to do to get TWRP to be able to access my partitions?
Thanks!
Click to expand...
Click to collapse
i have the same problem, even if u give wrong password during boot of cm it will show password is correct. when i rebooted to recovery it was stucked in twrp logo
Just tried encrypting on latest nightly (15 Oct) and unfortunately it did not work for me. I have the firmware flashed from http://forum.xda-developers.com/showpost.php?p=68023154&postcount=2
Which firmware do you have flashed?
I'm having the same problem too. I finally resolved to switch back to CM and tried to encrypt but it is not working on 15 October nightly.
Sent from my Redmi Note 3 using Tapatalk
Have you tried ZCX TWRP @purple.epod ? http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
I'm trying to encrypt on 10/10 but it is not working.
fcsprovenzano said:
Have you tried ZCX TWRP @purple.epod ? http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
I'm trying to encrypt on 10/10 but it is not working.
Click to expand...
Click to collapse
I have not, it seems to be made for phones with MIUI and I've been using CM13 since the first day I got the device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have been using FlashFire to upgrade my CM nightlies, as TWRP isn't decrypting properly.
I'm not using Radon Kernel. I will test it.
Is everything working correctly with Radon and CM13?
In twrp, go to wipe, format data partition to ext4, solved.
jujusito said:
In twrp, go to wipe, format data partition to ext4, solved.
Click to expand...
Click to collapse
My /data partition is ext4 already.
fcsprovenzano said:
I'm not using Radon Kernel. I will test it.
Is everything working correctly with Radon and CM13?
Click to expand...
Click to collapse
Yeah, all hardware is working properly. No issues.
I tested Radon Kernel but my flashlight stopped working and I returned to original kernel.
Sent from my Redmi Note 3 using Tapatalk
Related
Hi,
so recently i wanted to restore stock kernel and that's why I used MiFlash.
I did it, but now the problem is that there's something wrong with the phone.
I have TWRP installed, but the phone doesn't work right.
After it boots up eventually (after few soft reboots) I can't do anything.
On MIUI ROM i can't get past the configuration menu as it requires a SIM card or wifi to activate, where both don't work.
Now I've got AOSP 5.1.1 on the phone, but there's the same problem. Also most of the apps aren't working, such as settings, phone etc.
After few minutes the phone reboots by itself.
Any idea how to fix it?
Edit: I've fixed wifi and reboots. The only thing that is not working is Sim card. No imei and baseband is detected (probably wiped efs).
You flashed CM13 or any other MM rom?
Aadeep said:
You flashed CM13 or any other MM rom?
Click to expand...
Click to collapse
Yeah, I flashed AOKP based on MM (CM kernel - didn't lock the bootloader).
But few things didn't work and I wanted to get back to 5.1.1
Edit: I guess I've lost my IMEI semehow, right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mr.loverlover said:
Yeah, I flashed AOKP based on MM (CM kernel - didn't lock the bootloader).
But few things didn't work and I wanted to get back to 5.1.1
Edit: I guess I've lost my IMEI semehow, right?
Click to expand...
Click to collapse
Yes imei is lost, you can only flash MM based ROMs now (if you didn't backup efs of lollipop)
try this if u had previous lollipop backup https://youtu.be/I-3sVZAEXjQ
I've managed to fix wifi somehow.
kaushal64 said:
try this if u had previous lollipop backup https://youtu.be/I-3sVZAEXjQ
Click to expand...
Click to collapse
Unfortunatelly I had a backup but of an AOSP 5.1.1 and there were only 4 partitions backed up
Aadeep said:
Yes imei is lost, you can only flash MM based ROMs now (if you didn't backup efs of lollipop)
Click to expand...
Click to collapse
MM also doesn't get any signal.
Try this
http://en.miui.com/thread-233047-1-1.html
http://en.miui.com/thread-260943-1-1.html
arnes_king said:
Try this
http://en.miui.com/thread-233047-1-1.html
http://en.miui.com/thread-260943-1-1.html
Click to expand...
Click to collapse
1st option is a no do.
It's a new phone on warranty.
2nd option. I already tried it. Doesn't work
Btw, could someone please upload his /dev/block/ folder?
Sent from Note 3, Xiaomi Redmi Note 3.
http://forum.xda-developers.com/redmi-note-3/how-to/how-to-restore-lost-redmi-note-3-pro-t3401622
Flash qcn before xqcn
vkass said:
http://forum.xda-developers.com/redmi-note-3/how-to/how-to-restore-lost-redmi-note-3-pro-t3401622
Flash qcn before xqcn
Click to expand...
Click to collapse
The link doesn't work.
Sent from Note 3, Xiaomi Redmi Note 3.
hi the second one worked for me
just download the last version of qpst here 2.7 build 425
mr.loverlover said:
1st option is a no do.
It's a new phone on warranty.
2nd option. I already tried it. Doesn't work
Btw, could someone please upload his /dev/block/ folder?
Sent from Note 3, Xiaomi Redmi Note 3.
Click to expand...
Click to collapse
I can't believe it.
I fixed it.
The key to restoring imei was the qcn file, which was currupted in my phone.
I used this one (without editing hex): https://app.box.com/s/6mwo0n8qhi1nmmnpz0hrbmmqy0jyszr4
Try this
1.)Flash CM13 again.
2.)Unlock bootloader.
3.)Flash fastboot rom via miflash in fastboot rom.
kaushal64 said:
Try this
1.)Flash CM13 again.
2.)Unlock bootloader.
3.)Flash fastboot rom via miflash in fastboot rom.
Click to expand...
Click to collapse
I already fixed it with the method mentioned above.
Sent from Note 3, Xiaomi Redmi Note 3.
PitchBlack Recovery for Xiaomi Poco F1 (beryllium)
Info
PitchBlack v2.9.0 Official
Based on TWRP 3.2.3
Update Log :
- initial official build
Maintainer @androiabledroid
Download
https://sourceforge.net/projects/pi...ium-2.9.0-20181225-0547-OFFICIAL.zip/download
Channel : @PBTwrp
Chat : @pbrpcom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my POCO F1 using Tapatalk
Only need flash in twrp?
matheus_sc said:
Only need flash in twrp?
Click to expand...
Click to collapse
Yes choose image
Asking for password, Internal storage showing 0mb, need decryption support.
Yes Download the zip and flash through TWRP as usually on your existing twrp.
matheus_sc said:
Only need flash in twrp?
Click to expand...
Click to collapse
Sent from my POCO F1 using Tapatalk
Goto wipe section format your internal storage by typing "yes''
Mohan0004 said:
Asking for password, Internal storage showing 0mb, need decryption support.
Click to expand...
Click to collapse
Sent from my POCO F1 using Tapatalk
There are still touch lags / freeze. Never faced in the recent TWRP by Vasishath build.
Please update this recovery based on the latest official TWRP because it can successfully decrypt encrypted data partition on miui roms but latest pitch black can't. ?
Noor9933 said:
Goto wipe section format your internal storage by typing "yes''
Sent from my POCO F1 using Tapatalk
Click to expand...
Click to collapse
That's not a solution, what about if you don't want to wipe your phone and start fresh?
Skinpipe said:
That's not a solution, what about if you don't want to wipe your phone and start fresh?
Click to expand...
Click to collapse
Still being worked on (Pie decryption is different than Oreo).
plz.... update recent TWRP by Vasishath build based...
official twrp some problem
Does this support Aroma Installers?
Check out the latest version!
I am more than just surprised that why is this great recovery going unnoticed in our XDA!
https://sourceforge.net/projects/pitchblack-twrp/files/beryllium/
Right now this is the latest recovery with no bugs (my personal test, encryption decryption working great in android 10)...:good:
Definitely check out...!
Using 11 March 2020 build
Please tell me is this everything working fine
Rajeshrajkhaju said:
Please tell me is this everything working fine
Click to expand...
Click to collapse
Yes bro... everything
Awesome recovery, no bugs, smooth and clean
i just found this ! is everything working great for the latest update ? (android 10)
timmy6 said:
i just found this ! is everything working great for the latest update ? (android 10)
Click to expand...
Click to collapse
Thanks for heads up on the new version (28/7/2020). Best recovery, no issues since April.
Deleted
There are plenty of better recoveries than the old non updated twrp? I personally use the latest orangefox recovery V11. It's good to see that the development is still alive on poco ?
My phone recently I have done a flash rom as usual, but all the problems started from this point. I miss miui 9 because it's stable and fast. I have downloaded the 9.5 mui flash on the OrangeFox Twrp. After that, I waited a long time. But the flash did not finish for a time I can't wait to do so. Press and hold the button to turn on twrp again and get back to miui 10 again. Yes, it's done.
And after that I started to flash my rom again because I broke my rom
I have to format
Now I can't flash any rom.
Most messages have failed to mount system or failed to mount data and are usually accompanied by error 7 while the flash rom
My friends told me to change twrp.
I try
twrp-3.2.3-0-vince
OrangeFox R9
OrangeFox R8.3-unified
PitchBlack
All are the latest versions. As far as I can find Of course, I can't solve the problem.
And I tried to edit the text in updater-script Which still does not work
And I have tried using MiFlash
MiFlash is used. I can go to Rom Dev, but I can not go to magisk. It caused me to bootloop and I made a flash. lazyflasher-no-verity-opt-encrypt But still not working
I have been using MiFlash continuously. Sometimes I wait 300 seconds and finish, but the cause of Bootloop is unknown or sometimes shows the system has been destroyed.
MiFlash. Maybe I use it. I waited more than 300 seconds until 1500 seconds. Nothing happened. I continued to do this and successfully, but not three cars. I did not have to go to the magisk as usual and caused Bootloop.
Lastly, I was able to use it, but my imei number is missing, so I can't use the SIM. I can format it to flash rom, but it's still not successful.
How should I solve this problem? Please help me I have tried many ways, please. :crying: :crying: :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was also having this problem, you need the twrp 3.2.3-1: https://drive.google.com/file/d/167Uoh8Zi7km6eGIZdg3PS9HDhi7a5W_d/view
I'm sorry for the strange English. I use google translate. Hope you guys understand my problem.
I will experiment with rom miui_HM5PlusGlobal_8.11.15_dd40bfa136_8.1_2
joelzombie said:
I was also having this problem, you need the twrp 3.2.3-1: https://drive.google.com/file/d/167Uoh8Zi7km6eGIZdg3PS9HDhi7a5W_d/view
Click to expand...
Click to collapse
It doesn't work
I experimented with miui_HM5PlusGlobal_8.11.15_dd40bfa136_8.1_2 and crDroidAndroid-8.1-20190221-vince-v4.7.2
As far my experience goes, looks like you messed up your partitions. Look for a tutorial to recreate partitions from scratch.
What do I have to do? Can you teach me
bot88 said:
As far my experience goes, looks like you messed up your partitions. Look for a tutorial to recreate partitions from scratch.
Click to expand...
Click to collapse
Now imei number is missing and the auto reboot symptoms have happened. And if I do root, it will cause bootloop symptoms
not6248 said:
Now imei number is missing and the auto reboot symptoms have happened. And if I do root, it will cause bootloop symptoms
Click to expand...
Click to collapse
Imei number missing means you lost efs partitions. This is the first partition to backup after installing custom recovery. These partition can also be backup by adb. sorry to say you messed up real bad,
And how do I have to solve
bot88 said:
Imei number missing means you lost efs partitions. This is the first partition to backup after installing custom recovery. These partition can also be backup by adb. sorry to say you messed up real bad,
Click to expand...
Click to collapse
I have no intelligence
not6248 said:
I have no intelligence
Click to expand...
Click to collapse
sorry bro, but i have no experience in this kind of situation.
but here is a link which may help https://xiaomifirmware.com/guides-and-tips/how-to-restore-redmi-5-plus-and-fix-bootloop/
There's one solution. Fastboot flash any miui rom then Use orange fox recovery. ?
Hi, I am a K20 Pro, China Variant (6,128GB) User wanna share a horrible experience that happened with me.
let's start from the beginning. I was trying AOSP based rom because I wanted to leave MIUI.
I was happy with Evox rom. Then One day I have found Corvus OS 7.5 review , comes with OSS Vendor.
So I have flashed Corvus with OSS Vendor it was really awesome. I have never experienced that much smoothness in k20 Pro.
Then I thought Lets try F1Xy kernel. Mistakenly I have flashed The LOS FOD and boom.
My Raphael stucked into OrangeFox Recovery. I have tried Flashing F1xy with Mi9 FOD , No help. Booting into Recovery.
I had Evox Backup, Tried restoring the Backup, the backup included everything, kernel, model bla bla bla.
But even after restoring my phone was booting into recovery.
Then I thought Lets clean flash.
I have clean flashed Xiaomi.EU rom, Evox, Corvus and guess what it was still booting into recovery only.
I have wiped internal too. No help. everytime I have flashed rom I have also flashed DFE and Magisk.
Then I have Flashed Latest MIUI fastboot rom using Mi Flash Tool.
Guess what Its still booting into recovery. This time stock Chinese recovery.
Then I have flashed official TWRP, XiaomiEU rom. And phone just booted .
Then I have seen only 32GB INTERNAL storage . I was like what the haak.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Than I have fixed the internal storage using this command.
if you are rooted, get a terminal app such as termux then:
1. su (press enter)
2. Press grant when asked
3. resize2fs /dev/block/bootdevice/by-name/userdata (press enter again)
or do this in recovery, but skip 1 and 2
Thanks Superuser1958 for helping me on this.
So what was wrong? why my phone was booting into recovery even after clean flash
i do think every oss does not support custom kernels and its the inly idea i can think of
I recieved two complaints from other users have the same experience but with PE rom.
I'm assuming its the f1xy kernel issue. (haven't been active enough to confirm.)(I could be completely wrong here)
Anyways, I'll let superuser1958 (tg username) aka @joshuah1971 (xda username) confirm.
glad you got it fixed. Is everything else working perfectly?
(and v190 is known to be broken, so anything other than that.)
If it's making modifications that survive a clean_all MiFlash that's worrying. Nothing should be messing with device partitions.
Something similar happened with a Magisk mod. "FDE AI" if I remember correctly. Irreversibly mangled some Mi9T/K20 handsets and wasn't fixed by clean_all.
I do wonder whether EDL would be more thorough in putting devices in a factory state - but it's locked off. Heck, I'm astonished that today's devices can still be screwed up.
phones partition was somehow fked up and i bet even developer of the kernel couldnt say how, as it didnt even booted after clean flash from miflash tool that author states. Something similar happened to me when i was experimenting with kernels on different roms on redmi note 7 , firstly i was not even able to mount any storage and didnt see any partitions then reduced its size by half and only edl saved the day. it was predator kernel when issues started.
need helpi too having same issue how to resolve this, stuck on with orange fox and in computer there are three internal storage showing up of 107gb
I'm using Xiaomi Redmi Note 9 Pro (Joyeuse). I don't think I bricked my phone because I can run TWRP, but surely something went wrong when I tried to change one custom ROM (Havoc OS 3.12) to another (crDroid v7.2). Now when I try to flash crDroid zip, this is what happens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It would be wonderful if someone could help me bring my phone back to life. I've only had it about two months.
zkosmosu said:
I'm using Xiaomi Redmi Note 9 Pro (Joyeuse). I don't think I bricked my phone because I can run TWRP, but surely something went wrong when I tried to change one custom ROM (Havoc OS 3.12) to another (crDroid v7.2). Now when I try to flash crDroid zip, this is what happens:
View attachment 5197369
It would be wonderful if someone could help me bring my phone back to life. I've only had it about two months.
Click to expand...
Click to collapse
Nothing get flashed, you can boot back in your previous rom.
Check if partition are not already mounted in TWRP and untick them.
You can also report your issue to the relevant crdroid topic in ROM/DEVforum.
zkosmosu said:
I'm using Xiaomi Redmi Note 9 Pro (Joyeuse). I don't think I bricked my phone because I can run TWRP, but surely something went wrong when I tried to change one custom ROM (Havoc OS 3.12) to another (crDroid v7.2). Now when I try to flash crDroid zip, this is what happens:
View attachment 5197369
It would be wonderful if someone could help me bring my phone back to life. I've only had it about two months.
Click to expand...
Click to collapse
Try orange fox recovery there you have the option to unmount system n vendor while flashing works fine.
Cheers
HELP! is there any work around? I flash havoc rom but its says the same ( updater process ended with ERROR 1 )
Same error can anybody help me out
It is showing me error as,
Failed to mount '/system_root' (invalid argument)
Failed to mount '/vendor' (invalid argument)
Still no solution?
Flash the super image through recovery.
Same problem.. but i manage to install another custom rom. Twrp wont work for that even you repair the Data or change system files. My solution is i use OrangeFox recovery, and install havoc os a11 and it works but other roms like evo x , pixelui, corvus os doesnt work and having error the same as you.
I have the same issue like u.. use the orangefox recovery.. to install custom ROM. It fix my issue.
ligodligerem said:
I have the same issue like u.. use the orangefox recovery.. to install custom ROM. It fix my issue.
Click to expand...
Click to collapse
Which version of orangefox do you have installed!
xerel89 said:
Which version of orangefox do you have installed!
Click to expand...
Click to collapse
hey.. i fix it right now. using twrp and orangefox. updated version. please consider to redownload your custom rom zip file. cause thats the reason why its not mounting. I tested it and after i download a new custom rom file and delete the previous custom rom, and put it in main directory "sdcard/" and suddenly it worked.
xerel89 said:
Which version of orangefox do you have installed!
Click to expand...
Click to collapse
i thought the error is in custom recovery, until i found out its the custom rom zip is the one got the prob.,
I have also Redmi note 9 Pro device,
Custom recovery twrp 5.4 installed
Just flashed Ancient OS 12.1 and this same thing happens.
Now cannot flash any other roms. Maybe android partitions bricked.
What should I do now!