Database Info

getting root using MAC OS ??

Is there any step by step tutorial to get my htc magic rooted
I can only find posts where they say it is like on windows but without installing files but i have no idea how to enter that prompts on terminal
it would be much appreciated any help. I know i am not the only one interested

cesardeluxe said:
Is there any step by step tutorial to get my htc magic rooted
I can only find posts where they say it is like on windows but without installing files but i have no idea how to enter that prompts on terminal
it would be much appreciated any help. I know i am not the only one interested
Click to expand...
Click to collapse
The commands are the same. Just like Linux users can follow Windows directions but with some substitutions.
Download the SDK here: http://developer.android.com/sdk/1.5_r3/index.html
Follow the instructions here: http://developer.android.com/sdk/1.5_r3/installing.html
Once you have the SDK setup, you can follow the steps given in the rooting threads/wiki. Any time it says to enter a command you do it in your terminal (which on OSX i think is Terminal.app, use Spotlight to find it).
Hope this helps a bit.

i dont get this:
Code:
On a Mac, look in your home directory for .bash_profile and proceed as for Linux. You can create the .bash_profile if you haven't already set one up on your machine
i don't have that .bash_profile how do i create it?
thanks

Google easy to use and always there for you.
Clinton

yeah but all tutorials are made for xp or even linux.
I have tried to create it using vi command then edited with the path o the sdk tools
but when i type adb it doesn't do anything
i am stuck there

Did you check my link for your bash_profile ? This help at all?
Clinton

cesardeluxe said:
yeah but all tutorials are made for xp or even linux.
I have tried to create it using vi command then edited with the path o the sdk tools
but when i type adb it doesn't do anything
i am stuck there
Click to expand...
Click to collapse
Try reading this:
http://www.tech-recipes.com/rx/2621/os_x_change_path_environment_variable/
Sounds like the Path variable may be in a different file. It is the same on linux, I think it can be in a few places.
Irf you want to use adb without messing with your path you can do the following:
Code:
cd <android-sdk-location>/tools
./adb devices
This is convoluted so get that PATH working and everything should be nice and easy! Good luck.

I use a Mac, and when I was getting started I used the linux tutorials with no problem.

i can push the 2 files using commands to my sd. Adb devices shows my htc ok
but after i enter to fastboot mode the device is no longe shown
i type
Code:
./fastboot boot recovery-new.img
but the only thing i get is
Code:
-bash: fastboot: command not found
i am on tools directory on terminal

i think fastboot is not in the tools directory ...
i'd rather say the error is caused by that then a missing connection.
Does the phone write "FASTBOOT USB" ?
if you type "ls", can you find a file named fastboot in your directory?

cesardeluxe said:
i can push the 2 files using commands to my sd. Adb devices shows my htc ok
but after i enter to fastboot mode the device is no longe shown
i type
Code:
./fastboot boot recovery-new.img
but the only thing i get is
Code:
-bash: fastboot: command not found
i am on tools directory on terminal
Click to expand...
Click to collapse
The files have to be executable. You can do that by running:
Code:
chmod -R +x /path/to/tools
This makes all the files in the tools directory executable with ./
About the .bashrc or .bash_profile if you don't have one in your home directory you can safely make one. With the following command:
Code:
echo "export PATH=$PATH:/path/to/tools/" > ~/.bashrc
or if the file exists just do:
Code:
echo "export PATH=$PATH:/path/to/tools/" >> ~/.bashrc
Remember to restart the shell after you are done with this.

the reason adb work for you is because adb is in tools directory
fastboot does not. You have to get fastboot somewhere else
Whenever you get command not found, you can run another command to check
ls <program you ran>, and see what happened
Example
in your tools directory, where you have no problem running adb push, try doing "ls adb", without the quote
in your tools directory, where you have problem running fastboot, try doing "ls fastboot", without the quote
and you should see what's going on
BTW, this is fairly basic unix environment. If you are having trouble at this stage, you need to get yourself more familiar with unix environment, which is what osx is based on
I am sorry, but i don't really know where's good tutorial on unix
On google, i just search for "mac osx unix shell tutorial:, and come across this site
http://www.osxfaq.com/tutorials/LearningCenter/
Hope this help
Edit 1: btw, here's where you can find fastboot for MAC. Put it in your tools directory. IF you keep the filename as is, you need to type fastboot-mac whenever you see someone mention fastboot
http://www.htc.com/www/support/android/adp.html

yeah you're right fastboot is not on that tools directory. in fact i have looked into the whole sdk folder and i can't find it.
thanks

hey i managed to apply the update thanks to having fastboot-mac on tools folder
but after booting i go to terminal to apply the final step and i get this
Code:
MBdeluxe:tools cesarleon$ ./adb shell flash_image recovery /sdcard/recovery-new.img
error reading /sdcard/recovery-new.img header: Is a directory
what's wrong ?
thank you people

cesardeluxe said:
hey i managed to apply the update thanks to having fastboot-mac on tools folder
but after booting i go to terminal to apply the final step and i get this
Code:
MBdeluxe:tools cesarleon$ ./adb shell flash_image recovery /sdcard/recovery-new.img
error reading /sdcard/recovery-new.img header: Is a directory
what's wrong ?
thank you people
Click to expand...
Click to collapse
Are u sure that recovery.img got transferred properly? Maybe check the rights on it (it not read only or something). What if you mount the sdcard in OS X and copy and paste (vs push)?

If you're trying to flash the recovery image, try
Code:
adb shell mount -a
adb push recovery-new.img /system/recovery.img
adb push recovery-new.img /sdcard/recovery-new.img
adb flash_image recovery /sdcard/recovery-new.img
Hope that helps

adb shell mount -a
Click to expand...
Click to collapse
didn´t work i think the parameter a is not correct
well this is almost the last step! thank you all for your explanations

cesardeluxe said:
hey i managed to apply the update thanks to having fastboot-mac on tools folder
but after booting i go to terminal to apply the final step and i get this
Code:
MBdeluxe:tools cesarleon$ ./adb shell flash_image recovery /sdcard/recovery-new.img
error reading /sdcard/recovery-new.img header: Is a directory
what's wrong ?
thank you people
Click to expand...
Click to collapse
Very odd error message
Do this to check what your phone's sdcard looks like
Code:
adb shell ls -l /sdcard/recovery-new.img
Next, you should grab the file from your phone to your computer. This step assume you are in your tools directory
Code:
adb pull /sdcard/recovery-new.img recovery-new-phone.img
Finally, try to compare the file you have on your computer against the one you got from your phone, and see if they are the same. This assume you have your working recovery-new.img in tools directory
Code:
diff recovery-new.img recovery-new-phone.img
I have not try this diff command, and I assume it'l handle binary diff
If diff can not handle binary file, do ls and check file size. both file should match
Code:
ls -l recovery-new.img recovery-new-phone.img
If your computer and phone recovery-new.img are not the same, download to phone again

cesardeluxe said:
didn´t work i think the parameter a is not correct
well this is almost the last step! thank you all for your explanations
Click to expand...
Click to collapse
You will get Failed Mounts when u run
Code:
adb shell mount -a
You CAN ignore them.
See here: http://forum.xda-developers.com/showthread.php?p=4029461

This may not be the right way to do it but I always just downloaded the recovery to the tools directory of the android sdk. Then fire up the phone in fastboot mode and do:
./fastboot flash recovery recovery-new.img
(replacing recovery-new.img with the name of the downloaded img file.)
I'm sure there is a reason people are doing it the other way, but for myself one command to do the flash is alot easier!

[How to] [Linux] Root Hboot 2.02

For anyone having issues with running this in linux.
I used zikronix guide and modified it for use in a linux support thread. The original thread can be found here:
http://forum.xda-developers.com/showthread.php?t=829045
This is my setup:
-I made sure to show my .bashrc profile and path to my tools folder if you needed help getting that setup as well... If not please ignore.
Code:
[email protected]:~$ cat .bashrc | grep adb
alias start-adb='sudo /usr/local/android-sdk/tools/./adb start-server'
alias kill-adb='sudo /usr/local/android-sdk/tools/./adb kill-server'
[email protected]:~$ cat .bashrc | grep android-sdk
export PATH="/usr/local/android-sdk/tools/:${PATH}"
[email protected]:~$ $PATH
bash: /usr/local/android-sdk/tools/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:
Download: http://www.wackynoodle.com/hboot202-s_off-V6.2.zip
Download (Mirror): http://sdx-downloads.com/EVO/devs/jerdog/fixes/hboot202-s_off-V6.2.zip
Now This might make things easier.
-I have this so that you are in the same enviroment that i was in so that the paths will be the same.
Code:
wget http://www.wackynoodle.com/hboot202-s_off-V6.2.zip
mkdir Evo-root
mv hboot202-s_off-V6.2.zip
cd Evo-root
unzip hboot202-s_off-V6.2.zip
- This step I just made sure that adb devices showed my device. If not get it working.
- Once adb devices showed my device properly, I simply ran the following commands.
Code:
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push root/flash_image /data/local/
adb push root/rageagainstthecage /data/local/tmp
adb push root/amon_ra.img /sdcard/
- Then this is just changing permissions. Pretty straight forward.
Code:
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage
chmod 0755 /data/local/flash_image
- Running the script. Should kick you out of adb... If not after 5 min kill the adb server and restart.
Code:
adb shell
./data/local/tmp/rageagainstthecage
- Now you should see a "#", if you do proceed. If not then run the script above again till it works.
Code:
adb shell
- If you saw that "#" run this. This can only be ran as root "#" means root.
Code:
./data/local/flash_image misc /sdcard/mtd-eng.img
Now you are going to want to reboot into the bootloader. Make sure once you do that you selet bootloader and let the PC36IMG.zip load.
Code:
reboot bootloader
After that is done reboot into the new rooted rom. Then make sure adb works again. Then run the following commands. Make sure you terminal is in the same directory this entire time there is no reason to leave the direcory we went into earlier "cd Evo-root" You directory should always be Evo-root. Thanks. The part that I found out was the second command where the entire recovery/ needed the permissions changed to be executable. As you saw in my post on that forum board.
- This will remove the PC36IMG.zip to a different name so that the bootloader won't get confused again. Then the second commands makes the directory executable recursivly. Then the third will reboot you into recovery.
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-ENG.zip
chmod -R +x recovery/
adb reboot recovery
- Now this is going to be done at the recovery screen. As long as you followed the steps above it will work fine. Should only take you about 20 mins to root this phone. Though it took me about 2 hours since no one else has been rooting using linux. I am thinking about writing a script that will root everything and alls you have to do is follow a terminal guide.... But ill see.
- Just run these commands that will allow you to flash the unrevoked-forever.zip. Once you follow the onscreen instructions of the unrevoked-forever.zip you will be able to reboot into the recovery and see the S-Off. Once that is done reboot into the rom, now we need to flash a custom recovery!
Code:
adb push recovery /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
- Again make sure your terminal was never closed and in the same folder. Then simply run these commands to flash the Amon_ra recovery. Since it has wimax capabilities I prefer it.
Code:
adb push root/flash_image /data/local/
adb shell
chmod 0755 /data/local/flash_image
./data/local/flash_image recovery /sdcard/amon_ra.img
reboot recovery
Now you should see the custom recovery and you should be able to flash any rom you desire!

reserved for later use

i see that they are same commands as the pc.., so would this also work with PC?

nickespi said:
i see that they are same commands as the pc.., so would this also work with PC?
Click to expand...
Click to collapse
I am guessing your talking about windows? Sure make sure adb is in your path. Though there are steps in here that are only for linux.

95% success
Well I want to thank you for this thread
It has worked for me I have root I have NAND unlocked
I can flash ROMs
The only issue I have is my radio/baseband and PRI version have been lowered
I have not been able to get thise back where they whould with either update or by using teh wimax.ADDRESS.tree.xml fix (there is no file with that)
If you have any ideas how to fix this would be much appreciated
I am unable to get higher tahn baseband 1.36.00.04.02 in ant rom
when I got teh phone it was 2.15.00.xx.xx
any help would be appreciated

100% Success
THANK YOU
My Evo
Hardware 004
Build 3.30
Hboot 2.02
Baseband 2.15.xx.xx
is now sucessfully rooted.
I did have some problems after being able to flash ROMs of not haveing PRI and Baseband updated.
On thread #787756 there are downloads that can be flashed to fix this problem if anyone else is in that boat.
zikronix sent me there for the fix...I believe he is adding it to the main thread but if it isn't there yet I wanted to add it now for anyone in my boat.
Again this method works and there is success.
Happy rooting

Hey thanx for this Linux guide. Does this steps work with the update 12.25.10 on the windows thread?
Will you update this guide?

[Q] error: more than one device and emulator???[SOLVED]

So i'm trying to root my asus transformer by following this guide http://forum.xda-developers.com/showthread.php?t=1106587
i got to the part where it says to type the following command
Code:
adb push gingerbreakBB /data/local/
but i get the error
Code:
C:\Android>adb push gingerbreakBB /data/local/
error: more than one device and emulator
I ran adb devices to see what devices it recognises and it says
Code:
C:\Android>adb devices
List of devices attached
304D197CC264A27E device
28841c943012497 device
what now

unplug one of your devices (maybe your phone?) or use
Code:
adb -s 304D197CC264A27E push gingerbreakBB /data/local/
you might have to swap the serial number, depending what you have plugged in.

thanks mate it seemed like it rooted but it didnt lol. i got the progress bar on when i rebooted the device but it doesnt seem to be rooted hhmmmm any ideas?

Sorry, not sure... maybe your phone is rooted instead :0
Try starting over again without your phone plugged in

if you are on linux or have access to a linux machien use this http://forum.xda-developers.com/showthread.php?t=1198303
Otherwise do this http://forum.xda-developers.com/showthread.php?t=1125714

gee one said:
Sorry, not sure... maybe your phone is rooted instead :0
Try starting over again without your phone plugged in
Click to expand...
Click to collapse
LOLOLOL you were right my phone was plugged in HOWEVER it still didnt work. the progress bar did show up again but wasnt rooted
mrevankyle said:
if you are on linux or have access to a linux machien use this http://forum.xda-developers.com/showthread.php?t=1198303
Otherwise do this http://forum.xda-developers.com/showthread.php?t=1125714
Click to expand...
Click to collapse
thanks i'll try that out later today. i think its sign for my to go to sleep its 3 am right now lolol. i'll post what happens today morning

Oh yeh going to sleep did the trick. I woke up and removed everything by doing the commands
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
and also followed the this video tutorial
http://www.youtube.com/watch?v=WaZ4B60OWmY&feature=player_embedded
aand it worked it!
Thanks gee one and mrevankyle

kassim3 said:
Oh yeh going to sleep did the trick. I woke up and removed everything by doing the commands
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
and also followed the this video tutorial
http://www.youtube.com/watch?v=WaZ4B60OWmY&feature=player_embedded
aand it worked it!
Thanks gee one and mrevankyle
Click to expand...
Click to collapse
also would like to add to anyone else encountering this error with other uses of adb to make sure all of bluestacks processes are killed.

I had the same issue when I've tried to room my XT1032 (Moto G)... I fail to install with the SuperBoot way! So I've decide to install CWM and a modified recovery.
On my first try, I receive this message:
Code:
error: more than one device and emulator
When I used the command
Code:
adb devices
I've 2 device... My XT1033 and an AndroidEmulator...
C:\Fastboot>adb devices
List of devices attached
emulator-5554 offline
TA88305ZDH offline
Click to expand...
Click to collapse
Also, the command
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
is not working for me...
I've use the command:
Code:
adb kill-server
After, I've plug back my XT1033 via USB and launch the command:
Code:
adb usb
Only my XT1033 is now show when I use the
Code:
adb devices
!
So, I've finish my installation with
Code:
fastboot-moto-windows flash recovery recovery.testkeys.img
and I've run a sideload installation with:
Code:
adb-windows sideload supersu.motog.zip
Try this and share me your opinion!
---------- Post added at 11:11 PM ---------- Previous post was at 11:10 PM ----------
I had the same issue when I've tried to room my XT1032 (Moto G)... I fail to install with the SuperBoot way! So I've decide to install CWM and a modified recovery.
On my first try, I receive this message:
Code:
error: more than one device and emulator
When I used the command
Code:
adb devices
I've 2 device... My XT1033 and an AndroidEmulator...
C:\Fastboot>adb devices
List of devices attached
emulator-5554 offline
TA88305ZDH offline
Click to expand...
Click to collapse
Also, the command
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
is not working for me...
I've use the command:
Code:
adb kill-server
After, I've plug back my XT1033 via USB and launch the command:
Code:
adb usb
Only my XT1033 is now show when I use the
Code:
adb devices
!
So, I've finish my installation with
Code:
fastboot-moto-windows flash recovery recovery.testkeys.img
and I've run a sideload installation with:
Code:
adb-windows sideload supersu.motog.zip
Try this and share me your opinion!

Rooting the Asus Eee Pad Slider??

Hi everyone! First off i want to say im pleased to be a new owner of this machine and im struggling to get some straight forward info on rooting/unlocking the device. i am struggling to get adb commands sent to my device and my windows 7 x86 machine will not pick it up after installing all the drivers and suite from asus site. I understand at this point that eveb the serial number is critical to identifying what device i have to clarify if i can root so with that i will give the basics here
Slider SL101
HTK75.US_epad-8.6.5.21_20111216
Honeycomb 3.2.1
serail starts with B90KA....
thanks everyone!

Sorry to ask this, but did you turn on USB debugging in the settings -> Development menu? If not then it won't be picked up.
If it still doesn't work you can try doing it in a virtualbox running linux or on linux, which is easier driver wise.

yes i did, but thank you for asking. Im now trying to do a root on my linux machine (Ubuntu 11.10) any guidance to this process would be greatly appreciated.

Linux ADB: (Extract the Tar-Gz, contains the adb drivers you need, no need for ASUS Sync) http://developer.android.com/sdk/index.html (shouldn't need for razorclaw)
Root:
Razorclaw: (All can be done on your TF, gotta downgrade firmware then use this to gain root) http://forum.xda-developers.com/showthread.php?t=1345049
Vipermod (Use Option-1 I think):
http://forum.xda-developers.com/showthread.php?t=1427125

Thing O Doom said:
Linux ADB: (Extract the Tar-Gz, contains the adb drivers you need, no need for ASUS Sync) http://developer.android.com/sdk/index.html (shouldn't need for razorclaw)
Root:
Razorclaw: (All can be done on your TF, gotta downgrade firmware then use this to gain root) http://forum.xda-developers.com/showthread.php?t=1345049
Vipermod (Use Option-1 I think):
http://forum.xda-developers.com/showthread.php?t=1427125
Click to expand...
Click to collapse
the vipermod link for linux will not work. how do i downgrade?

adb push nachoroot.bin /data/local/
adb shell chmod 777 /data/local/nachoroot.bin
adb shell /data/local/nachoroot.bin --stage1
adb reboot
<wait for boot>
adb shell /data/local/nachoroot.bin --stage2
adb reboot
<wait for boot>
adb shell id
<if id is 0 / root then continue, else start over>
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell /data/local/nachoroot.bin --undo
adb reboot
can i run these commands on terminal if im on .21? I wont brick right? I know the nacho root doest work for me. and vipermod is just a bunch of scipt to auto root right?

sorry for back-to-back -back responses. I type adb devices in terminal and get..
[email protected]:~/android/tools$ '/home/charlie/android/tools/adb' devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? no permissions
I cant see the slider??? Why

http://wiki.cyanogenmod.com/wiki/Udev <-- Did you do this when setting up ADB on your ubuntu? its easy to miss and important.

pperho Thn
Thing O Doom said:
http://wiki.cyanogenmod.com/wiki/Udev <-- Did you do this when setting up ADB on your ubuntu? its easy to miss and important.
Click to expand...
Click to collapse
Thanks so much man! That worked great!
Here is a helpful link along with yours, gave some more clarification.
http://www.joescat.com/linux/android_rules.html
Rock and Rooted!

[Q] How to unroot phone Atrix 2

I used the eacy one click to root phone. I would like to unroot it now. I am having touch screen freezing problem. I need to start removing applications to see which one is causing the problem or if it is a hardware issue or software.
I downloaded the zip file 1-click_exploit. I expanded the files and ran the application. I have read that there is an option to uninstall with in that file but I don't see one. Where do I find it. If I just do a factory reset will it remove it? If I do a reset do I have to repurchase all of my apps?
Thank you in advance!

A factory data reset will not remove root.
Also, a reset does not delete your purchases. They are all stored in your google account. So, if they do get deleted, just reinstall them.
As far as unrooting, I do not know. Someone else may chime in here...probably going to tell you to post in the Q&A section as well.

Doesn't the one-click have an un-root feature?
Sent from my bootloader-locked MB865.

The one click method also has an un root option in the folder.
Sent from my MB865 using xda app-developers app

Generally the only trace rooting leaves is a setuid binary "su" in /system/bin. And Superuser.apk to manage permission which apps get to invoke the binary. So unrooting involves uninstalling Superuser application and removing the su binary. If you want to do it by hand: (1) adb remount (2) adb shell (3) su (4) rm /system/bin/su

kousik said:
Generally the only trace rooting leaves is a setuid binary "su" in /system/bin. And Superuser.apk to manage permission which apps get to invoke the binary. So unrooting involves uninstalling Superuser application and removing the su binary. If you want to do it by hand: (1) adb remount (2) adb shell (3) su (4) rm /system/bin/su
Click to expand...
Click to collapse
I have no idea what the above manual steps are for. I can uninstall the application but where and how do I remove the su binary. On the phone? Please send directions for a non technical type of user.
Thank you!

MaTrixJ said:
The one click method also has an un root option in the folder.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Not sure where in the the following files in 1-click_exploit is the unroot option.I have attached a list of the files in the download.

bushbaum said:
Not sure where in the the following files in 1-click_exploit is the unroot option.I have attached a list of the files in the download.
Click to expand...
Click to collapse
Out of these files, adb.exe and .dll files are left in your windows PC. Not sure if they are deleted afterwards, if not, you can always unzip the above into a directory. You'll need the adb and the dll files.
The su and superuser.apk are two files that are pushed to your phone that provides the root functionality.
The zerg file is the exploit payload temporarily used to root your phone, and removed later by the script.
So if you have unzipped these into a directory, connect your phone via USB (make sure usb debugging is on), and run the commands
Code:
adb.exe remount
adb.exe shell
su // superuser may pop a permission request on phone screen
rm /system/bin/su
rm /system/app/Superuser.apk
exit

kousik said:
Out of these files, adb.exe and .dll files are left in your windows PC. Not sure if they are deleted afterwards, if not, you can always unzip the above into a directory. You'll need the adb and the dll files.
The su and superuser.apk are two files that are pushed to your phone that provides the root functionality.
The zerg file is the exploit payload temporarily used to root your phone, and removed later by the script.
So if you have unzipped these into a directory, connect your phone via USB (make sure usb debugging is on), and run the commands
Code:
adb.exe remount
adb.exe shell
su // superuser may pop a permission request on phone screen
rm /system/bin/wu
rm /system/app/Superuser.apk
exit
Click to expand...
Click to collapse
What mode is my usb connection? charge only? I have the phone setting usb setting on. I run the commands (using the run command in windows accessories). When I go run "adb.exe remount" the black command screen blinks on screen so then under I go to run again and entered "adb.exe shell" the run command screen opens up with [email protected]:/$ I put in "su" After I entered the command rm system/bin/wu I get a "read only error" how do I change from read only?
Sorry for all these questions but I warned you that I was not a technical user. Thanks

bushbaum said:
What mode is my usb connection? charge only? I have the phone setting usb setting on. I run the commands (using the run command in windows accessories). When I go run "adb.exe remount" the black command screen blinks on screen so then under I go to run again and entered "adb.exe shell" the run command screen opens up with [email protected]:/$ I put in "su" After I entered the command rm system/bin/wu I get a "read only error" how do I change from read only?
Sorry for all these questions but I warned you that I was not a technical user. Thanks
Click to expand...
Click to collapse
I was wondering do I have to have the elite version superuser installed to grant permission to system? I just have the free version.

bushbaum said:
What mode is my usb connection? charge only? I have the phone setting usb setting on. I run the commands (using the run command in windows accessories). When I go run "adb.exe remount" the black command screen blinks on screen so then under I go to run again and entered "adb.exe shell" the run command screen opens up with [email protected]:/$ I put in "su" After I entered the command rm system/bin/wu I get a "read only error" how do I change from read only?
Click to expand...
Click to collapse
1. yes -- charge only
2. it is better to open a command prompt -- in run commands type in "cmd" which'll give you a shell, easy to track command outputs
3. in that shell cd to the directory you unzipped and run "adb.exe remount"
4. Unless it says "remount succeeded" further operations won't succeed
5. After you execute "su" your prompt will change from $ to # ... is this happening?
6. Only on # prompt, you can do "rm /system/bin/su" ... that too only if remount succeeded
Let us know at which step it fails.

kousik said:
1. yes -- charge only
2. it is better to open a command prompt -- in run commands type in "cmd" which'll give you a shell, easy to track command outputs
3. in that shell cd to the directory you unzipped and run "adb.exe remount"
4. Unless it says "remount succeeded" further operations won't succeed
5. After you execute "su" your prompt will change from $ to # ... is this happening?
6. Only on # prompt, you can do "rm /system/bin/su" ... that too only if remount succeeded
Let us know at which step it fails.
Click to expand...
Click to collapse
I get the following error after entering the run "adb.exe remount"
*daemon not running starting it now*
*daemon started successfully*
remount failed: operation not permitted

bushbaum said:
I get the following error after entering the run "adb.exe remount"
*daemon not running starting it now*
*daemon started successfully*
remount failed: operation not permitted
Click to expand...
Click to collapse
Then try remounting manually:
Code:
C:\> adb.exe shell
edison$/ su
edison#/ mount -o remount,rw /dev/block/system /system
Afterwards proceed with rest of the script.