[Q] Did I lose root? (stock to slimkat) - Sprint Samsung Galaxy S III

I recently switched over to slimkat version 8.10 and everything is working like butter so far. The only issue I have come across is anything that needs superuser permissions automatically gets denied. It shows the option on the screen to allow but when i click the field it just does not select., landscape or vertical. I aleady followed the steps to enable developer mode and turn on root access. What could be happening to cause this? It always takes me an hour to configure everything the way i like it so reinstalling would be the last thing I would ever want to do.

I just attempted to use Odin to install cf-auto-root. Still not working. I guess I might opt for the final option... wipe and reinstall rom.

Try flashing supersu from here in recovery:
Super SU 2.16
https://plus.google.com/app/basic/stream/z13tvntrmsmozdc2023wcdp55terwvove

Somehow 2.13 was included with the cf-autoroot that I installed via odin. I did install 2.16 through recovery but I am still having this problem. I mean it doesn't really hurt the usage of the phone... everything is working flawlessly. This is just a rock in my shoe. The only thing I can think might be causing me an issue is that I flashed the dkp kernel. Could that be it?

When you flashed dkp did you clear cashe and dalvik?

Related

[Q] GAAPs seem to break WiFi in CM 10.1 RC2

[EDIT] I meant GAPPs. Damnit.
Hello,
I'm at a loss for what's happening and how to fix it. My GoogleFU is failing and nothing I try seems to work.
Basically, WiFi does not work for me in CM 10.1 RC2 and it's something to do with the GAAPs. Everything is initially fine on a fresh install [edit: I don't know if it matters, but when I flash the latest milestone of AOKP WiFi never works. At the initial set up it connects but fails to authenticate over and over] and it's all going swimmingly at first. When I open the Playstore in these first few moments, it's the last version. Eventually the Playstore updates itself and that's when WiFi stops working. Nothing can connect to anything. In the Playstore I just get a 'failed to connect' message and a 'retry' button that doesn't work. The browser doesn't pull anything up and I can't get any sort of connection until I turn WiFi off and go to data.
I'm really at a loss. If it helps, I'm on the Sasktel version, but it's still the I747 [i747m in the stock ROM] which is the same as Bell/AT&T, right? So that shouldn't matter. I'm flashing the 20130301 GAAPs and even tried the 4.1.2 ones (they didn't work at all). I'm using CWMR 6.0.1.2. I can't figure out what I'm doing wrong. Any advice at all would be greatly appreciated. I don't know why I'm having so much trouble with ROMs on my S3 when it was so much easier to root than my old One V (which is still running CM 10 like a champ with 0 errors - I gave that phone to my sister).
Sorry for the long post, but this has been melting my brain.
so what all are you wiping before these flashes? i would recommend data, cache, dalvik, format /system, format /data when changing ROMs and especially when changing android versions (4.1 to 4.2, etc). If you have a micro sd card, place your ROM, gapps and a backup on there and go through the above wipe procedures.
you should also consider updating your recovery. 6.0.3.1 is the latest. you can flash this in recovery, go to Advanced and reboot recovery for this to take effect.

[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!

[Q] Reboot issue on 4.3 roms

Here is my problem on 4.3 roms, i have no trouble installing them and the load up perfectly but after i do a restart i cant get past the boot screen. It does it on all 4.3 roms, i have the latest twrp recovery latest modem and stuff everything is up to date only have this problem on 4.3 ive formatted the internal storage numerous times and always followed op instructions. i cant find anyone else with this problem any help is appreciated tia
The only time I had this issue was after I changed font in Rom Toolbox. How are you wiping?
sent from my GS3 running Illusion4.3
joeyhdownsouth said:
The only time I had this issue was after I changed font in Rom Toolbox. How are you wiping?
sent from my GS3 running Illusion4.3
Click to expand...
Click to collapse
im using twrp first i tried to factory reset, caches that didnt work i formated internal storage same problem everything works great untill i restart the phone then wont go past boot screen. like its not reading the internal drive even did fix permisions and wiped caches after install. Also i used the updated su to flash after still problems, beyond me no problems with older ones or tw just the 4.3 roms
I, also, am having this very same issue. I'm honestly surprised that noone else seems to have run across this issue.
Installing is never an issue, running is never a problem, but if I ever reboot, if a ROM reboots itself, I'm left stuck at the GalaxyS4 splash screen, and the only way out it to Wipe everything and reinstall.
I see youre posting from an S3, I am using an AT&T S4.
Clearly, the issue is related to 4.3...
I had that problem with an unofficial build. But that was a bad download. Do you have new phones? The mount points are different on the newer sg3's. There's a thread with a fix for that
i had that problem. for some reason it locks your recovery and internal storage. you have to wipe it and install a rom via odin to work again. thats why im staying away from 4.3
i got my phone last december so its not real new, guess Ill just stay away from 4.3 roms. my recovery never got locked it just wont boot back up after restart. thanks for all the ideas

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] Updated to 4.3, now GApps continuously force closes

I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.

Categories

Resources