whats has the radio update 32.37.00.32U_4.06.00.16_2 done to cause me to lose wifi "unable to start"
had a fully functiong phone rooted with app2sd installed until i just updated radio
tried dropping back to my earlier version still no joy
anyone got a fix
please
You could try flashing to a newer kernel version (e.g. MCR uvoc_V11) and see if that helps, link here:
http://forum.xda-developers.com/showthread.php?t=682419
If that fails, try a different ROM.
Did you not do a Nandroid backup before flashing?
I would have suggested that you flash back to your previous Radio version but I can see you have already tried that.
still getting to grips with all this
sadly didnt do a Nandroid backup
what is in the process of flashing the said kernel version what will it do give ?
will i lose all my phone data apps etc
msdl28712 said:
still getting to grips with all this
sadly didnt do a Nandroid backup
what is in the process of flashing the said kernel version what will it do give ?
will i lose all my phone data apps etc
Click to expand...
Click to collapse
Nope, you will not lose any data or apps.
The kernel update will give you CIFS, EXT4, tun, 8MB RAM hack (extra 8MB RAM)
CIFS (Common Internet File System) is a protocol used to enhance the wireless connection features on a smartphone.
Ext4 is a newer/better filesystem (you can use it with apps2sd)
tun (tun.ko) is a virtual network kernel driver used for routing OpenVpn purposes.
Yes, I have installed this kernel and everything is working as it should, no problems
Just flash the relevant file (e.g. if you are using an MCR ROM, flash the MCR uvoc v11 zip file for start) via recovery but do a Nandroid backup before. I recommend uvoc v11 as I am currently using it and I have found it to be very stable.
I always make sure i do a Nandroid backup beforehand because you never know what can go wrong.
If you still have the same problem, then flash back to stock ROM with this guide: http://android.modaco.com/content/htc-desire-desire-modaco-com/307683/howto-unroot-your-htc-desire/
one last thing mcr rom how would i know that i flashed using pauls rooting method over at modaco 1.15.405.4 based ROM that one i beleive
edit backing up
and do i just push files through recovery
msdl28712 said:
one last thing mcr rom how would i know that i flashed using pauls rooting method over at modaco 1.15.405.4 based ROM that one i beleive
nandroid is it a comp app or a market app
and do i just push files through recovery
Click to expand...
Click to collapse
If you had flashed one of Paul's ROMs then it will be an MCR (Modaco Custom Rom) ROM.
Place the updated kernel zip file in the root of your sd card, with the phone still connected via USB, switch off phone and then boot into recovery (hold down bottom volume key and press power button), then navigate to recovery.
The red triangle with the exclamation mark should appear, from your PC, run the relevent batch push file (e.g. recovery-windows.bat). Now, while in recovery mode menu, to perform a nandroid backup, select backup/restore from the menu and then select Nandroid.
Go back and flash the kernel zip file.
Reboot.
MCR uvoc_V11 or V!2 no download for the V11 version
cheers again
msdl28712 said:
MCR uvoc_V11 or V!2 no download for the V11 version
cheers again
Click to expand...
Click to collapse
In that case, you can try MCR_uvoc_V12-signed.zip instead, which also appears to be stable.
Mastoid big thanks sorted the wifi out back up and running
Guess it best to to do another nandroid backup while its stable.
you reckon another go on the newer radio or leave well alone
cheers again matey for your time
msdl28712 said:
Mastoid big thanks sorted the wifi out back up and running
Guess it best to to do another nandroid backup while its stable.
you reckon another go on the newer radio or leave well alone
cheers again matey for your time
Click to expand...
Click to collapse
No problem buddy, glad to help you out
If your current Radio version works well in terms of adequate battery life, GPS signal strength, reception, Wi-Fi, etc then I would just leave it. If you do not find it to be sutiable, then re-flash and downgrade to another compatible version, and see if it works any better as Radio's work specifcally depending on your region.
As you can see from my sig, i'm still using version 4.06.00.02.
Just because you have the newest Radio version installed does not mean it will work better for you
Regards,
Mas.
Hey guys I installed cm7 nightly on my phone (#114) but it turns out that my gps doesn't work I then flashed Radio_13.53.55.24H_3.35.19.25 and it's still not working. What I'm wondering is: I have nandroid backups of android 2.2.1 and 2.3.1 of wildpuzzle and cyanogen cm6. Would it be safe to do a nandroid restore to one of these backups and do you think that might fix the problem I'm having with my GPS?
I also read
ALTERNATE METHOD (SAFE) : This is working. First install cm7 and then make a nandroid backup of it. Then wipe everything and restore the previous nandroid backup of stock froyo rom and use gps to capture your location. Then again wipe everything and restore the cm7 backup. Now gps will be working. Atleast worked for me even after checking 3 times. And once gps on cm7 works, then even after a hard reset it still works. This seems to be an issue only when freshly installing cm7. This is definitely a safe method.
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showthread.php?t=1140519.
I would like to do this if the first option doesn't work but I'm not sure where to get the stock froyo rom. I have RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_signed (is this a stock froyo rom?) however my kernel is 2.6.35.13-nFinity so would it be safe to downgrade to an earlier kernel?
I haven't reflashed the radio update so should I do that before I try any of the above methods?
Thanks in advance
Ps. I did read as much as possible before posting this question but I can't really find an absolute answer
First, make sure GPS is indeed not working. Cyanogenmod will only show you the GPS icon when you actually use an app which uses GPS, eg: Any navigation app. Simply enabling GPS does not show the GPS icon on the statusbar.
Second, after you have confirmed that, (I am assuming you used Clockworkmod 2.x to flash the Radio), yes, you can downgrade to your Nandroid backups. Its safe, and, will not cause any issues. You can downgrade to your 2.2.1 Stock, make sure GPS works there, and, follow that post to get CM7 GPS working.
Thanks!
Great thanks for the help man!!
Has anybody found a GPS fix for MIUI that actually works? I tried 3 or 4 fixes with no success.
I did the GPSCLRX fix - flash Sense rom, dial and put in MSL, get a gps fix, reboot, restore, etc. It worked like a charm for me, have you tried that one?
Sent from my PC36100 using Tapatalk
I haven't tried this one. Can I have more details or a link? Thanks.
The best is if you have a stock/rooted ROM that you an nandroid back to.
My steps:
Nandroid to Stock ROM (I have GPS Status on that ROM already and my MSL Written down)
Open Maps
Open GPS Status, Clear AGPS data, the D/L AGPS Data.
Open Dialer, dial ##clrgpsx#
Put in MSL as Password, phone reboots
Open Maps, then GPS Status and get locks
Reboot to Recovery, Flash MIUI and you're done
Can i nandroid back to my MIUI build or do i have to flash?
HipKat said:
The best is if you have a stock/rooted ROM that you an nandroid back to.
My steps:
Nandroid to Stock ROM (I have GPS Status on that ROM already and my MSL Written down)
Open Maps
Open GPS Status, Clear AGPS data, the D/L AGPS Data.
Open Dialer, dial ##clrgpsx#
Put in MSL as Password, phone reboots
Open Maps, then GPS Status and get locks
Reboot to Recovery, Flash MIUI and you're done
Click to expand...
Click to collapse
jed394 said:
Can i nandroid back to my MIUI build or do i have to flash?
Click to expand...
Click to collapse
You can nandroid back.
I did this over six months ago when I was running the really early builds of CM7, and my GPS has worked perfectly ever since on every build of MIUI I've flashed.
Sent from my Evo + MIUI using Tapatalk!
Revamped the entire OP to make it relevant for current roms.
Many users of the Epic 4g Touch have reported various GPS inconsistencies. While this seems to happen more frequently on AOSP-based ROMs (CyanogenMOD, PAC-man, Evervolv, AOKP, etc), it has been reported on TouchWiz-based ROMs as well. Below are a few tips and tricks to help fix your GPS.
FIRST: You will need the necessary tools to troubleshoot the problem.
Google Maps - The app we will use to determine if GPS works properly or not.
GPS Status (Optional) - Provides additional information about GPS performance. This shows how many satellites are in view, coordinates, heading, and other useful information as well. This can help to confirm wether you have a GPS problem or are just in an area without GPS reception.
SECOND: You will need the tools to fix the problem.
- Root-capable file browser (ES File Explorer is my personal preference)
- Mobile ODIN (Free version is available on XDA, but Pro is well worth it, as well as supporting Chainfire, one of the most respected devs in the Android community)
THIRD: You will need some files saved to your sd card. These will be flashed in recovery or Mobile ODIN.
- The EL26+CWM recovery kernel.
- Any Jellybean ROM you want to run.
***For TouchWiz ONLY* Agat's 0.3.0 GB27 Kernel with tREC custom recovery.
- A working GPS.conf (explained later)
- Goddly's ComaDose tweaks (not required if you use a standalone GPS.conf, but highly recommended. See his thread for details.)
FOURTH: You will need these files on your sdcard to temporarily return to stock if needed.
- The EL29 CWM5 Directboot Kernel
- The EL29 Tempboot ROM
METHODS:
I will post each method of fixing GPS, in order of time investment. Test GPS with Google Maps (and optionally GPS Status) after EACH METHOD. Please provide feedback on which method worked for you so that I may improve this guide further.
Method 1 - GPS Toggle
Try this first. It only takes about 10 clicks to do the whole thing, and it saves you from having to flash anything if it works.
1. Close Maps and any other location aware apps. Make sure to clear them from Recents to ensure that they are fully closed.
2. Go the your Location tab under Settings. Toggle GPS satellites off and on, then toggle Location as well (System Settings>Location Access>Access to my Location). This should result in a popup asking if apps can have your permission to use GPS.
Method 2 - New GPS.conf
All thanks to Goddly for allowing me to use his gps.conf.
Sometimes, the GPS.conf file on your phone can become corrupted or otherwise unusable. This will prevent you from locking on to any satellites, even though you may have one (or several) in view.
1. Make sure you have a working GPS.conf on your phone. This can be a standalone GPS.conf like the one attached to this post (extract the zip first!), or it can be one contained in a tweak package such as Goddly's ComaDose v1.4
2. Copy & paste the working gps.conf into /System/App using your root file browser.
3. Set permissions to the gps.conf to 0777 (rwxrwxrwx)
4. Reboot.
5. After booting, toggle Location (triggering the popup).
Method 3 - Lock on Stock
This is a tried-and-true method that was most frequently used in the early days of CM10. It is usually not needed anymore, but I am keeping it in just in case.
1. In Mobile ODIN, flash the EL29 CWM5 Directboot kernel.
2. Reboot, you should automatically wind up in recovery. If you do not go to recovery, pull the battery, wait 10-15 seconds, replace the battery, and hold vol+ and power.
3. Flash the EL29 Tempboot ROM (This will be in the Multiboot folder on your SD card, assuming you followed the instructions in the link above.)
4. You should automatically boot into stock EL29 Gingerbread.
(Optional) 4 1/2. Update Profile and PRL (if desired, you can't do this on AOSP so you might as well do it now)
5. Open Google Maps and get a GPS lock (you will likely need to be outside to get a good lock). Sometimes it helps to navigate to a random place.
6. ***WHILE YOU STILL HAVE A GPS LOCK***, power down the phone, then hold vol+ and power until you boot to recovery.
7. In recovery, Wipe Cache, Wipe Dalvik Cache.
8. Flash your ROM of choice.
9. Reboot.
Please reply to this thread with any questions/issues/feedback.
Thanks....will try it.
I havent multibooted this device.... Do u just make a folder on internal sd or do i need to..... Nevermind i guess i should google first
Sent from an Apple killing JellyBean
moparfreak426 said:
I havent multibooted this device.... Do u just make a folder on internal sd or do i need to..... Nevermind i guess i should google first
Sent from an Apple killing JellyBean
Click to expand...
Click to collapse
Detailed instructions are in the tempboot link in the OP.
ok... i read up on it and stuff.... i cant mount phone to pc... idk why so i put multiboot on sd card and moved it to root of device..... its froze moving the system.ext4.img......... should i be worried? phone is so laggy... hit power button to turn on off screen... response = roughly 10 seconds later
---------- Post added at 11:57 PM ---------- Previous post was at 11:43 PM ----------
Phone completely froze and reset.... So no gps lock for me:/
Sent from an Apple killing JellyBean
moparfreak426 said:
ok... i read up on it and stuff.... i cant mount phone to pc... idk why so i put multiboot on sd card and moved it to root of device..... its froze moving the system.ext4.img......... should i be worried? phone is so laggy... hit power button to turn on off screen... response = roughly 10 seconds later
---------- Post added at 11:57 PM ---------- Previous post was at 11:43 PM ----------
Phone completely froze and reset.... So no gps lock for me:/
Sent from an Apple killing JellyBean
Click to expand...
Click to collapse
if you didnt get a good copy your multiboot wont work. Try downloading the file directly to your phone, and unzip it to the root of your internal with zarchiver.
Edit: apparently zarchiver can't extract to the root, or the system.IMG won't copy to the multiboot folder correctly. Try copying it again with your computer. Make sure it's on the root of your internal, not in /sdcard/ or on your external.
Failing that, nandroid your cm10, flash a tw-based gingerbread ROM with cwm5 recovery, get a GPS lock, reboot to recovery, flash cm10, reboot recovery, then restore your nandroid while on cwm6
Edit 2: what ROM are you on when trying to mount USB storage? It won't work on tw ICS or jb, and it might be disabled on aosp (Settings>storage > menu > USB computer connection > USB mass storage)
I was wanting to try this, but had a couple questions before I tried it:
Is the wipe of /data really necessary, or does it just help things run better?
Will this work on CWM6?
Also, with the PACman builds after 1/12, you don't have to flash Paranoid Preferences seperately.
Lt_data said:
I was wanting to try this, but had a couple questions before I tried it:
Is the wipe of /data really necessary, or does it just help things run better?
Will this work on CWM6?
Also, with the PACman builds after 1/12, you don't have to flash Paranoid Preferences seperately.
Click to expand...
Click to collapse
1: Technically no, but a /data wipe is always recommended. If you have issues after this procedure, wiping /data is your first step to fixing them.
2: You start out on the cwm6 included in our AOSP kernel. You flash the el29 cwm5 directboot kernel with mobile odin, then flash the el29 multiboot (which requires the el29 kernel). When you are done with your prl updates/gps fix/dialer codes, you then reboot recovery and flash your AOSP 4.1 again, which puts you back on the AOSP kernel that includes cwm6.
Updated OP.
Does it matter that AOSP ROMS now use /sdcard instead of /emmc for the internal card? I tried the steps (without any clearing of cache or data, doh) and it just bootlooped. I was just wondering if that would be a factor?
Re: [FIX][JB]GPS Workaround for AOSP-Based 4.1.2
Lt_data said:
Does it matter that AOSP ROMS now use /sdcard instead of /emmc for the internal card? I tried the steps (without any clearing of cache or data, doh) and it just bootlooped. I was just wondering if that would be a factor?
Click to expand...
Click to collapse
Talking about the multi boot I assume? It goes in /sdcard/. This is the root of the phone's internal storage when mounted as USB mass storage via PC.
I don't even remember when AOSP last used /emmc/...July I think? Alpha CM9 I think. Before Chris41g started releasing like 5 test builds a day. At any rate, long before jellybean, which is what this guide is for.
And don't forget to wipe the things, or you will have problems.
Sent from my SPH-D710 using xda app-developers app
Adreaver said:
Talking about the multi boot I assume? It doesn't go in /sdcard or /emmc. It goes on the root of your internal storage.
And don't forget to wipe the things, or you will have problems.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
/sdcard IS the internal storage. The actual SD card mounts to /external_sd. I realized this after 45 minutes of trying to make a multiboot folder in / unsuccessfully.
Lt_data said:
/sdcard IS the internal storage. The actual SD card mounts to /external_sd. I realized this after 45 minutes of trying to make a multiboot folder in / unsuccessfully.
Click to expand...
Click to collapse
*facepalm* You are correct. My mistake.
I was thinking root of internal storage when phone is mounted via USB. I could never get the multiboot to extract entirely on the phone, it would just freeze for a while, then force close ES, then eventually reboot.
The correct path (when flashing) is /sdcard/multiboot/EL29/Boot_EL29.zip. So make sure your install matches this, or you will have problems.
Tried it again, this time via Mobile Odin instead of desktop Odin and it worked great! Updated my modem to FL24 and then updated PRL and profile. Thanks for the instructions and the help!
Hello, I have tried fixing my gps lock with this method three times. I even "one clicked" back to EL29 rooted for a fresh(er?) start. While in the EL29 temp boot, I can get either a 9/9 or 10/10 GPS lock( all three attempts), power down while in the lock (using google navigation), and follow the rest of the steps. Once I flash back to my CM10.1, or a clean install of 10.1, I start up GPS Status, and it tells me 0/2 sattelites locked. What is odd is that the two it tries to connect to changes every second or so to another random sattelite. So I see something like 21->03->18->12->30->14->22->32 etc. Any tips? Would flashing a new modem help? I originally had FL24 (i think) when I tried this method the first two times, and EL29 the third time (because Odin One Click reset it back to EL29).
EDIT: oh I realize this method works for 4.1.2, but would it also work for CM10.1, which is 4.2?
chaosacolyte said:
Hello, I have tried fixing my gps lock with this method three times. I even "one clicked" back to EL29 rooted for a fresh(er?) start. While in the EL29 temp boot, I can get either a 9/9 or 10/10 GPS lock( all three attempts), power down while in the lock (using google navigation), and follow the rest of the steps. Once I flash back to my CM10.1, or a clean install of 10.1, I start up GPS Status, and it tells me 0/2 sattelites locked. What is odd is that the two it tries to connect to changes every second or so to another random sattelite. So I see something like 21->03->18->12->30->14->22->32 etc. Any tips? Would flashing a new modem help? I originally had FL24 (i think) when I tried this method the first two times, and EL29 the third time (because Odin One Click reset it back to EL29).
EDIT: oh I realize this method works for 4.1.2, but would it also work for CM10.1, which is 4.2?
Click to expand...
Click to collapse
sorry for the delayed response. This method should work for CM10.1, but I have not tested it personally. Post your results and let everyone know if it works for you.
Re: [FIX][JB]GPS Workaround for AOSP-Based 4.1.2
I did OP fix with el29 with no success. (Used to work for me)
However..
After trying a few ROMs. I noticed I could update prl/profile in jellyverse v.4 (FL26) and get a lock. At this point curiosity struck so I Mobil Odin cwm el26, wiped data/cache/dalvik **skipped format all zip** and I flashed a JB aosp ROM and ICS modem. Long behold I can get GPS locks on my favorite ROM now.
So if el29 doesn't work for you (It did at one point for me but not anymore) try this method. It worked for me. :thumbup:
GL
Sent from my SPH-D710 using Tapatalk 2
Re: [FIX][JB]GPS Workaround for AOSP-Based 4.1.2
Gazzuk said:
I did OP fix with el29 with no success. (Used to work for me)
However..
After trying a few ROMs. I noticed I could update prl/profile in jellyverse v.4 (FL26) and get a lock. At this point curiosity struck so I Mobil Odin cwm el26, wiped data/cache/dalvik **skipped format all zip** and I flashed a JB aosp ROM and ICS modem. Long behold I can get GPS locks on my favorite ROM now.
So if el29 doesn't work for you (It did at one point for me but not anymore) try this method. It worked for me. :thumbup:
GL
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Never use a format all script with this fix. It will cause problems.
Better yet, never use a format all script ever, unless specifically directed by the OP.
Sent from my Epic 4g Touch on PAC-man v19.3
Re: [FIX][JB]GPS Workaround for AOSP-Based 4.1.2
Adreaver said:
Never use a format all script with this fix. It will cause problems.
Better yet, never use a format all script ever, unless specifically directed by the OP.
Sent from my Epic 4g Touch on PAC-man v19.3
Click to expand...
Click to collapse
Thanks for the tip, I was using it as a shortcut... whoops
sent from my ET4G on Paranoid Android using XDA Premium HD in hybrid mode
Adreaver said:
sorry for the delayed response. This method should work for CM10.1, but I have not tested it personally. Post your results and let everyone know if it works for you.
Click to expand...
Click to collapse
sorrry for my late reply too, . The problem seems to be in the CM10.1 rom itself, because there are others in the thread (edit: the "wild for the night CM10.1 thread) that have the same situation as me. Actually the gps is locking correctly, with an error of 3 meters, its just GPS Status and other gps apps (like Ulysse) can not report correct lock information. Instead it shows spazzing attempts to lock to different sattelites. Hope this info works!
tl;dr: GPS locks even though apps dont report it locking in CM10.1
Re: [FIX][JB]GPS Workaround for AOSP-Based 4.1.2
chaosacolyte said:
sorrry for my late reply too, . The problem seems to be in the CM10.1 rom itself, because there are others in the thread (edit: the "wild for the night CM10.1 thread)... tl;dr: GPS locks even though apps dont report it locking in CM10.1
Click to expand...
Click to collapse
That would explain why I hadn't heard... I haven't been checking that one, I was on phantom's cm10 and hadn't been following WftN
Sent from my SPH-D710 using xda app-developers app
no matter what baseband i flash via odin, wi-fi could not be enabled after rebooting.
baseband version changes successfully. anyone have a solution for this issue? thanks
in advance.
flash it twice!
lOtz1009 said:
flash it twice!
Click to expand...
Click to collapse
doesn`t work.
is it neccessary that kernel and baseband have to be the same version?
crxvti said:
doesn`t work.
is it neccessary that kernel and baseband have to be the same version?
Click to expand...
Click to collapse
nope, I actually found a fix for the same issue, root your phone then delete /data/misc/wifi/wpa_supplicant.conf then flash your rom again (not sure if you need to clean data and cache) with odin and it should work.
Levent2101 said:
nope, I actually found a fix for the same issue, root your phone then delete /data/misc/wifi/wpa_supplicant.conf then flash your rom again (not sure if you need to clean data and cache) with odin and it should work.
Click to expand...
Click to collapse
unfortunately, this does not work, wi-fi can only be enabled if i use the one from my rom
I was have same issue.
How did I fix it? (I have 9190)
I flashed 9195's stock rom via odin. Of course odin gave me error. I removed the battery and placed it again. Flashed latest 9190's stock rom and wifi issue solved.
i flashed a rom that fits for i9195, that is not my problem. i have no wi-fi after i update my modem. version number is correct but wi-fi can not be enabled, even if i flash it twice. my rom is the sc-stock rom
http://forum.xda-developers.com/galaxy-s4-mini/development/rom-stock-nk5-deodexed-debloated-4-4-2-t3104160
crxvti said:
no matter what baseband i flash via odin, wi-fi could not be enabled after rebooting.
baseband version changes successfully. anyone have a solution for this issue? thanks
in advance.
Click to expand...
Click to collapse
The ROM controls the wifi, not the modem. Strange that multiple ROMs can't even be enabled, I suspect data is left somewhere, do full wipe to install a new ROM so all old data etc is wiped and make sure you are not installing app data etc from a backup for this.
Else it might be the kernel.........
IronRoo said:
The ROM controls the wifi, not the modem. Strange that multiple ROMs can't even be enabled, I suspect data is left somewhere, do full wipe to install a new ROM so all old data etc is wiped and make sure you are not installing app data etc from a backup for this.
Else it might be the kernel.........
Click to expand...
Click to collapse
wi-fi is working with the baseband which is included in the rom (until i flash another baseband, then it stops)