Related
Hi all,
I turned on my rooted nook color (which was running fine for a month) and suddenly, instead of the way I had customized the NC, I got the android logo on the screen, and was prompted to set up my google account again. It was similar to what you see as soon as you root the device for the first time. If I go to the 'extras' screen, all my downloaded apps are gone other than the default ones that came with the device. Superuser and NookColorTools are still there though. Anything I got from the market as well as all my custom settings are gone.
I have no idea what caused it. The process I used originally for stock rooting is here (using autorooter) and the device has 1.0.1. It was loaded to the internal memory.
nookdevs.com/NookColor_Rooting
Anyone know how I can return it to the way it was without losing my apps or data?
Sorry for my lack of correct terminology but I'm still new to this. I am afraid that if I try re-rooting I'll lose my settings and data. Thanks
EDIT: Just discovered something. I plugged in the NC to charge it, and it automatically installed an update bumping the firmware up to 1.1.0. I never manually did this update. And now I'm back to the default 8 apps under the extras screen, no NookColorTools or Superuser anymore. Seems it's back to factory defaults. Any way to at least salvage my angry birds data?
If you want to disable auto updates, you will need to follow these steps:
1. Re-root your NC
2. Download ADB or Root Explorer
3. Rename a file that is located in /etc/security. Change otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Thanks. It's odd that it was able to update the firmware at all, because it was always my understanding you needed to have the device back at stock (like new) before installing those, and this happened while it was still in a rooted state.
So you think there's no way to get it to the way it was without rooting again?
Hey guys, I didn't see anyone ask this question explicitly but if it has been stickied somewhere and I just overlooked it I apologize.
Basically I've flashed several different root images using Mofo root and they work for the most part minus one small aspect. After some duration of time (I'm not sure exactly how long but maybe from an hour to a few hours), root apps will basically stop functioning. If I go into supersu, I just get a loading circle that never gets anywhere. I've tried force closing it and disabling/reenabling superuser but that hasn't worked. Some apps continue to function (Gravitybox custom tiles, WiFi Tether, Seeder) but others do not start up properly (TiBackup for example gets stuck at the loading screen where it says asking for root privileges and tasker secure setting profiles return an error). Only a hard reboot will properly restore root but then the same issue occurs where after a while I have to continue to hard reboot once root stops functioning.
Any help would be greatly appreciated! Thanks!
Sorry I don't have a solution but I just wanted to bump this thread because I'm having the same issues as you. Wakelock detector also gets stuck on loading screen and supersu fails to open.
vahx129 said:
Hey guys, I didn't see anyone ask this question explicitly but if it has been stickied somewhere and I just overlooked it I apologize.
Basically I've flashed several different root images using Mofo root and they work for the most part minus one small aspect. After some duration of time (I'm not sure exactly how long but maybe from an hour to a few hours), root apps will basically stop functioning. If I go into supersu, I just get a loading circle that never gets anywhere. I've tried force closing it and disabling/reenabling superuser but that hasn't worked. Some apps continue to function (Gravitybox custom tiles, WiFi Tether, Seeder) but others do not start up properly (TiBackup for example gets stuck at the loading screen where it says asking for root privileges and tasker secure setting profiles return an error). Only a hard reboot will properly restore root but then the same issue occurs where after a while I have to continue to hard reboot once root stops functioning.
Any help would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
I also had the same issue. I am using the image with busy box and Xposed framework installed. After a an hour or so super user said that the binary was not installed, and most of my root apps stopped working. Root checker said my Turbo was not rooted, though gravity box and a few other Xposed modules continued to work. I rebooted the phone, but had the same problem. I turned notifications for the supersu app back on, and after about a minute it said the binary had to be updated, and I had root again. I'm not sure what is going on, but I will come back if I find anything
I'm not having any issues. I would reboot the phone into recovery and wipe the cache there. Hope that helps.
Glad I saw this thread...I'm having the exact same issue!
A hard reboot will solve the problem every time...but its quite annoying...
I'm going to try a factory reset and see if that helps
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Seems to have resolved itself
I just wanted to mention that between clearing the cache and flashing a different rooted image this issue appears to have resolved itself.
I will update after some time to see if this fix maintains or if anything else pops up. Thanks for the suggestions!
ahaynes42 said:
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Click to expand...
Click to collapse
What cache did you clear? I tried to clear the cache from the recovery, but my phone freezes and I have to reboot. Then I loose root a while later.
ahaynes42 said:
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Click to expand...
Click to collapse
I cleared cache in recovery...didn't help...gonna have to try a factory reset
I recently used the "New Root Method For 5.1.1 w/o custom kernel" to root my otherwise stock Note4 SM-N910T.
Everything was fine, but after a few weeks I lost root. I was able to get it back by re-flashing SuperSU 2.65 from recovery.
After further research, I found the blog post by Chainfire on SuperSU 2.74, and understand that 2.74 addresses the Samsung security update.
I've been using "SuperSU 2.65 Stable" because of root access compatibility issues with some programs.
How do I know if the Security Policy update was the cause of losing root? My phone's About Device has "Android Security Patch level" as 2015-11-01. So it doesn't look like something that was updated in the last week.
If it was not the security policy, then what caused the loss of root?
I have automatic updates off, and did not update anything at the time I lost root. Is there any other way that an update or change can be pushed? My /data/security/spota folder is empty. Should I delete the empty folder just to be sure?
I guess because you upgraded the system root cause failure，you need to flash supersu.zip again ，can retrieve root
Supersuer said:
I guess because you upgraded the system root cause failure，you need to flash supersu.zip again ，can retrieve root
Click to expand...
Click to collapse
Here's a summary of the problem:
1) FlashSuperSU from recovery.
2) Enjoy Root
3) 1 to 3 weeks later - something disables SuperSU, and root is lost
4) Go to 1)
I want to understand what is happening in 3) so I can exit this annoying loop.
timg11 said:
Here's a summary of the problem:
1) FlashSuperSU from recovery.
2) Enjoy Root
3) 1 to 3 weeks later - something disables SuperSU, and root is lost
4) Go to 1)
I want to understand what is happening in 3) so I can exit this annoying loop.
Click to expand...
Click to collapse
This has only happened once? Interestingly, I had the same exact issue happen to me on my S5 with MM, I rooted using chainfire and just out of the blue, all root privelages were dismissed. So I flashed SuperSU v2.65. It happened multiple occasions until I was able to switch to an AOSP ROM. After going completely custom it seemed to have stop doing this. Maybe because of a contrast of coding that differ in security.
Sent from my SM-G900P using XDA-Developers mobile app
It has happened twice. I'm working on a Tasker recipe that will check for root regularly and report when it is lost.
Now it has happened three times. Still trying to figure out what causes it. I have not found a tasker function that checks for root.
Unless I can find a solution, I guess I'll have to go back to the traditional root with beastmode kernel.
timg11 said:
Now it has happened three times. Still trying to figure out what causes it. I have not found a tasker function that checks for root.
Unless I can find a solution, I guess I'll have to go back to the traditional root with beastmode kernel.
Click to expand...
Click to collapse
Nobody seems to have any idea what's going on. I'm guessing the loss of root was specific to SuperSU 2.65.
Here what I've tried today:
1) Recovery / Flash with SuperSU 2.65 to get root back.
2) Update SuperSU Pro to 2.76 from Google Store. Download and copy ZIP to phone storage just in case.
3) reboot and verify root still available from Titanium Backup
4) Uninstall ES File Explorer Pro. Install Solid Explorer
5) Test root access of Solid Explorer. It works. Buy Solid Explorer.
6) reboot again just to be sure root remains
7) Backup with TB.
So far, everything is working. Hopefully it will remain rooted.
Almost 3 weeks, and no loss of root. Super SU 2.76 seems to fix the problem.
J500G lost root minutes after connected to internet. I have to root every single day.
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
same thing happened to me just now.
not sure what to do, not sure if i have to reinstall everything again
fmkilo said:
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
Click to expand...
Click to collapse
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
JokersWild0075 said:
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
Click to expand...
Click to collapse
Listen up folks. Do not and i repeat do not update any of samsungs apks. Until we can find out whats going on. It seems that samsung is now pushing updates thru their apks to check and get rid of SU. They are getting sneaky. So for now do not update any samsungs apk, not even thru google. Also do not update SU, this is another way to lose root. We are working on it. Please do not ask if we found anything, if a fix is found we will post our findings.
If you need shealth, iris scanner, samsung pay, android pay, or any other samsung apk, then you need to stay on stock firmware and not use root.
Also if anyone is having issue with files or odin not flashing, make sure you are not on the new PI4 stock ROM, if you are then odin will fail everytime and at this moment there is no way to root or down grade to the older firmware.
Otherwise Try to redownload all files as it seem that afh is/was having alot of issues with uploads and downloads. This not something that we can fix as we dont host or own that site.
Can you guys break down the steps to regain root without reinstalling the OS? Mine also lost root on v2.
It looks like my S-Health was automatically updated to the latest version, which has been reported to be a root of the cause.
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
elite-fusion said:
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
Click to expand...
Click to collapse
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
galaxyuser88 said:
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
Click to expand...
Click to collapse
I am currently logged into the Samsung account and have been for about 2 days now with no ill affects so far, downloaded a couple themes is all...that is with all the Sammy stuff froze and functional root.
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk