Develop Bugs

Fix for GPS loss after flashing UVDLJC modem

Solution to GPS loss after flashing this modem with some other ROMs:
1. Download the latest CM10.1 nightly for T999 and the lastest GAPPs for the CM10.1 (both files can be found in cyanogenmod.com)
2. Odin Stock Deodexed Official T999UVDLJA +Root
http://forum.xda-developers.com/show....php?t=1991255
3. Odin recovery (TWRP)
Note- do not make phone make a full reboot after odin twrp. The stock recovery might write over the flashed twrp. So remove battery of phone when rebooting.
4. Manually reboot to recovery by pressing simutaneously the home, volume up and on button. Release on button and keep pressing home and volume up button when phone vibrates.
5. In recovery (twrp), wipe cache, factory wipe, system and dalvik.
6. Flash CM10.1 nightly then GAPPs.
7. Reboot phone.
8. Turn on GPS and turn on navigation. A flashing GPS icon should appear on the navigation bar of your phone. This means your GPS has been fixed.
You can now flash whatever ROM you like. I flashed my favorite Frosty.
Thank button please it this helps..

kusgan said:
Solution to GPS loss after flashing this modem with some other ROMs:
1. Download the latest CM10.1 nightly for T999 and the lastest GAPPs for the CM10.1 (both files can be found in cyanogenmod.com)
2. Odin Stock Deodexed Official T999UVDLJA +Root
http://forum.xda-developers.com/show....php?t=1991255
3. Odin recovery (TWRP)
Note- do not make phone make a full reboot after odin twrp. The stock recovery might write over the flashed twrp. So remove battery of phone when rebooting.
4. Manually reboot to recovery by pressing simutaneously the home, volume up and on button. Release on button and keep pressing home and volume up button when phone vibrates.
5. In recovery (twrp), wipe cache, factory wipe, system and dalvik.
6. Flash CM10.1 nightly then GAPPs.
7. Reboot phone.
8. Turn on GPS and turn on navigation. A flashing GPS icon should appear on the navigation bar of your phone. This means your GPS has been fixed.
You can now flash whatever ROM you like. I flashed my favorite Frosty.
Thank button please it this helps..
Click to expand...
Click to collapse
This should be stickied, so many people having problems with GPS loss, mainly because people flash a 4.2.x ROM and flash back to a 4.1.x ROM.
Also for step number 1, it can be a ROM of your choice, at least that what I did and GPS worked perfectly fine.
Number 8 has a typo, the flashing GPS icon will appear in the status bar.
Thanks for this, should have a mod sticky this, its very helpful!
|When Emotion Goes Up, Logic Goes Down|

Nice info to have.
In some of my recent posts I helped someone that lost the use of their gps.
I've cut down the steps for myself now as all I have to do is backup my current custom rom, wipe cache/dalvik/system/factory, flash a cm10 rom, boot up and make sure gps works, boot back into recovery then restore the custom rom i was using.
That worked for me and 3 friends 100% of the time now. Sucks but 2 of them just about took their phone in for warranty work for gps issues but my short method fixed em right up.
Regardless it's nice to have options to fix these stupid gps problems so thanks

For question #3, may I ask why stock recovery would overwrite the custom recovery with a full reboot? I wouldn't recommend telling people to pull their battery at all while using Odin. While it seems obvious to most when to pull the battery, it's just a disaster waiting to happen.

Is this to only get GPS back on 10.1? I'm confused lol. I flashed the LJC modem and still have GPS, just installed a TouchWiz rom and still have GPS working... I'm confused.

mt3g said:
Is this to only get GPS back on 10.1? I'm confused lol. I flashed the LJC modem and still have GPS, just installed a TouchWiz rom and still have GPS working... I'm confused.
Click to expand...
Click to collapse
I think he's saying it's a general guide for losing GPS with any rom.
To OP: your time and effort are definitely appreciated, I'm just curious how far this method was tested. For example, did you try using Odin to go back to stock to see if that helped? What methods did you eliminate in the process? I'm wondering if it was more of a coincidence that it worked after going to AOSP, because there really isn't anything different from TW roms that would "fix" GPS. I'm not saying you're wrong by any means, I'm just a little confused as well

Towle said:
I think he's saying it's a general guide for losing GPS with any rom.
To OP: your time and effort are definitely appreciated, I'm just curious how far this method was tested. For example, did you try using Odin to go back to stock to see if that helped? What methods did you eliminate in the process? I'm wondering if it was more of a coincidence that it worked after going to AOSP, because there really isn't anything different from TW roms that would "fix" GPS. I'm not saying you're wrong by any means, I'm just a little confused as well
Click to expand...
Click to collapse
Exactly, from what I've read (why I'm confused) is that the issue is flashing a 4.2 rom then going back to a 4.1 rom, GPS is borked... not using 4.2 then going back to 4.2... Is there another issue at hand that I'm not aware of?

mt3g said:
Exactly, from what I've read (why I'm confused) is that the issue is flashing a 4.2 rom then going back to a 4.1 rom, GPS is borked... not using 4.2 then going back to 4.2... Is there another issue at hand that I'm not aware of?
Click to expand...
Click to collapse
There's no other issue that I'm aware of. Being that 4.2 and 4.1 have very different structures, I always odin root66 before going backwards, and have never experienced GPS issues.

Towle said:
There's no other issue that I'm aware of. Being that 4.2 and 4.1 have very different structures, I always odin root66 before going backwards, and have never experienced GPS issues.
Click to expand...
Click to collapse
I see the GPS thing, it isn't pin pointed, it gets me about 50ft off. ODIN it is, love boring nights like these.

mt3g said:
Is this to only get GPS back on 10.1? I'm confused lol. I flashed the LJC modem and still have GPS, just installed a TouchWiz rom and still have GPS working... I'm confused.
Click to expand...
Click to collapse
Towle said:
I think he's saying it's a general guide for losing GPS with any rom.
To OP: your time and effort are definitely appreciated, I'm just curious how far this method was tested. For example, did you try using Odin to go back to stock to see if that helped? What methods did you eliminate in the process? I'm wondering if it was more of a coincidence that it worked after going to AOSP, because there really isn't anything different from TW roms that would "fix" GPS. I'm not saying you're wrong by any means, I'm just a little confused as well
Click to expand...
Click to collapse
That's what I commented on earlier. It doesn't have to be cm 10.1, just flash the ROM of your choice.
I've actually tried this, but instead of flashing a stock ROM with root, I went back to complete stock without root and my GPS started working as it did before the issue occurred, I the rooted my s3 once again and flashed a custom ROM of my choice (Darthstalker) and my GPS was still working.
I think the problem is going from 4.2.x down to 4.1.x. At least that seems to be the issue. But I'm not sure if GPS would work again if you were to go from 4.2.x to 4.1.x back to 4.2.x.
|When Emotion Goes Up, Logic Goes Down|

707BeastMode707 said:
That's what I commented on earlier. It doesn't have to be cm 10.1, just flash the ROM of your choice.
I've actually tried this, but instead of flashing a stock ROM with root, I went back to complete stock without root and my GPS started working as it did before the issue occurred, I the rooted my s3 once again and flashed a custom ROM of my choice (Darthstalker) and my GPS was still working.
I think the problem is going from 4.2.x down to 4.1.x. At least that seems to be the issue. But I'm not sure if GPS would work again if you were to go from 4.2.x to 4.1.x back to 4.2.x.
|When Emotion Goes Up, Logic Goes Down|
Click to expand...
Click to collapse
Tried from 4.2.x to 4.1.x to 4.2.x. Did not fix...

[Q] android.phone.process problem on most ROMS.

Hi there, I am not new to installing Roms in any way but I accidentally installed a d2lte Liquid smooth ROM instead of what my phone is, a d2att. So when installing the above ROM I did everything what I was supposed to do (clean install, format system). However, whenever I go on any ROM (Such as Quantum or Omni) I get an error as soon as it boots up, and my signal keeps turning on and off. I wiped data, cache and dalvik twice and go to a new ROM and the problem persists. For some odd reason, Carbon ROM works but I need a different one due to battery drain. I've never experienced this problem ever and I was hoping someone could please help me out?

Have you tried re-flashing the modem?

audit13 said:
Have you tried re-flashing the modem?
Click to expand...
Click to collapse
Yes i tried that earlier but still no luck. It's weird though how there was no problem on carbon rom and yet there was a problem when i went back to the Quantum Rom. Something happened on the LiquidSmooth Rom but i don't know what. I will again try reflashing the modem though thank you.
EDIT: Re-flashing modem did not help

Is it possible to use Odin to get back to a completely stock rom? If you have a 4.3 bootloader, you can't use Odin to flash a stock ROM.

A way to get back to a stock ROM for those on the MJB bootloader has been provided by enewman17. See AT&T I747 UCUEMJB Stock Restore in the development forum.

[Q] Mobile Data Problem w/ Kitkat ROMs

Hi all, long time lurker and it's finally come to the point where I don't know what to do about my problem.
I've tried running multiple ROMs, CM10, CM11, AOSP, Carbon KK and for some reason, for each of these ROMs, the data doesn't seem to work. I have full reception and everything works well except I can't seem to get any sort of data transfer.
The only time the data works is when I restock the phone back to ATT I747 UCUEMJB stock ontop of installing the Modem CWM I747UCUEMJB.
I'm currently running AOSB Kitkat 1.2.9
Kernel version 3.4.79-cyanogenmod-g29c22cf
Modem CWM I747UCUEMJB
Any thoughts on how I can fix this data problem?

I am also facing this problme. I have only one ROM with working data is unified version for S3 of Illusion Rom. On SCH-R530U
Sent from my SCH-R530U using Tapatalk

AznBorder11 said:
Hi all, long time lurker and it's finally come to the point where I don't know what to do about my problem.
I've tried running multiple ROMs, CM10, CM11, AOSP, Carbon KK and for some reason, for each of these ROMs, the data doesn't seem to work. I have full reception and everything works well except I can't seem to get any sort of data transfer.
The only time the data works is when I restock the phone back to ATT I747 UCUEMJB stock ontop of installing the Modem CWM I747UCUEMJB.
I'm currently running AOSB Kitkat 1.2.9
Kernel version 3.4.79-cyanogenmod-g29c22cf
Modem CWM I747UCUEMJB
Any thoughts on how I can fix this data problem?
Click to expand...
Click to collapse
So I actually got it working and it was a weird fix... I've been using ATT_I747_UCUEMJP_StockRestore_2282014.zip to bring it back to stock and then using the rooting system from that stock rom.
My friend suggested to try using another root, so I brough it back to CF-Autoroot and it works. Not sure why... but maybe give it a try if your using that stock rom?

Can't get data on AOSP roms

OK guys let's see if you can help me out here. The problem I am having is any aosp based ROM I flash I cannot get data to load. The cm based rom , deviant rom or aicp ROM. Here's what I've tried so far, I've tried coming from zone ROM doing the typical wipes in recovery with no luck. I've tried loading from my stock back up with no luck. Then I tried flashing the M modem and still no go. Last thing I tried was backing up EFS on zone since data works on that then flashing on aosp with no data. Has anyone else came a crossed this nagging issue ? [emoji20]

Rinkle McBally said:
OK guys let's see if you can help me out here. The problem I am having is any aosp based ROM I flash I cannot get data to load. The cm based rom , deviant rom or aicp ROM. Here's what I've tried so far, I've tried coming from zone ROM doing the typical wipes in recovery with no luck. I've tried loading from my stock back up with no luck. Then I tried flashing the M modem and still no go. Last thing I tried was backing up EFS on zone since data works on that then flashing on aosp with no data. Has anyone else came a crossed this nagging issue ? [emoji20]
Click to expand...
Click to collapse
Honestly your best bet is ask in those threads as many of us are not running aosp.
BAD ASS G3

Rinkle McBally said:
OK guys let's see if you can help me out here. The problem I am having is any aosp based ROM I flash I cannot get data to load. The cm based rom , deviant rom or aicp ROM. Here's what I've tried so far, I've tried coming from zone ROM doing the typical wipes in recovery with no luck. I've tried loading from my stock back up with no luck. Then I tried flashing the M modem and still no go. Last thing I tried was backing up EFS on zone since data works on that then flashing on aosp with no data. Has anyone else came a crossed this nagging issue ? [emoji20]
Click to expand...
Click to collapse
I'm sure you found the answer by now but in case you didn't you have to change your APN to ipvp6 to get data

I don't know where it was but I saw a post saying that you have to change it to ipv6 or something. It was on the development thread.

Camera Error after downgrade

I've been jumping lately between various AOSP Jellybean roms, and Lollipop roms without issue on my I747m. Now, I'm upgrading my phone and want to give my S3 to my dad. He will just make basic calls and take pics. I want him to be on Touchwiz as i think the camera will be best for him in that regard.
I've tried 3 TW roms in a row, and they all give me the same error, "cannot connect to camera", as if another app is using the camera. Going back to my usual AOSP/CM roms in between attempts show the camera to work just fine. While on the touchwiz roms, I've cleared the camera cache, pulled the battery, etc etc... all the usual stuff. These are full wipes, clean installs with absolutely nothing being done to the phone (not even downloading an app). I install the ROM, wait a few minutes, then try the camera to no avail.
Any thoughts on what could be doing this? I have gone to touchwiz roms in the past (briefly) with no issue, but haven't tried in quite some time. I'm on the MK5 bootloader, if it matters.
Thanks.

Holmes108 said:
I've been jumping lately between various AOSP Jellybean roms, and Lollipop roms without issue on my I747m. Now, I'm upgrading my phone and want to give my S3 to my dad. He will just make basic calls and take pics. I want him to be on Touchwiz as i think the camera will be best for him in that regard.
I've tried 3 TW roms in a row, and they all give me the same error, "cannot connect to camera", as if another app is using the camera. Going back to my usual AOSP/CM roms in between attempts show the camera to work just fine. While on the touchwiz roms, I've cleared the camera cache, pulled the battery, etc etc... all the usual stuff. These are full wipes, clean installs with absolutely nothing being done to the phone (not even downloading an app). I install the ROM, wait a few minutes, then try the camera to no avail.
Any thoughts on what could be doing this? I have gone to touchwiz roms in the past (briefly) with no issue, but haven't tried in quite some time. I'm on the MK5 bootloader, if it matters.
Thanks.
Click to expand...
Click to collapse
I can think of a couple of things that may help.
MK5 is a 4.3 bootloader and modem. Were the TouchWiz ROMs you flashed Android 4.3 or KitKat ROMs? If they were Kitkat, Android 4.4.2, then the fix may be as simple as flashing the ROM and then flashing one of the custom kernels, either ibuddler's, found in the OP of the Likewise ROM, or the TW kernel by ktoonsez.
If you were flashing a 4.3 TW ROM, or if the custom kernel did not help with a 4.4.2 ROM; then you may need to flash a stock MK5 ROM, followed with a factory reset from the stock recovery. After that flash the custom recovery of your choice, root, and flash the TW ROM you like best.

dawgdoc said:
I can think of a couple of things that may help.
MK5 is a 4.3 bootloader and modem. Were the TouchWiz ROMs you flashed Android 4.3 or KitKat ROMs? If they were Kitkat, Android 4.4.2, then the fix may be as simple as flashing the ROM and then flashing one of the custom kernels, either ibuddler's, found in the OP of the Likewise ROM, or the TW kernel by ktoonsez.
If you were flashing a 4.3 TW ROM, or if the custom kernel did not help with a 4.4.2 ROM; then you may need to flash a stock MK5 ROM, followed with a factory reset from the stock recovery. After that flash the custom recovery of your choice, root, and flash the TW ROM you like best.
Click to expand...
Click to collapse
I had tried both 4.1 and 4.4 rom. Thanks for the tips though. I'll def look into all of that. I appreciate it!