[Q] Phone stuck on 'quietly brilliant' screen - AT&T, Rogers HTC One X, Telstra One XL

Hi all,
For no reason - overnight - my phone just stopped working. It displays the 'quietly brilliant' screen forever. It is HTC One X ATT version, unlocked and runs on t-mobile. I already bought it unlocked on Amazon and never 'tampered' with it nor anything.
I tired to obtain help from HTC support - they told me to hold the power button for 3 minutes, then all buttons for 2 minutes - nothing helped. Before I send it for repair I thought I would ask here.
I am able to boot into HBOOT by holding the volume- button. Then if I go into FASTBOOT and connect the phone (all drivers installed) the mode changes to FASTBOOT USB. I've downloaded the 3.07 RUU from HTC and tried that. It recognizes the phone while in the ".. USB" mode and does the 1st step: reboot. The phone boots into 'quietly brilliant' screen and the connection times out.
Next, I downloaded the android SDK and tried to connect with fastboot manually - I am able to connect, but unable to flash anything - signature not matching, etc. Clearing cache didn't help either - that was about all I could do with my skill level.
My HBOOT screen shows the following:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMCC-boot
Apr 2 2012,21:08:24
I've tried many tips from this forum but wasn't able to get anything to work. Help please!

mfigrs said:
Hi all,
For no reason - overnight - my phone just stopped working. It displays the 'quietly brilliant' screen forever. It is HTC One X ATT version, unlocked and runs on t-mobile. I already bought it unlocked on Amazon and never 'tampered' with it nor anything.
I tired to obtain help from HTC support - they told me to hold the power button for 3 minutes, then all buttons for 2 minutes - nothing helped. Before I send it for repair I thought I would ask here.
I am able to boot into HBOOT by holding the volume- button. Then if I go into FASTBOOT and connect the phone (all drivers installed) the mode changes to FASTBOOT USB. I've downloaded the 3.07 RUU from HTC and tried that. It recognizes the phone while in the ".. USB" mode and does the 1st step: reboot. The phone boots into 'quietly brilliant' screen and the connection times out.
Next, I downloaded the android SDK and tried to connect with fastboot manually - I am able to connect, but unable to flash anything - signature not matching, etc. Clearing cache didn't help either - that was about all I could do with my skill level.
My HBOOT screen shows the following:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMCC-boot
Apr 2 2012,21:08:24
I've tried many tips from this forum but wasn't able to get anything to work. Help please!
Click to expand...
Click to collapse
Anybody feel free to correct me if I am wrong, but you phones HBOOT should say this,
Since you are not rooted ignore whatever is in parenthesis.
(***TAMPERED***)
(***UNLOCKED***)
EVITA PVT SHIP (S-OFF) RL
(CID-11111111)
HBOOT-2.14.0000
RADIO-0.24P.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
Now if I am right, the problem should be that your RUU needs updating. You also seem to be running an old radio version. Your OpenDSP is outdated as well. I would suggest updating your RUU and radio version, I think your OpenDSP should be updated with the RUU. @Madcat8686 would probably be better at explaining everything and being able to give you links, but I think that is the main issue.

The trick is, the phone doesn't take the RUU update - at least not the recent one from HTC website. I have tried other updates though, and they didn't work either. After the 1st reboot the phone gets stuck on 'quietly brilliant' screen and is never recognized again by the computer, so it just times out.
Besides, I really don't care how much it is outdated as long as it works. Meanwhile - it doesn't, and that is the problem I am trying to fix. Factory reset and recovery didn't work either...

mfigrs said:
The trick is, the phone doesn't take the RUU update - at least not the recent one from HTC website. I have tried other updates though, and they didn't work either. After the 1st reboot the phone gets stuck on 'quietly brilliant' screen and is never recognized again by the computer, so it just times out.
Besides, I really don't care how much it is outdated as long as it works. Meanwhile - it doesn't, and that is the problem I am trying to fix. Factory reset and recovery didn't work either...
Click to expand...
Click to collapse
Do you know if it was running the Android 4.1.1 update or the original android 4.0.4?

ChadMan097 said:
Anybody feel free to correct me if I am wrong, but you phones HBOOT should say this,
Since you are not rooted ignore whatever is in parenthesis.
(***TAMPERED***)
(***UNLOCKED***)
EVITA PVT SHIP (S-OFF) RL
(CID-11111111)
HBOOT-2.14.0000
RADIO-0.24P.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
Now if I am right, the problem should be that your RUU needs updating. You also seem to be running an old radio version. Your OpenDSP is outdated as well. I would suggest updating your RUU and radio version, I think your OpenDSP should be updated with the RUU. @Madcat8686 would probably be better at explaining everything and being able to give you links, but I think that is the main issue.
Click to expand...
Click to collapse
Not exactly true. It should say what the user had first posted. The reason his radio is old is because you can't change radio on an unmodified phone. Nothing really needs updating as you put it, but an RUU should at least get the phone booting.
Sent from my Evita.
---------- Post added at 09:59 AM ---------- Previous post was at 09:58 AM ----------
mfigrs said:
The trick is, the phone doesn't take the RUU update - at least not the recent one from HTC website. I have tried other updates though, and they didn't work either. After the 1st reboot the phone gets stuck on 'quietly brilliant' screen and is never recognized again by the computer, so it just times out.
Besides, I really don't care how much it is outdated as long as it works. Meanwhile - it doesn't, and that is the problem I am trying to fix. Factory reset and recovery didn't work either...
Click to expand...
Click to collapse
That 3.07 RUU doesn't exist for our device, that's why it didn't work. Go to androidruu.com and navigate to the Evita section, there you'll find RUU's for our phone. Find one that is at&t/Cingular and try again.
Sent from my Evita.

mfigrs said:
Hi all,
For no reason - overnight - my phone just stopped working. It displays the 'quietly brilliant' screen forever. It is HTC One X ATT version, unlocked and runs on t-mobile. I already bought it unlocked on Amazon and never 'tampered' with it nor anything.
I tired to obtain help from HTC support - they told me to hold the power button for 3 minutes, then all buttons for 2 minutes - nothing helped. Before I send it for repair I thought I would ask here.
I am able to boot into HBOOT by holding the volume- button. Then if I go into FASTBOOT and connect the phone (all drivers installed) the mode changes to FASTBOOT USB. I've downloaded the 3.07 RUU from HTC and tried that. It recognizes the phone while in the ".. USB" mode and does the 1st step: reboot. The phone boots into 'quietly brilliant' screen and the connection times out.
Next, I downloaded the android SDK and tried to connect with fastboot manually - I am able to connect, but unable to flash anything - signature not matching, etc. Clearing cache didn't help either - that was about all I could do with my skill level.
My HBOOT screen shows the following:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMCC-boot
Apr 2 2012,21:08:24
I've tried many tips from this forum but wasn't able to get anything to work. Help please!
Click to expand...
Click to collapse
In fastboot mode (bootloader) with a command prompt type: fastboot getvar all
Post those details and then we can see the bigger picture. Please edit out your IMEI live when posting.
Edit - (just on the off chance you have superCID)

timmaaa said:
Not exactly true. It should say what the user had first posted. The reason his radio is old is because you can't change radio on an unmodified phone. Nothing really needs updating as you put it, but an RUU should at least get the phone booting.
Sent from my Evita.
---------- Post added at 09:59 AM ---------- Previous post was at 09:58 AM ----------
That 3.07 RUU doesn't exist for our device, that's why it didn't work. Go to androidruu.com and navigate to the Evita section, there you'll find RUU's for our phone. Find one that is at&t/Cingular and try again.
Sent from my Evita.
Click to expand...
Click to collapse
Right, but wouldn't that be the latest update for the device. He most likely got the international RUU update.

He can run any Evita RUU later than his current firmware version, it doesn't have to be the latest.
Sent from my Evita.

Hello everyone,
The results of 'getvar all':
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.85.502.3
(bootloader) serialno: HT246W30???? [last 4 digits obscured]
(bootloader) imei: ---
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4126mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
Responding to other questions - I think the RUU 3.07 that I downloaded from HTC suport page for ATT phone should normally work. In the filename it says Cingular, however I also tried other RUUs (at least one) that I downloaded from somewhere, and it didn't work as well. I tried flashing just 'boot_signed.img' from one of those ruus - result: failed - because of signature or something like that.
Regards,

Dude, I like I already said, that 3.07 RUU is not for our device, it's for the HTC One. Just because it says Cingular in the filename doesn't mean it's for our device, it just means it's an at&t RUU. Stop trying RUU's from random places, go to this site:
http://androidruu.com/?developer=Evita
That's where you'll find RUU's for Evita.
Sent from my Evita.

Guys, please - that's not the point!
timmaaa said:
Stop trying RUU's from random places, go to this site: (... it doesn't let me keep the link ...)
Click to expand...
Click to collapse
That's exactly the site I got my other RUU from. The first one that I tried was from HTC website and had this filename: "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe". It says "EVITA" as plainly as it could. I am aware of that.
The thing is: both didn't work. OK, I'm going to try another one just for the sake of completeness, but with two previous attempts the story was the same:
1) Turn on the phone holding volume-
2) Select FASTBOOT
3) Connect to USB
4) Launch RUU
5) Click through dialogs, agree to everything
6) Message appears "Verifying information..."
7) New dialog pops up allowing me to select the 3.18.502.6 update
8) I click Next -> Next -> ...
9) The dialog opens with a message that the phone is being "prepared" for update and it will be rebooted to bootloader
10) Phone reboots and goes to the 'quietly brilliant' screen (or more recently - just black screen)
11) Computer shows message "Waiting for bootloader"
12) Computer times out -> the only available option is Exit.
End of story for me. Is there a way to somehow fix that? I'm OK with doing stuff from cmd - it's just that none of the tips I found in this forum actually worked. For example, adb always ends up with error 'device not found' and fastboot only works while the phone is in the fastboot menu, but does not let me flash anything.
Thanks.

Ok, but the only RUU you specifically mentioned up until this point was one that isn't for this device (3.07), which is why I posted that. Maybe you got it from androidruu, but you definitely didn't get it from the Evita section. There's no need to get narky at me for trying to make sure you don't brick your phone after you've already run at least one RUU that isn't for your device.
Perhaps you need to try the 2.20 at&t RUU.
Sent from my Evita.

You could try putting it into RUU mode to try and force it to flash. I had to do that to mine about 5 hours ago. Just go to fastboot, type "fastboot OEM rebootRUU" and try running the RUU from there.
Sent from my HTC One X using xda app-developers app

My apologies for the confusion - the RUU I was mentioning as 3.07 is actually 3.07.2012 - this way it's being referred to on the HTC website, but the software version in it is 3.18. I'm not allowed to post links yet, so it's kind of hard to explain...
I have tried the 'rebootRUU' trick - it didn't do anything. After some experiments I found that letter sizes do matter - when I entered "fastboot oem rebootRUU" the phone actually rebooted. However, it went straight into the 'quietly brilliant' screen and I wasn't even able to go past the "Verifying information" pop-up on the computer - it ended up in 'usb connection timed out' error.
Anyway, I will try 2.20 - if that one doesn't work, I guess I'll have to send it for service.
Thank you all for trying to help.

timmaaa said:
Ok, but the only RUU you specifically mentioned up until this point was one that isn't for this device (3.07), which is why I posted that. Maybe you got it from androidruu, but you definitely didn't get it from the Evita section. There's no need to get narky at me for trying to make sure you don't brick your phone after you've already run at least one RUU that isn't for your device.
Perhaps you need to try the 2.20 at&t RUU.
Sent from my Evita.
Click to expand...
Click to collapse
http :// www htc com /us/support/htc-one-x-att/news (sorry can't post links)
I think the op might be talking about this RUU which i can confirm does indeed work for the One X. If not, try this RUU! You said it was 3.07.2012 but this is 3.07.2013 not sure if just a typo but here's hoping!
As for the phone, if the RUU doesn't work then it might be a hardware issue not letting the phone boot. It's happened to me on the EVO 4G and no amount of software flashing would fix that.
Also, this probably won't make a difference, but make sure to run the RUU as administrator

mfigrs said:
My apologies for the confusion - the RUU I was mentioning as 3.07 is actually 3.07.2012 - this way it's being referred to on the HTC website, but the software version in it is 3.18.
Click to expand...
Click to collapse
3.07.2013 (its not 2012) is neither the RUU number nor the software version, its the date the RUU was posted to the HTC website (March 7, 2013).
The software/RUU number is 3.18.502.6
The software/RUU number is always in the file name.

Related

[Q] Bootloop-case (no USB-connection)

First off, I've been using this site quite a while now. Lot of problems got fixed by just browsing through the huge archive. Now, I've got a problem that - I think - is hard to fix. Intresting case.
A couple of weeks ago, my powerbutton and USB/chargingconnector were broke. I returned my phone to an HTC-certified repaircompany. They told me they could not fix this problems, because a third party already tried to repair it. My bad, cause I got my broken screen repaired by this company. When I got back the phone, I went to another company that repaired the powerbutton, but the USB/chargingconnector is still broken. Which means I cannot charge my phone directly, I bought an extra battery and batterycharger.
Now, the phone got stuck in (I guess) a bootloop. I can still get into fastboot and recovery, but everytime I just press the powerbutton the logo of 'SENSATION' appears over and over again. I tried many things. A couple:
- Downgrade to Gingerbread-based ROM combined with firmware 1.17 and 3.12, both would not work
- Install latest firmware, including ViperS 1.4.1 rom
All would not work. As I said, I cannot connect my phone with USB-cable with my computer and use 'adb', which makes it very hard. Otherwise, I could maybe go S-ON again and install a stock ROM.
Does anybody know how I can get my phone working again? Thanks in progress!
The problem is a little similar to this one:
http://forum.xda-developers.com/showthread.php?t=1553052&page=2
Different device and I cannot get it running, so ADB WiFi is not an option.
F-CH said:
First off, I've been using this site quite a while now. Lot of problems got fixed by just browsing through the huge archive. Now, I've got a problem that - I think - is hard to fix. Intresting case.
A couple of weeks ago, my powerbutton and USB/chargingconnector were broke. I returned my phone to an HTC-certified repaircompany. They told me they could not fix this problems, because a third party already tried to repair it. My bad, cause I got my broken screen repaired by this company. When I got back the phone, I went to another company that repaired the powerbutton, but the USB/chargingconnector is still broken. Which means I cannot charge my phone directly, I bought an extra battery and batterycharger.
Now, the phone got stuck in (I guess) a bootloop. I can still get into fastboot and recovery, but everytime I just press the powerbutton the logo of 'SENSATION' appears over and over again. I tried many things. A couple:
- Downgrade to Gingerbread-based ROM combined with firmware 1.17 and 3.12, both would not work
- Install latest firmware, including ViperS 1.4.1 rom
All would not work. As I said, I cannot connect my phone with USB-cable with my computer and use 'adb', which makes it very hard. Otherwise, I could maybe go S-ON again and install a stock ROM.
Does anybody know how I can get my phone working again? Thanks in progress!
Click to expand...
Click to collapse
Hi,
Look HERE
4. Flashing RUU manually
Thanks! I wasn't able to find that one. Could somebody tell me with RUU I should pick? As you can understand, I cannot get my CID because I can't access my phone with USB/adb. Netherlands <> Vodafone.
Hmm, when I hold down Volume + Power, the screen lights (sometime 0,5 sec, sometimes 3 secs), but it doens't go into bootloader (anymore). Anyone knows why?
F-CH said:
Thanks! I wasn't able to find that one. Could somebody tell me with RUU I should pick? As you can understand, I cannot get my CID because I can't access my phone with USB/adb. Netherlands <> Vodafone.
Hmm, when I hold down Volume + Power, the screen lights (sometime 0,5 sec, sometimes 3 secs), but it doens't go into bootloader (anymore). Anyone knows why?
Click to expand...
Click to collapse
Hi,
I do not know what to suggest if you cannot get back to bootloader.
I assume that you are s-off,are you also supercid?
In which case it does not matter too much which RUU.
Get a European or Dutch Voda one.
You just want to get it working again.
I'm not supercid. Could it be that I installed wrong RUU and cannot get into bootloader?
F-CH said:
I'm not supercid. Could it be that I installed wrong RUU and cannot get into bootloader?
Click to expand...
Click to collapse
Hi,
The wrong RUU will only give you an error.
It would not cause this.
Downloading this one right now:
RUU_Pyramid_HTC_Europe_1.28.401.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_192608_signed.exe
Do 'RUU's include firmware?
Or is the firmware version in this RUU 1.28.401.1?
F-CH said:
Downloading this one right now:
RUU_Pyramid_HTC_Europe_1.28.401.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_192608_signed.exe
Do 'RUU's include firmware?
Or is the firmware version in this RUU 1.28.401.1?
Click to expand...
Click to collapse
i assume that is also the firmware
F-CH said:
Downloading this one right now:
RUU_Pyramid_HTC_Europe_1.28.401.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_192608_signed.exe
Do 'RUU's include firmware?
Or is the firmware version in this RUU 1.28.401.1?
Click to expand...
Click to collapse
Hi,
A RUU contains a stock ROM ,radio,firmware,and kernel.
The one you have chosen looks like a GingerBread RUU.
Maybe you should look at one that has 3.32 or 3.33 at the front.
malybru said:
Hi,
A RUU contains a stock ROM ,radio,firmware,and kernel.
The one you have chosen looks like a GingerBread RUU.
Maybe you should look at one that has 3.32 or 3.33 at the front.
Click to expand...
Click to collapse
I'm prefering a GingerBread RUU. Unfortunately, I'm getting this error 'An error (-5001)' etc. Normally, you would run the .exe when the phone is connected through USB with the computer, right? That's why I'm getting this error?
Edit: Not getting the error at this one: RUU_PYRAMID_ICS_HTC_Europe_3.33.401.6_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_266171_signed
Now renaming the .zip and putting it on the sd-card!
F-CH said:
I'm prefering a GingerBread RUU. Unfortunately, I'm getting this error 'An error (-5001)' etc. Normally, you would run the .exe when the phone is connected through USB with the computer, right? That's why I'm getting this error?
Click to expand...
Click to collapse
Hi,
I think you should match a RUU with your current setup.
Then,when you phone is working again,you can try to downgrade.
Remember,you have a very unusual situation.
Try to keep it as simple as possible.
Error 5001 may be a bad download.
I just installed the ROM* (picked it from temp, as explained in guide and renamed it as PG58IMG.zip) without an error. After bootloader finished the installation, he asked to press the Powerbutton for a reboot. I pressed the Powerbutton, but nothing happened after pressing it. I waited for 10 minutes before removing the battery and re-inserted the battery. When I press the Powerbutton, nothing happens (again). :crying:
*RUU_PYRAMID_ICS_HTC_Europe_3.33.401.6_Radio_11.76A .3504.00U_11.24A.3504.31_M_release_266171_signed
F-CH said:
I just installed the ROM* (picked it from temp, as explained in guide and renamed it as PG58IMG.zip) without an error. After bootloader finished the installation, he asked to press the Powerbutton for a reboot. I pressed the Powerbutton, but nothing happened after pressing it. I waited for 10 minutes before removing the battery and re-inserted the battery. When I press the Powerbutton, nothing happens (again). :crying:
*RUU_PYRAMID_ICS_HTC_Europe_3.33.401.6_Radio_11.76A .3504.00U_11.24A.3504.31_M_release_266171_signed
Click to expand...
Click to collapse
Hi,
Why not try this one:
RUU​_PYRAMID​_ICS​_Vodafone​_DE_3​.32.162​.11_R​_Radio​_11.69A​....
I know it is German,but it may contain the correct CID.
I'm gonna try that one as well. I also got my original clockworkmod-backup on my computer. Dates 2011 (november). With boot.img, cache.img etc. Can I flash this one as well? And which firmware? I found an android-info.txt:
modelid: PG5813000
modelid: PG5813001
modelid: PG5810000
modelid: PG5811000
cidnum: H3G__***
cidnum: HTCCN***
cidnum: HTC__***
cidnum: HTC*****
cidnum: VODAP***
cidnum: T-MOB***
cidnum: ORANG***
cidnum: O2___***
cidnum: ********
mainver: 1.45.531.1
hbootpreupdate:12
DelCache:1
Just to be clear: This is the last back-up before I rooted my phone.
F-CH said:
I'm gonna try that one as well. I also got my original clockworkmod-backup on my computer. Dates 2011 (november). With boot.img, cache.img etc. Can I flash this one as well? And which firmware? I found an android-info.txt:
modelid: PG5813000
modelid: PG5813001
modelid: PG5810000
modelid: PG5811000
cidnum: H3G__***
cidnum: HTCCN***
cidnum: HTC__***
cidnum: HTC*****
cidnum: VODAP***
cidnum: T-MOB***
cidnum: ORANG***
cidnum: O2___***
cidnum: ********
mainver: 1.45.531.1
hbootpreupdate:12
DelCache:1
Just to be clear: This is the last back-up before I rooted my phone.
Click to expand...
Click to collapse
Hi,
If you have an original nandroid,try restoring it as well.
You never know.
It might work...
malybru said:
Hi,
If you have an original nandroid,try restoring it as well.
You never know.
It might work...
Click to expand...
Click to collapse
But I'm now running 3.33.401.6 firmware. Won't that be a problem?
F-CH said:
But I'm now running 3.33.401.6 firmware. Won't that be a problem?
Click to expand...
Click to collapse
Hi,
Should be fine.

[Q] MY ONE XL IS BRICKED BUT IS BEING RECOGNISED IN DEV MANGER AS "My HTC"

need some help:
BEEN GOIN THROUGH MANY THREADS TRYING ALOT OF STUFF BUT NOTHING WORKS THUS FAR:
phone was in the qhusb dload mode which i get is a hard brick
sent it out to be jtagged but the person couldnt find the schematics for my phone therefore couldnt do it
however when i got it back instead of being recognised by device manager as
qhusb dload it is now....ANDROID DEVICE: My HTC
phone doesnt turn on
no led lights
no fastboot
nothing other than being seen in dev manager
and responding to the power button
TRIED RUNNING STOCK RUU IT STOPS AT WAITING FOR BOOTLOADER
THEN ITS ALMOST AS IF IT TRIES TO REBOOT BUT THE PHONE DISSAPEARS
OUT OF DEVICE MANAGER..AND I GET ERROR 171 USB CONNECTION
I HAVE TO THEN HOLD DOWN ON THE POWER BUTTON
FOR IT TO COME UP IN DEV MANAGER AGAIN AS MY HTC
ANOTHER THING WHEN TRYING TO INSTALL THE RUU
MY CURRENT SOFTWARE VERSION IS "1/4yE" (WHICH IS NO SOFTWARE VERSION I KNO)
ALSO NO MATTER WHAT I TRY IT ALWAYS SAYS
REMOTE ERROR
NO DEVICE CONNECTION
NO DEVICE FOUND
OR SOMETHING LIKE THAT
ONLY REASON I THINK THERE IS STILL HOPE IS
IS THT IT IS PICKED UP IN DEV MANAGER
PLZ HELP!!
Make a Linux boot disk and head over to unbrick Evita thread. If you make it past step 3 you can probably unbrick.
If not jtagg.
Sent from my One X using xda app-developers app
---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------
Unbrick thread
http://forum.xda-developers.com/showthread.php?t=1966850
Boot able usb:
http://forum.xda-developers.com/showthread.php?t=2223669&highlight=ubuntu+boot+usb
Sent from my One X using xda app-developers app
sternpimp1 said:
need some help:
BEEN GOIN THROUGH MANY THREADS TRYING ALOT OF STUFF BUT NOTHING WORKS THUS FAR:
phone was in the qhusb dload mode which i get is a hard brick
sent it out to be jtagged but the person couldnt find the schematics for my phone therefore couldnt do it
however when i got it back instead of being recognised by device manager as
qhusb dload it is now....ANDROID DEVICE: My HTC
phone doesnt turn on
no led lights
no fastboot
nothing other than being seen in dev manager
and responding to the power button
TRIED RUNNING STOCK RUU IT STOPS AT WAITING FOR BOOTLOADER
THEN ITS ALMOST AS IF IT TRIES TO REBOOT BUT THE PHONE DISSAPEARS
OUT OF DEVICE MANAGER..AND I GET ERROR 171 USB CONNECTION
I HAVE TO THEN HOLD DOWN ON THE POWER BUTTON
FOR IT TO COME UP IN DEV MANAGER AGAIN AS MY HTC
ANOTHER THING WHEN TRYING TO INSTALL THE RUU
MY CURRENT SOFTWARE VERSION IS "1/4yE" (WHICH IS NO SOFTWARE VERSION I KNO)
ALSO NO MATTER WHAT I TRY IT ALWAYS SAYS
REMOTE ERROR
NO DEVICE CONNECTION
NO DEVICE FOUND
OR SOMETHING LIKE THAT
ONLY REASON I THINK THERE IS STILL HOPE IS
IS THT IT IS PICKED UP IN DEV MANAGER
PLZ HELP!!
Click to expand...
Click to collapse
Who ever tried to jtag your phone installed some of the software but didn't install the drivers. See exad's advice and try to get the drivers installed.
Venomtester said:
Who ever tried to jtag your phone installed some of the software but didn't install the drivers. See exad's advice and try to get the drivers installed.
Click to expand...
Click to collapse
what drivers should i install?
exad said:
Make a Linux boot disk and head over to unbrick Evita thread. If you make it past step 3 you can probably unbrick.
If not jtagg.
Click to expand...
Click to collapse
tried it didnt work..my partitions wouldnt show
sternpimp1 said:
tried it didnt work..my partitions wouldnt show
Click to expand...
Click to collapse
That is because there is nothing on the phone to show. He wiped it. Can you manually check and see if bootloader still works?
---------- Post added at 09:02 PM ---------- Previous post was at 08:11 PM ----------
If there is no bootloader then you will have to jtag with riff box.
Sent from my HTC One X using xda premium
I do not understand. How is it that I was able to root, s-off, customize hboot, install multiple roms, and many other things on my first try? As you can see, I haven't been doing this for too long, but still. I read these threads, and think to myself "What on earth are you doing wrong?"
Venomtester said:
That is because there is nothing on the phone to show. He wiped it. Can you manually check and see if bootloader still works?
Click to expand...
Click to collapse
no bootloader..so jtag is my only option
all this because i downloaded cwm thru rom manager
dang man thats a standard no no around here. cwm doesnt work for our phones. did you try to install it after you had it jtagged?
jrlatta said:
dang man thats a standard no no around here. cwm doesnt work for our phones. did you try to install it after you had it jtagged?
Click to expand...
Click to collapse
need to do more research http://forum.xda-developers.com/showthread.php?t=2148909
ok it didnt the last time i read lol my apologies is clockwork any better than twrp, i use to use it on my other phone but that was a while back and now im so use to twrp
jrlatta said:
ok it didnt the last time i read lol my apologies is clockwork any better than twrp, i use to use it on my other phone but that was a while back and now im so use to twrp
Click to expand...
Click to collapse
nah just dont use 2.4 versions of twrp dont know about 2.5
jerrycoffman45 said:
need to do more research http://forum.xda-developers.com/showthread.php?t=2148909
Click to expand...
Click to collapse
Only the no-touch and swipe navigation version of 6.0.2.8b formatted my partitions properly. 6.0.2.8b-touch was borked for me but 6.0.3.1 works perfectly. You'll have to download it from CWM's website and flash it manually if you want it.
Of course, only a few people had this problem and I was one of them. It may have been a problem on my end. Not putting down CWM, but honestly you'll be best off with TWRP 2.3.3.0
Sent from my HTC One X using xda premium
this is what fastboot getvar all command shows!!
any help??
INFOversion: 0.5
INFOversion-bootloader: 1.09.0000
INFOversion-baseband:
INFOversion-cpld: ♠
INFOversion-microp: ♠
INFOversion-main: ÿ☻ƒσ
INFOserialno: t♥☻
INFOimei: 355195000000010
INFOproduct: └♠
INFOplatform: HBOOT-8960
INFOmodelid: TÉ►üTÇ É►ü Ç$É►ü$Ç♦¥▲/
INFOcidnum: ¼*É
INFObattery-status: good
INFObattery-voltage: 2788mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: UNKNOWN
INFOcommitno-bootloader: e964c535
INFOhbootpreupdate: 11
INFOgencheckpt: 0
sternpimp1 said:
this is what fastboot getvar all command shows!!
any help??
INFOversion: 0.5
INFOversion-bootloader: 1.09.0000
INFOversion-baseband: * have numbers here for ruu
INFOversion-cpld: ♠ * Should say None
INFOversion-microp: ♠ * 041f I think
INFOversion-main: ÿ☻ƒσ * Should have numbers
INFOserialno: t♥☻ * Should have numbers
INFOimei: 355195000000010
INFOproduct: └♠ * evita
INFOplatform: HBOOT-8960
INFOmodelid: TÉ►üTÇ É►ü Ç$É►ü$Ç♦¥▲/ * evita PJ numbers
INFOcidnum: ¼*É *111111 or at&t
INFObattery-status: good
INFObattery-voltage: 2788mV
INFOpartition-layout: Generic
INFOsecurity: off * 'Should be on'
INFObuild-mode: SHIP
INFOboot-mode: UNKNOWN
INFOcommitno-bootloader: e964c535
INFOhbootpreupdate: 11
INFOgencheckpt: 0
Click to expand...
Click to collapse
* = What I found wrong. You need jtagging.
Venomtester... Can you jtag phones?
Sent from my HTC One X using xda app-developers app
Yes sir. Only certain ones. Once I get my website up and running hopefully I can get jtaggers to join "For Free" so I can connect people to jtaggers in thier area.
Sent from my One X using xda premium
Venomtester said:
Yes sir. Only certain ones. Once I get my website up and running hopefully I can get jtaggers to join "For Free" so I can connect people to jtaggers in thier area.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I wouldn't mind learning how to JTAG. Probably can get the tools I need online. Only thing is that I'm shipping out to basic training in two weeks. So no go for me. I know cell phone doctors and they charge up to 100
Sent from my Carbon-ize Evita using xda-developers app

Noob - HTC One S on T-mobile stuck on edge with S-ON

I recently purchased a phone on ebay in great condition. It was locked, and was on stock rom. I decided I liked how my custom rom operated on my other phone so I unlocked, rooted, and added a custom rom (initally Cyanogenmod, then I tried PacMan) using this tutorial - http://forum.xda-developers.com/showthread.php?t=1583427.
Regardless of the ROM, I haven't been able to get anything over edge data speeds. I've checked the APN settings and they are correct. I have an unlimited data T-Mobile plan.
Here are some pieces of information that might prove helpful:
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
I was told that going back to stock ROM would fix this but that can't be the only way to get 4G...help?
The HTC One S
According to the seller, the phone's model is PJ40110.
My phone got stuck on EDGE after updating to the official JB OTA. I've tried a lot of things and have yet to find a fix. Might have to resort to sending it in for warranty, if possible. Looks like yours is on JB. Did you update it, or did you get it like that?
Here's my thread for reference: http://forum.xda-developers.com/showthread.php?t=2251286
dr3amsINdigital said:
My phone got stuck on EDGE after updating to the official JB OTA. I've tried a lot of things and have yet to find a fix. Might have to resort to sending it in for warranty, if possible. Looks like yours is on JB. Did you update it, or did you get it like that?
Here's my thread for reference: http://forum.xda-developers.com/showthread.php?t=2251286
Click to expand...
Click to collapse
I got it like that, then I updated it and still stuck on edge. Once I have tampered with the bootloader can I still use the warranty?
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.13.50.05.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **************************
(bootloader) imei: **************************
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4168mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Going to try downloading the appropriate RUU to see if that fixes it.
Have you tried forcing it to WCDMA only in *#*#4636#*#*?
There is no RUU yet for t-mobile JB, not that I know of.
Sent from my HTC VLE_U using xda app-developers app
usaff22 said:
Have you tried forcing it to WCDMA only in *#*#4636#*#*?
Click to expand...
Click to collapse
See attachment - when I do WCDMA only I get no data...
I'm beginning to wonder if it was a hardware issue...perhaps a bad antenna?
goosemon said:
I'm beginning to wonder if it was a hardware issue...perhaps a bad antenna?
Click to expand...
Click to collapse
Doubt this will help, but have you thought about trying to S-Off and then running an old RUU (ICS)? It sounds like it could be a hardware issue, though, as you mentioned.
npiper05 said:
Doubt this will help, but have you thought about trying to S-Off and then running an old RUU (ICS)? It sounds like it could be a hardware issue, though, as you mentioned.
Click to expand...
Click to collapse
I'm working on that now, currently getting error: device not found once I type adb shell to get SUPERCID. Looking at other posts to figure out how to get this to work. Phone connected to computer and showing FASTBOOT USB so the computer sees that it is connected. Once I get SUPERCID then I can get S-Off and try going back to ICS.
With adb shell, am I supposed to have my device driver files in the "platform tools" folder so the adb server can identify my phone? HTC Sense and drivers are already installed and work fine.
goosemon said:
With adb shell, am I supposed to have my device driver files in the "platform tools" folder so the adb server can identify my phone? HTC Sense and drivers are already installed and work fine.
Click to expand...
Click to collapse
Nope, just need HTC Sync, then uninstall it (so you're left with only the drivers) and get adb and fastboot files.
Edit: I don't think adb works in fastboot, works while booted only.
Sent from my HTC One S using Tapatalk 2
I've read that people that updated to the T-Mobile JB OTA can't get super CID, which means they can't get S-OFF. Let us know if it works out for you though.
dr3amsINdigital said:
I've read that people that updated to the T-Mobile JB OTA can't get super CID, which means they can't get S-OFF. Let us know if it works out for you though.
Click to expand...
Click to collapse
So I gotta go back to ICS to get SUPERCID...giving that a shot. At this point my sdcard can't be mounted, trying a fix from http://forum.xda-developers.com/showthread.php?t=1630459&page=25
goosemon said:
So I gotta go back to ICS to get SUPERCID...giving that a shot. At this point my sdcard can't be mounted, trying a fix from http://forum.xda-developers.com/showthread.php?t=1630459&page=25
Click to expand...
Click to collapse
I know you mentioned ADB not working when in fastboot. As a poster mentioned before, ADB only works when phone is booted up, not in fastboot. Make sure you have Debugging checked in developer options in the settings menue. I'm almost certain when you SuperCID, you start off with a booted up phone, not in fastboot, so that my be where you are running into an issue.
Also, do you have a custom recovery installed at this point? Just curios. Will your sd not mount in recovery, or just in general.
Keep working. You'll sort it out and learn a ton in the process. That's why I love XDA. Super helpful community.
Nick
npiper05 said:
I know you mentioned ADB not working when in fastboot. As a poster mentioned before, ADB only works when phone is booted up, not in fastboot. Make sure you have Debugging checked in developer options in the settings menue. I'm almost certain when you SuperCID, you start off with a booted up phone, not in fastboot, so that my be where you are running into an issue.
Also, do you have a custom recovery installed at this point? Just curios. Will your sd not mount in recovery, or just in general.
Keep working. You'll sort it out and learn a ton in the process. That's why I love XDA. Super helpful community.
Nick
Click to expand...
Click to collapse
I'll try ADB in regular bootup once I get sdcard to mount. This is in recovery...the latest clockworkmod recovery, I tried running Viperones rom and it happened sometime around 2 this morning, the details are a little fuzzy, I'm pretty sure I saw red and starting hitting my head against the wall and collapsed in tears and anguish
goosemon said:
I'll try ADB in regular bootup once I get sdcard to mount. This is in recovery...the latest clockworkmod recovery, I tried running Viperones rom and it happened sometime around 2 this morning, the details are a little fuzzy, I'm pretty sure I saw red and starting hitting my head against the wall and collapsed in tears and anguish
Click to expand...
Click to collapse
Been there and definitely understand. It can be frustrating, but I feel like most issues can be sorted out. Have you tried a different USB cord or port on your computer. Seems silly, but I've had similar issues, search high and low on xda, and someone suggested to try to different cord and it mounted. These phones can be moody.
Good luck and report back if you need more help.
Nick
Once I can find and flash stock recovery I think I'll be one step close to accessing my sdcard, and from there stock ROM or ICS ROM so I can get superCID, and then S-OFF.
goosemon said:
Once I can find and flash stock recovery I think I'll be one step close to accessing my sdcard, and from there stock ROM or ICS ROM so I can get superCID, and then S-OFF.
Click to expand...
Click to collapse
The first post in this thread has a link for the stock recovery http://forum.xda-developers.com/showthread.php?t=2250573

[Q] Sensation xe continuesly restarts, restart loop, help

htc sensation XE
Hi to all, I’m a newbie to the site and therefore apologies in advance if I’m asking or going to ask simple, newbie questions. I hope someone can help me, many thanks in advance
I went on holiday - whilst abroad I used my phone extensively to take pics, vibers calls, whats app and gps tracking without the SIM. on return when I touched home soil and placed my SIM into the phone it started rebooting in a constant loop i.e. I’m powering the device and it loads up to the home page and then restarts.
What I have done so far, very reluctantly: wiped the cache and restored factory setting with out the SIM card and the SD card - result = NO JOY
Can anyone help me please??? I keep reading that the phone may require flashing, can someone give me step by step instructions.
Much appreciated
gixxer600k6 said:
htc sensation XE
Hi to all, I’m a newbie to the site and therefore apologies in advance if I’m asking or going to ask simple, newbie questions. I hope someone can help me, many thanks in advance
I went on holiday - whilst abroad I used my phone extensively to take pics, vibers calls, whats app and gps tracking without the SIM. on return when I touched home soil and placed my SIM into the phone it started rebooting in a constant loop i.e. I’m powering the device and it loads up to the home page and then restarts.
What I have done so far, very reluctantly: wiped the cache and restored factory setting with out the SIM card and the SD card - result = NO JOY
Can anyone help me please??? I keep reading that the phone may require flashing, can someone give me step by step instructions.
Much appreciated
Click to expand...
Click to collapse
Seems like a loose battery problem. Just try putting a piece of paper between battery and body to make battery fit tight. I guess issue will be resolved after this. Try and report back.
Sent from my HTC Sensation Z710e
thanks, i tried this method and no result.
MrJukeHardbane said:
Seems like a loose battery problem. Just try putting a piece of paper between battery and body to make battery fit tight. I guess issue will be resolved after this. Try and report back.
Sent from my HTC Sensation Z710e
Click to expand...
Click to collapse
gixxer600k6 said:
thanks, i tried this method and no result.
Click to expand...
Click to collapse
Go to fastboot mode, and run
Code:
fastboot getvar all
Post the results (remove imei, serial)
how do i do that? i can get to the bootloader i.e. by holding the volume button down and power on.
i see the fastboot option, i can select this via the power button and thereafter i get 4 options :
1bootloader
2reboot
3reboot boatloader
4power down
appreciate the help,
Far_SighT said:
Go to fastboot mode, and run
Code:
fastboot getvar all
Post the results (remove imei, serial)
Click to expand...
Click to collapse
Can you confirm if the following is correct - just been reading a little about fastboot - am i correct in understanding that i have to download SDK to my pc/laptop and then connect my phone via usb thereafter, i need to go into bootloader of the phone and select fastboot, and then issue the command via the PC. What does the command do? many thanks
gixxer600k6 said:
how do i do that? i can get to the bootloader i.e. by holding the volume button down and power on.
i see the fastboot option, i can select this via the power button and thereafter i get 4 options :
1bootloader
2reboot
3reboot boatloader
4power down
appreciate the help,
Click to expand...
Click to collapse
gixxer600k6 said:
Can you confirm if the following is correct - just been reading a little about fastboot - am i correct in understanding that i have to download SDK to my pc/laptop and then connect my phone via usb thereafter, i need to go into bootloader of the phone and select fastboot, and then issue the command via the PC. What does the command do? many thanks
Click to expand...
Click to collapse
Correct. The command gives information about the board (the phone itself). Some of it is firmware version and many more. For security reasons when you post it to anywhere, remove the IMEI number and Serial.
Also, There is an issue when connecting to 2G networks on some devices that the device reboots. Can you try locking it to 3G only? (On the dialer Type *#*#4636#*#*, then choose "phone information", and there there will be a drop down list of network modes, choose WCDMA Only).
many thanks, i need some guidance, can you point me to a step by step guide if there is one available?
astar26 said:
Correct. The command gives information about the board (the phone itself). Some of it is firmware version and many more. For security reasons when you post it to anywhere, remove the IMEI number and Serial.
Also, There is an issue when connecting to 2G networks on some devices that the device reboots. Can you try locking it to 3G only? (On the dialer Type *#*#4636#*#*, then choose "phone information", and there there will be a drop down list of network modes, choose WCDMA Only).
Click to expand...
Click to collapse
ok managed to load the SDK and pull off the info as per previous post, what next ?? many thanks in advance
C:\AndroidSDK\sdk\tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.153
(bootloader) serialno: SH1____________
(bootloader) imei: 3591____________
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813001
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4113mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.500s
gixxer600k6 said:
many thanks, i need some guidance, can you point me to a step by step guide if there is one available?
Click to expand...
Click to collapse
gixxer600k6 said:
ok managed to load the SDK and pull off the info as per previous post, what next ?? many thanks in advance
C:\AndroidSDK\sdk\tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.153
(bootloader) serialno: SH1____________
(bootloader) imei: 3591____________
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813001
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4113mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.500s
Click to expand...
Click to collapse
This is for general information and I don't know what Far_Sight had in mind for this, but did you try my suggestion (of locking your device to 3g only?) I provided instuctions for that on my previous comment.
astar26 said:
This is for general information and I don't know what Far_Sight had in mind for this, but did you try my suggestion (of locking your device to 3g only?) I provided instuctions for that on my previous comment.
Click to expand...
Click to collapse
@astar26 I asked him to post this so that it is clear what we're dealing with.
Before going into flashing, make sure you have tried all the obvious ways like battery connections, change of SIM card etc.
The easiest way would be to do an ruu. It will reflash all your partitions and can help you out. See http://forum.xda-developers.com/showthread.php?t=1672425
Alternative is to unlock your device and flash custom Rom. Since you did a factory reset already follow http://forum.xda-developers.com/showthread.php?t=1631861 to unlock your bootloader and flash a custom recovery. Then either flash the ahrd Rom (link in the thread) or the stock one again
THESE METHODS WILL MAKE YOU FORMAT YOUR PHONE AGAIN (YOU'LL LOOSE YOUR DATA).
Happy to help.
many thanks again for the reply
I can’t get that far i.e. to the keypad, the phone starts, I see the htc logo and then it seems normal for maybe 2/3 seconds and then reboots. I have to remove the battery to power it down otherwise it continues the restart boot loop over and over again. I can get to the bootloader if there is a way to do it from there please provide newbie instructions.
Also the bootloader is unlocked - the previous owner unlocked it (I have had the phone like this since it was 4 months old and has been absolutely fine)
I’m thinking if it’s not a hardware issue then to flash the ROM and see if it resolves it. Now my issue is that I haven’t done anything like this before and when I Google for info it’s a bit like opening up a can of worms lol.
Am I correct, please confirm the following and put me right please

1:As the bootloaders unlocked can I download htc syn to my laptop, then download the correct RUU to the laptop, thereafter connect the phone via usb and boot into the bootloader and select fastboot, after selecting the fastboot option it should change to fastboot usb. Once this is done I can run the RUU and job done. (Is this correct)
2:According to an article I read my phone has a codename, is the codename for my phone Pyramid?
3nce I know the correct codename I can download the RUU from ‘shipped roms’ (http://www.shipped-roms.com/?category=android), Also at this stage when I select Pyramid I get a load of options for various RUU’s – which one is the correct one? And how do I know?
astar26 said:
This is for general information and I don't know what Far_Sight had in mind for this, but did you try my suggestion (of locking your device to 3g only?) I provided instuctions for that on my previous comment.
Click to expand...
Click to collapse
gixxer600k6 said:
many thanks again for the reply
I can’t get that far i.e. to the keypad, the phone starts, I see the htc logo and then it seems normal for maybe 2/3 seconds and then reboots. I have to remove the battery to power it down otherwise it continues the restart boot loop over and over again. I can get to the bootloader if there is a way to do it from there please provide newbie instructions.
Also the bootloader is unlocked - the previous owner unlocked it (I have had the phone like this since it was 4 months old and has been absolutely fine)
I’m thinking if it’s not a hardware issue then to flash the ROM and see if it resolves it. Now my issue is that I haven’t done anything like this before and when I Google for info it’s a bit like opening up a can of worms lol.
Am I correct, please confirm the following and put me right please

1:As the bootloaders unlocked can I download htc syn to my laptop, then download the correct RUU to the laptop, thereafter connect the phone via usb and boot into the bootloader and select fastboot, after selecting the fastboot option it should change to fastboot usb. Once this is done I can run the RUU and job done. (Is this correct)
2:According to an article I read my phone has a codename, is the codename for my phone Pyramid?
3nce I know the correct codename I can download the RUU from ‘shipped roms’ (http://www.shipped-roms.com/?category=android), Also at this stage when I select Pyramid I get a load of options for various RUU’s – which one is the correct one? And how do I know?
Click to expand...
Click to collapse
1) Bootloader unlocked means you can flash custom ROMs, but not firmware (only via RUU).
2) Yes, it is Pyramid
3) Since you are not S-Off, you need the exact RUU for your CID, which is HTC__001 in your case, which means you need a WWE one (good for you, as this one is easily found).
gixxer600k6 said:
many thanks again for the reply
I can’t get that far i.e. to the keypad, the phone starts, I see the htc logo and then it seems normal for maybe 2/3 seconds and then reboots. I have to remove the battery to power it down otherwise it continues the restart boot loop over and over again. I can get to the bootloader if there is a way to do it from there please provide newbie instructions.
Also the bootloader is unlocked - the previous owner unlocked it (I have had the phone like this since it was 4 months old and has been absolutely fine)
I’m thinking if it’s not a hardware issue then to flash the ROM and see if it resolves it. Now my issue is that I haven’t done anything like this before and when I Google for info it’s a bit like opening up a can of worms lol.
Am I correct, please confirm the following and put me right please

1:As the bootloaders unlocked can I download htc syn to my laptop, then download the correct RUU to the laptop, thereafter connect the phone via usb and boot into the bootloader and select fastboot, after selecting the fastboot option it should change to fastboot usb. Once this is done I can run the RUU and job done. (Is this correct)
2:According to an article I read my phone has a codename, is the codename for my phone Pyramid?
3nce I know the correct codename I can download the RUU from ‘shipped roms’ (http://www.shipped-roms.com/?category=android), Also at this stage when I select Pyramid I get a load of options for various RUU’s – which one is the correct one? And how do I know?
Click to expand...
Click to collapse
1)you are correct:good:
but i think you don't need htc sync(i am not sure for that)
2)sensation/xe/4G's codename is pyramid
3)the ruu have to correspond with your region(same firmware or higher) and your cid
you can also see Far_SighT's post for RUU
but i suggest to flash first the stock rom from recovery
if you don't have a custom recovery flash 4ext(again from Far_SighT's post on how to flash it,only step 2)
then from recovery :
nandroid backup just in case
format all partitions except sdcard
enable smartflash
flash the rom
done
Many thanks to all that have replied and viewed with the intent to help
I have managed to resolve the phone using the guide provided. I downloaded an RUU.
It was quite interesting doing all this 
I flashed the phone with an identical ROM i.e. version 3.33.401.153 – so I’m guessing whilst on holiday something happened which caused the software to get corrupt!
Next question, is it possible to flash the ROM again but with maybe the latest firmware – if yes can someone recommend an RUU.
many thanks
gixxer600k6 said:
Many thanks to all that have replied and viewed with the intent to help
I have managed to resolve the phone using the guide provided. I downloaded an RUU.
It was quite interesting doing all this 
I flashed the phone with an identical ROM i.e. version 3.33.401.153 – so I’m guessing whilst on holiday something happened which caused the software to get corrupt!
Next question, is it possible to flash the ROM again but with maybe the latest firmware – if yes can someone recommend an RUU.
many thanks
Click to expand...
Click to collapse
if you used a RUU with 3.33 firmware then you have the latest
@astar26 has the right idea. I had this issue for a long time, and after my own investigation I concluded that it was either the phones connection to 2g was resetting it, or I damaged the cpu by heavy overclocking. But the fix for the former helped me very much. One thing to note, if you can power up the device and have it perfectly without your SIM card in it. Or you can power it up with the phone in aeroplane mode then it tends to help the rebooting stop for a little while when your simcard is reactivated
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

S-OFF still possible anymore with latest phones?

I had a phone replacement done after my power button stopped working properly, and the latest phone comes with what appears to be the latest firmware and latest everything.
Is it possible to still get S-OFF anymore or did they disbale that all too well?
My phone info:
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012,17:10:57:-1
I tried to downgrade via different RUU's to lower firmware's but the HBOOT and Radio versions stay, only the software version downgrades.
I can easily always get back to Unlock Recovery, install Teamwin, and SuperSU for stock ROM afterwards.
I have tried all of the following with no success:
-Moonshine
-Rumrunner
-Revone method
-FacePalm method
I am sure I am doing all the steps right, got latest HTC driver, only via USB2.0, NO AV, no Firewall, and it just won't work. The furthest I got was with Rumrunner and after pouring first time and a few extra steps I got a WTF are you doing message.
So is it possible anymore, anything else I can try, or is it a dead cause?
Thanks for any help!!!
xtacydima said:
I had a phone replacement done after my power button stopped working properly, and the latest phone comes with what appears to be the latest firmware and latest everything.
Is it possible to still get S-OFF anymore or did they disbale that all too well?
My phone info:
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012,17:10:57:-1
I tried to downgrade via different RUU's to lower firmware's but the HBOOT and Radio versions stay, only the software version downgrades.
I can easily always get back to Unlock Recovery, install Teamwin, and SuperSU for stock ROM afterwards.
I have tried all of the following with no success
Moonshine
Rumrunner
Revone method
FacePalm method
I am sure I am doing all the steps right, got latest HTC driver, only via USB2.0, NO AV, no Firewall, and it just won't work. The furthest I got was with Rumrunner and after pouring first time and a few extra steps I got a WTF are you doing message.
So is it possible anymore, anything else I can try, or is it a dead cause?
Thanks for any help!!!
Click to expand...
Click to collapse
Which CID and build version your Phone Have?
TELUS_WWE_3.16.661.4?
TMOUS_3.14.531.11?
3.14.531.17 710RD - it's tmobile so should be TMOUS
CID according to my mmcblk0p4 file is T-MOB01
xtacydima said:
3.14.531.17 710RD - it's tmobile so should be TMOUS
CID according to my mmcblk0p4 file is T-MOB01
Click to expand...
Click to collapse
OK, I have the same version.
You have not tried this one:
http://firewater-soff.com
Let us know unless I try it before you.
808phone said:
OK, I have the same version.
You have not tried this one:
http://firewater-soff.com
Let us know unless I try it before you.
Click to expand...
Click to collapse
just tried
it stopped after chugging.........
Rumrunner and moonshine and this all appear to be related, same menu and startup screen
xtacydima said:
just tried
it stopped after chugging.........
Rumrunner and moonshine and this all appear to be related, same menu and startup screen
Click to expand...
Click to collapse
Sounds almost exactly like what happened to me. I could unlock boot loader, install TWRP, then even got superSU going. But couldn't do much more until I got my phone stuck in the HTC logo with red text boot loop.
I guess I will try either moonshine or firewater. Will let you know.
OK, you are not going crazy. Moonshine and firewater do not work. Tried them both.
Firewater crashes out of the adb shell.
Moonshine gets stuck on waiting for fastboot Try 3)
I give up.
808phone said:
OK, you are not going crazy. Moonshine and firewater do not work. Tried them both.
Firewater crashes out of the adb shell.
Moonshine gets stuck on waiting for fastboot Try 3)
I give up.
Click to expand...
Click to collapse
I know how you feel, every post that reports success basically directs you towards an older RUU so you can be on a different HBOOT, BUT, that is no longer the case as older RUU's will install OK - however - will only change the base software version, the HBOOT version remains the same now. Whatever they did to lock down the latest build they Nerf'd it good, unless a new exploit comes out I am afraid we are stuck.
What sucks is even after getting root back on stock ROM you don't truly have full control, I tried to delete some apk's and they are read only. Will try to mess with it later, I already invested way more hours than I care for on this thing.
Well I have a matching HBOOT I think. 2.15. In addition, there's a post saying it works - but it doesn't.
808phone said:
Well I have a matching HBOOT I think. 2.15. In addition, there's a post saying it works - but it doesn't.
Click to expand...
Click to collapse
I thought maybe Windows was somehow just in general the problem, so just tried in Ubuntu off of a live USB drive.
I got up to step 2 and after "Waiting for Device", next line "Device detected....."
got an "ERROR: ADB failure" and then it stops and goes back to default prompt
I think I officially give up
I almost want to pay the local expert $75 to s-off just to see if it could be done, but I did say "almost".
Not worth it.
What about the all in one tool that was discussed a while back?
bb
OK so I have read that moonshine getting stuck on "waiting for fastboot" Try 3) could be because of antivirus or firewall/internet security.
When you see "................................." forever etc...
Maybe try and disable these???
I don't think you're waiting long enough for Moonshine to finish. It took longer than three tries on the two phones I've done it on.
OK, finally got S-off
Thanks to a friend who is well experienced in the filed, here was how...
First, had to go to RUU: RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2
I was on 3.14.531.17 but it was too locked down to do anything
Then, after reboot, NO SuperSU, No sending a custom Recovery to the phone, just Dev unlock bootloader
Boot into normal stock ROM and run moonshine, worked on Win7 Pro 64bit with Firewall enabled and Symantec ver11 Corp edition both running on PC, of course latest HTC drivers
I think by sending a recovery and running SU somehow screwed it up, it was the only difference
I'll leave the RUU on my website for those whom need, not sure for how long though
http://d-innovations.org/RUU_Ville_....30.50.08L_release_309489_signed_ICS_2.exe.7z
WOW you got it working!!!!!! COOL! I may try it again!
And for the other poster -yes, my screen was filled with "................................" many times.
Thanks - downloading RUU now - please leave it up for a little while longer.
xtacydima said:
OK, finally got S-off
Thanks to a friend who is well experienced in the filed, here was how...
First, had to go to RUU: RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2
I was on 3.14.531.17 but it was too locked down to do anything
Then, after reboot, NO SuperSU, No sending a custom Recovery to the phone, just Dev unlock bootloader
Boot into normal stock ROM and run moonshine, worked on Win7 Pro 64bit with Firewall enabled and Symantec ver11 Corp edition both running on PC, of course latest HTC drivers
I think by sending a recovery and running SU somehow screwed it up, it was the only difference
I'll leave the RUU on my website for those whom need, not sure for how long though
]
Click to expand...
Click to collapse
I just realized that this is the RUU I have been using. I have it on my laptop already. So you say no SU, no custom recovery, just unlock the bootloader and boot into the stock ROM? I have the WinDroid HTC ONE S Toolkit and Rumrunner and Moonshine. I'm going to try the Toolkit first, then Rumrunner, and then finally Moonshine, since you say Moonshine works and it's basically the same as Rumrunner as far as methods are concerned. The toolkit may, however, do something different. Who knows. Here goes EVERYTHING!
[EDIT] I did get it working! Moonshine is the only one that worked. Maybe because it's more specific to firmware, rather than only device. I'm now moonshine S-OFF
So now another report of it working?
I guess I should try it BUT I'd like to hear from you guys on how/what ROMS you got installed AFTER the fact.
808phone said:
So now another report of it working?
I guess I should try it BUT I'd like to hear from you guys on how/what ROMS you got installed AFTER the fact.
Click to expand...
Click to collapse
Here I posted a tutorial for obtaining s-off that is a little more in depth: http://forum.xda-developers.com/showthread.php?t=2652601
I'm currently running Android 4.4.2 thanks to Dirty Unicorns AOKP ROM based off Omni-Rom. The link to that ROM is in my signature. Just click on the ROM name and it'll take you there. There are only three bugs on that one. No capacitive lights (not a big deal), No native torch app (down one from the play store), and wifi tends to act up. It connects to wifi and works great and tethering works too. But it has a tendency to disconnect while unused and take a little bit of try, try again to get it to connect again. Other than those, it's my daily driver. My wifi has been spot on for the past few days. But it's hit and miss.
I pretty much have the same question. I have an unbranded European HTC One S model.
version-bootloader: 2.15.0000
version-misc: PVT SHIP S-ON
platform: HBOOT-8960
modelid: PJ4010000
cidnum: HTC__E11
Managed to unlock the bootloader (via HTCDev), flash TWRP (2.0.33 cause members said newest wasn't stable/caused problems with CM11) and Root with SuperSU. I haven't flashed any custom ROM yet. Software info shows version 3.16.401.9
Unsure if I should proceed with any of the S-OFF methods (Facepalm, Moonshine, Rumrunner, firewater) right now prior to flashing any custom ROM. It seems most people who have tried these S-OFF methods have used them in combination with US models. Advise would be much appreciated.

Categories

Resources