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.
Related
Apologies if this is a noob question or has been answered before, but I just ran the RUU and I retained S-off and my bootloader was still unlocked afterwards. Is this suppose to happen?
I'll try and make this short: I had HBOOT 1.44 (S-off with revone and HTC Dev unlocked). I saw OMJ's thread with newer firmwares and a 4.06.651.4 RUU. I flashed the firmware, verified everything worked still, and ran the RUU (for peace of mind). RUU was successful but the fastboot screen still shows the pink ***UNLOCKED*** text and S-OFF message. Current HBOOT is 1.56.
MrLinky said:
Apologies if this is a noob question or has been answered before, but I just ran the RUU and I retained S-off and my bootloader was still unlocked afterwards. Is this suppose to happen?
I'll try and make this short: I had HBOOT 1.44 (S-off with revone and HTC Dev unlocked). I saw OMJ's thread with newer firmwares and a 4.06.651.4 RUU. I flashed the firmware, verified everything worked still, and ran the RUU (for peace of mind). RUU was successful but the fastboot screen still shows the pink ***UNLOCKED*** text and S-OFF message. Current HBOOT is 1.56.
Click to expand...
Click to collapse
Yes
hmm, i might have to try this later on...i was concerned it might relock or i might have to lock but i guess not?(ive been trying to search and find out but i think you answered my question lol)
Once S-OFF, always S-OFF, unless you write the secureflag to be S-ON again.
pinky059 said:
Once S-OFF, always S-OFF, unless you write the secureflag to be S-ON again.
Click to expand...
Click to collapse
Good to know, thanks. I was under the impression that an RUU totally resets a device but I guess not. It saved me having to s-off/unlock/root again :victory:
Hey I learned something new lol
mxx20 said:
Hey I learned something new lol
Click to expand...
Click to collapse
So did I, regarding RUUs that is.
v1ral said:
So did I, regarding RUUs that is.
Click to expand...
Click to collapse
Me too..lol, heyit's a learning game!
Yes you have to do a FASTBOOT RELOCK COMMAND to make the phone secure. You can also use root linux to disguise the bootloader/Hboot to make it appear S-ON if you choose. http://forum.xda-developers.com/showthread.php?t=2565201
Hi,
I was going to update the rom on my HTC One and add the most recent luna kernel but when i download it i didn't look at where the thread was coming from and i think i downloaded to another device. Now, im still able to flash any rom but the SIM Card isn't detected. I've tried a nadroid backup but when i flash the rom i had i get the same issue, no SIM card.
Terramoto said:
Hi,
I was going to update the rom on my HTC One and add the most recent luna kernel but when i download it i didn't look at where the thread was coming from and i think i downloaded to another device. Now, im still able to flash any rom but the SIM Card isn't detected. I've tried a nadroid backup but when i flash the rom i had i get the same issue, no SIM card.
Click to expand...
Click to collapse
Try flashing latest radio and maybe firmware, this will generally fix. Worst case you would need to backup and ruu.
Sent from my HTC One on some Awesome Rom..
Hey,
I was able to S-ON my device but now i don't know what to do. My HBoot is 1.44 could someone point me in the right direction? Im currently downloading RUU 3.04.651.2 which is the one i get from getvar version-main.
Terramoto said:
Hey,
I was able to S-ON my device but now i don't know what to do. My HBoot is 1.44 could someone point me in the right direction? Im currently downloading RUU 3.04.651.2 which is the one i get from getvar version-main.
Click to expand...
Click to collapse
... buddy why did you go for s-on is out of my understanding. people yearn to get s-off and you did the opposite. its ok. you can s-off later. Now relock your bootloader and run RUU. your phone will be up and running. then again go for s-off after unlocking bootloader and flashing custom recovery and root ...
Devilish_Angel said:
... buddy why did you go for s-on is out of my understanding. people yearn to get s-off and you did the opposite. its ok. you can s-off later. Now relock your bootloader and run RUU. your phone will be up and running. then again go for s-off after unlocking bootloader and flashing custom recovery and root ...
Click to expand...
Click to collapse
Its all good now , I did S-Off because i read on flashing RUU tutorials that i needed to be S-Off before i run RUU
Terramoto said:
Its all good now , I did S-Off because i read on flashing RUU tutorials that i needed to be S-Off before i run RUU
Click to expand...
Click to collapse
.. you got it all wrong. its not necessary to be s-on to run RUU. RUU will do good on both s-on and s-off. its the bootloader which matters and that too when s-on. In simple words, if device is s-on you HAVE to relock bootloader to RUU and if device is s-off, no need to bother about bootloader status ...
Devilish_Angel said:
.. you got it all wrong. its not necessary to be s-on to run RUU. RUU will do good on both s-on and s-off. its the bootloader which matters and that too when s-on. In simple words, if device is s-on you HAVE to relock bootloader to RUU and if device is s-off, no need to bother about bootloader status ...
Click to expand...
Click to collapse
Yeah! I just learned something today, thanks!!
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.
I have a HTC One on the EE network in the UK and I am still currently on Android 4.3 and Sense 5.5, they haven't bothered to release Android 4.4 yet and I have no hope that they will release Sense 6.
So, I would like to know how to go about changing my EE branded phone into an Unlocked International Version so that I can receive OTA updates direct from HTC.
Current CID: ORANG001
Current Hboot: 1.55
Current Software Number: 3.63.61.1
Radio: 4A.21.3263.04
Locked Bootloader with S-On
I would very much appreciate any help you can give.
Thank-You
rh92 said:
I have a HTC One on the EE network in the UK and I am still currently on Android 4.3 and Sense 5.5, they haven't bothered to release Android 4.4 yet and I have no hope that they will release Sense 6.
So, I would like to know how to go about changing my EE branded phone into an Unlocked International Version so that I can receive OTA updates direct from HTC.
Current CID: ORANG001
Current Hboot: 1.55
Current Software Number: 3.63.61.1
Radio: 4A.21.3263.04
Locked Bootloader with S-On
I would very much appreciate any help you can give.
Thank-You
Click to expand...
Click to collapse
first of all you need to unlock your bootloader and s-off your phone, debrand is not possible with s=on
the you would need to change your cid to something like HTC__001 or developer edition cid, one fastboot command required to do this.
and then run the correct RUU for those cid's and your done.
its quite easy to do, the hardest part is getting s-off, however you may be ok on 1.55 hboot, try rumrunner, read the instructions and download the required file here: http://rumrunner.us/
Seanie280672 said:
first of all you need to unlock your bootloader and s-off your phone, debrand is not possible with s=on
the you would need to change your cid to something like HTC__001 or developer edition cid, one fastboot command required to do this.
and then run the correct RUU for those cid's and your done.
its quite easy to do, the hardest part is getting s-off, however you may be ok on 1.55 hboot, try rumrunner, read the instructions and download the required file here: http://rumrunner.us/
Click to expand...
Click to collapse
Do I need custom recovery? If so which is best.
And do I need to have a custom ROM installed to gain s-off or can s-off be achieved on my current EE branded ROM?
Thanks
rh92 said:
Do I need custom recovery? If so which is best.
And do I need to have a custom ROM installed to gain s-off or can s-off be achieved on my current EE branded ROM?
Thanks
Click to expand...
Click to collapse
nope its not required for either, you should be able to s-off on stock rom, if you get an error or for some reason it fails, then you MAY have to flash a custom recovery and custom rom / kernel.
The RUU's will put you back to fully stock anyway in the end.
Seanie280672 said:
nope its not required for either, you should be able to s-off on stock rom, if you get an error or for some reason it fails, then you MAY have to flash a custom recovery and custom rom / kernel.
The RUU's will put you back to fully stock anyway in the end.
Click to expand...
Click to collapse
If the s-off does cause an error or it fails, can this cause my device to get bricked?
And by fully stock do you mean that the RUU turns s-on and locks my boot loader? (just in case I need to send my phone in for repair).
Thanks
rh92 said:
If the s-off does cause an error or it fails, can this cause my device to get bricked?
And by fully stock do you mean that the RUU turns s-on and locks my boot loader? (just in case I need to send my phone in for repair).
Thanks
Click to expand...
Click to collapse
no your phone wont brick
and no the ruu wont turn your phone s-on, you will need to lock your bootloader before running the RUU, but that's one simple command too, but only after s-off.
all you need right now is to make sure you have the drivers installed and that your device is detected in windows both when booted into a rom and on the bootloader screen.
Seanie280672 said:
no your phone wont brick
and no the ruu wont turn your phone s-on, you will need to lock your bootloader before running the RUU, but that's one simple command too, but only after s-off.
all you need right now is to make sure you have the drivers installed and that your device is detected in windows both when booted into a rom and on the bootloader screen.
Click to expand...
Click to collapse
After installing the RUU how would I get s-on?
Thanks
rh92 said:
After installing the RUU how would I get s-on?
Thanks
Click to expand...
Click to collapse
don't s-on, never s-on simple as that.
Seanie280672 said:
don't s-on, never s-on simple as that.
Click to expand...
Click to collapse
Ok, I was just asking in case I needed to send my phone in for repair in the future.
rh92 said:
Ok, I was just asking in case I needed to send my phone in for repair in the future.
Click to expand...
Click to collapse
not really something they will check to be honest, but if you s-on and you've played about with your phone down the line, like flashed a modified firmware or hboot, you will get an instant brick, if your hboot version is too high you will get the tampered flag back, or if you make a mistake along the way and the fix requires s-off, it will be very difficult to get again.
Seanie280672 said:
not really something they will check to be honest, but if you s-on and you've played about with your phone down the line, like flashed a modified firmware or hboot, you will get an instant brick, if your hboot version is too high you will get the tampered flag back, or if you make a mistake along the way and the fix requires s-off, it will be very difficult to get again.
Click to expand...
Click to collapse
So, is the following step by step list correct.
1. Unlock boot loader
2. Get s-off via rumrunner
3. Change CID
4. Lock boot loader
5. Run RUU
And, I am currently on 4.3 and Sense 5.5, so can I go straight to the sense 6 and Android 4.4 RUU, or do I have to install the sense 5.5 and Android 4.4 RUU first.
Thanks
rh92 said:
So, is the following step by step list correct.
1. Unlock boot loader
2. Get s-off via rumrunner
3. Change CID
4. Lock boot loader
5. Run RUU
And, I am currently on 4.3 and Sense 5.5, so can I go straight to the sense 6 and Android 4.4 RUU, or do I have to install the sense 5.5 and Android 4.4 RUU first.
Thanks
Click to expand...
Click to collapse
yup that's the correct order, and you will have to use this RUU as its the only full RUU available, everything else is just OTA's
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Seanie280672 said:
yup that's the correct order, and you will have to use this RUU as its the only full RUU available, everything else is just OTA's
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Click to expand...
Click to collapse
And after installing this RUU I can just download Sense 6 via OTA.
rh92 said:
And after installing this RUU I can just download Sense 6 via OTA.
Click to expand...
Click to collapse
yes, just accept the ota's one at a time.
Seanie280672 said:
yes, just accept the ota's one at a time.
Click to expand...
Click to collapse
Thanks for your help
I have an PN07200, how can I get sense 6, which will be the best RUU and CID?.... Thanks!
Enviado desde mi HTC One X+ mediante Tapatalk
is it possible to re-apply the branding?
i.e.
RUU
change cid
OTA with brand change
gwaitsi said:
is it possible to re-apply the branding?
i.e.
RUU
change cid
OTA with brand change
Click to expand...
Click to collapse
yup, change your cid to its original one, and find your service providers RUU and flash it.
I have an ATT M7. I am on T-Mobile. The phone is now unlocked. It is still running Android 4.3.
ATT software update doesn't find any updates - presumably because I need an ATT sim in there.
So how can I upgrade this to 4.4 and later 5.0?
Thanks!
808phone said:
I have an ATT M7. I am on T-Mobile. The phone is now unlocked. It is still running Android 4.3.
ATT software update doesn't find any updates - presumably because I need an ATT sim in there.
So how can I upgrade this to 4.4 and later 5.0?
Thanks!
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number
808phone said:
I have an ATT M7. I am on T-Mobile. The phone is now unlocked. It is still running Android 4.3.
ATT software update doesn't find any updates - presumably because I need an ATT sim in there.
So how can I upgrade this to 4.4 and later 5.0?
Thanks!
Click to expand...
Click to collapse
convert the phone to Developers Edition
http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
http://forum.xda-developers.com/htc-one/general/stock-rom-reset-developer-edition-t2915170
Thanks @alray
So I did more reading and yes developer edition or change CID and MID to T-Mobile
All require S-OFF.
So I need to unlock boot loader, install TWRP, S-OFF. etc?
This is the blue Best Buy version ATT - but ATT just unlocked it.
M7_UL PVT SHIP S-ON RH
HBOOT 1.55
Radio-4T.20.3218.13
808phone said:
So I did more reading and yes developer edition or change CID and MID to T-Mobile
All require S-OFF.
So I need to unlock boot loader, install TWRP, S-OFF. etc?
This is the blue Best Buy version ATT - but ATT just unlocked it.
M7_UL PVT SHIP S-ON RH
HBOOT 1.55
Radio-4T.20.3218.13
Click to expand...
Click to collapse
thats why I asked for your fastboot getvar all, unlock your bootloader and use rumrunner to s-off, do not take any updates until you get s-off as it gets harder the higher HBOOT you have.
Seanie280672 said:
thats why I asked for your fastboot getvar all, unlock your bootloader and use rumrunner to s-off, do not take any updates until you get s-off as it gets harder the higher HBOOT you have.
Click to expand...
Click to collapse
S-OFF now by using sunshine. I do have ADB and Fastboot working from my previous use with HTC One S.
808phone said:
OK, I believe I am S-OFF, just used sunshine.
Click to expand...
Click to collapse
well from there you can either follow clsA link and change to developer edition, which will require changing cid, mid and flash the RUU, dev edition gets the quickest updates, although its very touch and go at the moment as to whether the M7 is going to get anymore updates, or you can do the same with the latest T-mo RUU which is here: http://www.htc.com/us/support/htc-one-t-mobile/news/ that will also require you to change your cid and mid, after doing that follow the manual instructions on the HTC site, download link for the RUU is at the bottom.
Thanks!
Seanie280672 said:
well from there you can either follow clsA link and change to developer edition, which will require changing cid, mid and flash the RUU, dev edition gets the quickest updates, although its very touch and go at the moment as to whether the M7 is going to get anymore updates, or you can do the same with the latest T-mo RUU which is here: http://www.htc.com/us/support/htc-one-t-mobile/news/ that will also require you to change your cid and mid, after doing that follow the manual instructions on the HTC site, download link for the RUU is at the bottom.
Click to expand...
Click to collapse
808phone said:
Thanks!
Click to expand...
Click to collapse
at&t phones already have the required MID to flash the dev edition ruu (pn0712000) Only need to change the cid
alray said:
at&t phones already have the required MID to flash the dev edition ruu (pn0712000) Only need to change the cid
Click to expand...
Click to collapse
Darn it. Read this too late. OK, I changed CID to T-MOB010 and MID to PN0713000.
At this point, do I just run an RUU at some point? Hope it works.
808phone said:
Darn it. Read this too late. OK, I changed CID to T-MOB010 and MID to PN0713000.
At this point, do I just run an RUU at some point? Hope it works.
Click to expand...
Click to collapse
Yes this one >> http://www.htc.com/us/support/htc-one-t-mobile/news/
clsA said:
Yes this one >> http://www.htc.com/us/support/htc-one-t-mobile/news/
Click to expand...
Click to collapse
I used Sunshine to get S-OFF. Everywhere I read, it says I need to have the boot loader locked to apply the RUU. However, while contacting the sunshine authors, they told me that despite what I have read, I don't have to relock. Is this true?
808phone said:
I used Sunshine to get S-OFF. Everywhere I read, it says I need to have the boot loader locked to apply the RUU. However, while contacting the sunshine authors, they told me that despite what I have read, I don't have to relock. Is this true?
Click to expand...
Click to collapse
no you dont need to lock as your s-off, unlocked is fine.
locked / relocked for flashing firmware or RUU's is only required for s-on users and limited to 1 step forward or current only.
So now the ruu times out on sending.......
So I extracted the rom.zip. If I flash it from twrp since it has a recovery image in it, will it overwrite twrp?
I'm assuming yes and then I would have to fast boot twrp back again.
Is this correct? Thanks
Gave up and installed Maximus HD. Works fine. Just wanted to be on 5.0 to test things.
808phone said:
Gave up and installed Maximus HD. Works fine. Just wanted to be on 5.0 to test things.
Click to expand...
Click to collapse
Anyone know what the first part of this means? (unaligned ruu)
Where would I get this????
> Use an unaligned ruu or a matching hboot ruu