Why after installing pixel experience pie ver my recovery twrp request password?
And after canceling it can't mount internal storage and for resolve it you should reset factory so my internal storage cleared
Sent from my Le X820 using Tapatalk
I got same problem last time i switch to stock OS this error caused by latest TWRP image
You need to reinstall TWRP old version. i didn't remembered exact version. try TWRP images from old to new
naga ravi 259 said:
I got same problem last time i switch to stock OS this error caused by latest TWRP image
You need to reinstall TWRP old version. i didn't remembered exact version. try TWRP images from old to new
Click to expand...
Click to collapse
Which version of TWRP should we install?
I am using the latest version of 3.2.3.1, screaming and often crashing TWRP and resetting internal storage.
Can you look at your TWRP version and answer it.
I have the same problem.
Related
So my problem began when i flashed eu rom latest version my setup was:
TWRP offcial 3.1.0-0
/data and /cache F2FS
previously running android 7.1.2 (Nitrogen OS)
And Franco Kernel and even before that i used MIUI 8.2.20 with ZCX and ext4 patrtions
Flashing EU rom i got a weird intro screen username and password asking to validate the phone (NOT MI ACCOUNT IT WAS AT THE VERY BEGINNING OF THE BOOT)
so i gave my mi account credentials and then nothing so after i that i put my phone away for 15 days.
So yesterday after 15 days my exams ended i edl flashed my phone and then i install miui 8.1.6.0 and then updated to 8.2.3.0 and then i was good and running the s8 theme but within that span i started missing NOS so flashed ZCX Backed UP MIUI 8.2.3.0 and then i flashed Offcial TWRP no probs flashed absolutely fine and then i restored my backup of my rom before i went EU $#!T and i restored upon booting it asked for password i then remebered that miui encrypts the /data patition so i formatted /data and then i thought of restoring the /data partition and then it would stop at copying a certain partition and i would wait for a long time and then i ejected the phone from the computer but still i was not able to delete or do anything in the /data partition as if it is read only partition UPON DELETING ANYTHING I GET "RM -RF ERROR" I AM FLASHING ROMS SINCE 2010 WITH GALAXY S AND I NEVER FACED A ISSUE LIKE THIS !!! i completely freaked out i thought of doing something so i formatted /data and it would get stuck there forever!! because of this i had to flash miui through edl 4 times until i gave up and installed miui and then just installed NOS and Gapps then nos unroot,magisk and at last franco r5 as i didn't had the r6 version then after booting up i restored all my apps from titanium backup and i good to go..........
UNTIL THEN FK Manager Auto flashed r6 version of franco and then AS I REBOOTED I FOUND WIFI NOT WORKING SO I CHECKED MAC ADDRESS IT WAS 00:00:02...... I WAS COMPLETELY SHOCKED I THEN CHECKED BASEBAND IT WAS 'UNKNOWN' I WAS LIKE i was trying to restore modem i got "extractTarFork() process ended with ERROR: 255 " then now i am flashing miui thorugh EDL i will update u all soon...
BUT WHY IS THIS HAPPENING WHY I AM NOT ABLE TO TO NOS WITHOUT DOING ANY $#!T I LOVE NOS AND I WANT TO INSTALL IT AND ALSO CONVERT TO F2FS AND OFFICIAL TWRP PLEASE HELP IN DOING SO!!!!
Wipe everything first of all.
Flash nos
Flash gapps
Install apps from play store.
Forget about the backup. It may not be compatible with latest builds. Too many code mashups. Starting fresh is always considered best option
Flash latest firmware.
Done. Enjoy.
Archit9169 said:
Wipe everything first of all.
Flash nos
Flash gapps
Install apps from play store.
Forget about the backup. It may not be compatible with latest builds. Too many code mashups. Starting fresh is always considered best option
Flash latest firmware.
Done. Enjoy.
Click to expand...
Click to collapse
Update:I flashed using edl in phone booted fine and i was able to use phone network and wifi AND LUCKILY I WAS ABLE TO RESTORE THE BACKUP FROM PREVIOUS ROM AND RESTORED FINE and even copying the backup through offcial twrp worked fine
but still why the errors previously????? extractTarFork() process ended with ERROR: 255
Androbots said:
...process ended with ERROR: 255
Click to expand...
Click to collapse
I started having issues flashing ROMs and restoring backups after updating to the official TWRP 3.1.0.0 and 3.1.1.0
It sounds stupid and paradoxical but the previous 3.0.2.0 (or something) I used (not even sure if it was the official one) was faster and trouble-free in my experience. Don't know why nobody mentions this in the TWRP thread.
Androbots said:
Update:I flashed using edl in phone booted fine and i was able to use phone network and wifi AND LUCKILY I WAS ABLE TO RESTORE THE BACKUP FROM PREVIOUS ROM AND RESTORED FINE and even copying the backup through offcial twrp worked fine
but still why the errors previously????? extractTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
I had the same problem.
Flashed rom trough edl, with zcxrecovery img.
Flashed latest modem.
Restored my TWRP backup and the error was gone. ^^
Kaldrox said:
I started having issues flashing ROMs and restoring backups after updating to the official TWRP 3.1.0.0 and 3.1.1.0
It sounds stupid and paradoxical but the previous 3.0.2.0 (or something) I used (not even sure if it was the official one) was faster and trouble-free in my experience. Don't know why nobody mentions this in the TWRP thread.
Click to expand...
Click to collapse
Kollachi said:
I had the same problem.
Flashed rom trough edl, with zcxrecovery img.
Flashed latest modem.
Restored my TWRP backup and the error was gone. ^^
Click to expand...
Click to collapse
Yeah u all are correct something wrong with latest versions of twrp. Anyways i am up and running my rn3 again thanks for all ur help..!! Good night
Hi guys i tried using twrp 3.1.1.0 and it says password for unmount data. Also my phone in settings says encrypted.
I tried wiping data cahce, etc but that diidnt worked also using default_password but that diddnt worked as well
Model x820 stock ROM
Zlade112 said:
Hi guys i tried using twrp 3.1.1.0 and it says password for unmount data. Also my phone in settings says encrypted.
I tried wiping data cahce, etc but that diidnt worked also using default_password but that didnt worked as well
Model x820 stock ROM
Click to expand...
Click to collapse
Have you try reboot the phone into normal Android system? and later try reboot into TWRP, I read somewhere it might work.
Moon75 said:
Have you try reboot the phone into normal Android system? and later try reboot into TWRP, I read somewhere it might work.
Click to expand...
Click to collapse
Hi guys the solution for my me was doing an entire wipe of everything except recovery then flash rom, it seems that the stock rom of le max was causing that
What was your ROM in the beginning? Was it Indian ROM? Did it have the update manager? Which ROM did you flash after wiping everything except recovery?
I bought the phone from geekbuying with EUI version 5.8.019S (Stable), BUILD: FGXOSOP5801910121S release-keys. It looks like the latest vanilla Indian ROM, but it is most likely vendor-modified since the phone was received unsealed and there is no update manager. The main problem is the encryption - phone is encrypted right from the start without any password or PIN prompts. Factory reset allows to set up everything from the start, but the phone is still encrypted. TWRP asks for a decryption password. I have tried multiple vendor and default passwords with no luck. TWRP factory reset does not prevent the encryption.
This question keeps coming up in forums since people do not seem to search for similar questions. Well, I did. Therefore, I will try to assemble the list related to the encrypted ROM:
https://forum.xda-developers.com/le-max-2/help/eui-roms-support-device-encryption-t3516825
https://forum.xda-developers.com/le-max-2/help/wiping-to-install-rom-le-max2-suddenly-t3518405
https://forum.xda-developers.com/le-max-2/help/update-eui-t3480614
https://forum.xda-developers.com/le...dian-stock-19s-rom-chinese-bloatware-t3484388
https://forum.xda-developers.com/le-max-2/help/benefit-form-leaving-x829-to-indian-t3609698
Proposed solutions:
CASE 1: No Update manger + encrypted ROM
Since it is a vendor ROM, you can try flashing a clear stock ROM from recovery that can be downloaded from the official LeEco forum http://forum.le.com/in/eui_detail.html?euiid=206 . It might not directly resolve encryption, but will make the update manager appear, which can be used to upgrade to ROM w/o encryption. If you want to stick to the Indian ROMs, but want to remove encryption - see below
More reading here: https://forum.xda-developers.com/le-max-2/help/update-eui-t3480614
CASE 2: Encrypted ROM
You most likely have an Indian ROM. You can try reinstalling the ROM (TWRP) and immediately wiping the data partition from TWRP. Some users report success with this.
More reading here: https://forum.xda-developers.com/le...dian-stock-19s-rom-chinese-bloatware-t3484388
One user has found that upon multiple resets with TWRP the encryption seems to be ignored
More reading here: https://forum.xda-developers.com/le-max-2/help/benefit-form-leaving-x829-to-indian-t3609698
Another user suggests Chinese ROMs since they are likely not to encrypt the files. In other words, updating to a Chinese ROM might help.
More reading here: https://forum.xda-developers.com/le-max-2/help/plz-help-unskilled-x829-user-to-update-t3609639/page2
Have any of the proposed solutions worked for you?
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
gordonthegopher said:
Formatting /data in TWRP uses up all the blocks, but encryption from Lineage needs 16kb of free space at the end of the partition to store the headers.
Click to expand...
Click to collapse
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Hi guys,
I'm kind of stuck right now because I cannot encrypt my phone anymore and I don't know why. I got my phone last year and installed LOS 14.1 right away. For security reasons I also encrypted it - without any issues whatsoever. When LOS 15.1 came out, I upgraded my phone, with encryption still working. A couple of days back for some reason I decided to do a factory reset. Obviously, the device wasn't encrypted anymore after the reset. I then installed the new nightly of LOS (20180807) and tried to encrypt my phone once again. When I select "Encrypt phone", I need to enter my PIN, the phone restarts and reboots without encryption being started.
What I've done so far:
I've flashed two different TWRP versions: 3.2.3.0 and a customized one (https://forum.xda-developers.com/re...other-development/rom-lineageos-15-0-t3690465).
I've clean installed different LOS versions (unofficial LOS 14.1 and LOS 15.1 starting from the 20180710 release)
I've clean installed Omnirom (current release and a release from 20180107).
I've even flashed MIUI 9 and reinstalled LOS thereafter because some guy in the above mentioned LOS thread wrote, that this did the trick for him.
I've disabled WI-FI and mobile data before trying to encrypt my phone, because I found a blog article stating that this might help.
Nothing helped. The phone just reboots and stays unencrypted.
Do you guys have any additional hints or ideas how I can manage to encrypt my phone once again? Could another TWRP version do the trick? Is TWRP even involved in any kind when it comes to encryption of the OS? Do you think another ROM could be helpful?
Click to expand...
Click to collapse
Try orangewolf recovery ....
Sent from my Redmi Note 4 using Tapatalk
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
shakil002 said:
Try orangewolf recovery ....
Click to expand...
Click to collapse
Thanks for the advice. But I'm afraid it didn't help
CanBostanci said:
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
Click to expand...
Click to collapse
That's the most ****ed up part. For some people it does work, for some not.
There surely must be some ridiculous small detail we're not getting. Like disabling WI-FI while Bluetooth is enabled.
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
parkbank said:
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
Click to expand...
Click to collapse
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
CanBostanci said:
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
Click to expand...
Click to collapse
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
parkbank said:
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
Click to expand...
Click to collapse
I'm looking forward to hear the results. I'm about to become insane because of this encryption issue.
I've flashed both the dev and stable firmware found in this thread. No success
By flashing I mean factory reset, flashing the firmware and then installing LOS. I noticed, that flashing a new firmware while a ROM is still installed leads to some random ****ups.
After a couple of days of flashing, factory resetting, re-flashing, reading and a lot of cursing I finally found a working solution. I've added the fix to my initial post. Hopefully this helps
I was looking for solutions for quite a while and nothing else worked but did this and my device is encrypted again.
Thank you!
parkbank said:
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Click to expand...
Click to collapse
You have save my day "my MIDO" hehehehe
After the 1st PIE Rom the encryption was broken.
Your Step by Step save this and now Syberia 9 was able to encrypt with success :good:
Thank you one more time for sharing.
Thx!
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
Orangefox worked
is there any plan to fix twrp itself?? thx
Thank you. It worked for me to get Havoc OS 9.0 with hardware encryption on my Redmi Note 3 SE.
I bypassed unlocking the bootloader by doing this. Then I installed TWRP 3.1.0.0 from the recovery, did the reset and everything as instructed here, updated it to 3.3.1.0, rebooted, then flashed the Pie ROM and latest gapps without any further wiping.
I use the first link, I've modified the partition size -> did the trick wihtout formating nor loosing datas
Great, thank-You.
Hi, I want to ask, what is this encryption features you been using? can u tell me?
Hi, i was trying to install lineage os 16 and when i rebooted my phone, lineage os was asking for password, i panicked, launched TWRP and wiped data and restored a backup, since then im in bootloop. I dont know how to install lineage os or stock MIUI now that i cant boot my phone.
(i tried copying some files from my pc to poco but TWRP doesnt seem to recognice them to let me install)
Any help would be really appreciated!
EDIT: installed stock rom with xiaomi flash tool
First you should have flashed DFE you could have also fixed that by formatting the internal storage, anyways try flashing compatible vendor, firmware files are then flash LOS 16 with DFE if it doesn't work flash stock miui with and make sure to flash DFE after that or you'll lose TWRP and will get back on stock recovery
Blubandit23 said:
First you should have flashed DFE you could have also fixed that by formatting the internal storage, anyways try flashing compatible vendor, firmware files are then flash LOS 16 with DFE if it doesn't work flash stock miui with and make sure to flash DFE after that or you'll lose TWRP and will get back on stock recovery
Click to expand...
Click to collapse
Thanks, i had flashed firmware and then los 16, i followed munchy steps from youtube except that i installed newer version of magisk and TWRP, i skipped DFE because i wanted to have LOS16 encrypted (i thought this was not a must).
So it is not possible to skip DFE? or if i would had just formatted internal storage as you say would solve the password issue?
cyanocitta said:
Thanks, i had flashed firmware and then los 16, i followed munchy steps from youtube except that i installed newer version of magisk and TWRP, i skipped DFE because i wanted to have LOS16 encrypted (i thought this was not a must).
So it is not possible to skip DFE? or if i would had just formatted internal storage as you say would solve the password issue?
Click to expand...
Click to collapse
If you want your device encrypted follow the same steps as you previously did and reboot if it asks for password just go back to twrp go to wipe and simply format from there it should solve the problem:good:
Blubandit23 said:
If you want your device encrypted follow the same steps as you previously did and reboot if it asks for password just go back to twrp go to wipe and simply format from there it should solve the problem:good:
Click to expand...
Click to collapse
Great! Thanks a lot, gonna try that and write back.
Repeated the process to install LOS16, and this time it didnt ask for password. :laugh:
Hi there its me again, I have tried installing custom and stock rom and it do gets installed but when i boot into system it only boot into recovery
at first i did wipe Dalvik, cache, system, vendor, data, internal storage
i tried installing vendor too and it got installed then when i flashed stock rom it didnt work too and ozip file from realme website is having error when i install what i am doing wrong ?
Hello, first I need to ask questions to better assess the issue you're encoungering.
• What did you do to your phone before the problem happended?
• Were you able to mount all the partitions?
• After flashing, are you sure it is successful?
youcancallmekhen said:
Hello, first I need to ask questions to better assess the issue you're encoungering.
• What did you do to your phone before the problem happended?
• Were you able to mount all the partitions?
• After flashing, are you sure it is successful?
Click to expand...
Click to collapse
well i dont remember tbh i was so frustrated i wanted i install custom rom first i got into fastboot loop i wasnt able to use twrp it was showing the current image(boot/recovery) have been destroyed and can not boot,
so i installed boot.img and then twrp and it eventually go into twrp then i saw the tutorial of how to install nusantara rom and it says wipe all the above fields i told earlier
najam489 said:
well i dont remember tbh i was so frustrated i wanted i install custom rom first i got into fastboot loop i wasnt able to use twrp it was showing the current image(boot/recovery) have been destroyed and can not boot,
so i installed boot.img and then twrp and it eventually go into twrp then i saw the tutorial of how to install nusantara rom and it says wipe all the above fields i told earlier
Click to expand...
Click to collapse
i think going to orange fox recovery might help
najam489 said:
i think going to orange fox recovery might help
Click to expand...
Click to collapse
or maybe the vendor i am using is having issue i did used c10 and it was having issues maybe that was wrong so installed c14 and it got installed successfully
Try installing shapeshift OS ... That fixed my issue ... And AOSP android 10 would work too !! I am using TWRP ... Working fine for me !!