Why do we have to root the phone before flashing recovery - Samsung Galaxy S10 Questions & Answers

*Read the title*
Why was this "feature" added?
Why do newer samsung phones progressively get harder to root?
I didnt root the phone and only unlocked OEM and flashed Recovery and I got "Only offiicialy released binaries are allowed to be flashed" -> how does this correlate with the rooting part

Because the recovery and flashing process require super user privileges and an unlocked bootloader at least. Normally it's possible to do this without rooting first, but it requires technical expertise, such as using CMD, fastboot and adb.
The reasons are the same as always, so they can control you and make you pay more for receiving less, the same as when the western countries were flunking in poverty, because they could never take enough from the poor.

Related

Stuck trying to get back to unlock/root

I got my phone back from repair and I'm confused ass to what to do next. I'm set to 'relocked' bootloader, but s-off without recovery or su apparently on 4.3. Every guide I find requires me to do something that causes things to come to as halt. Unless I'm doing something wrong I can't flash a recovery due to some error, then can't flash anything through recovery obviously, and I tried rumrunner but that stalls out after some point saying 'device is not rooted AND unsecure kernel'. What do I do next? Will HTCDev work? That's how I originally unlocked at release.
Really need help here, leaving the country for 3 weeks thursday morning and want to be back in business.
included pic of bootloader
yeah unlock again at htc dev then you will be able to flash a recovery
Or look here
[how to] lock/unlock your bootloader without htcdev(s-off required)
Thanks, had a feeling I needed to HTCDev again but didn't want to risk it given my limited time. Took some tinkering but looks like I'm unlocked and rooted again. Thanks BD.

[Q] XT1058 (AT&T) lollipop root

I haven't seen any root methods listed here for 5.0.
I'm still on 4.4 because I didn't want to lose system write or root. Has anyone been able to successfully root 5.0 with system write ability? What method did you use?
I've seen mentions of using Chain Fire but the articles are usually poorly written, so I don't trust them.
d3athsd00r said:
I haven't seen any root methods listed here for 5.0.
I'm still on 4.4 because I didn't want to lose system write or root. Has anyone been able to successfully root 5.0 with system write ability? What method did you use?
I've seen mentions of using Chain Fire but the articles are usually poorly written, so I don't trust them.
Click to expand...
Click to collapse
Twrp has the option to root.
When you reboot from it.
That's how I rooted twrp
I'm on AT&T, so my bootloader is still locked. Unless someone has figured out how to unlock without paying $25.
d3athsd00r said:
I'm on AT&T, so my bootloader is still locked. Unless someone has figured out how to unlock without paying $25.
Click to expand...
Click to collapse
If you have a locked bootloader you need someone to find a in the phone, or its software. Then a repeatable process must be created to use the exploit to gain root. i.e. Hack It.
Root is only part. There is also Write Protection to worry about.. When Write Protection is enabled (the phone's default state with locked bootloader, any changes made to /system, or the like, (including, but not limited to, App installs, file modifications, deletions, renames, etc) are not permanent and are lost at power off/on. Starting with 4.4.2, on a locked bootloader we can't disable write protection. No Vulnerabilities have been found/posted. However, Unlocking the bootloader disables write protection.
So if you have a locked bootloader, and want to root 5.02, you first need 5.02 to come out, then vulnerability found, tested, and a process created. When 5.1 comes out, it needs to be tested to see if the vulnerability was patched. if it was, the work starts all over again.. Its like playing "whack a mole." And even then you likely will have write protection enabled... so any power off/on or "hard boot" will mean lost changes to your phone.
Since the 2013 X is getting old, and only ATT, Verizon, and Republic wireless can't unlock their bootloader through Motorola's site, Paying $25 to use Sunshine if your phone is still on 4.4.2 or lower, is not a bad deal if you want to be sure you can root and disable write protection no matter what Android version comes to your phone.
NOTE: I am not affiliated with Sunshine... just trying to help you understand... Coming up with a root process for a LOCKED Bootloader isn't "quick and easy"
d3athsd00r said:
I'm on AT&T, so my bootloader is still locked. Unless someone has figured out how to unlock without paying $25.
Click to expand...
Click to collapse
That's literally the only way you are going to have root on lollipop. At least for a while anyways. I don't think many people would be interested in finding and creating exploits after this phone has already be exploited to the point where almost everyone can unlock their bootloader. I started at 4.4, went down to 4.2.2, used RockMyMoto and MotoWPnomo, then used SlapMyMoto when upgrading back to 4.4. After that I installed Safestrap and was able to use the stock (and rooted) ROMs by @Ctrl-Freak all the way up to 4.4.4. But after I heard about Sunshine... That was the holy grail. Unlocked my bootloader, flashed a clean install of stock 4.4 and just upgraded till 4.4.4 again, flashed TWRP, rooted, and that was it.
Thanks guys. I was always wary about Sunshine. Just never sat well with me, but I think I'm going to do it after I move into my new house since I have no plans to upgrade anytime soon.
d3athsd00r said:
Thanks guys. I was always wary about Sunshine. Just never sat well with me, but I think I'm going to do it after I move into my new house since I have no plans to upgrade anytime soon.
Click to expand...
Click to collapse
Its true, Sunshine is kind of risky... BUT because of those involved with it, I would consider it as safe as any "hack" can get.
If I didn't have a Dev Edition X, and needed to unlock my bootloader, I would not hesitate to use Sunshine.

Root without paying anything?

Is there a way to root this device without paying anything?
I've an unlocked verizon droid turbo(supports all sim cards )
Sent from my XT1254 using Tapatalk
No.
Nope.
If you're unlocked you should be able to flash supersu on twrp. Unlocking carries the fee not rooting. Correct me if I'm wrong I just got this phone. However I never paid to root it. I paid to unlock it and felt awkward for it afterwards. I never had to pay to unlock a phone. It's like one of those things I get told not to do because it's a scam. Lol.
xrock8 said:
Is there a way to root this device without paying anything?
I've an unlocked verizon droid turbo(supports all sim cards )
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Unless you used Sunshine, your phone is not unlocked. Your phone is SIM unlocked, not bootloader unlocked.
iiWoodstocK said:
Unless you used Sunshine, your phone is not unlocked. Your phone is SIM unlocked, not bootloader unlocked.
Click to expand...
Click to collapse
Yeah my bad
Thanks for correcting me !
I actually meant SIM unlocked.
Sent from my XT1254 using Tapatalk
xrock8 said:
Yeah my bad
Thanks for correcting me !
I actually meant SIM unlocked.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
There's no way of getting free permanent root. You could use Sunshine to get temp root, but that might not be too useful since the bootloader is still locked.
The only way to get permanent root is to unlock the bootloader by paying for Sunshine.
Temp root doesn't really allow permanent changes. The write protection is really really annoying. Twrp disables this write protection.
That is incorrect. You can root without sunshine, or TWRP. There is a debate as to the permanence. You can run Kingroot, then some scripts to swap Kingroot for SU, this will result in permanent persistent root without installing TWRP. The question is if Sunshine disabled the write protection or not. If you have not unlocked with Sunshine then by all means git it a try and let us know if it worked. I posted a thread about it a while back.
I'm not sure why people repeat that TWRP is needed for perm root but rest assured, it is absolutely 100% not.
HT123 said:
That is incorrect. You can root without sunshine, or TWRP. There is a debate as to the permanence. You can run Kingroot, then some scripts to swap Kingroot for SU, this will result in permanent persistent root without installing TWRP. The question is if Sunshine disabled the write protection or not. If you have not unlocked with Sunshine then by all means git it a try and let us know if it worked. I posted a thread about it a while back.
I'm not sure why people repeat that TWRP is needed for perm root but rest assured, it is absolutely 100% not.
Click to expand...
Click to collapse
You're half right. An unlocked bootloader is required for persistent root on the Droid Turbo. There's not really any debate about that. Technically, TWRP is not required. There are ways to get SuperSU on there without TWRP after the bootloader is unlocked (sunshine or kingroot temp root + flashify), but most people prefer to use TWRP since it's incredibly useful for the things that people with unlocked bootloaders usually want to do. Unlocking a bootloader without installing TWRP is like buying a Swiss army knife that doesn't have any knives in it. And yes, if you're determined enough, you can get SuperSU on there via Kingroot with a locked bootloader. But with a locked bootloader, doing so achieves nothing more than a super unstable system. Root's great and all, but it's not better than a phone that will actually turn on for more than 5 seconds before every app starts force closing.
EDIT: Nevermind. I think I misread what you were trying to say. Your post was assuming an unlocked bootloader. I missed that.
---------- Post added at 12:40 PM ---------- Previous post was at 12:30 PM ----------
s4shield said:
If you're unlocked you should be able to flash supersu on twrp. Unlocking carries the fee not rooting. Correct me if I'm wrong I just got this phone. However I never paid to root it. I paid to unlock it and felt awkward for it afterwards. I never had to pay to unlock a phone. It's like one of those things I get told not to do because it's a scam. Lol.
Click to expand...
Click to collapse
Sunshine is 100% not a scam. It is primarily maintained by two guys known as jcase and beaups. If you google either of their names, you'll find that they're associated with many, if not the majority, of the root/unlock exploits that have been released for just about every Android phone that has ever received one. The fee, which is incredibly fair, is necessary to partially recoup the thousands of dollars of their own money that they spend on test devices. Jcase is also a professional security researcher by day, and by releasing things like Sunshine, he forfeits sizable bug bounties that he would receive if he reported these bugs to Google or any given phone manufacturer. You don't get something that is more legit, or two guys that are more willing to make our communities possible, than Sunshine and the team behind it.
That was the question that I have yet to see proved with empirical evidence. Does sunshine turn off write protection so that SU will be persistent between reboots. As i have a said a few times, i assume it did, but since i installed SU after I ran sunshine i can not tell for sure. Again, the question was not about preference it was about the misinformation that TWRP is required for permanent root. I dont know why but that one bugs the [email protected] out of me. Again, if you haven't run sunshine yet I urge you to look for the other thread I posted on root without TWRP and try it for yourself. Worst that happens is it does not work.
I am going to put this out there, not because I know I am right but because I'd like it confirmed or refuted myself.
On the Turbo, kingroot or whatever root implementation is used by sunshine is only a temp root, meaning it does not survive a reboot. Kingroot may or may not leave some components on the /system partition but it does not keep the phone rooted, sometimes it can't even keep root while the phone is continuously running. Either way, unstable temp root is not very useful, but it allows sunshine bootloader unlock to work through an exploit.
At this point the write protection may or may not be disabled, I assume it is disabled and I know the sunshine devs could clear this up. For most the next step is flashing twrp, which provides the option to disable WP or not. It is unclear why this needs to be done, I imagine for some circumstance where twrp is flashed but the user wants to keep WP. So twrp is able to toggle WP, but it isn't doing anything too special to accomplish this. For us there is absolutely no reason to unlock the BL, flash twrp, then keep WP on and in fact it may render the phone unusable in this state.
So to get perm root, you need WP turned off. To get WP turned off, you need the BL unlocked. To get the BL unlocked, you need temp root.
Thus there is no free option, just pay these hard working devs for their huge personal investment in our device and appreciate the fact that someone got it done. Root is not easy anymore, and that is why it costs something now. Other high-end carrier locked-down phones will never get root because no one with enough skill and determination is working on them. Or there is simply no available exploit (or at least one that is feasible to use).
Sent from my XT1254 using Tapatalk
Again, this is the question that some seem baffled by.
Does running sunshine turn off the write protection to enable the swapping of kingroot for SU to be persistent through reboots.
As i have said, numerous time, TWRP is 100% not needed for ermanent persistent root. it just isn't, no matter how often the claim is repeated, it does not make it true. This is not a question about paying the devs or any other philosophical discussion on the merrits of TWRP vs stock recovery. It is a simple technical question of "Can you make root persistent without running sunshine"
HT123 said:
Again, this is the question that some seem baffled by.
"Can you make root persistent without running sunshine"
Click to expand...
Click to collapse
Disclaimer: I have no idea what I am talking about but I'd wager I am right.
Not without a new exploit.
To date the only exploit we have that allows write protection disabled is the one that allows an unlocked bootloader.
After that we have full access and then have our choice to use fastboot, adb or twrp.
If another dev/hacker were to look for an exploit I'm guessing they would again attack the bootloader.
This is a very logical starting place since a persistent root would most likely need two exploits. One to gain root, another to gain write access.
mrkhigh said:
Disclaimer: I have no idea what I am talking about but I'd wager I am right.
Not without a new exploit.
To date the only exploit we have that allows write protection disabled is the one that allows an unlocked bootloader.
After that we have full access and then have our choice to use fastboot, adb or twrp.
If another dev/hacker were to look for an exploit I'm guessing they would again attack the bootloader.
This is a very logical starting place since a persistent root would most likely need two exploits. One to gain root, another to gain write access.
Click to expand...
Click to collapse
For the Droid Turbo XT1224, yes TWRP is needed for a fully stable write protection disabled permanent root.
On other phones, no a custom recovery is not necessarily needed. For example, on my old Droid 4, I rooted the phone without installing a custom recovery. That root was permanent, and had write protection turned off.
TheSt33v said:
You're half right. An unlocked bootloader is required for persistent root on the Droid Turbo. There's not really any debate about that. Technically, TWRP is not required. There are ways to get SuperSU on there without TWRP after the bootloader is unlocked (sunshine or kingroot temp root + flashify), but most people prefer to use TWRP since it's incredibly useful for the things that people with unlocked bootloaders usually want to do. Unlocking a bootloader without installing TWRP is like buying a Swiss army knife that doesn't have any knives in it. And yes, if you're determined enough, you can get SuperSU on there via Kingroot with a locked bootloader. But with a locked bootloader, doing so achieves nothing more than a super unstable system. Root's great and all, but it's not better than a phone that will actually turn on for more than 5 seconds before every app starts force closing.
EDIT: Nevermind. I think I misread what you were trying to say. Your post was assuming an unlocked bootloader. I missed that.
---------- Post added at 12:40 PM ---------- Previous post was at 12:30 PM ----------
Sunshine is 100% not a scam. It is primarily maintained by two guys known as jcase and beaups. If you google either of their names, you'll find that they're associated with many, if not the majority, of the root/unlock exploits that have been released for just about every Android phone that has ever received one. The fee, which is incredibly fair, is necessary to partially recoup the thousands of dollars of their own money that they spend on test devices. Jcase is also a professional security researcher by day, and by releasing things like Sunshine, he forfeits sizable bug bounties that he would receive if he reported these bugs to Google or any given phone manufacturer. You don't get something that is more legit, or two guys that are more willing to make our communities possible, than Sunshine and the team behind it.
Click to expand...
Click to collapse
I know it's not a scam when I first used it kind of came off that. I wasn't used to the process and I know why they charge. Anytime I've seen anyone asking you for money to either unlock your bootloader or root your phone it has always been a scam till now. So that's why I saw it that way.

[Q] No OEM Unlock, Rooting, and stock ROM

I know that there are a lot of the missing OEM Unlock posts, but this isn't about how to force it to appear.
What I would like to know is that if I want to stay on the stock ROM, but I don't have the OEM unlocked option, would I be able to factory reset to clear out encryption and then root with Magisk?
The guide says that I need to have OEM unlocked to be able to root, so I'm curious what would happen if I tried to root with the OEM still being locked? Would I soft brick it?
This is quite different from the other phones I've used and it's extremely frustrating that Samsung decided to pull this kind of bs on everyone and so far, there's no solution to it.
Thanks
If the OEM switch is not visible and switched on, then you cannot flash any non-official binaries, which means you can't flash TWRP or Magisk, which at this point means you can't get root. That's why everything boils down to the OEM switch being enabled. Please contact Samsung expressing your dissatisfaction about this OEM issue. All of us should, until they react to remedy this.
If we can get to fastboot, why can't we boot TWRP, install Supersu/magisk and dm-verity thus gaining root.
This wouldn't replace the stock recovery.
I believe this was how the Axon 7 was rooted prior to bootloader unlock being presented/found.
I do this on one of my phones (not Samsung) as I only want root access and still be able to get OTA updates.
Would booting TWRP instead of flashing it trip Knox and would root be gained or would you find the boot partition or other system files be altered and you get the error that seems to popping up on these devices?
Just throwing this out there as food for thought.
ultramag69 said:
If we can get to fastboot, why can't we boot TWRP, install Supersu/magisk and dm-verity thus gaining root.
This wouldn't replace the stock recovery.
I believe this was how the Axon 7 was rooted prior to bootloader unlock being presented/found.
I do this on one of my phones (not Samsung) as I only want root access and still be able to get OTA updates.
Would booting TWRP instead of flashing it trip Knox and would root be gained or would you find the boot partition or other system files be altered and you get the error that seems to popping up on these devices?
Just throwing this out there as food for thought.
Click to expand...
Click to collapse
Having an unlocked bootloader is what would allow us to use fastboot to boot or flash an image. Just because we can access fastboot, doesn't mean we can get it to write to partitions, even temporarily. I haven't messed with a Samsung phone for years, so I could be wrong. This has been my experience with google bootloader in general.
fragtion said:
If the OEM switch is not visible and switched on, then you cannot flash any non-official binaries, which means you can't flash TWRP or Magisk, which at this point means you can't get root. That's why everything boils down to the OEM switch being enabled. Please contact Samsung expressing your dissatisfaction about this OEM issue. All of us should, until they react to remedy this.
Click to expand...
Click to collapse
From what I did read from other threads, if you don't see the option in the Developer Option Settings, then you shouldn't need to enable it
77Eric77 said:
From what I did read from other threads, if you don't see the option in the Developer Option Settings, then you shouldn't need to enable it
Click to expand...
Click to collapse
I was reading about this as well and what I got from that was in regards to custom roms, the oem unlock option is default to unlock and hidden. but for the stock rom, it's locked by default unless visibly given the option. otherwise when you go into download mode, it'll show FRP Lock: On.
Sent from my SM-G930F using Tapatalk
di11igaf said:
Having an unlocked bootloader is what would allow us to use fastboot to boot or flash an image. Just because we can access fastboot, doesn't mean we can get it to write to partitions, even temporarily. I haven't messed with a Samsung phone for years, so I could be wrong. This has been my experience with google bootloader in general.
Click to expand...
Click to collapse
Ah, but if I want to just root and nothing else, would I still need to have the bootloader unlocked? I'm used to rooting stuff but the technicalities and mechanics of the process escapes mr.
my hope is to atleast root the stock rom and factory reset including wiping the internal sd to start fresh. but if I factory reset on a stock rom, the internal storage would still be encrypted right?
Sent from my SM-G930F using Tapatalk
mputtr said:
Ah, but if I want to just root and nothing else, would I still need to have the bootloader unlocked? I'm used to rooting stuff but the technicalities and mechanics of the process escapes mr.
my hope is to atleast root the stock rom and factory reset including wiping the internal sd to start fresh. but if I factory reset on a stock rom, the internal storage would still be encrypted right?
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
This is why I want to know if we can boot TWRP. It boots TWRP but leaves the stock recovery.
However, I'm not sure if the boot image is altered when flashing root. I know Magisk seems to alter the boot image but not sure if SuperSU does.
Would this trigger KNOX?
If it does trip KNOX, it's not worth booting into TWRP, might as well just bite the bullet and install but only if bootloader is unlocked 1st... Too expensive to just brick it for an experiment...
ultramag69 said:
This is why I want to know if we can boot TWRP. It boots TWRP but leaves the stock recovery.
However, I'm not sure if the boot image is altered when flashing root. I know Magisk seems to alter the boot image but not sure if SuperSU does.
Would this trigger KNOX?
If it does trip KNOX, it's not worth booting into TWRP, might as well just bite the bullet and install but only if bootloader is unlocked 1st... Too expensive to just brick it for an experiment...
Click to expand...
Click to collapse
personally I don't care about knox. I just want to be able to root and restore my apps so I can transfer my stuff from my s7 to the note 8 and freeze all the bloatware like touchwiz and stuff.
from what I gleaned from reading the threads is magisk makes a copy of the boot image as a backup.
but again I just want root and I can wait for a longer term solution in how to fix this moronic 7 day jail bs.
but I think knox will get tripped the moment you root
Sent from my SM-G930F using Tapatalk
mputtr said:
I was reading about this as well and what I got from that was in regards to custom roms, the oem unlock option is default to unlock and hidden. but for the stock rom, it's locked by default unless visibly given the option. otherwise when you go into download mode, it'll show FRP Lock: On.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
I didn't have OEM option as well (FRP lock was ON), I just followed me2151 guide but I was getting the partition error, so in first part I also added BL and after that everything went smoothly.
KNOX wasn't tripped, it's rooted as of this moment and tomorrow I will be installing custom rom.
PS: And yes it was an experiment but I was willing to take the risk because after reading half a day about no OEM option in developer options everyone was saying if it's not there you don't need it, I wasn't 100% sure but I was 98% sure I'm not going to brick it. btw I'm using Telus N950W note8 (locked)
I think you might want to be careful on that. I'm not sure who "everyone" is but the others like Dr.Ketan did not even recommend rooting without unlocking the option first and it seems to me that the general gist of the other thread (the 150+ page thread) was that you need it explicitly unlocked.
The ones who talked about not seeing the option means you probably don't need it are talking about custom roms (like renovate) that purposefully hid the option since it's already defaulted to unlocked on that rom.
I haven't used any custom roms yet, but that seems to be what I'm reading.
77Eric77 said:
I didn't have OEM option as well (FRP lock was ON), I just followed me2151 guide but I was getting the partition error, so in first part I also added BL and after that everything went smoothly.
KNOX wasn't tripped, it's rooted as of this moment and tomorrow I will be installing custom rom.
PS: And yes it was an experiment but I was willing to take the risk because after reading half a day about no OEM option in developer options everyone was saying if it's not there you don't need it, I wasn't 100% sure but I was 98% sure I'm not going to brick it. btw I'm using Telus N950W note8 (locked)
Click to expand...
Click to collapse
just following up. Were you able to root and flash a custom rom with OEM Unlocked checked after all?
Sent from my SM-G930F using Tapatalk
mputtr said:
just following up. Were you able to root and flash a custom rom with OEM Unlocked checked after all?
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
I was able to root it but the boot loader is still locked. It's faster without the bloatware and what not. KNOX is disabled. There is still no twrp and custom rom for Snapdragon to the best of my knowledge. It did change the model of the phone from N950W to N950U1.
finally got the OEM Unlock option and rooted + stock recovery... i had to restart my phone to bring my android ID back to the one I always used.. and got locked out...
so 7 more days for me. And all I wanted to do was to have Titanium backup up and running so i can transfer my phone over....
i am hating what samsung has done

Any way to flash SuperSU without TWRP?

So far, every damned Cricket phone I've ever bought has either a crippled bootloader, or no bootloader at all. I recently bought the LG Harmony (M257) (Android 7.0) from Cricket Wireless after unsuccessfully trying to root and bricking a ZTE Grand X 3 (Z959) (Android 5.1.1) from losing charge while attempting a root. Either way, these phones seem to have little to no bootloader. If you prompt adb with "adb reboot bootloader" it just boots as normal, right into the OS.
My whole question here is, is it possible to flash SuperSU without TWRP or an unlocked bootloader? I am in dire need of rooting this device, as I'm getting overwhelmed with how little it can do as stock.
If there's a downloadable version of twrp that is "universal" somewhere, with a proper signature that can be adb side-loaded, or anything that can get me a team win custom recovery on a device with a crippled bootloader, please tell me about that too.
Thanks in advance to anyone that replies with helpful info!
iiPostMaster said:
So far, every damned Cricket phone I've ever bought has either a crippled bootloader, or no bootloader at all. I recently bought the LG Harmony (M257) (Android 7.0) from Cricket Wireless after unsuccessfully trying to root and bricking a ZTE Grand X 3 (Z959) (Android 5.1.1) from losing charge while attempting a root. Either way, these phones seem to have little to no bootloader. If you prompt adb with "adb reboot bootloader" it just boots as normal, right into the OS.
My whole question here is, is it possible to flash SuperSU without TWRP or an unlocked bootloader? I am in dire need of rooting this device, as I'm getting overwhelmed with how little it can do as stock.
If there's a downloadable version of twrp that is "universal" somewhere, with a proper signature that can be adb side-loaded, or anything that can get me a team win custom recovery on a device with a crippled bootloader, please tell me about that too.
Thanks in advance to anyone that replies with helpful info!
Click to expand...
Click to collapse
- it has a bootloader; just crippled (like most carrier supplied prepaid devices)
- no way to install Magisk, SuperSU or similar tool on an unrooted device with locked bootloader (if it were that easy ...)
Davey126 said:
- it has a bootloader; just crippled (like most carrier supplied prepaid devices)
- no way to install Magisk, SuperSU or similar tool on an unrooted device with locked bootloader (if it were that easy ...)
Click to expand...
Click to collapse
Well, it was worth a shot... Guess I might just have to resort to a few sketchy one-touch methods and use SuperSU Me.
iiPostMaster said:
Well, it was worth a shot... Guess I might just have to resort to a few sketchy one-touch methods and use SuperSU Me.
Click to expand...
Click to collapse
Good luck - no known (or at least reliable) root exploits for M257 which is a prerequisite for SuperSU me.

Categories

Resources