Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a Boot Loop on my Samsung Galaxy Tab A8
Message:
Failed to load locales from the recource files, failed to compare
#Reboot Recovery Cause is [UNKNOWN]#
#Reason is []#
E:Failed to load bitmap installing_text for locale en-US (error -1)
Support API: 3
# MANUAL MODE v1.0.0#
No command specified.
- boot loop
-
All forum topics -
Previous Topic -
Next Topic
1 Solution
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It looks like you’re experiencing a boot loop issue on your Samsung Galaxy Tab A8. This is a common issue where the device is stuck in a loop and cannot start up properly. The error message suggests that there is an issue with loading some files and comparing them.
Here are a few steps that may help resolve the issue:
-
Boot into Recovery Mode: Press and hold the Volume Up, Power and Home buttons together until the Samsung logo appears, then release the Power button and continue holding the Volume Up and Home buttons. You should see the Recovery Mode screen.
-
Wipe cache partition: In Recovery Mode, navigate to «wipe cache partition» and select it. This will erase the cached data, but it won’t delete any personal files or settings.
-
Factory Reset: If wiping the cache partition doesn’t help, you can try a factory reset. To do this, navigate to «factory reset» in Recovery Mode and select it. Note that this will erase all data, apps, and settings from the device.
If these steps don’t work, it may be necessary to contact Samsung Support for further assistance
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It looks like you’re experiencing a boot loop issue on your Samsung Galaxy Tab A8. This is a common issue where the device is stuck in a loop and cannot start up properly. The error message suggests that there is an issue with loading some files and comparing them.
Here are a few steps that may help resolve the issue:
-
Boot into Recovery Mode: Press and hold the Volume Up, Power and Home buttons together until the Samsung logo appears, then release the Power button and continue holding the Volume Up and Home buttons. You should see the Recovery Mode screen.
-
Wipe cache partition: In Recovery Mode, navigate to «wipe cache partition» and select it. This will erase the cached data, but it won’t delete any personal files or settings.
-
Factory Reset: If wiping the cache partition doesn’t help, you can try a factory reset. To do this, navigate to «factory reset» in Recovery Mode and select it. Note that this will erase all data, apps, and settings from the device.
If these steps don’t work, it may be necessary to contact Samsung Support for further assistance
-
#1
I have tried flashing the latest firmware with the correct carrier using Odin but this has not worked.
Error message on the recovery screen
#fail to open recovery_cause (No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]
#Support SINGLE-SKU
File-Based OTASupported 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
-
#2
where did you get the firmware? sammobile? are you sure it is the correct firmware? it has to be for the exact model you have.
-
#3
where did you get the firmware? sammobile? are you sure it is the correct firmware? it has to be for the exact model you have.
I got it from SamMobile, and I’m 100% sure it is the correct firmware.
-
#4
I got it from SamMobile, and I’m 100% sure it is the correct firmware.
ok is there a way for you to post a screenshot of the exact output from odin?
-
#5
ok is there a way for you to post a screenshot of the exact output from odin?
This is the log in Odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6151 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> up_param.bin
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> userdata.img
<ID:0/006> dqmdbg.img
<ID:0/006> modem.bin
<ID:0/006> modem_debug.bin
<ID:0/006> cache.img
<ID:0/006> omr.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port …. 0
<OSM> All threads completed. (succeed 1 / failed 0)
-
#6
This is the log in Odin:
<OSM> All threads completed. (succeed 1 / failed 0)
well it seems to have worked. i did not see any errors on this run.
care to explain how your phone is? what happened to it when this all happened? the more info we have, the better we can help.
-
#7
well it seems to have worked. i did not see any errors on this run.
care to explain how your phone is? what happened to it when this all happened? the more info we have, the better we can help.
After the Odin flash, the phone reboots into the Installing system update screen. It gets up to 32% then says erasing. The phone reboots again where it says installing a system update, then it says no command with a yellow caution sign and then it goes into the recovery screen.
-
#8
After the Odin flash, the phone reboots into the Installing system update screen. It gets up to 32% then says erasing. The phone reboots again where it says installing a system update, then it says no command with a yellow caution sign and then it goes into the recovery screen.
what happened to the phone when all this happened? was this random? after an update? were you trying to root the phone?
-
#9
what happened to the phone when all this happened? was this random? after an update? were you trying to root the phone?
The phone randomly started restarting itself and when I would shut it down, it would reboot. I tried to factory reset the phone but then it wouldn’t work. So I booted into recovery and cleared the cache and factory reset there and then it wouldn’t boot to the OS anymore, just boots into the recovery screen.
-
#10
The phone randomly started restarting itself and when I would shut it down, it would reboot. I tried to factory reset the phone but then it wouldn’t work. So I booted into recovery and cleared the cache and factory reset there and then it wouldn’t boot to the OS anymore, just boots into the recovery screen.
sounds like your system partitions are corrupted and if flashing a firmware update does not work, i’m afraid your phone is toast. this phone came out in 2017. i think its time to upgrade your phone.
Можно пользоваться Android и никогда не заходить в Recovery Menu. Но если телефон не включается и не заходит в Рекавери, или вы хотели установить кастомную прошивку, то придется понять причины нежелания устройства запускать инженерное меню.
Данная статья подходит для всех брендов, выпускающих телефоны на Android 11/10/9/8: Samsung, HTC, Lenovo, LG, Sony, ZTE, Huawei, Meizu, Fly, Alcatel, Xiaomi, Nokia и прочие. Мы не несем ответственности за ваши действия.
Внимание! Вы можете задать свой вопрос специалисту в конце статьи.
Содержание
- Почему Android не заходит в Recovery?
- Как зайти в Recovery Menu
- Возможности Recovery
На некоторых смартфонах вообще нет официального Recovery, так что приходится сразу устанавливать кастомное. Если на экране появляется надпись «Команды нет» с лежащим роботом, это значит, что Recovery есть, но при его запуске возникли проблемы. Чтобы устранить неполадку, быстро нажмите на кнопку включения и клавишу увеличения громкости.
Если Android категорически не загружается в Рекавери, то причиной такого поведения может быть ошибка, устранить которую можно также установкой кастомного Recovery. Если установка кастомного Recovery не помогает, следует обратиться в сервисный центр — возможно, имеет место аппаратное повреждение, устранить которое программными методами невозможно.
Порядок входа отличается в зависимости от производителя мобильного устройства. Чтобы попасть в Recovery, нужно сначала выключить телефона, а затем зажать определенное сочетание клавиш. Сенсор в меню не работает, управление осуществляется клавишами громкости и кнопкой питания. Не следует путать Recovery и безопасный режим, в котором просто отключаются все сторонние приложения. Recovery – это, скорее, инженерное меню для управления телефоном в обход системы.
Нужна помощь?
Не знаешь как решить проблему в работе своего гаджета и нужен совет специалиста? На вопросы отвечает Алексей, мастер по ремонту смартфонов и планшетов в сервисном центре.Напиши мне »
Сочетания клавиш для входа в Recovery на разных телефонах:
- Lenovo — «Громкость +» и «Вкл.».
- HTC – «Громкость -» и «Вкл.» или «Громкость +» и «Вкл.».
- Samsung — «Домой», «Громкость +» и «Вкл.» зажать одновременно.
- Meizu — «Вкл.» и «Громкость +».
- Xiaomi — «Вкл.» и «Громкость +».
- Fly — «Вкл.» и «Громкость +» или «Вкл.» и «Громкость -».
- ASUS — «Вкл.» и «Громкость +» или «Вкл.» и «Громкость -».
Если сочетание не работает, и телефон не заходит, попробуйте поискать комбинацию конкретно для своей модели. Есть и универсальные способы запуска Recovery – с помощью компьютера или специальных приложений. Если под рукой есть компьютер:
- Скачайте и инсталлируйте ADB и драйверы телефона.
- Подключите Android через USB, включите отладку.
- Запустите ADB и выполните команду «adb reboot recovery».
Что делать, если компьютера нет? Установите приложение Boot Droid. В нем нужно выбрать значок «Recovery» и нажать «Yes».
Попасть в Recovery можно и с помощью Terminal Emulator. Наберите в нем «su», предоставьте root-доступ и выполните команду «reboot recovery».
Читайте FastBoot Mode — что это на Android
Возможности Recovery Mode отличаются в зависимости от вида. Если это официальное меню восстановления, то функциональность будет не самая высокая:
- Перезагрузка для запуска Android в обычном режиме.
- Установка обновлений.
- Сброс к заводскому состоянию.
- Очистка кэша.
- Создание резервной копии и восстановление данных.
В кастомном меню (установленном пользователем) возможностей больше. Кроме функций официального Recovery, кастомное предлагает:
- Установку сторонних прошивок.
- Создание образа восстановления Андроид.
- Очистку отдельных разделов.
- Возвращение телефона в исходное состояние без потери данных.
- Восстановление прав системных приложений и т.д.
Кастомные Recovery тоже бывают разными. Самыми популярными являются CWM и TWRP. При выборе следует учитывать модель телефона и желаемую функциональность. Но если вы не собираетесь устанавливать стороннюю прошивку, то можно вполне обойтись и возможностями официального Recovery.
АвторМастер Николай
Инженер по ремонту мобильной и компьютерной техники в специализированном сервисном центре, г. Москва. Непрерывный опыт работы с 2010 года.
Есть вопросы? Задавайте в комментариях к статье. Отвечать стараюсь максимально быстро вам на указанную почту. Каждый случай индивидуален и поэтому очень важно, чтобы вы максимально расписали свою проблему и какая у вас модель устройства.
Galaxy s7 won’t boot. how to recover data? stuck boot loop — installing system update no command
-
Thread startermisstique
-
Start dateSep 27, 2021
You should upgrade or use an alternative browser.
-
#1
My phone is stock everything and not rooted etc. I was using my phone normally and all of a sudden it just froze. I haven’t had a system update from samsung/carrier in a long *** time and it’s been working fine until today. The battery was full and it was plugged in. It then tried to restart and got past the splash screen then the samsung animation came up and it froze half way through. then i tried to vol down + pwr and the screen just went off but the blue led stayed solid on. i pulled out the SD card. but no buttons worked and my pc wouldn’t recognize it so i unplugged it and left it alone. the phone did not get hot at any point.
the blue led finally went off (battery drained) and i tried to restart it and it froze again. I restarted it using vol + home + power and the android guy came on with the arrow on the stomach and it said «installing system update» then it changed to a dead android guy and said «no command» then after some seconds, went into the regular recovery menu:
Android Recovery
samsung/heroltebmc/heroltebmc
8.0.0/R16NW/G930W8VLS8CTI1
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Mount /system
View recovery logs
Run graphics test
Power off
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No support SINGLE-SKU
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
Successfully verified dmverity hash tree
E:Failed to clear BCB message: failed to find /misc partition
i tried to just use the wipe cache option and it said E:Failed to clear BCB message: failed to find /misc partition again and restarting just does the same thing: installing update. and then no command.
the most important thing to me is recovering my data off it, the phone can get chucked for all I care since it sucks!!!
how do i get my stuff of it before i try flashing things? i don’t want to corrupt my stuff before getting it off first. i can still get it to go into download mode and recovery menu. nothing else.
please and THANK YOU so much to anyone that can help
Last edited: Sep 28, 2021
-
#2
Regardless of what is actually wrong with the phone, if you can’t get into the Android operating system and get past your lock screen you won’t be getting any information off the phone. Android is designed this way for security, it’s the only way it’s safe to walk around with all the personal information we keep on our devices. Hate to say it but anything that wasn’t backed up is probably already lost.
-
- Feb 6, 2017
-
- 86,683
-
- 658
-
- 113
-
#3
You would need to try factory reset or install the firmware through odin. Which both will delete your data.
Im surprised u dint back up data more regularly for such important things and i cant help retrieve data but suggest you start backing up your device in future to avoid these things in multiple places .
-
#4
-
#5
my other post didn’t show up maybe because i linked to reddit but i tried the freezer thing and it kind of worked. i managed to get past the pin lock screen and into my phone but it rebooted before i could start getting stuff off it
1 — Get it shut down (If it’s in the boot loop then hold volume down / power / home buttons and select shut down).2 — Charge the battery to full
3 — Put it in the freezer for a good long time. 20 minutes. Get that sucker frozen
4 — Plug in an external battery pack to it, with the USB cable running outside of the freezer door to the battery. When it gets that cold I found that it had trouble reading power levels from the internal battery. The phone may tell you it is too cold to charge the battery and that it will resume charging when warm enough. Fine.
5 — Boot it up while it’s in the feezer
6 — Hopefully it boots and stays booted. Don’t take it out of the freezer. Mine rebooted within minutes of being taken out.
7 — Do whatever you need to do to back up your data while it’s in the freezer. I installed SMS backup and restore to backup my conversations, etc.
8 — Connect it to a laptop via the USB cable, mount it as a file system, and shut the freezer door again
9 — Copy off any data you may need
Yes, there is risk to freezing it. Condensation can form when it thaws, etc — but since it was basically dead anyway it was worth a shot, I’m glad it worked for me. I hope it does for you.
for now it wasn’t staying booted but I’m going to charge it more and then try. i think the battery is the problem it keeps saying random %s when it reboots but maybe that’s because it’s almost frozen, lol. it could be the motherboard too but at least my crap is still there. it’s just REALLY HARD to get.
Last edited: Sep 28, 2021
-
- Feb 6, 2017
-
- 86,683
-
- 658
-
- 113
-
#6
-
#7
-
- Feb 6, 2017
-
- 86,683
-
- 658
-
- 113
-
#8
Just wanted to post an update in case anyone comes across this and has a similar issue. THE FREEZER WORKED! I charged up the phone to full then I ran an extension cord with the charger to my phone and closed it in the freezer and booted the phone. And the phone just had to be cold enough to display the warning popup that it is too cold to charge the battery and that it will resume charging when warm enough. Then I ran smart switch to my new phone and got everything off of it. The phone rebooted at about 15% and I shat a brick but I rebooted it and it resumed where it left off, and FINISHED! I’M SO THANKFUL IT WORKED! Thank you to whoever came up with this crazy but smart idea!!!
Thanks for sharing your fix
Similar threads
- Advertising
- Cookies Policies
- Privacy
- Term & Conditions
Recovery error after updating to Oreo
On Tuesday, I flashed the last BTU firmware (Nougat) to receive Oreo update via OTA. All works fine, no bootloops, no overheating.. but when I went to wipe data/cache after OTA update, I saw this on recovery:
fail to open recovery_cause(No such file or directory)#
Reboot Recovery Cause is [UNKNOWN]# No Support SINGLE-SKU
File Based OTA
Supported API: 3
MANUAL MODE v1.0.0#
Sucessfully verified dmverity hash tree E:Failed to clear BCB message:failed to find /misc partition
I didn’t wipe data/cache, afraid of maybe bricking my phone. How can I remove these error messages?