Related
I'm running converted GE with 1.54 Google Hboot on my AT&T M7 (S-Off)
in order to go back to stock with the RUU I have to first load the 2.17 firmware Vomer provided in his thread.
If I don't do that I get error 155 when using the RUU.
I lock my bootloader before running it.
What am I missing. I thought S-off and SuperCID bypassed the checks and RUU's just worked.
Thanks for any advice.
Why are you locking your bootloader? You don't need to do that with s-off, I thought.
I wonder if there is some sort of check in the GE bootloader that isn't s-on/s-off dependent.
iElvis said:
Why are you locking your bootloader? You don't need to do that with s-off, I thought.
I wonder if there is some sort of check in the GE bootloader that isn't s-on/s-off dependent.
Click to expand...
Click to collapse
I found RUU failed with it unlocked.
I'm very confused at this point and just wonder if HTC changed things up on us.
gunnyman said:
I found RUU failed with it unlocked.
I'm very confused at this point and just wonder if HTC changed things up on us.
Click to expand...
Click to collapse
Well, the new 1.54 hboot thwarts the s-off exploit, as you know. It could be HTC introduced some elements with it that restore some type of security checks. It might explain the weird things going on in the s-off threads.
I know there are some substantial differences between the 2.17 hboot and 2.24 hboot even though the version number is the same.
iElvis said:
Well, the new 1.54 hboot thwarts the s-off exploit, as you know. It could be HTC introduced some elements with it that restore some type of security checks. It might explain the weird things going on in the s-off threads.
I know there are some substantial differences between the 2.17 hboot and 2.24 hboot even though the version number is the same.
Click to expand...
Click to collapse
SO maybe it isn't me.
Good to know.
Should I be able to just flash a 1.44 HBoot to get around this? Because either the one I have is corrupt, or it doesn't work thanks to the new 1.54 HBoot.
Lucky for me, the 2.17 firmwre.zip installs and things work after that.
gunnyman said:
SO maybe it isn't me.
Good to know.
Should I be able to just flash a 1.44 HBoot to get around this? Because either the one I have is corrupt, or it doesn't work thanks to the new 1.54 HBoot.
Lucky for me, the 2.17 firmwre.zip installs and things work after that.
Click to expand...
Click to collapse
You might try sticking with the 2.17 hboot and see if that helps.
iElvis said:
You might try sticking with the 2.17 hboot and see if that helps.
Click to expand...
Click to collapse
I have it on the Google Edition HBoot for OTA updates but heck that OTA might make reversal impossible.
*eek*
gunnyman said:
I have it on the Google Edition HBoot for OTA updates but heck that OTA might make reversal impossible.
*eek*
Click to expand...
Click to collapse
Must be the GE hboot or perhaps hboot 1.54 from 2.24 in general. I had a AT&T device with the new firmware and hboot 1.54 (from 2.17) I was able to run the RUU with s-off and bootloader still unlocked.
My fear is an ota for the ge would break the ability to downgrade hboot. The 2.17 works because it is the same 1.54
Okay I'm not sure about GE but when I had 2.24 and HBOOT 1.54.0000 I just ran the 1.28.401.7 RUU and it all went fine. I'm S-OFF of course.
Rex2369 said:
Okay I'm not sure about GE but when I had 2.24 and HBOOT 1.54.0000 I just ran the 1.28.401.7 RUU and it all went fine. I'm S-OFF of course.
Click to expand...
Click to collapse
weird.
I've calmed my own fears I was able to flash sneakyghost's provided 1.44Hboot. I'm safe.
gunnyman said:
weird.
I've calmed my own fears I was able to flash sneakyghost's provided 1.44Hboot. I'm safe.
Click to expand...
Click to collapse
Coming from full GE experience (1.54 hboot, GE recovery and ROM), I had to flash just the 1.44 hboot and relock my bootloader before the Dev RUU worked for me.
Sent from my HTC One using xda premium
So clearly HTC changed something about what S-off means and what you can and can't do with it.
hello every one this is my first post i need some help please.
i bought a htc one preowned and i have since been in settings and its running a custom rom
android revolution hd 12.1 by mike 1986
my phone cid is htc_001
how do i return it to stock htc os
i have read a few posts before posting here i no i have to re lock bootloader then flash the ruu
i was wondering is there an easier way to relock bootloader and flash the ruu could some one also point me in the right direction
to which ruu to download with a link if possible to download.
thanks in advance for any help u may give with some simple instructions that i can understand as this is new to me and do not want to
make a mistake.
thankyou.
Is it S-OFF at the moment?
EddyOS said:
Is it S-OFF at the moment?
Click to expand...
Click to collapse
says m7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4a.18.3263.15
openDSP-v26.120.274.0202
eMMC-boot
so im guessing so
You don't need to relock, if you're s-off you can run whatever RUU you like.
iElvis said:
You don't need to relock, if you're s-off you can run whatever RUU you like.
Click to expand...
Click to collapse
thnks for your help can u link me to the correct ruu if u dont mind been looking not sure which one to download
thanks very much for your help to all.
Infamouslimey said:
thnks for your help can u link me to the correct ruu if u dont mind been looking not sure which one to download
thanks very much for your help to all.
Click to expand...
Click to collapse
Where was the phone purchased and what was the carrier? It's possible your CID was changed.
Assuming htc__001 is correct, the RUU collection is here:
http://forum.xda-developers.com/showthread.php?p=39588860
There are no RUUs for 4.2, so this would mean downgrading. But you should then start getting OTAs.
Note that running a RUU will fully wipe the phone. So back up anything on it you want to keep.
iElvis said:
Where was the phone purchased and what was the carrier? It's possible your CID was changed.
Assuming htc__001 is correct, the RUU collection is here:
http://forum.xda-developers.com/showthread.php?p=39588860
There are no RUUs for 4.2, so this would mean downgrading. But you should then start getting OTAs.
Click to expand...
Click to collapse
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Infamouslimey said:
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Click to expand...
Click to collapse
You have superCID, which means any RUU will run. You have the generic European model. CIDGetter is pulling the original cid from some system file, but it doesn't reflect the actual cid.
Infamouslimey said:
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Click to expand...
Click to collapse
will this ruu work
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Infamouslimey said:
will this ruu work
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Click to expand...
Click to collapse
Yes, that's the one you want. You don't need to relock or anything being s-off. Just plug into your computer and run the ruu.
iElvis said:
Yes, that's the one you want. You don't need to relock or anything being s-off. Just plug into your computer and run the ruu.
Click to expand...
Click to collapse
thank you very much for all your help great site with such helpful members.
will this method re-lock bootloader and put s-off back to s-on or whatever its called ?
Infamouslimey said:
will this method re-lock bootloader and put s-off back to s-on or whatever its called ?
Click to expand...
Click to collapse
No and no. You have to do those manually, and there is no need to here.
if i wanted to re lock bootloader and put s back on how would i do it trying to learn so i dont have to keep asking for help ?
Infamouslimey said:
if i wanted to re lock bootloader and put s back on how would i do it trying to learn so i dont have to keep asking for help ?
Click to expand...
Click to collapse
That is a bit trickier and riskier since you don't know what was done to your phone before you bought it. I don't recommend going back to s-on because of this. However, running the correct RUU should put you back to safe stock.
Once the RUU has run and you've confirmed that the phone boots and is back to a stable stock configuration, you need to reboot and run a series of commands in fastboot:
fastboot oem writecid HTC__001
This will restore your stock CID. Note that there are two underscores there.
fastboot reboot-bootloader
Confirm on your bootloader screen that the CID is correct.
fastboot oem lock
This will relock your bootloader. Reboot again and confirm that it says "LOCKED" on your bootloader (Not "RELOCKED"). Boot up your phone and confirm that everything seems to be running correctly. You may want to give this a few days. Then reboot to bootloader when you're comfortable with it.
fastboot oem writesecureflag 3
This will put you back to s-on. When you reboot from here, your bootloader should say LOCKED and S-ON as if it was out of the box.
iElvis said:
That is a bit trickier and riskier since you don't know what was done to your phone before you bought it. I don't recommend going back to s-on because of this. However, running the correct RUU should put you back to safe stock.
Once the RUU has run and you've confirmed that the phone boots and is back to a stable stock configuration, you need to reboot and run a series of commands in fastboot:
fastboot oem writecid HTC__001
This will restore your stock CID. Note that there are two underscores there.
fastboot reboot-bootloader
Confirm on your bootloader screen that the CID is correct.
fastboot oem lock
This will relock your bootloader. Reboot again and confirm that it says "LOCKED" on your bootloader (Not "RELOCKED"). Boot up your phone and confirm that everything seems to be running correctly. You may want to give this a few days. Then reboot to bootloader when you're comfortable with it.
fastboot oem writesecureflag 3
This will put you back to s-on. When you reboot from here, your bootloader should say LOCKED and S-ON as if it was out of the box.
Click to expand...
Click to collapse
thanks very much for all your help ill install the fastboot files anyway so if need them there there.
many thanks
I too need to put my T-mobile HTC One back to stock somehow, but don't even know where to start, I saw this thread so I didn't want to clutter up the subforum, and thought that maybe I should ask here. I'm at 1.27.531.11, S-ON, rooted w/ unlocked bootloader, and would like to make it look like nothing happened to it when I return it to the store tomorrow. Could you please give me some pointers?
N0wy0ud1e said:
I too need to put my T-mobile HTC One back to stock somehow, but don't even know where to start, I saw this thread so I didn't want to clutter up the subforum, and thought that maybe I should ask here. I'm at 1.27.531.11, S-ON, rooted w/ unlocked bootloader, and would like to make it look like nothing happened to it when I return it to the store tomorrow. Could you please give me some pointers?
Click to expand...
Click to collapse
You need to s-off first or it will say "RELOCKED" on the bootloader. Problem is you may or may not be able to s-off right now. There is a new T-Mo exploit that supposedly works but I know nothing about it.
Once you do that, you can run an older RUU, which will remove the TAMPERED from the bootloader, then relock and s-on as described above.
iElvis said:
You need to s-off first or it will say "RELOCKED" on the bootloader. Problem is you may or may not be able to s-off right now. There is a new T-Mo exploit that supposedly works but I know nothing about it.
Once you do that, you can run an older RUU, which will remove the TAMPERED from the bootloader, then relock and s-on as described above.
Click to expand...
Click to collapse
Crap. Well I know they're not going to check the bootloader lol, just that when you turn on the phone, you'll see the red text at the bottom saying "Developmental purposes" and I can't remember the rest of the message. Can I make that disappear so it just shows nothing on the white background but the green HTC logo? Btw thanks for the reply.
N0wy0ud1e said:
Crap. Well I know they're not going to check the bootloader lol, just that when you turn on the phone, you'll see the red text at the bottom saying "Developmental purposes" and I can't remember the rest of the message. Can I make that disappear so it just shows nothing on the white background but the green HTC logo? Btw thanks for the reply.
Click to expand...
Click to collapse
That goes away when you relock.
I found the RUU in http : / / www . htcdev.com/devcenter/downloads and tought if is possible do it.
Regards
only if your s-off
Victor Potasso said:
I found the RUU in http : / / www . htcdev.com/devcenter/downloads and tought if is possible do it.
Regards
Click to expand...
Click to collapse
Like I said in your previous thread http://forum.xda-developers.com/showthread.php?t=2552669
You might want to read this: http://forum.xda-developers.com/showthread.php?t=2541082
If you read, then you will understand that the RUU you want to execute need to be compatible with both your CID, MID and hboot version.
So yes its possible, but you need to be s-off to change CID/MID and to downgrade hboot if required.
and please don't start 2 different threads for relatively the same questions.
Hope it help
alray said:
Like I said in your previous thread http://forum.xda-developers.com/showthread.php?t=2552669
You might want to read this: http://forum.xda-developers.com/showthread.php?t=2541082
If you read, then you will understand that the RUU you want to execute need to be compatible with both your CID, MID and hboot version.
So yes its possible, but you need to be s-off to change CID/MID and to downgrade hboot if required.
and please don't start 2 different threads for relatively the same questions.
Hope it help
Click to expand...
Click to collapse
Can I set my device to s-off?
Victor Potasso said:
Can I set my device to s-off?
Click to expand...
Click to collapse
yes, use revone tool for hboot 1.44 or use rumrunner tool for hboot 1.54 and 1.55
This is the first thing listed in the thread I linked above.....
First you need to be S-Off, this will NOT work with S-On!!!
A) If you’re on hboot 1.44 use revone to get S-Off: http://forum.xda-developers.com/show....php?t=2314582
B) If you’re on hboot 1.54/1.55 use rumrunner to get S-Off: http://rumrunner.us/ and http://forum.xda-developers.com/show....php?t=2487888
Click to expand...
Click to collapse
---------- Post added at 02:38 AM ---------- Previous post was at 02:31 AM ----------
if you need to change cid:
Code:
fastboot oem writecid GOOGL01
where ''GOOGL01'' is the GPE cid
If you need to change MID:
http://forum.xda-developers.com/showthread.php?t=2322820
alray said:
yes, use revone tool for hboot 1.44 or use rumrunner tool for hboot 1.54 and 1.55
This is the first thing listed in the thread I linked above.....
---------- Post added at 02:38 AM ---------- Previous post was at 02:31 AM ----------
if you need to change cid:
Code:
fastboot oem writecid GOOGL01
where ''GOOGL01'' is the GPE cid
If you need to change MID:
http://forum.xda-developers.com/showthread.php?t=2322820
Click to expand...
Click to collapse
My hboot is 1.55 and I tried rumrunner but It got unsuccess. It stops when chilling... Do u think it happens because I have to change my MID
Victor Potasso said:
My hboot is 1.55 and I tried rumrunner but It got unsuccess. It stops when chilling... Do u think it happens because I have to change my MID
Click to expand...
Click to collapse
I can't answer that cause I'm not familiar with rumrunner since I s-off'd my One when it was on 1.44 hboot with revone. In theory rumrunner 0.5.0 should work on all international variant with hboot 1.54 and up except verizon model that need a different version of rumrunner. Maybe you should ask help directly on rumrunner thread for that step or search the forum for similar issue with s-off on 1.55. Hope you will find out.
alray said:
I can't answer that cause I'm not familiar with rumrunner since I s-off'd my One when it was on 1.44 hboot with revone. In theory rumrunner 0.5.0 should work on all international variant with hboot 1.54 and up except verizon model that need a different version of rumrunner. Maybe you should ask help directly on rumrunner thread for that step or search the forum for similar issue with s-off on 1.55. Hope you will find out.
Click to expand...
Click to collapse
Thanks mate, but I can't because I just Signed Up. I Can't write something in that threads yet :crying:
Cheers mate
Victor Potasso said:
Thanks mate, but I can't because I just Signed Up. I Can't write something in that threads yet :crying:
Cheers mate
Click to expand...
Click to collapse
I went back and forth with rumrunner and moonshine while using a rom 4.3 GPE ROM with twrp and it kept failing. ultimately installed a 4.1.2 stock then used revone and it worked wonderfully. I was able to remove the tampered flag, unlock the stock bootloader and flash the GPE 4.3 and receive the updates. I also only have a mac so i was limited in not being able to run .exe's.
swag1981 said:
I went back and forth with rumrunner and moonshine while using a rom 4.3 GPE ROM with twrp and it kept failing. ultimately installed a 4.1.2 stock then used revone and it worked wonderfully. I was able to remove the tampered flag, unlock the stock bootloader and flash the GPE 4.3 and receive the updates. I also only have a mac so i was limited in not being able to run .exe's.
Click to expand...
Click to collapse
I'm using Parallels Desktop as Virtual Machine. I use to run Win8 and Ubuntu with it. It works very well.
:good: w w w . parallels.com/products/desktop/
Sorry mate, I'm a bit noob. I got the TAMPERED FLAG when I tried to get S-OFF with rumrunner. What does it means?
I tried moonshine as well but it doesn't start
I've tried to get 4.1.2 stock as well but my device has to be S-OFF :crying:
Regards
Victor Potasso said:
I'm using Parallels Desktop as Virtual Machine. I use to run Win8 and Ubuntu with it. It works very well.
:good: w w w . parallels.com/products/desktop/
Sorry mate, I'm a bit noob. I got the TAMPERED FLAG when I tried to get S-OFF with rumrunner. What does it means?
I tried moonshine as well but it doesn't start
I've tried to get 4.1.2 stock as well but my device has to be S-OFF :crying:
Regards
Click to expand...
Click to collapse
Tampered flag is just that, a flag. It doesnt hinder anything, just a pop up for "Warranty" purposes. The flag pops up when you unlock the bootloader but when you get S-Off you can remove the flag.
Since you have access to windows i would go to http://forum.xda-developers.com/showthread.php?t=2428276 and find the .exe RUU for your area. Just get into your bootloader, select fastboot usb and run the .exe. Pick the lowest firmware available so you can ensure that you get the 1.44 hboot.
swag1981 said:
Tampered flag is just that, a flag. It doesnt hinder anything, just a pop up for "Warranty" purposes. The flag pops up when you unlock the bootloader but when you get S-Off you can remove the flag.
Since you have access to windows i would go to http://forum.xda-developers.com/showthread.php?t=2428276 and find the .exe RUU for your area. Just get into your bootloader, select fastboot usb and run the .exe. Pick the lowest firmware available so you can ensure that you get the 1.44 hboot.
Click to expand...
Click to collapse
swag1981 my hboot is 1.55
Is the process with .zip and .exe different? Maybe if I run .exe it can work with S-ON? :victory:
Victor Potasso said:
swag1981 my hboot is 1.55
Is the process with .zip and .exe different? Maybe if I run .exe it can work with S-ON? :victory:
Click to expand...
Click to collapse
The zip can only be used with S-Off where as the exe is designed to be used to return a phone to stock with S-On.
Just get into fastboot and run the exe, it should do the rest for you. It will wipe the entire phone, but as far as I'm concerned, a blank phone is better than an unusable one.
I'm not sure if the hboot makes a difference, but mine downgraded when I flashed an older RUU.
Once you get the older hboot and firmware, you may have to unlock your bootloader again through HTC Dev, then S-Off. Once your S-Off unlocking your bootloader is much easier.
Sent from my HTC One using Tapatalk
Whoo ho! Nice mate. I wanna to get it.
I'll try this soon. Thanks again mate. You've been helping me a lot.
Cheers
Whoo ho! Nice mate. I wanna to get it.
I'll try this soon. Thanks again mate. You've been helping me a lot.
:cheers:
Give this site a read over too when you get a chance http://www.htc1guru.com/downloads/
Sent from my HTC One using Tapatalk
swag1981 said:
The zip can only be used with S-Off where as the exe is designed to be used to return a phone to stock with S-On.
Just get into fastboot and run the exe, it should do the rest for you. It will wipe the entire phone, but as far as I'm concerned, a blank phone is better than an unusable one.
I'm not sure if the hboot makes a difference, but mine downgraded when I flashed an older RUU.
Once you get the older hboot and firmware, you may have to unlock your bootloader again through HTC Dev, then S-Off. Once your S-Off unlocking your bootloader is much easier.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
If you want to run a GPE RUU.exe your phone MUST have CID compatible (BS_US0001) with GPE and MID: PN0712000
you can check that with this command:
Code:
fastboot oem readcid
fastboot oem readmid
if they doesn't match, you MUST be S-OFF to change them
If your device is currently a DEV edition, you should already have PN0712000 as MID so the only concern is that CID need to match GPE RUU
You should post your
Code:
fastboot getvar-all
and remove imei and sn so it will be easier to see what options you have.
swag1981 said:
The zip can only be used with S-Off where as the exe is designed to be used to return a phone to stock with S-On.
Just get into fastboot and run the exe, it should do the rest for you. It will wipe the entire phone, but as far as I'm concerned, a blank phone is better than an unusable one.
I'm not sure if the hboot makes a difference, but mine downgraded when I flashed an older RUU.
Once you get the older hboot and firmware, you may have to unlock your bootloader again through HTC Dev, then S-Off. Once your S-Off unlocking your bootloader is much easier.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I just tried run this .exe but I got this error http://imgur.com/rYvIdBd
I downloaded RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe but my current ROM is Android 4.3 version 3.22.1540.1. I suppose I got this error because I tried to install a oldest version in my device. Does it make any ****ing sense?
I'm downloading the .exe for 3.22.1540.1 and than try to install it.
Regards
alray said:
If you want to run a GPE RUU.exe your phone MUST have CID compatible (BS_US0001) with GPE and MID: PN0712000
you can check that with this command:
Code:
fastboot oem readcid
fastboot oem readmid
if they doesn't match, you MUST be S-OFF to change them
If your device is currently a DEV edition, you should already have PN0712000 as MID so the only concern is that CID need to match GPE RUU
You should post your
Code:
fastboot getvar-all
and remove imei and sn so it will be easier to see what options you have.
Click to expand...
Click to collapse
Yep, my device has MID as PN0712000 and CID BS_US001
I tried run RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe from HTC1GURU byt i got this error http://imgur.com/rYvIdBd
My current software version is 3.22.1540.1.
@alray and @swag1981
I followed this thread http://forum.xda-developers.com/showthread.php?p=46046898
If I have a hboot S-ON it has to be LOCKED or RE-LOCKED. It'll never work with hboot UNLOCK. So if your hboot is S-OFF it not matter.
Thank u mates. You were friggin' awesome.
Regards
Alright, I've been through thread after thread and plenty of pages found on google.
Some say to Lock the bootloader BEFORE using the RUU and some say to lock it AFTER or you'll brick the phone?
I've got a T-mobile Variant of the HTC one M7 It's rooted, SuperCID and obviously the bootloader is unlocked.... I think it's on 1.55, not exactly sure, I'm currently backing up all my data.
I've got the new 5.14.531.1 RUU straight from the HTC website.
Since it's a Tmobile rom, I'm guessing resetting the CID to T-MOB010 before installing would be a good idea?
And what of the bootloader? running the RUU should install the new Hboot correct? from there I would just need to relock it or am I not understanding this?
~Out of all my phones I've NEVER returned one to stock, so this is all kinda new to me.
Vonrottes said:
I've got the new 5.14.531.1 RUU straight from the HTC website.
Click to expand...
Click to collapse
SuperCID means you're S-Off, so no need to lock/relock bootloader, but where did you get that RUU from? link please, cause I don't think it's an RUU (how big is the file??)
nkk71 said:
SuperCID means you're S-Off, so no need to lock/relock bootloader, but where did you get that RUU from? link please, cause I don't think it's an RUU (how big is the file??)
Click to expand...
Click to collapse
Doesn't exactly answer the question... I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
Also the link, right from HTC
http://dl3.htc.com/application/RUU_M7UL_TMOUS_5.14.531.1_With Partial.exe
it's a whooping 1.49GB
Vonrottes said:
Doesn't exactly answer the question... I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
Also the link, right from HTC
http://dl3.htc.com/application/RUU_M7UL_TMOUS_5.14.531.1_With Partial.exe
it's a whooping 1.49GB
Click to expand...
Click to collapse
ah ok, 1.49GB sounds good for an RUU
and to answer your question differently, if you are S-Off, then you do not need to lock/relock bootloader; the RUU should work fine with unlocked bootloader
refer to "Not so FAQ #2": http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
and remember to stay S-Off
nkk71 said:
ah ok, 1.49GB sounds good for an RUU
and to answer your question differently, if you are S-Off, then you do not need to lock/relock bootloader; the RUU should work fine with unlocked bootloader
refer to "Not so FAQ #2": http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
and remember to stay S-Off
Click to expand...
Click to collapse
Jolly good, I didn't even see that Not so FAQ.
So basically I just run the RUU according to the instructions on the HTC page ( http://www.htc.com/us/support/news.aspx?p_id=630&p_name=htc-one-t-mobile ) and I should be good?
Vonrottes said:
Jolly good, I didn't even see that Not so FAQ.
So basically I just run the RUU according to the instructions on the HTC page ( http://www.htc.com/us/support/news.aspx?p_id=630&p_name=htc-one-t-mobile ) and I should be good?
Click to expand...
Click to collapse
hmm, i can't seem to be able open that web page, but if the file is a full RUU (I'm downloading it, but with my connection it's gonna take quite a while), then hook up the phone, and run the RUU and all should be good.
Remember an RUU will fully wipe your phone (including sdcard/internal storage), and if for whatever reason you want to change bootloader to the original LOCKED (not relocked),
you can use this tool: http://forum.xda-developers.com/showthread.php?t=2527194
(though I don't see any reason to do it )
as long as you stay S-Off, you can easily get it unlocked again anytime
out of curiosity, any particular reason you're doing this?
nkk71 said:
hmm, i can't seem to be able open that web page, but if the file is a full RUU (I'm downloading it, but with my connection it's gonna take quite a while), then hook up the phone, and run the RUU and all should be good.
Remember an RUU will fully wipe your phone (including sdcard/internal storage), and if for whatever reason you want to change bootloader to the original LOCKED (not relocked),
you can use this tool: http://forum.xda-developers.com/showthread.php?t=2527194
(though I don't see any reason to do it )
as long as you stay S-Off, you can easily get it unlocked again anytime
out of curiosity, any particular reason you're doing this?
Click to expand...
Click to collapse
I know, that's why I'm currently backing up everything important on Google Drive.
I was just looking at Scotty1223's threads with the ADB commands to remove tampered flag and reset locked.
and like I said in my second post
I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
So to go back stock with no need to ever unlock or root again,
I'll be fine LOCKING the bootloader and resetting the CID to T-MOB010 Before running the RUU?
Vonrottes said:
I know, that's why I'm currently backing up everything important on Google Drive.
I was just looking at Scotty1223's threads with the ADB commands to remove tampered flag and reset locked.
and like I said in my second post
I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
So to go back stock with no need to ever unlock or root again,
I'll be fine LOCKING the bootloader and resetting the CID to T-MOB010 Before running the RUU?
Click to expand...
Click to collapse
I understood the part about upgrading your phone, but seeing your signature, you're running a custom ROM and kernel, so i'm not clear what you mean by upgrading
Anyway, if you are going back to stock, here's what I personally would do:
1- stay S-OFF
2- change CID back to original
3- remove TAMPERED and set LOCKED (using scotty1223's commands, or the Guru Bootloader Reset tool) not because it's necessary, just aesthetically more stock
4- run the RUU
5- stay S-OFF
nkk71 said:
I understood the part about upgrading your phone, but seeing your signature, you're running a custom ROM and kernel, so i'm not clear what you mean by upgrading
Anyway, if you are going back to stock, here's what I personally would do:
1- stay S-OFF
2- change CID back to original
3- remove TAMPERED and set LOCKED (using scotty1223's commands, or the Guru Bootloader Reset tool) not because it's necessary, just aesthetically more stock
4- run the RUU
5- stay S-OFF
Click to expand...
Click to collapse
Upgrading as in:
http://www.t-mobile.com/phone-upgrade.html
To get an HTC One M8 I have turn in my Current M7... Which has to be stock...as far as the T-mobile store tech needs to know.... I guess?
Vonrottes said:
Upgrading as in:
http://www.t-mobile.com/phone-upgrade.html
To get an HTC One M8 I have turn in my Current M7... Which has to be stock...as far as the T-mobile store tech needs to know.... I guess?
Click to expand...
Click to collapse
gotcha :good:
that's a completely different kind of upgrade, i thought you meant software
Do they care about S-OFF?? because if you intend on going S-ON, then I would highly recommend a 1.xx ruu, nothing higher.
because going from S-Off to S-On on hboot 1.55+, has been known to trigger "tamper detected - rebooting" and TAMPERED is back in bootloader screen.
nkk71 said:
gotcha :good:
that's a completely different kind of upgrade, i thought you meant software
Do they care about S-OFF?? because if you intend on going S-ON, then I would highly recommend a 1.xx ruu, nothing higher.
because going from S-Off to S-On on hboot 1.55+, has been known to trigger "tamper detected - rebooting" and TAMPERED is back in bootloader screen.
Click to expand...
Click to collapse
Yeah, it's gonna need to be S-on when I take it into the store...
Pretty sure they check the bootloader for S-ON, ***TAMPERED*** and ***LOCKED***
Is it just the 1.55+ Hboot that throws the tampered when locked?
If so Can I flash the 1.54.401.5 Hboot from Firewater and proceed like that?
Can't do the 1.44, My PC is running 8.1 and I've not played with Linux since 2009
Vonrottes said:
Yeah, it's gonna need to be S-on when I take it into the store...
Pretty sure they check the bootloader for S-ON, ***TAMPERED*** and ***LOCKED***
Click to expand...
Click to collapse
In that case, I recommend you use a 1.xx RUU
(check my guide in my signature)
Vonrottes said:
Is it just the 1.55+ Hboot that throws the tampered when locked?
Click to expand...
Click to collapse
Unknown when/what exactly triggers the "tamper detected" or some people have been able to S-On and not get that, others have not, so I can't say if it will happen or not. but if you wanna play it safe, go for 1.xx ruu.
Vonrottes said:
If so Can I flash the 1.54.401.5 Hboot from Firewater and proceed like that?
Click to expand...
Click to collapse
brick alert: Definitely NOT, that is a custom HBOOT, if you actually manage to S-On it with an unsigned hboot, you'll have an paperweight on your hands!! stay away from that.
Hi everyone.
I need your help to figure it out about something
I've an HTC One with:
S-OFF
HBOOT: 1.56
CID: HTC__001
Firmware 4.06.1540.2
Bootloader: unlocked
I downloaded an old .exe RUU (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed) because I thought with S-Off I could install any kind of RUUs. I decided to download it because I already used it the last year and because I thought I could get the 1.44 HBOOT after installing it to be able to use Revone to make bootloader locked, tampered out, and S-ON again. When I try to install the RUU.exe, it says that my device is not compatible with that image.
Maybe I can't use it because I've the bootloader unlocked? I hope someone can help me to understand what's going on and what should I do. Thanks everyone
Greetings, Mr.Kiko
Mr.Kiko said:
Hi everyone.
I need your help to figure it out about something
I've an HTC One with:
S-OFF
HBOOT: 1.56
CID: HTC__001
Firmware 4.06.1540.2
Bootloader: unlocked
I downloaded an old .exe RUU (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed) because I thought with S-Off I could install any kind of RUUs. I decided to download it because I already used it the last year and because I thought I could get the 1.44 HBOOT after installing it to be able to use Revone to make bootloader locked, tampered out, and S-ON again. When I try to install the RUU.exe, it says that my device is not compatible with that image.
Maybe I can't use it because I've the bootloader unlocked? I hope someone can help me to understand what's going on and what should I do. Thanks everyone
Greetings, Mr.Kiko
Click to expand...
Click to collapse
Follow @nkk71 Superguide it's much simpler that way
http://forum.xda-developers.com/showthread.php?t=2541082
clsA said:
Follow @nkk71 Superguide it's much simpler that way
http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Thank you. I've done everything without problems
Mr.Kiko said:
Thank you. I've done everything without problems
Click to expand...
Click to collapse
good to here .. good luck