Tab Mini C boot loop. Help please. - Page 5

Pentam · 04-21-2024, 12:04 PM

Quote:

Originally Posted by Wolf-HRB

then choose do factory reset. swipe the screen to select, then press power button to confirm

Already tried that. Doesn't help.

Wolf-HRB · 04-21-2024, 01:26 PM

hmmmm, that's strange. I tried the steps I wrote in the batch, everything works fine. What did you do before flashing the things I provided? I need to know the details

try the following command in fastboot mode:

fastboot getvar all

and provide me the result.

Pentam · 04-21-2024, 01:59 PM

Quote:

Originally Posted by Wolf-HRB

hmmmm, that's strange. I tried the steps I wrote in the batch, everything works fine. What did you do before flashing the things I provided? I need to know the details

try the following command in fastboot mode:

fastboot getvar all

and provide me the result.

It all started by falling asleep while reading and waking up to the error message posted two posts earlier. I selected "try again" and got boot loops. Everything I tried after that is documented in this thread here, except that I tried most possibilities several times to see if something changes.

Result of "getvar all":

Spoiler:

Renate · 04-21-2024, 03:28 PM

Since you have the decrypted update.zip, have you tried:

Code:

fastboot boot recovery.img

Does this run normally? Does it give you more options?

Pentam · 04-21-2024, 04:04 PM

Quote:

Originally Posted by Renate

Since you have the decrypted update.zip, have you tried:

Code:

fastboot boot recovery.img

Does this run normally? Does it give you more options?

Yes, this boots normally to recovery. Recovery options are still the same (see attached image). ADB still unauthorized.

Renate · 04-21-2024, 05:54 PM

I can probably patch recovery for ADB.
My internet here is slow, so could you post just the recovery somewhere for me.
I think that this is using the new updater and I'm not so experienced with that.
Does this have an update-binary of ~280 kB or so in META-INF?
Please post that too.

Wolf-HRB · 04-22-2024, 06:34 AM

please try the following steps:

1. remove 2 commands in my bat file:

fastboot erase userdata

fastboot -w

2. after flash, use following command:

fastboot reboot recovery

3. perform factory reset process in recovery

4. reboot

try this and see how it goes

Pentam · 04-22-2024, 01:06 PM

Quote:

Originally Posted by Renate

I can probably patch recovery for ADB.
My internet here is slow, so could you post just the recovery somewhere for me.
I think that this is using the new updater and I'm not so experienced with that.
Does this have an update-binary of ~280 kB or so in META-INF?
Please post that too.

Here is the link to the recovery.img.

META-INF just contains 2 files: "metadata" and "otacert"
No other file of ~280 kB size. Sorry.

Pentam · 04-22-2024, 01:11 PM

Quote:

Originally Posted by Wolf-HRB

please try the following steps:

1. remove 2 commands in my bat file:

fastboot erase userdata

fastboot -w

2. after flash, use following command:

fastboot reboot recovery

3. perform factory reset process in recovery

4. reboot

try this and see how it goes

Tried and failed.
Device freezes after 3 dots in the boot animation (reproducably). After a certain time it automatically reboots and get to the same point. The next reboot stops already at the ONYX logo. After a few more boot loops it ends up in fastboot.

It somehow seems as if the system "degrades" with each boot attempt.

Renate · 04-22-2024, 01:22 PM

Quote:

Originally Posted by Pentam

Here is the link to the recovery.img.

Thanks. It's 96 MB, did you pull this off the device? Is it the latest from the update?
I'm at 20% downloaded.

There's probably a count for failed reboots.

Pentam · 04-22-2024, 01:25 PM

Quote:

Originally Posted by Renate

Thanks. It's 96 MB, did you pull this off the device? Is it the latest from the update?
I'm at 20% downloaded.

Yes. 96 MB. That's straight from the update.upx.

Quote:

There's probably a count for failed reboots.

Yeah, would make sense...

Wolf-HRB · 04-23-2024, 12:59 AM

the final thing you could try is using 9008 to flash all partitions of the device.

Pentam · 04-23-2024, 04:14 PM

Quote:

Originally Posted by Wolf-HRB

the final thing you could try is using 9008 to flash all partitions of the device.

Ok. Thanks for the suggestion. I will see if a modified recovery by @Renate will solve the problem first. If that does not help, I will try that approach...

Renate · 04-23-2024, 05:30 PM

Usually, if the option is available, installing a new update semi-manually is easier than EDL-ing individual partitions.
Especially since super has become multiple files on some devices.

You can try adb sideload (I never have).
If that doesn't work, we can try the flash drive method.
That works with update-binary, but I've never tried with this new update engine.

Code:

update_engine_client --help
Android Update Engine Client

  --allocate  (Given payload metadata, allocate space.)  type: bool  default: false
  --cancel  (Cancel the ongoing update and exit.)  type: bool  default: false
  --follow  (Follow status update changes until a final state is reached. Exit status is 0 if the update succeeded, and 1 otherwise.)  type: bool  default: false
  --headers  (A list of key-value pairs, one element of the list per line. Used when --update or --allocate is passed.)  type: string  default: ""
  --help  (Show this help message)  type: bool  default: false
  --merge  (Wait for previous update to merge. Only available after rebooting to new slot.)  type: bool  default: false
  --metadata  (The path to the update payload metadata. Used when --verify or --allocate is passed.)  type: string  default: "/data/ota_package/metadata"
  --offset  (The offset in the payload where the CrAU update starts. Used when --update is passed.)  type: int64  default: 0
  --payload  (The URI to the update payload to use.)  type: string  default: "http://127.0.0.1:8080/payload"
  --reset_status  (Reset an already applied update and exit.)  type: bool  default: false
  --resume  (Resume a suspended update.)  type: bool  default: false
  --size  (The size of the CrAU part of the payload. If 0 is passed, it will be autodetected. Used when --update is passed.)  type: int64  default: 0
  --suspend  (Suspend an ongoing update and exit.)  type: bool  default: false
  --update  (Start a new update, if no update in progress.)  type: bool  default: false
  --verify  (Given payload metadata, verify if the payload is applicable.)  type: bool  default: false

Renate · 04-24-2024, 11:11 AM

Also, I believe that this is an SDM662, so we have the Firehose loader for that.

04-21-2024, 03:28 PM	#64
Renate Onyx-maniac Posts: 3,207 Karma: 12537601 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Since you have the decrypted update.zip, have you tried: Code: fastboot boot recovery.img Does this run normally? Does it give you more options?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Boot loop - what's wrong?	abarthch	Kindle Developer's Corner	65	05-09-2016 05:18 PM
[PW] Stuck in boot loop?	abarthch	Kindle Developer's Corner	11	02-04-2016 01:20 PM
PRS-350 Unbricking from boot loop?	Analogus	Sony Reader	19	06-16-2011 04:35 PM
Kindle 3 Boot loop	jlove	Kindle Developer's Corner	13	05-17-2011 06:23 AM
PRS-650 Boot loop after large changes	Soul_Est	Sony Reader	5	11-29-2010 01:12 PM

04-21-2024, 01:26 PM	#62
Wolf-HRB Enthusiast Posts: 37 Karma: 18 Join Date: Feb 2022 Device: PW3, PW4 and PW5 Signature Edition	hmmmm, that's strange. I tried the steps I wrote in the batch, everything works fine. What did you do before flashing the things I provided? I need to know the details try the following command in fastboot mode: fastboot getvar all and provide me the result.

04-21-2024, 05:54 PM	#66
Renate Onyx-maniac Posts: 3,207 Karma: 12537601 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	I can probably patch recovery for ADB. My internet here is slow, so could you post just the recovery somewhere for me. I think that this is using the new updater and I'm not so experienced with that. Does this have an update-binary of ~280 kB or so in META-INF? Please post that too.

04-22-2024, 06:34 AM	#67
Wolf-HRB Enthusiast Posts: 37 Karma: 18 Join Date: Feb 2022 Device: PW3, PW4 and PW5 Signature Edition	please try the following steps: 1. remove 2 commands in my bat file: fastboot erase userdata fastboot -w 2. after flash, use following command: fastboot reboot recovery 3. perform factory reset process in recovery 4. reboot try this and see how it goes

04-23-2024, 12:59 AM	#72
Wolf-HRB Enthusiast Posts: 37 Karma: 18 Join Date: Feb 2022 Device: PW3, PW4 and PW5 Signature Edition	the final thing you could try is using 9008 to flash all partitions of the device.

04-24-2024, 11:11 AM	#75
Renate Onyx-maniac Posts: 3,207 Karma: 12537601 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Also, I believe that this is an SDM662, so we have the Firehose loader for that.

Advert

Advert