Reboot recovery cause is unknown как исправить

Несколько советов если не можете зайти в меню Рекавери на своем Андроиде (телефон или планшет). Проблема решена

Можно пользоваться Android и никогда не заходить в Recovery Menu. Но если телефон не включается и не заходит в Рекавери, или вы хотели установить кастомную прошивку, то придется понять причины нежелания устройства запускать инженерное меню.

Данная статья подходит для всех брендов, выпускающих телефоны на Android 11/10/9/8: Samsung, HTC, Lenovo, LG, Sony, ZTE, Huawei, Meizu, Fly, Alcatel, Xiaomi, Nokia и прочие. Мы не несем ответственности за ваши действия.

Внимание! Вы можете задать свой вопрос специалисту в конце статьи.

Содержание

  1. Почему Android не заходит в Recovery?
  2. Как зайти в Recovery Menu
  3. Возможности Recovery

На некоторых смартфонах вообще нет официального Recovery, так что приходится сразу устанавливать кастомное. Если на экране появляется надпись «Команды нет» с лежащим роботом, это значит, что Recovery есть, но при его запуске возникли проблемы. Чтобы устранить неполадку, быстро нажмите на кнопку включения и клавишу увеличения громкости.

Android не загружается в режиме Recovery

Если Android категорически не загружается в Рекавери, то причиной такого поведения может быть ошибка, устранить которую можно также установкой кастомного Recovery. Если установка кастомного Recovery не помогает, следует обратиться в сервисный центр — возможно, имеет место аппаратное повреждение, устранить которое программными методами невозможно.

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

Android не загружается в режиме RecoveryНужна помощь?

Не знаешь как решить проблему в работе своего гаджета и нужен совет специалиста? На вопросы отвечает Алексей, мастер по ремонту смартфонов и планшетов в сервисном центре.Напиши мне »

Сочетания клавиш для входа в Recovery на разных телефонах:

  • Lenovo — «Громкость +» и «Вкл.».
  • HTC – «Громкость -» и «Вкл.» или «Громкость +» и «Вкл.».
  • Samsung — «Домой», «Громкость +» и «Вкл.» зажать одновременно.
  • Meizu — «Вкл.» и «Громкость +».
  • Xiaomi — «Вкл.» и «Громкость +».
  • Fly — «Вкл.» и «Громкость +» или «Вкл.» и «Громкость -».
  • ASUS — «Вкл.» и «Громкость +» или «Вкл.» и «Громкость -».

вход в рекавери андроид

Если сочетание не работает, и телефон не заходит, попробуйте поискать комбинацию конкретно для своей модели. Есть и универсальные способы запуска Recovery – с помощью компьютера или специальных приложений. Если под рукой есть компьютер:

  1. Скачайте и инсталлируйте ADB и драйверы телефона.
  2. Подключите Android через USB, включите отладку.
  3. Запустите ADB и выполните команду «adb reboot recovery».

Android не загружается в режиме Recovery

Что делать, если компьютера нет? Установите приложение Boot Droid. В нем нужно выбрать значок «Recovery» и нажать «Yes».

Android не загружается в режиме Recovery

Попасть в Recovery можно и с помощью Terminal Emulator. Наберите в нем «su», предоставьте root-доступ и выполните команду «reboot recovery».

Читайте FastBoot Mode — что это на Android

Возможности Recovery

Возможности Recovery Mode отличаются в зависимости от вида. Если это официальное меню восстановления, то функциональность будет не самая высокая:

  • Перезагрузка для запуска Android в обычном режиме.
  • Установка обновлений.
  • Сброс к заводскому состоянию.
  • Очистка кэша.
  • Создание резервной копии и восстановление данных.

меню recovery

В кастомном меню (установленном пользователем) возможностей больше. Кроме функций официального Recovery, кастомное предлагает:

  • Установку сторонних прошивок.
  • Создание образа восстановления Андроид.
  • Очистку отдельных разделов.
  • Возвращение телефона в исходное состояние без потери данных.
  • Восстановление прав системных приложений и т.д.

Кастомные Recovery тоже бывают разными. Самыми популярными являются CWM и TWRP. При выборе следует учитывать модель телефона и желаемую функциональность. Но если вы не собираетесь устанавливать стороннюю прошивку, то можно вполне обойтись и возможностями официального Recovery.

Мастер Николай

АвторМастер Николай

Инженер по ремонту мобильной и компьютерной техники в специализированном сервисном центре, г. Москва. Непрерывный опыт работы с 2010 года.
Есть вопросы? Задавайте в комментариях к статье. Отвечать стараюсь максимально быстро вам на указанную почту. Каждый случай индивидуален и поэтому очень важно, чтобы вы максимально расписали свою проблему и какая у вас модель устройства.

  1. DeviSn0w



    Thread Starter

    Hello Guys!
    i have Galaxy S7 (SM-G930F)
    blocked by FRP
    Oreo 8.0.0
    Stuck On Samsung Logo
    i tried many time to upgrade by many firmware (Binary 5)
    After Flash passed with Odin
    phone reboot
    Erasing…
    boot to recovery mode and i have this error :
    #fail to open recovery_cause (no such file or directory)#
    #Reboot recovery_cause is [unknown]#
    No support SINGLE-SKU file-based OTA
    Supported OTA
    Supported API: 3
    dm-verity verification failed…

    when i put my phone in Download mode and i tried to root or to flash with TWRP
    it shown me this error :
    Costum Binary Blocked by frp lock

    i tried to Wipe Partiotion & wipe cashe
    same problem
    i loosed my mind
    please help me


    1. Download the Forums for Android™ app!

      Download

  2. You need the Gmail account and password.
    There is no work around

  3. DeviSn0w



    Thread Starter

    i can i reset my gmail password
    but he is now stuck on samsung logo

  4. svim

    svim

    Extreme Android User

    Your statement on using ‘many firmware’ and the Binary 5 error message both indicate you’re not using the correct ROM. They are not interchangeable and you should never just try to mix-and-match different ROMs. Use only the Samsung stock ROM that matches your specific model (SM-G930F) and your carrier.
    Every phone model has its own, unique hardware configuration (different internal components) so while they make look similar on the outside, there’s a lot of variance on what’s inside. Each ROM is created to match that specific hardware so using a ROMs for other models (even if it has a model I.D. that’s ‘similar’) will result in Odin showing some kind of ‘binary’ error message. The errors referring to the Recovery might also be tied to this issue — when you’re flashing a new stock ROM this also installs a new stock Recovery. So if you did have TWRP installed previously, after a successful flashing your S7 will have a stock Samsung Recovery again.
    So try again but be very selective about which ROM you download. Another thing to make note of is any kind of error message during the download. That binary error message might be attributed to a corrupted download.

  5. DeviSn0w



    Thread Starter

    Thank’s for reply but everything is okey bro
    i find the correct ROM
    the only problem that i had is :
    after flashing with odin my phone reboot automaticaly to recovery mode and show this error

    #fail to open recovery_cause (no such file or directory)#
    #Reboot recovery_cause is [unknown]#
    No support SINGLE-SKU file-based OTA
    Supported OTA
    Supported API: 3
    dm-verity verification failed…

    when i reboot my phone stuck at Samsung logo

    and like i sayed my phone is frp locked so i can’t flash with TWRP or anything else

  6. svim

    svim

    Extreme Android User

    A corrupt or missing Recovery and always booting up with the Samsung logo are both are common indicators the ROM that was used is either the wrong one or bad, and needs to re-flashed. Again, try re-downloading the ROM and re-flash. If the same problem occurs using a newly downloaded ROM, that’s a sign it’s probably not a software issue but could be a hardware issue (i.e. internal storage chip is failing).

  7. DeviSn0w



    Thread Starter

    how to find the best ROM for my device ?
    you can’t say that there is a hardware problem because all things are working in my phone only the Bootloader

  8. I’m on my phone but sammobile should have your firmware. But again YOU NEED TO MAKE SURE THE ROM MATCHES EXACTLY YOUR SPECIFIC MODEL for your phone.

  9. svim

    svim

    Extreme Android User

    Try either:
    https://updato.com/firmware-archive-select-model/?q=SM-G930F&exact=1&r=&v=&rpp=100
    or
    https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/
    Both are reputable sources for Samsung stock ROMs and claim to verify the validity of their downloads. (… also note that you need to sign up for an account to get unfettered access, otherwise they intentionally limit the bandwidth speed of their download servers for everyone else.)

    Regarding something like the internal storage chip failing, note that the operating system and Recovery are stored there so the issue with only seeing that Samsung logo on screen is just part of the Samsung firmware that is in its own chip. The internal storage is read and write, something like the firmware will be read only. The issue being since you cannot get a working OS or even Recovery successfully flashed that’s likely attributed to using an incorrect ROM, a problem doing the flashing process, or a hardware error. The hardware suggestion is just supposition, but it could be proven wrong if you take your phone to a reputable service shop and have them flash your device for you. This might be the best measure anyway as you might still have issues tied to the FRP lock as you still need to authenticate your ownership of the device.

  10. DeviSn0w



    Thread Starter

    Bro i tried 6 or 7 firmwares
    Still the same problem
    stuck on Samsung Logo
    my problem is after flashing the mobile phone
    the phone reboot to recovery mode and show me this error

    #fail to open recovery_cause (no such file or directory)#
    #Reboot recovery_cause is [unknown]#
    No support SINGLE-SKU file-based OTA
    Supported OTA
    Supported API: 3
    dm-verity verification failed…

    i need to solve this problem as i think everything will be ok
    Please Please
    the reputable service shop says :
    your phone doesn’t accept the Flash
    try by your self or change the motherboard
    but everything is okay in my motherboard im sure

  11. bcrichster

    Moderator

    Listen…

    • Flash the correct factory firmware (NOT TWRP or ROM) and you should be able to access the FRP password section.
    • Enter the correct pswd and boot to main OS.
    • Go into Settings-Accounts-Google and remove the account.
    • NOW ya should be able to flash TWRP and appropriate ROM..

    You cannot bypass FRP until you’ve installed the correct FW and entered the correct pswd. Period.

    One last thing: You CANNOT install TWRP or ROM in any USA model Galaxy S7 due to the fact that they are ALL bootloader locked! You actually need the International version with Exynos chips to do so. If you’re on any Verizon Wireless device, just hang up any possibility of custom ROMs, even if it’s a Google Pixel phone. That’s just how VZW is on that..

    Edit: Derp Lol.. Just seen you have the «F» model.. = Int’l


    ocnbrze and svim like this.

Share This Page

Old
11-17-2019, 00:19

 
#1 (permalink)

errorcode999

Freak Poster

 

Join Date: Oct 2010

Posts: 260

Member: 1422819

Status: Offline

Thanks Meter: 42

S8 Flashing issue Need Help


Oem lock is on, frp is off. Tried the below flashing firmwares but still phone is in bootloop

G950FXXS5DSJ1_G950FOXM5DSHC_G950FXXU5DSH3_G950FXXS 5DSJ1_BTU
G950FXXS5DSJ1_G950FOXM5DSHC_G950FXXU5DSH3_G950FXXS 5DSJ1_XEU

unable to attach pic. the message appears on the screen is

#fail to open recovery_cause (No such file or directory) #
#reboot recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed …
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : ‘/ proc / device-tree / firmware / android / compatible’: No such file or directory

 

Reply With Quote
Old
11-17-2019, 00:41

 
#2 (permalink)

amleto90

Product Supporter

 

Join Date: Aug 2016

Posts: 2,344

Member: 2613252

Status: Offline

Thanks Meter: 1,835

Quote:

Originally Posted by errorcode999 View Post

Oem lock is on, frp is off. Tried the below flashing firmwares but still phone is in bootloop

G950FXXS5DSJ1_G950FOXM5DSHC_G950FXXU5DSH3_G950FXXS 5DSJ1_BTU
G950FXXS5DSJ1_G950FOXM5DSHC_G950FXXU5DSH3_G950FXXS 5DSJ1_XEU

unable to attach pic. the message appears on the screen is

#fail to open recovery_cause (No such file or directory) #
#reboot recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed …
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : ‘/ proc / device-tree / firmware / android / compatible’: No such file or directory

Hello, phone enter in recovery mode?

if you read the error screen you wrote it should be in recovery mode and has the drk error
dm-verity verification failed …

 

Reply With Quote
Old
11-17-2019, 01:02

 
#3 (permalink)

errorcode999

Freak Poster

 

Join Date: Oct 2010

Posts: 260

Member: 1422819

Status: Offline

Thanks Meter: 42

thanks for the quick reply, yes i can enter into the recovery mode.

is there any solution to fix this drk or dm-verity error ?

 

Reply With Quote
Old
11-17-2019, 01:17

 
#4 (permalink)

amleto90

Product Supporter

 

Join Date: Aug 2016

Posts: 2,344

Member: 2613252

Status: Offline

Thanks Meter: 1,835

Quote:

Originally Posted by errorcode999 View Post

thanks for the quick reply, yes i can enter into the recovery mode.

is there any solution to fix this drk or dm-verity error ?

put the phone in download mode and check rmm state and knox guard would be kg state, if rmm is prenormal or kg state nom be on

this is the guide for drk fix for g950f but download file g950f u5 fix drk frp: on rmm: on

https://www.full-repair-firmware.com…g950f.html?m=1

 

Reply With Quote
Old
11-17-2019, 11:47

 
#5 (permalink)

errorcode999

Freak Poster

 

Join Date: Oct 2010

Posts: 260

Member: 1422819

Status: Offline

Thanks Meter: 42

Thanks, cant see rmm in download mode, also kg state is checking. I have tried few other u5 firmwares without cache but still the phone is in boot loop. The links inside the page are not working.

 

Reply With Quote
Old
11-17-2019, 12:12

 
#6 (permalink)

amleto90

Product Supporter

 

Join Date: Aug 2016

Posts: 2,344

Member: 2613252

Status: Offline

Thanks Meter: 1,835

Quote:

Originally Posted by errorcode999 View Post

Thanks, cant see rmm in download mode, also kg state is checking. I have tried few other u5 firmwares without cache but still the phone is in boot loop. The links inside the page are not working.

the download links of the files work you just have to perform some steps to download to me from no problem looks

https://mega.nz/#!20NE3aDD!hSg0qs-Ej…fC4vxs-sqI8IBg

 

Reply With Quote
Old
11-17-2019, 12:14

 
#7 (permalink)

amleto90

Product Supporter

 

Join Date: Aug 2016

Posts: 2,344

Member: 2613252

Status: Offline

Thanks Meter: 1,835

Quote:

Originally Posted by errorcode999 View Post

Thanks, cant see rmm in download mode, also kg state is checking. I have tried few other u5 firmwares without cache but still the phone is in boot loop. The links inside the page are not working.

the download links of the files work you just have to perform some steps to download to me from no problem looks

https://mega.nz/#!20NE3aDD!hSg0qs-Ej…fC4vxs-sqI8IBg

 

Reply With Quote
Old
11-18-2019, 20:46

 
#8 (permalink)

errorcode999

Freak Poster

 

Join Date: Oct 2010

Posts: 260

Member: 1422819

Status: Offline

Thanks Meter: 42

thanks, it worked but the problem is i cant do hard reset or even after restart it goes to recovery and gives the same error. Any solution for this ?

 

Reply With Quote
Old
11-18-2019, 20:59

 
#9 (permalink)

amleto90

Product Supporter

 

Join Date: Aug 2016

Posts: 2,344

Member: 2613252

Status: Offline

Thanks Meter: 1,835

Quote:

Originally Posted by errorcode999 View Post

thanks, it worked but the problem is i cant do hard reset or even after restart it goes to recovery and gives the same error. Any solution for this ?

you have read and followed the link guide you need to make two flashes of the drk fix u5 file for g950f and then extract from the stock firmware of the phone with 7zip software the system.img file and rename it to tar format and then flash the file?

post screenshots here to see what kind of error appears on the phone screen in recovery mode

 

Reply With Quote
Old
11-18-2019, 21:30

 
#10 (permalink)

amleto90

Product Supporter

 

Join Date: Aug 2016

Posts: 2,344

Member: 2613252

Status: Offline

Thanks Meter: 1,835

Quote:

Originally Posted by errorcode999 View Post

thanks, it worked but the problem is i cant do hard reset or even after restart it goes to recovery and gives the same error. Any solution for this ?

read this post by xda developers has your same problem but oem: off and frp: off and rmm state: off.

https://forum.xda-developers.com/gal…creen-t3906627

It solved using the root twrp by flashing the filen or verity encrypted for fix drk, but it had oem: off, to root twrp like te oem: on.

If you have oem: for sure you cannot root twrp, but if you want to try doing it you do it at your own risk if you damage the phone

 

Reply With Quote
Old
11-18-2019, 22:44

 
#11 (permalink)

errorcode999

Freak Poster

 

Join Date: Oct 2010

Posts: 260

Member: 1422819

Status: Offline

Thanks Meter: 42

thanks, following are the steps i followed
downloaded drk file and flashed in BL
downloaded repair u5 firmware and then extracted system.img, made .tar and flashed in AP

Phone boots fine but as soon as i restart or hard reset it gives the same old error and boots into recovery.

#fail to open recovery_cause (No such file or directory) #
#reboot recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed …
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : ‘/ proc / device-tree / firmware / android / compatible’: No such file or directory

 

Reply With Quote

The Following User Says Thank You to errorcode999 For This Useful Post:

Понравилась статья? Поделить с друзьями:
  • Realmlist wtf как изменить
  • Reading package lists error debian
  • Read from disk ошибка торрента как исправить
  • React nestjs cors error
  • Rdr 2 ошибка автосохранение что делать