yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] silk_nz:
OK, it seems to have worked up to the 3.xxx update (which I am downloading now), the 2.xx update went through ok although I had to manually reset the phone several times to get it to continue... Thank you very much!!!

This is my current getvar all:

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

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.54.0000

(bootloader) version-baseband: 4A.17.3250.14

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.24.980.2

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

(bootloader) serialno: xxxxxxxx

(bootloader) imei: xxxxxxxxx

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

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-d16dc66985

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.065s

Hopefully now, I can get this purple camera problem fixed under warranty. Thanks again!:laugh::laugh:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
All should be good now, you won't need to manually reboot during the next OTA as your stock recovery has now been installed (thanks to the 2.xx OTA)

but edit your previous post and remove IMEI and s/n, IMEI should never be shared publicly
[One (M7) Q&A, Help & Troubleshooting] silk_nz:
Damn, that was foolish of me! Thanks! :o

Everything seems to be factory stock now inc updates. I hope my experience and your help is useful to someone else too. :fingers-crossed:
[One (M7) Q&A, Help & Troubleshooting] quicksilver53:
Hey nkk71 I hope that you can give me some direction on returning my Rogers m7 back to stock. I have lost my stock backup and am trying to run a nandroid backup that I got from htc1guru. I failed to do a backup after i installed twrp. My boot loader shows unlocked but not showing tampered at the moment. Here is my getvar

.

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.55.0000

(bootloader) version-baseband: 4T.21.3218.21

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.22.631.1

(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: ROGER001

(bootloader) battery-status: good

(bootloader) battery-voltage: 3957mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-fe1214

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

here is the nandroid backup from htc1guru,

M7 TWRP Nandroid Backup CID ROGER001 3.22.631.1

I have tried to follow crushalots instructions but I get lost. I just want to get it back to stock rom for waranty replacement. Thanks.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
That nandroid is no good, if you want to follow my guide, then you need to use CWM method, using 1.xx:

http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-roger001-1-29-631-4-2013-06-03-zip/

There is also: http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/ and also on androidruu: http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_351317_signed_2.exe

Though if you intend on going from S-Off to S-On, then I cannot guarantee that the infamous "tamper detected - rebooting", won't happen on the 4.4 ruu.... there is no "fool-proof" way to say it will or will not happen,

hence my guide takes you down to the earliest version possible (except 1.20) and works up from there.
[One (M7) Q&A, Help & Troubleshooting] quicksilver53:
Thanks for your reply. I downloaded that RUUexe but when I try to open or run as admin, my comp freezes. Can I run that cwm nandroid even though twrp is my recovery?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
No you cannot... TWRP and CWM (as far as i know), backups, are not identical.

I did write the guide in a very specific sequence, to avoid any potential problems... sometimes there are shortcuts, but if YOU decide to take shortcuts, please do so at your own discretion, and risk.
[One (M7) Q&A, Help & Troubleshooting] theplaypig:
EDITED: Wrong place to post... sorry
[One (M7) Q&A, Help & Troubleshooting] quicksilver53:
Thanks again. I have installed cwm so I will see if I have an easier time getting back to stock.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Good Luck, let me know if you have questions.

If you want a brief explanation of why the CWM method is so long, read this post: http://xdaforums.com/showpost.php?p=52430301&postcount=834

And there is a visual walk-through in post #8, so you can see what kind of output to expect.
[One (M7) Q&A, Help & Troubleshooting] Mihir1997:
INFOversion: 0.5
INFOversion-bootloader: 1.56.0000
INFOversion-baseband: 4A.23.3263.28
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.19.401.8
INFOversion-misc: PVT SHIP S-OFF
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: BS_US001
INFObattery-status: good
INFObattery-voltage: 4169mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-4dab9d12
INFOhbootpreupdate: 11
INFOgencheckpt: 0

I am on bell Canada. I need the appropriate files to restore to stock. Thanks.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
So Bell is:

modelid: PN0712000
cidnum: BM___001

so as discussed before, you'll need to use CWM restore method (post #1, #2, and #5); your MID is good, no need to change that, then:

using fastboot oem writecid BM___001 (in step 2) <- three underscores, CID is exactly 8 characters

using this CWM nandroid (in step 3): http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-bm___001-1-29-666-5-zip/

use this stock recovery (in step 4): https://www.dropbox.com/s/xlcf86fs68vtm20/recovery_1.29.666.17.img (MD5=9770DC1ED01D6B567BB13C2981E9C795)

Please make sure you're comfortable with the guide before proceeding (including the FAQs), and if you have any questions let me know before :)
[One (M7) Q&A, Help & Troubleshooting] Mihir1997:
The instructions under "CWM Nandroid" ask to flash RUU... I am assuming that is incorrect?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
No, it's not incorrect, it is

absolutely necessary

!! If it was a mistake I would have removed it a looong time ago.

If you need a brief explanation of why all these steps, check here: http://xdaforums.com/showpost.php?p=52430301&postcount=834

(as mentioned in the guide) you will need to use (for PN0712000):

fastboot oem writecid CWS__001 <- two underscores

fastboot reboot-bootloader

then flash this ruu.zip (twice): http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/

then change CID back to your original, and continue with the procedure.

You can also check post #8, which is a "Case in point: CWM method for MID: PN0712000 and CID: ROGER001" with visuals of what to expect.

I know the guide is quite long, (and it took even longer to write up), and is written in a

very specific sequence

to avoid any potential problems.

Please make sure you've read it thoroughly (including the FAQs), and let me know if you have any other questions.
[One (M7) Q&A, Help & Troubleshooting] Mihir1997:
Ok, I tried following the guide. Went to the letter.

THe nandroid was corrupted though, so touchscreen drivers weren't installed properly.

So This is what I did instead.

#1 Installed a Stock Sense Rom (ARHD's mike has some up)

#2 Flash stock recovery

#3 Change CID to BS_US001

#4 oem flashed ruu for Dev. Edition

#5 Locked bootloader using the fastboot boot cwm.img method you described in your guide

Now I am running stock Dev Edition 4.4 with Sense 5.5

Hope this helps everyone. If you need more details, let me know and I'll whip something up.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Well just out of curiosity i'm going to download that nandroid to see how "corrupt" it is.... and the nandroid didnt restore your touchscreen drivers?

how strange

, i thought that was the part the ruu was supposed to to do...hmm.

but since you feel/assume it's incorrect, kindly go to troll somewhere else. thank you.
[One (M7) Q&A, Help & Troubleshooting] Mihir1997:
You seem to have misunderstood.

I don't mean to troll. I was just really confused because the CWM nandroid method was asking for a RUU but you already addressed that concern of mine before. I did use the RUU, I was just trying to confirm that it was actually required and not a misplaced instruction.

Sorry for coming off as brash.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
I welcome questions, suggestions, criticism (preferably constructive), and any kind of information members want to share, but a little bit of research should always (and is sort of expected on xda) be done first.

So first off, if something was wrong or out of place, I think someone would have pointed in out by now.

Second, thouchscreen drivers are not part of a nandroid, that's one of the reasons why you need to ruu a 1.xx version first; the ruu 1.26.502.15 looks like this:

as you can see, it has (amongst other things), the touchscreen drivers: tp_SYN3202.img (which would allow a 1.xx nandroid's touchscreen to work)

Third, I've checked the 1.29.666.5 nandroid, and although I didn't install it (maybe I will later), all the MD5s check out, so I don't think there's anything wrong with it, but when I get a chance I'll confirm by posting a screenshot.

Fourth, I did give you multiple options, but since you're SIM-locked to Bell, and mentioned you may want to use an unlock code, I recommended you return it to stock Bell so the unlock code works; I don't think a Bell unlock code will work on Dev Edition CID (but I could be wrong)

Cheers
[One (M7) Q&A, Help & Troubleshooting] Mihir1997:
I did not know that nandroids do not have TS drivers, which leads me to believe that my RUU flash went wrong. perhaps I rebooted prematurely or something.

Alternatively, my download may be corrupted, which is completely possible considering my horrific internet connection.

Thanks for all the help. I just feel a little uncomfortable with the nandroid method, so I used the RUU for dev. instead. Until I can find an RUU for the bell variant, I guess I am stuck here haha.

Thank you so much for all the help. I was just posting so others would have something simple to refer to incase they were having the same dificulty like me.
[One (M7) Q&A, Help & Troubleshooting] dingurupa:
So I have hboot 1.56, which according to the instructions means i need to downgrade to hboot 1.44 to actually get rid of tampered. After I go through this process, can I revert back to hboot 1.56 without getting the tampered flag again? I need to return the phone to HTC for warranty (stupid purple camera issue) and don't want to raise any flags by having the old hboot on there. Thanks in advance!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Need a bit more details please,

1- can you post a "fastboot getvar all" (excluding IMEI and s/n)

2- do you have to go S-On, or can you send it in with S-Off?
[One (M7) Q&A, Help & Troubleshooting] dingurupa:
I need to send my device back to T-mobile for a warranty repair. I was assuming the sending the device in s-off would void my warranty. Is that not the case?

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.56.0000

(bootloader) version-baseband: 4A.24.3263.09

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.19.531.10

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

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0713000

(bootloader) cidnum: T-MOB010

(bootloader) battery-status: good

(bootloader) battery-voltage: 4281mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-4dab9d12

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.074s

---------- Post added at 08:23 AM ---------- Previous post was at 08:11 AM ----------

Another update, I read some more on s-off warranty issues with HTC and found someone who sent their HTC One in S-off with this result:

"The HTC Texas repair center refused to repair my M7 with S-Off. Wanted to charge me $180 to fix the purple camera. After arguing and elevating nothing happened, they sent it back, I re-locked/went completely back to stock and tried again. They sent it back no problem."

I don't really want to jump through those hoops..
[One (M7) Q&A, Help & Troubleshooting] dingurupa:
***EDIT***

I was able to place the Guru bootloader reset zip in the right folder with root explorer. I ran the zip from there and this got me back to locked. I followed all of the other steps, restarted multiple times, and changed the phone back to S-ON. I still need to run the system updates but I think that should go smoothly. I'll ship it off to HTC tomorrow and hope for the best!

***ORIGINAL***

Well I can't even get to that step because adb commands aren't working in recovery. I can get adb devices to work properly when the phone is booted up normally, but i get this message in adb when i try to run the adb devices command in recovery: Error: no devices found.

I've tried reinstalling the drivers a couple of times but nothing has worked so far.

After downgrading Hboot to 1.44, which didn't exactly work flawlessly (froze with the HTC logo and green bar 3/4 full), this is what the fastboot getvar all command gets me:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.24.3263.09

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.29.401.12

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

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0713000

(bootloader) cidnum: T-MOB010

(bootloader) battery-status: good

(bootloader) battery-voltage: 4191mV

(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.066s
[One (M7) Q&A, Help & Troubleshooting] bloodbath:
I need to return my phone to T-Mobile for the purple tint issue (it's insured so they are sending me a replacement). I want to make sure I return to stock completely, and so, want to verify I understand everything. This is what I get from the "fastboot getvar all" command:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.56.0000

(bootloader) version-baseband: 4A.25.3263.21

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.19.401.11

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

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0713000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 4122mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-4dab9d12

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

I have TWRP as my recovery and my phone is locked, but not Tampered (I used Revone long ago to remove this). I am also s-off. Here's what I expect to do:

1) Lock phone using: echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796

2) Flash: RUU Zip 7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted

3) Go s-on: fastboot oem writesecureflag 3

My questions:

1) When and how do I change my CID to T-MOB010 (I believe that's the one for T-Mobile US)?

2) Is that the correct RUU.zip?

3) Do I need to do change to CWM or can I use my current recovery (TWRP) when using the RUU.zip method?

4) What does this mean exactly "reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again

as far as I know, this was introduced in hboot 1.55"? Does this mean after the 3rd time rebooting, it will say "tampered"? And if it does say "tampered", how do I get rid of it permanently?

5) Will this get rid of the loading screen that has the red "This build is for development purposes only. Do not distribute..."?

Sorry for all the questions, but as I mentioned, I want it to be perfect when I send it back so I do not have any hassles later. Thanks in advance for all your input and help.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Sorry, had a couple of busy days, haven't had time to check in :o

So all is good? PS: and edit your previous post and remove IMEI.

Oh, and you should have checked the FAQs about adb not seeing your device, and the hboot flash (or any ruu mode flash) never goes to 100% as mentioned in post #8, the important part is that the flash is done twice and says "successful" in the command prompt.

I would really recommend you use a 1.xx ruu, the point 4 you mentioned, is because some/many users (although 100% stock) going from S-Off to S-On on

hboot 1.55

, after rebooting a few times, bootloader would say "tamper detected - rebooting" and upon reboot the TAMPERED is back.

In ruu.zip method, you only need the custom recovery to set LOCKED and remove TAMPERED (you can do that command even if it's not there, it won't hurt ;)) ... so TWRP should be fine with the adb commands.

1) change cid

fastboot oem writecid T-MOB010

fastboot reboot-bootloader

-> confirm CID is good "fastboot oem readcid"

2) enter recovery and use adb commands to remove tampered and set locked

3) flash ruu.zip twice:

http://www.htc1guru.com/dld/ruu-zip...0-20-10-40-1150-04-release-324846-signed-zip/

((modelid: PN0713000, cid: T-MOB010))

4) when the above is successful, boot up, just once to make sure everything is okay,

do not take any OTA

5) go S-On if really needed

fastboot oem writesecureflag 3

fastboot reboot-bootloader

device should now be untampered, locked, and s-on, and you are free to take OTAs if you wish... but why bother? either repair will update it for you, or even better just fix the camera, and send it back as is, so it will be easier for you to get S-Off again :)

PS: and yes, it will get rid of the red text
[One (M7) Q&A, Help & Troubleshooting] dingurupa:
Yep, I got everything sorted out. I read through a bunch before posting but missed the hboot flash not going to 100%. I tried the steps outlined in the FAQ to get adb to see my device but they didn't work. I just dropped the Guru Bootloader Reset file in one of the root folders and installed the zip from recovery instead. That did the trick but i never got adb to recognize my device with the steps outlined in the FAQ.
[One (M7) Q&A, Help & Troubleshooting] bloodbath:
Thank you!!!!!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
sure, no problem, hope all goes well with repair :)
[One (M7) Q&A, Help & Troubleshooting] nokevin:
Sorry for the delay, its been sent back, repaired & returned to me, the phone is all working as it was before, apart from the camera problem, thats sorted, it came back with no Vodacrap in so very happy

Thanks again
[One (M7) Q&A, Help & Troubleshooting] nkk71:
No problem, glad everything worked out :good: :victory:
[One (M7) Q&A, Help & Troubleshooting] cyrusct82:
[MENTION=2605798]nkk71[/MENTION] I have one question. I'm S-ON with bootloader locked. I'm curios if I open the bootloader through HTC DEV and then I try to S-OFF my device and if it will not work is there any way to come to stock with S-ON. (Hboot 1.56)

I ask this because i have the ST camera from 10.2013 and i think that it will have the infamous purple tint.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
if you cannot get S-Off then even if you are able to get your phone back to 100% stock, the best you can get from bootloader is saying it is RELOCKED.... without S-Off, there is no way you can set it to the original LOCKED.

Why not test the camera before unlocking? If it doesn't have the purple tint problem, then proceed with unlocking, otherwise off to exchange/repair before even bothering to unlock.
[One (M7) Q&A, Help & Troubleshooting] cyrusct82:
I have this device from 23.03.2014 but the S/N says that the manufacturing date is 11.11.2013.

If you can help me to decide if my camera is having the problem

This is an image with an white wall shouted right now.

And this is a photo that I've take one night at my window

The situation is the same since I've bought the phone. Even if my phone is hot.

Some photos taken when I bought the phone http://xdaforums.com/showthread.php?p=51499635

If I cover the camera it's all black.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
I honestly don't know, better to see what the guys in the "camera problem" thread think, whether this is the infamous camera tint issue or not.
[One (M7) Q&A, Help & Troubleshooting] .:Moro21:.:
[MENTION=2605798]nkk71[/MENTION] hi nkk!!

i follow your guide but when i restore a nandroid at post #5

http://xdaforums.com/showpost.php?p=47794219&postcount=5 -> STEP 5

how i can set locked if at the STEP 4 i removed the recovery?? and consequently removed the root...

thanks!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
correct, you will loose custom recovery, but in step 5 you use fastboot

boot

CWM.img, this allows you to enter into custom recovery without having to install it :)

however, the fastboot boot ... command only works on hboot 1.44, and that is the reason you need to restore a 1.xx ruu and 1.xx CWM/TWRP nandroid.

PS: root will already be removed when you flash the ruu.zip
[One (M7) Q&A, Help & Troubleshooting] .:Moro21:.:
after the restore 1.xx, obliviously it's possible to upgrade to 4.4.2 and 1.56 or not?

for the ps. but it's possible to rre-root.. no??
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Yes to both, but a question, what do you want to achieve? (the guide is mostly written for warranty/selling 100% stock reason), if you want to accomplish something else, maybe there is an easier way.

Remember to stay S-Off !!

I may not be able to answer today, but please give me more details about what you want to do, and i'll try to help as soon as i can.
[One (M7) Q&A, Help & Troubleshooting] .:Moro21:.:
yeah, i have to send for warrranty for g sensor faulty.. i tried a custom rom to see if was a hw problem or software, and its the first..

so i need to back "100% stock" ahhahah

i am on 4.19.401.11.. so i need to downgrade, lock 100% and then i can upgrade to last ota and then i can send it...
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Ah, in that case, yes... You'll need to downgrade, can you post a fastboot getvar all, excluding IMEI and s/n
[One (M7) Q&A, Help & Troubleshooting] Maxlp:
I have returned everything to stock, but I can't get any OTA's. Right now I have hboot 1.43. and baseband 4A.13.3227.06. It is already locked bootloader and S-ON. Any ideas?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yes, you used the 1.20 ruu, but you should have used the 1.28, as mentioned in post #1:

---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead

if you are now S-On with a LOCKED bootloader, get the RUU.EXE 1.28.401.7 (because you need a signed/encrypted ruu) and run that, the upgrade should work fine, and then you'll receive ota