Database Info

Problem installing ADRH 6.7.0

Hey, I have a Sensation 4g, I was running ARHD version 3, on 2.3.4 android, I installed that around febraury.
Now I wanted to install the latest Android Revolution HD 6.7.0, I did everything as the list suggested I update the firmware( PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100). But when I install the rom everything goes as normal except that when I reboot in never boots into the rom, I have leave it over 20 mins, and nothing happens, I have tried several times, and I tried to restore back to version 3, everything seems "Restored" except it won't pass from htc logo again (I think it's because I have an updated firmware)
So, how do I manage to install the lasted arhd , or how do I do to downgrade the firmware in order to have it working again, I would prefer to have ICS, but I can't manage to do it, Please help, as my phone is unusable now.
thanks

dcuchillas said:
Hey, I have a Sensation 4g, I was running ARHD version 3, on 2.3.4 android, I installed that around febraury.
Now I wanted to install the latest Android Revolution HD 6.7.0, I did everything as the list suggested I update the firmware( PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100). But when I install the rom everything goes as normal except that when I reboot in never boots into the rom, I have leave it over 20 mins, and nothing happens, I have tried several times, and I tried to restore back to version 3, everything seems "Restored" except it won't pass from htc logo again (I think it's because I have an updated firmware)
So, how do I manage to install the lasted arhd , or how do I do to downgrade the firmware in order to have it working again, I would prefer to have ICS, but I can't manage to do it, Please help, as my phone is unusable now.
thanks
Click to expand...
Click to collapse
Nice detailed description of what exactly is going on, we need more people like you on sensation forum (no i'm not being sarcastic, I'm just glad you have given clear, detailed description instead of crap like I read in other posts "help my phone wont boot" and no other details - sorry, rant over )
By the looks of it, I'm guessing you didnt super wipe when upgrading to lastest ROM version? when coming from GB ROM to ICS you need to do a full/super wipe otherwise phone wont boot.

Jonny said:
Nice detailed description of what exactly is going on, we need more people like you on sensation forum (no i'm not being sarcastic, I'm just glad you have given clear, detailed description instead of crap like I read in other posts "help my phone wont boot" and no other details - sorry, rant over )
By the looks of it, I'm guessing you didnt super wipe when upgrading to lastest ROM version? when coming from GB ROM to ICS you need to do a full/super wipe otherwise phone wont boot.
Click to expand...
Click to collapse
Hey thanks, if you are referring to the super wipe script they provide , I have ran it everytime I tried on installing

dcuchillas said:
Hey thanks, if you are referring to the super wipe script they provide , I have ran it everytime I tried on installing
Click to expand...
Click to collapse
Use 4ext touch recovery. Format everything except sd card.
Sent from my HTC Sensation 4G using xda premium

cameljockey1 said:
Use 4ext touch recovery. Format everything except sd card.
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
I am indeed using 4ext, I have done as you said with no results. I am using a 4ext 1.0.0.2 and the latest is 0.4 or 0.5, I don't know if that really affects on something.
The phone just stays on the htc quietly brilliant logo.

Does Arhd 6.7.0 have sense 3.6.Do I need to update my.firmware to3.33 or will 3.32 work alright. Thanks...
Sent from my HTC Sensation 4G with Beats Audio using xda app-developers app

dcuchillas said:
I am indeed using 4ext, I have done as you said with no results. I am using a 4ext 1.0.0.2 and the latest is 0.4 or 0.5, I don't know if that really affects on something.
The phone just stays on the htc quietly brilliant logo.
Click to expand...
Click to collapse
I remember seeing the exact issue when installing ARHD 6.6.3 for the first time. What I did is just updated the firmware and tried booting to the old stock rom. So this seems to be due to an unmatched firmware. Is that 3.33 firmware u used?

jyo1 said:
I remember seeing the exact issue when installing ARHD 6.6.3 for the first time. What I did is just updated the firmware and tried booting to the old stock rom. So this seems to be due to an unmatched firmware. Is that 3.33 firmware u used?
Click to expand...
Click to collapse
hey, thanks. I did updated the firmware as it stated on the guide, and that would make my firmware unlocked, I was on 2.32. I don't know if that's you're referring with the updating firmware, if there is another way that I can try let me know.
Also, would you suggest that trying to install other rome would solve this?
thanks

reflash the firmware again ..then 4EXT -> format all partitions except sdcard then flash the ROM again

ganeshp said:
reflash the firmware again ..then 4EXT -> format all partitions except sdcard then flash the ROM again
Click to expand...
Click to collapse
you wouldn't believe how many times I have done that, I am beginning to worry that my phone would be unusable.. :crying:

dcuchillas said:
hey, thanks. I did updated the firmware as it stated on the guide, and that would make my firmware unlocked, I was on 2.32. I don't know if that's you're referring with the updating firmware, if there is another way that I can try let me know.
Also, would you suggest that trying to install other rome would solve this?
thanks
Click to expand...
Click to collapse
Definitely won't suggest flashing an unmatched ROM! That was a silly thing i did, to know what will happen if the firmware doesn't match.

dcuchillas said:
you wouldn't believe how many times I have done that, I am beginning to worry that my phone would be unusable.. :crying:
Click to expand...
Click to collapse
ohh you are still stuck ..and somehow ive missed it ( i forgot to subscribe to this thread :silly
ok
shall we go by step by step ?
1.can you post the bootloader details (complete stuff present in the bootloader ...a screen shot of it would do too )
2.if you can use adb/fastboot ..and have them installed already
can you please connect the phone in fastboot/bootloader to pc (phone reads "fastboot usb" after that )
then post the complete output of this below command
(except IMEI and serial number)
fastboot getvar all
3. check the md5 of the ARHD rom you have downloaded ...and verify it against the one given in the thread ...just below the download button it will be there (in general)
(md5sum can be done via 4EXT recover itself ... 4EXT -> install from sdcrad -> calculate/check md5)

Maybe he flashed from GB to 3.33?

cashman0712 said:
Maybe he flashed from GB to 3.33?
Click to expand...
Click to collapse
yeah maybe ..to confirm that only im asking him to give the bootloader details

[Q] Jelly Bean?

Is there a jelly bean based rom or CM10 for the inspire? I can't seam to find one and my brother would like to try one out if possible?

GTDarthYoda said:
Is there a jelly bean based rom or CM10 for the inspire? I can't seam to find one and my brother would like to try one out if possible?
Click to expand...
Click to collapse
The Inspire 4G is very similar to the Desire HD and can use the Desire HD ROMs. In the Desire HD Development forums, there are several JB ROMs. randomblame has a CM and an AOKP (AOKP is less updated), and synergye has CM and codefireX (CM with many extra settings/features).

bananagranola said:
The Inspire 4G is very similar to the Desire HD and can use the Desire HD ROMs. In the Desire HD Development forums, there are several JB ROMs. randomblame has a CM and an AOKP (AOKP is less updated), and synergye has CM and codefireX (CM with many extra settings/features).
Click to expand...
Click to collapse
Seen stuff about different radios? Is there something I'll need to flash?

GTDarthYoda said:
Seen stuff about different radios? Is there something I'll need to flash?
Click to expand...
Click to collapse
If you are happy with how your radio works, I would not recommend flashing a new one. You don't need to flash a new one just for JB.
Be warned that you might encounter a problem with the ROM staying in the splash screen after flashing the newest kernel for the first time. Don't panic, it's very easily fixed; if you see it after flashing JB, come back here. (Or you could look for the only thread I've opened, concerning an ADSP firmware update.)

bananagranola said:
If you are happy with how your radio works, I would not recommend flashing a new one. You don't need to flash a new one just for JB.
Be warned that you might encounter a problem with the ROM staying in the splash screen after flashing the newest kernel for the first time. Don't panic, it's very easily fixed; if you see it after flashing JB, come back here. (Or you could look for the only thread I've opened, concerning an ADSP firmware update.)
Click to expand...
Click to collapse
are they talking about the fm radio thingy?
nevered used it so nvm

GTDarthYoda said:
are they talking about the fm radio thingy?
nevered used it so nvm
Click to expand...
Click to collapse
No, I think you're referring to people talking about updating the phone's firmware for accessing mobile data and networks in general. Usually, if your reception is working fine, let your radio be.

alright I feel like an idiot >.<
How do you flash a new rom for this device
Edit: nvm looks like I missed a step in the hackkit

GTDarthYoda said:
alright I feel like an idiot >.<
How do you flash a new rom for this device
Click to expand...
Click to collapse
It's the same as any other device. Backup, download the ROM, boot into recovery, full wipe, flash in recovery, reboot. If you're S-ON, there's an additional step required in fastboot. Check the PDF in post #7 in the link in my signature for more detailed instructions.
EDIT: sorry, I assumed you were rooted.

bananagranola said:
It's the same as any other device. Backup, download the ROM, boot into recovery, full wipe, flash in recovery, reboot. If you're S-ON, there's an additional step required in fastboot. Check the PDF in post #7 in the link in my signature for more detailed instructions.
EDIT: sorry, I assumed you were rooted.
Click to expand...
Click to collapse
working on that >.<

Well **** I could be in trouble here... I can't seem to boot the phone now >.<

GTDarthYoda said:
Well **** I could be in trouble here... I can't seem to boot the phone now >.<
Click to expand...
Click to collapse
AAHK comes with a very detailed manual. Did you read it? What happened? Did your phone ship with Gingerbread? Did you need to downgrade? Can you get into HBOOT? If so, what does it say?

bananagranola said:
AAHK comes with a very detailed manual. Did you read it? What happened? Did your phone ship with Gingerbread? Did you need to downgrade? Can you get into HBOOT? If so, what does it say?
Click to expand...
Click to collapse
Well I following the instructions here because my brother updated to the latest and lost root. After I finished that which everything seemed to work, it said to run the aahk, so I did and after it was done... nothing...
I can get into hboot, and it does say i'm s-off

GTDarthYoda said:
Well I following the instructions here because my brother updated to the latest and lost root. After I finished that which everything seemed to work, it said to run the aahk, so I did and after it was done... nothing...
I can get into hboot, and it does say i'm s-off
Click to expand...
Click to collapse
You need to flash a custom recovery. Read the PDF in post #7 of the "need help" link in my signature. Instructions on flashing a custom recovery start at the bottom of page 9. After that you can flash ROMs from recovery.

Fixed! kinda... re-copied the PD98IMG.zip from aahk and reupdated.
It's not rooted tho...

GTDarthYoda said:
Fixed! kinda... re-copied the PD98IMG.zip from aahk and reupdated.
It's not rooted tho...
Click to expand...
Click to collapse
S off is what's key here and you have that. Rooted is a function within ROM. Do as bananagranola says and use the guide to flash recovery. From there use recovery to flash a ROM which will be rooted.
Sent from my Inspire 4G using xda premium

Gizmoe said:
S off is what's key here and you have that. Rooted is a function within ROM. Do as bananagranola says and use the guide to flash recovery. From there use recovery to flash a ROM which will be rooted.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Worked like a charm
Rom seems to be working great! I just need to try it out with a sim in it.

[Q] I need the straight poop on flashing a custom ROM

Before I get flamed, let me say that I have done ALOT of research on the questions I am about to ask, and the fact of the matter that there is a lot of conflicting information out there. So please bear with me.
I am on a rooted phone, Android 4.1.1, Sense 4+, 3.18.502.6 radio, kernal version 3.4.10
Rooted with S-on
So here's my questions:
1. Can I install a custom rom with S-on?
2. If the answer is yes, can someone give me the quick run-down, or at the very least point me in the direction of another thread that I can refer to?
3. I have read conflicting threads that claim that with S-on, I need to flash the boot.img first, other threads say just go ahead and flash the ROM
Some of these threads are 30+ pages long and go back to 2012. If you miss one post in the thread then you're screwed. Any help is appreciated. For the record these forums have been extremely helpful. Successfully rooted two phones in the past year. I understand the rooting very, flashing custom roms gives me the willies.

First thing, why not just s-off and solve your problems? It's super simple. http://forum.xda-developers.com/showthread.php?t=2155071
But the answer is... Sometimes. Sometimes you need to flash the boot.img. If you're unsure, just do it anyways. This can be done by
1. Extracting the boot.img from the ROM zip archive you wish to flash.
2. Placing it in your adb working directory.
3. Enter fastboot on your phone.
4. fastboot flash boot boot.img
Sent from my HTC One X using Tapatalk 4

RollTribe said:
First thing, why not just s-off and solve your problems? It's super simple. http://forum.xda-developers.com/showthread.php?t=2155071
But the answer is... Sometimes. Sometimes you need to flash the boot.img. If you're unsure, just do it anyways. This can be done by
1. Extracting the boot.img from the ROM zip archive you wish to flash.
2. Placing it in your adb working directory.
3. Enter fastboot on your phone.
4. fastboot flash boot boot.img
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Thanks Man! I'll give the S-off a shot. I'll take your advice and just flasht he boot.img, just to be on the safe side
I am thinking about flashing the CleanRom, unless anyone has any other suggestions

Fivetenfrank said:
Thanks Man! I'll give the S-off a shot. I'll take your advice and just flasht he boot.img, just to be on the safe side
I am thinking about flashing the CleanRom, unless anyone has any other suggestions
Click to expand...
Click to collapse
If you're s-off there's no need to flash boot.img.
Sent from my HTC One X using Tapatalk 4

RollTribe said:
If you're s-off there's no need to flash boot.img.
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Thanks. One last question. Ok maybe not the last one but one more question regardless.
With custom roms, does the rom need to be based on the same firmware that's on my stock phone? I other words, right now my phone has build 3.18.502.6. I found a rom that I really like that's based on 3.8.402.1. Is that custom rom compatible with my phone?

Fivetenfrank said:
3. I have read conflicting threads that claim that with S-on, I need to flash the boot.img first, other threads say just go ahead and flash the ROM
Click to expand...
Click to collapse
The short (and incomplete) answer is that "it depends".
If you are s-on and hboot 1.14 or higher, you need to flash boot.img separately using fastboot. A few ROMs (ViperXL, some versions of CleanROM) will flash boot.img in the AROMA installer. But most will not.
Failure to do so will mean the kernel for the custom ROM is not flashed, and you will likely bootloop or be stuck on the boot screen.
Another option, as already mentioned, is to get S-off. But be aware that S-off means that all security checks are bypassed. Meaning you can flash lots of things, with security checks bypassed. Sometimes this is good, sometimes it can be really bad.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
Fivetenfrank said:
With custom roms, does the rom need to be based on the same firmware that's on my stock phone?
Click to expand...
Click to collapse
Typically no.
There are some exceptions. For instance, if you did OTA or RUU to get on the 3.18 stock ROM, the touch panel firmware was upgraded, and AOSP ROMs will not work right (no touch functions). The solution is to have S-off and downgrade the touch panel firmware.
Fivetenfrank said:
right now my phone has build 3.18.502.6. I found a rom that I really like that's based on 3.8.402.1. Is that custom rom compatible with my phone?
Click to expand...
Click to collapse
Link the ROM, and I can probably answer that for you pretty easily.

Notills his
redpoint73 said:
The short (and incomplete) answer is that "it depends".
If you are s-on and hboot 1.14 or higher, you need to flash boot.img separately using fastboot. A few ROMs (ViperXL, some versions of CleanROM) will flash boot.img in the AROMA installer. But most will not.
Failure to do so will mean the kernel for the custom ROM is not flashed, and you will likely bootloop or be stuck on the boot screen.
Another option, as already mentioned, is to get S-off. But be aware that S-off means that all security checks are bypassed. Meaning you can flash lots of things, with security checks bypassed. Sometimes this is good, sometimes it can be really bad.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
Typically no.
There are some exceptions. For instance, if you did OTA or RUU to get on the 3.18 stock ROM, the touch panel firmware was upgraded, and AOSP ROMs will not work right (no touch functions). The solution is to have S-off and downgrade the touch panel firmware.
Link the ROM, and I can probably answer that for you pretty easily.
Click to expand...
Click to collapse
It won't link to the rom because XDA won't let me because I am a new user. It's Scott's CleanRom version 6.5. It says its built on the 3.17 OTA build
My phone is a week old. It stock with 4.1.1 and 3.18.502.6. No OTA updates happening here. So can I assume the touchpanel firmware will NOT be an issue since 3.18 is stock?
And I'm not going to mess with S-off. Ill stick with S-on for now.

You should be fine to flash it. Like redpoint said, you may have to flash the boot.img. I can't remember whether CR6.5 flashes the boot.img for you or not. To be on the safe side, go ahead and flash it.

Fivetenfrank said:
It won't link to the rom because XDA won't let me because I am a new user. It's Scott's CleanRom version 6.5. It says its built on the 3.17 OTA build
Click to expand...
Click to collapse
Fair enough. CR6.5 will work great. One thing to note however, recent versions of TWRP (2.4 and 2.5) are known to be problematic and will not work with CR6.5. Either use an older TWRP (2.3) or use the official CWM.
Fivetenfrank said:
My phone is a week old. It stock with 4.1.1 and 3.18.502.6. No OTA updates happening here. So can I assume the touchpanel firmware will NOT be an issue since 3.18 is stock?
.
Click to expand...
Click to collapse
That would be the incorrect assumption. Since the phone came out of the box with 3.18, it will have the upgraded touch panel firmware. Meaning AOSP ROMs will not have a functional touch screen, unless you S-off and downgrade the touch panel firmware.
For Sense ROMs, its doesn't matter, you are fine with the upgraded touch panel firmware.
BTW, please hit the "Thanks" button for any posts that you found helpful!

redpoint73 said:
Fair enough. CR6.5 will work great. One thing to note however, recent versions of TWRP (2.4 and 2.5) are known to be problematic and will not work with CR6.5. Either use an older TWRP (2.3) or use the official CWM.
That would be the incorrect assumption. Since the phone came out of the box with 3.18, it will have the upgraded touch panel firmware. Meaning AOSP ROMs will not have a functional touch screen, unless you S-off and downgrade the touch panel firmware.
For Sense ROMs, its doesn't matter, you are fine with the upgraded touch panel firmware.
BTW, please hit the "Thanks" button for any posts that you found helpful!
Click to expand...
Click to collapse
I think I am in good shape. CleanRom is built on Sense. Ill flash the boot.img first to be on the safe side. Btw according to Scott's website for this Rom, with respect to TWRP vs CWM, this is what he says:
"Must have TWRP Recovery installed with unlocked bootloader! CWM Recovery not supported!" Can I get a clarification?
Once this is all done ill post and let everyone know how I made out. Going back now and "thanking" all who have replied

Fivetenfrank said:
I think I am in good shape. CleanRom is built on Sense. Ill flash the boot.img first to be on the safe side.
Click to expand...
Click to collapse
Since your phone is on 3.18, and CleanROM is 3.17 base, I don't know if you can be completely sure there haven't been kernel changes. You're right, it might be the same (or same enough) kernel, but to be on the safe side, it won't hurt to flash the boot.img.
Fivetenfrank said:
Btw according to Scott's website for this Rom, with respect to TWRP vs CWM, this is what he says:
"Must have TWRP Recovery installed with unlocked bootloader! CWM Recovery not supported!" Can I get a clarification?
Click to expand...
Click to collapse
Its an outdated statement. There was a time where CWM was only a unofficial (somewhat hacked) port, and caused some serious issues for some people, that then wrongly blamed scrosler and his ROM.
None of this is very relevant any longer. CWM is officially supported for our device. It works great with CleanROM 6.5 (its what I'm currently using); when I will guarantee you that the latest TWRP 2.5.0.0 will not work with CleanROM 6.5. And anything after TWRP 2.3.1.1 is known to be problematic for our device. So its really up to you, which recovery is the best to use.
If you pick CWM, this is the thread you want:
http://forum.xda-developers.com/showthread.php?t=2148909

redpoint73 said:
Since your phone is on 3.18, and CleanROM is 3.17 base, I don't know if you can be completely sure there haven't been kernel changes. You're right, it might be the same (or same enough) kernel, but to be on the safe side, it won't hurt to flash the boot.img.
Its an outdated statement. There was a time where CWM was only a unofficial (somewhat hacked) port, and caused some serious issues for some people, that then wrongly blamed scrosler and his ROM.
None of this is very relevant any longer. CWM is officially supported for our device. It works great with CleanROM 6.5 (its what I'm currently using); when I will guarantee you that the latest TWRP 2.5.0.0 will not work with CleanROM 6.5. And anything after TWRP 2.3.1.1 is known to be problematic for our device. So its really up to you, which recovery is the best to use.
If you pick CWM, this is the thread you want:
http://forum.xda-developers.com/showthread.php?t=2148909
Click to expand...
Click to collapse
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?

Fivetenfrank said:
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?
Click to expand...
Click to collapse
You don't have to remove TWRP. Just flash over the top of it with CWM.

Egrier said:
You don't have to remove TWRP. Just flash over the top of it with CWM.
Click to expand...
Click to collapse
Got it. Wish me me luck fellas. I am going to give this a whirl tonight
Hey while I have everyone's attention, are there any other roms out there worth checking out for someone like me? That's probably a loaded question given the fact that theres a boat load of Roms out there... but all opinions welcomed!

Fivetenfrank said:
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?
Click to expand...
Click to collapse
Just for the record, I'm not saying that CWM is necessarily better. Either CWM, or TWRP 2.3.1.1. Your choice. But TWRP 2.5 definitely does not work with CleanROM 6.5, and TWRP 2.4 has issues, also.
As already mentioned, no need to remove TWRP. Just flash CWM, and TWRP will be removed.
---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------
Fivetenfrank said:
Hey while I have everyone's attention, are there any other roms out there worth checking out for someone like me? That's probably a loaded question given the fact that theres a boat load of Roms out there... but all opinions welcomed!
Click to expand...
Click to collapse
Yes, that is a loaded question. They are all worth checking out! To suggest one (or a few), would suggest the others are somehow "not worth" checking out. Which is really not fair to the devs that have worked so hard to give us these ROMs.
Look through the ROMs, and if any look interesting, try them. This is what most of us do. You already mentioned you aren't going to s-off yet, so the AOSP ROMs are out (due to the touch panel firmware issue).

redpoint73 said:
Just for the record, I'm not saying that CWM is necessarily better. Either CWM, or TWRP 2.3.1.1. Your choice. But TWRP 2.5 definitely does not work with CleanROM 6.5, and TWRP 2.4 has issues, also.
As already mentioned, no need to remove TWRP. Just flash CWM, and TWRP will be removed.
---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------
Yes, that is a loaded question. They are all worth checking out! To suggest one (or a few), would suggest the others are somehow "not worth" checking out. Which is really not fair to the devs that have worked so hard to give us these ROMs.
Look through the ROMs, and if any look interesting, try them. This is what most of us do. You already mentioned you aren't going to s-off yet, so the AOSP ROMs are out (due to the touch panel firmware issue).
Click to expand...
Click to collapse
Yep, AOSPs are out. Thanks for all of your help everyone. Going to try this tonight. Hopefully I wont have a paperweight by this time tomorrow

Fivetenfrank said:
Yep, AOSPs are out. Thanks for all of your help everyone. Going to try this tonight. Hopefully I wont have a paperweight by this time tomorrow
Click to expand...
Click to collapse
Go slow follow directions and your phone will be fine. Don't skip steps or shortcut anything. That's where problems arise.
Sent from my HTC One XL using xda premium

also inpensi
31ken31 said:
Go slow follow directions and your phone will be fine. Don't skip steps or shortcut anything. That's where problems arise.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks for the heads up. I am good on the instructions. I have found a multitude of posts outlining the steps. My biggest fear is/was the compatibility issue - flashing a rom that's not compatible with my phone. I tried flashing a Rom a couple of months ago on an HTC One X on 2.20, and I bricked it. I flashed the wrong Rom. Luckily AT&T didnt catch it and they gave me a new phone. I had to get another new phone this week past because my old HTC One X died for some unknown reason. AT&T gave me another one on warranty. This new one has the 3.18

Sounds like you flashed a ROM for the quad core "international" version (ENDEAVORU). Stick to this forum (says "AT&T" at the top) and any ROM you flash will be fine.
Or use my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237

redpoint73 said:
Sounds like you flashed a ROM for the quad core "international" version (ENDEAVORU). Stick to this forum (says "AT&T" at the top) and any ROM you flash will be fine.
Or use my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
If my memory serves me correctly, that's exactly what I did.

[Q] Can't Update Past 4.2.2 HELP!

I have a CM ROM with Android 4.2.2 running now.
Whenever I try a 4.3 or 4.4 ROM in TWR or CWR I get a failed error during flashing.
If I fastboot flash one of the newer recoveries like the ones listed in the 4.4 rom threads, the phone will just go black when it tries to enter recovery mode and I have to flash back one of the regular recoveries to get back into the phone.
I am pretty sure that the phone is failing flashing the newer mods because the two recoveries I am trying to use can't handle them, but why wont the newer recoveries work when I fastboot flash them, flashboot reads successful.
Any help would be greatly appreciated.
Thanks!

What is the filename of the new recovery you're trying to flash? And what is the command you're using?
Sent from my Evita

timmaaa said:
What is the filename of the new recovery you're trying to flash? And what is the command you're using?
Sent from my Evita
Click to expand...
Click to collapse
recovery.img which is got from the CM 11 thread (http://forum.xda-developers.com/showthread.php?t=2541998)
fastboot flash recovery recovery.img

add this command after flashing the recovery...
fastboot erase cache

bzhmobile said:
add this command after flashing the recovery...
fastboot erase cache
Click to expand...
Click to collapse
Just tried it. Still just goes to a black screen when I try to enter recovery, and then it reboots again into CyanogenMod

Could it be because I am s-on?

Better to be S-off (not mandatory I think), What is your hboot?
Try with latest TWRP or Philz touch recovery to see if it the same

Okay I got S-Off but it still won't boot to any recoveries newer than TWRP 2.6.3.0 or CWMR 6.0.3.1

It's hard to tell what's gone wrong but now that you're s-off you should try running an RUU so you can start with a clean slate.
Sent from my Evita

timmaaa said:
It's hard to tell what's gone wrong but now that you're s-off you should try running an RUU so you can start with a clean slate.
Sent from my Evita
Click to expand...
Click to collapse
Just ran 3.18 RUU and it was successful. Can you link me to the recovery that you're using?

The SCID + S-OFF + RUU 3.18 seemed to have done the trick!
Thanks for all the help!

Good news, no problems. When someone on XDA helps you please press the thanks button on the posts that were helpful as well as saying thanks.
Sent from my Evita

timmaaa said:
Good news, no problems. When someone on XDA helps you please press the thanks button on the posts that were helpful as well as saying thanks.
Sent from my Evita
Click to expand...
Click to collapse
Done and Done!
Now, I have the more difficult task of picking the best KitKat Rom

veritas2884 said:
Just ran 3.18 RUU and it was successful. Can you link me to the recovery that you're using?
Click to expand...
Click to collapse
If you are looking to flash a 4.3 or lower Rom TWRP 2.6.3.0 will be fine.
If you want to go to 4.4 you can try this custom TWRP:
http://forum.xda-developers.com/showthread.php?t=2558503
@jrior001 just posted this today.

Madcat8686 said:
If you are looking to flash a 4.3 or lower Rom TWRP 2.6.3.0 will be fine.
If you want to go to 4.4 you can try this custom TWRP:
http://forum.xda-developers.com/showthread.php?t=2558503
@jrior001 just posted this today.
Click to expand...
Click to collapse
I will give it a whirl. Thanks! Any suggestion on which 4.4 is most stable? I tried the beanstalk 4.4 build but after about five mins of using it, it devolved into boot loops. I also tried the official CM 11 nightly but it wouldn't even post. Maybe it will work better with the new twrp.

Sorry, but asking which ROM/kernel is best/most stable isn't allowed here. This is because to say one is better/faster/more stable is to infer that the other ROMs are inferior in some way. This isn't fair to the devs who spend countless hours of their spare time providing us with these awesome ROMs free of charge. It's simply a matter of flashing and testing for yourself, it only takes a few minutes to flash a ROM. Reading the last few pages in a ROM thread goes a long way too, you'll find out pretty fast how the ROM is performing.
Sent from my Evita

Flashing problems

OK guys let me tell you about my issue's
I'm using TWRP 2.7.1.0 (Tried 2.7.0.2 no difference) S-off, Unlocked, latest firmware from Santods files. The phone works fine with Sense ROMS but for the life of me I can't flash a GPE ROM. They fail every time. Santod tried to help me out the best he could by having me replace the Boot.img from the ROM I was flashing thinking that I was on a secure Boot image (And I may be but I replaced it and they still won't flash). Mr. Jaydee82 also modified a ROM for me to try out (although I'm not sure exactly what he did to it) and it wouldn't Flash properly either. When I try to flash these ROMs it will appear to flash properly and then they will go to the bootscreen and just sit there and churn. Depending on the ROM some will time out and power down the device and some will just sit there forever until I do a virtual battery pull. I'm freaking desperate to find out what is going on with this device and I don't feel right bugging Santod so I decided to post this in hope of more ideas about what could possibly be going on with my device. Any and all help greatly appreciated!!!
Thanks!

Duckman_UF said:
OK guys let me tell you about my issue's
I'm using TWRP 2.7.1.0 (Tried 2.7.0.2 no difference) S-off, Unlocked, latest firmware from Santods files. The phone works fine with Sense ROMS but for the life of me I can't flash a GPE ROM. They fail every time. Santod tried to help me out the best he could by having me replace the Boot.img from the ROM I was flashing thinking that I was on a secure Boot image (And I may be but I replaced it and they still won't flash). Mr. Jaydee82 also modified a ROM for me to try out (although I'm not sure exactly what he did to it) and it wouldn't Flash properly either. When I try to flash these ROMs it will appear to flash properly and then they will go to the bootscreen and just sit there and churn. Depending on the ROM some will time out and power down the device and some will just sit there forever until I do a virtual battery pull. I'm freaking desperate to find out what is going on with this device and I don't feel right bugging Santod so I decided to post this in hope of more ideas about what could possibly be going on with my device. Any and all help greatly appreciated!!!
Thanks!
Click to expand...
Click to collapse
What did you use to s-off; firewater or sunshine? Are you able to flash/boot AOSP roms? Did you take the 1.55.605.2 OTA before?

krazie1 said:
What did you use to s-off; firewater or sunshine? Are you able to flash/boot AOSP roms? Did you take the 1.55.605.2 OTA before?
Click to expand...
Click to collapse
I used Firewater I'm able to Flash all of the Sense ROM's not sure if they are considered AOSP. Give me an example of one and I'll try it. I'm not 100% sure if I took the OTA update before I Rooted and S-offed/unlocked the device but I think I did. I Flashed Santods Nobootimg firmware via ADB to be sure I was on the latest firmware. I know my radios were up to date before doing this but I wasn't sure about the FW so I flashed it. Flashed fine, didn't need to flush again, flashed fine first time.

Duckman_UF said:
I used Firewater I'm able to Flash all of the Sense ROM's not sure if they are considered AOSP. Give me an example of one and I'll try it. I'm not 100% sure if I took the OTA update before I Rooted and S-offed/unlocked the device but I think I did. I Flashed Santods Nobootimg firmware via ADB to be sure I was on the latest firmware. I know my radios were up to date before doing this but I wasn't sure about the FW so I flashed it. Flashed fine, didn't need to flush again, flashed fine first time.
Click to expand...
Click to collapse
I'll post a link to a aosp ROM but first can you link me to the firmware file you flashed?

krazie1 said:
I'll post a link to a aosp ROM but first can you link me to the firmware file you flashed?
Click to expand...
Click to collapse
4th one down and this was per Santod's instuction so I'm sure it's good.
http://www.androidfilehost.com/?w=files&flid=13966

Duckman_UF said:
4th one down and this was per Santod's instuction so I'm sure it's good.
http://www.androidfilehost.com/?w=files&flid=13966
Click to expand...
Click to collapse
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8

krazie1 said:
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
Click to expand...
Click to collapse
Yes, ADB Fastboot Hboot...exactly as video instructed. No problems at all.
I'll give it a shot!

krazie1 said:
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
Click to expand...
Click to collapse
Is a Gapps package needed for this ROM. Ive used Cyanogen ROM's before just not on this Phone.

Duckman_UF said:
Yes, ADB Fastboot Hboot...exactly as video instructed. No problems at all.
I'll give it a shot!
Click to expand...
Click to collapse
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/

krazie1 said:
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
Click to expand...
Click to collapse
Thats what I thought..Thanks! About to dl Gapps and give it a shot.

krazie1 said:
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
Click to expand...
Click to collapse
Yep flashed fine...no problems.

Duckman_UF said:
Yep flashed fine...no problems.
Click to expand...
Click to collapse
OK then, did you try both GPE ROMs for the vzw variant? Download the newest version of sinlessrom and wipe advanced (cache, dalvik cache, data & system) in TWRP.
http://www.androidfilehost.com/?fid=23578570567721616

krazie1 said:
OK then, did you try both GPE ROMs for the vzw variant? Download the newest version of sinlessrom and wipe advanced (cache, dalvik cache, data & system) in TWRP.
http://www.androidfilehost.com/?fid=23578570567721616
Click to expand...
Click to collapse
Already tried...Various Roms, various versions, 2 versions of TWRP (As stated) Aroma, non Aroma...They all just sit there and churn away on the boot screen or power down the device. I always wipe in that fashion

Man I'm out of ideas, I really want to help but can't think of anything. I'll still look and see if I can find anything.

krazie1 said:
Man I'm out of ideas, I really want to help bit can't think of anything. I'll still look and see if I can find anything.
Click to expand...
Click to collapse
I really appreciate your help. Santod and me went back and forth via PM a few times and JayDee modified his Rom for me and now you. IDK....I'm dumbfounded. If you think of anything let me know. I'll just stay on AOSP for now. Always liked Cyanogen's stuff anyway, just never even thought about them since their ROMS are not in the forums. They used to be for my various other phones. Never really though about them not being on XDA until we did this just now. Thanks again for you time and help!!!

Duckman_UF said:
I really appreciate your help. Santod and me went back and forth via PM a few times and JayDee modified his Rom for me and now you. IDK....I'm dumbfounded. If you think of anything let me know. I'll just stay on AOSP for now. Always liked Cyanogen's stuff anyway, just never even thought about them since their ROMS are not in the forums. They used to be for my various other phones. Never really though about them not being on XDA until we did this just now. Thanks again for you time and help!!!
Click to expand...
Click to collapse
Yeah cm11 is what I'm currently using, it recently had a speakerphone issue but its been fixed since 7/30. The only AOSP ROMs that have incorporated the fix are cm11, liquidsmooth & aokp. Here is the section for all the aosp ROMs they are universal so means 1 zip for all HTC One M8 variants.
http://forum.xda-developers.com/htc-one-m8/orig-development

Have you tried a RUU?

young0ne said:
Have you tried a RUU?
Click to expand...
Click to collapse
What do you mean? I put the phone in RUU when when flashing the firmware with ADB??

Duckman_UF said:
What do you mean? I put the phone in RUU when when flashing the firmware with ADB??
Click to expand...
Click to collapse
it put stock back on the phone just like it was new out of box. it re installs everything from factory.

Thanks!
GNU con Linux