Related
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
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
Hey guys
My brother got the sensation a while ago, so i took it, rooted, and flashed a new rom.
I also think I updated the firmware because its running ICS(used to be 2.3).
Anyway, the phone is very laggy and slow plus when I get a call most time it reboots.
I flashed cyanogen rom (4.2.2) and through the set up it rebooted.
I wiped every thing before I installed CM.
Has any body experienced this before? any ideas?
Thank in advance m8s:good:
Provide more information. Post your bootloader details here.
Sent from my HTC Sensation
mr.dj26 said:
Hey guys
My brother got the sensation a while ago, so i took it, rooted, and flashed a new rom.
I also think I updated the firmware because its running ICS(used to be 2.3).
Anyway, the phone is very laggy and slow plus when I get a call most time it reboots.
I flashed cyanogen rom (4.2.2) and through the set up it rebooted.
I wiped every thing before I installed CM.
Has any body experienced this before? any ideas?
Thank in advance m8s:good:
Click to expand...
Click to collapse
what do you mean by rebooted...stuck on htc screen??
did you root with S-Off or On..provide more info
thx for the replies
the phone is S-OFF (Revolutionary)
Hboot 1.27.1100
Radio 11.22.3504.07_M
murtazasamiwala said:
what do you mean by rebooted...stuck on htc screen??
Click to expand...
Click to collapse
Nop, I mean it just restarts and works fine.
thank you
You said it lags? Android 4.2.2 should have no lag at all...
Sent from my HTC Sensation
AndroidSupporter318 said:
You said it lags? Android 4.2.2 should have no lag at all...
Sent from my HTC Sensation
Click to expand...
Click to collapse
lol, thats the problem i guess. Its not lagging on 4.2.2 but when I get a call it reboots..
any ideas guys? could it be a hardware issue?
guys after flashing CM10 the phone works great but it over heats a lot and most of the time when I get a call, I answer, it reboots..
Whats the problem with this phone
I don't think it's a hardware issue. You could try a stock ROM or an RUU to see if the problem is fixed. Try clearing the cache and data from the phone app and see if that fixes it.
Sent from my HTC Sensation
AndroidSupporter318 said:
I don't think it's a hardware issue. You could try a stock ROM or an RUU to see if the problem is fixed. Try clearing the cache and data from the phone app and see if that fixes it.
Sent from my HTC Sensation
Click to expand...
Click to collapse
Before installing CM10, I cleared the cache and date, rest to factory and wiped dalvik cache. I always flash roms on my oneX and DHD but never experienced this problem.
I noticed something, after booting in CM10 for the first time, the prior venom wallpaper was there which was awkward...
could be this the recovery? Im currently using CWM flashed directly from play store.
PLZ help guys this phone is becoming very annoying, almost every call I receive it will reboot
Hmm...I am running out of ideas. I think you need to somehow re-install the phone.apk, but this is coming from a semi-noob. You might need a pro to help you on this.
One more idea... Did you try putting a piece of cardboard by the battery to keep it in properly (although it's only when you open the phone app)
Sent from my HTC Sensation
Hi
Which developer rom are you using and also which kernel you are using ... Try to change your kernel ...
Sent from my HTC Sensation Z710e using Tapatalk 2
Flash 3.33 firmware. Try a Rom with sense 3.6. Elegancia works well. Then try different kernels. Lets see if u still have these issues.
Sent from my HTC Sensation XE with Beats Audio using xda app-developers app
Thanks guys. I will try different roms and kernels and ill post back.
Ill also try the card bored thing because I thing it reboots when I move the phone vertically.
Ill post back when I find the right solution.
Thanks again
Here it is...
As I mentioned in the first post that my brother uses the phone.
Sorry to disappoint you but the problem was from the battery
I dont know how i did not think about it.
I folded a piece of paper and placed it behind the battery and since then it never rebooted
THANKS GUYS!!!!
i've been messing around with roms trying to see if there was any different results to my network going to sleep and all my roms do the same thing. When i lock my screen ten minutes later i get a X through my cell network as if it was disconnected and it is. Upon unlocking the screen my phone says "prepairing internal storage" then my network is back up. I have turned off the options that say sleep data connection when screen is locked and the other one that says sleep data connection after long periods of no use/idle.
S-Off
Bootloader unlocked
TWRP 2.6
superSU installed
Roms tried scotts clean rom 7 (4.2.2 JB sense 5) Viper rom same os and sense 5
Tried a couple 4.4 roms and they fail to install during recovery
Could it be a problem with a loose SIM tray? Mine used to do that back in July, and HTC sent me a SIM tray for free
Sent from my HTC One XL using XDA Premium 4 mobile app
pandasa123 said:
Could it be a problem with a loose SIM tray? Mine used to do that back in July, and HTC sent me a SIM tray for free
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Doubt it, its never done this when i was using stock rom past few days been using custom roms and it started doing this right away. Thinking maybe i used tool/s intended for the xl to unlock my phone, or its some where in the software thats bugged out cause i did some thing wrong. Although every thing seems to be working fast and cleanly except my cell network shutting off when i lock the screen. Being a noob just hoping some one keys up and tells me how to fix this like flash a diff radio version or some thing.
This is probably TMI but this is what the phone reports to me under info
Bootloader Unlocked
TWRP 2.6
Phone name and model number HTC One X AT&T
Android version 4.2.2
HTC Sense 5.0
Software Number: CleanRom 7.0 P1
HTC SDK API Level 5.41
Kernel Version: [email protected]#1SMP PREEMPT
Baseband Version: 0.24p.32.09.06_10.130.32.34L
Build Number 5.08.111.2 CL227463 release-keys
Browser Version webkit/534.30
Flash Beastmode kernel or update firmware to 2.15 in order to fix signal drops.
Sent from my One X using XDA Premium 4 mobile app
KungFuCracka94 said:
Flash Beastmode kernel or update firmware to 2.15 in order to fix signal drops.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Where do i see my current firmware version? under firmware/software version info on the phone i posted. Sorry i'm still a newb and the numbers listed confuse me lol
How are your network drops?
Sent from my One X using XDA Premium 4 mobile app
KungFuCracka94 said:
How are your network drops?
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried to flash that kernel with both roms i am using and it errors and won't go through, also the firmware aka hboot is 2.14 i believe on my device for the life of me can't find a download of a hboot for my device. Found a thread stating i need my cid to lookup proper firmware for my device but isn't my cid all 1s now from being unlocked? Any way i saw yet another post that said to turn my data connection off and on then turn data roaming on then back off, followed by a reboot this actually seemed to fix my cell network dropping but!!!.... lol now my wifi won't enable and the wifi is marked with "ERROR" i'm going nuts maybe i screwed all this up by originally not having S-OFF or some thing.
Oh and i tried the fix wifi app recommended here in the forums and the app can't start the wifi just says its stuck.
Do you know how to access your bootloader?
It seems like your guessing with important details.
Sent from my One X using XDA Premium 4 mobile app
---------- Post added at 09:28 PM ---------- Previous post was at 09:11 PM ----------
I'm not sure why Beastmode isn't working for you. Maybe bad download. If you give up then you can upgrade firmware using the OP instructions found here:
http://forum.xda-developers.com/showthread.php?t=2423735
Sent from my One X using XDA Premium 4 mobile app
KungFuCracka94 said:
Do you know how to access your bootloader?
It seems like your guessing with important details.
Sent from my One X using XDA Premium 4 mobile app
---------- Post added at 09:28 PM ---------- Previous post was at 09:11 PM ----------
I'm not sure why Beastmode isn't working for you. Maybe bad download. If you give up then you can upgrade firmware using the OP instructions found here:
http://forum.xda-developers.com/showthread.php?t=2423735
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ooo says S-ON and it is hboot 2.14.0000
So if i manage to turn S-OFF i should be able to flash beastmode? Not sure why the tool i have didn't work for the S-OFF function.
Beastmode is OK for S On devices. It should fix the problems you mentioned.
It sounds like you have lots of reading to do. In general, you shouldn't rely on tools and one click methods. Know the processes that they are actually performing.
Sent from my One X using XDA Premium 4 mobile app
Thread cleaned and let's stay on topic from here thanks guys
No. Contact HTC for a sim card tray. That's exactly what it sounds like. I got mine and never lost connection again. But I do haft a say that u do need a good kernel when it comes viper xl ROM.
Chris B.
While that is true in some cases of signal problems, it isn't in this case. Changing the SIM tray won't stop the problem from happening as this isn't a physical problem. The phone is shutting down the cell connection when it's in sleep mode and is unable to initiate a connection again when it's woken. This is a case of mismatched firmware that's common on every single Sense 5 Android 4.2.2 ROM. The solution is to upgrade to the firmware package (2.15) that was shipped with the Sense 5 update and was supposed to be used in conjunction with the ROM for proper operation. Another option is to flash the Beastmode kernel. Please make sure you're giving the right advice.
Sent from my Evita
Its not a matter of"advice" the sim card tray Is a known issue with the one x. It was a suggestion...not advice. Lol. I figured that hed like to be made aware of the tray issue. I already know Abiut the kernel, and yes that was a fix. Just thought i would share the info!
Sent from my Desire HD using xda app-developers app
Yeah ok, but my point was that in this case it's irrelevant because that isn't the cause of the problems. In fairness your first word was "no", in order to disagree with the previous correct solutions that were given.
The SIM tray isn't "exactly what it sounds like" at all. You hadn't considered the fact that the signal is lost during periods where the phone is sleeping. If it was the SIM tray that was the problem the phone would be losing signal at any random time, not confined to sleep periods.
I'm all for sharing fixes and advice, but the fix you mentioned is completely irrelevant to the problem that this thread is discussing. Imagine the OP decides to take your advice instead of the correct advice: he contacts HTC, waits a week or two for a SIM tray, gets it, pops it in, and hey what do you know it's still losing signal during sleep periods. That's a week or two of having to put up with signal losses because someone shared a fix that wasn't relevant to his actual problem. Yes the symptoms are similar (generally speaking), but when you look harder at it the diagnosis is entirely different and therefore the solution is entirely different. I'm not trying to sound harsh, but this is after all a forum dedicated to helping people by giving them the correct fix to their problem.
Sent from my Evita
chrisb906 said:
It was a suggestion...not advice. Lol.
Click to expand...
Click to collapse
That seems like a ridiculous distinction to say the least.
Its pretty clear (as timmaaa suggests) that if the problem arises after flashing a Sense 5 ROM, and wasn't present before; then its a result of the Sense 5 sleep function and radio incompatibility (fixed with 2.15 firmware of Beastmode kernel).
So if i have TWRP 2.6 and S-ON is not a issue for flashing beastmode kernel how come it fails during flash?
WinDroid HTC One XL Toolkit 1.1 wants me to flash stock ruu as part of S-OFF process.
Below is what i believe to be the stock rom for the AT&T One X got the link from you guys at XDA
OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k.zip
Oh and what version of beastmode should i be using i have 3.0 and 3.5 reloaded and i can't find any install instructions to tell me if it has its own installer or i can use TWRP
The most important thing I have to say right now is do not run the RUU yet! If you have SuperCID (which I'm guessing you do) you will definitely brick your phone, we don't want that. There's a bug with the jb RUU that causes it to fail halfway through when it sees you have SuperCID, basically SuperCID + s-on + jb RUU = brick. So check your CID first using this fastboot command:
Code:
fastboot oem readied
If it comes back as 11111111 or 22222222 you have SuperCID. Post the result here anyway.
At this point your best and easiest option is just to get s-off so you can update to the 2.15 firmware package. The Beastmode kernel is s-on friendly but plenty of folks have had trouble installing it. There are two s-off methods for our device, Facepalm and Rumrunner. I'd suggest you try the Rumrunner method, it's brand new and I haven't personally tried it because I'm already s-off but it looks like a piece of cake to get done. Facepalm can be a bit tricky. You'll find a thread started by me in our general section for the Rumrunner s-off method. Once you have s-off you can update your firmware and you should have zero issues with Sense 5 ROMs after that. It also means you can run the jb RUU without bricking, SuperCID + s-off + jb RUU = no worries. Plus you no longer need to flash the boot.img from a ROM/kernel with fastboot and you have s-off. There are other advantages to having s-off but those are the main ones.
Sent from my Evita
Darthdiddy said:
So if i have TWRP 2.6 and S-ON is not a issue for flashing beastmode kernel how come it fails during flash?
Click to expand...
Click to collapse
Do people not bother reading through the thread (at least the last few pages) for things they flash anymore? I do this before flashing just about anything, as it gives a good indicator of what issues others may have had, and the solutions.
This is a somewhat known/common issue. Apparently the solution is to flash Beastmode 2 first, than 3/3.5.
Don't use the Windroid toolkit, as I stated above you'll brick if you RUU, plus you definitely do not need to run an RUU to get s-off. I'm not sure why it's asking you to do that. Those toolkits are nice and easy and all that but in my opinion they're bad news. They allow users to get things done very easily, but the problem is they completely remove the learning aspect of the whole procedure. Trust me, it's better to learn how to do this manually with fastboot and adb, you gain a much better understanding of Android by doing things manually, and the day will come when you need that knowledge to recover from some mishap.
Sent from my Evita
---------- Post added at 05:38 AM ---------- Previous post was at 05:36 AM ----------
redpoint73 said:
Do people not bother reading through the thread (at least the last few pages) for things they flash anymore? I do this before flashing just about anything, as it gives a good indicator of what issues others may have had, and the solutions.
This is a somewhat known/common issue. Apparently the solution is to flash Beastmode 2 first, than 3/3.5.
Click to expand...
Click to collapse
I don't think they do, it's very apparent they don't. I've already given my $0.02 on that situation in this thread so that's all I'm gonna say.
Sent from my Evita
Hello guys, my sensation is like 18 months old and several months ago the camera just stopped working. When I try to open it there is a message that says "unable to start camera".
I'm sure that it's not a software problem, I switched roms, wiped everything, restored, anything. Another weird thing is that every once in a while the camera works for few minutes or more, and then the problem returns. I'm considering buying a new camera from eBay and install it myself but I'm not sure it'll solve it & I'm afraid to ruin the device. Any help please?
Sent from my HTCSensation using xda app-developers app
ItayPBM said:
Hello guys, my sensation is like 18 months old and several months ago the camera just stopped working. When I try to open it there is a message that says "unable to start camera".
I'm sure that it's not a software problem, I switched roms, wiped everything, restored, anything. Another weird thing is that every once in a while the camera works for few minutes or more, and then the problem returns. I'm considering buying a new camera from eBay and install it myself but I'm not sure it'll solve it & I'm afraid to ruin the device. Any help please?
Sent from my HTCSensation using xda app-developers app
Click to expand...
Click to collapse
Have you ever dropped your phone before? You might have caused hardware damage from dropping it.
Sent from my Nexus 4 using Tapatalk
Of course it's have been dropped accidently from time to time, what's weird to me is that the camera sometime works for very short period and then the problem returns.
Sent from my HTCSensation using xda app-developers app
Have u try a RUU.exe to know if it only a ROM issue or hardware issue§???
I'm sure it wouldn't solve it because I didn't switch ruu and still several weeks ago the camera worked for few hours.
Sent from my HTCSensation using xda app-developers app
I think it's the software issue try ruu.exe...I believe it will work..if it were hardware related the camera won't function at all...
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Premium 4 mobile app
ItayPBM said:
I'm sure it wouldn't solve it because I didn't switch ruu and still several weeks ago the camera worked for few hours.
Sent from my HTCSensation using xda app-developers app
Click to expand...
Click to collapse
Try doing a firmware upgrade. Get 3.33 universal, then try again. Or if you're not s off, user rug.
Happy to help.
Far_SighT said:
Try doing a firmware upgrade. Get 3.33 universal, then try again. Or if you're not s off, user rug.
Happy to help.
Click to expand...
Click to collapse
Hi,
I have same problem. I did system format and the camera worked for a while. But now even if i do system format, camera doesn't work. I also think it is a software problem. Sometimes camera comes back even when i clean dalvik cache.
When i first noticed camera is not working, i had 4.0.3 android. This is when mobile network didn't work, i restarted phone and network worked, but this was when camera did not start first time.
I have CM 10.2 albinoman887, base band 11.76A.3504.00P_11.24A.3504.31_M
Just flash official Rom using RUU.exe....problem will be solved...I hope so
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Premium 4 mobile app
Firmware update didn't work. Where can I download ruu? The downloads on the thread aren't working.
Sent from my HTCSensation using xda app-developers app
ItayPBM said:
Firmware update didn't work. Where can I download ruu? The downloads on the thread aren't working.
Sent from my HTCSensation using xda app-developers app
Click to expand...
Click to collapse
did you check here?
http://forum.xda-developers.com/showthread.php?t=1672425
Just to make sure, what does it mean to flash ruu? It makes the device completely stock, without root, s-off, bootloader etc...
Sent from my HTCSensation using xda app-developers app
rzr86 said:
did you check here?
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
i checked my firmware and it's 3.33.401.53. i saw that yours is only 3.32.401.5. can it be that this difference cause the camera not to work? though i saw that mine is also for htc sensation.
---------- Post added at 09:41 PM ---------- Previous post was at 09:23 PM ----------
bashirchak said:
Just flash official Rom using RUU.exe....problem will be solved...I hope so
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Premium 4 mobile app
Click to expand...
Click to collapse
why? ruu contains all kernel that controls camera? if yes, what if later i want up to date rom like CM 10.2 rom which will overwrite kernel? actually, i flashed stock rom once and for my biggest surprise camera still didn't work there.
Sometimes camera still come back if i do a dalvik cache wipe and reboot and something, i've never could remake these steps to identify the cause.
do you think i should still flash official ruu? or firmware difference makes any difference? i.e 3.33.401.53 or 3.32.401.5 for HTC sensation.
Zeghra said:
i checked my firmware and it's 3.33.401.53. i saw that yours is only 3.32.401.5. can it be that this difference cause the camera not to work? though i saw that mine is also for htc sensation.
---------- Post added at 09:41 PM ---------- Previous post was at 09:23 PM ----------
why? ruu contains all kernel that controls camera? if yes, what if later i want up to date rom like CM 10.2 rom which will overwrite kernel? actually, i flashed stock rom once and for my biggest surprise camera still didn't work there.
Sometimes camera still come back if i do a dalvik cache wipe and reboot and something, i've never could remake these steps to identify the cause.
do you think i should still flash official ruu? or firmware difference makes any difference? i.e 3.33.401.53 or 3.32.401.5 for HTC sensation.
Click to expand...
Click to collapse
firmware has nothing to do at all
besides you have the latest version
also the only difference between 3.32 and 3.33 is radio upgrade
if you are on S-OFF and supercid you can use any ruu.exe
otherwise use the one which corresponds to your region(same firmware or higher) and cid
then we will see if it is software issue or not
rzr86 said:
firmware has nothing to do at all
besides you have the latest version
also the only difference between 3.32 and 3.33 is radio upgrade
if you are on S-OFF and supercid you can use any ruu.exe
otherwise use the one which corresponds to your region(same firmware or higher) and cid
then we will see if it is software issue or not
Click to expand...
Click to collapse
I used this RUU exe:
RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed
Camera and flashlight didn't work
then I used this RUU exe:
RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed
flashlight came back, but camera still doesn't work.
Do you think that sd card format would help? It seems to me that dalvik cache contains something that prevents my camera running.
Zeghra said:
I used this RUU exe:
RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed
Camera and flashlight didn't work
then I used this RUU exe:
RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed
flashlight came back, but camera still doesn't work.
Do you think that sd card format would help? It seems to me that dalvik cache contains something that prevents my camera running.
Click to expand...
Click to collapse
you could try but after 2 ruu.exe and still the same then consider it as a hardware issue
rzr86 said:
you could try but after 2 ruu.exe and still the same then consider it as a hardware issue
Click to expand...
Click to collapse
Thanks for your help anyway. I expected that. I have one concern though, front camera doesn't work either.
Zeghra said:
Thanks for your help anyway. I expected that. I have one concern though, front camera doesn't work either.
Click to expand...
Click to collapse
hardware mate
rzr86 said:
hardware mate
Click to expand...
Click to collapse
Still didn't give up
I checked my logcat and found an error message (logcat: mm_camera_init: controlfd is invalid) about camera that I also found here https://bugzilla.mozilla.org/show_bug.cgi?id=782456
From what I understood there, it is not a hardware problem, but maybe I'm wrong.
Can you say anything about it?
Zeghra said:
Still didn't give up
I checked my logcat and found an error message (logcat: mm_camera_init: controlfd is invalid) about camera that I also found here https://bugzilla.mozilla.org/show_bug.cgi?id=782456
From what I understood there, it is not a hardware problem, but maybe I'm wrong.
Can you say anything about it?
Click to expand...
Click to collapse
i really don't know mate
this is beyond me
but if it isn't a hardware then why ruu.exe couldn't fixed it?