Modded NFC, Root, and Updates - Sprint Samsung Galaxy S III

I have a SPH-L710. I've rooted it and patched the NFC.apk using the mod here. Its giving me problems, though (such as NFC stopping, and having to be toggled before it reads tags again), and I want to revert to stock. However the stock NFC.apks he has listed are for VPALEN only - I appear to be running VPALF9. I don't want to make things worse.
Additionally, (and I don't know if this is related to the NFC mod, or the root) but whenever I get an OTA update, it appears like its installing in CWM, but returns a message that the signature was invalid.
I was thinking about CM9 on my phone - will this potentially solve the issues I'm seeing, or make them worse? The CM9 page recommends I return my phone to stock before rooting via their method and flashing - will bringing it back to stock (hopefully) restore the stock NFC.apk?

Related

Wi-Fi and GPS Keep Engaging

I've searched the forum and can't see a solution to this problem.
My wi-fi keeps turning on even though I have switched it off and even if I put the phone in airplane mode, it switches back in.
Also, the GPS constantly tries to engage. The warning pops up which says, "By selecting "Standalone GPS Services", you are enabling access to all location information..." and it has 'disagree' and 'agree' at the end. If I click 'disagree' it goes away then reappears a short time later. If I click 'agree', the GPS goes on.
I have run an virus check which was negative.
I have ICS build 4.1.B.0.587 and it has recently been rooted.
I tried locking wi-fi with some software, but that didn't work.
Any ideas anybody?
if your phone is non-modded (custom kernel, rom etc.) re-install the firmware you're currently using by re-flashing it via flash tool 6 or higher..
if it is modded (root, rom, kernel etc.) re-flash the kernel or change it/re-flash the rom or change it
MrModMan said:
if your phone is non-modded (custom kernel, rom etc.) re-install the firmware you're currently using by re-flashing it via flash tool 6 or higher..
if it is modded (root, rom, kernel etc.) re-flash the kernel or change it/re-flash the rom or change it
Click to expand...
Click to collapse
Thanks MrModMan, I did as you recommended. My phone was rooted, so I downgraded the kernel again (using the LT18i downgrade as I was told that this would be OK on my LT15i by another member), re-rooted using the DooMLorD tool, then flashed the kernel again (using the LT15i ftf for .587 build).
The problem still exists.
I suspected that it may relate to an app which uses GPS/Wi-fi connectivity, maybe Google Maps. I backed up Google maps, then uninstalled using Titanium Backup, but the problem's still there.
Here's an update. I reinstalled the latest version of ICS and have not rooted my phone, The phone is not now reconnecting to wi-fi and the GPS nag screen has stopped appearing, so evidently there is something wrong with the rooting procedure that I used for the .587 build of ICS. I can say that I did follow the procedure outlined on this forum to the letter. Maybe somebody with more technical know-how can determine what the problem is.

[Q] Auto Rotate not working

I just recently rooted my i747 using the No Trip Counter method using ODIN and the stock ROM with root injected into it already. I had a fair amount of stuff frozen with TiBu but nothing on the "unsafe" list. I made sure screen rotation was on, tried to calibrate via the motion settings (little blue dot didn't move at all), even tried battery pulling, reflashing the ROM, wiping the cache, clearing the cache for System UI and Touchwiz. I don't have a custom recovery flashed. I flashed the unrooted stock ROM and called up AT&T. I've got a new device that auto rotate works now but a bit hesitant to re-root. Has anyone heard of this feature being disabled due to something done during/after root? I've Googled my butt off but couldn't find any issues related to rooting.
Note: I got jumped over the weekend and my phone was swiped. It was later returned to an AT&T store but who knows what it went through. That's my guess as far as why it didn't work anymore (probably thrown/dropped/who knows what) but I just wanted to see if there was a possible software issue that I may not have been able to find.
Cheers!

Proper GPS fix

I've seen quite a few "flash back to stock, then flash AOSP" fixes to get your GPS working. All you have to do to really fix the GPS is:
1. Backup your stock ROM's EFS through your recovery. (Do NOT wipe prior to doing this.)
2. Wipe
3. Flash AOSP based ROM.
4. Restored your ROM's EFS through your recovery's advanced restore.
Done.
GPS is my ROM's Bane!
ivanmmj said:
I've seen quite a few "flash back to stock, then flash AOSP" fixes to get your GPS working. All you have to do to really fix the GPS is:
1. Backup your stock ROM's EFS through your recovery. (Do NOT wipe prior to doing this.)
2. Wipe
3. Flash AOSP based ROM.
4. Restored your ROM's EFS through your recovery's advanced restore.
Done.
Click to expand...
Click to collapse
So, I am having a GPS issue that I've been unable to solve through any of the numerous method's posted around XDA (my primary source of all things android) and related sites. It could be a simple solution, but I've exhausted my very limited knowledge and am hoping you have some input or suggestion...
I'm on the LS970 and in an over-caffeinated moment, I fully wiped the stock ROM without a backup. I know that is totally stupid, and have been much more careful with my fingers since then. :silly: I have been unable to get a GPS lock on Spleef's Carbon 4.3 20131020 (or any previous), so tried to factory restore and TWRP flashed a ZV9 ODEX (failed install), ZV7 STOCK (failed install) and SPR-ZVB which flashed successfully but gave me FCs and reboots everytime I opened an app that would get a GPS lock. I have tried the FasterGPS, GPS Status and Toolbox, and edited my GPS.conf. Since I can't get back to factory, I need another way to get to a "factory-enough" for a GPS lock...
Any ideas? I think maybe there's a path/process to follow to be able to go from AOSP to stock that I'm not doing, but I have no idea what it is.
Fingers Crossed!
I was having the same issue with Bean Stalk then carbon also. using the app GPS essentials it would show 0 satellites in the sky even though GPS was enabled.
I flashed the Optimized ROM in the DEV section and this did bring back the GPS functionality.
just an FYI since your stock ROM is gone.
etownguy said:
I was having the same issue with Bean Stalk then carbon also. using the app GPS essentials it would show 0 satellites in the sky even though GPS was enabled.
I flashed the Optimized ROM in the DEV section and this did bring back the GPS functionality.
just an FYI since your stock ROM is gone.
Click to expand...
Click to collapse
Fabulous! Thank youuuuuu!
EDIT: Is this it? http://forum.xda-developers.com/showthread.php?t=2468979
Got the GPS Lock!! (Carbon4.3)
etownguy said:
I was having the same issue with Bean Stalk then carbon also. using the app GPS essentials it would show 0 satellites in the sky even though GPS was enabled.
I flashed the Optimized ROM in the DEV section and this did bring back the GPS functionality.
just an FYI since your stock ROM is gone.
Click to expand...
Click to collapse
You have SAVED MY WORLD!! HUURAAAAYYYYY!!!!!! :highfive:
The OpTimized ROM was PERFECT in bringing back my GPS, it locked in seconds. It took me a few tries to get it active on Carbon4.3, so I'm going to give my "steps" for successful completion.
I FULL WIPED before flashing OpTimuS_V4.4 (ODEX) - that's Data, System, Dalvik and Cache. (Obvious? I first ran a full TWRP Backup of the system, data, boot)
Then I flashed, booted, and let it go through its process. It took its own "soft reboot" which I thought would turn "Bootloop" but it did NOT... rebooting to the "Semi Stock OpTimuS" perfectly. It did the "Activate" process on its own.
Then - I went to System Updates. PRL first, then Profile. Then the VITAL UPDATES were Google Maps and Play Services.
After this, I rebooted to let it reacquaint, and then installed FasterGPS, using it to clear the current aGPS. Next, installed FreeGee.
Opening the updated Google Maps, I IMMEDIATELY got the lock, but let it sit for 5 minutes. (reset "display time" to 5 minutes to keep track.)
Next - AFTER the GPS locking for 5 minutes, I did a backup of EFS with FreeGee. If you have PREVIOUS BACKUPS on the Internal Storage, they need to be replaced. This can be easily done with ES File Explorer, or any which allow root access. Go to the active (sdcard on LS970) FreeGee, copy the EFS settings, and replace those in the "/0" or Legacy FreeGee folder.
This may be "overkill" but I went back into Google Maps, got a Lock again, let it sit a few minutes and "tested" the navigation function.
While still in Maps, I powered down. Booting into Recovery (I use TWRP), I ran a RESTORE of my TWRP Backup, since the backups aren't "install" compatible. My fear was the "Restore" would override my updates, but when you run it, just "uncheck" EFS in the restore choices and you're :good:.
My LS970 booted up LOVELY, ran its normal boot process, and when I opened Google Maps .... ~*Aaaaaaaahhhhhh~* light from the Heavens! It locked FAST, and the Nav even worked!!
I have been trying to find this Fix for almost TWO MONTHS so I am on Cloud 9 right now!! Thank You @etownguy!!!
GPS locking issue
Hello all,
I am an intermediate novice at flashing, but Ive gained some knowledge over the recent years here and there. Heres the issue, I am running into the same issue as euphoric fuzion except I have exhausted all that I know. I rooted, unlocked bootloader and flashed my ls970 without creating an official Rom backup or backing up my EFS- I know, not bright of me. After using my new roms I realized that MY GPS isnt locking. So, Ive done everything from writing new NPS locations in gps.conf, attempting to go back to stock via LGNPST-Ive used the auto option, Flash tool and they dont seem to recognize my phone via download mode but the drivers are installed-pc recognizes. One flash tool actually recognizes my phone as another model. Ive tried to flash stock based Roms-one ins particular at no suceess-symlink failure. Attempted to flash ZVC stock based Rom with Firmware flash- the phone remains in bootloop from my previous ROM. In order to use the phone I have to reinstall CM11- my fav for now- but I cannot lock my GPS with out SPrints PRL update, or network update for my profile. Any suggestions? Thanks in advance

[Q] Flashed ROM to 4.3, Nandroid back to 4.1.1, now no camera.

Help, I brokeded my phone trying to use this ROM!
I recently tried to flash the 4.3 Stock MOD ROM to my ATT S3. It wasn't smooth for me so I Nandroided back to 4.1.1. and now my camera does not work and I get an error that says "Cant connect to the Camera" or "Camera failed" depending if I use the Jelly Bean Camera or the Samsung camera.
No fault of the ROM I’m sure but I need help figuring out what I’ve done wrong. I switched back to my Nandroid backup of 4.1.1 Stock because 4.3 was just NO smooth for me. Also I can’t stand regular keyboard, I need my Samsung Note 2 keyboard!
4.3 had a lot of laggy-ness and random crashing. I flashed the Modem, ROM and Kernel in the order with the steps listed per the OP.
When I decided to go back to my backup, I flashed the DLK3 Stock Modem, then flashed back to my backup and wipe the various caches.
Everything about my backup works BUT my camera. I also noticed I can’t use the flashlight option on my 4.1.1 ROM now. Anything related to the camera is broken.
I’ve tried killing and clearing the camera process per several articles I found on Google and here on XDA without luck. Everything suggested it was a hardware issue at that point and to warranty the phone. I deiced to try 4.3 one more time and sure enough, my camera works when flash back to Anroid 4.3 ROM.
I’m stumped.
Any thoughts sort of reinstalling 4.1.1 from scratch?
kdoggy said:
Help, I brokeded my phone trying to use this ROM!
I recently tried to flash the 4.3 Stock MOD ROM to my ATT S3. It wasn't smooth for me so I Nandroided back to 4.1.1. and now my camera does not work and I get an error that says "Cant connect to the Camera" or "Camera failed" depending if I use the Jelly Bean Camera or the Samsung camera.
No fault of the ROM I’m sure but I need help figuring out what I’ve done wrong. I switched back to my Nandroid backup of 4.1.1 Stock because 4.3 was just NO smooth for me. Also I can’t stand regular keyboard, I need my Samsung Note 2 keyboard!
4.3 had a lot of laggy-ness and random crashing. I flashed the Modem, ROM and Kernel in the order with the steps listed per the OP.
When I decided to go back to my backup, I flashed the DLK3 Stock Modem, then flashed back to my backup and wipe the various caches.
Everything about my backup works BUT my camera. I also noticed I can’t use the flashlight option on my 4.1.1 ROM now. Anything related to the camera is broken.
I’ve tried killing and clearing the camera process per several articles I found on Google and here on XDA without luck. Everything suggested it was a hardware issue at that point and to warranty the phone. I deiced to try 4.3 one more time and sure enough, my camera works when flash back to Anroid 4.3 ROM.
I’m stumped.
Any thoughts sort of reinstalling 4.1.1 from scratch?
Click to expand...
Click to collapse
You have to have the bootloaders for 4.1.1 for the camera to work in 4.1.1. This happened to me a while back with 4.1.2. There's a thread here somewhere where you can download the correct bootloaders and flash with ODIN.
EDIT: Here's the thread: http://forum.xda-developers.com/showthread.php?t=2321310
You need the DLK3 bootloaders (well, that is if you have the AT&T gs3) for the camera to work.
jack man said:
You have to have the bootloaders for 4.1.1 for the camera to work in 4.1.1. This happened to me a while back with 4.1.2. There's a thread here somewhere where you can download the correct bootloaders and flash with ODIN.
EDIT: Here's the thread: http://forum.xda-developers.com/showthread.php?t=2321310
You need the DLK3 bootloaders (well, that is if you have the AT&T gs3) for the camera to work.
Click to expand...
Click to collapse
YOU ROCK! You have been thanked.
That completely fixed the issue. I didn't realize the bootloader changed.OK thanks again you saved me a lot of hassle and trouble shooting.

[Q] EACCES, Nandroid issues

I have a i747 phone which is unlocked and being used on the MetroPCS (T-mobile GSM) network. I have rooted the phone using saferoot and installed TWRP as a custom recovery. I have not flashed a custom rom as of yet and I am using build jss15j.i747ucuemjb (JB 4.3) that came with the phone when I purchased it used.
I have flashed mrRobinson-Ashaman.v3.02 debloat tool and opted for the less extreme course when prompted.
I have flashed dkp-tw43-20140426 dkp - d2att kernel so that I could overclock the cpu.
Issues:
The first issue I was having after doing the above is many apps were failing to function properly as they could not access the internal memory(e.g. dropbox, esfile explorer, titanium backup pro). I would receive the prompt eaccess permission denied when the apps would attempt to use either of the internal memory options. I know this problem is common to kitkat but not jellybean. I attempted the fixes suggested for kitkat roms to no avail. Flashing the AT&T Official 4.3 MJB seemed to fix the eaccess problem but it broke wifi. As its probably known here and what I have since learned is that the i747 phone does not fully utilize the T-mobile network making wifi a must until I switch to Aio.
The next issue I was having is with a few of my nandroid back ups. Every time before I tinker with the phone I make a nandroid back up so I have about four currently. After my first issue I decided to try the back up I made before flashing the dkp-tw43-20140426 dkp - d2att kernel to see if that would rectify my eaccess problem with out breaking wifi. After doing a full wipe in TWRP and restoring that nandroid I boot up the phone only to be presented with perpetual prompts of apps and service failures. I go back do a full wipe and restore my first nandroid that I made when I received the phone new. Effectively this is a factory, and fortunately this works. I have made back ups in titanium in addition to the nandroid so if the simplest solution is simply a custom rom I am receptive to trying it. I have interest in a custom rom but what is most important to me is stability, speed and the ability to overclock and so any suggestions for roms that fit these parameters would be appreciated.
Thanks in advance for all your help
efaustus9 said:
I have a i747 phone which is unlocked and being used on the MetroPCS (T-mobile GSM) network. I have rooted the phone using saferoot and installed TWRP as a custom recovery. I have not flashed a custom rom as of yet and I am using build jss15j.i747ucuemjb (JB 4.3) that came with the phone when I purchased it used.
I have flashed mrRobinson-Ashaman.v3.02 debloat tool and opted for the less extreme course when prompted.
I have flashed dkp-tw43-20140426 dkp - d2att kernel so that I could overclock the cpu.
Issues:
The first issue I was having after doing the above is many apps were failing to function properly as they could not access the internal memory(e.g. dropbox, esfile explorer, titanium backup pro). I would receive the prompt eaccess permission denied when the apps would attempt to use either of the internal memory options. I know this problem is common to kitkat but not jellybean. I attempted the fixes suggested for kitkat roms to no avail. Flashing the AT&T Official 4.3 MJB seemed to fix the eaccess problem but it broke wifi. As its probably known here and what I have since learned is that the i747 phone does not fully utilize the T-mobile network making wifi a must until I switch to Aio.
The next issue I was having is with a few of my nandroid back ups. Every time before I tinker with the phone I make a nandroid back up so I have about four currently. After my first issue I decided to try the back up I made before flashing the dkp-tw43-20140426 dkp - d2att kernel to see if that would rectify my eaccess problem with out breaking wifi. After doing a full wipe in TWRP and restoring that nandroid I boot up the phone only to be presented with perpetual prompts of apps and service failures. I go back do a full wipe and restore my first nandroid that I made when I received the phone new. Effectively this is a factory, and fortunately this works. I have made back ups in titanium in addition to the nandroid so if the simplest solution is simply a custom rom I am receptive to trying it. I have interest in a custom rom but what is most important to me is stability, speed and the ability to overclock and so any suggestions for roms that fit these parameters would be appreciated.
Thanks in advance for all your help
Click to expand...
Click to collapse
I installed the rom Dandroid 5.4 and every thing works as expected. I may try to flash the decimalman's dkp - d2att kernel again to see if I can get a bit more speed out of the device but all in all it works well. Still not sure what was the cause of my two issues with the rooted stock rom.

Categories

Resources