yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
you are S-OFF correct?
[One (M7) Q&A, Help & Troubleshooting] Bocko92:
Yes, that is correct.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
okay, if you look under the FAQ SECTION (now in post #2 thanks to [MENTION=4564111]KidCarter93[/MENTION]) under "Not so FAQ", you can see what you can and cannot do

http://xdaforums.com/showthread.php?p=52135024&postcount=2

with s-off / s-on ... (re)locked / unlocked
[One (M7) Q&A, Help & Troubleshooting] Bocko92:
So there's no point in even relocking the bootloader. Thanks mate, you saved me some time right there :)

---------- Post added at 11:43 PM ---------- Previous post was at 10:52 PM ----------

Am, i just ran the ruu and it's stuck at "checking header........."

any idea why that might be ? i'm with custom recovery and rom - s-off, unlocked bootloader.
[One (M7) Q&A, Help & Troubleshooting] melted_cow:
Hi all,

I need to go back to stock completely for warranty purposes. I've installed custom firmware, a new radio and some other things I can't remember. If I follow this guide will it reset everything, including radio, firmware etc. back to normal or is there anything else I'd need to do?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
sounds like a bad download... did you verify MD5 on the file you downloaded?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
If you follow the guide properly, everything will be reset to "out-of-the" box. If you have questions, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll tell you what files you need.

Please read the guide once or twice (completely) until you are comfortable with the procedure. It's written in a very specific order to avoid any potential problems.
[One (M7) Q&A, Help & Troubleshooting] melted_cow:
Thanks a lot for the help. Here's the result minus s/n and IMEI

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.55.0000

(bootloader) version-baseband: 4A.21.3263.04

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.62.401.1

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 3872mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-bb768ae1

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

EDIT: I just looked at the Nandroid restore method. My CID was originally H3G__001 and I can find a Nandroid for that CID but I can't find an RUU for H3G__001. Is the Nandroid method safe for me?
[One (M7) Q&A, Help & Troubleshooting] Bocko92:
Yes i verified the download, maybe it's a problem with the recovery? It must be stock?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Two options (depends if you need to be on the original carrier):

1- you can choose to go unbranded international, just set CID to HTC__001 and use RUU.ZIP method using 1.28.401.7 ruu.zip

2- Yes the CWM nandroid method is good for you if you want to restore to H3G__001; if you look, the example, is actually based on H3G__001 files; the nandroid is 1.28.771.6 so try this stock recovery in step 4 http://d-h.st/uGM or possibly this http://d-h.st/Vg2

once the first OTA goes through properly, you can be certain everything is 100% (including recovery/firmware as it is contained in the ota)

The only slightly tricky part (sometimes) is the stock recovery, for example, here he got the red triangle (meaning the OTA isn't going through), http://xdaforums.com/showpost.php?p=50593184&postcount=589 but solved it using a different recovery;

and be patient: http://xdaforums.com/showpost.php?p=50703466&postcount=614

Also IF you intend on going S-Off to S-On do it

before

any update to 3.xx, though I would recommend to stay S-Off, especially since you're in the UK, and they are quite lenient about these things (from what I've read on the forum).
[One (M7) Q&A, Help & Troubleshooting] nkk71:
No that's not it, the ruu will overwrite EVERYTHING on your phone, you can see the example in post #8

C:\ADB3>fastboot flash zip ruu.zip
sending 'zip' (1033216 KB)...
OKAY [ 41.559s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...

etc.

Maybe a connection issue (USB port / cable), also what OS are you using?
[One (M7) Q&A, Help & Troubleshooting] Bocko92:
I'm running windows 7, the phone was connected with the original htc cable via usb 2.0 port. I'm not sure if i did run the RUU as admin though, because it wouldnt start the 1st time, then i clicked as admin and then it popped up with 2 instances one of which saying it's already running, could that be the cause?

Otherwise in my understanding it should just flash completely stock with no problem. Last time my phone was stuck at checking header as well :D
[One (M7) Q&A, Help & Troubleshooting] nkk71:
maybe best to reboot your computer, disable any antivirus and firewall you have, and try again... is your adb/fastboot updated? (type adb version)

you can find 1.0.31 here: http://www.androidfilehost.com/?fid=23329332407585867
[One (M7) Q&A, Help & Troubleshooting] Bocko92:
I'll try to reboot and report later since i can't right now. Yes, my adb reports version 1.0.31

---------- Post added at 12:01 PM ---------- Previous post was at 11:31 AM ----------

Rebooted, ran as admin .. same result - checking header ......

what is this header anyways?

maybe a different usb port / computer may work ?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
If I'm not mistaken, it's checking the zip is not corrupt.

after that it parses it and checks your CID and MID against the ones in android-info.txt

hence, either the zip is corrupt, or is getting corrupted during the send operation due to USB port / OS problems... have you considered an Ubuntu Live USB?
[One (M7) Q&A, Help & Troubleshooting] Bocko92:
Am using an .exe file RUU - http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/

This one to be exact, not a zip ?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Oh that one, yeah seems many people are having problems running that ruu, though i can confirm it worked (after a lot of trouble!!)

http://xdaforums.com/showpost.php?p=52127142&postcount=30

maybe easier to go back to 1.28.401.7 and take OTA updates to 4.19?
[One (M7) Q&A, Help & Troubleshooting] Bocko92:
Yeah, seems so. So i have to flash hboot 1.44 now and then .runn the old ruu ? Again, no need to lock anything?

this one ? http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
[One (M7) Q&A, Help & Troubleshooting] nkk71:
quickest way would be ruu.zip method using http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/

fastboot oem rebootRUU

fastboot flash zip ruu.zip

fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.

fastboot reboot-bootloader

no need to lock or anything else with S-Off; just the above 4 commands are your phone is back to stock ROM (and completely wiped!!)

and you can take OTAs

BTW, saw you on ARHD62.0 ... why change? you know official Sense 6 on M7 will be out on ARHD too.
[One (M7) Q&A, Help & Troubleshooting] Bocko92:
So if i use the .zip file i won't need to downgrade the hboot ? Just flash the zip and i'm good to go?

Thank you for your help. Well, i got my phone changed with a new one because of the camera issues and i read that the port is generating more heat / causing pink camera again for some users, so i figured better not risk it since sense 6 is comming soon anyway..
[One (M7) Q&A, Help & Troubleshooting] nkk71:
1- yes the ruu.zip method only needs those 4 commands, (the first flash will downgrade hboot, the second will install the rest, you can see a live example in post #8)

2- soon, is always a relative term ;) and I'm on 62.0 no heating problems or camera problems either (except I don't like the new camera app)... or you could stay on 53.0 until it comes out.

But to each his own :)

Enjoy
[One (M7) Q&A, Help & Troubleshooting] Bocko92:
Thank you mate, i don't think there's more helpful dude on this forum...

one last retarded question on my side - the zip file and the .exe file lead to exactly the same result, right ? Because I downloaded the .exe and wonder if it's worth it to wait for the zip to download or should just downgrade hboot and run it.

P.S to be honest i love sense 6, but i'm afraid of getting my camera damaged again .. it was quite a wait for that replacement ;D
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yeah same result, go for it if you have it

just wanted to save you an extra step :)

so downgrade hboot, run RUU.EXE

(no locking, no nothing :))
[One (M7) Q&A, Help & Troubleshooting] nkk71:
If you think it's due to the overheating, maybe just install ElementalX and use "super-cool" (or whatever it's called) temperature throttling. But I'm on stock kernel and no overheating here (at least no more than before).... usually can get up to 40~45C max.
[One (M7) Q&A, Help & Troubleshooting] MasterThiefGarrett:
Great success!!

Followed your .ZIP RUU guide from post #4 and it worked perfectly, back to Locked and S-ON :)

without tampered and back to hboot 1.44 :)

Now for the warranty... cracking top speakers are NOT funny :P
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Well it is a SuperGuide LOL :cowboy:

Good luck with repair, hope it comes back soon :)
[One (M7) Q&A, Help & Troubleshooting] butcher211:
Hi,

thank you! It worked!

I used the firewater, ruu-zip, guru-bootloader-reset way and everything's fine!

The both other guides which I used before dont had the useful information included that you have to lock your bootloader again. (not relock)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Glad to be of service :) and happy you liked the guide; took quite a while to write ;)

Also LOCKED/RELOCKED won't matter with S-OFF (as mentioned in post #2 under Not so FAQ #2)

but if you're sending for warranty, then LOCKED is mandatory, relocked will probably get rejected.
[One (M7) Q&A, Help & Troubleshooting] DHD22800:
Hi.

I have a little problem: HBOOT 1.56 and firmware 4.19.401.11 and I can't get S-OFF...firewater doesn't work, and RumRunner doesn't support my HBOOT. How I can get S-OFF?

Thanks
[One (M7) Q&A, Help & Troubleshooting] nkk71:
You'll have to ask in the S-OFF threads, some devices just can't be S-OFFed at the moment.

But you should try both rumrunner, and firewater.... different exploits.

Good Luck
[One (M7) Q&A, Help & Troubleshooting] MasterThiefGarrett:
I set my device back to S-ON for warranty purposes by doing this:

fastboot oem writesecureflag 3

Does this REALLY set the device from S-OFF to S-ON or does it 'trick' the phone into 'thinking' it's S-ON?

Kind of hard to believe that a simple fastboot command could do such a thing :)
[One (M7) Q&A, Help & Troubleshooting] cschmitt:
It really sets it back to s-on.
[One (M7) Q&A, Help & Troubleshooting] MasterThiefGarrett:
But getting it to S-OFF again isn't as simple as a fastboot command then... hmmm too bad ;)
[One (M7) Q&A, Help & Troubleshooting] tronicx0906:
Hello, I am trying to S-off my HTC One 4.4.2 and I already installed weaksauce and everything is working correctly.

Its just when I say yes in the cmd for firewater to start. It only completes 1 or 2 bottles and then just stops. Any help?

Do you understand the implications of these warnings?

(Yes/No)
Yes
Yes

!!If firewater hangs for more than 2 minutes or device enters qhusb mode, hold power for 60 seco

!!If firewater hangs for more than 2 minutes or device enters qhusb mode, hold power for 60 seco

!!If firewater hangs for more than 2 minutes or device enters qhusb mode, hold power for 60 seco
nds !!
=========================================================================
preparing, one moment

The first bottle is open
chugging..........
[One (M7) Q&A, Help & Troubleshooting] nkk71:
We wish!!

As mentioned above:

You'll have to ask in the S-OFF threads, some devices just can't be S-OFFed at the moment.

But you should try both rumrunner, and firewater.... different exploits.

Good Luck
[One (M7) Q&A, Help & Troubleshooting] melted_cow:
Thank you so much. I just followed the guide and everything is back to normal. Now to send the phone back to HTC :crying:
[One (M7) Q&A, Help & Troubleshooting] randomA:
[MENTION=2605798]nkk71[/MENTION]

Hi,

able to help me again with my endless htc one problems ?

feel free to move this post elsewhere if you want.

but this time the problem is that

twrp bootloops

and cwm (that doesnt bootloop) is unable to install rom zips.

my getvar

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4320mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s

ever heard of this first issue that i had ?

E:error in /data/media/0/4.20.707.6_stock_odexed.zip
(Status 0)
Installation aborted.

however, then i tried a new attempt, and a new error came up:

set_metadata_recursive: some changes failed
E:Error in /data/media/0/4.20.707.6_stock_odexed.zip
(Status 7)
Installation aborted.

jeez there's no end to this. obviously the rom version is the same , so then why isn't it installing it?!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Not really related to the thread ;) but anyway

"set_metadata_recursive: some changes failed" is because you're using a recovery not suited for 4.4 ROMs (selinux support), so:

get TWRP from:

2.6.3.3: http://techerrata.com/browse/twrp2/m7

or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul

(make sure MD5 is correct, that site does not play nice with download managers)

2.7.0.4b: http://xdaforums.com/showthread.php?t=2708134

in bootloader/FASTBOOT USB:

fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img

fastboot erase cache

fastboot reboot-bootloader

-> enter RECOVERY and flash away

make sure to verify MD5 on

all

your downloads!! a corrupt download will have you wasting endless hours over nothing!!

.

PS: I can't move posts, only Moderators can do that.
[One (M7) Q&A, Help & Troubleshooting] randomA:
as mentioned previously, the phone bootloops continuously when i try to load in recovery and the recovery is TWRP.

I tried all the versions of TWRP that you linked and they all have the same effect.

From bootloader -> Recovery -> phone restarts, shows TWRP logo -> then reboots and goes to HTC logo and does the boot loop.

For some reason it goes into recovery only if i use a CWM.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
hmm, if MD5 is okay, and you did the erase cache, then no reason TWRP shouldnt boot up... did you recently flash something not for your phone? (such as a Sprint ROM?)

can you open a thread in Q&A or use this one: http://xdaforums.com/showthread.php?t=2732256

we're likely going to format your partitions, same as the guy in that thread.

post your getvar, and status of your phone (any working ROM?), and what you flashed to end up in this situation. mention me there and i'll post back.
[One (M7) Q&A, Help & Troubleshooting] dlshad:
Hi

i created un USB flash but when i paste last code show me this :

E: Unable to locate package android-tools-adb

E: Unable to locate package android-tools-fastboot

what i have to do please

thank you in advance
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Hi

1- can you please edit above post and remove the quote, thanks

2- do you have a working internet connection on Ubuntu? (which version are you running?)

and you did:

sudo add-apt-repository ppa:nilarimogard/webupd8

sudo apt-get update

and they were successful? sometimes you have to wait a bit, and do sudo apt-get update for it to succeed.
[One (M7) Q&A, Help & Troubleshooting] dlshad:
DISTRIB_RELEASE=14.04

DISTRIB_CODENAME=trusty

DISTRIB_DESCRIPTION="Ubuntu 14.04 LTS"

Intenet working first and secound command working but last one:

sudo apt-get install android-tools-adb android-tools-fastboot

got me Error

thank you 4 fast respond
[One (M7) Q&A, Help & Troubleshooting] nkk71:
guess it changed from 12.04 to 14.04, a quick google gave me this: http://www.ubuntuupdates.org/package/core/trusty/universe/base/android-tools-adb

check if that works, otherwise google for it for 14.04
[One (M7) Q&A, Help & Troubleshooting] silk_nz:
Further to my questions in another thread:

Yes, I am.

OK. I already HAVE the hboot 1.56 installed by mistake. I had gone through all the OTA updates. But i did manage to s-off it.

OK, I think i understand. Will downgrading to a 1.xx ROM also therefore downgrade the hboot ? I have only been able to find a nandroid of the __039 cidnum.

But I am told that http://www.htc1guru.com/dld/guru_reset_m7_2-24-980-2-zip/ is indeed the firmware I need. Anyone confirm? I did install it as my first run at this project, but I let it do the OTA's and I now have the 1.56 hboot - and the problem with TAMPERED flags when going s-on (for warranty).

So, if I do as you suggest just above, and let it do ONE OTA, the hboot will be 1.44? Or do I have to flash 1.44 manually at that stage to avoid the tampered detection of 1.56?

Sorry if I am being awkward; I am trying very hard to avoid some of the pitfalls others have fallen into. I just need that clarification :)

Thanks very much.

Here it is:

C:\mini-sdk-1.0.31-windows>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.56.0000

(bootloader) version-baseband: 4A.23.3263.28

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.20.980.1

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: XXXXXXXXXXXXXX

(bootloader) imei: xxxxxxxxxxxxxxx

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0714000

(bootloader) cidnum: HTC__039

(bootloader) battery-status: good

(bootloader) battery-voltage: 4295mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-09ff2ded

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.072s
[One (M7) Q&A, Help & Troubleshooting] nkk71:
No problem always better to ask first :)

First of all downgrading a ROM, will not downgrade your firmware, and if you downgrade to a 1.xx ROM with 2.xx+ firmware your touchscreen will not work. That's why the first thing is to use an ruu.zip to downgrade everything and work your way up.

If you want to use the CWM method, then use this cwm nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__039-1-29-980-2-2013-05-11-zip/

There are sometimes shortcuts (though I recommend against them) but the "Guru Reset M7 2.24.980.2" will only restore ROM and stock recovery (the rest of the firmware, such as hboot is not in there).

So if you wanted to use the Guru Reset method, you still need to find the 2.24.980.2 firmware.zip (included in the OTA), which I can't locate. (do you have a link to it?)

Still, I recommend you follow the CWM method using the above mentioned nandroid, and a 1.29.xxx.x stock recovery (or even the 2.24.980.2 stock recovery, inside the Guru Reset ROM.

I know it'll take a bit longer than just simply using the Guru Reset ROM, but in my opinion it's safer.
[One (M7) Q&A, Help & Troubleshooting] B3NJY:
Sober now

Thanks for a great guide mate...sober now but finished returning to stock thanks to you...now to celebrate with a tinnie...or 3 :laugh:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Well if all is done, i guess a few beers couldn't hurt :p

Don't drink and drive though!!!, and a "few" as in one or two, don't over-celebrate ;)

Enjoy :angel:
[One (M7) Q&A, Help & Troubleshooting] silk_nz:
Ahh, good point - would like the touch screen to work....

Thanks, think I'll do it your way.

I only have this one - I dont know if it has the hboot. I need the older hboot re the tampered flag.

http://www.htc1guru.com/dld/guru_reset_m7_2-24-980-2-zip/

I think I'll do what you recommend. I hope the nandroid comes with the earlier hboot?;)

Thanks again. (xda limits me to 8 thanks buttons a day..........).
[One (M7) Q&A, Help & Troubleshooting] nkk71:
That's only the ROM, recovery and radio. hboot and the rest of the firmware isn't in there.

the nandroid also only includes the ROM, that's why the first step in the guide is to flash a ruu.zip (even if it's not the same as your CID)... that will downgrade EVERYTHING to 1.xx, so you can use the 1.xx nandroid to restore your system.

However, since nandroid doesn't contain the firmware (hboot, recovery, bootsplash, etc), that is why you need to take an OTA update.... the OTA update includes a "firmware.zip", which will put the correct firmware for your CID, and then you'll be 100% stock.

Hope that makes sense now :)
[One (M7) Q&A, Help & Troubleshooting] silk_nz:
Ahh yes indeed it does! I did wonder where the older hboot was going to come from. :fingers-crossed: :good:

So, the ruu - even if not the right cid (we change it to make it work then change it back again) restores to version 1.xxx os, THEN the nandroid puts the rest in for my CID (since I can't find a ruu for my CID), and the first OTA gives me the hboot I want.

Then I get rid of all my activity including the tampered and unlocked flags, then s-on, then I do a factory reset and take the remaining OTAs. Which should work and behave...

Thanks for all your help!! I could easily have been trapped by hboot 1.56 trouble if not, I think. :laugh:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Yes almost,

step 1

: ruu.zip (CID doesn't matter only MID) -> result everything is downgraded and installed (including hboot, recovery, bootsplash, touchscreen, rom, and everything else you can think of), but not for your CID

step 2 & 3

: restore nandroid -> result only your ROM will get restored (but this time the correct one for your CID)

step 3b

: restore the preloaded apps -> those get deleted when you unlock bootloader, but are necessary to receive OTA

step 4

: install a stock recovery (close to your version 1.29.xxx.x) -> you need a stock recovery, for the OTA installation to work, since it's not exactly your version, it may hang at some point and you have to force reboot for it to continue it's thing (but be patient, don't confuse a slow progress to stuck)

step 5

: get rid of tampered and set locked -> why? because only hboot 1.44 will allow "fastboot

boot

CWM.img", and since we already have a stock recovery in place (from step 4), we don't want to change it!!

step 6

: successfully receive 1st OTA (either a 1.xx or a 2.xx) -> once the OTA installs correctly you can be sure you are now 100% stock (otherwise OTA would fail), and the OTA will contain your "firmware.zip" (including your stock recovery)

OTA 1.xx will contain hboot 1.44 and OTA 2.xx will contain hboot 1.54, both are safe to go from S-Off to S-On

step 7

: reset you phone, to get rid of any junk left on the phone

step 8

(though not recommended): go S-On on hboot 1.44 or hboot 1.54

and then you can continue receiving other OTAs if you wish.