Please check your USB cable and port work properly with other devices, and try again.
The phone must be off for SPFlash, and this script, to function.
Please check your USB cable and port work properly with other devices, and try again.
The phone must be off for SPFlash, and this script, to function.
fail
Please don’t use a pay software for this. It’s required to buy this software.
Please an instruction for Linux (Ubuntu 22.x LTS) or a OS that can used without installation.
The SPFlash method remains supported for Windows, MacOS, and Linux.
This method is meant specifically to be an easy method for the largest userbase.
I’m trying to follow the instructions from this thread’s OP. I found that the link to the USB_VCOM drivers (https://downloads.myteracube.com/Drivers/MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed.zip) is currently broken. Would it be possible to update the link please?
Thanks!
Welcome!
Sorry for the trouble.
I’ve let the team know and the links/files should be fixed presently.
Thanks for the reply @Saijin_Naib! Will this thread be updated when the link is fixed? Just tried it again and I see that the link is still broken. I realize it hasn’t been very long but wanted to make sure I’m looking for the fix in the right place.
This thread will most likely be updated, and if/when I hear back from the team that the resource has been placed somewhere, I will update you if someone else does not first.
Drivers link fixed in OP - thanks for letting us know.
When I got to step 5 above, ‘Double click the “InstallT2eFW.bat” file to run it’, and followed the Note about Windows, it pulled up a command prompt asking if I wanted to run the Flash. I typed ‘Y’ as prompted, and nothing happened. I had to restart my PC again after the second unzip, to activate the files. Then I could do step 5 and forward.
I’m trying to follow the instructions for using SP Flash to install factory software on my 2e on MacOS, but am running into problems with SP Flash not being supported. I’m also having trouble getting tools like Wine to try and run the Windows version. Are there instructions or any guidance on how SP Flash can be used to install the factory software using MacOS? I’m fine to follow the manual process, but I’m stuck at being unable to run flash_tool.exe.
Unfortunately, SPFlash is not supported on MacOS, and as you noted, Wine/DarWine will not run it properly.
You will need access to a Windows or Linux machine for the flash using SPFlash.
The procedure worked, however I had to reboot PC after point 4 to make it work
Does this procedure actually write zeroes across the entire internal memory of the phone, thus permanently wiping any user data and making it 100% unrecoverable?
If not, is there another recommended way of doing this before disposing of a Teracube or sending it back for repair?
It does not, no.
The SPFlash utility is meant for flashing the OEM image and partitions and communicating with the phone in a special lower-level mode that makes it (almost entirely) unbrickable and able to be recovered. Secure data erasure is a non-goal of this tool, from what I can tell from how it is laid out.
In terms of data recovery, a consistent write of 1 or 0 is easier to recover than (semi)random data written over it, so reflashing the user partition and maybe dumping a bunch of random-filled files on it between reflashes will be a much better secure-erase process. You can generate them on Linux with something like this: head -c 1G </dev/urandom >myfile
So I just received a warranty replacement device. Despite being told that the device would ship with Android 13, which should resolve security concerns from Android 11, the device in fact came with Android 11.
Unfortunately, I only discovered this after I logged into my Google Account on the phone.
When I went to Settings > System > Update, it showed me the following update was available:
Teracube 13.1.1+a21467d.emerald.user
Question 1: Is there a difference between installing v13 through the settings menu versus the process described in the original post in this thread? Specifically, I’m thinking about differences in device security, but curious to know others as well.
Question 2: Is it a problem that I logged into my Google account before updating to v13. It has been stated in several other threads how v11 had several known exploits that were blamed for the previously reported hacks where SMS 2FA codes were being forwarded by the phone.
Note: I never did and still have not put a SIM card in the replacement phone.
No, the are the same image, just applied differently. The manual flash is more of a failsafe/full recovery, whereas the upgrade from within Android doesn’t reimage everything as it isn’t needed on a functional device.
I don’t think that this is a likely risk factor, especially if your Google account is secured with 2FA and other best-practices. I’ve tested every build from TeraCube across Zirconia/Emerald/Thrive/Ruby with the same Google account, starting with Android 9 images, and I have not noticed anything suspicious at all in the logs.
These images will be updated with Android 13 stable builds.
Hi,
we are in the process of refurbishing a few Teracube 2e (2021) that we have. Would it be possible for you to make the Android 16 update packages available for Linux (using SP Flash) ?
It seems these images should exist as said in this thread :
I pinged the team and let them know.
Edit:
The SPFlash images for both Zirconia and Emerald are now posted in their Update threads: