Database Users

Root vs. Unlocked bootloader

In this thread I intend to give some basic insight about these two concepts, which are closely entwined with our phone's experience. I'm not a tech guy, but I think this little summary might clear some doubts for people who are new to this kind of issues (people who come from other non-Android phones especially). All feedback is welcome, in particular the one of people who can expand the topic with their knowledge.
"Root" is the common way to refer to the fact to the user account which has superuser rights on the device. Superuser rights imply full control over your phone's capacities, which are determined by the software and the hardware of the device. Non-superuser accounts have limitations, usually established for the sake of software security (for example, not allowing a user to disable critical functions such as phone or GPS), hardware safety (not allowing to change the processor's frequency speed, aka overclocking the CPU) or, in some cases, for someone's profit (disabling wi-fi tethering is a typical one as users are forced to buy data plans in order to use their devices to tether). In Android's case, Superuser is composed of an app* and a set of instructions to give this app root rights.
The bootloader is a program which accesses the internal storage and, basically, controls the loading of the programs and data necessary to initiate the sequence of launching the OS (aka booting, thus the name bootloader). We say that a bootloader is locked when it is programmed in such a way that it won't allow to load the device if it detects data from third-party sources. Unlocked bootloaders do allow these data and will load what these data contain, which will be usually a modified version of the phone's firmware, known as "Custom ROM".
As we can see, there was the fear that one would need to have unlocked bootloaders (i.e the ability to load third-party data in the booting sequence) in order to gain root rights. This would have been terribly inconvenient because only a minority of users will have unlocked bootloaders, since the phones with unlocked bootloaders by default are the ones sold carrier-unlocked. Said carrier-free phones will be a minority as the phone is pretty expensive: most Xperia Plays will be sold using carrier subsidies.
However, our fellow member Chainfire found an exploit (a programming loophole) in Gingerbread which allows said app and instructions to be loaded without the need of touching the bootloaders. Basically, his Gingerbreak program allows the user to have root rights without loading any bootloader-sensitive data. This widens the possibilities for the majority of users who will buy this phone with a subsidy.
*edit 3* Later on, it has become possible to unlock the bootloader even for SIM-locked devices, thanks to different unlockers like Alejandrissimo and Jinx13. This means that, provided that you pay what they charge, you can have your device set up without the bothers of having to buy a SIM-free phone. What's better: their method of unlocking the bootloader SIM-unlocks the phone as well.
I think this is more or less a succint framework of ideas which allows us to define "root" and "unlocked bootloaders" properly. As they say, knowing is half the battle, so I hope this nugget of information allows users to deal with their phones with more confidence.
*edit* as of version 2.3.3, this information has changed. Gingerbreak doesn't work with 2.3.3 anymore, and it seems now that the only way to root with locked bootloaders is to flash a 2.3.2 rom with FlashTool and update through OTA.
*edit2* note that this explanations pertains mostly to the Xperia Play. Other devices are NAND-locked, which means for us that they need unlocked bootloaders to even get root access.
*Note that Android is built in such a way that every app is a user account with limited rights (the ones specified before you download it). Thus, Superuser is a user account as any other app and the set of instructions is meant to give this user account root rights.

Thank you! This was very helpful in clarifying some things.

"As we can see, there was the fear that one would need to have unlocked bootloaders (i.e the ability to load third-party data in the booting sequence) in order to gain root rights. This would have been terribly inconvenient because only a minority of users will have unlocked bootloaders, since the phones with unlocked bootloaders by default are the ones sold carrier-unlocked. Said carrier-free phones will be a minority as the phone is pretty expensive: most Xperia Plays will be sold using carrier subsidies"
by carrier unlocked do you mean sim unlocked? sorry 4 noob question

Indeed, that is what I mean.

Logseman said:
Indeed, that is what I mean.
Click to expand...
Click to collapse
Alright, I asked this question and it was answered, but I want to make sure before I try anything.
I just found out from SE that my phone is the Rogers version. It's obviously been unlocked because I'm using it on AT&T.
What I don't know, though, is whether the bootloader is unlocked. Another member recommended that I check TrackID to see if it worked because it depends on the manufacturer DRM's that are wiped in unlocking the bootloader. It did work, so I assume it's still locked, but I wanted to confirm because of being carrier unlocked.
Sent from my R800a using XDA App

If TrackID works, your bootloader is locked, regardless of simlock.

I have a Sim-Unlocked Xperia Play from Rogers that I am using on ATT's network. My phone is boot-locked. When powered off, if I hold the search key while plugging in the USB cable, I do not get a blue light.
I was able to flash the firmware by holding the back key while plugging in the usb cable (with the phone off). I get a green light when I do this. Using flashtool, I was able get 2.3.3 rooted by loading the 2.3.2 firmware, rooting, and then updating OTA.
I bricked my phone several times while loading the firmware and each time I was able to fix it with flashtool or Sony Ericsson's Upgrade Utility. I found that you need a good USB cable, and even then it failed sometimes. I just kept trying and eventually it worked.

We wanted to provide an update on HTC’s progress with bringing bootloader unlocking to our newest phones. We know how excited some of you are for this capability, and we’ve put significant resources behind making this change as soon as possible. While we wish we could flip a simple switch and unlock all bootloaders across our device portfolio, this is actually a complex challenge that requires a new software build and extensive testing to deliver the best possible customer experience.
We’re thrilled to announce today that software updates to support bootloader unlocking will begin rolling out in August for the global HTC Sensation, followed by the HTC Sensation 4G on T-Mobile USA and the HTC EVO 3D on Sprint. We’re in the testing phase for the unlocking capability now, and we expect it to be fully operational by early September for devices that have received the software updates. We'll continue rolling out the unlocking capability over time to other devices as part of maintenance releases and new shipments.
HTC continues its commitment to unlocking bootloaders and supporting the developer community. Because of the importance of this community to us, please expect an update on this about every few weeks as we make progress toward launch. Thank you for your patience and continued support!
(they claim it will come to only two devices for starters the EVO 3D and the Sensation 4G and then it will slowly rollout to other devices that already have 2.3 or enough internal memory on them, this will all start in last August an early September for the first two droids listed... and others will soon follow suit, the only question is do you want you bootloader to come unlocked stock? Or will you buy it locked and be able to sit around and wait for your device to get an update to do so?? LOL

thats why my phone couldnt flash back to 2.3.2..(?)
I live in singapore.. phones are not carrier specific.. so does that mean my BL was unlocked even before I used gingerbreak?

I know this doesnt pertain to the play per se, but maybe you should add that, with nand locked devices, an unlocked bootloader is required to acheive full root, just incase someone with another device googles this question and ends up here

pros and cons of unlocked bootloader
Pros/Cons of rooting WITHOUT unlocking bootloader?
Since being interested in rooting my N1 I've been googling a lot but it's still somewhat confusing. One of the things that's making me hesitent is the idea of permanently (as of the date of this post) unlocking the phone and thus clearly/visibly voiding the warranty.
I've recently stumbled upon instructions for rooting without unlocking the bootloader? Am I correct in assuming this would make the phone appear (no unlock icon) to be unmodified? Also, does this mean one could fully reverse the rooting process and go back to fully stock google signed roms with OTA updates etc (essentially reverting it back as if it were never modified)?
It would seem this would be preferable to any method involving the unlocking of the bootloader. Are there any disadvantages of this? Any increased risks by NOT unlocking the bootloader? Is there a reason why most people have gone the rout of unlocking the bootloader?
My plan is simply to have root access to run setcpu on the stock FRF91 rom. As of now, I'm not interested in other ROMs (baby steps).

tommyinhi27 said:
Pros/Cons of rooting WITHOUT unlocking bootloader?
Since being interested in rooting my N1 I've been googling a lot but it's still somewhat confusing. One of the things that's making me hesitent is the idea of permanently (as of the date of this post) unlocking the phone and thus clearly/visibly voiding the warranty.
I've recently stumbled upon instructions for rooting without unlocking the bootloader? Am I correct in assuming this would make the phone appear (no unlock icon) to be unmodified? Also, does this mean one could fully reverse the rooting process and go back to fully stock google signed roms with OTA updates etc (essentially reverting it back as if it were never modified)?
It would seem this would be preferable to any method involving the unlocking of the bootloader. Are there any disadvantages of this? Any increased risks by NOT unlocking the bootloader? Is there a reason why most people have gone the rout of unlocking the bootloader?
My plan is simply to have root access to run setcpu on the stock FRF91 rom. As of now, I'm not interested in other ROMs (baby steps).
Click to expand...
Click to collapse
The N1 is made by HTC, generaly with htc devices, flashing a stock rom, will re-lock the bootloader, If you decide just to root, you will need a custom kernel before you can O/C All that unlocking the bootloader does is 2 things, It will security unlock the nand (on nand locked devices) allowing r/w access to read only partitions, and it allows you to issue fastboot commands to your device, the main reason alot of play owners went down the unlocking the bootloader path, is that atm it is the only way to flash custom roms other devices, have found sneaky ways to push a custom recovery without unlocking bootloaders, and thus do not need one to flash a custom rom

AndroHero said:
I know this doesnt pertain to the play per se, but maybe you should add that, with nand locked devices, an unlocked bootloader is required to acheive full root, just incase someone with another device googles this question and ends up here
Click to expand...
Click to collapse
I'm not too knowledgeable about the whole Nand thing, so I think you could give a much better explanation about it. I'll include it then

whoa whoa whoa!!!! i achieved root on 2.3.3 with no prob using superoneclick v2.3.3. it works beautifully!

Yes, but you're replying to a thread that's 8 months out of date too!
Sent from my R800x using XDA

Lol. I know, but I've been trolling the site, and I think it may need a bit of new info so someone doesn't follow the steps here now that a better method has been found.
Sent from my R800at using XDA

isavegas said:
Lol. I know, but I've been trolling the site, and I think it may need a bit of new info so someone doesn't follow the steps here now that a better method has been found.
Sent from my R800at using XDA
Click to expand...
Click to collapse
why not just stop bumping heavily old threads? then they can rest in piece
and nobody would care
the information thatit's outdated is alreada given in 1st post.
u also could ask a mod to close this as its outdated...

Hey, this thread may be outdated, but it's not my fault if someone necros old threads. Just let it die.

question
can i flash custom roms in a locked bootloader?

yes
big txmer said:
can i flash custom roms in a locked bootloader?
Click to expand...
Click to collapse
only stock gb ones nothing else

[Q] installing custom ROM on G2 [iPhone Refugee Thread]

Hello fellow XDA'ers,
I recently purchased the LG G2 and this is my first android phone. I'm coming from an iPhone 5 (for a multitude of reasons that are not applicable to this thread). I wanted to start this thread for people like myself who have no idea on how to install a ROM on an android device. There are various ROMs being released (verizon and ATT) and I would love a general walk through on how to install. Can anyone experienced point me in the right direction or offer any advice? Thanks in advance!

mjfan82 said:
Hello fellow XDA'ers,
I recently purchased the LG G2 and this is my first android phone. I'm coming from an iPhone 5 (for a multitude of reasons that are not applicable to this thread). I wanted to start this thread for people like myself who have no idea on how to install a ROM on an android device. There are various ROMs being released (verizon and ATT) and I would love a general walk through on how to install. Can anyone experienced point me in the right direction or offer any advice? Thanks in advance!
Click to expand...
Click to collapse
There aren't really any custom ROMs out for the G2 yet, just a couple of debloated ROMs (stock, plus root and minus carrier bloatware). Better ROMs will come, but it will be a little while. The G2 is just too new right now to have much out for it.
For a beginner, a few things you should keep in mind before rooting or installing a custom ROM:
* Be absolutely sure that what you're doing will work on your device before you do it. For instance, don't install a recovery image for an AT&T phone on a Verizon phone, unless you want to turn it into a paperweight.
* Read instructions carefully before you do anything. You should at least have some idea of what you're doing, so that in case something goes wrong, you'll at least have a chance of recovering. Don't just blindly follow instructions and hope you don't brick your phone.
* This *will* void your phone's warranty. If your phone dies after doing this (whether it's related to this or not), and you try to do a warranty exchange, they'll respond with something that is the same in English, Italian, and Spanish -- "No." On a related note, you are taking some risk by doing this. You could possibly mess up your phone. You could do things right, and an over-the-air update could conflict with what you've done and then mess up your phone. This is a risk you assume, not the developers of whatever you're trying to do.
* These forums, as well as #lg-g2, are for help. If you're not sure about something, ask. It's better to ask than to lose $600 because you incorrectly assumed that something would work.
Overall, rooting and ROMming your phone does give you more control. Just know what you're getting into.

antinorm said:
* This *will* void your phone's warranty. If your phone dies after doing this (whether it's related to this or not), and you try to do a warranty exchange, they'll respond with something that is the same in English, Italian, and Spanish -- "No." On a related note, you are taking some risk by doing this. You could possibly mess up your phone. You could do things right, and an over-the-air update could conflict with what you've done and then mess up your phone. This is a risk you assume, not the developers of whatever you're trying to do.
Click to expand...
Click to collapse
There is risk involved yes, but it doesn't just straight up void your warranty in every situation. Depending on the carrier you are with and their RMA process you can get a perfect replacement with no hassle every time, and the carriers that do give trouble still have a small chance of going ahead with a replacement anyway depending on the tech you get. Many times for certain hardware issues it wont matter if you are rooted or not and you can still get a replacement as well. But choosing to unlock your device and do custom software for it you do have to accept responsibility that you could do something to break you device and that is your fault, not the manufacturer.
(skips these couple sections of text for just custom recovery and ROM install)
As for specific instruction, I cant really help much there. The instructions didn't really work well for me in the TWRP thread on XDA for installing, as there is nothing available when using Goo Manager, despite what that retarded thread says. I found better info on Rootz Wiki through a Google search on what to do, and even that was a bit wrong and I had to use some common sense to do things the right way. That common sense only comes from knowing how to use the command line and knowing how ADB commands work though, someone new to the process wont know that for themselves.
Looking over this thread for the newest info it looks like pretty much everything in this video should be correct and the download link for installing root should have everything you need:
http://www.youtube.com/watch?v=Y45SXPRb31o&feature=player_embedded
http://downloads.codefi.re/thecubed/lg_g2/root/ioroot6.zip
That gets root access on your device. You may or may not even want to do that. That installs root into your ROM you are currently running (stock), but you want to install a custom ROM and your custom one probably already is rooted to begin with. What you most likely want to do is just go straight to installing the drivers to connect your phone properly and use ADB to send ("push") files to your phone, then use something called "Loki" to bypass the locked bootloader and flash a custom recover to your phone. From there you can install ROMs perfectly easily. You can follow this guide in the link, but it doesnt give you links to the phone and ADB drivers you will need:
http://rootzwiki.com/news/loki-bootloader-bypass-twrp-recovery-come-att-verizon-lg-g2/
Right now there is not really anything but Clean ROM available, which is the stock OS that has a bunch of the "bloated" and unnecessary LG and ATT system apps un-installed. It cleans things up a lot and gives you a much better experience. In the future hopefully we will see some AOSP based ROMs that have a lot of the good features like "knock on", and those ROMs will be best since they dont have any of the bloat that the LG ROM has, and the AOSP based stuff gets a lot better mods to them and offers far better customization and tweaking.

Thanks for the info! I did not know that a most ROMs come rooted. So basically, I would not need to root then install a ROM?
I have an AT&T G2 so I would be installing the Clean ROM posted in the developers section. I would love the opportunity to debloat the phone and it seems like this is the best option currently. Enigma, are you saying that the knock on and off feature does not work with this ROM?

Installing ROM
Hello everyone,
I have rooted and have TWRP with the verizon phone.
How do i move a ROM into a phone so i can install it?
I have already made a backup of the current phone with everyone and copied it to the computer.
Let me know,
Thank You

calirage2k said:
Hello everyone,
I have rooted and have TWRP with the verizon phone.
How do i move a ROM into a phone so i can install it?
I have already made a backup of the current phone with everyone and copied it to the computer.
Let me know,
Thank You
Click to expand...
Click to collapse
Put your phone in USB debugging mode under developer tools...hook up the micro usb to your phone and move the zipped ROM to the root of your internal phone storage.

calirage2k said:
Hello everyone,
I have rooted and have TWRP with the verizon phone.
How do i move a ROM into a phone so i can install it?
I have already made a backup of the current phone with everyone and copied it to the computer.
Let me know,
Thank You
Click to expand...
Click to collapse
Or enable wireless storage via the notification drop down, you can now approach your device via Wi-Fi lan and upload whatever (it makes your device into a network drive)
Sent from my LG-F320L using XDA Premium 4 mobile app

What happens to the One Plus 5 if I unlock the bootloader?

Greetings! I have just ordered my new OP5 and now I hat a Sony Z5. If you were Xperia users, you know that after unlock the bootloader, you lost permanently (or you did a backup before) a speial partition where Sony put very important data for the device (like the camera quality for example).
I know myself ad I have fear that if I unlock the bootloader I lose some imoprtant data or something so my question is: which consequences do you have if you unlock the OP5? Do you lose something important like in the Sony devices or not?
Thank you very much and sorry of there's a thread where you must post this questions :crying:

Unlocking the bootloader basically resets your phone and you lose data plus any apps you installed but you don't lose anything like what you are describing --you just need to set up your phone again. The biggest problem you would encounter is that Android Pay probably wouldn't work unless you flash a custom kernel. Default Android behavior is that if you unlock the bootloader you automatically can't pass Safety Net and I don't think OnePlus or any other phone maker that runs Android is officially allowed to change that behavior --which is why you need a custom kernel to still pass Safety Net.

Oh, and you have a screen at boot that pretty much states that the bootloader has been unlocked.
Not sure why we still have to deal with this as this has been masked on a few other model phones, like the Axon 7, and with all the dev's available for the one+ it's surprising this hasn't been sorted for us too...

So far after unlocking my bootloader and rooting with magisk, android pay is unavailable. I didn't use it much anyways as out here in rural country midwest (USA) it isn't very widespread. As far as warranty goes it is still in effect and 1+ also has a guide for restoring your phone to stock too. It's definitely a great phone for customizing and trying new things with. I didn't apply a new ROM though as most ROMs available at this time are still a work in progress and not what I deem entirely stable. I'm sure someone here will contradict me, but I'm doing fine with what I've got so far.

prozo said:
So far after unlocking my bootloader and rooting with magisk, android pay is unavailable. I didn't use it much anyways as out here in rural country midwest (USA) it isn't very widespread. As far as warranty goes it is still in effect and 1+ also has a guide for restoring your phone to stock too. It's definitely a great phone for customizing and trying new things with. I didn't apply a new ROM though as most ROMs available at this time are still a work in progress and not what I deem entirely stable. I'm sure someone here will contradict me, but I'm doing fine with what I've got so far.
Click to expand...
Click to collapse
Works for me on stock 7.1.1....
Sent from my OnePlus5 using XDA Labs

Essentially, if you're happy with how your phone is working, there is no need to unlock the boot loader and root. There is no point to unlock the bootloader and then not root .
Unlocking the bootloader allows custom recoveries and roms/kernels to be installed onto the phone.
It also allows such things as substratum, xposed and magisk to be installed as these apps generally require root priveliges that aren't available with a locked bootloader and being unrooted.
Customisation can be easier, Bloat can be removed instead of just frozen and tweaks can be applied BUT there is a downside too as this has effectively breached Googles security and will break certain apps (mostly banking but there has been reports of streaming apps being affected too on other forums).
Luckily as you have the One+5 you can, if you wish, revert to stock and relock the bootloader thus reverting all changes, unlocking most other phones which will destroy any hope of getting warranty or a relocked bootloader.
Just be sure you HAVE got it back to stock 1st however as having anything different, (kernel,rom or recovery) may very well brick your device once you relock the bootloader.

prozo said:
So far after unlocking my bootloader and rooting with magisk, android pay is unavailable. I didn't use it much anyways as out here in rural country midwest (USA) it isn't very widespread. As far as warranty goes it is still in effect and 1+ also has a guide for restoring your phone to stock too. It's definitely a great phone for customizing and trying new things with. I didn't apply a new ROM though as most ROMs available at this time are still a work in progress and not what I deem entirely stable. I'm sure someone here will contradict me, but I'm doing fine with what I've got so far.
Click to expand...
Click to collapse
You need to flash a custom kernel to pass safety net. It won't work with the stock kernel. Blu Spark seems to be the official unofficial kernel and you could easily flash that one and forget it as it is pretty fast and smooth as is. Boeffla kernel is built for stability and is rock solid but if you don't tweak the settings at all you might notice a slight drop in performance from stock. Either one will allow you to pass Safety Net and can improve the speed and performance of the phone over stock. Boeffla also includes a fix for the auto brightness making the phone too dim by allowing you to set a minimum screen brightness that it won't go below.

If I only root the device, will I be able to use Android Pay?

Struziu said:
If I only root the device, will I be able to use Android Pay?
Click to expand...
Click to collapse
You can't root without unlocking the bootloader

Hey,
I'm aware this is thread is pretty old, but I'm wondering how things are now? It's been quite some time since I've touched any bootloaders or custom roms and I'm interested in testing android 11 with my op5. What are the downsides with unlocking your bootloader and installing a custom rom?
Google pay not working?
Banking apps not working?
Netflix not working?
I tried searching this forum and googling around and I really could not find any answers. And none of the custom rom threads I checked mention safetynet.

Verizon Galaxy S7 Edge: Removing bloatware after 1-Clk-Root

Just picked up a carrier unlocked Verizon Galaxy S7 Edge model SM-G935V.
Now that I finally have a model which seems like it should be relatively easy to root, I would prefer to learn to do it using a PC ie flashing ROM, but I have no PC*access*right now.
My main question is:
After rooting my phone using a 1-click root method, will it be relatively easy for me to un-install ALL bloatware & eventually end up with a phone that's running just as efficiently as it would if I had picked out and flashed a good stripped down ROM using a PC instead of some 1-click method?
I'm also considering purchase and use of Super-sume Pro (if the job is done with Kingroot).
Any advice AT ALL regarding what I hope to do would be greatly appreciated... and jic it helps here s a little of my background:
I have NO successful experiences using TWRP or the like w other phones.. although I believe I came close!!... my last few phone picks turned out to be models which were pretty much impossible to root (locked bootloader was the common culprit best I could understand).... Otherwise I think I'd have been able to do at least 1 previous model the flash-rom way.
I DO have A lot of general experience w PCs and have successfully rooted a few phones using 1 click Android software such as Kingroot, but at that time I did not fully understand or hope to remove bloatware to cool battery or otherwise dial in best performance.
It's been at least 3 years since I last performed a 1 click root on any phone.
Thanks in advance for any advice or assistance... I really appreciate everyone & everything at XDA.

Best advice, get/borrow a laptop and follow the instructions in this thread https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 to see about rooting your S7e. All those "1-click" options never worked for me. With the method in the above link, I can root my S7e in under 15min.
1) First and foremost, what is the current software version your S7e is running? example= G935VVRS4CRI1. IF the 5th digit from the RIGHT is the letter "B" stop! You can't root. If it is the letter "A," or a number, you are good to go.
2) even with root, there is no flashing of ANY custom ROM's. Yes, you can debloat and make some changes, but with the godd**mn locked bootloader the options are limited. Rooting does not unlock the bootloader, therefore there is no TWRP, Magisk, etc.
Others with experience regarding those 1-click methods may chime in with their advice/experience. But none of those instant methods ever worked for me.
Good luck.

SkylineDriver said:
Best advice, get/borrow a laptop and follow the instructions in this thread https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 to see about rooting your S7e. All those "1-click" options never worked for me. With the method in the above link, I can root my S7e in under 15min.
1) First and foremost, what is the current software version your S7e is running? example= G935VVRS4CRI1. IF the 5th digit from the RIGHT is the letter "B" stop! You can't root. If it is the letter "A," or a number, you are good to go.
2) even with root, there is no flashing of ANY custom ROM's. Yes, you can debloat and make some changes, but with the godd**mn locked bootloader the options are limited. Rooting does not unlock the bootloader, therefore there is no TWRP, Magisk, etc.
Others with experience regarding those 1-click methods may chime in with their advice/experience. But none of those instant methods ever worked for me.
Good luck.
Click to expand...
Click to collapse
Skyline,
Thank you for taking the time. Much appreciated. Luckily I already found out about the software version issue and I'm looking at the number 4, so that potential roadblock isn't one
Let me try to understand exactly what you said towards the end of your reply, though.
Are you saying that even if I use a PC and avoid any 1 click method that I will not have any option to flash a custom ROM? I could have sworn I saw a thread a few nights ago somewhere here at XDA which required use of a PC, specifically for my phone model and it described the altered OS or ROM as being as simplified as it gets, devoid of all Verizon bloatware. Maybe I am referring to it in correctly when I say custom ROM, I'll look for said post to see what I may be remembering incorrectly.
I have personally had great experience w 1-click methods in the past, @ least 4 different phones (older Samsung, LG).. but I have NEVER tried 1-click w a phone thats truly important... as in important enough to seriously worry about stolen IMEI, keylogger or other malware, etc..
I want a perfectly clean, safe "out of the gates" root on this phone, so I'm willing to wait to make sure it's done the proper/best way on my FIRST attempt.
Looks like the thread is already talking me out of using 1-click (might have known deep down that needed to happen lol).
Anyway thanks again for your advice.
When I finally do get to rooting it, I'll post the details and overall experience info here.

Whatever you do, DO NOT UPDATE to the latest software version.
With root, you can debloat all you want. I have next to nothing running on my phone (goodbye Google "services"). You just can not flash any custom (non-official Samsung) ROM's such as LineageOS, Calvioppe, etc... thanks to that damn locked Crapdragon. Much as I love my S7e, when it dies, it will be my last Samsung for that reason alone.
If you follow the steps outlined in the above linked thread, you should be able to root 1-2-3. I have been rooted since it became available and have had zero issues. It will require a PC/ laptop but it is reliable and verified working.
Good luck with your project.

Canthigaster said:
Skyline,
Thank you for taking the time. Much appreciated. Luckily I already found out about the software version issue and I'm looking at the number 4, so that potential roadblock isn't one
Let me try to understand exactly what you said towards the end of your reply, though.
Are you saying that even if I use a PC and avoid any 1 click method that I will not have any option to flash a custom ROM? I could have sworn I saw a thread a few nights ago somewhere here at XDA which required use of a PC, specifically for my phone model and it described the altered OS or ROM as being as simplified as it gets, devoid of all Verizon bloatware. Maybe I am referring to it in correctly when I say custom ROM, I'll look for said post to see what I may be remembering incorrectly.
I have personally had great experience w 1-click methods in the past, @ least 4 different phones (older Samsung, LG).. but I have NEVER tried 1-click w a phone thats truly important... as in important enough to seriously worry about stolen IMEI, keylogger or other malware, etc..
I want a perfectly clean, safe "out of the gates" root on this phone, so I'm willing to wait to make sure it's done the proper/best way on my FIRST attempt.
Looks like the thread is already talking me out of using 1-click (might have known deep down that needed to happen lol).
Anyway thanks again for your advice.
When I finally do get to rooting it, I'll post the details and overall experience info here.
Click to expand...
Click to collapse
SkylineDriver said:
Whatever you do, DO NOT UPDATE to the latest software version.
With root, you can debloat all you want. I have next to nothing running on my phone (goodbye Google "services"). You just can not flash any custom (non-official Samsung) ROM's such as LineageOS, Calvioppe, etc... thanks to that damn locked Crapdragon. Much as I love my S7e, when it dies, it will be my last Samsung for that reason alone.
If you follow the steps outlined in the above linked thread, you should be able to root 1-2-3. I have been rooted since it became available and have had zero issues. It will require a PC/ laptop but it is reliable and verified working.
Good luck with your project.
Click to expand...
Click to collapse
Thanks again for the warning about no updating... I am WELL aware of this, my friend.
Take a look at this thread... it really looks to me as if this person is talking about flashing a ROM on the S7 Edge, no?
https://forum.xda-developers.com/s7...a-evolution-x-samsung-galaxy-s7-edge-t4058837
That's only 1 of at least 2 or 3 similar threads that I've been having a look at lately...

If you look closely, that is for the Exynos version of the S7e. Verizon uses the Snapdragon (ie. Crapdragon) processor which has a locked bootloader for US models.

Ok I get it completely... one last teeny tiny bit of hope- I purchased mine Unlocked by manufacturer. Could that possibly extend beyond carrier unlock and (maybe maybe please just possibly) mean my bootloader is unlocked?
Went out of my way to make sure it was unlocked by MANUFACTURER, not SELLER for obvious reasons. Had no knowledge about chipset... dammit there's always something to miss no matter how much prep one tries to do!

Unlocked just means that the phone is able to be activated on any carrier ie. not specifically locked to only Verizon.
Only the Exynos and Chinese Snapdragon can be bootloader unlocked. As mentioned, I love my S7e, and will use it until it dies, but I seriously doubt I will get another Snapdragon Samsung that is locked down tighter than Ft. Knox.
Good luck...

S8 Snapdrangon bootloader Q's

hi so i have a few things id like to talk about. i was wondering why it is not possible to port aosp roms to s8 snapdragon? givin its the same android version. also when i was messing around when rooting my s8 i saw that the software i had installed in the steps i went into settings and saw that i could enable oem unlock it worked and whenever i go back to that software its still enabled however i could not use any fastboot commands still. also i flashed twrp (not safe strap already have that) and now my base recovery does not show up....

kadenball said:
hi so i have a few things id like to talk about. i was wondering why it is not possible to port aosp roms to s8 snapdragon? givin its the same android version. also when i was messing around when rooting my s8 i saw that the software i had installed in the steps i went into settings and saw that i could enable oem unlock it worked and whenever i go back to that software its still enabled however i could not use any fastboot commands still. also i flashed twrp (not safe strap already have that) and now my base recovery does not show up....
Click to expand...
Click to collapse
Aosp roms requires a custom kernel to work, this requires:
1, unlocked bootloader(not possible on the snapdragon variant)
2, a custom recovery (not possible due to locked bootloader)
Just using the oem unlock option does not unlock the bootloader, more steps are required for most phones in order to unlock the bootloader, if it was that easy it would have been exploited by now, most of the guides on the snapdragon version mention that the bootloader is not unlockable.
You more than likely will need to restore the recovery through odin or something,

sofir786 said:
Aosp roms requires a custom kernel to work, this requires:
1, unlocked bootloader(not possible on the snapdragon variant)
2, a custom recovery (not possible due to locked bootloader)
Just using the oem unlock option does not unlock the bootloader, more steps are required for most phones in order to unlock the bootloader, if it was that easy it would have been exploited by now, most of the guides on the snapdragon version mention that the bootloader is not unlockable.
You more than likely will need to restore the recovery through odin or something,
Click to expand...
Click to collapse
Thanks ya I fixed it! And ya I understand there are additional steps to doing this that's why I mentioned fastboot. If you could guide me in a direction to potentially learn more about the kernals and how they work or what I would need to be good at to exploit download mode or knox whatever is required to potentially exploit the bootloader I would not give up on it im fine with wasting my time. I had recently talked to Sam help chat and they told me someone could unlock the bootloader for me (a phone company near me) I talked to a guy over the phone that said it could be possible bc they have the Samsung tools to do so but he told me to call the next day because the other tech knew more then him, so I called the next day and he said they could do it but they would get in trouble for doing so. My plan is to go in when the guy that doesn't know much is working ? and get him to unlock it. Hopefully then I could upload the software here and free the snapdragon slaves!!! If your interested in the conversations I had with Samsung and this other company I could upload the screen shots thank you for your reply!

kadenball said:
Thanks ya I fixed it! And ya I understand there are additional steps to doing this that's why I mentioned fastboot. If you could guide me in a direction to potentially learn more about the kernals and how they work or what I would need to be good at to exploit download mode or knox whatever is required to potentially exploit the bootloader I would not give up on it im fine with wasting my time. I had recently talked to Sam help chat and they told me someone could unlock the bootloader for me (a phone company near me) I talked to a guy over the phone that said it could be possible bc they have the Samsung tools to do so but he told me to call the next day because the other tech knew more then him, so I called the next day and he said they could do it but they would get in trouble for doing so. My plan is to go in when the guy that doesn't know much is working ? and get him to unlock it. Hopefully then I could upload the software here and free the snapdragon slaves!!! If your interested in the conversations I had with Samsung and this other company I could upload the screen shots thank you for your reply!
Click to expand...
Click to collapse
I've never dabbled in making kernels or anything so I'm pretty useless with that. The phone has been out for over 3 years now and as of yet there is no software method to unlock the bootloader, android devs would have figured that one out by now if it was possible, if it is possible then maybe there some extra hardware thats required to unlock the bootloader, I honestly don't know enough, I'm experienced enough to know to do certain things but I don't know the ins and out of how bootloader are coded, how the instructions are carried out. But it would defo be interesting to see if they do this for you.

sofir786 said:
I've never dabbled in making kernels or anything so I'm pretty useless with that. The phone has been out for over 3 years now and as of yet there is no software method to unlock the bootloader, android devs would have figured that one out by now if it was possible, if it is possible then maybe there some extra hardware thats required to unlock the bootloader, I honestly don't know enough, I'm experienced enough to know to do certain things but I don't know the ins and out of how bootloader are coded, how the instructions are carried out. But it would defo be interesting to see if they do this for you.
Click to expand...
Click to collapse
Ya thanks man when I talked to the inexperienced tech guy he said I could come in and we could try but I didn't want to drive there and waste my time ? but the experienced dude said I could probably find another repair place that would do it (figured it's another one of their shops he was hinting at as there are a few around me) so I will attempt to do this and hopefully some how it works and I can upload the software here not sure if flashing it would unlock anyone elses bootloaders as I expect it to be some sort of key like the HTC phones used to require and is unique to each device. When I got that oem to appear I was trying anything and everything in adb and fastboot as I suspected if we could glitch the phone in fastboot mode we could unlock it lol at least that's what I hoped for, tried upload mode kernal panic the 3 different download modes and tried to replace the Samsung download mode driver and flash the fastboot Android driver on top of it but my lack of knowledge on these things hindered me from making any progress but I believe there's a exploit in this root software that was copyed from the s9 and simply devs don't want to waste there time because they believe it is impossible. I've seen much hard thing accomplished in this dev sight hopefully the right person can figure it out and Is motivated by this post or point me in the right direction ? thanks if you read all this if I get it unlocked you will def see another post lengthy post ?