Hello all...I need a bit of help. I rooted and then un-rooter my previous phone with KingRoot. After removing it with the KR uninstall program, I would use multiple root checking apps, and they would all report that the phone was NOT rooted, but when I tried to update system files with WiFi update, it would error with a "Root has been detected, can not update device" message. I recently purchased a new phone with 6.0 and transferred my files and settings to the new phone and now am having the same problem with my new phone.
What file/files does the system check in order to make that determination??? Is it something I can remove or edit with out a complete wiping and re-installation of Android??? King Root does not offer a rooting for my current phone where I could install and then try a removal on this phone.
I was really hoping that with a new phone that I would be leaving that problem behind!
Thanks ahead
never mind....
Well, for what ever reason...I did one more hard reset and the problem solved itself. Now able to receive regular updates from BLU/Android. Go figure..
Related
Hello again in need of assistance asap.
I have a somehow minor problem with my phone. I decided to factory reset my rooted huawei y220 because
-All of a sudden I can't access websites like:
>facebook.com
>yahoo.com
>gmail.com
I also can't access their mobile sites. I can't access the said websites from any browser from my phone at the time(Stock browser & Dolphin Browser). There is no problem with my internet connection since I am able to access these websites from my laptop and other handheld devices.
FORTUNATELY, I stumbled upon a browser named UC MINI. I can somehow access these websites but only if I am using its feature call "Speed Mode". If I switch that off I can't access the said websites.
I also factory reset my phone because a person from XDA told me that unfortunately, there is no compatible Custom ROM with my phone.
I don't know why didn't I just Unroot my phone with Kingo Root(The program I used to root my phone). And I also wanted to start from a clean slate and since I deleted the bloatware using titanium backup.
After rebooting from the factory reset I noticed SuperSU was left behind and it said that "There is no SU binary installed, and SuperSU cannot install it This is a problem!" Why is that? I did my research that if you factory reset your phone with a custom rom it will cause problems(?) Well fortunately I wasn't using a Custom Rom and I checked my phone with root check to check it whether it is rooted, it isn't rooted anymore after the factory reset.
My doubts are:
>What is causing my phone from accessing these websites(And probably more)
>Is it a virus?
>Did I touch something with the system that made it faulty?
>I was kind of playing around with ROM Installer with the bootloader thing because I thought it would change the boot animation of my phone to something else.
>Is it okay if I root my phone again and see whether the SuperSU issue is fixed and the browsing thing fixed.
My Huawei Y220-U10 is working a smooth as new right now. Actually a bit faster than when I got it fresh because I uninstalled some bloatware when it was still rooted. My real concern is the connectivity issue and the SuperSU issue.
Hope to hear from you guys asap,
Jom
Hi,
I found this guide about factory reset for your phone, hope it is helpful.
As for the apps you are having trouble with, suggest deleting, doing a fresh install, and rebooting.
Not likely a virus.
Yes, if you root again you should regain superuser access... please note that superuser works on some devices and super su works on others.
As a reminder, we are happy to help when we can, as best we can- we are not here for troubleshooting issues.
Good luck !!
Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)
Anyone here with a modded Galaxy S3 phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
pchemerys said:
Anyone here with a modded Galaxy S3 phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
Click to expand...
Click to collapse
i have no explanation for what happened, actually never heard it happen before.
why not try to re-root and see what happens. if that doesn't work, i would think your only option would be to flash it clean and start over.
Reroot. Or unroot then reroot.
yeah i was thinking that might have to be done.. was hoping not and that this was some sort of known or fixable issue...but may have no choice..will wait another couple days to see if i find anything and do it if no other option..
pchemerys said:
yeah i was thinking that might have to be done.. was hoping not and that this was some sort of known or fixable issue...but may have no choice..will wait another couple days to see if i find anything and do it if no other option..
Click to expand...
Click to collapse
well, i haven't seen any root methods that require wiping the phone, so why wait to try re-rooting?
I would try a new busybox with kinguser and reroot.
I have messed my phone up and I don't know what to do, I am very aggravated and I need expert help trying to fix my LG G2.
My story is i rooted my phone with towel-root and downloaded a few root apps(Root Checker, Freedom, etc.)
I had an OTA update to go to i think D80120g, but my phone was already kitkat 4.4.2. I downloaded this update and it messed my phone up, I could not get on the play store and on Clash of Clans I had 2 accounts connected and I could not connect or switch between the two of them(usually to fix that I would go open up freedom and it would work) but i figured the update unrooted my phone. Root checker said I did not have root.
I have factory reset multiple times, and hard reset( which apparently didnt work) twice. I really need help and I regret rooting my phone because I know almost second to none about rooting phones and tweaking them.
So I appreciate anyone that helps me
As many of you may know, Nvidia has recalled their Shield Tablets. I'll be getting a replacement soon. I'll be rooting it as soon as possible when I get it, but first I have a few questions.
First of all, I rooted my tablet using a guide at IBTimes (that used info from XDA forums) installing CWM recovery.
After rooting I installed Link2SD, pretty much the reason I rooted, to save up some space on my internal memory. Everything was going fine, until I received the recall notice. I moved all my app files back to the internal memory, deleted Link2SD, ran a full unroot on SuperSU, (after a while of hanging on the "Please Wait" screen the app just crashed, it wouldn't load up and Root Checker said I had no root access after rebooting.
I don't know whether this was supposed to happen or whether it should have gone more smoothly, please give me an answer to this and tell me if it affected my system in any way) and fastboot flashed the stock recovery.img.
However when I tried to install the update, I got a red triangle error. After checking the log I got an error saying "Package expects build fingerprint of ... or ..., this device has ...."
I can't remember what the fingerprints were, but the first one was something that began with "nvidia/", had a bunch of numbers in the middle followed by an underscore, then it ended with "/release-keys".
However the device's current build fingerprint was exactly the same as the first, except that it cut off halfway through, right after the numbers and the underscore.
I tried resetting my cache, I tried a wipe of the user data. The only way to fix this for me was to re-install a bunch of stock images - recovery.img, boot.img, system.img, etc.
I don't want to wipe my data next time. So I ask for this in my answer:
- An explanation of what the error means
- How this error is caused
- A way to fix this error without wiping my device
- How to prevent this error
- If what happened to SuperSU in my case is normal and if it affected my device in some way
- And, if possible, a way to install the update successfully without getting this error and without having to unroot or remove CWM, and details on how to do this method and any risks.
Thanks in advance. An answer soon would be appreciated.
Hi there,
You'd be best served asking for help from the experts who own your device here:
Shield Tablet Q&A, Help & Troubleshooting
Good luck
I just purchased a new S6 today from Best Buy. I was lucky to get a OE2 version, saw it on the box labe before I bought it. I would like to root and install a ROM but I want to wait until my 14 day return period is over in case I'm not satisfied and decide to do something else. The prompt to update pops up constantly. It's very annoying and I'm concerned I may accidently tap the update button. I'm coming from a S4. On the S4 I was able to use Root Explorer to rename a couple of system files to stop the request for updates. Since I'm putting off rooting until after 14 days that method is not possible. I cannot uncheck to automatically upgrade because when I go to system update I only get the "update ready to install" message. I tried booting to recovery and wiping system cache but that had no effect. Any suggestions? Thanks
I used titanium backup to freeze mine but I know that requires root access... Before I had that I would constantly keep my phone in airplane mode and set mobile data limit low so it wouldn't dl it... Just an FYI I'm on a rooted gs6.. Still no exposed for our phones, it's for 5.1.1 and there's the risk for stage fright as its not patched on the root able version.
templton said:
I used titanium backup to freeze mine but I know that requires root access... Before I had that I would constantly keep my phone in airplane mode and set mobile data limit low so it wouldn't dl it... Just an FYI I'm on a rooted gs6.. Still no exposed for our phones, it's for 5.1.1 and there's the risk for stage fright as its not patched on the root able version.
Click to expand...
Click to collapse
Thank you very much for the reply. Someone on another forum suggested I do a factory reset, don't enter any user information during initial setup and disable auto check for updates. I tried that but apparently you can no longer stop checking for firmware updates. So I said screw it and rooted last night. I can always Odin back to stock if I decide not to keep the S6.
Eddie Hicks said:
Thank you very much for the reply. Someone on another forum suggested I do a factory reset, don't enter any user information during initial setup and disable auto check for updates. I tried that but apparently you can no longer stop checking for firmware updates. So I said screw it and rooted last night. I can always Odin back to stock if I decide not to keep the S6.
Click to expand...
Click to collapse
The smartest thing to do would be to root, freeze the SDM, then, If you no longer want the device, unroot using Odin