Hi
This is my first post here. I have come across a problem and need some help. We bought 4 galaxy grand i9082s in Pakistan and I flashed Indian XXUBMI1 4.2.2 firmwares on all of them using odin 3.07 (since 4.2.2 updates for Pakistani firmware were not available so I chose the neighbor's ). The updated firmware works fine on all of the devices except one whose motion sensors (accelerometer, gyro and orientation) are no longer working. The Samsung test feature (*#0*#) showed that accelerometer and gyro were not picking any data at all (x=0, y=0, z=0, and it remains zero). I then reinstalled the old firmware 4.1.1 and the sensors were working fine with it, but again after upgrading to 4.2.2 they stopped working (virtually making the phone not-upgradable to 4.2.2). I tried different countries' firmware on the phone but the result was sensors are working in 4.1.1 but not 4.2.2. Please guide me how to solve this problem and make the phone at par with the others.
P.S. Only one device has encountered this problem
I have tried the following for a solution:
1. Factory reset and data wipe
2. Downgrade to 4.1.1 (sensors working fine) and re-flash 4.2.2 (sensors no longer working)
3. Downgrade to 4.1.1 (russian version, sensors working fine) and get the OTA 4.2.2 update (sensors no longer working)
4. Installed philz_touch_5.15.0-i9082 recovery, rooted the phone with Update-SuperSU-v1.25 (however I don't know of any software that could reset the sensors)
5. Tried installing different kernels
6. Calibrate with Sensor Tester (works only in 4.1.1 but doesn't do anything on 4.2.2)
My guess is the problem is with the bootloader (or where ever the drivers are), maybe I made some mistake during the first upgrade and it set some flag to dirty or something, now its not resetting (because the update is working fine on rest of the 3 devices, if there was any hardware compatibility issue it wouldn't be working on them too)
Now I even tried NAND reset all on odin but no luck :crying:. Same problem persists (works in 4.1.1 but not in 4.2.2) and I am scared to use any other options in odin. I also just tried rooting the phone and checking options in wanam xposed software but nothing could be found. Also tried cleaning delvik cache and formatting everything from recovery such that the phone only showed galaxy grand sign and not move any further, then I flashed the firmware (latest vietnamese one XXUBMJ4), but same problem :crying:.
I don't think this is because of some wrong settings (because the test mode should pick something no matter what the settings, right). And since it works in 4.1.1 means hardware is also fine. Then what the heck is wrong with this particular phone. I noticed that on other phones (the ones on which everything is fine with 4.2.2), I noticed that RF cal and HW Rev show unknows while on this one they show 20121109 and REV0.4 respectively. Does that make a difference???
Please help, I haven't been able to sleep since 2 nights now because of this
Related
Hi everybody,
I got a problem which i've spent days searched all over the internet and tried so many different methods but still no hope. So posting this thread here is the only last hope, please anyone help me?
I recently got a problem with GPS service. Whenever i open the map search for a direction, it works, but it only give me the direction list but not navigation because the phone can't not be located.
And here is the point: I'm using different roms nothing works except LiquidSmooths Roms, But my favorite one is Frosty JB v6.
Please anyone?!
Had a similar problem after flashing 10.1 GPS wouldn't show in the left hand corner I had to get a new phone through warranty although I managed to fix it before returning it by Odin back to 4.0.4
Sent from my SGH-T999 using xda premium
I had a similar problem. There have been a couple of fixes posted. It generally happens when you downgrade from a 4.2 ROM back to 4.1. This is what I did to fix it:
1. Flashed a CM10 ROM (ex. LiquidSmooth)
2. Verified that GPS was working in that ROM (it should be working!)
3. ODIN to stock JB Touchwiz firmware (UVDLJA for TMobile users)
4. Once flashed and on stock firmware, verify the GPS is working (it should be working!)
5. Rooted the firmware and flashed to desired 4.1.1 ROM (ex. FrostyJB)
6. GPS should still be working!
Hope this helps!
I just started having that issue myself. I flashed back to original firmware via Odin. Still not working. Is there an issue with the GPS radia and possibly a fix?
limpexowns said:
I had a similar problem. There have been a couple of fixes posted. It generally happens when you downgrade from a 4.2 ROM back to 4.1. This is what I did to fix it:
1. Flashed a CM10 ROM (ex. LiquidSmooth)
2. Verified that GPS was working in that ROM (it should be working!)
3. ODIN to stock JB Touchwiz firmware (UVDLJA for TMobile users)
4. Once flashed and on stock firmware, verify the GPS is working (it should be working!)
5. Rooted the firmware and flashed to desired 4.1.1 ROM (ex. FrostyJB)
6. GPS should still be working!
Hope this helps!
Click to expand...
Click to collapse
I will confirm that moving from a 4.2 ROM to a 4.1 ROM (with all the necessary steps and wipes in between) will leave you without GPS. As discovered from scouring the various ROM threads, this also appears to be a hardware inconsistency problem (different factories use different distributors to build the same phones) and not everyone has this problem. This might be a problem with all T999 S3's but I do not have multiple phones so I am unable to test or confirm.
Has anyone flashed from a 4.2 back to a 4.1 and still had GPS?
I have done this with multiple 4.2 and 4.1 ROMs. So far, I have done this twice (from different 4.1 and 4.2 ROMs) and I always lose GPS.
Has anyone found a fix or is this a problem that we just have to deal with on our phones?
kpraytor said:
I will confirm that moving from a 4.2 ROM to a 4.1 ROM (with all the necessary steps and wipes in between) will leave you without GPS. As discovered from scouring the various ROM threads, this also appears to be a hardware inconsistency problem (different factories use different distributors to build the same phones) and not everyone has this problem. This might be a problem with all T999 S3's but I do not have multiple phones so I am unable to test or confirm.
Has anyone flashed from a 4.2 back to a 4.1 and still had GPS?
I have done this with multiple 4.2 and 4.1 ROMs. So far, I have done this twice (from different 4.1 and 4.2 ROMs) and I always lose GPS.
Has anyone found a fix or is this a problem that we just have to deal with on our phones?
Click to expand...
Click to collapse
This what I did to get my GPS back.
http://forum.xda-developers.com/showthread.php?t=2111306
I noticed that for some unknown reason my accelerometer and gyroscope just stopped working. I have managed to fix it and thought I would just give my story in case anyone else has this problem.
I did drop my phone but not badly and it landed on a relatively soft floor.
I tried factory resetting battery, pull, and full wipe and reinstall of custom roms. NONE of these options worked.
The only thing that managed to reset it was doing an update through Odin with an official samsung rom 4.4 that I downloaded from samsung
http://www.sammobile.com/firmwares/1/
This was the only way to reset the accelerometer and gyroscope sensors, it also updated the baseband version to a kitkat 4.4 compatible one so I suspect if I do go back to the custom roms again (I was on Carbon Rom) this baseband update will stay with the device.
Anyway it is all working now and I am very happy the updated samsung rom in much much better and more debugged than the stock rom that it had when I got it so I think I am going to try it out for a while and see how it goes I will undoubtedly go back to custom roms but in terms of recovery it is nice to know that a flash of the official rom will truely and fully reset and calibrate the sensors like the gyroscope and accelerometer.
cheers
:cyclops:
Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.
nelson2006 said:
Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.
Click to expand...
Click to collapse
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.
snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
I haved tried the first two steps and no luck at all. Maybe this weekend I'll try the third one. Thank you for the reply.
snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
RoyaLKurTx3 said:
On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.
Click to expand...
Click to collapse
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.
nelson2006 said:
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.
Click to expand...
Click to collapse
The problem, in fact is a fault in the hardware problem. If it's still under warranty, request a new phone.
Reposted in the correct forum
Afternoon everyone, I was hoping someone could assist with this problem, I have a Galaxy Tab 3 7" wifi only, I was running everything as stock inc 4.1.2 firmware, then I was prompted for an upgrade to 4.4.2, I stupidly did this without reading up ! I use to run the Tomtom software on my tab, used it everyday for work, now since the upgrade the tab will not find a GPS signal, no matter how long I leave it, after a few hours of reading and trying different things, cache cleared, reinstalled the app, restore to stock twice (still on 4.4.2) Im at a loss. I have read once its upto 4.4.2 it cannot go back to 4.1.2 as the boot loader is locked ? I am currently downloading a clean instal from Samobile of 4.4.2 to see if that will fix it, installed via Odin 3.10.6.
If anyone has cured a similar problem or can point me in the right direction I would be most grateful
Thanks
John
sort of fixed
Couldn't seem able to find a fix for this problem I had a dabble with my Tablet, installed TWRP, backed up the 4.4.2 stock ROM, found and installed the ROM by Jon Wesley Tranchida - uber cool ROM btw - fantastic boot logo's :good: but alas, the Tablet would still not run the GPS with Tomtom. So I took a risk and found a Stock 4.1.2 ROM from here http://stockroms.webs.com/downloads deleted everything and started again, Installed the 4.1.2 Ultimate ROM, installed Tomtom again and YES, everything works okay :highfive: I really miss all the addons though that were included in the ROM by Jon Wesley Tranchida. I still don't understand why Tomtom won't see GPS or the tablet wont access the GPS on 4.4.2, after 10 hours of reading up.. Although I did read it could be some thing to do with the baseband ? its beyond me lol
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.