Database Develop

[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

Ok I need help getting back to stock asap!!!

Hi, please can someone help me getting back to stock. I have tried using guides but I am just stumped.
My phone is a UK model unlocked to any network, I have messed around with it a lot and think I have messed up the radios or something as I am only getting Edge connectivity even though all my friends are getting HSPA on the same network, something is just not right!
C:\Users\Nath\Desktop\Fastboot>Fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.56.0000
INFOversion-baseband: 4A.20.3263.16
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: SH3BRW902127
INFOimei: xxxxxxxxxxxxxxxxxxxx
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 3754mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-4dab9d12
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.051s

Soff first. Then you can flash an older RUU..

SaHiLzZ said:
Soff first. Then you can flash an older RUU..
Click to expand...
Click to collapse
Can't get S-OFF have tried and tried, think it's cos my H-BOOT is 1.56

When I try sideloading this is what I get
C:\Users\Nath\Desktop\Fastboot>adb sideload 4.19.401.11.zip
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.

Rumrunner result
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
yES
Type 'Yes' or 'No'
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this w
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (35/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit

simmo0020 said:
Can't get S-OFF have tried and tried, think it's cos my H-BOOT is 1.56
Click to expand...
Click to collapse
There are some known problems with HBoot 1.56 in regards to SOFF.. try Firewater that is known to work
However, me being a noob am not allowed to post external links.. But the link is in this thread.. do let me know if it works..
http://forum.xda-developers.com/showthread.php?t=2633276

shabzbd said:
There are some known problems with HBoot 1.56 in regards to SOFF.. try Firewater that is known to work
However, me being a noob am not allowed to post external links.. But the link is in this thread.. do let me know if it works..
http://forum.xda-developers.com/showthread.php?t=2633276
Click to expand...
Click to collapse
Tried this and just get the whelp this sucks message

Try ADB push instead of sideload, download the 401 gurureset rom, ive used it loads of times, adb push it to your sdcard, then flash it in twrp recovery, select to wipe data and also select stock radio and stock recovery when given the option, once its finished and set up you will be completely stock and get OTA's
adb push (romname).zip /sdcard/ (from within recovery main page)
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Stock ROM version for these types:
modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016

Seanie280672 said:
Try ADB push instead of sideload, download the 401 gurureset rom, ive used it loads of times, adb push it to your sdcard, then flash it in twrp recovery, select to wipe data and also select stock radio and stock recovery when given the option, once its finished and set up you will be completely stock and get OTA's
adb push (romname).zip /sdcard/ (from within recovery main page)
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Stock ROM version for these types:
modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016
Click to expand...
Click to collapse
Just keep getting this
C:\Users\Nath\Desktop\htc one>adb push rom.zip /sdcard
cannot stat 'rom.zip': No such file or directory

simmo0020 said:
Just keep getting this
C:\Users\Nath\Desktop\htc one>adb push rom.zip /sdcard
cannot stat 'rom.zip': No such file or directory
Click to expand...
Click to collapse
you do have fastboot and adb on your computer right ?
you must place the rom.zip file in the same folder as adb and fastboot and then open a command window there, when you type the file name of the zip, it must be exactly the same as the zip file itself, capital letters, lower case etc.
you are also missing another forward slash from the end of your command /sdcard/

Are you root at the moment? This is what i found.. from another thread.. check out this post..
http://forum.xda-developers.com/showpost.php?p=52431720&postcount=10

Seanie280672 said:
you do have fastboot and adb on your computer right ?
you must place the rom.zip file in the same folder as adb and fastboot and then open a command window there, when you type the file name of the zip, it must be exactly the same as the zip file itself, capital letters, lower case etc.
you are also missing another forward slash from the end of your command /sdcard/
Click to expand...
Click to collapse
Ok so a little progress made, I managed to flash the guru reset stock ROM but I still only have EDGE.
Also I notice I am missing a main version. cpId and microp??
INFOversion-bootloader: 1.56.0000
INFOversion-baseband: 4A.21.3263.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: SH3BRW902127
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 3813mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-4dab9d12
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.047s

those were missing from your other output too, but nothing to worry about, mine is missing too, do you get OTA's now ? whith each OTA you should get a radio update too.
when you flashed the guru reset, did you select to install stock recovery and stock radio, did you also select to wipe data ?

Seanie280672 said:
those were missing from your other output too, but nothing to worry about, mine is missing too, do you get OTA's now ? whith each OTA you should get a radio update too.
when you flashed the guru reset, did you select to install stock recovery and stock radio, did you also select to wipe data ?
Click to expand...
Click to collapse
Yeah OTA's are available, is it worth updating?

yes definitely give it a try, download over wifi only not mobile network.
---------- Post added at 01:20 PM ---------- Previous post was at 01:18 PM ----------
Also I forgot to mention, check your APN setting regarding your mobile data being edge only, they could be wrong.

Seanie280672 said:
those were missing from your other output too, but nothing to worry about, mine is missing too, do you get OTA's now ? whith each OTA you should get a radio update too.
when you flashed the guru reset, did you select to install stock recovery and stock radio, did you also select to wipe data ?
Click to expand...
Click to collapse
Yeah I did.
I'm downloading the system update now.
This whole EDGE issue has me super confused.
When I go in to the city I am getting LTE no worries but near where I live I am only getting EDGE even though others around me are getting HSPA, so I know the phone is capable of it so it surely can't be a hardware issue?

simmo0020 said:
Yeah I did.
I'm downloading the system update now.
This whole EDGE issue has me super confused.
When I go in to the city I am getting LTE no worries but near where I live I am only getting EDGE even though others around me are getting HSPA, so I know the phone is capable of it so it surely can't be a hardware issue?
Click to expand...
Click to collapse
Others ? same phone same network ?

simmo0020 said:
When I try sideloading this is what I get
C:\Users\Nath\Desktop\Fastboot>adb sideload 4.19.401.11.zip
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
Click to expand...
Click to collapse
Just FYI, if you want to adb sideload in the future:
You need at least ADB version 1.0.29 to use sideload, yours is outdated, (1.0.26) and the "adb sideload" command was not implemented yet in this version. Most up-to-date version of ADB is 1.0.31

Seanie280672 said:
those were missing from your other output too, but nothing to worry about, mine is missing too, do you get OTA's now ? whith each OTA you should get a radio update too.
when you flashed the guru reset, did you select to install stock recovery and stock radio, did you also select to wipe data ?
Click to expand...
Click to collapse
Seanie280672 said:
Others ? same phone same network ?
Click to expand...
Click to collapse
Different phones same network but here is the weird bit, the only network I seem to be able to use a sim card on effectively out here is Rogers, any others I can't get signal with.
My friends are using a variety of phones on different networks and all have HSPA, Rogers, Telus and Virgin, anytime I try to use a Telus or Virgin sim around here I get nothing, at least with Rogers I get EDGE, in town I had HSPA with Telus and LTE with Rogers.

Still struggling with Data even after going back to sock, in fact really struggling for a signal completely.
Please help!

I messed up pretty bad....

Hey guys I just tried to root my phone and after a few failed attempts I tried to return it to its original condition. Now I have no OS, when powering up it goes on to the HTC logo then nothing. I can access the bootloader and TWRP but that is all.
I have a HTC One M7 running on 4.4.3 with a Vodafone UK contract, any ideas on how to fix this?

rossrfc95 said:
Hey guys I just tried to root my phone and after a few failed attempts I tried to return it to its original condition. Now I have no OS, when powering up it goes on to the HTC logo then nothing. I can access the bootloader and TWRP but that is all.
I have a HTC One M7 running on 4.4.3 with a Vodafone UK contract, any ideas on how to fix this?
Click to expand...
Click to collapse
Sounds like you just need to push a Rom to the phone, please can you connect fastboot usb in the bootloader, then in the fastboot command line type
Code:
fastboot getvar all
And post the out put here, please edit out your serial no. And imei no. Before posting.
Also please confirm which version of twrp you have currently.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Sounds like you just need to push a Rom to the phone, please can you connect fastboot usb in the bootloader, then in the fastboot command line type
Code:
fastboot getvar all
And post the out put here, please edit out your serial no. And imei no. Before posting.
Also please confirm which version of twrp you have currently.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3766mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
Also it wont let me into TWRP now. but it was the latest version.

rossrfc95 said:
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3766mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
Also it wont let me into TWRP now. but it was the latest version.
Click to expand...
Click to collapse
Have you relocked the bootloader? Custom recovery won't boot with a relocked bootloader.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Have you relocked the bootloader? Custom recovery won't boot with a relocked bootloader.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Bootloader is still unlocked

rossrfc95 said:
Bootloader is still unlocked
Click to expand...
Click to collapse
What happens when you try to boot twrp? Have you tried
Code:
fastboot erase cache
It's probably better to flash 2.6.3.3 for now anyway so flash 2.6.3.3 then fastboot erase cache and try boot into twrp.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
What happens when you try to boot twrp? Have you tried
Code:
fastboot erase cache
It's probably better to flash 2.6.3.3 for now anyway so flash 2.6.3.3 then fastboot erase cache and try boot into twrp.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Code:
C:\Users\Ross\Desktop\OneDrivers_Fastboo
ecovery-twrp-2.6.3.3-m7.img
target reported max download size of 151
sending 'recovery' (9184 KB)...
OKAY [ 1.192s]
writing 'recovery'...
OKAY [ 0.855s]
finished. total time: 2.055s
C:\Users\Ross\Desktop\OneDrivers_Fastboo
******** Did you mean to fastboot format
erasing 'cache'...
OKAY [ 0.391s]
finished. total time: 0.393s
I can boot into TWRP now.

rossrfc95 said:
Code:
C:\Users\Ross\Desktop\OneDrivers_Fastboo
ecovery-twrp-2.6.3.3-m7.img
target reported max download size of 151
sending 'recovery' (9184 KB)...
OKAY [ 1.192s]
writing 'recovery'...
OKAY [ 0.855s]
finished. total time: 2.055s
C:\Users\Ross\Desktop\OneDrivers_Fastboo
******** Did you mean to fastboot format
erasing 'cache'...
OKAY [ 0.391s]
finished. total time: 0.393s
I can boot into TWRP now.
Click to expand...
Click to collapse
Ok download this Rom. http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_81.0.zip
Rename the file to rom.zip and put it in your fastboot folder.
Boot the phone to twrp (just on the twrp home screen is fine) connect usb and in the command terminal type
Code:
adb devices
To check adb is working.
Code:
adb push rom.zip /sdcard
the command window will appear unresponsive until the push completes. Once it done Install the Rom with TWRP.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Ok download this Rom.
Rename the file to rom.zip and put it in your fastboot folder.
Boot the phone to twrp (just on the twrp home screen is fine) connect usb and in the command terminal type
Code:
adb devices
To check adb is working.
Code:
adb push rom.zip /sdcard
the command window will appear unresponsive until the push completes. Once it done Install the Rom with TWRP.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
after I went into the bootloader i just plugged my htc back into my computer and now my computer wont recognize the device, I have tried a different wire.

rossrfc95 said:
after I went into the bootloader i just plugged my htc back into my computer and now my computer wont recognize the device, I have tried a different wire.
Click to expand...
Click to collapse
See Q2 in this faq post to get your drivers working again. http://forum.xda-developers.com/showthread.php?p=52135024
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

got it connected now, results...
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>adb devices
List of devices attached
FA381W901618 recovery
Code:
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>adb push rom.zip /sdcard
cannot stat 'rom.zip': No such file or directory
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>

Solved
U need a ROOTed phone and a cable with USB acces,and then u put a room into usb and u mount USB from ur Phone and from there u install the Room u put it on USB
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

BeniHtc said:
U need a ROOTed phone and a cable with USB acces,and then u put a room into usb and u mount USB from ur Phone and from there u install the Room u put it on USB
View attachment 2968014
Click to expand...
Click to collapse
cant i just put one from my computer to my phone?

rossrfc95 said:
cant i just put one from my computer to my phone?
Click to expand...
Click to collapse
Ok so adb is working now, just push the Rom as instructed in my previous post
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 07:11 AM ---------- Previous post was at 06:55 AM ----------
rossrfc95 said:
got it connected now, results...
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>adb devices
List of devices attached
FA381W901618 recovery
Code:
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>adb push rom.zip /sdcard
cannot stat 'rom.zip': No such file or directory
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>
Click to expand...
Click to collapse
Sorry missed this post. Adb is unable to see the file, either it's in the wrong folder or the file name is different to what you typed.
If your sure the file is in the correct folder. And renamed rom.zip.
You have to be careful renaming with file extensions on Windows, it's possible you have a double .zip extension.
Windows appends (automatically adds) file extensions so your rom.zip could be called rom.zip.zip.
Try
Code:
adb push rom.zip.zip /sdcard
or try Removing the .zip from the Rom.zip file name so the name displays only Rom then use the original push command
Code:
adb push rom.zip /sdcard
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Sorry missed this post. Adb is unable to see the file, either it's in the wrong folder or the file name is different to what you typed.
If your sure the file is in the correct folder. And renamed rom.zip.
You have to be careful renaming with file extensions on Windows, it's possible you have a double .zip extension.
Windows appends (automatically adds) file extensions so your rom.zip could be called rom.zip.zip.
Try
Code:
adb push rom.zip.zip /sdcard
or try Removing the .zip from the Rom.zip file name so the name displays only Rom then use the original push command
Code:
adb push rom.zip /sdcard
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Tried that, the only thing thats done anything for me was
Code:
adb push rom.zip /sdcard /rom.zip
Results-
Code:
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot> adb push rom.zip /sdcard /ro
m.zip
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\Ross\Desktop\OneDrivers_Fastboot\Fastboot>

got it working after playing around for a little while today, thanks for your help Danny201281.

m7 issues cant reset, cant use phone

Last night, was charging the phone, woke up was not charged, so i pluged it into a differ charger. then when i turned it on today it said enter password for decrypting phone put in my password for the phone and said unsuccessfull, then it says to factory reset it, it wont reset it at all just stays on rebooting forever, go into bootloader to do reset throws up some errors about cant mount and bitmap etc and well i cant get it to reset, it will turn on and i can go to the settings on the phone and even connect to wifi but i can not get the damn thing to where i can use it.........
E:missing bitmap oem_unlock_bg (Code -1)
E:missing bitmap oem_unlock_bg_yes (Code -1)
E:missing bitmap oem_unlock_bg_no (Code -1)
E:missing bitmap icon_ruu (Code -1)
Backup necessary files in data partition
E:failed to mount /data (Invalid argument).. try emmc mount
Formatting /cache...
Data wipe failed.
basically these are the errors i get for any of the attempts i try.
If i try to do it from inside the phone its stuck on rebooting then throws those errors as well.
htc told me 90-300 dollars to fix it etf

YousufWalton said:
Last night, was charging the phone, woke up was not charged, so i pluged it into a differ charger. then when i turned it on today it said enter password for decrypting phone put in my password for the phone and said unsuccessfull, then it says to factory reset it, it wont reset it at all just stays on rebooting forever, go into bootloader to do reset throws up some errors about cant mount and bitmap etc and well i cant get it to reset, it will turn on and i can go to the settings on the phone and even connect to wifi but i can not get the damn thing to where i can use it.........
E:missing bitmap oem_unlock_bg (Code -1)
E:missing bitmap oem_unlock_bg_yes (Code -1)
E:missing bitmap oem_unlock_bg_no (Code -1)
E:missing bitmap icon_ruu (Code -1)
Backup necessary files in data partition
E:failed to mount /data (Invalid argument).. try emmc mount
Formatting /cache...
Data wipe failed.
basically these are the errors i get for any of the attempts i try.
If i try to do it from inside the phone its stuck on rebooting then throws those errors as well.
htc told me 90-300 dollars to fix it etf
Click to expand...
Click to collapse
Is everything on your phone stock (recovery, kernel, rom?)
Your bootloader is locked/unlocked ?
Do you know hot to use adb / fastboot? If yes, please post the output of "fastboot getvar all" but don't post the imei and serialno. If you don't know how to use fastboot at least write down all info you can see from the bootloader menu.

every thing is completely stock, nothing has been changed on the phone. Ive been trying to do the fastboot command,
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fasboot gerval all
'fasboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.531.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *******************
(bootloader) imei: **********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.113s
C:\Program Files (x86)\Minimal ADB and Fastboot>
from the stand point of fastboot menu fastboot recovery factory reset simlock check smartsd image crc and show barcode fastboot says boat loader reboot reboot boot loader and power down,
top part says locked
m7_ul ship s-on
hboot 1.61 0000
radio 4t.35 3218.16
open dsp-v35 120.274.0718
emmc boot 2048mb
feb 2015 18:39:53.0

i also have an otg cable and flash drive

i went ahead and unlocked the boot loader

well i thought i did and it still says locked =/

Try to flash the 7.18.531.2 ruu, this will reset your phone back to stock
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
file and instruction in post #1

let me try this

i am running into the issue that others have on that post, adb and fastboot wither say there is a dll issue or that it just opens and instantly closes. ive added the file and ive also added the way windows searches it in advanced system settings not sure what to do at this point.

YousufWalton said:
i am running into the issue that others have on that post, adb and fastboot wither say there is a dll issue or that it just opens and instantly closes. ive added the file and ive also added the way windows searches it in advanced system settings not sure what to do at this point.
Click to expand...
Click to collapse
What dll issue exactly, be more precise, we need to know the exact error not only that there is an error...
Did you download htc_fastboot.exe and saved it in your fastboot / adb folder where the other required files are (AdbWinApi.dll and AdbWinUsbApi.dll) ?

YousufWalton said:
i am running into the issue that others have on that post, adb and fastboot wither say there is a dll issue or that it just opens and instantly closes. ive added the file and ive also added the way windows searches it in advanced system settings not sure what to do at this point.
Click to expand...
Click to collapse
alray said:
What dll issue exactly, be more precise, we need to know the exact error not only that there is an error...
Did you download htc_fastboot.exe and saved it in your fastboot / adb folder where the other required files are (AdbWinApi.dll and AdbWinUsbApi.dll) ?
Click to expand...
Click to collapse
Probably missing the http://www.microsoft.com/en-us/download/details.aspx?id=29
Unless I'm mistaken htc_fastboot needs that too

installed that distributable you linked, still adb flys through lots of text and then closed it self. when i go in through cmd to the folder says error cant process file. and yes i put the htc fastboot in the same folder as my adb/fastboot

YousufWalton said:
installed that distributable you linked, still adb flys through lots of text and then closed it self. when i go in through cmd to the folder says error cant process file. and yes i put the htc fastboot in the same folder as my adb/fastboot
Click to expand...
Click to collapse
you can't "double click" adb, it's a command line tool
.
copy/paste us the command prompt output
.
try running Command Prompt as admin

c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\YousufWalton>cd c:/ADB
c:\ADB>fastboot flash zip RUU.zip
error: preprocess_file : Cannot open file RUU.zip
c:\ADB>adb
Android Debug Bridge version 1.0.32
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <specific device> - directs command to the device or emulator with the given
serial number or qualifier. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push [-p] <local> <remote>
- copy file/dir to device
('-p' to display the transfer progress)
adb pull [-p] [-a] <remote> [<local>]
- copy file/dir from device
('-p' to display the transfer progress)
('-a' means copy timestamp and mode)
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the following format:
<serial> " " <local> " " <remote> "\n"
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fails
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb reverse --list - list all reverse socket connections from device
adb reverse <remote> <local> - reverse socket connections
reverse specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
adb reverse --norebind <remote> <local>
- same as 'adb reverse <remote> <local>' but fails
if <remote> is already reversed.
adb reverse --remove <remote>
- remove a specific reversed socket connection
adb reverse --remove-all - remove all reversed socket connections from device
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-lrtsd] <file>
adb install-multiple [-lrtsdp] <file...>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
(-p: partial application install)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|-nosystem] [<packages
...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default
is noobb.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system and /vendor (if present) partitions on the device read-w
rite
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, /system, /vendor (if present), and /data partitions will be updated.
- If it is "system", "vendor" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
c:\ADB>fastboot flash RUU.zip
unknown partition 'RUU.zip'
error: cannot determine image filename for 'RUU.zip': No error
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
c:\ADB>

YousufWalton said:
c:\ADB>fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
Click to expand...
Click to collapse
have you checked MD5 on the download to make sure it's not corrupt
.
are you sure the filename is correct? "cannot open/load/stat" usually happens when you have a wrong file name (maybe you renamed it to ruu.zip.zip); use DIR and tab-completion to check
.
I also dont see a "fastboot oem rebootRUU" command, before the "fastboot flash zip ruu.zip"

when i do the fastboot oem rebootRUU it boots to the decrypt screen in android, when i do the flash from the cmd line it tells me this.
C:\Users\YousufWalton>CD c:/ADB
c:\ADB>fastboot flash zip RUU.zip
sending 'zip'... (43290 KB) OKAY
sending time = 3.983 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILbattery low
FAILED (remote: battery low)
Execution time is 10(s)
c:\ADB>fastboot flash zip RUU.zip
sending 'zip'... (43290 KB) OKAY
sending time = 3.954 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 11(s)
c:\ADB>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 40(ms)
c:\ADB>

oem reboot ruu does this
c:\ADB>fastboot oem rebootRUU
< waiting for device >

Well first charge your battery obviously, and secondly you need to be in ruu mode, to be able to flash ruu.zip
The first output looked pretty ok, except for the low battery, and you need to rebootRUU before flashing
Sent from my HTC One M9 using Tapatalk

gets to saying failed can not remote or something like that

YousufWalton said:
gets to saying failed can not remote or something like that
Click to expand...
Click to collapse
well, your last error message was pretty clear:
Code:
FAILbattery low
FAILED (remote: battery low)
fastboot detected (or "thinks") that your battery is too low for an RUU flash.... which BTW, if it get's interrupted at the precise millisecond, will turn your phone into a brick,
but i do have to say, I never heard of fastboot returning an error: failed "or something like that"
anyway, it's your phone, do with it as you please, and good luck, hope you get it fixed.

HTC One M7 OTA Failed with Red Triangle and Exclamation.

Hi,
I have a htc one m7 and was pushed the lollipop update and chose to download and install it. After doing so the phone rebooted and went to the red triangle and exclamation error. Been doing some research and based on that it seems that i have the wrong stock recovery on the device.
Observation:
1. - I recently got the phone and it was intended to be an International variant however when it turns on it would normally boots to htc logo then T-Mobile. My concern with this is that the phone doesn't show any T-mobile branding on the casing.
2. - I went into bootloader and realize that the CID is set to 11111111 instead of its own info. It seems that the phone was originally tampered with and the t-mobile ruu was installed thus the supercid.
Is there a way to revert to its previous settings? I have already ran factory reset and clear cache partition but the problem still persists. How can I fix this problem?
Thanks

360fifa said:
Hi,
I have a htc one m7 and was pushed the lollipop update and chose to download and install it. After doing so the phone rebooted and went to the red triangle and exclamation error. Been doing some research and based on that it seems that i have the wrong stock recovery on the device.
Observation:
1. - I recently got the phone and it was intended to be an International variant however when it turns on it would normally boots to htc logo then T-Mobile. My concern with this is that the phone doesn't show any T-mobile branding on the casing.
2. - I went into bootloader and realize that the CID is set to 11111111 instead of its own info. It seems that the phone was originally tampered with and the t-mobile ruu was installed thus the supercid.
Is there a way to revert to its previous settings? I have already ran factory reset and clear cache partition but the problem still persists. How can I fix this problem?
Thanks
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" (remove your imei and serialno)

INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.10.531.10
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: 00000000000
INFOimei: 00000000000000
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN071****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4311mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.151s
I removed the imei# and the serial #. Let me know if there's any other info required

alray said:
Post the output of "fastboot getvar all" (remove your imei and serialno)
Click to expand...
Click to collapse
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.10.531.10
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: 00000000000
INFOimei: 00000000000000
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN071****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4311mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.151s
I removed the imei and serial numbers, let me know if there's any other info required.
Thanks a lot.

360fifa said:
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.10.531.10
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: 00000000000
INFOimei: 00000000000000
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN071****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4311mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.151s
I removed the imei and serial numbers, let me know if there's any other info required.
Thanks a lot.
Click to expand...
Click to collapse
You could simply change the cid to HTC__001 and flash the 7.19.401.22 ruu.zip, this is the unlocked version.
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
Then flash the 7.19.401.22 ruu:http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
instructions at post 1, file at post 2
flashing the ruu will wipe your phone so backup your important files before

alray said:
You could simply change the cid to HTC__001 and flash the 7.19.401.22 ruu.zip, this is the unlocked version.
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
Then flash the 7.19.401.22 ruu:http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
instructions at post 1, file at post 2
flashing the ruu will wipe your phone so backup your important files before
Click to expand...
Click to collapse
thanks for your quick reply. i will download the file and proceed with the update. Quick question though... Installing this RUU is it based on a specific carrier or for the International variant? Also, will will this allow OTA in the future? or not recommended?
Thanks a lot.. i ill report once I have proceeded..

alray said:
You could simply change the cid to HTC__001 and flash the 7.19.401.22 ruu.zip, this is the unlocked version.
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
Then flash the 7.19.401.22 ruu:http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
instructions at post 1, file at post 2
flashing the ruu will wipe your phone so backup your important files before
Click to expand...
Click to collapse
I'm trying to do backup of the phone however it doesn't seem to be working....
This is the info from the adb command line:
C:\Users\diego\Desktop\ADB-Windows (1)>adb devices
List of devices attached
C:\Users\diego\Desktop\ADB-Windows (1)>adb backup -all -f C:\Users\diego\Desktop
\ADB-Windows (1)\backup.ab
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Users\diego\Desktop\ADB-Windows (1)>
Am I missing something?

360fifa said:
thanks for your quick reply. i will download the file and proceed with the update. Quick question though... Installing this RUU is it based on a specific carrier or for the International variant? Also, will will this allow OTA in the future? or not recommended?
Thanks a lot.. i ill report once I have proceeded..
Click to expand...
Click to collapse
This ruu is the international unlocked version (no carrier) and yes you'll be able to receive ota updates, you'll get one right after flashing the ruu (7.19.401.30)
360fifa said:
I'm trying to do backup of the phone however it doesn't seem to be working....
This is the info from the adb command line:
C:\Users\diego\Desktop\ADB-Windows (1)>adb devices
List of devices attached
C:\Users\diego\Desktop\ADB-Windows (1)>adb backup -all -f C:\Users\diego\Desktop
\ADB-Windows (1)\backup.ab
Android Debug Bridge version 1.0.26
Am I missing something?
Click to expand...
Click to collapse
First your android sdk tools are outdated. Latest version of adb is 1.0.32. You can get the latest tools here: https://developer.android.com/sdk/index.html#Other
To use adb, the phone must be booted in the OS with "USB Debugging" option turned on from the developer option menu or you can use adb when booted in TWRP recovery. If you still can't see the attached device with "adb devices" then its probably a driver issue. Make sure you have the latest htc driver installed on your computer and make sure your don't have htc sync installed on your computer.
I'm pretty sure that "adb backup -all" command is not available for the M7. You can backup your internal storage using "adb pull /sdcard C:\Users\diego\Desktop\MyBackup". This will backup your data from the sdcard but not your app / app data. If you really want your apps and app data backed-up, you can use Titanium backup from the playstore.

Ok thanks bro. I will have it sorted and let you know how it turns out.
Sent from my Desire HD using XDA Free mobile app

Thank you very much for your assistance. It worked perfectly!

360fifa said:
Thank you very much for your assistance. It worked perfectly!
Click to expand...
Click to collapse
Your welcome, glad to know everything is fine now :highfive:

Highfive
Sent from my HTC One using XDA Free mobile app

alray said:
Your welcome, glad to know everything is fine now :highfive:
Click to expand...
Click to collapse
Hi bro,
I'm trying to backup the apps and data off my old htc desire hd, however for some reason im not able to. I'm assuming that its because the htc one isn't rooted as Titanium backup is what I used for backup. I have since tried using adb but no luck so far.
Firstly, this is what happens when I run adb devices...
c:\android-sdk-windows\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
c:\android-sdk-windows\platform-tools>
If i try running the backup commands this is what happens....
c:\android-sdk-windows\platform-tools>adb backup -f backup.ab -apk -shared -all -nosystem
adb: unable to connect for backup: device '<null>' not found
c:\android-sdk-windows\platform-tools>
i would like to backup the M7 as it is due that if I unlock the bootloader I will loose apps and data + photos. I've already sorted the unlock code but can't get the phone backed up.. Any ideas I could try?
Thanks.

hello.
i have this one m7 (unrooted) which boots, i see splash screen (and after a while it says "process system isn't responding. do you want to close it? wait / ok") i am able to get into the recovery mode, its s-on. but computer does not recognize the device even tough i've installed the drivers.
since i am not familiar with htc devices, i am a sammy user, i found how to turn s-off and flash roms, but no clue with a issue like this.
only thing i've done was installing championship manager. after that pohne got hot and this is the point i am currently in.
could you guys please help me?

same thread
Hi,
i've a liquidsmooth rom (rooted), and few days ago i receive this message:
postimg.org/image/eyc5lurnp/
Android L Upgrade for user/release-keys
This software will upgrade your HTC One M7 Google Play Edition to Android 5.1 ( LMY47O.H9), which address the security vulnerability. To apply this update, you must have at least 500MB free on your device.
Downloading updates over a mobile network o while roaming may cause additional charges.
Click to expand...
Click to collapse
i can update this 5.1 LMY47O.H9 firmware by another way?
in any case, i want to stop receive this message.
TY

360fifa said:
Hi bro,
I'm trying to backup the apps and data off my old htc desire hd, however for some reason im not able to. I'm assuming that its because the htc one isn't rooted as Titanium backup is what I used for backup. I have since tried using adb but no luck so far.
Firstly, this is what happens when I run adb devices...
c:\android-sdk-windows\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
----> no devices detected here
c:\android-sdk-windows\platform-tools>
If i try running the backup commands this is what happens....
c:\android-sdk-windows\platform-tools>adb backup -f backup.ab -apk -shared -all -nosystem
adb: unable to connect for backup: device '<null>' not found
---> Because there is no device detected
c:\android-sdk-windows\platform-tools>
i would like to backup the M7 as it is due that if I unlock the bootloader I will loose apps and data + photos. I've already sorted the unlock code but can't get the phone backed up.. Any ideas I could try?
Thanks.
Click to expand...
Click to collapse
First your phone isn't detected by adb so adb commands won't work. Make sure you have the drivers installed correctly, that usb debuging is turned on from the developer option menu and that your phone screen is unlocked when connected to the computer.
If your phone is synced with google, all your apps will be re-installed automatically after the wipe. You can backup your pictures using
Code:
adb pull /data/media/0/DCIM C:\backup\
Apps that are synced with google or facebook for example, will have their data restored when reconnected.
For "adb backups", I can't really help, never used these commands to backup/restore my phones. Always used "adb pull" or made a backup in recovery since I always unlock my phones before I use them. The only thing I can say is that I tried it on my phone and it looks like it was working (got a screen on my phone telling me that a backup was being created and a backup.ab file was created in my sdk tools folder).
---------- Post added at 01:27 PM ---------- Previous post was at 01:23 PM ----------
rukenau said:
hello.
i have this one m7 (unrooted) which boots, i see splash screen (and after a while it says "process system isn't responding. do you want to close it? wait / ok") i am able to get into the recovery mode, its s-on. but computer does not recognize the device even tough i've installed the drivers.
since i am not familiar with htc devices, i am a sammy user, i found how to turn s-off and flash roms, but no clue with a issue like this.
only thing i've done was installing championship manager. after that pohne got hot and this is the point i am currently in.
could you guys please help me?
Click to expand...
Click to collapse
When your phone is connected to your computer, reboot it in bootloader / fastboot usb mode. Open your windows device manager and check if the phone is somehow detected (post a screenshot of your device manager). If the phone is detected, use "fastboot getvar all" commands and post the output here (remove your IMEI and Serialno before posting).

alray said:
First your phone isn't detected by adb so adb commands won't work. Make sure you have the drivers installed correctly, that usb debuging is turned on from the developer option menu and that your phone screen is unlocked when connected to the computer.
If your phone is synced with google, all your apps will be re-installed automatically after the wipe. You can backup your pictures using
Code:
adb pull /data/media/0/DCIM C:\backup\
Apps that are synced with google or facebook for example, will have their data restored when reconnected.
For "adb backups", I can't really help, never used these commands to backup/restore my phones. Always used "adb pull" or made a backup in recovery since I always unlock my phones before I use them. The only thing I can say is that I tried it on my phone and it looks like it was working (got a screen on my phone telling me that a backup was being created and a backup.ab file was created in my sdk tools folder).
---------- Post added at 01:27 PM ---------- Previous post was at 01:23 PM ----------
When your phone is connected to your computer, reboot it in bootloader / fastboot usb mode. Open your windows device manager and check if the phone is somehow detected (post a screenshot of your device manager). If the phone is detected, use "fastboot getvar all" commands and post the output here (remove your IMEI and Serialno before posting).
Click to expand...
Click to collapse
Ok thanks. I believe the drivers were installed correctly. Is there a way to verify? I have Windows 7. I have also installed twrp recovery and tried installing supersu from the play store it said that the binaries were missing but it can't seem to install..
I'm on android 5.0.2 with twrp 2.8.7.0. Is there anything that can be done?
Thanks again.
Sent from my HTC One using XDA Free mobile app

360fifa said:
Ok thanks. I believe the drivers were installed correctly. Is there a way to verify? I have Windows 7.
Click to expand...
Click to collapse
Connect your phone to your computer, open your windows devices manager and look for your phone: Android USB devices --> My HTC. Post a screenshot of your device manager if you are unsure.
I have also installed twrp recovery and tried installing supersu from the play store it said that the binaries were missing but it can't seem to install..
I'm on android 5.0.2 with twrp 2.8.7.0. Is there anything that can be done?
Click to expand...
Click to collapse
Flash supersu 2.46 using twrp recovery: https://download.chainfire.eu/696/SuperSU

alray said:
Connect your phone to your computer, open your windows devices manager and look for your phone: Android USB devices --> My HTC. Post a screenshot of your device manager if you are unsure.
Flash supersu 2.46 using twrp recovery: https://download.chainfire.eu/696/SuperSU
Click to expand...
Click to collapse
Hi,
attached is the screenshot of the device manager.
UPdated: I'm not sure if its becuz I was using adb from the fastboot usb in bootloader why it was coming up, howver I ran the command while booted into the device and it came up.
The supersu file was flashed successfully and the phone is now rooted. Thank you very again for your help.

360fifa said:
Hi,
attached is the screenshot of the device manager.
Click to expand...
Click to collapse
Everything looks fine, the phone is detected correctly.
UPdated: I'm not sure if its becuz I was using adb from the fastboot usb in bootloader why it was coming up, howver I ran the command while booted into the device and it came up.
Click to expand...
Click to collapse
ADB commands only works from a booted rom with USB Debug option turned on or from a booted custom recovery. ADB commands never works when in bootloader, only fastboot commands
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}