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

Wolf-HRB · 04-26-2024, 08:40 PM

yeah, it is SDM662 and this device is able to 9008 because there is no secure boot. I could provide the firehose if needed.

Pentam · 04-27-2024, 05:33 AM

Quote:

Originally Posted by Renate

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.

I already tried adb sideload as per this advise.
But the verification of the update fails.

Do you mean an external drive at USB by "flash drive method"?

Wolf-HRB · 04-29-2024, 10:52 AM

I think he wants you to use adb sideload or apply update from SD card

Renate · 04-29-2024, 11:06 AM

I was talking about using an flash drive and a custom recovery.
But I've never tried using the new "update engine".
It looks like you could put the payload.bin on a website or flash and update from there.

Edit: Oh, I see there is a new Poke5 update.
I guess that I can experiment with that on my Poke5.
It's a mixed bag, I guess, of whole images and payload.bin
I think that the update_engine only works with payload.bin?

Unfortunately my internet is mega-slow, so I can't download 1.6GB in my lifetime.

Since we have found a new Firehose loader for the Poke5 there's no risk.

bigwigs · 04-30-2024, 05:29 PM

Quote:

Originally Posted by Renate

I was talking about using an flash drive and a custom recovery.
But I've never tried using the new "update engine".
It looks like you could put the payload.bin on a website or flash and update from there.

Edit: Oh, I see there is a new Poke5 update.
I guess that I can experiment with that on my Poke5.
It's a mixed bag, I guess, of whole images and payload.bin
I think that the update_engine only works with payload.bin?

Unfortunately my internet is mega-slow, so I can't download 1.6GB in my lifetime.

Since we have found a new Firehose loader for the Poke5 there's no risk.

R u using satellite or dialup internet?

Renate · 04-30-2024, 08:03 PM

Quote:

Originally Posted by bigwigs

R u using satellite or dialup internet?

I'm using a Netgear LM1200 4G modem, rooted and with custom JSON status that I use for a monitoring app. The debug UART is brought out to a connector.

When I'm in the country the congestion can be bad at times. I downloaded the Poke5 update this morning at 3:30 AM without a problem.

Renate · 05-01-2024, 11:02 PM

We're making a bit of progress, but still bugs.

Edit: Oh! It does work!
The stock boot works, but I'm having problems with Magisk now.

Sigh, well at least I can read my book.

Edit^2: Ok, I got Magisk working again.
I was shadowing framework.jar and it was the old version.
An update fixed that.

Pentam · 05-02-2024, 03:32 AM

Quote:

Originally Posted by Renate

We're making a bit of progress, but still bugs.

Edit: Oh! It does work!
The stock boot works, but I'm having problems with Magisk now.

Sigh, well at least I can read my book.

That sounds very promising. Being able to read my books again would be amazing.

So if you have anything for me to try, please let me know.

Renate · 05-02-2024, 07:35 AM

I'll be making a new recovery, but the short version of how you do this:

Go to fastboot and determine which slot you are on.
Flash custom recovery to the current slot
Reboot recovery and see that it behaves correctly
Flash custom recovery to the inactive (other) slot
Get update.upx, decrypt, unzip on desktop (no payload dumper needed).
Put payload.bin & payload_properties.txt on a FAT-ish flash drive
Reboot recovery
adb shell start autoupdate
Remove USB cable, plug in OTG/flash
Drink a coffee, watch the little LED on the flash blink
Put the flash in the PC and look at autolog.txt

Renate · 05-02-2024, 01:25 PM

Yay!
I got my Poke5 to 3.5.1 with the new autoupdate.
AND I got the stupid short/long press for PgUp/PgDn defeated.
They changed some things so I needed new patches for framework.jar
OTOH, patching smali without disassembling brings joy to me.

Pentam · 05-02-2024, 02:18 PM

Quote:

Originally Posted by Renate

I'll be making a new recovery, but the short version of how you do this:

Go to fastboot and determine which slot you are on.
Flash custom recovery to the current slot
Reboot recovery and see that it behaves correctly
Flash custom recovery to the inactive (other) slot
Get update.upx, decrypt, unzip on desktop (no payload dumper needed).
Put payload.bin & payload_properties.txt on a FAT-ish flash drive
Reboot recovery
adb shell start autoupdate
Remove USB cable, plug in OTG/flash
Drink a coffee, watch the little LED on the flash blink
Put the flash in the PC and look at autolog.txt

Thanks for the instructions. I tried that.
Unfortunately, it does not seem to work here.
I get the following output on the screen:

Code:

ttyscreen has started
Waiting for flash drive...

But when I unplug the USB cable and connect the flash drive, nothing happens for about 12 seconds. Then the LED in the power button turns blue. Afterwards nothing else is happening and when I reconnect the device to the PC, it seems to be in EDL mode.

PS: I tried that with three different flash drives. All of them are FAT32 and get detected on my Android phone. So it is unlikely to be caused by the flash drive.

Renate · 05-02-2024, 02:25 PM

Quote:

Originally Posted by Pentam

All of them are FAT32 and get detected on my Android phone. So it is unlikely to be caused by the flash drive.

Yes, but are they Type C or Type A?
Are you using an OTG adapter?
Use an OTG adapter.

Pentam · 05-02-2024, 02:37 PM

Quote:

Originally Posted by Renate

Yes, but are they Type C or Type A?
Are you using an OTG adapter?
Use an OTG adapter.

I tried USB-C and USB-A with OTG adapter.
Both are accessible in the recovery of my phone. No luck with the TabminiC.

Renate · 05-02-2024, 02:45 PM

Boot to recovery, but don't start autoupdate.
Plug in one of your drives.
Does it still crash?
Try again with just the OTG adapter (no flash).
Does it still crash?

Pentam · 05-02-2024, 03:02 PM

Quote:

Originally Posted by Renate

Boot to recovery, but don't start autoupdate.
Plug in one of your drives.
Does it still crash?

Yes

Quote:

Try again with just the OTG adapter (no flash).
Does it still crash?

Yes

Looks like both are not the cause. It also cashes about 18 seconds after I unplug the USB cable without inserting anything.
With USB connected it stays in recovery.

04-29-2024, 11:06 AM	#79
Renate Onyx-maniac Posts: 4,125 Karma: 18764971 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	I was talking about using an flash drive and a custom recovery. But I've never tried using the new "update engine". It looks like you could put the payload.bin on a website or flash and update from there. Edit: Oh, I see there is a new Poke5 update. I guess that I can experiment with that on my Poke5. It's a mixed bag, I guess, of whole images and payload.bin I think that the update_engine only works with payload.bin? Unfortunately my internet is mega-slow, so I can't download 1.6GB in my lifetime. Since we have found a new Firehose loader for the Poke5 there's no risk. Last edited by Renate; 04-29-2024 at 01:14 PM.

05-01-2024, 11:02 PM	#82
Renate Onyx-maniac Posts: 4,125 Karma: 18764971 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	We're making a bit of progress, but still bugs. Edit: Oh! It does work! The stock boot works, but I'm having problems with Magisk now. Sigh, well at least I can read my book. Edit^2: Ok, I got Magisk working again. I was shadowing framework.jar and it was the old version. An update fixed that. Attached Thumbnails Last edited by Renate; 05-02-2024 at 12:12 PM.

05-02-2024, 07:35 AM	#84
Renate Onyx-maniac Posts: 4,125 Karma: 18764971 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	I'll be making a new recovery, but the short version of how you do this: Go to fastboot and determine which slot you are on. Flash custom recovery to the current slot Reboot recovery and see that it behaves correctly Flash custom recovery to the inactive (other) slot Get update.upx, decrypt, unzip on desktop (no payload dumper needed). Put payload.bin & payload_properties.txt on a FAT-ish flash drive Reboot recovery adb shell start autoupdate Remove USB cable, plug in OTG/flash Drink a coffee, watch the little LED on the flash blink Put the flash in the PC and look at autolog.txt

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-26-2024, 08:40 PM	#76
Wolf-HRB Enthusiast Posts: 37 Karma: 18 Join Date: Feb 2022 Device: PW3, PW4 and PW5 Signature Edition	yeah, it is SDM662 and this device is able to 9008 because there is no secure boot. I could provide the firehose if needed.

04-29-2024, 10:52 AM	#78
Wolf-HRB Enthusiast Posts: 37 Karma: 18 Join Date: Feb 2022 Device: PW3, PW4 and PW5 Signature Edition	I think he wants you to use adb sideload or apply update from SD card

05-02-2024, 01:25 PM	#85
Renate Onyx-maniac Posts: 4,125 Karma: 18764971 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Yay! I got my Poke5 to 3.5.1 with the new autoupdate. AND I got the stupid short/long press for PgUp/PgDn defeated. They changed some things so I needed new patches for framework.jar OTOH, patching smali without disassembling brings joy to me.

05-02-2024, 02:45 PM	#89
Renate Onyx-maniac Posts: 4,125 Karma: 18764971 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Boot to recovery, but don't start autoupdate. Plug in one of your drives. Does it still crash? Try again with just the OTG adapter (no flash). Does it still crash?