Related
Due to organizational requirements the bootloader needs to be locked. So, here go the questions:
After flashing factory image (5.1.0 (LMY47E), is it safe to re-lock bootloader?
And when, after the final reboot and before setup?
And, will the command, fastboot oem lock, wipe EVERYTHING off the phone, like fastboot oem unlock does?
And does the Developer options setting, "OEM unlocking", need to be turned on prior to the lock?
Thanks
No one has proven that locking the bootloaders does not cause a "brick". We have seen people lock after 5.1 and get a bootloop. This becomes a brick because they cannot unlock to fix it. We don't know if the update causes the loop or the lock does.
By the way, this was a completely stock Nexus 6 (5.0.1), no root, no apps other than Google. Before the factory image flash, the "OEM Unlocking" setting in Developer Options was persistent during power on/off. Now, with 5.1 the setting turns itself off during power on/off.
So, should I re-lock the bootloader and satisfy organizational requirements and risk a boot loop or proceed unlocked? Kinda feel like a "deer in the headlights" !
clairez said:
By the way, this was a completely stock Nexus 6 (5.0.1), no root, no apps other than Google. Before the factory image flash, the "OEM Unlocking" setting in Developer Options was persistent during power on/off. Now, with 5.1 the setting turns itself off during power on/off.
So, should I re-lock the bootloader and satisfy organizational requirements and risk a boot loop or proceed unlocked? Kinda feel like a "deer in the headlights" !
Click to expand...
Click to collapse
Well its your choice. I recommend not locking it. However, if you do lock it and end up bricked, at least we know its the locking that causes the loop and not the flash but.... Is it worth it?
If your organization is supplying the device ( or the money for the device) you have no business unlocking it. At my organization people are fired for such things.
If they are not compensating you somehow then I don't see how they can make requirements on your device.
Sent from my Nexus 6
And if it is the unlocking/locking that causes the boot loop (hard brick) then any flashing operation that requires unlocking the bootloader will require that the system remain unlocked forever. A penalty that will afflict a portion (large?) of the Nexus 6 community. Was this an issue before 5.0? Makes one wonder if this is by design or accidental.
DebianDog said:
If they are not compensating you somehow then I don't see how they can make requirements on your device.
Click to expand...
Click to collapse
Yes we totally can. If you work for my company and decide you would rather use your own device for corporate email and data, that data is ours. You may use your own device but we will manage it. If it gets stolen, we will wipe it. You will adhere the same policies for corporate owned data as you will with a phone supplied by us. You will have lock screen, you will be unrooted. You will keep your bootloaders locked. Or you can use this sh*tty Nokia.
My hardware, but if I want to utilize it in the organization, then I must abide by their rules.
This post was not meant to be an organizational ethics discussion, just a request for guidance. If anyone can give me input on the original questions, I would greatly appreciate it. Especially the wipe side effect of the lock operation. Do not want to spend a lot of time configuring the device if it will be erased.
Thanks in advance
clairez said:
My hardware, but if I want to utilize it in the organization, then I must abide by their rules.
Click to expand...
Click to collapse
Yep. Absolutely.
rootSU said:
No one has proven that locking the bootloaders does not cause a "brick". We have seen people lock after 5.1 and get a bootloop. This becomes a brick because they cannot unlock to fix it. We don't know if the update causes the loop or the lock does.
Click to expand...
Click to collapse
Just a little thinking out loud here. Wouldn't it be safe to have OEM Unlock checked under dev options, lock the bootloader, if you happen to bootloop OEM Unlock is still checked so you could still unlock? And then upon first boot OEM Unlock would get unchecked.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
Just a little thinking out loud here. Wouldn't it be safe to have OEM Unlock checked under dev options, lock the bootloader, if you happen to bootloop OEM Unlock is still checked so you could still unlock? And then upon first boot OEM Unlock would get unchecked.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Safe? No.. The flag resets at boot. Boot loop partially boots and it could be enough to reset the flag "at first boot"
Pretty much everything is an unknown here. We do t even know where the "enable OEM unlock" flag is set. Is it in the BL or one of the various partitions? What effect would setting the flag and wiping the OS have? We just don't know.
rootSU said:
Safe? No.. The flag resets at boot. Boot loop partially boots and it could be enough to reset the flag "at first boot"
Pretty much everything is an unknown here. We do t even know where the "enable OEM unlock" flag is set. Is it in the BL or one of the various partitions? What effect would setting the flag and wiping the OS have? We just don't know.
Click to expand...
Click to collapse
Good point. That's why more heads are better than one. I still think my theory would work, but yet I wouldn't be willing to risk my N6 on it, wouldn't suggest others do either.
Sent from my Nexus 6 using XDA Free mobile app
clairez said:
Due to organizational requirements the bootloader needs to be locked. So, here go the questions:
After flashing factory image (5.1.0 (LMY47E), is it safe to re-lock bootloader?
And when, after the final reboot and before setup?
And, will the command, fastboot oem lock, wipe EVERYTHING off the phone, like fastboot oem unlock does?
And does the Developer options setting, "OEM unlocking", need to be turned on prior to the lock?
Thanks
Click to expand...
Click to collapse
1. Unsure at this point. If everything is stock (including recovery), I would suspect that it would be OK, but it has not been verified yet.
2. After you flash the bootloader, radio, boot, system and recovery images, and format data and cache, then would be the time to re-lock and then boot into Android.
3. Yes. But based on what I gather, the process of wiping on an N6 (when unlocking or locking the bootloader) is done via the stock recovery. So, if you have a custom recovery when you lock, I suspect that it will give you a boot loop.
4. I don't know.
Update - Success
I re-locked the bootloader and the device is working normally, no boot loop. I will continue testing over the next few days and then share what I learned.
Thanks for the help ...
Upgraded to 5.1, booted system OK
rechecked the OEM unlock option and rebooted to fastboot and locked bootloader.
No bootloop or other issues noticed.
Hope this helps.
clairez said:
I re-locked the bootloader and the device is working normally, no boot loop. I will continue testing over the next few days and then share what I learned.
Thanks for the help ...
Click to expand...
Click to collapse
Interesting. And you were 100% stock?
Perhaps the loop isn't caused by the lock itself then. Good to know, though still people need to be cautious
androiduser2011 said:
Upgraded to 5.1, booted system OK
rechecked the OEM unlock option and rebooted to fastboot and locked bootloader.
No bootloop or other issues noticed.
Hope this helps.
Click to expand...
Click to collapse
A few question, for understanding:
Rooted?
Stock or TWRP recovery?
Encrypted?
Thanks
rootSU said:
No one has proven that locking the bootloaders does not cause a "brick". We have seen people lock after 5.1 and get a bootloop. This becomes a brick because they cannot unlock to fix it. We don't know if the update causes the loop or the lock does.
Click to expand...
Click to collapse
This happened to me literally tonight. I tried to lock the boot loader which was successful, from there the device would start to root into teamwin recovery. So from there I tired to flash a fully stock rom but the bootloader was locked. And then because you need permission from the OS to unlock the bootloader I was stuck. What I did is from the locked bootloader I ran the stock oem flash from a fresh download and check from wugs with the force flash enabled (make sure everything is right) miracles of miracles it worked and came back to me.
I learned my lesson. Never shall my bootloader be relocked unless my phone is out of my possession. I'm spending the rest of the time making sure that nobody can get to my data. I love the phone, but that data is my life.
So basically, we need to confirm that being 100% stock will safely allow the relocking of the bootloader on 5.1 per official instructions from Google. If it can be determined that having TWRP recovery installed is the cause of bricks then users can be instructed to be sure stock recovery is installed before relocking. My own thoughts are that this is a bug of sorts with the new security features of lollipop and I'm sure the talented folks here will get it figured out. I'm 100% stock on LMY47D that I sideloaded. Not sure I can afford to risk my 6 but I offer any assistance I can to help get this figured out.
Evolution_Freak said:
So basically, we need to confirm that being 100% stock will safely allow the relocking of the bootloader on 5.1
Click to expand...
Click to collapse
Some of the "bricks" happened after fully flashing stock, i.e they had stock recovery. They had a locked bootloader, an OS that didn't boot and a recovery that couldn't flash anything. If they had TWRP installed, they could format data and flash a rom.zip no problem.
I looked on Cyanogenmod's website below:
https://download.cyanogenmod.org/?device=shamu
and it just has 1 ROM for Nexus 6. I have Nexus 6 for Sprint. Is there only 1 version of the ROM that works for all carriers ?
My old Galaxy S4 has many different builds for Sprint, ATT, Verizon, etc.... wasn't sure if Nexus has the same set up.
Yes, applies to all N6 variants.
thats because every sgs4 has a different setup for different carriers. we only have one nexus 6, and its the same for every carrier.
simms22 said:
thats because every sgs4 has a different setup for different carriers. we only have one nexus 6, and its the same for every carrier.
Click to expand...
Click to collapse
I didn't have a locked bootloader with Sprint Galaxy S4. If I were to restore the Nexus 6 back to stock to do an OTA update to update everything, then re-root and put a new custom ROM does the bootloader need to be re-locked, or can the factory .img be suffice to do an OTA ?
I'm still trying to learn how to do this as it is much different than the Samsung GS4. I saw there is a Nexus Toolkit by wug fresh. Is there any benefit to doing these processes by adb vs just using this progra which seems easier ?
mikeprius said:
I didn't have a locked bootloader with Sprint Galaxy S4. If I were to restore the Nexus 6 back to stock to do an OTA update to update everything, then re-root and put a new custom ROM does the bootloader need to be re-locked, or can the factory .img be suffice to do an OTA ?
I'm still trying to learn how to do this as it is much different than the Samsung GS4. I saw there is a Nexus Toolkit by wug fresh. Is there any benefit to doing these processes by adb vs just using this progra which seems easier ?
Click to expand...
Click to collapse
you dont use adb for it, you use fastboot. and doung it right vs a toolkit.. toolkits dont teach you anything, and can mess things up.
simms22 said:
you dont use adb for it, you use fastboot. and doung it right vs a toolkit.. toolkits dont teach you anything, and can mess things up.
Click to expand...
Click to collapse
Does the bootloader need to be locked to do OTAs or does the stock ROM with leaving the bootloader unlock suffice for an OTA ?
mikeprius said:
Does the bootloader need to be locked to do OTAs or does the stock ROM with leaving the bootloader unlock suffice for an OTA ?
Click to expand...
Click to collapse
bootloader can be locked or unlocked, it doesnt matter. but i recommend that you keep it unlocked forever, as it can save your phone in certain situations. and having it locked can be the end of your device, in the same situations.
simms22 said:
bootloader can be locked or unlocked, it doesnt matter. but i recommend that you keep it unlocked forever, as it can save your phone in certain situations. and having it locked can be the end of your device, in the same situations.
Click to expand...
Click to collapse
Ok. That's what I was planning on doing once it becomes unlocked. I was going to have it set like my previous GS4 and just toggle custom ROMs from there. When you mention having it locked, are you referring to when people have re-locked the bootloader then had an error flashing the stock custom ROM thus bricking the phone ? That's what worries me. Looks like the security is more stringent on the new Nexus vs. older versions.
mikeprius said:
Ok. That's what I was planning on doing once it becomes unlocked. I was going to have it set like my previous GS4 and just toggle custom ROMs from there. When you mention having it locked, are you referring to when people have re-locked the bootloader then had an error flashing the stock custom ROM thus bricking the phone ? That's what worries me. Looks like the security is more stringent on the new Nexus vs. older versions.
Click to expand...
Click to collapse
i was actually refering to it because of the unlock setting that has to be ticked to unlock. some stock users got caught in a bootloop, then cant boot up to tick the setting, to fix their bootloop. since it cant get unlocked, their phones are a "brick".
simms22 said:
i was actually refering to it because of the unlock setting that has to be ticked to unlock. some stock users got caught in a bootloop, then cant boot up to tick the setting, to fix their bootloop. since it cant get unlocked, their phones are a "brick".
Click to expand...
Click to collapse
Is this what happened to this person below ?:
http://forum.xda-developers.com/nexus-6/help/help-nexus-6-brick-t3227126
Since the stock rom did not have developer options "checked" then the bootloader can't be unlocked ? How can you tick the OEM unlock if it is in a bootloop ?
mikeprius said:
Is this what happened to this person below ?:
http://forum.xda-developers.com/nexus-6/help/help-nexus-6-brick-t3227126
Since the stock rom did not have developer options "checked" then the bootloader can't be unlocked ? How can you tick the OEM unlock if it is in a bootloop ?
Click to expand...
Click to collapse
you cant, thats why i said that you should keep it unlocked.
simms22 said:
you cant, thats why i said that you should keep it unlocked.
Click to expand...
Click to collapse
Ok that makes sense. What is the purpose of having the bootloader come locked in a stock phone then ? What does it actually do ? Prevents root ? I probably took it for granted mine was always unlocked before so all I had to do was worry about flashing the proper carrier ROM
mikeprius said:
Ok that makes sense. What is the purpose of having the bootloader come locked in a stock phone then ? What does it actually do ? Prevents root ? I probably took it for granted mine was always unlocked before so all I had to do was worry about flashing the proper carrier ROM
Click to expand...
Click to collapse
Security.
Security in that if stolen your phone cannot be made to work for someone else...
Someone can (and likely will [emoji14]) correct me if I am wrong... But does little to secure your data...ESPECIALLY if you stay encrypted.
scryan said:
Security in that if stolen your phone cannot be made to work for someone else...
Someone can (and likely will [emoji14]) correct me if I am wrong... But does little to secure your data...ESPECIALLY if you stay encrypted.
Click to expand...
Click to collapse
It does nothing to secure data from remote access, but it will protect data (if set with a password) from physical access, providing they do not know the password. The bootloader being unlocked, with no password on encryption would allow them to flash a custom recovery and pull the data off. This will be decrypted on the fly. So it works in conjunction with Encryption. To secure data from physical access, you need both.
IF your bootloader is unlocked and you have no password, you may aswell not be encrypted
Does anyone know if there is a zip that is recovery flashable which can lock and relock the bootloader through recovery? I guess what I'm wondering about is there is a Aroma zip HTC users use called Guru which can lock and unlock the bootloader without a the need for a PC. If no big deal....
tapPeD fROM my neXus 6
probably possible, but its a god damn horrible idea to re-lock the bootloader once you have made ANY modifications to the phone.... We get enough "Phone wont boot for me to switch on "Allow OEM Unlock and bootloader is locked" threads.
The only thing relocking your phone does is prevent a thief from wiping it so they can use it. At that point your phone is stolen anyways, you really want to limit your ability to fix it should you have problems just to stop someone else from using the phone once you no longer have it in the first place?
I guess the only reason why I was asking is because I'm assuming you cannot use Android Pay while the bootloader is unlocked. Is that true or no? Otherwise, I completely agree.
tapPeD fROM my neXus 6
well, if you need a zip to unlock your bootloader via recovery, then itll never exist, as you need to unlock your bootloader before flashing a recovery.
andrewjt19 said:
I guess the only reason why I was asking is because I'm assuming you cannot use Android Pay while the bootloader is unlocked. Is that true or no? Otherwise, I completely agree.
tapPeD fROM my neXus 6
Click to expand...
Click to collapse
you can use android pay with an unlocked bootloader. In fact the only thing that prevents android pay from working is root access or core system file modification (xposed level).
I've currently got the viper/dolby atmos mod installed (adds apps to /system), docs sheets and slides uninstalled from system(deletes things from system) , elementalx (doesn't mod system) and cataclysm installed (mods system.. lightly I guess?) and android pay still works if you disable root.
Also you can use this app to test if android pay will work adding mods 1 by 1 without having to go through the card adding and pay testing. If it shows green android pay should work.
andrewjt19 said:
I guess the only reason why I was asking is because I'm assuming you cannot use Android Pay while the bootloader is unlocked. Is that true or no? Otherwise, I completely agree.
tapPeD fROM my neXus 6
Click to expand...
Click to collapse
No. Android Pay is based off your ROM not the bootloader. I flashed my phone back to stock with a unlocked bootloader and it worked (well it would have but my bank is not participating in it yet). You can also do OTA updates on a stock ROM with an unlocked bootloader.
I know that this has been said before but I agree with it, there's no point in re-locking your bootloader unless you have to send it back in or are turning it back to 100% stock. Just causes more problems than it's worth.
Hi,
I've searched and found how to do it but it was for Android 5.1 but I'm on 7.0 and I my recovery is TWRP 3.0.2-0 and apparently there are more steps to do if you are on TWRP, I'm wondering what are they.
Thanks
test84 said:
Hi,
I've searched and found how to do it but it was for Android 5.1 but I'm on 7.0 and I my recovery is TWRP 3.0.2-0 and apparently there are more steps to do if you are on TWRP, I'm wondering what are they.
Thanks
Click to expand...
Click to collapse
First, questions need to go in the Nexus 6 Q&A, Help & Troubleshooting Thread, not the General thread. Second, the steps to lock the bootloader have not changed. It's done from the bootloader with fastboot and the command "fastboot oem lock". It shouldn't matter what recovery you have.
Re-locking needs stock recovery(maybe full stock; boot, recovery, system) if you try to re-lock your boot loader without stock recovery you might hardbrick your phone. So just backup your apps and files, flash a stock image from google and re-lock your boot loader with "fastboot oem lock". Which probably needs wiping your phone.
Before you do anything search these forums for the many people who locked their bootloader and then when they had problems ended up with a bricked and useless device. Unless you have a very special reason for locking, leave it unlocked
dahawthorne said:
Before you do anything search these forums for the many people who locked their bootloader and then when they had problems ended up with a bricked and useless device. Unless you have a very special reason for locking, leave it unlocked
Click to expand...
Click to collapse
this right here...there is really no reason to ever re lock your bootloader
I flashed the factory image and and it went fine. But the bootloader is still unlocked. My main concern for locking the bootloader is to prevent any malicious app to root the phone and hide themselves by like installing as system app or something. And I'm not planning to flash any custom ROM. So:
1- Since I'm on stock ROM, is there still a possibility of hard bricking my phone if I relock?
2- If I leave it unlocked, will malwares be able to tamper with the phone by the means I mentioned or similar approaches?
Thanks
2. No, they don't. Bootloader is on a completly different layer.
test84 said:
I flashed the factory image and and it went fine. But the bootloader is still unlocked. My main concern for locking the bootloader is to prevent any malicious app to root the phone and hide themselves by like installing as system app or something. And I'm not planning to flash any custom ROM. So:
1- Since I'm on stock ROM, is there still a possibility of hard bricking my phone if I relock?
2- If I leave it unlocked, will malwares be able to tamper with the phone by the means I mentioned or similar approaches?
Thanks
Click to expand...
Click to collapse
I feel your concerns. I think the safest bet is to watch where you download apps and content from. And make sure "unknown sources" is turned off. That should minimize your potential for problems. I think the main thing is watching where you get apps from.
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