Database Develop

hang into bootloader after the of flashing RUU

Hey Guys,
my name is Marius and I´m from Berlin/Germany.
I bought a HTC One from Vodafone.
after some a while I get root and installed Cyanogenmod.
but I wanted an Original HTC android an so I get S-OFF an SuperCID.
Then I tried to flash an Original HTC RUU bu something went wrong.
it´s back to S.On an another try.. nothing... just failure about securecheck and something like that.
when it starts up it just go to Fastboot-Mode and nothing happens.
I tried to flash CWM again but it doesnt´t work.
Tried to flash the Vodafone Firmware. it also doesn´t work.
Is there anybody, who can help me?
or is there a RUU which works with evere CID an version??
CID is back to HTC__102 becouse of the RUU try.
thanks for your help.
Marius

Phago_Z said:
Hey Guys,
my name is Marius and I´m from Berlin/Germany.
I bought a HTC One from Vodafone.
after some a while I get root and installed Cyanogenmod.
but I wanted an Original HTC android an so I get S-OFF an SuperCID.
Then I tried to flash an Original HTC RUU bu something went wrong.
it´s back to S.On an another try.. nothing... just failure about securecheck and something like that.
when it starts up it just go to Fastboot-Mode and nothing happens.
I tried to flash CWM again but it doesnt´t work.
Tried to flash the Vodafone Firmware. it also doesn´t work.
Is there anybody, who can help me?
or is there a RUU which works with evere CID an version??
CID is back to HTC__102 becouse of the RUU try.
thanks for your help.
Marius
Click to expand...
Click to collapse
What is your bootloader status? Locked or unlocked? Make sure it is locked or relocked
After that go to fastboot mode
Go to your ADB/Fastboot files map on your pc whit MSDOS
Type then this:
fastboot oem rebootRUU
wait till device is booted in ruu mode
the type fastboot flash zip xxxxx.zip
(xxxxx is the your ruu file has) (your ruu file must be a ZIP file and located in your adb folder!!!!!!!!!)
This wil work
Remeber Downgrade is only posible whit Super-cid

Phago_Z said:
Hey Guys,
my name is Marius and I´m from Berlin/Germany.
I bought a HTC One from Vodafone.
after some a while I get root and installed Cyanogenmod.
but I wanted an Original HTC android an so I get S-OFF an SuperCID.
Then I tried to flash an Original HTC RUU bu something went wrong.
it´s back to S.On an another try.. nothing... just failure about securecheck and something like that.
when it starts up it just go to Fastboot-Mode and nothing happens.
I tried to flash CWM again but it doesnt´t work.
Tried to flash the Vodafone Firmware. it also doesn´t work.
Is there anybody, who can help me?
or is there a RUU which works with evere CID an version??
CID is back to HTC__102 becouse of the RUU try.
thanks for your help.
Marius
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (remove IMEI and s/n) and a screenshot of your bootloader.

c:\SWP\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(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.054s
also also tried to flash a firmware an some diffrent RUU´s
I can´t change the cid I have S-On
Bootloader in relocked

Phago_Z said:
c:\SWP\adb>fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-main: 2.24.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
Click to expand...
Click to collapse
hboot 1.44 but firmware 2.24, hmm
1- do you have a functioning ROM? yes -> try to get s-off using revone
2- get a new unlocktocken from HTCdev and unlock your bootloader
hmmm

nkk71 said:
hboot 1.44 but firmware 2.24, hmm
1- do you have a functioning ROM? yes -> try to get s-off using revone
2- get a new unlocktocken from HTCdev and unlock your bootloader
hmmm
Click to expand...
Click to collapse
1) I can´t use revone. I cant put it to the phone.
and adb shell doesn´t work. my problem is that I cant flash any rom something else.
CWM is not available

very good message
jipiiii
its alive
thats für the tip with bootloader unlock.
after i´ve done this, it starts automaticly
I`m so happy

Phago_Z said:
jipiiii
its alive
thats für the tip with bootloader unlock.
after i´ve done this, it starts automaticly
I`m so happy
Click to expand...
Click to collapse
good, keep it unlocked until you s-off!!
"relocked" mit keinem RUU, ist absolut Sch**sse, also pass auf!
(forum rules: english): either stay unlocked, and/or get s-off. if you end up in a situation with a locked or relocked bootloader and the unlocktocken doesnt work you are STUCK!!
Ich wuerde sagen: get S-Off.

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?

[Q] Downgrading 4.3 to 4.1.2

Because i'm having bluetooth audio problems with numerous carkits/headsets i found out that going back to stock 4.1.2 resolves this problem.
The way i do this now is:
1. flash hboot 1.44
2. restore downloaded nandroid backup via CWM stock rom 1.29.401.12 for HTC__E11 (M7 CWM Nandroid Backup / CID HTC__102 / 1.29.401.12 (DE Unbranded - Thanks to FordSierra88))
after restoring touch doesn't work but use a USB Mouse
3. flash stock 1.29.401.12 recovery
4. fastboot oem lock
5. install RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
I have a feeling that i'm taking a sightseeing tour with this approach. Can i do this quicker???
Maybe via Guru reset? or RUU.zip? I understand that my CID must be stock and no Custom recovery installed and bootloader locked?
Again.. my goal is stock rom including OTA's. I stop installing OTA's after the one in the picture.
Can someone clear things up for me please?

Tranzy said:
Because i'm having bluetooth audio problems with numerous carkits/headsets i found out that going back to stock 4.1.2 resolves this problem.
The way i do this now is:
1. flash hboot 1.44
2. restore downloaded nandroid backup via CWM stock rom 1.29.401.12 for HTC__E11 (M7 CWM Nandroid Backup / CID HTC__102 / 1.29.401.12 (DE Unbranded - Thanks to FordSierra88))
after restoring touch doesn't work but use a USB Mouse
3. flash stock 1.29.401.12 recovery
4. fastboot oem lock
5. install RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
I have a feeling that i'm taking a sightseeing tour with this approach. Can i do this quicker???
Maybe via Guru reset? or RUU.zip? I understand that my CID must be stock and no Custom recovery installed and bootloader locked?
Again.. my goal is stock rom including OTA's. I stop installing OTA's after the one in the picture.
Can someone clear things up for me please?
Click to expand...
Click to collapse
"I have a feeling that i'm taking a sightseeing tour with this approach. Can i do this quicker???" :silly:
can you post a "fastboot getvar all" excluding IMEI and s/n

(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) serialno:
(bootloader) imei:
(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: 4315mV
(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.078s
wow... just noticed my signature.. i guess it needs updating

Tranzy said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
wow... just noticed my signature.. i guess it needs updating
Click to expand...
Click to collapse
go to my guide, http://forum.xda-developers.com/showthread.php?t=2541082
in RUU.ZIP method, use this ruu.zip : http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
no need to mess with UNLOCKED or TAMPERED (unless you want), and definitely do not change S-Off.
let me know if you have any questions.

nkk71 said:
go to my guide, http://forum.xda-developers.com/showthread.php?t=2541082
in RUU.ZIP method, use this ruu.zip : http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
3.62
no need to mess with UNLOCKED or TAMPERED (unless you want), and definitely do not change S-Off.
let me know if you have any questions.
Click to expand...
Click to collapse
I tried flashing Guru_Reset_M7_1.29.401.13 and ticked everything stock. Ended up with touchscreen not working and noticed that i was still on version 3.62.
I will download the zip you suggested. I takes a while to download so i will report back.

Tranzy said:
I tried flashing Guru_Reset_M7_1.29.401.13 and ticked everything stock. Ended up with touchscreen not working and noticed that i was still on version 3.62.
I will download the zip you suggested. I takes a while to download so i will report back.
Click to expand...
Click to collapse
yeah that's normal, because the touchscreen drivers were updated in 2.xx (and not backwards compatible)
you just need to use Step 2:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE
fastboot reboot-bootloader
all done, no need to mess with anything else (tampered, unlocked, S-Off), everything back to stock 1.28 and you can take OTAs to whichever version you want, or stop at 1.28
recommend you stay s-off

nkk71 said:
yeah that's normal, because the touchscreen drivers were updated in 2.xx (and not backwards compatible)
you just need to use Step 2:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE
fastboot reboot-bootloader
all done, no need to mess with anything else (tampered, unlocked, S-Off), everything back to stock 1.28 and you can take OTAs to whichever version you want, or stop at 1.28
recommend you stay s-off
Click to expand...
Click to collapse
Do i need to flash the hboot 1.44 and do i need to lock the bootloader for this to work?

Tranzy said:
Do i need to flash the hboot 1.44 and do i need to lock the bootloader for this to work?
Click to expand...
Click to collapse
I'm at work. So i will have to download this at home later on. But i need a working phone now. So i decided to give the RUU.exe file a go again. (It worked before) but it failed this time. The only thing i did was flash the 1.44 hboot again and now the rom installed nicely.
I guess the RUU.exe needs the 1.44 hboot after all? Is this correct?
Sorry but i'm fairly new to this all and i'm just trying this out following your guides and that of other. Trial and error method

Tranzy said:
I'm at work. So i will have to download this at home later on. But i need a working phone now. So i decided to give the RUU.exe file a go again. (It worked before) but it failed this time. The only thing i did was flash the 1.44 hboot again and now the rom installed nicely.
I guess the RUU.exe needs the 1.44 hboot after all? Is this correct?
Sorry but i'm fairly new to this all and i'm just trying this out following your guides and that of other. Trial and error method
Click to expand...
Click to collapse
yes correct, the RUU.exe needs a separate hboot downgrade first (if hboot is 1.55+), to allow the RUU to work.
on the other hand, the ruu.zip method does not.
End result is the same.

One "this is a test device" help - urgent

Hi guys,
I'm in need of some help, my beloved HTC One has fallen victim to the dreaded Purple Camera issue and I need to send it back.
I'm on HBOOT 1.56 and I need to turn S-ON back on as my phone says that my phone is a "Test Device" in bold red writing if you reset the phone and under About>Help
I don't want any warranty issues with HTC as being in South Africa, support is very limited as it is and they will find any excuse not to try fix it.
If anyone can give out any tips or advice I'd be happy to donate even.
I've done lots of Googling and tried a couple things but it's all for older HBOOT's than mine.
Please and thanks guys. :good:

Terros said:
Hi guys,
I'm in need of some help, my beloved HTC One has fallen victim to the dreaded Purple Camera issue and I need to send it back.
I'm on HBOOT 1.56 and I need to turn S-ON back on as my phone says that my phone is a "Test Device" in bold red writing if you reset the phone and under About>Help
I don't want any warranty issues with HTC as being in South Africa, support is very limited as it is and they will find any excuse not to try fix it.
If anyone can give out any tips or advice I'd be happy to donate even.
I've done lots of Googling and tried a couple things but it's all for older HBOOT's than mine.
Please and thanks guys. :good:
Click to expand...
Click to collapse
First, post the output of ''fastboot getvar all'' (except imei and serialno)
Do NOT S-ON for the moment.

alray said:
First, post the output of ''fastboot getvar all'' (except imei and serialno)
Do NOT S-ON for the moment.
Click to expand...
Click to collapse
Thanks for the speedy response!
This is the getvar info:
D:\htcone\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(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__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 4323mV
(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.065s

Terros said:
Thanks for the speedy response!
This is the getvar info:
D:\htcone\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(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__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 4323mV
(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.065s
Click to expand...
Click to collapse
ok so you'll need to downgrade your phone first because turning back s-on on hboot 1.56 will trigger the tampered flag in the bootloader.
use the 1.28.401.7 ruu with the guru bootloader reset tool
refer to this guide and follow instructions carefully. Again, do not s-on on hboot 1.55 and above, only do it on 1.44 or 1.54.

alray said:
First, post the output of ''fastboot getvar all'' (except imei and serialno)
Do NOT S-ON for the moment.
Click to expand...
Click to collapse
alray said:
ok so you'll need to downgrade your phone first because turning back s-on on hboot 1.56 will trigger the tampered flag in the bootloader.
use the 1.28.401.7 ruu with the guru bootloader reset tool
refer to this guide and follow instructions carefully. Again, do not s-on on hboot 1.55 and above, only do it on 1.44 or 1.54.
Click to expand...
Click to collapse
Awesome! I just downgraded to 1.44,
Can I go ahead now and use fastboot oem writesecureflag 3 to S-ON the device?
Just wanting to make 100% sure.

Terros said:
Awesome! I just downgraded to 1.44,
Can I go ahead now and use fastboot oem writesecureflag 3 to S-ON the device?
Just wanting to make 100% sure.
Click to expand...
Click to collapse
have you removed tampered and set the phone to locked, and flashed the 1.28.401.7 ruu?

nkk71 said:
have you removed tampered and set the phone to locked, and flashed the 1.28.401.7 ruu?
Click to expand...
Click to collapse
My phone still says Locked, I flashed the 1.28.401.12_hboot_1.44.zip
I haven't actually done the 1.28.401.7 RUU, Is that what I do after I flashed the 1.44 hboot?
My phone is on 4.4.2.

Terros said:
My phone still says Locked, I flashed the 1.28.401.12_hboot_1.44.zip
I haven't actually done the 1.28.401.7 RUU, Is that what I do after I flashed the 1.44 hboot?
My phone is on 4.4.2.
Click to expand...
Click to collapse
DO NOT GO S-ON
first run the RUU.EXE or the flash the RUU.ZIP
then we can consider s-on, with S-On you cannot downgrade!!! and you'll be majorly stuck.
let me know when you've done the ruu
PS: please follow the guide
1- remove tampered set locked
2- run / flash ruu 1.28.401.7
3- boot up once to make sure everything is OK, do NOT take OTA
4- go S-ON if you really need to
.

nkk71 said:
DO NOT GO S-ON
first run the RUU.EXE or the flash the RUU.ZIP
then we can consider s-on, with S-On you cannot downgrade!!! and you'll be majorly stuck.
let me know when you've done the ruu
PS: please follow the guide
1- remove tampered set locked
2- run / flash ruu 1.28.401.7
3- boot up once to make sure everything is OK, do NOT take OTA
4- go S-ON if you really need to
.
Click to expand...
Click to collapse
Ok thanks.
Is this the correct RUU > RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed?

Terros said:
Ok thanks.
Is this the correct RUU > RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed?
Click to expand...
Click to collapse
yes,
this one for RUU.EXE method: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
or this one for RUU.ZIP method: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
AFH mirror: http://www.androidfilehost.com/?fid=23329332407584993
remember to check MD5 on the download, to make sure it's not corrupt
.

nkk71 said:
yes,
this one for RUU.EXE method: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
or this one for RUU.ZIP method: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
AFH mirror: http://www.androidfilehost.com/?fid=23329332407584993
remember to check MD5 on the download, to make sure it's not corrupt
.
Click to expand...
Click to collapse
It's now updated to the RUU you listed.
What's next?

Terros said:
It's now updated to the RUU you listed.
What's next?
Click to expand...
Click to collapse
As mentioned:
1- remove tampered set locked
2- run / flash ruu 1.28.401.7
3- boot up once to make sure everything is OK, do NOT take OTA
4- go S-ON if you really need to
so if your bootloader is now:
* untampered,
* LOCKED,
* and the ruu has been successfully installed.
you can go ahead and S-On your device.
.

nkk71 said:
As mentioned:
1- remove tampered set locked
2- run / flash ruu 1.28.401.7
3- boot up once to make sure everything is OK, do NOT take OTA
4- go S-ON if you really need to
so if your bootloader is now:
* untampered,
* LOCKED,
* and the ruu has been successfully installed.
you can go ahead and S-On your device.
.
Click to expand...
Click to collapse
All still LOCKED and installed RUU. So now S-OFF with the writebootflag 3 or what ever correct.

Terros said:
All still LOCKED and installed RUU. So now S-OFF with the writebootflag 3 or what ever correct.
Click to expand...
Click to collapse
You mean S-On, right.
to go s-on: fastboot oem writesecureflag 3

Flashing Stock Rom

i want to flash stock rom for my htc one m7. i have an unlocked bootloader.I have read that to flash the stock ruu files(.exe) [not the .zip files], we need to lock the bootloader.Is it true?what will happen if i flash the ruu while having my bootloader unlocked?
*i dont want to relock my bootloader because i will root my phone again after having everything back to stock.i have the proper ruu file for my phone.Please do reply!

$urajM said:
i want to flash stock rom for my htc one m7. i have an unlocked bootloader.I have read that to flash the stock ruu files(.exe) [not the .zip files], we need to lock the bootloader.Is it true?what will happen if i flash the ruu while having my bootloader unlocked?
*i dont want to relock my bootloader because i will root my phone again after having everything back to stock.i have the proper ruu file for my phone.Please do reply!
Click to expand...
Click to collapse
If your phone is S-ON you must relock the BL to flash a RUU. What will happen if you don't? SImple, the RUU won't flash. Just unlock the BL again after flashing the RUU.

I forgot to mention i have s-off. Can i flash the .exe ruu with an unlocked bootloader then? I just wondered why these files dont flash with an unlocked bootloader..

alray said:
If your phone is S-ON you must relock the BL to flash a RUU. What will happen if you don't? SImple, the RUU won't flash. Just unlock the BL again after flashing the RUU.
Click to expand...
Click to collapse
I have s-off

$urajM said:
I forgot to mention i have s-off. Can i flash the .exe ruu with an unlocked bootloader then? I just wondered why these files dont flash with an unlocked bootloader..
Click to expand...
Click to collapse
If your phone is S-OFF you don't need to relock the bootloader to flash a RUU (exe or zip).
When S-On you can only flash signed file and this signature verification can only be done by your phone with a locked (or relocked) bootloader hence the requirement to relock the BL if your phone is S-ON.

alray said:
If your phone is S-OFF you don't need to relock the bootloader to flash a RUU (exe or zip).
When S-On you can only flash signed file and this signature verification can only be done by your phone with a locked (or relocked) bootloader hence the requirement to relock the BL if your phone is S-ON.
Click to expand...
Click to collapse
Thanxks ,it ihelped a lot.

By the way do i need to have a superCID to flash rom or ruu of any region or is having an unlocked botloader with s-off sufficient?

$urajM said:
By the way do i need to have a superCID to flash rom or ruu of any region or is having an unlocked botloader with s-off sufficient?
Click to expand...
Click to collapse
Both CID and MID must be compatible for the RUU. CID and MID can be changed with S-OFF.
You can also decrypt the RUU and change the android-info.txt file so it match your CID/MID

alray said:
Both CID and MID must be compatible for the RUU. CID and MID can be changed with S-OFF.
You can also decrypt the RUU and change the android-info.txt file so it match your CID/MID
Click to expand...
Click to collapse
Thanks

alray said:
If your phone is S-OFF you don't need to relock the bootloader to flash a RUU (exe or zip).
When S-On you can only flash signed file and this signature verification can only be done by your phone with a locked (or relocked) bootloader hence the requirement to relock the BL if your phone is S-ON.
Click to expand...
Click to collapse
The links you have provided for htc one m7_u ,the one for my phone is not there. My OS is 7.21.707.151.
Can you provide me link? Also my bootloader info for more info-
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA^%$&*%#04
(bootloader) imei: 354435(*&^@
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4093mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

$urajM said:
The links you have provided for htc one m7_u ,the one for my phone is not there.
Click to expand...
Click to collapse
What links? I dont remember providing you with any link.
My OS is 7.21.707.151. Can you provide me link?
Click to expand...
Click to collapse
This is the RUU for 7.21.707.151
https://androidfilehost.com/?fid=312968873555002347
Also my bootloader info for more info-
Click to expand...
Click to collapse
You said at post #4 your phone was S-OFF but your "fastboot-getvar all" output is clearly showing that your phone is S-ON. Not really a problem but you'll need to relock bootloader before flashing, just so you know.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA^%$&*%#04
(bootloader) imei: 354435(*&^@
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4093mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse

alray said:
What links? I dont remember providing you with any link.
This is the RUU for 7.21.707.151
https://androidfilehost.com/?fid=312968873555002347
You said at post #4 your phone was S-OFF but your "fastboot-getvar all" output is clearly showing that your phone is S-ON. Not really a problem but you'll need to relock bootloader before flashing, just so you know.
Click to expand...
Click to collapse
The thing is in every post tat the bottom there is a tab that says says show hidden contents and there were some ruu links for htc one m7.Anyways, the thing is I brought my phone back to s-on as I was having a hard time finding the correct ruu for my phone and when you s-on the phone only the correct and latest ruu can be flushed .What I mean is that no wrong ruu can be flushed.But as soon as I s-on ed my phone ,I paniced as I was having a very hard time finding the latest ruu .So I posted the same things in both the threads in a panic which I am sorry for .I didn't know about that rule.Basiclly in this thread I wanted the latest ruu link for my phone. What I meant in the other thread was for someone to explain the version of my phone for the getvar all command so that I could identify my ruu easily.i was confused in many terms like "wwwe", .zip and .ruu. I will change my question in the other thread.
Anyways thanks for replying and giving the link.I just wanted to confirm that the link you provided will work for my indian edition ,right?Also, not that I am complaing but do you happen to know the link for the .ruu ( not the .zip) for the same? Thanks.

$urajM said:
The thing is in every post tat the bottom there is a tab that says says show hidden contents and there were some ruu links for htc one m7.
Click to expand...
Click to collapse
I Forgot about these links, they are added to all my posts automatically
Anyways, the thing is I brought my phone back to s-on as I was having a hard time finding the correct ruu for my phone and when you s-on the phone only the correct and latest ruu can be flushed .
Click to expand...
Click to collapse
I understand what you mean but it's always a bad idea to go back S-On, it can even brick your phone in the some situations (I.e going back S-On with an unsigned bootloader will brick)
Anyways thanks for replying and giving the link.I just wanted to confirm that the link you provided will work for my indian edition ,right?Also, not that I am complaing but do you happen to know the link for the .ruu ( not the .zip) for the same? Thanks.
Click to expand...
Click to collapse
This ruu is the only one that should work on your phone now that it's back S-On. If this one doesn't work, you're SOL (because S-On).
Ruu are rarely available in exe file, most of them are zip file and they must be flashed using htc_fastboot.exe from a Windows pc with the phone booted in RUU mode:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip your_ruu_file_name.zip
htc_fastboot reboot

pl don t panic. it is easy
I showed you 4.4.3 but as my idea latest build is better than old
https://forum.xda-developers.com/htc-one/development/help-selecting-correct-stock-rom-t3879097/page2

S-off
I can no longer s-off using rumrunner. I did some research and found that htc patched hboot 1.56 and above.The only solution i found is sunshine. ALso i found some posts saying that they were able to s-off by using custom roms with unsecure kernels and unsecure boot img. So just wanted to know whether they work for hboot 1.61 or do i use sunshine if i want to s-off again?
I mean is there even a slight chance that using unsecured kernels and boot imgs i can get s-off or are all of those posts lies?

$urajM said:
I can no longer s-off using rumrunner. I did some research and found that htc patched hboot 1.56 and above.The only solution i found is sunshine. ALso i found some posts saying that they were able to s-off by using custom roms with unsecure kernels and unsecure boot img. So just wanted to know whether they work for hboot 1.61 or do i use sunshine if i want to s-off again?
I mean is there even a slight chance that using unsecured kernels and boot imgs i can get s-off or are all of those posts lies?
Click to expand...
Click to collapse
You don't need s-off to flash the latest ruu version matching your cid/mid (the one linked in my last post), you only need s-off if you want to downgrade or if you want to convert your phone to another carrier/region version.
Only sunshine will hboot 1.57/1.61 security to off (s-off)
And FYI, "boot" = "kernel" these are not 2 different things