Database Develop

[Q] If I take my phone to a repair shop will they get it back on stock firmware?

I've been pulling my hair out trying to return my phone to stock in order to recieve OTA updates,
it's been the most frustrating process ever.
It's been made infinitely more frustrating because of the fact that my laptop and my desktop both run on windows 8.1
and my HTC One M7 isn't recognized in fastboot in either of them. As a result of this i've been having to borrow friends
laptops which run on windows 7 in order to try and sort the process which i'm not comfortable with.
Tried installing different drivers to no avail.
Been trying all types of things like Hasoon's tool box and an infinite amount of other techniqeus. For hours straight i've been trying and other methods to sort out the issue but have always stumbled into
walls. It's been so frustrating.
Will a phoneshop like a little store in town (not a big store like THREE or Vodaphone) be able to return my phone's software to as new like when I got it from my phone store so that I can recieve OTA updates?

tomquartey said:
I've been pulling my hair out trying to return my phone to stock in order to recieve OTA updates,
it's been the most frustrating process ever
Click to expand...
Click to collapse
I understand its frustrating but you really don't need to send your device to phone shop to return stock and get ota. Its a relatively simple process and many users here can help you. But we can't help if you keep creating new threads each days for the same issue.
thread 1
thread 2
thread 3
thread 4
So as nkk71 said in thread 1
make up your mind, where you wanna post, so people can actually help
Click to expand...
Click to collapse
Now what I understand from all this (correct me if i'm wrong), you were on H3G, you were not able to receive ota to kitkat (even if I doubt H3G released kitkat yet...) So you s-off'ed your phone to install 1.29.401 Ruu.exe with supercid. Now you have these issues:
You can't receive ota
you are using windows 8.1 with hboot 1.44 so fastboot isn't working properly
To receive OTA updates, you need:
stock recovery
CID that match your main-version (the ruu version you installed.... a .401 base)
MID that match your main-ver
CID that match the ruu you used (1.28.401.7):
HTC__001
HTC__E11
HTC__102
HTC__203
HTC__405
HTC__Y13
HTC__304
HTC__032
HTC__A07
HTC__J15
HTC__016
ref here (4th download link in the list)
MID that match the ruu you used (1.28.401.7)
PN0710000
ref here (4th download link in the list)
So now you will need to confirm what you need with this command:
Code:
fastboot getvar all
and you need this:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-main: [COLOR="Red"]1.29.401.7[/COLOR] [COLOR="red"]-----> assuming this info is good[/COLOR]
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: [COLOR="red"]PN0710000[/COLOR] [COLOR="red"]-------> need this MID (PN0710000)[/COLOR]
(bootloader) cidnum: [COLOR="Red"]NEED CID LISTED ABOVE HERE NOT H3G, NOT SUPERCID[/COLOR]
(bootloader) partition-layout: Generic
(bootloader) security: off
now you should know how to change CID because you already did to be supercid but just in case:
Code:
fastboot oem writecid HTC__001 [COLOR="DarkOrange"]I'll suggest you use HTC__001 but its up to you to chose from the list above[/COLOR]
fastboot reboot-bootloader
then reboot and try to search for ota from your phone.
Now the Win8.1/Fastboot/hboot 1.44 issue: (Yes, you need to solve this first )
get your hands on a winXP, win7 computer or
install windows 7 on dual boot on your computer or
use a Ubuntu live cd instead of windows to use fastboot from terminal (require no installation of ubuntu) as sugested by tobesedated in thread 4 with his awesome guide including picutres (maybe her.. idk ) you can skip steps that involve rumrunner as you already have s-off. you just want adb/fastboot working from the terminal)
now try all this and feel free to ask other questions or pm me like you did, but please don't create another thread for this
Im going to sleep now so don't expect any reply from me for the next 10 hours.
oh and when you'll get fastboot working, post your ''fastboot getvar all'' here (except imei/sn) it will help.
---------- Post added at 08:57 AM ---------- Previous post was at 08:52 AM ----------
Feel free to add anything if i'm missing something

[Q] HTC One M7 RUU IMG Error

Hey guys,
I recently got S-Off on my device and downgraded my HBoot to 1.44 and changed to SuperCID 11111111
The RUU i downloaded is " Sprint_HTC_One_m7wls_4.06.651.4_RUU"
The reason i need to go back to stock to see if i can get my Wifi and Bluetooth to start working again since it's stuck in "turning on mode" I have tried flashing new roms, radios, kernals, factory reset etc. No idea why Wifi and Bluetooth stopped working i just woke up one morning and it wouldn't turn on.
For some reason when flashing this RUUi keep on getting 158 IMG error? I have tried running as admin, and making sure phone is in Fastboot USB but still wont work.
Which RUU should i try, any help would be awesome as i would love to get my Wifi and Bluetooth working again, here are my phones details.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4079mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks guys.

iAMuSIK said:
Hey guys,
I recently got S-Off on my device and downgraded my HBoot to 1.44 and changed to SuperCID 11111111
The RUU i downloaded is " Sprint_HTC_One_m7wls_4.06.651.4_RUU"
The reason i need to go back to stock to see if i can get my Wifi and Bluetooth to start working again since it's stuck in "turning on mode" I have tried flashing new roms, radios, kernals, factory reset etc. No idea why Wifi and Bluetooth stopped working i just woke up one morning and it wouldn't turn on.
For some reason when flashing this RUUi keep on getting 158 IMG error? I have tried running as admin, and making sure phone is in Fastboot USB but still wont work.
Which RUU should i try, any help would be awesome as i would love to get my Wifi and Bluetooth working again, here are my phones details.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4079mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks guys.
Click to expand...
Click to collapse
Sprint_HTC_One_m7wls_4.06.651.4_RUU
Click to expand...
Click to collapse
this ruu isn't for your phone at all !
You have a M7_UL (GSM) not a M7WLS (sprint CDMA) !!
What was your original CID?
Your main-ver is .401 so you probably need a .401 ruu

alray said:
this ruu isn't for your phone at all !
You have a M7_UL (GSM) not a M7WLS (sprint CDMA) !!
What was your original CID?
Your main-ver is .401 so you probably need a .401 ruu
Click to expand...
Click to collapse
Its a good thing that RUU check for MID/CID... or I can't imagine posts from the amount of mis-match flashing.. :cyclops:

@iAMuSIK
From this thread:
You:
My HTC is a M7 on Optus Australia network.
Click to expand...
Click to collapse
so your cid was probably OPTUS001 and you need a .980 version
LS.xD:
Seems as there is no matching RUU
Click to expand...
Click to collapse
You:
So there is no Ruu for my phones carrier which does suck.
Click to expand...
Click to collapse
So why did you attempted to flash an incompatible RUU even if you already know there is none compatible for your phone?

I was
I was under the impression that if i was S-OFF and had SuperCID that i could run any RUU.
I know there is no RUU for my device hence why i wanted to get S-OFF and SuperCID so i could try another RUU, so this is not possible?
I have the nandroid backup for my device but when i flashed it Wifi and Bluetooth would still not work. Looks like i might have to send it into the shop for repairs.

iAMuSIK said:
I was under the impression that if i was S-OFF and had SuperCID that i could run any RUU.
Click to expand...
Click to collapse
Not ANY ruu! Only RUU for M7_UL models. CID and MID must match the ruu (can be easily changed to match RUU with s-off)
M7WLS is a different phone and flashing things for the WLS variant on your UL variant WILL brick your phone.
BTW Never flash things to your phone ''under the impression'' it is ok, read carefully and ask questions
---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------
@iAMuSIK
now you could try the 1.28.401.7 ruu
Be sure the MD5 value match the downloaded RUU: 2fd46305b6080830e2ca27a080999b93
fastboot oem writecid HTC__001
change MID to PN0710000 using this tool
then run the ruu
Never s-on
and stay bootloader unlocked for now
if your issue persist, your phone is hardware damaged and you will need to send it back for repair.

alray said:
Not ANY ruu! Only RUU for M7_UL models. CID and MID must match the ruu (can be easily changed to match RUU with s-off)
M7WLS is a different phone and flashing things for the WLS variant on your UL variant WILL brick your phone.
BTW Never flash things to your phone ''under the impression'' it is ok, read carefully and ask questions
Click to expand...
Click to collapse
I thought i did read everything, which obviously i missed a few parts. Since the nandroid backup didn't work ill take defeat and accept my Wifi and Bluetooth is possibly a hardware issue. Can't send phone in for warrenty since its "Rooted" so hopefully i can find a good repair center around my part of town.

iAMuSIK said:
I thought i did read everything, which obviously i missed a few parts. Since the nandroid backup didn't work ill take defeat and accept my Wifi and Bluetooth is possibly a hardware issue. Can't send phone in for warrenty since its "Rooted" so hopefully i can find a good repair center around my part of town.
Click to expand...
Click to collapse
try what I said above (post edited)

alray said:
Not ANY ruu! Only RUU for M7_UL models. CID and MID must match the ruu (can be easily changed to match RUU with s-off)
M7WLS is a different phone and flashing things for the WLS variant on your UL variant WILL brick your phone.
BTW Never flash things to your phone ''under the impression'' it is ok, read carefully and ask questions
---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------
@iAMuSIK
now you could try the 1.28.401.7 ruu
Be sure the MD5 value match the downloaded RUU: 2fd46305b6080830e2ca27a080999b93
fastboot oem writecid HTC__001
change MID to PN0710000 using this tool
then run the ruu
Never s-on
and stay bootloader unlocked for now
if your issue persist, your phone is hardware damaged and you will need to send it back for repair.
Click to expand...
Click to collapse
Just saw your added info, thanks a lot mate. Will give his a try today and report back if it works, fingers crossed!

iAMuSIK said:
Can't send phone in for warrenty since its "Rooted".
Click to expand...
Click to collapse
you can go back to stock with your nanadroid backup using this guide: http://forum.xda-developers.com/showthread.php?t=2541082 en send your phone for warranty repair

alray said:
Not ANY ruu! Only RUU for M7_UL models. CID and MID must match the ruu (can be easily changed to match RUU with s-off)
M7WLS is a different phone and flashing things for the WLS variant on your UL variant WILL brick your phone.
BTW Never flash things to your phone ''under the impression'' it is ok, read carefully and ask questions
---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------
@iAMuSIK
now you could try the 1.28.401.7 ruu
Be sure the MD5 value match the downloaded RUU: 2fd46305b6080830e2ca27a080999b93
fastboot oem writecid HTC__001
change MID to PN0710000 using this tool
then run the ruu
Never s-on
and stay bootloader unlocked for now
if your issue persist, your phone is hardware damaged and you will need to send it back for repair.
Click to expand...
Click to collapse
Just in the middle of doing this process now and im getting a error when trying to write CID.
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem writecid H
TC_001
...
(bootloader) fail: [writecid] Invalid cid
OKAY [ 0.013s]
finished. total time: 0.014s
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
EDIT: 2 underscores and not 1 lol.

So
@alray
So finally got the RUU but still not Wifi and Bluetooth working. Hardware issue it is. Thanks a lot for the help in getting this to work bud

[Q] Unable to update to 4.4

Hello,
I'm completely new to this so please bear with me. I bought an HTC One Mini off a Chinese seller on eBay. I have the "This is a test device" message in the "Tell HTC and error reporting" so from what I gathered, it means that it is S-OFF.
Edit: When trying to update, the update gets downloaded, phone reboots, I get the red warning with exclamation point and and it just reboots without updating.
To verify, I did the bootloader thing and it reads like so:
M7_UL PVT SHIP S-OFF RH
CID-1111111111
HDBOOT-1.55.0000
ADIO-4A.20.3263.16
OpenDSO-v32.120.274.0909
OS-3.22.1540.1
eMMC-boot 2048Mb
Sept 17 2013
1. What's the easiest way to get back to a place where I'll be able to update to KitKat and get rid of that message which doesn't involve too much complications?
I'm a web programmer so I'm not exactly a computer illiterate but I must say I'm completely lost.
Any answers would be appreciated.
Thank you!

This is the getvar all:
i.imgur.com/v6jiWgr.jpg
modelid: PN071****
cid: 111111111

calbertuk said:
This is the getvar all:
i.imgur.com/v6jiWgr.jpg
modelid: PN071****
cid: 111111111
Click to expand...
Click to collapse
The jpg of your getvar all did not show up properly. You have to copy and paste it. Based on the OS it looks like it might be a Dev Ed M7. When you post the getvar all remove the imei and serial number!
If you copied your cid correctly, then there should only have eight (8) "1" instead of nine. This post has a listing of all of the OTA beginning with your version. In order for the updates to run properly, you must have the stock recovery, stock rom and maybe some preloaded apps. This post will explain what the OTA is looking for.

calbertuk said:
This is the getvar all:
i.imgur.com/v6jiWgr.jpg
modelid: PN071****
cid: 111111111
Click to expand...
Click to collapse
Everything I can see make me believe you don't have an htc one mini but an htc one (m7) dev edition (which is a really good thing imo). Measure the display diagonal and you'll known.
4.7 inches for a M7
4.3 inches for a mini
If you have a m7 dev edition you could use the 3.22.1540 ruu to restore your phone back to stock and you'll then be able to apply ota. Red triangle with exclamation mark means there is a missing/modified system file. The ota is patching system files so if one of them is missing or modified, the installation will fail. restoring with the ruu should fix this issue. make a backup of your files before, the ruu will wipe everything on your phone.

alray said:
Everything I can see make me believe you don't have an htc one mini but an htc one (m7) dev edition (which is a really good thing imo). Measure the display diagonal and you'll known.
4.7 inches for a M7
4.3 inches for a mini
If you have a m7 dev edition you could use the 3.22.1540 ruu to restore your phone back to stock and you'll then be able to apply ota. Red triangle with exclamation mark means there is a missing/modified system file. The ota is patching system files so if one of them is missing or modified, the installation will fail. restoring with the ruu should fix this issue. make a backup of your files before, the ruu will wipe everything on your phone.
Click to expand...
Click to collapse
Turns out I have a M7, seller apparently sent me the wrong phone.
Since I'm not able to find out my cid, does any RUU 3.22.1540 work
? Even US ones (like this http://forum.xda-developers.com/showthread.php?t=2460534 ) or can I find a Euro one? Would you mind pointing me to one that will work?
After, can I follow this tutorial http://forum.xda-developers.com/showthread.php?t=2541082 ?
Thank you

majmoz said:
The jpg of your getvar all did not show up properly. You have to copy and paste it. Based on the OS it looks like it might be a Dev Ed M7. When you post the getvar all remove the imei and serial number!
If you copied your cid correctly, then there should only have eight (8) "1" instead of nine. This post has a listing of all of the OTA beginning with your version. In order for the updates to run properly, you must have the stock recovery, stock rom and maybe some preloaded apps. This post will explain what the OTA is looking for.
Click to expand...
Click to collapse
Your method would help me updating without getting back to stock?
To get back to stock, I need a matching RUU and a guide like this one http://forum.xda-developers.com/showthread.php?t=2541082 , right?
getvar all
c:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.22.1540.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4248mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.075s

calbertuk said:
Your method would help me updating without getting back to stock?
To get back to stock, I need a matching RUU and a guide like this one http://forum.xda-developers.com/showthread.php?t=2541082 , right?
Click to expand...
Click to collapse
Edit your last post to REMOVE the imei and serial number!
You can use the guide as reference but you just need to run the RUU. To run the RUU just double click it once you have it downloaded to your PC.
Go to the HTC Support Site and filter One M7 in the first box and Brightstar in the second. Then select Find Files, select the 3.22.1540.1 Developer Edition RUU to download. Use this RUU, it is directly from HTC.

majmoz said:
Edit your last post to REMOVE the imei and serial number!
You can use the guide as reference but you just need to run the RUU. To run the RUU just double click it once you have it downloaded to your PC.
Go to the HTC Support Site and filter One M7 in the first box and Brightstar in the second. Then select Find Files, select the 3.22.1540.1 Developer Edition RUU to download. Use this RUU, it is directly from HTC.
Click to expand...
Click to collapse
Thanks, I removed it.
I'm downloading the RUU.

majmoz said:
Edit your last post to REMOVE the imei and serial number!
You can use the guide as reference but you just need to run the RUU. To run the RUU just double click it once you have it downloaded to your PC.
Go to the HTC Support Site and filter One M7 in the first box and Brightstar in the second. Then select Find Files, select the 3.22.1540.1 Developer Edition RUU to download. Use this RUU, it is directly from HTC.
Click to expand...
Click to collapse
I've updated with the RUU, I'm now at version 4.3. The phone won't detect there is a 4.4 update and the "This is a test device" still appears. Any further help please?

calbertuk said:
I've updated with the RUU, I'm now at version 4.3. The phone won't detect there is a 4.4 update and the "This is a test device" still appears. Any further help please?
Click to expand...
Click to collapse
you should first fix MID and CID, PN071**** is not good, imho
since you are S-OFF, your phone can be anything you want, so please explain what you'd like it to be, before I link the appropriate files

nkk71 said:
you should first fix MID and CID, PN071**** is not good, imho
since you are S-OFF, your phone can be anything you want, so please explain what you'd like it to be, before I link the appropriate files
Click to expand...
Click to collapse
What I wanted was:
- Get the OTA update
- Get rid of the "This is a test device" message
The OTA update is now coming through after adding a clean RUU and I'm about to put s-on back in order to get rid of the message.
Is the fact that the MID and CID not there an issue?

calbertuk said:
What I wanted was:
- Get the OTA update
- Get rid of the "This is a test device" message
The OTA update is now coming through after adding a clean RUU and I'm about to put s-on back in order to get rid of the message.
Is the fact that the MID and CID not there an issue?
Click to expand...
Click to collapse
going S-ON is going to be a really bad idea.
first fix your MID and CID!!!
MIDs should be (as far as I'm aware):
PN0710000 -> international M7_UL
PN0711000 -> international M7_U
PN0712000 -> US/Canada M7_UL
PN0713000 -> US T-Mobile M7_UL
PN0714000 -> Asia M7_UL
To change your MID to one of the above (PN0710000 for example), you can use this tool: [TOOL] MID change without ENG HBOOT | Aroma GUI
which you use in a custom recovery.
CID choices will be dependent on the MID you choose.
you are looking for serious trouble staying on PN071**** and going S-ON.

nkk71 said:
going S-ON is going to be a really bad idea.
first fix your MID and CID!!!
MIDs should be (as far as I'm aware):
PN0710000 -> international M7_UL
PN0711000 -> international M7_U
PN0712000 -> US/Canada M7_UL
PN0713000 -> US T-Mobile M7_UL
PN0714000 -> Asia M7_UL
To change your MID to one of the above (PN0710000 for example), you can use this tool: [TOOL] MID change without ENG HBOOT | Aroma GUI
which you use in a custom recovery.
CID choices will be dependent on the MID you choose.
you are looking for serious trouble staying on PN071**** and going S-ON.
Click to expand...
Click to collapse
Just easier to stay s-off even though I'm complete newbie?
If I ever sell the phone, I'll need to go s-on, if I go for PN0710000, what CID should I be using (I'm in the UK)?
Once, I change the CID/MID, I'm all set to go back to s-on?

calbertuk said:
Just easier to stay s-off even though I'm complete newbie?
If I ever sell the phone, I'll need to go s-on, if I go for PN0710000, what CID should I be using (I'm in the UK)?
Once, I change the CID/MID, I'm all set to go back to s-on?
Click to expand...
Click to collapse
UK would be MID: PN0710000
CID would usually be HTC__001 <- two underscores, CID is exactly 8 characters
CIDs for PN0710000 are:
Code:
HTC__001 --> HTC-WWE
HTC__016 --> VODA-Africa-South
HTC__032 --> HTC-EastEurope
HTC__102 --> HTC-GER
HTC__203 --> HTC-FRA
HTC__304 --> HTC-SPA
HTC__405 --> HTC-ITA
HTC__A07 --> HTC-Russia
HTC__E11 --> HTC-Dutch
HTC__J15 --> HTC-GCC
HTC__Y13 --> HTC-Nor
CID is changed using (only possible with S-off):
fastboot oem writecid HTC__001 <- two underscores
fastboot reboot-bootloader
Personally, I wouldn't go S-ON even if I wanted to sell the phone (maybe the next user wants to customize his phone), just look at your situation, if your phone wasn't S-OFF, you'd be majorly stuck (<- replace that word with whatever comes to mind )
but one thing is for sure, if I ever did want to go from S-Off to S-On, then I would only do it on hboot 1.44 or 1.54 (I believe you've read my guide, so you know the "tamper detected - rebooting" issue)

nkk71 said:
UK would be MID: PN0710000
CID would usually be HTC__001 <- two underscores, CID is exactly 8 characters
CIDs for PN0710000 are:
Code:
HTC__001 --> HTC-WWE
HTC__016 --> VODA-Africa-South
HTC__032 --> HTC-EastEurope
HTC__102 --> HTC-GER
HTC__203 --> HTC-FRA
HTC__304 --> HTC-SPA
HTC__405 --> HTC-ITA
HTC__A07 --> HTC-Russia
HTC__E11 --> HTC-Dutch
HTC__J15 --> HTC-GCC
HTC__Y13 --> HTC-Nor
CID is changed using (only possible with S-off):
fastboot oem writecid HTC__001 <- two underscores
fastboot reboot-bootloader
Personally, I wouldn't go S-ON even if I wanted to sell the phone (maybe the next user wants to customize his phone), just look at your situation, if your phone wasn't S-OFF, you'd be majorly stuck (<- replace that word with whatever comes to mind )
but one thing is for sure, if I ever did want to go from S-Off to S-On, then I would only do it on hboot 1.44 or 1.54 (I believe you've read my guide, so you know the "tamper detected - rebooting" issue)
Click to expand...
Click to collapse
The "This is a test device" in the "Tell HTC" bit doesn't look great if I want to sell this.
Anyways, thanks a ton for your help and to the others, you should a bitcoin donation address in your signature!

calbertuk said:
The "This is a test device" in the "Tell HTC" bit doesn't look great if I want to sell this.
Anyways, thanks a ton for your help and to the others, you should a bitcoin donation address in your signature!
Click to expand...
Click to collapse
No problem, glad to be of help
And I guess, if you ever wanted to sell it, you could ask if he/she want's it S-Off or S-On

calbertuk said:
The "This is a test device" in the "Tell HTC" bit doesn't look great if I want to sell this.
Anyways, thanks a ton for your help and to the others, you should a bitcoin donation address in your signature!
Click to expand...
Click to collapse
I would follow @nkk71 advice and change your MID to PN0710000 and your CID to HTC__001. After you do that then you need to download this International WWE RUU and the next update to Sense 6. By doing this your phone will be complete with matching MID, CID and OS. Stay on this version because it generally gets the OTA's quicker than the carrier version. There is no reason to go S-ON especially since your phone doesn't have a warranty!

[Q] Return to stock again, Q hboot

Hi,
So returning to stock again and Im planning on doing the following
Install the following zip as per video instructions on website.
Select option to include root
Then install this version of SuperSU >
Follow this guide to set the bootloader to LOCKED
Removed root from within SuperSu settings
Enter the following command via fastboot to go S-ON
./fastboot oem writesecureflag 3
However, when I completed this last year I was on hboot 1.54, now after upgrading a few times my setup is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.06.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3880mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I will change the cidnum back to VODAP001 before I do any of the above, but how do I get back to hboot 1.54 ?
The following is the status I need to get the phone back to:
(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: 2.24.161.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36JW907644
(bootloader) imei: 357864050522398
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4149mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
will the version-main and baseband also be downgraded when I use the Guru_Reset_M7_2.24.161.1.zip file ?

No the version main won't be downgraded with the guru reset file, that file is pretty much rom only, you need the firmware.zip file to do that, you also need it to downgrade your hboot, or an ruu, I've had a look and there is no ruu for Vodafone, however, there is some earlier ota's. You could try downloading those and pull firmware.zip from them, then manually flash that, firmware zip contains things like stock recovery, radio, hboot, partition layouts etc, try and get one which matches the number on the guru reset file, ie search for 2.24.161.xx firmware, flash that first, you will then need to put a custom recovery back on to run the guru reset file, during the installation, select wipe data, install stock recovery and install stock radio, once it's all done and booted at least once, only then lock your bootloader and s-on, be careful when going back s-on though, it's been known for the tampered flag to return, personally I would send it back s-off, high chance they wouldn't even notice.
Just one question, why do you want to root ?, if your returning to stock for warranty then skip that part completely, you won't need root.
You may be able to pull firmware.zip from this ota http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/

Seanie280672 said:
No the version main won't be downgraded with the guru reset file, that file is pretty much rom only, you need the firmware.zip file to do that, you also need it to downgrade your hboot, or an ruu, I've had a look and there is no ruu for Vodafone, however, there is some earlier ota's. You could try downloading those and pull firmware.zip from them, then manually flash that, firmware zip contains things like stock recovery, radio, hboot, partition layouts etc, try and get one which matches the number on the guru reset file, ie search for 2.24.161.xx firmware, flash that first, you will then need to put a custom recovery back on to run the guru reset file, during the installation, select wipe data, install stock recovery and install stock radio, once it's all done and booted at least once, only then lock your bootloader and s-on, be careful when going back s-on though, it's been known for the tampered flag to return, personally I would send it back s-off, high chance they wouldn't even notice.
Just one question, why do you want to root ?, if your returning to stock for warranty then skip that part completely, you won't need root.
You may be able to pull firmware.zip from this ota http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
Click to expand...
Click to collapse
need root to remove the TAMPERED flag.

akuma24 said:
need root to remove the TAMPERED flag.
Click to expand...
Click to collapse
Nah you don't, on the guru reset site, there is a bootloader reset tool which you just run from custom recovery.
It will allow you to lock, relock, unlock the bootloader whilst s-off and also remove the tampered flag
http://www.htc1guru.com/guides/guru-bootloader-reset/

Seanie280672 said:
Nah you don't, on the guru reset site, there is a bootloader reset tool which you just run from custom recovery.
It will allow you to lock, relock, unlock the bootloader whilst s-off and also remove the tampered flag
http://www.htc1guru.com/guides/guru-bootloader-reset/
Click to expand...
Click to collapse
Thanks again, can you extract the firmware from this file for me ? I try to extract on a mac and it just zip's the file back up
http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
Then again, Im thinking, is it necessary to downgrade the firmware to version 2.24.161.1, maybe downgrade to 4.06.1540.2 instead

akuma24 said:
Thanks again, can you extract the firmware from this file for me ? I try to extract on a mac and it just zip's the file back up
http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
Then again, Im thinking, is it necessary to downgrade the firmware to version 2.24.161.1, maybe downgrade to 4.06.1540.2 instead
Click to expand...
Click to collapse
I'm not near a computer at the moment so can't do that sorry, 161 is Vodafone, the other one you mentioned is 1540 developer edition, as you are s-off you can flash any ruu, but it might get questioned.

Seanie280672 said:
I'm not near a computer at the moment so can't do that sorry, 161 is Vodafone, the other one you mentioned is 1540 developer edition, as you are s-off you can flash any ruu, but it might get questioned.
Click to expand...
Click to collapse
what about 4.19.401.11, is that developer also ?

akuma24 said:
what about 4.19.401.11, is that developer also ?
Click to expand...
Click to collapse
That's WWE unbranded Europe, that's what I have on my phone, that would work, change your cid to HTC__001 first then get the ruu 4.19.401.9 and run it, you'll be full stock in no time.
4.19.401.11 is just an ota

Seanie280672 said:
That's WWE unbranded Europe, that's what I have on my phone, that would work, change your cid to HTC__001 first then get the ruu 4.19.401.9 and run it, you'll be full stock in no time.
4.19.401.11 is just an ota
Click to expand...
Click to collapse
what about this firmware:
http://d-h.st/WO9 (2.24.401.1)

akuma24 said:
what about this firmware:
http://d-h.st/WO9 (2.24.401.1)
Click to expand...
Click to collapse
You may as well just run the 401 ruu which will update the firmware too and hboot, it will do everything for you.

Seanie280672 said:
You may as well just run the 401 ruu which will update the firmware too and hboot, it will do everything for you.
Click to expand...
Click to collapse
Wouldnt the fact I have a WWE rom on my phone with a cid of VODA raise eyebrows over at htc ? True I can change the cid to HTC__xx but do they not have a record of which phone was given to which network etc

akuma24 said:
Wouldnt the fact I have a WWE rom on my phone with a cid of VODA raise eyebrows over at htc ? True I can change the cid to HTC__xx but do they not have a record of which phone was given to which network etc
Click to expand...
Click to collapse
I got mine from Vodafone UK, unbranded on HTC__001, you can't send it unbranded with a Vodafone cid, you will need to send it with the HTC cid

Seanie280672 said:
I got mine from Vodafone UK, unbranded on HTC__001, you can't send it unbranded with a Vodafone cid, you will need to send it with the HTC cid
Click to expand...
Click to collapse
Have downloaded the following and it contains the firmware for 4-19-161-11
http://www.htc1guru.com/dld/ota_m7_...-63-161-6_release_356881mwn487m942rk64ep-zip/
The download for 2.24.161.1 on the site times out after download 142MB so think it is corrupt.
The plan is to flash the firmware from 4-19-161-11, then run the guru reset for 2.24.161.1 and take the OTA's to bring it up to whatever it should currently be ?
These phones were so easy to reset back in the Hero days

akuma24 said:
Have downloaded the following and it contains the firmware for 4-19-161-11
http://www.htc1guru.com/dld/ota_m7_...-63-161-6_release_356881mwn487m942rk64ep-zip/
The download for 2.24.161.1 on the site times out after download 142MB so think it is corrupt.
The plan is to flash the firmware from 4-19-161-11, then run the guru reset for 2.24.161.1 and take the OTA's to bring it up to whatever it should currently be ?
These phones were so easy to reset back in the Hero days
Click to expand...
Click to collapse
Yu can't do that, the 4xxxxx firmware will contain too high a hboot for the otas to work, although the guru reset file will install, the otas will lead to a bootloop due to you already having a higher hboot

Seanie280672 said:
Yu can't do that, the 4xxxxx firmware will contain too high a hboot for the otas to work, although the guru reset file will install, the otas will lead to a bootloop due to you already having a higher hboot
Click to expand...
Click to collapse
Right, I need someone to fix that link then, have posted it in the collection thread, hopefully someone fixes it

Right so decided Im short on time so will run the following after changing the cid to HTC__001
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
This will downgrade the firmware and also flash the stock rom for htc europe.
Ill then need to change the recovery in order to run the following:
http://www.htc1guru.com/guides/guru-bootloader-reset/
then reflash stock recovery and finally remove s-off
????

akuma24 said:
Right, I need someone to fix that link then, have posted it in the collection thread, hopefully someone fixes it
Click to expand...
Click to collapse
which link, maybe there is another ?
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
im home now so im just downloading that ota, see if it contains a firmware.zip that I can extract, then i'll upload it for you if its there.
the download keeps getting reset, this site is starting to do my head in.

Seanie280672 said:
which link, maybe there is another ?
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
im home now so im just downloading that ota, see if it contains a firmware.zip that I can extract, then i'll upload it for you if its there.
Click to expand...
Click to collapse
this link here http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
think the one you are downloading

akuma24 said:
this link here http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
think the one you are downloading
Click to expand...
Click to collapse
yeah, he has a problem with someone hacking that site and resetting the downloads every 5 mins or so, im just trying to source the file from somewhere else.

Seanie280672 said:
yeah, he has a problem with someone hacking that site and resetting the downloads every 5 mins or so, im just trying to source the file from somewhere else.
Click to expand...
Click to collapse
Thanks, would really appreciate it if you could an alternative download source\link

htc one restore

hi,
i have problem in my htc one m7 that the camera is purple, i want to send my htc to htc center, but my device rooted and s-off and superCID and i don't remember my original one. and i installed android 5.0.2
is there anyway to restore my htc to stock rom so they can not find out that i have been rooted before? and what are the steps to do that? or if there is anyway to fix my camera? i used the ISO100 option and it didn't work
Thnaks

CID... From which country you come from? Without CID I can't give you RUU with Sense ROM.

Bruce666 said:
CID... From which country you come from? Without CID I can't give you RUU with Sense ROM.
Click to expand...
Click to collapse
my old ruu support Arabic

theevilhere said:
my old ruu support Arabic
Click to expand...
Click to collapse
i think it was HTC_001

(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: 11111111
(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-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

theevilhere said:
i think it was HTC_001
Click to expand...
Click to collapse
Your original CID can be found in the MFG partition mmcblk0p6
Better to edit your previous post to remove your IMEI and SERIALNO

alray said:
Your original CID can be found in the MFG partition mmcblk0p6
Better to edit your previous post to remove your IMEI and SERIALNO
Click to expand...
Click to collapse
i removed it.
how can i get the original CID?

theevilhere said:
i removed it.
how can i get the original CID?
Click to expand...
Click to collapse
Use an adb sheel to make a copy of mmcblk0p6
Code:
adb shell
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.img
Better to copy/paste the command, if you make a typo, it can be harmful to your phone.
then take the mmcblk0p6.img file on your /sdcard and send it to me, I'll tell you what your original CID was

alray said:
Use an adb sheel to make a copy of mmcblk0p6
Code:
adb shell
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.img
Better to copy/paste the command, if you make a typo, it can be harmful to your phone.
then take the mmcblk0p6.img file on your /sdcard and send it to me, I'll tell you what your original CID was
Click to expand...
Click to collapse
i will try to send it to you later, but where you want me to send it to you?

theevilhere said:
i will try to send it to you later, but where you want me to send it to you?
Click to expand...
Click to collapse
upload it to your dropbox/mega/google drive and send me the link via PM

@theevilhere
According to your MFG partition you sent me, you original MID is PN0711000 and your original CID is HTC__332. Your phone was manufactured 2013/09/17.
This phone was originally running software version x.xx.599.x, its a Latin America version and unfortunately, afaik, there is no RUU (or any other useful files) available for that version.
The best you can do imo, is to convert it to another version and hope they will not realize.
Even if they realize you have tampered with your phone, they might replace the camera for free, its a well known hardware defect. Some users reported that their phone (camera) were repaired under warranty even if the phone wasn't 100% stock.

alray said:
upload it to your dropbox/mega/google drive and send me the link via PM
Click to expand...
Click to collapse
i sent it to you

alray said:
@theevilhere
According to your MFG partition you sent me, you original MID is PN0711000 and your original CID is HTC__332. Your phone was manufactured 2013/09/17.
This phone was originally running software version x.xx.599.x, its a Latin America version and unfortunately, afaik, there is no RUU (or any other useful files) available for that version.
The best you can do imo, is to convert it to another version and hope they will not realize.
Even if they realize you have tampered with your phone, they might replace the camera for free, its a well known hardware defect. Some users reported that their phone (camera) were repaired under warranty even if the phone wasn't 100% stock.
Click to expand...
Click to collapse
thanks, but can you tell me the steps to return it back to stock? and ruu i should use and how am i going to set the CID

theevilhere said:
thanks, but can you tell me the steps to return it back to stock? and ruu i should use and how am i going to set the CID
Click to expand...
Click to collapse
Maybe you missed that part?
alray said:
@theevilhere
(...)
This phone was originally running software version x.xx.599.x, its a Latin America version and unfortunately, afaik, there is no RUU (or any other useful files) available for that version.
(...)
Click to expand...
Click to collapse
That mean you can't return it to stock, the only thing you can do is to convert it to another "stock version", which is not your real stock version and hope that they will not realize this.
If you want to change your CID all you need to do is
Code:
fastboot oem writecid YOUR_CID
e.g:
Code:
fastboot oem writecid HTC__332
if you want instruction about using a RUU, read nkk71's thread linked in my signature.

alray said:
Maybe you missed that part?
That mean you can't return it to stock, the only thing you can do is to convert it to another "stock version", which is not your real stock version and hope that they will not realize this.
If you want to change your CID all you need to do is
Code:
fastboot oem writecid YOUR_CID
e.g:
Code:
fastboot oem writecid HTC__332
if you want instruction about using a RUU, read nkk71's thread linked in my signature.
Click to expand...
Click to collapse
so how can i change it to another version?

theevilhere said:
so how can i change it to another version?
Click to expand...
Click to collapse
change your CID and MID to match another RUU and follow nkk71's guide in my signature.
For example you could use the x.xx.401.x version so you'll need to change your CID to HTC__001 and your MID to PN0710000 then flash the 1.28.401.7 ruu, remove the tampered flag from the bootloader and set it back to locked (not relocked). Its the closest from stock you can be.

alray said:
change your CID and MID to match another RUU and follow nkk71's guide in my signature.
For example you could use the x.xx.401.x version so you'll need to change your CID to HTC__001 and your MID to PN0710000 then flash the 1.28.401.7 ruu, remove the tampered flag from the bootloader and set it back to locked (not relocked). Its the closest from stock you can be.
Click to expand...
Click to collapse
is 1.28.401.7 ruu an international version? and does it support arabic?

theevilhere said:
is 1.28.401.7 ruu an international version? and does it support arabic?
Click to expand...
Click to collapse
.401 is the European/WWE international version (world wide english). Im pretty sure it support Arabic.

alray said:
.401 is the European/WWE international version (world wide english). Im pretty sure it support Arabic.
Click to expand...
Click to collapse
and can i change my MID ?

theevilhere said:
and can i change my MID ?
Click to expand...
Click to collapse
yes you can, there is 2 methods to change MID
using this tool from custom recovery
using "dd" commands