Related
I have the following setup:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.16.3250.24
version-cpld: None
version-microp: None
version-main: 2.24.401.1
version-misc: PVT SHIP S-OFF
serialno: MEH
imei: MEH
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: 11111111
battery-status: good
battery-voltage: 4324mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
all: Done!
I have been reading around about HBOOT 1.54 and am wondering if anyone can give me a pros and cons list of going from 1.44 to 1.54 would be?
Thanks
incarceration said:
I have the following setup:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.16.3250.24
version-cpld: None
version-microp: None
version-main: 2.24.401.1
version-misc: PVT SHIP S-OFF
serialno: MEH
imei: MEH
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: 11111111
battery-status: good
battery-voltage: 4324mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
all: Done!
I have been reading around about HBOOT 1.54 and am wondering if anyone can give me a pros and cons list of going from 1.44 to 1.54 would be?
Thanks
Click to expand...
Click to collapse
you can change your hboot to 1.54 during upgrading your firmware to 2.24(it comes together)
you can find steps there:
http://forum.xda-developers.com/showthread.php?t=2365506
good luck
99piotrek said:
you can change your hboot to 1.54 during upgrading your firmware to 2.24(it comes together)
Click to expand...
Click to collapse
Thanks. But I know how to do it, I'm just wondering if there are any pros or cons of going to the 1.54 HBOOT from 1.44
incarceration said:
Thanks. But I know how to do it, I'm just wondering if there are any pros or cons of going to the 1.54 HBOOT from 1.44
Click to expand...
Click to collapse
I believe the 1.54 cannot be S-OFF'd
killman2659 said:
I believe the 1.54 cannot be S-OFF'd
Click to expand...
Click to collapse
Ah ok. That's what I was looking to confirm.
Do you know anything of an ENG BOOT? Any pros\cons for that?
incarceration said:
Thanks. But I know how to do it, I'm just wondering if there are any pros or cons of going to the 1.54 HBOOT from 1.44
Click to expand...
Click to collapse
The latest firmware brings updated touch screen drivers and a newer radio amongst other things and it's worth flashing for that alone as many feel it makes the device feel that little bit snappier. If you already have s-off then you won't lose that updating the firmware but if you haven't then you will not be able to s-off with hboot 1.54 at the moment so s-off before updating.
However available roms based on 2.24 will run ok on your existing firmware and the radios can be flashed independently so it's not essential to update if you're happy with your current setup.
Regarding the eng hboot I would advise against that as any modified hboot brings with it an increased risk of permanently bricking.
Most say that updating the firmware improves the device but as I say it's not essential at the moment so basically it's your choice.
incarceration said:
Do you know anything of an ENG BOOT? Any pros\cons for that?
Click to expand...
Click to collapse
There is no eng hboot for this phone, at least not one that will boot.
Sent from my Nexus 7 using Tapatalk HD
rider5512 said:
The latest firmware brings updated touch screen drivers and a newer radio amongst other things and it's worth flashing for that alone as many feel it makes the device feel that little bit snappier. If you already have s-off then you won't lose that updating the firmware but if you haven't then you will not be able to s-off with hboot 1.54 at the moment so s-off before updating.
However available roms based on 2.24 will run ok on your existing firmware and the radios can be flashed independently so it's not essential to update if you're happy with your current setup.
Regarding the eng hboot I would advise against that as any modified hboot brings with it an increased risk of permanently bricking.
Most say that updating the firmware improves the device but as I say it's not essential at the moment so basically it's your choice.
Click to expand...
Click to collapse
Thanks a lot for the clarification!
I flashed the "Combo" RUU from this thread (http://forum.xda-developers.com/showthread.php?t=2316726) and removed the HBOOT and Recovery images from them to avoid updating my HBOOT and overwriting my current custom recovery.
Does this still achieve what you noted in the first paragraph of your response? Do I have to update my HBOOT to achieve any other benefits? I guess I'm just trying to get at, what exactly does updating the HBOOT (the phone's bootloader) achieve?
Currently as I see it, I see the "firmware" as something other than the "HBOOT" (the other files within that same "Combo" RUU), correct?
incarceration said:
Thanks a lot for the clarification!
I flashed the "Combo" RUU from this thread (http://forum.xda-developers.com/showthread.php?t=2316726) and removed the HBOOT and Recovery images from them to avoid updating my HBOOT and overwriting my current custom recovery.
Does this still achieve what you noted in the first paragraph of your response? Do I have to update my HBOOT to achieve any other benefits? I guess I'm just trying to get at, what exactly does updating the HBOOT (the phone's bootloader) achieve?
Currently as I see it, I see the "firmware" as something other than the "HBOOT" (the other files within that same "Combo" RUU), correct?
Click to expand...
Click to collapse
I'm not sure to be honest as I always flash the full firmware package so I don't know if there will be any mismatch if the hboot has been left out.
If you are already s-off then I would flash the full 2.24 firmware package from the thread you quoted and then reflash your recovery in fastboot (no need to reboot into RUU mode) either CWM here or TWRP here following finally by flashing your rom
I can't open the link to download the firmware package for that post..... I used this 2.24 firmware package which I assume is the same as in the page you used but I would suggest this as I know it works fine
I stumbled across this when trying to find out what parts do what and are apart of what:
http://forum.xda-developers.com/showpost.php?p=43328416&postcount=3375
Apparently the HBOOT is part of the "firmware"
So again, if I update the HBOOT to 1.54 from 1.44, could I theoretically go back and forth between 1.54 and 1.44 whilst S-OFF?
EDIT: I just upgraded using the RUU from the link I posted, using the non-"combo" version.
I modified the android-info.txt to match my CID with the SuperCID I currently have, and I reinstalled my choice of recovery afterwards (TWRP, same version I had before.)
I'm now getting these 2 lines at the end of my 'getvar all' command via FASTBOOT:
commitno-bootloader: dirty-d16dc66985
hbootpreupdate: 11
what do those lines mean?
EDIT #2: I successfully switched back to HBOOT 1.44 whilst still S-OFF and got rid of those weird messages
C:\droidsdk\sdk\platform-tools>fastboot getvar all
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.17.3250.14
version-cpld: None
version-microp: None
version-main: 2.24.401.1
version-misc: PVT SHIP S-OFF
serialno: nah bro
imei: nah bro
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: 11111111
battery-status: good
battery-voltage: 4233mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
all: Done!
finished. total time: 2.771s
here's a random, somewhat related question from left field
incarceration said:
I stumbled across this when trying to find out what parts do what and are apart of what:
http://forum.xda-developers.com/showpost.php?p=43328416&postcount=3375
Apparently the HBOOT is part of the "firmware"
So again, if I update the HBOOT to 1.54 from 1.44, could I theoretically go back and forth between 1.54 and 1.44 whilst S-OFF?
EDIT: I just upgraded using the RUU from the link I posted, using the non-"combo" version.
I modified the android-info.txt to match my CID with the SuperCID I currently have, and I reinstalled my choice of recovery afterwards (TWRP, same version I had before.)
I'm now getting these 2 lines at the end of my 'getvar all' command via FASTBOOT:
commitno-bootloader: dirty-d16dc66985
hbootpreupdate: 11
what do those lines mean?
EDIT #2: I successfully switched back to HBOOT 1.44 whilst still S-OFF and got rid of those weird messages
C:\droidsdk\sdk\platform-tools>fastboot getvar all
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.17.3250.14
version-cpld: None
version-microp: None
version-main: 2.24.401.1
version-misc: PVT SHIP S-OFF
serialno: nah bro
imei: nah bro
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: 11111111
battery-status: good
battery-voltage: 4233mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
all: Done!
finished. total time: 2.771s
Click to expand...
Click to collapse
I have the 64 gb dev edition, non-carrier branded and using TMO network. Already updated to 2.24 with AndroidRevo12 and didn't have S-Off first, so I gather there's no going there for now w/o going back to pre-2.24. But the whole reason I started down that road was cuz I thought I needed S-Off to flash radio by itself. I just want the new radio for the LTE bump since I seem to have such good LTE coverage at home and work.
If I don't need S-off to flash radio as "that can be done independently," then can you offer any possible reasons why I'm getting a signature verify fail when trying to push first revone (via adb), then later (once I gave up on S-off) while trying to flash the new radio.img fia fastboot?
(radio img is the new TMOUS 4A.17.3250.20_10.440.1150.04L)
Fastboot and adb seem to be fine otherwise, and phone settings are all proper (debug/etc). Bootloader obviously unlocked, etc...HBOOT is 1.44.
Good morning people
Let me first get my story done
I had a unlocked htc one with maximusHD on, But I wanted to go back to complete Stock so i ran the RUU. I'm now on android 4.1.2 (the version i had when i bought the phone) and im not recieving any OTA updates (ive had one before when the phone was still stock to android 4.2.2 or 4.2.1 not completely sure anymore)
Below ill post some details of the version ive got now on my phone
android version: 4.1.2
software number: 1.20.401.1
kernel version 3.4.10-gc81fffd
baseband version: 4a.13.3227.06_10.27.1127.01L
build number: 1.20.401.1 CL156395
Fastboot Getvar all:
version: 0.5
version-bootloader: 1.43.0000
version-baseband: 4A.13.3227.06
version-cpld: None
version-microp: None
version-main: 1.20.401.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__E11
battery-status: good
battery-voltage: 4286mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
name of the RUU i installed
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4 (downloaded from htc1guru)
I hope you people can help me to recieve OTA updates again on my phone
If i havent posted something above (i think i posted all relevant things) pls give me a shout and ill post them
Regards
frayful
frayful said:
Good morning people
Let me first get my story done
I had a unlocked htc one with maximusHD on, But I wanted to go back to complete Stock so i ran the RUU. I'm now on android 4.1.2 (the version i had when i bought the phone) and im not recieving any OTA updates (ive had one before when the phone was still stock to android 4.2.2 or 4.2.1 not completely sure anymore)
Below ill post some details of the version ive got now on my phone
android version: 4.1.2
software number: 1.20.401.1
kernel version 3.4.10-gc81fffd
baseband version: 4a.13.3227.06_10.27.1127.01L
build number: 1.20.401.1 CL156395
Fastboot Getvar all:
version: 0.5
version-bootloader: 1.43.0000
version-baseband: 4A.13.3227.06
version-cpld: None
version-microp: None
version-main: 1.20.401.1
version-misc: PVT SHIP S-ON
serialno: FAxxxxxxxxxxxxxxxxxxxxx
imei: 3xxxxxxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__E11
battery-status: good
battery-voltage: 4286mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
name of the RUU i installed
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4 (downloaded from htc1guru)
I hope you people can help me to recieve OTA updates again on my phone
If i havent posted something above (i think i posted all relevant things) pls give me a shout and ill post them
Regards
frayful
Click to expand...
Click to collapse
hey mate, edit your post and remove IMEI and serial number, we don't need to see those.
Anyway, most of the details you showed look just fine, except hboot 1.43 As far as I know the lowest hboot for the One is 1.44
You may want to try this RUU instead (slightly newer, but still for you MID & CID): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
Remember that since you're S-On this (and any OTA after) is a one way trip, ie you can upgrade, but cannot downgrade.
And of course you're bootloader has to be locked/relocked to be able to run the RUU.
nkk71 said:
hey mate, edit your post and remove IMEI and serial number, we don't need to see those.
Anyway, most of the details you showed look just fine, except hboot 1.43 As far as I know the lowest hboot for the One is 1.44
You may want to try this RUU instead (slightly newer, but still for you MID & CID):
Remember that since you're S-On this (and any OTA after) is a one way trip, ie you can upgrade, but cannot downgrade.
And of course you're bootloader has to be locked/relocked to be able to run the RUU.
Click to expand...
Click to collapse
Evening i tried the RUU that you suggested
still hboot 1.43 and no OTA updates
anymore ideas?
regards,
frayful
Flash hboot 1.44 and then try the 1.28.401.7 RUU. That's how I got my device back to stock 4.1.2 and then got 4 OTA updates
1. 1.29.401.1
2. 2.24.401.1
3. 2.24.401.8
4. 3.62.401.1
Sent from my HTC One using Tapatalk
Ivanovic said:
Flash hboot 1.44 and then try the 1.28.401.7 RUU. That's how I got my device back to stock 4.1.2 and then got 4 OTA updates
1. 1.29.401.1
2. 2.24.401.1
3. 2.24.401.8
4. 3.62.401.1
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
i am trying to do that. I tried flashing a hboot 1.44 but i flash it it says okay i reboot back to bootloader it still says hboot 1.43
any thoughts
regards,
Frayful
How do you flash it? Fastboot flash zip filename.zip?
You 've go to do this twice
Sent from my HTC One using Tapatalk
Ivanovic said:
How do you flash it? Fastboot flash zip filename.zip?
You 've go to do this twice
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
i did fastboot oem rebootRUU
fastboot flash zip filename twice
fastboot reboot-bootloader
still says 1.43
But im going to look for another hboot to be sure
regards
If you want I can upload the file I used
Sent from my HTC One using Tapatalk
Ivanovic said:
If you want I can upload the file I used
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
that would be very helpfull bud
(btw cheers for the help and quick replies so far)
regards,
frayful
Here you are http://www60.zippyshare.com/v/66756398/file.html
I downgraded from 1.55 to 1.44 yesterday just fine
Ivanovic said:
Here you are http://www60.zippyshare.com/v/66756398/file.html
I downgraded from 1.55 to 1.44 yesterday just fine
Click to expand...
Click to collapse
cheers man that hboot worked like a charm
im having dinner now but ill try the OTA after my dinner and ill get back to you if it worked or not
regards,
frayful
Just use the 1.28.401.7 RUU and you 'll be fine! Enjoy your dinner
Sent from my HTC One using Tapatalk
Ivanovic said:
Just use the 1.28.401.7 RUU and you 'll be fine! Enjoy your dinner
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
yup works bud downloading the first ota update as we speak
u rock!
regards,
frayful
Hi guys, byesterday I did full backing to stock using this guide (http://forum.xda-developers.com/showthread.php?t=2541082) and everything works perfect (Locked, S-On, removed tamperer...) except thing that I not receiving any OTA.
I checked my getvar all and saw that my hboot is 1.43.
Here is mu getvar all:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.43.0000
(bootloader) version-baseband: 4A.13.3227.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.20.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA********
(bootloader) imei: 35************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4311mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.048s
I have 2 questions: Can I upgrade hboot (1.43) to 1.44 and run correct RUU with Locked Bootloader and S-on or I have to unlock bootloader again, root phone get s-off...?
And if i need to do all of this again, can you provide me the easiest way (links)?
I need to get back my Htc ONE to RMA (camera issue)..
Thanks!!
djmeex said:
Hi guys, byesterday I did full backing to stock using this guide (http://forum.xda-developers.com/showthread.php?t=2541082) and everything works perfect (Locked, S-On, removed tamperer...) except thing that I not receiving any OTA.
Thanks!!
Click to expand...
Click to collapse
Answered you in my thread.
cheers
So I want to revert back to stock, and get OTA updates, but I cannot find the RUU for my Internation HTC one, if you can find it, it will help. Thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4052mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
ShaheenXE said:
So I want to revert back to stock, and get OTA updates, but I cannot find the RUU for my Internation HTC one, if you can find it, it will help. Thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVE THIS
(bootloader) imei: REMOVE THIS
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4052mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
First see red text above, its dangerous to post that info
second, you didn't look very hard, this rom is the easiest stock rom to find, you can either try running this RUU
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
if that fails, flash the reset file below link through TWRP recovery 2.6.3.3
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Both those links are for the following devices
modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016
Seanie280672 said:
First see red text above, its dangerous to post that info
second, you didn't look very hard, this rom is the easiest stock rom to find, you can either try running this RUU
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
if that fails, flash the reset file below link through TWRP recovery 2.6.3.3
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Click to expand...
Click to collapse
Nope mate, that won't work, he's S-On
EDIT, unless there is a OTA 4.19.401.11_3.62.401.1 (but i don't think there is)
nkk71 said:
Nope mate, that won't work, he's S-On
EDIT, unless there is a OTA 4.19.401.11_3.62.401.1 (but i don't think there is)
Click to expand...
Click to collapse
he can use the guru reset file to go back to 3.62.401.1 and then OTA all the way from there, I did the same myself before I went s-off to get an OTA, I did notice he has 11 where as the RUU is 9, unfortunately 11 was a small OTA from 9 but thought it was worth a try.
Seanie280672 said:
he can use the guru reset file to go back to 3.62.401.1 and then OTA all the way from there, I did the same myself before I went s-off to get an OTA, I did notice he has 11 where as the RUU is 9, but thought it was worth a try.
Click to expand...
Click to collapse
the Guru Reset ROM could work, if he get's a notification to 4.19.401.11... but if there's an OTA version in between the two, it could fail because of the "version" downgrade
EDIT, true it's a small upgrade, so both your ideas could work, but for the RUU.EXE to work, he would need to use the misctool to change version-main to something lower, otherwise the ruu.exe won't let it through.
nkk71 said:
the Guru Reset ROM could work, if he get's a notification to 4.19.401.11... but if there's an OTA version in between the two, it could fail because of the "version" QUOTE
EDIT, true it's a small upgrade, so both your ideas could work, but for the RUU.EXE to work, he would need to use the misctool to change version-main to something lower, otherwise the ruu.exe won't let it through.
Click to expand...
Click to collapse
Damn this is confusing guys I just have no idea what to do
ShaheenXE said:
Damn this is confusing guys I just have no idea what to do
Click to expand...
Click to collapse
yep, sorry about that, I guess you could try the Guru Reset ROM and see if the OTA works, since the 4.4 RUUs are extremely sensitive.
but out of curiosity, why do you need stock and get OTAs? (and why no S-Off?)
nkk71 said:
yep, sorry about that, I guess you could try the Guru Reset ROM and see if the OTA works, since the 4.4 RUUs are extremely sensitive.
but out of curiosity, why do you need stock and get OTAs? (and why no S-Off?)
Click to expand...
Click to collapse
Well I have 2 HTC ones (both rooted with custom ROMs) I wanted to get back to stock and do some tests. And I really actually don't know why I don't have s-off, I think because it's just that I'm not bothered to get it, so I just unlocked bootloader via HTC dev.
ShaheenXE said:
Well I have 2 HTC ones (both rooted with custom ROMs) I wanted to get back to stock and do some tests. And I really actually don't know why I don't have s-off, I think because it's just that I'm not bothered to get it, so I just unlocked bootloader via HTC dev.
Click to expand...
Click to collapse
Well you already know my answer to S-Off: if you can get it, then do it.... with S-Off you wouldn't even need this thread, you'd just flash an old ruu and you are done.
hboot 1.56 is already tough to get S-Off, but hboot 1.57 (the one you'll get once you receive the 5.xx OTA, is even tougher/close-to-impossible)
but if you don't want to be bothered with that, I personally would try the Guru Reset ROM, and see how that works out.
I saw a 4.19.401.? guru reset rom around these forums somewhere created by crushalot an updated one and im buggered if I can find it, it doesn't seem to be on his site yet, there was a backup and a guru reset of it in the same thread.
Seanie280672 said:
I saw a 4.19.401.? guru reset rom around these forums somewhere created by crushalot an updated one and im buggered if I can find it, it doesn't seem to be on his site yet, there was a backup and a guru reset of it in the same thread.
Click to expand...
Click to collapse
hmm, yellow card to myself (over thinking stuff)
why not just flash the 4.19.401.11 stock odexed rom + stock recovery, and be done with it?
nkk71 said:
hmm, yellow card to myself (over thinking stuff)
why not just flash the 4.19.401.11 stock odexed rom + stock recovery, and be done with it?
Click to expand...
Click to collapse
lol story of my life.
Seanie280672 said:
lol story of my life.
Click to expand...
Click to collapse
ShaheenXE said:
Well I have 2 HTC ones (both rooted with custom ROMs) I wanted to get back to stock and do some tests. And I really actually don't know why I don't have s-off, I think because it's just that I'm not bothered to get it, so I just unlocked bootloader via HTC dev.
Click to expand...
Click to collapse
Sorry for over-thinking this one, i guess i couldn't see the forest through the trees
Just install "One_4.19.401.11_odexed.zip" using custom recovery (I have a copy of the file if you can't find it online, but would take hours to upload, and i'm sure a simple search will find it; just make sure it's the HTC One M7 ROM... the one I have has MD5=DEBE52CBCA078E3B64C78AC06DFA1D42),
EDIT: http://www.androidfilehost.com/?fid=23501681358545504
then flash stock recovery: http://d-h.st/Igg and you're done.
Will this definitely work, I really don't wanna get my phones bricked
Sent from my HTC One using XDA Free mobile app
ShaheenXE said:
Will this definitely work, I really don't wanna get my phones bricked
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
yep, should work fine.
Since you are S-On with "(bootloader) version-main: 4.19.401.11" means you couldn't have messed around with firmware, and the above odexed ROM is stock ROM for your MID+CID.
Once you have the ROM installed you will get the OTA update notification, but it won't install until you flash back the stock recovery (OTA updates don't work with custom recovery)
---------- Post added at 04:05 PM ---------- Previous post was at 03:51 PM ----------
ShaheenXE said:
Will this definitely work, I really don't wanna get my phones bricked
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
EDIT: or this one: http://www.androidfilehost.com/?fid=23501681358545524
has the option to install stock recovery during the installation
So do I just install this via TWRP?
Sent from my HTC One using XDA Free mobile app
Do I flash stock recovery just like another recovery e.g fast boot flash recovery therecovery.img
Sent from my HTC One using XDA Free mobile app
ShaheenXE said:
So do I just install this via TWRP?
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
yep exactly. just like any ROM. if you use the Guru Reset ROM, during installation it will give you the option to install stock recovery as well, then you can get and install the OTA
Thank you so much for your help, hope this works
Sent from my HTC One using XDA Free mobile app
Hello, first let me apologize if this issue has been covered already,
I've been searching for a solution more than a week and going over dozens threads here on XDA without finding an answer for my problem.
i have o2uk m7ul with hboot 1.57, emmc 9001 running stock rooted 4.4.2, twpr recovery, tempered and unlocked by htcdev and im looking for a way to go stock so i can update my rom and fw
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.206.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3836mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
this is what i've tried so far, please tell me if im missing something
1. i cant s-off the device with firewater or similar due to my emmc, although i didnt tried yet flashing bulletproof or cm nightly kernels (reading users feedback it didn't helped with this specific emmc)
2. i can relock, unroot and try to OTA, but i need the original recovery which i can't find for my device, i found an old recovery but probably ota will fail.
3. i have identical stock device, but i can't pull the recovery from it due to the hboot 1.57 version.
4. i can flash 4.4.3 custom rom or even stock rom but it won't update my firmware - firmware flashing is impossible (s-on)
5. i have o2 ruu.exe for KK4.4 sense 5.5, is it safe to oem lock and run it from fastboot? or i'll brick my device? if it is safe to use the RUU, will updating from 4.4 to 4.4.2 and then to 4.4.3 with OTA possible?
sh33z0r said:
Hello, first let me apologize if this issue has been covered already,
I've been searching for a solution more than a week and going over dozens threads here on XDA without finding an answer for my problem.
i have o2uk m7ul with hboot 1.57, emmc 9001 running stock rooted 4.4.2, twpr recovery, tempered and unlocked by htcdev and im looking for a way to go stock so i can update my rom and fw
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.206.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3836mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
this is what i've tried so far, please tell me if im missing something
1. i cant s-off the device with firewater or similar due to my emmc, although i didnt tried yet flashing bulletproof or cm nightly kernels (reading users feedback it didn't helped with this specific emmc)
2. i can relock, unroot and try to OTA, but i need the original recovery which i can't find for my device, i found an old recovery but probably ota will fail.
3. i have identical stock device, but i can't pull the recovery from it due to the hboot 1.57 version.
4. i can flash 4.4.3 custom rom or even stock rom but it won't update my firmware - firmware flashing is impossible (s-on)
5. i have o2 ruu.exe for KK4.4 sense 5.5, is it safe to oem lock and run it from fastboot? or i'll brick my device? if it is safe to use the RUU, will updating from 4.4 to 4.4.2 and then to 4.4.3 with OTA possible?
Click to expand...
Click to collapse
you should try what said at #5
#4: not true, you can flash firmware on s-on as long as the firmware is signed (from htc) and same or higher version
regarding s-off, i think its now posible for 9001 emmc using sunshine s-off, but its a paid exploit (25 usd)
alray said:
you should try what said at #5
#4: not true, you can flash firmware on s-on as long as the firmware is signed (from htc) and same or higher version
regarding s-off, i think its now posible for 9001 emmc using sunshine s-off, but its a paid exploit (25 usd)
Click to expand...
Click to collapse
thanks for the quick reply, much appreciated.
are those firmwares that posted under development sub forum (with no red text/no warning...) are signed by htc? is the firmware need to mach my specific cid as OTA? or i can flash without worrying to much since its higher than my 5.12 firmware?
You need x.x.206.x firmware.zip which is higher than your current firmware. With s-on, you are stuck like that
SaHiLzZ said:
You need x.x.206.x firmware.zip which is higher than your current firmware. With s-on, you are stuck like that
Click to expand...
Click to collapse
thanks! so it seems there is no new firmware for the o2uk devices atm...
just out of curiosity, is there any difference between the firmwares? lets say between the x.x.206.x and x.x.401.x versions? are those versions dedicated to regions? NA/europe/asia?
if i was with s-off, flashing 401 firmware can damage my radio or anything else?
save yourself the headaches and get s-off.
ok small update, i got the ota (ver: 6.14.206.2) file, i've extracted the firmware.zip file and tried to flash it but it failed time after time, any special preps for it? do i need to relock my bootloader before flashing firmware.zip?
ok so just to end up my story with a solution, as i wasn't able to flash firmware, i've tried one last thing.
1. extracting from firmware file the recovery image and flashing it
2. fastboot oem lock
3. applying OTA, i was sure it will fail, but it didnt, it applied the OTA even without unrooting
so bottom line, im on stock 4.4.3 right now with new 6.14.206.2 firmware, lost my root though...
sh33z0r said:
ok so just to end up my story with a solution, as i wasn't able to flash firmware, i've tried one last thing.
1. extracting from firmware file the recovery image and flashing it
2. fastboot oem lock
3. applying OTA, i was sure it will fail, but it didnt, it applied the OTA even without unrooting
so bottom line, im on stock 4.4.3 right now with new 6.14.206.2 firmware, lost my root though...
Click to expand...
Click to collapse
Hi, do you have a link to the recovery image that you extracted? I'm trying to what you have done here as I'm in the same position. Tks.
Hi,i have an htc one m7 that I recently decided to unlock the bootloader and root. I left the phone with S-on, Everything was going smoothly until today I decided to install a custom rom. I used the latest twrp and flashed venom. My phone is now stuck in a bootloop. I have tried several diferent roms and even tried flashing using fastboot. I still have acess to my hboot screen and recovery, fastboot, etc. I just cannot get the phone to boot. It is stuck in a bootloop, it stays on the splash screen for maybe 15 seconds then restarts. Any and all assistance is greatly appreciated. I am hoping to get this resolved as soon as possible.
zshep99 said:
Hi,i have an htc one m7 that I recently decided to unlock the bootloader and root. I left the phone with S-on, Everything was going smoothly until today I decided to install a custom rom. I used the latest twrp and flashed venom. My phone is now stuck in a bootloop. I have tried several diferent roms and even tried flashing using fastboot. I still have acess to my hboot screen and recovery, fastboot, etc. I just cannot get the phone to boot. It is stuck in a bootloop, it stays on the splash screen for maybe 15 seconds then restarts. Any and all assistance is greatly appreciated. I am hoping to get this resolved as soon as possible.
Click to expand...
Click to collapse
Fastboot getvar all and Post it here without IMEI
Sent from my XT1254 using Tapatalk
KARIM9377 said:
Fastboot getvar all and Post it here without IMEI
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.02.20.0922
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA388S903555
(bootloader) meid: 99000146074275
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
zshep99 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.02.20.0922
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA388S903555
(bootloader) meid: 99000146074275
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Your m7 ruu is here flash Ruu to fix the loop
https://forum.xda-developers.com/showthread.php?t=2795856
---------- Post added at 09:06 AM ---------- Previous post was at 09:02 AM ----------
Your m7 is Sprint
Sent from my XT1254 using Tapatalk
KARIM9377 said:
Your m7 ruu is here flash Ruu to fix the loop
https://forum.xda-developers.com/showthread.php?t=2795856
---------- Post added at 09:06 AM ---------- Previous post was at 09:02 AM ----------
Your m7 is Sprint
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Thank you, i will try this when i get home tonight, and do you know why i keep having the bootloop issue? Is it because my phone is still S-ON?
You have to update to lollipop to flash viperrom 9.0.0 for your m7
But don't flash firmware with S-ON get update with OTA or flash lollipop ruu
https://forum.xda-developers.com/showthread.php?t=2502430
Sent from my XT1254 using Tapatalk
KARIM9377 said:
You have to update to lollipop to flash viperrom 9.0.0 for your m7
But don't flash firmware with S-ON get update with OTA or flash lollipop ruu
https://forum.xda-developers.com/showthread.php?t=2502430
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
He's phone already running the lollipop firmware. For the Sprint variant M7WLS, 6.23.651.10 is the latest version, there is nothing requiring update here.
My guess is that he used the M7_UL twrp or M7_UL Viper version (or both) instead of the M7WLS version. Might want to check that @zshep99 :good:
alray said:
He's phone already running the lollipop firmware. For the Sprint variant M7WLS, 6.23.651.10 is the latest version, there is nothing requiring update here.
My guess is that he used the M7_UL twrp or M7_UL Viper version (or both) instead of the M7WLS version. Might want to check that @zshep99 :good:
Click to expand...
Click to collapse
I believe I may have used the m7 ul version of at least one of them, and I will ensure that I ix that, as the above uul got me running stock again. But I was trying to find a method of getting s off and the only option I found was sunshine, but that costs 35 ollars. is there a simpler way to gain s off? or even just a manual method that will work?
zshep99 said:
I believe I may have used the m7 ul version of at least one of them, and I will ensure that I ix that, as the above uul got me running stock again. But I was trying to find a method of getting s off and the only option I found was sunshine, but that costs 35 ollars. is there a simpler way to gain s off? or even just a manual method that will work?
Click to expand...
Click to collapse
Why do you want s-off? You dont need s-off to flash your rom...
alray said:
Why do you want s-off? You dont need s-off to flash your rom...
Click to expand...
Click to collapse
I apologize I was under the impression that i required s off in order to get the rom to work. I will atempt to flash the proper rom and recovery and hope that it works, i was at least able to get it working back to stock for the time being.
zshep99 said:
I apologize I was under the impression that i required s off in order to get the rom to work. I will atempt to flash the proper rom and recovery and hope that it works, i was at least able to get it working back to stock for the time being.
Click to expand...
Click to collapse
No, you don't need S-OFF to flash this but if you want s-off for another reason, yes, you'll need to use Sunshine.
Ok , thanks for the help. I appreciate it.