Database Develop

help - flashed kernel and now stuck at load screen

Hi everyone.
I something of a noob but have unlocked/rooted/flashed several roms in the past but this time I have made a mess of it.
I unlocked my phone then flasked CWM revovery ok but was not getting anywhere with rooting it. So for some reason i flashed the kernel and now it is stuck on the white htc screen with some red text stating this is a htc developer rom please dont use without htc permission etc.
All I am able to do now is down/power button boot into bootloader and get into recovery.
I don't have any rom saved on the SD card.
I checked other solutions on this site all day yesterday and nothing seemed to work for me.
Thanks for the help in advance.

You should be able to download a rom to your pic, mount the internal sd in recovery and push the rom to it. Then wipe and flash. I'm not familiar with the phone or cwm, but that's a method used in the past.

if you have an otg cable you can mount external storage in recovery and flash from there...

metalfan78 said:
You should be able to download a rom to your pic, mount the internal sd in recovery and push the rom to it. Then wipe and flash. I'm not familiar with the phone or cwm, but that's a method used in the past.
Click to expand...
Click to collapse
I tried to mount sd card
in CWM it gives me 'error mounting /sdcard'
What next?

I don't know what kernel you flashed, since there are no kernels out for this device, but you need a otg cable with a usb drive stick to put the new rom zip on to flash in recovery, or your other options are to use the android sdk(adb) to push the rom zip to your storage, or you could adb sideload the rom zip.
to adb push plug up to your pc & type this in the cmd prompt
Code:
adb push nameofROM.zip /sdcard/nameofROM.zip
sideload is an option in cwm, just start it from recovery & connect to your pc & in your cmd prompt type
Code:
adb sideload (path to your rom.zip)

rayford85 said:
I don't know what kernel you flashed, since there are no kernels out for this device, but you need a otg cable with a usb drive stick to put the new rom zip on to flash in recovery, or your other options are to use the android sdk(adb) to push the rom zip to your storage, or you could adb sideload the rom zip.
to adb push plug up to your pc & type this in the cmd prompt
Code:
adb push nameofROM.zip /sdcard/nameofROM.zip
sideload is an option in cwm, just start it from recovery & connect to your pc & in your cmd prompt type
Code:
adb sideload (path to your rom.zip)
Click to expand...
Click to collapse
I got 'adb is not a recognised internal or external command

trenzador said:
I got 'adb is not a recognised internal or external command
Click to expand...
Click to collapse
try using google search to find out how to properly install the android sdk, your gonna need it. In the mean time take this & extract it, open your cmd prompt inside the folder, also put the rom.zip in that folder & it will work. https://dl.dropbox.com/u/31377968/adb_files.zip

rayford85 said:
try using google search to find out how to properly install the android sdk, your gonna need it. In the mean time take this & extract it, open your cmd prompt inside the folder, also put the rom.zip in that folder & it will work. https://dl.dropbox.com/u/31377968/adb_files.zip
Click to expand...
Click to collapse
great....but do i need to get android sdk working before the rest of the method or are you saying i will need it one day in the future maybe?
cheers by the way.

trenzador said:
great....but do i need to get android sdk working before the rest of the method or are you saying i will need it one day in the future maybe?
cheers by the way.
Click to expand...
Click to collapse
your gonna need it in the future, just use my files for now to get your device running again

rayford85 said:
your gonna need it in the future, just use my files for now to get your device running again
Click to expand...
Click to collapse
ok sorry one more question..
what do you mean open the cmd inside the folder? is there a file to open in the folder or i just open the fo....you get the picture.

trenzador said:
ok sorry one more question..
what do you mean open the cmd inside the folder? is there a file to open in the folder or i just open the fo....you get the picture.
Click to expand...
Click to collapse
open the folder, hold shift & mouse right click, choose open command prompt here.

i did what you said and i got this
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:\Users\Leon\Desktop\ADB GUY\adb_files>

trenzador said:
i did what you said and i got this
C:\Users\Leon\Desktop\ADB GUY\adb_files>
Click to expand...
Click to collapse
Use 'adb shell' then adb sideload I think

MacHackz said:
Use 'adb shell' then adb sideload I think
Click to expand...
Click to collapse
sorry i gotta ask more, abd shell then adbsideload in the same command or what?
i got another wall of text bigger than last time.

trenzador said:
sorry i gotta ask more, abd shell then adbsideload in the same command or what?
i got another wall of text bigger than last time.
Click to expand...
Click to collapse
no need to shell, easiest way for me is to start sideload from recovery, once its started on your pc type adb sideload then drag the rom.zip into the cmd prompt & hit enter, it should do the rest.

rayford85 said:
no need to shell, easiest way for me is to start sideload from recovery, once its started on your pc type adb sideload then drag the rom.zip into the cmd prompt & hit enter, it should do the rest.
Click to expand...
Click to collapse
the good news is that worked in part, by that i mean it did load but on the phone i got this...
finding update package
opening update package
E: can't open /tmp/update.zip
(bad)
Installation aborted

trenzador said:
the good news is that worked in part, by that i mean it did load but on the phone i got this...
finding update package
opening update package
E: can't open /tmp/update.zip
(bad)
Installation aborted
Click to expand...
Click to collapse
redownload a rom like renovate for example and try again.

rayford85 said:
redownload a rom like renovate for example and try again.
Click to expand...
Click to collapse
I think I have it working...thank goodness.
Big thank you for the help and patience

Trenzador I have the same trouble can you please post instructions on how you managed to get it sorted out thanks
Sent from my Nexus 7 using xda app-developers app

stuck at boot animation - CM

i would post this on the CM tyhread but dont have permission with > 10 posts. I flashed CM nightly to my htc one and was stuck in the boot animation, bad part is that it wont shut off....so i let the battery die. i power into recovery and found out i cant access the internal storage via my pc without it being turned on (not in recovery) so how can i put my backup or a different rom in the internal storage through Team Win's recovery? everytime it turns on it just stays stuck at boot animation...

1) you can try to flash the boot.img in fastboot.
Maybe it will boot
2) You can push your backup into sd with adb command like:
Code:
adb push name_of_file.extenction /sdcard

anyway for me to restart the phone into recovery when its stuck in the boot animation?

Longpress power, when it will reboot, longpress Vol-.
you will boot into bootloader, then, recovery.

okay, i have gotten back into recovery mode, ive tried fastboot but it just stays at the animation. my computer doesnt recognize the phone in recovery...is there a way to change that?

mcydes said:
okay, i have gotten back into recovery mode, ive tried fastboot but it just stays at the animation. my computer doesnt recognize the phone in recovery...is there a way to change that?
Click to expand...
Click to collapse
From fastboot you can reflash a recovery
So, you pc don't recognize the phone with adb devices?

Guich said:
From fastboot you can reflash a recovery
So, you pc don't recognize the phone with adb devices?
Click to expand...
Click to collapse
no, and when i run Adb it will start to run the cmd prompt but closes immediately. i had the drivers installed...

mcydes said:
no, and when i run Adb it will start to run the cmd prompt but closes immediately. i had the drivers installed...
Click to expand...
Click to collapse
Very strange
Try to reflash recovery and re try

Guich said:
Very strange
Try to reflash recovery and re try
Click to expand...
Click to collapse
okay i am in fastboot USB mode on bootloader screen, and my computer still isnt recognizing the device...i opened my cmd prompt and entered adb devices, executed the command and it lists nothing after "list of devices attached" the phone is plugged in through the usb cable and on the phone it says Fastboot USB.

Guich said:
1) you can try to flash the boot.img in fastboot.
Maybe it will boot
2) You can push your backup into sd with adb command like:
Code:
adb push name_of_file.extenction /sdcard
Click to expand...
Click to collapse
I think that doing
Code:
adb sideload [I]package name[/I]
would fix the problem. If using CWM, just choose in.stall from sideload and do the previously stated code in cmd.exe

JacksonS918 said:
I think that doing
Code:
adb sideload [I]package name[/I]
would fix the problem. If using CWM, just choose in.stall from sideload and do the previously stated code in cmd.exe
Click to expand...
Click to collapse
i did it and got....
c:\Tools>adb sideload TrickDroid_5.5.1.zip
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.

mcydes said:
i did it and got....
c:\Tools>adb sideload TrickDroid_5.5.1.zip
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.
Click to expand...
Click to collapse
The problem is with the name of your file. Rename it to something like trickdroid.zip with NO UNDERSCORES because the sideload can't read it. Also, in recovery mode, make sure you select install by sideload!

JacksonS918 said:
I think that doing
Code:
adb sideload [I]package name[/I]
would fix the problem. If using CWM, just choose in.stall from sideload and do the previously stated code in cmd.exe
Click to expand...
Click to collapse
i still get the debug.
here is some additional information; i tried another htc one and my pc recognized it. i formatted the hard drive, and factory reset as well

What recovery are you using? Also, try using Cyanogen mod instead of TrickDroid. Both should work if you flash ClockWorkMod Recovery using the One AIO Toolkit by hasoon2000. With CWM installed, go to Install Zip from sideload and start, do the command adb sideload cm.zip, and wait. It should install.
Sent from my HTC One using xda app-developers app

JacksonS918 said:
What recovery are you using? Also, which nightly are you using?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Team win's. and im using CM's 5/22/2013 nightly

mcydes said:
Team win's. and im using CM's 5/22/2013 nightly
Click to expand...
Click to collapse
I'd flash CWM just because I believe it works better. Here, use this Nightly -> get.cm/?device=m7. Are you having problems with TrickDroid or with CyanogenMod? Re-flashing CyanogenMod should do the trick, but make sure to factory reset beforehand and clear the Dalvik Cache after the sideload. Then try to install TrickDroid by installing the Cydia Substrate from the Play Store as well as Winterboard and then install the TrickDroid ROM from Winterboard.

JacksonS918 said:
I'd flash CWM just because I believe it works better. Here, use this Nightly -> get.cm/?device=m7. Are you having problems with TrickDroid or with CyanogenMod? Re-flashing CyanogenMod should do the trick, but make sure to factory reset beforehand and clear the Dalvik Cache after the sideload. Then try to install TrickDroid by installing the Cydia Substrate from the Play Store as well as Winterboard and then install the TrickDroid ROM from Winterboard.
Click to expand...
Click to collapse
i cant do any of that because my phone isnt being recognized by my computer, however it is able to charge.

mcydes said:
i cant do any of that because my phone isnt being recognized by my computer, however it is able to charge.
Click to expand...
Click to collapse
You need to go into fastboot by holding down power and volume down, then going to bootloader by pressing power, then hit volume down once. After that, open up the toolkit and say flash ClockWorkMod Recovery. Alternatively, you can go into command prompt and do
Code:
fastboot flash recovery clockworkmod.zip
Make sure you rename the CWM file to the specified name in the code. I personally recommend flashing through the AIO Toolkit, but it's your decision. From there, you can follow the previously stated instructions.

JacksonS918 said:
You need to go into fastboot by holding down power and volume down, then going to bootloader by pressing power, then hit volume down once. After that, open up the toolkit and say flash ClockWorkMod Recovery. Alternatively, you can go into command prompt and do
Code:
fastboot flash recovery clockworkmod.zip
Make sure you rename the CWM file to the specified name in the code. I personally recommend flashing through the AIO Toolkit, but it's your decision. From there, you can follow the previously stated instructions.
Click to expand...
Click to collapse
read what ive done already, i cant do anything of that sort. in cmd prompt i am always returned with no device found.

wait!
adb devices lists no devices but fastboot devices command comes up with my phone...
i tried
>fastboot flash \sdcard trick.zip
it sent and said finished but its not in the \sdcard directory

Update.. issue

Hi guys I'm a bit of a noob when it comes to roms and updating phones.
I managed to root my phone and add team win and super user admin thing. I even updated all the way to Google vanilla but went back stock. My issues now is I want to update my phone via the update in systems and it won't let me. My phone boots up into team win recovery.
There's a 30mb update 2.24.401..... Can you help me with this small query. I just want to be able to update
Sent from my HTC One using xda app-developers app

nuzik said:
Hi guys I'm a bit of a noob when it comes to roms and updating phones.
I managed to root my phone and add team win and super user admin thing. I even updated all the way to Google vanilla but went back stock. My issues now is I want to update my phone via the update in systems and it won't let me. My phone boots up into team win recovery.
There's a 30mb update 2.24.401..... Can you help me with this small query. I just want to be able to update
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
You cannot update your phone when you have a custom recovery installed, you have to reinstall the stock recovery! If you have an international htc one with 2.24.401.1 here is a step by step guide to update the phone, i wrote it for someone else with the same problem as yours!
http://forum.xda-developers.com/showpost.php?p=45179063&postcount=5

im an idiot
RTIT said:
You cannot update your phone when you have a custom recovery installed, you have to reinstall the stock recovery! If you have an international htc one with 2.24.401.1 here is a step by step guide to update the phone, i wrote it for someone else with the same problem as yours!
http://forum.xda-developers.com/showpost.php?p=45179063&postcount=5
Click to expand...
Click to collapse
Ok it seems i went in TWRP and wiped everything, i have no roms on my phone! I cant get any files on it or anything suggestions please

nuzik said:
Ok it seems i went in TWRP and wiped everything, i have no roms on my phone! I cant get any files on it or anything suggestions please
Click to expand...
Click to collapse
lol dont worry your not an idiot, it happens to all of us what you have to do is boot into twrp go to advanced, then adb sideload and swipe, then on your computer open a command line where you have your folder for rooting the htc one (where fastboot and adb are etc...) and put any ROM in that folder, rename it to rom.zip and type "adb sideload rom.zip" without the quotes and you should be good to go!

Thanks one more...
RTIT said:
lol dont worry your not an idiot, it happens to all of us what you have to do is boot into twrp go to advanced, then adb sideload and swipe, then on your computer open a command line where you have your folder for rooting the htc one (where fastboot and adb are etc...) and put any ROM in that folder, rename it to rom.zip and type "adb sideload rom.zip" without the quotes and you should be good to go!
Click to expand...
Click to collapse
Sorry to ask any chance where the original stock HTC sense is? not the google play?

nuzik said:
Sorry to ask any chance where the original stock HTC sense is? not the google play?
Click to expand...
Click to collapse
No problem, here it is (2.24.401.1) http://forum.xda-developers.com/showthread.php?t=2353083
make sure you choose one of the odexed ones so you can install the update, either choose Stock Rooted + BusyBox Odexed or Stock Without ROOT Odexed
EDIT: btw if you install this rom, you can skip steps 3 and 4 in my step by step guide because this rom already containts these files

!
i keep getting an error closed message..
now all i get is the CMD prompt going through a list of things.
pushing etc

nuzik said:
i keep getting an error closed message..
Click to expand...
Click to collapse
Did you go to advanced, adb sideload and swipe and then entered the command in cmd?
EDIT: Try running "adb usb" and then running the "adb sideload rom.zip" command, it should work

RTIT said:
Did you go to advanced, adb sideload and swipe and then entered the command in cmd?
EDIT: Try running "adb usb" and then running the "adb sideload rom.zip" command, it should work
Click to expand...
Click to collapse
nope nothing still just runs through
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:\android\android-sdk-windows\platform-tools>adb devices
List of devices attached
SH36WW900035 host
C:\android\android-sdk-windows\platform-tools>adb usb sideload rom.zip
error: closed
C:\android\android-sdk-windows\platform-tools>adb sideload rom.zip
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:\android\android-sdk-windows\platform-tools>

nuzik said:
nope nothing still just runs through
Click to expand...
Click to collapse
Can you try this "adb push rom.zip /data/media/0/" and make sure that the rom zip file is in the platform tools folder

nope still nothing

nuzik said:
nope still nothing
Click to expand...
Click to collapse
Sorry I didnt say this eariler you have to run this command without going to advanced -> adb sideload so just enter the command "adb push rom.zip /data/media/0/" without going into sideload mode and tell me what happens and make sure you leave a space between zip and /media

well ive pressed it nothing is happening but it doesnt say failed yet

nuzik said:
well ive pressed it nothing is happening but it doesnt say failed yet
Click to expand...
Click to collapse
Does it say something like <12345678kb to 1234567kb> ?

no its just blank
said failed is a directory...

trying again straight to SDCARD
C:\android\android-sdk-windows\platform-tools>adb push rom.zip /sdcard/
4187 KB/s (1080318520 bytes in 251.959s)
when i go to flash it says failed reading zip...

nuzik said:
no its just blank
said failed is a directory...
Click to expand...
Click to collapse
Ok last thing I want you to try "adb push rom.zip /sdcard"
---------- Post added at 05:13 AM ---------- Previous post was at 05:10 AM ----------
nuzik said:
trying again straight to SDCARD
C:\android\android-sdk-windows\platform-tools>adb push rom.zip /sdcard/
4187 KB/s (1080318520 bytes in 251.959s)
when i go to flash it says failed reading zip...
Click to expand...
Click to collapse
mhm maybe try re-downloading the rom zip file, maybe its corrupted, but anyway now you can push any rom since its working, try pushing the google play edition rom until you redownload the sense rom

nuzik said:
trying again straight to SDCARD
C:\android\android-sdk-windows\platform-tools>adb push rom.zip /sdcard/
4187 KB/s (1080318520 bytes in 251.959s)
when i go to flash it says failed reading zip...
Click to expand...
Click to collapse
now its gone from the phone!

nuzik said:
now its gone from the phone!
Click to expand...
Click to collapse
Try pushing another rom, it should work!

RTIT said:
Try pushing another rom, it should work!
Click to expand...
Click to collapse
re did it and its installing i can go to bed now!!! i hope

[Q] Bootloop forever after KitKat install

So i decided to give insertcoin 4.4 rom a go yesterday. flashed twrp 2.6.3.3 via adb flash recovery which worked great.
Clean installed insertcoin kept to instructions no odex etc.... phone rebooted as required got to setup screen an just reboots itself and repeats the same procedure.
I cannot push anything via adb now all sdk is up to date and in correct folders etc.
would try sideload but i cant get any sense out of that. any help on this oh yeah.
hboot 1.54, htc dev unlocked and thought i had s-off but its showing s-on. tried rumrunner with the hope i can fix situation but no joy but the program just ends.
so whats i should route to take follow some tutorials and get back to stock or try a few more times to get it sorted?
edit: I have a backup but its on my laptop and i cannot push it through

ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Press ENTER to exitYes
This is the message I get when trying rumrunner. but there is no way i can enable/disable usb debugging as i cannot boot into the phone

I have tried many different ways to restore the phone but i keep getting remote not allowed error

iamsloany said:
I have tried many different ways to restore the phone but i keep getting remote not allowed error
Click to expand...
Click to collapse
I thought TWRP 2.6.3.3 was pulled due to some bugs, maybe best to go back to 2.6.3.0
then use adb push or sideload to get a Guru Reset ROM (same or close to your firmware) onto your phone (with ROOT, and without "stock recovery")
and use rumrunner to get s-off.

nkk71 said:
I thought TWRP 2.6.3.3 was pulled due to some bugs, maybe best to go back to 2.6.3.0
then use adb push or sideload to get a Guru Reset ROM (same or close to your firmware) onto your phone (with ROOT, and without "stock recovery")
and use rumrunner to get s-off.
Click to expand...
Click to collapse
thought i was being clever installed latest CWM made fatal mistake and delted user data phone still doing same thing booting and rebooting. cant get s-off as i cannot boot into phone and anything being sideloaded or pushed through adb other than a recovery img wont flash.
im majorly stuck help

iamsloany said:
thought i was being clever installed latest CWM made fatal mistake and delted user data phone still doing same thing booting and rebooting. cant get s-off as i cannot boot into phone and anything being sideloaded or pushed through adb other than a recovery img wont flash.
im majorly stuck help
Click to expand...
Click to collapse
what's the output of the adb push command? can you copy/paste your command prompt output please
example:
Code:
C:\ADB2>[B]adb push Guru_Reset_M7_3.62.401.1.zip /data/media/[/B]
2922 KB/s (1102709591 bytes in 368.450s) [I][B]<- just an example, and yes it takes 5 to 10 minutes without reporting any progress until finished[/B][/I]
C:\ADB2>[B]adb shell[/B]
~ # [B]cd /data/media[/B]
cd /data/media
/data/media #[B] ls -l[/B]
ls -l
-rw-rw-rw- 1 root root 1102709591 Oct 3 03:56 Guru_Reset_M7_2.24.707.1.zip [I]<- just an example[/I]
/data/media # [B]md5sum Guru_Reset_M7_3.62.401.1.zip[/B]
md5sum Guru_Reset_M7_3.62.401.1.zip
6444b41a1f332f31345d5ead674382d7 Guru_Reset_M7_3.62.401.1.zip [B][I]<- confirm MD5 sum is correct[/I][/B]
/data/media #[B] exit[/B]
exit
C:\ADB2>

nkk71 said:
what's the output of the adb push command? can you copy/paste your command prompt output please
example:
Code:
C:\ADB2>[B]adb push Guru_Reset_M7_3.62.401.1.zip /data/media/[/B]
2922 KB/s (1102709591 bytes in 368.450s) [I][B]<- just an example, and yes it takes 5 to 10 minutes without reporting any progress until finished[/B][/I]
C:\ADB2>[B]adb shell[/B]
~ # [B]cd /data/media[/B]
cd /data/media
/data/media #[B] ls -l[/B]
ls -l
-rw-rw-rw- 1 root root 1102709591 Oct 3 03:56 Guru_Reset_M7_2.24.707.1.zip [I]<- just an example[/I]
/data/media # [B]md5sum Guru_Reset_M7_3.62.401.1.zip[/B]
md5sum Guru_Reset_M7_3.62.401.1.zip
6444b41a1f332f31345d5ead674382d7 Guru_Reset_M7_3.62.401.1.zip [B][I]<- confirm MD5 sum is correct[/I][/B]
/data/media #[B] exit[/B]
exit
C:\ADB2>
Click to expand...
Click to collapse
going out for an hour will post when I get back

there you go its all i get
C:\Fastboot>fastboot flash zip C:\Fastboot\ViperOne_3.1.0_RC2.zip
sending 'zip' (982337 KB)...
OKAY [ 42.790s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 42.812s
C:\Fastboot>adb push "C:\Fastboot\HTC One Toolkit 2.0 - Squabbi.zip"
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:\Fastboot>

You didn't read nkk71's example properly.
Assuming this file is good: HTC One Toolkit 2.0 - Squabbi.zip, rename to Squabbi.zip only
try:
C:\Fastboot>adb push Squabbi.zip /data/media/
How does it go?

iamsloany said:
there you go its all i get
C:\Fastboot>fastboot flash zip C:\Fastboot\ViperOne_3.1.0_RC2.zip
sending 'zip' (982337 KB)...
OKAY [ 42.790s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 42.812s
Click to expand...
Click to collapse
you cant fastboot flash a ROM. you have to, be in custom recovery, then:
adb push C:\Fastboot\ViperOne_3.1.0_RC2.zip /data/media/ <- this will take 5 to 10 min
then in recovery INSTALL ZIP -> choose zip -> ViperOne
and you should be good.

All fixed now using revone to s-off and sideloaded zip I'm back in the game.
Thanks for you help guys really appreciate it.
Sent from my HTC One using xda app-developers app

iamsloany said:
All fixed now using revone to s-off and sideloaded zip I'm back in the game.
Thanks for you help guys really appreciate it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
all done? if yes, please add [SOLVED] to your main thread title. thanks

iamsloany said:
All fixed now using revone to s-off and sideloaded zip I'm back in the game.
Thanks for you help guys really appreciate it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I was having the same issue, but can't seem to get past it.
I have HBOOT 1.55 and CWM installed. S-ON.
I've tried Revone and Rumrunner but can't get S-OFF.
If I go back to Cyanogen Mod rom it works but I would like to try this ROM, no joy! http://forum.xda-developers.com/showthread.php?t=2544119&page=4

Back to the htc one stock rom

Is the only way to go stock rom by changing mainboard?? htc malaysia sent "only way is changing the mainboard. Mainboard is too expensive for me. Is any idea to back stockrom??

Check this http://forum.xda-developers.com/showthread.php?p=51151301
Sent from my HTC One

Help this company said:
Is the only way to go stock rom by changing mainboard?? htc malaysia sent "only way is changing the mainboard. Mainboard is too expensive for me. Is any idea to back stockrom??
Click to expand...
Click to collapse
This is now your 4 thread for the same problem. Please quit making new threads and follow the advice folks have already given you for your issue.

Thread 1
Thread 2 <----------------- there were people who helped you here but you have not answered and you left
Thread 3 <----------------- there were people who helped you here but you have not answered and you left
I guess it will be the same thing here...

Back to stock.
Hi. I am Superpulla and i like go to stock from Maximus HD rom. i have 4.19.401.8 Version. I don't know witch ruu.zip i must download. all of them are meant to be on JB??!. If someone could help me with this, i be so thankfull.
I allready get my cid back to stock: HTC__Y13
HTC One m7_ul kitkat 4.4.2 Sense 5.5
Main guestions are: 1. What i do now?
2. Witch Ruu.zip i can flash

Superpulla said:
Hi. I am Superpulla and i like go to stock from Maximus HD rom. i have 4.19.401.8 Version. I don't know witch ruu.zip i must download. all of them are meant to be on JB??!. If someone could help me with this, i be so thankfull.
I allready get my cid back to stock: HTC__Y13
HTC One m7_ul kitkat 4.4.2 Sense 5.5
Main guestions are: 1. What i do now?
2. Witch Ruu.zip i can flash
Click to expand...
Click to collapse
U should repost in your own thread, it's easier to track.
Also post output from fastboot getvar all

A
alray said:
Thread 1
Thread 2 <----------------- there were people who helped you here but you have not answered and you left
Thread 3 <----------------- there were people who helped you here but you have not answered and you left
I guess it will be the same thing here...
Click to expand...
Click to collapse
I need Thread 1,2,3. Each thread different..

Help this company said:
I need Thread 1,2,3. Each thread different..
Click to expand...
Click to collapse
Why? Is it a different device?

Help this company said:
I need Thread 1,2,3. Each thread different..
Click to expand...
Click to collapse
Hmmmm no
To summarize:
Thread #2 (initial thread) -----> phone soft bricked, explained you how to install adb/fastboot/drivers to post a ''getvar all'', determined that you can not use your stock rom atm because of this. So I have suggested you to try this. You did not answered.
Thread #1 ------> phone soft bricked, you are asking again to flash your stock rom (adb sideload) even after reading this. no body answered in this thread.
Thread #3 --------> phone soft bricked, you are asking direction how to use adb sideload.
Thread #4 (here) ----> phone soft bricked you are asking how to return stock again.
Your issue is: Phone soft bricked. You don't have to create a new thread for each problem you encounter with un-bricking your phone. You could simply update the information in your initial thread so its easier for people to help and for YOU to understand. Now read back those threads and ask questions about what you don't understand (not in a new thread) and I'll (we) be pleased to help you.
---------- Post added at 07:23 PM ---------- Previous post was at 07:08 PM ----------
Help this company said:
Is the only way to go stock rom by changing mainboard?? htc malaysia sent "only way is changing the mainboard. Mainboard is too expensive for me. Is any idea to back stockrom??
Click to expand...
Click to collapse
So again, you can return to stock using a ''guru reset rom''. This is a stock rom that when installed will reset your phone back to stock (stock rom, stock recovery, stock radio). The rom is pushed to your sd card via TWRP or sideloaded via TWRP. The problem is the guru reset rom version you need have a bad file that will prevent you to get ota updates (discussed here)
this Reset ROM is supposed to install 3.63.707.4 software on the phone but it installs 3.63.707.3 instead , the software information under settings shows 3.63.707.3 while OS in "fastboot getvar all" shows 3.63.707.4. i went ahead and tried to OTA update it with this ROM but it gave variant error because of fw and sw number not matching
Click to expand...
Click to collapse
. So you will not be 100% stock because of this but at least your phone will boot.
Option 2 is to flash a custom rom like ARHD. It really looks and feels like the stock rom. This is a rock stable rom, always up to date. Again you'll need to push or sideload the rom
Option 3 is to go back to stock using a RUU. Unfortunately the only RUU for you phone version is DECRYPTED which means it required S-OFF to be flashed. So to use this RUU you'll need to S-OFF your phone which require to flash ARHD rom before.
Hope its clear, ask any questions if not, or choose which option you prefer and we will assist you but please for the love of god, no more threads :victory:

a
alray said:
Hmmmm no
To summarize:
Thread #2 (initial thread) -----> phone soft bricked, explained you how to install adb/fastboot/drivers to post a ''getvar all'', determined that you can not use your stock rom atm because of this. So I have suggested you to try this. You did not answered.
Thread #1 ------> phone soft bricked, you are asking again to flash your stock rom (adb sideload) even after reading this. no body answered in this thread.
Thread #3 --------> phone soft bricked, you are asking direction how to use adb sideload.
Thread #4 (here) ----> phone soft bricked you are asking how to return stock again.
Your issue is: Phone soft bricked. You don't have to create a new thread for each problem you encounter with un-bricking your phone. You could simply update the information in your initial thread so its easier for people to help and for YOU to understand. Now read back those threads and ask questions about what you don't understand (not in a new thread) and I'll (we) be pleased to help you.
---------- Post added at 07:23 PM ---------- Previous post was at 07:08 PM ----------
So again, you can return to stock using a ''guru reset rom''. This is a stock rom that when installed will reset your phone back to stock (stock rom, stock recovery, stock radio). The rom is pushed to your sd card via TWRP or sideloaded via TWRP. The problem is the guru reset rom version you need have a bad file that will prevent you to get ota updates (discussed here)
. So you will not be 100% stock because of this but at least your phone will boot.
Option 2 is to flash a custom rom like ARHD. It really looks and feels like the stock rom. This is a rock stable rom, always up to date. Again you'll need to push or sideload the rom
Option 3 is to go back to stock using a RUU. Unfortunately the only RUU for you phone version is DECRYPTED which means it required S-OFF to be flashed. So to use this RUU you'll need to S-OFF your phone which require to flash ARHD rom before.
Hope its clear, ask any questions if not, or choose which option you prefer and we will assist you but please for the love of god, no more threads :victory:
Click to expand...
Click to collapse
thank you. I want to go back perfect stock rom. So I have to s-off... But how to s-off??
And I don't want to use any custom rom.
Last, I have a question, Do I not to send htc malaysia center to change mainboard??
Now, I'll not use any fixing ways but i will use only ur ways. I believe you!!
*Information.
my hboot is 1.56. radio ; 4A.23.3263.28 OS; 4.20.707.6 S-ON TAMPERED UNLOCKED.

Help this company said:
thank you. I want to go back perfect stock rom. So I have to s-off... But how to s-off??
And I don't want to use any custom rom.
Click to expand...
Click to collapse
Help this company said:
my hboot is 1.56.
Click to expand...
Click to collapse
You can s-off your phone using rumrunner tool or firewater tool. However many users reported not being able to s-off on hboot 1.56. You'll have to try it. You'll need to use a custom even if you don't want. A working rom is needed to achieve s-off. If you can't s-off you'll have no choice using a custom rom or the guru reset rom
Help this company said:
Last, I have a question, Do I not to send htc malaysia center to change mainboard??
Click to expand...
Click to collapse
If you phone still able to boot in bootloader mode, you don't have to send the phone for repair.

A
alray said:
You can s-off your phone using rumrunner tool or firewater tool. However many users reported not being able to s-off on hboot 1.56. You'll have to try it. You'll need to use a custom even if you don't want. A working rom is needed to achieve s-off. If you can't s-off you'll have no choice using a custom rom or the guru reset rom
If you phone still able to boot in bootloader mode, you don't have to send the phone for repair.
Click to expand...
Click to collapse
adb reboot (<--- important!!!!)
adb wait-for-device push firewater /data/local/tmp
adb shell su
chmod 755 /data/local/tmp/firewater /data/local/tmp/firewater
Shoud I input that code at cmd??? For example adb reboot. And Why important "adb reboot"?
And Shoud I add the file "firewater" at existing adb folder??
Last, To use adb command, what I have to prepare? Stay twrp recovery or bootloader or fastboot??
I'm so sorry about my short root knowledge...

Help this company said:
adb reboot (<--- important!!!!)
adb wait-for-device push firewater /data/local/tmp
adb shell su
chmod 755 /data/local/tmp/firewater /data/local/tmp/firewater
Shoud I input that code at cmd??? For example adb reboot. And Why important "adb reboot"?
And Shoud I add the file "firewater" at existing adb folder??
Last, To use adb command, what I have to prepare? Stay twrp recovery or bootloader or fastboot??
I'm so sorry about my short root knowledge...
Click to expand...
Click to collapse
Do you have arhd rom installed on your phone?

a
alray said:
Do you have arhd rom installed on your phone
Click to expand...
Click to collapse
No, Could you write download link?? And 1st install arhd 2nd go back to stock rom??
How to s-off by using firewater?? I downloaded file, and just type "adb reboot (<--- important!!!!)*adb wait-for-device push firewater /data/local/tmp*adb shell su*chmod 755 /data/local/tmp/firewater /data/local/tmp/firewater" ????

Help this company said:
No, Could you write download link??
Click to expand...
Click to collapse
Easy to find on the forum. ARHD is the second thread listed under the ''ROMs'' tab or a simple search on google using ''ARHD'' and ''HTC ONE'' key words will brings you at the right place.
Help this company said:
And 1st install arhd 2nd go back to stock rom??
Click to expand...
Click to collapse
flash arhd first then if you can achieve s-off you'll be able to run the ruu to go back to stock. If you can't s-off then use arhd rom.
Help this company said:
How to s-off by using firewater?? I downloaded file, and just type "adb reboot''
Click to expand...
Click to collapse
Hmmmm, so your phone is softbricked which mean it can't boot. How can you reboot a phone that is not booted?! You need a working rom before. Then follow the guide I have posted above to s-off.
Honestly, making your phone boot should be your absolute priority. You are at step #1 -----> making your phone boot by flashing a rom. S-off is like step #10.

alray said:
Easy to find on the forum. ARHD is the second thread listed under the ''ROMs'' tab or a simple search on google using ''ARHD'' and ''HTC ONE'' key words will brings you at the right place.
flash arhd first then if you can achieve s-off you'll be able to run the ruu to go back to stock. If you can't s-off then use arhd rom.
Hmmmm, so your phone is softbricked which mean it can't boot. How can you reboot a phone that is not booted?! You need a working rom before. Then follow the guide I have posted above to s-off.
Honestly, making your phone boot should be your absolute priority. You are at step #1 -----> making your phone boot by flashing a rom. S-off is like step #10.
Click to expand...
Click to collapse
1. Should I check the radio,etc of ARHD ROM??
2. If I downloaded Arhd, Should I use "adb sideload arhdname.zip"??
3. I entered adb sideload and Swipe it, it shows me "Failed". What's the problem???
Thank U Mr.alray helping me. I'll do that at night(korea time).
Sincerely, I appreciate ur help.

Help this company said:
1. Should I check the radio,etc of ARHD ROM??
2. If I downloaded Arhd, Should I use "adb sideload arhdname.zip"??
3. I entered adb sideload and Swipe it, it shows me "Failed". What's the problem???
Thank U Mr.alray helping me. I'll do that at night(korea time).
Sincerely, I appreciate ur help.
Click to expand...
Click to collapse
1. just flash the rom
2. adb sideload it or adb push it.
3. Maybe a driver issue. When in twrp sideload mode, open a command prompt from your adb/fastboot folder and type ''adb devices''. What is the output?

a
alray said:
1. just flash the rom
2. adb sideload it or adb push it.
3. Maybe a driver issue. When in twrp sideload mode, open a command prompt from your adb/fastboot folder and type ''adb devices''. What is the output?
Click to expand...
Click to collapse
when I typed adb devices,it shows "my serial name sideload". and I did adb sideload arhd.zip. it shows 100% but I can't find the file.
also, I did adb push,this shows me this.↓
-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.

Help this company said:
when I typed adb devices,it shows "my serial name sideload". and I did adb sideload arhd.zip. it shows 100% but I can't find the file.
also, I did adb push,this shows me this.↓
Click to expand...
Click to collapse
You need to add the file name you want to push and its destination on the phone! Not only ''adb push''
Code:
adb push <name_of_rom>.zip /sdcard/
then your rom will be on your sdcard folder.
or
adb sideload using this command:
Code:
adb sideload <name_of_rom>.zip
Btw use the sideload command when in twrp sideload mode (''adb devices'' must output your s/n + sideload)
use adb push when in twrp recovery main menu (''adb devices'' must output your s/n + recovery)
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
and the long text you posted is the help page. Every time you see that page means you did not typed a valid command.
-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'.
etc etc etc.....
Click to expand...
Click to collapse

a
alray said:
You need to add the file name you want to push and its destination on the phone! Not only ''adb push''
Code:
adb push <name_of_rom>.zip /sdcard/
then your rom will be on your sdcard folder.
or
adb sideload using this command:
Code:
adb sideload <name_of_rom>.zip
Btw use the sideload command when in twrp sideload mode (''adb devices'' must output your s/n + sideload)
use adb push when in twrp recovery main menu (''adb devices'' must output your s/n + recovery)
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
and the long text you posted is the help page. Every time you see that page means you did not typed a valid command.
Click to expand...
Click to collapse
WOW, Finally, I did !!!!!!! I hadn't supersu in my device. I was deleted it. I installed supersu by adb sideload today,It works well.!!!!!!!!
Thank U !!!! thank u very much(x100).!!!!!!!!!!!! U save my money and life.!!!!
Now, Should I s-off to go back to stock rom???
And If I clicked the Thanks, Can't I ask this inquiry???
Anyway Thanks Mr.alray. Ur perfert Guy!!!!!!:good: