Hi guys. Some background...
I have installed the 03 version of Null, and previously to that, I had attempted to root the phone following the sticky guide.
Almost everything has gone great. Why almost ?
I did follow the guide for rooting initially, but when I get to try to access the DATA folder (in order to proceed with other mods) using root explorer, it does not allow me access, saying device has to be rooted.
After a while I gave up and then last night I installed Null v.03. All is fine.
So far I have Nova and a few other apps in the gear using side loading etc. But still do not have access to full root.
It will never ask me to grant full permission once root explorer runs for the first time, no matter how many times I tried to redo it all over again.
Anyway, I am not sure right now whether I need it or not but ..... Any idea ?
P.S. When I run impactor, I see towards the end, the screen of the gear turning into that command line code if I can call it that, only a top line appears but nothing else is written...screen goes off and that's it after. No other notifications on gear or PC.
Just thought to mention that. Don't know if that's what it is supposed to happen or I am missing anything...Don't know if other lines of code or programming are supposed to show while impactor does its thing.
Thanks
Anyone has an idea ?
Thanks.
Related
Ok I have been looking through the tutorials for 2 days now and I finally today rooted my G1 and upgraded to the Cyanongen rom. Everything seems to be working great except for one issue. I attempted to install and run the tether wifi app but when I do I get this message "Cannot start Tether service Error: Permission denied. I am guessing it is not allowing it to run because the phone somehow did not get rooted.
When I rooted and installed Cyanongen I followed these directions
wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
I made sure that I followed each step carefully and didnt miss anything.
I then found this tutorial which had slightly different instructons on how to to root from the one I posted previously.
forum.xda-developers.com/showthread.php?t=563679
Am I going to have to start all over again with the tutorial listed above? Or can I do something to simply add root access to the current rom I have installed? Thanks alot for any help you can give me
No you should still be good. This seems like a pretty simple fix. Go into your app drawer, open up superuser permisions app, and delete everything thats checked with a (-). Then, open the wireless tether app and click on allow, and check the remember box. That should fix it!
Ok Firstly I did search, I couldnt find anything, maybe its cause im tired and frustrated, but i couldnt find any help to my problems. And i apologize in advance for my noobtardness.
Ok here it goes....I finally rooted my phone, after alot of research and almost a year of owning it I decided to make the leap.
Well i followed the instructions here (forum dot xda-developers dot com/showthread.php?t=636795) and everything went nice and smooth...until i did step 3 under "ROOT", after the reboot is when it started acting up. It reboots every couple of minutes is always wanting to force close, and freezes up on the launcher select screen, my n1 is unusable.....
now heres the other thing, i searched around online, tried doing the superboot following the instructions here (theunlockr dot com/2010/01/02/how-to-root-the-nexus-one/) well after i finish step step 9 my phone reboots and works just fine.
now the real problem, when i reboot with my n1 working it stops working, does the same stuff it did before, unless i go back into "fastboot usb" and do step 9 again.
anyone know how to fix this??? And thank you again for any help and for dealing with my noobness
When SU - Superuser was installed on the phone during root, did you click the checkbox to always allow SU permissions while the phone was being rooted? Also during initial bootup after the root, did you do the same for the programs requesting SU access?
I had a similar situation where I "thought" I rooted - however I never checked the box and clicked accept, so I got a lot of force closes and issues from that. Basically, I wasn't watching the N1 screen while the root process was taking place and didn't see the pop-up.
After I tried rooting through superboot again, I saw the pop-up, made sure the box was checked and clicked accept - then it worked fine. Also make sure you do that for any other programs that need routine root access like Titanium Backup or ROM Manager or else you'll have issues.
No I didn't see anything pop up for SU, guess I shoulda been paying a little more attention.
In order to do it over do I need to unroot first??? If so what's the best way to do so???
NM, just found the unroot steps on xda, I will try it when I get home, hope it works this time hope I pay more attention this time.
Ok well heres my problem.
I have a Galaxy Tablet 7" and was using the SuperOneClick Root method which said through the program that it worked but when I go to install programs that require root access nothing works because it says that it requires root access to use, but didn't the program say I was ok? Odd...
What I'm wondering is if there is any way what so ever to reset the Galaxy Tablet to absolute setting's(not factory reset). As through it were right out of the Store.
Also a bit more into, when trying to use the "unroot" option in the program it had a problem detecting my Android version installed, so it asked something along the lines of "is your device 2.0 or higher?" to which I said yes because I'm running 2.2, but furthermore it had a problem with something else and couldn't go any further and failed.
Anyway to wipe and reset this device completely so that everything works the way within the tablets internal memory?
Edit: It won't accept root status in any root only programs at all, even though everything else says it's rooted.
Go to the market and ibstall the Superuser app. That program grants the permission. If it won't install, you're not rooted.
Hello. I found a Polaris office 5 link which will work with rooted devices http://forum.xda-developers.com/showthread.php?t=2611723. Installed as a systems app. I'm rooted, locked BL. After flashing in TWRP it will be there. Trying to open it gives the unfortunately app has stopped message. Looking to clear data in apps it shows no data at all. I go to root explorer find the apk, run in, install new and whamo - works great, no watermark, nothing. However, this is where the problem is, once I restart phone it is back to being uninstalled. It's still in system apps and libs are still there, permission are set. I'm not sure if I missed something. Followed the directions. Searched all over. Is this something to do with being rooted but still having a locked BL? If anyone knows the reason I know where the thank you button is.
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.