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
Related
So I was going to switch roms on the fly and use flash image gui and found the rom, selected recovery img, and flashed. Success, so i rebooted to recovery. Weird part is, it took me to bootloader. Thinking I hit the wrong thing I moved to recovery and it sends me to fastboot. I assume I did something wrong and have to flash twrp again?
KungPow90 said:
So I was going to switch roms on the fly and use flash image gui and found the rom, selected recovery img, and flashed. Success, so i rebooted to recovery. Weird part is, it took me to bootloader. Thinking I hit the wrong thing I moved to recovery and it sends me to fastboot. I assume I did something wrong and have to flash twrp again?
Click to expand...
Click to collapse
Anyone have a thought before I just try something and accidentally brick my phone? Lol
KungPow90 said:
Anyone have a thought before I just try something and accidentally brick my phone? Lol
Click to expand...
Click to collapse
Download twrp for Evita
Boot into fastboot
fastboot flash recovery filename.img
K I got TWRP but everytime I power down the phone, it jumps back into fastboot 5 seconds later. Uhm, What? lol. I messed up bad this time...
KungPow90 said:
K I got TWRP but everytime I power down the phone, it jumps back into fastboot 5 seconds later. Uhm, What? lol. I messed up bad this time...
Click to expand...
Click to collapse
Fastboot reboot recovery
That command doesn't work. To execute a fastboot command you need to have the phone in bootloader right?I tried it from fastboot and from bootloader.
Download goo.im and install recovery from the app
Sent from my HTC One XL using Tapatalk 2
rpomponio said:
Download goo.im and install recovery from the app
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
That worked! Im in TWRP now. Thanks so much! Worried I wouldn't be able to boot up but I did. Phew!! Dont do that again... ok then. Is there any way to flash the boot img on the fly without fastboot?
Depends on the Rom. A lot of them you just download Rom to sd card then intall through twrp. No img fastboot needed on a lot of roms when using twrp. What img are u trying to flash?
Sent from my HTC One XL using xda premium
Idk any. I was trying to flash clean rom 5.1 but it always gets stuck on the boot.
In the current ics version of venom rom the camera refuses to work. I can sometimes open the app but is always a black screen. Any ideas?
Sent from the best d*** phone I've ever used
http://forum.xda-developers.com/showthread.php?t=1671237
this link has all roms and instruction. Very handy for hox
Sent from my HTC One XL using xda premium
DESERT.TECH said:
http://forum.xda-developers.com/showthread.php?t=1671237
this link has all roms and instruction. Very handy for hox
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks! As regards the camera issue... Thoughts?
Sent from the best d*** phone I've ever used
Hmm I believe that viper 2.4.2 addresed camera issues. To get that version you have to do ota update and it pushes update to your phone ...so if you have viper 2.4.0 just check for update as you would normally
Sent from my HTC One XL using xda premium
DESERT.TECH said:
Hmm I believe that viper 2.4.2 addresed camera issues. To get that version you have to do ota update and it pushes update to your phone ...so if you have viper 2.4.0 just check for update as you would normally
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I think you meant 2.4.1.
ATT HOX Premium App--Stock is fine but modded is Creative
DESERT.TECH said:
Hmm I believe that viper 2.4.2 addresed camera issues. To get that version you have to do ota update and it pushes update to your phone ...so if you have viper 2.4.0 just check for update as you would normally
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I did the ota update and I'm running it now. Still no dice with the camera. Starting to get annoying. Can't find anything like this online. Any other ideas?
Edit: I am running elementalx kernel. There's another q in here about the same Rom with the same issue running beastmode kernel. Could this have something to do with it?
Sent from the best d*** phone I've ever used
Ya camera issue isn't new. I never had any issues but I suggest posting question in this thread as it specializes that Rom
http://forum.xda-developers.com/showthread.php?t=1868236
Sent from my HTC One XL using xda premium
DESERT.TECH said:
Ya camera issue isn't new. I never had any issues but I suggest posting question in this thread as it specializes that Rom
http://forum.xda-developers.com/showthread.php?t=1868236
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Got it. Thanks man. Think of anything else pm me,
Thanks!
Sent from the best d*** phone I've ever used
I am having trouble connecting to Wifi since I've started using 4.2.2 roms. There was no trouble when I was using a 4.2.1 rom. My wifi switch will not move to on. When you click it, it says turning on wifi but nothing happens.
I am currently using [Official PACman All-in-1-ROM Ver. 22.0.1[4-3-13] .
I have Hboot 1.14, S-On. Do I need to have S-Off to connect to Wifi?
Thanks
Anybody have an idea of what's wrong? I'm running Rohan's test kernel C
I'm not sure how to fix it, my fiance's phone has the same problem. I can tell you that having s-off won't fix it though, that merely turns security checks off, it's completely unrelated.
Sent from my One XL using XDA Premium
You have to flash boot.img through fast boot
Sent from my HTC One X using xda app-developers app
You probably need to update your firmware to JB. There is a conflict between ICS firmware and the JB base that can cause your wifi to go haywire.
You do need to be s-off first, however, or you may get a brick running the RUU.
Megadoug13 said:
You have to flash boot.img through fast boot
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
i always do "fastboot flash boot boot.img", not working.
iElvis said:
You probably need to update your firmware to JB. There is a conflict between ICS firmware and the JB base that can cause your wifi to go haywire.
You do need to be s-off first, however, or you may get a brick running the RUU.
Click to expand...
Click to collapse
how can i go about upgrading the firmware?
zooobair said:
how can i go about upgrading the firmware?
Click to expand...
Click to collapse
Run the 3.17 (non-US) or 3.18 RUU (AT&T), depending on what phone you've got. You need to be s-off first or you may brick if you are supercid. You'll lose root, but getting it back is just a matter of pushing custom recovery back on and flashing superuser. You'll also need to downgrade your touchscreen firmware to use an AOSP rom; there's a thread in the Original Development forum on how to do it.
I'm not guaranteeing this will solve the problem, but I was having similar issues and this solved it.
iElvis said:
Run the 3.17 (non-US) or 3.18 RUU (AT&T), depending on what phone you've got. You need to be s-off first or you may brick if you are supercid. You'll lose root, but getting it back is just a matter of pushing custom recovery back on and flashing superuser. You'll also need to downgrade your touchscreen firmware to use an AOSP rom; there's a thread in the Original Development forum on how to do it.
I'm not guaranteeing this will solve the problem, but I was having similar issues and this solved it.
Click to expand...
Click to collapse
i figured out getting s-off. so after i run the 3.18RUU, do i have to use the following root method?http://forum.xda-developers.com/showthread.php?t=2285086? Sorry if I'm asking so many questions, just a little confused.
No. You can just flash recovery after ruu. Then either flash a rom or flash superuser if you want to stay stock rooted.
Sent from my One X using xda app-developers app
Correct, once you're s-off, you can never permanently lose root. No need for any exploits as you'll always have the ability to push a custom recovery back on and flash what you like.
iElvis said:
Correct, once you're s-off, you can never permanently lose root. No need for any exploits as you'll always have the ability to push a custom recovery back on and flash what you like.
Click to expand...
Click to collapse
I've been thinking about RUU'ing and starting over. Been having wifi and connection problems in general. Seeing as im s-off, do i need to change my cid back before running the att RUU? I seem to remember there being a conflict when the JB ota came out.
venelar said:
I've been thinking about RUU'ing and starting over. Been having wifi and connection problems in general. Seeing as im s-off, do i need to change my cid back before running the att RUU? I seem to remember there being a conflict when the JB ota came out.
Click to expand...
Click to collapse
No need to change cid
Don't need to relock bootloader, change cid or anything else if your phone is s-off, to ruu.
Sent from my One X using xda app-developers app
ronnie498 said:
No need to change cid
Click to expand...
Click to collapse
exad said:
Don't need to relock bootloader, change cid or anything else if your phone is s-off, to ruu.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Word. Weekend project.
Thanks
so i did everything mentioned, put on the 3.18RUU, installed recovery, downgraded the touchscreen firmware, flashed new rom and kernel. still no wifi working. any other ideas guys?
Sounds like a hardware fault to me if the RUU didn't fix it unfortunately.
Sent from my One XL using XDA Premium
I would think so as well, but it is working fine for me if I use 4.2.1 roms. Do you think that's still the case?
Sent from my One X using xda app-developers app
If it's working PERFECTLY on 4.2.1 then I would say it's not a hardware issue. And I'd also say I'm completely stumped as to what's causing your problem.
Sent from my One XL using XDA Premium
Damn. It's definitely working ok on both the 3.18RUU and 4.1.2 rom. Not sure what other measures I can take to try to get it right.
Sent from my One X using xda app-developers app
Which 4.2.2 ROMs have you tried so far?
Sent from my One XL using XDA Premium
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
Pls help me..
I have no sound in my HTC one xl at&t..not in call or notifications or speaker..even I can't play music..I have tried to change different Rom but still no sound..
I'm s-off , hboot 1.11 running on MagioRom R4
Sent from my HTC One XL using xda premium
What have you done to troubleshoot it? Try running an RUU, if the problem with sound still occurs it's a hardware issue, if not it was a software issue.
Sent from my Evita
timmaaa said:
What have you done to troubleshoot it? Try running an RUU, if the problem with sound still occurs it's a hardware issue, if not it was a software issue.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for reply..which RUU i need to use..?do i need to relock my bootloader..?sorry i am new to htc one x..
If you're s-off and SuperCID you can use any RUU, you don't need to lock your bootloader.
Sent from my Evita
Im having this same issue. It started for me after flashing the 5.08 firmware on both sense and aosp roms. I RUU'd back to 3.14 and its still happening but it seems much more intermittent now. Of course my phone has been through hell so I'm not surprised that its having hardware issues.
princedarian22 said:
Im having this same issue. It started for me after flashing the 5.08 firmware on both sense and aosp roms. I RUU'd back to 3.14 and its still happening but it seems much more intermittent now. Of course my phone has been through hell so I'm not surprised that its having hardware issues.
Click to expand...
Click to collapse
Same here, did anyone find a solution? I went back and RUUed the JB release, still no sound. It recognizes when I put in the headphones, idk if that helps. When I got to youtube, the video doesnt come on and it says touch to retry, same with any audio programs.
If you have no sound after an RUU you must likely have a hardware problem and will need it to be physically repaired.
Sent from my Evita
Yeah and the logcat will reflect the hardware failure. I don't know about you but I had also lost audio on phone calls. So I had to get a new phone. For what it's worth it worked a little better on kitkat but that means it would work for about 20mins before crapping out as opposed to 10.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
princedarian22 said:
Yeah and the logcat will reflect the hardware failure. I don't know about you but I had also lost audio on phone calls. So I had to get a new phone. For what it's worth it worked a little better on kitkat but that means it would work for about 20mins before crapping out as opposed to 10.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Could I identify what part is not working with logcat (never used it) and replace it myself? or is all lost?
Same here but i lock my bootloader and now it's work fine
the problem comes when u install many many of custom ROM's
just flash RUU and then re-lock your bootloader