it wont have an effect
it wont have an effect
so in your case bro, when you powercycle your phone after the rooting process, you didn't receive "dt-verity error" right?
nope it wont be risky i've don't it a couple of times but nothing happened and that stock image you have you can use that to patched it and re root your phone againI have backup my stock firmware beforehand with the use of 'mtkclient' maybe I could try to return to stock and redo the rooting process again? but seems like it's gonna be risky returning to stock, right?
oh now that I think about it, was it because I used the boot.img provided by @Zezo 089 and not the boot.img that is on my phone system before it was rooted? Was that the reason why I got the 'dt-veriy error'? I should have use my boot.img and patched it with magisk right? or it doesn't matter though?nope it wont be risky i've don't it a couple of times but nothing happened and that stock image you have you can use that to patched it and re root your phone again
nope it wont be risky i've don't it a couple of times but nothing happened and that stock image you have you can use that to patched it and re root your phone again
so when I tried to patch again this time with the patched boot.img from the stock boot.img of my phone, it still didn't get rid of 'dt-verity error" because it's already triggered due to my first flash of boot.img? I don't know if that's the reason but correct me if I'm wrong bro.oh now that I think about it, was it because I used the boot.img provided by @Zezo 089 and not the boot.img that is on my phone system before it was rooted? Was that the reason why I got the 'dt-veriy error'? I should have use my boot.img and patched it with magisk right? or it doesn't matter though?
it could be the source of the error and yes it doesnt matteroh now that I think about it, was it because I used the boot.img provided by @Zezo 089 and not the boot.img that is on my phone system before it was rooted? Was that the reason why I got the 'dt-veriy error'? I should have use my boot.img and patched it with magisk right? or it doesn't matter though?
thats the only command you should use since thats the original command that needs to be used in mtk clientbro can you guide me, I invoke this command for backing the firmware of my phone:
and it stored successfully on my PC, if I want to restore my phone back to stock, I should just invoke this command right?
or do I need to tweak or do something beforehand?
hmm so you already flash it successfully right ? but still didnt get rid of the message, no it wasn't triggered because it happens first its a problem that still persist because it still wasnt fixso when I tried to patch again this time with the patched boot.img from the stock boot.img of my phone, it still didn't get rid of 'dt-verity error" because it's already triggered due to my first flash of boot.img? I don't know if that's the reason but correct me if I'm wrong bro.
yes bro, I already tried the patched boot.img that I backed up but no effect.hmm so you already flash it successfully right ? but still didnt get rid of the message, no it wasn't triggered because it happens first it a problem that still persist because it still wasnt dix
there must be a really problem with it but you can just leave it if it doesnt bother you anywayyes bro, I already tried the patched boot.img that I backed up but no effect.
I also read someone in other forum that he also got the 'dt-verity error' after rooting so I guess I'm not alone, anyway I won't be thinking this alot anymore since it's not affecting the overall function of the phone. Thank you very much bro and @Zezo 089 for all the help.there must be a really problem with it but you can just leave it if it doesnt bother you anyway
your welcome bro glad to helpI also read someone in other forum that he also got the 'dt-verity error' after rooting so I guess I'm not alone, anyway I won't be thinking this alot anymore since it's not affecting the overall function of the phone. Thank you very much bro and @Zezo 089 for all the help.
Nopeso when I tried to patch again this time with the patched boot.img from the stock boot.img of my phone, it still didn't get rid of 'dt-verity error" because it's already triggered due to my first flash of boot.img? I don't know if that's the reason but correct me if I'm wrong bro.
You are welcomeI also read someone in other forum that he also got the 'dt-verity error' after rooting so I guess I'm not alone, anyway I won't be thinking this alot anymore since it's not affecting the overall function of the phone. Thank you very much bro and @Zezo 089 for all the help.
okay nevermind, I found the solution guys for reference:@Zezo 089 @Anonymous V hi guys, it's me again, may I ask if you have solution for the persistent notification "Rooting of your phone is detected" in the notification bar?
yep i was going to tell you to use thisokay nevermind, I found the solution guys for reference:
Might have any optimizations or tweaks you wanna share bro?yep i was going to tell you to use this
if a notification tells you that you have a root detected , just turn on hotspot and turn it off
bootloader unlock = OK
, unplug your phone and press power button , if you found a warning message while booting , so , unfortunately....pip3 install -r requirements.txt
python setup.py install
or python setup.py
python mtk da seccfg unlock
waiting for device
.. power off your phone and press vol up + vol down + release when connected, then let it do the magicyour device storage reached the end of life
, bruuuuuuuh, just uncheck (checking the device status) from settings and retry flashing!BruhThank you for creating the thread @Zezo 089 , I am using Oppo A5s and now I found a way to root the phone.
I've already download all the requirements first to prepare.
But, I could not run the "MTK CLIENT TOOL V5.2".
It was just nothing appear when I double click the application.
I use Windows 11. Did it caused by the Windows?
Other question is what step is the boot.img file needed?