Orange state everytime phone reboots /e/ OS

Teracube 2e
#3

Thank you that makes sense now. So now do I have repeat all the steps from unlocking bootloader to disable avb to flashing twrp to install iodeOS.

i’m using /e/ os right now would like to switch to iodeOS. i’m guessing I can skip the bootloader step since my phone is in orange state. Probably have to disable avb again just to be safe.

#4

If your bootloader is locked again, you’ll want to unlock it first despite the orange state. But as long as it’s actually unlocked, you’re probably at the stage where you’re ready to load TWRP into the system and then you can adb reboot recovery to get in. If you aren’t planning on wiping everything, be sure to disable ANY AND ALL screen locking security. If you have anything beyond swipe (even just a basic pattern) enabled, TWRP will not be able to access the data and you may or may not be able to reboot back to system without wiping data again. As people will repeatedly note in just about every release, the Teracube TWRP can’t decrypt yet, so it gets angry when you make it try.

1 Like
#5

Yea you are right i should unlock the bootloader just in case. And to remove password.

Weird thing I noticed that in /e/ os doesn’t have oem unlock in the developer options. im guessing fastboot flashing unlock should do the trick. Or add in fastboot oem unlock

#6

Alternatively, since you’re going to another OS that doesn’t involve data survival, you could reflash stock to make it super safe. Up to you.

#7

Apparently when I attempted to sideload the iodeos rom.
I got this error

Unmounting system....
E3004: This package is for device: 2e.Teracube_2e;
this device is yk673v6_lwg62_64

#8

Yea maybe I should try reflash stock. How do you flash if you’re on linux

#9

[Advanced] Installing an Android image w/ SP Flash - Guides - Teracube Community (myteracube.com)

The SP Flash directions will get you back to full stock. Alternatively, you can just reload the recovery from the full stock image. I’ve done that before. It’s definitely faster.

1 Like
#10

Ok I was able to flash full stock!

#11

Orange state notifies that bootloader is unlocked. Its not a problem by itself as long as you are aware of the reason. You will have to stay in this state if you want to run /e/ OS or any other non-stock firmware.

#12

For some reason I can’t sideload the iodeOS because the device name is yk673v6_lwg62_64 instead of 2e,teracube_2e .
Maymne mention this in another thread

#13

We’ve had a variety of different devices for our TWRP versions. The stock recovery is Teracube_2e, the SourceForge TWRP is 2e (no Teracube_ prefix), and the ‘official’ Github TWRP is the yk673v6 device name. While nothing except stock works to flash Stock16, getting Magisk up takes some variety of TWRP. It’s part of the fun.

#14

So what should I do, I dont quite follow. Sorry lol, figuring it out as I go lol

#15

Try this version of TWRP: malvibuilds - Browse /Teracube-2e/TWRP at SourceForge.net

You should be able to flash it from inside TWRP. This should be the version named 2e, which (based on what you posted above) should count as valid for flashing iodeOS for you.

#16

Oh ok, so I do this fastboot flash recovery recovery.img for the TWRP part?
fastboot reboot

#17

Or you can boot into TWRP and flash the img file from in there.

1 Like
#18

OMg it worked!

#19

Thank you so much Maymne!

#20

Glad to help. I don’t always track my emails or the forum especially well, but always happy to be of service when I see the messages. :slight_smile:

2 Likes
#21

Glad it worked. @Maymne - thanks for helping out :heart_eyes:.

@ide - could you do a mini write up on what issues you ran into and how did it work out finally. Might be helpful for other users.

#22

Sure.

Issue #1 Disabling avb with the vbmeta-2e-stock.img caused data corruption for me.

Solution (found this solution in this post [Advanced users only] TWRP recovery + root for Teracube 2e)

I flashed it with vbmeta.img instead fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Issue #2 I wasn’t able to sideload the os zip file because the official github TWRP version name didn’t
match with device name

solution (Thanks to Maymne) :

Download this twrp recovery malvibuilds - Browse /Teracube-2e/TWRP at SourceForge.net and fastboot flash recovery recovery.img

1 Like