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!
Hey guys,
I'm having an issue with rooting my HTC - I followed all of the steps on multiple guides with no luck. Here's the breakdown:
I have successfully unlocked the bootloader
I have tried flashing both the TWRP and the CWM ROMs
I have used the http://androidsu.com/superuser/ site on my phone to get the Superuser-3.2-RC3-arm-signed.zip file
I tried installing said file using both TWRP and CWM, both did not work
When booting into the OS and running Root Checker, it says "Sorry! This device does not have proper root access."
In the youtube video linked here: http://forum.xda-developers.com/showthread.php?t=2173863 many comments are from users describing the same issue I'm having, though searches on google and on the XDA forums have found nothing that has worked. At this point, I am not sure where to proceed.
Right now I am running Android Version 4.4.2 with HTC Sense version 5.5, and the HTC SDK API level is 5.68. I suspect that my android version is the problem, but before I go delving into how to downgrade, I wanted to check to see if anyone has any advice. Hopefully someone has come across this before, but if not, at least there'll be a searchable record of the problem for other users.
Thanks in advance for any help anyone is able to provide.
Kythios said:
Hey guys,
I'm having an issue with rooting my HTC - I followed all of the steps on multiple guides with no luck. Here's the breakdown:
I have successfully unlocked the bootloader
I have tried flashing both the TWRP and the CWM ROMs
I have used the http://androidsu.com/superuser/ site on my phone to get the Superuser-3.2-RC3-arm-signed.zip file
I tried installing said file using both TWRP and CWM, both did not work
When booting into the OS and running Root Checker, it says "Sorry! This device does not have proper root access."
In the youtube video linked here: http://forum.xda-developers.com/showthread.php?t=2173863 many comments are from users describing the same issue I'm having, though searches on google and on the XDA forums have found nothing that has worked. At this point, I am not sure where to proceed.
Right now I am running Android Version 4.4.2 with HTC Sense version 5.5, and the HTC SDK API level is 5.68. I suspect that my android version is the problem, but before I go delving into how to downgrade, I wanted to check to see if anyone has any advice. Hopefully someone has come across this before, but if not, at least there'll be a searchable record of the problem for other users.
Thanks in advance for any help anyone is able to provide.
Click to expand...
Click to collapse
After the phone has TWRP/CWM successfully installed, there will be a SuperSU app installed on the phone. Just open that app and follow the procedures. That should successfully root your device. The zip which you've mentioned didn't work on my One either
raghav kapur said:
After the phone has TWRP/CWM successfully installed, there will be a SuperSU app installed on the phone. Just open that app and follow the procedures. That should successfully root your device. The zip which you've mentioned didn't work on my One either
Click to expand...
Click to collapse
Thanks for your response,
I just checked my phone, and I don't seem to have SuperSU installed, just the Superuser app that is from the .zip. Should I uninstall the .zip, and will that make the SuperSU app appear?
Edit: So, I just tried clearing the fastboot cache and reflashing CWM, after disabling Superuser to see if it would reinstall its own app, with no luck.
To clarify, there is no procedure that pops up in the Superuser app, so that's why I tried to get the ROM's app to load. I also cannot find a way to just uninstall the .zip, and I'm not about to go deleting files without guidance. Out of curiosity, when the zip didn't work for your One, what steps did you take?
Kythios said:
Thanks for your response,
I just checked my phone, and I don't seem to have SuperSU installed, just the Superuser app that is from the .zip. Should I uninstall the .zip, and will that make the SuperSU app appear?
Edit: So, I just tried clearing the fastboot cache and reflashing CWM, after disabling Superuser to see if it would reinstall its own app, with no luck.
To clarify, there is no procedure that pops up in the Superuser app, so that's why I tried to get the ROM's app to load. I also cannot find a way to just uninstall the .zip, and I'm not about to go deleting files without guidance. Out of curiosity, when the zip didn't work for your One, what steps did you take?
Click to expand...
Click to collapse
http://www.google.com/url?sa=t&rct=...-oGwAQ&usg=AFQjCNFiD1-Ui0e9doyEWS3S0qXvg4lDuA
Try flashing this zip. I have the working zip on my phone. I think this is the one which I downloaded. If its not, let me know. Ill hunt for the link
raghav kapur said:
http://www.google.com/url?sa=t&rct=...-oGwAQ&usg=AFQjCNFiD1-Ui0e9doyEWS3S0qXvg4lDuA
Try flashing this zip. I have the working zip on my phone. I think this is the one which I downloaded. If its not, let me know. Ill hunt for the link
Click to expand...
Click to collapse
Or flash this one
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
raghav kapur said:
http://www.google.com/url?sa=t&rct=...-oGwAQ&usg=AFQjCNFiD1-Ui0e9doyEWS3S0qXvg4lDuA
Try flashing this zip. I have the working zip on my phone. I think this is the one which I downloaded. If its not, let me know. Ill hunt for the link
Click to expand...
Click to collapse
That one didn't work, I suspect it's because I have another copy of Superuser on this phone, but I'm no expert. I'm going to try the SuperSU that mb_guy suggested, maybe a different SU program will help. thanks for sticking with this. XD
this one worked, thanks so much!
it's weird, no matter how many times and ways I searched for SuperSU on google, I wouldn't ever get a link to the actual file. Maybe I just didn't put in the right keywords. Anyways, thanks for your assistance, and thanks to raghav kapur as well.
To anyone else having this problem: mb_guy's file worked for me, however it may not be the same for everybody. If you followed the XDA forum guide I linked in the OP, then chances are this fix will work, but if you followed any other guide, it may be worth it to give raghav kapur's .zip a try to see if that fixes it for you.
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
neil.io said:
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
Click to expand...
Click to collapse
You flashed the latest version of TWRP custom recovery?
samwathegreat said:
You flashed the latest version of TWRP custom recovery?
Click to expand...
Click to collapse
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
neil.io said:
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
Click to expand...
Click to collapse
That might be the issue. It might not be compatible with 4.4.3
Try this one: http://techerrata.com/browse/twrp2/ghost
Also, which version of SuperSU are you using? There was a new one released recently. Find it here: http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip (Flash it from within TWRP - install ZIP)
Please update, and then advise whether or not your issue is resolved.
EDIT: Also, make sure you are using the "stericson" busybox variant. Others have been reported to cause issues.
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
neil.io said:
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
Click to expand...
Click to collapse
Open SuperSU, and check to see if busybox is listed under apps. There should be a green "#" symbol next to it. It SHOULD have prompted you to grant access to it, so perhaps at some point you either denied the su request, or didn't see it. If you see a RED "#" symbol, tap it, and change to "Grant".
Please advise...
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
neil.io said:
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
Click to expand...
Click to collapse
I would suggest a full return to stock (follow the return to stock thread in the general sub-forum). This is not normal....
You appear to be using the XT1053, correct? Take caution to NOT downgrade or you could end up with a brick.
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
samwathegreat said:
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
Click to expand...
Click to collapse
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
neil.io said:
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
Click to expand...
Click to collapse
How did you SBF to stock? Did you use RSD Lite? Did you retain userdata, or wipe everything (suggested)?
The stericson variant installs fine for me...granted I'm on 4.4.2 (the latest for my variant).
I did NOT use smart install...just used regular install to /system/xbin (You might consider trying smart install if you haven't yet...)
Honestly, I'm out of ideas. Although the "stericson" variant is recommended, perhaps you should try another version from the market if you need busybox.
I've done extensive searches and haven't found anyone else having a similar issue - even with Moto X on 4.4.3
I gave up and used the recovery method. Really odd - it does seem like the other installer apps couldn't mount /system as writeable, but it's weird that other apps that installed to that area worked.
Anyway, thanks again!
This is driving me nuts... I was on 5.1.1 and I am trying to get it rooted.
I'm following a guide which goes like this..
1. downgrade to kitkat 4.4 using flashtool
2. root 4.4
3. Install custom recovery
4. Flash 5.1.1 pre-rooted zip
I have had problem after problem and I think something may have screwed up along the way.
I finally managed to get kitkat installed using flashtool and a generic C6903 .108 ftf.
Problem 1... I used 'Easy Root tool' from xda to root kitkat... but it seemed to hang at the cleaning up' stage - is this a problem?
Problem 2... every time I restart my phone - kitkat asks what language etc. Whats that all about?
PROBLEM 3. The guide Im following says to install busybox after rooting kitkat.
I've tried 2 different busybox installers and both of them fail when trying to install bb.
QUESTION: Are these 3 problems linked and will it prevent me from continuing with the guide I am trying to follow??? i.e. do I need busybox to install XZ Dual Recovery and therefore a pre-rooted zip?
Root Checker basic says kitkat is rooted, as does the first busybox installer.
I'm taking a short break from this nightmare, so in the meentime if any of you chaps could advise me on whether or not its ok to continue or if I have fecked up the whole process, that would be great.
Thanks in advance
problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?
I would just start over and try a different root program. busybox is failing to install because the root didn't work.
Gamer4Life said:
problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?
Click to expand...
Click to collapse
Problem1... thank you, I'll try again
Problem2... Thanks. I thought It could be the lack of a SIM card and then I thought no! that can't be it lol... as usual - I was wrong ha
others... yeah mate, tried 2 different installers from play store - no joy with either.
Thanks for your help
xasbo said:
I would just start over and try a different root program. busybox is failing to install because the root didn't work.
Click to expand...
Click to collapse
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate
i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb
thesweeney80 said:
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate
Click to expand...
Click to collapse
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.
Gamer4Life said:
i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb
Click to expand...
Click to collapse
thanks for the tip mate but no joy see my reply to xasbo, cheers
xasbo said:
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.
Click to expand...
Click to collapse
Thanks mate. I was hoping Gamer4life might be right as there was no Supersu installed.
I installed supersu from play store no problem... but when I try to update binaries it says' update failed. Please reboot and try again.'. tried reboot but same story.
I guess I'll try 'easy root tool' again and then will give kingroot a bash if needbe.
One last pre-emptive question...
If I root kitkat using kingroot... should I replace kinguser with supersu before proceeding with XZDR and a pre-rooted zip or will kinguser be sufficient to continue.
Many thanks to you and everyone else who has tried to help me with this clusterf*ck,.. I appreciate it
can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Gamer4Life said:
can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
must have been a glitch in the matrix mate becuase its now working (Possibly thanks to your suggestion of installing Supersu?).
I reconnected to PC in order to give 'easy root tool' another crack at it.
As soon as I start install.bat It says checking if device is rooted AND I get a superuser request on my phone for adb.shell - Happy days!
I granted root access to adb shell and the root tool says Job Done. Root success etc.
So I disconnect and try to update su binaries and it worked first go!!!
*Touch wood* I think I'm now past the tricky part and it should be plain sailing from here on in. lol
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:
Gamer4Life said:
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
Correct, TowelRoot doesn't work for this version.
---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------
thesweeney80 said:
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:
Click to expand...
Click to collapse
:good: godspeed
@thesweeney80 you are welcome have fun
xasbo said:
:good: godspeed
Click to expand...
Click to collapse
Gamer4Life said:
@thesweeney80 you are welcome have fun
Click to expand...
Click to collapse
you fellas are the muts nuts.
All done, everything went smoothly once I got kitkat rooted properly.
MANY thanks for all your help.
Honestly I wouldnt even bother owning a smartphone if it wasnt for the peeps on XDA... F*cking awesome. THANKS :good: :highfive:
:good: awesome! don't forget to pay it forward sometime.
Root Issue Reporting - "Could not access the package manager.Is the system running?"
Hi All, not sure whether I should request help here.. This is to report the root issue, I followed Z5 Rooting method here and use that rootkernel tool to modify and generate my Boot.img for X Performance F8132, then use Flashtool under fastboot mode to inject this modified new kernal into Original stock ROM - F8132_35.0.A.1.238_HK.tft, after rebooting, I got Rooted phone with DRM well maintained.
Everything is perfect working of Root, Greenify/Busybox... Until I found issue with My Android Tools Pro, though I've authorized it in SuperSU, My Android Tools Pro still advised error msg like Can't obtain Root access. I activated SuperSU logging and found it advised "Could not access the package manager.Is the system running?" for this App. I contacted with My Android Tools Pro developer and this issue seems should never occur in real phone as it's a common error under Development environment. So now it seems like SuperSU issue with Incomplete Root after all these investigations..
I'm looking for help to resolve this issue and if it's posted in wrong place, plz don't be hesitated to let me know and I would move the post to appropriate forum, thanks!!
kevinkoo said:
Hi All, not sure whether I should request help here.. This is to report the root issue, I followed Z5 Rooting method here and use that rootkernel tool to modify and generate my Boot.img for X Performance F8132, then use Flashtool under fastboot mode to inject this modified new kernal into Original stock ROM - F8132_35.0.A.1.238_HK.tft, after rebooting, I got Rooted phone with DRM well maintained.
Everything is perfect working of Root, Greenify/Busybox... Until I found issue with My Android Tools Pro, though I've authorized it in SuperSU, My Android Tools Pro still advised error msg like Can't obtain Root access. I activated SuperSU logging and found it advised "Could not access the package manager.Is the system running?" for this App. I contacted with My Android Tools Pro developer and this issue seems should never occur in real phone as it's a common error under Development environment. So now it seems like SuperSU issue with Incomplete Root after all these investigations..
I'm looking for help to resolve this issue and if it's posted in wrong place, plz don't be hesitated to let me know and I would move the post to appropriate forum, thanks!!
Click to expand...
Click to collapse
Maybe this issue.
http://www.mobile01.com/topicdetail.php?f=569&t=4861581#60965299
The New SuperSU folder have different locale.
If the app isn't update, they not work.
bkk99213 said:
Maybe this issue.
http://www.mobile01.com/topicdetail.php?f=569&t=4861581#60965299
The New SuperSU folder have different locale.
If the app isn't update, they not work.
Click to expand...
Click to collapse
Thanks man! I just resolved this issue, actually it's quite easy.. I just unchecked the option "Mount namespace seperation" in SuperSU, then everything works fine now!