What version of twrp works with hboot 2.14? Thanks
Sent from my HTC One XL using xda app-developers app
I use 2.3.3.1.
Sent from my HTC One X
Avoid any versions above 2.3.3.1 as they have issues wiping
Sent from my One X using xda app-developers app
I'm on 2.5.0.0, and I've used versions 2.4.x before that, and I've had no problems. I switched over from Hatka (sense) to Carbon (AOSP) yesterday with no issues. 2.5.0.0 has been out for a few months now, so you think they'd have patched it by now if there were widespread problems. Just curious why I've had none. S-Off?
Sent from my One X using Tapatalk 2
No one on team win has an Evita and no one has posted logs for them
Sent from my Nexus 7 using xda premium
mbcastle said:
I'm on 2.5.0.0, and I've used versions 2.4.x before that, and I've had no problems. I switched over from Hatka (sense) to Carbon (AOSP) yesterday with no issues. 2.5.0.0 has been out for a few months now, so you think they'd have patched it by now if there were widespread problems. Just curious why I've had none. S-Off?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Luck? Certainly not because of S-OFF. Wiping gave me errors every time in TWRP 2.4.x didn't bother trying 2.5 since 2.3.3.1 works just fine.
TWRP versions later then 2.3.X will not work with CleanROM 6.5, known issue.
I can confirm that CR6.5 does not work with TWRP 2.5.0.0.
exad said:
Luck? Certainly not because of S-OFF. Wiping gave me errors every time in TWRP 2.4.x didn't bother trying 2.5 since 2.3.3.1 works just fine.
Click to expand...
Click to collapse
Same here it always corrupted my sdcard but 2.5 has had no problems and I've used all of it's features
Sent from my HTC One XL using xda premium
redpoint73 said:
TWRP versions later then 2.3.X will not work with CleanROM 6.5, known issue.
I can confirm that CR6.5 does not work with TWRP 2.5.0.0.
Click to expand...
Click to collapse
True. And ImagioX1 suggest twrp 2.3.3 or lower to flash Evita Sense5 R2 http://forum.xda-developers.com/showthread.php?t=2293032
which is very smooth and esthetik btw !!
Related
I've run multiple versions of CleanROM and also CM10, but anytime I install a Sense based JB ROM (I've tried Newt's, JellyBlam, and a few others), my phone gets stuck on the HTC boot splash, reboots, and enters recovery. I am on HBOOT 1.09 and Ive tried to fastboot flash the boot.img just to be sure, but it still doesn't work? I'm sure I'm doing something wrong, any clue what it is? Thanks in advance.
Are you doing full wipes before flashing?
Sent from my HTC One XL using xda app-developers app
area51avenger said:
Are you doing full wipes before flashing?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I do a factory reset in TWRP. Does that count, or is there more to it?
Grazzert said:
I do a factory reset in TWRP. Does that count, or is there more to it?
Click to expand...
Click to collapse
Tell us what ROM you're trying to install. Also, you're right about the reset. Do all of that in twrp.
Sent from my One X using xda premium
ToxicWaste said:
Tell us what ROM you're trying to install. Also, you're right about the reset. Do all of that in twrp.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Newt's
Grazzert said:
Newt's
Click to expand...
Click to collapse
Are you sure it successfully installed?
omario8484 said:
Are you sure it successfully installed?
Click to expand...
Click to collapse
The log says it successfully installed and when i press reboot system, the sequence of events i described in OP happens
Factory reset and wipe system and both caches
Sent from my HTC One XL using xda app-developers app
area51avenger said:
Factory reset and wipe system and both caches
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
same thing happens :/
bump for answers....
Sounds like the correct procedure to me.
Sent from my HTC One XL
ECEXCURSION said:
Sounds like the correct procedure to me.
Sent from my HTC One XL
Click to expand...
Click to collapse
And yet it won't work. lol
Maybe you have an init.d folder that is telling the JB ROM to overclock? Could check and delete that first. Otherwise you can double check the md5 of the ROM you're flashing to make sure its not corrupt. Aside from that it might be worthwhile to try a ROM like urdroid which allows you to flash the kernel during the installer.
Dunno man, your problem is a strange one.
Sent from my HTC One XL
ECEXCURSION said:
Maybe you have an init.d folder that is telling the JB ROM to overclock? Could check and delete that first. Otherwise you can double check the md5 of the ROM you're flashing to make sure its not corrupt. Aside from that it might be worthwhile to try a ROM like urdroid which allows you to flash the kernel during the installer.
Dunno man, your problem is a strange one.
Sent from my HTC One XL
Click to expand...
Click to collapse
Urdroid was another that i tried. It would get to the ROMs boot splash and lock there, but its the only one i recall that even got that far out of the 3 or so that i tried. where would that init.d folder be?
Either the directory of the /sdcard or /. I forget which as I have deleted it. But it should be a folder. Don't delete it if it's by itself.
Sent from my HTC One XL
Really sounds like you are not flashing the boot.img correctly.
Extract the boot.img from the ROM you want to use and install it with:
fastboot flash boot boot.img
You're not alone....
Grazzert said:
Urdroid was another that i tried. It would get to the rom's boot splash and lock there, but its the only one i recall that even got that far out of the 3 or so that i tried. where would that init.d folder be?
Click to expand...
Click to collapse
I've been experiencing the same problem on my HTC Sensation 4G for the past couple years since I've had it. I have 3 HTC Sensations in my family and I've been playing around with all 3 phones during the last year. On my sister and my mom's phones, I'm able to install any rom (Sense-based...ARHD, Elegencia; and AOSP/AOKP-based...CM10, Paranoid Android, etc); however, on my own phone, after dozens of installs, trying all types of different kernels and roms, I was only able to install AOSP/AOKP-based ones. I've been running Touchcream ICS rom for awhile, then Paranoid Android, and currently JB Samsation V5 on my HTC and I love it. I'm really not missing out on anything, but it's just weird Sense-based roms just wouldn't boot. After some researching on the forum and experimenting with others, I've deducted that the reason could be very well my own hardware. :victory:
As title says, I can only flash Venom ROM, no other one is allowed. Every time I try, I get an error (Status 1) in TWRP. Do you guys have any similar problems/ways to fix it?
theking_13 said:
As title says, I can only flash Venom ROM, no other one is allowed. Every time I try, I get an error (Status 1) in TWRP. Do you guys have any similar problems/ways to fix it?
Click to expand...
Click to collapse
Downgrade your recovery to an earlier version. The latest one caused this problem.
Sent from my HTC One X using xda premium
bkmo said:
Downgrade your recovery to an earlier version. The latest one caused this problem.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Which version number do you recommend?
Sent from my Nexus 7 using Tapatalk 2
theking_13 said:
Which version number do you recommend?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I use 2.3.3.1 and it works great. If you have the updated firmware you will have to use 2.4 though
Sent from my VENOMized HoxL
area51avenger said:
I use 2.3.3.1 and it works great. If you have the updated firmware you will have to use 2.4 though
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
I have the latest hboot, so I have to use 2.4 no matter what?
Is it recommended to S-OFF and downgrade to 1.09 instead?
Sent from my HTC One X using Tapatalk 2
theking_13 said:
I have the latest hboot, so I have to use 2.4 no matter what?
Is it recommended to S-OFF and downgrade to 1.09 instead?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Going S-OFF and flashing 1.09 would make your life a lot easier, yeah.
theking_13 said:
I have the latest hboot, so I have to use 2.4 no matter what?
Is it recommended to S-OFF and downgrade to 1.09 instead?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Yes I recommend s-off with 1.09 hboot. What hboot do you have right now?
Sent from my VENOMized HoxL
My understanding of s-off is that your hboot version becomes irrelevant.
You can even leave your phone bootloader locked and still flash roms, radios, recoveries, kernels etc when you're s-off.
Before s-off, hboot 1.09 - 1.11 allowed for kernels and radios to be flashed via recovery which is why they were preferred.
The only issue with the newer hboot is the upgraded touch panel drivers which are not compatible with AOSP roms.
But h8rift created a thread so you can downgrade just the touch panel if you want to use AOSP.
Hi, I've searched for an answer to this but I can't find it. My fiance's one xl is seriously playing up. Some background: it's on hboot 1.09 and s-on. She's been using Viper since we rooted it.
A couple months back (possibly after moving to JB) her Wi-Fi was unable to find networks, or when it could find them it was unable to connect to networks. Ok so she dealt with that. Recently I thought I'd flash a different ROM to see if it would make a difference, so we flashed a recent version of AOKP (build 4). This booted fine but the WiFi just kept saying it was turning on but never actually turned on. So we thought we'd flash back to Viper. Full wipes were done while moving between ROMs by the way. Anyway viper just constantly bootloops no matter what we try now, so we can't use that. So we flashed back to AOKP and now neither Wi-Fi or Bluetooth work. Bluetooth at least turns on sometimes but it can't find other devices and other devices can't find it.
So yeah, no viper, no Bluetooth, no Wi-Fi, very frustrated fiance!
I've been reading the last couple days and just can't find what's wrong, does anyone have any idea? Any help would be greatly appreciated.
Sent from my One XL using XDA Premium
Sounds like hboot 1.14? Did you use flash gui or adb to flash the viper boot image?
Sent from my HTC One X using xda premium
ChrisPBacon said:
Sounds like hboot 1.14? Did you use flash gui or adb to flash the viper boot image?
Click to expand...
Click to collapse
On ViperXL, boot.img should flash in AROMA, even with hboot 1.14. Although it doesn't always work, so if it bootloops, then OP should flash boot.img using fastboot or Flash Image GUI.
Agree, sounds like it can be a ROM-kernel mismatch.
That's what happened to me when I flashed to the new CM to take it for a test drive. When I flashed back to Viper I went straight to bootloop. Forgot to flash the boot image. Aroma usually works for me but it has problems when going from aokp to sense.
Sent from my HTC One X using xda premium
I'm pretty sure it's not 1.14, it was one of the earliest models released way back nearly a year ago.
Any ideas on the Wi-Fi / Bluetooth situation guys?
Sent from my One XL using XDA Premium
Ok I can confirm its definitely on hboot 1.09
Sent from my One XL using XDA Premium
Bump, anyone??
Sent from my One XL using XDA Premium
I'd try dirty flash the rom.zip for the booted ROM a couple times in recovery, to see if something isn't sticking right. I've had that happen on a couple kernel changes in CM.
Sent from my HOX w/CM10.1 4.2.2 s-off
I'll try that. I've managed to get her Bluetooth working by flashing King Kang ROM. Now it's just the Wi-Fi that won't work, but I'll try that thanks for the suggestion, I'll report back.
Sent from my One XL using XDA Premium
timmaaa said:
I'll try that. I've managed to get her Bluetooth working by flashing King Kang ROM. Now it's just the Wi-Fi that won't work, but I'll try that thanks for the suggestion, I'll report back.
Sent from my One XL using XDA Premium
Click to expand...
Click to collapse
I am also facing the same problems my wifi , Bluetooth and mobile network are not turning on... i have tried all, factory reset, ruu flashing, new custom rom flashing , kernel flashing... please help:crying:
Ok so now Bluetooth is working fine and Wi-Fi turns on but it can't detect any networks. Basically all I did was another full wipe and flashed King Kang. Does anybody have any ideas on how to get the Wi-Fi working properly please?
Sent from my One XL using XDA Premium
Wow so I've done pretty much everything I can to get this phone working ok. S-off, RUU: phone still bootloops when booting Sense ROMs, even the RUU bootlooped. Sometimes it makes it into the ROM after several loops but it just crashes and starts all over again. Phone boots aosp ROMs perfectly fine, but WiFi and Bluetooth don't work still. I'm at a complete loss.
Sent from my EVITA using xda premium
timmaaa said:
Wow so I've done pretty much everything I can to get this phone working ok. S-off, RUU: phone still bootloops when booting Sense ROMs, even the RUU bootlooped. Sometimes it makes it into the ROM after several loops but it just crashes and starts all over again. Phone boots aosp ROMs perfectly fine, but WiFi and Bluetooth don't work still. I'm at a complete loss.
Sent from my EVITA using xda premium
Click to expand...
Click to collapse
sounds like a hardware issue to me.
Yeah it sure does. What's got me stumped is the fact that it boots aosp fine and runs fine apart from Bluetooth and WiFi. But sense ROMs loop like crazy, but sometimes boot into the OS before looping again. Eh I dunno.
Sent from my EVITA using xda premium
exad said:
sounds like a hardware issue to me.
Click to expand...
Click to collapse
Hey Exad, I wonder if this might be a kernel issue. We tried booting the latest CM10.1 and it's having the same boot problems. So maybe it's a 3.4 kernel issue, what are your thoughts?
Sent from my EVITA using xda premium
Its unlikely.. you're on the latest hboot right?
I mean.. If it was an issue with the 3.4 kernel, I imagine issues would be way more widespread.
It would be possible to have issues with a 3.4 kernel on an older hboot.. but otherwise I just don't see how.
Sent from my HTC One X using xda app-developers app
Yeah we RUU'd her phone to 3.18 so it's fully up to date. The thing that made me think kernel/boot.img was that every non 3.4 aosp ROM runs ok, apart from Bluetooth and WiFi. Which I guess is a hardware issue.
I thought maybe there's something within 3.4 kernel that won't let the phone operate properly with that specific hardware problem. But something within <3.4 kernels that lets the phone operate, just without Bluetooth and WiFi working.
Sent from my EVITA using xda premium
Yes, THAT theory is possible though no software will have things running 100%. I'm sure you knew that already.
Sent from my HTC One X using xda app-developers app
Yeah I know, I'm just kinda clutching at straws trying to work this out.
Sent from my EVITA using xda premium
Most likely the radio is fried.
Sent from my HTC One X using xda app-developers app
If anyone is having trouble with the later versions of elementalx I have found that v5.4 has no issues. I don't know what the problem is but anything above that has not worked for me on any sense based ROM. I am on 1.09 hboot and s-on. Currently I am running the miui v5 3.5.3 as my daily driver despite the MMS problem, soon to be fixed on the next update, hopefully
Sent from my One XL using xda app-developers app
I have never been able to flash any elemental kernel. I've tried every one, on multiple roms, tried messing with all of the settings...each time the phone starts rebooting itself within a few minutes of boot. I must just have some strange hardware. Bulletproof kernels work great.
Sent from my HTC One XL using xda app-developers app
dominatordave said:
I have never been able to flash any elemental kernel. I've tried every one, on multiple roms, tried messing with all of the settings...each time the phone starts rebooting itself within a few minutes of boot. I must just have some strange hardware. Bulletproof kernels work great.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
The bulletproof kernels are a solid choice.
I also remember 5.4 as being a particularly stable release.
This post was created and transmitted completely in analog.
I was on 5.4 for about 2 months and then recently upgraded to 6.6 and no problems to speak of.
What do you mean 'does not work for you'? What happens when you install it? I'm assuming you are flashing the boot.img since you are S-On.
I've tried both 6.6 and 6.7 and haven't had any issues.
Sent from my One XL using XDA Premium
The problem I'm having is I get a popup message constantly(android.process.com has stopped). As far as know I don't need to flash a boot.img considering I'm on hboot 1.09. Never had this with any other kernel whether it be aosp or sense based.
Sent from my One XL using xda app-developers app
libra83 said:
The problem I'm having is I get a popup message constantly(android.process.com has stopped). As far as know I don't need to flash a boot.img considering I'm on hboot 1.09. Never had this with any other kernel whether it be aosp or sense based.
Sent from my One XL using xda app-developers app
Click to expand...
Click to collapse
This only happens on later versions of elemental x? If you flash back to 5.4 does the process stop force closing?
Also, check the message...ls it com.android.process.acore or com.android.process.phone?
This post was created and transmitted completely in analog.
Still having issues.
=JKT= said:
This only happens on later versions of elemental x? If you flash back to 5.4 does the process stop force closing?
Also, check the message...ls it com.android.process.acore or com.android.process.phone?
This post was created and transmitted completely in analog.
Click to expand...
Click to collapse
Yes flashing back to 5.4 fixes the fc issues. Sorry for the confusion on the message. I've been working long hours lately. It is the second one mentioned above. Is it possible that even though I'm on the earlier hboot that i still need to be s-off because of the newer versions of kernels? Thanks for your time looking in to this issue.
S-off would make no difference with kernels. It would make more sense for your hboot version is causing it. Hard to say for sure without testing though. You did check md5 prior to flashing right?
Sent from my HTC One X using xda app-developers app
I'm on hboot 1.09 with s-off and i get similar issues, reboots, glitchy screen flickers
I am never getting issues like that
Sent from my HTC One XL using xda premium
Recently Google updated the Maps application and ever since they updated the map application I seem to have problems with keeping my signal now and it only happens when I'm using Google Maps. Has anyone else ever seen this issue and possibly fixed it?
Edit: I forgot to mention that occasionally the phone will reboot because of this issue.
Sent from my AT&T HTC One X Evita S-Off running CyanogenMod 10
I used it today on 10.1 3.4 kernel no issues..
Sent from my One X using xda app-developers app
I have a different kernel. I thought when you install a ROM it installed the kernel for that ROM is that not the case?
Edit: could the kernel be the cause of all this?
Sent from my AT&T HTC One X Evita S-Off running CyanogenMod 10
Yes it does. I'm just saying that it's working for me. Try wiping app data?
Could be anything. Try wiping the app data if stoll not working try factory reset in recovery, if still not working try clean flash. With latest twrp
Sent from my One X using xda app-developers app
So far I have what I have done is to clear the cache uninstall the program entirely then reinstalled it the only other option is to reinstall the entire ROM is far as I can tell. Which brings me to my next question how do I go back to AT&T stock? The reason I ask is ever since I've switched roms everything just is screwing up and with the stock AT&T rom things actually worked.
Edit: Google speech to text typos.
Sent from my AT&T HTC One X Evita S-Off running CyanogenMod 10
Most likely you're using twrp between 2.4 and 2.5 only 2.3.3.1 and under and 2.6 wiper properly and you probably never fastboot erase cache after installing a new recovery.
In any case to go stock, s-off then Ruu.
Sent from my One X using xda app-developers app
I believe you're right my TWRP is 2.5.0.0. About the cache after installing the ROM I am a little unfamiliar with. I already have the bootloader unlocked and I have s-off so I guess it's just a matter of using the AT&T ruu? Will that conflict with the custom kernel and TWRP?
Edit: typos. also I was having a little bit of difficulty understanding what your saying in your previous post about the versions. which version should I have installed?
Sent from my AT&T HTC One X Evita S-Off running CyanogenMod 10
2.6 is now stable but previously all versions above 2.3.3.1 would not wipe properly causing issues.
Whenever you flash recovery it is advisable to do fastboot erase cache after. Not always necessary but it takes a few seconds and can save you loads of issues.
Yes an Ruu will work so long as you are s-off. If you're not s-off you'll brick.
Sent from my One X using xda app-developers app
Thanks I appreciate the assistance perhaps reinstalling CyanogenMod 10 will fix the issue.
Sent from my AT&T HTC One X Evita S-Off running CyanogenMod 10
This past weekend I upgraded the recovery and I reinstalled CyanogenMod 10 and tested the GPS this morning and it doesn't seem to have been fixed. Could there just be some sort of incompatibility with the newer version of maps because it was working on an older version of maps?
Edit: Google speech to text typos.
Edit 2: Also the RUU doesn't seem to work either.
Edit 3: After changing ROMs to Viper XL the GPS started working fine. So I believe that CyanogenMod 10 has some sort of compatibility issue with the latest version of Google Maps.
Sent from my One X using XDA Premium 4 mobile app