Hi there,
I´ve got a problem/question about the firmware upgrade to the newest 4.06.1540.3 one. My device is S-On and on 3.62.401.1 at the moment. As written in most guides, you need to s-off your device to flash a new firmware, but my last firmware-upgrade to 3.62.401.1 worked on s-on, when i followed this tutorial: http://forum.xda-developers.com/showthread.php?t=2182823 (you should relock bootloader and then flash firmware.zip) I first tried to flash the 4.06.1540.3.zip like on s-off following Vomer´s guide [ http://forum.xda-developers.com/showthread.php?t=2365506 ], from which i also downloaded that custom zip ( http://d-h.st/Uz6 ). But during both flashing"kinds" (S-on and s-off style), i got the same error in cmd:
C:\HTCONE\Toolkit 2.0 - Squabbi>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28021 KB)...
OKAY [ 2.740s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.255s
Click to expand...
Click to collapse
So is there a way, maybe to modify that firmware to work on s-on, or is such a zip downloadable ? or do i have to switch to s-off to upgrade to the new kitkat firmware ??? THX in advance
P.s.:
C:\HTCONE\Toolkit 2.0 - Squabbi>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-ON
(bootloader) serialno: XXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(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: 4319mV
(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.069s
Click to expand...
Click to collapse
I locked my bootloader, that´s the status quo.... please help! :good: :good:
Hans_Schlila said:
Hi there,
I´ve got a problem/question about the firmware upgrade to the newest 4.06.1540.3 one. My device is S-On and on 3.62.401.1 at the moment. As written in most guides, you need to s-off your device to flash a new firmware, but my last firmware-upgrade to 3.62.401.1 worked on s-on, when i followed this tutorial: http://forum.xda-developers.com/showthread.php?t=2182823 (you should relock bootloader and then flash firmware.zip) I first tried to flash the 4.06.1540.3.zip like on s-off following Vomer´s guide [ http://forum.xda-developers.com/showthread.php?t=2365506 ], from which i also downloaded that custom zip ( http://d-h.st/Uz6 ). But during both flashing"kinds" (S-on and s-off style), i got the same error in cmd:
So is there a way, maybe to modify that firmware to work on s-on, or is such a zip downloadable ? or do i have to switch to s-off to upgrade to the new kitkat firmware ??? THX in advance
P.s.:
I locked my bootloader, that´s the status quo.... please help! :good: :good:
Click to expand...
Click to collapse
just use rumrunner to s-off then flash any firmware you like
the error was because your CID and MID do not match those in the firmware
you should also edit your post and remove your serial no and IEMI
You should also make note that once your phone is s-off it will be possible to Brick the phone if you don't flash correctly. Be sure to follow any guides you use Exactly as they say. And be sure the file you flash is for your phone. It's also highly recommended to keep s-off once you have it never go s-on
clsA said:
just use rumrunner to s-off then flash any firmware you like
the error was because your CID and MID do not match those in the firmware
you should also edit your post and remove your serial no and IEMI
Click to expand...
Click to collapse
Thank you VERY much, for quick reply, i´ll do that...
Hans_Schlila said:
Thank you VERY much, for quick reply, i´ll do that...
Click to expand...
Click to collapse
your welcome .. I also added more to my post above your's
clsA said:
You should also make note that once your phone is s-off it will be possible to Brick the phone if you don't flash correctly. Be sure to follow any guides you use Exactly as they say. And be sure the file you flash is for your phone. It's also highly recommended to keep s-off once you have it never go s-on
Click to expand...
Click to collapse
So when i have gone s-off, there is no way back to s-on in case of warranty purposes, e.g. to run an ruu.exe?
Hans_Schlila said:
So when i have gone s-off, there is no way back to s-on in case of warranty purposes, e.g. to run an ruu.exe?
Click to expand...
Click to collapse
yes you can but it's not recommended and RUU works great with s-off
clsA said:
yes you can but it's not recommended and RUU works great with s-off
Click to expand...
Click to collapse
Not recommended because of brick risk?
Hans_Schlila said:
Not recommended because of brick risk?
Click to expand...
Click to collapse
s-on a phone with modified hboot = brick
You can s-on after running a RUU without risk.
Other than that the dangers of s-on are only it can be difficult to get s-off back. You only need to search the forums for all the bonuses of having s-off.
Related
S on
Hboot 1.55
Main version 3.62.401.1
Cid htc_001 europe
I don't care tamperd and relocked and I don't want to s off
Only I want is stock phone and ota ok
So can I simply use ruu 1.29.401.1it will lead mee to jb4.1?
And while using Mike's guide 1 method with s on am I at complete stock ?
And even 2 method doesn't say about s off?
Help plss
shurahbil said:
S on
Hboot 1.55
Main version 3.62.401.1
Cid htc_001 europe
I don't care tamperd and relocked and I don't want to s off
Only I want is stock phone and ota ok
So can I simply use ruu 1.29.401.1it will lead mee to jb4.1?
And while using Mike's guide 1 method with s on am I at complete stock ?
And even 2 method doesn't say about s off?
Help plss
Click to expand...
Click to collapse
shurahbil said:
can I simply use ruu 1.29.401.1it will lead mee to jb4.1?
Click to expand...
Click to collapse
No, because you need to downgrade to hboot 1.44 to run this ruu and this require s-off
If you don't want to go s-off, you can restore stock rom and recovery by flashing that rom:
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Can I receive ota by flashing that rom?
Am I at 100% stock
shurahbil said:
Can I receive ota by flashing that rom?
Am I at 100% stock
Click to expand...
Click to collapse
Yes and Yes, you have to select "stock recovery" when installing the Guru Reset for OTAs to install properly.
BTW: there's nothing newer than 3.62 at the moment
Give me link nkk
shurahbil said:
Give me link nkk
Click to expand...
Click to collapse
1- can you please post a "fastboot getvar all" (remove IMEI and s/n)
2- confirm you're unlocked
3- which recovery do you have
nkk71 said:
1- can you please post a "fastboot getvar all" (remove IMEI and s/n)
2- confirm you're unlocked
3- which recovery do you have
Click to expand...
Click to collapse
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55
(bootloader) version-baseband: 4A.21.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S
(bootloader) serialno: FA35WW902409
(bootloader) imei: 354436058606037
(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: 4261mV
(bootloader) partition-layout: Generi
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dir
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
bootloader relocked
stock recoveryy
used system dump guide of mike 1986
i have used system dump to go back to stock
http://forum.xda-developers.com/showthread.php?t=2224752
see this is the link of system dump
http://forum.xda-developers.com/showthread.php?t=2265618
an this is mikes guide back to stock see last part of poST
1 METHOD OF GOING BACK TO STOCK
"SO I JUST WANT TO CONFIRM THAT THESE ALL THINGS I HAVE DONE WITH S-ON
SO AM I AT 100% STOCK WITHOUT RESPECT TO TAMPERED AND RELOCKED TAG"
AND WILL I RECIEVE OTA FURTHER
shurahbil said:
C:\android>fastboot getvar all
(bootloader) version-bootloader: 1.55
(bootloader) version-baseband: 4A.21.
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
bootloader relocked
stock recoveryy
used system dump guide of mike 1986
Click to expand...
Click to collapse
shurahbil said:
i have used system dump to go back to stock
http://forum.xda-developers.com/showthread.php?t=2224752
see this is the link of system dump
http://forum.xda-developers.com/showthread.php?t=2265618
an this is mikes guide back to stock see last part of poST
1 METHOD OF GOING BACK TO STOCK
"SO I JUST WANT TO CONFIRM THAT THESE ALL THINGS I HAVE DONE WITH S-ON
SO AM I AT 100% STOCK WITHOUT RESPECT TO TAMPERED AND RELOCKED TAG"
AND WILL I RECIEVE OTA FURTHER
Click to expand...
Click to collapse
a- edit your post and remove IMEI and s/n
b- would have been nice to include all the output of getvar (you cut off after some 30 characters or so), so couldn't see if s-on or s-off
(bootloader) version-misc: PVT SHIP S
Click to expand...
Click to collapse
, i'll assume s-on
c- bootloader relocked
so here it goes
WITHOUT RESPECT TO TAMPERED AND RELOCKED TAG
Click to expand...
Click to collapse
1- unlock bootloader again
2- flash custom recovery again
3- install this rom using custom recovery: http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
----> select WIPE, select "stock recovery", root and radio are up to you
you're all done, you will receive OTAs without any problems.
* You do not need to lock or relock bootloader, you can if you want but it's not necessary.
* if you choose root, then you may (or may not) loose it after OTAs, but it will not affect the OTA upgrade.
Hope that helps.
listen one more problrm i have deleted data of google service framework
someone told that by doing this u will recieve ota
now i knew its all fake
now my google apps is giving problem and even app
now how should i install google service framework properlyy????????
shurahbil said:
listen one more problrm i have deleted data of google service framework
someone told that by doing this u will recieve ota
now i knew its all fake
now my google apps is giving problem and even app
now how should i install google service framework properlyy????????
Click to expand...
Click to collapse
reflash the same rom, without selecting wipe (known as a "dirty flash").
there are no OTAs after 3.62 at the moment, and when they become available they'll work fine without messing with google services.
Hello,
i think i have a big problem. After the One of my brother did a provider update, it froze in the update process and it boot loops. I can access it via fastboot but not with adb. But with another One adb is no problem, that confuses me quite a bit.
I unlocked it with htcdev and installed twrp 2.7.0.0.
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno: 11111111111111
imei: 1111111111111111
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__102
battery-status: good
battery-voltage: 3962mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
I tried the following RUU locked and relocked:
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
But it failed with Error code 155. I really don't know what to do now.
dre-z said:
Hello,
i think i have a big problem. After the One of my brother did a provider update, it froze in the update process and it boot loops. I can access it via fastboot but not with adb. But with another One adb is no problem, that confuses me quite a bit.
I unlocked it with htcdev and installed twrp 2.7.0.0.
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno: 11111111111111
imei: 1111111111111111
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__102
battery-status: good
battery-voltage: 3962mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
I tried the following RUU locked and relocked:
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
But it failed with Error code 155. I really don't know what to do now.
Click to expand...
Click to collapse
Ahh, that RUU will not work because its for an older HBOOT version. That's for HBOOT 1.44, yours is on 1.55
So, u cannot use that RUU.
U will need to update the HBOOT to 1.56 and use this RUU:
http://www.htc1guru.com/2014/03/android-ruu-europe/
Plus, lock the bootloader before using the RUU. RUU will give an error if u have an unlocked bootloader
raghav kapur said:
Ahh, that RUU will not work because its for an older HBOOT version. That's for HBOOT 1.44, yours is on 1.55
So, u cannot use that RUU.
U will need to update the HBOOT to 1.56 and use this RUU:
http://www.htc1guru.com/2014/03/android-ruu-europe/
Plus, lock the bootloader before using the RUU. RUU will give an error if u have an unlocked bootloader
Click to expand...
Click to collapse
:good:
But i can't flash the hboot 1.56 without S-off, can't i? Adb is also not working :\
Everytime i try to flash the hboot i get:
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (24681 KB)...
OKAY [ 2.310s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 2.574s
dre-z said:
But i can't flash the hboot 1.56 without S-off, can't i? Adb is also not working :\
Everytime i try to flash the hboot i get:
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (24681 KB)...
OKAY [ 2.310s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 2.574s
Click to expand...
Click to collapse
I think ur flashing the wrong firmware. As far as im aware, HBOOT upgrade is possible S-ON, but downgrade requires S-OFF. Give me the link to the firmware ur flashing
raghav kapur said:
I think ur flashing the wrong firmware. As far as im aware, HBOOT upgrade is possible S-ON, but downgrade requires S-OFF. Give me the link to the firmware ur flashing
Click to expand...
Click to collapse
https://mega.co.nz/#!e5pkBDpL!KM_H4wmVCJTCB6XlTLxG5SxyfgoIhnH_ne0fAHdGPM4
Hboot 1.56 Base 4.06
Does it matter if my Bootloader is locked/unlocked when i flash the hboot?
dre-z said:
https://mega.co.nz/#!e5pkBDpL!KM_H4wmVCJTCB6XlTLxG5SxyfgoIhnH_ne0fAHdGPM4
Hboot 1.56 Base 4.06
Does it matter if my Bootloader is locked/unlocked when i flash the hboot?
Click to expand...
Click to collapse
You've flashed the wrong firmware.
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Choose 4.19.401.9
Unlock your bootloader and then flash this firmware
the exe form of ruu in htc1guru.com is corrupt, i checked md8 signatures. but zip form is ok.
hboot is now working with locked bootloader, i will try RUU later. Thanks to all of you to this point!!!
I can't download the ruu, the download speed is so worse, it takes 6 hours and cancles at 100-150mb -.- was googling for another mirror, but didn't find one yet
The phone is working again, you're the best, all of u!!! Big thanks again!!!!!!!
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
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
Hi All,
This might have been asked but couldn't find the right thread. I have rooted my phone, installed TWRP, super user but can't gain S-Off and don't want to spend $25 for sunshine. No custom rom installed. I am looking for options where I can get back to its original state.
Please help.
Regards,
Sam
cheetah_rider73 said:
Hi All,
This might have been asked but couldn't find the right thread. I have rooted my phone, installed TWRP, super user but can't gain S-Off and don't want to spend $25 for sunshine. No custom rom installed. I am looking for options where I can get back to its original state.
Please help.
Regards,
Sam
Click to expand...
Click to collapse
RUU will restore your phone to 100% stock. Only thing that will stand out is "tampered" flag in bootloader. If you don't mind that, just flash your respective RUU
donkeykong1 said:
Only thing that will stand out is "tampered" flag in bootloader.
Click to expand...
Click to collapse
and ***RELOCKED*** instead of ***LOCKED***
Thanks for your replies. I have tried "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.1 4.3250.13_10.33.1150.01_release_318450_signed_2.exe" but somehow it was error-ed out. I am not sure whether I am doing it right or not.
Any suggestions on which RUU executable should I consider for AT&T. The other one I found was ZIP. I have downloaded but nothing to execute. I have to say I am novice on this custom ROM process.
I truly appreciate your help.
cheetah_rider73 said:
Thanks for your replies. I have tried "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.1 4.3250.13_10.33.1150.01_release_318450_signed_2.exe" but somehow it was error-ed out. I am not sure whether I am doing it right or not.
Any suggestions on which RUU executable should I consider for AT&T. The other one I found was ZIP. I have downloaded but nothing to execute. I have to say I am novice on this custom ROM process.
I truly appreciate your help.
Click to expand...
Click to collapse
First, post your fastboot getvar all output, but erase your JMEI and serial no. That way we will know more about your software, and will be able to point you in the right direction
donkeykong1 said:
First, post your fastboot getvar all output, but erase your JMEI and serial no. That way we will know more about your software, and will be able to point you in the right direction
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxxxx
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4224mV
(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
all: Done!
finished. total time: 0.099s
So, you have that RUU.zip downloaded? And it's matching your firmware?
donkeykong1 said:
So, you have that RUU.zip downloaded? And it's matching your firmware?
Click to expand...
Click to collapse
As I said I am not very familiar with the process. Now I found the one matching my firmware and downloading it. I will update the forum after I install it. Thanks Anyway
Now I am getting this error.. Please help
C:\Users\sam\Desktop\S Off\platform-tools>fastboot flash zip RUU.zip
sending 'zip'... (1624538 KB) FAIL02 data length is too large
FAILED (data size is too large(1624538 KB) for device to download ZIP file 'RUU.zip'
)
Execution time is 6(ms)
cheetah_rider73 said:
Now I am getting this error.. Please help
C:\Users\sam\Desktop\S Off\platform-tools>fastboot flash zip RUU.zip
sending 'zip'... (1624538 KB) FAIL02 data length is too large
FAILED (data size is too large(1624538 KB) for device to download ZIP file 'RUU.zip'
)
Execution time is 6(ms)
Click to expand...
Click to collapse
You need htc fasboot because regular fasboot can't handle files over 1.5 GB.
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Here's a "how to" on Lollipop RUU flashing. Read the first page, and flash away [emoji4]
donkeykong1 said:
You need htc fasboot because regular fasboot can't handle files over 1.5 GB.
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Here's a "how to" on Lollipop RUU flashing. Read the first page, and flash away [emoji4]
Click to expand...
Click to collapse
I'm getting that error, even with the htc_fastboot. any ideas?