Related
i was ****ing around with terminal trying to get it to recognize my phone and i created a bash profile but now when i open terminal i get
-bash: {PATH}:: command not found
when i was copying/pasting **** from the tutorial i hit enter too soon and now i just get errors all the time when i try to do **** in terminal. anyway to revert terminal back to the way it was?
Code:
Last login: Sun Jul 25 00:08:05 on ttys000
e-bash: {PATH}:: command not found
new-host:~ videinfra$ echo $path
new-host:~ videinfra$ /Users/videinfra/sdkfolder/tools
-bash: /Users/videinfra/sdkfolder/tools: is a directory
new-host:~ videinfra$ /Users/videinfra/sdkfolder/tools/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
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 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.
new-host:~ videinfra$ adb devices
-bash: adb: command not found
new-host:~ videinfra$ adb usb
-bash: adb: command not found
new-host:~ videinfra$ -d
-bash: -d: command not found
new-host:~ videinfra$ $path
new-host:~ videinfra$ cd /Users/videinfra/sdkfolder/tools
new-host:tools videinfra$ adb devices
-bash: adb: command not found
new-host:tools videinfra$ -bash delete
-bash: -bash: command not found
new-host:tools videinfra$ .bash
-bash: .bash: command not found
new-host:tools videinfra$
I downloaded and installed the sdk manager, downloaded and installed the sdk packages, and rebooted. Since I rebooted, I haven't been able to start up the manager to update anything (I needed to update adb).
Why is this?
Swyped From My Mikrunny'd Superphone Using Magic (TapaTalk 2 Beta 5)
If you're running windows it could be possible that after installing the new ask tools that the filepath for adb was screwed up somehow.
Sent from my Incredible 2 using Tapatalk
disconnecktie said:
If you're running windows it could be possible that after installing the new ask tools that the filepath for adb was screwed up somehow.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
How would I go about fixing it?
Here's what I'm getting:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Tyler>adb
Android Debug Bridge version 1.0.29
-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 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] <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 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 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:\Users\Tyler>
Is this right?
Is there a way to do a full wipe of the phone? externalSD and all things in between. Im just curious.
aer0zer0 said:
Is there a way to do a full wipe of the phone? externalSD and all things in between. Im just curious.
Click to expand...
Click to collapse
I used the RUU in the development thread, but you have to be s-off.
I used these instructions:
http://forum.xda-developers.com/showthread.php?t=2251800
If you have a custom recovery installed you can go through and format each partition
Sent from my HTC6500LVW using Tapatalk
mlin said:
If you have a custom recovery installed you can go through and format each partition
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Reading some other posts since this thing came out, beware TWRP and wiping internal storage. That is will cause you to have to sideload a .zip to flash. Still prefer TWRP, just careful not to check that box.
chip.hughes said:
Reading some other posts since this thing came out, beware TWRP and wiping internal storage. That is will cause you to have to sideload a .zip to flash. Still prefer TWRP, just careful not to check that box.
Click to expand...
Click to collapse
Well I wiped internal like an idiot. Phone will go to the HTC screen with the red writing at the bottom but thats it. Any help getting things back together would be greatly appreciated.
unstab1e1199 said:
Well I wiped internal like an idiot. Phone will go to the HTC screen with the red writing at the bottom but thats it. Any help getting things back together would be greatly appreciated.
Click to expand...
Click to collapse
That's one way to do it. You'll have to side load a .zip (ROM) to flash. I have to go pick up pecans, so I can't answer a lot of questions if you are not familiar with ADB or command line. I promise it is not hard. Your not the first here to do this, I think Andybones helped someone not long back with this. I googled it for you, there are some youtube videos and here is a link.
http://www.oppoforums.com/threads/how-to-save-your-device-after-a-full-wipe.1907/
You'll need the drivers for this device and all that can be found here:
http://forum.xda-developers.com/showthread.php?t=2417043
look for "root files"
chip.hughes said:
That's one way to do it. You'll have to side load a .zip (ROM) to flash. I have to go pick up pecans, so I can't answer a lot of questions if you are not familiar with ADB or command line. I promise it is not hard. Your not the first here to do this, I think Andybones helped someone not long back with this. I googled it for you, there are some youtube videos and here is a link.
http://www.oppoforums.com/threads/how-to-save-your-device-after-a-full-wipe.1907/
You'll need the drivers for this device and all that can be found here:
http://forum.xda-developers.com/showthread.php?t=2417043
look for "root files"
Click to expand...
Click to collapse
My main problem at the moment is twrp just says starting sideload mode. It never actually enters it. I have Andy's Bonestock v1.1 and renamed it find5.zip, I've tried just running the command to see if would push but, that dosent seem to work either.
unstab1e1199 said:
My main problem at the moment is twrp just says starting sideload mode. It never actually enters it. I have Andy's Bonestock v1.1 and renamed it find5.zip, I've tried just running the command to see if would push but, that dosent seem to work either.
Click to expand...
Click to collapse
Quick guess is drivers. Never having done this myself, I'm thinking the twrp won't react until push starts. I have had to go to device manager (with device plugged in), uninstalled and reinstall the drivers. Sometimes I have had to just move to one of my other computers, that I never connected the phone to, to start fresh. Windows just wouldn't cooperate and let go of some old drivers. Try pm'ing andybones, if you still aren't having any luck by this evening, I'll remote you and look at it if you want me to.
chip.hughes said:
Quick guess is drivers. Never having done this myself, I'm thinking the twrp won't react until push starts. I have had to go to device manager (with device plugged in), uninstalled and reinstall the drivers. Sometimes I have had to just move to one of my other computers, that I never connected the phone to, to start fresh. Windows just wouldn't cooperate and let go of some old drivers. Try pm'ing andybones, if you still aren't having any luck by this evening, I'll remote you and look at it if you want me to.
Click to expand...
Click to collapse
I'm going to try a fresh download of everything and see if that works. adb devices is showing my phone in sideload but, adb sideload then the path to the zip isn't working. I'll figure it out eventually. Thank you for all the help it's really appreciated
unstab1e1199 said:
I'm going to try a fresh download of everything and see if that works. adb devices is showing my phone in sideload but, adb sideload then the path to the zip isn't working. I'll figure it out eventually. Thank you for all the help it's really appreciated
Click to expand...
Click to collapse
If you're using the push command you don't need/want to have the phone in sideload mode. Per TWRP's website normal adv commands don't work in sideload. I couldn't get sideload to work when I sis this but adb push to /data/media/0/ worked fine.
Sent from my HTC6500LVW using Tapatalk
mlin said:
If you're using the push command you don't need/want to have the phone in sideload mode. Per TWRP's website normal adv commands don't work in sideload. I couldn't get sideload to work when I sis this but adb push to /data/media/0/ worked fine.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
ok I have minimal adb and fastboot installed to c:. I have put my rom zip into the adb folder and opened my command from that folder. I have tried sideload to no avail so could u tell me what I need to type in command to push my zip? I have renamed it find5.zip. I have tried to push and sideload on three differnt computers usin different adb and drivers. Guess I have bricked it
unstab1e1199 said:
ok I have minimal adb and fastboot installed to c:. I have put my rom zip into the adb folder and opened my command from that folder. I have tried sideload to no avail so could u tell me what I need to type in command to push my zip? I have renamed it find5.zip. I have tried to push and sideload on three differnt computers usin different adb and drivers. Guess I have bricked it
Click to expand...
Click to collapse
Okay, do this.
1) Boot into recovery
2) Open command from your minimal fastboot/adb folder
3) type adb devices- you should see something like a serial number if your device is recognized, if not, you will need to install the htc drivers.
4) if your device is recognized, type the following command: adb push find5.zip /data/media/0/
5) Disconnect the phone from computer then in recovery go to install and to the location specified above. Your ROM should be there.
This is exactly what I did 2 days ago and it worked. If you can get to recovery, you're not bricked.
I'll be on my comp for a bit so I can help you trouble shoot through this.
mlin said:
Okay, do this.
1) Boot into recovery
2) Open command from your minimal fastboot/adb folder
3) type adb devices- you should see something like a serial number if your device is recognized, if not, you will need to install the htc drivers.
4) if your device is recognized, type the following command: adb push find5.zip /data/media/0/
5) Disconnect the phone from computer then in recovery go to install and to the location specified above. Your ROM should be there.
This is exactly what I did 2 days ago and it worked. If you can get to recovery, you're not bricked.
I'll be on my comp for a bit so I can help you trouble shoot through this.
Click to expand...
Click to collapse
just says no such file or directory in adb. Device is connected and in recovery
---------- Post added at 03:08 AM ---------- Previous post was at 03:00 AM ----------
unstab1e1199 said:
just says no such file or directory in adb. Device is connected and in recovery
Click to expand...
Click to collapse
This is what I get if I push the whole file path. Same when I try to sideload it
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Minimal ADB and Fastboot>adb push /C:/minimal adb and fastboot/find5.zip /dat
a/media
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:\Minimal ADB and Fastboot>
unstab1e1199 said:
just says no such file or directory in adb. Device is connected and in recovery
---------- Post added at 03:08 AM ---------- Previous post was at 03:00 AM ----------
This is what I get if I push the whole file path. Same when I try to sideload it
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Minimal ADB and Fastboot>adb push /C:/minimal adb and fastboot/find5.zip /dat
a/media
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:\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
You don't need to enter the path if your ROM is in the same folder as adb abd this is where you are opening the command prompt.
Here is what I did.
Move my ROM, named rom.zip into "c:\programs (x86)\minimal adb and fastboot\" (or whatever its called exactly).
Then, using Windows explorer, while in that folder, in the address bar typed "cmd" without the quotes. This opens command prompt from the present directory.
Then, simply type adb push rom.zip /data/media/0/
***Also, I had to have the /0/ after media. Without it, I got a no such directory message even though I could see the directory was there.***
mlin said:
You don't need to enter the path if your ROM is in the same folder as adb abd this is where you are opening the command prompt.
Here is what I did.
Move my ROM, named rom.zip into "c:\programs (x86)\minimal adb and fastboot\" (or whatever its called exactly).
Then, using Windows explorer, while in that folder, in the address bar typed "cmd" without the quotes. This opens command prompt from the present directory.
Then, simply type adb push rom.zip /data/media/0/
***Also, I had to have the /0/ after media. Without it, I got a no such directory message even though I could see the directory was there.***
Click to expand...
Click to collapse
I stuck everything in C: for easy reference. Opening my command prompt in that window and just typing amd push find5.zip /data/media/0/says no such file. I've been at this all day have to say out of all he rooted devices I have had this is the worst problem I have came across
unstab1e1199 said:
I stuck everything in C: for easy reference. Opening my command prompt in that window and just typing amd push find5.zip /data/media/0/says no such file. I've been at this all day have to say out of all he rooted devices I have had this is the worst problem I have came across
Click to expand...
Click to collapse
Weird. The "no such file" message makes it sound like your ROM is not in the same folder or isn't named as you've indicated.
mlin said:
Weird. The "no such file" message makes it sound like your ROM is not in the same folder or isn't named as you've indicated.
Click to expand...
Click to collapse
Would it make a difference if I downloaded the rom on another pc and copied it to a external drive then copied it back onto this pc? I am in the process of a fresh download onto this pc to see if it helps. Seems all the files are in the zip I copied though.
unstab1e1199 said:
Would it make a difference if I downloaded the rom on another pc and copied it to a external drive then copied it back onto this pc? I am in the process of a fresh download onto this pc to see if it helps. Seems all the files are in the zip I copied though.
Click to expand...
Click to collapse
Just to be clear, you definitely have find5.zip in the same folder as adb.exe?
Try this:
adb push find5.zip /data/media/0/find5.zip
mlin said:
Just to be clear, you definitely have find5.zip in the same folder as adb.exe?
Try this:
adb push find5.zip /data/media/0/find5.zip
Click to expand...
Click to collapse
Yeah I copied the rom to the exact folder. I am gonna have to get in the bed I gotta be at work soon. I'll try this tomorrow with a fresh rom download. Do I need to be on any specific screen in twrp other than the home screen?
unstab1e1199 said:
Yeah I copied the rom to the exact folder. I am gonna have to get in the bed I gotta be at work soon. I'll try this tomorrow with a fresh rom download. Do I need to be on any specific screen in twrp other than the home screen?
Click to expand...
Click to collapse
I don't believe so but I'll try it on my phone to confirm. I'll post here when I find out. Good luck getting this figured out, sorry I wasn't able to help you get it fixed. Very bizarre.
Hi guys. I have problem with update my phone to 4.3 because I have error.
Code:
Pushing system.ext4 to (this process will take a while)...
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.
-------------------------------------------------------------------------------
ERROR: failed to push some files, make sure you have enough free space then try
again. Press any key to exit
Quite obvious ol' chap, try freeing some space either on the computer or the phone.
Sorry if I am appearing a bit condescending to you.
I flash phone to 4.1.2 and root it and I format sd card. My computer is freshly after format so i have space on my phone and computer.
PS. Sorry for my english but I'm still learning the language because I'm from Poland kurwa mać!!
Ok make sure there are no other usb devices plugged into your computer at the same time, make sure you have full root, make sure you have busybox
Sent from my C2004 using xda app-developers app
I have full root for 100 % , To ports usb i have only connected mouse and keyboard. I installed busybox to do root but I uninstall when I finished rooting
ref
make sure you have full root access , i think that's the problem
Fikcyjny said:
I have full root for 100 %
Click to expand...
Click to collapse
Read this. I have full root, for example I uninstall systems apps (few at this same time) and I dont have restart
ref
adb isn't recognizing the push command and it's just displaying help instead. Which language are your OS? For debugging, open root.bat with notepad and remove the first line (@echo off), save and then run again. This time the console will show more details, copy all and post here so I can help...
Code:
C:\DOTELE~1\NICKIR~1>echo Pushing system.ext4 to (this process will take a whil
e)...
Pushing system.ext4 to (this process will take a while)...
C:\DOTELE~1\NICKIR~1>tools\adb.exe push system.ext4
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:\DOTELE~1\NICKIR~1>if not 1 == 0 goto err_push
C:\DOTELE~1\NICKIR~1>echo ------------------------------------------------------
-------------------------
-------------------------------------------------------------------------------
C:\DOTELE~1\NICKIR~1>echo ERROR: failed to push some files, make sure you have e
nough free space then try again. Press any key to exit
ERROR: failed to push some files, make sure you have enough free space then try
again. Press any key to exit
C:\DOTELE~1\NICKIR~1>pause 1>nul
Language is Polish .
That's really weird, your command prompt is using paths in DOS style, which Windows version are you using? Meanwhile, try extracting the root tool in C:\ and rename the folder from "NickiRoot" to something very small, like "NR", then try again and see if works...
Make sure that other adb processes are not running. Like an android emulator...
Sometimes I have weird errors because I have installed BlueStacks.
Rename folder didn't work. I have Windows XP Proffessional
WOW, it's time to upgrade your OS (even Microsoft ended its support). If you're using NickiRoot 1.1 or newer, that's your problem. To cleanup my code I dropped a ugly workaround and the script won't work in Windows XP anymore. The last version compatible with it is NickiRoot 1.0.1, anything newer won't work in Windows XP and there's no reason I should care in supporting it anymore
I have same problem..
I'm using windows xp ..
Hello
I'm having problems following the post [BOOTLOADER] 2nd-Bootloader/Recovery unlock process for KFire 2 [TWRP 2.6.3.0]
I tried several ways during several days but I'm totally stuck, I don't know what i should do more. My KF is 10.5.0, from 2012, not HD, without camera, so I'm sure that is KF2, second generation. And I'm working with Mac OSx.
Here what i did;
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery >>> i cannot make it
myname-MacBook-Pro:~ myname$ adb pull /dev/block/mmcblk0boot0 failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
So i didn't make backup and go direct to STEP 2 and 3.
I placed all the files on my device in the sdcard area.
STEP 3. Install the stack override in /system: It looked it worked, i used factory cable;
myname-MacBook-Pro:~ myname$ adb push stack/download
Android Debug Bridge version 1.0.29
-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 command 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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
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 default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem 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 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.
Silvia-Kozakura-no-MacBook-Pro:~ silviakozakura$ adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
And then the STEP 4, where I'm stuck "Flash the OLD bootloader, new otter2-freedom-boot.img and TWRP recovery" I used factory cable to enter in Fastboot mode but always i get this error;
myname-MacBook-Pro:~ myname$ fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
error: cannot load 'otter2-u-boot-prod-10.2.4.bin'
- Cannot load any file, I put all the files at sdcard/download, I don't know what i did wrong.
I'm willing to pay money to who will help me.
KindleRooteado said:
Hello
I'm having problems following the post [BOOTLOADER] 2nd-Bootloader/Recovery unlock process for KFire 2 [TWRP 2.6.3.0]
I tried several ways during several days but I'm totally stuck, I don't know what i should do more. My KF is 10.5.0, from 2012, not HD, without camera, so I'm sure that is KF2, second generation. And I'm working with Mac OSx.
Here what i did;
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery >>> i cannot make it
myname-MacBook-Pro:~ myname$ adb pull /dev/block/mmcblk0boot0 failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
So i didn't make backup and go direct to STEP 2 and 3.
I placed all the files on my device in the sdcard area.
STEP 3. Install the stack override in /system: It looked it worked, i used factory cable;
myname-MacBook-Pro:~ myname$ adb push stack/download
Android Debug Bridge version 1.0.29
-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 command 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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
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 default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem 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 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.
Silvia-Kozakura-no-MacBook-Pro:~ silviakozakura$ adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
And then the STEP 4, where I'm stuck "Flash the OLD bootloader, new otter2-freedom-boot.img and TWRP recovery" I used factory cable to enter in Fastboot mode but always i get this error;
myname-MacBook-Pro:~ myname$ fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
error: cannot load 'otter2-u-boot-prod-10.2.4.bin'
- Cannot load any file, I put all the files at sdcard/download, I don't know what i did wrong.
I'm willing to pay money to who will help me.
Click to expand...
Click to collapse
You have to keep the files on your PC, not the Kindle. Execute the commands from where you kept the files. I'll write you a full tutorial when I have time.
Sent from my device running CyanogenMod 11
SafinWasi said:
You have to keep the files on your PC, not the Kindle. Execute the commands from where you kept the files. I'll write you a full tutorial when I have time.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
That makes sense, thank you! I will try
Well, now I don't understand anything, I'm making the same i did yestarday but without the same results, with different errors.
I've relocated the factory settings in KF and I checked if the root is ok.
So now says;
STEP 1. Backup
myname-no-MacBook-Pro:~ myname$ adb pull /dev/block/mmcblk0boot0
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
STEP 3. Install the stack override in /system
myname-no-MacBook-Pro:~ myname$ adb push stack/download
Android Debug Bridge version 1.0.29
-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 command 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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
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 default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem 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 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.
myname-no-MacBook-Pro:~ myname$ adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"error: device not found
myname-no-MacBook-Pro:~ myname$ adb shell su -c "dd if=/download/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
error: device not found
myname-no-MacBook-Pro:~ myname$ adb shell su -c "dd if=/download/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
error: device not found
I tryed to run "stack" placed on sdcard of the device and placed on my computer, nothing worked.
I think is better don't do anything else, i will wait for help...
KindleRooteado said:
Well, now I don't understand anything, I'm making the same i did yestarday but without the same results, with different errors.
I've relocated the factory settings in KF and I checked if the root is ok.
So now says;
(post edited due to large size_
I tryed to run "stack" placed on sdcard of the device and placed on my computer, nothing worked.
I think is better don't do anything else, i will wait for help...
Click to expand...
Click to collapse
Okay,first off,download the files to your PC,not the Kindle. Connect the Kindle to your PC with USB debugging enabled. Then,open a command window and cd to the directory where you kept the files.
Now issue the following commands to backup partitions:
Code:
adb pull /dev/block/mmcblk0boot0
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/boot
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/system
Note:If you get "permission denied" error,use the following command:
Code:
adb remount
If you still get the error,ensure that you have root.
Next,install the stack override:
Code:
adb push stack /sdcard/
adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
And flash the old bootloader with 2nd bootloader and Team Win Recovery: (use factory cable to boot into fastboot)
Code:
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.0-recovery.img
fastboot -i 0x1949 reboot
SafinWasi said:
Okay,first off,download the files to your PC,not the Kindle. Connect the Kindle to your PC with USB debugging enabled. Then,open a command window and cd to the directory where you kept the files.
Now issue the following commands to backup partitions:
Code:
adb pull /dev/block/mmcblk0boot0
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/boot
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/system
Note:If you get "permission denied" error,use the following command:
Code:
adb remount
If you still get the error,ensure that you have root.
Next,install the stack override:
Code:
adb push stack /sdcard/
adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
And flash the old bootloader with 2nd bootloader and Team Win Recovery: (use factory cable to boot into fastboot)
Code:
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.0-recovery.img
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Hello, I really appreciate your help. I followed your instructions but I'm still stuck... I got:
Permission denied
remount failed: Operation not permitted
And Superuser is enabled for sure.
{
"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"
}
Can you try mounting system from ES file explorer?
Sent from my device running CyanogenMod 11
SafinWasi said:
Can you try mounting system from ES file explorer?
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
thanks, i will do tomorrow
Still doesn't work... I mounted system with ES file explorer and after I tried again to do the backup:
Code:
Last login: Sat Sep 6 09:24:20 on console
myname-no-MacBook-Pro:~ myname$ cd desktop
myname-no-MacBook-Pro:desktop myname$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
myname-no-MacBook-Pro:desktop myname$ ./adb pull /dev/block/mmcblk0boot0
-bash: ./adb: No such file or directory
myname-no-MacBook-Pro:desktop myname$ adb remount
remount failed: Operation not permitted
myname-no-MacBook-Pro:desktop myname$ ./adb remount
-bash: ./adb: No such file or directory
myname-no-MacBook-Pro:desktop myname$
KindleRooteado said:
Still doesn't work... I mounted system with ES file explorer and after I tried again to do the backup:
Code:
Last login: Sat Sep 6 09:24:20 on console
myname-no-MacBook-Pro:~ myname$ cd desktop
myname-no-MacBook-Pro:desktop myname$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
myname-no-MacBook-Pro:desktop myname$ ./adb pull /dev/block/mmcblk0boot0
-bash: ./adb: No such file or directory
myname-no-MacBook-Pro:desktop myname$ adb remount
remount failed: Operation not permitted
myname-no-MacBook-Pro:desktop myname$ ./adb remount
-bash: ./adb: No such file or directory
myname-no-MacBook-Pro:desktop myname$
Click to expand...
Click to collapse
Ok,try running "adb root" and then issue the commands
I think where can be my mistake. When I installed the android sdk adb I never got the list of my devices, my KF2 didn't appear, but i didn't think that was so important...
Then i thought that i didn't need to do anything else to connect the Kindle to my computer with USB debugging enabled, sorry. Now I'm trying to do USB debugging enabled following this guide: https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
And again I'm stuck. I don't understand the meaning of this errors, any idea? I'm working with mac OSX, no Windows PC available in 10.424 Km...
Code:
myname-no-MacBook-Pro:SDK tools myname$
myname-no-MacBook-Pro:SDK tools myname$ ./android update adb
Unable to access jarfile /Users/myname/desktop/SDK tools/archquery.jar
Unable to access jarfile /Users/myname/desktop/SDK tools/archquery.jar
Exception in thread "Thread-1" java.lang.NoClassDefFoundError: com/android/utils/ILogger
Caused by: java.lang.ClassNotFoundException: com.android.utils.ILogger
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
SafinWasi said:
Ok,try running "adb root" and then issue the commands
Click to expand...
Click to collapse
I'm a really pain, sorry.
I guest i cannot run any adb command until l fix the USB debugging enabled.
Code:
myname-no-MacBook-Pro:desktop myname$ adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adbd cannot run as root in production builds
I think i finally enabled USB debugging, but I'm not sure. I have made my device appears in the list, but the other .adb commands are not working still. The fact that my device appears in the list is a good sign or not?
Code:
myname-no-MacBook-Pro:desktop myname$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
D026A0A02494022P device
myname-no-MacBook-Pro:desktop myname$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
myname-no-MacBook-Pro:desktop myname$ adb remount
remount failed: Operation not permitted
myname-no-MacBook-Pro:desktop myname$ adb root
adbd cannot run as root in production builds
myname-no-MacBook-Pro:desktop myname$
KindleRooteado said:
I think i finally enabled USB debugging, but I'm not sure. I have made my device appears in the list, but the other .adb commands are not working still. The fact that my device appears in the list is a good sign or not?
Code:
myname-no-MacBook-Pro:desktop myname$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
D026A0A02494022Pdevice
myname-no-MacBook-Pro:desktop myname$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
myname-no-MacBook-Pro:desktop myname$ adb remount
remount failed: Operation not permitted
myname-no-MacBook-Pro:desktop myname$ adb root
adbd cannot run as root in production builds
myname-no-MacBook-Pro:desktop myname$
Click to expand...
Click to collapse
Its definitely a good sign. I'll keep digging.
Sent from my device running CyanogenMod 11
---------- Post added at 08:43 PM ---------- Previous post was at 08:39 PM ----------
OK,found something. Try this:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.IMG"
adb pull /Edvard/boot0block.IMG
Try this with other commands as well. And if it prompts SuperSU,say grant.
Sent from my device running CyanogenMod 11
SafinWasi said:
Its definitely a good sign. I'll keep digging.
Sent from my device running CyanogenMod 11
---------- Post added at 08:43 PM ---------- Previous post was at 08:39 PM ----------
OK,found something. Try this:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.IMG"
adb pull /Edvard/boot0block.IMG
Try this with other commands as well. And if it prompts SuperSU,say grant.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Thank you very much again. The first command works, it asked me to grant SuperSu and i did, but nothing else.
Is Edvard/boot0block.IMG a file i have to download?
Code:
myname-no-MacBook-Pro:~ myname$ cd desktop
myname-no-MacBook-Pro:desktop myname$ adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.IMG"
4096+0 records in
4096+0 records out
2097152 bytes transferred in 0.459 secs (4568958 bytes/sec)
myname-no-MacBook-Pro:desktop myname$ adb pull /Edvard/boot0block.IMG
[B]remote object '/Edvard/boot0block.IMG' does not exist
[/B]myname-no-MacBook-Pro:desktop myname$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
myname-no-MacBook-Pro:desktop myname$
Why it's so complicated?
KindleRooteado said:
Thank you very much again. The first command works, it asked me to grant SuperSu and i did, but nothing else.
Is Edvard/boot0block.IMG a file i have to download?
Code:
myname-no-MacBook-Pro:~ myname$ cd desktop
myname-no-MacBook-Pro:desktop myname$ adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.IMG"
4096+0 records in
4096+0 records out
2097152 bytes transferred in 0.459 secs (4568958 bytes/sec)
myname-no-MacBook-Pro:desktop myname$ adb pull /Edvard/boot0block.IMG
[B]remote object '/Edvard/boot0block.IMG' does not exist
[/B]myname-no-MacBook-Pro:desktop myname$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
myname-no-MacBook-Pro:desktop myname$
Why it's so complicated?
Click to expand...
Click to collapse
Lol,it should be:
adb pull /sdcard/boot0block.img
SafinWasi said:
Lol,it should be:
adb pull /sdcard/boot0block.img
Click to expand...
Click to collapse
Lol, I am about to give up.
The last command that you give me worked but again I couldn't make backup, cause i got the same error.
Silvia-Kozakura-no-MacBook-Pro:~ silviakozakura$ adb pull /sdcard/boot0block.img6366 KB/s (2097152 bytes in 0.321s)
So, i had the brilliant idea to skip that step and go ahead to install the stack and then to flash bootloader.
And now I'm stuck at the second command, my computer is sending 'boot' for 40 minutes, not sure if this is normal, but i suppose it is not...
I'm going to sleep, tomorrow i will see what to do or not. Thanks for your time.
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb pull /sdcard/boot0block.img
6245 KB/s (2097152 bytes in 0.327s)
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb push stack /sdcard/
204 KB/s (4096 bytes in 0.019s)
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
0+1 records in
0+1 records out
4096 bytes transferred in 0.002 secs (2048000 bytes/sec)
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 0.057s]
finished. total time: 0.186s
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
sending 'boot' (8153 KB)...
KindleRooteado said:
Lol, I am about to give up.
The last command that you give me worked but again I couldn't make backup, cause i got the same error.
Silvia-Kozakura-no-MacBook-Pro:~ silviakozakura$ adb pull /sdcard/boot0block.img6366 KB/s (2097152 bytes in 0.321s)
So, i had the brilliant idea to skip that step and go ahead to install the stack and then to flash bootloader.
And now I'm stuck at the second command, my computer is sending 'boot' for 40 minutes, not sure if this is normal, but i suppose it is not...
I'm going to sleep, tomorrow i will see what to do or not. Thanks for your time.
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb pull /sdcard/boot0block.img
6245 KB/s (2097152 bytes in 0.327s)
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb push stack /sdcard/
204 KB/s (4096 bytes in 0.019s)
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
0+1 records in
0+1 records out
4096 bytes transferred in 0.002 secs (2048000 bytes/sec)
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 0.057s]
finished. total time: 0.186s
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
sending 'boot' (8153 KB)...
Click to expand...
Click to collapse
What the… it should not ta take more than 10 seconds
Sent from my device running CyanogenMod 11
Hi, i was trying to to restore my kindle to 10.2.3 firmware cause i was told that it was the only way to flash a new rom and something didn't work.
Now shows this red triangle all the time. I cannot reboot, restore and my computer doesn't recognizes it.
Please help me, what i can do.
(It can enter to fastboot)