Tab Ultra C Pro - totally borked... but there may be hope

[Eternalcat]

Yes, they are physically identical. I just successfully "converted" my Tab 10C Pro into a Tab Ultra C Pro.I extracted the individual partition images from the official International OTA payload.bin, and then manually reconstructed the super.img.Interestingly, I was even able to boot into the International system without wiping userdata. For now, I will test the OTA.

[derget1212]

Originally Posted by Eternalcat

Yes, they are physically identical. I just successfully "converted" my Tab 10C Pro into a Tab Ultra C Pro.I extracted the individual partition images from the official International OTA payload.bin, and then manually reconstructed the super.img.Interestingly, I was even able to boot into the International system without wiping userdata. For now, I will test the OTA.

Yes, I've read that they are identical and interchangeable. I had a Tab10CPro recovery working on the TabUltraCPro. THANK YOU ETERNALCAT!!!!

How do I rebuild a super or blank super.img from the 1M provided? I'm assuming I flash a super.img w/ the partition layout of the super.img, then just flash an update.zip to fill in the update data via recovery?

[Renate]

Just flash the 1 MB manifest to super.
Then go to recovery and try to adb sideload a decrypted update.

[derget1212]

Originally Posted by Renate

Just flash the 1 MB manifest to super.
Then go to recovery and try to adb sideload a decrypted update.

IT WORKED!!

edl w super 1m
edl w misc_recovery.prc
edl reset

adb sideload update.zip  - I chose update 4.1 full from data.onyx-international*

Thank you all for all your help! I was feeling so hopeless, but Renate and Eternalcat really came through. I'm going to make a rooted backups and full flashable versions of the FW for this device. I love my Tab Ultra C Pro, but I'm really disappointed in Boox customer service during this instance.

[Eternalcat]

Originally Posted by derget1212

IT WORKED!!

edl w super 1m
edl w misc_recovery.prc
edl reset

adb sideload update.zip  - I chose update 4.1 full from data.onyx-international*

Thank you all for all your help! I was feeling so hopeless, but Renate and Eternalcat really came through. I'm going to make a rooted backups and full flashable versions of the FW for this device. I love my Tab Ultra C Pro, but I'm really disappointed in Boox customer service during this instance.

Congrats on getting your device fixed! 🎉 I'm really looking forward to your full flashable firmware backup.

Right now, after flashing TabUltarCPro, I'm unable to use ADB sideload or disable AVB on my device. If you're open to sharing your backup, I'd love to try flashing it to see if it resolves these two issues.

Thanks again, and glad the super partition header extract was helpful!

[Renate]

Originally Posted by Eternalcat

I'm unable to use ADB sideload or disable AVB on my device.

fastboot oem device-info

Pull your abl and post or PM it.

[Eternalcat]

Originally Posted by Renate

fastboot oem device-info

Pull your abl and post or PM it.

I apologize for the confusion earlier. I *can* disable AVB (I'm currently using a custom vbmeta to boot), and the system detects the non-standard AVB state, so the OTA updates are blocked.

Here is the output:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true

I've attached three ABL images: the original backup, the one from the TUCP zip, and a fresh dump of the current running state. I'm running the TUCP ABL on my T10CP hardware. For now, it'working.

[derget1212]

Originally Posted by Eternalcat

Congrats on getting your device fixed! 🎉 I'm really looking forward to your full flashable firmware backup.

Right now, after flashing TabUltarCPro, I'm unable to use ADB sideload or disable AVB on my device. If you're open to sharing your backup, I'd love to try flashing it to see if it resolves these two issues.

Thanks again, and glad the super partition header extract was helpful!

I am rooted with a patched boot.img to slots a/b. I know this breaks OTA, I'm assuming it breaks adb sideload as well? Or is that just if verity/avb are not disabled?

[Renate]

Originally Posted by Eternalcat

I've attached three ABL images...

All five are basically the same:

continue
download
getvar
oem device-info
oem disable-charger-screen
oem display-cmdline
oem enable-charger-screen
oem off-mode-charge
oem select-display-panel
reboot
reboot-bootloader
reboot-fastboot
reboot-recovery
snapshot-update

If you want to try turning off verity-mode, we can try that.
But it requires some effort on my part.

[Eternalcat]

Originally Posted by derget1212

I am rooted with a patched boot.img to slots a/b. I know this breaks OTA, I'm assuming it breaks adb sideload as well? Or is that just if verity/avb are not disabled?

I think so, my sideload issue is specifically caused by my custom-built super partition, so I think the stock `super.img` (the one installed via official recovery) might be enough to solve that.

[Eternalcat]

Originally Posted by Renate

All five are basically the same:

continue
download
getvar
oem device-info
oem disable-charger-screen
oem display-cmdline
oem enable-charger-screen
oem off-mode-charge
oem select-display-panel
reboot
reboot-bootloader
reboot-fastboot
reboot-recovery
snapshot-update

If you want to try turning off verity-mode, we can try that.
But it requires some effort on my part.

That sounds great. I'm ready to follow your instructions to disable verity-mode. Please let me know what steps or files you need from me. Thanks for the help!

[derget1212]

Originally Posted by Eternalcat

I think so, my sideload issue is specifically caused by my custom-built super partition, so I think the stock `super.img` (the one installed via official recovery) might be enough to solve that.

https://drive.google.com/file/d/12V5...ew?usp=sharing

[Renate]

Originally Posted by Eternalcat

I'm ready to follow your instructions to disable verity-mode.

I sent you a PM a week ago.