If you have trouble with SIM unlock on custom ROM on AT&T or other carriers read this
I came across this GitHub wiki page that discusses unlocking the E970 for all networks (I know that is a different phone, keep reading to see why it relates) and says that you need to use the stock ROM for it https://github.com/bibanon/android-development-codex/wiki/E970-SIM-Unlock. This got me thinking that maybe the reason trying to unlock my E980 failed when it was running CM back in 2016 was due to a similar reason, so I backed up all the data on the internal storage and then restored to stock using LG flash tool. I then followed "Method 2" in this guide https://fastphoneunlocking.com/how-to-unlock-any-lg-optimus-g-pro-e980-with-an-unlock-code (since it didn't require a non accepted SIM card, and I didn't have one either) using an unlock code AT&T had provided me with last year and sure enough, on the stock ROM it worked.
Moral of the story is, if you are trying to do a SIM unlock from AT&T (or possibly other carriers, but I am not sure on that) on this phone with a custom ROM and it isn't working, backup your data, flash back to AT&T stock and then try it there.
So I was on Oreo and accidentally flashed back to 7.1.
Didn't brick it but now it doesn't recognize my sim even after flashing back to Oreo.
I tried to fastboot the tmo baseband but no luck there.
Anyone run across this or have any suggestions?
That was one of the 1st thing I ran across in the Oreo update thread. With development just really getting fired up I'll be surprised if you find a fix. If. I was you I would flash the mod that hides the unlocked bootloader warning and take it to TMobile. It's only a 5 dollor charge for defective devices. I've returned a total brick before.
So I am on the same board. The problem is I'm in UK and I cant claim warranty repair. Also my warranty was void in December soon when I generated bootloader unlock key.
SO what have I tried so far?
Hard brick bootloader to state when it is Qualcomm loader- only blank flash and Oreo Flash All is able to bring it back to live.
Ive also tried boot from B slot in twrp but it looks like my B partition is messed up. Fastboot will show red warning about no flashable A/B slot and only oreo flash can get it back to boot because it will oem lock itself.
When I get back fully on unlocked bootloader to 7.1.1 I cant update via adb sideload or update menu in settings. Both will fail.
Sim looks like it is detected on start but when taken out and slided back in it wont show up.
I have QCN area backed up with nv data but it wont help me.
Please note when boot is bricked oreo flash all will flash it on locked bootloader and will not show warning screen at all about botloader. However I was unable to boot to recovery from that point so I had to unlock it and flash 7.1.1 then oreo again.
So if someone could do nandroid backup of clear not set up rom it would be great. I can try restore it. I dont even know if twrp is able to do backup on A/B device.
Also if someone could read NV data from phone and share it ( from phone with working radio of course) would be really appreciated.
Can someone PM me NV backup? I need urgently qcn file. I think my hw partition is messed up. Please don't share it in this post as it can contain IMEI.
this is what i did, and why there is a giant post in caps in the thread that says not to do this. You essentially end up with a bootloader mismatch which hoses the radio. the only solution is a replacement.
and DONT DOWNGRADE !!!
byt3b0mb said:
this is what i did, and why there is a giant post in caps in the thread that says not to do this. You essentially end up with a bootloader mismatch which hoses the radio. the only solution is a replacement.
and DONT DOWNGRADE !!!
Click to expand...
Click to collapse
Sorry but warning isn't clear. I did not enjoy Oreo and was looking for unlock method.
Also bootloader match to my current Oreo rom and radio but still no sim detected so I think it is hw partition messed up. When I flash retail Oreo on it bootloader just change itself to retail Oreo version. Still no sim.
Device is useable as paperweight with WiFi
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Everything about the phone works 100% except the Sim slot. It's like it can't read the Sim. It knows there is a sim in, but it can't access it.
On Oreo oem retail version.
donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
I'm happy to stay on 8 but need my sim get back to life. All works fine except SIM card is not detected.
My phone boot as normal. When downgraded it won't accept ota's. It won't install it via sideload too. SIM card remain undetected no matter what rom and what version( T-Mobile, retail, etc) when I try to boot from slot B via twrp it won't boot. It will show bootloader screen with unbootable a/B partition.
robdevil said:
I'm happy to stay on 8 but need my sim get back to life. All works fine except SIM card is not detected.
My phone boot as normal. When downgraded it won't accept ota's. It won't install it via sideload too. SIM card remain undetected no matter what rom and what version( T-Mobile, retail, etc) when I try to boot from slot B via twrp it won't boot. It will show bootloader screen with unbootable a/B partition.
Click to expand...
Click to collapse
i got a script that was able to get my tmobile variant back up and running on any version i installed please give this a try and let me know.
just copy all this to the platform tools drectory ans double click the oem flash.bat the oem lock.bat will re-lock your boot-loader if you want that as well.
pm me for a link to my drive since im still under 10 posts
Kaesberg said:
i got a script that was able to get my tmobile variant back up and running on any version i installed please give this a try and let me know.
just copy all this to the platform tools drectory ans double click the oem flash.bat the oem lock.bat will re-lock your boot-loader if you want that as well.
pm me for a link to my drive since im still under 10 posts
Click to expand...
Click to collapse
pm sent. i could use this
Please let us know if it works
Not OP, or guy with a link, but I did a similar bad thing and ended up on the retail Oreo without working SIM. What I did was take the modem file (the one that you fastboot flash to modem) from the tmo oreo zip and replaced the modem file in the retail oreo zip with the tmo one -- just change the name of the tmo modem file to the one that comes in the retail oreo zip and then run the retail flashall.
Still no way to get the latest tmo update that fixes some volte issues, though. Since I purchased within 14 days, I just added insurance and will probably end up drowning the phone to replace it... unless someone has a better idea. :/
breakerfall said:
Not OP, or guy with a link, but I did a similar bad thing and ended up on the retail Oreo without working SIM. What I did was take the modem file (the one that you fastboot flash to modem) from the tmo oreo zip and replaced the modem file in the retail oreo zip with the tmo one -- just change the name of the tmo modem file to the one that comes in the retail oreo zip and then run the retail flashall.
Still no way to get the latest tmo update that fixes some volte issues, though. Since I purchased within 14 days, I just added insurance and will probably end up drowning the phone to replace it... unless someone has a better idea. :/
Click to expand...
Click to collapse
Where did you get this modem?
mattlowry said:
Where did you get this modem?
Click to expand...
Click to collapse
from the tmo oreo zip here (bottom of the OP):
https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932
it's the NON-HLOS file
this is the retail oreo:
https://forum.xda-developers.com/showpost.php?p=75250794&postcount=82
I swapped the NONHLOS file from the tmo oreo into the retail oreo and I currently have working tmo service/SIM on the retail (tmo-less) oreo
donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
My Moto Z Play is bricked, after downgrade of oreo to nougat, my imei not work. so i decided go to oreo again, when i reboot my phone bricked. help me please!!!
Try this. Updated my Sprint only thread to be a little more universal.
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
bricked moto z2 force tmobile
donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
guys i tried blank flash oreo on mine bricked tmobile moto z2 force and it isnt working, any help would be great on this , thanks.. and also i have tried many blank flashes some for even other moto phone models none worked so far.. one or two of them got really close the oreo one did but failed at last part... tried about hundred times and yes i even tried holding down power and volume button with no success it didnt work it did though recognize the phone but still failed trying to boot or flash it though... seems to me it needs either up to date or just different blank flash it seems, but i dont know that for sure...
Hi all I have a MediaPad M2-802L it was on stock lollipop branded by Vodafone Australia, I upgraded to Marshmallow using a tutorial here on xda, I lost access to oem unlock, I tried reverting back to lollipop with huawei recovery and it "failed" but reverted still no oem unlock, I was flashing roms and accidentally flashed a DoCoMo rom and now I'm stuck on DoCoMo rom and nothing will flash back, I tried USB recovery and it gets stuck at 90%, Any ideas for fixing this? Much appreciated, Cheers, R3AL
So I've downloaded latest FW from Sammobile, and would like to flash it to my phone (SM-G960F).
The Sammobile firmware page describes how to flash the FW using Odin.
I believe these instructions assume a stock phone. Does having TWRP affect the Odin flashing procedure at all? I'm guessing that it will simply restore the stock recovery, and I will need to reinstall TWRP.
UPDATE:
I just flashed the FW following Sammobile directions without issue.
You need to reinstall TWRP after flashing. The OEM unlock setting was already enabled, so I did not need to format data or do dm-verity thing you do when installing TWRP, but YMMV.
Hi. Random question- I have an unlocked Samsung Z Fold 3 (SM-F926UI) that I bought from Samsung in the US. With the new software update it now shows the eSIM option in my phone. I am currently carrying a work phone and a personal phone. I would love to just carry one mobile phone instead of two. What I learnt is that I can transfer both my phone numbers to my Z Fold 3 (one physical + 1 eSIM) but only one number will work at any given time and other one would be at 'standby' mode (practically switched off).
I wonder if I can buy a dual sim tray for Z Fold 3 from ebay and install/flash latest firmware from sammobile or some other website. Would it allow me to use dual sim (both active at the same time) on my Z Fold 3?
I wonder if the hardware is already there, I just need to 'jailbreak' it??
Thanks in advance.
I'm trying to root and update my friends T-Mobile 7T (HD1907) to the most recent generic ROM. She's leaving the country and has no need or desire to keep the T-Mobile branding, and getting on a generic ROM seems like it will allow for faster updates.
I've seen some threads that look like they might help, but having had issues in the past with other attempts on other phones, I know that one little oversight can cause HOURS of frustration.
So I figured I'd ask first and try to save the drama this time.
Where can I get the correct ROM to do what I want on this phone?
I have TWRP installed and have rooted with Magisk.
Current build # is 10.0.3 HD63CB
Carrier configuration version is 2.370001
I appreciate any help on this, thanks!
JustinChase said:
I'm trying to root and update my friends T-Mobile 7T (HD1907) to the most recent generic ROM. She's leaving the country and has no need or desire to keep the T-Mobile branding, and getting on a generic ROM seems like it will allow for faster updates.
I've seen some threads that look like they might help, but having had issues in the past with other attempts on other phones, I know that one little oversight can cause HOURS of frustration.
So I figured I'd ask first and try to save the drama this time.
Where can I get the correct ROM to do what I want on this phone?
I have TWRP installed and have rooted with Magisk.
Current build # is 10.0.3 HD63CB
Carrier configuration version is 2.370001
I appreciate any help on this, thanks!
Click to expand...
Click to collapse
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
The key is to force reboot into bootloader mode when u get stuck on pink T-Mobile bootscreen after first "flash-all" script so u can repeat this "flash-all" second try which will then work.
Thanks for that. I managed to unlock the bootloader and update to Oxygen OS 11.0.7.1.HD65AA, which I believe is the most recent global ROM.
The model of the phone still shows HD1907, which I thought should change from the T-Mobile model to the global model in this process, but perhaps this is normal.
Everything seems to be working fine, but I'm a bit concerned it won't update properly if its not entirely "converted" to the global model.
I did the same. All working fine though. It brought me unlocked bootloader to flash the dual sim firmware or global. All works. Only concern I have is ..The unlock bootloader ticker in dev options shows greyed out "Already Unlocked" but, the ticker is in the off position to the left which is odd. My friends was done by token but mine using patched boot msm. Any reason to be concerned ? Perhaps that's going to hinder the re lock and possible re unlock ?