Related
Per title, Nexus 6 will not get past the white "Google". I can get into recovery fine. But the bootloader is locked, so I cannot properly flash stuff. Attempting to unlock the bootloader, I'm told I need to enable the option in the settings menu that I cannot access.
Looks like I'm not the only one I have the same issue and nothing works
AndrewZorn said:
Per title, Nexus 6 will not get past the white "Google". I can get into recovery fine. But the bootloader is locked, so I cannot properly flash stuff. Attempting to unlock the bootloader, I'm told I need to enable the option in the settings menu that I cannot access.
Click to expand...
Click to collapse
is this happened after trying to install update with adb sideload?
I got my nexus 6 today and tried to sideload the ota zip file, but I had no luck and now my nexus can not boot. I had enabled the option for bootloader unlock but my big mistake was that i tried to factory reset the device from recovery and now the bootloader can't be unlocked.
supposed to be experience with nexus devices, but with the bootloader locked I don't know what to do.
any ideas guys?
psybill said:
is this happened after trying to install update with adb sideload?
I got my nexus 6 today and tried to sideload the ota zip file, but I had no luck and now my nexus can not boot. I had enabled the option for bootloader unlock but my big mistake was that i tried to factory reset the device from recovery and now the bootloader can't be unlocked.
supposed to be experience with nexus devices, but with the bootloader locked I don't know what to do.
any ideas guys?
Click to expand...
Click to collapse
Yeah I think that's what I may have done too. I was just trying to go back to 100% stock (ignoring 5.1 even).
And of course NOW the 5.1 image is up on Google's page.
Have the same situation: flash 5.1 OTA and then wiped system
Now I can't unlock bootloader (as system just cant boot) and can't flash stock image (as system.img can't be flashed with locked bootloader)
I do not want to believe this is a brick, but it is very likely it
Sadly I've just done the same thing. ADB updated from 5.0.1 to 5.1, and the system.img didn't copy correctly. Phone wont boot past the Google splash screen, and I can't flash a factory image to recover the phone, because in order to unlock the bootloader I have to enable the option in developer settings, which I can't get to because the phone wont boot!
I understand the purpose of having an extra layer of security to prevent malicious types from trying to flash factory images onto stolen devices, but surely any system that allows a user to brick a device simply by leaving a setting unchecked (in a hidden menu, no less!) is asking for trouble? Particularly on a developer orientated device like a Nexus.
It seems crazy that a developer can ADB the official Google Android OTA zip, using the official Google Android SDK, onto the official Google Android flagship device, and the simple corruption of one of the sent files can cause the device to become totally unusable. Surely, say, providing an option in the developer option settings to PIN protect the bootloader, rather than just preventing it from being unlocked all together, would be a more sensible choice?
For what it's worth, I explained my situation to Google, and they are replacing the phone under warranty. This is probably your best (or only) option at this stage.
Good luck, and please let me know if you do manage to find a work-around/ solution to your woes!
I just want to root my HTC Desire 510 in order to use Xmod game assistant and just to delete bloatware. I tried using kingoroot, it said success, but it actually didn't even work. I found out that you need to unlock the bootloader. I don't really want to this, i have no interest in it. I was thinking of using Kingoroot's HTC bootloader unlock to unlock it, then root it using the kingoroot rooter, then re-lock the bootloader with the Kingoroot bootloader program. Is it risky? Please note my phone has no important data, it's new. And I do not want to install anything custom. Just get xmod and remove bloatware. That's all I need.
Would this all work? Please help.
uRager said:
I just want to root my HTC Desire 510 in order to use Xmod game assistant and just to delete bloatware. I tried using kingoroot, it said success, but it actually didn't even work. I found out that you need to unlock the bootloader. I don't really want to this, i have no interest in it. I was thinking of using Kingoroot's HTC bootloader unlock to unlock it, then root it using the kingoroot rooter, then re-lock the bootloader with the Kingoroot bootloader program. Is it risky? Please note my phone has no important data, it's new. And I do not want to install anything custom. Just get xmod and remove bloatware. That's all I need.
Would this all work? Please help.
Click to expand...
Click to collapse
No this won't work and the number one reason is because if you root the phone and then spend your time deleting all the bloatware you'll be wasting your time if you don't install a kernel with write protection removed because as soon as you reboot the phone will reinstall everything! So you need to unlock the bootloader and then install the custom recovery and then make a backup first before doing anything else and then install the kernel with write protection removed and then delete bloatware!
Ok, I decided I don't want to remove bloatware. I am just rooting so I can download Xmodgames and such apps that need a rooted device. No custom ROMS or anything. Would I be fine?
uRager said:
Ok, I decided I don't want to remove bloatware. I am just rooting so I can download Xmodgames and such apps that need a rooted device. No custom ROMS or anything. Would I be fine?
Click to expand...
Click to collapse
Yes. Although be warned rooting will restore the phone to stock after unlocking the bootloader.
Can you even use the phone if you make changes? What I mean is isn't the point behind a locked bootloader to keep changes from being made? So if you unlock -> make a change (rooting for example) -> then relock .... doesn't that equal bootloop when the bootloader notices you've changed something?
For my two cents... I'm probably more of a noob than you @uRager, and I got through the unlocking and rooting process with not too much trouble. I think the good old fashioned way will probably serve you the best. And there are several kernels that are just a modified version of the stock kernel (write protection removed) so a couple more minutes will get the bloat removed as well. Also don't be afraid to ask questions, from what Ive seen they usually get answered.
hi all,
i have recently aquired Sony Xperie SP C5303, and i now i'm lost since i never had android phone. all i used was various emulators for PC and stuff...
but now there is many stuff to be noisy about. and probably this has been answered many times but please, do me a favor and pretty please answer again if possible.
1. Phone is SIM locked (i'm working on getting unlock code from provider, since i have right to do so, after contract expires..which has)..but is there any way to unlock phone before i get the code? i'm wondering how technitians in local services do that. they ask about 30€ for unlocking device, and i doubt they have acces to provider's unlock code.
2. I tried to flash phone with custom firmware (using flashtool) but it failed on me even though i used right firmware, and phone bricked. however i managed to recover phone with sony PC companion and it now works same as when i got it. Firmware 12. 1. A. 1. 205, android version 4.3. i have no idea why it failed on me during flash. can it be cause phone is no rooted, and have no root support? (whill connect to this on 3.) do i have to root phone before flashing? i would really like to have root access.
3. i was unable to do hard reset of phone with power + volume down button. or any other trick didn't work. i couldn't not enter android recovery options. i followed instruction on how to root my phone on
Code:
developersonymobile(dotcom)/unlockbootloader/unlock-yourboot-loader/
. i entered
Code:
*#*#7378423#*#*
to check if my device is unlockable, it says boot loader unlock allowed : No. Does this mean i won't be able to have root acces on my phone? or i still have to learn difference between terms or what they mean.
also is that really true what they warn about that there is no turning back after i root phone and all. won't just hard reseting phone or repair device with all defaults troubh pc sofware bring back and vipe everything back? how will than service know if phone has been rooted ever?
thank you in advance for all your answers.
"Bootloader unlock allowed : No" <= this means you can't use UBL ROMs or custom kernels.
You can always root and use LBL ROMs though. There are plenty of LBL ROMs out there to try.
You can always un-root your phone. And you can always repair your phone's OS by flashing the Stock ROM via flashtool. Doing so would remove root access as well, no one would know you ever rooted.
Root using towelroot.
Get recoveries by Dssmex.
Then flash LBL ROMs, mods, ports etc. that you want.
and Be careful when you flash anything,
Read the threads, don't try to flash any UBL ROM as it may brick your device.
First thank you for helping.
UBL is unlocked boot loader right? and L is locked. sorry to doubt your last tip but i need to double check was it typo or...? you said don't flash UBL. isnt that supposed to say don't flash LBL. or i have totally got this wrong. maybe i don't know what what's LBL and UBL.
but just to be safe? where can i find stock ROM? i tried official site, they don't let me download firmware manualy. only trough sony PC companion automatic repiar. Which is ok too i guess. else i can download sony flash tool callsed emma, but i cannot get login info since they need about 7 days to approve my registration.
so my first step is to root my phone. ok i will do that. i might do it manualy, not trough application though.
what about sim lock? after i root phone, is there sim unlock command or what? and do i need code...how do you unlock your phone to be able to use other SIM.
IrethTassartir said:
First thank you for helping.
UBL is unlocked boot loader right? and L is locked. sorry to doubt your last tip but i need to double check was it typo or...? you said don't flash UBL. isnt that supposed to say don't flash LBL. or i have totally got this wrong. maybe i don't know what what's LBL and UBL.
but just to be safe? where can i find stock ROM? i tried official site, they don't let me download firmware manualy. only trough sony PC companion automatic repiar. Which is ok too i guess. else i can download sony flash tool callsed emma, but i cannot get login info since they need about 7 days to approve my registration.
so my first step is to root my phone. ok i will do that. i might do it manualy, not trough application though.
what about sim lock? after i root phone, is there sim unlock command or what? and do i need code...how do you unlock your phone to be able to use other SIM.
Click to expand...
Click to collapse
Welcome.
And no, I did mean "Don't flash UBL ROMs"
UBL = Unlocked Bootloader
LBL = Locked Bootloader
The ROMs that are made for Unlocked Bootloaders are UBL ROMs.
Unlocked Bootloader users can use both LBL and UBL ROMs.
But since your device's Bootloader cannot be unlocked, you can only use LBL ROMs.
It's written in almost all ROM threads if it's a LBL or an UBL ROM. But if it isn't specified, then be sure it's UBL. (Like all 5.1 ROMs are for UBL)
Download stock ftf from here.
Use Flashtool v0.9.18.5
and I can't say about the last one as I don't use a carrier locked device.
Try and see what happens.
thank you again for reply. you've been very helpfull with all info.
Zenith said:
Download stock ftf from (link deleted, i'm not allowed to post it)
Click to expand...
Click to collapse
that is exactly from where i got it the first time. also same flashtool version. after i tried to use that firmware, my phone bricked.
even though it's stock ROM, probably cause my phone had locked bootloader (i finally found article on what is bootloader and i got it now).
but after this, i have used sony software to recover my phone and it works again.
now important stuff. so my device's bootloader cannot be unlocked. does that 100% means that i'm stuck with locked bootloader and no way of getting it unlocked.
even on sony offical site there is process tutorial how to unlock bootloader, and it says "if you device isn't listed, than you cannot unlock bootloader".
but it IS listed and I AM able to get the unlock code for it. now i'm confused. can i still do the process showed?
another confusing thing is where i read about bootloader, it says that for to be able to root i need to flash custom ROM, and to do that i need to unlock bootloader.
but you have provided link for "towelroot" which was able to get my phone root acces. is it different from rooting my phone manualy after unlocking bootloader. how did it manage to root it anyway? and with towelroot it still has bootloader locked. actually it says "boot loader unlock allowed: NO!". now begs the question does that mean, not allowed, but i can be unobidient one and still unlock it without clearance, or does it mean .."you're stuck with locked bootloader. deal with it!. if you try to unlock bootloader your phone will brick"!.
i think after i get answer to this, than it would be my last question for this topic
also again, thank you for answering all previous questions...and this one, hopefully
IrethTassartir said:
thank you again for reply. you've been very helpfull with all info.
that is exactly from where i got it the first time. also same flashtool version. after i tried to use that firmware, my phone bricked.
even though it's stock ROM, probably cause my phone had locked bootloader (i finally found article on what is bootloader and i got it now).
but after this, i have used sony software to recover my phone and it works again.
now important stuff. so my device's bootloader cannot be unlocked. does that 100% means that i'm stuck with locked bootloader and no way of getting it unlocked.
even on sony offical site there is process tutorial how to unlock bootloader, and it says "if you device isn't listed, than you cannot unlock bootloader".
but it IS listed and I AM able to get the unlock code for it. now i'm confused. can i still do the process showed?
another confusing thing is where i read about bootloader, it says that for to be able to root i need to flash custom ROM, and to do that i need to unlock bootloader.
but you have provided link for "towelroot" which was able to get my phone root acces. is it different from rooting my phone manualy after unlocking bootloader. how did it manage to root it anyway? and with towelroot it still has bootloader locked. actually it says "boot loader unlock allowed: NO!". now begs the question does that mean, not allowed, but i can be unobidient one and still unlock it without clearance, or does it mean .."you're stuck with locked bootloader. deal with it!. if you try to unlock bootloader your phone will brick"!.
i think after i get answer to this, than it would be my last question for this topic
also again, thank you for answering all previous questions...and this one, hopefully
Click to expand...
Click to collapse
Did you install the drivers properly (Flashmode, fastboot, viskan common) ?
You need to disable driver signature verification before installing drivers if you're on Win 8/8.1/probably 10 too.
And flashtool should work perfectly in both LBL and UBL phones.
You said your service menu says, "Bootloader unlock allowed : No"
Even if you get a BL unlock code you can't unlock it coz it's not allowed.
And by messing with the bootloader or trying to flash UBL ROMs may permanently brick your phone.
And different phones have different rooting processses. Rooting our SP is easier than most other phones by TowelRoot.
And "Bootloader unlock allowed : No" is more like a "You're stuck with locked bootloader. deal with it!. If you try to unlock bootloader your phone will brick!".
And you can still use a lot of LBL ROMs, from 4.3 to 5.0. So don't worry Lol.
Welcome
i did install fastboot and drivers and everything acording to tutorial. i payed attention on par "pay attention to this. be sure to install drivers correctly, lol"
i'm using win 7 64bit sp1. i have disabled UAC. i'm alaways running as admin. as for flashtool. software works perfectly..it just fail flashing.
it goes to part where i need to unplug phone and plug in holding volume something button..it says on poppup. than i plug in phone and it starts flasshing..it goes up to 40% something percent. if finish few files but when it comes to system.(something) i forgot extension, it says failed. flasshing stopped. than after that i can't turn on phone again.
i couldn't untill i recovered via Sony PC companion. i did try to flash it several times with several roms. i think it's cause my provider messed with bootloader. they locked it together with sim. on official sony site. it says:
"Note! Even if your device is listed here, certain releases of the device model may not be supported due to operator restrictions. Please select your device on the Start tab to check if your particular device can be unlocked."
anyway, i even got my provider's firmware trough flashtool download system, got my provider's name and exact same firmware that was installed. it still failed on same file.
than after i recovered i didn't try to flash anymore. i don't even know what's the point, if i can have root access without it.
i'm not so keen on installing other android version, unless this one gives me problem. for that i need to unlcok phone first to be able to even use it or test it so far it's has been t urned off most of the time
IrethTassartir said:
i did install fastboot and drivers and everything acording to tutorial. i payed attention on par "pay attention to this. be sure to install drivers correctly, lol"
i'm using win 7 64bit sp1. i have disabled UAC. i'm alaways running as admin. as for flashtool. software works perfectly..it just fail flashing.
it goes to part where i need to unplug phone and plug in holding volume something button..it says on poppup. than i plug in phone and it starts flasshing..it goes up to 40% something percent. if finish few files but when it comes to system.(something) i forgot extension, it says failed. flasshing stopped. than after that i can't turn on phone again.
i couldn't untill i recovered via Sony PC companion. i did try to flash it several times with several roms. i think it's cause my provider messed with bootloader. they locked it together with sim. on official sony site. it says:
"Note! Even if your device is listed here, certain releases of the device model may not be supported due to operator restrictions. Please select your device on the Start tab to check if your particular device can be unlocked."
anyway, i even got my provider's firmware trough flashtool download system, got my provider's name and exact same firmware that was installed. it still failed on same file.
than after i recovered i didn't try to flash anymore. i don't even know what's the point, if i can have root access without it.
i'm not so keen on installing other android version, unless this one gives me problem. for that i need to unlcok phone first to be able to even use it or test it so far it's has been t urned off most of the time
Click to expand...
Click to collapse
I see.. I'm not actually sure why Flashtool isn't working.
Anyways some good 4.4.4 LBL ROMs are 'CM11 by Bagyusz', 'Omni-X by NeildownX', PA etc.
Try them if you want.
Zenith said:
I see.. I'm not actually sure why Flashtool isn't working.
Anyways some good 4.4.4 LBL ROMs are 'CM11 by Bagyusz', 'Omni-X by NeildownX', PA etc.
Try them if you want.
Click to expand...
Click to collapse
can i use flashtool to install CM11 by Bagyusz. on CM11 thread, under tutorial it says enter recovery mode..i can't do that. nothing happens when i power up+volume down ..or up..or any other combination. i installed clockwork mod, but i cannot install cwm recovery sincy my device is not listed. if i try to restart phone in recovery mode, nothing happens! it just restarts phone normaly!
IrethTassartir said:
can i use flashtool to install CM11 by Bagyusz. on CM11 thread, under tutorial it says enter recovery mode..i can't do that. nothing happens when i power up+volume down ..or up..or any other combination. i installed clockwork mod, but i cannot install cwm recovery sincy my device is not listed. if i try to restart phone in recovery mode, nothing happens! it just restarts phone normaly!
Click to expand...
Click to collapse
I assume you're now on a rooted stock ROM.
Follow this to get recoveries.
Reboot, when you see the Blue LED burn, press vol down to enter TWRP recovery.
can i use cm-11-20150822-UNOFFICIAL with flashtool so i avoid installing recoveris or CWMP?
flashtool worked for me it just gave me an error during flashing one of the files....that might be cause i didn't know difference between LBL roms and UBL roms. maybe problem was incorrect rom type for my phone.
i tried to install recovery tools. and i had some problems...when i swhitched on phone there was no light showdown,,just red led...and after phone entered safe mode. but not in recovery menu.
i sure have no idea what to do...now everything is so strange.
to be honest i'm considering dropping this whole thig of and use stock rom as it is...
it would be cool if there would be automatic debloat application which will remove all bloatware...
or at least bloatware list of apps i can delete manually, without loosing important function on my phone. than i would not need custom rom!
IrethTassartir said:
can i use cm-11-20150822-UNOFFICIAL with flashtool so i avoid installing recoveris or CWMP?
flashtool worked for me it just gave me an error during flashing one of the files....that might be cause i didn't know difference between LBL roms and UBL roms. maybe problem was incorrect rom type for my phone.
i tried to install recovery tools. and i had some problems...when i swhitched on phone there was no light showdown,,just red led...and after phone entered safe mode. but not in recovery menu.
i sure have no idea what to do...now everything is so strange.
to be honest i'm considering dropping this whole thig of and use stock rom as it is...
it would be cool if there would be automatic debloat application which will remove all bloatware...
or at least bloatware list of apps i can delete manually, without loosing important function on my phone. than i would not need custom rom!
Click to expand...
Click to collapse
If you're on CM11 by Bagyusz, Open Terminal Emulator and enter the following codes,
su
./system/bin/recovery.sh
^ it will give you access to recovery when you see the red LED while booting.
If you decide to go back to stock, you can freeze/remove these apps.
I made the list when I was on stock. Take a backup before removing them just to be safe.
thank you a lot! this has all been so helpful!
IrethTassartir said:
thank you a lot! this has all been so helpful!
Click to expand...
Click to collapse
Welcome
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