I am currently Rooted, unlocked bootloader, running a 5.0.2 ROM and TWRP. If I just wanted to unroot, lock boot loader and star from scratch. Meaning, accept OTA, unlock bootloader, root and install TWRP. Is this possible?
Yes.
If you want to make it easy
http://forum.xda-developers.com/showthread.php?t=2947452
Sent from my Nexus 6
Xirix12 said:
I am currently Rooted, unlocked bootloader, running a 5.0.2 ROM and TWRP. If I just wanted to unroot, lock boot loader and star from scratch. Meaning, accept OTA, unlock bootloader, root and install TWRP. Is this possible?
Click to expand...
Click to collapse
I wouldn't re-lock these devices ever... maybe if you sell it or turn it in. Too risky. Just use Wugs from that link, once 5.1 is there, flash it using his toolkit. Then root. Done.
I can't believe the amount of threads here and in the Nexus 9 board where guys are bricking their devices due to that darn "OEM unlock" being unchecked.
Hi all,
I am currently OTA updated to 5.1.1 OJ3 and as I understand there is not a way to unlock the boot loader without affecting the warranty counter.
This begs a question. Say I am out of warranty and DONT CARE if my counter shows a modified boot loader. Is there a way to flash an unlocked boot loader and root the device?
Fill me in.
Previously I used to root all my phones but I missed the opportunity on this one back at 4.4
shenweas said:
Hi all,
I am currently OTA updated to 5.1.1 OJ3 and as I understand there is not a way to unlock the boot loader without affecting the warranty counter.
This begs a question. Say I am out of warranty and DONT CARE if my counter shows a modified boot loader. Is there a way to flash an unlocked boot loader and root the device?
Fill me in.
Previously I used to root all my phones but I missed the opportunity on this one back at 4.4
Click to expand...
Click to collapse
No way to unlock bootloader, currently no way to root 5.1.1
i would have though that since verizon has allowed unlocking of the BL on their S5's i figured at&t would have followed suit.
darthmalus said:
i would have though that since verizon has allowed unlocking of the BL on their S5's i figured at&t would have followed suit.
Click to expand...
Click to collapse
Um no they haven't!
Sent from my SAMSUNG-SM-G900A using Tapatalk
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
I Bought a 2nd hand one plus 3t...!! and when i reboot it says dm -verity not enabled in enforcing
Does this mean the phone was rooted?
The bootloader was/is unlocked. It's not possible to say if the previous owner rooted the phone, but he did unlock the bootloader, and that's all you can say from the DM-Verity error.
99% it was rooted.
Why else to unlock the bootloader?
Unleashed by my rooted OP3T in 8.0
RASTAVIPER said:
99% it was rooted.
Why else to unlock the bootloader?
Unleashed by my rooted OP3T in 8.0
Click to expand...
Click to collapse
Well not always. Some users unlock bootloaders and to flash Custom ROMs that have more customization features, and they don't root it.
ak_bagade said:
I Bought a 2nd hand one plus 3t...!! and when i reboot it says dm -verity not enabled in enforcing
Does this mean the phone was rooted?
Click to expand...
Click to collapse
Was either rooted, still is rooted, or at least other related modifications as discussed above (unlocked bootloader, custom recovery, etc.).
Do you get the bootloader unlocked warning on boot also?
As for the implications this has for you, it depends on what state you want the phone (root, custom recovery, etc.). It's easy to put the phone back to full stock, if you want that.
ak_bagade said:
I Bought a 2nd hand one plus 3t...!! and when i reboot it says dm -verity not enabled in enforcing
Does this mean the phone was rooted?
Click to expand...
Click to collapse
First off, don't freak out. You can easily return the phone to stock if you like. Unlocking the bootloader, rooting, etc., is NOT nefarious. In large part, that's why XDA exists. You can remove the dm-verity warning with the OnePlus 3/3t unified toolkit or just return the device to stock.
Personally, if the phone is already unlocked and running TWRP, I'd just flash a ROM since OnePlus is orphaning the device now that we're on Oreo. You'll be better off.
I unlocked my bootloader just before the pie update s. I noticed my bank NFC pay stopped working around this time. At this time I don't really need the bootloader unlocked. Is there any harm relocking my bootloader? or possible bricking? If I leave it unlocked how can I hide my unlocked bootloader by rooting ?
bigshowjh said:
I unlocked my bootloader just before the pie update s. I noticed my bank NFC pay stopped working around this time. At this time I don't really need the bootloader unlocked. Is there any harm relocking my bootloader? or possible bricking? If I leave it unlocked how can I hide my unlocked bootloader by rooting ?
Click to expand...
Click to collapse
This is pretty bad if your bank app thinks that phone is 'rooted' just because BL was unlocked.
If you didn't do anything else (Recovery, eRecovery, Ramdisk, Kernel are still stock), you can relock BL, no harm, it will just Factory reset once again (prepare back-ups)
AFAIK, installing Magisk does not hide from apps that BL was unlocked
zgfg said:
This is pretty bad if your bank app thinks that phone is 'rooted' just because BL was unlocked.
If you didn't do anything else (Recovery, eRecovery, Ramdisk, Kernel are still stock), you can relock BL, no harm, it will just Factory reset once again (prepare back-ups)
AFAIK, installing Magisk does not hide from apps that BL was unlocked
Click to expand...
Click to collapse
Thank you for your response. All are still stock. I just unlocked it a while ago to remove emergency broadcast but did it through ADB instead. No need at this time to be unlocked. Thanks again.