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
Related
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?
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.
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
I have had at least 7 android phones where flashing stock was never such a hassle or maybe it's just me who finds htc one flashing a lot trickier than other phones.
I am totally confused how i can flash a sense 6 RUU as I am still sitting on 4.3 sense 5.5 and I have a feeling that the kk on htc one is a lot better than 4.3. Please enlighten me.
1. Unlock bootloader @ HTCdev.
2. Flash a custom recovery.
3. Flash a Sense 6 / KK rom.
Remember with S-On devices, you need to flash the custom roms boot.img from fastboot.
AndroHero said:
1. Unlock bootloader @ HTCdev.
2. Flash a custom recovery.
3. Flash a Sense 6 / KK rom.
Remember with S-On devices, you need to flash the custom roms boot.img from fastboot.
Click to expand...
Click to collapse
Yeah, I want to stay stock and not unlock the bootloader. Is there a way to flash a RUU without unlocking and S-OFF etc?
shad0wboss said:
Yeah, I want to stay stock and not unlock the bootloader. Is there a way to flash a RUU without unlocking and S-OFF etc?
Click to expand...
Click to collapse
Yeah of course, but you have to flash the correct RUU for your devices CID!
If you want to keep stock, you're better waiting 'till your carrier pushes the OTA to your device.
AndroHero said:
Yeah of course, but you have to flash the correct RUU for your devices CID!
If you want to keep stock, you're better waiting 'till your carrier pushes the OTA to your device.
Click to expand...
Click to collapse
is there any other way, to unlock the bootloader rather than from htcdev cuz then they know that i've unlocked my bootloader, right?
shad0wboss said:
is there any other way, to unlock the bootloader rather than from htcdev cuz then they know that i've unlocked my bootloader, right?
Click to expand...
Click to collapse
I've read that if you S-Off your device, there's a way to revert the bootloader to say locked rather than relocked. But it's something i've never tried....
AndroHero said:
Remember with S-On devices, you need to flash the custom roms boot.img from fastboot.
Click to expand...
Click to collapse
Not for the M7, boot.img is not secured.
---------- Post added at 08:17 AM ---------- Previous post was at 08:16 AM ----------
shad0wboss said:
is there any other way, to unlock the bootloader rather than from htcdev cuz then they know that i've unlocked my bootloader, right?
Click to expand...
Click to collapse
post the output of "fastboot getvar all" except IMEI and serialno
alray said:
Not for the M7, boot.img is not secured.
---------- Post added at 08:17 AM ---------- Previous post was at 08:16 AM ----------
post the output of "fastboot getvar all" except IMEI and serialno
Click to expand...
Click to collapse
c:\adb>fastboot getvar all
< waiting for device >
(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-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: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.053s
shad0wboss said:
c:\adb>fastboot getvar all
< waiting for device >
(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-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: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.053s
Click to expand...
Click to collapse
In theory you should have received updates for that version, latest one is 6.09.401.5 (sense 6 and android 4.4.3) Are you sure you are still on stock rom?
With S-ON + locked bootloader, you can only flash RUU same or higher version that match your CID, MID and version base (.401). The latest RUU available for your phone is 4.19.401.9
With S-OFF you can flash every RUU version you want + you can flash OTA updates manually
alray said:
In theory you should have received updates for that version, latest one is 6.09.401.5 (sense 6 and android 4.4.3) Are you sure you are still on stock rom?
With S-ON + locked bootloader, you can only flash RUU same or higher version that match your CID, MID and version base (.401). The latest RUU available for your phone is 4.19.401.9
With S-OFF you can flash every RUU version you want + you can flash OTA updates manually
Click to expand...
Click to collapse
well well well, I just checked and there's an update, 4.4.2.
Do you think that I should update this or are there battery or other stability issues with 4.4.2
shad0wboss said:
well well well, I just checked and there's an update, 4.4.2.
Do you think that I should update this or are there battery or other stability issues with 4.4.2
Click to expand...
Click to collapse
go ahead with the update.
-Just a side note, I know you don't wish to unlock or s-off but if you ever wants to s-off, it will become harder with each ota updates (s-off exploit are patched with OTA). So if you want to s-off, do it now it will be easier. If you dont want S-OFF, proceed with the update.
---------- Post added at 09:25 AM ---------- Previous post was at 09:22 AM ----------
and check updates again after applying this one, you'll probably get prompted to install 1 or 2 more
alray said:
go ahead with the update.
-Just a side note, I know you don't wish to unlock or s-off but if you ever wants to s-off, it will become harder with each ota updates (s-off exploit are patched with OTA). So if you want to s-off, do it now it will be easier. If you dont want S-OFF, proceed with the update.
---------- Post added at 09:25 AM ---------- Previous post was at 09:22 AM ----------
and check updates again after applying this one, you'll probably get prompted to install 1 or 2 more
Click to expand...
Click to collapse
So with S-off, i can flash any RUU, even if I want to downgrade? Also can i do it without unlocking the bootloader.
If so, can you direct me towards the procedure?
shad0wboss said:
So with S-off, i can flash any RUU, even if I want to downgrade? Also can i do it without unlocking the bootloader.
If so, can you direct me towards the procedure?
Click to expand...
Click to collapse
yes you can flash any RUU with s-off: signed ruu, decrypted ruu, lower/higher version, other version ruu (require to change CID/MID)
you will need to unlock bootloader to s-off
unlock bootloader
flash twrp recovery
root
flash an unsecured kernel or flash a custom rom pre-rooted that comes with an unsecured kernel
s-off using rumrunner
With s-off, you can set back to bootloader to LOCKED (not relocked) like if it was never unlocked and you can remove the TAMPERED flag from bootloader.
alray said:
yes you can flash any RUU with s-off: signed ruu, decrypted ruu, lower/higher version, other version ruu (require to change CID/MID)
you will need to unlock bootloader to s-off
unlock bootloader
flash twrp recovery
root
flash an unsecured kernel or flash a custom rom pre-rooted that comes with an unsecured kernel
s-off using rumrunner
With s-off, you can set back to bootloader to LOCKED (not relocked) like if it was never unlocked and you can remove the TAMPERED flag from bootloader.
Click to expand...
Click to collapse
can you link me to the best and user friendly method here on xda for all that?
shad0wboss said:
can you link me to the best and user friendly method here on xda for all that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one#root
http://forum.xda-developers.com/showthread.php?t=2488772
Hi everyone, I apologies if this is a bit of a silly question however I am attempting to root an android device for the first time and would just like to know what you thought about an issue which I am having.
My question is, I plan to root my phone and install TWRP recovery, if I ever needed to unroot I am under the impression I would need an RUU which matches the radio very I have. The details of the radio is 4T.29.3218.08 and the phone is from the UK (Europe). I cannot find this version anywhere. If I ever needed to unroot does this mean I would not be able to?
This is the only thing which is now stopping me from rooting my phone... Thank you in advance for your replies.
ashyk36 said:
Hi everyone, I apologies if this is a bit of a silly question however I am attempting to root an android device for the first time and would just like to know what you thought about an issue which I am having.
My question is, I plan to root my phone and install TWRP recovery, if I ever needed to unroot I am under the impression I would need an RUU which matches the radio very I have. The details of the radio is 4T.29.3218.08 and the phone is from the UK (Europe). I cannot find this version anywhere. If I ever needed to unroot does this mean I would not be able to?
This is the only thing which is now stopping me from rooting my phone... Thank you in advance for your replies.
Click to expand...
Click to collapse
post the output of "fastboot getvar all" except your imei and serialno. Radio version doesn't help much when trying to find a RUU
alray said:
post the output of "fastboot getvar all" except your imei and serialno. Radio version doesn't help much when trying to find a RUU
Click to expand...
Click to collapse
Hi, the details are as follows:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.10
(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__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4095mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
ashyk36 said:
Hi, the details are as follows:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.10
(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__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4095mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
Click to expand...
Click to collapse
your on the newest software their is no 6.x.401 RUU
to return to stock you simply flash the stock odex rom and stock recovery / do a factory reset and your Stock
you would still have an unlocked bootloader but without s-off you can't fix that (unlocked to locked)
clsA said:
your on the newest software their is no 6.x.401 RUU
to return to stock you simply flash the stock odex rom and stock recovery / do a factory reset and your Stock
you would still have an unlocked bootloader but without s-off you can't fix that (unlocked to locked)
Click to expand...
Click to collapse
So a couple of questions. Does that mean there is never going to be an RUU for my phone or is it just with time there will be more for the current version? As for flashing to the odex Rom and stock recovery, the Rom would be simple enough for TWRP recovery, how would i do the stock recovery part? Or would they be an all in one installation, installing the Rom would also install the recovery?
Thank you for your help
ashyk36 said:
So a couple of questions. Does that mean there is never going to be an RUU for my phone or is it just with time there will be more for the current version?
Click to expand...
Click to collapse
HTC doesn't release RUU each time there is a new version. Maybe with the future release of android lollipop, we don't know.
As for flashing to the odex Rom and stock recovery, the Rom would be simple enough for TWRP recovery, how would i do the stock recovery part?
Click to expand...
Click to collapse
flash the stock rom using twrp and then flash the stock recovery the same way you have flashed twrp recovery. Twrp will be overwritten by the stock recovery.
Just keep in mind that you'll need s-off if you want your warranty back (to set the bootloader back to *locked* (not relocked) and to remove the *tampered* flag)
alray said:
HTC doesn't release RUU each time there is a new version. Maybe with the future release of android lollipop, we don't know.
flash the stock rom using twrp and then flash the stock recovery the same way you have flashed twrp recovery. Twrp will be overwritten by the stock recovery.
Just keep in mind that you'll need s-off if you want your warranty back (to set the bootloader back to *locked* (not relocked) and to remove the *tampered* flag)
Click to expand...
Click to collapse
Hi thank you for your help. Just want to clarify, where would i get these stock files from and will ineed specific versions for my phone?
Were these the correct files?
http://forum.xda-developers.com/showthread.php?t=2224752
@alray if i was to keep a backup of my stock rom before i installed a custom rom, could i then restore the backup of the stock rom and then restore the stock recovery?
Where can i get the stock recovery from? Once i find it is possible i can then root
ashyk36 said:
Were these the correct files?
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
no, you are on 6.09.401.10, these files are for 6.09.401.5.
---------- Post added at 04:48 PM ---------- Previous post was at 04:45 PM ----------
ashyk36 said:
@alray if i was to keep a backup of my stock rom before i installed a custom rom, could i then restore the backup of the stock rom and then restore the stock recovery?
Click to expand...
Click to collapse
Yes but if you make a backup of your rom after unlocking the bootloader, there will be some files missing (htc preloaded apps in /data/preload) which will prevent you to use ota updates is you restore this backup. There is a 6.09.401.10 nandroid backup including the /data/preload folder on android file host.
https://www.androidfilehost.com/?fid=95832962473396068
Where can i get the stock recovery from? Once i find it is possible i can then root
Click to expand...
Click to collapse
You can extract it from any 6.09.401.10 firmware or from the 6.09.401.5 to 6.09.401.10 ota zip file.
nvm, I found it here: https://www.androidfilehost.com/?fid=95784891001603803
@alray - So my steps to stock would be:
Download and install the rom using TWRP recoveryfrom the following address:
https://www.androidfilehost.com/?fid=95832962473396068
Then install the stock recovery from the following link (Install is the same way I installed TWRP):
https://www.androidfilehost.com/?fid=95784891001603803
If the phone is still S-ON, I will not be able to change the label so will have to make it S-OFF if I need to change - just out of curiosity, if I leave the phone S-ON will this affect OTA updates?
Then factory reset the phone - I should be back to a stock phone.
Would these steps be correct?
ashyk36 said:
@alray - So my steps to stock would be:
Download and install restore (its a backup, you restore it using the restore menu in twrp, do not install like a rom) the rom using TWRP recoveryfrom the following address:
https://www.androidfilehost.com/?fid=95832962473396068
Then install the stock recovery from the following link (Install is the same way I installed TWRP):
https://www.androidfilehost.com/?fid=95784891001603803
yes:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot
If the phone is still S-ON, I will not be able to change the label so will have to make it S-OFF if I need to change Exactly - just out of curiosity, if I leave the phone S-ON will this affect OTA updates? No, if you rom is 100% stock (which will be the case after restoring the above backup) and you have stock recovery, youre good for ota update. S-ON/S-OFF doesn't affect ota updates.
Then factory reset the phone - I should be back to a stock phone.
Would these steps be correct?
Click to expand...
Click to collapse
see text in red above
@alray
Thank you so much for your help. I Will go ahead and root my phone.
How to S-Off
alray said:
see text in red above
Click to expand...
Click to collapse
My phone has hit the purple tint issue which is a well known fault. I have spoken to HTC and they have said that they will fix under warranty. I need to return the phone back to stock. I know I can use the nandroid backup and the recovery in the post above but I am very confused on how to S-off.
My problem is there are so many guides (some of them being very old) on how to do this and I do not know which method to use. Could someone please point me in the right direction so I can return my phone back to stock.
Thank you so much
I have seen
http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
Would this be ok? I used an article on the same website to root
ashyk36 said:
My phone has hit the purple tint issue which is a well known fault. I have spoken to HTC and they have said that they will fix under warranty. I need to return the phone back to stock. I know I can use the nandroid backup and the recovery in the post above but I am very confused on how to S-off.
My problem is there are so many guides (some of them being very old) on how to do this and I do not know which method to use. Could someone please point me in the right direction so I can return my phone back to stock.
Thank you so much
I have seen
http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
Would this be ok? I used an article on the same website to root
Click to expand...
Click to collapse
I would highly recommend to follow nkk71's super guide (linked in my signature). Everything is well explained in details, just make sure to read everything before beginning and also read the FAQ of his guide.
To achieve s-off, you will need to use Sunshine if your hboot is 1.57 or above. Sunshine cost 25$ USD. Its the only method to achieve s-off on hboot 1.54 and above.
S-OFF is a must to remove the tampered banner and set back the bootloader to ***LOCKED*** (not ***RE-LOCKED***) so your warranty is still valid, but again everything explained in that guide. If you have any question you can ask here or in nkk71's guide. If you have questions, post an updated "fastboot getvar all" at the same time.
alray said:
I would highly recommend to follow nkk71's super guide (linked in my signature). Everything is well explained in details, just make sure to read everything before beginning and also read the FAQ of his guide.
To achieve s-off, you will need to use Sunshine if your hboot is 1.57 or above. Sunshine cost 25$ USD. Its the only method to achieve s-off on hboot 1.54 and above.
S-OFF is a must to remove the tampered banner and set back the bootloader to ***LOCKED*** (not ***RE-LOCKED***) so your warranty is still valid, but again everything explained in that guide. If you have any question you can ask here or in nkk71's guide. If you have questions, post an updated "fastboot getvar all" at the same time.
Click to expand...
Click to collapse
I believe my phone has Hboot version 1.57. Is there no way I can downgrade or is sunshine the only way to return to stock? The details of the getvar all are:
C:\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.10
(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__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3981mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
alray said:
I would highly recommend to follow nkk71's super guide (linked in my signature). Everything is well explained in details, just make sure to read everything before beginning and also read the FAQ of his guide.
To achieve s-off, you will need to use Sunshine if your hboot is 1.57 or above. Sunshine cost 25$ USD. Its the only method to achieve s-off on hboot 1.54 and above.
S-OFF is a must to remove the tampered banner and set back the bootloader to ***LOCKED*** (not ***RE-LOCKED***) so your warranty is still valid, but again everything explained in that guide. If you have any question you can ask here or in nkk71's guide. If you have questions, post an updated "fastboot getvar all" at the same time.
Click to expand...
Click to collapse
The guide is really good, just one thing has thrown me though, Im not too sure which RUU to use.
I can see RUU for:
CID HTC__001
and MID PN0710000
but not baseband 4T.29.3218.08
Do I just use the files you linked me to in the posts above?
ashyk36 said:
Is there no way I can downgrade or is sunshine the only way to return to stock?
Click to expand...
Click to collapse
Downgrading requires s-off, s-off can only be achieved using Sunshine when hboot is 1.57 or newer
ashyk36 said:
The guide is really good, just one thing has thrown me though, Im not too sure which RUU to use.
I can see RUU for:
CID HTC__001
and MID PN0710000
but not baseband 4T.29.3218.08
Do I just use the files you linked me to in the posts above?
Click to expand...
Click to collapse
1.28.401.7 RUU zip
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
Baseband version is irrelevant when looking for RUUs. You want a ruu that match your CID, MID and firmware base (.401). Also you need the ruu to be hboot 1.44 (1.xx.xxx.x) so you can safely remove the tampered banner. So in our case you must use the 1.28.401.7 ruu.zip.
alray said:
Downgrading requires s-off, s-off can only be achieved using Sunshine when hboot is 1.57 or newer
1.28.401.7 RUU zip
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
Baseband version is irrelevant when looking for RUUs. You want a ruu that match your CID, MID and firmware base (.401). Also you need the ruu to be hboot 1.44 (1.xx.xxx.x) so you can safely remove the tampered banner. So in our case you must use the 1.28.401.7 ruu.zip.
Click to expand...
Click to collapse
Just so I know for the future, I know my firmware base is .401 based on the following line:
(bootloader) version-main: 6.09.401.10
Is this right? Thank you for your help!
ashyk36 said:
Just so I know for the future, I know my firmware base is .401 based on the following line:
(bootloader) version-main: 6.09.401.10
Is this right? Thank you for your help!
Click to expand...
Click to collapse
Right and also because your CID and MID are HTC__001 and PN0710000 so the corresponding software/firmware base is x.xx.401.x