Teracube 2e easy installer restart error

Thanks for the feedback @prflsjn and @aibd! I have another Teracube to get set up later this week – I’ll let you know how it goes and provide more detail on any errors.

You are correct @prflsjn, adb reboot bootloader failed (error: no devices/emulators found) and fastboot reboot bootloader was the winner. I was then able to do the fastboot flash recovery recovery.img.

Here’s the full sequence from #4 on the instructions:

fastboot -w
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot

Thanks for all your help!

2 Likes

I’m so glad it worked! Hopefully this information will be used to update the official instructions.

Over two months later since some very informative posts explaining what’s going on and the partition doesn’t exist error still hasn’t been addressed in the installer causing it to hang and leave users without a system partition. Guess I’ll try again in about six months but this is frustrating, to say the least when I had to unbrick my phone.

Don’t know who needs to see this to include fastbootd in the recovery.img file but I hope a bump helps get visibility on the subject.

1 Like

I started out as a total n00b, here’s how it worked out:

(A)
https://doc.e.foundation/devices/2e/install
do this, until you reach point nr. 4.

(B)
open up you device manager in windows

get your phone into fastboot-mode via
it should be in fastboot-mode (bootloader) once you arrived at step nr. 4
check that the driver is working right

now get you phone into fastbootd-menu via
fastboot reboot fastboot
watch the icons change in the device manager
check that the fastbootd driver is working right
if not, do this https://c.mi.com/oc/thread-3312019-1-0.html

If you have already overwritten the oem-registry.img do this

The driver stuff is crucial. I think you first need the regular device driver (MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed.zip) and then you need the adb driver from google. HINT: this step did not work on my PC, only on my laptop (!).

(C)
fastboot -w
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot reboot fastboot

now your phone should show the fastbootd-menu
use cmd-console and type, just to check the drivers and connection
fastboot devices
fastboot getvar is-userspace

if you get positve results, proceed
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vendor vendor.img

now choose reboot in the fastbootd-menu
fastboot flash recovery recovery.img
fastboot reboot

Good Luck guys.
It took me a whole day, but my burning anger for Klaus Schwab and the clot-shot agenda made me do it.

1 Like