Hi everyone
I have rooted my phone like a week ago, using CF root on the latest stock rom, and it worked. However I've been noticing certain situations in which the root is there but doesn't seem to be working. I have problems using most of the root apps, and the zips I've flashed.
For example I flashed a font package and all the new fonts appeared in the list after the reboot, I chose my font but now I don't see any of those fonts in the list, not even the one I chose (It's still the default font for my phone but it doesn't show in the list.) In addition I can't even touch play protect let alone disable it, and the samsung device manager keeps warning me that I should restart the phone to undo the root in order to "protect" my phone.
So I think it's partially rooted, and I don't know what the problem is. Would anyone please help me?
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, new here (runs...) however I've already spent about 6 hours on this and not getting anywhere with it.
i9000 UK on orange network
CYM 5.x installed and *did* have busybox 1.21.0 installed (poss part of the problem?)
Was running and ICS rom before the screen change, part of the change included new buttons (my home button binned it) which came with the part already mounted, they appear complete. All the micro connectors are attached and a quick check with a multi meter shows everything physically works with each other, so it must be a kernel issue right?
What I've tried...
reflashing OE rom with ODIN.
flashing a newer ICS rom which has previously been installed and worked fine, no change.
flashed a known good gingerbread rom, now the back button occasionally lights up but doesn't do anything, and a CYM button identify effort doesn't pick up either input either?
Tried installed busybox installer however was a bit tired when doing it and accidentally set the superuser permissions to 'remember forever - deny', and now I've flashed a new rom I can't get to the superuser list no matter where I go, despite formatting it and starting again it somehow remembers the deny for busybox? So as far as I can check the unstable 1.21.0 version of busybox is still installed, but I can't see it, remove it, or replace it? Frustrating much?!
OR, is there just something wrong with the screen/part I have bought, a hardware fault that I can't detect?
Cheers!
Anyone able to shed any light on this?
Cheers
Usually roms don't have any problems with the touchscreen and the capacitive buttons unless they're in REALLY early/alpha stages. I don't see much reason why a kernel would affect it either, considering that there's no usable kernel in here reportted to have touchscreen problems I believe...
So your problem probably lies with the hardware fault. I'm nowhere near capable enough with electrical equipment to know when something is working/should be working or not, but if your rom has everything working, your kernel is fine then the only thing it seems to be is some hardware fault.
With regards to the busybox issue, try a few things:
Under the Apps screen (Manage Apps on Gingerbread, or just Apps in ICS and above), try scroll down until you see Superuser. Clear data/cachee for Superuser and see if that fixes the problem.
Alternatively, busybox is just one of a few superuser apps. Is busybox needed for a specific process? Because if its not specifically needed then I've found that SuperSU works really well also.
Hope this helped!
Sent from my GT-P7510 using Tapatalk HD
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 everyone, I have have a big trouble with my note 8.
I did a update today because Samsung was proposing that to me
After the update, I have a error message about system ui and I can do nothing with my phone.
Not rooted, nothing is modified in my phone. I have only installed substratum with swift black theme but not rooted.
I think it's because of this.
Someone can help me please, the secured mode change Nothing.
Help please
Substratum is probably your problem. I ended up doing a hard reset but I think I read that if you can get into safe boot, you can delete Substratum from there.
If you go the hard reset method, don't recover your apps with backup. You'll just drag the problem back.
Epic my Note was already loosing the ability to open apps and once I updated I could not get the phone to open just do a hard reset and everything will go back to normal mine is running great
Zarancar said:
Hi everyone, I have have a big trouble with my note 8.
I did a update today because Samsung was proposing that to me
After the update, I have a error message about system ui and I can do nothing with my phone.
Not rooted, nothing is modified in my phone. I have only installed substratum with swift black theme but not rooted.
I think it's because of this.
Someone can help me please, the secured mode change Nothing.
Help please
Click to expand...
Click to collapse
Don't update with Substratum theme installed, as stated by another member just boot into safe mode and uninstall all the substratum layers you have installed and reboot.
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