I'm looking at buying an international Exynos N10, and running it on Verizon in the US.
My purposes in doing so are to either use root to make the phone as bulletproof as possible, or flash a rom onto it that focuses on security and privacy. Been rocking iphones for a while (last phone I rooted and rommed was the GS4, then Verizon started locking all the snapdragon bootloaders.
Anyway, there seems to be a wide range of available models to choose from. Is there one I should gravitate towards for my specific purposes?
I seem to see N975F mentioned a lot.
all the US snapdragons have the bootloader locked
the china model snapdragon doesn't
the F model doesn't
the question is can you achieve what you want w/o rooting the phone?
some of the advantages for rooting might be possible to be achieved also w/o root via ADB commands
read and try to get as much info as possible to be able to understand the ups and downs of rooting or not rooting
also consider if you want to sell the phone afterwards - how rooting would affect that sale
also a hint - unlocking the bootloader will "burn" the knox fuse which is irreversible - no more automatic OTA, only manual and a few specific apps will not work
w41ru5 said:
all the US snapdragons have the bootloader locked
the china model snapdragon doesn't
the F model doesn't
the question is can you achieve what you want w/o rooting the phone?
some of the advantages for rooting might be possible to be achieved also w/o root via ADB commands
read and try to get as much info as possible to be able to understand the ups and downs of rooting or not rooting
also consider if you want to sell the phone afterwards - how rooting would affect that sale
also a hint - unlocking the bootloader will "burn" the knox fuse which is irreversible - no more automatic OTA, only manual and a few specific apps will not work
Click to expand...
Click to collapse
also rooting will kill the private folder. Privacy can be achieved with debloating for example and private DNS / VPN
Rotting will seriously damage the resale and future official support as well as the safety net and payments.
Related
Hello,
I have had my G4 H815 locked to UKEE for a good few months now and I have been holding off on rooting as the official way of unlocking the bootloader I believe breaks the DRM keys and it was hinted that there was a small possibility than a nicer way may come about. It's not looking like that at the moment and I am now clucking to get my root apps and freedom back.
I have had and HTC Desire, Samsung S2 and Xperia Z1 all rooted many times and flashing multiple different things etc so I am by no means new to rooting but I am not a technological whizz kid and looking at the root methods for this, as with every new phone it seems, rooting methods are getting more difficult. My questions are;
1. Can anyone tell me what they have experienced not working when the bootloader gets unlocked? I understand it may just be video streaming? Can anyone confirm the likes of Netflix etc won't work? Any other apps / ill effects? I assume YouTube still works? I currently use Barclays banking app, that didn't work on old phone while that was rooted, I'm assuming with the bootloader unlocked it will never work again on G4?
2. Is Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks the best root method to use? Or is it, as I guess [ROOT] TMO/VZW/ATT/SPRINT/INTL Root your LG G4 with Low Effort Root! the best to use? Or is there another you suggest that is easier / better / harder to destroy my phone?
3. Slightly O/T but being on EE they are extremely stingy with updates so I am still running 10C, I have seen about FW up to 10H or more. Is there somewhere that has the change logs of these different firmwares?
"I believe breaks the DRM keys"
This is true for the Sony Xperia devices, but not really for others that I know (Samsung S6 and HTC M9 included). I have unlocked the device on day 2, and everything works: YouTube, My own banking apps (they give me a warning tough that I am rooted, but working without issues), all camera functionality, video streaming (no Netflix here to check tough), IRDA, BT etc.
The banking checks for root (if you have SU access and not if the bootloader is unlocked), this can be hidden with the RootCloak app, but depends on the banking app itself. As I said, mine warns me that I am rooted, but everything works.
As for which is the easiest method, I prefer flashing SuperSU package with TWRP recovery, since the bootloader is unlocked. It's safe and failproof.
The other methods you listed are mainly for devices, which can't have their bootloaders unlocked.
Thanks. I know the Xperia devices broke drm keys so that the bravia engine etc didn't work. But at least with them you could backup drm keys and relock the boot loader. I read somewhere that the g4 breaks the keys but it was only really streaming type service's that may be effected.
Yea Barclays just straight up won't work and there rootcloak doesn't have an exploit to hide root from that as far as I could find.
I read somewhere on this earlier too that there is an unofficial unoficial bootloader unlock being worked on sounds like not far off. May just wait and see if that way comes to light soon and if it's a safer way and revertible for warranty purposes etc as it can't be done after accepting an update looks like.
Sent from my LG-H815 using Tapatalk
Hello, my name is WatchersGrim.
I have worked with coding for a little while back in the day and use to root and jailbreak devices for a long time. Going from my old Galaxy J3 from sprint to Galaxy S9, I was excited to finally do root on better hardware. Then came around to finding out that US models with Snapdragon processors don't allow OEM unlock and are not able to be rooted. This started a dilemma in my head. How are we able to fix this and work around it. So one, many of us know that something will probably change a few years down the line with samsung as TWRP recovery has been found to be working on snapdragon processors in different countries. Secondly, without TWRP, is it possible to trip a javascript object(knowing that most of android OS coding is done in javascript) to enable the OEM object to be able to have access.?Possibly could work but may need a different method to do so(I.E. triggering the effect with a custom file that loads on a SDCARD the moment the phone reads it, or creating a program along the line of ODIN to do the same effect.). Thirdly, is it possible to manipulate the hardware itself to allow third party hardware to manipulate the system? If doing so, will it cause a fault in the internal system? I know it would void warrenty but I do not know if it has a security fault that locks the system when dealing with hardware tampering.
I just want to see what you guys think and see if we can brainstorm idea's to help these great dev's!
can you do anything to trick android into running a modifyable file as root?
Hi everyone,
So it has been a year since I have my S9 and still there is no exploit released to the public yet, and I understand that Samsung really locked down the security on their US variants.
On the Samsung S6, what I used to have, had an exploit where you can only have shell root access in terminal by modifying the boot.img and flashing it via odin, and thats using Android Nougat for root.
Could this perform a similar function to the S9? Like at least have an exploit where you can have shell root via ADB?
If not, is there any status on the G960U in terms of rooting?
AndroidFan16 said:
Hi everyone,
So it has been a year since I have my S9 and still there is no exploit released to the public yet, and I understand that Samsung really locked down the security on their US variants.
On the Samsung S6, what I used to have, had an exploit where you can only have shell root access in terminal by modifying the boot.img and flashing it via odin, and thats using Android Nougat for root.
Could this perform a similar function to the S9? Like at least have an exploit where you can have shell root via ADB?
If not, is there any status on the G960U in terms of rooting?
Click to expand...
Click to collapse
modifying the boot.img will cause the signature from sammy to fail as would anything else that isnt stock and properly signed.
No dice man. Still nada on the U devices. You do know that root is becoming less and less necessary, right? What are you looking to get done with root?
youdoofus said:
modifying the boot.img will cause the signature from sammy to fail as would anything else that isnt stock and properly signed.
No dice man. Still nada on the U devices. You do know that root is becoming less and less necessary, right? What are you looking to get done with root?
Click to expand...
Click to collapse
Ohh... Well that's kind of a dud.
I always want root mainly for more control with my device, for example, uninstalling bloatware (this way if I dare to factory reset my device, I dont need to disable the apps I dont want after performing a factory reset, unless if I have to reflash the rom).
Another thing is controlling the CPU's frequency speed (or governor) for either saving battery or pump out more performance, which is technically the #1 thing I want as root.
I also want to disable OEM updates from forcing me to update my phone after 10 defers (I found a bug to bypass this and it's by using the notification draw and click on the setting button).
I also want to configure access of changing the 4G LTE bands (which changing the config file in the /efs partition, which I assume, is locked without su access).
Like I have mentioned, the shell root is basically minimum for me, and I wouldn't mind on that. HOWEVER, if all that I have mentioned can be performed without root and have a similar function of doing these, please let me know.
AndroidFan16 said:
Ohh... Well that's kind of a dud.
I always want root mainly for more control with my device, for example, uninstalling bloatware (this way if I dare to factory reset my device, I dont need to disable the apps I dont want after performing a factory reset, unless if I have to reflash the rom).
Another thing is controlling the CPU's frequency speed (or governor) for either saving battery or pump out more performance, which is technically the #1 thing I want as root.
I also want to disable OEM updates from forcing me to update my phone after 10 defers (I found a bug to bypass this and it's by using the notification draw and click on the setting button).
I also want to configure access of changing the 4G LTE bands (which changing the config file in the /efs partition, which I assume, is locked without su access).
Like I have mentioned, the shell root is basically minimum for me, and I wouldn't mind on that. HOWEVER, if all that I have mentioned can be performed without root and have a similar function of doing these, please let me know.
Click to expand...
Click to collapse
youre not gonna get true debloating with this, but if you flash the U1 firmware with an unknown CSC, it wont install any carrier bloat and is very much akin to a GSI. Nice and stripped down. Over/unclocking, yup, you need root. I never see people talking about clockin the processor anymore tho as the new kernels are so adaptive and are written quite well. Ive also never not wanted to install an OEM update, so im not sure how to stave those off, or if ite even possible. To change the bands your phone is utilizing, you just need access to the special menu from the dialer.
Do you know what's the dialer code to access the service menu on the S9 on Verizon?
I'm pretty sure its locked but it's worth a try.
I came across this post on GitHub
https://github.com/topjohnwu/Magisk/issues/2534
I wanted to ask if I should continue using root or just relock my phone ?
tanzeel.ahmed1306 said:
I came across this post on GitHub
https://github.com/topjohnwu/Magisk/issues/2534
I wanted to ask if I should continue using root or just relock my phone ?
Click to expand...
Click to collapse
Unlocking your bootloader and rooting your devices is a choice that you and only you can make. There are always risks when modifying your devices. When you unlock the bootloader on most devices it will void your warranty unless stated otherwise by the manufacturer.
When it comes to root access there is always a chance for things to stop working. That is why it is up to you to do your research and make an informed decision before taking any action.
To some people, including me, an unlockable bootloader and gaining root access over a device is a must. I am paying for it and I want to use my devices how I see fit.
If you are concerned about an issue that may arise because you have an unlocked bootloader and root access I always try to look at it from both sides. Why did I unlock the bootloader? Why did I root? Am I able to do what I intended to do or not?
Sent from my OnePlus HD1907 using XDA Labs
tanzeel.ahmed1306 said:
I came across this post on GitHub
https://github.com/topjohnwu/Magisk/issues/2534
I wanted to ask if I should continue using root or just relock my phone ?
Click to expand...
Click to collapse
I'm kinda in the same boat. While I don't use GPay that often (and I can currently use it through Magisk), occasionally it would be nice for it to work without issue. However, the main reason I root is so that I can manually edit my HOSTS file to block ads.
Like fast69mopar mentioned, it's an individual preference. What do you gain by unlocking the bootloader and rooting?
In my opinion, the OP7T is a fantastic phone right from the get-go. So was the OP6T. Both phones I used for almost a full week before unlocking and rooting.
Got the OP7T a month ago and was faced with the same decision. All phones since Samsung Galaxy I have rooted.
Decided not to root the OP7T. So far couldn't be happier. Maybe missed it once. Everything working without issue is nice.
As for Ads.
Built in Private DNS in Android 10 with dns.adguard.com works pretty damn good.
I'm rooted, using magisk and edxposed with aosip. Definitely no loss of function comparing to stock. I don't use Google pay, but Samsung pay, bank apps, snapchat, everything works. Currently magisk and edxposed could be hidden without any loss of function when it comes to bank or paying apps. I don't use Google pay but safety net passes just fine with my setup
fast69mopar said:
Unlocking your bootloader and rooting your devices is a choice that you and only you can make. There are always risks when modifying your devices. When you unlock the bootloader on most devices it will void your warranty unless stated otherwise by the manufacturer.
When it comes to root access there is always a chance for things to stop working. That is why it is up to you to do your research and make an informed decision before taking any action.
To some people, including me, an unlockable bootloader and gaining root access over a device is a must. I am paying for it and I want to use my devices how I see fit.
If you are concerned about an issue that may arise because you have an unlocked bootloader and root access I always try to look at it from both sides. Why did I unlock the bootloader? Why did I root? Am I able to do what I intended to do or not?
Click to expand...
Click to collapse
Thanks a lot for your response
I actually rooted because I wanted to use substratum themes and enable aux module in gcam. Apart from that no other reason.
So I guess I am not missing out on too much .
I actually unrooted my phone and relocked the bootloader.
But again thanks for the response!
I had unlocked the bootloader and tried a couple of custom ROMs a few months back but decided it isn't worth it because my main hindrance of adblocking is addressed using DNS and any unneeded app can be disabled using adb. On the flip side, I need Widevine L1 for Netflix/Prime and no custom ROM can offer that on the 7T.
Makes more sense to me to stay within the walled garden, especially with the higher risk brought about by rogue Android apps that are now far too prevelent. The mods too are not that much value adding than it was may be when I first started using custom ROMs nearly a decade ago.
Can i modify my g988u from verizon in anyway? And if so how? Im new to this kind of stuff. I know i should probably leave verizon
You might be able to disable some packages with ADB , but beyond that, if your phone has been receiving OTA updates, it's likely hopeless. Substantial customization requires root, and that is precluded by locked bootloaders. There are paid services that can unlock bootloaders in S20s with older software, but my understanding is this isn't an option for devices with newer software
I actually just switched to Verizon, entirely motivated by AT&T's hostiliity towards most unlocked devices (that they don't sell). So, if you leave, who are you going to go to? T-Mobile is the most permissive of the big 3, but tends to lag in infrastructure.
Right didnt even look into that. Probably going to stay with verizon now that ya said that lol. Just curious What do people get out of from rooting their phone? I want to learn how and dont know where to start.
CainD5 said:
Right didnt even look into that. Probably going to stay with verizon now that ya said that lol. Just curious What do people get out of from rooting their phone? I want to learn how and dont know where to start.
Click to expand...
Click to collapse
A lot. Android phones have come a long way in past decade and change that they have been available, but root access, which is typically associated with at least an unlocked bootloader and possibly also a custom ROM, remains the single most powerful customization tool. A short non-exhaustive list of what you can do:
Use Magisk (See Magisk Module Repo for ideas of capabilties).
Use EdXposed or LSPosed (See Xposed Module Repo for ideas of capabilities).
Install a custom kernel (natively mount CIFS/NFS filesystems, overclock your device, and all sorts of other options).
Permanently debloat your ROM (survives hard reset).
Enjoy the best ad blocking experience.
View/backup/edit private application data.
There are also downsides to root, such as tripping the warranty void bit (and disabling Knox-related functionality like Samsung Pay, likely losing filesystem encryption, and greatly increasing your odds of a malware infestation. That said, the XDA site is largely powered by the modding/root access community, so those risks aren't discussed much.