I have a 4G LTE Xoom that was on Verizon. I recently upgraded (now I have a Galaxy Note 10.1 2014 Edition), and my parents are buying my Xoom for use around the house on Wifi.
My question is: Can I just flash a Wifi Rom? Or will that mess up other things? Also, can/should I remove the LTE SIM card?
I know prior to BigPart, you could flash Wingray roms and get the what you're trying to achieve, but I did read that someone else tried that with the BigPart roms and got a whole slew of FCs that made the tablet unusable. I've currently suspended my tablet line through Big Red and I simply took my SIM card out. I get a warning any time I reboot about mobile data not working until a valid SIM card is installed, but if you ignore that, it functions perfectly otherwise.
Sent from my HTC6435LVW using xda app-developers app
I'll be honest: I haven't flashed a new ROM to my Xoom in a long time. It's currently running EOS Nightly 197 (Android 4.2.2) I had to look up what BigPart is, but I haven't installed anything like that. Would it be better if I do install Bigpart, and a Bigpart ROM? I think they can deal with pressing a "no SIM card" message on startup, but even on my current ROM, it's pretty laggy and slows down. Are Bigpart ROMs any better, or should I downgrade back to Honeycomb or something?
romshark said:
I'll be honest: I haven't flashed a new ROM to my Xoom in a long time. It's currently running EOS Nightly 197 (Android 4.2.2) I had to look up what BigPart is, but I haven't installed anything like that. Would it be better if I do install Bigpart, and a Bigpart ROM? I think they can deal with pressing a "no SIM card" message on startup, but even on my current ROM, it's pretty laggy and slows down. Are Bigpart ROMs any better, or should I downgrade back to Honeycomb or something?
Click to expand...
Click to collapse
If your parents are like mine (read: not particularly tech-savvy), I'd probably just go back to stock JB. As much as I love the features of 4.4.2, you can't beat the stability and smoothness of 4.1.2 on this now-three-year-old tablet.
Sent from my HTC6435LVW using xda app-developers app
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...
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Daze7 said:
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Click to expand...
Click to collapse
Are you running the latest nightly or the 'stable' build? The 'stable' build (note the "") isn't that stable and from the sound of it you are experiencing the screen of death (SoD) that I believe is present in the 'stable' build.
If you flashed the 'stable' build, flash the newest nightly instead. Or better yet, head on over here and also flash this (it's better than CM10 IMO - Just be sure to flash the kernel AFTER the rom). :good:
Daze7 said:
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Click to expand...
Click to collapse
Which version of CM10? No reboots here on Provision.. Used CM10 latest nightly as a base.. If you have random reboots then I should too.. Also a logcat would be helpful.
Sent from my Provisioned Galaxy S Blaze
Im on the stable version, but ill try the nightly like the first post suggest or the link you provided
Edit: logcat on the way sorry about that
Sent from my SAMSUNG-SGH-T769 using Tapatalk 2
anactoraaron said:
Are you running the latest nightly or the 'stable' build? The 'stable' build (note the "") isn't that stable and from the sound of it you are experiencing the screen of death (SoD) that I believe is present in the 'stable' build.
If you flashed the 'stable' build, flash the newest nightly instead. Or better yet, head on over here and also flash this (it's better than CM10 IMO - Just be sure to flash the kernel AFTER the rom). :good:
Click to expand...
Click to collapse
Hey, I downloaded the rom and kernel that u suggested. When i plugged in my phone to my laptop to transfer the files to my sd card i noticed that my internal sd and ex sdcard now reads as 'Generic Hierarchical'. Prior to this i did notice that my ex and internal memory were not showing the correct amount of space after rooting but i was so happy with the root that it slipped my mind somehow.
What in the world is generic hierarchical? And how can I get it safely to Fat32 to flash the ParanoidAndroid without messing up my phone?
Daze7 said:
Hey, I downloaded the rom and kernel that u suggested. When i plugged in my phone to my laptop to transfer the files to my sd card i noticed that my internal sd and ex sdcard now reads as 'Generic Hierarchical'. Prior to this i did notice that my ex and internal memory were not showing the correct amount of space after rooting but i was so happy with the root that it slipped my mind somehow.
What in the world is generic hierarchical? And how can I get it safely to Fat32 to flash the ParanoidAndroid without messing up my phone?
Click to expand...
Click to collapse
Go to settings/storage. Press menu. Then USB computer connection. There you can choose. Select USB mass storage. When connected to the computer it will prompt you if you want to move files from computer to your phone.
Sent from my Provisioned Galaxy S Blaze
In the end I just went back to stock and did a clean new root, this time with ParanoidAndroid. I loved the cm10 stable i had but the phone shutting off was t0o much. Thanks for all the help though i really appreciate it. :angel:
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.
I have looked through quite a few threads, and followed a plethora of instructions, so If I have missed something I apologize.
I originally had the MZ600 without the 4G upgrade, and decided to give that to my little brother and purchase one that had the 4G radio.
So now I have an MZ600 with the 4G radio upgrade, activated on verizon. before I tried any flashing, I had 4G. I didn't want to do the bigPart upgrade yet, so I flashed the 196 version of EOS4 for stingray (not stingray cdma) and upon boot up, i could get 3g but not 4G. It showed the baseband as CDMA only with no LTE.
I flashed back to stock Honeycomb, and after the OTA update of the radios, i had 4G again. followed the OTA's all the way to 4.1.2. still maintained 4G.
After that, i decided to do the bigPart, which after some finagling I managed to get it partitioned, and installed OmniROM 4.4 stingray (not stingray cdma)
Upon boot, I had no 4g again, and could not even get 3g data at all. so i repartitioned back to stock, and reflashed honeycomb. got 4G again.
So my question is how the heck do I get a new ROM on this thing, when every time i flash one, I lose the 4G radio baseband?
Did you ever get an answer to this? I am in the exact same boat. Same story except I performed the LTE upgrade myself. Works flawlessly on Stock 4.1.2, but I have not found a single non-stock ROM with which I can use the mobile data.
Bump!!
taylorinnov said:
Did you ever get an answer to this? I am in the exact same boat. Same story except I performed the LTE upgrade myself. Works flawlessly on Stock 4.1.2, but I have not found a single non-stock ROM with which I can use the mobile data.
Bump!!
Click to expand...
Click to collapse
Crystawth said:
I have looked through quite a few threads, and followed a plethora of instructions, so If I have missed something I apologize.
I originally had the MZ600 without the 4G upgrade, and decided to give that to my little brother and purchase one that had the 4G radio.
So now I have an MZ600 with the 4G radio upgrade, activated on verizon. before I tried any flashing, I had 4G. I didn't want to do the bigPart upgrade yet, so I flashed the 196 version of EOS4 for stingray (not stingray cdma) and upon boot up, i could get 3g but not 4G. It showed the baseband as CDMA only with no LTE.
I flashed back to stock Honeycomb, and after the OTA update of the radios, i had 4G again. followed the OTA's all the way to 4.1.2. still maintained 4G.
After that, i decided to do the bigPart, which after some finagling I managed to get it partitioned, and installed OmniROM 4.4 stingray (not stingray cdma)
Upon boot, I had no 4g again, and could not even get 3g data at all. so i repartitioned back to stock, and reflashed honeycomb. got 4G again.
So my question is how the heck do I get a new ROM on this thing, when every time i flash one, I lose the 4G radio baseband?
Click to expand...
Click to collapse
I had the same problem, until I called into customer service and had them totally delete my tablet off of the account. After that I had them reactivate it using the (here's the catch) IMEI, same sim.Hope this helps.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
getyroks said:
I had the same problem, until I called into customer service and had them totally delete my tablet off of the account. After that I had them reactivate it using the (here's the catch) IMEI, same sim.Hope this helps.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
My tablet is already activated using the IMEI and has 4G data. but I am still running stock. I may attempt flashing cyanogenmod at some point to see. but for the time being I have simply dealt with the stock rom. Rooted of course lol.
Here's the Answer!!!
http://forum.xda-developers.com/showthread.php?t=2635282
Long story short, the problem is that final OTA update. You HAVE to stop installing OTA updates at IMM76L. DO NOT install JZO45M. As near as I can tell, it installs some sort of radio update that is not compatible with most if not all non-stock ROMs.
If you do let that final update install, you have to take the device all the way back to stock honeycomb and start over. See the above thread for precise details.
taylorinnov said:
http://forum.xda-developers.com/showthread.php?t=2635282
Long story short, the problem is that final OTA update. You HAVE to stop installing OTA updates at IMM76L. DO NOT install JZO45M. As near as I can tell, it installs some sort of radio update that is not compatible with most if not all non-stock ROMs.
If you do let that final update install, you have to take the device all the way back to stock honeycomb and start over. See the above thread for precise details.
Click to expand...
Click to collapse
That's my thread, and what Taylor says is spot on. All of these custom ROMs are built using proprietary files from ICS and the JB update screws everything up. It's a laborious process to get 4G working, but it's worth it.
Sent from my XT1060 using XDA Free mobile app
webeougher said:
That's my thread, and what Taylor says is spot on. All of these custom ROMs are built using proprietary files from ICS and the JB update screws everything up. It's a laborious process to get 4G working, but it's worth it.
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
4G LTE XOOM Update owners attempting to BigPart:
My pain should be your gain........check this page:
http://forum.xda-developers.com/showthread.php?t=2635282&page=4
Check the Final Update......you MUST stop at IMM76L......Activate your SIM after every patch update to be sure. If you don't have your 4G back by IMM76L you have to wipe and restart the process. The LTE Baseband files are not being flashed to the radio properly.
gooniegoogoo2 said:
4G LTE XOOM Update owners attempting to BigPart:
My pain should be your gain........check this page:
http://forum.xda-developers.com/showthread.php?t=2635282&page=4
Check the Final Update......you MUST stop at IMM76L......Activate your SIM after every patch update to be sure. If you don't have your 4G back by IMM76L you have to wipe and restart the process. The LTE Baseband files are not being flashed to the radio properly.
Click to expand...
Click to collapse
YOUR pain? You have no idea how many hours I put into trying to figure out why data wouldn't work and then going through all the possible steps to make it work again, AND THEN writing everything up.
Sent from my XT1060 using XDA Free mobile app
So, I'm buying this to replace my evo 4g and I was wondering how I would go about using a custom ROM for this and having the apns and data working correctly.
I plan to activate it on Ting.
To be a bit clearer, I want to use a custom ROM and I want to be sure that it'll work. So first, can anyone on Ting confirm that they're running a custom ROM (preferably KitKat) with no problems?
And I assume I'd have to activate the phone first, then install a custom ROM. Would I have any problems doing that? Would the apns be messed up? Or should everything be fine as long as I activate the phone and update everything on stock before installing a ROM? Reason I ask is because I know some Roms don't allow the *#*# thing needed to activate a phone on a new network.
Thanks!
I am using mine on Ting. I had used my first Q as unrooted stock JB, which worked pretty well for a year, but then it reached a near--bricked state where it wouldn't boot past the yellow Sprint screen. I couldn't resolve this in a timely fashion, so wound up buying a second Q which runs stock ICS, but failed to download the stock JB update.
In the meantime, I unlocked both phones' bootloaders, and tried a few kItkat ROMs on my original phone before settling on CM 10.2, which is a JB ROM. I then switched my Ting activation (back) to this phone. The lack of #*# commands isn't really a problem with respect to re-activation, but it is a problem with respect to PRLs and (perhaps) APNs. I recommend Ting activation and a PRL update prior to installing your custom ROM.
Like others, I would like to learn about a stable kitkat ROM where bluetooth, wifi, and phone data/sms/calling all work reliably. My other primary requirement is the ability to play DRM'd downloaded Amazon Prime Music, which didn't work on the kitkat ROMs I tried, but does work on my JB ROM.
Sent from my XT897 using Tapatalk