Related
Ok, I'm probably overlooking somthing simple but I can't get the latest nightly stingray ICS Xoom Rom to connect to verizon 3g/4g. I've searched around on google and the forums a bit but I don't see anything about it.
Here's what I've done so far.
Starting point Moray Xoom
Titanium back + nanodroid
factory reset
flash stingray
boot into ICS, all is well (didn't check internet)
reboot into recovery
install gapps (the zip located in the main stingray thread on this board)
boot up, everything works great on wifi
disable wifi, go to settings -> wireless & networks -> more -> Mobile Networks
click activate
I let it set there for 20 minutes and think about it but it never connected. One other thing i noticed is that the clock is correct, but is set to GMT instead of GMT-6.
What am I doing wrong?
Update: I'm running build EOS IML74K Nightly 8
Baseband version shows "Unknown"
Aethoes said:
Ok, I'm probably overlooking somthing simple but I can't get the latest nightly stingray ICS Xoom Rom to connect to verizon 3g/4g. I've searched around on google and the forums a bit but I don't see anything about it.
Here's what I've done so far.
Starting point Moray Xoom
Titanium back + nanodroid
factory reset
flash stingray
boot into ICS, all is well (didn't check internet)
reboot into recovery
install gapps (the zip located in the main stingray thread on this board)
boot up, everything works great on wifi
disable wifi, go to settings -> wireless & networks -> more -> Mobile Networks
click activate
I let it set there for 20 minutes and think about it but it never connected. One other thing i noticed is that the clock is correct, but is set to GMT instead of GMT-6.
What am I doing wrong?
Update: I'm running build EOS IML74K Nightly 8
Baseband version shows "Unknown"
Click to expand...
Click to collapse
I dont have a 3g/4g unit - but I would try this upgrade path instead.
-Factory Reset - Wipe Data and Dalvik
-Format ALL partitions as well (Yes this sucks) but not external sd card. I hope your nandroid is on a external sd card anyway.
-Be sure you have the ICS ROM and GAPPS ready to flash.
-Go into mounts/storage and mount all partitions.
-Flash ROM - and dont reboot
-Flash GAPPS
-Reboot Device
-DO NOT RESTORE TIBU DATA...just apps.
This is my preferred upgrade path on every android device.
Let us know how it worked.
I would start over, with a wipe data/factory reset from within CWM as well as a wipe cache and wipe dalvik. Then flash stingray then gapps (without rebooting in between - doing so has caused problems on other ics roms). If that doesn't work, you may have a bad download - did you check the mdsum?
Ok, I followed the steps exactly as listed above. Now when i start up it's going into a wizard which is automatically "Searching for service..." and has a option to skip and go with wifi instead.
Update:
After bypassing 3G and setting up wifi I've noticed that the baseband version listed under "Settings -> About Tablet" is still showing Unknown. Is this a sign that the baseband driver for 3G on my device isn't recognizing?
MZ600 is the same situation as you.
ALL available ROM cannot recognize the baseband version if you have not get 4G update.
That's a terrible problem for overseas users!
Intro
The info on how to do this is scattered around, thought it might be good to have a post for this, was really annoying for me to get this fixed
Problem
After upgrading to the latest Cyanogenmod 10.1 (cm-10.1-20121224-NIGHTLY-d2vzw.zip), the phone will not connect to the cell network. Some symptoms of this:
- Cannot send/receive text messages
- Cannot make calls, all calls give error "Your account is not authorized to make calls to this phone number"
- On boot, activation starts ("Waiting for network...") but cannot complete
- In Settings -> About Phone -> Status, you see the following info:
-- Roaming: Roaming
-- Mobile Network State: Disconnected
-- My phone number : 000-000-0311 (or similar)
Solution
I tried a number of solutions, but the only way I've seen to fix this is to revert to stock ICS using Odin, then perform a full factory reset. Please note that you will lose ALL data, including anything on the internal storage. The SD card should not be touched. You will also lose your unlocked bootloader, although that is easily restored.
1. BACK UP any data you might need, including clockwork/titanium backups, get them off your phone
2. Follow instructions here to flash the rooted ICS image (stock.vzw_root66.tar) using Odin. The torrent is much faster to download the image.
3. If your phone goes into a boot loop (stuck on the LTE boot logo), boot into stock recovery (Vol Up + Home + Power) and clear data / factory reset
4. Boot up the phone, go into the dialer, type: *2767*3855#
5. Your phone will immediately factory reset itself
You should now have cell connectivity again, and should also have root. You can then unlock your bootloader (get v1.2 here) and finally use Clockwork to re-install another ROM.
Note that after doing the above to restore my cell connectivity, I tried to do a clean install of CM 10.1, with full data wipe and such, and I once again lost cell connectivity and had to factory reset again. It seems to me like something is very broken with CM 10.1 for the VZ S3, and until it's figured out I recommend staying with CM 10.0 (cm-10-20121216-NIGHTLY-d2vzw.zip), which does not appear to have this problem.
funkymonk101 said:
Intro
The info on how to do this is scattered around, thought it might be good to have a post for this, was really annoying for me to get this fixed
Problem
After upgrading to the latest Cyanogenmod 10.1 (cm-10.1-20121224-NIGHTLY-d2vzw.zip), the phone will not connect to the cell network. Some symptoms of this:
- Cannot send/receive text messages
- Cannot make calls, all calls give error "Your account is not authorized to make calls to this phone number"
- On boot, activation starts ("Waiting for network...") but cannot complete
- In Settings -> About Phone -> Status, you see the following info:
-- Roaming: Roaming
-- Mobile Network State: Disconnected
-- My phone number : 000-000-0311 (or similar)
Solution
I tried a number of solutions, but the only way I've seen to fix this is to revert to stock ICS using Odin, then perform a full factory reset. Please note that you will lose ALL data, including anything on the internal storage. The SD card should not be touched. You will also lose your unlocked bootloader, although that is easily restored.
1. BACK UP any data you might need, including clockwork/titanium backups, get them off your phone
2. Follow instructions here to flash the rooted ICS image (stock.vzw_root66.tar) using Odin. The torrent is much faster to download the image.
3. If your phone goes into a boot loop (stuck on the LTE boot logo), boot into stock recovery (Vol Up + Home + Power) and clear data / factory reset
4. Boot up the phone, go into the dialer, type: *2767*3855#
5. Your phone will immediately factory reset itself
You should now have cell connectivity again, and should also have root. You can then unlock your bootloader (get v1.2 here) and finally use Clockwork to re-install another ROM.
Note that after doing the above to restore my cell connectivity, I tried to do a clean install of CM 10.1, with full data wipe and such, and I once again lost cell connectivity and had to factory reset again. It seems to me like something is very broken with CM 10.1 for the VZ S3, and until it's figured out I recommend staying with CM 10.0 (cm-10-20121216-NIGHTLY-d2vzw.zip), which does not appear to have this problem.
Click to expand...
Click to collapse
easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)
This should now let the ur phone have access to the network and get rid of the roaming issue.
Same problem
Having this exact problem. My problem is I do not have access to a windows computer and thus cannot use Odin. I have already performed a Factory reset so I may try the way that involves removing the sim card. I dont know how more people haven't posted on this yet...
---------- Post added at 05:48 PM ---------- Previous post was at 05:34 PM ----------
rossida said:
easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)
This should now let the ur phone have access to the network and get rid of the roaming issue.
Click to expand...
Click to collapse
as far as I can tell this does not work. You must have a sim card to get past the second screen in boot up. There is no other option besides to turn of your phone.
Thank you for the help! My phone as been out of commission for the past 2 days and the OP directions fixed it. However the second post did nothing to help out. Worth a shot though
Does anyone know if this can be done from a Mac?? I am a little desperate here. Ive spent most of Christmas day messing with this.
You'll have to find a Windows computer, or install a windows virtual machine using vmware fusion or parallels desktop.
will this work for us cellular??
rossida said:
easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)
This should now let the ur phone have access to the network and get rid of the roaming issue.
Click to expand...
Click to collapse
This has happened to me twice. The second time I used this method and it worked for me. It was only successful when I switched to the executioner 2.5 rom which was on my sd card. Thanks!
Nvm fixed it
*wrong thread*
killerkiyoshi said:
Nvm fixed it
Click to expand...
Click to collapse
How???
Okay, finally have my service back in stock touchwiz. This is what I did for anyone that cares to know: In CM10 during "activation" I pulled my sim card out, let it finish activating, powered down put sim card back in. Then I booted it back up and went to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV). THEN I did a factory reset in CM10 making it look as if I had just flashed it again. Then I booted into recovery and went back to stock TouchWiz where my 4g LTE came back magically and I could call and place texts. Not really any rhyme or reason but my service is back and I am beyond pleased. I am very nervous to flash any roms as of now I might wait til tomorrow luckily I have all my stuff backed up Hopefully it stays this way. Message me with any questions and I will help as much as I can. Merry Christmas
pupsinmytub said:
Okay, finally have my service back in stock touchwiz. This is what I did for anyone that cares to know: In CM10 during "activation" I pulled my sim card out, let it finish activating, powered down put sim card back in. Then I booted it back up and went to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV). THEN I did a factory reset in CM10 making it look as if I had just flashed it again. Then I booted into recovery and went back to stock TouchWiz where my 4g LTE came back magically and I could call and place texts. Not really any rhyme or reason but my service is back and I am beyond pleased. I am very nervous to flash any roms as of now I might wait til tomorrow luckily I have all my stuff backed up Hopefully it stays this way. Message me with any questions and I will help as much as I can. Merry Christmas
Click to expand...
Click to collapse
Yall all need to chill out. Just fix your mobile network settings, toggle airplane mode, and you'll be fine.
You have no reason to fear flashing any roms.... With common sense.
Sent from my SCH-I535 using xda app-developers app
Flash cm10.1 go to settings/networks/cdma subscriptions and change it back to RUIM/SIM. U haz data now. :thumbup:
Sent from my SCH-I535 using xda app-developers app
None of this has worked for me. I have followed the post directions and still have roaming. I am not seeing this option some of you are talking about though " wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)"... is this option supposed to be in the stock ics rom?
Update: the line had been suspended for some very odd reason
Got it working on VZW SG3 for now
This worked for me:
Reboot to recovery and fix permissions (not sure if this step helped just following some other posts) --> change mobile networks to the sim option ---> and most importantly enable National Data Roaming (this is the step that kicked over my signal)
After doing this it has started to let me call out and receive sms. My only concern is what consequences will i have with the national data roaming enabled and secondly when I am in other networks if I will get better signal; i live in a small town and get 1x so I have no idea what will happen till i get into the city but this seems to be a good fix for now. Hope this helps.
Tried all posted solutions and then some, still can't get CM 10.1 working on d2vzw
All,
I have a stock-rooted SCH-I535, and am also unable to get CM 10.1 working without losing the voice connection. It appears that my problem is corrupted NVRAM. Although my IMEI remains correct after flashing 10.1, my phone number and other info (ERI) gets corrupted. After a day of anxious attempts to fix the phone, the only fix I've found is flashing root66 (after which the phone still doesn't boot to the OS), factory reset (allows phone to boot), and then dialing factory-reset code *2767*3855#. For some reason the dialer-initiated reset seems to fix the NVRAM issue while the recovery-initiated reset does not.
After figuring out how to fix the problem, I've tried a handful of ways to get CM 10.1 working properly.
Original try: flash 10.1 over rooted-VRBLK1 using TWRP 2.3.1. After fixing by flashing root66, recovery factory-reset, and dialer factory-reset, I was nervous and made a couple backups.
used the su ; reboot nvbackup commands in this RootzWiki post.
Made a QPST backup with the instructions in this XDA post.
2nd try: factory reset, wipe data/system partitions, re-flash 10.1 with TWRP. This attempt had the same roaming/corrupted phone info result, but this time I was confident because I was armed with the two backup methods above.
I tried using the Samsung MEID RepairV3.5 in this XDA thread, but it wouldn't connect to the phone running CM10.1. I've gotten that tool to connect to the root66 image, so I know I'm following the procedure correctly. However, the developer specifically states that the tool is intended for stock images, so I wasn't surprised that it failed to work on CM 10.1.
with su privilages, I used terminal command "reboot nvrestore". I expected this to work, but it resulted in an unbootable OS. I had to flash root66 and repeat the fix process described at top.
Third try: flashed 10.1 again with TWRP 2.3.1. I tried using the QPST recovery I had created earlier. I got the phone into diagnostic mode (RMNET+DM+MODEM) using terminal commands for AOSP ROMs. For some reason I couldn't get the scripts to work, even with full permissions in the "root" directory -- the script resulted in the phone disconnecting from my computer in MTP mode, but it didn't connect in diagnostic mode. Terminal commands did the trick though -- I may be making some n00b mistake with the scripts. After typing the commands in manually and connecting to QPST, when I told QPST to "restore" the backup, it gave me an error message with incompatible phone, and if I checked the "allow phone/file ESN mismatch" box, the restore failed because the phone didn't respond to the QPST commands. I'm sure the phone was in diagnostic mode because it came up under Device Manager "ports" as depicted in the QPST instructions, so it seems like the corrupted NVRAM was causing problems with making a QPST connection.
Fourth try: TWRP update to 2.3.3.0. Same results as 2.3.1.0.
Fifth try: switch to clockworkmod touch recovery 6.0.2.3. Same result as both TWRP versions.
So, I'm pretty frustrated. I have the phone back up and running rooted-stock VRBLK3. I'd really like to get JB4.2 though, so if anyone can ID the problem, please post! I hope it's a simple fix from a n00b mistake, but after all the fruitless effort above, I expect that it's a more significant issue.
One last thought: I always rebooted into recovery to install the 10.1 image, and I never tried using the ClockworkMod ROM Manager or TWRP-compatible GooManager apps. My wife is tired of me spending the holiday weekend hunkered over my phone, so if anyone wants to try that route please let me know if it works.
The only other idea I have is to install 10.1, then try flashing the VRBLK3 baseband by itself. Again, I don't have the time to pursue this idea (or expertise to know if it's a good one), so any good insight would be appreciated. One last thought: personally, I'm not willing to wander around in voice or data "roaming" even if everything else is working fine. I rely on this phone for daily use, and am not comfortable without the radios working normally.
Happy new year!
thank you. can confrim this method to work for a verity of roms. ha.
vabeachfc3s said:
Flash cm10.1 go to settings/networks/cdma subscriptions and change it back to RUIM/SIM. U haz data now. :thumbup:
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This worked, just reboot the phone after you make this change and you'll have your activated phone back with voice/data. :good:
No Service
I flashed CM10.1-m a few days ago (using this method to root and unlock bootloader http://forum.xda-developers.com/show....php?t=2046439 then flashing CM10.1-m through Odin), and my phone worked flawlessly for 2 days. It started to lag a bit during swipe-style text entry (no tracing line or predictive words appeared), so I rebooted hoping to fix the problem.
After reboot I lost all verizon service. The phone said "No Signal" or "Emergency Calls Only." The phone would not identify a mobile network, and no option for CDMA/LTE was available under mobile network settings, although verizon APN's were still identified. I think I lost my IMEI/EFS but don't know enough to be sure.
First I flashed stock VRALG1 android 4.0.4 without success. However after I flashed stock VRBLK3 android 4.1.1 my verizon service was restored.
I would really like to figure out how to keep CM10.1... touchwhiz is awful. Can someone confirm this problem can be fixed through one of the following methods? http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2&nocache=1
Also don't want to trip my flash counter... any idea at what point this would happen?
NOTE: This is for the Verizon Wireless Samsung Galaxy S3 SCH-I535
Since I'm a new member I wasn't allowed to post this into the developers forum and before I continue: YES, I have searched valiantly for a fix to my particular problem and I spent the entire day new years and most of the day today trying to get CM10.1 to run on my SCH-I535 but ran into problem after problem. Every time I installed any version of CM10 or higher I ran into multiple problems: mainly being that I wasn't able to attain signal, the keyboard wouldn't load or there would be multiple problems with initial setup including having to restart during install so many times I gave up. In the past two days I have Odined back to stock at least 15+ times trying to get CM to run and now that it finally is I believe this is worth sharing.
Before I continue I should mention that your phone should be properly working so if you're in stock and you can't make phone calls or your IMEI is messed up then none of what I'm about to mention is going to work. After you Odin to stock using Root66.tar (http://www.megashare.com/4384479) then type *2767*3855# to reset to factory defaults everything should be running correctly. If not you may have bricked your phone or you have bigger problems for which I cannot help you and I apologize. There's also a torrent file available of the above stock tar file that downloads much faster here: http://forum.xda-developers.com/showthread.php?t=1840030.
So I assume, before I start this, that if you're on these boards you know how to properly root, unlock and flash then recover your phone through CWM 6+. If you do not know how to do this, then you will need to before continuing on.
Use this link: http://forum.xda-developers.com/showthread.php?t=1762709
Now follow Section 1 and pay attention to detail because if you don't you can mess something up and end up having to backtrack which can take valuable time and be amazingly frustrating.
Once these things are done you will need to reboot your phone back out of Recovery mode so you can properly move the necessary zip files onto your internal SD card.
Download CM10 Stable, you can find this here: http://get.cm/?device=d2vzw&type=stable
And download Gapps 4.2.1 here: http://www.teamandroid.com/gapps/ (I used version gapps-jb-20121212-signed.zip)
Put these files on your internal SD card and use EZ Recovery to Flash and then Reboot Recovery, I need to mention as well that when I dragged both of these zip files onto my internal SD I had EZ Recovery open while doing so. I don't know if that had anything to do with it but I thought it was worth mentioning. Clear the cache and data/factory reset then install CM10 followed by Gapps that you installed on the SD earlier.
Once you boot up you should have the phone working but the keyboard will constantly flash a message that it can't run, don't worry about that right now. Now download a nightly version of CM10.1 located here:http://get.cm/?device=d2vzw&type=nightly
(I used cm-10.1-20121231-NIGHTLY-d2vzw.zip)
Now put this on your internal SD card as well and hold the power button for 2 seconds and press restart then select recovery. Now that you're back into the recovery menu CLEAR ONLY CACHE then install the new CM10.1 nightly you just put on your internal SD and then re-install Gapps 4.2.1 from before and reboot. This all worked for me and writing this message is the first thing I wanted to do afterward to make sure no one has to go through the frustration and heartache of constantly failing at installing the ROM they want. I hope this helps at least one person, if you have any questions I will try and answer them to the best of my knowledge but I'm fairly new to all of this.
Or you can just flash CM10.1 first and do this.......
Tap the 4 corners of the screen to bypass activation screen then go into settings> more> mobile networks> and change CDMA Subscription to RUIM/SIM and System Select to Automatic then reboot...
Click to expand...
Click to collapse
Dirty flashing CM10.1 over CM10 is a much longer way then just clicking a couple buttons Its simply the fact that CM10.1 doesnt have the correct cdma subscription on default boot for our phone.
x714x said:
Or you can just flash CM10.1 first and do this.......
Dirty flashing CM10.1 over CM10 is a much longer way then just clicking a couple buttons Its simply the fact that CM10.1 doesnt have the correct cdma subscription on default boot for our phone.
Click to expand...
Click to collapse
I have everything working properly now but I wish I would've known this was the matter that would've fixed my problem without all these extra issues. Now my phone app is crashing in the 12-31-12 version of CM10.1. It just suddenly started happening and I can't seem to get around it.
Bosli said:
I have everything working properly now but I wish I would've known this was the matter that would've fixed my problem without all these extra issues. Now my phone app is crashing in the 12-31-12 version of CM10.1. It just suddenly started happening and I can't seem to get around it.
Click to expand...
Click to collapse
Clear it's cache APPS > ALL > PHONE APP > Clear Cache.
x714x said:
Or you can just flash CM10.1 first and do this.......
Dirty flashing CM10.1 over CM10 is a much longer way then just clicking a couple buttons Its simply the fact that CM10.1 doesnt have the correct cdma subscription on default boot for our phone.
Click to expand...
Click to collapse
What are the correct settings?
I have been doing this a while... and I was already on the 10.0 stable build. So I flashed the 10.1 nightly... Now Play Store closes immediately after opening. I have tried to uninstall and install from .apk without success. CWRM opens and closes immediately , also uninstalled and reinstalled from .apk without success (You can get to it from booting to it with the phone off ). My Gmail app and account nowhere to be found. My attempt to go back to 10.0 were unsuccessful.
Hello ladies and gents,
I purchased my girl an s3 and she has been running stock rooted for a while and wanted to try something different so I flashed cm10.1. I factory reset, cleared system, and caches. Then flashed the rom via trwrp 2.3.3 flashed gaps. Everything went successful but she lost all data. I read that it was fixed but I had to Odin root66 and dial that code to do another reset.
What can I do differently that won't lose data next time? The Verizon s3 seems more temperamental than my T-Mobile s3.
Sent from my SGH-T999 using Tapatalk 2
First thing to always do is read the OP for bugs I'm pretty sure he explained the loss of data and how to fix it.
Second would be to research the ROM you are flashing by reading comments from other flashers.
Last would be waiting for a stable version of the ROM to be uploaded.
Have fun and flash with the speed of light
But the things is I did all of those things. I am no stranger to rooting and crack flashing. I'm saying they said the data bug was fixed as of 12/24, I flashed 1/19 and it still broke data. But I guess I'll just lurk the thread... my bad for asking a question in the q/a forum...
Sent from my SGH-T999 using Tapatalk 2
Here's all the info I: have saved in case I come across this problem (again)
Fixing Data
If you flashed a CM10.1 nightly and are stuck at roaming/activating or don't have data, try any of the following (in order of simplicity):
(1) Go into Mobile Settings - Mobile Networks. Change CDMA mode to RUIM, go into airplane mode, come out, it should login to 4g in a minute. You can wait for activating to time out then skip or not install gapps until after setting the correct mobile network setting.
(2) Power down. Take out the sim card and reboot. In mobile network settings set roaming to auto and the subscription to RUIM/SIM, turn off the phone, pop the sim card back in, boot up.
If none of those work this will work for sure:
Originally Posted by Deevious88
Hallelujah! My phone has voice AND data back! (thanks to the posters above)
How to get voice AND data back:
1.) Odin the root66.tar file from http://forum.xda-developers.com/show....php?t=1762204 (the torrent version downloads MUCH faster)
2.) Open the dialer and enter *2767*3855#
3.) DONE! Voice and data should be fixed (it fixed it for me at least, and I had tried EVERYTHING else)
From there just Odin back to Jellybean following http://forum.xda-developers.com/show....php?t=1974114 and you're golden...
That's how to get back to working condition without fail... Might want to post similar instructions in the OP as dirty flashing did nothing for quite a few of us.
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Fixing GPS
Originally Posted by invisiblek
GPS - it HAS been working for 98% of builds, however if you cannot get GPS to connect, possibly due to dirty flashing, the following has worked every build for me: Settings - Apps - downloaded - GPS Status - clear cache, clear data, force stop. Then open gps status back up, let it sit with gps on for a moment and see if it starts searching for signal again....if this still doesn't work (sometimes) - settings - apps - all - google services framework - clear data. This has worked 100% of the time but I try to avoid it because if you do this, you need to go open back up the play store and see if it still connects. If not, recovery - clear cache, clear dalvik usually takes care of that.
Clean install of builds has given me 100% functional gps every time.
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Unofficial CM10.1
(I know several people have posted these, I looked quickly and only found mastamoon's which is also what I am running, I'll happily post more here if I find them).
mastamoon http://d-h.st/users/mastamoon
invisiblek http://rootzwiki.com/topic/35602-rom...0#entry1058210
aerovan http://rootzwiki.com/topic/37216-uno...zw-2012-12-18/
First do this: change your CDMA Subscription to RUIM/SIM then your Roaming Mode to Automatic and then reboot.
If doesn't work, try: restoring IMEI and then Odin back to stock.
The RUIM method mentioned prior has always been what fixed my problem when experiencing the same issue as you. Also, definitely back up your IMEI if you have not yet.
Can someone please instruct me how to get GPS up and running again? I am on latest nightly and have tried various past builds. I installed the new modern, I have cleared the cache several times, dalvik and otherwise. I have even factory resetted several times. I use GPS allot because I work for FedEx. Any help would be greatly appreciated.
Sent from my SGH-T699 using xda premium
chuckiev79 said:
Can someone please instruct me how to get GPS up and running again? I am on latest nightly and have tried various past builds. I installed the new modern, I have cleared the cache several times, dalvik and otherwise. I have even factory resetted several times. I use GPS allot because I work for FedEx. Any help would be greatly appreciated.
Sent from my SGH-T699 using xda premium
Click to expand...
Click to collapse
same here.
nardholio asked to pm him if one has this issue. i did some hours ago. when i have an reply i'll pm you. or publish it here (whatever is applicable).
Thanks man !!!!
Sent from my SGH-T699 using xda premium
I hope this will work for you. This worked for me. I don't pretend to understand all the details of what went wrong, but from what I understand there's a non-volatile (ie factory reset, reboot, etc won't fix it) privacy setting on the GPS which, when activated, basically breaks GPS. Samsung must have realized this was stupid too because the latest stock rom/modem doesn't mess with this setting anymore. Unfortunately, if it was set before you upgraded to the newest modem, that means your GPS is stuck in privacy, aka non-working mode (stupid because if you didn't want GPS you should just turn it off).
So what you need to do is backtrack to a combination of software that DOES mess with this setting. Once you are SURE GPS is working again, you can consider flashing the new stuff again (you may have to try more than once because there is absolutely no user control of the privacy setting, another stupidity in the system).
So
1. Flash either an older stock image (newer stock image contains the same privacy bug so you can't use that) or older cyanogenmod and modem. For stock, I recommend the original firmware released with the phone https://dl.dropboxusercontent.com/u/103520801/T699UVALH1_T699TMBALH1_T699UVALH1_HOME.tar.rar
That is what fixed mine
You can try the following version of cyanogenmod + modem
http://goo.im/devs/nardholio/apexqtmo/cm-10.1-20130309-UNOFFICIAL-apexqtmo.zip
https://dl.dropboxusercontent.com/u/103520801/RelayLJ1modem.zip
2. Do a battery pull and wait a minute. Just to clear out anything that might be lingering.
3. Obtain a solid GPS fix. Install GPS Status and stand outside. If GPS doesn't come back at this point try the other route (cyanogenmod or stock)
4. Turn off GPS.
5. Battery pull, do not power off
6. Flash forward to cyanogenmod (build 111 or higher)/newer modem. You can try restoring your nandroid (at this point mine worked with a restored nandroid) but if GPS goes away again try with a fresh install.
7. If you obtained GPS on stock but cannot get GPS going in cyanogenmod try repeating again but replace step 4 with "do battery pull while you have a solid gps fix"
Thanks nardholio! It worked like a charm. Any chance we will ever see photosphere? If not it's no big deal. Just curious.
Sent from my SGH-T699 using xda premium
thanks nardholio
will try that when i get back from work...
Thanks for this tip Nard.
I did this.
1) Created a nandroid of my full wiped build 111 install/setup
2) full wipe install of 20130309 build
Got GPS to lock.
Turned GPS off.
Battery Pull.
3) Without wipe, nandroid restore of 111 build.
Reboot, GPS works.
Thanks again :thumbup:
Sent from my SGH-T699 using xda app-developers app
took the files on the road with me and worked like a charm.. did:
-backup
-format data/system/cache
-install radio and cm provided by nardholio
-boot and installed a gps status.apk off the web since i was too lazy to setup my google account ^^
-INSTANT gps lock. kept it running a lil, then restarted the phone with gps still enabled.
-format data/system/cache
-restored backup
==> works like a charm
thx again
Sent from my SGH-T699 using xda app-developers app
Sweet that fixed it right up. I did these steps, in this order:
1. Nandroid backup from CWM
2. (From CWM) Factroy reset and cleared cache, then flashed this file(rom): http://goo.im/devs/nardholio/apexqtm...L-apexqtmo.zip followed immeditatly by this one (cell radio) https://dl.dropboxusercontent.com/u/...ayLJ1modem.zip
3. Booted into cyanogenmod.
4. Downloaded and installed a recent googlemaps.apk
5. (Switched off wifi) Obtained a solid GPS fix
6. Turn off GPS.
7. Did a battery pull, did not power off just pulled the battery..waited 1 min and put the battery back in.
8. Booted into CWM recovery (by presssing Home, Volume Up and Power) and flashed the nightly build #137, immedetally flashed the MC5 Modem from this thread, and then after that finished immediately restored my nandroid backup.
GPS is working and my phone is still setup like it was an hour ago. PERFECT!
Thanks Nardholio :highfive:
though the reason was me misreading when i applied the fix, but i kept GPS ON. which actually - from a logic pov - is the thing that makes sense to me.
and it worked fine.
all you others switch it off once you've gotten a good gps fix.
and it works fine as well.
but it really raises the question what the real issue behind this problem is..
No "real reason" mr conspiracy theorist. Cycling the setting after getting a GPS fix makes sure its set the right way when you upgrade to the newest rom. Otherwise you don't know what state the chip has been left in
Sent from my SGH-T699 using xda premium
which makes it russian gps roulette
i guess, whatever works...
When you guys are saying GPS is broken - do you mean it doesn't work at all, or just takes a while to get a fix? Mine is slow to lock and the compass is off kilter, but eventually it will lock.
nah, it never locked. he just kept on searching for satelites forever.
The first lock after i went back to the latest build took a little but after that fft was like 5 seconds. and still is.
MIA on all files
Hi,
All of the original firmware files seem to be MIA. Does anyone have an alternative link to the original modem?
Thanks
BRad Barnett said:
Hi,
All of the original firmware files seem to be MIA. Does anyone have an alternative link to the original modem?
Thanks
Click to expand...
Click to collapse
Found it here...
http://forum.xda-developers.com/showpost.php?p=35147531&postcount=691
Nardholio said:
I hope this will work for you. This worked for me. I don't pretend to understand all the details of what went wrong, but from what I understand there's a non-volatile (ie factory reset, reboot, etc won't fix it) privacy setting on the GPS which, when activated, basically breaks GPS. Samsung must have realized this was stupid too because the latest stock rom/modem doesn't mess with this setting anymore. Unfortunately, if it was set before you upgraded to the newest modem, that means your GPS is stuck in privacy, aka non-working mode (stupid because if you didn't want GPS you should just turn it off).
So what you need to do is backtrack to a combination of software that DOES mess with this setting. Once you are SURE GPS is working again, you can consider flashing the new stuff again (you may have to try more than once because there is absolutely no user control of the privacy setting, another stupidity in the system).
So
1. Flash either an older stock image (newer stock image contains the same privacy bug so you can't use that) or older cyanogenmod and modem. For stock, I recommend the original firmware released with the phone https://dl.dropboxusercontent.com/u/103520801/T699UVALH1_T699TMBALH1_T699UVALH1_HOME.tar.rar
That is what fixed mine
You can try the following version of cyanogenmod + modem
http://goo.im/devs/nardholio/apexqtmo/cm-10.1-20130309-UNOFFICIAL-apexqtmo.zip
https://dl.dropboxusercontent.com/u/103520801/RelayLJ1modem.zip
2. Do a battery pull and wait a minute. Just to clear out anything that might be lingering.
3. Obtain a solid GPS fix. Install GPS Status and stand outside. If GPS doesn't come back at this point try the other route (cyanogenmod or stock)
4. Turn off GPS.
5. Battery pull, do not power off
6. Flash forward to cyanogenmod (build 111 or higher)/newer modem. You can try restoring your nandroid (at this point mine worked with a restored nandroid) but if GPS goes away again try with a fresh install.
7. If you obtained GPS on stock but cannot get GPS going in cyanogenmod try repeating again but replace step 4 with "do battery pull while you have a solid gps fix"
Click to expand...
Click to collapse
Worked perfectly.
1. Backup CM11.
2. Wipe all partitions.
3. Flash CM10.1 and Modem.
4 Pull battery.
5 Boot CM and install Google Maps
6. Set GPS to device only and open G Maps
7. GPS WORKS!
8. Reboot to recovery (forgot to disable gps)
9. Wipe partitions and restore CM11 backup
10. GPS WORKS!
I am however on baseband T699UVLJ1 and I believe T699UVBMC5 is the latest one.
All seems to be working so I will leave it like this for a day and then update and test GPS again.
Flashed to the latest baseband again without any problems so far
Nardholio said:
I hope this will work for you. This worked for me. I don't pretend to understand all the details of what went wrong, but from what I understand there's a non-volatile (ie factory reset, reboot, etc won't fix it) privacy setting on the GPS which, when activated, basically breaks GPS. Samsung must have realized this was stupid too because the latest stock rom/modem doesn't mess with this setting anymore. Unfortunately, if it was set before you upgraded to the newest modem, that means your GPS is stuck in privacy, aka non-working mode (stupid because if you didn't want GPS you should just turn it off).
Click to expand...
Click to collapse
After I managed to bollix up my GPS, I went through the steps with CM (the link to the stock rom is 404). I flashed the 10.1 gapps as well, and I used GPS Status instead of Maps, but I did manage to get GPS working again after restoring my backup. Thanks a bunch!
I must say, my Avant has a vastly better GPS than the Relay, but (for now) the Avant is completely stock/unrooted.
Nardholio said:
So what you need to do is backtrack to a combination of software that DOES mess with this setting. Once you are SURE GPS is working again, you can consider flashing the new stuff again (you may have to try more than once because there is absolutely no user control of the privacy setting, another stupidity in the system).
Click to expand...
Click to collapse
And why does it not work with a CM11 image?
I cannot find any CM10.1 image, links are dead! :/
----
Right, going back to CM10.2.1 and after that back to CM11 also worked.
Phone never booted in CM10.2.1 by the way... CM boot circle was going round and round for 15 minutes... Removed battery, tried to boot again, same thing. Went into recovery mode, luckily I still had a CM11 ROM zip on my phone. Installed it and works! Some Trebuchet error message popping up though and Google Play services crashing all the time.. Hmm we will see what can be done about that. Maybe because I used a July nightly.
Need help
I need serious help to fix my GPS. I want to follow the steps, but all the links are dead. So I have no idea how to obtain 10.1 or original stock firmware to fix gps.
Anyone can help with the files?