Hello!
In the last week or so I've noticed my touchscreen doing weird things like pressing where it wants and annoying me with that. So, as this didn't stop with change of ROM, I asked around and got a verdict of a broken digitizer.
Okay, no problem. I started to Google and found out that replacing it is very expensive [ atleast in Latvia ] so I naturally thought of warranty service.
But here comes the problem: As I am on XDA, I am a ROM flasher [ addicted to it, kind of ] and I know that voids my warranty. I called an independent service and they told me: even if I revert to everything stock, they will still be able to see that I have flashed my ROM and lose mywarranty anyway.
I have SuperCID, S-OFF, ICS ARHD 6.6.5. - the max I could have.
Is this true or is there a method to return to stock everything?
I found this thread, where there are Pyramid STOCK ROM's. They have different firmwares and radios, I guess I would have to choose the first one as it is the oldest.
I also read the [Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on, will it be enough to get me through the warranty process ow will it say ***Re locked***?
not true. if you return everything to stock they won't know and you can claim your warranty.
follow this "For Warranty Purposes/Returns:Follow Step 4 below for removing Clockwork and Root
FOLLOW STEP 5 TO CHANGE BACK TO S-ON - CONFIRMED TO BE WORKING- USE WITH CAUTION"
HERE:http://forum.xda-developers.com/showthread.php?t=1192300
I've read through this method, after rebranding, will the bootloader say ***Re locked*** because I've read in the forums that this could happen and still void my warranty.
Tomekks said:
I've read through this method, after rebranding, will the bootloader say ***Re locked*** because I've read in the forums that this could happen and still void my warranty.
Click to expand...
Click to collapse
yup as long as it says ***Re locked*** you have no warranty
Is there any way to avoid it saying that or is it inevitable?
Tomekks said:
Is there any way to avoid it saying that or is it inevitable?
Click to expand...
Click to collapse
Yes. If you are currently S Off then just refer point 3 of this guide to RUUs: www.tinyurl.com/RUUGuide.
If you are already S On, then you need to S Off again, to make sure your bootloader doesn't say *Relocked*
If you have any questions, come to the IRC, link in signature pic.
S-ON RL
Hey!
I'm back with the results.
I ran into some problems the first time I got going with it but a little searching answered my questions.
Basically what I did:
1) Flash 1.17.0008 firmware Link
2) Installed [any] GB ROM.
3) Installed RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed Link
4) S-ON'ed Link
5) Changed CID to HTC__001 Link
Now the Bootloader screen says:
PYRAMID PVT SHIP S-ON RL
HBOOT-1.17.0008
eMMC-boot
May 13 2011.21:04:57
Is this what it should say or can the warranty service tell that I've messed around with my phone?
Tomekks said:
Hey!
I'm back with the results.
I ran into some problems the first time I got going with it but a little searching answered my questions.
Basically what I did:
1) Flash 1.17.0008 firmware Link
2) Installed [any] GB ROM.
3) Installed RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed Link
4) S-ON'ed Link
5) Changed CID to HTC__001 Link
Now the Bootloader screen says:
PYRAMID PVT SHIP S-ON RL
HBOOT-1.17.0008
eMMC-boot
May 13 2011.21:04:57
Is this what it should say or can the warranty service tell that I've messed around with my phone?
Click to expand...
Click to collapse
That seems good. Should be fine, unless Hboot says Relocked.
How to check that?
Tomekks said:
How to check that?
Click to expand...
Click to collapse
Go to the bootloader screen.
Power off. Remove, then re-insert battery.
Hold volume down + power button.
Ok, ne Relocked message, I'm in the clear.
But I also noticed that my problem with the digitizer has disappeard [ caugh, caugh ]. Could this happen?
Tomekks said:
Ok, ne Relocked message, I'm in the clear.
But I also noticed that my problem with the digitizer has disappeard [ caugh, caugh ]. Could this happen?
Click to expand...
Click to collapse
Yup! You can try going back to custom ROMs. Maybe you may not face any problems now.
So, a little update.
Warranty took my phone.
As they say: We reinstalled the software [ legal ICS, yay! ] and recalibrated the touchscreen, put it through testing and gave it back to me.
Everything sounds legit and I was excited getting my phone back.
After 5 minutes of use, I experience the same problems I had before the warranty service.
So, I'll be giving the phone back to warranty.
Another question: How to make a nandroid backup of an unrooted phone?
Related
So I am as excited as everyone else about s-off. Been waiting for awhile, but in the haste of everyone rooting their phone, I haven't been able to find a thread about restoring s-on in case of warranty work. Have I over looked something?
lots of views but no comments. This is from the IRC if interested
<splayer7> sorry if this has been asked, but what about resuming s-on for warranty work?
<hyuh> splayer7: no, not available
splayer7 said:
lots of views but no comments. This is from the IRC if interested
<splayer7> sorry if this has been asked, but what about resuming s-on for warranty work?
<hyuh> splayer7: no, not available
Click to expand...
Click to collapse
Exactly what has been said. There is no unrooting or S-On restoring at this time. I would just wait if you haven't already. HTC Released their source codes today. Its only a matter of time before an easier root is available with unroot, and S-on.
Was told that we could s-on by running the RUU. Here's a link to some I've found but haven't tested any of this. http://droidangel.blogspot.com/2011/06/htc-sensation-ruushipped-roms-packaged.html
kevinliu2336 said:
Was told that we could s-on by running the RUU. Here's a link to some I've found but haven't tested any of this. http://droidangel.blogspot.com/2011/06/htc-sensation-ruushipped-roms-packaged.html
Click to expand...
Click to collapse
do we have any confirmation on this working correctly
Tried it, resets your ROM but doesn't reset s-off
Guys.. There is about a 25% chance at best that HTC will actually check the boot loader status before providing warranty service. Even if you are unlucky and they do, if you make enough noise they might make an exception and let you off the hook. I think that as long as the issue that you are trying to resolve isn't a direct result of s-off or root, it should be fine.
splayer7 said:
So I am as excited as everyone else about s-off. Been waiting for awhile, but in the haste of everyone rooting their phone, I haven't been able to find a thread about restoring s-on in case of warranty work. Have I over looked something?
Click to expand...
Click to collapse
Flash an official RUU, and the device will be S-ON! TESTED!
lge73 said:
Flash an official RUU, and the device will be S-ON! TESTED!
Click to expand...
Click to collapse
Are you sure man? Somebody else above tested and found the opposite..
If the ruu is left untampered with, the boot image will be replaced with a stock one. Boot image is where your s-off lives. So in theory it should without a doubt work. You just have to make sure the boot image is in the ruu
smoochiezz24 said:
If the ruu is left untampered with, the boot image will be replaced with a stock one. Boot image is where your s-off lives. So in theory it should without a doubt work. You just have to make sure the boot image is in the ruu
Click to expand...
Click to collapse
I used the rom.zip file included in an untouched RUU, and I checked it includes HBOOT, also saw version change when I went into HBOOT.
It does NOT reset S-OFF back to S-ON.
I dont know if when you flash it reads S-OFF so keeps it, for users who genuinely had S-OFF?
I have personally tested this, and can confirm that using HTC's stock RUU does not return the phone to S-ON. However, it did remove the top area that says revolutionary, so now it appears as though I have a factory S-OFF device
Sent from my HTC Sensation 4G using XDA App
bummer.. I really hope there is a way to reverse s-off, just in case. but then again, I do have insurance so I guess I could say it was 'stolen' if I really need to get it replaced
prank1 said:
For those worrying about warranty issues..
You can try flashing the correct RUU for your phone.
IF that doesn't get rid of -revolutionary- s-off, then you can flash the ENG HBOOT (which gets rid of -revolutionary- but gives you ENG S-OFF) then you can flash the correct RUU for your region (which will definitely get rid of ENG S-OFF, and make you official stock HBOOT S-ON)
Click to expand...
Click to collapse
Try flashing ENG HBOOT, then the RUU afterwards.
I am going to try to get my phone back to S-ON now, just to test everything
EDIT
Hmm, very odd indeed, after flashing the RUU I have 'stock' Radio S-OFF (no -Revolutionary-) , I tried fastboot oem write secuflag 1 and fastboot oem writecid HTC__001 but I am still Radio S-OFF.
Just so people know, flashing full RUUs, even HBOOTs do NOT get rid of Radio S-OFF. Thats why it is favored by people, it can only be turned S-ON specifically by tools which may be released for the Sensation in the near future. I thought these tools only sent the commands that I tried to change the Radio security status. It would appear not.
However
There is no need to worry, Radio S-OFF probably won't void your warranty (if you sent it to a HTC repair center), as long as you have the correct CID and ROM installed you should be fine.
If I remember correctly, with the past Android phones, some people randomly got S-OFF (like sensation users did) out of the box. The HTC repair center didn't care. They don't like custom ROMs, custom HBOOTs, rooted ROMs, etc
Hello,
This morning I was in the market ( My Apps) and i chose Update all option. Loads of apps started to download, and after few minutes my phone froze. So i removed the battery and since then I', stuck in the bootloader menu:
AlphaRev
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.14_M
eMMC-boot
Mar 10 2011, 14:58:38
I can't do factory reset or access recovery. At some point I have successfully ran RUU, problem is I'm on UK O2 but being complete idiot I installed 3's ROM. Even the 3's ROM don't boot up. I can't run RUU anymore, because every time RUU is trying to reboot into boot loader it get stuck.
So,
I got phone from O2 that has a 3 logo (its stuck on it),
I have S-OFF phone so it probably voided the warranty.
Can anyone think of any solution please?
Thanks in advance for your help guys.
If you need more info please let me know.
Marcin
There are at least 5 similar topics, one is mine (same thing happened to me). Use search.
Does adb works yor you ?
yeap I have also created a topic on this.
I had to send mine back to HTC to fix.
What I would like to know is, if you send it back to HTC, would they notice the s-off and charge you money?
What ROMs were you all on? I got a similar problem on stock ROM after XTC Clip S-OFF, but a battery pull fixed it. I guess this only happens with S-OFF stock ROMs, so switch to avoid this.
No, adb doesn't see my phone....
mpolak83 said:
No, adb doesn't see my phone....
Click to expand...
Click to collapse
Remember with adb you need to be in Fastboot not Hboot! Very important. Cab you get into Fastboot?
InfernalByte said:
Remember with adb you need to be in Fastboot not Hboot! Very important. Cab you get into Fastboot?
Click to expand...
Click to collapse
When I run Adb devices it doesn't list my phone...so it doesn't work i suppose....
If I send my phone to HTC for repair will they accept it or will charge me because of S-OFF??
I just need my phone to be in the state so I can send it to HTC...I need to at least get rid off 3 logo and S-OFF...
mpolak83 said:
I just need my phone to be in the state so I can send it to HTC...I need to at least get rid off 3 logo and S-OFF...
Click to expand...
Click to collapse
Try flashing the eng hboot by PB88IMG method, and then try and run the correct RUU. That's my best idea.
InfernalByte said:
Try flashing the eng hboot by PB88IMG method, and then try and run the correct RUU. That's my best idea.
Click to expand...
Click to collapse
I have tried that, but I got the error that I can't roll back to older version of hboot.
I have just booked my phone for repair.. I'm gonna act stupid. I'll tell them that my friend installed something on my phone etc. Probably won't work... I will let you know what they said.
HTC gave me some terms and conditions to read and one of the says:
2.3 NonWarranty chargeable Repair Service
a) Repair of a Device that is
In-Warranty but which needs to be repaired including the following or similar
reasons shall be classified as a NonWarranty chargeable Repair Service:
1) Accidental damage. Accidental damage to the Device, such as dropping it
on the ground or in water. 2) Broken Liquid Crystal Display (hereinafter
known as “LCD”). 3) Damaged Sync or Charger Connector. 4) Damage
caused by liquid entering the Device, or other misuse due to the failure of the
Customer to follow the instructions properly. 5) Failure of the Customer to
upgrade the software according to the procedures outlined under the
warranty terms card of the Device. 6) Downloading illegal software onto the
Device. 7) Where the fault is caused by downloading illegal software onto the Device
or other accidental damage, the Customer shall be required to pay for spare
parts, labour, diagnosis and software refurbishment along with shipping and
handling charges.
Is S-OFF classified as illegal software?
Everything except RUU is illegal software...
Bubaaak said:
Everything except RUU is illegal software...
Click to expand...
Click to collapse
So I'm busted?
It's 50:50
Sent from my HTC Desire S using Tapatalk
Bubaaak said:
Everything except RUU is illegal software...
Click to expand...
Click to collapse
Wrong.
Its not illegal but you have probably invalidated your warranty. The thing is HTC have to bother to check your phone for custom software and a lot of the time they do.
Quick update.
I have sent my phone to HTC for repair under warranty yesterday. I have checked the status today, and it says "We are repairing your phone" So it looks like HTC don't check if the phone was rooted or have S-OFF
I've done the same i tried to flash a ruu image that was the wrong one i followed a thread on how to get s-on again just so i knew i could. I got s-on but now my phone is stuck on bootloader and is not recognised by the pc Please let me know how you get on and if you get charged as i will be doing the same i think.
InfernalByte said:
Wrong.
Its not illegal but you have probably invalidated your warranty. The thing is HTC have to bother to check your phone for custom software and a lot of the time they do.
Click to expand...
Click to collapse
Aren't custom Sense ROMs illegal ?
Coz Sense is HTC Proprietary framework.
goatimus said:
I've done the same i tried to flash a ruu image that was the wrong one i followed a thread on how to get s-on again just so i knew i could. I got s-on but now my phone is stuck on bootloader and is not recognised by the pc Please let me know how you get on and if you get charged as i will be doing the same i think.
Click to expand...
Click to collapse
You have to go to fastboot
Sent from my HTC Desire S using Tapatalk
Ok, I did something really stupid although I knew that it might have consequences. I s-offed via Revolutionary and flashed a new rom. Then I noticed that my phone, that I just got back today from repair, wasn't able to pull down the status bar.
After installing a Test App, I realized that the new phone had a failure and needs to get back to repair...and then the failure happend.
My phone is branded t-mobile and I tried the "how to s-off version from here ( http://forum.xda-developers.com/showthread.php?t=1187231 ), although it noticed that it is for non-branded phones. Just wanted to get back to something "normal"
Well, after using the RUU for TMO_DE (I'm from germany) there was a error message that it wasn't the right RUU version, and got me back to hboot.
And here is my problem: Now my hboot is s-on (0.98.0000) and everything is deleted (recovery, rom) and I have no idea what to do....did I brick my desire s now? is there any chance to put it back to life, aside from hboot?
Thanks a lot in advance, and sorry for my english...
English fine.
First question? What exactly does HBOOT screen say? are you S-OFF still?
If you can put device into HBOOT then you can put it into FASTBOOT
So Connect PC via USB and run a RUU that you want on phone
Thx,
no, that is the problem, i am s-on now, it exactly:
******Security Warning ****
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-3805.06.02.03_M
eMMC-boot
MAR 10 2011, 14:58_38
RUU isn't working...it starts fine, but always quits with error 131 (user Id error) and says i should get the right RUU
Any other ideas?
Chaosbreaker said:
Thx,
no, that is the problem, i am s-on now, it exactly:
******Security Warning ****
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-3805.06.02.03_M
eMMC-boot
MAR 10 2011, 14:58_38
RUU isn't working...it starts fine, but always quits with error 131 (user Id error) and says i should get the right RUU
Any other ideas?
Click to expand...
Click to collapse
Which RUU did you try.....full name?
you could try this one (or is that the one you just did try?)
RUU_Saga_TMO_DE_1.30.111.1_Radio_20.28b.30.0805U_3 8.03.02.11_M_release
I tried:
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release
RUU_Saga_TMO_DE_1.30.111.1_Radio_20.28b.30.0805U_3 8.03.02.11_M_release
and
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed
The only difference using the TMO RUU is, that the error is 140, not 131...but the error message is the same.
I had the same problem with s-on and everything else deleted. Send phone to warranty service and when phone came back, they said they had to replace phone's mothearboard. It's impossible to do something else to make it work
s4x0 said:
I had the same problem with s-on and everything else deleted. Send phone to warranty service and when phone came back, they said they had to replace phone's mothearboard. It's impossible to do something else to make it work
Click to expand...
Click to collapse
That sounds like a good idea, as it's now s-on they'll have no evidence that you did anything wrong, unless of course you admit it
Swyped from HTC Desire S using XDA Premium
Ok thanks, I already guessed that this might be the last solution.
I'll report back if they made it under "warranty" (and if not, what the price was I had to pay )
Ok I was at the t-mobile shop, and they said it will be replaced under warranty, I should come back tomorrow to get my new desire s. (I'm not sure if it really will be there tomorrow, but at least in a few days)
Chaosbreaker said:
Ok I was at the t-mobile shop, and they said it will be replaced under warranty, I should come back tomorrow to get my new desire s. (I'm not sure if it really will be there tomorrow, but at least in a few days)
Click to expand...
Click to collapse
That's excellent news.... <fingers crossed>
Ok, I got my new Desire S today, replaced under warranty, everything fine now I guess I won't do any strange experiments now, but I guess I can't keep my fingers from rooting it and replacing the stock rom with custom.
Anyways, thanks a lot guys
I'm using Android Revolution HD ICS ROM from mike since a couple of days,
but i noticed that i'm stil ***locked*** in de Boot menu.
I want to flash my radio, but this is not working now.
What do i need to do to get in in -revolution- ? If you know what i mean.
I think that i've forgot a step while updating the rom...
screen shows:
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29_2
There have been many people with the same issue. Please do some research, educate.
All that means is fastboot commands aren't going to work, most people rarely use them so you'll be fine.
Oke thanks, but do you know what i need to do to get it fixed?
(for my education)
Well you can flash a new update with the revolutionary bootloader. Kohr-Ah has a tidy selection with everything you could need located at http://forum.xda-developers.com/showthread.php?t=1459767
Head over to the second post and find the section that matches your carrier/CID. Download the 3.24 Unlocked version for your CID and put it on the root of your SD. Now, reboot your phone while holding volume down. The bootloader will detect the PG58IMG file and ask if you want to perform the update. Hit volume up, and it'll update a few things. Then, it'll reboot back into the new bootloader and update the rest. After that, make sure you have an ICS based rom (preferably one built from the 3.24 base, and you're all set. Be sure to delete the PG58IMG after updating, because the bootloader will pick it up every time and refuse to do anything else until it's gone.
Edit: However, I forgot to mention, it really depends on what you mean by "fixed", because you can currently run any rom and do most anything even with a locked bootloader. However, since it is a ten minute fix, I suppose it's worth doing.
tbeelen said:
Oke thanks, but do you know what i need to do to get it fixed?
(for my education)
Click to expand...
Click to collapse
You dont need to fix it you r soff so u can flash any Rom. If you want to unlock bootloader then u can get it done by htcdev.
Sent from my HTC Sensation Z710e using xda premium
Hello there, I Have Looked for an answer here (XDA) but with No success. I Apologize for creating a newer Thread on Almost the Same topic.
I have one problem which is ; the middle part of the Screen won't respond to 'touch.' Its only a Strip of which doesn't recognize 'touch'
INFO:
UNLOCKED
AT&T Version
S-off
CID-11111111
HBOOT-2. 14. 0000
RADIO-0. 24p. 32. 09. 06
OpenDSP-v34. 1. 0. 45. 1219 eMMC-boot
I have taken it to a Phone Repair Shop, in which a guy took it apart & said the connections were fine & that there was the possibility of it being a Software Problem.
I was thinking that maybe RUU'ing it to Original State could possibly Help? But i was also Wondering if Doing so would 'Erase/Get Rid of' Root/S-off/ things like that... thanks in Advance for any Help.
I don't see how it could be a software fault. It sounds like a faulty digitizer to me. Run an RUU, stay stock and if the problem persists it's a hardware fault.
Sent from my Evita
timmaaa said:
I don't see how it could be a software fault. It sounds like a faulty digitizer to me. Run an RUU, stay stock and if the problem persists it's a hardware fault.
Sent from my Evita
Click to expand...
Click to collapse
alright i see.. thanks. Will Running an RUU like ...clear my root/S-off and things like that? Or will that stay? & Since i have AT&T will any RUU do? Or do i have to get an AT&T? Sorry for the n00bish questions
Well, yes of course it will wipe root as it overwrites your system partition. But your unlocked bootloader and s-off status will survive the process. Any RUU is fine because you're s-off, but I'd suggest the at&t 3.18 RUU.
Sent from my Evita