Hi guys, I have a problem with my motorola moto g5. It turns out that I upgraded to android oreo and at the time of associating the fingerprint I asked for a pin for security which I put. En el twrp me pide el pin, el cual ingresa y ya podia utilizarlo pero cuando instalo una ROM me pide el pin antes de iniciar, en nougat inicia pero en oreo me sale el siguiente mensaje:
"Decryption unsuccessful. The password you entered is correct, but unfortunately yout data is corrupt. To resume using your phone, you need to perform a factory reset, you`ll have an opportunity to restore any data that was backed up your Google Account."
I have tried all the forms that have occurred to me, hard reset with RSD Lite and the stock firmware, formatting data gives me an error. I'm desperate and I do not know what to do, can someone please help me?
{
"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"
}
If you formatted some partition from F2FS to EXT4, the mobile will accuse this error. Go back to F2FS.
This error can also occur if you have not made all the necessary WIPES.
filipedonato said:
If you formatted some partition from F2FS to EXT4, the mobile will accuse this error. Go back to F2FS.
This error can also occur if you have not made all the necessary WIPES.
Click to expand...
Click to collapse
Thanks for your input, and make erase data in F2FS, but it does not let me format data to eliminate encryption. I still have the same problem, I still ask for the pin
alejandrorobles12 said:
Thanks for your input, and make erase data in F2FS, but it does not let me format data to eliminate encryption. I still have the same problem, I still ask for the pin
Click to expand...
Click to collapse
You must format data (different from wipe data)
Go into twrp
Select wipe
Select format data (option on right hand side)
TheFixItMan said:
You must format data (different from wipe data)
Go into twrp
Select wipe
Select format data (option on right hand side)
Click to expand...
Click to collapse
gives an error because it says it is encrypted
alejandrorobles12 said:
gives an error because it says it is encrypted
Click to expand...
Click to collapse
You can also go to bootloader & connect to pc & in a terminal window type
Code:
fastboot erase userdata
Note this will delete everything on internal stoeage (music pictures downloads etc) backup to sd or pc first if you need this data
You can also flash stock rom too if you then can't remove encryption - don't flash the partition or bootloader parts but there's no reason why you shouldn't be able to go into twrp - enter your decryption key to decrypt & mount data then format that partition
TheFixItMan said:
You can also go to bootloader & connect to pc & in a terminal window type
Code:
fastboot erase userdata
Note this will delete everything on internal stoeage (music pictures downloads etc) backup to sd or pc first if you need this data
You can also flash stock rom too if you then can't remove encryption - don't flash the partition or bootloader parts but there's no reason why you shouldn't be able to go into twrp - enter your decryption key to decrypt & mount data then format that partition
Click to expand...
Click to collapse
I have done exactly what you said but I still ask for the pin when installing a ROM and after putting it I get an error. I tried with the command fastboot erase data but nothing..
Microsoft Windows [Versión 10.0.15063]
(c) 2017 Microsoft Corporation. Todos los derechos reservados.
C:\WINDOWS\system32>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.238s]
finished. total time: 0.239s
C:\WINDOWS\system32>fastboot erase data
< waiting for device >
erasing 'data'...
(bootloader) Permission denied
FAILED (remote failure)
alejandrorobles12 said:
I have done exactly what you said but I still ask for the pin when installing a ROM and after putting it I get an error. I tried with the command fastboot erase data but nothing..
Microsoft Windows [Versión 10.0.15063]
(c) 2017 Microsoft Corporation. Todos los derechos reservados.
C:\WINDOWS\system32>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.238s]
finished. total time: 0.239s
C:\WINDOWS\system32>fastboot erase data
< waiting for device >
erasing 'data'...
(bootloader) Permission denied
FAILED (remote failure)
Click to expand...
Click to collapse
Flash stock rom firmware (except partition & bootloader part) boot phone fully then flash TWRP & format all partitions
TheFixItMan said:
Flash stock rom firmware (except partition & bootloader part) boot phone fully then flash TWRP & format all partitions
Click to expand...
Click to collapse
I thank you for your help and the time you have invested in me but fortunately and managed to decrypt by using a command with adb and then it has left me to format the data, eliminating with it all traces of encryption. :victory:
Here I leave the command and the source of where I got it in case someone could get through:
Code:
adb shell recovery --wipe_data --set_filesystem_encryption=off
If you need to run it from the phone itself (ie: you don't have a computer nearby to adb with):
Code:
recovery --wipe_data --set_filesystem_encryption=off
https://android.stackexchange.com/questions/98228/removing-encryption-from-recovery
alejandrorobles12 said:
I thank you for your help and the time you have invested in me but fortunately and managed to decrypt by using a command with adb and then it has left me to format the data, eliminating with it all traces of encryption. :victory:
Here I leave the command and the source of where I got it in case someone could get through:
Code:
adb shell recovery --wipe_data --set_filesystem_encryption=off
If you need to run it from the phone itself (ie: you don't have a computer nearby to adb with):
Code:
recovery --wipe_data --set_filesystem_encryption=off
https://android.stackexchange.com/questions/98228/removing-encryption-from-recovery
Click to expand...
Click to collapse
Did this method formatted your Internal Storage(files, songs, pictures, documents .etc)?
MP_Singh said:
Did this method formatted your Internal Storage(files, songs, pictures, documents .etc)?
Click to expand...
Click to collapse
Removing encryption will format internal storage - that's the whole point of encryption - it encrypts internal storage - you format data including user data to remove encryption you will loose everything on internal storage
Please help me
TheFixItMan said:
Removing encryption will format internal storage - that's the whole point of encryption - it encrypts internal storage - you format data including user data to remove encryption you will loose everything on internal storage
Click to expand...
Click to collapse
My guy i have the same issue plus adb is giving me an error saying "no devices/emulators found" can you please tell me how i can run the command on my phone any help would be appreciated. Thanks in advance.
A3G0N said:
My guy i have the same issue plus adb is giving me an error saying "no devices/emulators found" can you please tell me how i can run the command on my phone any help would be appreciated. Thanks in advance.
Click to expand...
Click to collapse
ADB will only work if your phone is in recovery mode or fully booted normally
If you are in bootloader mode you need to use fastboot commands
I've no idea what you are trying to achieve
If you want to remove encryption either format data in twrp (wipe than select option on the right to format data)
Or use the fastboot command with your phone in fastboot mode
fastboot erase userdata
This will erase everything on internal storage - once your phone has booted you can encrypt it again if you wish to
Help me asap!
TheFixItMan said:
ADB will only work if your phone is in recovery mode or fully booted normally
If you are in bootloader mode you need to use fastboot commands
I've no idea what you are trying to achieve
If you want to remove encryption either format data in twrp (wipe than select option on the right to format data)
Or use the fastboot command with your phone in fastboot mode
fastboot erase userdata
This will erase everything on internal storage - once your phone has booted you can encrypt it again if you wish to
Click to expand...
Click to collapse
so bro same thing is happening with me my MOTO g6 is showing decryption unsuccessful. and i just run bootloader and TWRP Help fast and i try all thing but not helped me i need help pls save my phone .
Bhagyesh dantani said:
so bro same thing is happening with me my MOTO g6 is showing decryption unsuccessful. and i just run bootloader and TWRP Help fast and i try all thing but not helped me i need help pls save my phone .
Click to expand...
Click to collapse
The answer is already in the post you quoted
Format data! Not wipe data - it must be formatted to remove encryption (which also wipes internal storage)
Or just flash your stock firmware - either way you will be formatting data
Hello I am Brazilian so forgive me for the english of google translator, you helped me a lot, I had the same problem and only with this step I managed to reverse the decryption. You really helped me, even after 3 years of making this comment
Related
PERISIST ERROR IN TWRP WHILE FLASHING ANY ZIP.....? THEN HERE IS THE GUIDE
{
"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 am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
What is the persist partition?
Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.
If you experience the following issues:
1. You get "e: cannot mount /persist" in recovery
2. Can't access to internal storage.
3. Boot loop on Lollipop 5.0 and above
4. IMEI number is lost even after formating cache and fastboot flash cache.img
5. No signal even after formating cache and fastboot flash cache.img
Then your persist partition have to be fixed
Follow instructions carefully to solve this issue
NOTE : UNLOCK your device bootloader first before doing this
1. Download this " persist file & ADB+&+Fastboot of yureka " provided by @Annabathina
2. extract them in PC
3. open ADB+&+Fastboot of yureka
4. place presist.img file which you have extracted in ADB+&+Fastboot folder
5. Hold shift key and right click on mouse and select Open command window here
6. Connect your device to pc..... and make sure that drivers are installed properly..... ( VERY VERY IMPORTANT )
a. Type : adb devices
If your device is connected you will get it in connected devices list
b. Type : adb reboot-bootloader
Your phone will restart into bootloader.
c. Type : fastboot -i 0x1ebf flash persist persist.img
7. Disconnect your device from PC and REBOOT
ADB+&+Fastboot : link
persist : link
Useful links
ADB for pc : link
YU usb drivers : link
PdaNet drivers : link
@Annabathina............................for Guide
Ricks ............... for Presist file
YU YUREKA
YU YUREKA PLUS
XDA:DevDB Information
[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016], Tool/Utility for the YU Yureka
Contributors
Annabathina
Version Information
Status: Stable
Stable Release Date: 2016-04-21
Created 2016-04-21
Last Updated 2016-04-23
Reserved
Reserved
I dont get a multirom function in the advanced settings menu. Is it because im using twrp 3.0.... Or is it bcoz of persist partition ?
Sent from my AO5510 using XDA-Developers mobile app
After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..
Bazilbycom said:
After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..
Click to expand...
Click to collapse
Have you solved it?
saurav007 said:
Have you solved it?
Click to expand...
Click to collapse
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers
Hi,
For me the message is : is not possible to erase this partition
Thanks a lot for your help
still same error.....what to do now..??
Bazilbycom said:
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers
Click to expand...
Click to collapse
Earlier i was getting error even after installing all the drivers, all i needed was to update PDAnet on phone as well & it does everything.
Thank you it worked well!
still stucking
i was suffering of problem error persist but using this method it solved the error is gone but not still my device stuck on boot i tried many custom roms stock rom formats and all but still it stuck after 2 of android logo. in twrp recovery in mount option the system, persist, firmware are uncheck .i think it means they are not mount right??? i click many time to check and reboot but still logo stuck problem please give me solution!!!!!!!
Thank You
Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk
vijaysingh1996 said:
Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk
Click to expand...
Click to collapse
This isn't TWRP flashable zip. You have to flash via fastboot (see OP) after extracting the img from downloaded zip file.
Failing on my Pantech Sky Vega Iron 2 IM-A910S (codename: ef63) and bootloader unlocked.
In Fedora Linux the command continues to display "waiting for device" message even though the device is detected by "fastboot devices" command, although its serial number is not displayed and ???????? is display in that place.
While in Windows 7 (64-bit), the following error message is displayed after execution of the command "fastboot -i 0x1ebf flash persist persist.img":
target reported max download size of 1610612736 bytes
sending 'persist' (4324 KB)...
OKAY [ 0.165s]
writing 'persist'...
FAILED (remote: It is not surpport in user build.)
finished. total time: 0.186s
Any one please help...
In my device it showing can't load persist
After typing last line
shekarsahani said:
In my device it showing can't load persist
After typing last line
Click to expand...
Click to collapse
Can you post CMD screenshot?
Make sure the file name is same as in CMD.
Unfortunately I can't is send cmd screenshot it is not uploading..
When I type fastboot -i 0x1ebf flash persist persist.img then it shows error cannot load 'persist.img'
{
"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"
}
Team Win Recovery Project
for Lenovo Vibe Z2 Pro
The only true recovery built straight from 8.1 source code.
Key features:
Based on android-8.1 TWRP sources and LineageOS 15.1
"eng" build (no adb authorization required, ro.secure=0)
Full /data HW decryption support (PIN/password/pattern)
Full adb support - sideload, etc...
Full SELinux support
OTA updates support
MTP & USB-OTG support
F2FS support
List of partitions:
System - /system
Data - /data
Persist - /persist
Preload - /preload
Firmware - /modem
Bootloader - /aboot
Boot (kernel) - /boot
Recovery - /recovery
Splash - /splash
Misc - /misc
FS Golden - /fsg
ESF (NV Data) - /modemst1 & /modemst2
MRD Data - /mrd
How to enter recovery?
Hold the POWER button and BOTH VOLUME buttons simultaneously until you see the TWRP logo.
Downloads
TWRP_3.2.1-0_K920.img (2018/02/24) [15.5 MB] | Google Drive Mirror
TWRP_3.1.1-0_K920.img (2017/10/15) [12.7 MB]
TWRP_3.1.0-0_K920.img (2017/03/21) [12.7 MB]
TWRP_3.0.3-0_K920.img (2017/01/24) [14.7 MB]
TWRP_3.0.2-2_K920.img (2016/11/26) [13.3 MB]
TWRP_3.0.2-1_K920.img (2016/10/08) [10.7 MB]
TWRP_3.0.2-0_K920.img (2016/09/04) [10.7 MB]
I am not responsible for anything that happens to your phone or computer. You have to understand what you are doing.
Sources
Manifest: https://github.com/K920/android/tree/master/twrp
Device tree: https://github.com/K920/android_device_lenovo_kingdom/tree/twrp
Dev Info
To build with 15.1 sources requires:
export ALLOW_MISSING_DEPENDENCIES=true
repopick -t oreo-lineage-build (omnirom)
Manual removal of "vendor" under out/.../recovery/root/
Screenshots
FAQ:
How do I flash this TWRP .img? (with PC)
If you haven't already, install ADB+Fastboot with drivers (I recommend this installer)
Enable ADB debugging on your phone (in Settings->Developer Options)
After connecting the phone to the PC, pop up may appear, tick Always allow from this computer and click OK
Extract downloaded recovery zip and copy .img file to C:/adb
Now open cmd line (press Start+R, type "cmd", press OK) and go to C:/adb (type "cd C:/adb" and hit Enter)
Reboot into bootloader (fastboot mode) (type "adb reboot-bootloader")
Your phone should now reboot into the bootloader (Little green android logo in the middle of the screen)
Flash the recovery.img (type "fastboot flash recovery recovery.img")
Finally, reboot!
Done!
Do I have to have unlocked bootloader?
Yes!Whenever I try to flash something, I'm getting ERROR 7. Help!
Reboot->Recovery, also make sure that your flashable zip isn't corrupted.I have formatted encrypted /data partition, now I can't mount it.
Reboot->RecoveryWrong password?!?
Reboot->RecoveryDoes this work on CN variants?
Yes!I can't flash my favorite ROM/.zip/we, this is not a kingdom_row device! (3.0.3+)
Yes, that's right. For the sake of using the same device tree as official Lineage OS, we're using common 'kingdom' device name. Many flashable .zips include safety mechanism to prevent them being flashed on unsupported device. If this is the case, ask the creator of your .zip to assert also on 'kingdom' device name. (e.g. by using TARGET_OTA_ASSERT_DEVICE), or edit the updater-script by yourself.
Electry said:
reserved
Click to expand...
Click to collapse
Installation error - android\google\update-binary
CM13 (03092016)
Alexander_Gostev said:
Installation error - android\google\update-binary
CM13 (03092016)
Click to expand...
Click to collapse
It is not a flashable zip... If you want to install this TWRP, you'll have to extract the .zip and flash the .img through fastboot (fastboot flash recovery recovery.img).
Electry said:
It is not a flashable zip... If you want to install this TWRP, you'll have to extract the .zip and flash the .img through fastboot (fastboot flash recovery recovery.img).
Click to expand...
Click to collapse
Thanks, I understood and flashed through recoveri.
How do the two systems?
Updated to 3.0.2-1
/persist is now mounted RW
thx, good work
Hello
After last update of CM 14.1 via OTA (20161104) I cannot re-flash TWRP when I trying to do that via TWRP i see error http://i.imgur.com/tJ4IZXf.png. Is it a problem with permissions or with something else ? Thx
yes it's not working. you can use "fastboot flash recovery recovery.img"
Sent from my K920 using Tapatalk
Hello friends,
I try to flash it but got this:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 1610612736 bytes
sending 'recovery' (17332 KB)...
OKAY [ 0.547s]
writing 'recovery'...
FAILED (remote: invalid data)
finished. total time: 0.758s
My phone is lenovo K920
Android version 5.0.2
Anyone can help me?
Thank you.
Do first unlock bootloader
Wysłane z mojego K920 przy użyciu Tapatalka
Electry said:
Updated to 3.0.2-1
/persist is now mounted RW
Click to expand...
Click to collapse
https://mega.nz/#!YIRiFZra!a3fVWBylwMDRghq3Aa15Q3R4WrSIFFMZLvHQa_HMLn4
не рабочая ссылка!
broken links!
Alexander_Gostev said:
https://mega.nz/#!YIRiFZra!a3fVWBylwMDRghq3Aa15Q3R4WrSIFFMZLvHQa_HMLn4
?? ??????? ??????!
broken links!
Click to expand...
Click to collapse
wtf? they're not broken
Electry said:
wtf? they're not broken
Click to expand...
Click to collapse
link does not boot at all, you can move?
ссылка не грузиться вобще, можете перезалить?
Hi all,
As I got instruction few posts before I tried to copy last version of twrp via ADB but it does not work. Installed TWRP 3.0.2-1 ,
When i try to push it via ADB I see an error -------------------------------------Ä»αÑñѽѡ¿Ñ ΓѽÑΣ«¡á
List of devices attached
89355fd4 recovery
-------------------------------------ÅÑαѺáúαπº¬á ó bootloader
-------------------------------------çá»π߬ root-shell
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.458s]
booting...
OKAY [ 0.019s]
finished. total time: 0.477s
-------------------------------------Åα«Φ¿ó¬á recovery
failed to copy 'fw\twrp.img' to '/sdcard/twrp.img': Read-only file system
CANNOT LINK EXECUTABLE "/system/bin/sh": library "libNimsWrap.so" not found
-------------------------------------ÅÑαѺáúαπº¬á ó recovery
-------------------------------------çáóÑαΦÑ¡«
-------------------------------------ì᪼¿ΓÑ ½εíπε ¬½áó¿Φπ.
internal mem is Read only mode ????
ROOT for ADB , USB enabled.
As I mentioned before flashing via TWRP dow not work too.
Any suggestions?
Thx
seekator said:
Hi all,
...
As I mentioned before flashing via TWRP dow not work too.
Any suggestions?
Thx
Click to expand...
Click to collapse
no, I won't provide support for any 3rd party batch scripts (or w/e is that log from). If you can't figure out how to flash single .img, you shouldn't be messing with this stuff.
ps: I'm uploading 3.0.3-0 with F2FS support.
Electry possible to make re-initialization of the system partition? To release the space not used by the system. She's stock was designed for Roma. A cm (lineage) is much easier.
And what topics can be done f2fs?
Отправлено с моего K920 (ROW) через Tapatalk
Sorry my google English)
Electry said:
no, I won't provide support for any 3rd party batch scripts (or w/e is that log from). If you can't figure out how to flash single .img, you shouldn't be messing with this stuff.
ps: I'm uploading 3.0.3-0 with F2FS support.
Click to expand...
Click to collapse
OK Thanks . When you mentioned about unsupported script I have taken a look on it and .... Yep I used wrong zip with adb . When I tried right one I had another output . Strange, I had TWRP, ROOT but locked bootloader.
Then QPST to version 143 ,update to lollipop, bootloader , root, yours TWRP and I have last recovery, LineageOS :good:
UPDATE
Something wrong is with last TWRP 3.0.3-0. Because I started fresh installation lastest TWRP and CM I had to install everything from the scratch and ..... I was not able to install GAPPS, error 64 and something about architecture, yep I was trying to install 32 bit gapps so it was ok, when I pressed reboot it came back to TWRP, reboot to system the same, Bootloader too. When I switched back to previous version TWRP_3.0.2-2_K920.img I was able to install gapps and reboot menu was operating as it should.
On TWRP_3.0.2-2_K920.img is ok .
seekator said:
UPDATE
Something wrong is with last TWRP 3.0.3-0. Because I started fresh installation lastest TWRP and CM I had to install everything from the scratch and ..... I was not able to install GAPPS, error 64 and something about architecture, yep I was trying to install 32 bit gapps so it was ok, when I pressed reboot it came back to TWRP, reboot to system the same, Bootloader too. When I switched back to previous version TWRP_3.0.2-2_K920.img I was able to install gapps and reboot menu was operating as it should.
On TWRP_3.0.2-2_K920.img is ok .
Click to expand...
Click to collapse
That's an issue with gapps. TWRP 3.0.3-0 uses toybox instead of busybox and the 'unzip' executable/link is missing. Check my 2nd post (FAQ) there is a way around it, but you can just use 3.0.2-2 if that's easier.
EDIT: I've rebuild 3.0.3-0 with busybox included, so this shouldn't be an issue anymore.
whats new in TWRP 3.2.0-0? when the official release of twrp for our k920?
On my Moto G5 TWRP when i try to wipe or flash any ROM it gives me unable to mount storage error and the storage shown as 0Mb and i can't even explore it inside the recovery
basem bebarse said:
On my Moto G5 TWRP when i try to wipe or flash any ROM it gives me unable to mount storage error and the storage shown as 0Mb and i can't even explore it inside the recovery
Click to expand...
Click to collapse
You haven't said which partition
If it's data goto wipe & select the option on the right
You can also do it in fastboot mode
fastboot erase userdata
This will erase everything on internal storage
Restart to recovery & data should be mountable
Anything else you may have to flash stock firmware via fastboot including gpt to repartition your device correctly - make sure you you flash a firmware that is equal or newer than the version currently installed
TheFixItMan said:
You haven't said which partition
If it's data goto wipe & select the option on the right
You can also do it in fastboot mode
fastboot erase userdata
This will erase everything on internal storage
Restart to recovery & data should be mountable
Anything else you may have to flash stock firmware via fastboot including gpt to repartition your device correctly - make sure you you flash a firmware that is equal or newer than the version currently installed
Click to expand...
Click to collapse
It works, Thank you so much that was very useful
i flashed twrp but now im stuck at a formatting error called "mke2fs -t ext4 -b 4096 /dev/block/sdc46 29325304 process ended with ERROR: 1 Unable to wipe Data. Unable to format to remove encryption."
I am installing PE11 Exp. ROM and right after successfully flashing my PE ROM I am stuck at this format stage. Will I be needing to flash MIUI stock rom and uninstall TWRP or what now? I'm confused. Pls help.
th1nd said:
i flashed twrp but now im stuck at a formatting error called "mke2fs -t ext4 -b 4096 /dev/block/sdc46 29325304 process ended with ERROR: 1 Unable to wipe Data. Unable to format to remove encryption."
I am installing PE11 Exp. ROM and right after successfully flashing my PE ROM I am stuck at this format stage. Will I be needing to flash MIUI stock rom and uninstall TWRP or what now? I'm confused. Pls help.
Click to expand...
Click to collapse
Just changed the formatter in format settings (rm -rf instead of formatting) and it did install PE rom but my internal storage is inaccessible now .
Same issue here, haven't changed the format settings yet. Did you fix the issue with the internal storage?
Same problem
Laminesls said:
Same problem
Click to expand...
Click to collapse
Just need for more steps. Wipe dalvik, data, cache, system, vendor > Reboot recovery. Format data> Reboot recovery. Then start do flash rom and do other steps again. This happen because of encryption. If wipe data error, go in fastboot and type "fastboot -w" in ADB PC
Kirasu2080 said:
Just need for more steps. Wipe dalvik, data, cache, system, vendor > Reboot recovery. Format data> Reboot recovery. Then start do flash rom and do other steps again. This happen because of encryption. If wipe data error, go in fastboot and type "fastboot -w" in ADB PC
Click to expand...
Click to collapse
I am stuck as well. I followed the flash guide of the LiteUp MIUI V12.5 rom for the redemi note 8 pro: https://telegra.ph/Steps-01-01 And I got the error message after formatting the data. I asked on the telegram channel and they told me to change the file system to ext4, but that didn't worked. I tried your solution of wipe, then reboot recovery, fromat data, reboot recovery... flashed the rom again and then I rebooted straight to TWRP again. Can you help me?
Anyone know how to fix this I've tried to format data typed yes and this is what I get back using OnePlus 6t android 11 twrp 3.7.0
jamiehawman said:
Anyone know how to fix this I've tried to format data typed yes and this is what I get back using OnePlus 6t android 11 twrp 3.7.0
Click to expand...
Click to collapse
If you have PC, boot in fastboot mode and type "fastboot -w"
If you dont have PC, you can do some tricks to format:
- For flash new rom, Wipe necessary things > Reboot Recovery > Format data > Reboot Recovery > Flash rom
- Or you can go Wipe > Advanced Wipe > Data and Change File System to Ext4 (Or any default file system that your phone using)
i rebooted the twrp asked for password it decrypted so now il drag and drop magisk to phone do i need to drag and drop the twrp and that rom too
ive sorted it now well a g
Kirasu2080 said:
If you have PC, boot in fastboot mode and type "fastboot -w"
If you dont have PC, you can do some tricks to format:
- For flash new rom, Wipe necessary things > Reboot Recovery > Format data > Reboot Recovery > Flash rom
- Or you can go Wipe > Advanced Wipe > Data and Change File System to Ext4 (Or any default file system that your phone using)
Click to expand...
Click to collapse
uy sorted it for me i had to install a new rom install the new twrp and wallah all good
Back up your data if you still can.
You can try two methods below. Be careful: both will wipe our your data.
Method 1: boot into fastboot
fastboot erase userdata
fastboot erase cache
fastboot erase recovery
fastboot erase system
Try flashing a recovery
fastboot flash recovery [name-of-your-recovery.img]
Method 2: boot into recovery, if you still can
In Twrp / Orangefox / other recovery, format data -> yes;
Plus, you can wipe data, cache and other partitions in recovery.
wenyendev said:
Back up your data if you still can.
You can try two methods below. Be careful: both will wipe our your data.
Method 1: boot into fastboot
fastboot erase userdata
fastboot erase cache
fastboot erase recovery
fastboot erase system
Try flashing a recovery
fastboot flash recovery [name-of-your-recovery.img]
Click to expand...
Click to collapse
Just logged in to say thanks. I flashed a PixelOS Rom without removing the password on the old ROM, and the storage is encrypted. Failed to format data, TWRP bootloop, tried different methods, did not work until I found this post.
Long story short, read the previous thread: https://forum.xda-developers.com/t/...-product-vendor-odm-invalid-argument.4431903/
After succesfully installing the fastboot rom via Mi Flash, the phone is still in a bootloop. Tried flashing TWRP via fastboot command (fastboot boot twrp.img) but it can't decrypt the /data partition with the correct passcode anymore. after a reboot in recovery, the /cust partition also can't be mounted anymore, with error "Structure needs cleaning".
I do not have a backup of my system nor data partition, nor internal storage, so i absolutely need it to work again without wiping/formatting the data partition
EDIT: after flashing the fastboot rom again via mi flash and twrp via fastboot command, the cust error disappears but twrp still can't decrypt /data
EDIT: i decided to do a full wipe of my internal memory and the phone works again. this thread should be closed.