![]() |
#1 |
Connoisseur
![]() Posts: 53
Karma: 10
Join Date: Jul 2023
Device: Boox Tab Mini C
|
Tab Mini C boot loop. Help please.
Something odd happened to my Tab Mini C.
It went into sleep mode and when I looked at it again the next day it said something had failed (don't exactly remember what) and I had the options of "try again" or "factory reset". I selected try again and the device went into a boot loop. I can get into Recovery mode but only "reboot to system" and "reboot to bootloader" is selectable. It is possible to reboot to bootloader and it shows up on a PC with fastboot devices. ADB in recovery shows "unauthorized". Is there any way to revive the device? Keeping the data would be great... |
![]() |
![]() |
![]() |
#2 | |
Enthusiast
![]() ![]() ![]() ![]() ![]() ![]() Posts: 42
Karma: 604
Join Date: Feb 2024
Device: Kindle Paperwhite
|
Quote:
If so, u can use fastboot boot boot.img Or else you will need to extract boot.img from update.upx |
|
![]() |
![]() |
Advert | |
|
![]() |
#3 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,851
Karma: 12000011
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
|
The last update for the TabMiniC was:
Code:
Model: TabMiniC (English) Finger: Onyx/TabMiniC/TabMiniC:11/2023-11-22_07-26_3.5_946657f755/43508:user/dev-keys Link: http://firmware-us.boox.com/0c30bf96b1f58c6884b83b110ab9b880/update.upx Size: 1,552,092,065 MD5: 0c30bf96b1f58c6884b83b110ab9b880 If somebody can, adb pull /system/lib64/libota_jni.so |
![]() |
![]() |
![]() |
#4 | |
Connoisseur
![]() Posts: 53
Karma: 10
Join Date: Jul 2023
Device: Boox Tab Mini C
|
Quote:
Tried flashing the original as well as the Magisk-rooted version. Both did not solve the problem. Last edited by Pentam; 03-31-2024 at 05:14 PM. |
|
![]() |
![]() |
![]() |
#5 | |
Connoisseur
![]() Posts: 53
Karma: 10
Join Date: Jul 2023
Device: Boox Tab Mini C
|
Quote:
I only know about the method with ADB. |
|
![]() |
![]() |
Advert | |
|
![]() |
#6 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,851
Karma: 12000011
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
|
With my Poke3 I've used a custom recovery to flash a decrypted update on a flash drive to the device.
Without userdata mounted it can be hard to find space for 1.5 GB. If someone has a working TabMiniC we need that libota_jni.so for the keys. |
![]() |
![]() |
![]() |
#7 | |
Enthusiast
![]() ![]() ![]() ![]() ![]() ![]() Posts: 42
Karma: 604
Join Date: Feb 2024
Device: Kindle Paperwhite
|
Quote:
Those keys need to be updated for tool that allows to extract rom details from update.upx. |
|
![]() |
![]() |
![]() |
#8 |
Junior Member
![]() Posts: 2
Karma: 18
Join Date: Mar 2024
Device: Clara HD
|
Name: libota_jni.so
Size: 11704 bytes (11 KiB) CRC32: 02478E8C 3B0B382BDA19D0E9F0755C8B01B086DC A602693F5AF19546BF7F40A523237E54 |
![]() |
![]() |
![]() |
#9 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,851
Karma: 12000011
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
|
Thank you. Added to https://github.com/Hagb/decryptBooxU...r/BooxKeys.csv
|
![]() |
![]() |
![]() |
#10 |
Connoisseur
![]() Posts: 53
Karma: 10
Join Date: Jul 2023
Device: Boox Tab Mini C
|
|
![]() |
![]() |
![]() |
#11 | |
Connoisseur
![]() Posts: 53
Karma: 10
Join Date: Jul 2023
Device: Boox Tab Mini C
|
Quote:
I decrypted the update.upx to update.zip. How do I use the files with fastboot? |
|
![]() |
![]() |
![]() |
#12 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,851
Karma: 12000011
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
|
You can try with fastboot to boot (not flash) the boot image off the update.
It might break some things, but it might not boot loop. Code:
fastboot boot boot.img |
![]() |
![]() |
![]() |
#13 | |
Connoisseur
![]() Posts: 53
Karma: 10
Join Date: Jul 2023
Device: Boox Tab Mini C
|
Quote:
In the device manager is see a repeated connection of a device "QUSB_BULK_SN:********". That is different from the repeated loop of screen flashing between the logo screen that I had before. |
|
![]() |
![]() |
![]() |
#14 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,851
Karma: 12000011
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
|
Quote:
You can try Magisk'ing the boot image from the update on another Android. You can try using an "empty" vbmeta or clearing the flags. Which files do you have in the update? I might be able to make something out of the recovery, but that is a bit of work and a bit tedious to do when I don't own one of these. |
|
![]() |
![]() |
![]() |
#15 |
Connoisseur
![]() Posts: 53
Karma: 10
Join Date: Jul 2023
Device: Boox Tab Mini C
|
Content of payload.bin:
- boot.img - dtbo.img - modem.img - product.img - recovery.img - system.img - system_ext.img - vbmeta.img - vbmeta_system.img - vendor.img - xbl.img Magisked boot image did not solve the problem. Same result. Sorry. Noob here... What do you mean with "empty" vbmeta? Clearing the partition or flashing 0 byte file? |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Boot loop - what's wrong? | abarthch | Kindle Developer's Corner | 65 | 05-09-2016 04:18 PM |
[PW] Stuck in boot loop? | abarthch | Kindle Developer's Corner | 11 | 02-04-2016 12:20 PM |
PRS-350 Unbricking from boot loop? | Analogus | Sony Reader | 19 | 06-16-2011 03:35 PM |
Kindle 3 Boot loop | jlove | Kindle Developer's Corner | 13 | 05-17-2011 05:23 AM |
PRS-650 Boot loop after large changes | Soul_Est | Sony Reader | 5 | 11-29-2010 12:12 PM |