I'm currently with Consumer Cellular, brought my moto g from them. They have my phone locked currently and I can't switch to another carrier for another 3 months. My question is, does anyone know if it matters if I flash a custom rom, which will replace the factory rom, if it will prevent me from unlocking the phone when the time comes to enter the unlock code they will provide.
Asking because I don't know if the OS they provide when you buy the phone has any special features that control the operating of the sim card. When I try to boot with a different sim a window comes up asking for a code.
Thanks in advance.
Anyone?
I think you should wait. When you get the carrier unlock code, usually you have to dial a ussd code (starting with *#*# and ending with #*#*, or similar, you know better), then a code prompt pops up where you put that code. In other cases, password prompt comes up when you insert other carrier's sim. While I am sure that custom ROMs are designed with carrier locked users in mind too, but some glitches can happen, as explained here-https://www.mobileunlocked.com/news/does-having-a-custom-rom-affect-phone-unlocking/.
You can indeed unlock now, but if the custom rom doesn't ask you for an unlock code and the new carrier sim doesn't work (rare case) then you may have to flash to stock again. An US user can explain you in good details about this, I just pointed out what could happen as I we usually not have carrier locked phones here in Asia.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
I think you should wait. When you get the carrier unlock code, usually you have to dial a ussd code (starting with *#*# and ending with #*#*, or similar, you know better), then a code prompt pops up where you put that code. In other cases, password prompt comes up when you insert other carrier's sim. While I am sure that custom ROMs are designed with carrier locked users in mind too, but some glitches can happen, as explained here-https://www.mobileunlocked.com/news/does-having-a-custom-rom-affect-phone-unlocking/.
You can indeed unlock now, but if the custom rom doesn't ask you for an unlock code and the new carrier sim doesn't work (rare case) then you may have to flash to stock again. An US user can explain you in good details about this, I just pointed out what could happen as I we usually not have carrier locked phones here in Asia.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Good info, thanks. I did make a backup of my stock rom in twrp recovery, even before flashing twrp. Would that still be considered original stock software that I could reinstall if I did flash custom rom and it caused problems.
Thanks!
melp57 said:
Good info, thanks. I did make a backup of my stock rom in twrp recovery, even before flashing twrp. Would that still be considered original stock software that I could reinstall if I did flash custom rom and it caused problems.
Thanks!
Click to expand...
Click to collapse
Yes. Nandroid backups are like system image backup in windows 7, they are virtual images of the backed up partition; so that wouldn't be a problem to restore these to get stock back.
Broadcasted from Zeta Reticuli
When you insert a Sim from a different carrier, it should immediately pop-up a window requiring the unlock code, stock or not, to unlock the Sim... If it doesn't, you should remove the Sim, jump into recovery and backup, restore stock, boot and unlock, then restore the nandroid. Should be good to go. Haven't seen a locked GSM phone in the US the last few years that requires dialing USSD codes to unlock.
Sent from my XT1575 using Tapatalk
acejavelin said:
When you insert a Sim from a different carrier, it should immediately pop-up a window requiring the unlock code, stock or not, to unlock the Sim... If it doesn't, you should remove the Sim, jump into recovery and backup, restore stock, boot and unlock, then restore the nandroid. Should be good to go. Haven't seen a locked GSM phone in the US the last few years that requires dialing USSD codes to unlock.
Click to expand...
Click to collapse
It just ask me for unlock code, via popup.
Yeah, we switched from Verizon to Consumer Cellular, which uses tmoble and AT&T. I had to buy the Moto from them because my Droid maxx was Verizon and CDMA. Anyway, we decided to switch to tmoble because we travel to Canada often and can use phone /data there. Got my sim from tmoble, put it in rebooted phone, then message pops up for code. Consumers don't tell you you have to be with them for 6 months. Phone was paid for upfront. If I had done my homework I would have just got a Google phone.
I don't believe there will be anything thing to dial, it just ask for network unlock code.
After I unlocked my bootloader, I booted into twrp and did a backup. Will that suffice as a stock backup? Also should the fact that I'm unlocked cause a problem?
Sorry everyone for the long post, but wanted to make people aware of the ends and outs of what can happen with different Carriers. I was under the assumption that all or most phones were unlocked.
acejavelin said:
When you insert a Sim from a different carrier, it should immediately pop-up a window requiring the unlock code, stock or not, to unlock the Sim... If it doesn't, you should remove the Sim, jump into recovery and backup, restore stock, boot and unlock, then restore the nandroid. Should be good to go. Haven't seen a locked GSM phone in the US the last few years that requires dialing USSD codes to unlock.
Click to expand...
Click to collapse
Would be interested to know what part of OS handles this process. Or maybe it's commands on a chip. My thinking was its carrier related, so must be handled by the OS they installed on the phone.
melp57 said:
Would be interested to know what part of OS handles this process. Or maybe it's commands on a chip. My thinking was its carrier related, so must be handled by the OS they installed on the phone.
Click to expand...
Click to collapse
It is a core OS function, not specifically carrier installed... There is just a security flag somewhere that's hidden and can be toggled with the proper code.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
It is a core OS function, not specifically carrier installed... There is just a security flag somewhere that's hidden and can be toggled with the proper code.
Click to expand...
Click to collapse
So any custom rom which should have this part of the core.
melp57 said:
So any custom rom which should have this part of the core.
Click to expand...
Click to collapse
Should is the key word here... ?
Sent from my XT1575 using Tapatalk
acejavelin said:
Should is the key word here... ?
Click to expand...
Click to collapse
Well, I Have a backup for the rom on my device currently, and before anything has been done, except unlock bootloader.
Enough on this subject, going to go ahead and flash RR, the one that was taken over.
Again, thanks for all your insight!
Related
Hi
I bought D2G from ebay it was listed with bad esn.It's not asking unlock code or anything, reads the sim card, changes to global mode, connects to a network(jumps from one to another all the time) but no service when I try to dial a number says network not available. So what is wrong with my phone? is it unlock?something is wrong wit the radio? or what?
If it is not asking for network subsidy code, then it must be unlocked if it works with your sim. Make sure it is set to GSM/UMTS mode, not Global - if your sim is active you should get reception. At least on 2G (GSM). If you are not getting reception, something might be wrong with the phone.
It might also be running a custom ROM (unlock requests only work on Blurry ROMs afaik); another possibility is former owner going to the “hidden” menu and choosing “USA Band”.
In the latter case, you need to SBF.
thanks Gasai Yuno custom rom was the problem now it's on stock rom and is asking for unlock code. I'll try to unlock it thanks again
Gasai Yuno said:
It might also be running a custom ROM (unlock requests only work on Blurry ROMs afaik); another possibility is former owner going to the “hidden” menu and choosing “USA Band”.
In the latter case, you need to SBF.
Click to expand...
Click to collapse
Good catch! I wouldn't thought somebody would sell their phone without bringing it factory default first..
Good luck to OP with the unlock codes - hopefully your phone won't turn out to be from those Verizon played with..
leobg said:
Good catch! I wouldn't thought somebody would sell their phone without bringing it factory default first..
Good luck to OP with the unlock codes - hopefully your phone won't turn out to be from those Verizon played with..
Click to expand...
Click to collapse
I bought unlock code from ebay and it worked and it's working fine. Thanks again
Gasai Yuno said:
It might also be running a custom ROM (unlock requests only work on Blurry ROMs afaik); another possibility is former owner going to the “hidden” menu and choosing “USA Band”.
In the latter case, you need to SBF.
Click to expand...
Click to collapse
Ask much as I understand. it stop asking for unlock code because of Custom Rom. I have the same problem. What should I do to be able to enter unlock code with Custom Rom?
Rexkh said:
Ask much as I understand. it stop asking for unlock code because of Custom Rom. I have the same problem. What should I do to be able to enter unlock code with Custom Rom?
Click to expand...
Click to collapse
Flash the stock ROM.
I try to flash stock rom (kdz extension) but it doesn't work because my boot recovery is not stock recovery. What should I do to remove CWM recovery for my phone model LG Optimus G E973?
Rexkh said:
I try to flash stock rom (kdz extension) but it doesn't work because my boot recovery is not stock recovery. What should I do to remove CWM recovery for my phone model LG Optimus G E973?
Click to expand...
Click to collapse
Ask in correct forum, this for Motorola's droid 2 global phone, instructions will be different.
Sent from my Amazon Otter using Tapatalk
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...
Hi,
I have Oreo on Pixel XL, and was wondering if there's any way to unlock the bootloader with dePixel8 or otherwise so I can install TWRP/root?
Thanks!
No
I was given the phone from a family member. I'm assuming it was Verizon, but I use it on Sprint now. Under developer options, OEM unlocking is greyed out, and it says to go online or talk to carrier.
Surely there's a way to root this phone?
H0wdy said:
I was given the phone from a family member. I'm assuming it was Verizon, but I use it on Sprint now. Under developer options, OEM unlocking is greyed out, and it says to go online or talk to carrier.
Surely there's a way to root this phone?
Click to expand...
Click to collapse
If it's a Verizon phone (sounds like it is), no. There is currently no way to root. If it's a Google phone, it can be done. However, for the option in developer options to not be greyed out, you need to be connected to the internet one way or another. If you are connected and it's still greyed out, it's almost certain that it's a Verizon phone.
robocuff said:
If it's a Verizon phone (sounds like it is), no. There is currently no way to root. If it's a Google phone, it can be done. However, for the option in developer options to not be greyed out, you need to be connected to the internet one way or another. If you are connected and it's still greyed out, it's almost certain that it's a Verizon phone.
Click to expand...
Click to collapse
Robocuff,
Thank you. That seems to be my situation, but I was wondering why this isn't an option?
https://www.xda-developers.com/verizon-pixelpixel-xl-bootloader-unlock-has-been-released/
Does it no longer work? I understand it probably doesn't, but I didn't know if there was another way.
H0wdy said:
Robocuff,
Thank you. That seems to be my situation, but I was wondering why this isn't an option?
https://www.xda-developers.com/verizon-pixelpixel-xl-bootloader-unlock-has-been-released/
Does it no longer work? I understand it probably doesn't, but I didn't know if there was another way.
Click to expand...
Click to collapse
dePixel8 doesn't work anymore. It only worked for a couple months. Google patched the hole that dePixel8 exploited in the December security update. So, any Verizon phone that was updated in December or anytime after and wasn't all ready unlocked, became unlockable after that.
robocuff said:
dePixel8 doesn't work anymore. It only worked for a couple months. Google patched the hole that dePixel8 exploited in the December security update. So, any Verizon phone that was updated in December or anytime after and wasn't all ready unlocked, became unlockable after that.
Click to expand...
Click to collapse
Thanks. I guess I'll wait to see if something else occurs.
I wonder if overwriting the Verizon Pixel's bootloader with a non-Verizon bootloader from one of the factory images would work. The logic behind this is that all G-2PW2100s seemd to have identical hardwares, and factory images contain all the bootloader/radio partition images; so in theory, flashing a non-Verizon factory image should make the device non-Verizon.
(Please note that this is just a theory & I have not tested this. There's a chance that doing this will brick the device.)
AncientDeveloper said:
I wonder if overwriting the Verizon Pixel's bootloader with a non-Verizon bootloader from one of the factory images would work. The logic behind this is that all G-2PW2100s seemd to have identical hardwares, and factory images contain all the bootloader/radio partition images; so in theory, flashing a non-Verizon factory image should make the device non-Verizon.
(Please note that this is just a theory & I have not tested this. There's a chance that doing this will brick the device.)
Click to expand...
Click to collapse
I don't believe this will work. The accepted theory is that Verizon locks the bootloader by IMEI number, so if your phone has an IMEI that is on the list, it will be locked no matter what. However, I'm not sure if anyone has tried to change their IMEI to test this theory. I'm also not sure if you can change your IMEI without root. That would require an unlocked bootloader, so probably no way to test.
jmartin72 said:
I don't believe this will work. The accepted theory is that Verizon locks the bootloader by IMEI number, so if your phone has an IMEI that is on the list, it will be locked no matter what. However, I'm not sure if anyone has tried to change their IMEI to test this theory. I'm also not sure if you can change your IMEI without root. That would require an unlocked bootloader, so probably no way to test.
Click to expand...
Click to collapse
But the bootloader is still locked locally. So even the phone sends the IMEI to Verizon, and Verizon sends some command back to the phone to lock it, it shouldn't require changing the IMEI to unlock.
AncientDeveloper said:
But the bootloader is still locked locally. So even the phone sends the IMEI to Verizon, and Verizon sends some command back to the phone to lock it, it shouldn't require changing the IMEI to unlock.
Click to expand...
Click to collapse
I wish someone could figure out how to get it done.
Hi - My Verizon Pixel XL is on Oreo OPR3 and OEM unlocking is *not* greyed out but bootloader status is LOCKED. Is it possible with my setup?
Edit: OEM unlocking is *not* greyed out even on Wifi
nyisles said:
Hi - My Verizon Pixel XL is on Oreo OPR3 and OEM unlocking is *not* greyed out but bootloader status is LOCKED. Is it possible with my setup?
Click to expand...
Click to collapse
Yep, Google has messed up on quite a few phones. Hit that slider now. That won't unlock it, you still have to issue the fastboot command. But moving that slider now will future proof you if you want to unlock.
jmartin72 said:
I wish someone could figure out how to get it done.
Click to expand...
Click to collapse
While I haven't figured out a way to gain the ability to write to the eMMC, it seems that the last byte on the eMMC controls whether the device is unlockable.
Pixxlman said:
What if we could overwrite the bootloader and leave the sim out of the phone and activate it with wifi then verizon can't check the imei and can't lock it? i have a verizon pixel XL i can try this with if someone could walk me through overwriting a bootloader
Click to expand...
Click to collapse
There are multiple problems with that theory. First, Verizon does not lock them. They all come locked, when they start up they phone home to Google and get permission to unlock. And two, the SIM has nothing to do with locking.
What is the point of Google shipping the phones with two different bootloaders and unlocked and locked states.
Some hope with the clkscrew exploit? Sounded like the phone needed to be rooted to work, but being able to pull trustzone keys from a Google variant could possibly enable a workable patch for the Verizon variant.
Have no idea, but sure sounds plausible.
H0wdy said:
Robocuff,
Thank you. That seems to be my situation, but I was wondering why this isn't an option?
https://www.xda-developers.com/verizon-pixelpixel-xl-bootloader-unlock-has-been-released/
Does it no longer work? I understand it probably doesn't, but I didn't know if there was another way.
Click to expand...
Click to collapse
robocuff said:
dePixel8 doesn't work anymore. It only worked for a couple months. Google patched the hole that dePixel8 exploited in the December security update. So, any Verizon phone that was updated in December or anytime after and wasn't all ready unlocked, became unlockable after that.
Click to expand...
Click to collapse
Google did not close the exploit. Verizon did with the release of 7.1.2 in November 2016.
AncientDeveloper said:
I wonder if overwriting the Verizon Pixel's bootloader with a non-Verizon bootloader from one of the factory images would work. The logic behind this is that all G-2PW2100s seemd to have identical hardwares, and factory images contain all the bootloader/radio partition images; so in theory, flashing a non-Verizon factory image should make the device non-Verizon.
(Please note that this is just a theory & I have not tested this. There's a chance that doing this will brick the device.)
Click to expand...
Click to collapse
The package will probably fail to install after modifying because of improper signature. It has been tried before....
AncientDeveloper said:
While I haven't figured out a way to gain the ability to write to the eMMC, it seems that the last byte on the eMMC controls whether the device is unlockable.
Click to expand...
Click to collapse
Probably encrypted, you don't have access to the correct tools, or both.
Would flashing the original image from Google onto the phone and running depixel then. Would that work? Or has that been tried?
Sent from my Pixel using Tapatalk
gobi42 said:
Would flashing the original image from Google onto the phone and running depixel then. Would that work? Or has that been tried?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
No. You can't downgrade with a locked bootloader.
Howdy all,
I'll try to keep things brief but informative.
Yesterday I got the unlock bin for my T-Mobile Oneplus 7 Pro. I unlocked it, flashed LineageOS (latest 17.1), Magisk (19.04 but then updated to latest after install), DM-Verity, and TWRP (unified Q version).
I have installed Nethunter, F-Droid, and some other basic apps.
I just got a new SIM Card from T-Mobile and activated it last night, however it shows the same as the empty SIM slot (which my phone doesn't have a physical second slot) and on the lock screen at the top left rotates between saying: "No SIM card" "No SIM card - T-Mobile" "No SIM card - No service". In the phone the top right does not show any bars, x'ed out or otherwise, however one time after taking it out, googling, then putting it back in it sis appear x'ed out until reboot.
I cannot send texts as it says no preferred SIM card selected, and I cannot make calls due to a lack of service; however, I can receive texts and calls and even answer calls and speak to the calling party just fine.
I was getting nothing, then I saw where someone received a text and it fixed it for them, so I texted myself, got a backlog of texts, but nothing else came of that.
I have no idea what to do from here and only vauge idea of why it may be like this but no understanding of it.
I found this reddit post seeming to detail the issue, but I do not know if it applies to me (presumably does) and I do not understand any of the information in the post, nor do I know what to do with this information:
reddit.com/r /oneplus /comments /gb5jlk /factory_reset_no_sim_card_detected_oneplus_7_pro /
(sorry for the spaces, can't post outside links until after I've posted 10 posts)
and with that I'm all out of idea and knowledge. My background is in Offensive Security, but I know very little about SIM Cards and smart phones so all help is greatly appreciated!
Is the device sim unlocked?
wired57 said:
Is the device sim unlocked?
Click to expand...
Click to collapse
I didn't do it so I'm going to assume it is not. I've only unlocked the bootloader (obviously). How would I go about unlocking the SIM?
Also, the original carrier was T-Mobile and the SIM is also T-Mobile, I assumed this would be ok but is there an issue since I didn't unlock it yet I installed custom stuffs - or what would be causing an issue by not unlocking it? (just trying to learn more )
MagicCooki3 said:
I didn't do it so I'm going to assume it is not. I've only unlocked the bootloader (obviously). How would I go about unlocking the SIM?
Also, the original carrier was T-Mobile and the SIM is also T-Mobile, I assumed this would be ok but is there an issue since I didn't unlock it yet I installed custom stuffs - or what would be causing an issue by not unlocking it? (just trying to learn more )
Click to expand...
Click to collapse
How did you root?
Did you grab a patched boot image or did you boot with the TWRP image and install Magisk yourself?
Grabbing the wrong image is the number one thing that causes WiFi and SIM issues.
tech_head said:
How did you root?
Did you grab a patched boot image or did you boot with the TWRP image and install Magisk yourself?
Grabbing the wrong image is the number one thing that causes WiFi and SIM issues.
Click to expand...
Click to collapse
I used this method (copied from irsa mintTM in a YouTube comment)
"REBOOT TWRP
FORMAT DATA (If you are encryted) your internal memory will be lost!!!
REBOOT TWRP
WIPE DATA & CACHE
Flash Rom
Flash TWRP Installer
REBOOT TWRP
WIPE DATA & CACHE
Flash Rom again
Flash TWRP again
REBOOT TWRP
Flash Magisk 19.4!!!! <----This version
Flash DM Verity zip file <--- Always last file before system reboot
REBOOT SYSTEM AND ENJOY"
Gotta unlock for custom ROMs. Flash back to TMobile firmware do a sim unlock, then you can flash back.
wired57 said:
Gotta unlock for custom ROMs. Flash back to TMobile firmware do a sim unlock, then you can flash back.
Click to expand...
Click to collapse
Oh ok, gotcha! I'll give that a go using this video and method and I'll update you if that fixed everything.
youtube .com/ watch?v=4CeCM88ecv4
Thank you so much!!
wired57 said:
Gotta unlock for custom ROMs. Flash back to TMobile firmware do a sim unlock, then you can flash back.
Click to expand...
Click to collapse
I got the T-Mobile stock everything back and everything locked back down, but my SIM card is showing now service now - the same no sim message as was on LineageOS, not even receiving texts now.
I'll re-seat and mess with it when I get some more time.
wired57 said:
Gotta unlock for custom ROMs. Flash back to TMobile firmware do a sim unlock, then you can flash back.
Click to expand...
Click to collapse
Also, I went to the unlock app and it says it's fully unlocked already and can be used with any carrier...
If you didn't use the msm tool to get you back to the T-Mobile firmware, then you probably aren't on T-Mobile firmware. I had the same issue trying to get lineage to work, and was able to get back to stock and have data.
Since you probably don't have the bootloader unlock code, you need to convert to international firmware, and fully update to at least 10.3.2 before you flash lineage. If you don't, you won't have service.
Sent from my GM1915 using Tapatalk
mjdavis871 said:
If you didn't use the msm tool to get you back to the T-Mobile firmware, then you probably aren't on T-Mobile firmware. I had the same issue trying to get lineage to work, and was able to get back to stock and have data.
Since you probably don't have the bootloader unlock code, you need to convert to international firmware, and fully update to at least 10.3.2 before you flash lineage. If you don't, you won't have service.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
I did use the MSM tool, it's locked, has the T-Mobile boot animation and everything.
I do have the unlock file & code, I had to wait a week to get it.
Hi All,
Been at this for several hours today and feeling a bit frustrated. Here's the context.
I bought a used Verizon Galaxy Note 10 and took it to another country.
I arrived and put a sim card in *(the phone is intended to stay here)
4G signal appeared and text messages came in
Phone blocked signal and said "sorry, your device cannot be activated on another Network right now" then it says to call Verizon.
I call Verizon and ask how to unlock.
After transferring to multiple agents, the answer is that the phone is not locked in their system and that upon inserting a SIM from another carrier, I should be prompted to put in a code and it will be "00000000" to unlock the phone
The phone never presents this option and is perpetually unable to activate because of this sim lock.
At this point, I started reading up on how I could get around this and settled on using odin to flash firmware for a different carrier and maybe having to flash the SM-N970U1 packages because that should allow me to have different stock firmware.
So I proceed to download various different images.
Here is the TMB image for SM-N970U that I downloaded:
https://samfw.com/firmware/SM-N970U/TMB/N970USQU6FUBH
I also figured maybe I would be able to flash the verizon base image and get around this lock:
https://samfw.com/firmware/SM-N970U/VZW/N970USQU6FUCD
So then I proceed to use Odin3_v3.14.4 and place all of the 4 files in their corresponding fields in odin. The file list is as follows for one of the packages:
BL_N970USQU6FUD9_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT.tar.md5
AP_N970USQU6FUD9_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
CP_N970USQU6FUD9_CP19049000_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_OMC_OYN_N970UOYN6FUD9_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT.tar.md5
I click start, the phone is recognized and then the flashing appears to occur successfully until it says pass at the end.
I reboot the phone and I notice right away that the signal is present, but then disappears and as the phone initializes the VERIZON message appears again.
Immediately I'm thinking, ok, I've just reflashed it with the TMobile image but the phone boots and says verizon and the sim lock is still there, so I probably didn't do something right.
So I factory reset, try again, no changes, I try adding the USERDATA and it also does nothing different.
At this point I'm willing to try the U1 firmware, so I download from here:
https://forum.xda-developers.com/t/n970u-and-n970u1-firmware-links-here.3957705/
But when I run the odin flash, I get model mismatch, yet the thread says they're compatible as U1 is just the samsung unlocked version. so I try the odin patch b found here:
https://odindownload.club/download/197/Odin3-v3.14.1-3B-PatcheD.zip
And it fails to write.
I am in desperate need of help as I've been unable to find more specific information, typically in threads people may say they've resolved the issue, but then they don't actually indicate what steps they took, or any of the details surrounding the resolution. If I can get help getting this resolved, I can document the exact steps i've taken in explicit detail so that others can follow them and achieve the same result.
Update:
Downloaded FRIJA to get the latest firmware, am going to explore doing a nand erase and repartition, followed by flashing tmobile firmware to see if that gets around it.
following:
https://technastic.com/odin-nand-erase-samsung/
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Verizon has a 6 month unlock policy. if the phone is free of debt and older than 6 months it should be automatically unlocked. phone them, you bought the phone in good faith.
jwoegerbauer said:
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Click to expand...
Click to collapse
That's why I am thinking of wiping the NVRAM and just re-partitioning. Then I'll flash a non-verizon system onto it. Could be that this resolves it.
Thoughts?
3mel said:
Verizon has a 6 month unlock policy. if the phone is free of debt and older than 6 months it should be automatically unlocked. phone them, you bought the phone in good faith.
Click to expand...
Click to collapse
I spent 2 hours on the phone with them and spoke to 3 different representatives. They all confirmed the phone was not locked in their system. I read it was 60 day unlock policy.
4rg3ntum said:
I spent 2 hours on the phone with them and spoke to 3 different representatives. They all confirmed the phone was not locked in their system. I read it was 60 day unlock policy.
Click to expand...
Click to collapse
With AT&T they give you requested then they gave you an unlock code, it's not automatic. At least it was like this a few years back.
4rg3ntum said:
I spent 2 hours on the phone with them and spoke to 3 different representatives. They all confirmed the phone was not locked in their system. I read it was 60 day unlock policy.
Click to expand...
Click to collapse
sorry yeah, 60 days is the right period.
jwoegerbauer said:
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Click to expand...
Click to collapse
So this appears to be true.
I loaded up ADB and turned on USB debugging and started passing shell commands through and found these files in the system with nvram in the name:
/sys/module/dhd/parameters/nvram_path
/vendor/firmware/nvram.txt_ES03_semco_b0
/vendor/firmware/nvram.txt_1rh_es13_b0
/vendor/firmware/nvram.txt_CS01_semco_b1
/vendor/firmware/nvram.txt_ES02_semco_b0
/vendor/firmware/nvram.txt_1rh_es43_b1
/vendor/firmware/nvram.txt_1rh_es41_b1
/vendor/firmware/nvram.txt_1rh_es32_b0
/vendor/firmware/nvram.txt_ES00_semco_b0
/vendor/firmware/nvram.txt_ES01_semco_b0
/vendor/firmware/nvram.txt_1rh_es12_b0
/vendor/firmware/nvram.txt_1rh_es42_b1
/vendor/firmware/nvram.txt_1rh_es11_b0
Makes me wonder if the value for locked/unlocked is editable in one of those files.
a sample of what is in the /vendor/firmware/nvram.txt_ES03_semco_b0 file:
### RSDB mode Parameters(Both core are active)
## 2g normal:15dB airplane:14dB
#slice/1/grip_rsdb_dynsar_2g=0xbcbc
#slice/1/grip_rsdb_dynsar_2g_2=0xb8b8
## 5g normal:13dB airplane:12dB
#grip_rsdb_dynsar_5g=0xb4b4
#grip_rsdb_dynsar_5g_2=0xb0b0
#
### FCC Mode: 10dB
#slice/1/fccpwrch12=0x28
#slice/1/fccpwrch13=0x28
In any case I have an issue that I can't seem to resolve. Every guide I have found about how to change carrier firmware is pretty straightforward. Yet when I flash the firmware successfully through odin for say, the sprint version of the phone, upon reboot, in about phone still says VZW, which basically tells me the phone isn't actually flashing.
I need to understand why I can't seem to get it to have another carrier's firmware. What am I doing wrong?
jwoegerbauer said:
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Click to expand...
Click to collapse
Maybe I can edit this with ADB?
I have seen several forums where people with the same error message simply flashed another carriers firmware onto the phone and were able to get around it.
Here is someone saying they tried the U1 firmware and it gave them the option to put in an unlock code:
https://forum.xda-developers.com/t/is-verizon-locking-s10.3908683/post-80813873
Every time I try to flash the U1 firmware odin tells me model mismatch.
Update:
I flashed the latest available ATT version of U1 firmware from here:
https://samfw.com/firmware/SM-N970U1/ATT/N970U1UEU6FUDA
Using Odin patch 3B downloaded from here:
https://www.droidmirror.com/downloading/download-odin3_v3-13-1_3b_patched-zip
Having tried many U firmware + USERDATA from different carriers and never was able to get it to say anything other VZW in the about phone section.
By going to the U1 version I was able to get the unlock code portion to pop up when inserting the sim card, the phone also claims it's model number is SM-N970U1 instead of SM-N970U now.
The code Verizon gave me on the phone 0000 0000 flat out DOESN'T work. I called again today and they had their manager use a tool to provide an unlock code because the "unlock" button in their system didn't appear for my IMEI.
That system said the unlock code is 0000 0000 just like the tech the previous day. So now, they're transferring me to the advanced technical support, but somehow I doubt they will give me a code.
In any case, what I would rather do is go through ADB and try to get some binaries or text files out (may require root for these files) and get the unlock code from the device itself.
I wish this thread was more active because there are some good opportunities here to explore the OS itself and the files in it as well as tools that can be used to read the binary.
Spoke with "Advanced" support at verizon. They had no way to generate a code to unlock the device. Basically Verizon's systems didn't automatically generate an unlock code after the previous owners had the phone activated for the minimum 60 days. Because the phone was a prepaid phone and not a post paid phone, their system deleted the history of the of the prepaid account after a certain period of time when the previous owner had sold the phone to the repair shop and it sat there for months.
BASICALLY, Verizon phones are uniquely equipped with a block that prevent legitimate purchasers of various types from being able to use their devices as they hold everyone hostage with their network locking.
It looks like I can't root the device either because of the oem unlock option not being present and the workaround of changing the date not presenting the option.
At this point I'm looking to root the device so I can inspect the OS
4rg3ntum said:
It looks like I can't root the device either because of the oem unlock option not being present and the workaround of changing the date not presenting the option.
At this point I'm looking to root the device so I can inspect the OS
Click to expand...
Click to collapse
Hello I came across your thread because I am having the same issue. I think mine is similar because thus phone was a replacement through asurion/verizon. It also says its unlocked when verszon looks and when asurion looks, but I do not have service for more than 10 secind with my new AT&T Sim. Have you found anything new?.
I also looked into rooting the phone but I don't plan to keep this phone and if I want to do the trade in process and they see the root on the back end I will not receive the trade in money.
TomHanks92 said:
Hello I came across your thread because I am having the same issue. I think mine is similar because thus phone was a replacement through asurion/verizon. It also says its unlocked when verszon looks and when asurion looks, but I do not have service for more than 10 secind with my new AT&T Sim. Have you found anything new?.
I also looked into rooting the phone but I don't plan to keep this phone and if I want to do the trade in process and they see the root on the back end I will not receive the trade in money.
Click to expand...
Click to collapse
If Verizon says the phone is unlocked, make sure to Flash the U package with Verizon bloat. Connect phone to Wifi and the unlock should happen. They only seem to unlock when on the Verizon bloat U package. Anything other than that and the phone stays locked. Once it unlocks you can flash back to whatever you want.