Database Develop

fastboot getvar version-main empty

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.

Finding the correct ruu

Hey,
I got S-OFF and want to reset my defice to full stock. I would like to use a ruu instead of a nandroid but I'm not sure with ruu to download. Does it matter or can I just download every ruu for my HTC__102 device if the number matches?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(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__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3863mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.066s

Slurpslurp said:
Hey,
I got S-OFF and want to reset my defice to full stock. I would like to use a ruu instead of a nandroid but I'm not sure with ruu to download. Does it matter or can I just download every ruu for my HTC__102 device if the number matches?
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
finished. total time: 0.066s
Click to expand...
Click to collapse
MID & CID preferably match, hence: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/

nkk71 said:
MID & CID preferably match, hence: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
Click to expand...
Click to collapse
What about
http://www.htc1guru.com/dld/ruu_m7_..._10-27-1127-01_release_308001_signed_2_4-exe/
What is the difference between these two? I don't just want to download. I want to understand

Slurpslurp said:
What about
http://www.htc1guru.com/dld/ruu_m7_..._10-27-1127-01_release_308001_signed_2_4-exe/
What is the difference between these two? I don't just want to download. I want to understand
Click to expand...
Click to collapse
not sure that's really an official one, maybe a pre-release, it has hboot 1.43 and does not receive any OTAs.

nkk71 said:
not sure that's really an official one, maybe a pre-release, it has hboot 1.43 and does not receive any OTAs.
Click to expand...
Click to collapse
Where can you see it has 1.43 and does not receive any OTA?

Slurpslurp said:
Where can you see it has 1.43 and does not receive any OTA?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=49271146&postcount=276
and
http://forum.xda-developers.com/showpost.php?p=49271225&postcount=277
and
http://forum.xda-developers.com/showpost.php?p=49365665&postcount=291

nkk71 said:
http://forum.xda-developers.com/showpost.php?p=49271146&postcount=276
and
http://forum.xda-developers.com/showpost.php?p=49271225&postcount=277
and
http://forum.xda-developers.com/showpost.php?p=49365665&postcount=291
Click to expand...
Click to collapse
Main Version is 1.29 so I can still use 1.28?

Slurpslurp said:
Main Version is 1.29 so I can still use 1.28?
Click to expand...
Click to collapse
yep, thanks to s-off.

nkk71 said:
yep, thanks to s-off.
Click to expand...
Click to collapse
So my phone is 100% stock as I bought it?

Slurpslurp said:
So my phone is 100% stock as I bought it?
Click to expand...
Click to collapse
yes, it will be 100% stock.
if you need bootloader to say "LOCKED" then you can follow my guide: http://forum.xda-developers.com/showthread.php?t=2541082
i recommend staying s-off, but if you intend on going s-on, then follow the guide exactly.

nkk71 said:
yes, it will be 100% stock.
if you need bootloader to say "LOCKED" then you can follow my guide: http://forum.xda-developers.com/showthread.php?t=2541082
i recommend staying s-off, but if you intend on going s-on, then follow the guide exactly.
Click to expand...
Click to collapse
I can't install the RUU.exe. It tells me I got the wrong version. I got S-OFF. I'm confused.

Slurpslurp said:
I can't install the RUU.exe. It tells me I got the wrong version. I got S-OFF. I'm confused.
Click to expand...
Click to collapse
are you sure you downloaded the correct one? http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It's has:
Code:
modelid: [B][COLOR="Red"]PN0710000[/COLOR][/B]
cid: HTC__001, HTC__E11
[B][COLOR="Red"]HTC__102[/COLOR][/B], HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016

Need little bit help please

I have to sent in my one because aof warranty.
Now my problem is, that I don't become my phone on o2 stock.
- I downloaded this (RUU M7 UL K44 SENSE55 MR O2 UK 4.20.206.16 Radio 4A.23.3263.28 10.38r.1157.04L Release 353143 Signed 2) RUU from http://forum.xda-developers.com/showthread.php?t=2428276
- I relocked my bootloader
- I change my CID to O2___102
And after the RUU is sending the files I became the message that the RUU is not right for my phone.
What can I do? Please help

ChronoWerX said:
I have to sent in my one because aof warranty.
Now my problem is, that I don't become my phone on o2 stock.
- I downloaded this (RUU M7 UL K44 SENSE55 MR O2 UK 4.20.206.16 Radio 4A.23.3263.28 10.38r.1157.04L Release 353143 Signed 2) RUU from http://forum.xda-developers.com/showthread.php?t=2428276
- I relocked my bootloader
- I change my CID to O2___102
And after the RUU is sending the files I became the message that the RUU is not right for my phone.
What can I do? Please help
Click to expand...
Click to collapse
post the output of ''fastboot getvar all'' minus IMEI/SN

alray said:
post the output of ''fastboot getvar all'' minus IMEI/SN
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.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: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

ChronoWerX said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.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: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Have you removed the tampered flag from the bootloader and set it back to locked (not relocked) for warranty? This ruu will probably take you to hboot 1.56 and you'll get stuck with a tampered flag if you s-on again.
For the RUU, I don't understand why it didn't worked, you have the correct CID and MID and your phone is s-off, so it should work. Maybe @nkk71 know why?

alray said:
Have you removed the tampered flag from the bootloader and set it back to locked (not relocked) for warranty? This ruu will probably take you to hboot 1.56 and you'll get stuck with a tampered flag if you s-on again.
For the RUU, I don't understand why it didn't worked, you have the correct CID and MID and your phone is s-off, so it should work. Maybe @nkk71 know why?
Click to expand...
Click to collapse
Oh yes thanks I forget this. For information I used the dark bootloader from here

ChronoWerX said:
Oh yes thanks I forget this. For information I used the dark bootloader from here
Click to expand...
Click to collapse
Don't ever S-ON with a moded hboot, You will brick your phone!

alray said:
Don't ever S-ON with a moded hboot, You will brick your phone!
Click to expand...
Click to collapse
Ok thx, hboot is now stock, its locked and tampered is removed, test now ruu again
Edit: It worked. It was the modded HBOOT ... Thanks man

alray said:
Have you removed the tampered flag from the bootloader and set it back to locked (not relocked) for warranty? This ruu will probably take you to hboot 1.56 and you'll get stuck with a tampered flag if you s-on again.
For the RUU, I don't understand why it didn't worked, you have the correct CID and MID and your phone is s-off, so it should work. Maybe @nkk71 know why?
Click to expand...
Click to collapse
unfortunately it seems i may have a vague idea, unfortunately, ... stay away from those "RUU_M7_UL_K44_SENSE55_MR...." something doesn't seem right there!! (especially with S-On!!!)
EDIT: above statement seems inaccurate!!

nkk71 said:
unfortunately it seems i may have a vague idea, unfortunately, ... stay away from those "RUU_M7_UL_K44_SENSE55_MR...." something doesn't seem right there!! (especially with S-On!!!)
Click to expand...
Click to collapse
Oh read too late ... all worked here. Especially S-ON

ChronoWerX said:
Oh read too late ... all worked here. Especially S-ON
Click to expand...
Click to collapse
Glad to hear, what I really meant you will most likely not be able to install/flash these ROMs with S-On, with S-Off yes.... but their packaging seems a bit off, so people with S-On are going to have a hard time installing/flashing them
PS: did you just go S-Off to S-On on hboot 1.56?
how many times have you rebooted?

nkk71 said:
Glad to hear, what I really meant you will most likely not be able to install/flash these ROMs with S-On, with S-Off yes.... but their packaging seems a bit off, so people with S-On are going to have a hard time installing/flashing them
PS: did you just go S-Off to S-On on hboot 1.56?
how many times have you rebooted?
Click to expand...
Click to collapse
- locked bootloader
- install ruu ... i think 2 or 3 reboots
- s-on with fastboot command
- 2 reboots to see if all works

ChronoWerX said:
- locked bootloader
- install ruu ... i think 2 or 3 reboots
- s-on with fastboot command
- 2 reboots to see if all works
Click to expand...
Click to collapse
you should only go back s-on on hboot 1.44-1.54. The tampered flag will probably comes on again on hboot 1.55+.

alray said:
you should only go back s-on on hboot 1.44-1.54. The tampered flag will probably comes on again on hboot 1.55+.
Click to expand...
Click to collapse
No it worked
{
"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"
}
Gesendet von meinem HTC One_M8 mit Tapatalk

[Q] Cannot receive OTA update

Hi Guys,
I recently got my hands on a used M7 but noticed that it is still stuck in Andriod 4.1.2. I tried running the RUU but when I check for OTA updates it still says no updates available.
I also discovered that there is a label that says this is a test device, perhaps that stops the device from getting OTA updates?
Here is what I got from fastboot:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.43.0000
(bootloader) version-baseband: 4A.13.3231.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.707.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4230mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
It will be great if someone can help me update this device Thanks!

Divinity Shins said:
Hi Guys,
I recently got my hands on a used M7 but noticed that it is still stuck in Andriod 4.1.2. I tried running the RUU but when I check for OTA updates it still says no updates available.
I also discovered that there is a label that says this is a test device, perhaps that stops the device from getting OTA updates?
Here is what I got from fastboot:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.43.0000
(bootloader) version-baseband: 4A.13.3231.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.707.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: Remove
(bootloader) imei: Remove
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4230mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
It will be great if someone can help me update this device Thanks!
Click to expand...
Click to collapse
In your post remove the imei and serialno.
You need to change your MID to PN0714000 and your CID to HTC__044 (eight characters). If you still do not receive OTA, here is a custom unsigned RUU 3.63.707.4 that you flash in bootloader. Or you could flash Guru_reset_m7_3-63-707-4-zip in TWRP.

majmoz said:
In your post remove the imei and serialno.
You need to change your MID to PN0711000 and your CID to HTC__044 (eight characters). If you still do not receive OTA, here is a custom unsigned RUU 3.63.707.4 that you flash in bootloader. Or you could flash Guru_reset_m7_3-63-707-4-zip in TWRP.
Click to expand...
Click to collapse
majmoz, sorry to bug in, but i would recommend PN0710000 or PN0714000 because PN0711000 is the m7_u, and the OP has an m7_ul

majmoz said:
In your post remove the imei and serialno.
You need to change your MID to PN0714000 and your CID to HTC__044 (eight characters). If you still do not receive OTA, here is a custom unsigned RUU 3.63.707.4 that you flash in bootloader. Or you could flash Guru_reset_m7_3-63-707-4-zip in TWRP.
Click to expand...
Click to collapse
Hi,
Thanks for reminding me about the imei & serial#.
I assume this is the tool that I should use to change the CID and MID?
http://forum.xda-developers.com/showthread.php?t=2535365
Sounds like flashing the custom RUU is an easier choice to me. I shall try changing the CID and MID first.

@Divinity Shins
what region are you in / what do you want your phone to be
a) European unbranded
b) Asian unbranded
?

nkk71 said:
@Divinity Shins
what region are you in / what do you want your phone to be
a) European unbranded
b) Asian unbranded
?
Click to expand...
Click to collapse
I'm in Hong Kong, but I don't really mind which area as long as I get the Andriod 4.4 now and all the future HTC upgrades (i.e Andriod L).

Divinity Shins said:
I'm in Hong Kong, but I don't really mind which area as long as I get the Andriod 4.4 now and all the future HTC upgrades (i.e Andriod L).
Click to expand...
Click to collapse
Sorry, I'm out at the moment to give detailed instructions, but you could go for PN0710000 and HTC__001 (European unbranded) and flash a x.xx.401.x ruu

Divinity Shins said:
I'm in Hong Kong, but I don't really mind which area as long as I get the Andriod 4.4 now and all the future HTC upgrades (i.e Andriod L).
Click to expand...
Click to collapse
not to jump nkk71 replies, but I just changed my phone to Dev edition last night in 30mins, it was very easy and got OTA's straight after booting.
Change cid to BS_US001 (always 8 characters)
Change MID to PN0712000 using this tool in a custom recovery: http://forum.xda-developers.com/showthread.php?t=2535365
download this firmware, put your phone into RUU mode and don't forget to flash it twice: https://www.androidfilehost.com/?fid=23329332407579901
download this RUU and run it with your phone in fastboot USB mode: http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_353887_signed_3-exe/
DONE !!!

I did it! Thanks everyone for the help :fingers-crossed:

Problem with Lollipop OTA

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.