Database Users

Rooted but not Rooted

I rooted my phone following these instructions. All seemed great. I then downloaded BusyBox and it says I am root but can't install as I "may not have nand root access".
Also when I connect to the Terminal Emulator I downloaded from the market place and from ADB SHELL I get "Permission denied" when trying to su. Any ideas??
I followed Part 1 and Part 2 in the video. JuiceDefender shows I am root and so does BusyBox. I also have SuperUser application but nothing shows in the logs or in the application list. I figured I get notified if an app asks for SU but nothing notified me. Just "Permission Denied".

Still no idea. Fiddling around with it and it still thinks it's rooted in some applications but a adb shell or terminal emulator (on the phone) and it says SU permission denied.

Do you have a superuser icon?!

yep. sure do. it shows empty logs and applications.

Try and install setcpu or wifi tether and see what u get? If u install setcpu and try and use it and get denied u will know right away if u r really rooted. same with wifi tether, it will say denied!

davidstjohn1 said:
Try and install setcpu or wifi tether and see what u get? If u install setcpu and try and use it and get denied u will know right away if u r really rooted. same with wifi tether, it will say denied!
Click to expand...
Click to collapse
WTF... LOL
Okay, so I download Wireless Tether for Root. Installs fine. Opens fine. Start tethering and get prompted to allow root access from SuperUser. I allow and tethering starts no problem.
So, how come I can't get SU as root? How come I can't install BusyBox (maybe nand not unlocked)?

Problem resolved.
Re-rooted with Unrevoked 3 and it works. Funny because unrevoked failed.

Unable to Re-Root Droid 2 after Gingerbread OTA

Here's my problem,
I had the Droid 2 with stock ROM rooted and all was well. My phone installed the Gingerbread ROM (4.5.601) when Verizon pushed it out a few days ago. Thankfully, this did not totally jack up my phone. However, I no longer have root access.
I have tried three different 1 click root methods for the Gingerbread ROM but none of them worked. I tried un-rooting and re-rooting with one clicks and that's not working. I tried manually removing the Superuser app and rooting, no joy.
The one clicks are connecting with the phone but the phone does not seem to want to allow access to change files.
Before anyone asks, YES I have the drivers installed and the connection with the PC is good. I have attempted to run the 1 click roots in "charge only" AND "PC Mode". Debugging is on and I am set to allow non-market applications.
Suggestions?
Thanks,
Tracker

Update: in trying to manually remove old superuser file with adb shell, I just can't seem to get the # prompt to execute the commands even after running Pete Souza's exploits.
suggestions?

Hope somebody comes up with an answer - same thing happened to me.

did you use the d3 root method? thats the only one that works 100% on gingerbread.

Yes. I used the "Pete's Motorola Root Tools.exe" program on Win7:
psouza4.com/droid3/#root
I also followed the "Droid X Notes" section at the bottom even though I have the D2 and I'm not able to get the "adb shell" ending with #.

SOS!!
Thank you for such a clear, concise post! I am in the same boat with no luck. I used the one click root for D3 which says it will work for a number of Android phones, including the D2 Global, but is NOT working with my D2. I have run the application two times and both times it went through the entire process, rebooted my phone three times and said success but...no success... I am sooo bummed as the only way I get internet at home is via Wireless Tether which I can no longer use because I do not have Root access!
Desperate in Cool (the name of the town I live in), I need help!!
Thanks in advance,
Jeni

Yeah, still no joy here. I've retried everything that I mentioned in the OP and still can't get the # so I can execute an un-root and/or re-root as described on Pete's website.
I've tried it on both a Win XP and a Win 7 machine.
Anyone have any suggestions? It appears the D2 Gingerbread firmware doesn't want to allow permissions to modify certain portions that were allowed before.

Success
I didn't so much fix the problem as hit it with a bat until it shattered, then rebuilt it.
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
At this point I'm getting some force-close errors which I'm sure are related to the Titanium restore but I was able to ADB Shell in and SU so I know I have rooted it properly and at the very least I will do another clean wipe and restore individual applications one at a time so I know which aren't working right and go from there.
Good luck everyone!

My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
Click to expand...
Click to collapse
I kinda figured that this would work. I'm trying to avoid a full nuke of the phone, but so far it appears that this is the only work around.
Anyone else got a plan?

Only option I was going to provide was SBF to 2.3.2 with RSDlite and re-flash the OTA, then run the Droid3 exploit.

I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================

drumster said:
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
Click to expand...
Click to collapse
IMO this instruction should be stickied.

This worked perfectly on my wife's D2G. Rooted Gingerbread = a good start to the day!

Awesome! Thanks!

Just wanted to say I think i love you...this worked for me after two tries on my Droid 2.
First time I was able to remove su and busybox...then when I applied the one click root again, it said there were a bunch of errors but still succeeded. After the reboot I didn't get superuser access yet so I went through deleting su and busybox again (but busybox wasn't found)
The second time i decided to restart my phone before running the script again and when attempting to verify if su was still installed by going into adb shell...it said my phone was already rooted.
Thanks!!

Awesome!
Thanks! This worked for me as well! (after additional reboot)

Good Info but one problem for me
Since I did the OTA Gingerbread, I cannot get into debugging mode. I have uninstalled the Moto drivers & reinstalled using my administrator profile on Windows 7. I have also sbf my phone. Wipe cache. Factory reset. Activate service (NOT download or sync w/ google). OTA Gingerbread. This is on a regualr D2. Anyone have any ideas on how I can get into debugging mode. Otherwise I can't do anything.

Thank you!
I am so glad I found this post and the directions posted by drumster. I had previously used z4root and had not unrooted before allowing the Gingerbread upgrade. Pete's application fixed my Droid 2 on the first attempt; no other steps were needed.
Thanks again,
Andrew

awesome
psouzas 1 click worked for me. Droid 2. previously had rooted with deroot method until it updated by itself to gingerbread which broke root.
enabled usb debugging
in pc mode, clicked on souza's link and followed instructions
i have win 7 64 bit computer

It works
I just got it to work. I was on rooted froyo. Sbf'd back to stock froyo. Downloaded and installed OTA G bread. Then I had to run the D3 one click root method twice but the 2nd time it worked fine.

[Q] I need help with Ice cream Sandwich loop

I updated my new kindle fire, then rootet it successfully.
After that i installed the Ice Cream Sandwich 4.0 and made it the default launcher.
But this failed, when i now start the kindle fire i get caught into the loop of this error:
! Sorry
The application Ice Cream Sandwich 4.0 (process androd.process.acore) has stopped unexpectedly. Please try again. [Button: force close]
Which i can press, and then the loop starts again.
I am a noob, so please how do i get rid of this launcher ? I could need a reset or factory default or whatever, but the normal ways dont work, because i cant reach them anymore. Any Ideas how to fix this ?
/edit: I have access to my device with adb shell. so i think i can somehow change the default launcher, if someone tells me which file to change because i have no idea which is the right.

You need to figure out what the package name is "adb shell pm list packages" without quotes. Once you figure out what the package name is you can "adb uninstall name.of.package"

Hard reset it with power button.
Guide - How to hard reset Kindle Fire?

Fyi.....I just tried the hold power for 20 seconds hard reset, and it doesn't work......
Sent from my Kindle Fire using Tapatalk

I've had this problem with a different launcher and posted my solution here : http://forum.xda-developers.com/showthread.php?t=1361138
... don't worry... you can fix it... all you need to do is install another launcher or uninstall the ICS launcher... and you may be wondering how you can do that if you can't get to a usable screen.
You can still install/uninstall apps using the adb service you used while rooting. FoxDog66 mentioned how to do this if you know the package name. In my case, I could not find out the package name of the offending package, so what I did was install another launcher via the same method I installed my google apps to the sys/apps folder. with another launcher installed, I get a choice again which launcher should run when turning on.
I suggest you try foxdog's suggestion first, but if you can not find the package name then get another launcher.apk install file like GOlauncher or ADW Launcher and push or install that app the way you see google apps being pushed via the following method:
Download GOlauncher http://61.145.124.93/soft/3GHeart/golauncher/v2.68/go_launcher_ex_v2.68.apk
now make it a system app:
adb remount
adb push c:\androidApps\go_launcher_ex_v2.68.apk /system/app/go_launcher_ex_v2.68.apk
adb reboot
After reboot you should be able to choose your launcher of choice. Don't make anything default until you know you like it!!!
Now that GO Launcher just installed via my method makes it a system app. You can't uninstall system apps in the normal way, so use a program like Titanium Backup to make that pushed launcher app a NON-system app (moves it and makes it easy to uninstall the way other apps do). Titanium Backup is just a great program to have if rooted.
Good Luck.

how to uninstall buggy launcher which is set to default
Thanks for helping me.
Yes thats exactly my problem and i am now trying to follow your instructions.
The hardware reset works, but it will not get rid of the launcher.
So i try to find out the right application name to uninstall it. But *blush* i have not idea which is the right name and i dont want to uninstall something randomly.
I have some very basic skills with linux which i uses 10 years ago or so, so i am able to make a list which i attached here.
OK, i am now trying to do this:
adb remount
adb push c:\androidApps\go_launcher_ex_v2.68.apk /system/app/go_launcher_ex_v2.68.apk
adb reboot
but "adb remount" gives me back a
remount failed: Operation not permitted
I need to look closer how to install and uninstall packages now.
/edit: what i can do is:
adb shell
$
su
#
so this looks like to me that i am superuser. I also see the file system, and i can do some stuff with this shell, but its very limited because this shell is different from the shells i knew long time ago.
/edit:
ok, found something:
i am in the file system in
/data/app
here i have 3 apk:
net.adisasta.androxplorer-1.apk
mobi.SyndicateApps.ICSv2-1.apk
mobi.SyndicateApps.ICS-1.apk
and i think this is the package i installed.
/last edit:
OK folks. SUCCESS..
I just did adb uninstall mobi.SyndicateApps.ICSv2 and i immidiatly got success and got rid of the fail launcher.
VERY NICE and a warm THANK YOU for helping me.
I think i will try more now -- hehe.
Just tasted some blood now. Probably i will be soon here with the next problem. But i really appriciate your help. Hopefull soon i will be more into it and be able to help other noobs, too.
Also if someone needs german help because of language barrier, i can help translating.
Best Regards
Usurpine

Glad you got it fixed
A few tips.... adb remount just remount's the system partition read-write which isn't needed unless the app is installed to /system/app (it also does not work. It does work with doomlord's kernel, i think because of the insecure ramdisk)
The "./" part of your command just means to run in the current directory, if you have fastboot or adb in path then you don't need that part and you can also run the commands from any directory. if you don't have them in path then you would need to have what you wanted to flash, boot, whatever in the same directory as fastboot/adb. To check if something is in path (let's say fastboot) you can type "which fastboot" and it will either tell you where it is (something like ~/Android-sdk/platform-tools/fastboot) or it will say, couldn't find fastboot and it will list out a bunch of directories.
One last thing, you can chain commands together with "&&" so say i want to "fastboot boot newboot.img" i would plug my kindle in, press the disconnect button that pops up on the kindle then type in terminal "adb reboot && fastboot boot newboot.img" if/when the first command runs successfully then it will run the second command. If it does not run successful, it won't run the second command. Also, for me, adb reboot takes a few seconds to work and fastboot waits for the device for a few seconds also.
Hope this is useful, I'm not always good at explaining things. I'm also not a Linux pro lol these are just a few things i have learned that are pretty useful

Well, this is useful. Basically you are talking about how to work with linux. Once i understood that inside my kindle there is just a typical linux i can take one of my old linux books and use any command (like the && and other stuff).
I am not a pro with linux (forgot almost everything) but now i know how to look after it and be able (limited) to use it after some testing.
That said, i now was able to do a lot of funny stuff with my kindle, i installed tons of applications just to look how it works (and it works great) and uninstalled them after that.
Now i can watch movies, listen music, play games and can do almost everything what you normally cannot do with a kindle due to amazons restrictions.
What i want to know is how i can extend the linux inside my kindle so it is using a shell which can do even more stuff, like a ksh (korn shell) or something. A shell with commands like i can find in a "normal" linux installation. Is that possible ?
And how about installing a more linux like grafical userinterface ? Or use the kindle as a normal linux pc, just for fun ?

Ummm..... Have you looked at busybox? It is possible to port command line tools to Android. I've seen things like cURL and lynx that worked. Porting and compiling is a little out of my league (wish it wasn't lol, I'd like a updated cURL binary with https support) i know bash scripts work, I've written a few and "run-parts" (part of busybox) will run a directory of scripts.
You should get into (or look into) custom Android development and/or kernel development. There is a lot that can be done

Help, im a real newbie
usurpine said:
I updated my new kindle fire, then rootet it successfully.
After that i installed the Ice Cream Sandwich 4.0 and made it the default launcher.
But this failed, when i now start the kindle fire i get caught into the loop of this error:
! Sorry
The application Ice Cream Sandwich 4.0 (process androd.process.acore) has stopped unexpectedly. Please try again. [Button: force close]
Which i can press, and then the loop starts again.
I am a noob, so please how do i get rid of this launcher ? I could need a reset or factory default or whatever, but the normal ways dont work, because i cant reach them anymore. Any Ideas how to fix this ?
/edit: I have access to my device with adb shell. so i think i can somehow change the default launcher, if someone tells me which file to change because i have no idea which is the right.
Click to expand...
Click to collapse
Please help me, I really have no experience and I followed a link that made it look very easy to install the ICS Launcher. Now I keep getting that same page and it's driving me up the wall.
I have tried the adb so I can uninstall the faulty apk myself but my mac wont detect it even though it still mounts.
Iv done the adb devices but the list is empty.
Please help me in a very easy way to understand.

[Q] Droidwall fail on rooted Kindle 6.3 stock

Hi,
I'm trying to get Droidwall working on my Kindle Fire - it has the 6.3 update and I used the Kindle Fire Utility 0.9.5 to root and install Google apps. I've got GMail, Google Play and GTalk all working fine. However, I'd like to prevent any future Amazon OTA updates so I'm trying to block access with Droidwall. I've installed it but when I enable the firewall it says "could not acquire root access ... error: permission denied".
I can use "adb shell" and then run the "su" command so it all appears to be working - why doesn't Droidwall work?
Please excuse me if this is the wrong place to ask the question, or if I've missed something obvious. But I've searched around and can't find any answers to this.
Any help much appreciated!
Thanks,
Rob

sorry - can't tell you about droidwall but this is much easier to prevent ota:
http://forum.xda-developers.com/showthread.php?t=1451328

Thanks - I'll try that out. I'd still like to know why Droidwall doesn't work, though. It implies that rooting the kindle didn't work properly. I checked the permissions on /system/xbin/su:
-rwsr-sr-x root root
Are there any problems with that?

Ok, after some more digging around I worked out what the problem is - Superuser wasn't installed properly (it wasn't doing what it should be doing and no mention was made to it in the list of applications on the Fire). KFU should install superuser but it must've failed.
I installed it manually from the Market and this time, when I try to get Droidwall working I have a pop-up asking me to allow the app to get super user privileges, and after accepting this it works.
Originally I wasn't aware of the role that the superuser app plays in the process, which was causing my confusion here. Glad it's fixed, though!

glad that you got it working ...
please mark the subject of the topic (edit first post) with [Solved]

[Android Box] How to remove invalid su files or get kingo root back to normal? Need help

This is an Android TV box, equipped with a deeply modified android 4.4 system, while the device is shielded from usb interface adb debugging, the only way to adb is to use root privileges to actively start adb wifi from the device.
I tried kingo root yesterday, and it's the only root tool I've found so far that still works with one click.
Seemed to have good luck as it worked once, but after I rebooted it today, kingo superuser tells me the device is not rooted yet.
I noticed that the location /system/bin/su still has a valid binary file (about 70KB in size).
I even installed a terminal emulator to actively execute the su command, but the result should also be as you guessed, no errors reported and no log output, and again, my permissions did not change from $ to #.
I've tried Google, but haven't found anything useful.
Is there anything I can try to solve this problem? I've tried sending a tweet to kingo root and sending feedback to the official website, but the last tweet on its Twitter feed was sent in 2018 and I think it's unlikely that anyone from the official team will be able to see my feedback.
So I'm trying to ask for help on the XDA forums, this is my first post here and I hope I'm not sending it to the wrong partition.
Thank you all.
===
Finally, I'd like to add a bit of information.
Since kingo root thinks the device is rooted, there is no way for me to get it to perform the root steps all over again.
Also, although kingo superuser provides the ability to remove root, there is no way for me to use it to remove this su file and kingo superuser since it suggests the device is not rooted, which seems to be stuck in a dead end loop
Even because it's a box, I don't even seem to have a way to get into fastboot
===
这是一台安卓的电视盒子，搭载的是经过深度修改的android 4.4系统，同时设备从usb接口上屏蔽了adb调试，想要进行adb的唯一办法就是使用root权限从设备上主动启动adb wifi。
我昨天尝试了kingo root，这是我目前找到唯一的一个还能够运行一键的root工具了。
看起来运气不错，因为一次就成功了，但是我今天重启了它之后，kingo superuser告诉我设备尚未root。
我注意到/system/bin/su这个位置依然存在着有效的二进制文件（大约70KB大小）。
甚至我还安装了一个终端模拟器，主动去执行su命令，但是结果也应该正如你所猜测的那样，没有报错，也没有输出log，同样的，我的权限也没有从$变成#。
我尝试过谷歌，但是没有查到过什么有用的东西。
请问我有什么可以尝试的办法去解决这个问题吗？我已经尝试向kingo root发送推特和向官网上发送反馈，但是它的推特上最后一条推文是在2018年发送的，我认为官方团队不大可能能够有人看到我的反馈。
所以我尝试在XDA论坛上寻求大家的帮助，这是我第一次在这里发帖，希望我没有将帖子发送到错误的分区。
谢谢大家
===
最后，我想补充一点信息。
因为kingo root认为设备已经root了，所以我也没有办法让它重新执行一遍root的步骤。
另外，虽然kingo superuser提供了移除root的功能，但是由于它提示设备无root权限，我也没有办法用它把这个su文件和kingo superuser移除掉，这看起来似乎陷入了一个死循环
甚至因为它是一个盒子，我似乎连进入fastboot的办法都没有