[Q] Rooting stock ICS - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

I tried the honeycomb rooting.zip file through CWM 4.0.0.4 and while Superuser is installed, but root apps cant seem to get su permission. how do I make it work?

Related

[Q] Rooted Thunderbolt SU problem

Hey Guys,
Got my Thunderbolt rooted and s-off. Running decent... But I have a few problems with bugs/wondering if there were any known fixes...
1: CWM is having problems... as in picky about when it wants to reboot... etc... should I just wait for a new flash?
2: I liked usinig Andguard on my droid... but it seems after rooting/s-off my thunderbolt and installing Superuser/CWM, I cannot use Andguard...It states it does not have SU permission and to check root or Busybox... help?
Best!
Thanks to the DEVs working hard on this!
Are other apps that require root working for you? Like maybe Titanium Backup, or Root Explorer? Heck, there's a free app called Root Checker you can download to test.
It sounds to me like you have issues with your su, superuser installation. Did you download and install SuperUser.apk from the Market? Does it give you a pop-up asking permission when you run your app? If you open SuperUser app, is the app listed as having permission allowed?
If all of that is yes, then try installing a new version of busybox. There's a busybox installer app on the Market, or you can use Titanium Backups "Problems?" button to download a copy.
Let me know if that helps out.

[Q] problem with root / superuser

i ave succesfully rooted my gt 10.1. Installed titanium Backup , worked.
After a factoryreset i can't install tb anymore. Installed the latest superuser but i am not able to update SU binary. Can't istall busybox either.
Suggestions?
(can i root again without harming something)
Problem solved: Rooted tab again, superuser now works well, TB is installed and can be used again.
I won't update su again......

[Q] No Root with Neak Kernel

Hi,
I have installed XXKL1 firmware (stock from samfirmwares) and afterwards Neak Kernel 1.3.3.
Everything seems to be fine, the kernel shows up under system info, I have a NEAK CWM Recovery, I can do adb shell for a root shell, adb remount reports success.
But when actually using the phone itself, all root fails. The superuser app from the NEAK flash does not pop when using a root app, all apps instantly tell "no root" (Busybox installer, Titanium backup, ...). Even Superuser itself does not seem to have superuser access, it cant update the su binary.
What am I missing?
Check the Neak thread first .
And or reflash the kernel .
jje
Why dont you root with a CF-Root kernel to get root and superuser and then flash the Neak kernel to see if the root access stays.
I was a bit worried because there was no exact cf-root kernel for XXKL1. But I used the XWKL1 one and flashed back to the other kernel and yes it worked.
Thanks!
(Although I don't quite understand why...)
CF-Root kernels are basically stock root kernels by Chainfire so being stock rooted they are,I imagine,more likely to get and hold root access.They are the only kernels is use as Im not into overclocking or anything like that.Anyway once root was acheived flashing the other over top was no problem.XXKL1 is the same as XWKL1 as long as the Firmware is the same.The important part is the last 3 digits.
Hossie2k said:
Hi,
I have installed XXKL1 firmware (stock from samfirmwares) and afterwards Neak Kernel 1.3.3.
Everything seems to be fine, the kernel shows up under system info, I have a NEAK CWM Recovery, I can do adb shell for a root shell, adb remount reports success.
But when actually using the phone itself, all root fails. The superuser app from the NEAK flash does not pop when using a root app, all apps instantly tell "no root" (Busybox installer, Titanium backup, ...). Even Superuser itself does not seem to have superuser access, it cant update the su binary.
What am I missing?
Click to expand...
Click to collapse
This happens only when the space left into /system partition is very low, so the kernel cannot root the phone
Check first if you have the Superuser app, if not, try to install it from market and see if you can gain root access...
Probably my kernel has installed only the su binary, because there was no space left to install also the superuser apk
simone201 said:
This happens only when the space left into /system partition is very low, so the kernel cannot root the phone
Check first if you have the Superuser app, if not, try to install it from market and see if you can gain root access...
Probably my kernel has installed only the su binary, because there was no space left to install also the superuser apk
Click to expand...
Click to collapse
The same happens to me. Even installing the Superuser from Play Store it says I don't have root access. I'm on a n7100 with 4.1.2 stock (rom) and latest neak kernel.
Thanks.
Siyah anyone?
Sent from the little guy

ROOT on Official ICS ???

I don't think anybody has mentioned this yet, so here we go.
Installed official ICS (italian version), running smooth.
decided to root, tried the exact method done for HC.
Seems like it was rooted, since SUperuser is now available.
Tried to update superuser binary >> no root access
Es file explorer>> no root access.
Basically does that method work on ICS, and if not, how to reverse what i already installed ?

Unable to access root

I rooted my Micromax A104 KitKat 4.4 with Kingroot and after using for some months I factory reset the phone without removing the root, (without unrooting) now I tried rooting again with the same method as before but I'm unable to gain access to root.When I tried to install the app. It says there is a same application with a conflicting certificate. (Problem is I don't find the kingroot or superuser apps in the apps drawer,and there is nothing to be found even in the list of install apps.) Now, even when I access /system/apps/ folder there is no install apps found in folder.
Note: When I install superuser apps it says su binary needs to be updated and when I tried to update, it fails.
That's because the SU app and binary are not in the normal app places. Basically you will have to either track down where it installs and remove it (will need Root for that) or flash the stock firmware.
Thanks...for the info.

Categories

Resources