Just like an Agatha Christie novel....and then there was only the one H918 left without oreo.
Welp,
Folks I'm trying out a refurb v30 converted to a US998. May be worth looking into if you want an unlocked bootloader and oreo. So far i haven't had any of the no signal and gps issues I had with H918 either. The overall development scene for that phone though is not as good as v20 and i'm going to miss the regular security patches from lineage.
regards!
I jumped ship to the V30 as well. I am still going to help out with the V20, and G6, and my V20 is still my go to phone if I know I am going to be out and need lots of battery.
Another reason I jumped ship is the fact that the V20 will more than likely never have Treble support. Not from a lack of trying, from the simple fact that some things MUST be in /system and that just doesn't work when a GSI expects things in /vendor.
We could hack it, but it just isn't worth it. The V30 might not have shipped with Treble support, but LG did things a little differently, so it is fairly easy to shoe-horn in Treble.
-- Brian
runningnak3d said:
I jumped ship to the V30 as well. I am still going to help out with the V20, and G6, and my V20 is still my go to phone if I know I am going to be out and need lots of battery.
Another reason I jumped ship is the fact that the V20 will more than likely never have Treble support. Not from a lack of trying, from the simple fact that some things MUST be in /system and that just doesn't work when a GSI expects things in /vendor.
We could hack it, but it just isn't worth it. The V30 might not have shipped with Treble support, but LG did things a little differently, so it is fairly easy to shoe-horn in Treble.
-- Brian
Click to expand...
Click to collapse
Well let me be the first to say thank you for all the support with the v20...and the V10 before it Brian. Was a samsung diehard ever since tmobile for their first galaxy and that junk sk4g but when the s6 had no removable battery or expandable storage i needed to find a change. You have made both of these overpriced, under supported LG phones servicable for myself and i would guess most everyone that invested in the V series. My new replacement V20 has had a junk screen since day 1 and it is completely unresponsive to touch in twrp so im done with the V20. I may be making that V30 jump with you in the next week or two. Im sure a year from now we will be right back here talkin lack of android pie for the tmo v30 lol
GSI Android Pie images already work fairly well on the V30.
With Treble and root, you don't need the OEM anymore.
-- Brian
runningnak3d said:
GSI Android Pie images already work fairly well on the V30.
With Treble and root, you don't need the OEM anymore.
-- Brian
Click to expand...
Click to collapse
Which variant is the best to grab for Root and Rom support? (I have T-Mobile btw)
So, I ordered an H918 from an eBay seller a few days ago, it'll be here mid-next week. Yeah, I know, it's older but dammit it's the removable battery and other aspects that still make it a great device for someone like me. Sure, the audio is fantastic, the screen should be OK - the one I bought was stated as having HEAVY FAIR USAGE so I expect the body of it to be pretty banged up in terms of cosmetic issues, dents, scratches. They didn't say what the condition of the screen/display glass is so I can only hope, they simply say it has signs of very heavy usage and that it's 100% functional so I'll find out soon enough - they do have a 30 day return window (15% restocking fee unless it's defective which of course it would be if I decide to return it <hint, hint>).
Anyway, so I've spent the past 2-3 days reading up as much as I can before I get into this. I grabbed the 10p KDZ file for safe keeping (I really wish the people sharing such files would use MD5/SHA1 checksums and post those along with the links to the files so we can check to make sure things are fine after the download of multi-gigabyte sized files, but that's another thread altogether). Been reading up on all the ins and outs with the H918, the rooting potential for Nougat builds, yes I know Oreo has no root yet and I just read yesterday someone chatted with T-Mobile or LG support and were told the H918 should be getting Oreo official in the next week or so (meaning the very end of September). I've never used a device with Oreo on it so far so I'm not even sure I'll want it.
I've been reading reports from some folks with Oreo on other variants saying it turned their V20 into an almost new different device, and of course other people saying it's crap and ruined their device so there's no way to know for sure till the H918 gets it - it's a given that the H918 will get Oreo, but for now it's still the waiting game from T-Mobile.
As long as the one I ordered works I'm good I suppose. I don't even care all that much about rooting except for one or two things, but I was interested in putting LineageOS on it at least for testing purposes so I've been reading up on all that as well (meaning 14.1 as again I don't have any experience with Oreo so far and probably not all that interested).
I ordered a half-decent camo styled case for it (rip off Slim Armor it looks like), screen protectors (presuming the glass isn't damaged so badly that a protector won't bubble up or just look terrible on it), and a new battery (no idea what the manufacturing date on it will be till it gets here). I have a Quick Charger available but I still don't like doing that to batteries so I'll just keep using my trusty Samsung 2A charger and do it the slow way. I'd love to get the LG battery cradle and order another battery but the pricing on that simple piece of white plastic is utterly ridiculous so, nope, not gonna do it.
As I'm late to the V20 party I suppose I'll say I'm grateful to those that have provided support up to this point with keeping it alive, I'll also say I'm sad that many of them, including runningnak3d seem to be moving on to newer more capable devices (can't say I blame them considering LG being so damned slow - 2 years of Nougat and then Oreo at EOL for the V20, geezus, that's pretty damned bad to be honest).
I hope I'll be able to make something good out of this device. The days of getting custom ROMs like LineageOS on carrier hardware is getting worse all the time. I just wish I had a device like a V20 - with all the features it has, the removable battery, microSD, good/great camera (I still say the camera assembly in the G4 is the best ever but that's just me), outstanding audio features, etc - that allowed for easy custom ROMs like LineageOS or whatever without having to jump through all the hoops.
If OnePlus would make a device with a removable battery and a microSD slot, I'd be all over it day one (and I've never purchased a new smartphone, I always buy used), but of course they'll never ever do such a smart thing unfortunately.
My hope is that I can get LineageOS 14.1 on it working smoothly with a decent kernel that gives me some more capable control over things, while still being as close to 100% functional as possible without any major hassles or problems. If I can do that I'm good. I was never a big huge fan of the second screen (had a V10 for a while as well and kept it turned off), nor a big huge fan of the 32-bit DAC either. I did appreciate the AOP mics for live recording, however, so I'd guess those are still functional with LOS but I guess I'll find out. My ears aren't what they used to be and since I transcoded my entire 2300+ CD collection to Opus 128 Kbps a few years ago, that's good enough for me.
Battery life will be a concern I suppose, but I owned a Samsung Galaxy S7 Active a few years back, Snapdragon 820 powered, and I was getting just shy of 2 full days of battery life with how I use my devices. I know some folks say the V20 is fantastic in that respect and just as many say it sucks so again I'll find out when I get the device and get started with it. I can't imagine it's that bad with a custom kernel and some of the thermal configuration adjustments - and yes I do plan to redo the thermal paste as well, that's near the top of the to-do list.
Anyway, too long post coming to a close: I'll see what happens. I owned a Sprint V20 for a short period of time just over a year ago, and I was able to use it with T-Mobile (my carrier of choice) without many issues but of course it being so tightly locked down (at that time) I didn't choose to keep it. The H918 offers at least more potential for experimenting so again, thanks to those of you that have done things in terms of development to make it better whenever possible.
lowridincrew said:
Which variant is the best to grab for Root and Rom support? (I have T-Mobile btw)
Click to expand...
Click to collapse
All V30s are currently rootable, however, if they increment ARB then that will go away. The H932 will stay rootable unless they make massive changes to the bootloader (that is the TMO variant).
As always, your safest bet is to get an unlocked model (US998), but if you want band 71 (600Mhz) on TMO, then you have to get an H932.
-- Brian
br0adband said:
My hope is that I can get LineageOS 14.1 on it working smoothly with a decent kernel that gives me some more capable control over things, while still being as close to 100% functional as possible without any major hassles or problems. If I can do that I'm good. I was never a big huge fan of the second screen (had a V10 for a while as well and kept it turned off), nor a big huge fan of the 32-bit DAC either. I did appreciate the AOP mics for live recording, however, so I'd guess those are still functional with LOS but I guess I'll find out. My ears aren't what they used to be and since I transcoded my entire 2300+ CD collection to Opus 128 Kbps a few years ago, that's good enough for me.
.
Click to expand...
Click to collapse
I would recommend you stick with rooted stock. I never got a decent camera working with lineage 14.1, had bluetooth problems with disappearing bluetooth mac, and signal and gps issues to just name a few. Although going back to stock fixed all of these (except for at&t cell signal). The US998 LG v30 is a far better phone (band 30 and 71 support will always be a problem on the non-carrier phones apparently).
Also be aware that the current 14.1 lineage stock is only for radios BEFORE 10p or ARB0. It does not work on ARB1. I think at ARB1 your only option is the lineage 15 unofficial rom.
runningnak3d said:
As always, your safest bet is to get an unlocked model (US998), but if you want band 71 (600Mhz) on TMO, then you have to get an H932.
-- Brian
Click to expand...
Click to collapse
Doesn't the unlocked model have the proper antenna for band 71? So is this just a software issue. I was looking into getting a V30 and I thought I read a thread in the V30 forums that it works with a T-Mobile SIM? You would know better than I would so If you don't mind clarifying this if you could I would appreciate it as I'm still interested in a V30 and am on TMobile and band 71 would be a buying decision for me.
Without a US998 to run some tests, I can't say for sure, but I believe the modem firmware is the limiting factor, and you can't flash H932 modem on the US998 due to the different RSA key.
-- Brian
KUSOsan said:
Doesn't the unlocked model have the proper antenna for band 71? So is this just a software issue. I was looking into getting a V30 and I thought I read a thread in the V30 forums that it works with a T-Mobile SIM? You would know better than I would so If you don't mind clarifying this if you could I would appreciate it as I'm still interested in a V30 and am on TMobile and band 71 would be a buying decision for me.
Click to expand...
Click to collapse
The US998 V30 that everyone including me is using does not have band 30 or 71. Both are disabled through the lack of the correct modem firmware. The tmobile variants all use different rsa keys and have been much more difficult to root or get roms for, but they would then have the right radio band enabled for tmobile. Within the last few days there has been an root and bootloader unlock method for the h932. Apparently its difficult and risky right now.
I was using the h918 on at&t because it was already bootloader unlocked via fastboot, but the signal was horrible on at&t.
For the v30, the options are 1) use the carrier phone H932 and deal with the bootloader unlock issues or 2) get the unlocked US998 and deal with bands missing band 30 for att and 71 for tmobile
For the v20, the H918 was the last of its kind with unlocked bootloader, removable battery, sdcard support, and the right radios for tmobile. You just had to deal with lack of updates from the carrier...ie still no oreo even though att/verizon/sprint varriants all have oreo now. And the different RSA keys have prevented cross flashing of roms.
Hope this helps
Rooting the H932 is as safe as rooting the H918 now...
-- Brian
runningnak3d said:
All V30s are currently rootable, however, if they increment ARB then that will go away. The H932 will stay rootable unless they make massive changes to the bootloader (that is the TMO variant).
As always, your safest bet is to get an unlocked model (US998), but if you want band 71 (600Mhz) on TMO, then you have to get an H932.
-- Brian
Click to expand...
Click to collapse
What's different on the Sprint v30 ? ARB 0?
zeusofyork said:
What's different on the Sprint v30 ? ARB 0?
Click to expand...
Click to collapse
If you mean why can the Sprint V30 be rooted and not the Sprint V20? ARB is definitely part of it...
There was a massive hole found in the Oreo abl (aboot) on the V30 that allowed them to flash a bogus unlock.bin file to unlock their bootloader if they flashed the US998 abl.
Just like the V20, if any of the carriers decide to increment ARB, that hole goes away. It appears that they are allowing people that unlocked their bootloader to keep the unlock even after patching it, but if ARB is incremented and you aren't already rooted, then you won't be able to rollback to the version that has the exploit.
So, my advice stands. If you are going to buy a V30, either get the US998, or get an H932. It is up in the air as to how long the others will be rootable, so if you had to send your phone back for a repair, and they ship it back with patched firmware that had ARB incremented, you are boned.
-- Brian
runningnak3d said:
If you mean why can the Sprint V30 be rooted and not the Sprint V20? ARB is definitely part of it...
There was a massive hole found in the Oreo abl (aboot) on the V30 that allowed them to flash a bogus unlock.bin file to unlock their bootloader if they flashed the US998 abl.
Just like the V20, if any of the carriers decide to increment ARB, that hole goes away. It appears that they are allowing people that unlocked their bootloader to keep the unlock even after patching it, but if ARB is incremented and you aren't already rooted, then you won't be able to rollback to the version that has the exploit.
So, my advice stands. If you are going to buy a V30, either get the US998, or get an H932. It is up in the air as to how long the others will be rootable, so if you had to send your phone back for a repair, and they ship it back with patched firmware that had ARB incremented, you are boned.
-- Brian
Click to expand...
Click to collapse
Hahah where theres a will theres (sometimes) a way. Well unintentional or not that's pretty sweet. Sucks for people finding out after the fact though. I just figure they should allow people to unlock but sign some release saying you accept xyz if something bad happens. Win win in my book.
Yeah that's what happened to me. I did a test flash for Alpha and bricked my v20. Got it back and had from LG and it was ZVD. I'm looking at my options now.
I really wish OnePlus or another owner-friendly device maker would make a device I want. Treble helps, and hopefully someone will make something like that. No more sealed batteries for me. I would probably still be running my Nexus 6 if it were not for that. Though it was getting a bit slow toward the end. I could replace the battery, but it's tough to find good replacement batteries for these sealed units. With the V20, some reputable battery makers have models available and it's easy to swap them should I get a bad one. I don't have to heat up the glue to open the thing.
runningnak3d said:
Rooting the H932 is as safe as rooting the H918 now...
-- Brian
Click to expand...
Click to collapse
Unless you are on tmobile and only plan on ever using tmobile, i wouldn't by another tmobile phone. They have become impossible to sim unlock and they used different encryption keys making them difficult to work with. And if I'm not mistaken they were the only carrier to increment to arb1 causing even more headaches with rom flashing...and what started this whole post. The v20 h918 still does not have oreo. The last one possibly. Probably because they locked down the phone so much with different rsa keys and radios that they can't use the stock roms that lg puts out?
Alibaba0101 said:
Unless you are on tmobile and only plan on ever using tmobile, i wouldn't by another tmobile phone. They have become impossible to sim unlock and they used different encryption keys making them difficult to work with.
Click to expand...
Click to collapse
Yeah I was hoping there was a way to use the band 71 on the unlocked phones but how are they impossible to sim unlock? All I did was run the unlock app that comes with the TMobile firmware
KUSOsan said:
Yeah I was hoping there was a way to use the band 71 on the unlocked phones but how are they impossible to sim unlock? All I did was run the unlock app that comes with the TMobile firmware
Click to expand...
Click to collapse
If you want to get a phone that supports band 71, then most likely you are already on tmobile and can have tmobile sim unlock the phone for your before you root it or unlock the bootloader.
If you don't have a tmobile account, the problem is that there is currently no vendor that supports sim unlocking tmobile phones that use the tmobile unlock app. Tmobile has switched to using their own unlock app which only works with tmobile customers.
There are several places that will SIM unlock T-Mobile phones for $10.00 or less. If I can get enough EFS dumps of before and after I will eventually be able to figure out how they do it.
In the meantime, I think $10 to have your phone unlocked is not unreasonable. I have tested two separate services, and they both worked flawlessly. One was used on the V20, and one on the V30.
-- Brian
Related
Hi..
Since I live outside of the US, this is the only way to install system updates as far as I know (OTA doesn't work), so I'm wondering, is there are any special procedures that should be taken before flashing the firmware? There is a dedicated thread for how to do that on the D855's forum (Link http://forum.xda-developers.com/showthread.php?p=53452990#post53452990) ,however, the mysterious lack of any threads like that in D850 forums has made me worried a little bit, especially that I've read somewhere that non international versions of the device comes with a locked boot-loader which can complicate things sometimes (The one that I have is network unlocked (obviously)).
Sorry if this is a dumb question or something like that, but I've never used/owned any of LG devices, plus the device is for my little sister so I can't take any chances even with something like soft break since it will totally freak her out, plus I've tried to use forum search box many times before asking, but it totally failed me however.
Thanks in advance.
ramy670 said:
Hi..
Since I live outside of the US, this is the only way to install system updates as far as I know (OTA doesn't work), so I'm wondering, is there are any special procedures that should be taken before flashing the firmware? There is a dedicated thread for how to do that on the D855's forum (Link http://forum.xda-developers.com/showthread.php?p=53452990#post53452990) ,however, the mysterious lack of any threads like that in D850 forums has made me worried a little bit, especially that I've read somewhere that non international versions of the device comes with a locked boot-loader which can complicate things sometimes (The one that I have is network unlocked (obviously)).
Sorry if this is a dumb question or something like that, but I've never used/owned any of LG devices, plus the device is for my little sister so I can't take any chances even with something like soft break since it will totally freak her out, plus I've tried to use forum search box many times before asking, but it totally failed me however.
Thanks in advance.
Click to expand...
Click to collapse
Yea that model you'll use the tot method. But you cannot get lollipop unless you have an active att sim. Or use a custom rom sadly.
Sent from my iPhone using Tapatalk
Pretty much you are stuck with doing custom ROMs. The only TOT file that I'm aware of floating officially or in the wild for the D850 AT&T is for KK. OTA is the only way to update past KK in terms of official updates, which of course requires an AT&T sim card.
Sent from my awesome phone.
Thanks for the replies..
But you cannot get lollipop unless you have an active att sim.
Click to expand...
Click to collapse
Does it suffice to only have an active SIM in order to "activate" OTA updates and then download them through WiFi? Or must the OTA update also be downloaded exclusively through AT&T's data connection? Because they sell AT&T SIM cards on eBay with international shipping for pretty cheap prices, and of course I'll have to activate some prepaid one-time plan that includes global roaming (unless it is already embedded in all plans and you have to pay extra only when you use calls, data or SMS etc, I'll be sure to check their website if you tell me that it works). Global data plans however are too expensive to pay for for such a thing, 800 MB plan costs around 120 $, So my only practical option here is to update through WiFi, while AT&T SIM is inserted (if that works).
The only TOT file that I'm aware of floating officially or in the wild for the D850 AT&T is for KK.
Click to expand...
Click to collapse
I think the flashing guide that I've put the link to does contain what seems to be D850's Lolipop ROM, you can find it here:
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/AT&T+D850/
Am I missing something?
Thanks.
What about this one also?:
http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041
I don't know if it is going to do any good, and I don't know if this applies to other carriers, but it certainly can't hurt...
I just typed this up and submitted it to the FCC Consumer Complaint Center: https://consumercomplaints.fcc.gov/hc/en-us
I purchased a phone from AT&T outright (not through a contract). This phone (LG V20) uses LTE B17 (700Mhz). As part of the auction of the class C spectrum, it was stated that:
"Handset locking prohibited. No licensee may disable features on handsets it provides to customers, to the extent such features are compliant with the licensee’s standards pursuant
to paragraph (b) of this section, nor configure handsets it provides to prohibit use of such handsets on other providers’ networks."
By AT&T locking and signing the bootloader of my phone, they are in violation of that clause.
I am no longer an AT&T customer, and am not using the phone on their network. I would like them to provide me with the OEM unlock code for my phone.
Please keep in mind that this is NOT the carrier unlock code so that the phone can be used on other carriers ...
this is the boot loader unlock code so that I can install a ROM that matches the carrier I am using (T-Mobile).
Lastly I would like to point out that AT&T does NOT make it clear that their boot loaders are locked with no way to unlock them or
I would never have purchased the phone from them.
Thank you,
-- Brian
I encourage anyone that has an AT&T v20 to submit something similar. I don't have the money to sue them, or I would because they ARE in violation since they use LTE B17.
I've been planning on getting the US996 anyway. Maybe others should do the same if they use AT&T or any of its MVNOs. Its also much cheaper: the H910 is $830+.
runningnak3d said:
I don't know if it is going to do any good, and I don't know if this applies to other carriers, but it certainly can't hurt...
I just typed this up and submitted it to the FCC Consumer Complaint Center: https://consumercomplaints.fcc.gov/hc/en-us
I purchased a phone from AT&T outright (not through a contract). This phone (LG V20) uses LTE B17 (700Mhz). As part of the auction of the class C spectrum, it was stated that:
"Handset locking prohibited. No licensee may disable features on handsets it provides to customers, to the extent such features are compliant with the licensee’s standards pursuant
to paragraph (b) of this section, nor configure handsets it provides to prohibit use of such handsets on other providers’ networks."
By AT&T locking and signing the bootloader of my phone, they are in violation of that clause.
I am no longer an AT&T customer, and am not using the phone on their network. I would like them to provide me with the OEM unlock code for my phone.
Please keep in mind that this is NOT the carrier unlock code so that the phone can be used on other carriers ...
this is the boot loader unlock code so that I can install a ROM that matches the carrier I am using (T-Mobile).
Lastly I would like to point out that AT&T does NOT make it clear that their boot loaders are locked with no way to unlock them or
I would never have purchased the phone from them.
Thank you,
-- Brian
I encourage anyone that has an AT&T v20 to submit something similar. I don't have the money to sue them, or I would because they ARE in violation since they use LTE B17.
Click to expand...
Click to collapse
You may want to do some more research on this as from what you posted this applies to locking it to their Network. Basically, they can lock the bootloader or whatever but they can't lock the device to their Network. Verizon entered a similar deal when they got B13 LTE. That's why any Verizon phone thinking B13 has to be able to run on other networks as well, but they lock their bootloader's as the two have nothing to do with each other. Also, companies are not required to make it known that they lock their bootloader's and don't allow you to unlock them, that's where you have to do your own research before buying a phone. If you've been on XDA for a good amount of time, you'd have known to stay away from at&t as they have a long history of bootloader locking. Your best bet is usually unlocked devices (Nexus, HTC unlocked, etc.) or even most T-Mobile devices (and btw T-Mobile devices pretty much share same bands as at&t). But anyways, hopefully you get something from them although I highly doubt it. Like I said, from the wording it appears this only applies to Network locking not being allowed.
jeffsga88 said:
You may want to do some more research on this as from what you posted this applies to locking it to their Network. Basically, they can lock the bootloader or whatever but they can't lock the device to their Network. Verizon entered a similar deal when they got B13 LTE. That's why any Verizon phone thinking B13 has to be able to run on other networks as well, but they lock their bootloader's as the two have nothing to do with each other. Also, companies are not required to make it known that they lock their bootloader's and don't allow you to unlock them, that's where you have to do your own research before buying a phone. If you've been on XDA for a good amount of time, you'd have known to stay away from at&t as they have a long history of bootloader locking. Your best bet is usually unlocked devices (Nexus, HTC unlocked, etc.) or even most T-Mobile devices (and btw T-Mobile devices pretty much share same bands as at&t). But anyways, hopefully you get something from them although I highly doubt it. Like I said, from the wording it appears this only applies to Network locking not being allowed.
Click to expand...
Click to collapse
I did do some research, even had a lawyer look at the wording. It is ambiguous, and in contract law, any clause that is ambiguous benefits that signee. Now, this is not contract law, but there is hope
Yes, I will be getting a reply from AT&T -- received this from the FCC today:
Hi William,
Your Ticket No. XXXXXXX was served on AT&T Wireless on Apr 13 for its review and response.
AT&T Wireless will likely contact you in an effort to resolve your issue.
A response is due to the FCC no later than 30 days from today. AT&T Wireless will respond to you directly by postal mail.
You can view a list of frequently asked questions at: https://consumercomplaints.fcc.gov/hc/en-us/articles/205082880.
We appreciate your submission and help in furthering the FCC’s mission on behalf of consumers.
I will update this post when I get the reply from AT&T. It would be in their best interest to just give me the OEM unlock code. What is funny is that I don't even want to run a custom ROM, I just want to remove the AT&T bloatware (#1 - it is bloatware, #2 - I am not on AT&T anymore so I couldn't use it if I wanted to).
Also, yes, I have been on XDA for quite some time, and am very familiar with AT&T and Verizon A-Hole policies concerning bootloaders. This was a deal that I just couldn't pass up.
Also, I know that there is a debug boot loader for the US996 that can be flashed using dirty santa, but that is NOT acceptable without a KDZ. I got a good deal on the phone, not a GREAT one
runningnak3d said:
I did do some research, even had a lawyer look at the wording. It is ambiguous, and in contract law, any clause that is ambiguous benefits that signee. Now, this is not contract law, but there is hope
Also, yes, I have been on XDA for quite some time, and am very familiar with AT&T and Verizon A-Hole policies concerning bootloaders. This was a deal that I just couldn't pass up.
Also, I know that there is a debug boot loader for the US996 that can be flashed using dirty santa, but that is NOT acceptable without a KDZ. I got a good deal on the phone, not a GREAT one
Click to expand...
Click to collapse
Yes, the wording is ambiguous. Hopefully you get a good resolution out of this, but I wouldn't be surprised if they just responded stating that it has to do with network locking, but again hopefully that's not the case as it would be a major step forward if they just unlocked the bootloader. However, is not as simple as giving you an unlock code unless things really changed from G5 to V20. On G5, fastboot was completely disabled on AT&T. So, if that's the case with the V20, they would have to push an update to enable fastboot and allow using the unlock.bin file lg provides (and lg would have to add support for it to be unlocked from their site) or they could just be nice and push an update to enable fastboot oem unlock
As far as the kdz for AT&T, did you check this:
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOURIMEMHERE
Just try putting your imei in and see if it gives you a kdz file key or not. Can't try as I don't have an imei for at&t.
Anyways, best of luck and hopefully you get a good resolution from your complaint against them
jeffsga88 said:
Yes, the wording is ambiguous. Hopefully you get a good resolution out of this, but I wouldn't be surprised if they just responded stating that it has to do with network locking, but again hopefully that's not the case as it would be a major step forward if they just unlocked the bootloader. However, is not as simple as giving you an unlock code unless things really changed from G5 to V20. On G5, fastboot was completely disabled on AT&T. So, if that's the case with the V20, they would have to push an update to enable fastboot and allow using the unlock.bin file lg provides (and lg would have to add support for it to be unlocked from their site) or they could just be nice and push an update to enable fastboot oem unlock
As far as the kdz for AT&T, did you check this:
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOURIMEMHERE
Just try putting your imei in and see if it gives you a kdz file key or not. Can't try as I don't have an imei for at&t.
Anyways, best of luck and hopefully you get a good resolution from your complaint against them
Click to expand...
Click to collapse
You know I didn't check to see if fastboot was disabled, but as you said, if they are going to grant my request they WILL find a way even if that means me taking my phone to AT&T and them giving me a US996
As for the KDZ, thanks, but that is the first thing that I did. From what I understand, due to the contracts that LG has with AT&T and Verizon, they aren't allowed to distribute the KDZ. After this experience, even with a GREAT deal, I will never do business with AT&T, Verizon, or Sprint ever again. I have NEVER had a locked boot loader on T-Mobile, and their network coverage is getting better and better (just had a fairly major auction win).
runningnak3d said:
You know I didn't check to see if fastboot was disabled, but as you said, if they are going to grant my request they WILL find a way even if that means me taking my phone to AT&T and them giving me a US996
As for the KDZ, thanks, but that is the first thing that I did. From what I understand, due to the contracts that LG has with AT&T and Verizon, they aren't allowed to distribute the KDZ. After this experience, even with a GREAT deal, I will never do business with AT&T, Verizon, or Sprint ever again. I have NEVER had a locked boot loader on T-Mobile, and their network coverage is getting better and better (just had a fairly major auction win).
Click to expand...
Click to collapse
check the dirty elf thread i was able to convert my h910 to the us996 model
runningnak3d said:
You know I didn't check to see if fastboot was disabled, but as you said, if they are going to grant my request they WILL find a way even if that means me taking my phone to AT&T and them giving me a US996
As for the KDZ, thanks, but that is the first thing that I did. From what I understand, due to the contracts that LG has with AT&T and Verizon, they aren't allowed to distribute the KDZ. After this experience, even with a GREAT deal, I will never do business with AT&T, Verizon, or Sprint ever again. I have NEVER had a locked boot loader on T-Mobile, and their network coverage is getting better and better (just had a fairly major auction win).
Click to expand...
Click to collapse
Yeah, have to agree never will get a phone from AT&T, Verizon or Sprint, and even T-Mobile might not be a great choice in the future. With the G5, V20 and now the G6, even though T-MOBILE allows you to unlock the bootloader via fastboot, they've disabled the fastboot boot and flash commands. On G5 and V20 there were still options using dirtycow or flashing unsigned tot files for the G5, although that appears to have been patched by LG. The G6 T-Mobile version has the same thing fastboot oem unlock, yet they can't root or install twrp because the fastboot flash and boot commands were disabled and dirtycow was patched. Looking like only way to go is completely unlocked non carrier phones, sucks because there's usually no deals on those phones :crying: Another thing for the kdz would be to try using lg bridge and see if it finds the software, if it does it should create a log file with the web address of the kdz (although you may have to use something to monitor web traffic to see where it's connecting for the file). Hopefully that works, if not though not sure how else to get one (technically they're not distributing the kdz using this method as it is only to restore or update the device and doesn't give you the location unless you know where to look).
jerrycoffman45 said:
check the dirty elf thread i was able to convert my h910 to the us996 model
Click to expand...
Click to collapse
That isn't a typo? I thought Dirty Elf was only for the h915 not the h910 (unless the us996 kdz has been successfully tested on the h910). Will have to give the thread a read again.
jeffsga88 said:
Yeah, have to agree never will get a phone from AT&T, Verizon or Sprint, and even T-Mobile might not be a great choice in the future. With the G5, V20 and now the G6, even though T-MOBILE allows you to unlock the bootloader via fastboot, they've disabled the fastboot boot and flash commands. On G5 and V20 there were still options using dirtycow or flashing unsigned tot files for the G5, although that appears to have been patched by LG. The G6 T-Mobile version has the same thing fastboot oem unlock, yet they can't root or install twrp because the fastboot flash and boot commands were disabled and dirtycow was patched. Looking like only way to go is completely unlocked non carrier phones, sucks because there's usually no deals on those phones :crying: Another thing for the kdz would be to try using lg bridge and see if it finds the software, if it does it should create a log file with the web address of the kdz (although you may have to use something to monitor web traffic to see where it's connecting for the file). Hopefully that works, if not though not sure how else to get one (technically they're not distributing the kdz using this method as it is only to restore or update the device and doesn't give you the location unless you know where to look).
Click to expand...
Click to collapse
Using LG bridge is an awesome idea *smacks head*. Yea, setting up a sniffer isn't a problem. I will test that as soon as I get home.
If the US996 KDZ has been tested on the V20, and I can get the location / copy of the H910 KDZ then I will no longer have any issues rooting. Great thing about LG phones -- can't brick them as long as you have a KDZ
runningnak3d said:
That isn't a typo? I thought Dirty Elf was only for the h915 not the h910 (unless the us996 kdz has been successfully tested on the h910). Will have to give the thread a read again.
Using LG bridge is an awesome idea *smacks head*. Yea, setting up a sniffer isn't a problem. I will test that as soon as I get home.
If the US996 KDZ has been tested on the V20, and I can get the location / copy of the H910 KDZ then I will no longer have any issues rooting. Great thing about LG phones -- can't brick them as long as you have a KDZ
Click to expand...
Click to collapse
not a typo i have done this only thing you probably would not be able to use lg website to unlock the bootloader because the imei would be for a h910 edit: and i am not sure if you would get otas when i tried it said the phone was not registered
runningnak3d said:
Using LG bridge is an awesome idea *smacks head*. Yea, setting up a sniffer isn't a problem. I will test that as soon as I get home.
If the US996 KDZ has been tested on the V20, and I can get the location / copy of the H910 KDZ then I will no longer have any issues rooting. Great thing about LG phones -- can't brick them as long as you have a KDZ
Click to expand...
Click to collapse
Well, hopefully that will work for getting the kdz. Oh, and most times you can't brick LG phones, but... It is still possible to do and even a kdz won't help (Qualcomm 9008 mode or whatever it is).
I went through this same thing with ATT when I had a GS5. Basically their reply was no we aren't going to do anything. Then one of their managers called me, and they gave me a free LG G3.
Interesting, I have 2 H910s on T-Mo network since 3/30/17
runningnak3d said:
I don't know if it is going to do any good, and I don't know if this applies to other carriers, but it certainly can't hurt...
I just typed this up and submitted it to the FCC Consumer Complaint Center: https://consumercomplaints.fcc.gov/hc/en-us
I purchased a phone from AT&T outright (not through a contract). This phone (LG V20) uses LTE B17 (700Mhz). As part of the auction of the class C spectrum, it was stated that:
"Handset locking prohibited. No licensee may disable features on handsets it provides to customers, to the extent such features are compliant with the licensee’s standards pursuant
to paragraph (b) of this section, nor configure handsets it provides to prohibit use of such handsets on other providers’ networks."
By AT&T locking and signing the bootloader of my phone, they are in violation of that clause.
I am no longer an AT&T customer, and am not using the phone on their network. I would like them to provide me with the OEM unlock code for my phone.
Please keep in mind that this is NOT the carrier unlock code so that the phone can be used on other carriers ...
this is the boot loader unlock code so that I can install a ROM that matches the carrier I am using (T-Mobile).
Lastly I would like to point out that AT&T does NOT make it clear that their boot loaders are locked with no way to unlock them or
I would never have purchased the phone from them.
Thank you,
-- Brian
I encourage anyone that has an AT&T v20 to submit something similar. I don't have the money to sue them, or I would because they ARE in violation since they use LTE B17.
Click to expand...
Click to collapse
Our problem exactly! I have 2 H910s on the T-Mobile network. It would be great to receive the bootloader unlock code or even if they could unlock it for us and allow us to go on about our business. Have you gotten a response?
wayne8821212 said:
Our problem exactly! I have 2 H910s on the T-Mobile network. It would be great to receive the bootloader unlock code or even if they could unlock it for us and allow us to go on about our business. Have you gotten a response?
Click to expand...
Click to collapse
I received a phone call, and the guy was actually knowledgeable. Basically he said AT&T's interpretation of that clause is exactly what we have assumed -- prevent locking to a carrier. That is just messed up since there was already a law in place to prevent them from doing that if the phone was paid for and the contract satisfied. It really sucks I don't have the money to fight this in court or I would.
They have 10 days in which to send me something in writing stating their reasons, and I have not received it yet.
However, I have opened another complaint and this one might have some more teeth. Because I am on T-Mobile, I can not receive any updates for my phone (H918 update won't work on an H910), and that most certainly is locking out functionality. I am not going to buy an AT&T Go Phone SIM just to update my phone. We will see where that goes.
I was informed that they couldn't give me an unlock code even if they were instructed to, because fastboot isn't even in the bootloader -- it is not just disabled (so no fastboot oem unlock blah.bin).
-- Brian
I think about the best I can hope for is they get tired of me and give me a refund even though I purchased the phone from a third party.
Wow why you all quoting so much???
A little editing makes the thread easier to read...
I was tempted to swap our H910s for 2 H918s but understandably T-Mobile wants $480 (down from$679) for the H918 and are only offering like $160 per H910.
Sent from my LG-H910 using XDA-Developers Legacy app
It's really not vague, it's telling you that this is pursuant to paragraph b which says
(b)Use of devices and applications. Licensees offering service on spectrum subject to this section shall not deny, limit, or restrict the ability of their customers to use the devices and applications of their choice on the licensee's C Block network, except:
(1) Insofar as such use would not be compliant with published technical standards reasonably necessary for the management or protection of the licensee's network, or
(2) As required to comply with statute or applicable government regulation.
in other words, it has nothing to do with bootloaders and everything to do with restricting network access. I'm guessing your lawyer friend doesn't work with this kind of law or maybe you just showed him section e without section b or something. try not to clog up the fcc with your misunderstandings though, we are trying to clog them up with net neutrality complaints which are more important than your misreading of fcc regulations.
I have an S20U now that is unlocked. What I love is that I get the updates faster it seems (although, the S20 has had way more updates than normal). I am thinking of getting the branded Tmobile one, I have never had any issues using their software and it seems to work better on the network. I do not honestly care about "bloatware" as I will at least be getting a 256GB model.
Anyone have any experiences either way?
I don't have any experience with TMO specifically, but what I do know is that typically the carrier branded devices get their updates WAY fast and more often than the Unlocked ones. I'm in the same boat, I don't really care much one way or another about the bloat. If I don't like it I uninstall it if I can or at the very least disable it
kangi26 said:
I don't have any experience with TMO specifically, but what I do know is that typically the carrier branded devices get their updates WAY fast and more often than the Unlocked ones. I'm in the same boat, I don't really care much one way or another about the bloat. If I don't like it I uninstall it if I can or at the very least disable it
Click to expand...
Click to collapse
It is my understanding that the unlocked one can be used in any country and any network. Just switch sim card and you are done. The TMobile one, may be locked until you pay off the device. You also don't get the bloatware with unlocked (one less thing to Uninstall if you don't care for it).
Sent from my SM-N976U 5G using XDA-Developers Legacy app
Eudeferrer said:
It is my understanding that the unlocked one can be used in any country and any network. Just switch sim card and you are done. The TMobile one, may be locked until you pay off the device. You also don't get the bloatware with unlocked (one less thing to Uninstall if you don't care for it).
Sent from my SM-N976U 5G using XDA-Developers Legacy app
Click to expand...
Click to collapse
There are 2 "Kinds" of Unlocked, you're referring to SIM unlocked, the other is the U1 devices sold by Samsung. Which I suspect what the OP is referring to
kangi26 said:
typically the carrier branded devices get their updates WAY fast and more often than the Unlocked onest
Click to expand...
Click to collapse
That used to be true, but not for the last couple of years. The unlocked US Note10+ (N975U1), for example, has gone through 18 software releases in the 12 months it's been out. Many of its updates came out within the first few days of the month, and included that month's Android security patch.
T-Mobile has been lagging for the past few months in its updates for both the N975U and the N975U1, but you can manually download and flash the latest unlocked software immediately.
Also, it is my understanding that Tmobile tweaks it's cellular radio's to perform slightly better than the unlocked version of any phone used on it's network.
From my experience, AT&T, the branded phones have the extras like wifi calling and VoLTE enabled and the unlocked ones don't. Some of the video call features are missing. I wouldn't have a problem with the bloatware but AT&T seems to force it back on and there is no way to remove it without root (which i don't do anymore). This has been my experience from Note 5 , 2 of the 7's ,note 8 and the note 9 I currently use, all have been unlocked.
Sent from my Samsung SM-N960U1 using XDA Labs
Unlock has free caller ID builtin, Tmobile you have to pay for it. Unlock has no Tmobile branding or bloatware. Unlock version is easier to bypass tmobile hotspot apn, and usage limits
T-Mobile version has video calling on the phone app, unlock use to, but not anymore. There might be a few more things but I can't remember right now.
Sent from my SM-N975U1 using Tapatalk
I'm on sprint/tmo but I got the unlocked for the first time because I paid outright for the phone this time
*Omnipresent* said:
Also, it is my understanding that Tmobile tweaks [its] cellular [radios] to perform slightly better than the unlocked version of any phone used on [its] network.
Click to expand...
Click to collapse
Are you referring to the APN settings, or to something else?
https://www.t-mobile.com/support/devices/not-sold-by-t-mobile/byod-t-mobile-data-and-apn-settings
*Omnipresent* said:
Also, it is my understanding that Tmobile tweaks it's cellular radio's to perform slightly better than the unlocked version of any phone used on it's network.
Click to expand...
Click to collapse
This simply isn't true with the Samsung phones. I have had both and there definitely is no difference in connectivity in either data or calls between unlocked and carrier version.
Sent from my SM-G986U1 using Tapatalk
agree - that was a bunch of talk on this forum last year when the note 10+ was shipping . lots of cats on here were trying to say this and it was just not true. i had 3 unlocked phones on tmo and service was consistent.
Gary02468 said:
Are you referring to the APN settings, or to something else?
https://www.t-mobile.com/support/devices/not-sold-by-t-mobile/byod-t-mobile-data-and-apn-settings
Click to expand...
Click to collapse
I think he's referring to carrier aggregation. I don't know if it's a thing licked phones have that unlocked don't. I always go unlocked (so the phone feels like it's mine, lol) and can't say I've noticed a difference.
d_ganggreen said:
I have an S20U now that is unlocked. What I love is that I get the updates faster it seems (although, the S20 has had way more updates than normal). I am thinking of getting the branded Tmobile one, I have never had any issues using their software and it seems to work better on the network. I do not honestly care about "bloatware" as I will at least be getting a 256GB model.
Anyone have any experiences either way?
Click to expand...
Click to collapse
Thank you for your post. Does the Wifi Calling on Tmobile work on the Unlocked phone? I am looking at buying the unlocked 512gb model but have to have wifi calling when I am traveling internationally.
Does anyone know if the stock firmware can be flashed on any device if it's factory unlocked? I think the answer is yes, but just want to make sure before I purchase one used. I know your can flash the carrier firmware so I assume you can do the reverse.
ccommcomm said:
Thank you for your post. Does the Wifi Calling on Tmobile work on the Unlocked phone? I am looking at buying the unlocked 512gb model but have to have wifi calling when I am traveling internationally.
Click to expand...
Click to collapse
Yes. and if you follow a few of the guides here you can "unlock" video calling and RCS in Samsung messages as well. And if you are really creative, there is another guide to expanding bands and tweaking receiving antennas
And the last question, if you buy the U1 unlocked, you can flash carrier firmware or unlocked firmware either way all you want, but keep in mind going from u to u1 firmware requires a wipe.
The old "unlocked" was slower to get updates is only true if you wait for Tmobile to release it. If you use Frija and Odin, you can pretty much get it the same day Samsung releases it. I'm too impatient to wait for Tmobile to "get around to" reviewing it and re-releasing what Samsung released weeks before.
Most of the "negatives" of having unlocked are long gone at this point and it tilts more into the positives.
Compusmurf said:
Yes. and if you follow a few of the guides here you can "unlock" video calling and RCS in Samsung messages as well. And if you are really creative, there is another guide to expanding bands and tweaking receiving antennas
And the last question, if you buy the U1 unlocked, you can flash carrier firmware or unlocked firmware either way all you want, but keep in mind going from u to u1 firmware requires a wipe.
The old "unlocked" was slower to get updates is only true if you wait for Tmobile to release it. If you use Frija and Odin, you can pretty much get it the same day Samsung releases it. I'm too impatient to wait for Tmobile to "get around to" reviewing it and re-releasing what Samsung released weeks before.
Most of the "negatives" of having unlocked are long gone at this point and it tilts more into the positives.
Click to expand...
Click to collapse
U and U1 have the same radios in them, they are made specifically for the USA market. Depending on what carrier sim card you insert those bands for said USA carrier will be made available for the user. No need to expand bands. The technical specifications of the U1 and U models are listed on samsung USA website for cross referencing.
Anyone successfully using call recording feature on either version? Still looking for my U.S t-mobile variant..
T-Mo non-unlocked Samsung phones (maybe just the Note 20 Ultra though since I haven't been with Samsung since the Note 3 lol) have a bunch of issues. They're about one month behind on updates when compared to all of the other companies. Additionally, I saw someone mention that they have better mobile data quality. That is also true... I found that out once I manually switched to the Android 11 beta as my 5G speeds went from a constant 130mb/s down to 0.5 - 2mb/s without the firmware being specifically from T-Mo. In my settings, all of the mobile connection stuff is exactly the same as it was before...
Also, I don't have voicemail support. Yet another T-Mo problem (but you can easily add Samsung as a possible cause of that problem too)... Had to switch back to the Google Phone app just so that I could get old-school style voicemail (where you have to call your own phone number to get in).
---------- Post added at 11:29 AM ---------- Previous post was at 11:25 AM ----------
dj24 said:
Anyone successfully using call recording feature on either version? Still looking for my U.S t-mobile variant..
Click to expand...
Click to collapse
This hasn't worked for me either. It's starting to seem like Samsung pushed some of their development onto the phone carriers now lol.
Hey Samsung, why not just leave Android alone when you get it from Google so you don't have to cause so many problems with your own, customized (ad filled, feature removing) version moving forward? Heck, I've already had some problems with a bunch of your apps and have gotten zero help or answers from you guys. That's the reason I've switched back to a bunch of Google apps, however, half of those didn't even work on this phone!!! But I messaged Google about these problems as well, and you know what? They fixed ALL OF THEM within two weeks.
I'll definitely be buying from a different manufacturer moving forward. Even more so since there's rumours spreading around online right now that the Note 20 was the last Note phone to be released since the upcoming S21 is going to have stylus support...
The difference between unlocked and t-mobile is that unlocked gets its updates directly from Samsung and is not branded.
While t-mobile version is branded and you receive the updates from t-mobile and not from Samsung. So delay or longer waiting time on updates would happen and maybe even won't get few of the updates.
Since t-mobile has to release them, which take longer time.
Skickat från min SM-N986B via Tapatalk
Whether you get a carrier version or the factory unlocked U1 model, OEM unlock does not exist on this phone. So those in the US that were thinking of doing custom roms with this cheap new Android device, look elsewhere.
Samsung has blocked their bootloaders on U.S. phone variants for years now. The only way to unlock is with paid service unfortunately.
ShaDisNX255 said:
Samsung has blocked their bootloaders on U.S. phone variants for years now. The only way to unlock is with paid service unfortunately.
Click to expand...
Click to collapse
What service are you referring to? I'd love to unlock mine.
Jay1175 said:
What service are you referring to? I'd love to unlock mine.
Click to expand...
Click to collapse
Well, it was located here: https://forum.xda-developers.com/t/sampwnd-usa-model-bl-unlock-info-u-u1-w.4201689/
But I guess it's temporarily closed until the person in charge returns. Usually it's not worth it for lower end phones since the unlock process can end up costing just as much as the phone tbh.
on some devices it takes 7 days for the oem unlock to show in developer options, have you tried the time and date hack to see if it shows
gav83collins said:
on some devices it takes 7 days for the oem unlock to show in developer options, have you tried the time and date hack to see if it shows
Click to expand...
Click to collapse
This does not work on U.S. variants
SamPWNd is dead. Samsung patched it with firmware updates in 2021 (it is in the warnings not to install unpatched firware updates). The website is down. Unless they can find a new exploit in the new firmware, it is not possible.
Samsung has blocked BL unlock for a while. They seem to have shifted their target audience to a different group in recent years. If you really want BL unlock you should pick Pixel.
b1283822 said:
SamPWNd is dead. Samsung patched it with firmware updates in 2021 (it is in the warnings not to install unpatched firware updates). The website is down. Unless they can find a new exploit in the new firmware, it is not possible.
Samsung has blocked BL unlock for a while. They seem to have shifted their target audience to a different group in recent years. If you really want BL unlock you should pick Pixel.
Click to expand...
Click to collapse
it doesnt make sense from a business perspective, a regular audience doesnt even know about unlocking a bootloader, so they will be buying the phone regardless if samsungs advertising impress more than the competition, but for us lets say "power users" we know our warranty is void when we oem unlock, and buy making it easier to do it (oem unlock), they are more likely to shift more handsets to our side of the market, not only that but there is more chance of us breaking our devices which in turn gives them more income when we seek samsung official repairs or splash out on a new replacement, i really dont see the logic behind not allowing oem unlock unless its to test the abilities of the likes of chainfire in regards to exposing vulnerabilities
I bought the phone on sale just a few days before this thread was made (hoping to use it as a fun side-project / second phone to get back into modding- haven't been able to since my Note 5 since the Note 8 was locked). I had assumed getting a non-carrier one would be open but I haven't been able to get OEM Unlock to appear either : /. I even went with the A53 instead of A52 because I thought there was a better chance of having unlock on Exynos than Snapdragon. It's not too late to return but I'm still holding out hope someone can come up with something. I like Samsung hardware (for the most part) but without root... meh.
Willing to try ODINing tars and stuff if anyone has any ideas.
sidestream84 said:
I bought the phone on sale just a few days before this thread was made (hoping to use it as a fun side-project / second phone to get back into modding- haven't been able to since my Note 5 since the Note 8 was locked). I had assumed getting a non-carrier one would be open but I haven't been able to get OEM Unlock to appear either : /. I even went with the A53 instead of A52 because I thought there was a better chance of having unlock on Exynos than Snapdragon. It's not too late to return but I'm still holding out hope someone can come up with something. I like Samsung hardware (for the most part) but without root... meh.
Willing to try ODINing tars and stuff if anyone has any ideas.
Click to expand...
Click to collapse
Exploits could take years to even begin to surface. S8 and S9 come to mind, but their root is so limited with locked bootloaders that it's almost not worth the hassle. I would return it to be honest or try and get an international variant imported. I've traveled to the U.S. with a Mexico variant phone and I got signal just fine, but I don't know how the internet speed compares if you use a U.S. SIM.
sidestream84 said:
I bought the phone on sale just a few days before this thread was made (hoping to use it as a fun side-project / second phone to get back into modding- haven't been able to since my Note 5 since the Note 8 was locked). I had assumed getting a non-carrier one would be open but I haven't been able to get OEM Unlock to appear either : /. I even went with the A53 instead of A52 because I thought there was a better chance of having unlock on Exynos than Snapdragon. It's not too late to return but I'm still holding out hope someone can come up with something. I like Samsung hardware (for the most part) but without root... meh.
Willing to try ODINing tars and stuff if anyone has any ideas.
Click to expand...
Click to collapse
I switched over from Pixel line just for a Samsung specific feature and a quick google had me certain I would be able to unlock the bootloader and root it. It sucks that its not the case, but I blame awful tech journalism. So many articles that claim their method will work for ALL devices in a family, or even ALL ANDROID devices period.
ShaDisNX255 said:
Exploits could take years to even begin to surface. S8 and S9 come to mind, but their root is so limited with locked bootloaders that it's almost not worth the hassle. I would return it to be honest or try and get an international variant imported. I've traveled to the U.S. with a Mexico variant phone and I got signal just fine, but I don't know how the internet speed compares if you use a U.S. SIM.
Click to expand...
Click to collapse
Getting an international version isn't worth doing IMO because the 5G bands don't overlap the same way 4G does. I looked in to getting an international model but decided against it as it doesn't support one of the three 5G frequencies used in my town. I figure there's 0 chance of new frequencies being added to the hardware, but always a chance of finding a security flaw to unlock the bootloader.
there are still U.S. Bootloader unlock services, but as of right now the A53 is not supported.
and only certain versions of bootloaders are supported.
Not SamPWND
How has nobody found a solution to this? Surely it's a software thing. You'd have thought some badass member somewhere with enough of a chip on their shoulder against Verizon would have figured a way around this.
Too bad there isn't a bounty for it.
jdkzombie said:
How has nobody found a solution to this? Surely it's a software thing. You'd have thought some badass member somewhere with enough of a chip on their shoulder against Verizon would have figured a way around this.
Too bad there isn't a bounty for it.
Click to expand...
Click to collapse
I doubt it is a simple or easy as it being simply a "software thing", and I completely believe it could/would never be done...but @wr3cckl3ss1 is on the case!
you can see a bit of how he's progressing HERE and HERE and HERE
It's unfortunate; this was actually the reason I switched from Verizon to T-Mobile lol. It appears the Verizon variant of the Pixel 6 remained locked all this time so I wouldn't bet on much different with the Pixel 7 :/ Hopefully somebody finds something for those with the VZW variant.
simplepinoi177 said:
I doubt it is a simple or easy as it being simply a "software thing", and I completely believe it could/would never be done...but @wr3cckl3ss1 is on the case!
you can see a bit of how he's progressing HERE and HERE and HERE
Click to expand...
Click to collapse
Nice!
Surely it couldn't be a hardware lock!?
Does anyone know how to read and interpret a Magisk log? And can show or tell me what's missing
jdkzombie said:
Nice!
Surely it couldn't be a hardware lock!?
Click to expand...
Click to collapse
The issue here is 2 java applets.....nothing hardware.
Too bad we didn't have a Verizon inside agent. Tell us wtf they do to lock it. Because isn't that against Googles Tos? It's sold as an unlock able device.
jdkzombie said:
Too bad we didn't have a Verizon inside agent. Tell us wtf they do to lock it. Because isn't that against Googles Tos? It's sold as an unlock able device.
Click to expand...
Click to collapse
It's Verizon that demands it. But it's Google's own code that puts the lock in place...so they're both at fault.
wr3cckl3ss1 said:
It's Verizon that demands it. But it's Google's own code that puts the lock in place...so they're both at fault.
Click to expand...
Click to collapse
Weird. Strange that this would still be a thing. Not like the device was cheap to purchase.
My question is why is Verizon so "gung-ho" about it? More than any other carrier (other carriers eventually allow to unlock the bootloader)? I could understand when they used to repair their own devices (so they didn't want the liability and the headaches of when customers messed with the devices); but that's the not the case anymore. Outside of their greedy archaic grasp on tethering and to load unremovable bloatware, I don't know what they have to fear of unlocked bootloaders & root access.
Who knows.
I'm willing to throw money towards a bounty that removes Verizons strangle hold on devices. I don't mind their service, and the signal is good where I live, but I like customization. And I'd love to try some new kernals to change up the CPU scheduler and power plans to stop the phone from bringing the 4 big cores online for casual use.
Just get the unlocked version and use with Verizon service. What's the upside with having the Verizon variant?
Because it's not that simple. You can't swappa sell a phone you're making any payments towards. And the phone is too new for trade in with another carrier of any type.
VZW variants have been locked since the OG Pixel days aside from that small window before taking an OTA you could unlock if it was on a certain version. Sadly I don't see this changing anytime soon and if you want to unlock BL and root get the unlocked version from the Google Store. There's really little incentive buying Pixels from Verizon now. With Pixel Pass and Google Store financing those are good options if you can't drop all the money up front.
Just buy the unlocked model. Some retailers have awesome trade in deals coming from the 6 series or iPhones. It works just as well on Verizon and avoids the 36 month committment.
I hate how Verizon shuts down the option for unlocking the bootloader and rooting, but it is easier to purchase a device from them because your payments will coincide with your regular monthly cell bill, you already pass the credit check when you open an account with them (no need to apply for one with Google Synchrony Financing), and I just went through with this with my wife's phone but unless you qualify enough to cover the Pixel (my wife qualified for the Pixel 7, not the P7P at the storage capacity we wanted), you're stuck paying all (up to $1400 [P7P 512GB w/ 2 year protection & tax]) up front -- where there's virtually no risk of this if you purchase through Verizon (they want to lock you in to years-long contract and you already passed the credit check)! So there's (some of) the benefits....
*but it's still more worth it beyond any of these "benefits" to get it from Google Store unlocked....
Lol. Here's a simple solution. Buy the unlocked version. Who changes carriers because of a bl lock? WTF?
At this point I think we all know that Verizon isn't going to unlock the Bootloader. if you want an unlocked bootloader, it is easier, and more guaranteed to just buy the unlocked version from Google vs trying to find vulnerabilities in the bootloader and having to worry about it being patched each month.
Not sure if this is still in effect, but many years ago, if you purchased an unlocked phone instead of the Verizon branded one, WiFi calling wouldn't work. I'm not sure if there was something missing from the phone that Verizon needed to make it happen, or if Verizon was just screwing over those who purchased unlocked versions.
andygold said:
Not sure if this is still in effect, but many years ago, if you purchased an unlocked phone instead of the Verizon branded one, WiFi calling wouldn't work. I'm not sure if there was something missing from the phone that Verizon needed to make it happen, or if Verizon was just screwing over those who purchased unlocked versions.
Click to expand...
Click to collapse
it's working perfectly fine with my device....it also worked with my Pixel 5 (also unlocked variant from Google Store)....