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.
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Nic2112 said:
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Click to expand...
Click to collapse
post output of "fastboot getvar all"
remove S/N & IMEI before posting
kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Nic2112 said:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Click to expand...
Click to collapse
your previous CID was BM_001, right?
look into nkk71 SuperGUIDE in my signature
kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
kamilmirza said:
your previous CID was BM_001, right?
Click to expand...
Click to collapse
I believe so, yes.
Nic2112 said:
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
Click to expand...
Click to collapse
yes sadly there is only nandroid of BM right now
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Nic2112 said:
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Click to expand...
Click to collapse
yeah maybe that could be the problem
why not try the nandroid and see how it goes?
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Oh Wow, there is a guide for Canadian HTC One, didn't know that!
Are you sure that a Telus RUU will work on a Bell phone? They use different networks I think
SaHiLzZ said:
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Click to expand...
Click to collapse
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
SaHiLzZ said:
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
Click to expand...
Click to collapse
I know how to go back to 1.44, I have done that before.
So what you are saying is that if I have the nandroid installed, and stock recovery from your thread, the phone will detect the OTA? It should install no problem because it will be a standard recovery.
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
SaHiLzZ said:
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
Click to expand...
Click to collapse
Thatk you, one last question before I try this, the OTA, will it replace the radios and firmware as well to Bell's? I guess it depends on what they put in the OTA.
Yes, OTA generally contain new OS, HBOOT, Recovery, and RADIO, practically a full RUU replacement, but not all. IF you are S-ON, you will need to lock bootloader after loading stock recovery, but if you are S-OFF, that doesnt matter, and I will suggest to stay S-OFF!
Please help
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
ginuwine96 said:
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
Click to expand...
Click to collapse
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Not sure what file I need
majmoz said:
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Click to expand...
Click to collapse
This is my phones Info I am not sure what file to use for it ?
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
ginuwine96 said:
This is my phones Info I am not sure what file to use for it ?
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
Click to expand...
Click to collapse
If you're going to follow my guide, you'll need to use CWM method, using this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-bm___001-1-29-666-5-zip/
make sure to have read it once or twice, to be sure you're comfortable with the process
Hi guys,
I'm in need of some help, my beloved HTC One has fallen victim to the dreaded Purple Camera issue and I need to send it back.
I'm on HBOOT 1.56 and I need to turn S-ON back on as my phone says that my phone is a "Test Device" in bold red writing if you reset the phone and under About>Help
I don't want any warranty issues with HTC as being in South Africa, support is very limited as it is and they will find any excuse not to try fix it.
If anyone can give out any tips or advice I'd be happy to donate even.
I've done lots of Googling and tried a couple things but it's all for older HBOOT's than mine.
Please and thanks guys. :good:
Terros said:
Hi guys,
I'm in need of some help, my beloved HTC One has fallen victim to the dreaded Purple Camera issue and I need to send it back.
I'm on HBOOT 1.56 and I need to turn S-ON back on as my phone says that my phone is a "Test Device" in bold red writing if you reset the phone and under About>Help
I don't want any warranty issues with HTC as being in South Africa, support is very limited as it is and they will find any excuse not to try fix it.
If anyone can give out any tips or advice I'd be happy to donate even.
I've done lots of Googling and tried a couple things but it's all for older HBOOT's than mine.
Please and thanks guys. :good:
Click to expand...
Click to collapse
First, post the output of ''fastboot getvar all'' (except imei and serialno)
Do NOT S-ON for the moment.
alray said:
First, post the output of ''fastboot getvar all'' (except imei and serialno)
Do NOT S-ON for the moment.
Click to expand...
Click to collapse
Thanks for the speedy response!
This is the getvar info:
D:\htcone\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__016
(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-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
Terros said:
Thanks for the speedy response!
This is the getvar info:
D:\htcone\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__016
(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-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
Click to expand...
Click to collapse
ok so you'll need to downgrade your phone first because turning back s-on on hboot 1.56 will trigger the tampered flag in the bootloader.
use the 1.28.401.7 ruu with the guru bootloader reset tool
refer to this guide and follow instructions carefully. Again, do not s-on on hboot 1.55 and above, only do it on 1.44 or 1.54.
alray said:
First, post the output of ''fastboot getvar all'' (except imei and serialno)
Do NOT S-ON for the moment.
Click to expand...
Click to collapse
alray said:
ok so you'll need to downgrade your phone first because turning back s-on on hboot 1.56 will trigger the tampered flag in the bootloader.
use the 1.28.401.7 ruu with the guru bootloader reset tool
refer to this guide and follow instructions carefully. Again, do not s-on on hboot 1.55 and above, only do it on 1.44 or 1.54.
Click to expand...
Click to collapse
Awesome! I just downgraded to 1.44,
Can I go ahead now and use fastboot oem writesecureflag 3 to S-ON the device?
Just wanting to make 100% sure.
Terros said:
Awesome! I just downgraded to 1.44,
Can I go ahead now and use fastboot oem writesecureflag 3 to S-ON the device?
Just wanting to make 100% sure.
Click to expand...
Click to collapse
have you removed tampered and set the phone to locked, and flashed the 1.28.401.7 ruu?
nkk71 said:
have you removed tampered and set the phone to locked, and flashed the 1.28.401.7 ruu?
Click to expand...
Click to collapse
My phone still says Locked, I flashed the 1.28.401.12_hboot_1.44.zip
I haven't actually done the 1.28.401.7 RUU, Is that what I do after I flashed the 1.44 hboot?
My phone is on 4.4.2.
Terros said:
My phone still says Locked, I flashed the 1.28.401.12_hboot_1.44.zip
I haven't actually done the 1.28.401.7 RUU, Is that what I do after I flashed the 1.44 hboot?
My phone is on 4.4.2.
Click to expand...
Click to collapse
DO NOT GO S-ON
first run the RUU.EXE or the flash the RUU.ZIP
then we can consider s-on, with S-On you cannot downgrade!!! and you'll be majorly stuck.
let me know when you've done the ruu
PS: please follow the guide
1- remove tampered set locked
2- run / flash ruu 1.28.401.7
3- boot up once to make sure everything is OK, do NOT take OTA
4- go S-ON if you really need to
.
nkk71 said:
DO NOT GO S-ON
first run the RUU.EXE or the flash the RUU.ZIP
then we can consider s-on, with S-On you cannot downgrade!!! and you'll be majorly stuck.
let me know when you've done the ruu
PS: please follow the guide
1- remove tampered set locked
2- run / flash ruu 1.28.401.7
3- boot up once to make sure everything is OK, do NOT take OTA
4- go S-ON if you really need to
.
Click to expand...
Click to collapse
Ok thanks.
Is this the correct RUU > RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed?
Terros said:
Ok thanks.
Is this the correct RUU > RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed?
Click to expand...
Click to collapse
yes,
this one for RUU.EXE method: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
or this one for RUU.ZIP method: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
AFH mirror: http://www.androidfilehost.com/?fid=23329332407584993
remember to check MD5 on the download, to make sure it's not corrupt
.
nkk71 said:
yes,
this one for RUU.EXE method: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
or this one for RUU.ZIP method: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
AFH mirror: http://www.androidfilehost.com/?fid=23329332407584993
remember to check MD5 on the download, to make sure it's not corrupt
.
Click to expand...
Click to collapse
It's now updated to the RUU you listed.
What's next?
Terros said:
It's now updated to the RUU you listed.
What's next?
Click to expand...
Click to collapse
As mentioned:
1- remove tampered set locked
2- run / flash ruu 1.28.401.7
3- boot up once to make sure everything is OK, do NOT take OTA
4- go S-ON if you really need to
so if your bootloader is now:
* untampered,
* LOCKED,
* and the ruu has been successfully installed.
you can go ahead and S-On your device.
.
nkk71 said:
As mentioned:
1- remove tampered set locked
2- run / flash ruu 1.28.401.7
3- boot up once to make sure everything is OK, do NOT take OTA
4- go S-ON if you really need to
so if your bootloader is now:
* untampered,
* LOCKED,
* and the ruu has been successfully installed.
you can go ahead and S-On your device.
.
Click to expand...
Click to collapse
All still LOCKED and installed RUU. So now S-OFF with the writebootflag 3 or what ever correct.
Terros said:
All still LOCKED and installed RUU. So now S-OFF with the writebootflag 3 or what ever correct.
Click to expand...
Click to collapse
You mean S-On, right.
to go s-on: fastboot oem writesecureflag 3
So I was an idiot and wrote S-On to my phone before I was finished flashing the RUU. I have tried firewater (obtained with Wayback Machine) and rumrunner, and both failed. I am on an old version of AHRD and HBoot 1.56. Every time I try to flash the latest RUU (6.10.531.10) from htc.com, it fails with Error 155 after trying to check the signature. I have also tried extracting the rom.zip and flashing that, but I get the same result (fails after trying to check signature).
I have tried S-OFFing with every method I've found. Using Arch Linux, using Windows, using old ROMs, new ROMs, AOSP, Sense, making sure I always use an unsecured kernel, etc. firewater deletes itself every time I try to run it, and rumrunner fails after 8 tries. I don't want to spend $25 on SunShine, so I'm looking for every alternative.
Phone info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [removed]
(bootloader) imei: [removed]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(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
iwasaperson said:
So I was an idiot and wrote S-On to my phone before I was finished flashing the RUU. I have tried firewater (obtained with Wayback Machine) and rumrunner, and both failed. I am on an old version of AHRD and HBoot 1.56. Every time I try to flash the latest RUU (6.10.531.10) from htc.com, it fails with Error 155 after trying to check the signature. I have also tried extracting the rom.zip and flashing that, but I get the same result (fails after trying to check signature).
I have tried S-OFFing with every method I've found. Using Arch Linux, using Windows, using old ROMs, new ROMs, AOSP, Sense, making sure I always use an unsecured kernel, etc. firewater deletes itself every time I try to run it, and rumrunner fails after 8 tries. I don't want to spend $25 on SunShine, so I'm looking for every alternative.
Phone info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [removed]
(bootloader) imei: [removed]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(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
opps, oh dear, try posting here: http://forum.xda-developers.com/htc-one-tmobile
Sunshine is the only way to s-off, if you dont want to pay $25 then your stuck with s-on.
6.10.531.10 is not the next step up from your current firmware which is 4.19.531.10, you need all the ota's in between which is why your getting 155 error, wrong RUU, trouble is, now your s-on, you cant manually flash the OTA's, your going to need to find a full stock nandroid, or reset rom, or RUU of 4.19.531.10, or similar if a reset rom.
Try this RUU http://forum.xda-developers.com/showthread.php?t=2796465 you may be lucky, but this is really your next ota: http://forum.xda-developers.com/showthread.php?t=2755021 OTA_M7_UL_K44_SENSE60_MR_TMOUS_TO ROM VERSION 5.14.531.1_R-FROM ROM VERSION 4.19.531.10_release_373019xng22l97gj5szmwv.zip
Seanie280672 said:
opps, oh dear, try posting here: http://forum.xda-developers.com/htc-one-tmobile
Sunshine is the only way to s-off, if you dont want to pay $25 then your stuck with s-on.
6.10.531.10 is not the next step up from your current firmware which is 4.19.531.10, you need all the ota's in between which is why your getting 155 error, wrong RUU, trouble is, now your s-on, you cant manually flash the OTA's, your going to need to find a full stock nandroid, or reset rom, or RUU of 4.19.531.10, or similar if a reset rom.
Try this RUU http://forum.xda-developers.com/showthread.php?t=2796465 you may be lucky, but this is really your next ota: http://forum.xda-developers.com/showthread.php?t=2755021 OTA_M7_UL_K44_SENSE60_MR_TMOUS_TO ROM VERSION 5.14.531.1_R-FROM ROM VERSION 4.19.531.10_release_373019xng22l97gj5szmwv.zip
Click to expand...
Click to collapse
That worked! Sucks I still have Tampered and Relocked, but I hope that won't matter.
iwasaperson said:
That worked! Sucks I still have Tampered and Relocked, but I hope that won't matter.
Click to expand...
Click to collapse
are you sending it back to HTC to have something repaired ? if so, what ? for some things ive heard they will charge you with those flags, for other they will just fix it.
Seanie280672 said:
are you sending it back to HTC to have something repaired ? if so, what ? for some things ive heard they will charge you with those flags, for other they will just fix it.
Click to expand...
Click to collapse
There are some issues with calls and signal dropping.
iwasaperson said:
There are some issues with calls and signal dropping.
Click to expand...
Click to collapse
they may charge you to fix it, they will try and blame you for that as you've unlocked it and tampered with it as recorded in the bootloader, they will probably blame you, thing like the purple tint camera you could of probably got away with as thats nothing to do with unlocking the bootloader.
Seanie280672 said:
they may charge you to fix it, they will try and blame you for that as you've unlocked it and tampered with it as recorded in the bootloader, they will probably blame you, thing like the purple tint camera you could of probably got away with as thats nothing to do with unlocking the bootloader.
Click to expand...
Click to collapse
If they try to make me pay for it, I'll just get a new phone. The M9 is coming soon anyway.
Also, the tampered flag went away for some reason. Relocked is still there though.
I'm doing the warranty through T-Mobile as well, not directly through HTC.
iwasaperson said:
the tampered flag went away for some reason. Relocked is still there though.
Click to expand...
Click to collapse
Its because of they way you did it, to get rid of the tampered flag and set locked, you need to stay s-off and back flash your RUU to an early one which contain HBOOT 1.54 or earlier, then remove tampered, lock and set s-on, then update to the latest, anything past HBOOT 1.54, when you set s-on, the flags come back - just so you know for the future.
iwasaperson said:
I'm doing the warranty through T-Mobile as well, not directly through HTC.
Click to expand...
Click to collapse
You may be OK if your going through your operator, they are not as strict. :good:
Seanie280672 said:
Its because of they way you did it, to get rid of the tampered flag and set locked, you need to stay s-off and back flash your RUU to an early one which contain HBOOT 1.54 or earlier, then remove tampered, lock and set s-on, then update to the latest, anything past HBOOT 1.54, when you set s-on, the flags come back - just so you know for the future.
You may be OK if your going through your operator, they are not as strict. :good:
Click to expand...
Click to collapse
I know that now. I have plenty of experience with HTC devices, but I just messed up this time. Now I know not to set S-ON until I'm completely done.
Thanks for your help, btw.
Alright so I have been wanting to change my htc one (802w/dual sim) from android 5.0.2, back to 4.4.2 or 4.4.3 though I want a full stock/htc like software of the android version.
I found some here http://forum.xda-developers.com/showthread.php?t=2617159
I've got a few questions though as I am a bit afraid I might harm my phone (saw some posts that some phones might break down and not function again..)
First thing about the RUU and firmware, I figured some stuff but please correct me if I'm wrong:
I will be downloading Android 4.2.2 RUU version: 2.19.401.1 - then OTA update version: 2.41.401.1-2.19.401.1 (should be still android 4.2.2 according to the collection thread)
And to be able to get to android 4.4.2 (might not need 4.4.3) I will download OTA 4.21.401.5-2.41.401.1
Well, is there anything wrong with the OTA versions or RUU?
Also, when I get to Android 4.2.2, can I just mainly check for updates over "Software updates" and will I get the updates from HTC? Or they will prevent it as I installed a *custom* rom?
And for the main thing, please link me any tutorial or guide (in-depth will be appreciated.. would like to know what I'm doing) to install the rom and any other files if needed.
Sorry for the long post, have a good day!
Regards,
Matt.
MattTucke said:
Alright so I have been wanting to change my htc one (802w/dual sim) from android 5.0.2, back to 4.4.2 or 4.4.3 though I want a full stock/htc like software of the android version.
I found some here http://forum.xda-developers.com/showthread.php?t=2617159
I've got a few questions though as I am a bit afraid I might harm my phone (saw some posts that some phones might break down and not function again..)
First thing about the RUU and firmware, I figured some stuff but please correct me if I'm wrong:
I will be downloading Android 4.2.2 RUU version: 2.19.401.1 - then OTA update version: 2.41.401.1-2.19.401.1 (should be still android 4.2.2 according to the collection thread)
And to be able to get to android 4.4.2 (might not need 4.4.3) I will download OTA 4.21.401.5-2.41.401.1
Well, is there anything wrong with the OTA versions or RUU?
Also, when I get to Android 4.2.2, can I just mainly check for updates over "Software updates" and will I get the updates from HTC? Or they will prevent it as I installed a *custom* rom?
And for the main thing, please link me any tutorial or guide (in-depth will be appreciated.. would like to know what I'm doing) to install the rom and any other files if needed.
Sorry for the long post, have a good day!
Regards,
Matt.
Click to expand...
Click to collapse
Post the output of "fastboot getvar all", remove your IMEI and SERIALNO before posting.
alray said:
Post the output of "fastboot getvar all", remove your IMEI and SERIALNO before posting.
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: U3.19.3509.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.402.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7cdug
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3756mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d0e3b226
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
MattTucke said:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: U3.19.3509.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.[COLOR="red"]402[/COLOR].15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7cdug
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) cidnum: [COLOR="Red"]HTC__J15[/COLOR]
(bootloader) battery-status: good
(bootloader) battery-voltage: 3756mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d0e3b226
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
You can't do what you said above. x.xx.401.x RUU is not for your cid (HTC__J15). You can only flash RUU that are designed for your CID and MID and since your phone is S-ON, you can't downgrade using a RUU. You'll either need to S-OFF the phone so you can flash an old M7CDUG x.xx.402.x RUU or use old costom roms.
alray said:
You can't do what you said above. x.xx.401.x RUU is not for your cid (HTC__J15). You can only flash RUU that are designed for your CID and MID and since your phone is S-ON, you can't downgrade using a RUU. You'll either need to S-OFF the phone so you can flash an old M7CDUG x.xx.402.x RUU or use old costom roms.
Click to expand...
Click to collapse
I did some searching and I found this RUU
Code:
www htc1guru com/dld/ruu_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe/
(I can't send outside links)
According to the site it's for CID HTC_J15 and modelid PN0710000
Does it mean I can flash it even though it's x.xx.401.x? Also if I can, can you please send a guide about how to S-OFF the phone?
Thanks again.
MattTucke said:
I did some searching and I found this RUU
Code:
www htc1guru com/dld/ruu_[B][COLOR="Red"]m7_ul[/COLOR][/B]_k44_sense55_mr_htc_europe_[B][COLOR="red"]4[/COLOR][/B]-19-[B][COLOR="red"]401[/COLOR][/B]-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe/
(I can't send outside links)
According to the site it's for CID HTC_J15 and modelid PN0710000
Does it mean I can flash it even though it's x.xx.401.x? Also if I can, can you please send a guide about how to S-OFF the phone?
Thanks again.
Click to expand...
Click to collapse
No you can't, this RUU is simply not for your phone, not even for the same variant.
To flash a ruu on a s-on phone:
The ruu must match your CID number. Yours is HTC__J15 ---> OK
The ruu must match your MID number Yours is PN0771000 this RUU is for PN0710000 --> NO
The ruu must match the firmware base version. Yours is .402 this RUU is .401 ---> NO
The ruu must be same or newer than the current firmware version installed. Yours is 7.xx.xxx.x , this ruu is 4.xx.xxx.x so it's a downgrade, can't downgrade with s-on --> NO
The ruu must match your variant. Yours is M&CDUG --> The ruu you want to flash is for M7_UL ---> NO
The bootloader must be locked or re-locked
If only on of the above condition isn't respected, the ruu won't flash... And even if you could achieve s-off, #5 will always cause problem. You can only use RUU for M7CDUG variant