Tab Mini C boot loop. Help please.

[jljtgr]

Originally Posted by dcarvil

Does that mean it is possible to adb sideload a debooxed update.zip? I have been wondering if that is possible, but have not found an answer.

Thanks.

ZIP, yes. UPX, no.

>adb sideload update.zip
Total xfer: 2.00x

[dcarvil]

Originally Posted by jljtgr

ZIP, yes. UPX, no.

>adb sideload update.zip
Total xfer: 2.00x

Do you have to deboox the upx to get the zip, or just rename upx to zip?

Thanks for the reply.

[jljtgr]

You definitely have to use decryptBooxUpdateUpx to get the ZIP from the UPX.

[dcarvil]

Originally Posted by Pentam

Unfortunately, that does not help in my case.
Slot A activated leads to constant onyx logo, blue LED and on the PC EDL-device repeatedly reconnects
Slot B activated leads to bootloop: onyx logo --> flashing screen --> onyx logo

Based on the information provided by jljtgr, I'd recommend you deboox the update.upx, then "adb sideload update.zip". First do an "adb reboot sideload" to get into sideload mode. Good luck.

[Renate]

I have no experience with adb sideload.
With my Poke3 I have a custom recovery that can do an update from a flash drive.

[Wolf-HRB]

Your problem is easy to solve. In my opinion, the reason causes this is some thing wrong within the Super partition (this device uses VAB). if you are stuck in fastboot mode (fastboot devices command works), you can easily flash boot, super, recovery and all other partitions. Since there is no security check for all BOOX devices, you do not need to worry about unlock BL or OEM lock. I have the partition images you need to solve your problem, simply contact me here and I will provide you. When you contact me, I can tell you what is the detail steps to solve this issue.

[Wolf-HRB]

BTW, I successfully flash my Tab Mini C Mainland China version (code name Tab 8C) to international version (code name Tab Mini C), LOL

[Pentam]

Originally Posted by jljtgr

ZIP, yes. UPX, no.

>adb sideload update.zip
Total xfer: 2.00x

Quick question: What does "Total xfer: 2.00x" do and how do I enable it?

Without that I get to:

serving: 'update.zip'   (~47%)    adb: failed to read command: No error

[Wolf-HRB]

IDK what you are asking. xfer is the built-in function of recovery.

[jljtgr]

Originally Posted by Pentam

Quick question: What does "Total xfer: 2.00x" do and how do I enable it?

Without that I get to:

serving: 'update.zip'   (~47%)    adb: failed to read command: No error

> is part of the command prompt, you don't write it. The line after that is the STDOUT/STDERR of the ADB command.

If you open the ZIP in something like 7-zip, and use the Test function... does it pass CRC?

What does the device show on the screen at the time?

[Pentam]

Originally Posted by jljtgr

The line after that is the STDOUT/STDERR of the ADB command.

thanks

If you open the ZIP in something like 7-zip, and use the Test function... does it pass CRC?

Yes, it does pass the test in 7-zip

What does the device show on the screen at the time?

[Pentam]

Originally Posted by Wolf-HRB

IDK what you are asking. xfer is the built-in function of recovery.

Sorry, misunderstanding from my side. Nevermind...

Wrote you a PM about the partition images. Would be happy to try it.

[jljtgr]

Originally Posted by Pentam

Image

Hmm, I had to Google that one. It sounds like a common error message for custom roms on locked bootloaders or when the rom is for the wrong version of Android. Since this is a vendor supplied stock rom, I'd think this isn't the issue unless you're trying to downgrade or flat out have the wrong device's update file.

There are some other internet thoughts about how you got to sideload mode changing things, but I find that hard to believe. Despite my skepticism of how you get there meaning something... I didn't use any ADB command to get the device into the right mode(like other posts suggested). Mine was bootlooping so bad only the power-button 6 click voodoo ritual got me into recovery. From there, I navigated the recovery menu into sideload.

Could how I got into recovery change things? Could how I got into sideload from recovery change things? I would hope not, but random people on the internet put the unreliable thought into my head to share.

[Pentam]

Originally Posted by jljtgr

Hmm, I had to Google that one. It sounds like a common error message for custom roms on locked bootloaders or when the rom is for the wrong version of Android. Since this is a vendor supplied stock rom, I'd think this isn't the issue unless you're trying to downgrade or flat out have the wrong device's update file.

There are some other internet thoughts about how you got to sideload mode changing things, but I find that hard to believe. Despite my skepticism of how you get there meaning something... I didn't use any ADB command to get the device into the right mode(like other posts suggested). Mine was bootlooping so bad only the power-button 6 click voodoo ritual got me into recovery. From there, I navigated the recovery menu into sideload.

Could how I got into recovery change things? Could how I got into sideload from recovery change things? I would hope not, but random people on the internet put the unreliable thought into my head to share.

I also got into the ADB sideload mode through power button magic (I'm an expert in this by now) and then tried sending the update.zip. However it did not even send the whole file. It aborted after about half the file transfer (47%).

For the previous recommended "adb reboot sideload" you would need normal ADB access, which I don't have ("unauthorized"). so that is not an option...

[jljtgr]

A lot of flashing commands in Android seem to reserve 50% for transferring and 50% for installing. So 47% probably means it transferred the file, but did not get into installing it because of the signature failure. At face value meaning the device did not think the ZIP was signed with a private key that it had a certificate for. APKs are signed like this too, I guess.

EDIT: I got around to updating my phone today and observed that the phone starts the install process at exactly 47% as well. So this number seems like the normal file transfer endpoint.