I have tried to changing my gps.conf into my nearest NTP from north-america into asia/my (I am living in Malaysia) on my Desire HD
But somehow after sometime without me doing anything, I realise that the gps.conf actually change back to north-america and sometimes it gone missing. Ever since then I have not get a fix.
As a result I have to unroot and reroot (either temproot or permroot) my phone so that I can get back the gps.conf file into it and change them once again. It happens >3 times as at now.
Any idea what or where has gone wrong?
I use VISIONary + to perform my rooting.
Thank you. =)
Related
So, I started out with 4g working. I was on stock kernel with fresh rom. Then I did a backup and flashed cm6. Ofcourse cm6 doesn't have 4g, so because of this, i did a full wipe and went back to the backup. Then i flashed 2-3 kernels like kings, and netarchys. Finally i flashed bakedsnack kernel and rom.
So right now I'm on bakedsnack. BUT my 4g doesn't seem to work. When i enable it, it says "scanning" and then "connecting to sprint". After that it loops back to scanning, and then to connecting to sprint again. Over and over.
I know it sounds as if I'm not in the 4g area, but this happens everywhere and anywhere i go. Even if im 50+ miles from my home (where it worked previously.)
Does anyone know how to fix it?
oh and i actually have clear wire at my house, which has the same exact coverage as sprints network, and right now i have 4 bars on my clearwire.
There are several things that can be done to fix this. Try deleting the tree XML file first, forcing your phone to generate a new one:
Using a terminal emulator or through adb on your computer....
su
ls /data/misc/wimax
(You should see a file with your mac address - several numbers followed by tree.xml)
rm /data/misc/wimax/xxxxxxxxxxxx.tree.xml
Then reboot. Your phone will generate a new tree file when it boots back up. Flip on 4g and see if that fixes it.
Sent from my PC36100 using Tapatalk
tried it. guess im back to starting over =/. Oh well.
Last-Chance said:
tried it. guess im back to starting over =/. Oh well.
Click to expand...
Click to collapse
Have the same issue good luck I havent found a fix other than a replacement phone
I have the correct mac I need I have certs etc etc
just reflashed it to start over. Seems to have teh same problem. Still have the 0016. Re doing it again now.
Same problem still, except now it does:
Scanning, connecting to sprint, turning off, turning on, scanning, etc..
sorry for the bump, but i had a nandroid backup of my old fresh rom with stock kernel. At first i wasn't expecting much when i restored, but i just saw that in the /data/misc/wimax dir, there are 2 xml files. One of which has my own hex (or w/e its called), the other one is 0016. I deleted the 0016, but it keeps re appearing. Is there any way to fix this?
I tried to adb remount it, but for some reason i cant. Is there another way to check to see if my rsa keys are still there?
Thanks
edit: I have now successfully changed my xml to the mac address, but 4g still doesnt work =/
I've had the same issue for a while now. I was on the 2.2 "leak" and it was still working. I used the roll back hack to get back and then went up to rooted 2.2. Since then, I've had nothing.
- My MAC was wrong, but the fastboot fix got that worked out.
- My tree.xml was wrong, but I renamed it and a new one with the right MAC in the name was generated.
- I went all the way back to stock unrooted (2.2 Final RUU) S-OFF and everything and still nothing.
I have mine sitting next to a friends and he's got 3 bars. Mine just keeps scanning, connecting and turning off then turning on (same cycle as the OP) without getting anywhere. I'll be watching this thread to see if there are any suggestions posted that I haven't seen in my searches. I think I've tried 4 ideas from other threads to no avail. If I don't get this worked out I'm going to have to visit the dreaded Sprint store and kill half a day waiting on them to test and most likely replace the damn thing but whatever.
Yea, im taking mine to the sprint store today. Tried everything. I cant even update it to 2.2 using the normal updater thats in the phone. Just fails at signature verification.
The problem is, I bought mine on craigslist, would they still replace it? Or am i ****ed?
Hi all, I've done a search but can not find a similar problem.
I have Eclair 2.1 running on my Desire. It's rooted
The problem is I can not connect to my router (or any other router for that matter).
The phone does however recognise available wireless networks. Allows me to select my home network and enter the WEP but just doesn't connect. It also has a MAC address allocated on the phone.
One thing I am unsure of is when I try to enter the WEP key, just above the input box there is the drop-down option to select Key Index of which the options are 1, 2, 3 or 4. What does this mean?
I've also got the option to update the OS to Froyo 2.2. It's an OTA update and unfortunately my only option is to do t via 3G as I can't do WIFI (as stated above). Almost 90mb!!!
Will there be any issues with installing this update... considering this phone has been unlocked, Rooted and has ClockworkRecoveryMod?
Don't want to waste 90MB to find it doesn't work.
Just a suggestion. try disabling your router security and see if it connects then. If it does try using Mac address filtering instead so the desire will think it's just going onto an unsecure network.
Why would you want to take the official OTA upgrade to froyo at this time when there are a bajillion custom froyo, desire hd and gingerbread roms out there?
If you like htc sense and froyo, then i suggest you try leedroid. Its pimped up stock froyo. And you can download it onto your computer first. Plus its guaranteed to work.
If I'm not wrong, doing the OTA update will overwrite your hboot and recovery as well, thus unrooting your phone. And the newest hboots may be shackled down with more security that existing methods cannot unlock- your phone may become unrootable.
nanujra said:
Why would you want to take the official OTA upgrade to froyo at this time when there are a bajillion custom froyo, desire hd and gingerbread roms out there?
If you like htc sense and froyo, then i suggest you try leedroid. Its pimped up stock froyo. And you can download it onto your computer first. Plus its guaranteed to work.
If I'm not wrong, doing the OTA update will overwrite your hboot and recovery as well, thus unrooting your phone. And the newest hboots may be shackled down with more security that existing methods cannot unlock- your phone may become unrootable.
Click to expand...
Click to collapse
Unfortunately... very unfortunately indeed... I went through with the OTA update via ClockworkRecovery. I used the 'Apply SD Card/Update.zip' option before I read your reply.
I've bricked my phone!! It won't go bast the initial HTC screen.... just keeps rebooting. Yes... I'm kicking myself for it now.
I've lost recovery mode now. I can get into the initial bootloader screen but when you select the option for 'Recovery', I ust get a pic of a phone with a hazard sign [!]. Very bad. It doesn't repspond to anything and the only way to turn it off is to pull the battery.
Any suuggestions on how to fix or have I got a dud phone now?
managed to sort it out eventually. Phew!!
Still got the wifi issue though
I've changed the Router (o2 wirless box) settings from WEP to WPA/PSK.. also selected different channels and even tried it without any security on at all (open network)... but my phone still won't connect. It scans perfectly fine and finds the network. Just won't connect.
I thought the Froyo update might hep fix it but to no avail.
i'm never going to get to the bottom of this am I?
Recently rooted my desire HD using Advanced Ace Hack Kit and flashed CM7.2. I am now having GPS connectivity issues. (I am aware there are already forums about gps problems with CM however i cannot resolve my problem).
As far as I can tell the GPS is working, but poorly.. Using GPS status i can see that my phone is fixing onto satellites slowly. It gets up to about 5 satellites and then slowly starts losing them again. It fluctuates between 0 and 5 satellites for a number of minutes. Sometimes if i'm lucky it will shoot up to 8 or 9 which gives me a GPS fix accurate enough to use google maps etc. It will take minutes to get a fix (if at all). Previous to root and CM I could get a fix within seconds every time, without fail. I copied a gps.conf file from my girlfriends legend which seem to fix the issue (got a fix within seconds). The next day however i could not get a lock on my location. I have tried various gps.conf configurations, some of which appear to fix the issue but only temporarily.
I am a total noob at this, I have read a little on the radio versions effect on GPS and that updating this may fix the issue. Is this possible? I am a little reluctant to do this as I have never done it before and would rather have a phone without a gps than no phone at all. Can anyone help or at least point me towards some reading so i can understand what is going on.
My gps.conf file is
NTP_SERVER=0.au.pool.ntp.org
XTRA_SERVER_1=1.au.pool.ntp.org
XTRA_SERVER_2=2.au.pool.ntp.org
XTRA_SERVER_3=3.au.pool.ntp.org
SUPL_HOST=supl.google.com
SUPL_PORT=7276
My baseband version is
12.56.60.25U_26.10.04.03_M
Try flashing a different ROM and see if thats the issue (I had a similar problem, re-flashing/flashing a different ROM did the trick
Sent from my Desire HD using Swype beta for Android!
Thank you, I ended up deleting the "supl" lines from gps.conf. Now it appears to be working. If it fails again I will try re-flashing. Thanks again.
keefst said:
Thank you, I ended up deleting the "supl" lines from gps.conf. Now it appears to be working. If it fails again I will try re-flashing. Thanks again.
Click to expand...
Click to collapse
I guess that u are using the settings for australia....that is what AU. stands for....replace your gps.conf with this one:
Code:
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
it works great....I am using it in Buenos Aires and gets a nice gps fix....to change the gps.conf u have to use a root explorer (such as file explorer) with root explorer and write permissions. Copy this code from the mobile application and then copy it in the system/etc/gps.conf file...or you can do a .txt file with that code, rename it gps.conf and then replace it in the phone....hope it works....:good:
yep, from Australia. Thanks, I have tried a gps.conf file with the north america region and it did work temporarily. The next day however it had reverted back to its old ways.
It appears i spoke too soon about my other fix. Tried it out today and once again it has stopped working. Even though i did multiple reboots yesterday after i thought everything was okay.
When i finish work I'm going to try flashing to CM7.1 and see if that helps.
keefst said:
yep, from Australia. Thanks, I have tried a gps.conf file with the north america region and it did work temporarily. The next day however it had reverted back to its old ways.
It appears i spoke too soon about my other fix. Tried it out today and once again it has stopped working. Even though i did multiple reboots yesterday after i thought everything was okay.
When i finish work I'm going to try flashing to CM7.1 and see if that helps.
Click to expand...
Click to collapse
hahaha sorry I read Newcastle and didn't see the flag from my mobile app...so I thought it was Uk...then u are right. Make sure that try the AGPS fix that are in the development section. I had that issue, that my gps detected sats but would not fix then. I used the GPS status app from play store and reseted the AGPS..with tools>manage A-GPS....
try that. It worked for me.
I have discovered a hardware defect in my phone. It just so happens that the problem only occurred after installing CM7.2 (very big coincidence but a coincidence none the less). Going to try to fix it more permanently soon. Thanks for your help.
Really not sure what to do here, and I'm starting to get very frustrated, especially since I know exactly what the issue is and I can't find a solution... So here is everything I did up to this point in detail. I wanted to go back to stock for a while, but I remembered not being able to update at all last time I tried this. I used the LG Flash Tool to go back to 10b (I think? Earliest firmware out there) It started when my phone would tell me that "My Device was not registered yet" in the System Update settings. I did some Googling and found out it was because my IMEI number was blanked out (All zeroes), and I found a tutorial that was for the G2, but worked for the G3, to repair the IMEI. I first rooted with the LG One Click Root Tool when I got to Lollipop, used the IMEI that was under my battery, converted it to HEX and injected it into my phone with RF_NV_Manager, which was installed with QPST by Quallcom. After doing this, my IMEI was fixed, it matched the same IMEI that was under the battery on my phone, though I never texted or called anyone from there so I never noticed anything strange. I was able to update to the latest official Lollipop firmware, but then my phone started telling me I left the home network. Thinking it was just a glitch or something, because I had roaming issues before on stock, I switched to a custom ROM since that fixed it last time before I even knew that IMEI's existed. That didn't fix it at all. I was on LiquidSmooth Alpha and my phone will still go to roaming, and the way I would fix it was to piss around with the mobile network settings and change them back, then I would get 4G LTE for a few minutes, but I would NEVER be able to call or text. Since it was a discontinued ROM, I thought I just got unlucky, so I went to an official Nightly for CM12.1. At the moment I have LTE but no calling or texting... Then I found out that these issues tend to occur after IMEI fixes, so what do I do? Can anyone point me to a proper tutorial on how to fix this? After looking, I ended up downloading and installing something called EFS Professional 2.1 but now I'm even more confused...
EDIT: I tried going into ADB and inputting "adb reboot nvrestore" but that didn't fix it... The site said it's based on a backup that was automatically created when the phone was first built but that was on a completely different forum for a different phone. Going to try to flash back to stock KitKat.
EDIT: Alrighty! I'm getting somewhere! I flashed back to 10B with the Upgrade DL option, before I used Board DL. I can call and text now, as well as LTE, and OTA updates work, but I'm just going to root and go straight to the Nightly CM12.1 that I wanted to go to in the first place.
EDIT3: That seems to have done the trick. For people who have had issues with roaming after IMEI repairs, try flashing your stock TOT with the Upgrade DL option, then root and install your preferred ROM.
I just got this phone yesterday & rooted it about 30 min ago. My WiFi will no longer connect after root. Can I fix this somehow? I used to root often till AT&T locked the boot-loaders in the S4 days.
I have since tried to remove root with SU-User but the kernel reroots on reboot. The WiFi will connect to an open network. I just restored or recovered with smart switch & the WiFi didn't fix itself. Damn this sucks!
You broke it. That's what rooting does, before it worked properly - root - broken.
Try finding a modem and flashing just the modem, it may take several flashes before it sticks. This should fix it.
My Wifi works all the time,,,,, ohh I forgot no root for me.
Pp.
I went back to the factory ROM. All is well now. I forgot to come back & report I fixed it
Ok then, next time don't forget!
Will send the "root gremlins" after your phone.
Pp. Lol.