Related
Too many threads... too many sites and PC options.
Here's my situation:
Droid X
Used the leak update... running 2.2 now.
Use a MAC. And have Terminal app on DX.
Have SBF file for 2.1 stock, have ZIP files of rooted 2.2's
Dont have custom recovery.
Dont care much about warranty or OTA... just want to be able to apply ZIPs.
I need to somehow either root my DX with Mac or Terminal app. Or flash the SBF to bring things back to 2.1.
Not sure what to do??? Please please help.
I am not familiar with terminal commands...so if you leave instructions that would be great.
-Roman
You follow the same ADB commands, more or less. Why not try something like Universal AndRoot though? Then you could just skip over it.
But, if you need to sbf, I would *think* you follow the Linux instructions.
1) download sbf_flash & sbf file
Code:
cd directory/where/these/are/located
./sbf_flash SBFfileLOCATION
The only way to SBF is to run windows through bootcamp or this http://www.droidforums.net/forum/droid-hacks/38671-flashing-sbf-mac.html . I am in the same boat as you luckily my girlfriend has a dell running Windows. You should also be able to root 2.2 using the Droid 2 method posted in this section http://forum.xda-developers.com/showthread.php?t=766767. I assume you have the SDK downloaded already? The Linux directions does not work for Mac.
x.v_ said:
You follow the same ADB commands, more or less. Why not try something like Universal AndRoot though? Then you could just skip over it.
I TRIED THAT, BUT THERE IS SOME ERROR THAT POPS UP... CAN'T DO IT. 2.2 ISN'T SUPPORTED... I THINK IT'S JUST FOR 2.1..
But, if you need to sbf, I would *think* you follow the Linux instructions.
1) download sbf_flash & sbf file
Code:
cd directory/where/these/are/located
./sbf_flash SBFfileLOCATION
Click to expand...
Click to collapse
SO THAT EASY? JUST TWO COMMAND LINES?
So, if I put the SBF on my desktop it would be:
cd desktop (enter)
./sbf_flash fullSBFfilename.sbf (enter)
???????
romanvail said:
SO THAT EASY? JUST TWO COMMAND LINES?
So, if I put the SBF on my desktop it would be:
cd desktop (enter)
./sbf_flash fullSBFfilename.sbf (enter)
???????
Click to expand...
Click to collapse
Running ADB with Mac OSX and therefore rooting with the mac is EASY. Just make sure you have the Android SDK installed on your Mac. Make sure in your .bash_profile you have the path set to the tools directory of your SDK folder.
Since I can't tell if you have all this down, I'll give you the instructions on setting up adb on the mac (using terminal), then give you the directions I followed on rooting my Droid X from OSX (I am running 2.2 leaked).
Essentially follow these instructions (taken from tjrocks91 on droidforum... I'd link, but I am not yet allowed to post outside links on this forum):
1. Download the Android SDK for Mac OSX. (google it)
2. Extract the zip file to any destination on your Mac. *Remember its path!*
In the AndroidSDK folder, there will be a folder named “tools”. We will be adding this folder to the path on Mac OSX. For this example, extract to your home folder (the folder that contains the desktop, documents, etc. folders)
3. To do this click on Finder > Go > Utilities > Terminal.
4. Type in without quotations “cd ~/”
5. Next, type "touch .bash_profile" to create your new bash or otherwise known path file.
6. Next, type "open -e .bash_profile" to open it in TextEdit. A TextEdit window will open, copy and past this into that window, substituting <username> for your username on OSX:
export PATH=${PATH}:/Users/<username>/AndroidSDK/tools
7. Save the file and close the window.
8. Repeat steps 5 through 7, but replace .bash_profile with ".bashrc" (without the quotes)
9. ADB should be ready to go. Make sure that your Droid X is set to "charge only" when connected via USB, and that you have debug mode set to on in your Android settings (settings>applications>development> USB Debugging)
10. In terminal, type (without the quotes): "adb devices". You should see a return that gives a list of devices attached. If the daemon wasn't started yet, this will do it. After that, type "adb shell" to enter adb.
11. After that, the adb commands are ALL the same on any platform, just make adjustments for different file systems when moving things TO your phone when using the command prompt (and not in the adb shell itself, but using adb commands). OSX follows unix/linux file structure, but not always the linux/unix file arrangement (but pretty darn close, since it is a Unix BSD GUI).
Now onto rooting your DX running 2.2. I've attached the file I used. It is a .rar files, so you will need a .rar extractor. I found a nice free one on the net called UnrarX. Google it, get it. Its free, it works. I will give instructions assuming you have them. These instructions come from karnovaran here on XDA. THey are for the droid 2, but work for the Droid X as well. i will translate them into instructions that can be followed verbatim on Mac (as the instructions he gave are meant for those doing this through the command prompt in windows).
1. Extract the contents of the attached file to your sdk tools folder
2. Open a terminal window and navigate to your sdk tools folder. if you put the sdk folder in your home folder, then the command and path you should enter from the terminal should be something like this:
cd AndroidSDK/tools
3. Now the process is as follows (follow EXACTLY, making sure you are faithful to YOUR file paths). I'm copying almost verbatim from karnovaran:
- adb devices (to verify the connection)
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (this WILL take a while, so don't TOUCH ANYTHING on your phone. Just go grab a beer and relax until the proces kicks you back out to the tools folder in terminal)
- adb kill-server
- cd <wherever-your-sdk-tools-folder-is>
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
- exit
This got me root on my DX and I did this on OSX no problem. The only PC I have that is functional is my laptop for work and because of the content on it and security procedures, though I could do android hacking with it, I will not, so I'm stuck with using my Mac. Thing is that it really is NOT hard. Commands are almost exactly as in Linux/Unix, and OSX terminal runs bash, which is quite versatile (more commands than busybox, iirc) in and of itself. And getting mac root access is bloody easy using sudo if you need it (otherwise, don't use it).
I hope this helps. Have fun.
many steps.... but will go slowly.
Thank you!!!!
Many steps, but they work!
SirBrass said:
Running ADB with Mac OSX and therefore rooting with the mac is EASY. Just make sure you have the Android SDK installed on your Mac. Make sure in your .bash_profile you have the path set to the tools directory of your SDK folder.
Since I can't tell if you have all this down, I'll give you the instructions on setting up adb on the mac (using terminal), then give you the directions I followed on rooting my Droid X from OSX (I am running 2.2 leaked).
Essentially follow these instructions (taken from tjrocks91 on droidforum... I'd link, but I am not yet allowed to post outside links on this forum):
1. Download the Android SDK for Mac OSX. (google it)
2. Extract the zip file to any destination on your Mac. *Remember its path!*
In the AndroidSDK folder, there will be a folder named “tools”. We will be adding this folder to the path on Mac OSX. For this example, extract to your home folder (the folder that contains the desktop, documents, etc. folders)
3. To do this click on Finder > Go > Utilities > Terminal.
4. Type in without quotations “cd ~/”
5. Next, type "touch .bash_profile" to create your new bash or otherwise known path file.
6. Next, type "open -e .bash_profile" to open it in TextEdit. A TextEdit window will open, copy and past this into that window, substituting <username> for your username on OSX:
export PATH=${PATH}:/Users/<username>/AndroidSDK/tools
7. Save the file and close the window.
8. Repeat steps 5 through 7, but replace .bash_profile with ".bashrc" (without the quotes)
9. ADB should be ready to go. Make sure that your Droid X is set to "charge only" when connected via USB, and that you have debug mode set to on in your Android settings (settings>applications>development> USB Debugging)
10. In terminal, type (without the quotes): "adb devices". You should see a return that gives a list of devices attached. If the daemon wasn't started yet, this will do it. After that, type "adb shell" to enter adb.
Last login: Tue Sep 14 09:12:34 on console
Roman-Vails-Computer:~ romanvail$ cd ~/
Roman-Vails-Computer:~ romanvail$ touch .bash_profile
Roman-Vails-Computer:~ romanvail$ open -e .bash_profile
Roman-Vails-Computer:~ romanvail$ touch .bashrc
Roman-Vails-Computer:~ romanvail$ open -e .bashrc
Roman-Vails-Computer:~ romanvail$ adb devices
-bash: adb: command not found
Roman-Vails-Computer:~ romanvail$
*****DOESNT WORK FOR ME*****
Click to expand...
Click to collapse
Do you have the path to adb set properly?
Sent from my DROIDX using XDA App
SirBrass said:
Do you have the path to adb set properly?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Yeah this would be your problem.
@OP,
yes, it would be just that easy IF AND ONLY IF the linux commands apply to macs as well. Which I have NO IDEA on. so proceed at your own risk :z
i finally figured it out... saw another post....
here's what worked:
./
Here's my log in case anyone else needs is:
Roman-Vails-Computer:~ romanvail$ adb
-bash: adb: command not found
Roman-Vails-Computer:~ romanvail$ cd/Users/romanvail/android-sdk-mac_x86/tools -bash: cd/Users/romanvail/android-sdk-mac_x86/tools: No such file or directory
Roman-Vails-Computer:~ romanvail$ cd /Users/romanvail/android-sdk-mac_x86/tools Roman-Vails-Computer:tools romanvail$ ./adb
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
Roman-Vails-Computer:tools romanvail$ adb devices
-bash: adb: command not found
Roman-Vails-Computer:tools romanvail$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015D61C60A003017 device
Roman-Vails-Computer:tools romanvail$ ./adb push Superuser.apk /sdcard/Superuser.apk
1059 KB/s (27688 bytes in 0.025s)
Roman-Vails-Computer:tools romanvail$ ./adb push su /sdcard/su
1802 KB/s (26248 bytes in 0.014s)
Roman-Vails-Computer:tools romanvail$ ./adb push busybox /sdcard/busybox
1918 KB/s (1926944 bytes in 0.980s)
Roman-Vails-Computer:tools romanvail$ ./adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
726 KB/s (5392 bytes in 0.007s)
Roman-Vails-Computer:tools romanvail$ ./adb shell
$ cd data/local/tmp
$ chmod 0755 rageagainstthecage-arm5.bin
$ ./rageagainstthecage-arm5.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3815, 3815}
[*] Searching for adb ...
[+] Found adb as PID 2846
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] 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.
$ Roman-Vails-Computer:tools romanvail$ ./adb kill-server
Roman-Vails-Computer:tools romanvail$ ./adb kill-server
* server not running *
Roman-Vails-Computer:tools romanvail$ cd /Users/romanvail/android-sdk-mac_x86/tools
Roman-Vails-Computer:tools romanvail$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXXXXXXXXXXXXX device
Roman-Vails-Computer:tools romanvail$ ./adb shell
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# cp /sdcard/busybox /system/bin/busybox
# chmod 4755 /system/bin/su
# chmod 4755 /system/bin/busybox
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# exit
Roman-Vails-Computer:tools romanvail$ exit
logout
[Process completed]
Now that's odd. I only get problems when I try and use ./ just regular "adb" works on my machine.
SirBrass said:
Now that's odd. I only get problems when I try and use ./ just regular "adb" works on my machine.
Click to expand...
Click to collapse
Yea pretty weird... I use OSX 10.5.8
Intel machine... so, it's weird, but IT DID WORK.
romanvail said:
Yea pretty weird... I use OSX 10.5.8
Intel machine... so, it's weird, but IT DID WORK.
Click to expand...
Click to collapse
There's your problem.... you're using leopard . I'm using 10.6.3. Love it. They did well with this new OS version (for those who don't know... the difference to users between Leopard and Snow Leopard for OSX folks is like the diff between Eclair and FroYo... the former is good, but the later far exceeds it under the hood though still remaining almost the same on the front end).
And obviously that means I'm running an intel machine as well. 2008 iMac 20".... 2.66 Ghz Core 2 Duo. Just your regular, nothing-special iMac.
I thought Macs were supposed to be user friendly?
*snicker*
Sent from my DROIDX using XDA App
Will this method work for a Droid X on Android 2.3.4 Gingerbread and with build # 4.5.1_57_DX8-51 Also is there a new one click type solution by now on a Mac?
Let`s start from beginning...
First download attached file New kernell install.7z and unpack it on your desktop.
Then go to ADB install procedure...
Open Terminal and you will see something like this...
HINT:
The best way to install is to run on Root Terminal. This is placed on Applications -> System Tools.
On Ubuntu it is invisible by default and you must to enable it on System -> Preferences -> Main menu and make it visible.
That`t it... lets go to work...
Open terminal and you will see this...
[email protected]_name:~$
Then type this in your Terminal window. Only BOLD text must be typed... Don`t forget to press ENTER after type the command in Terminal.
And don`t forget to type your root password after sudo command.
[email protected]_name:~$ cd Desktop
[email protected]_name:~/Desktop$ cd ADB_install
[email protected]_name:~/Desktop/ADB_install$ sudo cp adb /usr/bin
[email protected]_name:~/Desktop/ADB_install$ sudo chmod +x /usr/bin/adb
Don`t forget that USB Debugging MUST be enabled on your phone !!!
Connect your phone via USB cable and type this...
[email protected]_name:~$ adb devices
After that you can see that is your device properly connected to your computer and will see this...
List of devices attached
0123456789ABCDEF device
Close Terminal window.
Now, the ADB is finished to install on your linux OS and your phone is visible on computer.
Now we can go to update kernel...
Download kernel as you wish. I`m usin a MDJ kernel but if you can, you may use any other kernel.
Create new folder on your desktop and place all files from archive into this folder.
Rename folder to some simple name. In my case this folder is named newkernel
In MDJ kernel files is this...
zImage
bcm4329.ko
tun.ko
cifs.ko
fuse.ko
msm_rmnet.ko
nls_utf8.ko
Copy attached install_kernel.sh script and place it into the newkernel folder.
After that, all kernel files, modules and install_kernel.sh script must be in root of newkernel folder.
Open Terminal window and see something like this...
[email protected]_name:~$
Type...
[email protected]_name:~$ cd Desktop
[email protected]_name:~/Desktop$ cd newkernel
[email protected]_name:~/Desktop/newkernel$ sh install_kernel.sh
After finish and after see All Done!!! massage, you must to reboot yor phone and your new kernel is up.
Or just type in existing Terminal window...
[email protected]_name:~$ adb reboot
Enyoy !!!
FileFixer.
Hello I have a question. Is it possible to do this from teminal inside Android and after installing the new kernel to reboot? Thanks.
Sticky please
very usefull should be a sticky!
ogoglass said:
Hello I have a question. Is it possible to do this from teminal inside Android and after installing the new kernel to reboot? Thanks.
Click to expand...
Click to collapse
You need to mount and remoun your boot.img from NAND to SD card. Yaffs2 must be installed on android but i have not found anywher yaffs2 for ARM processor.
Maybe some other want to help with this. Rework the sh cript is not a major problem.
ADB was installed correctly... but the installation kernel not work for me:
~$ cd Desktop
~/Desktop$ cd newkernel
~/Desktop/newkernel$ sh install_kernel.sh
install_kernel.sh: 1: @echo: not found
Creating directory and mounting /boot...
mkdir failed for /data/boot, File exists
Pushing zImage...
1427 KB/s (2401156 bytes in 1.642s)
Remounting system and pushing modules...
remount succeeded
310 KB/s (272851 bytes in 0.857s)
1459 KB/s (185916 bytes in 0.124s)
failed to copy 'cifs.ko' to '/system/lib/modules/cifs.ko': No space left on device
1579 KB/s (635894 bytes in 0.393s)
1294 KB/s (120735 bytes in 0.091s)
619 KB/s (28764 bytes in 0.045s)
Cleaning up...
rmdir failed for /data/boot, Directory not empty
All done!
~/Desktop/newkernel$
FileFixer said:
You need to mount and remoun your boot.img from NAND to SD card. Yaffs2 must be installed on android but i have not found anywher yaffs2 for ARM processor.
Maybe some other want to help with this. Rework the sh cript is not a major problem.
Click to expand...
Click to collapse
mkyaffs2image command comes on most builds of android that are rooted
really cannot understand, please, advise for noob:
is this manual for Linux OS PC or Windows PC?
which exact Terminal you mean?
Excellent Job! Sticky for noobs!
dimdimdim said:
really cannot understand, please, advise for noob:
is this manual for Linux OS PC or Windows PC?
Click to expand...
Click to collapse
primarily for Linux,
I have run it under OSX
but ADB can run under everything.
internauta2000 said:
ADB was installed correctly... but the installation kernel not work for me:
~$ cd Desktop
~/Desktop$ cd newkernel
~/Desktop/newkernel$ sh install_kernel.sh
install_kernel.sh: 1: @echo: not found
Creating directory and mounting /boot...
mkdir failed for /data/boot, File exists
Pushing zImage...
1427 KB/s (2401156 bytes in 1.642s)
Remounting system and pushing modules...
remount succeeded
310 KB/s (272851 bytes in 0.857s)
1459 KB/s (185916 bytes in 0.124s)
failed to copy 'cifs.ko' to '/system/lib/modules/cifs.ko': No space left on device
1579 KB/s (635894 bytes in 0.393s)
1294 KB/s (120735 bytes in 0.091s)
619 KB/s (28764 bytes in 0.045s)
Cleaning up...
rmdir failed for /data/boot, Directory not empty
All done!
~/Desktop/newkernel$
Click to expand...
Click to collapse
This is correct on my PC...
~/Desktop/newkernel$ sh install_kernel.sh
install_kernel.sh: 1: @echo: not found
Creating directory and mounting /boot...
Pushing zImage...
1994 KB/s (2401156 bytes in 1.175s)
Remounting system and pushing modules...
remount succeeded
1809 KB/s (272851 bytes in 0.147s)
1775 KB/s (185916 bytes in 0.102s)
1951 KB/s (3056268 bytes in 1.529s)
1964 KB/s (635894 bytes in 0.316s)
1643 KB/s (120735 bytes in 0.071s)
663 KB/s (28764 bytes in 0.042s)
Cleaning up...
All done!
Do you have a rooted phone or you not have more free space on your phone?
Look at this line when start sh script...
mkdir failed for /data/boot, File exists
and this...
failed to copy 'cifs.ko' to '/system/lib/modules/cifs.ko': No space left on device
g30rg10u said:
primarily for Linux,
I have run it under OSX
but ADB can run under everything.
Click to expand...
Click to collapse
which are requirements for adb and how to run if I already have on my windows7 android sdk?
g30rg10u said:
primarily for Linux,
I have run it under OSX
but ADB can run under everything.
Click to expand...
Click to collapse
actually, adb.exe's window I'm trying to run under platform-tools disappears after a second.
what's my problem? (besides "invalid user", of course)
Ok...
The build is Gauner HD-FI 0.3 and understand that is routed by default ... Correct me if not...
With respect to free space on the phone, is a TMUS with 1024 Mb in ROM... shown that limited ... I do not know because it shows to have 431 Mb free...
This is what marks my last attempt:
...
install.sh: 1: @echo: not found
Creating directory and mounting /boot...
mkdir failed for /data/boot, File exists
Pushing zImage...
1653 KB/s (1708764 bytes in 1.009s)
Remounting system and pushing modules...
remount succeeded
1508 KB/s (272303 bytes in 0.176s)
1404 KB/s (184956 bytes in 0.128s)
failed to copy 'cifs.ko' to '/system/lib/modules/cifs.ko': No space left on device
1577 KB/s (633598 bytes in 0.392s)
1312 KB/s (117451 bytes in 0.087s)
654 KB/s (27800 bytes in 0.041s)
Cleaning up...
rmdir failed for /data/boot, Directory not empty
All done!
What confuses me even more you can look into the following screenshorts
It has installed the new kernel?
phoenixtraveller said:
FOR ALL THOSE WANTING UBUNTU/LINUX:
You just use DAF.EXE and DFT-Android (Desire original release with Magldr) partition layout.
Unyaffs BOOT.IMG and copy initrd.gz
Copy over ALL ubuntu \linux\ files to sdcard root (not \linux).
rename main adb_htc_leo_zimage to just zImage.
do not rename initrd.cpio.gz as ppl are doing: use initrd.gz from DFT' Android BOOT.IMG (unyaffs).
Now you can copy over all rootfs.ext2 to the appropriate partitions in NAND and Run.
Any suggestions on how to improve this?
Proper layout settings for flash.cfg?
I get to keyboard etc then cant use it (no usb connected - no touch).
But point is: IT WORKS AS LONG:
1) INITRD.GZ is Magldr compatible and matches flash.cfg/AD-NAND-partion (why I did this proof-of-concept with DFT's initrd)
2) rootfs.ext2 must now be mounted.
3) usb keyboard etc? internet? POWER?
self notes: for future ref: install magldr, do dft-droid-daf.exe, copy linux: ren htc_adb_zimage to just zImage. then. USE THE INITRD.GZ from inside DFT's BOOT.IMG. !!!
make magldr/ubuntu work: ad hardreset, install dft-android by daf.exe, copy all \linux\ files to root. rename files like so: (above)
Magldr and Ubuntu working: ok... You need to make sure your initrd.gz initial ramdisk is in sync with the nand partitioning by daf.exe so...
---
Update:
Hmmm.. Looks like--> It is mounting rootfs.ext2 --> by itself in - NAND? SDCARD? Will update but seems to have booted properly !!! Takes a LONG time and black screen etc for ages before "desktop" - mentions "adb" and other things in verbose output during "boot". Someone please let me know thoughts as I am nt kernel developer (drivers etc) and new to Linux. Thankyou. This is my first day on XDA. My first intro to all of this so sorry if over-posting or in wrong spot.
---
Update2:
Linux penguin screen verbose:
ANDROID unable to open persistent property directory
init: cannot find /system/...
(a lot of them)
then: enabling adb, adb open, et etc etc, host does not support read-only switch assuming write-enable...
mmc1: new high speed sdhc card at address b504
then a lot of lines with numbers microp set bkl(9) and ACR= FL= RAAC=
power button works as in screensaver/lock... this all leads up to keyboard and desktop eventually !!!
any ideas ?
Click to expand...
Click to collapse
It takes forever: but it is till going and ALIVE.
Can anyone please help getting Ubuntu/Linux up over Magldr-NAND/SD ***properly***?
Happy (as explained above) to make donation $$$.
Can you post a simple step by step guide for us Windows users?
I really dont know how to make it work.
Thanks.
i am getting a strange error after i connect the phone.
[email protected]:~/Desktop$ cd
ADB_install/ Backup/ Rom Android/
[email protected]:~/Desktop$ cd
ADB_install/ Backup/ Rom Android/
[email protected]:~/Desktop$ cd ADB_install/
[email protected]:~/Desktop/ADB_install$ sudo cp adb /usr/bin
[sudo] password for ionut:
[email protected]:~/Desktop/ADB_install$ sudo chmod +x /usr/bin/adb
[email protected]:~/Desktop/ADB_install$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? no permissions
[email protected]:~/Desktop/ADB_install$ adb devices
List of devices attached
???????????? no permissions
i am using on the phone this nand build: [03 Jan][NAND][data.img with copy from phone]LEO "Stock Desire" MOD
thanx
solved.
service MUST be started as root. if you are getting this error try this:
[email protected]:~$ sudo su -
[sudo] password for ionut: <<type root password >>
[email protected]:~# adb kill-server
[email protected]:~# adb start-server
[email protected]:~# adb devices
List of devices attached
0123456789ABCDEF device
seems it's working
The best way to install is to run on Root Terminal. This is placed on Applications -> System Tools.
On Ubuntu it is invisible and you must to enable it on System -> Preferences -> Main menu and make it visible.
hi.
i'm trying to root my HTC Legend (stock froyo) but i'm stuck to the downgrade step.
i've created the gold card but when i try to downgrade i get always this:
Code:
C:\Program Files (x86)\Android\android-sdk\tools>crackin.bat
"Copying tools"
2301 KB/s (698452 bytes in 0.296s)
1190 KB/s (76044 bytes in 0.062s)
2413 KB/s (655360 bytes in 0.265s)
"Freeing primary PERM linker"
rm failed for /data/DxDrm/fuse/*, No such file or directory
rm failed for /data/DxDrm/fuse, No such file or directory
rmdir failed for /data/DxDrm/fuse/, No such file or directory
cannot create /data/DxDrm/fuse: directory nonexistent
Unable to chmod /data/DxDrm/fuse: No such file or directory
"Freeing secondary PERM linker"
rmdir failed for /data/DxDrm/fuse/, No such file or directory
rmdir failed for /data/DxDrm, No such file or directory
link failed Permission denied
"Rebooting to normal mode to unlock CHMOD links"
rmdir failed for /data/dontpanic, Permission denied
rm failed for /data/DxDrm, No such file or directory
link failed File exists
link failed Permission denied
"Rebooting to normal mode to downgrade ROM"
/dev/mtd/mtd0: Permission denied
cr--rw---- 1 1001 2002 90, 0 Mar 5 17:17 /dev/mtd/mtd0
error writing misc: Permission denied
"Freeing links"
rm failed for /data/DxDrm, No such file or directory
rm failed for /data/dontpanic, Permission denied
any idea?
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
That should be enough to make it possible to run the 1.31 RUU.
same problem here..try many way as stated!!
Azaruc said:
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
That should be enough to make it possible to run the 1.31 RUU.
Click to expand...
Click to collapse
thanks for your answer.
please, tell me if i'm right.
i should follow these downgrade steps http://forum.xda-developers.com/showthread.php?t=725430 till the end when i keep receiving the reported error, then i should install visionary, temproot, and from a command prompt (starting from the "tools" directory of the android SDK? and the misc1-2.img goes there?) i should type those command.
and then?
run the RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_ 7.05.35.26L_release_126592_signed.exe?
thanks man!
i did it!
I get error [171] anyone have any idea what is the reason ??
please hepl
I tried every way i managed o find
hboot - 1.00.0000
radio-7.13.35.05
soft 3.14.161.1
kernel 2.6.32.17
Azaruc said:
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
That should be enough to make it possible to run the 1.31 RUU.
Click to expand...
Click to collapse
i get permissions denied on the last step
/data/local/flash_image misc /data/local/misc1-2.img
help please?
Ohh c'mom dude! What does "adb shell" return? What does "su" return?
Sent from my HTC Legend
chris.chhoeu said:
i get permissions denied on the last step
/data/local/flash_image misc /data/local/misc1-2.img
help please?
Click to expand...
Click to collapse
Did you get the # symbol after the su command? If not, then you have to do temp root again.
What does ADB say? Do you have Debug Mode eneabled?
Sent from my HTC Legend using XDA App
temproot on boot or temproot now pls ?? thanks m8
"Temproot now"
Sent from my HTC Legend using XDA Premium App
Received my KF about a week ago. Just tried to root it yesterday. That was successful. The instructions I was using said this: "This will “root” your Kindle Fire. You can actually stop here but I recommend you to go to the next steps to install TWRP Recovery, which will allow you to install/backup/restore ROMs and also “unroot” your Kindle Fire when needed easily." So, silly me, without doing further research, went on to the next steps. I almost immediately got stuck, here is the code, ending with the -bash where I was stuck.
Zach:~ Zbhest$
Zach:~ Zbhest$ cd Downloads/KindleFireRootMacLinux
Zach:KindleFireRootMacLinux Zbhest$ mkdir ~/.android
mkdir: /Users/Zbhest/.android: File exists
Zach:KindleFireRootMacLinux Zbhest$ cp adb_usb.ini ~/.android/.
Zach:KindleFireRootMacLinux Zbhest$ cp adb_usb.ini ~/.android/
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac kill-server
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac devices* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
08EC002600000001 device
Zach:KindleFireRootMacLinux Zbhest$ sh runmemac.sh
---------------------------------------------------------------
Easy rooting toolkit (v2.0)
created by DooMLoRD
Modified for Kindle Fire for Linux/Mac by Max Lee at RootKindleFire.com
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (10 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) enable USB DEBUGGING
from (Menu\Settings\Applications\Development)
(2) enable UNKNOWN SOURCES
from (Menu\Settings\Applications)
(3) [OPTIONAL] increase screen timeout to 10 minutes
(4) connect USB cable to PHONE and then connect 2 computer
---------------------------------------------------------------
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1836 KB/s (23056 bytes in 0.012s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40119cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd195bb 0xafd39357
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle USB DEBUGGING (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
4634 KB/s (1075144 bytes in 0.226s)
--- correcting permissions
--- remounting /system
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.038 secs (28293263 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
1508 KB/s (22228 bytes in 0.014s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
5116 KB/s (785801 bytes in 0.149s)
--- cleaning
--- rebooting
--- WAITING FOR DEVICE
5382 KB/s (3104805 bytes in 0.563s)
Error: Could not access the Package Manager. Is the system running?
All Done, Kindle Fire ROOTED!!!
Check out RootKindleFire.com for more cool hacks!
Zach:KindleFireRootMacLinux Zbhest$
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac root
restarting adbd as root
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac remountremount succeeded
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac push su /system/xbin/su
260 KB/s (22228 bytes in 0.083s)
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chmod -6755 /system/sbin/su
Bad mode
Zach:KindleFireRootMacLinux Zbhest$ .adb./adb-mac shell chown 0.0 /system/xbin/su
-bash: .adb./adb-mac: No such file or directory
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chown 0.0 /system/xbin/su
Zach:KindleFireRootMacLinux Zbhest$ cd Desktop/kindleFireRootNew
-bash: cd: Desktop/kindleFireRootNew: No such file or directory
Zach:KindleFireRootMacLinux Zbhest$ cd desktop/kindlefirerootnew
-bash: cd: desktop/kindlefirerootnew: No such file or directory
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac push su /system/xbin/su
877 KB/s (22228 bytes in 0.024s)
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac root
adbd is already running as root
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac remountremount succeeded
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac push su /system/xboin/su
264 KB/s (22228 bytes in 0.081s)
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell cown 0.0 /system/xbin/su
cown: not found
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chown 0.0 /system/xbin/su
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chmod 06755 /system/xbin/su
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac install Superuser.apk
3818 KB/s (785801 bytes in 0.200s)
pkg: /data/local/tmp/Superuser.apk
Success
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell
# su
# idme bootmode 4002
<idme> write 4002 to offset 0x1000
# reboot
Zach:KindleFireRootMacLinux Zbhest$ ./fastboot-mac -i 0x1949 boot twrp-blaze-2.0.0RC0.img
-bash: ./fastboot-mac: No such file or directory
And now my Mac does not recognize my KF. When I unplug my KF it appears bricked (will not turn on), but when it is plugged into a wall outlet I can do the hard reset, it charges, but does not go past the KF boot screen.
Also, ADB does not recognize any devices.
Additionally, I have a windows 7 machine. I was going to attempt to pick up where I left off, but as my KF is listed as an "unknown device," I cannot update drivers (or do not know how to do so manually). I also installed this little number: http://forum.xda-developers.com/showthread.php?t=1430038
And I currently have linux loaded on my W7 machine. When I try to use the "normal_boot" command, which is advised, I get:
"Resetting bootmode to standard boot...
< waiting for device >
"
So, yeah. That is where I am at. I WOULD go on to the other directions in firekit, but would prefer not to completely void the warranty using the "usb boot mode trick".
If windows 7 is the key here, I may need a walk through for driver installation and such. Otherwise, I am not totally disinclined to call customer service and ask for a replacement. Apparently they have been good about replacing rooted kindles?
Same issue right now... already tried reinstalling windows/firekit liveusb but nothing works=\ Is there any news on this problem?
http://support.microsoft.com/kb/315539/en-us
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
I did read all those threads about such problem before. Just no matter what i do those drivers won't install. I only get unknown device on 7/xp and cannot change it coz when i manually select those drives windows says that there no device info in it=\ Thanks for help anyways
did you select adb_usb.ini ? it's just the folder with this file in it. selecting just the folder is usually enough. if you want to select the file: the driver file is android_winusb.inf. there is the harware info
if you have xp available then use this machine - it's easier
Yeah i did select that inf file (it was only one selectable in folder anyway) but it still says same stuff. I have xp right now if that gonna change something
yes xp is easier to handle because:
only 32bit -> only 1 driver version
no user access control -> don't need to do every thing as administrator
please check the following:
you have a .android folder under your user directory - in this folder is adb_usb.ini - the file has entries for device 0x1949 and 0x18D1 - if not run install.bat from the driver set i provided
check your device manager and delete every entry with kindle or adb
unplug and replug your kf - select the driver i provided manually
Got those 0x1949 and 0x18D1 in adb_usb file. And i only have unknown device every time i plug kindle in, no adb kindle at all
right click unknown device - update driver - select android_winusb.inf
if this don't work we have to cleanup old drivers -> could help per teamviewer if you like
When i try to update driver and manually use inf you provided it says that there no device info there=\ And i got unknown device since fresh windows install so idk what driver can cause it -.- I could ve try teamviewer but my windows is not english so it gonna be quite useless.
what language ?
Well it's in russian +there no laptop drivers yet coz im using xp only for this god dam kindle
ok your right - with russian i have a problem
will try to describe you the steps:
disconnect and power off (pwr ~30sec) your KF
open a command prompt
type "set devmgr_show_nonpresent_devices=1"
type "start devmgmt.msc"
Click Show hidden devices on the View menu in Device Manager
uninstall every entry with kindle, android phone or adb device
power down computer and power on again (no restart)
tell me if your done - we will resume ...
ok i did everything step by step tho there was none of adb/android phone/kindle so i just deleted my unknown device.
ok - lets resume:
you may want to delete your old driver set previously downloaded - it must be faulty
now download the one from this post and extract it to c:\
now plugin your kf (don't power it on - will do it by itself)
if you' asked
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver i attached
-Select okay and okay
just in case you'r not asked:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver i attached
-Select okay and okay
if this don't work eighter then i would think you have a faulty cable !
try an other one ...
Nope still same=\ Guess i will look for new cable tomorrow then tho this one was just fine today at transfering stuff (dam you nokia!). Well thanks for trying to help anyway.
you have the nokia cable - i have the same one
tell me the status your kf now
stuck at boot screen ?
some other tricks:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
if you'r stuck in wrong bootmode:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
if you issue the fastboot commands and get <waiting for device> over some while power the kf off (pwr ~30sec) and on. at some point it should recognize the command
Yeah it same as before=\ I have same problem as topic starter aka device in fastboot and windows won't recognize it and install correct drivers. Fastboot commands won't work coz i don't have correct drivers and all they do is stuck on waiting for device/
xx time later = IT WORKS!!! for some weird reason it picked kindle up nothing changed in windows yet it works! Thanks again for your help time to flash recovery again.
courious - just tested on mine
when i switch to fastboot it is recognised as "android adb interface"
not the composite thing !
and i have the same drivers on xp
perhaps you want to try this one:
http://forum.xda-developers.com/showthread.php?t=1428428
sorry - no more ideas ...
UPDATE: hurraaa !!! - wish you all the best and good luck !!!
Okay...so here Iam once more driving myself insane. I'am pretty intermediate with devices and rooting and can usually do things solo or with slight help...but!!. So just received the device from a friend of mine and I actually want to unlock it to allow Simple Mobile (sim card) and services...when i Hboot it says Radio ON...to what i presume will be the freedom I need. Okay so here goes my trouble... I know that your supposed to downgrade the device to root, or temp root, I have been following the instructions to the T (or at least I'm hoping so) on http://forum.gsmhosting.com/vbb/f62...ouch-4g-2-3-4-hb-0-89-0005-stock-rom-1344617/ and even on this site which is where i also have tried following the directions. Okay so what confuses me is that one post says tools, the other says platform-tools..and if i'm incorrect the directory has both. Okay so I've opened up a command line from both and it's around
$ adb push fre3vo /sdcard/fre3vo
$ adb shell
$ chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
that I start to have my trouble!! I was actually able to copy this...
C:\AndroidSdk\platform-tools> adb push fre3vo /sdcard/fre3vo
adb server is out of date. killing...
* daemon started successfully *
cannot stat 'fre3vo': No such file or directory <---is this the error file im supposed to get?? so I rewrite it connecting the sdcard to fre3vo and then wallah!! A whole bunch of writing like ...
C:\AndroidSdk\platform-tools> adb push fre3vo/sdcard/fre3vo
Android Debug Bridge version 1.0.31 <------------------------Right over here (excessive content so i deleted)
C:\AndroidSdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
Unable to chmod /data/local/tmp/fre3vo: No such file or directory
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo: not found <---------------------------So I go down through the line of codes I'm supposed to trty and all say not found
$
Now as you can see this is where my problems arise. Every code or set of codes I get result in not found?? What am I doing wrong? I saw a tutorial on youtube and when he added this coding it was immediately followed by a massive amount of writing and then ADB seems to have shut down...Am i supposed to have ADB running while I do this? I've even tried rewriting the codes thinking that maybe a space was misplaced or such. Please help guys. Also what I did was manually created a directory at C;\Adroidsdk since there was none and placed all of the adb tools there or hope I did. Before that every time I'd open the executable the adb program would open from C\users\appdata\local\temp. I honestly don't know where i went wrong. I really want to root this phone. I went as far as spending 30 dollars on one of those bogus websites that can "root your device guaranteed" only to find that the programs they had like Superoneclick I already had on my desktop. Go figure..Ok I will sit here miserably until one of you rescues me. Thanks.
Some people said they used this tool to root.
http://forum.xda-developers.com/showthread.php?t=1870652
I personally have not tried it, but hey, you never know
Did you unzip the files before putting them in platform tools?
Also shouldn't you be pushing the file to the folder you are trying to chmod? It looks like you are pushing it to sdcard and I'm pretty sure it needs to be in the tmp folder:
adb push fre3vo /data/local/tmp
Instead of sdcard, but don't quote me on that I haven't done this in ages. Trying it *shouldn't* break anything... I think
If you can't push it to tmp then you are missing steps.
Edit:
Found an xda thread that verifies the file should be pushed to data local tmp
http://forum.xda-developers.com/showthread.php?t=1178912
Shame on the person who wrote the other guide.
If u already got s-off (cuz u might have to downgrade) or still in fryo u can try vissionary+ method efficient stressless
N_otori0us_ said:
Some people said they used this tool to root.
http://forum.xda-developers.com/showthread.php?t=1870652
I personally have not tried it, but hey, you never know
Click to expand...
Click to collapse
yeAh this is one of the tools the $30 dollar spot gave me. Funny because it actually says it worked..Su installed Busybox installed and once process is done..Nada..zip..is still the same now to convince them of a refund.
Relsig said:
Did you unzip the files before putting them in platform tools?
Also shouldn't you be pushing the file to the folder you are trying to chmod? It looks like you are pushing it to sdcard and I'm pretty sure it needs to be in the tmp folder:
adb push fre3vo /data/local/tmp
Instead of sdcard, but don't quote me on that I haven't done this in ages. Trying it *shouldn't* break anything... I think
If you can't push it to tmp then you are missing steps.
Edit:
Found an xda thread that verifies the file should be pushed to data local tmp
http://forum.xda-developers.com/showthread.php?t=1178912
Shame on the person who wrote the other guide.
Click to expand...
Click to collapse
Yeah, I've actually tried it this way and the other. the thing is one site says tools..the other platform tools, and then this last one sd card?? I've tried them all I think...Maybe my adb is installed in the wrong area? could that be why possibly after i chmod and start putting in the files to finally root the phone it says "file not found"? I know it's alot of writing but I'm going to copy and paste everything on a new reply to see if you or anyone can see what I'm doing wrong. I even copy and paste to the cmd and nothing.
ughoji said:
If u already got s-off (cuz u might have to downgrade) or still in fryo u can try vissionary+ method efficient stressless
Click to expand...
Click to collapse
If you could find me a place to download visionary from I'd be eternally grateful to you. It seems when they banned the app from google they must've done so everywhere else. Everytime I try to download my PC stops the download and says virus detected even with anti-virus off. Every time I go to the Visionary website and click the download link it takes me to some bogus website and never to the download link. The other sites I've found them on them on the PC says Virus detected...or maybe it's google chrome. Think I should try downloading on Internet Explorer?
what i'm gonna do guys is try the process from the xda website and then post it to see if one of you detect where I went wrong. Crossing Fingers...
now here it is ladies and gents...maybe we can find the problem here somewhere
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Jorge>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\Users\Jorge>cd c:\androidsdk\platform-tools
c:\AndroidSdk\platform-tools>adb push fre3vo /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
cannot stat 'fre3vo': No such file or directory <-- here also i get the no file or directory error so then i rewrite putting fre3vo and data together which follows with fre3vo/data
c:\AndroidSdk\platform-tools>adb push fre3vo/data/local/tmp
Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
c:\AndroidSdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
Unable to chmod /data/local/tmp/fre3vo: No such file or directory <--when i input chmod 777 /data/local/tmp/fre3vo it says no such file...so i
$ chmod 777/data/local/tmp/fre3vo rewrite it and connect the 777 to data like chmod 777/data and then
chmod 777/data/local/tmp/fre3vo the usahe chmod ...etc.
Usage: chmod <MODE> <FILE>
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo: not found
$ <-----I can continue and write the other passwords but it says not found.
I'm wondering if i might've installed adb in the wrong place and if so how do i change the variables? should i put C:android or as currently ANDROID_SDK_HOME then C:\AndroidSdk
There's no wrong place to install adb. If your in GingerBread, I don't think visionary will work. Try ginger break. But you have to downgrade to root your phone. If your on 2.3.4, you gotta get on 2.2.1 I think
Sent from my myTouch 4G using xda app-developers app
N_otori0us_ said:
There's no wrong place to install adb. If your in GingerBread, I don't think visionary will work. Try ginger break. But you have to downgrade to root your phone. If your on 2.3.4, you gotta get on 2.2.1 I think
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
yeA
YEAH PHONE IS ON 2.3.4...ooops sorry for caps! so can you see where i might've went wrong? I mean is it supposed to say file not found or those things? somewhere i messed up..sigh...
c:\AndroidSdk\platform-tools>adb push fre3vo /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
cannot stat 'fre3vo': No such file or directory
Is fre3vo in C:\AndroidSdk\platform-tools?
cause thats where you need to unzip the files to
-Nipqer
Found the problem...
Thanks to you guys I went back step by step and figured out the problem . So apparently when i had originally downloaded the fre3vo and misc files they were the wrong files. I looked inside of platform tools and both files were there as applications?? yeah like actual install type applications..finally it has all seemed to work so i'll now move on to step two...won't say im done till ive succesfully rooted and ill keep you posted but thank you guys.,.for your time and dedication towards helping me :_)
Playdoe said:
Thanks to you guys I went back step by step and figured out the problem . So apparently when i had originally downloaded the fre3vo and misc files they were the wrong files. I looked inside of platform tools and both files were there as applications?? yeah like actual install type applications..finally it has all seemed to work so i'll now move on to step two...won't say im done till ive succesfully rooted and ill keep you posted but thank you guys.,.for your time and dedication towards helping me :_)
Click to expand...
Click to collapse
Just in case u wanted to root an s-off phone search pd15img(2.2.1).zip got mine from 4shared rename it to pd15img.zip and move it to root of your SD card boot into bootloader navigate to the second option then OK with power on to downgrade. here is a working visionary but note most cases play store doesn't agree to download make sure u got explore or es in another phone to send it run your rooting and every.the visionary process is in the dev part its pinned
I used visionary and it worked for me