Related
I am running ubuntu 9.04. I have eclipse and the Android s.d.k. set up and running perfectly. But I cannot figure out how to setup a.d.b.
I apologize for the new post, but I promise I have searched for hours on this forum and Google. All I found was info on installing on Windows, and fixing a.d.b that used to work but won't work now after updating to 9.04. Anybody have a tutorial or a fix that I might have missed? Thanks in advance.
there is nothing to set up just make shure it has execute permissions, thats what had me stumped LOL
#chmod +x adb
then just plug in the g1 (no drivers required) and
#adb whatever you want
but i was using arch :O
to make it easier copy the adb executable to /usr/bin and you can execute from any directory withoud using cd /directory
Code:
sudo cp /androidsdk/tools/adb /usr/bin
sudo chmod +x /usr/bin/adb
that's how i use mine on my 8.10 and 9.04
Thanks guys, pretty sure it's working, just need to figure out how to connect to device. I will try your suggestions.
Done. Then I tried
#adb logcat
and i get
- waiting for device -
should I
#cd /bin
#adb logcat
?
I am following tutorials for windows, so it is kind of confusing. I don't think I can connect. I get
Code:
[email protected]:~$ adb start-server
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$
Here is me trying all kinds of stuff
Code:
[email protected]:~$ adb start-server
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$ adb kill-server
[email protected]:~$ adb
Android Debug Bridge version 1.0.20
-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
-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
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
(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] <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)
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 root - restarts adb with root permissions
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PDP 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.
[email protected]:~$ adb get-state
* daemon not running. starting it now *
* daemon started successfully *
unknown
[email protected]:~$ devices
bash: devices: command not found
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$ adb remount
error: device not found
[email protected]:~$ adb start-server
[email protected]:~$ adb remount
error: device not found
[email protected]:~$ adb get-serialno
unknown
[email protected]:~$
tried another usb cable, different usb port. Same stuff
Code:
[email protected]:~$ adb shell
error: device not found
[email protected]:~$ adb start-server
[email protected]:~$ adb shell
error: device not found
[email protected]:~$ ls
adb examples.desktop Templates
android-sdk-linux_x86-1.5_r2 Firefox_wallpaper.png Videos
Desktop Music workspace
Documents Pictures World of Warcraft Trial
eclipse Public
[email protected]:~$ cd /
[email protected]:/$ ls
bin dev initrd.img media proc selinux tmp vmlinuz
boot etc lib mnt root srv usr
cdrom home lost+found opt sbin sys var
[email protected]:/$ adb shell
error: device not found
[email protected]:/$ adb start-server
[email protected]:/$ adb shell
error: device not found
[email protected]:/$ ls
bin dev initrd.img media proc selinux tmp vmlinuz
boot etc lib mnt root srv usr
cdrom home lost+found opt sbin sys var
[email protected]:/$ adb start-server
[email protected]:/$ adb shell
error: device not found
[email protected]:/$ adb kill-server
[email protected]:/$ adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
[email protected]:/$ adb shell
error: device not found
[email protected]:/$
Any ideas?
I am using the Rogers v3 Rom with jf1.42 bootloader and the 2005 s.p.l
Would any of that matter.
CBowley said:
I am using the Rogers v3 Rom with jf1.42 bootloader and the 2005 s.p.l
Would any of that matter.
Click to expand...
Click to collapse
Doubtful. I too am looking to get ADB running on my Ubuntu laptop, as it would save a bunch of time for me being able to use it instead of my slow windows computer (ADB is corrupted driver-wise on my main rig).
Anyone have any reasonable tutorials for lower-level linux users on Ubuntu 9.04 32-bit?
I have Ubuntu + SDK and I don't have any issue.
Are you sure you installed your SDk the correct way == you followed exaclty the android.com howto ?
it should work with ubuntu 9.04. Just follow this instructions to setup connection to your phone. mainly create rule for you device in udev.
http://developer.android.com/guide/developing/device.html
If you're developing on Ubuntu Linux, you need to add a rules file:
1. Login as root and create this file: /etc/udev/rules.d/50-android.rules.
For Gusty/Hardy, edit the file to read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
For Dapper, edit the file to read:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
2. Now execute:
chmod a+rx /etc/udev/rules.d/50-android.rules
reboot, then if you are still having problem after this, one more thing to try to start server swith sudo.
adb kill-server
sudo adb start-server
knaries2000 said:
it should work with ubuntu 9.04. Just follow this instructions to setup connection to your phone. mainly create rule for you device in udev.
http://developer.android.com/guide/developing/device.html
If you're developing on Ubuntu Linux, you need to add a rules file:
1. Login as root and create this file: /etc/udev/rules.d/50-android.rules.
For Gusty/Hardy, edit the file to read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
For Dapper, edit the file to read:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
2. Now execute:
chmod a+rx /etc/udev/rules.d/50-android.rules
reboot, then if you are still having problem after this, one more thing to try to start server swith sudo.
adb kill-server
sudo adb start-server
Click to expand...
Click to collapse
I think I did this part, I will double check. I did try sudo adb start-server, that didn't work. I will double check the rest. Thank you.
Oh that's why I never did it, I cannot find a rule for jaunty, only hardy, dapper, and gutsy.. I'll do more searching. Thanks for the idea.
Okay it works now. This is what I get
Code:
[email protected]:~$ adb start-server
* daemon not running. starting it now *
* daemon started successfully *
[email protected]:~$ adb devices
List of devices attached
HT845GZ28769 device
[email protected]:~$ adb shell
# ls
cache init.goldfish.rc sbin
data init.rc sdcard
default.prop init.trout.rc sqlite_stmt_journals
dev proc sys
etc root system
init runme.sh
#
THIS IS WHAT I DID:
created 2 files on my desktop named:
50-android.rules
51-android.rules
Then I edited both files to read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Then I opened terminal and did this
Code:
[email protected]:~$sudo mv /home/chris/desktop/50-android.rules /etc/udev/rules.d
[email protected]:~$sudo mv /home/chris/desktop/51-android.rules /etc/udev/rules.d
Then I rebooted and It all worked. I am runnung ubuntu 9.04 jaunty jakelope(sp?)
Thanks for everyones help. Hope this helps someone else.
CBowley said:
Okay it works now. This is what I get-------
Thanks for everyones help. Hope this helps someone else.
Click to expand...
Click to collapse
Thank you so much, this works perfectly. Bump for someone else finding this who needs it.
Yes it has to be rule 51, not 50 with Jaunty. Google doc is not up to date yet.
see this thread :
http://groups.google.com/group/andr...read/thread/ab6e89c4b51cd905/a05c2a749cd55b88
> this was in /etc/udev/rules.d/50-android.rules
> But it seems to also work like this : (method for Ubuntu 9.04 :
> http://www.frandroid.com/2371/ubuntu-904-et-android/ )
> -> in /etc/udev/rules.d/51-android.rules :
> SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4", MODE=”0666"
Ubuntu 9.04 already has a rules/50-something file so you need to make
sure that the android rule is > 50. Otherwise whatever you define gets
reset. We should update the doc to just state rule/51-android.rules
which will work right now till the base configuration changes once
again
> Also take care if you copy/paste this rule : looks like double quotes
> (") may be wrongly copied from html page, and then it did not work for
> me before I retyped them.
Hmm thanks for the info. That's a new one.
Edit
Ok sorry a little OT, but I responded to this because I did not see an answer posted. I Seem to be having problems with posts showing up when I am logged in... but not when I am logged out... really weird. After I logged out at least another dozen posts showed up in this thread.
you need to change the rule from 50 to 51 on ubuntu 9.4
didnt realise the answer was posted sorry. but its def the right answer
CBowley said:
I am running ubuntu 9.04. I have eclipse and the Android s.d.k. set up and running perfectly. But I cannot figure out how to setup a.d.b.
I apologize for the new post, but I promise I have searched for hours on this forum and Google. All I found was info on installing on Windows, and fixing a.d.b that used to work but won't work now after updating to 9.04. Anybody have a tutorial or a fix that I might have missed? Thanks in advance.
Click to expand...
Click to collapse
sudo bash -c "echo SUBSYSTEM==\"usb\", SYSFS{idVendor}==\"0bb4\", MODE=\"0666\" > /etc/udev/rules.d/51-android.rules"
sudo /etc/init.d/udev restart
killall adb
adb shell
[Q] [GUIDE] Downgrade G2 (2.3.3) & DZ (2.3.3) & mT4g (2.3.4) w/ S-ON to Stock Froyo
i would like to downgrade using this thread. the sdk is not recognizing that i have installed jdk. is there anyone out there that would be willing to help me out . i searched and found there is no method to root 2.3.4 yet. i have not had any luck getting past installing sdk. i would appreciate help.
dirtyreturn said:
i would like to downgrade using this thread. the sdk is not recognizing that i have installed jdk. is there anyone out there that would be willing to help me out . i searched and found there is no method to root 2.3.4 yet. i have not had any luck getting past installing sdk. i would appreciate help.
Click to expand...
Click to collapse
I used the sdk zipped file and extracted it to local disk c:
if you don't mind another couple questions WOLF26915. im using windows 7 command prompt . am i supposed to? so far i got to
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\mine>cd\
C:\>cd androidsdk
C:\androidsdk> cd androidsdk\platform-tools\
The system cannot find the path specified.
C:\androidsdk>cd platform-tools
C:\androidsdk\platform-tools>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\androidsdk\platform-tools>adb push fre3vo / androidsdk/data/local/tmp
Android Debug Bridge version 1.0.26
-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 <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
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 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] <file> - push this package file to the device and i
nstall 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)
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 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>
dirtyreturn said:
if you don't mind another couple questions WOLF26915. Ok, i downloaded the sdk zip file placed it to c:/, right now is is installing updates or recommendations. do you think i will be set to use after it's done?
Click to expand...
Click to collapse
ya you should be good but if you are not here is a guide to help setup adb/fastboot http://forum.xda-developers.com/showthread.php?t=928370
if you could take a look at updated post.
dirtyreturn said:
if you don't mind another couple questions WOLF26915. im using windows 7 command prompt . am i supposed to? so far i got to
C:\adb>adb devices
List of devices attach
SH12SRM02177 device
C:\adb>adb shell
$ adb push fre3vo data
adb push fre3vo data/l
adb: permission denied
$ adb shell cat /dev/m
adb shell cat /dev/msm
adb: permission denied
$
Click to expand...
Click to collapse
ok you are doing it wrong type this
adb push fre3vo /data/local/tmp (hit enter)
adb shell (hit enter)
then you should see $ now type
chmod 777 /data/local/tmp/fre3vo (hit enter)
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF (hit enter)
then go to next step
i get permission denied. did i need to create folders for this data->local ->tmp ?
dirtyreturn said:
i get permission denied. did i need to create folders for this data->local ->tmp ?
Click to expand...
Click to collapse
ok if you don't mind pm me your number maybe we can get it done
s should be on right? is gingerbreak alright to use? hboot 0.86.0000, radio 26.11.04.03_M. Update is unzipping. is ROM Manager reliable for a new user?
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 !!!
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage & No ROM to Flash [19 May 15]
How to Sideload in TWRP if you erase your Internal Memory and don't have a ROM to Flash or Restore
Warning!
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements
Code:
#include
/*
* Unlocked Phone @ HTCDEV
* Custom Recovery
*/
Before You Start - Update Android SDK - How to set up Android SDK (ADB)
Instructions
MAKE SURE YOU BACK UP YOUR SD CARD FIRST!!!!!!!!
Make Sure HTC Drivers are installed and ADB is already working
1. Reboot into TWRP
2. in TWRP, Hit andvanced and find Sideload
3. Swipe to start Sideload
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. type adb devices and it should show your device conntected and say sideload
6. Your ZIP file should already be in your adb folder - See Example Below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7. You are now ready to push the zip.....
8. type adb sideload nameofzip.zip <------------See Example Below
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. if adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery
ADB Push from Recovery - If Sideload Fails For You
adb push rom.zip /data/media/0/
Click to expand...
Click to collapse
If You have any Troubles with ADB
Koush Universal ADB Driver - Works on Windows 8 - Thanks xeroxide
YouTube Video for ADB Help
How to install ADB Drivers for any Device
FAQ
If your Using Windows 8/8.1
Refer to Post #1 above the social media links for the 2 Posted Links
If your Output looks similiar to this below, then you are not in sideload mode or you typed the command incorrectly
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\William>cd Downloads\ADB
C:\Users\William\Downloads\ADB>adb sideload Slim-nozomi-4.2.2.build.6-OFFICIAL
Android Debug Bridge version 1.0.26
-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 <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
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
disconnect <host>:<port> - disconnect from a TCP/IP device
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
(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 i
nstall 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)
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 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.
C:\Users\William\Downloads\ADB>-d
'-d' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB>-d\
'-d\' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB>-d: \
'-d:' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB>:-d
C:\Users\William\Downloads\ADB>-d\
'-d\' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB>-d
'-d' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB
DO THE FOLLOWING - (Refer to Post 1 Before you start for Picture Example)
1. Run sdk manager and update all the 4.1.2 - 4.4.2 binaries, you will see installed if you have done so
2. Reboot into TWRP
3. Go to advanced
4. Touch ADB Sideload
5. Swipe To start sideload
6. in command promt example: cd c:\android\sdk\platform-tools (that is where my adb files are at)
7. Once you have navigated to where your adb is at in command promt type adb devices
8. When you type adb devices, it should show your HTCxxjxihdjiw (whatever yours is) and Sideload which indicates you are set up properly
9. Once you see the above type adb sideload nameofzip.zip
Thanks for spending the time to write this :good:
I used the all in one toolkit and it worked perfectly.
This is great for people who don't know about it.
Cheers
Great guide for newcomers!
OK I laugh hard when I saw ur file name is almost the same as I do. ARHD 10.2.
Is that becuz it's too long to type in? LOL
Nice tutorial though.
pablo11 said:
Thanks for spending the time to write this :good:
I used the all in one toolkit and it worked perfectly.
This is great for people who don't know about it.
Cheers
Click to expand...
Click to collapse
Thanks guys appreciate it.... Lol yeah man the file name is way too long haha
gianton said:
Great guide for newcomers!
Click to expand...
Click to collapse
wm2001wm2001 said:
OK I laugh hard when I saw ur file name is almost the same as I do. ARHD 10.2.
Is that becuz it's too long to type in? LOL
Nice tutorial though.
Click to expand...
Click to collapse
Sent from my HTC One using xda premium
You're God sent.
I bricked my friend's One & luckily found this post.
Everything's fixed.
Thanks for saving the One.
dsymbol said:
You're God sent.
I bricked my friend's One & luckily found this post.
Everything's fixed.
Thanks for saving the One.
Click to expand...
Click to collapse
I am glad you were able to fix your friends phone bro always good when you dodge that bullet lol
Sent from my HTC One using xda premium
thanks
thanks my bro but This method does not work with me
plz can you help me
here logo
-------------------------------------
C:\andsdk\tools>adb sideload Rayglobe_4_0_2_.zip
Android Debug Bridge version 1.0.26
-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 <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
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 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] <file> - push this package file to the device and i
nstall 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)
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 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:\andsdk\tools>
As a note I had to do this last week when I upgraded to the new 4.2.2 roms, and I was unable to sideload the rom until I rename it to something smaller.
So instead of something like "rom_trickdroid7.5" I just renamed it to "rom.zip" and at that point sideload command worked fine.
zakryia said:
thanks my bro but This method does not work with me
plz can you help me
here logo
-------------------------------------
C:\andsdk\tools>adb sideload Rayglobe_4_0_2_.zip
Android Debug Bridge version 1.0.26
-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 <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
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 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] <file> - push this package file to the device and i
nstall 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)
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 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:\andsdk\tools>
Click to expand...
Click to collapse
OK so what you need to do is place the zip in your tools folder in andsdk. I am not sure if you have a platform-tools folder where there is an adb.exe file but whatever folder you have that in the zip also needs to go.
In recovery make sure you navigate to advanced then sideload and then swipe to start sideload. Once sideload is enabled then you type in the command prompt adb devices... It should show your device and have sideload next to it. If that is what you see last step is type
adb sideload nameofzip.zip
It automatically hoes to the root of your internal memory
Sent from my HTC One using xda premium
I changed directories to where the adb.exe is (inside platform-tools) and ADB Sideload is already started in TWRP. However, whenever I type "adb devices" it only says "List of attached devices" and nothing under it. Whenever I try flashing the ROM, it says error: device not found. What am I doing wrong here? I even changed the name of the ROM to rom.zip to make it shorter as per a suggestion in the first page of the thread, but that didn't work either.
Okay now I realize my device isn't actually recognized, although it works fine with fastboot usb.
What do I do? I tried having windows automatically search for drivers but it didn't find anything.
Okay after doing some more reading I realized I never actually opened SDK Manager, and when I try, it just opens a black command prompt window and then shuts down. I then came across this article and realized I need Java JDK drivers before I can actually run SDK Manager and then follow the rest of the tutorial. Maybe that is the problem??
TarekElsakka said:
Okay now I realize my device isn't actually recognized, although it works fine with fastboot usb.
What do I do? I tried having windows automatically search for drivers but it didn't find anything.
Click to expand...
Click to collapse
are you trying to use adb while fastboot is running on the phone? if so that won't work.
you need to have your phone in recovery mode or during normal operation for adb to work.
also make sure no other instances of adb are running use task manager (through ctrl+alt+del) to check and make sure no other instance of adb is running. i had the issue where it wouldn't kill previous iterations of itself.
*edit*
hmmm i just noticed your screenshot.
looks like you may need to reinstall the htc drivers, alternatively you could try to install koush's universal adb driver.
TarekElsakka said:
Okay after doing some more reading I realized I never actually opened SDK Manager, and when I try, it just opens a black command prompt window and then shuts down. I then came across this article and realized I need Java JDK drivers before I can actually run SDK Manager and then follow the rest of the tutorial. Maybe that is the problem??
Click to expand...
Click to collapse
could very well be, if the sdk isn't properly installed - chances are the drivers aren't either. have you tried manually updating the drivers for the "unknown device"?
TarekElsakka said:
I changed directories to where the adb.exe is (inside platform-tools) and ADB Sideload is already started in TWRP. However, whenever I type "adb devices" it only says "List of attached devices" and nothing under it. Whenever I try flashing the ROM, it says error: device not found. What am I doing wrong here? I even changed the name of the ROM to rom.zip to make it shorter as per a suggestion in the first page of the thread, but that didn't work either.
Click to expand...
Click to collapse
Hey Man, you need to make sure you install HTC Drivers and make sure the phone is recognized by the computer. Also, open sdk Manager and download updates, I will post a screen shot, I am using the same adb bundle you are. Update all the 4.1.2 and 4.2.2 APIs and next to each item under 4.1.2 and 4.2.2 make sure it says installed...May help with adb recognizing your phone.
The only issue right now is your phone being recognized by adb while in sideload because once it is the process will work I can promise you that.
Let me know if you have questions, I would get back to you sooner but I am in Hawaii and where its 11pm on the east its only 5 18pm here
Yeah, thank you very much guys. I was playing God of War and waiting for HTC Sync Manager to download so I can install it, haha. Everything went fine and the rom sideloaded 100%. Now I rebooted into recovery but I do not know where the rom.zip is located so I can install it? Any ideas?
---------- Post added at 05:31 AM ---------- Previous post was at 05:26 AM ----------
Never mind, I just realized it should be in the sideload.zip file. I am so dumb today.
Thanks for all your help, guys.
TarekElsakka said:
Yeah, thank you very much guys. I was playing God of War and waiting for HTC Sync Manager to download so I can install it, haha. Everything went fine and the rom sideloaded 100%. Now I rebooted into recovery but I do not know where the rom.zip is located so I can install it? Any ideas?
---------- Post added at 05:31 AM ---------- Previous post was at 05:26 AM ----------
Never mind, I just realized it should be in the sideload.zip file. I am so dumb today.
Thanks for all your help, guys.
Click to expand...
Click to collapse
Glad everything worked out man that is what is important. The forum should always be about helping others
Sent from my HTC One using xda premium
Quick question guys, does sideload work with Cwm recovery too ?
Vodka69er said:
Quick question guys, does sideload work with Cwm recovery too ?
Click to expand...
Click to collapse
I have never used CWM but if you boot into recovery, look for ADB Sideload through the options you have in CWM Recovery, if you do enable sideload and verify its connected and recognized by the computer by typing adb devices and it will show you your device with sideload. If it shows that then yes it will work
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