Somebody knows why
This happend or what is the problem
Thanks in advance
Sent from my HTC One XL using xda app-developers app
Do you really expect anyone to be able to help if that's the only information you're giving? Seriously, you haven't given any information whatsoever.
Sent from my Evita
Im on hboot 2.15
Unlocked
S off
Twrp 2.6.3.0
Android 4.2.2
Sense 5
Kickdroid rom halloween edition
Beastmode kernel 3.5 reloaded
Sent from my HTC One XL using xda app-developers app
It looks like it's probably a hardware problem, but to test the theory you could run an RUU and see if the problem persists on the stock ROM. If so you have a faulty digitizer.
Sent from my Evita
I have the same problem on hboot 2.15 no matter what rom I use. Is it possible to downgrade?
Sent from my HTC One X using xda app-developers app
Yaakov. M said:
I have the same problem on hboot 2.15 no matter what rom I use. Is it possible to downgrade?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Please provide exact details on your situation, saying you have the same problem doesn't tell me anything. I also need your bootloader details, ROM details, kernel details, recovery details.
Sent from my Evita
Ok,
hboot 2.15 (latest AT&T ruu)
S-off supercid ect...
Currently running cleanrom 7.0r2 but the problem persists on every rom I've tried since I took the ruu.
I didn't play with custom kernel.
I also tried cm but phone's touchscreen would randomly stop responding all together after sleep.
Tried both twrp and cwm
Thanks
Sent from my HTC One X using xda app-developers app
I need your bootloader details, the first five or six lines, from the very top. The latest at&t RUU comes with the 2.18 hboot, not the 2.15 hboot. I also need to know exactly which recovery versions you've been using. And you haven't described the problem you're having.
Sent from my Evita
*** unlocked **
Evita put ship s off rl
Cid 11111111
Hboot 2.18.0000
Radio 1.35a 32.45.27
Open dsp v33.1.0.45.1128
Emmc boot
December 3 2013 17:10:01:1768
I've tried twrp 2.6.3.0, twrp 2.7, and the latest cwm.
The problem on every rom is a line to which the touch screen is not responding (just below the middle of the display)
Specifically on cm m4 the screen would stop responding all together after waking
Thanks
Edit : the problem started after I took the ruu
Sent from my HTC One X using xda app-developers app
Ok, so you have the 2.18 hboot, that's why I asked for your bootloader details the first time around. You should run an RUU, maybe the 3.18, to see if it resolves your problem.
Sent from my Evita
Can I run the 3.18 ruu after running the 5.something one? And yes I remembered the hboot wrong.
Sent from my HTC One X using xda app-developers app
You can run any Evita RUU when you have s-off, whether it's a higher or lower version.
Sent from my Evita
Related
I bought this phone outright, and I don't like the Telstra network so I put an Optus SIM in. Which works just fine, however I now have an issue which may or may not be related. I have unlocked my bootloader, and have obtained root. I cannot get s-off however, tried all the methods in this forum. And when I try to install a new Rom, such as cm10 and all nightly versions, venom viper, and all other Roms I have tried I cannot get passed the start up logo (or I just get a pure black screen). Yes I have waited and waited for extended periods of time but it won't load. No I'm not new to rooted phones, and have followed all insructions properly. Pls help me, I really hate all the Telstra bloatware on my phone.
Sent from my HTC One XL using xda app-developers app
you have to fastboot flash the boot.img when you are s-on
Only problem is I used that stupid one xl one click toolbox for my root. Which has completely stuffed me up.I should have done it the hard way like I did with my incredible s. I just got lazy. Don't suppose you know how to get s-off, without the one click fixes. Unfortunately they arnt working on this phone to acheive s-off
Sent from my HTC One XL using xda app-developers app
pretty sure you need supercid to s-off here is the s-off thread
http://forum.xda-developers.com/showthread.php?t=2155071
and how to get supercid on non att
http://forum.xda-developers.com/showthread.php?t=2212737
Thank you will give it a try tomorrow.
Sent from my HTC One XL using xda app-developers app
your welcome
jerrycoffman45 said:
you have to fastboot flash the boot.img when you are s-on
Click to expand...
Click to collapse
Not necessarily. It depends on your hboot version I believe.
I've never had to flash the boot image and I haven't done s-off.
@OP - did you need to s-off for any specific reason? You don't need to do this to flash a custom ROM. It's not required unless you want to reove the tampered text from the boot loader.
It makes life easier to have s-off. Besides I have issues with not having full access to something I have bought outright....lol
Sent from my HTC One XL using xda app-developers app
I s-off'd my HOXL because it makes it much safer from my own boneheaded mistakes. If I had done something silly like flashing the OTA RUU then I wouldn't be completely screwed.
Sent from my HOXL!
Hi
I was looking at various CM 10.1/AKOP ROMS and many of them had RUU 3.18 as a requirement. From what I understand this is only required for ROMS running the 3.4 kernal.
My only problem is that I am using a Telus HTC One XL, and while looking at a thread with the RUU of each provider, the latest RUU for my phone was 3.17, which I am currently running.
Would I still be able to flash ROMS running the 3.4 kernal or should I stick to ROMS without that kernal?
If it helps:
Unlocked Boot loader
Rooted
Super CID
S-OFF
Hboot 2.14
Touch Firmware Downgraded
Thanks in advance for any help.
Sent from my HTC One X using xda app-developers app
I'm not 100% sure, but you could always make a nandroid backup and try cm10.1. I *think* the 2.14 HBOOT is the important part.
Sent from my One X using xda app-developers app
I you might as well just backup then try it. Worst case is it doesn't work and you restore backup. Also, I'm pretty sure you can do the 3.18 ruu on any XL device.
-Sugardaddy
3.17 works too. I'm on Telus 3.17 and have run cm10.1 with 3.4 kernel.
OK guys, thanks. Guess I'll flash it and see how it goes.
Edit: Worked great! Thanks a lot guys!
Sent from my HTC One X using xda app-developers app
Hey all, I've just switched to this ATT One X and I'm looking for a little guidance. I've rooted, unlocked bootloader, and flashed TWRP. I've also downloaded PAC and GAPPs. That being said, I've read a little about flashing a Rom and a boot.img seperately which would be new to me. I didn't see anything mentioning that process on the PAC thread so I'm assuming that I just wipe data, flash Rom, wipe cache and dalvik, flash gapps and reboot? If there is something I'm missing, could anybody help? Thanks in advance!
Sent from my HTC One X using xda app-developers app
If you are s-off you do not have to flash the boot.img seperately. If you are s-on you have to flash the boot.img with fastboot from a computer.
Sent from my HTC One X using xda app-developers app
mmmatt312 said:
If you are s-off you do not have to flash the boot.img seperately. If you are s-on you have to flash the boot.img with fastboot from a computer.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks! Im s-on at the moment so I'll look into getting s-off when I get some free time. Hopefully adb will cooperate with me, we have a love/hate relationship....
Sent from my HTC One X using xda app-developers app
Quick question, flash the whole rom zip, then the boot.img, then gaaps?
Sent from my HTC One X using xda app-developers app
I'm pretty sure you can flash the boot.img with fastboot before or after the rom. But flash gapps after you flash the rom. The way I used to do it(when I was s-on) was flash rom, flash gapps, then flash the boot.img from the terminal using fastboot.
Sent from my HTC One X using xda app-developers app
[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode! is your friend
flash boot.img first then rom and gapps, but definately do s-off you don't wanna end up forgetting that flashing 3.17/3.18 with s-on + supercid will brick your phone.
Nice! I'm looking into s-off as of now, but what did you mean by flashing 3.17/3.18? I'm on 3.18 and I believe I have superCID. Does that mean I should hold off on flashing until I'm s-off?
Sent from my HTC One X using xda app-developers app
No you can flash now. We weren't aware that you're already on the 3.18 firmware. If you weren't on that firmware you would have needed to RUU up to it in order to flash the ROM, and the warning was to get s-off before running the RUU because s-on + SuperCID + RUU = brick. So, go ahead and flash the ROM.
PS. In future, make sure you provide all relevant information (current firmware/current recovery/s-off or s-on status). This information is needed to help, and it also stops this kind of confusion.
Sent from my Evita
timmaaa said:
No you can flash now. We weren't aware that you're already on the 3.18 firmware. If you weren't on that firmware you would have needed to RUU up to it in order to flash the ROM, and the warning was to get s-off before running the RUU because s-on + SuperCID + RUU = brick. So, go ahead and flash the ROM.
PS. In future, make sure you provide all relevant information (current firmware/current recovery/s-off or s-on status). This information is needed to help, and it also stops this kind of confusion.
Sent from my Evita
Click to expand...
Click to collapse
Sorry for the confusion. Trying to gather as much knowledge on this as possible and didn't think to mention that I did the ota update to 3.18. I appreciate the help guys and hopefully soon I'll have a custom Rom running on this thing :thumbup:
Sent from my HTC One X using xda app-developers app
Successfully flashed PAC and ended up using the app posted here. Worked like a charm! Thanks for all the help guys!
Sent from my One X using xda app-developers app
Hello geniuses
I have a doubt, my HOXL phone is new and comes with software
RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17. 32.09. 12_10. 86.32 08L_release_262092_signed. exe
EVITA PVT SHIP S-OFF
CID-11111111
H.boot 1.09.0000
I want to install the latest version
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24 p. 32.09 06_10. 130.32 34_release_signed. exe
But I am afraid of making it brick but the S-OFF CID 11111
I can? or not?
Or I have to return it to S-ON
Is which the correct way??
You'll be fine, it only bricks when you have SuperCID + s-on. Your current configuration (SuperCID + s-off) is fine.
Sent from my Evita
timmaaa said:
You'll be fine, it only bricks when you have SuperCID + s-on. Your current configuration (SuperCID + s-off) is fine.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, I am more reassured
You or someone I could confirm if the version
is 3.18 best for my phone? or they have any better?
The 3.18 RUU is the latest at&t RUU that has been released. It will update your hboot to 2.14, which is good because if you plan on running any recent aosp ROM you need that hboot. If you plan on staying stock though you'll have JB 4.1 running.
Sent from my Evita
timmaaa said:
The 3.18 RUU is the latest at&t RUU that has been released. It will update your hboot to 2.14, which is good because if you plan on running any recent aosp ROM you need that hboot. If you plan on staying stock though you'll have JB 4.1 running.
Sent from my Evita
Click to expand...
Click to collapse
Timmaaa,
If I've upgraded the firmware and flashed Turge's 4.2.2 sense ROM, do you think it's safe to RUU back to stock?
The combination of the new ROM, the new firmware, and Beastmode kernel seem to produce bad behaviors like going to airplane mode during calls and random shutdowns.
Thanks,
Dan
Sent from my HTC One XL using xda app-developers app
DanGeorges said:
Timmaaa,
If I've upgraded the firmware and flashed Turge's 4.2.2 sense ROM, do you think it's safe to RUU back to stock?
The combination of the new ROM, the new firmware, and Beastmode kernel seem to produce bad behaviors like going to airplane mode during calls and random shutdowns.
Thanks,
Dan
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I haven't seen anyone report running an RUU while on the latest firmware, but if you're s-off you should be safe to do so. Please note I'm saying you SHOULD be safe, this is not a guarantee as I haven't tested it, but I'd assume that the theory is sound.
Sent from my Evita
timmaaa said:
I haven't seen anyone report running an RUU while on the latest firmware, but if you're s-off you should be safe to do so. Please note I'm saying you SHOULD be safe, this is not a guarantee as I haven't tested it, but I'd assume that the theory is sound.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the advice and warning. The firmware downgrade is the one thing that makes me hesitate.
Any ideas on the issues I'm experiencing? I really like the ROM. It's buttery smooth.
Sent from my HTC One XL using xda app-developers app
If you've upgraded your firmware you might not necessarily need to use the Beastmode kernel, you could try dirty flashing the ROM. This will in effect just replace Beastmode with the stock kernel.
Sent from my Evita
I've been looking all over this forum and would appreciate some related help! I'm also trying to run ViperXL 4.1 but have constant reboots which many posts suggest can be remedied by upgrading ones firmware. I'm SuperCID + s-off, hboot 1.14, and I don't know where to go from here! What should I upgrade and how? ...any links/help would be appreciated!
Greatday1 said:
I've been looking all over this forum and would appreciate some related help! I'm also trying to run ViperXL 4.1 but have constant reboots which many posts suggest can be remedied by upgrading ones firmware. I'm SuperCID + s-off, hboot 1.14, and I don't know where to go from here! What should I upgrade and how? ...any links/help would be appreciated!
Click to expand...
Click to collapse
After all this time searching I only had to ask and I got lucky and found it!
http://forum.xda-developers.com/showthread.php?t=2423735
timmaaa said:
If you've upgraded your firmware you might not necessarily need to use the Beastmode kernel, you could try dirty flashing the ROM. This will in effect just replace Beastmode with the stock kernel.
Sent from my Evita
Click to expand...
Click to collapse
Can I just flash the boot.img from the ROM instead of dirty flashing the entire thing?
Yep.
Sent from my Evita
I am owning HTC One X (AT&T) Hboot 0.89, CID 1111111, S-ON. I have installed ViperXL 4.2.0 with this hboot, but can see some inormal acts on my phone. Do I need to upgrade HBOOT version? If yes, how can I do that?
First of all you need soff. It's in the original android development. After that, I wrote a guide in the general section on how to update the bootloader
Hit thanks if I helped
Sent from my HTC One XL using XDA Premium 4 mobile app
It isn't just the hboot you need to upgrade, it's the full firmware package that you need.
Sent from my Evita
pandasa123 said:
First of all you need soff. It's in the original android development. After that, I wrote a guide in the general section on how to update the bootloader
Hit thanks if I helped
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks a lot, now phone is S-OFF, HBOOT-2.15.00. Do I need to re-flash ViperXL 4.2.0?
You couldn't have to flash it again, just boot up.
Sent from my Evita
I would at least clear Dalvik and cache. It never hurts.