Related
My phone is boogered up so bad that it just boots into fastboot mode. I have been unsuccessful in flashing the stock ROMs. It's the Canadian version with unlocked GSM. I'm hoping that unlocking the bootloader will help me to flash it and get it working again. I have tried using the Motorola site but it says my phone cannot be unlocked.
Anyone?? Please? I have search these forums for days and cannot find the answer to my question. If it's there I'm finding it. Any help would be appreciated.
I know Rogers allows unlocking the bootloader. As I recall, you're a Fido user (which Rogers owns) right? Are you still looking for the Fido 4.1.2 SBF? I think I can track it down for you. I'm surprised Moto won't unlock the bootloader via the website. Have you tried Motoclypse (I think it's called) to try and unlock it? I guess you'll need a running ROM first.
Lemme know what you need exactly and I'll see if I can hunt it down for you.
CWGSM3VO said:
I know Rogers allows unlocking the bootloader. As I recall, you're a Fido user (which Rogers owns) right? Are you still looking for the Fido 4.1.2 SBF? I think I can track it down for you. I'm surprised Moto won't unlock the bootloader via the website. Have you tried Motoclypse (I think it's called) to try and unlock it? I guess you'll need a running ROM first.
Lemme know what you need exactly and I'll see if I can hunt it down for you.
Click to expand...
Click to collapse
CWG... Thank you! I've scoured a few sites that are still up and running (best one so far is motofirmware.com.) I found and downloaded this.. 9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml but cannot flash gpt and boot partitions. I have tried editing the xml file as suggested in other posts to prevail. Is there a way I can positively identify which region my phone is? I purchased it brand new from a Canadian seller on eBay. The listing said that it was a Rogers phone but when I unlocked the GSM the key came back as being from Fido. There was no carrier specific apps on it. I'm at the most current level of firmware on it by the carrier as of a few weeks ago.
I got the bootloader unlocked!!!! I was originally entering the code into Motorola's website through Chrome and something told me to try it through Firefox.... success!!
truebeliever71 said:
I got the bootloader unlocked!!!! I was originally entering the code into Motorola's website through Chrome and something told me to try it through Firefox.... success!!
Click to expand...
Click to collapse
Awesome, so you're good to go or still need a SBF for Fido?
CWGSM3VO said:
Awesome, so you're good to go or still need a SBF for Fido?
Click to expand...
Click to collapse
Nope. I'm good. Installed the one mention before and updated to KitKat.
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
newbienic said:
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
Click to expand...
Click to collapse
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Awesome! Thanks for the info... Really glad to know I can convert if need be. Thanks again!
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
newbienic said:
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
Click to expand...
Click to collapse
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
ITGuy11 said:
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
Click to expand...
Click to collapse
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
danaff37 said:
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
danaff37 said:
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Hypathetically, if I didn't want root or anything custom at all, do you think that relocking the bootloader could cause an issue while using the Stock Google image on a Verizon Pixel? I wish I had more knowledge on this, but I'm pretty in the dark on this stuff as of late... Thanks for your help!
Should be fine if all stock I think, just know that you may not be able to unlock later.
Sent from my Pixel using Tapatalk
newbienic said:
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
Click to expand...
Click to collapse
Contrary to what people are saying. You CAN relock your bootloader and then unlock it again later. However, keep in mind that at some point there will likely be an update that blocks the use of dePixel8 and you will no longer be able to unlock the bootloader unless someone writes another exploit.
I would like to find a way to permanently unlock VZW Pixels but until I get one from the Google Store to compare with my Verizon one I don't think I will make much progress.
Relocking your bootloader is as simple as running the "fastboot oem lock" command from the terminal window.
Lastly. If you want to relock the bootloader, make sure your phone is 100% stock image or you risk bricking the phone
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
b316kane said:
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
Click to expand...
Click to collapse
This is exactly what I did, and I am curious as well... We'll see next month I guess, but I'm guessing it will take the OTA just fine. My wife has a Pixel from the Google store, and mine is from Verizon. I've compared everything (including booloaders) since flashing the Google store Pixel image, and every informational detail is identical. Not sure if there is some other place hidden to me that might indicate a difference, but I'm thinking that Verizon's Pixel is only different in its official software image... And, that may be it. Please don't take my word for it, I'm no developer, and know very little about any of this, but in my comparisons, they are identical now since flashing Googles official (Non Verizon, Non European) image.
Sidenote, I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking. I think Verizon used Googles "Allow OEM Unlocking" software toggle in developer options as the only method to actually keep people from unlocking the bootloader (again speculative), and now that I'm on Googles image, that software "block" should no longer be present, so I should in theory, be free to lock/unlock the same as Pixels purchased from the Google store... Again, I've got no proof, or actual skill to back this up, but it's a theory I have, and if I end up locking my BL again, I'll post what I find...
newbienic said:
I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking.
Click to expand...
Click to collapse
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
alluringreality said:
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Click to expand...
Click to collapse
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
newbienic said:
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
Click to expand...
Click to collapse
I forget where, but I saw written or implied that the "checking for updates" screen about third of way through initial setup of first boot uses WiFi AND sim carrier data to install Verizon custom restrictions and settings that among other effects make depixel8 required.
Even on "non Verizon phones" (which you are saying use the same build images byte to byte?)... You have to either use a SIM card or wifi and google account to allow the developer options to enable OEM unlock.
My theory: In other words, if you don't allow via SIM and a network wifi or data connect, for Verizon to mark your phone, or another carrier, then the phone can not be unlocked. So carrier models may indeed be differentiated from current factory images AFTER boot and setup.
There is a post in Q&A of someone trying to unlock bootloader without loading into the device, not having luck. This is why oem unlock toggle is so important and why people are bricking from locked bootloaders that won't unlock (so no wipe and factory images cannot be flashed.)
Another thing to consider: SIM network lock will not be flashed over.
Sent from my sailfish using XDA Labs
I'm in a Verizon pixel and installed "v" version instead of "u" everything is working. What's different about the international version?
Just a fix for European carriers. I'm using the same on Verizon as well with no issues. You're good.
Nick_Gl said:
I'm in a Verizon pixel and installed "v" version instead of "u" everything is working. What's different about the international version?
Click to expand...
Click to collapse
Nothing it will work just fine. From what I understand just a slight difference for Europe. It will be fine.
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
jesssiii said:
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
Click to expand...
Click to collapse
You probably wouldn't get any updates. The trigger for that version probably wouldn't get to you. But I am not certain on that. Might be able to pull it via wifi with no SIM in it.
Do NOT relock your bootloader unless it is just before you are going to put it in a box to send back for warranty.
jesssiii said:
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
Click to expand...
Click to collapse
Why would you think you'd get the European version if you are in the US? Did I miss something in your question? You'd get the U version if you're on Verizon and you can lock and relock the bootloader at your discretion since you have the Google Pixel. I mean if you want to keep wiping your data each time, that is.
bobby janow said:
Why would you think you'd get the European version if you are in the US? Did I miss something in your question? You'd get the U version if you're on Verizon and you can lock and relock the bootloader at your discretion since you have the Google Pixel. I mean if you want to keep wiping your data each time, that is.
Click to expand...
Click to collapse
He made it sound like his pixel is from Verizon. In that case he can't lock and unlock the bootloader whenever he wants.
To the OP. What are you trying to do? It doesn't matter if you are on V. If it makes you feel better just flash U then. As long as you don't have twrp or root you will still get OTAs. Why would you want to lock your bootloader? You can have an unlocked bootloader and still take normal OTAs just fine . it its a Verizon sold pixel you won't be able to unlock once you lock.
fritzgerald said:
Just a fix for European carriers. I'm using the same on Verizon as well with no issues. You're good.
Click to expand...
Click to collapse
Thanks wasn't sure. I'll just remember to side load the correct one in February.
aholeinthewor1d said:
He made it sound like his pixel is from Verizon. <snip>
Click to expand...
Click to collapse
It was certainly a little bit confusing, however, the last part of his post it said.. (device from Google) so I figured it was a GPixel activated on Verizon.
Here's what I got. ATT LG G3 running stock Marshmallow D85030p with what I presume is the newest security patch (June 2016)
At this point it's not on a carrier but it's locked by ATT. They kept my number as well.. A number that was mine from previous carriers.
Will I be able to root, install TWRP, and unlock this device to use on a prepaid carrier? Keep in mind this same phone has been flashed, rooted and ran recovery mods and ROMs before. Still in perfect working condition after receiving it's last stock OTA.
jlgarr86 said:
Here's what I got. ATT LG G3 running stock Marshmallow D85030p with what I presume is the newest security patch (June 2016)
At this point it's not on a carrier but it's locked by ATT. They kept my number as well.. A number that was mine from previous carriers.
Will I be able to root, install TWRP, and unlock this device to use on a prepaid carrier? Keep in mind this same phone has been flashed, rooted and ran recovery mods and ROMs before. Still in perfect working condition after receiving it's last stock OTA.
Click to expand...
Click to collapse
First of all what do you mean they kept your number? Did you cancel? Unpaid bill? That would be a deciding factor on how to go about things.
But no root cannot unlock your device
1. If you left AT&T in good standing AT&T will unlock the device for free. Even if you don't have any account.
2. If not then you can get it unlocked for a few dollars from some eBay sellers.
3. What prepaid carrier? If Any provider that runs on AT&Ts network you don't have to get it unlocked, it will work fine with Go Phone, Cricket , H2O and many others that run on AT&Ts network.
But a note if it's no longer on AT&T due to unpaid bill, or on bad terms remember the device may no longer work on any GSM carrier within the USA due to AT&T will blacklist it.
Sent from my iPhone using Tapatalk
hyelton said:
First of all what do you mean they kept your number? Did you cancel? Unpaid bill? That would be a deciding factor on how to go about things.
But no root cannot unlock your device
1. If you left AT&T in good standing AT&T will unlock the device for free. Even if you don't have any account.
2. If not then you can get it unlocked for a few dollars from some eBay sellers.
3. What prepaid carrier? If Any provider that runs on AT&Ts network you don't have to get it unlocked, it will work fine with Go Phone, Cricket , H2O and many others that run on AT&Ts network.
But a note if it's no longer on AT&T due to unpaid bill, or on bad terms remember the device may no longer work on any GSM carrier within the USA due to AT&T will blacklist it.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I understand root alone won't unlock it. With all that being said can I still root and flash a recovery method that are permanent? Does MM still not have a reliable root or recovery method?
jlgarr86 said:
I understand root alone won't unlock it. With all that being said can I still root and flash a recovery method that are permanent? Does MM still not have a reliable root or recovery method?
Click to expand...
Click to collapse
You would need to downgrade to KitKat to do that. But remember once you downgrade you'll no longer be able to go back to any official firmware Past KitKat without an AT&T SIM card of some sort to ota update it.
Also remember if you get an unlock code you need to be running stock D850 firmware or else you won't be able to enter the unlock code.
Sent from my iPhone using Tapatalk
hyelton said:
You would need to downgrade to KitKat to do that. But remember once you downgrade you'll no longer be able to go back to any official firmware Past KitKat without an AT&T SIM card of some sort to ota update it.
Also remember if you get an unlock code you need to be running stock D850 firmware or else you won't be able to enter the unlock code.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Are there any unofficial MM or Lollipop ROMs that are worth looking into? I couldn't care less if it's official honestly. And that last bit you said, you mean if I wanted a phone unlocked I'd have to basically wipe my phone?
jlgarr86 said:
Are there any unofficial MM or Lollipop ROMs that are worth looking into? I couldn't care less if it's official honestly. And that last bit you said, you mean if I wanted a phone unlocked I'd have to basically wipe my phone?
Click to expand...
Click to collapse
If you unlock before you leave behind stock then no you don't have to wipe. Once you install any custom ROM, your only option to unlock at that point is to revert back to stock, which means wiping.
aybarrap1 said:
If you unlock before you leave behind stock then no you don't have to wipe. Once you install any custom ROM, your only option to unlock at that point is to revert back to stock, which means wiping.
Click to expand...
Click to collapse
Can I unlock it myself?
jlgarr86 said:
Can I unlock it myself?
Click to expand...
Click to collapse
Yes you can, if you are on stock. You will need to get the unlock code from AT&T, be on stock firmware, and have an active SIM card from another carrier (I.e. T-Mobile or of it's MVNOs like MetroPCS). Once you have the unlock code, put in the SIM card, turn on the phone, and you will get the prompts for the code you got. Then you're done.
This is an unlocked T-Mobile G5, but why have a special ROM for unlocked phone? I wonder if I flash other ROMs, I could lose the unlock. Anyone have any problem rooting and install twrp?
Conclusion after a month long discussion:
G5 with H83020i_un ROM is NOT factory unlock. Upgrading or downgrading will result in SIM lock to T-Mobile, period.
Once locked, it can only be unlocked by T-Mobile customers via T-Mobile unlocked app. Some has to go thru T-Mobile customer service and request SIM unlock by adding IMEI to their database.
I bought 6 (New to New other) unlocked H830 and 2 has the hacked ROM H83020i_un and 4 were completely locked to T-Mobile. Yes, those stupid sellers on ebay just keep sending lock phones as unlocked phone! Good luck getting a unlocked one.
No, you cannot install TWRP or root this version.
I ended up returning mine.
You shouldn't lose the unlock by flashing another ROM.
A ROM isn't just about 'locked or unlocked'. The ROM is the operating system. While it will still be Android no matter what you do, different ROMs are modified differently to provide additional features, or more control over the settings or just a slightly different user interface.
This has NOTHING to do with the phone being unlocked for use on any GSM network.
For example some people want to be able to control the CPU processor speed on the phone more. Some ROM's give you that control built into the settings and use customer kernels that allow the CPU to run faster than it does running stock. Other people just like a more simple UI that you get on base Android ROM's (rather than some of the overlays LG puts on)
Skipjacks said:
You shouldn't lose the unlock by flashing another ROM.
A ROM isn't just about 'locked or unlocked'. The ROM is the operating system. While it will still be Android no matter what you do, different ROMs are modified differently to provide additional features, or more control over the settings or just a slightly different user interface.
This has NOTHING to do with the phone being unlocked for use on any GSM network.
For example some people want to be able to control the CPU processor speed on the phone more. Some ROM's give you that control built into the settings and use customer kernels that allow the CPU to run faster than it does running stock. Other people just like a more simple UI that you get on base Android ROM's (rather than some of the overlays LG puts on)
Click to expand...
Click to collapse
I can't confirm this personally, but @autoprime mentioned on IRC that everyone who tried flashing other KDZs over this specific firmware lost the SIM unlock.
BehindTheMath said:
I can't confirm this personally, but @autoprime mentioned on IRC that everyone who tried flashing other KDZs over this specific firmware lost the SIM unlock.
Click to expand...
Click to collapse
So we can't flash this device?
dkyu said:
So we can't flash this device?
Click to expand...
Click to collapse
Well, technically you can, but as of now it sounds like you'd lose the SIM unlock.
BehindTheMath said:
Well, technically you can, but as of now it sounds like you'd lose the SIM unlock.
Click to expand...
Click to collapse
I don't know when people will understand that it has nothing to do with sim unlock. I have T-Mobile unlocked sim lg g5 and flashed roms, custom and stock both several times and never had any problem with sim lock stuffs. Just install twrp, root, flash custom rom, there will never hurt anything in your phone.
dksoni411 said:
I don't know when people will understand that it has nothing to do with sim unlock. I have T-Mobile unlocked sim lg g5 and flashed roms, custom and stock both several times and never had any problem with sim lock stuffs. Just install twrp, root, flash custom rom, there will never hurt anything in your phone.
Click to expand...
Click to collapse
It seems that this is not a regular unlock. When I open the T-Mobile app, it says the phone is still locked, but it works anyway.
dksoni411 said:
I don't know when people will understand that it has nothing to do with sim unlock. I have T-Mobile unlocked sim lg g5 and flashed roms, custom and stock both several times and never had any problem with sim lock stuffs. Just install twrp, root, flash custom rom, there will never hurt anything in your phone.
Click to expand...
Click to collapse
I just tried downgrading to 20A and lost the SIM unlock.
BehindTheMath said:
I just tried downgrading to 20A and lost the SIM unlock.
Click to expand...
Click to collapse
Did you confirm that by trying the phone with a non T Mobile SIM on a different network? Or did you just let the T Mobile unlocker app tell you it's still locked?
The app isn't the most reliable thing in the world. It's known to say it's not unlocked when it is or that it can't be unlocked when it already is. Etc etc...
Unlocking it manually (through codes, ADB, root, etc....) messes with the unlocker app. But the unlock itself should still be valid.
Skipjacks said:
Did you confirm that by trying the phone with a non T Mobile SIM on a different network? Or did you just let the T Mobile unlocker app tell you it's still locked?
The app isn't the most reliable thing in the world. It's known to say it's not unlocked when it is or that it can't be unlocked when it already is. Etc etc...
Unlocking it manually (through codes, ADB, root, etc....) messes with the unlocker app. But the unlock itself should still be valid.
Click to expand...
Click to collapse
I took the active H2o (At&t MVNO) SIM from my current device and tried it in this one. I could not make phone calls or access data, both in stock 20A and Resurrection Remix.
BehindTheMath said:
I took the active H2o (At&t MVNO) SIM from my current device and tried it in this one. I could not make phone calls or access data, both in stock 20A and Resurrection Remix.
Click to expand...
Click to collapse
that's sucks.
I wonder if you can actually get an unlock code to unlock the phone now.
dkyu said:
that's sucks.
I wonder if you can actually get an unlock code to unlock the phone now.
Click to expand...
Click to collapse
If I'm not mistaken, you can't unlock this phone with an unlock code.
dksoni411 said:
I don't know when people will understand that it has nothing to do with sim unlock. I have T-Mobile unlocked sim lg g5 and flashed roms, custom and stock both several times and never had any problem with sim lock stuffs. Just install twrp, root, flash custom rom, there will never hurt anything in your phone.
Click to expand...
Click to collapse
Maybe it is something to the specific phones people are getting from the ebay seller. They are being sold as new yet are not factory sealed and missing the Tmo sim card. People are claiming Android pay doesn't work and the phone isn't rooted. A new out of the box phone shouldn't have that issue. So something isn't necessarily kosher.
Guys, I have the same version (H83020i_un) and it has April security update and T-Mobile has different version #s on their website. I have checked for update, but nothing came up. So I can't get T-Mobile updates?
The software version H83020i_un is apparently not an official ROM released by T Mobile or LG.
There is a lot of speculation on Slickdeals (a website for coupons and stuff where this eBay deal has been discussed quite a bit) that the unlock was done by flashing a modified ROM. If so that would explain why flashing a new ROM loses the unlock.
Additionally people are saying that Android Pay doesn't work on this phone with that software update, presumably because it's not official firmware. I've never used Android Pay so I have no idea if it works or not.
All in all if you have the H83020i_un software and bought the phone 'new' I think you got conned. It's not new and that seems to be unofficial software.
I spent a lot of time, with help from @autoprime, trying to figure out where the unlock is stored. I was able to dump the partitions from 20i_un using the method here. After I downgraded to 20A and flashed TWRP, I flashed back all the 20i_un partitions (besides recovery, cache, and userdata), and it still wasn't unlocked. So I'm baffled as to how the unlock works.
Skipjacks said:
The software version H83020i_un is apparently not an official ROM released by T Mobile or LG.
There is a lot of speculation on Slickdeals (a website for coupons and stuff where this eBay deal has been discussed quite a bit) that the unlock was done by flashing a modified ROM. If so that would explain why flashing a new ROM loses the unlock.
Additionally people are saying that Android Pay doesn't work on this phone with that software update, presumably because it's not official firmware. I've never used Android Pay so I have no idea if it works or not.
All in all if you have the H83020i_un software and bought the phone 'new' I think you got conned. It's not new and that seems to be unofficial software.
Click to expand...
Click to collapse
I see. It will be used as a second device, so it is fine. I flashed the phone with stock T-Mobile H83020a, then got few OTA updates. Now my phone has H83020i, but T-Mobile's page(below) shows an "f" version as the latest. So is the H83020i, the latest update or not? Also would be good if anyone with real T-Mobile unit could chime in.
https://support.t-mobile.com/docs/DOC-30673
BehindTheMath said:
I spent a lot of time, with help from @autoprime, trying to figure out where the unlock is stored. I was able to dump the partitions from 20i_un using the method here. After I downgraded to 20A and flashed TWRP, I flashed back all the 20i_un partitions (besides recovery, cache, and userdata), and it still wasn't unlocked. So I'm baffled as to how the unlock works.
Click to expand...
Click to collapse
And there is no way to root the phone without downgrading to 20A right?
Charkatak said:
I see. It will be used as a second device, so it is fine. I flashed the phone with stock T-Mobile H83020a, then got few OTA updates. Now my phone has H83020i, but T-Mobile's page(below) shows an "f" version as the latest. So is the H83020i, the latest update or not? Also would be good if anyone with real T-Mobile unit could chime in.
https://support.t-mobile.com/docs/DOC-30673
Click to expand...
Click to collapse
Looks like 20i is the latest.
https://forum.xda-developers.com/tm...ock-h830-20i-rom-flashable-zips-imgs-t3609735
dkyu said:
And there is no way to root the phone without downgrading to 20A right?
Click to expand...
Click to collapse
Correct.
BehindTheMath said:
Looks like 20i is the latest.
https://forum.xda-developers.com/tm...ock-h830-20i-rom-flashable-zips-imgs-t3609735
Correct.
Click to expand...
Click to collapse
So if 20i is the latest, then it is possible that T-Mobile's variant of the phone could have a different model # than H830...