Database Develop

[SOLVED] Problems receiving OTA

Hello guys,
So, i might be in a big problem, tried a lot of things. This is my last try to finally get stock again.
I will start with how it began.
When i received my phone, i updated to 4.2.2, hboot 1.54.
After long waiting 1,54 was able to get S-OFF. And i achieved S-OFF successfully --> Flashed latest firmware (3.57.401.500) and flashed the latest
ARHD (30.00).
The new firmware came out, so i wanted to flash that. Once in bootloader I saw that my phone has gone S-ON again? And it really is S-ON.
I've tried flashing the GURU thingy to reset to stock 4.2.2, stock recovery everything. But i still fail to receive the OTA.
So here i am now, hoping you guys have an solution to all this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.57.401.500
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH35MW906757
(bootloader) imei: XXXXXXXXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3897mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6cad6811
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Did you get the popup of OTA?
However, strange that now you're s-on, maybe try to ask beaups.
p.s. For apply ota you need a locked bootloader, is yours?

Guich said:
Did you get the popup of OTA?
However, strange that now you're s-on, maybe try to ask beaups.
p.s. For apply ota you need a locked bootloader, is yours?
Click to expand...
Click to collapse
I have relocked my bootloader.
And i never received a popup for OTA, but since the international version is released, i should have it, IF i am completely stock. But i have no idea how to achieve that, since I tried most of the things already.

So, you've only to wait the popup...
Also other phone didn't get the OTA atm, but they are waiting

Guich said:
So, you've only to wait the popup...
Also other phone didn't get the OTA atm, but they are waiting
Click to expand...
Click to collapse
By other phones you mean other International models? If yes, i probably just have to wait.
But the thing is. I'm worried about that firmware that i flashed? or shouldn't i worry about that.
Thanks for the fast answers!

koenkokes said:
By other phones you mean other International models? If yes, i probably just have to wait.
But the thing is. I'm worried about that firmware that i flashed? or shouldn't i worry about that.
Thanks for the fast answers!
Click to expand...
Click to collapse
Yeah, i mean internationa models with other cid
No problem with the firmware, i think.
Maybe go s-off another time and reflash the 2.24 firmware

Guich said:
Yeah, i mean internationa models with other cid
No problem with the firmware, i think.
Maybe go s-off another time and reflash the 2.24 firmware
Click to expand...
Click to collapse
Hm, then I'll just wait another couple weeks.
And i dont think i can S-OFF now. because of my hboot 1.55 and firmware.

koenkokes said:
Hm, then I'll just wait another couple weeks.
And i dont think i can S-OFF now. because of my hboot 1.55 and firmware.
Click to expand...
Click to collapse
You can
Just check the rumrunners thread and post here the file he need for do the tool for the version main you've

Guich said:
You can
Just check the rumrunners thread and post here the file he need for do the tool for the version main you've
Click to expand...
Click to collapse
And how can I find a link to the corresponding RUU and/or firmware ota package?

koenkokes said:
And how can I find a link to the corresponding RUU and/or firmware ota package?
Click to expand...
Click to collapse
Check also this thread
Edit:
ops sorry, i forgot you've the 2.24 rom installed.

Yeah the thing is.
Stock 4.2.2 rom installed.
Stock 4.2.2 radio
stock kernel.
Unofficial firmware from mike: 3.57.xxx
Hboot 1.55
S-ON
So i'm still not sure IF i can receive OTA. Time will tell i guess.

koenkokes said:
Yeah the thing is.
Stock 4.2.2 rom installed.
Stock 4.2.2 radio
stock kernel.
Unofficial firmware from mike: 3.57.xxx
Hboot 1.55
S-ON
So i'm still not sure IF i can receive OTA. Time will tell i guess.
Click to expand...
Click to collapse
Seems, you've to wait, but i don't know
However, you can always re-unlock your bootloader, flash a 3.57 rom based and send the file to beaups

Guich said:
Seems, you've to wait, but i don't know
However, you can always re-unlock your bootloader, flash a 3.57 rom based and send the file to beaups
Click to expand...
Click to collapse
Will look into it, thanks man.

Update:
Relocked my bootloader, flashed stock recovery, and i received the new 4.3 update.
Now im on firmware 3.62. Managed to S-OFF.
Removed Tampered, and got my device back to LOCK. Seems everything worked perfectly, and there are no traces that i messed with my device

Out of curiosity are you planning on going back to s-on?
I'm hboot 1.55 stock Rom, stock recovery and firmware updated from 1.44 to 1.55 via various ota's. Is it safe to s on from this?

stovie_steve said:
Out of curiosity are you planning on going back to s-on?
I'm hboot 1.55 stock Rom, stock recovery and firmware updated from 1.44 to 1.55 via various ota's. Is it safe to s on from this?
Click to expand...
Click to collapse
I think it would be safe, but why would you? Some devices even ship with S-OFF right out the factory, so doing it for warranty reasons would be useless. But then again, each country handles this differently.

[Q] HTC One unlocked, tampered, S-ON and custom recovery - Can I do OTA

Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND

Torcidas1950 said:
PLEASE RESPOND
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
+ you need stock recovery, ota update will not flash using a custom recovery.
PLEASE SEARCH

alray said:
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
+ you need stock recovery, ota update will not flash using a custom recovery.
PLEASE SEARCH
Click to expand...
Click to collapse
So if I got you right, only thing that matters is that I have stock recovery instead of custom recovery. And how do I do that?

Torcidas1950 said:
So if I got you right, only thing that matters is that I have stock recovery instead of custom recovery.
Click to expand...
Click to collapse
Well yes and no, it depend what you did with your phone, read the link I have posted above, will not write all again
And how do I do that?
Click to expand...
Click to collapse
flash stock recovery the same way you have flashed a custom one
Code:
fastboot flash recovery name_of_recovery.img
you need the recovery that match your present firmware #

Torcidas1950 said:
Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND
Click to expand...
Click to collapse
You should be fully stock, including recovery, before taking an OTA, except that you can (and should) stay s-off and unlocked. You may not even get the OTA otherwise.

So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?

iElvis said:
You should be fully stock, including recovery, before taking an OTA, except that you can (and should) stay s-off and unlocked. You may not even get the OTA otherwise.
Click to expand...
Click to collapse
alray said:
Well yes and no, it depend what you did with your phone, read the link I have posted above, will not write all again
flash stock recovery the same way you have flashed a custom one
Code:
fastboot flash recovery name_of_recovery.img
you need the recovery that match your present firmware #
Click to expand...
Click to collapse
So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?

Torcidas1950 said:
So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?
Click to expand...
Click to collapse
post your "fastboot getvar all" (excluding IMEI and s/n)

nkk71 said:
post your "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
Here it is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(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: 3894mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Torcidas1950 said:
Here it is:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
did you change radio?
hboot 1.55 + MID + CID would indicate you are on 3.xx.502.x version
so i guess: http://d-h.st/D8F or http://d-h.st/6bH would be a suitable recovery, but you need to have your phone's ROM 100% stock

nkk71 said:
did you change radio?
hboot 1.55 + MID + CID would indicate you are on 3.xx.502.x version
so i guess: http://d-h.st/D8F or http://d-h.st/6bH would be a suitable recovery, but you need to have your phone's ROM 100% stock
Click to expand...
Click to collapse
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.

Torcidas1950 said:
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.
Click to expand...
Click to collapse
1- If you are 100% stock then Settings -> About should also show your correct version number
2- you rooted the phone, so that may or may not have changed some system files, so OTA may not work
3- once S-Off stay S-Off, my personal opinion
In my humble opinion, three choices really, when it comes to "modding" or not your phone:
A) stay stock and don't mess with it to get OTAs
B) you cannot achieve S-OFF (due to newer hboots, or device problems) -> fine live with an unlocked bootloader, and accept the fact that you cannot install OTAs .... you can however "download and install later" the OTA, then pull it to your phone, and use the signed firmware.zip in it
C) you can achieve S-OFF and want to mod your phone -> then do it, get S-Off and enjoy the freedom (but don't flash things not meant for your phone!! this goes for S-On too)
Of course you're going to say that "but S-Off is dangerous", it's a double edged sword... sometimes you are able save your phone thanks to S-Off, and sometimes you can brick it completely.
But then again, you can easily brick an S-On phone too (especially one that is modded), and much more difficult to save than an S-Off phone.
^^ All that is my personal opinion, and I'm not suggesting you S-Off, but if you want to mod your phone (whether S-On or S-Off), you need to be aware of what may, or may not, go wrong, and have done some reading and research
Good Luck

Well, its not worth it. I wont risk bricking my phone again

Torcidas1950 said:
Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND
Click to expand...
Click to collapse
Torcidas1950 said:
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.
Click to expand...
Click to collapse
Torcidas1950 said:
Well, its not worth it. I wont risk bricking my phone again
Click to expand...
Click to collapse
Those are completely rhetorical highlights, so you can disregard :cyclops:
Good luck, enjoy, and let us know how the OTA update goes

nkk71 said:
Those are completely rhetorical highlights, so you can disregard :cyclops:
Good luck, enjoy, and let us know how the OTA update goes
Click to expand...
Click to collapse
I will if I eventualy decide to do it, so one last question: can I damage my phone in any way if I try flashing stock reckovery?
Thank you so much for all the information you have given me

Torcidas1950 said:
I will if I eventualy decide to do it, so one last question: can I damage my phone in any way if I try flashing stock reckovery?
Thank you so much for all the information you have given me
Click to expand...
Click to collapse
That's a tough one... cause even if you manage to pull out the cable, at exactly the right (ie wrong) moment while flashing recovery, it wouldn't affect bootloader... and with a good bootloader (hboot, and some other variables) you should be able to revive your phone.... now mess with hboot, and that's a whole different story!!
As I said, this is my personal opinion, so maybe get some second opinions on the subject... I can only answer on what i've done, seen, experienced, fixed, not fixed, etc.
Maybe someone wiser will add his/her opinion to this

nkk71 said:
That's a tough one... cause even if you manage to pull out the cable, at exactly the right (ie wrong) moment while flashing recovery, it wouldn't affect bootloader... and with a good bootloader (hboot, and some other variables) you should be able to revive your phone.... now mess with hboot, and that's a whole different story!!
As I said, this is my personal opinion, so maybe get some second opinions on the subject... I can only answer on what i've done, seen, experienced, fixed, not fixed, etc.
Maybe someone wiser will add his/her opinion to this
Click to expand...
Click to collapse
Well, I am not planing to unplug the cable haha.. well if someone else knows please tell, the update is coming soon so I would like to know, but if its risky, there is no way I'm doing it

Torcidas1950 said:
but if its risky, there is no way I'm doing it
Click to expand...
Click to collapse
I hope you have a sense of humour, so no offense meant, but... why did the chicken cross the street (and was it risky?)
Wish you all the best
nkk71

nkk71 said:
I hope you have a sense of humour, so no offense meant, but... why did the chicken cross the street (and was it risky?)
Wish you all the best
nkk71
Click to expand...
Click to collapse
So, yesterday the OTA was finally released, and today I have flashed stock recovery... Now waiting for the OTA notification to come
Sent from my HTC One using XDA Free mobile app

hello guys,
i did a deep search, but nothing found about it, or found but did not understood, so i will ask you. if in my stock recovery it also says (TAMPER), will be possibly to instal OTA?
L.E. - rest is like the title of the topic - Unlocked, S-ON, tampered..

[Q] Restore to Stock ROM and Lock BL

Hi Everyone,
Okay so I have spent the last 3 hours following various guides in order to restore my ViperOne ROM HTC One M7 to a stock HTC ROM along with locking the bootloader again, everything I've tried has failed though. I'm wondering if anyone here can help me as I need to sell this phone ASAP but can't do that until I restore to stock.
Anyway, the bootloader was unlocked using the HTCDev website and I then installed the custom ROM after that. The Bootloader version appears to be 1.57, not sure if that actually matters.
I tried locking the bootloader which worked and then tried to restore using the O2 UK RUU which failed (The app just crashes at the same point every time).
So I'd really appreciate any help from you guys
Thanks in advance

sheppy1 said:
Hi Everyone,
Okay so I have spent the last 3 hours following various guides in order to restore my ViperOne ROM HTC One M7 to a stock HTC ROM along with locking the bootloader again, everything I've tried has failed though. I'm wondering if anyone here can help me as I need to sell this phone ASAP but can't do that until I restore to stock.
Anyway, the bootloader was unlocked using the HTCDev website and I then installed the custom ROM after that. The Bootloader version appears to be 1.57, not sure if that actually matters.
I tried locking the bootloader which worked and then tried to restore using the O2 UK RUU which failed (The app just crashes at the same point every time).
So I'd really appreciate any help from you guys
Thanks in advance
Click to expand...
Click to collapse
Post a fastboot getvar all with the imei and serialno removed. I am guessing that the RUU you ran was for an earlier version and unless you are S-OFF you can only run RUUs that are same OS version or higher.
You will need to use this guide to return to stock.

majmoz said:
Post a fastboot getvar all with the imei and serialno removed. I am guessing that the RUU you ran was for an earlier version and unless you are S-OFF you can only run RUUs that are same OS version or higher.
You will need to use this guide to return to stock.
Click to expand...
Click to collapse
Hi! Sorry for the late reply, please find below the output that you requested:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 3811mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
You were correct, I was trying to boot a lower version. I heard that people have had luck using Firewater to S-OFF with CM11 installed. It didn't help me though. Anything you might be able to suggest would be a massive help! Thanks

sheppy1 said:
Hi! Sorry for the late reply, please find below the output that you requested:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 3811mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
You were correct, I was trying to boot a lower version. I heard that people have had luck using Firewater to S-OFF with CM11 installed. It didn't help me though. Anything you might be able to suggest would be a massive help! Thanks
Click to expand...
Click to collapse
Based on your getvar all you have a Int'l (.401) phone not an O2 UK branded phone. You will need to follow the directions of this site for stock rom 5.11.401.10 and you should be back whole. You can get the stock firmware if you need it from this site: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One%2F401%2F Just select the 5.11.401.10 firmware.
For S-OFF, you need to be as close to stock as you can. If you are getting "whelp not able to S-OFF" then you might look at Sunshine S-OFF, but there is a price use it.

I realised that I had the international version shortly after posting my information back to you in this thread. Okay so I'm not really interested in getting S-OFF, I only wanted it to be able to use the RUU to restore to stock. So if I just follow method 1 from the post you linked me too, will I be back to get back to stock sense? I assume that I would still see "relocked" and "tampered" in my bootloader?
Thanks for all your help so far!
That worked a charm!!! I'm back on stock FW!!! Thank you! One thing though, will the person I sell the phone too be able to get software updates in future?

sheppy1 said:
I realised that I had the international version shortly after posting my information back to you in this thread. Okay so I'm not really interested in getting S-OFF, I only wanted it to be able to use the RUU to restore to stock. So if I just follow method 1 from the post you linked me too, will I be back to get back to stock sense? I assume that I would still see "relocked" and "tampered" in my bootloader?
Thanks for all your help so far!
That worked a charm!!! I'm back on stock FW!!! Thank you! One thing though, will the person I sell the phone too be able to get software updates in future?
Click to expand...
Click to collapse
If you have stock rom, stock recovery & stock firmware, he/she should be able to get OTA assuming you did not put a custom recovery or root after flashing the stock fw.

majmoz said:
If you have stock rom, stock recovery & stock firmware, he/she should be able to get OTA assuming you did not put a custom recovery or root after flashing the stock fw.
Click to expand...
Click to collapse
That's great news! Would the fact that I ran the stock FW recovery zip from your link mean that I no longer have TWRP on my phone or do I have to do something else to get rid of that too?

sheppy1 said:
That's great news! Would the fact that I ran the stock FW recovery zip from your link mean that I no longer have TWRP on my phone or do I have to do something else to get rid of that too?
Click to expand...
Click to collapse
Yes, you will have stock recovery, stock radio and stock hboot.

majmoz said:
Yes, you will have stock recovery, stock radio and stock hboot.
Click to expand...
Click to collapse
Thanks for all your help!

Should my bootloader still say "tampered"?

sheppy1 said:
Should my bootloader still say "tampered"?
Click to expand...
Click to collapse
Yes, you would have to be S-OFF to reset it.

Okay thank you! Was just thinking that something sill wasn't back to stock so thought I'd check

[Q] No Mainver code! unknown firmware version

Hello everyone,
I have a HTC One M7_UL GSM and I am wanting to upgrade the firmware but I cannot see it when I type the command getvar all, Its just blank next to the Mainver: everything else is showing something there,
I have 1.54 Hboot and am S-OFF with latest twrp 2.8.0.0 and Cyanogenmod 11 (M9 Snapshot Build)
any help greatly appreciated I do not want to mess the phone up.

JamieBlues said:
Hello everyone,
I have a HTC One M7_UL GSM and I am wanting to upgrade the firmware but I cannot see it when I type the command getvar all, Its just blank next to the Mainver: everything else is showing something there,
I have 1.54 Hboot and am S-OFF with latest twrp 2.8.0.0 and Cyanogenmod 11 (M9 Snapshot Build)
any help greatly appreciated I do not want to mess the phone up.
Click to expand...
Click to collapse
Does the phone boot into OS? If so, then it was overwritten during either the flash of an earlier version of TWRP or Cyanogenmod. If you were to flash a new firmware then it would be restored.

majmoz said:
Does the phone boot into OS? If so, then it was overwritten during either the flash of an earlier version of TWRP or Cyanogenmod. If you were to flash a new firmware then it would be restored.
Click to expand...
Click to collapse
Thanks for your reply, It does boot up normally and the phone is perfectly fine so your saying it has been overwritten by either the recovery or custom rom and thats why it isnt showing?
based on this i could flash the latest firmware 6.09.401.5?
Again Thanks.

JamieBlues said:
Thanks for your reply, It does boot up normally and the phone is perfectly fine so your saying it has been overwritten by either the recovery or custom rom and thats why it isnt showing?
based on this i could flash the latest firmware 6.09.401.5?
Again Thanks.
Click to expand...
Click to collapse
As long as it is higher or equal to your version, and if you are s-on you will have to lock your bootloader.

majmoz said:
As long as it is higher or equal to your version, and if you are s-on you will have to lock your bootloader.
Click to expand...
Click to collapse
This is why ive posted this thread mate because i dont know if it is higher or equal as i have said there is no firmware version visable i think it should be fine i cant see me having an earlier version than 6.XXXXX

JamieBlues said:
This is why ive posted this thread mate because i dont know if it is higher or equal as i have said there is no firmware version visable i think it should be fine i cant see me having an earlier version than 6.XXXXX
Click to expand...
Click to collapse
you can more or less infer your firmware version, from hboot version:
hboot 1.44 = 1.xx.xxx.x
hboot 1.54 = 2.xx.xxx.x
hboot 1.55 = 3.xx.xxx.x
hboot 1.56 = 4.xx.xxx.x (in some rare cases 5.xx)
hboot 1.57 = 5.xx.xxx.x and 6.xx.xxx.x
however, i would recommend you flash them incrementally, since firmwares are usually extracted from OTAs they expect the previous changes to already have been applied, so depending on the firmware package you intend on using (some of them have been repackaged to include previous changes), you could end up in trouble.
(for example, flashing a 5.xx ota firmware while on 3.xx or lower firmware will result in QHSUSB_DLOAD mode, and you'd have to try [UNBRICK][BETA] HTC Unbricking Project)
so i recommend you flash them incrementally.

nkk71 said:
you can more or less infer your firmware version, from hboot version:
hboot 1.44 = 1.xx.xxx.x
hboot 1.54 = 2.xx.xxx.x
hboot 1.55 = 3.xx.xxx.x
hboot 1.56 = 4.xx.xxx.x (in some rare cases 5.xx)
hboot 1.57 = 5.xx.xxx.x and 6.xx.xxx.x
however, i would recommend you flash them incrementally, since firmwares are usually extracted from OTAs they expect the previous changes to already have been applied, so depending on the firmware package you intend on using (some of them have been repackaged to include previous changes), you could end up in trouble.
(for example, flashing a 5.xx ota firmware while on 3.xx or lower firmware will result in QHSUSB_DLOAD mode, and you'd have to try [UNBRICK][BETA] HTC Unbricking Project)
so i recommend you flash them incrementally.
Click to expand...
Click to collapse
OK Thanks for the advice still i dont know what firmware it is even if it is 2.XXXXX because im on Hboot 1.54 but i geuss i could start with just one increment up from the lowest 2.XXXXX version only thing is im paranoid about attempting to flash an older firmware and it mess up the phone.
Again a big thanks to everyone who has replied.

JamieBlues said:
OK Thanks for the advice still i dont know what firmware it is even if it is 2.XXXXX because im on Hboot 1.54 but i geuss i could start with just one increment up from the lowest 2.XXXXX version only thing is im paranoid about attempting to flash an older firmware and it mess up the phone.
Again a big thanks to everyone who has replied.
Click to expand...
Click to collapse
are you s-off? then you can flash unsigned firmware, and you can go straight to 3.62.401.1
i personally use these: http://forum.xda-developers.com/showthread.php?t=2365506
(in that thread, even the 6.09.401.5 firmware has all the previous files included so it should be safe to go directly to 6.09, but i personally prefer incremental, just in case)
can you post a "fastboot getvar al"l (excluding IMEI and s/n)
PS: the real problem was for people with 3.xx firmware or lower going to 5.xx firmware (from OTA) which was missing SBL3 from 4.xx (another Secondary Bootloader), which would cause the device to go into QHSUSB_DLOAD

nkk71 said:
are you s-off? then you can flash unsigned firmware, and you can go straight to 3.62.401.1
i personally use these: http://forum.xda-developers.com/showthread.php?t=2365506
(in that thread, even the 6.09.401.5 firmware has all the previous files included so it should be safe to go directly to 6.09, but i personally prefer incremental, just in case)
can you post a "fastboot getvar al"l (excluding IMEI and s/n)
PS: the real problem was for people with 3.xx firmware or lower going to 5.xx firmware (from OTA) which was missing SBL3 from 4.xx (another Secondary Bootloader), which would cause the device to go into QHSUSB_DLOAD
Click to expand...
Click to collapse
Yes i am S-OFF and here is my 'getvar all'
D:\Jay's Data\Android\Fastboot>adb reboot bootloader
D:\Jay's Data\Android\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.5555
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3791mV
(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
all: Done!
finished. total time: 0.069s

JamieBlues said:
Yes i am S-OFF and here is my 'getvar all'
D:\Jay's Data\Android\Fastboot>adb reboot bootloader
D:\Jay's Data\Android\Fastboot>fastboot getvar all
(bootloader) version-bootloader: 1.54.5555
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
all: Done!
finished. total time: 0.069s
Click to expand...
Click to collapse
fyi, looks like you have a rumrunner/firewater ENG hboot in there, that will be gone once you update, you'll be back on normal hboot.
I would personally flash the following versions incrementally from vomers thread
- 3.62.401.1
- 4.19.401.8
- 4.19.401.11
- 5.11.401.10
- 6.09.401.5
(there is some redundancy doing this since the versions from 4.19.401.11 upwards, vomer has included all previous updates too, but better safe than sorry)

nkk71 said:
fyi, looks like you have a rumrunner/firewater ENG hboot in there, that will be gone once you update, you'll be back on normal hboot.
I would personally flash the following versions incrementally from vomers thread
- 3.62.401.1
- 4.19.401.8
- 4.19.401.11
- 5.11.401.10
- 6.09.401.5
(there is some redundancy doing this since the versions from 4.19.401.11 upwards, vomer has included all previous updates too, but better safe than sorry)
Click to expand...
Click to collapse
Thank you so much for all your help i successfully flashed all firmwares incrementally and the phone does feel alot more snappy :laugh:

Can't find RUU

hey xda,
trying to restore my M7 to stock for a warranty repair, but the link to download the Bell nandroid backup of the phone is down. it was HTC1guru but apparently it went down and came back as androidRUU, however all the backups are there except the one I need (but of course, right?). Could anyone please point me to the file I need? Nandroid or RUU is fine.

bbmaster123 said:
hey xda,
trying to restore my M7 to stock for a warranty repair, but the link to download the Bell nandroid backup of the phone is down. it was HTC1guru but apparently it went down and came back as androidRUU, however all the backups are there except the one I need (but of course, right?). Could anyone please point me to the file I need? Nandroid or RUU is fine.
Click to expand...
Click to collapse
We can't help you find the file you need if we don't know your phone details. Post the output of "fastboot getvar all" (remove imei and serialno before posting)

alray said:
We can't help you find the file you need if we don't know your phone details. Post the output of "fastboot getvar all" (remove imei and serialno before posting)
Click to expand...
Click to collapse
I didn't think the rest of the details mattered, but since you asked, here are the details. Original CID was BM__001 before I changed it to superCID
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 4T.33.3218.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.15.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3966mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

bbmaster123 said:
I didn't think the rest of the details mattered, but since you asked, here are the details. Original CID was BM__001 before I changed it to superCID
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-main: 7.15.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) security: off
Click to expand...
Click to collapse
There is no RUU for Bell (x.xx.666.x), Only a 3.23.666.1 nandroid backup is available which is useless in your situation. After restoring that nandroid backup, your firmware will still be that leaked 7.15.401.1 version and will not match the 3.23.666.1 software version which will void the warranty. You'll also need to set your bootloader back to "LOCKED" and remove your "TAMPERED" flag which should be done on hboot 1.44 or 1.54 like explained in nkk71's guide.

alray said:
There is no RUU for Bell (x.xx.666.x), Only a 3.23.666.1 nandroid backup is available which is useless in your situation. After restoring that nandroid backup, your firmware will still be that leaked 7.15.401.1 version and will not match the 3.23.666.1 software version which will void the warranty. You'll also need to set your bootloader back to "LOCKED" and remove your "TAMPERED" flag which should be done on hboot 1.44 or 1.54 like explained in nkk71's guide.
Click to expand...
Click to collapse
thats fine, I can reflash my firmware. I know how to do all of this, I just need the file, but as I said, since the htc1guru server is down, I can't find it.

bbmaster123 said:
thats fine, I can reflash my firmware. I know how to do all of this, I just need the file, but as I said, since the htc1guru server is down, I can't find it.
Click to expand...
Click to collapse
But there is no 3.23.666.1 firmware uploaded anywhere, only a Nandroid backup (which does NOT include the firmware, only the software) so how will you reflash the stock 3.23.666.1 firmware over you 7.15.401.1 firmware?
For the nandroid backup, you'll have to wait for htc1guru.com to be back online.

alray said:
But there is no 3.23.666.1 firmware uploaded anywhere, only a Nandroid backup (which does NOT include the firmware, only the software) so how will you reflash the stock 3.23.666.1 firmware over you 7.15.401.1 firmware?
For the nandroid backup, you'll have to wait for htc1guru.com to be back online.
Click to expand...
Click to collapse
huh, I think I found a TWRP backup of the stock OS. Downloading now. Will check if it includes the firmware. its strange, it din't show up in a google search of of the ruu, but came up when I searched for 3.23.666.1. I will post the link if its the right file

bbmaster123 said:
huh, I think I found a TWRP backup of the stock OS. Downloading now. Will check if it includes the firmware. its strange, it din't show up in a google search of of the ruu, but came up when I searched for 3.23.666.1. I will post the link if its the right file
Click to expand...
Click to collapse
TWRP backups never includes the firmware. Only include /data partition (user data), /system partition (software aka Operating System) and /boot partition (kernel).

alray said:
TWRP backups never includes the firmware. Only include /data partition (user data), /system partition (software aka Operating System) and /boot partition (kernel).
Click to expand...
Click to collapse
yea, your right. now the hunt has changed from nandroid backup to firmware. I will scour and report my findings.

bbmaster123 said:
yea, your right. now the hunt has changed from nandroid backup to firmware. I will scour and report my findings.
Click to expand...
Click to collapse
so you'll need to find at least a firmware.zip and a nandroid backup of the same version, restoring the backup using the appropriate recovery and flashing the firmware.zip with fastboot with the phone booted in ruu mode. Don't ever think about using a firmware.zip from an ota update or you will brick your phone. Good luck.

alray said:
so you'll need to find at least a firmware.zip and a nandroid backup of the same version, restoring the backup using the appropriate recovery and flashing the firmware.zip with fastboot with the phone booted in ruu mode. Don't ever think about using a firmware.zip from an ota update or you will brick your phone. Good luck.
Click to expand...
Click to collapse
I believe I found it, but I want to be sure. Why would an OTA version of the firmware brick the phone? heres the link for the file I found
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/666/3.23.666.1.zip

bbmaster123 said:
I believe I found it, but I want to be sure. Why would an OTA version of the firmware brick the phone? heres the link for the file I found
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/666/3.23.666.1.zip
Click to expand...
Click to collapse
Im not sure if that is OTA or Full firmware, im not too upto speed with firmware packages, but to answer your question, OTA firmware just upgrades the original firmware on your device, so its not a complete firmware package (which is what you need), and as you dont have the original firmware, it would just brick.
Could you not get away with using dev edition RUU and sending it back like that, dev edition devices come s-off and unlocked, the tampered flag is easy to remove, if they question it, deny any knowlege.

Seanie280672 said:
Im not sure if that is OTA or Full firmware, im not too upto speed with firmware packages, but to answer your question, OTA firmware just upgrades the original firmware on your device, so its not a complete firmware package (which is what you need), and as you dont have the original firmware, it would just brick.
Could you not get away with using dev edition RUU and sending it back like that, dev edition devices come s-off and unlocked, the tampered flag is easy to remove, if they question it, deny any knowlege.
Click to expand...
Click to collapse
thats a good idea, but I got impatient and just flashed everything. turns out it works fine. now ill just run the stock ota updates from the settings menu and s-on and lock the bootloader. I should probably make a new thread with instructions to return to stock bell and host post the nandroid and firmware. thanks for your help! now that I'm thinking about it, I should go back to all my previous threads and hit the thanks button for everyone who helped me!

bbmaster123 said:
thats a good idea, but I got impatient and just flashed everything. turns out it works fine. now ill just run the stock ota updates from the settings menu and s-on and lock the bootloader. I should probably make a new thread with instructions to return to stock bell and host post the nandroid and firmware. thanks for your help! now that I'm thinking about it, I should go back to all my previous threads and hit the thanks button for everyone who helped me!
Click to expand...
Click to collapse
you need to go locked and s-on before the OTA's, if you go s-on after HBOOT 1.54 the tampered flag will come back and you'll have to get s-off again and start all over.
Have a look at post 2 by @alray he has a link in his signature by nkk71 of how to return to 100% stock which contains all the instructions

Seanie280672 said:
Could you not get away with using dev edition RUU and sending it back like that, dev edition devices come s-off and unlocked, the tampered flag is easy to remove, if they question it, deny any knowlege.
Click to expand...
Click to collapse
Afaik they come unlocked but not s-off. Anyway converting it to full dev edition might be the best solution at this point. Customer support often repair modded phones depending what is broken. For the purple camera for example, some users got their phone repaired under warranty even if the phone was not stock.
bbmaster123 said:
thats a good idea, but I got impatient and just flashed everything. turns out it works fine. now ill just run the stock ota updates from the settings menu and s-on and lock the bootloader.
Click to expand...
Click to collapse
You can't !
Your firmware is 7.15.401.1, To use ota update firmware must match the software version. The ota need to patch the 3.23.666.1 firmware not the 7.15.401.1 firmware.
unless you have flashed the 3.23.666.1 firmware then you should be fine. You must make sure that firmware file is the FULL firmware and not a firmware extracted from an ota update before flashing.

alray said:
Afaik they come unlocked but not s-off. Anyway converting it to full dev edition might be the best solution at this point. Customer support often repair modded phones depending what is broken. For the purple camera for example, some users got their phone repaired under warranty even if the phone was not stock.
You can't !
Your firmware is 7.15.401.1, To use ota update firmware must match the software version. The ota need to patch the 3.23.666.1 firmware not the 7.15.401.1 firmware.
unless you have flashed the 3.23.666.1 firmware then you should be fine. You must make sure that firmware file is the FULL firmware and not a firmware extracted from an ota update before flashing.
Click to expand...
Click to collapse
I already flashed the 3.23.666.1 firmware, and it worked. I already went through the first round of the update process, now its downloading the OTA for kitkat. still s-off right now. bootloader is still unlocked too.

bbmaster123 said:
I already flashed the 3.23.666.1 firmware, and it worked. I already went through the first round of the update process, now its downloading the OTA for kitkat. still s-off right now. bootloader is still unlocked too.
Click to expand...
Click to collapse
I'm looking forward to your post with all the links and instructions ... good job