Develop Bugs

4G won't connect after flashing ROM

First Android phone, so I still getting up to speed so hoping someone could answer a couple quick questions. I'll start with the questions and then give the history.
1) How do you determine what ROM you have installed?
2) Any ideas why 4G won't connect? Is there any way to troubleshoot this?
3) Is there anyway to tether on 4G?
So I dove right in after purchasing this phone and flashed a ROM (Zedomax) so I could tether. After installing this ROM my battery life went down the drain and it wouldn't hold a charge for more than 6 hours.
So then I flashed the EG30 stock kernel and my battery life returned to normal. Still wanting to tether I tried another ROM (don't remember which one). This ROM had the same battery issues so I once again flashed the stock kernel back to my phone.
So now my battery life is great, but 4g won't connect (i'm in NYC) for a few days now. I've tried pulling battery, want what not to no success.
I believe I am running the stock kernel, but to my surprise I still have root access. No triangle on the home screen and ODIN says I'm using the Samsung Official binary.

Just to clarify, you are flashing kernels, not ROMs. Zedomax is a kernel, EG30 is a kernel, etc. You can find your current kernel version under Settings > About phone > Kernel version.
Also as an FYI, I wouldn't be going all willy nilly flashing kernels that you can't remember the name of. I'd have to imagine that's a good way to possibly brick your phone or have problems like you are with 4G.
I'm no expert on this stuff by any means but I'd probably recommend flashing Bubby's stock kernel or chris41g's version of it that is packaged up with CWM. These will get you back to the stock kernel (assuming you're not there already) and probably get your 4G working. Otherwise you probably need to update your PRL or something along those lines. Someone who actually knows more about this stuff (i.e. not me) may have a better suggestion for you.

Thanks.
Kernel version is 2.6.35.7-SPH-D710.EG30-CL435734
Is that stock?

walkingcrow said:
Thanks.
Kernel version is 2.6.35.7-SPH-D710.EG30-CL435734
Is that stock?
Click to expand...
Click to collapse
Yep! 10 char

Cool.
So flashing to chris41g's or Bubby's kernels probably won't help me. I'll go searching to figure out how to update my PRL but if anyone has any other ideas I'd be grateful.
Also does anyone know if it is possible to tether over 4G? I was never able to connect unless I turned off 4g before tethering.

It is working again. I started over and flashed Stock-EG30.tar and all is good now.

Out of curiosity did you update your system profile after you flashed? I think it's recommended to do that every time you flash a new kernel.
Settings > About phone > System updates then choose update profile.
Edit - Ahh cool looks like you got it worked out. Cheers!

Nope, I never updated my system profile. That could of been a fix....
Interestingly enough, I was retracing my steps after going stock, after each step I checked 4G connectivity. I lost 4G after enabling AdAway. So I disabled (each change requires a reboot) and got 4G back after the boot. I enabled it again hoping to be able to isolate the issue but after that next reboot I got 4G access with AdAway enabled.
Can't say it is AdAway, but after toggling it, I got 4G back.

[Q] Wi-Fi doesn't work. Need help. I'm new to this.

Hello, I'm new here to this and to the flashing stuff and rest.
I wanted to do some change to my buzz so I just flashed my 2.2.1 to 2.3.7 (CyanogenMod-7.1.0.1).
Everything was fine, flashed Gapps also.
The only thing is my wi-fi isn't working.
It can't even connect. It's like refreshing by 3 secs and doing that in a circle.
/// What I Did:
- Reflashed CyanogenMod twice.
- Reflashed my radio (the newest version anyway).
/// Specs:
- Android 2.3.7
- CyanogenMod-7.1.0.1
- Radio 3.35.20.10
- HBOOt 6.01.1002
- S-OFF
Did everything today and WiFi was working in the morning perfectly (on 2.2.1)
Just let me know if you want to know something more. Thanks guys.
Heard that Regulatory domain may cause that problem. Tips?

There is a cm mod 7.2 and that must fix it i think
Sent from my HTC Wildfire using xda app-developers app

wilek619 said:
Hello, I'm new here to this and to the flashing stuff and rest.
I wanted to do some change to my buzz so I just flashed my 2.2.1 to 2.3.7 (CyanogenMod-7.1.0.1).
Everything was fine, flashed Gapps also.
The only thing is my wi-fi isn't working.
It can't even connect. It's like refreshing by 3 secs and doing that in a circle.
Click to expand...
Click to collapse
first of all: you asked if regulatory domain could have to do with your problem. If you have access to your WiFi's settings you could check that by simply changing the channels (the procedure for that might be totally different in different routers). From my experience I doubt it anyway but I might be wrong here.
Another possibility to check if your phone's WiFi works or not would be to log into a different network - no idea if you could do that.
The reason I'm suggesting this first is, we could of course suggest things you might try with your phone - but - if your WiFi is the problem this might take some days and wasting lots of posts without any result or help

Did you do wipe all? I think if you installed CyanogenMod 7.2 it would be ok then. Give a try

Some tests that you can do:
- Flash an older radio, to see if the radio didn't got corrupted somehow. Reboot the phone and then flash the newer again;
- Flash the stable CM7.2;
Did you have issues with the stock ROM and the wifi?
Sent from my badass HTC Wildfire.

Lost GPS ? And how to get it working again.

I have seen a variety of posts in various threads about people not being able to get GPS connections and blaming the ROM they were on the for the problem - I imagine that sometimes that could be the reason but something happened to me recently that makes me wonder...
I am a flashaholic - often going back and forth between various ROMS via Nandroid back ups - all was good - then recently I noticed my GPS wasn't working. I thouht it was the rom - but no matter what I did I could not fix it. I tried installing other roms - totally clean install - I tried flashing back to rooted stock and no matter what I tried, GPS did not work.
I don't know where I saw it, but I finally saw a post from someone who suggested fixing it by going back to stock via odin - I tried that and it didnt work either - digging a little deeper someone suggested using odin to going back to pure stock then go into settings and do a factory restore.
I tried it - and it worked - took me virtually all day to figure it out - but it is working better than ever now - I wish I knew what caused it in the first place - but at least I found a somewhat reasonable solution.
If you have lost your GPS and can't get it working again - give it a shot -
Does anyone else have any other suggestiions that might work?

This is correct. I had this exact same issue and this worked for me as well.

Tyie101 said:
This is correct. I had this exact same issue and this worked for me as well.
Click to expand...
Click to collapse
Do you know why it happend in the first place? Was it the result of a specific Rom or just flashing in general?

Thats what i found that worked for me too. It only worked after i went into settings and reset the phone after odin.
Sent from my SGH-I747 using xda app-developers app

I heard it was sprint based leaks on the s3

pure stock ?? can you explain ..thanks

mocsab said:
I have seen a variety of posts in various threads about people not being able to get GPS connections and blaming the ROM they were on the for the problem - I imagine that sometimes that could be the reason but something happened to me recently that makes me wonder...
I am a flashaholic - often going back and forth between various ROMS via Nandroid back ups - all was good - then recently I noticed my GPS wasn't working. I thouht it was the rom - but no matter what I did I could not fix it. I tried installing other roms - totally clean install - I tried flashing back to rooted stock and no matter what I tried, GPS did not work.
I don't know where I saw it, but I finally saw a post from someone who suggested fixing it by going back to stock via odin - I tried that and it didnt work either - digging a little deeper someone suggested using odin to going back to pure stock then go into settings and do a factory restore.
I tried it - and it worked - took me virtually all day to figure it out - but it is working better than ever now - I wish I knew what caused it in the first place - but at least I found a somewhat reasonable solution.
If you have lost your GPS and can't get it working again - give it a shot -
Does anyone else have any other suggestiions that might work?
Click to expand...
Click to collapse
I recently lost my GPS after flashing a Sprint-based ROM. Unfortunately, ODIN back to stock and factory reset from the Settings menu (and from recovery) did not bring back my GPS.
However, I followed a suggestion from this thread:
http://forum.xda-developers.com/showthread.php?t=1923067
I used ODIN to go back to a rooted stock ROM, installed CWM, installed the Sprint-based ROM that seemed to have been the source of the trouble. My GPS started working again. I then used CWM to restore a stock nandroid backup I had from earlier and GPS continued to work thereafter in any ROM I flashed.
There may be a simpler process, but that's what worked for me.

frelnik said:
I recently lost my GPS after flashing a Sprint-based ROM. Unfortunately, ODIN back to stock and factory reset from the Settings menu (and from recovery) did not bring back my GPS.
However, I followed a suggestion from this thread:
http://forum.xda-developers.com/showthread.php?t=1923067
I used ODIN to go back to a rooted stock ROM, installed CWM, installed the Sprint-based ROM that seemed to have been the source of the trouble. My GPS started working again. I then used CWM to restore a stock nandroid backup I had from earlier and GPS continued to work thereafter in any ROM I flashed.
There may be a simpler process, but that's what worked for me.
Click to expand...
Click to collapse
Now that I thnk of it, I also had flashed a Sprint Based rom - that must have triggered my original issue - I explained what I did to restore my GPS at the start of this thread _ and it is similar to what you described - execept I did not odin to a SPRINT rom - I used ODIN to bak to pure stock - then did a factory restore - (and this second step is what seemed to do the trick) then I re-rooted and went backto my happy days of flashing roms - I haven't had an issue since.

mocsab said:
Now that I thnk of it, I also had flashed a Sprint Based rom - that must have triggered my original issue - I explained what I did to restore my GPS at the start of this thread _ and it is similar to what you described - execept I did not odin to a SPRINT rom - I used ODIN to bak to pure stock - then did a factory restore - (and this second step is what seemed to do the trick) then I re-rooted and went backto my happy days of flashing roms - I haven't had an issue since.
Click to expand...
Click to collapse
so what all of you are saying its only because you flashed that sprint leak and thats why ur gps was all jacked up?

amzi said:
so what all of you are saying its only because you flashed that sprint leak and thats why ur gps was all jacked up?
Click to expand...
Click to collapse
Well...that may not be the cause but it's a common denominator. I did and I had to flash back to stock and factory wipe to get mine back.

rpavich said:
Well...that may not be the cause but it's a common denominator. I did and I had to flash back to stock and factory wipe to get mine back.
Click to expand...
Click to collapse
It definitely seems to be a common element to most of these GPS issues. I'm not sure why, in some cases, all it takes is a factory reset in stock to fix it, while others have to re-install the Sprint ROM first. Either way, though, it seems like in most cases, it's user-fixable.

Got the GPS death syndrome today. Flashed a ton of stock ICS nandroid backups without any luck. Finally fixed it after flashing a Sprint JB ROM nandroid then back to ICS. Such a werid issue.

Why flash a Sprint ROM on an ATT phone though?

NYYFan02 said:
Why flash a Sprint ROM on an ATT phone though?
Click to expand...
Click to collapse
Because its the only official US Jelly Bean released at the moment.
It was one of the many backups I had. Don't know why it fixed it but it did.

I have the same issue. Now to flash a stock rom using Odin, do you have to use the toolkit? Also where can I download a Rogers stock rom from?

finally after losing gps and reading thread after thread got it to work , thank you to the guys that personally try to help , dont know why it struck this time but it did , now i will try to bring it back to stock , again thanks , by the way the rom i was using to bring it back was serenity 1.1 which i use before but wouldn't stick...:good:

xtwo said:
I have the same issue. Now to flash a stock rom using Odin, do you have to use the toolkit? Also where can I download a Rogers stock rom from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1968625
Canadian roms are on page 2

Gps still not working
I downloaded the stock Rogers rom and using Odin through toolkit I flashed the stock rom on my Rogers s3. The root is gone and it's back on stock but I still can't use gps. Also now I'm also unable to use ttorents What else can I do to fix this issue?

xtwo said:
I downloaded the stock Rogers rom and using Odin through toolkit I flashed the stock rom on my Rogers s3. The root is gone and it's back on stock but I still can't use gps. Also now I'm also unable to use ttorents What else can I do to fix this issue?
Click to expand...
Click to collapse
If your problem started after installing a Sprint-based ROM, then root your phone, install CWM and then install that same Sprint ROM. Your GPS will probably work after that. You can then restore a Nandroid backup of another ROM. That's how a lot of us were able to fix our GPS.
Sent from my SGH-T999 using xda app-developers app

thanks for figuring this out, I've been struggling to get it working a few days now
Sent from my SGH-I747 using xda app-developers app

GPS not working on SlimKat 4.4.4

Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo

drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
Hi, the link you provided points to build 4. You can find build 9 which is the latest slimkat here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
This is the one I have for my Koodo I747M. *note camera seemed a little buggy in some instances, so I installed open camera. Seemed to work a lot better.

I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?

drakemiller40 said:
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
Click to expand...
Click to collapse
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?

serathe said:
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
Click to expand...
Click to collapse
Im not very experienced lol and got lost on:
"The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course. "
I'm using TWRP

Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.

serathe said:
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
Click to expand...
Click to collapse
Yeah I always create a nandroid and backup my IME.

drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
First thing to try for GPS problems is taking off the back cover and snugging up all the little screws around the phone. Sometimes they work their way loose and the GPS antenna seems to be the first thing to suffer from it.
If that doesn't cure it you might need to flash a stock or at least stock based ROM and rebuild the nvram. Here's a link that describes how to do that if you need to.

GPS NOT locking but still showing available satellites

It used to work but just noticed today it isn't any more. GPS will still find me, but it won't travel along with me in google maps and none of the satellites lock on using GPS toolbox. It shows 20 or more satellites available but none lock. If I do a search for nearby places it gets it right every time but it won't lock on to any satellites. I am rooted, I tried changing the rom and even loading a fully stock one and it still isn't working. I don't get how some of this stuff will work but I can't get any full lock.
Is this likely a device issue or something that I can fix?

I am also having this issue with my Pixel (non XL). Next weekend I will try and reset the device but I have had this issue for a few months now. I am not sure if it's software or a hardware problem.

JAYNO20 said:
It used to work but just noticed today it isn't any more. GPS will still find me, but it won't travel along with me in google maps and none of the satellites lock on using GPS toolbox. It shows 20 or more satellites available but none lock. If I do a search for nearby places it gets it right every time but it won't lock on to any satellites. I am rooted, I tried changing the rom and even loading a fully stock one and it still isn't working. I don't get how some of this stuff will work but I can't get any full lock.
Is this likely a device issue or something that I can fix?
Click to expand...
Click to collapse
Did you change kernels as well.
Way back in the day I had an issue like you described and the only way to resolve was to restore backup in which gps worked.
Then fire up phone confirm GPS lock. Then do all the flashing.
The only solution I ever knew to this issue was to restore a backup or start over from factory images.

parakleet said:
Did you change kernels as well.
Way back in the day I had an issue like you described and the only way to resolve was to restore backup in which gps worked.
Then fire up phone confirm GPS lock. Then do all the flashing.
The only solution I ever knew to this issue was to restore a backup or start over from factory images.
Click to expand...
Click to collapse
Yeah I changed the kernel. I tried completely unrooting and flashing a fully stock roms (March and April ROM) then reflashing the rooted rom I'm on (pure nexus) and even a non stock kernel (ElementalX) and it still won't lock.

JAYNO20 said:
Yeah I changed the kernel. I tried completely unrooting and flashing a fully stock roms (March and April ROM) then reflashing the rooted rom I'm on (pure nexus) and even a non stock kernel (ElementalX) and it still won't lock.
Click to expand...
Click to collapse
I assuming no back up then if you didnt restore that.
In my experience i dont recall flashing the stock rom alone enough to undo the change to the kernel that screwed up GPS.
It wouldnt lock on stock rom?
try flashing stock kernel by itself maybe?

parakleet said:
I assuming no back up then if you didnt restore that.
In my experience i dont recall flashing the stock rom alone enough to undo the change to the kernel that screwed up GPS.
It wouldnt lock on stock rom?
try flashing stock kernel by itself maybe?
Click to expand...
Click to collapse
Hey,
Flashing stock firmware actually includes the stock Kernel by the way. :good:
Cheers...

It didn't lock on any of the stock roms I flashed (which as user 5.1 stated included the stock kernel) but it used to work fine before on stock roms and even on pure nexus at one time. Not sure what happened or why it just stopped locking onto satellites.

JAYNO20 said:
It didn't lock on any of the stock roms I flashed (which as user 5.1 stated included the stock kernel) but it used to work fine before on stock roms and even on pure nexus at one time. Not sure what happened or why it just stopped locking onto satellites.
Click to expand...
Click to collapse
Hey,
I don't think it will fix it, since several ROMs didn't... But did you try reverting to an older version which used to work. You likely did it already. Just in case you didn't...
Otherwise you may try contacting Google or whom you bought your device, report your issue and see if they are already aware of the situation with others users maybe? As it sounds like a hardware issue...
Looks like you are far of being alone here: https://www.google.fr/search?q=goog...j0l2.8956j0j4&sourceid=chrome-mobile&ie=UTF-8
Good luck...

5.1 said:
Hey,
I don't think it will fix it, since several ROMs didn't... But did you try reverting to an older version which used to work. You likely did it already. Just in case you didn't...
Otherwise you may try contacting Google or whom you bought your device, report your issue and see if they are already aware of the situation with others users maybe? As it sounds like a hardware issue...
Looks like you are far of being alone here: https://www.google.fr/search?q=goog...j0l2.8956j0j4&sourceid=chrome-mobile&ie=UTF-8
Good luck...
Click to expand...
Click to collapse
Yup I did try that already. I am ordering a replacement tonight.