Database Info

[Q] NEWB mistake

New to android here
Rooted phone cause of battery life
I have AntTek App Manager
Watchdog Lite
and other cool/fun apps
Now, I did an update on my apps the other day and looked at all the apps that are currently running (got obsessed with killing apps so i can extend my battery life).
All these new things were running (didnt want to touch them until I googled them).
I froze FlexProvider 1.0.0 which wasnt a good idea. Rebooted the phone and still not functioning the way it used to... Click on browser and I have to force close it. I defrosted FlexProvider and browser still isnt working... another kicker, Im getting no data connection as well on tmo. I connect WiFi and I get everything, except browser.....
Now, before I do a factory reset... is there a way to fix this before I do that drastic route (that is if that would work). Secondly, i use shopsavvy and I dont want to lose the things I scanned and saved. I've been lookin online wondering where that gets saved JUST in case the phone has to be brought back to OEM...
Any guidance or assistance would be greatly appreciated....
thank you
forgot to mention... when i reboot the phone, in the beginning upon boot up com.lge.omadmclient has stopped exptedly comes up when you unlock the phone

Thaw the apps you froze and it may recover just fine. FlexProvider is required to transfer data to and from the device, hence the browser FC and no data connection.

U should be fine but you shouldve done some research on this forum before just freezing apps
Sent from my LG-P999 using Tapatalk

r4d14n7 said:
Thaw the apps you froze and it may recover just fine. FlexProvider is required to transfer data to and from the device, hence the browser FC and no data connection.
Click to expand...
Click to collapse
Done that, still no go. Researched app before I froze but did not see anything about it doing this (saw a post about it outside of this site, sorry).
Any other suggestions? Would you guys know where shopsavvy saves the scanned images

Not too good at troubleshooting here. The only help I can give at this point is to flash ClockworkMod and restore the rooted stock nandroid image in the development section.

r4d14n7 said:
Not too good at troubleshooting here. The only help I can give at this point is to flash ClockworkMod and restore the rooted stock nandroid image in the development section.
Click to expand...
Click to collapse
Unless there is a ROM there (not image). Then you could simply flash over it. I would format /system before you do that if you can find one (plus wipe cache and dalvek).

thank you all
I have decided to factory wipe it. Too scared to go through all of that and possibly brick the phone..
I want to thank you all for your input though...

Question about TWRP.

I just got TWRP installed with the awesome help of gunnyman and now i'm on to my next step on my way to a custom rom. Which (correct me if i'm wrong) is making a backup.
TWRP is very user friendly..but not enough for me sadly. When I'm making a backup there are several check boxes of what to backup and I'm not sure which ones should be checked. Could anyone help me with that?
Also the backup will be stored on my sd card, which on the one x is internal..so its safe or what? Should I put on on dropbox just in case? Is there any reason after loading a custom rom that my backup would no longer be available or not work?
Are there any other steps between the backup and installing the custom rom.
annnddd one last question. This part of the cleanrom post scares me.. can someone explain what it means? Will this leave my phone unable to connect to 4g?
Special GSM Patch:
Removes the AT&T 4G Icon and reverts to standard GSM "H" Icon.
Unlocks the Hotspot in its entirety so ALLLLLLL people can use it regardless of carrier!
Wait for it... Unlocks the magical LTE Toggle capability. Does not work on AT&T but does work on all other carriers AFAIK.
This patch CAN be applied to ATT if you want. It wont hurt anything that I know of. I was also told that if you manually program APN's that you can toggle the LTE toggle on ATT. I gave up on testing this but it did work a couple times for me but I could not get it consistent. If you can help the community figure it out for ATT then lets do it!
Click to expand...
Click to collapse

PhatCrits said:
I just got TWRP installed with the awesome help of gunnyman and now i'm on to my next step on my way to a custom rom. Which (correct me if i'm wrong) is making a backup.
TWRP is very user friendly..but not enough for me sadly. When I'm making a backup there are several check boxes of what to backup and I'm not sure which ones should be checked. Could anyone help me with that?
Also the backup will be stored on my sd card, which on the one x is internal..so its safe or what? Should I put on on dropbox just in case? Is there any reason after loading a custom rom that my backup would no longer be available or not work?
Are there any other steps between the backup and installing the custom rom.
annnddd one last question. This part of the cleanrom post scares me.. can someone explain what it means? Will this leave my phone unable to connect to 4g?
Click to expand...
Click to collapse
Just use all the default options at first. Don't worry about what boxes are checked and all that. Go in and do a backup. Go back out and do a wipe I think on twrp its called factory reset, data and cache. Then wipe dalvik cache. Then rinse and repeat just for the heck of it. Then go and install the rom and reboot. Set things up and let things ssettle in. Then if you want go flash any mods such as battery percent and wifi tether. don't bother with the GSM patch just yet. You probably won't need or want it anyways.
Your backup should be fine on the phone but I always copy NY first to my PC. Dropbox would take too long for me. It's about a gig. I actually erase all my backups off the device once I realise I don't need it.
Sent from my HTC One X using xda app-developers app

Also the Nandroid backups are too big to upload to Dropbox. I've tried.
The GSM patch just changes your icons for data (ie LTE, H+, 3G, etc).
Sent from my HTC One X using xda app-developers app

[Q] [HELP] AT&T broke my phone (for now)

In an attempt to collect more data for this: http://forum.xda-developers.com/showpost.php?p=50666286&postcount=192, I made a new backup, and began restoring previous backups to identify when I had good WiFi speeds. I restored my stock ROM backup, and before I could even run any speed tests, AT&T jammed an update down my throat. No way to abort/postpone. Needless to say, I'm stuck in recovery. No matter which backup I restore, I can't get anywhere. My thoughts are that the update file is still somewhere on the phone, which is why nothing will get me past recovery. Does anybody know what the file is called and where it would be located? I'd like to exhaust every option before resorting to completely wiping everything.
Other thoughts: Is it possible to flash the stock recovery by itself? This would at least allow the update to happen.
Thanks.

What recovery are you using? This might help if you're using TWRP.

cron912 said:
What recovery are you using? This might help if you're using TWRP.
Click to expand...
Click to collapse
Perfect. Thank You.

Glad you got it working I don't know why carriers and lg find it okay to push updates to our device really without asking I've heard where people say no to the update and it installs it anyway I think its a bad business practice
Sent from my LG-VS980 using Tapatalk

[Q] Samsung Galaxy S3 Derp.

First I'd like to say hello to all. I've been looking for the most comprehensive android discussion forum, and I think I hit the jackpot here. Anyway to the point. As it is known by the pros here, The S3 comes from your telecom company loaded with your personal connection info. From what I've read recently, the carriers either don't know how, or simply wont backup the nv and efs data to the onboard chips to preserve it in case of software failure, or mod failure. I did find an article with google explaining that a couple of devs discovered the fix for this inside the bootloader that we can use to force that backup to happen like it should, and it works. I've flashed several times since that backup and not lost the data from the phone. When I install cyanogen mod 11, it does not read those 2 particular memory blocks on booting, thus cyanogenmod does not recover the imei data from the onboard backup, even after a factory reset. I really would like to see if there is a workaround for that because unfortunately for me, any other method for backup is illegal where I live. If I flash back to stock rom, It reads the data back out of the chip, and restores my connection data for the carrier to the efs partition as well as the other 3 displayed in EFS Backup Pro. But I really like cyanogenmod, and since one of it's developers worked at Samsung, I'm really hoping my question finds an answer here.
So my question is is anyone familiar enough with the Cricket version of the S3 and cyanogenmod to tell me of a workaround for that problem if it exists. Thanks in advance for the community's responses.

Did You used the "cricket" Version of cyanogenmod?
Sent from my loved HTC One S using buggy Tapatalk 0.o

LS.xD said:
Did You used the "cricket" Version of cyanogenmod?
Sent from my loved HTC One S using buggy Tapatalk 0.o
Click to expand...
Click to collapse
I used the cyanogenmod installer to install. From what I've read, the universal installer detects my phone and installs the correct version. Also I think that all s3 builds are now unified, so that's not an issue. Tried 10.2 after that, and caused my self more problems than I needed to fix, so I flashed back to stock. But I am going to attempt the mod again after backing up efs and nv if I have to. I can only run 4.3 or 4.4 android, which means I can only run 10.2 or 11 on my phone, or it will nuke the bootloader and hard brick my phone.

Corny007 said:
I used the cyanogenmod installer to install. From what I've read, the universal installer detects my phone and installs the correct version. Also I think that all s3 builds are now unified, so that's not an issue. Tried 10.2 after that, and caused my self more problems than I needed to fix, so I flashed back to stock. But I am going to attempt the mod again after backing up efs and nv if I have to. I can only run 4.3 or 4.4 android, which means I can only run 10.2 or 11 on my phone, or it will nuke the bootloader and hard brick my phone.
Click to expand...
Click to collapse
http://download.cyanogenmod.org/?device=d2cri
Sent from my loved HTC One S using buggy Tapatalk 0.o
---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------
This is the cricket Version
Sent from my loved HTC One S using buggy Tapatalk 0.o

Versions are correct. Its not a version problem, it's an implementation problem where cm10.2 or 11 does not read the memory blocks that store the eps and nv data. Stock rom from cricket will read them and restore nv data from the chips. (I am not referring to the efs folder that can be seen as root. Im referring to the data stored in the 2 chips that Samsung and Cricket don't tell you about. Normally a corrupted efs folder is backed up from there because no one backs it up first. Google "Samsung derp" and you will find the article I found that explains this. People lose their efs because they don't know this about the knox system, and that it's not backed up properly. When you do not do " su nvbackup" then you lose your number. You do he nv backup procedure correctly and it backs up your current efs, then it's automatically restored whenever you flash a rom that reads those blocks. Cyanogenmod does NOT read those blocks to rebuild the efs/nv data. If it did, then when I do the factory reset after flashing, my phone would work right after the reset, but it does not. Neither version 10.2 nor 11.x reads those blocks.on reboot.

Corny007 said:
Versions are correct. Its not a version problem, it's an implementation problem where cm10.2 or 11 does not read the memory blocks that store the eps and nv data. Stock rom from cricket will read them and restore nv data from the chips. (I am not referring to the efs folder that can be seen as root. Im referring to the data stored in the 2 chips that Samsung and Cricket don't tell you about. Normally a corrupted efs folder is backed up from there because no one backs it up first. Google "Samsung derp" and you will find the article I found that explains this. People lose their efs because they don't know this about the knox system, and that it's not backed up properly. When you do not do " su nvbackup" then you lose your number. You do he nv backup procedure correctly and it backs up your current efs, then it's automatically restored whenever you flash a rom that reads those blocks. Cyanogenmod does NOT read those blocks to rebuild the efs/nv data. If it did, then when I do the factory reset after flashing, my phone would work right after the reset, but it does not. Neither version 10.2 nor 11.x reads those blocks.on reboot.
Click to expand...
Click to collapse
Looked at this already? --> Backup + Restore EFS SIII

I'm not sure how, but I'm up and dialing.
LS.xD said:
Looked at this already? --> Backup + Restore EFS SIII
Click to expand...
Click to collapse
Sorry I didn't get back here. I have an update. Corny007 1, Samsung Galaxy S3 0. I won :highfive: The first time I installed cyanogen I did it with the installer, and like I said, the blocks weren't read. Not sure how or why yet as I'm just starting out, but I did about 2 or 3 days research, kept hitting dead ends, so I decided just to go back and use the installer again. For some reason, and I still have no idea why, as I mentioned my IMEI data would not restore. This time, it did, no backing up required. I do have them just in case, except I never went through the trouble to get them onto my Ext/SD, and I couldn't figure out how to work around version mismatches after Philz was overwritten. I could have installed the SDK, and took a couple more days probably to get it that way, but for some reason, that I still don't know, maybe it was a bugfix between last time and this, not sure. Bottom line is I am modded, and calling. Thanks for the suggestions, I'll hit the thanks button too. By the way, I never answered your question. I did look where you recommended. It just seemed like I was the one exeption to everything I found. EFS Pro for example couldn't make the .tar file, just little headaches like that. Thanks again.

Stops receiving or making calls

Having weird issues with a Pixel 3 were it will stop making or receiving calls. I can clear the cache and reboot and that often works but I am unsure how many calls I may have missed. Text still works the entire time. I am on the latest Android 11 build with an unlocked bootloader and magisk installed just the restore data with Titanium Backup from previous phone. Not a fan of all the stupidness that got changed/added with Android 12. Willing to try custom roms if that is the right direction. Any thoughts?

toasterboy1 said:
Having weird issues with a Pixel 3 were it will stop making or receiving calls. I can clear the cache and reboot and that often works but I am unsure how many calls I may have missed. Text still works the entire time. I am on the latest Android 11 build with an unlocked bootloader and magisk installed just the restore data with Titanium Backup from previous phone. Not a fan of all the stupidness that got changed/added with Android 12. Willing to try custom roms if that is the right direction. Any thoughts?
Click to expand...
Click to collapse
If you restored data from Titanium Backup, that may be your problem. Titanium Backup has not been updated for two years, and does not work well with newer versions of Android. The restore part caused the most problems. TB has pretty much been abandoned.

dcarvil said:
If you restored data from Titanium Backup, that may be your problem. Titanium Backup has not been updated for two years, and does not work well with newer versions of Android. The restore part caused the most problems. TB has pretty much been abandoned.
Click to expand...
Click to collapse
Thanks for the response. I noticed it had not been restoring apps for a while so I just resorted to restoring mostly game data with it. Wondering if I use Easy Backup & Restore to save my data then wipe and reinstall OS and apps then restore data if that would fix it.

toasterboy1 said:
Thanks for the response. I noticed it had not been restoring apps for a while so I just resorted to restoring mostly game data with it. Wondering if I use Easy Backup & Restore to save my data then wipe and reinstall OS and apps then restore data if that would fix it.
Click to expand...
Click to collapse
It is certainly worth trying. I don't know anything about Easy Backup - I use Swift Backup, and have successfully restored data from one phone to another using it. It might depend on what Android version was on your old phone, though. I recall reading somewhere that restoring data from different Android versions could cause problems.

dcarvil said:
It is certainly worth trying. I don't know anything about Easy Backup - I use Swift Backup, and have successfully restored data from one phone to another using it. It might depend on what Android version was on your old phone, though. I recall reading somewhere that restoring data from different Android versions could cause problems.
Click to expand...
Click to collapse
Finally got around to trying this after replacing the loud speaker on another Pixel 3. Seemed to work well. We will see if this solves the call problems.