yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] kevindiehl:
I tried flashing 2.17 then 3.06 (both without hboot), but 3.06 still fails.

I also tried 2.17->2.24->3.06 (all without hboot), but 3.06 still fails:

(bootloader) ...... Successful
FAILED (remote: 51 partition update fail)
finished. total time: 48.722s

I think it is related to "pg2fs_spcustom.img" failing to flash:

(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,22
(bootloader) [RUU]UZ,pg2fs_spcustom,41
(bootloader) [RUU]UZ,pg2fs_spcustom,70
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Failed

What is "pg2fs_spcustom.img" for? Did anyone else have issues flashing it?

---------- Post added at 09:29 PM ---------- Previous post was at 09:16 PM ----------

I deleted "pg2fs_spcustom.img" out of 3.06 and was able to flash without it.

Maybe pg2fs_spcustom.img requires hboot 1.54 to flash correctly?

I am still on hboot 1.44 since I heard revone does not work with 1.54 yet.

Did everyone else just flash 1.54 anyway?
[One (M7) Android Development] descenpet:
alot of people have problem with other parts of 3.06 firmware when they try to use it without the hboot. you don't really need to care so much about revone when you are already s-off. if you need to use it to re"locked", you can downgrade everything anytime.
[One (M7) Android Development] Clselfridge:
Ok. Just wondering here... But why are you guys trying to flash this firmware without hboot? It you have s-off already then the hboot isn't stopping you from getting it... Maybe there is something I am missing but the only real reason I can see to flash the 3.06 firmware is to get the radio(witch you can flash separately) and the black hboot. Which you won't get if you remove the hboot... So yeah not sure I understand why it's even being discussed.

Sent from Tapatalk
[One (M7) Android Development] descenpet:
i don't understand it either. my guess is they are too paranoid of losing the ability to use revone for some reason. maybe because a few people(2?) claimed they lost s-off for some reason. the first one said it happens while updating firmware/hboot but i doubt so. didn't hear more from him since then. the 2nd one claim something similar but after some long conversation, it turns out that he himself issued fastboot oem writesecureflag 3, without knowing what it does, just because someone else told him to. we could assume first case could be the same?. :rolleyes:
[One (M7) Android Development] Clselfridge:
Yeah I got s-off and have gone up to 2.24 and then ran a ruu back to AT&T stock and then took an ota to the latest AT&T firmware. Then I went to 3.06. And I haven't lost s-off. I plan on flashing through the firm wares again now though because my touch doesn't seem up to what it was with 2.24. But since it is possible to restore backwards with s-off I don't get the not wanting to update the hboot thing...

Sent from Tapatalk
[One (M7) Android Development] descenpet:
if you went back to stock 4.1.2 and upgrade the firmware straight to 3.06 then ya you will be with old touch firmware. :p

unless you use a mixed version with 2.24 touch firmware mixed in that is.
[One (M7) Android Development] Clselfridge:
Well the latest update from AT&T which is 1.26.502.15 was said to have some sort of touch driver update(obviously not the same ones since touch still works on 4.1.2) but running a 4.2.2 rom it doesn't feel as nice. So I am planning on running a combo update(posted in another thread...) now to go from the 1.26(well actually 3.06) and get all the goodies that are missing from 2.17/2.24 and keep the beautiful black hboot and little unlocked symbol from 3.06. Unless it is recommended to not use a combo zip and to run them all individually. Which seems like a real pain in the *ss...lol

Sent from Tapatalk
[One (M7) Android Development] vomer:
I am thinking incompatibilities cause the issue somehow. In any case, yes, once you are s-off hboot versions hardly matter.
[One (M7) Android Development] Eschmacher:
I just picked up my One yesterday and unlocked the bootloader.

When I run the ./revone -P command I get "...Segmentation fault (core dumped)"

Any ideas? I've rebooted the device multiple times, verified the revone file is set to 755...
[One (M7) Android Development] Newcron:
Did you check your hboot version? It is possible that the latest batches are shipped out with hboot 1.54 already.
[One (M7) Android Development] Eschmacher:
1.44, just double checked.
[One (M7) Android Development] descenpet:
if you are on latest tmobile ota, you can't use revone or so i heard.
[One (M7) Android Development] Eschmacher:
That would explain it...
[One (M7) Android Development] deeevan:
LOL tried to quote from thread in another and ended up posting here
[One (M7) Android Development] nKiwan:
Thanks for the guide.

S-OFF'd, SuperCID'd and updated my firmware to 2.24.401.1. :cool:
[One (M7) Android Development] wastedsunsets:
Nice informative thread. But i have a major issue here. After upgrading the firmware to include the latest touchpad drivers on my stock HTC One ROM, now my screen had stopped responding to the touches. When I'm booting into TWRP (recovery) through adb command mode, my touchscreen is working, but not once my phone boots up. Any idea where I might have gone wrong?
[One (M7) Android Development] descenpet:
because your rom is old. just flash a new rom and it will work.

if you still want to use old rom. downgrade your firmware.
[One (M7) Android Development] vomer:
You need to be on a 4.2.2 Rom because those new drivers are from that base.

Sent from my Nexus 7 (flo)
[One (M7) Android Development] fidoedidoe:
Using this excellent guide I've upgraded my firmware to version: 2.24.401, then 3.06.1700.10 (i got caught out by removing hboot from 3.06.1700.10, which failed - but seeing subsequent comment by vomer and other indicating that leaving hboot in the firmware will not compromise s-off i was quickly back on track - thank you!)

I do have one question (although not sure if this is best place here on in the ARHD thread?). Rebooting into ARHD 12.2 i now have a notification indicating that i need to "Install Super User, the su binary is out of date". Is it safe to simply update the su binary (i seem to recall seeing a post somewhere reporting issues - but that was a long time ago)?

hopefully not a noob question
[One (M7) Android Development] vomer:
Yup, just install the latest superuser from the play store - launch it and when it prompts for binaries - choose install :good:
[One (M7) Android Development] miketamm:
Same here. Backing out to oldest firmware in mentioned in post#1 of this thread still leaves me broken. Anyone have a link to the stock firmware.? TWRP touchscreen isn't working either so I can't load 4.2.2 rom.
[One (M7) Android Development] descenpet:
then your twrp is outdated. just get new twrp. no need to mess with firmwares.
[One (M7) Android Development] ChaosSystem:
Thanks. I managed to to perform this on a phone that was S-Off using HTC-Dev.

I had trouble changing the CID until I used Revone.
[One (M7) Android Development] rpmccormick:
I have been sticking with hboot 1.44 just because that seemed to be what everyone else wanted.

I do have S-OFF via revone, so I guess I can go ahead and update hboot? I already have a custom black hboot-screen (blue clockwork-android on black background) which I assume will be erased, but I assume I can custom-hboot again with the new one right? Is there any reason not to update if you are already S-OFF other than needing to re-flash my custom screen?

All I have is the radio flashed right now... no other FW updates, no OTAs. Is there anything I need to do the process for other than touchscreen? Also, my touchscreen works perfect always, so I'm not sure I want to update that.

PS: I won't brick with my custom hboot-screen since I DID NOT hex edit the hboot to remove the red-text... right?
[One (M7) Android Development] Clselfridge:
If I understand your talking about the splash screen right? You have a custom splash. Not a custom hboot? If that's what you mean then no you won't brick. As for updating the hboot you can do that. You won't lose s-off. You will lose the ability to use revone but with s-off you have the option to flash back to 1.44 if you needed to use revone for anything again. The touch drivers won't make your screen much different but will make the capacitive buttons much more responsive. But if you do run the 2.24 firmware update touch will not work on a 4.1.2 Rom. Hope this helps.
[One (M7) Android Development] Westnile:
Would this work on a one v I just want the s off its annoying? and some mods etc I want to use require it to be off
[One (M7) Android Development] kobezklutch:
hmm...

Got up to Step 6 (not very far at all) and this is what my command prompt looks like. Is there a new version of adb that I'm supposed to have or is my command prompt supposed to look like that? Sorry, I don't really know what I'm doing, just really want s-off so I can get rid of that tamper flag. Any help or advice is appreciated!
[One (M7) Android Development] vomer:
what hboot version? also is it a new t-mobile phone?
[One (M7) Android Development] BuT_TeR:
h boot version - 1.44 :eek:

can s- off?:rolleyes::rolleyes::confused::confused:
[One (M7) Android Development] descenpet:
yes, except if you are on latest at&t/tmobile.
[One (M7) Android Development] BuT_TeR:
latest t mobile?

i am on Cm 10.2 ,if thats what you mean
[One (M7) Android Development] xeyesofthousandx:
I'm not sure how it goes on CM10.2, but if you choose to update the T-Mobile One with the OTA for FW version 1.27.531.11, revone AND moonshine become useless, even if your hboot is still 1.44. I think they modified the 1.44 hboot in the OTA to block the S-Off exploits. I learned this the hard way today :mad: if you updated to .11, im afraid it's impossible right now. We'll just have to wait for revolutionary to find a S-Off method for .11, if they ever do...
[One (M7) Android Development] Bastaerd:
Nope, this is device specific.
[One (M7) Android Development] vomer:
Guide updated with latest firmware

2.24.401.8 :good:
[One (M7) Android Development] kazemitsui:
is there any sort of changelog for whats new in this compared to the last 2.24 and the 3.06

i havent updated my firmware yet
[One (M7) Android Development] vomer:
2.24 is based on 4.2.2 base - it has a new boot screen with no red warning text. Not much other new stuff I believe

Do not flash this one until you update to ARHD 13
[One (M7) Android Development] kazemitsui:
wth... 12.3 just out i swear last week friday or soemthing and now arhd13... haha wow
[One (M7) Android Development] vomer:
lol yup, new base = new ARHD version :D
[One (M7) Android Development] bl4ckdr4gon:
[MENTION=1363323]vomer[/MENTION]

Will 3.06 firmware still be ok when I finally get to try ARHD 13.0? Everything's working fine with 12.2. Planning to skip 12.3 since haven't had the chance to download it.

Or would you recommend I use the 2....8 firmware? Sorry as I do not understand so much of these stuff. Willing to learn though.
[One (M7) Android Development] vomer:
I would install the 2...8 firmware with v13

Sent from my Nexus 7
[One (M7) Android Development] bl4ckdr4gon:
Got it. So maybe I should, too. I just learned firmware thru adb here with your post. Thanks a lot bro. HTC's quite different from what I got used to with Sammies
[One (M7) Android Development] Jostian:
cant believe its taking Revone so long to sort out 1.54 h-boot, its been well over a month now...?
[One (M7) Android Development] xnknown:
why is yours 401 and the one in mikes thread 708, any diff?
[One (M7) Android Development] khriztianjs:
Hola, Good morning, thanks , but i have Arhd 12.3

And firmware 2.24.401.1

I have s off

1.54

I updgrade to 2...8 firmware with 12.3 or i have to flash Arhd 13.0 before that upgrade fir?

Sorry my English is not good :D

Gracias *

Enviado desde mi casa usando señales de humo :D
[One (M7) Android Development] Jostian:
I so badly want S-OFF but am on h-boot 1.54..... taking so long to get the firmware sorted for h-boot 1.54... sigh
[One (M7) Android Development] ZerockzZz:
the part with the firmware update worked perfectly, thank You!
[One (M7) Android Development] biohaz55:
You can flash the modified hboot but I advise you not to.

Flashing modified hboots is risky at the best of times..... if you try to go back to s-on or relock then you will brick your device. You will need to flash the original hboot if you want to go back.

In my opinion it's not worth the risk just to avoid the red text for a few seconds and if you don't boot that often you hardly see it anyway.
[One (M7) Android Development] pcusim:
I have a question: I have unlocked the bootloader with htcdev code, gained s-off with Revone, flashed Revolution HD 12.0 and flashed the new firmware. If I wanted to get back to stock do I need to flash the old 1.44 hboot before running a RUU or wil it be enough to run the RUU directly? I already know that s-on and relock are last things to do.

One more thing: where do I find the 1.44 firmware?
[One (M7) Android Development] rubino90:
One stupid question if i use this guide is possible return to HBoot 1.44 for return s-on and locked? with lastest hboot 1.54 revone command not works for return COMPLETELY stock many thanks for reply
[One (M7) Android Development] snowblind2142:
:good: :good: :good:

Thanks for the Great Guide, I have unlocked the boot loader and S-off'ed but I needed a bit more info as to updating the firmware.

Quick question, Im on O2.

I know I can return to my CID number, but wanted to confirm you cant roll back the Firmware, am I right?
[One (M7) Android Development] Wingzer:
What are the benefits of this firmware over older versions ?
[One (M7) Android Development] taha198:
Does this custom firmware checks and prevent installation based on model id?
[One (M7) Android Development] biohaz55:
With s-off you can return to your original state using the appropriate RUU for your region/carrier and this will also roll the firmware back.
[One (M7) Android Development] mojolive:
Well said, and great advice
[One (M7) Android Development] biohaz55:
The latest firmware from the 2.24 update includes a newer radio, new touchscreen drivers, plus other things. The update is worth it just for the improved touch but there is no need to update at this time unless you want to.

Because of the new touchscreen drivers if you choose to update the firmware you will need to flash the latest 2.24 based rom first otherwise touch won't work and you will need to update recovery to the latest CWM or TWRP, again for touch to work.

---------- Post added at 12:58 PM ---------- Previous post was at 12:50 PM ----------

Yes and no..... it's for modelid 071000 along with a small set of CID's.

However there are a couple of options.... in the firmware zip package check the android-info.txt file if your CID is there then you can edit the modelid to that of your device. Don't unzip the firmware package just open it with 7zip or similar, drag out the text file, edit it then drag it back in again and the flash away.

The other option is to change your CID to 11111111. This bypasses modelid checks and will allow to flash.

There are a couple of guides for flashing firmware in my signature below.
[One (M7) Android Development] vomer:
+100 to what he said^. Too risky and no added benefit.

UPDATE: Hboot 1.54 warning note added! thanks to [MENTION=2350273]rider5512[/MENTION] for the suggestion :)
[One (M7) Android Development] Jostian:
S-Off not working on HBoot 1.54... error code = -6 (everytime, tried about 6 times), a version that works with 1.54 would be great.
[One (M7) Android Development] vomer:
read my post right above yours. There is no S-OFF for 1.54 out yet.
[One (M7) Android Development] biohaz55:
LOL..... you're a few minutes early.... vomer has just updated the OP to add that s-off with hboot 1.54 can't be achieved at the moment. The revone team are working on it.
[One (M7) Android Development] vomer:
yup :) Once they have it released I can update the download link to latest version. Steps should remain the same :fingers-crossed:
[One (M7) Android Development] Jostian:
thanks, will keep an eye out for it.
[One (M7) Android Development] snowblind2142:
Ok, so im having problems...

So Im S-off, Ive changed CID to 11111111

Ive got as far as getting the silver HTC logo,

But then I got to fastboot flash zip C:\adb\firmware.zip

An it just says failed to flash....

Tried rebooting pc and phone, no joy, tried it from a different file (I originally was using it all in Android, tried ADB folder and followed to the step)

Still nothing. Any Ideas why its not flashing? doesn't seem to see the file to flash?

Am I missing something?

EDIT: maybe the firmware.zip has to be in another folder within ADB folder?

IE: C:\adb\randomfolderwithfirmare.zip

so firmware is separate to everything else?
[One (M7) Android Development] aulterra:
[MENTION=1363323]vomer[/MENTION]

Home ! Woo! Ok so just a few last questions, do I need to flash back to my stock rom? Or can I do this on the custom I'm using atm?
[One (M7) Android Development] vomer:
you need to do that step twice. Please read the guide... it already shows this.

you should be able to do it on your current ROM.
[One (M7) Android Development] snowblind2142:
Sorry vomer.

It wasn't clear in the guide, I must have read it 20 times now...

I read it that you did it a few times to get in to the Silver HTC screen..

Where as I got in to it first time.

I will try it again a few times and see how it goes.

Might want to make it clear in the guide, do it anyway, regardless if you get in to silver HTC logo or not.

Thank you for advising.

EDIT: still no joy, keeps saying the same as last time:

error: cannot load 'C:\adb\firmware.zip'
[One (M7) Android Development] Mikanoshi:
I'm interested in that too, will 12.3 work with the latest .8 firmware? Don't want to update ARHD until at least 13.3...

---------- Post added at 08:50 PM ---------- Previous post was at 08:01 PM ----------

Daaaaaammit, why he makes ROMs without mods first and then with mods, it's like beta ROMs :)
[One (M7) Android Development] vomer:
Flash firmware -> Install ARHD v13
[One (M7) Android Development] vomer:
No, 12.3 and new firmware do not work well together.
[One (M7) Android Development] Mikanoshi:
Flashed 3.06 fw with ARHD 12.3, working fine. Will wait for 13.3, CRT off anim was cool :silly:
[One (M7) Android Development] jaxtripp:
Anybody having issues with ADB after installing the latest firmware? When I issue "adb devices" nothing is listed. Fastboot works if I manually restart the phone into bootloader. I'm using Linux, so drivers aren't an issue. Can I revert to my old firmware without bricking? Any ideas?

UPDATE: After reverting back to GE firmware adb works again. Tried upgrading to 24...8 again and this time adb works. So not sure what happened.
[One (M7) Android Development] vomer:
adb is always iffy like that. I just do a restart when I have issues :good:
[One (M7) Android Development] jaxtripp:
Awesome, thank you.

One more question, can I remove hboot from the fw_2.24.401.1_custom.zip file? I'd like to keep the dark bootloader from the GE firmware if possible.
[One (M7) Android Development] nur.salikeen:
2.24.707 compatible to use ARHD 13.x?
[One (M7) Android Development] Jose Viegas:
How come this last firmware is less than 7mb while the others are all around 27mb?
[One (M7) Android Development] dark_polok:
Currently I'm at Hboot v1.44. I am planning to update my firmware from version 1.29.401.1. I see I can change the Hboot version on the latest firmwares to Hboot v1.44, by replacing the file of the latest firmwares. This means everything will update but the Hboot will remain the same version right? I think i got that part. But now, what benefits might I get by staying back with Hboot v1.44?

Thanks in advance.
[One (M7) Android Development] vomer:
Should be ok

Because the whole ROM update from HTC was only 37MB

If you follow my guide in the sequence it is presented - it will allow you to s-off while on 1.44. Once s-offed it does not matter if your hboot updates because you can always downgrade it.
[One (M7) Android Development] Mikanoshi:
65MB Radio.img inside :)
[One (M7) Android Development] demisb:
I used this guide some time ago, and i'm currently s-off, running ARHD 13.2. Bootloader 1.54, firmware 2.24.401.1

I downloaded 2.24.401.8, and tried to flash it in RUU mode, nut got a fail: error code 42, id check failed.

Tried a second time with the same result, any ideas?
[One (M7) Android Development] jaxtripp:
Great info, thank you!

If I remove the hboot image from fw_2.24.401.8_custom.zip, is it also nesesary to edit the android-info.txt to reflect the change? Or will it just skip the file if it's not present?

Sorry so many questions, just don't want to be sure before flashing.

Thanks again!!!
[One (M7) Android Development] dark_polok:
Trying to update to firmware 3.06.1700.10 (with the updated touch driver added into the .zip). This is what I get:

C:\adb>adb reboot bootloader

C:\adb>$ fastboot getvar all
'$' is not recognized as an internal or external command,
operable program or batch file.

C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.14.3250.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.29.401.17
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: [hidden on purpose]
INFOimei: [hidden on purpose]
INFOmeid: 00000000000000
INFOproduct: m7_u
INFOplatform: HBOOT-8064
INFOmodelid: PN0711000
INFOcidnum: HTC__J15
INFObattery-status: good
INFObattery-voltage: 3821mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s

C:\adb>fastboot reboot-bootloader
rebooting into bootloader... FAILED (status read failed (Unknown error))
finished. total time: 5.543s

C:\adb>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.041s]
finished. total time: 0.041s

C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28317 KB)... OKAY [ 2.910s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 3.396s

C:\adb>

Can someone please tell me what is going wrong and how to fix it?

UPDATE: I guess I figured it out. Mine's m7_u is that why? If that is the reason, is there any way I can still flash the latest firmware?

Thanks.
[One (M7) Android Development] descenpet:
why is the latest firmware uploaded with stock boot.img? i was wondering why alot of people who flashed firmware was having various issues on custom roms >.<
[One (M7) Android Development] vomer:
No need to edit that file :)

It was a mistake on my part - I fixed the issue and re-uploaded the zip with no boot.img :angel:

I would flash the original firmware then. 2.24.x then go to v3 if you like.
[One (M7) Android Development] Element515:
Thanks, very helpful