Related
I just ordered a recertified Verizon 3G Xoom, and I didn't think about the implications of it being a Verizon device. This is NOT upgraded to 4G LTE -- will the "Stingray" builds of the various ROMS still work? Is there any way to apply WIFI-only ROMS (including stock) if I don't care about the 3G working? Given the age of the device I really want to get Jelly Bean on it.
I will need to cancel this order ASAP if the answers to these questions turn out to be "no"...
Same question from me.
Can we install the WiFi only version of ROMs (CM9 in particular) onto a Verizon 3G Xoom and have it work for everything EXCEPT the 3g? I could honestly care less about ever activating it on Verizonas long as WIFI works.
trunzoc said:
Same question from me.
Can we install the WiFi only version of ROMs (CM9 in particular) onto a Verizon 3G Xoom and have it work for everything EXCEPT the 3g? I could honestly care less about ever activating it on Verizonas long as WIFI works.
Click to expand...
Click to collapse
From reading a bit in the Development sub-forum, it looks like there's a JB leak for the VZW version, and either version (WIFI Only or VZW) of the EOS 3 ROM should work. I think I will keep my order.
magnafides said:
From reading a bit in the Development sub-forum, it looks like there's a JB leak for the VZW version, and either version (WIFI Only or VZW) of the EOS 3 ROM should work. I think I will keep my order.
Click to expand...
Click to collapse
Thanks. I'm placing my order as soon as Wife says OK. If you don't mind, and if you remember, please send me a PM of how it goes with the flashing once to get yours.
Would love to coordinate what we do since there doesn;t seem like a whole lot of certainty exists about what we are trying to do.
I'm probably just going to flash the EOS 3 WIFI Only version. According to one of the devs, it should work fine:
http://forum.xda-developers.com/showpost.php?p=28578030&postcount=8
But I will try to remember to let you know how it goes.
magnafides said:
I'm probably just going to flash the EOS 3 WIFI Only version. According to one of the devs, it should work fine:
http://forum.xda-developers.com/showpost.php?p=28578030&postcount=8
But I will try to remember to let you know how it goes.
Click to expand...
Click to collapse
Any luck? I also have a Xoom 3G MZ600 on the way and could careless about 3G...
hasnt eos got jellybean roms for all versions of the xoom? 3g should work imo
Sent from my Xoom using XDA Premium App
I'm in the same boat and curious to see if anybody has any words of wisdom. I love my refurbed Xoom 3G but am eager to get JB on it. Any help is greatly appreciated.
FWIW everything I have heard/read seems to indicate that it is possible to flash WiFi only ROMs on the 3G Xoom, and apparently everything will work fine except for the 3G (naturally). I haven't taken the plunge yet myself, still running stock ICS.
Is there any word on whether the Verizon 3G Xoom will get Jelly Bean?
It can be done....
I purchased a used 3g Xoom around Apr 2012. After initially unlocking / rooting and installing a ROM (EOS) on my 3g Xoom, the 3G radio wasn't working so I started fresh. I locked the device and SBF'd the original Xoom firmware, then used the official over the air (OTA) upgrades to get back to stock ICS. I thought this might fix the 3g issue; it did nothing.
EOS Roms overclock the GPU by default, which caused problems with my (and my wife's Wifi version) Xoom. My only requirements for a ROM are stability, no clutter from dumb carrier installed applications, compatibility, and of course root access. I found a pre-rooted stock Jellybean rom, but it was for the Wifi Xoom. It worked great on my wife's though; and heard rumors that it could work with mine.
*SO*...I took a leap of faith and installed it. It works great. No 3g radio of course, but I gave up on trying to get that to work anyway...so if you don't care about losing your 3g , this will probably work for you. I don't think my 3g will ever work, but I suspect this won't ruin yours if it is currently working. Don't hold me to that; this is a risk.
Random notes and refresher info:
-you will need an SD card. I'm pretty sure the following instructions will only work if you use one.
-If at any point you get the android guy with an orange exclamation point during boot...it is probably ok, just let it sit there for a couple minutes. it should continue to boot into whatever ROM you are currently on. Make sure you enable usb debugging in settings after boot.
-to access RSD, Recovery, or Fastboot mode, press and hold your power button to start the Xoom booting. When you see the Motorola logo, wait a second then press the volume down button. Then you can use volume down again to cycle through your options, and use volume up to choose one.
-the exact differences between RSD / Fastboot and Recovery modes are beyond the scope of this post (and me) so just know that your Xoom can be modified using software on your PC via USB with RSD and Fastboot modes, and stock recovery can be replaced with modified versions to add more functionality. Recovery is used to do all sorts of things...flash Roms, mount drives, format, cleanup caches, etc.
***
General instructions. Just guidelines; you will probably need some previous experience with computers / rooting etc.
(If you are already unlocked, rooted, and have a replacement recovery, skip to the last step.)
1.) Follow this guide to prep your Xoom: (unlocking, rooting, and install CWM recovery)
http://www.xoomforums.com/forum/motorola-xoom-development/15179-how-rookie-rooting-flashing-unrooting-under-one-roof.html
Note: you may have heard of Lord AOI tool; it is supposedly designed to simply the above process. I found it didn't work well and was more difficult to use than good ol' adb commands. I recommend skipping it.
2.) OPTIONAL: Next, I recommend using the latest Rogue recovery. Just use standard CWM recovery to flash it. It is nice because it allows you to use the touchscreen to manipulate instead of having to use the hardware buttons (volume buttons are kind of a pain). See here: http://forum.xda-developers.com/showthread.php?t=1235170
3.) Finally, flash the pre-rooted stock Jellybean ROM. See here: http://forum.xda-developers.com/showthread.php?t=1796335
(here's the direct ROM link for those not needing instructions or extra info: http://www.mediafire.com/?7w5w65l66hgggo8 )
Good luck and let us know your results...
I am happy to let everyone know, I have my GS3 flashed to VZW prepay. Of course, its a Sprint version phone that has been flashed. (talk, text, and 3g) Currently its rooted, CWM Recovery 5.5.0.4 and running a Blazer Rom stock base off of LG8 L710VPLG8. It has the sprint bloat which i can do without. Since it is actually on VZW network, I would like to know....
Can a VZW ROM be flashed to the device that has a stock VZW feel and still very useable due to it being a Sprint phone? I would love to have a stock, rooted, unlocked rom that has all the apps out of the box.
Please help... Ive only gotten as far as changing the boot animation to make it a fully VZW ROM!
If you check the build.prop, see if it says d2vzw.
Sprint version is d2spr.
I changed my vzw to spr one time and was prompt me to do some Sprint stuff at startup. It was weird. Not sure if it can be done the other way around.
I don't think you can flash vzw roms. If the phone is Sprint based. You can always flash a generic Rom like aokp or slim.
And then manually install the Verizon apps?
Sent from my SCH-I535 using xda app-developers app
Does anyone else have any suggestions? Really need help cause 3g data jumps back and forth at times to 1X.
Hello, this is my first time posting on the forums here.
Recently I flashed the latest version of MIUI on my Verizon Galaxy s3. I decided that I preferred my previous rom; Jelly Bean's Build 10, and I restored it to my phone. After restoring the rom, I got a message saying that I was roaming, even though I am still in the same area where service has been working flawlessly. The first thing I tried to do was change the network type under network settings to LTE/CDMA but that choice was already selected. Thinking that I had no other options, I restored the stock rom that I had backed up on my device and I got the same issue. Thinking I could just send the phone back to Verizon, I unrooted the phone using the built in unroot tool in SuperSu Pro. I am now unrooted, but forgot to reflash the stock recovery (I am still using TWRP). I am just wondering what I should do about the issue, and if I were to send it back to verizon, would they be able to tell that I have a custom recovery. Sorry for being a noob and any help would be much appreciated.
Update: I rolled back to my rooted stock ROM and I used triangle away to reset the custom flash counter. I have also reflashed the stock recovery onto my device. Even though my phone appears to be unmodified I still have the same issue.
Sent from my SCH-I535 using xda app-developers app
there are SOOO many threads about how to fix the roaming issue it's not even funny....
^^^^^what he said!
This happened to me and what I had to do was ODIN to stock ICS rom and enter the code to reprovision sim. Google/forum search is your friend.
This is why Verizon locks down their phones! People who are not willing to search for a way to fix something that they screwed up is unacceptable. The bad thing is this phone is completely fixable with very little effort! Some people should not be allowed to flash anything!
I've dealing with so many issues ever since the DroidX so if there is one thing I've learned is there is ALWAYS a fix you may just need to do a little search if you can't find the resources your looking for on any of forums a simple google search will help you out.
The Problem/Symptoms: I've been running a version of last CM10.2 for the past year. On February 20th, I was able to send a single SMS and then subsequent texts failed. I could still receive SMS, send/receive MMS, send/receive calls and send/receive data. If I toggle airplane mode/reboot I can send another SMS and then subsequent sms are undeliverable.
What wont work: Flashing to CM11 does not change the issue.
Disabling Voice+ does not change the issue
Factory Reset does not change the issue
Workarounds: Toggle Airplane mode
Switching Mobile Network to CDMA only (not permanent)
Change your number to a different area code
Going back to a Touchwiz based ROM
The Solution
net-cat said:
Alright. I think I've refined my process and it results in having a newer radio as well as not having to ODIN things or do dd commands.
NOTE: This isn't fully tested. When I did this, my phone wasn't showing the issue. I did this after doing my original procedure, but the GPS stopped working after I updated the radio from VRALF2 to VRBMB1. You shouldn't need to do the original procedure for this to work, but I haven't tested that. At the very least, the original procedure still works and this one can be used afterward if you need the newer radio. (GSM support...)
Ideally, we'll want to get to a procedure that doesn't use ODIN or dd. Hopefully this is a step in that direction.
Requirements:
A rooted stock ROM of the VRUCML1/4.3 vintage. I used Scott's Stock Rooted Knox Free VRUCML1 - 4.3 - DeOdex - V2. (Thread here.)
VRBMB1 AIO Flash, available here. (Thread here.)
I'm going to assume you know how to boot into and use recovery.
NOTE: Do NOT let the stock ROM install any updates.
Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)
Flash the VRBMB1 AIO.
Wipe data and cache.
Flash the stock ROM.
Boot into the stock ROM.
The reprovisioning seems to happen as a part of ROM's initial boot up.
Send a few text messages to test. (I sent them to Twitter.)
Launch the Maps application, turn on your GPS and let it get a lock. If you don't, when you boot back into your ROM, you probably won't have working GPS.
This would be a good time to back up your IMEI if you haven't already done so.
Reboot into your recovery, wipe data/cache and restore your nandroid backup.
At this point, you'll be running your preferred ROM with a less archaic radio than my previous post.
DO NOT UPGRADE YOUR RADIO. The moment I upgraded my radio, the problem came back!
CM11 M3 will work just fine with the old radio. I've rebooted several times over the last few hours and it still works fine. (Time will tell if it's a long term fix or not.)
Click to expand...
Click to collapse
buffal0b1ll said:
I put a MB1 aoi zip in my dropbox for you. It's from invisblek.org which isn't working now for some reason https://www.dropbox.com/s/7b1aqspo40fxl00/VRBMB1.aio.zip
Click to expand...
Click to collapse
Notes: There are threads for the S4 with this identical problem. All updated information I have seen is listed above. If anyone knows more please post as I am going to keep this updated. If this does/doesn't work for you please post and let the community know. Feel free to hit the thanks button if it works for you.
This exact thing happened to me. I tried many fixes with no luck. After hours of hacking around in settings, I found a ROM of verizon's 4.3 OTA update and flashed that through ODIN. My texts are working just fine again. Kind of a cheap method of fixing my problem. I wish I could have taken more time to find a fix, but I needed to be able to communicate with people that day.
Stock 4.3 is kind of lame:
-4.3 is killing my battery faster than ever. CM11 had me going for days without charging and now I've needed to charge everyday.
-Stock 4.3 is laggier/slower than CM11. It tends to stutter for me.
-4.3 came with a new boot loader which no developers have exploited to install custom ROMs yet. This leaves you stuck with Verizon bloat. I hate all these damn apps. Going to try to safe root & see if I can't do some cleanup work.
Enough ranting. Just wanted to let you know you are not alone with this problem. Hopefully someone will figure it out. Missing my cyanogen mod already
It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://forum.xda-developers.com/showthread.php?t=2654822
It looks like the symptoms have all showed up at the same time approximately. (February 19th, 2014). Still looking for a better answer than going back to stock TW...
Edit: And another thread http://forum.xda-developers.com/showthread.php?t=2659280 This one suggests its all AOSP roms. But it seems many people are unaffected... I don't understand why/how.
edit2: and another thread http://forum.xda-developers.com/showthread.php?p=50627899
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Dex954 said:
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
SO this is the current status that I know.
The problem happens for everyone with a 570/717 area codes + on verizon + running Cyanogenmod (possibly any AOSP) + while connected to LTE which started on Feb 20th (the day before KitKat came out offically).
Current Workarounds:
Switch to TouchWiz based Roms
Switch your radios to be CDMA only
Call verizon and switch your number to a different area code
I know the workarounds all suck but that all I know for now. Switching SIM cards won't work. If I anyone knows anything more please feel free to let me know.
I'm 717
Sent from my SCH-I535 using Tapatalk
I have still be unable to find a solution for this issue. I think I have to give up on CM and go back to a TW based. If I hear anything new I'll update the post but I don't have the time to be wasting on my phone at the moment. If someone finds or hears of a fix or if it magically goes away as it started, please post it.
And spread the word if there are any other ROMs that this is occurring on. It seems the pool of those affected is just too small.
I have already had to give up. Been running slows tw. I take it Verizon didn't get back to you?
Sent from my SCH-I535 using Tapatalk
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
DreamFX said:
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
Click to expand...
Click to collapse
Godspeed my friend.
Anyone try aosp to see if fixed yet?
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
capt730 said:
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
Click to expand...
Click to collapse
I try every other day. 717 for me. Remaining hopeful it's fixed... One day...
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
capt730 said:
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It won't. It isn't software dependent. People who had already flashed builds prior to the 20th magically had issues starting on that date, so it isn't a problem with new builds, and it only happens to those in the 717-570 areas so it isn't a problem with AOSP code. It has to be a Verizon network issue, I just have no idea how.
Sent from my SCH-I535 using XDA Premium 4 mobile app
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
capt730 said:
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
Click to expand...
Click to collapse
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
I'm ok with using CR8, Beans or other stock roms. Can't see paying for LTE and not using it lol. Was curious to see how aosp has been coming along and sms was really the only issue I was having.
Obaterista93 said:
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
Click to expand...
Click to collapse
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Whisk_33 said:
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Click to expand...
Click to collapse
Basically. I've talked to a few friends who have worked for carriers and stuff, and everyone is stumped as to how something like this can even happen. Luckily I'm pretty much always in WiFi so I can survive on CDMA only.
As the title says, I am on T-mobile now with my D850. My phone is currently unlocked and rooted using stock rom.
the last phone i flashed a custom rom was with my htc one x and frankly i forgotten all the little details and never bothered because it took a lot of time. i know i need bootloader unlocked to install a custom recovery to flash the rom then back up, install gapps, etc etc. I don't have time or the patience to relearn everything.
I got interested in learning that CM11 is available and i checked out the CM website and was surprised to hear all i have to do is install the installer on both my phone and PC and boom, everything else is automated. This is what i want to try. Here are my questions:
- do i have to manually install any apn, radio, etc. things of that nature to get the proper t-mobile network signal for voice, LTE data, and text messaging?
- is an official D850 released so that once i install, i can simply keep up to date into CM12 via automatic updates through the software? (one click update OTA)
- do i need to make a titanium back up or will all my apps and settings stay when i flash CM?
I appreciate any and all answers. I have not unlocked bootloader via bump yet. but my main worry is will i have to custom install/input all the t-mobile apn and radios because that will require me to manually find and install and risk messing things up.
chillsen said:
As the title says, I am on T-mobile now with my D850. My phone is currently unlocked and rooted using stock rom.
the last phone i flashed a custom rom was with my htc one x and frankly i forgotten all the little details and never bothered because it took a lot of time. i know i need bootloader unlocked to install a custom recovery to flash the rom then back up, install gapps, etc etc. I don't have time or the patience to relearn everything.
I got interested in learning that CM11 is available and i checked out the CM website and was surprised to hear all i have to do is install the installer on both my phone and PC and boom, everything else is automated. This is what i want to try. Here are my questions:
- do i have to manually install any apn, radio, etc. things of that nature to get the proper t-mobile network signal for voice, LTE data, and text messaging?
- is an official D850 released so that once i install, i can simply keep up to date into CM12 via automatic updates through the software? (one click update OTA)
- do i need to make a titanium back up or will all my apps and settings stay when i flash CM?
I appreciate any and all answers. I have not unlocked bootloader via bump yet. but my main worry is will i have to custom install/input all the t-mobile apn and radios because that will require me to manually find and install and risk messing things up.
Click to expand...
Click to collapse
You just need to install Bump! And a backup is recommended in case something goes wrong, as far as connecting to tmobile all you need is the APN, i have a D850 and i live in mexico and CM11 and 12 work fine with just the apn, also everything will get wiped except for pics and music if you dont wipe internal storage
SmokeyTech1 said:
You just need to install Bump! And a backup is recommended in case something goes wrong, as far as connecting to tmobile all you need is the APN, i have a D850 and i live in mexico and CM11 and 12 work fine with just the apn, also everything will get wiped except for pics and music if you dont wipe internal storage
Click to expand...
Click to collapse
errr i am not comfortable with adb to install bump! would the automated installer on pc and phone do all this for me? i guess i can try? i just love how CM installer does everything for you. also thanks for confirming all i need to do is input the APN which i'm familiar with when i had switched to t-mobile after i had unlocked my phone. lastly will i have to install gapps separately? Thank you so much, i wish i didn't have to use adb to bump!
chillsen said:
errr i am not comfortable with adb to install bump! would the automated installer on pc and phone do all this for me? i guess i can try? i just love how CM installer does everything for you. also thanks for confirming all i need to do is input the APN which i'm familiar with when i had switched to t-mobile after i had unlocked my phone. lastly will i have to install gapps separately? Thank you so much, i wish i didn't have to use adb to bump!
Click to expand...
Click to collapse
Dont need to use adb, just download flashify from the play store, does it all by itself, very easy, the automated installer is just for the rom, you need a recovery first, the gapps should be installed at the same time as the rom, but ive never used the auto installer, i would flash it with the recovery, i like to things manually
Just to let you know that with every AOSP ROM with a T-Mobile Sim you will get a kernel panic if using LTE. I have the D850 but using a T-Mobile Sim. I have to have it on 3g instead of LTE. No ones been able to figure it out I'm guessing because there is only one or two of us using a T-Mobile Sim with this phone. Bummer huh
???CAUTION???
May ruin other ROMS after this
because nothing compares
coletague said:
Just to let you know that with every AOSP ROM with a T-Mobile Sim you will get a kernel panic if using LTE. I have the D850 but using a T-Mobile Sim. I have to have it on 3g instead of LTE. No ones been able to figure it out I'm guessing because there is only one or two of us using a T-Mobile Sim with this phone. Bummer huh
???CAUTION???
May ruin other ROMS after this
because nothing compares
Click to expand...
Click to collapse
Well then have you thought of changing carriers? It is a d850 for Att ..... Does it kernel panic on stock Roms ? You might just be **** out of luck cause I'm pretty sure everyone here uses Att. I use straight talk with no issues. You have slim choices..... Change carriers. .... Quit using T-Mobile if you are unhappy with the custom ROM and LTE kernel panics. Or buy a T-Mobile g3..... Lol suck eh... But just telling you what you need to hear.
Or maybe if you are ballsy try to see if a Dev for T-Mobile can help you with this cause I'm thinking that may be your beat bet cause none of us use T-Mobile. :thumbup::beer:
2SHAYNEZ
It's fine with stock based ROM s which I'd rather be on AOSP with HSPA
???CAUTION???
May ruin other ROMS after this
because nothing compares
coletague said:
It's fine with stock based ROM s which I'd rather be on AOSP with HSPA
???CAUTION???
May ruin other ROMS after this
because nothing compares
Click to expand...
Click to collapse
Maybe it will iron itself out after a while. Good luck
2SHAYNEZ
Do you have a beef with him or what?
4ndroid4Life said:
Do you have a beef with him or what?
Click to expand...
Click to collapse
You chose to say this for your first post on XDA ....... Wow...
2SHAYNEZ
coletague said:
Just to let you know that with every AOSP ROM with a T-Mobile Sim you will get a kernel panic if using LTE. I have the D850 but using a T-Mobile Sim. I have to have it on 3g instead of LTE. No ones been able to figure it out I'm guessing because there is only one or two of us using a T-Mobile Sim with this phone. Bummer huh
Click to expand...
Click to collapse
interesting note, will update you, LTE seems to be working fine, speeds are fine, but i need to use LTE longer to see the kernel problem. I'm on the CM 11, dec 6 nightly currently. how about you?
Latest nightly of cm12. Try downloading a ROM over LTE
???CAUTION???
May ruin other ROMS after this
because nothing compares
It's always recommended to use WiFi to download any Roms anyways ..... Do you have a crap ton if data or something ...
2SHAYNEZ
I don't have Internet.
I have literally unlimited data. My phone was free and my service is free
coletague said:
I don't have Internet.
I have literally unlimited data. My phone was free and my service is free
Click to expand...
Click to collapse
That's crazy... You must work for tmo
2SHAYNEZ
Is it now understandable why I use T-Mobile? Lol
???CAUTION???
May ruin other ROMS after this
because nothing compares
coletague said:
Is it now understandable why I use T-Mobile? Lol
???CAUTION???
May ruin other ROMS after this
because nothing compares
Click to expand...
Click to collapse
Oh yeah absolutely... Hook me up jeez.... Straight tall is good and all but unlimited unthrottled just isn't fair lol. Jeeez
2SHAYNEZ
Ha I can only have two Sims the way I do and that one is occupied. Fix my kernel panics lol I'll give you a last kmsg
???CAUTION???
May ruin other ROMS after this
because nothing compares