Did you follow the recommendation to reflash, rather than just factory reset, especially if thereâs still issues? If you did, and the problem is still happening, the followup recommendation from today is to reflash twice in a row, so that both the A and B versions of the system match the clean version, and donât potentially restore whatever is causing your specific reboot storm.
I only did the factory reset.
it remained Android 14 after the factory reset which i found a bit odd.
Do you want me to install a previous version of Android? or just reinstalling Android 14?
Re-installing the latest official image twice in a row is my current recommendation. I donât think we need to go back-level at this point, especially since this seems to be an isolated issue on your device. It feels like something didnât go well in a flash or update on-device.
1 Like
Factory reset is just wiping your data and starting over with the existing version of the OS thatâs currently installed. It wonât reset any corrupted parts of the system, just gets you back to where it was before you ran the initial setup on that specific OS version.
If anything was corrupted in the actual flash, then Factory Reset wonât fix it. It needs a new flash, preferably after verifying the hash or doing a new download if you canât validate the file hash against known good.
Currently going through an issue with supporting MS Windows 11 thatâs similar, where you need to actually download the installation files and re-run the setup (basically like an Android reflash) to fix some corrupted files in the system store. Doing a Windows reset just leaves it broken, because its immutable files arenât as pristine as they should be. Probably an AV caused corruption, but⌠not really sure, just know the workaround at this point.
1 Like
Downloaded the installation file from this thread and installed it twice in a row.
So far it looks good, no restart that i know of.
It still shows the two different android systems in the ram usage overview but i donât really care about that.
If you donât hear anything again from me, consider it solved.
thank you so much
1 Like
well, guess that was too early.
reboots are back, frequency went down to like 2 a day and the impact it has on the usage has improved a lot. Its lagging way less after the reboots.
1 Like
What is your batteryâs age, and about what runtime do you get?
Do you notice if the reboots happen when it is hot, or if youâre heavily using the device?
Is this update confirmed to work with AT&T?
I just exchanged my battery a couple of weeks ago so i have no issues with the runtime, especially compared to the previous battery.
I canât see a link between temperature and usage, it happened on either end of the scale for both
1 Like
Are you using a microSD Card as shared internal storage on this device?
No, i am not using a card
1 Like
At this juncture, Iâd suggest reaching out to support@myteracube.com to discuss warranty repair or replacement for your phone.
I repaired my Issues !!! No more reboots or crashing apps. 
Probably not all steps needed but this worked for me.
- Backup to Google Backup (system > Backup)
- I have taken out my sd Card.
- Backup of /storage/emulated/0 with âDriveSync to GoogleDriveâ
- I followed this reset manuell for Android 13 Link
- Skipped connection to google account
- Download upgrade zip and Upgrade to 14
- Connecting android to GoogleAccount
- Restore of last Google Backup
- Restore of /storage/emulated/0 with âDriveSync to GoogleDriveâ
- insert cd card
2 Likes
unfortunately the Issues are back.
Over time the Phone got slower and slower at times.
Now Iâm back at the same State. 1-2 Reboots a day and random freezing apps with reboot after 5min
1 Like
Please try our new update (14.1.0) and let us know if those issues are fixed 
2 Likes
No, sorry. Itâs the same development. First itâs better and then the Issues creep back. Since yesterday it is back to normal.
Is there a Teracube 3e in development? I assume the cersion 14.1.0 just needs better hardware
Yes it has been tested (The issue has been isolated now and every other builds will always have it working)
1 Like
I received a refurbished phone today, which shipped with Android 11. I followed the advice to install Android 13 first, using the 13.1.1. emerald build. This first step worked fine on the first attempt. However, from there when I tried to manually update to 14.1.0, I kept getting the error âunable to load package.â However, the updater APK looked online for an update and told me that 14.0.1 was available. So I allowed it to downloaded that version, and it installed without any problem.
Is there some reason why the updater APK would show the older 14.0.1 and not the 14.1.0, and why I would be unable to update to 14.1.0 by manually loading the âsys_emerald-images-14.1.0+65f18f1.emerald.user_signed.zipâ file?
14.1.0 is available as incremental on top of 14.0.1. The Updater would sometimes show your local installed version, just apply for any updates that appear.