Database Develop

Daemon not running - Failed to connect.

Apologies if this has been repeated but I have spent the last 30mins looking through this site and can not find a similar problem.
I am currently going through the process of overclocking my Nexus one.
I am running Cyanogen and have flashed the image file needed.
I am now trying to push the bcm4329.ko file to the system modules folder.
I have updated my USB drivers sand the phone appears to have liked that.
However when I try to perform an ADB remount command it takes a while thinking about it, tells me that "daemon is not running" and is "starting it now"
ADB server didnt ACK
* failed to start daemon *
error: can not connect to daemon.
Any suggestions as to how I can resolve this issue please?

adb kill-server
adb start-server

[Q] Motofail v905 = FAIL

Went to root the wife's phone today which has the 905 update on it, tried some of my old methods (pete's, tehRoot) they failed. So then found out the 'new hotness' is motofail. Downloaded that (not sure what version) and it failed as well. Can't seem to find an answer why, here's the output. Yes, Dev is enabled, USB Charging Mode, x64 moto drivers, Unknown Sources checked.
Code:
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
adb server is out of date. killing...
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
push: motofail/Superuser.apk -> /data/local/motofail/Superuser.apk
push: motofail/su -> /data/local/motofail/su
push: motofail/run.bat -> /data/local/motofail/run.bat
push: motofail/motofail -> /data/local/motofail/motofail
push: motofail/busybox -> /data/local/motofail/busybox
push: motofail/AdbWinUsbApi.dll -> /data/local/motofail/AdbWinUsbApi.dll
push: motofail/AdbWinApi.dll -> /data/local/motofail/AdbWinApi.dll
push: motofail/adb.exe -> /data/local/motofail/adb.exe
8 files pushed. 0 files skipped.
2667 KB/s (3972528 bytes in 1.454s)
[*] Owning phone...
/data/local/motofail: permission denied
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
[*] Cleaning up...
/data/local/motofail: permission denied
rm failed for /data/local/motofail, Is a directory
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Ideas?
Thanks,
Chad

I don't know what to tell you. I used motofail several times on my 905 and had no problems whatsoever.
Sent from my DROID BIONIC using xda premium

Ditto. rooted it first go around after the patch.

Are there different versions of the motofail? Maybe I just have an old one?

Try this one http://www.corusa.com/public/motofail.exe Download to your desktop. Right click downloaded file (run as administrator) follow program prompts. Celebrate your rooted.

Ah That worked! Thanks. I had to go in and manually rm the files in /data/local/motofail and the directory however. Most likely one of the old exploits stuck stuff in there and motofail was unable to overwrite them. Either way. Rooted and Rootkeeper installed.
Thanks,
Chad

Good for you, glad it worked out. :victory:

[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

Messed up HTC One

Hi all,
I am Marc and i'm new here on the forum..(and in installing custom roms). so i tried cyanogenmod for a couple of days , but then i decided to go back to stock rom. And somehow,i messed up at that moment. I now have a HTC One wich will only boot in bootloader mode,nothing else.
If i set the Phone to fastboot mode, i don't see it in windows..if it's in recovery mode i see the Phone in windows,but it is unaccessable...so i can't copy a new rom to the Phone and reinstall it with twrp recovery.(that is on the Phone)
HTC One is a international version. Here is the getvar info..
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__E11
battery-status: good
battery-voltage: 4291mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
Confused as i was i formatted the system in recovery mode and now it looks like there's no partition anymore..
I'm desperate...can somebody help me?

marc1201 said:
Hi all,
I am Marc and i'm new here on the forum..(and in installing custom roms). so i tried cyanogenmod for a couple of days , but then i decided to go back to stock rom. And somehow,i messed up at that moment. I now have a HTC One wich will only boot in bootloader mode,nothing else.
If i set the Phone to fastboot mode, i don't see it in windows..if it's in recovery mode i see the Phone in windows,but it is unaccessable...so i can't copy a new rom to the Phone and reinstall it with twrp recovery.(that is on the Phone)
HTC One is a international version. Here is the getvar info..
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__E11
battery-status: good
battery-voltage: 4291mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
Confused as i was i formatted the system in recovery mode and now it looks like there's no partition anymore..
I'm desperate...can somebody help me?
Click to expand...
Click to collapse
you must be using Windows 8.1
get yourself Windows 7 or Ubuntu
Sent from my One using Tapatalk

kamilmirza said:
you must be using Windows 8.1
get yourself Windows 7 or Ubuntu
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I am using windows 7 pro

marc1201 said:
I am using windows 7 pro
Click to expand...
Click to collapse
in custom recovery use:
adb push <name of rom>.zip /data/media/0/
or
adb sideload <name of rom>.zip
to get a ROM onto your phone and install it.

nkk71 said:
in custom recovery use:
adb push <name of rom>.zip /data/media/0/
or
adb sideload <name of rom>.zip
to get a ROM onto your phone and install it.
Click to expand...
Click to collapse
When i use adb push i got the following:
C:\Users\Marc\Downloads\HTCOneRoot>adb push firmware 3.62.401.1.zip/data/media/0
/
error: closed
So it says error: closed
When i use adb sideload it says:
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\Marc\Downloads\HTCOneRoot>
I don't know anymore...I'm really new in these things
Marc

marc1201 said:
When i use adb push i got the following:
C:\Users\Marc\Downloads\HTCOneRoot>adb push firmware 3.62.401.1.zip/data/media/0
I don't know anymore...I'm really new in these things
Marc
Click to expand...
Click to collapse
1- Why are you pushing a firmware?? you need to push a ROM
2- adb push <name of rom without spaces>.zip /data/media/0/ , you typed:
adb push firmware<space should not be here>3.62.401.1.zip<missing space>/data/media/0

nkk71 said:
1- Why are you pushing a firmware?? you need to push a ROM
2- adb push <name of rom without spaces>.zip /data/media/0/ , you typed:
adb push firmware<space should not be here>3.62.401.1.zip<missing space>/data/media/0
Click to expand...
Click to collapse
@ nkk71, isn't that the same?(rom or firmware) The file i downloaded is named firmware 3.62.401.1,wich should be the 4.3 rom with sense 5.5...
I guess i better left it Original..:crying:
Edit: when i do it like you said i still got the same error:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
C:\Users\Marc\Downloads\HTCOneRoot>

marc1201 said:
isn't that the same?(rom or firmware) The file i downloaded is named firmware 3.62.401.1,wich should be the 4.3 rom with sense 5.5...
I guess i better left it Original..:crying:
Click to expand...
Click to collapse
NO, it is certainly not the same.
I think you should take a break (before you do something you'll really regret), and do some reading (no offense intended).... we were all where you are now, but start searching and reading.

nkk71 said:
NO, it is certainly not the same.
I think you should take a break (before you do something you'll really regret), and do some reading (no offense intended).... we were all where you are now, but start searching and reading.
Click to expand...
Click to collapse
I think i should do that yes.. I have another file called M7-3.4.10-g6ac477c This is the rom i think.(m7 is given in the file name)
But still got errors...:crying::crying::crying:
I think i just going to send it to HTC...No warranty then,but probably less cost then buying a new one
Another question..do i need to have S-OFF?? It's still on S-ON...

marc1201 said:
I think i should do that yes.. I have another file called M7-3.4.10-g6ac477c This is the rom i think.(m7 is given in the file name)
But still got errors...:crying::crying::crying:
I think i just going to send it to HTC...No warranty then,but probably less cost then buying a new one
Another question..do i need to have S-OFF?? It's still on S-ON...
Click to expand...
Click to collapse
While in fastboot USB, use the command "fastboot erase cache", and then push the ROM, not the firmware..... do what nkk71 wrote and you should be alright! Do not send the phone to HTC, you will get no refund or repair done

I am able to erase the cache but pushing the rom will not work here.. then somehowe the device is not recognized
C:\Users\Marc\Downloads\HTCOneRoot>fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.066s
C:\Users\Marc\Downloads\HTCOneRoot>adb push m7-3.4.10-g6ac477c.zip /data/media/0
/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\Marc\Downloads\HTCOneRoot>adb devices
List of devices attached
C:\Users\Marc\Downloads\HTCOneRoot>adb devices
List of devices attached
FA35RW907658 recovery
C:\Users\Marc\Downloads\HTCOneRoot>adb push m7-3.4.10-g6ac477c.zip /data/media/0
/
cannot stat 'm7-3.4.10-g6ac477c.zip': No such file or directory
C:\Users\Marc\Downloads\HTCOneRoot>adb push m7-3.4.10-g6ac477c.zip /data/media/0
/
error: device not found

marc1201 said:
I am able to erase the cache but pushing the rom will not work here.. then somehowe the device is not recognized
C:\Users\Marc\Downloads\HTCOneRoot>fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.066s
C:\Users\Marc\Downloads\HTCOneRoot>adb push m7-3.4.10-g6ac477c.zip /data/media/0
/
error: device not found
error: device not found
Click to expand...
Click to collapse
you need to be in custom recovery for adb to work
bootloader => only fastboot commands
custom recovery => only adb commands
booted ROM with USB debugging enabled => only adb commands
I don't know where you got that file from (or if it is even a ROM, looks more like a kernel to me), but check my signature and use Clyde's index thread for a list of ROMs.
I'm on ARHD: http://forum.xda-developers.com/showthread.php?t=2183023
Recommended recovery (especially for 4.4 ROMs) is TWRP at the moment:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
make sure to check MD5 to know it's not a corrupt download, that site doesnt work with download managers.
in bootloader:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery
adb devices -> confirm it shows up
adb push Android_Revolution_HD-One_51.0.zip /data/media/0/ <- this will take about 5 mins, and will not show any progress until it's finished
in recovery select "install" and choose the ROM, go through the installation (and select wipe!!)
I hope that's clear

nkk71 said:
you need to be in custom recovery for adb to work
bootloader => only fastboot commands
custom recovery => only adb commands
booted ROM with USB debugging enabled => only adb commands
I don't know where you got that file from (or if it is even a ROM, looks more like a kernel to me), but check my signature and use Clyde's index thread for a list of ROMs.
I'm on ARHD: http://forum.xda-developers.com/showthread.php?t=2183023
Recommended recovery (especially for 4.4 ROMs) is TWRP at the moment:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
make sure to check MD5 to know it's not a corrupt download, that site doesnt work with download managers.
in bootloader:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery
adb devices -> confirm it shows up
adb push Android_Revolution_HD-One_51.0.zip /data/media/0/ <- this will take about 5 mins, and will not show any progress until it's finished
in recovery select "install" and choose the ROM, go through the installation (and select wipe!!)
I hope that's clear
Click to expand...
Click to collapse
nkk71,that's pretty clear,downloaded the Android_Revolution_HD-One_31.6.zip and followed all the steps you mentioned..But the Phone still won't cooperate.. I got a protocol failure..What is this?
C:\Users\Marc\Downloads\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6
.3.3-m7.img
< waiting for device >
sending 'recovery' (9184 KB)...
OKAY [ 1.165s]
writing 'recovery'...
OKAY [ 0.716s]
finished. total time: 1.884s
C:\Users\Marc\Downloads\HTCOneRoot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.058s]
finished. total time: 0.059s
C:\Users\Marc\Downloads\HTCOneRoot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
C:\Users\Marc\Downloads\HTCOneRoot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA35xxxxx sideload
C:\Users\Marc\Downloads\HTCOneRoot>adb push Android_Revolution_HD-One_31.6.zip /
data/media/0/
protocol failure
C:\Users\Marc\Downloads\HTCOneRoot>
At a second try i got this..:
C:\Users\Marc\Downloads\HTCOneRoot>adb push Android_Revolution_HD-One_31.6.zip /
data/media/0/
failed to copy 'Android_Revolution_HD-One_31.6.zip' to '/data/media/0/': Is a di
rectory
What does the sideload after the FA35XXX number? I tought it had to be FA35XXX Device...?

If device is in sideload then do adb sideload romname.zip
sent from my mobile device

marc1201 said:
nkk71,that's pretty clear,downloaded the Android_Revolution_HD-One_31.6.zip and followed all the steps you mentioned..But the Phone still won't cooperate.. I got a protocol failure..What is this?
C:\Users\Marc\Downloads\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6
.3.3-m7.img
< waiting for device >
sending 'recovery' (9184 KB)...
OKAY [ 1.165s]
writing 'recovery'...
OKAY [ 0.716s]
finished. total time: 1.884s
C:\Users\Marc\Downloads\HTCOneRoot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.058s]
finished. total time: 0.059s
C:\Users\Marc\Downloads\HTCOneRoot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
C:\Users\Marc\Downloads\HTCOneRoot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA35RW907658 sideload
C:\Users\Marc\Downloads\HTCOneRoot>adb push Android_Revolution_HD-One_31.6.zip /
data/media/0/
protocol failure
C:\Users\Marc\Downloads\HTCOneRoot>
Click to expand...
Click to collapse
you have to download a ROM. look here. http://forum.xda-developers.com/showthread.php?t=2183023 Download that rom and then do the above command.Just make sure you type in the correct name of the file in your command window. Firmware is not the same as a ROM. a ROM is a custom version of the operating system i.e. Android in this case. There are many ROMS to choose from. What you are attempting is not correct. This is why you must read.read .read and read BEFORE you attemp anything on a very expensive device. OK? Capeesh? Alright.

@ SaHiLzZ , sideload did the trick
Running the revolution HD-One 3.61 rom now...so back online hehe. Just pity that it isn't a stock rom...I rather had the Phone back in Original state..but that's a thing for later
Is there anyone out here who can help me find the Original stock rom...?
But for now, i am very happy that it runs again and i want to say a very big thank you to all that helped me !! THANK YOU !
Marc

marc1201 said:
@ SaHiLzZ , sideload did the trick
Running the revolution HD-One 3.61 rom now...so back online hehe. Just pity that it isn't a stock rom...I rather had the Phone back in Original state..but that's a thing for later
Is there anyone out here who can help me find the Original stock rom...?
But for now, i am very happy that it runs again and i want to say a very big thank you to all that helped me !! THANK YOU !
Marc
Click to expand...
Click to collapse
Why would you want to go back to stock ROM? ARHD is completely stock, just rooted and with improvements:
This is improved version of stock ROM - no visual changes!
Click to expand...
Click to collapse

nkk71 said:
Why would you want to go back to stock ROM? ARHD is completely stock, just rooted and with improvements:
Click to expand...
Click to collapse
Nkk71,this phone is only about 5 months old and i'm thinking about selling it. So to avoid warranty issues for the new owner and beeing able to update(via HTC) i want the phone back to original state.
Thus..again the question, who can help me with a stock rom?
Thanks again,
Marc

marc1201 said:
Nkk71,this phone is only about 5 months old and i'm thinking about selling it. So to avoid warranty issues for the new owner and beeing able to update(via HTC) i want the phone back to original state.
Thus..again the question, who can help me with a stock rom?
Thanks again,
Marc
Click to expand...
Click to collapse
modelid: PN0710000
cidnum: HTC__E11
Click to expand...
Click to collapse
if you want to sell it and/or return to 100% stock, you can follow my guide: http://forum.xda-developers.com/showthread.php?t=2541082
RUU.ZIP method, using this ruu.zip: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/

nkk71 said:
if you want to sell it and/or return to 100% stock, you can follow my guide: http://forum.xda-developers.com/showthread.php?t=2541082
RUU.ZIP method, using this ruu.zip: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
Click to expand...
Click to collapse
I am going to read your guide from a to z to be sure i don't brick it again.
Thanks once more for the help, i really appreciate it !

[Q] need help with a system problem please help me!

Went to change the patch on my htc one and the same system lost due to a failure during the process but not now conssigo send a rom to sdcard so I can install the following errors are these.
C:\Users\Lucas\Desktop\htc\ADB_Fastboot_light>fastboot flash rom boot.img
target reported max download size of 1526722560 bytes
sending 'rom' (5552 KB)...
OKAY [ 1.014s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.544s
C:\Users\Lucas\Desktop\htc\ADB_Fastboot_light>fastboot flash rom ady.zip
error: cannot open 'ady.zip'
C:\Users\Lucas\Desktop\htc\ADB_Fastboot_light>fastboot flash rom ady.zip
target reported max download size of 1526722560 bytes
sending 'rom' (309756 KB)...
OKAY [ 14.197s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 50.456s
C:\Users\Lucas\Desktop\htc\ADB_Fastboot_light>
C:\Users\Lucas\Desktop\htc\ADB_Fastboot_light>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
please help me because I can not upload the rom to the phone how do I fix this, where I'm going wrong?
Thank you and sorry for the translation

liufong said:
Went to change the patch on my htc one and the same system lost due to a failure during the process but not now conssigo send a rom to sdcard so I can install the following errors are these.
C:\Users\Lucas\Desktop\htc\ADB_Fastboot_light>fastboot flash rom boot.img
target reported max download size of 1526722560 bytes
sending 'rom' (5552 KB)...
OKAY [ 1.014s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.544s
C:\Users\Lucas\Desktop\htc\ADB_Fastboot_light>fastboot flash rom ady.zip
error: cannot open 'ady.zip'
C:\Users\Lucas\Desktop\htc\ADB_Fastboot_light>fastboot flash rom ady.zip
target reported max download size of 1526722560 bytes
sending 'rom' (309756 KB)...
OKAY [ 14.197s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 50.456s
C:\Users\Lucas\Desktop\htc\ADB_Fastboot_light>
C:\Users\Lucas\Desktop\htc\ADB_Fastboot_light>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
please help me because I can not upload the rom to the phone how do I fix this, where I'm going wrong?
Thank you and sorry for the translation
Click to expand...
Click to collapse
ADB commands do not work when the phone is in FASTBOOT USB mode. It will work while the phone is in the Recovery mode. Take a look at this post on the proper use of FASTBOOT commands. You used the wrong commands which will give you failures.

majmoz said:
ADB commands do not work when the phone is in FASTBOOT USB mode. It will work while the phone is in the Recovery mode. Take a look at this post on the proper use of FASTBOOT commands. You used the wrong commands which will give you failures.
Click to expand...
Click to collapse
Friend believe I posed the question in the wrong way ie I showed up when I enter adb sideload in recovery mode and do the command adb devices it shows that nothing is connected and when I am in fastboot mode and command to do it up which want something that has the zip extension of this error he
Reported target max download size of 1526722560 bytes
sending 'rom' (309756 KB) ...
OKAY [14.197s]
writing 'rom' ...
(bootloader) signature checking ... <------
FAILED (remote: signature verification verify fail) <----
finished. Total time: 50.456s

liufong said:
Friend believe I posed the question in the wrong way ie I showed up when I enter adb sideload in recovery mode and do the command adb devices it shows that nothing is connected and when I am in fastboot mode and command to do it up which want something that has the zip extension of this error he
Reported target max download size of 1526722560 bytes
sending 'rom' (309756 KB) ...
OKAY [14.197s]
writing 'rom' ...
(bootloader) signature checking ... <------
FAILED (remote: signature verification verify fail) <----
finished. Total time: 50.456s
Click to expand...
Click to collapse
Reboot your computer and try the commands again. If that fails, download the files from here, reboot computer and install the files. The post list two guides one for ADB commands and the other for FASTBOOT commands. Read those guides because what you posted in the first post are the incorrect commands for the files you wanted to flash.

error
majmoz said:
Reboot your computer and try the commands again. If that fails, download the files from here, reboot computer and install the files. The post list two guides one for ADB commands and the other for FASTBOOT commands. Read those guides because what you posted in the first post are the incorrect commands for the files you wanted to flash.
Click to expand...
Click to collapse
htc my friend when I go into recovery and then adb sideload and give the command adb devices does not appear in the device list sack 'and why not send any rom nothing pro sdcard, and the time I take wipe cache and wipe it appears in devilwick log E: unable to mount and One drive in the device manager it meets exclamation. Already tried updating and everything and decided not too. So it is not problems with command.

liufong said:
htc my friend when I go into recovery and then adb sideload and give the command adb devices does not appear in the device list sack 'and why not send any rom nothing pro sdcard, and the time I take wipe cache and wipe it appears in devilwick log E: unable to mount and One drive in the device manager it meets exclamation. Already tried updating and everything and decided not too. So it is not problems with command.
Click to expand...
Click to collapse
can you rephrase, i didnt understand anything, but
1- "unable to mount /cache" is completely normal after a fastboot erase cache
2- device manager: FAQ #2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

nkk71 said:
can you rephrase, i didnt understand anything, but
1- "unable to mount /cache" is completely normal after a fastboot erase cache
2- device manager: FAQ #2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
@ nkk71 my htc when I open the recovery and go into adb sideload, give the command adb devices does not appear in the list nothing independent in which pc I put it does not show any device in the list.
Question 2 in the device manager windows 7 when I open the recovery mode appears a One driver with exclamation already tried to update and to no avail.
3 question when I open the recovery mode and give factory reset wipe date and wipe data devilwick appears in log E: unable to mount
Sorry for google translator.

liufong said:
@ nkk71 my htc when I open the recovery and go into adb sideload, give the command adb devices does not appear in the list nothing independent in which pc I put it does not show any device in the list.
Question 2 in the device manager windows 7 when I open the recovery mode appears a One driver with exclamation already tried to update and to no avail.
3 question when I open the recovery mode and give factory reset wipe date and wipe data devilwick appears in log E: unable to mount
Sorry for google translator.
Click to expand...
Click to collapse
I was wondering do you have USB Debugging checked/enabled in Settings -> Developer options? If you don't then you need to enable it because it will prevent you from using ADB commands. If you don't see Developer options in your Settings then you have to enable them. Go to Settings -> About -> Software information -> More -> Build number and press Build number seven (7) times. This will enable Developer options. Back out to Settings and you will see Developer options. One other question are you S-ON?

majmoz said:
I was wondering do you have USB Debugging checked/enabled in Settings -> Developer options? If you don't then you need to enable it because it will prevent you from using ADB commands. If you don't see Developer options in your Settings then you have to enable them. Go to Settings -> About -> Software information -> More -> Build number and press Build number seven (7) times. This will enable Developer options. Back out to Settings and you will see Developer options. One other question are you S-ON?
Click to expand...
Click to collapse
USB Debugging is only needed in a booted ROM, in a custom recovery adb works fine.
liufong said:
@ nkk71 my htc when I open the recovery and go into adb sideload, give the command adb devices does not appear in the list nothing independent in which pc I put it does not show any device in the list.
Question 2 in the device manager windows 7 when I open the recovery mode appears a One driver with exclamation already tried to update and to no avail.
3 question when I open the recovery mode and give factory reset wipe date and wipe data devilwick appears in log E: unable to mount
Sorry for google translator.
Click to expand...
Click to collapse
Yes, google translate is making it a bit difficult, first fix your drivers:
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
for those who like a visual guide:
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
[/HIDE][/INDENT]

\o/
nkk71 said:
USB Debugging is only needed in a booted ROM, in a custom recovery adb works fine.
Yes, google translate is making it a bit difficult, first fix your drivers:
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
for those who like a visual guide:
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
[/HIDE][/INDENT]
Click to expand...
Click to collapse
:cyclops:
@nkk71 your tip drivers worked, now when I go into recovery and then sideload adb adb command I give my htc devices appear in the list, now's the problem see below:
C: \ Users \ Luke \ Desktop \ HTC \ ADB_Fastboot_light> adb usb
error: closed <---
C: \ Users \ Luke \ Desktop \ HTC \ ADB_Fastboot_light> adb devices
List of devices attached
HT346W908334 sideload
C: \ Users \ Luke \ Desktop \ HTC \ ADB_Fastboot_light> adb push HTC.zip / sdcard
error: closed <---
I did something wrong? Thanks and sorry for the translation.

liufong said:
:cyclops:
C: \ Users \ Luke \ Desktop \ HTC \ ADB_Fastboot_light> adb devices
List of devices attached
HT346W908334 sideload
C: \ Users \ Luke \ Desktop \ HTC \ ADB_Fastboot_light> adb push HTC.zip / sdcard See correct command below
error: closed <---
I did something wrong? Thanks and sorry for the translation.
Click to expand...
Click to collapse
Try this command for sideload: adb sideload HTC.zip
Wait until it says 100% then reboot back into recovery to flash the rom.

\o/
majmoz said:
Try this command for sideload: adb sideload HTC.zip
Wait until it says 100% then reboot back into recovery to flash the rom.
Click to expand...
Click to collapse
Friend the command adb sideload worked, finally managed to send a rom phone! kkkk Dude thank you for attention and the strength you gave me and also to thank @ nkk71 Thanks broke a twig