Database Develop

Problem with one click root method and me lol

Hey all. I upgraded to froyo 2.2 manually on my droid x a couple weeks ago and then used the one click root method for root. i downloaded several programs that required root and used them successfully. but these programs suddenly stopped working. set cpu for instance says it cant get root and i installed clockwork to try some of the mods out there and none of the commands in that program work (like i cant boot into clockwork recovery or install a rom). I've also tried unrooting it using the same program i rooted it with and THAT doesnt work. Does anyone have any suggestions? Thanks in advance for the help.

arstinince said:
Hey all. I upgraded to froyo 2.2 manually on my droid x a couple weeks ago and then used the one click root method for root. i downloaded several programs that required root and used them successfully. but these programs suddenly stopped working. set cpu for instance says it cant get root and i installed clockwork to try some of the mods out there and none of the commands in that program work (like i cant boot into clockwork recovery or install a rom). I've also tried unrooting it using the same program i rooted it with and THAT doesnt work. Does anyone have any suggestions? Thanks in advance for the help.
Click to expand...
Click to collapse
Well I am not sure how you got it to work but the one click method doesn't work on 2.2. There is a manual root method found below with the files you need to do it manually.
http://destdroid.com/showthread.php?11-Droid-X-2.2-Root-Manual-Method
Sent from my DROIDX using XDA App

most likely its in xbin instead of bin; so u have to move it.
1. adb shell
2. system/xbin/su
3. mount -o rw,remount /dev/block/system /system
4. cp /system/xbin/su /system/bin/su
5. chmod 4755 /system/bin/su"
6. ls /system/bin/su" (make sure the results are "/system/bin/su" and NOT "/system/xbin/su" - If you see this, repeat the previous step.)
7.exit
8.exit
9.adb reboot

thanks guys. i rooted it before upgrading actually. just after the upgrade it seemed to have problems. i will try these things and let you know how it works out. thanks again!

[Q] stuck rooted HELP! Nexus One

I was using Universal Androot on stock 2.2. The 2.2.1 OTA came through and after ignoring it for a few days, I accidently installed it. Now I can't unroot with Universal Androot, keeps saying "Failed! You still have the power, my lord.." Now things like AdFree say unable to get root access, and the SuperOneClick won't get past "waiting for device..."
Any way to fix this without completely wiping the phone?

doughanson78 said:
I was using Universal Androot on stock 2.2. The 2.2.1 OTA came through and after ignoring it for a few days, I accidently installed it. Now I can't unroot with Universal Androot, keeps saying "Failed! You still have the power, my lord.." Now things like AdFree say unable to get root access, and the SuperOneClick won't get past "waiting for device..."
Any way to fix this without completely wiping the phone?
Click to expand...
Click to collapse
Yes. Searching the forums for the various ways how to root 2.2.1

The problem is that it already says that I am rooted. But any app that requires root says that I'm not. I think it might have to do with being rooted with androot while the update happened. I want to try to avoid factory resetting the phone if possible.

doughanson78 said:
I was using Universal Androot on stock 2.2. The 2.2.1 OTA came through and after ignoring it for a few days, I accidently installed it. Now I can't unroot with Universal Androot, keeps saying "Failed! You still have the power, my lord.." Now things like AdFree say unable to get root access, and the SuperOneClick won't get past "waiting for device..."
Any way to fix this without completely wiping the phone?
Click to expand...
Click to collapse
I have the same problem. I tryed to restore to my 2.2 backup i made on rom manager before updating to 2.2.1 but it do not work.

nexusdue said:
Yes. Searching the forums for the various ways how to root 2.2.1
Click to expand...
Click to collapse
No research ... no gain.

it may say it but you dont.. why it says it cause it still sees the su in xbin and superuser in app.. but if you read the 2.2.1 update it did remove everything with root.. which sucks.. i have instructions on how to root 2.2.1 with rage..
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb shell
$chmod 700 /data/tmp rageagainstthecage
exit
go to sdk/tools
/tools>freenexus.bat
adb shell
$cd data/local/tmp
ls
check if all files are in
rage
su
Superuser.apk
busybox
$./rageagainstthecage
743C[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}[*] Searching for adb ...
[+] Found adb as PID 64[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
DONT TYPE ANYTHING TILL YOU HERE THE ADB ON PHONE RESTARTS.
C:/adb kill-server
C:/adb start-server
adb shell
#
should get pound sign if not run ragecage again and dont do anything to you here the last ding on computer
#cd /data/local/tmp
#./busybox cp busybox /system/bin/
(if get read-only error do this
mount -o remount,rw /dev/block/mtdblock3 /system)
#chmod 4755 /system/bin/busybox
#./busybox cp Superuser.apk /system/app
#./busybox cp su /system/bin/
#chmod 4755 /system/bin/su
#exit
if $ type exit again
then go into terminal on phone, and type su
if you get the # you have root once again! yay!
now to install busybox command
hope this will help you to get root back..
i found this so this may work for you and easier to do
http://forum.xda-developers.com/showthread.php?t=803682

I have done both the rageagainstthecage to see how hard it would be but if you follow step by step, you'd be fine. I have also upgraded to 2.2.1 and tried SOC and that works as well. After I used SOC, I reverted back to 2.2 and loaded Rod's Rom again. I was curious

What is SOC and how did you get back to 2.2?
Sent from my Nexus One using XDA App

Super One Click root, I believe.

cannot root with superoneclick?

Hi, i need to unlock bootloader of my galaxy tab so i need to root first and so i selected exploit (psneuter) and rooted with superoneclick and then when i copy patch to tab and run it it says "This application requires superuser(root) to function"
Can anyone help me?
Here is log of superoneclick:
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
1743 KB/s (585731 bytes in 0.328s)
OK
chmod psneuter...
OK
Running psneuter...
ROOTED
Pushing busybox...
1748 KB/s (1062992 bytes in 0.593s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/stl9
OK
Reading OS Version properties...
Version: 2.2
OK
Remounting system with read-write access...
OK
Pushing su-v2...
547 KB/s (26264 bytes in 0.046s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1023 KB/s (196521 bytes in 0.187s)
OK
Remounting system with read-only access...
mount: mounting /dev/block/stl9 on /system failed: Device or resource busy
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!

sorry for double post, pc problem

is superuser installed? if not get it from the market. Try some othe root apps (set cpu etc or http://www.talkandroid.com/android-...391-how-can-i-tell-if-i-have-root-access.html You are responsible if you brick it though

Yes superuser is installed but still get error says "This application requires superuser(root) to function" when i run the patch...any ideas?

andrew21 said:
Yes superuser is installed but still get error says "This application requires superuser(root) to function" when i run the patch...any ideas?
Click to expand...
Click to collapse
There must be another exploit in the package - try it (in my case psneuter was killed by AV guard immediately after unzipping package, so I had to use a second one).

qmanager said:
There must be another exploit in the package - try it (in my case psneuter was killed by AV guard immediately after unzipping package, so I had to use a second one).
Click to expand...
Click to collapse
Im sorry but i dont understand what you say

Can you get such using terminal emulator or adb shell
Sent from my GT-P1000 using XDA App

brilldoctor said:
Can you get such using terminal emulator or adb shell
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Well i dont the piece with me anymore so i cant test but just need to know, do i have to unlock the bootloader if i want to flash stock rom with ODIN?

May sound crazy but I thought my root didn't take using one click. No apps that require root would work. All I did was reboot my tab and everything was fine. Took me a few hrs but a simple reboot did the trick.
Sent from my SPH-P100 using XDA Premium App

Maddball said:
May sound crazy but I thought my root didn't take using one click. No apps that require root would work. All I did was reboot my tab and everything was fine. Took me a few hrs but a simple reboot did the trick.
Sent from my SPH-P100 using XDA Premium App
Click to expand...
Click to collapse
Ok will try that next time i root my tab..thanks

[Q] Rooting TELUS Optimus Black

Anyone figured out how to do it? I've tried following the guides with no success (gingerbreak). Model is P970g and software is 10a. Country code is TLS.
Anyone have a Telus OB and been able to root it? How did you do it?

I've rooted a couple of them, both 10a on Telus, one of them was pretty easy using z4root. Another one wouldn't work with z4root, latest superoneclick, gingerbreak or manually using adb shell to gingerbreak, rageaggainstthecage & psneuter. I did finally get the stubborn one to root wither an older superoneclick; version 1.6.5. Attached it below as it doesn't seem available in CLShortFuse's thread anymore.
Goodluck

alexredford said:
I've rooted a couple of them, both 10a on Telus, one of them was pretty easy using z4root. Another one wouldn't work with z4root, latest superoneclick, gingerbreak or manually using adb shell to gingerbreak, rageaggainstthecage & psneuter. I did finally get the stubborn one to root wither an older superoneclick; version 1.6.5. Attached it below as it doesn't seem available in CLShortFuse's thread anymore.
Goodluck
Click to expand...
Click to collapse
I tried both z4 and the superoneclick you suggested to no avail.
Do you think it's safe to try flashing another vulnerable rom? 10b or 10c? I'm worried the basebands may be different and the phone will have no voice/data connection.
Running out of ideas.

Attempted to root another one, same model, same version and none of the previous methods worked, was able to root this one as well using a combination of SOC 2.1.1 and the attached ADB Shell.
1. Download and run SuperOneClick 2.1.1, choose psneuter and click Shell Root
2. It should get stuck on step #4, run task manager, end superoneclick and terminate any adb.exe processes. (You should have Shell Root now)
3. Extract ADB.zip and open a command prompt to where you extracted it.
4. Enter the following commands
Code:
adb push su /tmp/
adb push Superuser.apk /tmp/
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
cat /tmp/su > /system/bin/su
cat /tmp/superuser.apk > /system/app/Superuser.apk
chown root.root /system/bin/su
chmod 06755 /system/bin/su
chown root.root /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
reboot
The permissions on /system/bin/su didn't stick the first time for me, and the phone rebooted a couple times, but eventually it all went through. To verify permissions on su, type "adb shell", then "ls -l /system/bin/su". The permission should read -rwsr-sr-x, if it doesn't repeat the shell root process and type
Code:
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
chmod 06755 /system/bin/su
ls -l /system/bin/su

Ok, i've figured out what the problem is. As soon as the adb process from SOC is shut down, the phone soft reboots and I lose temporary root. I've tried the psneuter exploit in the same adb command shell, but it hangs just like SOC. I've tried to be "quick" and get the commands in before the reboot, but it isn't possible.
Suggestions on how I may bypass that? Otherwise i'll wait for the official 2.3 update in september and try again then.

One of the phones I tried it on, did the same thing, ended the adb process and phone would reboot, pushed a file, phone would reboot, set permissions, phone would reboot. Occasionally the phone would appear to hang, buttons flash at the bottom for awhile, phone becomes unresponsive. Just wait a minute or 2 and it should return to normal. I also tried creating a script to do all of the above before the device had time to reboot and it didn't help.
Persistence was the key.

Did you try that ? If following the instructions don't work for you, I let you know how it works for me.
EDIT : Sorry, forget link's thread : http://forum.xda-developers.com/showthread.php?p=14458927
Sent from my LG-P970 using xda premium

Hey i am having the same problem and am fearing bricking my phone from making a mistake. is there an easier method than those above mentioned?
Android 2.2.2
software: v10a

Sobralobo said:
Did you try that ? If following the instructions don't work for you, I let you know how it works for me.
EDIT : Sorry, forget link's thread : http://forum.xda-developers.com/showthread.php?p=14458927
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
This method worked when rooting my wife's P970g.

KDZ file
hey does anyone have the Telus firmware KDZ file? i will need it to restore my phone back to original state to cash in on a waranty (ended up bricking it, had to install a german 1&1 firmware to get it back)

s0dhi said:
This method worked when rooting my wife's P970g.
Click to expand...
Click to collapse
...which ROM did you use, the v10a EEU from the thread?
I'm worried cause on Telus 970g as well.

The_non_rootable said:
hey does anyone have the Telus firmware KDZ file? i will need it to restore my phone back to original state to cash in on a waranty (ended up bricking it, had to install a german 1&1 firmware to get it back)
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=1

BusyBox problem: installed twice, removed one, damaged system

Hello guys, please help me out with this problem! I've been working on all day but my phone is still bad...
When I rooted my device BusyBox was supposedly installed by the toolkit I used to root (mskip's).
Then I installed BusyBox installer market app (Stericson's) and it said "BusyBox location could not be found". I thought it wasn't installed so I used the "smart install" with the default values, so it was installed to /system/bin and all the applets were listed as symlinked to /system/bin/busybox
After a while I realized that it was installed both in /system/xbin (by the root toolkit) and in /system/bin (by busybox installer). I used the uninstall option from the busybox installer app to remove it from /system/bin again and leave just one installation to avoid conflicts. This was not a good idea it seems. After uninstalling and rebooting, the phone started to work incorrectly, wifi doesn't work.. and most importantly, USB connection is dead with Android fully booted. the battery charges but the PC doesn't detect it. (It works on Recovery mode though).
I have an idea of what may be wrong. I think the "BusyBox installer" changed all the symlinks to system/bin/busybox, so when it was uninstalled, the phone was left without any of the applets of busybox even though the file /system/xbin/busybox is still present.
Or maybe I'm not really rooted anymore? However, the su binary is still present in /system/xbin/su but I still can't get to work commands like "mount".
How can I fix this problem? I will greatly appreciate any suggestions.
I think it might be fixed by installing busybox to /system/bin or even just copying the /system/xbin/busybox file to /system/xbin/busybox but because the phone is not working correctly I haven't been able to do that...
Here's the information I've gathered so far for you guys to PLEASE help me out with this:
SuperSU is installed and seems to works fine.
"BusyBox Free" installer app doesn't work. If I open it, it shows only black with the three buttons in the bottom but they can't be "clicked. It has been granted root permissions.
"ES File Explorer" gets root permissions but is unable to mount /system as writable (to copy the file).
In a terminal emulator application (Jack Palevich's), this is what I get:
Code:
$ which busybox
/system/xbin/busybox
$ ls
ls: not found
$ busybox ls
(works, outputs the directory content correctly)
$ mount -o remount,rw /system
mount: not found
$ busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$ su
(the terminal emulator app has root permission, but when issuing "su" command, the cursor stays inactive for several minutes and when it finally responds, the following operations are still not succesful. The "su" doesn't seem to work.
$ busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$ /system/bin/busybox --install -s /system/bin
busybox: /system/bin/zcat: Read-only file system
busybox: /system/bin/mountpoint: Read-only file system
busybox: /system/bin/nohup: Read-only file system
My plan is to make the USB work so I can use the toolkit again to restore a stock firmware and clean this mess. Oh, I have stock recovery and stock boot image if that's of any help to know it.
How can I issue the commands I need? or fix this problem?
I have basic linux experience so if you need the output of any command please let me know.
Any help is appreciated. Thank you!

... i think that flashing cwm recovery(.tar.md5) with odin and flashing a root+busybox.zip with cwm recovery should be the fastes way to fix this .... only thing is that it erease your "costum binary count" but with the "Triangel Away" app you can reset that counter ...

Thank you for the hint, enox. I'm will try to install the custom recovery now.

Thanks again enox for pointing me in the right direction. The phone is working again. I'm sharing what I did in case it helps someone in the future:
1) Installed the custom recovery 'twrp', provided by the toolkit (program_folder/recovery/recovery-twrp-2.4.3.0-GTI8190.tar) using odin with the phone in download mode.
2) Flashed this busybox uninstaller using twrp recovery. The phone wasn't working fine yet, so I continued to the following step.
3) Flashed a root+busybox.zip provided by the toolkit (program_folder/root/SuperSU-1.25-Busybox-RenameRecoveryRestore.zip) using twrp recovery.
At this point, the phone was working fine but to be sure that all symlinks were correct, I ran an additional cleaning script which you can find at the end of this post, along with my comments talking to myself while I was troubleshooting the problem.
I'll go to sleep now. Thank you.

Got a PM and I thought it would be better if I reply to it in the forum so others can benefit as well:
andr0id_n00b said:
hey i saw your problem here http://forum.xda-developers.com/showthread.php?t=2233942 and iam glad u solved your problem
can you please tell me what toolkit do you use ??
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
mskip's toolkit for Samsung Galaxy S3 Mini:
http://forum.xda-developers.com/showthread.php?t=2185700
Big thanks to him too, for providing that noob friendly yet full-featured toolkit

same with xperia mti27i
ive exactlly made the same but with my xperia mt27i android4.0 ics i dont i know what to do i dont have exp. with android so please help