Related
Hey everyone
Please anyone can help me to figure it out
I bought new htc one somedays ago with sense 5. And then i convert it into GE phone.
But now i want to return it into stock condition so when i try to find my main version always it shows the blank
Version-main:
Then nothing is showing.
Mine htc one is international version M7 AND when i flash the stock rom on my phone after relock my bootloader it stuck on signature verification then it show 12 signature verification failed.
Please anyone can help
Are you still S-OFF?
No my s-on.
So you didn't use the full conversion RUU, just a custom ROM based on the GE base?
yes u are right i used the custom based rom and flashed with twrp.
C:\Users\Asif\Desktop\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35WW915118
(bootloader) imei: 354436058680925
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3989mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
EddyOS said:
So you didn't use the full conversion RUU, just a custom ROM based on the GE base?
Click to expand...
Click to collapse
yes u are right i used the custom based rom and flashed with twrp.
C:\Users\Asif\Desktop\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35WW915118
(bootloader) imei: 354436058680925
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3989mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
So just flash another custom ROM based on Sense. It's weird that there is no mainver, though
EddyOS said:
So just flash another custom ROM based on Sense. It's weird that there is no mainver, though
Click to expand...
Click to collapse
yes i flashed so many custom Rom
like odexed
de-odexed
maximus 4.3 sense 5
all is sense 5
but still it is not showing the main version
Seeing as your CID is HTC__J15 you're going to have to find a stock backup matching that CID
EddyOS said:
Seeing as your CID is HTC__J15 you're going to have to find a stock backup matching that CID
Click to expand...
Click to collapse
if u dont mind can u find the correct ruu for my phone....i saw so many ruu on xda im confuse which i should flash.
please if u find and send me the link plaese let me know
There isn't one, hence my saying you need a backup
Go search the RUU/Backup thread in General and see if there's one available
Aisfkhan said:
if u dont mind can u find the correct ruu for my phone....i saw so many ruu on xda im confuse which i should flash.
please if u find and send me the link plaese let me know
Click to expand...
Click to collapse
EddyOS said:
There isn't one, hence my saying you need a backup
Go search the RUU/Backup thread in General and see if there's one available
Click to expand...
Click to collapse
Were you trying to flash firmware for you to loose version-main
Anyway, HTC__J15 (as far as i know) is a .401. Middle East variant, I have CWM backup of 2.24.401.2, but that's for the M7_U model, not M7_UL model which would be 2.24.401.1.
Do you know what firmware version you should be on? I think the signed x.xx.401.x firmware works with your phone. Since your hboot is 1.54, I would assume it's either 2.24.401.1 or 2.24.401.8.
This is from a signed 2.24.401.1 firmware:
Code:
[B]modelid: PN0710000[/B]
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__A07
[B]cidnum: HTC__J15[/B]
cidnum: HTC__016
mainver: 2.24.401.1
btype:1
aareport:1
hbootpreupdate:3
But don't go flashing firmware haphazardly with S-On!!
nkk71 said:
Were you trying to flash firmware for you to loose version-main
Anyway, HTC__J15 (as far as i know) is a .401. Middle East variant, I have CWM backup of 2.24.401.2, but that's for the M7_U model, not M7_UL model which would be 2.24.401.1.
Do you know what firmware version you should be on? I think the signed x.xx.401.x firmware works with your phone. Since your hboot is 1.54, I would assume it's either 2.24.401.1 or 2.24.401.8.
This is from a signed 2.24.401.1 firmware:
Code:
[B]modelid: PN0710000[/B]
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__A07
[B]cidnum: HTC__J15[/B]
cidnum: HTC__016
mainver: 2.24.401.1
btype:1
aareport:1
hbootpreupdate:3
But don't go flashing firmware haphazardly with S-On!!
Click to expand...
Click to collapse
hey thanks
yes i live in saudia arabia its arabic version
can u tell when i flash ruu my phone should s-on or s-off??
Aisfkhan said:
hey thanks
yes i live in saudia arabia its arabic version
can u tell when i flash ruu my phone should s-on or s-off??
Click to expand...
Click to collapse
You can't S-OFF as you're on HBOOT 1.54 so you can only flash a backup
Aisfkhan said:
hey thanks
yes i live in saudia arabia its arabic version
can u tell when i flash ruu my phone should s-on or s-off??
Click to expand...
Click to collapse
To run an official RUU exe you can be S-On, but I haven't seen one for 2.24.401.x. And since you are S-On, you cannot run a 1.xx RUU to downgrade.
In theory, you could flash a signed 2.24.401.1 or 2.24.401.8 firmware package, which are available to get your firmware (main version) fully back. But with S-On, IF something goes wrong, you would have problems.
Anyway, what's your main purpose? If it's just to go back to Sense 5 Stock ROM, you could flash a generic 2.24.401.8 ROM.
Also, supposedly, S-Off for 1.54 should be coming in a while. Then you could S-Off and do pretty much anything you like.
nkk71 said:
To run an official RUU exe you can be S-On, but I haven't seen one for 2.24.401.x. And since you are S-On, you cannot run a 1.xx RUU to downgrade.
In theory, you could flash a signed 2.24.401.1 or 2.24.401.8 firmware package, which are available to get your firmware (main version) fully back. But with S-On, IF something goes wrong, you would have problems.
Anyway, what's your main purpose? If it's just to go back to Sense 5 Stock ROM, you could flash a generic 2.24.401.8 ROM.
Also, supposedly, S-Off for 1.54 should be coming in a while. Then you could S-Off and do pretty much anything you like.
Click to expand...
Click to collapse
i flash custom odexed sense 5 rom which is working perfectly but i want it in stock condition so that i can claim warranty.
somedays ago i mistakenly thorugh my phone to the floor and after that my phone vibrator stop working.
and its about 11 months warranty remaining so thts y i want to send it to htc care
Aisfkhan said:
i flash custom odexed sense 5 rom which is working perfectly but i want it in stock condition so that i can claim warranty.
somedays ago i mistakenly thorugh my phone to the floor and after that my phone vibrator stop working.
and its about 11 months warranty remaining so thts y i want to send it to htc care
Click to expand...
Click to collapse
With S-On, you will not be able to change your bootloader to "LOCKED" only "RELOCKED", so any service center will know you've unlocked your bootloader and could say your warranty is void (depends on the guys in the service center).
And as EddyOS said, no S-Off for 1.54 at the moment; rumours for 1.54 s-off are here: http://forum.xda-developers.com/showthread.php?t=2474089
Aisfkhan said:
i flash custom odexed sense 5 rom which is working perfectly but i want it in stock condition so that i can claim warranty.
somedays ago i mistakenly thorugh my phone to the floor and after that my phone vibrator stop working.
and its about 11 months warranty remaining so thts y i want to send it to htc care
Click to expand...
Click to collapse
and now im downloading this rom from xda
Stock 2.24.401.1 ROM and Recovery with Aroma Installer
so when i flash does it slove my problem??
and Im not familier with htc phone
so please can u tell how to flash this rom from fastboot or with twrp/cwm???
nkk71 said:
With S-On, you will not be able to change your bootloader to "LOCKED" only "RELOCKED", so any service center will know you've unlocked your bootloader and could say your warranty is void (depends on the guys in the service center).
And as EddyOS said, no S-Off for 1.54 at the moment; rumours for 1.54 s-off are here: http://forum.xda-developers.com/showthread.php?t=2474089
Click to expand...
Click to collapse
no as pocketnow they said relocked dosent matter...htc will also accept ur phone if it is RELOCKED so it doesnt matter
Aisfkhan said:
and now im downloading this rom from xda
Stock 2.24.401.1 ROM and Recovery with Aroma Installer
so when i flash does it slove my problem??
and Im not familier with htc phone
so please can u tell how to flash this rom from fastboot or with twrp/cwm???
Click to expand...
Click to collapse
1- Flash it through CWM or TWRP, select stock as much as possible (for example without root).
2- You'll also need stock recovery, you can find one for 2.24.401.1 here: http://forum.xda-developers.com/showthread.php?t=2463387
you flash this using "fastboot flash recovery <name of recovery>.img
3- relock your bootloader: "fastboot oem lock"
But before doing step 2 and 3, check you "fastboot getvar all" and see if it show the main version (ie firmware), if it's still missing, you have two choices (IMHO) either flash a signed 2.24.401.1 firmware (using fastboot in RUU mode) or send it back for warranty and hope it passes.
As for the TAMPERED sign, it should go away after you flash stock recovery (step 2) above, BUT it seems for some it does go away, and for others it doesn't. I haven't found conclusive results as to why it sometimes stays or why it goes away.
Hello
My htc one is s-off with supercid and locked bootloader, i run RUU for wwe 1.20 firmware, but now my phone is stuck with controlling header 7% why does it not work??
knudsen81 said:
Hello
My htc one is s-off with supercid and locked bootloader, i run RUU for wwe 1.20 firmware, but now my phone is stuck with controlling header 7% why does it not work??
Click to expand...
Click to collapse
Is your modelid supported by the RUU?
attanasi0 said:
Is your modelid supported by the RUU?
Click to expand...
Click to collapse
I have supercid so i should flash all???
knudsen81 said:
I have supercid so i should flash all???
Click to expand...
Click to collapse
Can you please copy/paste the results of "fastboot getvar all" ?
Just follow this guide. I think you may have to relock bootloader (using revone) before using the RUU
attanasi0 said:
Can you please copy/paste the results of "fastboot getvar all" ? Could you link us to the RUU you are using ?
Click to expand...
Click to collapse
here
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT37SW901541
(bootloader) imei: 357864051186268
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.086s
But i have google edition on now, before was my main 1.24.401.8 and cid HTC__Y13
i try the ruu exe RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
I just want to downgrade
attanasi0 said:
Can you please copy/paste the results of "fastboot getvar all" ?
Just follow this guide. I think you may have to relock bootloader (using revone) before using the RUU
Click to expand...
Click to collapse
My bootloader is locked with use of revone
knudsen81 said:
here
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT37SW901541
(bootloader) imei: 357864051186268
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.086s
But i have google edition on now, before was my main 1.24.401.8 and cid HTC__Y13
i try the ruu exe RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
I just want to downgrade
Click to expand...
Click to collapse
What are the "modelid" listed inside the android-info.txt of your RUU?
attanasi0 said:
What are the "modelid" listed inside the android-info.txt of your RUU?
Click to expand...
Click to collapse
modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__J15
cidnum: HTC__016
mainver: 1.20.401.1
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
knudsen81 said:
modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__J15
cidnum: HTC__016
mainver: 1.20.401.1
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Click to expand...
Click to collapse
For some reason SuperCID is not listed. That might be the issue.
attanasi0 said:
For some reason SuperCID is not listed. That might be the issue.
Click to expand...
Click to collapse
Yes i have see it, i try to change cid to htc__001 and see
attanasi0 said:
For some reason SuperCID is not listed. That might be the issue.
Click to expand...
Click to collapse
Thanks man now i got past it and my phone is updating
I installed twrp on my HTC One and when trying to flash a new rom was getting remote not allowed error msg. I read that relocking and unlocking would sometimes fix this problem. I fastboot oem locked and then couldn't do anymore after that because when I try to unlock with my unlock token it says it is unlocking but never works.... so basically now i am stuck with nothing but bootloader!! I have also read that because I am hboot version 1.54.0000 now after recent update there is some new security that prevents unlocking through fastboot?? Please anyone who could help I would really appreciate it! I paid cash for the phone and have no warranty and only had it for about a month... really dont want to buy a new one! Whenever I try to flash a rom now through fastboot I get the error: signature verification failed! message. Thank you to anyone who can help.
~3 days deep in searching for an answer
CWS_001
bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main: 3.62.1700.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4277mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e82187e
hbootpreupdate: 11
gencheckpt: 0
@nkk71, do you think he can flash the Dev edition firmware 4.06.1540.x and unlock the bootloader? CID/MID already matches..
Dev firmware listed here: http://arhd.onedroid.net/db_mirror/Firmware/index.php?dir=HTC/HTC_One/1540/
SaHiLzZ said:
@nkk71, do you think he can flash the Dev edition firmware 4.06.1540.2 and unlock the bootloader? CID/MID already matches..
Dev firmware listed here: http://arhd.onedroid.net/db_mirror/Firmware/index.php?dir=HTC/HTC_One/1540/
Click to expand...
Click to collapse
Yo @SaHiLzZ, hope all is well.
Honestly, I don't know, everything looks "funny" (as in weird):
bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-main: 3.62.1700.1
version-misc: PVT SHIP S-ON
product: m7_ul
modelid: PN0712000
cidnum: CWS__001
an ATT phone, with GPE firmware on it, while S-On
if it is a GPE phone, then maybe (yes long shot), "fastboot oem unlock"
otherwise get a new token and try again.
---------- Post added at 07:52 PM ---------- Previous post was at 07:48 PM ----------
SaHiLzZ said:
Dev firmware listed here: http://arhd.onedroid.net/db_mirror/Firmware/index.php?dir=HTC/HTC_One/1540/
Click to expand...
Click to collapse
oh sorry, just saw the link; are those signed firmware packages, if so I guess upgrade should work. and then with a new unlock token, could work.
but isn't dev edition CID: BS_US001 ?
Doing well, thanks! Hope the same to you @nkk71. Yes, they are pulled from OTA.. http://forum.xda-developers.com/showthread.php?t=2182823
x.xx.1540.x - HTC One U.S. Developer Edition
modelid: PN0711000
modelid: PN0713000
modelid: PN0712000
modelid: PN0714000
modelid: PN0710000
modelid: PN071****
cidnum: HTC__***
cidnum: CWS__001
cidnum: H3G__***
cidnum: O2___***
cidnum: ORANG***
cidnum: TELNZ001
cidnum: OPTUS001
cidnum: T-MOB***
cidnum: TELST001
cidnum: VODAP***
cidnum: BM___001
cidnum: BS_US001
cidnum: GLOBA001
cidnum: ROGER001
cidnum: TELUS001
cidnum: TIM__***
Click to expand...
Click to collapse
SaHiLzZ said:
Doing well, thanks! Hope the same to you @nkk71. Yes, they are pulled from OTA.. http://forum.xda-developers.com/showthread.php?t=2182823
Click to expand...
Click to collapse
Code:
x.xx.1540.x - HTC One U.S. Developer Edition
modelid: PN0711000
modelid: PN0713000
modelid: PN0712000
modelid: PN0714000
modelid: PN0710000
modelid: PN071****
cidnum: HTC__***
cidnum: CWS__001
cidnum: H3G__***
cidnum: O2___***
cidnum: ORANG***
cidnum: TELNZ001
cidnum: OPTUS001
cidnum: T-MOB***
cidnum: TELST001
cidnum: VODAP***
cidnum: BM___001
cidnum: BS_US001
cidnum: GLOBA001
cidnum: ROGER001
cidnum: TELUS001
cidnum: TIM__***
^^ don't think that's a signed one, that looks more like a custom one (probably extracted from an official OTA, but android-info.txt modified), as far as i know, MID is PN0712000 and CID is BS_US001 for it to be an official & signed package.
Seems encrypted as I can't unzip it normally. OP, please try flashing the firmware from the link above like this (rename 4.06.1540.2.zip to firmware.zip):
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <-- May have to do it twice if you get a FAILED (remote: 90 hboot pre-update! please flush image again immediately)
fastboot reboot
Let us know how it goes.
THANK YOU!~!!!!
Awesome! I havent gotten it yet though. Thank you for all your help so far but im still stuck in bootloader... recovery goes to the triangle and (!) ,,, anyone know what I can do next?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
My getvar all:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.23.3263.28
version-cpld: None
version-microp: None
version-main: 4.20.707.6
version-misc: PVT SHIP S-OFF
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__044
battery-status: good
battery-voltage: 3951mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-59adc32b
hbootpreupdate: 11
gencheckpt: 0
New firmware:
modelid: PN0711000
cidnum: HTC__044
cidnum: HTC__038
mainver: 4.20.707.7
btype:1
aareport:1
hbootpreupdate:3
Can I flash this new firmware without problems? I'm worried because they don't have the same modelid. Please help
qwertyuiop404 said:
My getvar all:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.23.3263.28
version-cpld: None
version-microp: None
version-main: 4.20.707.6
version-misc: PVT SHIP S-OFF
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__044
battery-status: good
battery-voltage: 3951mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-59adc32b
hbootpreupdate: 11
gencheckpt: 0
New firmware:
modelid: PN0711000
cidnum: HTC__044
cidnum: HTC__038
mainver: 4.20.707.7
btype:1
aareport:1
hbootpreupdate:3
Can I flash this new firmware without problems? I'm worried because they don't have the same modelid. Please help
Click to expand...
Click to collapse
with S-Off you can flash any firmware, but
1- this one will give you MID mismatch unless you edit the android-info.txt (using notepad++)
2- why would you want to
nkk71 said:
with S-Off you can flash any firmware, but
1- this one will give you MID mismatch unless you edit the android-info.txt (using notepad++)
2- why would you want to
Click to expand...
Click to collapse
I guess i downloaded the wrong firmware. I based the compatibility with "version-main". So the compatibility with be based on MID and CID? I must have da same MID and CID with the firmware im going to flash. Right?
Sent from my HTC One using XDA Premium 4 mobile app
qwertyuiop404 said:
I guess i downloaded the wrong firmware. I based the compatibility with "version-main". So the compatibility with be based on MID and CID? I must have da same MID and CID with the firmware im going to flash. Right?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
it's not incompatible, it would work just fine,
with S-Off you can use any firmware you like, that's why custom firmwares, have android-info.txt already edited, for example:
Code:
modelid: PN0711000
modelid: PN0713000
modelid: PN0712000
modelid: PN0714000
modelid: PN0710000
modelid: PN071****
cidnum: HTC__***
cidnum: CWS__001
cidnum: H3G__***
cidnum: O2___***
cidnum: ORANG***
cidnum: TELNZ001
cidnum: OPTUS001
cidnum: T-MOB***
cidnum: TELST001
cidnum: VODAP***
cidnum: BM___001
cidnum: BS_US001
cidnum: GLOBA001
cidnum: ROGER001
cidnum: TELUS001
cidnum: TIM__***
So since i'm s-off, i can flash any firmware? So theres no chance getting bricked?
Sent from my HTC One using XDA Premium 4 mobile app
nkk71 said:
it's not incompatible, it would work just fine,
with S-Off you can use any firmware you like, that's why custom firmwares, have android-info.txt already edited, for example:
Code:
modelid: PN0711000
modelid: PN0713000
modelid: PN0712000
modelid: PN0714000
modelid: PN0710000
modelid: PN071****
cidnum: HTC__***
cidnum: CWS__001
cidnum: H3G__***
cidnum: O2___***
cidnum: ORANG***
cidnum: TELNZ001
cidnum: OPTUS001
cidnum: T-MOB***
cidnum: TELST001
cidnum: VODAP***
cidnum: BM___001
cidnum: BS_US001
cidnum: GLOBA001
cidnum: ROGER001
cidnum: TELUS001
cidnum: TIM__***
Click to expand...
Click to collapse
So since i'm s-off, i can flash any firmware? So theres no chance getting bricked?
Sent from my HTC One using XDA Premium 4 mobile app
qwertyuiop404 said:
So since i'm s-off, i can flash any firmware? So theres no chance getting bricked?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
well you won't want to flash a firmware for Sprint Or Verizon and thiers little use for the 1.xx.xxx.x firmwares they have outdated touchpad drivers
clsA said:
well you won't want to flash a firmware for Sprint Or Verizon and thiers little use for the 1.xx.xxx.x firmwares they have outdated touchpad drivers
Click to expand...
Click to collapse
Where can i check my current firmware?
Sent from my HTC One using XDA Premium 4 mobile app
qwertyuiop404 said:
Where can i check my current firmware?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
fastboot getvar all
search the forums for how it works, if your not sure
clsA said:
fastboot getvar all
search the forums for how it works, if your not sure
Click to expand...
Click to collapse
I know that command but which one tells me my current firmware version?
qwertyuiop404 said:
So since i'm s-off, i can flash any firmware? So theres no chance getting bricked?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here are two good threads for firmware(s) for your model:
[Guide] Vomer's Ultimate AIO - S-OFF, SuperCID, Firmware Upgrade & Custom Recovery (in the firmware section)
or
[HTC ONE M7] Newest Firmware 4.19.401.11 for KITKAT modified HBOOT, (No Red warning)
remember you need to be S-Off, and don't even THINK about going S-On!!
nkk71 said:
Here are two good threads for firmware(s) for your model:
[Guide] Vomer's Ultimate AIO - S-OFF, SuperCID, Firmware Upgrade & Custom Recovery (in the firmware section)
or
[HTC ONE M7] Newest Firmware 4.19.401.11 for KITKAT modified HBOOT, (No Red warning)
remember you need to be S-Off, and don't even THINK about going S-On!!
Click to expand...
Click to collapse
Is my current firmware version the "build number" in my phone?
qwertyuiop404 said:
I know that command but which one tells me my current firmware version?
Click to expand...
Click to collapse
version-main: 4.20.707.6
version-misc: PVT SHIP S-OFF
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
Click to expand...
Click to collapse
the one in blue is your firmware (or at least whatever you flashed last in ruu mode)
the ones in red indicate your model.
---------- Post added at 03:34 PM ---------- Previous post was at 03:31 PM ----------
qwertyuiop404 said:
Is my current firmware version the "build number" in my phone?
Click to expand...
Click to collapse
no that would be the ROM version it's based on.
by the way, your firmware is quite up-to-date, don't bother changing it.
.
nkk71 said:
the one in blue is your firmware (or at least whatever you flashed last in ruu mode)
the ones in red indicate your model.
---------- Post added at 03:34 PM ---------- Previous post was at 03:31 PM ----------
no that would be the ROM version it's based on.
by the way, your firmware is quite up-to-date, don't bother changing it.
.
Click to expand...
Click to collapse
Lol. okay. I got confused because I've been reading the thread "[HTC ONE M7] Newest Firmware 4.19.401.11 for KITKAT modified HBOOT, (No Red warning)". Then i thought, maybe my firmware is not the newest one.
Thanks man. I really appreciate the fast reply
qwertyuiop404 said:
Lol. okay. I got confused because I've been reading the thread "[HTC ONE M7] Newest Firmware 4.19.401.11 for KITKAT modified HBOOT, (No Red warning)". Then i thought, maybe my firmware is not the newest one.
Thanks man. I really appreciate the fast reply
Click to expand...
Click to collapse
it's really hard to tell which one is "newest", cause the 4.20.707.x versions, actually came out before the 4.19.401.x versions.... but in any case you should be good with the one you have :good:
nkk71 said:
it's really hard to tell which one is "newest", cause the 4.20.707.x versions, actually came out before the 4.19.401.x versions.... but in any case you should be good with the one you have :good:
Click to expand...
Click to collapse
Since mine is 4.20.707.6, I think someone already have 4.20.707.7.
qwertyuiop404 said:
Since mine is 4.20.707.6, I think someone already have 4.20.707.7.
Click to expand...
Click to collapse
theirs no benefit to updating your firmware all the time .. I have gone months without an update... some firmware's patch things you don't want patched
qwertyuiop404 said:
Since mine is 4.20.707.6, I think someone already have 4.20.707.7.
Click to expand...
Click to collapse
well here you go:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as you can see differences are pretty close to nothing,
android-info.txt -> nobody cares
hboot.img -> who cares
boot.img = stock kernel -> nobody cares (it'll get overwritten by the custom ROM's kernel)
recovery.img = stock recovery -> nobody cares cause we use custom recoveries (e.g. TWRP)
rcdata.img minor change (.6 has that line in red, .7 doesn't)
nkk71 said:
well here you go:
as you can see differences are pretty close to nothing,
android-info.txt -> nobody cares
hboot.img -> who cares
boot.img = stock kernel -> nobody cares (it'll get overwritten by the custom ROM's kernel)
recovery.img = stock recovery -> nobody cares cause we use custom recoveries (e.g. TWRP)
rcdata.img minor change (.6 has that line in red, .7 doesn't)
Click to expand...
Click to collapse
WOW! That was one hell of an effort. THANKS MAN. I love you! Hahaha
What about the Radio? Hahaha
qwertyuiop404 said:
WOW! That was one hell of an effort. THANKS MAN. I love you! Hahaha
What about the Radio? Hahaha
Click to expand...
Click to collapse
all the other files are 100% binary match! ZERO difference.
Update:
old post attached at the bottom!
Seems like I tried to flash the wrong OTA, so that problem is gone.
But does anyone have an idea, why they changed my CID?!
----------------------------------------------------------
Dear community,
I don't know if I really have a problem, maybe you can enlight me with your knowledge
The story of my htc one m7 in short words:
I had my m7 rooted, supercid and unlocked. Ealry this year around 9th january I sent my phone to HTC because og the pink camera problem and set it to stock -> unroot, lock, normal CID (htc__102) and flashged RUU
After I got it back, all worked nice and yesterday I read that the lollipop update is there. I checked several times but no update via OTA. So it can take a few days to get to me, but sadly I'm not that patient.
I downlaoded the OTA file and tried to flash through fastboot, but everytime I try it I get the same error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I checked my fastboot getvar and noticed I have a different CID as my previous, they changed it to htc__140 ?! Is there a possibility that they messed something up during the repair?
hboot: 1.57
firmware: 6.09.401.11
Or am I to quick with my thoughts and wait a little longer?
Any help is appreciated
best regards dre-z
dre-z said:
Update:
old post attached at the bottom!
Seems like I tried to flash the wrong OTA, so that problem is gone.
But does anyone have an idea, why they changed my CID?!
----------------------------------------------------------
Dear community,
I don't know if I really have a problem, maybe you can enlight me with your knowledge
The story of my htc one m7 in short words:
I had my m7 rooted, supercid and unlocked. Ealry this year around 9th january I sent my phone to HTC because og the pink camera problem and set it to stock -> unroot, lock, normal CID (htc__102) and flashged RUU
After I got it back, all worked nice and yesterday I read that the lollipop update is there. I checked several times but no update via OTA. So it can take a few days to get to me, but sadly I'm not that patient.
I downlaoded the OTA file and tried to flash through fastboot, but everytime I try it I get the same error:
I checked my fastboot getvar and noticed I have a different CID as my previous, they changed it to htc__140 ?! Is there a possibility that they messed something up during the repair?
hboot: 1.57
firmware: 6.09.401.11
Or am I to quick with my thoughts and wait a little longer?
Any help is appreciated
best regards dre-z
Click to expand...
Click to collapse
You can't flash ota update from fastboot, it must be flashed from stock recovery. If s-on, the only way to flash the ota update is by using the automated process in setting --> about --> update, like the average consumer do. If s-off, you can download the ota from the web and flash it manually from stock recovery.
ota update must match the rom fingerprint, cid and mid.
Are you sure about your cid? Never heard about HTC__140 before... can you post a "getvar all" ? If the CID isn't the same it might be because they have replaced the mainboard...
alray said:
You can't flash ota update from fastboot, it must be flashed from stock recovery. If s-on, the only way to flash the ota update is by using the automated process in setting --> about --> update, like the average consumer do. If s-off, you can download the ota from the web and flash it manually from stock recovery.
ota update must match the rom fingerprint, cid and mid.
Are you sure about your cid? Never heard about HTC__140 before... can you post a "getvar all" ? If the CID isn't the same it might be because they have replaced the mainboard...
Click to expand...
Click to collapse
As you can see htc__140, maybe they had to change the board because of the camera problem?
fastboot getvar
(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.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 11111111111111111
(bootloader) imei: 1111111111111111
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__140
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(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
Mhm I will be patient, someday the OTA will arrive at my m7 )
dre-z said:
As you can see htc__140, maybe they had to change the board because of the camera problem?
fastboot getvar
(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.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 11111111111111111
(bootloader) imei: 1111111111111111
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__140
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(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
Mhm I will be patient, someday the OTA will arrive at my m7 )
Click to expand...
Click to collapse
Very strange. First time I see HTC__140 for the WWE version. I would be curious to see if the android-info.txt file of the 7.19.401.2 ota update include this CID. Worst case scenario, you'll have to pay 25$ to use sunshine s-off and change your CID.
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
can you open the ota.zip? Inside the ota is a firmware.zip file, extract them and look at the android-info.txt. If your CID isn't listed there then I don't know how you'll receive the update...
---------- Post added at 09:14 AM ---------- Previous post was at 09:11 AM ----------
NVM just checked myself. It looks like your CID (HTC__140) isn't in the android-info.txt of 7.17.401.2. So in theory, your phone will never receive the 7.17.401.2 ota update with this CID, maybe it will be a different update. The only thing I know is HTC__140 is Switzerland but afaik, it was never used on the M7 (at least not on the WWE .401 version)
Code:
modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__J15
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
mainver: 7.19.401.2
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
alray said:
Very strange. First time I see HTC__140 for the WWE version. I would be curious to see if the android-info.txt file of the 7.19.401.2 ota update include this CID. Worst case scenario, you'll have to pay 25$ to use sunshine s-off and change your CID.
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
can you open the ota.zip? Inside the ota is a firmware.zip file, extract them and look at the android-info.txt. If your CID isn't listed there then I don't know how you'll receive the update...
---------- Post added at 09:14 AM ---------- Previous post was at 09:11 AM ----------
NVM just checked myself. It looks like your CID (HTC__140) isn't in the android-info.txt of 7.17.401.2. So in theory, your phone will never receive the 7.17.401.2 ota update with this CID, maybe it will be a different update. The only thing I know is HTC__140 is Switzerland but afaik, it was never used on the M7 (at least not on the WWE .401 version)
Code:
modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__J15
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
mainver: 7.19.401.2
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Click to expand...
Click to collapse
I think they messed something up while they repaired it and I need to use sunshine s-off.
Don't want to send it in again, the last time it lasts 3 1/2 weeks until I git it back.
dre-z said:
I think they messed something up while they repaired it and I need to use sunshine s-off.
Don't want to send it in again, the last time it lasts 3 1/2 weeks until I git it back.
Click to expand...
Click to collapse
If you don't really care about spending 25 for s-off, then you should definitively try to change your CID to HTC__001 or any other cid in the list. Otherwise, you might want to wait a little bit. I'm not 100% sure about your CID being wrong, maybe its tied to another version, idk. But I never seen this CID before... especially not on a x.xx.401.x version.
alray said:
If you don't really care about spending 25 for s-off, then you should definitively try to change your CID to HTC__001 or any other cid in the list. Otherwise, you might want to wait a little bit. I'm not 100% sure about your CID being wrong, maybe its tied to another version, idk. But I never seen this CID before... especially not on a x.xx.401.x version.
Click to expand...
Click to collapse
Don't mind, changed my CID and now the OTA is downloading. Thanks for your help.