Related
This is the place to discuss anything and everything related to SuperSU and SafetyNet / Android Pay.
To clarify, I am not currently actively doing any development on having SuperSU pass SafetyNet detection, or having Android Pay work; the same way I put no effort into beating other root detection methods such as various enterprise security tools.
In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU.
While I may not agree with Google's stance, I'm not about to go messing with payment systems. Is it possible though? Probably yes.
This thread has been created because you guys simply cannot stop talking about this, so these posts can now go here, where I don't ever have to see them.
Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?
0.0 said:
Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?
Click to expand...
Click to collapse
Root is a no no with android pay and I think custom ROMs are also out at the moment
Sent from my A0001 using Tapatalk
Pure Drive GT said:
Hey, thanks for your continued support for root on Android, was just wondering, is google making it harder to achieve decent root privileges, as in they don't want rooted devices or are they just unrelatedly changing up things which forces you guys to adapt?
On another note, is there any progress on root without the modded boot? This is by no means an ETA, just wanted to know if you think it's possible or the situation looks rather dire.
Thanks again for your many efforts!
Click to expand...
Click to collapse
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Many banking and financial apps restrict access on rooted devices; it's not just Google.
It makes sense in some ways: root access allows running things in the background to either circumvent, monitor, or interrupt program transactions. They're being paranoid, and I don't blame them.
I don't like the Google Pay concept (or Apple's either); like every other encryption or security system, it's destined to eventually be hacked.
mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Yep, I was able to add my debit card but not credit.
VZW LG G4
mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/0...hy-android-pay-doesnt-support-rooted-devices/
shaggyskunk said:
Yet the Note 5 has been rooted for at least a couple of weeks
Click to expand...
Click to collapse
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.
Srandista said:
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.
Click to expand...
Click to collapse
I believe that it's only at&t and Verizon that locks the bootloader - And none in Canada and many other Countries.
Sent From my SM-N910W8 Running SlimRemix V5.1
Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.
NYZack said:
Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.
Click to expand...
Click to collapse
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.
Lrs121 said:
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.
Click to expand...
Click to collapse
I also found that having an unlocked bootloader will stop Pay working. When MM released I decided to go fully back to stock but kept the bootloader unlocked so I could flash MM. Pay still failed, so I've given up and gone rooted again.
Sent from my Nexus 6 using Tapatalk
Ch3vr0n said:
@Chainfire if you actually are able to pull off fully working stable root WITHOUT modifying the /system does that mean you MIGHT have opened the door into having root AND still being able to get OTA's?
Click to expand...
Click to collapse
osm0sis said:
Yup, all you'd need to do is reflash stock kernel to pass the boot partition EMMC check, or, we could automate restoring the previous stock kernel, flashing the OTA and then injecting the new stock kernel with root after flashing (à la AnyKernel2 or MultiROM). So many exciting possibilities there where custom recoveries are concerned.
Click to expand...
Click to collapse
Chainfire said:
Honestly it's not so different from using FlashFire to flash re-flash system, then OTA, then re-root. But it is easier, yes.
Click to expand...
Click to collapse
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Andrew Morykin 12:24
This should retain Android Pay, right?
Click to expand...
Click to collapse
Chainfire 12:58
+Andrew Morykin if it does, then it's by accident and not by design, and Android Pay will be updated to block it.
Click to expand...
Click to collapse
https://plus.google.com/+Chainfire/posts/aJbqUZ8PEP4
also, I was confused by this:
Chainfire said:
- I have not tested with encrypted devices
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63197935
Aren't
Nexus 6P / angler
angler-mdb08k-boot-systemless.zip
Click to expand...
Click to collapse
and
Nexus 5X / bullhead
bullhead-mdb08i-boot-systemless.zip
Click to expand...
Click to collapse
encrypted out of the box?
dabotsonline said:
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Click to expand...
Click to collapse
How is that a downside?
It's exactly the same with every other form of root you will ever see. They don't want to support Android Pay (and some other stuff) on rooted devices. If we find a root that allows it, they will update their system to detect and block it. That cat and mouse game will not end as long as Google doesn't want Android Pay on rooted devices.
Maybe someone will make apps/modules that help circumvent this, but it certainly will not be me.
also, I was confused by this:
Aren't
Nexus 6P / angler
and
Nexus 5X / bullhead
encrypted out of the box?
Click to expand...
Click to collapse
Still can't test what I don't have.
russlowe73 said:
Factory images
Click to expand...
Click to collapse
So basically I have to go back to 100% stock using ADB, and then flash the new SuperSU stuff with any custom ROM? If so, what are the benefits of this other than getting Android Pay while rooted?
I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of root on the Nexus 6!!
efrant said:
Starting with Android 5.0, OTA updates are now block-based rather than file-based, so any modification to the system partition will cause the OTA to fail, even mounting the system partition as r/w.
Click to expand...
Click to collapse
Just to add to this, it's a whole-partition /system patch OTA if the device launched with Lollipop or later, anything that launched with KitKat is still receiving the old file-based patch OTAs. Modifying Settings.apk would likely trip either method for a lot of OTAs though, since it's a pretty central component.
galaxyuserx said:
I use Galaxy s6 G9200 HK with Kernel compiled by me, but i have problem with root 5.1.1 and i think in future too 6.0
These root method is integrated in kernel source or i can integrate with those "boot.img systemless" my selfcompiled kernel?(repack boot.img with kernel compiled by me)
Is possible to work this new root method to android 5.1.1?
I have problem with gain root when i use kernel compiled by me ( STOCK kernel have too this problem BOOTLOOPs and FREEZEs on boot system) and i don't know how slove it :/
I found on chineese forums root integrated in boot.img it working good and isn't comunicat "KERNEL is not SEandroid enforced" but when i try integrate my kernel with this boot.img error with boot system :/
Click to expand...
Click to collapse
Yup, it's all ramdisk changes so should be workable on any version of Android. Chainfire left instructions outlining the ramdisk changes in the WIP thread if you want to give it a try.
phishfi said:
I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of on the Nexus 6!!
Click to expand...
Click to collapse
Yup, seems to be the case with most banking and root-detecting apps... for now.
Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.
secguy said:
Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.
Click to expand...
Click to collapse
Just ran it and it passed.
Went ahead and installed su on a stock nexus 5, so far working well, android pay does not work but that was me being stupid and changing the host file and dpi before setting it up
I do notice a little input lag after this, not enough to even make me consider removing root, but it is noticeable, anybody else with this?
Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.
xda123455 said:
Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.
Click to expand...
Click to collapse
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com
kal250 said:
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com
Click to expand...
Click to collapse
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/
xda123455 said:
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/
Click to expand...
Click to collapse
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??
kal250 said:
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??
Click to expand...
Click to collapse
I've tried Kingroot, Kingo Root and Frama root. All with no luck.
devanttrio said:
I've tried Kingroot, Kingo Root and Frama root. All with no luck.
Click to expand...
Click to collapse
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.
Autolounge said:
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.
Click to expand...
Click to collapse
I did.
I also tried the apps, of the ones that have apps.
devanttrio said:
I did.
I also tried the apps, of the ones that have apps.
Click to expand...
Click to collapse
You're going to have to do it manually.
no go on kingo
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
consider yourself blessed my friend, i'd like to root mine just to get marshmallow.... i have lollipop and checked for updates and says i'm up to date, i can only install 1 app at a time because there is no room on the internal storage, i have to move every app to sd card and then clean cache for each and every app i want.. never recommending blu to anyone
trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!
ray2jerry said:
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!
Click to expand...
Click to collapse
I found a option in developer settings that is "Enable OEM unlocking" and it makes it so you can unlock the bootloader from fastboot, if you do adb reboot-bootloader and then fastboot unlock it should undo the bootloader for you
zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.
CreativiTimothy said:
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.
Click to expand...
Click to collapse
I too am trying to root this device, and am unclear on a few of the steps here. I actually found your site with the recovery and boot images independently, really appreciated! I am at the point where I just need to patch the boot image, though I am not sure how to do this. If you could help me out with this step I might be able to put together some sort of list of steps to get through the whole process if you don't have the time.
Any help would be appreciated, thanks!
Hey im new to Samsung phones and got an S10+ preordered. Will I be able to flash TWRP and Magisk the day I get it or will it take some time? Also is there anything special about rooting Samsung phones?
Thank you for your answers!
I would not expect for immediately. Devs need to reverse engineer/hack their way around the firmware locks to attain root and keep the device bootable. Once they do that, the devices are ours. though I cannot imagine it would be too different from the 9 series with flash counters and such not.
Edit: Typos.
F0rbidN said:
Hey im new to Samsung phones and got an S10+ preordered. Will I be able to flash TWRP and Magisk the day I get it or will it take some time? Also is there anything special about rooting Samsung phones?
Thank you for your answers!
Click to expand...
Click to collapse
If it's the US snapdragon I highly doubt it but with exynos most likely and it will trip knox just like the Note 9.
Misterxtc said:
If it's the US snapdragon I highly doubt it but with exynos most likely and it will trip knox just like the Note 9.
Click to expand...
Click to collapse
I will get the exynos version. What are the disadvantages of triggering knox? Thank you for letting me know.
zerolock said:
I would not expect for immediately. Devs need to reverse engineer/hack their way around the firmware locks to attain root and keep the device bootable. Once they do that, the devices are ours. though I cannot imagine it would be too different from the 9 series with flash counters and such not.
Edit: Typos.
Click to expand...
Click to collapse
Will I have to do a factory reset in order to root my device?
F0rbidN said:
I will get the exynos version. What are the disadvantages of triggering knox? Thank you for letting me know.
Click to expand...
Click to collapse
You will loose Samsung Pay, secure folders and banking apps probably won't work. There is more but that's all that comes to mind right now. Uninstalling root and flashing everything to stock won't fix the lost apps either, it's permanent. I think it will reset your phone too.
Root
Banking apps will work once able to flash Magisk, simply using a system-less root method will allow for work arounds such as Magisk hide etc. which will definitely allow for such apps to work. Exactly as has been seen for the past few generations of devices using Magisk! Anyway... on another note, yes bootloader will very likely be unlockable on Exynos variants allowing for TWRP and custom rom installation but highly unlikely on Snapdragon variants.
Misterxtc said:
You will loose Samsung Pay, secure folders and banking apps probably won't work. There is more but that's all that comes to mind right now. Uninstalling root and flashing everything to stock won't fix the lost apps either, it's permanent. I think it will reset your phone too.
Click to expand...
Click to collapse
Are you sure about permanent block ?!
A0_o said:
Are you sure about permanent block ?!
Click to expand...
Click to collapse
Yes because the past root methods trip knox and blow a efuse witch is not reversible. Unless a different root method is discovered this phone will be no different. As the post says above there are some workarounds but that is not a guarantee. Some apps can not be fooled.
Misterxtc said:
Yes because the past root methods trip knox and blow a efuse witch is not reversible. Unless a different root method is discovered this phone will be no different. As the post says above there are some workarounds but that is not a guarantee. Some apps can not be fooled.
Click to expand...
Click to collapse
i have read about some way to root without trip kNox but you have to dont use magisk or xposed just you got an access to system files.
Wish SuperUser root XDA god 'Chainfire' hadn't retired!
A0_o said:
i have read about some way to root without trip kNox but you have to dont use magisk or xposed just you got an access to system files.
Click to expand...
Click to collapse
Are you talking about sig. spoofing like Firegapps and stuff?
I'm waiting for anyone who has enough guts to try, all I really want is v4a.
This is the last galaxy I buy I think, prolly go one plus next time. But yea this is a waiting game. I'm waiting for someone to bribe the dev's to prenstall v4a for us in an ota update. Hey be a great April fools joke ....heh
Is the Samsung Galaxy S20 FE 5G rootable?
yes it is, there are 2 or 3 threads where people go over the methods they followed
Just don't update it past rev 1 or 2. 1 to be safe.
How To Root Samsung Galaxy S20 FE (SM-G780F) & Install Magisk - NaldoTech
Follow the guide below to root your Samsung Galaxy S20 FE (Fan Edition) and install Magisk Manager. The developer behind Magisk, topjohnwu, released a Magisk
www.naldotech.com
bininga59 said:
How To Root Samsung Galaxy S20 FE (SM-G780F) & Install Magisk - NaldoTech
Follow the guide below to root your Samsung Galaxy S20 FE (Fan Edition) and install Magisk Manager. The developer behind Magisk, topjohnwu, released a Magisk
www.naldotech.com
Click to expand...
Click to collapse
Unfortunately that is for exynos. Not sure how many people need to know how to systemlessly root an exynos. Full root might be more useful for exynos users but good ol' snapdragon has everyone in a pickle (most everyone.)
Flucker08 said:
Unfortunately that is for exynos. Not sure how many people need to know how to systemlessly root an exynos. Full root might be more useful for exynos users but good ol' snapdragon has everyone in a pickle (most everyone.)
Click to expand...
Click to collapse
there's zero difference in how both models are rooted. systemless root has been the standard method for all androids for a long time now.
pinguluk said:
Is the Samsung Galaxy S20 FE 5G rootable?
Click to expand...
Click to collapse
Yeah almost every phone is rootable but it will either cost money or if you've updated your firmware then you'll have to wait until they figure out how to get past it, assuming they do, they always have just takes time. If you have updated your firmware you can look in to selling your device and buying one that hasn't been updated. I can give you more pointers on how to find phones that haven't been updated for cheap but that's only if your interested and no I'm not selling anything.
pinguluk said:
Is the Samsung Galaxy S20 FE 5G rootable?
Click to expand...
Click to collapse
Yeah almost every phone is rootable but it will either cost money or if you've updated your firmware then you'll have to wait until they figure out how to get past it, assuming they do, they always have just takes time. If you have updated your firmware you can look in to selling your device and buying one that hasn't been updated. I can give you more pointers on how to find phones that haven't been updated for cheap but that's only if your interested and no I'm not selling anything.
3mel said:
there's zero difference in how both models are rooted.
Click to expand...
Click to collapse
Oh really. So then why does snapdragon lock the bootloader while exynos doesn't? Not to mention a root that works on exynos won't necessarily work on snapdragon. I thought this was fairly well known.
What exactly are you referring to by model?
Flucker08 said:
Yeah almost every phone is rootable but it will either cost money or if you've updated your firmware then you'll have to wait until they figure out how to get past it, assuming they do, they always have just takes time. If you have updated your firmware you can look in to selling your device and buying one that hasn't been updated. I can give you more pointers on how to find phones that haven't been updated for cheap but that's only if your interested and no I'm not selling anything.
Oh really. So then why does snapdragon lock the bootloader while exynos doesn't? Not to mention a root that works on exynos won't necessarily work on snapdragon. I thought this was fairly well known.
What exactly are you referring to by model?
Click to expand...
Click to collapse
magisk doesn't have different versions for different devices and it's been the standard root method for a few years now. since version 22 how it works has changed for all new phones.
I'm on a snapdragon that didn't have a locked bootloader because that's only done in the US market (at the request of or to please US carriers I'm guessing). SM-G780 is a model number of the Exynos S20FE... SM-G781 is the Qualcomm, they both use the exact same method to obtain root.
3mel said:
there's zero difference in how both models are rooted. systemless root has been the standard method for all androids for a long time now.
Click to expand...
Click to collapse
I didn't see your other post. I'm not really in to getting in to these debates online not really my thing but I still use full root myself and systemless as well. They both have their pros and cons. I suppose I prefer to edit system files myself to overclock the device instead of depending on an app to do it for me.
There are lots of people still using full root. I think a long time in terms of electronics can be hard to pinpoint. I've used full root way more times than I've used systemless but I guess that's just because I've been doing it for a long time. I know some linux phones you can buy don't come with systemless root but only come with full root and they don't make systemless root phones off the shelf like they do full root for a reason. To each their own.
google and OEMs have made messing around with the system partition harder, it's read only now and overlays are how edits are mostly done. plus there are more apps that won't run if root is detected, systemless gives you the chance to evade that detection if you want it.
CF-autoroot is pretty much dead, the superSU app is owned by a private company and Chainfire had moved on.
have a read of this
Installation
The Magic Mask for Android
topjohnwu.github.io
this is rooting today, it's very different
3mel said:
google and OEMs have made messing around with the system partition harder, it's read only now and overlays are how edits are mostly done. plus there are more apps that won't run if root is detected, systemless gives you the chance to evade that detection if you want it.
CF-autoroot is pretty much dead, the superSU app is owned by a private company and Chainfire had moved on.
have a read of this
Installation
The Magic Mask for Android
topjohnwu.github.io
this is rooting today, it's very different
Click to expand...
Click to collapse
Oh thanks for the info. Yeah I've definitely used systemless. I did like it but of course there's nothing like doing it yourself. Although I rooted phones back in the day I've also used Magisk though I could've swore I was able to use vi and edit system files that would've been unreadable and definitely unwritable but I'm pretty sure I just changed the mount of whatever it was I was working on from ro to rw with 'mount -o remount,rw /' I'm to lazy to pull up Magisk I think I have it on a tablet somewhere. I probably also changed the file permissions with chmod or chown then chmod but I think there are some files you can't change using systemless now that I think about it hence the name systemless I dunno it's been awhile since I messed around with rooted phones.
After awhile you realize how vulnerable the device is after root and then when you think you can trust these apps that have root access then someone announces they found "_______" app pulling user information... I'm definitely not referring to any apps used anymore but it was the app people used before they used Magisk and it pretty much did the same thing but I wouldn't be surprised if newer root apps did the same.
Wait you said since SDK 22? Was systemless even around then? I don't think it was. I know it's been around for awhile but not that long.
I did find out something pretty funny when this guy was rooting people's phones and he had a contact in China... I was determined to find out who this Chinaman was. Well I don't think I should really say out of respect because he clearly didn't want people to know where he was from but yeah I guess I'll have to keep that to myself but it was pretty funny to say the least.
Also this was before rona so him being from wherever was irrelevant I just wanted to get it cheaper than what everyone else was paying. Turned out to be some old guy and unsurprisingly as you've assumed, not from China, or was he? He actually just unlocks phones and didn't acknowledge I even used the word root, he was thinking "oh no, they've found me."
@Flucker08 I meant since version22 of magisk not SDK22.
rooting with magisk used to be something you could do all from a custom recovery. now you have to download your firmware and patch it with magisk on your phone and then flash the patched image from PC
Hello
Please tell me, if i rooted Samsung s20 FE 5G ( Snapdragon ) can update new Firmware its Odin ? and not lost my all user data ? ( i hope to not must clear ) and rooted again ?
Please write, how to do it ?
after the first time rooting and unlocking the bootloader (so you could root) you wouldn't have to wipe again.
you would download the updated firmware, patch the AP file from your phone same as before and flash the downloaded firmware and patched AP all together in Odin @onken
if you select CSC_home for the CSC partition your user data will not be wiped !!
Hi
Ok, thanks for info @3mel
Please tell me yet, patch the AP i must prepare before flash new update firmware ?
onken said:
Hi
Ok, thanks for info @3mel
Please tell me yet, patch the AP i must prepare before flash new update firmware ?
Click to expand...
Click to collapse
yes, you download the update from somewhere. extract the AP file from the archive and copy to the phone. run magisk from the phone and wait till it's finished. copy the patched file back to your computer and use it along with the rest of the firmware files. again for CSC you MUST use the HOME_CSC file and not the regular CSC if you don't want the phone wiped.
that last part only applies when updating the phone, the first time you root you will have to wipe.
onken said:
Hi
Ok, thanks for info @3mel
Please tell me yet, patch the AP i must prepare before flash new update firmware ?
Click to expand...
Click to collapse
It is advised against updating after root. If you're on exynos I don't know but snapdragon it will make you lose root and no getting it back. It's said you can do it by removing the boot files from the firmware before flashing but I haven't tried just heard about it. Honestly you should just leave it. You aren't missing out on any amazing features. Most updates are security and if you're root you don't have much anyways.
All ok thanks for advice
3mel said:
yes, you download the update from somewhere. extract the AP file from the archive and copy to the phone. run magisk from the phone and wait till it's finished. copy the patched file back to your computer and use it along with the rest of the firmware files. again for CSC you MUST use the HOME_CSC file and not the regular CSC if you don't want the phone wiped.
that last part only applies when updating the phone, the first time you root you will have to wipe.
Click to expand...
Click to collapse
Hi @3mel
If I unlock, install twrp and root with magisk as per afaneh92's method, since I have twrp now, how much will the update method differ from what you mentioned here, if i don't want a wipe. If possible, can you please tell the steps in brief or provide a source? Sorry if this is not the right place for asking this.
I'm on SM-G781B/DS with OneUI 4.1(Android12).
Hey there,
So I need to know all the necessary steps to properly install Andronix and Termux (F-Droid) by unlocking the bootloader. Do you know where I can find all the information about that for Galaxy s10?
Depends on WHICH S10 you have. Snapdragon CPU versions cannot really be unlocked. Exynos can. This forum is full of threads on how to do the Exynos, of course... I have a Snapdragon so I haven't spent much time learning it...
Ok thanks I have a snapdragon also so I guess I will do something else
I hear you - I have Snapdragon too, so I gave up ROM and rooting on this phone. Honestly, I don't miss it. I used to ROM and root all my previous phones, but I don't see the need to do that anymore.
I want to ssh my network from my phone using a vpn to access my router so I can wake on lan my server
You should be able to do that without root from the phone - ssh doesn't require root to run, and it's just a secure terminal. You can get an app to do that (I see plenty on the play store). As for VPN, again, you don't need root on the phone to do that - I have used OVPN many times from my phone without issue (and without root).
schwinn8 said:
You should be able to do that without root from the phone - ssh doesn't require root to run, and it's just a secure terminal. You can get an app to do that (I see plenty on the play store). As for VPN, again, you don't need root on the phone to do that - I have used OVPN many times from my phone without issue (and without root).
Click to expand...
Click to collapse
Ok thanks
Why is everybody so convinced that rooting will only be possible with an unlocked bootloader? if there were to be a kernel exploit which would gain us access to the block devices i would say it's possible to downgrade the bootloader or anything which is accessible by block devices like the recovery partition. Am i missing something here?
DaanNL said:
Why is everybody so convinced that rooting will only be possible with an unlocked bootloader? if there were to be a kernel exploit which would gain us access to the block devices i would say it's possible to downgrade the bootloader or anything which is accessible by block devices like the recovery partition. Am i missing something here?
Click to expand...
Click to collapse
If you have a solution to root a galaxy s10 snapdragon cpu I will read your comments on it. But I think I believe that is because of the articles in the internet are only mentioning that I need to unlock the bootloader.
Indirectelex said:
If you have a solution to root a galaxy s10 snapdragon cpu I will read your comments on it. But I think I believe that is because of the articles in the internet are only mentioning that I need to unlock the bootloader.
Click to expand...
Click to collapse
Yes, everybody is so convinced that you need to unlock the bootloader and i wonder why.... we don't need odin to flash, afaik as we can find a kernel exploit which would gain us root access we could set properties to enable the oem unlock option.... making it available and usable could be a different case..... some requirements need to be met. If we could access block devices we should be able to install magisk and root the device.
Indirectelex said:
If you have a solution to root a galaxy s10 snapdragon cpu I will read your comments on it. But I think I believe that is because of the articles in the internet are only mentioning that I need to unlock the bootloader.
Click to expand...
Click to collapse
I think i'm getting somewhere, don't know for sure... at first i was only able to flash CSC and now i'm able to flash every slot.... do you have the same results in odin?
DaanNL said:
I think i'm getting somewhere, don't know for sure... at first i was only able to flash CSC and now i'm able to flash every slot.... do you have the same results in odin?
Click to expand...
Click to collapse
I cant do tests on my galaxy s10 but I will on a Moto z2
we are so ****ed with the cellphones
Yeah, I need one too! I got a Galaxy S10 Plus Snapdragon. It's it's been 2 years since I have it and I can't find nobody that can teach me how to root it!!!
Because it cannot be rooted. US carriers have made that happen, and the manufacturers have had to keep doing it.
Many have tried, and on older BLs it can be done, but once you update you are stuck on a newer BL and cannot downgrade. If you root with the older BL, you cannot upgrade the BL either, because that will relock it.
If someone comes up with a way to do it, I'm all ears, as are many others... but with higher level crypto being implemented for this protection (ie, you need to know the crypto key!), it likely won't happen.
I have an idea but i don't know if it's possible, i tried but it seems corepatch isn't working.
I see a lot of topics about what's needed to unlock the bootloader, but if i look in the source code what is required to unlock the bootloader there's a lot of ro. properties which we can't set because we are not root.
As LSPatch can now communicate with Shizuku and gain system level access we might be able to disable system app verification (platform certificate, by extending CorePatch or maybe someone can write a signature verification disabler for lsposed). Then create an app which doesn't check for all these properties and initiates an OEM unlock and install it as system user./