• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root GPS stopped working

Tank2211

Tank2211

Well-Known Member
I flashed back to stock after I noticed the issue. Tried using GPS in stock and nothing. I flashed over to CTmod 3.3 to test it and its still not working. Any ideas on what to try before I call up Samsung and send it to them to fix?
 
Have you tried using Odin yet to install just a rooted version of either EJ06 or FA19 ? I would try that first .
 
yes I have... the only thing I havnt done yet is gone back to completely stock ( unrooted ) I dont know what else to do.
 
Bro , if you've used Odin to take it all the way back , I don't know what else to tell you . Doesn't look good man . May be hardware failure .
 
Damn... yea I was thinking the same thing. Well since this is my only way to get on the net I won't be around for a bit ( how long it takes them to get my phone back to me ) I'm so mad right now -__-
 
Not really sure Tank . I think it takes a couple of weeks but I may be wrong . Remember to Odin that sucker back to stock . Holla at me when ya get it back .
 
No doubt. I just have to find the thread and get the download. they said it takes 6 days total but somehow I doubt thats the case
 
When i sent them a phone it took 11 days from the day i shipped it out
(Michigan to Plano, TX. They use UPS ground)
 
Ah okay... im in NW Indiana so im sure it will be about the same. This sucks... I dont want to go that long without a phone and internet. -_- I know stuff happens but my money is on it failing due to how hot these lil time bombs get. They should have figured out someway to void that out before releasing them. But thats just my opinion. Pay damn near 200 and have to send them in within the year. At least they fly it and fix it free of charge. UUUUUGGGHHHH is all I can say right now.
 
Tank2211 said:
I flashed back to stock after I noticed the issue. Tried using GPS in stock and nothing. I flashed over to CTmod 3.3 to test it and its still not working. Any ideas on what to try before I call up Samsung and send it to them to fix?
Click to expand...


Just a quick note. I also odin to FA19 fresh installed CTMOD 3.3 and KK 2.2. When I got into the system I realized my GPS stopped working. I found that quite odd so I continued to search for what could be causing it.

I odin'ed again and reinstalled CTMOD 3.3 and KK 2.2. The GPS wasn't working again.

Finally I gave up and loaded CM7 and my GPS started working. Seems to me that CTMOD may have an issue with GPS on some phones. It could be a glitch. I'll let bloodawn know.
 
Xruptor said:
Just a quick note. I also odin to FA19 fresh installed CTMOD 3.3 and KK 2.2. When I got into the system I realized my GPS stopped working. I found that quite odd so I continued to search for what could be causing it.

I odin'ed again and reinstalled CTMOD 3.3 and KK 2.2. The GPS wasn't working again.

Finally I gave up and loaded CM7 and my GPS started working. Seems to me that CTMOD may have an issue with GPS on some phones. It could be a glitch. I'll let bloodawn know.
Click to expand...

I'm on EJ06 and CTmod 3.3 w/ KK2.2 and GPS works fine for me.
try switching basebands, It probably wont help, but it's something to try before giving your phone up for a repair cycle
 
Koumajutsu said:
I'm on EJ06 and CTmod 3.3 w/ KK2.2 and GPS works fine for me.
try switching basebands, It probably wont help, but it's something to try before giving your phone up for a repair cycle
Click to expand...

Oh I'm not going to turn in my phone. Just wanted to let the OP know that I encountered the same issue when I went from FA19 -> CTMOD 3.3 -> KK 2.2.

Do you really think it may be an issue with the baseband? I just find it unusual really since it works fine with STOCK and CM7. I'll stick to CM7 for now till I can figure out what is happening.
 
Xruptor said:
Oh I'm not going to turn in my phone. Just wanted to let the OP know that I encountered the same issue when I went from FA19 -> CTMOD 3.3 -> KK 2.2.

Do you really think it may be an issue with the baseband? I just find it unusual really since it works fine with STOCK and CM7. I'll stick to CM7 for now till I can figure out what is happening.
Click to expand...

Well, it works with other setups for you, and the only thing that seemed different from your CTmod 3.3 than mine is the baseband.

ergo, "when you have eliminated the impossible, whatever remains, however improbable, must be the truth"
 
Koumajutsu said:
Well, it works with other setups for you, and the only thing that seemed different from your CTmod 3.3 than mine is the baseband.

ergo, "when you have eliminated the impossible, whatever remains, however improbable, must be the truth"
Click to expand...


You reminded me of Spok when he said that line to Jim Kirk.... on several occasions.
 
Koumajutsu said:
Well, it works with other setups for you, and the only thing that seemed different from your CTmod 3.3 than mine is the baseband.

ergo, "when you have eliminated the impossible, whatever remains, however improbable, must be the truth"
Click to expand...


I have the same problem, same symptoms. I tried re-flashing everything today, this time FA19 w/ EJ06 baseband, no joy :(
 
Okay guys I'm back. I took a few days to play with the phone. I went back to straight stockfor about a day. Not sure what happened but it started working again so I'm happy
 
Glad ya got it working again Tank . Sounds like you may have lost or corrupted a driver somewhere . Just a guess though . :D
 
Who knows lol. Im just glad I dont have to send it in to them. I soooooo wasnt looking forward to being without a phone -.-
 
wetbiker7 said:
Glad ya got it working again Tank . Sounds like you may have lost or corrupted a driver somewhere . Just a guess though . :D
Click to expand...


It seems to be an issue with FA19 and CTMOD 3.3. I've tried it a few times and I still get the same problem GPS stops working.

lol I give up ;) I'm just going to stay with CM7.
 
I have been following your posts for a couple days Xruptor because I was having the same issue. It turns out the problem is in the Kernel and Kouma released an unnofficial version of 2.3 which you can find in the KoumaKernel thread you posted on earlier, post #646. The fix finally worked for me and I'm using the /data option, not the ssm. It even seems to have sped up my lock on time as well!
 
You must log in or register to reply here.
Back
Top Bottom