Thought I would share based on my experiences on trying to get this phone to work on t-mobile. It works on ATT 3g/T-mobile Edge, but still a pretty cool phone to have.
Also another note, this is a mod that will only go through on Windows. You will need ROOT EXPLORER app for this method to work.
1 - Make sure you are on the stock XT862 ROM, if you aren't flash it via this method found here: http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/
2 - Make sure your phone is rooted, if not download the following and follow the steps found here: http://www.psouza4.com/droid3/
3 - Unlock the phone. This can be accomplished by purchasing the unlock code, and later entering the code upon insertion of a sim card. (T-mobile ATT sim cards will work, but you will get an error saying UNLOCK FAILED, this is NORMAL do not freak out)
4 - Download the following files and unzip it to your desktop: http://www.mediafire.com/?y1wjw775v8itsx3
5 - Click Start and open cmd.
6 - Type in the following in cmd:
'cd desktop'
'cd fastboot'
'moto-fastboot flash radio radio.img'
ONCE it flashes, then enter:
'moto-fastboot reboot'
7 - Use root explorer to push the build.prop into the system folder
8 - Reboot, select GSM/UMTS in Network Settings.
AND BAM now it works. If there is any confusion please let me know.
Nice! Is that the XT883 radio you're flashing or a real unlocked (and signed) XT862 radio?
Also - change
Code:
ro.mot.phonemode.vzwglobalphone=1
to
Code:
ro.mot.phonemode.vzwglobalphone=0
in build.prop to get normal reading on signal strength indicator.
You can also change
Code:
ro.telephony.default_network=7
to
Code:
ro.telephony.default_network=3
so phone starts automatically in GSM/UMTS mode after hard reset.
Can anyone confirm that it's running on AT&T with 3G/4G?
Sent from my Droid Razr using xda premium
MeNaCe2s0cieTy said:
Can anyone confirm that it's running on AT&T with 3G/4G?
Sent from my Droid Razr using xda premium
Click to expand...
Click to collapse
it has att 3g bands you can check for yourself over at gsm arena.
leobg said:
Nice! Is that the XT883 radio you're flashing or a real unlocked (and signed) XT862 radio?
Also - change
Code:
ro.mot.phonemode.vzwglobalphone=1
to
Code:
ro.mot.phonemode.vzwglobalphone=0
in build.prop to get normal reading on signal strength indicator.
You can also change
Code:
ro.telephony.default_network=7
to
Code:
ro.telephony.default_network=3
so phone starts automatically in GSM/UMTS mode after hard reset.
Click to expand...
Click to collapse
Thanks man I'll reupload when I get back home with the edited bits . It is the XT883 radio.
Nice Guide!
I've read some people have had trouble unlocking the D3....and apparently it could be due to it being used on the Verizon network who then alter the unlock code via some update.
Anyone know if there is any truth in this? (I'm awaiting the delivery of a used D3 so would be handy to know).
fl4r3 said:
Nice Guide!
I've read some people have had trouble unlocking the D3....and apparently it could be due to it being used on the Verizon network who then alter the unlock code via some update.
Anyone know if there is any truth in this? (I'm awaiting the delivery of a used D3 so would be handy to know).
Click to expand...
Click to collapse
Even after the update, if you restore it to the first link and then follow the steps, you will be fine. It can still be unlocked.
Awesome! I am about to try this on my friend's droid 3. Are there issues with the market (as some have mentioned in a previous thread)?
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
I am stuck on <waiting for device> in the command prompt after telling it to flash the radio. What sort of USB connection should I be selecting?
EDIT: I'm an idiot.... I figured it out!
Is anyone else who is using this method on AT&T experiencing super slow data speeds? I have tried the sim card in an at&t branded phone and it seems to work ok. On the Droid 3, I am getting a ping of 2500~ ms, and speeds in the 15-60kbps range.
I can't seem to add an APN and connect to the 3G network. Does anyone else have this issue? I am using a Bell SIM at the moment
Follow all the steps, no luck here
When I put the unlock code, phone shows for a sec "requesting unlock" and goes back to a subsidy lock message with a discard dialog box.
After that, I followed all other steps, and still enter unlock code appears
Any ideas?
I dont have an att sim card, Im just using foreign sim cards cause Im outside US.
geek_riot said:
Is anyone else who is using this method on AT&T experiencing super slow data speeds? I have tried the sim card in an at&t branded phone and it seems to work ok. On the Droid 3, I am getting a ping of 2500~ ms, and speeds in the 15-60kbps range.
Click to expand...
Click to collapse
You can always call the carrier and make sure they are allowing your phone to connect. I'm not sure if this is the problem, but I read about another AT&T branded 4G phone (the D3 will never get 4G) getting only edge because the carrier thought it was foreign, and they just called in and gave the IMEI number to get access.
The customer service rep may not understand your problem, but just tell them the truth that you want to use your compatible device on your valid account and they should redirect you to someone who can help.
I can verify this works on T-Mobile and AT&T since I've tested it on both. Didn't test 3g on AT&T though cuz I didn't think about it lol. I know it allows the connection to umts in the settings though.
The OP poster helped me get it working on my phone just make sure you follow the directions closely and it's pretty simple. If your unlock codes aren't working because you got them off the internet, you may need to have the phone put on Verizon temporarily to get them to give you a code. Just ask a friend with a valid account to help you out.
Good luck to everyone, this is a great hack that definitely saves some money while letting us use this cool phone. I will have to edit my build.prop as mentioned above to fix the reboot network loss problem, thanks for that as well!
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img & custom build.prop
If verizon changed the codes while phones are connected to his network, changes could only be stored on a new bootloader.
There is no other unwritable part on the phone.
Wonder if the original poster used an ebay code or a verizon one...
Nice job! Pretty amazing what can be done with fastboot and signed radio images!
Custom ROM
What will happen if somebody follows this procedure and unlock the phone for AT&T but afterwards flash another rom? Will the radio still be unlocked for AT&T?
koukobin said:
What will happen if somebody follows this procedure and unlock the phone for AT&T but afterwards flash another rom? Will the radio still be unlocked for AT&T?
Click to expand...
Click to collapse
As long as that ROM you're flashing does not have radio image in it, you should be fine. If you meant sim lock - once unlocked, it will remain unlocked forever.
Sent from my HTC Desire Z using Tapatalk
I was asking about radio unlock, i know sim unlock is permanent. But has anyone tried to install any rom after the radio unlock and if yes which one?
thanks
koukobin said:
I was asking about radio unlock, i know sim unlock is permanent. But has anyone tried to install any rom after the radio unlock and if yes which one?
thanks
Click to expand...
Click to collapse
Just as @leobg said,
leobg said:
As long as that ROM you're flashing does not have radio image in it, you should be fine...
Click to expand...
Click to collapse
Now, I haven't tried flashing another ROM since flashing the xt883 radio.img, because I really don't mind the stock ROM with some build.prop tweaks and the help of Zeam Launcher. I would assume that any ROM you flash would cause the build.prop and radio.img to be replaced with new ones, made specifically for that ROM. You should probably consult with the developer of the ROM you want to use, and ask them if the build.prop changes specific to this process will have issues with their ROM. The xt883 radio.img shouldn't have any conflicts, but I believe it will still require the custom build.prop file which is found in the OP, or at a minimum the specific changes which allow this tweak to work.
BenSWoodruff said:
Just as @leobg said,
Now, I haven't tried flashing another ROM since flashing the xt883 radio.img, because I really don't mind the stock ROM with some build.prop tweaks and the help of Zeam Launcher. I would assume that any ROM you flash would cause the build.prop and radio.img to be replaced with new ones, made specifically for that ROM. You should probably consult with the developer of the ROM you want to use, and ask them if the build.prop changes specific to this process will have issues with their ROM. The xt883 radio.img shouldn't have any conflicts, but I believe it will still require the custom build.prop file which is found in the OP, or at a minimum the specific changes which allow this tweak to work.
Click to expand...
Click to collapse
Aslongasyoukeeptheradioandbuild.propchnges
Yikesmyspcebarisfiling and some"a's"
Enviado desde mi DROID3 usando Tapatalk
Will loading XT883 radio undo the wifi-hotspot hack?
Related
Hi,
I just recently bought (second hand, on eBay - that was my first mistake...) a Verizon Droid 3 (so presumably an XT862?). It is failing to connect to any network, and is not detecting my SIM card. I'm in Australia, so there is no CDMA network here (but GSM on 850, 900, and 2100; UMTS 850, 2100).
The peculiar thing is that the Baseband is 'unknown' in the phone 'About' screen. Likewise, the IMEI, IMEI SV, Network, MEID, MIN, ERI and PRL are unknown. I don't know how many of these relate to the network, but I can't imagine an 'unknown' baseband is a good thing.
The phone is ostensibly 'unlocked', but shouldn't it connect to networks for emergency calls? (which is doesn't), even if it is locked and so doesn't detect my SIM?
The listed Kernel version in 2.6.35.7-g790a33c [email protected] #1
Build number is 5.5.1_84_D3G-55
I haven't rooted it or anything, and just did a wipe from the bootloader but to no avail.
I haven't tried reflashing it with the Fast/easy unbrick technique, because I don't want to go messing with the device if I'm just going to have to return it.
So in brief, the questions are:
1. Is it likely a flash would fix this problem? Does anyone have any experience with this problem? (I did search, but none of the answers really covered it)
2. Does the fast/easy unbrick take it back to stock? If so, which stock - Verizon?
3. Can I do the fast/easy unbrick? It doesn't fix the thing to CDMA does it (there was no indication it does in the relevant thread, I'm just being paranoid).
Cheers,
Fighting disappointment
Hi
Sorry to hear that. I think your phone have radio problems.
Some time ago i have this type of problem when installing ICS or any other rom with the xt860 radio inside a stock verizon rom.
Do the easy unbrick method that you post to back to stock rom and radio.
And after that see that if the baseband, imei appear correct.
If the phone ask you the subsidy code the phone is not unlocked.
Try that and post it here.
FFU5y said:
Hi,
So in brief, the questions are:
1. Is it likely a flash would fix this problem? Does anyone have any experience with this problem? (I did search, but none of the answers really covered it)
2. Does the fast/easy unbrick take it back to stock? If so, which stock - Verizon?
3. Can I do the fast/easy unbrick? It doesn't fix the thing to CDMA does it (there was no indication it does in the relevant thread, I'm just being paranoid).
Cheers,
Fighting disappointment
Click to expand...
Click to collapse
1) try this http://forum.xda-developers.com/showthread.php?t=1406812
I heard it solves problems for those with an unlocked phone but cannot connect to GSM
2) Yes. To XT862 verizon 5.6.890
3) I don't see why not
Awesome, thanks guys.
I've decided to contact the seller and see what resolutions they offer before I go and do anything that may prevent me being able to return the phone.
With some luck (probably a lot of luck) they will permit me to reflash the phone to see if it fixes the problem, and still return the phone if it doesn't resolve the problem.
In that case, I'll post the results here so others can see what the outcome was.
Cheers.
Just an update: neither the unbrick method, not the XT883 radio.img fixed the problem, sadly.
Cheers for the help anyways.
Same Problem on brandnew Verizon XT862
Hi Guys,
I have the same problem here. I got a Droid3 from an american friend. Some keys didnt work lately. And as it was still under warranty, I did send it to him and he sent the exchanged new device back to me. So it's not activated or anything. May this be the problem? It does not even activate radio. No question for SIM, no SIM detected. No IMEI, no baseband version. Strange.
Is it possible to send it to motorola, so they "activate" it? I can't connect verizon from germany(infos?).
Maybe it could be done with radiocomm???
Would be glad about any help!
FFU5y said:
Just an update: neither the unbrick method, not the XT883 radio.img fixed the problem, sadly.
Cheers for the help anyways.
Click to expand...
Click to collapse
Find a solution? Im also from Australia and thinking of doing the same thing as u, i.e buying locked Verizon Droid 3 n unlocking
Sent from my NexusHD2 using Tapatalk 2
FFU5y said:
Hi,
I just recently bought (second hand, on eBay - that was my first mistake...) a Verizon Droid 3 (so presumably an XT862?). It is failing to connect to any network, and is not detecting my SIM card. I'm in Australia, so there is no CDMA network here (but GSM on 850, 900, and 2100; UMTS 850, 2100).
The peculiar thing is that the Baseband is 'unknown' in the phone 'About' screen. Likewise, the IMEI, IMEI SV, Network, MEID, MIN, ERI and PRL are unknown. I don't know how many of these relate to the network, but I can't imagine an 'unknown' baseband is a good thing.
The phone is ostensibly 'unlocked', but shouldn't it connect to networks for emergency calls? (which is doesn't), even if it is locked and so doesn't detect my SIM?
The listed Kernel version in 2.6.35.7-g790a33c [email protected] #1
Build number is 5.5.1_84_D3G-55
I haven't rooted it or anything, and just did a wipe from the bootloader but to no avail.
I haven't tried reflashing it with the Fast/easy unbrick technique, because I don't want to go messing with the device if I'm just going to have to return it.
So in brief, the questions are:
1. Is it likely a flash would fix this problem? Does anyone have any experience with this problem? (I did search, but none of the answers really covered it)
2. Does the fast/easy unbrick take it back to stock? If so, which stock - Verizon?
3. Can I do the fast/easy unbrick? It doesn't fix the thing to CDMA does it (there was no indication it does in the relevant thread, I'm just being paranoid).
Cheers,
Fighting disappointment
Click to expand...
Click to collapse
Read this, it worked for me.
http://forum.xda-developers.com/showthread.php?t=1686911
someone solve this problem?
I bought a new unlocked D3 from an online vendor who shipped it from Hong Kong.
I stuck in my Optus SIM and it just 'worked'.
I'm running hashcodes's CM10 on it at the moment.
So the phone is perfectly capable of working in Australia.
You might have to enable 'world mode' in the Wireless and Networks settings before it will talk to the SIM. It's been a while since i've run the 'stock' OS.
Just reassuring you the phone is capable of working down under - as mine does.
I am also having this problem and have tried many things to fix it, without luck. Anyone got a solution?
FIX MIN
Flash Verizon DROID 3 OTA 5.6.890 to phone_psouza4
GOOGLE THIS FILE AND DOWNLOAD. FIX MIN
JUST FASTBOOT
EXTRACT THE FOLDER
OPEN IT
ONE CLIC
LET ME KNOW
arnaldito said:
Flash Verizon DROID 3 OTA 5.6.890 to phone_psouza4
GOOGLE THIS FILE AND DOWNLOAD. FIX MIN
JUST FASTBOOT
EXTRACT THE FOLDER
OPEN IT
ONE CLIC
LET ME KNOW
Click to expand...
Click to collapse
Tried this and maaaany other potential fixes, with no luck :crying:
dinosaur swagg said:
I am also having this problem and have tried many things to fix it, without luck. Anyone got a solution?
Click to expand...
Click to collapse
I figured this out after having the problem several times the radio imei number is wrong even if you have did the *228 and ##PROGRAM with the correct info. I found that when you check the System IMEI with a 3rd party software it will shot something like 3112000xxxxxxxxxx or something of the sort. MTKdroidTools has the ability to let you correct this issue.
A couple days ago I followed the instructions to unlock my D3 to use on T-Mobile. Everything went perfect and I was using it with T-Mo. I just decided to flash to a custom rom (MavRom 4.5) and now I'm getting a general error of my SIM not being detected. I do not think there is anything wrong with my SIM since I was just using it in the phone this morning. I have tinkered with the build.prop and tried using a custom one too. It was like the phone was trying to work with my SIM but eventually failed or does so immediately. I just want to use my phone. I really don't know what's going on. I'm honestly tired of searching too. I'm kind of at a loss. Please someone help. It'd be much appreciated.
Mmmm... tell me some things:
1- Is your phone unlocked in some way?
2- Do you have tried another ROM? (i think yes)
3- use the base build.prop
4- do you have XT860 or XT862? because MAVRom has 2 versions..
kelz20 said:
A couple days ago I followed the instructions to unlock my D3 to use on T-Mobile. Everything went perfect and I was using it with T-Mo. I just decided to flash to a custom rom (MavRom 4.5) and now I'm getting a general error of my SIM not being detected. I do not think there is anything wrong with my SIM since I was just using it in the phone this morning. I have tinkered with the build.prop and tried using a custom one too. It was like the phone was trying to work with my SIM but eventually failed or does so immediately. I just want to use my phone. I really don't know what's going on. I'm honestly tired of searching too. I'm kind of at a loss. Please someone help. It'd be much appreciated.
Click to expand...
Click to collapse
Try replacing libmoto_ril.so file on /system/lib.
Follows attached. Unzip and place on the folder mentioned above, overwriting the existing one.
This is the only way that I'm able to use custom roms made for XT862. I hava a XT860 running on GSM networks, so this could help.
Probably after that you will need to check if you need to set up the APNs accordingly.
I'd just go back to what was working. There is nothing in Maverick that is worth the hassle of a phone that doesn't work the way that you want.
kelz20 said:
A couple days ago I followed the instructions to unlock my D3 to use on T-Mobile. Everything went perfect and I was using it with T-Mo. I just decided to flash to a custom rom (MavRom 4.5) and now I'm getting a general error of my SIM not being detected. I do not think there is anything wrong with my SIM since I was just using it in the phone this morning. I have tinkered with the build.prop and tried using a custom one too. It was like the phone was trying to work with my SIM but eventually failed or does so immediately. I just want to use my phone. I really don't know what's going on. I'm honestly tired of searching too. I'm kind of at a loss. Please someone help. It'd be much appreciated.
Click to expand...
Click to collapse
Hm, I use Maverick 4.0 without any issues (4.5 is the same thing with overclock scripts, but they cause a battery drain, so I stuck with 4.0). The only issue I have (rarely) is sometimes it'll say invalid sim, but usually it'll still work, just have to reboot to fix that. Long as you have the XT883 radio and proper edited build.prop it *should* work. Please do NOT use any libs for the XT860, you will only make the radio not work at all and potentially cause damage. The XT860 libs were made for a GSM only radio, the XT862 has a dual CDMA/GSM radio, so the libs do not know how to control the radio.
If you require any files or info, let me know. Where I work happens to have refarmed T-Mobile's HSPA to 1900MHz so my D3 can use it. You might have just missed a step somewhere or missed a permission.
Hello to you all
I would like to show all of you 4.3 users the solution "elvisypi" gave me in my private mail and finally i succeed to unlock my device.
So all of us know that sprint or google changed the way HtcOMADM works and we can't use the original system for unlocking our device.
So here is the solution that "elvisypi" gave me :
1. Download the "Stock with goodies 4.3 ROM". Don't flash it wet. (link : http://www.mediafire.com/?9y21d2wlszh6d6c )
2, With an archive viewer like winzip open the ROM.zip and go to /system/app
3. replace 2 apps which I have attached: HtcOMADM_SettingsPlugin_SPCS.apk and HtcOMADM_SPCS.apk. Just drag and drop and replace.
4. Finally flash the ROM.
5. Install the HTCOneSIMUnlockHelper and follow the onscreen instructions.
This system works 100% and this way you can be on 4.3 rom and still have an unlock GSM sprint device.
again , many thanks to "elvisypi" for his great support
sim unlock
Hope it does
downloading....
Would this work with other ROMs like insercoin?
phatmanxxl said:
Would this work with other ROMs like insercoin?
Click to expand...
Click to collapse
You must use a stock rom for this to work
Hey, are you using this with Tmobile or another service?
syedinsane said:
Hey, are you using this with Tmobile or another service?
Click to expand...
Click to collapse
I'm not using t-mobile , I'm not from the US but it should work with any GSM sim after the unlock is done
james341 said:
I'm not using t-mobile , I'm not from the US but it should work with any GSM sim after the unlock is done
Click to expand...
Click to collapse
I've followed your directions, using the ROM you provided (only difference being flashing the root-fix) and I get vDM errors every time I boot and the app says it's unlocked but my Tmobile SIM gets no signal. Is there any other way i can check if my phone's unlocked?
syedinsane said:
I've followed your directions, using the ROM you provided (only difference being flashing the root-fix) and I get vDM errors every time I boot and the app says it's unlocked but my Tmobile SIM gets no signal. Is there any other way i can check if my phone's unlocked?
Click to expand...
Click to collapse
Did you changed the phone in settings to GSM/UMTS?
james341 said:
Did you changed the phone in settings to GSM/UMTS?
Click to expand...
Click to collapse
Yes I have, it says preparing SIM card but I never get any bars. I read in another thread that I need to be on an older radio in order for Tmobile to work. And for that I'll need s-off which I can't. Sigh.
syedinsane said:
Yes I have, it says preparing SIM card but I never get any bars. I read in another thread that I need to be on an older radio in order for Tmobile to work. And for that I'll need s-off which I can't. Sigh.
Click to expand...
Click to collapse
Flash the release radio and let us know, I'm interested in using an At&t card for when I need a good data connection.
[/COLOR]Delete
Sent from my HTCONE using XDA Premium 4 mobile app[/QUOTE]
Sent from my HTCONE using XDA Premium 4 mobile app
It didnt work for me?
I did exactly what you said an When the phone starts up it says unfortunately ui has stop working an it keeps popping up an i cant do anything with my phone
Thank you for this already pressed the Thank you button also
i was getting annoyed that i couldnt find the files before i found this thread
HTC ONE
I did everthing s-off....flashed to the old radio baseband....tried everything still havent got any signal....who know what a problem?
The only thing is that I've flashed my sprint htc one to the Straight talk. Could it cause a problem?
I am also trying to unlock for T-Mobile. Running into the same issues as others. I was reading a thread where someone was apparently using it on T-Mobile, and PMed them on how exactly they did it but never got a response.
Would love to hear if anyone has it working on T-Mobile
This works. :victory:
Only need to extract, modify and zip again.
Flash with TWRP.
And everything is working normally, no need to reinstall or root, or whatever.
The only problem is that every time I turn on the phone, I get the error message VDM, but it disappears instantly, without stopping or forcing any application.
I live outside the U.S., and continues to operate all perfect with SIMUnlockerHelper. :fingers-crossed:
My device: Sprint Htc one = Unlockboot, TWRP, SIMUnlocker Helper, Root, and the rom on the top of the post. (benny's 4.3 LOL)
it actually works, but if you're using a sense rom I think you only need to download the apps in the op and replacing in system/app
I did this with insertcoin 6.0-4, the unlock helper app didn't recognize the rom, but with the terminal emulator method it worked just fine, tried with a sim and all fine ... then put again the original apks and you don't have to deal with any error popups
Interesting. I was under the impression that our version of this device did not support domestic (only international) GSM bands, hardware wise.
Is this version of sim unlocking different than what you would get if you asked Sprint? (they do allow you to unlock it if you meet certain criteria, like good account standing)
cbburtraw said:
Interesting. I was under the impression that our version of this device did not support domestic (only international) GSM bands, hardware wise.
Is this version of sim unlocking different than what you would get if you asked Sprint? (they do allow you to unlock it if you meet certain criteria, like good account standing)
Click to expand...
Click to collapse
it supports the bands, but all the radios except the original one block domestic gsm carriers. if you still unlock and use that radio, it'll work.
Not working
I tried everything mentioned above, ( Unlock bootloader, S-OFF, Root) also changed the 2 apps in the system for the 4.3 ROM Stock rooted deodexed and then used the SIM unlock helper.
Then Got the same result : No GSM signal, and the SPRINT logo still on the top when I make a call, the same answer comes: " Error number 16 script 3."
I'm using Straight Talk Sim by ATT.
Okay, I just got through doing this myself and it seemed that nowhere was this all said at once, or at all. So I thought I'd whip up a quick tutorial concerning how to Domestic Unlock the Samsung Galaxy S4 on any of the newer bootloaders/firmwares/modems. (Knox-enabled)
I did this on both a 4.4.1 galaxy and a 4.3 galaxy- one one NAE and one on MK2
First, for anything to work your modem must be an older one, like version MDL. Download the file SPH-L720_MDC_Modem.exe which is a one-click
Odin .exe that will flash ONLY your modem to MDL.
Steps- put into download mode by taking the battery out and putting it back in. Hold the volume down button, the home buttone and then press the power button. When it vibrates, let go. Press volume up.
Run the SPH-L720_MDC_Modem.exe odin one-click installer.
Connect the usb to computer from phone
when com[24] or whatever shows up, press start.
Now, for the domestic lock to work you first need to do the international unlock @ http://forum.xda-developers.com/showthread.php?t=2415587
It's real easy and explained well at the link above, but I'll run through it quickly anyways.
Download the s4unlocker installer from the post linked above.
Put your phone into diag mode by dialing ##3424#. Press Qualcom button and select the bottom selection.
connect (if it wasn't already) usb from phone to PC
You already installed the proper samsung drivers, right? If not, you'd better do that now.
Okay, now run the s4unlocker and press the scan and unlock button, then wait for the phone to reboot.
Now for the Domestic Unlock part.
Follow the directions at http://forum.xda-developers.com/showthread.php?t=2530610
I'll run through it real quick, too because there were a few things I wanted to mention.
dial *#0011# (or #*0011#, I can't remember)
when it comes up "No service", press the menu key on the bottom left of your phone. This brings up a menu (wow!), on which you should press "back"
Now press the menu key again and in the menu select "key input" A box will open up asking for you to type in something- enter a "1" and then press the enter key BEFORE hitting the OK button. Mine would not work unless I did this.
Now wait, sometimes it takes a good couple of seconds to give you the menu. Follow the rest of the directions from the above link, setting all the settings to what is stated. EXCEPT where he says to set all the preferences to WCDMA ALL, GSM ALL and LTE ALL. When I selected one, however, an asterisk appeared after my selection leading me to believe that you can only select one of these and so I set mine to GSM ALL and left the others alone. This worked for me, so I thought I'd mention it.
Now that you've manually rebooted after following the directions, you still have to edit your build prop to allow you to edit the apn settings. To edit your build.prop you must be rooted so root with CF auto-root http://autoroot.chainfire.eu/ download the proper one for the galaxy s4.
It's just an odin flash, so enter download mode
load up odin 3.x
hit the pda button and select the cf auto root tar
hit start.
After rooting I found that one time I had to do some of the service mode settings again and one time I did not, so I mention it here even though I think I had to because of some other error I had made at the time.
Go to play store and download build.prop editor and APN settings Shortcut
Load the build.prop editor and add these two lines to the end of the file
ril.sales_code=LOL
ro.csc.sales_code=LOL
Now reboot manually
add the apn settings widgit to the main screen and open it
click on menu and add an apn
Enter the apn settings for your carrier here. They're all different,(the carriers) but you can find them(the apn settings) easily with google, since they (carriers) all post their apn settings on their webpages.
Don't forget to save the apn settings.
Now select it.
Now reboot, since it couldn't hurt, right?
If you've done everything right you should now have an domestic and international unlocked Sprint galaxy s4. Enjoy.
I suppose you could now reflash the new modem back onto the phone, but I don't have firsthand knowledge whether this works or not- I've only read that others have said that it works. Remember, ONLY FLASH THE MODEM, the rest isn't necessary and will probably knox you all up
All I did was list these things- credit goes to all those who were linked in the above post. Thanks for all you do.
On stock 4.3 and higher you can go into settings and change your APN, so there's no reason to root and mess around with build.prop editor.
Every time i try this i cant get my wifi back up when i flash back to the nae modem. If i could get pass that then I'll definetly be do that.
can the modem be downgraded
mine came with mk2
leoiden said:
can the modem be downgraded
mine came with mk2
Click to expand...
Click to collapse
Yes, did like that on my L720 4.4.2 after unlocked with T-mobile i flashed 4.4.2 samsung s4 T-mobile odexed rom now the phone work like t-mobile s4 and full 4g signal, except the LTE data.
leoiden said:
can the modem be downgraded
mine came with mk2
Click to expand...
Click to collapse
tomy1986.nt said:
Yes, did like that on my L720 4.4.2 after unlocked with T-mobile i flashed 4.4.2 samsung s4 T-mobile odexed rom now the phone work like t-mobile s4 and full 4g signal, except the LTE data.
Click to expand...
Click to collapse
I have read that the modem itself cannot be downgraded. You can run older android versions and such on the newer modems, but the modem itself cannot be rolled back. I believe it has been like that since MJA.
You can downgrade modem, but can not downgrade bootloader (aboot)
Sent from my Phone using Tapatalk
I completed both the international & domestic unlock. I believe I was successful in each. I have a T-Mo sim card inserted but am not getting a mobile data connection. I do have 2 bars of service though. So I have gotten past the red X on the bars.
I am on 4.4.2 with the MDC modem. I did not do the build.prop stuff, instead opted to just access the APN's from the default menu.
A few things in my menu were different than the OP (probably because of 4.4) such as:
I dont have any roaming menu options
I dont have WCDMA.. just CDMA and LTE/CDMA. I currently have it set to LTE/CDMA
In my APN edit info there was not a place to put in MMS protocol: WAP 2.0
Also under About Device "my phone number" is wrong.
Am I missing something to get this t-mo working?
goblue30093 said:
I completed both the international & domestic unlock. I believe I was successful in each. I have a T-Mo sim card inserted but am not getting a mobile data connection. I do have 2 bars of service though. So I have gotten past the red X on the bars.
I am on 4.4.2 with the MDC modem. I did not do the build.prop stuff, instead opted to just access the APN's from the default menu.
A few things in my menu were different than the OP (probably because of 4.4) such as:
I dont have any roaming menu options
I dont have WCDMA.. just CDMA and LTE/CDMA. I currently have it set to LTE/CDMA
In my APN edit info there was not a place to put in MMS protocol: WAP 2.0
Also under About Device "my phone number" is wrong.
Am I missing something to get this t-mo working?
Click to expand...
Click to collapse
You didn't unlock it. If you were on NAE modem while unlocking then you failed miserably because you're not able to get into the most important part of the unlock...The service menu. If you did indeed downgrade the modem then you're going to need to follow the domestic unlock guide again. If it's showing CDMA/LTE you didn't do it right. It should show WCDMA only and WCDMA only isn't an option you can just select. It gets put there by the service menu.
Sent from my SPH-L720 using xda app-developers app
ecs87 said:
You didn't unlock it. If you were on NAE modem while unlocking then you failed miserably because you're not able to get into the most important part of the unlock...The service menu. If you did indeed downgrade the modem then you're going to need to follow the domestic unlock guide again. If it's showing CDMA/LTE you didn't do it right. It should show WCDMA only and WCDMA only isn't an option you can just select. It gets put there by the service menu.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I said I wasn't on NAE, I am on MDC. I did get into the service menu. I did everything in the process without issues. My service menu did NOT have a WCDMA only option. It had LTE/WCDMA and that's what i chose. I just went to the t-mobile store and they verified my APN settings were correct. I am unsure of what to do at this point other than just start all over and do it again.
Anyone else?
goblue30093 said:
I said I wasn't on NAE, I am on MDC. I did get into the service menu. I did everything in the process without issues. My service menu did NOT have a WCDMA only option. It had LTE/WCDMA and that's what i chose. I just went to the t-mobile store and they verified my APN settings were correct. I am unsure of what to do at this point other than just start all over and do it again.
Anyone else?
Click to expand...
Click to collapse
I apologize. Long work day. Follow the guide. When it comes to where it says select LTE, GSM, and WCDMA all, ONLY select WCDMA all. At no point should you see your Sprint phone number in about phone. Also you should see IMEISV in about phone as well if you've successfully unlocked it. It'll help if you posted the steps you've gone through. Otherwise were just shooting in the dark.
Sent from my SPH-L720 using xda app-developers app
tmobile rom
jaywaka2713 said:
I have read that the modem itself cannot be downgraded. You can run older android versions and such on the newer modems, but the modem itself cannot be rolled back. I believe it has been like that since MJA.
Click to expand...
Click to collapse
hi can you tell me where I can download 4.4.2 samsung s4 T-mobile odexed rom for l720. thanks.
ecs87 said:
I apologize. Long work day. Follow the guide. When it comes to where it says select LTE, GSM, and WCDMA all, ONLY select WCDMA all. At no point should you see your Sprint phone number in about phone. Also you should see IMEISV in about phone as well if you've successfully unlocked it. It'll help if you posted the steps you've gone through. Otherwise were just shooting in the dark.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Imeisv visible, definitely unlocked as i can make calls texts and use edge data on redpocket mobile (att mvno)
But in phone number I still see my sprint number and I can't get hspa (picking the wcdma all gives me red x no bars, picking gsm all gives me full bars and edge data)
ecs87 said:
I apologize. Long work day. Follow the guide. When it comes to where it says select LTE, GSM, and WCDMA all, ONLY select WCDMA all. At no point should you see your Sprint phone number in about phone. Also you should see IMEISV in about phone as well if you've successfully unlocked it. It'll help if you posted the steps you've gone through. Otherwise were just shooting in the dark.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
From the S5 thread and now here we meet again in a revisit in time. Since I know you own and understand the L720 more than I do, could you please explain to me if this will work on a 4.4.2 NAE rom? I picked up an L720 (bad esn) for $100 and its in pretty great shape. Now I'm looking to unlock it but my experience with Samsung devices are very mild. It came on CM10.2 (4.3.1) and ive slowly caught up with things. So i understand that sadly there is no such thing as downgrading from KK to JB, I was trying to get it stock on JB with no cigar. Elsewhere I found out that you must flash something identical or above. So im planning on flashing an NAE 4.4.2 stock rom (custom recovery flashable) I found in order to attempt to unlock it cause I can't seem to find a 4.4.1 as mentioned in the OP. I flashed the MDC modem and it stuck, so with little knowledge I am assuming that it will stick once I flash this new rom? Correct me if I am going down the wrong path...
EDIT: Great nobody ever mentioned anywhere that the software used on the international unlock is for 64bit only...
Crossvxm said:
From the S5 thread and now here we meet again in a revisit in time. Since I know you own and understand the L720 more than I do, could you please explain to me if this will work on a 4.4.2 NAE rom? I picked up an L720 (bad esn) for $100 and its in pretty great shape. Now I'm looking to unlock it but my experience with Samsung devices are very mild. It came on CM10.2 (4.3.1) and ive slowly caught up with things. So i understand that sadly there is no such thing as downgrading from KK to JB, I was trying to get it stock on JB with no cigar. Elsewhere I found out that you must flash something identical or above. So im planning on flashing an NAE 4.4.2 stock rom (custom recovery flashable) I found in order to attempt to unlock it cause I can't seem to find a 4.4.1 as mentioned in the OP. I flashed the MDC modem and it stuck, so with little knowledge I am assuming that it will stick once I flash this new rom? Correct me if I am going down the wrong path...
EDIT: Great nobody ever mentioned anywhere that the software used on the international unlock is for 64bit only...
Click to expand...
Click to collapse
The software works on 32 bit too. Actually you can even perform the international unlock WITHOUT the tool if you know how to use QPST or DFS. Anyway...
Flash full NAE. Flash MDC modem. International unlock. Domestic unlock. Win.
Sent from my SPH-L720 using XDA Free mobile app
ecs87 said:
The software works on 32 bit too. Actually you can even perform the international unlock WITHOUT the tool if you know how to use QPST or DFS. Anyway...
Flash full NAE. Flash MDC modem. International unlock. Domestic unlock. Win.
Sent from my SPH-L720 using XDA Free mobile app
Click to expand...
Click to collapse
Must be an issue with my PC, nothing new...
And I know a thing or two about QPST. I still have it on my computer from a few days ago from when I was fixing a horribly corrupted IMEI on a G2 a friend of mine bought. I'm assuming I have to use a NAE stock tar with ODIN, because I tried a ROM of it and it lags and stays on black screens for seconds and WiFi doesn't work im sure because of the fact that the modem is older than the rom. Let's see if that works cause ive been trying to flash back to any stock ROM since I got this thing yesterday.
(Almost there...)
NEVER MIND. Got the international part working perfectly by using the Windows Vista partition on my PC. Now reading on, OP mentions that next the domestic unlock must be done, a link is provided there to another thread with domestic unlock instructions. Heres the question. The OP in the other thread mentions to hop onto 4.3 via odin. How can I get to 4.3 to domestic unlock if Odin doesnt let you downgrade?
Crossvxm said:
(Almost there...)
NEVER MIND. Got the international part working perfectly by using the Windows Vista partition on my PC. Now reading on, OP mentions that next the domestic unlock must be done, a link is provided there to another thread with domestic unlock instructions. Heres the question. The OP in the other thread mentions to hop onto 4.3 via odin. How can I get to 4.3 to domestic unlock if Odin doesnt let you downgrade?
Click to expand...
Click to collapse
Read the specifics. You cannot downgrade boot loaders but you CAN downgrade modems.
Unlock just requires MDC or MDL modem.
daniel4653 said:
Read the specifics. You cannot downgrade boot loaders but you CAN downgrade modems.
Unlock just requires MDC or MDL modem.
Click to expand...
Click to collapse
Yeah I remember that part but from what I was understanding, that's for the international. Domestic requires messing with some files and done. I already got the international part by tossing CM10.2 along with the MDC modem because stock Touch wiz would cause lag and reboots and non working wifi I'm assuming because of the mismatched combo. I DO know that obviously we need a TW rom in order to unlock domestic.
EDIT: I finally got the hint and got it to work. But I only get Edge instead of 3G. Does anyone know where I may be able to find that T-Mobile rom made for us? When I Google it I end up on the T-Mobile side.
Crossvxm said:
(Almost there...)
NEVER MIND. Got the international part working perfectly by using the Windows Vista partition on my PC. Now reading on, OP mentions that next the domestic unlock must be done, a link is provided there to another thread with domestic unlock instructions. Heres the question. The OP in the other thread mentions to hop onto 4.3 via odin. How can I get to 4.3 to domestic unlock if Odin doesnt let you downgrade?
Click to expand...
Click to collapse
I downgraded from latest bootloader on 4.4.2 or was it 4.4.4? Down to 4.3 which is the absolute best ROM version for service mode menu. It got me into service mode menu on first try by selecting menu back and input of 1. What I did was first install cf autoroot to root then cwm and used cwm to flash the 4.3 stock deodexed, I only used Odin for flashing modem. Odin gave me an error when flashing modem and phone got stuck in kies mode but i got it to get unstuck by just flashing cf auto root again to make the kies mode error thingy think odin flash has went well. Turns out MDC modem flashed despite odin error.
Anyways. While on 4.3 and MDC modem I noticed no WiFi but I had sound. I followed the international and domestic unlock instructions and WiFi was still broke when I got back to 4.4.2 but I had unlock and sim card working and got bars. I am on aosp 4.4.4 now and the nae modem I finally flashed works well with this ROM but soon I gotta go to touchwhiz 4.4.4. If I go to 4.4.4 touch whiz WiFi and all else will work fine just as they do on slim aosp . 4.4.2 touchwhiz is still not giving me wifi on NAE modem. Update NAE 4.4.2 stock deodexed rooted rom i got from xda android thread did the trick and all works well now. All is perfectly working after i flashed it in cwm.
For aosp lovers. aosp requires additional things to do so aosp dialer can make and receive calls fine. I can call but there are issues until I follow another guide on xda that resolves those issues on aosp ROMs using sprint s4.
http://forum.xda-developers.com/showthread.php?t=2539794
If you see system slow, no wifi, no audio and lockscreen being nearly impossible to unlock, its due to you being on a higher ROM than the modem was meant for.
Sim Unlock Method 4.4.2/5.0.1
Disclaimer: i AM not resposile for anything that happens to your phone in the unlikely event something does happen.
this has only been tested lightly but it should work all-right. this is for the i537 S4A only.
You Need to start out on either NE3 or NH3. Downgrade now if you need to. Just remember when downgrading don't flash bootloader. This needs Odin and root to succede. Now That thats out of the way you need to download some files to deal with later on.
MF1 Odin flashable
regionlockaway go to the second post and download the apk to install on your phone.
this method uses an old method in a new way.
here is the guide
1. install regionlockaway and reboot to download mode
2. Flash modem.bin with odin in download mode
3.reboot to system and use regionlockaway. follow the instructions in the app.
4. profit?
As far as my understanding after you do this you can update your modem without it reverting back to being locked. I am running oc7 modem on a T-Mobile MVNO without issues( if you want aws unlock you are going to have to use this then the appropriate modem for that and not allow for the modem to update when updating to oc7 by modifying the oc7 installer and removing the modem from it)
I am ready... I have been reading for days about sim unlocking on 4.4 and up..I finally coined up $25 for a code but takes up to 5 days, 2 days ago. my next attempts were going to be with my paid copy of CDMA WS. Either way it is just to experiment with and would love to gain the knowledge. I have a couple different carrier sims ready to go. I would love to give it a shot.....
mateo121212 said:
hey guys i have created an easy sim unlock that should work for 4.4.2 and for 5.0.1
for the 5.0.1 sim unlock you have to do it on 4.4.2 and flash a modified partitions file to upgrade to 5.0.1 while keeping sim unlock.
if you guys are interested in it let me know and i will set up a few beta testers for it. i cant say for certain that it works because i dont have a non ATT sim card to test it with.but it should work. it should also allow you to enable aws for those on T-Mobile by following a secondary guide.
let me know and i will start having people beta test. i only need between 1 and 5 testers
Click to expand...
Click to collapse
nrgyitguy said:
I am ready... I have been reading for days about sim unlocking on 4.4 and up..I finally coined up $25 for a code but takes up to 5 days, 2 days ago. my next attempts were going to be with my paid copy of CDMA WS. Either way it is just to experiment with and would love to gain the knowledge. I have a couple different carrier sims ready to go. I would love to give it a shot.....
Click to expand...
Click to collapse
ok ill pm you with a guide once i have it written up.
EDIT: it should be in your inbox
i was able to test a verizon lte sim and it didnt give me any issues. it regestered the number in the status. so i belive it worked. i would like some more testers to get information about it. i need more testers before i feel ok giving out the method.
Been sooo busy!!!! K, thank you for the guide. I haven't been able to try anything except a Verizon Lte sim. It registers the number and the network lock is gone. However I don't believe we will get data service with a Verizon sim as I don't believe the hardware is capable?...I wasnt able to place a call as I got" Emergency calls only", all I did was swap sims, occasionally I have to call Verizon and have them add the new phone to the plan before it will work and I didn't do that yet. Will try a different carrier sim tonight.
mateo121212 said:
i was able to test a verizon lte sim and it didnt give me any issues. it regestered the number in the status. so i belive it worked. i would like some more testers to get information about it. i need more testers before i feel ok giving out the method.
Click to expand...
Click to collapse
nrgyitguy said:
Been sooo busy!!!! K, thank you for the guide. I haven't been able to try anything except a Verizon Lte sim. It registers the number and the network lock is gone. However I don't believe we will get data service with a Verizon sim as I don't believe the hardware is capable?...I wasnt able to place a call as I got" Emergency calls only", all I did was swap sims, occasionally I have to call Verizon and have them add the new phone to the plan before it will work and I didn't do that yet. Will try a different carrier sim tonight.
Click to expand...
Click to collapse
so before you did the guide did it give you issues with the verizon sim? and now it dosent?
It did give me issues before flashing the mf1 and after the flash and region away no nagging about sim unlock code! Havent gone any further yet. I will report back after using a different carrier sim besides verizon that is.....I think it works....
mateo121212 said:
so before you did the guide did it give you issues with the verizon sim? and now it dosent?
Click to expand...
Click to collapse
nrgyitguy said:
It did give me issues before flashing the mf1 and after the flash and region away no nagging about sim unlock code! Havent gone any further yet. I will report back after using a different carrier sim besides verizon that is.....I think it works....
Click to expand...
Click to collapse
sweet thank you for the feedback man. i did the 5.0.1 upgrade method i detailed in the PM after i finished doing the unlock on my phone and it worked the same as what you described (i only had access to vzw lte sim also) so i belive i made the update file correctly also. im not really getting any bites on more testers so if it pans out well for you i will polish up my guide and post it here to have people test it instead of making them PM me.
thanks again for being my beta tester. if we get this working well we can save alot of people alot of money
ps for voice and sms verizon lte sims are useless because they still use CDMA for those features
Finally put in another sim...Put in a Tomb sim and no nagging about unlock code, I got "Sim not provisioned" as it isn't active at the moment. So I'm thinking it worked. Thank you. I was thinking I'd get voice and edge speeds with a Verizon sim in this phone, (utilizing GSM bands), in my area anyway, but maybe I'm mistaken. I'll post again after using another carrier's sim.....
nrgyitguy said:
Finally put in another sim...Put in a Tomb sim and no nagging about unlock code, I got "Sim not provisioned" as it isn't active at the moment. So I'm thinking it worked. Thank you. I was thinking I'd get voice and edge speeds with a Verizon sim in this phone, (utilizing GSM bands), in my area anyway, but maybe I'm mistaken. I'll post again after using another carrier's sim.....
Click to expand...
Click to collapse
thank you for your work. im glad it worked for you. i will be posting the guide up here soon.
In reference to....
starting at post #327 of http://forum.xda-developers.com/gal...7oc6-5-0-1-t3089355/post61347589#post61347589
I did as instructed and according to flashfire at the end of flashing, it said it was successful and it rebooted (so far) to the lollipop boot animation and am awaiting for it to get past the at&t logo screen. Its at least gotten a lot further than all my earlier attempts...I am assuming its taking a little while for its initial setup of OC6....
more later on its success or failure....
well it was a partial success....it flash and booted into OC6 but sim card is not recognized, no baseband.....now installing updated version of flashfire....should i now flash the MF1 modem again via flashfire?
well i went ahead and did just that flashed the mf1 modem via flashfire and all is up and running successfully (FINALLY!!) with root on deodexed rom OC6...
Kudos and thanks goes out to ya!
jaksback said:
starting at post #327 of http://forum.xda-developers.com/gal...7oc6-5-0-1-t3089355/post61347589#post61347589
I did as instructed and according to flashfire at the end of flashing, it said it was successful and it rebooted (so far) to the lollipop boot animation and am awaiting for it to get past the at&t logo screen. Its at least gotten a lot further than all my earlier attempts...I am assuming its taking a little while for its initial setup of OC6....
more later on its success or failure....
well it was a partial success....it flash and booted into OC6 but sim card is not recognized, no baseband.....now installing updated version of flashfire....should i now flash the MF1 modem again via flashfire?
well i went ahead and did just that flashed the mf1 modem via flashfire and all is up and running successfully (FINALLY!!) with root on deodexed rom OC6...
Kudos and thanks goes out to ya!
Click to expand...
Click to collapse
your welcome man. i figured your problem could be fixed with my method. have fun with 5.0.1
partially completed downloads
Never mind. The downloads on dev-host work from my computer but not from tablet or phone.
I stopped THE INSTALLATION of I537_OC6_Stock_Partitions_mod_sim.zip and the phone is not the most part, dead, solutions?
spyke70 said:
I stopped THE INSTALLATION of I537_OC6_Stock_Partitions_mod_sim.zip and the phone is not the most part, dead, solutions?
Click to expand...
Click to collapse
Odin back to Ne3 and start over
so it didnt work. it stop saying it was an unreconizable sim card and region lock said it took. so i dunno it says (phone not aloud MM#6) right when i start up. but it shows i have a new voice mail? only emergency calls
oh ya and it was at&t and i put a family mobile simcard, (runs off t mobile network)
any ideas??
Jsturg1990 said:
so it didnt work. it stop saying it was an unreconizable sim card and region lock said it took. so i dunno it says (phone not aloud MM#6) right when i start up. but it shows i have a new voice mail? only emergency calls
oh ya and it was at&t and i put a family mobile simcard, (runs off t mobile network)
any ideas??
Click to expand...
Click to collapse
odin ne3
flash mf1 modem with flash fire
make sure you are rooted and have busybox
use region lock away. try with att sim in phone.
Trying to do this for my s4a but flashfire is being uncooperative, it just crashes any chance it gets. Any other flash apps this will work with?
Edit: do I need safestrap for FlashFire?
Edit2: Fixed the issue with flashfire, If anyone runs into this issue you need to flash stock NE3, and re-root.
Rest of tutorial went perfectly. Cannot test unlock status atm, but no errors.
Thanks Matteo, you're a top lad.
Will this same method work with a deodexed OC7 ROM? I only ask because of the I537_OC6_Stock_Partitions_mod_sim.zip - not sure if this still works the same for OC7. Just to clarify, do you know if region lockaway is necessary to get T-Mobile AWS/HSPA bands? I've got a working cell and LTE connection without doing any of this, so I really only needed to do what's necessary to get those bands (which I think the old modem will help enable).
Thanks for the assistance!
sunilbeforezod said:
Will this same method work with a deodexed OC7 ROM? I only ask because of the I537_OC6_Stock_Partitions_mod_sim.zip - not sure if this still works the same for OC7. Just to clarify, do you know if region lockaway is necessary to get T-Mobile AWS/HSPA bands? I've got a working cell and LTE connection without doing any of this, so I really only needed to do what's necessary to get those bands (which I think the old modem will help enable).
Thanks for the assistance!
Click to expand...
Click to collapse
edit to the edit:
go back to NE3 with odin.
then flash mf1 modem
then try this
[GUIDE] AWS Unlock for i537 I537UCUBML2 (4.3)
read the posts to make it work
also check out this post if you have issues with getting qpst to work. dont follow the whole post just qpst part http://forum.xda-developers.com/showpost.php?p=56023258&postcount=68
then follow the guide i posted in my last edit to keep the aws unlocked modem while on 0C7
edit:
you can use the oc7 deodexed rom. you just have to remove the modem from the rom file useing winrar or 7zip. also you have to remove it from the updater script useing a text editor. drag it out of winrar edit it and then drag it back into winrar. that way if you flash in this order you will be fine
partitions mod file
oc7 deodexed rom.
that way you keep the modem
from when you installed and unlocked mf1 modem on 4.4.2