[Certified] Android 13.1.0 for Teracube 2e Emerald (SN:2021)

[gadet]

I installed the latest update and then did a factory reset. Still cannot make or receive phone calls, but can send and receive text messages and use mobile data. Here are the APN settings I am using:
Name: H2O Wireless
APN: att.mvno
Proxy: 66.209.11.33
Port: 80
Username: Not set
Password: Not set
Server: Not set
MMSC: http://mmsc.cingular.com
MMS proxy: proxy.mvno.H2OMobileweb.com
MMS port: 80
MCC: 310
MNC: 410
Authentication type: PAP
APN type: default,mms,supl
APN protocol: IPv4
APN roaming protocol: IPv4
APN enable/disable: APN enabled
Bearer: Unspecified
MVNO type: None
MVNO value: Not set

[Saijin_Naib]

Please see the following post:

How to contact Teracube support

Hi @James_Krehbiel , Our T2e Android 13 update does not support AT&T. If you are using AT&T, then please revert to the earlier Android build using these steps - [Teracube 2e] Instructions to Install Factory Software and to Reset Here is the list of supported carriers

[Sahil_Sonar]

New update with charge limit is live on Updater. We are working on AT&T issue, users facing issue can rollback to Android 11.

[Sharad]

Users experiencing cellular connectivity issues on Android 13, please do the following:

1. Check Settings > System > Updater for any updates. Install any new updates.

2. Reset your APN settings at Settings > Network & internet > SIMs > Access point names > 3-dot > Reset to default.

[Vlaflip]

I’ve updated without problems through the auto updater to 13.0.5+ (security patch level 5th of July). Thanks! Seems to be working smoothly, no problems with cellular connectivity (thus far).

Root access is gone now though, is there a way to (easily) root the phone again?

[Maymne]

Beginning to get incredibly frustrated with the lack of live wallpaper support

Of note, it should only take 15 minutes or less to successfully root your phone, after you’ve done the prep work once. Current process, from scratch: Download the update file for your current build, if you don’t have it already. Extract the boot.img from it Copy that to your phone Install Magisk - I prefer Canary but that’s because I like being able to pass Certification and still use an official branch Open Magisk and patch the boot.img you copied over - do not try to patch vb or anything els…

Anytime you do a new build, it’ll remove root since it’s a new bootloader file. On a positive note, after you get used to the re-root process, it’s less than five minutes work to extract the boot.img from your update zip, patch it using your Magisk, and then it’s just copying to your computer and doing a quick flash. Should be less than 15 minutes total including the reboots.
Note that due to how Google does the current unlocked bootloader warning in Android 13, it’ll add 2 minutes to each reboot and at least on Zirconia, it adds an extra 3 minutes while it has a reboot timeout for a total of 7 minutes (two sets of 2 minute bootloader warnings, one 3 minute reboot timeout) additional waiting on each reboot while rooted. This did not happen on 13.0.4, but it’s still worth going to 13.0.5 for a Google app that doesn’t have broken voice search, integrated battery limiter, updated APN functionality, etc.

[Vlaflip]

Thanks for that, was easy enough to do! I’ve got root again Unfortunately now i’m experiencing connectivity problems. Can’t make calls or use wi-fi. Mobile ethernet does seem to work, if i activate it manually…

I’m not on AT&T, based in Europe…

[Maymne]

If it broke when you rooted, I’d probably revert back and see if that fixes it. Just repeat with the bootloader, fastboot flash the original unpatched boot, and back to system. If that fixes it, then I’d probably try a different version of Magisk or whatever rooting solution you’re using.
Kitsune Magisk was great for hiding but terrible in that it only works for elevating apps on main storage, not the sdcard, and it had a hiatus from February to July. Still the version that had the best compatibility for avoiding detection though.
Alpha Magisk is good if you don’t mind changelogs in Chinese.
Canary Magisk is good if you want the most working official branch.
Stable Magisk is good if you plan on ignoring updates for months.

[Vlaflip]

How to extract the original boot from the payload.bin though? Magisk does extract it, but will patch it right away. Thanks again for your help!

[Maymne]

Oh, I’d just take the update zip, whether from post 1 or from your /data/teracube_updates folder on your phone, open it with your preferred file utility, and extract boot.img from there. Should get you a clean boot image as well as providing another chance for a “This download really wasn’t corrupted, right?” check.

[Sharad]

Have you tried these steps?

[Vlaflip]

I have, it made no difference unfortunately. I did find a program to extract the boot.img with ( GitHub - tobyxdd/android-ota-payload-extractor: A fast & natively cross-platform Android OTA payload extractor written in Go ), because that file is contained in the payload.bin file these days (older firmware still has it in the regular zip file). With that, i was able to properly root my phone with the 13.0.4+5ae415b build installed (security patch 5th of june 2024).

It’s now working, I’m weary to update it again…

[Josh_Justic]

The update proceeded successfully until the first restart. I had to factory reset my phone for it to complete the update. After that the phone restarted successfully, but all my data on the phone was wiped.

[Saijin_Naib]

Sorry for the frustration, but there are cases where this might happen.

The team is working to ensure this does not happen on future final releases, as this came up during this past round of Betas.

[j-l]

It wiped all my saved passwords upon doing the update.
Downloaded apps and files remained.
Additionally, I was having major issues that were mentioned in a post about an update earlier this year. But even after updating to the new 13 version they are still occuring.

[Maymne]

Specifically, which previously mentioned major issues?

[Sahil_Sonar]

New update 13.1.0 is live! You can update using Updater directly or update manually using the steps above.

[winghongchan]

I just tried to do the update to 13.1.0 over the air (Settings → System → Updater) but after starting to reboot, my phone bootlooped for about 2 hours before the lock screen appeared. The update had apparently failed, since in the Settings I was still on the same Android version as before. My phone was at 80–90% battery and plugged in and had 14 GB internal storage free.

I want to try the update again (it’s still available to me through the Updater). Should I do anything different this time? (Additional info: I updated from Android 11 to 13 using the zip on this forum, and I’m currently on Android 13.0.5.)

[Saijin_Naib]

This is odd for sure.

Have you installed any custom recovery or unlocked the bootloader?

OTA from 13 to other point releases has not had issues in testing that I am aware of.

Do you have backups? Are you amenable to a full factory reset before trying the OTA upgrade again?

[winghongchan]

I don’t think I have any custom recovery and I haven’t unlocked the bootloader.
I’d like to avoid doing a factory reset because I would need my bus transit pass reissued.

I think the Updater is a little confused right now. I restarted my phone into safe mode just to see if my phone’s still on 13.0.5, and yes it is. The Updater lets me install 13.1.0, but when I tap “Install”, the dialog box says I’m about to install 13.0.5. So I’m not sure what it’s trying to do (this also happened outside of safe mode).