Hello everyone, I have been tring to root my phone for two day. I tried the z4root and it gets to rebooting and just stops, it finally reboots when I press the home button but it never installs super user app. I went to unlocker and tried androot, nothing. At the end of superone-click short fuse it failed the test for su permissions but installed superuser but it wouldnt do anything. Please help me root this phone. I have an Alltel phone. Kernel ver. 2.6.29-bc0d2cff firmware ver. 2.1-update 1 baseband ver. 2.42.01.04.23 if you need more info just pm me.
Thanks
I have never used these one click methods, but, if it actually roots it, just download super user from the market? Or just use one of the rooting methods found in the Development section (yes, you will have to read a short list of instructions).
I used z4 and it got stuck like you said, i clicked home and for me superuser was there.
but since not try rebooting and if its not there then, download android terminal emulator.. type su then press enter. if you see a # then youre rooted, so go just download superuser from the market and you should be solid
Try super one click. It installs superuser when it installs root files.
Sent from my HERO200 using XDA Premium App
stayclean said:
I have never used these one click methods, but, if it actually roots it, just download super user from the market? Or just use one of the rooting methods found in the Development section (yes, you will have to read a short list of instructions).
Click to expand...
Click to collapse
I tried it your way and this is what happens... So any Ideas
5. Then type:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
[1] Killed /data/local/asroot2/system/bin/sh
6. Then type:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
operation not permitted
I tried this one.. It didnt work..
but thanks..
Related
Obviously a radio difference, but what else prevents roms being easily ported to Milestone from Droid? Im not sure on the internals differences, but could we start porting.
NB do we even have root !?
we have root on both devices i think the exploit may be the same? forgive me if i am wrong.
(root guide for 2.1) the latest update at time of this post.
http://android.modaco.com/content/m...m/308422/milestone-2-1-update-and-root-guide/
the problem on the milestone as anyone will tell you, the LOCKED BOOT LOADER this isnt a problem for the Droid users, they got this for free. Hopefully with the power of the XDA super Dev team, we will have a solution for this, and start pumping out custom roms!
all of the accessories fit for each other, which maes it handy if you want some cheap bits from china, there isnt any carrier in the uk that has the milestone, what i am saying... carrier.. i mean mobile phone network!
i got my milestone from here. buymobilephones.net on a contract, but you can also get them from expansys, as far as i have researched, they are all unlocked. So you shouldnt even need to post about unlocking the sim.
there is another differnce i remember, if you are loading busybox on your device, this will not load if you use droid root helper from the market, you will need to manually do this via ADB and the loaction on the partition is different.
carphone warehouse sell the milestone on t-mobile and you can install busybox with droid root helper.
The kexec modules are nearly working. So there will be a 2nd bootloader in near future.
http://and-developers.com/motorola_milestone
I messed my first one up when I used droid root helper, but I have recently download titaium backup and that says it has installed busy box for me over the net. But terminal tells me no busy box found, the only way I have had it working was via the manual install.
iamdarren said:
I messed my first one up when I used droid root helper, but I have recently download titaium backup and that says it has installed busy box for me over the net. But terminal tells me no busy box found, the only way I have had it working was via the manual install.
Click to expand...
Click to collapse
Titanium installs busybox in its own data directory so that only it can access it.
Cool that answers that. I want to put busybox back on to use cachemate again. But can't find any instructions. So haven't yet
Main difference is the locked bootloader , there is a signature verification at boot time that prevents us from running custom Kernel .
Its unlikely that the bootloader signature will ever be cracked , other workaround like Kexec will most likely help achieve further mods to our device eventho it seem to be right around the corner there is still much work to be done
iamdarren said:
Cool that answers that. I want to put busybox back on to use cachemate again. But can't find any instructions. So haven't yet
Click to expand...
Click to collapse
Download Busybox and use this to install it:
Code:
ADB push busybox /sdcard/busybox
ADB shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
# cat /sdcard/busybox > /system/bin/busybox && chmod 700 /system/bin/busybox
# sync
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system
Its better to push it to xbin and not to bin, as the most apps search there for the busybox
After Titanium had installed busybox, I opened Root Explorer and moved it from Titanium's data folder to /system/xbin (had to temporarily mount R/W to do so, using the button up top). Titanium is still happy as it still finds busybox. Do I need to do anything else for other programs that require it?
cmstlist said:
After Titanium had installed busybox, I opened Root Explorer and moved it from Titanium's data folder to /system/xbin (had to temporarily mount R/W to do so, using the button up top). Titanium is still happy as it still finds busybox. Do I need to do anything else for other programs that require it?
Click to expand...
Click to collapse
your good ..
ok, so i tried to get help in the actual froyo 2.2.13 install thread but i'm not getting an answer.
i downloaded, installed, and it said it was successful.. i rebooted, went into the settings to see if it changed, and it still said 2.2.9. i tried to do it again and now my phone will not reboot into recovery using droid x bootstrap or rom manager... won't even go into it if i do it manually... i tried to uninstall bootstrap and rom manager and reinstalling, no luck. please help.
brandon2x said:
ok, so i tried to get help in the actual froyo 2.2.13 install thread but i'm not getting an answer.
i downloaded, installed, and it said it was successful.. i rebooted, went into the settings to see if it changed, and it still said 2.2.9. i tried to do it again and now my phone will not reboot into recovery using droid x bootstrap or rom manager... won't even go into it if i do it manually... i tried to uninstall bootstrap and rom manager and reinstalling, no luck. please help.
Click to expand...
Click to collapse
Try these comands from :
AllDroid Public Board»Motorola»Droid X Forums»Droid X Rooting»How to get 2.2, Rooted, on your Droid X
under:
If you have /system/xbin/su and /system/app/Superuser.apk, but cannot use "Superuser" (no prompts from Superuser app, "permission denied" when you try to run "su"), just do the following:
Run "adb shell"
Run "/system/xbin/su"
Watch your screen for Superuser app to prompt for permission and click "allow"
Run "mount -o remount,rw /dev/block/system /system"
Run "cp /system/xbin/su /system/bin/su"
Run "chmod 4755 /system/bin/su"
Open the SuperUser application on the phone (app launcher) and make sure that "superuser" isn't listed and denied. If so, "forget it" and return to step 2. If you can't find SuperUser, it's not installed and you should download from this posts attachments and "adb install Superuser.apk"
[optional] Run "mount -o remount,ro /dev/block/system /system"
This should help you get your su working again.
not sure on your process so if you still do not have the .13 I would go back to your process and see what you are missing. I rebooted into recovery from bootstrap when I installed mine. Then I had to do the above commands to get my su back.
If you still don't have it, try the FULL instructions from here:
MDW Presents: Droid X 2.3.13 - The Froyo Upgrade
read through it and see if #5 from step 2 pertains to you.
The biggest thing to remember is to mount before you select the file to load on your sd card.
This thread:
Motorola Droid 2Droid 2 Android DevelopmentHow to root the Droid 2
will also be helpful regarding root if you have further questions.
Hope this helps.
My su is working fine. Nothing is being denied when I open it. Just cannot get to recovery with any option... im lost...
Sent from my DROIDX using XDA App
Maybe just double check through adb shell even if you are not having su issues?
Run "adb shell"
Run "/system/xbin/su"
Watch your screen for Superuser app to prompt for permission and click "allow" (I never saw any request)
Run "mount -o remount,rw /dev/block/system /system"
Run "cp /system/xbin/su /system/bin/su"
Run "chmod 4755 /system/bin/su"
I had similar issues of nothing being denied after a successful install and had to do the su commands. It helped me to reboot into recovery afterwards.
Sent from my DROIDX, Froyo FTW. Obsidian?
Ok im still learning.... how do I "run adb shell" and do these commands you're telling me...
Sent from my DROIDX using XDA App
brandon2x said:
Ok im still learning.... how do I "run adb shell" and do these commands you're telling me...
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I saw your post in the other thread. The best thing you can do is go through the links I gave you. Start with the root thread and click the more directions link in it. read through the processes and make sure you download all files and also understand what sbf is. Once you have all of the tools to do root and load whatever leak or rom you want you should be set. Understanding what is going on is key. This is a decision you are making to alter your phone for your benefit. Take the time to download SDK and whatever else is needed for your computer. Become familiar with what shell is and how to get there as well as explore within it. If you can get shell down and how to access your su and run commands, you should know enough to start. There are many things you need to research in order to be confident in what you are doing. I am sure you will not have a problem, just putting the time in to figure out everything is key. This is what I had to do.
I think that this is the best advice I can give you. None of us can know exactly what you are doing so you need to know the processes and choose which one is going to work for your circumstance. Good luck and if you have anymore problems I am sure all of us on xda can figure out a solution for you.
ok, finally, with a little help i got my phone rerooted and back to normal. learned a lot in the process too. thanks to all...
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.
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
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