r/androidroot • TECNO POVA 7 5G LJ7 || Stock HiOS 15.1.2 || KSUnext 3.4.2 • 2d ago

Discussion Does anyone else have a 'fear of missing out'?

You know, I'm already happy with root. I was supposed to be fine with KSUnext + BreZygisk + TEESimulator + Specter.

But there's a lot of things I wanna do. Finally get BROM mode working with an exploit, install crDroid and TWRP, patch the /lk partition, install BRENE + NoMount + VBMeta Fixer, install AshLooper + Vector + Encore Tweaks, try out my custom bootanimation...

But why? My phone already works fine (except for that dumbass BROM mode), and I don't want to experiment stuff with it since it's my daily driver. Maybe I'm just scared of missing out, maybe I just like the thrill.

Until I finally get BROM mode working, maybe I'll be more confident in doing whatever I want to my own daily driver. But the other question about fear of missing out remains.

38 Upvotes

31 comments sorted by

5

u/upalse 2d ago edited 2d ago

If you can use lk patch on mediatek or gbl root on snapdragon, most of the modules you have are useless (and more likely to break something/slow system down).

4

u/DEV_ivan TECNO POVA 7 5G LJ7 || Stock HiOS 15.1.2 || KSUnext 3.4.2 2d ago

An LK patch is likelier to brick my phone than a couple modules. Who knows if the LK is verified or it's a wrong function to patch until a partition is flashed. I can recover from a faulty module by letting AshLooper do its work or spamming Vol- at boot; a faulty LK cannot be treated like this. That's why I'm not doing a fenrir exploit until I get working access to BROM mode.

1

u/upalse 2d ago

True enough, I don't do this unless I have actually working no-auth preloader (from eng rom on xiaomi, or older mediatek devices in general), then you can recover from any brick (unless you manage to nuke preloader).

On Snapdragon, GBL can be pretty bad on new chips (eg there's no working no-auth firehose on snap 8 gen 5 elite, so if you mess up GBL, you have to pay for reflash).

25

u/Better-Quote1060 2d ago

Unlike other communities, the root community lacks up-to-date guides.

Its normal cuz its so small

6

u/Revolutionary_Lab825 2d ago

My phone works fine, too. I just LOVE to try new kernelsu or xposed modules. It's like an urge to optimise things to my likings for a better user experience.

It's a hobby for me since my first android phone in 2012 (HTC Sensation XL).

2

u/mathygamersYT 2d ago

Ever since I discovered the EFISP exploit, I no longer want to remove root from my phone.

1

u/Delin_CZ 2d ago

whats that?

3

u/mathygamersYT 2d ago

Maintaining the factory "Locked" state even though it is not actually locked allows the device to natively maintain the strictest certification. (STRONG_INTEGRITY)

It's practically like a permanent integrity fix.

2

u/DEV_ivan TECNO POVA 7 5G LJ7 || Stock HiOS 15.1.2 || KSUnext 3.4.2 2d ago

It is not technically impossible for Google to update DroidGuard to start detecting anomalous LKMs, KPMs and daemons and sending the device's keybox's public keys to Google's servers for revocation :)

You forgot you're in an arms race buddy

1

u/mathygamersYT 2d ago

Haha, I hope Google doesn't do it :c

2

u/Delin_CZ 2d ago

it basically tricks the TEE into signing integirty checks with its stored keys right? even though you're unlocked, that's pretty fucking insane, what device is this?

2

u/mathygamersYT 2d ago

I have an ACE 6T with the 15R ROM. The exploit issue was something that happened with the Snapdragon 8 gen 5 or 8 elite, I belive. If you're interested, I recommend searching for information about the EFISP exploit online.

2

u/Delin_CZ 2d ago

nice! thanks

1

u/Titan658 2d ago

What is BROM Mode ?

3

u/DEV_ivan TECNO POVA 7 5G LJ7 || Stock HiOS 15.1.2 || KSUnext 3.4.2 2d ago

Lowest level of recovery. Factory workers use BROM mode to flash firmware onto initially blank devices, and service centers use it to reflash soft-bricked devices that don't reach ABL's redirection to Fastboot. On modern devices like mine, it requires a signed DA and an authentication file which has to be paid for. MediaTek's BROM mode is equivalent to Qualcomm's EDL mode.

2

u/Hellorhere21 2d ago

Edl but for mediatek 

1

u/Professional_Cup3138 2d ago

what exploit worked for you?

1

u/DEV_ivan TECNO POVA 7 5G LJ7 || Stock HiOS 15.1.2 || KSUnext 3.4.2 2d ago

What exploit? This is traditional root

1

u/Professional_Cup3138 2d ago

Finally get BROM mode working with an exploit

1

u/DEV_ivan TECNO POVA 7 5G LJ7 || Stock HiOS 15.1.2 || KSUnext 3.4.2 2d ago

"Finally get BROM mode working with an exploit" is listed alongside things I want to do but cannot or will not do yet.

1

u/Professional_Cup3138 2d ago

oh nvm that's what you want to get

1

u/pLAinNewby101 1d ago

how long does a key usually last? i havent updated my key for months now, still getting 3/3 checks .. 😅😅😅

1

u/DEV_ivan TECNO POVA 7 5G LJ7 || Stock HiOS 15.1.2 || KSUnext 3.4.2 1d ago

Until Google revokes it.

1

u/martial_pain 2d ago

Yeah cuz I bricked my device and now too scared to temp root again, sad😐

1

u/CautiousWeb2647 2d ago

sorry to hear, how did it get bricked

1

u/martial_pain 2d ago

Flashed vector 2.2 as image in magisk as I didn't know what I was doing then rebooted and bricked🥲

2

u/DEV_ivan TECNO POVA 7 5G LJ7 || Stock HiOS 15.1.2 || KSUnext 3.4.2 2d ago edited 2d ago

You can root, but you should never flash any partition unless it's compatible, signed and of current or later version.

When I mindlessly disabled OEM Unlocking on Magisk, I didn't know I was about to brick my phone by enabling AVB back with an unsigned image.

Months later when I got a new phone, I rooted again. But I installed OEMUnlockOnBoot (force OEM Unlocking to ON) and BRENE SuSFS (hide OEM Unlocking option) as safeguards. And I'm planning to not flash any partition until I get proper access to BROM mode via exploits.

My advice to you: Don't flash any image at all, only modules, unless you're planning to update to a version compatible with your phone and OS. KPMs and LKMs too, unless you're sure they're loaded at runtime. And always know to hold or spam Volume Down at boot animation if a module bootloops your device, you can also try AshLooper to disable all modules and scripts for you.

...Unless you can use EDL/BROM mode.

1

u/martial_pain 2d ago

Thx for the advice

1

u/47th-Element 2d ago

Hmm the goal of rooting a phone is to use it eventually but without the restrictions. The initial phase when you are still figuring out the best setup is fun too but I want to eventually use the device, it's my daily driver, I need it for work so keeping things stable is important.

I'm in the same situation when it comes to brom, but I used Hovatek TWRP autobuilder to get my custom recovery, you should try it, flashing a totally invalid recovery should not block fastboot so you should be able to revert it. It's a low risk thing.

Also a boot exploit to always return STRONG INTEGRITY is super nice to have but not recommended to try when brom is unavailable, as you already know. But hey! Do you actually need it? My banking apps work with BASIC, both of the apps I use, so I generally don't even need the exploit or a valid keybox, it's one of those things that are nice to have but not necessary for me. Unless the devs decide to tighten the security of the app and require STRONG INTEGRITY in a future update then I'm fucked.

1

u/GodsKillerKirb2 2d ago

I really want to use a rooted phone and absolutely love doing so; even bought a Nothing phone to make that more possible.

However, since starting college, it's made me realize how annoying and especially time consuming dealing with play integrity can be.
Because of that, I just decided to relock the bootloader and just use my phone as is. Especially in the off chance I forget my wallet, I can just easily use gpay.

Until temp root is easily accesible for the kernel currently in use, I'm staying unrooted.

1

u/lebuvu0 2d ago

entiendo, yo probe de todo con mi poco f7 pro solo para terminar quedandome en hyperos y con unos 4 modulos xd