Having trouble flashing TWRP to HTC M8 - One (M8) Q&A, Help & Troubleshooting

Hello i hope im posting this in the right place.
First let me explain that i am very much NOOB when it comes to Android rooting, I have always been an IOS user untill recently
when i seen the light and decided to move to Android.
So as for the problem, I have unlocked the Bootloader ( was simple enough), but now when i try flashing TWRP the phone will try to boot, then all that happens is a battery symbol starts falshing on screen and the phone is completely unresponsive. i assume this is "soft bricked", i am able to recover by unplugging the usb and holding the power buttons. I have tried many different TWRP versions
all with the same outcome.
Im not sure what info you will need in order to help but i will start with * Running Android 5.0.2
* Phone was originally O2uk, and now unlocked on 3 ireland
* Sense Version 6.0
any help would be much appreciated, thanks in advanced
Mick

The question is more how you flashed it ?
What exact command did you use ?

Ok so what i did was entered the command- "adb devices" the device is connected
next was "adb reboot bootloader" and my phone entered fastboot menu
finally was " fastboot flash recovery (filename)"
then on the phone selected "HBOOT" then "RECOVERY"
Mick

Oke that seems good, just making sure you didn't flash it to the boot partition !
Can you post another command output ?
Fastboot getvar all
Then post the full list except the serial and imei

bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.11.206.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 4107a7cf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!

Any ideas how i can fix this problem or is it something im doing wrong?

Mikey899 said:
Any ideas how i can fix this problem or is it something im doing wrong?
Click to expand...
Click to collapse
Yup definitely going the wrong route as you have the M8s and NOT the M8 !!!
http://forum.xda-developers.com/showthread.php?t=3114245
Have a read there mate
Roms for the M8 also don't work on the M8s, actually it's pretty unsupported. Also make sure to create a full stock backup once you flashed the correct TWRP for the M8s so you can go back to stock easily !!!

Now that was very NOOB of me, thanks man, will have a read and let you know how i get on

ok so i have had a good read and im still unclear on what method i need to use to flash the TWRP for the m8s

Mikey899 said:
ok so i have had a good read and im still unclear on what method i need to use to flash the TWRP for the m8s
Click to expand...
Click to collapse
Just fastboot flash it, you only need the correct TWRP (the one from that thread, it's modified to work with the M8s)
If that doesn't work you have to use the htc_fastboot files from that thread and fastboot flash it again

yes i was thinking that and i tried it, but rather than load it onto the device as it usually would, this is what i got
"adb flash recovery twrp-recovery-2.8.6.0-m8s-qlul.img"
Android Debug Bridge version 1.0.31
-a - directs adb to listen on all interfaces for a connection
-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 <specific device> - directs command to the device or emulator with the given
serial number or qualifier. 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.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
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 devices.
device commands:
adb push [-p] <local> <remote>
- copy file/dir to device
('-p' to display the transfer progress)
adb pull [-p] [-a] <remote> [<local>]
- copy file/dir from device
('-p' to display the transfer progress)
('-a' means copy timestamp and mode)
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 --list - list all forward socket connections.
the format is a list of lines with the following format:
<serial> " " <local> " " <remote> "\n"
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 forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fails
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-d] [-s] [--algo <algorithm name> --key <hex-encoded key> --iv <hex-encoded iv>] <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)
('-d' means allow version code downgrade)
('-s' means install on SD card instead of internal 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] [-obb|-noobb] [-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.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default
is noobb.)
(-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 get-devpath - prints: <device-path>
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.

i also tried the htc_fastboot.exe and when i run it i get "AdbWinApi.dll missing"

You don't "run" the fastboot file. And "adb flash recovery" can't work either
The command =
Fastboot flash recovery recovery filename
And the phone is in the bootloader -fastboot usb mode
You put the TWRP in the fastboot folder and then open a command prompt there. Then type the command

Thanks for all your help man, i have managed to root thanks to you. sorry for the inconvenience
Mick

Mikey899 said:
Thanks for all your help man, i have managed to root thanks to you. sorry for the inconvenience
Mick
Click to expand...
Click to collapse
Cool, no worries.

Related

adb help please

alright i deleted htc sync and now for some reason i cant mount my sdcard. so i need to push via adb.
i cant figure out the commands to push a file to sdcard any help please.
im on mac but codes should be about the same
or how can i get to the setting and reset them where is lets you choose charge phone,mount.tether extc
BigBallin said:
alright i deleted htc sync and now for some reason i cant mount my sdcard. so i need to push via adb.
i cant figure out the commands to push a file to sdcard any help please.
im on mac but codes should be about the same
or how can i get to the setting and reset them where is lets you choose charge phone,mount.tether extc
Click to expand...
Click to collapse
I can help with the first part;
Syntax: adb push source destination
Example:
adb push file.apk /sdcard
ive been doin that. and it says adb not found.
or i get this
Code:
Last login: Wed Oct 27 15:57:03 on ttys000
Laptop-5:~ kgirouex$ cd /Users/kgirouex/Documents/android/sdk/tools/
Laptop-5:tools kgirouex$ ./adb push apple.zip/sdcard
Android Debug Bridge version 1.0.25
-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
envivornment 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] <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 reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
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.
Laptop-5:tools kgirouex$
I don't know much about MAC but did you put the adb in the tools folder and direct the adb command from there for example in Windows its like this C:/Android/tools
sent through my Special Edition White HTC EVO 4g while in the ****ter
ins0dus said:
I don't know much about MAC but did you put the adb in the tools folder and direct the adb command from there for example in Windows its like this C:/Android/tools
sent through my Special Edition White HTC EVO 4g while in the ****ter
Click to expand...
Click to collapse
ya thats how i always run adb is in the tools folder. and the things i need to push are there also
I'm on the phone so the formatting of your post is jacked up, but it looks like you might be missing a space between your source and destination.
Sent from my blah blah blah blah
fachadick said:
I'm on the phone so the formatting of your post is jacked up, but it looks like you might be missing a space between your source and destination.
Sent from my blah blah blah blah
Click to expand...
Click to collapse
thanks. it supposed to read adb push apple.zip /sdcard i was doing the space after the slash and not before.
damnit, now it says cant push because /sdcard is a directory
redid it and pushed to sdcard/download and it worked wtf
Good! Don't you just love that feeling when everything runs smooth.. I hate all the troubleshooting bs
sent through my Special Edition White HTC EVO 4g while in the ****ter
Yeah, nice!
Sent from my blah blah blah blah

SDK manager issues...?

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?

[Q] How do you do a full erase of the phone, (eg: externalSD, etc)

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.

Helpe Me Please !! I delete my rom.

Hello good afternoon, yesterday I tried to change my rom via sdcard on my m7 32gb htc one however he has failed and erased the rom and not open more access to his sdcard to try to correct the mistake he is with root and my biggest doubt I do I return everything to normal? I'm watching videos, reading tutorials all night and nothing helps me what I can really do to put the rom on it again?
Ps: this happened after I sent the rom install google edition by twr recovery and gave error when I start my mobile al it appears google and gets into an infinite boot.
Thank you thank you for all the help.
liufong said:
Hello good afternoon, yesterday I tried to change my rom via sdcard on my m7 32gb htc one however he has failed and erased the rom and not open more access to his sdcard to try to correct the mistake he is with root and my biggest doubt I do I return everything to normal? I'm watching videos, reading tutorials all night and nothing helps me what I can really do to put the rom on it again?
Ps: this happened after I sent the rom install google edition by twr recovery and gave error when I start my mobile al it appears google and gets into an infinite boot.
Thank you thank you for all the help.
Click to expand...
Click to collapse
In twrp go in to menu Sideload
Connect your phone to PC
Now ADB should recognize it in sideload mode
check with command adb sideload in command prompt on PC
you can puch a rom like CM11 because its small in size
the comment is
ADB sideload filename.zip
One its transferred to phone will install automatically
You can google for ADB or sideload if you dont understand it.
please do not get mad
desiwizard said:
In twrp go in to menu Sideload
Connect your phone to PC
Now ADB should recognize it in sideload mode
check with command adb sideload in command prompt on PC
you can puch a rom like CM11 because its small in size
the comment is
ADB sideload filename.zip
One its transferred to phone will install automatically
You can google for ADB or sideload if you dont understand it.
Click to expand...
Click to collapse
do you have a comands in the terminal pass for me ? or a mini tutorial i'am new htc user i have various rom in my pc i can upload in the cellphone anyone ?
liufong said:
do you have a comands in the terminal pass for me ? or a mini tutorial i'am new htc user i have various rom in my pc i can upload in the cellphone anyone ?
Click to expand...
Click to collapse
Open a command prompt in the directory that contains ADB.
Boot your phone into TWRP recovery and connect a USB cable. Do not enter ADB Sideload.
From the command prompt, type 'adb devices' and after a few seconds you should see your phone in the list of connected devices. If the list is blank, you may not have the proper drivers installed for your phone. Assuming you do see a device listed, continue to the next step.
Place a copy of the ROM you wish to install in the same directory from above, naming it ROM.zip
Type the following command: 'adb push ROM.zip /sdcard/ROM.zip' and hit Enter. Depending on ROM size, it may take up to 5 minutes to complete. You will see a message when it completes.
Now unplug your phone, go to the Install option in TWRP, and select ROM.zip.
why?
NotATreoFan said:
Open a command prompt in the directory that contains ADB.
Boot your phone into TWRP recovery and connect a USB cable. Do not enter ADB Sideload.
From the command prompt, type 'adb devices' and after a few seconds you should see your phone in the list of connected devices. If the list is blank, you may not have the proper drivers installed for your phone. Assuming you do see a device listed, continue to the next step.
Place a copy of the ROM you wish to install in the same directory from above, naming it ROM.zip
Type the following command: 'adb push ROM.zip /sdcard/ROM.zip' and hit Enter. Depending on ROM size, it may take up to 5 minutes to complete. You will see a message when it completes.
Now unplug your phone, go to the Install option in TWRP, and select ROM.zip.
Click to expand...
Click to collapse
after executing the last line of the command you gave me "adb push Rom.zip / sdcard / ROM.zip it appears in the what I'm doing wrong screen?:silly:
Android Debug Bridge version 1.0.31
-a - directs adb to listen on all interfaces for a c
onnection
-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.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
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 --list - list all forward socket connections.
the format is a list of lines with the followin
g format:
<serial> " " <local> " " <remote> "\n"
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 forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fail
s
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
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] [-obb|-noobb] [-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 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.)
(-obb|-noobb enable/disable backup of any insta
lled apk expansion
(aka .obb) files associated with each applic
ation; the default
is noobb.)
(-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.
You must have typed something wrong in the cmd when you entered it.
Code:
adb push ROM.zip /sdcard/ROM.zip
The Rom.zip needs to be in the same folder that has adb.exe most folks use their platform tools folder.
You also need to open the cmd window from that same folder.
If you don't have that folder you can use the attached folder.
vish
BD619 said:
The Rom.zip needs to be in the same folder that has adb.exe most folks use their platform tools folder.
You also need to open the cmd window from that same folder.
If you don't have that folder you can use the attached folder.
Click to expand...
Click to collapse
I used the folder that you sent me and put the rom file inside it follows the photos below of the process I'm doing if possible please take a look, see if I'm doing something wrong.
thank you!
liufong said:
I used the folder that you sent me and put the rom file inside it follows the photos below of the process I'm doing if possible please take a look, see if I'm doing something wrong.
thank you!
Click to expand...
Click to collapse
You don't have spaces as I typed above. And you typed ROM2.zip, but the file is named ROM.zip.
adb push ROM.zip /sdcard/ROM.zip
up
NotATreoFan said:
You don't have spaces as I typed above. And you typed ROM2.zip, but the file is named ROM.zip.
adb push ROM.zip /sdcard/ROM.zip
Click to expand...
Click to collapse
I tried the method sideload it up al the rom.zip with the name sideload.zip sent install and gave error sent clean partitions
Now I saw what I was doing wrong were actually spaces, now I did the "adb devices" command does not appear and nothing will I have to update some drive? thank you!
liufong said:
I tried the method sideload it up al the rom.zip with the name sideload.zip sent install and gave error sent clean partitions
Now I saw what I was doing wrong were actually spaces, now I did the "adb devices" command does not appear and nothing will I have to update some drive? thank you!
Click to expand...
Click to collapse
Try using different USB port, USB 3.0 does give problems some time
liufong said:
I tried the method sideload it up al the rom.zip with the name sideload.zip sent install and gave error sent clean partitions
Now I saw what I was doing wrong were actually spaces, now I did the "adb devices" command does not appear and nothing will I have to update some drive? thank you!
Click to expand...
Click to collapse
You have to turn off Sideload. Normal adb commands do not work in that mode. Turn your phone off, then boot into recovery and try again.
I borked my phone in much the same way when I tried to update to kitkat with a crappy hotel Wi-Fi. I ended up having to fastboot flash a RUU. Sideload wasn't working for me.
@NotATreoFan
Why the extra Rom.zip at the end of the command? I have always used adb push Rom.zip /sdcard/ without problems...just curious if I'm missing something.
adb push Rom.zip /sdcard/Rom.zip
BD619 said:
@NotATreoFan
Why the extra Rom.zip at the end of the command? I have always used adb push Rom.zip /sdcard/ without problems...just curious if I'm missing something.
adb push Rom.zip /sdcard/Rom.zip
Click to expand...
Click to collapse
You probably don't need it. Just the way I've always done it.
You can do it both ways. The one way just allows you to push the file to the phone but save it under a different name ( adb push rom.zip /sdcard/myrom.zip)
cmlusco said:
You can do it both ways. The one way just allows you to push the file to the phone but save it under a different name ( adb push rom.zip /sdcard/myrom.zip)
Click to expand...
Click to collapse
Did not know that
Thanks for all !
super thanks for help guys, everything worked out here and conssegui install miui'm trying to google rom edition but this is already failing but alas another story, thank you very much for the help anyway!
liufong said:
super thanks for help guys, everything worked out here and conssegui install miui'm trying to google rom edition but this is already failing but alas another story, thank you very much for the help anyway!
Click to expand...
Click to collapse
Just to confirm you have a verizon HTC one and are trying to install a ROM specifically made for the verizon HTC one?
no
no my smartphone is international xD

Problem with Update to 4.3

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 ..

Categories

Resources