Related
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
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?
Hi,
I am new to this forum.
Few days back, I bought a sensation XE on ebay where the seller claims to have run an update and after that, the display backlight wouldn't go on again.
I thought that he screwed up somewhere and I could just flash a lower version and everything would be fine.
But once I got it and entered the bootloader (default one, no root it seems), the light wouldn't go on either. Somewhere I read that this is an indicator that there is a hardware problem which is causing the error since the bootloader is kind of software independant.
Is that right? I just wanted to make sure, before I digg into either way.
Or is it possible that it realy is a software error?
Any advice would be greatly apprechiated
Kindest Regards
Rene
surfer90 said:
Hi,
I am new to this forum.
Few days back, I bought a sensation XE on ebay where the seller claims to have run an update and after that, the display backlight wouldn't go on again.
I thought that he screwed up somewhere and I could just flash a lower version and everything would be fine.
But once I got it and entered the bootloader (default one, no root it seems), the light wouldn't go on either. Somewhere I read that this is an indicator that there is a hardware problem which is causing the error since the bootloader is kind of software independant.
Is that right? I just wanted to make sure, before I digg into either way.
Or is it possible that it realy is a software error?
Any advice would be greatly apprechiated
Kindest Regards
Rene
Click to expand...
Click to collapse
did not get your question try to simplify it and also the details of your phone and wad bootloader shows up is it
shrex said:
did not get your question try to simplify it and also the details of your phone and wad bootloader shows up is it
Click to expand...
Click to collapse
Question is: can this be a software error that could have come from something gone wrong while updating or does this show that it has to be a hardware error?
What I said was that when I enter the bootloader, the backlight isn't on either.
bootloader shows
****LOCKED***
Pyramid PVT SHIP S-ON RL
HBOOT 1.29.0000
RADIO-11.24A.3504.31_M
Open ADSP-v05.6.0.2226.00.0418
eMMC-boot
Noone knows the answer or noone understands the question?
maybe I should rerephrase the question:
If there is no backlight shining in bootloader, can this be caused by a firmware error or does this HAVE to be a hardware error?
surfer90 said:
maybe I should rerephrase the question:
If there is no backlight shining in bootloader, can this be caused by a firmware error or does this HAVE to be a hardware error?
Click to expand...
Click to collapse
do u mean the backlight wch the soft keys have (menu,home,back,search) buttons thos keys?
Not only that, I mean display and button backlight. You can't see anything unless you turn the phone to reflect the sun
Ohh now I got it ... Boot into bootloader n select factory reset but b sure it vll delet all ur data n vll make ur phone as stock
hit thanks if I hve hlped you
sent from HTC sensation using xda premium
Okay i chose factory reset and it didnt give me anything to choose.
Seems like it has finished now.
But still all light is off
surfer90 said:
Okay i chose factory reset and it didnt give me anything to choose.
Seems like it has finished now.
But still all light is off
Click to expand...
Click to collapse
Try flashing a ruu.. Check ruu info guide by kgs1992 in sensation general section.. There instructions to find correct ruu and flashing it were given
Sent from my HTC Sensation using xda premium
okay I did the flash and it was completed without an error. but still the screen has no light.
But (I am not sure whether this happened before) the buttons at the bottom sometimes are iluminated.
So this is a hardware error? or can it still be a software error?
thanks
For some of you this is pretty obvious, but I wanted to post in case someone else came across the same problem. My backlight is broken, and I wanted to reset my phone to stock before attempting a warranty repair. I followed the suggestions from this thread:
http://forum.xda-developers.com/showthread.php?t=2365352&highlight=backlight
RUU'd to 3.18
Installed a custom hboot with locked, S-ON, etc. written
ran fastboot oem writesecureflag 3
And was immediately bricked, i.e. the infamous qhsusb_dload issue. Luckily, I was able to overwrite my hboot using the unbrick_evita kit and get it back up and running. Hopefully, no one else will attempt to undo S-OFF after customizing hboot, assuming that is the issue.
Feel free to flame away - I know this was a pretty stupid move.
tlazarus said:
For some of you this is pretty obvious, but I wanted to post in case someone else came across the same problem. My backlight is broken, and I wanted to reset my phone to stock before attempting a warranty repair. I followed the suggestions from this thread:
http://forum.xda-developers.com/showthread.php?t=2365352&highlight=backlight
RUU'd to 3.18
Installed a custom hboot with locked, S-ON, etc. written
ran fastboot oem writesecureflag 3
And was immediately bricked, i.e. the infamous qhsusb_dload issue. Luckily, I was able to overwrite my hboot using the unbrick_evita kit and get it back up and running. Hopefully, no one else will attempt to undo S-OFF after customizing hboot, assuming that is the issue.
Feel free to flame away - I know this was a pretty stupid move.
Click to expand...
Click to collapse
Stupid yes lol but you fixed it. I'd call that a learning experience.
Sent from my HTC One XL using XDA Premium 4 mobile app
tlazarus said:
For some of you this is pretty obvious, but I wanted to post in case someone else came across the same problem. My backlight is broken, and I wanted to reset my phone to stock before attempting a warranty repair. I followed the suggestions from this thread:
http://forum.xda-developers.com/showthread.php?t=2365352&highlight=backlight
RUU'd to 3.18
Installed a custom hboot with locked, S-ON, etc. written
ran fastboot oem writesecureflag 3
And was immediately bricked, i.e. the infamous qhsusb_dload issue. Luckily, I was able to overwrite my hboot using the unbrick_evita kit and get it back up and running. Hopefully, no one else will attempt to undo S-OFF after customizing hboot, assuming that is the issue.
Feel free to flame away - I know this was a pretty stupid move.
Click to expand...
Click to collapse
experience is the greatest teacher....
This should not cause a brick as I have done it. You should think and be aware of risks whenever you are flashing or modifying any roms hboot firmware etc.