Just a suggestion and I'm not sure of the long term implications of this, but I was thinking those who want to avoid the hassles of getting the new bootloader that prevents fastboot boot and flash on locked bootloaders could try the following.
Unzip the update patch file to a folder on your computer.
Delete the bootloader.img file.
Use a text editor to open the file called /META-INF/com/google/android/updater-script and edit out/delete the following lines at the very end of the file:
Code:
ui_print("Writing bootloader...");
assert(package_extract_file("bootloader.img", "/tmp/bootloader.img"),
write_raw_image("/tmp/bootloader.img", "bootloader"),
delete("/tmp/bootloader.img"));
Rezip the folder with the altered files in it.
Boot to clockwork recovery and apply the update zip file with CW (since it's now not signed properly and stock won't do it.
We've had success with this type of modification to the update patch file from Google with people who modded /system files (like replacing gmail or the market app) that got failed updates on 2.3.1 and 2.3.2 updates.
I'm a bit pressed for time, but I may try this myself this weekend. I'm not in a big rush to update yet, though. I'm waiting for things like my custom kernel to become 2.3.3 friendly.
I've made a zip file that has the two changes I suggested above if anyone's brave enough to try it: http://dl.dropbox.com/u/432767/NoBo...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip
Bit late to the party i'm afraid, allready updated and flashed 2.3.3 update zip. I have lost my root and do not want to "fasboot oem unlock" yet...
My bad for being impatient as normal ^^
I will hold any actions and watch what solutions arise if any. Nice to see some methods being worked on
jamiemac1977 said:
Bit late to the party i'm afraid, allready updated and flashed 2.3.3 update zip. I have lost my root and do not want to "fasboot oem unlock" yet...
My bad for being impatient as normal ^^
I will hold any actions and watch what solutions arise if any. Nice to see some methods being worked on
Click to expand...
Click to collapse
Could you not flash back to stock using Odin and then apply the bootloaderless update after? Just an idea . . .
Is there any risk of bricking? If not I don't mind trying it.
Serious_Beans said:
Is there any risk of bricking? If not I don't mind trying it.
Click to expand...
Click to collapse
There is always a risk of bricking especially when playing with the bootloader.
kenvan19 said:
There is always a risk of bricking especially when playing with the bootloader.
Click to expand...
Click to collapse
But we're not messing with the bootloader per se, we're preventing the update script from checking it and reflashing/updating it.
Still, there's always the risk of bricking as you say.
Slightly off topic, buy why go to all the trouble when fastboot oem unlock is painless and 100% reversible? Why intentionally hobble along on a gimped locked bootloader?
mortzz said:
Slightly off topic, buy why go to all the trouble when fastboot oem unlock is painless and 100% reversible? Why intentionally hobble along on a gimped locked bootloader?
Click to expand...
Click to collapse
Because why not try? I'm not being sarcastic, ironic, facetious or anything rude, seriously; Why not? We have a phone that in terms of recent devices has an unprecedented amount of freedom in terms of rooting and unlocking of the device, why not push that to the limit and see just what can be done. Also, lets be honest, having your SD card wiped by the
Code:
fastboot oem unlock
command is kind of sucky. Sure you can copy all of your files to your computer then copy them all back but that isn't a short process and its boring as hell.
EDIT: @distortedloop: You know I trust you man, my point with my earlier comment is that running an outdated bootloader could very easily lead to an unbootable device, moreso than flashing a custom ROM so I was just being as honest and blunt as I could be
I updated the bootloader using:
fastboot flash bootloader bootloader.img
The bootloader stayed unlocked.
jamiemac1977 said:
Bit late to the party i'm afraid, allready updated and flashed 2.3.3 update zip. I have lost my root and do not want to "fasboot oem unlock" yet...
My bad for being impatient as normal ^^
I will hold any actions and watch what solutions arise if any. Nice to see some methods being worked on
Click to expand...
Click to collapse
You can replace the new bootloader in the update with the old bootloader, here's a link for the old bootloader Bootloader_I9020XXJK1
Has it been tested to work properly? It meaning the the old bootloader?
Sent from my MattedBlues CM7 Google Nexus S!
kenvan19 said:
Has it been tested to work properly? It meaning the the old bootloader?
Sent from my MattedBlues CM7 Google Nexus S!
Click to expand...
Click to collapse
I've been using it with 2.3.3 for the past day and it works perfectly, booting CWM and kernels without an OEM unlock.
Sent from my Nexus S using XDA App
Get Root Back With This Restore.
jamiemac1977 said:
Bit late to the party i'm afraid, allready updated and flashed 2.3.3 update zip. I have lost my root and do not want to "fasboot oem unlock" yet...
My bad for being impatient as normal ^^
I will hold any actions and watch what solutions arise if any. Nice to see some methods being worked on
Click to expand...
Click to collapse
if you have clockwork mod use this as a restore and you will have a rooted 2.3.3 its the easiest way to do it.
http://www.mediafire.com/?c1ww7zb837uycbk
just unzip and put the backup folder in your clockworkmod recovery folder boot into recovery and restore 2.3.3 takes 2 minutes and you will boot up with a rooted 2.3.3
also kept my bootloader unlocked. and i can flash back to any of my roms with no hassle keeping everything in tact.
reddv1 said:
You can replace the new bootloader in the update with the old bootloader, here's a link for the old bootloader Bootloader_I9020XXJK1
Click to expand...
Click to collapse
Ah thanks, I've been looking for that...
I'm going to link it in my root without unlock thread to help people who can't root now that they've updated with locked bootloaders.
kenvan19 said:
Because why not try? I'm not being sarcastic, ironic, facetious or anything rude, seriously; Why not? We have a phone that in terms of recent devices has an unprecedented amount of freedom in terms of rooting and unlocking of the device, why not push that to the limit and see just what can be done. Also, lets be honest, having your SD card wiped by the
Code:
fastboot oem unlock
command is kind of sucky. Sure you can copy all of your files to your computer then copy them all back but that isn't a short process and its boring as hell.
EDIT: @distortedloop: You know I trust you man, my point with my earlier comment is that running an outdated bootloader could very easily lead to an unbootable device, moreso than flashing a custom ROM so I was just being as honest and blunt as I could be
Click to expand...
Click to collapse
No worries on the outdated bootloader....that's why I said "I don't know the long term implications of this."
Everything you said, I couldn't have said better myself.
charlieb620 said:
if you have clockwork mod use this as a restore and you will have a rooted 2.3.3 its the easiest way to do it.
http://www.mediafire.com/?c1ww7zb837uycbk
just unzip and put the backup folder in your clockworkmod recovery folder boot into recovery and restore 2.3.3 takes 2 minutes and you will boot up with a rooted 2.3.3
Click to expand...
Click to collapse
But that defeats the whole point of not wanting to lose and restore your data, since the nandroid will write over all your stuff...
It also doesn't help those who end up with a locked bootloader and no root, since they can't access clockwork.
When I did it I kept my root and unlocked bootloader. If people didn't rush to update than they would have kept everything. I was able to restore my apps and all when I updated to the rooted 2.3.3
Sent from my Nexus S using XDA App
Will relocking bootloader wipe the phone?
I did "fastboot oem unlock" and everything is erased (it's not big deal as I always backup data).
mingkee said:
Will relocking bootloader wipe the phone?
I did "fastboot oem unlock" and everything is erased (it's not big deal as I always backup data).
Click to expand...
Click to collapse
No, the lock won't wipe it, just the unlock.
mingkee said:
Will relocking bootloader wipe the phone?
I did "fastboot oem unlock" and everything is erased (it's not big deal as I always backup data).
Click to expand...
Click to collapse
distortedloop said:
No, the lock won't wipe it, just the unlock.
Click to expand...
Click to collapse
Yes it will. Both locking and unlocking (via fastboot oem lock/unlock) will wipe your phone.
Related
.................
Unlocking will change no data on your phone. Fastboot oem unlock and go
Ignore the above, unlocking will wipe your phone.
Take a backup via recovery, unlock, then restore it.
..................
Rusty! said:
Ignore the above, unlocking will wipe your phone.
Take a backup via recovery, unlock, then restore it.
Click to expand...
Click to collapse
My bad, for some reason I never remembered it wiping my phone. Apologies.
Hollow.Droid said:
My bad, for some reason I never remembered it wiping my phone. Apologies.
Click to expand...
Click to collapse
That's fine, your intention was to help me .
Did it erase your custom recovery?
I'm wondering if I will have to install ClockworkMod again.
Will leave recovery alone, it's /data that goes when the phone is wiped.
Rusty! said:
Will leave recovery alone, it's /data that goes when the phone is wiped.
Click to expand...
Click to collapse
Thank you very much.
I dont mean to hijack a thread at the same time I don't want to start a new one on a simple question.
What is the benifit of an unlocked bootloader over just being rooted? With Gb on the horizon and every new update taking away easy root methods I've been debating on just unlocking and not worrying about it. Are there any other advantages?
wrench115 said:
I dont mean to hijack a thread at the same time I don't want to start a new one on a simple question.
What is the benifit of an unlocked bootloader over just being rooted? With Gb on the horizon and every new update taking away easy root methods I've been debating on just unlocking and not worrying about it. Are there any other advantages?
Click to expand...
Click to collapse
That's one advantage, another is that it lets you use fastboot for flashing radios etc. You don't risk bricking your phone that way.
I have a locked bootloader, I just use flash_image to flash the radios or whatever. Works just like fastboot.
futango said:
I have a locked bootloader, I just use flash_image to flash the radios or whatever. Works just like fastboot.
Click to expand...
Click to collapse
No, not "just like fastboot". If I'm not mistaken, flash_image doesn't check the signatures of the files being flashed, thus corrupt radios can be flashed using it, but they can't be flashed using fastboot - it'll safely revert the flash.
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
H4X0R46 said:
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
Click to expand...
Click to collapse
Thing is, when your bootloader is unlocked, the device is almost unbrickable. Also, you can be unlocked, 100% stock and still get OTA's if you want. If you have a locked bootloader, mess something up and end up in a bootloop, and can't boot to android, you're stuck.
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
H4X0R46 said:
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
Click to expand...
Click to collapse
Yes to all your questions.
Unlock it, its free insurance and wont change or harm a thing.
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
simms22 said:
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
Click to expand...
Click to collapse
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
danarama said:
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
Click to expand...
Click to collapse
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Evolution_Tech said:
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Click to expand...
Click to collapse
Well it shouldn't matter. When you tick that box, it writes the change to mmcblk0p18, which is OS independent. Now that booting the rom doesn't revert that partition, if it is ticked once, it shouldn't matter if there is an OS at all.
H4X0R46 said:
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Click to expand...
Click to collapse
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
cam30era said:
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
Click to expand...
Click to collapse
Scripts don't check recovery. It's just the OTA zip won't work without it.
-Jonny- said:
here you go!
Click to expand...
Click to collapse
Correct. Just taking this shortcut.
Great! Thanks guys! Appreciate all the help and support on this! I would HATE to brick a $700 device! Haha
Sent from my Nexus 6
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
H4X0R46 said:
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
Click to expand...
Click to collapse
N6 is ARM. Arm 64 is for 64 bit devices such as the N9.
Clarification question
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
alryder said:
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
Click to expand...
Click to collapse
Correct.
Ive done searching and just basically see alll sorts of other stuff. Im very familiar with rooting and modding. Done it now on 6 different phones. way back to the OG Droid.,.. This one is through the Jump program...... Id like to remain pure stock but root yet still have the ability to drop root when turning in the phone to get my g5 or v20. Root is all i want. no recovery or os..... The root will allow me to do viper audio, titanium and camera mods........ its H811 Tmobile running 20q pure stock.. please help..
MorbidMonkey101 said:
Ive done searching and just basically see alll sorts of other stuff. Im very familiar with rooting and modding. Done it now on 6 different phones. way back to the OG Droid.,.. This one is through the Jump program...... Id like to remain pure stock but root yet still have the ability to drop root when turning in the phone to get my g5 or v20. Root is all i want. no recovery or os..... The root will allow me to do viper audio, titanium and camera mods........ its H811 Tmobile running 20q pure stock.. please help..
Click to expand...
Click to collapse
yes its pure stock. you need to unlock bootloader .. and when return you need to relock it.
here are the commands for locking and relocking, and placing twrp temporary root it and then you are all set.
i use this method
go to where it says
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Going to try right now...actually better wait til after work tommorrow. Need it for alarm and tv time.. Just in case something happens.
raptorddd said:
yes its pure stock. you need to unlock bootloader .. and when return you need to relock it.
here are the commands for locking and relocking, and placing twrp temporary root it and then you are all set.
i use this method
go to where it says
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
To unlock first and add root i use this?
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
It wants me to downgrade and stuff. Is it possible to do it without downgrading? Also seems as alot of other posts say once your 20q you do not revert back to anything lower than 20o.. thats my concern.
Managed to get it unlocked.. Using that post.. Did not do the root part... So now.. Whats the next step? Install Recovery im sure. Then ROM... The plot thickens.
MorbidMonkey101 said:
To unlock first and add root i use this?
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
It wants me to downgrade and stuff. Is it possible to do it without downgrading? Also seems as alot of other posts say once your 20q you do not revert back to anything lower than 20o.. thats my concern.
Managed to get it unlocked.. Using that post.. Did not do the root part... So now.. Whats the next step? Install Recovery im sure. Then ROM... The plot thickens.
Click to expand...
Click to collapse
no dont downgrade i just used that post as reference the steps you need to use.. antirollback V3 (20o-20p-20q) (20i 10n this are V2.
yes install recovery use the same guide there..
use this recovery
https://dl.twrp.me/h811/
and rename it to twrp.img so the command should be renamed to twrp.img
have it on sd card. and hwen it boot you to twrp do install, then semlect botom right IMAGE and find the location the twrp is and select it and flash it , it will ask in a window select revocery .. and you are done with twrp installed permanent.
MorbidMonkey101 said:
To unlock first and add root i use this?
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
It wants me to downgrade and stuff. Is it possible to do it without downgrading? Also seems as alot of other posts say once your 20q you do not revert back to anything lower than 20o.. thats my concern.
Managed to get it unlocked.. Using that post.. Did not do the root part... So now.. Whats the next step? Install Recovery im sure. Then ROM... The plot thickens.
Click to expand...
Click to collapse
kk so i got it unlocked and rooted using that method.. but my phone reboots automatically every so often... what gives.. used adb to temp boot twrp...installed Su then rebooted...all done AFTER unlock
MorbidMonkey101 said:
kk so i got it unlocked and rooted using that method.. but my phone reboots automatically every so often... what gives.. used adb to temp boot twrp...installed Su then rebooted...all done AFTER unlock
Click to expand...
Click to collapse
Figured id say screw it.. I already unlocked and rooted.. might as well ROM it too.
im now running this mod. just unlocked and rooted using the method you told me.. then used twrp to install this ROM
https://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
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