Database Info

[Q] Please help. Stuck in Bootloop!

Hi there.
Bootloader details are
***Unlocked***
PYRAMID PVT SHIP S-ON RL
HBOOT- 1.27.0000
eMMC- boot
Jan 13 2012, 17:33:34
I'm trying run a RUU which I downloaded and have had an
'ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
The error may be because my bootloader is unlocked? But when I try to re-lock it it shows the "security warning" below "re-locked"
and then the RUU gives me ERROR [140]: BOOTLOADER VERSION ERROR
The RUU I'm trying to use is called RUU_Pyramid_hTC_Asia_WWE_1.35.707.1_Radio_10.43a.9 007.00U_10.51.9007.27_M3_release_198358_signed
Please help! I've been trying to Install MIUI all day and it is turning into a nightmare.. I don't want to lose this phone D:

You are 1.27 boot your kinda stuck you have to soff and that's not easy with 1.27 some ruu need super cid and soff
Sent from my Sensation using xda premium

craven667 said:
You are 1.27 boot your kinda stuck you have to soff and that's not easy with 1.27 some ruu need super cid and soff
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
Thanks for the reply.
I figured this would be hard as I've tried alot already..
I read somewhere there was a way to get soff involving connecting a wire somewhere and it can be risky. Can you affirm this is the best bet to recover my device?
By the way when relocked bootloader gives me these details..
Radio-11.23.3504.07_M2
OpenADSP-v02.6.0.2226.00.0131
Using ADB CMD I discovered the Android Image is version: 3.32.707.1
I hope someone can give my a clue as to what my best bet is here.. at this point I just want a usable phone again.

There's a new unlock out there but I never used it unlocked 3 at hboot 1.18 sorry
Sent from my Sensation using xda premium

Shunun said:
Hi there.
Bootloader details are
***Unlocked***
PYRAMID PVT SHIP S-ON RL
HBOOT- 1.27.0000
eMMC- boot
Jan 13 2012, 17:33:34
I'm trying run a RUU which I downloaded and have had an
'ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
The error may be because my bootloader is unlocked? But when I try to re-lock it it shows the "security warning" below "re-locked"
and then the RUU gives me ERROR [140]: BOOTLOADER VERSION ERROR
The RUU I'm trying to use is called RUU_Pyramid_hTC_Asia_WWE_1.35.707.1_Radio_10.43a.9 007.00U_10.51.9007.27_M3_release_198358_signed
Please help! I've been trying to Install MIUI all day and it is turning into a nightmare.. I don't want to lose this phone D:
Click to expand...
Click to collapse
the RUU you are using wont run...because you are s-on...right now based on your HBOOT ...you might have 3.32 firmware....and the RUU you are using has 1.35 firmware (see after WWE_<this is firmware> in the RUU name)...
that's why you are getting that bootloader error..
the best solution for your case is to use ICS RUU..
to get that i need your cid
steps to get cid
1.keep the phone in fastboot and connect it to pc (phone reads "fastboot usb")
2.go to your adb/fastboot folder and type
"fastboot getvar all" without quotes
and post all the results...except serial number and imei
I'll find you the correct RUU for you..which might/will avoid bootloop..after you gave me those details

Okay, I ran the command. Here is what I have.
C:\AndroidSDK\tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.707.10
(bootloader) serialno: ************
(bootloader) imei: **************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3893mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.516s
C:\AndroidSDK\tools>
You might want to know that since trying that RUU I have also tried one called
RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_TW_3.32.709.108_R1_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_251682_signed
It gave me ERROR [156]:IMAGE ERROR
Thanks for your help

please edit your post by removing,,,the serial number and imei present in the list
also the other RUU...wont run because the cid's are not matching...and there is No ICS RUU ...yet in your case...
so the choice left is ...to run a custom rom ?
fine with you ?
this the guide ...you need to follow to get ARHD custom rom
guide to flash roms with S-oN
please follow this guide step by step...and you'll have a custom ROM by end of it
.That guide is wriiten by a friend of mine ...and i helped him to make it pretty noob-free...follow that guide and let me know ..if you got any problem

So u know there's a kinda beta s-off but I would wait if it was me your call
Sent from my Sensation using xda premium

ganeshp said:
please edit your post by removing,,,the serial number and imei present in the list
also the other RUU...wont run because the cid's are not matching...and there is No ICS RUU ...yet in your case...
so the choice left is ...to run a custom rom ?
fine with you ?
this the guide ...you need to follow to get ARHD custom rom
guide to flash roms with S-oN
please follow this guide step by step...and you'll have a custom ROM by end of it
.That guide is wriiten by a friend of mine ...and i helped him to make it pretty noob-free...follow that guide and let me know ..if you got any problem
Click to expand...
Click to collapse
THANKS!!!
Through following your friends/your guide I was able to flash rom
rmk-pyramid-stock_ics_3.32.401.3-v1
I really don't understand why I couldn't do this before when I was using clockworkmod recovery... Although it may have been because I didn't flash the appropriate Boot.img..?
So from what I've read, being S-on on FW3.32 I cannot flash roms that aren't 3.32 as well, would that be correct?
I don't understand how I'm supposed to know which are 3.32 or not..
I really want MIUI still.
Perhaps you could provide link to the MIUI rom which is 3.32..? would it be the latest?
kind regards and thanks for you help and time

[Q] HTC One X (Evita) 3.18 RUU for S-ON

I have had this great phone for around 3-4 months now. In the second week of owning it, I already unlocked the bootloader and rooted my phone. It is not S-OFF, because I'm under the impression that you need to buy extra hardware.
What I want to know is if there is any way that I can flash 3.18 RUU on my AT&T branded (but I use T-Mobile) evita? If there is, can you provide me with a link?
Again, I'm already rooted and I'm bootloader unlocked. Thanks

You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita

Thanks, mate. I appreciate the fast answer. Naturally, I hate being left behind; and seeing that most of the new ROMs require S-Off for the 3.4 kernel, I decided it was time to upgrade. I'll give it a try, as I'm currently trying to flash a ROM because I mistakenly flashed one of ^. Now, it's stuck on the the HTC splash screen, and I guess it's just the first boot scenario. However, it has taken a curious amount of time.

Yeah it's pretty much gonna be essential from now on anyway so you might as well get it outta the way.
What ROM did you try to flash? Also, what firmware/hboot are you currently on?
Sent from my Evita

I tried flashing CarbonROM. It gave me that (Status 7) error so I figured it was the 3.4 kernel giving me problems. After that, I tried flashing a previous version of CarbonROM, and it'd just stay stuck in the splashscreen (This is the ROM that I was discussing in my previous post). Now I tried to flash RageXL, and it's bootlooping. So I'm figuring that I should just go to a stock ROM and get this procedure done, and THEN flash a custom ROM. #BadLuckw3r3w0lv33

Ok. Yep it's the fact that you haven't yet upgraded via the RUU that these ROMs won't boot. Try flashing something like MagioRom or ViperXL just to get the s-off procedure done.
Sent from my Evita

Hmph. I'm pretty sure I've downloaded the latest Google and HTC USB drivers. Still, when I enter "adb reboot bootloader", this pops up:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
I have enabled USB debugging on my HOXL. Perhaps, it's the HTC Sync Manager? I have no clue beyond that point. I even tried restarting my phone AND computer.
EDIT: Nevermind, I just manually rebooted to the bootloader and continued from there. I am now S-Off

:thumbup:
Sent from my Evita

Btw.... If I helped you, please press the thanks button.
Sent from my Evita

Help me please
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....

hirias said:
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
Click to expand...
Click to collapse
If you are already s-off, just install custom recovery, then flash a rooted ROM or SU to get root.
Sent from my HTC One XL using xda app-developers app

Will this RUU work if I have a locked bootloader and s-on?

Chudawg62 said:
Will this RUU work if I have a locked bootloader and s-on?
Click to expand...
Click to collapse
As I said earlier in the thread, SuperCID + s-on + jb RUU = brick.
Sent from my Evita

guys can you please help me here?
my phone is
*** LOCKED ***
EVITA PVT SHIP S_OFF RL
CID-11111111
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Junn 11 2012,14:36:28
i dont understand thiss phone that well so can you please tell me if its safe to install the stock jellybean RUU on my phone?

Yes you're s-off so you can run the RUU with minimal risk.
Sent from my Evita

3.17 or 3.18?
Hi,
First off, thanks everyone - this forum has provided me a wealth of information.
I'm wondering if I can run non-sense based roms (ex. Cyanogenmod 10.2 or 11) without downgrading the touchpanel firmware. Here are my phone specs:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT27XXXXXXXX
(bootloader) imei: 359691XXXXXXXXX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4050mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Currently running ViperXL Android 4.2.2, stock kernel. Had to upgrade to HBOOT 2.15 to get rid of the random reboots and signal drop.
Before I upgraded HBOOT from 2.14 to 2.15 I was pretty sure I was on 3.17. I'm not even sure how to check this again? Would the upgrade to hboot 2.15 put me on 3.18? Sorry for the n0ob questions, help would be appreciated.

Current aosp ROMs no longer require you to down the ts firmware, they haven't since about June. You're a bit confused about the terminology, you didn't just upgrade to the 2.15 hboot, you upgraded to the 2.15 firmware, so you're currently on the 2.15 firmware. The hboot is only one component of the firmware as a whole.
Long story short, yes you can flash non-sense ROMs.
Sent from my Evita.

timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
can i run this RUU if i'm on CM10.2 ? and it says it will delete ALL from my phone, do i need to flash a rom and gapps right after i did that or will it still boot on CM10.2 ?

The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.

timmaaa said:
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
Click to expand...
Click to collapse
it doesn't work, i'm getting the usb connection error (170) but the cmd adb devices works just fine and the rumrunner s-off procedure went fine too...maybe i'm missing something ?

[Q] Bootloader Help HTC Sensation XE

Hi all,
I successfully unlockes, rooted and S-off my Sensation XE and I think I also SIM-unlocked the phone.
To be able to do this, I had to downgrade my bootloader from 1.29.0000 to 1.17.000 to be able to S-Off it.
I also restored the original backup from the SD card. I never had any errors.
The poblem now is that the phones gets into endless cycles of rebooting and I'm not able to switch it on. I can still asily get into the bootloader. I think the problem lies in the Bootloader version and I tried to find my phone's up-to-date hboot version (I guess it has to be 1.29.1111 now). Any help would be highly appreciated. Links and easy explanation as I'm still a noob please.
Many thanks.

Output of my fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.17.1111
(bootloader) version-baseband: 10.14.9035.01_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.45.531.1
(bootloader) serialno: ********************
(bootloader) imei: *******************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 92e53710
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

wmgamd said:
Hi all,
I successfully unlockes, rooted and S-off my Sensation XE and I think I also SIM-unlocked the phone.
To be able to do this, I had to downgrade my bootloader from 1.29.0000 to 1.17.000 to be able to S-Off it.
I also restored the original backup from the SD card. I never had any errors.
The poblem now is that the phones gets into endless cycles of rebooting and I'm not able to switch it on. I can still asily get into the bootloader. I think the problem lies in the Bootloader version and I tried to find my phone's up-to-date hboot version (I guess it has to be 1.29.1111 now). Any help would be highly appreciated. Links and easy explanation as I'm still a noob please.
Many thanks.
Click to expand...
Click to collapse
Hi,
If you can get into bootloader,can you please post what it says there?

malybru said:
Hi,
If you can get into bootloader,can you please post what it says there?
Click to expand...
Click to collapse
Thanks for the quick reply. It says:
-Firmware-1.17-
Pyramid PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMMC-boot
Jun 2 2011,22:31:39

wmgamd said:
Thanks for the quick reply. It says:
-Firmware-1.17-
Pyramid PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMMC-boot
Jun 2 2011,22:31:39
Click to expand...
Click to collapse
Hi,
You are on GB.
Follow THIS THREAD in order to update your firmware and recovery.
Then, flash a new ROM.

malybru said:
Hi,
Follow THIS THREAD in order to update your firmware and recovery.
Then, flash a new ROM.
Click to expand...
Click to collapse
Thanks. Will do and keep you posted with the results.

Success. :good:
All I needed was the firmware update. My old ROM is back and working.
Thanks a million. you're a star.

wmgamd said:
Success. :good:
All I needed was the firmware update. My old ROM is back and working.
Thanks a million. you're a star.
Click to expand...
Click to collapse
how did you downgrade from hboot 1.29 to 1.17?

boyriot said:
how did you downgrade from hboot 1.29 to 1.17?
Click to expand...
Click to collapse
you can downgrade when you are on S-OFF

boyriot said:
how did you downgrade from hboot 1.29 to 1.17?
Click to expand...
Click to collapse
Hi, I used the same link in the begining of this post, added by malybru and downloaded the firmware 1.17 initially and flashed it. I then followed this link:
http://forum.xda-developers.com/showthread.php?t=1864053 (only the S-off section though as I've rooted and unlocked my phone earlier via HTCDev.com). Then I restored the backup.
when it didn't work as decribed in the begining of my post, I downloaded the newest firmware, but my mistake was that I left the old file (1.17) in the download folder on my pc which led to automatic addition of ''(1)'' to the end of the newest firmware file name. this led to the phone not seeing it as a firmware file and hence not using it.
When Malybru posted the same link, I had more confidence in the file and retried the file 1 more time and this time, I noted the change to the firmware name and corrected it. It all work like a charm.
Good luck.

rzr86 said:
you can downgrade when you are on S-OFF
Click to expand...
Click to collapse
but the OP said, he had to downgrade first before to be able to S-Off it.
so that mean, he was S-ON when downgrading right?

boyriot said:
but the OP said, he had to downgrade first before to be able to S-Off it.
so that mean, he was S-ON when downgrading right?
Click to expand...
Click to collapse
i just read again the OP
you are right
OP how did you downgrade while on S-ON?

rzr86 said:
i just read again the OP
you are right
OP how did you downgrade while on S-ON?
Click to expand...
Click to collapse
Sorry for the confusion. On careful recounting the steps I took, I did indeed S-off it first, using the link in my last post before being able to downgrade. The reason I downgraded was because when using the file PG58DIAG.nbh, I used to get an error msg about S-OFF, so I S-offed it but I kept getting the same error msg; so when researched online, I noticed that another cause for this error could be the wrong firmware so then I had to downgrade...
So I guess you're right rzr86.

Current ROM is not stable, unable to flash most of the roms via TWRP with S-Off

Ok, I'll start from the beginning.
I purchased my phone from Rogers at April 2012. So it was Rogers stock 4.0.x rom, everything was locked at that time. I FORGOT the stock hboot/ruu version number for Rogers ONE XL.
From the time being, I rooted it, superCID, unlocked via HTC DEV. After these, I flashed customer recovery, and successfully flashed several roms from time being. Finally I stayed with ViperXL.
Then, facepalm s-off is released, and I s-offed my phone. Everything worked just fine.
The problem occurred when I started to flash sense 5 roms about couple weeks ago. I did not upgrade my firmware and I flashed sense 5 based roms (this is my bad), so I'm experiencing random reboot and signal drops. Then I upgraded my firmware using the instruction in this tread: http://forum.xda-developers.com/showthread.php?t=2423735 . I verified my installtion with ./fastboot gervar all . At this time, there were two warnings on the top of my bootloader: "tampered" and "unlocked".
So, at this time, I tried several sense 5 roms. My recovery at this time was TWRP 2.6.3.0. All the roms have one common problem on my phone: after I locked the screen and left my phone for a while, if I wanna wake my phone/display, nothing happened by pressing the power button. I have to press the power button for 10+ seconds to restart my phone. If I just left my phone for a short time and wake it, it will work properly.
I was thinking are these sense 5 problems, so I tried to flash cm roms yesterday. I followed the instructions in http://forum.xda-developers.com/showthread.php?t=2382933 to upgrade my RUU to 3.18. I flashed TWRP 2.6.3.0, and tried to flash cm 10.1 and 10.2. For cm 10.2, there were a lot of force close when I boot my phone. For cm 10.1, it is so unstable with random reboots as well as did not respond when I try to wake up the phone. I am not questioning CM's roms, I am sure there were something wrong with my phone or what I've done to it.
So, I tried to flash viper rom again with ruu 3.18 installed. The rom won't even boot...... However I found something interesting when I am flashing the viper rom. The size of ViperXL is 700+ MB while the size of CM 10.1 or 10.2 is around 180MB. The time it took to flash ViperXL was shorter than the time it took to flash CM roms.
Then I re-installed the RUU 3.18 update on my phone. Right now, the AT&T stock rom also will not respond after I left my phone idle for a moment......
User timmaaa kindly reminds me about something. I am posting the original post I started in another tread.
Originally Posted by snake3276120 View Post
After I ran the RUU 3.18 upgrade in this tread: http://forum.xda-developers.com/show....php?t=2382933
I boot into bootloader, and ran fastboot getvar all, the result is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT246W304864
(bootloader) imei: 359691041684351
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4122mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I'm assuming "(bootloader) version-main: 3.18.502.6" is the RUU version. I also flashed an hboot 2.14, it became 3.17.xxxxxxx. That'w why I am assuming this is the RUU number.
Ok, regardless of the build number or ruu...... I think there is something wrong with my bootloader. It doesn't matter which hboot I flash (hboot 2.14 with version-main 3.17/3.18, or hboot 2.15 with version-main 5.08), and I tried several twrp (2.4.4.0 and 2.6.3.0). The time it took to flash viper xl is really short while viper xl has 700MB. It is even shorter than the time I flash CM, which is around 180 MB. (Sorry for the bad English, I actually mean "The size of ViperXL is 700+ MB while the size of CM 10.1 or 10.2 is around 180MB. The time it took to flash ViperXL was shorter than the time it took to flash CM roms.")
I guess I'll start with the current AT&T stock rom (which still lose respond after I left the phone open for a while, and I have to press the power button for 10 secs to reset my phone)on hboot 2.14 and ruu 3.18. Root it, try to s-off again. Not sure if this will solve the problem.
Something interesting when I'm booting my phone, when the phone displays only the green HTC in the middle of the display, there is some text below it... saying something like "This is an internal build, do not distribute outside of HTC, failure may cause to law action". However, the AT&T stock rom I'm running right now does not have this.
timmaaa:
It's a bit hard to follow what you're saying there but here goes. It's not the RUU number it's the build number. An RUU is the program that updates your phone, the reason you see them referred to as the 3.18 RUU is because they're known by the build number that they update your phone to.
Did you check the md5 of the downloaded file as someone else suggested? It might be corrupt. Also, maybe you should try TWRP 2.6, versions 2.4.x and 2.5.x are well known as being very buggy, and I've seen people have issues with version 2.6.3 too. 2.6 is rock solid though.
The red text you see when the phone boots up is completely normal for a modified phone so you needn't worry about that. The reason the stock ROM doesn't have it is because the RUU has returned your phone to being completely stock, therefore not modified, therefore no red text.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
OK, I am wondering where I can get my RUU number......
Also, in this case, what I should do now? Install TWRP 2.6.0.0 and try to flash everything again?
Currently "tampered" is gone from my bootloader, only "unlocked" stays there.

Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita

timmaaa said:
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
Click to expand...
Click to collapse
Because some posts are saying RUU 3.17 or 3.18, so I got confused...... but as long as it's a program, I will assume they are talking about the firmware or bootloader after running RUU 3.17 or 3.18 upgrade.

timmaaa said:
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
Click to expand...
Click to collapse
I fixed the qoute

Just to be clear, after you ran the 3.18 RUU you booted the phone without making any modifications and the problem was still occurring, right? It seems to me that it might be some kind of hardware problem that's causing a sleep of death every time the phone goes into sleep mode.
Sent from my Evita

timmaaa said:
Just to be clear, after you ran the 3.18 RUU you booted the phone without making any modifications and the problem was still occurring, right? It seems to me that it might be some kind of hardware problem that's causing a sleep of death every time the phone goes into sleep mode.
Sent from my Evita
Click to expand...
Click to collapse
That's right, I didn't even flash recovery... Well, my stock rom just self-rebooted, and stuck at booting animation while adb is still able to recognize it, and I can issue a reboot from adb. This also applies to my sense 5 roms.
If it's hardware problem, looks like upgrading to hboot 2.15 ruined my hardware, which is hard to believe...... Everything works fine before I upgrade my hboot to 2.15

Unfortunately it isn't under warranty anymore either.
Sent from my Evita

timmaaa said:
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
Click to expand...
Click to collapse
I know... it is unfortunate...

timmaaa said:
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
Click to expand...
Click to collapse
I upgraded my hboot to 2.15 and I flashed MaginRom 4.0. At least it's booting...... looks like my recovery hates aroma installer.

snake3276120 said:
I upgraded my hboot to 2.15 and I flashed MaginRom 4.0. At least it's booting...... looks like my recovery hates aroma installer.
Click to expand...
Click to collapse
Confirm your hboot and baseband version and post here. You said it upgraded, but let's make sure it actually was completely successful.
Also, I think TWRP 2.6.3 has some bugs, not sure if AROMA is one of them. You might check the TWRP thread. But I believe other 2.6.x versions are very stable. I've been on 2.6.0 for a while, and everything seems to be working great, and don't remember any bug reports on that version.

Yeah I can confirm I've seen folks with bugs on 2.6.3 but I've been using 2.6 for months and not a single problem (and no reports of bugs from others).
Sent from my Evita

timmaaa said:
Yeah I can confirm I've seen folks with bugs on 2.6.3 but I've been using 2.6 for months and not a single problem (and no reports of bugs from others).
Sent from my Evita
Click to expand...
Click to collapse
I used 2.6.0.0 to flash my current magiorom 4..... well at least it is usable now, with app/sense/notification bar/wake phone do not respond sometimes... I'm not blaming the rom, I am blaming my phone... probably now it's the time to get a new one lol

redpoint73 said:
Confirm your hboot and baseband version and post here. You said it upgraded, but let's make sure it actually was completely successful.
Also, I think TWRP 2.6.3 has some bugs, not sure if AROMA is one of them. You might check the TWRP thread. But I believe other 2.6.x versions are very stable. I've been on 2.6.0 for a while, and everything seems to be working great, and don't remember any bug reports on that version.
Click to expand...
Click to collapse
Here you are, boss.
PS E:\Program Files (x86)> cd '.\Minimal ADB and Fastboot'
PS E:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3874mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
PS E:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
I think the result is the same in thread http://forum.xda-developers.com/showthread.php?t=2423735
Quoted from the thread:
Install:
Installing the rom:
Download the rom and copy to your sdcard
Reboot to Recovery
Flash rom
I recommend you wipe data before or after flashing the rom
For root access, flash this: Flash this in recovery for root access
Reboot
OPTIONAL: Installing the Firmware (Warning: You MUST be S-OFF and Super CID to flash this! Flash at own risk!)
Reboot to bootloader (adb reboot bootloader if "USB Debugging" is enabled in Android)
Run: fastboot oem rebootRUU
Run: fastboot flash zip <PathToFirmware.zip>
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command AGAIN
If it ends with "INFO..... OK", reboot to the bootloader: fastboot reboot-bootloader
Verify everything was successful by running: fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4140mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Reboot into Android: fastboot reboot or into recovery: fastboot reboot-recovery
Click to expand...
Click to collapse
Please refer to the attachment for a photo of my bootloader

Will TWRP 2.3.3.0 solve my problem? It looks like most roms recommend this recovery.... btw I'm running 2.6.0.0 at the moment.

No, changing TWRP won't solve your problem. You said you're using TWRP 2.6 now and that version is fine. I'd suggest trying one more time to do a clean flash, so wipe cache/dalvik cache/factory reset/system and install the ROM. Hell, do the wipe two or three times to be sure before installing.
Sent from my Evita

timmaaa said:
No, changing TWRP won't solve your problem. You said you're using TWRP 2.6 now and that version is fine. I'd suggest trying one more time to do a clean flash, so wipe cache/dalvik cache/factory reset/system and install the ROM. Hell, do the wipe two or three times to be sure before installing.
Sent from my Evita
Click to expand...
Click to collapse
lol thanks... Every time before I flash a new rom, I just format everything...

I don't know what to tell you then. There's nothing wrong with the ROMs you're using so it's either a case of user error or hardware failure of some kind.
Sent from my Evita

timmaaa said:
I don't know what to tell you then. There's nothing wrong with the ROMs you're using so it's either a case of user error or hardware failure of some kind.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for all the help... I think it is hardware error... because I'm an electrical/computer engineer, I don't think I can't even handle flashing roms... Maybe I need to do more research lol
One XL is a nice phone, I don't wanna switch yet...

snake3276120 said:
Thanks for all the help... I think it is hardware error... because I'm an electrical/computer engineer, I don't think I can't even handle flashing roms... Maybe I need to do more research lol
One XL is a nice phone, I don't wanna switch yet...
Click to expand...
Click to collapse
Could you also try one last thing? Could you upgrade your twrp to latest release and try flashing cm 10.2 0310 nightly please.
Sent from my One X using Tapatalk 4

sandys1 said:
Could you also try one last thing? Could you upgrade your twrp to latest release and try flashing cm 10.2 0310 nightly please.
Sent from my One X using Tapatalk 4
Click to expand...
Click to collapse
Ok I'll do a backup and try tonight....latest twrp do u mean 2.6.3.0, or there is another new release?

[Q]

I have HTC One X- AT&T(Evita) With S4 processor. In fastboot, First three Lines are:
Tempered
Locked
S off
I went through complete process, mentioned at HTC devs, but un-successful. the following error occured:
Error 160
MID not allowed
I have to change CID, but for doing this, i must have root access.
Please anybody guide me step by step procedure to root/bootloader unlock?

You don't need root access, because you have s-off. You can simply use fastboot to change the CID to SuperCID.
Code:
fastboot oem writecid 11111111
Next time, do a bit of research before creating a thread. Pretty much every question you could think of asking has been asked, and answered within our forum. Check out all of the links in my signature, almost everything you'll ever need can be found there.
Sent from my Evita

Again Question sir
I have HTC One X- AT&T(Evita) With S4 processor. In fastboot, First three Lines are:
Tempered
Locked
S ON
I went through complete process, mentioned at HTC devs, but un-successful. the following error occured:
Error 160
MID not allowed
I have to change CID, but for doing this, i must have root access.
Please anybody guide me step by step procedure to root/bootloader unlock?[/QUOTE]

jezi251 said:
I have HTC One X- AT&T(Evita) With S4 processor. In fastboot, First three Lines are:
Tempered
Locked
S ON
I went through complete process, mentioned at HTC devs, but un-successful. the following error occured:
Error 160
MID not allowed
I have to change CID, but for doing this, i must have root access.
Please anybody guide me step by step procedure to root/bootloader unlock?
Click to expand...
Click to collapse
The at&t CID is blocked at htcdev, so you need to get SuperCID in order to unlock your bootloader. Reading the stickied threads (specifically the Evita FAQ thread) in the section you've just posted in world have uncovered this information. You're gonna want to read all of the threads in my signature so you can familiarise yourself with this device, and so you don't ask a question that's already been asked and answered a million times before.
Please post your hboot version, you'll find that in your bootloader screen.
You said earlier that you have s-off, why it s-on now?
Sent from my Evita

Evita pvt ship s-on
HBOOT-2.14.0000
Earlier mistaken s off written
Sent from my HTC One X using Tapatalk

Have you read the threads I mentioned?
Sent from my Evita

First I have to root it for cid change whts the procedure in this situation??
Sent from my HTC One X using Tapatalk

You need to use the 3.18 root method. Full instructions in my How-To Guide For Beginners thread.
Sent from my Evita

recovery
when i follow the procedure of rooting...when it goes to recovery screen (white one) its wait for 5 to 8 seconds and then restart normally..i can't goto recovery ..why??

That doesn't really make sense. The recovery screen isn't white, are you talking about the bootloader? And can you please be more specific about what's happening? I can't help you if you're giving vague two sentence posts like that.
Sent from my Evita

twrp
when i install twrp 2.7..after enter the recovery mode white htc scree appears...when i install twrp 2.2.0..on recovery it opens but touch screen don't works no button works just power button works which locks the twrp...can u send me valid link of twrp 2.7 because at twrp website at 99% downloading stops...

Why did you flash 2.7 if it didn't download completely? That's a surefire way to brick your phone. The md5 wouldn't have matched either. You'll find downloads here:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita

details of my evita
timmaaa said:
Why did you flash 2.7 if it didn't download completely? That's a surefire way to brick your phone. The md5 wouldn't have matched either. You'll find downloads here:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.24p.32.09.06
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: HT26GW303783
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4141mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a06e
hbootpreupdate: 11
gencheckpt: 0
can i update my jb to 4.3??how?

jezi251 said:
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.24p.32.09.06
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: HT26GW303783
imei: xxxxxxxxxxxxxxxx
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4141mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a06e
hbootpreupdate: 11
gencheckpt: 0
can i update my jb to 4.3??how?
Click to expand...
Click to collapse
First thing you need to do is edit your IMEI out of that post, never post your IMEI publicly. It looks like you've successfully gotten s-off now too which is good. What kind of ROM do you want?
Sent from my Evita

rom
timmaaa said:
First thing you need to do is edit your IMEI out of that post, never post your IMEI publicly. It looks like you've successfully gotten s-off now too which is good. What kind of ROM do you want?
Sent from my Evita
Click to expand...
Click to collapse
i want that rom which works perfectly not issue of baseband,network ...etc...can u suggest me correct rom regarding to my specifications..now i upgraded my hboot to 2.15..

jezi251 said:
i want that rom which works perfectly not issue of baseband,network ...etc...can u suggest me correct rom regarding to my specifications..now i upgraded my hboot to 2.15..
Click to expand...
Click to collapse
I actually meant do you want a Sense ROM or an aosp ROM? Asking which ROM is best/most stable/fastest/prettiest, or asking for a suggestion isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Our dev sections are as follows:
One XL Android Development (mainly Sense ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development (aosp ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1726
Have a look through the available ROMs and pick one you think will suit you.
Sent from my Evita

evita
thanks buddy

recovery
jezi251 said:
thanks buddy
Click to expand...
Click to collapse
i want to update my recovery from 2.7.0.0 to 2.7.1.0..when i insert fastboot flash recovery openrecovery-twrp-2.7.1.0 in CMD
error:cannot open 'openrecovery-twrp-2.7.1.0'...
because i want to install A.P rom or carbon or candy cat..
justnow i have 4.1.1 stock version,s-off,tempered, hboot 2.15
help me!!
when i try to install any rom by twrp 2.7.0.0 it gives error ..only cm11 snapshot installs but sometimes it hangs ...so i restore to 4.1.1...

Is that the exact command you're giving? It looks like you're missing the ".zip" on the end of the filename. For example, if the filename is "openrecovery-twrp-2.7.1.0.zip" then the command should look like this:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.0.zip
If you have filename extensions (.exe, .doc, .zip) turned off in Windows, this could be the reason why you're missing the extension from the command.
Sent from my Evita

recovery
timmaaa said:
Is that the exact command you're giving? It looks like you're missing the ".zip" on the end of the filename. For example, if the filename is "openrecovery-twrp-2.7.1.0.zip" then the command should look like this:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.0.zip
If you have filename extensions (.exe, .doc, .zip) turned off in Windows, this could be the reason why you're missing the extension from the command.
Sent from my Evita
Click to expand...
Click to collapse
i have also tried with .zip ext but it not works