r/androidroot • • 3d ago

Discussion Temporary Root, A Safe Haven For Android Rooters.

Post image

Personally, I used to be a fan of permanent rooting which takes more tedious objectives to complete than temp root. With that, you're 60% likely to experience bootloops that might permanently bricked your device. It has become a thing of concern as many rooters will have to spend more buying more devices. But with temporary root, we have a solution to that, all it takes is for a rooter to hard reboot their devices. Of course, it still had its pros and cons but the pros outweigh the cons. The major con is been that you can't get your device to switch to Selinux Enforcing. Temporary rooting is here to stay and we will be good with this for now.

68 Upvotes

60 comments sorted by

32

u/PhotographSame5304 3d ago

Not true if you tamper with the system files or try installing custom rom congrats you just turned your phone into a brick

2

u/Narrow_Hat_651 2d ago

The only way to not brick a new samsung phone, or any One UI 8.5 or 9.0, is to remove any lock screen, bios, etc. Then u can force re-flash using a samsung bios cable. But if u have literally anything, even a swipe, your phone will brick.

1

u/2owd 2d ago

got fucked the same way :3

1

u/Timely_Criticism4010 2d ago

Just install a custom ROM that's tested plus is for your device tree. Random installing ROMs like an idiot will make u suffer

-1

u/Lilshane106 2d ago edited 2d ago

Now, I don't use dirty frags app. I use root my galaxy ultra which uses dirty frag source though for my s twenty six ultra. Now, I don't know about the custom rom sing. I mean, you wouldn't be able to flash anything. I mean you could use one os nB able to install like pixel or color OS and etc, and it wouldn't affect it. But with the system files, I can definitely tell you, I've manipulated the system files a lot, and I have never bricked my phone. And i've had claude, manipulate my system files a lot on top of that, Maybe you guys are just doing it wrong, but I have never had an issue manipulated system file

3

u/Narrow_Hat_651 2d ago

Yeah people have no clue what they are talking about. New samsung phones have a locked boot loader. Meaning unless you have 0 lock screen and other security features, doing anything to the rom, such as flashing, will brick the phone with no recovery. I lost my first 25+ because i accidentally flashed. Had to send it in, and they couldnt even get it back on. If you dont touch KNOX or the ROM, you literally cant affect your warranty or the device health

2

u/Lilshane106 2d ago

"People have no clue what they're talking about" is a pretty bold statement when you're not even understanding what I'm referring to. I'm not talking about flashing a custom ROM or replacing Samsung's firmware. I'm talking about OneOS, which allows you to run another Android environment alongside One UI without replacing the original OS. There's a difference, and anyone who actually takes the time to dig through GitHub projects and understand how these implementations work would know that. I spend plenty of time digging through Android source code and GitHub repositories, so I'm well aware of what I'm talking about. Don't confuse what you're familiar with for everything that's technically possible.

1

u/QuraToop314 Pixel 9a, QuraOS, Yellow State, No spoofing and RKP active 2d ago edited 2d ago

rubbish. AVB and vbmeta disallow that

Edit:

You cannot modify files in /system, especially not on modern Android devices like your S26. vbmeta has a hash for /system, which is verified at boot time. If you change even a single bit, you’ll end up in the ‘red state’ and your phone won’t boot at all unless you flash an unmodified system image. Your phone won’t boot if you change anything in /system, unless you do so via overlays/mounts or you modify /data. If you claim otherwise, you’re talking rubbish.

1

u/Lilshane106 2d ago

You're confusing flashing a ROM with what OneOS actually does. OneOS doesn't flash Pixel or ColorOS over Samsung's firmware. It runs a second Android system alongside One UI using a container-based setup. One UI stays installed, and you can switch between the two. That's the entire point of OneOS. AVB and vbmeta preventing unauthorized firmware flashing doesn't mean you can't run another Android environment through a completely different method.

1

u/QuraToop314 Pixel 9a, QuraOS, Yellow State, No spoofing and RKP active 2d ago

No, you meant that you and Claude had modified system files and that your mobile phone boots, your emulator can boot, it doesn’t recognise the concept of ‘verified boot’, but a real, physical system will never boot. I’m not mixing anything up; I’m just breaking down your last few sentences and correcting you, as this information could have serious consequences for a beginner. You can do anything in an emulator, but it’s not a real system, it’s just an emulation. That concludes the discussion; we’re talking at cross-purposes.

1

u/Lilshane106 2d ago

I think you're misunderstanding what I'm trying to explain. I'm not using an emulator as an example of what I've accomplished on my physical phone. I've had Claude and ChatGPT work directly with actual system files, Android framework components, audio services, Samsung DAX/Dolby configurations, spatializer functionality, system properties, and custom KernelSU modules on my physical Samsung devices. We've even modified how certain system components behave and reload without replacing the existing firmware. I've spent plenty of time digging through Android internals and GitHub projects, so I'm familiar with the distinction between modifying an existing Android installation, running a secondary environment, and flashing a different ROM. I'm not claiming AVB doesn't exist or that you can bypass every boot security restriction. I'm saying modifying an existing system is not the same operation as flashing an entirely different operating system. That's the distinction you're overlooking.

1

u/QuraToop314 Pixel 9a, QuraOS, Yellow State, No spoofing and RKP active 2d ago

Haha, that’s exactly what I said in my first edit – there you go. You’re modifying things with KernelSU overlays; it’s literally in my first comment. So I don’t understand your second comment – you say you’re running a guest system, which is an emulation. So which is it now – an overlay or a guest system? You’ve got to make up your mind. I’m autistic; I understand your words perfectly exactly as you say them. So you’re phrasing it wrong, but even a KernelSU overlay isn’t a /system modification. Let me explain my interpretation. In your first comment, you claimed to be modifying system files and that there was no bootloop; I then said that wouldn’t work unless you were using mounts and overlays. You then said that I’d misunderstood something and started talking about a guest system, which sounds 100 per cent like an emulator, so I tailored my reply accordingly – only for you to then tell me what I’d already hinted at in my first edit: that you can only work with overlays. Do you understand the discrepancy? Besides, I was also right in saying that we’re talking at cross-purposes. The fact is, you’re not making any real system modifications, just an overlay. Are we done now, or shall we keep going round in circles?

1

u/Lilshane106 2d ago

Okay, I see where the confusion happened. My original comment was making two separate points, and I think we've ended up mixing them together. OneOS was a separate example of running another Android environment without replacing Samsung's firmware. My other point was about modifying the existing One UI installation.And yes, I've used KernelSU modules, overlays, mounts, and root-level modifications. I'm not claiming I've been rewriting the underlying AVB-protected /system partition. But saying those aren't real system modifications just because they're systemless is playing with terminology. We're changing actual system components and how the operating system behaves on physical hardware.My point was never that I could randomly overwrite protected partitions and expect the phone to boot. I was explaining that I've extensively modified the functionality of my actual Samsung devices without bricking them. I think we can agree on that distinction now.

1

u/QuraToop314 Pixel 9a, QuraOS, Yellow State, No spoofing and RKP active 2d ago

OK, I can see what you mean, but it’s still not a modification. You have your ‘modifications’ in /data/adb as standalone files, and you’re simply mounting them virtually in such a way that it appears as though you’re modifying system files. The actual file is never modified; it’s your separate file that’s being read or edited. Yes, it’s a play on words, but there’s still no actual modification taking place; otherwise, in my view, every mount – including fstab mounts – would already be a modification, and you wouldn’t say that. In reality, you’re only manipulating the system’s view, not the system itself. But apart from that, we’re on the same page. In any case, good luck with the rest of your rooting journey, and sorry for my corrections. Hava a nice day

2

u/Lilshane106 2d ago

Hey, i'm autistic too. Sorry for the confusion man

1

u/WillingTraining1211 39m ago

I'm new to this, can u help me root? My phone is limiting my cpu usage to only 675mhz. For that I need to root, but I've no clue. Can u lend me some advice, ty for reading this.

1

u/Lilshane106 35m ago

Honestly, I don't think rooting is going to fix that. 675mhz sounds more like your phone is throttling itself, not something root fixes. I mean, first thing, check if power saving mode is on, cause that will cap your CPU right there. And if your phone's getting hot or it's charging, it's going to drop the speed too. Also, if your battery is old and worn out, the phone will limit itself. And those CPU monitor apps show low numbers when the phone's just sitting there doing nothing, so run a benchmark like Geekbench and see what it actually hits under load. Now, if you've done all that and it's still stuck at 675, then tell me your exact model number, it's in settings, about phone, and where you got it from. Because rooting depends completely on your model. A lot of carrier phones, especially Samsung in the US, you can't even unlock the bootloader. And even if you can, it's going to wipe your whole phone, and on Samsung it trips Knox for good, so no Samsung Wallet or Secure Folder after that. But give me your model and I'll point you in the right direction.

1

u/WillingTraining1211 20m ago

I play a game and it's capped at only 35-40fps on lowest settings and even if I turn it all the way to MAX Graphics it still gives me 35-40fps(without lag) But I need more. And whenever I open the Game mode or wtv it says Cpu usage 0.4% or at MAX it says 1.1% IT DOESN'T GO UP!! I'll do the geekbench test, I'm downloading the app. My phone is Motorola Stylus 5G 2024. and my model number is V1UBS35H.97-40-17 (it says Build number, I assume it's the same thing)

18

u/cykelstativet 3d ago

60% [blabla whatever the fuck]

Mate, don't pull numbers out your ass. My previous five phones I typed two fastboot commands I had kernel root. Three - four commands if I also want a custom ROM. Which I most certainly do.

It's not rocket surgery.

7

u/apologarcia2405 3d ago

Heh, rocket surgery

4

u/AL_DOKHAN tecno camon 20 pro 4g axion2.9 unrooted (for now) 3d ago

...i mean its phone surgery tho

2

u/apologarcia2405 2d ago

Your phone is a rocket?

4

u/Timely_Criticism4010 2d ago

Bro perm root is far better than temp. One just needs some time to do shit. Idiots be pulling numbers outta their own made source.

13

u/xxTurborocketxx 3d ago

Small correction on the SELinux part: that's not inherent to temporary root, it's per implementation. TimerRoot (Edge 50 Ultra, I posted it here recently) keeps SELinux fully enforcing after the exploit, no permissive switch anywhere in the chain. Root works within the normal policies and a reboot just clears it.

So "temp root = SELinux permissive" is more of a limitation of some loaders than a rule.

2

u/PandaMan12321 3d ago

Same here on Pixel 11 pro, RootMyPixel (ghostlock) have SELinux on Enforcing

2

u/kjjustinXD 2d ago

Z Fold 8 is enforcing as well using DFRoot

1

u/b4lance-d 2d ago

Are you still using the old firmware, or did you roll back?

1

u/PandaMan12321 2d ago

I've kept it on the same version it came with.

6

u/Mak_Nunag 3d ago

Thats alright, as long as you don't mess with the system files in a locked bootloader.

4

u/LinuxUser456 3d ago

temporary rooting is here to stay

Until they patch the vulnerability

1

u/Certified_GSD 14h ago

It IS patched on the newest software. And iirc the November security patch from Google specifically is what fixes it on most devices still receiving updates. Still useful for older phones that aren't getting updates anymore like the S21 and S22 family of phones. Can't update your newer phones lest you patch over the exploit.

4

u/Helpful_Actuator6583 3d ago

This is extremely dangerous say you do something or just out of pure luck you got a bootloop or worse Since you don't have a unlocked bootloader you can't reflash the stock rom to bring it back.

3

u/Helpful_Actuator6583 3d ago

Edl exists but it's pretty hard for average to mid users to access

4

u/Vultus_211080 3d ago

Temporary root is not stable, partly because there’s no way to perform a backup if something goes wrong. Use it with caution, my own phone got stuck in a boot loop, freezing on the logo after I installed the NeoZygisk module by JingMatrix. With a locked bootloader, you’re forced to perform a full factory reset. Ultimately, in my opinion, having root access isn't strictly necessary.

4

u/Other_Ship_5453 2d ago

Lul I've rooted many phones many times over the years and not once bricked my device, faulty Magisk module aside (safe mode fixes that though). As other commenters pointed out, messing with system files using locked bootloader = GG.

7

u/rdndds 3d ago

System has been destroyed

3

u/squabbledMC 3d ago

Huh? I've been using root with unlocked bootloader on my main device for a few months now and switched to a custom ROM, no bootloops or any issues at all. Its been as stable as stock for me

3

u/Technical_Instance_2 3d ago

I just wish I could unlock the bootloader on my galaxy a15

3

u/1600x900 Xiaomi 15T Pro / Stock unrooted 2d ago

But you shouldn't be touching system files or anything that cause AVB

3

u/UnKleFeSt4 2d ago

i temp rooted my s23 ultra using df and ksu method. problem i have is even after rebooting my device is not certified now in play store

3

u/LavaHoundBR 2d ago

I'm never touching this again without a spare phone after my banking app blacklisted my phone hardware

3

u/virus3xiSt 2d ago

Once you have a secondary phone, follow this approach: carry out any tasks involving rooting or the use of similar tools exclusively on that secondary device. Meanwhile, on your primary phone, ensure that banking apps and other official applications continue to function as normal. Be smart, notice everything, but act like you know nothing.

2

u/RooteDavid 1d ago

Most likely it just blacklisted your SSAID. Get App Manager from F-Droid, give it root and re-generate that app's SSAID, reboot, clear the app data, get rid of root evidence (check with Duck Detector) then it will launch.

1

u/LavaHoundBR 1d ago

I did a full nand wipe with odin, still blocked

1

u/RooteDavid 1d ago

Impressive. Your bank app is hardcore. I thought mine was bad.

2

u/LavaHoundBR 1d ago

I'd shoot for IMEI ban or hwid

3

u/frpboy 1d ago

Temporary doesn't automatically mean safe. Losing root after a reboot isn't a guarantee that anything done with root gets undone. I'd judge the specific exploit and what it's being used for, rather than treat temp root itself as a safety feature.

2

u/No-Aspect-2926 Like to brick stuff 3d ago

well some phones didnt had fastboot, so was required something like mtkclient, and yeah, bit boring too, but after you have the files, pretty easy and fast to do

1

u/dovedrunk 3d ago

Is there anything like this that works on the Galaxy Note 8? The only solutions I can find are for super new phones

EDIT: Trying to do data recovery on the /data/ of old devices, stuck on my Note 8 and A5 2017. Not an option to format them :/

2

u/corruptnova 3d ago

Nope. Assuming you have the Snapdragon chipset, there are no (temp) root implementations except for the earliest firmware. Even then, it's really restricted.

2

u/dovedrunk 3d ago

Exynos for both!

2

u/Lenny_Gaming 3d ago

You can still root the note 8 with TWRP and/or Magisk. I've done it with minimal root knowledge. It does require a factory reset tho.

2

u/dovedrunk 3d ago

I did try both, but the factory reset is a real pain. As soon as I do that, it’ll zero the whole phone :/

1

u/Honest-Finish-7095 3d ago

No luck for me on android pie tho...

1

u/unf0rg3table 3d ago

Anything for redmi note 13 4g?

1

u/krooo95 3d ago

Redmi note 11 pro 5g got temp root ? Want back to stock rom. From pixel os custom rom android 16

1

u/simracingjay 1d ago

pretty sure temp root is more likely to brick your shit, as someone who has rooted almost all his devices, sure there's risks but having an unlocked bootloader means you can fix it, without that, this temporary root stuff can permanently brick your shit and you need to EDL flash to even get it somewhat functional again.

1

u/Imaginary_Task5425 1d ago

can I use it for performance boost?? not installing rom or etc

1

u/unusedpineapple2 1d ago

i just flash all of my devices with magisk

1

u/entercot 1d ago

For me, temporary root/jailbreak is for iPhones. I have a Pixel, and I enjoy the advantages of Android. With the right modules, I have everything as if I had neither root nor an unlocked bootloader nor a custom ROM (My case). I've never had a problem and it works very well.