Related
I was really surprised to learn that LG don't have a bootloader unlocking service like even HTC have done and given that the LG never managed to unlock the bootloader, I'm quite surprised that there wasn't more of a community outcry. What is up with that? Have LG ever spoken of supporting the development community? Is it unlikely that we'll see it happen within the flagship lifetime of our device?
NB: This is discussion topic, it's really not a question/answer topic.
sabret00the said:
I was really surprised to learn that LG don't have a bootloader unlocking service like even HTC have done and given that the LG never managed to unlock the bootloader, I'm quite surprised that there wasn't more of a community outcry. What is up with that? Have LG ever spoken of supporting the development community? Is it unlikely that we'll see it happen within the flagship lifetime of our device?
NB: This is discussion topic, it's really not a question/answer topic.
Click to expand...
Click to collapse
whoa is this 100% correct? if that's the case I will strongly reconsider getting the G3 and will probably go for either M8 or Z2...
Well, coming from an LG Nexus 5, I can tell you that the development community is booming over there. But that's to be expected with a Nexus device. I'm planning on switching from the Nexus 5 to the G3 (ordered yesterday) in an effort to no longer sacrifice hardware in order to get the vanilla Android experience. These days I'd rather give up some of the software advantages in AOSP ROMs in order to get significantly better hardware.
Unfortunately, it's a sacrifice one way or another. And if you buy a phone such as the G3 you must do so expecting that the development for it will take significantly longer and will likely have less options. However, in my opinion the interface/features offered in the latest stock LG interfaces are quite improved and look/feel much better than the interfaces provided by other manufacturers. I don't think I'll have any issue using the stock interface with the LG for many months after coming from the previous 4 generations of Nexus devices.
The vanilla Android experience has gotten quite boring in my opinion and I welcome the features that will be available on LG's stock ROM.
cez10 said:
whoa is this 100% correct? if that's the case I will strongly reconsider getting the G3 and will probably go for either M8 or Z2...
Click to expand...
Click to collapse
Sadly yes, it's something I should've looked into in the six months of waiting for this phone. But it's sadly the case. Even on the G2, they couldn't unlock the bootloader and instead had to bypass it.
sn0warmy said:
Well, coming from an LG Nexus 5, I can tell you that the development community is booming over there. But that's to be expected with a Nexus device. I'm planning on switching from the Nexus 5 to the G3 (ordered yesterday) in an effort to no longer sacrifice hardware in order to get the vanilla Android experience. These days I'd rather give up some of the software advantages in AOSP ROMs in order to get significantly better hardware.
Unfortunately, it's a sacrifice one way or another. And if you buy a phone such as the G3 you must do so expecting that the development for it will take significantly longer and will likely have less options. However, in my opinion the interface/features offered in the latest stock LG interfaces are quite improved and look/feel much better than the interfaces provided by other manufacturers. I don't think I'll have any issue using the stock interface with the LG for many months after coming from the previous 4 generations of Nexus devices.
The vanilla Android experience has gotten quite boring in my opinion and I welcome the features that will be available on LG's stock ROM.
Click to expand...
Click to collapse
If you have the patience, I'd recommend waiting a little while to see if they announce a GPe of the G3. That could provide you with the best of both worlds.
Development will improve for sure - the phone has only been out less than a week (D855) with most people still not having received their devices yet and is not even released in the US. It seems the Korean models have shipped with an unlocked bootloader (from what I have heard) and as for the D855 no one has yet confirmed it a) it is locked and b) if it can be unlocked.
I have certainly not looked into it yet myself, although if it is locked, unlocking via any "hacking" method, is beyond my knowledge, someone smarter than me will have to tell us how to do that.
Give it time, development is always slow in the first month of a new device (unless its a nexus), and tends ot only pick up after release in the USA.
sabret00the said:
If you have the patience, I'd recommend waiting a little while to see if they announce a GPe of the G3. That could provide you with the best of both worlds.
Click to expand...
Click to collapse
Eh, if they release a GP edition G3 it will still pay to have this one because any AOSP ROMs for the GP edition will be quickly ported over to the non-GP edition anyway. I plan on keeping this phone but will also still be happy if they come out with a GP edition as well so we can get some AOSP source code up and running for this device.
And I'm not worried about the bootloader being locked. Someone ALWAYS finds a way to unlock it rather quickly these days.
Personally, my goal with this phone is to root it to get my DPI settings where I want them and get rid of any bloat that may cause the phone to slow down. If I can manage to accomplish those two things, I'll be happy (and it's already doable). My days of rooting, flashing ROMs, bricking, unbricking, and flashing more ROMs are over. At this point I just want a solid phone that works flawlessly.
Lennyuk said:
Development will improve for sure - the phone has only been out less than a week (D855) with most people still not having received their devices yet and is not even released in the US. It seems the Korean models have shipped with an unlocked bootloader (from what I have heard) and as for the D855 no one has yet confirmed it a) it is locked and b) if it can be unlocked.
I have certainly not looked into it yet myself, although if it is locked, unlocking via any "hacking" method, is beyond my knowledge, someone smarter than me will have to tell us how to do that.
Give it time, development is always slow in the first month of a new device (unless its a nexus), and tends ot only pick up after release in the USA.
Click to expand...
Click to collapse
I'm not so much talking about from the community side, I have faith the community will find an unlock or bypass method. I'm more so talking about from LG's point of view. They don't seem to be supportive hence no official channel to unlock the G2 bootloader despite the G3 launching globally this week.
sabret00the said:
I'm not so much talking about from the community side, I have faith the community will find an unlock or bypass method. I'm more so talking about from LG's point of view. They don't seem to be supportive hence no official channel to unlock the G2 bootloader despite the G3 launching globally this week.
Click to expand...
Click to collapse
Remember it took years to get HTC to provide an unlock tool (and the company nearly going bankrupt!), Moto and Sony were the same - moto becoming better when Google acquired them and Sony nearly gave up making android devices completely before they decided to become more dev friendly.
Basically companies only provide unlock methods as a last resort, when they feel its the only way to improve their sales. LG haven't needed this yet.
There are still plenty of devices where you cannot officially unlock the bootloader, its not just an LG thing.
Lennyuk said:
Remember it took years to get HTC to provide an unlock tool (and the company nearly going bankrupt!), Moto and Sony were the same - moto becoming better when Google acquired them and Sony nearly gave up making android devices completely before they decided to become more dev friendly.
Basically companies only provide unlock methods as a last resort, when they feel its the only way to improve their sales. LG haven't needed this yet.
There are still plenty of devices where you cannot officially unlock the bootloader, its not just an LG thing.
Click to expand...
Click to collapse
I totally hear you, but with the success Sony have enjoyed, you'd hope manufacturers would get involved early on.
Lennyuk said:
and as for the D855 no one has yet confirmed it a) it is locked and b) if it can be unlocked.
I have certainly not looked into it yet myself, although if it is locked, unlocking via any "hacking" method, is beyond my knowledge, someone smarter than me will have to tell us how to do that.
Click to expand...
Click to collapse
Is this something that is easy to check?
Dubhar said:
Is this something that is easy to check?
Click to expand...
Click to collapse
I can't even access the bootloader. Despite turning USB debugging on, I can't get ADB to recognise the phone. I started a thread to check if others have a similar problem.
It's a flagship, I'm not worried about development support. Look at the g2, it got cm support. Plus the LG software looks decent, not too basic like HTC or too intrusive like Samsungs touchwiz
sabret00the said:
I can't even access the bootloader. Despite turning USB debugging on, I can't get ADB to recognise the phone. I started a thread to check if others have a similar problem.
Click to expand...
Click to collapse
I rooted D855 yesterday using ioroot and as a part of the process "adb devices" did show the phone with USB debugging on.
I had to install lg unified driver so windows 8 had a right driver for it.
Heisenberg420 said:
It's a flagship, I'm not worried about development support. Look at the g2, it got cm support. Plus the LG software looks decent, not too basic like HTC or too intrusive like Samsungs touchwiz
Click to expand...
Click to collapse
This thread is about development support from LG. Please read threads before commenting. The G2 you mentioned was given as an example of the lack of support previously provided by LG.
jodvova said:
I rooted D855 yesterday using ioroot and as a part of the process "adb devices" did show the phone with USB debugging on.
I had to install lg unified driver so windows 8 had a right driver for it.
Click to expand...
Click to collapse
Perhaps I need to update my drivers then. Though that's nearly unheard of as I'm on Linux.
If i can atleast root the phone to remove the bloatware, I'll be happy for a little while.
sabret00the said:
This thread is about development support from LG. Please read threads before commenting. The G2 you mentioned was given as an example of the lack of support previously provided by LG.
Perhaps I need to update my drivers then. Though that's nearly unheard of as I'm on Linux.
Click to expand...
Click to collapse
Hm, i've not check on Linux yet, but it is recognised on windows with the right USB drivers installed. Maybe its lacking some udev rule to properly recognise the device?
The LGD855 boots into recovery with adb reboot recovery, but not the bootloader using adb reboot-bootloader its just reboots. I goes into download mode with power+volume up, that about all ive tried.
Slash8915 said:
If i can atleast root the phone to remove the bloatware, I'll be happy for a little while.
Click to expand...
Click to collapse
towelroot worked.
on Win 7 by flashing sphinxrom for d855 and s,k,l :
when i was installing the lg driver, it installed the AndroidNet Sooner Single ADB Interface
i had to change it Android ADB Interface
what the hell the device just came out give it some time
daddioj said:
what the hell the device just came out give it some time
Click to expand...
Click to collapse
What the hell can't you read & understand what OP has said or trying to say? (sorry no offence intended). He isn't talking about the support of the development community to this device(G3), which by the way will certainly pick up from what it is now, but he is talking about LG's support to the development community(being more developer friendly as Sony & HTC).
And even if we talk about how much active Android development this device(& it's variants) will see, then let me tell you that the development activity of this device will(probably) never be as much as you see with other flagship devices like HTC One(M7 & m8), that is because a) HTC is more developer friendly by letting you to unlock the bootloader & thus making easy for developers to port(make) ROMs, recoveries & what not, where as with LG & G2 it is entirely different case(ask any developer involved in G2 development, how difficult it is or was to make a recovery or a ROM for G2 and for common flahers the risk factor of flashing those recoveries & ROMs that much more because all the solutions based on a bypassing solution with many permutations & combinations rather than a fully unlockable bootloader just as with HTC devices and b) they are more popular devices among people(as much successful the G2 was it wasn't sold as many as S4s & S5s or M7s & M8s).
We all hope that LG will follow HTC & Sony in being developer frienly. No doubt they are making beautiful devices like G2 & now G3. But sadly, as one of other member pointed out above, it is at the stage of extinction that a manufacturer tend to be more friendly with developer community.
st_7 said:
What the hell can't you read & understand what OP has said or trying to say? (sorry no offence intended). He isn't talking about the support of the development community to this device(G3), which by the way will certainly pick up from what it is now, but he is talking about LG's support to the development community(being more developer friendly as Sony & HTC).
And even if we talk about how much active Android development this device(& it's variants) will see, then let me tell you that the development activity of this device will(probably) never be as much as you see with other flagship devices like HTC One(M7 & m8), that is because a) HTC is more developer friendly by letting you to unlock the bootloader & thus making easy for developers to port(make) ROMs, recoveries & what not, where as with LG & G2 it is entirely different case(ask any developer involved in G2 development, how difficult it is or was to make a recovery or a ROM for G2 and for common flahers the risk factor of flashing those recoveries & ROMs that much more because all the solutions based on a bypassing solution with many permutations & combinations rather than a fully unlockable bootloader just as with HTC devices and b) they are more popular devices among people(as much successful the G2 was it wasn't sold as many as S4s & S5s or M7s & M8s).
We all hope that LG will follow HTC & Sony in being developer frienly. No doubt they are making beautiful devices like G2 & now G3. But sadly, as one of other member pointed out above, it is at the stage of extinction that a manufacturer tend to be more friendly with developer community.
Click to expand...
Click to collapse
i am Guilty of not reading the whole Thread
I want to pre-order the new S7 Edge but im from europe and I want the SD820 chip. Mostly because of it's easier to mod so developers will give more love to that.
Does anyone know where I can do this?
Makes no sense at all. If a phone ever cried out for non-stock to be avoided, it's this. You will lose all Samsung features like Edge and the camera features and quality will be s**t in comparison. If you're bothered about running AOSP or CM this isn't the phone for you regardless of what chip set it has in it.
Beefheart said:
Makes no sense at all. If a phone ever cried out for non-stock to be avoided, it's this. You will lose all Samsung features like Edge and the camera features and quality will be s**t in comparison. If you're bothered about running AOSP or CM this isn't the phone for you regardless of what chip set it has in it.
Click to expand...
Click to collapse
Not completely true. To be fair he just said modding. Not flashing Stock (AOSP) ROMs, Kernels, etc...
An "clean" TW ROM is always welcomed and usually the best of both worlds.
Except clean stock doesn't require an open source chip set. It's just as easy to debloat stock on Exynos as it is on Snapdragon.
Beefheart said:
Except clean stock doesn't require an open source chip set. It's just as easy to debloat stock on Exynos as it is on Snapdragon.
Click to expand...
Click to collapse
Eh... Got me there.
Beefheart said:
Makes no sense at all. If a phone ever cried out for non-stock to be avoided, it's this. You will lose all Samsung features like Edge and the camera features and quality will be s**t in comparison. If you're bothered about running AOSP or CM this isn't the phone for you regardless of what chip set it has in it.
Click to expand...
Click to collapse
I agree with you - for me I wouldn't spend a ton of money on a phone only to lose many of the special features - but at the end of the day, it's his call what he does with his phone - and if he prefers running a clean AOSP rom or even just modded touch wiz, it;s his call - regardless - it probably won't be easy for him to find an unlocked snapdragon model - at least not early on - maybe after it's been out for a while...
I believe the Verizon version would be the best one to get to support most of the spectrum around the world, but Verizon will lock that bootloader. I bought the T-Mobile version outright and will probably get mine unlocked a couple days after I get it(paid outright and meet requirements)
Sent from my Nexus 5X using Tapatalk
If anyone has an answer to the OP's question I am curious also
After the 810 I dont want a snapdragon ever again. Glad my country is getting the 8890.
At echoe they already said they will develop for thz exynos variant cuz most part of their theam is from europe so thats asewome! [emoji3]
Verstuurd vanaf mijn SM-N920C met Tapatalk
@Beefheart Just to clarify:
With regards to the S7 Edge, its best to leave it untouched with regards to custom roms & kernels otherwise "Edge" features will be lost ?
SlyUK said:
@Beefheart Just to clarify:
With regards to the S7 Edge, its best to leave it untouched with regards to custom roms & kernels otherwise "Edge" features will be lost ?
Click to expand...
Click to collapse
Yes. The edge features, as far as I'm aware, require Samsung libraries, which are closed source and can't be used outside of stock Touchwiz roms. It's for the same reason S-Pen features in non-stock roms on the Note series of devices can't be used and require third party software (SPenCommand for example).
Beefheart said:
Yes. The edge features, as far as I'm aware, require Samsung libraries, which are closed source and can't be used outside of stock Touchwiz roms. It's for the same reason S-Pen features in non-stock roms on the Note series of devices can't be used and require third party software (SPenCommand for example).
Click to expand...
Click to collapse
Would that be the case also with a custom rom that was based on the Stock rom but was "debloated" ?
mocsab said:
I agree with you - for me I wouldn't spend a ton of money on a phone only to lose many of the special features - but at the end of the day, it's his call what he does with his phone - and if he prefers running a clean AOSP rom or even just modded touch wiz, it;s his call - regardless - it probably won't be easy for him to find an unlocked snapdragon model - at least not early on - maybe after it's been out for a while...
Click to expand...
Click to collapse
Of course it's his money and his choice, he can buy an S7 Edge and use it as a paperweight if he wishes to. But this is a forum for discussion, and I'm simply pointing out that, in my opinion with 6 years experience of using and modifying Android devices, it wouldn't make any sense to buy an S7 Edge if he wants to use non-stock roms. It defeats the object of paying the premium on a device like this in the first place.
---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------
SlyUK said:
Would that be the case also with a custom rom that was based on the Stock rom but was "debloated" ?
Click to expand...
Click to collapse
Just to clarify, for me a "custom rom" means non-stock. Perhaps not entirely accurate but that is how I've always viewed the phrase. But to answer your question, no. That would be a debloated and minimised stock rom, and any desired features of Samsung vanilla stock could be included as the required libraries are still intact.
Beefheart said:
Of course it's his money and his choice, he can buy an S7 Edge and use it as a paperweight if he wishes to. But this is a forum for discussion, and I'm simply pointing out that, in my opinion with 6 years experience of using and modifying Android devices, it wouldn't make any sense to buy an S7 Edge if he wants to use non-stock roms. It defeats the object of paying the premium on a device like this in the first place.
Click to expand...
Click to collapse
Of course you are right, but he is not alone - there are lots of people who do what he plans to do no matter what we think ..and despite the many advantages and tools that are built into one of these phones, a high end phone with the kind of quality that is built into an S7 or Note 5 or whatever - is still an amazing phone when it uses a different system - AOSP or whatever - so I don't fault yuo for making your point - but it is likely that in his and many other cases it falls on deaf ears
Beefheart said:
Of course it's his money and his choice, he can buy an S7 Edge and use it as a paperweight if he wishes to. But this is a forum for discussion, and I'm simply pointing out that, in my opinion with 6 years experience of using and modifying Android devices, it wouldn't make any sense to buy an S7 Edge if he wants to use non-stock roms. It defeats the object of paying the premium on a device like this in the first place.
---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------
Just to clarify, for me a "custom rom" means non-stock. Perhaps not entirely accurate but that is how I've always viewed the phrase. But to answer your question, no. That would be a debloated and minimised stock rom, and any desired features of Samsung vanilla stock could be included as the required libraries are still intact.
Click to expand...
Click to collapse
I wasn't quite sure of the terminology to use for a slimmed down, debloated rom based on the official stock rom, so used the word custom to be on the safe side. Thanks for answering that, gives reassurance.
SlyUK said:
I wasn't quite sure of the terminology to use for a slimmed down, debloated rom based on the official stock rom, so used the word custom to be on the safe side. Thanks for answering that, gives reassurance.
Click to expand...
Click to collapse
It's worth noting that, to install such a rom, the knox flag would have to be tripped. On Samsung Marshmallow, the only way to avoid tripping knox when installing a new build is to use Odin, which can only be used to install vanilla stock. And to use tools like FlashFire to install a build, you need to be rooted, a process which in itself trips the knox flag so you may as well install TWRP or CWM and install via a zip in recovery.
im also one of a guy waiting for S7edge with S820 from outside of US so i felt the pain and confusion of the way Sammy doing. As one of a guy responded in Reddit chat is to start ordering UNLOCKED SIM Samsung S7 from ebay would be the easiest and fastest option...
Below is the one that I am watching closely. As it said Pre-order, I am a bit afraid of the RISK of ordering a phone that cost >1000$ without seeing actual unlocked & S820 phone as they mention.
[EDIT: can't put links due to lower posts count] googled this eBay item number:281944393668
Here is some other options
to Confirm: you might have to wait for unlocked version from Samsung to released in US since all the US carriers will delay the unlocked version so that mostly can able to attract customer by offering them insensitive to stay in their network.
to Confirm: As far as I knew, US is the ONLY country which S7 variant will come with S820. The rest will ONLY get Exynos version in it with Dual SIMs supported.
to Confirm: As far as I found online is that there is no unique model number which will be the UNLOCKED version of S7 is surfaced in Internet. All the model numbers of US variant are for tied with each US Carriers. So it is possible that US will never get unlocked version of S7 with S820.
to Confirm: some people said they can ask their US carrier to unlock their locked S7 after a period of time using.
ted_O_o said:
im also one of a guy waiting for S7edge with S820 from outside of US so i felt the pain and confusion of the way Sammy doing. As one of a guy responded in Reddit chat is to start ordering UNLOCKED SIM Samsung S7 from ebay would be the easiest and fastest option...
Below is the one that I am watching closely. As it said Pre-order, I am a bit afraid of the RISK of ordering a phone that cost >1000$ without seeing actual unlocked & S820 phone as they mention.
[EDIT: can't put links due to lower posts count] googled this eBay item number:281944393668
Here is some other options
to Confirm: you might have to wait for unlocked version from Samsung to released in US since all the US carriers will delay the unlocked version so that mostly can able to attract customer by offering them insensitive to stay in their network.
to Confirm: As far as I knew, US is the ONLY country which S7 variant will come with S820. The rest will ONLY get Exynos version in it with Dual SIMs supported.
to Confirm: As far as I found online is that there is no unique model number which will be the UNLOCKED version of S7 is surfaced in Internet. All the model numbers of US variant are for tied with each US Carriers. So it is possible that US will never get unlocked version of S7 with S820.
to Confirm: some people said they can ask their US carrier to unlock their locked S7 after a period of time using.
Click to expand...
Click to collapse
You are referring to this one:
http://www.ebay.com/itm/NEW-UNLOCKE...393668?hash=item41a53207c4:g:NhIAAOSwFNZWzWSU
No was not really thinking about a new rom if disabling touchwiz is possible. I had my mind more into rooting and xposed.
Is there something I'm missing?
Sammy locked the Bootloader
Yup. This is the most highly sought after device with almost no developer support.
If you wanted root then you should get pretty much any other phone.
if you change the Android Code, you have to share it.
ahq1216 said:
Sammy locked the Bootloader
Click to expand...
Click to collapse
Correct me if I am wrong, but according to the Android Platform User Agreement (I think), if you change the Android Code, you have to share it. Or some form of developers open source agreement. Correct?
So there has been no root accomplished whatsoever on the T-Mobile S7? If that's true, then I'm hanging on to my Note 7 and selling the S7E.
Binary100100 said:
Yup. This is the most highly sought after device with almost no developer support.
If you wanted root then you should get pretty much any other phone.
Click to expand...
Click to collapse
Then what is the post in your signature about?
https://forum.xda-developers.com/ve...sed-unroot-t3411039/post67605246#post67605246
And what's the deal with the engineering bootloader?
http://www.theandroidsoul.com/root-t-mobile-s7-edge-engineering-bootloader/
Looks like S7 has had an unlocked bootloader with this for a while... Still very confused as to why there are no roms here.
unkellsam said:
Then what is the post in your signature about?
https://forum.xda-developers.com/ve...sed-unroot-t3411039/post67605246#post67605246
Click to expand...
Click to collapse
unkellsam said:
And what's the deal with the engineering bootloader?
http://www.theandroidsoul.com/root-t-mobile-s7-edge-engineering-bootloader/
Looks like S7 has had an unlocked bootloader with this for a while... Still very confused as to why there are no roms here.
Click to expand...
Click to collapse
I suppose you really need to read a bit more.
For all Qualcomm US devices the bootloader is LOCKED.
This is well known and documented. Root is possible only with an engineering kernel. The page that you referenced is inaccurate as it referenced an engineering bootloader. It's actually an engineering boot.img file that the writer mistook for a bootloader. Again... it's an engineering kernel not engineering bootloader.
unkellsam said:
So there has been no root accomplished whatsoever on the T-Mobile S7? If that's true, then I'm hanging on to my Note 7 and selling the S7E.
Click to expand...
Click to collapse
There is, but it's very unstable. Phone tends to lag and overheat due to the (something i dont understand).
serendipityguy said:
Correct me if I am wrong, but according to the Android Platform User Agreement (I think), if you change the Android Code, you have to share it. Or some form of developers open source agreement. Correct?
Click to expand...
Click to collapse
Well, yes and no. Parts fall under GPL, and parts of what Samsung uses to enable full functionality of the phone are NOT. The fact that they use special digital signatures in the boot process to prevent loading unsigned code is totally up to them (i.e. its all the stuff that happens before "android" starts...
sbaeder said:
Well, yes and no. Parts fall under GPL, and parts of what Samsung uses to enable full functionality of the phone are NOT. The fact that they use special digital signatures in the boot process to prevent loading unsigned code is totally up to them (i.e. its all the stuff that happens before "android" starts...
Click to expand...
Click to collapse
But arn't there other S7 roms from Verizon, AT&T and Sprint having developers pushing out custom kernels? Is this something that T-mobile can release but won't?
Google gives/updates the OS, Samsung gives the S7 hardware / Updated OS - Patches the OS & then gives to the Carriers (Tmobile) and they plug in their hellware (Bloatware), surely they have the source or the ability to modify the stock rom when updates are being pushed out to the carriers.
When a New Stock drops, it is the phone carriers who modify the kernel's, boot animation, build property, and sets their modems and such . . . Not Samsung because they would not be want to push out the kernels, modems, build property, boot animation & custom roms for each phone carrier in each region of each county. So lf what I am thinking that our phone carriers developers are lame ducks....
Going the other way on this, how does Sam Mobile play into this? how is it that they are able to host the roms on their servers? Arn't there any links from Samsung to host the roms?
Please if I am wrong, please someone correct me.
It's complicated...
Samsung locked the bootloaders on all US (Qualcomm) S7 but left the bootloader unlocked on international (Exynos) roms and some international Qualcomm roms.
This sucks and hopefully is not repeated on the upcoming S8 which may be Qualcomm only.
Last summer, an engineering bootloader was leaked and a group of people here got a root that uses the engineering bootloader. It's not perfect, as it forces people to use a non-production kernel. More people here came up with settings to get the most out of that kernel.
Right now we are in the middle of the transition to Android 7 and the engineering root doesn't work with it presently. Until a solution for that is reached
At the same time, the international rom deveopment has gone smoothly with over a dozen roms updated and a few tweaked kernels. The Exynos phone itself seems to be faster and with better battery life (but worse reception) compared to a standard qualcomm. Rooted with a custom kernel on both, it's like night and day how much better the exynos performance is. Some people ported T-mobile wifi calling and Volte (through CSC settings) to the international version, so for a certain user (of which I am one), the ideal root solution is to run a full speed exynos 930F on Android 7 and retain t-mobile functionality.
unkellsam said:
Is there something I'm missing?
Click to expand...
Click to collapse
Samsung blows
T-Mobile and Samsung both ****ed up around this time
Sent from my SM-G935T using XDA-Developers Legacy app
fracture8 said:
T-Mobile and Samsung both ****ed up around this time
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
I hear you.
Im gonna pay off the half of the phone in 7 months and then will jump ship to a one plus 4/5 when its released.
So much wasted potential
I would get the G935F.
serendipityguy said:
But arn't there other S7 roms from Verizon, AT&T and Sprint having developers pushing out custom kernels? Is this something that T-mobile can release but won't?
Google gives/updates the OS, Samsung gives the S7 hardware / Updated OS - Patches the OS & then gives to the Carriers (Tmobile) and they plug in their hellware (Bloatware), surely they have the source or the ability to modify the stock rom when updates are being pushed out to the carriers.
When a New Stock drops, it is the phone carriers who modify the kernel's, boot animation, build property, and sets their modems and such . . . Not Samsung because they would not be want to push out the kernels, modems, build property, boot animation & custom roms for each phone carrier in each region of each county. So lf what I am thinking that our phone carriers developers are lame ducks....
Going the other way on this, how does Sam Mobile play into this? how is it that they are able to host the roms on their servers? Arn't there any links from Samsung to host the roms?
Please if I am wrong, please someone correct me.
Click to expand...
Click to collapse
T-Mobile and Samsung keep playing around. I'm really hoping the Note 8 comes with an unlocked boot-loader or this may be there strategy going forward for the US.
rp3 said:
It's complicated...
Samsung locked the bootloaders on all US (Qualcomm) S7 but left the bootloader unlocked on international (Exynos) roms and some international Qualcomm roms.
This sucks and hopefully is not repeated on the upcoming S8 which may be Qualcomm only.
Last summer, an engineering bootloader was leaked and a group of people here got a root that uses the engineering bootloader. It's not perfect, as it forces people to use a non-production kernel. More people here came up with settings to get the most out of that kernel.
Right now we are in the middle of the transition to Android 7 and the engineering root doesn't work with it presently. Until a solution for that is reached
At the same time, the international rom deveopment has gone smoothly with over a dozen roms updated and a few tweaked kernels. The Exynos phone itself seems to be faster and with better battery life (but worse reception) compared to a standard qualcomm. Rooted with a custom kernel on both, it's like night and day how much better the exynos performance is. Some people ported T-mobile wifi calling and Volte (through CSC settings) to the international version, so for a certain user (of which I am one), the ideal root solution is to run a full speed exynos 930F on Android 7 and retain t-mobile functionality.
Click to expand...
Click to collapse
I was dead set on getting the Note 7 but after the fiasco i settled for the S7 edge. the G935F also has all the bands that t-Mobiel uses so we get band 12 as well. The issue with getting the G935F is trying to buy online as it has to be imported and still get insurance and so forth. Bought from B&H photo ( aa reputable US store) for insurance and good support. The g935F turned out to be a good gamble. As long as you wait there was alot of development. Since alot of us T-Mobile guys hopped over we were able to get Volte and wificalling ported over via various CSC edits and other workarounds. So we get alot of custom roms and T-Mobile support as well. Only issue you have to root and loose Samsung pay but for me that a okay lol.
A couple of days ago I received my SM-T725 from Amazon. They had the international version in stock with free Prime two day shipping. Since this is the international version, it doesn't have any carrier bloat. I installed a T-Mobile SIM and it's getting a good LTE signal here in Minnesota. So far everything is working fine. I like the form factor and it's a nice upgrade from my very old SM-T817T.
Most of my previous devices I rooted and installed custom ROMs. For now I'll try to see if I can still to the stock ROM.
Glad you like it. I am enjoying mine, but I wish it had some custom roms and support from the community. Considering its price and features, I am honestly a bit surprised it is not more popular on here. This tablet is ripe for some lineage OS. Samsung's Android implementation is so heavy and bloated.
oRAirwolf said:
Glad you like it. I am enjoying mine, but I wish it had some custom roms and support from the community. Considering its price and features, I am honestly a bit surprised it is not more popular on here. This tablet is ripe for some lineage OS. Samsung's Android implementation is so heavy and bloated.
Click to expand...
Click to collapse
I'm sure someone will do it. Since mine is not carrier branded, Samsung allows you to unlock the boot loader. So a custom recovery is possible. Of course a custom recovery means that Magisk should work. Even without a custom ROM, you can debloat it when you have root access. The problem is knowing what you can remove without breaking things.
Just like it says on a tin can, I have a few questions I am wondering about to ask myself, and yeah, be warned, there is a few angry rants about Verizon's fraudulent practice of locking down the phones. Anyways, here we go...
I have been taking a stab at asking T-Mobile a few questions (via their Tweeter account, of course), regarding their stance on bootloader, and whether they will go the way of Verizon and perma-lock their phones in the future (Sprint have been rather infamous for that too, and don't get me started on Verizon, they still boil my blood), and I was told they have no reason to do so for the risk of losing a lot of customers which is sensible. In the other word, I can expect to see to it that T-Mobile phones will remain unlockable for good. (I will tell you why Verizon boil my blood; they permanently lock everything they touch under the Sun, except for the Nexus 6 of course, and get it, they will refuse to unlock it "for customer service experience" which is a rather lame excuse which anyone would blow through like a piece of paper tissue easily, and for this reason, I have intense hatred for Verizon for a very good reason because perma-locking the bootloader in the phones we buy with our cold, hard cash is a bona fide fraud. As you can see what's obvious; I left Verizon for T-Mobile for this reason.)
Anyhow, I wonder why is OnePlus starting to do something weird with the bootloader and Linux kernel in the recent OxygenOS update so that International version will not boot on converted T-Mobile OnePlus 6T phones (the infamous hardware mismatch warning which is also starting to happen with couple of custom OSes, nevertheless it CAN be bypassed so the OnePlus 6T phone will just continue to boot up normally), which is frankly a strange way to screw the sleeping dog because both T-Mobile (A6013) and International (A6010) versions are virtually the same hardware, absolutely no difference at all, except for the modem configuration, it's very expensive to respin the motherboard just to screw the customers.
(Except for both Samsung and Motorola, they don't care about the customers, all they want is money which the hateful Verizon have a lot of to make it so the identical phones are made with sneaky surprises inside so that a custom OS won't work on, nevertheless it usually won't work because LineageOS community prevails anyways. Still, I am disappointed about all that mess. I wonder why Verizon haven't been punished for perma-locking the LTE phones as their Block C LTE agreement clearly says that locking down the bootloader is forbidden. Full stop. Still, OnePlus is doing the right thing here, by allowing the customers to have choice. And shame on you, Google, why do you perma-lock the Verizon Google Pixel phones? C'mon, you know better than that.)
Still, T-Mobile telling me that they will refuse to lock the phones down is a good news in a way because the computer security is moving at alarming clip now (which means we will must unlock the bootloader to continue to be protected against future dangerous exploitations by continuing to be up to date especially with LineageOS which exists for this reason, and that's where a few carriers, especially Verizon, fall short in term of the computer security, and most newer Superuser managers, like Magisk, are password protected nowadays, which is absolutely mandatory). I am glad they made the commitment on it, thus I will be T-Mobile customer for a good while.
Sent from my OnePlus 6T using Tapatalk
Dr. Mario said:
Anyhow, I wonder why is OnePlus starting to do something weird with the bootloader and Linux kernel in the recent OxygenOS update so that International version will not boot on converted T-Mobile OnePlus 6T phones (the infamous hardware mismatch warning which is also starting to happen with couple of custom OSes, nevertheless it CAN be bypassed so the OnePlus 6T phone will just continue to boot up normally), which is frankly a strange way to screw the sleeping dog because both T-Mobile (A6013) and International (A6010) versions are virtually the same hardware, absolutely no difference at all, except for the modem configuration, it's very expensive to respin the motherboard just to screw the customers.
Click to expand...
Click to collapse
I'm on a converted T-Mobile 6T on OB15 and didn't have a problem booting when updating to this most recent. Is this just something they are starting the ball rolling on to where the International version will not boot on converted T-Mobile OnePlus 6T phones or have some run into this problem already with the hardware mismatch warning? And if this happens on the next update how can it be bypassed to be able to boot into the OS? Sorry if I'm behind the times on this but it is the first time I'm hearing about this.
Interesting, I will give recent ROM update a shot at aome point soon. Hope I don't get the warnings as a few people are starting to get the warning on their converted T-Mobile OnePlus 6T phones, so right now I am holding off on the update so I can be sure I don't run into this problem.
I flashed the OxygenOS 9.0.15 on both slots so I can update to recent LineageOS 16 and put some bootloader vulnerabilities to bed. It's the recent Android Quindim beta version that started to display the hardware mismatch warning, so I got nervous about the OxygenOS 9.0.15 bootloader which could have this type of check, as well as how recent custom OSes handle this situation.
Sent from my OnePlus 6T using Tapatalk
I'm in a TMO converted that's not paid off and I'm bootloader and Sim unlocked as well as running latest with no issues at all. Never ran into this hardware mismatch issue at all. I haven't really messed with custom ROMs on this though.
Dr. Mario said:
Interesting, I will give recent ROM update a shot at aome point soon. Hope I don't get the warnings as a few people are starting to get the warning on their converted T-Mobile OnePlus 6T phones, so right now I am holding off on the update so I can be sure I don't run into this problem.
I flashed the OxygenOS 9.0.15 on both slots so I can update to recent LineageOS 16 and put some bootloader vulnerabilities to bed. It's the recent Android Quindim beta version that started to display the hardware mismatch warning, so I got nervous about the OxygenOS 9.0.15 bootloader which could have this type of check, as well as how recent custom OSes handle this situation.
Sent from my OnePlus 6T using Tapatalk
Click to expand...
Click to collapse
Another thing also...I found that just doing the lighter OTA updates that I would sometimes run into some kind of bug here and there. Like after I did the OB14 OTA my FP sensor was buggy as hell...So I started downloading the full updates from the OP site and doing the local update. This has been working better for me...Phone has been working great since I started doing that. But yeah I did hear that about the Q beta on the T-Mobile phones now that you mention it...So I have steered clear of that.
---------- Post added at 10:50 PM ---------- Previous post was at 10:40 PM ----------
jestyr8 said:
I'm in a TMO converted that's not paid off and I'm bootloader and Sim unlocked as well as running latest with no issues at all. Never ran into this hardware mismatch issue at all. I haven't really messed with custom ROMs on this though.
Click to expand...
Click to collapse
I'm sim unlocked but haven't unlocked the bootloader yet as I'm happy with the OS and don't want to see the bootloader unlocked nag screen when I boot up. But I have been tempted to do it just to be able to play around with the phone more.
So along with this.. is this hardware mismatch issue something I managed to avoid by doing the unlocked bootloader and Sim unlock months ago? Whenever I've tinkered and messed something up I've just used the first release patched msmtool to fix it followed by flashing whatever the latest update is and I've never had any issues. I also keep the first release bootloader unlocked and rooting tool from here and again have had no issues unlocking and rerouting. Can someone clarify what circumstances this hardware mismatch is occurring in so that I can avoid it if possible..
Jeffro64 said:
Another thing also...I found that just doing the lighter OTA updates that I would sometimes run into some kind of bug here and there. Like after I did the OB14 OTA my FP sensor was buggy as hell..
Click to expand...
Click to collapse
That's why I usually do the full fastboot / TWRP flash, as I have been dealing with somewhat oblivious bugs and obvious ones on OTA updates before, and in rare case, it can actually brick a phone. AES 256 / SHA 256 encryption checksums are usually useless in special cases like OTA updates because you will never know what you get. Like that fingerprint scanner bugs.
Also, Jestyr8, you are good, that warning only have occurred recently, but sometimes bootloader can be pretty weird that it allows the specific OS to boot without warning. I am wondering if wiping the modem configuration to remove that SIM lock affects the Linux kernel in a way that it thinks that it's installed on the bona fide international version (A6010) so everything is hunky dory, allowing it to boot up normally. If that was the case, it usually is impossible to patch the SIM configuration, because if they did, they will have hard time assigning the IMEI to it in the factory due to how the Snapdragon modem firmware works (Qualcomm prefer to keep things simple for obvious logistical reasons).
Sent from my OnePlus 6T using Tapatalk