Database Develop

Please help!!!!

Hi
Please help me or I will possibly be killed by my wife!
She has a HTC One which was bought 2nd hand months ago. This morning there was a alert popped up on screen saying there was a OTA update. I pressed it and it took me into a recovery system called "Team Win Recovery Project V2.6.3.0".
Ive gone into this and pressed the "wipe" button and "format data" thinking this would do a full factory reset for this update.....I was wrong!
I now have no OS on the phone and she is seriously P!ssed at me!
I have been on with this for the past 4 hours and still no further forward.
I have managed to download a RUU and side load it onto the phone but when it updates I get the following error
"set_metadata_recursive: some changes failed
E : Error executing updater binary in zip '/sdcar
Error flashing zip '/sdcard/sideload.zip'
Updateing partition details..."
Can any1 help? could it be the RRU I have downloaded is corrupt? or the wrong one?
When I go into the bootload the following info is there......
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.61.1
eMMC-boot 2048MB
Jun 21 2013, 23:33:16.0
I don't know if the phones jailbroke/rooted etc. She isn't wanting any of that, just to be able to get the updates and that's it.....once again,
PLEASE HELP! lol
Thankyou in advance!
Dave

Are you familiar with fastboot commands? While booted to the white Bootloader screen connect phone to pc, then open a command prompt in whichever folder you have fastboot.exe in by holding the shift key down and right click the mouse anywhere in the folder fastboot is in. Then choose "open command prompt here"
In the black command prompt window please type
fastboot getvar all
Then hit enter. Copy and paste the info it spits out here please. This will give us more info about your devices firmware. If you had s-off you could flash any ruu, but since you are s-on we can only flash an ruu that is the same as current firmware or upgrade to a higher version (then you have to hope there is an ruu available)
This will help put you back to complete stock. The issue before was that you had twrp recovery installed when you tried to ota update. You can only update via OTA if you have stock recovery. Then the real issue is when you formatted data and wiped your firmware off phone.
Since your bootloader is unlocked it is possible to just push a stock rom through sideboard and then flash in recovery but you still couldn't accept updates since you have twrp installed. This would be the quicker fix but if the wife wants complete stock we need to look for the correct RUU.
Hope this helps!
Sent from my SGH-I337 using xda app-developers app

ive done as you asked and it just says < waiting for device >
Ive read somewhere that fastboot doesn't work correct with windows 8.1

dave mckenzie said:
Hi
Please help me or I will possibly be killed by my wife!
She has a HTC One which was bought 2nd hand months ago. This morning there was a alert popped up on screen saying there was a OTA update. I pressed it and it took me into a recovery system called "Team Win Recovery Project V2.6.3.0".
Ive gone into this and pressed the "wipe" button and "format data" thinking this would do a full factory reset for this update.....I was wrong!
I now have no OS on the phone and she is seriously P!ssed at me!
I have been on with this for the past 4 hours and still no further forward.
I have managed to download a RUU and side load it onto the phone but when it updates I get the following error
"set_metadata_recursive: some changes failed
E : Error executing updater binary in zip '/sdcar
Error flashing zip '/sdcard/sideload.zip'
Updateing partition details..."
Can any1 help? could it be the RRU I have downloaded is corrupt? or the wrong one?
When I go into the bootload the following info is there......
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.61.1
eMMC-boot 2048MB
Jun 21 2013, 23:33:16.0
I don't know if the phones jailbroke/rooted etc. She isn't wanting any of that, just to be able to get the updates and that's it.....once again,
PLEASE HELP! lol
Thankyou in advance!
Dave
Click to expand...
Click to collapse
the RUU is run from the PC not the phone
here are some directions to flash "rom.zip":
Quote:
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.
Click to expand...
Click to collapse

I am running windows 8.1 and it wont pick up the phone at all in fastboot mode.....

dave mckenzie said:
I am running windows 8.1 and it wont pick up the phone at all in fastboot mode.....
Click to expand...
Click to collapse
well theirs your problem, your going to need a windows 7 pc
try sideloading one of these
http://www.htc1guru.com/downloads/stock-rom-downloads/

dave mckenzie said:
ive done as you asked and it just says < waiting for device >
Ive read somewhere that fastboot doesn't work correct with windows 8.1
Click to expand...
Click to collapse
Yes sometimes fastboot does not play nice with win8.1 you need to get fastboot drivers working before you could fastboot oem rebootRUU anyways, plus you will need to make sure you have the correct RUU.
Do you have access to another pc that doesn't have win8.1? It would make this process much quicker. If not then let me fire up my pc to get you a few proper links to help you get fastboot working on current pc (on my phone right now).
Sent from my SGH-I337 using xda app-developers app

I have a MacBook but all pcs in this house has win8.1, I can only reply once every 5mins due to some restriction on my account on here so sorry for not replying straight away.

Last login: Sat Dec 28 16:00:02 on ttys000
Dave-McKenzies-MacBook-Pro-15:~ davemckenzie$
Dave-McKenzies-MacBook-Pro-15:~ davemckenzie$
Dave-McKenzies-MacBook-Pro-15:~ davemckenzie$
Dave-McKenzies-MacBook-Pro-15:~ davemckenzie$ cd
Dave-McKenzies-MacBook-Pro-15:~ davemckenzie$ cd /Users/davemckenzie/Desktop/andriod
Dave-McKenzies-MacBook-Pro-15:andriod davemckenzie$ ./fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA33VW904059
(bootloader) imei: ************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3958mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Dave-McKenzies-MacBook-Pro-15:andriod davemckenzie$

(bootloader) version-main: 2.24.61.1
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
Click to expand...
Click to collapse
This is all I can find for you phone
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-orang001-2-24-61-1-zip/
Extract this to the folder fastboot/adb is in, in a folder called backup
To use – download the latest version of the needed recovery and install it via fastboot:
fastboot flash recovery TWRP.img - you already have this
Then enter recovery either by holding power and vol down button until bootloader displays and then select recovery
Now perform a test backup and allow it to complete. Then make a note of the folder in which the backup was created. Now copy the downloaded stock Nandroid into that same folder so that recovery will see the backup and allow you to restore it.
Click to expand...
Click to collapse
to accomplish this you going to adb push the file to your phone
this is how it looks on my phone
C:\fastboot>adb devices
List of devices attached
HT********** recovery <-- You need this Number in the command below not the word recovery
C:\fastboot>adb push backup /data/media/0/TWRP/BACKUPS/Your number here HT**********/backup
1 file pushed. 0 files skipped.
3881 KB/s (28795564 bytes in 7.245s)
Click to expand...
Click to collapse
In the above example I named the folder the files are in backup
after it copy's you go back to the phone in recovery and choose restore
the folder backup should be their for you to choose

wil these be the same commands on mac?
thankyou for your help btw, every1 has been brilliant
Once this has got working, will I be able to update over wifi etc?

dave mckenzie said:
wil these be the same commands on mac?
thankyou for your help btw, every1 has been brilliant
Once this has got working, will I be able to update over wifi etc?
Click to expand...
Click to collapse
No most likely this is a Stock rooted backup
You phone will never get OTA updates while your on custom recovery. Until theirs a RUU for your device it will be tough getting full stock for OTA
Sent from my HTC One using Tapatalk

My HTC One is soft-bricked(?) and i have no idea what to do

Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000

George Kayogre said:
Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?

George Kayogre said:
Hello,
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592

clsA said:
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592
Click to expand...
Click to collapse
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".

George Kayogre said:
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".
Click to expand...
Click to collapse
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful

alray said:
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful
Click to expand...
Click to collapse
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something

George Kayogre said:
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something
Click to expand...
Click to collapse
uninstall htc sync and try again

alray said:
uninstall htc sync and try again
Click to expand...
Click to collapse
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.

George Kayogre said:
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.
Click to expand...
Click to collapse
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.

alray said:
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.
Click to expand...
Click to collapse
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
This is what "fastboot getvar all" returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
clsA said:
Unzip this to your desktop and open a command window from it's folder (right click - command prompt here)
plug in your phone to the pc boot to the bootloader with power + volume down
type fastboot devices
your phone serial number should be listed
now type fastboot erase cache
it should say something about formatting cache
now fastboot reboot
hopefully your phone will boot back up
Click to expand...
Click to collapse
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen

George Kayogre said:
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
This is what "fastboot getvar all" returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen
Click to expand...
Click to collapse
have you tried to perform a factory reset from the bootloader?

alray said:
have you tried to perform a factory reset from the bootloader?
Click to expand...
Click to collapse
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.

George Kayogre said:
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.
Click to expand...
Click to collapse
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms

alray said:
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms
Click to expand...
Click to collapse
Here's something new: after unlocking my phone, and having confirmed that i wanted all my "personal data erased", it just booted up normally and it worked, but then, while using it, t=it simply crashed...and got stuck in the bootloop again, which kinda points in the arrow of hardware issue again. I'm gonna try installing a rom (after i figure out how) and see where that leads me.
Update: Flashed CM11, phone still on boot loop, sending to repair soon.
Everyone, thanks for the help anyway, I really appreciate it.

[Q] M7_UL PVT SHIP S-ON RH stuck!

Hi, -- hoping for help...
My M7_UL died/hung up during upgrade yesterday - and is now stuck when rebooting - gets the black screen with a red triangle and the exclamation mark in it.... I have no idea on what went wrong, factory resets etc. does not help -- so I need to bring it back somehow... Any help would be greatly appreciated
Version info:
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.29.3218.08
OpenDSP-v32.120.274.0909
OS-6.09.401.11
eMMC-boot 2048MB
Nov 12 2014,22:08.05.0
Version info from fastboot getvar all:
C:\HTC bootloader>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3785mV
(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
Help
Cheers,
Joern

JornJenz said:
Hi, -- hoping for help...
My M7_UL died/hung up during upgrade yesterday - and is now stuck when rebooting - gets the black screen with a red triangle and the exclamation mark in it.... I have no idea on what went wrong, factory resets etc. does not help -- so I need to bring it back somehow... Any help would be greatly appreciated
Version info:
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.29.3218.08
OpenDSP-v32.120.274.0909
OS-6.09.401.11
eMMC-boot 2048MB
Nov 12 2014,22:08.05.0
Version info from fastboot getvar all:
C:\HTC bootloader>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-main: 6.09.401.11
(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: HTC__001
(bootloader) security: on
Help
Cheers,
Joern
Click to expand...
Click to collapse
First edit your post and remove the Serial no and IMEI
Next hold the power button for about 15 seconds and get the phone to shut down
after it's off you need to get into the bootloader / Fastboot USB - By holding Volume Down + Power
From here you can flash Firmware and a custom recovery
relock bootloader fastboot oem lock
Download this 6.09.401.11 firmware.zip
and flash it
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Next unlock bootloader and flash TWRP 2.8.4.0
fastboot flash recovery openrecovery-twrp-2.8.4.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Next download and extract this stock Nandroid to your TWRP/BACKUP/yourSerialNo/put backup here
https://www.androidfilehost.com/?fid=95832962473396067
your phone should work as normal after this

I am having exactly the same issue with my HTC One with the same version details as the TS:
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.29.3218.08
OpenDSP-v32.120.274.0909
OS-6.09.401.11
eMMC-boot 2048MB
Nov 12 2014,22:08.05.0
My HTC One had original software (never manually put any ROM on it), and it got stuck during the OTA upgrade to Lollipop.
I tried the steps you suggested:
1) fastboot oem rebootRUU
2) fastboot flash zip firmware.zip
3) fastboot flash zip firmware.zip
4) fastboot reboot-bootloader
Next unlock bootloader and flash TWRP 2.8.4.0
5) fastboot flash recovery openrecovery-twrp-2.8.4.0-m7.img
The first 4 steps went well, but I get stuck on step 5. I downloaded the TWRP 2.8.4.0 image from "techerrata . com" and put it in the fastboot folder on the PC. If I use the fastboot command from step 5 I get an error message: "FAILED (remote: signature verify fail).
I tried verious other images, all giving the same error message. Do you have any suggestions what I should try as a next step?

sunshine9 said:
I am having exactly the same issue with my HTC One with the same version details as the TS:
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.29.3218.08
OpenDSP-v32.120.274.0909
OS-6.09.401.11
eMMC-boot 2048MB
Nov 12 2014,22:08.05.0
My HTC One had original software (never manually put any ROM on it), and it got stuck during the OTA upgrade to Lollipop.
I tried the steps you suggested:
1) fastboot oem rebootRUU
2) fastboot flash zip firmware.zip
3) fastboot flash zip firmware.zip
4) fastboot reboot-bootloader
Next unlock bootloader and flash TWRP 2.8.4.0
5) fastboot flash recovery openrecovery-twrp-2.8.4.0-m7.img
The first 4 steps went well, but I get stuck on step 5. I downloaded the TWRP 2.8.4.0 image from "techerrata . com" and put it in the fastboot folder on the PC. If I use the fastboot command from step 5 I get an error message: "FAILED (remote: signature verify fail).
I tried verious other images, all giving the same error message. Do you have any suggestions what I should try as a next step?
Click to expand...
Click to collapse
unlock your bootloader at htcdev.com

clsA said:
unlock your bootloader at htcdev.com
Click to expand...
Click to collapse
Thx a lot for the pointer and the fast response! That indeed did the trick and TWRP is flashed now. I'm starting to feel silly, but I can't get anything on the SD memory from my computer yet. This means I can't finish the final step and install the image using TWRP. Probably a driver issue on my PC, I guess. I have installed several drivers that are recommended through the various fora, but none seem to work to get my phone to show up in windows explorer to make any file transfer. The only thing that works so far is the fastboot command. ADB fails, giving the error message "device not found".
When I plug in my phone, my PC sees the phone. On "Device Manager" it shows Android Device --> my HTC. However, nothing shows in Explorer. I'm using windows 8.1 64 bit. I have used the HTC sync manager drivers as well as several drivers found on the internet, but none seem to do the trick. Have you got any further pointers for the right drivers? Or am I looking in the wrong direction, and isn't this a driver issue?

sunshine9 said:
Thx a lot for the pointer and the fast response! That indeed did the trick and TWRP is flashed now. I'm starting to feel silly, but I can't get anything on the SD memory from my computer yet. This means I can't finish the final step and install the image using TWRP. Probably a driver issue on my PC, I guess. I have installed several drivers that are recommended through the various fora, but none seem to work to get my phone to show up in windows explorer to make any file transfer. The only thing that works so far is the fastboot command. ADB fails, giving the error message "device not found".
When I plug in my phone, my PC sees the phone. On "Device Manager" it shows Android Device --> my HTC. However, nothing shows in Explorer. I'm using windows 8.1 64 bit. I have used the HTC sync manager drivers as well as several drivers found on the internet, but none seem to do the trick. Have you got any further pointers for the right drivers? Or am I looking in the wrong direction, and isn't this a driver issue?
Click to expand...
Click to collapse
I'm stuck at the exact same spot as you, - the phone does not show up in explorer - but I can see it in device manager.... Phone is booted in FASTBOOT USB mode, and accepts fastboot commands - but can't be seen in explorer --- probably something trivial, but I am also stuck...
BWT: I am running Windows 7 Enterprise, 64 bit...
Cheers,
Joern

It wont be visible in explorer when in bootloader mode...if fastboot commands are working, you can go ahead and use the steps given by clsA earlier
Sent from my VZW LG G2

sunshine9 said:
Thx a lot for the pointer and the fast response! That indeed did the trick and TWRP is flashed now. I'm starting to feel silly, but I can't get anything on the SD memory from my computer yet. This means I can't finish the final step and install the image using TWRP. Probably a driver issue on my PC, I guess. I have installed several drivers that are recommended through the various fora, but none seem to work to get my phone to show up in windows explorer to make any file transfer. The only thing that works so far is the fastboot command. ADB fails, giving the error message "device not found".
When I plug in my phone, my PC sees the phone. On "Device Manager" it shows Android Device --> my HTC. However, nothing shows in Explorer. I'm using windows 8.1 64 bit. I have used the HTC sync manager drivers as well as several drivers found on the internet, but none seem to do the trick. Have you got any further pointers for the right drivers? Or am I looking in the wrong direction, and isn't this a driver issue?
Click to expand...
Click to collapse
JornJenz said:
I'm stuck at the exact same spot as you, - the phone does not show up in explorer - but I can see it in device manager.... Phone is booted in FASTBOOT USB mode, and accepts fastboot commands - but can't be seen in explorer --- probably something trivial, but I am also stuck...
BWT: I am running Windows 7 Enterprise, 64 bit...
Cheers,
Joern
Click to expand...
Click to collapse
Enter recovery, the device will now show up in my computer / explorer, then transfer the files, if it doesnt show up, check your drivers in device manager whilst the phone is plugged in and in recovery

Update: after a zillion tries to install the windows drivers it somehow succeeded now. My phone is working again. Thx a lot for the pointers!!!

Ok, I managed to download the M7_UL_TWRP_Nandroid_6.09.401.11_(inkl._preload-Ordner).rar - and extracted the files boot.emmc.win - data.ext4.win - system.ext.4.win000 - system.ext4.win001 (and the md5 files)- and copied them to the phone.... However, TWRP can't find the files - even though I look in the correct directory - do I need to change the extension or something - or does fastboot have a command that will flash my phone with these new files ?
Joern.

JornJenz said:
test
Click to expand...
Click to collapse
Test what ? if you want help describe your problem in detail
did you enter TWRP recovery and copy the files to your phone ?

Ok, I managed to download the M7_UL_TWRP_Nandroid_6.09.401.11_(inkl._preload-Ordner).rar - and extracted the files boot.emmc.win - data.ext4.win - system.ext.4.win000 - system.ext4.win001 (and the md5 files)- and copied them to the phone.... However, TWRP can't find the files - even though I look in the correct directory - do I need to change the extension or something - or does fastboot have a command that will flash my phone with these new files ?
Joern.
(Sorry if this is a "double-entry" - my pc lost power when trying to update my previous post)....

JornJenz said:
Ok, I managed to download the M7_UL_TWRP_Nandroid_6.09.401.11_(inkl._preload-Ordner).rar - and extracted the files boot.emmc.win - data.ext4.win - system.ext.4.win000 - system.ext4.win001 (and the md5 files)- and copied them to the phone.... However, TWRP can't find the files - even though I look in the correct directory - do I need to change the extension or something - or does fastboot have a command that will flash my phone with these new files ?
Joern.
(Sorry if this is a "double-entry" - my pc lost power when trying to update my previous post)....
Click to expand...
Click to collapse
No
The easy way is to go into TWRP and go to backup
create a backup of just boot or cache
this will create the folder you need to put the files in from the rar for TWRP to see them and restore them
on my phone their in TWRP/Backups/FA45xxxxx45/2015-2-24-19-46-0
your folder names will be different

Well now, - things are progressing --- I got the backup directories created, copied the files in the .rar file over - and made a restore without problems...
Rebooted, - and now my phone is restoring my contents from HTC backup - thank you so much for your assistance
Cheers,
Joern

Help please. Phone started boot looping

Hi guys,
A few days ago my phone started crashing after bout 10 seconds of getting to the android home screen. It literally didn't stop so i thought it might be smart to do a factory restore. That wiped everything but the boot/crashes still occurred. Now i'm stuck and don't know what to do. All the videos i've watched don't seem to match up with my issue and the fixes don't work. I've uploaded a video to show you what is happening.
I would be extremely grateful for any help or advice
With thanks
James

The flashing lights are normal when it comes to doing a hard reboot. You can unlock your bootloader as long as it isn't a Verizon model over on HTC's Dev website, it will tell you everything you need and the instructions. That will allow you to flash a custom recovery, such as TWRP. To flash that recovery after unlocking your bootloader, make sure you are in Fastboot and in the fastboot prompt on your PC/Mac type fastboot flash recovery recovery-name.img. From there, you can look around at the custom roms on this forum and see if anything suits you. If you prefer stock android then there are Lollipop and a few Marshmallow builds, if you prefer Sense 6/7 there's some builds for that as well. I'm going to be leaving and busy here for about 2-3 hours but when I get back if you need more assistance feel free to let me know on here.

jamesdf5 said:
Hi guys,
A few days ago my phone started crashing after bout 10 seconds of getting to the android home screen. It literally didn't stop so i thought it might be smart to do a factory restore. That wiped everything but the boot/crashes still occurred. Now i'm stuck and don't know what to do. All the videos i've watched don't seem to match up with my issue and the fixes don't work. I've uploaded a video to show you what is happening.
I would be extremely grateful for any help or advice
With thanks
James
Click to expand...
Click to collapse
It looks like a recovery issue. Can you get it to bootloader menu? Hold power + vol down till it enters bootloader
dey tuuk ur juurbs

fireball0093 said:
The flashing lights are normal when it comes to doing a hard reboot. You can unlock your bootloader as long as it isn't a Verizon model over on HTC's Dev website, it will tell you everything you need and the instructions. That will allow you to flash a custom recovery, such as TWRP. To flash that recovery after unlocking your bootloader, make sure you are in Fastboot and in the fastboot prompt on your PC/Mac type fastboot flash recovery recovery-name.img. From there, you can look around at the custom roms on this forum and see if anything suits you. If you prefer stock android then there are Lollipop and a few Marshmallow builds, if you prefer Sense 6/7 there's some builds for that as well. I'm going to be leaving and busy here for about 2-3 hours but when I get back if you need more assistance feel free to let me know on here.
Click to expand...
Click to collapse
Hi,
Thanks for the reply
The first thing i tried was unlocking the bootloader but my PC couldnt see the phone. I'll have to try again later and let you know

donkeykong1 said:
It looks like a recovery issue. Can you get it to bootloader menu? Hold power + vol down till it enters bootloader
dey tuuk ur juurbs
Click to expand...
Click to collapse
Thanks for replying. Yes i can get into bootloader

jamesdf5 said:
Thanks for replying. Yes i can get into bootloader
Click to expand...
Click to collapse
When you're in bootloader and you connect your phone to your PC, does it say fastboot usb on the phone?
dey tuuk ur juurbs

fireball0093 said:
The flashing lights are normal when it comes to doing a hard reboot. You can unlock your bootloader as long as it isn't a Verizon model over on HTC's Dev website, it will tell you everything you need and the instructions.
Click to expand...
Click to collapse
His bootloader his already unlocked see video @ 3:00, and that unlocked bootloader most likely caused the ota update to fail an so the bootloop (see video @ 0:49) (unlocking the bootloader = wipes /data/preload = ota will fail).
donkeykong1 said:
When you're in bootloader and you connect your phone to your PC, does it say fastboot usb on the phone?
Click to expand...
Click to collapse
Yep see video @ 3:00. So its the 1.44 + Win 8/10 incompatibility issue.
jamesdf5 said:
Hi,
The first thing i tried was unlocking the bootloader but my PC couldnt see the phone. I'll have to try again later and let you know
Click to expand...
Click to collapse
Its already unlocked as you can see from your bootloader screen ***UNLOCKED***
I guess you are using a Windows 8 or 10 PC? This is the reason why your PC doesn't detect your phone. It still running the old 1.44 Hboot version which isn't compatible with Win 8/10 for fastboot commands. Btw USB debugging on/off doesn't matters for using fastboot commands in bootloader or for using adb commands when in a custom recovery, its only needed to use adb commands from a booted rom. The simplest solution would be to get your hands on a Win 7 PC, install adb/fastboot and the drivers, and post the output of "fastboot getvar all" (don't post your imei / sn). Your phone is running a pretty old version, I'm sure we'll be able to find a RUU or a Guru reset rom to restore your phone back to stock.

alray said:
His bootloader his already unlocked see video @ 3:00, and that unlocked bootloader most likely caused the ota update to fail an so the bootloop (see video @ 0:49) (unlocking the bootloader = wipes /data/preload = ota will fail).
Yep see video @ 3:00. So its the 1.44 + Win 8/10 incompatibility issue.
Its already unlocked as you can see from your bootloader screen ***UNLOCKED***
I guess you are using a Windows 8 or 10 PC? This is the reason why your PC doesn't detect your phone. It still running the old 1.44 Hboot version which isn't compatible with Win 8/10 for fastboot commands. Btw USB debugging on/off doesn't matters for using fastboot commands in bootloader or for using adb commands when in a custom recovery, its only needed to use adb commands from a booted rom. The simplest solution would be to get your hands on a Win 7 PC, install adb/fastboot and the drivers, and post the output of "fastboot getvar all" (don't post your imei / sn). Your phone is running a pretty old version, I'm sure we'll be able to find a RUU or a Guru reset rom to restore your phone back to stock.
Click to expand...
Click to collapse
Thanks for your reply. Really helpful. I am using windows 10 but thankfully I have a windows 7 laptop that is stuck in an update loop . So i'm now using the laptop and have unlocked the bootloader. (I didnt have an unlocked bootloader, the image on the video i uploaded was just a screenshot of an example).
So now i'm at the unlocked bootloader stage. I now need to know what order to do things next. The phone is still bootlooping.
Using the laptop the bootloop screen now shows USB
Thanks again

donkeykong1 said:
When you're in bootloader and you connect your phone to your PC, does it say fastboot usb on the phone?
dey tuuk ur juurbs
Click to expand...
Click to collapse
It does now i've unlocked it. yes

jamesdf5 said:
It does now i've unlocked it. yes
Click to expand...
Click to collapse
Post a fastboot getvar all so we can tell you which RUU is for your phone. Be sure to delete your IMEI and serial no from the output before you post it
dey tuuk ur juurbs

donkeykong1 said:
Post a fastboot getvar all so we can tell you which RUU is for your phone. Be sure to delete your IMEI and serial no from the output before you post it
dey tuuk ur juurbs
Click to expand...
Click to collapse
Okie dokie thanks
(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.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Chicken Korma
(bootloader) imei: Chocolate
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

jamesdf5 said:
Okie dokie thanks
(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.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Chicken Korma
(bootloader) imei: Chocolate
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Latest firmware and s-on... Not good... There is no signed firmware for your phone, but there is a way to trick your phone to think it's on older firmware. @alray knows everything about that, so we'll have to wait for him to see this
dey tuuk ur juurbs

donkeykong1 said:
Latest firmware and s-on... Not good... There is no signed firmware for your phone, but there is a way to trick your phone to think it's on older firmware. @alray knows everything about that, so we'll have to wait for him to see this
dey tuuk ur juurbs
Click to expand...
Click to collapse
ok thank you :good:

jamesdf5 said:
Thanks for your reply. Really helpful. I am using windows 10 but thankfully I have a windows 7 laptop that is stuck in an update loop . So i'm now using the laptop and have unlocked the bootloader. (I didnt have an unlocked bootloader, the image on the video i uploaded was just a screenshot of an example).
So now i'm at the unlocked bootloader stage. I now need to know what order to do things next. The phone is still bootlooping.
Using the laptop the bootloop screen now shows USB
Thanks again
Click to expand...
Click to collapse
Sorry I thought the video was from you. So as I can see your phone isn't on hboot 1.44 so it should have worked fine with windows 10....
jamesdf5 said:
Okie dokie thanks
(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.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Chicken Korma
(bootloader) imei: Chocolate
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Flash twrp recovery
Code:
fastboot flash recovery twrp-3.0.0-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot your phone in twrp main menu so you can use adb commands. You'll need to change your version-main number from 7.19.61.51 to 7.19.61.10 so you can flash the 7.19.61.10 RUU which is the latest one for this phone:
Code:
adb shell
echo -ne "7.19.61.10\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
**** Better to copy/paste the command starting with "echo -ne". A typo in this command could be really dangerous for your phone so make sure you do not make any mistake.
Once back in bootloader mode, do a "fastboot getvar all" again and confirm your version-main is now 7.19.61.10, If yes, relock your bootloader using "fastboot oem lock" and flash the 7.19.61.10 RUU. Dont forget you need to use the fastboot version linked in that thread to flash the RUU, it won't work with the standard fastboot version. Then when the ruu is flashed, your phone should boot normally, go through the initial setup screen and then download and install all the ota updates so you're back to 7.19.61.51.

alray said:
Sorry I thought the video was from you. So as I can see your phone isn't on hboot 1.44 so it should have worked fine with windows 10....
Click to expand...
Click to collapse
Yes it was my video but the bootloader image was a screenshot i found on Google cos my phone wasn't getting me to bootloader so I wanted to refer to it.
alray said:
Flash twrp recovery
Code:
fastboot flash recovery twrp-3.0.0-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot your phone in twrp main menu so you can use adb commands. You'll need to change your version-main number from 7.19.61.51 to 7.19.61.10 so you can flash the 7.19.61.10 RUU which is the latest one for this phone:
Code:
adb shell
echo -ne "7.19.61.10\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
**** Better to copy/paste the command starting with "echo -ne". A typo in this command could be really dangerous for your phone so make sure you do not make any mistake.
Once back in bootloader mode, do a "fastboot getvar all" again and confirm your version-main is now 7.19.61.10, If yes, relock your bootloader using "fastboot oem lock" and flash the 7.19.61.10 RUU. Dont forget you need to use the fastboot version linked in that thread to flash the RUU, it won't work with the standard fastboot version. Then when the ruu is flashed, your phone should boot normally, go through the initial setup screen and then download and install all the ota updates so you're back to 7.19.61.51.
Click to expand...
Click to collapse
Fab thanks i'll give this a go tomorrow. I'll let you know how i get on
Thanks
James

jamesdf5 said:
Yes it was my video but the bootloader image was a screenshot i found on Google cos my phone wasn't getting me to bootloader so I wanted to refer to it.
Fab thanks i'll give this a go tomorrow. I'll let you know how i get on
Thanks
James
Click to expand...
Click to collapse
PS definitely not recognised on my Windows 10. Won't see it at all.

jamesdf5 said:
PS definitely not recognised on my Windows 10. Won't see it at all.
Click to expand...
Click to collapse
Strange, keep using your w7 pc for now. Maybe a driver problem, or maybe you are using an usb 3.0 port instead of a 2.0?

alray said:
Sorry I thought the video was from you. So as I can see your phone isn't on hboot 1.44 so it should have worked fine with windows 10....
Flash twrp recovery
Code:
fastboot flash recovery twrp-3.0.0-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot your phone in twrp main menu so you can use adb commands. You'll need to change your version-main number from 7.19.61.51 to 7.19.61.10 so you can flash the 7.19.61.10 RUU which is the latest one for this phone:
Code:
adb shell
echo -ne "7.19.61.10\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
**** Better to copy/paste the command starting with "echo -ne". A typo in this command could be really dangerous for your phone so make sure you do not make any mistake.
Once back in bootloader mode, do a "fastboot getvar all" again and confirm your version-main is now 7.19.61.10, If yes, relock your bootloader using "fastboot oem lock" and flash the 7.19.61.10 RUU. Dont forget you need to use the fastboot version linked in that thread to flash the RUU, it won't work with the standard fastboot version. Then when the ruu is flashed, your phone should boot normally, go through the initial setup screen and then download and install all the ota updates so you're back to 7.19.61.51.
Click to expand...
Click to collapse
Ok i got it working on my Windows 10.
I've just managed to flash the recovery image, cleared cache and rest. Thank you for the amazingly easy instructions.
However it won't go into the recovery it just keeps boot looping to the HTC logo.
When i select recovery i see the HTC logo and words that say entering recovery but then it restarts and continues boot looping.
Interestingly my bootloader now says **Tampered**. I'm guessing that is normal.
I appreciate all your time and effort trying to help me.
Regards
James

jamesdf5 said:
Ok i got it working on my Windows 10.
I've just managed to flash the recovery image, cleared cache and rest. Thank you for the amazingly easy instructions.
However it won't go into the recovery it just keeps boot looping to the HTC logo.
When i select recovery i see the HTC logo and words that say entering recovery but then it restarts and continues boot looping.
Interestingly my bootloader now says **Tampered**. I'm guessing that is normal.
I appreciate all your time and effort trying to help me.
Regards
James
Click to expand...
Click to collapse
Yes tampered is normal after flashing custom software. Try the old twrp 2.6.3.3, it sometime doing miracles. Mdmower's versions of TWRP are also known to boot when some other official twrp versions can't.
https://dl.twrp.me/m7/
http://android.cmphys.com/twrp-m7/
Btw did you erased the cache and rebooted the bootloader before attempting to boot in recovery ("fastboot erase cache" then "fastboot reboot-bootloader"? Its the main cause of non-booting recovery, just to be sure.

alray said:
Yes tampered is normal after flashing custom software. Try the old twrp 2.6.3.3, it sometime doing miracles. Mdmower's versions of TWRP are also known to boot when some other official twrp versions can't.
https://dl.twrp.me/m7/
http://android.cmphys.com/twrp-m7/
Btw did you erased the cache and rebooted the bootloader before attempting to boot in recovery ("fastboot erase cache" then "fastboot reboot-bootloader"? Its the main cause of non-booting recovery, just to be sure.
Click to expand...
Click to collapse
Oh dear. I have to confess i accidentally restarted the phone after i flashed it without erasing cache. :crying::crying: I then went back and flashed again and erased as you said in the instructions.
I have have tried the older version on twrp. No luck. I'm guessing i ballsed it up first time! Sorry

Can't go to stock rom HTC One M7m need stock rom

Hello.
In the first time, sorry for my english.
I have a HTC One M7 with this:
Tampered
Unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35-3218.16
OpenDSP-v35.120.274.0718
OS-
eMMC-boot 2048MB
Nov 16 2015,20:23:35.28773
In this moment, I use other ROM, I need install original stock rom.
A few months ago I try to made this (using some instructions and files of the htc1guru) but I was have problem, install fine (with android 4.x) and in the sewcond or third update of the system by HTC, when restart, not start the phone, try this operation 3 or 4 times, and always the same result, after this upgrade, when restart phone, not start, enter in bucle mode in the start.
For this reasson, now I have other rom, but need the original stock rom.
Thanks in advanced!!

wonder_skydive said:
Hello.
In the first time, sorry for my english.
I have a HTC One M7 with this:
Tampered
Unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35-3218.16
OpenDSP-v35.120.274.0718
OS-
eMMC-boot 2048MB
Nov 16 2015,20:23:35.28773
In this moment, I use other ROM, I need install original stock rom.
A few months ago I try to made this (using some instructions and files of the htc1guru) but I was have problem, install fine (with android 4.x) and in the sewcond or third update of the system by HTC, when restart, not start the phone, try this operation 3 or 4 times, and always the same result, after this upgrade, when restart phone, not start, enter in bucle mode in the start.
For this reasson, now I have other rom, but need the original stock rom.
Thanks in advanced!!
Click to expand...
Click to collapse
Please post your "fastboot getvar all" output (don't post your imei/serialno)

Thank you!
alray said:
Please post your "fastboot getvar all" output (don't post your imei/serialno)
Click to expand...
Click to collapse
This is the info:
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3931mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s
Again, thank you!

Please, somebody can help me?
I search info, but I don't view and when I was try, I have a error that I indicate above
Thanks in advance :good:

wonder_skydive said:
Please, somebody can help me?
I search info, but I don't view and when I was try, I have a error that I indicate above
Thanks in advance :good:
Click to expand...
Click to collapse
flash the 7.19.401.51 RUU
https://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

alray said:
flash the 7.19.401.51 RUU
https://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
I need block the bootloader for install this ruu?
Thank you very much!

wonder_skydive said:
I need block the bootloader for install this ruu?
Thank you very much!
Click to expand...
Click to collapse
Yes you must relock the bootloader to flash a RUU when your phone is S-ON
Code:
fastboot oem lock

alray said:
Yes you must relock the bootloader to flash a RUU when your phone is S-ON
Code:
fastboot oem lock
Click to expand...
Click to collapse
Ok, thanks
I have doubt about install, my apologies for this doubt, I feel a little absurd...
I need a stock recovery? If its yes, I don't have and I don't know how to flash.
At the moment, never flash my phone with a RUU, I search info about flash, and view that, its possible I need stock recovery ( I don't have) and in all posts, indicate a .exe "auto install".
This ruu is a .zip and I don't know how to flash...
I work in linux but also I have windows.
Again, my apologies, I feel a little embarrassed.
Thanks in advenced.

wonder_skydive said:
I need a stock recovery? If its yes, I don't have and I don't know how to flash.
Click to expand...
Click to collapse
You don't need to flash the stock recovery back before flashing the ruu. The stock recovery is included in the RUU and will be flashed automatically at the same time.
This ruu is a .zip and I don't know how to flash...
I work in linux but also I have windows.
Click to expand...
Click to collapse
To flash a ruu.zip you need to have fastboot installed on your computer. Newer RUU (starting with 7.xx.xxx.x) requires to use a fastboot.exe version distributed by HTC (often referred as htc_fastboot.exe), The regular fastboot.exe you'll find in the android sdk tool will not work for these ruu. You can download htc_fastboot from here (just save it in the same folder where you already have your regular fastboot.exe and adb.exe). Btw make sure the RUU file is in the same folder.
Reboot your phone in bootloader mode and make sure you can see "FASTBOOT USB" in red
Start a command windows from your adb/fastboot folder
To relock your bootloader, type:
Code:
fastboot oem lock
Then hit Enter. Your phone will reboot automatically
Reboot it again in bootloader mode and again make sure "FASTBOOT USB" in showing in red characters
Type:
Code:
fastboot oem rebootRUU
and hit Enter (note that fastboot commands are case sensitive so don't forget "RUU" are capital letters). Your phone will reboot in RUU mode (a black screen with a silver HTC logo). At this point your phone is ready to flash the RUU and waiting for the flash command, type:
Code:
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
The flash process will start. Don't touch anything until it's completed: your phone should reboot twice during the process 1st time in the middle of the flash and it will go back in ruu mode by itself and continue the flashing process. The 2nd time should make your phone reboot in the rom at the welcome/setup screen. Do not disconnect or play with your phone or computer until it's rebooted at the welcome screen.

alray said:
You don't need to flash the stock recovery back before flashing the ruu. The stock recovery is included in the RUU and will be flashed automatically at the same time.
To flash a ruu.zip you need to have fastboot installed on your computer. Newer RUU (starting with 7.xx.xxx.x) requires to use a fastboot.exe version distributed by HTC (often referred as htc_fastboot.exe), The regular fastboot.exe you'll find in the android sdk tool will not work for these ruu. You can download htc_fastboot from here (just save it in the same folder where you already have your regular fastboot.exe and adb.exe). Btw make sure the RUU file is in the same folder.
Reboot your phone in bootloader mode and make sure you can see "FASTBOOT USB" in red
Start a command windows from your adb/fastboot folder
To relock your bootloader, type:
Code:
fastboot oem lock
Then hit Enter. Your phone will reboot automatically
Reboot it again in bootloader mode and again make sure "FASTBOOT USB" in showing in red characters
Type:
Code:
fastboot oem rebootRUU
and hit Enter (note that fastboot commands are case sensitive so don't forget "RUU" are capital letters). Your phone will reboot in RUU mode (a black screen with a silver HTC logo). At this point your phone is ready to flash the RUU and waiting for the flash command, type:
Code:
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
The flash process will start. Don't touch anything until it's completed: your phone should reboot twice during the process 1st time in the middle of the flash and it will go back in ruu mode by itself and continue the flashing process. The 2nd time should make your phone reboot in the rom at the welcome/setup screen. Do not disconnect or play with your phone or computer until it's rebooted at the welcome screen.
Click to expand...
Click to collapse
In the first time, thank you very much for your help and explanation.
Your directions have been very helpful and have helped me to learn a lot. Thank you.
I made all steps like you indicate, in the last step, on you indicate this:
alray said:
The flash process will start. Don't touch anything until it's completed: your phone should reboot twice during the process 1st time in the middle of the flash and it will go back in ruu mode by itself and continue the flashing process. The 2nd time should make your phone reboot in the rom at the welcome/setup screen. Do not disconnect or play with your phone or computer until it's rebooted at the welcome screen.
Click to expand...
Click to collapse
I wait to finish all, in terminal windows, appears that, htc_fastboot was finished (with any error), all ok, but the phone appears a progress bar stop at 80 or 90%.
I wai for a 10-20 or 30 minutes, and the progress bar was continue stoped.
I try in terminal windows type: htc_fastboot reboot (I view this in the past in some post) and then the phone was reboot.
And yes, the phone are flashed and start all fine!!
And a doubt: this ruu contain the last rom? I question this because, after config the phone, I view that, not have any system update, and for example, in menu, the colour of screen in menu are black, and I remember that, in some update this colour screen menu, was changed to blue.
Again, thank you very much for your details and help!!!
It's a pleasure, few people help / teach so well.
Regards!

wonder_skydive said:
You don't need to flash the stock recovery back before flashing the ruu. The stock recovery is included in the RUU and will be flashed automatically at the same time.
To flash a ruu.zip you need to have fastboot installed on your computer. Newer RUU (starting with 7.xx.xxx.x) requires to use a fastboot.exe version distributed by HTC (often referred as htc_fastboot.exe), The regular fastboot.exe you'll find in the android sdk tool will not work for these ruu. You can download htc_fastboot from here (just save it in the same folder where you already have your regular fastboot.exe and adb.exe). Btw make sure the RUU file is in the same folder.
Reboot your phone in bootloader mode and make sure you can see "FASTBOOT USB" in red
Start a command windows from your adb/fastboot folder
To relock your bootloader, type:
Then hit Enter. Your phone will reboot automatically
Reboot it again in bootloader mode and again make sure "FASTBOOT USB" in showing in red characters
Type:
and hit Enter (note that fastboot commands are case sensitive so don't forget "RUU" are capital letters). Your phone will reboot in RUU mode (a black screen with a silver HTC logo). At this point your phone is ready to flash the RUU and waiting for the flash command, type:
In the first time, thank you very much for your help and explanation.
Your directions have been very helpful and have helped me to learn a lot. Thank you.
I made all steps like you indicate, in the last step, on you indicate this:
I wait to finish all, in terminal windows, appears that, htc_fastboot was finished (with any error), all ok, but the phone appears a progress bar stop at 80 or 90%.
I wai for a 10-20 or 30 minutes, and the progress bar was continue stoped.
I try in terminal windows type: htc_fastboot reboot (I view this in the past in some post) and then the phone was reboot.
And yes, the phone are flashed and start all fine!!
And a doubt: this ruu contain the last rom? I question this because, after config the phone, I view that, not have any system update, and for example, in menu, the colour of screen in menu are black, and I remember that, in some update this colour screen menu, was changed to blue.
Again, thank you very much for your details and help!!!
It's a pleasure, few people help / teach so well.
Regards!
Click to expand...
Click to collapse
Yes this is the latest version. You're welcome