Database Info

[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.

Any stable roms on xda......

Admin, please remove/delete this tread, I am starting a new one to fully address my issue...... Sorry about the inconvenience.

Running magio sense 5... Stable as they get. Sounds like you have other issues if you can't get viperxl to boot. What recovery version do you use?
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
Running magio sense 5... Stable as they get. Sounds like you have other issues if you can't get viperxl to boot. What recovery version do you use?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
twrp 2.6.3.0. The viper rom is always good at android 4.1. When I upgrade my hboot to 2.15, viper rom for sense 5 still work, it's just not stable. After I upgraded to RUU 3.18 today, viper rom doesn't even boot.

Have you wiped everything before flashing?
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
Have you wiped everything before flashing?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I did...... wipe data, cache, system, dev cache

For hahas I just flashed viper on 2.15 hboot and it's working fine
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
For hahas I just flashed viper on 2.15 hboot and it's working fine
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you RUU 3.18?

Yes I ruu to 3.18 a while back, to play with the new cm roms. Now I'm using the 4.2.2 hboot (2.15 and the 3.18 radio)
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
Yes I ruu to 3.18 a while back, to play with the new cm roms. Now I'm using the 4.2.2 hboot (2.15 and the 3.18 radio)
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sigh, I'll see what I can do

I'd start over with ruu. And double manual wipe everything before install, after flash wipe cache n dalvik. And factory reset in twrp before first boot.
And verify md5 on rom your flashing, it would suck if your glitches are from a slightly corrupt download.
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
I'd start over with ruu. And double manual wipe everything before install, after flash wipe cache n dalvik. And factory reset in twrp before first boot.
And verify md5 on rom your flashing, it would suck if your glitches are from a slightly corrupt download.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just RUU to 3.18 and flashing hboot 2.15 right now...I will check md5 on the rom. Thanks for all the advise.

snake3276120 said:
I just RUU to 3.18 and flashing hboot 2.15 right now...I will check md5 on the rom. Thanks for all the advise.
Click to expand...
Click to collapse
after I flash hboot 2.15, the ruu becomes 5.08.111.2 ......

I think you're getting your terminology mixed up, do you mean the build number becomes 5.08.111.2?
Sent from my Evita

timmaaa said:
I think you're getting your terminology mixed up, do you mean the build number becomes 5.08.111.2?
Sent from my Evita
Click to expand...
Click to collapse
After I ran the RUU 3.18 upgrade in this tread: http://forum.xda-developers.com/showthread.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.
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.

snake3276120 said:
After I ran the RUU 3.18 upgrade in this tread: http://forum.xda-developers.com/showthread.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.
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.
Click to expand...
Click to collapse
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.
Sent from my Evita

timmaaa said:
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.
Sent from my Evita
Click to expand...
Click to collapse
Sorry for my broken English, and thanks for the reply...... I will start another tread to fully address my problem.

There's no need to start another thread, you're already getting help in here. The threads don't just get deleted, creating a new one just means you're duplicating the post which is unnecessary.
Sent from my Evita

timmaaa said:
There's no need to start another thread, you're already getting help in here. The threads don't just get deleted, creating a new one just means you're duplicating the post which is unnecessary.
Sent from my Evita
Click to expand...
Click to collapse
Sigh,I have already started a new one... Please take a look at http://forum.xda-developers.com/showthread.php?p=46229767#post46229767

So to summarize and to be clear: It turns out the OP is having some issues possibly due to updating hboot, and not problems with the stability of the ROMs themselves.
I know the OP deleted the content in the top post and started another thread (which is in itself not the right way to go about things). But it was in pretty bad style to title this thread the way it is, and imply that the ROMs are unstable, when you don't even know what the root cause of the problems is. If you have flashed several ROMs, and having the same issue on all, its most probable the problem is not with the ROMs, but with something you did (or didn't do), or else a hardware issue.

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?

[Resolved] Problems updating X920d Android 4.3 version 3.15.707.4 from 2.33.707.3

Resolved!
Apparently it was due to the fact that I installed Xposed Framework that causes the update process to fail.
I try to manually update the OTA.zip via stock recovery and found out that the process stopped at
"assert failed apply_patch_check( /system/bin/app_process."
Click to expand...
Click to collapse
Further checks showed that Xposed replaced the app_process file and causes it to fail checksum. I then copied /system/bin/app_process.orig back to /system/bin/app_process.
After that, the update was a breeze. The recovery used was from 3.15.707.4 (extracted from OTA.zip).
I've also S-OFF and Super-CID during my testing process.
If your update process stops after 25%, usually some checksum error has happened. Use manual update to determine the error message.
________________________________________________________________________
I'm having a problem updating my Butterfly to Android 4.3 from 4.2.2
My current firmware is 2.33.707.3 and the upgrade version is 3.15.707.4.
On my current phone, I have unlock my bootloader, flash recovery to TWRP 2.6.3.0 as well as rooted it. Due to inexperience, I did not backup my original recovery.
As per gleamed from this forum, I've tried to flash recovery from other stock ROM to proceed with the OTA update.
Steps taken:
Clicked Install now on the OTA message
Phone reboots to recovery
Phone icon with Green exclamation mark appears
Bottom part blue progress bar appears
Upon 30 to 40% progress, the screen changes to Red exclamation mark and update is stopped.
Edit: Did a Factory reset, problem remains.
I've tried the following recovery from other stock ROM without success.
Recovery from 3.15.707.4 (extracted OTA zip in phone's Download folder)
Recovery from 1.19.707.1 (extracted from DLXB1_U_JB_45_hTC_Asia_WWE_1.19.707.1_V0.0)
Recovery from 2.28.709.2 (extracted from OTA_DLXB1_U_JB_50_S_hTC_Asia_TW_2.28.709.2-1.18.709.3)
Recovery from 1.12.707.1
Recovery from 2.33 (from @Bassie39's OTA collection)
Recovery from 2.28.709.3
I've searched high and low for stock Recovery from 2.33.707.3 but unable to locate it.
Any tips or suggestion apart from S-OFF and update firmware, PL99img.zip update via bootloader, look in the OTA collection?
Code:
Model: Butterfly x920d
Android Version: 4.2.2
HTC Sense: 5.0
Software number: 2.33.707.3
CID: 044
[I][B]Bootloader Menu[/B][/I]
*** TAMPERED ***
*** UNLOCKED ***
DELUXE_UB1 PVT SHIP [B]S-ON[/B] RH
[B]HBOOT-1.54.0000[/B]
RADIO-3A.28.306.09
OpenDSP-V10.120.274.0520
[B]OS-2.33.707.3[/B]
eMMC-boot 2048MB
Aug 16 2013
[B][I]Fastboot getvar all results[/I][/B]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 3A.28.306.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.33.707.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: x
(bootloader) imei: x
(bootloader) meid: x
(bootloader) product: deluxe_ub1
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL9911000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3856mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0c6295fdaf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
A list of posts with the same problem:
[Q] Help In Updating To 4.3 - Unsolved
Followed @bluheart suggestion - Not working

Try this buddy
Do everything as written.

bluheart said:
Try this buddy
Do everything as written.
Click to expand...
Click to collapse
@bluheart, How do I go from S-OFF to update my OTA? Is Rumrunner better?

Any help or advice would be very appreciated.
Sent from my HTC Butterfly using Tapatalk

Firewater or Rumrunner are equally effective.
I liked Firewater as its very simple to use.

What's the next step after having S-Off?
Sent from my HTC Butterfly using Tapatalk

kemikelx said:
What's the next step after having S-Off?
Sent from my HTC Butterfly using Tapatalk
Click to expand...
Click to collapse
Super cid
Sent from my HTC Butterfly s using XDA Premium 4 mobile app

After supercid flash the TW (Taiwan) firmware not the WWE (World Wide Edition) so that you get faster updates as this is a Taiwanese company. WWE gets updates a lot later (2-4 months later) so think about that.

abhinav.tella said:
After supercid flash the TW (Taiwan) firmware not the WWE (World Wide Edition) so that you get faster updates as this is a Taiwanese company. WWE gets updates a lot later (2-4 months later) so think about that.
Click to expand...
Click to collapse
Yes, This means I have to change the CID to HTC__621? But would this affect my Carrier settings?

kemikelx said:
Yes, This means I have to change the CID to HTC__621? But would this affect my Carrier settings?
Click to expand...
Click to collapse
No, I have done this with my old Butterfly without any bad effects or signal problems.

bluheart said:
Firewater or Rumrunner are equally effective.
I liked Firewater as its very simple to use.
Click to expand...
Click to collapse
Firewater didn't work. Instead I used Rumrunner.

Hope things worked out, and also I hope you took my advice and switched to Taiwan RUU.
You don't have to change CID if you are supercid which is 11111 something like that, you can install any RUU.
Sent from my LG-LS980 using XDA Premium 4 mobile app

abhinav.tella said:
Hope things worked out, and also I hope you took my advice and switched to Taiwan RUU.
You don't have to change CID if you are supercid which is 11111 something like that, you can install any RUU.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm trying to find a way to install the Taiwanese RUU on my phone. Looking around this forum but some of the instructions are contradictory.
Any help or useful links to share?

kemikelx said:
I'm trying to find a way to install the Taiwanese RUU on my phone. Looking around this forum but some of the instructions are contradictory.
Any help or useful links to share?
Click to expand...
Click to collapse
Go to the unlock thread page 9, I posted a detailed S-Off procedure. Any further questions regarding TW firmware they can answer.

Questions about installing downgraded custom rom

Hi guys, I'm new to installing custom roms. I've been reading for countless hours on the process before I attempt to install one. Here's where I'm at.
Phone: Verizon HTC One m8
1) Used Sunshine to get unlocked bootloader & S-OFF
2) I downloaded all OTA updates
3) Then flashed TWRP 3.0.2.0 and rooted with superSU
4) I immediately made a nandroid backup using TWRP
My phone's current state is working fine on stock rom.
Android 6.0
Sense 7.0
Here's my getvar all output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.14.20.0930
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.21.605.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXX
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I want to install Android Revolution HD
I downloaded Android Revolution HD 53.1 which is Marshmallow (Android 6.0.0 + HTC Sense 7.0) according to their site.
I made one attempt to install that rom but it didn't work. Here's what I did:
1) Copied the rom zip to my sdcard
2) Entered recovery (TWRP)
3) Performed a Wipe in TWRP (default wipe settings)
4) Clicked Install, selected the Android Revolution zip.
The install screen came up, I went through the dialog and selected which apps I wanted to be installed in ARHD, and the install went through and eventually said Success. I rebooted the phone and was stuck in bootloop. So I restored to my nandroid backup and haven't tried again since.
I have read and re-read their instructions and am still not sure what I'm missing. Any help is greatly appreciated, and if you need any info just let me know. Thanks!

jdub55 said:
Hi guys, I'm new to installing custom roms. I've been reading for countless hours on the process before I attempt to install one. Here's where I'm at.
Phone: Verizon HTC One m8
1) Used Sunshine to get unlocked bootloader & S-OFF
2) I downloaded all OTA updates
3) Then flashed TWRP 3.0.2.0 and rooted with superSU
4) I immediately made a nandroid backup using TWRP
My phone's current state is working fine on stock rom.
Android 6.0
Sense 7.0
Here's my getvar all output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.14.20.0930
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.21.605.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXX
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I want to install Android Revolution HD
I downloaded Android Revolution HD 53.1 which is Marshmallow (Android 6.0.0 + HTC Sense 7.0) according to their site.
I made one attempt to install that rom but it didn't work. Here's what I did:
1) Copied the rom zip to my sdcard
2) Entered recovery (TWRP)
3) Performed a Wipe in TWRP (default wipe settings)
4) Clicked Install, selected the Android Revolution zip.
The install screen came up, I went through the dialog and selected which apps I wanted to be installed in ARHD, and the install went through and eventually said Success. I rebooted the phone and was stuck in bootloop. So I restored to my nandroid backup and haven't tried again since.
I have read and re-read their instructions and am still not sure what I'm missing. Any help is greatly appreciated, and if you need any info just let me know. Thanks!
Click to expand...
Click to collapse
If I'm reading the op correctly I don't think that rom is compatible with the Verizon m8
Sent from my HTC One M8 using XDA Labs

jurington said:
If I'm reading the op correctly I don't think that rom is compatible with the Verizon m8
Click to expand...
Click to collapse
Ah shoot. I must have overlooked that. Okay, then how about this Verizon Stock Rooted rom?
Here's the thing. I really want a debloated rom. I'm not picky. It would be nice to get a stable custom rom that supports ART and is debloated. But I'm a bit confused.
It seems most of the stable roms are running Lollipop. Does this mean I need to downgrade somehow? Can I flash firmware, or do I need to do a actual factory reset? Please clarify this part, I think this is where I'm most confused at the moment.

jdub55 said:
Ah shoot. I must have overlooked that. Okay, then how about this Verizon Stock Rooted rom?
Here's the thing. I really want a debloated rom. I'm not picky. It would be nice to get a stable custom rom that supports ART and is debloated. But I'm a bit confused.
It seems most of the stable roms are running Lollipop. Does this mean I need to downgrade somehow? Can I flash firmware, or do I need to do a actual factory reset? Please clarify this part, I think this is where I'm most confused at the moment.
Click to expand...
Click to collapse
So for the most part just stay on marshmallow firmware. Everything I believe is compatible with it. And I'm running viper rom right now and it's pretty amazing. But just look in the Verizon m8 development and original development and you'll find roms that are compatible with it.
Sent from my HTC One M8 using XDA Labs

jurington said:
So for the most part just stay on marshmallow firmware. Everything I believe is compatible with it. And I'm running viper rom right now and it's pretty amazing. But just look in the Verizon m8 development and original development and you'll find roms that are compatible with it.
Sent from my HTC One M8 using XDA Labs
Click to expand...
Click to collapse
Oh okay. I actually already downloaded ViperOneM8 6.0.0 from their website. Is it safe to say I can perform a Wipe in TWRP, and then install the Viper rom and I should be good?
Also, just to clarify: I don't need to flash any firmware.zip?
Thanks so much.

jdub55 said:
Oh okay. I actually already downloaded ViperOneM8 6.0.0 from their website. Is it safe to say I can perform a Wipe in TWRP, and then install the Viper rom and I should be good?
Also, just to clarify: I don't need to flash any firmware.zip?
Thanks so much.
Click to expand...
Click to collapse
If you're already on the latest ota then you're good to go. And it'll have you perform a wipe through the aroma installer so no need to wipe before hand. And it's pretty slick, I just flashed it this morning and I'm liking it so far.
Sent from my HTC One M8 using XDA Labs

jurington said:
If you're already on the latest ota then you're good to go. And it'll have you perform a wipe through the aroma installer so no need to wipe before hand. And it's pretty slick, I just flashed it this morning and I'm liking it so far.
Click to expand...
Click to collapse
Thanks, I'm now running ViperOne!
I'm noticing a couple issues though:
1) The HTC Calendar app won't sync with my Google account. And my Google account isn't showing in the "Accounts" setting in Calendar. (I opted to not install Google Calendar during the rom install, but opted to install HTC Calendar)
2) None of the photos I've taken after installing V1 work with uFocus. I don't know if it's an issue with uFocus, or the dual lens. But when I go to edit a photo I took, I go into uFocus, and it says "Tap anywhere to adjust focus", but it doesn't matter where I tap, it doesn't adjust anything. Also, when taking a photo it doesn't tell me if my finger is blocking the 2nd lens. It will take the shot anyway, and if the 2nd lens was blocked, it will simply deny going into uFocus for that shot.
3) Is there any way to hide the Boomsound notification when playing audio?
If I can resolve these issues I can see myself sticking with this rom for a long time

jdub55 said:
Thanks, I'm now running ViperOne!
I'm noticing a couple issues though:
1) The HTC Calendar app won't sync with my Google account. And my Google account isn't showing in the "Accounts" setting in Calendar. (I opted to not install Google Calendar during the rom install, but opted to install HTC Calendar)
2) None of the photos I've taken after installing V1 work with uFocus. I don't know if it's an issue with uFocus, or the dual lens. But when I go to edit a photo I took, I go into uFocus, and it says "Tap anywhere to adjust focus", but it doesn't matter where I tap, it doesn't adjust anything. Also, when taking a photo it doesn't tell me if my finger is blocking the 2nd lens. It will take the shot anyway, and if the 2nd lens was blocked, it will simply deny going into uFocus for that shot.
3) Is there any way to hide the Boomsound notification when playing audio?
If I can resolve these issues I can see myself sticking with this rom for a long time
Click to expand...
Click to collapse
The first two issues are known about, and I don't know if it can be fixed since its a port from the HTC 10 and it's a completely different base than the m8 and if you follow the main thread and the Verizon for viper you see if there can be a fix. And I haven't looked hard to see if I can hide that dialogue but if I do I will definitely let you know.
Sent from my HTC One M8 using XDA Labs