yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] samersh72:
[MENTION=2605798]nkk71[/MENTION]

thx for this tuto.

im new to HTC, just got it now and it was rooted. i want to go back to full stock, here is my info:

1- i found my RUU (that match my cid and modelid) as .exe and as .zip, so what method do you prefer that i use?

just to be sure, this is the right RUU for me?:

2- i see that i am S-ON, so i need to make it S-OFF before flashing?

3- my current version is 1.29.401.17, and the version that i found is 1.29.401.2, so no problem if i flash it??

4- you mentioned for reseting tamper and lock BL after flashing the guru reset zip to "go through the installer and select "Remove TAMPERED" and "LOCK Bootloader", what do you mean by the "installer"?

i dont wanna to end by bricking this phone since it is not mine :D

im just wanna get it back to full stock.

thanks in advance

Samer
[One (M7) Q&A, Help & Troubleshooting] nkk71:
be back in a little while, but something "stinks" in your output above

product: m7_ul <---> modelid: PN0711000

cidnum: HTC__J15

doesn't make sense, PN0711000 HTC__J15 should be an M7_U model not M7_UL
[One (M7) Q&A, Help & Troubleshooting] samersh72:
oops, sorry for this mistake.... it is m7_u indeed

thx
[One (M7) Q&A, Help & Troubleshooting] nkk71:
that's the problem with typing stuff, a nice copy/paste is always the best :p

so you want "out of the box" never been messed with phone?

the ruu.zip: http://www.htc1guru.com/dld/ruu-zip...0-01_release_311663_signed_2_4_decrypted-zip/

or even ruu.exe: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/

should be fine, as long as you're not using Windows 8 / 8.1 (if you are, then either get Win7, or use an Ubuntu 12.04 LTS 32bit Live USB)

you are already on hboot 1.44, so first thing is to get s-off using revone: http://xdaforums.com/showthread.php?t=2314582

use this ROM, if you're having problems: http://xdaforums.com/showpost.php?p=48955645&postcount=250

once s-off, use RUU.EXE or RUU.ZIP methods (post #2 or #3 in the guide)

recommend you use use CWM recovery in post #7, as other ones have issues with adb in "fastboot boot CWM.img".

Let me know if you need any more help, or questions.
[One (M7) Q&A, Help & Troubleshooting] samersh72:
in fact it is a copy paste from a pre-posted info but i miss edited well :laugh:

thanks for your info.

do i can still take ota after flashing?

and no problem flashing 401.2 on my 401.17 version, right?

thx, i will post result.

cheers
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yes, yes,

no

"copy paste from a pre-posted info" :rolleyes:

once, you're s-off, you downgrade to .2 and you receive OTA updates to higher versions

IF you intend on going s-on, then only do so on hboot 1.44 or 1.54... do not attempt to go s-on on hboot 1.55
[One (M7) Q&A, Help & Troubleshooting] samersh72:
can i use revone option to reset tamper and lock bootloader instead of Guru zip?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Yes
[One (M7) Q&A, Help & Troubleshooting] hmgan:
Wow that was detail!!! Now, what's the difference running RUU.exe vs RUU.zip?

Nkk71, you refer me to ruu_m7_ul_jb_50_htc_asia_wwe_1-26-707-5_radio_4a-13-3231-20_10-30-1131-05_release_309365_signed_2_4-exe

Please confirm my RUU again. Could I send for warranty claim with s-off?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
1) RUU.EXE vs RUU.ZIP is pretty much the same thing (as far as results are concerned); RUU.EXE is a Windows application, whereas RUU.ZIP can be used in Windows, Mac, and Linux, by using fastboot commands.

So for example, if you have Windows 8.1 and problems with it "seeing" your phone, and you don't have access to a Win7 machine, then best to use an Ubuntu Live USB, and use the RUU.ZIP method.

2) as for which ruu, as per your previous output:

(bootloader) modelid: [B]PN0714000[/B]
(bootloader) cidnum: [B]HTC__044[/B]

you can use either of the following:

RUU_1.26.707.5_PN0714000_HTC__044.exe

or

RUU_1.29.707.3_PN0714000_HTC__044.exe

I (personally) have a tendency of using the lowest version (with the exception of 1.20.401.1), but either of the above should be fine.

3) "Could I send for warranty claim with s-off?" theoretically, yes. the only thing repair service should care about is if they see TAMPERED or RELOCKED/UNLOCKED, which is an obvious giveaway that you "messed" with your phone; some phones (very rare) do actually ship S-Off from the factory.

If you are worried about it, then just go S-On, BUT if you do go S-On, do it as mentioned in the guide before taking any OTA updates; in particular 3.xx (which comes with hboot 1.55), because going S-Off to S-On on hboot 1.55 will very likely trigger a "tamper detected - rebooting" and TAMPERED is back.

After you're S-On, you can take OTAs if you like, but why bother, they will probably update it for you anyway.
[One (M7) Q&A, Help & Troubleshooting] samersh72:
toooo bad connection, i didnt manage yet to download the RUU :(

[MENTION=2605798]nkk71[/MENTION] sorry for bothering you with my questions,

1- is it the same firmware to flash for 32GB and 64GB versions??

2- i noticed that a twrp recovery is installed, sure the flashed RUU will install the stock one, right?

3- is there a potential risk to lose network/operator connectivity, or wifi problem after flashing the RUU, since it may happen on some of my Samsung devices?

thx in advance
[One (M7) Q&A, Help & Troubleshooting] nkk71:
1- yes it's the same for both

2- ruu will reset EVERYTHING to zero

3- not as far as i know, ruu, will reset your device to stock. why would you loose "network/operator connectivity, or wifi problem"?
[One (M7) Q&A, Help & Troubleshooting] samersh72:
some new modems included in stock firmwares for samsung, had a different structure than the old one that may corrupt the efs partition.

any way i noticed that the ruu i intend to flash contains the same modem version already installed on my device.

thank you
[One (M7) Q&A, Help & Troubleshooting] nkk71:
as far as i've seen, radios on M7 are all "interchangeable"
[One (M7) Q&A, Help & Troubleshooting] zinder33:
Do i need to be on latest hboot to recieve ota as 4.4.2 hit europe and i am still at 4.3?

I am on hboot 1.44 shall i update the hboot so as to get ota?

Any guide please

Thanks
[One (M7) Q&A, Help & Troubleshooting] nkk71:
hboot shouldnt matter, only stock ROM and stock recovery. and of course CID and MID for the released OTA.

what's your current "fastboot getvar all" (except IMEI and s/n)?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
but the update from 2.24 to 3.62.401.1 went well?

didn't think OTA checks firmware version, but i could be wrong; are you on 100% stock rom 3.62.401.1? (rooted or no? if rooted, i check something first).
[One (M7) Q&A, Help & Troubleshooting] zinder33:
Yup i followed your advice in going stock but also after your advice i rooted also without touching stock recovery and downgraded my hboot to 1.44 and things went well ..

Just fastboot recovery not flashed it ...

My main version is 1.29.401.12 not 2.24 or 3.62?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
since you're rooted, can you use a root-enabled file explorer (such as ES File Explorer or similar) with ROOT enabled, and go to /system and copy build.prop and post it here (or upload to dropbox or similar), i wanna take a look please :)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
That's perfectly normal, cause of hboot downgrade, the main version will always show the last thing flashed, doesn't actually mean your firmware is 1.29.

EDIT: from radio 4A.21.3263.04 we can conclude actual firmware to be WWE 3.62.401.1/4.3. (unless you flashed radio separately too)
[One (M7) Q&A, Help & Troubleshooting] zinder33:
Here is the file sir

https://www.dropbox.com/s/2bzrdobtuuati0d/build.prop
[One (M7) Q&A, Help & Troubleshooting] nkk71:
"fingerprint" matches the new OTA... and you're not receiving any update notification? i guess, it looks like OTA check does actually look at mainversion.

i guess best to flash back 3.62.401.1 firmware, you can download it here: http://xda7.androidrevolution.nl/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/

MD5: 72eb59a1ee882c68fc29c66d056abb18

fastboot oem rebootRUU

fastboot flash zip 3.62.401.1.zip

fastboot flash zip 3.62.401.1.zip

fastboot reboot-bootloader

-> if all OK now,

fastboot reboot

and check for software updates
[One (M7) Q&A, Help & Troubleshooting] zinder33:
No update still available shall i flash 4.19.401.8 zip now?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
so i guess, version-main doesn't matter after all, or does it :confused:

i guess, something must be delaying the OTA, so either wait a few days, or go ahead and do it manually:

you'll have to download the OTA file "OTA_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.8-3.62.401.1_release_34978069qunfn8klmohm8p.zip"

probably best to rename to just "ota.zip", and put that on your internal storage,

then boot to stock recovery, and briefly press POWER + VOLUP to get to the menu (or POWER + VOLDOWN + VOLUP briefly), you may need to try a couple of times to get the timing right.

then apply from phone storage, find the ota.zip and let it install.
[One (M7) Q&A, Help & Troubleshooting] zinder33:
u wont believe what i did i just flashed 4.19.401.8 firmware and now phone keeps rebooting on splash screen ? hahah what the puck i did?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
just reflash 3.62.401.1 firmware again

EDIT: then you need to get the whole OTA file it's about 320MB. the firmware is also in the OTA, but more importantly the patches from 3.62.401

ROM

to 4.19.401.8.
[One (M7) Q&A, Help & Troubleshooting] zinder33:
yeah did same but same problem trying wiping cache from stock recovery if that would help?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
reflash 3.62.401.1 firmware as mentioned in previous post, then

fastboot erase cache
[One (M7) Q&A, Help & Troubleshooting] samersh72:
[MENTION=2605798]nkk71[/MENTION]

weird! can not S-OFF it or lock the bootloader! always give error -1 with revone when executing "./revone -s 0 -u"

even with rumrunner, everything went ok but S-ON still

did i miss something?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
wait, before trying to lock etc, you first need to S-Off

did you install the ROM i suggested earlier (ARHD 9.4): http://xdaforums.com/showpost.php?p=48955645&postcount=250

and did the revone steps:

1. Download revone (above) and push it to your device: adb push revone /data/local/tmp/

2. Open an adb shell and:

* cd /data/local/tmp

* chmod 755 revone

4. Prepare to gain S-OFF by running the command: ./revone -P

4a. If revone reports success reboot the device and proceed to step 5)

4b. If revone reboots the device (we'll pretend this isn't an undiagnosed random crash) please wait 2 minutes then try again from step 2.

4c. If revone reports that you need to reboot and try again please reboot and try again from step 2.

5. Now that revone has successfully prepared your device for S-OFF please open another adb shell (as per step 2) and change to

the /data/local/tmp directory.

6. Instruct revone to grant you S-OFF and unlock status by running the command: ./revone -s 0 -u

copy/paste command prompt output please if you still aren't s-off
[One (M7) Q&A, Help & Troubleshooting] ketto:
problem installing RUU

Guys im having a weird problem. I did all as said, everything worked as said in first post, only problem is that the RUU.exe wont intstall and i got the correct one for mine... can you point me if im wrong, heres my getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.21.3263.04

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

(bootloader) cidnum: HTC__032

(bootloader) battery-status: good

(bootloader) battery-voltage: 3865mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

i tried this one

http://www.htc1guru.com/dld/ruu_m7_..._10-27-1127-01_release_308001_signed_2_4-exe/

and 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] samersh72:
ok... i managed to have S-OFF, remove tamper, lock state using terminal emulator:D

i dont know if this is a driver issue on my vista pc.

note that adb and fastboot command are working fine. i used to flash sony, LG, samsung devicves on my laptop...

dont know what is happening with the HTC

any way.. i guess im ready to execute the RUU.exe. right?

i see that you can be on fastboot or bootloader status on device, so to run the .exe must be on what or is it the same?

thx
[One (M7) Q&A, Help & Troubleshooting] nkk71:
not the first (1.20.401.1), use the second one: 1.28.401.7

what's the error with the RUU? (and which Windows/Mac/Linux are you using?)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
ALMOST ready for ruu, you need to fix driver issue first though!

maybe update, drivers, check here: http://xdaforums.com/showthread.php?t=2089508
[One (M7) Q&A, Help & Troubleshooting] ketto:
Using Windows 7. Error 155. Thanks for rply
[One (M7) Q&A, Help & Troubleshooting] nkk71:
strange.

anyway, fastboot working good? then download this: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/

and use RUU.ZIP method (post #3)
[One (M7) Q&A, Help & Troubleshooting] samersh72:
ok, im installing the HTC driver.

i need to be on Hboot to run RUU.exe?

if the flash fail, will it brick the phone or it can boot normally to the old one?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
once drivers are installed, I would test fastboot and adb commands to be sure they're working, otherwise RUU will not detect your phone correctly, and be able to reset your device.

RUU will not brick your phone unless you unplug while it's trying to update hboot partition.

RUU can be run from booted up ROM, it will reboot to bootloader then "fastboot oem rebootRUU" mode. but yes you could run in directly in bootloader should work fine also.
[One (M7) Q&A, Help & Troubleshooting] ketto:
I changed the USB port, i started from the beginning and finaly it worked :)

I dont know what was the deal but the point is that it worked :)

Thank you man, youre awesome!

Can you tell me is the s off default when you buy or s on?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
You're welcome :laugh:

Default is usually S-On, some phones (very rare) actually ship S-Off by mistake from the factory, but S-On is usually default.

If you are going to S-On, do so before any updates (especially to 3.xx which includes hboot 1.55); see the guide about "tamper detected - rebooting"
[One (M7) Q&A, Help & Troubleshooting] samersh72:
[MENTION=2605798]nkk71[/MENTION]

Finally, im stock :good:

if i dont want to make it S-ON, can i still take OTA?

thank you my friend for your Guide and help :):)

Edit: i boot into recovery, but there is a device photo with red triangle and no recovery commands, what is that??
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Yes, absolutely no problem receiving OTAs with S-Off :good:

I prefer S-OFF :D

You're welcome, glad it helped :)

That's "stock recovery" no problem!

starts with a green triangle, then turns red after 30secs or so, and if you briefly press POWER + VOLUP or POWER + VOLUP + VOLDOWN, you'll see the stock recovery menu (you may need to try a few times to get the timing right)

see attached screenshots :)
[One (M7) Q&A, Help & Troubleshooting] zinder33:
i just took the ota.zip and now when i tried to flash via recovery it gives me a error saying "/system/app/htclockscreen.apk" has unexpected contents. installation aborted.

is there problem with some system apk or shall i flash the system.img for current rom again??
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Stop flashing for the moment, obviously something isn't "stock" in your setup.

I'll get back to you when I get a chance.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
hi [MENTION=4741043]zinder33[/MENTION] ,

first question is where did you get the ota from, are you sure it's "OTA_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.8-3.62.401.1_release_34978069qunfn8klmohm8p"

(this is sort of a silly question, cause first thing the OTA would check is the fingerprint)

Basically, the OTA will do the following checks:

1- ro.build.fingerprint

2- ro.aa.taskid

3- CID

4- MID

5- if those above pass, then it will begin checking all the apps, libs, fonts, etc (in the case of OTA to 4.19.401.8) it checks 1275 files!!

if ALL of those check out OK, it can proceed with the update; if even only one of those differ from expected in cannot update because the patches are just diff's so require an exact version to be able to apply a patch.

"/system/app/HtcLockScreen.apk" check is number 68 of the 1275 checks. I don't know why it's different, perhaps you changed or deleted it to use another LockScreen app?

Anyway, here's what you can do, download this: http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/ and put it on your phone

reinstall a custom recovery

fastboot flash recovery <name of recovery>.img

fastboot erase cache

fastboot reboot-bootloader

-> enter recovery

and install the above Guru Reset, with the following options:

* do not WIPE (so that your settings, apps, data, etc) remain intact, if you wipe, you will loose settings+apps+data

* select "stock recovery"

* radio doesn't matter

* root at your discretion (i don't think it should interfere with the OTA update), you can always try with root, if OTA fails, then dirty flash (ie without wipe) Guru Reset again without root

the above Guru Reset will reinstall all system files, and the OTA should work now.
[One (M7) Q&A, Help & Troubleshooting] zinder33:
Haha hell of process again ....i actually got ota from the androidhost website and i will try again and will post then feeling annoyed...???
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yeah, i understand your frustration, but did you change/rename/overwrite the htcLockScreen by any chance (or some rooted app did)?
[One (M7) Q&A, Help & Troubleshooting] zinder33:
voila without installing root and busy box from guru reset stock i managed to flash ota zip and right now on total stock but urge to root still there lols,,,,,,
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Good :good:

I couldn't live without root :D

but why you on stock, the custom ROMs have been updated / are being updated to latest base, and seem smooth :cool:
[One (M7) Q&A, Help & Troubleshooting] zinder33:
lols i just dont want custom roms i just want some tweaks thats all but in future if i root now may infer with ota ? so better advice from you will be?????

i just managed to downgrade hboot from 1.56 to 1.44 and install tempted superuser..lols and big releif......thanks mate for always being there in bad times yeahhhhhhhhhhhhhhhhh
[One (M7) Q&A, Help & Troubleshooting] nkk71:
I really don't know why htcLockscreen was modified, it must have been "something"; maybe one of those tweaks you were using?

Root by itself shouldn't affect OTA, you may loose root after the update installs, but just being rooted shouldn't cause a problem; plenty of successful post about being rooted and able to receive OTA, a quick look and I found this example: http://xdaforums.com/showthread.php?p=42122514

in that post you can obviously skip step 2, as you already have them back

and several other posts with successful OTA even when rooted.

If one of the tweaks is actually changing a system app, then back that up first (using any root-enabled file explorer), and restore it before OTA.
[One (M7) Q&A, Help & Troubleshooting] zinder33:
i just edited my reply above hboot downgrade is possible with 1.56 hboot even as i did it ..
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Isnt S-Off wonderful :cowboy:

anyway, since you have the OTA.zip file, you could also just flash a custom recovery, and when the next OTA comes out, just extract "recovery.img" from within the OTA and flash it back.
[One (M7) Q&A, Help & Troubleshooting] zinder33:
yup s-off is awesome mate anyways finally on 4.4.2 yeah now i can have my carling with cheers lols ...
[One (M7) Q&A, Help & Troubleshooting] DaiC1:
I’m considering the benefit (if Any) of un-branding my O2___001 *.*.206.* to HTC__001 *.*.401.* {WWE} fully stock (No real reason just trying to get my head around process and having a play)and was wondering if this would work.

Current S-0FF,Unlocked Hboot. 1.56.

Flash to Hboot 1.44

Change cid to HTC__001 then follow #3

Install “Guru_Bootloader_Reset_1.0.zip”

RUU.EXE “ruu_m7_ul_jb_50_htc_europe_1-20-401-1_radio_4a-13-3227-06_10-27-1127-01_release_308001_signed_2_4

Custom ROM and remain S-OFF.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Well,

1- O2 -> so i guess model id would already by PN0710000 so no need to mess with that.

2- S-Off, so no need to downgrade for CID, just "fastboot oem writecid HTC__001"

3- Guru Bootloader Reset to remove TAMPERED (but you probably already did)

4- I would remain UNLOCKED, otherwise normal "fastboot flash" won't work, check my chart: http://xdaforums.com/showpost.php?p=49832723&postcount=388

(eg, even with s-off "fastboot flash recovery <name of recovery>.img" will NOT work)

5- If you're going for custom ROM, then no need to use RUU.EXE, no benefits

----> just install custom ROM and flash firmware

If you are going to use an RUU (but why?) then you have to use the 1.28.401.7 http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/

the 1.20 seems to be some kind of pre-release (it has hboot 1.43 :confused: and doesnt get any OTAs)

Hope that helps, let me know if you have any questions
[One (M7) Q&A, Help & Troubleshooting] DaiC1:
Thanks for the quick reply, you are a star.
[One (M7) Q&A, Help & Troubleshooting] Mohanned85:
hi guys

I am trying to get my hboot back to 1.44,

i follow these steps

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

but it fails

were do i copy fastboot flash zip 1.29.401.12_hboot_1.44.zip

---------- Post added at 02:13 AM ---------- Previous post was at 02:08 AM ----------

i get this error

target reported max download size of 1526722560 bytes

sending 'zip' (501 KB)...

OKAY [ 0.233s]

writing 'zip'...

(bootloader) zip header checking...

(bootloader) zip info parsing...

(bootloader) Read zipped android_info fail

FAILED (remote: 99 unknown fail)

finished. total time: 0.479s
[One (M7) Q&A, Help & Troubleshooting] Mohanned85:
Lads please help

i back in work monday and need phone back working :(
[One (M7) Q&A, Help & Troubleshooting] clsA:
You have to edit the android-info.txt inside the zip file to match your MID and CID. Open the zip in 7zip and click the android-info.txt edit it and save it when your done. The file just has to be in the same folder as fastboot/adb.
[One (M7) Q&A, Help & Troubleshooting] tobesedated:
I don't have a problem just want to say thanks. I'm on Rogers and there's no RUU for us, so getting back to stock to get the latest update was a chore. I followed your specific Rogers advice and messed up a couple times. All mistakes were mine and were silly. I didn't give up though..I just looked at what I did, re-read what your steps were and made minor adjustments to what I had done. I now have a copy or two of the Rogers KitKat OTA, a TWRP backup of stock KitKat, and a CWM backup as well. Now if I need to get back to KitKat stock it will be much easier lol.

So again, thank you for your help and also for your referrals. If you could use a copy of the backups or OTA for Rogers, I'd be happy to share. All KitKat...
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Are you s-on? You need to be s-off.