Hi Guys!
First: I´m german, so my english is not so well, but i hope you can help me.
My navigation on my one m9 doesn´t work. I already installed GPS Test and Toolbox and it´s not getting a gps fix, but finds 23 sattelites.
I tried many different gps configs, still doesn´t work.
I also installed a different rom (viperone) --> no change --> went back to stock --> still no change
I have the newest firmware (3.35.401.12)
I hope you can help me
Thank you guys
Exact same problem. I've been trying to find a fix for months. Let me know if you work it out.
That.. Is a bug with android, phone side. reflash with an ruu to fix it. You need to reset all the gps software on the device.
Beamed in by telepathy.
shivadow said:
That.. Is a bug with android, phone side. reflash with an ruu to fix it. You need to reset all the gps software on the device.
Beamed in by telepathy.
Click to expand...
Click to collapse
So flashing the same ruu I already had will work? From here.
http://forum.xda-developers.com/one-m9/development/ota-1-32-401-15-firmware-noredtext-t3072571
shivadow said:
That.. Is a bug with android, phone side. reflash with an ruu to fix it. You need to reset all the gps software on the device.
Beamed in by telepathy.
Click to expand...
Click to collapse
Flashed ruu. Firmeware. Rom. Nothing fixed it.
Same here.
Tried every gps.conf configuration existing, nothing. GPS Never fixes.
Tried to swap SIM (I read some people saying that they solved this issue swapping between different sims), Nothing, GPS Never fixes.
I'm getting always:
SAT 0/8-20 SIG 0/infinite on GPS Status.
eljuls said:
Same here.
Tried every gps.conf configuration existing, nothing. GPS Never fixes.
Tried to swap SIM (I read some people saying that they solved this issue swapping between different sims), Nothing, GPS Never fixes.
I'm getting always:
SAT 0/8-20 SIG 0/infinite on GPS Status.
Click to expand...
Click to collapse
shivadow said:
That.. Is a bug with android, phone side. reflash with an ruu to fix it. You need to reset all the gps software on the device.
Beamed in by telepathy.
Click to expand...
Click to collapse
Flashed RUU with OPJAIMG.zip and changed the SIM --> Still no GPS Fix. I don´t understand why it finds 23 Sattelites but gets no fix
Any other Ideas? I think i´m going to send it to htc and hope they fix it without saying it´s my fault because of software changing
jens97 said:
Flashed RUU with OPJAIMG.zip and changed the SIM --> Still no GPS Fix. I don´t understand why it finds 23 Sattelites but gets no fix
Any other Ideas? I think i´m going to send it to htc and hope they fix it without saying it´s my fault because of software changing
Click to expand...
Click to collapse
I recently bought a new M9 EMEA version from Ebay. Had the exact same issue using factory ROM. Sent it back and got another, which works fine. I think it was a hardware defect.
Related
Hi All,
I am facing the dreaded 'No GSM' error and unable to flash radio rom problem.
tried to flash every possible rom including original O2 one. All failed on radio ram flash.
Went through various threads and there seems to be no solution yet for universal (though there seems to be a solution for Hermes).
So all, please help me if there is some light in the end of this tunnel
regards
Topgun
i have tried all the possible things but no luck so far.....
please help
I just bought a used XDA with this same problem. Thought if i flash it it would work... any suggestions on what I can do? i havent touched it yet. Thanks
has ANYONE been able to solve this problem?!!!! Pls what did u do step by step.... I spent so much money on this %&%$& Phone!!! pulllleeeessssss
I haven't had this problem, however it sounds like you phone may be SIM locked? If so, you will need to flash it with the native ROM from it;'s origin. If it is SIM and CID locked, it will only take the OEM signed ROM.
Quote from POF (Moderator)
"Not in 100% of the cases... there are some situations where the radio bootloader is intact, but the radio is screwed, this causes all bootloader commands that require radio seclevel to be queried to hang the device (like 'task 32' or 'info 2'), thus not being able to flash it with the usual RUUs.
If this happens, it can easily be fixed with hermflasher by flashing the raw radio without prior authenticating to bootloader."
If this is of any help. It is from a thread on CID Unlocking RUU for Uni
Thanks.
i have been through that thread.
well the question on that is 'Is hermflasher okay to flash Universal as well'?
Where is this thread? i can try it.... but cant find the thread on cid unlocking ruu for universal in mermes section....
raskell said:
I haven't had this problem, however it sounds like you phone may be SIM locked? If so, you will need to flash it with the native ROM from it;'s origin. If it is SIM and CID locked, it will only take the OEM signed ROM.
Quote from POF (Moderator)
"Not in 100% of the cases... there are some situations where the radio bootloader is intact, but the radio is screwed, this causes all bootloader commands that require radio seclevel to be queried to hang the device (like 'task 32' or 'info 2'), thus not being able to flash it with the usual RUUs.
If this happens, it can easily be fixed with hermflasher by flashing the raw radio without prior authenticating to bootloader."
If this is of any help. It is from a thread on CID Unlocking RUU for Uni
Click to expand...
Click to collapse
Here is the thread
http://forum.xda-developers.com/showthread.php?t=301662&highlight=radio+error
Let me know if you have any luck with this.
cheers
topgunarindam said:
http://forum.xda-developers.com/showthread.php?t=301662&highlight=radio+error
Let me know if you have any luck with this.
cheers
Click to expand...
Click to collapse
no, hermflasher wont work with universal (I dont think) ill consult with some others and report back here our consensus on what to try
I am facing the same 'No GSM' error in xda exec, plz can somebody tell me step by step how to solve it.
Thanks Midget
shall wait for your word.
Midget
topgunarindam said:
shall wait for your word.
Click to expand...
Click to collapse
I'm waiting too.
Good News at Last
atleast it worked for me.
flashed using a different pc with radio 1.18 and it worked.
the radio is working fine with laurentius26's WM6 rom.
atleast my brick comes live again.
LUCKY YOU!!!!!!!!
topgunarindam said:
atleast it worked for me.
flashed using a different pc with radio 1.18 and it worked.
the radio is working fine with laurentius26's WM6 rom.
atleast my brick comes live again.
Click to expand...
Click to collapse
lucky you, I tried that same WM6 ROM (with radio 1.18) and still same problem. I've tried falshing with 2 different desktops and a laptop. Still same problem! Topgun, did u have active sinc installed ? was the PC u used fresh? (no apps installed). do u think if i format my PC it could flash the radio? DID u flash radio only? or the whole laurentious v3 WM6 package (that is at the same time)?
Pls reply
Tbaba said:
lucky you, I tried that same WM6 ROM (with radio 1.18) and still same problem. I've tried falshing with 2 different desktops and a laptop. Still same problem! Topgun, did u have active sinc installed ? was the PC u used fresh? (no apps installed). do u think if i format my PC it could flash the radio? DID u flash radio only? or the whole laurentious v3 WM6 package (that is at the same time)?
Pls reply
Click to expand...
Click to collapse
Him
well it was a laptop dell to be precise.
it was never used for window mobile usage previously and hence fresh Active sync 4.5 was installed.
only radio rom 1st (using the RUU check bypassing)......
once succesful, then laurentiius rom was tried.
one more thing i had entered bootloader manually after disabling AS 4.5
i used the original USB cable as well
hope this helps....
suggest get hold of some friends "win mobile virgin" pc/laptop.
P.S>- i am not sure but this prob might be somewhat related to COM ports available on your machine.
For those of you who have NO GSM on boot (and I know there are a few). The solution could've been posted some time ago, but might be too far back or lost.
I received a board with locked GSM, showing NO GSM on boot. Every radio flash failed, as well as MTTY and factory ROM attempts. Error 114 and Country ID errors prevent proper flashing of any radio.
Here is what got my GSM sorted - I flashed radio through CID by-pass by inserting the necessary .nbf into flashing facility and managed to flash the radio. On a first boot it will show NO GSM, so will seem like the problem is still there. However, I removed the battery overnight and in the morning the flashed radio showed on the boot screen, the Uni booted as usual and is working as it should.
Thanks enigma
I´ll post this on the FAQ
Cheers,
enigma1nz said:
For those of you who have NO GSM on boot (and I know there are a few). The solution could've been posted some time ago, but might be too far back or lost.
Click to expand...
Click to collapse
thanx dear for the expert advice..LOL.it's grat to have techxpert.
I'll try with ma Uni ^ ^
Thank you
rajivshahi said:
thanx dear for the expert advice..LOL.it's grat to have techxpert.
Click to expand...
Click to collapse
Not sure why you LOL, but the solution worked for me and I hope it will work for others. I now have a JasJar with Radio 1.18, instead of No GSM on boot and no valid solution offered to everyone with the same problem.
it dosen't work I try it but nothing what can I do
Beautifully working VU2.39. Then decided to add new lock ring. Totally messed up phone.
Restored with ROM Manager to prior situation, but have totally lost phone radio (and therefore phone, 3g etc.) Have tried restoring many times, tried airplane mode, wiped cache...all with no solution.
Shows no service, no CDMA or other option exists in settings, phone info shows:
Signal Strength =0
Mobile Network Type unknown
Service state= out of service
What did I do here??? How to fix???
Have now done factory reset and called Verizon. They tried to change manual codes but to no avail. Seems my radio got fried by applying the Captain America launch ring. Is this possible that that was the cause. Worked perfectly before I patched this today.
Help! I don't want a new phone as it will come with 2.3.4 not rootable.
lair12 said:
Have now done factory reset and called Verizon. They tried to change manual codes but to no avail. Seems my radio got fried by applying the Captain America launch ring. Is this possible that that was the cause. Worked perfectly before I patched this today.
Help! I don't want a new phone as it will come with 2.3.4 not rootable.
Click to expand...
Click to collapse
2.3.4 is definitely rootable. And I don't think a ring would change that much. Have you tried flashing a New radio?
Sent from my Incredible 2 HD using XDA App
I tried flashing new radio. No difference.
I just can't believe that the sense link patch would have actually physically damaged the radio and killed the system, but I cannot get anything to "activate" the radio. In manual program mode ##778, the display settings say "radio version 1.09.01.0622", so the software should be there. But it cannot find the hardware.
I have matched my NAM settings and Home SID to the same as my wife (her phone is fine).
lair12 said:
I tried flashing new radio. No difference.
I just can't believe that the sense link patch would have actually physically damaged the radio and killed the system, but I cannot get anything to "activate" the radio. In manual program mode ##778, the display settings say "radio version 1.09.01.0622", so the software should be there. But it cannot find the hardware.
I have matched my NAM settings and Home SID to the same as my wife (her phone is fine).
Click to expand...
Click to collapse
Try flashing this Radio. It's the last one on the list.
No difference whatsoever! So what do you think has happened and how and why? How could flashing the Captain America htc unlock ring have caused such destruction?
Any how could it fry or totally immobilize the radio? I really do not want to replace the phone, but am giving up hope for a solution. It's got to be either something very simple, or the radio did get fried.
And I still don't see where I can unlock and root 2.3.4 on this forum or at the Revolutionary site.
lair12 said:
No difference whatsoever! So what do you think has happened and how and why? How could flashing the Captain America htc unlock ring have caused such destruction?
Any how could it fry or totally immobilize the radio? I really do not want to replace the phone, but am giving up hope for a solution. It's got to be either something very simple, or the radio did get fried.
And I still don't see where I can unlock and root 2.3.4 on this forum or at the Revolutionary site.
Click to expand...
Click to collapse
Well...... Was the lockring made for your specific ROM and phone? If not, that may be why.
Have you tried any other ROMs to make sure it's not just something interfering in the ROM itself?
To root 2.3.4, you have to downgrade the hboot v.98 to v.97 following these steps found here.
Link came from here: http://forum.xda-developers.com/archive/index.php/t-1135020.html
SHould this have bricked the radio??
Can you resend root 2.3.4 link, as the one above goes back to the radio instructions.
Many thanks.
lair12 said:
Link came from here: http://forum.xda-developers.com/archive/index.php/t-1135020.html
SHould this have bricked the radio??
Can you resend root 2.3.4 link, as the one above goes back to the radio instructions.
Many thanks.
Click to expand...
Click to collapse
Post edited so the link for 2.3.4 root should work. But, yeah, that's for Thunderbolt, not the DINC2. Try flashing another ROM or full wipe/reflash of VU 2.39. Don't apply any mods until you find out if it works, and see if someone can port the lockring to the DINC2.
Wiped twice regular and dalvik, installed the clean ROM for phone I had saved. DEAD Radio. Bummer, but thanks for you help.
Mobile Network Type= unknown
Service State= out of service
This has not changed with any fixes I have tried.
lair12 said:
Wiped twice regular and dalvik, installed the clean ROM for phone I had saved. DEAD Radio. Bummer, but thanks for you help.
Mobile Network Type= unknown
Service State= out of service
This has not changed with any fixes I have tried.
Click to expand...
Click to collapse
What about the .722 radio?? Earlier you said you had the .622 radio which is an older one. If that doesn't work, boot into hboot and factory reset (I think this works). Then you'll probably have to re-root. Otherwise, you can get a new phone, and root via the downgrade.
Absolutely no solutions anywhere. Tried everything twice! New phone on the way. Very frustrating situation.
lair12 said:
Absolutely no solutions anywhere. Tried everything twice! New phone on the way. Very frustrating situation.
Click to expand...
Click to collapse
Sorry to hear that.... Let us know how the rooting goes.
Sent from my Incredible 2 HD using XDA App
dear all,
i recently bought a HTC ONE X.
all was fine, until the last few updates.
i noticed when i got the .11 update that GPS was not locking on, and i was getting crazy results in Navigation.
silly me, i thought - i know i'll root my phone and stick on an older ROM...Magnolia X - works with GPS fine.
then i found out that i didnt need to root, i could have used an RUU software update to step it down to an older version.
but because id unlocked my bootloader, it wouldnt take it.
i even tried relocking but then even tho it got past the signature stage, it failed on bootloader version at the end.
so now i dont know what to do.
all custome roms are on the latest build, which has the GPS problem.
how can i go back to .7 or .9 ???
can i get the phone back to stock albeit older ROM, after rooting, and unlocking, relocking, unlocking again?
LOL!
Ta lads.
So...stupidly I thought ids give latest custom Rom a chance again. No feckin signal. Is there a stock custom Rom for .9. ? Everyone seems to have updated to .11 sadly. I can't be the only one with this GPS issue
Hello, have you tried to "reset the localisation" ?
See in parameters, you have a localisation folder, try to reinstall localisation ...
Don't know exactly how it's called in english, i have a french phone.
And you can also try a "factory reset".
Plus, it can be a hardware issue, and i don't think a custom ROM can solve a hardware issue ...
Mate how can I go from custom Rom to ruu?
Hello, basically you will have to relock the bootloader and run the appropriate RUU in fastboot ...
http://forum.xda-developers.com/showthread.php?t=1660642
thanks mate, that worked.
i tried it yesterday but it failed after updating signature, at bootloader.
but i downloaded a later version
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe and it worked
the one failing was
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_1.1204.104.14_release_259281_signed.exe
so im back to stock now.
hope the GPS issue has gone away!!!
manikm303 said:
so im back to stock now.
hope the GPS issue has gone away!!!
Click to expand...
Click to collapse
Well test it and let us know!
Sent from my HTC One X using Tapatalk 2
distortedloop said:
Well test it and let us know!
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
nah didnt work mate.
so basically, whether its my phone or what, but any ROM stock or custom based on 1.29.401.11 does NOT lock on to GPS at all.
im using this custom one (magnolia - based on 1.28.707.10)
http://forum.xda-developers.com/showthread.php?t=1620942
and it locks on fine.
works ok with SYGIC, but not with GOOGLE Navigation. (constant stopping, and rerouting, but the sat symbol is solid - and not flashing)
unfortunately the only STOCK ROM i can flash with - RUU is the 1.29.401.11 - any lower ones either complain about 155 - unknown error, or its a 140 (or 104) bootloader error.
i tried a Vodafone RUU but that moaned about a Custom ID error or something.
so im fooked.
hopefully HTC will release an updated .13 f/w which will make me happy, but right now i feel duped.
i wish i hadnt ROOTED now, but i had to - to find out that it was a software issue, which it DOES appear to be!
but i know plenty of peoples GPS does work on 1.29.401.11 - mine wont even LOCK!
the reason i suspected software, is that when i first got my phone GPS worked on SYGIC (didnt try GOOGLE NAV) but then i received 2 updates and since then it stopped working.
i tried the SATNAV fix posted on this forum, but when i went into ClockWorkRecovery (CWR) to run UPDATE.ZIP it failed.
Good Day Fellow HOX Users
Yesterday I flashed the TripNdroid Linux 3.4.11 Kernel Revised 001 then my phone's Reception was dead after flashing the same Kernel but Revision 002 its still dead After flash the whole ROM + Full Wipe and reflashing everything its still dead, the baseband and IMEI is still there and it dosen't say "Unknown" like other Related problems and I don't want to flash the OEM ROM and return stock because it might get worse
I can't call I can't send SMS but I can use Bluetooth and Wifi
Could Anyone please help me...
Thanks
maybe it's radio related problem, try to flash right ruu for your phone, i think you'll solve
and you're sure you flashed the modules?
tomascus said:
and you're sure you flashed the modules?
Click to expand...
Click to collapse
Yes I flashed it like 5 times something like that already with the whole ROM
Thats BAD
Okay Guys I did more searching and I found this
PhilipL said:
Hi
It sounds like a fault, probably the radio chip has just stopped working, no software is going to repair that. If it was a software problem, there would be hundreds or thousands of people all having the same issue.
Regards
Phil
Click to expand...
Click to collapse
My baseband is still there as its not showing "Unknown"
but the "Network Type" is saying "UNKNOWN :0"
....
Sent From my HTC Desire Z Using XDA Premium