Database Develop

[Q] Going back to stock

Hi, i seem to have gotten a problem with my phone jumping to car mode randomly, even when its plugged in, so guess it is in need of a service.
After reading some guides about going back to stuff, i just have to get confirmation that i have understood it correctly.
The only process i need to do is the following (I have s-off and hboot 1.44, latest firmware):?
1. Change the SID back to stock
2. Run the RUU.exe
3. Make it s-off again and remove tampered with revone?
Is that all or am i forgetting something crucial?

raysv said:
Hi, i seem to have gotten a problem with my phone jumping to car mode randomly, even when its plugged in, so guess it is in need of a service.
After reading some guides about going back to stuff, i just have to get confirmation that i have understood it correctly.
The only process i need to do is the following (I have s-off and hboot 1.44, latest firmware):?
1. Change the SID back to stock
2. Run the RUU.exe
3. Make it s-off again and remove tampered with revone?
Is that all or am i forgetting something crucial?
Click to expand...
Click to collapse
1- change CID back to stock
2- remove TAMPERED using either revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- change to LOCKED using either revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- AFTER ABOVE use the correct RUU.exe for your phone; you will not loose S-Off because of the RUU.

nkk71 said:
1- change CID back to stock
2- remove TAMPERED using either revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- change to LOCKED using either revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- AFTER ABOVE use the correct RUU.exe for your phone; you will not loose S-Off because of the RUU.
Click to expand...
Click to collapse
Thanks for the reply.
Did all the things, but it refuses to flash the ruu.. when running the ruu.exe its returning error 155 after awhile Any idea of what might be wrong?

are you using the right CID for the RUU?

stovie_steve said:
are you using the right CID for the RUU?
Click to expand...
Click to collapse
Yes I changed my CID back to the original CID, and the RUU i downloaded said on the download page that this was for this CID HTC__Y13.
My bootloader also says LOCKED

raysv said:
Yes I changed my CID back to the original CID, and the RUU i downloaded said on the download page that this was for this CID HTC__Y13.
My bootloader also says LOCKED
Click to expand...
Click to collapse
Did u also check MID?
I thought 155 was because of an unlocked bootloader, does it give any information more than 155? Maybe also try to find the log (should be somewhere in temp on ur pc)
I'll be online later today, and will check back.
Sent from my HTC One using Tapatalk

I also had that error before when I was on a later hboot (1.54 and 1.55) and would only work if I had hboot 1.44
Can you post your fastboot getvar all removing S/N and IMEI?

stovie_steve said:
I also had that error before when I was on a later hboot (1.54 and 1.55) and would only work if I had hboot 1.44
Can you post your fastboot getvar all removing S/N and IMEI?
Click to expand...
Click to collapse
Here is my getvar:
C:\Android>fastboot 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.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4273mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
Have tried downgrading the firmware also by "unlocking" the bootloader again as described in the post over (not the revone way but the other). and try and flash the hboot 1.44.. but now it seems that I'm just getting remote denied when trying to flash.. Dosn't that indicate that the bootloader is still locked?

Have managed to downgrade the hboot and firmware... Will try the ruu again and see if it works if i can get it to stay connected to the computer via USB... Right now it just plings for 2 sekunds, and then loosing the connection again..

Thanks alot guys for the help.
Seems like it was my hboot messing up, once i downgraded the firmaware and zip before trying the ruu it seems to work Atleast no 155 error or problems arised so faar, just the green progress bar *keeps his fingers crossed*
Again, great help Now its time to ship it to service
BTW: anyone know if they are actually able to fix the usb plug since its unibody design? Or will it most likly be a replacement?

Help returning to stock for repair

Hi Guys i am following this guide to restore my phone to stock for HTC repair (camera issue)
http://forum.xda-developers.com/showthread.php?t=2358738
do I need to make the phone s-on and lock the bootloader?
it mentions that can brick if has a modified HBOOT when re-locking the bootloader
so my main question is this "is the Stock HBOOT included in RUU?

Dynomutt said:
Hi Guys i am following this guide to restore my phone to stock for HTC repair (camera issue)
http://forum.xda-developers.com/showthread.php?t=2358738
do I need to make the phone s-on and lock the bootloader?
it mentions that can brick if has a modified HBOOT when re-locking the bootloader
so my main question is this "is the Stock HBOOT included in RUU?
Click to expand...
Click to collapse
you might wanna check my guide: http://forum.xda-developers.com/showthread.php?t=2541082

thanks so much

Dynomutt said:
thanks so much
Click to expand...
Click to collapse
no problem, please follow instruction 1, then 2 then 3, etc.
s-on is OPTIONAL, it's up to YOU to decide that

still having trouble, found my original stock backup of 4.2.2, but now have HBOOT 1.44, i really need a full Vodafone UK RUU the .exe version would probably be best but just cant find anywhere, cant even flash the OTA RUU probably because I have mismatched firmware, recovery and HBOOT now,
well UPS is picking it up tomorrow so i'll just have to hope they don't refuse repair due to software not being 100% stock especially as the issue is a hardware fault
wish me luck and thanks for you help

Dynomutt said:
still having trouble, found my original stock backup of 4.2.2, but now have HBOOT 1.44, i really need a full Vodafone UK RUU the .exe version would probably be best but just cant find anywhere, cant even flash the OTA RUU probably because I have mismatched firmware, recovery and HBOOT now,
well UPS is picking it up tomorrow so i'll just have to hope they don't refuse repair due to software not being 100% stock especially as the issue is a hardware fault
wish me luck and thanks for you help
Click to expand...
Click to collapse
can u post a "fastboot getvar all" (remove IMEI and s/n)

nkk71 said:
can u post a "fastboot getvar all" (remove IMEI and s/n)
Click to expand...
Click to collapse
sure will thanks, whats ODD is that the CID does not match my CID in bootloader, in bootloader it says VODAP001 is my CID,
EDIT: just check it and it is HTC__001 changing back to VODAP001 and trying OTA again
(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: xxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3984mV
(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.087s

Dynomutt said:
sure will thanks, whats ODD is that the CID does not match my CID in bootloader, in bootloader it says VODAP001 is my CID
(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: SHxxxxxxxxxxxxxx
(bootloader) imei: 3xxxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3984mV
(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.087s
Click to expand...
Click to collapse
1- you might wanna edit your post and remove IMEI and s/n
2- from above getvar, you look like you followed the first part of my guide an now your phone, is an European unbranded phone.
3- so quick quick question, you wanna go back to "VODAP001" (do you really need to?) ? is there a nandroid backup out there?

nkk71 said:
1- you might wanna edit your post and remove IMEI and s/n
2- from above getvar, you look like you followed the first part of my guide an now your phone, is an European unbranded phone.
3- so quick quick question, you wanna go back to "VODAP001" (do you really need to?) ? is there a nandroid backup out there?
Click to expand...
Click to collapse
Yeah sorry I noticed edited post now, ive changed my CID back to VODAP001, I have my original 4.2.2 stock rom flashed hopefully be able to pull to 4.3 OTA once im back up and running, thanks for you help mate

thanks again for your help, OTA is now downloading and i should be back to fully stock soon and can send for repair worry free.

Dynomutt said:
Yeah sorry I noticed edited post now, ive changed my CID back to VODAP001, I have my original 4.2.2 stock rom flashed hopefully be able to pull to 4.3 OTA once im back up and running, thanks for you help mate
Click to expand...
Click to collapse
don't forget you need "stock recovery" for OTA to update correctly, and do not go from s-off to s-on on 4.3 (hboot 1.55) it will most likely trigger a "tamper detected"!!
if you did get hboot 1.55 just keep s-off, otherwise you're gonna be back on square 1.
I have to sign off now, but you can PM me if anything comes up before tomorrow.
if my guide did help you in any way, i would appreciate it if you posted your details, in my thread (whenever you get a chance), it will be helpful to others.
and hit the thanks button in the guide
good luck :fingers-crossed:

Yeah I flashed my original stock backup, flashed stock recovery and locked bootloader , I had forgot to change my CID back, it wasn't till u advised that I post my " getvar all" that I noticed, I haven't checked if my HBOOT is still 1.44 or updated to 1.55 yet, I left s-off hope it still is, again many thanks mate
Sent from my HTC One using xda app-developers app

Yeah I'm on HBOOT 1.55 now but still s-off, I take it if I s-on again I won't be able to get it back, I used rumrunner s-off last time but I that was on HBOOT 1.54 iirc, not that it matter now anyway
Sent from my HTC One using xda app-developers app

Dynomutt said:
Yeah I'm on HBOOT 1.55 now but still s-off, I take it if I s-on again I won't be able to get it back, I used rumrunner s-off last time but I that was on HBOOT 1.54 iirc, not that it matter now anyway
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Keep s-off, otherwise u may end up having to start at square 1, and if I read correctly, u have to send it off in the morning.
UK repair centers seem quite decent, and they can't really prove it wasnt s-off to begin with.
"what's s-what anyways, hmm, no clue what u talking about"
Sent from my HTC One using Tapatalk

nkk71 said:
Keep s-off, otherwise u may end up having to start at square 1, and if I read correctly, u have to send it off in the morning.
UK repair centers seem quite decent, and they can't really prove it wasnt s-off to begin with.
"what's s-what anyways, hmm, no clue what u talking about"
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
ha ha yeah, weirdly though this morning I still had root, is this normal after OTA?

OTA update will remove tampered flag or not ?????

Okay I`m planning to send my phone back for wrrnty claim ( bottom speaker issue ).......manage to revert back to stock 4.1.2, stock recovery, s-on and locked bootloader except this tricky tampered flag........already tried removing many times it using revone but always ended up with error =2........now my final option is updating to 4.2.2 through OTA...........
Will those tampered flag gone if I updating to 4.2.2 through OTA ???? Thanxx in advance............

Maybe.. something isn't original, could be boot, hboot, recovery, etc that's why you have the flag up.

backfromthestorm said:
Maybe.. something isn't original, could be boot, hboot, recovery, etc that's why you have the flag up.
Click to expand...
Click to collapse
Not so convincing answer...........anyone ????

OMG nobody can help me I`m really confuse here

crazynobita said:
OMG nobody can help me I`m really confuse here
Click to expand...
Click to collapse
if you s-off, you can use either one of these:
http://forum.xda-developers.com/showthread.php?t=2477792
http://forum.xda-developers.com/showthread.php?t=2527194
and if you want to go completely back to stock, check my guide (in my signature), if you REALLY insist on going S-On, do it exactly WHEN it is mentioned to do it, ie after 1st OTA, but BEFORE hboot 1.55!!

crazynobita said:
Okay I`m planning to send my phone back for wrrnty claim ( bottom speaker issue ).......manage to revert back to stock 4.1.2, stock recovery, s-on and locked bootloader except this tricky tampered flag........already tried removing many times it using revone but always ended up with error =2........now my final option is updating to 4.2.2 through OTA...........
Will those tampered flag gone if I updating to 4.2.2 through OTA ???? Thanxx in advance............
Click to expand...
Click to collapse
Yup Use the below link and it should be removed.. No need to worry abt or u could flash ruu to revert back to fully stock to claim warranty.
http://forum.xda-developers.com/showthread.php?t=2477792
Hope it helps:good:

Sedariya11 said:
Yup Use the below link and it should be removed.. No need to worry abt or u could flash ruu to revert back to fully stock to claim warranty.
http://forum.xda-developers.com/showthread.php?t=2477792
Hope it helps:good:
Click to expand...
Click to collapse
ALready used revone guide but always ended up with error =-2......
DOn`t know if root device causing that..........
I will follow NKK71 guide later btw............

WOW made it.......thanks NKK71 for your awesome guide.......
Manage to revert back to 4.1.2 using ruu.zip guide.......but can you really confirm to me if it also replacing costum recovery to stock recovery also ????
I want to do OTA update btw.........that`s why I`m asking............

crazynobita said:
WOW made it.......thanks NKK71 for your awesome guide.......
Manage to revert back to 4.1.2 using ruu.zip guide.......but can you really confirm to me if it also replacing costum recovery to stock recovery also ????
I want to do OTA update btw.........that`s why I`m asking............
Click to expand...
Click to collapse
can you tell me exactly which steps you followed (and any links you used), and also a "fastboot getvar all" (remove IMEI and s/n), post back in my thread please

nkk71 said:
can you tell me exactly which steps you followed (and any links you used), and also a "fastboot getvar all" (remove IMEI and s/n), post back in my thread please
Click to expand...
Click to collapse
I`m using RUU.zip guide.........
Also here my fastboot getvar all :-
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.707.3
(bootloader) version-misc: PVT SHIP S-ON
(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: 3888mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT

crazynobita said:
I`m using RUU.zip guide.........
Also here my fastboot getvar all :-
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.707.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
1- remove IMEI and s/n, we don't need to these these
2- if you used the ruu.zip method (successfully) then you are now 100% stock
I see you even decided to s-on
(i prefer s-off)

nkk71 said:
1- remove IMEI and s/n, we don't need to these these
2- if you used the ruu.zip method (successfully) then you are now 100% stock
I see you even decided to s-on
(i prefer s-off)
Click to expand...
Click to collapse
1- remove IMEI and s/n........errr what`s that mean ???? how ???
2- really ???? glad to hear it
3-some said s-off will void wrrnty some said it`s not so it`s safe to just s-on

crazynobita said:
1- remove IMEI and s/n........errr what`s that mean ???? how ???
2- really ???? glad to hear it
3-some said s-off will void wrrnty some said it`s not so it`s safe to just s-on
Click to expand...
Click to collapse
(bootloader) serialno: xxxxxxx
(bootloader) imei: xxxxxx
He's saying don't ever share this stuff with anyone. These numbers are uniquely for your phone. IE your phone's social security number.

crazynobita said:
1- remove IMEI and s/n........errr what`s that mean ???? how ???
2- really ???? glad to hear it
3-some said s-off will void wrrnty some said it`s not so it`s safe to just s-on
Click to expand...
Click to collapse
go to your post and click the EDIT button, then you can "xxxxx" out IMEI and serialno
you're good to send to warranty, and receive OTAs if you wish.

[Q] Bootloop after RUU attempt (completely stuck!)

I recently tried to revert back from CM 10 to stock on my HTC one.
Everything seemed to be going fine, I found what I believed to be the right RUU(I couldnt find it in a .exe, only .zip) .
And I successfully used revone to get s-off, remove tampered and change unlocked to locked in the bootloader.
But when changing s-off back to s-on the security warning banner showed up in the bootloader and for some reason I couldn’t get into the OS anymore, it just went straight to the bootloader. I didn’t bother thinking about it since I was going to install the RUU either way. But I get the same error every time I try to install it: FAILED (remote: 12 signature verify fail). Also I couldn’t get into recovery, it just shot be back straight into the bootloader.(Correct me if i'm wrong but did the ruu.zip fail because you have to have s-off for it to work? Would make sense.) On top of that I couldn’t just get s-off again because for some reason i can only use adb commands when the phone is in the actual OS, it doesn't seem recognize it when its in bootloader/fastboot/recovery, fastboot commands work fine tho.
I was able to unlock the bootloader again using htcdev and I can now access twrp, but I can't seem to be able to factory reset, it just says: Unable to mount /data and unable to mount internal storage. The mount option in twrp does not seem to work either, trying to check data makes nothing happen. Also instead of it just launching to the bootloader directly on startup, it now gets stuck in a bootloop until you make it go into the bootloader.
As you can see i'm in quite the pickle and absolutely any help on either getting back to a functional CM or stock would be much appreciated.
The getvar all info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W903347
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4065mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.045s
If any more info is needed just ask

victor_021 said:
I recently tried to revert back from CM 10 to stock on my HTC one.
Everything seemed to be going fine, I found what I believed to be the right RUU(I couldnt find it in a .exe, only .zip) .
And I successfully used revone to get s-off, remove tampered and change unlocked to locked in the bootloader.
But when changing s-off back to s-on the security warning banner showed up in the bootloader and for some reason I couldn’t get into the OS anymore, it just went straight to the bootloader. I didn’t bother thinking about it since I was going to install the RUU either way. But I get the same error every time I try to install it: FAILED (remote: 12 signature verify fail). Also I couldn’t get into recovery, it just shot be back straight into the bootloader.(Correct me if i'm wrong but did the ruu.zip fail because you have to have s-off for it to work? Would make sense.) On top of that I couldn’t just get s-off again because for some reason i can only use adb commands when the phone is in the actual OS, it doesn't seem recognize it when its in bootloader/fastboot/recovery, fastboot commands work fine tho.
I was able to unlock the bootloader again using htcdev and I can now access twrp, but I can't seem to be able to factory reset, it just says: Unable to mount /data and unable to mount internal storage. The mount option in twrp does not seem to work either, trying to check data makes nothing happen. Also instead of it just launching to the bootloader directly on startup, it now gets stuck in a bootloop until you make it go into the bootloader.
As you can see i'm in quite the pickle and absolutely any help on either getting back to a functional CM or stock would be much appreciated.
The getvar all info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W903347
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4065mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.045s
If any more info is needed just ask
Click to expand...
Click to collapse
Where did you get the RUU from? It should work even if S-ON as long as the version of the RUU is the same as or newer than your current version.
EDIT: Did it say it was Encrypted or Decrypted? It needs to have an Encrypted Signature or else you'll get the Remote 12 error.

victor_021 said:
I recently tried to revert back from CM 10 to stock on my HTC one.
Everything seemed to be going fine, I found what I believed to be the right RUU(I couldnt find it in a .exe, only .zip) .
And I successfully used revone to get s-off, remove tampered and change unlocked to locked in the bootloader.
But when changing s-off back to s-on the security warning banner showed up in the bootloader and for some reason I couldn’t get into the OS anymore, it just went straight to the bootloader. I didn’t bother thinking about it since I was going to install the RUU either way. But I get the same error every time I try to install it: FAILED (remote: 12 signature verify fail). Also I couldn’t get into recovery, it just shot be back straight into the bootloader.(Correct me if i'm wrong but did the ruu.zip fail because you have to have s-off for it to work? Would make sense.) On top of that I couldn’t just get s-off again because for some reason i can only use adb commands when the phone is in the actual OS, it doesn't seem recognize it when its in bootloader/fastboot/recovery, fastboot commands work fine tho.
I was able to unlock the bootloader again using htcdev and I can now access twrp, but I can't seem to be able to factory reset, it just says: Unable to mount /data and unable to mount internal storage. The mount option in twrp does not seem to work either, trying to check data makes nothing happen. Also instead of it just launching to the bootloader directly on startup, it now gets stuck in a bootloop until you make it go into the bootloader.
As you can see i'm in quite the pickle and absolutely any help on either getting back to a functional CM or stock would be much appreciated.
The getvar all info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W903347
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4065mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.045s
If any more info is needed just ask
Click to expand...
Click to collapse
Never Go S-ON !!!!
flash this with TWRP
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/

Thanks for the replies but after a few hours of nonstop research i managed to fix the problem. I simply installed CWM because TWRP had totally crapped out on me. From there I just simply sideloaded a Viperone 4.4.2 rom and everything is working fine, don't really feel the need to return to stock anymore. Can't believe how simple that turned out to be, anyway thanks for the replies and hopefully this might help other people in the same situation.

stuck
hlo sir,I m really depressed these days bcz I can't finf ruu for my htc one as it shows
TAMPERED RELOCKED SECURITY WARNING.. my cid is VODAP021 and mied is PN071400 hboot
is 1.54 and os is 2.24.980.3... I tried to flash a guru reset with same cid no. but with slight
difference in os it was 2.24.980.2 and it showed signature verify fail......so plzzzz helpppp
meee....suggest me the perfect ruu

jaspreet4140 said:
hlo sir,I m really depressed these days bcz I can't finf ruu for my htc one as it shows
TAMPERED RELOCKED SECURITY WARNING.. my cid is VODAP021 and mied is PN071400 hboot
is 1.54 and os is 2.24.980.3... I tried to flash a guru reset with same cid no. but with slight
difference in os it was 2.24.980.2 and it showed signature verify fail......so plzzzz helpppp
meee....suggest me the perfect ruu
Click to expand...
Click to collapse
Guru reset is a rom not a ruu, so you must be bootloader unlocked to flash it via custom recovery (twrp 2.6.3.3 preferred)

stuck
@aray ,sir thnx for the quik reply....sir but I m stuck can't unlock bootloader I m s-on plz tell with which ruu I would flash my phone..send link....I would really appreciate that

jaspreet4140 said:
@aray ,sir thnx for the quik reply....sir but I m stuck can't unlock bootloader I m s-on plz tell with which ruu I would flash my phone..send link....I would really appreciate that
Click to expand...
Click to collapse
No need to use ''sir''
You can unlock bootloader, it has nothing to do with being s-on! Get you identifier token then submit it to htcdev. They will instantly send you an e-mail with your unlock_code.bin. Flash it and you'll be unlocked.
Video tutorial here
And there is no RUU for your phone so the guru reset rom is the best option.
Video tutorial to use a guru reset rom here

re
@alray,thx for showing concern n my problem...when I use command 'fastboot oem get_indentifier_token' I get msg of command error.....help

jaspreet4140 said:
@alray,thx for showing concern n my problem...when I use command 'fastboot oem get_indentifier_token' I get msg of command error.....help
Click to expand...
Click to collapse
do you have your htc drivers correctly installed on your computer and the android sdk?
When you go in windows devices manager, do you see you your phone as ''My HTC'' ?
in command prompt when you do ''fastboot devices'' does it reply your phone s/n + fastboot ?

ya I downloaded htc driveres frm xda only...but I don't hve android sdk.....
but on running fastboot devices it shows my phone serial....

stuck
@alray plzz reply me........n help mee

jaspreet4140 said:
ya I downloaded htc driveres frm xda only...but I don't hve android sdk.....
but on running fastboot devices it shows my phone serial....
Click to expand...
Click to collapse
jaspreet4140 said:
@alray plzz reply me........n help mee
Click to expand...
Click to collapse
hlo sir,I m really depressed these days bcz I can't find ruu for my htc one as it shows TAMPERED RELOCKED SECURITY WARNING.. my cid is VODAP021 and mied is PN071400 hboot is 1.54 and os is 2.24.980.3... I tried to flash a guru reset with same cid no. but with slight difference in os it was 2.24.980.2 and it showed signature verify fail......so plzzzz helpppp meee....suggest me the perfect ruus
Click to expand...
Click to collapse
could i ask you to go to your other post: http://forum.xda-developers.com/showpost.php?p=52109146&postcount=41 and remove it. (EDIT and just but "deleted" as text), let's keep it here
you can get the mini-sdk from here: http://www.androidfilehost.com/?fid=23329332407585867
extract it and put the files in a simple folder, maybe something like C:\ADB\
then you need to get bootloader unlocked using HTCdev: http://www.htcdev.com/bootloader/

Rooting, custom ROM and warranty?

Hello there all!
Recently I've switched from a Galaxy S3 to the HTC One and I'm really loving it. I have got some questions on it however. With my S3 rooting and putting custom firmware on the device was really easy. I'm sure I'll be able to root the One as well and put custom recovery and firmware on it. The question I have however, is whether it is possible to unroot and go back to stock, S-On and relock the boot loader without a trace, or rather without voiding the warranty. I really want to try out the Sense 6 Roms, but if I cannot go back to the original state of the phone and the stock firmware, I'm not sure whether I should do this. Can anyone shed light on the situation?
Thanks in advance!
Sent from my HTC One using XDA Premium 4 mobile app

daanismyname said:
Hello there all!
Recently I've switched from a Galaxy S3 to the HTC One and I'm really loving it. I have got some questions on it however. With my S3 rooting and putting custom firmware on the device was really easy. I'm sure I'll be able to root the One as well and put custom recovery and firmware on it. The question I have however, is whether it is possible to unroot and go back to stock, S-On and relock the boot loader without a trace, or rather without voiding the warranty. I really want to try out the Sense 6 Roms, but if I cannot go back to the original state of the phone and the stock firmware, I'm not sure whether I should do this. Can anyone shed light on the situation?
Thanks in advance!
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can get it back to "out of the box" state if you are able to achieve S-Off, otherwise not... can you post a "fastboot getvar all" (excluding IMEI and s/n)
Here's my guide on returning 100% back to stock including S-ON, but you need S-Off to accomplish it: http://forum.xda-developers.com/showthread.php?t=2541082

nkk71 said:
You can get it back to "out of the box" state if you are able to achieve S-Off, otherwise not... can you post a "fastboot getvar all" (excluding IMEI and s/n)
Here's my guide on returning 100% back to stock including S-ON, but you need S-Off to accomplish it: http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Thanks for the answer! This is what I get after running fastboot getvar all:
Code:
C:\Windows\system32>fastboot getvar all
(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-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4101mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
As for the S-Off, would it be possible to achieve that with Firewater? Thanks for the help.

daanismyname said:
Thanks for the answer! This is what I get after running fastboot getvar all:
Code:
C:\Windows\system32>fastboot getvar all
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
As for the S-Off, would it be possible to achieve that with Firewater? Thanks for the help.
Click to expand...
Click to collapse
i think firewater should work on that model, but i cannot confirm it! And since I'm not actively following any firewater threads, maybe best to go ask in one of them, as there have been plenty of problems with the newer phones (and yours is about as new as they come 4.19.401.11).
there is a "fastboot oem <something>" command you can run which would allow the devs to tell you if your device is supported or not, but i don't know the details unfortunately.
If this is something of crucial importance to you, I recommend you check out the various firewater and rumrunner threads (even IRC) to see if your device is supported or not.
Good Luck

nkk71 said:
i think firewater should work on that model, but i cannot confirm it! And since I'm not actively following any firewater threads, maybe best to go ask in one of them, as there have been plenty of problems with the newer phones (and yours is about as new as they come 4.19.401.11).
there is a "fastboot oem <something>" command you can run which would allow the devs to tell you if your device is supported or not, but i don't know the details unfortunately.
If this is something of crucial importance to you, I recommend you check out the various firewater and rumrunner threads (even IRC) to see if your device is supported or not.
Good Luck
Click to expand...
Click to collapse
Thank you! I'll do that.