e unable to decrypt fbe device что это

Как исправить невозможность смонтировать хранилище в TWRP Recovery

В этом руководстве мы покажем вам шаги по исправлению невозможности смонтировать хранилище в TWRP Recovery. Экосистема Android, благодаря своей природе с открытым исходным кодом, допускает множество настроек.

Единственное требование — разблокировать загрузчик устройства. Как только вы этого добьетесь, вы сможете запустить множество пользовательских двоичных файлов, модов, пользовательских ПЗУ и даже Magisk для рутирования вашего устройства. Однако стандартное восстановление не может установить эти файлы. Вам нужно будет установить кастомное рекавери, например TWRP.

После того, как ваше устройство загрузится в это восстановление, вы можете стереть различные разделы устройства, выполнить резервное копирование Nandroid и, конечно, прошить вышеупомянутые файлы. Однако несколько раз вы можете столкнуться с ошибкой или двумя.

Среди них самые распространенные и пугающие, похоже, не могут смонтировать ошибку хранилища при отображении TWRP. В этом руководстве мы рассмотрим различные причины этой ошибки, а затем перечислим возможные исправления для исправления этой ошибки. Следуйте.

Причина невозможности смонтировать хранилище в TWRP

Первая причина, по-видимому, связана с тем, что внутреннее хранилище вашего устройства зашифровано. В результате TWRP не может расшифровать его на ходу и, следовательно, не может получить доступ к файлам, хранящимся на вашем устройстве.

Это причина, по которой эта ошибка чаще всего возникает, когда вы собираетесь прошить файл с помощью этого восстановления.

В других случаях ваш раздел данных может быть поврежден из-за того, что мигает неправильный файл или файл в неправильном разделе. Во всех этих сценариях ваш TWRP может отображать внутреннее хранилище как имеющее 0 МБ занятого места.

Но не волнуйтесь, это не так, и ваши данные на данный момент могут быть все еще нетронутыми. Итак, с учетом сказанного, вот различные методы исправления невозможности монтировать хранилище в TWRP Recovery.

Как исправить невозможность смонтировать хранилище в TWRP Recovery

Мы поделимся тремя разными способами решения этой проблемы. Следуйте инструкциям в том же порядке, как указано. Просто убедитесь, что ваше устройство уже загружено в TWRP. Е

Исправление 1: удалить экран блокировки

Если вы используете графический ключ на своем устройстве, TWRP не сможет его расшифровать. Рекомендуется переключиться на пин-код или пароль.

Теперь попробуйте прошить нужные файлы и посмотрите, исправлена ли проблема с невозможностью монтировать хранилище в TWRP Recovery.

Исправление 2: восстановить или изменить файловую систему

Вы также можете попробовать восстановить или изменить файловую систему вашего устройства. Все это можно было сделать прямо из самого TWRP.

Убедитесь, что вы по-прежнему получаете сообщение об ошибке «Невозможно смонтировать хранилище при восстановлении TWRP».

Исправление 3: форматирование внутренней памяти

Убедитесь, что вы создали эту резервную копию на SD-карте или USB OTG, а не в памяти телефона, так как мы собираемся полностью стереть этот раздел. Когда вы закончите резервное копирование, выполните следующие действия.

Мы поделились тремя разными методами для одного и того же, дайте нам знать, какой из них сработал за вас.

Источник

E unable to decrypt fbe device что это

В теме нет куратора. Если в теме есть пользователь, желающий стать Куратором и соответствующий Требованиям для кандидатов, он может подать заявку, создав новую тему в разделе Хочу стать Куратором (предварительно изучив Правила и рекомендации для Кураторов).
До назначения куратора, по вопросам наполнения шапки, обращайтесь к модераторам раздела через кнопку под сообщениями, на которые необходимо добавить ссылки.

boltaevruslan,
индийскую ставь там есть.
только загрузчик сначала разблокируй!

makar42, makar42, makar42,

А Индийскую где можно скачать? Подскажи пожалуйста.

boltaevruslan,
Судя по сайту https://www.mi.co.id/id/list/ он не продаётся в Индонезии, поэтому как вам и посоветовали ставьте Индию, прошивка в шапке темы.

boltaevruslan,
Читайте посты внимательно! Вам всё написали, не нужно строчить в теме как в чате.

Если кто напишет свою подробную инструкцию по прошивке в этой теме, то с удовольствием поставлю + и добавлю в шапку!

Переход между разными прошивками на заблокированном загрузчике, в том числе и на индийскую прошивку.
FAQ общих инструкций и рекомендаций для устройств Xiaomi (Пост Dima_Apatity #86902456)

Что такое dm-verity?

Android 4.4 и более поздние версии поддерживают режим «проверенной загрузки» для борьбы с руткитами. Реализован через функцию device-mapper-verity (dm-verity), которая проверяет конфигурацию устройства во время загрузки.
Если dm-verity активирован на вашем устройстве, тогда вы не можете вносить изменения в системный раздел. А если вы все таки попытаетесь, тогда получите bootloop. В ramdisk есть проверка dm-verify. Если ее убрать, вы сможете обойти dm-verity. Представленный ниже скрипт как раз делает эту работу по удалению проверки.

Что такое forced encryption (принудительное шифрование)?

Принудительно шифрование на Андроид осуществляется через ядро, которое запускает процесс шифрования всего раздела с данными при первойзагрузке.
Что бы отключить принудительное шифрование при загрузке, сначала нужно получить модифицированный boot.img у которого отключена проверка dm-verity.

Скрипт ниже позволяет отключить принудительное шифрование, но у вас остается возможно зашифровать устройство в ручном режиме.
Скрипт устанавливается как любой другой апдэйт для TWRP.

Доброго времени суток. Сегодня тоже пробовал на заблокированном Индию, не получилось, пробовал качать с разных мест. Может кто подскажет как прошить индию на заблокированном пошагово.
4\64 глобалка PCNMIXM. Может это только на разблокированном можно, нет смысла мучиться пока не будет разблокировки?

Источник

E unable to decrypt fbe device что это

boltaevruslan,
индийскую ставь там есть.
только загрузчик сначала разблокируй!

makar42, makar42, makar42,

А Индийскую где можно скачать? Подскажи пожалуйста.

boltaevruslan,
Читайте посты внимательно! Вам всё написали, не нужно строчить в теме как в чате.

Что такое dm-verity?

Что такое forced encryption (принудительное шифрование)?

Источник

MIUI 11.2 20.1.16/21 v3

surfcaster1

Members

Disable Voice match in Google Assistant. It will work again. This is a bug when updating to Android 10. Soon it will fix in the next updates.

Sent from my Redmi Note 7 using Tapatalk

Vagelis74

Members

The same problem for me, it’s very smooth rom and with very good BB, any fix or solution?

Στάλθηκε από το Redmi Note 7 μου χρησιμοποιώντας Tapatalk

TECHMANGURU

Members

TECHMANGURU

Members

Disable Voice match in Google Assistant. It will work again. This is a bug when updating to Android 10. Soon it will fix in the next updates.

Sent from my Redmi Note 7 using Tapatalk

Domingo!!

Members

Contact pictures is not sync complete with google contacts. The picures is small and not show on full screen when I have incoming call.
Even if I resubmit a photo, it becomes small again when synced.
This was not the case with Android 9

redzwhen

Members

Well that’s not the case for me. My Lavender earpiece is fine and normal.

Sent from my Redmi Note 7 using Tapatalk

surfcaster1

Members

guerrierodipace

Members

The latest TWRP from the latest update don’t decrypt my data
So I can not install the update

Gesendet von meinem MIX 3 mit Tapatalk

Vagelis74

Members

Clean flash again and it’s ok?

Στάλθηκε από το Redmi Note 7 μου χρησιμοποιώντας Tapatalk

Poney70

Donator

guerrierodipace

Members

guerrierodipace

Members

the problem now is when I install ROM after cleaned DATA start messagge:
E:unhandled flag: «wrappedkey»
E: unable to decrypt FBE device

After that the instalation follw but when restart the device boot always in twrp

Poney70

Donator

the problem now is when I install ROM after cleaned DATA start messagge:
E:unhandled flag: «wrappedkey»
E: unable to decrypt FBE device

After that the instalation follw but when restart the device boot always in twrp

E:unhandled flag: «wrappedkey» = not an issue, it’s a tiny Official TWRP bug.

E: unable to decrypt FBE device = means your device is not encrypted, it will be encrypted after first system boot so. not an issue too.

«Format Data» =/= Wipe /data, no mistake here?

Did you flash K20 to Mi 9T conversion patch before?

guerrierodipace

Members

E:unhandled flag: «wrappedkey» = not an issue, it’s a tiny Official TWRP bug.

E: unable to decrypt FBE device = means your device is not encrypted, it will be encrypted after first system boot so. not an issue too.

«Format Data» =/= Wipe /data, no mistake here?

Did you flash K20 to Mi 9T conversion patch before?

Poney70

Donator

No, you don’t need it.

So, you can try to flash the previous ROM version. I really don’t know why your device can’t boot.

guerrierodipace

Members

No, you don’t need it.

So, you can try to flash the previous ROM version. I really don’t know why your device can’t boot.

Ofir Gan

Members

MI CC9/Mi 9 lite Tapatalk

jose_ramon_navar

Members

And the reboot after swipe with Gboard?

Enviado desde mi Redmi K20 Pro mediante Tapatalk

Sielski

Members

Sielski

Members

And the reboot after swipe with Gboard?

Enviado desde mi Redmi K20 Pro mediante Tapatalk

stalvatero

Members

Just installed the ROM on the MI 9 Lite. I had a problem with the official TWRP because during the FORMAT / data step it did not rebuild the data folder and therefore I was unable to install the Rom. I had to change the recovery to an unofficial one and everything went well. The first impressions compared to the Global I came from, haven’t changed many things, some new features and animation but no wow effect. Indeed it bothers me that it is not well translated into Italian with many parts in English. Not that it is a problem but there is no graphic consistency. I also noticed that in general the UI has many micro lag. The battery seems to go down faster and this morning I had serious difficulties with the GPS which managed to lock the signal after about 5 minutes. Afterwards I actually had no more problems with GPS. Spotify often stops songs as a lost of mobile data. Also the wifi signal seems slightly weaker to me. In short, even if there are many interesting goodies that I have found, I believe that for now I will return with the global that seems more balanced.
Anyway greetings for the great work on Xiaomi devices.

Inviato dal mio MI CC 9 utilizzando Tapatalk

Alan098765

Members

Inviato dal mio MI CC 9 utilizzando Tapatalk

My battery wasn’t good for a day or two, now its very good, all’s running smoothly on my cc9

Источник

Development [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project

Breadcrumb

jeehuu91

Senior Member

Please help. Installed TWRP. Did
1. Format Data
2. Wipe Dalvik & Cache
3. Tried installing ROM

Pls see attached for error. Pls advise how to fix. Thanks

Just reboot the recovery and try to flash the rom again.

Got to Reboot > Recovery

iooxda

Senior Member

I am trying to automate some common TWRP tasks. I see TWRP has command line support here: https://twrp.me/faq/openrecoveryscript.html.

I would like to launch the TWRP terminal and run a shell script when TWRP starts. If this isn’t possible then I would like to just run a twrp command or series of commands when TWRP starts.

as either the place to put the script or the twrp command. Does anyone know how this works?

I tried MANY different combinations of the following:

I can’t get the syntax correct, nothing seems to start when I launch TWPR. Nebrassy or others with experience can you explain a bit more how I can run a script automatically when TWPR starts?

Other than that FAQ page I linked above and two vague references there doesn’t seem to be any otherreference to the «Open Recovery Script» system and how it works in TRWP.

kazi69

Member

iooxda

Senior Member

I have run into some problems with my recovery. I am no longer able to decrypt the data partition. I am seeing several errors:

even though Lineage is installed and there is a valid data partition.

If I try to flash Magisk I get:

. and Magisk does install however when I boot recovery it no longer automatically asks for a password to decrypt the data partition. If I try to use the decrypt data button I get:

I also get this error if I try to wipe the data partition.

I did try to format data several times, wiped data, cache, davilk, install firmware and flash LineageOS. The OS installs properly, I can setup a password which it asks for when booting into the OS but my recovery can no longer decrypt data. It used to prompt for the password automatically.

I am not sure what happened, this phone has been working without problems and I have been able to flash many different ROMs, Magisk, format data several times previously but something happened this last time.

Even though Lineage is still installed.

Any ideas on how I can recover from this? If I do this, shouldn’t it fix the problem:

What is this default password it it is asking for. Does this default password exist somewhere outside of the data partition? Why can the OS decrypt the data but recovery can’t?

How can I get recovery to prompt for a password again automatically when I boot into it?

I am running 3.5.2_11-Nebrassy version.

iooxda

Senior Member

Okay I have tried many different attempts. Different ROMs, formatting data, wiping cache, data etc. I also tried booting from the two older older Nebrassy TWRP images from fastboot etc. Nothing works, TWRP never prompts to decrypt the data anymore and I can’t decrypt it manually either. I see this message as soon as I boot into TWRP so this is the root cause:

From the /tmp/recovery.log there is more detail:

These two look like the key log entries:

fscrypt_initialize_systemwide_keys returned fail

E:fde::get_crypt_ftr_and_key::Unexpected value for crypto key location:

E:Error getting crypt footer and keyE:Could not get footerFailed to decrypt data.

I can see there are key files mentioned in the metadata partion. If I format data and install a new ROM, I get the same results, always failed to decrypt FBE device. It doesn’t matter if the ROM has a password set or not. Any ideas on what has happened or how to recover from this? Nebrassy?

Nebrassy

Recognized Developer

From the /tmp/recovery.log there is more detail:

These two look like the key log entries:

fscrypt_initialize_systemwide_keys returned fail

E:fde::get_crypt_ftr_and_key::Unexpected value for crypto key location:

E:Error getting crypt footer and keyE:Could not get footerFailed to decrypt data.

cldkrs

Senior Member

inglar2k

Member

@Nebrassy, what does it mean «E: Unable to decrypt FBE device»?
ROM has been installed successfully and working properly, but why this error appears in log?

Supermatt01

Senior Member

rzfndrkt

New member

WhereIsMyROM

Member

I am also facing the same issue as @rzfndrkt i.e. TWRP is being overwritten by stock MIUI recovery.

Here is the process that I followed:
1) Unlock bootloader
2) Flash recovery using minimal adb (Command: fastboot flash recovery recovery.img)
3) Boot to TWRP after successfully flashing

But as soon as i try to boot into system and then again to recovery I am welcomed by MIUI recovery instead of TWRP.

I have successfully followed the above steps to flash TWRP in my Redmi Note 4 and Poco F1 without any issues.

I also tried to follow certain tutorials one of which said to do the following procedure:
1) Unlock bootloader
2) Then use minimal adb to and type fastboot boot recovery.img and then in TWRP->Advanced->Flash current recovery. But this option is simply missing. Maybe the option has been removed (not sure).

BTW mine is Indian unit of Redmi Note 10 pro (I think its called sweetin).

Also, please let me know if I missed something or if any more info is needed.

Laptapper

Senior Member

I am also facing the same issue as @rzfndrkt i.e. TWRP is being overwritten by stock MIUI recovery.

Here is the process that I followed:
1) Unlock bootloader
2) Flash recovery using minimal adb (Command: fastboot flash recovery recovery.img)
3) Boot to TWRP after successfully flashing

But as soon as i try to boot into system and then again to recovery I am welcomed by MIUI recovery instead of TWRP.

I have successfully followed the above steps to flash TWRP in my Redmi Note 4 and Poco F1 without any issues.

BTW mine is Indian unit of Redmi Note 10 pro (I think its called sweetin).

Also, please let me know if I missed something or if any more info is needed.

Please try ro flash twrp via adb (before that: developer settings usb debug on)
After Flashing don’t restart via adb, instead use hardware buttons to reboot in recovery
Then afterwards directly format data in twrp with yes, reboot twrp, flashing ROM gapps magisk.
Format data with yes again and reboot, ignore failures, reboot give time

[email protected]

Senior Member

I am also facing the same issue as @rzfndrkt i.e. TWRP is being overwritten by stock MIUI recovery.

Here is the process that I followed:
1) Unlock bootloader
2) Flash recovery using minimal adb (Command: fastboot flash recovery recovery.img)
3) Boot to TWRP after successfully flashing

But as soon as i try to boot into system and then again to recovery I am welcomed by MIUI recovery instead of TWRP.

I have successfully followed the above steps to flash TWRP in my Redmi Note 4 and Poco F1 without any issues.

BTW mine is Indian unit of Redmi Note 10 pro (I think its called sweetin).

Also, please let me know if I missed something or if any more info is needed.

WhereIsMyROM

Member

Thank you @Laptapper and @ [email protected] for your prompt responses.

I tried the procedure you mentioned but now there is a new problem, after TWRP is flashed (from adb) and I boot into recovery via hardware buttons and format data (with yes), I can no longer see my internal storage on my pc which means i cannot copy ROMs, Gapps etc.

I also tried rebooting to recovery after format data and the result is same, still my internal storage is not detected

I even deleted Dalvik/ART cache, Cache, Data and then again did format data and then rebooted to recovery only to find that nothing changed

Ok I will try that once my internal storage is detected somehow.

Laptapper

Senior Member

Thank you @Laptapper and @ [email protected] for your prompt responses.

I also tried rebooting to recovery after format data and the result is same, still my internal storage is not detected

I even deleted Dalvik/ART cache, Cache, Data and then again did format data and then rebooted to recovery only to find that nothing changed

Ok I will try that once my internal storage is detected somehow.

WhereIsMyROM

Member

Thanks for the super quick responses @Laptapper

So I tried flashing ROM from sd card as you suggested and I get an error. I have attached a pic of error.

I am going to try OrangeFox and let you know if that works or not.

Please let me know if you need any more info.

EDIT:
I tried OrangeFox just now and it works without any errors. I successfully flashed crdroid and flamegapps. So I can confirm that nothing is wrong with my device. But I still cannot understand why TWRP doesn’t work. It is my favorite recovery and I would really like to use it.

Attachments

ZainBilq

Senior Member

Thanks for the super quick responses @Laptapper

So I tried flashing ROM from sd card as you suggested and I get an error. I have attached a pic of error.

I am going to try OrangeFox and let you know if that works or not.

Super Partition or something is damaged. You need to flash stock or any other MIUI ROM which has fix for not damaging partition.

WhereIsMyROM

Member

Super Partition or something is damaged. You need to flash stock or any other MIUI ROM which has fix for not damaging partition.

But out of curiosity, why doesn’t OrangeFox show any errors, tried it just now and successfully flashed CrDroid and FlameGapps. I mean if a partition is damaged or something then shouldn’t OrangeFox also throw errors since it uses codebase from TWRP.

Laptapper

Senior Member

Thanks for the super quick responses @Laptapper

So I tried flashing ROM from sd card as you suggested and I get an error. I have attached a pic of error.

I am going to try OrangeFox and let you know if that works or not.

Please let me know if you need any more info.

fmrogonhantu

Member

ive got issue when flashing zip file.twrp will restart when im trying to flash any zip file

then it shows internal and sd card 0mb? when trying to boot to system it says no os installed.

it works just fine before.

Similar threads

Breadcrumb

Xiaomi Redmi Note 10 Pro

Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage

In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.

We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.

If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.

Hello, this is TWRP, for Redmi note 10 Pro Global/Indian/Indian Pro Max (sweet/sweetin)

touch and adb work
SD card and USB OTG are working
Decryption is working

Источник