yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Yep, i see what you're going through :eek::eek:

Well I think probable best to keep MID as is, since it's consistent with USA models, but change CID to ATT

fastboot oem writecid CWS__001

fastboot reboot-bootloader

and then use the AT&T ruu: http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/

the other alternative would be to change MID to PN0710000 + CID HTC__001 and run the international RUU.

What do you think?

As for S-On, the one thing I'm slightly concerned about, is if they send you the same phone back (just repaired), then there is a small possibility that HTCdev unlock may not work; it may be only a very small chance of not working, but who knows.... the ones that haven't been able to unlock again were people with S-On + SuperCID or S-On + GOOGL001 cid.
[One (M7) Q&A, Help & Troubleshooting] dray:
I don't know what to do...now I'm leary of S-On...If I had a better idea of the repair process, it would help. Do they actually open it up, repair the camera and re-ship it? or do they send me a different device? I don't want to have a stock device from now on. That would blow big time.

If anything changing the MID would make more sense as I would get updates faster through HTC than At&t so long as RUU is for M7-UL (LTE):confused:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Can't really say about the repair process much, as i've read many different outcomes, but most agree that the S-On part is strictly optional, as they cannot prove that you did the S-Off, some (okay very rarely, but some) do actually come S-Off by mistake and it doesnt void warranty, eg: https://twitter.com/htc/status/377422743626842112

I think, in the US it's customary for them to ship you either a new phone or a refurbished one; other countries actually repair the same device. It's really very country specific (and repair centre specific), i've seen plenty of posts (particularly UK), where they shipped the phone unlocked, rooted, custom rom, s-off, and got it back exactly the same way.

on the other hand, some other places complain about S-Off, until you yell at them long enough :p

Hmm, just a thought came to mind: why not give it a try, change CID to AT&T (as posted above) then request a new unlock token from HTCdev and see if works. (the bootloader unlock)... if it works out fine, then I would say that's the safest way to go.

Makes sense to you too?

EDIT: but run the RUU first, so everything is downgraded to 1.xx
[One (M7) Q&A, Help & Troubleshooting] clsA:
I would suggest the conversion to Developer Edition and take the OTA

updates. And stay s-off, I think the developer phones get less hassle from HTC because you are a developer.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
interesting idea, could be one way to go.

but he would have to ship it in UNLOCKED right? cause Dev Edition comes unlocked by default, if i'm not mistaken
[One (M7) Q&A, Help & Troubleshooting] clsA:
To be honest, I think when they see it's developer edition they ignore everything else ... I think they are so busy changing cameras they don't really care at this point
[One (M7) Q&A, Help & Troubleshooting] dray:
Won't they know by SN and IMEI of what it was originally and deem the warranty void? Dev edition is 64gb mine is a 32gb or am I being paranoid? Lol
[One (M7) Q&A, Help & Troubleshooting] clsA:
I think your over thinking it .. your phone shipped unlocked that's the main thing. if your camera is bad they have been replacing them.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
I don't think they bother tracking s/n and IMEIs, that would be a ridiculous process/hassle to go through, especially when they know it's a hardware problem.

I could understand complaining about obvious things, such as UNLOCKED and TAMPERED, but beyond that, I don't think it's worth the hassle.

Personally (yep me personally), would just try converting to AT&T (changing CID), run RUU, and while still S-Off check if the HTCdev unlock code works.
[One (M7) Q&A, Help & Troubleshooting] dray:
My phone is Sim unlocked. Not sure if that's what you are referring to.

---------- Post added at 10:41 AM ---------- Previous post was at 10:39 AM ----------

My phone is Sim unlocked if that's what you are referring to
[One (M7) Q&A, Help & Troubleshooting] nkk71:
no was referring to bootloader unlock, how did you unlock in the first place? as in the bootloader saying UNLOCKED
[One (M7) Q&A, Help & Troubleshooting] dray:
My phone is Sim unlocked. Sorry XDA app acting nuts
[One (M7) Q&A, Help & Troubleshooting] clsA:
well good luck with which ever path you decide to take Ruu to AT&T or Guru reset to DE ... I have done both it's not hard
[One (M7) Q&A, Help & Troubleshooting] dray:
Yes i unlocked it through HTC Dev site with token. I remember that being a cumbersome process. Sorry for the confusion
[One (M7) Q&A, Help & Troubleshooting] nkk71:
well then just go for it:

fastboot oem writecid CWS__001 <- two underscores

fastboot reboot-bootloader

run: http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/

don't bother with OTA's !!!, just go back to HTCdev get a new unlock tocken, and if bootloader unlocks, then everything is fine.

in order to avoid having to start from square one, you can just use the

fastboot boot CWM.img

and then use the commands from here: http://xdaforums.com/showthread.php?t=2475914

to set back to LOCKED.
[One (M7) Q&A, Help & Troubleshooting] dray:
Yes I unlocked the bootloader through the HTC dev site. I thinkI am going to do what you suggested...ATT RUU Change CID to CWS__001 I just don't remember the whole Dev site bootloader unlock process. Will research it. Geez this becoming an ordeal...lol

Thanks again for your support
[One (M7) Q&A, Help & Troubleshooting] nkk71:
it wasnt that bad, here's a quick guide: http://www.theandroidsoul.com/htc-one-m7-bootloader-unlock-guide/ (plenty of others around too),

basically, involves you log into HTCdev,

http://www.htcdev.com/bootloader/ -> All Other Supported Models

fastboot oem get_identifier_token

copy/paste the code, you'll get an email with "Unlock_code.bin"

fastboot flash unlocktoken Unlock_code.bin

screen should come up:

done.
[One (M7) Q&A, Help & Troubleshooting] dray:
Cool I can do it from my phone? Geez I did it the hard way

So i tried to update using the RUU you suggested and it failed....***error 155***

Its says its the wrong Rom utility :(
[One (M7) Q&A, Help & Troubleshooting] nkk71:
1- you'll need a pc for the fastboot commands (and HTCdev website) to work.

2- what do you mean RUU failed with 155? that usually only happens if (a) you're on hboot 1.55+ or (b) S-On with an unlocked bootloader

---> you're s-off, with correct MID (PN0712000) and CID (CWS__001) correct?
[One (M7) Q&A, Help & Troubleshooting] dray:
Yes it's on the picture too...:mad:

***update***

I just tried running it again and now after verifying my phone it says: Verify that you want to update the ROM

from IMAGE VERSION 1.29.401.12 to IMAGE VERSION 1.26.502.15

when I tried it earlier, the FROM VERSION was different, it read something like 4.06.1540.2

WTH
[One (M7) Q&A, Help & Troubleshooting] nkk71:
which picture?
[One (M7) Q&A, Help & Troubleshooting] dray:
The picture i posted earlier in the thread...in bootloader mode. See my update comment above ^^

---------- Post added at 01:24 PM ---------- Previous post was at 01:15 PM ----------

here is my latest getvar all...

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4T.21.3218.21

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.29.401.12

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

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0712000

(bootloader) cidnum: CWS__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4256mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too many links))

finished. total time: 0.687s

looks like my version mysteriously changed.. I did not complete the flashing process...WTH? :confused: :confused:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
okay, let's relax a little, take it easy :angel:

1- "from IMAGE VERSION 1.29.401.12 to IMAGE VERSION 1.26.502.15" -> that's because you downgraded hboot to the one i linked, no problem.

2- "FROM VERSION was different, it read something like 4.3.502.15" is it something "like" or was that the actual one? cause the .502. in it implies your old version was ATT!!! not .401.

3- now the real question, is how did you get the 4.3.502.15 ??? or 4.x3.502.x ???
[One (M7) Q&A, Help & Troubleshooting] dray:
Sorry I'm annoyed but not at you! You've been awesome!

I have updated my post since you viewed it...it showed what's in my sig under FW...4.06.1540.2

Currently the version shows as 1.29.401.12 and I found a OTA zip if that helps any here: http://xdaforums.com/showthread.php?p=39588860

Not sure if this matters but I have been running the GPE ARHD DEV ROM and that maybe why it is all screwy. I'm a little lost at this point.

:o :o
[One (M7) Q&A, Help & Troubleshooting] nkk71:
but your phone was Sense in the beginning right? (not GPE),

go ahead an run RUU.EXE you are using Win7 (maybe 8) but NOT 8.1? and both adb & fastboot working correctly.

you're still "(bootloader) version-misc: PVT SHIP S-OFF" so no worries.
[One (M7) Q&A, Help & Troubleshooting] dray:
Correct it was sense out of the box. So try re-running the RUU I just ran? I'm using Win 7 vmware off a MAC...fastboot for some reason gets stuck everytime I issue a command....I've read where that is an HBOOT 1.44 bug but it works
[One (M7) Q&A, Help & Troubleshooting] nkk71:
you could have said so from the beginning; ie that you're on mac!

are fastboot & adb working on mac properly (native)? (without vmware)
[One (M7) Q&A, Help & Troubleshooting] dray:
lol yes...but the fastboot commands are buggy too (HBOOT 1.44)

Just tried it again and it failed same thing error 155
[One (M7) Q&A, Help & Troubleshooting] nkk71:
get fastboot & adb working on your mac natively, then use this:

http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-12-zip/

rename it to ruu.zip, then:

fastboot oem rebootRUU

fastboot flash zip ruu.zip

fastboot flash zip ruu.zip <- yes TWICE, make sure it reports success

fastboot reboot-bootloader
[One (M7) Q&A, Help & Troubleshooting] nkk71:
let's pick this up tomorrow if you don't mind, here's a few downloads in the meantime:

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

http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/

http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/

or if you get vm back online: http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/

see u...
[One (M7) Q&A, Help & Troubleshooting] hmgan:
nkk71, i have a lil prob here...i am following your step to go back to stock. done s-off. but i have prob downgrade my hboot to 1.44

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU

...

(bootloader) Start Verify: 0

OKAY [ 0.050s]

finished. total time: 0.054s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip 1.29.401.12_hboot_1.44.zip

target reported max download size of 1526722560 bytes

error: cannot load '1.29.401.12_hboot_1.44.zip': No error

below is my getvar all

(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.63.707.3

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

(bootloader) serialno: FA35WW9*****

(bootloader) imei: 3558590502*****

(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: 3865mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-ea0bccbd

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.080s

what should i do next?
[One (M7) Q&A, Help & Troubleshooting] Dynomutt:
damn i just downgraded to 1.44 anyway I can get back to 1.54??

thanks for the help
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
I think you can restore the using: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-vodap102-1-29-161-7-7z/

and continue from OP's post quoted above

---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------

This backup will match 1.44 HBOOT, do follow the restore process accurately.
[One (M7) Q&A, Help & Troubleshooting] Dynomutt:
OK many more thanks, i used this from your OP and now have the red text on the HTC screen

in bootloader/FASTBOOT USB, flash it:

fastboot oem rebootRUU

fastboot flash zip 1.29.401.12_hboot_1.44.zip

fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”

fastboot reboot-bootloader

--> and confirm hboot is now 1.44

can I still lock the bootloader without brick in order to take OTA once im back to stock??
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
Yes but first restore and get on the VODA nandroid. Once it is restored, you can verify things are working on the device, then relock the bootloader and wait for OTA..
[One (M7) Q&A, Help & Troubleshooting] Dynomutt:
thanks again but the nandoid backup you linked to is not a .zip file
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
Download 7-zip.. that will work to unzip. I am sure you could have found out .7z extension by a quick google search..
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Hi [MENTION=3525160]SaHiLzZ[/MENTION], thanks for the assist :)

[MENTION=4228421]Dynomutt[/MENTION], please read posts 1 and 4 completely and carefully, the steps are NOT OPTIONAL, they have to be done all, and in sequence,

except the S-On part

, that's your decision.
[One (M7) Q&A, Help & Troubleshooting] vegetaleb:
So if I use your guide it should remove the developer red warning too?

I still don't have a One but I am afraid to get purple tint in camera so I document myself before jumping in :D
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yes, the guide will put you "out of the box" again, no warnings or anything, but make sure an RUU or nandroid is available for your version; and once you unlock, first thing to do a nandroid backup.
[One (M7) Q&A, Help & Troubleshooting] vegetaleb:
I see you are in Beirut,did you take the Gomobile One version?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Got mine from London :)
[One (M7) Q&A, Help & Troubleshooting] TonyTheTaiga:
Can i use method two on a mac?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
you mean ruu.zip method -> yes you can :)

only s-on if you absolutely insist and only do it before hboot 1.55!!
[One (M7) Q&A, Help & Troubleshooting] BuT_TeR:
(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.18.3263.15

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.29.401.12

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

(bootloader) serialno: xxxxxxxxxxxx

(bootloader) imei: xxxxxxxxxxxxxxxxxx

(bootloader) meid: xxxxxxxxxxxxxxxxxx

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0713000

(bootloader) cidnum: T-MOB010

(bootloader) battery-status: good

(bootloader) battery-voltage: 3846mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too many links))

finished. total time: 0.079s
[One (M7) Q&A, Help & Troubleshooting] nkk71:
(bootloader) modelid: PN0713000

(bootloader) cidnum: T-MOB010

are those the original ones, or did you change them?

edit: if yes, download and run this: http://www.htc1guru.com/dld/ruu_m7_...0-20_10-40-1150-04_release_324846_signed-exe/
[One (M7) Q&A, Help & Troubleshooting] BuT_TeR:
those are the original ones

Will it be okay if i flash latest 4.3 Update Ruu ?

PS: flashing what will change my hboot ?

1. recovery

2.firmware

3.rom

??
[One (M7) Q&A, Help & Troubleshooting] nkk71:
use this: http://www.htc1guru.com/dld/ruu_m7_...0-20_10-40-1150-04_release_324846_signed-exe/

follow steps in my guide:

1- LOCK, no TAMPERED

2- run the above RUU <- this will reset & wipe everything to 100% stock

3- if you wish take the 1st OTA (so you are convinced everything is good), and only the 1st, if you have the intention of going s-on

4- if you decide to go s-on, you MUST do it before 4.3 (hboot 1.55)

hboot 1.55: when you go from s-off to s-on, on hboot 1.55 after one or two reboots, it will come back with "tamper detected - rebooting", and then TAMPERED is back!!!!!
[One (M7) Q&A, Help & Troubleshooting] BuT_TeR:
so i need to lock bootloader and remove tamper before flashing ruu?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yes, better to do that first cause you need custom recovery, please follow the steps in the guide; I put them

in that order for a purpose

:)

s-on is strictly optional, but if you do want to do it, you HAVE TO DO IT BEFORE HBOOT 1.55.
[One (M7) Q&A, Help & Troubleshooting] nokevin:
How do I get this ???

Thanks
[One (M7) Q&A, Help & Troubleshooting] nkk71:
"cannot load", just means the filename is wrong
[One (M7) Q&A, Help & Troubleshooting] hmgan:
thanks nkk71, that was dumb of me not putting the file in the folder. now, i've got this :

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip 1.29.401.12_hboot_1.44.zip

target reported max download size of 1526722560 bytes

sending 'zip' (501 KB)...

OKAY [ 0.261s]

writing 'zip'...

(bootloader) zip header checking...

(bootloader) zip info parsing...

(bootloader) checking model ID...

(bootloader) checking custom ID...

FAILED (remote: 42 custom id check fail)

finished. total time: 0.768s
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
Your CID:

(bootloader) cidnum: HTC__044

Supported CIDs from 1.44HBoot you are trying to flash

cidnum: 11111111

cidnum: T-MOB010

cidnum: CWS__001

cidnum: BS_US001

cidnum: GOOGL001

cidnum: HTC__001

cidnum: HTC__E11cidnum: HTC__102

cidnum: HTC__203

cidnum: HTC__405

cidnum: HTC__Y13

cidnum: HTC__304

cidnum: HTC__032

cidnum: HTC__A07

cidnum: HTC__J15

cidnum: HTC__016

Either match your CID to the list above (fastboot oem writecid XXXXXXXX), or add your CID to android-info.txt (probably not a good idea)
[One (M7) Q&A, Help & Troubleshooting] hmgan:
How bout using the original stock hboot I found somewhere? How come is not a good idea to add CID to the file?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
just temporarily change CID, only takes a second:

fastboot oem writecid HTC__001 <--- two underscores

fastboot reboot-bootloader

fastboot oem rebootRUU

fastboot flash zip 1.29.401.12_hboot_1.44.zip

fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”

fastboot reboot-bootloader

fastboot oem writecid HTC__044 <--- two underscores (back to original)

fastboot reboot-bootloader
[One (M7) Q&A, Help & Troubleshooting] LibertyMarine:
[MENTION=2605798]nkk71[/MENTION] You wrote in your guide that you have to be S-OFF to use an RUU. Does this mean that I can flash a RUU zip even with a locked bootloader as long as I am s off?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
here's my conclusion (so far) on that subject:

* (re)locked bootloader (S-On or S-Off) = you cannot flash anything using normal fastboot commands, eg "fastboot flash recovery ..." it will fail (remote not allowed)

* bootloader (re)locked AND S-On = you can only flash a signed firmware.zip or ruu.zip in fastboot oem rebootRUU mode, with same or higher version

* bootloader (re)locked AND S-Off = you can only flash any firmware.zip (whatever it contains) or ruu.zip in fastboot oem rebootRUU mode, eg: http://xdaforums.com/showthread.php?t=2624227 (only contained TWRP recovery, but masquerading as a firmware.zip)

(you can easily create your own package, and put whatever you like in it; don't mess with hboot)

you have to be S-Off if any of the following are involved:

* downgrade

* unsigned firmware

* unsigned ruu.zip

hope that answers your question.
[One (M7) Q&A, Help & Troubleshooting] LibertyMarine:
thanks!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
[MENTION=5458228]LibertyMarine[/MENTION], I've made a small chart:

what's worth noting, is that

with S-Off you do not need to lock/relock bootloader

to be able to flash in "fastboot oem rebootRUU" mode (or RUU.EXE); this is still a small misconception some users have due some of the pre-S-Off days guides, where locking/relocking bootloader was required (due to S-On) in order to update firmware or run an ruu.

PS: the above chart obviously assumes that CID and MID match "android-info.txt"
[One (M7) Q&A, Help & Troubleshooting] LibertyMarine:
oh my f*cking god... thanks! You are awesome! Just wow.. thanks! awesome !
[One (M7) Q&A, Help & Troubleshooting] nkk71:
no problem, i'll update the chart to include some more stuff when i have some more time :cowboy:
[One (M7) Q&A, Help & Troubleshooting] LibertyMarine:
ok, this is awesome. thanks! already the idea of this chart is very good!
[One (M7) Q&A, Help & Troubleshooting] hmgan:
Thanks so much nkk71!! U r the best!! Now I'm s-off n on hboot 1.44, I'm gonna b back to stock very soon.*

Before I proceed to next step, can I use twrp to install the guru bootloader to remove my tampered instead of cwm mentioned? Sorry for the silly question but I just wanna be safe than sorry.*

Once I flash RUU, recovery will be back to stock or still twrp?*
[One (M7) Q&A, Help & Troubleshooting] alray:
refer to here for recovery compatibility with guru bootloader reset

After you flashed the ruu, you'll have stock recovery
[One (M7) Q&A, Help & Troubleshooting] nkk71:
as [MENTION=4654136]alray[/MENTION] mentioned, you will need TWRP 2.6.3.3+ it seems older versions of TWRP had the partition write-protected: http://xdaforums.com/showpost.php?p=47484899&postcount=9

since it looks like you're going to use a ruu.zip, then you can go ahead with TWRP 2.6.3.3+ and make sure the changes (untampered and locked) are applied successfully; if you have problems with adb in "fastboot boot recovery.img" you can even "fastboot flash recovery <name of recovery>.img" (in

your case

, as you will be using ruu.zip later on).

or you can use the CWM I suggested in post #7, because other versions sometimes have problems with adb commands in "fastboot boot recovery.img".

Once you have confirmed: no TAMPERED and LOCKED status in bootloader, go ahead and flash ruu.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

after the Successful ruu.zip, your phone (everything) will be wiped and "out of the box"

I recommend staying S-Off, but if you really need to go S-On, do so

before

taking any OTA to 3.xx.

BTW: which ruu.zip are you using?