yashsingh1/xdaforums huggingface dataset:
[Moto X General] ejlmd:
code:

fastboot oem config carrier T-MOB010

This fixed the outgoing SMS issue, lack of signal bars and signal strength measurements. Also I now have H+ data icon when WiFi turned off. In "Phone Status" the carrier is now listed as T-Mobile, and no more roaming indicator.

Thanks to leonardoafa, the OP of the CarbonROM thread, who answered this for me http://xdaforums.com/showpost.php?p=54467172&postcount=44. I can confirm it works for T-Mobile USA.

In terms of other GSM carriers, I found this listing http://xdaforums.com/showthread.php?t=2445289 from this thread http://htc-one.wonderhowto.com/how-t...rrier-0151867/.
[Moto X General] bean1975:
I emailed you saying "my moto x is in the post when it arrives i am sure in with say $20". That still didn't change :) Ask Pitney Bowes / Canada Post not me when the thing gets here :)
[Moto X General] samwathegreat:
This is JUST AWESOME. Linked in POST # 2, and gave you and leonardoafa appropriate credit. Thanks so much!

[MENTION=767282]cellzealot[/MENTION] [MENTION=5960203]fastover[/MENTION] [MENTION=5966395]martinz_a[/MENTION] [MENTION=5966368]anasananass[/MENTION]

Guys, see the quoted post!!! This should fix the issues you all have been experiencing - and without even having to flash a different ROM!

No worries. If I saw that message, I somehow overlooked it...and I still can't find it after having looked just now. Maybe you didn't include your XDA name, or maybe I misplaced it? Regardless, not trying to rush you. As stated in that post to the pledgers, it was an attempt to let everyone know the GOAL has been accomplished....and good thing because many members (including shantnu as he has posted above) had either not been here to even see the project was completed, or had more-or-less given up. Now they will at least get notified that the SIM-CRACK is a success!

Thanks! And again, no rush. I understand how the U.S. Post works...lol, and I imagine Canada Post isn't any different ;)
[Moto X General] fastover:
xt1056

No im not haveing the signal issues everything works well with no problems and i am on the simple mobile network i have flashed the tmobile,att,and a few other roms to this model and can tell you you need to go back to stock sprint 4.2 rom other wise you will have problems another note on that after flashing the xt1053 rom could not reflash the gpt.bin file as that is a partition file and for what ever reson wont flash back remove that file from sprints rom and flash the rest with rsd lite and yes the phone was active on sprint at one time but when the new sim you are useing weather att tmobile or other when unlocked and running will auto prl by defalt
[Moto X General] samwathegreat:
The RED above is a known issue. You are never supposed to "downgrade". The issue here is that you flashed a 4.4.3 rom to your phone, but the SPRINT ROM is only at 4.4.2. This could be a BIG issue for you.

I want to make sure no one else does this. I did warn to NOT do this in my previous posts....

Anyways, for YOU, you NOW need to take great care to NOT accept the Sprint OTA to 4.4.3 -- it could brick your device (you are lucky you didn't brick already). This is why we have all the warnings against downgrading. Instead (to be safe) you need to wait until the FULL 4.4.3 Sprint SBF is released for your carrier (NOT THE OTA). Once the FULL SBF is released, you can safely flash the entire SBF to upgrade to 4.4.3. Until then, REFUSE the OTA update, and STAY on 4.4.2. This is a safety thing...I don't want anyone to end up with a brick. Some may disagree with me on this and suggest that you CAN accept the OTA, but if you want to be safe, you'll follow my advice.

And to anyone else who reads this: IT ONLY APPLIES TO anyone who has flashed another carrier's --STOCK-- ROM on an android version ABOVE 4.4.2. If you didn't do this, you CAN safely accept the OTA to 4.4.3 or above (once released).

And finally, thanks for all your help / effort / testing. I'm not sure why it works for you without having to do the "fastboot oem config carrier XXX" command listed a few posts above...but at least we seem to have found the solution for everyone else now. :good:

(On a completely un-related note): THANKS [MENTION=1402017]shantnu[/MENTION] -- you are very generous to double your pledge! I really appreciate that you respect all the work I've put into this. Enjoy your XT1056 on GSM!!!
[Moto X General] fastover:
unlocking

i agree to everyone don't do like i did took many hours to recover it but for the best it works great and don't get the ota stay on 4.2 good work again and thank you
[Moto X General] kiory01:
help

Hi there. when attempt FLASH ONLY I GET THIS. AND NOT GET UNLOCK. sorry for my bad English : (Writing NV-items from a file:

Unsuccessfully written NV-items:

00000 (0x0000) - Access denied

00001 (0x0001) - Read only item

00005 (0x0005) - Command failed

00018 (0x0012) - Command failed

00031 (0x001F) - Command failed

00032 (0x0020) - Read only item

00033 (0x0021) - Read only item

00034 (0x0022) - Command failed

00035 (0x0023) - Command failed

00036 (0x0024) - Command failed

00037 (0x0025) - Read only item

00048 (0x0030) - Command failed

00049 (0x0031) - Command failed

00050 (0x0032) - Command failed

00176 (0x00B0) - Read only item

00177 (0x00B1) - Read only item

00178 (0x00B2) - Command failed

00209 (0x00D1) - Read only item

00212 (0x00D4) - Command failed

00215 (0x00D7) - Command failed

00258 (0x0102) - Command failed

00259 (0x0103) - Command failed

00262 (0x0106) - Read only item

00263 (0x0107) - Read only item

00264 (0x0108) - Read only item

00265 (0x0109) - Read only item

00266 (0x010A) - Read only item

00550 (0x0226) - Access denied

01943 (0x0797) - Access denied

05597 (0x15DD) - Read only item

05598 (0x15DE) - Read only item

Done.
[Moto X General] samwathegreat:
Hmm... I have NO IDEA what you are doing here.

Please read POST # 2 and follow the instructions and PICTURES step-by-step. You shouldn't be writing ANY of those NVITEMS you are showing. You will be lucky if you didn't BRICK your phone...... Are you using the CORRECT files I posted in POST # 2?

My method doesn't attempt to write ANY of those NVITEMS -- you are doing something VERY wrong.

Please re-read everything, and start over.....CAREFULLY. You don't want to brick!!!
[Moto X General] cellzealot:
Just to clarify, I don't have this phone and have only been helping someone else go through all these steps.

He is still having no luck with his T -Mobile SIMs and has run the oem carrier commands above.

We are leaning towards a SIM incompatibility at this point, since it works fine with an ATT SIM.

We don't understand the nature of the problem are trying to figure out why it won't register on T-Mobile despite reading the SIM properly.

As we find out more I will post any relevant information.
[Moto X General] lazy_ninja:
1

Hey

Does this work with BAD ESN Moto X? I live in Russia btw
[Moto X General] Vekhez:
If I am correct a BAD ESN phone means it cannot be activated on it's intended CDMA carrier, but it should work fine on GSM carriers.
[Moto X General] ezeuba:
OK. Got my unlock code for one of my RW MOTO X and it worked. I've flashed stock Sprint 4.4.2 with RSD Lite and all went well. Flashed bootlogo to remove unlocked bootloader warning, ok. Now each time I reboot, I am faced with the activation prompt. I have to cancel before I can get to home screen. Any help?

Thanks.
[Moto X General] ecs87:
As far as I know, the CDMA blacklist also carries over to GSM.
[Moto X General] samwathegreat:
Guys: we don't discuss "bad esn" devices here on XDA. If you want to know if it works --- try it and find out. No more asking about that topic, please.

It's probably because the IMSI, NAM, MIN, MDN, etc. are all unprogrammed. Since you are quite familiar with CDMA WS and the like, you can probably copy some bogus values into all of these fields (maybe the MIP fields as well), AND a CDMA PRL, and it will probably quit prompting you. Once the fields are populated, my guess is it will quit asking you....and since you will be using it on GSM, it doesn't matter what is in those CDMA fields anyways. You may need to set "NV ONLY", program all the fields, then after you confirm activation is bypassed, change back to "RUIM Only".

Good Luck -- let me know if it works.
[Moto X General] ezeuba:
Done that even before posting here. Still same thing. People... Please... Help...
[Moto X General] iBowToAndroid:
Depends on why it's bad.

Nonpayment = it'll still work on GSM.

Lost/stolen = it won't work on US GSM, international is fine

An easier way is to delete or rename any system apks with Sprint in the title - one of them is responsible for HFA. SprintDM possibly, though every phone is different and I don't have one in front of me to check
[Moto X General] samwathegreat:
[MENTION=2026715]ezeuba[/MENTION] : The above suggestion is a good one. It has worked on nearly all past Sprint devices for activation-bypass.

EDIT: [MENTION=2026715]ezeuba[/MENTION] : All the relevant sprint APKs appear to start with "OMADM" (which stands for Open Mobile Alliance Device Management). I sugget deleting all those APKs and trying again. If anything gets messed up, you can use RSD Lite to get back to 100% stock.....and if you edit the XML file in the SBF, and remove the two commands "erase modemst1, erase modemst2", you shouldn't have to reapply the SIM-CRACK.
[Moto X General] ezeuba:
I would have preferred not to root this phone, but since this is the only way to disable the activation screen...
[Moto X General] samwathegreat:
Un-root it afterwards. Then if you subsequently "Factory Reset" the phone, it will STILL not have the OMADM apk's since you are deleting them from /system. :)

EDIT: just be sure to flash stock recovery back AFTER un-rooting it. Keep in mind you might (PROBABLY) won't be able to accept any future OTAs after this. If the phone had been activated previously none of this should have been an issue...

This is much more involved....but you could also make an image of system.img after you confirm activation is bypassed, and flash THAT system.img on the other phone. You won't have to go through all this again on the 2nd RW phone...
[Moto X General] ezeuba:
Pray, do tell, how would I go about extracting the system.img from the bypassed phone? I know if I can do that, I can also use 7zip to send it back to the sbf zip and it will be the default stock.
[Moto X General] samwathegreat:
AFAIK, it requires BusyBox to be installed (AND ROOT)....

then, from an ADB SHELL, you *should* be able to:

dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/NEWsystem.img

Let me know if you have success...

And you are correct! If you are able to do this, you can re-package the SBF with the new image. Keep in mind that you will ONLY be able to flash this to a phone with an unlocked bootloader...

And ALSO, since busybox requires ROOT, you will still need to uninstall busybox, and UN-ROOT after flashing the new system.img...

Make sense?
[Moto X General] ezeuba:
If I can do this and get the sbf repackaged, then i can just use it to return to stock and re-crack SIM... I'll post how it goes...
[Moto X General] samwathegreat:
Delete the lines that include "erase modemst1" and "erase modemst2" from the XML file in the SBF.....then you won't **NEED** to RE-CRACK the SIM-LOCK...

EDIT: [MENTION=2026715]ezeuba[/MENTION] : if you are planning to use RSD Lite, you will ALSO have to calculate the MD5 of the NEW system.img, and replace the MD5 of the OLD system.img in the XML file. See the attached screenshot....

Regardless, the new system.img will be ROOTED and have busybox installed. So assuming you don't want root, after "returning to stock" with the new image, you will STILL need to uninstall busybox, and UN-ROOT.
[Moto X General] ecs87:
Is it the stupid HFA Sprint nag that he's talking about? If so, you might be able to apply a fix [MENTION=1130160]AlpineMan[/MENTION] has come up with. Connect the phone to DFS, send the SPC and 16 digit password, then populate the MDN and MIN fields with something other than 000000xxxx AND fill in profile 1's username with something other than MEID@hcm.sprintpcs.com (make something up like stupidhfa@sprintpcs.com). Reboot and it should go away. On many Samsung devices this is the norm (I understand that this thread isn't about Samsung devices but I'm hoping that it's similar since it's Sprint's particular activation application).

ROOT NOT NEEDED.
[Moto X General] samwathegreat:
He already tried that....a few posts back... (bottom of page 14)

EDIT: Maybe not! [MENTION=2026715]ezeuba[/MENTION] : did you actually change the profile 1 username as well (where the MEID goes)? Of course this requires MIP settings to be unlocked, but my method does this already! Try [MENTION=4959296]ecs87[/MENTION] 's suggestion before you go through all the work rooting and removing APKs, etc.

And post back if successful...
[Moto X General] ezeuba:
Done this but can't find the system image file...
[Moto X General] samwathegreat:
If it was successful, it should be in the root of the SD Card. You might have to use root explorer to change the permissions for you to be able to see it when connected to your PC...dunno.

Did you see the last POST? Another user suggested a MUCH easier way of getting around the activation...if it works...
[Moto X General] ezeuba:
Done. The extraction of the system image file was successful. I changed the MD5 values accordingly, copied the modified files (I even went a step further and replaced the logo.bin with the modified one that removes the BL unlock warning), and all went well with the flashing. The HFA screen is gone. I have also uninstalled busybox and done a full unroot. All is well. Thanks to samwathegreat and others for all the guidance.

Thanks again.

NB By the way, if anyone should have any need of the file, it's online somewhere and I can share the link.
[Moto X General] ecs87:
So I'm assuming you didn't try the DFS method? Might've been easier and less time intensive (for future reference).
[Moto X General] Rayz321:
Hi, just a quick update on my progress with my Moto X.

After unlocking with your method the sim unlocked successful (no more incorrect sim notification).

I was using an unactivated H20 (ATT) sim and it would pickup the network but couldn't register to them (hence no bars).

So I took my phone to a MetroPCS (T-mobile) and had them use a live nano sim to try to get it working.

First, I was really excited as when they put in the new sim and rebooted I got 4 full bars.

However, after much tinkering and trying to call (to activate over the phone) we realized it was just getting sprint's message not the Metro activation message.

After I left I put my H20 sim in and went to the setting and realized that somehow it was switched back to CMDA mode and that's the only reason I was getting bars.

So no luck so far with getting my Moto X working.
[Moto X General] ecs87:
It shouldn't switch back to CDMA if it picks up GSM fast enough. Have you tried forcing it to GSM, registering on the network and making the call? After that it shouldn't switch back to CDMA so easily (or at least it shouldn't). I'm not that well versed in GSM so...I may be completely off (I've been on CDMA my whole life) but I have had limited experience with GSM on customers' phones.
[Moto X General] Rayz321:
Yeah I switched it back to GSM manually but still couldn't register on the network even though it detects the network and has the proper APNs.
[Moto X General] samwathegreat:
Well done!! This might be useful to others who have devices that were never activated....although (if it works), [MENTION=4959296]ecs87[/MENTION] 's suggested method IS superior simply because it doesn't affect your ability to accept future OTAs (like 4.4.4), whereas your method is almost guaranteed to prevent the phone from successfully updating to future android versions. Thanks for the offer to share the link! PM it to me, please -- just so I can store a copy on my personal server.

A few thoughts...first, re-read the relevant NVITEMS and make sure they match what I've said they should...

( [MENTION=4959296]ecs87[/MENTION] is on to something here - you shouldn't have switched back to CDMA if you had flashed the "nv-ruim-only" file...)

Second, Check post # 2 for the solution about using fastboot to set your config carrier (if you haven't already)

Third, you might try re-flashing the entire stock sprint SBF and starting all over...

Please try and advise :)
[Moto X General] ecs87:
Fourth...check your imei on checkesnfree.com!
[Moto X General] Rayz321:
Okay, here's the read from all 3 of those NVITEMS http://pastebin.com/2mSjNk1n

They do match (unless I'm missing something)

Looking at the fastboot solution, I can't seem to find a CID for the H2O carrier. I've tried searching a few places but nothing seems to come up.

Maybe I would just use the "ATT CWS__001" CID since H2O uses ATT?

One quick observation though.

When I put the H20 Sim it finds the H20 network.

When I put a sprint sim (I tested with 2 different sims) in it detects the AT&T & T-Mobile networks.

When there is no sim inserted it also detects AT&T and T-mobile.

All of these observations are with reboots after each sim insert.

I'm with online support for H2O now to see if they have any ideas.
[Moto X General] ezeuba:
The DFS method did not work. In fact I was baffled that I had to go through all this just to remove activation screen, never happened before. The MOTO X I'm currently using never had this issue so I guess it may be because this one was never activated on RW before I unlocked the BL and flashed the Sprint sbf on it. The 2 RW phones are still BNIB, so this may be the reason. Back to the main issue. The DFS method did not work. I even had to populate the phone with my own working parameters from the phone I'm using currently, yet the activation screen always came up. The only way was to rename Sprint OMADM2 apk file. Funny enough, the same file is still around on the one I'm using currently and there was no activation screen, although I suspect it may have been activated by the previous owner before selling on ebay. Long story short, the phone is working now, thanks to the modification, and the modified sbf is working well incase anyone should need it. Thanks again.
[Moto X General] samwathegreat:
LOL yeah... hold up on the H2O conversation....you ARE missing something....

FIRST: 855 should be 00, NOT 01 < This NVITEM is the the RUIM-only item, and it explains EXACTLY why your phone is switching back to CDMA

Second, you didn't even show me what you have for NVITEM 8322 !!!

8322 --Is the DOMESTIC-unlock solution--

You need to do this over.... go slowly so you don't miss anything.
[Moto X General] Rayz321:
[MENTION=2509024]samwathegreat[/MENTION] major face palm right there.... I flashed all the files before you posted the domestic unlock so that's why it wasn't working.

It seems to be working great right now, I'll activate my sim tomorrow or the next day to check data and such.

Thank you so much! This is really great and I appreciate your work a whole lot.

I'll PM you regarding a donation :)
[Moto X General] dmonleo:
Great thread!!!!
[Moto X General] Yedite:
Thanks bro

Thank you my friend. You are my hero.

I followed all the steps and it's working smooth.

Cheers! :o
[Moto X General] ecs87:
Donated $25. In sure I'll be using this at one point or another.
[Moto X General] kiory01:
hi

you need root for this?
[Moto X General] samwathegreat:
No. Not if its an XT1056. The instructions are extremely detailed. Please make sure you understand completely (read the first 3 posts), then if you get stuck, we may be able to help you.
[Moto X General] kiory01:
I do exactly. what the post but when I write the NV unlock. just says access denied.
[Moto X General] samwathegreat:
Then I would guess that you didn't use the SPC utility to get --YOUR-- correct SPC and enter it as shown on the pictures. Tell me you aren't entering "12345" as shown in the EXAMPLE pic....
[Moto X General] kiory01:
and that this is correct. NV says read the spc correct your Cell unlocked. but .. I'm still locked. sorry for my bad English I am from DOMINICAN REPUBLIC.
[Moto X General] samwathegreat:
Do THIS:

Now, follow these instructions:

1. Click "READ" --AT THE TOP--

2. Make sure it says: "SPC is Correct. Phone Unlocked."

3. Click the "Write" button, and find the "nv-unlock.txt" file - make sure it confirms success

4. Click the "Write" button, and find the "nv-unlock2.txt" file - make sure this confirms success

5. Click the "Write" button, and find the "unlock-domestic.txt" file - make sure this also confirms success

6. Click the "Write" button, and find the "nv-ruim-only.txt" fine - and make sure it confirms success as well

7. Last, click MODE, then RESET

Then send me a

screenshot

of whatever error you get. Also tell me which file(s) gives you the ERROR.

Also, how about hitting the "THANKS" button on all my posts since you are:

1. Using my method

and

2. Asking me for help....

I don't get why people aren't doing this...
[Moto X General] ecs87:
If it is still giving him trouble he might try sending the Sprint 16 character password in addition to the SPC.

I also totally don't get why people can't hit the thanks button either. It's not difficult...and much less pricey than a donation (which everyone who's using this method should do!!!)
[Moto X General] Vivjen:
Which FW is better? On 4.4.2 I have problem with not working home button. Anybody have same issue? Returning on 4.2.2 now
[Moto X General] samwathegreat:
NO!!! Don't downgrade you can end up with a brick!!!

Just reload 4.4.2. That is not normal.
[Moto X General] Vivjen:
Thanks for care, but I kept bootloader from 4.2.2 (30.71) within flashing 4.4.2.

Update: On 4.2.2 I have permanent bootloop

(modems was not erased in all cases)

Update: possible reason is too long cable not tested prior flashing at all. I'll try to use tested one
[Moto X General] samwathegreat:
Having a mismatched bootloader and/or partition table might be causing your issues. It is my best guess. 4.4.2 has no issues for anybody else and is recommended.

I suggest full SBF to stock 4.4.2 including BL and gpt.bin

Good to see you! It's been a while... Haven't heard from you since I found the solution.
[Moto X General] Vivjen:
Glad to see you too. It's nice that you have solved the not simple task. I'll be happy to help again. I'll try to flash with BL 4.4.2 and will let you know. I have never had such issues within downgrading (without BL flashing) earlier.

P.S. Which exact apk should be removed on never registered phones? Please mention exact folder.
[Moto X General] samwathegreat:
I will PM you a link to a firmware already modified!
[Moto X General] kiory01:
gracias

thanks, thanks, thanks. Now if I run the problem was to download files were wrong ... and everything works usd 5 for you: Laugh:: Laugh:
[Xposed Framework Modules] vikasb32:
Hello firends this is my first xposed module and i am new to xposed coding and still learn xposed framwork.

XToast contain small tweak for toast nofication in android.

features list:

add app icon to toast notification

change icon size display in toast notification

add app title name to toast notification.

select different toast style jellybean,kitkat,gingerbread,holo light,kitkat light

change toast background color

select toast duration:sort and long.

change toast background transparency

select where toast notification appear on the screen.

change toast font color.

change app tittle toast font color.

xposed repository:-http://repo.xposed.info/module/com.vikas.toaststyler

credit

MohammadAG
[Xposed Framework Modules] killoid:
is it possible to add gingerbnread support?
[Xposed Framework Modules] Walter.White:
Nice work. Please add it to xposed repo :)
[Xposed Framework Modules] godlesplay:
[MENTION=4075919]vikasb32[/MENTION] fix Ginerbread to Gingerbread http://i.imgur.com/hrs2KAv.png
[Xposed Framework Modules] vikasb32:
sorry my English too good i will correct that mistake.
[Xposed Framework Modules] vikasb32:
xposed repository link added.
[Xposed Framework Modules] vikasb32:
can you test this build in gingerbread.if it fc plz provide logcat.

Xtoast gingerbread