Related
Noob question I know but I've tried reading up on the subject as much as I can - I still don't fully understand what exactly the locked loader does to this phone (aside from making it more difficult to root) and would really appreciate a brief explanation.
As I understand now the phone can be rooted, ROMs can be loaded (but they have to be specific to the VZW S3 right?), and full recovery options as well. Basically wondering what the disadvantages are and if they're more significant than just a little more work to root/mod the phone? Much thanks!
It prevents root access, you know jail breaking. You can't control your rom. You use the one provided to you by Verizon with all their bloatware. You can't change what software was delivered to you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
It prevents changing boot.img
Sent from my SCH-I535 using xda app-developers app
saucyzest said:
Noob question I know but I've tried reading up on the subject as much as I can - I still don't fully understand what exactly the locked loader does to this phone (aside from making it more difficult to root) and would really appreciate a brief explanation.
As I understand now the phone can be rooted, ROMs can be loaded (but they have to be specific to the VZW S3 right?), and full recovery options as well. Basically wondering what the disadvantages are and if they're more significant than just a little more work to root/mod the phone? Much thanks!
Click to expand...
Click to collapse
A locked bootloader is ultimately intended to prevent you from potentially costing the carrier $money$ by:
Bricking your phone and then playing dumb when you return it for an exchange. (people on xda opening admit to this kind of fraud. kinda sad. you brick it you keep it!, or buy another)
Modifying your phone and then blaming bugs on the carrier. A support vampire.
Assuring content providers they've made exclusive deals with that their content is "secure".
Great Question!
If your phone was a Windows 7 computer....
If you rooted it, you'd have an account with Administrator access.
As for the bootloader... Suppose you wanted to upgrade to Windows 8, even though it hasn't been authorized by your ISP, on this Windows 7 computer with a locked bootloader.
You cant, c:\windows is locked. If you change anything in that directory, your Windows 7 computer will start, but only to display "Invalid System Software Installed! Please shutdown and return this computer to your ISP's store for assistance."
What we have on Verizon, is a phone with admin rights (rooted), where we can't re-install the software needed to boot a different operating system.
If you're interested in more detail on how the hardware prevents the bootloader from being cracked, and what the attack vectors are, you might be interested in the presentation linked from this post http://forum.xda-developers.com/showthread.php?t=1766638
(And yes I know that c:\windows isn't actually the boot partition on windows. Just trying to make it easier for the OP to understand.)
jmacko said:
Great Question!
If your phone was a Windows 7 computer....
If you rooted it, you'd have an account with Administrator access.
As for the bootloader... Suppose you wanted to upgrade to Windows 8, even though it hasn't been authorized by your ISP, on this Windows 7 computer with a locked bootloader.
You cant, c:\windows is locked. If you change anything in that directory, your Windows 7 computer will start, but only to display "Invalid System Software Installed! Please shutdown and return this computer to your ISP's store for assistance."
What we have on Verizon, is a phone with admin rights (rooted), where we can't re-install the software needed to boot a different operating system.
If you're interested in more detail on how the hardware prevents the bootloader from being cracked, and what the attack vectors are, you might be interested in the presentation linked from this post http://forum.xda-developers.com/showthread.php?t=1766638
(And yes I know that c:\windows isn't actually the boot partition on windows. Just trying to make it easier for the OP to understand.)
Click to expand...
Click to collapse
Thank you for this explanation, I found it helpful to hear such an analogy.
jmacko said:
Great Question!
If your phone was a Windows 7 computer....
If you rooted it, you'd have an account with Administrator access.
As for the bootloader... Suppose you wanted to upgrade to Windows 8, even though it hasn't been authorized by your ISP, on this Windows 7 computer with a locked bootloader.
You cant, c:\windows is locked. If you change anything in that directory, your Windows 7 computer will start, but only to display "Invalid System Software Installed! Please shutdown and return this computer to your ISP's store for assistance."
What we have on Verizon, is a phone with admin rights (rooted), where we can't re-install the software needed to boot a different operating system.
If you're interested in more detail on how the hardware prevents the bootloader from being cracked, and what the attack vectors are, you might be interested in the presentation linked from this post http://forum.xda-developers.com/showthread.php?t=1766638
(And yes I know that c:\windows isn't actually the boot partition on windows. Just trying to make it easier for the OP to understand.)
Click to expand...
Click to collapse
Thanks that really helped. So in the example of Jelly Bean -sounds like we need to wait for Verizon to release a version of it? Do all custom ROMs as well have to be based off of the VZW file that checks ok with the bootloader?
I'm really only concerned with Jelly Bean (knowing how long VZW takes to release stuff) and that wifi nag screen, I want to punch someone in the nose every time i see it...I will check out that presentation over lunch, would love to learn all about the details.
interesting and helpful topic.. however.. i thought i understood the locked bootloader situation on my droid bionic i could flash any rom i wanted to in conjunction with bootstrap wich i believe to be a bootloader by pass based recovery but no kernals were able to be flashed that is what i understood to be a locked b.l was not overclocking or custom kernals maybe i was wrong this whole time..
Bfitz26 said:
interesting and helpful topic.. however.. i thought i understood the locked bootloader situation on my droid bionic i could flash any rom i wanted to in conjunction with bootstrap wich i believe to be a bootloader by pass based recovery but no kernals were able to be flashed that is what i understood to be a locked b.l was not overclocking or custom kernals maybe i was wrong this whole time..
Click to expand...
Click to collapse
Weird this is how i understood it as well. I'm coming from the Droid X2 and thanks do DK we had cm9 up and running with ICS but the bootloader was locked down. I took it that bootstrap is a recovery tool that works in a way of when your phone is off and you plug it in you boot up to the bootloader. This would allow you to re-flash a rom if your current one was corrupt.
So in my mind you can run different roms and different android versions its just harder to get them on the phone. But from what i've seen you cant flash a new kernal if the bootloader is locked.
Maybe i miss understood this if so i really would like to know fully how this works
On the verizon gs3 the locked bootloader is keeping us from flashing a custom kernel thru odin...we can root and flash a custom rom / recovery but it has to utilize the stock kernel currently. Our bootloader debacle is nothing like moto devices and I wish folks would stop comparing the 2!
droidstyle said:
On the verizon gs3 the locked bootloader is keeping us from flashing a custom kernel thru odin...we can root and flash a custom rom / recovery but it has to utilize the stock kernel currently. Our bootloader debacle is nothing like moto devices and I wish folks would stop comparing the 2!
Click to expand...
Click to collapse
Exactly, what a locked bootloader will allow you to do will vary on different phones and firmwares. I've known some which would not even allow you to flash a recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
I really hope we get the bootloader unlocked would love to see cm on this phone with some of invisblek's great kernels. btw will I be able to even usrge "set cpu" to overclock and under clock with verizon stock kernal or can this be done with tweaks in the build.prop file, forgive me if this sounds stupid its been a while and I am a samsung's odin first time user.
Sadly this is the outcome of Americans NOT buying a device without a subsidy from the carrier.
Kind of like whining about NOT getting the best Porterhouse steak when buying with food stamps......
I would love to see an end to carrier subsidies.
~~~Sent from the 23rd century, thru a Samsung Onehunglow powered by Walmart brand Higgs Boson particles. (Aisle 27)~~~
I am disappointed in samsung they start to look like Apple can not my apps to my sd card write that they have locked that 2
I've been watching the developer board regarding the root and locked bootloader issue, and I've spent hours researching this and have yet to find a solution that's known to work without loss of something, likely a permanent or semi permanent loss. My device is a Z3 model D6616. I'm unhappy with the phone for several other reasons, but haven't owned an un-rooted phone for some time, and prefer keeping this phone if I can root it successfully. Root with stock firmware is my objective and am only interested in responses from people that have themselves rooted (and dealt with bootloader issues) a Z3.
- Root phone installing current T-mobile stock firmware.
- Known loss of function: Sony DRM dependant features/funtion only (from memory, mostly related to camera low light performance and DRM playback issues)
- Other loss of function experienced with stock features, or any other problem with any other app. Especially concerned with root dependant features of Play apps? Also ad blockers?
- Waranty loss (potential) and loss of OTA updates understood.
- Feature/function loss with workarounds or fixed that survive power cycle?
- Expect permament bootlocker inability to relock
- A link to the specific process you used, any problems you encountered whatever the cause. For example it usually takes me at least 3 attempts to root using any complex process, and I always read through 5 times before starting and download every needed file and program in advance.
Again: Sony Xperia z3 D6616 T-mobile
Firmware: 4.4.4 23.0.3.1.123
Software: D6166 R16B
In the past, I've had the most problems when an understood part of a process is not explicitly stated, or I've ignored or misunderstood a step. Plugging and unplugging from usb to PC a typical example. I don't have the technical know how to critique or ignore, so always attempt to follow all instructions without variance. I've had some problems, and most were solved by starting the process again. I hesitate to ask for help since the last time I did that I was attacked for witholding information when asked if I had backed up the phone. Since i didn't have access to the PC at the time of the question I honestly answered I didn't know (since I had attempted to but couldn't confirm). If you've ever answered a question here implying the request or requester is stupid or dishonest, I'm fully aware of my ignorance and my own integrity, and other personality traits, so please ignore this request, which accepts my lack of knowlege and has no tolerance for your issues not previously resolved through your own peaceful and respectful process.
Please only respond if you have personally rooted this specific phone model. If you have not, but know someone who has, please ask them to review this post and respond.
Nobody has rooted this phone without unlocking the bootloader. If you unlock to root, you will permanently lose DRM keys from the TA partition with no way to recover. No current root method works on 4.4.4 on the Z3. No one knows when or if an exploit will be found. We all want root. If you want it now, unlock the bootloader. If you can wait, wait. It's your call either way. As soon as a root method surfaces, best believe it will be in these forums. I'll be waiting with you...
First of all, check *#*#7378423#*#* to see if you bootloader can be unlocked or not.
Coz I think 6616's bootloader is unlockable.
freddy1991 said:
First of all, check *#*#7378423#*#* to see if you bootloader can be unlocked or not.
Coz I think 6616's bootloader is unlockable.
Click to expand...
Click to collapse
This is true. D6616 owner here, T-MO not unlockable yet :/ eagerly awaiting root as well as I really enjoy the z3, maybe even more than my Nexus 6 (gasp, blasphemy!)
Thanks For the Responses
freddy you addressed my concern, exactly. My phone reports:
Rooting Status:
Boot Unlocker Allowed: No
Although variants of the z3 have been bootlocker unlocked and rooted, I have not found a clear claim that was successfully done with D6616 z3. Since I'm a new T-mobile customer, this and their attitude about it are a poor way to start. I have a HTC phone I haven't returned, maybe I can get them to take the Z3 back instead. While I have benefited from and appreciate the great work so many people have done to make our phones usable and available to us, I've seen how carriers, mfgs, and users push good phones to market crippled by junk and unecessarily locked down. it's time to consider the mamufacturers that have been successful building good phones and selling in places like China at much lower prices.
Regarding any loss of DRM, I couldn't care less. This phone takes worse low light photos and video than my rooted Samsung G3, making it functionaly useless to me. Add to that the lack of a rational UI for telephony and IM, and done with Sony.
To be clear, if the bootloader can be unlocked and the phone can be rooted and you have done this yourself, please post.
Well...
I think there is no way you could unlock the bootloader of 6616.
The only way is to wait for the root on locked bootloader.
Check here http://forum.xda-developers.com/showthread.php?t=2940539
But that means you have to stick in the .93 firmware, even if the exploit is also usable for Z3.
Or return your 6616 and buy a 6603 or 6653 variant.
BREAKING NEWS
http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
Man, No bootloader unlock = Useless phone
HORiZUN said:
BREAKING NEWS
http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
Click to expand...
Click to collapse
Nope.
http://forum.xda-developers.com/showpost.php?p=58468332&postcount=815
I'm similarly confused about this whole thing, this new Giefroot program means we can all potentially get root for our devices, but we still lose the DRM keys right? So that means we can never have the Sony camera/image processing processes back again right?
Thwwack said:
I'm similarly confused about this whole thing, this new Giefroot program means we can all potentially get root for our devices, but we still lose the DRM keys right? So that means we can never have the Sony camera/image processing processes back again right?
Click to expand...
Click to collapse
NO
Unlocking the bootloader = loss of DRM
Rooting that does not involve unlocking the bootloader means you keep the DRM keys
gregbradley said:
NO
Unlocking the bootloader = loss of DRM
Rooting that does not involve unlocking the bootloader means you keep the DRM keys
Click to expand...
Click to collapse
Thanks, I'm new to Android and this is all over my head. To clarify, Giefroot does this without unlocking the bootloader?
It's all pretty frustrating, I gotta say... I'd love to install Cyanogenmod on this, but losing key features on the device is a pretty harsh trade off.
Thwwack said:
Thanks, I'm new to Android and this is all over my head. To clarify, Giefroot does this without unlocking the bootloader?
It's all pretty frustrating, I gotta say... I'd love to install Cyanogenmod on this, but losing key features on the device is a pretty harsh trade off.
Click to expand...
Click to collapse
Yes, giefroot does not unlock the boot. There is only one way to do that and that is to obtaining the code from sony and fastboot it either manually or using flashtool.
Delete
hello guys
i intended to create a custom recovery
i have done several methods like grabbing a exact specs recovery and modding it according to my phone
and i flashed it to my phone
it flashed
but after that when i am going to recovery it saying that
"this phone has been installed a unautorised version of android and contact the customer care for any problem"
indirectly it saying that the recovery i installed is a modded and we wont allow such kind of things ,so reinstall the original firmware
what is the problem
is that i ave something wrong
kvbkiran said:
hello guys
i intended to create a custom recovery
i have done several methods like grabbing a exact specs recovery and modding it according to my phone
and i flashed it to my phone
it flashed
but after that when i am going to recovery it saying that
"this phone has been installed a unautorised version of android and contact the customer care for any problem"
indirectly it saying that the recovery i installed is a modded and we wont allow such kind of things ,so reinstall the original firmware
what is the problem
is that i ave something wrong
Click to expand...
Click to collapse
You omitted to mention the phone model which is important in troubleshooting.
And it sounds like you tried to flash a custom recovery to a device that has a locked bootloader which usually leads to these kinds of results.
Nonta72 said:
You omitted to mention the phone model which is important in troubleshooting.
And it sounds like you tried to flash a custom recovery to a device that has a locked bootloader which usually leads to these kinds of results.
Click to expand...
Click to collapse
sorry to not mentioning that
i have a LYF flame 1 (ls4503)
running 5.1.1
Nonta72 said:
You omitted to mention the phone model which is important in troubleshooting.
And it sounds like you tried to flash a custom recovery to a device that has a locked bootloader which usually leads to these kinds of results.
Click to expand...
Click to collapse
there is no bootloader in this mobile
or the bootloader has been locked so it cant be unlocked anyway
i have tried different methods
you may have a look at this thread:https://forum.xda-developers.com/android/help/lyf-flame-1-custom-recovery-t3453265
and this
https://forum.xda-developers.com/android/help/how-to-unlock-bootloader-lyf-flame-1-ls-t3532776
these threads are about my device
the bootloader wont unlock
its just saying error remote command
kvbkiran said:
there is no bootloader in this mobile
or the bootloader has been locked so it cant be unlocked anyway
i have tried different methods
you may have a look at this thread:https://forum.xda-developers.com/android/help/lyf-flame-1-custom-recovery-t3453265
and this
https://forum.xda-developers.com/android/help/how-to-unlock-bootloader-lyf-flame-1-ls-t3532776
these threads are about my device
the bootloader wont unlock
its just saying error remote command
Click to expand...
Click to collapse
You're probably wrong. Only Mediatek powered phones can be modded without unlocking their bootloader (and even that's limited because it no longer works with newer chipsets).
Anyway, the message you're getting clearly means that the Bootloader is blocking unofficial softwares. You should probably ask the manufacturer for bootloader unlocking procedure.
Nonta72 said:
You're probably wrong. Only Mediatek powered phones can be modded without unlocking their bootloader (and even that's limited because it no longer works with newer chipsets).
Anyway, the message you're getting clearly means that the Bootloader is blocking unofficial softwares. You should probably ask the manufacturer for bootloader unlocking procedure.
Click to expand...
Click to collapse
but i am having a very old snapdragon chipset(its qualcomm snapdragon 210)
even thought if i ask for the manufacturers they wont expel because its not what they do
so you are saying that qualcomm chipsets cant be modded without unlocking bootloader right?
incase that
if you know any methods for the unlocking bootloader will you please tell me
i will try my level best
Nonta72 said:
You're probably wrong. Only Mediatek powered phones can be modded without unlocking their bootloader (and even that's limited because it no longer works with newer chipsets).
Anyway, the message you're getting clearly means that the Bootloader is blocking unofficial softwares. You should probably ask the manufacturer for bootloader unlocking procedure.
Click to expand...
Click to collapse
i contacted the customer care and they told that they wont provide such service now maybe in future
kvbkiran said:
i contacted the customer care and they told that they wont provide such service now maybe in future
Click to expand...
Click to collapse
Bad for you my friend.
Hi. Hope some Sony Xperia guru can help me with this.
I recently went on vacation and left my Xperia XA F3111 at home. Some a***hole had access to it for over 2 weeks and installed some malware on it. When I found out I factory reset the phone, but I really want to restore the stock ROM too in case he has flashed the phone with a malware-infested ROM which will survive a reset.
My problem is, the phone settings say "Bootloader unlock allowed = No". The guide here on XDA Developers say that this setting means he could not root the phone. My first question is, would this setting have also prevented him from installing a custom ROM?
If that would not have stopped him, are there any step-by-step instructions as to how I can reinstall a clean stock Sony ROM with that bootloader config setting in place?
Thx. D.
Hi, factory reset of the phone was the best choice. You don't need to worry about the integrity of the system as long as your bootloader stay locked so you don't need to flash it again.
For the malwares it's probably coming from crappy apps, for sample: https://www.google.com/amp/s/bgr.com/2018/11/25/google-play-store-apps-removed-malware-found/amp/
@rrvuhpg
Many thanks for your answer. The phone says the bootloader cannot be unlocked, but does this mean he could not have unlocked it, flashed a virus infected ROM and then re-locked it?
I mean, does that config setting mean that nobody can ever unlock the bootloader and change the ROM?
dmeddings said:
@rrvuhpg
Many thanks for your answer. The phone says the bootloader cannot be unlocked, but does this mean he could not have unlocked it, flashed a virus infected ROM and then re-locked it?
I mean, does that config setting mean that nobody can ever unlock the bootloader and change the ROM?
Click to expand...
Click to collapse
Yes exactly, almost nobody can corrupt the system (for now). If one day you see a TA dumper for locked bootloader on Nougat or a root exploit it will mean that your phone can be corrupted.
First of all:
I'm no Dev...just someone who likes to play lego.
From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk.
I've read a good startup here.
Hopefully this makes this thread clear enough so that i dont need to describe the whole procedure step by step.
(https://www.naldotech.com/root-samsung-galaxy-z-flip-3-5g-magisk/)
(1.OEM-Unlock,2.BL-Unlock,3.extract boot.img,4.patch boot.img via magisk on the unrooted mobile,5.patch boot.img.tar to AP&BL via Odin, 6.pray)
Anyways...here are maybe small hints to avoid a few traps.
a) Just do the oem-unlock in the dev-options (enabled by tapping buildnumber 5 times) is just half of the rent.
Afterwards i had to go in Download-mode (switch of mobile, press volUp+volDown and connect PC-cable.)
There appears a possibility of choice.
Press VolUp short: get the mobile on standby to flash the rom via odin.
Press VolUp LOONG: get the mobile to the menu where the bootloader can finally get unlocked. (Otherwhise every try to patch a rooted img will be blocked by bootloader-protection.)
Of course this can possibly be done via adb/fastboot commands.
Funny side note: OEM-Unlock-option will completely disappear from Dev-options and waranty is lost. Also the mobile stops to get Updates OTA which means that you have to update manually whenever a new version will appear in the net.
b) patching boot.img via magisk should work as described in many other magisk-rooting-manuals.
Flashing the tar back to the mobile via odin was little bit tricky.
It doesnt reach out just to provide the magisk_patched.tar to Odin just on the AB-line.
I had to patch it to BL too.
Cheers
MikGx
When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.
@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2
MikGx said:
@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2
Click to expand...
Click to collapse
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.
naldotech.com, the link you provide is pretty clear about the process. What it doesnt say is what to do at the end. When you untick "reboot" in odin, and you finish flashing, your phone will stay in download mode. Then what to do?. Press power and volume down to leave and restart the phone? or, power and volume down, screen goes black imediately power and volume up, enter recovery and restart from there.? please someone ?
Press the power and volume down buttons for about 7 seconds and it will reboot
beanbean50 said:
Press the power and volume down buttons for about 7 seconds and it will reboot
Click to expand...
Click to collapse
I did as you mention but it didnt work. It made me reset the system. But I Fallowed the naldotech.com guide. At the end, being in dawnload mode, I pressed power and volume down, when the screen got black I pressed power and volumen up, I entered recovery mod, cleared cache and re- started the system: Voila my phone is rooted
Hello.
Can someone pleas provide a working link for frija download? The one referring from naldotech seems to be broken (https://www.naldotech.com/download-samsung-galaxy-stock-firmware-frija-tool/)
Update: Found a link via google -> https://technastic.com/odin-download-samsung-latest-all-versions/
twistedumbrella said:
When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.
Click to expand...
Click to collapse
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.
d0x360 said:
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.
Click to expand...
Click to collapse
twistedumbrella said:
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.
Click to expand...
Click to collapse
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.
twistedumbrella said:
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.
Click to expand...
Click to collapse
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.
d0x360 said:
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.
Click to expand...
Click to collapse
You got where I said "I guess the disclaimer is misleading" right?
twistedumbrella said:
You got where I said "I guess the disclaimer is misleading" right?
Click to expand...
Click to collapse
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons
d0x360 said:
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons
Click to expand...
Click to collapse
Lucky? I dunno. Had I known it would cause this much trolling, I wouldn't have bothered to mention it.
I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?
david.siebauer said:
I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?
Click to expand...
Click to collapse
Partially. I just did that: I have AfWall running on my old phone, tried to unlock the Flip with this manual here in order to use the firewall there, did something wrong - and stumbled upon Netguard while searching what might have happened and decided to give it a try first. (Unless there is a custom ROM for the phone available, I have no other need for root or an unlocked bootloader.)
From what I could find on my Flip 3, you can unlock and relock the bootloader as you like - but as soon as you install a non-genuine bootloader (i.e. one chnaged by Magisk) you will trip Knox - and this cannot be reverted.
In such a case you can still re-lock your bootloader and unlock it later (on my phone, that "7-day-no-switch-indeveloper-options" routine kicked in, but you can circumvent that) - but Knox will stay in its state. From what I read this means some things will not work such as Samsung Pay, but I do not know the details (yet) apart from that it does not bother me ;-), and the nag screen during boot is gone.
Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now
david.siebauer said:
Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now
Click to expand...
Click to collapse
Well, it's better than my Sony - there it is "once unlocked, always unlocked" with no way back at all
But I have to admit I understand the logic why the manufacturers do that, at least to the degree that they trip a fuse as Samsung does.
By rooting the phone, you shift the responsibility for the software state of the phone from the manufacturer to the user, so I think it is okay to implement something to make it clear to possible future buyers that it is or has been in that state.
(This does not include however all the other stones they put in the way of people wanting to develop or use custom ROMs!)
I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features. Guess u shouldn't have bought a Samsung lol.
david.siebauer said:
I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features.
Click to expand...
Click to collapse
Oh, trust me - as soon as I hear there is a custom ROM that works as a daily driver I will root mine as well. I really hope that there will be one for this phone
david.siebauer said:
Guess u shouldn't have bought a Samsung lol.
Click to expand...
Click to collapse
Sadly there is no Fairphone mini or Fairphone Flip - or would it be Fairfliphone? ... Flipfairphone?... - yet (if ever), so the only current alternative would be Motorola. And the price tag for the Razr is simply too much, even if I personally think it looks better than the Samsung. Additionally, I do not know if they are in any way better when it comes to rooting or loading custom ROMs.