yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M7)] selayan:
Right here at the bottom of post 2.

http://xdaforums.com/showthread.php?t=2485319

There is signed and decrypted versions. I guess you can't go backwards. So you should not try to flash .8 if you are on .10, etc.

I downloaded the .15 ruu from that page, I'm using Linux mint 16 x64 so it's just a zip file, once downloaded. Upon flashing that ruu after some tries, booting to recovery took me to a blank screen so looks like if you do not load stock recovery before locking boot loader and flashing ruu, it messes up the recovery you have because I left twrp on before locking and flashing.
[Verizon HTC One (M7)] Gizmoe:
Those zips are not RUU's. They just contain hboot, radio and boot img. An RUU stands for rom update utility and are made by HTC to update the software. HTC stopped providing them and we are not allowed to share them on xda. A true RUU is an exe file encrypted and signed and needs HTC sync to run. The only thing close to that we can use is the decrypted version. The decrypted version has to be renamed to rom.zip and run via fastbootRUU manually. The state of the phone doesn't matter as it wipes and replaces every partition. The reason we lock bootloader prior to running it is because you would have to flash a custom recovery and re root to use Scotties locking method which would be taking a step backwards.

Edit. The zips mentioned are RUU's. It does flash recovery however and booting to a black screen is normal behavior for the stock recovery.
[Verizon HTC One (M7)] selayan:
Yea maybe I got confused with the names then. So what is the point of signed and decrypted? I swear I tried decrypted one's and they didn't work but signed one's did. Many times I downloaded all the versions, renamed them, booted to ruu, and did fastboot flash zip Rom.zip and it just stayed at sending for half an hour in my Linux terminal until I decided to close it and hard shut off the phone. So I dunno why this was happening but when it did work finally I forgot weather I used a signed or decrypted zip.
[Verizon HTC One (M7)] Gizmoe:
Anyone can sign a zip file. Decryption makes it so it will run on an s off device. As encrypted only runs on an s on device. Only HTC could re encrypt an RUU. As for why the decrypted version wasn't working for you I couldn't say. The file size should be a little over a gigabyte though. The link in OP doesn't actually work. I have used the decrypted version to return to stock so I could take the 4.3 update and retain s off. I will do the same for 4.4 which should be out in a few days. I always like to play with the new stock version to see how it compares.
[Verizon HTC One (M7)] selayan:
Yeah the file was a little over 1gb. Not sure what my issues were, but after many tries it did work. It could be because I have an actual android environment on my Linux box as well as a mini fastboot directory as well or who knows.

I was just worried that every time it said "sending" for minutes on end and I would need to unplug and shut down the phone that I would end up getting bricked.
[Verizon HTC One (M7)] Gizmoe:
Yeah that's never a good feeling. I hate having to make the decision to pull the plug not knowing if you will ever see hboot again. I've actually had better luck with ADB in windows with this particular phone than in linux. After I actually got fastboot to work.
[Verizon HTC One (M7)] selayan:
Yea but fastboot in Windows 8.1 does not work unless your on firmware 4.3. Adb works as long as you are in recovery or the phone os, but once you go to boot loader adb and fastboot will not recognize the device. Even though I have the asrock mobo. I think another poster confirmed too since they have a phone with 4.3 and Windows 8.1
[Verizon HTC One (M7)] Gizmoe:
Yeah it's a b#@ch. I was lucky and able to get mine working with 8.1 via the asrock drivers on a gigabyte mb.
[Verizon HTC One (M7)] Mono41:
Last month I decided to root my HTC One. I tried out a few custom roms, but decided to stay on Sense 5. Anyways, shortly after rooting, I started having some issues. For example, I can no longer send or receive MMS messages, which is rather frustrating. Also, all my notifications are always expanded, and it's a bit annoying. I figured it had something to do with rooting, so I deleted things like Xposed and any modules I downloaded through it to try to resolve the problems. That didn't work, and neither did factory resetting my phone. So anyways, I don't really care much for being rooted anymore, and I'm thinking about unrooting, but leaving s-off, in case I change my mind in the future. I just have a few questions. First, does anyone think that unrooting may fix the problems I'm having? Second, if I use this method to unroot, am I going to lose any data? Like, is my phone going to get wiped in the process? These might sound like stupid questions, but I'm really new to rooting.
[Verizon HTC One (M7)] selayan:
This depends on the rom you are using. Are you using a global rom on a Verizon htc one? If so you need the verizon MMS settings set correctly. Download Tweaker from the Play store and use that for getting the mms settings based on your provider. Most global roms do not work properly on Verizon phones. Again, I'm not sure what you mean by notifications being expanded? Perhaps there are settings or tweaks within the ROM you use to hide those things.

Nothing sounds like a rooting issue, I've had all my phones rooted and I never had issues and if I did, they were mainly software/rom related or things I did not know I could change (advanced tweaks or settings).

Yes your phone will get wiped when you use this thread's method to return to stock. You will still stay S-OFF though and have a locked bootloader at the end.
[Verizon HTC One (M7)] Gizmoe:
[MENTION=5674367]Mono41[/MENTION] just and fyi don't do a factory reset unless you want everything wiped. When successful you will lose all data. I would backup sd card, flash RUU method in this thread. Then try factory reset from bootloader once stock. Then you can just take all the updates to 4.3 and then install custom recovery and root if you want to. Root will not cause the problems you are having. Something is messed up from rom flashing that needs to be rectified.
[Verizon HTC One (M7)] thewahlrus:
All of a sudden it doesn't recognize my SIM. I relocked but get an error flashing

(bootloader) Read zipped android_info fail

FAILED (remote: 24 parsing android-info fail)

I was able to flash firmware, but get this error trying to flash 2.10.05.1 odex full from Santod's thread.
[Verizon HTC One (M7)] Gizmoe:
I

Santods rom isn't for this process. Only the decrypted RUU.

I see now why people are going to his thread. As selayen pointed out earlier they are at the very bottom of post 2 on Santods stock rom thread.

[MENTION=1773831]thewahlrus[/MENTION] you need to go down to bottom of second post and use the ones that say decrypted. You are trying a rom meant for custom recovery.
[Verizon HTC One (M7)] selayan:
Do you know where we can find the md5 on the server for those files at the bottom of that thread? The site those files are hosted on is through flyhalf205 and each time I click the little info icon to the right a javascript window pops up listing md5, sha1, so on but next to those titles there is no md5sum. I know how to get the md5 in my terminal in Linux but I have nothing to compare it to.

I downloaded the .15 ruu and was going to start fresh after trying out a gpe edition Rom in case anything went wrong.
[Verizon HTC One (M7)] thewahlrus:
Got it now, flashed decrypted and phone is up and running again. Thanks.

Oh Snap. My fault I grabbed the wrong one. Thanks!
[Verizon HTC One (M7)] gtofan350:
Hello everyone! My current issue after trying this guide is after I got the normal failure message after the first attempt at flashing the RUU, my phone went completely blank and unresponsive. I've tried every type of button press and hold but nothing works. When I plug the phone into my pc, I get the chime that my pc recognizes the hardware but adb or fastboot doesn't see it. As of right now the phone is a paper weight. Any suggestions?
[Verizon HTC One (M7)] disconnecktie:
Can you get into the boot loader and does the led come on when you plug it in?
[Verizon HTC One (M7)] selayan:
Do you have the HTC ruu screen with four triangles? Type fastboot devices after connecting the phone. If the device shows up in the terminal then you have fast boot. Try holding power and volume down if you still have boot loader it will boot to bootloader.

If you are s off and still access to fastboot you just need to do fastboot oem rebootRUU then keep trying to flash the ruu again. I've had this happen before and it failed at the hboot section, so I had four triangles in the corners. All I did was keep connecting the phone and flashing the ruu until it was successful. It takes a few tries.
[Verizon HTC One (M7)] gtofan350:
Negative. I've held the power button and vol down together for 5 minutes at one point. No led when I plug on the phone.
[Verizon HTC One (M7)] selayan:
Hold the power button until its completely off then power button and volume down. It will turn on but you won't see anything. It's stuck in a loop because of a failed ruu flashing. Do fastboot devices in terminal and you should get your device listed there. Boot into ruu mode from console even though you won't see anything on screen and keep trying to flash the ruu.

When its stuck like that you won't get an led indication.
[Verizon HTC One (M7)] gtofan350:
How will I know when it's completely turned off when the screen is off?
[Verizon HTC One (M7)] selayan:
You can see a certain backlight around the screen faintly when its stuck with a black screen like that. Or plug it in to an ac outlet see if the battery starts charging, were you on low charge when you were flashing ?
[Verizon HTC One (M7)] gtofan350:
When I started, I was full charge. When I plug into the wall, the led doesn't turn on.
[Verizon HTC One (M7)] selayan:
Well just keep trying to turn it on, and connecting it to the pc and do fastboot devices until you get your device listed in the terminal. Then do the ruu command to get to the ruu mode and try flashing again.
[Verizon HTC One (M7)] disconnecktie:
Typically when the led charge light doesn't even come on that means you have a hard brick. Not being able to enter the bootloader is another sign of a hardbrick.
[Verizon HTC One (M7)] gtofan350:
So most likely I'm SOL?
[Verizon HTC One (M7)] selayan:
It's possible. I've had a bad ruu flash before. I lost hboot but still had ruu screen with four triangles. I think it happens when you try to flash an ruu that is a version lower than what you have. Even though it should not happen if you are s off, shouldn't mattter what ruu version you flash. But it all depends when the ruu fails. If its during the time it's loading the hboot then you loose bootloader but still have fastboot.

Plug the phone to the pc. Do fastboot devices what do you get. Then try fastboot getvar all.
[Verizon HTC One (M7)] gtofan350:
When I plug into the pc I get the chime that the pc acknowledges the device. When I go into device manager, my phone shows up as "MyHTC". Adb doesn't see anything and when I check fastboot devices all I get is ????????????. The RUU failed when it asks the flush again, when it is supposed to fail then u try again. After it failed, I was kicked out of RUU and couldn't get back in so here I am.
[Verizon HTC One (M7)] disconnecktie:
He's not getting anything though. Just a black screen and no charge led. No bootloader or hboot for that matter. Sounds to me like a bad ruu flash (I don't know if he checked the md5). He might could recover it if he is able to get fastboot commands.
[Verizon HTC One (M7)] selayan:
So fastboot works. Yea sounds like a bad download and flash. When it kicks you out of ruu mode it should boot back into it. If it did not, you have go back into it and then flash again. Looks like fastboot does not recognize your device if you get ????. What does fastboot getvar all give you?
[Verizon HTC One (M7)] gtofan350:
I'll give that a go tomorrow. I really appreciate the help guys.
[Verizon HTC One (M7)] scotty1223:
for the record... this is not my thread. ;) on to your issue... i have heard of htc phones entering a "deep sleep" mode,wich can be wakened by plugging into a wall charger(not a PC) for 8 hours. after that time try and hold power again,and see what happens. if you get flashing softkeys after 20ish seconds,start holding vol down as well to get to hboot, or you can let the phone go and see if it boots.

another thing you might try is to look thru the "purchased a java card for s off" thread. i seem to remember sonic recieving and somehow fixing a phone with your same or similar issues.

failing all that,jtag might be your only option. if your decrypted ruu had a corrupt(via incomplete download) hboot,or something happed while flushing the first stage of firmware(as a result of windows driver issue,program interferance,power surge,funky usb cable or port,or who knows what) then likely you are in a processor "do not boot" mode,wich is a pretty effective hard brick. you can try mobile tech videos for an esitimate on jtag repair
[Verizon HTC One (M7)] gtofan350:
Thank you for that Scotty. This gives me a lot to try and hopefully one of them works.
[Verizon HTC One (M7)] gtofan350:
So after executing "fastboot getvar all" on cmd this is what i get

C:\Users\Adam\Desktop\Android>fastboot getvar all

INFOversion: 0.5

INFOversion-bootloader: 2.46.0000

INFOversion-baseband: N/A

INFOversion-cpld: None

INFOversion-microp: None

INFOversion-main:

INFOversion-misc: UNKNOWN

INFOserialno:

INFOimei: 355000000000010

INFOmeid: 00000000000000

INFOproduct:

INFOplatform: HBOOT-8064

INFOmodelid: *********

INFOcidnum:

INFObattery-status: good

INFObattery-voltage: 3434mV

INFOpartition-layout: Generic

INFOsecurity: off

INFObuild-mode: SHIP

INFOboot-mode: UNKNOWN

INFOcommitno-bootloader: dirty-14eb688c

INFOhbootpreupdate: 11

INFOgencheckpt: 0

all: Done!

finished. total time: 0.043s

Also I'll note that when I plug my phone into my computer, HTC Sync opens.
[Verizon HTC One (M7)] scotty1223:
So your phone is working again? What was the fix?
[Verizon HTC One (M7)] selayan:
Looks like you have a dirty hboot sector from the bad flash. So the ruu flashing must have started then failed at hboot. Make sure while you ruu flash that nothing else major is going on.

You still have s off, your phone chimes when plugged in and you have fastboot access.

I would download a decrypted version of the ruu you are trying to flash just to rule out a bad download. Check the santod thread at the bottom of post two.

Even though you see nothing on the phone, plug it in, pull up terminal, and go to ru mode even though you won't notice. Only thing you can do is try flashing the ruu over and over until it's successful.

Remove HTC sync manager only. Not the drivers.
[Verizon HTC One (M7)] gtofan350:
Still having the same issues. I've been trying to fastboot a few commands and when i try to execute "fastboot oem rebootRUU" i get this "... INFOStart Veryify: -1"

when I enter fastboot reboot-bootloader i get

"rebooting into bootloader... OKAY [ 0.042s ]

But I'm not booted into bootloader and the screen is still black and the phone is still completely unresponsive.

I guess it reassuring that getvar all is showing something but that's as much as I get out of the phone. I was hoping that posting that info would bring any ideas on how to get this phone back up.
[Verizon HTC One (M7)] scotty1223:
What phone do you have?
[Verizon HTC One (M7)] gtofan350:
I have the verizon htc one.
[Verizon HTC One (M7)] selayan:
So it looks like you lost ruu mode. Since phone boots in the boot loader mode but you dont see it, can you flash the hboot.img from the ruu in fastboot ?
[Verizon HTC One (M7)] gtofan350:
I don't know anything about that or how to do it but I'll try anything at this point.
[Verizon HTC One (M7)] selayan:
Is your ruu a zip file? Copy it to another area where you can unzip it, look for an hboot.img file. Take that file and put it in your adb directory. Then do fastboot devices and see that your device is somewhat plugged in. Unplug it and plug it in if you have to. Do either adb reboot boot loader or fastboot reboot - bootloader and get that okay message you got earlier.

Then do fastboot boot hboot.img (that hboot image that you took from the zip).
[Verizon HTC One (M7)] gtofan350:
So now when I plug into the computer, the phone connects to the PC then 2 seconds later disconnects. I tried a different USB port but it's doing the same thing.
[Verizon HTC One (M7)] scotty1223:
are you sure? :confused: does your phone have a fingerprint scnaner? your hboot version is that of the one max,and what your describing is pretty accurate for a phone whose had an incorrect bootloader and firmware flashed.

the other possibility is that you have a one,and have tried to install a one max ruu :eek:

what is the md5 of the ruu that you tried to flash?

he cannot fsatboot flash hboot with a normal ship hboot. i think we need to hold off flashing any ruus,hboots or firmware until we figure out exactly why his phone shows a one max hboot version

also,i dont believe he did "lose" ruu mode. its there,he just cant see it. the cmd window doesnt show anything after the command is entered.

try

fastboot oem rebootRUU

give it a few seconds after you get the "finished" message. then

fastboot getvar all

and see if your boot-mode has changed to RUU

scott@Scott:~/sdk-tools$ [COLOR="Red"]adb reboot bootloader[/COLOR]
scott@Scott:~/sdk-tools$ [COLOR="Red"]sudo ./fastboot oem rebootRUU[/COLOR]
[sudo] password for scott:
...
(bootloader) Start Verify: 0
OKAY [ 0.052s]
finished. total time: 0.052s
scott@Scott:~/sdk-tools$ [COLOR="Red"]sudo ./fastboot getvar all[/COLOR]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3827mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader)[COLOR="Blue"] boot-mode: RUU[/COLOR]
(bootloader) commitno-bootloader: dirty-b617f0f0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
scott@Scott:~/sdk-tools$ [COLOR="Red"]sudo ./fastboot reboot-bootloader[/COLOR]
rebooting into bootloader...
OKAY [ 0.044s]
finished. total time: 0.045s
scott@Scott:~/sdk-tools$ [COLOR="Red"]sudo ./fastboot reboot[/COLOR]
rebooting...

finished. total time: 0.044s
scott@Scott:~/sdk-tools$
[Verizon HTC One (M7)] gtofan350:
what is the md5 of the ruu that you tried to flash?

Where can I find the md5 for the RUU? I got it from the top of this thread. I modified the android-info so now it says "modelid: PN0731000

cidnum: VZW__001

mainver: 1.11.605.4

btype:1

aareport:1

hbootpreupdate:12

DelCache:1

---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------

Here's the md5 0e2465cd034653461039be6e1fee58d2
[Verizon HTC One (M7)] scotty1223:
does your phone have a fingprint scanner? and a 5.9" screen?
[Verizon HTC One (M7)] gtofan350:
No, it isn't a HTC One max.
[Verizon HTC One (M7)] scotty1223:
does someone with a max use your adb and fastboot? you have a one max hboot.
[Verizon HTC One (M7)] selayan:
Mine says ship as well and security off. I didn't realize you had the one max hboot. Definately could have downloaded a wrong ruu.
[Verizon HTC One (M7)] gtofan350:
I dont know anyone with a One max and I've never seen or held one.
[Verizon HTC One (M7)] scotty1223:
wait,what?

you modified the android info document? why did you do that and what did it say before?

also your md5 does

not

match that listed in the OP
[Verizon HTC One (M7)] gtofan350:
I flashed a work around so I could use google wallet on my One. Does this mean I'm boned?

Here's the download link to the RUU I downloaded.

http://fs1.d-h.st/download/00091/bQF/RUU_0P3PIMG_Verizon_WWE_1.11.605.4.zip
[Verizon HTC One (M7)] scotty1223:
i have no idea what workaround your refering to. why did you modify android info ??
[Verizon HTC One (M7)] gtofan350:
http://xdaforums.com/showthread.php?t=2436383

here's the mod i flashed
[Verizon HTC One (M7)] selayan:
The ruu link in thread on page one here does not work. If you look on page 26 or 27 of this thread there is a link to a thread with the ruu's we use to flash for the Verizon HTC one. You need the decrypted version.
[Verizon HTC One (M7)] gtofan350:
Will the correct RUU help me any in this situation?
[Verizon HTC One (M7)] selayan:
Yes I would try the version that getvar all says you need. Decrypted. Unless you flahsed something wrong from the start.
[Verizon HTC One (M7)] gtofan350:
All i flashed was the incorrect ruu
[Verizon HTC One (M7)] selayan:
Which explains while your hboot and ruu mode are borked. If you have a Verizon one I'm not sure why your boot loader version is 2.46.
[Verizon HTC One (M7)] scotty1223:
ahhhhh its all very clear now. yep you sure did try and install a max ruu :rolleyes: where did you get that link??

0P3IMG=max

PN07IMG=one

in the future please be more careful what you flash.

i dont know if an ruu will help you or not. it depends on what partitions the max ruu overwrote.

heres what you need to do:

-download CORRECT ruu

-place in fastboot folder

-enter

fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip zipname.zip

expect it to fail the first time with a pre-update error. with some luck,when the bootloader reboots,youll be able to see it on the screen again. dont panic and start pushing power/vol buttons right away. give it a couple minutes to reboot back to a visible ruu mode

enter,a second time(even if you dont see ruu mode on the phone screen):

fastboot flash zip zipname.zip

this time it should finish. keep your fingers crossed ;)

i think you may be OK,since both hboots are group 8064. as i said it really depends on this point the damage done to other firmware,as not all of it lives in flash memory and is re-writable when damaged.

---------- Post added at 01:46 AM ---------- Previous post was at 01:44 AM ----------

it actually doesnt matter if he uses the decrypted version or not. he just needs one that is good,and needs to make sure he verifies the md5 prior to screwing up his phone with further bad flashes.

but a signed version will be fine.
[Verizon HTC One (M7)] gtofan350:
C:\Users\Adam\Desktop\Android>fastboot erase cache

******** Did you mean to fastboot format this partition?

erasing 'cache'...

FAILED (remote: erasing error!)

finished. total time: 0.005s

This is the message I get trying to fastboot erase cache
[Verizon HTC One (M7)] selayan:
Look on page two of that thread. You are flashing firmware when you need the ruu. The ruu is like 1.2gb. Or did you rename it to firmware ?
[Verizon HTC One (M7)] gtofan350:
I renamed it firmware
[Verizon HTC One (M7)] scotty1223:
how are you getting to fastboot? if via power/vol down the phone may be in hboot. you may need to push power to select fastboot(even tho you cant see it,its at the top of the list)

however you were able to enter ruu mode earlier,you need to repeat that process ;)
[Verizon HTC One (M7)] selayan:
Just fastboot to ruu mode and keep trying to flash the right ruu. At one point it should succeed as long as it's the correct one.
[Verizon HTC One (M7)] gtofan350:
C:\Users\Adam\Desktop\Android>fastboot oem rebootRUU

...

(bootloader) Start Verify: -1

OKAY [ 0.044s]

finished. total time: 0.046s

This is what I'm seeing after attempting to boot into RUU mode. Does this look right? I'm flying blind essentially since the screen is completely blank.
[Verizon HTC One (M7)] selayan:
Yea I can check my output for you when I get home.
[Verizon HTC One (M7)] scotty1223:
yes,youre fine. continue on