Database Info

[Q]Galaxy Tab 10.1 problem

I purchased my tab in China. Samsung China has deleted all Google apps from the pre-installed rom. As a result, the Chinese GT 10.1 community has compiled an Google app pack (GoogleServeice_P7510.zip) to bring back those apps.
I flashed it immediately after I rooted the tab. The Google apps were installed successfully. I entered my google account after the boot and every google app was running without a glitch. But not long after that I found I could no longer enter browser settings anymore. It would always give me a FC when I tried to do so. I then downloaded the dolphin browser. So this problem was bypassed.
Then I found there was something wrong with the superuser, I could not adb remount/push, and it couldn't be revoked by the apps that required root access.
This problem was partially resolved later by flashing the OC kernel for GT 10.1, which secured adb privileges. But the superuser was still problematic. Then I found out that after I flashed any zip other than root.zip in recovery, be it the kernel.zip, the su_busybox_tools.zip or google_servicepack.zip, the superuser icon in the app drawer would always become 4 times smaller (2 time in both height and length) than the superuser app "installed" by root.zip, as well all other apps.
There seemed to be something wrong with this version of superuser app (small icon). Whenever I opened an app that required root access, the superuser prompt window would not pop out. But if I flashed the root.zip again, the big-icon superuser app would be back. And other apps can revoke it most of time. However, it was not perfectly stable. Somethimes, it still failed to be revoked. I have flashed the root.zip among the other 3 zips for many times to get this conclusion.
I then applied the V6 SuperCharger script and flashed the su_busybox tools for GT 10.1 right before that, because SuperCharger script required busybox. However, due to the superuser problem, the SuperCharger script was not fully working. After reboot, part of the settings was changed back to default, because 99supercharger.sh couldn't be run on boot with root and there's not init.d folder in GT Tab 10.1. Then I flashed the OC kernel hoping it will fix all the problems. After that, I surprisingly found out that I was able adb remount and push. But the icon of the superuser app was again back to the small one. So the apps requiring root could not revoke it for permission.
As a result, I flashed the root.zip again. At this moment, superuser works normally, even after some reboots. SetCPU and script manager are able to automatically acquired root access on boot. But when I rechecked the supercharger script, current pages(minfree) were still showing blank.
Other problems include backspace and enter keys not working in terminal emulator/console. And the problem I just found - the notification ringtone list in the system settings and other app (e.g. Gmail) settings was blank. I could not change ringtone, although the system can play it without problem. And the ogg files are still there in /system/media/notifications.
Since all Android devices works more or less the same. I hope some of you phone experts can shed some light on these problem. The user base of Android tabs has made it less supported than Android phones. It'll be highly appreciated if all these annoying problems get fixed.
Thank you!

Needing help with root and Titanium.

Hi Guys.
I'm a noob trying to root my Chacha. This phone is a parrallel import, language options are Singapore English and Thai, the plug is a euro 2 round pin and it was unlocked for carrier.
I bought an XTC clip and S-off is done. So far so good.
Then I followed this guide here: http://forum.xda-developers.com/showthread.php?t=1184118
But when installing Titanium backup (with the intent of removing facebook etc) I get the message that Titanium cannot get root access. Usually preceded by a superuser error and forceclose or report options.
Typing "su" into a terminal window gives me "permission denied".
So I went back to the very good guide here: http://forum.xda-developers.com/showthread.php?t=1184118
and I noticed I get the following messages when installing PH06img.zip. "No image" followed by "no image or wrong image".
Any ideas?

Hmm, you have stopped reading the thread after the first two posts.
There is a problem with superuser (the application itself is buggy). Go to Market and update superuser to latest version. That should fix everything.
Otherwise you'll have to use the complicated method (re-flash stock, reinstall CWM, superuser, start superuser, start Titanium).

Superuser has updated itself several times (it comes up with a random, "that was cool, do it again" loop) and ends up on version 3.0 (binary).
But that doesn't seem to help. I'm still getting (process com.noshufou.android.su) has stopped.
Titanium still tells me it can't acquire root privilieges as well.
I've tried clearing the app data to fix the force-close but with no success.
Is there a walk through for the complicated method? TIA.

Is SU 3.02 or 3.04 worth a try?

Yeah, that's the version. Not only the binaries, the application itself needs updating. Get the latest one from market.

Haha, I have it. After 12 hours.
Superuser 2.6.3 worked. I found the files here: goo-inside.me/superuser/
The latest version is no use at all. I had been trying with 3.0.5

Weird. 3.0.5 Should work fine.

Superuser is a GREAT app but latest update is horrible. Blocks all rooted access apps and causes major forces closes and freezes. I emailed the developers with NO reply. Had to move Su to my SD card and uninstall it entirely. Guess its a waiting game now.
Sent from my EVO 4G running R3CHARED ROM using XDA Premium App

Am I the only one with fully functional superuser? I've set it to auto-allow access from preferences.

Alex, which phone do you have? Do you have access to Market, Titanium, spare parts etc......?
Sent from my EVO 4G running R3CHARGED ROM using XDA Premium App

It is very strange indeed.
I tried the 3.0.5 version install about 5 times over 8 hours. Interspersed with trying everything else I could google up. No luck, same force-close result each time.
Then I started trying 3.0.4 and 3.0.2 with no luck, eventually I found in that very long SU thread a reference to 2.6.3. So I found it on goo.inside.me and it worked.

[Q] Root not working as expected.

I got my HTC One X about a week ago now for AT&T. Almost immediately, I tried rooting but ran into an odd issue.
Before rooting I had installed Apex launcher. There is an option in the settings to enable Root Helper, which previously would give an error message of something like, "This device does not have root access"
I went through the rooting procedure as detailed here on my mac. The script didn't work at first until I realized I had to switch it to Unix from DOS (Didn't look at the script before running) after I fixed it, it ran and rebooted twice and everything looked normal. Now I tried using the apex root abilities and it just froze and crashed.
So I booted up windows and tried using that to root, but the exact same thing happened. It seems to recognize my root, but not actually give any permissions.
I've tried using other root apps such as uninstallers,titanium backup, etc and all of them just freeze when trying to get elevated permissions.
Is there something wrong with my phone or the way I did the root?

Have you tried clicking on the su app? I had to upgrade mine.
Sent from my HTC One XL using XDA

Yea load up the Su app and ugrade binaries. That should fix the issue. Ive had issues like this on other phones.

You could also try running paulobrien's root method. That's what I used, and my phone's good.

jason.hamilton said:
Yea load up the Su app and ugrade binaries. That should fix the issue. Ive had issues like this on other phones.
Click to expand...
Click to collapse
I've also had a situation where the Busybox version installed on a custom ROM on my HTC Flyer tablet interfered with some apps (like Titanium). Make sure Busybox is up to date. I even had to install a different Busybox installer in order to get it to work right on my Flyer in that particular instance. I had to use the JRUMMY16 version in the market, and not the Stericson installer (which seem the most popular).

No packages were installed with the root.
I'll try using paulobrien's method later and hopefully that will work.

Strange Root behavior - New apps can't get root

I have had my tablet rooted since I got it pre-4.2.1. I was trying to setup TWRP as I finally decided to ROM my device and ran the unlock tool.
However, once I got past that and tried to use goomanager and TWRP manager, I realized apps were not being provided root any longer. However, the old apps that were approved in Superuser continue to get root and think that they have root, such as Titanium Backup, SManager, ES Explorer, etc. They continue to function as expected. However in SuperUser the logs have not updated in quite a while.
I've done several steps and reviewed a few related threads. Changing the prompt settings have not done anything, and I've tried several combinations of setting it to allow, setting it to prompt, rebooting etc. To confirm root is actually working I ran SManager and ran /system/bin/su which does work, and causes SuperUser to show new root access. Along the lines, I've nuked my dalvik cache using SManager and rebooted.
However, nothing else updates the logs, and new apps do not get root. Based on some other thread, I used voodoo OTA rootkeeper to remove root and then ran motochopper. Root came back, but continues to have the same behavior. SuperUser is unable to update itself, although it does show the binary as up to date. When I try to run an update anyway, it fails at the getting root step. SuperSU, rootchecker, android root toolkit all fail.
I am hoping I can figure out how to fix this, even though I unlocked the tablet, I'm traveling and not in a position to flash in TWRP. Since running SU works and previously approved apps also work - I think there is someway to restore full root capabilities. Any suggestions are appreciated.
ASUS Transformer Infinity TF700 - rooted/stock
Motorola ATRIX 4G - Rooted/Currently Stock/No longer in use - anyone need a guinea pig?
Motorola ATRIX2 - vanilla
ASUS Transformer TF101 - now vanilla and given to the wife
Really I swear I've had lots of roms on these devices at other times.

5.3.6.4?

This is downloading on my device? Is this going to brick it?

No it's fine. Lots of us received that update the days. I don't see anything new but the performance after the update seems very good.
Sent from my iPhone using Tapatalk

Why would you think it would brick your device?
Did any of the previous updates brick it?
I know the number looks strange - it really should be 5.6.... not 5.3, but that's a mistake on Amazon's end as the "Learn more" link to the User Guide has the correct number.

OP had probably downgraded his tablet to a earlier version of FireOS like I did and installed the play store and nova launcher. I havent used it in a few days but when i got it out today, it said it downloaded and installed 5.3.6.4 on 11/11/18 at 1:16am... which is weird because I had previously used this guide to downgrade to 5.4.0.0 ( https://forum.xda-developers.com/amazon-fire/help/fire-7-2017-7th-gen-downgrade-debloat-t3699937 ) and this "update" seems to have downgraded it even further. But nothing has changed except the version number. Lockscreen ads and all the bloat is still gone and nova is still my launcher, so having the update message appear is very head scratching...
BTW, i did the downgrade to 5.4.0.0 MONTHS ago, and have never seen an update message until today. In fact, if I went into the Device Options and selected System Update, it wouldn't allow me into the setting...it would just kick me back to the home screen. Now it DOES allow me into the setting. Very strange.

5.3.6.4 Update remove root?....
After receiving the 5.3.6.4 update on my HD 10 (11/15/18) -
Lock Screen Ads re-appeared on reboot
Titanium Backup - "no longer finds root" (and in turn, no longer works)
SuperSu - No longer works
Nova Launcher remains in-place oddly enough
I have since theoritically (read on) uninstalled all apps mentioned above and re-rooted via kingoroot and can access a root prompt via ADB (id reflects uid=0(root) gid=0(root) context=u:r:init:s0), however I have been unable to update the binaries for SuperSU despite multiple re-installs and reboots (I'm running the previously working v2.79 btw). Additionally, when I now run a fresh install of Titanium BackUp, all I get is an ongoing "Detecting SU & Busybox..." message onscreeen that leads to no where (I just re-installed BusyBox prior) AND when I run Root Checker, it relects no root as well, despite both kingoroot reflecting root within it's app and my ability to run su via an adb shell on my PC., though please also note that I am unable to run su via a shell/terminal emulater installed on the device ("su: not found").
Thoughts?....thanks in advance for the assist.
Peace.