No sensors/GPS with custom roms - HTC One X

Last weekend I flashed an old HTC One X I had lying around with This Cyanogen
After a while I noticed location services was barely working.
Using androsensor I saw that, apart from sound and battery, none of my sensors were registering anything (waiting for event, or zero), and GPS saw NO satellites at all. (Sony in at the same time saw 21)
Being my first flash, I was thinking user error, everything else was working but hey.
I tried this resurrection remix, exactly the same result
I went back to old storage layout and tried the latest cm-11 snapshot, no difference.
Since I didn't think of testing the gps & co before flashing, I wanted to try to return to stock rom. but that's not as easy as it sounds apparently.
Backups got wiped while I was trying to get my first flash, and online references and links to tools are mostly invalid now.
I tried an original recovery and locking the bootloader, but got an error running the presumably correct RRU.exem, probably due to the 1.7x HBOOT I have.
There might be a hardware issue, I opened the device to check a dicky USB connector, but don't see any damage.
Finally tried This cyanogen again no difference.
So is there anyone left here with some more experience/insight that can help me get the sensors working in custom rom, OR be able to get me back to stock, so I can test them there.
If you need any more details, just ask.

Related

no service at all after routine flash

Just flashed to a new rom yesterday and now my phone is completely incapable of getting a signal.
I've flashed plenty of roms and they've all worked fine until flashing to a 21889 rom yesterday (firestormLeo v5.5). Not a single bar of service since. Text messages don't get received and no data either.
I reflashed, hard reset after the flash, updated the radio, flashed back to an older rom that worked, and hard reset again.
Nothing works! I now have a completely unusable phone (phone-wise). It completely works otherwise (music, sync to pc, wifi etc) although it does seem to get warmer than usual. I'm assuming that's because it's trying to grab a signal or something.
Anyone have any ideas on whats going on?
I would try flashing the original rom/radio that came with your device including removing the spl and seeing if that fixes it.
If that doesn't fix it, then you are all prepared for warranty service.
If it does fix it, then you can reflash your favourite rom and it should still work. But sometimes flashing an official rom can fix things. I know back with my Kaiser it was advised to always flash an official rom between switching from an unofficial to another unofficial.
thanks for the suggestion!
just did all that and now i'm on stock rom and removed spl but it still has zero signal/service.
i bought this tmo tp2 from craigslist so i'm not sure if i'm covered by warranty. where do i go to get this fixed? or am i screwed
anyone else have any idea whats going on?
I had a similar problem with you(http://forum.xda-developers.com/showthread.php?t=616426), and have been waiting for some reply since last night, though got none, but the problem disappeared on it's own.
I continuesly flashed and flashed official ROM's and Radio's, totally gave up at the end, charged the battery to 100%, removed battery and let it like that for 5 hours, did an hard reset, and well, working as well as new.
It's a T-Mobile version as well, though my problem was losing signal continuosly and asking for PIN again and again every 5-10 mins. HTC support offered me to use another SIM card today, since I asked what could I try last night, though I didn't have the need for it =)
A lot of roms do not come with a radio so you may have to get one and flash it. If you put stock rom back on make sure it has a radio as well. Make sure the radio matches the rom and the ril.dll is the right one.
I have not had the problem but have read about others flashing new roms and no signal only to find out they had to write a radio as well.
i'm certain i have the radio flashed on it and it isnt the problem.
just took the battery out and hoping it'll somehow fix itself in a few hours.
I would also recommend to flash the shipped stock rom. Go to htc's support/download page and download the rom they have for the t-mobile touch pro 2.
If that doesn't work, take it in for warranty with t-mobile. I purchased a used at&t tilt off craigslist and had an issue with it. Took it into at&t's device support center and they replaced it no questions asked.

[Q] bluetooth fails to enable

Hi,
Im really hoping someone can help me here.
Yesterday my phone threw a wobbly and started to loop boot to the htc logo, it had happened before but i payed little attention. When i removed the battery to reset it i found that it had corrupted my whole sd card, stange file names etc was everywhere.
i decided it was time for a clean start and super wiped the lot then installed arhd,
everything went fine until i went to use bluetooth, nothing i say or do will enable it.
Ive since have wiped and flashed leedroid, arhd, and runny but cant get this little but one of the most used features on my phone to activate.
Ive also reflashed the radio, does it sound like a hard ware failure to you guys?
is there anything that i could have missed, i would also like to add that i havent re installed any previous apps etc and bluetooth still fails to activate.
thanks
sorry to reply to my own thread, but i think i just worked it out. After reading my own post i though about the sd card, i decided to remove the card and reboot, voilia!! the bluetooth is now functioning!!, totally confused now as to why an sd card can affect the running of a seperate piece of hardware!!
ok, it happened again a few time since i posted this thread.
it happened again yesterday and no matter what i done it wouldnt come back.
So i decided to do a nandroid backup and wipe, install a new rom then recover my nandroid backup.
this solved the problem, im not sure what is causing the bluetooth to just die like it does but now i have to keep another rom on my card and a nandroid back up just to get the bluetooth to work- seems strange as the backup is the same drivers etc and stops working. must be hardware...
this dosnt seem to be rom specific as well as its happened now on leedroid, runny, 3dmix, and anotherone i forget the name.
roll on htc edge as im pretty sure i may have a impending hardware failure on the bluetooth radio

(A Type of) Random Reboot Problem Solved?

Short version:
Use CWM or TWRP to (1) format sdcard, (2) erase dalvik cache, (3) erase cache and (4) factory reset. This seems to resolve at least one source of random reboots. If installing a new ROM, do that first and then followed by the four steps, then boot into the new ROM. Step (1) may be the important one (in which case it might, in principle, be possible to solve the problem while saving userdata), but I don't know.
UPDATE: It was working fine and I had to spoil it all by installing MIUI, just for kicks. Now, the old problem is back and the solution above doesn't seem to work. Looks like this is not a completely reliable solution...
* * * * *
Long version:
My wife's GNex was in a very bad way. It is entirely stable in Android 4.0.2. But if either upgraded or flashed to anything else, will randomly reboot. Actually, it's not even that random--it will reboot on its own within a couple of minutes of idle with the screen off. I tried all sorts of things--flashed different ROMs, radios, etc.--factory reset multiple times. Googling turns up lots of chatter about random reboots but little by way of viable solution. I figured that the problem may be hardware related. But all Samsung's servicing did for me is to return the unit to 4.0.2. At that time, 4.0.4 was just released and the local servicing centre hadn't even received their copy of the ROM (for yakjuwx). In the end, I 'solved' the problem by rooting and disabling the OTA update notification. (My wife wasn't bothered by the fact that she wasn't running the latest Android version. And the phone works fine in 4.0.2 otherwise.) Work and life caught up and I didn't think much of the matter after that.
That was about a year ago.
Recently, I migrated my wife to a brand new GNex, and took the opportunity to try my hand at solving the problem again. I flashed the latest 4.3 ROM, the latest stable CM10.1, Paranoidandroid, etc. But no matter what I tried, somehow, the phone is stable only with Android 4.0.2 (ICL53F). A chance find online mentioned something about data corruption on the sdcard as a source of problem, and that the usual factory reset doesn't actually reformat the sdcard (it only marks it as empty). Putting 1 and 1 together, I used CWM to do the things listed above (see "short version") and now, the phone is running stock 4.3 (JWR66V), stable CM10.1 and Paranoidandroid without random reboots so far. So now, I am a happy camper, though with one extra, fully functional white GNex.
Footnote: If you don't understand what I said in the short version, it's best you don't try doing anything yourself without first reading up on fastboot commands. This is one place to start. I am not responsible for anyone bricking their device fooling around.
Thanks for reading.
Update to my adventure.
Just about resigned to the fact that the phone is back to its old ways. The old tricks no longer work. What happened next?
1. Left off for more than a day (I gave up).
2. Installed AOSPA PARANOIDANDROID 3.96--using CWM, installed ROM, GApps, wipe dalvik, wipe cache, format sdcard.
Weirdly, the phone now seems fine. It hasn't rebooted by itself after 30+min in sleep. The old problem was that it will invariably reboot by itself in within 2 minutes from screen off so even if there are other problems, the old one is not there anyway.
Something in the steps above seems to have made a difference.
Still monitoring.

Camera frozen on black screen no matter what I do

I've done a lot of digging through the forum and can't find an answer, so forgive me if this is an already-answered question.
I have a T-mobile S4 with a camera stuck on the classic "updating camera firmware" error message with black screen. If I open Snapchat the front facing camera will work, but with a slight delay in projection.
Here's the thing...this has happened on two separate phones now and on both of them it happened about 48 hours after I signed into the phone with my google account. Is it possible there is some kind of malware attached to my google account?
In the newest phone I have done a clean full wipe using TWRP, then Odin-flashed a full firmware package I found here on xda (recovery, OS, modem, kernel). Cache wipe and factory reset immediately after rebooting from Odin mode. Still have problem.
Have switched out known good cameras from other phones, and the phone I'm working on was functioning perfectly until I signed into it with my account. Totally stumped here, and really need some assistance.
Phone is:
M919 logic board in I337 body
Kitkat 4.4.4
Baseband: M919UVUFNH7
Kernel: 3.4.9-6281449, [email protected] #1
Build: KTU84P.M919UVUFOK3
Security software version: MDF v1.0 release 3, VPN v1.4 release 2
If anybody's got some ideas, please let me know!
Ok, no answers yet but plenty of views, so either this is an extremely rare issue that no one knows a solution for, or it's a ridiculously stupid question that everyone knows the answer to. I'm going to try and keep a log of what I'm doing with this phone in case any other rookies need assistance in the future.
So far I've flashed three different versions of stock Kitkat onto the phone....OH3, OK3 and NH7. When I flash OK3 my build number doesn't match my baseband (baseband reads NH7)...not sure what's going on there. Also, if I flash OK3 I lose my wifi....do not have this problem with other versions of firmware. Each flash is done after a full clean wipe with TWRP.
I found a thread that mentions an almost identical camera issue being caused on an M919 that was flashed with Nottache Xposed framework for AT&T phones. The OP said they could fix the issue by wiping the framework off the phone. Since my M919 motherboard is installed in an I337 body, I'm wondering if this is something related to a compatibility issue between T-Mobile and AT&T components. Best lead I've got so far.
Two posts have mentioned a fix. One says he opened Google Edition Camera Photosphere and his problem went away. He was running a different machine than mine so I haven't tried this yet, but I'm doubtful. The other user said they have only been able to solve the cam issue by installing a stock modded kernel by @jovy23. All the links I've found to this kernel are dead now, so no dice there.
I'm gonna put my M919 motherboard into an M919 body, wipe and flash stock rom again and see if somehow that does anything.
As a side note, I started getting "SIM not inserted" errors just before I began flashing different roms, and since the initial flash I've lost my SIM completely. So now I've got no camera, no SIM card being read, and sometimes losing wifi. I need this phone for work, so this is kind of sh*tty.
You cant downgrade once youve updated to OK3. The order would have to have been NH7, OH3 then OK3. It seems like mabey its not flashing correctly. Try a different odin program 3.04 3.07 3.09 are good ones. Flash it twice, untick auto reboot and manually power off and back into download mode and flash again. Dont use adv reboot menu to boot into download or it may not flash correctly. If that doesnt work I'm not sure what else to try. Good Luck
Ok, latest update for future readers...
It seems that lordodin912 is right when he says that flashing to OK3 means you can't flash backwards to a previous baseband/build. I hadn't seen that info anywhere so I didn't know about it. I'm not sure how to go about finding this kind of info on the forum but it would have been nice to know ahead of time. Anyhow...thank you for that information lordodin.
Here's where I'm at now:
-I was originally on NH7 with the camera error and sim card error. Flashed NH7 full stock after doing a full wipe and still had problems.
-Flashed OK3 full stock after full wipe and still had the problems, and also lost wifi capabilites (as in the phone wouldn't turn on wifi at all). At this point the baseband read as NH7 but the build read as OK3. I don't know why.
-Tried flashing OH3 after that (didn't know any better) and it wouldn't take. At this point wifi capabilites returned but still no cam and not reading sim card.
-Flashed OK3 again and wifi returned but still no cam and no sim. A couple hours later I powered the phone off and then back on, and Samsung then notified me of OTA updates. This update notification hadn't appeared before I manually rebooted the phone. I took the updates and now have wifi, sim card is being read, and my camera appears to be functioning properly as well. About 20 minutes or so after the updates are applied, the sim card error returned and told me to restart the phone. I did so and now the phone is reading the sim card again.
Right now my best guess is that when I was on NH7 I had accidentally made some app and update settings changes that prevented me from receiving some of the important OTA updates connected to camera and sim functioning, and this caused incompatibility between certain parts of the firmware that had been updated and others that had not. Trying to flash OH3 failed to solve the issue because I had already flashed OK3 before that and you can't go backwards from OK3. I don't know why the initial OK3 flash failed to fix anything, but I'm guessing the flash just didn't take as well as I thought it did. Flashing OK3 twice in a row seems to have done the trick, I presume because it reset and updated everything so that all firmware was compatible with itself.
I don't know how this could have happened (I try to be very careful about what I freeze and uninstall), but it's the most likely culprit because after flashing the latest firmware manually (twice) and allowing OTA updates my phone returns to proper function. Why OK3 didn't work correctly at first is beyond me....I don't see why it should have taken a few hours or a second reboot for OK3 to begin offering updates but whatever.
I'm doubtful that the camera will continue to work after the next 48 hours, but we'll see. I'll report back in with what happens after a few days go by.
Leaving an update here as I said I would.
For two months the phone has been functioning properly. Camera, sim and wifi have all been good. About one week ago my camera started acting glitchy again and then stopped working. The problem is the same as before- upon opening camera app the screen is black with a message saying "updating camera firmware", then nothing happens. This occurred around the same time I started using google hangouts frequently...don't know if that is related to the issue or not.
Yesterday the phone began showing the error message about sim card not being read, and then today it stopped reading the card altogether.
I repeated the same procedure that seemed to fix these problems two months ago and it hasn't done the trick. Full clean wipe of phone using TWRP, then installation of Chainfire's Autoroot, then flashed OK3 stock firmware twice with battery pulls between installations. Factory reset immediately after install of stock ROM. When connecting to wifi, no OTA updates appear. Camera not functioning, sim card not being read.
Phone shows baseband and build number are matching. I have no ****ing idea what the problem is with this phone. Beyond frustrated.
Anyhow, I'll keep updates going as long as I am working with this thing, maybe it'll help someone later. Anyone knows anything that could help, feel free to chime in.

Back camera not working/Flashlight not activating on stock, custom ROM or safe mode

Hi all,
I've been having quite a few problems with my month-old HTC 10, specifically with the camera (and the WLAN coverage, but at least that's working somewhat!) I finally unpacked it last week and have spent the whole week since attempting to fix the "Camera has stopped/Unable to connect to camera" problem. The selfie camera, however, is perfect and can be used in other apps, but attempting to switch to the camera on the back results in a freeze/force close. Considering I decided on the HTC 10 because of the camera quality, I'm a bit disappointed so far. A google search reveal a number of people having the same problem, but no real solution. Here's what I've done so far:
- Set up phone, comes with Nougat 7.0. Camera works at first, though seems to have problems with the auto focus. Camera app then updates overnight and stops working. Clear data/cache, remove updates, hard reset - no good. Flashlight does not work either, simply says "loading..." and stays like this indefinitely until closed.
- Factory reset, no change. Switch to safe mode, no change. Decided to unlock bootloader and install custom ROM after hearing that would fix it (I know, I know...I should have just sent it back at this point). Install Viper 5.10 + root with magisk, camera and flashlight still not working. Safe mode, not working. Full wipe in TWRP, RUU back to stock firmware (CID: HTC_034, flashed 2.41.401.3 signed firmware). Set up phone again on stock firmware, still no change in camera or flashlight.
- Install LeeDroid 10 3.7.0 custom ROM, root with magisk. I get a breakthrough here; turning off "OK Google" in settings gets the camera and flashlight working again! Still have the "laser autofocus blocked" issue, but I figure I'll deal with that later. Backed up with TiBu.
- Next day, decide to use a ROM that includes the latest security patches (got a bit annoyed waiting for HTC to push out the European updates, still on 1st January patch) so went for Resurrection Remix. Wipe, clean install etc. Camera stops working again, no change in safe mode. Wipe, clean flash back to LeeDroid, camera is no longer working, in normal mode or safe mode.
- Went through a bunch of custom ROMs at this point; ICE, Dirty Unicorns, LineageOS, then decided to try RR, LeeDroid and Viper again - camera still not working in normal mode or safe mode. With the ROMs that required GApps, used every package in both Open GApps and Dynamic GApps to install. No change to camera, Google Camera was unable to start as well.
- Flashed upgraded RUU (2.41.401.4 signed firmware) and went through the process of wipe/clean install custom ROM/test camera with all the above custom ROMs in normal mode and safe mode. No change in camera, though the ROMs were all excellently made
At this point I'm pretty stumped If it was a hardware problem, why did it work when I first installed LeeDroid, but not after? It's not been mishandled, it's just been sitting on my desk since I got it. The fact that it doesn't work in safe mode would suggest to me that ,maybe, a camera driver has been deleted somewhere along the way? I also tried a load of other methods I found on various message boards; flash it with no SD card inserted, flash without SIM card installed, etc. but absolutely nothing works.
Third party camera apps also don't work; most simply crash on starting. Open Camera says "Unable to access camera. Maybe being used by another app?", so I tried removing the permissions of all apps that had access to the camera except the camera itself - no change. Deleted cache/data/preferences of all apps - no change.
Finally, I had a look at the HTC diagnostics test using *#*# 3424 #*#* on the dialler - the camera test doesn't even show up! :crying:
I've run out of things to try at this point, so I'm posting this here to see if anyone can possibly shed some light on this very strange situation. Is there something I can do to fix it? Or should I start begging Amazon to give me a refund? Unfortunately I'm a week outside their 30 day return window...lesson learned for next time; if in doubt, send it back!
Oops, meant to post this in the Q and A forum. Don't want to spam a duplicate, is it possible to move it over?
Hardware issue. Contact HTC for a replacement. sounds like it may just not be connected. I had one with no working vibration notification, the motor would turn on, you could hear it, but the phone wouldn't vibrate. Got it replaced ASAP! I recommend you do the same!
FinnMacKool said:
Hi all,
I've been having quite a few problems with my month-old HTC 10, specifically with the camera (and the WLAN coverage, but at least that's working somewhat!) I finally unpacked it last week and have spent the whole week since attempting to fix the "Camera has stopped/Unable to connect to camera" problem. The selfie camera, however, is perfect and can be used in other apps, but attempting to switch to the camera on the back results in a freeze/force close. Considering I decided on the HTC 10 because of the camera quality, I'm a bit disappointed so far. A google search reveal a number of people having the same problem, but no real solution. Here's what I've done so far:
- !
Click to expand...
Click to collapse
Same issue here. The only thing that works for me (so far) is flashing back to a Marshmallow rom. HTC has been completely silent on this issue in terms of actually fixing the problem. They know the problem is there for only a small number of us and so aren't going to do anything about it. Fine. This was my first and will be my LAST htc phone. Buh bye htc, you'll never get another dime from me.
Did you fix the issue, coz i have the same in my HTC 10
Hi
follow my post in anildsouza73 blog..I will show how to fix it if someone really spoiled it...have a good day..
from yesterday morning the problem appeared to me. Initially, the difficulty in focusing, then rebooting the impossibility of opening the camera app and the flashlight. I found on Youtube the videos that showed the same problem. Is there a solution today?
Hi all
I found if I cleared my flashlight cache and then the camera cache, soft reset phone I could get the camera working again. Only problem now is the autofocus is not working properly. Any ideas for that?
Same problem. Focus stopped working, then I cannot launch camera app. Anyone found a solution?

Categories

Resources