RELOCKED in bootloader.. - HTC Desire S

Hello all, I'd like to know if there's a way to edit/remove the "RELOCKED" I got in bootloader while locking my htcdev's unlocked Desire S. Can I go back to 0.98.0002 hboot and keep it S-ON without this RELOCKED alert? I have to send my device for warranty repair and I'm scared I'll have to pay the repair (vibration has gone)

@Sim0cYz
The only way I know personally would be to downgrade, two threads can be found in the general section.
Although regardless of what your bootloader says, HTC can still check on their systems and tell that you unlocked via HTCdev.

Are you sure the problem with the vibration isn't due to some custom ROM you're on?

If it has 7 vibrations on boot (I don't see anything listed in this thread) - it's most likely HW problem. On Nexus One it was overheating CPU, confirmed by running the phone in freezer (worked fine inside). I believe it to be the same sign.

I flashed many many different roms, stock RUU too, so I can say it's not a sotware problem. Now my Desire S is being repaired in warranty, let's hope I shouldn't pay for this.
No, it doesn't 7 vibration on boot, no vibration at all.

Related

[Q] HTC's "official" bootloader unlock process

Please please forgive the newb question, but once the bootloader is officially unlocked by HTC's method (basically entering a token you pull from your phone, and then flashing a .bin file they send you based on that token), is it reversible? I.E. is it possible to re-lock it back to factory status? I'm assuming not, but can't find any hard evidence one way or the other...
Apparently someone has said you can re-lock it but I've not used it. Better using Revolutionary IMO
Well you can do a "simple" re-lock just to ensure noone else can make changes to it with "fastboot oem lock" - but it's not the factory lock. The bootloader simply says "re-locked" instead of "unlocked", or compared to the factory "locked".
But I was thinking in terms of reverting it truly back to factory status. Again, I don't think it's possible (without HTC's intervention anyway), given the nature of how it was locked, but need someone smarter than me to confirm that suspicion.
So basically, using Super CID, you can run the RUU.exe from the bootloader only, and get your phone back to 100% stock, but it'll still be unlocked. So I'm guessing there is no way to reverse HTC's unlock process.
jntdroid said:
So basically, using Super CID, you can run the RUU.exe from the bootloader only, and get your phone back to 100% stock, but it'll still be unlocked. So I'm guessing there is no way to reverse HTC's unlock process.
Click to expand...
Click to collapse
I flashed the android revolution rom with my device unlocked through htc website, I cannot flash back to stock, I tried the RUU to bring me back to 1.27 and 1.29 and error'd on both of those. I am not sure how to get back to stock. I tried several times. I also cannot get my security to turn off in the bootloader after I unlocked through htc. Has anyone figured out how to do this? I tried the revoltionary.io tool and successfully used the tool only to reboot and see the S-ON in bootloader mode. CRAZY I suggest for anyone to turn their S-OFF using revolutionary.io before they ever attempt to unlock the bootloader through htc. What I am experiencing is error under the wifi switch I cannot seem to get wifi working with any of the roms, probably due to the kernel or not having s-off in bootloader. I tried different and stock kernels only to have the same problem.
Read this if you want more info: http://forum.xda-developers.com/showthread.php?t=1290395
Has ANYBODY tried the goldcard method to reflash to stock? Take the rom.zip from RUU and flash in bootloader
So ive gone back to stock htc orange ROM with the CID ORANG001 and i am now also S-On after being on ARHD, after probelms with the phone in case i need to send it back, so by the looks of what you are saying I am not actually back to factory status? So will HTC be able to tell in the case that i have to send it back fro repair or whatever? If so i also need to know how to re lock and get back to complete factory status!?
EDIT: im pretty sure bootloader was already available on the phone, and my firends incredible s, he is able to access bootloader without doing anything to his phone
Gold card doesn't work, otherwise we could've used it before S-OFF
gtcalder said:
So ive gone back to stock htc tmobile ROM with the CID ORANG001 and i am now also S-On after being on ARHD, after probelms with the phone in case i need to send it back, so by the looks of what you are saying I am not actually back to factory status? So will HTC be able to tell in the case that i have to send it back fro repair or whatever? If so i also need to know how to re lock and get back to complete factory status!?
EDIT: im pretty sure bootloader was already available on the phone, and my firends incredible s, he is able to access bootloader without doing anything to his phone
Click to expand...
Click to collapse
Where is this CID ORANG001 you are referring to? Do you have a link? And as far as I know you can unlock the bootloader but there is currently no true relock.
droiddv said:
Where is this CID ORANG001 you are referring to? Do you have a link? And as far as I know you can unlock the bootloader but there is currently no true relock.
Click to expand...
Click to collapse
Hi, list of CIDs for each ROM..
http://forum.xda-developers.com/showthread.php?t=1195475

[Q] CID

Hi ,
Wanting to get rid of 3 uk junk and flash to normal UK RUU
Do we need super CID?
My bootloader is unlocked , can't download the RUU from from the Dev section as all the slots are gone , or when it seems to work it errors out .
Has anyone got the latest UK RUU file they can share with me and can someone confirm if I need Super CID to run RUU to unbrand
Thanks in Advance
Just flash Modaco or the Virtuous roms through recovery, these are unbranded and really good.
You will need to flash a Recovery image first though.
Hi and thanks
Yes , I understand this but I want to just unbrand through RUU then re-lock my bootloader.
Do we need Super CID ?
Ok can someone remind me if I need S-Off to change the CID , playing around with ADB at the moment
If Im honest mate, no idea what you mean by CID...
But if you want a new rom, all that needs to be done is unlock bootloader, flash recovery, flash rom.
Thats all anyone has done in the dev threads, and worked fine for me (coming from a retail, unbranded unit).
You can 'lock' the bootloader again, BUT it never goes back to its true original state. This is as HTC designed their unlocking/locking process to be (and is stated in their terms when you go to their site to unlock).
Edit: OK, just read up on it. Possibly then! Depends how annoying 3 are I suppose... Probably best to ask one of the devs
Edit 2: CHeck the following, may be of help (though its for the One X)
http://forum.xda-developers.com/showthread.php?t=1594262
http://android.modaco.com/topic/353106-debrand-one-x/
Edit 3: If you're applying a flashable zip, does the CID limitiation on RUUs even come into play?
Hi thanks ,
Yea what I want to achieve is this .
My CID is HG3____001 this will need to be changed to a CID that is HTC UK specific usually HTC_____001
To find out your CID in ADB
Fastboot Getvar CID
To get to a retail version from a branded version , what usually needed to happen was this .
Unlock bootloader , change CID to 11111111 via ADB
Run the specific UK RUU.exe
Change your CID to the HTC_____001 which is the usual default for UK unbranded devices .
re-lock your bootloader and then you should receive OTA updates from HTC instead of your network supplier which can take months
I can't remember if S-off was needed to do this. I have just checked revolution site and One s is not listed , will play around tonight though and see
Thanks for the help so far
Hi, I know what CID is - coming from the Sensation.
I dont think its possible to change CID without S-OFF, you cant use advanced ADB functions with S-ON
Until revolutionary or someone else makes tool for S-OFF, we will just have to stick with HTCDev, Its not the best, but it allows to flash recovery and ROMs so its better than nothing.
Im pretty sure there will be some progress in the next few weeks, Once the phone is available worldwide
Ahh ok , thanks , yea this phone is set S- on , so S-off will be needed sooner or later
yeah, as development develops and more rights are needed from the phone, S-0FF will eventually be a MUST.
I wish it was available already, I hate the fact that HTC know i have tampered with my HBOOT and voided my warranty.
Luckily enough, if i have a problem, my provider fixes / repairs the phone, Not HTC, So i might just get off lightly
I think HTC will know if you have tampered with the phone period if they wish to look that far into it .
Unless you fry your processor where you have set it too high etc then shouldn't be a problem. If you have a hardware problem such as your screen fails , battery etc then should be fine .
As you say though , if you brought it through a retail unit then that is where it is returned so in some respects is a bit easier as they will use a third party repairer acting for HTC .
well with the sensation it was possible to return everything back to stock, Including the bootloader and S-ON..
There was no way it could be diagnosed as being tampered with, If you did it properly..
But with HTCDev. youve already submitted a code (which i assume contains serial number) so all they have to do is check whether that device matches anything on their database of tampered devices. Thats why i dislike it so much..
But i need root for most of my apps so there was no workaround for me...
I see on the One X forum S-off is under way . Can't wait to get this baby to true stock.
Just did another Google search for S-Off on the S but nothing as yet .

Desire S Bootloader Question

I have read various guides, and eventually taken the plunge to downgrade my bootloader.
htcDev Unlock
Goldcard
Install oldest RUU
S-OFF using revolutionary
Flash CWM recovery
Backup Stock 2.33 ROM with Sense
Install CM9
Feeling quite pleased with myself, even though you guys have really done all the hard work, I've just followed the steps!
What I can't find is this;
If I go back to the Stock ROM and updates are offered OTA, if I accept, will this, not only bring me back to 2.3.5 with Sense 3.0, but also change my bootloader back to 2.00.0002 Locked and S-ON ?
Unfortunately it will be *RELOCKED* and S-ON
Sent from my HTC Desire S
amidabuddha said:
Unfortunately it will be *RELOCKED* and S-ON
Click to expand...
Click to collapse
What he said. If you wanted to remain "locked" and not "relocked" - you should have avoided unlocking the bootloader, and should have used temp-root for misc_version.
Ok, what are the inplications of being 'RE-LOCKED'
Like CM9, but get the feeling development stalled, also certain apps won't work Nat West being one, though I suspect that is to do with their development.
Thinking about going back to Stock. If I do this via OTA, my bootloader will be upgraded back to 2.00.0002, 'RE-LOCKED' and S-ON, then wait for official OTA upgrade to ICS, which seems not to be happening as per HTC announcements. Even then I may have issues with apps that haven't been coded to deal with it.
If I am 'RE-LOCKED' can I not use htcDev again, or am I stuck with the Official bootloader etc and unable to load other ROMS, or can I just repeat the processes I have been through already?
I have also been reading about unlocking with an XTC Clip, where would I get this done, Is this a better solution? etc etc..
No issues with RELOCKED except that your warranty is gone.
If you have no warranty you can go for XTC Clip, since permanent S-OFF will give you more freedom in terms of modifications. Personally I consider flashing boot.img separately each time as annoying.
As per the unlock again, it should be possible, but I am not sure if this can be done by a fastboot command or the unlock token has to be flashed again.
Sent from my HTC Desire S
When I unlocked mine I remember reading somewhere that the token would need to be used again if the phone was re locked. So I kept it just in case

[Q] One S Hard Brick after RUU update (S-ON and Locked)

Hi guys, something pretty bad happened tonight to my Htc One S.
I had maximusHD installed, so of course S-OFF and bootloader Unlocked. However, I was having some problems and decided to revert back to stock. I re-locked the bootloader, changed the CID back to the stock one and flashed the RUU. Everything went perfectly fine. Sort of. I noticed that the RUU I flashed was some kind of pre-release one (the whole interface was watermarked). I got that from androidruu.com
So I downloaded a newer RUU (yes, both of them were for the appropriate country) and flashed that one.
It went on normally for a while and then nothing. Black screen, no response, no charging light. It shows as QHSUSB_dload under Windows and as Qualcomm Gobi Wireless Modem under Linux.
Now, are RUUs so damn risky? Luckily the phone was Relocked and S-ON, so warranty should cover this. I read all kinds of threads about this problem but none of the proposed solutions worked... did I miss something or do really need to send it for repairs?
Thanks!
Camazza said:
Hi guys, something pretty bad happened tonight to my Htc One S.
I had maximusHD installed, so of course S-OFF and bootloader Unlocked. However, I was having some problems and decided to revert back to stock. I re-locked the bootloader, changed the CID back to the stock one and flashed the RUU. Everything went perfectly fine. Sort of. I noticed that the RUU I flashed was some kind of pre-release one (the whole interface was watermarked). I got that from androidruu.com
So I downloaded a newer RUU (yes, both of them were for the appropriate country) and flashed that one.
It went on normally for a while and then nothing. Black screen, no response, no charging light. It shows as QHSUSB_dload under Windows and as Qualcomm Gobi Wireless Modem under Linux.
Now, are RUUs so damn risky? Luckily the phone was Relocked and S-ON, so warranty should cover this. I read all kinds of threads about this problem but none of the proposed solutions worked... did I miss something or do really need to send it for repairs?
Thanks!
Click to expand...
Click to collapse
Hi,
I was stuck with the same issue. What threads have you tried I heard the only way is via JTAG but just wanna know if there is any other way
It seems like I could do something with the phone using QPST (which I have). What I'm missing are the device and chipset-specific files that need to be recovered from a working phone. There has been some talk about QPST and its usefulness here on xda, but I think they only made i work for some Samsung devices with Qualcomm chipsets.
Is there someone who is willing to help me, maybe by dumping the contents of his phone using QPST and posting them? I only need the SPL partition, which is the HBOOT i need to recover the phone.
Please, tell me I don't have to send it to HTC...
Camazza said:
It seems like I could do something with the phone using QPST (which I have). What I'm missing are the device and chipset-specific files that need to be recovered from a working phone. There has been some talk about QPST and its usefulness here on xda, but I think they only made i work for some Samsung devices with Qualcomm chipsets.
Is there someone who is willing to help me, maybe by dumping the contents of his phone using QPST and posting them? I only need the SPL partition, which is the HBOOT i need to recover the phone.
Please, tell me I don't have to send it to HTC...
Click to expand...
Click to collapse
QPST is just a software right... no hardware is required for it ha!!!!... I thought jtag is the only way to access a bircked phone.
our pc is able to detect QHSUSB_dload and via that itself will we be able to flash a mobile if we have a system dump??

Need to Unroot Verizon HTC One M8 But Something's wrong

Alright so I rooted my phone around February and installed CM12.1 but because I want to get a replacement from HTC due to my friend dropping my phone and cracking the screen, so I need to unroot the device so I can use the warranty. Looking around there are some methods but they seem to not work correctly for my phone. And because I am a total dingus, I accidentally relocked the bootloader and now I can't reflash a custom recovery. I have tried installing RUUs from different threads on this site via hboot but they seem to not work. I don't know if anyone can help me if you can I really would appreciate it and would like to get this fixed as soon as possible. The CID is VZW__001 and the main OS on the bootloader says 3.28.605.4 but the box says 1.55.605.2 so I don't know which one is the correct one so if someone could clear something up and give me a link to a correct RUU for my phone that would be amazing. Thanks in advance
Have you tried re unlocking the boot loader?
Save the Manuals!!!

Categories

Resources