Database Develop

[Q] Soft Brick - ADB Push/Sideload; ROM is "corrupt"

[SOLVED]
Hello gentlemen,
I'm the noob that wiped his OS without installing a new one--yea, that guy. :laugh:
Long story short: I'm using TWRP and trying to sideload or push via ADB a new ROM onto the M7. I've tried a stock rom and two other well renowned ROMS. Each time, though it pushes over or sideloads, it fails install because the file is "corrupt." I searched the forums and web to get up to where I'm at, but can't get further. I also tried that other recovery CWM or whatever it is--that one had a similar error, though it didn't say corrupt (I can get that info if it'd help you help me).
Thanks in advance. I'll send some bitcoin to whoever gets my case solved. :fingers-crossed:
Code in TWRP is as follows:
Updating partition details...
Full Selinux support is present.
Starting ADB sideload feature...
Installing '/data/media/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
E: Zip file is corrupt!
Updating partition details...

seth22h said:
Hello gentlemen,
I'm the noob that wiped his OS without installing a new one--yea, that guy. :laugh:
Long story short: I'm using TWRP and trying to sideload or push via ADB a new ROM onto the M7. I've tried a stock rom and two other well renowned ROMS. Each time, though it pushes over or sideloads, it fails install because the file is "corrupt." I searched the forums and web to get up to where I'm at, but can't get further. I also tried that other recovery CWM or whatever it is--that one had a similar error, though it didn't say corrupt (I can get that info if it'd help you help me).
Thanks in advance. I'll send some bitcoin to whoever gets my case solved. :fingers-crossed:
Code in TWRP is as follows:
Updating partition details...
Full Selinux support is present.
Starting ADB sideload feature...
Installing '/data/media/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
E: Zip file is corrupt!
Updating partition details...
Click to expand...
Click to collapse
Your output of fastboot getvar all (remove IMEI) .. also the exact command you are running for sideload?

SaHiLzZ said:
Your output of fastboot getvar all (remove IMEI) .. also the exact command you are running for sideload?
Click to expand...
Click to collapse
getvar all:
seths-air:android sethhoskins$ ./fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.17
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34HW902411
(bootloader) imei: lololololololol
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.064s
-----------
As for the sideload, i'm following a set of instructions, "How to Fix a Soft-Bricked HTC One by Flashing a New ROM via ADB" from HTC-One Wonder How To website.
It seems to work and send through. In terminal:
./adb kill-server
./adb usb
./adb devices (to ensure device shows up)
./adb sideload *name of ROM*
Then sideload starts, showing percent complete, etc. Then once complete, it fails in the device with the TWRP output in the OP.

Change CID to BS_US001 and flash this while in bootloader mode.. http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
You will need a Windows machine..

SaHiLzZ said:
Change CID to BS_US001 and flash this while in bootloader mode..
You will need a Windows machine..
Click to expand...
Click to collapse
How do I change the CID?
What am I flashing there? What ROM/version of android?
No way to do this on a mac? (No windows, no access to one)

seth22h said:
How do I change the CID?
What am I flashing there? What ROM/version of android?
No way to do this on a mac? (No windows, no access to one)
Click to expand...
Click to collapse
The same way you changed it to 11111111
You were going to be flashing a RUU of the same version as per your fastboot output main-ver. However, this is this file that I found that you can use on a mac.
http://forum.xda-developers.com/showthread.php?t=2460534
Download it.. and flash it with..
fastboot oem rebootRUU
fastboot flash zip filename.zip
fastboot flash zip filename.zip (twice.)
fastboot reboot

SaHiLzZ said:
The same way you changed it to 11111111
You were going to be flashing a RUU of the same version as per your fastboot output main-ver. However, this is this file that I found that you can use on a mac.
http://forum.xda-developers.com/showthread.php?t=2460534
Download it.. and flash it with..
fastboot oem rebootRUU
fastboot flash zip filename.zip
fastboot flash zip filename.zip (twice.)
fastboot reboot
Click to expand...
Click to collapse
Sorry man, I didn't change it to '111111111'. I bought this thing used and it was already unlocked. Please help me out on that.
I'll then try those commands.
So that will install a new OS? (I was convince by the internets I had to use ADB because I have no OS on the device and it's wiped).
Thanks man!

Read this, its my thread and I did the same thing myself, its much easier to do it this way than sideload.
http://forum.xda-developers.com/showthread.php?t=2757977

Seanie280672 said:
Read this, its my thread and I did the same thing myself, its much easier to do it this way than sideload.
http://forum.xda-developers.com/showthread.php?t=2757977
Click to expand...
Click to collapse
I tried adb push. The problem is the .zip file keeps failing to install because it's "corrupt."

Try downloading the zip file again, other than that try and get hold of the guru reset zip for your phone, however as you are S-OFF you can download any Rom for your phone and push it and flash it.

Fastboot oem writecid BS_US001

Seanie280672 said:
Try downloading the zip file again, other than that try and get hold of the guru reset zip for your phone, however as you are S-OFF you can download any Rom for your phone and push it and flash it.
Click to expand...
Click to collapse
I tried re-downloading multiple ROM multiple times.

SaHiLzZ said:
Fastboot oem writecid BS_US001
Click to expand...
Click to collapse
Thanks for the command. So the only way you know of to fix this is on a Windows?

seth22h said:
Thanks for the command. So the only way you know of to fix this is on a Windows?
Click to expand...
Click to collapse
No .. my second reply is with a zip file. Its higher than what you have but as it is a zip file, it will work on MAC

SaHiLzZ said:
No .. my second reply is with a zip file. Its higher than what you have but as it is a zip file, it will work on MAC
Click to expand...
Click to collapse
Sorry -- forgot you listed another. I will try this after work today and follow up.

SaHiLzZ said:
The same way you changed it to 11111111
You were going to be flashing a RUU of the same version as per your fastboot output main-ver. However, this is this file that I found that you can use on a mac.
http://forum.xda-developers.com/showthread.php?t=2460534
Download it.. and flash it with..
fastboot oem rebootRUU
fastboot flash zip filename.zip
fastboot flash zip filename.zip (twice.)
fastboot reboot
Click to expand...
Click to collapse
So I downloaded that RUU, but it was some weird video file..?
[coldhell]_Rozen_Maiden_2013_EP03_v2_[2001BCE4].mkv.002
Weird. Need different link.

deleted........

SaHiLzZ said:
No .. my second reply is with a zip file. Its higher than what you have but as it is a zip file, it will work on MAC
Click to expand...
Click to collapse
Tried it with a different ROM (sorry, impatient) and it failed:
seths-air:android sethhoskins$ ./Fastboot oem writecid BS_US001
...
(bootloader) Start Verify: 0
OKAY [ 0.022s]
finished. total time: 0.022s
seths-air:android sethhoskins$ ./fastboot devices
HT34HW902411 fastboot
seths-air:android sethhoskins$ ./fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
seths-air:android sethhoskins$ ./fastboot flash zip M7_UL_JB43_50_Cingular_3.10.502.2.zip
./fastboot flash zip M7_UL_JB43_50_Cingular_3.10.502.2.zip
./fastboot rebootsending 'zip' (1153504 KB)...
OKAY [ 46.191s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 46.683s
seths-air:android sethhoskins$ ./fastboot flash zip M7_UL_JB43_50_Cingular_3.10.502.2.zip
sending 'zip' (1153504 KB)...
OKAY [ 46.531s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 47.026s
seths-air:android sethhoskins$ ./fastboot reboot
rebooting...
finished. total time: 0.035s

X.X.502.X - CINGULAR/ATT US - needs a CID of CWS__001
You can try that
---------- Post added at 12:53 AM ---------- Previous post was at 12:49 AM ----------
Alternate link> http://www.htc1guru.com/dld/ruu-zip...r_brightstarus_wwe_3-22-1540-1-decrypted-zip/< This one Needs BS_US001 as your CID

SaHiLzZ said:
X.X.502.X - CINGULAR/ATT US - needs a CID of CWS__001
You can try that
---------- Post added at 12:53 AM ---------- Previous post was at 12:49 AM ----------
Alternate link> http://www.htc1guru.com/dld/ruu-zip...r_brightstarus_wwe_3-22-1540-1-decrypted-zip/< This one Needs BS_US001 as your CID
Click to expand...
Click to collapse
Downloading now. That's the same CID as before, by the way.
I'm going with the link RUU, not the one you named (and didn't link). Same command as before.
All correct?

[Q] Please help me try to un soft brick HTC One - KK, with sense 6 [SOLVED!!!!! THX]

Hi, I'm new to the site so I apologize if this particular problem has been solved somewhere - but I cannot find it.
My phone was running fine - it WAS STOCK with all the latest kit kat OS - including sense 6 (the one that has the greenish highlights versus the blue ones for blink feed etc.)
My phone is from Thailand - I guess it is the Asia or SEA version.
After I restarted the phone the other morning, it just went into the boot loop - white screen, saying powered by android - and then the HTC logo - with beats audio - over and over again.
I tried to do a hard reset - it didn't seem to work.
I then started to investigate - downloaded the RUU file etc - I can get the phone into the fastboot mode and get it talking to the computer - but then I got a 155 error when I tried to run the RUU file on to the phone.
Then I went to the HTCdev site and managed to UNLOCK the phone - it is still S-ON - and ran the RUU again - and with the same result.
It may be that I need to S- OFF the phone or run the TWRP thing on the side, but I do not know how to do this, or if it is the right thing to do - but I don't want to do anymore until I discuss with someone here - I am currently on holidays for a few more weeks in Australia, and will return to Thailand - the phone is still under warranty - but I would like to try to fix it and get it working before then.
At the very least, I would like to return it completely to stock - or at least LOCK it again - so that if I cannot fix it now, maybe I can submit it under warranty in a few more weeks. (but I would like to try to get the phone working now).
Any help someone can give would be great.
Thank you very much.

This is the information that comes up if I type the getvar command - I just did this because I saw others asked for it on other threads, in case it helps...
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.12.707.104
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__044
battery-status: good
battery-voltage: 4303mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
al time: 0.048s

204
Dear people, I am getting desperate here - I have been told by Thailand HTC service that once my bootloader has been unlocked, it is no longer covered under warranty - so I am getting anxious to try to unbrick my phone....
further to the above - this is what i have done/tried...
I have downloaded the latest TWRP image and put it in the same folder as the adb fastboot file - ran the command to flash the recovery image - and it cannot read the file.
FYI, when I type in fastboot devices, it does register that the phone is connected.
I have tried to flash other RUU exe files for my phone - but there does not seem to be the right EXE file anywhere that I can find.
my phone is still in S ON.
Ideally, I just want my phone to get back to stock and hopefully relock or return to stock locked status the bootloader - I understand that I may need to perform S OFF to do this - however I can't seem to find the process for doing all this for my particular situation.
I have looked around a lot for tutorials etc to do this - but cannot seem to find something cohesive from start to finish for my problem.
I am not very computer literate - but I can follow clear instructions.
If anyone can help, I would be very grateful.
Cheers....

Just follow the return to stock guide. The 707 in your firmware version is the important bit.

gawoz said:
This is the information that comes up if I type the getvar command - I just did this because I saw others asked for it on other threads, in case it helps...
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-main: 5.12.707.104
version-misc: PVT SHIP S-ON
product: m7_u
modelid: PN0711000
cidnum: HTC__044
Click to expand...
Click to collapse
The above is all that matters
Your already on the new Firmware and S-On ... theirs no RUU that will help you.
use these instructions I just posted in another thread
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=One_5.11.401.10_odexed.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

Hi - many thanks for this - I feel that there is something simple that is going wrong - when I download the TWRP file - and put it in the same folder as fastboot etc - this is the result I get - cannot open:
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>fastboot devices
MB336W900370 fastboot
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.
3.4-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.4-m7.img'
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>
I also tried the very latest TWRP file on the techerrata site - same result.
Is there something else that might be going wrong here? For some reason, the phone is having trouble with the img files. I also tried a CWM image file too - same result.
Any help most welcome and thanks for your assistance so far....

Did you follow clsA 1st instruction - UNLOCK THE BOOTLOADER FIRST.
You cant flash anything with that locked.

You probably need to type the full path to the file, or to put the file in the same directory as the shell is running from (you can see the directory before the command prompt).

Seanie280672 said:
Did you follow clsA 1st instruction - UNLOCK THE BOOTLOADER FIRST.
You cant flash anything with that locked.
Click to expand...
Click to collapse
Hi - yes - I used the HTC Dev site to successfully unlock the bootloader a few days ago.
I believe I did clear the cache at some point yesterday while trying to find a solution to this - but this was after I has downloaded the TWRP IMG file and failed to load it to the phone - the message has been the same - cannot open.
I am using windows 8.1 OS.
Other info:
When I select IMAGE CRC on phone - it calculates - then gives:
rpm: 0x403AD75
sbl1:0xFE316EA5
sbl2:0x EBF06ECC
sbl3:0x3A410C2C
tz: 0xC73B0D94
radio:0xE9CC6D25
hboot: 0x0
boot: 0x0
recovery: 0x0
system 0x0
This is the latest GETVAR information - I notice that now the baseband version says N/A...I don't know what this means - maybe it is a result of the cache wipe? Maybe i have messed something up? But, the FASTBOOT command would not read the IMG file before this change.
version: 0.5
version-bootloader: 1.57.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main: 5.12.707.104
version-misc: PVT SHIP S-ON
serialno: xxxxxxxxxxxxxxxxx
imei: xxxxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__044
battery-status: good
battery-voltage: 4313mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Again - thank you for any help you may be able to give...

fenstre said:
You probably need to type the full path to the file, or to put the file in the same directory as the shell is running from (you can see the directory before the command prompt).
Click to expand...
Click to collapse
Hi - I have put the img file (which I have renamed TWRP.img) in the platform-tools folder - the fastboot file is also in this folder - see below....
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>
...and when I try to load/run it - I type the following:
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools> fastboot flash recovery TWRP.img
....then I get the error - cannot open 'TWRP.img'

gawoz said:
Hi - I have put the img file (which I have renamed TWRP.img) in the platform-tools folder - the fastboot file is also in this folder - see below....
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>
...and when I try to load/run it - I type the following:
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools> fastboot flash recovery TWRP.img
....then I get the error - cannot open 'TWRP.img'
Click to expand...
Click to collapse
Looks like it is NOT in the same folder or atleast not the same name.
Can you type dir, and post a screenshot of it ?
---------- Post added at 12:03 PM ---------- Previous post was at 12:02 PM ----------
Also, because you are On 1.57 HBOOT, chances of going back to LOCKED bootloader by S-OFF are slim to none.

SaHiLzZ said:
Looks like it is NOT in the same folder or atleast not the same name.
Can you type dir, and post a screenshot of it ?
Click to expand...
Click to collapse
indeed, "a powerful ally that dir command can be"
if I had to take a wild guess, it's probably in the same folder but with a .img.img extension, courtesy of Windows Explorer

SaHiLzZ said:
Looks like it is NOT in the same folder or atleast not the same name.
Can you type dir, and post a screenshot of it ?
---------- Post added at 12:03 PM ---------- Previous post was at 12:02 PM ----------
Also, because you are On 1.57 HBOOT, chances of going back to LOCKED bootloader by S-OFF are slim to none.
Click to expand...
Click to collapse
nkk71 said:
indeed, "a powerful ally that dir command can be"
if I had to take a wild guess, it's probably in the same folder but with a .img.img extension, courtesy of Windows Explorer
Click to expand...
Click to collapse
LOL this guy sent me a PM and I get to the thread and see the entire team is here to help where's @alray.
thanks guys .... I'm not positive the bootloader is still unlocked .. he relocked it to run a RUU.

clsA said:
LOL this guy sent me a PM and I get to the thread and see the entire team is here to help where's @alray.
thanks guys .... I'm not positive the bootloader is still unlocked .. he relocked it to run a RUU.
Click to expand...
Click to collapse
@clsA @SaHiLzZ @alray all in one thread... looks like trouble... i'm better go watch a movie/series (a few come to mind )
but for the OP, don't know if you have a locked (remote failed) or unlocked bootloader, but "cannot load" = MyFileNameIsWrong (or isn't even in the correct folder)
try that DIR command in command prompt to see what the filenames are

gawoz said:
Hi - yes - I used the HTC Dev site to successfully unlock the bootloader a few days ago.
I believe I did clear the cache at some point yesterday while trying to find a solution to this - but this was after I has downloaded the TWRP IMG file and failed to load it to the phone - the message has been the same - cannot open.
I am using windows 8.1 OS.
Other info:
When I select IMAGE CRC on phone - it calculates - then gives:
rpm: 0x403AD75
sbl1:0xFE316EA5
sbl2:0x EBF06ECC
sbl3:0x3A410C2C
tz: 0xC73B0D94
radio:0xE9CC6D25
hboot: 0x0
boot: 0x0
recovery: 0x0
system 0x0
This is the latest GETVAR information - I notice that now the baseband version says N/A...I don't know what this means - maybe it is a result of the cache wipe? Maybe i have messed something up? But, the FASTBOOT command would not read the IMG file before this change.
version: 0.5
version-bootloader: 1.57.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main: 5.12.707.104
version-misc: PVT SHIP S-ON
serialno: xxxxxxxxxxxxxxxxx
imei: xxxxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__044
battery-status: good
battery-voltage: 4313mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Again - thank you for any help you may be able to give...
Click to expand...
Click to collapse
nkk71 said:
@clsA @SaHiLzZ @alray all in one thread... looks like trouble... i'm better go watch a movie/series (a few come to mind )
but for the OP, don't know if you have a locked (remote failed) or unlocked bootloader, but "cannot load" = MyFileNameIsWrong (or isn't even in the correct folder)
try that DIR command in command prompt to see what the filenames are
Click to expand...
Click to collapse
Thanks for your help - here is the details of the DIR command - ( it seems the the file has an img.img identity - this doesn't show up on the folder - how do I change it? - Do I need to download again and save it to the folder some other way? It gets saved straight to the downloads folder - then I rename it and cut and paste it to the same folder as fastboot - which is also still in the downloads folder...) - I don't know what to do next - and is it true that I cannot relock the bootloader if I get phone up and working? It does say UNLOCKED on the phone....
<DIR> .
<DIR> ..
819,200 adb.exe
96,256 AdbWinApi.dll
60,928 AdbWinUsbApi.dll
<DIR> api
8,968,192 CWM.img.img
0 fastboot
160,256 fastboot.exe
727,881 NOTICE.txt
9,404,416 openrecovery-twrp-2.6.3.3-m7.img
9,660,416 openrecovery-twrp-2.7.1.1-m7.img
1,054,703,616 ruu.zip.zip
39 source.properties
<DIR> systrace
9,660,416 TWRP.img.img
256 Unlock_code.bin
File(s) 1,094,261,872 bytes
Dir(s) 452,554,018,816 bytes free
ONE other thing - 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
9,660,416 openrecovery-twrp-2.7.1.1-m7.img
These files are not img.img - and they didn't seem to work either - and I also notice one of the RUU zip files I had downloaded to try to help with all this is also a zip.zip = why does this happen and how do I prevent it?
Thanks again for any help....

gawoz said:
Thanks for your help - here is the details of the DIR command - ( it seems the the file has an img.img identity - this doesn't show up on the folder - how do I change it? - Do I need to download again and save it to the folder some other way? It gets saved straight to the downloads folder - then I rename it and cut and paste it to the same folder as fastboot - which is also still in the downloads folder...) - I don't know what to do next - and is it true that I cannot relock the bootloader if I get phone up and working? It does say UNLOCKED on the phone....
<DIR> .
<DIR> ..
819,200 adb.exe
96,256 AdbWinApi.dll
60,928 AdbWinUsbApi.dll
<DIR> api
8,968,192 CWM.img.img
0 fastboot
160,256 fastboot.exe
727,881 NOTICE.txt
9,404,416 openrecovery-twrp-2.6.3.3-m7.img
9,660,416 openrecovery-twrp-2.7.1.1-m7.img
1,054,703,616 ruu.zip.zip
39 source.properties
<DIR> systrace
9,660,416 TWRP.img.img
256 Unlock_code.bin
File(s) 1,094,261,872 bytes
Dir(s) 452,554,018,816 bytes free
ONE other thing - 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
9,660,416 openrecovery-twrp-2.7.1.1-m7.img
These files are not img.img - and they didn't seem to work either - and I also notice one of the RUU zip files I had downloaded to try to help with all this is also a zip.zip = why does this happen and how do I prevent it?
Thanks again for any help....
Click to expand...
Click to collapse
You have double file extension (.zip.zip or .img.img) because by default, windows hide known file type extensions and you manually renamed your file adding a .zip or a .img. To prevent that kind of error and always display file extensions, open any folder,then click in that folder and hit left ALT then click on Tools ---> Folders options ---> View tab ---> make sure ''Hide extensions of known files type'' is not selected. Then click ''apply''.
Now in your folder, delete double extensions, rename all your file so they have only have one file extension.
edit: here is a nice tutorial with pictures: http://askabouttech.com/how-to-show-file-extension-in-windows-7/

nkk71 said:
indeed, "a powerful ally that dir command can be"
if I had to take a wild guess, it's probably in the same folder but with a .img.img extension, courtesy of Windows Explorer
Click to expand...
Click to collapse
You were right! Thank you - I am having progress - I have successfully put TWRP onto the phone now - but it is not letting me sideload now!
Please see errors in next post...

284
clsA said:
LOL this guy sent me a PM and I get to the thread and see the entire team is here to help where's @alray.
thanks guys .... I'm not positive the bootloader is still unlocked .. he relocked it to run a RUU.
Click to expand...
Click to collapse
Hi - i got TWRP into the phone - the guys were correct - there were double .img descriptions in the saved file names - so once that was cleared up - it loaded onto the phone straight away.
I did download that ROM file - and followed the instructions - however here are the details of what came up on the computer screen next - (FYI, the TWRP screen on phone continued to say: updating partitiion details, Full SELinux support is present, Starting ADB sideload feature.
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.562s]
finished. total time: 0.563s
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.034s
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>adb sideload One_5.11.401.10_odexed.zip
error: device not found
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>adb sideload One_5.11.401.10_odexed.zip
error: device not found
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>
(is this ROM file the stock ROM - is there anyway to get that? or is this the first step in the process to that? I think my stock ROM is this one - but again - I guess I am taking baby steps - and it's good to have some progress...)
http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
(NB - I have not downloaded or tried to sideload the above ZIP - only the one provided by clsA)
In the Bootloader mode - my phone now says UNLOCKED TAMPERED.
Feeling violated, hahaha. Anyway - thanks for the continued help so far....

gawoz said:
Hi - i got TWRP into the phone - the guys were correct - there were double .img descriptions in the saved file names - so once that was cleared up - it loaded onto the phone straight away.
I did download that ROM file - and followed the instructions - however here are the details of what came up on the computer screen next - (FYI, the TWRP screen on phone continued to say: updating partitiion details, Full SELinux support is present, Starting ADB sideload feature.
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>adb sideload One_5.11.401.10_odexed.zip
error: device not found
Click to expand...
Click to collapse
while in custom recovery, what does "adb devices" report?
it should report, List of attached devices
<serial number> recovery
or
<serial number> sideload
if it doesn't, open Windows Device Manager and check the FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
PS: Alternatively, in an effort to avoid reposting the same thing several times, I've also added this information, in the FAQ sticky thread. (I believe it's still in the last post)... you may want to check it.

nkk71 said:
while in custom recovery, what does "adb devices" report?
it should report, List of attached devices
<serial number> recovery
or
<serial number> sideload
if it doesn't, open Windows Device Manager and check the FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
PS: Alternatively, in an effort to avoid reposting the same thing several times, I've also added this information, in the FAQ sticky thread. (I believe it's still in the last post)... you may want to check it.
Click to expand...
Click to collapse
THANK YOU! It is working - I did what you suggested and yes - the driver was not there - now the zip file has sideloaded!
Is the next thing to do to go to recovery and install the sideloaded zip file? NOTE that my phone is not rooted - the TWRP is asking me if I want to root the phone - using the SU thing - do I need to do anything like that first - or just go ahead and confirm to flash the file - TWRP is saying "this operation may install incompatible software which may render your device unusable..."
**My phone is an ASIAN one - from Thailand actually - so does this matter at all at this point?**
If you could just let me know....thanks so much!

[Q] M7 full wipe no system 6.12.161.8 M7_UL Vodafone

hi my problem is with my htc I wipe it full and I have no software on it , it is vodafone has HBOOT 1.57.0000 and firmware 6.12.161.8 they can help me back up to play a firmware ?:crying:
C:\Users\-\Desktop\ADB>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) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4280mV
(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!

XFX-Gaming said:
hi my problem is with my htc I wipe it full and I have no software on it , it is vodafone has HBOOT 1.57.0000 and firmware 6.12.161.8 they can help me back up to play a firmware ?:crying:
C:\Users\-\Desktop\ADB>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) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4280mV
(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!
Click to expand...
Click to collapse
Remove your IMEI and SERIALNO from your getvar all.
I can't find any files useful to reset your phone back to stock 6.12.161.8 version. You should flash a custom recovery + a custom rom.

alray said:
Remove your IMEI and SERIALNO from your getvar all.
I can't find any files useful to reset your phone back to stock 6.12.161.8 version. You should flash a custom recovery + a custom rom.
Click to expand...
Click to collapse
how can I do that they can give me a manual or via teamviewer help me would be very grateful

XFX-Gaming said:
how can I do that they can give me a manual or via teamviewer help me would be very grateful
Click to expand...
Click to collapse
Follow this guide
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"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"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
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
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
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
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse

alray said:
Follow this guide
​
Click to expand...
Click to collapse
my htc is relocked

XFX-Gaming said:
my htc is relocked
Click to expand...
Click to collapse
same thing apply, follow the guide. (see 3rd prerequisite)

alray said:
same thing apply, follow the guide. (see 3rd prerequisite)
Click to expand...
Click to collapse
i have an error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
error: device not found

XFX-Gaming said:
i have an error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Might be because your driver isn't installed (should not be the case if you have followed the guide)
or maybe because you haven't enabled USB debugging
Hoewever, just do it manually by holding power and volume down until your phone reboot in bootloader then select "recovery"

alray said:
Might be because your driver isn't installed (should not be the case if you have followed the guide)
or maybe because you haven't enable USB debugging
Hoewever, just do it manually by holding power and volume down until your phone reboot in bootloader then select "recovery"
Click to expand...
Click to collapse
and i have this problem
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery openrec
very-twrp-2.6.3.3-m7.img
target reported max download size of 1509875712 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.152s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.056s

XFX-Gaming said:
and i have this problem
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery openrec
very-twrp-2.6.3.3-m7.img
target reported max download size of 1509875712 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.152s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.056s
Click to expand...
Click to collapse
You are not following the guide! Make sure you have all prerequisites before starting and then proceed step by step.
You are having this error because your bootloader is locked/relocked (see 3rd prerequisite, click "show content" and see step 1)

alray said:
You are not following the guide! Make sure you have all prerequisites before starting and then proceed step by step.
You are having this error because your bootloader is locked/relocked (see 3rd prerequisite, click "show content" and see step 1)
Click to expand...
Click to collapse
yes my bootloader is relocked

So I helped him ( @XFX-Gaming ) via team viewer. Bootloader is S-ON and Re-Locked. We got a fresh Unlock_code.bin from HTCDev.com. The unlock code flash fine and the bootloader unlock screen shows up. When selecting "yes" to unlock, phone attemps to boot in recovery and hangs at the "entering recovery" white screen. When force reboot to the bootloader, still re-locked.
Any idea @nkk71 @clsA @Danny201281 ?
I think we should reflash the firmware in RUU mode but can't find any useful files for his version (6.12.161.8)
So we need the 6.12.161.8 firmware or the 6.12.161.8 ota zip file

alray said:
So I helped him ( @XFX-Gaming ) via team viewer. Bootloader is S-ON and Re-Locked. We got a fresh Unlock_code.bin from HTCDev.com. The unlock code flash fine and the bootloader unlock screen shows up. When selecting "yes" to unlock, phone attemps to boot in recovery and hangs at the "entering recovery" white screen. When force reboot to the bootloader, still re-locked.
Any idea @nkk71 @clsA @Danny201281 ?
I think we should reflash the firmware in RUU mode but can't find any useful files for his version (6.12.161.8)
So we need the 6.12.161.8 firmware or the 6.12.161.8 ota zip file
Click to expand...
Click to collapse
Yeah your dead right. Fixed this same issue in the Unbrick Thread just the other day.
Flashing the firmware and getting a new Unlock_code.bin fixed it.

alray said:
So I helped him ( @XFX-Gaming ) via team viewer. Bootloader is S-ON and Re-Locked. We got a fresh Unlock_code.bin from HTCDev.com. The unlock code flash fine and the bootloader unlock screen shows up. When selecting "yes" to unlock, phone attemps to boot in recovery and hangs at the "entering recovery" white screen. When force reboot to the bootloader, still re-locked.
Any idea @nkk71 @clsA @Danny201281 ?
I think we should reflash the firmware in RUU mode but can't find any useful files for his version (6.12.161.8)
So we need the 6.12.161.8 firmware or the 6.12.161.8 ota zip file
Click to expand...
Click to collapse
My German is not so great but look here >> http://www.handy-faq.de/forum/htc_o...c_one_firmwaresammlung_ruus_otas_backups.html

Here you go
zHi5k0 said:
My stautus is relocked. This is the problem. When I'm trying to unlock it with HTCDev method it 's trying to get to recovery but there's no recovery.
Click to expand...
Click to collapse
Danny201281 said:
Ok that makes some sense, you probably have a minor firmware incompatiblity that's causing this problem.
Download this firmware zip and put it in your fastboot folder. Rename it "firmware.zip"
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.11.zip
Reboot the phone into the bootloader and connect fastbootusb.
In the fastboot command line type.
Code:
fastboot erase cache
fastboot oem rebootRUU
**---case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
When that's done go to htcdev.com and go through the entire unlock my bootloader to get a new Unlock_code.bin then use it to Unlock your bootloader. :good:
The firmware will also restore your Stock Recovery, so after the unlock you will need to flash a new custom recovery.
Click to expand...
Click to collapse
zHi5k0 said:
I have an unlocked phone now. Thank you very much. I have no words about the help you did to me. Please tell me what should I do for getting the phone back to stock without bricking it again.
Click to expand...
Click to collapse

Danny201281 said:
Yeah your dead right. Fixed this same issue in the Unbrick Thread just the other day.
Flashing the firmware and getting a new Unlock_code.bin fixed it.
Click to expand...
Click to collapse
Thanks for the info
clsA said:
My German is not so great but look here >> http://www.handy-faq.de/forum/htc_o...c_one_firmwaresammlung_ruus_otas_backups.html
Click to expand...
Click to collapse
Nice collection, everything about x.xx.161.x can be found there... except the 6.12.161.8 firmware or ota we need
Btw the OP also have a thread about his issue on that forum here
and it looks like even them don't have the 6.12.161.8 firmware
will ask in the update thread just in case someone have it.

Mike1986 has 6.12.161.5 in his repository but thats the closest i can find

@alray, i'm capturing 6.12.161.9 OTA (didnt get the .8 one, got straight to .9).... i'll post firmware once i have it

@alray here is the signed firmware from 6.12.161.9
https://www.dropbox.com/s/ov1x96x8c5qhyb6/signed_ota_firmware_6.12.161.9.zip?dl=0
Code:
modelid: PN0710000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAPE17
cidnum: VODAP405
cidnum: VODAP304
cidnum: VODAPD18
cidnum: VODAP120
cidnum: VODAP110
mainver: 6.12.161.9
btype:1
aareport:1
hbootpreupdate:3
as this is only an OTA update it only contains:
Code:
android-info.txt
boot.img
hboot_signedbyaa.img
rcdata.img
recovery.img
splash1.nb0
I was able to capture (even while on SuperCID )
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.5-5.16.161.2_release_387413_VodaIT.zip (608 MB)
then
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.9-6.12.161.5_release_401650aawyk6dy4kqo5flm.zip (250 MB)
don't know why no 6.12.161.8.... i'll try again in a bit (using different CID), so if you wanna wait to see if i can get the .8 version i'll let you know shortly....
@alray EDIT: just changed cid to VODAP102 and got the 6.12.161.8 update info..... downloading... (i've removed the other one from my dropbox)

nkk71 said:
@alray here is the signed firmware from 6.12.161.9
https://www.dropbox.com/s/ov1x96x8c5qhyb6/signed_ota_firmware_6.12.161.9.zip?dl=0
Code:
modelid: PN0710000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAPE17
cidnum: VODAP405
cidnum: VODAP304
cidnum: VODAPD18
cidnum: VODAP120
cidnum: VODAP110
mainver: 6.12.161.9
btype:1
aareport:1
hbootpreupdate:3
as this is only an OTA update it only contains:
Code:
android-info.txt
boot.img
hboot_signedbyaa.img
rcdata.img
recovery.img
splash1.nb0
I was able to capture (even while on SuperCID )
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.5-5.16.161.2_release_387413_VodaIT.zip (608 MB)
then
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.9-6.12.161.5_release_401650aawyk6dy4kqo5flm.zip (250 MB)
don't know why no 6.12.161.8.... i'll try again in a bit (using different CID), so if you wanna wait to see if i can get the .8 version i'll let you know shortly....
@alray EDIT: just changed cid to VODAP102 and got the 6.12.161.8 update info..... downloading... (i've removed the other one from my dropbox)
Click to expand...
Click to collapse
Thanks so much!
 @XFX-Gaming New hope :good:

restore O2 UK HTC One M7 to stock Android required

I have an HTC One M7 running CyanogenMod and need to restore it so that I can change operators.
It will not let me unlatch it using the O2 unlatch code.
Any help welcome
Thanks
Jim

dennyjim said:
I have an HTC One M7 running CyanogenMod and need to restore it so that I can change operators.
It will not let me unlatch it using the O2 unlatch code.
Any help welcome
Thanks
Jim
Click to expand...
Click to collapse
I assume you mean to SIM unlock the device. For the code to work you need to flash an O2 stock Rom.
Please post the output of
Code:
fastboot getvar all
Remember to remove your IMEI and Serial number before posting. I'll see what can be found
Sent from my HTC One using Tapatalk

I've installed ADB and fastboot, but when I run "fastboot getvar all" it says "waiting for device" ??

dennyjim said:
I've installed ADB and fastboot, but when I run "fastboot getvar all" it says "waiting for device" ??
Click to expand...
Click to collapse
And your device is in fastboot usb mode? Check your drivers in Windows device manager. What is your HTC listed as. Anything other than "My HTC" indicates a driver issue.
Sent from my HTC One using Tapatalk

I'm using windows 10 and its listed only as "One" ?

dennyjim said:
I'm using windows 10 and its listed only as "One" ?
Click to expand...
Click to collapse
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 the latest driver in the list :good:
Sent from my HTC One using Tapatalk

Once I get to "let me pick"
Only shows "MTP Device" no sign of "Android USB Device"
Thanks for trying Danny but got to go to work!
Saturday nightshift Taxi driver :crying:

dennyjim said:
Once I get to "let me pick"
Only shows "MTP Device" no sign of "Android USB Device"
Thanks for trying Danny but got to go to work!
Saturday nightshift Taxi driver :crying:
Click to expand...
Click to collapse
Ok when you get a chance Dow load this. http://www.mediafire.com/download_repair.php?dkey=qzmgethe1nt&qkey=2lyl151pt5pah2v
Extract the zip on your pc and install the driver .exe. If that doesn't help try the above procedure again.
If you still don't get any joy just post the info from your bootloader screen. :good:
Sent from my HTC One using Tapatalk

Tampered
Unlocked
M7_UL PUT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS/7.18.206.30
eMMC-boot 2048MB
Aug 5 , 17:22:13.0
HBOOT
FASTBOOT
RECOVERY
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE

dennyjim said:
Tampered
Unlocked
M7_UL PUT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS/7.18.206.30
eMMC-boot 2048MB
Aug 5 , 17:22:13.0
HBOOT
FASTBOOT
RECOVERY
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Click to expand...
Click to collapse
So I guess your still having driver problems?
There is and ruu you can flash https://www.androidfilehost.com/?fid=24052804347813898 but you will need to get those drivers working to do so. As it requires fastboot.
I did find a nandroid backup https://www.androidfilehost.com/?fid=95916177934549269 you could download this direct to the phone and restore it with twrp. But the RUU is a better option if you can get the drivers to work :good:
Sent from my HTC One using Tapatalk

Danny201281 said:
So I guess your still having driver problems?
There is and ruu you can flash https://www.androidfilehost.com/?fid=24052804347813898 but you will need to get those drivers working to do so. As it requires fastboot.
I did find a nandroid backup https://www.androidfilehost.com/?fid=95916177934549269 you could download this direct to the phone and restore it with twrp. But the RUU is a better option if you can get the drivers to work :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Got fastboot going Danny. Here are the results
C:\Users\Jim>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.206.30
(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: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c50a98a5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 93(ms

dennyjim said:
Got fastboot going Danny. Here are the results
C:\Users\Jim>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.206.30
(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: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c50a98a5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 93(ms
Click to expand...
Click to collapse
Ok cool, download the ruu from the first link in my previous post.
Download htc_fastboot https://www.androidfilehost.com/?fid=95916177934550031 Copy both files to your existing fastboot folder and rename the RUU zip file to something simple. e.g "ruu"
Boot your device to the bootloader and connect fastboot usb. Then relock your bootloader and flash the RUU with the following commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Wait for reboot
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
The device will reboot during the flash, and the progress bar on the phone won't quite reach 100% that's normal. Wait till the command windows competes it's output with a successful message then
Code:
fastboot reboot
Note first boot will take longer than usual. It may seem to be stuck on the HTC boot screen for 15 to 20 minutes.
Sent from my HTC One using Tapatalk

Danny201281 said:
Ok cool, download the ruu from the first link in my previous post.
Download htc_fastboot https://www.androidfilehost.com/?fid=95916177934550031 Copy both files to your existing fastboot folder and rename the RUU zip file to something simple. e.g "ruu"
Boot your device to the bootloader and connect fastboot usb. Then relock your bootloader and flash the RUU with the following commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Wait for reboot
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
The device will reboot during the flash, and the progress bar on the phone won't quite reach 100% that's normal. Wait till the command windows competes it's output with a successful message then
Code:
fastboot reboot
Note first boot will take longer than usual. It may seem to be stuck on the HTC boot screen for 15 to 20 minutes.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'm getting this error message when i execute "htc_fastboot flash zip ruu.zip"
C:\Users\Jim>htc_fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
C:\Users\Jim>htc_fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip

dennyjim said:
I'm getting this error message when i execute "htc_fastboot flash zip ruu.zip"
C:\Users\Jim>htc_fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
C:\Users\Jim>htc_fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
Click to expand...
Click to collapse
fastboot cannot see the ruu file. Possible reasons for this.
Is the ruu file in the fastboot folder? The ruu needs to be in your fastboot folder in order for the flash command to work. Otherwise you need to specify the full path to the files location.
Is the command window working from your fastboot folder? To make sure of this Open your fastboot folder on your pc. Hold shift and right click on an empty space inside the folder window. Select option - "Open Command Window Here"
File name can also cause a problem. The fastboot flash zip command must specify the correct file name.
Also Windows appends file extensions so they should not be included in the file name. i.e
If you name a file ruu.zip Windows will see it as ruu.zip.zip. so make sure to rename the file simply as "ruu" Windows will automatically append the .zip :good:
Failing all that there is the full proof drag and drop method. Enter the first part of the command "htc_fastboot flash zip " leaving a space on the end.
Then simply drag the ruu file with your mouse into the command window. It will automatically add the full file path to the ruu. Hit enter :good:
Sent from my HTC One using Tapatalk

Danny201281 said:
fastboot cannot see the ruu file. Possible reasons for this.
Is the ruu file in the fastboot folder? The ruu needs to be in your fastboot folder in order for the flash command to work. Otherwise you need to specify the full path to the files location.
Is the command window working from your fastboot folder? To make sure of this Open your fastboot folder on your pc. Hold shift and right click on an empty space inside the folder window. Select option - "Open Command Window Here"
File name can also cause a problem. The fastboot flash zip command must specify the correct file name.
Also Windows appends file extensions so they should not be included in the file name. i.e
If you name a file ruu.zip Windows will see it as ruu.zip.zip. so make sure to rename the file simply as "ruu" Windows will automatically append the .zip :good:
Failing all that there is the full proof drag and drop method. Enter the first part of the command "htc_fastboot flash zip " leaving a space on the end.
Then simply drag the ruu file with your mouse into the command window. It will automatically add the full file path to the ruu. Hit enter :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
This worked great Danny
Open your fastboot folder on your pc. Hold shift and right click on an empty space inside the folder window. Select option - "Open Command Window Here"
All up and running Using BT sim and all Apps restored :victory:
You are a star Bud :good::good::good:
If I can cancel the unlocked HTC I ordered on EBAY I'll donate to you via your home page on here.
I'm one happy bunny
Many many thanks
Jim

dennyjim said:
This worked great Danny
Open your fastboot folder on your pc. Hold shift and right click on an empty space inside the folder window. Select option - "Open Command Window Here"
All up and running Using BT sim and all Apps restored :victory:
You are a star Bud :good::good::good:
If I can cancel the unlocked HTC I ordered on EBAY I'll donate to you via your home page on here.
I'm one happy bunny
Many many thanks
Jim
Click to expand...
Click to collapse
Excellent, Happy to help Glad you got the result you were looking for :good:
Sent from my HTC One using Tapatalk

Soft bricked my HTC ONE M7_UL (S-ON,HBOOT 1.57) Have access to TWRP

Evening,
I've been desperately trying to figure this out myself but I've concluded that it's too complex for me to go it alone, as it stands my HTC one M7_UL is I believe soft bricked, I can get to the bootloader and into TWRP recovery but I've had no luck with FASTBOOT/ADB, I can sideload a rom.zip but it just fails to do anything after 100%, I reboot it and it just gets stuck on the previous bootloop. Currently have no OS installed and honestly I don't have a clue what I'm doing, exactly why I'm in this mess in the first place, I bricked it a while ago but I figure I wiped system partitions and as a result am in a bad place any advice you could offer would be brilliant.
Thank you in advance, I've included some additional details below but let me know if I've missed anything.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.206.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA39PWxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4320mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-44d68d6b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
Also I get this as well not sure if it's a problem but I haven't seen it anywhere else -
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA39PWxxxxxx offline
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA39PWxxxxxx sideload

mattage101 said:
Evening,
I've been desperately trying to figure this out myself but I've concluded that it's too complex for me to go it alone, as it stands my HTC one M7_UL is I believe soft bricked, I can get to the bootloader and into TWRP recovery but I've had no luck with FASTBOOT/ADB, I can sideload a rom.zip but it just fails to do anything after 100%, I reboot it and it just gets stuck on the previous bootloop. Currently have no OS installed and honestly I don't have a clue what I'm doing, exactly why I'm in this mess in the first place, I bricked it a while ago but I figure I wiped system partitions and as a result am in a bad place any advice you could offer would be brilliant.
Thank you in advance, I've included some additional details below but let me know if I've missed anything.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.206.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA39PWxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4320mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-44d68d6b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
Also I get this as well not sure if it's a problem but I haven't seen it anywhere else -
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA39PWxxxxxx offline
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA39PWxxxxxx sideload
Click to expand...
Click to collapse
What is your twrp version?

alray said:
What is your twrp version?
Click to expand...
Click to collapse
TWRP v2.6.3.0
Thanks for the interest!

mattage101 said:
TWRP v2.6.3.0
Thanks for the interest!
Click to expand...
Click to collapse
You should take a few minutes and update your twrp first because there's not much you'll be able to flash with this version and also because newer version will allow you to use mtp instead of sideload (you'll be able to see your phone storage from your computer when booted in TWRP like if it was a thumb drive)
Here is the link to download the latest version (3.0.M5.0) http://android.cmphys.com/twrp-m7/
Save the file in your fastboot/adb folder. With the phone booted in bootloader mode showing "fastboot usb" in red, start a command window and type:
Code:
fastboot flash recovery twrp-3.0.M5-0-m7univ.img
fastboot erase cache
fastboot reboot-bootloader
then you can restore this twrp backup: https://www.androidfilehost.com/?fid=95897840722646675
To restore a backup,boot in twrp and make a backup of boot.img only (this is only to generate a backup path). Then using twrp's files manager navigate to /sdcard/TWRP/BACKUPS/your_serial_number/date_of_backup and delete backup files in this folder and replace them by the files contained in the nandroid backup you want to use. Then select "restore" and restore all available partitions.

alray said:
You should take a few minutes and update your twrp first because there's not much you'll be able to flash with this version and also because newer version will allow you to use mtp instead of sideload (you'll be able to see your phone storage from your computer when booted in TWRP like if it was a thumb drive)
Here is the link to download the latest version (3.0.M5.0)
Save the file in your fastboot/adb folder. With the phone booted in bootloader mode showing "fastboot usb" in red, start a command window and type:
Code:
fastboot flash recovery twrp-3.0.M5-0-m7univ.img
fastboot erase cache
fastboot reboot-bootloader
then you can restore this twrp backup:
To restore a backup,boot in twrp and make a backup of boot.img only (this is only to generate a backup path). Then using twrp's files manager navigate to /sdcard/TWRP/BACKUPS/your_serial_number/date_of_backup and delete backup files in this folder and replace them by the files contained in the nandroid backup you want to use. Then select "restore" and restore all available partitions.
Click to expand...
Click to collapse
Mate. MATE! I can't thank you enough, got it to work, cheers buddy - for what it's worth you're awesome!

mattage101 said:
Mate. MATE! I can't thank you enough, got it to work, cheers buddy - for what it's worth you're awesome!
Click to expand...
Click to collapse
I do have one question though, why when I try to update the OS does it reboot into TWRP, am I suppose to update it from in there?

mattage101 said:
I do have one question though, why when I try to update the OS does it reboot into TWRP, am I suppose to update it from in there?
Click to expand...
Click to collapse
In order to flash the official OTA you need stock recovery. You can't update your phone the official way with custom recovery

HTC One
I followed your instructions, copied all the downloaded files to the Date folder, except the file "system.ext4.win000" 1.5GB. It hangs, won't go past approx. 15-20%. I tried a very similar method yesterday, and the same happened.

vik919 said:
I followed your instructions, copied all the downloaded files to the Date folder, except the file "system.ext4.win000" 1.5GB. It hangs, won't go past approx. 15-20%. I tried a very similar method yesterday, and the same happened.
Click to expand...
Click to collapse
Try another usb cable and another usb port. I would also format data.
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
mattage101 said:
I do have one question though, why when I try to update the OS does it reboot into TWRP, am I suppose to update it from in there?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95897840722646669

alray said:
Try another usb cable and another usb port. I would also format data.
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
https://www.androidfilehost.com/?fid=95897840722646669
Click to expand...
Click to collapse
So I flashed the stock recovery .img you linked and I searched for software updates, clicked ok and it reboots and comes up with a screen with a phone displaying a green triangle, after a couple of minutes the triangle turns red, I pressed the power button and the volume up button so I could see the error report and I got this:
Finding update package...
opening update package...
Verifying update package...
Installing update...
Verifying current system...
Check /data/preload/SoundHound_Freemium.apk failed, error No such file or directory()
Installation aborted.
Write host_mode:0 done
What do you make of it?
Thanks again for all your responses, genuinely appreciate it!

mattage101 said:
Verifying current system...
Check /data/preload/SoundHound_Freemium.apk failed, error No such file or directory()
Click to expand...
Click to collapse
Looks like the nandrdoid backup was missing the files in /data/preload. When unlocking the bootloader, /data is wiped to prevent unauthorized access to your files. Unfortunately HTC packed a few stock apps in /data/preload so these apps are lost when unlocking. So the person who made that nandroid backup did it after unlocking the bootloader hence why the missing files. Sorry
When installing an OTA update, the updater-script check for all the files to be updated (thousand of files). They must all be there and as expected (not modded or corrupt). If only one of these files is missing/corrupt, the ota installation will abort, this is to prevent patching wrong files and making your system unusable.
This can usually be corrected by restoring the missing files. Unfortunately I can't find the /data/preload files for your version...
Another option would be to update your firmware so you can flash the latest version using a RUU
Download these 3 files and save them in your adb/fastboot folder on your computer:
https://www.androidfilehost.com/?fid=95916177934535002
https://www.androidfilehost.com/?fid=24385226645962836
https://www.androidfilehost.com/?fid=24341993505161791
re-lock your bootloader (needed since your phone is S-ON):
Code:
fastboot oem lock
Update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.18.206.2.zip
fastboot flash zip M7_UL_Firmware_7.18.206.2.zip
fastboot reboot-bootloader
Flash the RUU:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459056_signed.zip
fastboot reboot

alray said:
Looks like the nandrdoid backup was missing the files in /data/preload. When unlocking the bootloader, /data is wiped to prevent unauthorized access to your files. Unfortunately HTC packed a few stock apps in /data/preload so these apps are lost when unlocking. So the person who made that nandroid backup did it after unlocking the bootloader hence why the missing files. Sorry
When installing an OTA update, the updater-script check for all the files to be updated (thousand of files). They must all be there and as expected (not modded or corrupt). If only one of these files is missing/corrupt, the ota installation will abort, this is to prevent patching wrong files and making your system unusable.
This can usually be corrected by restoring the missing files. Unfortunately I can't find the /data/preload files for your version...
Another option would be to update your firmware so you can flash the latest version using a RUU
Download these 3 files and save them in your adb/fastboot folder on your computer:
https://www.androidfilehost.com/?fid=95916177934535002
https://www.androidfilehost.com/?fid=24385226645962836
https://www.androidfilehost.com/?fid=24341993505161791
re-lock your bootloader (needed since your phone is S-ON):
Code:
fastboot oem lock
Update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.18.206.2.zip
fastboot flash zip M7_UL_Firmware_7.18.206.2.zip
fastboot reboot-bootloader
Flash the RUU:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459056_signed.zip
fastboot reboot
Click to expand...
Click to collapse
Ok I'm all sorted that worked, thanks for your time!