[Q] error: more than one device and emulator???[SOLVED] - Eee Pad Transformer Q&A, Help & Troubleshooting

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!

Related

[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] UCLA3 NANDRoid to flashable zip

I successfully received the OTA update, and was wondering if anyone wanted/needed a rooted nandroid.
I tried to do the requisite search before posting, (did not find a clear answer) - I'd love to make a CWM zip, but don't know how, but am in the midst of looking for the answer. Might try kitchen...
If I missed someone else's effort to do the same, kindly disregard.
Let me know, I'll get it up tonight. This is 2.3.6 and DOES NOT have CIQ.
hey can u dump the modem for me
I've got adb and kitchen setup on PC, but really have not tried to dabble until now. Got a reference for the modem dump that I can follow? If not I'll look how to do just the modem. Flashed radios via adb but never saved one from a device.
yes....turn on usb debugging in development. connect to your pc.....open cmd prompt.....navigate to the directory that has adb in it
---------- Post added at 10:17 PM ---------- Previous post was at 10:14 PM ----------
run these commands
adb shell dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin
adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm.bin
Thanks guys for doing this. Will there be two zip files: one for the UCLA3 baseband (radio) and one for GINGERBREAD.UCLA3 build? Or can they be combined into one flashable zip?
Sent from my SAMSUNG-SGH-I727 using XDA App
silver03wrx said:
yes....turn on usb debugging in development. connect to your pc.....open cmd prompt.....navigate to the directory that has adb in it
---------- Post added at 10:17 PM ---------- Previous post was at 10:14 PM ----------
run these commands
adb shell dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin
adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm.bin
Click to expand...
Click to collapse
I got a permission denied error, please see attached screenshot
opss lol sorry start over
type adb shell hit enter
type su hit enter
then run those commands
silver03wrx said:
opss lol sorry start over
type adb shell hit enter
type su hit enter
then run those commands
Click to expand...
Click to collapse
hmm, denied again, sreenshot attached
sob.. lol ok.
adb shell hit enter
su hit enter
then
mount -o remount,rw /dev/block/stl9 /system
then those commands
silver03wrx said:
sob.. lol ok.
adb shell hit enter
su hit enter
then
mount -o remount,rw /dev/block/stl9 /system
then those commands
Click to expand...
Click to collapse
Grrr, I'll keep trying. after entering "su" it seems to be thinking for about a min.
attached
superfire71 said:
Grrr, I'll keep trying. after entering "su" it seems to be thinking for about a min.
attached
Click to expand...
Click to collapse
if your phone is rooted, then make sure that on screen you allow SU permissions after typing su in the cmd prompt
unplug phone
plug back in
close the terminal..
reopen it
get to adb directory
adb start service
adb shell
su
Pirateghost said:
if your phone is rooted, then make sure that on screen you allow SU permissions after typing su in the cmd prompt
Click to expand...
Click to collapse
k, trying again, brb
lol dificult with out phone in hand
much closer, see attached. Now says "not found" when entering original commands. never mind the nonsense entered at the bottom
I did have to allow on phone screen when entering su, missed that originally
ok close the terminal
re open it
unplug phone
plug back in
adb start service
adb shell
su
dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin
dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm.bin
adb pull /sdcard/amss.bin
adb pull /sdcard/mdm.bin
superfire71 said:
much closer, see attached. Now says "not found" when entering original commands. never mind the nonsense entered at the bottom
I did have to allow on phone screen when entering su, missed that originally
Click to expand...
Click to collapse
once you are already IN adb shell, you dont enter the command adb shell...lol
adb shell
su
dd command
silver03wrx said:
ok close the terminal
re open it
unplug phone
plug back in
adb start service
adb shell
su
adb shell dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin
adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm.bin
adb pull /sdcard/amss.bin
adb pull /sdcard/mdm.bin
Click to expand...
Click to collapse
silver,
when IN adb shell, adb shell is bad command. just start it at dd
Pirateghost said:
once you are already IN adb shell, you dont enter the command adb shell...lol
adb shell
su
dd command
Click to expand...
Click to collapse
thank you sir
Ok guys, really close. see attached, setting up to do it again.
check your sd card
---------- Post added at 11:07 PM ---------- Previous post was at 11:07 PM ----------
i dont think you need to do adb pull for them after the first 2 commands
is that right pg?

[Q] Using ADB from Terminal Emulator

I recently received my Transformer back after RMA-ing it for a non functioning screen. Of course, even though the problem lied with the hardware, they still unrooted and reinstalled stock firmware on it. Everything on it works, except for the USB cable that seems to be either not working, or because they installed all my apps and settings back on the tablet, something's wrong. This is a problem when it comes to rooting it again. What I'm trying to do is run the commands through the Terminal Emulator, but here is what happens:
Code:
[email protected]: /sdcard $ adb start-server
* Daemon not running, starting it on port 5038 *
* Daemon started successfully *
[email protected]: /sdcard $ adb connect localhost:5038
connected to localhost:5038
[email protected]: /sdcard $ adb push su /data/local/tmp
error: device not found
So my question is, is it even possible to do this? If not, is there another way to do it?
Thanks in advanced for any help!
adb is the android debugging bridge what it does is changes your shell from your computer to your device so you do not need to run anything that refers to adb from your device
Hmm, run Wolf's exploit but remove 'adb' from all the commands, pretend you're already in the shell. (Because you are)
Thing O Doom said:
Hmm, run Wolf's exploit but remove 'adb' from all the commands, pretend you're already in the shell. (Because you are)
Click to expand...
Click to collapse
Yeah, I've tried that too.
Code:
/system/bin/sh: push: not found
aldude999 said:
Yeah, I've tried that too.
Code:
/system/bin/sh: push: not found
Click to expand...
Click to collapse
push is an adb command not a terminal command
mrevankyle said:
push is an adb command not a terminal command
Click to expand...
Click to collapse
I understand that.
I've been trying mv with no luck:
Code:
mv /sdcard/su /data/local/tmp
failed on '/sdcard/su' - Cross-device link
Download a Recovery.zip you want, and then extract the file called 'recoveryblob' out of it. (I highly recommend Rouge XM touch)
Place it on the root of your internal storage /sdcard/.
Run this:
Code:
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
reboot the tab, get back in, run this:
Code:
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot again, then you see a blue bar if it worked.
Then you can access CWM recovery that you just flashed with dd, and use that to install the Superuser or SuperSU .zip
Thing O Doom said:
Download a Recovery.zip you want, and then extract the file called 'recoveryblob' out of it. (I highly recommend Rouge XM touch)
Place it on the root of your internal storage /sdcard/.
Run this:
Code:
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
reboot the tab, get back in, run this:
Code:
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot again, then you see a blue bar if it worked.
Then you can access CWM recovery that you just flashed with dd, and use that to install the Superuser or SuperSU .zip
Click to expand...
Click to collapse
Code:
mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - Permission denied
EDIT: Also, I've tried chmod, and I get an Operation not permitted error.
This is a TF101 correct? What stock firmware is it running?
You need to get USB working again.
Thing O Doom said:
This is a TF101 correct? What stock firmware is it running?
You need to get USB working again.
Click to expand...
Click to collapse
Yes It's running completely up to date (unfortunately) 9.2.1.24.
aldude999 said:
Yeah, I've tried that too.
Code:
/system/bin/sh: push: not found
Click to expand...
Click to collapse
It might help to understand what is going on. In this case, adb push su /data/tmp becomes "cp su /data/tmp/" if you are running from the terminal. You'll need stronger linux-fu.
You might also need a few extra /'s at the end of *some* of your commands.
sent from my transformer
gee one said:
It might help to understand what is going on. In this case, adb push su /data/tmp becomes "cp su /data/tmp/" if you are running from the terminal. You'll need stronger linux-fu.
You might also need a few extra /'s at the end of *some* of your commands.
sent from my transformer
Click to expand...
Click to collapse
Yeah, I gotcha, but the only command I have that comes close to cp is mv, and all the commands are very strictly limited.

ADB

Hello, I have a problem. I'm trying to do some things from my pc in the phone with the ADB Shell and not let me.
My problem is that I put adb: not found.
I do this:
img204.imageshack.us/img204/1832/adbshell.jpg
Worth up here all right but when I have root permissions and everything working I put the commands and none let me get adb remount such or adb pull and nothing makes me adb: not found.
Thank you.
Xele said:
Hello, I have a problem. I'm trying to do some things from my pc in the phone with the ADB Shell and not let me.
My problem is that I put adb: not found.
I do this:
img204.imageshack.us/img204/1832/adbshell.jpg
Worth up here all right but when I have root permissions and everything working I put the commands and none let me get adb remount such or adb pull and nothing makes me adb: not found.
Thank you.
Click to expand...
Click to collapse
if everything is installed correctly then just make sure you are in the platform-tools dierectory eg.
c:\android-sdk\platform-tools\
yes, all is succesfully installed. I started adb shell with cmd of directory platform-tools\adb but when I put code adb remount or other command I appear me adb: not found
AlOpen task manager and see if any adb process is running. If there are kill them and try again :
Also verify that adb. .exe is in the platform -tools folder. Actually it might be in the tools folder if so try running adb from there...
Sent from my Nexus One using xda premium
Xele said:
yes, all is succesfully installed. I started adb shell with cmd of directory platform-tools\adb but when I put code adb remount or other command I appear me adb: not found
Click to expand...
Click to collapse
That's not the way to use adb, so you're not following the guide you're reading correctly.
Usually the guide won't tell you to go to the shell directly, but instead typing something like: adb shell mount -o rw,remount ...
Once you type adb shell you're INSIDE the shell you don't need to call the debugger (adb) anymore...
You shouldn't follow guides without reading them completely and fully understanding them before trying anything.
And by the way you opened two threads with the same question.
Xele said:
Hello, I have a problem. I'm trying to do some things from my pc in the phone with the ADB Shell and not let me.
My problem is that I put adb: not found.
I do this:
img204.imageshack.us/img204/1832/adbshell.jpg
Worth up here all right but when I have root permissions and everything working I put the commands and none let me get adb remount such or adb pull and nothing makes me adb: not found.
Thank you.
Click to expand...
Click to collapse
This is your second warning about creating multiple threads on the same topic. The next incident will result in infractions being issued. Thread closed.

HTC One X Root Assistance

Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
blinkbomber said:
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
Click to expand...
Click to collapse
check pm
beaups said:
check pm
Click to expand...
Click to collapse
Could you help me too X( ? I got my HOX last night at 8pm; I traded my rooted S2 Skyrocket for it.
Been looking for the past day through forums and google. It's so different from Samsung's phones, but a nice change indeed.
I'm on 1.85 and tried those two methods also. I'm not very familiar with ADB. From reading all night and this morning, I believe I root, unlock bootloader, flash recovery, flash custom roms?
smartnphone said:
Could you help me too X( ? I got my HOX last night at 8pm; I traded my rooted S2 Skyrocket for it.
Been looking for the past day through forums and google. It's so different from Samsung's phones, but a nice change indeed.
I'm on 1.85 and tried those two methods also. I'm not very familiar with ADB. From reading all night and this morning, I believe I root, unlock bootloader, flash recovery, flash custom roms?
Click to expand...
Click to collapse
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium
abhipati said:
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks. I used this for ADB http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
I remember using it for my S2, but I don't quite understand the directions for the http://forum.xda-developers.com/showthread.php?t=1709296 method. Could you dumb it down for this HOX noob?
smartnphone said:
Thanks. I used this for ADB http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
I remember using it for my S2, but I don't quite understand the directions for the http://forum.xda-developers.com/showthread.php?t=1709296 method. Could you dumb it down for this HOX noob?
Click to expand...
Click to collapse
I'll try to help! all of the following is my interpretation of the rooting method described here: http://forum.xda-developers.com/showthread.php?t=1709296
What you need:
HOX on ATT 1.85
su binary from http://dl.dropbox.com/u/don'tusemeimabadsubinary
EDIT: The su binary above has issues. Use this one instead: http://dl.dropbox.com/u/9060692/su
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Download correct su file (assuming you don't have a problem with this step )
Put su in same directory as ADB. Get to adb command prompt and cd into that directory
Quote from Butters619: cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
NEW - pull sim card
NEW - do factory reset
NEW - when reset is complete, do not replace sim, do NOT connect to wifi. Go through setup, go to settings, enable USB debugging. When that's done:
Enter these commands in adb:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
(If you get file doesn't exist after the FIRST command don't worry - they may not be there)
Now, on the phone, go to settings and check for software update. It will tell you you need to connect to network. Now, replace the SIM OR connect to wifi. Have it check for software update again. When it's done, do NOT click "yes" or "ok" on the phone. Simply:
Enter these commands in adb:
adb shell ls -l /data/local.prop
IF AND ONLY IF you get "file not exists" or anything like that then set your phone's date 2 days ahead and reboot the phone and start over. If you get file info, you're golden. Proceed...
Enter these commands into adb:
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Reboot via adb by entering this command: adb reboot
After phones reboots
Enter these commands in adb:
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 rm /data/local.prop
adb reboot
You should be rooted.
A cool username said:
I'll try to help! all of the following is my interpretation of the rooting method described here: http://forum.xda-developers.com/showthread.php?t=1709296
What you need:
HOX on ATT 1.85
su binary from http://dl.dropbox.com/u/don'tusemeimabadsubinary
EDIT: The su binary above has issues. Use this one instead: http://dl.dropbox.com/u/9060692/su
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Download correct su file (assuming you don't have a problem with this step )
Put su in same directory as ADB. Get to adb command prompt and cd into that directory
Quote from Butters619: cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
NEW - pull sim card
NEW - do factory reset
NEW - when reset is complete, do not replace sim, do NOT connect to wifi. Go through setup, go to settings, enable USB debugging. When that's done:
Enter these commands in adb:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
(If you get file doesn't exist after the FIRST command don't worry - they may not be there)
Now, on the phone, go to settings and check for software update. It will tell you you need to connect to network. Now, replace the SIM OR connect to wifi. Have it check for software update again. When it's done, do NOT click "yes" or "ok" on the phone. Simply:
Enter these commands in adb:
adb shell ls -l /data/local.prop
IF AND ONLY IF you get "file not exists" or anything like that then set your phone's date 2 days ahead and reboot the phone and start over. If you get file info, you're golden. Proceed...
Enter these commands into adb:
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Reboot via adb by entering this command: adb reboot
After phones reboots
Enter these commands in adb:
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 rm /data/local.prop
adb reboot
You should be rooted.
Click to expand...
Click to collapse
Thanks. Yeah i've been trying it alld ay but it can't find where my SU is. it's in the same location as the ADB stuff i believe C:\android-sdk-windows. Seem like some of the senior members are willing to go through teamviewer to help the ones who can't do it. I'll try asking them :/
Sorry I couldn't be of any help, but please let me know if/how you get this to work just in case this happens to me when I get my one x.
Sent from my Touch Pro 2 using xda app-developers app
---------- Post added at 08:22 PM ---------- Previous post was at 08:18 PM ----------
blinkbomber said:
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
Click to expand...
Click to collapse
I wonder if the one who actually started this thread got his/her phone to work...???
Sent from my Touch Pro 2 using xda app-developers app
Someone think they can help me root the phone? I'm on 1.85 and I believe I finally got adb to recognize my device but after that I don't think I'm doing it right
Sent from my SGH-I777 using XDA Premium App

Categories

Resources