So I just recently upgraded from MF3 with root and safestrap to MK2, also root and ss as the title suggests. The process went smoothly, even got myself a shiny new shostock installed painlessly. Today I went to use my navigation and came to the realization that my gps will not lock on, just endless waiting for location. My first thought was to get a baseline on the rom, so I swapped to my stock slot still with stock rom and was having the same issue, endless waiting for loc.
So I have done a lot of searching around, tried a few gps fix apps, to no avail. Has anyone else run into the same issue or possibly have some advice to offer me? Everything else works just fine, lte, wifi etc, just the dang gps! Thanks in advance everyone!
I'm having the same issue.. I unrooted and disabled/uninstalled safestrap with no luck. I even had AT&T reflash mk2 for me, but still no GPS locking on. Anyone help?
Try using this app.
https://play.google.com/store/apps/details?id=com.Double.FasterFix
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
Same thing happened to me. Just installed the MDL modem and worked again right away :thumbup:
Sent from my SGH-I337 using Tapatalk 2
Same issue here - see my thread at http://forum.xda-developers.com/showthread.php?t=2599961 (with 0 replies).
I will try restoring shostock and flashing the MDL modem.
UPDATE: Booted back to stock and GPS now working, without flashing a new modem! Restored ShoStock nandroiid, and GPS working there also! No idea why.
I finally found the problem, in hyperdrive there is an option to choose your region for faster gps locks. I went in, saw it was set to asia, changed it to north america, then deleted hyperdrive so I could have more space for shostock and my gps is now working flawlessly.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
TBayTom said:
I'm having the same issue.. I unrooted and disabled/uninstalled safestrap with no luck. I even had AT&T reflash mk2 for me, but still no GPS locking on. Anyone help?
Click to expand...
Click to collapse
Same with me: I've reflashed with leaked KK, than back to stock MK2, installed several modems: nothing, GPS would not lock and no satellites are found.
mess18 said:
Same with me: I've reflashed with leaked KK, than back to stock MK2, installed several modems: nothing, GPS would not lock and no satellites are found.
Click to expand...
Click to collapse
The same happened with me on my MK2 SS with GoldenEye rom. I tried everything and nothing would work. I flashed several modems, booted in stock rom, restored MK2 with odin, factory reset multiple times, tightened the screws on the frame of the phone, and nothing worked..
My only solution was to Odin to MK2, upgrade to KK via the OTA update from AT&T. And from there, reflash stock 4.4 image with Odin. After all that, my GPS is finally working again.
Oh when I went from MK2 to NBA with AT&T OTA, my wifi stopped working, so if that happens just restore with the KK stock image in Odin. I even had scheduled a repair with Samsung, but I guess I wont be sending it in anymore.
To anyone having problems, this is what I had to do to fix it. I need my GPS working, so I didnt really care about upgrading from MK2 to NB1, besides I am sure a root method will be out within weeks. (or you can do the downgrade method)
trillog said:
The same happened with me on my MK2 SS with GoldenEye rom. I tried everything and nothing would work. I flashed several modems, booted in stock rom, restored MK2 with odin, factory reset multiple times, tightened the screws on the frame of the phone, and nothing worked..
My only solution was to Odin to MK2, upgrade to KK via the OTA update from AT&T. And from there, reflash stock 4.4 image with Odin. After all that, my GPS is finally working again.
Oh when I went from MK2 to NBA with AT&T OTA, my wifi stopped working, so if that happens just restore with the KK stock image in Odin. I even had scheduled a repair with Samsung, but I guess I wont be sending it in anymore.
To anyone having problems, this is what I had to do to fix it. I need my GPS working, so I didnt really care about upgrading from MK2 to NB1, besides I am sure a root method will be out within weeks. (or you can do the downgrade method)
Click to expand...
Click to collapse
So, actually I have solved the problem. Please read my long story in the post #2050 here: http://forum.xda-developers.com/showthread.php?t=2305752&page=205.
It also should solve Wi-Fi problem as well as I had it too in between...
Related
Hi guys. I bought an S4 I9505 Yesterday. Got it home, and set straight to setting up a custom rom and recovery etc. I tried to Omega 4.3 V2 first. But it ended up getting stuck in a Boot loop..Then i tried Omega 4.2 V11. That worked fine with no Sound from speakers etc. I have no idea how to sort it out. I wiped the phone, cache and Dalvic cache before and after install etc. But still no sound.
Tried to install a stock firmware and start again, but unfortunatly the stock firmware that was on the phone when i bought it was I9505XXUDMH8 with the No downgrade bootloader. When i try to flash back to the original firmware now, theres no Wifi or no sound...so its even worse than the omega flash. I have tried everything i can think off and im at a loss..
Any help is appreciated.
Jamie.D said:
Hi guys. I bought an S4 I9505 Yesterday. Got it home, and set straight to setting up a custom rom and recovery etc. I tried to Omega 4.3 V2 first. But it ended up getting stuck in a Boot loop..Then i tried Omega 4.2 V11. That worked fine with no Sound from speakers etc. I have no idea how to sort it out. I wiped the phone, cache and Dalvic cache before and after install etc. But still no sound.
Tried to install a stock firmware and start again, but unfortunatly the stock firmware that was on the phone when i bought it was I9505XXUDMH8 with the No downgrade bootloader. When i try to flash back to the original firmware now, theres no Wifi or no sound...so its even worse than the omega flash. I have tried everything i can think off and im at a loss..
Any help is appreciated.
Click to expand...
Click to collapse
re-flash the MH8 stock firmware (untick "auto-reboot" when it pass, pull battery, insert it, boot into recovery,wipe data and cache, reboot)
if it didnt fix, flash MH8 modem twice http://d-h.st/UcW before flashing the stock, wipe, reboot.
Sorted now. Thanks for the reply. After downloading loads of different firmwares, i downloaded an Odexed MH8 pre-rooted rom and flashed that. Finally everything works. Massive relief all round.
Jamie.D said:
Sorted now. Thanks for the reply. After downloading loads of different firmwares, i downloaded an Odexed MH8 pre-rooted rom and flashed that. Finally everything works. Massive relief all round.
Click to expand...
Click to collapse
Which rom did you download.i am in the same damn position as you were. Share the link please
//olme
me too
Jamie.D said:
Sorted now. Thanks for the reply. After downloading loads of different firmwares, i downloaded an Odexed MH8 pre-rooted rom and flashed that. Finally everything works. Massive relief all round.
Click to expand...
Click to collapse
me too,I wll try download MH8 pre-rooted
Same thing !
Hey guys, after i flashed a new 4.3 Android version Rom, i realised i lost sound and Wifi, i tried to flash back the stock custom ROM ( SAMMOBILE frimware ) , the problem persist... PLEASE HELP !
i was in the same position as you and fixed it litterally 10 mins ago, download and flash this through odin http://forum.xda-developers.com/showthread.php?t=2250824
http://www.hotfile.com/dl/250965162/033166a/I9505XXUEMJ5_I9505OXAEMJ5_DBT.zip.html < pre rooted stock rom that fixed the problem for me.
---------- Post added at 09:11 AM ---------- Previous post was at 09:03 AM ----------
i was in the same position as you and fixed it litterally 10 mins ago, download and flash this through odin http://forum.xda-developers.com/showthread.php?t=2250824
http://www.hotfile.com/dl/250965162/033166a/I9505XXUEMJ5_I9505OXAEMJ5_DBT.zip.html < pre rooted stock rom that fixed the problem for me.
I had used cm 10.1 for a year and one day I decided to flash slimbean 4.3 weekly 1.4. So I downloaded bootloader Z20i.zip and radio .84.zip and flashed via TWRP 2.6.3.0 and then wiped everything, flashed rom then gapps. I used the original kernel of rom. Everything seem to be fine and flawless. but one day my phone hanged and rebooted itself stucked at bootanimation. I tried to restart many times and it didnt success. So I decided to download factory image JWR66Y from google and run flash-all.bat via fastboot mode and then flash superSU via TWRP. Yeah..bootloop was gone. I used stock JWR66Y rom and kernel with root for a while and it happened again. One day my phone hanged and rebooted itself stucked at X animation. I tried to Wipe cache, davik, factory reset but it didnot success. So I tried to install cm10.2, PA3.99 (I have had installation zip file in my phone storage.) but it didnot sucess too. So I decided to flash stock Stock 4.2.2 JDQ39 image from google. thanks God my phone resurrected. But I dont want 4.2.2 anymore. I decide to try again with 4.3 stock JWR66Y. It happened bootloop same as above I described again. I have no idea anymore but I tried flash radio.48 via fastboot and finally my phone can use normally. Bootloop was gone away. Now I use Slimbean 4.3 weekly 1.6 original kernel with bootloader z20i and radio .48 without any bootloop.
So I think the problem for me is why radio .84 make my phone got bootloop.
Sent from my Nexus 4 using xda app-developers app
quirell said:
I had used cm 10.1 for a year and one day I decided to flash slimbean 4.3 weekly 1.4. So I downloaded bootloader Z20i.zip and radio .84.zip and flashed via TWRP 2.6.3.0 and then wiped everything, flashed rom then gapps. I used the original kernel of rom. Everything seem to be fine and flawless. but one day my phone hanged and rebooted itself stucked at bootanimation. I tried to restart many times and it didnt success. So I decided to download factory image JWR66Y from google and run flash-all.bat via fastboot mode and then flash superSU via TWRP. Yeah..bootloop was gone. I used stock JWR66Y rom and kernel with root for a while and it happened again. One day my phone hanged and rebooted itself stucked at X animation. I tried to Wipe cache, davik, factory reset but it didnot success. So I tried to install cm10.2, PA3.99 (I have had installation zip file in my phone storage.) but it didnot sucess too. So I decided to flash stock Stock 4.2.2 JDQ39 image from google. thanks God my phone resurrected. But I dont want 4.2.2 anymore. I decide to try again with 4.3 stock JWR66Y. It happened bootloop same as above I described again. I have no idea anymore but I tried flash radio.48 via fastboot and finally my phone can use normally. Bootloop was gone away. Now I use Slimbean 4.3 weekly 1.6 original kernel with bootloader z20i and radio .48 without any bootloop.
So I think the problem for me is why radio .84 make my phone got bootloop.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have the same exact problem! :crying:
Cannot update beyond 4.2.2. I have tried all the things that you seem to have tried but with absolutely no luck. And since there aren't many people with this problem, nobody has come up with a solution. It is extremely frustrating to see everyone else updating to to the latest firmware while we have to make do with the ancient 4.2.2
If anybody can think of anything which might help, please go ahead and share.(Cannot return the phone back to Google as I got it from another country)
Rekursion said:
I have the same exact problem! :crying:
Cannot update beyond 4.2.2. I have tried all the things that you seem to have tried but with absolutely no luck. And since there aren't many people with this problem, nobody has come up with a solution. It is extremely frustrating to see everyone else updating to to the latest firmware while we have to make do with the ancient 4.2.2
If anybody can think of anything which might help, please go ahead and share.(Cannot return the phone back to Google as I got it from another country)
Click to expand...
Click to collapse
Hi,
I just fixed a Nexus 4 with broken screen and fastboot flashed the latest 4.4.2 official ROM but I was stuck in bootloop on the 4 circles.
Then I flashed the 4.2.2 version and everything worked until I accepted the the 4.3 update (official OTA) and the phone was bootlooping again.
Then I found your posts and downgraded the radio .84 to .48 and android 4.3 finally booted successfully.
BUT, when trying to upgrade to 4.4 (from 4.3 with official OTA), I'm stuck again! And downgrading radio .97 to .48 does not work anymore...
I've found nothing like a software fix until now. People facing the same issues are mostly getting some replacement devices. Given that I replaced the screen myself, I'm not certain that they would give me a new one.
Any feedback from someone having the same issue?
neoantho said:
Hi,
I just fixed a Nexus 4 with broken screen and fastboot flashed the latest 4.4.2 official ROM but I was stuck in bootloop on the 4 circles.
Then I flashed the 4.2.2 version and everything worked until I accepted the the 4.3 update (official OTA) and the phone was bootlooping again.
Then I found your posts and downgraded the radio .84 to .48 and android 4.3 finally booted successfully.
BUT, when trying to upgrade to 4.4 (from 4.3 with official OTA), I'm stuck again! And downgrading radio .97 to .48 does not work anymore...
I've found nothing like a software fix until now. People facing the same issues are mostly getting some replacement devices. Given that I replaced the screen myself, I'm not certain that they would give me a new one.
Any feedback from someone having the same issue?
Click to expand...
Click to collapse
Yes.., I am joining your club. I have a same problem. I flashed 4.4 & 4.4.2 .., almost all sources and ended with four circle boot loop. Then flashed 4.2.2 and it was success. Did you people managed to flash Kit Kat ? Please anyone help us.
Please try these links...dont know whether it helps...I sold my phone., cant try..
http://forum.xda-developers.com/showthread.php?t=2529450
http://forum.xda-developers.com/showthread.php?t=2347060
Hope it helps someone.
richie16171 said:
Yes.., I am joining your club. I have a same problem. I flashed 4.4 & 4.4.2 .., almost all sources and ended with four circle boot loop. Then flashed 4.2.2 and it was success. Did you people managed to flash Kit Kat ? Please anyone help us.
Click to expand...
Click to collapse
richie16171 said:
Please try these links...dont know whether it helps...I sold my phone., cant try..
http://forum.xda-developers.com/showthread.php?t=2529450
http://forum.xda-developers.com/showthread.php?t=2347060
Hope it helps someone.
Click to expand...
Click to collapse
Hi, yes I finally found out that my proximity sensor was only disconnected (I forgot to reconnect it properly after the screen replacement). Then I managed to update my phone.
Found answers on this thread : http://forum.xda-developers.com/showpost.php?p=49141665&postcount=75
Sorry that you had to sell it...
neoantho said:
Hi, yes I finally found out that my proximity sensor was only disconnected (I forgot to reconnect it properly after the screen replacement). Then I managed to update my phone.
Found answers on this thread : http://forum.xda-developers.com/showpost.php?p=49141665&postcount=75
Sorry that you had to sell it...
Click to expand...
Click to collapse
You mean to say.,,you could flash 4.3 and your only problem to update kit kat.., because of the proximity sensor?
richie16171 said:
You mean to say.,,you could flash 4.3 and your only problem to update kit kat.., because of the proximity sensor?
Click to expand...
Click to collapse
Well, I meant I could get 4.3 to work after downgrading the radio file (baseband) to its previous version, otherwise I was stuck in bootloop in 4.3 already.
But I couldn't do the same operation after flashing 4.4 : even downgrading the radio to a previous version didn't get 4.4 to work.
Once I reconnected the proximity sensor, I could use any radio and was able to update from 4.2 to 4.3 and 4.4 or directly flashing the latest.
You can use the Androsensors app to see if your light and proximity sensors are working properly, the displayed values should change all the time. If they are not changing or if there is no value displayed, it means that your sensors are not working properly
Alright, I have a Virgin Mobile S4. I rooted it a year ago with towelroot and installed clockwork mod on it to install cyanogenmod. I tried it, didn't like it so I restored my backup of the stock rom using CWM.
Fast forward to now. I tried to update my S4 OTA for Lollipop, but it would give me an error. I figured it was because I had changed the recovery software. So I went and downloaded the virgin mobile lollipop stock rom from sammobile. ( I337MVLUGOC4_I337MOYAGOC4_VMC ).
I tried to flash it onto my S4 using Odin 3.09. To no avail, it always failed at the system4.img.ext or something. From there I tried to make it work by using 3.10. Still failed. I googled for a fix or workaround and found something about reinstalling clockwork mod. I also tried reinstalling the PIT file for I337M. It was still not working. So I tried to flash back to my stock backup.
1st time I flashed, I kept having program that didn't want to start errors. I wiped dalvik, I wiped cache, I factory reset. Still bugged. So as a last resort I restored the backup again after having done all this. It worked! But...
Well, I'm at a lost now, I can't update using OTA, I can't update with Odin, I can't update with Kies. Now what? Is there a way to go back to the stock recovery and let the OTA or Kies update go through unhindered?
BTW, I had a problem when trying to use EFS professional to backup my EFS before the procedure. No matter which port I used ( front port or back motherboard port ), I could never make the backup, it said something about the phone currently being offline or something.
Anyway, I'd prefer to be able to switch back to the stock recovery and let the OTA or Kies do its thing. Any clues?
EDIT UPDATE: After fiddling some more around, I changed usb port again and reflashed using a more up to date version of Odin and I finally have Lollipop on my device, only problem is that I have no 3g or 4g connectivity even tho the IMEI, baseband and SMS as well as calls work just fine, what's wrong?
See first post edit^^
Diabo|ik said:
EDIT UPDATE: After fiddling some more around, I changed usb port again and reflashed using a more up to date version of Odin and I finally have Lollipop on my device, only problem is that I have no 3g or 4g connectivity even tho the IMEI, baseband and SMS as well as calls work just fine, what's wrong?
Click to expand...
Click to collapse
Did you check the APN settings? Make sure you have the right one for your carrier.
Ill start from the beginning att s4 running oc4 bad power switch i downgraded to nb1 flashed nc1 kernel and rooted towelroot installed safestrap flashed stock rooted nj4 then hyperdrive was running flawless except the power switch new one came in i soldered it in works great now home button dowsnt work so i figured it was software seeing as my menu and back works fine so i reflashed nb1 via odin and proceeded with my above root method but towelroot wont install says app not installed tried changing security level to normal was set to high but just goes back to high and home button still not working ive tried several stock flashes with and without pit file and stock updated via stock recovery just to try to get the app to install but still nogo any help or suggestions would be greatly appreciated
Not quite sure how or why but after 2 more stock nb1 flashes let me install rooted and safestrapped home button still not working though
Not sure what noob mistake I made here, but i can only flash CM based roms.
I unlocked the bootloader and loaded TWRP no problem. I've been running CM for months but wanted to try something else. I went with Resurrection Remix and realized i had no GPS. So i tried AICP, no GPS, Then Mokee, no GPS, then back to CM13 which worked before... No GPS! I saw threads saying to load rom based on stock and gps lock then reflash, so i tried but nothing else will boot!
g900v
Using twrp 3.0.2-2
No Boot.
Note5 Port
BS FREE
vzw stock something.. i already deleted this one and can't remember which it was now.
They all just bootloop.
What am i missing? Or if there is a gps fix i don't really care about loading non cm based roms, as thats likely what i'll go with in the end, but i need gps.
Flash a close to stock rom such as a rooted touchwiz rom in twrp
[email protected] said:
Flash a close to stock rom such as a rooted touchwiz rom in twrp
Click to expand...
Click to collapse
Thanks i tried a ton of stock based roms and nothing would load.
I tried to go back to stock on PD1 and that didnt work either. even after flashing kernel and stock rom through odin, it would lock on the verizon logo. no amount of factory resets or thread recommends helped. I ended up going to PB1 stock using odin and that fired right up after a pb1 kernel flash.
So i'm back at pb1 stock now, which is borderline unusable without root if nothing more than the constant dust cover notifications and update notifications that i can't seem to stop.
At least gps and everything works 100%. guess ill be following the pb1 root guide at some point soon. or maybe ill just do the ota to pd1, at least in 6.0 you can disable notifications on apps which would solve some of my issues..
Ok glad to hear you got it figured out
Sent from my SM-G900V using Tapatalk
I actually just ran into the same thing but I'd like to try and figure it out so I don't have to odin after updating ROMs. Hopefully my TWRP log attached. (Originally it was 9mb so I trimmed it down.)
This is my first time reading recovery logs but it looks like it's having an issue writing to some areas. I read on the net that someone had a similar issue due to encryption. I have never knowingly enabled encryption but i do use fingerprint lock. I tried removing that completely and testing again but get the same errors in the log. TWRP doesn't display any errors at time of flashing a TW ROM that I noticed.
Running latest TWRP 3.0.2.2 (i think that's it) using CM13. Tried multiple TW ROMs (and downloading) but other custom ROMs work fine.
Any thoughts?
Sent from my SM-G900V using Tapatalk
Sorry, I only now realized my logs never attached. Anyway, I was able to get it straightened out although I never determined the root cause.
I completely started over from scratch, odin to stock, root, unlock bootloader. I did continue to have issues flashing ROMs (including CM now) but finally resolved that by failing back to TWRP 3.0.0. Now I can flash Cam and TW ROMs again. I made a TW nandroid so if the GPS goes out again I should be able to easily do the CM->TW->CM trick.
I may have been firmware or partition corruption that CM just didn't care about but there may also have been related to TWRP > 3.0.0.
Sent from my SAMSUNG-SM-G900A using Tapatalk