So the story is I switched from telus to wind, what I did first was the QPST AWS band unlock thing, that went smoothly but afterwards I was unable to unlock my phone. I know that I can't reach that special menu because of the latest firmware samsung released which blocked it but I even got a code from telus which I know it's correct, the thing is it doesn't work for some reason... "network unlock request unsuccessful" I tried everything, first I did a factory reset, I restored the file that QPST replaces which I was sure was the source of the problem but no luck there. I rooted my phone, still nothing. I contacted samsung and asked if there was a way to completely reinstall everything, I mean make the phone a clean slate, they said nothing can be done besides a factory reset (officially anyway). So I'm stuck with a locked phone that won't unlock with the unlock code. Anybody have any idea what I can try? I have a brand new galaxy s4 that I can't use, to some extent it's heartbreaking...
I did some more research and I found that its possible that the device is "frozen"? And that you need some unfreeze code, mck "manufacturer control key"? Anyone know anything about this? I'm dead in the water, I've tried everything I could find
Try fastgsm.com.
Hi,
I have a Defy MB525 on T-Mobile running CM 7.2. The phone is getting old and has some hardware problems, so I bought a more gently used one on eBay. I've rooted the new one and successfully installed Bootmenu, 2ndInit, and CM 7.2, but when put my SIM card in it, it wants an unlock code. I tried the soft unlock method discussed here, but no success. I then tried the troubleshooting recommendation involving airplane mode and terminal emulator, but that didn't work either. I then got the idea to backup my "old" phone and restore it to the "new" one, and that went smoothly, *BUT* while I no longer get prompted for a SIM unlock code, there is an "x" next to the service bars and the phone indicates "no service." Both old and new phones have EPU93_U_00.59.01 baseband, old phone does get service, while new one does not. I'd love to hear any advice people may have. Oh, new phone was on Moviestar service . . . sorry for the stupid question, but when I've been prompted for a SIM unlock code is it Movistar's unlock code that I'm being prompted for or is it T-Mobile's? I assume that SIM unlock code is associated with the phone and not the particular SIM card itself--is that right?
Thanks,
Doug
I guess what you need to do is install Baseband switcher 4.1 or 4.0 and configure it so it grabs the correct baseband
Dear experts,
I have a T-mobile S6edge plus, SM-G928T, build MMB29K...... purchased from US and got it rooted and sim unlocked for using other SIM. I am not getting any OTA, instead a message appears which says, unauthorised modification to operating system, download updates via Smart switch or customer centre.
My question here is, if, in the first place, i even get an update in smart switch on PC, should i update my phone? And if i update my phone, will it remain network unlocked? coz i still have all those T-mobile apps on my phone including "device unlock" app which (as i have heard from someone) gets removed once T-mobile unlocks the phone themselves.
Is there any chance that my phone gets network locked again after the update?
Help will be greatly appreciated.
Regards
I moved my T-Mobile SIM card from my Nexus 6 to my never used, eBay purchase, 6p. The 6p does not detect the SIM card. I reinserted it multiple times with no luck. I don't know if it matters that I installed TWRP, Nitrogen ROM and Franco kernel, without the SIM in the phone?
The phone is otherwise fully functional.
Any ideas on what might be going wrong? The package slip that came with the 6p states, "Tested for Key Functions, Ready for Resale". I've contacted the seller for advice.
msmcintosh said:
I moved my T-Mobile SIM card from my Nexus 6 to my never used, eBay purchase, 6p. The 6p does not detect the SIM card. I reinserted it multiple times with no luck. I don't know if it matters that I installed TWRP, Nitrogen ROM and Franco kernel, without the SIM in the phone?
The phone is otherwise fully functional.
Any ideas on what might be going wrong? The package slip that came with the 6p states, "Tested for Key Functions, Ready for Resale". I've contacted the seller for advice.
Click to expand...
Click to collapse
Probably should of checked it out before loading a custom ROM. That being said if the ROM is 8.0 I don't think the first version of the update is compatible with T-Mobile.
"8.0.0 (OPR6.170623.013, Aug 2017, Not for TMO/USCC/Fi)"
You should maybe try a stock ROM first. Get nexus root kit. There is an option to revert the phone back to stock. Might help.
Just a shot in the dark. May also be locked to a region. Good luck though.
I reinstalled stock Oreo. Now, I'm only seeing "No Service". I don't know if this is of significance, but when I check Settings - > System - > About phone - > Status, SIM status everything is blank. At least the SIM was detected. I didn't realize when I installed stock Oreo it would wipe out my SDcard.
The vendor image is used with Nitrogen was opr5.170623.007.img.
And I suppose the sim works in other phones?
It's hard to say what is going on. May just be in backwards?
Aside from the bootloop and battery issues the 6p has been awesome as far as loading ROMs. You never have to replace the bootloader so even if you break the recovery it can be fixed easily. Not the same for my sapphire unfortunately.
Anyways I would first say it may be a physical issue, Especially if the sim says it's blank. Again, good luck.
I believe it's just Android 8 and not the phone. Go through any 6p Oreo thread and will find one person with this problem. Solutions that where posted fingerprint/pincode security off before flashing, no encryption on first boot and solution that worked for me complete wipe of phone flashing stock Oreo. I haven't heard any direct answer on what the cause is and I think the first 2 solutions worked for people because they did a clean flash of stock Android 8 anyways.
Yes, the SIM works fine in my Nexus 6. I noticed under SIM status, it lists "No signal".
I installed the factory Nougat ROM and still no service.
Under SIM status in Settings, Network is Unknown, Signal strength is 0, Cellular network type is Unknown and Service state is Out of Service.
msmcintosh said:
Yes, the SIM works fine in my Nexus 6. I noticed under SIM status, it lists "No signal". I installed the factory Nougat ROM and still no service. Under SIM status in Settings, Network is Unknown, Signal strength is 0, Cellular network type is Unknown and Service state is Out of Service.
Click to expand...
Click to collapse
Is your IMEI field blank too in Settings? If the phone does not have an IMEI, the device may have corrupted EFS partition(s). Boot the device to bootloader (fastboot mode) and select "Barcodes". Is your IMEI there? Is your model a H1511 (US model)?
Put a known working SIM in the phone from a different carrier (preferrably not an MVNO), If that doesn't work, since your phone is new (to you) there is no harm in fastboot formatting these 3 partitions (system, cache and userdata) and then using the Google script (batch file) that comes with a full factory image. Not a factory reset, not manually flashing a ROM. One other possible scenario is that if the phone was previously used on ProjectFi, you may need to contact Google and have your phone's IMEI de-registered. Hopefully you get it working and won't be forced to return the phone.
v12xke said:
Is your IMEI field blank too in Settings? If the phone does not have an IMEI, the device may have corrupted EFS partition(s). Boot the device to bootloader (fastboot mode) and select "Barcodes". Is your IMEI there? Is your model a H1511 (US model)?
Put a known working SIM in the phone from a different carrier (preferrably not an MVNO), If that doesn't work, since your phone is new (to you) there is no harm in fastboot formatting these 3 partitions (system, cache and userdata) and then using the Google script (batch file) that comes with a full factory image. Not a factory reset, not manually flashing a ROM. One other possible scenario is that if the phone was previously used on ProjectFi, you may need to contact Google and have your phone's IMEI de-registered. Hopefully you get it working and won't be forced to return the phone.
Click to expand...
Click to collapse
Barcodes shows IMEI present and model is H1511. I ran the script in the full factory image for Oreo and then tried the same with Nougat. I didn't reformat the partitions prior to flashing ROM. Is this important or does the factory image replace them anyways?
I don't have access to another carriers SIM card.
msmcintosh said:
Barcodes shows IMEI present and model is H1511. I ran the script in the full factory image for Oreo and then tried the same with Nougat. I didn't reformat the partitions prior to flashing ROM. Is this important or does the factory image replace them anyways? I don't have access to another carriers SIM card.
Click to expand...
Click to collapse
The script uses fastboot erase which does not format the partitions. Formatting returns partition information, any errors and in some cases corrections. You did not mention IMEI within settings, both under "SIM Status" and "IMEI information". If present in bootloader, but not in settings, this may further point to a SIM card. Until you try (borrow) another carrier's SIM for 5 minutes you won't know for sure. At the very least you could get TMo to provision you new SIM. They should not charge you for this, and it may change your situation. There are many threads on this very same topic. Maybe searching those would give you another idea.
v12xke said:
The script uses fastboot erase which does not format the partitions. Formatting returns partition information, any errors and in some cases corrections. You did not mention IMEI within settings, both under "SIM Status" and "IMEI information". If present in bootloader, but not in settings, this may further point to a SIM card. Until you try (borrow) another carrier's SIM for 5 minutes you won't know for sure. At the very least you could get TMo to provision you new SIM. They should not charge you for this, and it may change your situation. There are many threads on this very same topic. Maybe searching those would give you another idea.
Click to expand...
Click to collapse
According to Google, the phone was purchased from them. They do not know if the phone is financed, as this would cause the IMEI to be locked. I'll try the T-Mobile store next.
Spent an hour at T-Mobile. The sales rep was determined to fix it, but in the end was unsuccessful. The Ebay seller issued an RMA and I dropped off at the P.O.. Will try getting another.
msmcintosh said:
According to Google, the phone was purchased from them. They do not know if the phone is financed, as this would cause the IMEI to be locked. I'll try the T-Mobile store next.
Click to expand...
Click to collapse
No, I meant the the Google-Fi the MVNO (carrier) not finance. If the phone was activated on Fi, it will have to be de-registered on their end. You still did not reply about IMEI present or not in Settings>>Sim info?
v12xke said:
No, I meant the the Google-Fi the MVNO (carrier) not finance. If the phone was activated on Fi, it will have to be de-registered on their end. You still did not reply about IMEI present or not in Settings>>Sim info?
Click to expand...
Click to collapse
When I went into Settings, the IMEI was present, but no carrier information. The phone recognized the SIM card, but that was all.
In the chat session with Google Support, I did ask about Google-Fi and she wrote that she was unable to provide any information on that. She said the only information she could provide is where the phone was purchased.
I came across the same issue. Just flash your vendor.img using flashfire, this will fix everything.
Another fix for the no sim is too turn off security pin lock and reboot the phone. I take no credit for this find just spreading the good word. ?
Exodusche said:
Another fix for the no sim is too turn off security pin lock and reboot the phone. I take no credit for this find just spreading the good word.
Click to expand...
Click to collapse
Thanks so much. Worked like a charm and could then reenable pin lock and reboot and SIM kept working.
swamp2 said:
Thanks so much. Worked like a charm and could then reenable pin lock and reboot and SIM kept working.
Click to expand...
Click to collapse
could you detail how to do just that? Because I'm in Brazil and I have the same problem.
As of this point the warranty on it has long since expired (for both Motorola and Target, the place where it was purchased) so we're pretty much willing to try anything to get it working
I've got with me here a G5 Plus XT1687 that, at best, I can describe as being in a state of "limbo". Its bootloader mode can only be set to flashing_unlock and flashing_lock. We've obtained the unlock key from Motorola's tool and have tried fully unlocking the bootloader multiple times following the guide on XDA, but it seems to not want to accept the command fully and remains on flashing_unlock. When I try to relock everything to start over, it gets stuck on "flashing_lock" and won't go back to fully locked. When it's in the flashing_unlock state I am able to flash ROMs and TWRP builds, so technically it's unlocked.... sort of. I'm unable flash SOME things, like new bootloaders or gpt partition tables, but other things will work just fine, albeit with the occasional "invalid signature" message following flashing. But this right here is only the start of our problems.
Having purchased the US retail XT1687 model, it was supposed to come carrier unlocked out of the box. My friend who got this didn't have a SIM when he got it at the time, so he just used it as a WiFi-only media player sort of thing. When he finally got a T-Mobile SIM and put it in, it asked him for an unlock code. This of course doesn't make any sense, because we didn't get this from a carrier, so why would it be locked to anything in the first place. It was tried with multiple different SIM cards, running multiple different ROMs (and even stock firmware) all with the same result: the phone seems to be network locked to nothing at all.
I tried calling Motorola and they said they can't make an unlock code for us since it's the carrier that decides what algorithm to use for network unlock codes... but this phone didn't come from a carrier, so I don't know what to do.
Fixing the bootloader thing would be nice, but my main goal here is to try and remove this nonsensical network lock so my friend can actually use it with T-Mobile. At this point he doesn't want to send it back (since we'd have to pay for the repairs, and he got a cheap LG to use as a primary phone anyway). That being said, we're pretty much willing to try anything to get it working. Any suggestions?
EDIT: just want to mention as well, we've never had a problem with the IMEI being set to 0. It's always been what it originally was