Hi,
After going through a lot of threads created this one. I'm from India and my HTC ONE is of x.xx.707.x region.
I recently S-off'ed my One hboot 1.54 with rumrunner guide (http://forum.xda-developers.com/showthread.php?t=2488772)
Then i updated my firmware to fw_3.62.401.1_custom that i got from Vomer's guide (http://forum.xda-developers.com/showthread.php?t=2365506)
I also flashed custom recovery (TWRP).
I then flashed the stock 3.62.401.1.zip rom that i got from ARHD thread.
My main concerns are
1. Can i downgrade the hboot anytime ?
2. Can i get back to 100% stock? With S-on ? if so any help regarding this is greatly appreciated.
3. I'm now new to S-Off thing, and is there anything that i should take care of from now? (like what firmware i should not flash, or Rom or radio restrictions)
Thanks.
the same questions
coolshritz said:
My main concerns are
1. Can i downgrade the hboot anytime ?
2. Can i get back to 100% stock? With S-on ? if so any help regarding this is greatly appreciated.
3. I'm now new to S-Off thing, and is there anything that i should take care of from now? (like what firmware i should not flash, or Rom or radio restrictions)
Thanks.
Click to expand...
Click to collapse
dingnangen said:
the same questions
Click to expand...
Click to collapse
With S-Off:
1- Yes you can downgrade/upgrade anytime you see fit.
2- 100% Stock with S-Off!! With S-On, you can get pretty close but you can't make your bootloader say "LOCKED" it will only show "RELOCKED"
3- no restrictions, you can flash pretty much anything with S-Off (obviously you should stay away from Sprint or Verizon stuff as they are not GSM)
4- don't go S-On!
nkk71 said:
With S-Off:
1- Yes you can downgrade/upgrade anytime you see fit.
2- 100% Stock with S-Off!! With S-On, you can get pretty close but you can't make your bootloader say "LOCKED" it will only show "RELOCKED"
3- no restrictions, you can flash pretty much anything with S-Off (obviously you should stay away from Sprint or Verizon stuff as they are not GSM)
4- don't go S-On!
Click to expand...
Click to collapse
4- can i downgrade to 1.44 then s-on using revone?(for warranty)after that,can I get s-off again using revone?
Sent from my HTC One using Tapatalk 2
dingnangen said:
4- can i downgrade to 1.44 then s-on using revone?(for warranty)after that,can I get s-off again using revone?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
If you really need to go S-On again (though many people send in their phones with S-Off, cause some actually ship from HTC S-Off), here are the steps:
1- change CID & MID back to stock (in case you changed them)
2- remove TAMPERED using either revone or http://forum.xda-developers.com/show....php?t=2477792
3- change to LOCKED using either revone or http://forum.xda-developers.com/show....php?t=2475914
4- AFTER ABOVE use the correct RUU.exe for your phone; you will not loose S-Off because of the RUU
5- AFTER YOUR ARE 100% SATISFIED OF ABOVE RESULTS (ie no more tampered, bootloader LOCKED, 100% stock)
"fastboot oem writesecureflag 3" to get S-On.
Hit the thanks button if I helped
Nkk71 I have a similar question
I s offed then restored a nandroid backup of 4.1.2 and removed tampered and locked bootloader. I ota'd right up to the latest 3.62.306.7 version soiit's stock Rom, stock recovery and hboot 1.55
Can I s on for warranty purpose now?
stovie_steve said:
Nkk71 I have a similar question
I s offed then restored a nandroid backup of 4.1.2 and removed tampered and locked bootloader. I ota'd right up to the latest 3.62.306.7 version soiit's stock Rom, stock recovery and hboot 1.55
Can I s on for warranty purpose now?
Click to expand...
Click to collapse
If the phone looks "out of the box" to you then yes, ie no TAMPERED, says LOCKED (not RELOCKED), no red text "this a developer bla bla bla", has a stock ROM and a stock recovery, correct CID and MID, then by all means, YES.
Otherwise fix anything that might be out of order, and only as the VERY LAST STEP go back S-On.
nkk71 said:
If the phone looks "out of the box" to you then yes, ie no TAMPERED, says LOCKED (not RELOCKED), no red text "this a developer bla bla bla", has a stock ROM and a stock recovery, correct CID and MID, then by all means, YES.
Otherwise fix anything that might be out of order, and only as the VERY LAST STEP go back S-On.
Click to expand...
Click to collapse
One last question. If i give you my flow of what I did can you help, as I don't want to s-on and mess it up...
1. Rumrunner to obtain s-off on hboot 1.54
2. Downgraded my hboot to 1.44 - this was a stock hboot, but I modified the android.info part so I could flash it onto my model
3. Changed CID to HTC__032 and ran "RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed" which reset my hboot, bootloader etc and completely stock. At this stage my bootloader is LOCKED and still s-off
4. With bootloader still locked, installed CWM Recovery and restored a nandroid backup CID O2__102 1.27.206.1 and stock recovery
5. Changed CID back to O2___001
6. Installed the various OTA updates right up to current 3.62.206.1 software version and hboot is 1.54
Now can I s-on??
---------- Post added at 08:11 PM ---------- Previous post was at 07:26 PM ----------
nkk71 said:
If the phone looks "out of the box" to you then yes, ie no TAMPERED, says LOCKED (not RELOCKED), no red text "this a developer bla bla bla", has a stock ROM and a stock recovery, correct CID and MID, then by all means, YES.
Otherwise fix anything that might be out of order, and only as the VERY LAST STEP go back S-On.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Does the cimmitno-bootloader: dirty-d959c75800 mean that if I s-on it will brick the phone as well?
nkk71 said:
If you really need to go S-On again (though many people send in their phones with S-Off, cause some actually ship from HTC S-Off), here are the steps:
1- change CID & MID back to stock (in case you changed them)
2- remove TAMPERED using either revone or http://forum.xda-developers.com/show....php?t=2477792
3- change to LOCKED using either revone or http://forum.xda-developers.com/show....php?t=2475914
4- AFTER ABOVE use the correct RUU.exe for your phone; you will not loose S-Off because of the RUU
5- AFTER YOUR ARE 100% SATISFIED OF ABOVE RESULTS (ie no more tampered, bootloader LOCKED, 100% stock)
"fastboot oem writesecureflag 3" to get S-On.
Hit the thanks button if I helped
Click to expand...
Click to collapse
when I get back my phone from HTC service center,i can get soff my phone(hboot1.44) again using revone,right?
Sent from my HTC One using Tapatalk 2
Now that I have latest updates but all of different region. I'm from x.xx.707.x but I have x.xx.401.x Rom and bootloader. The bootloader is custom so it says developer edition phone. I have a backup of just rom of my stock version.
What would be the best way to go to stock now. My current hboot version is 1.55 custom and rom is 3.62.401.1. I have rom backup of 2.24.707.3 that had hboot of 1.54.
Sent from my HTC One using xda app-developers app
guys no need for s-on for warranty and don't go s-on cause there can be a problem to go back to s-off.Secondly if u r concerned abt the service just flash 1.29 ruu use revone remove tampered lock ur bootloader and ota ur way to 4.2 update.Many guys have given their one with s-off and they got through service without a hitch.Hell even im gonna go on monday to service center cause my camera module has gone kaput and a dead zone in the mid section of touchscreen but with s-off , bootloader locked and everything stock and the red text doesn't come after u lock the bootloader . So what's the problem ???
---------- Post added at 04:27 PM ---------- Previous post was at 04:15 PM ----------
coolshritz said:
Now that I have latest updates but all of different region. I'm from x.xx.707.x but I have x.xx.401.x Rom and bootloader. The bootloader is custom so it says developer edition phone. I have a backup of just rom of my stock version.
What would be the best way to go to stock now. My current hboot version is 1.55 custom and rom is 3.62.401.1. I have rom backup of 2.24.707.3 that had hboot of 1.54.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Be careful if u wanna go stock here's what u should do:
1.) First of all flash a non modified stock hboot doesn't matter what version but it should be unmodified since custom hboot can lead to hard brick when going back to stock.
2.) Now after flashing stock unmodified hboot just flash the 1.29 ruu use revone remove tampered if there lock bootloader and ota ur way to 4.2.2 the latest available for us indian users.But don't s-on cause its risky cause i don't know whether u can go back s-off after s-on so just leave s-off as it is.
That's it ur done
Slim Shady said:
guys no need for s-on for warranty and don't go s-on cause there can be a problem to go back to s-off.Secondly if u r concerned abt the service just flash 1.29 ruu use revone remove tampered lock ur bootloader and ota ur way to 4.2 update.Many guys have given their one with s-off and they got through service without a hitch.Hell even im gonna go on monday to service center cause my camera module has gone kaput and a dead zone in the mid section of touchscreen but with s-off , bootloader locked and everything stock and the red text doesn't come after u lock the bootloader . So what's the problem ???
---------- Post added at 04:27 PM ---------- Previous post was at 04:15 PM ----------
Be careful if u wanna go stock here's what u should do:
1.) First of all flash a non modified stock hboot doesn't matter what version but it should be unmodified since custom hboot can lead to hard brick when going back to stock.
2.) Now after flashing stock unmodified hboot just flash the 1.29 ruu use revone remove tampered if there lock bootloader and ota ur way to 4.2.2 the latest available for us indian users.But don't s-on cause its risky cause i don't know whether u can go back s-off after s-on so just leave s-off as it is.
That's it ur done
Click to expand...
Click to collapse
Well, I directly flashed RUU zip that i got from htc1guru.com, it matched the cid and mid, that were stock. Flashed with no issues and updated it to 4.1.2 (Yet to do 4.2.2). I dont see red text in hboot, but in the "Tell HTC" section. I'm still S-off, bootloader locked. Is this normal?
I read somewhere that only S-On can remove that text. Is that true??
stovie_steve said:
Does the cimmitno-bootloader: dirty-d959c75800 mean that if I s-on it will brick the phone as well?
Click to expand...
Click to collapse
No it will not brick, it's always "dirty", no worries.
---------- Post added at 01:28 PM ---------- Previous post was at 01:25 PM ----------
coolshritz said:
Well, I directly flashed RUU zip that i got from htc1guru.com, it matched the cid and mid, that were stock. Flashed with no issues and updated it to 4.1.2 (Yet to do 4.2.2). I dont see red text in hboot, but in the "Tell HTC" section. I'm still S-off, bootloader locked. Is this normal?
I read somewhere that only S-On can remove that text. Is that true??
Click to expand...
Click to collapse
Yes you are right, the "Tell HTC" part will have the red text with S-Off and will only go away when you're 100% stock and then set S-On.
coolshritz said:
Well, I directly flashed RUU zip that i got from htc1guru.com, it matched the cid and mid, that were stock. Flashed with no issues and updated it to 4.1.2 (Yet to do 4.2.2). I dont see red text in hboot, but in the "Tell HTC" section. I'm still S-off, bootloader locked. Is this normal?
I read somewhere that only S-On can remove that text. Is that true??
Click to expand...
Click to collapse
Yes It's solely because you're S-OFF. Your device has all security disabled, thus it acts like a test device. Once you go S-ON, the red text will immediately disappear. Well have u mended everything else except the s-off like remove tampered restoring mid and cid if changed.Update to 4.2.2 go to service center turn in ur device and if they by chance ask (generally they don't) abt s-off tell i don't know and it was like that only when u bought it and voila have ur phone repaired/replaced as the situation demands for it.
Going back s-on is really ur choice though not recommended cause if u get the same phone back repaired complications might arise in going back to s-off.
dingnangen said:
when I get back my phone from HTC service center,i can get soff my phone(hboot1.44) again using revone,right?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
yes, for hboot 1.44 (pre June 2013) you can use revone for 1.54 you can use rumrunner.
nkk71 said:
yes, for hboot 1.44 (pre June 2013) you can use revone for 1.54 you can use rumrunner.
Click to expand...
Click to collapse
I saw that : WARNING Going back to S-ON isn't necessary for warranty, just lock the bootloader and go back to a stock rom/recovery if you do decide to be crazy and go S-ON again you will receive back a non-s-offable device... YOU HAVE BEEN WARNED
In this post : http://forum.xda-developers.com/showthread.php?p=45270020
Sent from my HTC One using Tapatalk 2
dingnangen said:
I saw that : WARNING Going back to S-ON isn't necessary for warranty, just lock the bootloader and go back to a stock rom/recovery if you do decide to be crazy and go S-ON again you will receive back a non-s-offable device... YOU HAVE BEEN WARNED
In this post : http://forum.xda-developers.com/showthread.php?p=45270020
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I agree with the S-Off part, as some phones ship S-Off. The important parts are 100% stock rom, firmware, recovery, hboot; no TAMPERED or red text on boot. and LOCKED not RELOCKED.
However some people have been denied warranty because of S-Off (really depends on country, service center, and probably most important the person in the center).
As for "you will receive back a non-s-offable device" this is no longer the case since rumrunner can now achieve s-off on hboot 1.54 and 1.55.
It's locked, OTA 4.3 update with S-On but after i did this:"fastboot oem writesecureflag 3" to get S-On.
It's ***tampered*** again....
What to do, everything is back to stock now, no root..
nkk71 said:
I agree with the S-Off part, as some phones ship S-Off. The important parts are 100% stock rom, firmware, recovery, hboot; no TAMPERED or red text on boot. and LOCKED not RELOCKED.
However some people have been denied warranty because of S-Off (really depends on country, service center, and probably most important the person in the center).
As for "you will receive back a non-s-offable device" this is no longer the case since rumrunner can now achieve s-off on hboot 1.54 and 1.55.
Click to expand...
Click to collapse
it's means that if I get back my phone with 4.1(hb1.44,i will tell HTC don't update my system),I can also get soff using revone?
Sent from my HTC One using Tapatalk 2
Why did you do it when you already had S-On??
Related
All right, here comes a noob question:
My HTC One is from Israel, and though I made a nandroid backup of my phone after I rooted it, I don't have one from before my rooting it. That said, my CID was HTC__K18...there is no RUU for that CID, so I used rumrunner to s-off my phone, changed my CID to HTC__01 and used the European RUU (the U not the UL because my phone is a U) to get %100 back to stock. The RUU that I flashed has a hboot of 1.44 and my stock was already a 1.54 and 4.2.2 (maybe 4.1.2?)...anyway after flashing the RUU, I'm not able to OTA and I really just want to get %100 stock...in a way that I'd be capable of receiving all the updates OTA and have the highest firmware/software. Thanks in advance!
Oh, and here's some of my info:
version-bootloader: 1.44.0000 (it shipped with 1.54 but I RUUed an older version)
version-baseband: 4A.14.3250.13
version-main: 1.29.401.2 (it shipped with 2.24.401.2)
version-misc: PVT SHIP S-OFF (used rumrunner to s-off hboot of 1.54)
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__001 (I changed the cid from HTC__k18)
shpongleeyes said:
All right, here comes a noob question:
My HTC One is from Israel, and though I made a nandroid backup of my phone after I rooted it, I don't have one from before my rooting it. That said, my CID was HTC__K18...there is no RUU for that CID, so I used rumrunner to s-off my phone, changed my CID to HTC__01 and used the European RUU (the U not the UL because my phone is a U) to get %100 back to stock. The RUU that I flashed has a hboot of 1.44 and my stock was already a 1.54 and 4.2.2 (maybe 4.1.2?)...anyway after flashing the RUU, I'm not able to OTA and I really just want to get %100 stock...in a way that I'd be capable of receiving all the updates OTA and have the highest firmware/software. Thanks in advance!
Oh, and here's some of my info:
version-bootloader: 1.44.0000 (it shipped with 1.54 but I RUUed an older version)
version-baseband: 4A.14.3250.13
version-main: 1.29.401.2 (it shipped with 2.24.401.2)
version-misc: PVT SHIP S-OFF (used rumrunner to s-off hboot of 1.54)
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__001 (I changed the cid from HTC__k18)
Click to expand...
Click to collapse
Question: where do you want to go?
1- To an European stock model
2- To your version (I have a nandroid of 2.24.401.2 for a PN0711000, M7_U)
nkk71 said:
Question: where do you want to go?
1- To an European stock model
2- To your version (I have a nandroid of 2.24.401.2 for a PN0711000, M7_U)
Click to expand...
Click to collapse
Whatever would give me OTA updates and allow me to be as stock as possible! Just out of curiosity, what would the benefits of each be? Thank you!
shpongleeyes said:
Whatever would give me OTA updates and allow me to be as stock as possible! Just out of curiosity, what would the benefits of each be? Thank you!
Click to expand...
Click to collapse
LOL, this just resulted in another question: why not use a custom ROM, they get updated way more frequently than OTAs? If you want "stock as possible" you can check out ARHD, it's very stock. (and since you're S-Off you can upgrade/downgrade anytime, including firmware!!)
As for benefits of the other two options:
1) I think HTC__001 (or was it Y13, not sure), are usually among the first WWE editions to get OTAs (not as fast as custom ROMs )
2) HTC_K18 would put you back to a state where you bought the phone.
It's all personal choice, eg I like stock but want it rooted so I'm currently running ARHD 13.3 (until I decide to upgrade), others like their Venom Tweaks or InsertCoin etc... and again for others they need to be unrooted because of some banking apps.
So give it a thought and let me know, which road you wanna take
PS: Hit the thanks button if I helped
nkk71 said:
LOL, this just resulted in another question: why not use a custom ROM, they get updated way more frequently than OTAs? If you want "stock as possible" you can check out ARHD, it's very stock. (and since you're S-Off you can upgrade/downgrade anytime, including firmware!!)
As for benefits of the other two options:
1) I think HTC__001 (or was it Y13, not sure), are usually among the first WWE editions to get OTAs (not as fast as custom ROMs )
2) HTC_K18 would put you back to a state where you bought the phone.
It's all personal choice, eg I like stock but want it rooted so I'm currently running ARHD 13.3 (until I decide to upgrade), others like their Venom Tweaks or InsertCoin etc... and again for others they need to be unrooted because of some banking apps.
So give it a thought and let me know, which road you wanna take
PS: Hit the thanks button if I helped
Click to expand...
Click to collapse
Thank you for the quick reply!
Okay, so I'd like to go with the European road...as far as custom ROMs are concerned, I had ARHD, both GE and Sense, but I just want things to run smoothly and not worry about OTAs....I'd like to receive them as soon as they're available with the least amount of headache...
On that note, can I receive OTA updates directly from HTC while I'm s-off? Because currently I don't have that option...it doesn't even show that I have an update available.
Also, is your nandroid of 2.24.401.2 made with cid HTC__k18?
P.s. I don't even need/want to root the phone again...it's just too much for me. I'd like to get as stock as possible while keeping the options open (that's why I want to leave s-off).
Thank you again for your help! You're awesome!
shpongleeyes said:
Thank you for the quick reply!
Okay, so I'd like to go with the European road...as far as custom ROMs are concerned, I had ARHD, both GE and Sense, but I just want things to run smoothly and not worry about OTAs....I'd like to receive them as soon as they're available with the least amount of headache...
On that note, can I receive OTA updates directly from HTC while I'm s-off? Because currently I don't have that option...it doesn't even show that I have an update available.
P.s. I don't even need/want to root the phone again...it's just too much for me. I'd like to get as stock as possible while keeping the options open (that's why I want to leave s-off).
Thank you again for your help! You're awesome!
Click to expand...
Click to collapse
Ok, European road
1- You've already changed your CID, you still need to change your MID: "fastboot oem writemid PN0710000"
(keep a record of your original CID, MID, and software/firmware version somewhere in case you ever need it)
2- remove tampered either using revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- set your phone to LOCKED (not relocked) using revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- then use the full European RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
you should keep S-Off and not go back S-On.
After installing the RUU you should immediately start receiving OTAs all the way up to 3.62
PS: remember the above procedure will wipe everything off your phone, so back up anything you may need first!!
nkk71 said:
Ok, European road
1- You've already changed your CID, you still need to change your MID: "fastboot oem writemid PN0710000"
(keep a record of your original CID, MID, and software/firmware version somewhere in case you ever need it)
2- remove tampered either using revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- set your phone to LOCKED (not relocked) using revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- then use the full European RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
you should keep S-Off and not go back S-On.
After installing the RUU you should immediately start receiving OTAs all the way up to 3.62
PS: remember the above procedure will wipe everything off your phone, so back up anything you may need first!!
Click to expand...
Click to collapse
You're awesome. However, I did all those steps except for the first step...when I go into recovery mode now, there's still the red lettering as well as when I go into "Tell HTC and error reporting" the red lettering says "This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings." Oh, and I'm not able to receive the OTAs.
Now, if I change the MID, do I need to do all the steps again or can I just do the first step now? Will that help get rid of the "test device" warnings that I have on the phone?
Oh, and I used this European one before (cause I have a U and not UL) http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
Why would I use the UL one?
Thank you again for you time and help!
shpongleeyes said:
You're awesome. However, I did all those steps except for the first step...when I go into recovery mode now, there's still the red lettering as well as when I go into "Tell HTC and error reporting" the red lettering says "This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings." Oh, and I'm not able to receive the OTAs.
Now, if I change the MID, do I need to do all the steps again or can I just do the first step now? Will that help get rid of the "test device" warnings that I have on the phone?
Thank you again for you time and help!
Click to expand...
Click to collapse
You won't get any OTAs because of your MID, change it, and see if you start getting the OTAs. M7_U and M7_UL share pretty much most of the software stuff, the hardware is different of course, but MID 0711 and CID HTC__001 won't get any OTAs.
The "Tell HTC and error reporting" red text is because you're S-Off, personally I wouldn't care. But if it bothers you A LOT, you'll need to go S-On again, and AT THIS TIME you should NOT!!! we can deal with that later.
Change MID, and confirm you are now getting OTAs
Again DO NOT GO S-ON, at least for the time being!!
---------- Post added at 07:51 PM ---------- Previous post was at 07:48 PM ----------
shpongleeyes said:
Oh, and I used this European one before (cause I have a U and not UL) http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
Click to expand...
Click to collapse
Oh I didnt see that one, but it should give you updates till 2.24.401.9 at least. Don't know if 3.62 out yet for that PN.
nkk71 said:
You won't get any OTAs because of your MID, change it, and see if you start getting the OTAs. M7_U and M7_UL share pretty much most of the software stuff, the hardware is different of course, but MID 0711 and CID HTC__001 won't get any OTAs.
The "Tell HTC and error reporting" red text is because you're S-Off, personally I wouldn't care. But if it bothers you A LOT, you'll need to go S-On again, and AT THIS TIME you should NOT!!! we can deal with that later.
Change MID, and confirm you are now getting OTAs
Again DO NOT GO S-ON, at least for the time being!!
---------- Post added at 07:51 PM ---------- Previous post was at 07:48 PM ----------
Oh I didnt see that one, but it should give you updates till 2.24.401.9 at least. Don't know if 3.62 out yet for that PN.
Click to expand...
Click to collapse
Okay, I tried to change the mid but the console is giving me an error:
...
<bootloader> [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.031s
shpongleeyes said:
Okay, I tried to change the mid but the console is giving me an error:
...
<bootloader> [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.031s
Click to expand...
Click to collapse
Let's slow it down a little, if I understand correctly:
1- you are now unTAMPERED
2- you are now LOCKED, not RElocked or UNlocked
3- you have CID: HTC__001
4- you have MID: PN0711000
5- you ran the RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- you are still S-Off (please!)
If all of the above are true, when you go to Settings->About->Software Update (or whatever it's called), does it show an update? or what does it say
EDIT: can you repost a "fastboot getvar all" (remove IMEI and s/n)
nkk71 said:
Let's slow it down a little, if I understand correctly:
1- you are now unTAMPERED
2- you are now LOCKED, not RElocked or UNlocked
3- you have CID: HTC__001
4- you have MID: PN0711000
5- you ran the RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- you are still S-Off (please!)
If all of the above are true, when you go to Settings->About->Software Update (or whatever it's called), does it show an update? or what does it say
EDIT: can you repost a "fastboot getvar all" (remove IMEI and s/n)
Click to expand...
Click to collapse
you're correct about everything:
All it says is that my software is up-to-date...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
shpongleeyes said:
you're correct about everything:
All it says is that my software is up-to-date...
(bootloader) cidnum: HTC__001
Click to expand...
Click to collapse
Before we go on messing with MID, can you just change CID to HTC__J15 (two underscores) and check for a software update, don't know the original 1.xx version, but I am sure that J15 PN0711 got the 2.24.401.2 and (possibly) 2.24.401.9.
Just check if it gives an update with HTC__J15, no need to download it!!
nkk71 said:
Before we go on messing with MID, can you just change CID to HTC__J15 (two underscores) and check for a software update, don't know the original 1.xx version, but I am sure that J15 PN0711 got the 2.24.401.2 and (possibly) 2.24.401.9.
Just check if it gives an update with HTC__J15, no need to download it!!
Click to expand...
Click to collapse
Yes
That gives me an option to upgrade...
now what?
shpongleeyes said:
Yes
That gives me an option to upgrade...
now what?
Click to expand...
Click to collapse
Oh man, sorry to keep you hanging, but we may need to pick this up tomorrow, going for dinner now, wont be back till tomorrow,
but try setting CID to your original one, and see if you get any updates for your original CID.
sorry, got to go, I'll check back on you tomorrow
whatever you decide to do, do NOT GO S-ON (at least for now)
Have a good evening...
nkk71 said:
Oh man, sorry to keep you hanging, but we may need to pick this up tomorrow, going for dinner now, wont be back till tomorrow,
but try setting CID to your original one, and see if you get any updates for your original CID.
sorry, got to go, I'll check back on you tomorrow
whatever you decide to do, do NOT GO S-ON (at least for now)
Have a good evening...
Click to expand...
Click to collapse
When I set it back to my original CID there are no updates...enjoy the food
I look forward to tomorrow!
shpongleeyes said:
When I set it back to my original CID there are no updates...enjoy the food
I look forward to tomorrow!
Click to expand...
Click to collapse
Hey, how are you today?
I'll be online later (around 5 or 6), but it looks like that RUU is fully compatible with ur original CID. So go ahead with your original CID, and get the OTAs. U should be able to get at least to 2.24.401.9, don't know if 3.62 is out for u yet.
Keep s-off in case we need to change something later.
C u later...
Sent from my HTC One using Tapatalk
nkk71 said:
Hey, how are you today?
I'll be online later (around 5 or 6), but it looks like that RUU is fully compatible with ur original CID. So go ahead with your original CID, and get the OTAs. U should be able to get at least to 2.24.401.9, don't know if 3.62 is out for u yet.
Keep s-off in case we need to change something later.
C u later...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Hey, no the RUU is not compatible with my original CID (HTC__K18) as there are no available upgrades after I change the CID...also the same is true when I change it to HTC__001, though it did work when you told me to update to J something or other...weird.
shpongleeyes said:
Hey, no the RUU is not compatible with my original CID (HTC__K18) as there are no available upgrades after I change the CID...also the same is true when I change it to HTC__001, though it did work when you told me to update to J something or other...weird.
Click to expand...
Click to collapse
Well I guess you have 2 choices:
1- set CID to HTC__J15 -> a friend of mine has PN0711000 HTC__J15, it's basically the M7_U version and HTC__J15 is a nonbranded WWE edition but usually for the Middle East
2- set CID to HTC__001, set MID to PN0710000, and use this RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
by changing to MID PN0710000, it will make the software on your phone think it's a UL model, but since the hardware isn't there for LTE, it won't make any difference.
Step 1, is probably the easiest to do, so why not just set it to J15 and see how far the updates go. (ie if 3.62 is out for J15).
Hope that helps
nkk71 said:
Well I guess you have 2 choices:
1- set CID to HTC__J15 -> a friend of mine has PN0711000 HTC__J15, it's basically the M7_U version and HTC__J15 is a nonbranded WWE edition but usually for the Middle East
2- set CID to HTC__001, set MID to PN0710000, and use this RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
by changing to MID PN0710000, it will make the software on your phone think it's a UL model, but since the hardware isn't there for LTE, it won't make any difference.
Step 1, is probably the easiest to do, so why not just set it to J15 and see how far the updates go. (ie if 3.62 is out for J15).
Hope that helps
Click to expand...
Click to collapse
Thank you for you patience and your help! You've been amazing!
shpongleeyes said:
Thank you for you patience and your help! You've been amazing!
Click to expand...
Click to collapse
No problem, glad to be of help. If everything's OK now, could I please ask you to change the main thread title to include [SOLVED]. Thanks & take care
Hi,
Below are the details of my instrument HTC One and right now am on Revolution HD ROM 4.3+Sense5.5 rooted. I would like to go back to original stock ROM to get OTA. Kindly let me know complete detailed procedure to unroot and get back to stock as original factory reset.
C:\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4148mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Regards!
Kashif
http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Instal this. Stock rom and stock recovery in one zip. Version Stock rom and firmware must be the same. 2.24.401.8 propably will work good. I dont see 2.24.401.9. After this you have stock phone and you get OTA updates. (bootloader still be "unlocked") But you must know that some people write after back to stock and OTA from htc they phone dont bootup. OTA can brick your phone. Sorry for my english.
Htc One return back to original stock ROM to get OTA
xnobex said:
http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Instal this. Stock rom and stock recovery in one zip. Version Stock rom and firmware must be the same. 2.24.401.8 propably will work good. I dont see 2.24.401.9. After this you have stock phone and you get OTA updates. (bootloader still be "unlocked") But you must know that some people write after back to stock and OTA from htc they phone dont bootup. OTA can brick your phone. Sorry for my english.
Click to expand...
Click to collapse
Hi,
Can I do S-Off and lock the bootloader after restoring guru reset and ota. Will it retain the stock and able to get future ota
kash_9763 said:
Hi,
Can I do S-Off and lock the bootloader after restoring guru reset and ota. Will it retain the stock and able to get future ota
Click to expand...
Click to collapse
Quick question (gotto go away for a bit): why do you want to go through all the hassle involved?
Htc One return back to original stock ROM to get OTA
xnobex said:
http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Instal this. Stock rom and stock recovery in one zip. Version Stock rom and firmware must be the same. 2.24.401.8 propably will work good. I dont see 2.24.401.9. After this you have stock phone and you get OTA updates. (bootloader still be "unlocked") But you must know that some people write after back to stock and OTA from htc they phone dont bootup. OTA can brick your phone. Sorry for my english.
Click to expand...
Click to collapse
nkk71 said:
Quick question (gotto go away for a bit): why do you want to go through all the hassle involved?
Click to expand...
Click to collapse
I want to get back to the Stock ROM as original with lock bootloader, I did rooted to get OTA but now I want to regain the original one.
kash_9763 said:
I want to get back to the Stock ROM as original with lock bootloader, I did rooted to get OTA but now I want to regain the original one.
Click to expand...
Click to collapse
Don't really understand why anybody would want to go backwards, except for warranty, but in any case, your choice so here goes: you need s-off
1- So download Guru Reset 2.24.401.8 (closest available to your version): http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Flash it, you do need to WIPE, deselect "stock recovery", select ROOT, radio doesnt matter
2- Download rumrunner package 2.24.401.9, and use it to get S-Off
once s-off
3- remove TAMPERED: http://forum.xda-developers.com/showthread.php?t=2477792
4- set your phone to LOCKED: http://forum.xda-developers.com/showthread.php?t=2475914
5- download and run the following RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- do not take any OTA YET
7- if you insist on S-On, then "fastboot oem writesecureflag 3", if you don't mind keeping S-Off keep it
8- take the OTAs
If I've helped hit the thanks button
Let me know if you need any more help
nkk71 said:
Don't really understand why anybody would want to go backwards, except for warranty, but in any case, your choice so here goes: you need s-off
1- So download Guru Reset 2.24.401.8 (closest available to your version): http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Flash it, you do need to WIPE, deselect "stock recovery", select ROOT, radio doesnt matter
2- Download rumrunner package 2.24.401.9, and use it to get S-Off
once s-off
3- remove TAMPERED: http://forum.xda-developers.com/showthread.php?t=2477792
4- set your phone to LOCKED: http://forum.xda-developers.com/showthread.php?t=2475914
5- download and run the following RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- do not take any OTA YET
7- if you insist on S-On, then "fastboot oem writesecureflag 3", if you don't mind keeping S-Off keep it
8- take the OTAs
If I've helped hit the thanks button
Let me know if you need any more help
Click to expand...
Click to collapse
Thanks Dear! I will try and update you once done.
Htc One return back to original stock ROM to get OTA
nkk71 said:
Don't really understand why anybody would want to go backwards, except for warranty, but in any case, your choice so here goes: you need s-off
1- So download Guru Reset 2.24.401.8 (closest available to your version): http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Flash it, you do need to WIPE, deselect "stock recovery", select ROOT, radio doesnt matter
2- Download rumrunner package 2.24.401.9, and use it to get S-Off
once s-off
3- remove TAMPERED: http://forum.xda-developers.com/showthread.php?t=2477792
4- set your phone to LOCKED: http://forum.xda-developers.com/showthread.php?t=2475914
5- download and run the following RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- do not take any OTA YET
7- if you insist on S-On, then "fastboot oem writesecureflag 3", if you don't mind keeping S-Off keep it
8- take the OTAs
If I've helped hit the thanks button
Let me know if you need any more help
Click to expand...
Click to collapse
Hi,
I have took TWRP backup of 4.2.2 but not in zip format. If I do restore that backup and do lock the bootloader then I will be on Stock original ROM? and also able to get OTA? Kindly help me out
kash_9763 said:
Hi,
I have took TWRP backup of 4.2.2 but not in zip format. If I do restore that backup and do lock the bootloader then I will be on Stock original ROM? and also able to get OTA? Kindly help me out
Click to expand...
Click to collapse
No need to lock bootloader to get OTA, you just need:
1- stock rom
2- (preferably) matching firmware
3- stock recovery
so if your TWRP backup is same version as firmware, then just restore it, that will get you back to stock rom.
after that, you still need to flash stock recovery; for you (2.24.401.9) you can use the 2.24.401.8 from here: http://forum.xda-developers.com/showthread.php?t=2463387 (it's in under the WWE section)
Htc One return back to original stock ROM to get OTA
nkk71 said:
No need to lock bootloader to get OTA, you just need:
1- stock rom
2- (preferably) matching firmware
3- stock recovery
so if your TWRP backup is same version as firmware, then just restore it, that will get you back to stock rom.
after that, you still need to flash stock recovery; for you (2.24.401.9) you can use the 2.24.401.8 from here: http://forum.xda-developers.com/showthread.php?t=2463387 (it's in under the WWE section)
Click to expand...
Click to collapse
Hi Dear! I really appreciate your quick response.
kash_9763 said:
Hi Dear! I really appreciate your quick response.
Click to expand...
Click to collapse
No problem, hit the thanks button if I've helped
Note: before flashing stock recovery copy everything to your PC, one time I did it and it fully wiped my /sdcard
Can't switch back to HTC One Stock ROM
I am Having troubles switching back to Stock HTC Sense ROM. I Rooted my Phone. S-Off Done, Bootloader Unlocked. And installed the Google Play Edition ROM RUU. Now I cant switch back to the HTC Sense India Stock ROM.
Phone Deatils,
M7_U PVT SHIP S-OFF RH
CID-11111111
HBOOT – 1.44.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
eMMC-boot
Apr 12 2013, 12:10:45:-1
Please help me in finding a solution and a proper RUU or Guru Reset or Stock ROM zip.
PS:- Also my bootloader is not detecting my device. It only detects the device when the phone is switched on.
nkk71 said:
Don't really understand why anybody would want to go backwards, except for warranty, but in any case, your choice so here goes: you need s-off
1- So download Guru Reset 2.24.401.8 (closest available to your version): http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Flash it, you do need to WIPE, deselect "stock recovery", select ROOT, radio doesnt matter
2- Download rumrunner package 2.24.401.9, and use it to get S-Off
once s-off
3- remove TAMPERED: http://forum.xda-developers.com/showthread.php?t=2477792
4- set your phone to LOCKED: http://forum.xda-developers.com/showthread.php?t=2475914
5- download and run the following RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- do not take any OTA YET
7- if you insist on S-On, then "fastboot oem writesecureflag 3", if you don't mind keeping S-Off keep it
8- take the OTAs
If I've helped hit the thanks button
Let me know if you need any more help
Click to expand...
Click to collapse
Hello, Thanks for your help. I have to clear a doubt before applying this.
Thanks for the guide.
I have 3.62.401.1 World Wide English (WWE) HTC ONE with the last JB 4.3 OTA update.
Unlocked, Custom recovery, Rooted and S-OFF, Hboot 1.55, Stock ROM (stocks apps deleted)
I have speaker issue so I need to send back my phone to customer service.
I find the right RUU.exe for my CID => RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
I think this is with hboot 1.44
1. I have to downgrade htboot 1.55 to 1.44 before running RUU.exe?
2. Stock recovery is it included in RUU ?
Thanks in advance
Ethan_93 said:
Hello, Thanks for your help. I have to clear a doubt before applying this.
Thanks for the guide.
I have 3.62.401.1 World Wide English (WWE) HTC ONE with the last JB 4.3 OTA update.
Unlocked, Custom recovery, Rooted and S-OFF, Hboot 1.55, Stock ROM (stocks apps deleted)
I have speaker issue so I need to send back my phone to customer service.
I find the right RUU.exe for my CID => RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
I think this is with hboot 1.44
1. I have to downgrade htboot 1.55 to 1.44 before running RUU.exe?
2. Stock recovery is it included in RUU ?
Thanks in advance
Click to expand...
Click to collapse
Hi there, that post you quoted me on is really old, since then things have progressed ; if you want to send to repair, check my guide (has all the info for you): http://forum.xda-developers.com/showthread.php?t=2541082
Check it out, and If you have questions let me know.
nkk71 said:
Hi there, that post you quoted me on is really old, since then things have progressed ; if you want to send to repair, check my guide (has all the info for you): http://forum.xda-developers.com/showthread.php?t=2541082
Check it out, and If you have questions let me know.
Click to expand...
Click to collapse
Thank you. It's more clear for me.
I'm going to apply the Post 2 method. Just a question, at what step we return back to STOCK RECOVERY please ? RUU.EXE will restore or I have to do it maually ?
Ethan_93 said:
Thank you. It's more clear for me.
I'm going to apply the Post 2 method. Just a question, at what step we return back to STOCK RECOVERY please ? RUU.EXE will restore or I have to do it maually ?
Click to expand...
Click to collapse
if you're using RUU.EXE method it will be restored automatically.
after "Step 2: Run your RUU.EXE", your phone will be 100% out-of-the box (also fully wiped!), if you decide to go S-On, do it after the RUU, and before OTA updates (hboot 1.55+ can be nasty!!)
Hey guys and girls. A little backstory:
New to android
Use Cyanogenmod Installer
Get Purple Camera. Need to go back to stock.
Stumble upon guide by nkk71 http://forum.xda-developers.com/showthread.php?t=2541082
Botch last step
So I found an ruu with my CID and MID, but it was the GPE ruu not the ATT RUU! The ATT RUU zips don't list CID and MID so I assumed I should not use them and all that matters is matching those.
I had locked and went back to s-On when following the guide.... big mistake.
I've since unlocked and tried to root so that I could go back to S-Off.
Flashed several different correct recoveries and none will work. I am erasing the cache, but nothing works. I've tried the most recent versions of CWM and TWRP and can't get anywhere.
What should I try next?
bradreputation said:
Hey guys and girls. A little backstory:
New to android
Use Cyanogenmod Installer
Get Purple Camera. Need to go back to stock.
Stumble upon guide by nkk71 http://forum.xda-developers.com/showthread.php?t=2541082
Botch last step
So I found an ruu with my CID and MID, but it was the GPE ruu not the ATT RUU! The ATT RUU zips don't list CID and MID so I assumed I should not use them and all that matters is matching those.
I had locked and went back to s-On when following the guide.... big mistake.
I've since unlocked and tried to root so that I could go back to S-Off.
Flashed several different correct recoveries and none will work. I am erasing the cache, but nothing works. I've tried the most recent versions of CWM and TWRP and can't get anywhere.
What should I try next?
Click to expand...
Click to collapse
Sorry to hear that, I thought my guide was pretty clear
please post
1- a fastboot getvar all (excluding IMEI and s/n)
2- a screenshot of your bootloader
3- more details of what you have flashed (with links to the threads)
nkk71 said:
Sorry to hear that, I thought my guide was pretty clear
please post
1- a fastboot getvar all (excluding IMEI and s/n)
2- a screenshot of your bootloader
3- more details of what you have flashed (with links to the threads)
Click to expand...
Click to collapse
Your guide is very good and I thank you for it. I just messed up. I think it would be good to clarify that a person should reboot after flashing RUU before going back to S-On. I had the impression that was my only chance to go back S-On.
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4291mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-5d4c562c
hbootpreupdate: 11
gencheckpt: 0
http://imgur.com/yXDR6lr Shot of my Bootloader
This is what I flashed for RUU http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
I've flashed the latest TWRP and CWM. The problem really started when I installed CWM and Su from this guidehttp://forum.xda-developers.com/showthread.php?t=2292729.
bradreputation said:
Your guide is very good and I thank you for it. I just messed up. I think it would be good to clarify that a person should reboot after flashing RUU before going back to S-On. I had the impression that was my only chance to go back S-On.
Click to expand...
Click to collapse
Technically, you can, but shouldn't reboot the OS because of the OTA notification, which may make it tempting to take, but I'll try and rephrase the guide.
bradreputation said:
version-bootloader: 1.54.0000
version-main:
version-misc: PVT SHIP S-ON
product: m7_ul
modelid: PN0712000
cidnum: CWS__001
http://imgur.com/yXDR6lr Shot of my Bootloader
This is what I flashed for RUU http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
I've flashed the latest TWRP and CWM. The problem really started when I installed CWM and Su from this guidehttp://forum.xda-developers.com/showthread.php?t=2292729.
Click to expand...
Click to collapse
bootloader is unlocked, good... do NOT try and lock it!!
reflash TWRP and a custom ROM (you can try ARHD 31.6 or similar), and get S-OFF using rumrunner and/or firewater
i'm off for tonight, sorry about the mess
The stock att RUU's would almost certainly have the stock CWS_001 Cid. You just need one that is the same or postdated to your current hboot version since you are s-on now. Unfortunately, now that you are s-on, you will also need to relock the bootloader to flash an RUU. I would do that and then use firewater/rumrunner/latest s-off method to get s-off and unlock boot loader. Then you want to fix the "relocked" flag to "locked", and s-on again, and get it repaired.
I would try to get S-OFF where you are now.
I'll keep this here just in case
Otherwise, you can use the 3.xx RUU.EXE: http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
this will upgrade to hboot 1.55, and rumrunner and/or firewater should work on it.
(remember you need to relock bootloader for that to work with S-On, that's why i'm recommending to try where you are now, so you don't lock bootloader)
there is also a 4.xx RUU but do not use it, because it will upgrade your hboot to 1.56, making it even more difficult to S-OFF.
and once you're S-OFF, you should use this ruu.zip for my guide (which is for PN0712000 + CWS__001):
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/
AFH Mirror: http://www.androidfilehost.com/?fid=23501681358544977
nkk71 said:
I would try to get S-OFF where you are now.
I'll keep this here just in case
Otherwise, you can use the 3.xx RUU.EXE:
this will upgrade to hboot 1.55, and rumrunner and/or firewater should work on it.
(remember you need to relock bootloader for that to work with S-On, that's why i'm recommending to try where you are now, so you don't lock bootloader)
there is also a 4.xx RUU but do not use it, because it will upgrade your hboot to 1.56, making it even more difficult to S-OFF.
and once you're S-OFF, you should use this ruu.zip for my guide (which is for PN0712000 + CWS__001):
]
Click to expand...
Click to collapse
I was able to get TWRP (newest version) and ARHD (31.6) running. I then got S-OFF using Firewater. I'll use the RUU and follow the guide again.
I saw another one of your posts that suggested S-OFF may not effect warranty claims. Any further thought on that?
Thanks again for all your contributions.
bradreputation said:
I was able to get TWRP (newest version) and ARHD (31.6) running. I then got S-OFF using Firewater. I'll use the RUU and follow the guide again.
I saw another one of your posts that suggested S-OFF may not effect warranty claims. Any further thought on that?
Thanks again for all your contributions.
Click to expand...
Click to collapse
It's really very country/carrier/people specific, in theory, S-Off shouldn't matter as some phones accidentally ship S-Off (ok, it's very very very rare), but S-Off shouldn't void warranty https://twitter.com/htc/status/377422743626842112
Then again, in practice some carriers/technicians may try to use any excuse to refuse warranty.
Hello Everyone,
I have read multiple guides from here and want to emphasize what a great community this place seems to be!
I am a proud owner of an HTC One M7 with Miui installed.
I have CWM Recovery installed and am S-ON.
I have the tint problem of the camera and intend to bring it to the seller for a repair. This requires me to go back to the stock HTC Sense ROM.
Below is the output of the fastboot getvar all command:
c:\fastboot>fastboot.exe getvar all
(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) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4317mV
(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
all: Done!
finished. total time: 0.052s
Click to expand...
Click to collapse
I don't know how to choose the correct RUU. The only thing which comes close to what I have in terms of software version is this:
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
Should I use it?
Also, most of the guides start with the assumption that your phone is S-OFF (not really sure what that means exactly, but that's a different conversation).
Does that mean I can skip the steps for getting it back to S-ON from those guides and continue onward or I should get it first to S-OFF, do whatever needs to be done and then get it back to S-ON and continue with the RUU?
Thanks a lot, guys!
Best,
Wisher
WisherBG said:
Hello Everyone,
I have read multiple guides from here and want to emphasize what a great community this place seems to be!
I am a proud owner of an HTC One M7 with Miui installed.
I have CWM Recovery installed and am S-ON.
I have the tint problem of the camera and intend to bring it to the seller for a repair. This requires me to go back to the stock HTC Sense ROM.
Below is the output of the fastboot getvar all command:
I don't know how to choose the correct RUU. The only thing which comes close to what I have in terms of software version is this:
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
Should I use it?
Also, most of the guides start with the assumption that your phone is S-OFF (not really sure what that means exactly, but that's a different conversation).
Does that mean I can skip the steps for getting it back to S-ON from those guides and continue onward or I should get it first to S-OFF, do whatever needs to be done and then get it back to S-ON and continue with the RUU?
Thanks a lot, guys!
Best,
Wisher
Click to expand...
Click to collapse
That RUU will work for you, but it won't do any good for reinstating your warranty. You need to be s-off to return to 100% stock.
As you will need to set the bootloader back to ***LOCKED*** which requires s-off. With s-on the best you will get is ***RELOCKED*** and that's a sure sign the device was tampered with.
WisherBG said:
Hello Everyone,
I am a proud owner of an HTC One M7 with Miui installed.
I have CWM Recovery installed and am S-ON.
I don't know how to choose the correct RUU. The only thing which comes close to what I have in terms of software version is this:
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
Should I use it?
Thanks a lot, guys!
Best,
Wisher
Click to expand...
Click to collapse
Danny201281 said:
That RUU will work for you, but it won't do any good for reinstating your warranty. You need to be s-off to return to 100% stock.
Click to expand...
Click to collapse
this ruu won't work for you it's version is low you need same or higher version
Stock Reset Rom can help you but not 100%
S Off is only option
yatindroid said:
this ruu won't work for you it's version is low you need same or higher version
Stock Reset Rom can help you but not 100%
S Off is only option
Click to expand...
Click to collapse
Good catch I didn't spot he was on .11 not .9 :good:
Thanks for your replies.
So how do I go about getting a newer RUU?
I am currently trying to get S-OFF with rumrunner... hopefully it will work.
If I get it to be S-OFF, what should I do from that point on?
The unbranded EU Lollipop RUU (in ZIP form) is here:
http://forum.xda-developers.com/htc-one/general/htc-one-m7-european-signed-ruu-t3048384
EddyOS said:
The unbranded EU Lollipop RUU (in ZIP form) is here:
http://forum.xda-developers.com/htc-one/general/htc-one-m7-european-signed-ruu-t3048384
Click to expand...
Click to collapse
If you use that ruu you won't be able to get s-off, there is no working method to s-off hboot 1.60. You'd be better off finding a stock Rom to flash and get s-off with rumrunner. Once you update past hboot 1.57 you will have to pay $25 for sunshine to s-off and as I mentioned if you go to hboot 1.60 you will ha e to wait for a new exploit that will work with that version. No doubt that will also be an updated version of Sunshine
What's wrong with paying for S-OFF? Gotta show the Devs some love
So the current option is to find a stock 401.11 ROM?
Any ideas where to look for one?
I have found the original/stock OTA zip file for the 401.11 update from an article by Android Revolution HD.
Also the 401.11 stock firmware zip from the android revolution collection.
(sorry, I'm too new of a user and can't post the actual links but they can be found by googling "4.19.401.11 ruu" and seeing the android revolution blogspot article)
Am I correct in thinking that I should do the following:
1. Flash with this firmware (since it is the stock one).
2. Install the OTA zip with fastboot (I think there is a tutorial on how to do this). Will this work the same as installing a RUU?
3. Run rumrunner while still on hboot 1.56
4. Go to S-OFF
5. Return everything to stock
6. Apply latest OTA (lolipop etc.)
7. Pay the price if I want to have S-OFF later.
Best,
Wisher
WisherBG said:
So the current option is to find a stock 401.11 ROM?
Any ideas where to look for one?
I have found the original/stock OTA zip file for the 401.11 update from an article by Android Revolution HD.
Also the 401.11 stock firmware zip from the android revolution collection.
(sorry, I'm too new of a user and can't post the actual links but they can be found by googling "4.19.401.11 ruu" and seeing the android revolution blogspot article)
Am I correct in thinking that I should do the following:
1. Flash with this firmware (since it is the stock one).
2. Install the OTA zip with fastboot (I think there is a tutorial on how to do this). Will this work the same as installing a RUU?
3. Run rumrunner while still on hboot 1.56
4. Go to S-OFF
5. Return everything to stock
6. Apply latest OTA (lolipop etc.)
7. Pay the price if I want to have S-OFF later.
Best,
Wisher
Click to expand...
Click to collapse
No RUU, flash this inside TWRP recovery just like you would with a custom rom, only this will make your phone stock.
https://www.androidfilehost.com/?fid=23501681358545524
you cant manually flash OTA's whilst s-on, also you shouldnt need to flash firmware that you are already on.
Seanie280672 said:
No RUU, flash this inside TWRP recovery just like you would with a custom rom, only this will make your phone stock.
YOUR LINK (removed due to too new a user)
you cant manually flash OTA's whilst s-on, also you shouldnt need to flash firmware that you are already on.
Click to expand...
Click to collapse
Ok, I will be flashing with this guru reset file.
Then I should go S-OFF and follow the guide to get everything back to stock (no **UNLOCKED**, no TAMPERED, etc.).
Correct?
WisherBG said:
Ok, I will be flashing with this guru reset file.
Then I should go S-OFF and follow the guide to get everything back to stock (no **UNLOCKED**, no TAMPERED, etc.).
Correct?
Click to expand...
Click to collapse
get s-off as long as you can, do not accept any updates.
after s-off you will need to flash HBOOT 1.44 and a very early RUU, then get rid of the flags and s-on before updating.
removing the flags and then going s-on with anything higher than HBOOT 1.54 and the flags come back on the next reboot.
Seanie280672 said:
get s-off as long as you can, do not accept any updates.
after s-off you will need to flash HBOOT 1.44 and a very early RUU, then get rid of the flags and s-on before updating.
removing the flags and then going s-on with anything higher than HBOOT 1.54 and the flags come back on the next reboot.
Click to expand...
Click to collapse
Ok, thanks! I will see what I can do with the help of the guides in this forum.
Any helpful links will be highly appreciated.
Best,
Wisher
WisherBG said:
Ok, thanks! I will see what I can do with the help of the guides in this forum.
Any helpful links will be highly appreciated.
Best,
Wisher
Click to expand...
Click to collapse
just report back here once your s-off and all the guys will be more than happy to help you :good:
Seanie280672 said:
after s-off you will need to flash HBOOT 1.44 and a very early RUU, then get rid of the flags and s-on before updating.
removing the flags and then going s-on with anything higher than HBOOT 1.54 and the flags come back on the next reboot.
Click to expand...
Click to collapse
Important Thanks
Got the following with rumrunner:
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
Click to expand...
Click to collapse
However I can do "adb shell" and then "su" brings me to be a super user.
What is different to what the situation was when I was with MIUI is that now when I type "adb shell" I am not automatically root (don't have # but $ at the console). When I do "su", the $ changes to #, which basically means that I am root.
I guess rumrunner has a requirement that you are root by default when logging via adb shell.
Any idea on a fix?
Best,
Wisher
EddyOS said:
What's wrong with paying for S-OFF? Gotta show the Devs some love
Click to expand...
Click to collapse
There's nothing wrong with paying for s-off. I have purchased Sunshine myself when necessary, and made regular donations to other devs. but it's only fair to inform people of there options before you land them with a $25 solution not everyone has money to spare for that sort of thing. :good:
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
WisherBG said:
So the current option is to find a stock 401.11 ROM?
Any ideas where to look for one?
I have found the original/stock OTA zip file for the 401.11 update from an article by Android Revolution HD.
Also the 401.11 stock firmware zip from the android revolution collection.
(sorry, I'm too new of a user and can't post the actual links but they can be found by googling "4.19.401.11 ruu" and seeing the android revolution blogspot article)
Am I correct in thinking that I should do the following:
1. Flash with this firmware (since it is the stock one).
2. Install the OTA zip with fastboot (I think there is a tutorial on how to do this). Will this work the same as installing a RUU?
3. Run rumrunner while still on hboot 1.56
4. Go to S-OFF
5. Return everything to stock
6. Apply latest OTA (lolipop etc.)
7. Pay the price if I want to have S-OFF later.
Best,
Wisher
Click to expand...
Click to collapse
You should try rumrunner with the Rom @Seanie280672 posted to gain s-off. Not guaranteed to work as HTC started patching firmware at this point but if you need 100% stock it's your best chance to s-off without Sunshine.
If rumrunner won't work Sunshine is still cheaper than paying for the repair, and when you get your device back you can use Sunshine again for free, as long as it is the same device and not a replacement :good:
Seanie280672 said:
No RUU, flash this inside TWRP recovery just like you would with a custom rom, only this will make your phone stock.
https://www.androidfilehost.com/?fid=23501681358545524
you cant manually flash OTA's whilst s-on, also you shouldnt need to flash firmware that you are already on.
Click to expand...
Click to collapse
---------- Post added at 09:34 PM ---------- Previous post was at 09:31 PM ----------
WisherBG said:
Got the following with rumrunner:
However I can do "adb shell" and then "su" brings me to be a super user.
What is different to what the situation was when I was with MIUI is that now when I type "adb shell" I am not automatically root (don't have # but $ at the console). When I do "su", the $ changes to #, which basically means that I am root.
I guess rumrunner has a requirement that you are root by default when logging via adb shell.
Any idea on a fix?
Best,
Wisher
Click to expand...
Click to collapse
Did you select the option to install root when you flashed the rom?
Danny201281 said:
There's nothing wrong with paying for s-off. I have purchased Sunshine myself when necessary, and made regular donations to other devs. but it's only fair to inform people of there options before you land them with a $25 solution not everyone has money to spare for that sort of thing. :good:
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
You should try rumrunner with the Rom @Seanie280672 posted to gain s-off. Not guaranteed to work as HTC started patching firmware at this point but if you need 100% stock it's your best chance to s-off without Sunshine.
If rumrunner won't work Sunshine is still cheaper than paying for the repair, and when you get your device back you can use Sunshine again for free, as long as it is the same device and not a replacement :good:
Did you select the option to install root when you flashed the rom?
Click to expand...
Click to collapse
Thanks for the info.
I did select to have the phone rooter.
However, I remembered that I forgot to switch fastboot off while testing rumrunner with the ROM from @Seanie280672.
I have now disabled this and am trying again. If it doesn't work, will reinstall the ROM again with CWM and *make sure* to have super user privileges (although I do have the Superuser app installed now just after flashing.)
I also remember that I had some super user issues when I was trying to install MIUI and had to install some zip via CWM. I still have that zip so will try with it.
Again, thank you VERY VERY much for helping me out!
Best,
Wisher
WisherBG said:
Thanks for the info.
I did select to have the phone rooter.
However, I remembered that I forgot to switch fastboot off while testing rumrunner with the ROM from @Seanie280672.
I have now disabled this and am trying again. If it doesn't work, will reinstall the ROM again with CWM and *make sure* to have super user privileges (although I do have the Superuser app installed now just after flashing.)
I also remember that I had some super user issues when I was trying to install MIUI and had to install some zip via CWM. I still have that zip so will try with it.
Again, thank you VERY VERY much for helping me out!
Best,
Wisher
Click to expand...
Click to collapse
your better off using TWRP recovery to flash the rom, there should be an option to root during the installer, but if there isnt then TWRP will ask you if you would like to root before leaving recovery.
Seanie280672 said:
your better off using TWRP recovery to flash the rom, there should be an option to root during the installer, but if there isnt then TWRP will ask you if you would like to root before leaving recovery.
Click to expand...
Click to collapse
Did it via CWM, made sure to select to root the phone. Still, I can do "su" when in the phone shell via adb, but it won't be directly with root access after "adb shell".
Now will try with TWRP (since installing the guru reset rom also resets the recovery to the HTC stock) and report back.
Good thing is I still have the MIUI backed up to use with CWM.
I will write soon.
Best,
Wisher
Hi , I have a One (M7) and I'm planning to send it back to HTC in order to fix the purple tint problem.
I'm S-off and I want to Lock the bootloader and returning to Stock + S-on.
I'll follow these steps from http://forum.xda-developers.com/showthread.php?t=2541082 Post #4 but i have doubts marked in blue
Step 0: -not in the previous thread link- I have hboot 1.57. Do I have to move to 1.44 ?
Step 1: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
and confirm no TAMPERED and LOCKED status. (I have UNLOCKED status, so I'm only have to set it to LOCKED, isn't it?)
Step 2: Flash your RUU.zip
Download your MID & CID compatible RUU.zip: http://www.htc1guru.com/downloads/ruu-zip-downloads/
Rename the downloaded file to ruu.zip (careful about ruu.zip.zip in Windows)
(My mid is PN0710000 and cid= HTC__304 so I'll flash
RUU+Zip+M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed)
Do I need first to flash a stock splash?. Currently, I have Maximus 53 HD rom installed (with its own splash bootloader).
Step 3: if YOU decide to go S-On (Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
fastboot oem writesecureflag 3
( with 1.44 hboot, doesn't exist the possibility of a TEMPERED boot loop, Is it right?)
Thx in advance.
Nasrudin78 said:
Hi , I have a One (M7) and I'm planning to send it back to HTC in order to fix the purple tint problem.
I'm S-off and I want to Lock the bootloader and returning to Stock + S-on.
I'll follow these steps from http://forum.xda-developers.com/showthread.php?t=2541082 Post #4 but i have doubts marked in blue
Step 0: -not in the previous thread link- I have hboot 1.57. Do I have to move to 1.44 ?
Step 1: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
and confirm no TAMPERED and LOCKED status. (I have UNLOCKED status, so I'm only have to set it to LOCKED, isn't it?)
Step 2: Flash your RUU.zip
Download your MID & CID compatible RUU.zip: http://www.htc1guru.com/downloads/ruu-zip-downloads/
Rename the downloaded file to ruu.zip (careful about ruu.zip.zip in Windows)
(My mid is PN0710000 and cid= HTC__304 so I'll flash
RUU+Zip+M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed)
Do I need first to flash a stock splash?. Currently, I have Maximus 53 HD rom installed (with its own splash bootloader).
Step 3: if YOU decide to go S-On (Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
fastboot oem writesecureflag 3
( with 1.44 hboot, doesn't exist the possibility of a TEMPERED boot loop, Is it right?)
Thx in advance.
Click to expand...
Click to collapse
You need to downgrade hboot to 1.44 or you will get a fail when you use the ruu.
Also hboot 1.44 has the ability to boot a custom recovery without actually flashing it to the device and returning to s-on on hboots above 1.55 could lead to Tampered message returning after you've completed the process. Then you will need to go back to s-off and start again. So it is best to downgrade hboot to 1.44, lock bootloader remove tampered, run the ruu. Then take the first (and only the first) OTA update. If the update installs OK then it's safe to say you can go back to s-on. :good:
Sent from my HTC One using Tapatalk
But what happens if I decide not to take 1st OTA update? Can i omit this step and run "fastboot oem ...3" (taking into account that I flashed hboot 1.44) ?
Nasrudin78 said:
But what happens if I decide not to take 1st OTA update? Can i omit this step and run "fastboot oem ...3" (taking into account that I flashed hboot 1.44) ?
Click to expand...
Click to collapse
Everything must be stock 100% before you go back to s-on. That's why you must flash the RUU. You don't have to take the first OTA, bit it's a good way for ensuring it's safe to turn s-on. If the OTA installs OK then you have unmodified system and it's safe to lock it up. The RUU should do the Job it's just an extra precaution.
Sent from my HTC One using Tapatalk
Uppps, but now that I'm reading more in detail... If I decide to take the 1st OTA just for extra checking, Can this OTA change the hboot (I mean, hboot 1.44 to more actual one)
doing "fastboot oem ...3" impossible due to the Tampered message protection in hboot > 1.55?
Thx
Danny201281 said:
Everything must be stock 100% before you go back to s-on. That's why you must flash the RUU. You don't have to take the first OTA, bit it's a good way for ensuring it's safe to turn s-on. If the OTA installs OK then you have unmodified system and it's safe to lock it up. The RUU should do the Job it's just an extra precaution.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Hi again,
I downgraded hboot to 1.44, but I realized that exists this Lollipop RUU.zip --> PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
(https://www.androidfilehost.com/?fid=24052804347763626)
Is it a good idea,having hboot 1.44, flashing this .zip, instead of Jellybean -RUU+Zip+M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A .13.3231.27_10.31.1131.05_release_310878_signed-? and therefore ,accept 1st OTA and apply fastboot oem ...3 afterwards?
I'm scared because i saw ((status read failed (Too many links))) when I only tested a "fastboot getvar all" command:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <DEL>
(bootloader) imei: <DEL>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4165mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Execution time is 1(s)
Click to expand...
Click to collapse
And finally, If it's not possible and I install JB_50 RUU.zip, can I accept ALL OTA's up to Lollipop and then apply "fastboot oem writesecureflag 3"?
Thx!
Nasrudin78 said:
Hi again,
I downgraded hboot to 1.44, but I realized that exists this Lollipop RUU.zip --> PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
(https://www.androidfilehost.com/?fid=24052804347763626)
Is it a good idea,having hboot 1.44, flashing this .zip, instead of Jellybean -RUU+Zip+M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A .13.3231.27_10.31.1131.05_release_310878_signed-? and therefore ,accept 1st OTA and apply fastboot oem ...3 afterwards?
Click to expand...
Click to collapse
Even with these new RUU's you still need to downgrade to go back to s-on. You must go s-on with a hboot 1.55 or below
I'm scared because i saw ((status read failed (Too many links))) when I only tested a "fastboot getvar all" command:
Click to expand...
Click to collapse
This is normal with hboot 1.44 and nothing to worry about. All devices with hboot 1.44 give that error after getvar all.
And finally, If it's not possible and I install JB_50 RUU.zip, can I accept ALL OTA's up to Lollipop and then apply "fastboot oem writesecureflag 3"?
Thx!
Click to expand...
Click to collapse
No you must go s-on after the first OTA from JB_50 RUU.zip. Further OTA updates will upgrade you to hboot 1.56 then it's to late to go s-on without risking TAMPERED flag returning :good:
Sent from my HTC One using Tapatalk
Danny201281 said:
Even with these new RUU's you still need to downgrade to go back to s-on. You must go s-on with a hboot 1.55 or below
This is normal with hboot 1.44 and nothing to worry about. All devices with hboot 1.44 give that error after getvar all.
No you must go s-on after the first OTA from JB_50 RUU.zip. Further OTA updates will upgrade you to hboot 1.56 then it's to late to go s-on without risking TAMPERED flag returning :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Ok.
So, what do you suggest me to install, supposing I have hboot 1.44 installed, Lollipop RUU or JB RUU?
I don't understand when you say this:
No you must go s-on after the first OTA from JB_50 RUU.zip. Further OTA updates will upgrade you to hboot 1.56 then it's to late to go s-on without risking TAMPERED flag returning
Click to expand...
Click to collapse
If I run JB_RUU, Doesn't it change hboot version even if I take only 1st OTA?
Otherwise, If I run Lollipop_RUU doesn't it change hboot version even if I take only 1st OTA?
Why do 2nd,3rd OTA and so on change hboot and not 1st (only for understanding the reason)?
I'm aware that hboot > 1.54 adds "TAMPERED" ...
Thx
Nasrudin78 said:
Ok.
So, what do you suggest me to install, supposing I have hboot 1.44 installed, Lollipop RUU or JB RUU?
I don't understand when you say this:
If I run JB_RUU, Doesn't it change hboot version even if I take only 1st OTA?
Otherwise, If I run Lollipop_RUU doesn't it change hboot version even if I take only 1st OTA?
I'm aware that hboot > 1.54 adds "TAMPERED" ...
Thx
Click to expand...
Click to collapse
You must flash the jb ruu. After that you will still be on hboot 1.44.
Then you can take OTA updates. The first OTA will update hboot to 1.54. It is still safe to go back to s-on because your below hboot 1.56
Technically you can also take the next OTA up to hboot 1.55. But I don't recommend it. You won't gain anything from it and it increases the risk of problems later on.
Sent from my HTC One using Tapatalk
Danny201281 said:
You must flash the jb ruu. After that you will still be on hboot 1.44.
Then you can take OTA updates. The first OTA will update hboot to 1.54. It is still safe to go back to s-on because your below hboot 1.56
Technically you can also take the next OTA up to hboot 1.55. But I don't recommend it. You won't gain anything from it and it increases the risk of problems later on.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
And what happens if technical support receives the terminal with JB?
I mean, They asked me if my terminal had the last firmware version, because although I explained them that it was a HW problem, they insist to go last version and check if it fixes .
Then if I send the terminal (let's supose up to hboot 1.55 and JB) they would discover that I'm hiding something to them...
That's the reason I want to let the terminal with the latest firmware and Android version...
Thx
Danny201281 said:
You must flash the jb ruu. After that you will still be on hboot 1.44.
Then you can take OTA updates. The first OTA will update hboot to 1.54. It is still safe to go back to s-on because your below hboot 1.56
Technically you can also take the next OTA up to hboot 1.55. But I don't recommend it. You won't gain anything from it and it increases the risk of problems later on.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Let me explain what I'm planning to do and tell me if it's a good idea or not.
(with hboot 1.44 also installed)
Option 1:
htc_fastboot flash zip LP.zip (x2)
Apply 1st OTA (risk of TAMPERING??)
SOFF -> SON
Click to expand...
Click to collapse
Option 2: (safer??)
fastboot flash zip JB.zip (x2)
Apply 1st OTA ( here I'd have hboot 1.54)
SOFF -> SON
Apply 2nd, 3rd, and so OTA's up to LP and last firmware (risk of TAMPERING??)
Click to expand...
Click to collapse
Thanks, that's my last question. Sorry
Nasrudin78 said:
Let me explain what I'm planning to do and tell me if it's a good idea or not.
(with hboot 1.44 also installed)
Thanks, that's my last question. Sorry
Click to expand...
Click to collapse
Definitely option 2 :good: Follow nkk71's guide here http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4
Using the JB ruu you have. And it will be fine
Sent from my HTC One using Tapatalk
Danny201281 said:
Definitely option 2 :good: Follow nkk71's guide here http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4
Using the JB ruu you have. And it will be fine
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks Danny,
Option 2 worked like a charm! But i spent more than 3hours during the overall OTA update process. LOL!