Hey guys,
So the last Samsung device I owned was S7, So I'm pretty familiar with Odin and flashing to Samsung.
However still quiet new, I was reading in forum that after rooting S21Ultra, Knox would be a huge headache. And Samsung pay would not work.
So just wanted to know what all are things that break after I root. And will my phone be able to pass the safety net with additional modules? Like safety net fix.
Thanks for your reply.
Also if someone could link a thread to unlocking and installing twrp and rooting it. That would be great, as I'm unable to find it. I' have the snapdragon variant
No Problem,donʼt worry it is true that after unlocking bootloader banking apps will not work (also MyJio app) but you can fix it by safetynet fix and magisk hide or zygisk for further help you can contact me on telegram @the_arxyn
the_arxyn said:
No Problem,donʼt worry it is true that after unlocking bootloader banking apps will not work (also MyJio app) but you can fix it by safetynet fix and magisk hide or zygisk for further help you can contact me on telegram @the_arxyn
Click to expand...
Click to collapse
Thanks for your prompt reply. Im unable to find links to telegram groups for S21 Ultra. Do you have any ?
I will later send u on telegram
Related
Hey Guys, you see i am the new onem
i cant find a direct answer by searching, so sorry if the question is answered many times.
I want to know of you experts if there is a common method in rooting the Samsung Galaxy Tab S2 (T810) without tripping Knox or void my warranty.
Ty so much for any answer, every help is appreciated.
Greetz
TheNewOne11 said:
Hey Guys, you see i am the new onem
i cant find a direct answer by searching, so sorry if the question is answered many times.
I want to know of you experts if there is a common method in rooting the Samsung Galaxy Tab S2 (T810) without tripping Knox or void my warranty.
Ty so much for any answer, every help is appreciated.
Greetz
Click to expand...
Click to collapse
Rooting your device is not illegal. Ofcourse Samsung will do believe you it is. And you'll get a hard time goaling your rights...
halloarno said:
Rooting your device is not illegal. Ofcourse Samsung will do believe you it is. And you'll get a hard time goaling your rights...
Click to expand...
Click to collapse
Ty for this information, but the best way for me would be to root without tripping knox. I just cant find clear informations :/
TheNewOne11 said:
Ty for this information, but the best way for me would be to root without tripping knox. I just cant find clear informations :/
Click to expand...
Click to collapse
At this moment there is no clear information about this problem.
Pingpongroot method is for Android 5.0.2 and Samsung Galaxy S6 Edge devices. If our kernel is similar to Edge's kernel (has same vulnerability), so we can get root without tripping knox counter. Anyway, no news, no testers, not even kernel comparision.
There is another method avoiding knox - engineering bootloader. "Silver bullet" But not in our guns
5[Strogino] said:
At this moment there is no clear information about this problem.
Pingpongroot method is for Android 5.0.2 and Samsung Galaxy S6 Edge devices. If our kernel is similar to Edge's kernel (has same vulnerability), so we can get root without tripping knox counter. Anyway, no news, no testers, not even kernel comparision.
There is another method avoiding knox - engineering bootloader. "Silver bullet" But not in our guns
Click to expand...
Click to collapse
Hi Mate, ty for participating & for the good information you shared.
I'm very glad to find some other people with similiar wishes & needs.
The difference between you & me is that it seems that you got much more knowledge about this problem than me, and believe me, google is burning because of my searches xD.
I would be very glad if you could share new informations you get with me.
Of Course i will do the same and contact you if i find some.
TheNewOne11 said:
Hi Mate, ty for participating & for the good information you shared.
I'm very glad to find some other people with similiar wishes & needs.
The difference between you & me is that it seems that you got much more knowledge about this problem than me, and believe me, google is burning because of my searches xD.
I would be very glad if you could share new informations you get with me.
Of Course i will do the same and contact you if i find some.
Click to expand...
Click to collapse
Hi did you root with knox not tripped? Thanks
Hi everyone,
I'm getting really annoyed by Magisk on my phone.
I'm absolutely not able to make it work. No way it can pass safety net control.
If you need some other information, just ask!
Any help would be appreciated,
thanks in advance,
Lorenzo Benevento.
EDIT: I've just upgraded to the last LAOS build and now it doesn't pass also the basic integrity test!
Bump.
With V15.2 basic integrity works, but I can't pass the whole test!
Lorenzo Benevento said:
Bump.
With V15.2 basic integrity works, but I can't pass the whole test!
Click to expand...
Click to collapse
So in other words: MagiskHide is working on your device but Google doesn't recognise it as a certified device.
If you wan't to pass CTS as well, you're going to have to trick Google into thinking you have another device/ROM, probably by using the fingerprint from a stock ROM that is certified. There's some info on that in the troubleshooting guide (which I'm hoping to have some time to update in the next few days).
Okay, thank you for the infos! I will do some research an hopefully go through it.
Hi, unfortunately seems like there is no way of getting it to work, I also tried Universal Fix but it messed out everything.
I was discussing about it on discord and they said that looks like my device (Zuk Z1) is not fully supported (and it is plausible since is not this popular).
So, if I can help with the development (boot images, logcats, Magisk Log, trying, whatever), let me know who should I contact and how.
Thank you so much.
I'm having troubles with Magisk since V13, the first I tried...!
Lorenzo Benevento said:
Hi, unfortunately seems like there is no way of getting it to work, I also tried Universal Fix but it messed out everything.
I was discussing about it on discord and they said that looks like my device (Zuk Z1) is not fully supported (and it is plausible since is not this popular).
So, if I can help with the development (boot images, logcats, Magisk Log, trying, whatever), let me know who should I contact and how.
Thank you so much.
I'm having troubles with Magisk since V13, the first I tried...!
Click to expand...
Click to collapse
Well... Since you can pass basic integrity we know that MagiskHide is working. The Universal SafetyNet Fix module might not be your best option... Simply using a resetprop tool script to change ro.build.fingerprint, like mentioned in the guide I linked (under "Spoofing device fingerprint") might be enough.
Didgeridoohan said:
So in other words: MagiskHide is working on your device but Google doesn't recognise it as a certified device.
If you wan't to pass CTS as well, you're going to have to trick Google into thinking you have another device/ROM, probably by using the fingerprint from a stock ROM that is certified. There's some info on that in the troubleshooting guide (which I'm hoping to have some time to update in the next few days).
Click to expand...
Click to collapse
Didgeridoohan said:
Well... Since you can pass basic integrity we know that MagiskHide is working. The Universal SafetyNet Fix module might not be your best option... Simply using a resetprop tool script to change ro.build.fingerprint, like mentioned in the guide I linked (under "Spoofing device fingerprint") might be enough.
Click to expand...
Click to collapse
Okay, thank you, I have just a question before trying (and mark this thread as solved hopefully). Will this change in props affect LAOS OTAs?
Lorenzo Benevento said:
Okay, thank you, I have just a question before trying (and mark this thread as solved hopefully). Will this change in props affect LAOS OTAs?
Click to expand...
Click to collapse
Changing the fingerprint can cause your phone to be recognised for something it isn't, so it's perfectly possible that it can affect OTAs. It should just be a matter of disabling the script when you need to update.
I have no real world experience with it though... I've just once tested and confirmed that changing the fingerprint can help with passing SafetyNet on a non-certified ROM.
Okay, I'm going to try, the only problem is that I can't find the official fingerprint of my phone! Only outdated version, I think I should match at least Android version, isn't it?
Thank you so much for your quick and useful replies.
Didgeridoohan said:
Changing the fingerprint can cause your phone to be recognised for something it isn't, so it's perfectly possible that it can affect OTAs. It should just be a matter of disabling the script when you need to update.
I have no real world experience with it though... I've just once tested and confirmed that changing the fingerprint can help with passing SafetyNet on a non-certified ROM.
Click to expand...
Click to collapse
Okay, I'm going to try, the only problem is that I can't find the official fingerprint of my phone! Only outdated version, I think I should match at least Android version, isn't it?
Thank you so much for your quick and useful replies.
Lorenzo Benevento said:
Okay, I'm going to try, the only problem is that I can't find the official fingerprint of my phone! Only outdated version, I think I should match at least Android version, isn't it?
Thank you so much for your quick and useful replies.
Click to expand...
Click to collapse
Actually, when testing I used an official Nougat fingerprint for a custom Oreo ROM. If you can't get a hold of a more recent fingerprint, I'd recommend asking in your device's forum if anyone can provide one.
Thank you so much, I'll ask there.
Hello, dear forum users. Don't get it wrong, I'm new. Help is better than discuss! How to contact the developer Magisk? Root is malfunctioning on the J610fn (J6 +) phone. It gives a dip for software, but they in particular do not work, I was advised to ask for optimization for my phone!
Hi everyone!
I have a really difficult question, as you see above
Is root and custom rom good option?
Is there any alternative for samsung pass? Or is there any "hider" for KNOX status 0x1? Can magisk do that?
The benefits and downsides of rooting have already been thoroughly discussed on this forum. Use search next time!
Now, let's try to be helpful anyway. On to the first question: Why do you want to root? Is there anything specific you want out of your phone that you can't get without rooting?
I've just bought this phone, I have a SIM that does support WiFi calling and VoLTE (it's EE in UK), but I don't see the option anywhere. Similarly I don't see a VoLTE option. I've been everywhere in the menus, and it's just not there, or in the phone app.
Is there some magic code I can type in to force it on, like *#*#86583#*#* on a Xiaomi ?
Do either of these work OK for anyone ?
I have version 17.0922.2005.11
I found the answer, and if someone else is looking, Asus needs to add your carrier / country VOLTE/VOWIFI profiles to their firmware.
I guess I have to wait.
lordxenu said:
I found the answer, and if someone else is looking, Asus needs to add your carrier / country VOLTE/VOWIFI profiles to their firmware.
I guess I have to wait.
Click to expand...
Click to collapse
Your carrier/counrty COULD be in there already. Prop edits might be necessary. I posted a thread a few days ago, but deleted it, because the thread got spammed.
bs3pro said:
Your carrier/counrty COULD be in there already. Prop edits might be necessary. I posted a thread a few days ago, but deleted it, because the thread got spammed.
Click to expand...
Click to collapse
can we possibly convince you to share the info again ( read the thread, and yeah, seems people either are clueless or want everything 5G .. aparently they dont get the dofference between network limitations and phone limitations or something :/ ) just got the ROG3 yesterday, but living in a low coverage area, im more or less depending on VoWIFI most of the time, so would be great to have the phone actually working as intended instead of mostly handheld console XD ..
thank you
bs3pro said:
Your carrier/counrty COULD be in there already. Prop edits might be necessary. I posted a thread a few days ago, but deleted it, because the thread got spammed.
Click to expand...
Click to collapse
Please if you have a solution help us
@bs3pro
Can you share this information please? Do you need root? Mind PMing it to me if possible if anything..
bs3pro said:
Your carrier/counrty COULD be in there already. Prop edits might be necessary. I posted a thread a few days ago, but deleted it, because the thread got spammed.
Click to expand...
Click to collapse
Any chance you can share it here mate. It would be of great help to everyone. There are stupids everywhere, please donot hesitate to share the info because of those self entitled pricks.
Thanks mate.
bindassever said:
Any chance you can share it here mate. It would be of great help to everyone. There are stupids everywhere, please donot hesitate to share the info because of those self entitled pricks.
Thanks mate.
Click to expand...
Click to collapse
Hi Guys,
Just finished adding some hours ago all what is needed to enable it for my ROG 3 and my carrier.
[Guide] Enabling VoLTE/VoWiFi v2 | XDA Developers Forums
I have rooted the phone...
1) download the bootloader unlock from asus support webpage and unlock the bootloader (!!!this wipes your phone!!!)...just select the model and they give you the apk.
2) download twrp custom rom and flash it in fastboot (you need drivers and fasbtoot tool)
3) install magisk apk and use the app to download the proper zip that has to be flashed via custom recovery to enable root
4) having root enabled now you can use the guide above and activate diagnostics (I had to use the remote port option as it would not detect it via USB
5) based on the guide I also used the Xiaomi mi9 mbns (sort of config files for volte and vofi) using my carrier file.
Rebooted and all works now
PS: I had to enable magisk hiding mechanisms to make sure banking apps are working also.
While at this I also added some ad blocking capabilities now that I had to have root
PPS: here is a guide for rooting....(https://www.ytechb.com/how-to-install-xposed-framework-on-android-10/)
for custom recovery (https://dl.twrp.me/I003D/twrp-3.5.0_10-0-I003D.img.html)
With the new update to a12, here in USA a lot of users can make or receive any phone call. with the A11 not issues. Any idea how we can fix this issue ? My phone is not rooted.