I have problems with getting my 2e connected to my Windows 10 PC so that “adb devices” shows my device when in fastboot mode. It simply does not show. I even installed the MTK VCOM USB drivers, but this did not help. When booting the device normally and connecting it to USB it is getting recognized by “adb devices”, but it is not after booting it into fastboot mode. Windows 10 device manager shows an “Android” device with an exclamation mark. Any hint? Would be much appreciated!
It’ll not respond to “adb devices” once it is in fastboot mode. You need “fastboot devices” at that point.
1 Like
Thanks! “fastboot devices” also did not show anything. But I got it working now!
By using the MediaTEK drivers available here:
The drivers mentioned in the posting under “Optional Windows drivers” seem not to work really.
3 Likes
Thanks a bunch for posting the new drivers.
1 Like
I tried the method above for about an hour, in which it went to fastboot fine, but kept ‘waiting on device’ when trying to flash unlock. Tried a couple of driver packs to no avail, but the Mediatek drivers worked! Thanks a lot for sharing that Jaxom! Maybe the guide can be updated with these drivers? Thanks again to Jaxom and Sharad for the helpful information!
2 Likes
I used the setup ‘signed’ drivers.
Me, too. The Automatic installation.
I downloaded the drivers. Even though they say “signed”, the Windows security prompt said source: “Unknown”. Do you guys know any truly signed source?
Yes, sure you are right. I did take this risk. At least it was better than having to configure Windows 10 to not check drivers signatures at all to get the (not working) driver installed which is originally linked in the article… And sorry, no, I did not find any better source.
1 Like
Same for me.
1 Like
Sorry to bump this topic, but when I do the above instructions, I get “Unlock Failed”. I’m on Windows 7, and I have the Teracube 2e phone.
EDIT 6/5/2021
Nevermind, I didn’t see the instructions to go into the Developers menu and enable “OEM Unlock Bootloader”
1 Like
Should only download from trusted sources.
Scroll down to the MTK (aka MediaTek) section for driver download.
1 Like
Thanks @SaraphimAngel for letting us know. Could you confirm if the download from Android Developers website work?
1 Like
Confirmed… I am on the latest firmware SW16 and latest Phhusson GSI AOSP 11.0 v312
2 Likes
Cool - have downloaded the official drivers and hosted them on our own servers (since the direct Mtk link is a bit fidgety).
1 Like
"OEM Unlocking" is missing from my developer options on my 2E.
I am trying to root the phone… mostly so I can get call recording to work… “Cube ACR” doesn’t work, so I’m trying “boldbeast” call recorder. Still, it would be nice to be rooted. I have googled this and found very little specific to /e/ os or teracube. Does anyone have any words of wisdom for me ??? Thank you in advance.
My build # is
e_2e_userdebug 10 QQ3A.
200805.001 eng.root.
20210827.151134
dev-keys,stable-release
There’s your trouble… I sh*t you not, I get better results for /e/ foundation stuff when I use DuckDuckGo instead of Google. Maybe this is the link you’re looking for? It was literally the first hit when I DuckDuckGo’d “e foundation teracube 2e”
The specific link you want for enabling OEM unlock is here. Scroll down until you see “Steps to enable OEM Unlock through the command line” You’ll need a desktop/laptop with fastboot and adb installed to do this, but you need that for the rooting process anyway.
The instructions are pretty thorough, but I can’t vouch for them personally, because I ordered the “Murena” 2e with /e/ OS preinstalled. I did however install /e/ OS from scratch on my previous Android phone, so I’m happy to try to answer questions if you run into any problems…
2 Likes
Thank you very much for this. It looks as if I don’t have the “oem unlock” in the gui of developer options, but can do it via usb debugging. No problem. I am a little confused… can someone expain to me the difference between the stock teracube rom (which I though was /e/ OS and the /e/ OS that people install or get via Murena? I bought two phones used, and both have /e/ OS and I thought they were stock roms… no biggy if not. Thank you ecs for your help. 
1 Like
I found this a bit confusing too. I think you could have two things if they have /e/ OS already: they’re either Murena, like mine (in which case /e/ foundation has already unlocked the bootloader), or they’re true stock (like you would get from Teracube), where someone else has installed /e/ OS aftermarket (but would need to unlock the bootloader first). Hypothetically, you shouldn’t be able to tell the difference, and it shouldn’t make much difference for rooting, but I did have to root my Murena slightly differently from the method discussed here.
One way to get an idea of which kind of installation you have is to boot to the recovery software. If you go to “Developer options” and enable “Advanced restart,” you should be able to reboot directly to recovery by holding down the start button and selecting restart then recovery.
If the recovery is /e/ foundation software, then you probably have a Murena, if it’s TWRP, then someone installed /e/ OS on a stock phone. Either way is fine, it’s actually a little easier with TWRP, in my opinion.